AI photo review for FMX work orders

Overview

An FMX maintenance request is a record of work authorized and work closed, not a record of what the space looks like. It holds a request type, a building, a location, the equipment involved, a due date, a description and an Attachments field where photos of the issue go. It moves through statuses that are hard coded in FMX, and it ends Finalized. What it cannot do is look at the photo a technician attached and tell you whether the room is actually in good repair. RapidEye reads those attachments, along with the building and location FMX already stamped on them, and returns a finding per issue: what it is, where it is, how bad, and the photos behind it.

How it works with FMX

FMX splits work into reactive and planned, and describes both in those words. The checks follow the same split, because the photos on each one answer a different question.

• Reactive maintenance requests. A requester photographs a stained ceiling tile or a broken handle and submits it from a phone. RapidEye reads that first photo and says what it sees, so the request that arrives with the description "door issue" arrives with a severity too.
• The photo at the end. A technician attaches a photo before moving the request toward Finalized. RapidEye compares it against the photo the requester sent and against the last time that location appeared, and flags the repair that was closed but not done, or the wall that got fixed and the carpet that got ruined doing it.
• Planned maintenance instructions. An instruction set is the step list a technician follows, and one of its step types is Attachments. Where a step asks for before and after photos of a filter, a belt or a fixture, RapidEye reads this month's against last quarter's on the same asset.
• Recurring inspections and checklists. A monthly PM checklist or a lift inspection produces the same photos every cycle from the same spots. That repetition is what a baseline is made of, and drift shows up against it long before anyone reports a problem.
• Equipment tagged with QR codes. FMX lets a requester scan a QR code on a piece of equipment to submit a request or see its history. Photos captured that way arrive already tied to the asset, which is the cleanest input this integration gets.
• Buildings, campuses and regions. FMX filters work, reports and assets by building, campus or region. Findings roll up the same way, so a district sees which school is drifting rather than a flat list of tickets.

Each finding names the building, the room or the equipment, the kind of problem, a severity, the photos it came from and a suggested next step. It lands in the RapidEye dashboard, and in a Slack channel or an inbox for the facilities office if you want it there. Your team decides whether a finding becomes a new maintenance request in FMX. Photos are the common case, not the limit: video walkthroughs, 3D scans and an inspection format your district already uses are all things we read, and the standard a finding is measured against is the one you set. If your input or your use case is not in the list above, ask.

How to connect FMX to RapidEye

1. Pick the buildings and the modules. Which buildings on your FMX site RapidEye should read, and whether that is maintenance requests, planned maintenance, or both. Every request already carries a building, a location and any equipment attached to it, so findings inherit that address for free.
2. Make sure the photos are there. FMX says request forms can be configured to attach photos, videos and documents, and instruction steps offer an Attachments step type. If a form your team uses has no photo step yet, add one, or use a RapidEye capture link that opens on any phone with no app to install.
3. Add RapidEye as a user. Users & Contacts, add a User, give it access to the buildings you chose. The modal has the details. Requesters and technicians keep the same forms and the same phones.

How a request carries photos through FMX

Checked against FMX's help centre, September 2026.

FMX calls its work orders maintenance requests, and its own help centre uses the two words interchangeably. According to FMX's help centre documentation (gofmx.com), a maintenance request is an authorization of maintenance, repair or operations work to be completed, and the form asks for a request type, a title, a building, a location, an optional person it was submitted on behalf of, any equipment involved, a due date, followers, a description, custom fields, and attachments, described there as the place for photos of the issue and schematics. FMX creates a unique ID for each one. So a photo does not float loose: it arrives stamped with a building and a location before anyone has looked at it.

What happens after that is a status ladder. FMX states these statuses are hard coded and cannot be reworded or edited, which is unusual and useful, because it means the same six words mean the same thing on every FMX site in the world. Below is the work request ladder, and what a photo attached at each rung is worth.

1. Pending DetailsThe request still needs details before it can move. A photo submitted here is the requester's version of the problem, taken before anyone with a toolbox has seen it.RapidEye reads this
2. Pending ApprovalSomebody has to approve or deny. FMX supports optional approval chains, so the approver is often deciding from the description and the photo alone.
3. Pending AssignmentThe request needs a technician. Automatic routing can pick one.
4. Pending ResolutionAssigned and waiting to be resolved. The technician sees it in the FMX Work List app, under Recent, Nearby or Overdue, and works from the phone.RapidEye reads this
5. Pending FinalizationResolved, and now a second person has to finalize the job. This is the one rung where somebody is explicitly asked to check the work, and in practice they are checking a list, not a photograph.RapidEye reads this
6. FinalizedResolved and finalized. The attachment stays on the record forever and is opened again only when someone goes looking.

Two more statuses sit off the ladder: On Hold, set for a reason the organization decides, and Overdue, which any request past its due date picks up. Planned maintenance runs a shorter ladder of its own, from Upcoming and Pending Assignment through Partially Completed and Pending Finalization to Completed, with Overdue applying there too.

What an instruction step can capture

Planned maintenance in FMX runs from instructions: named step lists like a monthly chiller checklist or a thirty day lift inspection, built in a step editor with an active-steps tab and a preview of what the technician will see. Each step has a type, and the types are the vocabulary of the whole inspection.

The two marked above are where condition actually lives. FMX's documented example for the Attachments type is before and after photos of a repair, and for the drop down type it is an equipment condition of Good, Fair or Poor. Both are judgments a person types in at the end of a job. RapidEye reads the photos underneath the judgment and tells you whether the two agree.

Can FMX tell you the condition of a space?

Only when a person says so. FMX gives that person good places to say it: the condition dropdown on an instruction step, the FIT Inspections module for California K-12 districts, where each of fifteen categories is marked OK, D for deficiency, X for extreme deficiency or NA and the results roll into a scored state report. That is a genuinely well-built inspection instrument, and it produces a number every district needs. What it records is an evaluator's determination, and the photo sitting next to it is evidence nobody re-reads. The integration adds the second reading: the same attachments, evaluated against every previous photo of that building and that asset, on every request rather than on the annual walk.

FMX integration FAQ