The Connected Product Opportunity
Every category of industrial equipment — pumps, compressors, HVAC units, generators, industrial vehicles, refrigeration systems, power tools — is becoming a connected product. Customers expect remote monitoring, diagnostic alerts, performance analytics, and service scheduling from the equipment they buy.
The manufacturers who offer these capabilities are differentiating from those who don’t. The question isn’t whether to build connected product capability — it’s how to build it without becoming a software company.
The path most manufacturers take: negotiate a contract with a white-label IoT platform provider, configure the monitoring experience their customers need, and launch the capability under their own brand.
ArgusIQ is built for exactly this path.
The alternative: white-label a platform that already has all of this, configure it for your product’s specific use case, and launch under your brand.
What White-Label ArgusIQ Looks Like
The Customer Experience
A pump manufacturer’s customer visits connected.pumpmanufacturer.com. They log in with their pump manufacturer account credentials. They see their fleet of installed pumps, the health status of each one, the maintenance schedule, and the recent alert history. The interface uses the pump manufacturer’s brand colors, logo, and terminology.
Nowhere in this experience does the customer see “ArgusIQ” or “Viaanix.” They are using “Pump Manufacturer Connected” — the manufacturer’s connected product offering.
The manufacturer’s customer support team receives alerts from the same system. When a pump at a customer site triggers an abnormal condition alert, the manufacturer’s service team gets the notification, can see the pump’s current sensor readings and maintenance history, and can dispatch a service technician with the full context of the issue.
The manufacturer owns the customer relationship. They own the data. They own the brand experience. ArgusIQ is the infrastructure underneath it.
The Technical Architecture
White-label ArgusIQ deployments use ArgusIQ’s multi-tenant architecture in a specific configuration:
- Platform operator: Viaanix (the OEM accesses the platform management layer)
- OEM tenant: The manufacturer’s management layer — sees all their customers’ deployments
- Customer tenants: Each of the manufacturer’s customers sees only their own installed base
The OEM sees every deployment. Each customer sees only their own. The data boundaries are enforced at the platform level.
Custom domain, logo, color scheme, and terminology are configured in ArgusIQ’s white-label settings. The OEM’s customers visit the OEM’s domain; they never resolve to a viaanix.com URL.
ArgusForge: Configuring the OEM Solution
White-labeling the platform is the brand layer. ArgusForge is what makes the platform fit the OEM’s specific product.
A pump manufacturer’s monitoring solution needs different configurations than a refrigeration equipment manufacturer’s:
Pump manufacturer:
- Device profiles for the specific sensor configuration (discharge pressure, suction pressure, flow rate, motor current, vibration) on each pump model
- Dashboard views showing pump performance curves with current operating point vs. design point
- Alert thresholds calibrated to pump operating limits (not generic IoT thresholds)
- PM schedule templates based on pump operating hours
- Cavitation detection logic from pump curve analysis
Refrigeration equipment manufacturer:
- Device profiles for refrigeration monitoring (supply/return temperatures, refrigerant pressure, compressor current, evaporator superheat, condenser subcooling)
- Dashboard views organized around refrigeration efficiency (COP, EER) and compliance (temperature vs. setpoint, excursion history)
- Alert thresholds from food safety temperature standards and equipment operating limits
- PM schedule templates based on operating hours and seasonal startup/shutdown
- Efficiency degradation detection from performance trend analysis
ArgusForge packages these domain-specific configurations so that each new customer site deployed under the OEM’s platform instantiates the correct configuration — device profiles, dashboard views, alert rules, PM templates — without the OEM needing to configure each deployment from scratch.
System Integrators: The Repeatable Solution Path
System integrators (SIs) face a different version of the same problem. The SI builds a custom IoT solution for Customer A over 6 months. Customer B wants something similar. The SI builds it again — or tries to adapt what was built for Customer A. Each build is partially from scratch.
ArgusForge + ArgusIQ changes this model for SIs:
- The SI builds an ArgusForge solution configuration for their domain (cold chain monitoring, predictive maintenance for CNC machines, water utility monitoring — whatever their specialization is)
- Each new customer deployment uses that solution configuration as the starting point
- Customer-specific customization is layered on top of the standard configuration, not built from scratch
- ArgusOps manages the ongoing operation of all customer deployments from one console
The SI’s competitive advantage is their domain expertise — the alarm logic that correctly detects bearing failure signatures, the dashboard layout that matches what maintenance supervisors actually need, the compliance documentation format that regulatory agencies accept. ArgusForge packages that expertise so it’s reusable, not rebuilt.
Revenue Models for OEM Deployments
OEMs building connected products on ArgusIQ can structure the commercial model in several ways:
Bundled hardware + monitoring: The monitoring subscription is included in the equipment purchase price (or first year free). Creates product differentiation without explicit SaaS discussion with customers unfamiliar with subscription models.
Equipment + monitoring subscription: Hardware sold, monitoring service sold separately on a per-asset, per-year subscription. Clear SaaS revenue line. Requires customers to see value before renewal.
Service contract + monitoring: Monitoring is bundled into the manufacturer’s service or maintenance contract. Natural for manufacturers with existing service contract programs — the monitoring data improves service efficiency and justifies the service contract value.
Monitoring-as-a-feature: No separate pricing; monitoring is presented as a standard feature of the connected product line, differentiated against competitors who don’t offer it.
ArgusIQ’s pricing for OEM deployments is per-asset, allowing the OEM to calculate their cost based on their deployed fleet and structure customer pricing accordingly.
What Makes an OEM Deployment Work
The technology layer is the easy part. The operational elements that determine whether an OEM connected product program succeeds:
Sensor configuration aligned to the product: The sensors on the equipment need to generate the data that makes the monitoring valuable. A pump without vibration monitoring doesn’t get the predictive maintenance benefit. This means the OEM either specifies sensors as part of the product BOM or provides a clear sensor kit that installers add during commissioning.
Service integration: The most valuable use of remote monitoring data is improving service efficiency — reducing truck rolls by diagnosing issues remotely, arriving with the right parts based on the sensor picture, catching issues before they require emergency service. The OEM’s service team needs to be trained on reading ArgusIQ alerts and using the platform data in the service workflow.
Customer onboarding: The customer needs to understand the monitoring capability at product installation, configure their alert contacts, and see early value from the platform. OEM deployments without structured onboarding have lower engagement rates — the platform access is mentioned in the manual and not much more.
ArgusOps for fleet management: As the deployed base grows across many customer accounts, ArgusOps provides the fleet health view that the OEM’s service and operations team needs — without logging into each customer account individually.
Talk to our team about white-label ArgusIQ for your hardware product line or system integration practice.