An Introduction to ISO 15926 November 2011 - iRINGToday

More documents

Recommendations

Info

Map to Common Dictionary Map from Common Dictionary Engineering Application Line Table tag_no dia len temp press ifc wcolor tag_no dia len temp press ifc wcolor szTag dDia dLen dTemp dPress dateIFC oColor1 szTag dDia dLen dTemp dPress dateIFC oColor1 id dia cl temp press ifc color id dia cl temp press ifc color Line Table Construction Application New Definition New Definition Industry Reference Data Fig 1.12 Public extensible dictionary. What each developer does, independent of the other, is consult the public dictionary to see whether or not there is an attribute (or “class,” as it is properly known) that describes the color of widgets. In the previous example, there is such an attribute: ColorW. Each developer—again, independent of the other—creates their map. The engineering application maps wcolor to ColorW, and the construction application maps ColorW to color. Note that neither developer had any constraints on what they named the attribute internally, nor had to consult the other to configure their own half of the database map. Indeed, the two developers could have been on different continents—each speaking a different language. Thus, we are now back to the first benefit of ISO 15926; that it has a publicly available data dictionary. 7 The simple fact that the data dictionary exists means that an organization does not have to develop one of its own. The ISO 15926 dictionary can be used for any purpose without royalty payment. However, what if in the previous example the public dictionary did not have a term for the color of widgets? Even if the dictionary were 100-percent up to date when it was first published, new technology would undoubtedly require new terminology. So, another requirement for the ISO 15926 data dictionary is that it be able to handle change. To handle change, the developers of ISO 15926 envision a library that will allow anyone (perhaps with the requirement of a bit of training first) to add new terms. A pilot project, called the RDS/WIP (Reference Data Service/Work in Progress), is in operation—sufficient to handle research needs. One of the current development efforts of ISO 15926 is to create an industrialscale reference data library. With a fully functioning, publically available RDS we will enable organic growth. Each organi- 7. Truth in advertising: ISO 15926 does not intend to have a complete data dictionary for all of “life, the universe, and everything.” It contains an “initial” dictionary and specifies how to extend it. CHAPTER 1 28
zation will use it to further their own private interests, but the result will be an expanded RDS for everyone to use. An Example Project Everyone can see the value of having all participants in a project able to exchange information with one another directly from database to database. On a typical fast-tracked project, however, there is no time for participants to map their software applications to each other’s databases once the project starts. On the other hand, there is no incentive to do so before contracts are awarded either. About the only situation in which the partners in a data exchange are known well enough ahead of time, and in which the volume of information justifies a custom data mapping project, is between an EPC contractor designing a capital asset and the owner. Some owners realize that the handover of asset information is a bottleneck to efficient startup and are increasingly specifying information standards and transfer protocols in advance as a condition of contract award. But one only needs to look at recent examples of this type of thing to verify that such an exercise is expensive and time consuming. However, if all participants in plant design, construction, and operation map their databases and configure their software to comply with an industry standard the time constraint is removed. They no longer have to design and implement database mapping within the window of opportunity of one project. • Vendors are able to bid on more projects. • EPC contractors are able to entertain more bidders. • Owners can mandate more stringent standards for information turnover without limiting the field of participants. Many Project Participants All project participants benefit from mapping their software applications to be able to talk to one another. However, the sheer number of pairs of participants makes doing so prohibitive. The owner has it the worst because one way or another it will have to pay for all mapping exercises on its project. Even if all information an owner receives is funneled through one EPC, all participants will embed the costs of database mapping in their prices. Figure 1.13 is a diagram showing what might be a moderately large project. There are two engineers, three construction contractors, and one owner. The owner has two preferred suppliers it wants everyone to deal with. There are five suppliers between the two engineers, and five suppliers between the three construction contractors. CHAPTER 1 29
Page 1 and 2: ELEMENT 8 WORKFORCE & TRAINING An I
Page 3 and 4: ACKNOWLEDGMENTS Fiatech has produce
Page 5 and 6: TABLE OF CONTENTS INTRODUCTION 1 In
Page 7 and 8: INTRODUCTION Introduction to ISO 15
Page 9 and 10: • The owner will open the link to
Page 11 and 12: that a large proportion of plant in
Page 13 and 14: Although it describes some complex
Page 15 and 16: who need to exchange information al
Page 17 and 18: Open-source and commercial tools ex
Page 19 and 20: what it means in information exchan
Page 21 and 22: No one really liked this (as in “
Page 23 and 24: The Data Sheet Problem Consider a m
Page 25 and 26: Let’s say you are an engineer wor
Page 27 and 28: There is always an easy solution to
Page 29 and 30: pair of applications. Conceivably,
Page 31 and 32: Map to Common Dictionary Map from C
Page 33: application, he simply used the app
Page 37 and 38: EPC 1 F F Const 3 Fig 1.14 Everyone
Page 39 and 40: der will have to fill in the remain
Page 41 and 42: Some owners these days make turnove
Page 43 and 44: Previous project information stored
Page 45 and 46: V 03 EPC 1 ISO 15926 Owner Const 2
Page 47 and 48: How we use the internet to find inf
Page 49 and 50: Suppose one such friend is Bill, wh
Page 51 and 52: “I have data I want to keep for d
Page 53 and 54: markup tags freed document creators
Page 55 and 56: minimize the variability of parts b
Page 57 and 58: change drawings with each other and
Page 59 and 60: 1980 1990 2000 2010 NIST IGES IGES
Page 61 and 62: 1980 1990 2000 2010 This AP is a me
Page 63 and 64: were themselves made up of other co
Page 65 and 66: The Japan Electric Measuring Instru
Page 67 and 68: useful today as a starting point fo
Page 69 and 70: APs by their nature overlap with ea
Page 71 and 72: EPISTLE’s idea was that if you br
Page 73 and 74: For planning, Fiatech developed wha
Page 75 and 76: can be read by another. A translato
Page 77 and 78: plug to integrate their products).
Page 79 and 80: Procurement A Construction A Engine
Page 81 and 82: Part 2: Data Model Fig. 3.6 The par
Page 83 and 84: in French, cook in German, type in
Page 85 and 86:
y pulling in the individual parts a
Page 87 and 88:
Where it gets complicated is differ
Page 89 and 90:
many engineering standards for vari
Page 91 and 92:
15926 so that it can be translated
Page 93 and 94:
ably 1:00 in the morning. Walking t
Page 95 and 96:
But what if we told you that your o
Page 97 and 98:
Part 9: Implementation Methods for
Page 99 and 100:
Other Parts of ISO 15926 Astute rea
Page 101 and 102:
“Do you retain any information of
Page 103 and 104:
When new terms are introduced, you
Page 105 and 106:
you are using them correctly and wi
Page 107 and 108:
from the structure of the data in t
Page 109 and 110:
In turn, you program your cell phon
Page 111 and 112:
CHAPTER 4: CURRENT EVENTS IN THE WO
Page 113 and 114:
umes on an asset. POSC Caesar will
Page 115 and 116:
Fig. 4.1 O&M reference information
Page 117 and 118:
• There will be many levels of ce
Page 119 and 120:
adopting ISO 15926 by highlighting
Page 121 and 122:
Automating Equipment Information Ex
Page 123 and 124:
proof-of-concept software that will
Page 125 and 126:
two applications. (Note here that w
Page 127 and 128:
Tools When the project is ready for
Page 129 and 130:
have already been written and are a
Page 131 and 132:
Part 2 Formal name: Data Model Publ
Page 133 and 134:
for a way to test systems to see ho
Page 135 and 136:
Functional capability Semantic Prec
Page 137 and 138:
URIs Resolvable in Shared Reference
Page 139 and 140:
Functional Capability This category
Page 141 and 142:
Roles Fig. C.1 Figure out each exch
Page 143 and 144:
ACME EMCA Table Name Column Name Ta
Page 145 and 146:
tremely improbable that a valve wil
Page 147 and 148:
number but in a separate table base
Page 149 and 150:
wej The nominal pressure rating for
Page 151 and 152:
drawing_no_piping_ortho maintenance
Page 153 and 154:
and may find that some terms confli
Page 155 and 156:
SEQUENCE NUMBER PR3 1.10 VALVE TYPE
Page 157 and 158:
New Role Fig. C.16 Use ISO 15926-4
Page 159 and 160:
• EMCA receives the neutral file
Page 161 and 162:
Class: The URI of the Class Pressur
Page 163 and 164:
lndirectPropertyScaleReal Individua
Page 165 and 166:
Examples In the search box, search
Page 167 and 168:
Hans Teijgeler has been influential
Page 169 and 170:
Other Organizations MIMOSA http://w
Page 171 and 172:
ver must often operate on what is l
Page 173 and 174:
GLOSSARY OF CONCEPTS There are alre
Page 175 and 176:
meant, ‘there’s a nice knock-do
Page 177 and 178:
If you are a Start Trek fan and hav
Page 179 and 180:
In this example, you reduce the Cor
Page 181:
3925 West Braker Lane (R4500) Austi
show all

An Introduction to ISO 15926 November 2011 - iRINGToday

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?