Read-only by design
Valqor reads historian, alarm, maintenance and log data. It never writes to the control system or changes a setpoint.
Valqor is built for operational technology environments. It reads data and never writes to control systems. It can work from exported files or run inside your own network.
Valqor reads historian, alarm, maintenance and log data. It never writes to the control system or changes a setpoint.
Work from exported files in a Valqor-hosted environment, or run Valqor inside your network in the Level 3.5 DMZ, connecting outbound only.
Use cloud-hosted or locally hosted models, depending on your site’s policy.
Tag names and equipment IDs can be anonymized before data is shared, as long as the renaming is consistent across sources.
Data is kept confidential, used only for your investigations, and deleted on request.
Every finding links to the record behind it, and an engineer reviews it before anything is acted on.
When connected, Valqor runs at Purdue Level 3.5. It reads from site operations systems and never reaches the control network.
No. Valqor reads from the historian, alarm logs and maintenance systems. It has no access to the control network and never writes to it.
Yes. Valqor can work from files your team exports, such as historian data, alarm logs and work orders, with nothing installed at your site.
Inside your network, in the industrial DMZ at Purdue Level 3.5, reading from your Level 3 systems and connecting outbound only.
It can use cloud-hosted or locally hosted models. Which one depends on your site’s rules on where data may go.
Yes. Tag names and equipment IDs can be replaced with neutral labels. The meaning and units of each tag need to stay clear, and the renaming has to be consistent across files.
Only your team and the people you choose to share them with.
We’re happy to walk them through how Valqor is deployed.
Talk to us