1 / 15

PLCS DEXs Trine Hansen DNV 20 April 2005

PLCS DEXs Trine Hansen DNV 20 April 2005. Content. OASIS / PLCS Organization PLCS DEXs DEX architecture Process – define and verify capabilities Way forward. OASIS / PLCS Organization. DEX development - Overall status.

carlosm
Download Presentation

PLCS DEXs Trine Hansen DNV 20 April 2005

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. PLCS DEXsTrine HansenDNV20 April 2005

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

  3. OASIS / PLCS Organization

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

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

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

  7. DEX Business framework How to represent PLCSRef data Capability (Usage guide) DEX Conformance Class Based on What to be represented Business specificref. data Businessspecific concepts Exchange contract

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

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

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

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

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

  13. Process – Develop Capabilities

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

  15. The End

More Related