OpenText Internet of Things Platform - ServiceNow Integration and Automation

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

1. IoT Alert to Incident Creation for Critical Equipment Failures

When OpenText Internet of Things Platform detects abnormal sensor readings such as overheating, vibration spikes, pressure loss, or device offline events, it can automatically create an incident in ServiceNow. This gives operations and support teams immediate visibility into the issue and starts the response process without manual logging.

• Data flow: OpenText Internet of Things Platform to ServiceNow
• Business value: Faster response to equipment failures, reduced downtime, and improved service continuity
• Example: A manufacturing plant sends a high-temperature alert from a production motor to ServiceNow, triggering an incident assigned to the maintenance team with device details, location, and severity

2. Automated Work Order Creation for Predictive Maintenance

Sensor trends analyzed in OpenText Internet of Things Platform can identify early signs of asset degradation. When thresholds or predictive models indicate likely failure, the integration can create a maintenance task or work order in ServiceNow for planned intervention before a breakdown occurs.

• Data flow: OpenText Internet of Things Platform to ServiceNow
• Business value: Lower repair costs, fewer unplanned outages, and better asset utilization
• Example: A logistics company detects abnormal engine vibration in a fleet vehicle and automatically opens a ServiceNow maintenance request for inspection during the next scheduled stop

3. ServiceNow Change Management for IoT Device Configuration Updates

When IoT devices, gateways, or edge systems require firmware updates, configuration changes, or network adjustments, ServiceNow can manage the change approval workflow. OpenText Internet of Things Platform can provide device status, impact data, and deployment readiness to support controlled rollout decisions.

• Data flow: Bi-directional
• Business value: Better governance, reduced change risk, and improved auditability
• Example: Before updating thousands of connected sensors in a utility network, OpenText Internet of Things Platform shares affected device groups with ServiceNow, which routes the change for approval and tracks implementation status

4. Asset and Device Lifecycle Synchronization

OpenText Internet of Things Platform can send device health, usage, and location data to ServiceNow to enrich asset records. ServiceNow can then use this information to maintain a more accurate view of connected assets, support contracts, and service history across the enterprise.

• Data flow: OpenText Internet of Things Platform to ServiceNow
• Business value: Better asset visibility, improved support decisions, and more accurate lifecycle management
• Example: A field service organization updates ServiceNow asset records with live telemetry from connected pumps, helping support teams prioritize assets nearing end of life

5. Service Request Fulfillment for Connected Device Access or Replacement

Employees or field teams can submit service requests in ServiceNow for actions related to IoT-connected devices, such as replacement, reactivation, calibration, or access provisioning. ServiceNow can trigger workflows that interact with OpenText Internet of Things Platform to validate device status or update device assignments.

• Data flow: ServiceNow to OpenText Internet of Things Platform
• Business value: Streamlined request fulfillment, fewer manual handoffs, and faster turnaround times
• Example: A warehouse manager requests replacement of a faulty environmental sensor in ServiceNow, and the workflow checks device status in OpenText Internet of Things Platform before dispatching a replacement unit

6. Operational Dashboard Enrichment for Service Desk and Field Teams

OpenText Internet of Things Platform can feed real-time operational metrics into ServiceNow dashboards and records so support teams can see live device conditions alongside incidents, requests, and changes. This helps teams make faster decisions using both operational and service data.

• Data flow: OpenText Internet of Things Platform to ServiceNow
• Business value: Better situational awareness, faster triage, and improved collaboration between IT and operations
• Example: A service desk agent handling a complaint about a refrigeration unit can view current temperature, connectivity status, and recent sensor anomalies directly in ServiceNow

7. Closed-Loop Resolution and Status Feedback

After an incident or maintenance task is resolved in ServiceNow, the resolution status can be sent back to OpenText Internet of Things Platform to close the operational loop. This allows IoT monitoring rules to suppress duplicate alerts, update device state, or resume normal monitoring after remediation.

• Data flow: ServiceNow to OpenText Internet of Things Platform
• Business value: Reduced alert noise, better event correlation, and more accurate operational reporting
• Example: Once a technician replaces a failed sensor and closes the incident in ServiceNow, the platform updates the device status in OpenText Internet of Things Platform and clears the active fault condition

8. Compliance and Audit Tracking for Regulated Operations

In regulated industries such as utilities, manufacturing, and logistics, IoT events can be linked to ServiceNow records for audit trails, approvals, and evidence collection. This creates a traceable record of what happened, who responded, and how the issue was resolved.

• Data flow: Bi-directional
• Business value: Stronger compliance, improved accountability, and easier audit preparation
• Example: A utility company records a critical pressure sensor anomaly in OpenText Internet of Things Platform, then stores the related incident, approval steps, and remediation actions in ServiceNow for regulatory review