Data Management System (DMS)

(v. 5.4.9019)

The Data Management System (DMS) is an interim repository for data gathered from external sources. Using a collection interface (for example, the Data Collection Service, or DCS), you can pass this data into the SPC client's data entry process, eliminating the need for manual data entry.

DMS Model

The DMS model consists of several layers, illustrated and explained below.

Without a means of collecting data directly from shop floor equipment, you would have to enter data manually, which could require additional time and introduce typographical and other errors into your data.

DMS Terminology

DMS as a Service

The DMS is a Windows service that runs when the computer boots, and the application does not require a logged in user or user interaction.

DMS Provider

A Provider is a software object that captures values from shop floor equipment using interfaces or links, and then places those captured values into separate Items.

DMS Consumer

A Consumer is a software object that reads values from the DMS DataStore, and then writes those captured values into a database.

DMS Item

Managed by a Provider, an Item contains one value from the connected shop floor equipment. For example, if a Provider connects to a PLC and you were capturing X, Y, and Z positions from a servo controller, the Provider would manage three items (one for X, one for Y, and one for Z).

DMS Provider Hierarchy

In the DMS system, there could be several Providers, and each Provider could be publishing several Items.

  • Provider 1
    • Item 1
    • Item 2
    • Item 3
    • ...
  • Provider 2
    • Item 1
    • Item 2
    • Item 3
    • ...
  • Provider 3
    • Item 1
    • ...

DMS Providers

In DMS, there are providers that connect directly to a hardware or software data source using specific interfaces for files, TCP/IP, serial data (RS-232, RS-422, etc.), or OPC. Once connected, the DMS assembles the available data and publishes the values to the DMS DataStore, making the data available to the SPC software.

When using the OPC Provider in a VMWare or virtual environment, you must set the virtual network to Bridged, and not NAT.

The available DMS providers are:

  • Bridge Provider. The Bridge Provider enables connections to a remote computer's DMS via TCP/IP, allowing you to access the providers and their items on that remote computer as though they were local.
  • Clock Calendar Provider. The Clock Calendar Provider publishes date/time values based on the computer's real-time clock, which can be localized or in UTC, and can be formatted as a standard date or as Unix Time (Posix). In addition, the provider can publish elapsed values, such as the number of seconds since the start of the month, or the number of seconds since the start of the year.
  • Clock Events Provider. The Clock Events Provider publishes specific values at specific time intervals. You can configure a unique time for each event, and also include or exclude specific days of the week. While enabled, the provider calculates the current time period and determines the current active event, publishing that value first.
  • Counter Provider. The Counter Provider publishes an ascending or descending count based on start and end values and an increment (for example, 1 2 3 4 5 6 7 8 9 10, or 10 8 6 4 2). You can configure the counters to increment or decrement on Read Requests or at a fixed interval, and you can also configure the counters to be writeable, allowing other applications (for example, DCS) to post values back to the counter, which can then be consumed by another application.
  • Data Converter Provider. The Data Converter Provider assembles data from other providers, applies rules to that data, and then republishes the results to the DMS DataStore under its own name and items. Because of this behavior, the Data Converter Provider is both a client to other Providers as well as a Provider itself.
  • Database Provider. The Database Provider retrieves data from tables a database, assembling and publishing data to the DMS DataStore. Using a SQL query (including expressions and derived values) that is valid to the OLE database, you can access nearly any data, even data from other systems.

  • GE iHistorian Provider. The GE iHistorian Provider connects to the GE/Fanuc iHistorian servers, assembling and publishing data to the DMS DataStore. Similar to the OPC, the iHistorian can transfer data and commands between PCs and shop floor equipment (for example, PLCs) through the iHistorian SQL database.

    The GE/Fanuc iHistorian server is a software package that was installed with your PLC or other equipment. InfinityQS International is not responsible for the GE/Fanuc iHistorian server.

  • Grid Data Provider. The Grid Data Provider parses data streams from serial devices, TCP/IP devices, columned data files (for example, tab- or comma-delimited files), or DMS items, converting the data into records based on user-defined formatting rules, and then publishing the records to the DMS.
  • JSON Provider. The JSON Provider queries a remote API resource, retrieving and parsing JSON data from a non-InfinityQS website, which can then be consumed by another application. After sending a request to and receiving a response from the remote server, the JSON Provider runs one or more queries against the data and publishes the results as individual consumable DMS items.
  • Mux Device Provider. The Mux (or multiplexer) Device Provider reads data through the InfinityQS mux device from multiple measuring devices, such as micrometers and calipers, attached to a single workstation. The Mux Provider can de-multiplex (or disassemble) data from the different measuring devices, publishing readings from each gauge independently.

  • OPC Provider. The OPC Provider connects to the OPC server, assembling and publishing data to the DMS DataStore, and can transfer data and commands between PCs and shop floor equipment (for example, PLCs).

    There are three versions of the OPC Provider (.COM, .NET, and UA), which correspond to newer and older OPC servers respectively. By default, use the .NET version, and if that doesn't work, use the .COM version.

    The OPC server is a software package that was installed with your PLC or other equipment. InfinityQS International is not responsible for the OPC server.

  • Simulator Provider. The Simulator Provider generates and publishes random values based on the current system time for testing purposes, allowing you to verify that the DMS system is operational and that the SPC software is collecting data properly.
  • Thermoworks WiFi Provider. The Thermoworks WiFi Provider monitors refrigeration and heat sources for Quick Service Restaurants (QSR), connecting directly to a Thermoworks WiFi (ThermaData) device via an Azure-provided IoT endpoint.
  • Timer Provider. The Timer Provider publishes specific values for ON state and OFF state at specific time intervals. When the ON interval passes, the provider publishes the ON value, and then when the OFF interval passes, the provider publishes the OFF value.
  • Wave Generator Provider. The Wave Generator Provider generates and publishes random, triangle, sawtooth, and square values for testing purposes, allowing you to verify that the DMS system is operational and that the SPC software is collecting data properly.

  • Wonderware Live Provider. The Wonderware Live Provider connects to the Wonderware server, assembling and publishing data to the DMS DataStore. The Wonderware Live Provider can transfer data and commands between PCs and shop floor equipment (for example, PLCs).

    The Wonderware server is a software package that was installed with your PLC or other equipment. InfinityQS International is not responsible for the Wonderware server.

  • XPath Data Provider. The XPath Data Provider extracts specific data selectively from an XML source. Because the XML Path Language (XPath) is defined and documented by the World Wide Consortium (W3C), you can find additional information about the specification at the W3C website here: http://www.w3.org/TR/xpath/.

    To use the XPath Data Provider, you must first familiarize yourself with the XML Path Language.

