PLCS DEXsTrine HansenDNV20 April 2005

Content

• OASIS / PLCS Organization • PLCS DEXs • DEX architecture• Process – define and verify capabilities• Way forward

OASIS / PLCS Organization

Quality AssuranceLeadTesters

Quality AssuranceLeadTesters

OASIS TCChairSecretariat1 Voting Member per CompanyTechnical LeadImplementers Forum Lead

OASIS TCOASIS TCChairSecretariat1 Voting Member per CompanyTechnical LeadImplementers Forum Lead

PLCS TC Organization

Technical OversightLead (Information Architect)2 Tool Experts2 Business Experts

Technical OversightTechnical OversightLead (Information Architect)2 Tool Experts2 Business Experts

DEX Development Teams

1 Team Lead1 Modeler1 Business Expert

Implementers ForumLeadSoftware Product VendorsImplementersIntegrators

Implementers ForumLeadSoftware Product VendorsImplementersIntegrators

Infrastructure / Tool Team

Information Architect1 Tool Expert

Secretariat1 Secretariat

SecretariatSecretariat1 Secretariat

Pilots/ProjectsNorwegian PilotUK MOD PilotSwedish PilotOthers

Pilots/ProjectsNorwegian PilotUK MOD PilotSwedish PilotOthers

DEX 0 Development Team

DEX 1 Development Team

DEX 2 Development Team

DEX X Development Team

DEX 0 Development Team

DEX 1 Development Team

DEX 2 Development Team

DEX X Development Team

DEX Y Development TeamDEX Y Development Team

DEX development - Overall status

• 8 DEXs are under development, all together representing the major part of the AP239 domain

• 90 capabilities are defined (building blocks for the DEXs)

• A PLCS reference data library is established (add semantics to the AP239 model)

• The DEXLib tool is established for support of

– Development of the DEXs

– Review activities

– All DEX relevant documentation. Single source of all DEX information

What is a DEX?

• A DEX represents a sub-set of the PLCS data model that includes constraints on how the model can be

interpreted • It serves as a technical specification for implementers of PLCS• The use of standardised DEXs enables:

– The common interpretation of PLCS; multiple dialects of PLCS are avoided– Easy communications across the user communities– A unique reference source for contractors

Maintenance PlanReliability data

LCC data

Provision data

PLCS DEXs

• Product Breakdown for support (D001)• Fault states (D002)• Task set (D003)• Work package definition (D004)• Maintenance plan (D005)• Operational feedback (D007)• Product as individual (D008)• Work package report (D009)

DEX Business framework

PLCSRef data

Business specificref. data

Capability(Usage guide)

Businessspecific concepts

DEX

Exchange contract

Conformance Class

How to represent

What to be represented

Based on

DEX Architecture – Reference data

• Add semantics to the PLCS model •PLCS Reference data library is established• Created and published using the W3C Web Ontology Language (OWL)

PLCSRef data

Business specificref. data

Capability(Usage guide)

Businessspecificconcepts

DEX

Exchange contract

Conformance Class

Based on

DEX Architecture – Capabilities

• Building blocks for the DEX• Represent generic business concepts• Describe HOW the model (AP 239) should be used to represent generic business concepts• Documented in DEXLib

PLCSRef data

Business specificref. data

Capability(Usage guide)

Businessspecificconcepts

DEX

Exchange contract

Conformance Class

Based on

DEX Architecture – DEX

• A DEX represents a sub-set of the PLCS data model • The DEXs are defined to support specific business processes• Support efficient exchange of information between IT systems or organizations• Documented in DEXLib

PLCSRef data

Business specificref. data

Capability(Usage guide)

Businessspecificconcepts

DEX

Exchange contract

Conformance Class

Based on

DEX Architecture – Business Concepts

• Capabilities applied in a business specific context• Mapping guide• A business concept may contain:

• Mapping (textual) to the capability/capabilities that represent the concept• Description of the applicable reference data• Constraints, if needed• Instance diagram

PLCSRef data

Business specificref. data

Capability(Usage guide)

Businessspecificconcepts

DEX

Exchange contract

Conformance Class

Based on

DEX Architecture – Exchange contract

An exchange contract explain WHAT information that is required in a specific data exchange:

• Identify the DEX and its version• Identify the relevant conformance class (documented in the DEX)• Identify business concepts (which again refer to business specific sets of reference data)• Reference data library / ref data sources• Bounding scope of reference data • Data representation rules and constraints (for data validation)• Explanation of HOW that information is represented is defined in the capabilities

PLCSRef data

Business specificref. data

Capability(Usage guide)

Businessspecificconcepts

DEX

Exchange contract

Conformance Class

Based on

Process – Develop Capabilities

Planned activities

• A “Modeller Core team” is established• Leif Gyllström (Saab)• Sean Barker (BAESystem)• Tim Turner (LSC)• Rob Bodington (Eurostep)• Trine Hansen (DNV)

• The Core team will meet frequently and focus on • Review and update core capabilities according to latest agreements• Harmonize reference data• Establish example template of a business concept

• Checklists for review of capabilities and DEXs to be updated/established ASAP• Proposed Architecture and processes to be sent out for ballot soon• DEX 3 meetings……

The End