Exhibit B - Functional & Non-Functional Requirements - BECRT.xlsm
XLSM spreadsheet 124 KB Posted
- Attached to
- RFP 2526053
- Solicitation number
- 0000039947
- Issued by
- California
About this file
Exhibit B: Functional & Non-Functional Requirements for Building Embodied Carbon Reporting Tool
This document is a functional and non-functional requirements specification for the Building Embodied Carbon Reporting Tool (BECRT), a state contract opportunity issued by the California Department of Technology (CDT) under RFP 2526053. The BECRT solution is a comprehensive web-based system designed to manage company registration, user authentication, data submission, fee collection, correspondence management, ledger operations, and reporting capabilities for building embodied carbon emissions tracking and compliance. The system must support multiple user roles including external users (Registrants, DataSubmitters, CompanyAdmins, ThirdParty reporters, and Persons with Signatory Authority) and internal CARB staff (InternalAdmins and InternalUsers). Key functional requirements include company lifecycle management with approval workflows, Excel/CSV/XML template-based data submission with dynamic configuration capabilities, automatic and manual fee waiver processing, real-time data validation with configurable error handling, and correspondence thread management with search and filtering functionality. The system must accommodate up to 1,000 concurrent external users and 100 concurrent internal users during submittal periods, with data uploads completing in 500 milliseconds for 100 concurrent users. The Environmental Ledger component must track product carbon intensity, product tracking, GHG emissions calculations, and reduction compliance transactions across multiple reporting entities including manufacturers, owner-builders, and importers.
Non-functional requirements mandate compliance with California AB 434, ADA Section 508 accessibility standards, and responsive user interface design compatible with the latest versions of Chrome, Edge, Safari, and Firefox browsers. The solution must adhere to CARB's OIS Coding Standards, Software Architecture Standards, and approved technology stack, with all source code maintained in CARB's version control repository. The system requires design documentation approval prior to implementation, code walkthroughs with OIS technical staff and security representatives at each iteration, ADA accessibility scanning for all public-facing documents and pages with zero errors, and comprehensive user and administrator documentation. The reporting period is defined as January 1 through December 31, with a submittal period from January 1 through March 31 of the following year. The bidder must mark "Yes" or "No" in the compliance column for each requirement, with blank or "No" answers potentially resulting in proposal rejection.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| Exhibit D - Cost Workbook - BECRT_1.xlsx | XLSX spreadsheet | |
| CARB Building Embodied Carbon Reporting Tool (BECRT).pdf | ||
| Exhibit D - Cost Workbook - BECRT.xlsx | XLSX spreadsheet | |
| Exhibit C - BECRT Deliverables and Milestones - BECRT.xlsx | XLSX spreadsheet | |
| CARB Building Embodied Carbon Reporting Tool (BECRT)_1.pdf | ||
| Exhibit B - Functional & Non-Functional Requirements - BECRT_1.xlsm | XLSM spreadsheet | |
| Exhibit C - BECRT Deliverables and Milestones - BECRT_1.xlsx | XLSX spreadsheet |
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
Instructions
| EXHIBIT B: Functional and Non-Functional Requirements |
| Enter full name of Bidder in Row #4 |
(Example ABC Corporation)
| ABC Corporation |
| Overview and Instructions |
| The Bidder must indicate compliance and confirmation to each of the requirements by marking “Yes” or “No” in the column labeled “Will Solution Meet Requirement? (Yes/No)”. A blank or “No” answer in this column may be considered non-responsive and may be the basis for rejecting the Bidder's proposal. |
Below are the definitions and descriptions for the columns within this spreadsheet. Please review this content before proceeding to the next tab.
Requirement Column Definitions:
Functional Requirements Column - Definition A - Objective # - Indicates the Project Approval Lifecycle (PAL) Stage 1 Objective number B - Requirement Category - Indicates the Requirement Category Name C - Requirement Sub-Category - Indicates the Sub-Category that the Requirement belongs to D - Requirement Number - Indicates the Requirement Number E - Requirement - Indicates the Requirement Description F - Will Solution Meet Requirement? (Yes/No) - Indicates the column where Bidders mark their responses as Yes to indicate the solution's ability to meet the requirement or No if the solution does not meet the requirement G - Priority - Indicates the Priority Classification for the requirement (Mandatory/Mandatory Optional/Desirable)
Non-Functional Requirements Column - Definition A - Requirement Category - Indicates the Requirement Category Name B - Requirement Number - Indicates the Requirement Number C - Requirement - Indicates the Requirement Description D - Bidder's Library Reference Documents - Indicates the Bidder's Library for accessing reference documents for the Non-Functional Requirements E- Acceptance Vehicle - Indicates the acceptance vehicle/mode for each requirement F - Phase - Indicates the Phase the requirement must be completed G - Acceptance Criteria - Indicates the acceptance criteria for each requirement H - Will Solution Meet Requirement? (Yes/No) - Indicates the column where Bidders mark their responses as Yes to indicate the solution's ability to meet the requirement or No if the solution does not meet the requirement I - Priority - Indicates the Priority Classification for the requirement (Mandatory/Mandatory Optional/Desirable)
State of California California Department of Technology RFP 2526053 Bidder Response July 31, 2026
&P
Functional
| Stage 1 Objective # | Requirement Category | Requirement Sub-Category | Requirement Number | Requirement | Will Solution Meet Requirement? | ||
| (Yes/No) | Priority | ||||||
| 1.1 | Data Submission | Business Rules & Additional Requirements | BRR-001 | User Data Locking - The system shall prevent reporters from altering data after submission deadlines. | Mandatory | ||
| 1.1 | Data Submission | Business Rules & Additional Requirements | BRR-002 | The system shall allow ExternalAdmins to request access to submitted data locked after submission deadline if an InternalAdmin approves the request. | Mandatory | ||
| 1.1 | Data Submission | User Roles & Permissions | BRR-003 | The system shall allow InternalAdmin Users to edit data in all Internal Data fields except the fields that identify the PSA. No data entered by the submitter can be altered by an Internal User | Mandatory | ||
| 1.1 | Data Submission | User Roles & Permissions | BRR-004 | The system shall prevent CARB internal users from altering company-submitted data. | Mandatory | ||
| 1.1 | Data Submission | Misc Rules | BRR-005 | Field Behavior – The system shall autoformat values and allow users to press tab, enter, or touch screen to advance the cursor to the next field. | Mandatory | ||
| 1.1 | Data Submission | Misc Rules | BRR-006 | The system shall send validated product cost/other data to ledger/fee modules. | Mandatory | ||
| 1.1 | Data Submission | Misc Rules | BRR-007 | The system shall send the Web Data and Excel/CSV or XML template-submitted data to the ledger/product module. | Mandatory | ||
| 1.2 | User Sign-up, Company Registration, Company Administration, and CARB Administration | Company Administration | CAD-001 | The system shall allow Company administration features to be accessible only if CompanyStatus is shown as "Approved". | Mandatory | ||
| 1.2 | User Sign-up, Company Registration, Company Administration, and CARB Administration | Company Administration | CAD-002 | The system shall only allow Company Admins to invite other external users to their company. This is accomplished from a user admin screen. The designated new member receives an email with a link to create their account. Once completed, they assume the role specified by the admin. | Mandatory | ||
| 1.2 | User Sign-up, Company Registration, Company Administration, and CARB Administration | Company Administration | CAD-003 | The system shall allow the company admin(s) to view and perform the following list of actions for all registered users, including changing user's roles and activating and deactivating accounts. |
- The system shall allow the CompanyAdmin to have the option to "Permanently Deactivate Account" when deactivating a user account.
- The system shall require an Internal User to enter a "reason for modification" if they reactivate a permanently deactivated account."
| - The system shall allow a CompanyAdmin to enter the email and role into an Invite New User" form to invite new external users to their company." | Mandatory | |||||
| 1.2 | User Sign-up, Company Registration, Company Administration, and CARB Administration | Company Administration | CAD-004 | The system shall detect whether an invited External CompanyAdmin or DataSubmitters user's email matches the domain in the company profile. If domain does not match, then stop invited user from continuing action (company would either update email domain so they match, or require user with different email to contact CARB for resolution). InternalAdmins or InternalUsers can override this requirement. | Mandatory | |
| 1.2 | User Sign-up, Company Registration, Company Administration, and CARB Administration | Company Administration | CAD-005 | The system shall display a visual notification and block the invitation if the external user is already associated with another company, when inviting a CompanyAdmin or DataSubmitter. | Mandatory | |
| 1.2 | User Sign-up, Company Registration, Company Administration, and CARB Administration | Company Administration | CAD-006 | The system shall validate for invited ThirdParty that the company does not already have a ThirdParty user. If there are already ThirdParty users, a validation screen warns the company that there are current ThirdParty users, displaying their email addresses, requiring CompanyAdmin to verify that they want to proceed anyway. | Mandatory | |
| 1.2 | User Sign-up, Company Registration, Company Administration, and CARB Administration | Company Administration | CAD-007 | The system shall check whether an invited ThirdParty user is associated with other companies. If so, the system displays a warning to PSA and CompanyAdmins and requires a positive affirmation to proceed. This affirmation must be logged and available for future reference. | Mandatory | |
| 1.2 | User Sign-up, Company Registration, Company Administration, and CARB Administration | Company Administration | CAD-008 | The system shall send an email invitation to the external user when the PSA or CompanyAdmin invites an external user and selects their role. | Mandatory | |
| 1.2 | User Sign-up, Company Registration, Company Administration, and CARB Administration | Company Administration | CAD-009 | The system shall provide a link in the email for the external user to click on to creates their CARB specified Authentication Service (Okta/login account), if one doesn't already exist. | Mandatory | |
| 1.2 | User Sign-up, Company Registration, Company Administration, and CARB Administration | Company Administration | CAD-010 | The system shall allow CompanyAdmins to initially assign and subsequently change other users' CompanyRole. | Mandatory | |
| 1.2 | User Sign-up, Company Registration, Company Administration, and CARB Administration | Company Administration | CAD-011 | The system shall notify a user of any role change upon first login after the role change. | Mandatory | |
| 1.2 | User Sign-up, Company Registration, Company Administration, and CARB Administration | Company Administration | CAD-012 | The system shall follow the same role matrix for ThirdParty and DataSubmitter. Admins cannot invite or modify the assignment or role of a ThirdParty user. Role matrix is defined by CARB. | Mandatory | |
| 1.2 | User Sign-up, Company Registration, Company Administration, and CARB Administration | Company Administration | CAD-013 | The system shall only allow the PSA to assign another PSA to replace them. The PSA is a high-level approver role. | Mandatory | |
| 1.2 | User Sign-up, Company Registration, Company Administration, and CARB Administration | Company Administration | CAD-014 | The system shall require a CompanyAdmin to contact CARB for assistance in naming a new PSA if the designated PSA becomes unavailable. | Mandatory | |
| 1.2 | User Sign-up, Company Registration, Company Administration, and CARB Administration | Company Administration | CAD-015 | The system shall follow the same role matrix for PSA and CompanyAdmin. In the role matrix PSA also has the additional role of adding, deleting, or editing ThirdParty information. No other external roles will have this ability. | Mandatory | |
| 1.2 | User Sign-up, Company Registration, Company Administration, and CARB Administration | Company Administration | CAD-016 | The system shall allow users with the roles of DataSubmitter, CompanyAdmin, or ThirdParty to submit the completed data using Excel/CSV or XML data templates and contain XML schema developed by contractors in the form of XSD files to facilitate XML data submission. | Mandatory | |
| 1.1 | Data Submission | Configure Data Submission Excel/CSV or XML Imports | CDS-001 | The system shall allow InternalAdmins and InternalUsers to add, edit, or deactivate required data fields to the Excel/CSV or XML data submission template at any time for each CompanyType. (See IUA-002) |
- Field Validation (example)
- Error messages (example)
- If you add a calculation field, where else should this field be shown? (e.g. excel template, UI) (example)
- UI (ex. Radio button, drop down)
| - Ex. When Internal Admins and InternalUser create a new field in the excel, the system shall allow them to choose where the data appears within the system | Mandatory | |||||
| 1.1 | Data Submission | Configure Data Submission Excel/CSV or XML Imports | CDS-002 | The system shall require an Internal User to enter a reason for modification if they add, edit, or deactivate a required data field in the Excel/CSV or XML data submission template. | Mandatory | |
| 1.1 | Data Submission | Configure Data Submission Excel/CSV or XML Imports | CDS-003 | The system shall allow internal and external data submission fields to be configurable. | Mandatory | |
| 1.1 | Data Submission | Configure Data Submission Excel/CSV or XML Imports | CDS-004 | The system shall allow authorized InternalAdmins and InternalUsers to mark required external data submission fields as inactive at any time and be tagged as not to be completed for external users. | Mandatory | |
| 1.1 | Data Submission | Configure Data Submission Excel/CSV or XML Imports | CDS-005 | The system shall allow authorized Internal Admins and InternalUsers to add fields to the internal validation and calculation tables at any point in time, no matter the calendar date or the submittal year. | Mandatory | |
| 1.1 | Data Submission | Configure Data Submission Excel/CSV or XML Imports | CDS-006 | The system shall require an Internal User to enter a reason for modification if they add, edit, or deactivate fields within the internal validation and calculation tables. | Mandatory | |
| 1.1 | Data Submission | Configure Data Submission Excel/CSV or XML Imports | CDS-007 | The system shall have an intuitive graphical user interface for the addition of new data fields by Internal Admins and InternalUsers in BECRT Excel/CSV or XML templates, validation tables, reference tables, and calculation tables by Internal Admins and InternalUsers. | Mandatory Optional | |
| 1.1 | Data Submission | Configure Data Submission Excel/CSV or XML Imports | CDS-008 | The system shall execute External Data Submission calculations as defined by CARB. | Mandatory | |
| 1.2 | User Sign-up, Company Registration, Company Administration, and CARB Administration | Company Lifecycle and Roles | CLR-001 | The system shall utilize CompanyRole to define the external user's role within the company: |
- Registrant performs Company Registration with company role as CompanyReg. Once the PSA completes registration, the Registrant role is converted to DataSubmitter.
- DataSubmitter - Can perform data submissions as defined by Excel templates only (meaning they may not edit web form data or invite additional internal users in any role).
- CompanyAdmin - Can manage users and company data.
- CompanyAdmin can invite additional CompanyAdmins and DataSubmitters.
- CompanyAdmin can deactivate other CompanyAdmins and DataSubmitters.
- Business Rule: if a CompanyAdmin deactivates another CompanyAdmin, a notice of this action will be sent to the PSA by email.
- CompanyAdmins can perform data submissions in web forms, Excel/CSV, and XML for company information such as Person with Signatory Authority (PSA), company address. CompanyAdmin and other external data submitters can perform data submissions using Excel/CSV, XML, or JSON (for specific Environmental Product Declaration) templates.
-CompanyAdmin and other external data submitters can perform data submissions for non-web-form using either Excel/CSV, or XML templates. However, data cannot be submitted in both formats or partially in XML and partially in Excel data submission formats.
- ThirdParty - Same role as company DataSubmitter, but CompanyAdmin cannot add a ThirdParty reporter (only a PSA can do that), change their role, and this external user may hold a ThirdParty role in multiple companies. Can perform data submissions as defined by Excel, CSV, or XML templates only (meaning they will not be able to edit web form data).
- Person with Signatory Authority (PSA) -
- High-level role that reviews the company registration.
- Only PSA can designate a ThirdParty for Excel/CSV, JSON, or XML data submission.
- Designates the initial CompanyAdmin.
- Can designate subsequent CompanyAdmins.
- PSA is alerted by the system if the ThirdParty is already in the BECRT system as a ThirdParty for another company (the name of the other company will not be shared with the PSA).
- PSA can actively accept this condition through an acknowledgement of system warning and continue the process to invite the ThirdParty or choose to not invite the ThirdParty.
| - PSA is also a CompanyAdmin | Mandatory | |||||
| 1.2 | User Sign-up, Company Registration, Company Administration, and CARB Administration | Company Lifecycle and Roles | CLR-002 | The system shall allow a Company to only have one PSA. | Mandatory | |
| 1.2 | User Sign-up, Company Registration, Company Administration, and CARB Administration | Company Lifecycle and Roles | CLR-003 | The system shall allow only an external user with ThirdParty data submitter role to be a member of multiple Companies. | Mandatory | |
| 1.2 | User Sign-up, Company Registration, Company Administration, and CARB Administration | Company Lifecycle and Roles | CLR-004 | The system shall utilize CompanyStatus to control the lifecycle of a company registration and shall include: CompanyReg, SubmittedToPSA, Approved, Rejected, Disabled. | Mandatory | |
| 1.1 | Data Submission | Submission Confirmation and Legal Attestation | CNF-001 | The system shall require that the PSA check a box to affirmatively attest that the submitted data are correct prior to formal submission. | Mandatory | |
| 1.1 | Data Submission | Submission Confirmation and Legal Attestation | CNF-002 | The system shall require the PSA to acknowledge understanding of California Code of Regulations Title 17, Sections 91000-91022 specifying how the California Air Resources Board handles confidential information. | Mandatory | |
| 1.1 | Data Submission | Submission Confirmation and Legal Attestation | CNF-003 | The system shall provide a checkbox for each company PSA to affirm that their submission is Confidential Business Information (CBI). | Mandatory | |
| 1.2 | User Sign-up, Company Registration, Company Administration, and CARB Administration | Company Registration Form | CRF-001 | The system shall define the external user that registers a Company as the Registrant. | Mandatory | |
| 1.2 | User Sign-up, Company Registration, Company Administration, and CARB Administration | Company Registration Form | CRF-002 | The system shall split Company data entry into multiple forms and web pages. | Mandatory | |
| 1.2 | User Sign-up, Company Registration, Company Administration, and CARB Administration | Company Registration Form | CRF-003 | The system shall allow the Registrant to "Save Draft" of in-process registration. | Mandatory | |
| 1.2 | User Sign-up, Company Registration, Company Administration, and CARB Administration | Company Registration Form | CRF-004 | The system shall "autosave" periodically and prior to time out to protect Registrant from losing data entered due to web session timeout. | Mandatory | |
| 1.2 | User Sign-up, Company Registration, Company Administration, and CARB Administration | Company Registration Form | CRF-005 | Web session shall save and time out after 30 minutes of no activity. | Mandatory | |
| 1.2 | User Sign-up, Company Registration, Company Administration, and CARB Administration | Company Registration Form | CRF-006 | The system shall allow the Registrant to preview a formatted page in a read-only format prior to submitting. | Mandatory | |
| 1.2 | User Sign-up, Company Registration, Company Administration, and CARB Administration | Company Registration Form | CRF-007 | The system shall allow the Registrant to return to the Editable form from the preview page. | Mandatory | |
| 1.2 | User Sign-up, Company Registration, Company Administration, and CARB Administration | Company Registration Form | CRF-008 | The system shall allow the CompanyType to include these options: |
- Manufacturer that Does Not Report via Mandatory Reporting Regulation (MRR)
- Manufacturer that Does Report via Mandatory Reporting Regulation (MRR)
- Owner-Builder
| - Importer | Mandatory | ||||
| 1.2 | User Sign-up, Company Registration, Company Administration, and CARB Administration | Company Registration Form | CRF-009 | The system shall present the Registrant with a form requiring the following fields (See complete list in Data Definitions section): |
- CompanyCode (max 10 characters; uppercase letters, numbers, underscores only - validated unique system-wide, e.g., HM_DEPOT | KB_HOME |MAT_IMPORT |INSUL_MAN)
- CompanyName (Required)
- CompanyEIN (Required, format validated NN-NNNNNNN, must be unique)
- Complete Address including international addresses (Required)
- Include verification of address using CARB's recommended technology stack.
- CompanyType (Required: Select one or more from predefined list)
- PSA Information (Required: Name, Email and Phone)
| - Message - filled out by Registrant to PSA (especially if data corrected as a result of an initial request to PSA being rejected by PSA) | Mandatory | |||||
| 1.2 | User Sign-up, Company Registration, Company Administration, and CARB Administration | Company Registration Form | CRF-010 | The system shall allow a Company to have more than one CompanyType, except only one of the two categories of Manufacturer (that Does Report via MRR or that Does Not Report via MRR). | Mandatory | |
| 1.2 | User Sign-up, Company Registration, Company Administration, and CARB Administration | Company Registration Form | CRF-011 | The system shall allow a Company to choose the specific data entry type option for each CompanyType for each data entry session. | Mandatory | |
| 1.2 | User Sign-up, Company Registration, Company Administration, and CARB Administration | Company Registration Form | CRF-012 | The system shall include a required checkbox indicating agreement to the Terms and Conditions on the Company data entry form. | Mandatory | |
| 1.2 | User Sign-up, Company Registration, Company Administration, and CARB Administration | Company Registration Form | CRF-013 | The system shall display a Terms and Conditions link to text of the terms and conditions that opens in a separate window so that the Terms and Conditions can be viewed by the Registrant. | Mandatory | |
| 1.2 | User Sign-up, Company Registration, Company Administration, and CARB Administration | Company Registration Form | CRF-014 | The system shall allow the Registrant to check box to accept terms and conditions. Successful registration will require Registrant to check box to accept terms and conditions | Mandatory | |
| 1.2 | User Sign-up, Company Registration, Company Administration, and CARB Administration | Company Registration Form | CRF-015 | The system shall require the Registrant to enter the Name, Email, and Phone Number of the PSA. | Mandatory | |
| 1.2 | User Sign-up, Company Registration, Company Administration, and CARB Administration | Company Registration Form | CRF-016 | The system shall display a validation error if a required field is left null upon submission. | Mandatory | |
| 1.2 | User Sign-up, Company Registration, Company Administration, and CARB Administration | Company Registration Form | CRF-017 | The system shall limit a Registrant to submitting only one Company Registration. | Mandatory | |
| 1.2 | User Sign-up, Company Registration, Company Administration, and CARB Administration | Company Registration Form | CRF-018 | The system shall allow the Registrant to optionally provide text in the message field of the submission form to the PSA. | Mandatory | |
| 1.2 | User Sign-up, Company Registration, Company Administration, and CARB Administration | Company Registration Form | CRF-019 | The system shall validate that EIN is not already in use. | Mandatory | |
| 1.2 | User Sign-up, Company Registration, Company Administration, and CARB Administration | Company Registration Form | CRF-020 | The system shall validate that the CompanyCode is not already in use. | Mandatory | |
| 1.2 | User Sign-up, Company Registration, Company Administration, and CARB Administration | Company Registration Form | CRF-021 | The system shall change the CompanyStatus from "CompanyReg" to "SubmittedToPSA" upon successful submission by the Registrant. | Mandatory | |
| 1.2 | User Sign-up, Company Registration, Company Administration, and CARB Administration | Company Registration Form | CRF-022 | The system shall send an email to the PSA with a link for them to create an account, if an account for the PSA does not already exist, and proceed with PSA Review upon changing to SubmittedToPSA. | Mandatory | |
| 1.2 | User Sign-up, Company Registration, Company Administration, and CARB Administration | Company Registration Form | CRF-023 | The system shall ensure the submitted information becomes read-only for the Registrant when CompanyStatus changes to SubmittedToPSA. | Mandatory | |
| 1.2 | User Sign-up, Company Registration, Company Administration, and CARB Administration | Company Registration Form | CRF-024 | The system shall ensure that the information is fully editable (not read-only) for Registrant if the company's status changes back to CompanyReg | Mandatory | |
| 1.2 | User Sign-up, Company Registration, Company Administration, and CARB Administration | Company Registration Form | CRF-025 | The system shall render the link to the PSA for creating an account inactive if the PSA does not act within 14 days of receipt of email or the PSA rejects the account creation option. | Mandatory | |
| 1.2 | User Sign-up, Company Registration, Company Administration, and CARB Administration | Company Registration Form | CRF-026 | The system shall give the Registrant the option to "Recall Submission," changing CompanyStatus from "SubmittedToPSA" to "CompanyReg." | Mandatory | |
| 3.1 | Correspondence | Correspondence Thread and Entry Management | CRR-001 | The system shall include the following CorrespondenceType for both InternalUsers and ExternalUsers: |
- External Sign up and Login
- Company Registration
- Manage Company Users
- Modify Company PSA
- Data Submission
- Fee Collection
- Reports
- Internal User and Admin Registration - hide from external users
| - Other | Mandatory | |||||
| 3.1 | Correspondence | Correspondence Thread and Entry Management | CRR-002 | The system shall associate each CorrespondenceEntry with the user who entered it and the date/time of entry. | Mandatory | |
| 3.1 | Correspondence | Correspondence Thread and Entry Management | CRR-003 | The system shall allow internal and external users to select and respond to existing correspondence threads. | Mandatory | |
| 3.1 | Correspondence | Correspondence Thread and Entry Management | CRR-004 | The system shall allow all internal users to view and participate in correspondence threads as needed. | Mandatory | |
| 3.1 | Correspondence | Correspondence Thread and Entry Management | CRR-005 | The system shall allow all external users within a company to view and participate in correspondence threads associated with their company. | Mandatory | |
| 3.1 | Correspondence | Correspondence Thread and Entry Management | CRR-006 | The system shall allow internal admin staff to define communications created/viewed/edited based on user roles and note type. | Mandatory | |
| 3.1 | Correspondence | Correspondence Thread and Entry Management | CRR-007 | The system shall display a status indicator (open/closed) for each correspondence thread. | Mandatory | |
| 3.1 | Correspondence | Correspondence Thread and Entry Management | CRR-008 | The system shall allow users to respond only if the correspondence thread is open; closed threads shall be read-only. | Mandatory | |
| 3.1 | Correspondence | Correspondence Thread and Entry Management | CRR-009 | The system shall allow internal users to mark a correspondence thread as 'closed' once completed. | Mandatory | |
| 3.1 | Correspondence | Correspondence Thread and Entry Management | CRR-010 | The system shall allow ongoing access to closed correspondence threads for reference. | Mandatory | |
| 3.1 | Correspondence | Correspondence Thread and Entry Management | CRR-011 | Internal users must have the ability to reopen closed correspondence threads. | Mandatory | |
| 3.1 | Correspondence | Correspondence Thread and Entry Management | CRR-012 | The system shall allow the authorized users to view the existing email communication migrated data within the respective Correspondence threads represented in the same data format followed for the new correspondence threads. | Mandatory | |
| 3.1 | Correspondence | Search, Filter, and Tracking | CRR-013 | The system shall allow internal and external users to search, filter, and view correspondence history by date, user, ProductUploadID (Excel/CSV or XML file upload), CorrespondenceCategory, and status (open/closed). | Mandatory | |
| 3.1 | Correspondence | Search, Filter, and Tracking | CRR-014 | The system shall allow internal users to search and filter correspondence history the same categories as external users, and, in addition, by LEDGER TRANSACTION AND COMPANY. | Mandatory | |
| 3.1 | Correspondence | Search, Filter, and Tracking | CRR-015 | The system shall allow internal users to flag up to 10 correspondence threads as to-do items which will limit internal user correspondence to the internal user who flagged the correspondence. Also knows as “Claim” the issue. | Mandatory | |
| 3.1 | Correspondence | Search, Filter, and Tracking | CRR-016 | The system shall allow internal users to flag up to 10 correspondence threads as to-do items, indicating that these correspondence threads remain unresolved. This "claimed" flag shall be visible to all other internal users. | Mandatory | |
| 3.1 | Correspondence | Search, Filter, and Tracking | CRR-017 | The system shall allow internal users to flag correspondence related to ledger transactions for tracking. This is independent from CorrespondenceCategory. | Mandatory | |
| 3.1 | Correspondence | Search, Filter, and Tracking | CRR-018 | The system shall allow internal users to tag correspondence entries with priority levels (e.g., Urgent, Normal). | Mandatory | |
| 3.1 | Correspondence | Search, Filter, and Tracking | CRR-019 | The system shall make visible to internal users the priority levels for each tagged correspondence entry. | Mandatory | |
| 3.1 | Correspondence | Search, Filter, and Tracking | CRR-020 | The system shall allow attachments to CorrespondenceThreads, such as supporting documents, error messages, or screenshots. The file types allowed are: PDF, TXT, Word, CSV, XML, JPG, Excel/CSV. The maximum file size for attachments is 100MB. | Mandatory | |
| 3.1 | Correspondence | Notifications | CRR-021 | The system shall require notifications for correspondence updates to include a link to the specific thread within the BECRT application. | Mandatory | |
| 3.1 | Correspondence | Notifications | CRR-022 | The system shall generate email notifications to CARB staff assigned to Correspondence to alert them of new messages received. | Mandatory | |
| 3.1 | Correspondence | Security, Permissions, and Display | CRR-023 | The system shall prevent external users from deleting correspondence entries once submitted. | Mandatory | |
| 3.1 | Correspondence | Security, Permissions, and Display | CRR-024 | When correspondence threads are viewed by external users, the system shall display internal entries under a generic 'CARB Staff' identifier instead of individual usernames. | Mandatory | |
| 1.1 | Data Submission | Configure UI Screens | CUI-001 | The system shall allow InternalAdmins and InternalUsers to add, edit, or remove web form fields without negatively impacting functionality. | Mandatory Optional | |
| 1.1 | Data Submission | Configure UI Screens | CUI-002 | The system shall require an Internal User to enter a "reason for modification" if they add, edit, or deactivate web form fields. | Mandatory Optional | |
| 1.2 | User Sign-up, Company Registration, Company Administration, and CARB Administration | Authentication and User Management | DDS-001 | The system database structural guidance for Authentication and User Management proposed by CARB. Refer to the BECRT Data Definitions document for field information. | Mandatory | |
| 1.2 | User Sign-up, Company Registration, Company Administration, and CARB Administration | Company Lifecycle and Roles | DDS-002 | The system database structural guidance for Company Lifecycle and Roles proposed by CARB. Refer to the BECRT Data Definitions document for field information. | Mandatory | |
| 1.2 | User Sign-up, Company Registration, Company Administration, and CARB Administration | Company Registration Form | DDS-003 | The system database structural guidance for Company Registration Form proposed by CARB. Refer to the BECRT Data Definitions document for field information. | Mandatory | |
| 1.2 | User Sign-up, Company Registration, Company Administration, and CARB Administration | PSA Designation of Company Admin | DDS-004 | The system database structural guidance for PSA Designation of Company Admin proposed by CARB. Refer to the BECRT Data Definitions document for field information. | Mandatory | |
| 1.2 | User Sign-up, Company Registration, Company Administration, and CARB Administration | Post-Submission Actions | DDS-005 | The system database structural guidance for Post-Submission Actions proposed by CARB. Refer to the BECRT Data Definitions document for field information. | Mandatory | |
| 1.2 | User Sign-up, Company Registration, Company Administration, and CARB Administration | Company Administration | DDS-006 | The system database structural guidance for Company Administration proposed by CARB. Refer to the BECRT Data Definitions document for field information. | Mandatory | |
| 1.2 | User Sign-up, Company Registration, Company Administration, and CARB Administration | Internal User Administration | DDS-007 | The system database structural guidance for Internal User Administration proposed by CARB. Refer to the BECRT Data Definitions document for field information. | Mandatory | |
| 1.1 | Data Submission | Dynamic Data Validation | DDV-001 | The system shall allow Internal Admins and InternalUsers to add new data fields to the BECRT Excel/CSV or XML data template without negatively impacting functionality. | Mandatory Optional | |
| 1.1 | Data Submission | Dynamic Data Validation | DDV-002 | The system shall allow InternalAdmins and InternalUsers to add new data fields and calculations to the validation reference tables without negatively impacting functionality. | Mandatory | |
| 1.1 | Data Submission | Dynamic Data Validation | DDV-003 | The system shall allow InternalAdmins and InternalUsers to define and edit calculations via an intuitive GUI. | Mandatory | |
| 1.1 | Data Submission | Data Submission Waiver | DSW-001 | The system shall allow a waiver for Excel/CSV, JSON, or XML Template Data Submission. | Mandatory | |
| 1.1 | Data Submission | Automatic Data Submission Waiver | DSW-002 | The system shall follow predefined Excel/CSV or XML Template Data Submission waiver as defined by CARB. | Mandatory | |
| 1.1 | Data Submission | Automatic Data Submission Waiver | DSW-003 | The system shall send a notification via the correspondence function to inform external user that no Excel/CSV or XML Template Data Submission is required if the submission qualifies for waiver. | Mandatory | |
| 1.1 | Data Submission | Automatic Data Submission Waiver | DSW-004 | The system shall provide the ability for the external user to download the CARB confirmation of exemption If the Company qualifies for an Excel/CSV or XML Data Submission waiver. | Mandatory | |
| 1.1 | Data Submission | Automatic Data Submission Waiver | DSW-005 | The system shall allow internal users to modify Excel/CSV or XML Template Data Submission waiver status for external users. All modifications must be logged with timestamps and reason codes. | Mandatory | |
| 1.1 | Data Submission | Automatic Data Submission Waiver | DSW-006 | The system shall require an Internal User to enter a reason for modification if they modify an Excel/CSV or XML Template Data Submission waiver status. | Mandatory | |
| 1.1 | Data Submission | Manual Data Submission Waiver | DSW-007 | The system shall allow external users to request an Excel/CSV or XML Template Data Submission waiver via Correspondence Thread, and provide supporting documentation in Excel/CSV, JPG, XML, TXT, Word, and PDF formats. | Mandatory | |
| 1.1 | Data Submission | Manual Data Submission Waiver | DSW-008 | The system shall only process an Excel/CSV or XML Template Data Submission waiver request after the Excel or XML Template Data Submission waiver supporting documentation and attestation that information is truthful is uploaded to the system. | Mandatory | |
| 1.1 | Data Submission | Manual Data Submission Waiver | DSW-008 | The system shall notify the external user at the time the Excel/CSV or XML Template Data Submission waiver is requested by way of a text warning that the submission will not proceed until supporting documentation and an attestation that the information is truthful. | Mandatory | |
| 1.1 | Data Submission | Manual Data Submission Waiver | DSW-009 | The system shall specify each type of Excel/CSV or XML Template Data Submission waiver available as defined by CARB plus “Other” with a text description. | Mandatory | |
| 1.1 | Data Submission | Manual Data Submission Waiver | DSW-010 | The system shall send an email notification to a CARB-designated group when a Excel/CSV or XML Template Data Submission waiver request is submitted. | Mandatory | |
| 1.1 | Data Submission | Manual Data Submission Waiver | DSW-011 | The system shall allow CARB users to review the Excel/CSV or XML Template Data Submission waiver request with the option to approve or deny the request. | Mandatory | |
| 1.1 | Data Submission | Manual Data Submission Waiver | DSW-012 | The system shall allow external users to submit multiple Excel/CSV or XML Template Data Submission waiver requests up to a maximum number defined by CARB staff. | Mandatory | |
| 1.1 | Data Submission | Manual Data Submission Waiver | DSW-013 | The system shall allow CARB staff to define the maximum number of Excel/CSV or XML Template Data Submission waiver requests allowed for an external user to submit. | Mandatory | |
| 1.1 | Data Submission | Manual Data Submission Waiver | DSW-014 | The system shall track all Excel/CSV or XML Template Data Submission waivers and allow internal users to generate reports on approved and denied waivers with the following information on the reports: |
o Date/time waiver is submitted, o External user submitting request, o Notification of waiver approval or denial, with a date/time stamp
| o Confirmation that the fee waiver outcome was sent, including date/time stamp | Mandatory | |||||
| 1.1 | Data Submission | Manual Data Submission Waiver | DSW-015 | The system shall notify external users of the outcome of the Excel/CSV or XML Template Data Submission waiver request via the correspondence function. | Mandatory | |
| 1.1 | Fee Collections | Fee Calculation | FEE-001 | The system shall generate an Invoice of Fee Calculation after the external user completes their Data Submission. | Mandatory | |
| 1.1 | Fee Collections | Fee Calculation | FEE-002 | The system shall generate an invoice containing all necessary information as defined by law for a valid invoice. | Mandatory | |
| 1.1 | Fee Collections | Fee Calculation | FEE-003 | If the fee has been recalculated, the system shall generate an updated invoice is generated. | Mandatory | |
| 1.1 | Fee Collections | Fee Calculation | FEE-004 | The system shall have the ability to generate a positive, negative, or zero balance invoice. | Mandatory | |
| 1.1 | Fee Collections | Fee Calculation | FEE-005 | The system shall automatically generate a confirmation of an updated invoice and refund in the correspondence module. | Mandatory | |
| 1.1 | Fee Collections | Fee Calculation | FEE-006 | The system shall follow predefined fee calculation rules set by CARB regulations, including considerations for product type, quantity, and adjustments for inflation where applicable. | Mandatory | |
| 1.1 | Fee Collections | Fee Calculation | FEE-007 | The system shall execute Fee calculations as defined by CARB. | Mandatory | |
| 1.1 | Fee Collections | Fee Calculation | FEE-008 | The system shall allow Internal User to search and view for required Fee Information with the search criteria and results defined by CARB. | Mandatory | |
| 1.1 | Fee Collections | Fee Administration | FEE-009 | The system shall allow CARB admin staff the ability to search for required Fee Collections with the following information: |
Defined by CARB and receive, view search results with the below information
| Defined by CARB | Mandatory | |||||
| 1.1 | Fee Collections | Fee Administration | FEE-010 | The system shall provide a notification banner while registering a Company that informs the authorized user that the Fee Payment module is inactive. | Mandatory | |
| 1.1 | Fee Collections | Fee Administration | FEE-011 | The system shall provide the Fee Payment module notification banner to authorized users until the Fee Payment module is implemented on the Company registration location. | Mandatory | |
| 1.1 | Fee Collections | Fee Administration | FEE-012 | The system shall allow InternalAdmin to enter fees (currency) into a price list within the reporting period. | Mandatory | |
| 1.1 | Fee Collections | Fee Administration | FEE-013 | The system shall process batch fee and allow External User to make one fee payment. | Mandatory | |
| 1.1 | Fee Collections | Automatic Fee Waiver | FEE-014 | The system shall follow predefined fee exemption rules set by CARB regulations, including considerations for revenue and adjustments of fees to account for inflation where applicable. | ||
| - If the annual sales revenue is less than the CARB-defined annual sales revenue, then exempt the reporting entity. | Mandatory | |||||
| 1.1 | Fee Collections | Automatic Fee Waiver | FEE-015 | The system shall send a notification via the correspondence function to inform external user that no fee is required if the submission qualifies for exemption. | Mandatory | |
| 1.1 | Fee Collections | Automatic Fee Waiver | FEE-016 | If the Company qualifies for a waiver, the system shall provide the ability for the external user to download the CARB confirmation of exemption. | Mandatory | |
| 1.1 | Fee Collections | Automatic Fee Waiver | FEE-017 | The system shall allow internal users to modify fee exemption status for external users. All modifications must be logged with timestamps and reason codes. | Mandatory | |
| 1.1 | Fee Collections | Automatic Fee Waiver | FEE-018 | The system shall require an Internal User to enter a reason for modification if they modify a fee exemption status. | Mandatory | |
| 1.1 | Fee Collections | Manual Fee Waiver | FEE-019 | The system shall allow external users to request a fee waiver via Correspondence Thread, and provide supporting documentation in Excel/CSV, CSV, JPG, XML, Word, TXT, and PDF formats. | Mandatory | |
| 1.1 | Fee Collections | Manual Fee Waiver | FEE-020 | The system shall not process a fee waiver request until fee waiver supporting documentation and attestation that information is truthful is uploaded to the system. External User will be notified of this requirement at the time the fee waiver is requested by way of a text warning that the submission will not proceed until supporting documentation, attestation that the information is truthful, and accepted Terms and Conditions. | Mandatory | |
| 1.1 | Fee Collections | Manual Fee Waiver | FEE-021 | The system shall specify each type of fee waiver available plus “Other” with a text description. | Mandatory | |
| 1.1 | Fee Collections | Manual Fee Waiver | FEE-022 | The system shall send an email notification to a CARB-designated group when a fee waiver request is submitted. | Mandatory | |
| 1.1 | Fee Collections | Manual Fee Waiver | FEE-023 | The system shall allow CARB users to review the fee waiver request with the option to approve or deny the request. | Mandatory | |
| 1.1 | Fee Collections | Manual Fee Waiver | FEE-024 | The system shall allow external users to submit multiple fee waiver requests up to a maximum number defined by CARB staff. | Mandatory | |
| 1.1 | Fee Collections | Manual Fee Waiver | FEE-025 | The system shall allow CARB staff to define the maximum number of fee waiver requests allowed for an external user to submit. | Mandatory | |
| 1.1 | Fee Collections | Manual Fee Waiver | FEE-026 | The system shall track all fee waivers and allow internal users to generate reports on approved and denied waivers. |
o Date/time waiver is submitted, o External user submitting request, o Notification of waiver approval or denial, with a date/time stamp
| o Confirmation that the fee waiver outcome was sent, including date/time stamp | Mandatory | |||||
| 1.1 | Fee Collections | Manual Fee Waiver | FEE-027 | The system shall notify external users of the outcome of the fee waiver request via the correspondence function. | Mandatory | |
| 1.1 | Fee Collections | Fee Dispute Resolution | FEE-028 | The system shall allow users to dispute the Fee amount by initiating Correspondence with internal users. | Mandatory | |
| 1.1 | Fee Collections | Fee Dispute Resolution | FEE-029 | The system shall log all correspondence related to fee disputes, including timestamps, user information, and resolution outcomes. | Mandatory | |
| 1.1 | Fee Collections | Fee Dispute Resolution | FEE-030 | The system shall allow internal users to lock an external user out of the payment process if their payment is under dispute. | Mandatory | |
| 1.1 | Fee Collections | Fee Dispute Resolution | FEE-031 | The system shall allow internal users to unlock an external user after the disputed final invoice amount has been determined. | Mandatory | |
| 1.1 | Fee Collections | Fee Dispute Resolution | FEE-032 | The system shall send Correspondence to internal users when a fee dispute is resolved. | Mandatory | |
| 1.1 | Fee Collections | Fee Submission | FEE-033 | The system must allow fees to be paid within the Submittal Period, and will allow the fee be paid after the invoice is generated as long as the payment occurs within the Submittal Period. | Mandatory | |
| 1.1 | Fee Collections | Fee Submission | FEE-034 | The system will allow ExternalUser to request from InternalUser extension of fee payment period through the correspondence function. | Mandatory | |
| 1.1 | Fee Collections | Fee Submission | FEE-035 | The system will allow internal user to open or extend fee payment functionality for a specific company if approved by InternalUser. | Mandatory | |
| 1.1 | Fee Collections | Fee Submission | FEE-036 | The system shall allow external users to schedule future payment dates as long as the payment is made within the data SubmittalPeriod. | Desirable Scored | |
| 1.1 | Fee Collections | Payment Processing and Tracking | FEE-037 | The system shall integrate with CARB's existing payment portal to allow users to make payments in CARB's calculated fee amount only - no payments in amounts other than those invoiced will be accepted. | Mandatory | |
| 1.1 | Fee Collections | Payment Processing and Tracking | FEE-038 | The system shall provide notification banner with the Fee payment terms such as transaction fees information applied with the Fee payment modes applicable on the Fee Payment location. | Mandatory | |
| 1.1 | Fee Collections | Payment Processing and Tracking | FEE-039 | The system shall be able to receive notification from CARB's payment portal that the fee has been paid. | Mandatory | |
| 1.1 | Fee Collections | Payment Processing and Tracking | FEE-040 | The system shall allow internal users to query the payment status for each company | Mandatory | |
| 1.1 | Fee Collections | Payment Processing and Tracking | FEE-041 | The system shall send confirmation the external user when payment has been received, including transaction details and payment receipt. | Mandatory | |
| 1.1 | Fee Collections | Payment Processing and Tracking | FEE-042 | The system shall track payment status, including pending, completed, and failed payments, and notify external users of status changes. | Mandatory | |
| 1.1 | Fee Collections | Payment Processing and Tracking | FEE-043 | The system shall prevent more than one fee submission for the same reporting period. | Mandatory | |
| 1.1 | Fee Collections | Payment Processing and Tracking | FEE-044 | The system shall notify users if their payment fails and provide instructions for retrying the payment. | Mandatory | |
| 1.1 | Fee Collections | Payment Processing and Tracking | FEE-045 | The system shall allow external users to view their fee status and payment history. | Mandatory | |
| 1.1 | Fee Collections | Reporting | FEE-046 | The system shall allow internal users to generate a report of all outstanding balances and unpaid fees. | Mandatory | |
| 1.1 | Fee Collections | Reporting | FEE-047 | The system shall allow both internal users to query for and external users to generate a report showing their company's payment status. | Mandatory | |
| 1.1 | Fee Collections | Reporting | FEE-048 | Internal users shall have access to external user reports showing payment status. | Mandatory | |
| 1.1 | Fee Collections | Audit Logging | FEE-049 | The system shall maintain an audit log capturing all user actions related to fee disputes, documenting timestamps, user information, and resolution outcomes in the queryable database. | Mandatory | |
| 1.1 | Fee Collections | Audit Logging | FEE-050 | The system shall capture the following historical Fee information and add this information into the queryable database. Fields information is captured after successful Fee Payments (Single and Batch Registration, Updates) |
- History Unique ID
- Payment Due Date
- Payment Received Date
- Payment Valid Through
- Fee Amount
| - Refer to the Data Elements document | Mandatory | ||||
| 1.1 | Fee Collections | Audit Logging | FEE-051 | The system shall provide authorized users with the following user roles to view the Fee historical information: |
- Internal Users (Refer to the user role matrix for specific roles)
| - External Users (Refer to the user role matrix for specific roles) | Mandatory | |||||
| 1.1 | Fee Collections | Audit Logging | FEE-052 | The system shall retain all the historical information for Fee Payments as defined within CARB's data retention policy. | Mandatory | |
| 1.1 | Fee Collections | Fee Calculation | FEE-053 | The system database structural guidance for Fee Calculation proposed by CARB. Refer to the BECRT Data Definitions document for field information. | Mandatory | |
| 1.1 | Fee Collections | Fee Administration | FEE-054 | The system database structural guidance for Fee Administration proposed by CARB. Refer to the BECRT Data Definitions document for field information. | Mandatory | |
| 1.1 | Fee Collections | Waiver | FEE-055 | The system database structural guidance for Waiver proposed by CARB. Refer to the BECRT Data Definitions document for field information. | Mandatory | |
| 1.1 | Fee Collections | Fee Dispute Resolution | FEE-056 | The system database structural guidance for Fee Dispute Resolution proposed by CARB. Refer to the BECRT Data Definitions document for field information. | Mandatory | |
| 1.1 | Fee Collections | Fee Submission | FEE-057 | The system database structural guidance for Fee Submission proposed by CARB. Refer to the BECRT Data Definitions document for field information. | Mandatory | |
| 1.1 | Fee Collections | Payment Processing and Tracking | FEE-058 | The system database structural guidance for Payment Processing and Tracking proposed by CARB. Refer to the BECRT Data Definitions document for field information. | Mandatory | |
| 1.1 | Fee Collections | Reporting | FEE-059 | The system database structural guidance for Fee Calculation proposed by CARB. Refer to the BECRT Data Definitions document for field information. | Mandatory | |
| 1.1 | Fee Collections | Audit Logging | FEE-060 | The system database structural guidance for Fee Calculation proposed by CARB. Refer to the BECRT Data Definitions document for field information. | Mandatory | |
| 1.1 | Data Submission | Validation and Resubmission Workflow | FLW-001 | The system shall provide a validation configuration interface that allows internal users to define which uploaded Excel/CSV or XML formatted reporting fields are required and which are optional, that allows internal users to define the range of normal value for a given field, that assigns internal flags and/or external flags to out-of-range values, and that allows internal users to define a numerical risk score for each internal flag. | Mandatory | |
| 1.1 | Data Submission | Validation and Resubmission Workflow | FLW-002 | The system shall provide an admin interface that allows internal users to configure Regular Expression ("RegEx") field validations for Excel/CSV and XML import validations and configure the error message text that will appear should the RegEx fail. | Mandatory | |
| 1.1 | Data Submission | Validation and Resubmission Workflow | FLW-003 | The system shall automatically validate uploaded reports against the field configuration selected by the internal user per FLW-001 and FLW-002. | Mandatory | |
| 1.1 | Data Submission | Validation and Resubmission Workflow | FLW-004 | When a reporting entity (CompanyAdmins, DataSubmitters, or ThirdParties) uploads a completed reporting template, the system shall display a structured summary view of data fields submitted. This view will present a hierarchy of data fields and will be expandable/collapsable such that the default view only displays fields that have missing required data or fields with external flags. | Desirable Scored |
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .