A Foundational Guide for Facility Management (FM-009) · By David Gray | DavidGrayProjects.com
Introduction: The Building Is Not Finished at Substantial Completion
Construction teams measure success by schedule, budget, and substantial completion. Operations teams measure success by whether the facility can be run safely, efficiently, and reliably for decades. Those outcomes are related, but they are not the same.
A project can hit its turnover date and still hand over incomplete asset data, inaccessible equipment, unstable control sequences, and untrained staff. Each gap moves cost and risk from the capital budget to the operating budget, where it shows up later as the deferred-maintenance and reliability problems I covered in The Hidden Costs of Deferred Maintenance. Facility management should not inherit those decisions after the fact. It should influence them while they are still cheap to change. The same logic drives early owner's-rep engagement, covered in The $1.2M Mistake.
Having worked on both sides of that handover, as an owner's representative pushing a project to completion and alongside the operations teams who had to live with the result, I have come to see the gap less as a technical problem than as a governance one. Most of the issues operations inherits were visible to someone during design or construction. They simply had no owner with the authority and incentive to fix them before turnover.
1. Define Operational Readiness at Project Initiation
Operational readiness is not a binder delivered at the end. It is a defined scope with deliverables, owners, milestones, and acceptance criteria. At project authorization, identify:
The future operator and maintenance model (in-house, outsourced, or hybrid)
Staffing levels and skills required at opening
The asset hierarchy and naming convention for the CMMS
The critical spares philosophy
The warranty strategy and who will manage claims
Applicable compliance, inspection, and permitting obligations
Assign one accountable operational readiness lead with a seat in project decision-making.
Commissioning standards already provide the anchor document. ASHRAE's commissioning process starts with the Owner's Project Requirements (OPR), documented at inception, against which the design's Basis of Design is checked [1][2]. Make sure operations and maintenance requirements are written into the OPR. A requirement that is not documented early is exposed to value engineering, late redesign, or omission; early requirements definition is consistently one of the cheapest risk controls an owner has.
What belongs in the OPR from an FM perspective
| OPR topic | Examples of FM requirements |
|---|---|
| Maintainability | Service clearances, access routes, lifting points, removal paths for major equipment |
| Reliability and redundancy | Which systems require standby capacity; acceptable outage durations |
| Controls and data | Open protocols, point naming, trend logging, integration with existing building automation |
| Metering | Submetering by system, tenant, or cost center to support billing and benchmarking |
| Standardization | Preferred equipment families to limit spare-parts inventory and training needs |
| Documentation | Format and structure of O&M manuals, as-builts, and asset data |
| Training | Audiences, systems, timing, and acceptance |
An operational readiness timeline
| Project phase | Operational readiness activities |
|---|---|
| Initiation / planning | Name readiness lead; define operating model; write O&M requirements into the OPR |
| Design | FM design reviews at each stage; lifecycle cost comparisons; data and naming standards issued |
| Procurement | Commissioning, training, and data deliverables in contracts; spare-parts lists requested |
| Construction | Operating team recruited or assigned; asset data sampled and test-loaded; Cx witnessing |
| Start-up and testing | Functional performance tests; training delivered; first operating-year budget finalized |
| Occupancy and warranty | Post-occupancy reviews; seasonal testing; warranty management; closeout |
The most common failure is starting the right-hand column too late. If the operating team is first assembled after substantial completion, every downstream activity becomes a catch-up exercise, and the people who will run the building never had a chance to shape it.
2. Bring FM Into Design Reviews
FM should review at concept, schematic design, design development, and construction documents, using a focused checklist:
Can technicians safely reach valves, filters, panels, and major equipment?
Can heavy components be removed and replaced without demolition?
Are shutdown boundaries and isolation points practical?
Can the systems be maintained with available skills and local service support?
Are metering, controls, and data interfaces suited to the operating model?
Keep FM reviews from becoming an uncontrolled wish list. Each comment should state the operating consequence, the applicable standard or requirement, the lifecycle cost, and the decision needed. The objective is disciplined design optimization, not scope growth, and every accepted comment should flow through the project's change control and scope baseline.
A simple test I use with design teams is to ask them to walk us through how a technician would replace the largest piece of equipment in each mechanical space. More than once, that question has surfaced a problem nobody had noticed on the drawings: a unit that could only come out through a wall that was about to be finished, or a filter bank that could only be reached from a ladder over a pipe rack. Each was cheap to fix on paper and would have been expensive and disruptive to fix later.
Design review comment template
| Field | Purpose |
|---|---|
| Location / system | Ties the comment to a specific drawing or asset |
| Issue | What the reviewer observed |
| Operating consequence | What happens in operation if unchanged (safety, downtime, cost) |
| Requirement or standard | OPR clause, code, or owner standard that applies |
| Recommendation | Specific change requested |
| Cost and schedule impact | Estimated, even roughly |
| Decision owner | Who accepts or rejects |
Comments written this way are easier to accept, easier to reject with a documented reason, and far easier to track.
3. Evaluate Total Cost of Ownership
Lowest installed cost is not always lowest lifecycle cost. Compare options on initial capital, energy, maintenance labor, consumables, reliability, replacement cycles, downtime exposure, and residual value, with transparent assumptions and sensitivity analysis. A more expensive equipment package can be justified where better reliability and access materially reduce operating risk. In other cases a simple, maintainable system will outperform a complex "smart" alternative.
Finance, engineering, and FM should agree on the evaluation horizon, discount rate, utility price assumptions, and who validates vendor performance claims. Record the selected option and why it won.
Worked illustration: two air-handling options
Illustrative example only; hypothetical figures.
A project team is choosing between two air-handling packages for a new building.
| Option A (lower first cost) | Option B (higher first cost) | |
|---|---|---|
| Installed cost | $1.80M | $2.10M |
| Annual energy | $210,000 | $175,000 |
| Annual maintenance | $60,000 | $45,000 |
| Expected major overhaul | Year 12, $400,000 | Year 15, $350,000 |
Assume a 20-year horizon, a 6% real discount rate, and costs in constant dollars. Option B saves $50,000 a year in operating cost ($35,000 energy plus $15,000 maintenance). At an annuity factor of about 11.47, that stream has a present value of roughly $573,000, which more than recovers Option B's $300,000 premium. The overhauls widen the gap: Option A's year-12 overhaul has a present value of about $199,000 versus about $146,000 for Option B's year-15 overhaul, a further $53,000 in Option B's favor. Before residual value, Option B comes out roughly $326,000 ahead in present-value terms.
Now test the assumption that matters most. Option B only breaks even if it delivers at least about $21,600 a year of the promised $50,000 in operating savings, roughly 43% of the vendor claim. That is the number to put in front of the decision-makers. The answer is sensitive to the energy price assumption and to whether the claimed efficiency is verified at commissioning, which is why the business case should name who will confirm performance after occupancy. The point is not that the more expensive option always wins; it is that the comparison should be made explicitly, with operating costs on the table, before procurement.
4. Commissioning Must Start Before Construction Ends
Commissioning (Cx) should be planned during design and carried through construction, startup, functional testing, and occupancy. Depending on the jurisdiction, the energy code may require some commissioning activities; treat that as the floor, not the scope. ANSI/ASHRAE/IES Standard 202-2024 sets out the process requirements for new buildings and new systems, and ASHRAE Guideline 0-2019 describes the process in detail [1][2]. Under ASHRAE's process the lead role is the Commissioning Provider (CxP); you will still see "commissioning authority" (CxA) or "agent" in older documents and some rating-system language [5].
Define the CxP's independence, system boundaries, functional test procedures, acceptance criteria, issues log, and re-testing obligations. A contractor's startup checklist is not a substitute for integrated functional performance testing.
For critical facilities, the Cx program may need to verify loss-of-utility scenarios, emergency and standby power, controls interactions, alarms, redundancy, and recovery procedures. Tests should fit the actual facility and its hazards, under approved methods of procedure and safety controls.
Commissioning milestones FM should track
OPR documented and approved
Basis of Design reviewed against the OPR
Commissioning requirements included in construction specifications
Submittals reviewed for commissioning and maintainability
Pre-functional checklists completed
Functional performance tests executed and witnessed
Issues log closed or formally deferred with owners
Systems manual and training delivered
Seasonal or deferred testing completed after occupancy
Post-occupancy review before warranty expiry
The schedule pressure at the end of a project almost always lands on steps 6 through 8. Protect them in the schedule from the start, and agree in advance which tests can be deferred to a later season and which cannot.
5. Make Digital Handover Usable
A data dump is not an asset-management system. Require a structured asset register with agreed naming conventions, locations, manufacturer/model/serial data, warranty dates, preventive maintenance tasks, criticality, spare-parts lists, and links to approved O&M manuals and as-builts.
Open standards help. COBie (Construction to Operations Building information exchange), part of the U.S. National BIM Standard (NBIMS-US), defines a structured format for handing over maintainable-asset data, and NIBS advises owners to specify the tables, fields, timing, and responsible parties at the start of the project [3]. Internationally, ISO 19650 sets out the information-management process that such deliverables sit within, and NBIMS-US is aligned with it [4]. Neither is mandatory unless your contracts make it so, which is exactly why the requirement has to be written into them. Whatever you specify, test it: load sample records into the receiving CMMS or EAM before turnover. If operations cannot load, search, and plan maintenance from the data, the handover has not done its job.
On one project our team inherited at the end of construction, the handover package was technically complete: every manual, every submittal, every warranty letter was there. It was also several thousand scanned pages with no consistent asset tags, and the equipment schedules did not match what had actually been installed after substitutions. It took the operations team months of field verification to build a usable asset register. On every project since, I have pushed to have a sample of the asset data delivered and test-loaded well before substantial completion. It is a small ask early and an enormous one late.
Handover data acceptance criteria
Every maintainable asset has a unique tag that matches the physical label and the drawings
Manufacturer, model, and serial numbers reflect installed equipment, not the original specification
Warranty start dates and durations are recorded per asset
Preventive maintenance tasks are assigned with frequencies
Spare parts are listed for critical equipment
Documents are linked to assets, not just filed by specification section
A sample load into the CMMS has been completed and accepted by operations
Writing readiness into the contracts
None of the activities in this article will happen reliably unless they are in the contracts. Procurement is the point at which operational readiness either becomes enforceable or becomes optional. At a minimum, design and construction contracts should specify:
Commissioning scope and responsibilities, including contractor participation in functional testing and re-testing at the contractor's cost when tests fail
Asset data requirements, with the template, format, delivery milestones, and acceptance test, not just "provide O&M information"
Training requirements by system and audience, with acceptance by the owner
Spare parts and special tools to be handed over at turnover
Warranty terms, including response times and who coordinates multi-trade issues
Retention or holdback linked to readiness deliverables, so data, training, and documentation carry real commercial weight
The last point is often decisive. When retention is released on substantial completion alone, the owner loses most of its leverage over the deliverables operations needs most. Tying a portion of retention to accepted handover data and completed training changes contractor priorities in the final months of a project, usually at modest cost to the owner.
6. Training Is a Contract Deliverable
Specify training by audience and system, with learning objectives, instructor qualifications, attendance records, recorded sessions where permitted, and hands-on demonstrations. Cover normal operation, emergency response, isolation, troubleshooting, warranty escalation, and common failure modes. Schedule it when systems are complete enough to demonstrate and the future operators can attend.
Avoid a single rushed training week just before occupancy. Stage the training and add refresher sessions after the facility has been operating for a few months, when operators know what questions to ask.
7. Connect Project Controls to Operating Controls
A project's cost and schedule controls should connect to the owner's operating budget and asset-management plan, the life-cycle discipline that ISO 55001:2024, the current edition of the international asset-management system standard, is built around [6]. Track how design changes affect maintenance contracts, utility consumption, staffing, software licenses, consumables, and capital renewal. (For the project-side discipline, see What Are Project Controls?.) Assign clear responsibility for open punch-list items, latent defects, warranty claims, permits, and post-occupancy optimization.
Structured post-occupancy reviews, for example at 30, 60, and 90 days and again before the warranty period ends, surface comfort complaints, control instability, unexpected energy use, and documentation gaps. Assign corrective actions and keep a funded closeout mechanism; do not assume the project team will stay available indefinitely.
The first operating-year budget
A useful discipline is to require a first operating-year budget as a project deliverable, prepared jointly by the project team and FM before construction is complete. It should cover:
Staffing and contracted services
Utilities, based on design energy models adjusted for expected occupancy
Preventive maintenance and consumables
Software licenses and service subscriptions for new systems
Warranty management and expected out-of-warranty costs
A contingency for start-up issues
If no one can produce this budget, the operating model has not been defined, and the building is not ready to be handed over.
8. Clarify Accountability
The owner should name who approves design deviations, accepts Cx results, signs off operational readiness, and takes custody of each system. Substantial completion, beneficial occupancy, operational acceptance, and final completion can fall on different dates and carry different contractual meanings. Treat them as distinct milestones with explicit criteria and evidence.
A RACI is useful only if it resolves decisions. Give FM a formal approval role, or documented consultation, on maintainability, operational data, training, and readiness. Give the project manager authority over scope and cost. Escalate unresolved trade-offs before procurement or installation makes them irreversible.
9. Where Handover Gaps Usually Start
Most operational problems that appear after turnover can be traced to a small number of recurring causes. Recognizing them early is half the battle.
| Gap | Where it starts | Early warning sign | Prevention |
|---|---|---|---|
| Inaccessible equipment | Design development, when space is tight | Mechanical rooms shrinking in successive drawing sets | FM maintainability review with removal-path check |
| Unusable asset data | Specifications that say "provide O&M manuals" without structure | No data template issued with the contract | Specify COBie or an owner template; test-load early |
| Unstable controls | Late sequence-of-operations changes; rushed point-to-point checks | Controls contractor still programming during functional testing | Freeze sequences early; protect Cx time in the schedule |
| Untrained operators | Training scheduled in the last week | Operators not yet hired or assigned near completion | Staff the operating team before substantial completion |
| Orphaned deficiencies | Punch list closed for contractual completion, not operational acceptance | Deficiencies marked "accepted" without an owner | Separate contractual completion from operational acceptance |
| Surprise operating costs | Value engineering that trades first cost for lifecycle cost | VE log with no operating-cost column | Require lifecycle impact on every VE proposal |
Value engineering deserves its own discipline
Value engineering is legitimate and often necessary. The problem is when it is used as a synonym for cost cutting under schedule pressure, with no one assessing the operating consequence. Every VE proposal should carry the same fields as an FM design comment: what changes in operation, what it costs over the life of the asset, and who accepts the trade-off.
I have been in value engineering sessions where a long list of substitutions was approved in an afternoon to close a budget gap, and the only person in the room who would have to live with them was not there. Since then I have insisted that someone from operations sits in on VE decisions, even for an hour. The point is not to block savings. It is to make sure the organization is choosing them knowingly.
10. Managing the Warranty Period
The warranty period is an important window for documenting defects and exercising contract remedies, but it is not necessarily the owner's last source of contractual or legal recourse. Rights after warranty expiry depend on the contract and applicable law. This practical window is often underused.
Log every issue against the asset and the warranty. Operators under pressure will often fix a problem themselves rather than raise a claim, which quietly transfers cost from the contractor to the owner.
Hold a pre-expiry review. A walkdown and data review a couple of months before warranty expiry catches problems while they can still be claimed.
Complete seasonal testing. Systems that could not be fully tested at turnover, such as cooling in a winter handover, need to be tested in the first relevant season.
Track latent defects separately. Some issues will not appear until well after occupancy. Know what the contract says about them.
A separately identified, owner-controlled closeout budget can support follow-up testing, training, and data reconciliation. Any retainage or withholding from contractors must follow the actual contract, payment requirements, and applicable law.
11. What the Executive Team Should Ask
Before approving a major capital project:
Who will operate this asset, and are they involved now?
What does the lifecycle cost model assume?
Which systems are critical to business continuity?
How will performance be verified, and by whom?
What information must be loaded into operating systems, in what format?
Who owns unresolved deficiencies after turnover?
What does the first operating-year budget look like?
Who is accountable for the first 90 days of stable operation?
These questions are cheap to answer early and expensive to answer late.
Conclusion: Deliver an Operating Asset, Not Just a Construction Project
The strongest capital programs treat operations as an intended outcome from day one, which is the asset-value argument at the heart of FM-001. They align design, procurement, construction, commissioning, digital handover, training, and finance around the asset's useful life. FM involvement is not an administrative add-on; it is one of the most practical ways an owner protects the value of a capital investment.
The next article in this series looks at the skills FM leaders need to play that role.
Related from Albers Management:
The $1.2 Million Lesson: Why Owner’s Reps Belong at Day One – Albers Management
Why Early Requirements Definition Saves Millions – Albers Management
Sources
ANSI/ASHRAE/IES Standard 202-2024, The Commissioning Process Requirements for New Buildings and New Systems. ashrae.org
ASHRAE Guideline 0-2019, The Commissioning Process. ashrae.org
National Institute of Building Sciences, NBIMS-US, COBie. nibs.org
National Institute of Building Sciences, NBIMS-US V4 Introduction (alignment with ISO 19650). nibs.org
ASHRAE, "Effectively Applying the Commissioning Process" (on the Commissioning Provider role and terminology). ashrae.org
ISO 55001:2024, Asset management — Asset management system — Requirements (Edition 2, published July 2024). iso.org
Worked examples labeled "illustrative" use hypothetical figures to explain methods.
About the Author
David Gray is a capital delivery strategist, owner's representative, and founder of DavidGrayProjects.com. With over two decades of experience helping organizations bring complex projects to life, from data centers and healthcare facilities to higher-ed campuses, David blends practical delivery with forward-thinking strategy.
He writes about project controls, capital planning, and real estate development to help leaders deliver smarter, faster, and more sustainably.
📩 Connect on LinkedIn | 🌐 Explore More at DavidGrayProjects.com | 🌐 Explore More at Albers Management