CTR076760_Contract_Documents_.pdf

ATTACHMENT #1

OFFER AND ACCEPTANCE

Solicitation No: BPM006754 Available online at https://app.az.gov

Rev 11/2024

OFFER

TO THE STATE OF ARIZONA:

The undersigned hereby offers and agrees to perform in compliance with all terms, conditions, specifications and amendments of this solicitation and any written exceptions in the offer. Signature also acknowledges receipt of all pages indicated in the Table of Contents.

Deloitte Consulting LLP

Offeror (Company) Name Signature of Person Authorized to Sign Offer

100 S. Mill Ave., STE 1800 Josh Nisbet 03/18/2025

Address Printed Name Date Tempe Arizona 85281 Principal City State Zip Title jnisbet@deloitte.com 916-718-8331

Email Address Phone Number jnisbet@deloitte.com

844-366-0011 Company Email Address Fax Number

By signature in the Offer section above, the Offeror certifies that the submission of the Offer did not involve collusion or other anticompetitive practices.

ACCEPTANCE OF OFFER (FOR DEPARTMENT USE ONLY)

The Contractor is now bound to perform based upon Contract Number _________________________________including all terms, conditions, specifications, amendments, etc., and the Contractor's offer as accepted by the state.

The Contractor is hereby cautioned not to commence any billable work or provide any material, service or construction under this contract until contractor receives a purchase order document.

State of Arizona

Effective this day of 20

Procurement Officer Awarded Date

Docusign Envelope ID: 5FC7E6CB-613A-4CD2-A02D-EA6612890924

May 25

CTR076760

5/1/2025 https://app.az.gov/

ARIZONA DEPARTMENT OF TRANSPORTATION

1655 W. Jackson Street, MD 100P

Phoenix, AZ 85007

Contract Amendment Summary

CONTRACTOR: DELOITTE CONSULTING AMENDMENT NO.: 1

DESCRIPTION: Capital Project Delivery System (CPDS)

Rev. 03/2025

Pursuant to the Uniform Terms and Conditions, Section 5, Contract Changes, the above referenced contract is amended. Summary of changes is as follows:

1. The Special Terms and Conditions are hereby amended to include the following:

Project Dependencies:

In accordance with A.R.S. § 18-121, A.R.S. § 18-104, Administrative Code R2-18-101, all statewide IT projects with a total cost of $25,000 or more are required to submit a Project Investment Justification (PIJ) to Arizona Department of Administration Arizona Strategic Enterprise Technology (ADOA-ASET) for review and approval prior to any expenditure of funds. Additionally, IT projects costing $1 million or those within a 10% contingency of that threshold or more are required to present at the Information Technology Authorization Committee (ITAC) for approval.

All contract awards are contingent on the Department receiving project approval from ADOA-ASET and ITAC when required. Should approval for the project associated with this contract not be granted, the Department may take any of the following actions:

1. Cancel the Contract; or

2. Cancel the Contract and re-solicit the requirements.

Additionally, should project costs exceed $5,000,000, the Department shall require the budget unit to contract with an independent third party to review and guide the technology approach, scope, estimated cost, timeline for completion and overall feasibility of the project before making recommendations to ITAC.

2. All other terms, conditions and provisions of this contract remain unchanged.

javascript:void('0')

1655 W. Jackson Street, MD 100P

Contract Amendment Summary

CONTRACTOR: DELOITTE CONSULTING AMENDMENT NO.: 2

DESCRIPTION: Capital Project Delivery System (CPDS)

Rev. 03/2025

Pursuant to the Uniform Terms and Conditions, Section 5, Contract Changes, the above referenced contract is amended. Summary of changes is as follows:

1. The Scope of Work Section 5.1.11.1. is hereby amended to the following:

The Contractor shall provide a security plan which shall be submitted to Department for review, comment and approval, within 30 days of approval of the System Detail Design deliverable. The Contractor shall then update the security plan as required upon the initiation of a project phase/release. The security plan shall detail the policies, procedures, system capabilities, work steps and other actions to be implemented to meet the security requirements for the Digital Project Delivery solution as specified in this scope of work.

2. All other terms, conditions and provisions of this contract remain unchanged.

Rev. 11/2024

STATE OF ARIZONA

1655 W. Jackson St., MD 100P

REQUEST FOR PROPOSAL

SOLICITATION NUMBER: BPM006754

DESCRIPTION: Capital Project Delivery System (CPDS) with Optional Maintenance Management System (MMS)

