Versions Compared

Key

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

Pipeline Data Carrier

other

Linktoparent

Project Details

Page properties
Domain
Project Identifier
Text Field
defaultexample: P1021
idpid
requiredtrue
P1045
Bureau Decision #
Text Field
defaultexample: P1021
idBureauDecision
requiredtrue
#1609028
Project Proposal Status

SP Page Status
dateMar 09, 2018 12:14
hidetrue
width25%
userMalik
statusofficial

Project Page

Pipeline Data Carrier

Supporting VC
Project Lead
HoD Support
Text Field
defaultexample: EU / US / UN
idHodSupport
requiredtrue
SN / ES / UK
Status
Select2
defaultSelect the status for this project
idproject_status
requiredtrue
selectedCompleted
  • 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
2016-08-28
Draft Development Completion
Date Picker
defaultDraft Development date
idDraft
2019-04-01
Publication Date
Date Picker
defaultExit date
idExit
2019-09-01

Project Purpose

Text Area
default<click here to edit>
idproject_purpose
Easing modern trade flow requires improvements in the entire supply chain, including commercial and border management. Key to managing these new demands and making optimum choices is to capture and use the right data at the right time from the right source. In this aim, a number of pilot projects have developed an end to end data carrier that describes the data to be sent to regulatory authorities through a “seamless integrated transaction.” This process has necessitated a major rationalisation of current business requirements and approaches in order to ensure capturing the accurate data at its source. 

In today’s business processes in global supply chains, information about transactions resides in fragmented business and government systems. As a result, the flow of goods is accompanied by information streams of poor quality. The lack of reliable, accurate and complete data makes it hard to achieve supply chain visibility. This, in turn, makes decision making, risk detection, efficient risk management, supply chain optimization by companies and supervision by border inspection agencies very difficult.

Connectivity infrastructures for information sharing such as data pipelines enable better quality of data, supply chain visibility and information sharing. They open new possibilities for system-based audit and the development of smart software applications to offer value added services to business such as automated planning and scheduling and for border agencies such as automated monitoring and targeting.

In such a pipeline approach, the quantity of data in the pipeline therefore grows as the goods move from seller and shipper to consignee and buyer.  These pipelines will need to have a sequence of generic milestones but these will be individually constructed based on customer needs; so each one may be different.

Project Scope

Text Area
default<click here to edit>
idproject_scope
This project will aim to define the pipeline concept (its purpose, usage, implementation…), provide guidance on defining these generic milestones (which could also be called waypoints), identify the generic actors involved in such pipelines, standardize and harmonize a pipeline data carrier which would cover all data requirements for such procedures. This project is proposed as being based on the Multi Modal Transport Reference Data Model.

Project Deliverables

Text Area
default<click here to edit>
idproject_deliverables
The project deliverables are:
A.	A White Paper on the pipeline concept
B.	A BRS for the Pipeline Data Carrier 
C.	CCBDA RSM for the Pipeline Data Carrier based on MMT
D.	An XML schema of the Pipeline Data Carrier Message

Exit Criteria

Text Area
default<click here to edit>
idexit_criteria
The exit criteria will be:
•	A White Paper on the pipeline concept
      o	External review disposition log
      o	Final draft ready for publication
•	Subset BRS for the Pipeline Data Carrier based on MMT
      o	External review disposition log
      o	Final draft ready for publication
•	CCBDA RSM for the Pipeline Data Carrier based on MMT
      o	External review disposition log
      o	Final draft ready for publication
•	An XML schema of the Pipeline Data Carrier Message
      o	Incorporation into the Core Component Library, if required
      o	Final deliverable ready for publication by Library Maintenance

Project Team Membership and Required Functional Expertise

Text Area
default<click here to edit>
idproject_membership
The project team is open to experts with broad knowledge and experience in the area of supply chain and related activities as well as in modelling techniques. 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.

Geographical Focus

Text Area
default<click here to edit>
idgeographical_focus
Global

Initial Contributions

Text Area
default<click here to edit>
idinitial_contributions
Initial contributions will be sourced from existing documentation and standards including: 
•	EU CORE Project, http://www.coreproject.eu/ (weblink as of July 30th 2016)
•	EU Cassandra Project, http://www.cassandra-project.eu/ (weblink as of July 30th 2016) 
•	T&L's Multi-Modal Transport Reference Data Model (project p1023)
•	There are no known IPR issues and there are no planned formal collaborations.

Resource Requirements

Text Area
default<click here to edit>
idresource_requirements
Required resources include project management and modelling expertise.
Restrict Content
usersMalik

Milestones


DELIVERABLE NAME

Project

Inception

Expected Completion Date

Requirements

Gathering

Expected Completion Date

Draft

Development

Expected Completion Date

Public

Review

Expected Completion Date

Project

Exit

Expected Completion Date

Publication

Expected Completion Date

Maintenance

Expected Completion Date

Text Field
default<click here to edit>
iddeliverable_name1
White Paper, BRS, RSM, schema
Select2
defaultSELECT
idyesno_odp1
selectedYES
  • YES
  • NO
Date Picker
defaultNO DATE SELECTED
idexpdate_odp1
 
Select2
defaultSELECT
idyesno_odp2
selectedYES
  • YES
  • NO
 
Date Picker
defaultNO DATE SELECTED
idexpdate_odp2
Select2
defaultSELECT
idyesno_odp3
selectedYES
  • YES
  • NO
Date Picker
defaultNO DATE SELECTED
idexpdate_odp3
 
Select2
defaultSELECT
idyesno_odp4
selectedYES
  • YES
  • NO
 
Date Picker
defaultNO DATE SELECTED
idexpdate_odp4
Select2
defaultSELECT
idyesno_odp5
selectedYES
  • YES
  • NO
 
Date Picker
defaultNO DATE SELECTED
idexpdate_odp5
Select2
defaultSELECT
idyesno_odp6
selectedYES
  • YES
  • NO
Date Picker
defaultNO DATE SELECTED
idexpdate_odp6
 
Select2
defaultSELECT
idyesno_odp7
selectedYES
  • YES
  • NO
 
Date Picker
defaultNO DATE SELECTED
idexpdate_odp7

Project Proposal Files

Attachments
oldfalse