Facilities

The Facilities model describes physical sites where production processes and operations are performed, and the organizational structure of nodes (producers and consumers) within those sites.

Facility

A Facility is a physical location scoped to a tenant where production processes and operations are performed. It is geographically compact and has distinct receiving and shipping processes served by transportation assets.

Property	Type	Multiplicity	Description
name	String	[1..1]	Name of the facility
postalAddress	Address	[1..1]	Postal address of the facility
receivingAddresses	Address	[0..*]	Receiving dock addresses
shippingAddresses	Address	[0..*]	Shipping dock addresses
nodes	Node	[1..*]	Nodes that perform operations in the facility
belongsTo	Reference to Organization	[1..1]	The organization that operates this facility
locations	Location	[0..*]	Named locations configured within the facility

Location

A Location is a named physical location within a facility, scoped to that facility. Locations provide the addressing system for kanban card placement and inventory positioning.

Property	Type	Description
name	String	Name of the location within the facility
spatial	(spatial value)	Optional spatial coordinate information

Node Hierarchy

A Node is an abstraction representing the origin or destination of Kanban loops within a facility. The node hierarchy models the flow of materials through operations.

Node (abstract)

The base type for all nodes. A node has a name unique within the facility and tenant, and an optional location reference.

Producer (abstract)

A node that produces materials as fulfillment for kanban cards. A producer has one or more discharge points where produced materials are delivered.

Consumer (abstract)

A node that consumes materials from kanban cards and issues demand upstream for replenishment. A consumer has one or more induct points where materials are received for its operation.

Station

A Station is both a Producer and a Consumer — it is the smallest unit where complete operations take place. Materials are consumed from incoming cards and produced in response to other cards’ demand. A station has both induct points (for receiving materials) and discharge points (for delivering produced materials).

Inbound (abstract)

A node that inbounds materials from outside the system, typically through receiving at a dock. Inbound nodes may also model interfaces to operations not controlled by Arda.

• RawMaterials: An internal source of materials not controlled by Arda.
• Receiving: A source that procures materials from external parties, typically with associated commercial paperwork (purchase orders, delivery receipts).

Outbound (abstract)

A node that outbounds materials to outside the system. Outbound nodes consume materials from cards and may represent shipping docks or interfaces to operations not controlled by Arda.

• FinishedGoods: An internal consumer of materials not controlled by Arda.
• Shipping: A consumer that ships materials to outside parties, typically with associated commercial paperwork.

Induct and Discharge

• Induct: An endpoint where materials are received for an operation (used by Consumer nodes). Has an optional batch size parameter.
• Discharge: An endpoint where materials are delivered by an operation (used by Producer nodes). Has an optional batch size parameter.

Relationship to Kanban Loops

The Facility node hierarchy is the structural foundation for kanban loops. A Loop entity (see Kanban Cards) connects an origin node (typically a Discharge on a Producer) to a destination node (typically an Induct on a Consumer). Cards circulate through this loop, triggering replenishment when consumed and returning to the producer when fulfilled.