Exhibit C - BECRT Deliverables and Milestones - BECRT_1.xlsx

XLSX spreadsheet 37 KB Posted

Attached to
RFP 2526053
Solicitation number
0000039947
Issued by
California

About this file

Summary

This document is an Exhibit C deliverables and milestones schedule submitted as part of RFP 2526053 for the Building Embodied Carbon Reporting Tool (BECRT) Solution by the California Department of Technology. The solicitation establishes a comprehensive project structure organized into five tasks covering ongoing project management activities and four sequential software development releases. Task 1 includes continuous project management deliverables such as monthly and weekly status reports, project management plans, task accomplishment plans, project schedules, meeting documentation, and deliverable tracking throughout the contract term. Tasks 2 through 5 address the BECRT Minimum Viable Product (MVP) and three subsequent post-MVP releases, each progressing through Planning, Analysis, Design, Execution, Testing, and Deployment phases. The MVP development includes critical components such as registration, fee modules, data submission, query, and export functionality, while subsequent releases add ledger capabilities, fee calculation and collection modules, and advanced reporting and correspondence functionality. All phases include comprehensive security, compliance, and documentation requirements aligned with California government standards, including Privacy Impact Assessments, Security Plans, System Security Plans, and vulnerability scanning protocols. The deliverables schedule specifies completion timeframes for each phase ranging from initiation through end-of-phase milestones, with deployment phases culminating in knowledge transfer, lessons learned documentation, and transition planning by the end of Release 3.

The document does not contain explicit pricing information, contract term length, renewal options, award dates, set-asides, incumbent vendor information, or funding source details. The bidder response date of July 31, 2026 is referenced, though specific proposal submission dates and other key action dates are referenced as contained in separate solicitation documents within a zip file. The schedule requires bidders to formally agree to produce and meet each proposed deliverable through a yes/no confirmation column, establishing clear performance accountability for all defined milestones and outputs across the entire project lifecycle.

View the file

Other files

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

Task 1

A: Deliverable 1: Ongoing
Phase #PhaseReleaseProposed Deliverable #Proposed DeliverablesDeliverable FrequencyBidder Agrees to Produce and Meet? (Yes/No)
1.1OngoingOngoing1.1.1Monthly Status Reports (MSRs)End of the Month
1.1.2Weekly Status Reports (WSRs)End of the Week
1.1.3Project Management Plan (PMP)Submit at pre-planning stage and update until formal CARB Project Manager (PM) acceptance is received
1.1.4Task Accomplishment Plan (TAP)End of the Month
1.1.5Project Schedule Development and UpdatesFirst Draft at Planning Stage and Updates are completed every Week
1.1.6Meeting Participation, Setup and DocumentationOngoing
1.1.7Meeting Notes DevelopmentOngoing
1.1.8Deliverable Tracker Steps ExecutionOngoing
1.1.9Deliverable Tracker Updates/CommunicationOngoing
1.1.10Deliverables' documentation Update and ResubmissionOngoing
1.1.11Deliverables Routing Process for SignaturesOngoing
1.1.12Action Items Log, Issues and Risks Register, Decision Log DocumentationOngoing

State of California California Department of Technology Exhibit C: BERCT Deliverables and Milestones RFP 2526053 Bidder Response July 31, 2026

&P

Task 2

