Overview
Many tenders require that live and historical data be reachable by external reporting, business-intelligence, and analytics tools through standard SQL, often over ODBC or JDBC. ControlBird exposes its data over the PostgreSQL wire protocol, so any tool or driver that speaks PostgreSQL can connect and run SQL against current entity data and recorded history, under the same access control as the rest of the system.
Key requirements
- Standard query language
- Let external tools retrieve data using standard SQL rather than a proprietary API.
- Common connectivity
- Be reachable through widely supported drivers such as ODBC and JDBC.
- Live and historical data
- Expose both current values and recorded history to queries.
- Access control on data access
- Apply the same permissions to queries as to the rest of the system.
How ControlBird aligns
- Speaks the PostgreSQL wire protocol
- ControlBird presents a PostgreSQL-compatible endpoint, so the large ecosystem of PostgreSQL drivers, ODBC and JDBC connectors, and BI tools can connect without a custom integration.
- Query live and historical data with SQL
- Standard SELECT queries run against current entity data and against the historian’s recorded time series, including filtering by time range, for reporting and analytics.
- Read and write through one interface
- Beyond queries, inserts, updates, and deletes are supported over the same interface for tools that need to write back.
- The same access control applies
- Queries run as an authenticated user, so the role- and attribute-based permissions enforced in the data layer also govern what a query can see or change.
Need this for a tender?
We can provide deployment-specific detail and supporting documentation for procurement and security reviews.