Autonomous work.
Your rules.
Put AIMMS to work without giving up control. Protect your facility knowledge, set the access and approval rules, and keep your people in charge of equipment.
The control loop
- Ground
- Verify
- Approval gate
- Act
- Record
The questions your team needs answered.
Data, authority, access and deployment, before work begins.
Select a question to read the answer.
Who owns and controls our data?
Your organization retains ownership of its data. Customer-defined roles and permissions govern access, and the deployment defines approved data sources, retention, and protection controls.
Is our information used to train AI models?
Customer data is not used to train or improve EQUA or third-party models. AI processing uses approved context within the requesting user’s permissions.
Can AIMMS operate equipment or change plant controls?
No. Operational technology is read-only. AIMMS does not write to PLC, DCS or SCADA, issue setpoints or restarts, or bypass interlocks. Qualified personnel retain physical work and return-to-service authority.
Can we control autonomous transactions and spending?
Yes. Set roles, permitted actions, spend limits and approval routes for each workflow. AIMMS carries out authorized digital work within those rules, reducing routine coordination while keeping decisions with the required owner. Denied gates remain denied.
What happens when a fact or approval is missing?
The affected action stops. AIMMS makes the blocker visible, preserves the last known state and routes it to an authorized owner. The work resumes only after the required checks and approval.
How is access protected?
Enterprise identity, single sign-on, multifactor authentication and role-based permissions control access. Encryption protects data in transit and at rest. Access changes and digital actions are recorded for review.
How do deployment and retention fit our requirements?
Single-tenant and hybrid options support customer-defined data paths. We review the approved records, integrations, retention and deletion requirements with your team when scoping the deployment.
What can our IT and security team review?
Walk through identity and access, permitted data flows, encryption, retention, action records, backup and recovery, and incident response. Review the controls and configuration for your intended use before activation.
Tell us how your team works. We’ll make the next step concrete.
See AIMMS in actionWho can do what, and what gets recorded.
Your organization defines the roles, permissions, limits, and approvals for each workflow. AIMMS keeps its own operating record and can update connected business systems within those rules. Connections are mapped, permissioned, and validated with your team.
| Action | AIMMS authority | Human owner | Recorded evidence |
|---|---|---|---|
| Read a SCADA event or historian trend | Read-only | Operations | Source and timestamp |
| Detect an anomaly or deviation and raise a fault | Read-only | Operations | Signal, threshold and timestamp |
| Recommend the next check | Allowed | Technician decides | Cited evidence and procedure |
| Draft a work order or supplier RFQ | Allowed | Reviewer where required | Draft content and sources |
| Reserve a stocked part | Configurable | Maintenance lead | Transaction receipt |
| Send approved supplier outreach | Configurable | Named approver | Message, rule, and approval |
| Approve spend above the customer’s threshold or where policy requires | Human required | Named approver | Approval record and threshold |
| Place a purchase within customer-approved limits | Configurable | Customer policy and named workflow owner | Governing rule, permitted amount and transaction receipt |
| Update the AIMMS operating record | Configurable | Workflow owner | AIMMS record and action receipt |
| Write to an external CMMS, EAM, or ERP | Configurable | Customer policy and integration owner | Target-system receipt after activation |
| Write to PLC, DCS, or SCADA or execute a setpoint, restart, interlock, or actuator command | Prohibited | Qualified customer personnel | Outside AIMMS authority |
Enterprise identity in. Customer controls throughout.
Review identity, data, and model controls individually. Confirm the configuration, dependencies, and operating requirements for your deployment.
Access follows enterprise identity and role.
- Customer single sign-on, your identity provider authoritative
- Direct FIDO2 and WebAuthn enrollment for accounts you do not federate
- Phishing-resistant hardware security keys available to every user
- Recovery by registered second credential, with a named break-glass path
- Role-based access control by action
- Authentication, access change, and deprovisioning events recorded
Data and model controls, stated plainly.
- Encryption in transit
- Encryption at rest
- Data-retention controls
- Model-provider controls
- Customer-managed keys
Everything on this page is a product control we implement and can walk through during your security review. It does not represent a third-party certification, audit, or independent attestation, and we will not describe it as one.
Use operational context without giving AI control authority.
The boundary is on the write, not on the reading. AIMMS consumes the sources on the left, and it analyzes them: it detects anomalies and deviations, raises the fault itself rather than waiting for someone to notice an alarm, and surfaces slower drifts as work worth scheduling. What it may never do is on the right, and no permission level, administrator role or support request changes it. Detection is a read. Control is a write.
Read-only inputs
- Permitted SCADA events
- Historian context
- IoT and sensor telemetry
- Alarms
- Inspections
- Asset records
Permanent no-write boundary
- PLC, DCS, or SCADA writes
- Setpoint or restart commands
- Interlock commands or bypasses
- Actuator commands
- Relay, protection, or switching commands
When a dependency fails, AIMMS stops safely and leaves the work legible.
A missing fact, failed connection, denied permission, or rejected approval never becomes an invisible workaround. AIMMS contains the issue, preserves the record, and returns the decision to the authorized owner.
One deterministic safe-stop sequence
- Stop
Hold only the affected action and its dependent steps.
- Expose
Name the blocker, source, owner, and current state.
- Preserve
Keep the evidence, prior verified state, and action receipts.
- Route
Send the exception to the person authorized to resolve it.
- Revalidate
Resume from a verified checkpoint only after the blocker is cleared.
Five conditions that stay visible
Normal work continues where it is independent of the blocker.
- Condition
Stale or missing data
Safe responseHold the dependent recommendation or action. Show the source, timestamp, and missing fact instead of filling the gap.
Resume gateRevalidate the required facts. The last verified state remains unchanged until new evidence is accepted.
- Condition
Integration unavailable
Safe responseDo not represent the transaction as complete. Record the failed attempt and route it to the integration owner.
Resume gateReconnect, recheck permission and payload, then continue from the last verified checkpoint.
- Condition
Permission denied
Safe responseStop before the action. Record the denied scope and route it to the identity or workflow owner. Never switch identities or bypass policy.
Resume gateRetry only with a valid authorized identity and after confirming that the underlying facts have not changed.
- Condition
Approval held or denied
Safe responseKeep the action unexecuted. Preserve the decision and any reason supplied. A denial is never treated as a delay.
Resume gateA modified action returns for a new review. The original approval cannot be stretched to cover changed facts.
- Condition
Partial execution
Safe responseStop dependent downstream steps. Preserve receipts for completed steps and identify the first unconfirmed step.
Resume gateAn authorized owner chooses reconciliation, retry, or target-supported rollback. AIMMS does not erase completed real-world events.
AIMMS never writes to PLC, DCS, or SCADA and never executes setpoints, restarts, interlocks, or actuator commands. Qualified customer personnel retain operating, safety, engineering, and return-to-service authority.
AIMMS keeps its operating record and completes digital work in connected CMMS, EAM, ERP, inventory, and procurement systems. Your configured permissions, spending limits, approval rules, and validated connections govern those actions.
No silent substitution / No permission bypass / No unverified completion
Approvals you configure. Evidence you can inspect.
You decide where people approve and where policy is enough.
Approval requirements can be configured by action type, asset criticality, role, spend, supplier, safety condition, data confidence, and write target. Available decisions: approve, modify, hold, reject, escalate.
Drift protection: AIMMS revalidates material facts before a previously approved action is completed. Approval permits the reviewed action. It does not authorize changed facts.
Every permitted action is explainable, attributable, and reviewable.
- Action logs and action receipts
- Backup and disaster recovery
- Vulnerability scanning
- Incident-response process
Each receipt records
- Source facts
- Actor
- Governing rule
- Approval
- Time
- Attempt
- Result
- Evidence
Fit your operation. Keep your safeguards.
Deployment options
Single-tenant cloud or hybrid. Keep existing systems and repositories in place.
Customer-controlled data path
Connect approved facility records and read-only operating context while retaining customer-defined access and authority.
System connection coverage
Email · SCADA events · Historians · CMMS · EAM · ERP · Inventory · Procurement · GIS · Vendor portals
Customer activation
Mappings · Identity · Permissions · Network access · Customer approval · Validation before external writeback
Product connector capability and a customer's activated connection are distinct. Every customer connection is configured and validated in that environment. Your organization sets the permissions and approval rules for business-system actions.
Move work forward with confidence.
Explore the value for your operation and walk through the security, data, and authority requirements with the people who own them.