Collecting data from a machine

In a manufacturing process we deal with 2 different devices:

1) Devices with their own control, such as a PLC.

2) Devices without their own controls. Often the older machines.

Matranda offers a solution for collecting data for both devices.

For equipment with its own control, we look at which protocol the device communicates with. This could be OPCUA, ModBus TCP, etc.

For equipment without its own control, Matranda installs a Master and/or Slave Module to which all IOs can be connected. These could be switches, sensors, etc.

Real time visualization and processing

The data collected from the machines / devices is further processed by an MTD Fat Client and/or by the MTD Control Module.

MTD Fat Client:

The MTD Fat Client can be installed in any production process. The advantages of this are:

• Live data visualization through dashboarding that is drawn up together with the customer.
• Direct connection with the MTD Control Module.
• Direct connection with the machine/equipment/MTD Master-Slave module.
• Data filtering

MTD Control Module:

The MTD Control Module is an independently operating module, the main purpose of which is to send the data to the correct MTD Fat Client and MTD Control Modules and MTD Server. This MTD Control Module is also called the traffic controller of all data.

All MTD Control Modules located in an organization are connected to each other. The location of these modules is unlimited, so they can also be on the other side of the world.

Data storage and analysis

All data from the MTD Control Module (-s) is stored on the MTD Server.

The MTD Server contains the following software packages:

• Alarms and warnings. Also called the Fault Report System.
• Predictive maintenance.
• Machine Learning.
• Link with PowerBI.

If the customer already has a Data Warehouse, it is possible to retrieve the data from the MTD Server and process it in their own ERP systems.

The data is stored on the MTD Server for a minimum of 7 years.