Project Proposal: Extension of Cross Industry Invoice technical artefacts

other

Submitted dateLast Update DateVersionApproval StatusProject Page
 
 
 
 

 

 

Project Purpose

In the interest of anticipating and following technological trends, UN/CEFACT is extending from a document-centric to a process-driven approach for electronic business message development.
The UN/CEFACT Supply Chain Reference Data Model (SCRDM) is a standardized and harmonized semantic framework fully compliant with the UN/CEFACT Core Component Library. The SCRDM focusses on interoperability, re-use of supply chain core components (globally standardised semantics), and will speed-up and ease implementation. It builds the foundation for deriving syntax-neutral CCBDA compliant semantic business document models.
A proof-of-concept  project about the type of artefacts for this project has been completed April 12, 2016. This project proposal will target the Cross Industry Invoice (CII) as a next step. 
The purpose of this project is to develop the technical artefacts needed in order to allow users to implement the CII based on the SCRDM and Core Component Business Document Assembly (CCBDA).

Project Scope

This project will complement the existing CII artefacts, basing on the SCRDM and incorporating the findings of the CII Proof-of-Concept (PoC) thereby producing a process-driven XML schema. 
It should be noted that the new process-driven CII XML schema is intended to replace the published (document-centric) CII XML schema. 
In order to provide support and guidance for existing users of the current document-centric CII, this project will develop a publication transition plan which will define the timetable for the replacement. 
Through the transition period, business requirements consistency will be ensured as both schemas will be based on the same updated BRS.

Project Deliverables

 

Exit Criteria

 

Project Team Membership and Required Functional Expertise

 

Head of Delegation Support

 

Geographical Focus

 

Initial Contributions

 

Resource Requirements

 

Project Leadership

 

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

 
  • YES
  • NO
 
  • YES
  • NO
 
  • YES
  • NO
 
  • YES
  • NO
 
  • YES
  • NO
 
  • YES
  • NO
 
  • YES
  • NO
 
 
  • YES
  • NO
 
  • YES
  • NO
 
  • YES
  • NO
 
  • YES
  • NO
 
  • YES
  • NO
 
  • YES
  • NO
 
  • YES
  • NO
 
 
  • YES
  • NO
 
  • YES
  • NO
 
  • YES
  • NO
 
  • YES
  • NO
 
  • YES
  • NO
 
  • YES
  • NO
 
  • YES
  • NO
 

Project Proposal Files