Operations

Orchestration of internal manufacturing and business processes within a facility — production runs, work orders, internal material flows, and inventory state — that do not involve external suppliers or customers. The OPS domain is intentionally minimal today; content emerges as specific manufacturing process types are modeled. Canonical domain reference: Operations (OPS).

Context

The domain’s modules and their relationships, with the client and server domains wired to the actual modules they depend on. Clients sit to the left of the servers they depend on; every arrow is a dependency the client calls, and together they form a DAG.

The domain holds one module today, Demand. Orders service its demand items from above, and receiving records production deliveries against them; downward it reaches all three resources modules (the collated card signals, the holding pool, the anchoring station) and the item catalog.

Linear

• Initiative: Product / Operations

Sub-areas

• Demand — demand items: collating individual kanban demand signals into aggregate production tasks that orders service (in development)
• Inventory
• Material Flows