Emergent Metering
    Sign in
    Back to blog
    Industry Solutions
    Emergent Team·June 6, 2026·6 min read

    The MEP Engineer's Specification Guide for IECC Submetering: How to Write a Metering Spec That Passes Code Review on the First Submission

    Share:
    The MEP Engineer's Specification Guide for IECC Submetering: How to Write a Metering Spec That Passes Code Review on the First Submission

    Every IECC 2021 and 2024 compliant building needs an energy monitoring specification on the construction documents. Yet most MEP firms have never written one because submetering was not mandatory before the 2021 edition. This guide walks engineers through the specification process step by step: what to include in Division 26 (Electrical) and Division 25 (Integrated Automation), how to map sensors to circuits on the electrical one-line, what accuracy and data retention requirements to call out, and how to specify the PowerRadar unified front end as the data acquisition system.

    Where Metering Lives in the Construction Documents

    Energy monitoring specifications typically span two CSI MasterFormat divisions. Division 26 (Electrical) Section 26 09 43 (Network Lighting Controls) or a new section 26 27 26 (Wiring Devices) covers the metering hardware: sensors, current transformers, branch circuit monitors, and their locations on the electrical distribution system. Division 25 (Integrated Automation) or a dedicated section within Division 26 covers the data acquisition system: the communication bridge, cloud platform, data storage requirements, reporting capabilities, and integration with non-electrical meters.

    Some firms create a standalone specification section (26 27 16 — Electrical Metering or 26 29 00 — Low-Voltage Monitoring Equipment) to consolidate all metering requirements in one place. The approach matters less than ensuring that every code requirement is addressed in the specification and that the contractor understands exactly which circuits require sensors, what sensor model to install on each, and how the data flows from sensor to reporting platform.

    Key Specification Elements

    1. Scope and Code Reference

    The specification should explicitly reference the applicable code section: IECC 2021 Section C405.12, IECC 2024 Section C405.13, or ASHRAE 90.1-2019/2022 Section 8.4.3, depending on the jurisdiction. It should state the building's gross conditioned floor area and confirm that it exceeds the applicable threshold (25,000 sqft for 2021, 10,000 sqft for 2024). It should list the required end-use categories and any additional categories specified by the owner or local amendments.

    2. Sensor Schedule

    A sensor schedule—typically shown on the electrical drawings as a table or on a dedicated metering diagram—maps every monitoring point to a specific piece of equipment and assigns a sensor model. Each row identifies the panel name, circuit number, load served (e.g., RTU-1, LP-2A, RP-3), sensor model (PAN-10, PAN-12, PAN-14, PAN-42, or S7100 BCM), CT size (if applicable), and IECC end-use category (HVAC, Interior Lighting, Exterior Lighting, Plug Loads, Process, EV Charging).

    3. Accuracy and Data Requirements

    The specification must call out the code's accuracy requirement (±2 percent for the 2021 IECC; verify with local amendments for 2024). Data recording intervals must be specified (minimum 15-minute for 2024 IECC and ASHRAE 90.1; hourly minimum for 2021 IECC). Data retention must be specified as 36 months minimum. The specification should require that the data acquisition system provide hourly, daily, monthly, and annual graphical reports accessible through a web-based interface and that the reporting mechanism be permanently installed and accessible to building operations personnel.

    4. Communication and Integration

    The specification should identify the communication pathway: wireless 915 MHz from Panoramic Power sensors to Gen 4+ Bridge, and from bridge to PowerRadar cloud via LAN, WiFi, or 4G LTE cellular. For non-electrical meters integrated via Modbus or pulse, the specification should identify the data hub (AcquiSuite, JACE, or Optergy) and the communication protocol for each non-electrical meter. If BMS integration is required, specify the protocol (BACnet IP, Modbus TCP) and the data points to be shared.

    5. Acceptance Testing and Commissioning

    The specification should require the contractor to demonstrate that every sensor is reporting data to the PowerRadar platform, that device groups correctly map to IECC end-use categories, that data is recording at the specified interval, and that the reporting interface generates the required graphical reports. A functional performance test should verify that alerts trigger correctly, that automated reports deliver on schedule, and that historical data is accessible for the full retention period. The commissioning agent (required under ASHRAE 90.1-2019 for buildings over 10,000 sqft) should include the metering system in the commissioning plan.

    Emergent Metering provides specification templates, sensor schedule spreadsheets, and sample Division 26 language to engineers at no cost. Contact sales@emergentmetering.com or call 215-645-7141 to request specification support for your project.

    About Emergent Metering Solutions

    Emergent Metering Solutions provides commercial and industrial metering hardware, installation support, and energy analytics services. We specialize in electric meters, water meters, BTU meters, compressed air meters, gas meters, and steam meters with Modbus RTU, BACnet IP, pulse output, and wireless communication options. Our Managed Intelligence services deliver automated reporting, anomaly detection, tenant billing, and AI-powered consumption forecasting. We support compliance with IECC 2021, ASHRAE 90.1-2022, NYC Local Law 97, Boston BERDO 2.0, DC BEPS, California LCFS, and EU CSRD requirements.

    Contact our engineering team for meter selection guidance, system design, and project quotes.

    Explore More Resources

    We use cookies to analyze site traffic and improve your experience. Privacy Policy