Interoperability Between ISO-IEC Standardization and ANSI-IsA V
89
7/21/2019 Interoperability Between ISO-IEC Standardization and ANSI-IsA V http://slidepdf.com/reader/full/interoperability-between-iso-iec-standardization-and-ansi-isa-v 1/89 1 The differences betw een IS0 10628 ISO/IEC 14617 and ANSI/ISA 5.1 2009 and the implications to neutral data exchange between P&ID’s as to the use of ISO 15926. (First Draft still under construction) From Hindrik Koning Date 20-03-2014 To Fiatech PCA Proteus 2 To Fiatech PCA Instrumentation & Control SIG. To USPI team To ISO SC184/WG3ST General Summary In view of the development of ISO 15926 on the neutral data exchange it is in general strongly advised to reduce the number of all possible standards supported, as inter- operatability requires a unreasonable amount of work at the first time but even more as the standards comes in the five years review and update period. This is specially applicable to the standards referring to the indication of control and instrumentation on P&ID’s as some of the functional codes cannot be mapped two ways in all the different engineering phases. Also many other items are troublesome to maintain, all reasons to look into it. The “recent version” of the ISO 10628 / IEC 14617 and the reconfirmation of the ANSI/ISA 5.1 in 2009(from ANSI/ISA-5.1-1984) on the indication of Instrumentation on P&ID’s made a comparison and positioning of the two documents to the two represented P&ID worlds worthwhile, we also will briefly touch VGB work (European power industry) and we briefly will touch the VGB work as we know it of the KKS, we will exclude the KKS way of designation in this first attempt to master the subject. The ISO went even more and more over to a rather pure functional engineering method and functional recording of it on the P&ID. At the same time we conclude the ANSI/ISA has more materialized or single function oriented way of engineering and the recording thereof. This results in the following picture ISO: FIRC ISA: FT-FI-FR-FCThe translation seem easy but as there are no stringent rules to make the letter combinations (we humans also like to test others with there own inventions) This positions of ISO is in conceptual engineering / FEED and the ISAdetail engineering as in the EPC work.(For basic engineering both can be used to the rules of EPC and principal. In the past the rules for instrument identification where not to thight, a rule based transition between the two system was not possible. A designation system standard specifies how to name an object in the plant, and how to refer to it with relative names on printed documentation like diagrams and data listings. Power plant designation system standards like KKS [27] later RDS PP and IEC 61346 [13] provide three major aspects: There is no need to use them all three in full blown together 1) Function aspect – the function and functional organization of a modeled system 2) Location aspect – the physical locations of subsystems and components 3) Product aspect – the assembly structure of the system implementation. This document will in his first appearance only deal with the Functional aspect as indicated in the upper part of the balloons on P&ID’s
Transcript
7/21/2019 Interoperability Between ISO-IEC Standardization and ANSI-IsA V
The differences between IS0 10628 ISO/IEC 14617 and ANSI/ISA 5.1 2009 andthe impl ications to neutral data exchange between P&ID’s as to the use of ISO15926. (First Draft stil l under construc tion)
From Hindrik Koning
Date 20-03-2014
To Fiatech PCA Proteus 2
To Fiatech PCA Instrumentation & Control SIG.
To USPI team
To ISO SC184/WG3ST General
Summary
In view of the development of ISO 15926 on the neutral data exchange it is in generalstrongly advised to reduce the number of all possible standards supported, as inter-
operatability requires a unreasonable amount of work at the first time but even more as thestandards comes in the five years review and update period.This is specially applicable to the standards referring to the indication of control andinstrumentation on P&ID’s as some of the functional codes cannot be mapped two ways in allthe different engineering phases.
Also many other items are troublesome to maintain, all reasons to look into it.
The “recent version” of the ISO 10628 / IEC 14617 and the reconfirmation of the ANSI/ISA5.1 in 2009(from ANSI/ISA-5.1-1984) on the indication of Instrumentation on P&ID’s made acomparison and positioning of the two documents to the two represented P&ID worldsworthwhile, we also will briefly touch VGB work (European power industry) and we brieflywill touch the VGB work as we know it of the KKS, we will exclude the KKS way ofdesignation in this first attempt to master the subject.
The ISO went even more and more over to a rather pure functional engineering method andfunctional recording of it on the P&ID.
At the same time we conclude the ANSI/ISA has more materialized or single function orientedway of engineering and the recording thereof.This results in the following pictureISO: FIRCISA: FT-FI-FR-FC The translation seem easy but as there are no stringent rules to make the letter combinations(we humans also like to test others with there own inventions) This positions of ISO is in conceptual engineering / FEED and the ISAdetail engineering asin the EPC work.(For basic engineering both can be used to the rules of EPC and principal. Inthe past the rules for instrument identification where not to thight, a rule based transitionbetween the two system was not possible.
A designation system standard specifies how to name an object in the plant, and how to refer
to it with relative names on printed documentation like diagrams and data listings. Powerplant designation system standards like KKS [27] later RDS PP and IEC 61346 [13] providethree major aspects:There is no need to use them all three in full blown t ogether1) Function aspect – the function and functional organization of a modeled system2) Location aspect – the physical locations of subsystems and components3) Product aspect – the assembly structure of the system implementation.
This document will in his first appearance only deal with the Functional aspect asindicated in the upper part of the balloons on P&ID’s
7/21/2019 Interoperability Between ISO-IEC Standardization and ANSI-IsA V
1. Introduction1.0 Contents and Function of the P&ID
1.1 ISA way of working
1.2 ISO way of working
1.3 VGB (KKS) and the Power Industry way of working
2 The letter codes (identification) annotation , the Symbols for instruments on P&ID’sIdentification and Reference Designation
2.2 Conclusion to Identification Characters/Letters2.2.2,The application of the ISO 10628 and ISO 14617 for instrument symbols2.2.1.The application of the ANSI/ISA 5.1 2009.
3 Rule based engineering from functional engineering as in ISO to materialized engineeringmore developed in ANSI/ISA 5.13.1.The conventional Instrumentation Analog (pneumatic electronic) Digital3.2. DCS Shared Displays/ Shared Control3.3.Systems with (mainly) Field busses.3.4.No additional effect of Wireless transmission to the designation
4 Conversion of functional Diagrams to Materialized Diagrams Explanation4.1. Functional and Physical Objects - the big picture(Hans Teijgeler)
4.2. Functional Physical Object vs Materialized Physical Object (,,)
5 Plant break down structures and equipment designations.5.0.A few lines from the OGI Pilot Demo5.1 Standard equipment breakdown structure and coding forcomponents5.2 Technical information about the KKS (RDS-PP )power plant classification system
6. Harmonization work of VBG to ISO Reference Designation System for Power Plants RDS-PP
7. Documentation of the design7.0 Document Management ISA and ISO7.1. Documentation Specific ISA7.2 Documentation ISO/IEC7.3 Documentation Power Industry
Annex 1 The symbols as per ISO 10628, ANSI-ISA 5.1 and ISA
Annex 1.1 The ISO 60617 ISO 14617 all symbols Annex 1.2 The ISA recognizes different types of performers of the functions to be executed,to location and systems
Annex 1.3 Powergeneration to VGB and KKS or RDSPP Annex1.4 Review of Standards Henrik Johansen
A piping and instrumentation diagram/drawing (P&ID) is a diagram in the processindustry which shows the piping of the process flow together with the installed Processequipment, piping (and components) and instrumentation.
1.0 Contents and Function of the P&ID
An example of a P&ID.to ISA mainly I&C is indicated
For processing facilities, it is a pictorial representation of
• Key piping and instrument details• Control and shutdown schemes• Safety and regulatory requirements • Basic start up and operational information
List o f P&ID itemsInstrumentation and designations
• Mechanical equipment with names and numbers• All valves and their identifications• Process piping, sizes and identification• Miscellanea - vents, drains, special fittings, sampling lines, reducers, increasers and
swaggers
• Permanent start-up and flush lines• Flow directions
• Interconnections references• Control inputs and outputs, interlocks• Interfaces for class changes• Computer control system input• Identification of components and subsystems delivered by others
For all systems (methods of generating P&ID’s) to be discussed we have the functionalindication in the upper part of the baloon. The lower part will give a designation, sequencenumber, a break down oriented number or multi coded as , functional, product, location(KKS).
The functional part is way more uniformed than the designation part, that has a lot of differenttheoretical and practical backgrounds
1.1 ISA way of worki ng
= A piping and instrumentation diagram/drawing (P&ID) is defined by the ISA A diagramwhich shows the interconnection of process equipment and the instrumentation used tocontrol the process. In the process industry, a standard set of symbols is used to preparedrawings of processes. The instrument symbols used in these drawings are generally basedon International Society of Automation (ISA) Standard S5. 1.
Not the whole S5.1 standard is applicable on the P&ID, the SAMA diagrams, Signalprocessing function block symbols, Electrical schematic symbols have nothing to do on theP&ID. The title of ANSI/ISA-5.1-2009 Instrumentation Symbols and Identification is notconsistent with the content of the document
1.2 ISO way of working
= The primary schematic drawing used for laying out a process controlinstallation.P&IDs playa significant role in the maintenance and modification of the process that it describes. It iscritical to demonstrate the physical sequence of equipment and systems, as well as howthese systems connect. During the design stage, the diagram also provides the basis for thedevelopment of system control schemes, allowing for further safety and operationalinvestigations, such as a Hazard Analysis and Operability Study commonly pronounced asHAZOP.
The ISO 10628 itself does not contain I&C symbols but refers to IEC 10417 or IEC 60617.ISO 10628-2:2012 defines graphical symbols for the preparation of diagrams for thechemical and petrochemical industry. It is a collective application standard of the ISO14617 series
1.3 VGB (KKS) and the Power Industry way of working
Also here the systems (methods of generating P&ID’s) to be discussed we have thefunctional indication in the upper part of the baloon. The lowerpart will give a designation, sequence number, a break down oriented number or multi codedas , functional, product, location (KKS).
The functional part is in line with the others, designation part as in the KKS or RDS is uniformfor power plants (same equipment in same place) of course less to Oil & Gas and the processindustry.
[1] ISO 10628:1997, Flow diagrams for process plants — General rules
[2] IEC 60050-351, International Electrotechnical Vocabulary — Part 351: Control
technology ( IEC 65/324/CDV:2003)
[3] IEC 61346-2, Industrial systems, installations and equipment and industrial products —
Structuring principles and reference designations — Part 2: Classification of objects
and codes for classes
[4] IEC 81714-3, Design of graphical symbols for use in the technical documentation of
2The letter codes (identification) annotation, the Symbols for instruments onP&ID’sIdentification and Reference Designation
Based on Standard ANSI/ISA S5.1 and ISO 14617-6, the P&ID is used for the identifi-cationof measurements within the process. The identifications consist of up to 5 letters. The firstidentification letter is for the measured value, the second is a modifier, 3rd indicatespassive/readout function, 4th - active/output function, and the 5th is the function modifier.
Letter Column 1 (Measuredvalue)
Column 2 (Modifier)
Column 3 (Readout/Passivefunction)
Column 4 (Output/activefunction)
Column 5 (Functionmodifier)
A Analysis Alarm
B Burner, combustion User choice User choice User choice
CUser's choice (usuallyconductivity)
Control Close
D User's choice (usuallydensity)
Difference Deviation
E Voltage Sensor
F Flow rate Ratio
GUser's choice (usuallygaging/gauging)
Gas Glass/gauge/viewing
H Hand High
I Current Indicate
J Power Scan
K Time, time scheduleTime rate ofchange
Control station
L Level Light Low
M User's choiceMiddle /intermediate
N
User's choice (usually
torque) User choice User choice User choiceO User's choice Orifice Open
P Pressure Point/test connection
Q Quantity Totalize/integrate Totalize/integrate
R Radiation Record Run
S Speed, frequency Safety Switch Stop
T Temperature Transmit
U Multivariable Multifunction Multifunction
VVibration, mechanicalanalysis
Valve or damper
W Weight, force Well or probe
XUser's choice (usuallyon-off valve as XV)
X-axis Accessory devices,unclassified
Unclassified Unclassified
YEvent, state,presence
Y-axis Auxiliary devices
Z Position, dimension Z-axis Actuator, driver orunclassified finalcontrol element
In the letter code, the first letter defining the main process variable of the control function asin functional design (conceptual design or initial part of feed), or of the all the equipment partsin the control loop are the same.The second character the variable modifier are almost the same, except that ISO now thusnot define the Z for a switch in a Safety Instrumented System ???? a comic’
2.2.1.The application of the ANSI/ISA 5.1 2009.
Feedback of ISA 5.1 applications shows the use of many balloons (one balloon for eachapplicable function in a loop). The Standard still confirms to a materialized design, rather thanthe functional design in ISO 10628 and ISO 14617 for instrument symbols
2.2.2,The application of the ISO 10628 and ISO 14617 for ins trument symbols
This standard start purely functional, when all functions are allocated to the P&ID in the one
single balloon much of the letter combination identification is making up
7/21/2019 Interoperability Between ISO-IEC Standardization and ANSI-IsA V
Chemical industry and Power plants (functional engineering)In the two examples below we compare the functional codes as in the upper part of thebaloons for a chemical plant and the same for power plants and we see this part is functionalexact the same (Temperature measurement, indication, control and recording)
The number part (designation) in chemical industryThe number part is different as 401 could read area 4 and sequence nr 01 in the chemicalplant.
Functional engineering and functional codingThe characters in the bottom part of the balloon in the Kraftwerk (powerplant) example is of
different nature, it gives the function of the unit it belongs to LAC35 and gets sequenceBT001 in “all” the power plants.So not the function code of the control loop but of a set offequipment it belongs to
7/21/2019 Interoperability Between ISO-IEC Standardization and ANSI-IsA V
3 Rule based engineering from functional engineering as in ISO or DIN tomaterialized engineering more developed in ANSI/ISA 5.1
Below we see examples from the ISO DIN mechanisms standard and alternatives,The use of +and – for high and low is in the frame we live not required, this tipe of informationis copied to many other applications, we should not use all different alternatives.
7/21/2019 Interoperability Between ISO-IEC Standardization and ANSI-IsA V
But we need the other way around w hen talking from functional engineering tomaterialized engineering, this will be discussed below.The rule based translation from the functional examples (so we talk only about the functioncode as in the upper part of the balloon) above (old DIN 19227 ISO 10628 and ISO10417 ??? to the more materialized ANSI/ ISA is doable
In the table next page below we see a number of letter combinations that are the same as inISO as ISA.
Our problem is only in ISO’s pure functional notation where different functions of a controldiagram/control loop (not a loop diagram) are given in one balloon,
The different functions as we find in a control loop areTransmitter (sensor) alarmsswitches control lers alarms switches actors, as hardware but functionally speaking weshould talk about Transmission, alarming switching controll ing alarming and acting orcorrecting this will appear in one balloon but for interoperatability reasons we should be ableto read it back and forward to other systems, this of course to systems that do basic anddetailing engineering by conversion to the components, performers of those functions
The next question is how is the sequence of the functions (in the main) balloon including thequestion how do we designate the functions to the later added performers. When they will gettheir own “equipment” type balloon
♥
IEC:2008(E)CONTROL TECHNOLOGY –RULES FOR THE DESIGNATION OF MEASURINGINSTRUMENTS1 Scope and objectThis International Standard is applicable to measurement technology. It defines rules for theunambiguous designation of different types of measuring instruments and of measuringinstrument features with the intention of enabling unambiguous technical communication overlanguage 62419boundaries.The scope of this International Standard is
– the adaptation of the designation of measuring instruments and of measuring instrumentfeatures to the state of science by designating them according to the measuring quantityor the measuring task instead of the unit, and
7/21/2019 Interoperability Between ISO-IEC Standardization and ANSI-IsA V
– the adaptation of the designation of measuring instruments and of measuring instrumentfeatures to the terms given in the ISO/IEC Guide 99 (VIM).It is strongly recommended that “…….. measuring instrument” is used as secondarycomponent in compound terms. This is consistent with the objective of standardization,namely uniformity, especially since the meaning of other secondary components, e.g.“indicator”, “gauge”, “meter”, is no more descriptive than that of the standard component inthis context. For exceptions see 4.1 and A.2.The ambiguous secondary component “... sensor” shall not be used. In its place one of thesecondary components “… sensing element”, “... detector”, “... transformer”, “... transducer”,“… transmitter”, “... measuring instrument” or “ ... measuring chain” shall be used, dependingon the task of the functional unit being termed. The definitions for detector (detecting device),transformer, transducer and transmitter are given in IEC 60050-351.
Power plant
ISO/TS 16952-10:2008 contains sector-specific stipulations for structuring principles andreference designation rules on technical products and technical product documentation ofpower plants.
It applies in combination with ISO/TS 16952-1, IEC/PAS 62400 and VGB B 101 for theclassification of systems and objects, and for function-, product- and location-specificdesignation of technical products and their documentation for power plants.
It specifies the designation blocks for the clear identification and localization of the technicalproducts, which are used for their labeling in the plant, for their designation in technicaldocuments and for the designation of the technical documents as well.
3.1. The conventional Instrumentation Analog (pneumatic electronic) Digital
Also in the past we could expect a lot of alarms, alarm inflation was something to recognizedand managed
7/21/2019 Interoperability Between ISO-IEC Standardization and ANSI-IsA V
3.2. DCSShared Displays/ Shared ControlSome instruments are part of a Distributed Control System (DCS) where aspecific controller or indicator can be selected from many others but shown inone location (like a terminal screen)
In the control room in the plant not accessible
7/21/2019 Interoperability Between ISO-IEC Standardization and ANSI-IsA V
Parallel with the introduction of the field bus the associated “smart” transmitters. Nothingspecial, but this type of electronics opens also the way to numerous alarms of different types,transmitted to the operation stations in a central control room.
The detailed Functional Control Diagram shows an increase of the functions
7/21/2019 Interoperability Between ISO-IEC Standardization and ANSI-IsA V
4 Conversion of functional Diagrams to Materialized Diagrams Explanation
- Functional Unit = ClassOfFunctionalObject (the "design")
- Technical Solution = ClassOfInanimatePhysicalObject (the "hardware")
4.1. Functional and Physical Objects - the b ig p icture
Hans Teijgeler / latest revision on 20 April 2013 July 2010, rev. 18 Nov. 2010,rev. 22 Dec. 2010, rev. 11 Feb. 2011, rev. 10 May 2012
Introduction
The activities around the implementation of ISO 15926 are, for the most, bottom-up, which isgood for a quick deployment. This document tries to sketch a scenario for true lifecycleinformation management on the basis of ISO 15926.
The design of a plant is, in principle, not different from the design of a car or airplane. Just thenumber of copies is different. Where a car design is used to produce up to millions of such acar, a plant design usually (not always) results in one plant. Sometimes multiple plants orparts thereof are built according a plant design (e.g. in cases of parallel "trains", and in casesthe design of a process licensor is being used).
The objects handled in the design process are classes, resulting in a car class (e.g.Mercedes 300SEL) or airplane class (e.g. Boeing 747), with numerous variant classes, due tocustomer requirements.
All components of such a design are classes as well.
Process design
The design of a plant starts with process design. In essence this is ClassOfActivity-centric,with instances of ClassOfStream*) as input and output, and instances ofClassOfFunctionalObject as the participants whose function, once materialized, it isto execute the activity to the stream(s).
*) Not a Part 2 entity type, shall be in the RDL as a subclass ofClassOfInanimatePhysicalObject.
This functional process design results in documents like a PFD (Process Flow Diagram) andHeat and Material Balances. Derived from that the "Process Conditions" for equipment, piping,and instrumentation are produced.
Functional and Plant Design
Although disputed by some, the concept of the so-called Hamburger Model, designed byWimGielingh et al in 1988, explains this:
This can be applied at all composition levels, from the entire plant down to components.
If you read:
- Functional Unit = ClassOfFunctionalObject (the "design")
- Technical Solution = ClassOfInanimatePhysicalObject (the "hardware")
You’re pretty close to understanding the concept.
Now the engineering groups (Process, Mechanical, Control Systems, Electrical, and Piping)translate this process design into P&IDs (Piping and Instrument Diagrams) and specificationsfor all plant items.
If you look at the specification/data sheet for P101, you see things like:• service description (what does it do in the context of the plant?)• functional requirements, for process equipment often expressed in term of process
conditions• physical requirements, such as materials, pressure and temperature ratings, corrosion
allowances, etc• protection against hazards (weather, explosion, fire, human exposure, etc)• connections (process, electrical)• testing requirements• references to other documents and standards• etc
All of them are criteria for membership of the class P101.
Most of these requirements are based on the place and role that P101 has in the plant design.If the process design and/or plant design changes, we may need a different P101 class, withits definition recorded in a revised specification/data sheet.
And if a member of the P101 class had already been installed, we may need another pump. Ifthe existing installed pump complies with those new criteria for membership, it can stay in situ,if not we have to obtain and install another PhysicalObject that does comply with therevised P101 class.
4.2. Functional Physical Object vs. Materialized Physical Object
Hans Teijgeler / latest revision on 20 Apr il 2013
Detailed Engineering & Plant DesignIn this phase of the project the requirements, as defined by the Process Engineers, are thebasis of so-called Piping & Instrument Diagrams (P&IDs). These schematic diagrams depictthe required networks of piping and instrumentation of the plant to be built. The equipmentand instrumentation items, shown with symbols, are interconnected.
Next the technical disciplines work on their detailed engineering, such as:• Electrical One-line Diagrams for power generation and distribution• Logic Diagams• Instrument Loop Diagrams• P&IDs for equipment auxiliary systems (e.g. lube and seal oil systems)• the Piping Group starts building their 3D models, thereby detailing the geometry of the
plant and the piping connections.In this phase of the project we need to be able to generate and collect data about all thesethings, but there is nothing tangible yet. We deal here with what ISO 15926 calls"FunctionalPhysicalObject"s. SAP calls them Function Places. The definition in ISO 15926-2 for them is:
"A FunctionalPhysicalObject is a PhysicalObject that has functional, rather than material,continuity as its basis for identity".
Functional physical objects ("FPO") often get a tag number, or equipment number, or linenumber, but by far not all FPOs get one (e.g. an elbow in a (pipe)line normally doesn't getone, unless we need to store information that is specifically about that elbow, such as amaterial certificate).
As can be seen on above diagram, a particular FPO is a member of aClassOfFunctionalObject. The latter is a very generic class, such as PUMP FUNCTION. Thedefinition of ClassOfFunctionalObject is:
"A ClassOfFunctionalObject is a ClassOfArrangedIndividual that indicates the functionor purpose of an object." EXAMPLE Pump, valve, and car are examples of ClassOfFunctionalObject. Particularmodels of pump, valve, car, etc are instances of ClassOfInanimatePhysicalObject thatare specializations of these instances of ClassOfFunctionalObject.
The role of Specification ("data sheet')
Let us focus now on our proverbial pump P-101. Its story is typical for most equipment andother hardware.
The Mechanical Engineers write a Pump Specification, based on a set of process data thathas been derived from the process design done by the Process Engineers. That specificationalso covers all sorts of requirements by the authorities and the future plant owner (e.g.required overcapacity). A specification is the definition of a ClassOfInanimatePhysicalObjectof which the particular FPO is a member.
Because that FPO is already a member of the instance of ClassOfFunctionalObject "PUMPFUNCTION", the above ClassOfInanimatePhysicalObject shall be a subclass of "PUMPFUNCTION".
A specification is sent to, say, three suppliers with a request for quotation (see below). Itdetails all requirements for the piece of hardware that we want to buy.
The role of the P&ID
The pump symbol by itself does not reveal much news. It is the place and function of thatpump in the context of the plant network that tells what the role of that pump really is.
The fact that a P&ID (co-)defines a ClassOfInanimatePhysicalObject is because you canbuild more than one plant from the same P&ID. Think about parallel trains in a plant, or aboutP&IDs of process licensors.
Having said that, nothing stops a software supplier to generate FPOs on the basis of theP&ID. That is very useful when defining the connectivity of all FPOs. Manually that isundoable, and certainly not maintainable.
Procurement
The yellow part of above diagram deals with the physical world. Suppliers can specify theirinstances of ClassOfInanimatePhysicalObject as entries in their catalogs. Next to that theyhave other documentation that relates to these classes.
A task of the Procurement group, together with the related technical disciplines, is to make aselection of the offered goods (and services), by comparing them with the requirements asset forth for the FPOs. That is not always easy and certainly hard to automate.
But once the decision has been made that, in this case, the offered pump meets thoserequirements, and then this can be put on record by creating aClassOfInanimatePhysicalObject that is a class-of-temporal-part of the offeredClassOfInanimatePhysicalObject AND of the requirements ClassOfInanimatePhysicalObject.This is in fact a class of function place.
This should be done not only for the successful bidder, but also for any other bidder, if soapplicable. By doing so it will be easy to find an alternative in case of problems with thesuccessful bidder/supplier.
7/21/2019 Interoperability Between ISO-IEC Standardization and ANSI-IsA V
5 Plant break down structures and equipment designations.
A purely logicalreasoningis a Standard equipment breakdown structure is equal equipmentdesignations.
5.0. A few lines from the OGI Pilot Demo
TCTJL's role as the lead EPC for the Downstream OGI Pilot, involves developing andmanaging the Intelligent P&ID’s(SP PID) and associated Engineering reference data set(Equipment, Valve, Instrument lists, Line Designation Table and P&ID Legend & Symboldrawings etc.) making the data available in XML format utilizing the new SmartPlant PID ISO15926 Export utility released by Intergraph in April 2012.
Watching the demo you will see a P&ID go from three organizations, representing 3 EPC
contractors, get bent and spindled in the middle, and finally to an IBM application that does --something(?)Here we will show you where the information ends up and why this is revolutionary AVEVA many P&ID vendors participating. "Shows how interoperable we all are" AVEVA acting as second EPC. This is like a project with multiple contractors. Multiple formatsof P&ID but what we want all the data to end up in the proper place.Proteus based on XMpLant 3.3.3. Part of Fiatech project years agoBentley part. Bentley provided the same information as from INGR and AVEVA, but in adifferent format.Comes in two parts. Part 8 OWL and ecXML.UniSAOWL. items, identifiers, properties, equipment types, breakdown structure.ecXML. topology, piping connections, flow direction, geometry.
It seems this subject requires more thoughts as it is one of the carriers of ISO 15926
5.1 Standard equipment breakdown structure and coding forcomponents
EPRI has developed a standard equipment breakdown structure and coding forcomponentsin combustion turbine or combined-cycle generation units. This standardized listing andaccompanying diskette can be used for indexing equipment history files, as a basis for amore detailed equipment capitalization, or to facilitate information sharing on equipmentreliability problems. Overall, this EPRI project establishes the basis for accurately monitoringthe availability and reliability of combined-cycle plants at all equipment levels.Background
Across the electric power generation industry, there exist multiple sets of gas turbineequipment breakdown structures and codes. These codes, however, are either manufacturer
specific (no generic) or have insufficient structural detail to meet many utility needs. Forexample, the Federal Energy Regulatory Commission furnishes a list of equipment that canbe capitalized in terms of taxes, but it lists only major components. In another example, thereseems to be no consistency in the way equipment is defined for indexing plant maintenancehistory files, thus making it difficult to share experiences from plant to plant. The purpose ofthis EPRI research, therefore, was to devise a standard equipment breakdown structure andcoding with sufficient detail to meet such needs and to form the basis for a standard.ObjectiveTo develop and publish a standard equipment breakdown structure and coding for gasturbine and combined-cycle generation equipment.
Approach
7/21/2019 Interoperability Between ISO-IEC Standardization and ANSI-IsA V
The project team was comprised of gas turbine design specialists as well as senior gasturbine and combined-cycle plant operations and maintenance management personnel. Theteam determined that a standard equipment breakdown structure and coding should featurethe following characteristics: (1) sufficient but not excessive detail to meet utility plant needs;(2) generic information that covers all manufacturers' equipment; (3) a hierarchical designwith respect to equipment function to facilitate reliability analysis and reporting; and (4)rationalized information with respect to other equipment coding systems such as theEuropean coding standard--Power Plant Designation System (KKS). Major equipmentmanufacturers reviewed the coding structure and nomenclature to ensure completeness andaccuracy.ResultsEPRI's standard equipment breakdown structure and coding provides an approach foraccurately monitoring the impact of a component failure, maintenance action, or repair andreplacement strategy on plant availability. This listing also provides a basis for accumulatinghistorical operational and failure information that can be used to assess equipment problems
from a reliability, availability, and maintainability perspective.The standard equipment breakdown structure and coding has been adopted by theOperational Reliability Analysis Program (ORAP), which is an industry wide reliabilitydatabase on gas turbine and combined-cycle equipment. Over the past year, AnchorageMunicipal Light and Power (AML&P) and Florida Power and Light (FP&L) have used thestructure and coding for reporting gas turbine and combined-cycle reliability data. AML&Pused the listing as a basis for a more detailed capitalization of its gas turbine equipment anddocumented increased income of $1.8 million, in part, due to the new coding (EPRI InnovatorIN-103307). FP&L used the structure and coding to index its plant maintenance history files.Two manufacturers have adopted the coding internally for describing their own equipmentbreakdown structures.EPRI PerspectiveEPRI has developed an equipment breakdown structure and coding to standardize andfacilitate data collection and reporting. The hierarchical structure is flexible, allowing forchanges such as new emissions controls and more complex combined-cycle power plants. Inall, the listing provides a uniform, consistent organization of outage and maintenance eventsreported directly by users of the various equipment. The primary objective is to help powerplant personnel accurately attribute frequency of events, event durations, and correctiveactions to specific plant components. Tests have shown that the standard equipmentbreakdown structure and coding is effective and easy to use. EPRI recommends itsapplication throughout the industry to improve plant-to-plant and utility-manufacturercommunications. Establishing the equipment breakdown structure and coding as an industrywide standard is a key goal.
5.2 Technical information about the KKS power plant classification system
The KKS power plant classification system is a system for identifying plants, systems,subsystems, equipment items, electrical and I&C cabinets, and buildings and rooms,depending on viewpoints of the plant operating companies. Application of the KKS
classification system is specified and prescribed by the guidelines of VGB PowerTeche.V.
Note:
Not only the KKS power plant classification system can do so but any coherent system will do for Oil Gas and theProcess Industry, as the content (all the troublesome work) of the more uniform Power Industry is not to be copied
A designation according to the KKS classification system comprises a 15 to 17-charactercombination of letters and numerals. The letters are usually used for classification of thesystems and units. The numerals are usually used for numbering.
7/21/2019 Interoperability Between ISO-IEC Standardization and ANSI-IsA V
The KKS designation has an invariable structure based on breakdown levels. The level ofdetail of the designation increases from left to right. The structure of the breakdown levels isalphanumeric. In the explanation below, A stands for letters and N for numerals. A blank isinserted between the breakdown levels. In the point of installation designation, the breakdownsymbol "." (period) is inserted between breakdown levels 1 and 2.
Breakdown level 0 - Overall plant
The first breakdown level refers to the overall plant and merely numbers it. It consists of anumeral and a letter. This identifies the generating unit
Breakdown level 1 – Function or system designation
The second breakdown level denotes functions, systems, or subsystems of a generating unit.
It consists of 3 letters and 2 numerals with an optional leading numeral. The letters aredefined according to a function key for the systems in generating units. The first letter (fromthe left) denotes the main systems (so-called main groups), the following letters then denotethe further subdivision into subgroups. The two numerals that follow are counters and arereferred to as FN numbering.
Breakdown level 2 – Equipment uni t designation
The third breakdown level refers to an equipment unit in the subgroup. It consists of 2 lettersand 3 numerals. The letters are assigned according to a defined equipment unit key for powerplants. The first letter denotes a group of equipment units; the following letter then denotesthe further subdivision into subgroups. The numerals that follow are counters for numbering.
Breakdown level 3 - Component / signal designation
The fourth breakdown level denotes an equipment item (component) or signal designation inthe equipment unit. It consists of 2 letters and 2 numerals. The letters are assigned accordingto a defined component key. The first letter denotes a group of equipment items; the followingletter then denotes the further subdivision into subgroups. The numerals that follow arecounters for numbering. In the case of a signal designation, defined assignment is possible,e.g. XB01 is the “open” feedback signal of a valve actuator. XB51 is the “not open” feedbacksignal of the same actuator; XB02 is the "CLOSED" feedback signal and therefore XB52 isthe "not CLOSED" feedback signal.
Example of application of the power pl ant classification system
7/21/2019 Interoperability Between ISO-IEC Standardization and ANSI-IsA V
6. Harmonization work of VBGto ISOReference Designation System for PowerPlants RDS-PP
The technical standard is based on the basic principles of international standards and takesinto account nearly all the KKS structures. Around 90% of the code letters in the KKS functionkey were transferred to the new system key. KKS aggregate and equipment key will bereplaced in the new reference designation system by a standard in which the code letters arestandardized globally for specialist areas and sectors. These code letters do not unfortunatelyalways match the KKS-specifications. There are tools available for comparing RDS-PP toKKS and for performing the required conversion from KKS to RDS-PP. These tools supportthe transfer of the KKS function key to the RDS-PP system key and from the aggregate andequipment key to the code letters in the international standard.The article depicts the development of the new reference designation system from the pointofview of standardization, describes the main features, mentions offers of support by the VGB“Reference designation and plant documentation” working panel and provides
recommendations for future use.
7/21/2019 Interoperability Between ISO-IEC Standardization and ANSI-IsA V
Ar trA Document Management System A key requirement for a 3D Plant Asset Management (PLM) and Asset Lifecycle Management(ALM) system is the ability to link electronic documentation to CAD or BIM models, allowingO&M staff to quickly access and maintain all the information pertaining to the building orfacility. ArtrA Librarian is an electronic Document Management System (EDMS) for processplant and Building Information Models (BIMs). Its unique structure allows it to be used in amanner that suits the multiple disciplines and engineering processes that are used duringdesign, construction, installation and commissioning. ArtrA Librarian EDMS has beenspecifically developed to run with 3D CAD or BIM systems for the efficient handover of projectinformation.
Ar trA Librar ian Librarian is a complete document management system and provides sophisticated but easyto use tools for managing and linking documents to a model. Librarian uses ArtrA tags andCAD attributes in 3D process plant & BIMs to create document links with its SQL database.
ArtrA manages documents by their properties (author, date etc.), categories (O&M,installation, isometric, weld report, defects, etc.) and disciplines (piping, instrumentation,architectural, structural, etc.) and is ideally suited to the process planning and AEC documentcontrol environment.
7/21/2019 Interoperability Between ISO-IEC Standardization and ANSI-IsA V
The Instrument List or Instrument Index is a list of the data related to aFacility’s control system components and, possibly, their functions. InstrumentIndexes are organized using the alphanumeric tag numbers of the controlsystem devices. They reference the various documents that contain the informationneeded to define the total installation. Instrument Indexes are discussedin Chapter 3. The terms list and index are essentially interchangeable.10 Instrumentation and Control Systems Documentation
Figure I-3: Typical Instrument Identi fication/Tag Number - 10-PDAL-01A-1A1From ANSI/ISA-5.1-2009
The general term database is also used. It has many definitions in the ISA
Dictionary. The most simple is: any body of information.The control systems design group personnel place tag numbers on the P&IDand enter them into the Instrument List or database for tracking. This is donefor control purposes because, on a large project, there may be many P&IDs—perhaps one hundred or more—plus thousands of tag-marked devices. Sinceeach device serves a specific function, all devices’ status must be tracked untilthey are installed during construction, their operation has been verified duringcommissioning, and the plant has been accepted by the owner. Furthermore,each device must be uniquely tracked so its configuration and measurement orcontrol range are known, and many facilities capture the devices’ maintenance
7/21/2019 Interoperability Between ISO-IEC Standardization and ANSI-IsA V
Specification FormsSpecification Forms (or Instrument Data Sheets) define each tag-numberedinstrument with sufficient detail that a supplier can quote and eventually furnishthe device. For a typical Specification Form, see Chapter 4, Figures 4-4,4-5 and 4-6. More importantly, the Specification Form retains the critical informationneeded by control system technicians, such as the manufacturer, modelnumber, range, power requirements and other features needed to define thedevice for maintenance.
After tag numbers are entered on the Instrument Index or List, the controlsystem design group starts a Specification Form for each tag-marked item.Developing these Specification Forms can be a major part of the controlsystem design group’s effort. Specification Forms must be completed to securebids from suitable suppliers, to purchase the items from the successful bidders,
and to generate a permanent record of what was purchased.
Binary Logic Systems
There usually is some on-off or binary or discrete control in a continuous processplant control system. Discrete control is defined in the ISA Dictionary as on-offcontrol. P&ID’s are excellent documents to define continuous control systems.Other methods are needed to define on/off control. ISA-5.1 and Chapter 6include descriptions of many of these as does ANSI/ISA-5.06.01-2007 FunctionalRequirements Documentation for Control Software Applications.
As the design progresses, the need to define on-off control will become evident.For instance, on a pulp and paper mill project, it may be necessary to isolate apump discharge to prevent pulp stock from dewatering in the pipe if the pumpis shut down. An on-off valve is added to provide the isolation, but it is necessaryIntroduction 11to document why that device was added and what it is supposed to do. Sincethis on-off control may affect many design groups, it is important to define itas early and as accurately as possible.
Loop Diagrams A Loop Diagram is a schematic representation of a control loop, which in itsidealized form is comprised of a sensing element (often called a transmitter), acontrol component (perhaps part of a shared display, shared control system),and a final control element (usually a control valve or a variable speed driveon a motor). It depicts the process connections, the instrumentation interconnection,connections to the power sources, and the signal transmissionmethods, whether pneumatic, electronic, digital or a combination thereof. Fora typical Loop Diagram see Chapter 7, Figure 7-7.Finally, when all connection details are known and electrical design has progressed
to the point that wiring connection points are known, the control systemsdesign group can develop Loop Diagrams. These diagrams show all theinformation needed to install and check out a loop. Because these diagramsmay repeat information that the piping and electrical design teams includedon their drawings, it is critically important that the control systems designgroup coordinates closely with other disciplines.
Installation DetailsInstallation Details are used to show how the instruments are interconnectedand connected to the process. They are also a primary coordination toolbetween disciplines. The details provide the means used to mount and support
7/21/2019 Interoperability Between ISO-IEC Standardization and ANSI-IsA V
the devices and the specific requirements for properly connecting themto the process. Installation Details are discussed in Chapter 8.The control systems design group develops Installation Details based on thespecific requirements of the devices it has specified, along with any facilityowner-driven requirements. The installation requirements needed for goodoperation and control are established by the instrument suppliers, by variousindustry groups and by the owners themselves. These requirements are thendocumented in the Installation Details. These details may be developed forthe project, for the specific site, or possibly by the owner’s corporate entity.
Location PlansLocation Plans are orthographic views of the facility or process area, drawn toscale, showing the locations of field mounted transmitters and control valves.
7.2 Documentation ISO/IEC (Corrigendum to IEC 61175 edition 2)
A method for presentation of the concatenations of reference designation sets has beenintroduced in IEC 61082-1 edition 2. This form of presentation have been used, in the samestandard, also for concatenation of signal names to a reference designation (see IEC 61082-1 item 7.1.8 and figure 52). The method was introduced to IEC 61082-1 after IEC 61175edition 2 was published and therefore the method is not mentioned or used in this standard.The method, described in IEC 61082-1, of presenting concatenation of a signal name to thereference designation of the signal domain shown as a boundary frame in a circuit diagram isrecommended to be used. Therefore the reader of this standard shall consider the referencedesignations shown in relevant figures (see list below) to be written as shown in figure 52 ofIEC 61082-1 edition 2.Example: In figure 2b) of this standard shall the reference designation =MA1 be understood
as written =MA1; (a semicolon added after the designation).This corrigendum is applicable for the following figures: Figure 2b), Figure 10b), Figure 13,Figure 14, Figure 20, Figure 21 and Figure B.3.This draft corrigendum was prepared but CO did not accept to deal with the changes as acorrigendum. CO instead proposed an amendment, but that has so far not been prepared.Considering that the Maintenance Result Date for IEC 61175 is already 2011, a MCR will bedistributed suggesting a complete revision.This plenary meeting has also another issue to consider. The convener for MT 17 will in thebeginning of 2011 retire on a pension and therefore a new convener is needed.
Diagrams, such as circuit diagrams and connection diagrams, for example for test circuits,shall be prepared in accordance with IEC 61082-1. Graphical symbols used in schematicdiagrams shall be in accordance with IEC 60617 and ISO 14617. Reference designations andsignal designations shall be in accordance with IEC 81346 and IEC 61175 respectively.
7.3 Documentation Power Industry As already explained in the chapters above, the RDS-PP consists of severalcomponentswhich are summed up again below, along with information on their status and therespective reference documents:DIN 6779-10 Structuring principles for technical products and technical productdocumentation - Part 10: Power plants- most important national standard, replaces KKS guideline
7/21/2019 Interoperability Between ISO-IEC Standardization and ANSI-IsA V
(Beuth-Verlag)ISO/TS 16952-10 Technical product documentation – Referencedesignation system –Part 10:Power Plants- most important international standard, replaces KKS guideline,to be published inQ1/2008(Beuth-Verlag)DIN ISO/TS 16952-10 Kennzeichnungssystematik für technische Produkte undtechnischeProduktdokumentation – Teil 10: Kraftwerke- German version of ISO/TS 16952-10to be published in Q1/2008, replaces DIN 6779-10(Beuth-Verlag)DIN 6779-2 Structuring principles for technical products and technical productdocumentation - Part 2: Letter codes - Main classes and subclassesof objects according to their purpose or task(Beuth-Verlag)IEC/PAS 62400: Structuring principles for technical products and technical productdocumentation - Letter codes - Main classes and subclasses ofobjects according to their purpose and task(Beuth-Verlag)
VGB-B 101 RDS-PP Reference Designation System for Power Plants (systemkey),English version to be published in November 2007(VGB PowerTech Service GmbH)VGB-B 116 RDS-PP Reference Designation System for Power Plants, Applicationexplanations,to be published in December 2007 (German version) and April 2008(English version)(VGB PowerTech Service GmbH)Software-Tool Supplementary information and an efficient way of experiencing theRDS-PP and the interrelations in designation and documentation byselected examples,to be published in April 2008(VGB PowerTech Service GmbH)
7/21/2019 Interoperability Between ISO-IEC Standardization and ANSI-IsA V
