MOPS OPC UA
OPC UA is the next generation of OPC technology. OPC UA is a more secure, open, reliable mechanism for transferring information between servers and clients. It provides more open transports, better security and a more complete information model than the original OPC, “OPC Classic". OPC UA provides a very flexible and adaptable mechanism for moving data between enterprise-type systems and the kinds of controls, monitoring devices and sensors that interact with real world data.
OPC Unified Architecture (UA) follows today’s and future requirements of industrial communication needs. It unifies and extends the individual standards of the first generation OPC (also called OPC COM or OPC Classic) using a service oriented architecture (SOA) paradigm. This result is platform independent, scalable and high-performance communication infrastructure. The use in small devices of process and measurement technology with their specialized operating systems is just as well possible as the use in enterprise applications on Unix/Linux machines or Mainframes.
The rich information model can represent complex relationships of data and its semantics. Specially designed transport protocols offer highest communication speed and interoperability.
Furthermore OPC UA provides security mechanisms like authentication, authorization, encryption and data integrity based on the latest cryptographic standards such as PKI, AES, and SHA.
MOPS OPC UA – receives data from one OPC UA server and writes the data (possibly modified using calculation) to another OPC UA server.
MOPS OPC UA is a communication application designed to exchange data between OPC UA servers where MOPS Historian can be the data destination or source. This information can be processed and entered into the MOPS Historian database. See How MOPS OPC UA interacts with MOPS Historian for system overview. Once configured and started up, this program will run continuously until explicitly stopped by issuing the proper command.
Features of this product:
· Receives the updates from an OPC UA server and stores the data in the MOPS Historian database
· Sends out data from the MOPS Historian database and updates an OPC UA Server
· Replicates data between OPC UA Servers
· Displays communication statistics via the standard performance monitor
· Buffering, recovering and acknowledgments of transmitted data
· Heartbeat for connection monitoring in both directions; i.e. the server as well as the client recognize failures
· Redundancy support on client and server side, multiple redundancy