Versions Compared

Key

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

Methodology to Subset RDM based Messages

other

Linktoparent


Project Details

Page properties
Domain

Supply Chain Management Specification Domain

Project Identifier
Text Field
defaultexample: P1021
idpid
requiredtrue
P1123
Bureau Decision #
Text Field
defaultexample: P1021
idBureauDecision
requiredtrue
#.....#2305044, #2309067, ##2404023
Project Proposal Status

SP Page Status
dateMar 05, 2018 09:14
hidetrue
width25%
userLaThompson
statusofficial

Project Page

Methodology to Subset RDM based Messages

Supporting VC
Project Lead
HoD Support


NA

Text Field
defaultClick to set the version number
idversion_number
requiredtrue
......
Status
Select2
defaultSelect the status for this project
idproject_status
requiredtrue
selectedin-development
  • Initiated
  • In development
  • Completed
Version
Text Field
defaultClick to set the version number
idversion_number
requiredtrue
1.0
Submitted date
Date Picker
defaultClick to set the submissions date
idsubmitted_date
requiredtrue
2023-05-19
Draft Development Completion
Date Picker
defaultDraft Development date
idDraft
2023-0912-1931
Publication Date
Date Picker
defaultExit date
idExit
20232024-1001-1931

Project Purpose

Text Areadefault<click here to edit>idproject_purpose

The

current

master

RDM

messages,

derived

from

a

RDM

master

message

structure,

cover

all

international

supply

chain

operations

and

take

into

consideration

all

potential

complexities

of

any

industry.

The

deliverable

also

accommodates

any

mode

of

transport.

The

resulting

deliverable

is

rather

large

and

complex

and

can

deter

some

companies

notably

MSMEs

from

being

aware

of

the

potential

of

RDM

based

solutions.

By

providing

an

easy

to

understand

methodology

for

supply

chain

specification

users

will

enable

interoperability

across

the

supply-chain,

combining

features

such

as

end-to-end

track

&

trace,

contributing

directly

to

the

United

Nations

sustainable

development

goals

and

ESG

monitoring.

This

project

aims

to

develop

a

methodology

to

assist

business

process

automation

specialists

to

easily

create

a

subset

of

the

RDM

based

master

messages

for

their

own

supply

chain

or

sector

specific

requirements.

This

would

tailor

a

master

message

to

the

target

industry-specific

elements

and

produce

a

message

subset

(and

children

subset)

that

could

be

used

as

a

basis

for

international

trade

operations.

It

is

expected

that

this

methodology

would

make

it

easier

for

organizations

to

implement

and

exchange

with

others

within

a

specific

sector

or

group

of

trading

partners.

Diagram:

Showing

the

process

to

which

this

Methodology

to

Subset

RDM

based

messages

applies  

applies.

Image Added

Project Scope

Text Area
default<click here to edit>
idproject_scope
This project aims to develop a subset (and children subset(s)) of the RDM based master messages that would be used as a simplified basis for international trade operations. It is expected that this subset will also make subsets of the related code lists (either as qualified data types or restricted by other means, such as schematron). It is expected that there will be no additions to the RDM as a result of this project; the objective is to make a methodology to create a subset of the existing RDM master messages. The resulting artefacts will be based on the existing RDM artifacts and its related BRS.

Project Deliverables

  • Deliverable 1: Webinar to launch the project and get in the key resources
  • Deliverable 2: Whitepaper on methodology for creating a subset of a RDM master message (e.g. Cross Industry Invoice) for implementation
  • Deliverable 3: Training material on the implementation of the RDM

Exit Criteria

  • Exit Criteria for Deliv. 1: Webinar
  • Exit Criteria for Deliv. 2: Whitepaper on methodology for creating subset of a RDM master message (e.g. Cross Industry Invoice) for implementation
  • Exit Criteria for Deliv. 3: Training material ready for publication

Project Team Membership and Required Functional Expertise

Text Area
default<click here to edit>
idproject_membership

Membership

is

open

to

UN/CEFACT

experts

with

broad

knowledge

in

the

area

of:

Supply

chain

management,

RDM,

Message

Implementation

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

HoD support

Text Area
default<click here to edit>
idproject_membership
Required for Technical Standards, Business Standards and UNECE Recommendations. And at the request of the UN/CEFACT Bureau.
Projects that require HoD support must obtain this within 6 months of Bureau provisional approval

Geographical Focus

Text Areadefault<click here to edit>

idgeographical_focusThe geographical focus of the project is global.

Initial Contributions

form-textarea-macro

default<click here to edit>
idinitial_contributions

The

following

contributions

are

submitted

as

part

of

this

proposal.

It

is

understood

that

these

contributions

are

only

for

consideration

by

the

Project

Team

and

that

other

participants

may

submit

additional

contributions

in

order

to

ensure

that

as

much

information

as

possible

is

obtained

from

those

with

expertise

and

a

material

interest

in

the

project.

It

is

also

understood

that

the

Project

Team

may

choose

to

adopt

one

or

more

of

these

contributions

“as

is”.

• SCRDM • Derived messages of SCRDM • White Paper on Reference Data Model • Reference Data Model (RDM) Guideline • Message Construction Guidelines for Core Components Business Document Assembly (CCBDA) • Code Management User Guide • Cross Industry Common Requirements • Relevant regulations

Resource Requirements

Participants in the project shall provide resources for their own participation. The existence and functioning of the project shall not require any additional resources from the UNECE

Resource Requirements

Text Area
default<click here to edit>
idresource_requirements
Participants in the project shall provide resources for their own participation. The existence and functioning of the project shall not require any additional resources from the UNECE secretariat.

Project Proposal Files

Attachments
oldfalse