DEX Publication Project

1

• DEX Publication Project
• Core Team Workshop
• 13-14 February 2007
• Filton

2
Agenda

• Status
• Pilot uploads to DEXLib
• Project Objectives
• Workshop Deliverables
• DEX related concepts
• Configuration requirements
• Detailed plan for completion of selected
  Capabilities and Templates
• Example data (postponed to a later meeting)
• Next meeting
• AOB

3
Status

• TLSS (UK MOD)
• Development of templates. Status is reflected in
  DEXLib
• Aviation Maintenance DEX (UKMOD)
• Development of Capabilities and Templates. Status
  reflected in DEXLib. Overlapping scope
  (templates) with TLSS
• NDLO DEXs
• Issues to capabilities and templates not
  uploaded. To be performed the next two weeks
• FMV
• Developing a PLCS interface for various systems.
  Business DEX to be defined by end of March 07.
  FMV terminology part of scope.

4
Project Objectives

• Develop at least two DEXs ready for publication
  /standardization in OASIS. Related capabilities,
  templates and reference data are part of the
  scope.
• The following DEXs are scope of this project
• Aviation Maintenance
• NDLO Task DEX
• OASIS Task DEX
• Operational Feedback DEX Work Package Report
  DEX ? NO FUNDING AVAILABLE

5
Workshop Deliverables

• Concepts to be documented Relationship between
  them
• What to be standardized / Checklists to be
  developed
• Procedure for review and co-ordination activities
• Prioritize activities
• Capabilities / templates (which ones, when, who)
• Infrastructure (DEXLib)
• Ref data ? Separate workshop
• Architecture,
• Content,
• Process
• Help documentation

6
Concepts

• To be documented Definition, Why, Criteria for
  defining new ones, naming conventions etc.
• DEX
• Business DEX
• Capability
• Template
• Template
• Business Template
• Business Objects
• Publication levels
• Reference data
• Rules

7
DEXLib

• How should a DEX look like?
• Links to its components
• Various views
• Business view
• Developer view
• Implementer view
• Mapping view
• DEXLib, 2 publication environments
• For developers
• For the public

8
Check lists
9
Conclusions

• We do need standard DEXs for defining Conformance
• standard Something published by OASIS as a
  standard
• A business DEX is a subset of a standard DEX
• 4 levels of approvals (publications)
• OASIS standard. DEXs that has been through the
  OASIS ballot process, i.e. approved as a standard
  OASIS DEX (TC checklist OASIS specific check
  list). Approved by PASIS, TC, sponsor.
• Validation. Implementers Forum. Test data.
  Published.
• Published. DEXs that has been checked against the
  OASIS TC check list and approved by the TC.
  Sponsor approved. Published as a defacto
  standard or community standard.
• Presented. DEXs published for information only.
  Non or minimum review of the TC. Approved by
  funding organization

10
Conclusions

• We do need Business Object as separate items in
  DEXlib. Short run business as usual.
• Infrastructure issues
• Business Objects / Business DEXs
• Longform generation of DEXs through Templates and
  not Capabilities
• Terminology generic DEX ? DEX
• Business Template is a valid term. Deviates
  from Template by additional business
  constraints and use of reference data classes
• Remove all referencing capabilities

11
Risks

• No DEXLib functionality for supporting the Ballot
  process
• New revision of the PLCS schema

12
Actions (1)
13
Actions (2)
14

• The End

15
DEX

• Why Contractual and exchange purposes
• DEX Schema plus reference data to which one can
  claim conformance to
• Information of how the schema shall be used. The
  specification must be unambiguous.
• A packaging mechanism ???
• Represented through a conformance class
• DEX exchange by packaging in Message and Envelope

16
Conformance to a DEX

• Conformance to a valid DEX schema, including
  rules provided through the templates
  instantiation patterns

17
Capability

• User guide for how PLCS entities can be used.
  Provides the context for related templates and an
  explanation of how PLCS entities can be used to
  represent concepts
• To make PLCS understandable for new users
• Represents a view of PLCS functionalities
• Not for technical implementation purposes
• Criteria for defining new capabilities Through
  need for functionalities that are not described
  by existing capabilities

18
Templates

• Provides a normative instantiation pattern of
  entities referenced within the capability
• Normative means shall
• Two templates are not allowed to represent the
  same concept / functionality
• Criteria for defining new templates / extend
  existing templates
• Normative
• Functionality
• Re-usable in the community

19
Business Objects

• A subset of a DEX
• Business Term (definition)
• PLCS representation
• A grouping of one or more logical related
  business objects or business term (e.g Part
  list)
• Why do we need BOs?
• Logical units for data exchanges between two
  business partners (on working level)
• Risk for not defining BCs as separate units in
  DEXLib Re-usability
• Investigate inclusion of Business Objects into a
  DEX

20
Business DEX publication

• Presentation of a list of Business Objects
• Information flow supporting the business need
• Terms describing the business objects

21
Business Concepts / Capability

• Type of groupings
• A set of templates that instantiates different
  functionalities of one capability ? Capability
• A set of templates that together provides a set
  of functionalities ? Business Object ?
• One template to be used in various ways ? The
  same template with different use of the parameter
  set

22
Configuration requirements

• Project plan
• This activity establishes requirements for
  configuration management of capabilities and
  DEXs, including documentation. The activity also
  contains the implementation of the requirements
  in the DEXLib tool

23
Reference data

• OWL
• Rdf
• Point to the source
• RDL
• Templates
• We shall not use Assigning business specific
  reference data . Use assigning reference data.

24
Next meeting Reference data WS

• Next meeting / Reference data 7-9 March
  Stockholm / Eurostep
• Subject Conclude previous discussions of PLCS
  Reference data
• Participants
• Core team
• 1 additional resource from DNV
• Eurostep David Price or Per Åke Ling
• Preparations
• WebEx 22 Feb, 1400 UK time
• WebEx 1 March, 1400 UK time

25

• The End