Presentation on theme: "Slide 1 Presentation of the example business concept – DNV Exchange architecture - DNV Summary / issues from last workshop - DNV Presentation of Swedish."— Presentation transcript:
Slide 1 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 Agenda - Wednesday 20 October
Slide 2 The business driven need for data exchange. Business concept in the context of a DEX
Slide 3 Equipment and parts part part_version part_view_definition part part_version part_view_definition view_definition_context Next_assembly_usage Assign quantified properties Assign string properties Equipment Equipment parts (and spares) Related attributes values, assignments and classifications Context Equipment and part relationship.
Slide 4 Architecture Legacy 1Legacy 2 Translator 1 DEX n spec Translator 2 DEX n spec RDL Core (standard) Local ref data Legacy concepts Standard concepts Maps legacy and standard concepts EXPRESS: Business tailored sub-set of PLCS schema. DEX spesification (DEX schema) enables: Unambiguous interpretation of business concepts and data Automatic data exchange between legacy systems in an open business environment P21/P28 Data exchange in an open business environment Translator may claim compliance to the business concepts and standards represented in the DEX schemas. Quality rules. RDL: Ensure unambigous interpretation of standard data Contains standard concepts for all legacy data Opens legacy data to selected partners DEX – contains standard ref data only? Exceptions? Codification data Product names Descriptions
Slide 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.
Slide 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.
Slide 7 Summary / issues from last workshop Todays 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.
Slide 8 Business concpts – are they DEXs? 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 D001 D005 D003 D002 D001/D003? ? ?
Slide 9 Example Business concept Equipment and parts Assign a string property Identification assignment Organisation or person in organisation assignment Representation_of_numerical_value Assign a quantified property Equipment Assign a string property Representation_of_numerical_value Assign a quantified property Assign a product category Identification assignment Organisation or person in organisation assignment Context Equipment and part relationship Assign a string property Representation_of_numerical_value Assign a quantified property Equipment parts
Slide 10 Example Business concept Equipment and parts part part_version part_view_definition Equipment product_category_assignmentproduct_category classification assignment Assign a product category Identification assignment identification_assignment Classification capability idnamedescription organisation_or_person_in_organisation_assignmentorganisation Classification assignment Organisation or person in organisation assignment /Name_assignee part category class software category class raw material category class bulk item category class POL product category class model category class contractor designation type number contractor_equipment_code_class equipment_description_class brand_name_class role_of_organization_assignment_class name_assignee name_assignee contractor_name description_originator of_brand_name Draft – not completed