Enterprise Integration Service (EIS)

(v. 5.4.9019)

InfinityQS EIS is a routing service that moves data from one location to another, which is accomplished by reading data from a data source, converting it into InfinityQS Data Exchange Format (IDEF), and then transferring and writing the contents of that IDEF file to a data destination.

In a typical EIS architecture, worldwide offices would collect measurement data and route this data up to the corporate headquarters for management, review, and reporting. Meanwhile, the corporate headquarters would maintain structural data (part names, process names, test names, specifications, etc.), and would push this data down to its worldwide offices.

EIS runs as a service, so no user interaction is required and no user needs to be logged into the computer running the service.

EIS Model

The EIS model is illustrated and explained below.

Standard Model

The EIS Reader reads data from the data source, converting it into an IDEF file, and then dispatches that data to an EIS Writer, which publishes the data to the data destination.

HTTP Model

More complex than the standard model, the EIS Reader reads data from the data source, converting it into an IDEF file, and then dispatches that data to an HTTP Writer, which transfers data over an HTTP port to an HTTP Reader. The HTTP Reader receives the data and then dispatches that data to an EIS Writer, which publishes the data to the data destination.

EIS Readers

In EIS, there are Readers that read data from a data source, converting it into an IDEF file, and then dispatch the file to a Writer.

The available EIS Readers are:

  • AQDEF File Reader (MDI). The AQDEF File Reader processes descriptor data from a file in Automotive Quality Data Exchange Format (AQDEF).
  • CMM Reader (Calypso). The CMM Reader (Calypso) routes subgroup information from the Calypso data files.
  • CMM Reader (LK-DMIS). The CMM Reader (LK-DMIS) routes subgroup information from the LK-DMIS data files.
  • CMM Reader (PC-DMIS XML). The CMM Reader (PC-DMIS XML) routes subgroup information from the PC-DMIS XML data file.
  • CMM Reader (PC-DMIS). The CMM Reader (PC-DMIS) routes subgroup information from the PC-DMIS data file.
  • HTTP Reader (*). The HTTP Reader processes data transferred using the Hypertext Transfer Protocol (HTTP), which would be useful when your ProFicient quality system running on one local area network (LAN) needs to transport data to a ProFicient quality system running on another LAN.
  • IDEF File Reader (*). The IDEF File Reader processes data from a file in InfinityQS Data Exchange Format (IDEF).
  • ProFicient Database Reader (MDI;UDI;EDI). The ProFicient Database Reader processes measurement data (subgroups), descriptor and limit data (structural), process event data, sampling requirements data, and employee security data from a ProFicient database source.
  • Text File Reader (TextFile). The Text File Reader routes text data files from a remote (UNC) location to a local folder, allowing DMS to process the data file.

EIS Writers

In EIS, there are Writers that convert the incoming IDEF packets from an EIS Reader into properly formatted data and then publish that data to the destination.

The available EIS Writers are:

  • Enact Writer (*). The Enact Writer writes subgroup data to Enact.
  • IDEF File Writer (*). The IDEF File Writer writes data to an IDEF file.

Reader – Writer Examples

Store and Forward Routing

In this example, you ensure that your workstations continue to collect data even when the network database is inaccessible, or you can route department data to a corporate database on the same network. This would use the standard model described above.

To forward workstation data, a ProFicient Measurement Data Reader reads subgroup data from the workstation database, converts it into an IDEF file, and then dispatches that data to a ProFicient Database Writer, which publishes the data to the network database.

Store and Forward Routing Over the Cloud

In this example, you can route data from one network domain to another. For example, you could route data collected in your production network domain to your corporate network domain. This would use the HTTP model described above.

To forward workstation data over the cloud, a ProFicient Measurement Data Reader reads subgroup data from the production database on a server, converts it into an IDEF file, and then dispatches that data to an HTTP Writer, which transfers the data over an HTTP port. On the corporate server, an HTTP Reader, which is listening on that HTTP port, receives the data and then dispatches it to a ProFicient Database Writer, which publishes the data to the corporate database.

Equipment Integration Routing

In this example, you route IDEF measurement data files, written by your test equipment, to a ProFicient database. This would use the standard model described above.

To route test data, an IDEF File Reader reads subgroup data from the IDEF file produced by your equipment and then dispatches that data to a ProFicient Database Writer, which publishes the data to the network database.

EIS Browser Interface

Activity State

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

EIS configuration is disabled.

EIS configuration is enabled. No data processed since being enabled or EIS service started.

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

(Icon flashing) EIS configuration is enabled. Currently processing data, with one flash per IDEF processed.

(Icon solid) EIS lost connection to database and is attempting to reestablish the connection. Once successful, EIS continues processing data.

(Icon solid for 1 minute) EIS configuration is enabled. Currently processing data, but there was a recent error.

Device State

The EIS Browser displays providers as Enabled or Disabled.

  • Enabled. The configuration is enabled and can process data.
  • Disabled. The provider is disabled and cannot process data.

Integration Strategies

Using EIS, you can route data between quality systems.

Integrating with Suppliers

If you outsource any part of your manufacturing operations and services to external vendors, EIS allows you to route data to or from those vendors. If your suppliers are already using ProFicient, you can route structural data to their ProFicient database while they route measurement data to your ProFicient database. If your suppliers are not using ProFicient, you should check with them to see if their internal quality system supports the InfinityQS Data Exchange Format (IDEF).

Integrating with Test Equipment

If your test equipment's controlling software application can output measurement results in different formats, you should check with the equipment manufacturer to see if their equipment supports the InfinityQS Data Exchange Format (IDEF).

Integrating with Enterprise Systems

If your MRP, MES, LIM, or other enterprise-level system supports the transfer of data in different formats, you should check with the software manufacturer to see if their software supports the InfinityQS Data Exchange Format (IDEF).

Integrating with Store and Forward

If your data collection must run without interruption, or if your operation requires you to process data on a local workstation and only upload to the corporate server once the job is complete, you can use EIS for Store and Forward integration.