New NAMUR Recommendations

Size: px

Start display at page:

Download "New NAMUR Recommendations"

Alexina Rose
5 years ago
Views:

1 Fieldbus Foundation Freedom to choose. Power to integrate New NAMUR Recommendations Sven Seintsch

2 Part 1 NAMUR Recommendation NE 105 Specifications for Integrating Fieldbus Devices in Engineering Tools for Field Devices Part 2 NAMUR Recommendation NE 107 Requirements regarding self-monitoring and diagnosis in field instrumentation Prepared by: NAMUR-Working group 2.6 Feldbus

3 NAMUR Recommendation NE 105 Specifications for Integrating Fieldbus Devices in Engineering Tools for Field Devices Introduction Scope of the NAMUR Recommendation Long-Term Viability of the Device Integration User Interface Specification and Style Guide Functional Specifications for Device Connections and Interfaces for Device Data Processing Certification Result

4 Introduce of the NAMUR Recommendation Field buses and field devices that are suitable for use in the chemical industry are commercially available. From a user s perspective, one has to summarize the device integration specifications, despite the standardization of buses and the permanent progress made in establishing data transfer rules. The main focus lies on life cycle management: Make sure that complex Automation systems can be maintained without undue effort over a production plant s life cycle a view to adopting version update frequencies that do not impede technological progress

Existing Integration methods for Field devices Engineering-, Configuration- or Maintainace- tool GSD Interpreter (E)DD Interpreter HCF DD Interpreter FDT-Container ASCII Datei GSD (E)DD HCF DD Device

5 Existing Integration methods for Field devices Engineering-, Configuration- or Maintainace- tool GSD Interpreter (E)DD Interpreter HCF DD Interpreter FDT-Container ASCII Datei GSD (E)DD HCF DD Device Device DTM DTM Descriptions Data: Software driver: + Operating system independent + implementation of complex functions + unified User interface - depend on Operating system - Complex functions different to implement - Device specific user interface

6 Objective of the NAMUR Recommendation This NAMUR Recommendation lays out the specifications for uniform user interfaces, the functionality of device connections and for configuration tool interfaces for the processing of device data. The goal is to be able to efficiently and safely operate, parameterise and manage the data of devices from various manufacturers with a uniform tool.

7 Long-Term Viability of Device Integration Investment Safety Investments must be safeguarded by a clear and stable interface between the application and operating system. Specifications: New field device with a new device description No operating system updates required New version of the operating system No change of device description required New version of the device integration tool No change of operating system or device description required The Device integration just as one part of the automation system should not decrease the live cycle of the complete system

8 Long-Term Viability of Device Integration Version Conflicts Configuration Tool Device Description Device descriptions must be upward and downward compatible for integration.

9 User Interface Specifications & Style Guide Integration of Devices Integration of Devices A standard procedure for the integration of new devices must be established. It must be compatible with all modes of communication (HART, FF, DP, PA, etc.). User Guidance Uniform user guidance must be provided for every component regardless of the manufacturer or type of device. Key features must be made available in a clearly defined manner.

10 User Interface Specifications Representation of devices Operating concepts and the user interface employed to configure and diagnose field devices must share a uniform structure. A difference must be made between standard features and parameters (e.g. measurement limit settings) of various device types (e.g. measurement transmitters) and manufacturer specific features and parameters (e.g. extended diagnostic features). Display methods used for standard parameters components as well as the grouping of standard parameters and nomenclature must be determined uniformly for al manufactures.

11 Functional Specifications for Device Connections and Interfaces for Device Data Processing Device Descriptions Each field device may only have one device description, which should work without requiring changes to every tool (across manufactures) Licensing of Device Descriptions The device description and the device form a functional unit. The device description is an integral component of the device and therefore cannot be licensed separately. Cross-Platform Compatibility Device descriptions must be compatible with all versions of the computer s operating system.

12 Functional Specifications for Device Connections and Interfaces for Device Data Processing Full Support of Device Functionality Device descriptions should allow one to access all of the device s parameters and features. One should also consider using graphical images (shell curves, characteristic curves, etc.) to simplify operation. Standardized Data Filing Inconsistencies between sets of parameters, which often occur in various systems (control systems, device parameterisation tools, asset management systems, etc.) should be avoided by adopting a uniform data structure and filing strategy, with a central storage space. Storing of parameter datasets by name and version number

13 Certification User interface Compliance with established user guidance and device mapping criteria must be ensured. (Certification process) Functionality A mechanism must be devised to ensure that system and field device suppliers can guarantee that their products work. The mechanism should comply with manufacturer-independent certification standards that ensure interoperability and crossversion compatibility.

