Our communication integration enables maximum flexibility between existing SCADA or DSC utilizing industry standard OPC, MQTT or other protocols. The RIPA™ platform utilizes enterprise-grade third-party client-server communication software as part of its installation and integration with a client’s system.
The RIPA™ platform has been built agnostic to SCADA or DCS, leveraging industry-standard protocols to connect.
When deploying the RIPA™ platform, there is flexibility in setting both the polling rates for sending and receiving data from SCADA. Additionally, there is flexibility in setting the thresholds for commands to be sent. These work in unison to ensure the existing system is not overwhelmed.
The minimum specifications for a single system of moderate complexity are:
Intel i7 | 100 GB hard drive space | 32 GB Ram | Windows OS
The minimum requirements will vary depending on the complexity, type, and number of the system(s) being automated by the RIPA™ platform.
No. The RIPA™ platform is deployed on-premise.
The RIPA™ platform is deployed on-premise within the client’s existing firewalls on a separate VM from the SCADA or DCS within either the DMZ or operations environment.
I phase: PILOT
The pilot is performed on client infrastructure. Assets harnessing the power of CruxOCM in real-time validate full deployment business case.
II phase: PRODUCTION
Full deployment of RIPA™ across all asset types & facilities. Actualization of ROI is obtained in real-time for all assets.
Orchestration: Each deployment is facilitated by a deployment manager (who is the primary personnel), information, and WBS liaison between CruxOCM and a client.
Technical: Each deployment has a minimum of two primary and one secondary technical resource that facilitate the installation, MOC, point-to-point checks, testing, tuning, and various other milestones between CruxOCM and a client.
The RIPA™ platform can be deployed on greenfield or brownfield operations. The quickest deployments have 6-12 months of high-fidelity historical data available for initial model learning & tuning.
Like all great things in life, that depends.
Simple systems can be deployed very quickly (less than 5 months).
Complex systems, systems with low fidelity historic data or systems with missing telemetry to SCADA/DCS will require more time to deploy (more than 3 months).
No. As part of the deployment, the RIPA™ platform also has a module that enables the building of ‘soft sensors’ for telemetered data missing from the field equipment.
Yes! Complex systems, uncodified rules of thumb, institutionalized best practices, and mental models are where the CruxOCM software excels.
Please see an overview of our solutions here.
No. This is impossible due to the software’s deployment on a separate VM from the SCADA or DCS within either the DMZ or operations environment.
Any operator-initiated changes on their existing HMI screens are read into the RIPA™ platform in real-time, which initiates the automatic disengagement of any CruxOCM software currently enabled. An informational message is sent to the messages page.
Any permissives set in the field or on the SCADA/DCS are read into the RIPA™ platform in real-time. The RIPA™ platform will perform the required actions as defined in deployment.
All commands that CruxOCM software sends to the SCADA/DCS are written out to the client’s historian in real time.
The RIPA™ platform can handle various common upset conditions and be deployed with autonomous responses to common conditions.
The RIPA™ platform can handle the following types of common upset conditions:
Equipment Trips
Pressure & Equipment Nominal Operating Ranges & Limits
Transient Handling
Leak Detected
Yes. The CruxOCM and its RIPA™ platform are both ISO27001 and SOC2 Type 2 compliant.
No. The RIPA™ platform is deployed on-premise within the client’s existing firewalls on a separate VM within either the DMZ or operations environment.
CruxOCM conforms to each client’s specific IT security requirements for installing, deploying, and maintaining the RIPA™ platform. The following recommendations can be adjusted to conform to the specific security requirements of your organization:
Onsite or remote access to RIPA™ server in the target environment (remote preferred)
Service & support accounts in target environments
Per our ISO27001 and SOC2 Type 2 certifications, CruxOCM personnel adhere to stringent IT policies, training, and audits to ensure internal compliance is maintained to the standards required.
Physical data are stored (per any specific terms within a client’s agreement provisions) within the CruxOCM infrastructure using strong passwords, MFA, least privilege, and other security provisions as outlined in our IT policies.
A mutual NDA is put in place early on in discussions with any client to enable the two-way sharing of information that will be maintained confidentially.