Data collected within the RMS environmental monitoring system can be extracted and integrated into other systems via the following means:
•Open Platform Communication Unified Architecture (OPC UA). The OPC UA interface is a standard and secure way to enable data exchange between multiple systems without any custom programming due to the fact that the multiple systems understand OPC UA based upon a server (RMS)/client (3rd party system) setup. More details about the OPC UA option can be found here: RMS-WEB-OPC.
oData integrity: to ensure data integrity, the OPC UA interface is unidirectional only meaning that the server can send data to the client but the client (3rd party system) cannot send data to the server (RMS).
•Application Programming Interface (API). The API interface is not a standard, but secure way to enable data exchange between multiple systems, but custom programming is usually required. Rotronic supply users with all of the API data: API Function.
oData integrity: The API interface is bidirectional. However, to ensure data integrity, when sending data to RMS, a token generated by RMS is required (together with a user name and password for the system). Rotronic offer a specific software for data integration into RMS: RMS JSON API
•OSIsoft PI Server data historian. The OSIsoft PI Server interface can collect data directly from the MS SQL database directly. Rotronic have generated the HistoryView.sql file that generates the dbo.HistoryView. The Point Builder – PI System Management Tool needs to be configured to link with the dbo.HistoryView, then via the PI Interface Configuration Utility – RDBMSPI connector all of the data is collected. The RDBMSPI connector is added to the PI Server interface list. Rotronic AG recommend working with an OSIsoft PI specialist. The RMS license has been adapted in the V2.4 to meet the OSIsoft PI requirements (RMS-WEB-EXP).
oData integrity: The user must ensure that the OSIsoft PI Server has no write rights on the MS SQL database.
Validation: all interfaces can be validated. However, it is important to point out that when using a software that is custom (GAMP category 5 software) that designed/programmed by/for the customer, the validation will be more complex compared to the validation of a GAMP category 3 or 4 software (Off-the-shelf or configured).