Addendum_1_PO_5125-004.pdf

STATE OF CALIFORNIA------- CALIFORNIA STATE TRANSPORTATION AGENCY Gavin Newsom, Governor

DEPARTMENT OF TRANSPORTATION

ADMINISTRATION

DIVISION OF PROCUREMENT AND CONTRACTS MS-65

1727 30TH STREET

SACRAMENTO, CA 95816-7006

PHONE (916) 227-6000

FAX (916) 227-6155

TTY (800) 735-0193 or (916) 227-6131 https://dot.ca.gov/programs/procurement-and-contracts/

Flex your power!

Be energy efficient!

September 3, 2024

Addendum No. 1 PO # 5125*004 / Request for Quote RQS # 5124*16

Vehicle to Infrastructure Communication

NOTICE TO ALL PROSPECTIVE BIDDERS:

Addendum No. 1 is being issued for the above-referenced PO. Offers for this work shall be with the full understanding of this Addendum. All other terms and conditions set forth in PO 5125*004 shall remain in full force and effect.

RFQ has been updated. All quotes shall be in accordance with the updated RFQ and bidders must submit the updated RFQ with their quote package. Failure to use the correct RFQ will result in their bid being non-responsive.

THE FOLLOWING REPRESENT QUESTIONS ASKED AND THE DEPARTMENTS RESPONSE:

REVISIONS

The due date for quote submission has been extended. Please see the updated timeline below:

Question 1:

The description below from the Cal eProcure web site does not describe any monitoring or testing services. It describes SCMS and PKI but does not let us know exactly what you want us to do. RSUs are short range wireless devices that communicate with an onboard unit (OBU) that are typically installed in vehicles. Do you want us to perform an RSU to OBU test at each RSU in the Caltrans inventory by driving a vehicle equipped with an OBU to each RSU site? The event package does not tell us how many there are or where they are located.

How often do you want them tested (once per year)? Do you have any test metrics, or would you like for us to develop them?

Answer:

No.

PO 5125*004

Question 2:

The RSUs are also typically connected to a network of some kind, like the fiber optic network in D12. Do you want us to perform a communications test through the network to ensure that the RSU to Infrastructure side is working?

Answer:

No.

Question 3:

Please provide us with a description of the services that you would like for us to perform, along with the quantity and location of the RSUs.

Answer:

Requesting a Security Credential Management System (SCMS) V2X credentials and turnkey managed service to securely generate and distribute vehicle-to-vehicle and vehicle-to-infrastructure certificates direct to vehicle and roadside communication devices.

The SCMS portal provides the security infrastructure to issue and manage the security certificates that form the basis of trust for V2V and V2I communication. Connected vehicle devices Roadside Unit (OBU) and Onboard Unit (OBU) enroll into an SCMS portal, obtain security certificates from Certificate Authorities (CAs), and attach those certificates to their messages as part of a digital signature. The SCMS portal will register and manage security certificates for the RSU and OBU devices.” The RSU and OBU renew security certificates with the SCMS portal within a predetermined time frame i.e., two weeks.

Projected number of RSU and OBU devices to register for security certificates in the SCMS portal:

Year 1 (181 RSUs) and (20 OBUs), Year 2 (490 RSUs) and (30 OBUs), Year 3 (610 RSUs) and (40 OBUs).

The service is in California.

Question 4:

Are you looking for BSM information from OBUs? Do you need BSM/PSM forwarding?

Answer:

No.

Question 5:

Do you need the ability to update or upgrade the firmwares of RSUs? How about OBUs?

Answer:

No.

Question 6:

Are there specific fields on the CV2X radio, such as radio power, CPU usage, that you’re looking for? Please specify fields.

Answer:

No.

Question 7:

Do you require SCMS signing? SCMS relay?

Answer:

Yes, SCMS signing.

Question 8:

Any requirement for API interface to your incident response server?

Answer:

We are not aware of any.

Question 9:

Automated TIM creation?

No.

Question 10:

Can documentation be provided that detail the requirements including technical, engineering service, implementation and operational aspects?

