With millions in operating costs on the line, high quality has become a performance imperative. Larger organizations typically have plants spread across the globe, so how can quality performance be assessed if each plant has its own database, separate from the others? InfinityQS' Enterprise Integration Services (EIS) makes consolidating data a snap - even when data resides in separate databases, in different plants, or even in foreign countries.
EIS lets you easily route data from one location to another. As the name implies, EIS enhances your decision making power by allowing enterprise-wide quality data to be accessible from within a single interface. EIS runs in the background as a Windows Service, so no operator attention is required. ProFicient does not need to be running for EIS to route data.
Learn more about the benefits of using EIS for enterprise-wide integration of SPC data on our integration page or watch the below video for an in-depth look at the software.
Store and Forward Routing
Store and Forward Routing is set up on each ProFicient workstation. This ensures uninterrupted data collection, even if the network fails or the database goes offline. You can also use Store and Forward Routing to send department data to a particular site or to a shared corporate database.
With EIS, data can also be forwarded over the internet from one network domain to another. To perform this type of routing EIS must be running on at least two computers—one on each side of the Internet “cloud”.
Equipment Integration Routing
EIS allows ProFicient to connect to process automation systems and special test equipment, no matter how specialized or unique.
To simplify data routing, equipment manufacturers can automate data passing in the standard InfinityQS Data Exchange Format (IDEF), which also fits within this routing paradigm. Test equipment writes IDEF Measurement Data files which are then read by a File Reader and a ProFicient Measurement Data Writer.
How it Works
A Reader reads data from a data source, converts the data into the IDEF standard format, then dispatches the packets to a Writer.A Writer receives IDEF Packets from a Reader, converts the IDEF packets into appropriately formatted data and then publishes that information to a data source. Different readers and writers exist for connecting to different types of data sources.