FDI-User-Requirements 2011, in addition to NE 105from 2011-10-19
Functions and information from devices can be made accessible to superordinate systems with the aid of device integration (e.g. to central PCS or maintenance systems). Device integration is generally independent of the manufacturer and the data transfer method employed. This paper summarizes the most important requirements to be met by a uniform interface characterised by long-term stability if FDI (Field Device Integration) is to be accepted as the new standard for device integration.
Aim and contents
The acceptance and implementation of these basic requirements form the basis for the acceptance and successful application of FDI device packages, including mandatory implementation of the FDI standard interface "Common Host Components" for the manufacturer-independent implementatio of device packages via server-client and FDT (2.0) applications. The objective is to ensure that no new EDDL or DTM (2.0) will be used for future devices. Only FDI device packages should be sold and utilised for new devices.
- Harmonised EDDL must be used within FDI (e.g. within the device packages).
- FDI standard common host components (EDD Engine, UID Renderer, UIP Hosting Component, Binary Readers ...) must be utilised completely and consistently as the standard interface for device packages in all FDI systems (servers, FDT (2.0),....). These standard common host components must be centrally administered (FDI?) as a toolkit.
- The EDD blocks "Device Definition", "Business Logic" and "User Interface Description" must be mandatory in all device packages in order to support the start-up of the devices.
- The integration and activation of FDI device packages must be flexible. Active device integration must be achieved, optionally with UID (User Interface Description) and UIP (User Interface Plugin), or alternatively just with the UID.
- Migration solutions should ensure further operation of devices presently installed within new FDI systems.
- Each device must only have one device package. The selection of several device packages for a device (e.g. with different functionalities inside device packages) is not permissible.
- FDI servers, communication servers and clients must have a certified manufacturer-independent and standardised interface (e.g. OPC).
- There must be independent certification of all products (including frames/host interfaces/servers, style guide, device packages...). All new product versions must also be certified. Only certified products will be approved.
- All device integration software downloads and installations must be possible without rebooting the DCS.
- There must be a uniform download and installation process for a given system (e.g. for device packages).
- Uniform version and update scenarios must be defined. It should be possible to obtain an overview from a central position and identify which components (e.g. device packages) are available, in which version and at which location in a system. Installation of a single device package (not only libraries) must be possible.
- Device packages must contain the complete functionality of a device, including cyclic and acyclic communication (e.g. GSD files).
- Labelling of device packages and devices must be realised pursuant to NE53.
- All certified download products (e.g. device packages) must be centrally available on an FDI homepage
- Standard profile device packages and profile communication packages (e.g. for nested communication) must be available.
- Licenses restricting use of device packages and license fees are not permissible
- A life cycle concept should exist for investment protection.
For detailed information:
NAMUR (Interessengemeinschaft Automatisierungstechnik der Prozessindustrie)
c/o Bayer Technology Services GmbH Building K 9
Telephone: +49 - 214 - 30 – 71034
Fax: +49 - 214 - 30 – 72774
WIB (International Instrument Users' Association)
2514 AP The Hague (The Netherlands)
Telephone: +31 - 70 - 3560092
Fax: +31 - 70 - 3560074
Unter Mitwirkung des AK –Feldbus– der IGR (Interessengemeinschaft Regelwerk Technik e.V.)