NATIVE INTEGRATIONS
Haltless integrates seamlessly with the world's leading industrial hardware and enterprise software. Explore our native compatibility below.
01 · CONNECTIVITY
Five ways to read your machines
Four open input protocols and one direct push API. The Python edge agent that ships with the platform speaks all of them.
OPC UA
Any compliant OPC UA server, including the latest spec with security policies and message signing.
Modbus TCP
Any Modbus TCP slave; supports holding registers, input registers, coils, and discrete inputs.
CSV file ingestion
Watch a directory; pick up MES exports and historian CSV dumps automatically after every shift.
JSON file ingestion
Same file-watch flow for JSON drops from legacy production systems and homegrown data pipelines.
REST API
Direct push from custom integrations using scoped, read- and write-capable API keys.
02 · PLC AND HMI COMPATIBILITY
Any PLC that speaks OPC UA or Modbus TCP
Both protocols are open standards, so the list below is illustrative rather than exhaustive. If your PLC exposes either, the edge agent reads it.
03 · ENTERPRISE SYSTEMS
Connect to the systems your business already runs
ERP, identity, and the historians your engineers already trust.
ERP adapters
Production adapters for SAP S/4HANA, Oracle EBS and Microsoft Dynamics 365: bi-directional work orders, parts reservations and cost rollups, with the same audit chain behind every write.
Identity and SSO
App-level OAuth 2.0 with PKCE for Google and Microsoft. Tenant-level SAML 2.0 or OpenID Connect for any Okta-, Auth0-, JumpCloud-, or Entra-compatible identity provider.
Historian bridges
OSIsoft PI and AVEVA PI reachable through their OPC UA bridges. Inductive Automation Ignition through its built-in OPC UA server.
04 · NOTIFICATIONS AND WORKFLOW
Ten outbound channels to the rest of your stack
Every alert routes to wherever your team already lives. We support these channels out of the box.
SMTP-based transactional email with templated bodies, retry on bounce, and per-tenant signing.
SMS
Short-message escalation through a regional SMS gateway, throttled per machine to keep noise out of the on-call.
Webhook
Signed POST to any HTTPS endpoint, with retries and a published payload schema.
05 · BI AND REPORTING
Plug your dashboards into Haltless data
A read-only REST API plus CSV exports for every report keep your BI stack in the loop.
REST API with scoped keys
Read-only API keys with fine scopes such as read:machines and read:sensors, so a BI integration cannot reach beyond what it needs.
CSV exports per report
Fleet, OEE, maintenance, downtime, and work-orders reports all export as CSV from the dashboard or the API.
Grafana panels
Pull machine health and OEE figures through the REST API into Grafana for your existing operations dashboards.
Power BI and Tableau
Connect to the REST API and refresh your Power BI or Tableau dashboards on the cadence your analytics team wants.
COEXISTENCE
Haltless does not replace your historian, SCADA, or CMMS
Haltless is designed to live next to the systems your plant already trusts, not on top of them. Three concrete patterns.
Historians stay your system of record
If OSIsoft PI or AVEVA PI is your long-term tag store, Haltless reads through their OPC UA bridges. We do not replicate years of historical data; we score the live readings and signal back into your historian when an alert fires.
SCADA and DCS stay in control
Haltless is a monitoring and analytics platform, not a control system. We do not write to PLCs, we do not close control loops, and we do not coordinate emergency-stop arrangements. Your existing SCADA or DCS keeps that responsibility.
CMMS hand-off, not displacement
If you already run MaintainX, UpKeep, Fiix, IFS, or Maximo, Haltless routes alerts in as work orders through the ten outbound notification channels (ServiceNow and Jira included) rather than forcing them into our own CMMS. The choice is per tenant.
COMMON QUESTIONS
Questions about connecting it up
Which industrial protocols does Haltless support?
OPC UA (IEC 62541), Modbus TCP, CSV file watch and JSON file watch are in production. MQTT, native Siemens S7 and EtherNet/IP via CIP are on the roadmap. If a machine only drops files somewhere, the file watchers are usually the fastest route in.
Will it work with our existing CMMS?
Alerts open work orders in the platform’s own CMMS workflow, and integrate outward to the enterprise systems you already run. Haltless complements SCADA, DCS, MES, ERP and your existing CMMS rather than replacing any of them.
How do alerts reach the people who need them?
Through ten notification channels, so an alert lands where a team already works rather than in one more dashboard nobody opens. The alert lifecycle and every signoff on it are recorded in the audit chain.
How long does it take to get connected?
Install the agent on a Linux box near the machines and point it at the PLCs. The detectors then need 24 to 72 hours to establish a rolling baseline before the first meaningful alert, because a z-score has nothing to compare against until it has seen normal.
