A few practical answers.
Your system, your data and what it takes to get started.
What would we receive in a first pilot?
A working simulated system, agreed operating scenarios and recordings your team can review and use for training. The current HVAC reference offer covers one system with up to 35 points in two stages over 8–9 weeks. Your written proposal confirms the scope, timing, price and acceptance criteria. Live plant integration is a separate step.
What do we need to get started?
One operational question, the available equipment documentation and an expert who understands the system. No live plant access is needed to begin with a simulator. We agree what information and time your team will provide before starting.
Who is ArcUI for?
Engineering and commissioning firms, and plant teams responsible for investigating incidents or training operators. The initial commercial focus is HVAC and controlled environments. The public product video uses a wind-turbine demonstration.
Does the agent act without a person?
Actions the agent proposes wait for human authorization. Separately, an expert can configure predefined alarm automation under agreed policies; its execution is recorded. The initial pilot uses a simulator, and any later connection to plant equipment starts with the agreed access limits.
Do we have to use a headset?
No. Desktop supports everyday investigation and review. PC VR and standalone mixed reality offer additional ways to explore the system. ArcUI uses OpenXR; device and feature compatibility are confirmed for your deployment.
Does our data have to leave the site?
ArcUI supports local deployment of the twin, rules and recordings, with a locally hosted AI model or an external provider you choose. Offline operation requires all selected models and services to be available locally. We agree the data flow when scoping the deployment.
What can ArcUI connect to?
Start with a simulator or imported historical data. Supported integration routes include OPC UA, MQTT, Modbus TCP, REST and WebSocket; BACnet uses a gateway. The selected source and its behavior are tested as part of integration. Your existing control system and historian keep their roles.
What does a recording contain?
The recorded context, decisions, authorizations and observed outcomes. Incident windows are captured around alarms and actions; REC captures a full session. Your team can retain readable exports and reopen recordings in a compatible ArcUI runtime.
How does the system learn?
Recorded sessions can support proposed changes to operating knowledge. An expert reviews each change and its evidence before approval. This is reviewed knowledge, not automatic model training.
Explore the Learn step →Does ArcUI replace a safety or validated quality system?
No. The pilot supports investigation and training. Your PLC, safety interlocks and validated quality records keep their jobs. Any production use, permissions and validation requirements need a separate agreed scope.
How is it purchased?
The simulated pilot is a scoped service. Integration into a site is quoted separately, reusing the agreed work from the pilot. Continued production use is licensed annually per site; support and service levels are separate when required. Prices, any pilot credit and the licence start date are stated in the written proposal.
Bring one operational question. We’ll define a first scenario, show what ArcUI can do and agree how your team would judge success.
Discuss a pilot →