NOTE Equipment with no manufacturer-published maintenance requirement and not identified in the Contract Documents as requiring maintenance (e.g., passive devices) does not generate a separate O&M obligation unless the Engineer of Record directs otherwise. (1.3)

NOTE This standard applies to new construction, renovation, and addition projects alike. (1.4)

NOTE Any project that installs equipment or systems requiring ongoing owner maintenance generates an O&M obligation. The depth of the package scales with the complexity of the installed systems, but the organizational and delivery rules below apply uniformly regardless of project type or size. (1.5)

NOTE The O&M package comprises five document types. (1.6)

NOTE The five types are distinct deliverables with different audiences and depth: (1) a master directory of O&M documentation that indexes the whole package; (2) emergency operation manuals covering life-safety and system-critical sequences; (3) operation manuals covering start-up, shutdown, seasonal changeover, and interlock descriptions; (4) product maintenance manuals carrying manufacturer-specific schedules, lubrication, filter and media replacement, and calibration; and (5) systems-and-equipment maintenance manuals coordinated across trades. Each type is specified in its own section below. (1.7)

NOTE O&M data is a closeout deliverable that gates owner occupancy; it is not a convenience document assembled after the fact. (1.8)

NOTE The package is the owner's primary reference for operating and maintaining the building after the contractor leaves. An incomplete or late package strands the facilities staff at the moment they assume responsibility and starts the warranty clock without the records needed to make a claim. Timing and completeness are therefore treated as schedule-critical, not clerical. (1.9)

NOTE This standard governs what the package contains and how it is delivered; it does not restate processes owned by adjacent standards. (1.10)

NOTE Commissioning execution and functional performance testing are governed by Commissioning — O&M data content triggers the commissioning sequence but this standard does not specify test procedures. Final testing, adjusting, and balancing reports are produced under Testing Adjusting And Balancing and appended to the O&M manuals by reference only. Final inspections, certificate of occupancy, and punchlist resolution belong to Closeout Procedures. The submittal review and transmittal mechanics are governed by Submittal And Quality Procedures; O&M data is a submittal type but the review workflow is not repeated here. Warranty terms and bond claim procedures live in Warranties And Bonds; warranty certificates are collected into the O&M package but their terms are not specified here. As-built record drawings and progress photographs belong to Construction Progress Documentation. Equipment labeling and nameplate conventions are specified in Electrical Identification and the equivalent mechanical identification sections — this standard requires only that installed identification match the O&M directory. (1.11)

NOTE A bare instruction to "submit O&M manuals" generates RFIs and incomplete submittals. (1.12.1)

NOTE When the specification says only "submit operation and maintenance manuals," it delegates every consequential decision — how many manuals, organized how, in what depth, in how many copies, by when — to the contractor's discretion, and the result is a package that does not match the owner's needs and arrives too late to fix. Each of those decisions is captured as an explicit requirement or datasheet field in the sections below so the obligation is unambiguous at bid time. (1.12.2)

NOTE Conflating O&M data with record documents produces gaps and duplication at handover. (2.1.1)

NOTE Record documents — the marked-up as-built drawings, the shop drawing log, the approved submittal record — are produced and controlled under Construction Progress Documentation. O&M data is the operating and maintenance reference. The two overlap in the operator's mind but are different deliverables with different content and different controlling standards. The specification shall state plainly which artifacts go into the O&M binder and which belong to the record document set so neither is assumed by both parties and dropped by both. (2.1.2)

NOTE Quality control inspection records, material certifications, and approval test reports are procedural quality documents governed by Quality Requirements and are included in the O&M package only where this standard or the owner expressly calls for them. (2.2)

NOTE ASHRAE Guideline 4 is a guideline, not a code; O&M manuals are prepared "in accordance with" it rather than "in compliance with" it. (3.3)

NOTE Several of the references below are consensus guidelines or industry references that define content and depth without carrying the force of code. They are used as the measure of completeness for the relevant system manuals. The codes in the table (NFPA, NEC) carry enforcement weight and establish content that must appear in the package as a condition of the installed equipment's lawful operation. (3.4)

NOTE O&M data is submitted in two passes: a preliminary submittal for review and a final submittal incorporating review comments. (4.1)

NOTE The preliminary submittal lets the Engineer of Record, the owner's facilities team, and the commissioning agent review organization, completeness, and project-specific accuracy while there is still time to correct it. The final submittal is the corrected, owner-of-record copy. Skipping the preliminary pass — submitting only at Substantial Completion — leaves no time to fix deficiencies before the owner occupies and the warranty period begins. (4.2)

