Connect & Manage Data
OTCognix supports multiple ingestion and data-management workflows depending on whether your signals come from on-site historians, MQTT brokers, direct HTTP clients, historical files, or operator entries.
Data Ingestion Paths
| Method | Best For | Where to Configure |
|---|---|---|
| OTCognix Field Agent | On-site PI Web API / historian connectivity via outbound certificate-verified WSS (field-agent-gateway). | Installed on-site Field Agent + Plant activation code |
| MQTT Publisher / Subscriber | Industrial IoT brokers and edge gateways (emqx-mqtt-bridge-service). | Telemetry → MQTT Publisher / Subscriber |
| Telemetry Ingestion API | Custom scripts, PLCs, or middleware pushing JSON readings over HTTPS. | Telemetry Ingestion API |
| Import Historical Data | Backfilling historical CSV/Excel datasets into plant tags. | Data Management → Import Historical Data |
| Manual Values | Lab results, shift logs, and non-instrumented measurements. | Data Management → Manual Values |
Data Quality & Sharing
- Data Integrity: Inspect coverage, gaps, stale tags, and data-quality issues under Data Management → Data Integrity.
- Data Collections: Package curated plant tags with consumer-safe aliases and share them internally or with external API consumers.
Next Steps
- Create Telemetry Credentials (MQTT & REST API) to authenticate gateways and ingestion scripts.
- Check Troubleshooting if a connected source is online but tags do not update.
- Review Developers & Integrators for API key setup and payload schemas.