ONE RecordEpisode 2 Episode 3 Episode 4 Episode 5 Episode 6 ONE Record 17 September 14:00 –15:30...
Transcript of ONE RecordEpisode 2 Episode 3 Episode 4 Episode 5 Episode 6 ONE Record 17 September 14:00 –15:30...
ONE Record
17 September 2020
IATA Digital Cargo Webinars
Your hosts today
David SauvManager, Digital Cargo
IATA
Competition law guidelines
Do not discuss:
• Any element of prices, including fares or service charges
• Commissions
• Allocations of customers or markets
• Marketing plans, commercial terms or any other strategic decision
• Group boycotts
• Your relations with agents, airlines, solution providers, or other third parties
• Any other issue aimed at influencing the independent business decisions of competitors
How to participate during the meeting?
• You can only hear the presenters
• Your microphones are disabled
• Use the questions box to interact
• Simply enter your questions in the chat box on the right
The entire recording along with questions will be available shortly after this webinar finishes.
Simply click on the link in the invite for the live event to access it.
The presentations shown today will be available for download on our website:
www.iata.org/one-record
This meeting is recorded for future use
Episode 2: ONE Record
Part 1
Part 2
Part 3
Part 4
Part 5
ONE Record development – What’s new this year?David Sauv, IATA
ONE Record Developer PortalAndra Blaj, IATA
ONE Record in real lifeMalcom Fowler, CCS UK / Pramod Rao, Nexshore
ONE Record behind the scenePhilipp Billion, LH / Shashank Mardikar, LX / Mary Stradling, DGF / Christophe Lambert, IATA
Q&A Session
Part 1
ONE Record development – What’s new this year?
2020 Digital Cargo Webinars
David SauvManager, Digital Cargo,
IATA
The concept
ONE Record concept
The ONE Record concept
is based on 3 pillars
enabling to define:
WHAT, HOW, with WHOM
data can be shared
Data API Security
Data semantics, vocabulary, linked data,
data ownership
Internet of Logistics, Application Programming
Interface (API), HTTP
Trust network, identification, authentication, authorization, token, confidentiality, privacy
VIRTUAL SHIPMENT RECORD
Governance / Roles & Permissions
ONE Recordis a
data-centric modeland NOT a
document-centric model
Provide better visibility and
transparency
Eliminateduplicate
Improvedata quality
CO2Emission
Customs(Advance Cargo
Information)
Shipper’sLetter of
Instruction
CargoDistribution
InteractiveCargo
DangerousGoods / Pharma
Airline Core Ontology
ULDTracking
GroundHandling
ONE Record Data Model: the ambition
CO2Emission
Customs(Advance Cargo
Information)
Shipper’sLetter of
Instruction
CargoDistribution
InteractiveCargo
DangerousGoods / Pharma
Airline Core Ontology
ULDTracking
GroundHandling
ONE Record Data Model: the ambition
Airline Core Ontology
• Minimal requirements for the transport of general cargo
• Detailed and extensive enough to enable piece-level management and tracking
Add-ons
• Sets of data elements required to handle specificities of certain shipments (e.g. Dangerous Goods, Pharmaceutical) and/or operations (e.g. ULD tracking, Interactive Cargo)
Industry benefits
Data qualityand control
Visibility andtransparency
Plug & PlayConnectivity
Future ofdigital cargo
Welcome a newgeneration
• Data shared by data
owner
• Full control of data
• Data stays at the
source
• Owner determines
data access
• Foundation for true
digital air cargo
• Develop
collaborative and
automated digital
services
• Facilitate the direct
connectivity
between all the
stakeholders
• Use of web API
• New cooperative IT
solutions and
innovation
• End-to-end
transportation chain
• Share data of the
shipment with
relevant parties
• Enhanced visibility
and transparency
• Technology platform
that is ready for a
new generation of
digital natives
Standard development: where do we stand?
ONE Record Task Force (ORTF) kicked off in June 2018
16
The Task Force is established under the Cargo Operations and Technology Board (COTB)
Objectives
To provide the air cargo industry with a standard for data sharing
Data model specification
API specification
Security specification
~60 participants from all the areas of the air cargo industry
Freight Forwarder
GSAShipper
Airline Ground Handler Association
IT Provider CCSCustoms
ONE RecordObjectives for 2020Validate the ONE Recordstandard through pilot projectsand speed up its adoption withindustry tools and supportwhile continuously adding dataelements and features to thestandard
Drivepilot projectswith industry stakeholders
Develop a ONE Developer Portal to
host tools and support to
accelerate the standard adoption
Enhancethe ONE Record
standard
ONE Record Standard
https://github.com/IATA-Cargo/ONE-Record
Data model specification: provides the air cargo industry with a standarddata structure for data exchange using JSON-LD that facilitates dataintegration with existing and new data services;
API specification: specifies the interface and interaction of the web API orApplication Programming Interface that allows airlines and their partnersto connect their system directly using best in class web technologies;
Security specification: uses an industrywide and federated trust networkto manage identification and authentication of data sharing systems andensures data privacy and confidentiality for all parties.
ONE Record – Standard development dashboard
Data Model API / Security
Pilot projects
Pilot companies 4911Use cases
▪ IATA published a series of insight articles, white papers and webinars to communicate and educate the industry on the ONE Record standard▪ IATA developed a Multilateral Data Agreement (MDA) to facilitate the pilot implementation▪ IATA launched a ONE Developer Portal with the objective to be a one stop shop for anyone who wants to implement the ONE Record standard
General status Last update: 16 SEP 2020
Airline Core Ontology
Shipper’sLetter of Instruction
CargoDistribution
CO2Emission
e-CMR
Customs(PLACI, ICS2)
GroundHandling
ULDTracking
InteractiveCargo (IoT)
DangerousGoods
Pharmaceutical
E
P
P
A
I
PUB/SUB
LO update
Access delegation
Security
Event
SHACL shapes
IoT updates
Audit trail / Versioning
Access Control
Cascading status update - Pub/Sub in multi-chain
Data integrity / non repudiation with RDF
Rich data
A
A
A
V
A
V
A
A
I
I
E
I
A
E
A
A
E
P
I Ideation A AdoptedE Experimental P Proposed V Verified
• N/A
Red Flag
ONE Record – Standard development dashboard
http://iata.org/one-record
ONE Record InsightsA series of insights into the many topics related to ONE Record, including technical, data, pilot and project subjects
https://www.iata.org/one-record/#tab-2
ONE Record White Papers
ONE Record Data Model
ONE Record API
ONE RecordSecurity
https://www.iata.org/one-record/#tab-2
Don’t miss our series of three white papers coming this summer !
ONE Record Insights
The ONE Record API: an overview of the key featuresTuesday, 14th July 11:00 – 12:30 (CEST)
ONE Record: One step closer to digital cargoTuesday, 23rd June 11:00 – 12:30 (CEST)
The data model: a digital twin of the air cargo industryTuesday, 30th June 11:00 – 12:30 (CEST)
Data security: securing the Internet of LogisticsTuesday, 21st July 11:00 – 12:30 (CEST)
Crafting ontologies: from physical freight to machine readable dataTuesday, 7th July 11:00 – 12:30 (CEST)
Pilot testing: engaging with the cargo communityTuesday, 28th July 11:00 – 12:30 (CEST)
ONE Record Flower
Standard
ONE Record Pilot Projects
31
The objectives of the pilot projects are to verify that the ONE Record standard components are fit for purpose, i.e. they bring the expected value, and to capture the lessons learned as an input for standard improvement. To join our pilot project program, please follow the below steps.
For more information, visit our ONE Record Pilot Project webpage
Enriching commercial documents
ONE Record Airport hub
Cargo pre-advise for trucking
Cargo distribution Customer integration
ONE Record node expansion
ONE Record and Existing Messaging
Standards
ONE Record prototyping
Pharmaceuticals
Existing Uses Cases
Formalize a specific use case
1
Start a pilot project
2
Report Pilot findings to IATA
3
Process
ONE Record for Road Transport
IATA Multilateral Data Agreement (MDA)
32
The IATA Multilateral Data Agreement (MDA) provides a single non-disclosure agreement standard wherebystakeholders sign once with IATA and start exchanging through ONE Record with all other signatory parties tothe Agreement. By signing the Agreement with IATA, stakeholders effectively enter into Data Agreements witheach other, i.e. enabling them to share data through the ONE Record API.
Before starting ONE Record, stakeholders are required to sign theMultilateral Data Agreement (MDA) following the below steps:
Complete and submit the Online Joining Form
1
Receive the Agreement by e-mail from IATA Cargo
2
Review and e-sign the Agreement
3
Receive counter-signed agreement from IATA
4
Process
Provides the necessary legal framework for establishing ONE Record Data exchange
Free of charge
Enables to share data with all stakeholders
Avoids the need to negotiate numerous bilateral Data agreements with stakeholders
Participating companies are listed on the ONE Record website
$
For more information, visit the MDA page
ONE Record Flower
Standard
IATACARGOHACKATHONONE RECORD12-13 SEPTEMBER 2020
Global participation
33 nationalities – 176 participants – 17 teams
13%
2%
27%
13%
45%
1 minute to pitch the initial idea
28 hours of coding
5 minutes of final presentation
8 jury members
HackathonWeekend
Episode 6
Hackathon
2020 Digital Cargo Webinars
Arnaud LambertONE Record Engagement
Manager, IATA
Save the date to discover the
outcome
1 October14h00 – 15h30 CEST
ONE Record Flower
Standard
ONE Record Implementation Playbook
https://www.iata.org/one-record/#tab-2
Provides a step by step guide to implement the ONE Record standard
1. Select a task from the Master Operating Plan (MOP)
_ACT1Activity
Task
https://a71bcec4-d0e1-4b94-80d6-695ec0bd0435.filesusr.com/ugd/722a02_e289dc70805f4bd491a467906f728abc.pdf#page=29Go to MOP document
2. The stakeholder presented below is the one accountable to make the data available. However other parties (not specified here) can be designated to perform this action (e.g. GHA on behalf of the airline)
Stakeholders
3. The below sections presents the Logistic/Common object to be created and a description of what need to be done during this specific tasks
Logistic Object Common Object Action / Comment
YES1 Characteristics YES1 Company
YES2 CustomsInfo YES2 Country
YES3 DangerousGoods YES3 Dimensions
YES4 Item YES4 Event
YES5 PackagingType YES5 ExternalReference
YES6 Piece YES6 Location
YES7 Product YES7 OtherIdentifier
YES8 ReasonsForSecurityStatus YES8 Person
YES9 ReceivedFrom YES9 Value
YES10 SecurityStatus YES10 VolumetricWeight
YES11 ServiceRequest YES11
YES12 TransportSegment YES12
YES13 ULD YES13
YES14 YES14
YES15 YES15
YES16 YES16
YES17 YES17
YES18 YES18
YES19 YES19
YES20 YES20
YES21 YES21
YES22 YES22
YES23 YES23
YES24 YES24
YES25 YES25
YES26 YES26
YES27 YES27
YES28 YES28
YES29 YES29
The booking is made between the shipper and the forwarder, at this stage this booking is not in the scope of the data model.
The shipper ensures that the following LO are created or updated for the shipment: Product, Item, Piece, Dangerous Goods, Transport
Segment (Origin and Destination, reference to the pieces), ULD if relevant (creating/updating if he is the owner, linking to existing ULD
object otherwise), Security Status, Customs information, Service Request
In this list the following are optional objects that are not mandatory at this stage: Item, ULD, Security Status, Customs information
If there is no Item, the Product is directly linked to the Piece
1 Book & plan shipments
1.1 Receive booking from shippers'request & check security status
Click here to see the complete description
Shipper
ONE Record - Data Model and MOP mapping
Object name Piece
Object type Logistic Object
Data type: (O - Object, E - Embedded object, N - Numeric, D -DateTime, T - Text)
Attribute DescriptionOptional or
MandatoryCardinality
Data TypeLinked object
additionalSecurityInfo Ad hoc security statement required by state regulators 0 n T
coload Coload indicator for the pieces (boolean) 0 0 B
containedPiece Details of contained piece(s) n E Piece
customsInfo Customs details 0 n E CustomsInfo
dimensions Dimensions details E Dimensions
event Event details e.g. DEP, ARR, FOH, RCS, security screening, customs status, etc. 0 n E Event
externalReference Reference documents details n E ExternalReference
goodsDescription General goods description M T
grossWeight Weight details M E Value
Back to "MOP vs Data Model" screen
ONE Record - Data Model and MOP mapping
ONE Record MOP Mapper
https://www.iata.org/one-record/#tab-6
Making the link between the Industry MOP and the ONE Record Data Model
ONE Record Developer Portal
http://www.onerecordcargo.org/
One stop shop for anyone who wants to implement the ONE Record standard
Part 2
ONE RecordDeveloper Portal
2020 Digital Cargo Webinars
Andra BlajDeveloper
ONE Record, IATA
Part 3
ONE Record in real life
2020 Digital Cargo Webinars
Malcom FowlerConsultant,
CCS-UK User Group
Pramod RaoCEO,
Nexshore Technologies
A short introduction to CCS-UK
• Cargo Community Service operated since 1994 for Air
• Provides interfaces to Chief for Customs Clearance, ASN (Anti-smuggling net) and Lucas
• Provides electronic inventory management for Imports and reporting for Exports
• Airline/Community Messaging
• Best known for interconnecting Forwarders, Transit sheds and Airlines to HMRC/BF for
air cargo
• Manages over 1000 Forwarders, Transit sheds and Airlines
• Operates across almost all the UK airports
• Provides functionality for inter-shed and inter-airport removals
• Reconciles movements across UK airports thus avoiding the need to use NCTS
• Considerable number of maritime export declarations made through CCS-UK
2020 The CCS-UK Cargo Community User Group Limited 44
A short introduction to Nexshore
2020 The CCS-UK Cargo Community User Group Limited 45
Industry Recognition
Winner of The Red Herring Global 100
Technology Companies award (2010)
Winner of TiE50 Finalist (2011) and
‘The Bizz’ award for Business
Excellence (2011)
Overview
Nexshore is aligned around a single focused objective: Enhancing the business value of Clients. As experts in modern technology we bring valuable Consulting, Development and Implementation of our award-winning Products and Services aligned to industry standard processes.
PartnershipsIBM PartnerWorld, Global
Entrepreneurship Program
(GEP) and Independent
Software Vendor (ISV).
Independent Software
Vendor, powered by
Azure
CCS-UK – Getting started with One Record
2020 The CCS-UK Cargo Community User Group Limited 46
• The initial ideas for the One Record Pilot were developed by a small team from Heathrow Airport, CCS-UK,IAG,VS,CX & dnata
• The IATA team provided more detailed information to help inform the Pilot participants and explain the small print
• Ideas for the Pilot were discussed, modified agreed with the wider project team from across the UK community. The project was registered with IATA
ONE Record Airport hub (Project registered with IATA)
• Implementation of the IATA One Record specification based on Github documentation.• Master airwaybill data from two Forwarders being moved through a One Record hub to two Airlines and one Ground Handler• Initially the trade lane LHR-HKG & HKG-LHR.• Pilot may include status messages to/from CX• The pilot server will be built to accommodate additional business scenarios that will be discussed during 2020.
Pilot Description
Pilot Participants
System build timelines
Ground work Apr 20
Register Company/User
Apr 20
Create LOApr 20
AuthenticationApr 20
Update to v1.2Jun 20
TrialsJuly 20
CCS-UK – Moving into development
2020 The CCS-UK Cargo Community User Group Limited 48
• The business requirements where developed and agreed with the group and Nexshore Inc approached to build the system.
• We initiated two-weekly video progress meetings with a wide industry team which included a sub-set of active partcipants• Allport, Geodis, Cathay, IAG Cargo, VS, GLS Hong
Kong, Wisetech Global,HAL, ABS, BT, dnata, Swissport, AFSS
• Active in Pilot project: CCS-UK / Nexshore / Wisetech / Geodis / GLS Hong Kong / Cathay Pacific
• Once business requirements were frozen, Nexshore
set about developing the ONE Record server in
“Node” format – provided by IATA in their
architecture.
• A Node is a completely isolated account secured by
its own ONE Record ID on an application server,
asynchronously tethered with API and Database
servers. All web facing components are secured with
TLS and handshakes must be established between
certified servers before any data can be exchanged.
• Nexshore chose to implement the architecture on
the Microsoft Azure Cloud on servers located in the
UK south data centers.
ONE Record servers build out and accounts management
18/09/2020 (c) 2017 The CCS-UK Cargo Community User Group Limited - Commercial in confidence 49
ONE Record servers and data flow
18/09/2020 (c) 2017 The CCS-UK Cargo Community User Group Limited - Commercial in confidence 50
AirWaybill Object
Shipment Status Update
• Pub/Sub, Data Delegation and Server TLS handshake
was implemented and tested between
• CCS-UK ONE Record Nodes for GEODIS and dnata (data
delegated by Cathay Pacific on AWB)
• GLSHK’s ONE Record Server for Cathay Pacific.
• Waybill objects were exchanged and immediate
Shipment status updates were received.
• The test was conducted with interrupts so the
audience was able to follow along.
2020 The CCS-UK Cargo Community User Group Limited 51
CCS-UK One Record Server by Nexshore
1. Geodis/Wisetechcreates a FWB object in the CCS-UK 1RS server
and provides a hard copy of the same.
4. GLS retrieves the airwaybill LO via their CCS-
UK account into the CX server in Hong Kong, prints out a hard copy and sends a
scanned copy
3. Send PDF 5. Send PDF
6. Compare the data integrity with
visual checks. Share results with
the group
2. FWB Check
email email
7. Publish results
CCS-UK – Success criteria published
CCS-UK – Build and deliver
2020 The CCS-UK Cargo Community User Group Limited 52
• Bi-lateral meetings between technical stakeholders take place to keep project on track (Nexshore/Wisetech & GLS).
• Actively engage with IATA to keep up with specification changes
• Nexshore have time to add some additional features (Status messages & SMS alerts)
• Pilot tests rehearsed by small group• A larger group witness an end to end
demonstration and sign off a successful pilot (Phase 1)
• All agree to start on Phase 2 in September after the Hackathon
CCS-UK – The user interface
2020 The CCS-UK Cargo Community User Group Limited 53
User interface developed to review the data in the system, to provide an historical repository and to view the logistics objects
CCS-UK – What did we learn?
2020 The CCS-UK Cargo Community User Group Limited 54
• One Record is largely a technical implementation with little or no visible interface
• A stable 1R version is essential• Some perception that this is just a new
specification for exchanging the same old data• New ideas on how to exploit 1R need to be
developed• The internet is a safe, secure and cost effective
platform for the exchange of air cargo data• Data exchange over email, which is fraught with
issues, could easily be replaced with secure 1R servers
Feedback
2020 The CCS-UK Cargo Community User Group Limited 55
Nexshore were an ideal partner, they delivered a project plan, stuck to it and were extremely good at liaising with all the parties. Nothing was too much trouble for them. Regarding the technology, it is clearly the way forward. Seems to be very effective and easy to use and should improve the flows of data between the supply chain partners, the industry should embrace it and IATA need to mandate it in order that the participants adopt it quickly. The pilot showed us that centralised One Record servers were the way forward.
Guy Thompson - CCS-UK Programme Manager
I’d like to thanks all the involved parties and the technical teams who worked hard to make this 1R pilot a reality for us and a strong basis for future decisions. It was a pleasure to participate to that collaborative project perfectly driven, and I look forward to see how this technology is going to move forward within the Air freight industry!
Eloïse PONTHUS - Business Process Management & Applications – Airfreight GEODIS
Part 4
ONE Record behind the scene
2020 Digital Cargo Webinars
Christophe LambertProject Manager
Digital Cargo, IATA
Dr. Philipp BillionSenior Manager efreight,
Lufthansa Cargo
Shashank MardikarSenior Manager,
Swiss WorldCargo
Mary StradlingGlobal Airfreight Ops Manager,
DHL Global Forwarding
Christophe LambertProject Manager
Digital Cargo, IATA
Moderated by
Part 5
Q&A Session
ONE RecordInsights
NEXT EPISODES
Episode 2
Episode 3
Episode 4
Episode 5
Episode 6
ONE Record17 September 14:00 – 15:30 (CEST)
Digital Connectivity22 September 14:00 – 15:30 (CEST)
Interactive Cargo24 September 14:00 – 15:30 (CEST)
Customs/Mail29 September 14:00 – 15:30 (CEST)
Hackathon1 October 14:00 – 15:30 (CEST)