NOTE On BIM-enabled institutional and federal projects, equipment O&M data is increasingly delivered as a structured COBie export so the data can be loaded directly into the owner's CMMS or linked to model objects. COBie supplements the PDF package; it does not replace the human-readable manuals. Where the owner maintains a model-based document management program, equipment O&M PDFs may additionally be hyperlinked to model objects via the COBie export. (4.7)

NOTE Subcontractor-compiled manuals submitted without general-contractor review produce mismatched formats, missing sections, and duplicated or irrelevant data. (5.1.1)

NOTE When each trade assembles and transmits its own binder independently, the owner receives an inconsistent package: different tab schemes, different page sizes, generic catalog data alongside project-specific data, and gaps where one trade assumed another would cover a shared system. A single point of coordination — the general contractor reviewing and normalizing every trade's submission against the directory before it goes out — is what makes the package usable. (5.1.2)

NOTE Generic catalog cuts that do not match the installed equipment are a recurring defect. (5.3.1)

NOTE A binder full of manufacturer catalog pages that show every model in a product family — rather than the specific model, options, and accessories actually installed — forces the facilities staff to guess which data applies. The package shall carry the approved submittal cut sheets, the as-installed model numbers, recorded serial numbers, and project test data so that the document matches the building. (5.3.2)

NOTE O&M data organized in a scheme the owner's CMMS cannot consume is functionally useless to the operator. (5.4.1)

NOTE Owners track assets by equipment tag, by system, or by building area depending on how their CMMS is structured. A package organized solely by specification section is opaque to an owner who maintains by equipment tag. The organization scheme is therefore a coordination item to be settled with the owner's facilities team before compilation, not a contractor default. (5.4.2)

NOTE Setting the submission deadline at or after Substantial Completion defeats the purpose of the review. (6.1.1)

NOTE If the manuals arrive only when the building is substantially complete, there is no schedule float to find a deficiency, return it for correction, and receive a corrected resubmittal before the owner occupies. The preliminary deadline is set ahead of Substantial Completion precisely to create that review-and-correct window. Simpler projects can tolerate a shorter lead time; complex or phased projects need more. (6.1.2)

NOTE Copy counts differ sharply between commercial and institutional owners. (6.3.1)

NOTE Two hard-copy sets plus an electronic copy is the common baseline for mid-size commercial projects; institutional and government owners (universities, hospitals, federal agencies) commonly require three or four. Because each additional full set is a real reproduction cost and the right number depends on how the owner distributes the manuals across facilities, the count is confirmed with the owner before compilation rather than assumed. (6.3.2)

NOTE Round-ring binders larger than 1 inch hold pages off-center so they will not lie flat, and the pages tear at the punch line under normal handling. D-ring binders hold the pages flush against the back cover and are the standard for any capacity above 1 inch. The 3 inch D-ring is the common baseline; smaller capacities are acceptable where the volume is genuinely small. (6.4.2)

NOTE Tabbed organization with a per-binder table of contents is what makes a binder navigable. (6.5.1)

NOTE A binder of unlabeled, undivided pages is no better than a loose stack. Labeled tab dividers keyed to a front-of-binder table of contents let the operator turn directly to the system or equipment they need. The tab scheme shall follow the package organization scheme selected in Quality Assurance so the navigation is consistent end to end. (6.5.2)

NOTE Reduced-size as-built drawings inserted into the binder are a reference convenience, not a substitute for the record drawing set. (6.6.1)

NOTE Reduced 11 × 17 prints folded into the O&M binder give the operator a quick on-the-spot reference, but the controlled record drawings are produced and maintained under Construction Progress Documentation. The spec shall state clearly which drawings are inserted into the O&M binder and which belong to the separate record set so the two deliverables are not conflated. (6.6.2)

NOTE Scanned image PDFs satisfy a literal reading of "electronic PDF" but are not searchable and degrade in usefulness over time. (6.7.1)

