Operations and supply chain landscape
Support sourcing, traceability and recall decisions by connecting recorded material flows and identifying gaps in evidence.
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 Filled
2 bundles · 2 layers · 4 findings · 8 questions
Supply network Who supplies what, through which sites and transformations.
Sources and flows
Suppliers, sites and the flows between them.
Known origin
Suppliers and sites with established origin of materials.
- Which suppliers and sites feed this flow of materials?
- Where is the origin of a component unknown, and is it flagged?
Plan versus movement
Planned flows kept apart from recorded movements.
- Is this flow a plan, a promise or a recorded movement?
- Which process step does each recorded movement belong to?
Traceability Item-level genealogy from component batches to finished units.
Genealogy
Links from inputs to outputs, based on recorded events.
Event-based genealogy
Each genealogy link backed by a transformation or movement event.
- Which events link this component batch to finished units?
- Is the actual composition recorded, or only inferred from the bill of materials?
Affected units
Provably and potentially affected units for a recall.
- Which units are provably affected by this batch?
- Which units are only potentially affected, and why?
Classifiers Filled
- Family
- Enterprise profiles
- Category
- Enterprise landscape
- Entry kind
- landscape
- Domain
- EnterpriseLND
- Industry
- Cross-industry
- Tags
- EM-LND-11W3landscapeOperationsLandscapeSupplyNetwork
What it is Filled
Flows of sourcing, transformations, inventory and deliveries with item-level traceability.
Why it exists Filled
Support sourcing, traceability and recall decisions by connecting recorded material flows and identifying gaps in evidence.
Distinguishing features Filled
- Genealogy rests on recorded events, not on what a bill of materials says should have been used.
- Plans and promises are kept apart from movements that actually happened.
- Unknown origin is flagged as a break in traceability, never filled in.
- Distinct from the inventory contour, which holds the events; this view connects them across the network.
What robots and AI may and may not do Filled
Must not
- Treat a bill of materials as proof of the actual composition of every batch.
- Report a planned shipment as a completed movement.
- Fill in an unknown origin with a probable supplier.
- Narrow a safety recall to provable units without showing the potentially affected ones.
Only with a human decision
- Deciding the scope of a recall.
- Accepting a supplier into the network where origin cannot be verified.
May
- Trace a component batch to the units built from it using recorded events.
- Separate provably affected units from potentially affected ones in a recall.
- Flag suppliers or sites where traceability is broken.
Moral aspects Filled
- Missed units in a recall can expose people to unsafe products.
- Over-wide recalls waste goods and can harm suppliers who were not at fault.
Who is affected
- End users and consumers
- Suppliers and their workers
- Operations and quality teams
Owners Filled
Steward
The supply chain traceability steward is accountable for network relationships, genealogy evidence and coordination with authoritative record owners.
Master systems
- Supplier management systems govern supplier and sourcing records.
- Manufacturing execution systems govern transformation and component consumption records.
- Warehouse management systems govern inventory and handling records.
- Transport management systems govern shipment and delivery records.
- Traceability repositories govern cross-network event and genealogy records.
Links to other meta-models Filled
neighbor
- EM-OPS-05 - Batches, movements and transformation events come from the inventory and logistics contour.
- EM-OPS-04 - Designed composition comes from the bill of materials contour and is checked against actual events.
- EM-COM-01 - Suppliers in the network are counterparties described in the relationships contour.
What else AI and robots need to interact with it Filled
Identity and identifiers required Filled
- The network has a stable identifier and a separately recorded version.
- Batches, units and logistic units retain identifiers qualified by their issuing authority and scheme, including internal identifiers or GS1 identification keys.
Direct properties not applicable Not applicable
Not applicable
Enterprise record contour: physical properties belong to referenced world models.
Recognition required Filled
- The landscape connects suppliers, sites, transformations and item-level events.
- It can be confused with a procurement plan or a static bill of materials.
Capabilities and actions required Filled
- Candidate recall scope can be derived from recorded genealogy with explicit limits from evidence completeness and reliability.
- Provably affected units and potentially affected units remain distinguishable.
- Breaks in traceability can be located by supplier and site.
Hazards and failure modes required Filled
- Unsafe products may remain in use when genealogy is inferred instead of recorded.
- Planned flows presented as actual movements can create false assurance.
- Incomplete or unreliable genealogy can understate the affected population.
Standards and interfaces optional Filled
- EPCIS from GS1 supports exchange of supply chain event data.
- Identification keys from GS1 support identification of trade items and logistic units.
- IEC 62264 from the International Electrotechnical Commission supports integration between enterprise and manufacturing control systems.
Context of use required Filled
- The landscape supports manufacturing, food, pharmaceutical and other supply chains.
- It informs recalls, origin claims and supplier risk reviews.
Sources Filled
- Vercy composition and whole-object: a separate landscape object and delegation
- ArchiMate/ISO 42010: views, questions and representation rules
- Compare participant subject models and the practical assembly of a permitted context
- Vercy Whole-Object Description Profile - Checked live (HTTP 200) on 2026-10-07.
Open questions
- How to find affected items by a component batch?
- Where does an unknown supplier break traceability?
- How to link the process to actual movement?
- Установить границу и решение reuse/extend/new по действующим спецификациям.
- Подтвердить semantic crosswalk, права и source mastership.
- Выбрать immutable refs; провести проверки fixtures до заявления о публикационной готовности.
Machine files
Provenance
enterprise research programme · published-partial
Built from: enterprise/models/em-lnd-11/brief.json, ver-cy/world-models/card-supplements/em-lnd-11.json
Still in Russian: suggested owner, blocking decisions. Translate in research/enterprise/i18n/units.en.json.