Versions Compared

Key

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

Canonical Model

other

Linktoparent

Submitted dateLast Update Date

Project Details

Page properties
Domain
Project Identifier
Text Field
defaultexample: P1021
idpid
requiredtrue
P1052
Bureau Decision #
Text Field
defaultexample: P1021
idBureauDecision
requiredtrue
#1709031
Version
Project Proposal Status

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

Project Page

Canonical Model

Supporting VC
Project Lead
HoD Support
form-
date
textfield-macro
default
Click to set the submissions date
example: EU / US / UN
id
submitted_date
HodSupport
requiredtrue
 
N/A
Status
form-
date
select2-macro
default
Click to set the latest update date
Select the status for this project
id
latest_updated_date
project_status
requiredtrue
selectedCompleted
  • Initiated
  • In development
  • Completed
Version
 
Text Field
defaultClick to set the version number
idversion_number
requiredtrue
 
SP Page Status
hidetrue
width25%

Comment

Insert here a link to the project page using the brackets [   ]

 

 

Project Purpose

Text Area
default<click here to edit>
idproject_purpose
The project’s purpose is to address the now globally recognised importance of the role of canonical process and data models in facilitating trade. 
Given UN/CEFACT’s current global recognition as a proven and effective standards developer, the development of such a canonical mode is considered to be UN/CEFACT’s number one opportunity.
The project will draw on UN/CEFACT’s sound foundations and current progress to date in the development of such a canonical model and proceed to develop guidelines to assist all working groups engaged in the development of UN/CEFACT standards and recommendations to contribute effectively to the delivery of the required canonical model. 

What does “canonical” mean?
(adj.) Authoritative or standard: conforming to an accepted rule or procedure. When referring to programming, canonical means conforming to well-established patterns or rules. The term is typically used to describe whether or not a programming interface follows the already established standard.	

The opportunity & the driving forces
UN/CEFACT is poised to significantly contribute to:
     •	Blockchain enabled “Trust” applied to the supply chain
     •	Internet enabled “Collaboration” applied to the supply chain “Data Pipeline”
     •	The uptake of process driven as distinct to document driven supply chains as required to gain benefit from blockchain and IoT technologies, and in support of “Event Driven Architectures” based services
     •	Deployment of UN/CEFACT’s Reference Data Model approach
To deliver UN/CEFACT must now focus on processes and choreography moving beyond primarily focussing only on message definition.

Project Scope

Text Area
default<click here to edit>
idproject_scope
The project will examine all current UN/CEFACT deliverables covering BRS; RSM; ISCRM; CCL: SCRDM & MMT-RDM; MA & schema. 
Based on the existing UMM (2003) and CCTS (2003) both designed to ensure that UN/CEFACT works to the delivery of the required canonical model, and in considering newer technologies, an analysis will be conducted to determine the extent to which modernization may be required of the base UN/CEFACT instruments and methods.
Preliminary assessment and experience dating back to 2002 indicates that to original developers of the UN/CEFACT instruments UMM & CCTS held great insight into the directions of future technologies including blockchain and sensor technology.
The project will assess any identifiable gap in existing instruments, tools and methods, make recommendations as to how to address, and then to develop guidelines to ensure that the opportunity to use to greater purpose in particular UMM and related artifacts is addressing the global move to Event Driven Architectures applied to software based business solutions. This project may result in subsequent projects where technical specifications may need to be updated to the latest technologies.

Project Deliverables

Text Area
default<click here to edit>
idproject_deliverables
The project deliverables are:
     •	Gap analysis and recommendations with respect to any ‘modernization’ required of existing instruments, methods or deliverables.
     •	Report on the current and proposed use of tools, both commercial and bespoke as deployed in the work of developing UN/CEFACT recommendations and standards
     •	Development of Guidelines for extended/deeper use of UMM, CCTS and resultant BRS, RSM, ISCRM, SCRDM, MMT-RDM, CCL, schema
     •	Executive guide material suited to communication of the UN/CEFACT capability in standards development
2.0
Submitted date
Date Picker
defaultClick to set the submissions date
idsubmitted_date
requiredtrue
2017-07-24
Draft Development Completion
Date Picker
defaultDraft Development date
idDraft
2018-02-01
Publication Date
Date Picker
defaultExit date
idExit
2018-05-01
Excerpt

Project purpose

The project’s purpose is to address the now globally recognised importance of the role of canonical process and data models in facilitating trade. Given UN/CEFACT’s current global recognition as a proven and effective standards developer, the development of such a canonical mode is considered to be UN/CEFACT’s number one opportunity.

