Get Started with Facility Operations

Use this guide when a customer team is preparing the first Facility Operations workspace in FactVerse. The goal is to give facility managers, operations teams, maintenance owners, and field users one reviewed view of assets, alarms, inspections, work orders, documents, energy signals, and follow-up actions.

Facility Operations works best as a governed operating loop: define the site scope, connect asset and source identities, review current conditions, route work through accountable owners, and feed completed work back into the digital twin and data layer.

Setup Flow

Prerequisites

Requirement	Why it matters
Site owner	Confirms which buildings, floors, systems, and teams belong in the first rollout.
Asset owner	Reviews asset names, equipment classes, source IDs, and operational responsibility.
Data owner	Confirms BMS, meters, CMMS, inspection, document, and energy data are current enough for use.
Maintenance owner	Accepts routed work, reviews work-order drafts, and verifies completion evidence.
Field execution path	Defines whether users execute work through Inspector, a CMMS, or a connected work-order system.

Start with a focused operating boundary. A single facility, system, floor, utility area, or service team gives the customer a clearer validation path before portfolio rollout.

Step 1: Define the First Operating Boundary

Document the boundary before configuring workflows.

Decision	Example
Site scope	Building, campus, plant, data center, warehouse, or utility area.
System scope	HVAC, chilled water, electrical, fire safety, water, elevator, IAQ, lighting, or production utilities.
User scope	Facility manager, operator, inspector, maintenance lead, contractor coordinator, or ESG reviewer.
Work scope	Daily triage, field inspection, alert review, work-order routing, energy review, or evidence preparation.
Review cadence	Shift handover, daily operating review, weekly maintenance planning, or monthly performance review.

Step 2: Prepare Asset and Location Context

Facility Operations depends on stable asset and location identity.

Context	Required preparation
Site hierarchy	Site, building, floor, area, room, system, and equipment relationships.
Equipment records	Asset ID, name, class, owner, location, manufacturer, model, status, and source-system aliases.
Spatial context	3D, BIM, CAD, or model asset binding when operators need visual or location-based context.
Operating relationship	Connected systems, upstream and downstream equipment, meters, spaces, and affected zones.
Responsibility	Owner team, maintenance team, contractor role, and escalation path.

Use Asset and Twin Context for a deeper setup path.

Step 3: Prepare Source Data

The first workspace should include only the data needed for the selected operating boundary.

Data source	Typical use
BMS or facility system	Current values, alarms, statuses, setpoints, and equipment behavior.
Meters	Energy, water, gas, demand, consumption, and carbon-related review input.
CMMS or work-order system	Open work, history, owner, status, priority, action notes, and closure evidence.
Inspector	Alerts, inspections, worker tasks, field notes, attachments, and audit records.
ECM or document source	Manuals, SOPs, drawings, inspection evidence, service reports, and compliance files.
DFS	Connector state, mappings, quality checks, fused datasets, lineage, and reusable operating data.

For source setup, use Operational Data Readiness and Connect BMS Data to a Facility Twin.

Step 4: Enable Operating Surfaces

Confirm which product views are active for the tenant.

Surface	Use
Inspector alerts	Review operating events, alarm context, and related records.
Work orders	Create, assign, update, complete, comment, attach evidence, and review closure.
Inspections	Run scheduled checks, collect field findings, and escalate issues.
Worker views	Support mobile execution, QR scan, check-in, photo upload, voice notes, and progress update.
Asset center	Review asset inventory and link operational records to model assets.
Energy	Review meter data, consumption, carbon-related output, and targets.
Green Mark workspace	Prepare clauses, evidence items, evidence packs, gap views, and owner review.
AI Agent	Summarize evidence, explain alerts, draft checks, and prepare action text for review.

Step 5: Validate One End-to-End Scenario

Before adding more systems, validate one operating scenario.

1. Pick one asset, system, or room.
2. Confirm the asset can be found in the facility hierarchy.
3. Confirm source values or records resolve to the same asset.
4. Open a related alert, inspection task, or work-order record.
5. Attach or retrieve at least one supporting document.
6. Route a finding into a reviewed work order or field task.
7. Close the work with outcome notes and evidence.
8. Confirm the audit trail and operating summary reflect the result.

Expected Output

At the end of setup, the customer team should have:

• a defined operating boundary;
• named owners for asset, data, maintenance, and evidence review;
• a small asset and source-data set that can be trusted;
• active Inspector, work-order, inspection, or energy surfaces for the first workflow;
• a visible path from alert or inspection finding to reviewed work;
• a review cadence for daily operation and continuous data improvement.

Validation Checklist

• Site, building, floor, area, system, and asset identity are consistent.
• Source records show timestamps, source-system references, and quality notes where available.
• Work-order or field execution ownership is clear.
• Documents and evidence are linked to the correct asset, area, work order, or clause.
• AI-assisted output stays tied to source evidence and owner review.
• Completed work feeds back into operations, maintenance, and data-quality improvement.

Failure Handling

Symptom	Response
Asset names differ across systems	Pause workflow expansion and resolve aliases through asset owner or DFS MDM review.
Source data is stale	Record the freshness gap, confirm connector status, and keep the workflow in review mode.
Work ownership is unclear	Keep generated work as draft text until the responsible owner is confirmed.
Field users cannot find the asset	Review hierarchy, location labels, model binding, and Inspector context before rollout.

Related Docs

• Facility Operations
• Asset and Twin Context
• Operational Data Readiness
• Daily Operations Triage
• Alert to Inspection and Work Order Loop
• Facility Operations AI Tools