The CoreSpec Agent Team

Your agent can think. It cannot see, and it does not remember the building.

CoreSpec 3D is not an agent. It is the base layer, the MCP, the living twin every agent stands on. These are the agents. Most FM platforms now ship a version of the first three. We add the same two things to every one of them.

Book a walkthrough See FM 2.0

The loop

Four steps. Every other platform competes on one of them.

01 Ours

3D geometry in

Volume, topology, obstruction, path. Not a table of rows.

02 Anyone's

The task

Intake, dispatch, prediction, compliance. The familiar work.

03 Ours

3D you can act on

The answer lit up on the model, not buried in a list.

04 Ours

The twin gets truer

Every run writes back. Nobody types it in.

Step two is a commodity. Ten platforms shipped a named agent for it in the last eighteen months and they are all competent at it. Steps one, three and four are the whole product. Nobody else has them, because you cannot fake a building.

The roster

Six agents. One twin underneath all of them.

Intake Agent

Turns "it is freezing in here" into a real work order, with the right asset on it.

Everyone has this. Facilio Mira, Prism AI, ServiceChannel, Planon Assistant.

What CoreSpec adds

1 It sees where The request lands as a point in a real building, so the asset resolves itself. No ID to look up, no QR sticker on the wall, no guess to correct later.
2 It updates the twin Every confirmed request writes the room to asset link back into the model. The building learns what serves what, one ticket at a time.

Dispatch Agent

Decides who goes, in what order, and what they will hit when they get there.

Everyone has this. Nuvolo Dispatch AI, Corrigo, ServiceChannel routing.

What CoreSpec adds

1 It sees the path Routes by distance and floor, not just by trade and availability. The route is drawn on the building, with the lift, the locked door and the tenant hours flagged before the truck leaves.
2 It updates the twin Every arrival confirms or corrects where the asset actually is, and every access surprise is stored so the next tech never meets it cold.

Asset Health Agent

Predicts the failure, then tells you what the failure actually costs you.

Everyone has half of this. Fiix Asset Health, IBM Condition Insights, Nuvolo Predictive. They stop at the prediction.

What CoreSpec adds

1 It sees the blast radius The prediction lands on a map of what it takes down. Every room that goes dark, the tenants exposed, the headcount, and the valve to close first.
2 It updates the twin Every confirmed outage sharpens the served area graph, so the next prediction knows more about the building than the last one did.

Systems Agent

Checks the air side maths. Is this unit sized for the space it is actually feeding.

Nobody has this. It runs on cubic feet, and a floor plan only holds square feet.

What CoreSpec adds

1 It sees the volume Air changes per hour and zone balance need cubic feet. Starved rooms shade on the floor plate. Oversized units flag against the volume they actually condition.
2 It updates the twin Corrected equipment to space mapping, and the real thermal zones, including the ones a tenant fit out created and nobody wrote down.

Compliance Agent

Watches what expires, and computes the evidence instead of chasing the binder.

Everyone has half of this. Facilio compliance, Prism Document Intelligence. Certificates yes, geometry no.

What CoreSpec adds

1 It sees the evidence Egress routes, travel distance, equipment clearance and coverage computed from the model and drawn as the audit exhibit. Gaps shown in place, not listed on a page.
2 It updates the twin Verified device placements, logged clearance violations, and every manual and certificate pinned to the thing it describes rather than filed by name.

As Built Agent

Rebuilds the model out of the work that just happened. This is the one that closes the loop.

Nobody has this. You cannot reconcile a record against reality without holding reality.

What CoreSpec adds

1 It sees what changed Reads the close out photo, the parts used and the spoken note against the model, and shows the proposed change ghosted in place before anyone accepts it.
2 It updates the twin This one is the update. A numbered revision, diffable and reversible, traceable to a work order and a photograph. Every other agent depends on it.
Already have agents

Keep them. We are the two things they are missing.

Nobody is asking you to rip out an agent that already works. Maximo Assistant, Mira, Prism, Dispatch AI. They are all competent at the task. They are blind, and they forget. We fix exactly those two things, and we leave everything else alone.

Your agent → CoreSpec MCP → The living twin → back to your agent

Add one

Your work orders get a place.

Every request, route, prediction and inspection your agent produces resolves to a point in a real building, and comes back as something on the model. The list becomes a floor. The floor becomes a decision. Nothing about your workflow changes.

Add two

Your building updates itself.

What your agent finishes flows back into the twin as a new revision. Serial numbers, swapped parts, moved equipment, the sensor nobody logged. The next job starts from a building that is actually current, and no one had to type it in.

The specialist

Security Design Agent

Not an operations agent. A design one. It places cameras and readers against real walls and real obstructions, then writes the Division 28 spec ready to price.

1 It sees the coverage Field of view from lens, sensor and mount height, against every obstruction in the model. Blind spots you can look at instead of argue about in a meeting.
2 It updates the twin As installed truth, for when the camera lands four feet from where it was drawn and the coverage map quietly stops being right.

Standing one agent up is the easy part. Giving it a building to stand on is not.

Every one of these agents reads the same twin and writes back to the same twin. They cross reference each other and they remember the building between conversations. Ask about a change order and the as built agent confirms the field, compliance checks the code, systems checks the zone still balances, and asset health tells you what it exposes.

That is not a bot on a drawing. It is a team on a building.

Book a walkthrough See FM 2.0