Data Panda brings your IFS Cloud 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.
IFS (Industrial and Financial Systems) was founded in 1983 in Linköping, Sweden, where its headquarters still sit. The product targets asset-intensive industries: aerospace and defence, discrete and process manufacturing, energy and utilities, engineering and construction, and field-service-led businesses. A single platform covers financials, supply chain, manufacturing, project management, enterprise asset management (EAM) and field service management (FSM), which is why companies that maintain expensive equipment over long lifecycles tend to consolidate on it. IFS Cloud is the current platform, replacing IFS Applications 10, and the company is privately held under EQT and Hg.
Pulling IFS into a warehouse is about the questions that sit between modules and between systems. Project margin in IFS Projects depends on labour from IFS HR, parts cost from IFS Supply Chain, and field-service hours from IFS FSM, and a Lobby report rarely lines those up cleanly. Add the CRM (Salesforce, HubSpot), the HR system (HiBob), and a financial subsidiary on Exact Online, and the warehouse becomes the place where the project P&L, the MRO turnover and the work-order SLA finally agree on the same numbers.
Project, asset, supply-chain and finance numbers on one view, not four IFS Lobby tabs.
Keep IFS in sync with the commercial, HR and finance tools sitting around it.
Use IFS history to forecast spares, project drift and asset failure on your own data.
Internal tools on IFS data for people who should not need an IFS seat.
A list of concrete reports, automations and AI features we have built on IFS ERP data. Pick the one that matches your situation.
Where is a project losing margin?
Project P&L per phase, with labour from IFS HR, parts from IFS Supply Chain, subcontractor cost and field-service hours from IFS FSM rolled in. The phase where margin slips, and whether the slip is hours, materials or scope creep, becomes visible before the project closes, not at the post-mortem.
Are we holding the right MRO inventory for the maintenance plan?
Spare-parts stock and turnover next to the IFS EAM maintenance schedule that consumes them, with lead times from IFS Supply Chain. Identifies the parts that are eating cash on shelves and the parts that are quietly causing planned maintenance to slip because they were not there.
Are field-service contracts profitable per customer?
Work-order revenue against the cost of the technician hours, parts and travel that delivered it, per customer and per contract. The contract where SLA penalties or unbilled work are dragging margin shows up against the contract that performs, not buried in a service P&L total.
Project P&L, plant-level result and multi-entity consolidation across IFS companies on one view, with the FSM and EAM cost lines that drive an asset-heavy business already attached. Group close stops waiting on the controller stitching together IFS Lobby exports.
Quote-to-project-to-revenue timing per rep and product line, tied back to Salesforce or HubSpot. Forecast accuracy is checked against IFS invoices and project completions, not against optimistic CRM stages.
Work-order completion, first-time-fix, supplier reliability and asset uptime in one place. The handoff between supply chain, maintenance and field service shows up as data, not as Monday-morning chases between three IFS modules.
Closed-won Salesforce opportunities drop into IFS as a sales order for a product deal or as a project for an engineer-to-order or service contract, with customer, items, scope and pricing mapped. Project status, milestone billing and invoice flow back to the opportunity, so sales and delivery see the same cycle from closed-won to recognised revenue.
HubSpot deals that reach closed-won open the matching customer, sales order or service contract in IFS, and contract status flows back to HubSpot. Marketing reports ROI against revenue recognised in IFS, not against a forecast number that never matches the project ledger.
New hires, role changes, absences and leavers in HiBob push into IFS HR as resource records, with skills, cost rates and site assignments aligned. Field-service planners and project managers see the right people available with the right certifications, instead of scheduling work to a technician who left last month.
Critical work orders nearing or breaching SLA in IFS FSM ping the right Slack channel, with the asset, customer, contract and the technician on the job already in the message. The next action is one click instead of three IFS screens, and the SLA conversation happens before the customer notices.
For groups running IFS in the operating company and Exact Online in a Belgian or Dutch subsidiary, we align chart of accounts, sync customer and supplier masters, and push journal totals between the two. One consolidated group P&L without re-keying invoices on either side.
IFS project phases, milestones and dependencies appear as boards in monday.com for the engineering or delivery team that lives there, while time logs and status updates from monday flow back into IFS Projects. Project managers stop maintaining a parallel plan and the IFS project ledger stays the source of truth for billing.
These are the 2 tables we currently pull from IFS ERP into your warehouse. Query them directly in SQL, join them to the rest of your stack, or build reports on top.
Missing a table you need? We can extend the sync. Tell us what is missing and we will build it for you.
You keep the reporting tool you already have. We connect it to the warehouse where your IFS ERP 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.
IFS Cloud is the primary path through its REST APIs and OData endpoints. For groups still on IFS Applications 10 or earlier, we connect through the same OData layer where exposed, or fall back to the database extracts. The warehouse schema lines up regardless, so reports survive the IFS Cloud upgrade rather than needing a rebuild.
Custom fields, custom logical units and the data behind Lobby pages come across as first-class columns and tables in the warehouse. Existing Lobby reports stay as a reference so downstream dashboards can mirror the logic, but the warehouse version uses native SQL joins instead of the IFS reporting engine, which is where most of the speed-up comes from.
We review your IFS ERP setup and the systems around it. Together we pick the first thing worth building.