Set up NFRC's Component Modeling Approach (CMA) to determine curtain wall U-factor and SHGC via simulation instead of whole-unit testing
domain: nfrc.org · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Confirm on nfrc.org the current governing procedures — CMA determines U-factor under NFRC 100 and solar heat gain coefficient under NFRC 200, using NFRC-approved simulation software rather than testing a physical whole-assembly specimen.
Confirm the current list of NFRC-approved CMA simulation software and approved component databases (frame, glass, spacer) on nfrc.org, since approvals and version numbers change periodically.
Assemble the three required component inputs — the specific frame profile's simulated performance, the specific glass makeup's optical/thermal properties, and the specific spacer system's certified performance — each of which must independently carry current NFRC-recognized data.
Confirm the curtain wall geometry is modeled per NFRC's current curtain wall-specific simulation guidance (e.g., treatment of intermediate verticals/horizontals as jamb/head/sill members) rather than using a standard window model.
Route the CMA simulation output through an NFRC-licensed simulator for certification/labeling if project documents require an NFRC label, since self-run simulation without going through a licensed simulator/certification path is generally not code-acceptable on its own.
Known gotchas
CMA outputs are only as reliable as the underlying component database entries — verify the specific frame, glass, and spacer combination actually has current, valid NFRC-recognized data rather than assuming generic values apply.
This is a distinct process from searching the NFRC Certified Products Directory for an already-labeled product — CMA is used to generate new simulated performance values, and requires an NFRC-licensed simulator to be code-acceptable in most jurisdictions.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?