Presentation of the example business concept – DNV Exchange architecture - DNV Summary / issues from last workshop - D - PowerPoint PPT Presentation

adamdaniel
slide1 l.
Skip this Video
Loading SlideShow in 5 Seconds..
Presentation of the example business concept – DNV Exchange architecture - DNV Summary / issues from last workshop - D PowerPoint Presentation
Download Presentation
Presentation of the example business concept – DNV Exchange architecture - DNV Summary / issues from last workshop - D

play fullscreen
1 / 11
Download Presentation
Presentation of the example business concept – DNV Exchange architecture - DNV Summary / issues from last workshop - D
222 Views
Download Presentation

Presentation of the example business concept – DNV Exchange architecture - DNV Summary / issues from last workshop - D

- - - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

  1. Agenda - Wednesday 20 October • Presentation of the example business concept – DNV • Exchange architecture - DNV • Summary / issues from last workshop - DNV • Presentation of Swedish pilot – FMV/Eurostep/Saab • Business concepts – are they DEXs? - All • Documentation of example business concept in DEXLib - All • Further work – next workshops - All

  2. Business concept in the context of a DEX The business driven need for data exchange.

  3. “Equipment and parts“ Equipment parts(and spares) Equipment part part part_version part_version part_view_definition part_view_definition Context view_definition_context Next_assembly_usage Related attributes values,assignments and classifications Equipment and partrelationship. Assign quantified properties Assign string properties

  4. RDL Core (standard) EXPRESS: Business tailored sub-set of PLCS schema. Data exchange in an open business environment Translator 1 Translator 2 P21/P28 Legacy 2 Legacy 1 DEX n spec DEX n spec Architecture Legacy concepts • RDL: • Ensure unambigous interpretation of standard data • Contains standard concepts for all legacy data • Opens legacy data to selected partners Maps legacy and standard concepts Standard concepts Local ref data • DEX – contains standard ref data only? • Exceptions? • Codification data • Product names • Descriptions • DEX spesification (DEX schema) enables: • Unambiguous interpretation of business concepts and data • Automatic data exchange between legacy systems in an open business environment Translator may claim compliance tothe business concepts and standards represented in the DEX schemas.Quality rules.

  5. Summary / issues from last workshop • “Something more” is needed to represent the business concept, as represented by the proposed example, in DEXLib. In this context, the term “business concept” means the business driven need for data exchange. • The workshop agreed a set of DEX and DEX specification requirements that were not resolved by the current DEXs. • It is still uncertain if the current documentation in DEXLib is precise enough for an implementer to claim compliance to a business driven DEX.

  6. Summary / issues from last workshop • Observation: OASIS/PLCS has three levels of abstraction: (1) PLCS schema, (2) DEX and (3) capability. Specific business concepts for unambiguous implementations are missing. The Norwegian pilot has one level of abstraction – the PLCS schema, and applies business concept representations only. Capabilities have been applied as functions to support the business concepts.

  7. Summary / issues from last workshop • Today’s method to identify and record reference data may not be sufficient. This depends on the boundary for reference data. • Based on the solutions to the issues identified in this workshop, there may be limitations in the DEXLib tool. • The UK MoD document “Common Approach For Mapping Existing Information Models To ISO 10303-239 (Product Life Cycle Support), Working Draft 01, 2004-05-21” may be affected by resolutions to the above observations.

  8. Proposed business concepts Equipment in product Configuration items in product Equipment and parts Equipment spare parts Codification data for parts Configuration items and associated tasks Equipment and associated tasks Task and associated documents Resources for tasks Changes due and changes imlemented Maintenance plan FMECA / FRACAS RCM LORA LCC OASIS DEXs D001 Product breakdown for support D002 Fault states D003 Task set D004 Work package definition D005 Maintenance plan D007 Operational feedback D008 Product as individual D009 Work package report Business concpts – are they DEXs? D001 ? ? D001/D003? D003 D005 D002

  9. Assign a product category Identification assignment Organisation or person in organisation assignment Assign a string property Assign a string property Assign a string property Assign a quantified property Assign a quantified property Assign a quantified property Representation_of_numerical_value Representation_of_numerical_value Representation_of_numerical_value Example Business concept “Equipment and parts“ Organisation or person in organisation assignment Identification assignment Equipment Equipment parts Context Equipment and part relationship

  10. organisation_or_person_in_organisation_assignment organisation Classification assignment Example Business concept “Equipment and parts“ id name description Assign a product category Equipment product_category_assignment product_category part category class software category class raw material category classbulk item category classPOL product category class model category class part classification assignment Draft – not completed part_version Identification assignment part_view_definition contractor designation type numbercontractor_equipment_code_classequipment_description_class brand_name_class identification_assignment Classification capability Organisation or personin organisation assignment /Name_assignee ”name_assignee”contractor_name description_originator of_brand_name role_of_organization_assignment_class ”name_assignee”

  11. Proposed workshop schedule