The concept of FDT IIoT Server (FITS) was created to prepare the FDT technology for a digital future. Through surveys of FDT Group members it became clear that certain extensions of the standard are necessary in order to adapt FDT to the changing environment and emerging user requirements. However, investment protection and interoperability with existing FDT products are also important aspects.

After an initial vision of the concept had been drafted, various working groups (each with M&M participation) within the FDT Group became active and developed a concrete and implementable specification based on this vision.

FDT Working Groups

  • Working Group Architecture & Specification (WG A&S)
    Creates the specifications to standardize the interfaces between the different building blocks.
  • FIT Server CCB (Change Control Board)
    Monitors the development of the FIT Server and sets the detailed requirements.
  • Working Group Test & Certification (WG T&C)
    Creates test cases and processes so that FITS components can be officially tested and certified.
  • Working Group OPC UA (WG OPC UA)
    Creates the FDT Companion specification for FDT / OPC UA.

The way to FITS

The first FDT server prototypes with a focus on "Web interfaces for DTMs" were already implemented on a trial basis in 2017. The project was started with the intention to access devices and offline data sets contained within a DTM via common web browsers (and thus from different end devices).

In order to keep the migration costs manageable, the FDT Group requested that the business logic of the DTMs be kept as unchanged as possible compared to the FDT Specification 2.x.

The OPC UA Companion specification for FDT was already prototypically implemented in advance by a working group of the FDT Group. In the beginning, prototypes were developed and tested based on fdtCONTAINER component developed by M&M. In the further course fdtCONTAINER component was replaced by an early version of the FDT Server.

Regarding the technology platform used for FITS, it was decided - after a survey among FDT users - to migrate to .NET Core. This required some modifications to the FDT specification.

The current FDT specification (version 3.0) has undergone a thorough member review and is expected to be released by the end of 2019.

The FDT IIoT Server has already been adapted by M&M to the current FDT specification and serves as the basis for the upcoming prototyping. Long-term stability, performance and security will be further optimized and subsequently finalized.

Figure 1 graphically illustrates individual components of the overall concept of FITS. Inside are the core server (the implementation of the FDT frame) and the interfaces to OPC UA and the Web. These components represent the FDT server currently being developed by M&M.



FDT IIoT Server


Due to the implemented OPC UA Companion specification for FDT, applications can access the DTMs via OPC UA. Existing FDT2™ DTMs can also be used here without any problems, if the FDT IIoT Server runs on a system based on Windows. This allows the DTMs to be integrated in many applications in which OPC UA is used for data exchange or for executing device-specific functions.

The user interfaces of an FDT DTM for FITS are created with HTML5 and JavaScript. Accordingly, the FDT IIoT Server runs a Web Server from which theseDTM user interfaces are being served. Thus, end users can now access the GUI of the DTMs from any end device.

With open interfaces such as OPC UA or the Web Server, security plays an important role. The FDT Group has taken this into account by setting up its own security working group, whose work also influences the development of the FDT IIoT server.

The DTM Business Logic Objects and the FDT Frame are developed in FITS based on .NET Standard or .NET Core. Thus, the FDT IIoT Server can be operated not only on Windows operating systems, but also on Linux for example. This opens new possibilities for the architecture of an FDT-based system.

With all these innovations, the advantages of FDT remain unchanged, such as the possibility of offline parameterization, access to devices through network hierarchies ("Nested Communication") or the open concept for the integration of fieldbuses.

The practical implementation of the FDT IIoT server is of a modular design. This allows users to decide for themselves whether to use the server "Out of the box" or to implement individual parts such as the OPC UA Server or the Web Server itself. A future expansion should also offer the possibility to develop application or manufacturer specific apps. These cloud be very specific application (e.g. fast display of the device or system status) and make proprietary functions of a manufacturer specific device accessible.

FITS Products

The FDT IIoT Server will be available as a product from the FDT Group (

Consulting, workshops, customized builds etc. around the FDT Server are available at M&M Software. Volker Herbst  and Christian Gnädig will be happy to answer your questions and provide further information on what is possible.

Our FDT-Specific services

M&M Software is working actively with the FDT Group to bring innovation to your products. Our experience with industrial IoT and FDT will help you get your FDT IIoT Server (FITS)-Strategy ready today.

  • Consulting
    We advise our customers professionally and comprehensively about device integration and help to find a tailor-made and future-proof device management strategy. We always take into account state-of-the-art and future technologies, such as FDT (1.2.x / 2.x) and FITS.
  • DTM Development
    We develop DTMs (including FDT 3.0 DTMs) for field devices and communication components quickly and efficiently based on our development platforms dtmMANAGER and basicDTM.
  • DTM Test & Certification
    As one of the official test labs of the FDT Group, we test and certify DTMs. In addition, we support our customers in the preparation of their DTMs for the test procedure. This helps to avoid possible problems and delays.
  • The FDT products distributed by M&M
    fdtCONTAINER component, fdtCONTAINER application and dtmMANAGER already support FDT 3.0.

Sprache der Seite ändern