File preview
DEVICE INTEGRATION
FDT one step more... ISA103
Standards Certification Education & Training Publishing Conferences & Exhibits
Contents
· Why FDT ? Today`s situation · Overview FDT Technology · Benefits in Automation · IEC Standardisation · FDT Group · Summary
C. Verney 07/09/2009
Why FDT ?
Today`s Situation
C. Verney 07/09/2009
Today`s situation
· A lot of different tools
Administration effort (Versions and Functions) Varying conditions for the different tools Training effort to handle the tools for all devices Knowing all tools is nearly impossible
C. Verney 07/09/2009
Today`s situation
· Many field devices means many project files
Each tool has its own data management Each data set of a device is created and stored separately Each data set corresponds to a project file Inconsistent administration
C. Verney 07/09/2009
Today`s situation
· Access to the field busses
Different field busses used depending on the country/market or customer Each supplier supports a different field bus HW module in the PC Different PC field bus HW modules needed for the same field bus Increased effort for the stock Increased training effort Uncomfortable handling
C. Verney 07/09/2009
What is FDT-DTM ?
·
FDT means Field Device Tool and represents any kind of engineering tool or process control system DTM means Device Type Manager and represents a tool to handle a field device in its different life cycle phases CommDTM represents a DTM providing access to the network/field bus
FDT Technology allows easy integration of tools
. os ot Ph
..
·
It is a software component like a driver for a printer It provides the functionality to handle the device It is « plugged » into the FDT frame application
DTM is delivered with the device
·
C. Verney 07/09/2009
The technology is field bus independent
XML data exchange between the SW components Field bus services defined with XML schemas CommDTM converts schema into field bus protocol
General Architecture
Interface description and behavior Based on Standards (Windows, Active X, XML) Scalable (not all interfaces are mandatory) Extendable by defining new interfaces
C. Verney 07/09/2009
Logical and Physical Communication
ool
Communication DTM
T FDT
Ethernet
Gateway DTM
Gateway DTM
Device DTM
C. Verney 07/09/2009
Communication DTM
· Contains the application software for specific communication hardware.
For example, it may support configuration settings like baud-rate, start and stop bits, etc.
· Provides Communication Channels which provide the services to access the fieldbus
C. Verney 07/09/2009
Gateway DTM
· Contains the application software for a device linking field busses · Can be seen as a combination of a Communication DTM and a Device DTM.
It provides Communication Channels to access to the linked fieldbus and Process Channels for the fieldbus where it's connected to.
C. Verney 07/09/2009
Device DTM
· Contains the application software for field device.
For example such a DTM supports functions to configure and parameterize the device Device's I/O signals or process values are accessed via the Process Channel objects
C. Verney 07/09/2009
Example of a DTM GUI and Features
C. Verney 07/09/2009
FDT at a glance
· One Tool
· One Communication Hardware
· One Project
· Field bus independent Communication
C. Verney 07/09/2009
FDT major benefits
· Enhances existing Device Description technologies
Installed base stays untouched and can be enhanced seamless
· Allows integration of different device tools into one engineering system
Provides a field bus independent interface
· Allows extended capabilities (GUI, device features, asset management, predictive maintenance and diagnostics)
Customer is vendor independent selecting devices
· FDT is supported by major players
Will be soon a standardized open interface (IEC 62453)
C. Verney 07/09/2009
IEC 62453 series
· FDT interface specification has several parts
Part 2 Concepts and detailed detailed description Part 3xy Communication Profile Integration
Part 5xy Communication Profile Implementation
Part 4z Implementation Profile
C. Verney 07/09/2009
IEC 62453 series includes the following parts
· · · · · · · · · · · · · · · · ·
C. Verney 07/09/2009
Part 1: Overview and guidance Part 2: Concepts and detailed description Part 301: Communication profile integration - IEC 61784 CPF 1 Part 302: Communication profile integration - IEC 61784 CPF 2 Part 303-1: Communication profile integration - IEC 61784 CP 3/1 and CP 3/2 Part 303-2: Communication profile integration - IEC 61784 CP 3/4, CP 3/5 and CP 3/6 Part 306: Communication profile integration - IEC 61784 CPF 6 Part 309: Communication profile integration - IEC 61784 CPF 9 Part 315: Communication profile integration - IEC 61784 CPF 15 Part 41: Object model integration profile Common object model Part 501: Communication implementation for common object model - IEC 61784 CPF 1 Part 502: Communication implementation for common object model - IEC 61784 CPF 2 Part 503-1: Communication implementation for common object model - IEC 61784 CP 3/1 and CP 3/2 Part 503-2: Communication implementation for common object model - IEC 61784 CP 3/4, CP 3/5 and CP 3/6 Part 506: Communication implementation for common object model - IEC 61784 CPF 6 Part 509: Communication implementation for common object model - IEC 61784 CPF 9 Part 515: Communication implementation for common object model - IEC 61784 CPF 15
Thanks
for your attention
C. Verney 07/09/2009
FDT one step more... ISA103
Standards Certification Education & Training Publishing Conferences & Exhibits
Contents
· Why FDT ? Today`s situation · Overview FDT Technology · Benefits in Automation · IEC Standardisation · FDT Group · Summary
C. Verney 07/09/2009
Why FDT ?
Today`s Situation
C. Verney 07/09/2009
Today`s situation
· A lot of different tools
Administration effort (Versions and Functions) Varying conditions for the different tools Training effort to handle the tools for all devices Knowing all tools is nearly impossible
C. Verney 07/09/2009
Today`s situation
· Many field devices means many project files
Each tool has its own data management Each data set of a device is created and stored separately Each data set corresponds to a project file Inconsistent administration
C. Verney 07/09/2009
Today`s situation
· Access to the field busses
Different field busses used depending on the country/market or customer Each supplier supports a different field bus HW module in the PC Different PC field bus HW modules needed for the same field bus Increased effort for the stock Increased training effort Uncomfortable handling
C. Verney 07/09/2009
What is FDT-DTM ?
·
FDT means Field Device Tool and represents any kind of engineering tool or process control system DTM means Device Type Manager and represents a tool to handle a field device in its different life cycle phases CommDTM represents a DTM providing access to the network/field bus
FDT Technology allows easy integration of tools
. os ot Ph
..
·
It is a software component like a driver for a printer It provides the functionality to handle the device It is « plugged » into the FDT frame application
DTM is delivered with the device
·
C. Verney 07/09/2009
The technology is field bus independent
XML data exchange between the SW components Field bus services defined with XML schemas CommDTM converts schema into field bus protocol
General Architecture
Interface description and behavior Based on Standards (Windows, Active X, XML) Scalable (not all interfaces are mandatory) Extendable by defining new interfaces
C. Verney 07/09/2009
Logical and Physical Communication
ool
Communication DTM
T FDT
Ethernet
Gateway DTM
Gateway DTM
Device DTM
C. Verney 07/09/2009
Communication DTM
· Contains the application software for specific communication hardware.
For example, it may support configuration settings like baud-rate, start and stop bits, etc.
· Provides Communication Channels which provide the services to access the fieldbus
C. Verney 07/09/2009
Gateway DTM
· Contains the application software for a device linking field busses · Can be seen as a combination of a Communication DTM and a Device DTM.
It provides Communication Channels to access to the linked fieldbus and Process Channels for the fieldbus where it's connected to.
C. Verney 07/09/2009
Device DTM
· Contains the application software for field device.
For example such a DTM supports functions to configure and parameterize the device Device's I/O signals or process values are accessed via the Process Channel objects
C. Verney 07/09/2009
Example of a DTM GUI and Features
C. Verney 07/09/2009
FDT at a glance
· One Tool
· One Communication Hardware
· One Project
· Field bus independent Communication
C. Verney 07/09/2009
FDT major benefits
· Enhances existing Device Description technologies
Installed base stays untouched and can be enhanced seamless
· Allows integration of different device tools into one engineering system
Provides a field bus independent interface
· Allows extended capabilities (GUI, device features, asset management, predictive maintenance and diagnostics)
Customer is vendor independent selecting devices
· FDT is supported by major players
Will be soon a standardized open interface (IEC 62453)
C. Verney 07/09/2009
IEC 62453 series
· FDT interface specification has several parts
Part 2 Concepts and detailed detailed description Part 3xy Communication Profile Integration
Part 5xy Communication Profile Implementation
Part 4z Implementation Profile
C. Verney 07/09/2009
IEC 62453 series includes the following parts
· · · · · · · · · · · · · · · · ·
C. Verney 07/09/2009
Part 1: Overview and guidance Part 2: Concepts and detailed description Part 301: Communication profile integration - IEC 61784 CPF 1 Part 302: Communication profile integration - IEC 61784 CPF 2 Part 303-1: Communication profile integration - IEC 61784 CP 3/1 and CP 3/2 Part 303-2: Communication profile integration - IEC 61784 CP 3/4, CP 3/5 and CP 3/6 Part 306: Communication profile integration - IEC 61784 CPF 6 Part 309: Communication profile integration - IEC 61784 CPF 9 Part 315: Communication profile integration - IEC 61784 CPF 15 Part 41: Object model integration profile Common object model Part 501: Communication implementation for common object model - IEC 61784 CPF 1 Part 502: Communication implementation for common object model - IEC 61784 CPF 2 Part 503-1: Communication implementation for common object model - IEC 61784 CP 3/1 and CP 3/2 Part 503-2: Communication implementation for common object model - IEC 61784 CP 3/4, CP 3/5 and CP 3/6 Part 506: Communication implementation for common object model - IEC 61784 CPF 6 Part 509: Communication implementation for common object model - IEC 61784 CPF 9 Part 515: Communication implementation for common object model - IEC 61784 CPF 15
Thanks
for your attention
C. Verney 07/09/2009