BS ISO 23354-2020 Business requirements for end-to- end visibility of logistics flow.
7 Visibility data interchange requirements between LISSs
7.1 Event data classification
The LISS network should classify the types of interchanged logistics data from different views:
1. Event data relating to the mode of transport i.e. to maritime, air, train, road, rail or inland waterway.
2. Event data relating to cargo and means of transport such as logistics status data or administrative data.
3. Event data relating to B2B. G2B. or B2G.
LISS systems typically have a wide array of data exchange stakeholders, e.g. governmental agencies. port community systems, import and export companies, manufacturers, and transport service providers etc. LISS systems need to satisfy their diverse needs. B2B, G2B and B2G data interchanges are therefore a usual part of the systems’ daily operations.
Harmonized and standardized data sets and electronic messages incorporating international code standards are keys for effective and efficient B23, 32G, G2B interchanges and information sharing. Thus, efforts shall be made to build better pipeline data exchange standards (PDES) i.e. the IJN/CEFACT Multi Modal High-Level Business Requirements Specification (BRS) and the data pipeline project based on that specification shall be reused to support a more seamless flow of trade data.
4. Event data relating to public or private interests.
Most of the LISS systems are non-profit, neutral and open to both the public and private parties, such as government departments and enterprises involved in international trade. LISS systems can also provide public information services, such as statistical data reporting and relevant information on policies and regulations.
Private information is also stored in the LISS systems given that port community systems, importers and exporters, manufacturers, transport service providers and other participants in the supply chain use these systems to exchange e-documents and information with their partners.
The 5Ws (Whom, What, When, Where, Why) framework can be used to abstract all elements of different event data objects as shown below.
1. Whom: With whom to interchange information (Role definition).
2. What: What event object (also known as resource) such as vessel, vehicle, flight, train and cargo.
3. When: The occurrence or recording time of an event.
4. Where: The location details of where an event occurs.
5. Why: The type of an event and its reason where relevant (status condition and reason codes such as listed in UNECE Recommendation 24 – Transport and Logistics Status Code List).
Reported event examples include:
1. Vessel and Cargo events during maritime transport;
2. Vehicle and Cargo events during road transport;
3. Flight and Cargo events during air transport;BS ISO 23354 pdf download.