14 Result The existing integration methods do not match complete the recommendations in the NE 105. Future device technology with higher functionality and faster version changes in the device technology or IT World will cause a non containable situation, if the presented requirements are not solved. Manufactures/Foundations are called to react with proper moves, otherwise the user acceptance of the technology is endangered.

15 Part 2 NAMUR Recommendation NE 107 Requirements regarding self-monitoring and diagnosis in field instrumentation Diagnose History Experience Result User requirements (Author: Dr. Zobel)

Diagnosis Information Process Plant/ automobile Information to

16 Who needs which Diagnostic Information? Process technology automotive technology Operator/ Driver Diagnosis Information Process Plant/ automobile Information to Operator/Driver: All information needed for save driving No needless information As soon as possible

17 Who needs which Diagnostic Information? Information to work shop laborer: As detailed as possible includes proposals for solution work shop diagnosis tool: 773 Diagnostic codes!

18 A Beginning: Diagnostic structure NAMUR 64 Organization into 3 status signals: Failure: Due to a malfunction at the field equipment or at its periphery the output signal is invalid. Function control: On the field equipment one works, the measuring signal is temporarily invalid therefore. Maintenance Required: The measuring signal is still valid, but the wear supply will shortly be exhausted.

Status byte in the Fieldbustechnique (256 Stati) 00 Hex bis 1F Hex Messwert BAD 40 Hex bis 59 Hex Messwert UNCERTAIN 60 Hex bis 63 Hex Messwert UNCERTAIN 64 Hex bis 67 Hex Messwert

19 Status byte in the Fieldbustechnique (256 Stati) 00 Hex bis 1F Hex Messwert BAD 40 Hex bis 59 Hex Messwert UNCERTAIN 60 Hex bis 63 Hex Messwert UNCERTAIN 64 Hex bis 67 Hex Messwert UNCERTAIN 80 Hex bis A7 Hex Messwert GOOD (NON CASCADE) C0 Hex bis E7 Hex Messwert GOOD (CASCADE) Failure Funktion control 84 hex Maintenance Positioner: Additional information by checkback bits

Diagnostic transmission with Foundation Fieldbus Resource Block Transducer Block Analog Input Block Status Byte Block Error Block Error Block Error Classify

20 Diagnostic transmission with Foundation Fieldbus Resource Block Transducer Block Analog Input Block Status Byte Block Error Block Error Block Error Classify status Information! Switch! No Maske Yes Abnormal Active BAD Active Status information visualized, acyclic readable Status information visualized, cyclic readable

21 Result: Diagnostics with Fieldbus No manufacturer-spreading classification of diagnostic massages Classification of diagnosis messages according to NAMUR 64 only device-specifically High developing costs (driver, alarm system) Announcement of the status signals over color changes good acceptance in factory Differentiated diagnosis: possible with Fieldbus

22 Result: Diagnostics with Fieldbus Application specific: error messages not to be disabled (Pressure measuring cell overpressure, measuring tube empty, ) Reporting gush with start-up Not all messages are classifiable: Measuring tube not completely filled, to high solid part, electronics temperature too highly, DCS or vendor specific diagnostic not useable for multi vendor plants

23 User Requirements Standardization of all diagnostic messages into four status signals - 4. Status signal Out of Specification - Fine partitioning of the 4 status signals possible Allocation of the diagnostic messages to the status signals must take place in the field instrument Independence from DCS! Suppression of individual diagnostic messages in the equipment Diagnostics must take place in real time! interoperability for all devices independent from the technical transmission (PA / FF / Hart /..)

24 User Requirements NE 107 Requirements regarding self-monitoring and diagnosis in field instrumentation Cyclic diagnosis from the Device structured: reliable internal just in time failure maintenance request function control out of specification (New)

25 failure Def.: Ausfall (F = failure) Due to a malfunction at the field equipment or at its periphery the output signal is invalid.

26 maintenance request Def.: Wartungsbedarf (M = maintenance request) The measuring signal is still valid, but the wear supply will shortly be exhausted.

27 check Def.: Funktionskontrolle (C = check) On the field equipment one works, the Measuring signal is therefore temporarily invalid.

28 out of specification Def.: außerhalb der Spezifikation (S = out of specification) The Device is used out of it s spez. Range or Deviation cursed by internal Problems or Process characteristics

29 Profit - better planning of maintenance no needless maintenance - more confidence into the measured value less examination - longer time between service checks

30 Thank you for your attention

WirelessHART Is Ready for the Real World

WirelessHART Is Ready for the Real World PR-2010-1080PA-eng-WirelessHART_products Pepperl+Fuchs GmbH Lilienthalstrasse 200 68307 Mannheim Germany Please indicate the following contact information for publication: Tel.: +49 621 776-2222, Fax: