CBECC Software Enhancements -Technical Specification Development Workflow

CBECC Software Enhancements: Technical Specification Development Workflow

Purpose

The California Building Energy Code Compliance (CBECC) software is the public domain compliance tool developed and maintained by the California Energy Commission (CEC) to demonstrate performance compliance with Title 24, Part 6. California Investor-Owned Utilities (IOUs) Codes and Standards Team supports the needs of CBECC users by developing technical specification reports to summarize requested enhancements to the software. The technical specification effort is aimed at collecting stakeholder needs to accelerate the incorporation of new, desired updates to the Alternative Calculation Method (ACM) Reference Manual and CBECC software.    

California Building Energy Modeling Working Group 3 (CalBEM WG3) provides a forum for energy modelers and industry to propose new enhancement ideas, provide prioritization input and technical specification review. CalBEM WG3 focuses on increasing the usability, accuracy, and capabilities of California building energy modeling documentation, software, and technologies. Topic areas include energy modeling software for Title 24, Part 6 and for statewide programs. Efforts focus on short-term enhancements, encompassing the current or near-term energy code software, or long-term over the upcoming one to two code cycles.

Workflow

Energy Solutions with California Energy Commission (CEC) input and project funding by Southern California Edison (SCE) and Pacific Gas and Electric Company (PG&E) developed a systematic workflow. This workflow ensures CBECC enhancement requests follow a standardized and transparent process with input from all stakeholders.

The CBECC Enhancements technical specification development consists of six stages from initial idea intake, through prioritization and detailed specification development, to software implementation:

Stage	Name	Description	Responsibility / Contributors
1	Idea Intake	Collect ideas, organize and track progress	CalBEM WG3, Codes and Standard Enhancement (CASE) Teams, Consultants, Industry
2	Scoping Memo	Scope and feasibility defined with background research and justifications	Idea proposer, Consultants, Energy Solutions
3	Prioritization	Decision to proceed or defer	CEC, IOUs
4	Technical Specification Report Development	Detailed technical requirements defined including additional research and testing	Idea proposer/Consultants, IOUs, Energy Solutions
5	Final Review & Approval	Review technical specification for completeness and readiness for implementation	CEC, IOU and CalBEM WG3
6	Software Implementation	Enhancement added to CBECC	CEC and CBECC Developers Team

A brief description of each stage is provided below:

Stage 1 – Idea Intake

Objective: Capture and document all proposed software enhancement ideas and proposals in a centralized repository.  Review for scope alignment and prioritize for scoping memo development.

How to submit an idea?
Anyone can submit ideas to the CBECC Enhancement Project via the CalBEM website (link to survey), WG3 meetings, or direct outreach to your utility program contact. Provide a brief description of the proposed enhancement, the problem it addresses, and its expected benefit to CBECC users or compliance pathways.

Stage 2 – Scoping Memo

Objective: Define the scope, objectives, and feasibility of each proposed enhancement to inform prioritization and planning.

How to develop a scoping memo?
For each enhancement idea submitted, the enhancement proposer develops a scoping memo with additional research and stakeholder input, typically including:

• Problem statement and rationale
• Proposed scope and type of enhancement (identify whether it is related to standard design, proposed design, output reports, updating default values to correct unrealistic assumptions, etc.)
• Potential benefits to CBECC users (including number of users impacted), energy savings, compliance pathways, and modeling accuracy
• Preliminary assessment of effort and complexity

Scoping memos may be developed by anyone submitting the enhancement idea, subject matter experts or members of CalBEM WG3, or any consultant interested in championing the idea.  Energy Solutions reviews the Scoping Memo to ensure completeness and shares with stakeholders. At this stage, CEC, IOUs, and stakeholders may provide feedback to refine the scope or identify concerns.  A scoping memo template is available (link to scoping memo template).

Stage 3 – Prioritization

Objective: Evaluate and rank proposed enhancements based on value, complexity, stakeholder needs, and alignment with program goals.

How are enhancements prioritized?
The project team presents Scoping Memos for proposed enhancements at WG3 meetings (quarterly), IOU/vendor meetings (monthly), at CEC coordination meetings (quarterly), or via online surveys (ad hoc).  The authors of the scoping memos typically present the idea for prioritization.  CEC reviews prioritization input and makes final recommendation on which enhancements will proceed with developing a technical specification report. A CBECC Enhancement tracker is updated with prioritization information and posted to the CalBEM website.

Consultant/Modelers role: CalBEM WG3 members and other stakeholders are encouraged to participate in prioritization discussions, provide feedback via surveys, and share insights on the value and feasibility of proposed enhancements.

Stage 4 – Technical Specification Report Development

Objective: Develop a detailed technical specification report that describes modeling changes, algorithms, inputs/outputs, and Alternative Calculation Method (ACM) Reference Manual updates required to implement the enhancement in CBECC software.

Technical Specification Development Process:

1. Consultants/Project Team typically lead the development of the technical specification.  All enhancement idea authors and consultants can be lead authors of technical specification development. Funding for technical specification development is subject to CEC prioritization and availability of IOU funding. 
2. Once developed, the draft technical specification report is shared with CalBEM WG3, IOUs, CEC, and other interested stakeholders for review and comment. 
3. IOUs conduct status reviews and offer feedback during development.
4. CalBEM WG3 reviews and comments on draft Tech Specs.
5.  The project team incorporates feedback and finalizes the Tech Spec.

Each technical specification report includes the following:

• Gap analysis: What is missing or incorrect in current CBECC modeling capabilities?
• Ruleset definition: How should the proposed measure or feature function within the ACM framework?
• Algorithm development: Define calculations, assumptions, and modeling logic.
• Input/output specification: What new or modified user inputs are required? What outputs or reports will be generated?
• ACM Reference Manual markup: Draft language and tables for inclusion in Appendix C of Title 24, Part 6 CASE reports or other ACM sections.
• Coordination plan: Identify dependencies on other enhancements, code cycle updates, or implementation details.

An example, completed technical specification report is available (link to example tech spec report).

Stage 5 – Final Review & Handoff

Objective: Obtain final approval from CEC, prioritize the enhancement for implementation, and hand off the technical specification report and supporting materials to the CEC implementation team.

Approval Process:

1. CalBEM WG3 provides final comments on the technical specification.
2. The CEC conducts a final review of the technical specification.
3. Consultants/Project Team finalize the technical specification and prepare the handoff package; may offer optional implementation assistance as needed.
4. CEC reviews, approves, and prioritizes the technical specification for the CBECC development team.

 

Stage 6 – Software Implementation

Objective: Integrate the approved enhancement as described in the technical specification report into CBECC and release an updated version of the software.  CEC works with the CBECC development team to implement the enhancement.  Once the software is updated/released, the enhancement idea will be considered complete.

Consultant/Modeler role: The project team may provide ongoing implementation assistance, answer technical questions or clarify modeling requirements as the CBECC development team implements software changes.  Users and stakeholders are encouraged to test new CBECC release, provide feedback on functionality, and report any issues to the project team for further action.