Answer:

Yes, see attachment section 2.5.

Question 11:

The SCMS of Autocrypt consists of 1) a server, 2) certificate, and 3) a web portal for registration and system management. If there are any additional necessary features, please let us know.

Answer:

No.

Question 12:

For the management tool, are there any specific requirements on functions or features?

Answer:

No.

Question 13:

Can you provide a concept of operation including system architecture.

Answer:

See attachment, section 2.4.

Question 14:

Which version of the standards should we be supporting? CAMP or 1609.2.1?

Answer:

1609.2.1.

Question 15:

Is there a CTL or an existing system we need to be compatible with?

Answer:

We are not aware of what CTL is. If the question in reference is regarding CRL, that is yet to be determined.

Question 16:

Is there a requirement for an elector system for adopting and rejecting Root Authorities (RA) and Certificate Authorities (CA)?

Answer:

Yes. “Electors represent a distributed body of trust anchors who authorize themselves and root CAs to operate within the PKI. Essentially, an elector is similar to a root certificate, except that the actual root must be affirmed by the signatures of multiple electors.”

Question 17:

Misbehavior Detection shall be included? If so, we will need to see overall requirements for the system architecture.

Answer:

Yes, see attachment.

Question 18:

How long are certificates intended to last? Expiration date?

Answer:

Up to three (3) years.

Question 19:

How many OBU and RSU have been deployed and planned for future deployment?

Projected Deployment Year 1 (181 RSUs) and (20 OBUs), Year 2 (490 RSUs) and (30 OBUs), Year 3 (610 RSUs) and (40 OBUs) Question 20:

Do you have a list of approved PSIDs?

Answer:

Yes.

Question 21:

Is there any expected deployment timeline or schedule we should be adhering to over the 3 years?

Answer:

See projected RSUs and OBUs deployment.

Sincerely, Michelle Garcia IT Contract Analyst

2.5 How does an SCMS Portal work?

An SCMS portal provides the security infrastructure to issue and manage the security certificates that form the basis of trust for V2V and V2I communication. Connected vehicle devices enroll into an SCMS, obtain security certificates from Certificate Authorities (CAs), and attach those certificates to their messages as part of a digital signature. The certificates prove the device is a trusted actor in the system, while also maintaining privacy. Misbehavior detection and reporting allow the system to identify bad actors and revoke message privileges when necessary.

Enrolling into the System:

The enrollment process, also referred to as bootstrapping, is the first step in getting a device connected to the SCMS. During enrollment, a device will create a public or private key pair and produce an enrollment request that includes its public key. The public key is signed with its private key, which will be sent to the SCMS and await the enrollment request response. The SCMS will respond with an enrollment private key reconstruction file, so the device can create its enrollment public-private key pair. This process requires a secure physical environment because keys are being exchanged.

Device vendors generally conduct the enrollment or bootstrapping process themselves to ensure it is done securely.

Normal Operations:

Once a device has valid enrollment credentials it can start requesting operational certificates. Devices will connect through a normal network connection to an SCMS Registration Authority (RA) to request new certificates. The RA is an intrinsically, non-central component of the SCMS. There may be multiple RAs active at any given time in the SCMS. Requesting new certificates is done via normal HTTPS protocols. For OBUs, they will need to connect to the SCMS via an RSU that advertises either the SCMS service or an IP service. The SCMS generates and stores three years’ worth of pseudonym/identification certificates. Each week, a new weeks’ worth of certificates is generated and added. (Note: OBUs can download however many weeks’ worth of certificates the device vendor configures, up to 3 years.) The SCMS generates application certificates only up to a week in advance, so RSUs will be required to connect to the SCMS on a more regular basis to request new application certificates.

Certificate Management:

CAs within the SCMS ecosystem create, distribute, and revoke certificates. The CAs form a chain of trust, with each authority representing an individual link along the chain. The chain follows a hierarchy so that the signature on a certificate from any entity (CA) along the chain is validated as a validator climbs up a link of the chain, and if the last signature on the chain is verified and that entity is implicitly trusted (a trust anchor), then the whole chain is accepted, and trust flows down to the entity at the bottom of the chain. This concept is called chain-validation of certificates and is the fundamental concept of a PKI system. The SCMS makes use of several certificate types depending on whether the connected vehicle application is installed on a vehicle or roadside unit (RSU).

STATE OF CALIFORNIA------- CALIFORNIA STATE TRANSPORTATION AGENCY Gavin Newsom., Governor

DEPARTMENT OF TRANSPORTATION

ADMINISTRATION

1727 30TH STREET, MS-65

SACRAMENTO, CA 95814

FAX (916) 227-6155

TTY 711

http://caltrans-opac.ca.gov/

Making Conservation a California Way of Life!

Notice to Bidders Request for Quote RQS # 5124*16 PO # 5125*004

Formal Competitive Over $50,000 – IT Goods Request for Quote (RFQ) – IT Goods. This method is for competitive procurements. Procurements over 50K are required to be published on The California State Contracts Register (CSCR) system which was established to maximize competition through advertising State purchasing and contracting opportunities.

This RFQ solicitation incorporates, by reference, the following terms and conditions:

Bidder Instructions (GSPD 451)

Information Technology General Provisions (GSPD-401 IT) General Artificial Intelligence (GenAI) A. The State of California seeks to realize the potential benefits of GenAI, through the development and deployment of GenAI tools, while balancing the risks of these new technologies.

B. Bidders/Offerors must notify the State in writing if their solution or service includes, or makes, available, any GenAI technology, including GenAI from third parties or subcontractors. The State has developed a GenAI Disclosure & Factsheet to be completed by the Bidder/Offeror.

C. Failure to disclose GenAI to the State and submit the GenAI Disclosure & Factsheet will result in disqualification of the Bidder/Offeror and may void any resulting contract. The State reserves its right to seek any and all relief it may be entitled to as a result of such non-disclosure.

D. Upon receipt of a Bidder/Offeror GenAI Disclosure & Factsheet the state reserves the right to incorporate GenAI Special Provisions into the final contract or reject bids/offers that present an unacceptable level of risk to the state

Submittal of a quote in response to this solicitation is the Bidder’s acceptance to the terms and conditions at the links above and confirmation of compliance to the provisions set forth herein.

You are invited to review and respond to this Request for Quote (RFQ), RQS # 5124*16. In submitting your quote, you shall comply with the instructions found herein. Prospective Vendors and/or Suppliers are encouraged to consider programs and preferences that are available, such as those for the use of Microbusinesses (MB), Small Businesses (SB), Disabled Veteran Business Enterprises (DVBE), Disadvantaged Business Enterprises (DBE), and other businesses covered by State and Federal programs and preferences.

As required by Executive Order S-02-06, the California Department of Transportation (Caltrans) is committed to meeting the State’s 25 percent (25%) Small Business (SB) participation goal. Certified SBs and Micro Businesses (MB) are encouraged to submit bids and a SB incentive may apply to this RFQ. A Disabled Veteran Business Enterprise (DVBE) goal is not required, but DVBE participation is encouraged, and a DVBE incentive may apply to this RFQ.

Time Schedule: It is recognized that time is of the essence. All bidders are hereby advised of the schedule set forth below and are expected to adhere to the specified required dates and times below.

http://caltrans-opac.ca.gov/ https://www.dgs.ca.gov/-/media/Divisions/PD/PTCS/OPPL/Model-Language/IT/GSPD451-110911.ashx?la=en&hash=9EED86E70D634F5F89087ACE5A3583FB0D79C347 https://www.documents.dgs.ca.gov/dgs/fmc/pdf/std1000.pdf https://www.documents.dgs.ca.gov/dgs/fmc/pdf/std1000.pdf

Department of Transportation Formal Competitive Over $50,000 RFQ - IT Goods (Rev. 11/2023)

EVENT DATE TIME

RFQ available to prospective bidders 8/21/2024 Questions due from prospective bidders 8/28/2024 3:00PM

