EN 62424-2016 en Representation of process control engineering - Requests in P&I diagrams and data exchange between P&ID tools and PCE-CAE tools.pdf

《EN 62424-2016 en Representation of process control engineering - Requests in P&I diagrams and data exchange between P&ID tools and PCE-CAE tools.pdf》由会员分享，可在线阅读，更多相关《EN 62424-2016 en Representation of process control engineering - Requests in P&I diagrams and data exchange between P&ID tools and PCE-CAE tools.pdf（172页珍藏版）》请在麦多课文档分享上搜索。

1、Representation of processcontrol engineering Requests in P 35.240.50Compliance with a British Standard cannot confer immunity fromlegal obligations.This British Standard was published under the authority of theStandards Policy and Strategy Committee on 31 January 2017.Amendments/corrigenda issued si

2、nce publicationDate Text affectedBRITISH STANDARDBS EN 62424:2016EUROPEAN STANDARD NORME EUROPENNE EUROPISCHE NORM EN 62424 November 2016 ICS 25.040.40; 35.240.50 Supersedes EN 62424:2009 English Version Representation of process control engineering - Requests in P representation of transmitters wit

3、h integrated local display (if not otherwise defined in a specification of the field device) 142 Figure B.17 Local pressure indication, CCR pressure indication, alarms and switches . 142 Figure B.18 CCR pressure indication, high and low alarm, safety relevant switch action on on/off valve 143 Figure

4、 B.19 Switched valve with on/off indication and switching action, safety relevant switched valve . 143 Figure B.20 Pressure restriction . 143 Figure B.21 Flow restriction 143 Figure B.22 PT compensated flow control, safety-relevant pressure switch (two out of three (2oo3) shutdown), switched control

5、 valve with on/off indication and switching action at open position 144 Figure B.23 CCR temperature control, additional manual switch actions from CCR with indication and local control panel . 144 Figure B.24 Motor typical, local on/off control, CCR off control, current, fault with alarm and running

6、 indication . 145 Figure B.25 Multivariable controller 145 Figure B.26 On/off valve with position indication . 146 Figure B.27 On/off valve with safety relevant switch and position indication 146 Figure B.28 Level control with continuous controller . 146 Figure B.29 Level control with on/off switch

7、146 Figure B.30 Cascade control for temperature as control input, flow control as follow-up controller . 147 Figure B.31 Safety directed high control to a subsequent valve, manual control for reset function and manual control for manual/automatic switch of the valve, valve with open/close indication

8、 and safety-relevant switch to subsequent valve 147 Figure B.32 Flow control in CCR 147 Figure B.33 Temperature control with high alarm and high switch . 148 Figure B.34 Manual control from CCR 148 Figure B.35 Flow measurement with display and alarms in CCR, high high switch on process control funct

9、ion and switch on/off valve 148 Figure B.36 Local P-/F-/T-/S- control without auxiliary power (stand-alone) . 148 Figure C.1 Full XML text of the CAEX Schema file “CAEX_ClassModel_V.3.0.xsd” 154 Figure D.1 Attribute type library with additional PCE request related attributes 155 Figure D.2 XML code

10、of the Attribute type library 156 Figure D.3 Example of CAEX interface library . 156 Figure D.4 XML code of the example CAEX interface library . 156 Figure D.5 Example CAEX role library illustrating the modeling of a PCE request role referencing PCE request related attributes 157 Figure D.6 XML code

11、 for the example CAEX role library . 158 Figure D.7 Example P any IEC National Committee interested in the subject dealt with may participate in this preparatory work. International, governmental and non-governmental organizations liaising with the IEC also participate in this preparation. IEC colla

12、borates closely with the International Organization for Standardization (ISO) in accordance with conditions determined by agreement between the two organizations. 2) The formal decisions or agreements of IEC on technical matters express, as nearly as possible, an international consensus of opinion o

13、n the relevant subjects since each technical committee has representation from all interested IEC National Committees. 3) IEC Publications have the form of recommendations for international use and are accepted by IEC National Committees in that sense. While all reasonable efforts are made to ensure

14、 that the technical content of IEC Publications is accurate, IEC cannot be held responsible for the way in which they are used or for any misinterpretation by any end user. 4) In order to promote international uniformity, IEC National Committees undertake to apply IEC Publications transparently to t