NOTE A PDF assembled from scanned paper pages contains no selectable text, so the operator cannot search it, and the image quality is fixed at the scan resolution. Requiring PDF/A with text-searchable (born-digital or OCR'd) content and bookmarks ensures the electronic copy is genuinely usable for the life of the building rather than a picture of a binder. (6.7.2)

NOTE The directory is what turns a stack of binders into a usable reference. (7.1.1)

NOTE On a project of any size the package runs to multiple binders or a large PDF set, and an operator with a failing chiller cannot leaf through all of it. The master directory is the lookup that takes the operator from a system or equipment tag directly to the binder, tab, and page where its data lives. It is the first thing compiled against and the last thing checked before delivery, because every other document's findability depends on it. (7.1.2)

NOTE The directory is the single entry point to the whole package. For it to work, the equipment tags it lists must match the physical labels installed on the equipment (specified under Electrical Identification and the equivalent mechanical identification sections) and the asset records in the CMMS. A directory whose tags do not match the field labels sends the operator hunting. (7.1.4)

NOTE The emergency manual is also called an emergency response manual or emergency operating procedure (EOP) binder; the content requirement governs regardless of the name used. (8.1.1)

NOTE Different owners and master specs use different names for this deliverable. The defining characteristic is content, not title: a concise, fast-reference document covering what an operator must do when a life-safety or system-critical event occurs — alarm response, system shutdown, manual override, and notification — without having to read through the full operation manual. (8.1.2)

NOTE The emergency manual's value is speed of access under stress. (8.3.1)

NOTE During a fire alarm, a generator transfer, or an elevator entrapment, the operator does not have time to read a multi-page operation narrative. The emergency procedure shall be a short, sequenced, action-first checklist — what to do, in what order, whom to notify — so it can be followed under pressure. Background and design explanation belong in the operation manual, not the emergency procedure. (8.3.2)

NOTE For systems not on the required-emergency-manual list, an emergency-procedures section within the operation manual is acceptable in place of a standalone emergency manual. (8.5)

NOTE Not every system warrants its own emergency binder. The systems enumerated above carry life-safety or major-property consequences and get a dedicated, fast-reference manual. Lesser systems can carry their emergency procedures as a section of the operation manual, provided the procedures are present and clearly flagged. (8.6)

NOTE Seasonal changeover is a frequent source of operator error when it is not documented. (9.2.1)

NOTE Systems that switch between heating and cooling modes — changeover hydronic loops, economizer sequences, dual-temperature systems — require a defined procedure to transition without tripping interlocks or stranding zones. A new operator who has never run the building through a season has no way to know the sequence unless it is written down. The operation manual shall carry the changeover steps for every system that has them. (9.2.2)

NOTE Undocumented interlocks lead operators to override protective logic they do not understand. (9.3.1)

NOTE Interlocks exist to prevent damage and unsafe conditions — a pump that cannot start until flow is proven, a damper that must open before a fan runs, a generator that will not parallel out of phase. When an interlock trips and the operator does not know why, the temptation is to bypass it to restore service, which is exactly when equipment is damaged or people are hurt. Documenting each interlock's purpose and trigger conditions gives the operator the understanding to troubleshoot rather than defeat it. (9.3.2)

NOTE A systems narrative is what lets a new operator understand the building as a set of interacting systems rather than a pile of equipment. (9.4.1)

NOTE Equipment-only documentation tells the operator what each box does but not how the boxes work together — how the boiler plant, the air handlers, and the controls coordinate to hold a setpoint, or what happens to the air system when a fire alarm trips. The narrative explains the design intent and the interactions so the operator can reason about the building. On simpler projects a brief narrative is acceptable; on integrated institutional projects it is essential. (9.4.2)

NOTE Maintenance intervals stated only as "per manufacturer" without a schedule force the operator to reconstruct the program. (10.2.1)

NOTE The owner needs a usable maintenance calendar, not a directive to go read every manufacturer's manual and build one. The product maintenance manual shall present the actual interval-banded task list — what to do monthly, quarterly, semi-annually, and annually for each item — drawn from the manufacturer data but assembled into a schedule the operator can hand to a technician. (10.2.2)

NOTE The maintenance frequencies for HVAC systems are established by ANSI/ASHRAE/ACCA 180, and the inspection, testing, and maintenance intervals for water-based fire protection systems are established by NFPA 25. The schedules in the O&M manual shall reflect those intervals so the owner's maintenance program is defensible against the standard the authority having jurisdiction will measure it against. Where a manufacturer specifies a more frequent interval to preserve the warranty, the more frequent interval governs. (10.3.2)

NOTE SMACNA O&M guidance defines the manufacturer data that air, duct, and hydronic system manuals must carry. (10.4.1)

NOTE For air-handling equipment, ductwork, and hydronic systems, the SMACNA HVAC operation and maintenance guidance identifies the format and the manufacturer data the manual should include. It is used together with ASHRAE Guideline 4 as the measure of completeness for the HVAC portions of the package. (10.4.2)

NOTE Missing emergency service contacts cripple the owner's ability to respond to equipment failure during the warranty period. (10.5.1)

NOTE When a critical item fails after hours, the operator needs to reach the manufacturer's service representative immediately — not search for a number the next business day. Requiring a 24-hour emergency contact (where the manufacturer offers one) in each equipment manual makes the package the owner's first and fastest point of response. (10.5.2)

NOTE The O&M manual is the owner's primary vehicle for establishing equipment-specific lockout/tagout procedures. (11.2.1)

NOTE OSHA 29 CFR 1910.147 makes hazardous-energy control an ongoing obligation of the building operator. Equipment-specific LOTO procedure sheets in the maintenance manual give the owner a ready-made, energy-source-specific isolation procedure for each machine, rather than leaving the facilities staff to author them from scratch after occupancy. Omitting them is a recurring and consequential defect. (11.2.2)

NOTE Cord-and-plug-connected equipment exempt under 29 CFR 1910.147(a)(2)(iii) and equipment with no maintenance-mode hazardous-energy exposure do not require a LOTO procedure sheet unless the Contract Documents direct otherwise. (11.2.3)

NOTE A restorable software backup is the owner's only path to recovery after a controller failure or a corrupted change. (12.1.1)

NOTE When a controller fails or a well-intentioned change corrupts the control logic, the owner needs to restore the building to its as-commissioned state. That is only possible if a complete, version-stamped backup of the programming and configuration was delivered. A partial backup, or one captured before commissioning corrections were made, restores the wrong building. The backup shall be the as-commissioned version and shall record its version and date so the owner knows what they are restoring to. (12.1.2)

NOTE Control system documentation is routinely missing from general O&M submittals and discovered only at commissioning. (12.2.1)

NOTE Building automation system (BAS) and direct digital control (DDC) data — the written sequences of operation, the I/O point list, the wiring diagrams, and a restorable software backup — is the data the owner needs to operate, troubleshoot, and recover the controls. Because it is produced by the controls subcontractor rather than an equipment manufacturer, it frequently falls through the cracks of a general O&M submittal. Calling it out as a distinct, explicit deliverable is what gets it delivered. Its review shall be coordinated with Commissioning so that controls O&M data is approved before functional performance testing depends on it. (12.2.2)

NOTE The systems requiring operator training are those identified as major systems in the Contract Documents; absent such identification, training is required for each system for which an operation manual is required under this standard. (13.1.1)

NOTE Training delivered by someone unfamiliar with the as-built system teaches the catalog, not the building. (13.1.3)

NOTE Generic product training from a sales representative who never saw the installation leaves the operator unable to run the specific configuration that was built — the actual sequences, the field overrides, the project-specific setpoints. Training shall be delivered by the installing subcontractor or a manufacturer's representative familiar with the as-installed system so the instruction matches the building the operator will run. (13.1.4)

NOTE Without an agenda and a sign-off sheet, there is no record of whether training occurred or what it covered. (13.2.1)

NOTE Training disputes surface during warranty claims: the manufacturer or contractor asserts the operator was trained; the owner asserts the session never happened or omitted the failed system. A written agenda issued before the session and a signed attendance sheet afterward create the evidence that the required training was delivered and what it covered, closing that dispute before it starts. (13.2.2)

NOTE Video recording of training sessions is recommended on healthcare and other high-turnover-operator facilities so that future staff can review the original instruction. (13.4.1)

NOTE On healthcare projects and other facilities with frequent operator turnover, the staff trained at handover are often gone within a few years. A recording of the original training lets the owner re-train new staff on the as-built systems without recalling the contractor. Where the owner anticipates this, video recording should be specified. (13.4.2)

NOTE Federal and large-institution owners impose content beyond the commercial baseline. (14.1.1)

NOTE Federal facility owners and large institutions (universities, hospitals, government agencies) typically maintain their own master O&M specifications that add content the commercial baseline does not require — most commonly system interdependency diagrams that map how the building's systems depend on one another, expanded narratives, and structured-data delivery. Where such an owner specification applies, its content requirements are additive to this standard, and any conflict is resolved in favor of the more stringent requirement per the Referenced Standards section. (14.1.2)

NOTE Recommended spare parts and special tools documentation lets the owner stock and equip before a failure, not after. (15.1.1)

NOTE The manufacturer's recommended spare parts list and the inventory of any non-standard tools needed to service the equipment are part of preparing the owner to maintain the building. Without ordering information current as of handover, the owner discovers the part number and the special tool only when something has already failed. Note that this section documents the spare parts; the actual quantity of spare parts to be furnished under the contract, if any, is specified in the relevant product standard, not here. (15.1.2)

NOTE O&M data review and commissioning are interdependent and must be sequenced together. (16.1.1)

NOTE Functional performance testing under Commissioning depends on approved sequences of operation and equipment data; conversely, the commissioning process surfaces corrections that must flow back into the O&M manuals. If the two are scheduled independently, testing stalls waiting on documentation, or the final manuals ship without the commissioning corrections. The project schedule shall treat the O&M-submittal and commissioning milestones as a coordinated sequence, not parallel afterthoughts. (16.1.2)