synchronise work on dexs and reference data between plcs pilots and oasis/plcs workshop #3 10 – 11...
DESCRIPTION
3 PLCS Inc. (c) 2002 Agenda – Thursday 11 November Next workshops November in Oslo and 9-10 December in London Agenda Summing up yesterdays discussions Mapping solutions Document Review applied capabilities with reference data Minimum data set for representation Scenarios Documenting business concepts in DEXLibTRANSCRIPT
Synchronise work on DEXs and reference data between PLCS pilots and OASIS/PLCS
Workshop #310 – 11 November 2004
2PLCS Inc. (c) 2002
Agenda – Wednesday 10 November
Actions from previous meetings Mapping solutions Identification for referencing Tagging Meta data Standard reference data Documentation of business concept Workshop schedule
3PLCS Inc. (c) 2002
Agenda – Thursday 11 November Next workshops
23-25 November in Oslo and 9-10 December in London Agenda
Summing up yesterdays discussions Mapping solutions
Document Review applied capabilities with reference data
Minimum data set for representation Scenarios
Documenting business concepts in DEXLib
4PLCS Inc. (c) 2002
Proposed agenda for reference data workshop in Oslo 23-25 November
Identify local reference data for the example Recommend standard reference data for the example Identify local codes Recommend representation of codes in the RDL Where to link reference data (capabilities and/or
DEXs?) Which reference data to be located where?
In the DEX specification In the P21/P28 file In the capabilities
5PLCS Inc. (c) 2002
Proposed agenda for workshop in London 9-10 December
Report from the workshops Review MOD mapping document Plan for DEX and reference data development in
OASIS
6PLCS Inc. (c) 2002
Conclusions - 1
The example business concept to be documented as a DEX in DEXLib
DEX name: ”Equipment and part list” Relationship between Parts and Equipment:
Promissory_usage (not assembly_usage)
7PLCS Inc. (c) 2002
Conclusions - 2 Messaging.
Message is part of the P21 DEX file only one type of DEX in each P21 file. only one P21 file per message
Message identifies the “starting point” (equipment) using the content_item. Content_item refers to P21 equipment id (OID).
Multiple equipments to be exchanged using multiple content_items. Message is not used to transmit access instruction such as add, delete, update, partial
update. Identify the message:
identification_assignment to be assigned to message. The sender is identified using envelope.
The envelope is not part of the exchange file (P21/P28) or the message. Need to be generated at the receiving end to identify the sender.
8PLCS Inc. (c) 2002
Conclusions - 3 Baselines.
Baselines are documented in C063 “representing_product_configuration”.To be reviewed. Recommend a higher level ontology for view_definition_context. To be entered in the PLCS RDL.
Proposed life cycle stages (maybe states or status) for tasks: Identification Draft Mature Obsolete
9PLCS Inc. (c) 2002
Conclusions - 4 Investigate how to exclude entities from capabilities used in a DEX to reduce
the longform
Recoding the information entry into a PLCS application (date/time, source, approval) is an implementation issue
Classification of identifiers.How to preserve identifiers throughout the lifetime?The OEM (Original Equipment Manufactorer or equivalent) identifier should be classified as the master id, and maintained throughout the lifetime. Two alternatives: (1) Always exchange the master identifier or (2) Store the identifier as reference data.
10PLCS Inc. (c) 2002
Conclusions - 5 Ignore all description attributes.
Use document_assignment and classify the entity as description class, annotation class etc. Where not possible use property_assignment (to be explicit documented in the capability). To manage the description as a document the translator has to identify the document and generate document ID.
Ignore ID, name and role attributesID and name attributes to be represented by identification_assignment.Role attribute values to be represented as classification.
NEW Capability ”Representing_description” neededCapability - Short term solution. Long term solution: new module “Description”.Scope: Descriptions, annotations, warnings/labelsDependent capabilities: Justification and organization_or_person_in_organizationAction: The capability is registered, but has no content – TBD
11PLCS Inc. (c) 2002
Conclusions - 6
C016 Representing_person_organizationThe capability need to be completed for review. Original editor: NDLO pilot.
C036 Assigning_date_timeThe capability need to be completed for review. Original editor: NDLO pilot.
12PLCS Inc. (c) 2002
Conclusions - 7
Todays architecture imply three categories of documentation in DEXLib Generic capabilities:
Building blocks for longforms Represent agreed model interpretations
Specific exchange needs (business concepts) Defines the data to be exchanged for a specific business objective including a longform
Generic DEXs Business objective: When used, these shall represent the specific exchange needs Technical objective: generate a DEX longform
Usage of the DEX.3 user categories:
Business partners: Contracting for a DEX Software vendors End users: queries supporting applications
13PLCS Inc. (c) 2002
Conclusions - 8
Indexing and business conceptsSearch functionality in DEXLib to be supported by an indexing functionality. Recommendations for index functionalities – part of scope for this project The Index list should contain business concepts No direct link between the business concept and its undelaying capabilities Direct link to the business concept DEX
14PLCS Inc. (c) 2002
Conclusions - 9
Documentation of a business concept in DEXLibAgreed on method for documenting business concepts To be documented as a DEX The documentation should be supported by graphical representation of the business
concept (instantiation diagram) Existing generic capabilities to be used as building blocks for the longform of the
example DEX The longform should be pruned for the specific business concept. All entities from
generic capabilities are not always needed. How to exclude entities will be investigated. The business concept specific information that is not covered by the generic capabilities
shall be documented in the DEX. Separate set of standard reference data for the business concept to be defined in the
DEX (no re-use of reference data in the generic capabilities).
15PLCS Inc. (c) 2002
Outstanding questions
Representing business concepts/objects as Separate DEX Specialization of existing DEX Capability
16PLCS Inc. (c) 2002
Actions
Update AP239 schema: identification_assignment to be assigned to message. (Rob B)
Baselines.Documented in C063 “representing_product_configuration”.To be reviewed. (DNV)
Prune longform.Investigate how to exclude entities from capabilities used in a DEX (Rob B)
Messaging.Update Messaging capability according to agreed solutions in the meeting (Sean B)
17PLCS Inc. (c) 2002
Actions Classification of identifiers.
How to preserve identifiers throughout the lifetime?One identifier should be defined as master and maintained throughout the lifetime. Two alternatives: (1) Always exchange the master identifier or (2) Store the identifier as reference data. (Rob B)
Need life_cycle_stages and application_domains.Propose an upper ontology on the OASIS TC exploder. (DNV)
Effectivity.Extend selects. (Rob B)
Identify and recommend use of /IGNORE as attribute value and alternative ways of representation. action on Leif G.Should be documented in “Introduction” to DEXLib. Action: TBD
18PLCS Inc. (c) 2002
Actions Complete capabilities C016 Representing_person_organization
C036 Assigning_date_time for review (DNV)
Distribute latest version of Part 4 in OWL (DNV)
Distribute PLCS terminology document (Rob B)
Upoload DEX ”Equipment and part list” to DEXLiB as soon as possible (DNV)
19PLCS Inc. (c) 2002
Capabilities used by the business concept
Assign a string property
Identification assignment
Organisation or person in organisation assignment
Representation_of_numerical_value
Assign a quantified property
EquipmentAssign a string property
Representation_of_numerical_value
Assign a quantified property
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
Documents
C002 Representing_parts
C003 representing_assembly_structure
+ C010 Assigning_reference_data+ C001 Assigning identifiers+ C014 Messaging+ C036 Assigning_date_time+ C016 Representing_person_organisation+ C074 Referencing_person_organization
C005 Representing documentsC037 Referencing document
C079 Representing_properties_numerically
C080 Representing_properties_textually
20PLCS Inc. (c) 2002
Capabilities used by the business concept
Ref Fig. 1 in DEX 1