Attachment_B_-_Functional_Requirements.xlsm

XLSM spreadsheet 418 KB Posted

Attached to
REQUEST FOR INFORMATION (RFI) - 2024CARB_ ACC II-RFI002 - Advanced Clean Cars (ACC) II ZEV Regulation Tracking System
Solicitation number
0000032094
Issued by
Sacramento County, Sacramento City, California

About this file

This document is a Request for Information (RFI) issued by the California Air Resources Board (CARB) for the development of an Advanced Clean Cars (ACC) II ZEV Regulation Tracking System. The purpose of this RFI is to solicit information, suggestions, and best practices on the technical resources available to provide the State with a comprehensive solution for tracking and reporting ZEV compliance across multiple jurisdictions, enhancing data verification processes, and contributing to the success of ACC II in reducing emissions from passenger cars and light-duty trucks.

The RFI does not provide specific details on quantities, response dates, award dates, or contract terms. However, it indicates that the system should be designed to be available 24/7 to provide user access to the system information and complete electronic transactions, while being compliant with Web Content User Interface Guidelines (WCAG) under Section 508 of the Rehabilitation Act of 1973. The RFI also outlines several non-functional security and design requirements for the system, including secure authentication, encryption, and integration with CARB's existing systems and databases.

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

Instructions

STATEWIDE INFORMATION MANAGEMENT MANUAL

SECTION 19B.3 MID-LEVEL SOLUTION REQUIREMENTS TEMPLATE TOOL

PROJECT NUMBER:3900-079AGENCY/STATE ENTITY NAME:California Air Resources Board
The Statewide Information Management Manual (SIMM) 19B.3 Mid-Level Solution Requirements Template tool is provided as a guideline to document functional solution requirements. For functional solution requirements, the fields included in this template are required and must be included in an Agency/state entity's requirement documentation submission. Agencies/state entities may utilize another requirement documentation tool as long as the required fields are included. Additionally, Agencies/state entities may include more fields than those provided in this template.

INSTRUCTIONS:

Identify the Project Number and Agency/State Entity Name:

In the Instructions tab, enter the Project Number and Agency/State Entity Name. This information will automatically populate on each corresponding "Requirement Type" tab.

Enter requirements:

Enter mid-level solution requirements in the corresponding tab based on the "Requirement Type" (i.e., Functional Mandatory, Functional Desirable, Non-Functional Mandatory, Non-Functional Desirable, Project-Transition Mandatory, Project-Transition Desirable). For additional instructions , refer to the SIMM Section 19B.1 Preparation Instructions Section 2.6.

Note: Footer information may be modified based on Agency/state entity preference.

Create a combined worksheet that displays all requirements:

Click on the "Create Combined Worksheet" button to combine all the requirements from the separate "Requirement Type" tabs (i.e., Functional Mandatory, Functional Desirable, Non-Functional Mandatory, Non-Functional Desirable, Project-Transition Mandatory, Project-Transition Desirable) onto one worksheet. Do not re-select the "Create Combined Worksheet" button if a "Combined" tab already exists, as the automatic combine macro will not function correctly. To ensure proper functionality, first delete the existing "Combined" tab and then select the "Create Combined Worksheet" button to update the combined listing of requirements.

Format the "Combined" tab:

Click on the File Menu tab, select Print. In the Print Menu, use the appropriate drop down arrows to change the "Portrait Orientation" to "Landscape Orientation" and change the "No Scaling" to "Fit All Columns on One Page."

Set Print Area:

Prior to printing from a tab/worksheet, set the Print Area.

To do this, Select the entire area to be printed. Once selected, click the Page Layout Menu tab, then select Set Print Area.

Attach requirements:

Once completed and ready to submit, attach the completed requirements documentation as indicated in Section 2.6.

REQUIREMENT TYPE TAB
Combined requirements = Combined tab (viewable only if the "Create Combined Worksheet" button is used.)
Functional Mandatory tab
Functional Desirable tab
Non-Functional Mandatory tab
Non-Functional Desirable tab
Project/Transition Mandatory tab
Project/Transition Desirable tab

California Department of Technology SIMM Section 19 Mid-Level Solution Requirements B.3 Mid-Level Solution Requirements Template &P

August 2016

Create Combined Worksheet

Combined

