Begin with the workflow vocabulary
Facilities service intake, Asset maintenance, Energy investigation each have distinct inputs and review points. A shared vocabulary should explain what the core entities—Building, Asset, Service request, Meter reading—mean and how they relate. A model cannot repair conflicting business definitions just by receiving a longer prompt.
Preserve context that changes the answer
Resolve building and asset hierarchy, standardize meter units and intervals, and retain occupancy and schedule assumptions. Record the source authority and the conditions under which information applies. An answer can be fluent and still be wrong because it used the wrong entity relationship, document version, unit, or time period.
Make evidence a product feature
A facilities team translates service requests into asset context and investigates energy anomalies using building records and operational schedules. The user experience should expose the evidence behind a proposed output and make uncertainty visible. Provide source links, relevant dates, and a clear distinction between observed records and model-produced interpretation.
Give agents a bounded responsibility
Classify requests and draft service work orders using asset context. Define this responsibility with explicit completion criteria and a small tool set. Keep retrieval, draft preparation, and record-changing actions separate in the permission model. An agent’s ability to suggest a next step does not imply authority to execute it.
Test the difficult cases first
Include conflicting identifiers, missing evidence, obsolete documents, and restricted records in evaluation. Proposed measures include asset resolution accuracy, request completeness, anomaly review usefulness, and approved work-order quality. Also test whether reviewers can understand and correct an output without reconstructing the whole task themselves.
Keep the ownership model visible
Building controls, contractor commitments, and safety actions require operator approval. Data stewards resolve source meaning and quality, platform teams operate access and reliability, and workflow owners accept the business behavior. Treat these responsibilities as part of the architecture rather than a handover note.
Architecture takeaway
Resolve building and asset hierarchy, standardize meter units and intervals, and retain occupancy and schedule assumptions. A useful AI experience preserves this context through ingestion, retrieval, generation, and review.