Home | Connectors | OpenText Information Archive | OpenText Information Archive - OpenText Internet of Things Platform Integration and Automation

OpenText Information Archive - OpenText Internet of Things Platform Integration and Automation

Integrate OpenText Information Archive Cloud Storage and OpenText Internet of Things Platform Internet of Things (IoT) apps with any of the apps from the library with just a few clicks. Create automated workflows by integrating your apps.

Common Integration Use Cases Between OpenText Information Archive and OpenText Internet of Things Platform

OpenText Information Archive and OpenText Internet of Things Platform complement each other well in environments that need both real-time operational visibility and long-term, compliant retention of machine-generated data. The IoT platform captures and processes device and sensor data, while Information Archive preserves selected records, events, and reports for audit, regulatory, and historical access. Together, they support operational teams, compliance teams, and IT in managing high-volume IoT data more efficiently.

1. Archive high-volume sensor data after operational use

Data flow: OpenText Internet of Things Platform to OpenText Information Archive

Sensor readings, telemetry streams, and device events are retained in the IoT platform for short-term monitoring and analytics, then automatically archived once they are no longer needed for active operations. This reduces storage pressure in the IoT environment while preserving historical data for trend analysis, audits, and investigations.

  • Useful in manufacturing plants with continuous equipment telemetry
  • Supports retention policies by device type, site, or data category
  • Reduces cost of keeping large time-series datasets in active systems

2. Preserve compliance evidence for regulated operations

Data flow: OpenText Internet of Things Platform to OpenText Information Archive

Organizations in utilities, pharmaceuticals, food production, and logistics can archive IoT records that prove operational compliance, such as temperature logs, pressure readings, calibration events, and exception alerts. The archive provides immutable, searchable retention for audits and regulatory reviews.

  • Supports proof of chain of custody for monitored assets
  • Helps satisfy retention requirements for safety and quality records
  • Enables fast retrieval during inspections or incident reviews

3. Decommission legacy monitoring systems while retaining historical IoT data

Data flow: OpenText Internet of Things Platform to OpenText Information Archive

When replacing older SCADA, historian, or device monitoring platforms with OpenText Internet of Things Platform, historical records from the legacy environment can be migrated into OpenText Information Archive. This allows the old system to be retired without losing access to past operational data.

  • Reduces maintenance costs tied to obsolete infrastructure
  • Preserves historical records for engineering and compliance teams
  • Supports phased migration with minimal business disruption

4. Store exception-based IoT events for incident investigation

Data flow: OpenText Internet of Things Platform to OpenText Information Archive

Rather than archiving every reading, the IoT platform can send only exceptions such as threshold breaches, device failures, connectivity loss, or safety alarms to the archive. This creates a durable record of incidents that operations, maintenance, and risk teams can review later.

  • Captures the most relevant data for root-cause analysis
  • Supports maintenance ticketing and post-incident reporting
  • Improves accountability for critical operational events

5. Retain asset lifecycle history for service and warranty claims

Data flow: Bi-directional, with OpenText Internet of Things Platform generating device history and OpenText Information Archive storing long-term records

For connected assets such as fleet vehicles, industrial machines, or utility equipment, the IoT platform can generate usage and condition history that is archived over the asset lifecycle. Service teams can later retrieve the archived record to validate warranty claims, maintenance actions, or customer disputes.

  • Creates a complete history of asset performance and events
  • Supports field service, customer support, and legal teams
  • Improves claim resolution with evidence-based records

6. Archive analytics outputs and operational reports from IoT monitoring

Data flow: OpenText Internet of Things Platform to OpenText Information Archive

Dashboards, daily summaries, compliance reports, and predictive maintenance outputs generated by the IoT platform can be archived as official business records. This ensures that the exact report used for decision-making remains available for future reference.

  • Preserves signed-off operational reports and KPI snapshots
  • Supports audit trails for management decisions
  • Useful for quality assurance and governance processes

7. Provide long-term access to retired device and site data for business continuity

Data flow: OpenText Information Archive to OpenText Internet of Things Platform, or archive as the system of record for historical lookup

When devices, production lines, or sites are retired, their historical telemetry and event records can remain accessible through the archive while new assets continue to be managed in the IoT platform. This gives engineering, finance, and compliance teams a consistent way to access historical operational data without keeping inactive devices online.

  • Supports post-retirement analysis and benchmarking
  • Maintains continuity for long-running infrastructure programs
  • Reduces clutter in active IoT dashboards and device catalogs

These integration patterns help organizations balance real-time IoT operations with disciplined information retention, lowering infrastructure costs while improving compliance, traceability, and cross-team access to operational history.

How to integrate and automate OpenText Information Archive with OpenText Internet of Things Platform using OneTeg?