Intelligent Data Sets Accelerating Deployment of ISO15926

Realizing Open Information Interoperability

Template Methodologies

This page is part of the IDS-ADI modeller's project work scope.

This page exists to define the methdologies by which business data sets are chartacterized in terms of templates, and by which different template types are mapped, transformed, assembled or otherwise related.

For definition of what templates are and what differnt kinds of template there are, refer to template types.

For definition of the starting set of specific templates in WIP reference data, refer to template definitions.

The source material for this page is the IDS Characterization Methodology document and associated IDS Characterization Methodology spreadsheet.

Below is an earlier draft from the TracWiki template characterization IdsAdiPart7Lite pages.

This page describes the methodology by which any data set is characterized in terms of 15926.

The characterization methodology proceeds from a business-use definition of that data set (aka a "foreign schema") via its expression as P7L (aka short-cut, Gellish or Part-7-Lite) templates to transformation into short-hand or full Part-7 / Part-2 expressions.

This page defines the process by which short-cuts templates are selected and assembled to create that characterization.

This page and subsequent pages will therefore also explicitly document the short-cut / short-hand and other specific template types implied by that methodology. All templates used are reference data, managed at any time in the WIP RDL (or project RDL extensions).

Back to MmtSig (Modelling, Methodology & Technology SIG) Forward to TemplateStartingSet for initial set of templates to be available in the WIP Forward to TemplateMinimumSubSet minimum subset necessary to populate new WIP content. Continue on this page for the definition of the Template Characterization Methodology This methodology is a detailed elaboration of existing earlier reference specifications. These are provided for reference only, and these pages are intended to supersede them.

P7L Characterization Methodology IDS-120-001 Iss 2x IDS (P7L) Methodology Document (less two large figure image files) ECMv3 Usage Patterns REFERENCE ONLY - Earliest (1999) public description of "Templates" as usage patterns, based on Gellish naming or relation types. The original EPISTLE Useage Patterns Specification (pre-cursor to Part 7) OUTLINE OF METHODOLOGY

This outline describes the methodology proceeding through the layers of modelling in terms of the template types involved.

... graphic ...

IDS/ADI "Part7-lite (P7L)" implementation

Mapping methodology and software tools

Subproject leader: Ian Glendinning (European Time Zone).


Conclusions / end products: (warning! work in progress)

The methodology by which any data set is characterized in terms of 15926: TemplateCharacterization
Templates considered to be the "starting set" of the WIP: TemplateStartingSet
Templates necessary to support minimum population of new WIP content: TemplateMinimumSubSet

Project documents:

All P7L documents


P7-lite ("part seven light") is about mapping methodology between legacy systems and facades.

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

FIATECH ADI will build software using this methodoly; an open source public domain Mapping Tool.

Level of implementation

Better than demo/proof of concept level, but not yet production grade scalable to big projects.

Level of compliancy

Highest level, but in gradual steps.

Example of a gellish template

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.

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.

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.

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

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

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.

About PCA
Reference Data Services (RDS)
RDS Operations Support
Meetings and Conferences
ISO 15926
Special Interest Groups
Technical Advisory Board
Norwegian Continental Shelf Std