OpenText Internet of Things Platform - NetX Integration and Automation

Common Integration Use Cases Between OpenText Internet of Things Platform and NetX

1. Real-Time Asset Health Monitoring and Service Ticket Creation

Data flow: OpenText Internet of Things Platform ? NetX

Sensor data from connected equipment is streamed into OpenText Internet of Things Platform, where thresholds and anomaly rules detect early signs of failure. When a critical condition is identified, the platform sends an alert and asset context to NetX to automatically create a service ticket, assign it to the correct maintenance team, and prioritize it based on operational impact.

Business value: Reduces unplanned downtime, shortens response times, and helps maintenance teams act before failures disrupt operations.

2. IoT-Driven Work Order Prioritization

Data flow: OpenText Internet of Things Platform ? NetX

Operational data such as temperature, vibration, pressure, or location is used to determine the urgency of maintenance or field service work in NetX. For example, a production line asset showing abnormal vibration can automatically move its work order ahead of routine tasks, ensuring the most critical issues are addressed first.

Business value: Improves maintenance scheduling, reduces backlog risk, and aligns field service effort with actual equipment condition.

3. Closed-Loop Maintenance Feedback to IoT Monitoring

Data flow: NetX ? OpenText Internet of Things Platform

When technicians complete a repair or inspection in NetX, the resolution details, parts replaced, and root cause codes are sent back to OpenText Internet of Things Platform. This allows the IoT platform to refine alert rules, correlate recurring failure patterns, and improve future anomaly detection based on real maintenance outcomes.

Business value: Creates a feedback loop that improves predictive accuracy and helps operations teams reduce repeat incidents.

4. Connected Field Service for Remote Equipment

Data flow: Bi-directional

OpenText Internet of Things Platform monitors remote assets such as pumps, compressors, vehicles, or utility meters and sends exception events to NetX. NetX then dispatches the appropriate technician, while updates from the field such as repair status, parts usage, and completion notes are returned to the IoT platform for operational visibility.

Business value: Supports faster field response, better technician coordination, and a single operational view of remote assets.

5. Inventory and Spare Parts Replenishment Based on Asset Condition

Data flow: OpenText Internet of Things Platform ? NetX

When IoT data indicates that a component is nearing failure, OpenText Internet of Things Platform can trigger NetX to reserve or request the required spare parts before the technician is dispatched. This is especially useful for high-value assets where repair delays are costly and parts availability is critical.

Business value: Reduces service delays, improves first-time fix rates, and lowers emergency procurement costs.

6. Compliance and Audit Trail for Regulated Operations

Data flow: Bi-directional

In regulated environments, OpenText Internet of Things Platform captures device readings and event history, while NetX records maintenance actions, approvals, and technician certifications. Together, they provide a complete audit trail showing what the asset reported, what action was taken, who performed it, and when it was resolved.

Business value: Strengthens compliance reporting, supports audits, and improves traceability for safety-critical operations.

7. Operational Dashboards for Production and Service Teams

Data flow: OpenText Internet of Things Platform ? NetX

IoT telemetry is aggregated into operational dashboards that are shared with service managers in NetX. This gives production, maintenance, and customer support teams a common view of asset performance, active incidents, and service workload so they can coordinate responses more effectively.

Business value: Improves cross-team visibility, speeds decision-making, and helps leaders balance production uptime with service capacity.

8. SLA-Based Escalation for Customer-Facing Equipment

Data flow: OpenText Internet of Things Platform ? NetX

For customer-installed equipment, OpenText Internet of Things Platform detects service-impacting events and sends them to NetX with asset location, customer account, and severity details. NetX can then trigger SLA-based escalation, notify account teams, and route the case to the correct support group before the issue affects customer operations.

Business value: Improves customer experience, protects service-level commitments, and enables proactive support for connected products.