INDUSTRY FIELD GUIDE
Marine cargo handling data for AI tally reconciliation
One cargo unit can be scanned at two locations during discharge.
NAICS 488320 · Marine Cargo Handling
One cargo unit can be scanned at two locations during discharge. A tally of scans can therefore overstate the amount unloaded. OSHA’s longshoring materials provide the work context, and GS1’s event model describes how to keep location and business steps with an observation. A handling company can test custody reasoning with an offline sample. OSHA marine terminal and longshoring guidance · GS1 EPCIS guidance
Draw a fictional sequence from vessel to staging area. Use mock labels for three units and give one unit a duplicate scanner event. Mark the scan point, event time, and supervisor-confirmed discharge tally separately. Add one shipment ID with the same last characters as another. Ask the assistant to cite which evidence identifies distinct handled units and which gap remains.
Use generic props, synthetic records, or separately approved stills. Avoid live lifting, terminal equipment filming, container markings, commercial manifests, and cargo security information.
Describe a cargo tally evaluation
Original Fiund exercise
Two scan locations and a duplicate event can still describe one handled unit
A synthetic vessel-to-staging sequence uses generic objects and original scan cards. There is no live lifting, terminal equipment, commercial manifest or real cargo-security information.
| Record | Source | What it records |
|---|---|---|
| MT1 | Unit U1 scans | Shipment S-A/U1 observed at discharge point, then staging point. Staging event E2 duplicated with the same event key. |
| MT2 | Confirmed tally | Supervisor's original mock tally confirms distinct units S-A/U1 and S-A/U2 discharged. U2 has one exact matching discharge scan. |
| MT3 | Loose scan | S-B/U3 has the same last characters as S-A's shipment label but is a distinct shipment. No S-A/U3 tally or exact scan supplied. |
Question for the model
Which distinct S-A units are supported, and why cannot the raw scan total establish another handled unit?
Show the reference answer and checks
MT1 and MT2 support two distinct S-A units, U1 and U2, matching the supervisor tally. U1's scans at successive locations and duplicated E2 remain observations of the same unit. MT3 belongs to shipment S-B and cannot create an S-A/U3 record from suffix similarity. Count unique shipment/unit identities with event provenance rather than sum scans or treat every location observation as another discharged item.
- Counting repeated scans or location transitions as additional cargo units.
- Joining shipment records by matching suffixes instead of full identity.
Fields to preserve
- Full shipment and unit ID
- Defines unique cargo props.
- Scan point, time and event key
- Supports sequence and deduplication.
- Supervisor tally and missing exact match
- Provides independent review context.
Test another case
Add an S-A/U3 staging scan without discharge confirmation. Require its presence to be acknowledged while discharge status remains unsupported.
Use props, synthetic records or separately cleared stills. Exclude real markings, manifests and operating equipment footage.
Discuss a contribution
Describe the sources you control, the task they could support and what has already been checked. Use the existing-data assessment for an archive or the collection brief for a new recording project. The contributor agreement defines Fiund’s licensing authority and compensation. A guide or fictional exercise does not establish an accepted collection or a sale.