Platforms
Product Lines
Platforms Safecrete Safewall Mine Operating System (Coming Soon)
On this page

Data Sources and Connectivity

Overview

IndustryOS Data Analytics connects directly to your existing databases using standard SQL connections. There is no data ingestion layer or ETL pipeline to configure — the platform queries your data sources in place.

Supported Databases

IndustryOS Data supports 60+ SQL-speaking databases out of the box:

Category Databases
Enterprise PostgreSQL, MySQL, SQL Server, Oracle, IBM Db2, MariaDB
Cloud Data Warehouses Snowflake, Google BigQuery, Amazon Redshift, Azure Synapse
Analytical Engines ClickHouse, Apache Druid, Apache Pinot, Presto, Trino
Open Source DuckDB, Apache Spark SQL, CockroachDB, CrateDB

Any database with a Python DB-API driver and SQLAlchemy dialect can be connected as a data source.

IndustryOS IoT Integration

The Data Analytics platform connects directly to the IndustryOS IoT time-series database, making all device telemetry, attributes, and alarm data available for analysis and visualization.

Available data:

Entity Description
Telemetry Time-series sensor readings across all connected devices
Attributes Device metadata, configuration, and status information
Alarms Alarm history with severity, status, acknowledgement, and resolution timestamps
Devices Device inventory with type, label, tenant, and activity status

Example queries:

1
2
3
4
5
6
-- Average temperature by device over the last 24 hours
SELECT device_name, AVG(temperature) as avg_temp
FROM telemetry
WHERE timestamp >= NOW() - INTERVAL '24 hours'
GROUP BY device_name
ORDER BY avg_temp DESC;
1
2
3
4
5
-- Active alarms by severity
SELECT severity, COUNT(*) as alarm_count
FROM alarms
WHERE status = 'ACTIVE'
GROUP BY severity;

No manual data movement is required. Telemetry is queryable as soon as it is ingested by the IoT platform.

Adding a Data Source

  1. Navigate to DataDatabase Connections
  2. Select the database type from the supported list
  3. Enter the connection string (host, port, database, credentials)
  4. Test the connection
  5. Save — the database tables are now available for charting and exploration

Security

  • All database credentials are encrypted at rest
  • Connections use TLS/SSL where supported by the database
  • Row-level security filters can be applied per role to restrict data visibility
  • All query activity is logged for audit compliance