Operation and Maintenance Data
Remake batch 25 and its neighbor re-points, batch 24 where missing, and the adopted-electrical-code parameter: brought in line with the authoring repository
Showing changes from Rev 2
to Rev 3
in Operation and Maintenance Data.
---
title: Operation and Maintenance Data
…2 unchanged lines
description: >
When to use: preparing, organizing, and delivering operation and maintenance (O&M) data packages for building systems and equipment on commercial, institutional, and industrial projects — directory of documentation, emergency operation manuals, operation manuals, product maintenance manuals, and systems-and-equipment maintenance manuals; covers delivery format (binders, PDF/A, structured data), copy counts, timing relative to Substantial Completion, and training coordination across new construction, renovation, and additions.
− Not intended for: commissioning execution and functional testing (sync/commissioning); final testing, adjusting, and balancing reports (sync/testing-adjusting-and-balancing); project closeout, final inspections, and occupancy (sync/closeout-procedures); the submittal review workflow itself (sync/submittal-and-quality-procedures); warranty terms and bond claims (sync/warranties-and-bonds); as-built record drawings and progress photos (sync/construction-progress-documentation); equipment labeling and nameplate conventions (sync/electrical-identification); temporary facilities (sync/temporary-facilities-and-controls); and quality control inspection records and material certifications (sync/quality-requirements).
+ Not intended for: commissioning execution and functional testing (sync/commissioning); final testing, adjusting, and balancing reports (sync/testing-adjusting-and-balancing); project closeout, final inspections, and occupancy (sync/closeout-procedures); the submittal review workflow itself (sync/submittal-and-quality-procedures); warranty terms and bond claims (sync/warranties-and-bonds); as-built record drawings and progress photos (sync/construction-progress-documentation); equipment labeling and nameplate conventions (sync/equipment-labeling); temporary facilities (sync/temporary-facilities-and-controls); and quality control inspection records and material certifications (sync/quality-requirements).
---
…20 unchanged lines
## This standard governs what the package contains and how it is delivered; it does not restate processes owned by adjacent standards. {note}
−## Commissioning execution and functional performance testing are governed by [[sync/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 [[sync/testing-adjusting-and-balancing]] and appended to the O&M manuals by reference only. Final inspections, certificate of occupancy, and punchlist resolution belong to [[sync/closeout-procedures]]. The submittal review and transmittal mechanics are governed by [[sync/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 [[sync/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 [[sync/construction-progress-documentation]]. Equipment labeling and nameplate conventions are specified in [[sync/electrical-identification]] and the equivalent mechanical identification sections — this standard requires only that installed identification match the O&M directory. {note}
+## Commissioning execution and functional performance testing are governed by [[sync/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 [[sync/testing-adjusting-and-balancing]] and appended to the O&M manuals by reference only. Final inspections, certificate of occupancy, and punchlist resolution belong to [[sync/closeout-procedures]]. The submittal review and transmittal mechanics are governed by [[sync/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 [[sync/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 [[sync/construction-progress-documentation]]. Equipment labeling and nameplate conventions are specified in [[sync/equipment-labeling]] and the equivalent mechanical identification sections — this standard requires only that installed identification match the O&M directory. {note}
## O&M data shall not be specified in general terms only; the manual types, organization, content depth, and copy counts shall all be defined.
…259 unchanged lines
### The directory shall identify each item of equipment by the same tag used on the installed identification and in the owner's CMMS.
−### 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 [[sync/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. {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 [[sync/equipment-labeling]] 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. {note}
## Whether the master directory is bound as a standalone index binder separate from the system binders shall be selected below.
…239 unchanged lines
### 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.