M&M FDT 1.2.1 Online Specification
 1.7 Scope of performance


Interfaces and Methods   -   Schemas   -   FDT Specification   -   Quicklinks   -   Abbreviations

Up to FDT Specification

1.1 Problem
1.2 State of the Art
1.3 Aims
1.4 Technological Orientation
1.5 Solution Concept
1.6 Migration to DTM
1.7 Scope of performance
1.8 Audience

1.7 Introduction: Scope of performance

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.

The scope of this version of the FDT concept 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 a way 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.



© by M&M Software GmbH, parts of this website taken from FDT Interface Specification Version 1.2.1, © by FDT Group, AISBL.
This website is published for support of M&M products as granted in license conditions, chapter 2.1.
Last updated 2015-02-05 15:17
Email: FDT Technical Support Line.