Extracted text (via pymupdf)
145993 characters
SERIAL 260056-C
ROADSIDE UNIT AND ONBOARD UNIT DEVICES (CVAZ)
DATE OF LAST REVISION: January 28, 2026
CONTRACT END DATE: January 31, 2028
CONTRACT PERIOD THROUGH JANUARY 31, 2028
TO:
All Departments
FROM:
Office of Procurement Services
SUBJECT:
Contract for ROADSIDE UNIT AND ONBOARD UNIT DEVICES (CVAZ)
Attached to this letter is published an effective purchasing contract for products and/or services to be
supplied to Maricopa County activities as awarded by Maricopa County on January 28, 2026
All purchases of products and/or services listed on the attached pages of this letter are to be obtained
from the vendor holding the contract. Individuals are responsible to the vendor for purchases made
outside of contracts. The contract period is indicated above.
RB/mm
Attach
Copy to:
Office of Procurement Services
Beverly Krumm, MCDOT
Joe Cottrell, MCDOT
SERIAL 260056-C
AM SIGNAL LLC, 8100 SOUTHPARK WAY, UNIT A-10, LITTLETON, CO 80120
COMPANY NAME:
AM Signal, LLC
DOING BUSINESS AS (dba):
MAILING ADDRESS:
8100 Southpark Way A10
Littleton, CO 80120
REMIT TO ADDRESS:
8100 Southpark Way A10
Littleton, CO 80120
TELEPHONE NUMBER:
720-348-6925
WWW ADDRESS:
www.amsignal.com
CONTACT NAME:
Gale Nation
CONTACT TELEPHONE NUMBER:
720-348-6925
CONTACT EMAIL ADDRESS:
gale@amsignal.com
UNIQUE ENTITY IDENTIFIER (UEI):
86-1864868
YES
NO
REBATE
WILL ALLOW OTHER GOVERNMENTAL ENTITIES TO PURCHASE
FROM THIS CONTRACT:
X
WILL ACCEPT PROCUREMENT CARD FOR PAYMENT:
X
Central core of the Phoenix metro region encompassing areas of Phoenix, Avondale, Tolleson and
unincorporated Maricopa County.
Item
Description
Unit of
Measure
Quantity
Unit
Price ($)
Bulk Price Discount
Notes
Roadside Unit
(RSU) Hardware
and
Configuration
Roadside
Unit
hardware
per unit
Each
1
$5,459.00
10% 15-50 units
15% 50-85 units
20% 85 units +
Commsignia
RSU. Price
includes 5 yr
warranty
Roadside
Processor
(RSP) Hardware
Roadside
Processor
hardware
Each
1
$5,500.00
100+ is 1% discount
200+ is 2% discount
300+ is 3% discount
MH Corbin
RSP with 5
year warranty
Roadside
Processor
(RSP) Software
and
Configuration
Roadside
Processor
Software
Each
1
$3,930.00
10% 200-299 units
12.5% 300-399 units
15% 400-499 units
20% 500+ units
IntelliConnect
RSP Software.
Price includes
5 year warranty
On-Board Unit
(OBU)
Hardware and
Configuration
On-Board
Unit
hardware
per unit
Each
1
$5,448.00
10% 15-50 units
15% 50-85 units
20% 85 units +
Commsignia
OBU. Price
includes 5 yr
warranty
SERIAL 260056-C
AM SIGNAL LLC
WARRANTY
Year
Unit of
Measure
Quantity
Unit Price
Description
Year 6 - Commsignia
RSU or OBU
/device/year
1
$370.00
Commsignia RSU and OBU
extended warranty per device/ per
year
Year 7 - Commsignia
RSU or OBU
/device/year
1
$370.00
Commsignia RSU and OBU
extended warranty per device/ per
year
Year 8 - Commsignia
RSU or OBU
/device/year
1
$370.00
Commsignia RSU and OBU
extended warranty per device/ per
year
Year 9 - Commsignia
RSU or OBU
/device/year
1
$370.00
Commsignia RSU and OBU
extended warranty per device/ per
year
Year 6 - Kyra Solutions
S/W
/device/year
1
$675.00
Kyra IntelliConnect RSP Software
Year 7 - Kyra Solutions
S/W
/device/year
1
$830.00
Kyra IntelliConnect RSP Software
Year 8 - Kyra Solutions
S/W
/device/year
1
$942.00
Kyra IntelliConnect RSP Software
Year 6 - MH Corbin RSP
Hardware
/device/year
1
$350.00
MH Corbin RSP Hardware
extended warranty per device/ per
year
Year 7 - MH Corbin RSP
Hardware
/device/year
1
$370.00
MH Corbin RSP Hardware
extended warranty per device/ per
year
Year 8 - MH Corbin RSP
Hardware
/device/year
1
$390.00
MH Corbin RSP Hardware
extended warranty per device/ per
year
Year 9 - MH Corbin RSP
Hardware
/device/year
1
$410.00
MH Corbin RSP Hardware
extended warranty per device/ per
year
Please provide discount off catalog of products with current pricing. You may upload a separate
document for catalog style. The catalog must have Unit Price, Percent Discount, Effective Date, and
Product Name or Product Description. Contractor must list catalogs encompassing the scope of
items/commodities offered for sale by/through that respondent. Contractor are strongly encouraged to
list any other additional pricing caveats separately (such as volume discounts, or discounts by item
type or category).
Product
Code (If
applicable)
Product Name or
Product Description
Manufacturer
Quantity
Unit
Price
Percent
Discount
From
Catalog
Additional
notes
RSU and OBU Basic
training per 8 hr day.
Add'l training beyond
initial training sessions.
Commsignia
1
$1,330.00
10%
Commsignia ForeSight
Android Application -
OBU
Commsignia
1
$1,335.00
10%
SERIAL 260056-C
AM SIGNAL LLC
HMI Android
Commsignia
1
$360.00
10%
Professional Remote
Support per
month/device
Commsignia
1
$350.00
10%
Per month
per device
Commsignia On-site
technical assistance with
intersection set up
Commsignia
1
$2,778.00
10%
All other Commsignia
items not listed, take
10% off list price
Commsignia
1
10%
Commsigna
product list
and
associated
items.
Kyra Solutions Labor
Rate for Software
Specialist (travel cost
extra ast actual, if
required)
Kyra
Solutions
1
$225.00
10%
All other Kyra products
not listed, take 10% off
list price.
Kyra
Solutions
1
10%
Kyra
Solutions
product list
and
associated
items.
All other AM Signal
RSU, OBU, RSP
Related items not listed,
take 10% off list price
AM Signal,
LLC
1
10%
AM Signal
product list
and
associated
items.
PRICING SHEET: NIGP CODE 55080
Terms:
NET 30 DAYS
Vendor Number
VC0000006776
Certificates of Insurance
Required
Contract Period:
To cover the period ending January 31, 2028.
ATTACHMENT B: AGREEMENT PAGE
Respondent hereby certifies that respondent has read, understands, and agrees that acceptance by Maricopa County
of the respondent’s offer will create a binding contract. Respondent agrees to fully comply with all terms and conditions
as set forth in the Maricopa County Procurement Code, and amendments thereto, together with the specifications and
other documentary forms herewith made a part of this specific agreement.
BY SIGNING THIS PAGE, THE SUBMITTING RESPONDENT CERTIFIES THAT RESPONDENT HAS REVIEWED
MARICOPA COUNTY’S “STANDARD TERMS AND CONDITIONS,” A COPY OF WHICH CAN BE FOUND AT
https://www.maricopa.gov/DocumentCenter/View/6453.
RESPONDENT (FIRM) SUBMITTING PROPOSAL
FEDERAL TAX ID #
PRINTED NAME AND TITLE
ADDRESS
TELEPHONE #
CITY
STATE
ZIP
DATE
WEBSITE URL
EMAIL
MARICOPA COUNTY, ARIZONA
BY:
CHAIRMAN, BOARD OF SUPERVISORS
DATE
ATTESTED:
CLERK OF THE BOARD
DATE
APPROVED AS TO FORM:
DEPUTY COUNTY ATTORNEY
DATE
AUTHORIZED SIGNATURE
AM Signal, LLC
Brooke Hageny, Director of Inside Sales and Estimating
Brooke@amsignal.com
8100 Southpark Way #A10
Littleton CO
80120
www.amsignal.com
86-1864868
720-348-6925
11/09/2025
SIGN
SIGN
SIGN
SERIAL 260056-C
COHDA WIRELESS AMERICA LLC DBA: COHDA WIRELESS, 450 E 96TH ST STE 500 OFFICE 5119,
INDIANAPOLIS, IN 46240
COMPANY NAME:
Cohda Wireless America LLC
DOING BUSINESS AS (dba):
MAILING ADDRESS:
450 East 96th Street Suite 500 Office 5119
Indianapolis IN 46240-3760
REMIT TO ADDRESS:
450 East 96th Street Suite 500 Office 5119
Indianapolis IN 46240-3760
TELEPHONE NUMBER:
+1 317 818 5595
WWW ADDRESS:
cohdawireless.com
CONTACT NAME:
Paul Gray
CONTACT TELEPHONE NUMBER:
+61 423 495 449
CONTACT EMAIL ADDRESS:
paul.gray@cohdawireless.com
UNIQUE ENTITY IDENTIFIER (UEI):
U4ABXX4CFJH9
YES
NO
REBATE
WILL ALLOW OTHER GOVERNMENTAL ENTITIES TO PURCHASE
FROM THIS CONTRACT:
X
WILL ACCEPT PROCUREMENT CARD FOR PAYMENT:
X
Central core of the Phoenix metro region encompassing areas of Phoenix, Avondale, Tolleson and
unincorporated Maricopa County.
Item Description
Unit of
Measure
Quantity
Unit Price
($)
Bulk
Price
Discount
Notes
Roadside Unit (RSU)
Hardware and
Configuration
Roadside Unit
hardware per
unit
Each
650
2667
34.4%
Bulk price
discount
applied for
650 units.
TPT
inclusive.
Roadside Processor
(RSP) Hardware
Roadside
Processor
hardware
Each
1
Not
offered
Roadside Processor
(RSP) Software and
Configuration
Roadside
Processor
Software
Each
1
Not
offered
On-Board Unit (OBU)
Hardware and
Configuration
On-Board Unit
hardware per
unit
Each
400
1983
27.1%
Bulk price
discount
applied for
400 units.
TPT
inclusive.
SERIAL 260056-C
COHDA WIRELESS AMERICA LLC DBA: COHDA WIRELESS
WARRANTY
Year
Unit of
Measure
Quantity
Unit Price
Description
Year 6
2% of price
650 RSU / 400 OBU
$53 RSU / $40 OBU
TPT inclusive
Year 7
2% of price
650 RSU / 400 OBU
$53 RSU / $40 OBU
TPT inclusive
Year 8
2% of price
650 RSU / 400 OBU
$53 RSU / $40 OBU
TPT inclusive
Year 9
2% of price
650 RSU / 400 OBU
$53 RSU / $40 OBU
TPT inclusive
Please provide discount off catalog of products with current pricing. You may upload a separate
document for catalog style. The catalog must have Unit Price, Percent Discount, Effective Date, and
Product Name or Product Description. Contractor must list catalogs encompassing the scope of
items/commodities offered for sale by/through that respondent. Contractor are strongly encouraged
to list any other additional pricing caveats separately (such as volume discounts, or discounts by
item type or category).
Product Code (If
applicable)
Product
Name or
Product
Description
Manufacturer
Quantity
Unit
Price
Percent
Discount
From
Catalog
Additional notes
CWP-RSUsK-MK06-
US00106
MK6 RSU
Kit inc.
Maintenance
+ PoE
Cohda
Wireless
1
5319
23.6%
Includes 12
months
maintenance, 5
years warranty,
shipping
CWP-OBUsK-MK06-
US00106
MK6 OBU
Kit inc.
Maintenance
Cohda
Wireless
1
4761
42.9%
Includes 12
months
maintenance, 5
years warranty,
shipping
PRICING SHEET: NIGP CODE 55080
Terms:
NET 30 DAYS
Vendor Number
VS0000011391
Certificates of Insurance
Required
Contract Period:
To cover the period ending January 31, 2028.
$77$&+0(17% $*5((0(173$*(
5HVSRQGHQWKHUHE\FHUWLILHVWKDWUHVSRQGHQWKDVUHDGXQGHUVWDQGVDQGDJUHHVWKDWDFFHSWDQFHE\0DULFRSD&RXQW\
RIWKHUHVSRQGHQW¶VRIIHUZLOOFUHDWHDELQGLQJFRQWUDFW5HVSRQGHQWDJUHHVWRIXOO\FRPSO\ZLWKDOOWHUPVDQGFRQGLWLRQV
DVVHWIRUWKLQWKH0DULFRSD&RXQW\3URFXUHPHQW&RGHDQGDPHQGPHQWVWKHUHWRWRJHWKHUZLWKWKHVSHFLILFDWLRQVDQG
RWKHUGRFXPHQWDU\IRUPVKHUHZLWKPDGHDSDUWRIWKLVVSHFLILFDJUHHPHQW
%<6,*1,1*7+,63$*(7+(68%0,77,1*5(6321'(17&(57,),(67+$75(6321'(17+$65(9,(:('
0$5,&23$ &2817<¶6 ³67$1'$5' 7(506 $1' &21',7,216´ $ &23< 2) :+,&+ &$1 %( )281' $7
KWWSV ZZZPDULFRSDJRY'RFXPHQW&HQWHU9LHZ
5(6321'(17 ),50 68%0,77,1*352326$/
)('(5$/7$;,'
35,17('1$0($1'7,7/(
$''5(66
7(/(3+21(
&,7<
67$7(
=,3
'$7(
:(%6,7(85/
(0$,/
0$5,&23$&2817<$5,=21$
%<
&+$,50$1%2$5'2)683(59,6256
'$7(
$77(67('
&/(5.2)7+(%2$5'
'$7(
$33529('$672)250
'(387<&2817<$77251(<
'$7(
$87+25,=('6,*1$785(
Cohda Wireless America LLC
Paul Gray, CEO
paul.gray@cohdawireless.com
450 E 96TH ST, OFC 5119 STE 500
Indianapolis IN
46240
cohdawireless.com
46-3504330
317 818 5595
November 29, 2025
f0a95036-38af-4452-8b42-
dd4e095ea50d
Digitally signed by f0a95036-38af-4452-8b42-
dd4e095ea50d
Date: 2025.11.29 14:31:58 +10'30'
SERIAL 260056-C
ETTIFOS INC., 4010 MOORPARK AVE STE 111, SAN JOSE, CA 95117
COMPANY NAME:
Ettifos Inc
DOING BUSINESS AS (dba):
Ettifos
MAILING ADDRESS:
4010 MOORPARK AVE, SUITE 111
SAN JOSE, CA 95117
REMIT TO ADDRESS:
4010 MOORPARK AVE, SUITE 111
SAN JOSE, CA 95117
TELEPHONE NUMBER:
(408) 247-1050
WWW ADDRESS:
https://www.ettifos.com/
CONTACT NAME:
Michael Kang
CONTACT TELEPHONE NUMBER:
+82-10-5912-8912
CONTACT EMAIL ADDRESS:
Michael.kang@ettifos.com
UNIQUE ENTITY IDENTIFIER (UEI):
QZ7ABF1B5PF1
YES
NO
REBATE
WILL ALLOW OTHER GOVERNMENTAL ENTITIES TO PURCHASE
FROM THIS CONTRACT:
X
WILL ACCEPT PROCUREMENT CARD FOR PAYMENT:
X
Central core of the Phoenix metro region encompassing areas of Phoenix, Avondale, Tolleson and
unincorporated Maricopa County.
Item Description
Unit of
Measure
Quantity
Unit
Price ($)
Bulk Price
Discount
Notes
On-Board Unit (OBU)
Hardware and
Configuration
On-Board
Unit
hardware
per unit
Each
1
3,065.83
51-100 units =
US$2,801.06 per
unit
101-500 units =
US$2,497.48 per
unit
Product
Name:
V2X-AIR
Product
Code: ETF-
AIR-C02
5 year
warranty
WARRANTY
Year
Unit of Measure
Quantity
Unit Price
Description
Year 6
Device
1
180
Please refer to "Warranty Administration Plan -
OBU_Ettifos.pdf" for Warranty coverage
Year 7
Device
1
215
Please refer to "Warranty Administration Plan -
OBU_Ettifos.pdf" for Warranty coverage
Year 8
Device
1
260
Please refer to "Warranty Administration Plan -
OBU_Ettifos.pdf" for Warranty coverage
Year 9
Device
1
310
Please refer to "Warranty Administration Plan -
OBU_Ettifos.pdf" for Warranty coverage
SERIAL 260056-C
ETTIFOS INC
Please provide discount off catalog of products with current pricing. You may upload a separate
document for catalog style. The catalog must have Unit Price, Percent Discount, Effective Date, and
Product Name or Product Description. Contractor must list catalogs encompassing the scope of
items/commodities offered for sale by/through that respondent. Contractor are strongly
encouraged to list any other additional pricing caveats separately (such as volume discounts, or
discounts by item type or category).
Product
Code (If
applicable)
Product
Name or
Product
Description
Manufacturer
Quantity
Unit Price
Percent
Discount From
Catalog
Additional
notes
ETF-AIR-
C02
V2X-AIR
Ettifos Inc.
1
3,065.83
See "Bulk Price
Discount" details
above
On-board
Unit (OBU)
PRICING SHEET: NIGP CODE 55080
Terms:
NET 30 DAYS
Vendor Number
VS0000011388
Certificates of Insurance
Required
Contract Period:
To cover the period ending January 31, 2028.
$77$&+0(17% $*5((0(173$*(
5HVSRQGHQWKHUHE\FHUWLILHVWKDWUHVSRQGHQWKDVUHDGXQGHUVWDQGVDQGDJUHHVWKDWDFFHSWDQFHE\0DULFRSD&RXQW\
RIWKHUHVSRQGHQW¶VRIIHUZLOOFUHDWHDELQGLQJFRQWUDFW5HVSRQGHQWDJUHHVWRIXOO\FRPSO\ZLWKDOOWHUPVDQGFRQGLWLRQV
DVVHWIRUWKLQWKH0DULFRSD&RXQW\3URFXUHPHQW&RGHDQGDPHQGPHQWVWKHUHWRWRJHWKHUZLWKWKHVSHFLILFDWLRQVDQG
RWKHUGRFXPHQWDU\IRUPVKHUHZLWKPDGHDSDUWRIWKLVVSHFLILFDJUHHPHQW
%<6,*1,1*7+,63$*(7+(68%0,77,1*5(6321'(17&(57,),(67+$75(6321'(17+$65(9,(:('
0$5,&23$ &2817<¶6 ³67$1'$5' 7(506 $1' &21',7,216´ $ &23< 2) :+,&+ &$1 %( )281' $7
KWWSV ZZZPDULFRSDJRY'RFXPHQW&HQWHU9LHZ
5(6321'(17 ),50 68%0,77,1*352326$/
)('(5$/7$;,'
35,17('1$0($1'7,7/(
$''5(66
7(/(3+21(
&,7<
67$7(
=,3
'$7(
:(%6,7(85/
(0$,/
0$5,&23$&2817<$5,=21$
%<
&+$,50$1%2$5'2)683(59,6256
'$7(
$77(67('
&/(5.2)7+(%2$5'
'$7(
$33529('$672)250
'(387<&2817<$77251(<
'$7(
$87+25,=('6,*1$785(
7(
7+25,=(' 6,*1$785(
Ettifos Inc.
Michael Kang / North America Sales Representative
michael.kang@ettifos.com
4010 MOORPARK AVE, SUITE 111
San Jose CA
95117
https://www.ettifos.com/
33-1502780
(408) 247-1050
10/6/2025
SERIAL 260056-C
KAPSCH TRAFFICCOM USA INC., 8201 GREENSBORO DRIVE, SUITE 1002, MCLEAN, VA 22102
COMPANY NAME:
Kapsch TrafficCom USA, Inc.
DOING BUSINESS AS (dba):
Kapsch TrafficCom USA, Inc.
MAILING ADDRESS:
2855 Premiere Parkway Suite F Duluth GA 30097
REMIT TO ADDRESS:
2855 Premiere Parkway Suite F Duluth GA 30097
TELEPHONE NUMBER:
470.473.6400
WWW ADDRESS:
www.kapsch.net/us
CONTACT NAME:
Lauri Brady
CONTACT TELEPHONE NUMBER:
602.317.7175
CONTACT EMAIL ADDRESS:
Lauri.Brady@kapsch.net
UNIQUE ENTITY IDENTIFIER (UEI)
FBKPFMK8PMY5
YES
NO
REBATE
WILL ALLOW OTHER GOVERNMENTAL ENTITIES TO PURCHASE
FROM THIS CONTRACT:
X
WILL ACCEPT PROCUREMENT CARD FOR PAYMENT:
X
Central core of the Phoenix metro region encompassing areas of Phoenix, Avondale, Tolleson and
unincorporated Maricopa County.
Item
Description
Unit of
Measure
Quantity
Unit Price
($)
Bulk Price
Discount
Notes
Roadside
Unit (RSU)
Hardware
and
Configuration
Roadside
Unit
hardware
per unit
Each
1
$3,917.00
See "Volume
Pricing
(Discounted)"
Worksheet
The unit price for each item
is inclusive of all costs
associated with hardware
equipment, delivery,
configuration support,
testing, training, and
warranty. Specifically
accounts for:
• Unit pricing based on the
inclusion of all components
that comprise a Kapsch
RIS-9360-Q000 RSU Kit.
• Extended manufacturer 5-
year warranty.
• Additional 6.3% sales tax
(based on a 0.7% state tax
and a 5.6% county tax).
Pricing for the individual
parts is included separately
in the catalog below.
SERIAL 260056-C
KAPSCH TRAFFICCOM USA INC
WARRANTY
Year
Unit of
Measure
Quantity
Unit Price
Description
Year 6
Each
1
$195.86
Optional extended warranty for Years 6–9 priced
at 5% of the total hardware equipment price
(assumes 1 RSU KIT inclusive of all required
accessories per the catalog below) at time of
procurement. Rate is fixed (non-escalating) and
provides the same coverage as the initial 5-year
term. Warranty pricing will vary proportionally
based on the number of units procured.
Annual warranty for a Kapsch RIS-9360-Q000
RSU Kit is approximately $178.05.
Year 7
Each
1
$195.86
Year 8
Each
1
$195.86
Year 9
Each
1
$195.86
Please provide discount off catalog of products with current pricing. You may upload a separate document for
catalog style. The catalog must have Unit Price, Percent Discount, Effective Date, and Product Name or Product
Description. Contractor must list catalogs encompassing the scope of items/commodities offered for sale
by/through that respondent. Contractor are strongly encouraged to list any other additional pricing caveats
separately (such as volume discounts, or discounts by item type or category).
Note 1: All pricing for the products listed in the following catalog includes a 6.3% sales tax (based on a 0.7% state tax
and a 5.6% county tax). Delivery to zip codes within the Chandler city limit will incur an additional city sales tax of 1.5%.
Product
Code (If
applicable)
Product Name
or Product
Description
Manufacturer
Quantity
Unit
Price
Percent
Discount
From
Catalog
Additional notes
Roadside Unit (RSU) Hardware
RIS-9360-Q000
- KIT (5-Year
Warranty)
Kapsch
1
$3,917.00
See "Volume
Pricing
(Discounted)"
Worksheet
9360 RSU KIT –
Includes (1) Kapsch
RIS-9360 Roadside
Unit, (1) PoE injector,
(2) white stick V2X
antennas, (1)
“mushroom”
GNSS/GPS antenna, (1
set) of RSU mounting
bracket components
(x3), and (2) U-bolts for
pole installation.
Includes extended
manufacturer five-year
warranty.
Additional volume-
based kit pricing at
various tax levels
(including tax exempt)
can be found in the
accompanying
worksheet.
SERIAL 260056-C
KAPSCH TRAFFICCOM USA INC
RIS-9360-Q000
Device
Kapsch
1
$3,229.61 Note 2: All
pricing for
individual
components
includes
extended
five-year
manufacturer
warranty, at
no additional
cost to client.
If required,
extended,
multi-year
warranty
coverage for
six years or
more will
need to
priced
separately at
the time of
procurement.
9360 RSU Device
POE
INJECTOR,
30W Adapter.
AC/DC IN-10G,
power cord
Procet
1
$175.40
PoE Injector
Omni-directional
5.9 GHz
Broadband
Antenna
MobileMark
or GTT
Wireless
1
$144.91
White Stick
Antenna - 2
required
ANTENNA,
GPS/GLONASS,
1.57542 - 1.602
GHz, 28.1dBi
GTT
Wireless
1
$93.80
"Mushroom" GPS
Antenna
Mounting
Bracket: RSU
Backplate
Kapsch
1
$51.19
RSU mounting
bracket
Component
Mounting
Bracket: RSU
Saddle Bracket
Kapsch
1
$35.75
RSU mounting
bracket
Component
Mounting
Bracket: RSU
Washer Plate
Kapsch
1
$15.07
RSU mounting
bracket
Component
U-BOLT, 304SS,
5/16" TH, 3.31"x
3.5"x .5" (EACH)
Kapsch
1
$13.27
U-bolt with nuts -
(mounting bracket
Component) - 2
required
Volume Pricing (Discounted) - 9360 RSU KIT
Discount
7%
10%
12%
16%
20%
RSUs
Kapsch Part
Number
Quantities
1-10
11-25
26-50
51-100
101-250
251+
RIS-9360 (Tax Exempt)
34034343001
$3,670
$3,413
$3,303
$3,230
$3,083
$2,936
RIS-9360 (includes 6.3%
Sales Tax)
34034343001
$3,917
$3,643
$3,525
$3,447
$3,290
$3,134
RIS-9360 (includes 7.8%
Sales Tax)
34034343001
$4,223
$3,927
$3,801
$3,716
$3,547
$3,378
Note 1: All RSU Kit prices shown in this volume-based, discounted pricing table are fully inclusive of the
required five (5)-year warranty, as specified in the solicitation. Pricing includes all costs for delivery, testing,
configuration support, mounting hardware, and warranty coverage through Year 5. No additional charges apply
for warranty during this initial five-year term.
Note 2: Volume-based pricing has been provided for three different tax levels:
(a) tax exempt;
(b) 6.3% sales tax [based on a 0.7% state tax and a 5.6% county tax]; and
(c) 7.8% sales tax [based on a 07.% state tax, a 5.6% county tax, and a 1.5% city tax for delivery within the
Chandler city limit].
SERIAL 260056-C
KAPSCH TRAFFICCOM USA INC
PRICING SHEET: NIGP CODE 55080
Terms:
NET 30 DAYS
Vendor Number
VS0000001554
Certificates of Insurance
Required
Contract Period:
To cover the period ending January 31, 2028.
$77$&+0(17% $*5((0(173$*(
5HVSRQGHQWKHUHE\FHUWLILHVWKDWUHVSRQGHQWKDVUHDGXQGHUVWDQGVDQGDJUHHVWKDWDFFHSWDQFHE\0DULFRSD&RXQW\
RIWKHUHVSRQGHQW¶VRIIHUZLOOFUHDWHDELQGLQJFRQWUDFW5HVSRQGHQWDJUHHVWRIXOO\FRPSO\ZLWKDOOWHUPVDQGFRQGLWLRQV
DVVHWIRUWKLQWKH0DULFRSD&RXQW\3URFXUHPHQW&RGHDQGDPHQGPHQWVWKHUHWRWRJHWKHUZLWKWKHVSHFLILFDWLRQVDQG
RWKHUGRFXPHQWDU\IRUPVKHUHZLWKPDGHDSDUWRIWKLVVSHFLILFDJUHHPHQW
%<6,*1,1*7+,63$*(7+(68%0,77,1*5(6321'(17&(57,),(67+$75(6321'(17+$65(9,(:('
0$5,&23$ &2817<¶6 ³67$1'$5' 7(506 $1' &21',7,216´ $ &23< 2) :+,&+ &$1 %( )281' $7
KWWSV ZZZPDULFRSDJRY'RFXPHQW&HQWHU9LHZ
5(6321'(17 ),50 68%0,77,1*352326$/
)('(5$/7$;,'
35,17('1$0($1'7,7/(
$''5(66
7(/(3+21(
&,7<
67$7(
=,3
'$7(
:(%6,7(85/
(0$,/
0$5,&23$&2817<$5,=21$
%<
&+$,50$1%2$5'2)683(59,6256
'$7(
$77(67('
&/(5.2)7+(%2$5'
'$7(
$33529('$672)250
'(387<&2817<$77251(<
'$7(
$87+25,=('6,*1$785(
(
+25,=('6,*1$785(
Kapsch TrafficCom USA, Inc.
Lauri Brady, Vice President, Sales and Business Development
Lauri.Brady@kapsch.net
2855 Premiere Parkway, Suite F
Duluth GA
30097
www.kapsch.net/us
16-1317836
602.317.7175
12/1/25
SERIAL 260056-C
SONAMORE, INC DBA: P3MOBILITY, 330 LIBERTY ST, ANN ARBOR, MI 48104
COMPANY NAME:
Sonamore, Inc
DOING BUSINESS AS (dba):
P3Mobility
MAILING ADDRESS:
330 LIBERTY ST, ANN ARBOR, MI 48104
REMIT TO ADDRESS:
13400 SE Fletcher RD, Dayton OR 87114
TELEPHONE NUMBER:
734-276-4850
WWW ADDRESS:
www.p3mobility.com
CONTACT NAME:
Jeremy Ward
CONTACT TELEPHONE NUMBER:
708-268-1526
CONTACT EMAIL ADDRESS:
Jeremy.ward@p3mobility.com
UNIQUE ENTITY IDENTIFIER (UEI):
L8BYXDTMKQ59
YES
NO
REBATE
WILL ALLOW OTHER GOVERNMENTAL ENTITIES TO PURCHASE
FROM THIS CONTRACT:
X
WILL ACCEPT PROCUREMENT CARD FOR PAYMENT:
X
Central core of the Phoenix metro region encompassing areas of Phoenix, Avondale, Tolleson and
unincorporated Maricopa County.
Item
Description
Unit of
Measure
Quantity
Unit
Price
($)
Bulk Price
Discount
Notes
Roadside
Processor
(RSP) Software
and
Configuration
Roadside
Processor
Software
Each
1
$6,546
Additional price
per additional unit
at bulk quantities
Units 11-50 =
$4,909.50 per unit
Units 51-250 =
$3,273.00 per unit
Units 251-650 =
$1,091.00 per unit
Units 651-1,000 =
$545.50 per unit
(Annual Software
License Price)
Example for 650
units:
10 units at
$6,546.00 =
$65,460.00
40 units at
$4,909.50 =
$196,380.00
200 unit at
$3,273.00 =
$654,600.00
400 unit at
$1,091.00 =
$436,400.00
Total =
$1,352,840 per
year in year 1 and
2
$676,420 per year
for years 3 to 6
(50% discount)
Minimum quantity is 20.
Pricing is for one year of
software license. Years 1 and
2 at 0% discount. Years 3 to
6 includes a 50% discount.
Warranty is provided for
duration of software license
period.
Includes cost share for
USDOT.
Renewal discount may
increase based on a revenue
share agreement with
MCDOT (or other relevant
partner).
Includes supporting
documentation and training
as referenced in the Training
Plan.
Lead time < 1 week from
receipt of PO.
Standard software licensing
terms apply.
Price includes Transaction
Privilege Tax of 9.1%. Tax
will be removed from price
upon receipt of Arizona Form
5000 TPT Exemption
Certificate.
SERIAL 260056-C
SONAMORE, INC DBA: P3MOBILITY
PRICING SHEET: NIGP CODE 55080
Terms:
NET 30 DAYS
Vendor Number
VS0000009457
Certificates of Insurance
Required
Contract Period:
To cover the period ending January 31, 2028.
$77$&+0(17% $*5((0(173$*(
5HVSRQGHQWKHUHE\FHUWLILHVWKDWUHVSRQGHQWKDVUHDGXQGHUVWDQGVDQGDJUHHVWKDWDFFHSWDQFHE\0DULFRSD&RXQW\
RIWKHUHVSRQGHQW¶VRIIHUZLOOFUHDWHDELQGLQJFRQWUDFW5HVSRQGHQWDJUHHVWRIXOO\FRPSO\ZLWKDOOWHUPVDQGFRQGLWLRQV
DVVHWIRUWKLQWKH0DULFRSD&RXQW\3URFXUHPHQW&RGHDQGDPHQGPHQWVWKHUHWRWRJHWKHUZLWKWKHVSHFLILFDWLRQVDQG
RWKHUGRFXPHQWDU\IRUPVKHUHZLWKPDGHDSDUWRIWKLVVSHFLILFDJUHHPHQW
%<6,*1,1*7+,63$*(7+(68%0,77,1*5(6321'(17&(57,),(67+$75(6321'(17+$65(9,(:('
0$5,&23$ &2817<¶6 ³67$1'$5' 7(506 $1' &21',7,216´ $ &23< 2) :+,&+ &$1 %( )281' $7
KWWSV ZZZPDULFRSDJRY'RFXPHQW&HQWHU9LHZ
5(6321'(17 ),50 68%0,77,1*352326$/
)('(5$/7$;,'
35,17('1$0($1'7,7/(
$''5(66
7(/(3+21(
&,7<
67$7(
=,3
'$7(
:(%6,7(85/
(0$,/
0$5,&23$&2817<$5,=21$
%<
&+$,50$1%2$5'2)683(59,6256
'$7(
$77(67('
&/(5.2)7+(%2$5'
'$7(
$33529('$672)250
'(387<&2817<$77251(<
'$7(
$87+25,=('6,*1$785(
Sonamore, Inc.
Jeremy Ward, VP of Operations
jeremy.ward@p3mobility.com
330 E Liberty St
Ann Arbor
Michigan
48104
p3mobility.com
83-2298928
708-268-1526
11/25/2025
SERIAL 260056-C
WESTERN SYSTEMS INC, 1122 INDUSTRY STREET, BUILDING B, EVERETT, WA 98203
COMPANY NAME:
Western Systems Inc.
DOING BUSINESS AS (dba):
MAILING ADDRESS:
1122 Industry Street, Bldg B. Everett, WA 98203
REMIT TO ADDRESS:
1122 Industry Street, Bldg B. Everett, WA 98203
TELEPHONE NUMBER:
425.438.1133
WWW ADDRESS:
https://www.westernsystems-inc.com/
CONTACT NAME:
Joe Marioni
CONTACT TELEPHONE NUMBER:
480.487.3657
CONTACT EMAIL ADDRESS:
jmarioni@westernsystems-inc.com
UNIQUE ENTITY IDENTIFIER (UEI)
K4P8GJXDUMN4
YES
NO
REBATE
WILL ALLOW OTHER GOVERNMENTAL ENTITIES TO PURCHASE
FROM THIS CONTRACT:
X
WILL ACCEPT PROCUREMENT CARD FOR PAYMENT:
X
Central core of the Phoenix metro region encompassing areas of Phoenix, Avondale, Tolleson and
unincorporated Maricopa County.
Item Description
Unit of
Measure
Quantity
Unit Price ($)
Bulk Price Discount
Roadside Unit
(RSU) Hardware
and Configuration
Roadside Unit
hardware per unit
Each
1
$4,502.25
See Catalog Pricing
Below
Roadside Processor
(RSP) Hardware
Roadside
Processor
hardware
Each
1
$4,765.35
See Catalog Pricing
Below
Roadside Processor
(RSP) Software and
Configuration
Roadside
Processor
Software
Each
1
Included in
RSP
Hardware
Price
On-Board Unit
(OBU) Hardware
and Configuration
On-Board Unit
hardware per unit
Each
1
$4,261.80
See Catalog Pricing
WARRANTY
Year
Unit of
Measure
Quantity
Unit Price
Description
Year 6
Each
1
$294.12
RSU - See pricing below
Year 7
Each
1
$294.12
RSU - See pricing below
Year 8
Each
1
$294.12
RSU - See pricing below
SERIAL 260056-C
WESTERN SYSTEMS INC
Year 9
Each
1
$294.12
RSU - See pricing below
Year 6
Each
1
$440.74
RSP HW/SW
Year 7
Each
1
$661.11
RSP HW/SW
Year 8
Each
1
$881.47
RSP HW/SW
Year 9
Each
1
$1,101.84 RSP HW/SW
Year 6
Each
1
$676.47
OBU
Year 7
Each
1
$800.00
OBU
Year 8
Each
1
$923.53
OBU
Year 9
Each
1
$1,047.06 OBU
Please provide discount off catalog of products with current pricing. You may upload a
separate document for catalog style. The catalog must have Unit Price, Percent Discount,
Effective Date, and Product Name or Product Description. Contractor must list catalogs
encompassing the scope of items/commodities offered for sale by/through that
respondent. Contractor are strongly encouraged to list any other additional pricing
caveats separately (such as volume discounts, or discounts by item type or category).
Product
Code (If
applicable)
Product Name or
Product
Description
Manufacturer
Quantity Unit Price
Percent
Discount
From
Catalog
Additional
notes
8830010600
On-Board Unit
(OBU) Hardware
and Configuration
DENSO
1-100
$4,261.80
8830010600
On-Board Unit
(OBU) Hardware
and Configuration
DENSO
101-200
$3,927.90
8830010600
On-Board Unit
(OBU) Hardware
and Configuration
DENSO
201-400
$3,732.20
8830010600
On-Board Unit
(OBU) Hardware
and Configuration
DENSO
401+
$3,469.80
8830010102
ROADSIDE UNIT
(RSU) HARDWARE
AND
CONFIGURATION
YUNEX
1-100
$4,502.25
8830010102
ROADSIDE UNIT
(RSU) HARDWARE
AND
CONFIGURATION
YUNEX
101-200
$4,267.65
8830010102
ROADSIDE UNIT
(RSU) HARDWARE
AND
CONFIGURATION
YUNEX
201-400
$3,944.50
8830010102
ROADSIDE UNIT
(RSU) HARDWARE
AND
CONFIGURATION
YUNEX
401+
$3,621.35
SERIAL 260056-C
WESTERN SYSTEMS INC
8812500182
Roadside Processor
(RSP) Hardware,
Software and
Configuration
MH Corbin
1-100
$4,765.35
8812500182
Roadside Processor
(RSP) Hardware,
Software and
Configuration
MH Corbin
101-200
$4,652.96
8812500182
Roadside Processor
(RSP) Hardware,
Software and
Configuration
MH Corbin
201-400
$4,540.58
8812500182
Roadside Processor
(RSP) Hardware,
Software and
Configuration
MH Corbin
401+
$4,428.19
YUNEX RSU
Extended Warranty
Yunex
1-100
$294.12
Price per
device
based on
number of
devices
deployed at
the start of
each
warranty
years 6-9
YUNEX RSU
Extended Warranty
Yunex
101-200
$235.29
YUNEX RSU
Extended Warranty
Yunex
201-400
$176.47
YUNEX RSU
Extended Warranty
Yunex
401+
$117.65
Submitting Respondent Name:___Western Systems_-_Alternate Bid____
Item Description
Unit of
Measure
Quantity
Unit
Price ($)
Bulk Price
Discount
Notes
Roadside Unit
(RSU) Hardware
and Configuration
Roadside
Unit
hardware
per unit
Each
1
$5,807.60
See Catalog
pricing
below
RSU to run RSP
Software
natively. See
included
datasheets for
alternate
architecture.
On-Board Unit
(OBU) Hardware
and Configuration
On-Board
Unit
hardware
per unit
Each
1
$4,261.80
See Catalog
pricing
below
WARRANTY
Year
Unit of Measure
Quantity
Unit Price
Description
Year 6
Each
1
$294.12
RSU
Year 7
Each
1
$294.12
RSU
Year 8
Each
1
$294.12
RSU
Year 9
Each
1
$294.12
RSU
Year 6
Each
1
$676.47
OBU
SERIAL 260056-C
WESTERN SYSTEMS INC
Year 7
Each
1
$800.00
OBU
Year 8
Each
1
$923.53
OBU
Year 9
Each
1
$1,047.06
OBU
Please provide discount off catalog of products with current pricing. You may upload a separate
document for catalog style. The catalog must have Unit Price, Percent Discount, Effective Date, and
Product Name or Product Description. Contractor must list catalogs encompassing the scope of
items/commodities offered for sale by/through that respondent. Contractor are strongly encouraged
to list any other additional pricing caveats separately (such as volume discounts, or discounts by
item type or category).
Product
Code (If
applicable)
Product Name or
Product Description
Manufacturer
Quantity
Unit Price
Percent
Discount
From
Catalog
Additional
notes
8830010600
On-Board Unit (OBU)
Hardware and
Configuration
DENSO
1-100
$4,261.80
8830010600
On-Board Unit (OBU)
Hardware and
Configuration
DENSO
101-200
$3,927.90
8830010600
On-Board Unit (OBU)
Hardware and
Configuration
DENSO
201-400
$3,732.20
8830010600
On-Board Unit (OBU)
Hardware and
Configuration
DENSO
400+
$3,469.80
8830010106
ROADSIDE UNIT
(RSU) HARDWARE,
CONFIGURATION,
AND RSP
SOFTWARE
YUNEX
1-100
$5,807.60
8830010106
ROADSIDE UNIT
(RSU) HARDWARE,
CONFIGURATION,
AND RSP
SOFTWARE
YUNEX
101-200
$5,277.66
8830010106
ROADSIDE UNIT
(RSU) HARDWARE,
CONFIGURATION,
AND RSP
SOFTWARE
YUNEX
201-400
$4,572.00
8830010106
ROADSIDE UNIT
(RSU) HARDWARE,
CONFIGURATION,
AND RSP
SOFTWARE
YUNEX
400+
$4,042.80
YUNEX RSU
Extended Warranty
Yunex
1-100
$294.12
Price per
device
based on
number of
devices
deployed
at the start
of each
warranty
years 6-9
YUNEX RSU
Extended Warranty
Yunex
101-200
$235.29
YUNEX RSU
Extended Warranty
Yunex
201-400
$176.47
YUNEX RSU
Extended Warranty
Yunex
401+
$117.65
SERIAL 260056-C
WESTERN SYSTEMS INC
PRICING SHEET: NIGP CODE 55080
Terms:
NET 30 DAYS
Vendor Number
VS0000009310
Certificates of Insurance
Required
Contract Period:
To cover the period ending January 31, 2028.
$77$&+0(17% $*5((0(173$*(
5HVSRQGHQWKHUHE\FHUWLILHVWKDWUHVSRQGHQWKDVUHDGXQGHUVWDQGVDQGDJUHHVWKDWDFFHSWDQFHE\0DULFRSD&RXQW\
RIWKHUHVSRQGHQW¶VRIIHUZLOOFUHDWHDELQGLQJFRQWUDFW5HVSRQGHQWDJUHHVWRIXOO\FRPSO\ZLWKDOOWHUPVDQGFRQGLWLRQV
DVVHWIRUWKLQWKH0DULFRSD&RXQW\3URFXUHPHQW&RGHDQGDPHQGPHQWVWKHUHWRWRJHWKHUZLWKWKHVSHFLILFDWLRQVDQG
RWKHUGRFXPHQWDU\IRUPVKHUHZLWKPDGHDSDUWRIWKLVVSHFLILFDJUHHPHQW
%<6,*1,1*7+,63$*(7+(68%0,77,1*5(6321'(17&(57,),(67+$75(6321'(17+$65(9,(:('
0$5,&23$ &2817<¶6 ³67$1'$5' 7(506 $1' &21',7,216´ $ &23< 2) :+,&+ &$1 %( )281' $7
KWWSV ZZZPDULFRSDJRY'RFXPHQW&HQWHU9LHZ
5(6321'(17 ),50 68%0,77,1*352326$/
)('(5$/7$;,'
35,17('1$0($1'7,7/(
$''5(66
7(/(3+21(
&,7<
67$7(
=,3
'$7(
:(%6,7(85/
(0$,/
0$5,&23$&2817<$5,=21$
%<
&+$,50$1%2$5'2)683(59,6256
'$7(
$77(67('
&/(5.2)7+(%2$5'
'$7(
$33529('$672)250
'(387<&2817<$77251(<
'$7(
$87+25,=('6,*1$785(
Western Systems Inc
Zach Hoiting - Senior Vice President
zhoiting@westernsystems-inc.com
1122 Industry Street, Bldg B
Everett WA
98203
www.westernsystems-inc.com
91-2099547
425.438.1133
11/26/2025
Zach Hoiting
Digitally signed by Zach Hoiting
Date: 2025.11.26 15:33:39 -08'00'
SERIAL 260056-C
ROADSIDE UNIT AND ONBOARD UNIT DEVICES (CVAZ)
1.0
INTENT
1.1
The intent of this Invitation for Bids (IFB) is to establish sources for the procurement,
configuration, and delivery of Connected Vehicle (CV) equipment to support Maricopa
County Department of Transportation's (MCDOT) Connected Vehicle Acceleration Zone
(CVAZ) initiative. This solicitation will include procuring Roadside Units (RSU), Roadside
Processors (RSP), and On-Board Units (OBU).
1.2
Other governmental entities under agreement with Maricopa County (County) may have
access to services provided hereunder (see also Sections 3.21 and 3.22 below).
1.3
The County reserves the right to add additional contractors, at the County’s sole discretion,
in cases where the currently listed contractors are of an insufficient number or skill set to
satisfy the County’s needs or to ensure adequate competition on any project or task order
work.
1.4
The County reserves the right to award this contract to multiple vendors. The County
reserves the right to award in whole or in part, by item or group of items, by section or
geographic area, or make multiple awards, where such action serves the County’s best
interest.
2.0
SPECIFICATIONS
2.1
BACKGROUND INFORMAITON
2.1.1
Location of Work: MCDOT CVAZ is focused on the central core of the Phoenix
metropolitan region, targeting the jurisdictions of Phoenix, Tolleson, Avondale,
parts of unincorporated Maricopa County, as well as along Grand Avenue/US60.
Emergency Vehicle Preemption (EVP), Transit Signal Priority (TSP), Vulnerable
Road User (VRU) Safety, and Freight Signal Priority (FSP) Vehicle-to-Everything
(V2X) applications will be supported. EVP intersections are located along major
thoroughfares, which are generally spaced at one-mile increments within the
regional street network. TSP routes include those with a high level of intersection
delay and highest ridership routes (greater than 2,000 daily riders) where there are
visual gaps at signalized intersections. Additional TSP locations are along Grand
Avenue, an important express bus route along US60. VRU intersections are based
on the Maricopa Association of Government’s (MAG) list of top 100 intersections
in the Phoenix metropolitan area for crash risk.
2.1.2
FSP intersections are those along local and regionally significant freight corridors,
as identified by the MAG 2017 regional freight study.
2.2
GENERAL REQUIREMENTS
2.2.1
The contractor may submit for one or more of the following items in technical
specifications (RSU, RSP Hardware, RSP Software, or OBU).
2.2.2
All contractors that submit a bid by agrees that all parts, components and
equipment, supplied will comply to Buy America/Build America (BABA)
requirements. If the County purchases any equipment that is later determined not
to meet BABA requirements, the contractor shall fully reimburse the County for the
cost of the equipment.
SERIAL 260056-C
2.2.3
Warranty Requirements
2.2.3.1
All items furnished under this contract shall conform to the requirements
of this solicitation and be free from defects in design, materials, and
workmanship.
2.2.3.2
The warranty period shall be a minimum of five years and shall
commence upon written acceptance by the County following successful
delivery, installation, and testing.
2.2.3.3
The contractor shall indicate on the pricing sheet the duration of the
warranty and any applicable limitations or conditions.
2.2.3.4
The contractor agrees, at its own expense, to provide all labor and parts
required to remove, repair, and replace any defective workmanship or
materials identified during the warranty period.
2.2.3.5
The contractor shall guarantee that all equipment supplied complies with
all applicable regulations.
2.2.4
Training
2.2.4.1
When required, training shall be provided by the contractor in multiple
sessions.
2.2.4.2
Contractor shall submit a training plan with their proposal.
2.2.4.3
The first training session shall be for maintenance and troubleshooting.
This session shall be a minimum of eight hours in length for each type
of field device installed, including communications. This session shall be
oriented for the County maintenance staff.
2.2.4.4
The second training session shall be for operations. This session shall
be a minimum of eight hours in length for each type of field device
installed. This session shall be oriented for the County Traffic
Management staff.
2.2.5
Payment
2.2.5.1
The unit price for each item shall be inclusive of all costs associated with
delivery, testing, warranty, documentation, training, mounting hardware,
and configuration support. No additional charges will be allowed unless
expressly authorized by the County in writing.
2.2.5.2
All equipment delivered shall be subject to County inspection and
preliminary acceptance prior to installation and testing.
2.2.5.3
Payment for configuration support and testing labor shall be made only
upon successful demonstration that the delivered equipment is fully
operational and functions in accordance with the specifications.
2.2.5.4
Final payment for each item shall be made only after the item has been
successfully installed, properly configured, and has passed County
testing with verification of full functionality
SERIAL 260056-C
2.3
TECHNICAL SPECIFICATIONS
2.3.1
Roadside Units (RSUs):
2.3.1.1
RSUs shall come equipped with antennas, Power-over-Ethernet
adaptors\injectors, mounting brackets and hardware, and any other
ancillary components required for complete installation and operation.
2.3.1.2
After the RSUs are installed, the RSU supplier shall assist MCDOT and
the project team with configuring.
2.3.1.3
RSUs shall be configured to sign, and broadcast Signal Phase and
Timing (SPaT) and Map Data (MAP), based in J4501.
2.3.1.4
RSUs shall be configured to sign and broadcast Society of Automotive
Engineers (SAE) J2735 Signal Status Message (SSMs).
2.3.1.5
RSUs shall be configured to sign and broadcast SAE J3224 Sensor
Data Sharing Messages (SDSM).
2.3.1.6
RSUs shall be configured to sign and broadcast Institute of Electrical
and Electronics (IEEE) WAVE Service Advertisements (WSAs) as
defined in the RSU.
2.3.1.7
RSUs shall be configured to verify and forward SAE J2735 Basic Safety
Message (BSMs) and Signal Request Message (SRMs) to the roadside
processor.
2.3.1.8
All RSUs components, configuration, and installation may meet or
exceed the requirements contained in the RSU Requirements Table.
RSU REQUIREMENTS
Requirement ID
Description
Roadside Unit Functional Requirements
RSU-FR-001-v1.0
An RSU shall have California Test Interval
(CTI) 4001 "immediate forward" capability.
RSU-FR-002-v1.0
An RSU shall have CTI 4001 "store and
repeat" capability.
RSU-FR-003-v1.0
An RSU shall have CTI 4001 "message
forwarding" capability.
RSU-FR-004-v1.0
An RSU shall be configurable.
RSU-FR-005-v1.0
The RSU shall allow the user to configure
parameters to generate the WSA.
RSU-FR-006-v1.0
An RSU should forward the IEEE 1609.3 WSA
to the CVAZ Message Exchange Platform, per
NTCIP 1218.
RSU-FR-007-v1.0
An RSU shall provide the RSU status to the
V2X management system, per NTCIP 1218.
RSU-FR-008-v1.0
An RSU shall operate on the upper 30-
megahertz (MHz) of the 5.9 gigahertz (GHz)
(5.895-5.925 GHz) safety band.
RSU-FR-009-v1.0
An RSU shall be capable of supporting both
10 and 20 MHz channel in one mode or the
other, NOT simultaneously
SERIAL 260056-C
RSU REQUIREMENTS
Requirement ID
Description
RSU-FR-010-v1.0
An RSU shall support National Transportation
Communications for Intelligent Transportation
System Protocol (NTCIP) 1218v1.038 for
diagnostic and health monitoring functions.
RSU-FR-011-v1.0
An RSU shall support remote login such that
an authorized device administrator can modify
configuration settings (through Secure Shell
(SSH) and V2X Management System).
RSU-FR-012-v1.0
An RSU shall support remote firmware
updates (through SSH and V2X Management
System).
RSU-FR-013-v1.0
An RSU shall be compliant with mandatory
requirements in CTI 4001.
RSU-FR-014-v1.0
An RSU shall be compliant with IEEE
1609.2.1.
RSU-FR-015-v1.0
An RSU shall be compliant with IEEE 1609.3.
RSU-FR-016-v1.0
An RSU shall be compliant with SAE J3161/0
and Third Generation Partnership Project
(3GPP) 36.521-1.
RSU-FR-017-v1.0
An RSU shall be powered by an IEEE 802.3
AT Power over Ethernet (PoE) injector.
RSU-FR-018-v1.0
An RSU shall be compliant with applicable
sections of Title 47 of the Code of Federal
Regulations Part 15, Subpart C.
RSU-FR-019-v1.1
An RSU shall send status and monitoring data
to the V2X management system
Roadside Unit Interface Requirements
RSU-IR-001-v1.0
An RSU shall have at least one Ethernet
Registered Jack – 45 (RJ-45) port for network
connection.
RSU-IR-002-v1.0
An RSU shall support both Internet Protocol
version 4 (IPv4) and Internet Protocol version
6 (IPv6) network protocols over ethernet.
RSU-IR-003-v1.0
An RSU shall support all management through
the RJ-45 port.
RSU-IR-004-v1.0
An RSU shall communicate with the V2X
management system, data system, and other
systems and hardware using Simple Network
Management Protocol version 3 (SNMPv3).
RSU-IR-005-v1.0
An RSU shall utilize Global Positioning
System (GPS) for time synchronization.
RSU-IR-006-v1.0
An RSU shall communicate with the Security
Credential Management System (SCMS) over
an IPv4 network connection.
RSU-IR-008-v1.0
An RSU should support IPv6 tunneling over
IPv4.
RSU-IR-009-v1.0
An RSU should act as an IPv6 Gateway to
enable OBUs to request and download IEEE
1609.2 Certificates from MCDOTs SCMS.
SERIAL 260056-C
RSU REQUIREMENTS
Requirement ID
Description
RSU-IR-010-v1.0
An RSU shall broadcast SAE J2735 Radio
Technical Commission for Maritime (RTCM)
received from the Roadside Processor (RSP)
using the Immediate Forwarding functionality.
RSU-IR-011-v1.0
An RSU shall broadcast SAE J2735 SPaT
received from the RSP using the Immediate
Forwarding functionality.
RSU-IR-012-v1.0
An RSU shall broadcast SAE J2735 MAP
received from the RSP using the Immediate
Forwarding functionality.
RSU-IR-013-v1.0
An RSU shall broadcast J3224 SDSM
received from the RSP using the Immediate
Forwarding functionality.
RSU-IR-014-v1.0
An RSU shall broadcast J2735 SSM received
from the RSP using the Immediate Forwarding
functionality.
RSU-IR-015-v1.0
An RSU shall generate and broadcast IEEE
1609.3
Wireless
Access
in
Vehicular
Environment (WAVE) Service Advertisements
(WSA).
RSU-IR-016-v1.0
An RSU shall forward J2735 SRM to the RSP.
RSU-IR-017-v1.0
An RSU shall forward SAE J2735 messages,
including but not limited to SPaT, MAP, SSM,
Traveler Information Message (TIM), RTCM,
and SDSM that it broadcasts to multiple
external network hosts (e.g. V2X management
system, Data System.) per NTCIP 1218
RSU-IR-018-v1.0
An RSU shall forward SAE J2735 messages
received from nearby RSUs, including but not
limited to SPaT, MAP, SSM, TIM, RTCM, and
SDSM to multiple external network hosts (e.g.
RSP,
V2X
management
system,
Data
System.)
RSU-IR-019-v1.0
An RSU shall forward SAE J2735 messages
received from nearby OBUs, including but not
limited to BSM and SRM, to multiple external
network hosts (e.g. RSP, V2X management
system, Data System.)
RSU-IR-020-v1.0
An RSU shall be delivered with a National
Electrical Manufacturers Association (NEMA)
Technical Standard 2 (TS2) PoE, IEEE 802.3
AT, PoE injector.
RSU-IR-021-v1.0
An RSU shall receive location and time data
from Global Navigation Satellite System
(GNSS).
Roadside Unit Performance Requirements
RSU-PR-001-v1.0
The IEEE 1609.3 WSA shall reflect the current
service configuration.
RSU-PR-002-v1.0
The RSU shall broadcast the WSA once per
second.
RSU-PR-003-v1.0
An RSU shall broadcast between 9-11 J2735
MAP messages in a 10-second interval.
SERIAL 260056-C
RSU REQUIREMENTS
Requirement ID
Description
RSU-PR-004-v1.0
An RSU shall broadcast 90-110 J2735 SPaT
messages in a 10-second interval.
RSU-PR-005-v1.0
An RSU shall broadcast between 90-110
J2735 SSM messages in a 10-second interval
when conditions to broadcast SSM have been
met.
RSU-PR-006-v1.0
An RSU shall broadcast between 90-110
J3224 SDSM messages in a 10-second
interval when conditions to broadcast SDSM
have been met.
RSU-PR-007-v1.0
The system clock of an RSU shall be accurate
to within 10 milliseconds of the Universal Time
Coordinated (UTC) reference.
RSU-PR-008-v1.0
The RSU V2X message broadcast range shall
be sufficient to support priority application
requirements.
RSU-PR-009-v1.0
An RSU shall have an overall uptime greater
than 99 percent.
RSU-PR-010-v1.0
An RSU shall have a minimum of 64 Megabyte
(MB) Static Dynamic Radom Access Memory
(SDRAM).
RSU-PR-011-v1.0
An RSU shall have a minimum of a 500MHz
Central Processing Unit (CPU) speed.
RSU-PR-012-v1.0
An RSU shall be OmniAir certified for Cellular
Vehicle-to-Everything (C-V2X) Release 1 or
provide a letter from OmniAir stating the RSU
(make and model) is actively in the OmniAir
certification process.
RSU-PR-013-v1.0
An RSU shall have associated documentation
that indicate it has been tested at events such
as OmniAir Plugfests.
RSU-PR-014-v1.0
An RSU shall be time synchronized with other
system devices.
Roadside Unit Data Requirements
RSU-DR-001-v1.0
The IEEE 1609.3 WSA shall broadcast as
Provider Service Identifier (PSID) 0p80-07.
RSU-DR-002-v1.0
The IEEE 1609.3 WSA shall contain the SSM
PSID, 0pE0-00-00-15, to advertise the Signal
Priority service.
RSU-DR-003-v1.0
An IEEE 1609.3 WSA should contain the IPv6
Services PSID, 0pEF-FF-FF-FE, to advertise
the Internet Protocol (IP) Service.
RSU-DR-004-v1.0
An RSU should broadcast WSAs containing
WAVE
Routing
Advertisements
(WRA)
comprised of IPv6 network information to be
utilized by OBUs.
RSU-DR-005-v1.0
An RSU should support over-the-air IPv6
communications with OBUs.
Roadside Unit Security Requirements
RSU-SR-001-v1.0
All RSUs shall comply with IEEE 1609.2.
SERIAL 260056-C
RSU REQUIREMENTS
Requirement ID
Description
RSU-SR-01a-v1.0
An RSU shall be compliant with IEEE
1609.2.1.
RSU-SR-002-v1.0
All RSUs shall be provisioned with valid IEEE
1609.2 enrollment certificates (by the supplier)
prior to deployment.
RSU-SR-003-v1.0
An RSU shall sign all outgoing messages for
broadcast with a valid IEEE 1609.2 application
certificate.
RSU-SR-004-v1.0
An
RSU
shall
cease
transmission
of
messages if no valid IEEE 1609.2 application
certificates are available.
RSU-SR-005-v1.0
RSUs shall be capable of performing
certificate verification on received messages,
according to IEEE 1609.2.
RSU-SR-006-v1.0
An RSU shall reject V2X messages that fail
signature verification or are signed with
expired or revoked certificates.
RSU-SR-007-v1.0
RSUs should download and utilize the latest
Certificate Revocation List (CRL) from the
SCMS.
RSU-SR-008-v1.0
RSUs should reject all messages received
from any source listed on the current CRL.
RSU-SR-009-v1.0
An RSU shall have no more than two weeks of
IEEE 1609.2 application certificates loaded at
a time.
RSU-SR-010-v1.0
An RSU shall request to receive additional
IEEE 1609.2 application certificates at least
once per week from the SCMS.
RSU-SR-011-v1.0
An RSU shall implement IEEE 1609.2
certificate download and renewal processes
over
secure,
encrypted,
end-to-end
connections.
RSU-SR-012-v1.0
Access to an RSU shall be controlled using
role-based access control, ensuring users can
access only the functions necessary for their
role.
RSU-SR-013-v1.0
RSU user accounts shall be authenticated
using a unique username and a strong
password
meeting
National
Institute
of
Standards and Technology (NIST) SP 800-
63B guidelines (minimum length, complexity,
and password history requirements).
RSU-SR-014-v1.0
All RSUs shall be protected by network
firewalls that restrict inbound and outbound
traffic to only approved IP addresses and ports
necessary for system operations.
RSU-SR-015-v.10
An RSU shall utilize the national Certificate
Trust List (CTL ) to verify messages signed
with certificates from SCMS providers other
than the provider the RSU is enrolled in.
SERIAL 260056-C
2.3.2
Roadside Processors (RSPs) Hardware
2.3.2.1
RSPs shall come equipped with all necessary 120v power cables,
mounting brackets, and any other ancillary components required for
complete installation and operation.
2.3.2.2
RSPs for the CVAZ deployment may meet or exceed the hardware
requirements in RSP Hardware Requirements table.
RSP HARDWARE REQUIREMENTS
Requirement ID
Description
Roadside Processor Hardware Requirements
RSP-HW-001-v1.0
RSP shall support an operating temperature of -
29°F to 165°F (-34°C to 74°C).
RSP-HW-002-v1.0
RSP shall support operating Humidity up to 95
percent Relative Humidity (RH).
RSP-HW-003-v1.0
RSP shall have a Web Interface for control and
configuration
RSP-HW-004-v1.0
RSP at a minimum shall have Power, Single
Board Computer (SBC), Hard Disk Drive (HDD),
and Heartbeat light-emitting diode (LEDs).
RSP-HW-005-v1.0
RSP shall support 10V-36V, 6W of power.
RSP-HW-006-v1.0
RSP shall have a minimum of two Ethernet, two
USB, two RS-232, four RS-485, two Digital out,
two Analog input, one HDMI, Audio in, and Audio
out connectors.
RSP-HW-007-v1.0
RSP shall have a GPS receiver with external
antenna port.
RSP-HW-008-v1.0
RSP shall have a minimum of an Intel Core i3
Dual Core 1.7 GHz processor.
RSP-HW-009-v1.0
RSP shall have a minimum of 4GB of random-
access memory (RAM).
RSP-HW-0010-v1.0
RSP shall have a minimum hard drive size of
16GB SSD.
RSP-HW-0011-v1.0
RSP shall have an Operating System equivalent
to Ubuntu 16.04 Long-Term Support (LTS).
2.3.3
Roadside Processor (RSP) Software
2.3.3.1
Contractors shall furnish all required software to generate SPaT
messages, based on SAE J4501, SAE J2735 Signal Status Messages
(SSM), SAE J3224 SDMS, and SAE J2735 RTCM messages. The RSP
shall store SAE J2735 MAP messages. The RSP software shall send
SPaT, MAP, SDSM, and RTCM messages to the local RSU and Mobile
Edge Processor (MEP), as applicable, for broadcast. RSP software shall
send signal priority\preemption calls to the local traffic signal controller.
RSP software shall send SPaT, MAP, SSM, RTCM, SRM, BSMs, and
other V2X messages to the V2X Management System. RSP software
for the CVAZ deployment shall meet or exceed the requirements
contained In RSP requirement software table.
2.3.3.2
After installation, the responder shall assist MCDOT and the project
team with configuring RSP in deployment.
2.3.3.3
RSPs shall be configured to generate and send SPaT messages to the
local RSU and MEP.
SERIAL 260056-C
2.3.3.4
RSPs shall be configured to store and send MAP messages to the local
RSU and MEP.
2.3.3.5
RSPs shall be configured to generate and send SSMs to the local RSU
and MEP.
2.3.3.6
RSPs shall be configured to generate and send SDSMs to the local RSU
and MEP.
2.3.3.7
RSPs shall be configured to send signal priority\preemption calls to the
local traffic signal controller.
2.3.3.8
RSPs shall be configured to forward SPaT, MAP, SSM, RTCM, SRM,
BSMs, and other V2X messages to the V2X Management System.
2.3.3.9
RSP software for the CVAZ deployment may meet or exceed the
requirements contained in the Table below.
RSP SOFTWARE REQUIREMENTS
Requirement ID
Description
Roadside Processor Functional Requirements
RSP-FR-001-v1.0
An RSP shall generate J2735 RTCM using
position correction information, along with any
other user-configured parameters for RTCM
generation.
RSP-FR-020-v1.0
An RSP shall generate J2735 SPaT using
Traffic Signal Controller Broadcast Message
(TSCBM), along with any other user-configured
parameters for SPaT generation.
RSP-FR-003-v1.0
An RSP shall store J2735 MAP messages.
RSP-FR-004-v1.0
An RSP shall use detection data to determine if
a detected VRU is in a configured conflict zone.
RSP-FR-005-v1.0
An RSP shall generate J3224 SDSM using
detection data, along with any other user-
configured parameters for SDSM generation.
RSP-FR-006-v1.0
A RSP shall determine which vehicle type is
making a priority\preemption request (freight,
emergency, transit) based on SRMs.
RSP-FR-007-v1.0
An RSP shall allow a user to configure a list of
vehicles “authorized” to receive signal priority
or preemption.
RSP-FR-008-v1.0
An RSP shall store a list of vehicle IDs
“authorized” to receive signal priority or
preemption.
RSP-FR-009-v1.0
An RSP shall compare the vehicle ID (and/or
other data) in J2735 SRM against the
authorized vehicle list to determine eligibility for
emergency preemption requests.
RSP-FR-010-v1.0
An RSP shall compare the vehicle ID (and/or
other data) in J2735 SRM against the
authorized vehicle list to determine eligibility for
transit priority requests.
SERIAL 260056-C
RSP SOFTWARE REQUIREMENTS
Requirement ID
Description
RSP-FR-011-v1.0
An RSP shall use the vehicle ID (and/or other
data) in J2735 SRM in a query to the V2X
Auth/Payment System to determine eligibility
for freight priority requests.
RSP-FR-012-v1.0
A RSP shall address conflicts when multiple
J2735 SRMs are received simultaneously
based on configurable prioritization rules.
RSP-FR-013-v1.0
An RSP shall store a list of priority and
preemption call types.
RSP-FR-014-v1.0
An RSP shall compare the data elements from
the
J2735
SRM
against
the
list
of
priority/preemption call types to determine
which priority or preemption plan to call on the
controller.
RSP-FR-015-v1.0
An RSP shall generate J2735 SSM using
Traffic Signal Controller (TSC) signal status
data, along with any other user-configured
parameters for SSM generation (for authorized
requests).
RSP-FR-016-v1.0
An RSP shall generate J2735 SSMs with a
"denied" status if the requesting vehicle ID is
not on the "authorized" vehicle list.
RSP-FR-017-v1.0
An RSP shall generate J2735 SSM if a priority
or preemption plan is not defined for the
request with a status of "denied".
RSP-FR-018-v1.0
An
RSP
shall
support
remote
user
authenticated access.
RSP-FR-020-v1.0
RSP shall send status and monitoring data to
the V2X management system.
Roadside Processor Interface Requirements
RSP-IR-001-v1.0
An RSP shall receive position corrections data
from a Continuously Operating Reference
Station (CORS).
RSP-IR-002-v1.0
An RSP shall send J2735 RTCM to an RSU.
RSP-IR-003-v1.0
An RSP should send J2735 RTCM to the MEP.
RSP-IR-004-v1.0
An RSP shall receive TSCBM from a TSC.
RSP-IR-005-v1.0
When TSCBM is not available, An RSP should
receive J2735 SPaT from the TSC.
RSP-IR-006-v1.0
An RSP shall send J2735 SPaT to an RSU.
RSP-IR-007-v1.0
An RSP shall send J2735 SPaT to the MEP.
RSP-IR-008-v1.0
An RSP shall receive J2735 MAP from the V2X
Management System.
RSP-IR-009-v1.0
An RSP shall send J2735 MAP to the RSU.
RSP-IR-010-v1.0
An RSP shall send J2735 MAP to the MEP.
RSP-IR-011-v1.0
An RSP shall receive detection data from
Vulnerable Road User Detection Equipment.
RSP-IR-012-v1.0
An RSP shall allow a user to input a
configurable detection zone geometry for
determining if an SDSM should be broadcast.
RSP-IR-013-v1.0
An RSP shall send J3224 SDSM to an RSU if a
VRU is detected in a configured conflict zone.
SERIAL 260056-C
RSP SOFTWARE REQUIREMENTS
Requirement ID
Description
RSP-IR-014-v1.0
An RSP shall not send J3224 SDSM to an RSU
if a VRU is not detected or the VRU is not in
configured conflict zone.
RSP-IR-015-v1.0
An RSP shall send J3224 SDSM to the MEP if
a VRU is detected in a configured conflict zone.
RSP-IR-016-v1.0
An RSP shall not send J3224 SDSM to the
MEP if a VRU is not detected or the VRU not in
a configured conflict zone.
RSP-IR-017-v1.0
An RSP shall receive J2735 SRM from an RSU.
RSP-IR-018-v1.0
An RSP shall receive J2735 SRM from the
MEP.
RSP-IR-019-v1.0
An RSP shall allow a user to input a list of
priority and preemption call types. This
configuration shall map SRM data elements
(e.g., Request Type, Vehicle Class, Request
ID)
to
corresponding
TSC
priority
and
preemption plan identifiers.
RSP-IR-020-v1.0
The RSP shall allow a user to input a
configurable value for the amount of time a
signal status entry (for a given priority or
preemption request with an unchanging status)
is included in the SSM.
RSP-IR-021-v1.0
An RSP shall send an account status request
to the V2X Auth/Payment system (using a
unique vehicle identifier - from the J2735 SRM)
to determine if a freight vehicle is authorized to
receive signal priority.
RSP-IR-022-v1.0
An RSP shall receive account status validation
results from the V2X Auth/Payment system.
RSP-IR-023-v1.0
An RSP shall send an NTCIP 1202 priority or
preemption request to the TSC (for authorized
requests, and when a priority or preemption
plan is defined for the request).
RSP-IR-024-v1.0
An RSP shall not send a priority or preemption
request to the TSC for unauthorized requests.
RSP-IR-025-v1.0
An RSP shall not send a priority or preemption
request to the TSC when a priority or
preemption plan is not defined for the request.
RSP-IR-026-v1.0
An RSP shall send J2735 SSM to an RSU.
RSP-IR-027-v1.0
An RSP shall send J2735 SSM to the MEP.
RSP-IR-028-v1.0
An RSP shall send J2735 SSM (or other data
that indicates the final status of the request) to
the V2X Authorization and Payment System for
freight requests.
RSP-IR-029-v1.0
An RSP shall not send J2735 SSM to an RSU
if there are no entries in the signal status list.
RSP-IR-030-v1.0
An RSP shall not send J2735 SSM to the MEP
if there are no entries in the signal status list.
RSP-IR-031-v1.0
An RSP shall communicate with the V2X
management system, data system, and other
systems and hardware using SNMPv3.
SERIAL 260056-C
RSP SOFTWARE REQUIREMENTS
Requirement ID
Description
RSP-IR-032-v1.0
An RSP shall forward all V2X messages sent to
an RSU or MEP (J2735 SPaT, MAP, RTCM,
SSM, and J3224 SDSM), to the data system
and the V2X Management System.
RSP-IR-033-v1.0
An RSP shall send all V2X messages received
from the MEP (J2735 SRM and J2735 BSM) to
the data system and the V2X Management
System.
Roadside Processor Performance Requirements
RSP-PR-001-v1.0
Any timestamp data elements included in
messages should be accurate to within 10
milliseconds.
RSP-PR-019-v1.0
The MsgCount data field of all applicable V2X
messages shall increment by 1 when data in
the message has changed (other than
timestamp data, excluding elements in the
SPaT Time Change Details data frame).
RSP-PR-004-v1.0
The J2735 SPaT should be CTI 4501
compliant.
RSP-PR-005-v1.0
The J2735 SPaT shall contain all required data
elements per CTI 4501, except for startTime
and nextTime.
RSP-PR-006-v1.0
J2735 SPaT and MAP broadcast from the
same intersection should have matching
intersection and road authority identifiers (Road
Authority ID).
RSP-PR-007-v1.0
The list of unique signal group ID between
J2735 SPaT and MAP broadcast for the same
intersection, shall match.
RSP-PR-008-v1.0
The revision (message count) should increment
by one only when any data elements in the
SPaT message change, except for the
timestamp in the intersection data frame.
Otherwise, the revision (message count)
should remain the same.
RSP-PR-009-v1.0
The J2735 SPaT enabled lanes list shall only
include lanes identified as revocable in the
MAP message.
RSP-PR-009a-v1.0
The J2735 SPaT enabled lanes list shall
accurately reflect the lanes and operations in
use at the time the message is broadcast.
RSP-PR-010-v1.0
The J2735 SPaT shall contain all movement
events for the current movement state.
RSP-PR-011-v1.0
The J2735 SPaT should contain movement
events for a subsequent movement state, only
for movement events in the current movement
state with a green or yellow event state
(protected-Movement-Allowed,
permissive-
Movement-Allowed,
protected-Clearance,
permissive-Clearance).
RSP-PR-012-v1.0
The J2735 SPaT Movement events shall be
updated at the computation frequency of the
traffic signal controller.
SERIAL 260056-C
RSP SOFTWARE REQUIREMENTS
Requirement ID
Description
RSP-PR-013-v1.0
The J2735 SPaT eventState data element
should always accurately reflect actual signal
indications for all movement events for the
current movement state (when linked to a MAP
message using the signal group). This includes
movements that are controlled by more than
one phase, such as protected-permissive
turns).
RSP-PR-014-v1.0
The J2735 SPaT minEndTime should never
decrease.
RSP-PR-015-v1.0
The J2735 SPaT maxEndTime should never
increase.
RSP-PR-016-v1.0
The J2735 SPaT minEndTime shall equal the
maxEndTime
when
the
event
state
is
Protected-Clearance or Permissive-Clearance.
RSP-PR-017-v1.0
The actual transition from one event state to the
next for a given signal group shall occur
between the minEndTime and maxEndTime
values specified in the last message for that
signal group before the transition occurs.
RSP-PR-018-v1.0
The J2735 SSM shall contain one signal status
entry for each active priority or preemption
request
RSP-PR-019-v1.0
The J2735 SSM shall only include a signal
status entry (for a given priority or preemption
request with an unchanging status) for the
configured amount of time.
RSP-PR-020-v1.0
All required J2735 SSM data elements shall be
accurately populated.
RSP-PR-022-v1.0
V2X message latency from generate to RSU
broadcast shall be less than 300 milliseconds.
RSP-PR-023-v1.0
The latency between change in signal head and
the corresponding change in the SPaT
message shall be less than 300 milliseconds.
RSP-PR-024-v1.0
An RSP shall have an overall uptime greater
than 99 percent.
RSP-PR-025-v1.0
An RSP shall be time synchronized with other
system devices.
Roadside Processor Data Requirements
RSP-DR-001-v1.0
The J2735 RTCM shall include the msgCnt field
to support sequencing (J2735 Section 7.113).
RSP-DR-002-v1.0
The J2735 RTCM shall include the rev
(message revision number) (J2735 Section
7.178).
RSP-DR-003-v1.0
The J2735 RTCM may include the RTCM
Header field if metadata tagging is used (J2735
Section 6.122).
RSP-DR-004-v1.0
The J2735 SPaT shall contain the MsgCount
data element (J2735 Section 7.113).
RSP-DR-005-v1.0
The J2735 SPaT shall contain the time stamp
data element (J2735 Section 7.109).
RSP-DR-006-v1.0
The J2735 SPaT shall contain the Intersections
data frame (J2735 Section 6.64).
SERIAL 260056-C
RSP SOFTWARE REQUIREMENTS
Requirement ID
Description
RSP-DR-007-v1.0
The
J2735
SPaT
shall
contain
the
IntersectionState data frame (J2735 Section
6.45).
RSP-DR-008-v1.0
The
J2735
SPaT
shall
contain
the
IntersectionReferenceID data frame (J2735
Section 6.44).
RSP-DR-009-v1.0
The J2735 SPaT shall contain the intersection
status data element (J2735 Section 7.65).
RSP-DR-010-v1.0
The J2735 SPaT shall contain the MOY (minute
of the year) data element (J2735 Section
7.109).
RSP-DR-011-v1.0
The
J2735
SPaT
shall
contain
the
MovementState data frame (J2735 Section
6.61).
RSP-DR-012-v1.0
The
J2735
SPaT
shall
contain
the
MovementEvent data frame (J2735 Section
6.59).
RSP-DR-013-v1.0
The
J2735
SPaT
shall
contain
the
MovementPhaseState data element (J2735
Section 7.112).
RSP-DR-014-v1.0
The
J2735
SPaT
shall
contain
the
SignalGroupID data element (J2735 Section
7.187).
RSP-DR-015-v1.0
The
J2735
SPaT
shall
contain
the
TimeChangeDetails data frame (J2735 Section
6.148).
RSP-DR-016-v1.0
The J2735 SPaT shall contain the minEndTime
data element (J2735 Section 7.213).
RSP-DR-017-v1.0
The
J2735
SPaT
shall
contain
the
maxEndTime data element (J2735 Section
7.213).
RSP-DR-018-v1.0
The J2735 MAP shall contain all mandatory
data elements (J2735 Section 5.8).
RSP-DR-019-v1.0
The J2735 MAP may contain Preempt Priority
List (J2735 Section 6.99).
RSP-DR-020-v1.0
The
J2735
MAP
shall
contain
MinuteOfTheYear (J2735 Section 7.109).
RSP-DR-021-v1.0
The J2735 MAP shall contain the MsgCount
data element (J2735 Section 7.113).
RSP-DR-022-v1.0
The
J2735
MAP
shall
contain
the
IntersectionGeometryList data frame (J2735
Section 6.43).
RSP-DR-023-v1.0
The
J2735
MAP
shall
contain
the
IntersectionGeometry
data
frame
(J2735
Section 6.42).
RSP-DR-024-v1.0
The
J2735
MAP
shall
contain
the
IntersectionReferenceID data frame (J2735
Section 6.44).
RSP-DR-025-v1.0
The J2735 MAP shall contain the IntersectionID
data element (J2735 Section 7.64)
RSP-DR-026-v1.0
The J2735 MAP shall contain the Position3D
(refPoint) data frame (J2735 Section 6.96).
SERIAL 260056-C
RSP SOFTWARE REQUIREMENTS
Requirement ID
Description
RSP-DR-027-v1.0
The J2735 MAP shall contain the Latitude data
element (J2735 Section 7.99).
RSP-DR-028-v1.0
The J2735 MAP shall contain the Longitude
data element (J2735 Section 7.103).
RSP-DR-029-v1.0
The J2735 MAP shall contain the LaneWidth
data element (J2735 Section 7.98).
RSP-DR-030-v1.0
The J2735 MAP shall contain the LaneList data
frame (J2735 Section 6.55).
RSP-DR-031-v1.0
The J2735 MAP shall contain the GenericLane
data frame (J2735 Section 6.34).
RSP-DR-032-v1.0
The J2735 MAP shall contain the LaneID data
element (J2735 Section 7.96).
RSP-DR-033-v1.0
The
J2735
MAP
shall
contain
the
AllowedManeuvers
data
element
(J2735
Section 7.5).
RSP-DR-034-v1.0
The J2735 MAP shall contain the NodeListXY
data frame (J2735 Section 6.80).
RSP-DR-035-v1.0
The J2735 MAP shall contain the NodeSetXY
data frame (J2735 Section 6.85).
RSP-DR-036-v1.0
The J2735 MAP shall contain the NodeXY data
frame (J2735 Section 6.86).
RSP-DR-037-v1.0
The
J2735
MAP
shall
contain
the
NodeOffsetPointXY
data
element
(J2735
Sections 6.69-6.74).
RSP-DR-038-v1.0
The J2735 MAP shall contain the Connection
data frame (J2735 Section 6.17).
RSP-DR-039-v1.0
The
J2735
MAP
shall
contain
the
ConnectingLane data frame (J2735 Section
6.16).
RSP-DR-040-v1.0
The
J2735
MAP
shall
contain
the
SignalGroupID data element (J2735 Section
7.187).
RSP-DR-041-v1.0
The J3224 SDSM message shall include the
msgCnt field (J3224).
RSP-DR-042-v1.0
The J3224 SDSM message shall include the
required fields in DetectedObjectCommonData
(J3224).
RSP-DR-043-v1.0
The J2735 SSM shall contain the MsgCount
data element (J2735 Section 7.113).
RSP-DR-044-v1.0
The J2735 SSM shall contain the timeStamp
data element (J2735 Section 7.109).
RSP-DR-045-v1.0
The
J2735
SSM
shall
contain
the
SignalStatusList data frame (J2735 Section
6.134).
RSP-DR-046-v1.0
The
J2735
SSM
shall
contain
the
id
(IntersectionReferenceID) data frame (J2735
Section 6.44).
RSP-DR-047-v1.0
The J2735 SSM shall contain the intersection
status data element (J2735 Section 7.65).
RSP-DR-048-v1.0
The J2735 SSM shall contain the RequestID
data element (J2735 Section 7.166).
SERIAL 260056-C
RSP SOFTWARE REQUIREMENTS
Requirement ID
Description
RSP-DR-049-v1.0
The J2735 SSM shall contain the vehicleID
(TemporaryID) of the requesting vehicle (J2735
Section 7.167).
RSP-DR-050-v1.0
The
J2735
SSM
shall
contain
the
SignalStatusPackage
data
frame
(J2735
Section 6.136).
RSP-DR-051-v1.0
The
J2735
SSM
shall
contain
the
PrioritizationResponseStatus
data
element
indicating granted, denied, or pending status
(J2735 Section 7.152).
Roadside Processor Security Requirements
RSP-SR-001-v1.0
Access to an RSP shall be controlled using
role-based access control, ensuring users can
access only the functions necessary for their
role.
RSP-SR-002-v1.0
RSP user accounts shall be authenticated
using a unique username and a strong
password
meeting
NIST
SP
800-63B
guidelines (minimum length, complexity, and
password history requirements).
RSP-SR-003-v1.0
All RSPs shall be protected by network firewalls
that restrict inbound and outbound traffic to only
approved IP addresses and ports necessary for
system operations.
2.3.4
On-Board Units (OBUs)
2.3.4.1
V2X OBUs will generate and broadcast J2735 SRM to request signal
priority\preemption through RSUs within the deployment area.
2.3.4.2
OBUs will generate and broadcast SAE J3161/1 BSM.
2.3.4.3
OBUs will sign all messages with IEEE 1609.2 certificates from the
MCDOT SCMS.
2.3.4.4
OBU Antennas – Roof-mounted, or other as appropriate and approved
by the department of transportation,
2.3.4.5
RSUs will broadcast SPaT and MAP messages, based on SAE J4501,
SAE J2735 SSM, SAE J3224 SDSM, as well as IEEE 1609.3 Wireless
Access in Vehicular Environment (WAVE) Service Advertisements
(WSA) to advertise signal priority. RSUs will sign all messages with
IEEE 1609.2 certificates from the MCDOT SCMS.
2.3.4.6
OBUs will be installed in local transit vehicles, first responder vehicles,
agency owned fleet vehicles, as well as private commercial freight
vehicles. OBUs will typically be installed under the driver’s seat, behind
the driver’s seat, in a concealed compartment or cabinet, or any other
location such that the OBU does not interfere with vehicle operation and
is not subjected to a harsh environment. OBUs will be connected to a
constant vehicle power source as well as a power source that turns on
and off with the vehicle ignition. The associated OBU antenna will be
mounted on the vehicle roof (the highest surface on the vehicle) to
maximize communication range.
SERIAL 260056-C
2.3.4.7
The OBU supplier shall configure each OBU for either EVP, TSP, VRU
Safety, or FSP based on a list of vehicles provided by MCDOT with the
Purchase Order.
2.3.4.8
OBUs shall be configured to sign and broadcast SAE J3161/1 BSMs
and SAE J2735 SRMs as defined in the OBU requirements table.
2.3.4.9
OBUs shall be configured to verify SPaT, MAP, SDSM, SSM, and WSAs
as defined in the OBU requirements table.
2.3.4.10 The OBU Supplier shall provide general installation instructions and
support OBU installers, as needed during installation.
2.3.4.11 OBU Hardware shall be delivered including power cables, antennas,
mounting brackets and hardware, and any other ancillary components
required for complete installation and operation.
2.3.4.12 OBU Configuration support shall paid a lump sum covering all labor and
associated costs required to support the demonstration of full OBU
operations in the identified vehicles.
2.3.4.13 All OBU purchase may meet all the requirements in the OBU
requirements table.
OBU REQUIREMENTS
Requirement ID
Description
Onboard Unit Functional Requirements
OBU-FR-001-v1.0
Emergency vehicle OBUs shall use WSAs
containing PSID 0pE0-00-15 as an indication
that
the
intersection
supports
signal
priority\preemption.
OBU-FR-002-v1.0
Emergency vehicle OBUs shall use the J2735
MAP message received from the intersection
along with the vehicles' position information to
determine the intersection identifier, road
regulator identifier, and if the vehicle is located
within a lane geometry.
OBU-FR-003-v1.0
Emergency vehicle OBUs shall determine
identifiers for the approach and lane the
vehicle is in from the received SPaT and MAP
messages
OBU-FR-004-v1.0
Emergency vehicle OBUs shall generate
SRMs using the vehicles current position,
vehicle identifier, intersectionID, and lane and
approach information, from received SPaT
and MAP messages, along with any other
user-configured
parameters
required
for
authorized requests.
OBU-FR-005-v1.0
Transit vehicle OBUs shall use WSAs
containing PSID 0pE0-00-15 as an indication
that
the
intersection
supports
signal
priority\preemption.
SERIAL 260056-C
OBU REQUIREMENTS
Requirement ID
Description
OBU-FR-006-v1.0
Transit vehicle OBUs shall use the J2735 MAP
message received from the intersection along
with the vehicles' position information to
determine the intersection identifier, road
regulator identifier, and if the vehicle is located
within a lane geometry.
OBU-FR-007-v1.0
Transit
vehicle
OBUs
shall
determine
identifiers for the approach and lane the
vehicle is in from the received SPaT and MAP
messages.
OBU-FR-008-v1.0
Transit vehicle OBUs shall generate SRMs
using the vehicles current position, vehicle
identifier,
intersectionID,
and
lane
and
approach information, from received SPaT
and MAP messages, along with any other
user-configured
parameters
required
for
authorized requests.
OBU-FR-009-v1.0
VRU Safety OBUs shall use J3224 SDSM
along with the vehicles position and motion
information to determine if the vehicle is on a
potential collision course with a VRU.
OBU-FR-010-v1.0
OBUs shall generate J2735 BSMs using the
vehicles position, speed, heading, etc. using
data from GNSS and onboard sensors, along
with any other user-configured parameters for
BSM generation.
OBU-FR-011-v1.0
All OBUs should use RTCM to correct
positioning, if available.
Onboard Unit Interface Requirements
OBU-IR-001-v1.0
Emergency vehicle OBUs shall receive all
over-the-air messages from direct V2X RSUs.
OBU-IR-002-v1.0
An emergency vehicle OBU shall receive the
status of lights/siren systems from the
emergency vehicle on board system.
OBU-IR-003-v1.0
Emergency vehicle OBUs shall broadcast
SRMs, if the intersection WSA contains PSID
0pE0-00-15, the vehicle is within lane
geometry defined in the intersection MAP
message, and the vehicle lights and sirens are
active.
OBU-IR-004-v1.0
Emergency vehicle OBUs shall not broadcast
an SRM if the intersection WSA does not
contain PSID 0pE0-00-15 or the intersection is
not broadcasting a WSA.
OBU-IR-005-v1.0
Emergency vehicle OBUs shall not broadcast
SRMs if lights and sirens are not active.
OBU-IR-006-v1.0
An emergency vehicle OBU should not
broadcast an SRM (if not located within a lane
geometry).
OBU-IR-007-v1.0
Emergency vehicle OBUs may broadcast
SRMs if the vehicle is not located within lane
geometry defined in the intersection MAP
Message.
SERIAL 260056-C
OBU REQUIREMENTS
Requirement ID
Description
OBU-IR-008-v1.0
Transit vehicle OBUs shall receive all over-
the-air messages from direct V2X RSUs.
OBU-IR-009-v1.0
Transit vehicle OBUs should receive "on-time
status" data from the vehicles on-board
Automatic Vehicle Location System (AVL)
system.
OBU-IR-010-v1.0
Transit vehicle OBUs shall broadcast SRMs if
the intersection WSA contains PSID 0pE0-00-
15, the vehicle is within lane geometry defined
in the intersection MAP message, and the
vehicle is behind schedule by more than a
user-configurable amount of time.
OBU-IR-011-v1.0
Transit vehicle OBUs shall not broadcast an
SRM if the intersection WSA does not contain
PSID 0pE0-00-15 or the intersection is not
broadcasting a WSA.
OBU-IR-012-v1.0
Transit vehicle OBUs shall not broadcast
SRMs if the vehicle is not behind schedule
more than a user-configurable amount of time
or data is available to make a determination.
OBU-IR-013-v1.0
Transit vehicle OBUs shall not broadcast
SRMs if the vehicle is not located within a lane
defined in the intersection MAP message.
OBU-IR-014-v1.0
VRU Safety OBUs shall receive all over-the-air
messages from direct V2X RSUs.
OBU-IR-015-v1.0
VRU Safety OBUs shall deliver visual and/or
audible warnings to the vehicle operator via an
OBU Human-Machine Interface (HMI) if the
vehicle is on a potential collision course with a
vulnerable road user.
OBU-IR-016-v1.0
VRU Safety OBUs shall not deliver visual
and/or audible warnings to the vehicle
operator if the vehicle is not on a potential
collision course with a vulnerable road user.
OBU-IR-017-v1.0
OBUs shall broadcast SAE J3161/1 BSMs.
OBU-IR-018-v1.0
All OBUs shall receive location and time data
from GNSS.
Onboard Unit Performance Requirements
OBU-PR-001-v1.0
An OBU shall broadcast between 9-11 J2735
SRM messages in a 10-second interval when
conditions to broadcast SRM have been met.
OBU-PR-002-v1.0
All required SRM data elements shall be
accurately populated.
OBU-PR-003-v1.0
OBUs shall broadcast 90-110 SAE J3161/1
BSM messages in a 10-second interval.
OBU-PR-004-v1.0
All required SAE J3161/1 BSM data elements
shall be accurately populated.
OBU-PR-005-v1.0
An OBU shall be OmniAir certified for C-
V2X Release 1 or provide a letter from
OmniAir stating the OBU (make and model)
is actively in the OmniAir certification
process.
SERIAL 260056-C
OBU REQUIREMENTS
Requirement ID
Description
OBU-PR-006-v1.0
An OBU shall have associated documentation
that indicate it has been tested at events such
as OmniAir Plugfests, 5GAA Plugfests, etc.
Onboard Unit Data Requirements
OBU-DR-001-v1.0
The J2735 SRM shall contain the MsgCount
data element (J2735 Section 7.113).
OBU-DR-002-v1.0
The J2735 SRM shall contain the timeStamp
data element (J2735 Section 7.192).
OBU-DR-003-v1.0
The J2735 SRM shall contain the requestor
data frame (RequestorDescription) (J2735
Section 6.98).
OBU-DR-004-v1.0
The J2735 SRM shall contain the VehicleID
field within requestor (J2735 Section 6.147).
OBU-DR-005-v1.0
The
J2735
SRM
shall
contain
the
TemporaryID field under VehicleID (J2735
Section 7.187).
OBU-DR-006-v1.0
The J2735 SRM shall contain the RequestID
data element (J2735 Section 7.153).
OBU-DR-007-v1.0
The
J2735
SRM
shall
contain
the
SignalRequestList data frame (J2735 Section
6.118).
OBU-DR-008-v1.0
The
J2735
SRM
shall
contain
the
SignalRequest data frame within the list
(J2735 Section 6.120).
OBU-DR-009-v1.0
The
J2735
SRM
shall
contain
the
IntersectionReferenceID data frame (J2735
Section 6.36).
OBU-DR-010-v1.0
The
J2735
SRM
shall
contain
the
inBoundLane
data
frame
(IntersectionAccessPoint)
(J2735
Section
6.33).
OBU-DR-011-v1.0
The
J2735
SRM
shall
contain
the
PriorityRequestType
field
to
distinguish
request intent (J2735 Section 7.142).
OBU-DR-012-v1.0
The J2735 SRM shall contain expected arrival
time and duration if used (J2735 Section
6.120).
OBU-DR-013-v1.0
The J2735 SRM shall contain current speed,
heading, and position of the vehicle (J2735
Section 6.98).
OBU-DR-014-v1.0
BSMs
shall
include
all
data
elements
contained in the BSMcoreData data frame
(J2735 Section 6.10).
OBU-DR-015-v1.0
BSMs may include any of the Part II
extensions (VehicleSafetyExtensions J2735
Section 6.168, Special Vehicle Extensions
J2735
Section
6.142,
SupplementalVehicleExtensions
J2735
Section 6.147), only if there are data elements
within those frames that can be accurately
populated.
Onboard Unit Security Requirements
SERIAL 260056-C
OBU REQUIREMENTS
Requirement ID
Description
OBU-SR-001-v1.0
All OBUs shall comply with IEEE 1609.2.
OBU-SR-001a-v1.0
OBUs shall comply with IEEE 1609.2.1.
OBU-SR-002-v1.0
All OBUs shall be provisioned with valid IEEE
1609.2 enrollment certificates (by the supplier)
prior to deployment.
OBU-SR-003-v1.0
OBUs shall sign BSMs with valid IEEE 1609.2
pseudonym certificates.
OBU-SR-004-v1.0
OBUs that support EVP or TSP shall sign
SRMs with IEEE 1609.2 identity certificates.
OBU-SR-006-v1.0
An
OBU
shall
cease
transmission
of
messages if no valid IEEE 1609.2 pseudonym
or IEEE 1609.2 identity certificates are
available.
OBU-SR-007-v1.0
OBUs shall be capable of performing digital
signature validation and certificate verification
according to IEEE 1609.2.
OBU-SR-008-v1.0
An OBU shall reject V2X messages that fail
signature validation or are signed with expired
or revoked certificates.
OBU-SR-010-v1.0
OBUs
should
generate
and
transmit
misbehavior reports to the SCMS.
OBU-SR-011-v1.0
OBUs should download and utilize the latest
Certificate Revocation List (CRL) from the
SCMS.
OBU-SR-012-v1.0
OBUs should reject all messages received
from any source listed on the current CRL.
OBU-SR-013-v1.0
An OBU using IEEE 1609.2 pseudonym
certificates shall have no more than three
years’ worth of pseudonym certificates loaded
at a time.
OBU-SR-014-v1.0
An OBU using IEEE 1609.2 pseudonym
certificates shall request to receive additional
pseudonym certificates at least once per year
from the SCMS.
OBU-SR-015-v1.0
An OBU using IEEE 1609.2 identity certificates
shall have no more than three years’ worth of
identity certificates loaded at a time.
OBU-SR-016-v1.0
An OBU using IEEE 1609.2 identity certificates
shall request to receive additional identity
certificates at least once per year from the
SCMS.
OBU-SR-017-v1.0
An OBU shall implement IEEE 1609.2
certificate download and renewal processes
over
secure,
encrypted,
end-to-end
connections.
OBU-SR-018-v1.0
Access to an OBU shall be controlled using
role-based access control, ensuring users can
access only the functions necessary for their
role.
SERIAL 260056-C
OBU REQUIREMENTS
Requirement ID
Description
OBU-SR-019-v1.0
OBU user accounts shall be authenticated
using a unique username and a strong
password
meeting
NIST
SP
800-63B
guidelines (minimum length, complexity, and
password history requirements).
OBU-SR-020-v01
An OBU shall utilize the national Certificate
Trust List (CTL) to verify messages signed
with certificates from SCMS providers
other than the provider the OBU is enrolled
in.
2.4
TECHNICAL AND DESCRIPTIVE SALES LITERATURE
The contractor shall provide copies of its sales literature and brochures and copies of any
manufacturer’s technical and/or descriptive literature (e.g., PDF versions of sales literature,
brochures, and/or webpages) specific to the material(s) the contractor proposes to provide.
Literature shall be sufficient in detail to allow for full and fair evaluation of the material(s)
submitted and must be included with the bid. Failure to include this information may result
in the bid being rejected.
3.0
PURCHASING REQUIREMENTS
3.1
DELIVERY
3.1.1
Delivery is desired as soon as possible, and details shall be stipulated on the
purchase order. Contractor shall notify the County representative listed on the
purchase order if the requested delivery date and/or the anticipated lead time
cannot be met. Failure to communicate to County changes in the order status may
result in default proceedings.
3.1.2
Supplies or equipment shall be delivered between the hours of 8:00 a.m. and 3:00
p.m. Mountain Standard Time (MST), Monday through Friday, except on County
recognized holidays.
3.1.3
Delivery shall be F.O.B. Destination Freight Prepaid.
3.2
EXPEDITED DELIVERY
3.2.1
If the department determines that expedited delivery or other alternate shipping is
required, it shall notify the contractor. The contractor shall determine any additional
costs associated with such delivery terms and communicate that cost to the
department.
3.2.2
The department shall not advise the contractor to proceed with an expedited
shipment until acceptable terms are agreed upon and a purchase order is issued.
Upon agreeing to the additional costs, the department shall advise the contractor
to proceed.
3.2.3
Upon receipt of material(s) and invoicing, the department shall ensure that any
additional charges are in compliance with and do not exceed agreed to costs. The
department shall retain all documents related to these costs within the agency
purchase file.
SERIAL 260056-C
3.3
SHIPPING DOCUMENTS
A packing list or other suitable shipping document shall accompany each shipment and
shall include the following:
3.3.1
Contract serial number
3.3.2
Contractor’s name and address
3.3.3
Department name and address
3.3.4
Department purchase order number
3.3.5
A description of product(s) shipped, including item number(s), quantity(ies),
number of containers and package number(s), as applicable
3.3.6
A table of configurations and means of identifying individual devices shall be on
the outside of each devices box or packaging.
3.3.7
A certification and serial number of build America/buy America (or that statement
of compliance is via waiver with backup provided)
3.4
SHIPPING TERMS
Bid price(s) and terms shall be F.O.B. Destination Freight Prepaid at the location(s)
stipulated on the purchase order. All delivery locations are within Maricopa County.
3.5
OPERATING MANUALS
Upon delivery, contractor shall provide comprehensive operational manuals, service
manuals and schematic diagrams, if required by the department.
3.6
SAMPLES
The contractor may be requested to furnish samples of material(s) bid to allow for
examination by the County. Any materials so requested shall be furnished within 10
working days from the date of request and furnished at no cost to the County and sent to
the address designated in the requesting correspondence.
3.7
TESTING
Unless otherwise specified, materials purchased will be inspected by the department to
ensure the materials meet the quality and quantity requirements of the specifications.
When deemed necessary by the County, samples of the materials may be taken at random
from stock received for submission to a commercial laboratory or other appropriate agency
for analysis and tests to determine whether the materials conform in all respects to the
specifications. In cases where commercial laboratory reports determine that the materials
do not meet the specifications, the expense of such analysis shall be borne by the
contractor.
3.8
ACCEPTANCE
Upon delivery and successful installation, the material(s) shall be deemed accepted, and
the warranty period shall begin. Successful installation shall be defined as a) the
material(s)/equipment is installed and tested (as necessary) and fully operational; and b)
initial training, if any, is complete. All documentation shall be completed prior to final
acceptance.
SERIAL 260056-C
3.9
TRAINING
The contractor shall provide training services to completely train County personnel in the
use and care of the equipment. All training shall take place on-site in Maricopa County,
unless otherwise negotiated with County.
3.10
STOCK
The contractor shall be expected to stock sufficient quantities as may be necessary to meet
the County’s needs and deliver as stated in the Invitation for Bids.
3.11
DISCONTINUED MATERIALS
3.11.1 In the event that a manufacturer discontinues materials, the County may allow the
contractor to provide a substitute for the discontinued item or may cancel the
contract. If the contractor requests permission to substitute a new material, the
contractor shall provide the following to the County:
3.11.1.1 Documentation from the manufacturer that the material has been
discontinued.
3.11.1.2 Documentation that names the replacement material.
3.11.1.3 Documentation that provides clear and convincing evidence that the
replacement material meets or exceeds all specifications required by the
original solicitation.
3.11.1.4 Documentation that provides clear and convincing evidence that the
replacement material will be compatible with all the functions or uses of
the discontinued material.
3.11.1.5 Documentation confirming that the price for the replacement is the same
as or less than the discontinued material.
3.11.2 Material discontinuance applies only to those materials specifically listed on any
resultant contract. This will not apply to catalog items not specifically listed on any
resultant contract.
3.12
WARRANTY
3.12.1 All items furnished under this contract shall conform to the requirements of this
contract and shall be free from defects in design, materials, and workmanship.
3.12.2 The warranty period for workmanship and materials shall be for a minimum initial
period of five years and commence upon acceptance by County per Section 3.8 -
Acceptance.
3.12.2.1 The contractor shall indicate on the price sheet the duration of the
warranty and any applicable limitations or conditions which may apply.
3.12.2.2 The contractor agrees that it will, at its own expense, provide all labor
and parts required to remove, repair, or replace, and reinstall any such
defective workmanship and/or materials which becomes or is found to
be defective during the term of this warranty. The contractor shall
guarantee the equipment to be supplied complies with all applicable
regulations.
SERIAL 260056-C
3.13
MODEL/YEAR OF MATERIALS
The
County
will
only
accept
bids
offering
the
most
current
model/year
equipment/material(s).
3.14
ORDER CUTOFF INFORMATION
3.14.1 Contractors submitting bids shall advise the County of all known order cutoff
dates/times for the equipment/product(s) specified in this solicitation at the time of
bid submission. Notification of any subsequent cutoff date(s)/time(s) (learned after
submission of bid) shall also be the contractor’s responsibility. The contractor shall
advise the County of subsequent cutoff date(s)/time(s) by notifying the
procurement officer, in writing, of the new information.
3.14.2 If the item(s) become no longer available, contractor shall notify County of the last
available ordering date for the item(s) and may provide County with alternative
item(s) that the County may elect to purchase at its option. If the alternative item(s)
do not meet the County’s requirements, County may take action including
termination of this contract for convenience per Section 4.16 – Termination for
Convenience.
3.15
ORDER LEAD-TIME NOTIFICATION
3.15.1 Contractors submitting bids shall advise the County of lead-time(s) for the required
items specified in this solicitation at the time of bid submission. Notification of any
changes to lead time (learned after submission of bid) shall also be the contractor’s
responsibility. The contractor shall also notify all County representatives included
on purchase orders of lead-time information.
3.16
USAGE REPORT
The contractor shall furnish the County a usage report, upon request, delineating the
acquisition activity governed by the contract. The format of the report shall be approved by
the County and shall disclose the quantity and dollar value of each contract item by
individual unit of measure.
3.17
Background CHECK
Bidders/proposers may be required to pass multiple background checks (e.g. Sheriff’s
Office, County Attorney's Office, Courts, as well as Maricopa County general government)
to determine if the respondent is acceptable to do business with the County. This applies
to, but is not limited to, the company, subcontractors, and employees.
3.18
INVOICES AND PAYMENTS
3.18.1 The contractor shall submit one legible copy of their detailed invoice before
payment(s) will be made. Incomplete invoices will not be processed. At a minimum,
the invoice must provide the following information:
•
Company name, address, and contact information
•
County bill-to name and contact information
•
Contract serial number
•
County purchase order number
•
Invoice number and date
•
Payment terms
•
Date of service or delivery
•
Quantity
•
Contract item number(s)
•
Arrival and completion time
SERIAL 260056-C
•
Description of purchase (product or services)
•
Pricing per unit of purchase
•
Extended price
•
Freight (if applicable)
•
Total amount due
•
Certification and Serial Number of build America/buy America (or that
statement of compliance via waiver with backup provided if requested)
3.18.2 Labor, services, and maintenance must be billed as a separate line item.
3.18.3 Problems regarding billing or invoicing shall be directed to the department as listed
on the purchase order.
3.18.4 Payment will only be made to the contractor by Accounts Payable through the
Maricopa County Vendor Express Payment Program. This is an Electronic Funds
Transfer (EFT) process. After contract award, the contractor shall complete the
Vendor Registration Form located on the County Department of Finance Vendor
Registration website (https://www.maricopa.gov/5169/Vendor-Information).
3.18.5 Discounts offered in the contract shall be calculated based on the date a properly
completed invoice is received by the County.
3.18.6 EFT payments to the routing and account numbers designated by the contractor
shall include the details on the specific invoices that the payment covers. The
contractor is required to discuss remittance delivery capabilities with their
designated financial institution for access to those details.
3.19
APPLICABLE TAXES
3.19.1 It is the responsibility of the contractor to determine any and all applicable taxes
and include those taxes in their proposal. The legal liability to remit the tax is on
the entity conducting business in Arizona. Tax is not a determining factor in
contract award.
3.19.2 The County will look at the price or offer submitted and will not deduct, add, or alter
pricing based on speculation or application of any taxes, nor will the County
provide contractor any advice or guidance regarding taxes. If you have questions
regarding your tax liability, seek advice from a tax professional prior to submitting
your bid. You may also find information at https://www.azdor.gov/Business.aspx.
Once your bid is submitted, the offer is valid for the time specified in this solicitation,
regardless of mistake or omission of tax liability. If the County finds overpayment
of a project due to tax consideration that was not due, the contractor shall be liable
to the County for that amount, and by contracting with the County agrees to remit
any overpayments back to the County for miscalculations on taxes included in a
bid price.
3.19.3 Tax Indemnification: Contractor and all subcontractors shall pay all Federal, state,
and local taxes applicable to their operation and any persons employed by the
contractor. Contractor shall, and require all subcontractors to, hold Maricopa
County harmless from any responsibility for taxes, damages, and interest, if
applicable, contributions required under Federal and/or state and local laws and
regulations, and any other costs including transaction privilege taxes,
unemployment compensation insurance, Social Security, and Workers’
Compensation. Contractor may be required to establish, to the satisfaction of
County, that any and all fees and taxes due to municipality or the State of Arizona
for any license or transaction privilege taxes, use taxes, or similar excise taxes are
currently paid (except for matters under legal protest).
SERIAL 260056-C
3.20
POST AWARD MEETING
The contractor may be required to attend a post-award meeting with the department to discuss
the terms and conditions of this contract. This meeting will be coordinated by the procurement
officer of the contract.
3.21
STRATEGIC ALLIANCE for VOLUME EXPENDITURES (SAVE)
The County is a member of the SAVE cooperative purchasing group. SAVE includes the
State of Arizona, many Phoenix metropolitan area municipalities, and many K-12 unified
school districts. Under the SAVE Cooperative Purchasing Agreement, and with the
concurrence of the successful respondent under this solicitation, a member of SAVE may
access a contract resulting from a solicitation issued by the County. If contractor does not
want to grant such access to a member of SAVE, state so in the bid. In the absence of a
statement to the contrary, the County will assume that contractor does wish to grant access
to any contract that may result from this bid. The County assumes no responsibility for any
purchases by using entities.
3.22
INTERGOVERNMENTAL COOPERATIVE PURCHASING AGREEMENTS (ICPAs)
County currently holds ICPAs with numerous governmental entities. These agreements
allow those entities, with the approval of the contractor, to purchase their requirements
under the terms and conditions of the County contract. It is the responsibility of the non-
County government entity to perform its own due diligence on the acceptability of the
contract under its applicable procurement rules, processes, and procedures. Certain
governmental agencies may not require an ICPA and may utilize this contract if it meets
their individual requirements. Other governmental agencies may enter into a separate
Statement of Work with the contractor to meet their own requirements. The County is not
a party to any uses of this contract by other governmental entities.
4.0
CONTRACTUAL TERMS & CONDITIONS
4.1
CONTRACT TERM
This Invitation for Bids is for awarding a firm, fixed price purchasing contract to cover a
term of two years.
4.2
OPTION TO RENEW
The County may, at its option and with the concurrence of the contractor, renew the term
of this contract up to a maximum of 4 additional years, (or at the County’s sole discretion,
extend the contract on a month-to-month basis for a maximum of six months after
expiration). The contractor shall be notified in writing by the Office of Procurement Services
of the County’s intention to renew the contract term at least 60 calendar days prior to the
expiration of the original contract term.
4.3
CONTRACT COMPLETION
In preparation for contract completion, the contractor shall make all reasonable efforts for
an orderly transition of its duties and responsibilities to another provider and/or to the
County. This may include, but is not limited to, preparation of a transition plan and
cooperation with the County or other providers in the transition. The transition includes the
transfer of all records and other data in the possession, custody, or control of the contractor
that are required to be provided to the County either by the terms of this agreement or as
a matter of law. The provisions of this clause shall survive the expiration or termination of
this agreement.
SERIAL 260056-C
4.4
PRICE ADJUSTMENTS
4.4.1
Any requests for reasonable price adjustments must be submitted 60 calendar
days prior to the contract expiration. Requests for adjustment in cost of labor
and/or materials must be supported by appropriate documentation. The
reasonableness of the request will be determined by comparing the request with
the Consumer Price Index or by performing a market survey. If County agrees to
the adjusted price terms, County will issue written approval of the change and
provide an updated version of the contract. The new change shall not be in effect
until the date stipulated on the updated version of the contract.
4.5
INDEMNIFICATION
To the fullest extent permitted by law, and to the extent that claims, damages, losses, or
expenses are not covered and paid by insurance purchased by the contractor, the
contractor shall defend, indemnify, and hold harmless the County (as Owner), its agents,
representatives, officers, directors, officials, and employees from and against all claims,
damages, losses, and expenses (including, but not limited to attorneys' fees, court costs,
expert witness fees, and the costs and attorneys' fees for appellate proceedings) arising
out of, or alleged to have resulted from, the negligent acts, errors, omissions, or mistakes
of the contractor, a subcontractor, anyone directly or indirectly employed by them, or
anyone for whose acts they may be liable relating to the performance of this contract.
4.5.1
Contractor's duty to defend, indemnify, and hold harmless the County, its agents,
representatives, officers, directors, officials, and employees shall arise in
connection with any claim, damage, loss, or expense that is attributable to bodily
injury, sickness, disease, death, or injury to, impairment of, or destruction of
tangible property, including loss of use resulting therefrom, caused by negligent
acts, errors, omissions, or mistakes in the performance of this contract, but only to
the extent caused by the negligent acts or omissions of the contractor, a
subcontractor, anyone directly or indirectly employed by them, or anyone for
whose acts they may be liable, regardless of whether or not such claim, damage,
loss, or expense is caused in part by a party indemnified hereunder.
4.5.2
The amount and type of insurance coverage requirements set forth herein will in
no way be construed as limiting the scope of the indemnity in this section.
4.5.3
The scope of this indemnification does not extend to the sole negligence of County.
4.6
INSURANCE
4.6.1
Contractor, at contractor’s own expense, shall purchase and maintain, at a
minimum, the herein stipulated insurance from a company or companies duly
licensed by the State of Arizona and possessing an AM Best, Inc. category rating
of B++. In lieu of State of Arizona licensing, the stipulated insurance may be
purchased from a company or companies, which are authorized to do business in
the State of Arizona, provided that said insurance companies meet the approval of
County. The form of any insurance policies and forms must be acceptable to
County.
4.6.2
All insurance required herein shall be maintained in full force and effect until all
work or service required to be performed under the terms of the contract is
satisfactorily completed and formally accepted. Failure to do so may, at the sole
discretion of County, constitute a material breach of this contract.
SERIAL 260056-C
4.6.3
In the event that the insurance required is written on a claims-made basis,
contractor warrants that any retroactive date under the policy shall precede the
effective date of this contract and either continuous coverage will be maintained,
or an extended discovery period will be exercised for a period of two years
beginning at the time work under this contract is completed.
4.6.4
Contractor’s insurance will be primary insurance as respects County, and any
insurance or self-insurance maintained by County will not contribute to it.
4.6.5
Any failure to comply with the claim reporting provisions of the insurance policies
or any breach of an insurance policy warranty shall not affect the County’s right to
coverage afforded under the insurance policies.
4.6.6
The insurance policies may provide coverage that contains deductibles or self-
insured retentions. Such deductibles and/or self-insured retentions shall not be
applicable with respect to the coverage provided to County under such policies.
Contractor shall be solely responsible for the deductible and/or self-insured
retention and County, at its option, may require contractor to secure payment of
such deductibles or self-insured retentions by a surety bond or an irrevocable and
unconditional letter of credit.
4.6.7
The insurance policies required by this contract, except Workers’ Compensation
and Errors and Omissions, shall name County, its agents, representatives, officers,
directors, officials, and employees as additional insureds.
4.6.8
The policies required hereunder, except Workers’ Compensation and Errors and
Omissions, shall contain a waiver of transfer of rights of recovery (subrogation)
against County, its agents, representatives, officers, directors, officials, and
employees for any claims arising out of contractor’s work or service.
4.6.9
If available, the insurance policies required by this contract may be combined with
Commercial Umbrella Insurance policies to meet the minimum limit requirements.
If a Commercial Umbrella insurance policy is utilized to meet insurance
requirements, the Certificate of Insurance shall indicate which lines the
Commercial Umbrella Insurance covers.
4.6.9.1
Commercial General Liability
Commercial General Liability (CGL) insurance with a limit of not less
than $2,000,000 for each occurrence, $4,000,000 Products/Completed
Operations Aggregate, and $4,000,000 General Aggregate Limit. The
policy shall include coverage for premises liability, bodily injury, broad
form property damage, personal injury, products and completed
operations and blanket contractual coverage, and shall not contain any
provisions which would serve to limit third-party action over claims.
There shall be no endorsement or modifications of the CGL limiting the
scope of coverage for liability arising from explosion, collapse, or
underground property damage.
4.6.9.2
Automobile Liability
Commercial/Business Automobile Liability insurance with a combined
single limit for bodily injury and property damage of not less than
$2,000,000 each occurrence with respect to any of the contractor’s
owned, hired, and non-owned vehicles assigned to or used in
performance of the contractor’s work or services or use or maintenance
of the premises under this contract.
SERIAL 260056-C
4.6.9.3
Workers’ Compensation
4.6.9.3.1
Workers’ Compensation insurance to cover obligations
imposed by Federal and state statutes having jurisdiction of
contractor’s employees engaged in the performance of the
work or services under this contract; and Employer’s
Liability insurance of not less than $1,000,000 for each
accident, $1,000,000 disease for each employee, and
$1,000,000 disease policy limit.
4.6.9.3.2
Contractor, its subcontractors, and sub-subcontractors
waive all rights against this contract and its agents, officers,
directors, and employees for recovery of damages to the
extent these damages are covered by the Workers’
Compensation and Employer’s Liability or Commercial
Umbrella Liability insurance obtained by contractor, its
subcontractors, and its sub-subcontractors pursuant to this
contract.
4.6.10 Certificates of Insurance
4.6.10.1 Prior to contract award, contractor shall furnish the County with valid and
complete certificates of insurance, or formal endorsements as required
by the contract in the form provided by the County, issued by
contractor’s insurer(s), as evidence that policies providing the required
coverage, conditions, and limits required by this contract are in full force
and effect. Such certificates shall identify this contract number and title.
4.6.10.2 In the event any insurance policy(ies) required by this contract is (are)
written on a claims-made basis, coverage shall extend for two years past
completion and acceptance of contractor’s work or services and as
evidenced by annual Certificates of Insurance.
4.6.10.3 If a policy does expire during the life of the contract, a renewal certificate
must be sent to County 15 calendar days prior to the expiration date.
4.6.10.4 Certificates of Insurance shall identify Maricopa County as the certificate
holder as follows:
Maricopa County
c/o Risk Management
301 W Jefferson St, Suite 910
Phoenix, AZ 85003
4.6.11 Cancellation and Expiration Notice
Applicable to all insurance policies required within the insurance requirements of
this contract, contractor’s insurance shall not be permitted to expire, be
suspended, be canceled, or be materially changed for any reason without 30
calendar days prior written notice to Maricopa County. Contractor must provide
notice to Maricopa County, within two business days of receipt, if they receive
notice of a policy that has been or will be suspended, canceled, materially changed
for any reason, has expired, or will be expiring. Such notice shall be sent directly
to Maricopa County Office of Procurement Services and shall be mailed, or hand
delivered to 301 W. Jefferson, Suite 700, Phoenix, AZ 85003, or emailed to the
procurement officer noted in the solicitation.
SERIAL 260056-C
4.7
FORCE MAJEURE
4.7.1
Neither party shall be liable for failure of performance, nor incur any liability to the
other party on account of any loss or damage resulting from any delay or failure to
perform all or any part of this contract, if such delay or failure is caused by events,
occurrences, or causes beyond the reasonable control and without negligence of
the parties. Such events, occurrences, or causes include, but are not limited to,
acts of God/nature (including fire, flood, earthquake, storm, hurricane, or other
natural disaster), war, invasion, act of foreign enemies, hostilities (whether war is
declared or not), civil war, riots, rebellion, revolution, insurrection, military or
usurped power or confiscation, terrorist activities, nationalization, government
sanction, lockout, blockage, embargo, labor dispute, strike, and interruption or
failure of electricity or telecommunication service and pandemic.
4.7.2
Each party as applicable, shall give the other party notice of its inability to perform
and particulars in reasonable detail of the cause of the inability. Each party must
use best efforts to remedy the situation and remove, as soon as practicable, the
cause of its inability to perform or comply.
4.7.3
The party asserting Force Majeure as a cause for non-performance shall have the
burden of proving that reasonable steps were taken to minimize delay or damages
caused by foreseeable events, that all non-excused obligations were substantially
fulfilled, and that the other party was timely notified of the likelihood or actual
occurrence which would justify such an assertion, so that other prudent
precautions could be contemplated.
4.8
ORDERING AUTHORITY
Any request for purchase shall be accompanied by a valid purchase order issued by a
County department or directed by a Certified Agency Procurement Aid (CAPA) with a
purchase card for payment.
4.9
AVAILABILITY OF FUNDS
4.9.1
The provisions of this contract relating to payment shall become effective when
funds assigned for the purpose of compensating the contractor as herein provided
are actually available to County for disbursement. The County shall be the sole
judge and authority in determining the availability of funds under this contract.
County will keep the contractor fully informed as to the availability of funds.
4.9.2
If any action is taken by any state agency, Federal department, or any other agency
or instrumentality to suspend, decrease, or terminate its fiscal obligations under,
or in connection with, this contract, County may amend, suspend, decrease, or
terminate its obligations under, or in connection with, this contract. In the event of
termination, County will be liable for payment only for services rendered prior to
the effective date of the termination, provided that such services are performed in
accordance with the provisions of this contract. County will give written notice of
the effective date of any suspension, amendment, or termination under this
section, at least 10 days in advance.
4.10
PROCUREMENT CARD ORDERING CAPABILITY
County may opt to use a procurement card (Visa or Master Card) to make payment for
orders under this contract.
4.11
INTERNET ORDERING CAPABILITY
It is the intent of Maricopa County to use the Internet to communicate and to place orders
under this contract.
SERIAL 260056-C
4.12
NO MINIMUM OR MAXIMUM PURCHASE OBLIGATION
This contract does not guarantee any minimum or maximum purchases will be made.
Orders will only be placed under this contract when the County identifies a need and proper
authorization, and documentation have been approved.
4.13
PURCHASE ORDERS
4.13.1 County reserves the right to cancel purchase orders within a reasonable period of
time after issuance. Should a purchase order be canceled, the County agrees to
reimburse the contractor for actual and documentable costs incurred by the
contractor in response to the purchase order. The County will not reimburse the
contractor for any costs incurred after receipt of County notice of cancellation, or
for lost profits, or for shipment of product prior to issuance of purchase order.
4.13.2 Contractor agrees to accept verbal notification of cancellation of purchase orders
from the County with written notification to follow. Contractor specifically
acknowledges to be bound by this cancellation policy.
4.14
SUSPENSION OF WORK
The procurement officer may order the contractor, in writing, to suspend, delay, or interrupt
all or any part of the work of this contract for the period of time that the procurement officer
determines appropriate for the convenience of the County. No adjustment shall be made
under this clause for any suspension, delay, or interruption to the extent that performance
would have been so suspended, delayed, or interrupted by any other cause, including the
fault or negligence of the contractor. No request for adjustment under this clause shall be
granted unless the claim, in an amount stated, is asserted in writing as soon as practicable
after the termination of the suspension, delay, or interruption, but not later than the date of
final payment under the contract.
4.15
STOP WORK ORDER
4.15.1 The procurement officer may, at any time, by written order to the contractor, require
the contractor to stop all, or any part, of the work called for by this contract for a
period of 90 calendar days after the order is delivered to the contractor, and for
any further period to which the parties may agree. The order shall be specifically
identified as a stop work order issued under this clause. Upon receipt of the order,
the contractor shall immediately comply with its terms and take all reasonable
steps to minimize the incurrence of costs allocable to the work covered by the order
during the period of work stoppage. Within a period of 90 calendar days after a
stop work order is delivered to the contractor, or within any extension of that period
to which the parties shall have agreed, the procurement officer shall either:
4.15.1.1 cancel the stop work order; or
4.15.1.2 terminate the work covered by the order as provided in the Termination
for Default or the Termination for Convenience clause of this contract.
4.15.2 The procurement officer may make an equitable adjustment in the delivery
schedule and/or contract price, and the contract shall be modified, in writing,
accordingly, if the contractor demonstrates that the stop work order resulted in an
increase in costs to the contractor.
4.16
TERMINATION FOR CONVENIENCE
Maricopa County may terminate the resultant contract for convenience by providing 60
calendar days advance notice to the contractor.
SERIAL 260056-C
4.17
TERMINATION FOR DEFAULT
4.17.1 The County may, by written Notice of Default to the contractor, terminate this
contract in whole or in part if the contractor fails to:
4.17.1.1 deliver the supplies or to perform the services within the time specified
in this contract or any extension;
4.17.1.2 make progress, so as to endanger performance of this contract; or
4.17.1.3 perform any of the other provisions of this contract.
4.17.2 The County’s right to terminate this contract under these subparagraphs may be
exercised if the contractor does not cure such failure within 10 business days (or
more if authorized in writing by the County) after receipt of a Notice to Cure from
the procurement officer specifying the failure.
4.18
STATUTORY RIGHT OF CANCELLATION FOR CONFLICT OF INTEREST
Notice is given that, pursuant to Arizona Revised Statute (A.R.S.) § 38-511, the County
may cancel any contract without penalty or further obligation within three years after
execution of the contract, if any person significantly involved in initiating, negotiating,
securing, drafting, or creating the contract on behalf of the County is at any time, while the
contract or any extension of the contract is in effect, an employee or agent of any other
party to the contract in any capacity or consultant to any other party of the contract with
respect to the subject matter of the contract. Additionally, pursuant to A.R.S. § 38-511, the
County may recoup any fee or commission paid or due to any person significantly involved
in initiating, negotiating, securing, drafting, or creating the contract on behalf of the County
from any other party to the contract arising as the result of the contract.
4.19
OFFSET FOR DAMAGES
In addition to all other remedies at Law or Equity, the County may offset from any money
due to the contractor any amounts contractor owes to the County for damages resulting
from breach or deficiencies in performance of the contract.
4.20
CONTRACTOR LICENSE REQUIREMENT
4.20.1 Contractor shall procure all permits, insurance, and licenses and pay the charges
and fees necessary and incidental to the lawful conduct of his/her business, and,
as necessary, complete any requirements, by any and all governmental or non-
governmental entities as mandated to maintain compliance with and remain in
good standing. The contractor shall keep fully informed of existing and future trade
or industry requirements, and Federal, state, and local laws, ordinances, and
regulations which in any manner affect the fulfillment of a contract and shall comply
with the same. Contractor shall immediately notify both Office of Procurement
Services and the department of any and all changes concerning permits,
insurance, or licenses.
4.20.2 Contractor furnishing finished products, materials, or articles of merchandise that
will require installation or attachment as part of the contract shall possess any
licenses required. Contractor is not relieved of its obligation to obtain and possess
the required licenses by subcontracting of the labor portion of the contract.
Contractors are advised to contact the Arizona Registrar of Contractors, Chief of
Licensing, to ascertain licensing requirements for a particular contract. Contractor
shall identify which license(s), if any, the Registrar of Contractors requires for
performance of the contract.
SERIAL 260056-C
4.21
SUBCONTRACTING
4.21.1 The contractor may not assign to another contractor or subcontract to another
party for performance of the terms and conditions hereof without the written
consent of the County. All correspondence authorizing subcontracting must
reference the bid serial number and identify the job or project.
4.21.2 The subcontractor’s rate for the job shall not exceed that of the prime contractor’s
rate, as bid in the Pricing Sheet, unless the prime contractor is willing to absorb
any higher rates. The subcontractor’s invoice shall be invoiced directly to the prime
contractor, who in turn shall pass-through the costs to the County, without mark-
up. A copy of the subcontractor’s invoice must accompany the prime contractor’s
invoice.
4.22
AMENDMENTS
All amendments to this contract shall be in writing and approved/signed by both parties.
Maricopa County Office of Procurement Services shall be responsible for approving all
amendments for Maricopa County.
4.23
ADDITIONS/DELETIONS OF COMMODITIES
The County reserves the right to add and/or delete materials to a contract. If additional
materials are required from a contract, prices for such additions will be negotiated between
the contractor and the County.
4.24
RIGHTS IN DATA
4.24.1 The County shall have the use of data and reports resulting from a contract without
additional cost or other restriction except as may be established by law or
applicable regulation. Each party shall supply to the other party, upon request, any
available information that is relevant to a contract and to the performance
thereunder.
4.24.2 Data, records, reports, and all other information generated for the County by a third
party as the result of a contract are the property of the County and shall be provided
in a format designated by the County or shall be and remain accessible to the
County into perpetuity.
4.25
ACCESS TO AND RETENTION OF RECORDS FOR THE PURPOSE OF AUDIT AND/OR
OTHER REVIEW
4.25.1 In accordance with Section MC1-372 of the Maricopa County Procurement Code,
the contractor agrees to retain (physical or digital copies of) all books, records,
accounts, statements, reports, files, and other records and back-up documentation
relevant to this contract for six years after final payment or until after the resolution
of any audit questions, which could be more than six years, whichever is longest.
The County, Federal or state auditors and any other persons duly authorized by
the department shall have full access to and the right to examine, copy, and make
use of, any and all said materials.
4.25.2 If the contractor’s books, records, accounts, statements, reports, files, and other
records and back-up documentation relevant to this contract are not sufficient to
support and document that requested services were provided, the contractor shall
reimburse Maricopa County for the services not so adequately supported and
documented.
SERIAL 260056-C
4.26
AUDIT DISALLOWANCES
If at any time it is determined by the County that a cost for which payment has been made
is a disallowed cost, the County will notify the contractor in writing of the disallowance. The
course of action to address the disallowance shall be at sole discretion of the County, and
may include either an adjustment to future invoices, request for credit, request for a check,
or a deduction from current invoices submitted by the contractor equal to the amount of the
disallowance, or to require reimbursement forthwith of the disallowed amount by the
contractor by issuing a check payable to Maricopa County.
4.27
STRICT COMPLIANCE
Acceptance by County of a performance that is not in strict compliance with the terms of
the contract shall not be deemed to be a waiver of strict compliance with respect to all other
terms of the contract.
4.28
VALIDITY
The invalidity, in whole or in part, of any provision of this contract shall not void or affect
the validity of any other provision of the contract.
4.29
SEVERABILITY
The removal, in whole or in part, of any provision of this contract shall not void or affect the
validity of any other provision of this contract.
4.30
RELATIONSHIPS
4.30.1 In the performance of the services described herein, the contractor shall act solely
as an independent contractor, and nothing herein or implied herein shall at any
time be construed as to create the relationship of employer and employee, co-
employee, partnership, principal and agent, or joint venture between the County
and the contractor.
4.30.2 The County reserves the right of final approval on proposed staff. Also, upon
request by the County, the contractor will be required to remove any employees
working on County projects and substitute personnel based on the discretion of
the County within two business days, unless a different time period was previously
approved by the County.
4.31
NON-DISCRIMINATION
Contractor agrees to comply with all provisions and requirements of Arizona Executive
Order 2009-09, including flow down of all provisions and requirements to any
subcontractors. Executive Order 2009-09 supersedes Executive Order 99-4 and amends
Executive Order 75-5 and is hereby incorporated into this contract as if set forth in full
herein. During the performance of this contract, contractor shall not discriminate against
any employee, client, or any other individual in any way because of that person’s age, race,
creed, color, religion, sex, disability, or national origin. (Arizona Executive Order 2009-09
can be viewed at https://apps.azsos.gov/public_services/register/2009/46/governor.pdf).
4.32
WRITTEN CERTIFICATION PURSUANT TO A.R.S. § 35-393.01
If vendor engages in for-profit activity and has 10 or more employees, and if this agreement
has a value of $100,000 or more, vendor certifies it is not currently engaged in and agrees
for the duration of this agreement to not engage in, a boycott of goods or services from
Israel. This certification does not apply to a boycott prohibited by 50 U.S.C. § 4842 or a
regulation issued pursuant to 50 U.S.C. § 4842.
SERIAL 260056-C
4.33
CERTIFICATION REGARDING DEBARMENT AND SUSPENSION
4.33.1 The undersigned (authorized official signing on behalf of the contractor) certifies
to the best of his or her knowledge and belief that the contractor, its current officers,
and directors:
4.33.1.1 are not presently debarred, suspended, proposed for debarment,
declared ineligible, or voluntarily excluded from being awarded any
contract or grant by any United States department or agency or any
state, or local jurisdiction;
4.33.1.2 have not within a three-year period preceding this contract:
4.33.1.2.1 been convicted of fraud or any criminal offense in
connection with obtaining, attempting to obtain, or as the
result of performing a government entity (Federal, state, or
local) transaction or contract; or
4.33.1.2.2 been convicted of violation of any Federal or state antitrust
statutes or conviction for embezzlement, theft, forgery,
bribery, falsification or destruction of records, making false
statements, or receiving stolen property regarding a
government entity transaction or contract;
4.33.1.3 are not presently indicted or criminally charged by a government entity
(Federal, state, or local) with commission of any criminal offenses in
connection with obtaining, attempting to obtain, or as the result of
performing a government entity public (Federal, state, or local)
transaction or contract;
4.33.1.4 are not presently facing any civil charges from any governmental entity
regarding obtaining, attempting to obtain, or from performing any
governmental entity contract or other transaction; and
4.33.1.5 have not within a three-year period preceding this contract had any
public transaction (Federal, state, or local) terminated for cause or
default.
4.33.2 If any of the above circumstances described in the paragraph are applicable to the
entity submitting a bid for this requirement, include with your bid an explanation of
the matter including any final resolution.
4.33.3 The contractor shall include, without modification, this clause in all lower tier
covered transactions (i.e. transactions with subcontractors or sub-subcontractors)
and in all solicitations for lower tier covered transactions related to this contract. If
this clause is applicable to a subcontractor or sub-subcontractor, the contractor
shall include the information required by this clause with their bid.
4.34
VERIFICATION REGARDING COMPLIANCE WITH A.R.S. § 41-4401 AND FEDERAL
IMMIGRATION LAWS AND REGULATIONS
4.34.1 By entering into the contract, the contractor warrants compliance with the
Immigration and Nationality Act (INA using E-Verify) and all other Federal
immigration laws and regulations related to the immigration status of its employees
and A.R.S. § 23-214(A). The contractor shall obtain statements from its
subcontractors certifying compliance and shall furnish the statements to the
procurement officer upon request. These warranties shall remain in effect through
the term of the contract. The contractor and its subcontractors shall also maintain
Employment Eligibility Verification forms (I-9) as required by the Immigration Reform
SERIAL 260056-C
and Control Act of 1986, as amended from time to time, for all employees performing
work under the contract and verify employee compliance using the E-Verify system
and shall keep a record of the verification for the duration of the employee’s
employment or at least three years, whichever is longer. I-9 forms are available for
download at www.uscis.gov.
4.34.2 The County retains the legal right to inspect documents of contractor and
subcontractor employees performing work under this contract to verify compliance
with paragraph 4.34.1 of this section. Contractor and subcontractor shall be given
reasonable notice of the County’s intent to inspect and shall make the documents
available at the time and date specified. Should the County suspect or find that the
contractor or any of its subcontractors are not in compliance, the County will consider
this a material breach of the contract and may pursue any and all remedies allowed
by law, including, but not limited to suspension of work, termination of the contract
for default, and suspension and/or debarment of the contractor. All costs necessary
to verify compliance are the responsibility of the contractor.
4.35
Contractor EMPLOYEE WHISTLEBLOWER RIGHTS AND REQUIREMENT TO INFORM
EMPLOYEES OF WHISTLEBLOWER RIGHTS
4.35.1 The parties agree that this contract and employees working on this contract will be
subject to the contractor employee whistleblower protections established by Title
41 U.S.C. § 4712 and Section 3.908 of the Federal Acquisition Regulation.
4.35.2 Contractor shall inform its employees in writing, in the predominant language of
the workforce, of employee whistleblower rights and protections under 41 U.S.C.
§ 4712, as described in Section 3.908 of the Federal Acquisition Regulation.
Documentation of such employee notification must be kept on file by contractor
and copies provided to County upon request.
4.35.3 Contractor shall insert the substance of this clause, including this paragraph, in all
subcontracts over the simplified acquisition threshold ($250,000 as of Fiscal Year
2018).
4.36
INFLUENCE
4.36.1 As prescribed in MC1-1203 of the Maricopa County Procurement Code, any effort
to influence an employee or agent to breach the Maricopa County Ethical Code of
Conduct or any ethical conduct, may be grounds for disbarment or suspension
under MC1-902.
4.36.2 An attempt to influence includes, but is not limited to:
4.36.2.1 A person offering or providing a gratuity, gift, tip, present, donation,
money, entertainment or educational passes or tickets, or any type of
valuable contribution or subsidy that is offered or given with the intent to
influence a decision, obtain a contract, garner favorable treatment, or
gain favorable consideration of any kind.
4.36.3 If a person attempts to influence any employee or agent of Maricopa County, the
chief procurement officer, or his designee, reserves the right to seek any remedy
provided by the Maricopa County Procurement Code, any remedy in equity or in
the law, or any remedy provided by this contract.
4.36.4 ABSOLUTELY NO CONTACT BETWEEN THE RESPONDENT AND ANY
COUNTY PERSONNEL, OTHER THAN THE OFFICE OF PROCUREMENT
SERVICES, IS ALLOWED DURING THE SOLICITATION PROCESS UNLESS
THE COMMUNICATION IS IN REGARD TO PRE-EXISTING BUSINESS WITH
THE COUNTY. ANY COMMUNICATIONS REGARDING THE SOLICITATION,
SERIAL 260056-C
ITS PARTICIPANTS, OR ANY DOCUMENTATION PRIOR TO THE CONTRACT
AWARD MAY BE GROUNDS FOR DISMISSAL OF THE RESPONDENT FROM
THE EVALUATION PROCESS.
4.37
CONFIDENTIALITY
In the course of the solicitation process, the County may disclose information that is
proprietary or confidential. By submitting a bid to the solicitation, the offeror agrees that,
except as necessary to prepare a response to this solicitation, neither it nor its agents or
employees will communicate, divulge, or disseminate to any third-party persons or entities,
any information that is disclosed to it by the County during the course of these discussions
without the express written authorization of the County. If the offeror does disclose County
proprietary or confidential information to a third party in preparing a response to this
solicitation, it shall require the third party to acknowledge and comply with this provision.
4.38
CONFIDENTIAL INFORMATION
4.38.1 Any information obtained in the course of performing this contract may include
information that is proprietary or confidential to the County. This provision
establishes the contractor’s obligation regarding such information.
4.38.2 The contractor shall establish and maintain procedures and controls that are
adequate to assure that no information contained in its records and/or obtained
from the County or from others in carrying out its functions (services) under the
contract shall be used by or disclosed by it, its agents, officers, or employees,
except as required to efficiently perform duties under the contract. The contractor’s
procedures and controls, at a minimum, must be the same procedures and controls
it uses to protect its own proprietary or confidential information. If, at any time
during the duration of the contract, the County determines that the procedures and
controls in place are not adequate, the contractor shall institute any new and/or
additional measures requested by the County within 15 business days of the
written request to do so.
4.38.3 Any requests to the contractor for County proprietary or confidential information
shall be referred to the County for review and approval, prior to any dissemination.
4.39
PUBLIC RECORDS
Under Arizona law, all offers submitted and opened are public records and must be
retained by the County at the Maricopa County Office of Procurement Services. Offers shall
be open to public inspection and copying after contract award and execution, except for
such offers or sections thereof determined to contain proprietary or confidential information
by the Office of Procurement Services. If an offeror believes that information in its offer or
any resulting contract should not be released in response to a public record request, under
Arizona law, the offeror shall indicate the specific information deemed confidential or
proprietary and submit a statement with its offer detailing the reasons that the information
should not be disclosed. Such reasons shall include the specific harm or prejudice which
may arise from disclosure. The records manager of the Office of Procurement Services
shall determine whether the identified information is confidential pursuant to the Maricopa
County Procurement Code.
4.40
INTEGRATION
This contract represents the entire and integrated agreement between the parties and
supersedes
all
prior
negotiations,
proposals,
communications,
understandings,
representations, or agreements, whether oral or written, expressed, or implied.
SERIAL 260056-C
4.41
UNIFORM ADMINISTRATIVE REQUIREMENTS
By entering into this contract, the contractor agrees to comply with all applicable provisions
of
Title
2,
Subtitle
A,
Chapter
II,
Part
200—UNIFORM
ADMINISTRATIVE
REQUIREMENTS, COST PRINCIPLES, AND AUDIT REQUIREMENTS FOR FEDERAL
AWARDS contained in Title 2 C.F.R. § 200 et seq.
4.42
GOVERNING LAW
This contract shall be governed by the laws of the State of Arizona. Venue for any actions
or lawsuits involving this contract will be in Maricopa County Superior Court, Phoenix,
Arizona.
4.43
FORCED LABOR
4.43.1 By submitting a bid for this solicitation and/or entering into a contract as a result of
this solicitation, contractor agrees to comply with all applicable portions of Arizona
Revised Statutes Section 35-394. Contracting; procurement; prohibition; written
certification; remedy; termination; exception; definitions.
4.43.2 Contractor certifies that it does not currently, and agrees for the duration of the
contract, that it will not use:
4.43.2.1 The forced labor of ethnic Uyghurs in the People’s Republic of China.
4.43.2.2 Any goods or services produced by the forced labor of ethnic Uyghurs
in the People’s Republic of China.
4.43.2.3 Any contractors, subcontractors or suppliers that use the forced labor or
any good or services produced by the forced labor of ethnic Uyghurs in
the People’s Republic of China.
4.43.3 If contractor becomes aware during the term of the agreement that contractor is
not in compliance with this paragraph, the contractor shall notify the County within
five business days after becoming aware of the noncompliance. If the contractor
fails to provide a written certification to the County that the contractor has remedied
the noncompliance within 180 days after notifying the County of its noncompliance,
then the agreement terminates, except that if the agreement termination date
occurs before the end the 180-day period, the agreement terminates on the
agreement termination date.
4.44
UNIQUE ENTITY IDENTIFIER (UEI) AND SYSTEM FOR AWARD MANAGEMENT
REGISTRATION
All
contractors
that
receive
funding
must
have
a
UEI
number
through
https://sam.gov/content/entity-registration. Contractor must also remain maintain current
information and active registration with the System for Award Management (www.sam.gov)
throughout the term of the contract.
4.45
RELIGIOUS ACTIVITIES
The contractor agrees that costs, planned or claimed, including costs incurred, shall not
include any expense for any religious activity.
SERIAL 260056-C
4.46
POLITICAL ACTIVITY PROHIBITED
None of the funds, materials, property, or services contributed by the County or the
contractor under the agreement shall be used in the performance of this agreement for any
partisan political activity, or to further the election or defeat of any candidate for public
office.
4.47
EQUAL EMPLOYMENT OPPORTUNITY
4.47.1 The contractor shall not discriminate against any employee or applicant for
employment because of race, age, disability, color, religion, sex, or national origin.
The contractor shall take affirmative action to ensure applicants are employed and
that employees are treated during employment without regard to their race, age,
disability, color, religion, sex, or national origin. Such action shall include but is not
limited to the following: employment, upgrading, demotion or transfer, recruitment,
or recruitment advertising, lay-off or termination, rates of pay or other forms of
compensation, and selection for training, including apprenticeship.
4.47.2 Contractor shall comply with the following provisions:
4.47.2.1 Title VI and VII of the Civil Rights Act of 1964, as amended (42 U.S.C.
§§ 2000a, et seq.);
4.47.2.2 The Rehabilitation Act of 1973, as amended (29 U.S.C. §§ 701, et seq.);
4.47.2.3 The Age Discrimination in Employment Act of 1967, as amended (29
U.S.C. §§ 621, et seq.);
4.47.2.4 The Americans With Disabilities Act of 1990 (42 U.S.C. §§ 12101, et
seq.); and Arizona Executive Order 2009-09, as amended, et seq. which
mandates that all persons shall have equal access to employment
opportunities.
4.47.2.5 Contractor understands that the United States has the right to seek
judicial enforcement of this assurance.
4.48
CERTIFICATION REGARDING LOBBYING
4.48.1 Contractor certifies, to the best of their knowledge and belief, that:
4.48.1.1 No federal appropriated funds have been paid or will be paid, by or on
behalf of the contractor, to any person for influencing or attempting to
influence an officer or employee of any agency. This applies to a
Member of Congress, an officer or employee of Congress, or an
employee of a Member of Congress in connection with the awarding of
any federal contract, the making of any federal grant. Including the
making of any federal, loan the entering into of any cooperative
agreement, and the extension, continuation, renewal, amendment, or
modification of any federal contract, grant, loan, or cooperative
agreement.
4.48.2 If any funds other than federal appropriated funds, have been paid or will be paid
to any person for influencing or attempting to influence an officer or employee of
any agency, member of Congress, an officer or employee of Congress, or an
employee of a member of Congress in connection with this federal contract, grant,
loan, or cooperative agreement, the undersigned shall complete and submit
Standard Form-LLL, “Disclosure Form to Report Lobbying,” in accordance with its
instructions.
SERIAL 260056-C
4.48.3 Contractor shall include Lobbying Certification language in the award documents
for all subcontractors (including sub-grants, and contract under grants, loans, and
cooperative agreements) and that all sub-recipients shall certify and disclose
accordingly.
4.48.3.1 The Lobbying Certification is a material representation of fact upon
which reliance was placed when this transaction is made or entered into.
Submission of this certification is prerequisite for making or entering into
this transaction imposed by section 1352, Title 31, U.S. Code. Any
successful proposer(s) who fail to file the required certification shall be
subject to a civil penalty of not less than $10,000.00 and not more than
$100,000.00 for each such failure.
4.49
CLEAN AIR ACT & CLEAN WATER ACT
Contractor must comply with all applicable standards, orders, or requirements issued under
section 306 of the Clean Air Act (42 U.S.C. 7606), section 508 of the Clean Water Act (33
U.S.C. 1368) Executive Order 11738, and Environmental Protection Agency regulations.
4.50
ENERGY POLICY AND CONSERVATION ACT
Contractor must adhere to the standards and policies relating to energy efficiency, which
are contained in the State energy conservation plan issued in compliance with the Energy
Policy and Conservation Act (Pub. L. 94-163, 89 Stat.871).
4.51
CONTRACT DISPUTES
All Contract disputes will be handled in accordance with the Maricopa County Procurement
Code, MCI-906.