15058-CONTRACT - TRANSCORE.DOCX

SERIAL 15058-RFP BELL RD ADAPTIVE SIGNAL CONTROL TECHNOLOGY (ASCT)
DEPLOYMENT
(Contract – TransCore ITS, LLC)
DATE OF LAST REVISION: September 07, 2016 CONTRACT END DATE: August 31, 2021
CONTRACT PERIOD THROUGH AUGUST 31, 2021
TO: All Departments
FROM: Office of Procurement Services
SUBJECT: Contract for BELL RD ADAPTIVE SIGNAL CONTROL TECHNOLOGY
(ASCT) DEPLOYMENT
Attached to this letter is published an effective purchasing contract for products and/or services to be supplied to
Maricopa County activities as awarded by Maricopa County on September 07, 2016.
All purchases of products and/or services listed on the attached pages of this letter are to be obtained from the
vendor holding the contract. Individuals are responsible to the vendor for purchases made outside of contracts.
The contract period is indicated above.
NP/at
Attach
Copy to: Office of Procurement Services
Sami Birchard, MCDOT
April Wire, MCDOT

CONTRACT PURSUANT TO RFP
SERIAL 15058-RFP
This Contract is entered into this 7th day of September, 2016 by and between Maricopa County (“County”), a
political subdivision of the State of Arizona, and TransCore ITS, LLC (“TransCore”) a limited liability company
organized under the laws of the State of Delaware, with a principal place of business at 150 4th Avenue North, Suite
1200, Nashville, TN 37219 (“Contractor”) for the purchase of adaptive signal control technology services.
1.0 CONTRACT TERM:
1.1 This Contract is for a term of five (5) years, beginning on the 7th day of September, 2016 and
ending the 31st day of August, 2021.
1.2 The County may, at its option and with the agreement of the Contractor, renew the term of this
Contract for additional terms up to a maximum of five (5) years, (or at the County’s sole
discretion, extend the contract on a month-to-month bases for a maximum of six (6) months after
expiration). The County shall notify the Contractor in writing of its intent to extend the Contract
term at least sixty (60) calendar days prior to the expiration of the original contract term, or any
additional term thereafter.
2.0 FEE ADJUSTMENTS:
2.1 Any request for a fee adjustment must be submitted sixty (60) days prior to the current Contract
expiration. Requests for adjustment in cost of labor and/or materials must be supported by
appropriate documentation. If County agrees to the adjusted fee, County shall issue written
approval of the change. The reasonableness of the request shall be determined by comparing the
request with the lesser of 3% or Consumer Price Index – All Urban Consumers, Series ID
CUUR0400AA0, Not Seasonally Adjusted, West Urban Area, All items old base (12/77).
3.0 PAYMENTS:
3.1 As consideration for performance of the duties described herein, County shall pay Contractor the
sum(s) stated in Exhibit “A.”
3.2 Payment shall be made upon the County’s receipt of a properly completed invoice.
3.3 INVOICES:
3.3.1 The Contractor/Consultant shall be paid a fee as awarded by the County for complete and
satisfactory performance of work and/or materials delivered in accordance with the
detailed scope of work and any technical specifications. The County does not guarantee
any minimum or maximum fee during the period of this contract.
3.3.2 The County shall pay the Consultant/Contractor in full for each monthly payment
request, upon approval by the County and subject to the limitations set forth in the Scope
of Work under this contract. A Project Specific Consultant Payment Request form is
enclosed in Exhibit E. and must include back-up documentation with each invoiced
progress payment request. The backup documentation shall clearly indicate the hours

