Smart Container Business Requirements Specifications (BRS)
Total Page:16
File Type:pdf, Size:1020Kb
Final September 2019 UNITED NATIONS ECONOMIC COMMISSION FOR EUROPE UNITED NATIONS CENTRE FOR TRADE FACILITATION AND ELECTRONIC BUSINESS (UN/CEFACT) BUSINESS REQUIREMENTS SPECIFICATION (BRS) Smart Containers Approved: UN/CEFACT Bureau on 30 September 2019 Version: 1.0 1. Introduction The aim of this document is to define the data elements required for a Smart Container Solution. First, we will detail use cases to share a common understanding of the potential of the Smart Container Solutions and then derive the data elements. We will use the existing data elements of the UN/CEFACT Core Components Library (CCL), in particular, the Multi-Modal Transport (MMT) subset, a.k.a. the MMT Reference Data Model. Whenever new data elements are needed, they will be included in the CCL and the MMT subset. Depending on the use case, a different set of data elements may need to be transmitted to satisfy its Smart Container Solution. The use cases are prioritized and organized accordingly. The sum of all data elements for all use cases would provide all data that may be required in any message format used within the context of Smart Container Information Exchanges. The aim of this work is to define only WHAT may be exchanged among stakeholders and not the HOW this information may be exchanged (e.g. EDI, API, EPCIS). The message exchanged will contain only a subset of “the sum of all data elements”. Data governance and roles/credentials-based access to the smart containers’ data elements are part of the terms of contracts in place between the smart containers’ service providers and the logistic chain stakeholders. The ‘smart container solution’ is based on different technical pillars: 1) an active smart device fixed on a container or included in the container, 2) a platform collecting the data, processing it and sharing with the different stakeholders, and 3) various communication protocols including those wireless communications technologies enabling multi-hopping and collaboration between devices. A ‘smart device’ has an embedded sensor or set of sensors. Extra remote sensors could also be added/paired with the main device to address the specific needs of a given cargo consignment. 2 2. Table of Contents 1. Introduction ..................................................................................................................................... 2 2. Table of Contents ............................................................................................................................ 3 3. Glossary and Business Context ........................................................................................................ 5 4. Business Use Cases Overview Table .............................................................................................. 13 5. Business Use Cases Details ............................................................................................................ 17 Business Use Case 1: Operational - Estimated Time of Arrival (ETA) Updates................................. 17 Business Use Case 2: Operational and Security Awareness - Actual Executed Transit Time ........... 18 Business Use Case 3: Operational and Security Awareness - Schedule Deviation Alert (Trip In Progress versus Planned Trip) ........................................................................................................... 19 Business Use Case 4: Operational and Security Awareness - Unexpected Door Opening Detection ........................................................................................................................................................... 21 Business Use Case 5: Operational and Security Awareness- Unexpected Temperature change for Temperature Sensitive Cargo ............................................................................................................ 22 Business Use Case 6: Operational and Security Awareness - Unexpected Humidity Change for Sensitive Cargo .................................................................................................................................. 23 Business Use Case 7: Operational - Missing containers from onboard of vessels ........................... 24 Business Use Case 8: Operational - Short-shipped: Containers left behind on the pier or Rolled off ........................................................................................................................................................... 25 Business Use Case 9: Operational - Overlanded Container: discharged in the wrong port ............. 26 Business Use Case 10: Operational - Fragile Cargo / Breakable Artefacts ........................................ 27 Business Use Case 11: Operational - Dry Container Temperature Monitoring................................ 28 Business Use Case 12: Operational and Security Awareness - Empty gate-in/gate-out at Depot ... 29 Business Use Case 13: Operational and Security Awareness - Depot reconciliation ....................... 30 Business Use Case 14: Operational - Container Daily Status Message for fleet management & Usage KPIs ......................................................................................................................................... 31 Business Use Case 15: Operational and Security Awareness - Trip Tracking for merchant haulage container ........................................................................................................................................... 32 Business Use Case 16: Operational and Security Awareness - Fast lanes for cross-border agencies ........................................................................................................................................................... 33 Figure 21: Fast lanes for cross-border agencies ............................................................................ 34 Business Use Case 17: Compliance- Contract Compliance of Container Routing ............................ 34 Business Use Case 18: Green Maintenance - Reefer Pre-trip Inspection (PTI) on demand = predictive maintenance ..................................................................................................................... 35 Business Use Case 19: Quality- .......................................................................................................... 36 Identifying the shipment ................................................................................................................... 36 3 Business Use Case 20: Sovereign- Port Infrastructure usage monitoring by Port Authority ........... 37 Business Use Case 21: Operational – Intermodal Change ................................................................ 38 Business Use Case 22 – Additional Sensors: Fixed or Ad-hoc ........................................................... 39 6. Business Process Diagrams ............................................................................................................ 41 7. Inputs for Smart Container Data Modeling ................................................................................... 51 8. Door-to-door Common Reference ................................................................................................ 54 9. Conclusion ..................................................................................................................................... 57 Annex 1 – Standards relevant to Smart Containers ...................................................................... 58 Annex 2 – Inputs for Smart Container Data Modeling .................................................................. 60 Device ........................................................................................................................................ 68 Sensor ........................................................................................................................................ 69 Container ................................................................................................................................... 69 Event .......................................................................................................................................... 70 Transport Booking ..................................................................................................................... 72 Means of Transport ................................................................................................................... 74 Annex 3 - Mapping Data Elements to Use Cases ........................................................................... 75 4 3. Glossary and Business Context Term / Abbreviation Description Ad-hoc additional These sensors are added in ad-hoc manner inside of the cargo, . The ad- Sensors hoc sensors are not embedded in the tracking devices however they communicate with the cloud via the tracking device. AIS Automatic Identification System: Automatic, self-organizing tracking system transmitting vessels’ positional and static information via VHF frequencies. Mandatory for commercial vessels under the SOLAS agreement primarily for Safety of Navigation reasons. Signal reception can be achieved by coastal receiving stations or satellites. ASC MH10 ASC MH10 is an American National Standards Institute (ANSI) Accredited Standards Committee. Among other things, MH10 concerns itself with standards for Unit-Loads & Transport-Packages. BAPLIE (BAyPLan Including Empties.) The BAPLIE message is a widely used EDIFACT message in the shipping industry. It is used by and between various