Project Number:3900-079Agency/state Entity:California Air Resources Board
Obj. Ref.
(Obj. #)Requirement CategoryRequirement NumberMain Business Capability/FunctionSub Business Capability/FunctionBusiness ProcessRequirementRequirement TypePriorityBusiness Owner/ Stakeholder
1.1, 1.7FMSA-01System AdministrationSystem SecurityUser AccessThe System shall include a single log-on attribute to communicate forgotten user ID or password.FunctionalMandatoryAnna Wong
1.1, 1.7FMSA-02System AdministrationSystem SecurityUser AccountThe System shall display notice when an unsuccessful sign-on attempt occurs and display the number of attempts remaining.FunctionalMandatoryAnna Wong
1.1, 1.7FMSA-03System AdministrationSystem SecurityUser AccountThe System shall lock-out a user after a configurable number of unsuccessful sign-on attempts and display a configurable notice when lock-out occurs.FunctionalMandatoryAnna Wong
1.1, 1.7FMSA-04System AdministrationSystem SecurityUser AccountThe System shall provide a secure process (example: multi-factor User Management (MFA)) that allows a locked-out user to obtain a forgotten user ID, forgotten password, and to reestablish a password.FunctionalMandatoryAnna Wong
1.1, 1.7FMSA-05System AdministrationSystem SecurityUser AccountThe System shall provide a secure process that allows a user to obtain a forgotten user ID, forgotten password, and to reestablish a password.FunctionalMandatoryAnna Wong
1.1, 1.7FMSA-06System AdministrationSystem SecurityUser AccountThe System shall logout a user when the user leaves the site or closes the browser or is inactive for a configurable amount.FunctionalMandatoryAnna Wong
1.4, 1.5, 1.7FMSA-07System AdministrationZEV AdministrationRoles and PermissionsThe System shall provide the Program or State Administrator notification at login of items requiring attention. This will be grouped by like items and sortable by date, manufacturer, type of transaction, etc.FunctionalMandatoryAnna Wong
1.4, 1.5, 1.7FMSA-08System AdministrationZEV AdministrationRoles and PermissionsThe System shall provide the Program Administrator the ability to display important deadlines (e.g., submitting Annual ZEV Requirement performance for the model year prior to May 1st) and reminders on the login screen.FunctionalMandatoryAnna Wong
1.1, 1.7FMSA-09System AdministrationGeneralAudit/LogThe System shall provide a log of all transactions capturing the following, but not limited to, previous value, updated value, date changed, and account user who made the update.FunctionalMandatoryAnna Wong
1.1, 1.4, 1.7FMSA-10System AdministrationReporting Sales DataNotificationsThe System shall notify the Program or State Administrator when changes to NMOG+NOx production data of passenger cars and light-duty trucks for current and previous model years have been submitted for approval.FunctionalMandatoryAnna Wong
1.1, 1.4, 1.7FMSA-11System AdministrationReporting Sales DataApprovalsThe System shall allow Program or State Administrator to approve or reject sales data submitted by manufacturer for current and previous model years.FunctionalMandatoryAnna Wong
1.1, 1.3, 1.4, 1.7FMSA-12System AdministrationReporting Sales DataData ValidationThe System shall automatically verify if the NMOG+NOx production data match with a spreadsheet uploaded by the Program or State Administrator to verify sales data.FunctionalMandatoryAnna Wong
1.1, 1.3, 1.4, 1.7FMSA-13System AdministrationReporting Sales DataNotificationsThe System shall send message to the manufacturer when NMOG+NOx production data does not match the uploaded spreadsheet or when NMOG+NOx production data has not been provided.FunctionalMandatoryAnna Wong
1.1, 1.3, 1.7FMSA-14System AdministrationReporting Value DataData Import/ExportThe System shall allow the Program Administrator to load and modify the data from ECCD.FunctionalMandatoryAnna Wong
1.1, 1.3, 1.4, 1.7FMSA-15System AdministrationReporting Value DataData ValidationThe System shall validate whether a manufacturer has data from ECCD in the System.FunctionalMandatoryAnna Wong
1.1, 1.2, 1.7FMSA-16System AdministrationReporting Value DataApprovalsThe System shall allow the Program or State Administrator to approve, reject, or request revision for the VINs reported.FunctionalMandatoryAnna Wong
1.1, 1.7FMSA-17System AdministrationSystem AccessRoles and PermissionsThe System shall provide the Program Administrator the ability to make designated data read-only to all users except for the Program Administrator. The time and date shall be configurable.FunctionalMandatoryAnna Wong
1.1, 1.7FMSA-18System AdministrationSystem MessagesUser AccountThe System shall send an email message to the Program Administrator when a new user account application is submitted.FunctionalMandatoryAnna Wong
1.1, 1.7FMSA-19System AdministrationSystem AccessRoles and PermissionsThe System shall require two manufacturer representatives before allowing them to enter or modify any ZEV information.FunctionalMandatoryAnna Wong
1.1, 1.7FMSA-20System AdministrationSystem MessagesUser AccountThe System shall allow Program Administrator to automatically send an email message of approval with username, password, account ID information or rejection.FunctionalMandatoryAnna Wong
1.1, 1.4, 1.7FMSA-21System AdministrationSystem MessagesUser AccountThe System shall remind manufacturers quarterly via email and the system interface to review and update their primary, secondary, executive, and read-only users.FunctionalMandatoryAnna Wong
1.4, 1.5FMSA-22System AdministrationSystem SecurityUser AccountThe System shall require a configurable number of CARB approved security questions to authenticate users when a user ID or password is forgotten.FunctionalMandatoryAnna Wong
1.1, 1.4, 1.5, 1.7FMUI-01User InterfaceSystem AccessUser AccessThe System shall provide a single, seamless web user interface for participant registration, ZEV account management, reporting and administration.FunctionalMandatoryAnna Wong
1.4, 1.5FMUI-02User InterfaceSystem AccessUser AccountThe System shall provide users the ability to update their password.FunctionalMandatoryAnna Wong
1.1FMUI-03User InterfaceSystem AccessNavigationThe System shall provide Graphic User Interface point and click and pull-down menu access to various pages and content.FunctionalMandatoryAnna Wong
1.1, 1.7FMUI-04User InterfaceSystem AccessNavigationThe System shall provide links to all CARB designated Internet web sites such as, but not limited to, "Advanced Clean Cars II” and “New Vehicle and Engine Certification: Executive Orders for Light-Duty Vehicles”.FunctionalMandatoryAnna Wong
1.4, 1.5FMUI-05User InterfaceSystem AccessRoles and PermissionsThe System shall provide users with read-only access to historical data.FunctionalMandatoryAnna Wong
1.1, 1.7FMUI-06User InterfaceSystem AdministrationHelp FunctionalityThe System shall provide help functionality on each displayed page as determined by CARB.FunctionalMandatoryAnna Wong
1.1, 1.7FMUI-07User InterfaceSystem AdministrationSearch FunctionalityThe System shall provide a search function based on defined roles, to search data element fields to find specific data, with search parameters based on CARB defined business rules (e.g., searching for a specific company name or reported vehicle, and selecting all records within a specific program type).FunctionalMandatoryAnna Wong
1.4, 1.5FMUI-08User InterfaceGeneralUser AccessThe System shall be designed to allow manufacturers and Program Administrators to switch between different states efficiently.FunctionalMandatoryAnna Wong
1.1, 1.7FMUI-09User InterfaceGeneralData HandlingThe System shall provide the ability to record text comments for transactions.FunctionalMandatoryAnna Wong
1.1, 1.7FMUI-10User InterfaceGeneralData HandlingThe System shall provide the user with the ability to save information in the middle of a transaction and restart, without loss of transaction data, at a later date and time.FunctionalMandatoryAnna Wong
1.1, 1.7FMUI-11User InterfaceGeneralError HandlingThe System shall provide meaningful error messages if a transaction cannot be completed.FunctionalMandatoryAnna Wong
1.1, 1.7FMUI-12User InterfaceGeneralNavigationThe System shall display a warning to the user if any current displayed information will be lost or deleted upon navigation to another form or screen.FunctionalMandatoryAnna Wong
1.1, 1.7FMUI-13User InterfaceGeneralNotificationsThe System shall generate real-time user notifications (e.g., registration submitted, incomplete registration information, manufacturer VIN submittals complete for each state) for the Program Administrators and all the State Administrators.FunctionalMandatoryAnna Wong
1.1, 1.7FMUI-14User InterfaceZEV AdministrationRoles and PermissionsThe System shall allow Program Administrator to define user notifications (e.g., end of year notification, all manufacturer submissions have been received, forecasts, designation of compliance flexibilities).FunctionalMandatoryAnna Wong
1.6FMUI-15User InterfaceZEV AdministrationRoles and PermissionsThe System shall allow Program Administrator to manually edit any data due to rounding errors or other possible issues in the backend through use of a consistent programming language and/or Open Database Connectivity (ODBC).FunctionalMandatoryAnna Wong
1.1, 1.4, 1.5, 1.7FMUI-16User InterfaceGeneralUser AccountThe System shall support use of an User Management check box to agree to terms of use (e.g., a user confirms entered data is complete and correct upon submittal).FunctionalMandatoryAnna Wong
1.1, 1.7FMUI-17User InterfaceGeneralUser AccountThe System shall require all user profile data to be entered and maintained by user.FunctionalMandatoryAnna Wong
1.4, 1.5, 1.7FMUI-18User InterfaceZEV AdministrationRoles and PermissionsThe system shall provide the Program Administrator the capability to enter, store, and edit required data.FunctionalMandatoryAnna Wong
1.4, 1.5, 1.7FMUI-19User InterfaceZEV AdministrationRoles and PermissionsThe System shall provide the Program Administrator the capability to enter, store, and edit NMOG+NOx production data for the current and past model years.FunctionalMandatoryAnna Wong
1.4, 1.5, 1.7FMUI-20User InterfaceZEV AdministrationRoles and PermissionsThe System shall provide the Program Administrator the capability to enter, store, and edit volume status of the manufacturers.FunctionalMandatoryAnna Wong
1.4, 1.5, 1.7FMUI-21User InterfaceZEV AdministrationRoles and PermissionsThe System shall provide the Program Administrator the capability to enter, store, and edit vehicle values for the current and past model years.FunctionalMandatoryAnna Wong
1.1, 1.7FMUI-22User InterfaceReportsGeneralThe System shall generate reports by model year for each manufacturer.FunctionalMandatoryAnna Wong
1.1, 1.7FMUI-23User InterfaceReportsGeneralThe System shall provide capability to view and print account balances on demand.FunctionalMandatoryAnna Wong
1.1, 1.7FMUI-24User InterfaceReportsAccount Balance ManagementThe System shall produce a summary compliance report of all account holders’ balances (by values and vehicles) by model year, requirement if appropriate, and indication of compliance.FunctionalMandatoryAnna Wong
1.1, 1.7FMUI-25User InterfaceReportsGeneralThe System shall produce a report with the number of vehicles and number of values by vehicle type and model year with a total.FunctionalMandatoryAnna Wong
1.1, 1.7FMUI-26User InterfaceReportsTransfersThe System shall produce a summary transfer report with transferor, transferee, vehicle type, and number of values.FunctionalMandatoryAnna Wong
1.1, 1.7FMUI-27User InterfaceReportsAccount Balance ManagementThe System shall provide a public summary report of active manufacturer value balances by vehicle type at the conclusion of each reporting year.FunctionalMandatoryAnna Wong
1.1, 1.7FMUI-28User InterfaceReportsAd Hoc ReportsThe System shall allow to Program and State Administrator to generate special reports on key fields (i.e., customized reports based on existing data variables such as various value types, state, production volume).FunctionalMandatoryAnna Wong
1.1, 1.7FMUI-29User InterfaceReportsGeneralThe System shall generate a report that summarizes all executive orders, test group number, technology type, make, model, model year, and number of values.FunctionalMandatoryAnna Wong
1.1, 1.7FMUI-30User InterfaceReportsGeneralThe system shall generate a report which displays all manufacturer submittals (i.e., makes, models, number of values).FunctionalMandatoryAnna Wong
1.1, 1.7FMUI-31User InterfaceTransfersApprovalsThe System shall allow the Transferor submit a Transfer request, have the Transferee accept it, and then require the Program or State Administrator to approve the transfer.FunctionalMandatoryAnna Wong
1.1, 1.7FMUI-32User InterfaceTransfersEarly Compliance Values Validation ProcessThe System shall not allow Early Compliance Vehicle Values to be transferred.FunctionalMandatoryAnna Wong
1.1, 1.4, 1.7FMUI-33User InterfaceTransfersTransfers Between ManufacturersThe System shall allow manufacturers to initiate a transfer.FunctionalMandatoryAnna Wong
1.1, 1.4, 1.7FMUI-34User InterfaceTransfersTransfers Between ManufacturersThe System shall allow manufacturers to modify and validate transfer information until it is submitted to receiving party.FunctionalMandatoryAnna Wong
1.1, 1.4, 1.7FMUI-35User InterfaceTransfersTransfers Between ManufacturersThe System shall allow a manufacturer to initiate a transfer of its own values between states (i.e., an intra-company transfer).FunctionalMandatoryAnna Wong
1.1, 1.7FMUI-36User InterfaceTransfersApprovalsThe System shall allow the Transferee to reject or approve transfer request.FunctionalMandatoryAnna Wong
1.1, 1.7FMUI-37User InterfaceTransfersApprovalsThe System shall allow Program or State Administrator to approve or reject transfers.FunctionalMandatoryAnna Wong
1.1, 1.7FMUI-38User InterfaceTransfersApprovalsThe System shall display the date the transfer request is approved or rejected.FunctionalMandatoryAnna Wong
1.1, 1.4, 1.7FMUI-39User InterfaceTransfersApprovalsThe System shall allow impacted Program or State Administrator to approve or reject an intercompany transfer.FunctionalMandatoryAnna Wong
1.1, 1.5, 1.7FMUI-40User InterfaceTransfersGeneralThe System shall impose the following rules regarding transfers between states:

• EJ Values cannot be transferred to another S177 state.

• Pooled ZEV and PHEV Values transfer rules are outlined in ABM-51 to ABM-54.FunctionalMandatoryAnna Wong
1.1, 1.4, 1.7FMUI-41User InterfaceTransfersGeneralPooled values cannot be traded with other manufacturers once pooled values are approved by the Program or State Administrator.FunctionalMandatoryAnna Wong
1.1, 1.7FMUI-42User InterfaceZEV AdministrationTransfersThe System shall allow Program Administrator to place holds on any account to prohibit transfers.FunctionalMandatoryAnna Wong
1.1, 1.4, 1.7FMUI-43User InterfaceGeneralData HandlingThe System shall allow manufacturers to report annual data online.FunctionalMandatoryAnna Wong
1.1, 1.4, 1.7FMUI-44User InterfaceGeneralData HandlingThe System shall allow manufacturers to save their progress on reporting and requests.FunctionalMandatoryAnna Wong
1.1, 1.4, 1.7FMUI-45User InterfaceGeneralData HandlingThe System shall allow manufacturers to remove saved reporting and requests.FunctionalMandatoryAnna Wong
1.1, 1.4, 1.7FMUI-46User InterfaceReporting Sales DataData HandlingThe System shall allow manufacturers to enter total NMOG+NOx production data of passenger cars and light-duty trucks for the current reporting year.FunctionalMandatoryAnna Wong
1.1, 1.4, 1.7FMUI-47User InterfaceReporting Sales DataApprovalsThe System shall allow manufacturers to submit changes to NMOG+NOx production data for current and previous model years of passenger cars and light-duty trucks requiring input in a comment box that justifies the changes.FunctionalMandatoryAnna Wong
1.1, 1.2, 1.4, 1.7FMUI-48User InterfaceReporting Value DataData Import/ExportThe System shall provide an excel template (.xlsx or .csv) that manufacturers can download and use to report VINs.FunctionalMandatoryAnna Wong
1.1, 1.2, 1.4, 1.7FMUI-49User InterfaceReporting Value DataData Import/ExportThe System shall allow manufacturers to report VINs from all states by uploading one spreadsheet.FunctionalMandatoryAnna Wong
1.1, 1.4, 1.7FMUI-50User InterfaceReporting Value DataApprovalsThe System shall allow manufacturers to submit revisions and justification in a comment box for their reporting. The Program or State Administrator will be notified and approve/reject the revision.FunctionalMandatoryAnna Wong
1.1, 1.7FMUI-51User InterfaceReporting Value DataError HandlingThe System shall allow the Program Administrator to reverse approved reporting and revert the value balances to the pre-approval timeframe.FunctionalMandatoryAnna Wong
1.1, 1.2, 1.7FMUI-52User InterfaceReporting Value DataSearch FunctionalityThe System shall allow the Program or State Administrator to search and select VINs using the following parameters: match, no match, approved, revision requested. The Program or State Administrator shall also be able to download the results selected in a .csv format. Additional search parameters may be added later.FunctionalMandatoryAnna Wong
1.1, 1.7FMUI-53User InterfaceReporting ComplianceComplianceThe System shall display to the Program or State Administrator upon login a list of manufacturers that have not submitted their Annual ZEV Requirement.FunctionalMandatoryAnna Wong
1.1, 1.4, 1.7FMUI-54User InterfaceGeneralData HandlingThe System shall allow manufacturers to search and download their data on demand.FunctionalMandatoryAnna Wong
1.1, 1.4, 1.7FMUI-55User InterfaceSystem AccessUser AccountThe System shall allow manufacturers and parties representing manufacturers (not brokers) to register for and manage a ZEV account online.FunctionalMandatoryAnna Wong
1.1, 1.4, 1.5, 1.7FMUI-56User InterfaceSystem AccessUser AccountThe System shall provide the capability for users to apply for a ZEV account through a webform that details what information is required.FunctionalMandatoryAnna Wong
1.1, 1.7FMUI-57User InterfaceGeneralUser AccountThe System shall allow registered users to update profile information.FunctionalMandatoryAnna Wong
1.1, 1.4, 1.5, 1.7FMUI-58User InterfaceGeneralUser AccountThe System shall allow registered users to report periodic and annual data online.FunctionalMandatoryAnna Wong
1.4, 1.5FMUM-01User MaintenanceZEV AdministrationUser AccountThe System shall provide the Program Administrator the ability to add, modify, or remove application users (company users (herinafter referred to as manufacturers), state administrators, and program administrators) and corresponding information (name, email, phone number).FunctionalMandatoryAnna Wong
1.4, 1.5FMUM-02User MaintenanceZEV AdministrationRoles and PermissionsThe System shall provide the Program Administrator with the ability to dynamically define, assign and maintain roles and permissions for all roles.FunctionalMandatoryAnna Wong
1.4, 1.5FMUM-03User MaintenanceZEV AdministrationRoles and PermissionsThe System must provide the ability to add multiple State Administrators based on the State being represented.FunctionalMandatoryAnna Wong
1.4, 1.5FMUM-04User MaintenanceSystem AccessRoles and PermissionsThe System shall have the ability to maintain secured role-based user authorization levels and restrict access at the report, file, table, screen, and field level based on user authorization.FunctionalMandatoryAnna Wong
1.1, 1.7FMUM-05User MaintenanceZEV AdministrationRoles and PermissionsThe System shall provide the ability for Program Administrator, with appropriate security permissions, to add and edit registration and company records that were submitted through electronic copies.FunctionalMandatoryAnna Wong
1.1, 1.7FMUM-06User MaintenanceZEV AdministrationUser AccountThe system shall allow Program Administrators to reset the password of any manufacturer.FunctionalMandatoryAnna Wong
1.4, 1.5, 1.7FMUM-07User MaintenanceZEV AdministrationRoles and PermissionsThe System shall provide the Program Administrator with the capability to deactivate a user's account.FunctionalMandatoryAnna Wong
1.1, 1.7FMUM-08User MaintenanceZEV AdministrationUser AccountThe System shall allow the Program Administrator to approve or reject new user accounts.FunctionalMandatoryAnna Wong
1.1, 1.7FMCL-01Calculation LogicAccount Balance ManagementGeneralThe System shall have separate accounts for different values: ZEV, PHEV, converted ZEV, converted PHEV, Environmental Justice (EJ), early compliance ZEV and PHEV, and proportional FCEV.FunctionalMandatoryAnna Wong
1.1, 1.7FMCL-02Calculation LogicAccount Balance ManagementGeneralThe System shall provide the Program Administrator flexibility to add or remove account types as needed.FunctionalMandatoryAnna Wong
1.1, 1.7FMCL-03Calculation LogicAccount Balance ManagementNotificationsThe System shall send email message to Program and State administrator when new or updated information is submitted.FunctionalMandatoryAnna Wong
1.1, 1.7FMCL-04Calculation LogicAccount Balance ManagementCalculating Annual ZEV RequirementThe System shall calculate and display for each regulated manufacturer the annual ZEV requirements expressed in whole vehicles, using the following formula:

Annual ZEV Requirement = Annual Percentage Requirement x Production Volume Where:

Annual ZEV Requirement = manufacturer's ZEV production required, expressed in whole vehicles, for the applicable model year

Annual Percentage Requirement = the annual percentage requirement as seen in the table below:

Model Year Percentage Requirement 2026 35% 2027 43% 2028 51% 2029 59% 2030 68% 2031 76% 2032 82% 2033 88% 2034 94% 2035 and subsequent 100%

FunctionalMandatoryAnna Wong
1.1, 1.7FMCL-05Calculation LogicAccount Balance ManagementCalculating Annual ZEV RequirementThe System shall allow the manufacturer to input the total number of passenger cars and light-duty trucks produced and delivered for sale in California and the S177 States and any medium-duty ZEVs produced and delivered for sale in California and the S177 States for which the manufacturer optionally chooses to certify to this section.FunctionalMandatoryAnna Wong
1.1, 1.7FMCL-06Calculation LogicAccount Balance ManagementCalculating Annual ZEV RequirementThe System shall calculate and display from each regulated manufacturer the Production Volume, which is calculated via one of two methods described below, based on the total number of passenger cars and light-duty trucks produced and delivered for sale in California or a given S177 State and any medium-duty ZEVs produced and delivered for sale in California or a given S177 State for which the manufacturer optionally chooses to certify to this section.

The System will allow for these two methods for calculating the Production Volume:

1) Previous year average method to determine production volume through 2034 model year.

