Demand

The Demand (DEM) area covers production requests — the collation layer that gathers individual kanban demand signals (and direct demand) into aggregate production tasks that orders service. These use cases describe the designed Demand module and the Demand Collation feature. They are New-distinct: no current implementation counterpart.

OPS::DEM::0001 — Collate Demand into a Production Request

Status: New-distinct.

OPS::DEM::0001::0001.UC — Collate Card Signals

As the Procurement Manager (David), I gather eligible card signals — and direct, card-less demand — into a production request for a given item at a given station, and set its intended quantity. Which signals I group together is my choice; the system enforces that a signal is never held by two live requests at once and that a signal is eligible before it is attached. Postcondition: an open production request holds the chosen signals with an intended quantity.

OPS::DEM::0002 — Run and Complete a Production Request

Status: New-distinct.

OPS::DEM::0002::0001.UC — Release, Produce, and Complete

As David, I release the request to its station (freezing the intended quantity), then as materials are produced I record them into the request’s holding pool in increments and distribute them to the waiting card signals. I complete the request when the run is done, even if the result differs from the intended quantity. Postcondition: the request is complete and its produced materials are distributed. Alternative path: a request may be canceled while still open (before release).

Summary

Use Case	Scenarios	US	FS	UC
OPS::DEM::0001 Collate Demand into a Production Request	1	0	0	1
OPS::DEM::0002 Run and Complete a Production Request	1	0	0	1
Total	2	0	0	2

---