15、he maximum extent possible in their national and regional publications. Any divergence between any IEC Publication and the corresponding national or regional publication shall be clearly indicated in the latter. 5) IEC itself does not provide any attestation of conformity. Independent certification

16、bodies provide conformity assessment services and, in some areas, access to IEC marks of conformity. IEC is not responsible for any services carried out by independent certification bodies. 6) All users should ensure that they have the latest edition of this publication. 7) No liability shall attach

17、 to IEC or its directors, employees, servants or agents including individual experts and members of its technical committees and IEC National Committees for any personal injury, property damage or other damage of any nature whatsoever, whether direct or indirect, or for costs (including legal fees)

18、and expenses arising out of the publication, use of, or reliance upon, this IEC Publication or any other IEC Publications. 8) Attention is drawn to the Normative references cited in this publication. Use of the referenced publications is indispensable for the correct application of this publication.

19、 9) Attention is drawn to the possibility that some of the elements of this IEC Publication may be the subject of patent rights. IEC shall not be held responsible for identifying any or all such patent rights. International Standard IEC 62424 has been prepared by IEC technical committee 65: Industri

20、al-process measurement, control and automation. This second edition cancels and replaces the first edition published in 2008. This edition constitutes a technical revision. This second edition is a compatible extension of the first edition. The main changes and extensions are detailed in Annex E and

21、 are summarized below: a) updated definitions and new definitions; b) identification replaced with reference designation; c) updated PCE categories and process functions; d) CAEX version 3.0, introduction of: native multiple role support; BS EN 62424:2016IEC 62424:2016 IEC 2016 9 nested interfaces;

22、life cycle meta information; a separate Attribute library; updated examples; e) updated electronic data model of the PCE request: new normative attribute library for basic PCE request attributes; new informative extended attribute library for further PCE request attributes; new informative electroni

23、c data model for the PCE request. The text of this standard is based on the following documents: CDV Report on voting 65/544/CDV 65/560B/RVC Full information on the voting for the approval of this standard can be found in the report on voting indicated in the above table. This publication has been d

24、rafted in accordance with the ISO/IEC Directives, Part 2. The committee has decided that the contents of this publication will remain unchanged until the stability date indicated on the IEC website under “http:/webstore.iec.ch“ in the data related to the specific publication. At this date, the publi

25、cation will be reconfirmed, withdrawn, replaced by a revised edition, or amended. IMPORTANT The colour inside logo on the cover page of this publication indicates that it contains colours which are considered to be useful for the correct understanding of its contents. Users should therefore print th

26、is document using a colour printer. BS EN 62424:2016 10 IEC 62424:2016 IEC 2016 INTRODUCTION Efficient process engineering requires highly sophisticated tools for the different needs of the involved work processes and departments. These engineering tools are normally specialized in Process Design (P

27、D), in Process Control Engineering (PCE), etc. Therefore, a working interoperability is essential to optimize the engineering process in total. Thus, the definition of a harmonized interface and data management is a core task to ensure a smooth workflow during the whole project and to guarantee data

28、 consistency in the different tools. This standard defines procedures and specifications for the exchange of PCE relevant data provided by the Piping and Instrumentation Diagram (P it shall not allow unguided automatic changes. The configurable checking step shall include functionality for automatic

29、 or manual acceptance of data changes, allowing single decisions up to bulk data management. All changes in the proprietary database and all discovered data inconsistencies shall be reported by the import application. The generation of the report shall be configurable. The import/export application

30、has to assure that the intersection of the different databases contains the same information, and that additional division specific data is handled in a consistent way. Data manipulation by a project division is an ongoing process during the whole project and beyond it. Thus the creation, changing a

31、nd deletion of data shall be possible during the life-cycle of the plant. CAEX databases have to be consistent. This requires a consistency check before exporting the data. This procedure has to be followed after a successful data manipulation in a P 2) mandatory fields being filled in; 3) correct u

32、se of numbering system of the PCE requests. Inconsistent data shall not be exported. b) Generate PCE relevant information; c) Check for changed information in comparison with previously stored data in the neutral database; d) Renaming of PCE request shall be supported by the export functionality; e)