The production volume used to calculate a manufacturer's Annual ZEV Requirement for the 2026 through 2034 model years is the three-year average of the manufacturer's volume of passenger cars and light-duty trucks, produced and delivered for sale in California or a given S177 State, in the prior second, third, and fourth model years (e.g., 2026 model year Annual ZEV Requirements are calculated using the California or given S177 State production volume average of passenger cars and light-duty trucks for the 2022 through 2024 model years).

2) Same year method to determine production volume.

In lieu of the three-year average in above, a manufacturer may elect in any model year from 2026 through 2034 to use the same model year to determine its production volume and Annual ZEV Requirements (e.g., 2026 model year Annual ZEV Requirements are calculated using the California or given S177 State production volume of 2026 model year passenger cars and light-duty trucks). However, once a manufacturer elects to use the same year method under this subsection for a model year, it must continue to use this same year method for all subsequent model years and may not use the previous year average method. Additionally, for 2035 and subsequent model years, the production volume for all manufacturers will be determined according to the same year method of this subsection.FunctionalMandatoryAnna Wong
1.1, 1.7FMCL-07Calculation LogicAccount Balance ManagementCalculating Annual ZEV RequirementThe System shall display whether a manufacturer is using the previous year average method or the same year method calculation through 2034 model year.FunctionalMandatoryAnna Wong
1.1, 1.7FMCL-08Calculation LogicAccount Balance ManagementCalculating Annual ZEV RequirementThrough 2034 model year, the System shall allow the manufacturer to download a template to fill out if they elect to use the same year method and allow the manufacturer to reupload it to the System. The Program or State administrator will be notified when the manufacturer uploads it into the System and be able to download this information to verify the manufacturer meets the same year method requirement.FunctionalMandatoryAnna Wong
1.1, 1.7FMCL-09Calculation LogicAccount Balance ManagementCalculating Annual ZEV RequirementThe System shall allow the program and state administrator to select whether a manufacturer elects to use the same model year calculation through 2034 model year.FunctionalMandatoryAnna Wong
1.1, 1.7FMCL-10Calculation LogicAccount Balance ManagementCalculating Annual ZEV RequirementThe System shall allow for small volume manufacturer (meaning those manufacturers with less than 4,500 vehicles delivered in each state) to begin compliance with the Annual ZEV Requirement in model year 2035.FunctionalMandatoryAnna Wong
1.1, 1.7FMCL-11Calculation LogicAccount Balance ManagementCalculating Annual ZEV RequirementThe System shall notify the small volume manufacturer on December 31, 2031 and June 1, 2032 and require the manufacturer to upload compliance plan documents required no later than December 31, 2032, or if a manufacturer becomes a small volume manufacturer after January 1, 2032, within one year of becoming a small volume manufacturer, to show its plan for complying with the 2035 model year Annual ZEV Requirement.FunctionalMandatoryAnna Wong
1.1, 1.7FMCL-12Calculation LogicAccount Balance ManagementCalculating Annual ZEV RequirementThe System shall notify all State Administrators on December 31, 2031 and June 1, 2032 the requirement for the small manufacturer to upload compliance plan documents required no later than December 31, 2032, or if a manufacturer becomes a small volume manufacturer after January 1, 2032, within one year of becoming a small volume manufacturer, to show its plan for complying with the 2035 model year Annual ZEV Requirement.FunctionalMandatoryAnna Wong
1.1, 1.7FMCL-13Calculation LogicAccount Balance ManagementCalculating Annual ZEV RequirementThe System will display the requirements for the compliance plan, which must include the expected number of vehicle test groups, expected vehicle classes and models, expected powertrain, expected certification range value by model, and expected 2035 model year vehicle sales volumes.FunctionalMandatoryAnna Wong
1.1, 1.7FMCL-14Calculation LogicAccount Balance ManagementCalculating Annual ZEV RequirementThe System shall allow the program and state administrator to add and update percentage requirements listed in ABM-4 to accommodate the increase or decrease of manufacturer production volume which would trigger or remove ZEV requirements in a given model year.FunctionalMandatoryAnna Wong
1.1, 1.7FMCL-15Calculation LogicAccount Balance ManagementCalculating Annual ZEV PerformanceThe System shall calculate manufacturer annual ZEV performance for each model year, using the following formula:
Vehicle Values for ZEVs delivered for sale + Vehicle Values for PHEVs delivered for sale (limited by the allowance for a model year) + EJ Values (limited by the allowance for a model year) + Early Compliance Values (limited by the allowance for a model year) = Annual ZEV PerformanceFunctionalMandatoryAnna Wong
1.1, 1.7FMCL-16Calculation LogicAccount Balance ManagementCalculating Annual ZEV PerformanceThe System shall generate a vehicle value of (one), through the ZEV/PHEV Value Validation Process outlined in ABM-67 through ABM-76.FunctionalMandatoryAnna Wong
1.1, 1.7FMCL-17Calculation LogicAccount Balance ManagementPHEV ValuesThe System shall generate a partial vehicle value for each applicable 2026 through 2028 MY PHEV according to the following equation, rounded to two significant digits and capped at 0.85 (minimum certification range value of less than 70 miles and greater than or equal to 43 miles):

