Conceptual Modeling of Inventory Management Processes as a Thinging Machine

A control model is typically classified into three forms: conceptual, mathematical and simulation (computer). This paper analyzes a conceptual modeling application with respect to an inventory management system. Today, most organizations utilize computer systems for inventory control that provide protection when interruptions or breakdowns occur within work processes. Modeling the inventory processes is an active area of research that utilizes many diagrammatic techniques, including data flow diagrams, Universal Modeling Language (UML) diagrams and Integration DEFinition (IDEF). We claim that current conceptual modeling frameworks lack uniform notions and have inability to appeal to designers and analysts. We propose modeling an inventory system as an abstract machine, called a Thinging Machine (TM), with five operations: creation, processing, receiving, releasing and transferring. The paper provides side-by-side contrasts of some existing examples of conceptual modeling methodologies that apply to TM. Additionally, TM is applied in a case study of an actual inventory system that uses IBM Maximo. The resulting conceptual depictions point to the viability of FM as a valuable tool for developing a high-level representation of inventory processes.

💡 Research Summary

The paper introduces a novel conceptual modeling approach for inventory management systems called the Thinging Machine (TM). It begins by categorizing control models into three types—conceptual, analytical (mathematical), and simulation—and points out that existing conceptual techniques such as Data Flow Diagrams (DFD), Unified Modeling Language (UML) diagrams, and Integration DEFinition (IDEF) suffer from fragmentation, inconsistent meta‑models, and a lack of a unified, holistic view. Designers and analysts must juggle multiple heterogeneous diagrams, making it difficult to understand the entire process flow and to communicate effectively with stakeholders.

To address these shortcomings, the authors propose the TM framework, which treats every entity in a system as a “thing” that flows through an abstract machine. The machine operates with exactly five primitive actions: Create, Process, Receive, Release, and Transfer. These actions correspond to the classic input‑process‑output paradigm but are generalized to capture any state change, movement, or transformation of a thing. Storage is not a separate primitive; instead, it is modeled as a post‑creation or post‑processing state. Multiple TM instances (sub‑machines) can be linked via directed flows, and triggers—represented by dashed arrows—model conditional or temporal transformations (e.g., an electricity flow triggering an air flow). This minimal set of operations is claimed to be sufficient to represent any activity within a machine, thereby simplifying model construction and maintenance.

The TM methodology is applied to a real‑world inventory system built on IBM Maximo, a comprehensive asset and enterprise resource planning platform. Maximo’s workflow nodes (start, condition, interaction, sub‑process, task, stop) and actions (create, change, incident, service request, work order) are mapped onto TM sub‑machines. Core inventory processes—purchase order creation, order approval, receipt of goods, stock‑on‑hand verification against minimum/maximum thresholds, automatic re‑order triggers, and exception handling—are expressed as sequences of TM operations. For example, a new purchase order is a “Create” event; validation and approval constitute “Process”; goods arriving from a supplier are modeled as “Transfer” followed by “Receive”; a low‑stock warning is a “Release” that triggers a “Transfer” to the purchasing sub‑machine.

The case study demonstrates several advantages. First, a single TM diagram integrates structural, behavioral, and control aspects, eliminating the need for multiple UML or IDEF diagrams and improving stakeholder comprehension. Second, the five‑operation vocabulary reduces modeling effort and eases maintenance, as extensions or modifications involve adding or re‑linking flows rather than redesigning entire diagram families. Third, TM naturally incorporates dynamic triggers and temporal constraints, making it well‑suited for representing real‑time inventory alerts, automatic reorder logic, and exception pathways. Fourth, both technical staff and business managers found the TM visualizations intuitive, enabling quicker identification of bottlenecks, redundant steps, or potential failure points.

In conclusion, the paper argues that existing conceptual modeling frameworks lack uniformity and fail to appeal to practitioners, whereas the Thinging Machine provides a concise, expressive, and unified representation for inventory management processes. By successfully applying TM to an IBM Maximo implementation, the authors validate its practical viability and suggest that TM could serve as a generic modeling tool for a wide range of business processes beyond inventory control.