IEC-PAS-62424-2005.pdf

PUBLICLY AVAILABLE SPECIFICATION IEC PAS 62424 Pre-Standard First edition 2005-06 Representation of process control engineering requests in 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 collaborates 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 on 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 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 the 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 provides no marking procedure to indicate its approval and cannot be rendered responsible for any equipment declared to be in conformity with an IEC Publication. 6) All users should ensure that they have the latest edition of this publication. 7) No liability shall attach 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) 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. 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. A PAS is a technical specification not fulfilling the requirements for a standard, but made available to the public. IEC-PAS 62424 has been processed by IEC technical committee 65: Industrial-process measurement and control. The text of this PAS is based on the following document: This PAS was approved for publication by the P-members of the committee concerned as indicated in the following document Draft PAS Report on voting 65/356/NP 65/361/RVN Following publication of this PAS, which is a pre-standard publication, the technical committee or subcommittee concerned will transform it into an International Standard. This PAS shall remain valid for an initial maximum period of three years starting from 2005-06. The validity may be extended for a single three-year period, following which it shall be revised to become another type of normative document or shall be withdrawn. Copyright International Electrotechnical Commission Provided by IHS under license with IECLicensee=NASA Marshall Space Flight Center/9972545001 Not for Resale, 03/07/2007 02:40:45 MSTNo reproduction or networking permitted without license from IHS -,-,- PAS 62424 © IEC:2005(E) 7 INTRODUCTION Efficient process engineering requires highly sophisticated tools for the different needs of the departments involved. These engineering tools are normally specialised in process design (PD), in process control engineering (PCE), etc. Therefore, working interoperability is essential to optimise the engineering process in total. Thus, the definition of a harmonised interface and data management is a core task to ensure a smooth workflow throughout the whole project and to guarantee data consistency in the different tools. This document defines procedures and specifications for the exchange of PCE relevant data provided by the P b) Foil strain gauge; c) pH electrode. 3.5 Actuator functional unit that generates from the controller output variable the manipulated variable required to drive the final controlling element NOTE If the final controlling element is mechanically actuated, it is controlled via an actuating drive. The actuator drives the actuating drive in this case. EXAMPLE A practical example of an actuator acting directly on the final controlling element is a d.c. drive. The control unit takes the function of an actuator. The final controlling element is formed by the thyristor assembly that delivers a variable d.c. voltage as an output variable. The control unit and the thyristor assembly together form the final controlling equipment. 3.6 CE loop collection of PCE requests and PCE control functions depicting their functional coherence 3.7 Bubble symbol used to denote and identify a process function. It contains an identification 3.8 process function function in a process IEC 61512-1 Copyright International Electrotechnical Commission Provided by IHS under license with IECLicensee=NASA Marshall Space Flight Center/9972545001 Not for Resale, 03/07/2007 02:40:45 MSTNo reproduction or networking permitted without license from IHS -,-,- PAS 62424 © IEC:2005(E) 11 3.9 PCE control function function in a PCE control IEC 61512-1 3.10 process category letter that designates the kind of process control request 4 Abbreviations Table 1 shows the abbreviations used in this specification. Table 1 Abbreviations CAD Computer Aided Design CAE Computer Aided Engineering CAEX Computer Aided Engineering eXchange CCR Central Control Room E it shall not allow unguided automatic changes. The configurable Copyright International Electrotechnical Commission Provided by IHS under license with IECLicensee=NASA Marshall Space Flight Center/9972545001 Not for Resale, 03/07/2007 02:40:45 MSTNo reproduction or networking permitted without license from IHS -,-,- 12 PAS 62424 © IEC:2005(E) checking step shall include functionality for automatic or manual acceptance of data changes, allowing single decisions up to bulk data management. All changes in the proprietary database and all data inconsistencies discovered shall be reported by the import application. The generation of the report shall be configurable. The import/export application shall assure that the intersection of the different databases holds 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 and deletion of data shall be possible during the life-cycle of the plant. CAEX databases shall be consistent. This requires a consistency check before exporting the data. This procedure shall be followed after a successful data manipulation in a P ii) mandatory fields being filled in; iii) correct use of numbering system of the PCE requests; Inconsistent data shall not be exported 2) Generate PCE relevant information. 3) Check for changed information in comparison with previously stored data in the neutral database. 4) Renaming of PCE request shall be supported by the export functionality. 5) Perform data export from proprietary into neutral database i) e. g. if the PCE request has been changed, the old PCE request within the neutral database shall be deleted and the new one can be exported from the proprietary database into the neutral database. The old PCE request information may be stored in a backup. ii) Other changes shall be performed with the existing object. 6) Generate reports after each data exchange i) new PCE requests list, missing PCE requests list, changed PCE requests list, deleted PCE requests list, problems and error list. b) Data import from neutral database into the target database 1) Generate PCE relevant information from neutral database. 2) Check for changed information by comparing the neutral database with the target database. 3 Perform data import from the neutral into the proprietary database. 4 Renaming of PCE request shall be supported by the import functionality. 5 Generate reports after each data exchange. i) error lists: ii) inconsistencies due to imported data can be detected by the target application during the import process and are not considered within this specification. Copyright International Electrotechnical Commission Provided by IHS under license with IECLicensee=NASA Marshall Space Flight Center/9972545001 Not for Resale, 03/07/2007 02:40:45 MSTNo reproduction or networking permitted without license from IHS -,-,- PAS 62424 © IEC:2005(E) 13 6 Representation of PCE requests in P b) the numbering system for PCE requests in P c) the graphical representation of PCE requests in P d) the type of functional connection between the PCE requests: the control functions; e) the graphical representation of signals in P this means that at least one sensor and one actuator connected to a USZ has the Z as a processing function. 7 Neutral data exchange of PCE relevant P b) an external link which is part of the external plant, connecting B/SIOut000 with A/SIIn000; c) a link which is part of PlantSection A, connecting A/SIIn000 with A/080.1/In001. 7.4.5.2 PCE loops PCE loops are identified by naming conventions. PCE loops will not be mapped to structural elements. The consuming application shall know the special meaning of the naming convention to be able to identify PCE loops. 7.4.6 Example Figure 19 is an example for the CAEX mappings given in Annex B (see Clause B.7). For example, the PCE request 080.5 is mapped as internal element under the system unit class. This means the PCE request is an element of a plant. It contains the required attributes and the external interfaces, which are linked with the external interfaces of the other PCE requests or technical units. The PCE request may be extended with optional attributes. Copyright International Electrotechnical Commission Provided by IHS under license with IECLicensee=NASA Marshall Space Flight Center/9972545001 Not for Resale, 03/07/2007 02:40:45 MSTNo reproduction or networking permitted without license from IHS -,-,- PAS 62424 © IEC:2005(E) 27 UY 080.4 TIC 080.2 YC 080.1 H 080.5 H 080.3 OSH OSL SH SL on/off AH AL Figure 20 Basic mappings In the following, the full XML-text is shown for this example. Copyright International Electrotechnical Commission Provided by IHS under license with IECLicensee=NASA Marshall Space Flight Center/9972545001 Not for Resale, 03/07/2007 02:40:45 MSTNo reproduction or networking permitted without license from IHS -,-,- 28 PAS 62424 © IEC:2005(E) true Y Central true true T Central on/off H Local panel true U Central Copyright International Electrotechnical Commission Provided by IHS under license with IECLicensee=NASA Marshall Space Flight Center/9972545001 Not for Resale, 03/07/2007 02:40:45 MSTNo reproduction or networking permitted without license from IHS -,-,- PAS 62424 © IEC:2005(E) 29 H Central 8 Recommended attributes The object of this subclause is to give a set of attributes, which are typically stored in P it promotes but does not enforce the structure of libraries and permits the free exchange of data. The schema diagrams uses the following conventions to illustrate the structure of the schema elements, the types of the elements, the attributes, the rules for optional elements and the repetitions (see Table 8). Copyright International Electrotechnical Commission Provided by IHS under license with IECLicensee=NASA Marshall Space Flight Center/9972545001 Not for Resale, 03/07/2007 02:40:45 MSTNo reproduction or networking permitted without license from IHS -,-,- 32 PAS 62424 © IEC:2005(E) Table 8 Convention Diagram element Description Example Rectangle with solid border Indicates an element that shall be implemented (mandatory) Rectangle with dashed border Indicates an Element that may be implemented (optional) Datatype Indicates the datatype of an Element after the keyword “type” in the second line of an Element Namespace Indicates the namespace of the used datatype. (Keyword “xs:”) The described CAEX schema refers only to the namespace of W3C (xs:schema xmlns:xs=“http:/www.w3.org/2001/XMLSche ma) Sequence Indicates that the following elements shall be in the defined order Range Indicates the range in which the element can occur. For example 1 to infinite Plus Sign Indicates that the xml-element contains another element. The containing elements are not shown Minus Sign Indicates that all containing XML-elements are shown Greying background with dashed rectangle Indicates that the elements shown are composed in a defined datatype. The name of the dataype is shown at the top of the dashed rectangle with dashed lines A.2 Definition of terms In the following, all the elements and datatypes of CAEX are described. Table 9 CAEX datatypes and elements AdditionalInformation Auxiliary field that may contain any additional information. It may be used in the substructure of the header. AdditionalAttribute Characterizes an additional attribute AdditionalAttributeValue Characterizes an additional value of a defined attribute and its constraints Datatype of the XML Element Used Namespace Range of the element Contains sub-elements All containing sub- elements are shown Datatype of the element shown Copyright International Electrotechnical Commission Provided by IHS under license with IECLicensee=NASA Marshall Space Flight Center/9972545001 Not for Resale, 03/07/2007 02:40:45 MSTNo reproduction or networking permitted without license from IHS -,-,- PAS 62424 © IEC:2005(E) 33 AdditionalExternalInterface Characterizes an additional external interface of a defined interface Attribute Characterizes a property of an defined element AttributeNameMapping Mapping of an internal used attribute name to an external defined attribute name AttributeValue Values of predefined attributes may be set CAEXFile Root-element of the exchanged data Constraint Element to restrict the range of validity of a defined attribute Copyright OrganiZational information about the copyright protection DefaultValue Pred