An additional 0.15 partial vehicle value credit if the PHEV has a US06 all‑electric range of at least 10 miles.

The maximum total partial vehicle value plus additional credit may not exceed 1.00.

FunctionalMandatoryAnna Wong
1.1, 1.7FMCL-18Calculation LogicAccount Balance ManagementPHEV ValuesThe System shall calculate an annual PHEV allowance by multiplying 20 percent times the applicable model year Annual ZEV Requirement. The System shall allow PHEV values generated in excess of this allowance to be banked and used according to section 1962.4(f)(3) for 3 additional model years. For example, a PHEV value earned in 2026 MY can be banked and used toward meeting a manufacturer’s shortfall in 2027, 2028, and 2029 MY.FunctionalMandatoryAnna Wong
1.1, 1.7FMCL-19Calculation LogicAccount Balance ManagementEJ ValuesThe System shall prompt a manufacturer to indicate the type of EJ Vehicle Values earned, by model year (Community-based Clean Mobility Programs and its corresponding name, End of Lease Program, or below MSRP threshold ).FunctionalMandatoryAnna Wong
1.1, 1.7FMCL-20Calculation LogicAccount Balance ManagementEJ ValuesThe System shall allow the manufacturer to input the number of ZEVs and PHEVs produced in accordance with the applicable elected provision.FunctionalMandatoryAnna Wong
1.1, 1.7FMCL-21Calculation LogicAccount Balance ManagementEJ ValuesThe System shall allow the program and state administrator to verify EJ Values earned by category (Community-based Clean Mobility Programs, End of Lease Program, or below MSRP threshold).FunctionalMandatoryAnna Wong
1.1, 1.7FMCL-22Calculation LogicAccount Balance ManagementEJ ValuesThe System shall input an additional 0.50 vehicle value for new ZEVs and an additional 0.40 vehicle value for new PHEVs 2024 through 2031 New MY ZEVs and PHEVs for manufacturers that elect to participate in the Community-based Clean Mobility Programs.FunctionalMandatoryAnna Wong
1.1, 1.7FMCL-23Calculation LogicAccount Balance ManagementEJ ValuesThe System shall input additional vehicle values for manufacturers that elect to participate sell ZEVs or PHEVs at End of Lease:

