ISO 23354:2020
(Main)Business requirements for end-to-end visibility of logistics flow
Business requirements for end-to-end visibility of logistics flow
This document specifies three business requirements for the visibility of logistics traffic flow based on the use cases and gap analysis in Annex A. It includes 1) LISS network architecture requirements, 2) visibility data interchange requirements between LISSs, and 3) visibility data interface and process requirements for an LISS network. These three business requirements are described further in Clause 6, Clause 7 and Clause 8 respectively. Furthermore, Clause 8 describes the requirement for a guideline for business participants and stakeholders in an LISS network such as logistics information service providers, single window/SSP operators, data providers and logistics data users. This document does not include standardization 1) at the level of logistics devices (areas of standardisation covered by ISO/TC 104, ISO/TC 204), 2) for ships, navigation and marine technologies (areas of standardisation covered by ISO/TC 8), or 3) related to international data exchange such as standards developed, published and maintained by UN/CEFACT, GS1, WCO which are referenced as appropriate in this document.
Titre manque
General Information
Standards Content (Sample)
INTERNATIONAL ISO
STANDARD 23354
First edition
2020-04
Business requirements for end-to-end
visibility of logistics flow
Reference number
ISO 23354:2020(E)
©
ISO 2020
---------------------- Page: 1 ----------------------
ISO 23354:2020(E)
COPYRIGHT PROTECTED DOCUMENT
© ISO 2020
All rights reserved. Unless otherwise specified, or required in the context of its implementation, no part of this publication may
be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting
on the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address
below or ISO’s member body in the country of the requester.
ISO copyright office
CP 401 • Ch. de Blandonnet 8
CH-1214 Vernier, Geneva
Phone: +41 22 749 01 11
Fax: +41 22 749 09 47
Email: copyright@iso.org
Website: www.iso.org
Published in Switzerland
ii © ISO 2020 – All rights reserved
---------------------- Page: 2 ----------------------
ISO 23354:2020(E)
Contents Page
Foreword .iv
Introduction .v
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 1
4 Abbreviated terms . 2
5 Business requirements overview . 2
6 Logistics information service system network architecture requirements .4
6.1 Network architecture requirements overview. 4
6.2 LISS network entities . 5
6.2.1 Logistics information service system (LISS) . 5
6.2.2 Single window . 6
6.2.3 Data providers . 6
6.2.4 Data users . 6
6.3 Network architecture requirement between different LISSs . 6
6.4 Network architecture requirement between LISS and SW/SSP. 6
6.5 Network architecture requirement between LISS and data providers . 6
6.6 Network architecture requirement between LISS and data users from other LISSs . 6
7 Visibility data interchange requirements between LISSs . 7
7.1 Event data classification . 7
7.2 Data control for different entities in the LISS network . 8
8 Visibility data interface and process requirements for LISS network .8
8.1 Unified user management and authentication process requirements . 8
8.1.1 Federation authentication among LISSs . 8
8.1.2 Enable users log in to multiple LISSs and query services by single sign-on . 8
8.2 Open data access . 8
9 Guideline for business participants and stakeholders . 8
9.1 LISS operator . 8
9.2 Single window operator . 9
9.3 Data providers . 9
9.4 Data users . 9
Annex A (informative) Use cases and gap analysis .10
Annex B (informative) Related standards and organizations .17
Bibliography .23
© ISO 2020 – All rights reserved iii
---------------------- Page: 3 ----------------------
ISO 23354:2020(E)
Foreword
ISO (the International Organization for Standardization) is a worldwide federation of national standards
bodies (ISO member bodies). The work of preparing International Standards is normally carried out
through ISO technical committees. Each member body interested in a subject for which a technical
committee has been established has the right to be represented on that committee. International
organizations, governmental and non-governmental, in liaison with ISO, also take part in the work.
ISO collaborates closely with the International Electrotechnical Commission (IEC) on all matters of
electrotechnical standardization.
The procedures used to develop this document and those intended for its further maintenance are
described in the ISO/IEC Directives, Part 1. In particular, the different approval criteria needed for the
different types of ISO documents should be noted. This document was drafted in accordance with the
editorial rules of the ISO/IEC Directives, Part 2 (see www .iso .org/ directives).
Attention is drawn to the possibility that some of the elements of this document may be the subject of
patent rights. ISO shall not be held responsible for identifying any or all such patent rights. Details of
any patent rights identified during the development of the document will be in the Introduction and/or
on the ISO list of patent declarations received (see www .iso .org/ patents).
Any trade name used in this document is information given for the convenience of users and does not
constitute an endorsement.
For an explanation of the voluntary nature of standards, the meaning of ISO specific terms and
expressions related to conformity assessment, as well as information about ISO's adherence to the
World Trade Organization (WTO) principles in the Technical Barriers to Trade (TBT) see www .iso .org/
iso/ foreword .html.
This document was prepared by Technical Committee ISO/TC 154, Processes, data elements and
documents in commerce, industry and administration.
Any feedback or questions on this document should be directed to the user’s national standards body. A
complete listing of these bodies can be found at www .iso .org/ members .html.
iv © ISO 2020 – All rights reserved
---------------------- Page: 4 ----------------------
ISO 23354:2020(E)
Introduction
Visibility of logistics traffic flow and finding the precise logistics information in a simple and trusted
way are very important for the logistics processes in international trade.
However, the logistics data to be obtained by the logistics operator is often provided by several logistics
information service systems (LISS) and other logistics and/or trade parties. Although international
standards (such as UN/EDIFACT) have existed for decades and many national and regional systems
have been implemented based on such international standards, LISSs are often developed in isolation
and fragmentation based on their individual business requirements; and this has led to many different
and non-interoperable interpretations of standard messages. In order to realize the visibility of logistics
traffic flow, data from different LISSs should be interchanged with each other by using a standardized
method to establish an LISS network.
This document specifies three business requirements of a future LISS network. The purpose of including
the network architecture in this document is to support the business requirements of data exchanges
between different LISSs on the application layer. Existing international standards (Annex B) can be
reused in a standardized way and any gaps filled by new international standards where identified. This
document is an important reference and guideline to related logistics parties such as LISS providers,
single window/SSP operators, logistics data providers and logistics data users.
© ISO 2020 – All rights reserved v
---------------------- Page: 5 ----------------------
INTERNATIONAL STANDARD ISO 23354:2020(E)
Business requirements for end-to-end visibility of
logistics flow
1 Scope
This document specifies three business requirements for the visibility of logistics traffic flow based on
the use cases and gap analysis in Annex A. It includes
1) LISS network architecture requirements,
2) visibility data interchange requirements between LISSs, and
3) visibility data interface and process requirements for an LISS network.
These three business requirements are described further in Clause 6, Clause 7 and Clause 8 respectively.
Furthermore, Clause 8 describes the requirement for a guideline for business participants and
stakeholders in an LISS network such as logistics information service providers, single window/SSP
operators, data providers and logistics data users.
This document does not include standardization
1) at the level of logistics devices (areas of standardisation covered by ISO/TC 104, ISO/TC 204),
2) for ships, navigation and marine technologies (areas of standardisation covered by ISO/TC 8), or
3) related to international data exchange such as standards developed, published and maintained by
UN/CEFACT, GS1, WCO which are referenced as appropriate in this document.
2 Normative references
The following documents are referred to in the text in such a way that some or all of their content
constitutes requirements of this document. For dated references, only the edition cited applies. For
undated references, the latest edition of the referenced document (including any amendments) applies.
1)
UN/CEFACT Multi Modal High-Level Business Requirements Specification (BRS)
3 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
ISO and IEC maintain terminological databases for use in standardization at the following addresses:
— ISO Online browsing platform: available at https:// www .iso .org/ obp
— IEC Electropedia: available at http:// www .electropedia .org/
1) This high-level BRS describes the requirements for a generic reference data model supporting the trade
and transport-related processes involved in the cross-border supply chain and covering, at a high-level, the
involved business areas, the main parties and the information involved. It provides the framework for any cross-
border transport-related business and government domains to specify their own specific information exchange
requirements whilst complying with the overall processes and data structures. Reference: https:// www .unece .org/
fileadmin/ DAM/ cefact/ brs/ BRS _T _L -MMT .zip.
© ISO 2020 – All rights reserved 1
---------------------- Page: 6 ----------------------
ISO 23354:2020(E)
3.1
logistics information service system
LISS
trusted third party that provides the services of a platform for the electronic exchange of logistics
information in the supply chain for increased efficiency and effectiveness
3.2
single window
SW
facility that allows parties involved in trade and transport to lodge standardized information and
documents with a single-entry point to fulfil all import, export, and transit-related regulatory
requirements
Note 1 to entry: If information is electronic, then individual data elements should only be submitted once.
Note 2 to entry: See UN/CEFACT Recommendation 33 (currently under revision).
3.3
single submission portal
SSP
portal that allows traders to submit all of the information related to a specific activity to a single
electronic platform, which then redistributes the information to all participants within that portal
Note 1 to entry: A single submission portal differs from a single window (3.2) in that it can or cannot handle
regulatory procedures and it can or cannot be the only portal within a market.
4 Abbreviated terms
API application programming interface
B2B business to business
B2G business to government
CCS cargo community system
G2B government to business
LSP logistics service platform
MEP message exchange pattern
MMT RDM multi-modal transport reference data model
MSME micro, small and medium enterprise
OGA other government agency
PCS port community system
PPP public-private partnership
SCRDM supply chain reference data model
5 Business requirements overview
Based on the use cases and gap analysis in Annex A, the three business requirements include:
1) logistics information service system network architecture requirements;
2 © ISO 2020 – All rights reserved
---------------------- Page: 7 ----------------------
ISO 23354:2020(E)
2) visibility data interchange requirements between LISSs;
3) visibility data interface and process requirements for an LISS network.
The major related business requirements for each use case and gap analysis are summarized in Table 1.
Table 1 — Major related business requirements for each use case and gap analysis
Sub- Business requirements
Use cases Issues and gaps Gap analysis
clause
1) 2) 3)
A.1 Data connection The logistics informa- Global logistics infor- Y
between non- tion is disseminated and mation networks should
harmonised fragmented in the logistics be established to pro-
partners chain, including both logis- vide one-stop logistics
tics status information and information service.
administrative data. The reasons for the
fragmentation need to
be investigated as they
are often commercial or
international contractu-
al reasons which tech-
nical solutions cannot
solve alone.
A.2 Basic logistics data It is difficult to form closed It is vital to harmo- Y
with non-harmo- loop data link because of nize the differences
nised technical non-harmonised technical of industry-level and
and data format and data format standards. country-level standards
standards by providing solutions to
achieve mutual recog-
nition. The differences
in terminology and data
rules set by the interna-
tional contractual con-
ventions in the different
modes of transport are
a barrier which needs to
be addressed.
A.3 Same logistics For the same data query Uniform user manage- Y
data query with from user side, the re- ment and authorization
different return quired parameters and should be standardized
information from return information of LISSs for LISSs recognising the
different LISSs are not in a simply and importance of harness-
uniform way. ing international data
standards.
A.4 Public or private No clear rules and steps Public/private authori- Y Y
data connection for public or private data zation and management
connection. should be standardized
to set up a trust and con-
trolled LISS network.
1) Logistics information service system network architecture requirements
LISS networks should be multi-party connected logistics networks including national and regional
LISS operators, national, regional single window/SSP operators, data providers and trade and
data users.
Data connections should be established between national and regional LISSs to realize visibility of
logistics flow geographic regions and multi-modal transport modes such as maritime, air, rail, road,
inland water, etc. National and regional single window/SSP operators can connect to corresponding
national and/or regional LISSs for data connections to an LISS directly and to other LISSs indirectly.
© ISO 2020 – All rights reserved 3
---------------------- Page: 8 ----------------------
ISO 23354:2020(E)
Data providers can share/obtain data to/from connected LISS directly and to/from other LISSs
indirectly. Data users can obtain data from multi-LISSs directly or indirectly.
The detailed network architecture requirements are specified in Clause 6.
2) Visibility data interchange requirements between LISSs
Data interchange should be neutral, trusted and controlled. Event data should be classified with
regard to commercial and other data security considerations; and data security access levels
should be specified for different entities linked to an LISS network in order to assure data owners
that their data will at all times only be made available to parties they trust, that they themselves
determine which data will be shown, and how, and that they can block access to this data at any
time. Data owners should be able to maintain access control to their individual data ownership at
all times.
The detailed visibility data interchange requirements are specified in Clause 7.
3) Visibility data interface and process requirements for LISS network
Data interface and process should be open and based on unified user management and
authentication. There should be a single way of working that is suitable for all modalities, large and
small organizations, public and private-sector parties, bodies requesting data and those supplying
it, and their software suppliers, so that data can be shared in a simple manner across the whole
sector. As a result, logistics efficiency will be improved; time and costs will be saved.
The detailed visibility data interface and process requirements are specified in Clause 8.
6 Logistics information service system network architecture requirements
6.1 Network architecture requirements overview
An LISS network should be a multi-party connected logistics network including national and regional
LISS operators, national plus regional single window/SSP operators, data providers and data users. The
network architecture of a LISS is shown in Figure 1. In an LISS network, there are three roles:
1) LISS, the third-party logistics data service system, such as a port community system, a cargo
community system etc.
2) Data providers, who provide the data to an LISS, such as port and sea data providers.
3) Data users, who access logistics data from LISS network, such as buyers, sellers and logistics
agencies.
An LISS has its own data providers and data users, and the logistics data can be interchanged within the
LISS area. Data connection can be established among LISSs. Furthermore, LISS can connect to national
and regional single window/SSP to exchange government data. Single window/SSP has the major role of
providing government data to LISS, such as custom clearance data. Therefore, data can be interchanged
between LISS area to form a multi-party connected logistics network.
4 © ISO 2020 – All rights reserved
---------------------- Page: 9 ----------------------
ISO 23354:2020(E)
Figure 1 — Network architecture of a logistics information service system (LISS)
6.2 LISS network entities
6.2.1 Logistics information service system (LISS)
Most logistics information service systems (LISS) serve the entire logistics chain: maritime transport,
land transport, warehousing to support international trade eBusiness and internet platform-based
e-commerce sales transactions. Some LISSs also support administrative functions and provide
information services relating to international trade regulations.
Data providers and data users can interact or exchange data with an LISS. Data can be interchanged
between data providers and LISS. Besides, users can obtain specific data from LISS by exchanging
messages between users and LISS.
Sometimes, users require data exchange from multiple LISSs. This can be enabled via a data
communications connection (such as an APIs) between users and other LISSs. Similarly, data sharing
among LISSs can be enabled, as well as B2G and G2B data interchanges between an LISS and a SW.
Therefore, national or regional LISSs could enable data exchange among LISSs and SWs to establish a
global logistics network.
The types of LISS include:
— Port community system (PCS)
A port community system is a neutral and open electronic platform enabling intelligent and
secure exchange of information between public and private stakeholders in order to improve the
competitive position of the sea and airports’ communities (sometimes referred to as port user
groups).
© ISO 2020 – All rights reserved 5
---------------------- Page: 10 ----------------------
ISO 23354:2020(E)
— Cargo community system (CCS)
A cargo community system is an information technology platform linked to the freight flows
(import/export/transit) of any kind of cargo passing through identified port, airport, or multi-
modal site(s) at a local or national level. A CCS is open to all parties involved in cargo freight and
logistics including customs administrations. It handles a database in which information is collected,
processed, stored and exchanged aiming to enhance freight optimization, trade safety and security,
cargo tracking and tracing, and the facilitation of customs and administrative procedures.
— Logistics service platform (LSP)
A logistics service platform is an information technology platform that optimizes the logistics
network to be more efficient and convenient. An LSP can provide smart logistics data analysis
and visibility data track and trace, especially provide logistics service to micro, small and medium
enterprises (MSMEs) by cooperation with logistics and transport companies.
6.2.2 Single window
Single window (SW) allows parties involved in trade and transport to lodge standardised information
and documents. In this document, single windows have the major role of providing government data to
LISS such as custom clearance data.
B2G and G2B data interchange can be enabled via the connection (such as APIs) between LISS and SW. It
is an entry for national or regional LISSs interchange data outside.
6.2.3 Data providers
Data providers are the logistics data providers such as ports, airline and transport companies, who are
authorized to provide the logistics data to LISS.
6.2.4 Data users
Data users are the logistics parties that are authorized to access logistics data from LISS network, such
as buyers, sellers and logistics agencies involved in international trade. They can obtain the data via the
connection (such as APIs) between LISS and users.
6.3 Network architecture requirement between different LISSs
The data provided by an LISS is national or regional, or limited to one transport method such as port
data or air data. The data interchange between different national/regional LISSs should be established
to provide the data service about visibility of logistics flow among multi-regions and multi-modal
transport methods such as maritime, air, train, inland, etc.
6.4 Network architecture requirement between LISS and SW/SSP
Single window/SSP operators can share/obtain data to/from connected LISS directly and to/from other
LISSs indirectly.
6.5 Network architecture requirement between LISS and data providers
Data providers can share/obtain data to/from connected LISS directly and to/from other LISSs
indirectly.
6.6 Network architecture requirement between LISS and data users from other LISSs
Data users can obtain data from multi-LISSs directly or indirectly.
6 © ISO 2020 – All rights reserved
---------------------- Page: 11 ----------------------
ISO 23354:2020(E)
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 B2B, B2G, G2B interchanges and information sharing.
Thus, efforts shall be made to build better pipeline data exchange standards (PDES) i.e. the UN/
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;
4. Train and Cargo events during railway transport;
5. Customs, Quarantine & Inspections and OGA during cargo clearance control processes.
© ISO 2020 – All rights reserved 7
---------------------- Page: 12 ----------------------
ISO 23354:2020(E)
7.2 Data control for different entities in the LISS network
For each data interchange event, a corresponding event data control process will be implemented by
related two entities in the LISS network. Different entities in the LISS network can retrieve different
types of event data based on the data control scheme. This will assure data owners that their data will
at all times only be made available to parties they trust, that they themselves determine which data
will be shown, and how, and that they can block access to this data at any time. Data owners shall be
supported to maintain control at all times. Therefore, the data subset and the information key to access
data should be clearly defined for each data interchange event. Multiple-level data sharing policies and
data authorization mechanism should be used between different stakeholders in the LISS network.
8 Visibility data interface and process requirements for LISS network
8.1 Unified user management and authentication process re
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.