The project will draw on UN/CEFACT’s sound foundations and current progress to date in the development of such a canonical model and proceed to develop guidelines to assist all working groups engaged in the development of UN/CEFACT standards and recommendations to contribute effectively to the delivery of the required canonical model.

Info
titleWhat does “canonical” mean?

(adj.) Authoritative or standard: conforming to an accepted rule or procedure. When referring to programming, canonical means conforming to well-established patterns or rules. The term is typically used to describe whether or not a programming interface follows the already established standard.

The opportunity & the driving forces

UN/CEFACT is poised to significantly contribute to:

  • Blockchain enabled “Trust” applied to the supply chain
  • Internet enabled “Collaboration” applied to the supply chain “Data Pipeline”
  • The uptake of process driven as distinct to document driven supply chains as required to gain benefit from blockchain and IoT technologies, and in support of “Event Driven Architectures” based services
  • Deployment of UN/CEFACT’s Reference Data Model approach

To deliver UN/CEFACT must now focus on processes and choreography moving beyond primarily focussing only on message definition.

Project scope

The project will examine all current UN/CEFACT deliverables covering BRS; RSM; ISCRM; CCL: SCRDM & MMT-RDM; MA & schema.

Based on the existing UMM (2003) and CCTS (2003) both designed to ensure that UN/CEFACT works to the delivery of the required canonical model, and in considering newer technologies, an analysis will be conducted to determine the extent to which modernization may be required of the base UN/CEFACT instruments and methods. Preliminary assessment and experience dating back to 2002 indicates that to original developers of the UN/CEFACT instruments UMM & CCTS held great insight into the directions of future technologies including blockchain and sensor technology.

The project will assess any identifiable gap in existing instruments, tools and methods, make recommendations as to how to address, and then to develop guidelines to ensure that the opportunity to use to greater purpose in particular UMM and related artifacts is addressing the global move to Event Driven Architectures applied to software based business solutions. This project may result in subsequent projects where technical specifications may need to be updated to the latest technologies.

Project Deliverables

The project deliverables are:

  • Gap analysis and recommendations with respect to any ‘modernization’ required of existing instruments, methods or deliverables.
  • Report on the current and proposed use of tools, both commercial and bespoke as deployed in the work of developing UN/CEFACT recommendations and standards
  • Development of Guidelines for extended/deeper use of UMM, CCTS and resultant BRS, RSM, ISCRM, SCRDM, MMT-RDM, CCL, schema
  • Executive guide material suited to communication of the UN/CEFACT capability in standards development

Exit Criteria

The exit criteria will be:

  • Gap analysis and recommendations with respect to any ‘modernization’ required of existing instruments, methods or deliverables.
    • Analysis and recommendations presented to the Bureau for Project Exit
  • Report on the current and proposed use of tools, both commercial and bespoke as deployed in the work of developing UN/CEFACT recommendations and standards
    • Report presented to the Bureau for Project Exit
  • Development of Guidelines for extended/deeper use of UMM, CCTS and resultant BRS, RSM, ISCRM, SCRDM, MMT-RDM, CCL, schema
    • Guideline presented to the Bureau and intended to be circulated to all Domains and eventually published on the website for future usage guidance.
  • Executive guide material suited to communication of the UN/CEFACT capability in standards development
    • Guide presented to the Bureau and intended to be presented to the Plenary for information and published on the

Exit Criteria

Text Area
default<click here to edit>
idexit_criteria
The exit criteria will be: • Gap analysis and recommendations with respect to any ‘modernization’ required of existing instruments, methods or deliverables. o Analysis and recommendations presented to the Bureau for Project Exit • Report on the current and proposed use of tools, both commercial and bespoke as deployed in the work of developing UN/CEFACT recommendations and standards o Report presented to the Bureau for Project Exit • Development of Guidelines for extended/deeper use of UMM, CCTS and resultant BRS, RSM, ISCRM, SCRDM, MMT-RDM, CCL, schema o Guideline presented to the Bureau and intended to be circulated to all Domains and eventually published on the website for future usage guidance. • Executive guide material suited to communication of the UN/CEFACT capability in standards development o Guide presented to the Bureau and intended to be presented to the Plenary for information and published on the
    • website.

Project Team Membership and Required Functional Expertise

Text Areadefault

<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.

Head of Delegation Support

Text Areadefault<click here to edit>idhead_of_delegation

HoD

support

not

required

for

internal

/

communication

deliverables.

Geographical Focus

Text Areadefault<click here to edit>idgeographical_focus

The

geographical

focus

is

global.

Initial Contributions