• 2026 through 2031 End of Lease MY ZEVs and PHEVs, an additional 0.10 vehicle value for ZEV or PHEV initially leased new and sold at end of lease in 2026 through 2031 calendar year to a dealership participating in a financial assistance program.

• 2026 through 2031 MY ZEVs or PHEVs, an additional 0.15 vehicle value for ZEV or PHEV sold to a participating dealership is then sold to a financial assistance program participant in 2026 through 2031 calendar year for a maximum total of 0.25 additional vehicle values.

FunctionalMandatoryAnna Wong
1.1, 1.7FMCL-24Calculation LogicAccount Balance ManagementEJ ValuesThe System shall input an additional vehicle 0.10 value for each 2026 through 2028 model year ZEV or PHEV delivered for with an MSRP less than or equal to $20,275 for passenger cars and less than or equal to $26,670 for light-duty trucks.FunctionalMandatoryAnna Wong
1.1, 1.7FMCL-25Calculation LogicAccount Balance ManagementEJ ValuesThe System shall calculate an annual EJ Value Allowance by multiplying 5 percent times the applicable model year Annual ZEV Requirement. The System shall allow EJ values generated in excess of this allowance to be banked and used according to section 1962.4(f)(3) through 2031 MY.FunctionalMandatoryAnna Wong
1.1, 1.7FMCL-26Calculation LogicAccount Balance ManagementEarly Compliance ValuesThe System shall allow the Program or State Administrator to upload spreadsheets containing Early Compliance Values and shall retain these Values for each manufacturer through 2028 MY.FunctionalMandatoryAnna Wong
1.1, 1.7FMCL-27Calculation LogicAccount Balance ManagementEarly Compliance ValuesThe System shall calculate an allowance for Early Compliance Values that a manufacturer may apply for 2026 through 2028 MY by multiplying 15 percent times the applicable model year Annual ZEV Requirement.FunctionalMandatoryAnna Wong
1.1, 1.7FMCL-28Calculation LogicAccount Balance ManagementDetermining Surplus or ShortfallThe System shall calculate and display the number of surplus or shortfall vehicle values it has generated according to the following equation rounded to the nearest whole vehicle value:

