Finance Eye, FactoryEye Plant Finance, FactoryEye Analytics, and Plant Modeling, with one governed data layer underneath all four. Finance, plant operations, and IT each get their own view into the same trusted numbers. Start with the app that solves this quarter's problem. The others are already there.
1
Governed data layer under every app
100+
Pre-built connectors, floor to back office
18 in 18
Plants rolled out in 18 weeks
How it works
Pre-built apps, a governed data layer underneath them, and a way to extend either, all delivered by one team. Nothing subcontracted at any layer.
01
Finance Eye, FactoryEye Plant Finance, FactoryEye Analytics, and Plant Modeling. Ready to run, not built to order.
For finance and plant operations teams
02
Governance and AI enablement, built on Magic xpi. The layer that makes your data trustworthy enough to act on, and ready for AI.
For IT and data leaders
03
Customization with Magic SmartUX Studio. What you see isn't fixed: describe the app you need and Studio scaffolds it, on the same governed data.
For anyone with a different workflow
The apps
Bundled, it isn't four apps. It's one governed data layer that Finance, Plant Ops, and IT each get their own view into. IT approves one platform instead of four point tools, and nobody waits on a procurement cycle per app.
Finance Eye
Live now · Order entryProblem
Sales orders and vendor invoices arrive in any format (email, PDF, a spreadsheet) and get keyed in by hand, one at a time.
Solution
AI-assisted document capture extracts sales orders and vendor invoices automatically, flagging exceptions for review before anything posts.
Benefit
Exceptions surface immediately instead of getting buried. Orders and invoices move from inbox to ERP without anyone typing them in.
From inbox to ERP, without anyone typing it in.
Start with AI order entryFactoryEye Plant Finance
Problem
The plant controller loses days of every close to manual overhead allocation. Standard cost was set months ago, and nobody can say why a job's margin just moved.
Solution
Activity-based costing off real production data, connected through Data Hub and Magic xpi. Never written direct to the GL.
Benefit
Real allocated cost per work order while there's still time to act on it. The number the plant controller and the CFO can finally agree on.
Close the gap between your shop floor and your income statement.
Make the numbers trueFactoryEye Analytics & Plant Modeling
Problem
Plant-floor visibility is manual or end-of-shift. OEE, downtime, and quality events don't reach the ERP until it's too late to act.
Solution
Real-time OEE, automatic downtime capture, and quality traceability, computed from the plant-floor data Magic xpi already connects. No new integration to build.
Benefit
Faster answers on the floor, working alongside the MES and historian you already run. One more connected view, not one more disconnected point tool.
No new integration vendor. No rip and replace.
See what's actually happeningThe architecture
Source systems never talk to an app directly. Everything routes through Data Hub, built on Magic xpi, which is what makes the data governed and safe enough for AI to use.
Data Hub · built on Magic xpi
Governance + AI enablement. Schemas, roles, access control, one source of truth.
Governed apps
Finance Eye · Plant Finance · Plant Analytics · Plant Modeling
Studio
SmartUX · extend any app
AI · via Magic MCP
One governed path in, reachable by every app and by AI.
AI, governed
Whatever OT platform runs your floor, the same pattern applies: one governed connection, reused by every AI question.
Your OT platform
Ignition, Rockwell, AVEVA, or others
OT data backbone
Event streams
Magic xpi
Integration + governance
Magic MCP
Role-scoped AI access
Ask the plant, in plain language
Where this goes next
Every stage builds on the one before it. Nothing gets rebuilt to grow into the next.
1 · Land
Start with one app on your own data. Fast to stand up, and it proves the value on your own numbers.
e.g. AI order entry into your ERP
2 · Connect the floor
Magic Engineering connects the real floor systems: Ignition, Iconics, FT Optix, whatever is already there.
e.g. Machine and line data into Data Hub
Learn more3 · Expand to more apps
A second and third app read from the same governed feed. Each one adds value without a new integration project.
e.g. Vendor invoices, job cost, OEE
4 · Customize with Studio
Extend the workflow to fit your process, on the platform you're already running.
e.g. Your screens, your approvals
Learn moreOne platform, growing with you. Not a series of separate projects.
Where it fits
Illustrative scenarios for FactoryEye Plant Finance: the same activity-based costing engine, tuned to your process and mapped to your ERP.
| Sector | Use case | Primary ERP |
|---|---|---|
| Industrial Components · High-Mix | SKU Profitability | Epicor Kinetic |
| Job Shop · Contract Manufacturing | Quoting Accuracy | JobBOSS² |
| Aerospace / Defense · Tier 2 | Close-Cycle Speed | SAP Business One |
| Medical Device Manufacturing | Customer Lifetime Cost | NetSuite |
| Automotive Tier 1/2 · Stamping + Assembly | Is This Machine Earning Its Keep? | Infor SyteLine |
| Specialty Chemicals · Custom Formulation | The Formula Didn't Change. The Batch Did. | SAP Business One |
Platform reach
Magic xpi's 100+ pre-built connectors span everything from the plant floor to the back office. One integration layer, already fluent in the systems around your ERP.
OT / Floor
ERP
PLM
CMMS
Commerce
CRM
Docs / Files
Transport
A global manufacturer needed a practical path to Industry 4.0 without overhauling systems or stalling in another long pilot. FactoryEye proved the model in one plant, then replicated it across 18 plants in 18 weeks with structured sprint delivery.
18
Plants Rolled Out
18 weeks
Scale Timeline
90 days
Pilot Sprint
A short working session is enough to see which app fits first, and what your own data would show.