33、 Perform data export from proprietary into neutral database: 1) For example, if the PCE request has been changed, the old PCE request within the neutral database has to be deleted and the new one shall be exported from the proprietary database into the neutral database. The old PCE request informati

34、on shall be stored in a backup storage system; BS EN 62424:2016IEC 62424:2016 IEC 2016 19 2) Other changes shall be performed with the existing object. f) Generate reports after each data exchange: For example, new PCE requests list, missing PCE requests list, changed PCE requests list, deleted PCE

35、requests list, problems and error list. Data import from neutral database into the target database shall comprise the following activities. g) Generate PCE relevant information from neutral database; h) Check for changed information by comparing the neutral database with the target database; i) Perf

36、orm data import from the neutral into the proprietary database; j) Renaming of PCE request shall be supported by the import functionality; k) Generate reports after each data exchange: 1) For example, error lists; 2) inconsistencies due to imported data shall be detected by the target application du

37、ring the import process and are not considered within this standard. 6 Representation of PCE requests in a P b) the graphical representation of PCE requests in a P c) the type of functional connection between the PCE requests: the control functions; d) the graphical representation of signals in a P&

38、ID. In addition a reference designation system used for PCE requests in a P&ID shall be specified (see 6.3.5). Detailed information on complex control functions shall not be part of the P&ID. Therefore, additional documentation (e.g. control narratives, function charts) has to be prepared to define

39、the required functionality. A control function shall also be individually identified and shall be represented on the P&ID. 6.3 Requirements for the reference designation and representation of PCE requests 6.3.1 General Each PCE request shall be graphically represented by a bubble, which collects all

40、 information about the functional requirements. Three data fields inside and ten data fields outside the bubble are defined to hold all the information of a PCE request (see Figure 3). For detailed information see 6.3.3 to 6.3.9. US xxxx.3 AH SHH AH SHH YS xxxx.4 AL OH PCE loop xxxx (optional) PCE r

41、equest PCE control function a PCE request FI xxxx.2 TI xxxx.1 PCE request IEC BS EN 62424:2016IEC 62424:2016 IEC 2016 21 Figure 3 General representation of a PCE-Request in a P&ID As stated before, only the PCE functionality shall be depicted on the P&ID, not the PCE implementation. In exceptional c

42、ases however, there might be constellations where the presentation of detailed realization information is inevitable. For example, in the case of a multi-sensing element which means an instrument that produces measurements for different categories, every category shall be represented by its own bubb

43、le. The bubbles are stacked up, as shown in Figure 4. Figure 4 Multi-sensing element In all cases where the PCE request is connected to the equipment or pipe, this shall be shown by a full line, connecting the bubble with the equipment or pipe. 6.3.2 Types of lines Signal lines are used to illustrat

44、e the functional relationship between PCE requests. A signal line shall be depicted as a dashed line with an arrow to indicate the information flow. Source of information flow shall be a bubble of a PCE control function or request or switching action consisting of the six fields on the right side of

45、 the bubble. The sink of information flow shall be a bubble of a PCE request or a control function. Process connections shall be depicted by a solid line without a direction. Multi-sensing elements instruments with only one process connection shall have an extra bubble for each category and only one

46、 process connection. 6.3.3 Displaying the location of the operator interface Each PCE request is graphically represented by a bubble. This standard distinguishes the location of the operator interface between a local interface, a local control panel and a central control room. The location does not

47、reflect any realization in systems. PCE category and function PCE Reference PU Vendor Typical identification Device information ZHHH AH SHH AL ALL SLLL Safety relevant GMP Quality relevant (SIL3) IEC DI xxxx FI xxxx PI xxxx IEC BS EN 62424:2016 22 IEC 62424:2016 IEC 2016 A local interface shall be r

48、epresented as shown in Figure 5. It could be for example a pressure gauge. Figure 5 Local interface Operator action/information on a local control panel shall be represented as shown in Figure 6. Figure 6 Manually operated switch in local control panel Remote requests operated in a central control r

49、oom shall be represented as shown in Figure 7. Figure 7 Pressure indication in central control room by a central control system It is recommended to simplify the presentation of PCE for combined local interface and indication in central control room by only one bubble as shown in Figure 7. For this case it is required to have a note in the definitions of a P&ID. 6.3.4 PCE categories and processing functions 6.3.4.1 Indication of PCE categories and process