Quote Submission Due Date and Time (Pacific Time) 9/5/2024

9/9/2024 3:00PM

Intent to Award (estimate) 9/19/2024 9/30/2024

To be considered responsive, quotes must be received by the Quote Submission Due Date and Time, as specified above. The State assumes no responsibility if the vendor cannot transmit its quote package via fax or email or if the entire quote package is not received by the quote due date and time.

RETURN QUOTES AND/OR SUBMIT QUESTIONS TO

Department of Transportation Requester’s Name: District #: Office Name:

Michelle Garcia HQ IT Procurements and Contracts Address (Street, City, State, Zip):

1727 30th Street, Sacramento, CA 95816 Telephone Number: Email Address:

(279) 234-2470 Michelle.garcia@dot.ca.gov

Note: Any oral information given will not be binding upon Caltrans unless such information is issued in writing as an official addendum.

Quote Expiration Date Delivery Date/# of days ARO Shipment 60 days from Quote Due Date FOB Destination, Freight Prepaid Ship To:

By signing below, with inclusion of the date of signature, the bidder DECLARES UNDER PENALTY OF PERJURY under the laws of the State of California as follows:

1. Statement of Compliance. The below signed as complied with the non-discrimination program requirements of

Government Code 12990 and Title 2, California Administrative Code Section 8103, and such declaration is true and correct.

2. The National Labor Relations Board declaration set forth in Paragraph 48 of the General Provisions is true and correct.

3. If a claim is made for the Small Business or Disabled Veterans Business Enterprise preference, the information set forth within is true and correct.

Signatory must be authorized to bind vendor contractually.

SUPPLIER INFORMATION

Supplier Name Contact Name

Address City State Zip Code Phone Number Fax Number Email Address Federal Employer Identification (FEIN) Number

Seller’s Permit Number

SB/DVBE Certification Number

Bidder agrees if this response is accepted within 60 calendar days following the date the response is due to furnish all the items upon which prices are offered, at the prices set opposite each item, delivered at the designated point(s) by the method of delivery, within the times specified and subject to the referenced General Provisions.

Printed Name and Title Official’s Signature Date

SUPPLIER REQUIRED DOCUMENTS CHECKLIST

To be considered responsive, Bidder must return the completed documents listed.

Formal Competitive over $50,000 Request for Quote (This form signed and completed) Quote Sheet(s) (Supplier’s letterhead is optional and subject to all requirements in this solicitation)

Bidder Declaration Form (GSPD-05-105 Rev. 08/09) is required from all bidders. If not MB, SB, SB/NVSA, and/or DVBE, select “None” on form. See page 2 of form for instructions

Any MB, SB, SB/NVSA, and/or DVBE must provide a Commercially Useful Function Certification Form GenAI Disclosure & Factsheet Form (STD 1000) required from all offerors to be deemed responsive

California Civil Rights Laws Certification: Complete, as applicable, when the total contract value is $100,000 or more.

Payee Data Record (STD. 204) Complete and return

N/A If claiming DVBE status, you must complete STD. 843, Disabled Veteran Business Enterprise Declaration

Note:

• Bidder’s forms, license agreements, or other documents shall not be signed by state employees.

• Any documents provided by the bidder may be incorporated by referenced in accordance with the

General Provisions – Order of Precedence referenced on the front page of this solicitation.

• Supplier Signatures - For any written solicitation, supplier quote and/or bid responses regardless of dollar value; solicitation format or delivery method (i.e., fax, electronically, mailed or delivered in person) must include the signature of an authorized supplier representative of the bidder.

https://www.documents.dgs.ca.gov/dgs/fmc/gs/pd/gspd05-105.pdf https://forms.dot.ca.gov/v2Forms/servlet/FormRenderer?frmid=ADM3025 https://www.documents.dgs.ca.gov/dgs/fmc/pdf/std1000.pdf https://cefs2.dot.ca.gov/v2Forms/servlet/FormRenderer?frmid=ADM0076 https://www.documents.dgs.ca.gov/dgs/fmc/pdf/std204.pdf https://www.documents.dgs.ca.gov/dgs/fmc/gs/pd/pd_843.pdf https://www.documents.dgs.ca.gov/dgs/fmc/gs/pd/pd_843.pdf

