The Gap Every IoT Platform Left Open
Industrial operations have been accumulating IoT deployments for a decade. Sensors are installed. Gateways are provisioned. Dashboards are built. Alerts are configured.
And still, in most facilities, the maintenance technician gets a text message when an alarm fires, walks to the machine, assesses the condition, goes back to a different system to create a work order, and documents the repair on paper or in a CMMS that has never seen the sensor data that triggered the dispatch.
The IoT platform did its job. The gap was never in the sensors or the connectivity. The gap was in what happened between “sensor detects a condition” and “operation responds correctly and learns from what happened.”
No one had built a platform organized around closing that gap.
ArgusIQ is that platform.
What ArgusIQ Is
ArgusIQ is an integrated operational intelligence platform — eight modules, one data model, one login, one source of truth for the physical operations it manages.
The word “operating system” is deliberate. An operating system doesn’t do one thing. It provides the foundation that lets everything else run — and ensures that everything running on that foundation can talk to everything else. ArgusIQ is that foundation for physical operations: every sensor, every asset, every space, every maintenance event, every work order, every alert, every AI query — on one platform with one consistent data model connecting all of it.
The Eight Modules
Asset Hub
The center of ArgusIQ’s data model. Asset Hub maintains digital twin records for every physical asset in the operation: identity (manufacturer, model, serial number, installation date, specifications), current state from live sensor telemetry, operational baseline computed from rolling historical data, health score derived from current readings relative to that baseline, maintenance history linked to every work order ever generated for the asset, and relationships to parent assets, peer assets, and dependent systems.
Asset Hub is the answer to the question no simple device management platform could answer: not “what is this sensor reading?” but “what does this reading mean for this specific asset, given everything we know about its history?”
A motor that normally runs at 84°F showing 91°F is different from a motor that normally runs at 89°F showing 91°F. Asset Hub knows the difference. Fixed thresholds don’t.
IoT Hub
The connectivity layer — but organized around assets, not devices. IoT Hub handles every protocol industrial operations require: MQTT, REST/HTTP, LoRaWAN, AWS IoT Core, Modbus RTU/TCP, OPC-UA, CoAP, LWM2M, Kafka.
When data arrives through IoT Hub, it doesn’t land in a device-centric record. It lands in the asset’s digital twin, enriching the data model that every other module reads from.
IoT Hub also manages OTA firmware updates for connected devices and cellular/SIM management for devices on mobile networks — so the connectivity infrastructure is maintained from the same platform that uses the data it produces.
Space Hub
Floor plans, site maps, SCADA diagrams, geofence boundaries — the spatial layer that maps sensor data to physical reality.
Operations teams think spatially. They know the north wall of Building 2, the basement pump room, the east parking apron. They don’t know device IDs. Space Hub bridges the gap: upload a floor plan, pin assets to their physical locations, and see real-time health status overlaid on the map of the facility.
RTLS live views for facilities with real-time location tracking. Multi-floor navigation for multi-story buildings. Zone-based alert filtering — show me everything in Zone 4 that’s in alert status.
CMMS
The maintenance management module — integrated with the IoT data model, not bolted on separately.
When the Alarm Engine detects a condition on an asset, CMMS can automatically generate a work order with the triggering condition, the current sensor readings, the asset’s maintenance history, and the recommended parts pre-populated from the asset record. The technician assigned to the work order sees all of this context before they reach the machine.
When the repair is complete, CMMS captures findings, parts used, labor hours, and post-repair sensor readings. That documentation updates the asset’s maintenance history in Asset Hub. The next alert for the same asset arrives with the context of every prior event.
Preventive maintenance scheduling in ArgusIQ CMMS can be driven by operating hours computed from sensor data, by condition triggers (schedule PM when health score drops below threshold), or by calendar — and each PM’s interval can adjust based on historical maintenance outcomes.
Alarm and Automation Engine
Six trigger types: threshold crossing, rate of change, duration above threshold, time-of-day, sensor offline, scheduled check. Logical combinations: AND/OR conditions, time-window constraints.
When conditions are met, the Alarm Engine can take multiple simultaneous actions: notify by SMS, email, or push notification; generate a CMMS work order; send a webhook to an external system; write a value back to a connected device; log the event to the audit trail.
No single alert needs to trigger a single action. A bearing temperature that’s been above baseline for more than 2 hours can simultaneously notify the maintenance supervisor, generate a work order, send a webhook to the parts ordering system, and start a timer that escalates to the plant manager if the work order isn’t acknowledged within 30 minutes.
Dashboard and Widget System
Twenty-five-plus widget types — gauges, trend charts, tables, heat maps, KPI cards, status indicators, geographic maps, floor plan embeds. Drag-and-drop layout configuration. Real-time data binding that updates without page refresh.
Dashboards in ArgusIQ are role-aware: the plant manager sees the site-wide health summary; the maintenance supervisor sees the assets currently in alert and the work orders due this week; the field technician sees their assigned work orders and the sensor data for the assets on their list.
Ticketing and Service Management
For operations where the workflow is service-oriented rather than maintenance-oriented — facility helpdesk, customer service queues, field service dispatch — Ticketing provides full ticket lifecycle management with SLA tracking, smart queue routing, and status visibility for both the team handling the ticket and the requestor who submitted it.
Tickets can be triggered automatically (same as CMMS work orders) or submitted manually. They tie to asset records the same way work orders do, giving every service event full context from the asset’s operational history.
Ask Argus
The AI natural language layer built into every module.
“Which assets in Building A have been in alert status more than twice this month?”
“Show me the maintenance cost per unit for all motors on Press Line 2 over the past 12 months.”
“What happened with Motor 14B between July 10th and July 15th?”
“Which assets are showing the early-warning pattern that preceded last quarter’s bearing failures?”
Ask Argus queries the complete ArgusIQ data model — telemetry history, maintenance records, alert history, asset identities, work orders, spatial data — and returns answers in natural language or as structured data visualizations. No SQL. No dashboard configuration. No waiting for an analyst to pull the report.
The Architecture That Makes Integration Real
The modules aren’t stitched together through APIs. They share a data model. When IoT Hub receives a sensor reading, Asset Hub updates immediately. The Alarm Engine evaluates against the updated asset state. If an alert fires, CMMS can generate a work order with the full asset context already populated. Space Hub reflects the new alert status on the floor plan. Ask Argus can answer questions about the event because it happened in the same data model Ask Argus reads.
This is what distinguishes ArgusIQ from a stack of integrated tools: there is no “integration” to maintain. There is one platform that does all of it, with one data model underneath.
Multi-Tenant, White-Label, Deployment-Flexible
ArgusIQ supports multi-tenant deployment for organizations that manage operations across multiple customers, divisions, or subsidiaries. The tenant hierarchy maps to real organizational structures: platform operator at the top, customer organizations as tenants, individual sites or divisions as sub-tenants. Data isolation between tenants is enforced at the platform level.
White-label configuration lets organizations deploy ArgusIQ under their own brand — custom domain, logo, color scheme, terminology — for their customers or internal divisions.
Deployment options: cloud (AWS or Azure, single-region or multi-region), on-premises for regulated environments, air-gapped for classified or ITAR-restricted deployments.
What ArgusIQ Is For
ArgusIQ is for operations that are done managing a technology stack. Facilities managers who need one system that handles everything from sensor to maintenance record. Operations directors who need visibility across 20 sites without 20 logins. Maintenance teams who need context when they get dispatched, not just a text message with a device ID.
It’s also for organizations building toward AI-driven operations. The data model ArgusIQ maintains — asset identity, operational baselines, maintenance history, alert patterns, labeled outcomes — is the foundation that makes AI-driven predictive maintenance possible. Ask Argus is the first AI capability; the data model supports more.
Deployment Timeline
ArgusIQ deployments follow a structured onboarding sequence:
- Week 1–2: IoT Hub provisioning — protocols configured, existing devices migrated
- Week 2–4: Asset Hub population — asset records created, devices linked, baselines initializing
- Week 3–6: Alarm Engine configuration — threshold logic migrated or built fresh, work order routing configured
- Week 4–8: CMMS activation — PM schedules loaded, parts inventory staged
- Week 6–12: Space Hub floor plans uploaded, devices pinned, spatial dashboards live
- Month 3+: Baselines mature, health scores stabilize, Ask Argus starts returning high-value historical queries
The order matters. Asset Hub has to know about the assets before the Alarm Engine can generate work orders with context. Baselines need 30 days of history before the health scoring is meaningful. The platform’s value accumulates over time — and the foundation has to be correct before the intelligence layer can work.
ArgusIQ Is Available Now
ArgusIQ is the next generation of Viaanix’s industrial operations platform — designed from the architecture up to be an asset-centric intelligence platform, not a device management system with intelligence features added later.
For organizations evaluating the platform, the right starting point is a conversation about the operation: what’s connected, what’s managed, what questions you’re currently unable to answer, and what the path to operational intelligence looks like for your specific environment.
Talk to our team about ArgusIQ for your operation.