1.1 Performance
This part of IEC 62453 includes the engineering and commissioning of field devices.
Functionality for documentation and audit trail support is also considered. Examples and use
cases are mainly given for actors, sensors and remote I/Os. Of course, FDT is prepared to be
used for devices like drives, analyzers, recorders, etc. as well.
The FDT interfaces are designed in such a way as to support all significant fieldbus protocols.
The main focus of this version of FDT does not lie on any specific fieldbus protocol. Due to
the scalable structure of FDT it will be easy to add new schemas in order to extend the scope
to new protocols.
The FDT concept allows a device manufacturer to provide his device specific functionality
within an engineering system. So the main capacity of FDT depends on the functionality of the
devices and the according applications.
This PAS is intended for developers who want to implement FDT components.
The FDT concept does not claim to provide a solution for all engineering tasks and the
associated tools. Therefore, the engineering subjects "electrical wiring planning, mechanical
planning, etc." or the plant management subjects such as "maintenance, optimization,
archiving, etc." do not form part of the current performance range of FDT. Some of these
aspects may be included with future versions of FDT.
1.2 Audience
This PAS is intended as reference material for developers of FDT compliant Frame
Applications and DTMs. It is assumed that the reader is familiar with Microsoft ActiveX1
technology and the needs of the Process Control industry or of the field devices.
This PAS is intended to facilitate development of DTMs and Frame Applications in the
language of choice that supports Microsoft ActiveX. Therefore, the developer of the respective
component is expected to be familiar with the technology required for the specific component.
Remember, FDT is a client/server architecture implemented in a first step with Microsoft
COM.2