Surplus or Shortfall = ZEV Requirement Performance-Annual ZEV Requirement Where:

Surplus or Shortfall = manufacturer's calculated surplus or shortfall, rounded to the nearest whole vehicle value, where a positive number results in surplus values and a negative number results in a shortfall of values;

• ZEV requirement performance = manufacturer's calculated performance per ABM-14

• Annual ZEV Requirement = manufacturer's calculated requirement per ABM-4

FunctionalMandatoryAnna Wong
1.1, 1.7FMCL-29Calculation LogicAccount Balance ManagementSurplusThe System shall display the banked and carried over excess ZEV, PHEV, and EJ vehicle values for use in future model years in which a manufacturer has a shortfall or used to offset a deficit carried over from a previous model year.FunctionalMandatoryAnna Wong
1.1, 1.7FMCL-30Calculation LogicAccount Balance ManagementSurplusThe System shall allow manufacturers to retain excess ZEV and PHEV values for an additional four model years after the model year in which they were earned. For example, 2026 model year ZEV and PHEV values can be used to meet a manufacturer's shortfall through 2030 model year but may not be used in the 2031 model year.FunctionalMandatoryAnna Wong
1.1, 1.7FMCL-31Calculation LogicAccount Balance ManagementSurplusThe System shall allow manufacturers to retain excess environmental justice vehicle values through the 2031 model year. Environmental justice vehicle values may not be used to demonstrate compliance in 2032 model year or any subsequent model year.FunctionalMandatoryAnna Wong
1.1, 1.7FMCL-32Calculation LogicAccount Balance ManagementSurplusThe System shall allow manufacturers to retain unused early compliance vehicle values through the first three model years of a manufacturer’s Annual ZEV Requirements. Early compliance vehicle values may not be used to demonstrate compliance in the fourth model year of the Annual ZEV Requirements of this section or any subsequent model year.FunctionalMandatoryAnna Wong
1.1, 1.7FMCL-33Calculation LogicAccount Balance ManagementFulfilling ShortfallFor 2026 through 2031 model years, the System will limit manufacturers to utilize excess EJ values to fulfill a shortfall up to any remaining EJ value allowance, calculated per ABM-25.FunctionalMandatoryAnna Wong
1.1, 1.7FMCL-34Calculation LogicAccount Balance ManagementFulfilling ShortfallFor the first three model years of the Annual ZEV Requirements, the System will limit manufacturers to utilize excess early compliance vehicle values up to any remaining early compliance vehicle value allowance, calculated per ABM-27.FunctionalMandatoryAnna Wong
1.1, 1.7FMCL-35Calculation LogicAccount Balance ManagementFulfilling ShortfallFor 2026 through 2030 model years, the System will limit manufacturers to utilize converted ZEV and PHEV values, combined, up to the converted ZEV and PHEV allowance, calculated per ABM-39.FunctionalMandatoryAnna Wong
1.1, 1.7FMCL-36Calculation LogicAccount Balance ManagementFulfilling ShortfallThe System will ensure the sum of excess PHEV values, converted PHEV values, pooled PHEV values, early compliance PHEV values, and PHEV values counted towards a manufacturer's performance for the model year may not exceed the PHEV allowance, calculated per ABM-18.FunctionalMandatoryAnna Wong
1.1, 1.7FMCL-37Calculation LogicAccount Balance ManagementFulfilling ShortfallFor 2026 through 2030 model years, the System will limit manufacturers to utilize proportional FCEV values up to the annual proportional FCEV allowance, calculated per ABM-55.FunctionalMandatoryAnna Wong
1.1, 1.7FMCL-38Calculation LogicAccount Balance ManagementConverted ZEV and PHEV ValuesPHEV and ZEV credit account balances earned according to CCR, title 13, section 1962.2, will undergo a one-time conversion:
The System shall calculate the Converted ZEV and PHEV values based on the archival data from ZEV CRDTS. Converted ZEV and PHEV values will be rounded to the nearest whole number in units of vehicle values.FunctionalMandatoryAnna Wong
1.1, 1.7FMCL-39Calculation LogicAccount Balance ManagementConverted ZEV and PHEV ValuesAs a default setting, the System will calculate and apply a Converted ZEV and PHEV Annual Allowance for each manufacturer for model years 2026 through 2030 by multiplying 15 percent times the applicable model year Annual ZEV Requirement.FunctionalMandatoryAnna Wong
1.1, 1.7FMCL-40Calculation LogicAccount Balance ManagementConverted ZEV and PHEV ValuesThe System shall allow a manufacturer to elect to use cumulative allowance, in lieu of the annual allowance per ABM-39. The System will prohibit a manufacturer from using the annual allowance option for all model years prior to and including 2030.FunctionalMandatoryAnna Wong
1.1, 1.7FMCL-41Calculation LogicAccount Balance ManagementConverted ZEV and PHEV ValuesFor manufacturer electing the cumulative allowance, the System will calculate and apply a Converted ZEV and PHEV Cumulative Allowance applied in model years 2026 through 2030 and calculated by multiplying 10 percent times the applicable model year Annual Requirement for each model year and then summed together for the cumulative allowance.FunctionalMandatoryAnna Wong
1.1, 1.7FMCL-42Calculation LogicAccount Balance ManagementConverted ZEV and PHEV ValuesFor manufacturers electing to use a cumulative allowance per ABM-40, the System will calculate an EJ Cumulative threshold for each manufacturer by multiplying 0.5 percent times the applicable model year Annual ZEV Requirement.FunctionalMandatoryAnna Wong
1.1, 1.7FMCL-43Calculation LogicAccount Balance ManagementConverted ZEV and PHEV ValuesThe System will compare EJ Values earned (see ABM-19 through ABM-25) in MY 2026, 2027 and 2028 ≥ EJ Cumulative threshold for the same model year. This is an individual comparison and not additive. If the EJ Values earned is ≥ EJ Cumulative threshold for one of those model years, the System will add 5% to the Converted PHEV and ZEV Cumulative Allowance threshold for the first three model years of the Annual ZEV Requirement, and recalculate manufacturers cumulative allowance, per ABM-41. The System will calculate and apply a new Converted ZEV and PHEV Cumulative Allowance applied in 2026 through 2028 MY and calculated by multiplying 15 percent times the applicable model year Annual Requirement for each model year and then summed together for the cumulative allowance.FunctionalMandatoryAnna Wong
1.1, 1.7FMCL-44Calculation LogicAccount Balance ManagementConverted ZEV and PHEV ValuesIf the EJ Values earned is ≥ EJ Cumulative threshold for two of those model years, the System will add 5% to the Converted PHEV and ZEV Cumulative Allowance threshold for the first four model years of the Annual ZEV Requirement, and recalculate manufacturers cumulative allowance, per ABM-41. The System will calculate and apply a new Converted ZEV and PHEV Cumulative Allowance applied in 2026 through 2029 MY and calculated by multiplying 15 percent times the applicable model year Annual Requirement for each model year and then summed together for the cumulative allowance.FunctionalMandatoryAnna Wong
1.1, 1.7FMCL-45Calculation LogicAccount Balance ManagementConverted ZEV and PHEV ValuesIf the EJ Values earned is ≥ EJ Cumulative threshold for three of those model years, the System will add 5% to the Converted PHEV and ZEV Cumulative Allowance threshold for the first five model years of the Annual ZEV Requirement, and recalculate manufacturers cumulative allowance, per ABM-41. The System will calculate and apply a new Converted ZEV and PHEV Cumulative Allowance applied in 2026 through 2030 MY and calculated by multiplying 15 percent times the applicable model year Annual Requirement for each model year and then summed together for the cumulative allowance.FunctionalMandatoryAnna Wong
1.1, 1.7FMCL-46Calculation LogicAccount Balance ManagementPooled ZEV and PHEV ValuesThe System will calculate and apply a Pooled ZEV and PHEV Allowance for each manufacturer for model years 2026 by multiplying 25 percent times the applicable model year Annual ZEV Requirement.FunctionalMandatoryAnna Wong
1.1, 1.7FMCL-47Calculation LogicAccount Balance ManagementPooled ZEV and PHEV ValuesThe System will calculate and apply a Pooled ZEV and PHEV Allowance for each manufacturer for model years 2027 by multiplying 20 percent times the applicable model year Annual ZEV Requirement.FunctionalMandatoryAnna Wong
1.1, 1.7FMCL-48Calculation LogicAccount Balance ManagementPooled ZEV and PHEV ValuesThe System will calculate and apply a Pooled ZEV and PHEV Allowance for each manufacturer for model years 2028 by multiplying 15 percent times the applicable model year Annual ZEV Requirement.FunctionalMandatoryAnna Wong
1.1, 1.7FMCL-49Calculation LogicAccount Balance ManagementPooled ZEV and PHEV ValuesThe System will calculate and apply a Pooled ZEV and PHEV Allowance for each manufacturer for model years 2029 by multiplying 10 percent times the applicable model year Annual ZEV Requirement.FunctionalMandatoryAnna Wong
1.1, 1.7FMCL-50Calculation LogicAccount Balance ManagementPooled ZEV and PHEV ValuesThe System will calculate and apply a Pooled ZEV and PHEV Allowance for each manufacturer for model years 2030 by multiplying 5 percent times the applicable model year Annual ZEV Requirement.FunctionalMandatoryAnna Wong
1.1, 1.7FMCL-51Calculation LogicAccount Balance ManagementPooled ZEV and PHEV ValuesThe System shall allow manufacturers to transfer excess 2026 through 2030 MYs ZEV and PHEV values earned in California or a S177 State to satisfy shortfalls or deficit in 2026 through 2030 MYs earned in California or a S177 State, up to their calculated Pooled ZEV and PHEV Allowance, per ABM-46 through ABM-51.FunctionalMandatoryAnna Wong
1.1, 1.7FMCL-52Calculation LogicAccount Balance ManagementPooled ZEV and PHEV ValuesThe System shall allow manufacturers to report to the Program or State Administrator to which state the values are being transferred.FunctionalMandatoryAnna Wong
1.1, 1.7FMCL-53Calculation LogicAccount Balance ManagementPooled ZEV and PHEV ValuesThe System shall allow the Program and State Administrator to confirm the transfer request of excess Values, in the case of “pooling”.FunctionalMandatoryAnna Wong
1.1, 1.7FMCL-54Calculation LogicAccount Balance ManagementPooled ZEV and PHEV ValuesThe System shall ensure that a manufacturer does not transfer more excess ZEV or PHEV values than are necessary to fulfill a shortfall within a given year or a deficit carried forward from a previous MY.FunctionalMandatoryAnna Wong
1.1, 1.7FMCL-55Calculation LogicAccount Balance ManagementProportional FCEV ValuesThe System shall calculate the Annual proportional FCEV allowance based on the state among California and all Section 177 ZEV states with the highest quantity of vehicle values earned from FCEVs.FunctionalMandatoryAnna Wong
1.1, 1.7FMCL-56Calculation LogicAccount Balance ManagementProportional FCEV ValuesThe System shall calculate the FCEV percentage share by dividing the number of vehicle values from FCEVs earned in that state by the manufacturers Annual ZEV Requirement (in vehicle values) for the model year in the same stateFunctionalMandatoryAnna Wong
1.1, 1.7FMCL-57Calculation LogicAccount Balance ManagementProportional FCEV ValuesThe System shall calculate the Annual proportional FCEV allowance by multiplying the FCEV percentage share, or 10 percent, whichever is smaller, times the applicable model year Annual ZEV Requirement (in vehicle values).FunctionalMandatoryAnna Wong
1.1, 1.7FMCL-58Calculation LogicAccount Balance ManagementProportional FCEV ValuesFor each model year 2026 through 2030, the System shall calculate the proportional FCEV values as equal to the annual proportional FCEV allowance minus the vehicle values earned from FCEV in the state.FunctionalMandatoryAnna Wong
1.1, 1.7FMCL-59Calculation LogicAccount Balance ManagementProportional FCEV ValuesThe System shall prohibit a manufacturer from earning proportional FCEV values if FCEV vehicle values in the state is equal to or exceeds the proportional FCEV allowance for a given MY.FunctionalMandatoryAnna Wong

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 .