How to connect Power BI to Ignition (MES/SCADA)

Inductive Automation Ignition (MES/SCADA) integration surface

• Historian SQL storage: tag history is held in partitioned data tables with a tag lookup table, in your chosen database such as SQL Server, PostgreSQL or MySQL. Naming and structure vary by version, so inspect your schema.
• Transaction Groups (SQL Bridge module) write selected tags to relational tables on a trigger, which suits production counts, batch records and recipes that you want in clean rows.
• Named queries and database connections let you build views over the data, and the Reporting module can produce scheduled extracts as well.
• WebDev endpoints can return JSON for small, near-live datasets, though they are not the right path for large history loads.
• Historian query functions return aggregated values with defined intervals, which you can write to summary tables on a schedule from a Gateway timer script.

How it works

1. 1

   Decide the data path

   Prefer a reporting database or read replica fed from the historian, so heavy Power BI refreshes do not compete with plant logging.

2. 2

   Build curated summary tables

   Create hourly and per-shift tables for production, state time, downtime and key process values. A Gateway timer script, a stored procedure or an ETL job can populate them.

3. 3

   Create reporting views

   Present clean views with friendly names, units, line and area attributes and a calendar and shift dimension, not raw tag IDs.

4. 4

   Install the on-premises data gateway

   Put the gateway on a server that can reach the SQL database. Configure credentials with a read-only account and schedule refreshes outside peak logging periods.

5. 5

   Model and measure

   Import summaries, use DirectQuery only for narrow cases, define OEE and downtime measures once in DAX, and document the definitions.

6. 6

   Add row-level security and Q&A

   Limit data by plant or line with roles, then enable natural-language questions over a tidy semantic model, with synonyms for your line and product names.

Security checklist

• Use a read-only SQL account limited to the reporting views, never the account Ignition uses to write history.
• Apply row-level security by plant and line, and review which workspaces and people can export data.
• Avoid exposing the historian database directly to the internet; route refresh through the data gateway.
• Mask or exclude fields that reveal customer, recipe or proprietary process details when sharing beyond the plant.
• Document dataset owners and refresh credentials, and rotate them on a schedule.