Inventory, production and logistics
Batches, serialized units, stock levels, transformations, movements and shipments. The balance is derived from events with explicit adjustments.
Research draft, second pass
A second pass drafted this model: the structure a model of this thing needs, and what is known about it in the world. The line under this one says how the second half was obtained - researched against sources, or recalled without web access, in which case nothing here was read anywhere and every claim is a lead to verify. Unreviewed either way.
Bundle → Layer → Finding → Questions Missing, in the backlog
Not described yet. This gap is in the card backlog.
Note: Research contour: bundles not designed yet; questions are listed as open questions.
Classifiers Filled
- Family
- Enterprise profiles
- Category
- Enterprise subject
- Entry kind
- subject
- Domain
- EnterpriseOPS
- Industry
- Cross-industry
- Tags
- EM-OPS-05W3subjectLotStockPositionTransformationEventShipmentLogisticsEvent
What it is Filled
Batches, serialized units, stock levels, transformations, movements and shipments. The balance is derived from events with explicit adjustments.
Why it exists Filled
Batches, serialized units, stock levels, transformations, movements and shipments. The balance is derived from events with explicit adjustments.
Distinguishing features Derived, awaiting review
- Units of measure are consistent
- A transformation preserves genealogy
- A stock adjustment has a basis
What robots and AI may and may not do Derived, awaiting review
Must not
- Negative case: Shipped means delivered and accepted by the buyer.
Note: Negative case of the research brief, not yet a rule for agents.
Moral aspects Missing, in the backlog
Not described yet. This gap is in the card backlog.
Owners Filled
Steward
Операционный руководитель
Master systems
- BPM
- ERP
- WMS
- PLM
- EAM
Links to other meta-models Filled
neighbor
- EM-COM-03
- EM-OPS-02
- EM-OPS-04
references
- WM-ECO-024 - conceptual-candidate
What else AI and robots need to interact with it Incomplete
Identity and identifiers required Derived, awaiting review
- Lot
- StockPosition
- TransformationEvent
- Shipment
- LogisticsEvent
Direct properties not applicable Not applicable
Not applicable
Enterprise record contour: physical properties belong to referenced world models.
Recognition required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Capabilities and actions required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Hazards and failure modes required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Standards and interfaces required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Context of use required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Sources Filled
- APQC/BPMN: process definitions and execution
- GS1 EPCIS/SCOR: traceability and supply chain
- IDTA AAS and PLM/EAM/WMS practice: product, instance and maintenance
Open questions
- How to link input batches to output products?
- How to distinguish a promised delivery from an actual movement?
- How to execute a recall of an affected batch?
- Установить границу и решение reuse/extend/new по действующим спецификациям.
- Подтвердить semantic crosswalk, права и source mastership.
- Выбрать immutable refs; провести проверки fixtures до заявления о публикационной готовности.
Machine files
Provenance
enterprise research programme · published-partial
Built from: enterprise/models/em-ops-05/brief.json
Still in Russian: suggested owner, blocking decisions, vercy candidates. Translate in research/enterprise/i18n/units.en.json.