B: Deliverable 2: BECRT Minimum Viable Product (MVP)
Phase #PhaseReleaseProposed Deliverable #Proposed DeliverablesCompletion TimeframeBidder Agrees to Produce and Meet? (Yes/No)
2.1PlanningBECRT Minimum Viable Product (MVP)2.1.1Vendor Onboarding Sessions Participation (PMO Review)Beginning of Planning
2.1.2Vendor Onboarding Sessions and Assignments completion (PMO Review)Beginning of Planning
2.1.3Implementation PlanDuring Planning
2.1.4SharePoint Site Setup and Usage (PMO Review)During Planning
2.1.5Project documentation Setup and Sharing (PMO Review)During Planning
2.1.6Product RoadmapDuring Planning
2.1.7Training PlanDuring Planning
2.1.8Business Continuity PlanDuring Planning
2.1.9Testing PlanDuring Planning
2.1.10Azure DevOps Product Backlog Hierarchy Setup and UpdatesEnd of Planning
2.1.11Azure DevOps Product Backlog, Sprint Backlog, Testing Artifacts and Reporting Metrics Setup and UpdatesEnd of Planning
2.1.12Go-Live PlanEnd of Planning
2.1.13Release PlanEnd of Planning
2.2AnalysisBECRT Minimum Viable Product (MVP)2.2.1User Story Development, Updates and FinalizationDuring Analysis
2.2.2Azure DevOps Sprint Allocation exportsEnd of Analysis
2.3DesignBECRT Minimum Viable Product (MVP)2.3.1Architecture Board Presentation MaterialsInitiation of Design
2.3.2Architecture Board ApprovalInitiation of Design
2.3.3California Cloud Services Assessment (CCSA) ParticipationDuring Design
2.3.4California Cloud Services Assessment (CCSA) DocumentationDuring Design
2.3.5Entity Relationship Diagram (ERD)During Design
2.3.6Data DictionaryDuring Design
2.3.7Enterprise Data QuestionnaireDuring Design
2.3.8Business GlossaryDuring Design
2.3.9Enterprise Data ReviewDuring Design
2.3.10Database ReviewDuring Design
2.3.11Privacy Impact Assessment (PIA)During Design
2.3.12eDiscovery and Litigation Hold PolicyDuring Design
2.3.13Privacy NoticeDuring Design
2.3.14FIPS Data Classification DocumentDuring Design
2.3.15STRIDE ModelDuring Design
2.3.16Information Technology Risk Assessment SessionsDuring Design
2.3.17Information Technology Risk Assessment DocumentDuring Design
2.3.18Firewall Design DiagramDuring Design
2.3.19System Security PlanDuring Design
2.3.20Business Impact Analysis (BIA)End of Design
2.3.21Technology Recovery Plan (TRP)End of Design
2.3.22Information Security Incident Response Plan (ISIRP)End of Design
2.3.23Visual Design ApprovalEnd of Design
2.4ExecutionBECRT Minimum Viable Product (MVP)2.4.1Database Request Form DocumentInitiation of Execution
2.4.2Registration, Fee Module Banner, Data Submission, Reference Tables, Data Query, Filter and Export Results Modules ExecutionEnd of Execution
2.4.3Requirements Traceability Matrix (RTM)End of Execution
2.4.4Database UpdatesDuring Execution
2.4.5Test CasesEnd of Execution
2.5TestingBECRT Minimum Viable Product (MVP)2.5.1Test ExecutionDuring Testing
2.5.2Vulnerability Scan ReportsDuring Testing
2.5.3Security ReviewDuring Testing
2.5.4User Interface ReviewDuring Testing
2.5.5Code ReviewDuring Testing
2.5.6DevOps ReviewDuring Testing
2.5.7GIS ReviewDuring Testing
2.5.8Infrastructure ReviewDuring Testing
2.5.9Defect Management Process ExecutionDuring Testing
2.5.10Test ReportsDuring Testing
2.6DeploymentBECRT Minimum Viable Product (MVP)2.6.1Release Activities DevelopmentInitiation of Deployment
2.6.2User Manuals (Documentation Review)During Deployment
2.6.3Training MaterialsDuring Deployment
2.6.4Standard Operating Procedures (SOP)During Deployment
2.6.5Information Technology Risk Assessment UpdatesDuring Deployment
2.6.6System Security Plan UpdatesDuring Deployment
2.6.7Knowledge Transfer MaterialsDuring Deployment
2.6.8Knowledge Transfer SessionsDuring Deployment
2.6.9Lessons Learned DocumentationEnd of Deployment
2.6.10Lessons Learned SessionsEnd of Deployment
2.6.11Release Activities CompletionEnd of Deployment
2.6.12Release LogEnd of Deployment

State of California California Department of Technology Exhibit C: BERCT Deliverables and Milestones RFP 2526053 Bidder Response

&P

Task 3

