An Introduction to ISO 15926 November 2011 - iRINGToday

More documents

Recommendations

Info

Custom Map Line Number Area Fluid Code Nom Dia Service Class Insulation Thk 150 HCL 250 1C200 35 In fact, it may not even be that nice. It could be something like this: Area WBS Service Class Nom Dia Fluid Code Testing Insulation Thk 150 7395-132 1C200 250 HCL 3 35 Many engineering procurement and construction (EPC) contractors have proprietary work processes for plant design supported with custom software. It is quite possible that the database the design engineer used to create your line list has the columns in a different order, and with other columns mixed in. The line list sent to you could have been created with reportwriting software that had been configured to select just the right columns and put them in just the correct order just for your project. This added complication may not reveal itself until you get “under the hood” and look at the database dump. If you are the one transferring information from one application to another, it is up to you to figure out all the pieces and to put Humpty Dumpty back together for your construction application. It is a good thing that the lexical scope of a line list is only a few dozen terms! A Confederation of Applications If linking the first two applications together works out well, you may be tempted to link in another one. Figure 1.8 shows how the engineering application might be mapped to a procurement application with a second custom database map. Engineering Application Line Table tag_no dia len temp press ifc tag_no dia len temp press ifc id dia cl temp press ifc id dia cl temp press ifc Line Table Construction Application Custom Map tag_no dia len temp press ifc tag dia cl ifc tag dia len code price ifc Line Table Procurement Application Fig 1.8 A confederation of applications. This is the beginning of what might be called a “confederation of applications” whereby many applications get information from each other, with custom-built database maps between each CHAPTER 1 22
pair of applications. Conceivably, you could link all of the construction applications for your project together in this manner to form an enterprise-wide solution (Figure 1.9). Fig 1.9 An enterprise-wide solution. If you managed to do all of this before your construction project was finished, you would have at least a short period of relative bliss. Instead of having to manually export a list from one application, massage it a bit, perhaps do a unit conversion or two, and then import it into another application all you have to do is push a button. The advantage, in terms of lower labor costs and higher reliability, is obvious. In addition, if mapping databases together point to point on a project is good why not connect all applications in your company together the same way? Of course, many organizations do this. Although there may not be a theoretical limit to the number of applications that can be connected in this way, there is a practical limit. Every piece of software you link together is subject to change. For the most part, this is good. As hardware becomes more powerful, we can make software do more things. However, the natural cost of this is that eventually the database structure of an application will change. If you use point-to-point maps to link databases directly together, the link will break when either of the databases changes. If you have many applications daisy-chained together, they may all go down like a row of dominos. The practical reality of this approach is short lifetimes, high maintenance, and having to relearn an application’s data structure whenever something goes wrong. How do we deal with this? As it turns out, collectively, we have tried a number of options. The first approach is some variation of “If it ain’t broke, don’t fix it!” Here an organization deliberately stops upgrading software even when new versions are released. The immediate CHAPTER 1 23
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: There is always an easy solution to
Page 31 and 32: Map to Common Dictionary Map from C
Page 33 and 34: application, he simply used the app
Page 35 and 36: zation will use it to further their
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

Create successful ePaper yourself

Delete template?

Save as template?