The (forthcoming) Mapping Wizard requires a decision tree to assist the person defining the mapping.
This is a description of the user interface of that wizard. It is an evolution of the JORD mapping methodology, and NOT the wizard itself.
First we must define who or what the ObjectOfInterest (OOI) the information is. That requires a declaration, one per OOI . For that we have a few TIPs:
Kind of object
Then we must define about what kind of ObjectOfInterest (OOI) the information is.
Individual or Class
Then we must make the distinction whether we deal with a Class or with an Individual. The table above gives some examples.
Real World or Design World Individual
IFF the OOI is an Individual, then we must make a choice whether it is in the real world around us, or whether it is an Individual in a "Design World" :
Essential type of object
Now we must define what the function or purpose of the OOI is. This cannot be changed without terminating this OOI. For example, whether it is a PUMP (in general) , not CENTRIFUGAL PUMP because that is HOW it is done, or VESSEL and not KNOCK OUT VESSEL because that is too specific. Making it more specific comes later, by classifying it. The choice is large because there are many types of physical objects. Select the applicable class from link.
Finally the Individual or Class must get a label, like a tag number for an Individual or Class in the Design World, or a serial number for manufactured engineered objects. It is important that these identifiers are unique in the context of the data, such as a process plant, If that is not possible other data shall be added to make it unique (e.g. there are many John Doe's, then add the date and place of birth). Since piping systems don't have a serial number the line number may be used in combination with the information whether it is a design or actual piping system.
The label has an important funtion in ISO 15926 in that it is used to fetch the applicable immutable system ID of the OOI for which we use a UUID. A UUID is a universally unique identifier, e.g. 8267d106-7941-470a-b7e3-9f106bef8f42 or fa518ca8-c9cc-4c04-9d85-dc183ecf1cbe . All information about an OOI is attributed to its UUID.
This concludes the declaration of any OOI.
There are two groups of information here:
Information is represented by templates. An indication of the type of template is given by groups:
Select the OOI(s) that will be referred to in the template of choice below:
When both OOIs exist select one of the following templates, when applicable: