Data Panda brings your iFIX tag, alarm and historian data together with the data from the rest of your business. From one place, we turn it into dashboards, automations, AI workflows and custom apps your team uses every day.
iFIX is an industrial HMI/SCADA platform first built as FIX by Intellution, a Massachusetts vendor founded in 1981 by Steve Rubin. FIX 1.0 shipped in 1983 as one of the first PC-based HMI/SCADA products. The line evolved through FIX DMACS, FIX Hawaii and the 32-bit FIX32, then was re-released as iFIX once Windows NT was fully 32-bit. Intellution moved to GE in the early 2000s, became part of the Proficy family under GE Fanuc and later GE Digital, and now sits inside GE Vernova, the energy spin-off GE listed as a separate company on the NYSE on 2 April 2024.
What iFIX manages is a tag database of process variables read from PLCs, drives and field devices, with a Scan Alarm and Control engine on top, alarm and event handling, recipe management, a process database for distributed SCADA and tight pairing with Proficy Historian for time-series capture. It runs in water and wastewater, food and beverage, pharma, power generation, oil and gas, chemical and discrete manufacturing. The point of pulling iFIX out of the control room is not that the operator screens are bad. It is that tag history, alarm streams and batch records sit in OT formats the rest of your business never sees. Margin per batch, OEE that matches finished-goods yield, alarm fatigue versus actual incident rate, the lot trace from raw material through ship, all live across iFIX, the historian, the LIMS and the ERP. In a warehouse the OT and IT data finally read on the same timeline.
Tag history, alarms and batch records next to the ERP and quality data, not five operator screens stitched together by hand.
Move signal from the iFIX tag database into the ERP, MES and quality system without bolting another point-to-point on the control network.
Use historian time-series and alarm streams to predict failures, score recipes and find the deviation that mattered.
Small tools on iFIX data for people who do not need an HMI station to do their job.
A list of concrete reports, automations and AI features we have built on iFIX (GE Vernova) data. Pick the one that matches your situation.
Why does the OEE on the iFIX dashboard not match finished-goods yield in the ERP?
Plant OEE is built from iFIX tags counting good parts and runtime, while finished-goods yield in the ERP is built from posted production receipts after QA release. We pull both into the warehouse so the gap shows up by line, shift and product, with the in-process scrap, the QA holds and the rework loops named, instead of arguing across two screens.
How many of last quarter's critical alarms drove a real operator response?
Alarm history from iFIX joined to operator acknowledgement, the work order opened in maintenance and the downtime logged for the same minute. The board sees the share of alarms that turned into real action against the share that the team has trained itself to ignore, which is the data that drives a real alarm rationalisation pass.
If a customer reports a defect, which batches and raw lots are in scope?
Forward and backward genealogy from the iFIX batch record and the historian time-series back through the raw-material lot, and forward to every shipped pallet that came out of the same process window. The recall scope is the actual list of customers, not a wider conservative pull because the trace stopped at a missing entry.
Plant-floor cost lands in the same view as the GL: material, labour and energy per batch, OEE versus standard, scrap charged where it happened. Standard cost variance gets a real driver instead of a single line at month-end.
Promised dates that account for what the line really runs, not the planning ideal. Stock and lead time at quote stop being a guess once the iFIX downtime and yield trend land in the same view as the order book.
OEE, downtime, alarm rate and recipe parameters on one screen, joined to ERP yield and LIMS quality. Production, planning and quality argue from the same dashboard, and an alarm rationalisation pass is a query, not a six-month project.
Production counts, scrap and downtime reasons captured in iFIX post against the SYSPRO work order in real time, with material issues and labour bookings reconciled against what the line really ran. Plant managers and the controller see the same OEE versus BOM-cost picture, instead of arguing across an operator screen and a SYSPRO variance report a week later.
Plant OEE, downtime and recipe parameters from iFIX land in the same warehouse as F&O production orders, item costs and finished-goods receipts. Group operations sees yield gaps per line and product across legal entities, with the in-process scrap and the QA holds named, so the multi-site close reconciles to one number instead of fourteen.
For smaller manufacturers running Business Central as the ERP, iFIX feeds production output, downtime reasons and per-batch energy use into the BC production order. The plant manager and the bookkeeper see the same per-batch margin, instead of a finished-good consumption journal that always shows up off by a few percent.
For Belgian and Dutch manufacturers running Exact Online as the local ledger, iFIX batch records and energy consumption flow into Exact as cost-per-batch postings against the right cost centre and project. The plant cost the controller sees in Exact reconciles to what the line really did, instead of a flat overhead absorption that nobody on the floor recognises.
You keep the reporting tool you already have. We connect it to the warehouse where your iFIX (GE Vernova) data lives.
OAuth authentication. Read-only by default. We sign a DPA and your admin keeps the keys.
Data flows into your warehouse on your schedule. Near real time or nightly, your call. You own the data.
We build the first dashboard, workflow or AI feature with you, then hand over the keys. Or we stay on for ongoing delivery.
We set up the foundation. Your team builds on top.
Best fit Teams that already have a BI analyst or data engineer and want to own the build.
We build the whole thing, end to end.
Best fit Teams without in-house BI or dev capacity. You tell us what you need and we deliver it.
You do. It lands in your warehouse, on your cloud account. We don't resell or aggregate it. If you stop working with us, the warehouse stays yours and keeps running.
Near real time for most operational systems. For heavier sources we schedule hourly or nightly. You pick based on what the reports need.
No. If you don't have one, we help you pick one and set it up as part of the first delivery. Common starting points are Snowflake, Microsoft Fabric, or a small Postgres start.
Both, depending on what is available. iFIX has its own process database for live tag values and a tight pairing with Proficy Historian for time-series capture. Where Historian is in place we read the historian extract for high-resolution trend data; where it is not, we collect the iFIX tag, alarm and event tables directly. The warehouse model is the same either way, so reports keep working when Historian is added later.
iFIX deployments usually sit on a controlled OT segment behind a DMZ, separated from the IT network on purpose. We deploy the collector inside the OT zone or inside the DMZ depending on the site's reference architecture, push to the warehouse one-way, and never open inbound paths to the control system. Plant IT and OT review the integration before go-live.
We review your iFIX (GE Vernova) setup and the systems around it. Together we pick the first thing worth building.