Extension of Cross Industry Invoice technical artefacts
other
| Submitted date | Last Update Date | Version | Project Proposal Status | Project Page |
|---|---|---|---|---|
2016-05-16 | 2016-05-16 | 1.0 |
Official
| Extension of Cross Industry Invoice technical artefacts |
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
The project deliverables are: 1. Updated CII BRS reflecting the CII PoC findings 2. CII message assembly components based on the CII PoC findings 3. Process-driven CII XML Schema based on the CII PoC findings 4. Publication transition plan for replacing the publication of the current document-centric UN/CEFACT CII XML schema with the publication of the new process-driven CII XML schema.Exit Criteria
1. Updated CII BRS o External review logs o Final draft ready for publication 2. CII CCBDA document assembly specification o External review logs o Final draft ready for publication 3. Process-driven CII XML Schema o External review logs o Final draft ready for publication 4. Publication transition plan o Approval by Bureau o Final draft ready for publicationProject Team Membership and Required Functional Expertise
Membership is open to UN/CEFACT Experts with broad knowledge in the area of standards production and publication and awareness of implementer’s expectations, the functions of UN/CEFACT, and its groups. 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.Head of Delegation Support
• Germany • France • AustriaGeographical Focus
The geographical focus is global.Initial Contributions
The contributions submitted with this proposal include: • CCL D16A and schemas • Draft SCRDM based on CCL D16A • Procedure for CCTS 2.01 & CCBDA 1.0 & NDR 2.1 Artefacts Publication Project • Public Review of PoC : CCTS 2.01 & CCBDA 1.0 & NDR 2.1 Artefacts Publication • CII BRS v2.00.05Resource Requirements
Required resources include project management and modelling expertise.Project Leadership
• Project Leader: Natascha Rossner • Lead Editor: Andreas Pelekies • Editor: Gerhard HeemskerkMilestones
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 |
BRS,XML Schemas,Publication | YES | 2016-05-23 | NO | YES | 2016-06-30 | YES | 2016-08-30 | YES | 2016-09-10 | YES | 2016-09-30 | NO |
Project Proposal Files