Facility Behaviors

Use cases and scenarios for the RES::FAC (Facilities) area of the Functional Domain Taxonomy. This area covers the creation and configuration of physical facility structures within a tenant’s organization. The primary documented use case is the automatic creation of an initial facility configuration during the new-tenant sign-up flow.

RES::FAC::0001 — Initial Facility Configuration

When a new tenant completes sign-up, the system automatically creates a minimal operations configuration consisting of a Facility, standard Stations (Receiving and Shipping), a Transfer Loop, an initial Card configuration, and bindings between the Purchasing and Demand services and the respective stations. This configuration provides the structural minimum needed to begin using the Kanban replenishment system immediately after account creation.

Persona	Owen Ownerton (Business Principal)
Depends	OAM::IAM::0001
Status	Covered

RES::FAC::0001::0001.FS — Create Minimal Organization and Facility Configuration

As the final step of the sign-up flow (see OAM::IAM::0001), the BFF calls create initial facility configuration on the Arda API. The Organization service orchestrates the creation of the following entities in sequence:

1. A Facility entity representing the tenant’s primary physical location.
2. A Receiving Station (source station) with a Receiving Discharge point.
3. A Shipping Station (sink station) with a Shipping Induct point.
4. A Transfer Loop connecting the Receiving Discharge to the Shipping Induct.
5. An initial Card configuration bound to the Transfer Loop.
6. A Purchasing service binding associated with the Receiving Station.
7. A Demand service binding associated with the Shipping Station.

The resulting structure represents the minimal viable facility: inbound materials arrive at the Receiving Station (tracked by the Purchase Queue), flow through the Transfer Loop via Kanban cards, and are consumed or shipped from the Shipping Station (tracked by the Demand service). This minimal configuration supports a single-loop replenishment model. Tenants who need more granular tracking can add internal stations later to create a multi-loop model (e.g., separate Inbound and Outbound loops with an intermediate Station representing all internal operations).

RES::FAC::0001::0002.US — Load Existing Tenant Configuration

When an existing tenant user signs in or an already-registered user completes the sign-up flow with a joining key for an existing organization, the system retrieves the existing organization configuration from getOrganizationConfiguration(tenantIdentity) rather than creating a new one. The retrieved configuration is used to compose the dashboard page. No new Facility or Station entities are created.

Summary

Use Case	Scenarios	US	FS	UC
RES::FAC::0001 Initial Facility Configuration	2	1	1	0
Total	2	1	1	0

---