C. Deliverable 3: BECRT Post Minimum Viable Product – Release 1
Phase #PhaseReleaseProposed Deliverable #Proposed DeliverablesCompletion DateBidder Agrees to Produce and Meet? (Yes/No)
3.1PlanningBECRT Post Minimum Viable Product – Release 13.1.1Project documentation Setup and Sharing (PMO Review)During Planning
3.1.2Azure DevOps Product Backlog Hierarchy Setup and UpdatesEnd of Planning
3.1.3Azure DevOps Product Backlog, Sprint Backlog, Testing Artifacts and Reporting Metrics Setup and UpdatesEnd of Planning
3.1.4Release PlanEnd of Planning
3.2AnalysisBECRT Post Minimum Viable Product – Release 13.2.1User Story Development, Updates and FinalizationDuring Analysis
3.2.2Azure DevOps Sprint Allocation exportsEnd of Analysis
3.3DesignBECRT Post Minimum Viable Product – Release 13.3.1Entity Relationship Diagram (ERD)During Design
3.3.2Data DictionaryDuring Design
3.3.3Enterprise Data QuestionnaireDuring Design
3.3.4Business GlossaryDuring Design
3.3.5Enterprise Data ReviewDuring Design
3.3.6Database ReviewDuring Design
3.3.7Visual Design ApprovalEnd of Design
3.4ExecutionBECRT Post Minimum Viable Product – Release 13.4.1Registration, Ledger, Data Query, Filter and Export Results Modules ExecutionInitiation of Execution
3.4.2Requirements Traceability Matrix (RTM)End of Execution
3.4.3Database UpdatesDuring Execution
3.4.4Test CasesEnd of Execution
3.5TestingBECRT Post Minimum Viable Product – Release 13.5.1Test ExecutionDuring Testing
3.5.2Vulnerability Scan ReportsDuring Testing
3.5.3Security ReviewDuring Testing
3.5.4User Interface ReviewDuring Testing
3.5.5Code ReviewDuring Testing
3.5.6DevOps ReviewDuring Testing
3.5.7GIS ReviewDuring Testing
3.5.8Infrastructure ReviewDuring Testing
3.5.9Defect Management Process ExecutionDuring Testing
3.5.10Test ReportsDuring Testing
3.6DeploymentBECRT Post Minimum Viable Product – Release 13.6.1Release Activities DevelopmentInitiation of Deployment
3.6.2User Manuals (Documentation Review)During Deployment
3.6.3Training MaterialsDuring Deployment
3.6.4Standard Operating Procedures (SOP)During Deployment
3.6.5Information Technology Risk Assessment UpdatesDuring Deployment
3.6.6System Security Plan UpdatesDuring Deployment
3.6.7Knowledge Transfer MaterialsDuring Deployment
3.6.8Knowledge Transfer SessionsDuring Deployment
3.6.9Lessons Learned DocumentationEnd of Deployment
3.6.10Lessons Learned SessionsEnd of Deployment
3.6.11Release Activities CompletionEnd of Deployment
3.6.12Release LogEnd of Deployment

State of California California Department of Technology Exhibit C: BERCT Deliverables and Milestones RFP 2526053 Bidder Response

&P

Task 4

D. Deliverable 4: BECRT Post Minimum Viable Product – Release 2
Phase #PhaseReleaseProposed Deliverable #Proposed DeliverablesCompletion DateBidder Agrees to Produce and Meet? (Yes/No)
4.1PlanningBECRT Post Minimum Viable Product – Release 24.1.1Project documentation Setup and Sharing (PMO Review)During Planning
4.1.2Azure DevOps Product Backlog Hierarchy Setup and UpdatesEnd of Planning
4.1.3Azure DevOps Product Backlog, Sprint Backlog, Testing Artifacts and Reporting Metrics Setup and UpdatesEnd of Planning
4.1.4Release PlanEnd of Planning
4.2AnalysisBECRT Post Minimum Viable Product – Release 24.2.1User Story Development, Updates and FinalizationDuring Analysis
4.2.2Azure DevOps Sprint Allocation exportsEnd of Analysis
4.3DesignBECRT Post Minimum Viable Product – Release 24.3.1Entity Relationship Diagram (ERD)During Design
4.3.2Data DictionaryDuring Design
4.3.3Enterprise Data QuestionnaireDuring Design
4.3.4Business GlossaryDuring Design
4.3.5Enterprise Data ReviewDuring Design
4.3.6Database ReviewDuring Design
4.3.7Visual Design ApprovalEnd of Design
4.4ExecutionBECRT Post Minimum Viable Product – Release 24.4.1Data Submission, Fee Calculation and Collection, Data Query, Filter and Export Results Modules ExecutionEnd of Execution
4.4.2Requirements Traceability Matrix (RTM)End of Execution
4.4.3Database UpdatesDuring Execution
4.4.4Test CasesEnd of Execution
4.5TestingBECRT Post Minimum Viable Product – Release 24.5.1Test ExecutionDuring Testing
4.5.2Vulnerability Scan ReportsDuring Testing
4.5.3Security ReviewDuring Testing
4.5.4User Interface ReviewDuring Testing
4.5.5Code ReviewDuring Testing
4.5.6DevOps ReviewDuring Testing
4.5.7GIS ReviewDuring Testing
4.5.8Infrastructure ReviewDuring Testing
4.5.9Defect Management Process ExecutionDuring Testing
4.5.10Test ReportsDuring Testing
4.6DeploymentBECRT Post Minimum Viable Product – Release 24.6.1Release Activities DevelopmentInitiation of Deployment
4.6.2User Manuals (Documentation Review)During Deployment
4.6.3Training MaterialsDuring Deployment
4.6.4Standard Operating Procedures (SOP)During Deployment
4.6.5Information Technology Risk Assessment UpdatesDuring Deployment
4.6.6System Security Plan UpdatesDuring Deployment
4.6.7Knowledge Transfer MaterialsDuring Deployment
4.6.8Knowledge Transfer SessionsDuring Deployment
4.6.9Lessons Learned DocumentationEnd of Deployment
4.6.10Lessons Learned SessionsEnd of Deployment
4.6.11Release Activities CompletionEnd of Deployment
4.6.12Release LogEnd of Deployment

