260052-CONTRACT-TRUSTPOINT SYSTEMS INC,.PDF
Extracted text (via pymupdf)
105512 characters
CONTRACT CONNECTED VEHICLE ACCELERATION ZONE
(CVAZ) MESSAGE EXCHANGE PLATFORM & MOBILE
DEVICE APPLICATION 260052-RFP
This contract is entered into this 11th day of February, 2026 by and between Maricopa County (County), a
political subdivision of the State of Arizona, and Trustpoint Systems Inc, a Virginia corporation (Contractor)
for the purchase of a complete Network-V2X Message Exchange Platform (MEP) and a mobile device
application that sends and receives SAE J2735 messages to and from the MEP.
1.0
CONTRACT TERM
This contract is for a term of four years, beginning on the 11th of February, 2026 and ending the
31st of January, 2030.
2.0
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 four additional year(s), (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.
3.0
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.
4.0
PRICE ADJUSTMENTS
Any requests for reasonable price adjustments must be submitted 60 calendar days prior to
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 shall 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.
5.0
PAYMENTS
5.1
As consideration for performance of the duties described herein, County shall pay
Contractor the sum(s) stated in Exhibit A – Vendor Information and Pricing.
SERIAL# 260052-RFP
5.2
Payment shall be made upon the County’s receipt of a properly completed invoice.
5.3
Hardware, training and testing will be paid upon completion and acceptance.
5.4
The initial four years of the software will be paid during the first year of the contract.
5.5
INVOICES
5.5.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
•
Project name and/or number
•
Invoice number and date
•
Payment terms
•
Date of service or delivery
•
Quantity
•
Contract item number(s)
•
Arrival and completion time
•
Description of purchase (product or services)
•
Cost share percentage and back up documentation
•
Pricing per unit of purchase
•
Extended price
•
Freight (if applicable)
•
Mileage with rate (if applicable)
•
Total amount due
•
Build America/Buy America Certifications (if applicable)
5.5.2
Problems regarding billing or invoicing shall be directed to the department as listed
on the purchase order.
5.5.3
Payment shall 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 Web Site (https://www.maricopa.gov/5169/Vendor-Information).
5.5.4
Discounts offered in the contract shall be calculated based on the date a properly
completed invoice is received by the County.
5.5.5
Participate in cost sharing by furnishing an in-kind match of 20 percent of each
system (MEP and/or MD). In-kind match must meet federal requirements
applicable to the Accelerating V2X Deployment grant.
5.5.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.
5.6
APPLICABLE TAXES
5.6.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.
SERIAL# 260052-RFP
5.6.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 www.azdor.gov/business. 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 over payment of a project
due to tax consideration that was not due, the contractor will 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.
5.6.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).
6.0
AVAILABILITY OF FUNDS
6.1
The provisions of this contract relating to payment for services 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 shall keep the
Contractor fully informed as to the availability of funds.
6.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
shall 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 shall give written notice of the effective date of any suspension,
amendment, or termination under this section, at least 10 days in advance.
7.0
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 contractor’s 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.
8.0
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
SERIAL# 260052-RFP
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.
9.0
DUTIES
9.1
The Contractor shall perform all duties stated in Exhibit B – Scope of Work, or as otherwise
directed in writing by the procurement officer.
10.0
TERMS AND CONDITIONS
10.1
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.
10.1.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.
10.1.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.
10.1.3 The scope of this indemnification does not extend to the sole negligence of County.
10.2
INFRINGEMENT DEFENSE AND INDEMNIFICATION
10.2.1 Definitions
For purposes of this section:
10.2.1.1 “Claim” means any cause of action in a third-party action, suit, or
proceeding against County alleging that Contractor software, or its
upgrades, modifications, or revisions, as of its delivery date under this
agreement, infringes a valid U.S. patent, copyright, or trademark.
10.2.1.2 “Participate and Share in the Costs” means Contractor will assist the
County in the defense of the Claim, to the extent agreed to by the
parties, except that Contractor shall be solely responsible for any and all
costs adjudged in a successful Claim against the County.
10.2.1.3 “Third-Party Products” means any products made by a party other than
Contractor, and may include, without limitation, products ordered by
SERIAL# 260052-RFP
County from third parties. However, components of Contractor branded
products are not Third-Party Products if they are both:
10.2.1.4 embedded in Third-Party Products (i.e., not recognizable as standalone
items); and
10.2.1.5 not identified as separate items on Contractor’s price list, quotes, order
specifications forms, or documentation.
10.2.2 Defense and Indemnity
Contractor shall defend, and Participate and Share in the Cost, in the full defense
of the County against any Claim, and will indemnify and hold harmless the County,
as provided for in this section, for any judgments, settlements, and court awarded
attorney’s fees resulting from a Claim where the claimant is adjudged the
successful party in the Claim. Contractor’s obligations under this section are
conditioned on the following:
10.2.2.1 County promptly notifies Contractor of the Claim, in writing, upon being
made aware of the Claim;
10.2.2.2 County gives Contractor lead authority control of the defense and (if
applicable) settlement of the Claim, provided that County’s legal counsel
may participate in such defense and settlement, at County’s expense;
and
10.2.2.3 County provides all information and assistance reasonably requested by
Contractor to handle the defense or settlement of the Claim.
10.2.3 Remedial Measures
10.2.3.1 If software becomes, or Contractor reasonably believes use of software
may become, the subject of a Claim, Contractor may, at its own expense
and option:
10.2.3.1.1 procure for County the right to continue use of the product;
10.2.3.1.2 replace or modify the software; or
10.2.3.2 to the extent that neither 10.2.3.1.1 nor 10.2.3.1.2 are deemed
commercially practicable, refund to County a pro-rated portion of the
applicable fees for software based on a linear depreciation monthly over
a 10-year useful life, in which case County will cease all use of software
and return it to Contractor.
10.2.4 Exceptions
Contractor will have no defense or indemnity obligation for any Claim based on:
10.2.4.1 modifications by someone other than Contractor;
10.2.4.2 software has been modified by Contractor in accordance with County-
provided specifications or instructions;
10.2.4.3 use or combination by the County of software with Third-Party Products,
open source, or freeware technology;
10.2.4.4 Third-Party Products, open source, or freeware technology;
SERIAL# 260052-RFP
10.2.4.5 a product that is used or located by County in a country other than the
country in which or for which it was supplied by Contractor;
10.2.4.6 possession or use of a product after Contractor has informed County of
modifications or changes required to avoid such Claim and offered to
implement those modifications or changes, if such Claim would have
been avoided by implementation of Contractor's suggestions and to the
extent County did not provide Contractor with a reasonable opportunity
to implement Contractor's suggestions; or
10.2.4.7 the amount of revenue or profits earned, or other value obtained by the
use of products, or the amount of use of the products.
10.2.5 The foregoing states Contractor’s entire liability, and County’s sole and exclusive
remedy, except as provided by law or equity, with respect to any infringement or
misappropriation of any intellectual property rights of another party.
10.3
INSURANCE
10.3.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.
10.3.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.
10.3.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.
10.3.4 Contractor’s insurance shall be primary insurance as respects County, and any
insurance or self-insurance maintained by County shall not contribute to it.
10.3.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.
10.3.6 The insurance policies may provide coverage that contains deductibles or self-
insured retentions. Such deductible 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.
10.3.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.
SERIAL# 260052-RFP
10.3.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.
10.3.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.
10.3.9.1 Commercial General Liability
Commercial General Liability (CGL) insurance and, if necessary,
Commercial Umbrella insurance with a limit of not less than $1,000,000
for each occurrence, $2,000,000 Products/Completed Operations
Aggregate, and $2,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.
10.3.9.2 Automobile Liability
Commercial/Business Automobile Liability insurance with a combined
single limit for bodily injury and property damage of not less than
$1,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.
10.3.9.3 Workers’ Compensation
10.3.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.
10.3.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.
10.3.9.4 Errors and Omissions/Professional Liability Insurance
Contractor shall maintain Professional Liability insurance which will
provide coverage for any and all acts arising out of the work or services
performed by the contractor under the terms of this contract, with a limit
SERIAL# 260052-RFP
of not less than $1,000,000 for each claim, and $2,000,000 aggregate
claims.
10.3.9.5 Cyber, Network Security, and Privacy Liability
Cyber, Network Security and Privacy Liability Insurance with a limit of
not less than $2,000,000 per occurrence. The policy shall include, but
not be limited to; coverage for all directors, officers, agents and
employees of the Contractor, losses with respect to network risks (such
as data breaches, unauthorized access or use, and ID theft of data),
invasion of privacy (regardless of the type of media involved in the loss
of private information), crisis management, identity theft response costs,
breach notification costs, credit remediation, and credit monitoring,
defense, and claims expenses, regulatory defense costs plus fines and
penalties, cyber extortion, electronic data restoration expenses (data
asset protection), network business interruption, computer fraud
coverage, funds transfer loss, third-party fidelity, theft, no requirement
for arrest and conviction, and loss outside the premises of the named
insured.
10.3.10 Certificates of Insurance
10.3.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.
10.3.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.
10.3.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.
10.3.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
10.3.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 days
prior written notice to Maricopa County. Contractor must provide 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# 260052-RFP
10.4
FORCE MAJEURE
10.4.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.
10.4.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.
10.4.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.
10.5
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.
10.6
PROCUREMENT CARD ORDERING CAPABILITY
County may opt to use a procurement card (Visa or Master Card) to make payment for
orders under this contract.
10.7
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.
10.8
PURCHASE ORDERS
10.8.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.
10.8.2 Contractor agrees to accept verbal notification of cancellation of purchase orders
from the County procurement officer with written notification to follow. Contractor
specifically acknowledges to be bound by this cancellation policy.
SERIAL# 260052-RFP
10.9
BACKGROUND CHECK
Respondents 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, and the failure to pass
these checks shall deem the respondent non-responsible.
10.10
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.
10.11
STOP WORK ORDER
10.11.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:
10.11.1.1 cancel the stop work order; or
10.11.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.
10.11.1.3 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
10.12
TERMINATION FOR CONVENIENCE
Maricopa County may terminate the resultant contract for convenience by providing 60
calendar days advance notice to the Contractor.
10.13
TERMINATION FOR DEFAULT
10.13.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:
10.13.1.1 deliver the supplies or to perform the services within the time specified
in this contract or any extension;
10.13.1.2 make progress, so as to endanger performance of this contract; or
10.13.1.3 perform any of the other provisions of this contract.
SERIAL# 260052-RFP
10.13.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.
10.14
PERFORMANCE
It shall be the Contractor’s responsibility to meet the proposed performance requirements.
Maricopa County reserves the right to obtain services on the open market in the event the
Contractor fails to perform, and any price differential will be charged against the Contractor.
10.15
CONTRACTOR EMPLOYEE MANAGEMENT
10.15.1 Contractor shall endeavor to maintain the personnel proposed in their proposal
throughout the performance of this contract.
10.15.2 If Contractor personnel’s employment status changes, Contractor shall provide
County a list of proposed replacements with equivalent or greater experience.
10.15.3 Under no circumstances shall the implementation schedule to be impacted by a
personnel change on the part of the Contractor.
10.15.4 Contractor shall not reassign any key personnel identified in their proposal without
the express consent of the County.
10.15.5 County reserves the right to immediately remove from its premises any Contractor
personnel it determines to be a risk to County operations.
10.15.6 County reserves the right to request the replacement of any Contractor personnel
at any time, for any reason.
10.16
TRAINING
Contractor shall provide training services to completely train four 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.
10.17
WARRANTY OF SERVICES
10.17.1 The Contractor warrants that all services provided hereunder will conform to the
requirements of the contract, including all descriptions, specifications, and
attachments made a part of this contract. County’s acceptance of services or
goods provided by the Contractor shall not relieve the Contractor from its
obligations under this warranty.
10.17.2 In addition to its other remedies, County may, at the Contractor's expense, require
prompt correction of any services failing to meet the Contractor's warranty herein.
Services corrected by the Contractor shall be subject to all the provisions of this
contract in the manner and to the same extent as services originally furnished
hereunder.
10.18
INSPECTION OF SERVICES
10.18.1 The Contractor shall provide and maintain an inspection system acceptable to
County covering the services under this contract. Complete records of all
inspection work performed by the Contractor shall be maintained and made
available to County during contract performance and for as long afterwards as the
contract requires.
SERIAL# 260052-RFP
10.18.2 County has the right to inspect and test all services called for by the contract, to
the extent practicable at all times and places during the term of the contract.
County shall perform inspections and tests in a manner that will not unduly delay
the work.
10.18.3 If any of the services do not conform to contract requirements, County may require
the Contractor to perform the services again in conformity with contract
requirements, at no cost to the County. When the defects in services cannot be
corrected by re-performance, County may:
10.18.3.1 require the Contractor to take necessary action to ensure that future
performance conforms to contract requirements; and
10.18.3.2 reduce the contract price to reflect the reduced value of the services
performed.
10.18.4 If the Contractor fails to promptly perform the services again or to take the
necessary action to ensure future performance in conformity with contract
requirements, County may:
10.18.4.1 by contract or otherwise, perform the services and charge to the
Contractor, through direct billing or through payment reduction, any cost
incurred by County that is directly related to the performance of such
service; or
10.18.4.2 terminate the contract for default.
10.19
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.
10.20
STATUTORY RIGHT OF CANCELLATION FOR CONFLICT OF INTEREST
Notice is given that, pursuant to 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.
10.21
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.
SERIAL# 260052-RFP
10.22
SUBCONTRACTING
10.22.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.
10.22.2 The subcontractor’s rate for the job shall not exceed that of the prime Contractor’s
rate, as bid in the pricing section, 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.
10.23
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.
10.24
ADDITIONS/DELETIONS OF REQUIREMENTS
The County reserves the right to add and/or delete materials and services to a contract. If
a service requirement is deleted, payment to the Contractor will be reduced proportionately,
to the amount of service reduced in accordance with the bid price. If additional materials
or services are required from a contract, prices for such additions will be negotiated
between the Contractor and the County.
10.25
RIGHTS IN DATA
10.25.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.
10.25.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.
10.26
ACCESS TO AND RETENTION OF RECORDS FOR THE PURPOSE OF AUDIT AND/OR
OTHER REVIEW
10.26.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.
10.26.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# 260052-RFP
10.27
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 shall 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.
10.28
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.
10.29
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.
10.30
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.
10.31
RELATIONSHIPS
10.31.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.
10.31.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.
10.32
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)
10.33
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# 260052-RFP
10.34
CERTIFICATION REGARDING DEBARMENT AND SUSPENSION
10.34.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:
10.34.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;
10.34.1.2
have not within a three-year period preceding this
contract:
10.34.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
10.34.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;
10.34.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;
10.34.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
10.34.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.
10.34.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.
10.34.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.
10.35
VERIFICATION REGARDING COMPLIANCE WITH A.R.S. § 41-4401 AND FEDERAL
IMMIGRATION LAWS AND REGULATIONS
10.35.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
SERIAL# 260052-RFP
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
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.
10.35.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 10.35.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.
10.36
Contractor EMPLOYEE WHISTLEBLOWER RIGHTS AND REQUIREMENT TO INFORM
EMPLOYEES OF WHISTLEBLOWER RIGHTS
10.36.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.
10.36.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.
10.36.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).
10.37
CONTRACTOR LICENSE REQUIREMENT
10.37.1 The 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
the Office of Procurement Services and the department of any and all changes
concerning permits, insurance, or licenses.
10.37.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# 260052-RFP
10.38
INFLUENCE
10.38.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.
10.38.2 An attempt to influence includes, but is not limited to:
10.38.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.
10.38.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.
10.39
CONFIDENTIAL INFORMATION
10.39.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.
10.39.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.
10.39.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.
10.40
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.
10.41
INTEGRATION
SERIAL# 260052-RFP
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.
10.42
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.
10.43
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.
10.44
FORCED LABOR
10.44.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.
10.44.2 Contractor certifies that it does not currently, and agrees for the duration of the
contract, that it will not use:
10.44.2.1 The forced labor of ethnic Uyghurs in the People’s Republic of China.
10.44.2.2 Any goods or services produced by the forced labor of ethnic Uyghurs
in the People’s Republic of China.
10.44.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.
10.44.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.
10.45
PRICES
Contractor warrants that prices extended to County under this contract are no higher than
those paid by any other customer for these or similar services.
10.46
ORDER OF PRECEDENCE
In the event of a conflict in the provisions of this contract and Contractor’s license
agreement, if applicable, the terms of this contract shall prevail.
10.47
UNIQUE ENTITY IDENTIFIER (UEI) AND SYSTEM FOR AWARD MANAGEMENT
REGISTRATION
SERIAL# 260052-RFP
All contractors must have a UEI number through https://sam.gov/content/entity-
registration. Contractor must also maintain current information and active registration with
the System for Award Management (www.sam.gov) throughout the term of the contract.
10.48
RELIGIOUS ACTIVITIES
The contractor agrees that costs, planned or claimed, including costs incurred, shall not
include any expense for any religious activity.
10.49
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.
10.50
EQUAL EMPLOYMENT OPPORTUNITY
10.50.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.
10.50.2 Contractor shall comply with the following provisions:
10.50.2.1 Title VI and VII of the Civil Rights Act of 1964, as amended (42 U.S.C.
§§ 2000a, et seq.);
10.50.2.2 The Rehabilitation Act of 1973, as amended (29 U.S.C. §§ 701, et
seq.);
10.50.2.3 The Age Discrimination in Employment Act of 1967, as amended
(29U.S.C. §§ 621, et seq.);
10.50.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.
10.50.3 Contractor understands that the United States has the right to seek judicial
enforcement of this assurance.
10.51
CERTIFICATION REGARDING LOBBYING
10.51.1 Contractor certifies, to the best of their knowledge and belief, that:
10.51.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
SERIAL# 260052-RFP
modification of any federal contract, grant, loan, or cooperative
agreement.
10.51.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.
10.51.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.
10.51.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.
10.52
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.
10.53
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).
10.54
CONTRACT DISPUTES
All Contract disputes will be handled in accordance with the Maricopa County Procurement
Code, MCI-906
10.55
INCORPORATION OF DOCUMENTS
10.55.1 The following are to be attached to and made part of this Contract:
10.55.1.1
Exhibit A – Vendor Information and Pricing
10.55.1.2
Exhibit B – Scope of Work
10.55.1.3
Exhibit C – Minimum System Requirements for MEP and MED
10.55.1.4
Exhibit D – MCDOT Supplemental Terms and Conditions
10.56
NOTICES
All notices given pursuant to the terms of this contract shall be addressed to:
For County:
SERIAL# 260052-RFP
Maricopa County
Office of Procurement Services
301 W. Jefferson St. Suite 700
Phoenix, Arizona 85003-1647
For Contractor:
Trustpoint Systems, Inc
11328 Hall Road
Lewes, DE 19958
10.57
INQUIRIES
10.57.1 Administrative telephone/email inquiries shall be addressed to:
ABBY WEEDA, JR PROCUREMENT OFFICER
TELEPHONE: (602) 506-8711
Abigail.Weeda@maricopa.gov
10.57.2 Inquiries may be submitted by telephone but must be followed up in writing. No
oral communication is binding on Maricopa County.
SERIAL# 260052-RFP
IN WITNESS WHEREOF, this contract is executed on the date set forth above.
CONTRACTOR
AUTHORIZED SIGNATURE
PRINTED NAME AND TITLE
ADDRESS
DATE
MARICOPA COUNTY
CHAIRMAN, BOARD OF SUPERVISORS
DATE
ATTESTED:
CLERK OF THE BOARD
DATE
APPROVED AS TO FORM:
DEPUTY COUNTY ATTORNEY
DATE
-RVHSK$.RVKXWD*HQHUDO0DQDJHU
+DOO5RDG/HZHV'(
CHAIR, BOARD OF SUPERVISORS
Joseph A Koshuta
Digitally signed by Joseph A
Koshuta
Date: 2026.01.22 11:20:31 -05'00'
SERIAL# 260052-RFP
EXHIBIT A – VENDOR INFORMATION AND PRICING
COMPANY NAME:
Trustpoint Systems, Inc.
DOING BUSINESS AS (dba):
MAILING ADDRESS:
11328 Hall Road
Lewes, DE 19958
REMIT TO ADDRESS:
11328 Hall Road
Lewes, DE 19958
TELEPHONE NUMBER:
703-362-5757
WWW ADDRESS:
https://www.trustpointsystems.com/
CONTACT NAME:
Joseph A Koshuta
CONTACT TELEPHONE NUMBER:
703-362-5757
CONTACT EMAIL ADDRESS:
jkoshuta@trustpointsystems.com
UNIQUE ENTITY IDENTIFIER (UEI)
R8JXN4YLGZY3
NET 30 DAYS
PRICING
1.0 Message Exchange Platform (MEP)
Price shall be all inclusive for the initial term of four
years.
Cost ($)
In-kind
match (%)
1.1 Hardware
included
0%
1.2 Software - 48 months of MEP = National Mobility
Interchange + TrafficAuth-Authority license (ISS Hosted)
$ 456,000.00
20%
1.3 Installation
included
0%
1.4 Training
included
0%
1.5 Testing
included
0%
1.6 Warranty
included
0%
1.7 48 Months of Support, Integration & Training Services
for National Mobility Interchange + TA-Authority + TA
Mobile
$ 107,730.00
20%
Subtotal
$ 563,730.00
20%
2.0 Mobile Device Application (MD)
Price shall be all inclusive for the initial term of four
years.
Cost ($)
In-kind match
(%)
2.1 Hardware
included
0%
2.2 Software - 48 Months of MD = TrafficAuth Mobile
Application licensing (100 licenses on Android or Iphone)
$ 38,000.00 20%
2.3 Installation
included 0%
2.4 Training
included 0%
SERIAL# 260052-RFP
2.5 Testing
included
0%
2.6 Warranty
included 0%
Subtotal $ 38,000.00 20%
Total cost for MEP and MD
$ 601,730.00
Total cost for MEP and MD with in-kind match applied
$ 481,384.00
3.0 Additional Training
If requested by Maricopa County
3.1 Additional Training for MEP
210 /hr.
3.2 Additional Training for Mobile Device Application
210 /hr.
SERIAL# 260052-RFP
EXHIBIT B – SCOPE OF WORK
1.0
SCOPE OF WORK
1.1
MESSAGE EXCHANGE PLATFORM (MEP)
1.1.1
The Network-V2X MEP will be a center-based system that enables the exchange
of V2X messages between roadside equipment, such as traffic signal controllers,
and mobile devices using existing Fourth Generation/Fifth Generation (4G/5G)
cellular communication systems. The MEP shall utilize intelligent message
distribution methods, such as geohashing, to efficiently determine which mobile
device should receive specific messages based on their geographic location.
1.1.2
The MEP shall seamlessly integrate with Connected Vehicle Acceleration Zone
(CVAZ) system components, providing real-time access to traffic signal controller
data and the ability to support signal priority and preemption requests from mobile
devices and send vulnerable road user (VRU) notifications and position correction
messages to mobile devices.
1.1.3
As the central Network-V2X communications hub for the CVAZ, the MEP shall
deliver the infrastructure needed to enable the CVAZ target applications via cellular
communications.
1.1.4
See Exhibit C for the minimum system requirements.
1.1.5
Configuration
1.1.5.1
CVAZ Roadside Processors (RSP) will send Signal Phase and Timing
(SPaT), MAP, Signal Status Messages (SSM), and Sensor Data Sharing
Messages (SDSM) to the MEP in near-real time. Mobile device
applications will “check-in” to the MEP on a predefine interval (e.g. once
a second). The MEP will send messages to the mobile device based on
the device’s location.
1.1.5.2
Transit and Freight vehicle mobile devices will send Signal Request
Messages (SRM) to the MEP as they approach a CVAZ intersection that
supports Transit Signal Priority (TSP) or Freight Signal Priority (FSP).
The MEP will send the SRM to the RSP at the applicable CVAZ
intersection(s). The RSP will determine if the mobile device is authorized
to receive signal priority. The RSP sends SSMs to the MEP in response
to SRMs. The MEP sends SSMs to the mobile device that requested
signal priority.
1.1.5.3
When VRUs are detected, the RSP will send SDSMs to the MEP. The
MEP shall send SDSMs to mobile devices in the vicinity of the VRU to
notify mobile device users, as needed.
1.1.5.4
Figure 1 depicts the high-level CVAZ system architecture. The MEP is
circled in red.
SERIAL# 260052-RFP
Figure 1: High Level CVAZ System Architecture: MEP and Mobile Device
1.2
LOCATION OF WORK
1.2.1
The 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.
1.2.2
Emergency Vehicle Preemption (EVP), Transit Signal Priority (TSP), Vulnerable
Road Use (VRU) Safety, and Freight Signal Priority (FSP) V2X applications will be
supported.
1.2.2.1
EVP Intersections are located along major thoroughfares, which are
generally spaced at one-mile increments within the regional street
network.
1.2.2.2
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.
1.2.2.3
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.
1.2.2.4
FSP intersections are those along local and regionally significant freight
corridors, as identified by the MAG 2017 regional freight study.
1.3
DEPLOYMENT
SERIAL# 260052-RFP
1.3.1
A total of 650 Roadside Units (RSUs) will be deployed at signalized intersections.
1.3.1.1
all 650 will support EVP,
1.3.1.2
200 intersections will support TSP,
1.3.1.3
75 intersections will support VRU safety,
1.3.1.4
75 intersections will support FSP,
1.3.1.5
an additional 100 intersections will support Network-V2X using a
Message Exchange Platform (MEP).
1.3.2
See Figure 2 below for a depiction of the deployment area.
Figure 2: CVAZ Deployment Area
1.4
MOBILE DEVICE APPLICATION (MD)
1.4.1
The CVAZ Mobile Device (MD) application will be utilized by partner vehicle
operators to request signal priority from CVAZ intersections. The application will
also provide alerts to the vehicle operator when there is potential for a VRU to
cross paths with the vehicle. The application will receive infrastructure messages
from the MEP, providing similar functionality as On-Board Unit (OBUs), for
interactions with V2X infrastructure.
1.4.2
The MD application shall be delivered as a Beta version of both Android and
iPhone Operating System (iOS) applications for testing and the delivery of the final
versions of the Android and iOS application for user distribution.
1.4.3
See Exhibit C for the minimum system requirements.
1.4.4
Configuration
1.4.4.1
The MD application shall be developed for both Android and iOS
Operating Systems.
SERIAL# 260052-RFP
1.4.4.2
To minimize unintended use, only authorized users designated by
MCDOT will be able to download and create an account for CVAZ signal
priority. Simulated payment information will be required to create an
account for FSP.
1.4.4.3
The MD will “check-in” to the MEP on a predefine interval (e.g. once a
second). The MEP will send SAE J2735 Signal Phase and Timing
(SPaT), MAP, and Sensor Data Sharing Messages (SDSM) to the MD
based on the device’s location. When approaching a CVAZ intersection,
the MD will generate and send a Signal Request Message (SRM) to the
MEP to request signal priority from the upcoming intersection. The MD
will notify the vehicle operator of the status of the signal priority request
(granted, denied, etc.) based on the SSM received from the MEP.
1.4.4.3.1
For FSP, the MD shall have a mechanism to allow the
vehicle operator to turn signal priority requests “off”. This
will provide the simulation of the vehicle operator not
wanting to pay for signal priority.
1.4.4.4
The MD will receive SDSMs from the MEP based on the location of the
device. If a VRU is near the location of the vehicle, the MD will provide
an alert to the operator, notifying them of the potential threat.
1.4.4.5
See Figure 3 below for the high level CVAZ system architecture with the
mobile device circled in blue.
ZŽĂĚƐŝĚĞ
WƌŽĐĞƐƐŽƌ
^WĂdͰDWͰ
^^DͰ^^D
^DͰ^ZD
^ĞĐƵƌŝƚLJƌĞĚĞŶƚŝĂů
DĂŶĂŐĞŵĞŶƚ^LJƐƚĞŵ
ĞƌƚŝĨŝĐĂƚĞ
ƌĞƋƵĞƐƚͰĚŽǁŶůŽĂĚ
sϮyDĂŶĂŐĞŵĞŶƚ
^LJƐƚĞŵ
ŽŵŵĂŶĚΘŽŶƚƌŽů
dƌĂŶƐŝƚsĞŚŝĐůĞ
&ƌĞŝŐŚƚsĞŚŝĐůĞ
sϮyZŽĂĚƐŝĚĞhŶŝƚ
ŵĞƌŐĞŶĐLJsĞŚŝĐůĞ
^DͰ^ZD
^DͰ^ZD
t^Ͱ^WĂdͰDWͰ^^DͰ^^D
sZhĚĞƚĞĐƚŝŽŶĚĂƚĂ
dƌĂĨĨŝĐ^ŝŐŶĂůŽŶƚƌŽůůĞƌ
^WĂdĂƚĂ
WƌŝŽƌŝƚLJ
^ŝŐŶĂůŽŶƚƌŽů
sZhĞƚĞĐƚŝŽŶ
^ĞŶƐŽƌƐ
sZh
DĞƐƐĂŐĞ džĐŚĂŶŐĞ
WůĂƚĨŽƌŵ
^WĂdͰDWͰ
^^DͰ^^D
^ZD
DŽďŝůĞĞǀŝĐĞ
KZ^
ŽŵŵĂŶĚΘŽŶƚƌŽů
WŽƐŝƚŝŽŶŽƌƌĞĐƚŝŽŶ
^ZD
ĞƌƚŝĨŝĐĂƚĞ
ƌĞƋƵĞƐƚͰĚŽǁŶůŽĂĚ
^WĂdͰDWͰ
^^DͰ^^D
ĞƌƚŝĨŝĐĂƚĞ
ƌĞƋƵĞƐƚͰĚŽǁŶůŽĂĚ
sϮyƵƚŚŽƌŝnjĂƚŝŽŶĂŶĚ
WĂLJŵĞŶƚ^LJƐƚĞŵ
ƵƚŚŽƌŝnjĂƚŝŽŶ
sĞƌŝĨŝĐĂƚŝŽŶ
^D
Figure 3: High Level CVAZ System Architecture: Mobile Device
SERIAL# 260052-RFP
1.5
IMPLEMENTATION
1.5.1
Any travel-related expenses will be incidental. No payment will be made for travel
charges.
1.5.2
Contractor shall ensure initial implementation includes the following elements:
1.5.2.1
Contractor shall assign to the County a dedicated implementation
manager (can be the account manager) assigned to guide the
implementation process through the go-live period, and who shall act as
the County’s liaison for all activities associated with the implementation.
1.5.2.2
Contractor’s implementation shall include but not be limited to, project
milestones; testing; training procedures; meeting schedule, and review
timeline for the County. The implementation plan must be approved by
the County before the project may commence.
1.5.2.3
The County will own and have access to any data collected by the
system.
1.5.2.4
Contractor shall fix any issues or “bugs” that may be identified during
implementation and retest the system after issues are fixed. Resolution
of these issues shall be a prerequisite for the County’s approval.
1.5.2.5
Contractor shall provide any hardware required to operate the MEP or
Mobile Application. Equipment will require review by County staff to
ensure compatibility with technical systems. Hardware shall be provided
with Build America/Buy America certifications as needed.
1.5.3
Initial Testing and Acceptance
1.5.3.1
Contractor shall test the system before the County will start acceptance
tests.
1.5.3.2
The County will notify the contractor in writing of the acceptance of the
system when:
1.5.3.2.1
County determines the system functions as necessary per
the scope of work.
1.5.3.2.2
Contractor has completed all training requirements.
1.5.3.2.3
Contractor has provided all documentation and other
deliverables.
1.5.3.2.4
All other acceptance conditions defined in the contract
documents have been met.
1.5.3.3
Refer to section 1.10 for full acceptance criteria.
1.5.4
Initial Customer Support and Training
1.5.4.1
Contractor shall provide user training on all installed systems.
1.5.4.2
Contractor shall provide an end-user manual and technical
documentation. User’s manual shall include step-by-step instructions for
all major system functions.
1.6
SYSTEM SUPPORT AND MAINTENANCE
SERIAL# 260052-RFP
1.6.1
Ongoing Support Services
1.6.1.1
Contractor shall work with MCDOT to provide ongoing maintenance of
all system software.
1.6.1.2
Support shall be available Monday through Friday from 7:00 a.m. to 6:00
p.m. MST. Service shall be toll-free, live, English-speaking customer
service telephone support.
1.6.1.3
If an issue occurs within standard business hours, the contractor shall
address issues that can be fixed through remote internet access within
one hour.
1.6.1.3.1
Standard business hours are between the hours of
6:00 a.m. and 6:00 p.m., MST, Monday through Friday,
excluding County holidays.
1.6.1.3.1.1 County holidays are New Years Day, MLK Day,
President’s Day, Memorial Day, Independence
Day, Labor Day, Veteran’s Day, Thanksgiving
Day, Day after Thanksgiving, and Christmas
Day.
1.6.1.4
If an issue is reported after 6:00 p.m. MST, on weekends, or on a County
holiday, the issue shall be addressed no later than 8:00 a.m. MST the
following business day.
1.6.2
System Updates
Contractor shall provide regular system updates to ensure that the system
software, including all third-party software, shall be the manufacturer’s “current”
version.
1.7
MINIMUM CONTRACTOR REQUIREMENTS
1.7.1
Contractor shall provide documentation of prior experience running/operating a
MEP.
1.7.2
Contractor shall provide documentation of prior experience with mobile application
integration with MEP services.
1.8
FUNDING
1.8.1
This procurement is funded in whole or in part through the U.S. Department of
Transportation (USDOT) under the program titled Saving Lives with Connectivity:
Accelerating Vehicle-to-Everything (V2X) Deployment.
1.8.2
Assistance Listing Number (ALN) Funding Catalog
1.8.2.1
The ALN (formally known as Catalog of Federal Domestic Assistance
(CFDA) number) is a government-wide collection of Federal programs,
projects, services, and activities that provide assistance or benefits to
the American public. The catalog contains financial and nonfinancial
assistance programs administered by departments and establishments
of the Federal government.
SERIAL# 260052-RFP
1.8.2.2
Activities under this solicitation are supported by the following Federal
Assistance Listing Number (ALN): ALN 20.200 – Highway Research and
Development.
1.8.3
Funding Requirements
1.8.3.1
Respondents shall participate in cost sharing by providing an in-kind
match equal to twenty percent (20%) of the total submitted proposal cost
for both the MEP and MD proposed.
1.8.3.2
In-kind match contributions must comply with all Federal requirements
applicable to the Accelerating V2X Deployment Grant, including 2 CFR
§200.306 (Cost Sharing or Matching). In-kind contributions must be
allowable,
necessary,
reasonable,
properly
valued,
and
fully
documented for Federal audit purposes.
1.9
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.
1.10
ACCEPTANCE
For the County’s initial purchase of each equipment and software product, the contractor
shall provide an acceptance test period (Test Period) that commences upon installation.
Installation shall be defined as a) the equipment, if any, is mounted; b) the software is
installed on the database server(s) and/or personal computer(s); and c) implementation
team training, if any, is complete. During the Test Period, County shall determine whether
the equipment and software meet the contractor published electronic documentation
(“Specifications”). The Test Period shall be for 90 calendar days. If County has not given
the contractor a written deficiency statement specifying how the equipment or software fails
to meet the Specifications (“Deficiency Statement’) within the Test Period, the equipment
and software shall be deemed accepted. If County provides a Deficiency Statement within
the Test Period, the contractor shall have 30 calendar days to correct the deficiency, and
the customer shall have an additional 60 calendar days to evaluate the equipment and
software.
1.10.1 Termination
1.10.1.1 If the equipment or software does not meet the Specifications at the end
of the additional 60 calendar day period, the County may terminate this
contract without further notice and receive a full refund of monies paid
to the contractor. If the contract is terminated after acceptance and prior
to the full term the county will receive a refund of all future year’s
software subscription fees outside of the current year’s software
subscription.
1.10.1.2 Upon any such termination, contractor shall, at contractor’s cost, remove
all equipment and software from County premises and equipment.
County shall return all equipment and software to the contractor, and the
contractor shall refund any monies paid by County to the contractor.
1.10.2 Upon completion of these terms, neither party shall then have any further liability
to the other for the products that were the subject of the acceptance test.
SERIAL# 260052-RFP
Exhibit C – Minimum System Requirements for MEP and MED
MESSAGE EXCHANGE PLATFORM (MEP) SYSTEM REQUIREMENTS
Requirement
ID
Description
Meets
Requirement?
Y or N
Notes
MEP Functional Requirements
MEP-FR-
002-v1.1
The MEP shall determine which mobile devices
J2735 SPaT should be distributed to.
Yes
Confirmed, the
NMI (ISS
production version
of the MEP)
delivers SPaT data
to all systems that
subscribe to a
regionally defined
MQTT topic name.
MEP-FR-
003-v1.1
The MEP shall determine which mobile devices
J2735 MAP should be distributed to.
Yes
Confirmed, the
NMI (ISS
production version
of the MEP)
delivers MAP data
to all systems that
subscribe to a
regionally defined
MQTT topic name.
MEP-FR-
004-v1.1
The MEP shall determine which mobile devices
J3224 SDSM should be distributed to.
Yes
Confirmed, the
NMI (ISS
production version
of the MEP)
delivers SDSM
data to all systems
that subscribe to a
regionally defined
MQTT topic name.
MEP-FR-
005-v1.1
The MEP shall determine which RSP to forward
a J2735 SRM.
Yes
Confirmed, the
NMI (ISS
production version
of the MEP)
delivers SRM
messages to all
systems that
subscribe to a
regionally defined
MQTT topic name.
The body of the
standard J2735
SRM message
contains an
intersection ID that
clearly defines
which intersection
is the subject of the
SRM request.
SERIAL# 260052-RFP
MEP-FR-
006-v1.1
The MEP shall determine which mobile devices
J2735 SSM should be distributed to.
Yes
Confirmed, the
NMI (ISS
production version
of the MEP)
delivers SSM
messages to all
systems that
subscribe to a
regionally defined
MQTT topic name.
The body of the
standard J2735
SSM message
contains a
reference to the
corresponding
request ID from the
SRM that initiated
the request. The
MD system that
produced that
request will
recognize the
relevant SSM and
process the
message content.
MEP Interface Requirements
MEP-IR-
003-v1.1
The MEP shall receive J2735 SPaT messages
from the RSP.
Yes
Confirmed, see
note in response to
MEP-IR-001-v1.1
MEP-IR-
004-v1.1
The MEP shall send J2735 SPaT to (applicable)
mobile devices.
Yes
Confirmed, see
note in response to
MEP-IR-002-v1.1
MEP-IR-
005-v1.1
The MEP shall receive J2735 MAP messages
from the RSP.
Yes
Confirmed, see
note in response to
MEP-IR-001-v1.1
MEP-IR-
006-v1.1
The MEP shall send J2735 MAP to (applicable)
mobile devices.
Yes
Confirmed, see
note in response to
MEP-IR-002-v1.1
MEP-IR-
007-v1.1
The MEP shall receive J3224 SDSM from the
RSP.
Yes
Confirmed, see
note in response to
MEP-IR-001-v1.1
MEP-IR-
008-v1.1
The MEP shall send J3224 SDSM to (applicable)
mobile devices.
Yes
Confirmed, see
note in response to
MEP-IR-002-v1.1
MEP-IR-
009-v1.1
The MEP shall receive J2735 SRM.
Yes
Confirmed, see
note in response to
MEP-IR-001-v1.1
MEP-IR-
010-v1.1
The MEP shall send J2735 SRM to the RSP.
Yes
Confirmed, see
note in response to
MEP-IR-001-v1.1
MEP-IR-
011-v1.1
The MEP shall receive J2735 SSM from the
RSP.
Yes
Confirmed, see
note in response to
MEP-IR-001-v1.1
MEP-IR-
012-v1.1
The MEP shall send J2735 SSM to (applicable)
mobile devices.
Yes
Confirmed, see
note in response to
MEP-IR-002-v1.1
SERIAL# 260052-RFP
MEP-IR-
015-v1.1
The MEP shall utilize GPS for time
synchronization.
Yes
Confirmed, the
TrafficAuth-Mobile
application is
synchronized with
the Android or iOS
app which is
updated using
carrier-supplied
timing information
that is derived from
GPS time.
MEP Performance Requirements
MEP-PR-
001-v1.1
The MEP shall have an overall uptime greater
than 99 percent.
Yes
Confirmned, ISS
wil ensure >>99%
uptime for the NMI.
This goal is
currently achieved
by the existing NMI
instance.
MEP-PR-
002-v1.1
The MEP shall implement a geohashing process
to deliver messages based on the relative spatial
context of the recipient device, ensuring efficient
and accurate location-based message routing.
Yes
Confirmed,
Geohash-based
topic names is a
standard feature of
the NMI
architecture.
MEP Security Requirements
MEP-SR-
001-v1.1
The MEP should comply with IEEE 1609.2.
Yes
Confirmed, the
NMI monitors
MQTT traffic and
takes action to
block any sender
that delivers
content that does
not include a valid
IEEE 1609.2
signature.
MEP-SR-
003-v1.1
The MEP shall be capable of performing digital
signature validation and certificate verification
according to IEEE 1609.2.
Yes
Confirmed,
validation of IEEE
1609.2 messages
is a core capability
of the NMI
architecture.
MEP-SR-
006-v1.1
The MEP shall reject V2X messages that fail
signature validation or are signed with expired or
revoked certificates.
Yes
Confirmed, the
NMI includes both
signature validation
and certificate
validity checks
when monitoring
MQTT traffic for
valid messages.
MOBILE DEVICE (MD) SYSTEM REQUIREMENTS
Requirement
ID
Description
Meets
Requirement?
Y or N
Notes
MD Functional Requirements
SERIAL# 260052-RFP
MD-FR-002-
v1.1
A freight vehicle MD shall use J2735 MAP
along with its position information to
determine the intersection identifier, road
authority identifier, and if it is located within a
lane geometry.
Yes
Confirmed, the
TrafficAuth-Mobile
application, when
Freight Priority mode
is enabled for use by
an authorized user,
will use J2735 MAP
data and it's position
to identify the current
lane.
MD-FR-003-
v1.1
A freight vehicle MD, within a lane geometry,
shall determine identifiers for the approach
and lane it is in.
Yes
Confirmed, the
TrafficAuth-Mobile
application, when
Freight Priority mode
is enabled for use by
an authorized user,
will use J2735 MAP
data and it's position
to identify the land ID
of the approach lane.
MD-FR-004-
v1.1
A freight vehicle MD shall form the SRM
using its position, vehicle identifier,
intersection ID, road authority ID, and
identifiers for the lane and approach it is in,
along with any other user-configured
parameters for SSM generation (for
authorized requests).
Yes
Confirmed, the
TrafficAuth-Mobile
application, when
Freight Priority mode
is enabled for use by
an authorized user,
will produce a valid
(and signed) J2735
SSM.
MD-FR-006-
v1.1
A transit vehicle MD shall use J2735 MAP
along with its position information to
determine the intersection identifier, road
authority identifier, and if it is located within a
lane geometry.
Yes
Confirmed, the
TrafficAuth-Mobile
application, when
Transit Priority mode
is enabled for use by
an authorized user,
will use J2735 MAP
data and it's position
to identify the current
lane.
MD-FR-007-
v1.1
A transit vehicle MD, within a lane geometry,
shall determine identifiers for the approach
and lane it is in.
Yes
Confirmed, the
TrafficAuth-Mobile
application, when
Transit Priority mode
is enabled for use by
an authorized user,
will use J2735 MAP
data and it's position
to identify the land ID
of the approach lane.
MD-FR-008-
v1.1
A transit vehicle MD shall form the SRM
using its position, vehicle identifier,
intersection ID, road authority ID, and
identifiers for the lane and approach it is in,
along with any other user-configured
parameters for SSM generation (for
authorized requests).
Yes
Confirmed, the
TrafficAuth-Mobile
application, when
Transit Priority mode
is enabled for use by
an authorized user,
will produce a valid
(and signed) J2735
SSM.
SERIAL# 260052-RFP
MD-FR-009-
v1.1
A VRU Safety MD shall use J3224 SDSM
along with its position and motion information
to determine whether the vehicle is on a
potential collision course with a pedestrian.
Yes
Confirmed, the
TrafficAuth-Mobile
application can
receive and process
J3224 compliant,
digitially signed
SDSM messages
and warn about
potential collissions
with a pedestrian
represented in the
SDSM data.
MD-FR-010-
v1.1
An MD shall generate the J2735 BSM using
its position, speed, heading, etc. using data
from GNSS, onboard sensors, along with any
other user-configured parameters for BSM
generation.
Yes
Confirmed, the
TrafficAuth-Mobile
application will
generate J2735
compliant, digitally
signed BSM data
using internally
observed speed and
heading data.
MD-FR-012-
v1.0
An MD shall run Android.
Yes
Confirmed, the
TrafficAuth-Mobile
application is
currently available
for download for
Android mobile
devices.
MD-FR-013-
v1.0
An MD shall run iOS.
Yes
Confirmed, the
TrafficAuth-Mobile
application is
currently available
for download for iOS
(Apple) mobile
devices.
MD Interface Requirements
MD-IR-002-
v1.1
A freight vehicle MD shall allow the user to
input whether they want to receive priority
(on/off switch).
Yes
Confirmed, the
TrafficAuth-Mobile
application, when
Freight Priority mode
is enabled for use by
an authorized user,
will include an option
to enable or disable
the freight priority
request feature.
MD-IR-003-
v1.1
A freight vehicle MD shall send an SRM to
the MEP (if the intersection can provide
priority or preemption, switch is on and
located within lane geometry).
Yes
Confirmed, the
TrafficAuth-Mobile
application, when
Freight Priority mode
is enabled for use by
an authorized user,
will send a valid and
signed SRM when
the Freight Priority
function is enabled.
MD-IR-005-
v1.1
A freight vehicle MD shall not send an SRM
to the MEP if the switch is off.
Yes
Confirmed, the
TrafficAuth-Mobile
application, when
SERIAL# 260052-RFP
Freight Priority mode
is enabled for use by
an authorized user,
will not send an SRM
message when the
freight priority feature
is switched off.
MD-IR-006-
v1.1
A freight vehicle MD shall not send an SRM
to the MEP (if not located within a lane
geometry).
Yes
Confirmed, the
TrafficAuth-Mobile
application, when
Freight Priority mode
is enabled for use by
an authorized user,
will not send an SRM
message if the
application
determines that the
vehicle is not in a
supported lane.
MD-IR-009-
v1.1
A transit vehicle MD shall send an SRM to
the MEP (if the intersection can provide
priority or preemption and located within lane
geometry. If data is available, a
determination if the vehicle is behind
schedule more than a user-configurable
amount of time should also be used).
Yes
Confirmed, the
TrafficAuth-Mobile
application, when
Transit Priority mode
is enabled for use by
an authorized user,
will be able to access
schedule data to
determine if transit
priority is required.
MD-IR-010-
v1.1
A transit vehicle MD shall not send an SRM
to the MEP (if the intersection cannot provide
priority or preemption).
Yes
Confirmed, the
TrafficAuth-Mobile
application, when
Transit Priority mode
is enabled for use by
an authorized user,
will not send an SRM
if the conditions are
not met.
MD-IR-012-
v1.1
A transit vehicle MD shall not send an SRM
to the MEP (if not located within a lane
geometry).
Yes
Confirmed, the
TrafficAuth-Mobile
application, when
Transit Priority mode
is enabled for use by
an authorized user,
will not send an SRM
if the vehicle is not
located in an
appropriate lane.
MD-IR-014-
v1.1
A VRU Safety MD shall deliver a visual
and/or audible warning to the vehicle
operator via the MD HMI (if on a potential
collision course).
Yes
Confirmed, the
TrafficAuth-Mobile
application will not
produce a warning
when not on a
collission course
MD-IR-015-
v1.1
A VRU Safety MD shall not deliver a visual
and/or audible warning to the vehicle
operator via the MD HMI (if not on a potential
collision course).
Yes
Confirmed, the
TrafficAuth-Mobile
application will not
produce a warning
SERIAL# 260052-RFP
when not on a
collission course
MD-IR-016-
v1.1
An MD shall send BSMs to the MEP.
Yes
Confirmed, the
TrafficAuth-Mobile
application will send
valid and signed
BSM data to the
MEP
MD-IR-017-
v1.1
An MD shall receive location and time data
from GNSS.
Yes
Confirmed, the
TrafficAuth-Mobile
application will use
GNSS for location
and time data
MD Performance Requirements
MD-PR-001-
v1.1
An MD shall broadcast between 9-11 J2735
SRM messages in a 10-second interval when
conditions to broadcast SRM have been met.
Yes
Confirmed, the
TrafficAuth-Mobile
app can be
configured to
produce 10 SRM
messags per-second
MD-PR-002-
v1.1
All required SRM data elements shall be
accurately populated.
Yes
Confirmed, the
TrafficAuth-Mobile
app can be
configured to
produce messages
with all required
elements
MD-PR-003-
v1.1
An MD shall broadcast 90-110 J2735 BSM
messages in a 10-second interval.
Yes
Confirmed, the
TrafficAuth-Mobile
app can be
configured to
produce 10 SRM
messags per-second
MD-PR-004-
v1.1
All required BSM data elements shall be
accurately populated.
Yes
Confirmed, the
TrafficAuth-Mobile
app accurately
populates J2735
style BSM messages
MD-PR-005-
v1.1
All MDs shall be time synchronized with
other system devices.
Yes
Confirmed, the
TrafficAuth-Mobile
app uses GPS data
to synchronize time
with other devices
MD Data Requirements
MD-DR-001-
v1.1
The J2735 SRM shall contain the MsgCount
data element (J2735 Section 7.113).
Yes
Confirmed, The
TrafficAuth-Mobile
app populates the
MsgCount data
elment in the SRM
MD-DR-002-
v1.1
The J2735 SRM shall contain the time stamp
data element (J2735 Section 7.192).
Yes
Confirmed, The
TrafficAuth-Mobile
app populates the
time stamp data
elment in the SRM
MD-DR-003-
v1.1
The J2735 SRM shall contain the requestor
data frame (Requestor Description) (J2735
Section 6.98).
Yes
Confirmed, The
TrafficAuth-Mobile
app populates the
SERIAL# 260052-RFP
data frame data
elment in the SRM
MD-DR-004-
v1.1
The J2735 SRM shall contain the VehicleID
field within requestor (J2735 Section 6.147).
Yes
Confirmed, The
TrafficAuth-Mobile
app populates the
Vehicle ID data
elment in the SRM
MD-DR-005-
v1.1
The J2735 SRM shall contain the
TemporaryID field under VehicleID (J2735
Section 7.187).
Yes
Confirmed, The
TrafficAuth-Mobile
app populates the
Temporary ID data
elment in the SRM
MD-DR-006-
v1.1
The J2735 SRM shall contain the RequestID
data element (J2735 Section 7.153).
Yes
Confirmed, The
TrafficAuth-Mobile
app populates the
Request ID data
elment in the SRM
MD-DR-007-
v1.1
The J2735 SRM shall contain the
SignalRequestList data frame (J2735 Section
6.118).
Yes
Confirmed, The
TrafficAuth-Mobile
app populates the
SignalRequestList
data frame elment in
the SRM
MD-DR-008-
v1.1
The J2735 SRM shall contain the
SignalRequest data frame within the list
(J2735 Section 6.120).
Yes
Confirmed, The
TrafficAuth-Mobile
app populates the
SignalRequest
elment in the SRM
MD-DR-009-
v1.1
The J2735 SRM shall contain the
IntersectionReferenceID data frame (J2735
Section 6.36).
Yes
Confirmed, The
TrafficAuth-Mobile
app populates the
ReferenceID data
elment in the SRM
MD-DR-010-
v1.1
The J2735 SRM shall contain the
inBoundLane data frame
(IntersectionAccessPoint) (J2735 Section
6.33).
Yes
Confirmed, The
TrafficAuth-Mobile
app populates the
BoundLane data
frame in the SRM
MD-DR-011-
v1.1
The J2735 SRM shall contain the
PriorityRequestType field to distinguish
request intent (J2735 Section 7.142).
Yes
Confirmed, The
TrafficAuth-Mobile
app populates the
PriorityRequestType
field n the SRM
MD-DR-012-
v1.1
The J2735 SRM shall contain expected
arrival time and duration if used (J2735
Section 6.120).
Yes
Confirmed, The
TrafficAuth-Mobile
app is able to
populate the arrival
time and duration in
the SRM
MD-DR-013-
v1.1
The J2735 SRM shall contain current speed,
heading, and position of the vehicle (J2735
Section 6.98).
Yes
Confirmed, The
TrafficAuth-Mobile
app can include the
current speed,
heading, and
position in the SRM
MD-DR-014-
v1.1
The J2735 BSM shall include all data
elements contained in the BSMcoreData
data frame (J2735 Section 6.10).
Yes
Confirmed, The
TrafficAuth-Mobile
app populates the
SERIAL# 260052-RFP
BSMcoreData in the
BSM message
MD-DR-015-
v1.1
The J2735 BSM message 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.
Yes
Confirmed, The
TrafficAuth-Mobile
app can populate the
BSM part II
extension when
enabled by an
authorized user and
provided with an
appropriate security
certificate
MD Security Requirements
MD-SR-001-
v1.1
All MDs should comply with IEEE 1609.2.
Yes
Confirmed, the
TrafficAuth-Mobile
app compies with
IEEE 1609.2
MD-SR-002-
v1.1
All MDs should be provisioned with valid
IEEE 1609.2 enrollment certificates (by the
supplier) prior to deployment.
Yes
Confirmed, the
TrafficAuth-Mobile
app can enroll with
an SCMS service,
using permission
information obtained
about the registered
user. This
information is used
to limit permissions
on the certificates
issued.
MD-SR-003-
v1.1
An MD should sign all outgoing messages for
broadcast with a valid IEEE 1609.2
pseudonym or IEEE 1609.2 identity
certificate.
Yes
Confirmed, the
TrafficAuth-Mobile
app is able to access
an SCMS service to
download
certificates.
MD-SR-004-
v1.1
An MD that supports FSP or TSP should use
identity certificates to sign all V2X messages.
Yes
Confirmed, the
TrafficAuth-Mobile
app can be
configured to use
identity certificates
where required.
MD-SR-005-
v1.1
An MD that does not support FSP or TSP
(only supports VRU Safety) should use
pseudonym certificates to sign all V2X
messages.
Yes
Confirmed, the
TrafficAuth-Mobile
app uses
pseudonym
certificates by
default.
MD-SR-007-
v1.1
All MDs should cease transmission of
messages if no valid IEEE 1609.2
pseudonym or IEEE 1609.2 identity
certificates are available.
Yes
Confirmed, the
TrafficAuth-Mobile
app will not deliver
any V2X messages if
no certificates are
available.
MD-SR-007-
v1.1
All MDs should be capable of performing
digital signature validation and certificate
verification according to IEEE 1609.2.
Yes
Confirmed, the
TrafficAuth-Mobile
app validates
signatures on all
SERIAL# 260052-RFP
incomming
messages.
MD-SR-008-
v1.1
All MDs should reject V2X messages that fail
signature validation or are signed with
expired or revoked certificates.
Yes
Confirmed, the
TraffficAuth-Mobile
app rejects all invalid
messages.
MD-SR-009-
v1.1
All MDs should download and utilize the
latest Certificate Revocation List (CRL) from
the SCMS.
Yes
Confirmed, the
TrafficAuth-Mobile
app applies the latest
CRL when
validationg
messages.
MD-SR-010-
v1.1
All MDs should reject all messages received
from any source listed on the current CRL.
Yes
Confirmed, the
TrafficAuth-Mobile
app applies the latest
CRL when
validationg
messages.
MD-SR-011-
v1.1
An MD using IEEE 1609.2 pseudonym
certificates should have no more than two
weeks’ worth of pseudonym certificates
loaded at a time.
Yes
Confirmed, the
TrafficAuth-Mobile
app does not store
more than 2 weeks
of certificates.
MD-SR-012-
v1.1
An MD using IEEE 1609.2 pseudonym
certificates should request to receive
additional pseudonym certificates at least
once per week from the SCMS.
Yes
Confirmed, the
TrafficAuth-Mobile
app automatically
downloads
certificates as
needed
MD-SR-013-
v1.1
An MD using IEEE 1609.2 identity
certificates should have no more than two
weeks’ worth of identity certificates loaded at
a time.
Yes
Confirmed, the
TrafficAuth-Mobile
app does not store
more than 2 weeks
of certificates.
MD-SR-014-
v1.1
An MD using IEEE 1609.2 identity
certificates should request additional identity
certificates at least once per week from the
SCMS.
Yes
Confirmed, the
TrafficAuth-Mobile
app automatically
downloads
certificates as
needed
MD-SR-015-
v1.1
An MD should implement IEEE 1609.2
certificate download and renewal processes
over secure, encrypted, end-to-end
connections.
Yes
Confirmed, the
TrafficAuth-Mobile
application uses TLS
to ensure a secure
connection to the
SCMS infrastructure.
SERIAL# 260052-RFP
Exhibit D – MCDOT SUPPLEMENTAL TERMS AND CONDITIONS
1.0
TITLE VI
The Maricopa County Department of Transportation (MCDOT), in accordance with the provisions
of Title VI of the Civil Rights Act of 1964 (78 Stat. 252.42 U.S.C. § 2000d to 2000d-4) and the
Regulations, hereby notifies all bidders that it will affirmatively ensure that any contract entered into
pursuant to this advertisement, Disadvantaged Business Enterprises will be afforded full and fair
opportunity to submit bids in response to this invitation and will not be discriminated against on the
grounds of race, color, or national origin in consideration for an award. See Exhibit 6 2025 Title VI
Assurances.
2.0
SMALL BUSINESS ENTERPRISES (SBE REPORTING FORM)
2.1. It is Maricopa County (County) policy to facilitate and encourage participation by Small Business
Enterprise
(SBE)
concerns
in
County
contracts.
The
County
encourages
the
contractor/consultant to take reasonable steps to eliminate obstacles to SBE participation and
to utilize SBEs in performing contracts.
2.2. The contractor/consultant shall comply with 49 Code of Federal Regulations (CFR) 26.7 and
further defined pursuant to Section 3 of the Small Business Act and Small Business
Administration regulations implementing it (13 CFR Part 21) where possible. For more details
on the SBE program and process requirements, reference the Arizona Department of
Transportation (ADOT) Business Engagement and Compliance (BECO) guidelines for SBEs,
which are registered in the Arizona Unified Transportation Registration and Certification System
(AZ UTRACS).
2.3. The contractor/consultant shall complete the SBE Participation Reporting Form included in
Exhibit 7 Small Business Enterprise Program Participation Reporting Form and submit with
each
invoice/payment
request.
3.0
PROMPT PAY LEGISLATION
3.1. In accordance with Arizona Revised Statutes (A.R.S.) § 34-221, the County must issue
payments to prime contractor/consultants within a certain number of calendar days after receipt
of an invoice/payment request. The law also requires the contractors/consultants to pay their
subcontractors/subconsultants within a specific number of calendar days after issuance of
payment
by
the
County,
unless
exceptions
exist
within
the
agreed-upon
contractor/subcontractor or consultant/subconsultant agreement.
3.2. Upon any resolution of unapproved invoices/payment requests, prime contractors/consultants
shall not withhold subtractors’/subconsultants’ payments if the County has paid for the full value
of services rendered. Failure by the prime contractor/consultant to invoice the County in
accordance with the terms of the contract and/or pay subcontractors/subconsultants in
accordance with A.R.S. § 34-221 shall be constituted as a material breach of contract, subjecting
the prime contractor/consultant to disqualification under this contract. The County reserves the
right
to
request
the
prime
contractor/consultant
provide
proof
of
payment
to
subcontractors/subconsultants at any time. See Exhibit 8 Local Public Agency (LPA) Prompt
Pay and Payment Reporting Provisions.
4.0
DISADVANTAGED BUSINESS ENTERPRISE (DBE) PARTICIPATION
The contractor/consultant, subrecipient, or subcontractor/subconsultant shall not discriminate on
the basis of race, color, national origin, or sex in the performance of this contract. The
contractor/consultant shall carry out applicable requirements of 49 CFR part 26 in the award and
administration of Department of Transportation (DOT) assisted contracts. Failure by the
contractor/consultant to carry out these requirements is a material breach of this contract, which
may result in the termination of this contract or such other remedy as the recipient deems
appropriate. The minimum goal for participation of DBE’s on this contract is 0 percent.
SERIAL# 260052-RFP
5.0
BUY
AMERICA
AND
BUILD
AMERICA,
BUY
AMERICA
(BABA)
ACT
5.1. The contractor/consultant shall comply, as applicable, with the current requirements of 23 CFR
635.410 Buy America and the Build America, Buy America Act specified in Title IX, Subtitle A,
Part 1, Sections 70901 and 70911-70918 (Pub. L. No. 117-58 §§ 70901; §§ 70911-70918) of
the Infrastructure Investment and Job Act (IIJA).
5.2. Build America, Buy America Act requirements due to Federal Highway Administration (FHWA)
construction funding United States Department of Transportation (USDOT) is being utilized for
this contract and related project activities and/or procurement. As applicable, all clauses in this
form are to be complied with under this contract, and this form shall be inserted in any
contractor’s/consultant’s subcontracts. See Exhibit 10 Build America, Buy America Stored
Specifications.
6.0
CARGO PREFERENCE ACT
The Cargo Preference regulations in 46 CFR 381 govern the implementation of the Cargo
Preference Act of 1954. The USDOT has ultimate reporting responsibility under this act. Reporting
by the contractor/consultant to the engineer and Maritime Administration is particularly important,
requiring shipping details in the form of a master freighted bill of lading sent to
cargo.marad@dot.gov.