| 8 | | '''Conclusions / end products:''' (warning! work in progress) |
| 9 | | |
| 10 | | The methodology by which any data set is characterized in terms of 15926: TemplateCharacterization[[br]] |
| 11 | | Templates considered to be the "starting set" of the WIP: TemplateStartingSet[[br]] |
| 12 | | Templates necessary to support minimum population of new WIP content: TemplateMinimumSubSet[[br]] |
| 13 | | |
| 14 | | |
| 15 | | '''Project documents:''' |
| 16 | | |
| 17 | | |
| 18 | | [source:projects/IDS-ADI/Part7/Part7SpecificationsMethodologies All P7L documents] |
| 19 | | |
| 20 | | * [source:projects/IDS-ADI/Part7/Part7SpecificationsMethodologies/ECMv3_Useage_Patterns.doc ECMv3 Usage Patterns] REFERENCE ONLY - Earliest (1999) public description of "Templates" as usage patterns, based on Gellish naming or relation types. |
| 21 | | * [source:projects/IDS-ADI/Part7/Part7SpecificationsMethodologies/P7L_Characterization_Methodology_IDS-120-001_Iss_2x.doc P7L Characterization Methodology IDS-120-001 Iss 2x] IDS (P7L) Methodology Document (less two large figure image files) |
| 22 | | * [source:projects/IDS-ADI/Part7/Part7SpecificationsMethodologies/P7l_IDS_120_SCT_Latest_0707.zip P7L IDS_120_SCT_Latest_0707] Zip containing latest working spreadsheets representing the P7L Templates and Methodology |
| 23 | | * [source:projects/IDS-ADI/Part7/Part7SpecificationsMethodologies/P7L_Pre2006AT.zip P7L Pre2006AT] REFERENCE ONLY - Most developed previous version of Short-Cut "Atomic" Templates - provided by AVEVA. |
| 24 | | * [source:projects/IDS-ADI/Part7/Part7SpecificationsMethodologies/ISO_15926-2_mapping_to_Gellish.xls ISO 15926-2 mapping to Gellish] mapping 15926 entities to Gellish |
| 25 | | * [source:projects/IDS-ADI/Part7/Part7SpecificationsMethodologies/P7L_relationsset_V1.0.xls P7L relationsset V1.0] first proposal for basic set of P7L relations |
| 26 | | * [source:projects/IDS-ADI/Part7/Part7SpecificationsMethodologies/property-to-template-mapping.xls property-to-template-mapping] Hans Teijgeler's previously proposed mappings beteween Part-2 and the full Part-7-Templates |
| 27 | | * [source:projects/IDS-ADI/Part7/Part7SpecificationsMethodologies/Gellish_and_ISO_15926_V3_Leo_van_Ruijven.rar Gellish and ISO 15926 V3 Leo van Ruijven] Presentation made for ISO plenary as preparation for prososal for integration of the Gellish methodology as a part of 15926 |
| 28 | | * [source:projects/IDS-ADI/Part7/Part7SpecificationsMethodologies/Copy_of_P7LGellish_StartingSet_LeoIan.xls Copy of P7LGellish StartingSet LeoIan] A copy of Leo's spreadsheet, Marked-up by Ian |
| 29 | | * [source:projects/IDS-ADI/Part7/Part7SpecificationsMethodologies/basic_set_V2.xls basic set V2] renewed version of basic set gellish relations |
| 30 | | * [source:projects/IDS-ADI/Part7/Part7SpecificationsMethodologies/basic_set_V5_including_entities.xls basic set V5 including entities] reviewed version of basic set of Gellish relations (57) and applied on systems engineering OIM's |
| 31 | | |
| 32 | | === Scope === |
| 33 | | P7-lite ("part seven light") is about mapping methodology between legacy systems and facades. |
| 34 | | |
| 35 | | The methodology is developed by the IDS project. It uses a wizard-like approach involving Gellish to come to a methodology that can be operated by power users (engineers). |
| 36 | | |
| 37 | | FIATECH ADI will build software using this methodoly; an open source public domain Mapping Tool. |
| 38 | | |
| 39 | | === Level of implementation === |
| 40 | | |
| 41 | | Better than demo/proof of concept level, but not yet production grade scalable to big projects. |
| 42 | | |
| 43 | | === Level of compliancy === |
| 44 | | |
| 45 | | Highest level, but in gradual steps. |
| 46 | | |
| 47 | | === Example of a gellish template === |
| 48 | | |
| 49 | | To be able to understand the difference and similarity between part 7 (lite) and gellish there is agreed to set up use cases c.q. examples based upon generic object information models. |
| 50 | | |
| 51 | | In the context of gellish an OIM can also be seen as a "template" . A template is a collection of gellish facts, representing the OIM. |
| 52 | | |
| 53 | | The example as presented in the attaches files has as subject a "requirement" in the context of systems engineering. In principal, a requirement is represented by a string that capture the actual specification text (a separate template). the model allows to add a new textual specification without deleting the superseded specification text. A requirement is classified by a severity, type of requirement and subject. The requirement has as source a (design)activity and will be used in a activity. Further more a requirement is related to one or more elements in the project decomposition structure such as a system, component, process, function etc. |
| 54 | | |
| 55 | | The OIM is as a entity relation diagram presented in a powerpoint sheet, and worked out in a so called "gellish table" (see the excel file). |
| 56 | | |
| 57 | | In the gellish table there is one main template that uses a second template for capturing the textual specification of the requirement and the status of it (the actual and superseded as well). The template it self and a populated version is given. All used terms can be found in the RDL and are more or less derived from STEPlib because of the fact that part 4 doesn't know these terms yet (see the RDL worksheet). |
| 58 | | |
| 59 | | this example is supported by documentation about gellish, derived from sourceforge.com (search for "gellish") With in the excel file "relation set gellish.xls" you will find in the colomn "Gellish phrase" the until this moment defined available gellish relationships. |
| 60 | | |
| 61 | | |
| 62 | | |
| 63 | | |