State of California California Department of Technology Exhibit C: BERCT Deliverables and Milestones RFP 2526053 Bidder Response

&P

Task 5

E. Deliverable 5: BECRT Post Minimum Viable Product – Release 3
Phase #PhaseReleaseProposed Deliverable #Proposed DeliverablesCompletion DateBidder Agrees to Produce and Meet? (Yes/No)
5.1PlanningBECRT Post Minimum Viable Product – Release 35.1.1Project documentation Setup and Sharing (PMO Review)During Planning
5.1.2Azure DevOps Product Backlog Hierarchy Setup and UpdatesEnd of Planning
5.1.3Azure DevOps Product Backlog, Sprint Backlog, Testing Artifacts and Reporting Metrics Setup and UpdatesEnd of Planning
5.1.4Release PlanEnd of Planning
5.2AnalysisBECRT Post Minimum Viable Product – Release 35.2.1User Story Development, Updates and FinalizationDuring Analysis
5.2.2Azure DevOps Sprint Allocation exportsEnd of Analysis
5.3DesignBECRT Post Minimum Viable Product – Release 35.3.1Entity Relationship Diagram (ERD)During Design
5.3.2Data DictionaryDuring Design
5.3.3Enterprise Data QuestionnaireDuring Design
5.3.4Business GlossaryDuring Design
5.3.5Enterprise Data ReviewDuring Design
5.3.6Database ReviewDuring Design
5.3.7Visual Design ApprovalEnd of Design
5.4ExecutionBECRT Post Minimum Viable Product – Release 35.4.1Reports, Correspondence Functionality, Filter and Export Results Modules ExecutionEnd of Execution
5.4.2Requirements Traceability Matrix (RTM)End of Execution
5.4.3Database UpdatesDuring Execution
5.4.4Test CasesEnd of Execution
5.5TestingBECRT Post Minimum Viable Product – Release 35.5.1Test ExecutionDuring Testing
5.5.2Vulnerability Scan ReportsDuring Testing
5.5.3Security ReviewDuring Testing
5.5.4User Interface ReviewDuring Testing
5.5.5Compliance AnalysisDuring Testing
5.5.6Code ReviewDuring Testing
5.5.7DevOps ReviewDuring Testing
5.5.8Reporting ReviewDuring Testing
5.5.9GIS ReviewDuring Testing
5.5.10Infrastructure ReviewDuring Testing
5.5.11Defect Management Process ExecutionDuring Testing
5.5.12Test ReportsDuring Testing
5.6DeploymentBECRT Post Minimum Viable Product – Release 35.6.1Release Activities DevelopmentInitiation of Deployment
5.6.2User Manuals (Documentation Review)During Deployment
5.6.3Training MaterialsDuring Deployment
5.6.4Standard Operating Procedures (SOP)During Deployment
5.6.5Information Technology Risk Assessment UpdatesDuring Deployment
5.6.6System Security Plan UpdatesDuring Deployment
5.6.7Knowledge Transfer MaterialsDuring Deployment
5.6.8Knowledge Transfer SessionsDuring Deployment
5.6.9Lessons Learned DocumentationEnd of Deployment
5.6.10Lessons Learned SessionsEnd of Deployment
5.6.11Release Activities CompletionEnd of Deployment
5.6.12Release LogEnd of Deployment
5.6.13Maintenance & Operations (M&O) PlanEnd of Deployment
5.6.14Transition PlanEnd of Deployment

State of Calirornia California Department of Technology Exhibit C: BERCT Deliverables and Milestones RFP 2526053 Bidder Response

&P

File details come from the government source that posted it. Updated .