Facilities directors in SLED organizations manage some of the most complex operational environments in the public sector — aging infrastructure, limited staff, deferred maintenance backlogs, and occupants who expect problems resolved fast. Most of them are doing it with the same tools they had ten years ago.

The incumbent platforms — Brightly Asset Essentials, Eptura, and similar CMMS systems — are solid work order management tools. But none of them have a native AI intake layer. When an occupant has a problem, they fill out a form, call a number, or walk to the facilities office. When a technician is dispatched, they spend time tracking down asset history and maintenance records before they can diagnose anything.

That gap is exactly where an AI agent changes the equation.

What the Portal Actually Does

The Building Operations AI Portal is a dual-interface system built on Google Cloud. It gives occupants a conversational intake experience and gives technicians a live briefing tool — both grounded in the organization's actual facility data.

For occupants: Instead of a static form, they describe their issue in plain language. The agent asks targeted clarifying questions — building, location, nature of the problem — and creates a structured work order automatically. It checks for existing open tickets at the same location before submitting, and suggests the nearest available alternative facility if the issue will take time to resolve. No form. No phone call. No guesswork about what information to include.

Building Operations Occupant Portal — conversational work order intake
Occupant portal — conversational work order intake with building and location triage

For technicians: Before dispatch, they click a single button and receive a complete pre-field briefing in one response — all open tickets in the building, asset details for the equipment in question, similar historical tickets with resolution notes, and a field prep summary. On site, they can query the agent for vendor documentation, part numbers, and diagnostic procedures in real time.

Building Operations Technician Portal — pre-dispatch briefing
Technician portal — pre-dispatch briefing with asset history, open tickets, and field prep summary delivered in a single response

"The technician briefing is the part that surprises people. Four steps of research — asset details, open tickets, similar history, field prep — delivered in one response before they leave the building."

Why Facilities Teams Adopt This Faster Than Almost Any Other Use Case

Three things make building operations the fastest path to visible AI value in a SLED organization.

  • The incumbent has no AI competitor. Brightly Asset Essentials is a strong work order platform. It has no native AI intake, no conversational interface, and no technician briefing capability. There is no feature comparison to win — the AI layer is entirely additive.
  • The buyer is non-technical. Facilities directors and operations managers evaluate tools based on whether they solve operational problems, not on architecture or platform strategy. The demo speaks for itself in five minutes.
  • The ROI is immediate and measurable. Fewer incomplete work orders. Faster technician dispatch. Reduced first-visit failures when the technician arrives without the right parts or information. These are metrics facilities teams already track.
4 steps
of pre-dispatch research — building tickets, asset details, similar history, field prep — delivered to the technician in a single agent response before they leave the shop.

How It Connects to Your Existing Systems

The portal is grounded in the organization's actual data — not generic AI trained on public information. Facility manuals, asset records, maintenance history, and vendor documentation are all indexed in a private Vertex AI Search environment. The agent queries that data on every turn. Nothing leaves your Google Cloud boundary.

Work orders created through the portal write back to the existing CMMS. The AI layer sits in front of the system the facilities team already uses — it does not replace it. Integration targets include Brightly Asset Essentials and Eptura Archibus, with a production migration path through the Nerdery delivery partnership.

What a Pilot Looks Like

A building operations pilot is scoped as a single-facility proof of concept. Asset and maintenance data for one building is loaded into a private Vertex AI Search instance. The occupant and technician portals are deployed on Google Cloud Run. The full build — data load, agent configuration, dashboard deployment — is completed within the Gemini Starter Pack service hours.

Most facilities teams have a visible result within the first week of use. The work order intake quality improves immediately. The technician briefing capability is usually the moment the team asks about expanding to additional buildings.