Data Harmonisation Middleware adapter

The Data Harmonisation Middleware (DHM) Adapter actually consists of various components, which are detailed below. It functions as Linked Data adapter for specific middleware solutions, including GAMMA V, and OPC UA.

  • LiveData-Access: The Live Data Access component is used to get values from a machine via the DHM-Adapter. It depends on the Machine Semantic (from the WP8 ontology set), which provides for each available sensor a special URI, by which the values of sensors & actuators can be acquired.
  • Linked Data Publisher (LDP): The Linked Data Publisher extracts the configuration of sensors and actuators from a Gamma machine. It is used to generate the Machine Semantic (from the WP8 ontology set) which is stored in the Linked Data Server (LDS). The LDP gets active each time a Gamma system is booting up or is shutting down and then “publishes” the new Machine Semantic.
  • Middleware Logger: The component Middleware-Log is used to continuously log sensor and actuator data. For the maintenance staff this logged data provides later on an analysis of the “data history” and eases the detection and repair of machine defects. It also allows at runtime to activate/deactivate the logging-mechanism for selectable Process Variables (e.g. Sensors or Actuators).


  • Job controller: The task of the Job Controller component is receiving incoming requests and organizing and controlling the distribution of the tasks to the components of the DHM-Adapter. Requests for performing tests are handled by the Test Execution Environment.
  • Test execution environment: The task of the TEE is to perform predefined tests and store the results in a Linked Data Server.
  • Mobile maintenance modelling component: The modelling component for a system for Mobile Maintenance should take care about modelling and generating maintenance (test) cases. Within the project ComVantage Mobile Maintenance we specified requirements for the functionality of a tool to support these tasks. Within the ComVantage project a concept about how one could support the creation of mobile maintenance test cases was described.
  • Predictive active machine maintenance support: The Predictive Active Machine Maintenance Support component (PAMMS) is responsible for collecting and interpreting relevant data for predicting impending failures. At user defined intervals it attaches itself to a GAMMA service and collects relevant sensor values. With predefined checking functions the collected data are analysed and under certain predefined conditions (e.g. the measured value is more than 10 % higher than the expected threshold), an alarm message is stored in the Linked Data Store.
  • Extended predictive machine maintenance system (EPAMMS): The EPAMMS is the counterpart at the site of the Support Company of the PAMMS. In the Final Mobile Maintenance Prototype only a message will be sent to the Mobile Maintenance Coordinator in case of a defect as a proof of concept.