Handling Unit / Logistics Container
Describe one identified logistics load, its time-bounded contents, observations and custody assertions across packing, movement and dissolution.
Bundle → Layer → Finding → Questions Filled
3 bundles · 3 layers · 5 findings · 11 questions
Unit identity and nesting What the unit is and what it contains.
Identity and type
The licence plate identifier and packaging type of the unit.
Unit identifier
The identifier that makes the unit trackable.
- Which identifier marks this handling unit, and who issued it?
- Which packaging type and reusable asset does the unit use?
Nesting and content
Parent and child units and the goods declared inside.
- Which handling units does this unit contain, and which unit contains it?
- Which goods, batches or serial numbers are declared inside it?
Movement and custody Where the unit is and who holds it.
Custody chain
Transfers of physical possession between parties.
Current custody
Who holds the unit now and since when.
- Which party has physical custody of the unit now, and since when?
- Which scans or handover events record the last transfer?
Condition at handover
Damage, seals and temperature observed at transfer.
- Was the unit intact and sealed at the last handover, and was any damage noted?
- Which conditions, such as temperature, were recorded during transport?
Lifecycle How the unit comes into being and ends.
Build and dissolution
Packing, repacking and unpacking of the unit.
Unit lifecycle
When the unit was built, changed or dissolved.
- When and where was the unit packed, and by whom?
- Was it repacked or split, and which identifiers replaced it?
- Has the unit been dissolved, and has its identifier been retired or reused?
Classifiers Filled
- Family
- World Models
- Category
- Physical world and living systems
- Entry kind
- entity
- Navigation path
- NAV.PHY.OBJ.PKG
- Domain
- PHY.OBJ.PKG
- Industry
- Cross-industry
- Tags
- handlingunitlogisticscontainerphy.obj.pkg
What it is Filled
A handling unit is a physical unit put together for transport and handling, such as a pallet, case, roll cage or shipping container, identified so that it can be moved and tracked as one object. It nests: a container holds pallets, a pallet holds cases, and each level has its own identity and custody history; the goods inside and the transport order are separate records.
In scope
- Unit identity and recognition evidence, including unresolved or conflicting labels
- Time-bounded nesting and declared, observed or reconciled content references
- Unit measurements, handling constraints, seals and condition observations with provenance
- Qualified location and custody assertions, packing changes and dissolution lineage
- Local record access, revision, retention and interoperability rules
Out of scope
- Packaging design, reusable equipment maintenance, certification, rental and asset disposal
- Item manufacture, inventory valuation, product quality determination and batch master data
- Shipment planning, carriage contracts, route execution, delivery obligations and customs clearance
- Actuating handling machinery, opening containers, breaking seals or authorizing transport
- Detailed instructions for hazardous or controlled cargo; retain policy and qualified-authority references only
Why it exists Filled
Describe one identified logistics load, its time-bounded contents, observations and custody assertions across packing, movement and dissolution.
Distinguishing features Filled
- The handling unit is the thing that is moved and scanned; the goods inside are separate records it declares.
- Units nest, and each level carries its own identifier and custody history.
- A unit is built and dissolved by packing operations, so its life is shorter than that of the goods it carries.
- Distinct from the reusable asset itself, such as a pallet or container, which outlives many handling units.
What robots and AI may and may not do Filled
Must not
- Reuse an identifier while the earlier unit can still appear in the supply chain.
- Change the declared contents of a sealed unit without recording an inspection or repack.
- Record a handover that the receiving party has not confirmed.
- Omit recorded damage, broken seals or temperature excursions from the unit's history.
- Declare dangerous goods wrongly or leave their declaration off the unit record.
Only with a human decision
- Breaking a seal or opening a unit for inspection.
- Accepting a unit with damage or a temperature excursion.
- Releasing a unit whose contents do not match the declaration.
May
- Create and record handling units with their identifier, type, contents and nesting.
- Record scans, handovers and condition observations against a unit.
- Report the current location, custody and declared contents of a unit.
- Flag mismatches between declared contents and what was scanned.
Moral aspects Filled
- Wrong declarations put handlers at risk, especially where dangerous goods are involved.
- Tracking data about units also reveals the movements and performance of the people handling them.
- Unrecorded damage shifts loss onto the party least able to prove what happened.
Who is affected
- Warehouse and transport workers
- Shippers, carriers and consignees
- Recipients of temperature sensitive goods
- Customs and inspection authorities
Owners Filled
Steward
The logistics or warehouse operations lead of the party that currently holds the unit.
Roles
- Unit data steward
- Own local schema profile, namespace and reconciliation authority
- Authorized recorder
- Submit observations with evidence and uncertainty; do not fabricate acceptance
- Custody reviewer
- Assess handover assertions under the designated acceptance policy
- Safety profile reviewer
- Review applicability, restrictions and release evidence within delegated authority
- Records and access administrator
- Enforce purpose-limited access, lawful holds, redaction and disposition
Master systems
- Warehouse management system
- Transport management system
- Container and equipment tracking system
Links to other meta-models Filled
references
- WM-OBJ-001 - Represent registry CONTAINS through time-bounded physical content edges to independently mastered item instances; quantity lines can be used where serial identities are absent.
- WM-FLW-011 - Inverse reference for incoming shipment CONTAINS. Shipment membership is commercial context and cannot substitute for physical containment, custody proof or delivery execution.
- WM-OBJ-021 - Recursive child-unit references use effective intervals and an acyclic accepted physical graph; model self-reference is not instance self-containment.
aligned
- WM-OBJ-009 - Qualify the registry parent as packaging and reusable-equipment alignment; pin an equipment reference when present without inheriting maintenance, rental or retirement ownership.
- GS1 EPCIS pinned adoption profile - Map event evidence and unit projections using an explicitly versioned profile; no conformance claim or event-server implementation.
- W3C PROV-O - Optionally express source attribution and derivation for local views without equating provenance with truth or authority.
neighbor
- WM-OBJ-009 Packaging / Returnable Asset - The candidate registry parent is accepted as conceptual alignment, not unqualified inheritance. Repeatedly used equipment can support successive loads and must retain its separate asset identity. A bare container number must not merge different load episodes.
- WM-OBJ-001 Physical Item Instance - Outgoing CONTAINS is a physical membership assertion, not record ownership. Empty, unknown and quantity-only content representations remain possible; item identity, condition master and lifecycle are external.
- WM-FLW-011 Shipment / Consignment - Incoming CONTAINS links commercial movement groupings to units. Shipment membership is not physical nesting and does not imply common location. The shipment retains contractual and delivery lifecycle ownership.
- WM-OBJ-021 child handling units - Recursive physical nesting uses time-bounded references and an acyclic active membership graph. Shared shipment membership is a different edge; inconsistent parent reports remain unresolved evidence.
- External events, places, parties and evidence records - This model stores qualified references and local assertions. Observation is not proof of a handover or title; external record systems keep execution and event master ownership.
parent
- WM-OBJ-009
contains
- WM-OBJ-001
What else AI and robots need to interact with it Filled
Identity and identifiers required Filled
- Pallets and cases are usually identified by a Serial Shipping Container Code (SSCC) on a GS1 logistics label.
- Intermodal containers are identified by a BIC-registered container number under ISO 6346.
- Identifiers must stay unique over time, so retired numbers are not reused while units may still circulate.
Direct properties required Filled
- Gross and net mass in kilograms, and tare mass of the packaging.
- Outer dimensions in millimetres, including height with the load.
- Volume in cubic metres and, for containers, declared payload capacity in kilogrammes.
- Temperature in degrees Celsius for units under controlled conditions, with the measurement point.
- Count of contained units or items, with the unit of measure stated.
Recognition required Filled
- Recognised by the printed or marked identifier, barcode, RFID tag and packaging type.
- Container numbers and check digits are marked on the container itself.
- Easily confused with a similar unit from the same shipment when the label is damaged or missing.
Capabilities and actions required Filled
- Units can be nested, split and merged with new identifiers recorded.
- Each movement can be scanned and attributed to a party and place.
- Contents can be traced from a unit to batches and serial numbers.
Hazards and failure modes required Filled
- Unstable or overweight units injuring handlers or damaging equipment.
- Wrong or missing dangerous goods declaration.
- Broken cold chain hidden by missing temperature records.
- Identifier collisions that break traceability across partners.
Standards and interfaces required Filled
- GS1 General Specifications for SSCC and the GS1 logistic label, and GS1 EPCIS for event exchange.
- ISO 6346 for freight container coding, marking and identification.
- UN/CEFACT and UN/EDIFACT messages for despatch advice and transport instructions.
Context of use required Filled
- Used in warehousing, road, rail, sea and air transport, and in customs and retail receiving.
- Dangerous goods transport rules and food traceability law apply to the declarations carried.
Sources Filled
- What is a Logistics unit and how is it identified? - GS1
- What is the main use of Global Returnable Asset Identifier (GRAI) in GS1 Transport & Logistics? - GS1
- Container Identification Number - Bureau International des Containers
- EPCIS Standard - GS1
- IMO/ILO/UNECE Code of Practice for Packing of Cargo Transport Units (CTU Code) - United Nations Economic Commission for Europe
- CTU Code Chapter 2. Definitions - United Nations Economic Commission for Europe
- Guidelines regarding the verified gross mass of a container carrying cargo - International Maritime Organization
- PROV-O: The PROV Ontology - World Wide Web Consortium
- GS1 General Specifications, GS1
- ISO 6346 Freight containers - Coding, identification and marking, ISO
- UN/CEFACT Core Component Library and supply chain messages, UNECE
Open questions
- Verify admitted source availability and authoritative versions, including CTU revision status, EPCIS version pin and scheme-specific allocation and reuse rules.
- Develop adoption profiles and executable fixtures for successive loads on one asset, quantity-only contents, incomplete scans, cycles, late events, disputed custody, sensor gaps, repacking and lawful disposition.
- Restore independent external review and complete source, profile and conformance gates before any canonical or publishable-draft promotion.
- Independent external provider review is absent
- Full current standards verification, including EPCIS URL/document version discrepancy and CTU revision adoption status
- Executable nested schemas, identifier allocation and reuse rule profiles, mappings and instance conformance fixtures
- Air cargo, tank, bulk, refrigerated, biosecurity and jurisdiction-specific handling profiles are incomplete
- Remote publication availability and operational safety or legal compliance are not established
Machine files
Provenance
world-models research · reviewable-draft
Built from: models/wm-obj-021-handling-unit-logistics-container/spec.yaml, ver-cy/world-models/card-supplements/wm-obj-021-handling-unit-logistics-container.json