| 13 | | Here are some other attempts at a definition of Part 7 templates: |
| 14 | | * A template is a pattern for stating facts. |
| 15 | | * The ISO 15926-7 Templates are small "implementation models" based on the Part 2 data model. |
| 16 | | * A template is like a lego block. You can put lego blocks together in a great many ways to build anything you like. |
| 17 | | |
| 18 | | ---- |
| 19 | | |
| 20 | | |
| 21 | | == ISO 15926 Part 7 == |
| 22 | | |
| 23 | | Previously we have compared ISO 15926 Templates to engineering data sheet templates, but on a much smaller, more atomic, scale. The comparison is apt. |
| 24 | | |
| 25 | | When engineers start a plant project, one of the first things we do is make templates of each kind of data sheet we expect to use to ensure a common look and feel across the project. For instance, all data sheets for level transmitters will look the same, and have the same values in the same place. The reason a common look and feel is important is because, traditionally, human beings are the ones reading the data sheets. Humans rely on visual clues to determine meaning, and we get used to, essentially, looking at certain (x,y) coordinates for particular values. (For instance, "Maximum Allowable Working Pressure" for a control valve might be something like "1/3 of the way up the page near the right-hand side.") |
| 26 | | |
| 27 | | But in the full ISO 15926 world, machines are the ones reading the data sheets. To a machine, the visual format means nothing--it is more interested in the precise definition of the terms. And there is the rub: To be interoperable based on ISO 15926-2, information has to be modeled rigorously to remove all ambiguity. At the level of information modeling, you cannot implement ISO 15926 ''partly'', you must go all the way. But modeling information to the necessary degree of rigor is beyond what most design engineers will have time to do in a busy project. |
| 28 | | |
| 29 | | Part 7 Templates, then, enable people who are not trained information modelers to achieve the high semantic precision of Part 2 without having to actually deal with Part 2. In other words, Part 7 ''encapsulates'' Part 2. |
| 30 | | |
| 31 | | Using a Part 7 Template is much easier because we only have to be concerned about the few bits of information we are interested in. The template contains all the necessary connection to Part 2, but leaves it "Under the Hood" where we don't have to deal with it. |
| 32 | | |
| 33 | | |
| 34 | | === Metaphor: Templates Make it Easier to Describe Walking the Dog === |
| 35 | | |
| 36 | | Let's say a married couple named Bill and Joan take their dog Willy out for a walk after getting home from work. Figure 1 shows one way to diagram this. |
| 37 | | |
| 38 | | [[Image(HowItWorks_WalkingTheDog.JPG, 650px)]] |
| 39 | | |
| 40 | | '''Fig 1: Walking The Dog''' |
| 41 | | |
| 42 | | This shows that there is the relationship of 'marriage' between two physical objects that are classified as persons and identified as 'man' and 'woman'. There is an indirect relationship between the 'man', and a physical object classified as an organism and identified as 'dog'. |
| 43 | | |
| 44 | | If you've never seen this kind of notation before it will probably look very complex. But the reality is that the diagram is not nearly complex enough to capture everything an information modeler would need to know. For example: |
| 45 | | |
| 46 | | * Details about the 'walking' activity |
| 47 | | * The period_in_time in which they did the walking |
| 48 | | * The location in which they did the walking |
| 49 | | * Is the marriage happy? |
| 50 | | * Are they holding hands? |
| 51 | | * What is the means of the indirect_connection? (A leash?) |
| 52 | | * What is the composition of the leash? |
| 53 | | * What is the breed of dog? |
| 54 | | * etc. |
| 55 | | |
| 56 | | Friends of Bill and Joan will be able to answer all of these questions because they know the context. But our reason for modeling the information is that Bill and Joan's friends are not the intended audience, machines are. We want computer programs to be able to understand the information as well as humans do. |
| 57 | | |
| 58 | | For instance, what is the time of day? Friends will know that Bill and Joan are lab technicians who work the afternoon shift at the local hospital. If they just got home from work it's probably 1:00 in the morning. Walking the dog at that time of day might normally be dangerous given the part of town they live in, but Willy is a large Rottweiler. Friends would understand this implicitly, but if you want a machine to understand it, you have to embed all the context into the information. |
| 59 | | |
| 60 | | Similarly, when modeling plant information, there are a great many people who work with plant objects all day, every day: |
| 61 | | |
| 62 | | * Engineers |
| 63 | | * Buyers |
| 64 | | * Suppliers |
| 65 | | * Installation contractors |
| 66 | | * Maintenance technicians |
| 67 | | * Operators |
| 68 | | * etc. |
| 69 | | |
| 70 | | These people all have a great deal of knowledge about the plant objects because they know the context. However very few of them will have to motivation or patience to learn information modeling. If everyone involved with plant objects had to learn information modeling, ISO 15926 would never get off the ground. |
| 71 | | |
| 72 | | Fortunately, we have Part 7, templates. Templates allow users to implement the full ISO 15926 Part 2 (15926-2) without having to know Part 2. |
| 73 | | |
| 74 | | |
| 75 | | === What a Template Looks Like on the Outside === |
| 76 | | |
| 77 | | [[Image(HowItWorks_TemplatesOutside.JPG, 500px)]] |
| 78 | | |
| 79 | | '''Figure 2: Template''' |
| 80 | | |
| 81 | | A template is basically a regular pattern of information, like rows and columns in a spreadsheet. The column headers in the spreadsheet are the "roles" of the template. Each row of the spreadsheet is a template instance. Each cell in the row is a value of a the role (the column heading). |
| 82 | | |
| 83 | | A template definition is the generic spreadsheet itself - it defines the name of the template, and the roles and what types of information are valid in those roles. |
| 84 | | |
| 85 | | === References === |
| 86 | | |
| 87 | | There are no public repositories of templates for you to look at, but here are a few websites that talk about them some more: |
| 88 | | |
| 89 | | * http://15926.org/home/tiki-index.php?page=ISO%2015926%20part%207 |
| 90 | | |
| 91 | | * http://15926.org/home/tiki-index.php?page=Tutorial%20ISO%2015926%20part%207 |
| 92 | | |
| 93 | | * http://www.infowebml.ws/ |
| 94 | | |
| 95 | | POSC-Caesar Template Definitions |
| 96 | | * https://www.posccaesar.org/wiki/RdsWipTemplateDefinitions |
| 97 | | |
| 98 | | == Next == |
| 99 | | |
| 100 | | * [wiki:ISO15926Primer_HowItWorks_ComplianceColors Primer: How the ISO 15926 Compliance Colors Work] |
| 101 | | |
| 102 | | === Acknowledgements === |
| 103 | | |
| 104 | | Thanks to Hans Teijgeler for the example of a married couple walking the dog. |
| 105 | | |
| 106 | | ---- |
| | 13 | * [wiki:ISO15926Primer An Introduction to ISO 15926] |
