An Introduction to ISO 15926 November 2011 - iRINGToday

More documents

Recommendations

Info

CHAPTER 5: GETTING STARTED WITH ISO 15926 116 Key Preparation 117 Implementing ISO 15926 118 Join Fiatech or the POSC Caesar Association 123 APPENDIX A: THE PARTS OF ISO 15926 124 ISO 15926 124 APPENDIX B: COMPLIANCE WITH ISO 15926 128 Semantic Precision 129 Representation Technology 129 Referencing Technology 130 Interface Technology 131 Industrial Standardization 131 Subject Matter Scope 132 Metadata Scope 132 Functional Capability 133 APPENDIX C: EXAMPLES OF DATABASE MAPPING 134 Example Set 1: Let’s Just Exchange Raw Data and Figure It Out Together 134 Example Set 2: Wouldn’t It Be Better to Agree on Common Definitions? 141 Example Set 3: Why Don’t We Use Industry Standard Definitions? 147 Example Set 4: Would It Help if I Told You How I Was Using the data? 151 EMCA 156 Using the RDS/WIP 158 APPENDIX D: OTHER RESOURCES 160 Information Modeling Resources 160 Origin of ISO 15926 161 Organizations Responsible for ISO 15926 161 User Groups 162 Other Organizations 163 RDS Browsers 164 Business Interface Definition Guides 164 GLOSSARY OF CONCEPTS 167 Artificial Intelligence and the Semantic Web: Difference Between 167 First-order Logic, Semantics, and Reference Data 167 Ontology and Taxonomy: Difference Between 169 Integration and Interoperability: Difference Between 170 Strong Coupling, Loose Coupling, and Encapsulation 171 Abstraction 172 Semantic Web Technology 173
INTRODUCTION Introduction to ISO 15926 If you are new to the concept of information interoperability, you will be forgiven for thinking that ISO 15926 is a new phenomenon. In fact, the search for easy ways to exchange and reuse engineering information stretches back to the mid 1970s—led by increasingly frustrated end users who resented the inability to transfer their information from one computer-aided design (CAD) system to another. This bit of history is especially poignant for your humble author, who at that time was just starting his career as a piping designer. Whereas large users—heavily represented by the U.S. military and aerospace organizations—were just starting to confront compatibility issues among competing CAD systems, your author had just enrolled in technical school to learn how to draft with a pencil. A few years later—while the U.S. Air Force was hosting a conference that led to the CAD drawing exchange standard known as IGES (which we introduce in Chapter 2)—the author’s idea of high technology was drafting on Mylar with (gasp!) plastic lead! In this introduction to ISO 15926, we will look at the need for information interoperability, some of the things that have been done to address interoperability issues, and some of the things we should be doing instead. We will take a brief historical look at the forebears of ISO 15926, look at the different parts that make up the standard today, and end with some of the things you can do to get started implementing the standard. The obvious question is: Why do we need ISO 15926? The short answer is: So that we can exchange and reuse complex plant and project information more easily and more cheaply. A slightly longer answer is: To mitigate the current high costs of rekeying and reformatting information to move it from one proprietary system to another. For example, take the task of designing, specifying, and purchasing a process instrument for a plant modification. Imagine how many times information has to be rekeyed after the instrument is basically designed, until it is installed and commissioned in the target plant. • After design, enter the information into the project’s engineering design system (which may be a database or spreadsheet). • For quotation, a procurement officer assembles several sets of data sheets and sends a set to each bidder. • Each bidder will have a sales engineer read the data sheets and enter some of the data values into proprietary software to make a selection, and then compose a quotation and return it to the engineering, procurement, and construction (EPC) contractor. • During the design of an instrument, the engineer will usually specify only those properties necessary for operation under process conditions. However, there are many other properties that must be known—which are dependent on the manufacturer. After vendor has been chosen, the design engineer has to enter this information manually into the engineering design system from the vendor’s quotation. • Data sheet turnover to the client will likely be something like an Excel file for each data sheet. • After receiving a load of boxes filled with CDs from the EPC contractor, the owner will review each data sheet. Critical data values will be rekeyed into an asset management system. This can take months. INTRODUCTION 1
Page 1 and 2: ELEMENT 8 WORKFORCE & TRAINING An I
Page 3 and 4: ACKNOWLEDGMENTS Fiatech has produce
Page 5: TABLE OF CONTENTS INTRODUCTION 1 In
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 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?