physical measurements and parameters. In addition to the periodic measurements, new data elements also include inputs such as expected physical values or trip plan descriptions that enable the smart container solution provider to generate alerts and predictive values, like Estimated Time of Arrival (ETA). The Library provides clear semantic data exchange standards, so all stakeholders understand the same data element in the same way. The deliverable is the Smart Container Business Requirements Specifications (BRS). This step is complete.
Steps Share a common
1 2
3 4
understanding of the Smart Container Business use cases & stakeholders: SCOPE
Define structured data elements generated by smart container and their qualifiers TERMINOLOGY/SEMANTIC
Select the data elements for a given use case
Choose the SYNTAX (language) to be used to communicate
The UN/CEFACT Smart Container project is a collaborative initiative comprised of volunteer experts (over 50) from intergovernmental organizations, individual countries’ authorities, and the business community. Adoption of UN/CEFACT standards is entirely voluntary.
Envisioning the State of the Art Today, there is a need for a clear
Smart Container White Paper
Business Requirements Specifications (BRS) & Entities Relationship Diagrams
Generic message structure (Technology Neutral)
APIs
data exchange standard to enhance the collaboration between multiple stakeholders that are involved in the information linked to a single smart container.
Hence, stakeholders are increasingly reluctant to adopt proprietary standards and risk being locked into one solution provider. Agreed-upon API standards enable stakeholders to
Project Working Group from different backgrounds
Step 3: Select required data elements from the Library for the smart container project and define semantics for all new generated data elements and their relationships. This includes creating semantics for business definitions and data structures. The deliverable will be a data model and associated schema based on the UN/CEFACT Multi-Modal Transport Reference Data Model, which is a subset of the Core Components Library. This step is in progress.
Step 4: Select a subset of data to define a contextualized message structure to meet the requirements of a given use case. The message structure is technology-agnostic - independent of the technology used to communicate the data. This step is in progress.
Step 5: Define the message from the syntax point of view using a chosen technology, which will result in API definitions based on standardized data elements. This step is planned.
Figure 1: UN/CEFACT Smart Container Methodology. From data elements to APIs definition Deliverables Resources
UN/CEFACT CODES Lists & Multi Modal Transport
Reference Data Model (MMT)
Contextualized Notification Messages Structures
Multi Syntax World
adopt the services of their choice and add or change providers as their business needs require— without the fear of obsolescence, high support costs for legacy technology, or inability to meet customers’ needs. Without defined standards, Smart Container solution providers will have to develop their own interfaces to each stakeholder, adding cost and slowing time to market.
The Smart Container project aims to create the state of the art in providing and exposing services that can be orchestrated and enriched to meet business process needs of any intermodal ecosystem stakeholder. The availability and exposition of these services can boost the digital transformation of the transportation and logistics industry, fuelling innovation in applications and services.
For more information, contact Hanane Becha, UN/CEFACT Smart Container Project Lead, at
h.becha@
traxens.com or visit
https://www.traxens.com
The Report • March 2020 • Issue 91 | 71
Page 1 |
Page 2 |
Page 3 |
Page 4 |
Page 5 |
Page 6 |
Page 7 |
Page 8 |
Page 9 |
Page 10 |
Page 11 |
Page 12 |
Page 13 |
Page 14 |
Page 15 |
Page 16 |
Page 17 |
Page 18 |
Page 19 |
Page 20 |
Page 21 |
Page 22 |
Page 23 |
Page 24 |
Page 25 |
Page 26 |
Page 27 |
Page 28 |
Page 29 |
Page 30 |
Page 31 |
Page 32 |
Page 33 |
Page 34 |
Page 35 |
Page 36 |
Page 37 |
Page 38 |
Page 39 |
Page 40 |
Page 41 |
Page 42 |
Page 43 |
Page 44 |
Page 45 |
Page 46 |
Page 47 |
Page 48 |
Page 49 |
Page 50 |
Page 51 |
Page 52 |
Page 53 |
Page 54 |
Page 55 |
Page 56 |
Page 57 |
Page 58 |
Page 59 |
Page 60 |
Page 61 |
Page 62 |
Page 63 |
Page 64 |
Page 65 |
Page 66 |
Page 67 |
Page 68 |
Page 69 |
Page 70 |
Page 71 |
Page 72 |
Page 73 |
Page 74 |
Page 75 |
Page 76 |
Page 77 |
Page 78 |
Page 79 |
Page 80 |
Page 81 |
Page 82 |
Page 83 |
Page 84 |
Page 85 |
Page 86 |
Page 87 |
Page 88 |
Page 89 |
Page 90 |
Page 91 |
Page 92 |
Page 93 |
Page 94 |
Page 95 |
Page 96 |
Page 97 |
Page 98 |
Page 99 |
Page 100 |
Page 101 |
Page 102 |
Page 103 |
Page 104
