Facility Operations
Facility Operations is the SmartFM and Inspector operations workspace for buildings, parks, plants, data centers, and other asset-intensive sites. It brings asset identity, operational digital twin context, alerts, work orders, worker task execution, energy records, FMS analytics, and evidence preparation into one governed operating surface.
Use this guide when a facilities, operations, maintenance, or ESG team needs to turn sensor events and inspection findings into reviewed actions, traceable records, and operational evidence.
Current service boundary
Facility Operations is implemented across several runtime surfaces:
| Surface | Current role |
|---|---|
| FactVerse frontend | Provides Inspector alerts, work orders, inspection workflow, energy views, platform asset center, FMS Lite, Green Mark views, maintenance calendar, maintenance windows, and worker mobile views. |
| Core backend | Provides work-order lifecycle, worker task execution, operations read model, audit timeline, Inspector binding, asset center inventory, model asset and twin-model binding APIs, energy records, FMS Lite, ESG, and Green Mark evidence APIs. |
| FMS submodules | Provide dashboard and route surfaces for chiller, IAQ, elevator, lighting, fire, parking, preventive maintenance, UPS, water, cleaning, inventory, contractor, space, billing, visitor, and feedback workflows. |
| AI Engine | Provides energy analysis, equipment profiling, benchmarks, Advisor chat, maintenance knowledge, knowledge graph review, reliability calls, HVAC/VAV diagnostics, chiller checks, EnergyPlus-oriented building simulation endpoints, and work-order text structuring. |
| DFS | Provides connector setup, source mapping, sync history, data quality review, governed datasets, and fusion recipes for BMS, work orders, inspections, meters, and equipment records. |
| Green Mark module | Provides Singapore Green Mark-oriented evidence workflow, ETTV and envelope assessment support, report assembly, and improvement calculation helpers. |
The Green Mark surfaces support evidence preparation and internal review. Certification, final submission strategy, and official assessment remain governed by the customer's appointed project and compliance owners.
What users can do today
The current application exposes these user workflows:
| Workflow | What users can review or perform |
|---|---|
| Operations read model | Review normalized alert and work-order records, open detail pages, read audit timelines, and inspect Inspector bindings. |
| Work orders | List, create, start, complete, assign, reassign, return, rate, reorder, comment, attach files, use templates, and review closed-loop records. |
| Worker execution | Accept or reject assigned work orders, update progress, complete work, review daily and monthly stats, run inspection tasks, check in, scan QR codes, upload photos or voice notes, and report field issues. |
| Field inspections | Review daily inspection summaries, open scheduled tasks, start and complete tasks, capture notes, issue counts, QR verification, and nearby stations. |
| Asset inventory | Review platform asset-center inventory and connect operational objects with 3D/BIM/CAD model assets and twin-model bindings. |
| Energy | Review energy dashboard data, meters, consumption, carbon, spatial energy data, and energy targets. |
| FMS Lite | Review equipment counts, alert states, life-cycle cost entries, RCFA records, alert diagnosis links, reliability statistics, and Weibull reliability calls. |
| FMS subsystems | Review subsystem dashboards and workflows for chiller, IAQ, elevator, lighting, fire safety, parking, preventive maintenance, UPS, water, cleaning, inventory, contractors, space, billing, visitors, and user feedback. |
| Green Mark evidence | Review clauses, evidence items, evidence packs, manual uploads, auto-collection, gap dashboard, and summary views. |
| AI-assisted review | Use Advisor, energy analysis, equipment knowledge, knowledge graph root-cause and impact review, work-order text structuring, alert explanation, SOP drafting, and nameplate extraction as operator review aids. |
Before you start
Prepare the tenant, asset model, and source data before using the workflow:
| Requirement | Notes |
|---|---|
| Tenant context | All operational records should resolve under the correct tenant. Many backend services read tenant context server-side. |
| Permissions | Work orders, worker views, operations read model, FMS, energy, ESG, Green Mark, and platform asset APIs use separate RBAC scopes. Confirm the operator has the required read or write scope before testing. |
| Asset identity | Equipment, model assets, spaces, stations, and source-system IDs need stable identifiers before operational records can be joined reliably. |
| Digital twin binding | 3D/BIM/CAD assets and component geometry should be linked to the correct twin objects when operators need spatial context. |
| Source mappings | BMS, meters, CMMS, inspection, worker task, and evidence sources should be mapped through DFS or another governed integration path. |
| Work ownership | Define who accepts alerts, creates work orders, performs field work, verifies completion, and reviews closed-loop outcomes. |
| Evidence ownership | For Green Mark or ESG workflows, define who reviews generated evidence, uploads manual evidence, and approves evidence packs before external use. |
For data preparation, start with Getting Started with DFS, Connect BMS to a Facility Twin, and Fuse Inspection, Work Order, and Sensor Data.
Open Facility Operations
Open the FactVerse application and use these current entry points:
| View | Route |
|---|---|
| Inspector alerts | /alerts |
| Inspector work orders | /workorders |
| Inspector inspection workflow | /inspections |
| Maintenance calendar | /maintenance-calendar |
| Maintenance windows | /maintenance-windows |
| Energy | /energy |
| Platform asset center | /platform/asset-center |
| FMS dashboard | /fms |
| FMS overview | /fms/overview |
| FMS RCFA | /fms/rcfa |
| FMS simulation | /fms/sim |
| FMS acoustics | /fms/acoustics |
| FMS optimization | /fms/optimize |
| Green Mark workspace | /gm-compliance |
| Green Mark dashboard | /gm-compliance/dashboard |
| Green Mark clauses | /gm-compliance/clauses |
| Green Mark evidence | /gm-compliance/evidence |
| Green Mark envelope assessment | /gm-compliance/envelope-assessment |
| Green Mark gap analysis | /gm-compliance/gap-analysis |
| Green Mark asset ontology | /gm-compliance/asset-ontology |
| Green Mark data ethics | /gm-compliance/data-ethics |
| Green Mark digital commissioning | /gm-compliance/digital-commissioning |
FMS subsystem modules also register their own dashboard and detail routes. Use the application navigation for the active tenant because module availability depends on tenant configuration.
Review assets and twin context
Start by confirming the asset and twin model layer:
- Open Platform Asset Center and review inventory categories.
- Confirm equipment and model assets are available for the tenant.
- Register or update model assets when new 3D, BIM, CAD, or geometry data needs to become part of the platform asset plane.
- Add model asset versions as geometry or source files change.
- Bind model assets, model asset versions, and optional component geometry to the correct twin objects.
- Use Inspector bindings to connect operational read-model items with Inspector context.
The platform model-asset API supports model assets, versions, component geometry, geometry retrieval, and twin-model bindings. Treat this layer as the shared asset identity plane for operations, Inspector, and digital twin workflows.
Run work orders and field execution
The work-order workflow connects alerts, field work, and operational feedback:
- Open Inspector Work Orders.
- Filter by status, equipment, or module loop when applicable.
- Create a work order manually or from a template.
- Assign or reassign the order to the responsible owner.
- Add sub-orders when work needs to split across teams.
- Attach photos, files, or comments as work progresses.
- Start and complete the order from the management UI or worker UI.
- Review closed-loop records after completion.
Worker views provide field execution APIs for accepting, rejecting, progressing, and completing orders. The worker flow also supports daily and monthly stats, nearby station lookup, QR scan matching, photo upload, voice upload, and preference updates.
Run field inspections
Use field inspections when a site team needs scheduled checks and evidence from the field:
| Step | What to verify |
|---|---|
| Daily summary | Review total, pending, in-progress, completed, issue count, and total duration for the selected day. |
| Task list | Filter scheduled inspection tasks by date and status. |
| Task detail | Review task title, equipment, location, checklist, notes, QR status, and issue count. |
| Start task | Move the task into progress and capture the start time. |
| Complete task | Capture notes, duration, and issue count. |
| Check-in and scan | Confirm site presence and QR match when QR-coded tasks or stations are used. |
| Issue report | Turn field issues into work orders for follow-up. |
Use inspection output as operational evidence only after the responsible reviewer confirms task scope, source identity, and attachments.
Review energy and sustainability signals
Energy and sustainability workflows use platform energy records, ESG records, and AI Engine analysis:
| Workflow | Current support |
|---|---|
| Energy dashboard | Summary view of metering and consumption state. |
| Meter management | List and create energy meters. |
| Consumption review | Query energy consumption over a selected period. |
| Carbon review | Review carbon-related energy output from the energy API. |
| Spatial energy data | Review energy data prepared for spatial context. |
| Targets | Review energy targets for operational tracking. |
| ESG | Review emissions, summaries, targets, dashboards, and report generation surfaces. |
| AI energy analysis | Analyze equipment energy profiles, anomalies, recommendations, carbon footprint, and benchmark references from submitted readings. |
| Building simulation | Extract KPIs, build IDF inputs, and run EnergyPlus-oriented simulations through AI Engine endpoints when project data is prepared. |
Use energy analysis as an engineering review input. Confirm meter mapping, tariff assumptions, time windows, weather normalization, and operating constraints before relying on results in an external report.
Use FMS analytics
FMS Lite connects core equipment, alerts, reliability, and maintenance analytics:
| Surface | What users can review |
|---|---|
| Dashboard | Equipment total and alert state summary. |
| Life-cycle cost | Equipment LCC entries, summaries, and optional benchmark-backed analysis. |
| RCFA | Alert-linked root-cause records, verification, and review history. |
| Diagnosis link | Advisor handoff for an alert. |
| Reliability | Alert-derived reliability statistics and AI Engine Weibull reliability call. |
| Subsystem dashboards | Chiller, IAQ, elevator, lighting, fire, parking, preventive maintenance, UPS, water, cleaning, inventory, contractor, space, billing, visitor, and feedback views. |
| HVAC/VAV slice | HVAC/VAV analytics and control-loop work belong under SmartFM with FMS, energy, ESG, and SHM context. |
Use FMS analytics to prepare maintenance and facility review. Keep the decision record tied to source evidence, work orders, and responsible owners.
Prepare Green Mark evidence
The Green Mark workflow helps facility teams organize evidence for Singapore BCA Green Mark-related review:
- Open Green Mark Clauses and review active clauses, evidence types needed, source-module mapping, evidence count, and status.
- Open a clause detail page and review existing evidence items.
- Upload manual evidence when project owners approve a file for review.
- Run evidence auto-collection to scan available sensors, alerts, work orders, and related system records.
- Review the gap dashboard for categories, missing items, and action focus.
- Generate evidence packs for internal review.
- Review PDF or ZIP exports before external distribution.
Green Mark evidence collection can use operational records, maintenance logs, asset registers, energy reports, and source-module references. The asset ontology view should be used when Brick Schema or other semantic asset relationships are needed to explain how building systems, spaces, meters, and equipment connect.
Use AI-assisted review
AI-assisted facility operations are exposed through backend proxy and AI Engine routes:
| AI workflow | Current support |
|---|---|
| Advisor chat | Facility management assistant with tool-aware chat and optional facility context injection. |
| Equipment knowledge | Equipment knowledge, failure modes, maintenance procedures, cross-system knowledge, and supported languages. |
| Knowledge graph | Equipment subgraph, root-cause analysis, and impact analysis. |
| Energy analysis | Equipment energy profile, anomaly detection, recommendations, carbon footprint, and benchmarks. |
| HVAC/VAV diagnostics | Responsiveness, oscillation, deviation, static pressure, diagnostic summary, and health endpoint. |
| Chiller analysis | Efficiency, staging, setpoint, simulation, and benchmark endpoints. |
| Work-order text | Structure free-text work-order feedback, explain alerts, draft SOPs, and extract nameplate fields. |
| Maintenance planning | Calendar prediction and priority scoring based on operating and maintenance inputs. |
AI output should enter the same review path as operator findings: source check, owner review, work-order linkage, and closed-loop outcome capture.
API surface
Facility Operations uses several API groups:
| Group | Example endpoints |
|---|---|
| Work orders | /api/v1/workorders, /api/v1/workorders/{id}, /api/v1/workorders/{id}/status, /api/v1/workorders/{id}/start, /api/v1/workorders/{id}/complete, /api/v1/workorders/{id}/comments, /api/v1/workorders/{id}/attachments, /api/v1/workorders/{workOrderId}/closed-loop |
| Worker | /api/v1/worker/workorders, /api/v1/worker/workorders/{id}, /api/v1/worker/inspections/summary, /api/v1/worker/inspections/tasks, /api/v1/worker/inspections/checkin, /api/v1/worker/issues/report, /api/v1/worker/scan |
| Operations read model | /api/v1/ops/read-model, /api/v1/ops/read-model/{itemType}/{itemId}, /api/v1/ops/audit-timeline/{itemType}/{itemId}, /api/v1/ops/inspector-bindings/{targetObjectId} |
| Operations commands | /api/v1/ops/alarm-candidates, /api/v1/ops/alarm-events, /api/v1/ops/work-orders/{workOrderId}/commands |
| Asset center | /api/v1/platform/asset-center/inventory |
| Model assets | /api/v1/model-assets, /api/v1/model-assets/{modelAssetId}/versions, /api/v1/model-assets/{modelAssetId}/components, /api/v1/twin-model-bindings |
| Energy | /api/v1/energy/dashboard, /api/v1/energy/meters, /api/v1/energy/consumption, /api/v1/energy/carbon, /api/v1/energy/spatial-data, /api/v1/energy/targets |
| FMS Lite | /api/v1/fms/dashboard, /api/v1/fms/equipment/{equipmentId}/lcc, /api/v1/fms/assets/{id}/lcc-analysis, /api/v1/fms/rcfa, /api/v1/fms/alerts/{alertId}/diagnosis, /api/v1/fms/equipment/{equipmentId}/weibull |
| Green Mark | /api/v1/gm/clauses, /api/v1/gm/evidence, /api/v1/gm/evidence/upload, /api/v1/gm/evidence/auto-collect, /api/v1/gm/packs, /api/v1/gm/packs/generate, /api/v1/gm/gap-analysis, /api/v1/gm/summary |
| ESG and carbon | /api/v1/esg/emissions, /api/v1/esg/targets, /api/v1/esg/dashboard, /api/v1/esg/report, /api/v1/carbon/dashboard, /api/v1/carbon/report, /api/v1/carbon/report/pdf |
| AI proxy | /api/v1/ai/energy/analyze, /api/v1/ai/energy/profile, /api/v1/ai/energy/benchmarks, /api/v1/ai/knowledge/equipment/{type}, /api/v1/ai/graph/root-cause, /api/v1/ai/graph/impact |
| AI Engine | /ai/energy/analyze, /ai/energy/profile, /ai/energy/benchmarks, /ai/sim/extract-kpis, /ai/sim/build-idf, /ai/sim/run, /ai/advisor/chat, /ai/llm-pdm/structure-workorder, /ai/hvacops/vav/diagnostics/summary, /ai/hvacops/chiller/efficiency |
Validation checklist
Before using Facility Operations output in an operating meeting, evidence review, or external report, confirm:
- tenant context and permissions match the target site;
- equipment, meter, space, station, work-order, and source-system IDs are mapped consistently;
- model assets and twin-model bindings point to the intended asset version;
- sensor values, work records, inspection records, and evidence files have acceptable timestamps and source freshness;
- work-order state changes and field uploads are visible in the audit trail;
- AI-assisted findings are linked to source evidence and reviewed by an accountable owner;
- Green Mark evidence packs have been reviewed by the project or compliance owner before external use.