Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Development of electronic data exchange structures for the transport and logistics sector suitable for exchanging via mobile communication technologies

other

Linktoparent

Project Details

Page properties
Domain

Linktoparent

Project Identifier
Text Field
defaultexample: P1021
idpid
requiredtrue
P1063
Bureau Decision #
Text Field
defaultexample: P1021
idBureauDecision
requiredtrue
#00000
Project Proposal Status

SP Page Status
dateJan 22, 2018 14:32
hidetrue
width25%
userMalik
statusdraft

Project Page

TBD

Supporting VC

TBD

Project Lead

TBDProposed: Dr. Youngkon Lee

HoD Support
Text Field
defaultexample: EU / US / UN
idHodSupport
requiredtrue
TBDAT / TBDKR / TBDJP
Status
Select2
defaultSelect the status for this project
idproject_status
requiredtrue
selectedInitiated
  • Initiated
  • In development
  • Completed
Version
Text Field
defaultClick to set the version number
idversion_number
requiredtrue
1.0
Submitted date
Date Picker
defaultClick to set the submissions date
idsubmitted_date
requiredtrue
20182016-0105-2204
Draft Development Completion
Date Picker
defaultDraft Development date
idDraft
2018-1108-19
Publication Date
Date Picker
defaultExit date
idExit
2019-0111-19

Project Purpose

Text Area
default<click here to edit>
idproject_purpose
The purpose of this project is the specification of the business requirements and essential data items suitable to be transferred using mobile technologies during the delivery of transport services. A transport services provider (carrier or freight forwarder) when contracted by a transport services buyer (consigner or consignee) is committed to deliver the contracted consignment to a designated consignee via any named contractual locations. In reality, as a result of the diversified nature of the modern intermodal, synchromodal and multimodal transport infrastructures, the actual routes deployed often vary from the contractual arrangements. The reasons for these deviations are very varied but most often result from operational considerations. However, changes in itineraries during transport movements can also be pointers to security and other risks of interest to cross-border agencies. In both cases, the tracking of the trade items is made more difficult with every operational route change and all the parties concerned are needing new methods by which they can be informed of all such changes in safer, more precise and prompt ways. 
Modern communication methods such as those based on mobile technologies can assist in providing real-time information to keep all interested parties up to date along the transport chain. However, these new communications methods are not suitable for exchanging large-scale amounts of data and therefore the key data requirements need to be identified to support short, sharp efficient data deliveries at regular intervals.
This project will base its work on the Multi Modal Transport (MMT) reference model and will analyse the required subset business process scenario and identify the relevant data items and structures needed for supporting real-time mobile technologies. 

Project Scope

Text Area
default<click here to edit>
idproject_scope
The updatescope toof Recommendationthis 16project willis addresslimited the following questions that have emerged in recent years:
1.	What is the precise definition of a location? Is it a point or an area? Which entities should be allocated a UN/LOCODE? 
2.	What are good, unambiguous definitions for the existing Function Codes: 1, 2, 3, 4, 5, 6, 7, B? Should new function codes be added? 
3.	What is the process to handle locations which have multiple names – either from different languages or otherwise?
4.	How should political change when locations change hands or new countries emerge be handled?
5.	Should there be changes to the Status of location codes? For instance, do we need a better process and definition for “Request under consideration” given that there is currently no workflow to move these from “under consideration” to “approved”?
6.	What is the policy around changing or removing codes which had been previously published and are already in use? When a code has been deprecated, is it acceptable to reassign the code to another location?
7.	Is there a need to limit the number of requests made for new codes or changes to existing codes from a single entity for a given cycle?
8.	Should precision of coordinates be improved from minutes to seconds?
9.	Should new attributes be added, for example, time zone?

In addition to answering the above questions, comments will be solicited from participating experts from standards bodies, logistics providers and industry in order to address challenges they have with the use and maintenance of the UN/LOCODE standard.

Project Deliverables

Text Area
default<click here to edit>
idproject_deliverables
The project deliverables are: 
a)	Revised Recommendation 16 Recommendation & Guidelines
to: 
-	specifying real time and geographical data items to be useful to exchange in order to increase transparency, reliability and completeness during the transport movements of consignments;
-	developing BRS based on the MMT high-level BRS;
-	developing an RSM to help users apply the identified data items in standardised message structures.
-	Develop a guideline for implementing the scenario defined in the BRS and RSM deliverables

Project Deliverables

Text Area
default<click here to edit>
idproject_deliverables
The project deliverables are:
•	Business Requirements Specification (BRS) as defined during the business requirements gathering
•	Requirements Message Specifications (RSM)
•	UN/EDIFACT messages (to be defined or updated)
•	XML schema of the required messages
•	Guideline - Guideline document.

Exit Criteria

Text Area
default<click here to edit>
idexit_criteria
The exit criteria will be:
•	Business Requirements Specification (BRS) as defined during the business requirements gathering
o	External Review Log showing all comments have been addressed
•	Requirements Message Specifications (RSM)
o	External Review Log showing all comments have been addressed
•	XML schema of the required messages
o	External Review Log showing all comments have been addressed
•	Guideline document
o	External Review Log showing all

Exit Criteria

Text Area
default<click here to edit>
idexit_criteria
a)	Revised Recommendation 16 Recommendation & Guidelines
•	Internal and external review logs showing how comments have been addressed 
•	Final draft text ready for publication

Project Team Membership and Required Functional Expertise

Text Area
default<click here to edit>
idproject_membership
MembershipThe project team is open to experts with broad knowledge and experience in the area of transport, clearance, supply chain and relatedlogistics and related mobile communication messaging activities as well as in recommendationmodelling draftingtechniques. In addition, Heads of Delegations may invite technical experts from their constituency to participate in the work. Experts are expected to contribute to the work based solely on their expertise and to comply with the UN/CEFACT Code of Conduct and Ethics and the policy on Intellectual Property Rights.

Geographical Focus

Text Area
default<click here to edit>
idgeographical_focus
The geographical focus of the project is global.

Initial Contributions

Text Area
default<click here to edit>
idinitial_contributions
•	UNECE Recommendation 16The following contributions are submitted as part of this proposal. It is understood that these contributions are only for consideration by the Project Team and that other participants may submit additional contributions in order to ensure that as much information as possible is obtained from those with expertise and a material interest in the project. It is also understood that the Project Team may choose to adopt one or more of these contributions “as is”.
•	T&L's Multi-Modal Transport Reference Data Model (project p1023)
•	BRS IFTM International Forwarding and Transport
•	UN/CEFACT Modelling Methodology (CEFACT/TMG/N093)
•	UN/LOCODE Advisory Group Terms of Reference
•	UN/LOCODE Focal Point Terms of ReferenceCEFACT ebXML Core Components Technical Specification Version 2.01
•	Artefacts from the South Korea Electronic Bill of Delivery for Logistics (eBOD) project  

Resource Requirements

Text Area
default<click here to edit>
idresource_requirements
Participants in the project shall provide resources for their own participation. The existence and functioning of the project shall not require any additional resources from the UNECE secretariat. The project will be prepared in between Forums, principally using conference call facilities.

Project Leadership

Text Area
default<click here to edit>
idproject_leadership
Project Leader: 	Alper KEÇELİ 
Lead Editor:		TBD

Project Proposal Files

Attachments
oldfalse