QUESTIONS: Inquiries regarding the solicitation are to be submitted online through the State’s e-Procurement system, Arizona Procurement Portal (APP) (https://app.az.gov/) using the Discussion Forum tab.

OFFERORS ARE STRONGLY ENCOURAGED TO READ THE ENTIRE SOLICITATION.

Kelly Greene Procurement Officer Phone: 602-712-4879 Email: kgreene@azdot.gov

This solicitation is issued in accordance with A.R.S. §41-2534 and A.A.C. R2-7-C301 et seq., Competitive Sealed Proposals.

“An Equal Opportuni ty Agency”

The Arizona 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 Americans with Disabilities Act (ADA), hereby notifies all bidders that it will affirmatively ensure that any contract entered into pursuant to this advertisement, disadvantaged business enterprises will be afforded full and fair opportunity to submit bids in response to this invitation and will not be discriminated against on the grounds of race, color, national origin in consideration for an award.

Persons that require a reasonable accommodation based on language or disability should contact ADOT’s Procurement Office by phone (602) 712-7466. Requests should be made as early as possible to ensure the State has an opportunity to address the accommodation.

Las personas que requieran asistencia (dentro de lo razonable) ya sea por el idioma o discapacidad deben ponerse en contacto con ADOT (602) 712-7466.

TABLE OF CONTENTS

Sol icitation No: BPM006754 Avai lable onl ine at

SECTION PAGE

Notice 1

Table of Contents 2

Scope of Work 3

Special Terms and Conditions 89

Uniform Terms and Conditions 108

EXHIBITS

1 - Title VI/Non-Discrimination Assurances Appendix A 126

2 - Title VI/Non-Discrimination Assurances Appendix E 127

3- Quarterly Usage Report 128

SCOPE OF WORK

1. Statement of Need

1.1. Pursuant to the Arizona Procurement Code, A.R.S. §41-2501 et seq., the State of Arizona Department of Transportation (Department), has a requirement for a qualified firm, (herein referred to as the Contractor) to provide, implement, and operate (for up to ten (10) years) a new Cloud-based Software as a Service (SaaS) Capital Project Delivery System (CPDS) that supports preconstruction management, construction management, and materials testing. Additionally, the Department may require an option for a Maintenance Management System (MMS), and an option for the extension of CPDS functionality to support the following Department business processes:

planning to programming (P2P) which support capital project identification and prioritization;

transportation programming; project financial management; consultant contract management and general project management system functionality for the Department’s transportation projects.

2. Introduction and Background

2.1. The Department is the multi-modal state-level agency responsible for providing safe and efficient transportation of goods and people within Arizona. The Department handles planning, designing, constructing, and maintaining the state highway system in Arizona, operating the Grand Canyon airport, and providing pass-through grant funding to small transit agencies within the State. In addition, the Department’s Motor Vehicle Division (MVD) provides vehicle title and registration and driver-license services statewide for the citizens of Arizona.

2.2. A key element of the Department’s mission is managing its highway construction program, including the letting and award of highway construction projects, the management and oversight of the work of construction contractors during the construction phase of this work, and the testing of materials being used on construction projects. The Department currently utilizes a set of legacy systems to manage these business processes. The new Capital Project Delivery System (CPDS) shall replace these legacy systems. Some of these systems are almost 30 years old and written in technologies which are increasingly difficult to support. There is also limited integration between the existing systems, necessitating redundant entry into various systems.

2.3. Another key element of the Department’s mission is operating and maintaining transportation infrastructure. Currently multiple non-integrated systems are utilized to track the asset inventory, asset condition and plan and manage the work performed on Department infrastructure assets.

These existing systems include the Performance Controlled System (PeCoS), the Feature Inventory System (FIS), the Level of Service (LOS) application and the Needs Based Budget (NBB) workbook.

2.4. The Department plans to implement various digital delivery initiatives with a goal of more effectively sharing and exchanging information digitally throughout the capital project delivery process. The Department sees the opportunity of replacing its capital project delivery systems and its asset inventory and maintenance management systems at the same time as a significant opportunity to enhance the digital exchange of information across these next generation systems, thus increasing the digital footprint in terms of the Department’s project delivery and asset management lifecycles.

3. General Requirements

3.1. The Contractor shall provide, implement, and support, for up to ten (10) years, a new Cloud-based

Software as a Service (SaaS) Digital Project Delivery solution consisting of a Capital Project Delivery System (CPDS) and as a Department option a new Maintenance Management System (MMS).

3.2. The new Digital Project Delivery solution shall be implemented in three (3) phases:

3.2.1. Phase 1 shall be the deployment of a Capital Project Delivery System (CPDS) to support preconstruction management, construction management and materials testing functionality.

3.2.2. Phase 2 shall be the optional implementation of a new MMS, at the discretion of the Department.

3.2.3. Phase 3 shall be the optional implementation of additional CPDS functionality to support the Department’s planning to programming (P2P) process, transportation programming processes, project finance, consultant contract management, and general project management capabilities for Department transportation projects. This shall be implemented at the discretion of the Department.

3.3. For planning purposes, the following is an approximate user count per system function:

3.3.1. Phase 1 CPDS: 300 total (approximate), 21 for preconstruction management, 275 for construction management and 88 for materials testing.

3.3.2. Phase 2, MMS: 800 users (approximate).

3.3.3. Phase 3, CPDS extension: 200 additional users (approximate) across all Phase 3 functions.

4. Specific Requirements

4.1. Phase 1 – Capital Project Delivery System (CPDS)

4.1.1. In Phase 1, the Contractor shall design, configure, test, and deploy a CPDS solution which supports the Department’s capital project delivery lifecycle from the preparation of specifications, through project letting and contract award, management of the construction phase of work and the construction contract(s), tracking of the testing of materials used on construction projects and management of the construction hand-over process.

4.1.2. Phase 1 shall be deployed in three (3) releases, with Pre-construction Management deployed as Release 1, followed by Construction Management as Release 2 and Materials Testing as Release 3.

4.1.3. The Contractor shall implement Release 1 (Pre-construction Management) within 14 months of Notice to Proceed (NTP) for Phase 1 and Release 2 (Construction Management) implemented within 18 months of NTP for Phase 1. Release 3 (Materials Testing) is targeted for implementation within 28 months of NTP for Phase 1.

4.1.4. Phase 1 of CPDS shall support, at a minimum, the functions outlined in Sections 4.1.5 through Section 4.1.7.

4.1.5. Pre-Construction Management (Phase 1, Release 1)

4.1.5.1. Support procurement of design-bid-build construction projects.

4.1.5.2. Support procurement of design-build construction projects.

4.1.5.3. Support procurement of construction projects by other alternative delivery methods including but not limited to: Progressive Design-Build, Construction Manager at Risk (CMAR), etc.

4.1.5.4. Support transfer of historical letting and award information stored in FAST, which is the Department’s current construction management system, into the new CPDS for use in letting new construction projects.

4.1.5.5. Integrate with the Department Project Master system to obtain project number and project attribute information for use in managing/tracking preconstruction processes.

4.1.5.6. Integrate with the Department Environmental Systems Research Institute (Esri) Roads and Highways environment to obtain linear referencing system (LRS) information and other attribute information about the project limits.

4.1.5.7. Integrate with the Department Geographic Information System (GIS) environment to spatially display project limits with the GIS viewer within the CPDS application.

4.1.5.8. Allow an authorized user to add additional project description and attribute information within the Preconstruction module.

4.1.5.9. Provide each project with a contract number as a unique identifier.

4.1.5.10. Allow for reuse of contract number in a re-bid but maintain the history from the initial bid via version control.

4.1.5.11. Integrate with the Department Computer-Aided Design and Drafting (CADD) environment (Bentley OpenRoads) to obtain digital design information and create initial draft Plans, Specifications, and Estimates (PS&E) packages within CPDS.

4.1.5.12. Allow an authorized user to modify the draft PS&E package including adding specialty and other line items, adjusting quantities, etc.

4.1.5.13. Provide ability to enter Federal Codes on project work to track funding sources for participating and non-participating line items.

4.1.5.14. Support division of the project into multiple sections based on changes in project funding or other project attributes.

4.1.5.15. Support utilization of the same item number in multiple sections of the project.

4.1.5.16. On a lump sum item, support break up of contractor bid items to allocate contractor price/cost to the portions of the item being paid for by different funding sources (federal, state, multiple local).

4.1.5.17. Allow contractors to bid a single item that is broken into multiple items by funding source for contract management and reimbursement billing purposes.

4.1.5.18. Support the option to bid lump sum structures individually that are rolled up into a lump sum.

4.1.5.19. Provide a workflow capability to support review and approval of the PS&E package.

4.1.5.20. Maintain a database of historical cost for the three (3) lowest responsive proposers from each project and the associated Department engineers estimate.

4.1.5.21. Store supplemental agreement pricing from each construction contract in the historical cost database.

4.1.5.22. Populate historical pricing database automatically upon approval of a supplemental agreement on a construction contract.

4.1.5.23. Allow an authorized user to prepare an engineer's estimate by looking up information in the historical cost database.

4.1.5.24. Support the generation of an initial draft estimate based on information in the database and parameters set by the engineer with the ability for the engineer to revise/adjust draft estimate as necessary. Engineers in generating draft estimates shall be able to set parameters for dates, location, quantities, etc.

4.1.5.25. Support capturing of cost of miscellaneous and specialty items so as to support future comparison of the cost of these items. Provide capability to search by name with wildcard search.

4.1.5.26. Provide the ability to bring in fuel and bituminous pricing from a third party vendor service.

4.1.5.27. Support integration with electronic rental bluebook/Pro Estimator to assist in preparation of engineers estimates.

4.1.5.28. Provide ability to integrate with a third-party estimating package to import an estimate into CPDS.

4.1.5.29. Support preparation of estimates for all phases of a project, particularly for use in evaluating contractor bids for construction work detailed in project plans.

4.1.5.30. Allow ability for designers, engineers and bid specialists to enter project estimates.

4.1.5.31. Provide ability for estimates and unit pricing to be entered or pulled into CPDS in

Excel or CSV format.

4.1.5.32. Allow authorized users to modify/update/change an estimate with each of the prior estimate versions kept for historical review/comparison with versioning capability.

4.1.5.33. Provide a workflow capability to support review and approval of engineers' estimates.

4.1.5.34. Maintain security on an engineer's estimate for a project to an authorized list of users as established by the Department Contracts and Specifications.

4.1.5.35. Manage/track prequalification of contractors. Please refer to the current Department contractor prequalification application at:

https://azdot.gov/sites/default/files/2023-11/application-for-contractor-prequalification.pdf.

4.1.5.36. Manage/track prequalification of subcontractors.

4.1.5.37. Store a list of pre-qualified contractors, approved work categories, financial limits, and other relevant contractor information.

4.1.5.38. Provide ability to prequalify prime contractors for certain work types by allowing contractors to enter an application and attachments to share financial data, equipment experience and general construction experience confidentially.

https://app.az.gov/ https://azdot.gov/sites/default/files/2023-11/application-for-contractor-prequalification.pdf https://azdot.gov/sites/default/files/2023-11/application-for-contractor-prequalification.pdf

4.1.5.39. Maintain confidentiality of prequalification information. Please refer to R17-3-204 in the Department prequalification package.

4.1.5.40. Manage and track prequalification status. Support the ability for contractors to request an extension of prequalification application and if granted by the Department, maintain prequalified status until end of extension.

4.1.5.41. Integrate with AZ360 (State of Arizona ERP system) to obtain basic vendor information and then allow for maintenance of additional Department construction specific information within the Preconstruction module. Allow for specific pre-qualification contact information, including but not limited to: name, address, email, phone, etc.

4.1.5.42. Provide an online portal capability to allow a contractor to submit initial and renewal prequalification applications.

4.1.5.43. Allow an already prequalified contractor in certain work types to apply for prequalification in additional work types.

4.1.5.44. Notify the contractor electronically of upcoming expiration of prequalification.

4.1.5.45. Provide a workflow capability to support review and disposition of a contractor's prequalification application.

4.1.5.46. Generate reports on prequalified contractor bidding activity for a specific time range including but not limited to specific projects that a contractor bid on, a specific contractor’s awards, a specific contractor’s pre-qualifications, etc.

4.1.5.47. Generate reports of projects a contractor has been awarded, and/or is working on currently as prime or subcontractor, etc.

4.1.5.48. Capture/track project partnering evaluation information.

4.1.5.49. Maintain future bid letting schedule and support publication of schedule to the

Department website. Provide for ability to regularly update information on the Department website.

4.1.5.50. Integrate with Pro Project Tracker database and Adobe Workfront to regularly update information on the website.

4.1.5.51. Provide for creating publication ready versions of the bid package.

4.1.5.52. Generate standard specifications from templates based on project funding

(Federal, State, etc.).

4.1.5.53. Publish bid opportunities to the Department website that shall make available all elements of the bid package for download.

4.1.5.54. Advertise bids through a restricted website (available to pre-qualified contractors), allowing prospective bidders to view and download Plans, Specifications and Estimates (PS&E) package. This allows for questions from contractors and the Department responses, including issuing any addenda.

4.1.5.55. Integrate with Bid Express to set-up projects on Bid Express to receive contractor proposals.

4.1.5.56. Allow contractors to request to be a plan holder for a project via contractor portal.

4.1.5.57. Support workflow for review/approval of plan holder requests.

4.1.5.58. Notify the contractor of the disposition of the plan holder request.

4.1.5.59. Integrate with Bid Express to indicate the contractor is a plan holder and can submit a bid.

4.1.5.60. Publish/maintain list of plan holders on the Department website.

4.1.5.61. Support receiving and responding to questions from bidders online.

4.1.5.62. Support preparing and publishing addenda to the Department website for access by authorized plan holders. Notify plan holders of addenda via email.

4.1.5.63. Integrate with Bid Express to provide addenda and adjust required bid response information based on addenda.

4.1.5.64. Integrate with Bid Express to receive contractor bid responses into CPDS for analysis.

4.1.5.65. Integrate with Bid Express to obtain and display in CPDS the number of bids submitted at any given time during the letting process.

4.1.5.66. Provide capability to receive contractor bid responses into CPDS, maintaining security on responses until after the due date/time.

4.1.5.67. Allow the contractor to revise bid response until bid due date/time.

4.1.5.68. Automatically conduct analysis of bids received.

4.1.5.69. Provide comparison of bidders against each other and in comparison to engineers' estimates. Rank proposers based on total bid price.

4.1.5.70. Automatically identify potential bid anomalies (unbalanced bids, etc.) based on user defined business rules.

4.1.5.71. Provide for designation of apparent selected bidder and publication of this information to the Department website.

4.1.5.72. Provide for contractor submission of DBE plan online.

4.1.5.73. Support analysis of DBE commitments against project goals.

4.1.5.74. Allow contractors to submit all required pre-award documentation online

(insurance certificate, proof of workers comp, performance bonds, etc.).

4.1.5.75. Provide for generation of construction contracts using templates within the system.

4.1.5.76. Provide workflow for the Department internal review of construction contract package.

4.1.5.77. Document Board award of construction contract.

4.1.5.78. Support routing of contract to contractor for signature.

4.1.5.79. Integrate with DocuSign to support contract signing.

4.1.5.80. Support contract signature routing and processing within CPDS.

4.1.5.81. Integrate with AZ360 to establish encumbrance for construction contract.

4.1.5.82. Generate post award letters within the system and route to contractors electronically.

4.1.5.83. Provide capability to transfer contractor information to the construction module, converting bid items into pay items.

4.1.5.84. Integrate with Adobe Workfront to update key milestone dates during the preconstruction process.

4.1.5.85. Provide capability to integrate with PIRT (Project Information Retrieval Tool) or provide a dashboard that can retrieve project data from multiple sources.

4.1.6. Construction Management (Phase 1, Release 2)

4.1.6.1. Integrate with Preconstruction module to transfer contract information including but not limited to contract attributes, pay items, etc., to support managing of construction contracts.

4.1.6.2. Support entry by the Department staff and/or contractor of key contact information for the Department and contractor.

4.1.6.3. Generate award letters to provide to contractor via email and contractor portal.

4.1.6.4. Enter award/time date to start contract time clock based on award letter being generated.

4.1.6.5. Store start memo/project status memo and record date of start memo.

4.1.6.6. Record subcontractors working on projects and items on which they will be working.

4.1.6.7. Record bond requirements and receipt of any required bonds.

4.1.6.8. Record receipt of insurance certificates at contract start including policy coverage information and expiration date(s).

4.1.6.9. Track expiration of insurance certificates over life of contract and flag when certificates are within 30 days of expiring. Provide for updating/recording receipt of new insurance certificate(s).

4.1.6.10. Integrate with the Manpower application to provide the construction project/contract information required in the Manpower application to allow for forecasting of construction inspection staffing needs for the project.

4.1.6.11. Integrate with the Consultant Invoicing application to provide the construction project/contract information required in the Consultant Invoicing application to allow for consultant inspectors to be assigned to the project, charge time and invoice for work performed.

4.1.6.12. Integrate with the consultant contract management module within CPDS during Phase 3 to provide construction project information needed to support consultant resource forecasting, resource assignment, time tracking and invoicing for consultant inspectors on the project.

4.1.6.13. Provide ability to manage and track required field inspections.

4.1.6.14. Support assigning tasks to inspectors and recording completion of the task.

4.1.6.15. Provide ability to document inspector diaries.

4.1.6.16. Record and differentiate between a working day and a non-working day, and shall include reason(s) for the non-working day (weather, holiday, weekend).

4.1.6.17. Record time stop and time re-start after a stoppage.

4.1.6.18. Support capture of inspector daily work reports via workstation or laptop with ability to utilize laptop offline with automated sync upon returning to office.

4.1.6.19. Support capture of inspector daily work reports via mobile application with automated syncing for work performed offline.

4.1.6.20. Support capture of GPS location where work was performed.

4.1.6.21. Track materials, equipment and workers onsite.

4.1.6.22. Record weather and other site condition information.

4.1.6.23. Record work performed by contractor by pay item and location.

4.1.6.24. Support recording of work performed by either contractor or subcontractor and be able to differentiate as to who performed the work.

4.1.6.25. Record receipt of materials on the job site.

4.1.6.26. Support the implementation of e-ticketing by providing the ability to electronically receive material tickets from suppliers (e.g., asphalt, concrete) via standard application program interface (API). API shall support integration with multiple material suppliers and external contractor ticketing systems.

4.1.6.27. Support recording of various measurements including calculation of dimensions.

4.1.6.28. Capture inspector notes including the option to capture a location reference to which note is tied.

4.1.6.29. Provide sketching capability including ability to tie sketches to pay items/locations.

4.1.6.30. Support attachment of photos including GPS location.

4.1.6.31. Support attachment of videos including GPS location.

4.1.6.32. Support attachment of documents.

4.1.6.33. Provide earthwork calculation function and link calculations to associated pay item(s).

4.1.6.34. Provide workflow for review and approval of inspector daily work reports.

4.1.6.35. Track independent assurance samples pulled on a project.

4.1.6.36. Generate an automated alert when an independent assurance test is needed based on sampling guidelines.

4.1.6.37. Record samples pulled by GPS location.

4.1.6.38. Prepare an electronic sample card for each unique sample which identifies specific attributes in regards to the sample, including but not limited to: the project, date sample was taken, material sampled, location of sample, material source, and whether the sample is an independent assurance sample or quality assurance and quality control (QA/QC) sample, etc.

4.1.6.39. Prepare an initial list of tests to be performed based on sampling guidelines.

4.1.6.40. Integrate sample card with Materials Testing module of system upon transfer of sample to Materials lab personnel.

4.1.6.41. Maintain a log of samples and status of each sample.

4.1.6.42. Provide inquiry access to test results upon completion/approval of test via integration with Materials Testing module of the system.

4.1.6.43. Support certification of compliance via a materials certification or sufficient passing tests before allowing items to be paid in progress estimate.

4.1.6.44. Provide ability to designate pay items that are subject to bituminous price adjustments and to maintain the business rules associated with these adjustments.

4.1.6.45. Maintain a database of terminal fuel prices (terminal, effective date, fuel type, price).

4.1.6.46. Provide ability to update terminal prices via electronic file from a third party service via an application program interface.

4.1.6.47. Calculate price adjustments as part of progress estimate based on terminal prices and appropriate business rules.

4.1.6.48. Generate draft of contractor pay estimate based on approved daily diaries.

Progress estimates are generated on a monthly basis.

4.1.6.49. Lock progress pay estimates to certain dates based on the Department business rules and have all future inspection reports/approvals after the lock date roll to the next progress estimate.

4.1.6.50. Allow authorized users (Resident Engineer or other Construction staff) to make adjustments to the draft estimate.

4.1.6.51. Provide ability to electronically share final draft of progress estimate with contractor for their review.

4.1.6.52. Provide workflow for review and approval of progress estimate (Resident Engineer, contractor, State Construction Office, the Department Finance team).

4.1.6.53. Integrate with AZ360 to generate a draft accounts payable voucher.

4.1.6.54. Track and display status of payments via integration with AZ360 (CPDS to receive update when payment is made with warrant number/ Automated Clearing House (ACH) information and date of payment, etc.).

4.1.6.55. Allow authorized users (Resident Engineer or other Construction staff) to prepare a draft supplemental agreement.

4.1.6.56. Provide the ability to add a pay item.

4.1.6.57. Provide ability to modify an existing pay item to change quantities.

4.1.6.58. Provide a workflow capability to electronically route draft supplemental agreement to contractor for review of draft.

4.1.6.59. Capture contractor comments on draft supplemental agreement.

4.1.6.60. Provide a workflow capability to route supplemental agreement for review and approve internally and for approval by the contractor.

4.1.6.61. Initiate request for budget adjustment where the amount of proposed supplemental agreement exceeds available contract contingency. Place supplemental agreement on hold until budget request is approved.

4.1.6.62. Provide eSignature capability within the CPDS solution for approval of supplemental agreements.

4.1.6.63. Integrate with DocuSign to support review/approval of supplemental agreements and store signed documents as an attachment within the system.

4.1.6.64. Provide collaboration area /contractor portal to allow contractor to submit questions/Request for Information (RFI) and provide the Department the ability to respond to those questions/comments within the format.

4.1.6.65. Provide ability to connect a contractor RFI to any future supplemental agreements or claims.

4.1.6.66. Provide an RFI log and track the Department response and any contractor follow-up.

4.1.6.67. Provide ability for documenting potential claim situations.

4.1.6.68. Track claim submitted by a contractor, linking this claim to any potential claim documentation created by the contracotr or any RFIs submitted by the Department and the Department's responses to these RFIs.

4.1.6.69. Record proposed resolution of claim.

4.1.6.70. Provide a workflow for internal review and approval of the resolution.

4.1.6.71. Support linking of claim information to draft of any supplement agreement developed to document claim resolution.

4.1.6.72. Support management and monitoring of contractor compliance with various contract requirements.

4.1.6.73. Integrate with DOORS (B2GNow) which is the Department’s system for

Disadvantaged Business Enterprise (DBE) and on-the-job training (OJT) reporting, and UTRACS which is Arizona’s Transportation Business Portal, to obtain contractor compliance information and status in terms of DBE reporting and OJT requirements.

4.1.6.74. Integrate with the LPT Tracker, the Department’s application for tracking certified payrolls, to obtain contractor compliance information in terms of certified payrolls.

4.1.6.75. Provide a mechanism via contractor portal for contractors to report payments to subs by the 15th of each month for the prior month. Provide a reminder notification to the contractor prior to the due date if not yet entered based on user configurable business rules. Provide alert to designated Department construction staff if the contractor does not complete on-time.

4.1.6.76. Generate penalty as a credit item on progress estimate based on the Department business rules if the contractor is late in reporting (penalty is currently $5,000).

4.1.6.77. Provide ability for contractors to submit certified payroll information.

4.1.6.78. Provide ability for subcontractors to submit certified payroll information.

4.1.6.79. Provide ability for contractors to submit on-the-job-training records.

4.1.6.80. Perform checks to confirm that contractors are meeting DBE goals.

4.1.6.81. Perform checks to confirm that contractors are complying with OJT utilization targets.

4.1.6.82. Perform checks to confirm that contractors are meeting various requirements, including but not limited to: Prevailing wage (Davis-Bacon Act) requirements.

4.1.6.83. Perform checks to confirm that contractors are meeting various requirements, including but not limited to: Bonding requirements.

4.1.6.84. Perform checks to confirm that contractors are meeting various requirements, including but not limited to: Insurance requirements.

4.1.6.85. Manage all project records and documentation, including emails, photos, videos, PDF files, electronic daily reports, and others.

4.1.6.86. Provide ability to view Building Information Models (BIM) through CPDS in addition to the plan sheets.

4.1.6.87. Provide ability to upload documents into the system and associate the document with a particular project record (daily diary, supplemental agreement, etc.).

4.1.6.88. Provide ability to integrate with the Department’s document management solution (OnBase) to link/associate a document stored in OnBase with an electronic project record in CPDS.

4.1.6.89. Provide a project risk register.

4.1.6.90. Provide a project issues log.

4.1.6.91. Provide a project decision log.

4.1.6.92. Provide an action item log.

4.1.6.93. Support tracking of items in each of the project logs and any changes in the status of items including involved parties (accountable, responsible, others) and ball in court information.

4.1.6.94. Allow for storing of contractor's project schedule as a document within the project records.

4.1.6.95. Allow for importing of the contractor's project schedule from Primavera P6 for viewing within the schedule tool within CPDS.

4.1.6.96. Track key milestone dates including but not limited to: Award Date, Contract Execution Date, Start Date, Substantial Completion Date, Financial Close Date, Project Close Date.

4.1.6.97. Track other key dates for activities within the construction phase within CPDS.

These key dates can be either entered /maintained by authorized Department staff or extracted from contractor schedules imported into CPDS.

4.1.6.98. Provide tracking of project float time.

4.1.6.99. Track delay damages for milestone events during the project (for example must have the road re-opened by 5:00 a.m. Monday morning), Calculate any damages due to missed dates/times per contract requirements and populate as a credit item on the next progress estimate.

4.1.6.100. Store stop memo/project status memo and record date of project completion.

4.1.6.101. Support preparation of semi-final contractor pay estimate including routing of estimate via electronic workflow for review and approval.

4.1.6.102. Record final contract quantities including recording/tracking of any required adjustments.

4.1.6.103. Provide for a contract close out check list with workflow to route to different parties responsible for completing steps on the checklist.

4.1.6.104. Support preparation of final contractor voucher and routing of final voucher via workflow for review and approval based on the Department business rules.

4.1.6.105. Provide ability to compile, maintain, and track contractor performance scorecard.

4.1.6.106. Integrate with Esri Roads and Highways and planned Maintenance Management

System in Phase 2 to provide As-Built asset inventory information for import into the Department asset inventory systems.

4.1.6.107. Integrate with the Bentley suite of tools to provide the ability to import asset inventory information using pre-defined information standards and APIs.

4.1.6.108. Provide a project dashboard with project budget and financial status in a single view. Dashboard shall have a map view to allow for selecting a project.

Dashboard shall also support searching by multiple criteria, including but not limited to: (project number, project description, contract number, contractor, project type, the Department resident engineer, etc.).

4.1.6.109. Generate a report of all projects in a final state where the project has not yet been sent to the final voucher; filter this report by various parameters such as district, the Department resident engineer, contractor, etc.

4.1.6.110. Generate a report of completed contracts for a user-defined period of time.

4.1.7. Materials Testing (Phase 1, Release 3)

4.1.7.1. Provide an end-to-end laboratory information management system (LIMS) capability that tracks a sample from the time it is taken in the field, through being logged in at the lab and all tests performed and logged on that sample.

4.1.7.2. Support independent assurance testing for a construction project.

4.1.7.3. Support QA/QC testing for a construction project.

4.1.7.4. Support correlation testing for a construction project.

4.1.7.5. Support tracking of testing performed that is not specifically related to the construction phase of the project (as an example geotechnical testing pre-design, etc.).

4.1.7.6. Support tracking of tests performed for an external customer to allow for billing back of the third party. The system shall generate a list of tests performed for an external customer for a designated period of time to serve as support for billing.

4.1.7.7. Support tracking of tests performed by a third party as part of a project which may be billed back to a contractor (for example referee testing).

4.1.7.8. Support performance of proficiency testing samples (American Association of State Highway and Transportation Officials (AASHTO), Cement and Concrete Reference Laboratory (CCRL), Western Cooperative Test Group, etc.).

4.1.7.9. Track request for new asphalt and concrete mix designs and use of mix designs on projects, including tracking historical mix designs and validity of mix designs.

4.1.7.10. Capture history of changes to mix design - what changed and when it changed.

4.1.7.11. Maintain an online library of mix design tolerances including those for target changes.

4.1.7.12. Validate mix designs based on approved mix design tolerances.

4.1.7.13. Allow contractors to submit mix design requests electronically via portal, with notification to appropriate Construction project personnel.

4.1.7.14. Provide work flow for review/approval of mix designs.

4.1.7.15. Link aggregate quality test results to mix design to confirm all required testing has been performed.

4.1.7.16. Support capture of verification test results for a mix design. Capture the

Department verification of mix design properties based on test results.

4.1.7.17. Link performance history to mix design by linking samples pulled during the project.

4.1.7.18. Provide ability to link to the Department’s pavement management system for long-term performance monitoring via GPS location of samples taken.

4.1.7.19. Integrate with Esri Roads and Highways and MMS application to allow for viewing of historical mix design information for a road network segment or area of interest.

4.1.7.20. Provide for the categorization of mix designs by plant.

4.1.7.21. Support the search of mix designs by various parameters including mix design, material, material source, asphalt plant, projects used on, etc.

4.1.7.22. Maintain a list of approved plants including history.

4.1.7.23. Provide work flow for review/approval of plants.

4.1.7.24. Maintain a list of approved products including history.

4.1.7.25. Store different versions of products based on validity dates.

4.1.7.26. Provide for electronic submission of approved product requests with supporting documentation.

4.1.7.27. Provide a work flow for review/approval of approved product requests.

4.1.7.28. Maintain a list of approved material sources (quarries, etc.) including history.

4.1.7.29. Support electronic request for approval of material source including environmental clearance.

4.1.7.30. Track status of environmental review/ clearance of potential material source.

4.1.7.31. Support publication of approved sources to the Department website (currently on the Environmental web page). List shall be able to be published on demand, on a specific schedule, or when information changes. Please refer to:

https://azdot.gov/sites/default/files/2023-05/Cleared-Material-Sources-List.pdf.

4.1.7.32. Provide ability to track inspections of labs and their approvals for testing materials for the Department. Please refer to the following link for more information on the Department's Laboratory Inspection program:

https://azdot.gov/business/engineering-and-construction/construction/laboratory-inspection-program.

4.1.7.33. Maintain online sampling guidelines for a wide range of materials used on a construction project.

4.1.7.34. Allow for the specification of tests to be performed on each material and the number of tests required based on quantities of materials used or placed.

4.1.7.35. Maintain online guidelines for correlation of tests by material and test type.

4.1.7.36. Maintain history of changes to guidelines with effective dating.

https://app.az.gov/ https://azdot.gov/sites/default/files/2023-05/Cleared-Material-Sources-List.pdf https://azdot.gov/business/engineering-and-construction/construction/laboratory-inspection-program https://azdot.gov/business/engineering-and-construction/construction/laboratory-inspection-program

4.1.7.37. Maintain an electronic sample card for each unique sample that shall identify specific attributes about the sample including but not limited to: the project, date sample was taken, material sampled, location of sample, material source, and whether the sample is an independent assurance sample or QA/QC sample, etc.

4.1.7.38. Support assigning a sample to multiple projects.

4.1.7.39. Generate a list of tests to be performed on a sample based on the sampling guidelines.

4.1.7.40. Ensure the system is configurable to support changes to test criteria.

4.1.7.41. Allow an authorized user to modify the system generated list of tests to be performed (add a test, remove a test).

4.1.7.42. Support splitting the sample into multiple sub-samples as required for tracking performance of tests but maintaining all test results together under the original parent sample.

4.1.7.43. Allow lab supervisor or other authorized user to assign samples to lab staff for testing.

4.1.7.44. Allow lab supervisor or other authorized user to designate a sample for priority testing.

4.1.7.45. Provide for a workflow which routes test assignments to the assigned lab staff member.

4.1.7.46. Provide an online work queue for each lab staff member which shows the work assigned to them in priority order.

4.1.7.47. Allow for a different technician, other than the one assigned to a test, to perform a test.

4.1.7.48. Capture technician who performs the test and the date and time test is performed.

4.1.7.49. Provide a window/form in the system to capture test results for each test as identified in the Department standard specifications and sampling guide, Please refer to https://azdot.gov/business/engineering-and-construction/construction/manuals/materials-testing-manual.

4.1.7.50. Provide the ability to create a new form for a new test, and include validation for the test fields (for pass/fail and incentive/disincentive calculations) with limited to no programming required. Strong preference is for this to be configurable by a system administrator with no programming required.

4.1.7.51. Compute test results based on required input entered by technician from values generated by testing device and based on calculations, display results and determine if test is a pass or fail.

4.1.7.52. Provide capability to interface test results directly from test equipment where this capability is available from test equipment. Allow for technicians to override imported values if required.

4.1.7.53. Provide ability to allow for the Department fillable testing cards as electronic forms in the system. Current Department forms are available here:

https://azdot.gov/business/engineering-and-construction/materials/the Department-forms-fillable-testing-cards-laboratory-and-field.

4.1.7.54. Support documentation storage related to a test and the link back of this documentation to the test results.

4.1.7.55. Provide a work flow for review and approval of test results by the lab supervisor.

https://app.az.gov/ https://azdot.gov/business/engineering-and-construction/construction/manuals/materials-testing-manual https://azdot.gov/business/engineering-and-construction/construction/manuals/materials-testing-manual https://azdot.gov/business/engineering-and-construction/materials/adot-forms-fillable-testing-cards-laboratory-and-field https://azdot.gov/business/engineering-and-construction/materials/adot-forms-fillable-testing-cards-laboratory-and-field

4.1.7.56. Integrate with the construction management module of CPDS to transmit results of tests back to project and update project sample/test log with test results when test result is approved.

4.1.7.57. Notify project team electronically (email, notification in CPDS) in event of failing test.

4.1.7.58. Determine acceptability of correlation tests based on QA/QC standards.

4.1.7.59. Notify appropriate stakeholders (email, notification in CPDS) of a non-correlating test (project team, regional materials, acceptance lab performing test, etc.).

4.1.7.60. Maintain correlation history and statistics to allow for adjustment of frequency of testing.

4.1.7.61. Maintain history and statistics for acceptance testing to allow for consideration of adjustments of frequency of testing.

4.1.7.62. Support the recording of test results performed by the contractor.

4.1.7.63. Allow for upload of contractor test results via contractor portal by uploading a file that conforms to a standard application program interface (API).

4.1.7.64. Allow for import of contractor test results via an interface using a standard application program interface (API).

4.1.7.65. Integrate with Esri Roads and Highways and MMS application to allow for viewing of historical test results for a specific road network segment or area of interest.

4.1.7.66. Support acceptance of products planned for use on projects based on manufacturer and/or approved third party certifications.

4.1.7.67. Integrate with the construction management module of CPDS to record certifications in project records and update project sample/test log.

4.1.7.68. Provide ability to attach support documentation to a request for acceptance based on certification.

4.1.7.69. Perform materials certification for a construction project, ensuring sufficient tests have been performed based on quantities of materials utilized/placed on a project. Highlight discrepancies on an ongoing basis throughout the project to facilitate mitigation of the issue.

4.1.7.70. Provide comparison of independent assurance and QA/QC test results for a project.

4.1.7.71. Flag test results where the QA/QC test result does not correlate with Independent Assurance test results; Notify appropriate Department staff based on business rules.

4.1.7.72. Generate Payment Factor reports and provide them to contractors via contractor portal to notify contractors as to the amount of their incentive to be paid based on quality of material placed on the project.

4.1.7.73. Support calculation and analysis of running average specification requirements for concrete and asphalt tests where both specifications need to be met. (For example, a Materials Coordinator may keep multiple spreadsheets to track multiple concrete samples. Provide the ability to also filter this analysis by mix design.)

4.1.8. CPDS Phase 1 Integrations

4.1.8.1. Design, develop, test and deploy all integration points identified in subsections

4.1.5 through 4.1.7.

4.1.8.2. Integrate with the Department’s OKTA environment to support single sign-on to

CPDS.

4.1.8.3. Integrate with the Department data warehouse environment to populate the data warehouse with applicable construction contract information.

4.1.8.4. In addition to the integration requirements identified in subsections 4.1.5 to 4.1.7, provide for a reserve of ten (10) additional interfaces of medium…