15058-RFP
worked, date and employee’s name, including subconsultants. All backup documentation
shall include copies of any subconsultant or vendor invoices.
The Small Business Enterprise Participation Reporting form, as shown in Exhibit E, is
to be submitted with each invoice/progress payment request. Any payment request
submitted to the County without this form may be rejected as an incomplete payment
request, pursuant to the terms of the contract.
Upon completion of all deliverables under the scope(s) of work and related technical
requirements in this contract, and final acceptance by Maricopa County Department of
Transportation, the Contractor/Consultant shall submit a Certificate of Performance and
Payment of ALL Claims form, as shown in Exhibit E.
3.3.3 Problems regarding billing or invoicing shall be directed to the using agency as listed on
the Purchase Order.
3.3.4 Payment shall 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
(http://www.maricopa.gov/Finance/Vendors.aspx).
3.3.5 Discounts offered in the contract shall be calculated based on the date a properly
completed invoice is received by the County (ROI).
3.3.6 EFT payments to the routing and account numbers designated by the Contractor shall
include the details on the specific invoices that the payment covers. The Contractor is
required to discuss remittance delivery capabilities with their designated financial
institution for access to those details.
3.4 PAYMENT RETENTION:
See Exhibit A System Verification & Acceptance, Milestone Payments
3.5 APPLICABLE TAXES:
3.5.1 Payment of Taxes: The Contractor shall pay all applicable taxes. With respect to any
installation labor on items that are not attached to real property performed by Contractor
under the terms of this Contract, the installation labor cost and the gross receipts for
materials provided shall be listed separately on the Contractor’s invoices.
3.5.2 State and Local Transaction Privilege Taxes: Maricopa County is subject to all
applicable state and local transaction privilege taxes. To the extent any state and local
transaction privilege taxes apply to sales made under the terms of this contract it is the
responsibility of the seller to collect and remit all applicable taxes to the proper taxing
jurisdiction of authority.
3.5.3 Tax Indemnification: Contractor and all subcontractors shall pay all Federal, state, and
local taxes applicable to its 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
Worker’s Compensation.

15058-RFP
3.6 TAX: (SERVICES)
No tax shall be levied against labor. It is the responsibility of the Contractor to determine any and
all taxes and include the same in proposal price.
4.0 AVAILABILITY OF FUNDS:
4.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.
4.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 ten
(10) days in advance.
5.0 DUTIES:
5.1 The Contractor shall perform all duties stated in Exhibit “B”, or as otherwise directed in writing
by the Procurement Officer.
5.2 During the Contract term, County may provide Contractor’s personnel with adequate workspace
for consultants and such other related facilities as may be required by Contractor to carry out its
contractual obligations.
6.0 TERMS and CONDITIONS:
6.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, agents, officers,
directors, officials, and employees from and against all claims, direct damages, losses, and
expenses (including, 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 relating to the performance of this Contract.
Contractor's duty to defend, indemnify, and hold harmless the County, its agents, representatives,
agents, officers, directors, officials, and employees shall arise in connection with any claim, direct
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 there from,
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, any
one 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. For professional liability claims, indemnification responsibility is limited
to the Contractor’s proportionate share of the negligence.
The scope of this indemnification does not extend to the sole negligence of County.

15058-RFP
6.2 INSURANCE.
6.2.1 Contractor, at Contractor’s own expense, shall purchase and maintain the herein
stipulated minimum insurance from a company or companies duly licensed by the State
of Arizona and possessing a current A.M. Best, Inc. 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.
6.2.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.
6.2.3 Contractor’s insurance shall be primary insurance as respects County, and any insurance
or self-insurance maintained by County shall not contribute to it.
6.2.4 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.
6.2.5 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.
6.2.6 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.
6.2.7 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.
6.2.8 Commercial General Liability.
Commercial General Liability insurance and, if necessary, Commercial Umbrella
insurance with a limit of not less than $2,000,000 for each occurrence, $4,000,000
Products/Completed Operations Aggregate, and $4,000,000 General Aggregate Limit.
The policy shall include coverage for premises liability, bodily injury, broad form
property damage, personal injury, products and completed operations and blanket
contractual coverage, and shall not contain any provisions which would serve to limit
third party action over claims. There shall be no endorsement or modifications of the
CGL limiting the scope of coverage for liability arising from explosion, collapse, or
underground property damage.
6.2.9 Automobile Liability.
Commercial/Business Automobile Liability insurance and, if necessary, Commercial
Umbrella 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.

15058-RFP
6.2.10 Workers’ Compensation.
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.
Contractor, its contractors and its subcontractors waive all rights against 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 contractors and its
subcontractors pursuant to this Contract.
6.2.11 Errors and Omissions (Professional Liability) Insurance.
Errors and Omissions (Professional Liability) insurance and, if necessary, Commercial
Umbrella insurance, which shall insure and provide coverage for errors or omissions or
professional liability of the CONTRACTOR, with limits of no less than $2,000,000 for
each claim. Coverage shall include Network and Information Security (cyber liability)
6.2.12 Professional Liability.
Contractor shall maintain Professional Liability insurance which shall 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 of not less than $1,000,000 for each claim, and
$3,000,000 aggregate claims.
6.2.13 Certificates of Insurance.
6.2.13.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.
6.2.13.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.
6.2.13.3 If a policy does expire during the life of the Contract, a renewal certificate must
be sent to County prior to the expiration date.
6.2.14 Cancellation and Expiration Notice.
Insurance required herein shall not be permitted to expire, be canceled, or materially
changed without thirty (30) days prior written notice to the County.
6.3 WARRANTY
6.3.1 All items furnished under this Contract shall conform to the requirements of this Contract
and shall be free from defects in design, materials and workmanship.
6.3.2 The warranty period for workmanship and materials shall be for an initial period of
twelve (12) months and commence upon acceptance by County.
6.3.3 The Contractor agrees that he will, at his own expense, provide all labor and parts
required to remove, repair or replace, and reinstall any such defective workmanship
and/or materials which becomes or is found to be defective during the term of this

15058-RFP
warranty. The Contractor shall guarantee the equipment to be supplied complies with all
applicable regulations.
6.4 WARRANTY OF SERVICES:
6.4.1 The Contractor warrants that all services provided hereunder shall 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.
6.4.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.
6.5 INSPECTION OF SERVICES:
6.5.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.
6.5.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 shall not unduly delay the work.
6.5.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:
6.5.3.1 Require the Contractor to take necessary action to ensure that future
performance conforms to Contract requirements; and
6.5.3.2 Reduce the Contract price to reflect the reduced value of the services performed.
6.5.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:
6.5.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
6.5.4.2 Terminate the Contract for default.
6.6 REQUIREMENTS CONTRACT:
6.6.1 Contractors signify their understanding and agreement by signing a bid submittal, that the
Contract resulting from the bid is a requirements contract. However, the Contract does
not guarantee any minimum or maximum number of purchases shall be made. It only
indicates that if purchases are made for the materials or services contained in the
Contract, they shall be purchased from the Contractor awarded that item if the Contractor
can meet all the delivery requirements of the County. Orders shall only be placed when
the County identifies a need and proper authorization and documentation have been
approved.
6.6.2 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

15058-RFP
the Purchase Order. The County shall not reimburse the Contractor for any costs incurred
after receipt of County notice of cancellation, or for lost profits, shipment of product prior
to issuance of Purchase Order, etc.
6.6.3 Contractors agree to accept verbal notification of cancellation of Purchase Orders from
the County Procurement Officer with written notification to follow. By submitting a bid
in response to this Invitation for Bids, the Contractor specifically acknowledges to be
bound by this cancellation policy.
6.7 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.
6.8 Stop Work Order
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 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 days after a stop-work is delivered to
the Contractor, or within any extension of that period to which the parties shall have agreed, the
Procurement Officer shall either—
6.8.1 Cancel the stop-work order; or
6.8.2 Terminate the work covered by the order as provided in the Default, or the Termination
for Convenience of the County, clause of this contract.
6.8.3 The Procurement Officer may make an equitable adjustment in the delivery schedule
and/or contract price, or otherwise, 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.
6.9 UNCONDITIONAL TERMINATION FOR CONVENIENCE:
Maricopa County may terminate the resultant Contract for convenience by providing sixty (60)
calendar days advance notice to the Contractor. In the event of a termination for convenience or a
termination for default, as provided in Section 6.10 below, Maricopa County will only be entitled
to a refund of unused license and maintenance fees if the ACDSS, as defined on Section 1 of
Exhibit C.1 (ACDSS License Agreement), is fully decommissioned. Moreover, refunds of unused
license and maintenance fees shall not be prorated for partial years of services not used. The
refunds will only be assessed for complete years of service not used at $19,611.83 per service
year.
6.10 TERMINATION FOR DEFAULT:
The County may, by written notice of default to the Contractor, terminate this contract in whole or
in part if the Contractor fails to:

15058-RFP
6.10.1 Deliver the supplies or to perform the services within the time specified in this contract or
any extension;
6.10.2 Make progress, so as to endanger performance of this contract; or
6.10.3 Perform any of the other provisions of this contract.
6.10.4 The County’s right to terminate this contract under these subparagraph may be exercised
if the Contractor does not cure such failure within 10 days (or more if authorized in
writing by the County) after receipt of the notice from the Procurement Officer
specifying the failure.
6.11 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.
6.12 CONTRACTOR LICENSE REQUIREMENT:
6.12.1 The Respondent shall procure all permits, insurance, licenses and pay the charges and
fees necessary and incidental to the lawful conduct of his/her business, and as necessary
complete any required certification requirements, required by any and all governmental or
non-governmental entities as mandated to maintain compliance with and in good standing
for all permits and/or licenses. The Respondent shall keep fully informed of existing and
future trade or industry requirements, Federal, State and Local laws, ordinances, and
regulations which in any manner affect the fulfillment of a Contract and shall comply
with the same. Contractor shall immediately notify both Office of Procurement Services
and the using agency of any and all changes concerning permits, insurance or licenses.
6.12.2 Respondents furnishing finished products, materials or articles of merchandise that shall
require installation or attachment as part of the Contract, shall possess any licenses
required. A Respondent is not relieved of its obligation to posses the required licenses by
subcontracting of the labor portion of the Contract. Respondents are advised to contact
the Arizona Registrar of Contractors, Chief of Licensing, at (602) 542-1525 to ascertain
licensing requirements for a particular contract. Respondents shall identify which
license(s), if any, the Registrar of Contractors requires for performance of the Contract.
6.13 SUBCONTRACTING:
6.13.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 project.
6.13.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 or the County has approved the increase. 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.

15058-RFP
6.14 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.
6.15 ADDITIONS/DELETIONS OF SERVICE:
6.15.1 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 shall 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
shall be negotiated between the Contractor and the County.
6.15.2 The County reserves the right of final approval on proposed staff for all Task Orders.
Also, upon request by the County, the Contractor shall 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 previously approved by the County.
6.16 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.
6.17 SEVERABILITY:
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 this Contract.
6.18 RIGHTS IN DATA:
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.
6.19 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
may be viewed and downloaded at the Governor of the State of Arizona’s website
http://azmemory.azlibrary.gov/cdm/singleitem/collection/execorders/id/680/rec/1 which 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.
6.20 CERTIFICATION REGARDING DEBARMENT AND SUSPENSION
6.20.1 The undersigned (authorized official signing for the Contractor) certifies to the best of his
or her knowledge and belief, that the Contractor
6.20.1.1 is not presently debarred, suspended, proposed for debarment, declared
ineligible, or voluntarily excluded from covered transactions by any Federal
Department or agency;
6.20.1.2 have not within 3-year period preceding this Contract been convicted of or had a
civil judgment rendered against them for commission of fraud or a criminal
offense in connection with obtaining, attempting to obtain, or performing a

15058-RFP
public (Federal, State or local) transaction or contract under a public transaction;
violation of Federal or State antitrust statues or commission of embezzlement,
theft, forgery, bribery, falsification or destruction of records, making false
statements, or receiving stolen property;
6.20.1.3 are not presently indicted or otherwise criminally or civilly charged by a
government entity (Federal, State or local) with commission of any of the
offenses enumerated in paragraph (2) of this certification; and
6.20.1.4 have not within a 3-year period preceding this Contract had one or more public
transaction (Federal, State or local) terminated for cause of default.
6.20.2 The Contractor agrees to include, without modification, this clause in all lower tier
covered transactions (i.e. transactions with subcontractors) and in all solicitations for
lower tier covered transactions related to this Contract.
6.21 VERIFICATION REGARDING COMPLIANCE WITH ARIZONA REVISED STATUTES §41-
4401 AND FEDERAL IMMIGRATION LAWS AND REGULATIONS:
6.21.1 By entering into the Contract, the Contractor warrants compliance with the Immigration
and Nationality Act (INA using e-verify) and all other federal immigration laws and
regulations related to the immigration status of its employees and A.R.S. §23-214(A). The
contractor shall obtain statements from its subcontractors certifying compliance and shall
furnish the statements to the Procurement Officer upon request. These warranties shall
remain in effect through the term of the Contract. The Contractor and its subcontractors
shall also maintain Employment Eligibility Verification forms (I-9) as required by the
Immigration Reform 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 USCIS.GOV.
6.21.2 The County retains the legal right to inspect contractor and subcontractor employee
documents performing work under this Contract to verify compliance with paragraph 6.20
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 shall 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.
6.22 INFLUENCE
As prescribed in MC1-1202 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.
An attempt to influence includes, but is not limited to:
6.22.1 A Person offering or providing a gratuity, gift, tip, present, donation, money,
entertainment or educational passes or tickets, or any type valuable contribution or
subsidy,
6.22.2 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.
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

15058-RFP
Maricopa County Procurement Code, any remedy in equity or in the law, or any remedy provided
by this contract.
6.23 CONTRACTOR EMPLOYEE WHISTLEBLOWER RIGHTS AND REQUIREMENT TO
INFORM EMPLOYEES OF WHISTLERBLOWER RIGHTS.
6.23.1 The Parties agree that this Contract and employees working on this Contract shall be
subject to the whistleblower rights and remedies in the pilot program on contractor
employee whistleblower protections established at 41 U.S.C. § 4712 by section 828 of the
National Defense Authorization Act for Fiscal Year 2013 (Pub. L. 112–239) and section
3.908 of the Federal Acquisition Regulation;
6.23.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.
6.23.3 Contractor shall insert the substance of this clause, including this paragraph (c), in all
subcontracts over the simplified acquisition threshold ($150,000 as of September 2013).
6.24 FEDERAL CLAUSES
6.24.1 Title VI
The Maricopa County Department of Transportation, in accordance with the provisions
of Title VI of the Civil Rights Act of 1964 (78 Stat. 252.42 U.S.C. §§ 2000d-4) and the
Regulations, hereby notifies all bidders that it shall affirmatively ensure that any contract
entered into pursuant to this advertisement, disadvantaged business enterprises shall be
afforded full and fair opportunity to submit bids in response to this invitation and shall
not be discriminated against on the grounds of race, color, or national origin in
consideration for an award.
Additional Title VI Assurance language can be found in Exhibit E, Special Federal
Terms, Conditions and Documents. This Exhibit contains a commitment by the Maricopa
County Department of Transportation, as the recipient of the federal funding associated
with this Contract and related project. This commitment pertains to complying with all
referenced Acts and Regulations. Similar assurances are required of contractors and
consultants and must also be included in any subcontracts. Maricopa County Department
of Transportation’s Title VI Plan details can be found at:
http://www.mcdot.maricopa.gov/technical/TitleVI/home.htm.
6.24.2 Buy America
As applicable, the Contractor shall comply with CFR 23, § 635.410 Buy America
requirements and provide proof of compliance with delivery of the pertinent materials.
6.24.3 Small Business Enterprises
It is the County’s policy to facilitate and encourage participation by Small Business
Enterprise concerns (SBE) 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.
The Contractor/Consultant shall comply with 49 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 ADOT Business Engagement and Compliance
(BECO) guidelines for SBEs, which are registered in the Arizona Unified Transportation
Registration and Certification System (AZ UTRACS).

15058-RFP
The Contractor/Consultant shall complete the SBE Participation Reporting Form
included in Exhibit E and submit with each invoice/payment request.
6.24.4 Prompt Pay Legislation
In accordance with A.R.S. § 28-411 (Prompt Payment to Consultants and
Subconsultants), the County must issue payments to Prime Consultants within a certain
number of calendar days after receipt of an Payment Request/Invoice. The law also
requires the Consultants to pay their Subconsultants within a specific number of calendar
days after issuance of payment by the County, unless exceptions exist within the agreed-
upon Consultant/Subconsultant agreement.
Upon any resolution of unapproved invoices/Payment Requests, Prime Consultants shall
not withhold Subconsultants’ payments if the County has paid for the full value of
services rendered. Failure by the Prime Consultant to invoice the County in accordance
with the terms of the contract and/or pay Subconsultants in accordance with A.R.S. § 28-
411 shall be constituted as a material breach of contract, subjecting the Prime Consultant
to disqualification under this contract. The County reserves the right to request the Prime
Consultant provide proof of payment to Subconsultants at any time.
6.24.5 Disadvantaged Business Enterprises (DBE)
The Arizona Department of Transportation (hereinafter the Department or ADOT) has
established a DBE program in accordance with the regulations of the U.S. Department of
Transportation (USDOT), 49 CFR Part 26. This contract has no established contract goals
for DBE participation. Consultants/Contractors are still encouraged to employ reasonable
means to obtain DBE participation. Consultants/Contractors must retain records in
accordance with the DBE specifications included in Exhibit E.
Consultants/Contractors are hereby notified that this recordkeeping is important to the
ADOT, so that it can track DBE participation where only race neutral efforts are
employed.
6.24.6 Aid Contracts
FHWA-1273 form is included in Exhibit E due to FHWA construction funding
(USDOT) 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/Consultant’s
subcontracts.
6.25 ACCESS TO AND RETENTION OF RECORDS FOR THE PURPOSE OF AUDIT AND/OR
OTHER REVIEW:
6.25.1 In accordance with section MCI 371 of the Maricopa County Procurement Code the
Contractor agrees to retain all books, records, accounts, statements, reports, files, and
other records and back-up documentation relevant to this Contract for six (6) years after
final payment or until after the resolution of any audit questions which could be more
than six (6) years, whichever is latest. 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.
6.25.2 If the Contractor’s books, records , accounts, statements, reports, files, and other records
and back-up documentation relevant to this Contract are not sufficient to support and
document that requested services were provided, the Contractor shall reimburse Maricopa
County for the services not so adequately supported and documented.
6.25.3 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 deduction from current billings Submitted by the Contractor by the amount of

15058-RFP
the disallowance, or to require reimbursement forthwith of the disallowed amount by the
Contractor by issuing a check payable to Maricopa County.
6.26 AUDIT DISALLOWANCES:
If at any time, County determines that a cost for which payment has been made is a disallowed
cost, such as overpayment, County shall notify the Contractor in writing of the disallowance.
County shall also state the means of correction, which may be but shall not be limited to
adjustment of any future claim submitted by the Contractor by the amount of the disallowance, or
to require repayment of the disallowed amount by the Contractor.
6.27 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.
6.28 PUBLIC RECORDS:
Under Arizona law, all Offers submitted and opened are public records and must be retained by
the Records Manager at the 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.
6.29 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.
6.30 INTEGRATION:
This Contract represents the entire and integrated agreement between the parties and supersedes
all prior negotiations, proposals, communications, understandings, representations, or agreements,
whether oral or written, express or implied.
6.31 RELATIONSHIPS:
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.
6.32 GOVERNING LAW:
This Contract shall be governed by the laws of the state of Arizona. Venue for any actions or
lawsuits involving this Contract shall be in Maricopa County Superior Court or in the United
States District Court for the District of Arizona, sitting in Phoenix, Arizona
6.33 ORDER OF PRECEDENCE:
In the event of a conflict in the provisions of this Contract and any Exhibits incorporated below, if
applicable, the terms of this Contract shall prevail.

15058-RFP
6.34 INCORPORATION OF DOCUMENTS:
The following are to be attached to and made part of this Contract:
6.34.1 Exhibit A, Pricing;
6.34.2 Exhibit B, Scope of Work;
6.34.3 Exhibit C, Software License and Maintenance Agreements
6.34.4 Exhibit D, Office of Procurement Services Contractor Travel and Per Diem Policy
6.34.5 Exhibit E, Special Federal Terms, Conditions and Documents
NOTICES:
All notices given pursuant to the terms of this Contract shall be addressed to:
For County:
Maricopa County
Office of Procurement Services
ATTN: Contract Administration
320 West Lincoln Street
Phoenix, Arizona 85003-2494
For Contractor:
Contractual:
Ricardo Perez
Contract Manager
TransCore
150 4th Ave. North, Suite 1200
Nashville, TN 37219
Technical:
William L. Skillas, PE
Vice President
TransCore
192 Technology Parkway, Suite 500
Norcross, GA 30092

15058-RFP
MARICOPA COUNTY
CHAIRMAN, BOARD OF SUPERVISORS DATE
ATTESTED:
CLERK OF THE BOARD DATE
APPROVED AS TO FORM:
DEPUTY COUNTY ATTORNEY DATE

15058-RFP
EXHIBIT A
PRICING
SERIAL 15058-RFP
NIGP CODE: 918-42
RESPONDENT'S NAME: TransCore ITS, LLC
COUNTY VENDOR NUMBER : 2011001538 0
ADDRESS: 15300 N. 90th Street, Ste 750
Scottsdale, Arizona 85260
P.O. ADDRESS: N/A
TELEPHONE NUMBER: (480) 551-4600
FACSIMILE NUMBER: (480) 661-5490
WEB SITE: www.transcore.com
CONTACT (REPRESENTATIVE): William L. Skillas
REPRESENTATIVE'S E-MAIL ADDRESS: william.skillas@transcore.com
YES NO REBATE
WILL ALLOW OTHER GOVERNMENTAL ENTITIES TO PURCHASE
FROM THIS CONTRACT [X] [ ]
WILL ACCEPT PROCUREMENT CARD FOR PAYMENT: [X] [ ]
WILL OFFER REBATE (CASH OR CREDIT) FOR UTILIZING
PROCUREMENT CARD: [ ] [X] %
(Payment shall be made within 48 hours of utilizing the Purchasing
Card)
[X] NET 30 DAYS
1.0 PRICING FOR: PROJECT AREA 3
Year 1 Year 2 Year 3 Year 4 Year 5
Implementation/
Professional Services NTE $221,016.90 $ $ $ $
Licensing NTE $58,750 included included included included
Maintenance and
Support NTE $50,947.32 included included included included
Proprietary Hardware NTE $27,125.00 $ $ $ $
NOT TO EXCEED
(NTE) TOTAL $357,839.23
1.0 PRICING FOR: PROJECT AREA 4
Year 1 Year 2 Year 3 Year 4 Year 5
Implementation/
Professional Services NTE $199,170.42 $ $ $ $
Licensing NTE $58,750 included included included included
Maintenance and
Support NTE $50,947.32 included included included included
Proprietary Hardware NTE $42,586.25 $ $ $ $
NOT TO EXCEED
(NTE) TOTAL $351,454.00

15058-RFP
EARLY TERMINATION OF MAINTENANCE
MCDOT shall have the option to discontinue maintenance and support on a yearly basis and receive a
rebate of funds paid up front for the four-year subscription for unused years of maintenance, per the
sliding scale shown below. Partial years of maintenance will not be refunded. The following schedule of
rebates applies:
Termination of M&S after year 1: $50,947.32 refund
Termination of M&S after year 2: $38,210.49 refund
Termination of M&S after year 3: $25,473.66 refund
Termination of M&S after year 4: $12,736.83 refund

15058-RFP
System Verification & Acceptance
This section identifies required, but not limited to, verification activities that will lead to project Final
Acceptance. System verification testing shall be conducted by the contracted system provider to verify
that the ASCT complies with the functional requirements as listed in the Technical Requirements shown
in Attachment C of "Serial 15058 - RFP Request for Proposal for Bell Road Adaptive Signal Control
Technology (ASCT) Deployment".
The contracted system provider shall provide any and all necessary on-site and off-site support, labor and
equipment as appropriate during the system implementation, integration and verification testing. A
proposed System Verification Plan shall be provided by the contracted system provider within 15
working days after Notice to Proceed. The Proposed Verification Plan shall be submitted to and
reviewed by MCDOT. Any deficiencies in the proposed plan will be identified by MCDOT. All
deficiencies identified shall be addressed by he contracted system provider.
All system requirements listed in the Technical Requirements & Responses table identified by the
contracted system provider as “Provided”, and accounting for stated and MCDOT accepted concessions
regarding to what extent they are met, shall be verified using one of the following verification methods:
 Demonstration is used for a requirement that the system can demonstrate without external test
equipment.
 Test is used for a requirement that requires some external piece of test equipment.
 Analyze is used for a requirement that is met indirectly through a logical conclusion or
mathematical analysis of a result. For example, algorithms for congestion: the contracted system
provider may need to show that the requirement is met through the analysis of count and
occupancy calculations in software or firmware.
 Inspection is used for verification through a visual comparison.
The proposed System Verification Plan submitted by the contracted system provider shall identify the
specific verification method, location, stage at which the project verification is anticipated to occur, and
verification procedure for each system requirement shown in the system Technical Requirements &
Responses table. Additional details may be provided to or requested by MCDOT, in addition to
identifying the verification method, as necessary to clarify the proposed verification procedure.
The proposed System Verification Plan shall contain as a minimum, but not limited to, a schedule
showing all activities, testing procedures relative to other project schedule components, equipment
needed, personnel and roles. The proposed System Verification Plan shall include examples of forms to
be used during testing for documentation purposes, acceptance criteria, duration(s) of each test,
compliance criteria, retesting timeframes and shall provide a place on the form to record results.
The proposed System Verification Plan responses to each system requirement will be subject to approval
by MCDOT. Each system requirement, accounting for stated and MCDOT accepted concessions
regarding to what extent they are met, shall be associated with a verification procedure.
The contracted system provider shall identify how the veracity of the items listed in System
Requirements Reference Number 6.0-5 can be verified by the agency. The contracted system provider
shall detail the method/source of data acquisition and calculation algorithm(s) (methodology) to the
agency resulting in validating the veracity of providing accurate data back to the ASCT and producing
accurate performance measures listed in the System Requirements Reference Number 6.0-5.
All deliverables included as part of the System Verification shall be listed as part of the proposed System
Verification Plan submittal to MCDOT. MCDOT may request the proposed forms be revised. All forms
shall be approved by MCDOT before use.
MCDOT will respond to a submitted proposed System Verification Plan within 20 working days, noting
any specific requirement procedures that may require clarification, further detail or revision. The

15058-RFP
contracted system provider shall revise the Proposed Verification Plan as directed, until acceptance of the
System Verification Plan is granted by MCDOT.
All requirements listed in the Technical Requirements & Responses table shall be met. Requirements
found to be deficient to any level other than full compliance shall be deemed not accepted and final
acceptance shall not be granted until all items are resolved. No additional compensation will be given to
bring the system into compliance if found to be non-compliant during the System Verification procedures
for requirements noted as compliant by the contracted system provider in the Technical Requirements &
Responses table as part of this agreement.
MCDOT shall identify a Verification Monitor, responsible for observing and documenting the results of
each verification procedure. Any verification failure or lack of performance to meet the stated system
requirements shall be recorded by the Verification Monitor and the contracted system provider shall
prepare a report stating why a system requirement was not met. The report shall include a proposed
solution to resolve the deficiency and shall be submitted to MCDOT within 10 working days after the
failure is discovered. If the proposed solution includes a software revision or hardware replacement,
upgrade, or repair, such mitigation shall be executed and retested. No additional payment shall be made
for such solution.
If there is a system requirement that the contracted system provider is not able to meet, the contracted
system provider shall document in a report, and develop a proposed plan to provide similar performance
or operation to meet the requirement. The proposed revised approach to meet the system requirement
shall be subject to review and approval by MCDOT, and new testing of the revised requirement shall be
initiated within 10 working days of any approved approach.
Upon completion of all required verification testing, the contracted system provider shall prepare an final
System Verification Report which will document:
 Verification procedures
 Verification Results
 Necessary mitigations/revisions
 Retesting procedures and results
 Final disposition of each system requirement listed in the Technical Requirements & Responses
table
 Failures and detailed resolution to each of the failures
The Final System Verification Report shall be submitted to MCDOT for review. Any comments
resulting from the review shall be transmitted to the contracted system provider. The report shall be
revised as directed, and resubmitted to MCDOT. An Approved Final Verification Report is necessary for
final project acceptance.
Milestone Payments
The parties acknowledge that payment for the Milestones hereunder be payable only upon the County’s
acceptance of such Milestone, acceptance of which shall not be unreasonably withheld, delayed or
conditioned. The Schedule of Milestones, as defined below, is inclusive of the terms and conditions
within the Master Agreement.
Milestone 1 – Mobilization
Milestone Value - 10% of Total Project Cost (Area 3) $ 35,783.92
Milestone Value – 10% of Total Project Cost (Area 4) $ 35,145.40
Milestone 2 - Intersection Detection Identification
The system provider shall work cooperatively with MCDOT and MCDOT’s design consultant to identify
specific detection to be provided on each approach, for each movement, resulting from the ASCT system
configuration mutually agreed to by MCDOT and the system provider for this project. Such detection
will be provided by MCDOT under separate contract, unless specifically made a part of the system
provider's contract herein. System provider shall specify, detection distances, zone(s), output
configuration (channels) and method of verification of suitable detection implementation resulting in the

15058-RFP
optimum conditions for the system provider's ASCT system to operate successfully. MCDOT shall
review and approve system providers recommendations for detection implementation. Final plans shall
be the responsibility of MCDOT. System provider shall note that 15 specific locations are available for
intrusive detection (loops). All others shall use non-intrusive detection methods that do not result in any
ground disturbance.
Vendor shall also supply specifications for detection technologies and systems that are compatible with
their system resulting in maximum system effectiveness. Vendor shall identify any detection
technologies or systems that are incompatible with or unsuitable for use with their proposed system.
Milestone Value - 30% of Total Project Cost (Area 3) $ 107,351.77
Milestone Value - 30% of Total Project Cost (Area 4) $ 105,436.20
Milestone 3 - System Installation and Training
The system provider shall deliver, install, configure and set up all hardware and software associated with
the ASCT system, and conduct agency staff training per the terms and conditions of this agreement.
System provider shall acknowledge that the field detection elements, installed by separate contract,
unless specifically made a part of the system provider's contract herein, shall be in-place and functional
prior to full ASCT implementation and agency staff training.
Milestone Value - 30% of Total Project Cost (Area 3) $ 107,351.77
Milestone Value - 30% of Total Project Cost (Area 4) $ 105,436.20
Milestone 3 - Final Acceptance
The system provider shall attain Final Acceptance from MCDOT based on successfully passing the
testing requirements of the MCDOT approved Verification Plan, which test functionality and compliance
to the System Technical Requirements agreed to by the system provider under the terms and conditions
of this agreement.
Milestone Value - 30% of Total Project Cost (Area 3) $ 107,351.77
Milestone Value - 30% of Total Project Cost (Area 4) $ 105,436.20

15058-RFP
EXHIBIT B
SCOPE OF WORK
1 PROJECT APPROACH/METHODOLOGY
1.1 Solution Overview
TransCore ITS, LLC, in association with KLD Engineering, P.C. (KLD) is proposing to deploy
the Adaptive Control with Decision Support System (ACDSS) in response to the Bell Rd Adaptive
Signal Control Technology (ASCT) Deployment RFP. ACDSS is a comprehensive adaptive traffic
control module, developed by KLD, which is fully integrated with TransCore’s TransSuite®
Traffic Control System (TCS). ACDSS provides the following features:
 Fully NTCIP compatible, works with existing traffic control infrastructure, and supports
multiple types of controllers (including Econolite ASC3 and Cobalt)
 Flexible detectorization requirements, supports sparse detector layouts
 Cutting-edge multi-objective, multi-regime signal optimization, capable of handling both
unsaturated and oversaturated traffic conditions
 Applicable to small cluster of intersections, arterials, diamond interchanges, and grid
networks of hundreds of intersections
 User definable periods to run the system according to a schedule, with ability to turn on or off
manually
 Deals with short-term traffic variations, and long-term pattern drifting

15058-RFP
ACDSS is operational on an arterial in Staten Island, NY similar to Bell Road. It is the ASCT component of one of
the largest Active Traffic Management (ATM) systems in the U.S. – the Midtown in Motion (MIM) system
deployed in New York City. In highly congested Midtown Manhattan, ACDSS has delivered an average 10%
improvement in travel speeds, and a 5% reduction in vehicle emissions. On the Staten Island arterial, it has achieved
a travel time saving of 10-15% during peak hours and 7-9% reductions in fuel consumption and pollutant emissions.
Figure 4-1 presents the ACDSS system architecture. Figure 4-1 - ACDSS System Architecture
ACDSS is integrated with the TransSuite TCS via a web
services interface. Communications between ACDSS and
the field controllers are accommodated through the
TransSuite TCS system. This means no communications
modifications shall be required for the Bell Road signals
as the TransSuite system is fully compatible with the
participating Cities’ existing IP-based network
architecture. ACDSS is highly flexible in terms of
detection requiring minimal detectorization. Preferred
detection includes advanced detection on the mainline and
major side streets, as well as stop bar detection for left
turns.
ACDSS is highly integrated with the TransSuite TCS
making use of TransSuite’s Unified Controller Manager
(UCM) and Central Communications Server (CCS) to
affect control selected intersections. Adaptive status is
monitored by the TCS providing historical detector data
when failover thresholds are not exceeded. Additionally, if
intersections fail out of adaptive mode, the TCS reverts
intersection control to the previously selected mode
automatically. All statuses are viewable in the TCS Proper
as well as all graphical reports, including ATMS Map and
ATMS Explorer. Adaptive mode can be initiated both
manually and via the TCS scheduler allowing more
strategic control of the selected corridor.
1.2 Proposed Approach
TransCore’s proposed solution is being
offered for two of the four project areas identified in the RFP. Specifically our proposal is
addressing Project Areas 3 and 4, the Cities of Scottsdale and Phoenix. TransCore’s proposed
ACDSS based solution shall leverage the existing TransSuite TCS deployment in each City. In
addition, the Arizona Department of Transportation (ADOT) is a TransSuite TCS user allowing
simpler integration of the ADOT intersection of Bell Road and I-17 in Project Area 4. The
following Sections discuss the approach to deploying ASCT in Phoenix and Scottsdale.
1.2.1 Scottsdale Deployment
1.2.1.1 System Deployment
TransCore shall deploy ACDSS integrated with the existing City of Scottsdale
TCS. Currently TransSuite is deployed in a virtual environment hosted on City
of Scottsdale servers. ACDSS shall be deployed in this virtual environment
saving the cost of additional hardware for the City of Scottsdale ASCT.
TransCore shall discuss this hardware deployment option with the City of
Scottsdale and Scottsdale IT. We shall secure an additional virtual machine from
the City of Scottsdale. The ACDSS virtual machine shall need to be configured
as follows:
 4 compute cores
 16GB RAM
 500GB Hard Drive
 Windows Server 2012R2

15058-RFP
Optionally, TransCore can procure and install a new server specifically for the
ACDSS implementation. TransCore has not included the cost of this server in
this proposal. That server would serve as host for the ACDSS applications and
shall reside in the City of Scottsdale TMC. The new server would consist of the
following:
 Dell PowerEdge R730 rackmount server
 Intel Xeon E5-2650L Processor (12 processing cores)
 64GB Memory
 2 x 1.2TB 10K RPM Hard Drives (RAID-1)
 PERC H330 RAID Controller
 4 x 1Gb Network Ports
 Windows Server 2012R2
 3-year Pro Warranty
As part of the ACDSS deployment, TransCore shall update the City of
Scottsdale TCS to the most recent release at the time of deployment. This shall
ensure compatibility and ease support for both Project Area 3 and 4. The City of
Scottsdale is also a user of the TransSuite Traveler Information System. We
shall upgrade this TransSuite module as well, bringing it to current release
standards.
ACDSS interfaces with TransSuite through a defined web service allowing data
to be exchanged between the respective servers. TransCore shall activate the
ACDSS web service on the City of Scottsdale server for ASCT. This shall allow
ACDSS to actively manage intersections on the TCS for the Bell Rd. ASCT.
Figure 1-2 is a high level diagram of the proposed system deployment for the
City of Scottsdale and Project Area 3.
Figure 1-2: Project Area 3 ASCT Architecture

15058-RFP
1.2.1.2 Controller Modifications
Deployment of ACDSS shall require upgrades to the controllers deployed in the
City of Scottsdale. Those intersections are identified in Attachment B of the
RFP and are listed here for reference:
 Frank Lloyd Wright Boulevard and Scottsdale Road
 Frank Lloyd Wright Boulevard and Promenade
 Frank Lloyd Wright Boulevard and 76th Street
 Frank Lloyd Wright Boulevard and Greenway-Hayden Loop
 Frank Lloyd Wright Boulevard and Northsight Boulevard
 Frank Lloyd Wright Boulevard and Hayden Road
 Frank Lloyd Wright Boulevard and L-101 (Pima Freeway)
 Frank Lloyd Wright Boulevard and 90th Street
 Frank Lloyd Wright Boulevard and 92nd Street/100th Street
 Frank Lloyd Wright Boulevard and Thompson Peak Parkway
ACDSS requires access to the ACS Lite objects available via NTCIP on the
ACS-3 controllers. Activation of these objects requires the use of a data key
obtained from Econolite. TransCore shall procure these data keys for the ASCT
project and activate the ACS Lite objects on the Area 3 intersections above.
TransCore shall review controller operation with City of Scottsdale staff prior to
activating the ACS Lite modules. This shall minimize the likelihood of any
adverse functionality of the upgraded controllers in the field.
1.2.1.3 Detection Requirements
Project Area 3 includes 10 intersections. ACDSS can be deployed for the
Scottsdale ASCT using "AS IS" detection based on the following conditions:
1. Detection "AS IS" is supported by ACDSS, provided that all detectors are
in working conditions and provide 30-second aggregated volume and
occupancy data.
2. Using detection "AS IS", ACDSS adaptive over-saturated control (queue
balancing and queue management) shall not be activated. At the critical
intersections, the crossing arterials shall have to be treated as minor traffic
(without additional advance detectors).
3. "AS IS" detection shall be suitable for light to medium-light traffic (no
serious cycle failures, no queue spill backs of left turns) on the mainline,
while there are no prevalent queuing issues at minor approaches with just
random variations and no systematic capacity problems.
To make better use of the features of ACDSS, three detection scenarios are
proposed. For all three scenarios, the data shall be volume and occupancy data,
aggregated at minimum every 30 seconds. Since no ground disturbing activities
are allowed, only Video or Radar based detection technology is considered.
All additional detection proposed is advance detection. Compared to stop line
detection, advance detection provides better time/space dimensions of data for
demand estimation and queue prediction, especially when a phase becomes
saturated and when cycle failures occur.

15058-RFP
Scenario A requires adding advanced detection on 4 critical intersections, namely,
 Frank Lloyd Wright Blvd @ Scottsdale Rd
 Frank Lloyd Wright Blvd @ Greenway-Hayden Loop
 Frank Lloyd Wright Blvd @ 101
 Frank Lloyd Wright Blvd @ Thompson Parkway
At these critical intersections, advanced detection is added at protected left turn lanes and thru lanes of both cross
street and main line. Non-critical intersections use detection AS IS.
In Scenario A (Figure 1-3), critical intersections’ cycle, offset and splits are continuously optimized on a cycle-by-
cycle basis. Cycle optimization provides the needed capacity proactively with varying demand levels; offset
optimization provides the progression for the prevailing pattern; and split optimization optimizes splits to either
minimize delay when traffic is unsaturated, or perform queue management when traffic becomes oversaturated.
Those non-critical intersections that use detection AS IS shall have to depend on critical intersections to determine
their optimal cycle and offsets in real-time. The splits of those intersections shall be optimized only if stop-line
detection is available on all approaches, otherwise no split optimization shall be performed (splits shall be
determined by the underlying base plans). Scenario A provides the most cost-effective detection plan; it works
best if those non-critical intersections have minor/random cross street traffic demand.
Figure 1-3: Project Area 3: Detection Proposal Scenario A
Locations to add Advance Detections
on Left Turns and on Thru Lanes of both Mainline Detection "As Is"
and Cross Road

15058-RFP
Additional Per-Lane Advance Detectors
Scenario A Cross Rd FLW Boulevard
NBL NBT NBR SBL SBT SBR EBL EBT EBR WBL WBT WBR
Frank Lloyd Wright Blvd
Y Y Y Y Y Y Y Y
& Scottsdale
Frank Lloyd Wright Blvd
& Promenade
Frank Lloyd Wright Blvd
& 76 St.
Frank Lloyd Wright Blvd
Y Y Y Y Y Y Y Y
& Greenway Hayden Loop
Frank Lloyd Wright Blvd
& Northsight Blvd
Frank Lloyd Wright Blvd
& Hayden Rd
Frank Lloyd Wright Blvd
Y Y Y Y Y Y Y Y
& L101
Frank Lloyd Wright Blvd
& 90th St.
Frank Lloyd Wright Blvd
& 92nd St.
Frank Lloyd Wright Blvd
& Thompson Peak Y Y Y Y Y Y Y Y
Parkway
Scenario B is one step further of Scenario A. In addition to the four critical intersections, advance detection is
added on mainline protected left turn lanes and thru lanes as well.
In Scenario B (Figure 1-4), all intersections cycle, offset and splits are continuously optimized on a cycle-by-cycle
basis. Cycle optimization provides the needed capacity proactively with varying demand levels; offset optimization
provides the progression for the prevailing pattern; and split optimization optimizes splits to either minimize delay
when traffic is unsaturated, or perform queue management when traffic becomes oversaturated (such as special
events).
In Scenario B, when traffic becomes oversaturated at critical intersections, ACDSS adaptive control system can
automatically perform queue management (queue balancing) strategy to mitigate congestion (because advance
detection is available on all approaches). Since non-critical intersections have no advance detection on minor
approaches, queue management shall not be available.
Scenario B provides a relatively cost-effective detection plan, with its capacity to support fully adaptive
operation with cycle, offset and split optimized on a cycle by cycle basis for all intersections; it works best if
those non-critical intersections have light to mid-level cross street traffic demand with variability and no
significant queueing issues at minor approaches.

15058-RFP
Figure 1-4: Project Area 3: Detection Proposal Scenario B
Locations to add Advance Detections
on Left Turns and on Thru Lanes of both Mainline Locations to add Advance Detections on Left Turns and on Thru Lanes
and Cross Road of Mainline ONLY
Additional Per-Lane Advance Detectors
Scenario B Cross Rd FLW Boulevard
NBL NBT NBR SBL SBT SBR EBL EBT EBR WBL WBT WBR
Frank Lloyd Wright Blvd
Y Y Y Y Y Y Y Y
& Scottsdale
Frank Lloyd Wright Blvd
Y Y Y Y
& Promenade
Frank Lloyd Wright Blvd
Y Y Y Y
& 76 St.
Frank Lloyd Wright Blvd
Y Y Y Y Y Y Y Y
& Greenway Hayden Loop
Frank Lloyd Wright Blvd
Y Y Y Y
& Northsight Blvd
Frank Lloyd Wright Blvd
Y Y Y Y
& Hayden Rd
Frank Lloyd Wright Blvd
Y Y Y Y Y Y Y Y
& L101
Frank Lloyd Wright Blvd
Y Y Y Y
& 90th St.
Frank Lloyd Wright Blvd
Y Y Y Y
& 92nd St.
Frank Lloyd Wright Blvd
& Thompson Peak Y Y Y Y Y Y Y Y
Parkway
Scenario C requires installing advance detection on all protected left turn lanes and thru lanes, of both mainline and
minor approaches, at all intersections.

15058-RFP
In Scenario C (Figure 1-5), all intersections’ cycle, offset and splits are continuously optimized on a cycle-by-cycle
basis. Cycle optimization provides the needed capacity proactively with varying demand levels; offset optimization
provides the progression for the prevailing pattern; and split optimization optimizes splits to either minimize delay
when traffic is unsaturated, or perform queue management when traffic becomes oversaturated (such as special
events).
In Scenario C, when traffic becomes oversaturated at critical intersections or at minor intersections, ACDSS
adaptive control system can automatically perform queue management (queue balancing) strategy to mitigate
congestion (because advance detection is available on all approaches).
Scenario C provides a basis for the most comprehensive adaptive signal operation, for multi-regime adaptive
control of both unsaturated and oversaturated traffic. It works best that non-critical intersections have
occasionally heavy cross street traffic demand with variability and significant queueing issues at both minor
approaches and main approaches.
Figure 1-5: Project Area 3: Detection Proposal Scenario C
Locations to add Advance Detections
on Left Turns and on Thru Lanes of both Mainline
and Cross Road

15058-RFP
Additional Per-Lane Advance Detectors
Scenario C Cross Rd FLW Boulevard
NBL NBT NBR SBL SBT SBR EBL EBT EBR WBL WBT WBR
Frank Lloyd Wright Blvd
Y Y Y Y Y Y Y Y
& Scottsdale
Frank Lloyd Wright Blvd
Y Y Y Y Y Y Y Y
& Promenade
Frank Lloyd Wright Blvd
Y Y Y Y Y Y Y Y
& 76 St.
Frank Lloyd Wright Blvd
Y Y Y Y Y Y Y Y
& Greenway Hayden Loop
Frank Lloyd Wright Blvd
Y Y Y Y Y Y Y Y
& Northsight Blvd
Frank Lloyd Wright Blvd
Y Y Y Y Y Y Y Y
& Hayden Rd
Frank Lloyd Wright Blvd
Y Y Y Y Y Y Y Y
& L101
Frank Lloyd Wright Blvd
Y Y Y Y Y Y Y Y
& 90th St.
Frank Lloyd Wright Blvd
Y Y Y Y Y Y Y Y
& 92nd St.
Frank Lloyd Wright Blvd
& Thompson Peak Y Y Y Y Y Y Y Y
Parkway
1.2.2 Phoenix Deployment
1.2.2.1 System Deployment
TransCore shall deploy ACDSS integrated with the existing City of Phoenix and
ADOT TransSuite TCSes. TransCore shall configure and deploy a new virtual
machine on the City of Phoenix’s existing TransSuite servers specifically for the
ACDSS implementation. That server shall serve as host for the ACDSS
applications and shall reside in the City of Phoenix TMC. The ACDSS virtual
machine shall need to be configured as follows:
 4 compute cores
 16GB RAM
 500GB Hard Drive
 Windows Server 2012R2
Optionally, TransCore can procure and install a new server specifically for the
ACDSS implementation. TransCore has not included the cost of this server in
this proposal. That server would serve as host for the ACDSS applications and
shall reside in the City of Phoenix TMC. The new server would consist of the
following:
 Dell PowerEdge R730 rackmount server
 Intel Xeon E5-2650L Processor (12 processing cores)
 64GB Memory
 2 x 1.2TB 10K RPM Hard Drives (RAID-1)
 PERC H330 RAID Controller
 x 1Gb Network Ports
 Windows Server 2012R2

15058-RFP
 3-year Pro Warranty
As part of the ACDSS deployment, TransCore shall update the City of Phoenix
and ADOT TCSes to the most recent release at the time of deployment. This
shall ensure compatibility between the systems where jurisdictional boundaries
intersect. Additionally, this shall allow TransCore to provide support to the
selected contractor for Project Area 2, which has a single intersection identified
for ASCT control as well.
ACDSS interfaces with TransSuite through a defined web service allowing data
to be exchanged between the respective servers. TransCore shall activate the
ACDSS web service on both the City of Phoenix and ADOT TCS servers for
ASCT. This shall allow ACDSS to actively manage intersections on both TCS
for the Bell Rd. ASCT. Figure 1-6 below is a high level diagram of the proposed
system deployment for the City of Phoenix and Project Area 4.
Figure 1-6: Project Area 4 ASCT Architecture
TransCore has assumed network connectivity shall be available between the
City of Phoenix TMC and ADOT TMC allowing ACDSS to communicate with
intersections on both systems as required. In addition, TransCore shall enable
the TransSuite center-to-center (C2C) interface on both systems allowing users
of both systems to view the status of the Bell Rd. intersections. TransCore shall
configure appropriate jurisdictions on each host TransSuite system, allowing
users to monitor intersections on both systems. Control shall be authorized only
for appropriate users of the individual systems. Shared viewing of ASCT
enabled intersections shall also be available through TransSuite’s map-based
and schematic graphics packages, ATMS Map and ATMS Explorer, further
integrating ACDSS into the daily operations of the host systems.

15058-RFP
1.2.2.2 Controller Modifications
Deployment of ACDSS shall require upgrades to the controllers deployed in
both the City of Phoenix and ADOT. Currently the six intersections identified
for ASCT in the City of Phoenix are operating with Econolite ASC2S
controllers. Those intersections are identified in Attachment B of the RFP and
are listed here for reference:
 Bell Road and 35th Avenue
 Bell Road and 33rd Avenue
 Bell Road and 29th Avenue/Holmes Boulevard
 Bell Road and 23rd Avenue
 Bell Road and 21st Avenue
 Bell Road and 19th Avenue
TransCore is proposing to upgrade each of these controllers to Econolite ASC3
controllers for the ASCT Deployment. ACDSS requires access to the ACS Lite
objects available via NTCIP. ACS-3 provides the simplest access to the objects
activating ACS Lite via a data key. TransCore shall be responsible for migrating
existing ACS-2S databases to the ACS3 controllers. TransCore has assumed
City staff shall be available for swapping out the existing ASC2S for the new
ASC3 controllers. Econolite ASC-3 controllers are currently being used
elsewhere within the City of Phoenix so this controller upgrade is consistent
with current controller standards used by the City.
The remaining Project Area 4 intersection is owned by ADOT. This intersection,
Bell Road and I-17, is currently using an Econolite Cobalt controller. This
controller shall not need to be physically replaced. TransCore shall provide the
required data key to activate the ACS Lite objects on the controller.
1.2.2.3 Detection Requirements
Project Area 4 (Figure 1-7) includes 7 intersections. ACDSS can be deployed
for the Phoenix ASCT using "AS IS" detection based on the following
conditions:
1. Detection "AS IS" is supported by ACDSS, provided that all detectors are
in working conditions and provide 30-second aggregated volume and
occupancy data.
2. Using detection "AS IS", ACDSS adaptive over-saturated control (queue
balancing and queue management) shall not be activated. At the critical
intersections, the crossing arterials shall have to be treated as minor traffic
(without additional advance detectors).
3. "AS IS" detection shall be suitable for light to medium-light traffic (no
serious cycle failures, no queue spill backs of left turns) on the mainline,
while there are no prevalent queuing issues at minor approaches with just
random variations and no systematic capacity problems.
To make better use of the features of ACDSS, TransCore proposes additional
detectorization in Area 4. The required data are volume and occupancy data,
aggregated at minimum every 30 seconds. Since all 7 intersections are identified
as “Potential New Detection” in the RFP and have been cleared through a
separate Federal funding process, we propose adding per-lane advance detection
on all protected left turn lanes, and thru lanes of both minor and major
approaches, of all the 7 intersections.
Advance detection provides better time/space dimensions of data for demand
estimation and queue prediction, especially when a phase becomes saturated and
when cycle failures occur.

15058-RFP
Additional advance detection provides the basis for ACDSS to perform effective
multi-regime adaptive control for both unsaturated and oversaturated traffic.
ACDSS optimizes cycle, offset and splits are continuously optimized on a cycle-
by-cycle basis. Cycle optimization provides the needed capacity proactively
with varying demand levels; offset optimization provides the progression for the
prevailing pattern; and split optimization optimizes splits to either minimize
delay when traffic is unsaturated, or perform queue management when traffic
becomes oversaturated. Advance detectors allow ACDSS to identify the regime
of traffic flow and automatically switch to queue management when traffic
becomes oversaturated.
The operational advantage of advance detection is as follows:
With stop-line detection, the information available at best is the so called “phase
saturation”, an equivalent of v/c ratio. When traffic becomes oversaturated on
the approach, stop line detection provides little information regarding the
existence, scale, duration, or severity of oversaturation. Even worse, stop line
detectors may miscount due to tail-gating. Likewise, occupancy data from stop-
line detection is of little value since higher values can be resulted from one
single vehicle staying on the detector. Such data are misleading from an
adaptive control perspective, especially when it comes to oversaturated control
and queue management.
ACDSS multi-regime adaptive control takes advantage of advance detection to
perform effective queue management when traffic becomes oversaturated. Using
advanced detection, the severity of queueing conditions are more accurate, and
can be incorporated into signal optimization for sophisticated congestion
management and queue balance logics.
Figure 1-7: Project Area 4: Detection Proposal
Locations to add Advance Detections
on Left Turns and on Thru Lanes of both Mainline
and Cross Road

15058-RFP
Additional Per-Lane Advance Detectors
Area 4 Cross Rd Bell Rd
NBL NBT NBR SBL SBT SBR EBL EBT EBR WBL WBT WBR
Bell Rd & 35th Ave Y Y Y Y Y Y Y Y
Bell Rd & 33th Ave Y Y Y Y Y Y Y Y
Bell Rd & 29th Ave Y Y Y Y Y Y Y Y
Bell Rd & I-17 Y Y Y Y Y Y Y Y
Bell Rd & 23th Ave Y Y Y Y Y Y Y Y
Bell Rd & 21th Ave Y Y Y Y Y Y Y Y
Bell Rd & 19th Ave Y Y Y Y Y Y Y Y

15058-RFP
2 WORK PLAN
2.1 Project Areas
Figure 2-1 and Figure 2-2 presents the 17 candidate intersections along Bell Road/ Frank Lloyd
Wright Boulevard in Project Areas 3 and 4 per the RFP. These are the two Project Areas
TransCore is addressing with this proposal. Preliminary field surveys shall be conducted to assess
the general traffic conditions and shall be factored into determining any additional detector
requirements.
Figure 2-1: Project Area 3
Figure 2-2: Project Area 4

15058-RFP
2.2 Project Management
TransCore shall provide project management for the Bell Rd ASCT. A kick-off meeting shall be
scheduled with each jurisdiction subsequent to notice to proceed. This kick-off meeting shall
include a review of the requirements matrices for Project Areas 3 and 4. The purpose of the
requirements review is to clarify any ambiguity in our proposal response for the deployment of
ACDSS. Site visits to each existing TMC and field reviews for each corridor shall be scheduled
subsequent to the kick-off meetings. TransCore shall submit meeting minutes from the kick-off
meeting within 5 business days for comment.
Bi-weekly status meetings shall be held through final acceptance of the project. Final acceptance
is discussed in Section 3.4 of the RFP. TransCore envisions these bi-weekly meetings as
teleconferences between all involved parties.
The following sections present our proposed Scopes of Work for each Project Area.
2.3 Scope of Work – Area 3
The proposed ACDSS adaptive signal control system supports multi-regime variable objective
adaptive signal control (Figure 2-3). It handles oversaturated traffic and unsaturated traffic
seamlessly on a cycle-by-cycle basis, providing delay minimization or queue management with
varying traffic demands. For various geometry types, from diamond interchanges to urban grids,
from CBD critical intersections or arterials to cluster of intersections, ACDSS applies
differentiated adaptive treatments that better address the geometric characteristics for real time
signal optimization.
Area 3 is featured by an E-W bound arterial of 10 intersections. Four (4) critical intersections are
identified, including the following:
 Frank Lloyd Wright Blvd @ Scottsdale Rd
 Frank Lloyd Wright Blvd @ Greenway-Hayden Loop
 Frank Lloyd Wright Blvd @ 101 (SPUI)
 Frank Lloyd Wright Blvd @ Thompson Peak Parkway

15058-RFP
Figure 2-3: ACDSS Multi-Regime Variable Objective Adaptive Signal Control for Different Geometric
Characteristics and Traffic Flow Conditions
Arterial Progression ACDSS - System Kernel Multi-Source Data Fusion
and Management
Queue Management
Signal
Congestion Management Algorithm
Grid Network Control Repository Optimization
Diamond Interchange
Real-time Database
- In-Memory
- On Disk
Data Interface Data Interface
Signal Timing Interface Signal Timing Interface
Algorithm Level) Algorithm
Signal Signal Level)
Code
New New (Script
A Optimization (Source Algorithm A Optimization
Signal
(Binary)
New
A Optimization
2.3.1 Project Area 3 - Detection Scenarios
Four Detection Scenarios are proposed for Project Area 3, for adaptive signal operations
on this arterial, each with different operational characteristics, and pricing implications.
Scenario “AS IS” uses detection “AS IS”, with existing stop line detectors.
For this scenario, ACDSS operation shall primarily address unsaturated traffic (light to
medium light traffic), providing optimized progression based on prevailing traffic
directional pattern. No queue management or queue balancing optimizations are
involved. Cycle length shall be optimized based on the real-time capacity needs of the
critical intersections (up to a certain demand level under saturation). Offsets shall be
determined based on the identified pattern. Splits shall be optimized based on stop line
detections for delay minimization. At approaches where there is no stop line detection,

15058-RFP
splits shall be adjusted based on the cycle length as determined by the critical
intersections. This detection scenario is suitable if the arterial in question has no serious
cycle failures and no left turn spill backs with existing signals, while minor approaches
only have random traffic arrivals without queueing.
Scenario A requires adding additional advance detectors, at the four critical
intersections listed above, both on mainline and minor approaches.
This scenario allows the system to perform adaptive signal operations as permitted by
Scenario “AS IS”. Additionally, Scenario A allows ACDSS to perform the following two
operations:
 Queue Management at Critical Intersections
Queue management shall be performed at the critical intersections when traffic on all
approaches has queueing, typical of the intersection with two major arterials crossing
each other. When queue management is active, signals are optimized to prevent
cycle failure and queue spillbacks, giving all directions balanced treatment, without
compromising the other crossing approaches (e.g., Scottsdale Rd, L101 Freeway off
ramps)
Queue balancing when properly operated, can further provide more coherent
platoons on the progression since the critical intersections by themselves can be
utilized as the “metering” point for certain management strategies.
 Diamond Interchange Adaptive Control at L101 (Pima Freeway)
Diamond interchange (or similar geometry) is characterized by two closely spaced
intersections (that may be controlled by one single controller), with left turns on the
common approach connecting the two intersections. The common approach
generally is a short block fed by movements from various phases. The primary
objective of diamond interchange adaptive control is to ensure that queues do not
block the common approach and spill back into the intersections, with the priority to
not impact freeway operations. This is treated as a special type of over-saturated
control by ACDSS, requiring advance detectors to be deployed for each phase. The
phases of two intersections are processed in a combined manner. Each detector
provides volume and occupancy data, which are converted to calculate slack time the
subject phase can contribute, or additional green time the subject phase would need.
The algorithm systematically distributes the slack time based on the needed extra
time, while selectively applying traffic gating at certain phases to meet the control
goal.
On top of Scenario A, Scenario B requires adding additional advance detectors,
at those non-critical intersections, mainline only.
This scenario allows the system to perform adaptive signal operations as permitted
by Scenario “AS IS” and Scenario A queue management. Additionally, Scenario B
allows ACDSS to perform the following extra:
 Progression fine tuning due to secondary platoons along the arterial.
This scenario allows the system to further fine tune the progression when the arterial
has non-trivial secondary platoons. Secondary platoons are generated by the left-
turning or right-turning vehicles. On the contrary, primary platoons are those
vehicles that go through from both ends of the arterial. Using these extra advance
detectors, ACDSS shall be able to fine tune the progression for secondary platoons.

15058-RFP
Scenario C requires adding additional advance detectors, at all intersections, on
both mainline and minor approaches.
This scenario is the superset of all previous detection scenarios (AS IS, Scenario A and
B). It provides the redundancy and robustness for a comprehensive adaptive system to
perform both unsaturated and oversaturated control when needed at all intersections.
Signals are optimized for facilitating progression, minimizing delay, and maximizing
throughput. Queue management is performed systematically at relevant intersections
when necessary.
This scenario is typically best for an arterial that carries significant directional traffic with
non-trivial demands at minor approaches causing queuing and delays.
2.3.2 Project Area 3 – Tasks
Project Area 3 Scope of Work includes the following tasks.
2.3.2.1 Project Staging, Initial Project Meeting with the Agency.
This task involves project staging, initial project kick-off meeting with the
Agency and all stake holders. The Agency stipulates their expectation of the
adaptive operations, for example, progression focused and/or perform queue
management at critical intersections. The Agency provides policy guidelines
when it comes to prioritized treatments over conflicting objectives.
Detection Scenario shall be determined by the time this task completes.
DELIVERABLE: Report documenting the project staging decisions, the
operational goals and control objectives as stipulated (expected) by the Agency,
and policy guidelines.
2.3.2.2 Review Existing Signal Plans, Signal Sequences, Field Survey
This task reviews the existing signal plans and phase sequences. A field survey
shall be performed to obtain insights of the existing and (potentially) future
traffic flow conditions, and the existing detector set up. If the detection scenario
calls for new installation of additional detectors, the preferred detector setbacks
shall be determined by the time this task completes.
Test of Performance Plan shall be drafted and submitted for the Agency review
and approval.
DELIVERABLE: Report of the findings of the field survey, and draft Test of
Performance Plan. Recommended setbacks for additional advance detectors.
Recommended phase sequences to be employed in adaptive (if change of
existing sequence is in order).
2.3.2.3 Procure New Virtual Machine from Scottsdale IT
TransCore shall negotiate the procurement of an additional virtual machine from
the City of Scottsdale IT department. This virtual machine shall host the ACDSS
server for the Project Area 3 ASCT. The virtual machine shall be configured as
described in Section 1.2.1.1 of this proposal.
DELIVERABLE: New virtual machine configured as ACDSS Server for Project
Area 3.

15058-RFP
2.3.2.4 Configure and Install New Scottsdale TransSuite® Build
TransCore shall configure and install a new Scottsdale specific TransSuite build
updating their existing software to the latest available release. This version of
TransSuite shall have the ACDSS interface enabled allowing integration with
the new ACDSS server.
DELIVERABLE: Updated City of Scottsdale TransSuite software.
2.3.2.5 Install ACDSS Software on a Central Server
ACDSS software shall be installed on the new virtual machine procured in
Section 2.3.2.3 above. Relevant TransSuite TCS credentials shall be set up to
allow the adaptive control system to retrieve detector data, controller status data,
and perform adaptive control.
The communication between ACDSS adaptive control module and TransSuite
TCS shall be tested and validated.
DELIVERABLE: Installed ACDSS software on the server. Login credentials of
ACDSS software.
2.3.2.6 Verify (Existing and/or New) Detection and Set Up Data Feeds, Examine
Detection Data Accuracy and Quality
Depending on the Detection Scenario selected and operational goals set by the
Agency, this task involves testing and validating the data stream of existing
detectors via the TransSuite Adaptive Control Web Service interface. If it is
decided by the Agency to have additional detectors installed, this task shall also
verify that those new detectors (as configured as system detectors) can report the
required volume and occupancy data at 30-sec intervals, and the data are
accurate and reliable to meet adaptive control requirement.
DELIVERABLE: Report documenting the results, conclusions and suggestions.
Suggestions to the additional detectors (if decided) regarding improvement on
their data quality and accuracy if needed.
2.3.2.7 Update Existing ASC3 Controllers
TransCore shall update the existing City of Scottsdale ASC3 controllers to
enable the ACS Lite objects required for ACDSS. This update shall consist of
the installation of a data key at each controller location. TransCore shall
coordinate with City staff to accomplish these updates.
The updated controllers shall be tested to verify the needed adaptive control
object has been correctly implemented to allow the adaptive control operations
by ACDSS from the central system. Controller actions in response to pedestrian
calls and vehicle calls are examined and tested with the presentence of adaptive
control objects.
DELIVERABLE: Data keys to enable ACS Lite objects on 10 existing City of
Scottsdale Econolite ASC3 controllers
DELIVERABLE: Report documenting the testing results, conclusions and
suggestions. Suggestions to fine tune certain actuated parameters to fit adaptive
control operations when necessary.
2.3.2.8 Configure ACDSS
In this task, ACDSS is configured for operating adaptive signals on 10
intersections. The configuration shall be based on the determined Detection

15058-RFP
Scenario, the operational priority, and control objectives/goals as determined
from the project staging task.
DELIVERABLE: Configured ACDSS, and a report documenting the
configuration.
2.3.2.9 System go-live
In this task, ACDSS adaptive control shall be turned on in two steps. The first
step is the “One-Way” burn-in, i.e., ACDSS receives all the needed real-time
detector data and controller status data, performs signal optimizations and
determines optimized timings, and logs all computation and data, without
actually transmitting the new timing to the field controllers. This step is for
double checking that the system configuration, the communication, and the
optimization process are as designed. After verification of the first step, the
system shall be turned on as “Two-Way” operation, with field controllers being
fully controlled by ACDSS live and 7/24.
DELIVERABLE: Report documenting the go-live process, and the live system.
2.3.2.10 System Fine Tuning
In this task, ACDSS shall be fine-tuned to adjust relevant parameters to further
improve the adaptive operation. For example, queue balancing might be turned
on and off, with different priorities adjusted for different turning movements at
the diamond interchange. This task may involve iterative discussions with the
Agency on the operational objectives and policy guidelines when needed, after
examining the impacted traffic flow conditions under adaptive.
DELIVERABLE: Report documenting the fine tuning process, and a fine-tuned
live system.
2.3.2.11 Training
In this task, training is provided based on the items as stipulated in the
requirement matrix, covering system operations, trouble shooting, configuration,
administration and calibration. The training shall be presented at the designated
locations for the designated staff of the Agency. Printed course materials and
references, electronic copies of presentations and references shall be provided.
The total number of training sessions and total hours are as stipulated in
the Matrix.
DELIVERABLE: Training in the format as defined in the Requirement Matrix and
relevant materials.
2.3.2.12 90-day Test of Performance
In this task, a 90-day performance test is performed. The system shall be
monitored and support shall be provided to the Agency to assist the performance
test and acceptance. Successful completion of the 90-day performance test
marks final acceptance of the Project Area 3 ASCT for the City of Scottsdale.
DELIVERABLE: Technical and maintenance support during this 90-day period.
Any corrective actions needed to improve the system operations.
2.3.2.13 Final Deployment Report
A final deployment report shall be provided documenting the system
deployment. Project goals and objectives will be discussed at the project Kick
Off Meeting. The final report will include these goals and objectives and how
they have been met.

15058-RFP
DELIVERABLE: Final report for this deployment.
2.3.2.14 Warranty and Support
TransCore shall provide one year of warranty and support for the Project Area 3
ASCT. This warranty and support period is being provided in accordance with
Section 3.7 of the RFP and Section 16 of the Project Area 3 Requirements
Matrix. The one-year warranty and support period shall commence upon the
completion 90-dat performance test as described in Section 2.3.2.12 above.
TransCore has provided optional pricing for ongoing maintenance and support
of the ACDSS system for years 2-5. Maintenance and support of the deployed
City of Scottsdale TransSuite system shall be handled under the existing
maintenance agreement with the City.
DELIVERABLE: One year warranty and support.
DELIVERABLE: Optional ongoing maintenance and support for years 2-5.

15058-RFP
2.4 Scope of Work – Area 4
ACDSS adaptive signal control system supports multi-regime variable objective adaptive signal
control (Figure 2-4). It handles oversaturated traffic and unsaturated traffic seamlessly on a cycle-
by-cycle basis, providing delay minimization or queue management with varying traffic demands.
For various geometry types, from diamond interchanges to urban grids, from CBD critical
intersections or arterials to cluster of intersections, ACDSS applies differentiated adaptive
treatments that better address the geometric characteristics for real time signal optimization.
Area 4 is featured by an E-W bound arterial of 7 intersections. Three (3) critical intersections are
identified, including the following:
 35th Ave @ Bell Rd
 I-17 @ Bell Rd
 19th Ave @ Bell Rd
Figure 2-4: ACDSS Multi-Regime Variable Objective Adaptive Signal Control for Different Geometric
Characteristics and Traffic Flow Conditions
Arterial Progression ACDSS - System Kernel Multi-Source Data Fusion
and Management
Queue Management
Signal
Congestion Management Algorithm
Grid Network Control Repository Optimization
Diamond Interchange
Real-time Database
- In-Memory
- On Disk
Data Interface Data Interface
Signal Timing Interface Signal Timing Interface
Algorithm Level) Algorithm
Signal Signal Level)
Code
New New (Script
A Optimization (Source Algorithm A Optimization
Signal
(Binary)
New
A Optimization

15058-RFP
2.4.1 Project Area 4 - Detection Scenarios
Four Detection Scenarios are proposed for Project Area 3, for adaptive signal operations
on this arterial, each with different operational characteristics, and pricing implications.
Scenario “AS IS” uses detection “AS IS”, with existing stop line detectors.
For this scenario, ACDSS operation shall primarily address unsaturated traffic (light
to medium light traffic), providing optimized progression based on prevailing traffic
patterns. No queue management or queue balancing optimizations are involved.
Cycle shall be optimized based on the real-time capacity needs of the critical
intersections (up to a certain demand level under saturation). Offsets shall be
determined based on the identified pattern. Splits shall be optimized based on stop
line detections for delay minimization. At approaches where there is no stop line
detection, splits shall be adjusted based on the cycle length as determined by the
critical intersections. This detection scenario is suitable if the arterial in question has
no serious cycle failures and no left turn spill backs with existing signals, while
minor approaches only have random traffic arrivals without queueing.
Scenario A requires adding additional advance detectors, at the above three critical
intersections, both on mainline and minor approaches.
This scenario allows the system to perform adaptive signal operations as permitted
by Scenario “AS IS”. Additionally, Scenario A allows ACDSS to perform the
following two operations:
 Queue Management at Critical Intersections
Queue management shall be performed at the critical intersections when traffic
on all approaches has queueing, typical of the intersection with two major
arterials crossing each other. When queue management is active, signals are
optimized to prevent cycle failures and queue spillbacks, giving all directions
balanced treatment, without compromising the other crossing approaches (e.g.,
35th Ave and 19th Ave)
Queue balancing when properly operated, can further provide more coherent
platoons on the progression since the critical intersections by themselves can be
utilized as the “metering” point for certain management strategies.
 Diamond Interchange Adaptive Control at I-17
Diamond interchange (or similar geometry) is characterized by two closely
spaced intersections (that may be controlled by one single controller), with left
turns on the common approach connecting the two intersections. The common
approach generally is a short block fed by movements from various phases. The
primary objective of diamond interchange adaptive control is to ensure that
queues do not block the common approach and spill back into the intersections,
with the priority to not impact freeway operations. This is treated as a special
type of over-saturated control by ACDSS, requiring advance detectors to be
deployed for each phase. The phases of two intersections are processed in a
combined manner. Each detector provides volume and occupancy data, which
are converted to calculate slack time the subject phase can contribute, or
additional green time the subject phase would need. The algorithm
systematically distributes the slack time based on the needed extra time, while
selectively applying traffic gating at certain phases to meet the control goal.
On top of Scenario A, Scenario B requires adding additional advance detectors,
at those non-critical intersections, mainline only.

15058-RFP
This scenario allows the system to perform adaptive signal operations as permitted by
Scenario “AS IS” and Scenario A queue management. Additionally, Scenario B allows
ACDSS to perform the following extra:
 Progression fine tuning due to secondary platoons along the arterial.
This scenario allows the system to further fine tune the progression when the arterial has
non-trivial secondary platoons. Secondary platoons are generated by the left-turning or
right-turning vehicles. On the contrary, primary platoons are those vehicles that go
through from both ends of the arterial. Using these extra advance detectors, ACDSS shall
be able to fine tune the progression for secondary platoons.
Scenario C requires adding additional advance detectors, at all intersections, on
both mainline and minor approaches.
This scenario is the super-set of all previous detection scenarios (AS IS, Scenario A and
B). It provides the redundancy and robustness for a comprehensive adaptive system to
perform both unsaturated and oversaturated control at all intersections. Signals are
optimized for facilitating progression, minimizing delay, and maximizing throughput.
Queue management is performed systematically at relevant intersections when necessary.
This scenario is typically best for an arterial that carries significant directional traffic with
non-trivial demands at minor approaches causing queuing and delays.
2.4.2 Project Area 4 - Tasks
Project Area 4 Scope of Work includes the following tasks.
2.4.2.1 Project Staging, Initial Project Meeting with the Agency
This task involves project staging, initial project kick-off meeting with the
Agency and all stake holders. The Agency stipulates their expectation of the
adaptive operations, for example, progression focused and/or perform queue
management at critical intersections. The Agency provides policy guidelines
when it comes to prioritized treatments over conflicting objectives.
This task shall particularly determine the adaptive operation at I-17@Bell Rd,
which is operated by ADOT. ACDSS can be configured to run I-17@Bell Rd as
an isolated Diamond Interchange Adaptive Control, while the rest of the arterial
as arterial adaptive control with designated critical intersections. Or ACDSS can
treat the entire arterial as one single system, transparently communicating with
two separate TransSuite TCS by the respective Agency for a unified adaptive
control operation. ACDSS fully supports both operations. This shall be
discussed and determined in this task.
Detection Scenario shall be determined by the time this task completes.
DELIVERABLE: Report documenting the project staging decisions, the
operational goals and control objectives as stipulated (expected) by the Agency,
and policy guidelines. Treatment on I-17@Bell Rd (as isolated Diamond
Interchange Adaptive Control operation, or as unified adaptive control).
2.4.2.2 Review Existing Signal Plans, Signal Sequences, Field Survey
This task reviews the existing signal plans and phase sequences. A field survey
shall be performed to obtain insights of the existing and (potentially) future
traffic flow conditions, and the existing detector set up. If the detection scenario

15058-RFP
calls for new installation of additional detectors, the preferred detector setbacks
shall be determined by the time this task completes.
Test of Performance Plan shall be drafted and submitted for the Agency review
and approval.
DELIVERABLE: Report of the findings of the field survey, and draft Test of
Performance Plan. Recommended setbacks for additional advance detectors.
Recommended phase sequences to be employed in adaptive (if change of
existing sequence is in order).
2.4.2.3 Deploy New Virtual Machine on City of Phoenix TransSuite® Servers
TransCore shall deploy an additional virtual machine on the existing City of
Phoenix TransSuite server. This virtual machine shall host the ACDSS server
for the Project Area 4 ASCT. The virtual machine shall be configured as
described in Section 1.2.2.1 of this proposal.
DELIVERABLE: New virtual machine configured as ACDSS Server for Project
Area 4.
2.4.2.4 Configure and Install New Phoenix TransSuite® Build
TransCore shall configure and install a new Phoenix specific TransSuite build
updating their existing software to the latest available release. This version of
TransSuite shall have the ACDSS interface enabled allowing integration with
the new ACDSS server.
DELIVERABLE: Updated City of Phoenix TransSuite software.
2.4.2.5 Configure and Install New ADOT TransSuite® Build
TransCore shall configure and install a new ADOT specific TransSuite build
updating their existing software to the latest available release. This version of
TransSuite shall have the ACDSS interface enabled allowing integration with
the new ACDSS server.
DELIVERABLE: Updated City of ADOT TransSuite software.
2.4.2.6 Install ACDSS Software on a Central Server
ACDSS software shall be installed on the new virtual machine procure in
Section 2.4.2.3 above. Relevant TransSuite TCS credentials shall be set up to
allow the adaptive control system to retrieve detector data, controller status data,
and perform adaptive control.
The communication between ACDSS adaptive control module and TransSuite
TCS shall be tested and validated.
DELIVERABLE: Installed ACDSS software on the server. Login credentials of
ACDSS software.
2.4.2.7 Verify (Existing and/or New) Detection and Set Up Data Feeds, Examine
Detection Data Accuracy and Quality
Depending on the Detection Scenario selected and operational goals set by the
Agency, this task involves testing and validating the data stream of existing
detectors via the TransSuite Adaptive Control Web Service interface. If it is
decided by the Agency to have additional detectors installed, this task shall also
verify that those new detectors (as configured as system detectors) can report the

15058-RFP
required volume and occupancy data at 30-sec intervals, and the data are
accurate and reliable to meet adaptive control requirement.
DELIVERABLE: Report documenting the results, conclusions and suggestions.
Suggestions to the additional detectors (if decided) regarding improvement on
their data quality and accuracy if needed.
2.4.2.8 Update Existing Controllers
TransCore shall update the 6 existing City of Phoenix ASC2S controllers. As
part of the Project Area 4 ASCT TransCore shall procure 6 new Econolite ASC3
controllers. Existing controller databases shall be converted from ASC2S to
ASC3. TransCore has assumed City staff shall undertake the actual controller
swap in the field.
In addition all seven of the project Area 4 controllers (including ADOT) shall be
equipped with data keys enabling the ACS Lite objects required for ACDSS.
This update shall consist of the installation of a data key at each controller
location. TransCore shall coordinate with City and ADOT staff to accomplish
these updates.
Controller firmware shall be tested to verify the needed adaptive control object
has been correctly implemented to allow the adaptive control operations by
ACDSS from a central system. Controller actions in response to pedestrian calls
and vehicle calls are examined and tested with the presentence of adaptive
control objects.
DELIVERABLE: Six new Econolite ASC3 controllers for City of Phoenix
locations. These controllers shall include translated ASC2S databases.
DELIVERABLE: Data keys to enable ACS Lite objects on 7 City of Phoenix and
ADOT Econolite controllers.
DELIVERABLE: Report documenting the testing results, conclusions and
suggestions. Suggestions to fine tune certain actuated parameters to fit adaptive
control operations when necessary.
2.4.2.9 Configure ACDSS
In this task, ACDSS shall be configured for operating adaptive signals on 7
intersections. The configuration shall be based on the determined Detection
Scenario, the operational priority, and control objectives/goals as determined
from the project staging task.
I-17@Bell Rd is operated by ADOT, while the rest of intersections by the City
of Phoenix. In this task, ACDSS is configured to be able to perform adaptive
control communicating with two separate central TransSuite ATMS. Systematic
coordination between the 7 signals shall be handled by one single ACDSS
adaptive server communicating with two TransSuite centrals. This can be
accomplished by treating I-17@Bell Rd as an isolated Diamond Interchange
Adaptive Control, and the rest of the arterial as arterial adaptive control.
Alternatively, the entire system can be treated as one single arterial system with
designated critical intersections. The actual configuration shall be based on the
outcome of Task 1, upon discussion with the Agency.
DELIVERABLE: Configured ACDSS, and a report documenting the
configuration.

15058-RFP
2.4.2.10 System go-live
In this task, ACDSS adaptive control shall be turned on in two steps. The first
step is the “One-Way” burn-in, i.e., ACDSS receives all the needed real-time
detector data and controller status data, performs signal optimizations and
determines optimized timings, and logs all computation and data, without
actually transmitting the new timing to the field controllers. This step is for
double checking that the system configuration, the communication, and the
optimization process are as designed. After verification of the first step, the
system shall be turned on as “Two-Way” operation, with field controllers being
fully controlled by ACDSS live and 7/24.
DELIVERABLE: Report documenting the go-live process, and the live system.
2.4.2.11 System Fine Tuning
In this task, ACDSS shall be fine-tuned to adjust relevant parameters to further
improve the adaptive operation. For example, queue balancing might be turned
on and off, with different priorities adjusted for different turning movements at
the diamond interchange. This task may involve iterative discussions with the
Agency on the operational objectives and policy guidelines when needed, after
examining the impacted traffic flow conditions under adaptive.
DELIVERABLE: Report documenting the fine tuning process, and a fine-tuned
live system.
2.4.2.12 Training
In this task, training is provided based on the items as stipulated in the
requirement matrix, covering system operations, trouble shooting, configuration,
administration and calibration. The training shall be presented at the designated
locations for the designated staff of the Agency. Printed course materials and
references, electronic copies of presentations and references shall be provided.
The total number of training sessions and total hours are as stipulated in
the Matrix.
DELIVERABLE: Training in the format as defined in the Requirement Matrix and
relevant materials.
2.4.2.13 90-Day Test of Performance
In this task, a 90-day performance test is performed. The system shall be
monitored and support shall be provided to the Agency to assist the performance
test and acceptance. Successful completion of the 90-day performance test
marks final acceptance of the Project Area 4 ASCT for the City of Phoenix and
ADOT.
DELIVERABLE: Technical and maintenance support during this 90-day period.
Any corrective actions needed to improve the system operations.
2.4.2.14 Final deployment report
A final deployment report shall be provided documenting the system
deployment. Project goals and objectives will be discussed at the project Kick
Off Meeting. The final report will include these goals and objectives and how
they have been met.
DELIVERABLE: Final report for this deployment.

15058-RFP
2.4.2.15 Warranty and Support
TransCore shall provide one year of warranty and support for the Project Area 4
ASCT. This warranty and support period is being provided in accordance with
Section 3.7 of the RFP and Section 16 of the Project Area 4 Requirements
Matrix. The one-year warranty and support period shall commence upon the
completion 90-day performance test as described in Section 2.4.2.13 above.
TransCore has provided optional pricing for ongoing maintenance and support
of the ACDSS system for years 2-5. Maintenance and support of the deployed
City of Phoenix and ADOT TransSuite systems shall be handled under the
existing maintenance agreements with the Agencies.
DELIVERABLE: One year warranty and support.
DELIVERABLE: Optional ongoing maintenance and support for years 2-5.

15058-RFP
3 PROJECT SCHEDULE
TransCore is proposing the following schedule for the Bell Rd ASCT Project Area 3 and Area 4
deployments. The schedules for each Project Area run concurrently and are expected to be complete
approximately 8 months after Notice-to-Proceed.
For Project Area 3, City of Scottsdale IT shall be engaged at Notice-to-Proceed to facilitate procurement of
the required virtual machine. It is suggested that Scottsdale IT representatives attend the Project Area 3
Kick-off Meeting.
TransCore is assuming timely review on all updated controllers and databases in Project Area 4, allowing
us to maintain this aggressive schedule.
Enabling of ACS Lite objects is required on all Project Area 3 and Area 4 controllers. Data keys shall be
provided to the representative agencies allowing testing for any unsafe operation.
This schedule shall be reviewed at each Project Area Kick-off meeting. Adjustments to the schedule shall
be discussed at that time to incorporate any other existing agency projects that may impact the ASCT
Deployment.

Maricopa County Solicitation 15058-RFP for Bell Rd Adaptive Signal Control Technology (ASCT) Deployment

SERIAL 15058-RFP
4 DELIVERABLES
4.1 Project Area 3 Deliverables
The following deliverables shall be provided for Project Area 3 of the Bell Rd ASCT Deployment.
These deliverables are further discussed in Section 2.3.2 of this proposal.
 DELIVERABLE: Report documenting the project staging decisions, the operational goals and
control objectives as stipulated (expected) by the Agency and policy guidelines.
 DELIVERABLE: Report of the findings of the field survey, and draft Test of Performance Plan.
Recommended setbacks for additional advance detectors. Recommended phase sequences to
be employed in adaptive (if change of existing sequence is in order).
 DELIVERABLE: New virtual machine configured as ACDSS Server for Project Area 3.
 DELIVERABLE: Updated City of Scottsdale TransSuite software.
 DELIVERABLE: Installed ACDSS software on the server. Login credentials of ACDSS
software.
 DELIVERABLE: Report documenting the results, conclusions and suggestions. Suggestions to
the additional detectors (if decided) regarding improvement on their data quality and accuracy
if needed.
 DELIVERABLE: Data keys to enable ACS Lite objects on 10 existing City of Scottsdale
Econolite ASC3 controllers
 DELIVERABLE: Report documenting the testing results, conclusions and suggestions.
Suggestions to fine tune certain actuated parameters to fit adaptive control operations when
necessary.
 DELIVERABLE: Configured ACDSS, and a report documenting the configuration.
 DELIVERABLE: Report documenting the go-live process, and the live system.
 DELIVERABLE: Report documenting the fine tuning process, and a fine-tuned live system.
 DELIVERABLE: Training in the format as defined in the Requirement Matrix and relevant
materials.
 DELIVERABLE: Technical and maintenance support during this 90-day period. Any corrective
actions needed to improve the system operations.
 DELIVERABLE: Final report for this deployment.
 DELIVERABLE: One year warranty and support.
 DELIVERABLE: Optional ongoing maintenance and support for years 2-5.
4.2 Project Area 4 Deliverables
The following deliverables shall be provided for Project Area 4 of the Bell Rd ASCT Deployment.
These deliverables are further discussed in Section 2.4.2 of this proposal.

SERIAL 15058-RFP
 DELIVERABLE: Report documenting the project staging decisions, the operational goals and
control objectives as stipulated (expected) by the Agency, and policy guidelines. Treatment
on I-17@Bell Rd (as isolated Diamond Interchange Adaptive Control operation, or as unified
adaptive control).
 DELIVERABLE: Report of the findings of the field survey, and draft Test of Performance Plan.
Recommended setbacks for additional advance detectors. Recommended phase sequences to
be employed in adaptive (if change of existing sequence is in order).
 DELIVERABLE: New virtual machine configured as ACDSS Server for Project Area 4.
 DELIVERABLE: Updated City of Phoenix TransSuite software.
 DELIVERABLE: Updated City of ADOT TransSuite software.
 DELIVERABLE: Installed ACDSS software on the server. Login credentials of ACDSS
software.
 DELIVERABLE: Report documenting the results, conclusions and suggestions. Suggestions to
the additional detectors (if decided) regarding improvement on their data quality and accuracy
if needed.
 DELIVERABLE: Six new Econolite ASC3 controllers for City of Phoenix locations. These
controllers shall include translated ASC2S databases.
 DELIVERABLE: Data keys to enable ACS Lite objects on 7 City of Phoenix and ADOT
Econolite controllers.
 DELIVERABLE: Report documenting the testing results, conclusions and suggestions.
Suggestions to fine tune certain actuated parameters to fit adaptive control operations when
necessary.
 DELIVERABLE: Configured ACDSS, and a report documenting the configuration.
 DELIVERABLE: Report documenting the go-live process, and the live system.

 DELIVERABLE: Report documenting the fine tuning process, and a fine-tuned live system.
 DELIVERABLE: Training in the format as defined in the Requirement Matrix and relevant
materials.
 DELIVERABLE: Technical and maintenance support during this 90-day period. Any corrective
actions needed to improve the system operations.
 DELIVERABLE: Final report for this deployment.
 DELIVERABLE: One year warranty and support.
 DELIVERABLE: Optional ongoing maintenance and support for years 2-5.

SERIAL 15058-RFP
ATTACHMENT C-3
TECHNICAL REQUIREMENTS & RESPONSES
PROJECT AREA 3
Version March 26, 2015 Project Area #3: Frank Lloyd Wright Proposer Response
2.1 Boulevard and Loop 101
from Scottsdale Road through Thompson
Peak Parkway
Sys Reqs Level System Concept of Operations Need Statements Meet Proposer Written Verification
Reference of Requirements from Final FHWA Model Documents, FHWA- Requir Description of How Method
Number Impo HOP-11-027, Appendix B ements Proposed System Fulfills
rtanc (Yes or Requirement
e No)
1 1 Network
Characteristics
1.0-1 5 The ASCT shall control 4.2.0-1 Yes No limitation. TransSuite TransSuite
a minimum of 10 The system operator needs to eventually TCS has been deployed TCS can
signals concurrently adaptively control up to 10 signals from the on systems ranging from show the
Scottsdale TMC at 9191 East San Salvador 50 to 12,000 signals status
Drive, Scottsdale, AZ 85258 and from a intersections. ACDSS in as being
satellite TMC (e.g., at Corp Yard, major event Manhattan performs "adaptive".
center, or local EOC). The exact location of adaptive control at more
the satellite TMC has not been determined than 300 intersections.
at this time.
1.0-2 5 The ASCT shall 4.2.0-2 Yes ACDSS supports signal System
support groups of The system operator needs to be able to groups. The grouping config UI &
signals. adaptively control up to 3 independent can be static, or dynamic TransSuite
groups of signals (Hayden & L101, east of and varying based on a TCS console.
L101, west of L101). user specified time of

SERIAL 15058-RFP
4.2.0-3 day schedule.
The system operator needs to vary the
number of signals in an adaptively controlled
group to accommodate the prevailing traffic
conditions.
1.0-2.0-1 5 The boundaries 4.2.0-2 Yes The boundaries are System
surrounding signal The system operator needs to be able to inputs to the system and configuration
controllers that adaptively control up to 3 independent specified by the user. UI.
operate in a groups of signals (Hayden & L101, east of
coordinated fashion L101, west of L101).
shall be defined by
the user.
1.0-2.0-2 4 The ASCT shall control 4.2.0-2 Yes No limitation. The System
a minimum of 3 The system operator needs to be able to number of groups can be config UI &
groups of signals adaptively control up to 3 independent as many as needed. For actual
groups of signals (Hayden & L101, east of example, ACDSS in operations
L101, west of L101). Manhattan controls 18
signal groups; in Arcadia
4 groups.
1.0-2.0-3 4 The size of a group 4.2.0-3 Yes No limitation. ACDSS can System
shall range from 1 to The system operator needs to vary the set the group size config UI &
10 signals. number of signals in an adaptively controlled ranging from 1 to 10. actual
group to accommodate the prevailing traffic operations
conditions.
1.0-2.0-4 4 Each group shall 4.2.0-2 Yes Each group operates System
operate The system operator needs to be able to independent of each config UI &
independently adaptively control up to 3 independent other. actual
groups of signals (Hayden & L101, east of operations
L101, west of L101).
1.0-2.0-5 4 The boundaries 4.2.0-3 Yes The boundaries of System
surrounding signal The system operator needs to vary the coordinated signals can config UI &
controllers that number of signals in an adaptively controlled be altered by the system actual
operate in a group to accommodate the prevailing traffic based on the configured operations

SERIAL 15058-RFP
coordinated fashion conditions. parameters.
shall be altered by the
system according to
configured
parameters
1.0-2.0- 4 The boundaries Yes Each signal group has a System
5.0-1 surrounding signal TOD schedule, resulting config UI &
controllers that in boundaries of actual
operate in a coordinated signals operations
coordinated fashion being altered on a
shall be altered by the schedule. Multiple
system according to a groups with overlapping
time of day schedule. signals running on
(For example: this different schedule result
may be achieved by in dynamic boundaries.
assigning signals to
different groups or by
combining groups.)
1.0-2.0- 4 The boundaries Yes Boundaries can be System
5.0-2 surrounding signal determined by the config UI &
controllers that ACDSS based on traffic actual
operate in a flow conditions such as operations
coordinated fashion overall demand level
shall be altered by the (light, medium, heavy or
system according to special event), prevalent
traffic conditions. (For directional patterns,
example: this may be critical intersections left
achieved by assigning turns and queueing.
signals to different
groups or by
combining groups.)
1.0-2.0- 5 The boundaries Yes The user can command System
5.0-3 surrounding signal to alter the boundaries. config UI &
controllers that The candidate boundary actual

SERIAL 15058-RFP
operate in a must be pre-specified by operations
coordinated fashion the user.
shall be altered by the
system when
commanded by the
user.
2 2 Type of Operation
2.1 2.1 General
2.1.1 2.1.1 Mode of
Operation
2.1.1.0-2 5 The ASCT shall 4.14.0-1 Yes ACDSS requires NO Actual
operate non- The system operator needs to fall back to special adaptive operations
adaptively when the TOD coordination, as specified by the equipment in field. Only
adaptive control operator, without causing disruption to NTCIP controllers
equipment fails. traffic flow, in the event of equipment, required.
2.1.1.0- 3 The ASCT shall communications and software failure. Yes ACDSS reverts to default System
2.0-1 operate non- TOD, when user- config UI and
adaptively when a specified critical actual ops
user-specified detector fails.
detector fails.
2.1.1.0- 4 The ASCT shall Yes ACDSS reverts to default System
2.0-2 operate non- TOD, when total failed config UI and
adaptively when the detectors of a controller actual ops
number of failed exceeding a user-
detectors connected specified threshold.
to a signal controller
exceeds a user-
defined value.
2.1.1.0- 4 The ASCT shall Yes ACDSS reverts to default System
2.0-3 operate non- TOD, when total failed config UI and
adaptively when the detectors of a group actual ops
number of failed exceeding a threshold.
detectors in a group
exceeds a user-

SERIAL 15058-RFP
defined value.
2.1.1.0- 3 The ASCT shall Yes ACDSS reverts to default System
2.0-4 operate non- TOD when critical config UI and
adaptively when a intersections have COM actual ops
user-defined failure.
communications link
fails.
2.1.1.0-3 5 The ASCT shall 4.7.0-3 Yes The user can turn off an Actual
operate non- The system operator needs to over-ride adaptive signal group operations
adaptively when a adaptive operation. When the system and revert to default
user manually operator is advised of an incident that shall TOD when need as need.
commands the ASCT increase demand, the operator may select an
to cease adaptively appropriate flush plan. The operator shall
controlling a group of schedule an ending time for the event. The
signals. flush plan shall remain in place until either
the scheduled end time passes or the
operator cancels the plan.
2.1.1.0-4 5 The ASCT shall 4.7.0-3 Yes The user can turn off the Actual
operate non- The system operator needs to over-ride adaptive operation for operations
adaptively when a adaptive operation. When the system the entire area when
user manually operator is advised of an incident that shall needed and revert to
commands the ASCT increase demand, the operator may select an default TOD control.
to cease adaptive appropriate flush plan. The operator shall
operation. schedule an ending time for the event. The
flush plan shall remain in place until either
the scheduled end time passes or the
operator cancels the plan.
2.1.1.0-5 4 The ASCT shall 4.7.0-2 Yes ACDSS adaptive System
operate non- The system operator needs to schedule pre- operation can be set to config UI and
adaptively in determined operation by time of day. There run on a time of day, day actual
accordance with a are event centers located at Westworld of of week, date of month, operations.
user-defined time-of- Scottsdale and the TPC golf course. Some or holiday schedule.
day schedule. events occur (e.g., a concert) where its start

SERIAL 15058-RFP
time is scheduled and the end time is
predictable.
4.7.0-3
The system operator needs to over-ride
adaptive operation. When the system
operator is advised of an incident that shall
increase demand, the operator may select an
appropriate flush plan. The operator shall
schedule an ending time for the event. The
flush plan shall remain in place until either
the scheduled end time passes or the
operator cancels the plan.
2.1.1.0-6 3 The ASCT shall 4.17.0-2 Yes External command has Actual
operate non- The system operator needs to react to higher priority and shall operations &
adaptively when commands issued by an external decision override adaptive TransSuite
commanded by an support system or an Integrated Corridor operation. This is TCS console.
external system Management system, commanding the ASCT accomplished by via
process. to initiate a flush plan. This flush plan shall TransSuite TCS Manual
remain in operation until the command from Override function.
the external source is removed.
2.1.1.0-7 4 The ASCT shall alter 4.1.0-1.0-1 Yes ACDSS supports multi- System
the adaptive Maximize the throughput on coordinated regime variable config UI and
operation to achieve routes objective adaptive actual
required objectives in 4.1.0-1.0-3 control. It handles operatoins.
user-specified Distribute green time among competing oversaturated &
conditions. movements at critical intersections to unsaturated traffic
provide an equitable distribution of delays. seamlessly by adjusting
4.1.0-3 cycle, offset and split on

SERIAL 15058-RFP
The system operator needs to change the a cycle-by-cycle basis,
operational strategy (for example, from providing delay
smooth flow to maximizing throughput or minimization, equitable
managing queues) based on changing traffic green time distribution,
conditions. For example, an incident is or queue management
blocking the freeway and traffic is diverting with increasing
onto the arterial. The system shall adaptively demands. ACDSS
respond and the off-ramp shall become the intelligently applies
coordinated phase. Outside peak hours, the differentiated adaptive
diverted traffic may not be so severe that a treatments that better
specific flush plan is required. The ASCT shall address geometric
recognize if an increase in demand is within characteristics for
the level accommodated by the adaptive freeway interchanges,
operation. If so, it shall then allow adaptive arterials, and urban
operation to react to the change in demand. grids. The user can
If the demand is outside this level, the ASCT specify locations to
shall go to appropriate flush plan, and activate queue
continue operating that plan until demand management, while the
drops below the maximum acceptable level. adaptive system can
dynamically
activate/deactivate
designated coordinated
phase for special events.
2.1.1.0- 5 When current 4.1.0-1.0-1 Yes ACDSS can proactively Actual
7.0-1 measured traffic Maximize the throughput on coordinated identify capacity operations.
conditions meet user- routes insufficiency and adjust
specified criteria, the 4.1.0-3 cycle lengths to provide

SERIAL 15058-RFP
ASCT shall alter the The system operator needs to change the the needed extra
state of the signal operational strategy (for example, from capacity for through
controllers, smooth flow to maximizing throughput or movements or critical
maximizing the managing queues) based on changing traffic left turns (so it won't
throughput of the conditions. For example, an incident is spill back blocking thru
coordinated route. blocking the freeway and traffic is diverting lanes causing capacity
onto the arterial. The system shall adaptively drop). It also optimizes
respond and the off-ramp shall become the offsets to maximize
coordinated phase. Outside peak hours, the throughput of the
diverted traffic may not be so severe that a coordinated route
specific flush plan is required. The ASCT shall (mainline direction). In
recognize if an increase in demand is within oversaturated
the level accommodated by the adaptive conditions, ACDSS shall
operation. If so, it shall then allow adaptive seamlessly switch to
operation to react to the change in demand. queue management at
If the demand is outside this level, the ASCT critical intersections to
shall go to appropriate flush plan, and prevent queue spillback
continue operating that plan until demand and system break down.
drops below the maximum acceptable level.
2.1.1.0- 5 When current 4.1.0-1.0-4 Yes Traffic signal Actual
7.0-2 measured traffic The objective of the coordination shall be to optimization is all about operations.
conditions meet user- manage the lengths of queues stored at allocating time or space
specified criteria, the critical locations within the coordinated resource. When traffic
ASCT shall alter the group so that long queues do not block becomes oversaturated
state of signal upstream intersections or otherwise reduce with cycle failures and
controllers, the capacity available during the green significant queueing,
preventing queues phases. This shall involve controlling phase ACDSS switches to
from exceeding the lengths so that the size of platoons entering queue management,
storage capacity at a downstream block do not exceed the balancing queue storage
user-specified storage length if the platoon shall be ratio to prevent queue
locations. stopped. It shall also involve control of spillbacks and further
offsets and phase lengths so that queues capacity drops while
may be stored in locations where they shall minimizing gridlock
not adversely affect capacity of the system. potential at selected

SERIAL 15058-RFP
critical locations.
2.1.1.0- 4 When current 4.1.0-1.0-3 Yes Equitable distribution of Actual
7.0-3 measured traffic Distribute green time among competing green time is also known operations.
conditions meet user- movements at critical intersections to as "Webster
specified criteria, the provide an equitable distribution of delays. Philosophy", only
ASCT shall alter the 4.1.0-3 meaningful with
state of signal The system operator needs to change the unsaturated traffic to
controllers providing operational strategy (for example, from minimize average vehicle
equitable distribution smooth flow to maximizing throughput or delay. ACDSS seamless
of green times. managing queues) based on changing traffic handles unsaturated and
conditions. For example, an incident is oversaturated traffic. If
blocking the freeway and traffic is diverting unsaturated, ACDSS shall
onto the arterial. The system shall adaptively apply equitable
respond and the off-ramp shall become the distribution of green
coordinated phase. Outside peak hours, the times (actually, v/c ratio,
diverted traffic may not be so severe that a or equivalently but
specific flush plan is required. The ASCT shall termed otherwise, phase
recognize if an increase in demand is within saturation ratio) among
the level accommodated by the adaptive conflicting movements.
operation. If so, it shall then allow adaptive
operation to react to the change in demand.
If the demand is outside this level, the ASCT
shall go to appropriate flush plan, and
continue operating that plan until demand
drops below the maximum acceptable level.
2.1.1.0- 4 When current 4.1.0-1.0-2 Yes ACDSS can proactively Actual

SERIAL 15058-RFP
7.0-4 measured traffic Provide smooth flow along coordinated identify the directional operations.
conditions meet user- routes. The operator shall be able to define patterns such as
defined criteria, the for each group of intersections the prevalent East Bound,
ASCT shall alter the appropriate operational objective. For West Bound, or
state of signal example, near a freeway interchange or in a Balanced Patterns. If it is
controllers providing location with heavy turning movements, the determined as Balanced
two-way progression queue management strategy may be Pattern, ACDSS shall
on a coordinated specified, while on an arterial with long alter the signals to
route. signal spacing the smooth flow objective may achieve two-way
be specified. progression on the
4.1.0-3 coordinated route.
The system operator needs to change the
operational strategy (for example, from
smooth flow to maximizing throughput or
managing queues) based on changing traffic
conditions. For example, an incident is
blocking the freeway and traffic is diverting
onto the arterial. The system shall adaptively
respond and the off-ramp shall become the
coordinated phase. Outside peak hours, the
diverted traffic may not be so severe that a
specific flush plan is required. The ASCT shall
recognize if an increase in demand is within
the level accommodated by the adaptive
operation. If so, it shall then allow adaptive
operation to react to the change in demand.
If the demand is outside this level, the ASCT
shall go to appropriate flush plan, and
continue operating that plan until demand
drops below the maximum acceptable level.
2.1.1.0-8 2 The ASCT shall 4.1.0-1.0-3 Yes Each phase has System
provide maximum Phase sequence of lead-lag phases, and the minimum split as input. config UI.
and minimum phase operation of left turn phases twice per cycle, Maximum split time is
times shall be determined by the system. The implicitly determined

SERIAL 15058-RFP
entire corridor may be set by the operator to from other phases min.
2.1.1.0- 2 The ASCT shall operate as one coordinated group, or the Yes Max phase split is System
8.0-1 provide a user- system may have the freedom to operate it determined jointly by config UI.
specified maximum as one group subject to user-specified the minimum splits of
value for each phase criteria, such as similar required cycle lengths phases of the same ring.
at each signal in different parts of the corridor are similar
controller. or the volume of traffic in the peak direction
2.1.1.0- 2 The ASCT shall not exceeds a threshold. Yes ACDSS shall not generate Actual
8.0-1.0-1 provide a phase a phase split longer than operations.
length longer that the the maximum value.
maximum value.
2.1.1.0- 2 The ASCT shall Yes Phase minimum is an System
8.0-2 provide a user- explicit input of ACDSS. config UI and
specified minimum actual ops.
value for each phase
at each signal
controller.
2.1.1.0- 2 The ASCT shall not Yes ACDSS shall not generate Actual
8.0-2.0-1 provide a phase a phase split shorter operations.
length shorter than than the min.
the minimum value.
2.1.1.0-9 4 The ASCT shall detect 4.1.0-4 Yes ACDSS identifies Actual
repeated phases that The system operator needs to detect repeated phases with operations
do not serve all repeated phase failures and control signal residual queues by and system
waiting vehicles. timing to prevent phase failures building up checking if the phase has logs.
(These phase failures queues. The operator in this case is trying to been forced-off (i.e.,
may be inferred, such prevent a routine queue from forming where keep extending till the
as by detecting it shall block another movement in the cycle allocated split time).
repeated max-out.) unnecessarily. The system shall determine
2.1.1.0- 4 The ASCT shall alter the optimal order of phases to provide the Yes When repeated phase Actual

SERIAL 15058-RFP
9.0-1 operations, to best coordination. If the green time required failures are detected, operations
minimize repeated for a left turn phase is longer the time ACDSS shall adjust the and system
phase failures. required to service a queue fully occupying phase split if such logs.
the left turn bay, and the queue would failures are local; or
overflow and block the adjacent lane, the increase cycle length if
operator shall be able to specify the phase to such failures are
operate twice for each occurrence of the determined as
opposing through movement, in order to insufficient intersection
avoid queue overflow. The user shall specify capacity, or perform
a maximum elapsed time between queue management if
successive occurrences of a phase when the the system has become
phase is called. oversaturated.
2.1.1.0-10 5 The ASCT shall 4.1.0-1.0-1 Yes ACDSS shall determine Actual
determine the order Maximize the throughput on coordinated the order of phases at operations
of phases at a user- routes user specified and system
specified intersection. 4.1.0-1.0-2 intersections by a logs.
(The calculation shall Provide smooth flow along coordinated feature called TP
be based on the routes. The operator shall be able to define mapper, which allows
optimization for each group of intersections the phase sequences to be
function.) appropriate operational objective. For optimized based on the
example, near a freeway interchange or in a prevalent traffic
location with heavy turning movements, the patterns.
queue management strategy may be
specified, while on an arterial with long
signal spacing the smooth flow objective may
be specified.
4.1.0-1.0-4
The objective of the coordination shall be to
manage the lengths of queues stored at
critical locations within the coordinated
group so that long queues do not block
upstream intersections or otherwise reduce
the capacity available during the green
phases. This shall involve controlling phase

SERIAL 15058-RFP
lengths so that the size of platoons entering
a downstream block do not exceed the
storage length if the platoon shall be
stopped. It shall also involve control of
offsets and phase lengths so that queues
may be stored in locations where they shall
not adversely affect capacity of the system.
2.1.2 2.1.2 Allowable
Phases
2.1.2.0-1 4 The ASCT shall not 4.9.0-1.0-14 Yes ACDSS does not prevent Actual
prevent Permissive/protected phasing and alternate perm/prot left turn operations
permissive/protected left turn phase sequences. Where leading phases. and system
left turn phase and lagging left turn phases are used, the logs.
operation. system shall determine the optimal phase
2.1.2.0-2 5 The ASCT shall not sequence in order to provide the best Yes ACDSS selects the best Actual
prevent the protected coordination. This would be linked to the phase sequence operations
left turn phase to lead direction of offset, such as providing a (lead/lag combinations) and system
or lag the opposing lagging left turn in the heavy, coordinated based on a prespecified logs.
through phase based direction. If the green time required for a left set of sequence
upon user-specified turn phase is longer the time required to candidates. Phase
conditions. service a queue fully occupying the left turn recycling is only possible
bay, and the queue would overflow and when the conflicting
block the adjacent lane, the operator shall be thru has gapped out and
able to specify the phase to operate twice sufficient time left
per cycle in order to avoid queue overflow. before crossing the
barrier with the
compatible phases.
2.1.2.0-3 4 The ASCT shall 4.9.0-1.0-6 Yes ACDSS prevents skipping Actual
prevent skipping a Prevent one or more phases being skipped a use specified phase by operations
user-specified phase under certain traffic conditions or signal placing a phase min and system
when the user- states. recall for that phase. logs.
specified phase
sequence is
operating.

SERIAL 15058-RFP
2.1.2.0-4 3 The ASCT shall Yes User specified external Actual
prevent skipping a 4.17.0-2 input (a special plan) operations
user-specified phase The system operator needs to react to shall override ACDSS and system
based on the state of commands issued by an external decision adaptive command. This logs.
a user-specified support system or an Integrated Corridor cam accomplished by
external input. Management system, commanding the ASCT using TransSuite TCS
to initiate a flush plan. This flush plan shall Manual Override
remain in operation until the command from functionality.
the external source is removed.
2.1.2.0-5 3 The ASCT shall 4.9.0-1.0-6 Yes This is accomplished by Actual
prevent skipping a Prevent one or more phases being skipped placing min recall to that operations
user-specified phase under certain traffic conditions or signal phase on a time of day and system
according to a time of states. schedule. logs.
day schedule.
2.1.2.0-6 2 The ASCT shall omit a 4.9.0-1.0-5 Yes This is accomplished by Actual
user-specified phase Allow one or more phases to be omitted associating cycle length operations
when the cycle length (disabled) under certain traffic conditions or candidates with phase and system
is below a user- signal states. sequences. logs.
specified value.
2.1.2.0-7 2 The ASCT shall omit a Yes If there is no call, a (non Actual
user-specified phase coordinated) phase shall operations
based on measured be skipped. and system
traffic conditions. logs.
2.1.2.0-8 2 The ASCT shall omit a Yes The use can use Manual Actual
user-specified phase Override functionality operations
based on the state of 4.17.0-2 via TransSuite TCS to and system
a user-specified command a special plan logs.
external input. The system operator needs to react to (that omits a phase). The
commands issued by an external decision special plan shall
support system or an Integrated Corridor override ACDSS adaptive
Management system, commanding the ASCT control commands.
to initiate a flush plan. This flush plan shall
remain in operation until the command from
the external source is removed.

SERIAL 15058-RFP
2.1.2.0-9 2 The ASCT shall omit a 4.9.0-1.0-5 Yes This is accomplished by Actual
user-specified phase Allow one or more phases to be omitted an ACDSS feature called operations
according to a time of (disabled) under certain traffic conditions or TP mapper and associate and system
day schedule signal states. the TP mapper with a logs.
schedule.
2.1.2.0-10 5 The ASCT shall assign 4.9.0-1.0-10 Yes This is configured using Actual
unused time from a different force-off operations
preceding phase that modes (floating force off and system
terminates early to a or fixed force off) at logs.
user-specified phase individual controller
as follows: level to specify whether
the extra green is
returned to next
coordinated phase, or
next phase in the same
ring.
* Next phase; Allow the operator to specify which phase
* Next coordinated receives unused time from a preceding
phase; phase
* User-specified
phase.
2.1.2.0-11 5 The ASCT shall assign Yes Unused green due to Actual
unused time from a preceding phase operations
preceding phase that skipping shall be and system
is skipped to a user- returned to user logs.
specified phase as designated phases
follows: according to the
specified force-off mode
(fixed force off or
floating force off).
* Previous phase;
* Next phase;
* Next coordinated

SERIAL 15058-RFP
phase;
* User-specified
phase.
2.1.2.0-12 5 The ASCT shall have The option to hold the position of Yes The position can be held Actual
the ability to hold the uncoordinated phases within a cycle. by the specified phase operations
position of sequence subject to the and system
uncoordinated phases relevant ring-barrier logs.
within a cycle. structure.
2.1.3 2.1.3 Oversaturation
2.1.3.0-1 5 The ASCT shall detect 4.1.0-1.0-4 Yes ACDSS relies on advance Actual
the presence of The objective of the coordination shall be to detectors to identify operations
queues at pre- manage the lengths of queues stored at queues. Shockwave and system
configured locations. critical locations within the coordinated theory is utilized to logs.
group so that long queues do not block predict queue dynamics
upstream intersections or otherwise reduce and identify existing
the capacity available during the green queue.
phases. This shall involve controlling phase
lengths so that the size of platoons entering
a downstream block do not exceed the
storage length if the platoon shall be
stopped. It shall also involve control of
offsets and phase lengths so that queues
may be stored in locations where they shall
not adversely affect capacity of the system.
2.1.3.0-2 5 When queues are 4.1.0-1.0-5 Yes ACDSS performs queue Actual
detected at user- Manage queues in a manner that minimizes balancing and queue operations
specified locations, the impact of queues on intersection management when and system
the ASCT shall efficiency. Queues often overflow from turn queues are identified at logs.
execute user- bays at the FLW/Hayden and FLW/L101 specified locations.
specified timing intersections during peak periods.
plan/operational
mode.
2.1.3.0-3 5 When queues are 4.1.0-4 Yes ACDSS can apply Actual

SERIAL 15058-RFP
detected at user- The system operator needs to detect diamond interchange operations
specified locations, repeated phase failures and control signal control logic for off and system
the ASCT shall timing to prevent phase failures building up ramps traffic, special logs.
execute user- queues. The operator in this case is trying to phase sequence for
specified adaptive prevent a routine queue from forming where queueing left turns, or
strategy in it shall block another movement in the cycle systematic queue
accordance with unnecessarily. The system shall determine management to handle
requirements 2.1.1.0- the optimal order of phases to provide the queues at specified
2. best coordination. If the green time required locations. Metering a
for a left turn phase is longer the time designated phase is also
required to service a queue fully occupying a candidate strategy for
the left turn bay, and the queue would oversaturated control.
overflow and block the adjacent lane, the
operator shall be able to specify the phase to
operate twice for each occurrence of the
opposing through movement, in order to
avoid queue overflow. The user shall specify
a maximum elapsed time between
successive occurrences of a phase when the
phase is called.
2.1.3.0-4 2 When queues are 4.5.0-4 Yes ACDSS shall possibly Actual
detected at user- The system operator needs to store queues omit a user-specified operations
specified locations, in locations where they can be phase to provide the and system
the ASCT shall omit a accommodated without adversely affecting needed capacity for logs.
user-specified phase adaptive operation. Beyond the coordinated other phases.
at a user-specified system, there is a capacity constraint that
signal controller. regularly results in queuing back into the
2.1.3.0-5 4 The ASCT shall meter system. This reduces the throughput Yes "Metering" is Actual
traffic into user- available during green on the coordinated accomplished by operations
specified bottlenecks movement, and increasing congestion is adjusting offsets and and system
by storing queues at measured within the system. While the splits to create a band logs.
user-specified normal response to increased congestion tapering for on-coming
locations. traffic.

SERIAL 15058-RFP
2.1.3.0-6 4 The ASCT shall store within the system would normally be to Yes Queues are stored at Actual
queues at user- increase cycle length, phase times and other designated locations as a operations
specified locations parameters to increase the capacity for the result of the above and system
relevant movements, when the queuing metering strategy. If the logs.
originates outside the system, this shall not
be the appropriate response. In these detector is an advance
circumstances, it is normally more detector, ACDSS can set
appropriate for the system to reduce the an alarm based on the
throughput into the bottleneck or reduce the estimated queue length
size of platoons, so that the queuing does (which internally is
not block other movements within the derived from the
system. The system shall detect the presence
volume/occupancy time
of this condition or the presence of queues
and take appropriate action to reduce the series).
volume of traffic joining the queue, such as
2.1.3.0-7 4 The ASCT shall reducing green time or omitting phases. Yes Capacity flow at Actual
maintain capacity bottlenecks are operations
flow through user- maintained by jointly and system
specified bottlenecks. applying queue balance logs.
and metering strategy.
2.1.3.0-8 4 When queues are Yes Longer cycle may further Actual
detected at user- deteriorate operations
specified locations, oversaturation. The user and system
the ASCT shall limit can specify a proper and logs.
the cycle length of applicable cycle length
the group to a user- for queue management
specified value. to be used by ACDSS.
2.2 2.2 Sequence-based
Adaptive
Coordination
2.2.0-2 4 The ASCT shall select 4.1.0-1.0-1 Yes ACDSS supports Actual
cycle length based on Maximize the throughput on coordinated selecting cycle length operations
a time of day routes based on a time of day and system
schedule. 4.1.0-1.0-2 schedule. Depending on logs.

SERIAL 15058-RFP
Provide smooth flow along coordinated the schedule, applicable
routes. The operator shall be able to define cycle lengths vary.
for each group of intersections the
appropriate operational objective. For
example, near a freeway interchange or in a
location with heavy turning movements, the
queue management strategy may be
specified, while on an arterial with long
signal spacing the smooth flow objective may
be specified.
4.1.0-1.0-3
Distribute green time among competing
movements at critical intersections to
provide an equitable distribution of delays.
4.1.0-1.0-4
The objective of the coordination shall be to
manage the lengths of queues stored at
critical locations within the coordinated
group so that long queues do not block
upstream intersections or otherwise reduce
the capacity available during the green
phases. This shall involve controlling phase
lengths so that the size of platoons entering
a downstream block do not exceed the
storage length if the platoon shall be
stopped. It shall also involve control of
offsets and phase lengths so that queues
may be stored in locations where they shall
not adversely affect capacity of the system.
2.2.0-3 5 The ASCT shall 4.1.0-1.0-3 Yes ACDSS performs cycle, Actual
calculate phase Distribute green time among competing offset and split operations
lengths for all phases movements at critical intersections to optimization. For a given and system
at each signal provide an equitable distribution of delays. cycle, phase splits and logs.
controller to suit the 4.1.0-1.0-5 offset are optimized to

SERIAL 15058-RFP
current coordination Manage queues in a manner that minimizes provide the needed
strategy. the impact of queues on intersection bandwidth and
efficiency. Queues often overflow from turn progression for the
bays at the FLW/Hayden and FLW/L101 current directional
intersections during peak periods. pattern (e.g., EB, WB or
4.1.0-4 Balanced).
The system operator needs to detect
repeated phase failures and control signal
timing to prevent phase failures building up
queues. The operator in this case is trying to
prevent a routine queue from forming where
it shall block another movement in the cycle
unnecessarily. The system shall determine
the optimal order of phases to provide the
best coordination. If the green time required
for a left turn phase is longer the time
required to service a queue fully occupying
the left turn bay, and the queue would
overflow and block the adjacent lane, the
operator shall be able to specify the phase to
operate twice for each occurrence of the
opposing through movement, in order to
avoid queue overflow. The user shall specify
a maximum elapsed time between
successive occurrences of a phase when the
phase is called.
2.2.0-4 5 The ASCT shall 4.1.0-1.0-1 Yes Offset can be optimized System
calculate offsets to Maximize the throughput on coordinate for progression along the config UI and
suit the current routes coordinated arterial. The actual
coordination strategy 4.1.0-1.0-2 anchor point (reference operations.

SERIAL 15058-RFP
for the user-specified Provide smooth flow along coordinated point) can be user
reference point for routes. The operator shall be able to define specified.
each signal controller for each group of intersections the
along a coordinated appropriate operational objective. For
route within a group. example, near a freeway interchange or in a
location with heavy turning movements, the
queue management strategy may be
specified, while on an arterial with long
signal spacing the smooth flow objective may
be specified.
4.1.0-1.0-4
The objective of the coordination shall be to
manage the lengths of queues stored at
critical locations within the coordinated
group so that long queues do not block
upstream intersections or otherwise reduce
the capacity available during the green
phases. This shall involve controlling phase
lengths so that the size of platoons entering
a downstream block do not exceed the
storage length if the platoon shall be
stopped. It shall also involve control of
offsets and phase lengths so that queues
may be stored in locations where they shall
not adversely affect capacity of the system.
2.2.0-4.0-1 5 The ASCT shall apply 4.1.0-1.0-1 Yes The optimized offset is Actual
offsets for the user- Maximize the throughput on coordinate implemented at each operations
specified reference routes signal controller along and system
point of each signal 4.1.0-1.0-2 the coordinated route. logs.
controller along a Provide smooth flow along coordinated
coordinated route. routes. The operator shall be able to define
for each group of intersections the
appropriate operational objective. For
example, near a freeway interchange or in a

SERIAL 15058-RFP
location with heavy turning movements, the
queue management strategy may be
specified, while on an arterial with long
signal spacing the smooth flow objective may
be specified.
4.1.0-1.0-4
The objective of the coordination shall be to
manage the lengths of queues stored at
critical locations within the coordinated
group so that long queues do not block
upstream intersections or otherwise reduce
the capacity available during the green
phases. This shall involve controlling phase
lengths so that the size of platoons entering
a downstream block do not exceed the
storage length if the platoon shall be
stopped. It shall also involve control of
offsets and phase lengths so that queues
may be stored in locations where they shall
not adversely affect capacity of the system.
2.2.0-5 5 The ASCT shall 4.1.0-1.0-1 Yes. ACDSS optimizes cycle Actual
calculate a cycle Maximize the throughput on coordinate based on the objective. operations
length for each cycle routes When a new cycle is and system
based on its 4.1.0-1.0-2 implemented, the entire logs.
optimization Provide smooth flow along coordinated system shall hold on that
objectives (as routes. The operator shall be able to define cycle (Pattern On Hold)
required elsewhere, for each group of intersections the for a user specified
e.g., progression, appropriate operational objective. For period, e.g., 10 minutes.
queue management, example, near a freeway interchange or in a The system shall be
equitable distribution location with heavy turning movements, the snappier to increase
of green). queue management strategy may be from shorter cycle to
specified, while on an arterial with long longer cycle (for
signal spacing the smooth flow objective may example, 90-sec to 135
be specified. sec cycle), but shall drop

SERIAL 15058-RFP
cycle length slowly (e.g.,
from 135 to 120, then
90) with decreasing
demand.
2.2.0-5.0-1 4 The ASCT shall limit 4.1.0-1.0-3 Yes The user can specify the System
cycle lengths to user- Distribute green time among competing set of candidate cycle config UI and
specified values. movements at critical intersections to lengths. actual
provide an equitable distribution of delays. operations.
2.2.0-5.0-2 5 The ASCT shall limit 4.1.0-1.0-4 Yes The user can specify the System
cycle lengths to a range of candidate cycle config UI and
user-specified range. lengths. actual ops
2.2.0-5.0-3 5 The ASCT shall The objective of the coordination shall be to Yes Cycle lengths are
calculate optimum manage the lengths of queues stored at determined based on
cycle lengths critical locations within the coordinated the objective and
according to the user- group so that long queues do not block whether queue
specified coordination upstream intersections or otherwise reduce management is activated
strategy. the capacity available during the green or not.
2.2.0-5.0-4 4 The ASCT shall limit phases. This shall involve controlling phase Yes The user can limit the System
changes in cycle lengths so that the size of platoons entering changes (delta) in cycle config UI and
length to a user- a downstream block do not exceed the length. actual ops
specified value. storage length if the platoon shall be
2.2.0-5.0- 3 The ASCT shall stopped. It shall also involve control of No This is not supported as
4.0-1 increase the limit for offsets and phase lengths so that queues part of ACDSS logic.
the following 3 cycles may be stored in locations where they shall
based on a change in not adversely affect capacity of the system.
conditions
2.2.0-5.0- 3 The change in No This is not supported as
4.0-1.0-1 conditions shall be part of ACDSS logic.
defined by 3
successive adaptive
increases in cycle
length at the
maximum rate.

SERIAL 15058-RFP
2.2.0-5.0- 3 The increase shall be No This is not supported as
4.0-1.0-2 user-defined. part of ACDSS logic.
2.2.0-5.0-5 4 The ASCT shall adjust 4.1.0-5 Yes Offsets are adjusted for Actual
offsets to minimize The system operator needs to minimize the an intended progression operations.
the chance of chance that a queue forms at a specified pattern of primary
stopping vehicles location. platoons, while
approaching a signal facilitating secondary
that have been platoon.
served by a user-
specified phase at an
upstream signal.
2.3 2.3 Non-sequence-
based adaptive
coordination
2.3.0-2 4 The ASCT shall 4.1.0-1.0-1 Yes Signal state of critical Actual
calculate the Maximize the throughput on coordinate intersections are operations.
appropriate state of routes optimized on a cyclic
the signal at the 4.1.0-1.0-2 basis. ACDSS adjust
critical signal Provide smooth flow along coordinated cycle, offset and splits
controller. (A critical routes. The operator shall be able to define maintaining
signal controller is for each group of intersections the coordination using
defined by the user.) appropriate operational objective. For common cycles and
example, near a freeway interchange or in a offsets.
location with heavy turning movements, the
queue management strategy may be
specified, while on an arterial with long
signal spacing the smooth flow objective may
be specified.
2.3.0-3 4 At non-critical 4.1.0-1.0-3 No ACDSS is a cyclic system.
intersections within a Distribute green time among competing Acyclic operations are
group, the ASCT shall movements at critical intersections to not supported.
calculate the time at provide an equitable distribution of delays.
which a user-specified 4.1.0-1.0-4
phase shall be green,

SERIAL 15058-RFP
relative to a reference
point at the critical
intersection, to suit
the current
coordination strategy.
2.3.0-4 3 When demand is The objective of the coordination shall be to No ACDSS is a cyclic system.
present, the ASCT manage the lengths of queues stored at Acyclic operations are
shall implement a critical locations within the coordinated not supported.
user-specified group so that long queues do not block
maximum time upstream intersections or otherwise reduce
between successive the capacity available during the green
displays of each phases. This shall involve controlling phase
phase at each lengths so that the size of platoons entering
intersection. a downstream block do not exceed the
storage length if the platoon shall be
stopped. It shall also involve control of
offsets and phase lengths so that queues
may be stored in locations where they shall
not adversely affect capacity of the system.
2.3.0-5 4 The ASCT shall adjust 4.1.0-5 Yes The signal timing can be Actual
signal timing so that The system operator needs to minimize the adjusted on a cycle by operations.
vehicles approaching chance that a queue forms at a specified cycle basis to facilitate
a signal that have location. progression of second
been served during a and primary platoons.
user-specified phase
at an upstream signal
do not stop.
2.4 2.4 Single NOT USED
intersection adaptive
operation
2.5 2.5 Phase-based NOT USED
adaptive
coordination
2.6 2.6 Responsiveness

SERIAL 15058-RFP
2.6.0-3 3 The ASCT shall limit 4.8.0-2 Yes The optimization Actual
the changes in the The system operator needs to constrain the frequency can be up to operations.
direction of primary selection of cycle lengths to those that every 1 cycle.
coordination to a provide acceptable operations. During peak
user-specified periods when one or more intersections are
frequency. oversaturated, the primary objective of the
system shall be to maximize the throughput
along the corridor in the peak direction. The
cycle length chosen by the system shall be
the maximum permitted by the operator, or
determined by a user-specified maximum
duration between successively servicing a
phase with demand present. The system
shall determine the direction with peak flow
and provide the maximum bandwidth
possible within the selected cycle length.
This shall be subject to user-specified
constraints, such as allowable phase
sequences, and minimum and maximum
phase times.
2.6.0-4 4 When a large change 4.8.0-3 Yes The fastest response Actual
in traffic demand is The system operator needs to respond would be next local zero operations.
detected, the ASCT quickly to sudden large shifts in traffic with new cycle length,
shall respond more conditions. offset and/or splits.
quickly than normal
operation, subject to
user-specified limits.
2.6.0-5 3 The ASCT shall select 4.8.0-2 Yes The user can specify the System

SERIAL 15058-RFP
cycle length from a The system operator needs to constrain the list of candidate cycle config UI and
list of user-defined selection of cycle lengths to those that lengths. actual
cycle lengths. provide acceptable operations. During peak operations.
periods when one or more intersections are
oversaturated, the primary objective of the
system shall be to maximize the throughput
along the corridor in the peak direction. The
cycle length chosen by the system shall be
the maximum permitted by the operator, or
determined by a user-specified maximum
duration between successively servicing a
phase with demand present. The system
shall determine the direction with peak flow
and provide the maximum bandwidth
possible within the selected cycle length.
This shall be subject to user-specified
constraints, such as allowable phase
sequences, and minimum and maximum
phase times.
3 3 External/Internal
Interfaces
3.0-1 The ASCT shall
support external
interfaces according
to the MAG Regional
ITS Architecture and
the following detailed
requirements.
Interface
requirements include:
3 · Information layer 4.3.0-1 Yes ACDSS is TransSuite TCS Actual
protocol adaptive module. This is operations.
The system operator needs to adaptively implemented at
control signals operated by the City of TransSuite level.

SERIAL 15058-RFP
Scottsdale.
3 · Application layer 4.3.0-2 Yes ACDSS is TransSuite TCS Actual
protocol adaptive module. This is operations.
The system operator needs to send data to implemented at
another system that would allow the other TransSuite level.
system to coordinate with the ASCT system.
2 · Lower layer protocol 4.3.0-4 Yes ACDSS is TransSuite TCS Actual
adaptive module. This is operations.
The system operator needs to receive data implemented at
from another system that shall allow the TransSuite level.
ASCT system to coordinate its operation with
the adjacent system.
3 · Data aggregation 4.11.0-5 Yes ACDSS is TransSuite TCS Actual
adaptive module. This is operations.
The system operator needs to report implemented at
performance data in real time to the TransSuite level.
Regional Archive Data Server (RADS).
3 · Frequency of 4.17.0-2 Yes ACDSS is TransSuite TCS Actual
storage adaptive module. This is operations.
3 · Frequency of The system operator needs to react to implemented at
reporting commands issued by an external decision TransSuite level.
3 · Duration of storage) support system or an Integrated Corridor Yes ACDSS is TransSuite TCS Actual
Management system, commanding the ASCT adaptive module. This is operations.
to initiate a flush plan. This flush plan shall implemented at
remain in operation until the command from TransSuite level.
the external source is removed.
3.0-1.0-1 4 The ASCT shall send 4.3.0-2 Yes ACDSS is integrated Actual
operational data to The system operator needs to send data to adaptive control module operations;
the TranSuite and another system that would allow the other of TransSuite. All TransSuite
Regional Archive Data system to coordinate with the ASCT system. operational data are TCS console
Server (RADS) 4.11.0-5 sent to TransSuite.
external system. The system operator needs to report TransSuite sends
performance data in real time to the controller status and
detector data to ACDSS,

SERIAL 15058-RFP
Regional Archive Data Server (RADS). and ACDSS returns
optimized signal timing
back to TransSuite.
TransSuite then
downloads the
optimized timing in field
controllers via NTCIP.
3.0-1.0-3 4 The ASCT shall send 4.11.0-1 Yes ACDSS is part of Actual
monitoring data to The agency needs the (specify external TransSuite. ACDSS operations;
the TranSuite system. decision support system) to be able to archives all monitoring TransSuite
monitor the ASCT system automatically. data in dedicated TCS
database. console/ACD
SS DB.
3.0-1.0-4 4 The ASCT shall send 4.3.0-2 Yes ACDSS as an adaptive Actual
coordination data to The system operator needs to send data to control module controls operations;
the TranSuite system. another system that would allow the other signals through TransSuite
system to coordinate with the ASCT system. TransSuite. All data and TCS console.
control are via
TransSuite.
3.0-1.0-5 4 The ASCT shall send 4.11.0-5 No ACDSS logs all the
performance data to The system operator needs to report performance data in its
the TranSuite and performance data in real time to the own database. ACDSS
Regional Archive Data Regional Archive Data Server (RADS). logs the following direct
Server (RADS) data:
external system. - detector
volume/occupancy
- cycle, offset and splits
- intermediate
calculations log
3.0-1.0-6 4 The ASCT shall receive 4.17.0-2 Yes As TransSuite adaptive Actual
commands from the The system operator needs to react to module, ACDSS receives operations.
TranSuite system. commands issued by an external decision commands via adaptive
support system or an Integrated Corridor control web service

SERIAL 15058-RFP
Management system, commanding the ASCT interface.
3.0-1.0-7 The ASCT shall to initiate a flush plan. This flush plan shall Yes As TransSuite module, Actual
implement the remain in operation until the command from ACDSS support all these. operations.
following commands the external source is removed.
from the TranSuite
system when
commanded:
4 · Specified cycle
length
4 · Specified direction
of progression
4 · Specified adaptive
strategy
4 4 Crossing Arterials
and Boundaries
4.0-1 4 The ASCT shall 4.3.0-4 Yes TransSuite can perform Actual
conform its operation The system operator needs to receive data "Manual Override" to operations.
to an external from another system that shall allow the issue commands to an
system's operation. ASCT system to coordinate its operation with adaptive signal
the adjacent system. overriding ACDSS
4.17.0-2 decisions.
The system operator needs to react to
commands issued by an external decision
support system or an Integrated Corridor
Management system, commanding the ASCT
to initiate a flush plan. This flush plan shall
remain in operation until the command from
the external source is removed.
4.0-1.0-1 4 The ASCT shall alter 4.3.0-4 Yes ACDSS can apply Actual
its operation to The system operator needs to receive data gating/metering operations.
minimize interruption from another system that shall allow the strategies to smooth the
of traffic entering the ASCT system to coordinate its operation with traffic entering the
system. (This may be the adjacent system. system.
achieved via

SERIAL 15058-RFP
detection, with no
direct connection to
the other system)
4.0-1.0-2 3 The ASCT shall be 4.3.0-5 Yes At selected locations, Actual
based on a fixed cycle The system operator needs to constrain the the cycle length can be operations.
length to match an adaptive system to operate a cycle length "locked" to match
adjacent system. compatible with the crossing arterial. adjacent systems.
4.0-1.0-3 4 The ASCT shall alter 4.3.0-4 Yes ACDSS can adjust signals Actual
its operation based The system operator needs to receive data based on detection data operations.
on data received from from another system that shall allow the from another system.
another system. ASCT system to coordinate its operation with
the adjacent system.
4.0-1.0-4 3 The ASCT shall 4.3.0-3 Yes This is handled by ACDSS Actual
support adaptive The system operator needs to adaptively grid network control operations.
coordination on coordinate signals on two crossing routes logic.
crossing routes. simultaneously.
5 5 Access and Security
5.0-1 The ASCT shall be 4.4.0-1
implemented with a
security policy that
addresses the
following selected
elements:
5.0-1.0-1 4 Local access to the The system operator needs to have a Yes This is supported via Actual
ASCT. security management and administrative TransSuite operations
5.0-1.0-2 4 Remote access to the system that allows access and operational Yes This is supported via Actual
ASCT. privileges to be assigned, monitored and TransSuite operations
5.0-1.0-3 4 System monitoring. controlled by an administrator, and conform Yes This is supported via Actual
to the agency's access and network TransSuite operations
5.0-1.0-4 4 System manual infrastructure security policies. Yes This is supported via Actual
override. TransSuite operations
5.0-1.0-5 4 Development Yes This is supported via Actual
TransSuite operations

SERIAL 15058-RFP
5.0-1.0-6 4 Operations Yes This is supported via Actual
TransSuite operations
5.0-1.0-7 4 User login Yes This is supported via Actual
TransSuite operations
5.0-1.0-8 4 User password Yes This is supported via Actual
TransSuite operations
5.0-1.0-9 4 Administration of the Yes This is supported via Actual
system TransSuite operations
5.0-1.0-10 4 Signal controller Yes This is supported via Actual
group access TransSuite operations
5.0-1.0-11 4 Access to classes of Yes This is supported via Actual
equipment TransSuite operations
5.0-1.0-12 4 Access to equipment Yes This is supported via Actual
by jurisdiction TransSuite operations
5.0-1.0-13 4 Output activation Yes This is supported via Actual
TransSuite operations
5.0-1.0-14 4 System parameters Yes This is supported via Actual
TransSuite operations
5.0-1.0-15 4 Report generation Yes This is supported via Actual
TransSuite operations
5.0-1.0-16 4 Configuration Yes This is supported via Actual
TransSuite operations
5.0-1.0-17 4 Security alerts Yes This is supported via Actual
TransSuite operations
5.0-1.0-18 4 Security logging Yes This is supported via Actual
TransSuite operations
5.0-1.0-19 4 Security reporting Yes This is supported via Actual
TransSuite operations
5.0-1.0-20 4 Database Yes This is supported via Actual
TransSuite operations
5.0-1.0-21 4 Signal controller Yes This is supported via Actual
TransSuite operations

SERIAL 15058-RFP
5.0-2 The ASCT shall
provide monitoring
and control access at
the following
locations:
5.0-2.0-1 5 Agency TMC 4.10.0-1.0-1 Yes ACDSS shall be running Actual
Scottsdale TMC at 9191 East San Salvador from a virtual server at operations
Drive, Scottsdale, AZ 85258 the TMC
5.0-2.0-5 4 Local controller 4.10.0-1.0-5 Yes This is via TransSuite TCS Actual
cabinets Local controller cabinets operations
5.0-3 4 The ASCT shall 4.4.0-1 Yes As TransSuite module, Actual
comply with the The system operator needs to have a this is transparently operations
agency's security security management and administrative handled by TransSuite
policy. system that allows access and operational TCS.
privileges to be assigned, monitored and
controlled by an administrator, and conform
to the agency's access and network
infrastructure security policies.
5.0-4 5 The ASCT shall not 4.10.0-2 Yes ACDSS does not prevent Actual
prevent access to the The operator needs to access to the any of these. operations
local signal controller database management, monitoring and
database, monitoring reporting features and functions of the signal
or reporting functions controllers and any related signal
by any installed signal management system from the access points
management system. defined for those system components.
6 6 Data Log
6.0-1 The ASCT shall log the 4.11.0-6 Yes This is managed by TransSuite
following events: The system operator needs to be able to TransSuite TCS TCS console
6.0-1.0-1 4 Time-stamped vehicle report the exact state of signal timing and No This function is not TransSuite
phase calls input data for a specified period, to allow currently supported by TCS console
historical analysis of the system operation. TransSuite TCS. The
The agency needs to maintain a complete capability can be added
record of the actions and performance of the if needed.

SERIAL 15058-RFP
6.0-1.0-2 4 Time-stamped adaptive system. This shall allow staff to No This function is not TransSuite
pedestrian phase calls monitor the effectiveness of the system, and currently supported by TCS console
also respond to requests for information and TransSuite TCS. The
review the operation when complaints are capability can be added
received. The system shall maintain a if needed.
6.0-1.0-3 4 Time-stamped complete record of all its calculations, Yes This is managed by TransSuite
emergency vehicle changes of output state, inputs received TransSuite TCS TCS console
preemption calls from other systems and commands to local
6.0-1.0-6 4 Time-stamped start signal controllers. All calculations that are Yes ACDSS logs this type of ACDSS DB
and end of each affected by calibration parameters (including data.
phase the results of intermediate calculations that
6.0-1.0-7 4 Time-stamped are inputs to optimization routines and Yes ACDSS logs this type of ACDSS DB
controller interval selection tables) shall be reported, to data.
changes facilitate set-up, fine tuning and trouble-
6.0-1.0-8 4 Time-stamped start shooting. The log shall include a record of all Yes ACDSS logs this type of ACDSS DB
and end of each inputs received from external sources, and data.
transition to a new all external outputs generated by the system.
timing plan It shall also record the actual values of all
parameters that are subject to a user-
specified maximum, minimum or range.
6.0-2 4 The ASCT shall export 4.11.0-4 System log export in Actual
its systems log in the Excel or CSV format operation.
following formats: supported.
* MS Excel The system operator needs to store all Yes
* CSV operational data and signal timing
6.0-3 3 The ASCT shall store parameters calculated by the adaptive Yes Event logs are archived ACDSS DB
the event log for a system, and export selected data to from 1 month to
minimum of 14 days TranSuite. The log shall be maintained on- permanent
line in a format able to be queried by a user,
for a user specified period. The log shall be
able to be exported in .csv or MS Excel
format for further analysis. The log shall be
able to be archived in .csv or MS Excel
format.

SERIAL 15058-RFP
6.0-4 3 The ASCT shall store 4.11.0-2 Yes Calculations are archived ACDSS DB
results of all signal The system operator needs to store and from 1 month to
timing parameter report data used to calculate signal timing permanent
calculations for a and have the data available for subsequent
minimum of 14 days. analysis.
4.11.0-3
The system operator needs to store and
report data that can be used to measure
traffic performance under adaptive control.
6.0-5 4 The system shall store 4.11.0-2 Yes ACDSS archives volume ACDSS DB
the following and occupancy data.
measured data in the Queue length data are
form used as input to not direct measurement
calculations for a but estimate
minimum of 14 days:
* Volume The system operator needs to store and based on volume and
report data used to calculate signal timing occupancy data.
and have the data available for subsequent
analysis.
* Occupancy 4.11.0-3
* Queue length The system operator needs to store and
report data that can be used to measure
traffic performance under adaptive control.
4.11.0-7
Have the ability to generate historic and real-
time reports that effectively support
operation, maintenance and reporting of
system performance and traffic conditions.
6.0-6 3 The ASCT system shall 4.11.0-4 Yes. ACDSS archives all the ACDSS
archive all data The system operator needs to store all data minimum 1 month. DB/TransSuit
automatically after a operational data and signal timing e TCS
user-specified period parameters calculated by the adaptive
not less than 14 days.

SERIAL 15058-RFP
6.0-7 4 The ASCT shall system, and export selected data to Yes All these data are ACDSS
provide data storage TranSuite. The log shall be maintained on- archived for a minimum DB/TransSuit
for a system size of 10 line in a format able to be queried by a user, 1 month time. e TCS
signal controllers. The for a user specified period. The log shall be
data to be stored able to be exported in .csv format for further
shall include the analysis. The log shall be able to be archived
following: in .csv format.
* Controller state
data
* Reports
* Log data
* Security data
* ASCT parameters
6.0-8 4 The ASCT shall 4.11.0-7 Yes ACDSS shall generate ACDSS
calculate and report report on the required distiller and
relative data quality items. dashboard
including:
* The extent data is Have the ability to generate historic and real-
affected by detector time reports that effectively support
faults operation, maintenance and reporting of
* Other applicable system performance and traffic conditions.
items
6.0-9 4 The ASCT shall report Yes This functionality is TransSuite
comparisons of provided through TCS Console
logged data when TransSuite TCS console.
requested by the
user:
* Day to day
* Hour to hour
* Hour of day to hour
of day
* Hour of week to
hour of week

SERIAL 15058-RFP
* day of week to day
week
* Day of year to day
of year
6.0-10 4 The ASCT shall store 4.11.0-4 Yes All data are stored in TransSuite
data logs in a The system operator needs to store all SQL-2003 compatible TCS/ACDSS
standard database. operational data and signal timing standard database. DB
parameters calculated by the adaptive
system, and export selected data to
TranSuite. The log shall be maintained on-
line in a format able to be queried by a user,
for a user specified period. The log shall be
able to be exported in .csv format for further
analysis. The log shall be able to be archived
in .csv format.
6.0-11 3 The ASCT shall report 4.11.0-7 Yes The data are reported by ACDSS
stored data in a form Have the ability to generate historic and real- a dashboard and can be Dashboard
suitable to provide time reports that effectively support exported as separate
explanations of operation, maintenance and reporting of files.
system behavior to system performance and traffic conditions.
public and politicians
and to troubleshoot
the system.
7 7 Advanced
Controller Operation
7.0-1 3 When specified by 4.9.0-1.0-1 Yes This is configured at the Actual
the user, the ASCT Service a phase more than once per cycle controller level to enable operation.
shall display a vehicle phase reservice.
phase more than
once for each time
the coordinated
phase is served.
7.0-2 4 The ASCT shall 4.9.0-1.0-2 Yes This is configured at the Actual
provide a minimum of Operate at least 8 overlap phases controller level as operations.

SERIAL 15058-RFP
8 phase overlaps. supported by the
controller firmware.
7.0-3 4 The ASCT shall 4.9.0-1.0-3 Yes This is configured at the Actual
accommodate a Operate four rings, eight phases and up to controller level as operations.
minimum of 8 phases four phases per ring supported by the
at each signal controller firmware.
7.0-4 4 The ASCT shall Yes This is configured at the Actual
accommodate a controller level as operations.
minimum of 4 rings at supported by the
each signal. controller firmware.
7.0-5 4 The ASCT shall Yes This is configured at the Actual
accommodate a controller level as operations.
minimum of 4 phases supported by the
per ring controller firmware.
7.0-6 5 The ASCT shall 4.1.0-6 Yes This is configured at the Actual
provide a minimum of The system operator needs to modify the controller level as operations.
16 different user- sequence of phases to support the various supported by the
defined phase operational strategies. controller firmware.
sequences for each
signal.
7.0-6.0-1 5 Each permissible 4.9.0-1.0-4 Yes This is configured at the Actual
phase sequence shall Permit different phase sequences under controller level as operations.
be user-assignable to different traffic conditions supported by the
any signal timing controller firmware.
plan.
7.0-6.0-2 3 Each permissible Yes Permissible phase Actual
phase sequence shall sequence can be set to operations.
be executable by a run on a TOD schedule
time of day schedule.
7.0-6.0-3 3 Each permissible Yes Permissible phase Actual
phase sequence shall sequence can be operations.
be executable based selected based on traffic
on measured traffic conditions.
conditions

SERIAL 15058-RFP
7.0-7 3 The ASCT shall not 4.1.0-6 Yes Phase /overlap is not Actual
prevent a The system operator needs to modify the prevented by time of operations.
phase/overlap output sequence of phases to support the various day.
by time-of-day. operational strategies.
7.0-8 3 The ASCT shall not 4.1.0-6 Yes ACDSS does not prevent Actual
prevent a The system operator needs to modify the phase/overlap based on operations.
phase/overlap output sequence of phases to support the various an external input.
based on an external operational strategies.
input. 4.17.0-2
The system operator needs to react to
commands issued by an external decision
support system or an Integrated Corridor
Management system, commanding the ASCT
to initiate a flush plan. This flush plan shall
remain in operation until the command from
the external source is removed.
7.0-10 3 The ASCT shall have 4.9.0-1.0-12 Yes Early return to green can Actual
the option for a Allow the coordinated phase to terminate be adjusted by selecting operations.
coordinated phase to early under prescribed traffic conditions fixed force-off or floating
be released early force-off.
based on a user-
definable point in the
phase or cycle.
7.0-11 5 The ASCT shall not 4.9.0-1.0-15 Yes FLA is not prevented. Actual
prevent the controller Use flashing yellow arrow to control operations.
from displaying permissive left turns.
flashing yellow arrow
left turn.
7.0-13 2 When adaptive 4.9.0-1.0-16 Yes ACDSS does not prevent Actual
operation is used in Service side streets and pedestrian phases at a controller to run a operations.
conjunction with minor locations more often than at adjacent cycle different from
normal coordination, signals when this can be done without adjacent intersections, if
the ASCT shall not compromising the quality of the configured as such.
prevent a controller

SERIAL 15058-RFP
serving a cycle length coordination. (E.g., double-cycle mid-block
different from the pedestrian crossing signals.)
cycles used at
adjacent
intersections.
7.0-14 5 The ASCT shall 4.9.0-1.0-8 Yes ACDSS can be configured Actual
operate adaptively Accommodate the following custom features to support the required operations.
with coordinated currently used in coordination patterns. This coordination.
turning movement feature shall need to remain available in
phases between fallback operation should the ASCT fail:
FLW/Hayden and Coordinated turning movement phases
FLW/L101. between FLW/Hayden and FLW/L101.
8 8 Pedestrians and
Bicyclists
8.0-1 1 When a pedestrian 4.6.0-5 Yes This requires the Actual
phase is called, the The system operator needs to accommodate controller firmware to operations.
ASCT shall execute early start of walk and exclusive pedestrian support Lead Pedestrian
pedestrian phases phases. Interval (LPI).
before the vehicle
green of the related
vehicle phase.
8.0-2 5 When the pedestrian 4.6.0-2 Yes Pedestrian WK + FLDW Actual
phase is called, the The system operator needs to accommodate has higher priority over operations.
ASCT shall infrequent pedestrian operation while adaptive timing. If
accommodate maintaining adaptive operation. (This is WK+FLDW is longer than
pedestrian crossing appropriate for pedestrian calls that are the current adaptive
times during adaptive common but not so frequent that they drive timing, WK+FLDW shall
operations. the operational needs.) be honored.
4.6.0-3
The system operator needs to incorporate
frequent pedestrian operation into routine
adaptive operation. (This is appropriate
when pedestrians are frequent enough that
they must be assumed to be present every

SERIAL 15058-RFP
cycle or nearly every cycle.)
8.0-5 4 The ASCT shall have 4.6.0-3 Yes Pedestrian phase can Actual
the option for a phase The system operator needs to incorporate start late as long as operations.
to start late, when frequent pedestrian operation into routine there is sufficient time
there is not a adaptive operation. (This is appropriate remaining on the
pedestrian call for when pedestrians are frequent enough that compatible vehicle
that phase, provided they must be assumed to be present every phase. This is subject to
the minimum green cycle or nearly every cycle.) the controller firmware.
time is available.
8.0-6 5 When specified by 4.9.0-1.0-13 Yes Ped recall can be Actual
the user, the ASCT Allow flexible timing of non-coordinated specified on ped phase operations.
shall execute phases (such as late start of a phase) while adjacent to non
pedestrian recall on maintaining coordination coordinated phases.
pedestrian phase
adjacent to
coordinated phases.
8.0-7 5 When specified by 4.6.0-3 Yes Ped recall can be Actual
the user, the ASCT The system operator needs to incorporate specified on ped phase operations.
shall execute frequent pedestrian operation into routine adjacent to non
pedestrian recall on adaptive operation. (This is appropriate coordinated phases.
pedestrian phase when pedestrians are frequent enough that
adjacent to they must be assumed to be present every
coordinated phases. cycle or nearly every cycle.)
8.0-8 5 When pedestrian 4.6.0-3 Yes Pedestrian WK + FLDW Actual
phases are on recall, The system operator needs to incorporate has higher priority over operations.
the ASCT shall frequent pedestrian operation into routine adaptive timing. If
accommodate adaptive operation. (This is appropriate WK+FLDW is longer than
pedestrian timing when pedestrians are frequent enough that the current adaptive
during adaptive they must be assumed to be present every timing, WK+FLDW shall
operation. cycle or nearly every cycle.) be honored.
8.0-9 4 The ASCT shall The system operator needs to incorporate Yes Bicycle crossing times Actual

SERIAL 15058-RFP
accommodate bicycle operation suitable for bicyclists into routine are honored to override operations.
crossing times during adaptive operation. adaptive timing.
adaptive operations. Hayden Road has bike lanes north of Frank
Lloyd Wright Boulevard.
9 9 Special Functions
9.0-1 5 The ASCT shall allow This is an essential part of operation, Yes Special function shall Actial
for Special Functions, especially if adaptive mode fails to handle take precedence over operation;
including Remote traffic. adaptive. Adaptive TransSuite
Stop Time, and operation shall be halted TCS console.
Remote Preemption when special function is
to be activated activated, and recovered
remotely by the TMC if special function is
User during any deactivated.
operation mode. The
system shall readjust
and transition back to
the specified
operation mode once
Special Function is
deactivated.
10 10 Detection
10.0-1 5 The ASCT shall be The ASCT shall be compatible with existing Yes ACDSS support any Actual
compatible with the and furnished detector technologies. detector technology as operation
following detector Furnished detection sensors or detection long as volume and
technologies: equipment shall not be battery operated. occupancy data are
provided.
* Existing standard
loop detectors
* Existing Econolite
Autoscope video
detector technology
* Furnished detection
(shall not be battery
operated)

SERIAL 15058-RFP
11 11 EV Pre-emption
11.0-2 5 The ASCT shall 4.13.0-2 Yes Non-preempted Actual
maintain adaptive The system operator needs to accommodate intersections shall operations
operation at non- emergency vehicle preemption. The City of operate normal adaptive
preempted Scottsdale uses intersection-based operations.
intersections during preemption. The request is received at the
emergency vehicle controller directly from the emergency
preemption. vehicle.
11.0-4 5 The ASCT shall Yes Special function that Actual
operate normally at omits phase or put a operations.
non-preempted signal max recall shall not
controllers when impact normal adaptive
special functions are operation.
engaged by a
preemption event.
(An example of such a
special functions is a
phase omit, a phase
maximum recall or a
fire route.)
11.0-6 5 The ASCT shall return Yes Adaptive operation shall Actual
to normal adaptive be resumed when operations.
operation when preemption is released.
preemption of a
signal controller is
released.
11.0-7 4 The ASCT shall Yes Preemption always has Actual
preempt a user- higher priority than operations.
specified group of adaptive operations.
signal controllers ACDSS supports
when a user-specified preempting signal
preemption is groups.
requested.
11.0.8 4 The ASCT shall not Yes ACDSS doesn't prevent Actual

SERIAL 15058-RFP
prevent the local local actuated mode. operations.
signal controller from
operating in normally
detected limited-
service actuated
mode during
preemption.
12 12 Transit Priority NOT USED
13 13 Failure Events and
Fallback
13.1 13.1 Detector Failure
13.1.0-1 4 The ASCT shall take 4.14.0-1 Yes ACDSS allows to use Actual
user-specified action The system operator needs to fall back to historical data or operations.
in the absence of TOD coordination, as specified by the adjacent detector data
valid detector data operator, without causing disruption to to compensate missing
from one or more traffic flow, in the event of equipment, data.
vehicle detectors communications and software failure.
within a group.
13.1.0-1.0- 3 The ASCT shall release Yes ACDSS shall release Actual
1 control to central adaptive. The system operations.
system control. shall revert to the
default mode, central
system control or local
TOD
13.1.0-1.0- 3 The ASCT shall release Yes ACDSS shall revert to Actual
2 control to local local TOD, if such is set operations.
operations to operate as the default fall back.
under its own time-
of-day schedule.
13.1.0-2 The ASCT shall use Yes
the following
alternate data
sources for
operations in the

SERIAL 15058-RFP
absence of the real-
time data from a
detector:
13.1.0-2.0- 4 * Data from a user- Yes ACDSS can use historical Actual
1 specified alternate data or specified operation.
detector. alternative detectors
* Historical Archived data to compensate the
Data. missing data.
13.1.0-2.0- 4 The ASCT shall switch Yes ACDSS can switch to Actual
3 to the alternate alternate source operation.
source in real time transparently.
without operator
intervention.
13.1.0-3 4 In the event of a 4.12.0-1 Yes Alarm shall be send as Actual
detector failure, the The system operator needs to immediately txt messages or emails. operation.
ASCT shall issue an notify maintenance and operations staff of
alarm to user- alarms and alerts.
specified recipients. 4.12.0-2
(This requirement
The system operator needs to immediately
may be fulfilled by
and automatically pass alarms and alerts to
sending the alarm to
the TranSuite system.
a designated list of
recipients by a
designated means, or
by using an external
maintenance
management system.
13.1.0-4 4 In the event of a 4.12.0-3 Yes Detection failures are log ACDSS DB
failure, the ASCT shall The system operator needs to maintain a in a database.
log details of the complete log of alarms and failure events.
failure in a
permanent log.
13.1.0-5 4 The permanent Yes The log is ACDSS DB
failure log shall be searchable/achievable,

SERIAL 15058-RFP
searchable, and exportable.
archivable, and
exportable.
13.2 13.2 Communications
Failure
13.2-1 4 The ASCT shall 4.14.0-1 Yes In case of COMM failure, Actual
execute user- The system operator needs to fall back to ACDSS can either revert operation
specified actions TOD coordination, as specified by the back to default TOD, or
when operator, without causing disruption to ignore such failure if
communications to traffic flow, in the event of equipment, only split changes are
one or more signal communications and software failure. involved.
controllers fails within
a group.
13.2-1.0-1 3 In the event of loss of Yes COMM failure with a Actual
communication to a critical intersection can operation
user-specified signal cause ACDSS release
controller, the ASCT adaptive and revert back
shall release control to TOD
of all signal
controllers within a
user-specified group
to local control.
13.2-1.0-2 3 The ASCT shall switch Yes The release and revert is Actual
to the alternate transparently handled by operation
operation in real time ACDSS
without operator
intervention.
13.2-2 4 In the event of 4.12.0-1 Yes The TransSuite Alarm Actual
communications The system operator needs to immediately System shall send operation
failure, the ASCT shall notify maintenance and operations staff of alarms.
issue an alarm to alarms and alerts.
user-specified 4.12.0-2

SERIAL 15058-RFP
recipients. (This The system operator needs to immediately
requirement may be and automatically pass alarms and alerts to
fulfilled by sending the existing TranSuite system.
the alarm to a
designated list of
recipients by a
designated means, or
by using an external
maintenance
management system.
13.2-3 4 The ASCT shall issue Yes This is supported. Actual
an alarm within 1 operation
minute of detection
of a failure.
13.2-4 4 In the event of a 4.12.0-3 Yes The failures are logged Actual
communications The system operator needs to maintain a permanently in a DB. operation
failures, the ASCT complete log of alarms and failure events.
shall log details of the
failure in a
permanent log.
13.2-5 4 The permanent Yes The log is in a RDB and Actual
failure log shall be meeting the operation
searchable, requirement.
archivable, and
exportable.
13.3 13.3 Adaptive
Processor Failure
13.3-1 4 The ASCT shall 4.14.0-1 Yes ACDSS has no hardware-
execute user- The system operator needs to fall back to based adaptive
specified actions TOD coordination, as specified by the processor.
when adaptive operator, without causing disruption to
control fails:

SERIAL 15058-RFP
13.3-1.0-1 4 The ASCT shall release traffic flow, in the event of equipment, Yes Adaptive shall be Actual
control to central communications and software failure. released if the central operation
system control. ACDSS server faills. The
system reverts to central
system control if
configured so as fallback.
13.3-1.0-2 3 The ASCT shall release TOD control shall be the Actual
control to local fallback if configured so. operation
operations to operate
under its own time-
of-day schedule.
13.3-2 4 In the event of 4.12.0-1 Yes Alarms by text message Actual
adaptive processor The system operator needs to immediately or by email. operation
failure, the ASCT shall notify maintenance and operations staff of
issue an alarm to alarms and alerts.
user-specified 4.12.0-2
recipients. (This
The system operator needs to immediately
requirement may be
and automatically pass alarms and alerts to
fulfilled by sending
the existing TranSuite system.
the alarm to a
designated list of
recipients by a
designated means, or
by using an external
maintenance
management
system.)
13.3-3 4 The permanent Yes The logged failure is Actual
failure log shall be searchable, achievable, operation
searchable, and exportable.
archivable, and
exportable.
13.3-4 4 During adaptive 4.14.0-1 Yes ACDSS does not Actual

SERIAL 15058-RFP
processor failure, the The system operator needs to fall back to intercept local detector operation
ASCT shall provide all TOD coordination, as specified by the inputs to local controller.
local detector inputs operator, without causing disruption to
to the local controller. traffic flow, in the event of equipment,
communications and software failure.
14 14 Software
14.0-1 4 The vendor's adaptive 4.15.0-2 No ACDSS is a Windows
software shall be fully based software running
operational within on a Windows Server.
the following TransSuite TCS is
platform: Windows/Linux based
software.
* Linux The system operator needs to use
equipment and software acceptable under
current agency IT policies and procedures.
14.0-2 The system shall 4.15.0-1.0-2 Yes ACDSS interface the TransSuite
interface with Detector type: inductive loops, Econolite detectors via TransSuite TCS console
detectors from Autoscope video TCS.
Econolite Autoscope
and standard loop
detectors.
14.0-3 4 The system shall 4.15.0-1.0-1 Yes ASC/3 is supported. Actual
interface with Controller type: Econolite ASC/3 operation
Econolite ASC/3
controllers.
15 15 Training
15.0-1 The vendor shall 4.16.0-1 Yes This is part of our
provide the following The agency needs all staff involved in standard training
training. operation and maintenance to receive package.
15.0-1.0-1 5 The vendor shall appropriate training. Yes This is part of our
provide training on standard training
the operations of the package.
adaptive system.

SERIAL 15058-RFP
15.0-1.0-2 5 The vendor shall Yes This is part of our
provide training on standard training
troubleshooting the package.
system.
15.0-1.0-3 5 The vendor shall Yes This is part of our
provide training on standard training
preventive package.
maintenance and
repair of equipment.
15.0-1.0-4 5 The vendor shall Yes This is part of our
provide training on standard training
system configuration. package.
15.0-1.0-5 5 The vendor shall Yes This is part of our
provide training on standard training
administration of the package.
system.
15.0-1.0-6 5 The vendor shall Yes This is part of our
provide training on standard training
system calibration. package.
15.0-1.0-7 5 The vendor's training Yes This is part of the
delivery shall include: deliverable.
printed course
materials and
references, electronic
copies of
presentations and
references. The
vendor shall provide
training materials
seven days in advance
of each training
session.
15.0-1.0-8 5 The vendor's training Yes The training shall be
shall be delivered at provided at the

SERIAL 15058-RFP
the Scottsdale TMC at designated location.
9191 East San
Salvador Drive,
Scottsdale, AZ 85258.
15.0-1.0-9 5 The vendor shall Yes The training shall be
provide a minimum of provided for the
40 hours training to a designated staff of the
minimum of 5 City City.
personnel after the
system is installed
and fully operational.
15.0-1.0- 4 The vendor shall Yes This is part of our
10 provide a minimum of standard training
2 training sessions, package.
one at the start of the
project and one six
months after
commissioning.
16 16 Maintenance,
Support and
Warranty
16.0-1 5 The Maintenance 4.16.0-2 Yes This is part of our
Vendor shall provide The agency needs the system to fulfill all standard maintenance
maintenance requirements for the life of the system. The and support agreement.
according to a agency therefore needs the system to be Full terms and
separate maintained to repair faults that are not conditions of the
maintenance defects in materials and workmanship. maintenance and
contract. That support contract shall be
contract should negotiated when
identify repairs appropriate.
necessary to preserve
requirements
fulfillment,
responsiveness in

SERIAL 15058-RFP
effecting those
repairs, and all
requirements on the
maintenance provider
while performing the
repairs.
16.0-2 5 The Vendor shall 4.16.0-4 Yes This is part of our
provide routine The agency needs the system to fulfill all standard maintenance
updates to the requirements for the life of the system. The and support agreement.
software and agency therefore needs support to keep Full terms and
software software and software environment updated conditions of the
environment as necessary to prevent requirements no maintenance and
necessary to preserve longer being fulfilled. support contract shall be
the fulfillment of negotiated when
requirements for a appropriate.
period of 1 year from
Final Acceptance.
Preservation of
requirements
fulfillment especially
includes all IT
management
requirements as
previously identified.
16.0-3 5 The Vendor shall 4.16.0-3 Yes Warranty shall be

SERIAL 15058-RFP
warrant the system to The agency needs the system to fulfill all provided as specified.
be free of defects in requirements for the life of the system. The
materials and agency therefore needs the system to
workmanship for a remain free of defects in materials and
period of one year. workmanship that result in requirements no
Warranty is defined longer being fulfilled.
as correcting defects
in materials and
workmanship (subject
to other language
included in the
purchase documents).
Defect is defined as
any circumstance in
which the material
does not perform
according to its
specification. Said
intrument shall
provide for support
with the following
response times:
* Support provided by
telephone - 24 hours
* Support provided
via remote login to
the system - 24 hours
* Support requiring
vendor staff onsite - 3
business days
17 17 Schedule
17.0-1 4 The ASCT shall set the 4.17.0-1 Yes This is accomplished via TransSuite
state of external The TPC Scottsdale Champions Golf Course TransSuite TCS TCS console
input/output states and Westworld of Scottsdale are located

SERIAL 15058-RFP
according to a time- north of the corridor. When an event occurs
of-day schedule. (e.g., the Phoenix Open), its start and end
17.0-2 4 The ASCT output time are not predictable (e.g., events Yes This is accomplished via TransSuite
states shall be throughout the day for several days). The TransSuite TCS TCS console
settable according to agency shall program the system so that at a
a time-of-day scheduled time it begins operation in a mode
schedule that accommodates the arrival of patrons to
17.0-3 4 The ASCT operational the event. The schedule shall allow normal Yes This is accomplished via TransSuite
parameters shall be operation while the event is in progress and TransSuite TCS TCS console
settable according to there is little associated traffic. The schedule
a Time of Day shall also place the system in an appropriate
schedule mode of operation to accommodate patrons
leaving the event. An operator shall be able
to manually implement the appropriate
signal operation during any time of the
event.
18 18 Performance
Measurement,
Monitoring and
Reporting
18.0-1 4 The ASCT shall report 4.11.0-2 Yes ACDSS logs all data and ACDSS DB
measures of current The system operator needs to store and measures of traffic
traffic conditions on report data used to calculate signal timing conditions in the
which it bases signal and have the data available for subsequent database.
state alterations. analysis.
18.0-2 4 The ASCT shall report Yes All intermediate ACDSS DB
all intermediate calculated values are
calculated values that logged.
are affected by
calibration
parameters.
18.0-3 4 The ASCT shall 4.11.0-2 Yes All signal state change ACDSS DB
maintain a log of all The system operator needs to store and (detailed controller
signal state report data used to calculate signal timing status data including

SERIAL 15058-RFP
alterations directed and have the data available for subsequent cycle, offset, and
by the ASCT. analysis. individual splits, cycle
4.11.0-7 start and end time).
Have the ability to generate historic and real- Whether the signal is in
time reports that effectively support transition, and transition
operation, maintenance and reporting of cycles are also logged.
system performance and traffic conditions.
18.0-3.0-1 4 The ASCT log shall 4.11.0-7 No This is not supported
include all events Have the ability to generate historic and real- right now.
directed by the time reports that effectively support
external inputs. operation, maintenance and reporting of
18.0-3.0-2 4 The ASCT log shall system performance and traffic conditions. No This is not supported
include all external right now.
output state changes.
18.0-3.0-3 4 The ASCT log shall Yes All the configurable ACDSS DB
include all actual inputs are logged in the
parameter values that DB
are subject to user-
specified values.
18.0-3.0-4 4 The ASCT shall Yes The log can be kept from ACDSS DB
maintain the records minimum 1 month to
in this ASCT log for a permanent
minimum of 60 days.
18.0-3.0-5 4 The ASCT shall Yes All data can be kept from ACDSS DB
archive all stored data minimum 1 month to
automatically after a permanent
user-specified period
not less than 60 days
and when
commanded by the
user.

SERIAL 15058-RFP
ATTACHMENT C-4
TECHNICAL REQUIREMENTS & RESPONSES
PROJECT AREA 4
Version March 26, 2015 Project Area #4: Bell Road and I-17 Proposer Response
2.1 from 35th Avenue through 19th Avenue
Sys Reqs Level System Requirements Concept of Operations Need Statements Meet Proposer Written Verification
Reference of from Final FHWA Model Documents, Requir Description of How Method
Number Impor FHWA-HOP-11-027, Appendix B ements Proposed System
tance (Yes or Fulfills Requirement
No)
1 1 Network
Characteristics
1.0-1 5 The ASCT shall control 4.2.0-1 Yes No limitation. Demonstration
a minimum of 8 signals The agencies have plans to adaptively TransSuite TCS has
concurrently control a total of 8 intersections from the been deployed on
City of Phoenix TMC located at 200 West systems of 50 to
Washington Street, Phoenix, AZ 85003 and 12,000 intersections.
the ADOT TOC located at 2302 West ACDSS in Manhattan
Durango Street, Phoenix, AZ 85009. controls at more than
300 intersections.
2 2 Type of Operation
2.1 2.1 General
2.1.1 2.1.1 Mode of
Operation
2.1.1.0-2 5 The ASCT shall operate 4.14.0-1 Yes ACDSS requires NO Demonstration
non-adaptively when The system operator needs to fall back to special adaptive
the adaptive control TOD operation without causing disruption equipment in field.
equipment fails. to traffic flow, in the event of equipment, Only NTCIP controllers

SERIAL 15058-RFP
communications and software failure. required.
2.1.1.0- 1 The ASCT shall operate Yes ACDSS reverts to Demonstration
2.0-1 non-adaptively when a default TOD, when
user-specified user-specified critical
detector fails. detector fails.
2.1.1.0- 3 The ASCT shall operate Yes ACDSS reverts to Demonstration
2.0-2 non-adaptively when default TOD, when
the number of failed total failed detectors
detectors connected of a controller
to a signal controller exceeding a user-
exceeds a user-defined specified threshold.
value.
2.1.1.0- 5 The ASCT shall operate Yes ACDSS reverts to Demonstration
2.0-3 non-adaptively when default TOD, when
the number of failed total failed detectors
detectors in a group of a group exceeding a
exceeds a user-defined threshold.
value.
2.1.1.0- 1 The ASCT shall operate Yes ACDSS reverts to Demonstration
2.0-4 non-adaptively when a default TOD when
user-defined critical intersections
communications link have COM failure.
fails.
2.1.1.0-3 5 The ASCT shall operate 4.7.0-3 Yes The user can turn off Demonstration
non-adaptively when a The system operator needs to over-ride an adaptive signal
user manually adaptive operation. When operator is group and revert to
commands the ASCT advised of an incident that shall increase default TOD when
to cease adaptively demand, the operator selects an need as need.
controlling a group of appropriate flush plan. The operator shall
signals. schedule an ending time for the event. The
2.1.1.0-4 5 The ASCT shall operate flush plan shall remain in place until either Yes The user can turn off Demonstration
non-adaptively when a the scheduled end time passes or the the adaptive
user manually operator cancels the plan. operation for the

SERIAL 15058-RFP
commands the ASCT entire area and revert
to cease adaptive to default TOD
operation. control.
2.1.1.0-6 3 The ASCT shall operate 4.17.0-2 Yes External command has Demonstration
non-adaptively when The system operator needs to react to higher priority and
commanded by an commands issued by an external decision shall override adaptive
external system support system or an Integrated Corridor operation. This is
process. Management system, commanding the accomplished by via
ASCT to initate a flush plan. This flush plan TransSuite TCS Manual
shall remain in operation until the Override function
command from the external source is
removed.
2.1.1.0-7 5 The ASCT shall alter 4.1.0-1.0-1 Yes ACDSS supports multi- Demonstration
the adaptive operation Maximize the throughput on coordinated regime variable
to achieve required routes objective control. It
objectives in user- 4.1.0-1.0-3 handles over &
specified conditions. Distribute phase times in an equitable unsaturated traffic
fashion seamlessly adjusting
4.1.0-3 cycle, offset and split
cyclically, providing
The system, or the operator, shall select
delay minimization,
the appropriate coordination objective,
equitable green time
depending on the current traffic
distribution, or queue
conditions. For example, during commuter
management with
peaks the primary objective may be to
increasing demands.
maximize the throughput along the road in
ACDSS applies
the peak direction and at accommodate
differentiated
the turning movements at the freeway
adaptive treatments
interchange. Then during the business
to address geometric
hours the objective may be to balance
characteristics for
delays between traffic associated with the
freeway interchanges,
adjacent activity and traffic simply
arterials, and urban
traveling through the system.
grids. Queue
management can be

SERIAL 15058-RFP
activated at selected
locations. Designated
coordinated phase can
be changed for special
events.
2.1.1.0- 5 When current 4.1.0-1.0-1 Yes ACDSS can proactively Demonstration
7.0-1 measured traffic Maximize the throughput on coordinated identify capacity
conditions meet user- routes insufficiency and
specified criteria, the 4.1.0-3 adjust cycle to provide
ASCT shall alter the The system, or the operator, shall select the needed extra
state of the signal the appropriate coordination objective, capacity for through
controllers, depending on the current traffic movements or critical
maximizing the conditions. For example, during commuter left turns. It also
throughput of the peaks the primary objective may be to optimizes offsets to
coordinated route. maximize the throughput along the road in maximize throughput
the peak direction and at accommodate of the coordinated
the turning movements at the freeway route (mainline
interchange. Then during the business direction). In
hours the objective may be to balance oversaturated
delays between traffic associated with the conditions, ACDSS
adjacent activity and traffic simply shall seamlessly switch
traveling through the system. to queue management
at critical intersections
to prevent queue
spillback and system
break down.
2.1.1.0- 5 When current 4.1.0-1.0-4 Yes For oversaturated Demonstration
7.0-2 measured traffic Manage the lengths of queues traffic with cycle
conditions meet user- failures/queueing,
specified criteria, the ACDSS switches to
ASCT shall alter the queue management,
state of signal balancing queue
controllers, preventing storage ratio to
queues from prevent

SERIAL 15058-RFP
exceeding the storage spillbacks/capacity
capacity at user- drops while
specified locations. minimizing gridlock
potential at critical
locations.
2.1.1.0- 3 When current 4.1.0-1.0-3 Yes Equitable distribution Demonstration
7.0-3 measured traffic Distribute phase times in an equitable of green time is also
conditions meet user- fashion known as "Webster
specified criteria, the 4.1.0-3 Philosophy", only
ASCT shall alter the The system, or the operator, shall select meaningful with
state of signal the appropriate coordination objective, unsaturated traffic to
controllers providing depending on the current traffic minimize average
equitable distribution conditions. For example, during commuter vehicle delay. ACDSS
of green times. peaks the primary objective may be to seamless handles
maximize the throughput along the road in unsaturated and
the peak direction and at accommodate oversaturated traffic.
the turning movements at the freeway If unsaturated, ACDSS
interchange. Then during the business shall apply equitable
hours the objective may be to balance distribution of green
delays between traffic associated with the times (actually, v/c
adjacent activity and traffic simply ratio, or equivalently
traveling through the system. but termed otherwise,
phase saturation ratio)
among conflicting
movements.
2.1.1.0- 3 When current 4.1.0-1.0-2 Yes ACDSS can proactively Demonstration
7.0-4 measured traffic Provide smooth flow along coordinated identify the directional
conditions meet user- routes patterns such as
defined criteria, the 4.1.0-3 EB/WB, or Balanced
ASCT shall alter the The system, or the operator, shall select Patterns. If it is
state of signal the appropriate coordination objective, determined as
controllers providing depending on the current traffic Balanced Pattern,
two-way progression conditions. For example, during commuter ACDSS shall alter the
on a coordinated peaks the primary objective may be to signals to achieve two-

SERIAL 15058-RFP
route. maximize the throughput along the road in way progression on
the peak direction and at accommodate the coordinated route.
2.1.1.0-7 5 The ASCT shall alter the turning movements at the freeway Yes See above Demonstration
the state of the signal interchange. Then during the business
controllers based on hours the objective may be to balance
current measured delays between traffic associated with the
traffic conditions. (The adjacent activity and traffic simply
alteration may be traveling through the system.
made by adjusting
parameters or by
directly controlling the
state of signal
controllers.)
2.1.1.0-8 5 The ASCT shall provide 4.1.0-1.0-3 Yes Each phase has Demonstration
maximum and Distribute phase times in an equitable minimum split as
minimum phase times fashion input. Maximum split
time is implicitly
determined from
other phases min.
2.1.1.0- 5 The ASCT shall provide Yes Max phase split is Demonstration
8.0-1 a user-specified determined jointly by
maximum value for the minimum splits of
each phase at each phases of the same
signal controller. ring.
2.1.1.0- 5 The ASCT shall not Yes ACDSS shall not Demonstration
8.0-1.0-1 provide a phase length generate a phase split
longer that the longer than the
maximum value. maximum value.
2.1.1.0- 5 The ASCT shall provide Yes Phase minimum is an Demonstration
8.0-2 a user-specified explicit input of
minimum value for ACDSS.
each phase at each
signal controller.
2.1.1.0- 5 The ASCT shall not Yes ACDSS shall not Demonstration

SERIAL 15058-RFP
8.0-2.0-1 provide a phase length generate a phase split
shorter than the shorter than the min.
minimum value.
2.1.1.0-9 5 The ASCT shall detect 4.1.0-4 Yes ACDSS identifies Demonstration
repeated phases that At a small group of intersections, with the repeated phases with
do not serve all user defining one as being critical, while residual queues by
waiting vehicles. the adjacent intersections require a lower checking if the phase
(These phase failures cycle length or progression must be has been forced-off
may be inferred, such provided for specific phases to minimize (i.e., keep extending
as by detecting the formation of queues on the till the allocated split
repeated max-out.) approaches to the critical intersection, the time).
2.1.1.0- 5 The ASCT shall alter phase lengths of the critical intersection Yes When repeated phase Demonstration
9.0-1 operations, to shall be determined by the system based failures are detected,
minimize repeated on the current traffic conditions. The ACDSS shall adjust the
phase failures. operation of the adjacent intersections phase split, increase
shall then be set so that platoons cycle, or perform
departing the critical intersection are queue management if
progressed through the non-critical the system has
intersections, or platoons arriving at the become
critical intersection do so at a time when oversaturated.
they shall have little or no delay waiting for
the appropriate phase.
2.1.1.0-10 5 The ASCT shall 4.1.0-1.0-1 Yes ACDSS shall determine Demonstration
determine the order of Maximize the throughput on coordinated the order of phases at
phases at a user- routes user specified
specified intersection. 4.1.0-1.0-2 intersections by a
(The calculation shall Provide smooth flow along coordinated feature called TP
be based on the routes mapper, which allows
optimization function.) 4.1.0-1.0-4 phase sequences to be
optimized based on
Manage the lengths of queues
the prevalent traffic
patterns.
2.1.1.0-11 5 The ASCT shall provide 4.1.0-8 Yes Coordination along a Demonstration

SERIAL 15058-RFP
coordination along a The system operator needs to designate route is specified a
route. the coordinated route based on traffic series of coordinated
conditions and the selected operational phases at each
strategy. relevant signal.
2.1.1.0- 3 The ASCT shall Yes ACDSS provides coord Demonstration
11.0-1 coordinate along a along a user-specified
user-defined route. route.
2.1.1.0- 3 The ASCT shall Yes Coordinated route can Demonstration
11.0-2 determine the Yes be activated based on
coordinated route traffic conditions.
based on traffic
conditions.
2.1.1.0- 5 The ASCT shall Yes Coordinated route can Demonstration
11.0-3 determine the Yes be activated based on
coordinated route user specified
based on a user- schedule.
defined schedule.
2.1.1.0- 5 The ASCT shall store a Yes User defined Demonstration
11.0-4 minimum of 20 user- Yes coordination routes
defined coordination are stored at local
routes. controller db as timing
plan patterns at each
signal.
2.1.1.0- 5 The ASCT shall Yes The operator can Demonstration
11.0-4.0-1 implement a stored Yes command a stored
coordinated route by coordinate route by
operator command. activating a relevant
pattern along the
signals.
2.1.1.0- 4 The ASCT shall Yes ACDSS implements a Demonstration
11.0-4.0-2 implement a stored Yes stored coordinate
coordinated route route by activating a
based on traffic relevant pattern on
conditions. traffic conditions.

SERIAL 15058-RFP
2.1.1.0- 5 The ASCT shall Yes ACDSS implements a Demonstration
11.0-4.0-3 implement a stored Yes stored coordinate
coordinated route route by activating a
based on a user- relevant pattern on a
defined schedule. user specified
schedule.
2.1.1.0-12 5 The ASCT shall not 4.1.0-9 Yes ACDSS doesn't prevent Demonstration
prevent the use of The system operator needs to set signal the agency specified
phase timings in the timing parameters (such as minimum phase timings in local
local controller set by green, maximum green and extension controller.
agency policy. time) to comply with agency policies.
2.1.2 2.1.2 Allowable
Phases
2.1.2.0-1 5 The ASCT shall not 4.9.0-1.0-14 Yes ACDSS does not Demonstration
prevent Protected/permissive phasing and prevent perm/prot left
protected/permissive alternate left turn phase sequences. turn phases.
left turn phase
operation.
2.1.2.0-2 5 The ASCT shall not Yes ACDSS selects the best Demonstration
prevent the protected phase sequence
left turn phase to lead (lead/lag
or lag the opposing combinations) based
through phase based on a prespecified set
upon user-specified of sequence
conditions. candidates.
2.1.2.0-3 5 The ASCT shall prevent 4.9.0-1.0-6 Yes ACDSS prevents Demonstration
skipping a user- The ability to maintain coordination with skipping a use
specified phase when external movements by preventing phases specified phase by
the user-specified from being skipped, or by omitting phases, placing a phase min
phase sequence is based on time-of-day, external input or recall for that phase.
operating. when certain phase sequences are in
2.1.2.0-4 5 The ASCT shall prevent operation. Yes User specified external Demonstration
skipping a user- 4.17.0-2 input (a special plan)

SERIAL 15058-RFP
specified phase based The system operator needs to react to shall override ACDSS
on the state of a user- commands issued by TranSuite and future adaptive command.
specified external decision support system, such as an ICM This cam
input. system. accomplished by using
TransSuite TCS Manual
Override functionality.
2.1.2.0-5 3 The ASCT shall prevent 4.9.0-1.0-6 Yes This is accomplished Demonstration
skipping a user- The ability to maintain coordination with by placing min recall
specified phase external movements by preventing phases to that phase on a
according to a time of from being skipped, or by omitting phases, time of day schedule.
day schedule. based on time-of-day, external input or
when certain phase sequences are in
operation.
2.1.2.0-6 1 The ASCT shall omit a 4.9.0-1.0-5 Yes This is accomplished Demonstration
user-specified phase Allow one or more phases to be omitted by associating cycle
when the cycle length (disabled) under certain traffic conditions length candidates with
is below a user- or signal states to allow a shorter cycle phase sequences.
specified value. length to operate, or to provide additional
time to other phases in the absence of
calls to skipped phase(s).
2.1.2.0-7 5 The ASCT shall omit a Yes If there is no call, a Demonstration
user-specified phase (non coordinated)
based on measured phase shall be
traffic conditions. skipped.
2.1.2.0-8 1 The ASCT shall omit a 4.17.0-2 Yes The use can use Demonstration
user-specified phase The system operator needs to react to Manual Override via
based on the state of a commands issued by TranSuite and future TransSuite TCS to
user-specified external decision support system, such as an ICM command a special
input. system. plan (that omits a
phase). The special
plan shall override
ACDSS adaptive
control commands.

SERIAL 15058-RFP
2.1.2.0-9 3 The ASCT shall omit a 4.9.0-1.0-5 Yes This is accomplished Demonstration
user-specified phase Allow one or more phases to be omitted by an ACDSS feature
according to a time of (disabled) under certain traffic conditions called TP mapper and
day schedule or signal states to allow a shorter cycle associate the TP
length to operate, or to provide additional mapper with a
time to other phases. schedule.
2.1.2.0-10 5 The ASCT shall assign 4.9.0-1.0-10 Yes This is configured Demonstration
unused time from a using different force-
preceding phase that off modes (floating
terminates early to a force off or fixed force
user-specified phase off) at individual
as follows: controller level to
specify whether the
extra green is
returned to next
coordinated phase, or
next phase in the
same ring.
* Next phase; Allow the operator to specify which phase
* Next coordinated receives unused time from a preceding
phase; phase
* User-specified
phase.
2.1.2.0-11 5 The ASCT shall assign Yes Unused green due to Demonstration
unused time from a preceding phase
preceding phase that skipping shall be
is skipped to a user- returned to user
specified phase as designated phases
follows: according to the
specified force-off
mode (fixed force off
or floating force off).
* Previous phase;

SERIAL 15058-RFP
* Next phase;
* Next coordinated
phase;
* User-specified
phase.
2.1.2.0-12 4 The ASCT shall not 4.1.0-7 Yes The position can be Demonstration
alter the order of The system operator needs to fix the held by the specified
phases at a user- sequence of phases at any specified phase sequence
specified intersection location. For example, the operator may subject to the relevant
need to fix the phase order at a diamond ring-barrier structure.
interchange.
2.1.3 2.1.3 Oversaturation
2.1.3.0-1 5 The ASCT shall detect 4.1.0-1.0-4 Yes ACDSS relies on Demonstration
the presence of Manage the lengths of queues advance detectors to
queues at pre- 4.1.0-1.0-5 identify queues.
configured locations, Shockwave theory is
Manage the locations of queues within the
particularly at the I-17 utilized to predict
network
Interchange. queue dynamics and
4.1.0-4
identify existing
At a small group of intersections, with the queue.
user defining one as being critical, while
the adjacent intersections require a lower
cycle length or progression must be
provided for specific phases to minimize
the formation of queues on the
approaches to the critical intersection, the
phase lengths of the critical intersection
shall be determined by the system based
on the current traffic conditions. The
operation of the adjacent intersections
shall then be set so that platoons
departing the critical intersection are
progressed through the non-critical
intersections, or platoons arriving at the

SERIAL 15058-RFP
critical intersection do so at a time when
they shall have little or no delay waiting for
the appropriate phase.
2.1.3.0-2 5 When queues are 4.5.0-1 Yes ACDSS performs Demonstration
detected at user- The system operator needs to detect queue balancing and
specified locations, the queues from outside the system and queue management
ASCT shall execute modify the ASCT operation to when queues are
user-specified timing accommodate the queuing. identified at specified
plan/operational 4.5.0-2 locations.
mode. The system operator needs to detect
queues within the system's boundaries and
modify the ASCT operation to
accommodate the queuing.
4.5.0-3
The system operator needs to detect
queues propagating outside its boundaries
from within the ASCT boundaries, and
modify its operation to accommodate the
queuing.
4.5.0-5
The system operator needs to prevent
queues forming at the Bell Road / I-17
Interchange.
2.1.3.0-3 3 When queues are Yes Strategy (e.g. diamond Demonstration
detected at user- control, left turn
specified locations, the treatment, gating,
ASCT shall execute queue balance) can be
user-specified activated on detected
adaptive strategy queue

SERIAL 15058-RFP
2.1.3.0-4 5 When queues are 4.1.0-1.0-4 Yes ACDSS shall possibly Demonstration
detected at user- Manage the lengths of queues omit a user-specified
specified locations, the 4.1.0-1.0-5 phase to provide the
ASCT shall omit a user- needed capacity for
Manage the locations of queues within the
specified phase at a other phases, or as
network
user-specified signal part of a systematic
4.1.0-4
controller. oversaturated control
At a small group of intersections, with the strategy. ACDSS can
user defining one as being critical, while apply diamond
the adjacent intersections require a lower interchange control
cycle length or progression must be logic for off ramps
provided for specific phases to minimize traffic, special phase
the formation of queues on the sequence for queueing
approaches to the critical intersection, the left turns, or
phase lengths of the critical intersection systematic queue
shall be determined by the system based management to
on the current traffic conditions. The handle queues at
operation of the adjacent intersections specified locations.
shall then be set so that platoons
departing the critical intersection are
progressed through the non-critical
intersections, or platoons arriving at the
critical intersection do so at a time when
they shall have little or no delay waiting for
the appropriate phase.
4.5.0-5
The system operator needs to prevent
queues forming at the Bell Road / I-17
Interchange.
2.2 2.2 Sequence-based
Adaptive
Coordination
2.2.0-2 5 The ASCT shall select 4.1.0-1.0-1 Yes ACDSS supports Demonstration
cycle length based on Maximize the throughput on coordinated selecting cycle length

SERIAL 15058-RFP
a time of day schedule routes based on a time of day
at user-specified signal 4.1.0-1.0-2 schedule. Depending
controllers. Provide smooth flow along coordinated on the schedule,
routes applicable cycle
4.1.0-1.0-3 lengths vary.
Distribute phase times in an equitable
fashion
4.1.0-1.0-4
Manage the lengths of queues
2.2.0-3 5 The ASCT shall 4.1.0-1.0-3 Yes ACDSS performs cycle, Demonstration
calculate phase Distribute phase times in an equitable offset and split
lengths for all phases fashion optimization. For a
at each signal 4.1.0-1.0-5 given cycle, phase
controller to suit the Manage the locations of queues within the splits and offset are
current coordination network optimized to provide
strategy. 4.1.0-4 the needed bandwidth
and progression for
At a small group of intersections, with the
the current directional
user defining one as being critical, while
pattern (e.g., EB, WB
the adjacent intersections require a lower
or Balanced).
cycle length or progression must be
provided for specific phases to minimize
the formation of queues on the
approaches to the critical intersection, the
phase lengths of the critical intersection
shall be determined by the system based
on the current traffic conditions. The
operation of the adjacent intersections
shall then be set so that platoons
departing the critical intersection are
progressed through the non-critical
intersections, or platoons arriving at the
critical intersection do so at a time when
they shall have little or no delay waiting for

SERIAL 15058-RFP
the appropriate phase.
2.2.0-4 5 The ASCT shall 4.1.0-1.0-1 Yes Offset can be Demonstration
calculate offsets to suit Maximize the throughput on coordinate optimized for
the current routes progression along the
coordination strategy 4.1.0-1.0-2 coordinated arterial.
for the user-specified Provide smooth flow along coordinated The anchor point
reference point for routes (reference point) can
each signal controller 4.1.0-1.0-4 be user specified.
along a coordinated
Manage the lengths of queues
route within a group.
2.2.0-4.0-1 5 The ASCT shall apply Yes The optimized offset is Demonstration
offsets for the user- implemented at each
specified reference signal controller along
point of each signal the coordinated route.
controller along a
coordinated route.
2.2.0-5 1 The ASCT shall 4.1.0-1.0-1 Yes For a new cycle, Demonstration
calculate a cycle length Maximize the throughput on coordinate ACDSS shall hold on
for each cycle based routes that cycle for a user
on its optimization 4.1.0-1.0-2 specified period, e.g.,
objectives (as required Provide smooth flow along coordinated 10 min. The system is
elsewhere, e.g., routes snappier to increase
progression, queue from short to long
management, cycle (e.g, 90 to 105),
equitable distribution but shall drop cycle
of green). slowly with decreasing
demand.

SERIAL 15058-RFP
2.2.0-5.0-1 5 The ASCT shall limit 4.1.0-1.0-3 Yes The user can specify Demonstration
cycle lengths to user- Distribute phase times in an equitable the set of candidate
specified values. fashion cycle lengths.
4.1.0-1.0-4
Manage the lengths of queues
2.2.0-5.0-2 3 The ASCT shall limit Yes The user can specify
cycle lengths to a user- the range of candidate
specified range. cycle lengths.
2.2.0-5.0-3 1 The ASCT shall Yes Cycle lengths are Demonstration
calculate optimum determined based on
cycle lengths according the objective and
to the user-specified whether queue
coordination strategy. management is
activated or not.
2.2.0-5.0-4 5 The ASCT shall limit Yes The user can limit the Demonstration
changes in cycle length changes (delta) in
to a user-specified cycle length.
value.
2.2.0-5.0- 4 The ASCT shall No This is not supported
4.0-1 increase the limit for as part of ACDSS logic.
the following 1 cycle
based on a change in
conditions
2.2.0-5.0- 4 The change in No This is not supported
4.0-1.0-1 conditions shall be as part of ACDSS logic.
defined by 2
successive adaptive
increases in cycle
length at the
maximum rate.
2.2.0-5.0- 5 The increase shall be No This is not supported Demonstration
4.0-1.0-2 user-defined. as part of ACDSS logic.
2.2.0-5.0-5 4 The ASCT shall adjust 4.1.0-5 Yes Offset s are adjusted Demonstration

SERIAL 15058-RFP
offsets to minimize the The system operator needs to minimize for an intended
chance of stopping the chance that a queue forms at a progression pattern
vehicles approaching a specified location. for primary platoons
signal that have been while facilitating
served by a user- secondary platoons.
specified phase at an
upstream signal.
2.3 2.3 Non-sequence- NOT USED
based adaptive
coordination
2.4 2.4 Single intersection NOT USED
adaptive operation
2.5 2.5 Phase-based NOT USED
adaptive coordination
2.6 2.6 Responsiveness
2.6.0-1 3 The ASCT shall limit 4.8.0-1 No The cycle is bounded
the change in The system operator needs to modify the by the range and
consecutive cycle ASCT operation to closely follow changes candidate values,
lengths to be less than in traffic conditions. though, there is no
a user-specified value. user specified limit of
the delta.
2.6.0-2 3 The ASCT shall limit No The phase duration is
the change in phase bounded by the min
times between and max, there is no
consecutive cycles to user specified limit on
be less than a user- the delta.
specified value. (This
does not apply to early
gap-out or actuated
phase skipping.)
2.6.0-3 5 The ASCT shall limit Yes The optimization Demonstration
the changes in the frequency can be up
direction of primary 4.8.0-2 to every 1 cycle.

SERIAL 15058-RFP
coordination to a user- The system operator needs to constrain
specified frequency. the selection of cycle lengths to those that
provide acceptable operations, such as
when resonant progression solutions are
desired.
2.6.0-4 5 When a large change 4.8.0-3 Yes The fastest response Demonstration
in traffic demand is The system operator needs to respond would be next local
detected, the ASCT quickly to sudden large shifts in traffic zero with new cycle
shall respond more conditions. length, offset and/or
quickly than normal splits.
operation, subject to
user-specified limits.
2.6.0-5 5 The ASCT shall select 4.8.0-2 Yes The user can specify Demonstration
cycle length from a list The system operator needs to constrain the list of candidate
of user-defined cycle the selection of cycle lengths to those that cycle lengths.
lengths at user- provide acceptable operations, such as
specified locations. when resonant progression solutions are
desired.
3 3 External/Internal
Interfaces
3.0-1 The ASCT shall support
external interfaces
according to the
referenced interface
control documents
and the following
detailed requirements.
Interface
requirements include:
5 · Information layer 4.3.0-1 ACDSS is TransSuite Demonstration
protocol TCS adaptive module.
This is implemented at
TransSuite level.
The system operator needs to adaptively Yes

SERIAL 15058-RFP
control signals operated by the City of
Phoenix and ADOT.
5 · Application layer 4.3.0-2 Yes ACDSS is TransSuite Demonstration
protocol TCS adaptive module.
This is implemented at
TransSuite level.
The system operator needs to send data to
another system that would allow the other
system to coordinate with the ASCT
system.
5 · Lower layer protocol 4.3.0-4 ACDSS is TransSuite Demonstration
TCS adaptive module.
This is implemented at
TransSuite level.
The system operator needs to receive data Yes
from another system that shall allow the
ASCT system to coordinate its operation
with the adjacent system.
5 · Data aggregation 4.11.0-5 Demonstration
The system operator needs to report Yes ACDSS is TransSuite
performance data in real time to TranSuite TCS adaptive module.
and Regional Archived Data System This is implemented at
(RADS). TransSuite level.
5 · Frequency of storage 4.17.0-2 ACDSS is TransSuite Demonstration
TCS adaptive module.
This is implemented at
TransSuite level.
5 · Frequency of The system operator needs to react to
reporting commands issued by TranSuite and future
5 · Duration of storage decision support system, such as an ICM Yes
system.
3.0-1.0-1 5 The ASCT shall send 4.3.0-2 Yes ACDSS is integrated Demonstration

SERIAL 15058-RFP
operational data to The system operator needs to send data to adaptive control
TranSuite and Regional another system that would allow the other module of TransSuite.
Archived Data System system to coordinate with the ASCT All operational data
(RADS). system. are sent to TransSuite.
4.11.0-5 TransSuite sends
The system operator needs to report controller status and
performance data in real time to TranSuite detector data to
and Regional Archived Data System ACDSS, and ACDSS
(RADS). returns optimized
signal timing back to
TransSuite. TransSuite
then downloads the
optimized timing in
field controllers via
NTCIP.
3.0-1.0-2 5 The ASCT shall send 4.3.0-2 Yes ACDSS is TransSuite Demonstration
control data to The system operator needs to send data to TCS adaptive module.
TranSuite. another system that would allow the other All control data is sent
system to coordinate with the ASCT to TransSuite and
system. implemented by the
latter.
3.0-1.0-3 5 The ASCT shall send 4.11.0-1 Yes ACDSS is part of Demonstration
monitoring data to The agency needs TranSuite to be able to TransSuite. ACDSS
TranSuite. monitor the ASCT system automatically. archives all monitoring
data in dedicated
database.
3.0-1.0-4 5 The ASCT shall send 4.3.0-2 Yes ACDSS as an adaptive Demonstration
coordination data to The system operator needs to send data to control module
TranSuite. another system that would allow the other controls signals
system to coordinate with the ASCT through TransSuite. All
system. data and control are
via TransSuite.
3.0-1.0-5 5 The ASCT shall send 4.11.0-5 No ACDSS logs all the Demonstration

SERIAL 15058-RFP
performance data to The system operator needs to report performance data in
TranSuite and Regional performance data in real time to TranSuite its own database
Archived Data System and Regional Archived Data System
(RADS). (RADS).
3.0-1.0-6 5 The ASCT shall receive 4.17.0-2 Yes As TransSuite adaptive Demonstration
commands from The system operator needs to react to module, ACDSS
TranSuite or a future commands issued by TranSuite and future receives commands
decision support decision support system, such as an ICM via adaptive control
system, such as an ICM system. web service interface.
system.
3.0-1.0-7 5 The ASCT shall 4.17.0-2 Yes As TransSuite module, Demonstration
implement the ACDSS support all
following commands these.
from the TranSuite
external system when
commanded:
· Specified cycle length The system operator needs to react to
· Specified direction of commands issued by TranSuite and future
progression decision support system, such as an ICM
· Specified adaptive system.
strategy
4 4 Crossing Arterials
and Boundaries
4.0-1 5 The ASCT shall 4.3.0-4 Yes TransSuite can Demonstration
conform its operation The system operator needs to receive data perform "Manual
to an external system's from another system that shall allow the Override" to issue
operation. ASCT system to coordinate its operation commands to an
with the adjacent system. adaptive signal
4.3.0-6 overriding ACDSS
The system operator needs to detect decisions.
traffic approaching from a neighboring
system and coordinate the ASCT operation
with the adjacent system. The agency

SERIAL 15058-RFP
needs the adaptive system to maintain
coordination with another adjacent system
by sensing arriving traffic.
4.17.0-2
The system operator needs to react to
commands issued by TranSuite and future
decision support system, such as an ICM
system.
4.0-1.0-1 5 The ASCT shall alter its 4.3.0-4 Yes ACDSS can apply Demonstration
operation to minimize The system operator needs to receive data gating/metering
interruption of traffic from another system that shall allow the strategies to smooth
entering the system. ASCT system to coordinate its operation the traffic entering the
(This may be achieved with the adjacent system. system.
via detection, with no 4.3.0-6
direct connection to The system operator needs to detect
the other system) traffic approaching from a neighboring
system and coordinate the ASCT operation
with the adjacent system. The agency
needs the adaptive system to maintain
coordination with another adjacent system
by sensing arriving traffic.
4.0-1.0-2 5 The ASCT shall be 4.3.0-5 Yes At selected locations, Demonstration
based on a fixed cycle The system operator needs to constrain the cycle length can be
length to match an the adaptive system to operate a cycle "locked" to match
adjacent system at length compatible with the crossing adjacent systems.
user-specified arterial. The agency needs the adaptive
intersections. system to maintain coordination with
another adjacent system by using
constraints on cycle length.
4.0-1.0-3 3 The ASCT shall alter its 4.3.0-4 Yes ACDSS can adjust Demonstration
operation based on The system shall accept data from a signals based on
data received from neighboring system that allows it to stay in detection data from
another system. coordination with the adjacent system another system.

SERIAL 15058-RFP
while still operating in adaptive mode.
4.0-1.0-4 2 The ASCT shall support 4.3.0-3 Yes This is handled by Demonstration
adaptive coordination The system operator needs to adaptively ACDSS grid network
on crossing routes. coordinate signals on two crossing routes control logic.
simultaneously. A coordinated group shall
be able to include more than one
coordinated route, such as two crossing
arterials. The system shall be able to
maintain coordination along both roads.
The crossing arterials in this area are 19th
Avenue and 35th Avenue.
5 5 Access and Security
5.0-1 The ASCT shall be 4.4.0-1
implemented with a The system operator needs to have a
security policy that security management and administrative
addresses the system that allows access and operational
following selected privileges to be assigned, monitored and
elements: controlled by an administrator, and
conform to the agency's access and
network infrastructure security policies.
5.0-1.0-1 5 Local access to the External to the controller cabinet, Yes This is supported via Demonstration
ASCT. information flowing in or out shall be TransSuite
encrypted
5.0-1.0-2 5 Remote access to the Yes This is supported via Demonstration
ASCT. TransSuite
5.0-1.0-3 5 System monitoring. Yes This is supported via Demonstration
TransSuite
5.0-1.0-4 5 System manual Yes This is supported via Demonstration
override. TransSuite
5.0-1.0-5 5 Development Yes This is supported via Demonstration
TransSuite
5.0-1.0-6 5 Operations Yes This is supported via Demonstration

SERIAL 15058-RFP
TransSuite
5.0-1.0-7 5 User login Yes This is supported via Demonstration
TransSuite
5.0-1.0-8 5 User password Yes This is supported via Demonstration
TransSuite
5.0-1.0-9 5 Administration of the Yes This is supported via Demonstration
system TransSuite
5.0-1.0-10 5 Signal controller group Yes This is supported via Demonstration
access TransSuite
5.0-1.0-11 5 Access to classes of Yes This is supported via Demonstration
equipment TransSuite
5.0-1.0-12 5 Access to equipment Yes This is supported via Demonstration
by jurisdiction TransSuite
5.0-1.0-13 5 Output activation Yes This is supported via Demonstration
TransSuite
5.0-1.0-14 5 System parameters Yes This is supported via Demonstration
TransSuite
5.0-1.0-15 5 Report generation Yes This is supported via Demonstration
TransSuite
5.0-1.0-16 5 Configuration Yes This is supported via Demonstration
TransSuite
5.0-1.0-17 5 Security alerts Yes This is supported via Demonstration
TransSuite
5.0-1.0-18 5 Security logging Yes This is supported via Demonstration
TransSuite
5.0-1.0-19 5 Security reporting Yes This is supported via Demonstration
TransSuite
5.0-1.0-20 5 Database Yes This is supported via Demonstration
TransSuite
5.0-1.0-21 5 Signal controller Yes This is supported via Demonstration
TransSuite
5.0-2 The ASCT shall provide
monitoring and
control access at the

SERIAL 15058-RFP
following locations:
5.0-2.0-1 5 City of Phoenix TMC 4.10.0-1.0-1 Yes ACDSS shall be Demonstration
located at 200 West Agency TMC running from a central
Washington Street, server at the TMC.
Phoenix, AZ 85003 Monitoring and
control access are via
remote desktop.
5.0-2.0-2 5 User-specified 4.10.0-1.0-2 Yes ACDSS shall be Demonstration
locations Maintenance facility running from a central
server at the TMC.
Monitoring and
control access are via
remote desktop.
5.0-2.0-3 5 Workstations on 4.10.0-1.0-3 Yes ACDSS shall be Demonstration
agency LAN or WAN Workstations on agency LAN or WAN running from a central
located at City of server at the TMC.
Phoenix traffic signal Monitoring and
shop located at 2141 E control access are via
Jefferson St, Phoenix, remote desktop.
AZ 85009
5.0-2.0-4 5 ADOT TOC located at 4.10.0-1.0-4 Yes ACDSS shall be Demonstration
2302 West Durango Other agency's TMC running from a central
Street, Phoenix, AZ server at the TMC.
85009 Monitoring and
control access are via
remote desktop.
5.0-2.0-5 5 Local controller 4.10.0-1.0-5 Yes This is via TransSuite Demonstration
cabinets Local controller cabinets TCS
5.0-3 5 The ASCT shall comply 4.4.0-1 Yes As TransSuite module, Demonstration

SERIAL 15058-RFP
with the agency's The system operator needs to have a this is transparently
security policy as security management and administrative handled by TransSuite
described in City of system that allows access and operational TCS.
Phoenix IT Standards. privileges to be assigned, monitored and
controlled by an administrator, and
conform to the agency's access and
network infrastructure security policies.
The adaptive processor/server shall be
protected within the agency's firewalls.
The IT Department shall provide resources,
equipment and system management so
that operators shall have appropriate
access to the system locally, from within
the agency's LAN and from remote
locations.
5.0-4 5 The ASCT shall not 4.10.0-2 Demonstration
prevent access to the The operator needs to access to the
local signal controller database management, monitoring and
database, monitoring reporting features and functions of the
or reporting functions signal controllers and any related signal
by any installed signal management system from the access
management system. points defined for those system
components.
6 6 Data Log
6.0-1 The ASCT shall log the 4.11.0-6
following events: The system operator needs to be able to
report the exact state of signal timing and
6.0-1.0-1 5 Time-stamped vehicle input data for a specified period, to allow Yes This is managed by Demonstration
phase calls historical analysis of the system operation. TransSuite TCS
6.0-1.0-2 5 Time-stamped Yes This is managed by Demonstration
pedestrian phase calls TransSuite TCS
6.0-1.0-3 5 Time-stamped Yes This is managed by Demonstration

SERIAL 15058-RFP
emergency vehicle TransSuite TCS
preemption calls
6.0-1.0-6 5 Time-stamped start Yes ACDSS logs this type of Demonstration
and end of each phase data.
6.0-1.0-7 5 Time-stamped Yes ACDSS logs this type of Demonstration
controller interval data.
changes
6.0-1.0-8 5 Time-stamped start Yes ACDSS logs this type of Demonstration
and end of each data.
transition to a new
timing plan
6.0-2 5 The ASCT shall export 4.11.0-4 Yes System log export in Demonstration
its systems log in the Excel, Text or CSV
following formats: format supported.
* MS Excel The system operator needs to store all
* Text operational data and signal timing
* CSV parameters calculated by the adaptive
system, and export selected data to a City
6.0-3 5 The ASCT shall store of Phoenix TMC server using remote Yes Event logs are Demonstration
the event log for a access from TMC. archived from 1
minimum of 31 days. month to permanent
6.0-4 5 The ASCT shall store 4.11.0-2 Yes Calculations are Demonstration
results of all signal The system operator needs to store and archived from 1
timing parameter report data used to calculate signal timing month to permanent
calculations for a and have the data available for subsequent
minimum of 31 days. analysis.
4.11.0-3
The system operator needs to store and
report data that can be used to measure
traffic performance under adaptive
control.
6.0-5 5 The system shall store 4.11.0-2 No This is not fully Demonstration
the following supported by current
measured data in the version of ACDSS but

SERIAL 15058-RFP
form used as input to the following shall be
calculations for a supported in the next
minimum of 31 days: release by
* Volume by The system operator needs to store and by the end of Q1,
movement report data used to calculate signal timing 2016.
and have the data available for subsequent
analysis.
* Occupancy 4.11.0-3
* Queue length The system operator needs to store and Currently support
* Wait time / delay on report data that can be used to measure Volume, Occupancy
side streets traffic performance under adaptive and Queue Length
* % Arrivals on Green / control. (estimated)
Red 4.11.0-7
* Phase Failure Have the ability to generate historic and
* Green Utilization real-time reports that effectively support
* Time in Transition operation, maintenance and reporting of
* V/C Ratio system performance and traffic conditions.
6.0-6 1 The ASCT system shall 4.11.0-4 Yes ACDSS archives all the Demonstration
archive all data The system operator needs to store all data minimum 1
automatically after a operational data and signal timing month.
user-specified period parameters calculated by the adaptive
not less than 31 days. system, and export selected data to a City
6.0-7 5 The ASCT shall provide of Phoenix TMC server using remote All these data are Demonstration
data storage for a access from TMC. archived for a
system size of 8 signal minimum 1 month
controllers. The data time.
to be stored shall
include the following:
* Controller state data
* Reports
* Log data
* Security data

SERIAL 15058-RFP
* ASCT parameters
6.0-8 5 The ASCT shall 4.11.0-7 Yes ACDSS/TransSuite TCS Demonstration
calculate and report shall generate report
relative data quality on the required items.
including:
* The extent data is Have the ability to generate historic and
affected by detector real-time reports that effectively support
faults operation, maintenance and reporting of
* Communication system performance and traffic conditions.
faults between ASCT
devices or TMC
* Local system faults
6.0-9 5 The ASCT shall report Yes This functionality is Demonstration
comparisons of logged provided through
data when requested TransSuite TCS
by the user: console.
* Day to day
* Hour to hour
* Hour of day to hour
of day
* Hour of week to
hour of week
* Day of week to day
week
* Day of year to day of
year
6.0-10 5 The ASCT shall store 4.11.0-4 Yes All data are stored in Demonstration
data logs in a standard The system operator needs to store all SQL-2003 compatible
database. operational data and signal timing standard database.
parameters calculated by the adaptive
system, and export selected data to a City
of Phoenix TMC server using remote
access from TMC.

SERIAL 15058-RFP
6.0-11 5 The ASCT shall report 4.11.0-7 Yes The data are reported Demonstration
stored data in a form Have the ability to generate historic and by a dashboard and
suitable to provide real-time reports that effectively support can be exported as
explanations of system operation, maintenance and reporting of separate files.
behavior to system performance and traffic conditions.
troubleshoot the
system.
7 7 Advanced Controller
Operation
7.0-1 5 When specified by the 4.9.0-1.0-1 Yes This is configured at Demonstration
user, the ASCT shall Service a phase more than once per cycle, the controller level to
display a vehicle phase such as running a left turn phase before enable phase
more than once for and after its opposing through movement reservice.
each time the
coordinated phase is
served.
7.0-2 5 The ASCT shall provide 4.9.0-1.0-2 Yes This is configured at Demonstration
a minimum of eight Operate at least eight overlap phases the controller level as
phase overlaps. supported by the
controller firmware.
7.0-3 5 The ASCT shall 4.9.0-1.0-3 Yes This is configured at Demonstration
accommodate a Operate three rings, eight phases and up the controller level as
minimum of eight to two phases per ring. supported by the
phases at each signal controller firmware.
7.0-4 5 The ASCT shall Yes This is configured at Demonstration
accommodate a the controller level as
minimum of three supported by the
rings at each signal. controller firmware.
7.0-5 5 The ASCT shall Yes This is configured at Demonstration
accommodate a the controller level as
minimum of two supported by the
phases per ring controller firmware.
7.0-6 5 The ASCT shall provide 4.1.0-6 Yes This is configured at Demonstration
a minimum of eight The system operator needs to modify the the controller level as

SERIAL 15058-RFP
different user-defined sequence of phases to support the various supported by the
phase sequences for operational strategies. controller firmware.
each signal. 4.9.0-1.0-4
Permit different phase sequences under
7.0-6.0-1 5 Each permissible different traffic conditions or by time-of- Yes This is configured at Demonstration
phase sequence shall day the controller level as
be user-assignable to supported by the
any signal timing plan. controller firmware.
7.0-6.0-2 5 Each permissible Yes Permissible phase Demonstration
phase sequence shall sequence can be set
be executable by a to run on a TOD
time of day schedule. schedule
7.0-6.0-3 5 Each permissible Yes Permissible phase Demonstration
phase sequence shall sequence can be
be executable based selected based on
on measured traffic traffic conditions.
conditions
7.0-7 3 The ASCT shall not 4.1.0-6 Yes Phase /overlap is not Demonstration
prevent a The system operator needs to modify the prevented by time of
phase/overlap output sequence of phases to support the various day.
by time-of-day. operational strategies.
7.0-8 3 The ASCT shall not Yes ACDSS does not Demonstration
prevent a prevent phase/overlap
phase/overlap output 4.17.0-2 based on an external
based on an external input.
The system operator needs to react to
input.
commands issued by TranSuite and future
decision support system, such as an ICM
system.
7.0-9 4 The ASCT shall not 4.1.0-6 Yes ACDSS does not Demonstration
prevent user-specified The system operator needs to modify the prevent user-specified
phases to be sequence of phases to support the various phases to be
designated as operational strategies. designated as
coordinated phases. 4.9.0-1.0-9 coordinated phases.

SERIAL 15058-RFP
Allow any phase to be designated as the
coordinated phase
7.0-10 5 The ASCT shall have 4.9.0-1.0-12 Yes Early return to green Demonstration
the option for a Allow the coordinated phase to terminate can be adjusted by
coordinated phase to early under prescribed traffic conditions selecting fixed force-
be released early off or floating force-
based on a user- off.
definable point in the
phase or cycle. (User
selected phase or
cycle.)
7.0-11 3 The ASCT shall not 4.9.0-1.0-15 Yes FLA is not prevented. Demonstration
prevent the controller Use flashing yellow arrow to control
from displaying permissive left turns.
flashing yellow arrow
left turn.
7.0-13 5 When adaptive 4.9.0-1.0-16 Yes ACDSS does not Demonstration
operation is used in Service side streets and pedestrian phases prevent a controller to
conjunction with at minor locations more often than at run a cycle different
normal coordination, adjacent signals when this can be done from adjacent
the ASCT shall not without compromising the quality of the intersections, if
prevent a controller coordination. (E.g., double-cycle mid-block configured as such.
serving a cycle length pedestrian crossing signals.)
different from the
cycles used at adjacent
intersections.
8 8 Pedestrians
8.0-2 5 When the pedestrian 4.6.0-2 Yes Pedestrian WK + FLDW Demonstration
phase is called, the The system operator needs to has higher priority
ASCT shall accommodate infrequent pedestrian over adaptive timing.
accommodate operation while maintaining adaptive If WK+FLDW is longer
pedestrian crossing operation. (This is appropriate for than the current
times during adaptive pedestrian calls that are common but not adaptive timing,
operations. so frequent that they drive the operational WK+FLDW shall be

SERIAL 15058-RFP
needs.) honored.
4.6.0-3
The system operator needs to incorporate
frequent pedestrian operation into routine
adaptive operation. (This is appropriate
when pedestrians are frequent enough
that they must be assumed to be present
every cycle or nearly every cycle.)
8.0-3 5 The ASCT shall execute 4.6.0-1 Yes User specified Demonstration
user-specified The system operator needs to exclusive pedestrian
exclusive pedestrian accommodate infrequent pedestrian phases can be
phases during operation and then adaptively recover. actuated and serviced
adaptive operation. (This is appropriate for rare pedestrian during adaptive
calls.) operations upon ped
calls.
8.0-5 5 The ASCT shall have 4.6.0-3 Yes Pedestrian phase can Demonstration
the option for a phase The system operator needs to incorporate start late as long as
to start late, when frequent pedestrian operation into routine there is sufficient time
there is not a adaptive operation. (This is appropriate remaining on the
pedestrian call for that when pedestrians are frequent enough compatible vehicle
phase, provided the that they must be assumed to be present phase. This is subject
minimum green time every cycle or nearly every cycle.) to the controller
is available. firmware.
9 9 Special Functions
9.0-1 3 The ASCT shall set a 4.9.0-1.0-11 Yes This is supported via Demonstration
specific state for each Allow the controller to respond TransSuite
special function output independently to individual lanes of an
based on the approach. This may be implemented in the
occupancy on a user- signal controller using extension/passage
specified detector. timers, which may be assignable to each
vehicle detector input channel. This may

SERIAL 15058-RFP
allow the adaptive operation to be based
on data from a specific detector, or by
excluding specific detectors.
9.0-2 3 The ASCT shall set a 4.17.0-1 Yes This is supported via Demonstration
specific state for each The system operator needs to be able to TransSuite
special function output turn on signs that control traffic or provide
based on the current driver information when specific traffic
cycle length. conditions occur, when needed to support
9.0-3 3 The ASCT shall set a the adaptive operation, when congestion is Yes This is supported via Demonstration
specific state for each detected at critical locations or according TransSuite
special function output to a time-of-day schedule
based on a time-of-day
schedule.
10 10 Detection
10.0-1 4 The ASCT shall be Yes ACDSS support any Demonstration
compatible with the detector technology
following detector as long as volume and
technologies: occupancy data are
provided.
* Existing Inductive
Loops
* Existing Video
* Furnished Detection
11 11 EV Pre-emption
11.0-2 3 The ASCT shall 4.13.0-2 Yes Non-preempted Demonstration
maintain adaptive The system operator needs to intersections shall
operation at non- accommodate emergency vehicle operate normal
preempted preemption. The City of Phoenix and ADOT adaptive operations.
intersections during use intersection-based preemption. The
emergency vehicle request is received at the controller
preemption. directly from the emergency vehicle.
11.0-4 5 The ASCT shall operate Yes Special function that Demonstration

SERIAL 15058-RFP
normally at non- omits phase or put a
preempted signal max recall shall not
controllers when impact normal
special functions are adaptive operation.
engaged by a
preemption event. (An
example of such a
special functions is a
phase omit, a phase
maximum recall or a
fire route.)
11.0-6 5 The ASCT shall return Yes Adaptive operation Demonstration
to normal adaptive shall be resumed
operation when when preemption is
preemption of a signal released.
controller is released.
11.0-7 1 The ASCT shall Yes Preemption always Demonstration
preempt a user- has higher priority
specified group of than adaptive
signal controllers operations. ACDSS
when a user-specified supports preempting
preemption is signal groups.
requested.
11.0.8 5 The ASCT shall not Yes ACDSS doesn't prevent Demonstration
prevent the local local actuated mode.
signal controller from
operating in normally
detected limited-
service actuated mode
during preemption.
12 12 Transit Priority NOT USED
13 13 Failure Events and
Fallback
13.1 13.1 Detector Failure

SERIAL 15058-RFP
13.1.0-1 5 The ASCT shall take 4.14.0-1
user-specified action The system operator needs to fall back to
in the absence of valid TOD operation without causing disruption
detector data from a to traffic flow, in the event of equipment,
user-specified number communications and software failure. The
of vehicle detectors system shall recognize a detector failure
within a group. and take appropriate action to
13.1.0-1.0- 5 The ASCT shall release accommodate the missing data. For a local
1 control to central detector failure, the local controller shall
system control. place a soft recall or maximum recall (to be
13.1.0-1.0- 2 The ASCT shall release user-specified) on the appropriate phase,
2 control to local and issue an alarm. For a detector that
operations to operate influences the adaptive operation (e.g., a
under its own time-of- system detector), the system shall use
day schedule. historical data from the failed detector,
13.1.0-2 2 The ASCT shall use the from a period that can reliably be expected
following alternate to be similar to the current period. If the
data sources for number of detector failures within a
operations in the specified group exceeds a user-specified
absence of the real- threshold, the system shall cease adaptive
time data from a operation and go to a fallback operation
detector: Stored specified by the user (such as time-of-day
historical data from operation or free operation). The fallback
the failed detector. operation shall be specified by the user
13.1.0-2.0- 5 The ASCT shall switch based on location and time of day.
3 to the alternate source
in real time without
operator intervention.
13.1.0-3 5 In the event of a 4.12.0-1
detector failure, the The system operator needs to immediately
ASCT shall issue an notify maintenance and operations staff of
alarm to user-specified alarms and alerts.
recipients. (This 4.12.0-2

SERIAL 15058-RFP
requirement may be The system operator needs to immediately
fulfilled by sending the and automatically pass alarms and alerts to
alarm to a designated the TranSuite and Regional Archived Data
list of recipients by a System (RADS).
designated means, or
by using an external
maintenance
management system.)
13.1.0-4 5 In the event of a 4.12.0-3
failure, the ASCT shall The system operator needs to maintain a
log details of the complete log of alarms and failure events.
failure in a permanent
log.
13.1.0-5 5 The permanent failure
log shall be
searchable, archivable,
and exportable.
13.2 13.2 Communications
Failure
13.2-1 5 The ASCT shall execute 4.14.0-1
user-specified actions The system operator needs to fall back to
when communications TOD operation without causing disruption
to one or more signal to traffic flow, in the event of equipment,
controllers fails within communications and software failure.
a group.
13.2-1.0-1 5 In the event of loss of
communication to a
user-specified signal
controller, the ASCT
shall release control of
all signal controllers
within a user-specified
group to local control.
13.2-1.0-2 5 The ASCT shall switch

SERIAL 15058-RFP
to the alternate
operation in real time
without operator
intervention.
13.2-2 5 In the event of 4.12.0-1
communications The system operator needs to immediately
failure, the ASCT shall notify maintenance and operations staff of
issue an alarm to user- alarms and alerts.
specified recipients. 4.12.0-2
(This requirement may
The system operator needs to immediately
be fulfilled by sending
and automatically pass alarms and alerts to
the alarm to a
the TranSuite and Regional Archived Data
designated list of
System (RADS).
recipients by a
designated means, or
by using an external
maintenance
management system.)
13.2-3 5 The ASCT shall issue an
alarm within 1 minute
of detection of a
failure.
13.2-4 5 In the event of a 4.12.0-3
communications The system operator needs to maintain a
failures, the ASCT shall complete log of alarms and failure events.
log details of the
failure in a permanent
log.
13.2-5 5 The permanent failure
log shall be
searchable, archivable,
and exportable.
13.3 13.3 Adaptive
Processor Failure

SERIAL 15058-RFP
13.3-1 5 The ASCT shall execute 4.14.0-1 Yes
user-specified actions The system operator needs to fall back to
when adaptive control TOD operation without causing disruption
fails: to traffic flow, in the event of equipment,
13.3-1.0-1 5 The ASCT shall release communications and software failure. Yes ACDSS shall release Demonstration
control to central adaptive. The system
system control. shall revert to the
default mode, central
system control or local
TOD
13.3-1.0-2 2 The ASCT shall release Yes ACDSS shall revert to Demonstration
control to local local TOD, if such is set
operations to operate as the default fall
under its own time-of- back.
day schedule.
13.3-2 5 In the event of 4.12.0-1 Yes Alarms by text Demonstration
adaptive processor The system operator needs to immediately message or by email.
failure, the ASCT shall notify maintenance and operations staff of
issue an alarm to user- alarms and alerts.
specified recipients. 4.12.0-2
(This requirement may
The system operator needs to immediately
be fulfilled by sending
and automatically pass alarms and alerts to
the alarm to a
the TranSuite and Regional Archived Data
designated list of
System (RADS).
recipients by a
designated means, or
by using an external
maintenance
management system.)
13.3-3 5 The permanent failure 4.12.0-3 Yes The logged failure is Demonstration
log shall be The system operator needs to maintain a searchable,
searchable, archivable, complete log of alarms and failure events. achievable, and
and exportable. exportable.
13.3-4 5 During adaptive 4.14.0-1 Yes ACDSS does not Demonstration

SERIAL 15058-RFP
processor failure, the The system operator needs to fall back to intercept local
ASCT shall provide all TOD operation without causing disruption detector inputs to
local detector inputs to traffic flow, in the event of equipment, local controller.
to the local controller. communications and software failure.
14 14 Software
14.0-1 5 The vendor's adaptive 4.15.0-2 Yes ACDSS is a Windows Demonstration
software shall be fully based software
operational within the running on a Windows
following platform: Server. TransSuite TCS
(edit as appropriate) is Windows/Linux
based software.
* Windows-PC The system operator needs to use
* Linux equipment and software acceptable under
current agency IT policies and procedures.
14.0-2 5 The system shall 4.15.0-1.0-2 Yes ACDSS interface the
interface with Detector type detectors via
standard loop TransSuite TCS.
detectors, Traficon
video detection and
furnished detection.
14.0-3 5 The system shall 4.15.0-1.0-1 Yes These controllers are Demonstration
interface with Controller type supported.
Econolite ASC/2S-
2100, Econolite ASC/2-
2000RM, and ASC/3
controllers.
15 15 Training
15.0-1 The vendor shall 4.16.0-1 Yes This is part of our
provide the following The agency needs all staff involved in standard training
training. operation and maintenance to receive package.
15.0-1.0-1 5 The vendor shall appropriate training. This is part of our
provide training on the standard training
operations of the package.
adaptive system.

SERIAL 15058-RFP
15.0-1.0-2 5 The vendor shall This is part of our
provide training on standard training
troubleshooting the package.
system.
15.0-1.0-3 5 The vendor shall This is part of our
provide training on standard training
preventive package.
maintenance and
repair of equipment.
15.0-1.0-4 5 The vendor shall This is part of our
provide training on standard training
system configuration. package.
15.0-1.0-5 5 The vendor shall This is part of our
provide training on standard training
administration of the package.
system.
15.0-1.0-6 5 The vendor shall This is part of our
provide training on standard training
system calibration. package.
15.0-1.0-7 5 The vendor's training This is part of our
delivery shall include: standard training
printed course package.
materials and
references, electronic
copies of
presentations and
references.
15.0-1.0-8 5 The vendor's training The training shall be
shall be delivered at provided at the
the TMC and Signal designated location.
Shop.
15.0-1.0-9 5 The vendor shall The training shall be
provide a minimum of provided for the
4 hours training to a designated staff of the

SERIAL 15058-RFP
minimum of 25 staff. City.
15.0-1.0- 5 The vendor shall This is part of our
10 provide a minimum of standard training
5 training sessions package.
over 3 months.
16 16 Maintenance,
Support and Warranty
16.0-1 5 The Maintenance 4.16.0-2 Yes This is part of our
Vendor shall provide The agency needs the system to fulfill all standard maintenance
maintenance requirements for the life of the system. and support
according to a The agency therefore needs the system to agreement. Full terms
separate maintenance be maintained to repair faults that are not and conditions of the
contract. That contract defects in materials and workmanship. maintenance and
should identify repairs support contract shall
necessary to preserve be negotiated when
requirements appropriate.
fulfillment,
responsiveness in
effecting those repairs,
and all requirements
on the maintenance
provider while
performing the
repairs.
16.0-2 5 The Vendor shall 4.16.0-4 Yes This is part of our
provide routine The agency needs the system to fulfill all standard maintenance
updates to the requirements for the life of the system. and support
software and software The agency therefore needs support to agreement. Full terms
environment keep software and software environment and conditions of the
necessary to preserve updated as necessary to prevent maintenance and
the fulfillment of requirements no longer being fulfilled. support contract shall
requirements for the be negotiated when
life of the system. appropriate.
Preservation of

SERIAL 15058-RFP
requirements
fulfillment especially
includes all IT
management
requirements as
previously identified.
16.0-3 5 The Vendor shall 4.16.0-3 Yes Warranty shall be
warrant the system to The agency needs the system to fulfill all provided as specified.
be free of defects in requirements for the life of the system.
materials and The agency therefore needs the system to
workmanship for a remain free of defects in materials and
period of 5 years. workmanship that result in requirements
Warranty is defined as no longer being fulfilled.
correcting defects in
materials and
workmanship (subject
to other language
included in the
purchase documents).
Defect is defined as
any circumstance in
which the material
does not perform
according to its
specification.
17 17 Schedule
17.0-1 3 The ASCT shall set the 4.17.0-1 Yes This is accomplished Demonstration
state of external The system operator needs to be able to via TransSuite TCS
input/output states turn on signs that control traffic or provide
according to a time-of- driver information when specific traffic
day schedule at user- conditions occur, when needed to support
specified locations. the adaptive operation, when congestion is
17.0-2 3 The ASCT output detected at critical locations or according Yes This is accomplished Demonstration

SERIAL 15058-RFP
states shall be settable to a time-of-day schedule via TransSuite TCS
according to a time-of-
day schedule
17.0-3 3 The ASCT operational Yes This is accomplished Demonstration
parameters shall be via TransSuite TCS
settable according to a
Time of Day schedule
18 18 Performance
Measurement,
Monitoring and
Reporting
18.0-1 5 The ASCT shall report 4.11.0-2 Yes ACDSS logs all data Demonstration
measures of current The system operator needs to store and and measures of
traffic conditions on report data used to calculate signal timing traffic conditions in
which it bases signal and have the data available for subsequent the database.
state alterations. analysis.
18.0-2 5 The ASCT shall report Yes All intermediate Demonstration
all intermediate calculated values are
calculated values that logged.
are affected by
calibration
parameters.
18.0-3 5 The ASCT shall Yes All signal state change Demonstration
maintain a log of all 4.11.0-7 (detailed controller
signal state alterations Have the ability to generate historic and status data including
directed by the ASCT. real-time reports that effectively support cycle, offset, and
operation, maintenance and reporting of individual splits, cycle
system performance and traffic conditions. start and end time).
Whether the signal is
in transition, and
transition cycles are
also logged.
18.0-3.0-1 5 The ASCT log shall No This is not supported Demonstration

SERIAL 15058-RFP
include all events right now.
directed by the
external inputs.
18.0-3.0-2 5 The ASCT log shall No This is not supported Demonstration
include all external right now.
output state changes.
18.0-3.0-3 5 The ASCT log shall Yes All the configurable Demonstration
include all actual inputs are logged in
parameter values that the DB
are subject to user-
specified values.
18.0-3.0-4 5 The ASCT shall Yes The log can be kept Demonstration
maintain the records from minimum 1
in this ASCT log for 31 month to permanent
days.
18.0-3.0-5 5 The ASCT shall archive Yes The log can be kept Demonstration
the ASCT log after 31 from minimum 1
days in the following month to permanent
manner: .CSV, MS
Excel, Text

SERIAL 15058-RFP
Exhibit C
Software License and Maintenance Agreements
C.1 ACDSS License Agreement
The following document represents KLD’s End User License Agreement for ACDSS. This license agreement will be
executed with Maricopa County for the ACDSS deployments in Scottsdale and Phoenix. Existing Scottsdale and
Phoenix TransSuite license will not be affected.
ACDSS Software End User License Agreement
I. Definitions
KLD means KLD Engineering, P.C. a firm incorporated in the State of New York that provides professional services in
the practice of engineering, including transportation and transportation-related software engineering.
ACDSS, Software, or ACDSS Software means the binary, executable version of the adaptive signal control software
package as described in the purchase order and related documentation.
Agency means Maricopa County, the State of Arizona, City of Phoenix, or City of
Scottsdale_____________________________
II. License
KLD grants to Agency a non-exclusive, non-transferable license for use of the ACDSS software in Agency. Title to all
intellectual property rights including patent, trademark, copyright and trade secret rights and title to all ownership rights
and all copies of and all media bearing the licensed Software, support materials and control concept shall remain in
KLD.
The license is a permanent license, at the one-time cost specified and for the specific use specified in Section VII. This
fee also covers one year of maintenance that includes free upgrades of the ACDSS software.
The Agency may elect to pay an annual software maintenance fee after the initial one year maintenance period cited, at
the cost specified in Section VII. If the Agency does not elect to have continual maintenance coverage, it may - at its
own risk and responsibility - continue to use the product as initially delivered and/or as upgraded during any continual
maintenance period thereafter (unless it breaches the conditions below, in this Section II).
KLD’s commitment and obligation is to maintain and service the most recent revision/release/version number of the
software licensed. That revision/release/version will be the result of the activities cited in Section IV (“Warranty”).
The Agency may choose to install the latest revision/release/version or not, but it is only the most recent
revision/release/version that is supported.
Agency shall be entitled to:
a. Use the licensed Software, only in binary, executable form on licensed computers.
b. Use the support documentation but only as required to support the use of the licensed Software.
c. Make as many backup copies of the licensed Software in binary, executable form as necessary for its
operating policies and practices. All backup copies must include the copyright notice in the original
form as it appears on the licensed Software.
Agency may not:
a. Sub-license, share, sell, rent, lease or otherwise transfer Agency’s right to use the Software; or
b. Copy, modify, translate, decompile, disassemble, tamper with, or reverse engineer any part of the
Software; or
c. Use the Software to develop any other Software and derivative products; or

SERIAL 15058-RFP
d. Alter, remove or obscure copyright or Intellectual Property statements applied to the Software.
e.
The licensed Software and support material included with this Agreement are confidential information that is the
property of KLD. The licensed Software, control concepts or any of the support materials shall not be made available to
any other party or organization without the written consent of KLD.
KLD can terminate this agreement if Agency breaches a provision of this License and have not remedied that breach
within 30 calendar days after receipt of a notice from KLD requiring Agency to rectify such breach.
On termination of the License, Agency must immediately:
a. Stop using the Software;
b. Ensure all copies of the Software are deleted or permanently removed from any form of storage; and
c. Return to KLD all other confidential information of KLD in material form.
III. Confidentiality
Confidential Information
In the performance of this Agreement or in contemplation thereof, the parties and their respective employees and agents
may have access to private or confidential information owned or controlled by the other party and such information may
contain proprietary details and disclosures. All information and data identified in writing as proprietary or confidential
by either party ("Confidential Information") and so acquired by the other party or its employees or agents under this
Agreement or in contemplation thereof shall be and shall remain the disclosing party's exclusive property. The recipient
shall use all reasonable efforts (which in any event shall not be less than the efforts the recipient takes to ensure the
confidentiality of its own proprietary and other confidential information) to keep, and have its employees and agents
keep, any and all "Confidential Information" confidential, and shall not copy, publish or disclose it to others, nor
authorize it's employees, agents or anyone else to copy or disclose it to others without the disclosing party's written
approval; nor shall the recipient make use of the "Confidential Information" except for the purposes of executing its
obligations hereunder, and (except as provided for herein) shall return the Confidential Information and data to the first
party at its request. Agency's duty to maintain confidentiality as described hereunder shall be subject to the laws of the
State of New York.
Excluded information
The foregoing conditions will not apply to information or data which is, or which becomes generally known to the
public by publication or by any means other than a breach of duty on the part of the recipient hereunder, is information
previously known to the recipient, is information independently developed by or for the recipient or is information
generally released by the owning party without restriction.
Right to Injunctive Relief
Because of the unique nature of the Confidential Information, the parties agree that each party may suffer irreparable
harm in the event that the other party fails to comply with any of its obligations under this Confidentiality Article, and
that monetary damages may be inadequate to compensate either party for such breach. Accordingly, the parties agree
that either party will, in addition to any other remedies available to it at law or in equity, be entitled to seek injunctive
relief to enforce the terms of this Article.
IV. Warranty
KLD warrants to Agency that KLD shall supply to Agency, during the license period and any continuous period of
extended maintenance thereafter, in a timely manner, any software revisions that are developed for the ACDSS
software, without fee. Such revisions are either to correct “bugs”, provide additional features, or integrate the most up-
to-date Research and Development work by KLD, and are at the sole discretion of KLD. KLD will make a good faith
effort to remedy “bugs” identified by the Agency within the license period and any continuous period of extended
maintenance thereafter, should it concur that the problem identified is due to a “bug” and not using the software beyond
the capability for which it was designed and delivered.

SERIAL 15058-RFP
If KLD transfers its principal assets to another entity by sale or other means, the terms of this agreement will continue.
If KLD ceases operations without arrangements to transfers its assets including the source code of ACDSS, that source
code will be made available to the Agency for its own use only. If KLD discontinues support of the product at any time
in the future, the source code will be made available to the Agency for its own use only.
V. Schedule of Costs
The Agency shall have the right to use this license on any number of intersections that are under the jurisdiction of the
Agency, as represented to KLD in its definition of use.
The ACDSS permanent license requires a one-time license fee as described in Exhibit A of this Contract. This fee also
covers the first year of software maintenance. Software maintenance and support is included for years two through five
as described in Exhibit A.
Should the Agency wish to have software enhancements done by KLD, they will be offered at the standard rate table
(Attachment B below) used for public sector clients, or can be quoted on a firm fixed price basis. This can be done as a
separate authorization or as an option in the Agency’s purchase order, at the Agency’s discretion.
Should the Agency wish to have system design and traffic engineering professional services done by KLD, either
directly or as a subconsultant to another consultant, they will be offered at the standard rate table used for public sector
clients. If the preference is for KLD to be a subconsultant to another consultant however, KLD must retain the right to
choose whether to participate in the particular teaming arrangement of interest.
C.2 Software Maintenance Agreement
The following Software Maintenance Agreement will be executed with Maricopa County for Project Areas 3 and 4,
Scottsdale and Phoenix. Existing TransSuite Maintenance Agreements between the Cities of Scottsdale and Phoenix
and TransCore will not be affected.
1 AGREEMENT COVERAGE
Period of Coverage:
2 SOFTWARE COVERAGE
Services will be provided under this agreement for the following software applications:
 Adaptive Control Decision Support System
All software listed above and covered under this agreement is provided under and subject to the Software License
Agreement between TransCore and Maricopa County.
3 GENERAL TERMS AND CONDITIONS
The purpose of this Software Maintenance Agreement is to provide support and applicable updates for the software
components listed in Section 2, along with the option for additional work as discussed in Section 6.
3.1 The scope-of-services presented in this Software Maintenance Agreement (herein referred to as the
"Agreement") are to be provided by TransCore ITS, LLC. (TransCore) to Maricopa County, the State of
Arizona, City of Phoenix, or City of Scottsdale hereinafter referred to as the “Customer.”

SERIAL 15058-RFP
3.2 Neither TransCore nor the Customer will assign this Agreement or any right hereunder to any person, firm, or
entity without the written consent of the other party. In addition, such consent will not be unreasonably
withheld.
3.3 Neither party shall be responsible for delays or failures in performance resulting from acts beyond its control,
such as labor strikes, fire, acts of war, terrorist attacks (or other casualties), communication line failures,
electrical/power failures, or irregularities, and the like. The Customer shall be responsible for ensuring that all
necessary communications lines are restored to proper operation before requesting on-site assistance under the
provision of this contract unless it is for the purpose of troubleshooting system problems as noted in Section 4,
Paragraph 3.
3.4 This Agreement will be interpreted and construed in accordance with the laws of the State of Arizona, without
regard to its conflicts of law principles.
3.5 The Customer agrees not to engage in any recruiting efforts of TransCore's personnel without receiving written
consent from the individual employee's management.
3.6 Any terms of this Agreement which are held to be invalid will be deleted, but the remainder of these terms will
not be affected.
3.7 If either party becomes insolvent, is unable to pay its debt when due, files for bankruptcy, is the subject of
involuntary bankruptcy, has a receiver appointed, or has its assets assigned, the other party may cancel any
unfulfilled obligations.
3.8 Neither party's failure to exercise any of its rights under this Agreement will constitute or be deemed a waiver
or forfeiture of those rights.
3.9 Any changes, additions, and enhancements in the form of new or partial programs or documentation as may be
provided under this Agreement shall remain the proprietary property of TransCore. The License Agreement
specified above will include under its proprietary restrictions any such additional programming and
documentation provided under this Agreement.
4 CONTRACT LENGTH OF SERVICES
4.1 Agreement Duration – The time period within this Agreement for the rendering of Software Support Services
by TransCore to the Customer shall be as stated in Article 1 above.
INTENTIONALLY OMITTED
4.2 Agreement Hours of Operation and Response Times – TransCore’s services hereunder are provided on an
ad hoc time and materials basis at the Customer’s request. TransCore personnel will be available for telephone
consultations/inquiries and/or on-site visits as the situation demands and staff availability permit. The primary
hours for services will be during our regular business hours Monday thru Friday, 8:00 AM thru 6:00 PM
Eastern Time.
Services outside these normal operating hours, including nights, weekends, and holidays, will be provided as
staff availability permits. The Customer will be required to contact appropriate TransCore personnel in these
cases. TransCore staff contacts, and after hours contact numbers, are listed in Attachment A.
TransCore personnel will respond to Customer requests for Software Support Services within a reasonable
time period. During regular business hours, TransCore will begin to provide services to the Customer within
twenty-four (24) hours of the request. During emergency situations, during regular business hours, TransCore
will begin to provide services to the Customer within four (4) hours of official notification when possible.
Outside normal business hours, TransCore will make every effort to provide services to the Customer within
eight (8) hours of official notification when possible and dependent upon the availability of a responsible
TransCore employee.

SERIAL 15058-RFP
5 AGREEMENT COST AND PAYMENT
5.1 The total amount/cost of this Agreement shall be as stated in Exhibit “A” of Contract 15058-RFP, plus any
amounts which may become due because of Additional services contracted by the Customer to TransCore
under the terms of the Contract and this Agreement.
5.2 All Contract Support and Software Support Services to be provided by TransCore, whether planned or an
emergency, shall be covered under the Contract and this Agreement at the cost listed above. Services not
covered within the Contract and this Agreement are subject to TransCore’s standard time and material rates.
5.3 Payment of the annual Agreement fee (as outlined in #1 above) shall entitle the Customer to specified
application software maintenance support services by TransCore based on the terms and conditions set forth
within the Contract and this Agreement.
5.4 If the Customer fails to pay any additional support fees (services not covered under the Contract and/or this
Agreement but requested by the Customer at TransCore’s standard time and material rates), or fails to perform
under the Contract or this Agreement with TransCore after 10 days written notice, TransCore reserves the right
to withhold services pending full payment of fees or compliance with these terms by the Customer. If
TransCore fails to respond to the Customer within 10 days of verbal correspondence, the Customer has the
option to terminate this agreement.
5.5 TransCore will submit itemized cost invoices to the Customer for prior approval of Additional services
rendered (services not covered under the Contract and/or this Agreement, but requested by the Customer at
TransCore’s standard time and material rates). All charges for Additional services are payable by the Customer
as a net amount due in thirty (30) days from the date of the invoice. All payments made by the Customer after
forty-five (45) days from date of invoice shall be subject to a 1.5% per month penalty fee until the date paid.
5.6 Time and Materials Rates are as per Attachment B.
5.7 There shall be added to maintenance fees and other charges under this agreement amounts equal to any tariff,
duties and/or sales or use tax, or any tax in lieu thereof (including any interest or penalties) imposed by the
government or governmental agency with respect to services rendered by TransCore under the Contract and/or
this Agreement and which TransCore now or in the future may be required to collect or remit. If the Customer
has tax exemption capabilities, they are free to exercise these options, as always.
5.8 Corrections for difficulties or defects traceable to Customer errors or system changes will be billed at
TransCore standard time and material rates.
6 AGREEMENT SCOPE-OF-SERVICES
6.1 Coverage – The software covered under this Agreement is that software outlined in Section 1 of this
Agreement. Any corrections or alterations to or new versions of the Software that TransCore may deliver to the
Customer under this Agreement shall be limited to one (1) copy of the source code and documentation (if new
documentation is appropriate).
6.2 Services to be Performed – TransCore will support the Customer in the maintenance and operation of their
TransCore software as outlined in Section 1. This support may span a broad range of services including, but
not limited to, technical consulting, troubleshooting and diagnosis of problems, software defect correction,
periodic or preventive maintenance, software version upgrades, training, system expansion, and/or system
enhancement.
6.3 Software Installation Scheduling – TransCore will install any and all software modifications and/or programs
for portions thereof on the Customer’ systems only at times mutually agreeable between both parties.
6.4 Documentation – TransCore will maintain a log of the Customer’ user requests/errors/problems.

SERIAL 15058-RFP
6.5 Cost Accounting and Invoicing (For Time and Materials Work ONLY )– TransCore will track time and
material costs and generate monthly Contract invoices through our job cost accounting system. This monthly
Contract invoice will reflect the current time and materials cost for the invoice period and the total time and
materials cost over the duration of the Contract to date.
7 WARRANTY
TransCore does not warrant that the operation of its software products will be uninterrupted or error-free. TransCore
will place the highest emphasis on resolving problems within a mutually agreed upon time period.
THE EXPRESS WARRANTIES, IF ANY, CONTAINED IN THIS CONTRACT ARE THE SOLE AND
EXCLUSIVE WARRANTIES PROVIDED BY CONTRACTOR. TRANSCORE SPECIFICALLY DISCLAIMS
ANY OTHER WARRANTIES, EXPRESS OR IMPLIED INCLUDING BUT NOT LIMITED TO WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, AS WELL AS ANY WARRANTIES
ALLEGED TO HAVE ARISEN FROM CUSTOM, USAGE, OR PAST DEALINGS BETWEEN THE PARTIES.
8 CUSTOMER RESPONSIBILITIES
8.1 The Customer shall have an assigned individual to serve as liaison between the Customer and TransCore. The
Customer acknowledges its obligation to provide personnel having sufficient skills and experience to operate
and manage the equipment and/or programs being provided to obtain the desired results.
8.2 The Customer shall be exclusively responsible for the supervision, management, and control of its use of the
TransCore software including, but not limited to the following:
- assuring proper configuration, program installation, audit controls, and operating methods;
- establishing adequate backup plans based on alternate procedures in the event of computer system
malfunction;
- implementing sufficient procedures and checkpoints to satisfy its requirements for security and
accuracy of input and output as well as restart and recovery in the event of malfunction;
- informed use of the output insofar as technical expertise or professional judgment is required; and
- maintenance and distribution of system passwords.
8.3 The Customer is responsible for the security of its proprietary and confidential information and for maintaining
a procedure external to the software products to reconstruct lost or altered Customer files, data, or programs.
8.4 Before execution of on-site support service by TransCore, the Customer shall make reasonable efforts to have
a representative of the Customer available at the time these services are provided. TransCore will accept
written approval, if a representative is not available, so as to have on-site access to the system for support
purposes. TransCore will be held harmless for all circumstances arising from this access that would normally
be the domain of the Customer or its designated representative including but not limited to shortages, loss,
damages or destruction of Customer property. TransCore upon discovery of such facts shall report said items
to the Customer before beginning maintenance of system items.
8.5 The Customer shall notify TransCore if software products are being used in an environment or location, which
the Customer reasonable believes, poses a potential health and/or safety hazard to TransCore employees or
subcontractors.
8.6 The Customer shall maintain the hardware and software products in its system at the prescribed revision levels
while TransCore’s Software Support Services are in-effect at TransCore’s discretion.
8.7 The Customer shall provide TransCore access to and use of all information and facilities determined necessary
by TransCore to support the software.

SERIAL 15058-RFP
8.8 The Customer acknowledges that all TransCore software and/or changes, improvements, revisions or updates
made to TransCore software are the sole and exclusive property of TransCore and may be provided by
TransCore to others.
8.9 The Customer agrees to provide TransCore with dumps, as requested, and with sufficient support and test time
on the Customer’ computer system to duplicate the problem, certify that the problem is indeed with
TransCore’s Software, and to certify that the problem has indeed been fixed or a suitable work-around devised.
8.10 The Customer agrees to install and maintain, for the duration of the Contract, internet access and a Customer
VPN account at the host computer.
9 DISPUTES
All Parties agree to first enter into negotiations to resolve any controversy, claim or dispute (“dispute”) arising under or
relating to this Agreement. The Parties agree to negotiate in good faith to reach a mutually agreeable resolution of such
dispute within a reasonable period of time.
10 NOTICES
Any notice or communication to TransCore shall be deemed served if it is delivered, in writing, personally or by
registered or certified mail to:
TransCore ITS, LLC
Contractual:
Ricardo Perez
Contract Manager
TransCore
150 4th Ave. North, Suite 1200
Nashville, TN 37219
Technical:
William L. Skillas, PE
Vice President
TransCore
192 Technology Parkway, Suite 500
Norcross, GA 30092
Any notice or communication to the CUSTOMER shall be deemed served if it is delivered, in writing, personally or by
registered or certified mail to:
April Wire
Maricopa County Department of Transportation
2901W.Durango
Phoenix, Arizona 85009
14 LIMITATION ON DISSEMINATION OF TRANSCORE COMMERCIAL WORK PRODUCT
TransCore and Customer expressly exclude any and all third parties from the benefits of this Agreement. In the event
that Customer furnishes any TransCore work product to a person who is not a party to this Agreement, Customer agrees
to defend, indemnify, and hold harmless TransCore from and against all claims, damages, losses, costs and expenses
(including reasonable attorney’s fees) of actions brought by third parties, and arising out of or relating to such third
party's use or distribution of, or reliance upon, the TransCore’s work product.

SERIAL 15058-RFP
Attachment A
TransCore Authorized Representatives
Wuping Xin
Office: 631-617-5650 x 227
Cell: 631-617-5649
Email: wxin@kldcompanies.com
Bill Skillas
Office: 770-246-6242
Cell: 678-910-8602
Email: william.skillas@transcore.com

SERIAL 15058-RFP
Attachment B
Time and Materials Rates
Labor 2016 2017 2018 2019 2020 2021
Category Hourly Rate Hourly Rate Hourly Rate Hourly Rate Hourly Rate Hourly Rate
Project Manager $ 220.31 $ 226.92 $ 233.73 $ 240.74 $ 247.96 $ 255.40
System Architect $ 220.31 $ 226.92 $ 233.73 $ 240.74 $ 247.96 $ 255.40
Senior Systems $ 186.81 $ 192.41 $ 198.19 $ 204.13 $ 210.26 $ 216.56
Engineer
Engineer I $ 132.40 $ 136.37 $ 140.46 $ 144.68 $ 149.02 $ 153.49
Engineer II $ 154.14 $ 158.76 $ 163.53 $ 168.43 $ 173.49 $ 178.69
Engineer III $ 265.66 $ 273.62 $ 281.83 $ 290.29 $ 299.00 $ 307.97

SERIAL 15058-RFP
Exhibit D
OFFICE OF PROCUREMENT SERVICES CONTRACTOR TRAVEL AND PER DIEM POLICY
1.0 All contract-related travel plans and arrangements shall be prior-approved by the County Contract
Administrator.
2.0 Lodging, per diem and incidental expenses incurred in performance of Maricopa County/Special
District (County) contracts shall be reimbursed based on current U.S. General Services
Administration (GSA) domestic per diem rates for Phoenix, Arizona. Contractors must access the
following internet site to determine rates (no exceptions): www.gsa.gov
2.1 Additional incidental expenses (i.e., telephone, fax, internet and copying charges) shall not
be reimbursed. They should be included in the contractor’s hourly rate as an overhead
charge.
2.2 The County will not (under no circumstances) reimburse for Contractor guest lodging, per
diem or incidentals.
3.0 Commercial air travel shall be reimbursed as follows:
3.1 Coach airfare will be reimbursed by the County. Business class airfare may be allowed only
when preapproved in writing by the County Contract Administrator as a result of the
business need of the County when there is no lower fare available.
3.2 The lowest direct flight airfare rate from the Contractors assigned duty post (pre-defined at
the time of contract signing) will be reimbursed. Under no circumstances will the County
reimburse for airfares related to transportation to or from an alternate site.
3.3 The County will not (under no circumstances) reimburse for Contractor guest commercial air
travel.
4.0 Rental vehicles may only be used if such use would result in an overall reduction in the total cost of
the trip, not for the personal convenience of the traveler. Multiple vehicles for the same set of
travelers for the same travel period will not be permitted without prior written approval by the
County Contract Administrator.
4.1 Purchase of comprehensive and collision liability insurance shall be at the expense of the
contractor. The County will not reimburse contractor if the contractor chooses to purchase
these coverage.
4.2 Rental vehicles are restricted to sub-compact, compact or mid-size sedans unless a larger
vehicle is necessary for cost efficiency due to the number of travelers. (NOTE: contractors
shall obtain pre-approval in writing from the County Contract Administrator prior to rental
of a larger vehicle.)
4.3 County will reimburse for parking expenses if free, public parking is not available within a
reasonable distance of the place of County business. All opportunities must be exhausted
prior to securing parking that incurs costs for the County. Opportunities to be reviewed are
the DASH; shuttles, etc. that can transport the contractor to and from County buildings with
minimal costs.

SERIAL 15058-RFP
4.4 County will reimburse for the lowest rate, long-term uncovered (e.g. covered or enclosed
parking will not be reimbursed) airport parking only if it is less expensive than shuttle
service to and from the airport.
4.5 The County will not (under no circumstances) reimburse the Contractor for guest vehicle
rental(s) or other any transportation costs.
5.0 Contractor is responsible for all costs not directly related to the travel except those that have been
pre-approved by the County Contract Administrator. These costs include (but not limited to) the
following: in-room movies, valet service, valet parking, laundry service, costs associated with
storing luggage at a hotel, fuel costs associated with non-County activities, tips that exceed the per
diem allowance, health club fees, and entertainment costs. Claims for unauthorized travel expenses
will not be honored and are not reimbursable.
6.0 Travel and per diem expenses shall be capped at 15% of project price unless otherwise specified in
individual contracts.
7.0 Contractor shall provide, (upon request) with their invoice(s), copies of receipts supporting travel
and per diem expenses, and if applicable with a copy of the written consent issued by the Contract
Administrator. No travel and per diem expenses shall be paid by County without copies of the
written consent as described in this policy and copies of all receipts.

SERIAL 15058-RFP
Exhibit E
Special Federal Terms, Conditions and Documents
Maricopa County Small Business Enterprise Program
Participation Reporting Form
This form is to be submitted with each pay application or invoice. Any pay application or invoice without this form
attached is subject to rejection as not being a completed pay application or invoice pursuant to the terms of the
contract.
Name of Prime Consultant Contractor Contract No.
Contact Person Project No.
Street Address Amount of this Pay Application/ Invoice
City, State ZIP
Complete below with information on the SBE firms utilized as sub consultants/ subcontractors for this pay
application/ invoice. If work was self-performed and your firm, as the prime, is an SBE firm pursuant to
ARS.§ 41-1001, et seq then you may list your firm as the SBE firm.
Type Of Work $ Paid to SBE App./
SBE Firm Name SBE Firm Address
Performed Invoice
$
$
$
$
$
$
￿ A mark in this box certifies that no SBE firms were utilized as the prime, subconsultant or subcontractor with
respect to this pay application/ invoice.
Date: Signature:
Printed Name & Telephone Number

SERIAL 15058-RFP
**FOR USE ON FEDERAL AID PROJECTS WITHOUT GOALS**
(EPRISENGL, 03/15/11)
DISADVANTAGED BUSINESS ENTERPRISES:
1.0 Policy:
The Arizona Department of Transportation (hereinafter the Department) has established a Disadvantaged
Business Enterprise (DBE) program in accordance with the regulations of the U.S. Department of
Transportation (USDOT ), 49 CFR Part 26. The Department has received Federal financial assistance from
the U.S. Department of Transportation and as a condition of receiving this assistance, the Department has
signed an assurance that it will comply with 49 CFR Part 26.
It is the policy of the Department to ensure that DBEs, as defined in Part 26, have an equal opportunity to
receive and participate in USDOT-assisted contracts. It is also the policy of the Department:
1. To ensure nondiscrimination in the award and administration of USDOT-assisted contracts;
2. To create a level playing field on which DBEs can compete fairly for USDOT-assisted contracts
3. To ensure that the DBE program is narrowly tailored in accordance with applicable law;
4. To ensure that only firms that fully meet 49 CFR Part 26 eligibility standards are counted as DBEs;
5. To help remove barriers to the participation of DBEs in USDOT-assisted contracts; and
6. To assist in the development of firms that can compete successfully in the market place outside the
DBE program.
Local Public Agencies (LPA) and or sub-recipients of Federal financial assistance will administer and
manage the contracts from advertising, consultant selection, negotiation, contract execution, processing
payment reports and contract modifications, audits, DBE compliance (e.g., reporting and monitoring)
through contract closeout.
2.0 Assurances of Non-Discrimination:
The contractor, sub-recipient, or subcontractor shall not discriminate on the basis of race, color, sex or
national origin in the performance of this contract. The contractor shall carry out applicable requirements
of 49 CFR Part 26 in the award and administration of contracts. Failure by the contractor tocarry 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 state deems appropriate. The contractor, sub-recipient, or subcontractor shall
ensure that all subcontract agreements contain this non-discrimination assurance.
3.0 Definitions:
A. Disadvantaged Business Enterprise (DBE): a for-profit small business concern which meets both
of the following requirements:
1. Is at least 51 percent owned by one or more socially and economically disadvantaged individuals
or, in the case of any publicly owned business, at least 51 percent of the stock is owned by one or
more such individuals; and,
2. Whose management and daily business operations are controlled by one or more of the socially
and economically disadvantaged individuals who own it.
B. Socially and Economically Disadvantaged Individuals: any individual who is a citizen (or
lawfully admitted permanent resident) of the United States and who is:

SERIAL 15058-RFP
1 Any individual who is found to be a socially and economically disadvantaged individual on a
case-by-case basis.
2 Any individual in the following groups, members of which are rebuttably presumed to be socially
and economically disadvantaged:
i. Black Americans," which includes persons having origins in any of the Black racial groups of
Africa;
ii. "Hispanic Americans," which includespersons of Mexican, Puerto Rican, Cuban, Central or
South American, or other Spanish or Portuguese culture or origin, regardless of race;
iii. "Native Americans," which includespersons who are American Indians, Eskimos, Aleuts, or
Native Hawaiians;
iv. "Asian-Pacific Americans," which includes persons whose origins are from Japan, China,
Taiwan, Korea, Burma (Myanmar), Vietnam, Laos, Cambodia (Kampuchea), Thailand, Mala-
ysia, Indonesia, the Philippines, Brunei, Samoa, Guam, the U.S. Trust Territories of the Pacific
Islands (Republic of Palau), the Commonwealth of the Northern Marianas Islands, Macao, Fiji,
Tonga, Kiribati, Tuvalu, Nauru, Federated States of Micronesia, or Hong Kong;
v. "Subcontinent Asian Americans," which includes persons whose origins are from India,
Pakistan, Bangladesh, Bhutan, the Maldives Islands, Nepal or Sri Lanka;
vi. "Women;"
vii. Any additional groups whose members are designated as socially and economically
disadvantaged by the Small Business Administration (SBA), at such time as the SBA
designation becomes effective.
C. Joint Venture: an association of a DBE firm and one or more other firms to carry out a single, for-
profit business enterprise, for which parties combine their property, capital, efforts, skills and
knowledge, and in which the DBE is responsible for a distinct, clearly defined portion of the work of
the contract and whose share in the capital contribution, control, management, risks, and profits of
the joint venture are commensurate with its ownership interest.
D. Non-DBE: any firm that is not a DBE.
E. RACE-CONSCIOUS: a measure or program is one that is focused specifically on assisting only
DBEs, including women-owned DBEs.
F. RACE-NEUTRAL: a measure or program is one that is, or can be, used to assist all small
businesses. For the purposes ofthis part, race-neutral includes gender- neutrality.
4.0 Working with DBEs:
The Department works with DBEs and assists them in their efforts to participate in the highway construction
program. All bidders should contact the Business Engagement and Compliance Office at the address shown
below for assistance in their efforts to use DBEs in the construction program of the Department:
Arizona Department of Transportation
Business Engagement and Compliance Office
1135 N. 22nd Avenue (second floor), Mail Drop 154A
Phoenix, AZ. 85009
Phone: (602) 712-7761
FAX:(602) 712-8429

SERIAL 15058-RFP
5.0 Applicability:
The Department has established an overall annual goal for DBE participation on Federal-aid contracts.
The Department intends for the goal to be met with a combination of race conscious efforts and race
neutral efforts. Race conscious participation occurs where the contractor uses a percentage of DBEs, as
defined herein, tomeet the contract-specified goal. Race neutral efforts are those that are, or can be, used to
assist all small businesses or increase opportunities for all small businesses. The regulation, 49 CFR 26,
defines race neutral as when a DBE wins a prime contract, is awarded a subcontract on a project without
DBE goals, and is awarded a subcontract from a prime contractor that did not consider the firm's DBE
status.
The provisions are applicable to all bidders including DBE bidders.
6.0 Certification:
Certification as a DBE shall be predicated on:
1. The completion and execution of an application for certification as a "Disadvantaged Business
Enterprise".
2. The submission of documents pertaining to the firm(s) as stated in the application(s), including but not
limited to a statement of social disadvantage and a personal financial statement.
3. The submission of any additional information which the Department may require to determine the firm's
eligibility to participate in the DBE program.
4. The information obtained during the on-site visits to the offices of the firm and to active job-sites.
Applications for certification may be filed with the Department at any time. Both hardcopy submission and
online submission is available.
For hardcopy submissions, applications for certification are available at the Business Engagement and
Compliance Office, 1135 N. 22nd Avenue (second floor), mail drop 154A, Phoenix, Arizona 85009, phone
(602) 712-7761. Hardcopy applications may also be obtained through the internet at www.azdbe.org.
Hardcopy applications must be filed through the Business Engagement and Compliance Office at the
above address.
For online submissions, the online application process may be accessed through the internet at
www.azdbe.org.
DBE firms and firms seeking DBE certification shall cooperate fully with requests for information relevant
to the certification process. Failure or refusal to provide such information is a ground for denial or removal
of certification.
Arizona is a member of the AZ Unified Certification Program (AZUCP). Only DBE firms that are certified
by the AZUCP are eligible for credit on ADOT projects. A list of DBE firms certified by AZUCP is available
on the internet at www.azdbe.org. The list will indicate contact information and specialty for each DBE firm,
and may be sorted in a variety of ways.
However, ADOT does not guarantee the accuracy and/or completeness of this information, nor does ADOT
represent that any licenses or registrations are appropriate for the work to be done.
The Department's certification is not a representation of qualifications and/or abilities. The contractor bears
all risks that the firm may not be able to perform its work for any reason.

SERIAL 15058-RFP
7.0 General:
Each contractor shall establish a program that will ensure nondiscrimination in the award and
administration of contracts and subcontracts.
Each contractor shall also designate a full time employee who shall be responsible for the administration of
the contractor's DBE program.
Agreements between the bidder and a DBE in which the DBE promises not to provide subcontracting
quotations to other bidders are prohibited.
8.0 DBE Subcontractor Payment Reporting:
The Department is required to collect data on DBE and non-DBE participation to report to Department Of
Transportation on Federal-aid projects. Maricopa County Transport will notify the contractor that such
record keeping is required by the Department for tracking DBE participation.
The contractor shall submit a report on a monthly basis indicating the amounts earned by and paid to all
DBEs and non-DBEs working on the project. In addition, the contractor shall require that all DBE and non-
DBE subcontractors verify receipt of payment.
The contractor shall provide all such required information for the current month by the 5th of the
following month. The required information shall be submitted electronically through the Department's web-
based payment tracking system (https://arizonalpa.dbesystem.com).
9.0 Goals:
The Department has not established contract goals for DBE participation in this contract. Contractors are
still encouraged to employ reasonable means to obtain DBE participation. Contractors must retain records
in accordance with these DBE specifications. The contractor is notified that this record keeping is important
to the Department so that it can track DBE participation where only race neutral efforts are employed.
10.0 Crediting DBE Participation:
10.01 General Requirements:
Only the value of the work actually performed by the DBE can be credited toward DBE
participation. Credit is given only after the DBE has been paid for the work performed.
The contractor bears the responsibility to determine whether the DBE possesses the proper
contractor's license(s) to perform the work.
The Department's certification is not a representation of qualifications and/or abilities. The
contractor bears all risks that the DBE may not be able to perform its work for any reason.
A DBE may participate as a prime contractor, subcontractor, joint venture partner with either a
prime contractor or a subcontractor, or as a vendor of materials or supplies. A DBE joint venture
partner shall be responsible for a clearly defined portion of the work to be performed, in addition to
meeting the requirements for ownership and control.
The dollar amount of work to be accomplished by DBEs, including partial amount of a lump sum
or other similar item, shall be on the basis of subcontract, purchase order, hourly rate, rate per ton,
etc., as agreed to between parties.
With the exception of bond premiums, all work must be attributed to specific bid items. Where
work applies to several items, the DBE contracting arrangement must specify unit price and
amount attributable to each bid item. DBE credit for any individual item of work performed by the
DBE shall be the lesser of the amount to be paid to the DBE or the prime contractor's bid price. If

SERIAL 15058-RFP
the amount bid by the DBE on any item exceeds the prime contractor's bid amount, the prime
contractor may not obtain credit by attributing the excess to other items.
Where more than one DBE is engaged to perform parts of an item (for example, supply and
installation), the total amount payable to the DBEs will not be considered in excess of the prime
contractor's bid amount for that item.
Bond premiums may be stated separately, so long as the arrangement between the prime
contractor and the DBE provides for separate payment not to exceed the price charged by the
bonding company.
DBE credit may be obtained only for specific work done for the project, supply of equipment
specifically for physical work on the project, or supply of materials to be incorporated in the work.
DBE credit will not be allowed for costs, such as overhead items, capital expenditures (for example,
purchase of equipment), and office items.
If a DBE performs part of an item (for example, installation of materials purchased by a Non-
DBE), the DBE credit shall not exceed the lesser of (1) the DBE's contract or (2) the prime
contractor's bid for the item, less a reasonable deduction for the portion performed by the Non-
DBE.
When a DBE performs as a partner in a joint venture, only that portion of the total dollar value of
the contract which is clearly and distinctly performed by the DBE's own forces can be credited.
The contractor may credit second-tier subcontracts issued to DBEs by non-DBE subcontractors. Any
second-tier subcontract to a DBE must meet the requirements of a first-tier DBE subcontract.
All DBE and non-DBE subcontracting activity must be reported by the contractor. This includes
lower-tier subcontracting regardless of whether or not the DBE is under contract with another
DBE.
A prime contractor may credit the entire amount of that portion of a construction contract that is
performed by the DBE's own forces. The cost of supplies and materials obtained by the DBE for
the work of the contract can be included so long as that cost is reasonable. Leased equipment
may also be included. No credit is permitted for supplies purchased or equipment leased from the
prime contractor or its affiliate(s).
When a DBE subcontracts a part of the work of its contract to another firm, the value of the
subcontract may be credited towards DBE participation only if the DBE's subcontractor is itself a
DBE and performs the work with its own forces. Work that a DBE subcontracts to a non-DBE
firm does not count towards DBE participation.
A prime contractor may credit the entire amount of fees or commissions charged by a DBE firm
for providing a bona fide service, such as professional, technical, consultant, or managerial
services, or for providing bonds or insurance specifically required for the performance of a
USDOT-assisted contract, provided the fees are reasonable and not excessive as compared with
fees customarily allowed for similar services.
10.02 Police Officers:
DBE credit will not be permitted for procuring DPS officers. For projects on which officers from
other agencies are supplied, DBE credit will be given only for the broker fees charged, and will
not include amounts paid to the officers. The broker fees must be reasonable.

SERIAL 15058-RFP
10.03 Commercially Useful Function:
As a prime contractor, a DBE shall perform a significant portion of the contract work with its own
work force in accordance with normal industry practices and Subsection 108.01 - Subletting of
Contract of the Standard Specifications.
A prime contractor can credit expenditures to a DBE subcontractor only if the DBE performs a
commercially useful function on the contract. A DBE performs a commercially useful function
when it is responsible for execution of the work of a contract and is carrying out its
responsibilities by actually performing, managing, and supervising the work involved. To perform
a commercially useful function, the DBE must also be responsible, with respect to materials and
supplies on the contract, for negotiating price, determining quality and quantity, ordering the
material, and installing (where applicable) and paying for the material itself. To determine
whether a DBE is performing a commercially useful function, the Department will evaluate the
amount of work subcontracted, industry practices, whether the amount the firm is to be paid under
the contract is commensurate with the work it is actually performing and the DBE credit claimed
for its performance of the work, and other relevant factors.
A DBE will not be considered to perform a commercially useful function if its role is limited to
that of an extra participant in a transaction contract, or project through which funds are passed in
order to obtain the appearance of DBE participation. In determining whether a DBE is such an
extra participant, the Department will examine similar transactions, particularly those in which
DBEs do not participate.
If a DBE does not perform or exercise responsibility for at least 30 percent of the total cost of
its contract with its own work force, or if the DBE subcontracts a greater portion of the work of a
contract than would be expected on the basis of normal industry practice for the type of work
involved, the Department will presume that the DBE is not performing a commercially useful
function.
When a DBE is presumed not to be performing a commercially useful function as provided above,
the DBE may present evidence to rebut this presumption. Decisions on commercially useful
function matters are subject to review by DOT, but are not administratively appealable to U.S.
DOT.
10.04 Trucking:
The Department will use the following factors in determining whether a DBE trucking company is
performing a commercially useful function. The DBE must be responsible for the management
and supervision of the entire trucking operation for which it is responsible on a particular
contract, and there cannot be a contrived arrangement for the purpose of meeting DBE goals.
The DBE must itself own and operate at least one fully licensed, insured, and operational truck
used on the contract on every day that credit is to be given for trucking.
The contractor will receive credit for the total value of transportation services provided by the
DBE using trucks it owns, insures and operates, and using drivers it employs.
The DBE may lease trucks from another DBE firm, including an owner-operator who is certified
as a DBE. The DBE who leases trucks from another DBE receives credit for the total value of the
transportation services.
The DBE may also lease trucks from a non-DBE firm, including an owner-operator. The DBE
who leases trucks from a non-DBE is entitled to credit for the total value of the transportation
services provided by non-DBE lessees not to exceed the value of transportation services provided by
DBE-owned trucks on the contract. Additional participation by non-DBE lessees results in credit
only for the fee or commission paid to the DBE as a result of the lease agreement.

SERIAL 15058-RFP
Example: DBE Firm X uses two of its own trucks on contract. It leases two trucks from DBE
Firm Y and six trucks from non-DBE firm Z. DBE credit would only be awarded for the total
value of transportation services provided by Firm X and Firm Y, and may also be awarded for
the total value of transportation services provided by four of the six trucks provided by Firm Z. In
all, full credit would be allowed for the participation of eight trucks. With respect to the other two
trucks provided by Firm Z, D BE credit could be awarded only for the fees or commissions
pertaining to those trucks Firm X receives as a result of the lease with Firm Z.
10.05 Materials and Supplies:
The Department will credit expenditures with DBEs for material and supplies as follows. If the
materials or supplies are obtained from a DBE manufacturer, 100 percent of the cost of the
materials or supplies is credited. A manufacturer is defined as a firm that operates or maintains a
factory or establishment that produces, on the premises, the materials, supplies, articles, or
equipment required under the contract, and of the general character described by the
specifications.
If the materials or supplies are purchased from a DBE regular dealer, 60 percent of the cost of
the materials or supplies is credited. A DBE regular dealer is defined as a firm that owns,
operates, or maintains a store or warehouse or other establishment in which the materials,
supplies, articles, or equipment of the general character described by the specifications and
required under the contract are bought, kept in stock, and regularly sold or leased to the public in
the usual course of business. To be a regular dealer, the firm must be an established, regular
business that engages, as its principal business and under its own name, in the purchase and sale
or lease of the products in question. A firm may be a DBE regular dealer in such bulk items as
petroleum products, steel, cement, stone or asphalt without owning, operating, or maintaining a
place of business, as provided above, if the person both owns and operates distribution
equipment for the products. Any supplementing of regular dealers' own distribution equipment
shall be by a long-term lease agreement, and not on an ad-hoc or contract-by-contract basis.
Packagers, brokers, manufacturers' representatives, or other persons who arrange or expedite
transactions are not regular dealers within the meaning of this paragraph and the paragraph
above.
With respect to materials or supplies purchased from a DBE which is neither a manufacturer nor
a regular dealer, the Department will credit the entire amount of the fees or commissions charged
by the DBE for assistance in the procurement of the materials and supplies, or fees or
transportation charges for the delivery of materials or supplies required on a job site, toward DBE
goals, provided the fees are determined to be reasonable and not excessive as compared with
fees customarily allowed for similar services. The cost of the materials and supplies themselves
may not be counted toward the DBE goal.
DBE credit for supplying paving grade asphalt and other asphalt products will only be permitted
for standard industry hauling costs, and only if the DBE is owner or lessee of the equipment and
trucks. Leases for trucks must be long term (extending for a fixed time period and not related to
time for contract performance) and must include all attendant responsibilities such as insurance,
titling, hazardous waste requirements, and payment of drivers.
11.0 Joint Checks:
11.01 Requirements:
A DBE subcontractor and a material supplier (or equipment supplier) may request permission for
the use of joint checks for payments from the prime contractor to the DBE subcontractor and the
supplier. Joint checks may be issued only if all the conditions in this subsection are met.
1. The DBE subcontractor must be independent from the prime contractor and the supplier, and
must perform a commercially useful function. The DBE subcontractor must be responsible

SERIAL 15058-RFP
for negotiating the price of the material, determining quality and quantity, ordering the
materials, installing (where applicable), and paying for the material. The DBE subcontractor
may not be utilized as an extra participant in a transaction, contract, or project in order to
obtain the appearance of DBE participation.
2. The use of joint checks will be allowed only if the prime contractor, DBE subcontractor, and
material supplier establish that the use of joint checks in similar transactions is a commonly
recognized business practice in the industry, particularly with respect to similar transactions
in which DBE's do not participate.
3. A material or supply contract may not bear an excessive ratio relative to the DBE
subcontractor's normal capacity.
4. There may not be any exclusive arrangement between one prime and one DBE in the use of
joint checks that may bring into question whether the DBE is independent of the prime
contractor.
5. Any arrangement for joint checks must be in writing, and for a specific term (for example,
one year, or a specified number of months) that does not exceed a reasonable time to
establish a suitable credit line with the supplier.
6. The prime contractor may act solely as the payer of the joint check, and may not have
responsibility for establishing the terms of the agreement between the DBE subcontractor
and the supplier.
7. The DBE must be responsible for receiving the check from the prime contractor and
delivering the check to the supplier.
8. The prime contractor cannot require the DBE subcontractor to use a specific supplier, and
the prime contractor may not participate in the negotiation of unit prices between the DBE
subcontractor and the supplier.
11.02 Procedure and Compliance:
1. Maricopa County Dept. Transportation Procurement Office must approve the agreement for
the use of joint checks in writing.
2. After obtaining authorization for the use of joint checks, the prime contractor, the DBE, and
the supplier must retain documentation to allow for efficient monitoring of the agreement.
3. Copies of canceled checks must be submitted period in which the joint check was issued.
whether or not joint checks were used. with the payment information for the Certificates of
payment must indicate
4. The prime contractor, DBE, and supplier each have an independent duty to report to the
Maricopa County Dept. Transportation Procurement Office in the case of any change from the
approved joint check arrangement.
5. Any failure to comply will be considered by the Maricopa County Dept. Transportation
Procurement Office to be a material breach of this contract and will subject the prime
contractor, DBE, and supplier to contract remedies and, in the case of serious violations, a
potential for termination of the contract, reduction or loss of prequalification, debarment, or
other remedies which may prevent future participation by the offending party.

SERIAL 15058-RFP
EXAMPLE INVOICE
Company Name
Address
Phone Number
DATE: INVOICE NUMBER:
TIME PERIOD:
TO: Maricopa County Department of Transportation
2901 West Durango Street
Phoenix, Arizona 85009-6357
MCDOT PROJECT MANAGER:
PROJECT NAME:
WORK ORDER NUMBER:
CONTRACT NUMBER:
MILESTONE CONTRACT MILESTONE COMPLETED REMAINING
AMOUNT VALUE PERCENT MILESTONE CONTRACT
COST AMOUNT
(identify either tasks or phases)
Milestone 1 $0 20% $0.00 $0.00
Milestone 2 $0 20% $0.00 $0.00
Milestone 3 $0 15% $0.00 $0.00
Milestone 4 $0 15% $0.00 $0.00
Milestone 5 $0 30% $0.00
TOTAL: 100% $0.00
CONTRACT AMOUNT COMPLETED $0.00
PREVIOUSLY BILLED $0.00
TOTAL DUE $0.00
TOTAL INVOICE $0.00
Submitted by:___________________________________________________________
Consultant
Payment Request Verification:______________________________________________
MCDOT Project Manager
Approval to Pay:________________________________________________________
MCDOT Division Head
IF THIS IS A FULL AND FINAL PAYMENT REQUEST BE CERTAIN TO INCLUDE THE REQUIRED CERTIFICATE OF

SERIAL 15058-RFP
FHWA-1273 -- Revised May 1, 2012
REQUIRED CONTRACT PROVISIONS
FEDERAL-AID CONSTRUCTION CONTRACT

SERIAL 15058-RFP

SERIAL 15058-RFP

SERIAL 15058-RFP

SERIAL 15058-RFP

SERIAL 15058-RFP

SERIAL 15058-RFP

SERIAL 15058-RFP

SERIAL 15058-RFP

SERIAL 15058-RFP

SERIAL 15058-RFP

SERIAL 15058-RFP

SERIAL 15058-RFP

SERIAL 15058-RFP

SERIAL 15058-RFP

SERIAL 15058-RFP

SERIAL 15058-RFP

SERIAL 15058-RFP

SERIAL 15058-RFP

SERIAL 15058-RFP
MARICOPA COUNTY DEPARTMENT OF TRANSPORTATION
Certificate of Performance and Payment of ALL Claims
PROJECT NAME:
hereby certifies to the Maricopa County Department of Transportation
(Name of Signer)
(MCDOT) that all lawful claims for labor, rental of equipment, material used, and any other
claims by or its subconsultants in connection with the project described in
MCDOT Contract No , have been paid.
understands that with receipt of payment for any previously invoiced amounts,
plus any retained monies, that this is a settlement of all claims of every nature and kind against MCDOT arising
out of the performance of MCDOT’S Contract No . relating to the material,
equipment and work covered in and required by the contract.
The undersigned hereby certifies that to his/her knowledge, no contractual disputes exist in regard to this contract
and that he/she has no knowledge of any pending or potential claims in regard to this contract.
Upon submission of this document and a separate invoice for any retained funds to MCDOT, invoice
processing will be completed within sixty (60) calendar days.
State of Arizona )
§
County of Maricopa )
Signed this day of , 20 .
Signature
Subscribed and Sworn to before me this day of , 20
Notary Public
My Commission Expires:

SERIAL 15058-RFP
Title VI Assurances
Maricopa County Department of Transportation
Title VI Assurances
The Maricopa County Department of Transportation The Civil Rights Restoration Act of 1987 clarified the
(herein referred to as the "Recipient"), HEREBY original intent of Congress, with respect to Title VI and
AGREES THAT, as a condition to receiving any Federal other Non-discrimination requirements (The Age
financial assistance from the U.S. Department of Discrimination Act of 1975, and Section 504 of the
Transportation (DOT}, through Federal Highway Rehabilitation Act of 1973}, by restoring the broad,
Administration and Arizona Department of Transportation, institutional-wide scope and coverage of these
is subject to and will comply with the following: non-discrimination statutes and requirements to include all
programs and activities of the Recipient, so long as any
Statutory/Regulatory Authorities portion of the program is Federally assisted.
• Title VI of the Civil Rights Act of 1964 (42 U.S.C.§
2000d et seq., 78 stat. 252}, (prohibits discrimination on Specific Assurances
the basis of race, color, national origin); More specifically, and without limiting the above general
Assurance, the Recipient agrees with and gives the
• 49 C.F.R. Part 21 (entitled Non-discrimination In following Assurances with respect to its Federal Aid
Federally-Assisted Programs of the Department of Highway Program.
Transportation-Effectuation of Title VI of the Civil
Rights Act of 1964}; 1. The Recipient agrees that each "activity,"
"facility," or "program," as defined in §§ 21.23 (b)
• 28 C.F.R. section 50.3 (U.S. Department of Justice and 21.23 (e) of 49 C.F.R. § 21 will be (with regard
Guidelines for Enforcement of Title VI of the Civil to an "activity") facilitated, or will be (with regard
Rights Act of 1964}; to a "facility") operated, or will be (with regard to
a "program") conducted in compliance with all
• 23 C.F.R. Part 200 Subchapter C-Civil Rights requirements imposed by, or pursuant to the Acts
(Title VI program implementation and related and the Regulations.
statues)
2. The Recipient will insert the following
The preceding statutory and regulatory cites hereinafter notification in all solicitations for bids, Requests
are referred to as the ':O.cts" and "Regulations," For Proposals for work, or material subject to the
respectively. Acts and the Regulations made in connection with
all Federal Aid Highway Program and, in adapted
General Assurances form, in all proposals for negotiated agreements
In accordance with the Acts, the Regulations, and other regardless of funding source:
pertinent directives, circulars, policy, memoranda and/or
guidance, the Recipient hereby gives assurances that it "The Maricopa County Department of
will promptly take any measures necessary to ensure Transportation, in accordance with the
that: provisions of Title VI of the Civil Rights
Act of 1964 (78 Stat. 252.42 U.S.C.§§
"No person in the United States shall, on the 2000d- 4} and the Regulations, hereby
grounds of race, color, or national origin, be notifies all advertisement, disadvantaged
excluded from participation in, be denied the business enterprises will be afforded full
benefits of, or be otherwise subjected to and fair opportunity to submit bids in
discrimination under any program or activity," response to this invitation and will not be
for which the Recipient receives Federal discriminated against on the grounds of
financial assistance from DOT, including the race, color, or national origin in
Federal Highway Administration. consideration for an award."

SERIAL 15058-RFP
3. The Recipient will insert the clauses of Appendix or any transference for the longer of the following
A and E of this Assurance in every contract or periods:
agreement subject to the Acts and the Regulations.
a. the period during which the property is used for
4. The Recipient will insert the clauses of Appendix a purpose for which the Federal financial
B of this Assurance, as a covenant running with assistance is extended, or for another purpose
the land, in any deed from the United States involving the provision of similar services or
effecting or recording a transfer of real property, benefits; or
structures, use, or improvements thereon or interest
therein to a Recipient. b. the period during which the Recipient retains
ownership or possession of the property.
5. That where the Recipient receives Federal financial
assistance to construct a facility or part of a 9. The Recipient will provide for such methods of
facility, the Assurance will extend to the entire administration for the program as are found by the
facility and facilities operated in connection Secretary of Transportation or the official whom
therewith. he/she delegates specific authority to give
reasonable guarantee that it, other recipients, sub-
6. That where the Recipient receives Federal financial recipients, sub-grantees, contractors, subcontractors,
assistance in the form, or for the acquisition of real consultants, transferees, successors in interest, and
property or an interest in real property, the other participants of Federal financial assistance
Assurance will extend to rights to space on, over, under such program will comply with all
or under such property. requirements imposed or pursuant to the Acts, the
Regulations, and this Assurance.
7. That the Recipient will include the clauses set
forth in Appendix C and Appendix D of this 10. The Recipient agrees that the United States has a
Assurance, as a covenant running with the land, in right to seek judicial enforcement with regard to
any future deeds, leases, licenses, permits, or any matter arising under the Acts, the Regulations,
similar instruments entered into by the Recipient and this Assurance.
with other parties:
a. for the subsequent transfer of real property
acquired or improved under the applicable
activity, project, or program; and
b. for the construction or use of, or access to,
space on, over, or under real property acquired
or improved under the applicable activity,
project or program.
8. That this Assurance obligates the Recipient for the
period during which Federal financial assistance is
extended to the program, except where the Federal
financial assistance is to provide, or is in the form
of, personal property, or real property, or interest
therein, or structures or improvements thereon, in
which case the Assurance obligates the Recipient,

SERIAL 15058-RFP
By signing this ASSURANCE, Maricopa County Department of Transportation also agrees to comply (and require any
sub-recipients, sub-grantees, contractors, successors, transferees, and/or assignees to comply) with all applicable provisions
governing Federal Highway Administration or Arizona Department of Transportation access to records, accounts,
documents, information, facilities, and staff. You also recognize that you must comply with any program or compliance
reviews, and/or complaint investigations conducted by the Federal Highway Administration or Arizona Department of
Transportation. You must keep records, reports, and submit the material for review upon request to Federal Highway
Administration, Arizona Department of Transportation, or its designee in timely, complete, and accurate way. Additionally,
you must comply with all other reporting, data collection, and evaluation requirements, as prescribed by law or detailed
in program guidance.
Maricopa County Department of Transportation gives this ASSURANCE in consideration of and for obtaining any
Federal grants, loans, contracts, agreements, property, and/or discounts, or other Federal-aid and Federal financial
assistance extended after the date hereof to the recipients by the U.S. Department of Transportation under the Federal
Highway Administration and Arizona Department of Transportation. This ASSURANCE is binding on Arizona, other
recipients, subrecipients, sub-grantees, contractors, subcontractors and their subcontractors, transferees, successors in
interest, and any other participants in the Federal Aid Highway Program the person(s) signing below is authorized to sign
this ASSURANCE on behalf of the Recipient.

SERIAL 15058-RFP
APPENDIX A
During the performance of this contract, the contractor, for itself, its assignees and successors in interest
(hereinafter referred to as the "contractor") agrees as follows:
1. Compliance with Regulations: The contractor of a contractor is in the exclusive possession of
(hereinafter includes consultants) will comply another who fails or refuses to furnish the
with the Acts and the Regulations relative to Non- information, the contractor will so certify to the
discrimination in Federally- assisted programs of Recipient, the Federal Highway Administration, or
the U.S. Department of Transportation, Federal Arizona Department of Transportation, as
Highway Administration or the Arizona appropriate, and will set forth what efforts it has
Department of Transportation, as they may be made to obtain the information.
amended from time to time, which are herein 5. Sanctions for Noncompliance: In the event of a
incorporated by reference and made a part of this contractor's noncompliance with the Non-
contract. discrimination provisions of this contract, the
Recipient will impose such contract sanctions as it
2. Nondiscrimination: The contractor, with regard to or the Federal Highway Administration or Arizona
the work performance by it during the contract, Department of Transportation, may determine to be
will not discriminate on the grounds of race, color, appropriate, including, but not limited to:
or national origin in the selection and retention of
a. withholding payments to the contractor under the
subcontractors, including procurements of
contract until the contractor complies; and/or
materials and leases of equipment. The contractor
will not participate directly or indirectly in the b. cancelling, terminating, or suspending a contract,
discrimination prohibited by the Acts and the in whole or in part.
Regulations, including employment practices
when the contract covers any activity, project, or 6. Incorporation of Provisions: The contractor will
program set forth in Appendix B of 49 CFR Part include the provisions of paragraphs one through six
21. in every subcontract, including procurements of
materials and leases of equipment, unless exempt by
3. Solicitations for Subcontractors, Including the Acts, the Regulations and directives issued
Procurements of Materials and Equipment: In all pursuant thereto. The contractor will take action with
solicitations, either by competitive bidding, or request to any subcontract or procurement as the
negotiation made by the contractor for work to be Recipient, the Federal Highway Administration, or
performed under a subcontract, including Arizona Department of Transportation may direct as a
procurements of materials, or leases of equipment, means of enforcing such provisions including
each potential subcontractor or supplier will be sanctions for noncompliance. Provided, that if the
notified by the contractor of the contractor's contractor becomes involved in, or is threatened with
obligations under this contract and the Acts and litigation by a subcontractor or supplier because of
Regulations relative to Non- discrimination on the such direction, the contractor may request the
grounds of race, color, or national origin. Recipient to enter into any litigation to protect the
interests of the Recipient. In addition, the contractor
4. Information and Reports: The contractor will may request the United States to enter into the
provide all information and reports required by the litigation to protect the interests of the United States.
Acts, the Regulations, and directives issued pursuant
thereto and will permit access to its books, records,
accounts, other sources of information, and its
facilities as may be determined by the Recipient, the
Federal Highway Administration or Arizona
Department of Transportation to be pertinent to
ascertain compliance with such Acts, Regulations,
and instructions. Where any information required

SERIAL 15058-RFP
APPENDIX E
During the performance of this contract, the contractor, for itself, its assignees, and successors in interest
(hereinafter referred to as the "contractor") agrees to comply with the following nondiscrimination
statutes and authorities; including but not limited to:
Pertinent Non-Discrimination Authorities:
• Title VI of the Civil Rights Act of 1964 (42 U.S.C. § 2000d et seq., 78 stat. 252), (prohibits discrimination
on the basis of race, color, national origin): and 49 CFR Part 21.
• The Uniform Relocation Assistance and Real Property Acquisition Policies Act of 1970, (42 U.S.C. §
4601), (prohibits unfair treatment of persons displaced or whose property has been acquired because of
Federal or Federal-aid programs and projects);
• Federal-Aid Highway Act of 1973, (23 U.S.C. § 324 et seq.), (prohibits discrimination on the basis of
sex);
• Section 504 of the Rehabilitation Act of 1973, (29 U.S.C.§ 794 et seq.), as amended, (prohibits
discrimination on the basis of disability); and 49 CFR Part 27;
• The Age Discrimination Act of 1975, as amended, (42 U.S.C. § 6101 et seq.), (prohibits discrimination on
the basis of age);
• Airport and Airway Improvement Act of 1982, (49 USC§ 471, Section 47123), as amended, (prohibits
discrimination based on race, creed, color, national origin, or sex);
• The Civil Rights Restoration Act of 1987, (PL 100-209), (Broadened the scope, coverage and applicability
of Title VI of the Civil Rights Act of 1964, The Age Discrimination Act of 1975 and Section 504 of the
Rehabilitation Act of 1973, by expanding the definition of the terms "programs or activities" to include all
of the programs or activities of the Federal-aid recipients, sub- recipients and contractors, whether such
programs or activities are Federally funded or not);
• Titles II and Ill of the Americans with Disabilities Act, which prohibit discrimination on the basis of
disability in the operation of public entities, public and private transportation systems, places of public
accommodation, and certain testing entities (42 U.S.C. §§ 12131-12189) as implemented by Department
of Transportation regulations at 49 C.F.R. parts 37 and 38;
• The Federal Aviation Administration's Non- discrimination statute (49 U.S.C. § 47123) (prohibits
discrimination on the basis of race, color, national origin, and sex);
• Executive Order 12898, which ensures discrimination against minority populations by discouraging
programs, policies, and activities with disproportionately high and adverse human health or environmental
effects on minority and low-income populations;
• Executive Order 13166, Improving Access to Services for Persons with Limited English Proficiency, and
resulting agency guidance, national origin discrimination includes discrimination because of limited
English proficiency (LEP). To ensure compliance with Title VI, you must take reasonable steps to ensure
that LEP persons have meaningful access to your programs (70 Fed. Reg. at 74087 to 74100);
• Title IX of the Education Amendments of 1972, as amended, which prohibits you from discriminating
because of sex in education programs or activities (20 U.S.C. 1687 et seq).

SERIAL 15058-RFP
TRANSCORE ITS, LLC, 15300 N. 90TH STREET, STE 750, SCOTSDALE, AZ 852860
PRICING SHEET: NIGP CODE 91842
Terms: NET 30
Vendor Number: VC0000009395
Certificates of Insurance Required
Contract Period: To cover the period ending August 31, 2021.