Text Areadefault<click here to edit>idinitial_contributions

  • UN/CEFACT
  • Modelling
  • Methodology
  • (CEFACT/TMG/N093)
  • UN/CEFACT
  • ebXML
  • Core
  • Components
  • Technical
  • Specification
  • Version
  • 2.01
  • UN/EDIFACT
  • Data
  • element
  • directory
  • D.16A
• BRS and RSM Templates
  • BRS and RSM Templates

Resource Requirements

No additional secretariat resources will

Resource Requirements

Text Area
default<click here to edit>
idresource_requirements
No additional secretariat resources will

required.

Project Leadership

Text Area
default<click here to edit>
idproject_leadership
Proposed Project Leader. Tat Tsen Jonathon Koh

Proposed Project Leader: Jonathan Tat Tsen KOH

Restrict Content
anonymoushide
usersMalik

Milestones

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
Gap analysis, report, guidelines, Executive Guide
Select2
defaultSELECT
idyesno_odp1
selectedYES
  • YES
  • NO
Date Picker
defaultNO DATE SELECTED
idexpdate_odp1
2017-09-01
Select2
defaultSELECT
idyesno_odp2
selectedYES
  • YES
  • NO
Date Picker
defaultNO DATE SELECTED
idexpdate_odp2
2017-11-01
Select2
defaultSELECT
idyesno_odp3
selectedYES
  • YES
  • NO
Date Picker
defaultNO DATE SELECTED
idexpdate_odp3
2018-02-01
Select2
defaultSELECT
idyesno_odp4
selectedYES
  • YES
  • NO
Date Picker
defaultNO DATE SELECTED
idexpdate_odp4
2018-04-01
Select2
defaultSELECT
idyesno_odp5
selectedYES
  • YES
  • NO
Date Picker
defaultNO DATE SELECTED
idexpdate_odp5
2018-05-01
Select2
defaultSELECT
idyesno_odp6
selectedYES
  • YES
  • NO
Date Picker
defaultNO DATE SELECTED
idexpdate_odp6

 
2018-05-01
Select2
defaultSELECT
idyesno_odp7
selectedNO
  • YES
  • NO
Date Picker
defaultNO DATE SELECTED
idexpdate_odp7
 
Text Field
default<click here to edit>
iddeliverable_name2
 
Select2
defaultSELECT
idyesno_odp11
selectedYES
  • YES
  • NO
Date Picker
defaultNO DATE SELECTED
idexpdate_odp11
 
Select2
defaultSELECT
idyesno_odp22
selectedYES
  • YES
  • NO
Date Picker
defaultNO DATE SELECTED
idexpdate_odp22
 
Select2
defaultSELECT
idyesno_odp33
selectedYES
  • YES
  • NO
Date Picker
defaultNO DATE SELECTED
idexpdate_odp33
 
Select2
defaultSELECT
idyesno_odp44
selectedYES
  • YES
  • NO
Date Picker
defaultNO DATE SELECTED
idexpdate_odp44
 
Select2
defaultSELECT
idyesno_odp55
selectedYES
  • YES
  • NO
Date Picker
defaultNO DATE SELECTED
idexpdate_odp55
 
Select2
defaultSELECT
idyesno_odp66
selectedYES
  • YES
  • NO
Date Picker
defaultNO DATE SELECTED
idexpdate_odp66
 
Select2
defaultSELECT
idyesno_odp77
selectedYES
  • YES
  • NO
Date Picker
defaultNO DATE SELECTED
idexpdate_odp77
 
Text Field
default<click here to edit>
iddeliverable_name3
 
Select2
defaultSELECT
idyesno_odp111
selectedYES
  • YES
  • NO
Date Picker
defaultNO DATE SELECTED
idexpdate_odp111
 
Select2
defaultSELECT
idyesno_odp222
selectedYES
  • YES
  • NO
Date Picker
defaultNO DATE SELECTED
idexpdate_odp222
 
Select2
defaultSELECT
idyesno_odp333
selectedYES
  • YES
  • NO
Date Picker
defaultNO DATE SELECTED
idexpdate_odp333
 
Select2
defaultSELECT
idyesno_odp444
selectedYES
  • YES
  • NO
Date Picker
defaultNO DATE SELECTED
idexpdate_odp444
 
Select2
defaultSELECT
idyesno_odp555
selectedYES
  • YES
  • NO
Date Picker
defaultNO DATE SELECTED
idexpdate_odp555
 
Select2
defaultSELECT
idyesno_odp666
selectedYES
  • YES
  • NO
Date Picker
defaultNO DATE SELECTED
idexpdate_odp666
 
Select2
defaultSELECT
idyesno_odp777
selectedYES
  • YES
  • NO
Date Picker
defaultNO DATE SELECTED
idexpdate_odp777
 

Project Proposal Files

Attachments
oldfalse