TwinWorX by e-Magic
Different vendors. Different decades.
One model of your operation.
TwinWorX is an open, intelligent digital twin platform for operating and optimizing the built environment. It sits above the systems you already own and turns them into one live model that operations, energy, and IT all work from. Nothing gets ripped out.
Deployed across buildings, campuses, hospitals, infrastructure, and manufacturing operations.

Illustrative operator view.

INDEPENDENTLY RECOGNIZED
Gartner Tech Innovator, Digital Twins for ET/OT Providers
Verdantix Innovator, Verdantix Green Quadrant: Unified Building Orchestration Platforms (2026)
Microsoft Managed Partner, Azure Marketplace and AppSource
Four problems we hear in almost every first conversation
Every system has its own screen, its own naming, and its own alarms.
Piecing together what happened takes three logins and an afternoon.
TwinWorX connects them into one model of your operation, from any vendor and any protocol, including the ones the installer called closed.
Your controls vendor sets the price of every change.
Closed systems mean no competitive bids and no way out.
TwinWorX connects above them, and the model it builds belongs to you, so the next bid is open.
Alarms arrive without context, so people learn to silence them.
The same faults come back, and nobody can say what they cost.
TwinWorX traces each fault to its cause, ranks it by cost and by how often it recurs, and sends it to your work order system with the diagnosis attached.
Anything that touches the controls has to get past IT.
Rightly so. Building systems were not designed for the network they now sit on.
TwinWorX runs in your cloud tenant, in ours, or on your own servers. However it is deployed, every connection to your building systems is encrypted and authenticated. Commands come only from authorized users with the right role, life-safety systems stay read-only, and every change is recorded with who made it and when.
HOW TWINWORX WORKS
Most vendors sell you the destination.
We will also get you there.
Everything TwinWorX does reads from one model of your operation. Connect it once, name it once. What you do with it grows in three stages, and nearly every client starts at the first.



Built for where you are going.
Deployed for where you are.
A word about AI in buildings
Every algorithm is limited by the data underneath it, and in buildings that data is often not good enough to act on. Sensors drift and meters fail quietly.

A language model never acts on your building. TwinWorX Copilot, our own assistant (not Microsoft Copilot), can run on the model your organization already approved, so operational data never reaches a third-party model.
Dollar figures are engineering estimates, and we label them that way.
What this looks like in production
HIGHER EDUCATION - VENDOR LOCK-IN
$1M
Proprietary system upgrade avoided
An Integrated Facilities Management System being rolled out across the 214 building urban research university campus
About $500,000 saved on IT hardware, software, and services
About $1 million a year in maintenance now open to competitive bid
30 to 40 percent saving on future building systems, the university's own estimate
Healthcare · On premise
202
Patient room displays fed live over HL7
A 164-bed acute care hospital
147 bedside terminals for room temperature, lighting, and blinds
One on-premise instance, with no cloud connection permitted
HL7, REST, and BACnet/IP working together
HIGHER EDUCATION - SCALE & LONGEVITY
1,000,000
I/O points under management
A 225-building campus, 18 million square feet
1993 - Today
A client since 1993, continuously
19 server groups migrated in four phases, with the campus running throughout
More than ten control platforms, some from the early 1990s
Higher education · Sustainability reporting
15 from 1
Reporting frameworks from one data model
A 360-building research campus, six sub-campuses
99 buildings in one model
Weather normalized, so year-over-year comparisons hold up
Reports that took days now run without manual work
Why Pick e-Magic
We came from industry, not from buildings.
Our founders built AI process optimization for gold, copper, nickel, and diamond operations in the 1980s, and that company was acquired by ABB. Buildings are not the hardest environment we have worked in.
We build the platform, and we connect it.
The engineers who wrote TwinWorX integrate it with your systems, directly or with our partners, on brownfield and greenfield facilities. We work with any contractor or systems integrator, including yours. That is why the hard protocols get solved instead of scoped out.
Your model stays yours.
TwinWorX builds on the open ontology your domain already uses, not an e-Magic schema. If you replace us in ten years, you keep the asset you paid to build.
Unlimited points, buildings, and users.
The TwinWorX license has no per-point, per-user, or per-building charge, and the historian has no tag or retention limit.
The founders are still on the work.
Self-funded since 1998, with no venture capital and no acquisition timeline. Our founders are on every major engagement, and the engineers who built our longest-running system still support it.
WHERE TWINWORX IS USED
One platform, not a different product per sector.
Connecting a hospital and connecting a terminal are the same kind of project for us.

Start with a conversation, not a procurement process.
Thirty minutes with one of our engineers, not a sales development rep. Bring your systems list and your worst recurring problem. If TwinWorX is not the right answer, we will say so.
1
A 30-minute working session
We map your systems and where the silos are, with whoever owns the problem.
2
A scoped starting point
A few buildings or one system, to prove the model on your own data.
3
A decision on your terms
Buy direct, within your construction contract, on the Azure Marketplace with committed spend applied where you have a Microsoft spend commitment, or through Carahsoft for U.S. government.
Prefer to read first? See how it works → · Why e-Magic →