Supplier Name Contact Name Supplier’s Quote Number

COMMODITY INFORMATION: Supplier’s quotes as stated herein are all inclusive and no additional allowance will be paid unless separate payment provisions in the Purchase Order should specifically provide otherwise.

The list of commodities is continued on the next page – The total of all quotes shall be entered on this page.

Quotation Award: For the purposes of this solicitation, contract award will be made to the lowest responsive responsible bidder on the basis of “All or None.”

Quotation Award: For the purposes of this solicitation, contract award will be made to the lowest responsive responsible bidder’s individual items and/or a combination of items.

Supplier Attached Quote on Supplier’s Letterhead. Unit Price and Extension price are not required on this form when provided on Supplier’s letterhead. Quote Total $

Item # Quantity Unit of

Measure

Commodity or Product Code (if applicable)

Description/Specifications/Pallet Requirements

Vendor may propose an alternative model/brand name or trade name that complies with the specifications or requirements of this solicitation.

Any mention of a model/ brand name or trade name description is for reference purposes ONLY.

Unit Price $ Extension $ (Quantity* Unit Price)

1 1 181 EA 046171640

Vehicle to Everything Communication Monitoring Year 1 2024 Roadside Unit (RSU)

2 1 490 EA 046171640

Vehicle to Everything Communication Monitoring Year 2 2025 Roadside Unit (RSU)

3 1 610 EA 046171640

Vehicle to Everything Communication Monitoring Year 3 2026 Roadside Unit (RSU)

4 1 20 EA 046171640

Vehicle to Everything Communication Monitoring Year 1 2024 Onboard Unit (OBU)

5 1 30 EA 046171640

Vehicle to Everything Communication Monitoring Year 1 2024 Onboard Unit (OBU)

6 1 40 EA 046171640

Vehicle to Everything Communication Monitoring Year 1 2024 Onboard Unit (OBU)

Supplier Name Contact Name Supplier’s Quote Number

OPTIONAL AMENDMENT:

1. Subject to the original terms and conditions and contingent upon approval of the State and the Contractor, the State may have the option to amend the Agreement. The Purchase Order (STD. 65) allows for an Agreement Amendment for time and/or quantity, for more of the same item(s).

2. If the Agreement were amended, the Contractor’s rates below would apply. There is no commitment as a result of this RFQ to issue an Agreement for any part of the optional amendment items.

Any resulting Agreement Amendment will not take effect until it is signed by a Caltrans Contract Officer, and the Contractor has received a signed copy of the Purchasing Authority Purchase Order (STD. 65) amendment.

Supplier Attached Quote on Supplier’s Letterhead. Unit Price and Extension price are not required on this form when provided on Supplier’s letterhead. Quote Total $

Item # Quantity Unit of

Measure

Commodity or Product Code (if applicable)

Description/Specifications/Pallet Requirements

Vendor may propose an alternative model/brand name or trade name that complies with the specifications or requirements of this solicitation.

Any mention of a model/ brand name or trade name description is for reference purposes ONLY.

Unit Price $ Extension $ (Quantity* Unit Price)

1 1 181 EA 046171640

Vehicle to Everything Communication Monitoring Year 1 2024 Roadside Unit (RSU)

2 1 490 EA 046171640

Vehicle to Everything Communication Monitoring Year 2 2025 Roadside Unit (RSU)

3 1 610 EA 046171640

Vehicle to Everything Communication Monitoring Year 3 2026 Roadside Unit (RSU)

4 1 20 EA 046171640

Vehicle to Everything Communication Monitoring Year 1 2024 Onboard Unit (OBU)

5 1 30 EA 046171640

Vehicle to Everything Communication Monitoring Year 1 2024 Onboard Unit (OBU)

6 1 40 EA 046171640

Vehicle to Everything Communication Monitoring Year 1 2024 Onboard Unit (OBU)