Procedure for CCTS 2.01 & CCBDA 1.0 & NDR 2.1 Artefacts Publication Project
back to Linktoparent
| Submitted date | Last Update Date | Version | Approval Project Proposal Status | Project Page | |||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|
|
| Procedure for CCTS 2.01 & CCBDA 1.0 & NDR 2.1 Artefacts Publication Project |
Project Purpose
| Text Area | ||||
|---|---|---|---|---|
| ||||
The purpose of the project is to define the procedures for the creation and publication of CCTS 2.01, CCBDA 1.0 and NDR 2.1 Business Standards. Reason for version 2: http://www.unece.org/cefact/codesfortrade/ccts_index.html |
Project Scope
| Text Area | ||||
|---|---|---|---|---|
| ||||
The ODP process of developing a Business Standard from inception to publication for CCTS 2 and NDR 2 artefacts includes but is not limited to: - Harmonization of core components - Verification of libraries and other artefacts - Definition of the publication bundle - Publication schedules The project will define all new procedures and artefacts required to develop a Business Standard using the CCL Library and the CCTS 2.01, CCBDA 1.0 and NDR 2.1 Technical Specifications. The project will be conducted by undertaking a proof of concept Business Standard development. The CII semantic content in the CCL will be reused by defining CCBDA Message Assembly restrictions. A public review version of the resultant proof of concept Cross Industry Invoice (CII) will be published. The proof of concept example used will therefore be semantically equal to published CII D15B which will increase the usefulness of the project results for comparison purposes. |
Project Deliverables
| Text Area | ||||
|---|---|---|---|---|
| ||||
The deliverables from this project will include: - Procedure definitions - Description of the deliverables at each step - Proof of concept Business Standard (CII) |
Exit Criteria
| Text Area | ||||
|---|---|---|---|---|
| ||||
NO EXIT CRITERIA |
Project Team Membership and Required Functional Expertise
| Text Area | ||||
|---|---|---|---|---|
| ||||
The project team is a group of experts with deep knowledge in standards production and publication and awareness of implementers’ expectations. |
Head of Delegation Support
| Text Area | ||||
|---|---|---|---|---|
| ||||
Geographical Focus
| Text Area | ||||
|---|---|---|---|---|
| ||||
The geographic focus of the project is global. |
Initial Contributions
| Text Area | ||||
|---|---|---|---|---|
| ||||
The contributions submitted with this proposal include: - CCTS 2.01, CCBDA 1.0 and NDR 2.1 Technical Specifications - CCL D15B - The draft results of the work of the preceding version of the project including : i. Draft publication plans prepared by TBG 1, TBG 6 ii. Draft CCTS 3 Transition Plan |
Resource Requirements
| Text Area | ||||
|---|---|---|---|---|
| ||||
Required resources include project management and modeling expertise plus knowledge of CCTS, CCBDA, NDRs, the ODP and the production rules of the CCL. |
Project Leadership
| Text Area | ||||
|---|---|---|---|---|
| ||||
Proposed Project Lead: Rolf Wessel Proposed Editor: Gerhard Heemskerk |
Milestones
It is proposed that the revised project should restart at ODP Step 4 where the earlier project reached in 2013. This will enable the earlier relevant work to be reused thereby saving time.
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 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Project Proposal Files
| Attachments | ||
|---|---|---|
|