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. The 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 manages this initiative with CalBEM WG3 input, CEC approval, and funding by IOUs (Southern California Edison and Pacific Gas and Electric Company). A systematic workflow was developed to ensure CBECC enhancement requests follow a standardized and transparent process with input from all stakeholders.

For any questions or comments, please contact Jacob Rumschlag (jrumschlag@energy-solution.com), Krishnan Gowri (kgowri@energy-solution.com), and/or Chris Uraine (curaine@energy-solution.com).

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

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.

Process:

1. Anyone can be an enhancement proposer and submit ideas via the CBECC Software Enhancements Idea Form on the CalBEM website.
   • Proposers should provide a name for the proposed CBECC enhancement, a brief description, the problem it addresses, its expected benefit to CBECC users or compliance pathways, and the proposer’s email.
2. Energy Solutions will receive and review the proposed enhancement and reach out to the proposer about proceeding to Stage 2.

Stage 2 – Scoping Memo

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

Process:

1. After the idea is proposed in Stage 1, Energy Solutions will reach out to the proposer about developing a scoping memo for Stage 2.
2. For each enhancement idea submitted, the proposer and/or any consultant interested in being the lead author for the proposal will develop a scoping memo
   • A scoping memo template is available here: link to scoping memo template.
3. Scoping memos typically includes:
   • 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
4. Energy Solutions reviews the scoping memo to ensure completeness and prepares to share with stakeholders.
5. IOUs and CalBEM WG3 are given the opportunity to provide feedback to refine the scope or identify concerns. 
   

Stage 3 – Prioritization

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

Process:

1. Energy Solutions coordinates with the lead author to present the proposed enhancement at CalBEM WG3 meetings (quarterly), IOU meetings (monthly), at CEC coordination meetings (quarterly), or via online surveys (ad hoc).
   • 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.
2. The CEC reviews the obtained stakeholder prioritization input and scoping memos to make the final decision on which enhancements should proceed with technical specification report development.

Stage 4 – Technical Specification Report Development

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

Process:

1. The lead author drafts technical specification report.
   • An example, completed technical specification report is available here: link to example technical specification report.
2. Each technical specification report typically 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.
3. Once developed, the draft technical specification report is shared with CalBEM WG3, IOUs, CEC, and other interested stakeholders for the opportunity to review and provide comments.   

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.

Process:

1. The CEC is given a final opportunity to review the technical specification report and provide comments.
2. The lead author finalizes the technical specification report and prepares the handoff package.
3. The CEC prioritizes the technical specification for the CBECC development team in Stage 6.

 

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. 

Process:

1. The CEC works with the CBECC development team to implement the enhancement. 
2. The technical specification lead author may provide ongoing implementation assistance, answer technical questions, or clarify modeling requirements as the CBECC development team implements software changes. 
3. 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.
4. Once the CBECC software is updated/released, the enhancement idea will be considered complete.

Jump up to Workflow ^

---

CBECC Software Enhancements Idea Submission Form