Skip to content

System Domain Model

The Domain Model describes the specific entities and values that the system manages. It will be organized based on the Domain structure of the system functional decomposition. The models will be developed and organized as the roadmap requires and initially there may be only a few models available without an effort to cover or organize the complete system.

Important

The Definition of properties is better handled in a structured table format and has moved to Coda in System Entity Information Specification
Please refer to that document and make comments/questions/suggestions there.

The Information models described here will focus on showing the relationships between entities and the overall
structure of the information model, with the details described in the Coda Document.

Layered Information Model of Operations and Supply Chains

  • Assets: Describing the physical and digital assets and resources that manufacturing and supply chain operations use and manage.
  • Actions: Describing the atomic actions, events, and observations that are the smallest units to describe operations. e.g. machine movements, sensor readings, etc.
  • Operations: Describing discrete operations, processes and workflows, together with their execution and management that can be performed as a unit of work. E.g. material transfer, storage, cnc machining, etc.
  • Transactions: Describing the business transactions that a company performs with its customers, suppliers or internally that are units of business performance and value. E.g. Sales Orders, Receipt of good, etc…
  • Contracts: Describing the framework of agreements, standards and policies that govern the execution of Transactions and Operations.
  • Business: Describing the business creation of value and financial performance.

List of available models:

  • Common: Common Entities and Values used in multiple domains and models.
    • Lang: Extensions to concepts offered by programming languages, systems frameworks or API specifications.
      • primitives: Common data types that are useful to model explicitly for clarity.
      • identity: The concept of identity and addressability of resources in the system.
    • Types: Data Types to express specialized concepts and constructs
      • Geo: Geographical types and Values.
      • Time: Time types and Values.
  • System: Elements that compose the system itself and the information the system needs to operate.
    • Accounts: Modeling Users, Tenants and their relationships.
  • Assets: The layer in the information model that describes the physical and digital assets and resources.
    • Affiliates: Modeling the relationships between legal entities and the persons that act on their behalf.
    • Facility: The Facility Model with its supporting entities (e.g. Locations, Machines, etc.)
    • Items: Items and Inventory Model.
  • Actions: The layer in the information model that describes the atomic actions, events, and observations.
    • Actions: The Kanban Cards Model with its supporting entities (e.g. Loops)

Copyright: © Arda Systems 2025, All rights reserved

Comments