Enterprise appliance transaction module

An enterprise appliance transaction module (EATM) is a device, typically used in the manufacturing automation marketplace, for the transfer of plant floor equipment and product status to manufacturing execution systems (MES), enterprise resource planning (ERP) systems and the like.

Solutions that deliver manufacturing floor integration have evolved over time. Initially they took the form of custom integrated systems, designed and delivered by System Integrators. These solutions were largely based on separate Commercial off the Shelf (COTS) products that a System Integrator acquired and integrated into the custom solution.

These solutions have evolved into vendor supplied product solutions that no longer require the integration of separate components. EATM products, as they are known today, are available as COTS Appliance products, fully configurable, and not needing any software development or custom integration.

Components required for EATM functionality

Hardware platform – embedded computer, computer appliance

Device communications software – Support for the device protocols from which data will be extracted. Device communications software typically operates through polled or change based protocols that are vendor specific. Data to be extracted is typically organized into related items, and transferred based on a machine status such as Cycle Complete, Job Start, System Downtime Event, Operator Change, etc.

Typical protocols; Rockwell Automation CIP, ControlLogix backplane, EtherNet/IP, Siemens Industrial Ethernet, Modbus TCP. There are hundreds of automation device protocols and EATM solutions are typically targeting certain market segments and will be based on automation vendor relationships.

Enterprise communications software – Software that will enable communications to Enterprise systems. Communications at this level are typically transaction oriented and require data transactions to be sent and acknowledged to ensure the data integrity. Examples include; Relational Database Adapters, Java Message Services (JMS), Oracle Database Interfaces and proprietary interfaces to specific products.

Transaction application – Software that is configured to watch and collect device variables, formats them into required transactions, and transfer the results securely and reliably to the Enterprise Solutions. The Transaction Application resides between the Device Communications and the Enterprise communications.

Enterprise solutions

Manufacturing solutions fall into many categories. Overall, the manufacturing environment is portrayed as a three layer Manufacturing Pyramid. At the base, Device Control Systems – Programmable Logic Controller (PLC) and Supervisory Control and Data Acquisition systems (SCADA) perform the process automation functions. A layer above that encompasses Plant Execution Systems that deliver the functions of; Asset Management, Genealogy, SPC, MES, Order Tracking, Quality Assurance and Scheduling. At the top most level, Enterprise Resource Planning (ERP) systems offer final control over the enterprise and track overall enterprise performance.

It is the job of EATM solutions to act as a bi-directional bridge between field devices and the supervisory control systems. These field devices could be located in a work cell or an assembly or process line. They could be very simple devices, or programmable controllers, machine controls, or PLCs. The upstream business systems could be ANDON and Kanban systems for that line, manufacturing execution systems (MES), and Archival Quality databases.

gollark: Where did you get the idea to make such bad quotes from?
gollark: Fonctional Prugramming.
gollark: Yes, that was used in the older version.
gollark: They're pulled from my proprietary API.
gollark: No, top 1% of "OSes" on the forums etc.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.