c11 - fdi field device integration_alexanderkaiser
DESCRIPTION
In this document the FDI technology is definedTRANSCRIPT
© ABB Group June 27, 2009 | Slide 1
FDI –A technology development project
Product Management APR/I:
© ABB Group – Alexander Kaiser June 27, 2009 | Slide 2
What is device management?
Give me process value
45.89 °C
Status = Good
Give me parameter value
Set parameter value
Device IntegrationCommunication world
Device ManagementBehaviour / Parameter world
Information of the device needed by
DCS to configure the cyclic
transmission of process value(s).
Done in DCS. Process /
communication is not running.
Information of the device needed for
modification of behaviour of the
device measurement, data
representation. Observation
of device during running process.
Done in special applications.
Acyclic access to device.
Process / communication
running.
© ABB Group – Alexander Kaiser June 27, 2009 | Slide 3
Which technologies are available?
ECT -> EDDL Cooperation Team
ECT, founded 2003
5 member organizations
Driver files:
EDD with and without
enhancements
Runtime environment:
Interpreter
Interpreter e.g.:
DHH8x0 Handhelds – ABB
Asset Vision Professional – ABB
800xA - ABB
FieldMate – Yokogawa
PDM – Siemens
AMS – Emerson
FDT -> Field Device Tools
FDT Group, founded 2003
62 member companies (Mar. 2008)
Driver application:
DTM
Runtime environment:
FDT Frame application
Frame Applications e.g.:
Asset Vision Basic,
Device Management Aspect
(800xA, Asset Vision Pro.) – ABB
FieldCare – E+H
PACTware – independent
fdtContainer – M&M
© ABB Group – Alexander Kaiser June 27, 2009 | Slide 4
What are pros and cons?
Pros:
- Light weight solutions (files)
- Usable also on Handheld devices
- Fully scalable implementations
Cons:
- Many variants (DCS specific)
- Limited UI / Logic capabilities
- No nested communication
- Not supported by all DCS
Pros:
- All capabilities of high level
programmers language usable
- Nested communication
- Offline configuration possible
- Multimedia capabilities
- Extensible in protocol support
Cons:
- Heavy components (Applications)
- Usable on PCs only
- Solutions not scalable for device
types
- Not supported by all DCS
© ABB Group – Alexander Kaiser June 27, 2009 | Slide 5
What are overall drawbacks of both technologies?
User‘s Instrument selection also depends on device management
technology supported by DCS.
A single technology is needed.
Device Management solution has to be deployed on all workstations
where access to the device type is necessary.
A Client / Server technology is needed.
Despite of the benefits of one technology the user also wants
the use the benefits of the other technology.
A combination of the benefits of both technologies is needed.
Competing technologies move the focus on the competition and
away from user needs.
A joined effort of the competing interest groups is needed.
© ABB Group – Alexander Kaiser June 27, 2009 | Slide 6
What is the solution?
March 2007: FDT Group and ECT Members are working together to create a
common device management technology: Field Device Integration: FDI
FDI
© ABB Group – Alexander Kaiser June 27, 2009 | Slide 7
Basic Requirements
Host system independent
Platform and operating system independent
Provides access to the full capability of the field device
Supports FOUNDATION™, HART®, PROFIBUS® & PROFINET®
Adoptable to support other fieldbus communication technologies
Based on OPC UA client/server specifications & information model
Specifications independently validated by the ECT organizations
Provides backward compatibility with existing EDD’s & DTM’s
Provides conformance test requirements to assure compliance
Provides guidelines for field device and system developers
© ABB Group – Alexander Kaiser June 27, 2009 | Slide 8
FDI Architecture
Device Package
Server OPC UA Client
FOUNDATION™
HART®,
PROFIBUS
PROFINET
System Architecture
© ABB Group – Alexander Kaiser June 27, 2009 | Slide 9
FDI Device Package
Device
Definition
User Interface
Description
User Interface
Plug-in
Business
Logic
Based on
IEC 61804-3 EDDL
Based on
IEC 62453 FDT
Runs on ClientInterpreted on ClientInterpreted on Server
Mandatory Optional Optional Optional
Device Package
Based on
IEC 62541 OPC UA
© ABB Group – Alexander Kaiser June 27, 2009 | Slide 10
FDI – How does it work.
Client WindowClient Window
Programmed
Application
File Edit View
<Device Instance Name>
<Device Type>
<Version>
<Manufacturer>
1
2
UI Function 1
UI Functions
UI Function 2
Options
UI Function UI Function
100.01
Group 1
°C
Option 1
Option 2
Group 2
CancelApplyOK
Group 2
Group 2Group 1
User
Interface
DescriptionGroup 2
© ABB Group – Alexander Kaiser June 27, 2009 | Slide 11
FDI – How does it work.
File Edit View
<Device Instance Name>
<Device Type>
<Version>
<Manufacturer>
1
2
UI Function 1
UI Functions
UI Function 2
Options
UI Function UI Function
Group 2
Client WindowClient Window
Group 2
Group 2Group 1
User
Interface
Plug-In
© ABB Group – Alexander Kaiser June 27, 2009 | Slide 12
Project schedule
June
2009
Top level
use cases
ECT and FDT
Group agree to
develop
FDI Project
Technical design
team kick off
meeting
Use cases
validated by
end users
Architecture and
functional specification
development
System Architecture
Final
Specifications
Functional
Specifications
Technical specification
development and
validation
Mar
2007
Dec
2007
Dec
2008Dec
2009
Architecture
validated
by
end users
© ABB Group – Alexander Kaiser June 27, 2009 | Slide 13