Versions Compared

Key

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

International Supply Chain Orchestration

- Focal Point

Domain

Explore other 
Linktoparent

PDAInternational Supply Chain
Coordinatorsvacant position

 

 

Profile
modeminimal
usergargr


UI Button
colorblue
sizelarge
iconlink
titleWorking Area - Focal Point: ISC Orchestration Domain
urlhttps://uncefact.unece.org/display/themepressdemo/Focal+Point%3A+ISC+Orchestration+Domain

(Access only for registered members)

Background Information

 


Text Area
defaultBACKGROUND-INFORMATION
idbackground-information
Over the past decades, UN/CEFACT has developed a number of standards including business process models, XML schema and core components. The general overarching technical specification of the UN/CEFACT Modeling Methodology (UMM) was intended to guide much of this work. This guidance was useful for electronic messages which correspond to complete paper documents.

Today, data exchange is being conceived as snippets of information
 

 

 

Scope

 

 
 through event-driven data exchanges instead of exchanging complete ‘document’ equivalent messages. This is evident in projects such as the Reference Data Models, the Data Pipeline, Blockchain or Internet of Things. These new methods of data exchange require new methods of considering how these exchanges can work together and complement each other for a same transaction.

Scope


Text Area
defaultSCOPE
idbackground-information2
The scope of the international supply chain orchestration Domain is to support the efforts of all UN/CEFACT related projects to deliver their semantic specifications in a way that suits implementers of web platforms and pipeline /IoT projects as well as traditional document exchange projects.  To achieve that, we will;
	•	Develop an architecture model that presents the Supply Chain Reference Data Model (SCRDM) and Multi-Modal Transport Reference Data Model (MMT) as a set of granular information resources with clearly defined state lifecycles.

	•	For each web resource, explore possibilities such as an Open API 3.0 specification that represents the resource as a RESTful API with JSON data payload and JSON-LD links to related resources. 

	•	Explore the development of a standard event specification such as those based on W3C WebSub that will be used to exchange the event messages (aka “snippets”) that describe each state change in the web resource lifecycle.

Active Projects

Content by Label
showLabelsfalse
max100
showSpacefalse
sorttitle
operatorAND
cqllabel = "project-in-development" and label = "communication-committee" in ("harmonization","orchestration") and label = "project-proposal"
labelstfig,project-in-development,project-proposal

Related Deliverable

 


 
Text Area
defaultRELATED DELIVERABLE
idrelated-deliverable