Versions Compared

Key

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

Revision of Recommendation 16

other

Linktoparent

Project Details

Page properties
Domain
Project Identifier
Text Field
defaultexample: P1021
idpid
requiredtrue
P1061P1062
Bureau Decision #
Text Field
defaultexample: P1021
idBureauDecision
requiredtrue
#00000#1802054
Project Proposal Status

SP Page Status
dateJan 22Apr 12, 2018 1416:3221
hidetrue
width25%
userMalik
statusdraftofficial

Project Page

TBDRevision of Recommendation 16

Supporting VC
Project Lead
HoD Support
Text Field
defaultexample: EU / US / UN
idHodSupport
requiredtrue
TBDFI / TBDTR / TBDMY
Status
Select2
defaultSelect the status for this project
idproject_status
requiredtrue
selectedInitiatedCompleted
  • 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
2018-01-22
Draft Development Completion
Date Picker
defaultDraft Development date
idDraft
2018-11-19
Publication Date
Date Picker
defaultExit date
idExit
2019-01-19

Project Purpose

Text Area
default<click here to edit>
idproject_purpose
The UN/LOCODE has emerged as the prominent international standard for referring to locations used in international trade. The UN/LOCODE is used by carriers, logistics providers, multinational corporations and software providers as the standard way to refer to cities, ports, airports, etc. Given the adoption of the UN/LOCODE, changes to the standard can have major impact on industry.

The rules governing the maintenance of the UN/LOCODE (Recommendation 16) are based on the business scenario of several decades ago. However, the use and importance of the UN/LOCODE has grown tremendously since Recommendation 16 was last updated in 1998.

The purpose of this project is to update Recommendation 16 in order to allow it to continue to govern the modern usage of the UN/LOCODE. Emerging industry requirements are leading to inconsistencies in the application of the codes. An update to Recommendation 16 will add more specificity to definitions and process, leading to less ambiguity and more consistency in the application of the codes. It will ensure that the UN/LOCODE remains an important international standard which keeps pace with the changes in usage and in technology.

Project Scope

Text Area
default<click here to edit>
idproject_scope
The update to Recommendation 16 will address 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)	UpdatedRevised UN/EDIFACTRecommendation guides16 forRecommendation the FAL messages
b)	Equivalent CCBDA message structures derived from the MMT-RDM
c)	XML schema based on the CCBDA message structures
& Guidelines

Exit Criteria

Text Area
default<click here to edit>
idexit_criteria
a)	UpdatedRevised UN/EDIFACTRecommendation guides16 forRecommendation the& FAL messagesGuidelinesFinalInternal draftand readyexternal for publication
b)	Equivalent CCBDA message structures derived from the MMT-RDMreview logs showing how comments have been addressed 
•	Final draft ready for publication
c)	XML schema based on the CCBDA message structures
•	Final draft text ready for publication

Project Team Membership and Required Functional Expertise

Text Area
default<click here to edit>
idproject_membership
Membership is open to experts with broad knowledge and experience in the area of maritimetransport, transportclearance, regulatorysupply procedureschain and the IMO FAL Compendium related activities as well as in recommendation drafting. 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
IMOUNECE FAL Convention, 1965Recommendation 16IMO FAL Compendium, 2013
•	UN CCLUN/LOCODE Advisory Group Terms of Reference
•	UN/CEFACT MMT-RDM
•	UN/CEFACT messages (UN/EDIFACT)LOCODE Focal Point Terms of Reference

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: 	TBD
Lead Editor:		TBD

Project Proposal Files

Attachments
oldfalse