Corpus sync: neutrality remakes, note hygiene, datasheet relocation, transformer-split cross-refs
---
title: Operation and Maintenance Data
…41 unchanged lines
### Conflating O&M data with record documents produces gaps and duplication at handover. {note}
−### Record documents — the marked-up as-built drawings, the shop drawing log, the approved submittal record — are produced and controlled under [[sync/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. {note}
+### Record documents — the marked-up as-built drawings, the shop drawing log, the approved submittal record — are produced and controlled under [[sync/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.
## Quality control inspection records, material certifications, and approval test reports are procedural quality documents governed by [[sync/quality-requirements]] and are included in the O&M package only where this standard or the owner expressly calls for them. {note}
…92 unchanged lines
## Whether a structured data export (COBie) is required in addition to the PDF package shall be selected below.
−## 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. {note}
−
```datasheet
label: Structured Data (COBie) Export Required
…5 unchanged lines
```
+## 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. {note}
+
# Quality Assurance {toc}
…10 unchanged lines
### Generic catalog cuts that do not match the installed equipment are a recurring defect. {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. {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.
## Each manual shall be organized using a single scheme coordinated with the owner's computerized maintenance management system (CMMS).
…20 unchanged lines
## The preliminary O&M submittal shall be delivered the specified number of days before the scheduled date of Substantial Completion.
−### Setting the submission deadline at or after Substantial Completion defeats the purpose of the review. {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. {note}
−
```datasheet
label: Preliminary O&M Submittal Lead Time Before Substantial Completion
…7 unchanged lines
```
+### Setting the submission deadline at or after Substantial Completion defeats the purpose of the review. {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. {note}
+
## The final, corrected O&M package shall be delivered no later than the time selected below.
…16 unchanged lines
## Hard-copy manuals shall be delivered in three-ring binders with the specified ring capacity and configuration.
−### Round-ring binders exceeding 1 inch shall not be used.
−
−### 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. {note}
−
```datasheet
label: Binder Ring Configuration
…7 unchanged lines
```
+### Round-ring binders exceeding 1 inch shall not be used.
+
+### 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. {note}
+
## Each binder shall use labeled tab dividers and a table of contents at the front identifying the contents behind each tab.
### Tabbed organization with a per-binder table of contents is what makes a binder navigable. {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. {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.
## Pages shall be 8.5 × 11 inch (letter) format; drawings larger than letter size shall be reduced to 11 × 17 inch and folded to letter size, or provided full size in a separate drawing set.
### Reduced-size as-built drawings inserted into the binder are a reference convenience, not a substitute for the record drawing set. {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 [[sync/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. {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 [[sync/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.
```datasheet
…65 unchanged lines
### The emergency manual's value is speed of access under stress. {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. {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.
## An emergency manual shall be provided for each of the following systems where present on the project: fire alarm, smoke control, emergency power and standby generator, elevator and escalator, laboratory fume hoods, fuel gas systems, and any NFPA 101-regulated egress system.
…22 unchanged lines
### Seasonal changeover is a frequent source of operator error when it is not documented. {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. {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.
## The operation manual shall describe each system interlock, including what it protects against and the conditions under which it acts.
…5 unchanged lines
## The operation manual shall include a plain-language systems narrative describing how integrated systems function together, not equipment data alone.
−### A systems narrative is what lets a new operator understand the building as a set of interacting systems rather than a pile of equipment. {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. {note}
−
```datasheet
label: Systems Narrative Depth
…5 unchanged lines
```
+### A systems narrative is what lets a new operator understand the building as a set of interacting systems rather than a pile of equipment. {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. {note}
+
# Product Maintenance Manuals {toc}
…4 unchanged lines
### Maintenance intervals stated only as "per manufacturer" without a schedule force the operator to reconstruct the program. {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. {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.
## Inspection and maintenance frequency intervals reflected in the schedule shall be consistent with ANSI/ASHRAE/ACCA 180 for HVAC systems and with NFPA 25 for water-based fire protection systems.
…5 unchanged lines
## HVAC product maintenance manuals shall be prepared in accordance with ASHRAE Guideline 4 and shall at minimum include equipment schedules, sequences of operation, maintenance schedules, filter schedules, lubrication charts, and belt and drive data.
−### SMACNA O&M guidance defines the manufacturer data that air, duct, and hydronic system manuals must carry. {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. {note}
−
```datasheet
label: HVAC O&M Content Set (ASHRAE Guideline 4 minimum)
…15 unchanged lines
```
+### SMACNA O&M guidance defines the manufacturer data that air, duct, and hydronic system manuals must carry. {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. {note}
+
## Each product maintenance manual shall include the manufacturer's service-representative contact information, including a 24-hour emergency telephone number where the manufacturer provides one.
…20 unchanged lines
### A restorable software backup is the owner's only path to recovery after a controller failure or a corrupted change. {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. {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.
## Control system O&M data shall be delivered as an explicit, itemized deliverable comprising sequences of operation, input/output (I/O) point lists, control wiring diagrams, and a backup of the BAS/DDC programming and configuration.
### Control system documentation is routinely missing from general O&M submittals and discovered only at commissioning. {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 [[sync/commissioning]] so that controls O&M data is approved before functional performance testing depends on it. {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 [[sync/commissioning]] so that controls O&M data is approved before functional performance testing depends on it.
## Whether control system O&M data is delivered as a dedicated standalone binder set or integrated into the system binders shall be selected below.
…18 unchanged lines
### Training delivered by someone unfamiliar with the as-built system teaches the catalog, not the building. {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. {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.
### Training shall use the approved O&M manuals as the reference material so that operators learn the same documents they will rely on afterward.
…65 unchanged lines
## The Contractor shall coordinate with the commissioning agent to identify which O&M submittals must be reviewed and approved before functional performance testing begins, and shall sequence those submittals in the project schedule accordingly.
−### O&M data review and commissioning are interdependent and must be sequenced together. {note}
+### O&M data review and commissioning are interdependent and must be sequenced together.
−### Functional performance testing under [[sync/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. {note}
+### Functional performance testing under [[sync/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.