Standardize faucet parameter names by fixing them at the spec-sheet level, before submittal, using a single crosswalk document that maps every technical term to its code reference and its CMMS field. If the submittal reads “thermostatic mixing valve compliance” and the CMMS asset tag reads “ASSE 1070 rating,” a facilities tech doing a shutoff six months after handover will not connect the two, and that gap is where compliance data disappears.
Why Naming Drift Breaks Airport Handovers
Terminal and MRO faucet installs move through more hands than a typical commercial job: design engineer, GC, plumbing sub, commissioning agent, airport facilities, and eventually a CMMS administrator who never saw the original spec. Each party tends to relabel the same parameter in their own shorthand. A spec sheet might say “ASSE 1070 compliant,” the submittal log might shorten it to “mixing valve cert,” and the CMMS record might just say “hot water limiter.” All three describe the same requirement, but a text search during an FAA or TSA facilities audit will only find one of them.
This matters more at airports than in general commercial construction because faucet compliance data at a terminal is not just maintenance trivia. ADA reach ranges, scald-prevention ratings, and water-conservation specs get pulled during accessibility audits, insurance reviews, and sustainability reporting. If the parameter name used in the audit request doesn’t match anything in the facilities database, the fixture reads as non-compliant even when it isn’t.
Core Faucet Parameters Needing Locked Names
Not every spec on a faucet cut sheet needs a locked naming convention. Cosmetic finish and manufacturer SKU can vary in phrasing without causing problems downstream. But a small set of parameters carry compliance weight and need identical wording from spec to submittal to asset tag:
- ASSE 1070 mixing valve compliance — governs outlet water temperature limiting; must appear with this exact code number, not “thermostatic valve” or “scald guard,” in every document.
- 0.5 GPM aerator flow rate per EPAct 1992 — the federal maximum for public lavatory faucets; write it as a flow rate with the standard cited, not just “low-flow” or “water-efficient.”
- 3/8 inch NPS supply thread size — determines which supply lines and shutoff valves are compatible; a mismatch here causes actual field delays, not just paperwork confusion.
- ADA operable-parts reach range (15 to 48 inches) — ties the faucet handle location to accessibility compliance and needs to match the architectural accessibility drawings, not just the plumbing spec.
- Mounting configuration (deck-mount, wall-mount, sensor-activated) — affects both installation crew instructions and CMMS equipment classification.
Everything else, including finish, faucet body style, or handle design, can be described loosely because it doesn’t get checked during a compliance audit. If a concourse restroom package specifies matte black fixtures for a design refresh, for example, the procurement team might reference something like black kitchen faucets for finish and style consistency in a crew lounge or admin pantry area, and that reference doesn’t need code-level naming discipline the way the mixing valve or flow rate does.
Aligning Spec Sheets With CMMS Asset Tags
Most naming drift happens at the CMMS entry point, because facilities staff building asset records were not in the room when the spec was written. They’re often working from a cut sheet PDF and abbreviating fields to fit a database template with character limits. The fix isn’t asking facilities to type more; it’s giving them a pre-built field map before they ever touch the asset record.
Before handover, produce a field-mapping table that lists every parameter name exactly as it appears on the approved submittal, next to the CMMS field it should populate. Hand this to whoever is doing asset entry, not just to the project closeout binder. A crosswalk that lives in a binder nobody opens after substantial completion has the same failure rate as no crosswalk at all.
| Submittal Parameter Name | CMMS Asset Field | Code Reference |
|---|---|---|
| ASSE 1070 Mixing Valve Compliance | Compliance_MixingValve | ASSE 1070 |
| Aerator Flow Rate | FlowRate_GPM | EPAct 1992, 0.5 GPM max |
| Supply Thread Size | SupplyConnection_NPS | 3/8 in NPS |
| ADA Reach Range | AccessCompliance_Reach | ADA 308, 15-48 in |
| Mounting Type | Equipment_MountConfig | N/A |
This table should be finalized during design development, not during closeout. If it’s built after the fixtures are already installed, you’re reverse-engineering compliance data from field photos, which is slower and less reliable than locking the names up front.
Mapping ASSE and ADA Codes To Labels
Code references get mangled in a specific, predictable way: someone drops the standard number and keeps only the plain-language description. “ASSE 1070” becomes “anti-scald valve,” and “ADA 308” becomes “accessible reach.” Plain language is fine for a maintenance work order a tech reads on a tablet, but it’s useless for an audit trail that needs to prove code compliance to an inspector or an insurance underwriter.
The solution is to never let the code number and the plain description exist as separate fields. Every parameter label should carry both, formatted the same way every time: standard number first, plain description second, in parentheses. “ASSE 1070 (mixing valve, scald prevention)” survives a database export, a PDF search, and a verbal handoff meeting equally well. A label that’s only “scald prevention” survives none of those, because nobody searching for ASSE 1070 will find it.
The same logic applies to EPAct flow rate citations and ADA reach ranges. Write the number, then the plain-language context, every time, in every document that touches the fixture record.
Building A Handover Naming Crosswalk Document
The crosswalk document itself doesn’t need to be complicated. It needs to be the single source of truth that every party references instead of retyping parameter names from memory. At minimum, it should include:
- The exact parameter name as it will appear on every document, spec sheet, submittal, and CMMS record, from project kickoff through year-one facilities audits.
- The applicable code or standard number attached to that parameter, written in full, not abbreviated.
- The CMMS field name it maps to, confirmed with whoever administers that system, not assumed by the design team.
- A revision date and owner, so if a parameter name changes mid-project, there’s a record of when and why.
Distribute this crosswalk to the plumbing sub, the commissioning agent, and the facilities asset administrator before installation begins, not at closeout. The goal is that nobody ever has to guess whether “mixing valve cert” and “ASSE 1070” refer to the same fixture attribute, because the crosswalk already told them.
Before submittal review, pull the crosswalk table and confirm every locked parameter, ASSE 1070, EPAct flow rate, 3/8 inch NPS thread, and ADA reach range, appears with identical wording in the spec, the submittal log, and the CMMS field map. If any of those four terms shows up differently in two places, fix the wording before the fixture ships, not after it’s behind a wall.