Extension of Cross Industry Technical Artefacts
other
Submitted date | Last Update Date | Version | Project Proposal Status | Project 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 models. This project proposal will target the Cross Industry messages for Quotation, Cataloguing, Ordering, Delivering and Remittance advice. The purpose of this project is to develop the technical artefacts needed to allow users to implement the business messages for cataloguing, quotation, ordering, delivering and remittance advice based on the SCRDM and Core Component Business Document Assembly (CCBDA).Project Scope
This project will complement the existing artefacts of cataloguing, quotation, ordering, delivering and remittance advice based on the SCRDM and thereby producing process driven XML schemas. It should be noted that the new process driven XML schemas are intended to replace the published (document-centric) XML schemas for cataloguing, quotation, ordering, delivering and remittance advice. Through the transition period, business requirements consistency will be ensured as all the XML schemas will be based on the same but updated BRSes.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 | YES | YES | YES | YES | YES | YES | ||||||||
YES | YES | YES | YES | YES | YES | YES | ||||||||
YES | YES | YES | YES | YES | YES | YES |
Project Proposal Files