To make humans superiorat solving problems.
Decision & Execution Control for construction and complex operations.
Expertise gaps
Slow decisions
Stakeholder opacity
No decision owner
Cost cascades
Disruption becomes cost for every hour nobody decides
Isotact solves it, executes it once released, and proves what changed
Isotact reads the whole operation — and takes one decision out of it
A plant, a data hall and a site all fail the same way: a part that is not where it was booked, an asset drifting out of spec, a contractor who has stopped answering. The signal exists in five systems and belongs to no one. Isotact holds the operating picture across all of them, works out what the disruption costs in time and money, and hands one prepared decision to the person with the authority — then executes it through those same systems and keeps the evidence.
Isotact · decision responsibility mapLive
From field risk to measured proof
Fragmented signals converge — one priced decision leaves with its owner.
Risk createdDecision waitingDecision ownedResult proven
Tap any node to see the risk it carries, who owns the decision, and what it costs.
Decision feedlive · MDC-1042
- 09:41MONITORINGReading signals across every field role
The map runs live. Hover any role to inspect it — click to pin.
Validated in simulation · sample project
Not reported.Solved.
Isotact solves the problems that stop the operation and the ones that block other people’s work alike — a pump that fails and takes the line with it, a part that never arrived, a defect found at handover, a contractor who stopped answering.
The solution is executed by Isotact through everything it has access to — the existing systems, the machines and equipment, and the people it communicates with. Shift and site leadership accept it, adjust it through feedback where needed, and carry out only what Isotact has no access to.
Isotact runs continuously — every site, every shift, all year. Select a case to see cost impact, owner, and next step.
Isotact · decision queue · all sitesLive
MDC-1042 · openedDecision required
Value at risk
€30,000
Read from
Procore (defect log, responsibility)PlanRadar (inspection status)Primavera (sequence)Email
Procore + PlanRadar REST, read-only · Microsoft Graph
- Detected
- Electrical defect E-114 unassigned for 3 days
- Affected workfront
- Zone B · drywall ready in 36h
- Decision required by
- Today, 14:00
Why this decision
- E-114 sits on the critical path to the drywall start — every other trade queues behind it.
- Zone C is a ready front for the same crew with no open inspection gate.
- 36h of crew capacity is exposed at the project cost centre's day rate.
- Recommended action
- Assign to electrical lead · resequence drywall to Zone C
- Approval
- Project Manager
Execution through
ProcorePlanRadar
Learned for the next case
Unresolved electrical defect before drywall start → flag earlier
Measured effect
Confirmed once the action runs
—
Value protected · last 24 hours€0
Validated in simulation · sample case
Nothing replaced. Everything orchestrated.
Isotact sits above the systems that already run your plants, data halls and sites — maintenance, procurement, dispatch, scheduling, process data and condition monitoring. Your tools keep their job. Isotact is the layer that actually operates across them: it reads their signals, works out the decision, and once a person releases it, executes it through everything it has access to — the systems, the machines and equipment, and the people it communicates with — then measures what changed. Nothing is replaced, and nothing runs without a person releasing it.
Signals rise · action routes back
Measure the work, not the reputation.
Closed decision cases leave a measured record of how a work package or operating unit actually operates.
Operating evidenceRead from 7 closed cases
Work package
Electrical · first fix
Critical path · Zones A–D
Where problems originate
7 / 7
closed cases began in this work package
How fast action begins
3.4 days
median from routed decision to first action
Whether handoffs move
2 / 7
handoffs moved on closure — 5 stayed blocked
Completed cases become operating evidence — never a rating, a leaderboard, or remembered opinion.
The Isotact Ontology of the Physical World
We connect what your systems keep apart.
A schedule records that task B follows task A. It does not record that a supplier email moved a delivery by five weeks, that the part reserved for it was booked to another job, or that the subcontractor has missed four other call-outs this month. Those facts sit in the ERP, in the maintenance system, in someone’s inbox — never in the plan. Isotact keeps one running model of the operation: work packages, equipment, parts, orders, crews, subcontractors, defects, and what each one blocks. It is built from the data your systems already produce and stays current on its own. Nobody maintains it by hand.
Physical fact
An electrical defect is open in Zone B.
Constraint
Inspection cannot release the drywall work.
forces a decision
Management decision
Move the crew to the ready workfront in Zone C.
changes the workfront
Next physical fact
Zone C is active while Zone B is corrected.
Future direction · not today's deployment
The second site does not pay for the first site’s learning.
A pump fails at one site. Three days to find the cause, four to source the part, and only then does someone establish that a temporary bypass would have kept the line running. The case closes. Six weeks later the same fault starts at another site and the whole sequence runs again from zero. This is what Isotact is built towards: when a case closes, the pattern behind it would be kept — the fault signature, the lead time that actually applied rather than the one promised, the action that worked, the cost of waiting. Equipment tags, names and locations stay where they are.
This operation
- Readings
- Orders
- Faults
- Schedules
- Releases
Raw operating data stays on site
The next operationRisk formingDecision prepared
Same risk — recognized earlier
The relevant management decision is prepared before the risk spreads.
The next operation starts prepared
Only the rule is carried over
Nothing would cross the boundary except the rule.
That is what would let this work between separate companies, contracts and tenants.
The same decision infrastructure could extend across the physical world.
Across all of them, the same situation: an order waiting on material that is reserved somewhere else, a contractor that has not come back, a maintenance window about to expire. Isotact reads that in the systems where it already happens — SAP PM, SAP MM, the CMMS, the process historian (OSIsoft PI / AVEVA), the MES, condition monitoring, the schedule and the inbox.
Construction
Energy networks
Data centers
Industrial operations
What Isotact is built for today
Rail
Manufacturing
Future direction · not today's deployment
The team behind Isotact.
Benedikt Bauch
Founder & CEO
- Three years of operational experience in the construction industry.
- Author of three published preprints in quantitative finance and financial mathematics.
- Winner, TUM.ai Midterm Pitch; advanced to the TUM.ai Final Pitch.
Founded Isotact to make humans superior at solving problems in complex environments.
Benedikt Bauch on LinkedInSamad Najm
Co-Founder & CTO
- M.Sc. in Statistics and Data Science, LMU Munich.
- Machine Learning Working Student, Texas Instruments.
- Machine Learning Research Assistant, Fraunhofer IIS.
- Winner, TUM.ai Midterm Pitch; advanced to the TUM.ai Final Pitch.
Builds Isotact's Operating Graph and decision infrastructure.
Samad Najm on LinkedIn
Contact the team: b.bauch@isotact.com
Request access
Show us a live project or operation
Tell us about a project or operation in flight. We’ll show you what Isotact would detect, what the stalled decisions are costing — and the priced, owned decisions it would hand back.
Share the role and operating context you want Isotact to read. The request opens in your email client for review before sending.