DMS Consumers

In the DMS, there are consumers that link the DMS DataStore to a receiving InfinityQS database, the InfinityQS Historian table, or another destination.

The available DMS consumers are:

  • Data Collection Service. The Data Collection Service (DCS) imports subgroup information from the InfinityQS Data Management System (DMS) into an InfinityQS database.
  • Historian. The Historian captures data from the providers and pushes that data into a database for future consumption. Using this data collection and retrieval system, you can store standard DMS data in a database table, and then query and link that data from other applications.

DMS Browser Interface

Activity State

The icon to the left of the provider name indicates the activity state of the provider, as follows:

DMS Provider is disabled.

DMS Provider is enabled. No data processed since being enabled or DMS service started.

(Icon solid) DMS Provider is enabled. Has processed data within the past 60 seconds, but not currently processing data.

DMS Provider is enabled. Data processed within the last 60 seconds contains one or more non-fatal warnings. After 60 seconds of no warnings, the status LED switches back to green.

DMS Provider is enabled. Data processed within the last 60 seconds contains one or more fatal errors. After 60 seconds of no errors, the status LED switches back to green.

(Icon flashing) DMS Provider is enabled. Currently processing data.

Device State

The DMS Browser displays providers as Enabled or Disabled, and may include the suffix (Remote).

  • Enabled. The provider is enabled and can publish to the DataStore.
  • Disabled. The provider is disabled and cannot publish to the DataStore.
  • (Remote). InfinityQS did not create the provider (it may have been created by third party software or temporarily created by the SPC software) or it is located on a different computer from the DMS. This means that you cannot manage the provider locally, and will not able to modify, disable, or delete the provider from this local computer.

You will need to manage the provider from the remote location where the provider resides.

DMS Toolkit

Using the DMS toolkit, you can create custom providers, which the DMS Browser displays as (Remote). You retain full control of your custom providers within your application development environment.