Loading...
The URL can be used to link to this page
Your browser does not support the video tag.
Home
My WebLink
About
Contract 62240
CSC No. 62240 THE CITY OF FORT WORTH, TEXAS CONTRACT FOR THE CONSTRUCTION OF SCADA SYSTEM REPLACEMENT FORTWORTH. City Project No. 103086 Mattie Parker David Cooke Mayor City Manager Chris Harder P.E. Director, Water Department Prepared for The City of Fort Worth Water Department March 21, 2024 Arcadis U.S., Inc. 420 Throckmorton Street, Suite 200 Fort Worth, Texas 76102 (817) 502-1165 Rosser R. Standifer, P.E. (No. 92755) POARCADIS CONFORMED INCORPORATING ADDENDUM NO. 1 THROUGH NO. 9 OFFICIAL RECORD CITY SECRETARY FT. WORTH, TX OF TfX Z� / ROSSER R. STANDIFER ...i ....92755 i1`1 ASS ONA� EO \�� ++THIS PAGE INTENTIONALLY LEFT BLANK++ 00 00 00 TABLE OF CONTENTS Page 1 of 4 SECTION 00 00 00 TABLE OF CONTENTS* Document provided is distributed to Prequalified Offerors following submittal of Section 00 23 13 — Non -Disclosure Agreement (NDA), for use in preparing a Competitive Sealed Proposal. Prequalified Offerors may share document content with subconsultants and subcontractors subject to NDA requirements. DIVISION 00 — GENERAL CONDITIONS 0005 10 Mayor and Council (M&C) Communication 0005 15 Addenda 0011 15 Notice to Offerors 0021 13 Prequalification Instructions 0021 15 Instructions to Offerors 0023 13 Non -Disclosure Agreement 0035 13 Conflict of Interest Affidavit 0042 10 Proposal 0043 15 Proposal Surety (Bid Bond) 00 43 37 Vendor Compliance to State Law Non -Resident Bidder 00 45 26 Contractor Compliance with Worker's Compensation Law 00 45 42 Business Equity Goal CSP 00 46 12 Offeror Statement of Qualifications 00 52 45 Agreement** 0061 13 Performance Bond 0061 14 Payment Bond 0061 19 Maintenance Bond 0061 25 Certificate of Insurance 00 72 00 General Conditions 00 73 00 Supplementary Conditions DIVISION 01— GENERAL REQUIREMENTS 01 11 13 01 1416 CITY OF FORT WORTH September 16, 2024 Summary of Work Coordination with City's Operations SCADA System Replacement 103086 00 00 00 TABLE OF CONTENTS Page 2 of 4 01 1419 Use of Site 0122 13 Measurement and Payment Contract 01 26 00 Modification Procedures Schedule 01 29 73 of Values 01 29 76 Progress Payment Procedures Project 013113 Coordination 01 31 19.23 Progress Meetings 01 31 26 Electronic Communication Protocols 01 32 16 Progress Schedule 01 3300 Submittal Procedures 01 70 00 Mobilization and Remobilization 0177 19 Closeout Requirements 01 78 23 Operations and Maintenance Data 01 78 36 Warranties 01 78 39 Project Record Documents DIVISION 40 — PROCESS INTERCONNECTIONS 4061 13 SCADA System General Provisions 40 61 21 SCADA System Factory Acceptance Testing 40 61 23 SCADA System Field Assessment, Testing, and Start -Up 40 61 26 SCADA System Training 40 68 63 SCADA System Programming and Configuration CITY OF FORT WORTH SCADA System Replacement September 16, 2024 103086 00 00 00 TABLE OF CONTENTS Page 3 of 4 APPENDICES APPENDIX A TEXAS SALES AND USE TAX EXEMPTION CERTIFICATE APPENDIX GC 6.07 WAGE RATES ATTACHMENTS Attachment 1 PLC and HMI Configuration Standards Attachment 2 City -furnished SCADA Software and Licenses Attachment 3*** Existing HMI Databases Attachment 4 Existing HMI Screens Attachment 5 * * * Existing Reports Attachment 6 Existing WTP PLC Systems Table Attachment 7 SCADA Assets Responsibility Matrix Attachment 8 Sample Functional Control Narrative (FCN) Template * The Contract Documents are Conformed with Addendum No. 1 and Addendum No. 2 changes only. Copies of Addendum No. 3 through No. 9 are provided inside the cover for ease of reference. * * The Agreement section has been modified by mutual agreement of the parties and incorporated into the Contract Documents for execution. *** Attachment 3 and Attachment 5 will be provided as Excel (*.xlsx) files to the Successful Offeror only CTTY OF FORT WORTH SCADA System Replacement September 16, 2024 103086 00 00 00 TABLE OF CONTENTS Page 4 of 4 ++THIS PAGE INTENTIONALLY LEFT BLANK++ CTTY OF FORT WORTH SCADA System Replacement September 16, 2024 103086 City of Fort Worth, Texas Mayor and Council Communication DATE: Tuesday, October 15, 2024 REFERENCE NO.: **M&C 24-0853 LOG NAME: 60WATER SCADA REPLC REMONT SUBJECT: (ALL) Authorize Execution of Contract with Remont Engineering & Design Group, LLC in the Amount Not to Exceed $8,233,836.00 for Construction of Fort Worth Water SCADA Replacement and Adopt Appropriation Ordinances to Effect a Portion of Water's Contribution to the Fiscal Years 2025-2029 Capital Improvement Program RECOMMENDATION: It is recommended that the City Council: 1. Authorize execution of a contract with Remont Engineering & Design Group, LLC in the amount not to exceed $8,233,836.00 for construction of the Fort Worth Water SCADA Replacement project (City Project No. 103086); 2. Adopt the attached appropriation ordinance increasing estimated receipts and appropriations in the Water & Sewer Capital Projects Fund in the amount of $8,595,336.00, from available PayGo Residuals in the Water and Sewer Capital Projects Fund, for the purpose of funding the SCADA Replacement project (City Project No. 103086); and 3. Adopt the attached appropriation ordinance adjusting estimated receipts and appropriations in the Water & Sewer Revenue Bonds Series 2024 Fund by increasing estimated receipts and appropriations in the SCADA Replacement project (City Project No. 103086) in the amount of $850,500.00 and decreasing estimated receipts and appropriations in the Commercial Paper project (City Project No. UCMLPR) by the same amount to effect a portion of Water's Contribution to the Fiscal Years 2025-2029 Capital Improvement Program. DISCUSSION: In November of 2020, Mayor & Council Communication (M&C) 20-0833, the City Council authorized execution of an agreement with Arcadis US, Inc. to prepare engineering, performance and contractual standards and specifications to be incorporated into a Request for Proposals for the replacement of the existing Supervisory Control and Data Acquisition (SCADA) system for the Water Department. The Water Department utilizes a SCADA system to monitor and control the water treatment and distribution facilities along with remotely located sanitary sewer lift stations. The existing SCADA system, initially installed in 1987, utilizes proprietary components, that are no longer manufactured and in need of replacement. The construction project was advertised for bid on March 21 and March 28, 2024, in the Fort Worth Star - Telegram. On June 13, 2024, seven proposals were received. Three proposals complied with the Diversity and Inclusion Department/Business Equity Division published procedures and were allowed to be scored. The evaluation panel consisted of individuals from across the Water Department and a Business Equity representative. A scoring matrix was established detailing specific needs for this best value project. Total points available in the matrix were 100, with 50\% based on price, 20\% based on schedule, and 30\% based on technical qualifications. The firms' final scores are listed in the table below. Propose Evaluation Criteria A I B I C I D I E I Total Score Remont Engineering & Design Group, LLC Controls Panel USA, Inc. 9.50 8.75 9.63 18.52 24.25 0.53 1.20 1.01 5.89 50.00 Tesco Control, LLC 7.64 Prime Controls, LP Vertech Industrial Systems, LLC Wunderlich-Malec Systems, Inc. Revere Control Systems, Inc Best Value Criteria: 70.65 671.310% 8.47 7.63 13.81 10.01 47.56 Proposers were considered non- responsive by the Diversity and Inclusion Department/Business Equity Division for failure to comply with published procedures. A= Project approach which includes general approach narrative, organizational chart, QA/QC program, project controls, and safety program. B= Firm experience which includes depth of project experience, firm certification & licenses, firm qualifications, and firm local staffing and response. C= Key personnel which will be scored based on quality and completeness of the key personnel and key subcontractor' resumes presented. D= Contract time and schedule level of details. E=Total of base contact proposal items. Based on the criteria above, Remont Engineering & Design Group, LLC was determined to offer the best value. This M&C is also funding the Water Information Technology equipment purchases of servers, Fiber Chanel switches, storage, firewalls, work stations and tablets, cyber security suite, licensing, SequelData Pro services, and other equipment to support the SCADA upgrade in the amount of $1,212,000.00. It is the practice of the Water Department to appropriate its CIP plan throughout the Fiscal Year (FY), instead of within the annual budget ordinance, as projects commence, additional funding needs are identified, and to comply with bond covenants. The actions in the M&C will amend the City of Fort Worth's Fiscal Year 2025-2029 Capital Improvement Program as follows: 60SCADA Replac Remont Capital FY2025 CIP Revised Budget Change Fund Project Name Appropriations Authority (Increase/Decrease) FY2025 Name Budget 56022- W&S 103086 — Rev SCADA $0.00 This M&C $850,500.00 $850,500.00 Bonds REPLACEMENT Series PROJECT 2024 56002- 103086 — W&S SCADA $0.00 This M&C $8,595,336.00 $8,595,336.00 Capital REPLACEMENT Projects PROJECT Funding is currently available in the Commercial Paper project within the W&S Rev Bonds Series 2024 Fund and in the Unspecified All -Funds project within the W&S Capital Projects Fund for the purpose of funding this project. Funding for the SCADA REPLACMENT PROJECT is depicted below: FUND Existing Additional project Total* Appropriations Appropriations W&S Capital Projects -Fund $791,992.00 $8,595,336.00 $9,387,328.00 56002 W&S Rev Bond Bonds Series $1,875,097.00 $0.00 $1,875,097.00 Fund 56019 W&S Rev Bond Bonds Series $32,000,000.00 $850,500.00 $32,850,500.00 Fund 56022 Project Total 1 $34,667,089.00I $9,445,836.00I$44,112,925.00 *Numbers rounded for presentation purposes. Business Equity: The Business Equity Division placed a 5 percent business equity goal on this contract. Red Group Inc., submitted a Prime Waiver Form, which is in accordance with the City's Business Equity Ordinance. Red Group, Inc., will be self -performing the entire scope of the contract. This project is located in ALL COUNCIL DISTRICTS. FISCAL INFORMATION / CERTIFICATION: The Director of Finance certifies that funds are currently available in the Unspecified All -Fund project within W&S Capital Projects Fund and in the Commercial Paper project with in the W&S Rev Bonds Series 2024 Fund and upon approval of the above recommendations and adoption of the attached appropriation ordinances, funds will be available in the W&S Capital Projects Fund and the W&S Rev Bonds Series 2024 Fund for the SCADA REPLACEMENT PROJECT. Prior to any expenditure being incurred, the Water Department has the responsibility of verifying the availability of funds. FUND IDENTIFIERS (FIDs): TO Fund Department Account Project ProgramActivity Budget Reference # Amount ID ID Year (Chartfield 2) FROM Fund Department Accoun� Project Program�Activity' Budget Reference # AmountID ID I Year (Chartfield 2) CERTIFICATIONS: Submitted for City Manager's Office by: Fernando Costa (6122) Originating Department Head: Chris Harder (5020) Additional Information Contact: Alexander Pierce (8401) ATTACHMENTS 1. 60SCADA Replacement Remont FID Table (WCF 09.20.24)V3.xlsx (CFW Internal) 2. 60WATER SCADA REPLC REMONT.docx (CFW Internal) 3. Form 1295 Certificate 101252020.pdf (CFW Internal) 4. ORD.APP 60WATER SCADA REPLC REMONT 56002 A025(r2).docx (Public) 5. ORD.APP 60WATER SCADA REPLC REMONT 56022 A025(r3).docx (Public) 6. PBS CPN 103086.pdf (CFW Internal) 7. Project Map-SCADA WTP.pdf (Public) 8. Red Group Compliance Memo Approved-NS.pdf (CFW Internal) 56002 0600430 4956001 103086 2025 56002 0600430 103086 2025 56022 0600430 4905158 UCMLPR 2025 56022 0600430 4905158 103086 2025 56022 0600430 UCMLPR 2025 56022 0600430 103086 2025 56002 0600430 4956001 UNSPEC UNSPEC 9999 56002 0600430 4956001 103086 005580 9999 56022 0600430 4905158 UCMLPR UNSPEC 9999 56022 0600430 4905158 103086 005580 9999 56022 0600430 5330500 103086 56002 0600430 5330500 103086 56022 0600430 5330500 103086 56002 0600430 5610109 103086 56002 0600430 5610110 103086 56002 0600430 5610603 103086 005580 CAPEXP 005580 CAPEXP CAPEXP CAPEXP 9999 9999 9999 9999 9999 9999 $8,595,336.00 Expenditures not eligible to be $8,595,336.00 capitalized ($850,500.00) Expenditures eligible to be $850,500.00 capitalized ($850,500.00) $850,500.00 $8,595,336.00) Expenditures not eligible to be $8,595,336.00 capitalized $850,500.00 Expenditures eligible to be ($850,500.00) capitalized $123,500.00 Remont expenditures eligible to be capitalized Remont expenditures not eligible $8,110,336.00 $8,233,836.00 to be capitalized $727,000.00 Water IT equip expenditures eligible to be capitalized Water IT expenditures not eligible miner equipment $155,000.00 to be capitalized Water IT expenditures not eligible minor software $150,000.00 to be capitalized Water IT expenditures not eligible software licenses $180,000.00 to be capitalized $1,212,000.00 0005 10 MAYOR AND COUNCIL (M&C) COMMUNICATION Pagel of 2 y ON I [e)\iII1116611111 MAYOR AND COUNCIL (M&C) COMMUNICATION [Assembler: For Contract Document execution, remove this page and replace with the approved M&Cfor the award of the project. M&C insert shall be on blue paper.] ++END OF SECTION++ CITY OF FORT WORTH March 21, 2024 SCADA System Replacement 103086 0005 10 MAYOR AND COUNCIL (M&C) COMMUNICATION Page 2 of 2 : III11161Xxi"a1010 N 010Is] eV.11a FAA aQ080W.1VIC� CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ADDENDUM NO. 1 Page 1 of 2 CITY OF FORT WORTH, TEXAS PREQUALIFICATION FOR THE CONSTRUCTION OF SCADA SYSTEM REPLACEMENT ADDENDUM NO. 1 This Addendum is part of the Contract Documents and modifies the Contractor for The Construction of SCADA System Replacement Document dated March 2024 for the above referenced project. This change affects the Prequalification Document distributed on March 21, 2024 to prequalify Interested Parties. Acknowledge receipt of this Addendum in accordance with the requirements in Section 00 21 13 Prequalification Instructions. Failure to do so may result in the Interested Party not being prequalified. Overview and General Clarifications: 1. This addendum provides Section 00 72 00 General Conditions and Section 00 73 00 Supplementary Conditions to all Interested Parties following completion of legal review. ADDENDUM ITEMS (SPECIFICATION MODIFICATIONS & PROJECT CLARIFICATIONS): 1. Delete the words "— NOT INCLUDED IN DOCUMENT*" following "Section 00 72 00 General Conditions" and "Section 00 73 00 Supplementary Conditions" in the Table of Contents. 2. Section 00 72 00, attached following the words "END OF ADDENDUM No. 1" as ATTACHMENT 1 — AD 1, is added to the Contract Documents. Section 00 73 00, attached following the words "END OF ADDENDUM No. 1" as ATTACHMENT 2 — AD 1, is added to the Contract Documents. *: :* ROSSER R. i STANDIFER ��� �• 92755 S()NAl�-��`�� s Rosser R. Standifer, PE Principal Engineer Arcadis Addendum No. 1 Issued by the City of Fort Worth Date: March 22, 2024 Alexander Pierce Project Manager City of Fort Worth END OF ADDENDUM No. 1 ADDENDUM NO. 1 Page 2 of 2 STANDARD GENERAL CONDITIONS OF THE CONSTRUCTION CONTRACT CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: &23/2021 ATTACHMENT 1 - AD1 STANDARD GENERAL CONDITIONS OF THE CONSTRUCTION CONTRACT TABLE OF CONTENTS Page Article I — Definitions and Terminology .......................................................................................................... I 1.01 Defined Terms ............................................................................................................................... 1 1.02 Terminology .................................................................................................................................. 6 Article2 — Preliminary Matters ......................................................................................................................... 7 2.01 Copies of Documents .................................................................................................................... 7 2.02 Commencement of Contract Time; Notice to Proceed ................................................................ 7 2.03 Starting the Work .......................................................................................................................... 8 2.04 Before Starting Construction ........................................................................................................ 8 2.05 Preconstruction Conference .......................................................................................................... 8 2.06 Public Meeting .............................................................................................................................. 8 2.07 Initial Acceptance of Schedules .................................................................................................... 8 Article 3 — Contract Documents: Intent, Amending, Reuse ............................................................................ 8 3.01 Intent .............................................................................................................................................. 8 3.02 Reference Standards ...................................................................................................................... 9 3.03 Reporting and Resolving Discrepancies ....................................................................................... 9 3.04 Amending and Supplementing Contract Documents ................................................................. 10 3.05 Reuse of Documents ................................................................................................................... 10 3.06 Electronic Data ............................................................................................................................ 11 Article 4 — Availability of Lands; Subsurface and Physical Conditions; Hazardous Environmental Conditions; Reference Points ........................................................................................................... 11 4.01 Availability of Lands .................................................................................................................. 11 4.02 Subsurface and Physical Conditions .......................................................................................... 12 4.03 Differing Subsurface or Physical Conditions ............................................................................. 12 4.04 Underground Facilities ............................................................................................................... 13 4.05 Reference Points ......................................................................................................................... 14 4.06 Hazardous Environmental Condition at Site .............................................................................. 14 Article 5 — Bonds and Insurance ..................................................................................................................... 16 5.01 Licensed Sureties and Insurers ................................................................................................... 16 5.02 Performance, Payment, and Maintenance Bonds ....................................................................... 16 5.03 Certificates of Insurance ............................................................................................................. 16 5.04 Contractor's Insurance ................................................................................................................ 18 5.05 Acceptance of Bonds and Insurance; Option to Replace ...........................................................19 Article 6 — Contractor's Responsibilities ....................... 6.01 Supervision and Superintendence ............... CITY OF FORT WORTH STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS Revision: 8/23/2021 ................................................................................. 19 ................................................................................ 19 SCADA System Replacement 103086 ATTACHMENT 1 — AD1 6.02 Labor; Working Hours ................................................................................................................ 20 6.03 Services, Materials, and Equipment ........................................................................................... 20 6.04 Project Schedule .......................................................................................................................... 21 6.05 Substitutes and "Or-Equals"....................................................................................................... 21 6.06 Concerning Subcontractors, Suppliers, and Others .................................................................... 24 6.07 Wage Rates .................................................................................................................................. 25 6.08 Patent Fees and Royalties ........................................................................................................... 26 6.09 Permits and Utilities .................................................................................................................... 27 6.10 Laws and Regulations ................................................................................................................. 27 6.11 Taxes ........................................................................................................................................... 28 6.12 Use of Site and Other Areas ....................................................................................................... 28 6.13 Record Documents ...................................................................................................................... 29 6.14 Safety and Protection .................................................................................................................. 29 6.15 Safety Representative .................................................................................................................. 30 6.16 Hazard Communication Programs ............................................................................................. 30 6.17 Emergencies and/or Rectification ............................................................................................... 30 6.18 Submittals .................................................................................................................................... 31 6.19 Continuing the Work ................................................................................................................... 32 6.20 Contractor's General Warranty and Guarantee .......................................................................... 32 6.21 Indemnification ......................................................................................................................... 33 6.22 Delegation of Professional Design Services .............................................................................. 34 6.23 Right to Audit .............................................................................................................................. 34 6.24 Nondiscrimination ....................................................................................................................... 35 Article 7 - Other Work at the Site ................................................................................................................... 35 7.01 Related Work at Site ................................................................................................................... 35 7.02 Coordination ................................................................................................................................ 36 Article 8 - City's Responsibilities ................................................................................................................... 36 8.01 Communications to Contractor ................................................................................................... 36 8.02 Furnish Data ................................................................................................................................ 36 8.03 Pay When Due ............................................................................................................................ 36 8.04 Lands and Easements; Reports and Tests ................................................................................... 36 8.05 Change Orders ............................................................................................................................. 36 8.06 Inspections, Tests, and Approvals .............................................................................................. 36 8.07 Limitations on City's Responsibilities ....................................................................................... 37 8.08 Undisclosed Hazardous Environmental Condition .................................................................... 37 8.09 Compliance with Safety Program ............................................................................................... 37 Article 9 - City's Observation Status During Construction ........................................................................... 37 9.01 City's Project Manager ............................................................................................................ 37 9.02 Visits to Site ................................................................................................................................ 37 9.03 Authorized Variations in Work .................................................................................................. 38 9.04 Rejecting Defective Work .......................................................................................................... 38 9.05 Determinations for Work Performed .......................................................................................... 38 9.06 Decisions on Requirements of Contract Documents and Acceptability of Work .....................38 CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1 - AD1 Article 10 - Changes in the Work; Claims; Extra Work ................................................................................ 38 10.01 Authorized Changes in the Work ............................................................................................... 38 10.02 Unauthorized Changes in the Work ........................................................................................... 39 10.03 Execution of Change Orders ....................................................................................................... 39 10.04 Extra Work .................................................................................................................................. 39 10.05 Notification to Surety .................................................................................................................. 39 10.06 Contract Claims Process ............................................................................................................. 40 Article 11 - Cost of the Work; Allowances; Unit Price Work; Plans Quantity Measurement ......................41 11.01 Cost of the Work ......................................................................................................................... 41 11.02 Allowances .................................................................................................................................. 43 11.03 Unit Price Work .......................................................................................................................... 44 11.04 Plans Quantity Measurement ...................................................................................................... 45 Article 12 - Change of Contract Price; Change of Contract Time ................................................................. 46 12.01 Change of Contract Price ............................................................................................................ 46 12.02 Change of Contract Time ............................................................................................................ 47 12.03 Delays .......................................................................................................................................... 47 Article 13 - Tests and Inspections; Correction, Removal or Acceptance of Defective Work ...................... 48 13.01 Notice of Defects ........................................................................................................................ 48 13.02 Access to Work ........................................................................................................................... 48 13.03 Tests and Inspections .................................................................................................................. 48 13.04 Uncovering Work ........................................................................................................................ 49 13.05 City May Stop the Work ............................................................................................................. 49 13.06 Correction or Removal of Defective Work ................................................................................ 50 13.07 Correction Period ........................................................................................................................ 50 13.08 Acceptance of Defective Work ................................................................................................... 51 13.09 City May Correct Defective Work ............................................................................................. 51 Article 14 - Payments to Contractor and Completion .................................................................................... 52 14.01 Schedule of Values ...................................................................................................................... 52 14.02 Progress Payments ...................................................................................................................... 52 14.03 Contractor's Warranty of Title ................................................................................................... 54 14.04 Partial Utilization ........................................................................................................................ 55 14.05 Final Inspection ........................................................................................................................... 55 14.06 Final Acceptance ......................................................................................................................... 55 14.07 Final Payment .............................................................................................................................. 56 14.08 Final Completion Delayed and Partial Retainage Release ........................................................ 56 14.09 Waiver of Claims ........................................................................................................................ 57 Article 15 - Suspension of Work and Termination ........................................................................................ 57 15.01 City May Suspend Work ............................................................................................................. 57 15.02 City May Terminate for Cause ................................................................................................... 58 15.03 City May Terminate For Convenience ....................................................................................... 60 Article16 - Dispute Resolution ...................................................................................................................... 61 16.01 Methods and Procedures ............................................................................................................. 61 CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1 - AD1 Article 17 — Miscellaneous .................................... 17.01 Giving Notice .................................... 17.02 Computation of Times ...................... 17.03 Cumulative Remedies ....................... 17.04 Survival of Obligations ..................... 17.05 Headings ............................................ CITY OF FORT WORTH STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS Revision: 8/23/2021 .......................................................................................... 62 .......................................................................................... 62 .......................................................................................... 62 .......................................................................................... 62 .......................................................................................... 63 .......................................................................................... 63 SCADA System Replacement 103086 ATTACHMENT 1 — AD1 007200-1 GENERAL OONDITIONS Page 1 of 63 ARTICLE 1— DEFINITIONS AND TERMINOLOGY 1.01 Defined Terms A. Whereverused in these General Conditions or in other Contract Documents, the terms listed below have the meanings indicated which are applicable to both the singular and plural thereof, and words denoting gender shall include the masculine, feminine and neuter. Said terms are generally capitalized or written in italics, but not always. When used in a context consistent with the definition of a listed -defined term, the term shall have a meaning as defined below whether capitalized or italicized or otherwise. In addition to terms specifically defined, terms with initial capital letters in the Contract Documents include references to identified articles and paragraphs, and the titles of other documents or forms. 1. Addenda —Written or graphic instruments issued prior to the opening of Bids which clarify, correct, or change the Bidding Requirements or the proposed Contract Documents. 2. Agreement —The written instrument which is evidence of the agreement between City and Contractor covering the Work. 3. Application for Payment —The form acceptable to City which is to be used by Contractor during the course of the Work in requesting progress or final payments and which is to be accompanied by such supporting documentation as is required by the Contract Documents. 4. Asbestos Any material that contains more than one percent asbestos and is friable or is releasing asbestos fibers into the air above current action levels established by the United States Occupational Safety and Health Administration. 5. Award — Authorization by the City Council for the City to enter into an Agreement. 6. Bid —The offer or proposal of a Bidder submitted on the prescribed form setting forth the prices for the Work to be performed. 7. Bidder —The individual or entity who submits a Bid directly to City. 8. Bidding Documents —The Bidding Requirements and the proposed Contract Documents (including all Addenda). 9. Bidding Requirements —The advertisement or Invitation to Bid, Instructions to Bidders, Bid security of acceptable form, if any, and the Bid Form with any supplements. 10. Business Day — A business day is defined as a day that the City conducts normal business, generally Monday through Friday, except for federal or state holidays observed by the City. 11. CalendarDay —A day consisting of 24 hours measured from midnight to the next midnight. CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1— AD1 007200-1 GENERAL OONDITIONS Page 2 of 63 12. Change Order —A document, which is prepared and approved by the City, which is signed by Contractor and City and authorizes an addition, deletion, or revision in the Work or an adjustment in the Contract Price or the Contract Time, issued on or after the Effective Date of the Agreement. 13. City— The City of Fort Worth, Texas, a home -rule municipal corporation, authorized and chartered under the Texas State Statutes, acting by its governing body through its City Manager, his designee, or agents authorized under his behalf, each of which is required by Charter to perform specific duties with responsibility for final enforcement of the contracts involving the City of Fort Worth is by Charter vested in the City Manager and is the entity with whom Contractor has entered into the Agreement and for whom the Work is to be performed. 14. City Attorney — The officially appointed City Attorney of the City of Fort Worth, Texas, or his duly authorized representative. 15. City Council - The duly elected and qualified governing body of the City of Fort Worth, Texas. 16. City Manager — The officially appointed and authorized City Manager of the City of Fort Worth, Texas, or his duly authorized representative. 17. Contract Claim —A demand or assertion by City or Contractor seeking an adjustment of Contract Price or Contract Time, or both, or other relief with respect to the terms of the Contract. A demand for money or services by a third party is not a Contract Claim. 18. Contract —The entire and integrated written document between the City and Contractor concerning the Work. The Contract contains the Agreement and all Contract Documents and supersedes prior negotiations, representations, or agreements, whether written or oral. 19. Contract Documents —Those items so designated in the Agreement. All items listed in the Agreement are Contract Documents. Approved Submittals, other Contractor submittals, and the reports and drawings of subsurface and physical conditions are not Contract Documents. 20. Contract Price —The moneys payable by City to Contractor for completion of the Work in accordance with the Contract Documents as stated in the Agreement (subject to the provisions of Paragraph 11.03 in the case of Unit Price Work). 21. Contract Time —The number of days or the dates stated in the Agreement to: (i) achieve Milestones, if any and (ii) complete the Work so that it is ready for Final Acceptance. 22. Contractor —The individual or entity with whom City has entered into the Agreement. 23. Cost of the Work —See Paragraph 11.01 of these General Conditions for definition. CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1— AD1 007200-1 GENERAL OONDITIONS Page 3 of 63 24. Damage Claims — A demand for money or services arising from the Project or Site from a third party, City or Contractor exclusive of a Contract Claim. 25. Day or day — A day, unless otherwise defined, shall mean a Calendar Day. 26. Director of Aviation — The officially appointed Director of the Aviation Department of the City of Fort Worth, Texas, or his duly appointed representative, assistant, or agents. 27. Director of Parks and Community Services — The officially appointed Director of the Parks and Community Services Department of the City of Fort Worth, Texas, or his duly appointed representative, assistant, or agents. 28. Director of Planning and Development — The officially appointed Director of the Planning and Development Department of the City of Fort Worth, Texas, or his duly appointed representative, assistant, or agents. 29. Director of Transportation Public Works — The officially appointed Director of the Transportation Public Works Department of the City of Fort Worth, Texas, or his duly appointed representative, assistant, or agents. 30. Director of Water Department — The officially appointed Director of the Water Department of the City of Fort Worth, Texas, or his duly appointed representative, assistant, or agents. 31. Drawings —That part of the Contract Documents prepared or approved by Engineer which graphically shows the scope, extent, and character of the Work to be performed by Contractor. Submittals are not Drawings as so defined. 32. Effective Date of the Agreement —The date indicated in the Agreement on which it becomes effective, but if no such date is indicated, it means the date on which the Agreement is signed and delivered by the last of the two parties to sign and deliver. 33. Engineer —The licensed professional engineer or engineering firm registered in the State of Texas performing professional services for the City. 34. Extra Work — Additional work made necessary by changes or alterations of the Contract Documents or of quantities or for other reasons for which no prices are provided in the Contract Documents. Extra work shall be part of the Work. 35. Field Order —A written order issued by City which requires changes in the Work but which does not involve a change in the Contract Price, Contract Time, or the intent of the Engineer. Field Orders are paid from Field Order Allowances incorporated into the Contract by funded work type at the time of award. 36. Final Acceptance — The written notice given by the City to the Contractor that the Work specified in the Contract Documents has been completed to the satisfaction of the City. CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1— AD1 007200-1 GENERAL OONDITIONS Page 4 of 63 37. Final Inspection — Inspection carried out by the City to verify that the Contractor has completed the Work, and each and every part or appurtenance thereof, fully, entirely, and in conformance with the Contract Documents. 38. General Requirements —Sections of Division 1 of the Contract Documents. 39. Hazardous Environmental Condition —The presence at the Site of Asbestos, PCBs, Petroleum, Hazardous Waste, Radioactive Material, or other materials in such quantities or circumstances that may present a substantial danger to persons or property exposed thereto. 40. Hazardous Waste Hazardous waste is defined as any solid waste listed as hazardous or possesses one or more hazardous characteristics as defined in the federal waste regulations, as amended from time to time. 41. Laws and Regulations —Any and all applicable laws, rules, regulations, ordinances, codes, and orders of any and all governmental bodies, agencies, authorities, and courts having jurisdiction. 42. Liens —Charges, security interests, or encumbrances upon Project funds, real property, or personal property. 43. Major Item — An Item of work included in the Contract Documents that has a total cost equal to or greater than 5% of the original Contract Price or $25,000 whichever is less. 44. Milestone —A principal event specified in the Contract Documents relating to an intermediate Contract Time prior to Final Acceptance of the Work. 45. Notice of Award —The written notice by City to the Successful Bidder stating that upon timely compliance by the Successful Bidder with the conditions precedent listed therein, City will sign and deliver the Agreement. 46. Notice to Proceed —A written notice given by City to Contractor fixing the date on which the Contract Time will commence to run and on which Contractor shall start to perform the Work specified in Contract Documents. 47. PCBs Polychlorinated biphenyls. 48. Petroleum —Petroleum, including crude oil or any fraction thereof which is liquid at standard conditions of temperature and pressure (60 degrees Fahrenheit and 14.7 pounds per square inch absolute), such as oil, petroleum, fuel oil, oil sludge, oil refuse, gasoline, kerosene, and oil mixed with other non -Hazardous Waste and crude oils. 49. Plans — See definition of Drawings. CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1— AD1 007200-1 GENERAL OONDITIONS Page 5 of 63 50. Project Schedule —A schedule, prepared and maintained by Contractor, in accordance with the General Requirements, describing the sequence and duration of the activities comprising the Contractor's plan to accomplish the Work within the Contract Time. 51. Project —The Work to be performed under the Contract Documents. 52. Project Manager —The authorized representative of the City who will be assigned to the Site. 53. Public Meeting — An announced meeting conducted by the City to facilitate public participation and to assist the public in gaining an informed view of the Project. 54. Radioactive Material —Source, special nuclear, or byproduct material as defined by the Atomic Energy Act of 1954 (42 USC Section 2011 et seq.) as amended from time to time. 55. Regular Working Hours — Hours beginning at 7:00 a.m. and ending at 6:00 p.m., Monday thru Friday (excluding legal holidays). 56. Samples —Physical examples of materials, equipment, or workmanship that are representative of some portion of the Work and which establish the standards by which such portion of the Work will be judged. 57. Schedule of Submittals —A schedule, prepared and maintained by Contractor, of required submittals and the time requirements to support scheduled performance of related construction activities. 58. Schedule of Values —A schedule, prepared and maintained by Contractor, allocating portions of the Contract Price to various portions of the Work and used as the basis for reviewing Contractor's Applications for Payment. 59. Site —Lands or areas indicated in the Contract Documents as being furnished by City upon which the Work is to be performed, including rights -of -way, permits, and easements for access thereto, and such other lands furnished by City which are designated for the use of Contractor. 60. Specifications —That part of the Contract Documents consisting of written requirements for materials, equipment, systems, standards and workmanship as applied to the Work, and certain administrative requirements and procedural matters applicable thereto. Specifications may be specifically made a part of the Contract Documents by attachment or, if not attached, may be incorporated by reference as indicated in the Table of Contents (Division 00 00 00) of each Project. 61. Subcontractor An individual or entity having a direct contract with Contractor or with any other Subcontractor for the performance of a part of the Work at the Site. CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1— AD1 007200-1 GENERAL OONDITIONS Page 6 of 63 62. Submittals All drawings, diagrams, illustrations, schedules, and other data or information which are specifically prepared or assembled by or for Contractor and submitted by Contractor to illustrate some portion of the Work. 63. Substantial Completion — The stage in the progress of the Project when the Work is sufficiently complete in accordance with the Contract Documents for Final Inspection. 64. Successful Bidder —The Bidder submitting the lowest and most responsive Bid to whom City makes an Award. 65. Superintendent— The representative of the Contractor who is available at all times and able to receive instructions from the City and to act for the Contractor. 66. Supplementary Conditions —That part of the Contract Documents which amends or supplements these General Conditions. 67. Supplier —A manufacturer, fabricator, supplier, distributor, materialman, or vendor having a direct contract with Contractor or with any Subcontractor to furnish materials or equipment to be incorporated in the Work by Contractor or Subcontractor. 68. Underground Facilities —All underground pipelines, conduits, ducts, cables, wires, manholes, vaults, tanks, tunnels, or other such facilities or attachments, and any encasements containing such facilities, including but not limited to, those that convey electricity, gases, steam, liquid petroleum products, telephone or other communications, cable television, water, wastewater, storm water, other liquids or chemicals, or traffic or other control systems. 69 Unit Price Work —See Paragraph 11.03 of these General Conditions for definition. 70. Weekend Working Hours — Hours beginning at 9:00 a.m. and ending at 5:00 p.m., Saturday, Sunday or legal holiday, as approved in advance by the City. 71. Work —The entire construction or the various separately identifiable parts thereof required to be provided under the Contract Documents. Work includes and is the result of performing or providing all labor, services, and documentation necessary to produce such construction including any Change Order or Field Order, and furnishing, installing, and incorporating all materials and equipment into such construction, all as required by the Contract Documents. 72. Working Day — A working day is defied as a day, not including Saturdays, Sundays, or legal holidays authorized by the City for contract purposes, in which weather or other conditions not under the control of the Contractor will permit the performance of the principal unit of work underway for a continuous period of not less than 7 hours between 7 a.m. and 6 p.m. 1.02 Terminology A. The words and terms discussed in Paragraph 1.02.13 through E are not defined but, when used in the Bidding Requirements or Contract Documents, have the indicated meaning. B. Intent of Certain Terms or Adjectives: CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1— AD1 007200-1 GENERAL OONDITIONS Page 7 of 63 The Contract Documents include the terms "as allowed," "as approved," "as ordered," "as directed" or terms of hike effect or import to authorize an exercise of judgment by City. In addition, the adjectives "reasonable," "suitable," "acceptable," "proper," "satisfactory," or adjectives of hike effect or import are used to describe an action or determination of City as to the Work. It is intended that such exercise of professional judgment, action, or determination will be solely to evaluate, in general, the Work for compliance with the information in the Contract Documents and with the design concept of the Project as a functioning whole as shown or indicated in the Contract Documents (unless there is a specific statement indicating otherwise). C. Defective: 1. The word "defective," when modifying the word "Work," refers to Work that is unsatisfactory, faulty, or deficient in that it: a. does not conform to the Contract Documents; or b. does not meet the requirements of any applicable inspection, reference standard, test, or approval referred to in the Contract Documents; or c. has been damaged prior to City's written acceptance. D. Furnish, Install, Perform, Provide: 1. The word "Furnish" or the word "Install" or the word "Perform" or the word "Provide" or the word "Supply," or any combination or similar directive or usage thereof, shall mean furnishing and incorporating in the Work including all necessary labor, materials, equipment, and everything necessary to perform the Work indicated, unless specifically limited in the context used. E. Unless stated otherwise in the Contract Documents, words or phrases that have a well-known technical or construction industry or trade meaning are used in the Contract Documents in accordance with such recognized meaning. ARTICLE 2 — PRELIMINARY MATTERS 2.01 Copies of Documents City shall furnish to Contractor one (1) original executed copy and one (1) electronic copy of the Contract Documents, and four (4) additional copies of the Drawings. Additional copies will be furnished upon request at the cost of reproduction. 2.02 Commencement of Contract Time; Notice to Proceed The Contract Time will commence to run on the day indicated in the Notice to Proceed. A Notice to Proceed maybe given no earlier than 14 days after the Effective Date of the Agreement, unless agreed to by both parties in writing. CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1— AD1 007200-1 GENERAL OONDITIONS Page 8 of 63 2.03 Starting the Work Contractor shall start to perform the Work on the date when the Contract Time commences to run. No Work shall be done at the Site prior to the date on which the Contract Time commences to run. 2.04 Before Starting Construction Baseline Schedules: Submit in accordance with the Contract Documents, and prior to starting the Work. 2.05 Preconstruction Conference Before any Work at the Site is started, the Contractor shall attend a Preconstruction Conference as specified in the Contract Documents. 2.06 Public Meeting Contractor may not mobilize any equipment, materials or resources to the Site prior to Contractor attending the Public Meeting as scheduled by the City. 2.07 Initial Acceptance of Schedules No progress payment shall be made to Contractor until acceptable schedules are submitted to City in accordance with the Schedule Specification as provided in the Contract Documents. ARTICLE 3 — CONTRACT DOCUMENTS: INTENT, AMENDING, REUSE 3.01 Intent A. The Contract Documents are complementary; what is required by one is as binding as if required by all. B. It is the intent of the Contract Documents to describe a functionally complete project (or part thereof) to be constructed in accordance with the Contract Documents. Any labor, documentation, services, materials, or equipment that reasonably may be inferred from the Contract Documents or from prevailing custom or trade usage as being required to produce the indicated result will be provided whether or not specifically called for, at no additional cost to City. C. Clarifications and interpretations of the Contract Documents shall be issued by City. D. The Specifications may vary in form, format and style. Some Specification sections maybe written in varying degrees of streamlined or declarative style and some sections may be relatively narrative by comparison. Omission of such words and phrases as "the Contractor shall," "in conformity with," "as shown," or "as specified" are intentional in streamlined sections. Omitted words and phrases shall be supplied by inference. Similar types of provisions may appear in various parts of a section or articles within a part depending on the format of the CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1— AD1 007200-1 GENERAL OONDITIONS Page 9 of 63 section. The Contractor shall not take advantage of any variation of form, format or style in making Contract Claims. E. The cross referencing of specification sections under the subparagraph heading "Related Sections include but are not necessarily limited to:" and elsewhere within each Specification section is provided as an aid and convenience to the Contractor. The Contractor shall not rely on the cross referencing provided and shall be responsible to coordinate the entire Work under the Contract Documents and provide a complete Project whether or not the cross referencing is provided in each section or whether or not the cross referencing is complete. 3.02 Reference Standards A. Standards, Specifications, Codes, Laws, and Regulations 1. Reference to standards, specifications, manuals, or codes of any technical society, organization, or association, or to Laws or Regulations, whether such reference be specific or by implication, shall mean the standard, specification, manual, code, or Laws or Regulations in effect at the time of opening of Bids (or on the Effective Date of the Agreement if there were no Bids), except as may be otherwise specifically stated in the Contract Documents. 2. No provision of any such standard, specification, manual, or code, or any instruction of a Supplier, shall be effective to change the duties or responsibilities of City, Contractor, or any of their subcontractors, consultants, agents, or employees, from those set forth in the Contract Documents. No such provision or instruction shall be effective to assign to City, or any of its officers, directors, members, partners, employees, agents, consultants, or subcontractors, any duty or authority to supervise or direct the performance of the Work or any duty or authority to undertake responsibility inconsistent with the provisions of the Contract Documents. 3.03 Reporting and Resolving Discrepancies A. Reporting Discrepancies: 1. Contractor's Review of Con tract Documents Before Starting Work: Before undertaking each part of the Work, Contractor shall carefully study and compare the Contract Documents and check and verify pertinent figures therein against all applicable field measurements and conditions. Contractor shall promptly report in writing to City any conflict, error, ambiguity, or discrepancy which Contractor discovers, or has actual knowledge of, and shall obtain a written interpretation or clarification from City before proceeding with any Work affected thereby. 2. Contractor's Review of Contract Documents During Performance of Work: If, during the performance of the Work, Contractor discovers any conflict, error, ambiguity, or discrepancy within the Contract Documents, or between the Contract Documents and (a) any applicable Law or Regulation , (b) any standard, specification, manual, or code, or (c) any instruction of any Supplier, then Contractor shall promptly report it to City in writing. Contractor shall not proceed with the Work affected thereby (except in an emergency as required by Paragraph CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1— AD1 007200-1 GENERAL OONDITIONS Page 10 of 63 6.17.A) until an amendment or supplement to the Contract Documents has been issued by one of the methods indicated in Paragraph 3.04. 3. Contractor shall not be liable to City for failure to report any conflict, error, ambiguity, or discrepancy in the Contract Documents unless Contractor had actual knowledge thereof B. Resolving Discrepancies: Except as may be otherwise specifically stated in the Contract Documents, the provisions of the Contract Documents shall take precedence in resolving any conflict, error, ambiguity, or discrepancy between the provisions of the Contract Documents and the provisions of any standard, specification, manual, or the instruction of any Supplier (whether or not specifically incorporated by reference in the Contract Documents). 2. In case of discrepancies, figured dimensions shall govern over scaled dimensions, Plans shall govern over Specifications, Supplementary Conditions shall govern over General Conditions and Specifications, and quantities shown on the Plans shall govern over those shown in the proposal. 3.04 Amending and Supplementing Contract Documents A. The Contract Documents may be amended to provide for additions, deletions, and revisions in the Work or to modify the terms and conditions thereof by a Change Order. B. The requirements of the Contract Documents may be supplemented, and minor variations and deviations in the Work not involving a change in Contract Price or Contract Time, may be authorized, by one or more of the following ways: 1. A Field Order; 2. City's review of a Submittal (subject to the provisions of Paragraph 6.18.C); or 3. City's written interpretation or clarification. 3.05 Reuse of Documents A. Contractor and any Subcontractor or Supplier shall not: 1. have or acquire any title to or ownership rights in any of the Drawings, Specifications, or other documents (or copies of any thereof) prepared by or bearing the seal of Engineer, including electronic media editions; or 2. reuse any such Drawings, Specifications, other documents, or copies thereof on extensions of the Project or any other project without written consent of City and specific written verification or adaptation by Engineer. CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1— AD1 007200-1 GENERAL OONDITIONS Page 11 of 63 B. The prohibitions of this Paragraph 3.05 will survive final payment, or termination of the Contract. Nothing herein shall preclude Contractor from retaining copies of the Contract Documents for record purposes. 3.06 Electronic Data A. Unless otherwise stated in the Supplementary Conditions, the data furnished by City or Engineer to Contractor, or by Contractor to City or Engineer, that may be relied upon are limited to the printed copies included in the Contract Documents (also known as hard copies) and other Specifications referenced and located on the City's on-line electronic document management and collaboration system site. Files in electronic media format of text, data, graphics, or other types are furnished only for the convenience of the receiving party. Any conclusion or information obtained or derived from such electronic files will be atthe user's sole risk. Ifthere is a discrepancy between the electronic files and the hard copies, the hard copies govern. B. When transferring documents in electronic media format, the transferring party makes no representations as to long term compatibility, usability, or readability of documents resulting from the use of software application packages, operating systems, or computer hardware differing from those used by the data's creator. ARTICLE 4 — AVAILABILITY OF LANDS; SUBSURFACE AND PHYSICAL CONDITIONS; HAZARDOUS ENVIRONMENTAL CONDITIONS; REFERENCE POINTS 4.01 Availability of Lands A. City shall furnish the Site. City shall notify Contractor of any encumbrances or restrictions not of general application but specifically related to use of the Site with which Contractor must comply in performing the Work. City will obtain in a timely manner and pay for easements for permanent structures or permanent changes in existing facilities. 1. The City has obtained or anticipates acquisition of and/or access to right-of-way, and/or easements. Any outstanding right-of-way and/or easements are anticipated to be acquired in accordance with the schedule set forth in the Supplementary Conditions. The Project Schedule submitted by the Contractor in accordance with the Contract Documents must consider any outstanding right-of-way, and/or easements. 2. The City has or anticipates removing and/or relocating utilities, and obstructions to the Site. Any outstanding removal or relocation of utilities or obstructions is anticipated in accordance with the schedule set forth in the Supplementary Conditions. The Project Schedule submitted by the Contractor in accordance with the Contract Documents must consider any outstanding utilities or obstructions to be removed, adjusted, and/or relocated by others. B. Upon reasonable written request, City shall furnish Contractor with a current statement of record legal title and legal description of the lands upon which the Work is to be performed. CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1— AD1 007200-1 GENERAL OONDITIONS Page 12 of 63 C. Contractor shall provide for all additional lands and access thereto that may be required for construction facilities or storage of materials and equipment. 4.02 Subsurface andPhysical Conditions A. Reports and Drawings: The Supplementary Conditions identify: 1. those reports known to City of explorations and tests of subsurface conditions at or contiguous to the Site; and 2. those drawings known to City of physical conditions relating to existing surface or subsurface structures at the Site (except Underground Facilities). B. Limited Reliance by Contractor on Technical Data Authorized: Contractor may rely upon the accuracy of the "technical data" contained in such reports and drawings, but such reports and drawings are not Contract Documents. Such "technical data" is identified in the Supplementary Conditions. Contractor may not make any Contract Claim against City, or any of their officers, directors, members, partners, employees, agents, consultants, or subcontractors with respect to: 1. the completeness of such reports and drawings for Contractor's purposes, including, but not limited to, any aspects of the means, methods, techniques, sequences, and procedures of construction to be employed by Contractor, and safety precautions and programs incident thereto; or 2. other data, interpretations, opinions, and information contained in such reports or shown or indicated in such drawings; or 3. any Contractor interpretation of or conclusion drawn from any "technical data" or any such other data, interpretations, opinions, or information. 4.03 Differing Subsurface or Physical Conditions A. Notice: If Contractor believes that any subsurface or physical condition that is uncovered or revealed either: 1. is of such a nature as to establish that any "technical data" on which Contractor is entitled to rely as provided in Paragraph 4.02 is materially inaccurate; or 2. is of such a nature as to require a change in the Contract Documents; or 3. differs materially from that shown or indicated in the Contract Documents; or 4. is of an unusual nature, and differs materially from conditions ordinarily encountered and generally recognized as inherent in work of the character provided for in the Contract Documents; CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1— AD1 007200-1 GENERAL CONDITIONS Page 13 of 63 then Contractor shall, promptly after becoming aware thereof and before further disturbing the subsurface or physical conditions or performing any Work in connection therewith (except in an emergency as required by Paragraph 6.17.A), notify City in writing about such condition. B. Possible Price and Time Adjustments Contractor shall not be entitled to any adjustment in the Contract Price or Contract Time if: 1. Contractor knew of the existence of such conditions at the time Contractor made a final commitment to City with respect to Contract Price and Contract Time by the submission of a Bid or becoming bound under a negotiated contract; or 2. the existence of such condition could reasonably have been discovered or revealed as a result of the examination of the Contract Documents or the Site; or 3. Contractor failed to give the written notice as required by Paragraph 4.03.A. 4.04 Underground Facilities A. Shown or Indicated.• The information and data shown or indicated in the Contract Documents with respect to existing Underground Facilities at or contiguous to the Site is based on information and data furnished to City or Engineer by the owners of such Underground Facilities, including City, or by others. Unless it is otherwise expressly provided in the Supplementary Conditions: 1. City and Engineer shall not be responsible for the accuracy or completeness of any such information or data provided by others; and 2. the cost of all of the following will be included in the Contract Price, and Contractor shall have full responsibility for: a. reviewing and checking all such information and data; b. locating all Underground Facilities shown or indicated in the Contract Documents; c. coordination and adjustment of the Work with the owners of such Underground Facilities, including City, during construction; and d. the safety and protection of all such Underground Facilities and repairing any damage thereto resulting from the Work. B. Not Shown orindicated: 1. If an Underground Facility which conflicts with the Work is uncovered or revealed at or contiguous to the Site which was not shown or indicated, or not shown or indicated with reasonable accuracy in the Contract Documents, Contractor shall, promptly after becoming aware thereof and before further disturbing conditions affected thereby or performing any CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: &23/2MI ATTACHMENT 1— AD1 007200-1 GENERAL OONDITIONS Page 14 of 63 Work in connection therewith (except in an emergency as required by Paragraph 6.17.A), identify the owner of such Underground Facility and give notice to that owner and to City. City will review the discovered Underground Facility and determine the extent, if any, to which a change may be required in the Contract Documents to reflect and document the consequences of the existence or location of the Underground Facility. Contractor shall be responsible for the safety and protection of such discovered Underground Facility. 2. If City concludes that a change in the Contract Documents is required, a Change Order may be issued to reflect and document such consequences. 3. Verification of existing utilities, structures, and service lines shall include notification of all utility companies a minimum of 48 hours in advance of construction including exploratory excavation if necessary. 4.05 Reference Points A. City shall provide engineering surveys to establish reference points for construction, which in City's judgment are necessary to enable Contractor to proceed with the Work. City will provide construction stakes or other customary method of marking to establish line and grades for roadway and utility construction, centerlines and benchmarks for bridgework. Contractor shall protect and preserve the established reference points and property monuments, and shall make no changes or relocations. Contractor shall report to City whenever any reference point or property monument is lost or destroyed or requires relocation because of necessary changes in grades or locations. The City shall be responsible for the replacement or relocation of reference points or property monuments not carelessly or willfully destroyed by the Contractor. The Contractor shall notify City in advance and with sufficient time to avoid delays. B. Whenever, in the opinion of the City, any reference point or monument has been carelessly or willfully destroyed, disturbed, or removed by the Contractor or any of his employees, the full cost for replacing such points plus 25% will be charged against the Contractor, and the full amount will be deducted from payment due the Contractor. 4.06 Hazardous Environmental Condition at Site A. Reports and Drawings: The Supplementary Conditions identify those reports and drawings known to City relating to Hazardous Environmental Conditions that have been identified at the Site. B. Limited Reliance by Contractor on Technical Data Authorized: Contractor may rely upon the accuracy of the "technical data" contained in such reports and drawings, but such reports and drawings are not Contract Documents. Such "technical data" is identified in the Supplementary Conditions. Contractor may not make any Contract Claim against City, or any of their officers, directors, members, partners, employees, agents, consultants, or subcontractors with respect to: 1. the completeness of such reports and drawings for Contractor's purposes, including, but not limited to, any aspects of the means, methods, techniques, sequences and procedures of CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1— AD1 007200-1 GENERAL OONDITIONS Page 15 of 63 construction to be employed by Contractor and safety precautions and programs incident thereto; or 2. other data, interpretations, opinions and information contained in such reports or shown or indicated in such drawings; or 3. any Contractor interpretation of or conclusion drawn from any "technical data" or any such other data, interpretations, opinions or information. C. Contractor shall not be responsible for any Hazardous Environmental Condition uncovered or revealed at the Site which was not shown or indicated in Drawings or Specifications or identified in the Contract Documents to be within the scope of the Work. Contractor shall be responsible for a Hazardous Environmental Condition created with any materials brought to the Site by Contractor, Subcontractors, Suppliers, or anyone else for whom Contractor is responsible. D. If Contractor encounters a Hazardous Environmental Condition or if Contractor or anyone for whom Contractor is responsible creates a Hazardous Environmental Condition, Contractor shall immediately: (i) secure or otherwise isolate such condition; (ii) stop all Work in connection with such condition and in any area affected thereby (except in an emergency as required by Paragraph 6.17.A); and (iii) notify City (and promptly thereafter confirm such notice in writing). City may consider the necessity to retain a qualified expert to evaluate such condition or take corrective action, if any. E. Contractor shall not be required to resume Work in connection with such condition or in any affectedarea until after City has obtained any required permits related thereto and delivered written notice to Contractor: (i) specifying that such condition and any affected area is or has been rendered suitable for the resumption of Work; or (ii) specifying any special conditions under which such Work may be resumed. F. If after receipt of such written notice Contractor does not agree to resume such Work based on a reasonable belief it is unsafe, or does not agree to resume such Work under such special conditions, then City may order the portion of the Work that is in the area affected by such condition to be deleted from the Work. City may have such deleted portion of the Work performed by City's own forces or others. G. To the fullest extentpermitted by Laws and Regulations, Contractor shall indemnify and hold harmless City, from and against all claims, costs, losses, and damages (including but not limited to all fees and charges of engineers, architects, attorneys, and other professionals and all court or arbitration or other dispute resolution costs) arising out of or relating to a Hazardous Environmental Condition created by Contractoror by anyoneforwhom Contractor is responsible. Nothing in this Paragraph 4.06.G shall obligate Contractor to indemnify any individual or entity from and against the consequences of that individual's or entity's own negligence. H. The provisions of Paragraphs 4.02, 4.03, and 4.04 do not apply to a Hazardous Environmental Condition uncovered or revealed at the Site. CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1- AD1 007200-1 GENERAL OONDITIONS Page 16 of 63 ARTICLE 5 — BONDS AND INSURANCE 5.01 Licensed Sureties and Insurers All bonds and insurance required by the Contract Documents to be purchased and maintained by Contractor shall be obtained from surety or insurance companies that are duly licensed or authorized in the State of Texas to issue bonds or insurance policies for the limits and coverages so required. Such surety and insurance companies shall also meet such additional requirements and qualifications as may be provided in the Supplementary Conditions. 5.02 Performance, Payment, and Maintenance Bonds A. Contractor shall furnish performance and payment bonds, in accordance with Texas Government Code Chapter 2253 or successor statute, each in an amount equal to the Contract Price as security for the faithful performance and payment of all of Contractor's obligations under the Contract Documents. B. Contractor shall furnish maintenance bonds in an amount equal to the Contract Price as security to protect the City against any defects in any portion of the Work described in the Contract Documents. Maintenance bonds shall remain in effect for two (2) years after the date of Final Acceptance by the City. C. All bonds shall be in the form prescribed by the Contract Documents except as provided otherwise by Laws or Regulations, and shall be executed by such sureties as are named in the list of "Companies Holding Certificates of Authority as Acceptable Sureties on Federal Bonds and as Acceptable Reinsuring Companies" as published in Circular 570 (amended) by the Financial Management Service, Surety Bond Branch, U.S. Department of the Treasury. All bonds signed by an agent or attorney -in -fact must be accompanied by a sealed and dated power of attorney which shall show that it is effective on the date the agent or attorney -in -fact signed each bond. D. If the surety on any bond furnished by Contractor is declared bankrupt or becomes insolvent or its right to do business is terminated in the State of Texas or it ceases to meet the requirements of Paragraph 5.02.C, Contractor shall promptly notify City and shall, within 30 days after the event giving rise to such notification, provide another bond and surety, both of which shall comply with the requirements of Paragraphs 5.01 and 5.02.C. 5.03 Certificates of Insurance Contractor shall deliver to City, with copies to each additional insured and loss payee identified in the Supplementary Conditions, certificates of insurance (other evidence of insurance requested by City or any other additional insured) in at least the minimum amount as specified in the Supplementary Conditions which Contractor is required to purchase and maintain. 1. The certificate of insurance shall document the City, and all identified entities named in the Supplementary Conditions as "Additional Insured" on all liability policies. CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1— AD1 007200-1 GENERAL OONDITIONS Page 17 of 63 2. The Contractor's general liability insurance shall include a, "per project" or "per location", endorsement, which shall be identified in the certificate of insurance provided to the City. 3. The certificate shall be signed by an agent authorized to bind coverage on behalf of the insured, be complete in its entirety, and show complete insurance carrier names as listed in the current A.M. Best Property & Casualty Guide 4. The insurers for all policies must be licensed and/or approved to do business in the State of Texas. Except for workers' compensation, all insurers must have a minimum rating of A-: VII in the current A. M. Best Key Rating Guide or have reasonably equivalent financial strength and solvency to the satisfaction of Risk Management. If the rating is below that required, written approval of City is required. 5. All applicable policies shall include a Waiver of Subrogation (Rights of Recovery) in favor of the City. In addition, the Contractor agrees to waive all rights of subrogation against the Engineer (if applicable), and each additional insured identified in the Supplementary Conditions 6. Failure of the City to demand such certificates or other evidence of full compliance with the insurance requirements or failure of the City to identify a deficiency from evidence that is provided shall not be construed as a waiver of Contractor's obligation to maintain such lines of insurance coverage. 7. If insurance policies are not written for specified coverage limits, an Umbrella or Excess Liability insurance for any differences is required. Excess Liability shall follow form of the primary coverage. 8. Unless otherwise stated, all required insurance shall be written on the "occurrence basis". If coverage is underwritten on a claims -made basis, the retroactive date shall be coincident with or prior to the date of the effective date of the agreement and the certificate of insurance shall state that the coverage is claims -made and the retroactive date. The insurance coverage shall be maintained for the duration of the Contract and for three (3) years following Final Acceptance provided under the Contract Documents or for the warranty period, whichever is longer. An annual certificate of insurance submitted to the City shall evidence such insurance coverage. 9. Policies shall have no exclusions by endorsements, which, neither nullify or amend, the required lines of coverage, nor decrease the limits of said coverage unless such endorsements are approved in writing by the City. In the event a Contract has been bid or executed and the exclusions are determined to be unacceptable or the City desires additional insurance coverage, and the City desires the contractor/engineer to obtain such coverage, the contract price shall be adjusted by the cost of the premium for such additional coverage plus 10%. 10. Any self -insured retention (SIR), in excess of $25,000.00, affecting required insurance coverage shall be approved by the City in regards to asset value and stockholders' equity. In CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1- AD1 007200-1 GENERAL OONDITIONS Page 18 of 63 lieu of traditional insurance, alternative coverage maintained through insurance pools or risk retention groups, must also be approved by City. 11. Any deductible in excess of $5,000.00, for any policy that does not provide coverage on a first -dollar basis, must be acceptable to and approved by the City. 12. City, at its sole discretion, reserves the right to review the insurance requirements and to make reasonable adjustments to insurance coverage's and their limits when deemed necessary and prudent by the City based upon changes in statutory law, court decision or the claims history of the industry as well as of the contracting party to the City. The City shall be required to provide prior notice of 90 days, and the insurance adjustments shall be incorporated into the Work by Change Order. 13. City shall be entitled, upon written request and without expense, to receive copies of policies and endorsements thereto and may make any reasonable requests for deletion or revision or modifications of particular policy terms, conditions, limitations, or exclusions necessary to conform the policy and endorsements to the requirements of the Contract. Deletions, revisions, or modifications shall not be required where policy provisions are established by law or regulations binding upon either party or the underwriter on any such policies. 14. City shall not be responsible for the direct payment of insurance premium costs for Contractor's insurance. 5.04 Contractor's Insurance A. Workers Compensation and Employers' Liability. Contractor shall purchase and maintain such insurance coverage with limits consistent with statutory benefits outlined in the Texas Workers' Compensation Act (Texas Labor Code, Ch. 406, as amended), and minimum limits for Employers' Liability as is appropriate for the Work being performed and as will provide protection from claims set forth below which may arise out of or result from Contractor's performance of the Work and Contractor's other obligations under the Contract Documents, whether it is to be performed by Contractor, any Subcontractor or Supplier, or by anyone directly or indirectly employed by any of them to perform any of the Work, or by anyone for whose acts any of them may be liable: 1. claims under workers' compensation, disability benefits, and other similar employee benefit acts; 2. claims for damages because of bodily injury, occupational sickness or disease, or death of Contractor's employees. B. Commercial General Liability. Coverage shall include but not be limited to covering liability (bodily injury or property damage) arising from: premises/operations, independent contractors, products/completed operations, personal injury, and liability under an insured contract. Insurance shall be provided on an occurrence basis, and as comprehensive as the current Insurance Services Office (ISO) policy. This insurance shall apply as primary insurance with respect to any other CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1— AD1 007200-1 GENERAL OONDITIONS Page 19 of 63 insurance or self-insurance programs afforded to the City. The Commercial General Liability policy, shall have no exclusions by endorsements that would alter of nullify premises/operations, products/completed operations, contractual, personal injury, or advertising injury, which are normally contained with the policy, unless the City approves such exclusions in writing. For construction projects that present a substantial completed operation exposure, the City may require the contractor to maintain completed operations coverage for a minimum of no less than three (3) years following the completion of the project (if identified in the Supplementary Conditions). C. Automobile Liability. A commercial business auto policy shall provide coverage on "any auto', defined as autos owned, hired and non -owned and provide indemnity for claims for damages because bodily injury or death of any person and or property damage arising out of the work, maintenance or use of any motor vehicle by the Contractor, any Subcontractor or Supplier, or by anyone directly or indirectly employed by any of them to perform any of the Work, or by anyone for whose acts any of them may be liable. D. Railroad Protective Liability. If any of the work or any warranty work is within the limits of railroad right-of-way, the Contractor shall comply with the requirements identified in the Supplementary Conditions. E. Notification of Policy Cancellation: Contractor shall immediately notify City upon cancellation or other loss of insurance coverage. Contractor shall stop work until replacement insurance has been procured. There shall be no time credit for days not worked pursuant to this section. 5.05 Acceptance of Bondsandlnsurance, Option to Replace If City has any objection to the coverage afforded by or other provisions of the bonds or insurance required to be purchased and maintained by the Contractor in accordance with Article 5 on the basis of non-conformance with the Contract Documents, the City shall so notify the Contractor in writing within 10 Business Days afterreceipt of the certificates (or other evidence requested). Contractor shall provide to the City such additional information in respect of insurance provided as the City may reasonably request. If Contractor does not purchase or maintain all of the bonds and insurance required by the Contract Documents, the City shall notify the Contractor in writing of such failure prior to the start of the Work, or of such failure to maintain prior to any change in the required coverage. ARTICLE 6 — CONTRACTOR'S RESPONSIBILITIES 6.01 Supervision and Superintendence A. Contractor shall supervise, inspect, and direct the Work competently and efficiently, devoting such attention thereto and applying such skills and expertise as may be necessary to perform the Work in accordance with the Contract Documents. Contractor shall be solely responsible for the means, methods, techniques, sequences, and procedures of construction. CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1— AD1 007200-1 GENERAL OONDITIONS Page 20 of 63 B. At all times during the progress of the Work, Contractor shall assign a competent, English- speaking, Superintendent who shall not be replaced without written notice to City. The Superintendent will be Contractor's representative at the Site and shall have authority to act on behalf of Contractor. All communication given to or received from the Superintendent shall be binding on Contractor. C. Contractor shall notify the City 24 hours prior to moving areas during the sequence of construction. 6.02 Labor; Working Hours A. Contractor shall provide competent, suitably qualified personnel to perform construction as required by the Contract Documents. Contractor shall at all times maintain good discipline and order at the Site. B. Except as otherwise required for the safety or protection of persons or the Work or property at the Site or adjacent thereto, and except as otherwise stated in the Contract Documents, all Work at the Site shall be performed during Regular Working Hours. Contractor will not permit the performance of Work beyond Regular Working Hours or for Weekend Working Hours without City's written consent (which will not be unreasonably withheld). Written request (by letter or electronic communication) to perform Work: 1. for beyond Regular Working Hours request must be made by noon at least two (2) Business Days prior 2. for Weekend Working Hours request must be made by noon of the preceding Thursday 3. for legal holidays request must be made by noon two Business Days prior to the legal holiday. 6.03 Services, Materials, and Equipment A. Unless otherwise specified in the Contract Documents, Contractor shall provide and assume full responsibility for all services, materials, equipment, labor, transportation, construction equipment and machinery, tools, appliances, fuel, power, light, heat, telephone, water, sanitary facilities, temporary facilities, and all other facilities and incidentals necessary for the performance, Contractor required testing, start-up, and completion of the Work. B. All materials and equipment incorporated into the Work shall be as specified or, if not specified, shall be of good quality and new, except as otherwise provided in the Contract Documents. All special warranties and guarantees required by the Specifications shall expressly run to the benefit of City. If required by City, Contractor shall furnish satisfactory evidence (including reports of required tests) as to the source, kind, and quality of materials and equipment. CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1— AD1 007200-1 GENERAL OONDITIONS Page 21 of 63 C. All materials and equipment to be incorporated into the Work shall be stored, applied, installed, connected, erected, protected, used, cleaned, and conditioned in accordance with instructions of the applicable Supplier, except as otherwise may be provided in the Contract Documents. D. All items of standard equipment to be incorporated into the Work shall be the latest model at the time of bid, unless otherwise specified. 6.04 Project Schedule A. Contractor shall adhere to the Project Schedule established in accordance with Paragraph 2.07 and the General Requirements as it may be adjusted from time to time as provided below. Contractor shall submit to City for acceptance (to the extent indicated in Paragraph 2.07 and the General Requirements) proposed adjustments in the Project Schedule that will not result in changing the Contract Time. Such adjustments will comply with any provisions of the General Requirements applicable thereto. 2. Contractor shall submit to City a monthly Project Schedule with a monthly progress payment for the duration of the Contract in accordance with the schedule specification 0132 16. 3. Proposed adjustments in the Project Schedule that will change the Contract Time shall be submitted in accordance with the requirements of Article 12. Adjustments in Contract Time may only be made by a Change Order. 6.05 Substitutes and "Or -Equals" A. Whenever an item of material or equipment is specified or described in the Contract Documents by using the name of a proprietary item or the name of a particular Supplier, the specification or description is intended to establish the type, function, appearance, and quality required. Unless the specification or description contains or is followed by words reading that no like, equivalent, or "or -equal" item or no substitution is permitted, other items of material or equipment of other Suppliers may be submitted to City for review under the circumstances described below. "Or -Equal "Items: If in City's sole discretion an item of material or equipment proposed by Contractor is functionally equal to that named and sufficiently similar so that no change in related Work will be required, it may be considered by City as an "or -equal" item, in which case review and approval of the proposed item may, in City's sole discretion, be accomplished without compliance with some or all of the requirements for approval of proposed substitute items. For the purposes of this Paragraph 6.05.A.1, a proposed item of material or equipment will be considered functionally equal to an item so named if: a. the City determines that: 1) it is at least equal in materials of construction, quality, durability, appearance, strength, and design characteristics; CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1— AD1 007200-1 GENERAL OONDITIONS Page 22 of 63 2) it will reliably perform at least equally well the function and achieve the results imposed by the design concept of the completed Project as a functioning whole; and 3) it has a proven record of performance and availability of responsive service; and b. Contractor certifies that, if approved and incorporated into the Work: 1) there will be no increase in cost to the City or increase in Contract Time; and 2) it will conform substantially to the detailed requirements of the item named in the Contract Documents. 2. Substitute Items: a. If in City's sole discretion an item of material or equipment proposed by Contractor does not qualify as an "or -equal" item under Paragraph 6.05.A.1, it may be submitted as a proposed substitute item. b. Contractor shall submit sufficient information as provided below to allow City to determine if the item of material or equipment proposed is essentially equivalent to that named and an acceptable substitute therefor. Requests for review of proposed substitute items of material or equipment will not be accepted by City from anyone other than Contractor. c. Contractor shall make written application to City for review of a proposed substitute item of material or equipment that Contractor seeks to furnish or use. The application shall comply with Section 0125 00 and: 1) shall certify that the proposed substitute item will: a) perform adequately the functions and achieve the results called for by the general design; b) be similar in substance to that specified; c) be suited to the same use as that specified; and 2) will state: a) the extent, if any, to which the use of the proposed substitute item will prejudice Contractor's achievement of final completion on time; b) whether use of the proposed substitute item in the Work will require a change in any of the Contract Documents (or in the provisions of any other direct contract with City for other work on the Project) to adapt the design to the proposed substitute item; CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1- AD1 007200-1 GENERAL OONDITIONS Page 23 of 63 c) whether incorporation or use of the proposed substitute item in connection with the Work is subject to payment of any license fee or royalty; and 3) will identify: a) all variations of the proposed substitute item from that specified; b) available engineering, sales, maintenance, repair, and replacement services; and 4) shall contain an itemized estimate of all costs or credits that will result directly or indirectly from use of such substitute item, including costs of redesign and Damage Claims of other contractors affected by any resulting change. B. Substitute Construction Methods or Procedures: If a specific means, method, technique, sequence, or procedure of construction is expressly required by the Contract Documents, Contractor may furnish or utilize a substitute means, method, technique, sequence, or procedure of construction approved by City. Contractor shall submit sufficient information to allow City, in City's sole discretion, to determine that the substitute proposed is equivalent to that expressly called for by the Contract Documents. Contractor shall make written application to City for review in the same manner as those provided in Paragraph 6.05.A.2. C. City's Evaluation: City will be allowed a reasonable time within which to evaluate each proposal or Submittal made pursuant to Paragraphs 6.05.A and 6.05.13. City may require Contractor to furnish additional data about the proposed substitute. City will be the sole judge of acceptability. No "or -equal" or substitute will be ordered, installed or utilized until City's review is complete, which will be evidenced by a Change Order in the case of a substitute and an accepted Submittal for an "or -equal." City will advise Contractor in writing of its determination. D. Special Guarantee: City may require Contractor to furnish at Contractor's expense a special performance guarantee, warranty, or other surety with respect to any substitute. Contractor shall indemnify and hold harmless City and anyone directly or indirectly employed by themfrom and against any and all claims, damages, losses and expenses (including attorneys fees) arising out of the use of substituted materials or equipment. E. City's Cost Reimbursement: City will record City's costs in evaluating a substitute proposed or submitted by Contractor pursuant to Paragraphs 6.05.A.2 and 6.05.13. Whether or not City approves a substitute so proposed or submitted by Contractor, Contractor may be required to reimburse City for evaluating each such proposed substitute. Contractor may also be required to reimburse City for the charges for making changes in the Contract Documents (or in the provisions of any other direct contract with City) resulting from the acceptance of each proposed substitute. F. Contractor's Expense: Contractor shall provide all data in support of any proposed substitute or "or -equal" at Contractor's expense. CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1- AD1 007200-1 GENERAL OONDITIONS Page 24 of 63 G. City Substitute Reimbursement: Costs (savings or charges) attributable to acceptance of a substitute shall be incorporated to the Contract by Change Order. H. Time Extensions: No additional time will be granted for substitutions. 6.06 Concerning Subcontractors, Suppliers, and Others A. Contractor shall perform with his own organization, work of a value not less than 35% of the value embraced on the Contract, unless otherwise approved by the City. B. Contractor shall not employ any Subcontractor, Supplier, or other individual or entity, whether initially or as a replacement, against whom City may have reasonable objection. Contractor shall not be required to employ any Subcontractor, Supplier, or other individual or entity to furnish or perform any of the Work against whom Contractor has reasonable objection (excluding those acceptable to City as indicated in Paragraph 6.06.C). C. The City may from time to time require the use of certain Subcontractors, Suppliers, or other individuals or entities on the project, and will provide such requirements in the Supplementary Conditions. D. Minority Business Enterprise Compliance: It is City policy to ensure the full and equitable participation by Minority Business Enterprises (MBE) in the procurement of goods and services on a contractual basis. If the Contract Documents provide for a MBE goal, Contractor is required to comply with the intent of the City's MBE Ordinance (as amended) by the following: 1. Contractor shall, upon request by City, provide complete and accurate information regarding actual work performed by a MBE on the Contract and payment therefor. 2. Contractor will not make additions, deletions, or substitutions of accepted MBE without written consent of the City. Any unjustified change or deletion shall be a material breach of Contract and may result in debarment in accordance with the procedures outlined in the Ordinance. 3. Contractor shall, upon request by City, allow an audit and/or examination of any books, records, or files in the possession of the Contractor that will substantiate the actual work performed by an MBE. Material misrepresentation of any nature will be grounds for termination of the Contract in accordance with Paragraph 15.02.A. Any such misrepresentation may be grounds for disqualification of Contractor to bid on future contracts with the City for a period of not less than three years. E. Contractor shall be fully responsible to City for all acts and omissions of the Subcontractors, Suppliers, and other individuals or entities performing or furnishing any of the Work just as Contractor is responsible for Contractor's own acts and omissions. Nothing in the Contract Documents: CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1— AD1 007200-1 GENERAL OONDITIONS Page 25 of 63 1. shall create for the benefit of any such Subcontractor, Supplier, or other individual or entity any contractual relationship between City and any such Subcontractor, Supplier or other individual or entity; nor 2. shall create any obligation on the part of City to pay or to see to the payment of any moneys due any such Subcontractor, Supplier, or other individual or entity except as may otherwise be required by Laws and Regulations. F. Contractor shall be solely responsible for scheduling and coordinating the Work of Subcontractors, Suppliers, and other individuals or entities performing or furnishing any of the Work under a direct or indirect contract with Contractor. G. All Subcontractors, Suppliers, and such other individuals or entities performing or furnishing any of the Work shall communicate with City through Contractor. H. All Work performed for Contractor by a Subcontractor or Supplier will be pursuant to an appropriate agreement between Contractor and the Subcontractor or Supplier which specifically binds the Subcontractor or Supplier to the applicable terms and conditions of the Contract Documents for the benefit of City. 6.07 Wage Rates A. Duty to pay Prevailing Wage Rates. The Contractor shall comply with all requirements of Chapter 2258, Texas Government Code (as amended), including the payment of not less than the rates determined by the City Council of the City of Fort Worth to be the prevailing wage rates in accordance with Chapter 2258. Such prevailing wage rates are included in these Contract Documents. B. Penalty for Violation. A Contractor or any Subcontractor who does not pay the prevailing wage shall, upon demand made by the City, pay to the City $60 for each worker employed for each calendar day or part of the day that the worker is paid less than the prevailing wage rates stipulate d in these contract documents. This penalty shall be retained by the City to offset its administrative costs, pursuant to Texas Government Code 2258.023. C. Complaints of Violations and City Determination of Good Cause. On receipt of information, including a complaint by a worker, concerning an alleged violation of 2258.023, Texas Government Code, by a Contractor or Subcontractor, the City shall make an initial determination, before the 31st day after the date the City receives the information, as to whether good cause exists to believe that the violation occurred. The City shall notify in writing the Contractor or Subcontractor and any affected worker of its initial determination. Upon the City's determination that there is good cause to believe the Contractor or Subcontractor has violated Chapter 2258, the City shall retain the full amounts claimed by the claimant or claimants as the difference betweenwages paid and wages due under the prevailing wage rates, such amounts being subtracted from successive progress payments pending a final determination of the violation. CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1— AD1 007200-1 GENERAL OONDITIONS Page 26 of 63 D. Arbitration Required if Violation NotResolved. An issue relating to an alleged violation of Section 2258.023, Texas Government Code, including a penalty owed to the City or an affected worker, shall be submitted to binding arbitration in accordance with the Texas General Arbitration Act (Article 224 et seq., Revised Statutes) if the Contractor or Subcontractor and any affected worker does not resolve the issue by agreementbefore the 15th day afterthe date the City makes its initial determination pursuant to Paragraph C above. If the persons required to arbitrate under this section do not agree on an arbitrator before the 1 lth day after the date that arbitration is required, a district court shall appoint an arbitrator on the petition of any of the persons. The City is not a party in the arbitration. The decision and award of the arbitrator is final and binding on all parties and may be enforced in any court of competent jurisdiction. E. Records to be Maintained. The Contractor and each Subcontractor shall, for a period of three (3) years following the date of acceptance of the work, maintain records that show (i) the name and occupation of each worker employed by the Contractor in the construction of the Work provided for in this Contract; and (ii) the actual per diem wages paid to each worker. The records shall be open at all reasonable hours for inspection by the City. The provisions of Paragraph 6.23, Right to Audit, shall pertain to this inspection. F. Progress Payments. With each progress payment or payroll period, whichever is less, the Contractor shall submit an affidavit stating that the Contractor has complied with the requirements of Chapter 2258, Texas Government Code. G. Posting of Wage Rates. The Contractor shall post prevailing wage rates in a conspicuous place at all times. H. Subcontractor Compliance. The Contractor shall include in its subcontracts and/or shall otherwise require all of its Subcontractors to comply with Paragraphs A through G above. 6.08 PatentFees and Royalties A. Contractor shall pay all license fees and royalties and assume all costs incident to the use in the performance of the Work or the incorporation in the Work of any invention, design, process, product, or device which is the subject of patent rights or copyrights held by others. If a particular invention, design, process, product, or device is specified in the Contract Documents for use in the performance of the Work and if, to the actual knowledge of City, its use is subject to patent rights or copyrights calling for the payment of any license fee or royalty to others, the existence of such rights shall be disclosed by City in the Contract Documents. Failure of the City to disclose such information does not relieve the Contractor from its obligations to pay for the use of said fees or royalties to others. B. To the fullest extent permitted by Laws and Regulations, Contractor shall indemnify and hold harmless City, from and against all claims, costs, losses, and damages (including but not limited to all fees and charges of engineers, architects, attorneys, and other professionals and all court or arbitration or other dispute resolution costs) arising out of or relating to any infringement of patent rights or copyrights incident to the use in the performance of the Work or resultingfrom CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1— AD1 007200-1 GENERAL OONDITIONS Page 27 of 63 the incorporation in the Work of any invention, design, process, product, or device not specified in the Contract Documents. 6.09 Permits and Utilities A. Contractor obtained permits and licenses. Contractor shall obtain and pay for all construction permits and licenses except those provided for in the Supplementary Conditions or Contract Documents. City shall assist Contractor, when necessary, in obtaining such permits and licenses. Contractor shall pay all governmental charges and inspection fees necessary for the prosecution of the Work which are applicable at the time of opening of Bids, or, if there are no Bids, on the Effective Date of the Agreement, except for permits provided by the City as specified in 6.09.B. City shall pay all charges of utility owners for connections for providing permanent service to the Work. B. City obtainedpermits and licenses. City will obtain and pay for all permits and licenses as provided for in the Supplementary Conditions or Contract Documents. It will be the Contractor's responsibility to carry out the provisions of the permit. If the Contractor initiates changes to the Contract and the City approves the changes, the Contractor is responsible for obtaining clearances and coordinating with the appropriate regulatory agency. The City will not reimburse the Contractor for any cost associated with these requirements of any City acquired permit. The following are permits the City will obtain if required: 1. Texas Department of Transportation Permits 2. U.S. Army Corps of Engineers Permits 3. Texas Commission on Environmental Quality Permits 4. Railroad Company Permits C. Outstanding permits and licenses. The City anticipates acquisition of and/or access to permits and licenses. Any outstanding permits and licenses are anticipated to be acquired in accordance with the schedule set forth in the Supplementary Conditions. The Project Schedule submitted by the Contractor in accordance with the Contract Documents must consider any outstanding permits and licenses. 6.10 Laws and Regulations A. Contractor shall give all notices required by and shall comply with all Laws and Regulations applicable to the performance of the Work. Except where otherwise expressly required by applicable Laws and Regulations, the City shall not be responsible for monitoring Contractor's compliance with any Laws or Regulations. B. If Contractor performs any Work knowing or having reason to know that it is contrary to Laws or Regulations, Contractor shall bear all claims, costs, losses, and damages (including but not limited to all fees and charges of engineers, architects, attorneys, and other professionals and all CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1— AD1 007200-1 GENERAL OONDITIONS Page 28 of 63 court or arbitration or other dispute resolution costs) arising out of or relating to such Work. However, it shall not be Contractor's responsibility to make certain that the Specifications and Drawings are in accordance with Laws and Regulations, but this shall not relieve Contractor of Contractor's obligations under Paragraph 3.02. C. Changes in Laws or Regulations not known at the time of opening of Bids having an effect on the cost or time of performance of the Work may be the subject of an adjustment in Contract Price or Contract Time. 6.11 Taxes A. On a contract awarded by the City, an organization which qualifies for exemption pursuant to Texas Tax Code, Subchapter H, Sections 151.301-335 (as amended), the Contractor may purchase, rent or lease all materials, supplies and equipment used or consumed in the performance of this contract by issuing to his supplier an exemption certificate in lieu of the tax, said exemption certificate to comply with State Comptroller's Ruling .007. Any such exemption certificate issued to the Contractor in lieu of the tax shall be subject to and shall comply with the provision of State Comptroller's Ruling .011, and any other applicable rulings pertaining to the Texas Tax Code, Subchapter H. B. Texas Tax permits and information may be obtained from: 1. Comptroller of Public Accounts Sales Tax Division Capitol Station Austin, TX 78711; or 2. http://www.window.state.tx.us/taxinfo/taxforms/93-forms.html 6.12 Use of Site and Other Areas A. Limitation on Use of Site and Other Areas: 1. Contractor shall confine construction equipment, the storage of materials and equipment, and the operations of workers to the Site and other areas permitted by Laws and Regulations, and shall not unreasonably encumber the Site and other areas with construction equipment or other materials or equipment. Contractor shall assume full responsibility for any damage to any such land or area, or to the owner or occupant thereof, or of any adjacent land or areas resulting from the performance of the Work. 2. At any time when, in the judgment of the City, the Contractor has obstructed or closed or is carrying on operations in a portion of a street, right-of-way, or easement greater than is necessary for proper execution of the Work, the City may require the Contractor to finish the section on which operations are in progress before work is commenced on any additional area of the Site. CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1— AD1 007200-1 GENERAL OONDITIONS Page 29 of 63 3. Should any Damage Claim be made by any such owner or occupant because of the performance of the Work, Contractor shall promptly attempt to resolve the Damage Claim. 4. Pursuant to Paragraph 6.21, Contractor shall indemnify and hold harmless City, from and against all claims, costs, losses, and damages arising out of or relating to any claim or action, legal or equitable, brought by any such owner or occupant against City. B. Removal of Debris During Performance of the Work: During the progress of the Work Contractor shall keep the Site and other areas free from accumulations of waste materials, rubbish, and other debris. Removal and disposal of such waste materials, rubbish, and other debris shall conform to applicable Laws and Regulations. C. Site Maintenance Cleaning: 24 hours after written notice is given to the Contractor that the clean-up on the job site is proceeding in a manner unsatisfactory to the City, if the Contractor fails to correct the unsatisfactory procedure, the City may take such direct action as the City deems appropriate to correct the clean-up deficiencies cited to the Contractor in the written notice (by letter or electronic communication), and the costs of such direct action, plus 25 % of such costs, shall be deducted from the monies due or to become due to the Contractor. D. Final Site Cleaning: Prior to Final Acceptance of the Work Contractor shall clean the Site and the Work and make it ready for utilization by City or adjacent property owner. At the completion of the Work Contractor shall remove from the Site all tools, appliances, construction equipment and machinery, and surplus materials and shall restore to original condition or better all property disturbed by the Work. E. Loading Structures: Contractor shall not load nor permit any part of any structure to be loaded in any manner that will endanger the structure, nor shall Contractor subject any part of the Work or adjacent property to stresses or pressures that will endanger it. 6.13 Record Documents A. Contractor shall maintain in a safe place at the Site or in a place designated by the Contractor and approved by the City, one (1) record copy of all Drawings, Specifications, Addenda, Change Orders, Field Orders, and written interpretations and clarifications in good order and annotated to show changes made during construction. These record documents together with all approved Samples and a counterpart of all accepted Submittals will be available to City for reference. Upon completion of the Work, these record documents, any operation and maintenance manuals, and Submittals will be delivered to City prior to Final Inspection. Contractor shall include accurate locations for buried and imbedded items. 6.14 Safety and Protection A. Contractor shall be solely responsible for initiating, maintaining and supervising all safety precautions and programs in connection with the Work. Such responsibility does not relieve Subcontractors of their responsibility for the safety of persons or property in the performance of their work, nor for compliance with applicable safety Laws and Regulations. Contractor shall CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1- AD1 007200-1 GENERAL OONDITIONS Page 30 of 63 take all necessary precautions for the safety of, and shall provide the necessary protection to prevent damage, injury or loss to: 1. all persons on the Site or who maybe affected by the Work; 2. all the Work and materials and equipment to be incorporated therein, whether in storage on or off the Site; and 3. other property at the Site or adjacent thereto, including trees, shrubs, lawns, walks, pavements, roadways, structures, utilities, and Underground Facilities not designated for removal, relocation, or replacement in the course of construction. B. Contractor shall comply with all applicable Laws and Regulations relating to the safety of persons or property, or to the protection of persons or property from damage, injury, or loss; and shall erect and maintain all necessary safeguards for such safety and protection. Contractor shall notify owners of adjacent property and of Underground Facilities and other utility owners when prosecution of the Work may affect them, and shall cooperate with them in the protection, removal, relocation, and replacement of their property. C. Contractor shall comply with the applicable requirements of City's safety programs, if any. D. Contractor shall inform City of the specific requirements of Contractor's safety program, if any, with which City's employees and representatives must comply while at the Site. E. All damage, injury, or loss to any property referredto in Paragraph6.14.A.2 or 6.14.A.3 caused, directly or indirectly, in whole or in part, by Contractor, any Subcontractor, Supplier, or any other individual or entity directly or indirectly employed by any of them to perform any of the Work, or anyone for whose acts any of them may be liable, shall be remedied by Contractor. F. Contractor's duties and responsibilities for safety and for protection of the Work shall continue until such time as all the Work is completed and City has accepted the Work. 6.15 Safety Representative Contractor shall inform City in writing of Contractor's designated safety representative at the Site. 6.16 Hazard Communication Programs Contractor shall be responsible for coordinating any exchange of material safety data sheets or other hazard communication information required to be made available to or exchanged between or among employers in accordance with Laws or Regulations. 6.17 Emergencies and/or Rectification A. In emergencies affecting the safety or protection of persons or the Work or property at the Site or adjacent thereto, Contractor is obligated to act to prevent threatened damage, injury, or loss. Contractor shall give City prompt written notice if Contractor believes that any significant CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1— AD1 007200-1 GENERAL OONDITIONS Page 31 of 63 changes in the Work or variations from the Contract Documents have been caused thereby or are required as a result thereof. If City determines that a change in the Contract Documents is required because of the action taken by Contractor in response to such an emergency, a Change Order may be issued. B. Should the Contractor fail to respond to a request from the City to rectify any discrepancies, omissions, or correction necessary to conform with the requirements of the Contract Documents, the City shall give the Contractor written notice that such work or changes are to be performed. The written notice shall direct attention to the discrepant condition and request the Contractor to take remedial action to correct the condition. In the event the Contractor does not take positive steps to fulfill this written request, or does not show just cause for not taking the proper action, within 24 hours, the City may take such remedial action with City forces or by contract. The City shall deduct an amount equal to the entire costs for such remedial action, plus 25%, from any funds due or become due the Contractor on the Project. 6.18 Submittals A. Contractor shall submit required Submittals to City for review and acceptance in accordance with the accepted Schedule of Submittals (as required by Paragraph 2.07). Each submittal will be identified as City may require. 1. Submit number of copies specified in the General Requirements. 2. Data shown on the Submittals will be complete with respect to quantities, dimensions, specified performance and design criteria, materials, and similar data to show City the services, materials, and equipment Contractor proposes to provide and to enable City to review the information for the limited purposes required by Paragraph 6.18.C. 3. Submittals submitted as herein provided by Contractor and reviewed by City for conformance with the design concept shall be executed in conformity with the Contract Documents unless otherwise required by City. 4. When Submittals are submitted for the purpose of showing the installation in greater detail, their review shall not excuse Contractor from requirements shown on the Drawings and Specifications. 5. For -Information -Only submittals upon which the City is not expected to conduct review or take responsive action may be so identified in the Contract Documents. 6. Submit required number of Samples specified in the Specifications. 7. Clearly identify each Sample as to material, Supplier, pertinent data such as catalog numbers, the use for which intended and other data as City may require to enable City to review the submittal for the limited purposes required by Paragraph 6.18.C. CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1- AD1 007200-1 GENERAL OONDITIONS Page 32 of 63 B. Where a Submittal is required by the Contract Documents or the Schedule of Submittals, any related Work performed prior to City's review and acceptance of the pertinent submittal will be at the sole expense and responsibility of Contractor. C. City's Review: 1. City will provide timely review of required Submittals in accordance with the Schedule of Submittals acceptable to City. City's review and acceptance will be only to determine if the items covered by the submittals will, after installation or incorporation in the Work, conform to the information given in the Contract Documents and be compatible with the design concept of the completed Project as a functioning whole as indicated by the Contract Documents. 2. City's review and acceptance will not extend to means, methods, techniques, sequences, or procedures of construction (except where a particular means, method, technique, sequence, or procedure of construction is specifically and expressly called for by the Contract Documents) or to safety precautions or programs incident thereto. The review and acceptance of a separate item as such will not indicate approval of the assembly in which the item functions. 3. City's review and acceptance shall not relieve Contractor from responsibility for any variation from the requirements of the Contract Documents unless Contractor has complied with the requirements of Section 01 33 00 and City has given written acceptance of each such variation by specific written notation thereof incorporated in or accompanying the Submittal. City's review and acceptance shall not relieve Contractor from responsibility for complying with the requirements of the Contract Documents. 6.19 Continuing the Work Except as otherwise provided, Contractor shall carry on the Work and adhere to the Project Schedule during all disputes or disagreements with City. No Work shall be delayed or postponed pending resolution of any disputes or disagreements, except as City and Contractor may otherwise agree in writing. 6.20 Contractor's General Warranty and Guarantee A. Contractor warrants and guarantees to City that all Work will be in accordance with the Contract Documents and will not be defective. City and its officers, directors, members, partners, employees, agents, consultants, and subcontractors shall be entitled to rely on representation of Contractor's warranty and guarantee. B. Contractor's warranty and guarantee hereunder excludes defects or damage caused by: 1. abuse, modification, or improper maintenance or operation by persons other than Contractor, Subcontractors, Suppliers, or any other individual or entity for whom Contractor is responsible; or CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1— AD1 007200-1 GENERAL CONDITIONS Page 33 of 63 2. normal wear and tear under normal usage. C. Contractor's obligation to perform and complete the Work in accordance with the Contract Documents shall be absolute. None of the following will constitute an acceptance of Work that is not in accordance with the Contract Documents or a release of Contractor's obligation to perform the Work in accordance with the Contract Documents: 1. observations by City; 2. recommendation or payment by City of any progress or final payment; 3. the issuance of a certificate of Final Acceptance by City or any payment related thereto by City; 4. use or occupancy of the Work or any part thereof by City; 5. any review and acceptance of a Submittal by City; 6. any inspection, test, or approval by others; or 7. any correction of defective Work by City. D. The Contractor shall remedy any defects or damages in the Work and pay for any damage to other work or property resulting therefrom which shall appear within a period of two (2) years from the date of Final Acceptance of the Work unless a longer period is specified and shall furnish a good and sufficient maintenance bond, complying with the requirements of Article 5.02.13. The City will give notice of observed defects with reasonable promptness. 6.21 Indemnification A. Contractor covenants and agrees to indemnify, hold harmless and defend, at its own expense, the City, its officers, servants and employees, from and against any and all claims arising out of, or alleged to arise out of, the work and services to be performed by the Contractor, its officers, agents, employees, subcontractors, licenses or invitees under this Contract. THIS iNDEMNi ICATiON PROVISION iS SPFCiFiCAi1V INTENDED TO OPERATE AND BF FFFECTiVE EVEN IF iT iS ALLEGED OR PROVEN THAT ALL OR SOME OF THE DAMAGES BEING: SOiJGIU WERE CAUSFD. iN WUQ,i,F ORIN PART, BY ANY ACTS OMISSION OR NE(T IGFNCF OF THE CiTY. This indemnity provision is intended to include, without limitation, indemnity for costs, expenses and legal fees incurred by the City in defending against such claims and causes of actions. B. Contractor covenants and agrees to indemnify and hold harmle s s, at its own expense, the City, its officers, servants and employees, from and against any and all loss, damage or destruction of property of the City, arising out of, or alleged to arise out of, the work and services to be performed by the Contractor, its officers, agents, employees, subcontractors, licensees or invitees under this Contract. ]MiS INDEMNIFICATION PROVISION iS CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: &23/202I ATTACHMENT 1— AD1 007200-1 GENERAL OONDITIONS Page 34 of 63 SPECIFICALLY INTENDED TO OPER 11"ND HE FUELTIVF, FVFN IF IT IS ALLEGED OR PROVEN THAT ALL OR SOME, OF THE. DAMAGES BEING SOIA MT WERE CAUSED- IN WHOL OR IN PART. BY ANY AC-L- OMISSION OR NEGLICFNCF OF THE CITY,. 6.22 Delegation of Professional Design Services A. Contractor will not be required to provide professional design services unless such services are specifically required by the Contract Documents for a portion of the Work or unless such services are required to carryout Contractor's responsibilities for construction means, methods, techniques, sequences and procedures. B. If professional design services or certifications by a design professional related to systems, materials or equipment are specifically required of Contractor by the Contract Documents, City will specify all performance and design criteria that such services must satisfy. Contractor shall cause such services or certifications to be provided by a properly licensed professional, whose signature and seal shall appear on all drawings, calculations, specifications, certifications, and Submittals prepared by such professional. Submittals related to the Work designed or certified by such professional, if prepared by others, shall bear such professional's written approval when submitted to City. C. City shall be entitled to rely upon the adequacy, accuracy and completeness of the services, certifications or approvals performed by such design professionals, provided City has specified to Contractor performance and design criteria that such services must satisfy. D. Pursuant to this Paragraph 6.22, City's review and acceptance of design calculations and design drawings will be only for the limited purpose of checking for conformance with performance and design criteria given and the design concept expressed in the Contract Documents. City's review and acceptance of Submittals (except design calculations and design drawings) will be only for the purpose stated in Paragraph 6.18.C. 6.23 Right to Audit A. The Contractor agrees that the City shall, until the expiration of three (3) years after final payment under this Contract, have access to and the right to examine and photocopy any directly pertinent books, documents, papers, and records of the Contractor involving transactions relating to this Contract. Contractor agrees that the City shall have access during Regular Working Hours to all necessary Contractor facilities and shall be provided adequate and appropriate work space in order to conduct audits in compliance with the provisions of this Paragraph. The City shall give Contractor reasonable advance notice of intended audits. B. Contractor further agrees to include in all its subcontracts hereunder a provision to the effect that the subcontractor agrees that the City shall, until the expiration of three (3) years after final payment under this Contract, have access to and the right to examine and photocopy any directly pertinent books, documents, papers, and records of such Subcontractor, involving transactions to the subcontract, and further, that City shall have access during Regular Working Hours to all CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1— AD1 007200-1 GENERAL OONDITIONS Page 35 of 63 Subcontractor facilities, and shall be provided adequate and appropriate work space in order to conduct audits in compliance with the provisions of this Paragraph. The City shall give Subcontractor reasonable advance notice of intended audits. C. Contractor and Subcontractor agree to photocopy such documents as may be requested by the City. The City agrees to reimburse Contractor for the cost of the copies as follows at the rate published in the Texas Administrative Code in effect as of the time copying is performed. 6.24 Nondiscrimination A. The City is responsible for operating Public Transportation Programs and implementing transit - related projects, which are funded in part with Federal financial assistance awarded by the U.S. Department of Transportation and the Federal Transit Administration (FTA), without discriminating against any person in the United States on the basis of race, color, or national origin. B. Title VI, Civil Rights Act of 1964 as amended: Contractor shall comply with the requirements of the Act and the Regulations as further defined in the Supplementary Conditions for any project receiving Federal assistance. ARTICLE 7 — OTHER WORK AT THE SITE 7.01 Related Work at Site A. City may perform other work related to the Project at the Site with City's employees, or other City contractors, or through other direct contracts therefor, or have other work performed by utility owners. If such other work is not noted in the Contract Documents, then written notice thereof will be given to Contractor prior to starting any such other work; and B. Contractor shall afford each other contractor who is a party to such a direct contract, each utility owner, and City, if City is performing other work with City's employees or other City contractors, proper and safe access to the Site, provide a reasonable opportunity for the introduction and storage of materials and equipment and the execution of such other work, and properly coordinate the Work with theirs. Contractor shall do all cutting, fitting, and patching of the Work that may be required to properly connect or otherwise make its several parts come together and properly integrate with such other work. Contractor shall not endanger any work of others by cutting, excavating, or otherwise altering such work; provided, however, that Contractor may cut or alter others' work with the written consent of City and the others whose work will be affected. C. If the proper execution or results of any part of Contractor's Work depends upon work performed by others under this Article 7, Contractor shall inspect such other work and promptly report to City in writing any delays, defects, or deficiencies in such other work that render it unavailable or unsuitable for the proper execution and results of Contractor's Work. Contractor's failure to so report will constitute an acceptance of such other work as fit and proper for integration with Contractor's Work except for latent defects in the work provided by others. CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1— AD1 007200-1 GENERAL CONDITIONS Page 36 of 63 7.02 Coordination A. If City intends to contract with others for the performance of other work on the Project at the Site, the following will be set forth in Supplementary Conditions: 1. the individual or entity who will have authority and responsibility for coordination of the activities among the various contractors will be identified; 2. the specific matters to be covered by such authority and responsibility will be itemized; and 3. the extent of such authority and responsibilities will be provided. B. Unless otherwise provided in the Supplementary Conditions, City shall have authority for such coordination. ARTICLE 8 — CITY'S RESPONSIBILITIES 8.01 Communications to Contractor Except as otherwise provided in the Supplementary Conditions, City shall issue all communications to Contractor. 8.02 Furnish Data City shall timely furnish the data required under the Contract Documents. 8.03 Pay When Due City shall make payments to Contractor in accordance with Article 14. 8.04 Lands and Easements; Reports and Tests City's duties with respect to providing lands and easements and providing engineering surveys to establish reference points are set forth in Paragraphs 4.01 and 4.05. Paragraph 4.02 refers to City's identifying and making available to Contractor copies of reports of explorations and tests of subsurface conditions and drawings of physical conditions relating to existing surface or subsurface structures at or contiguous to the Site that have been utilized by City in preparing the Contract Documents. 8.05 Change Orders City shall execute Change Orders in accordance with Paragraph 10.03. 8.06 Inspections, Tests, and Approvals City's responsibility with respect to certain inspections, tests, and approvals is set forth in Paragraph 13.03. CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: &23/2MI ATTACHMENT 1— AD1 007200-1 GENERAL OONDITIONS Page 37 of 63 8.07 Limitations on City's Responsibilities A. The City shall not supervise, direct, or have control or authority over, nor be responsible for, Contractor's means, methods, techniques, sequences, or procedures of construction, or the safety precautions and programs incident thereto, or for any failure of Contractor to comply with Laws and Regulations applicable to the performance of the Work. City will not be responsible for Contractor's failure to perform the Work in accordance with the Contract Documents. B. City will notify the Contractor of applicable safety plans pursuant to Paragraph 6.14. 8.08 Undisclosed Hazardous Environmental Condition City's responsibility with respect to an undisclosed Hazardous Environmental Condition is set forth in Paragraph 4.06. 8.09 Compliance with Safety Program While at the Site, City's employees and representatives shall comply with the specific applicable requirements of Contractor's safety programs of which City has been informed pursuant to Paragraph 6.14. ARTICLE 9 — CITY'S OBSERVATION STATUS DURING CONSTRUCTION 9.01 City's Project Manager City will provide one or more Project Manager(s) during the construction period. The duties and responsibilities and the limitations of authority of City's Project Manager during construction are set forth in the Contract Documents. The City's Project Manager for this Contract is identified in the Supplementary Conditions. 9.02 Visits to Site A. City's Project Manager will make visits to the Site at intervals appropriate to the various stages of construction as City deems necessary in order to observe the progress that has been made and the quality of the various aspects of Contractor's executed Work. Based on information obtained during such visits and observations, City's Project Manager will determine, in general, if the Work is proceeding in accordance with the Contract Documents. City's Project Manager will not be required to make exhaustive or continuous inspections on the Site to check the quality or quantity of the Work. City's Project Manager's efforts will be directed toward providing City a greater degree of confidence that the completed Work will conform generally to the Contract Documents. B. City's Project Manager's visits and observations are subject to all the limitations on authority and responsibility in the Contract Documents including those set forth in Paragraph 8.07. CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1— AD1 007200-1 GENERAL OONDITIONS Page 38 of 63 9.03 Authorized Variations in Work City's Project Manager may authorize minor variations in the Work from the requirements of the Contract Documents which do not involve an adjustment in the Contract Price or the Contract Time and are compatible with the design concept of the completed Project as a functioning whole as indicated by the Contract Documents. These may be accomplished by a Field Order and will be binding on City and also on Contractor, who shall perform the Work involved promptly. 9.04 Rejecting Defective Work City will have authority to reject Work which City's Project Manager believes to be defective, or will not produce a completed Project that conforms to the Contract Documents or that will prejudice the integrity of the design concept of the completed Project as a functioning whole as indicated by the Contract Documents. City will have authority to conduct special inspection or testing of the Work as provided in Article 13, whether or not the Work is fabricated, installed, or completed. 9.05 Determinations for Work Performed Contractor will determine the actual quantities and classifications of Work performed. City's Project Manager will review with Contractor the preliminary determinations on such matters before rendering a written recommendation. City's written decision will be final (except as modified to reflect changed factual conditions or more accurate data). 9.06 Decisions on Requirements of Contract Documents and Acceptability of Work A. City will be the initial interpreter of the requirements of the Contract Documents and judge of the acceptability of the Work thereunder. B. City will render a written decision on any issue referred. C. City's written decision on the issue referred will be final and binding on the Contractor, subject to the provisions of Paragraph 10.06. ARTICLE 10 — CHANGES IN THE WORK; CLAIMS; EXTRA WORK 10.01 Authorized Changes in the Work A. Without invalidating the Contract and without notice to any surety, City may, at any time or from time to time, order Extra Work. Upon notice of such Extra Work, Contractor shall promptly proceed with the Work involved which will be performed under the applicable conditions of the Contract Documents (except as otherwise specifically provided). Extra Work shall be memorialized by a Change Order which may or may not precede an order of Extra work. B. For minor changes of Work not requiring changes to Contract Time or Contract Price, a Field Order may be issued by the City. CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1— AD1 007200-1 GENERAL OONDITIONS Page 39 of 63 10.02 Unauthorized Changes in the Work Contractor shall not be entitled to an increase in the Contract Price or an extension of the Contract Time with respect to any work performed that is not required by the Contract Documents as amended, modified, or supplemented as provided in Paragraph 3.04, except in the case of an emergency as provided in Paragraph 6.17. 10.03 Execution of Change Orders A. City and Contractor shall execute appropriate Change Orders covering: changes in the Work which are: (i) ordered by City pursuant to Paragraph 10.01.A, (ii) required because of acceptance of defective Work under Paragraph 13.08 or City's correction of defective Work under Paragraph 13.09, or (iii) agreed to by the parties; 2. changes in the Contract Price or Contract Time which are agreed to by the parties, including any undisputed sum or amount of time for Work actually performed. 10.04 Extra Work A. Should a difference arise as to what does or does not constitute Extra Work, or as to the payment thereof, and the City insists upon its performance, the Contractor shall proceed with the work after making written request for written orders and shall keep accurate account of the actual reasonable cost thereof. Contract Claims regarding Extra Work shall be made pursuant to Paragraph 10.06. B. The Contractor shall furnish the City such installation records of all deviations from the original Contract Documents as may be necessary to enable the City to prepare for permanent record a corrected set of plans showing the actual installation. C. The compensation agreed upon for Extra Work whether or not initiated by a Change Order shall be a full, complete and final payment for all costs Contractor incurs as a result or relating to the change or Extra Work, whether said costs are known, unknown, foreseen or unforeseen at that time, including without limitation, any costs for delay, extended overhead, ripple or impact cost, or any other effect on changed or unchanged work as a result of the change or Extra Work. 10.05 Notification to Surety If the provisions of any bond require notice to be given to a surety of any change affecting the general scope of the Work or the provisions of the Contract Documents (including, but not limited to, Contract Price or Contract Time), the giving of any such notice will be Contractor's responsibility. The amount of each applicable bond will be adjusted by the Contractor to reflect the effect of any such change. CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1— AD1 007200-1 GENERAL OONDITIONS Page 40 of 63 10.06 Contract Claims Process A. City's Decision Required: All Contract Claims, except those waived pursuant to Paragraph 14.09, shall be referred to the City for decision. A decision by City shall be required as a condition precedent to any exercise by Contractor of any rights or remedies he may otherwise have under the Contract Documents or by Laws and Regulations in respect of such Contract Claims. B. Notice: 1. Written notice stating the general nature of each Contract Claim shall be delivered by the Contractor to City no later than 15 days after the start of the event giving rise thereto. The responsibility to substantiate a Contract Claim shall rest with the party making the Contract Claim. 2. Notice of the amount or extent of the Contract Claim, with supporting data shall be delivered to the City on or before 45 days from the start of the event giving rise thereto (unless the City allows additional time for Contractor to submit additional or more accurate data in support of such Contract Claim). 3. A Contract Claim for an adjustment in Contract Price shall be prepared in accordance with the provisions of Paragraph 12.01. 4. A Contract Claim for an adjustment in Contract Time shall be prepared in accordance with the provisions of Paragraph 12.02. 5. Each Contract Claim shall be accompanied by Contractor's written statement that the adjustment claimed is the entire adjustment to which the Contractor believes it is entitled as a result of said event. 6. The City shall submit any response to the Contractor within 30 days after receipt of the claimant's last submittal (unless Contract allows additional time). C. City's Action: City will review each Contract Claim and, within 30 days after receipt of the last submittal of the Contractor, if any, take one of the following actions in writing: 1. deny the Contract Claim in whole or in part; 2. approve the Contract Claim; or 3. notify the Contractor that the City is unable to resolve the Contract Claim if, in the City's sole discretion, it would be inappropriate for the City to do so. For purposes of further resolution of the Contract Claim, such notice shall be deemed a denial. CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1— AD1 007200-1 GENERAL OONDITIONS Page 41 of 63 D. City's written action under Paragraph 10.06.0 will be final and binding, unless City or Contractor invoke the dispute resolution procedure set forth in Article 16 within 30 days of such action or denial. E. No Contract Claim for an adjustment in Contract Price or Contract Time will be valid if not submitted in accordance with this Paragraph 10.06. ARTICLE 11— COST OF THE WORK; ALLOWANCES; UNIT PRICE WORK; PLANS QUANTITY MEASUREMENT 11.01 Cost of the Work A. Costs Included: The term Cost of the Work means the sum of all costs, except those excluded in Paragraph 11.0l.B, necessarily incurred and paid by Contractor in the proper performance of the Work. When the value of any Work covered by a Change Order, the costs to be reimbursed to Contractor will be only those additional or incremental costs required because of the change in the Work. Such costs shall not include any of the costs itemized in Paragraph 11.01.13, and shall include but not be limited to the following items: 1. Payroll costs for employees in the direct employ of Contractor in the performance of the Work under schedules of job classifications agreed upon by City and Contractor. Such employees shall include, without limitation, superintendents, foremen, and other personnel employed full time on the Work. Payroll costs for employees not employed full time on the Work shall be apportioned on the basis of their time spent on the Work. Payroll costs shall include; a. salaries with a 55% markup, or b. salaries and wages plus the cost of fringe benefits, which shall include social security contributions, unemployment, excise, and payroll taxes, workers' compensation, health and retirement benefits, bonuses, sick leave, vacation and holiday pay applicable thereto. The expenses of performing Work outside of Regular Working Hours, Weekend Working Hours, or legal holidays, shall be included in the above to the extent authorized by City. 2. Cost of all materials and equipment furnished and incorporated in the Work, including costs of transportation and storage thereof, and Suppliers' field services required in connection therewith. 3. Rentals of all construction equipment and machinery, and the parts thereof whether rented from Contractor or others in accordance with rental agreements approved by City, and the costs of transportation, loading, unloading, assembly, dismantling, and removal thereof. All such costs shall be in accordance with the terms of said rental agreements. The rental of any such equipment, machinery, or parts shall cease when the use thereof is no longer necessary for the Work. CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1- AD1 007200-1 GENERAL OONDITIONS Page 42 of 63 4. Payments made by Contractor to Subcontractors for Work performed by Subcontractors. If required by City, Contractor shall obtain competitive bids from subcontractors acceptable to City and Contractor and shall deliver such bids to City, who will then determine, which bids, if any, will be acceptable. If any subcontract provides that the Subcontractor is to be paid on the basis of Cost of the Work plus a fee, the Subcontractor's Cost of the Work and fee shall be determined in the same manner as Contractor's Cost of the Work and fee as provided in this Paragraph 11.01. 5. Costs of special consultants (including but not limited to engineers, architects, testing laboratories, surveyors, attorneys, and accountants) employed for services specifically related to the Work. 6. Supplemental costs including the following: a. The proportion of necessary transportation, travel, and subsistence expenses of Contractor's employees incurred in discharge of duties connected with the Work. b. Cost, including transportation and maintenance, of all materials, supplies, equipment, machinery, appliances, office, and temporary facilities at the Site, and hand tools not owned by the workers, which are consumed in the performance of the Work, and cost, less market value, of such items used but not consumed which remain the property of Contractor. c. Sales, consumer, use, and other similar taxes related to the Work, and for which Contractor is liable not covered under Paragraph 6.11, as imposed by Laws and Regulations. d. Deposits lost for causes other than negligence of Contractor, any Subcontractor, or anyone directly or indirectly employed by any of them or for whose acts any of them may be liable, and royalty payments and fees for permits and licenses. e. Losses and damages (and related expenses) caused by damage to the Work, not compensated by insurance or otherwise, sustained by Contractor in connection with the performance of the Work, provided such losses and damages have resulted from causes other than the negligence of Contractor, any Subcontractor, or anyone directly or indirectly employed by any of them or for whose acts any of them may be liable. Such losses shall include settlements made with the written consent and approval of City. No such losses, damages, and expenses shall be included in the Cost of the Work for the purpose of determining Contractor's fee. £ The cost of utilities, fuel, and sanitary facilities at the Site. g. Minor expenses such as telegrams, long distance telephone calls, telephone and communication services at the Site, express and courier services, and similar petty cash items in connection with the Work. CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1- AD1 007200-1 GENERAL OONDITIONS Page 43 of 63 h. The costs of premiums for all bonds and insurance Contractor is required by the Contract Documents to purchase and maintain. B. Costs Excluded: The term Cost of the Work shall not include any of the following items: 1. Payroll costs and other compensation of Contractor's officers, executives, principals (of partnerships and sole proprietorships), general managers, safety managers, engineers, architects, estimators, attorneys, auditors, accountants, purchasing and contracting agents, expediters, timekeepers, clerks, and other personnel employed by Contractor, whether at the Site or in Contractor's principal or branch office for general administration of the Work and not specifically included in the agreed upon schedule of job classifications referred to in Paragraph 11.01.A.1 or specifically covered by Paragraph 11.0LAA, all of which are to be considered administrative costs covered by the Contractor's fee. 2. Expenses of Contractor's principal and branch offices other than Contractor's office at the Site. 3. Any part of Contractor's capital expenses, including interest on Contractor's capital employed for the Work and charges against Contractor for delinquent payments. 4. Costs due to the negligence of Contractor, any Subcontractor, or anyone directly or indirectly employed by any of them or for whose acts any of them may be liable, including but not limited to, the correction of defective Work, disposal of materials or equipment wrongly supplied, and making good any damage to property. 5. Other overhead or general expense costs of any kind. C. Contractor's Fee: When all the Work is performed on the basis of cost-plus, Contractor's fee shall be determined as set forth in the Agreement. When the value of any Work covered by a Change Order for an adjustment in Contract Price is determined on the basis of Cost of the Work, Contractor's fee shall be determined as set forth in Paragraph 12.01.C. D. Documentation: Whenever the Cost of the Work for any purpose is to be determined pursuant to Paragraphs 11.01.A and 11.01.13, Contractor will establish and maintain records thereof in accordance with generally accepted accounting practices and submit in a form acceptable to City an itemized cost breakdown together with supporting data. 11.02 Allowances A. Specified Allowance: It is understood that Contractor has included in the Contract Price all allowances so named in the Contract Documents and shall cause the Work so covered to be performed for such sums and by such persons or entities as may be acceptable to City. B. Pre -bid Allowances: 1. Contractor agrees that: CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1— AD1 007200-1 GENERAL OONDITIONS Page 44 of 63 a. the pre -bid allowances include the cost to Contractor of materials and equipment required by the allowances to be delivered at the Site, and all applicable taxes; and b. Contractor's costs for unloading and handling on the Site, labor, installation, overhead, profit, and other expenses contemplated for the pre -bid allowances have been included in the allowances, and no demand for additional payment on account of any of the foregoing will be valid. C. ContingencyAllowance: Contractor agrees that a contingency allowance, if any, is for the sole use of City. D. Prior to final payment, an appropriate Change Order will be issued to reflect actual amounts due Contractor on account of Work covered by allowances, and the Contract Price shall be correspondingly adjusted. 11.03 Unit Price Work A. Where the Contract Documents provide that all or part of the Work is to be Unit Price Work, initially the Contract Price will be deemed to include for all Unit Price Work an amount equal to the sum of the unit price for each separately identified item of Unit Price Work times the estimated quantity of each item as indicated in the Agreement. B. The estimated quantities of items of Unit Price Work are not guaranteed and are solely for the purpose of comparison of Bids and determining an initial Contract Price. Determinations of the actual quantities and classifications of Unit Price Work performed by Contractor will be made by City subject to the provisions of Paragraph 9.05. C. Each unit price will be deemed to include an amount considered by Contractor to be adequate to cover Contractor's overhead and profit for each separately identified item. Work described in the Contract Documents, or reasonably inferred as required for a functionally complete installation, but not identified in the listing of unit price items shall be considered incidental to unit price work listed and the cost of incidental work included as part of the unit price. D. City may make an adjustment in the Contract Price in accordance with Paragraph 12.01 if: 1. the quantity of any item of Unit Price Work performed by Contractor differs materially and significantly from the estimated quantity of such item indicated in the Agreement; and 2. there is no corresponding adjustment with respect to any other item of Work. E. Increased or Decreased Quantities: The City reserves the right to order Extra Work in accordance with Paragraph 10.01. 1. If the changes in quantities or the alterations do not significantly change the character of work under the Contract Documents, the altered work will be paid for at the Contract unit price. CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1— ADl 007200-1 GENERAL OONDITIONS Page 45 of 63 2. If the changes in quantities or alterations significantly change the character of work, the Contract will be amended by a Change Order. 3. If no unit prices exist, this will be considered Extra Work and the Contract will be amended by a Change Order in accordance with Article 12. 4. A significant change in the character of work occurs when: a. the character of work for any Item as altered differs materially in kind or nature from that in the Contract or b. a Major Item of work varies by more than 25% from the original Contract quantity. 5. When the quantity of work to be done under any Major Item of the Contract is more than 125% of the original quantity stated in the Contract, then either party to the Contract may request an adjustment to the unit price on the portion of the work that is above 125%. 6. When the quantity of work to be done under any Major Item of the Contract is less than 75% of the original quantity stated in the Contract, then either party to the Contract may request an adjustment to the unit price. 11.04 Plans Quantity Measurement A. Plans quantities may or may not represent the exact quantity of work performed or material moved, handled, or placed during the execution of the Contract. The estimated bid quantities are designated as final payment quantities, unless revised by the governing Section or this Article. B. If the quantity measured as outlined under "Price and Payment Procedures" varies by more than 25% (or as stipulated under "Price and Payment Procedures" for specific Items) from the total estimated quantity for an individual Item originally shown in the Contract Documents, an adjustment may be made to the quantity of authorized work done for payment purposes. The party to the Contract requesting the adjustment will provide field measurements and calculations showing the final quantity for which payment will be made. Payment for revised quantity will be made at the unit price bid for that Item, except as provided for in Article 10. C. When quantities are revised by a change in design approved by the City, by Change Order, or to correct an error, or to correct an error on the plans, the plans quantity will be increasedor decreased by the amount involved in the change, and the 25% variance will apply to the new plans quantity. D. If the total Contract quantity multiplied by the unit price bid for an individual Item is less than $250 and the Item is not originally a plans quantity Item, then the Item may be paid as a plans quantity Item if the City and Contractor agree in writing to fix the final quantity as a plans quantity. CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1— AD1 007200-1 GENERAL OONDITIONS Page 46 of 63 E. For callout work or non -site specific Contracts, the plans quantity measurement requirements are not applicable. ARTICLE 12 — CHANGE OF CONTRACT PRICE; CHANGE OF CONTRACT TIME 12.01 Change of Contract Price A. The Contract Price may only be changed by a Change Order. B. The value of any Work covered by a Change Order will be determined as follows: 1. where the Work involved is covered by unit prices contained in the Contract Documents, by application of such unit prices to the quantities of the items involved (subject to the provisions of Paragraph 11.03); or 2. where the Work involved is not covered by unit prices contained in the Contract Documents, by a mutually agreed lump sum or unit price (which may include an allowance for overhead and profit not necessarily in accordance with Paragraph 12.0l.C.2), and shall include the cost of any secondary impacts that are foreseeable at the time of pricing the cost of Extra Work; or 3. where the Work involved is not covered by unit prices contained in the Contract Documents and agreement to a lump sum or unit price is not reached -under Paragraph 12.01.13.2, on the basis of the Cost of the Work (determined as provided in Paragraph 11.01) plus a Contractor's fee for overhead and profit (determined as provided in Paragraph 12.01.C). C. Contractor's Fee: The Contractor's additional fee for overhead and profit shall be determined as follows: 1. a mutually acceptable fixed fee; or 2. if a fixed fee is not agreed upon, then a fee based on the following percentages of the various portions of the Cost of the Work: a. for costs incurred under Paragraphs 11.0l.A.1, 11.0l.A.2. and 11.01.A.3, the Contractor's additional fee shall be 15 percent except for: 1) rental fees for Contractor's own equipment using standard rental rates; 2) bonds and insurance; b. for costs incurred under Paragraph 11.01.A.4 and 11.0l.A.5, the Contractor's fee shall be five percent (5%); 1) where one or more tiers of subcontracts are on the basis of Cost of the Work plus a fee and no fixed fee is agreed upon, the intent of Paragraphs 12.0l.C.2.a and 12.0l.C.2.b is that the Subcontractor who actually performs the Work, at whatever CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1— AD1 007200-1 GENERAL CONDITIONS Page 47 of 63 tier, will be paid a fee of 15 percent of the costs incurred by such Subcontractor under Paragraphs 11.0l.A.1 and 11.0l.A.2 and that any higher tier Subcontractor and Contractor will each be paid a fee of five percent (5%) of the amount paid to the next lower tier Subcontractor, however in no case shall the cumulative total of fees paid be in excess of 25%; c. no fee shall be payable on the basis of costs itemized under Paragraphs 11.0l.A.6, and 11.01.13; d. the amount of credit to be allowed by Contractor to City for any change which results in a net decrease in cost will be the amount of the actual net decrease in cost plus a deduction in Contractor's fee by an amount equal to five percent (5%) of such net decrease. 12.02 Change of Contract Time A. The Contract Time may only be changed by a Change Order. B. No extension of the Contract Time will be allowed for Extra Work or for claimed delay unless the Extra Work contemplated or claimed delay is shown to be on the critical path of the Project Schedule or Contractor can show by Critical Path Method analysis how the Extra Work or claime d delay adversely affects the critical path. 12.03 Delays A. Where Contractor is reasonably delayed in the performance or completion of any part of the Work within the Contract Time due to delay beyond the control of Contractor, the Contract Time may be extended in an amount equal to the time lost due to such delay if a Contract Claim is made therefor. Delays beyond the control of Contractor shall include, but not be limited to, acts or neglect by City, acts or neglect of utility owners or other contractors performing other work as contemplated by Article 7, fires, floods, epidemics, abnormal weather conditions, or acts of God. Such an adjustment shall be Contractor's sole and exclusive remedy for the delays described in this P aragraph. B. If Contractor is delayed, City shall not be liable to Contractor for any claims, costs, losses, or damages (including but not limited to all fees and charges of engineers, architects, attorneys, and other professionals and all court or arbitration or other dispute resolution costs) sustained by Contractor on or in connection with any other project or anticipated project. C. Contractor shall not be entitled to an adjustment in Contract Price or Contract Time for delays within the control of Contractor. Delays attributable to and within the control of a Subcontractor or Supplier shall be deemed to be delays within the control of Contractor. D. The Contractor shall receive no compensation for delays or hindrances to the Work, except when direct and unavoidable extra cost to the Contractor is caused by the failure of the City to provide information or material, if any, which is to be furnished by the City. CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: &23MI ATTACHMENT 1— AD1 007200-1 GENERAL OONDITIONS Page 48 of 63 ARTICLE 13 — TESTS AND INSPECTIONS; CORRECTION, REMOVAL OR ACCEPTANCE OF DEFECTIVE WORK 13.01 Notice ofDefects Notice of all defective Work of which City has actual knowledge will be given to Contractor. Defective Work may be rejected, corrected, or accepted as provided in this Article 13. 13.02 Access to Work City, independent testing laboratories, and governmental agencies with jurisdictional interests will have access to the Site and the Work at reasonable times for their observation, inspection, and testing. Contractor shall provide them proper and safe conditions for such access and advise them of Contractor's safety procedures and programs so that they may comply therewith as applicable. 13.03 Tests and Inspections A. Contractor shall give City timely notice of readiness of the Work for all required inspections, tests, or approvals and shall cooperate with inspection and testing personnel to facilitate required inspections or tests. B. If Contract Documents, Laws or Regulations of any public body having jurisdiction require any of the Work (or part thereof) to be inspected, tested, or approved, Contractor shall assume full responsibility for arranging and obtaining such independent inspections, tests, retests or approvals, pay all costs in connection therewith, and furnish City the required certificates of inspection or approval; excepting, however, those fees specifically identified in the Supplementary Conditions or any Texas Department of Licensure and Regulation (TDLR) inspections, which shall be paid as described in the Supplementary Conditions. C. Contractor shall be responsible for arranging and obtaining and shall pay all costs in connection with any inspections, tests, re -tests, or approvals required for City's acceptance of materials or equipment to be incorporated in the Work; or acceptance of materials, mix designs, or equipment submitted for approval prior to Contractor's purchase thereof for incorporation in the Work. Such inspections, tests, re -tests, or approvals shall be performed by organizations acceptable to City. D. City may arrange for the services of an independent testing laboratory ("Testing Lab") to perform any inspections or tests ("Testing") for any part of the Work, as determined solely by City. 1. City will coordinate such Testing to the extent possible, with Contractor; 2. Should any Testing under this Section 13.03 D result in a "fail", "did not pass" or other similar negative result, the Contractor shall be responsible for paying for any and all retests. Contractor's cancellation without cause of City initiated Testing shall be deemed a negative result and require a retest. CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1— AD1 007200-1 GENERAL OONDITIONS Page 49 of 63 3. Any amounts owed for any retest under this Section 13.03 D shall be paid directly to the Testing Lab by Contractor. City will forward all invoices for retests to Contractor. 4. If Contractor fails to pay the Testing Lab, City will not issue Final Payment until the Testing Lab is paid. E. If any Work (or the work of others) that is to be inspected, tested, or approved is covered by Contractor without written concurrence of City, Contractor shall, if requested by City, uncover such Work for observation. F. Uncovering Work as provided in Paragraph 13.03.E shall be at Contractor's expense. G. Contractor shall have the right to make a Contract Claim regarding any retest or invoice issued under Section 13.03 D. 13.04 Uncovering Work A. If any Work is covered contrary to the Contract Documents or specific instructions by the City, it must, if requested by City, be uncovered for City's observation and replaced at Contractor's expense. B. If City considers it necessary or advisable that covered Work be observed by City or inspected or tested by others, Contractor, at City's request, shall uncover, expose, or otherwise make available for observation, inspection, or testing as City may require, that portion of the Work in question, furnishing all necessary labor, material, and equipment. 1. If it is found that the uncovered Work is defective, Contractor shall pay all claims, costs, losses, and damages (including but not limited to all fees and charges of engineers, architects, attorneys, and other professionals and all court or other dispute resolution costs) arising out of or relating to such uncovering, exposure, observation, inspection, and testing, and of satisfactory replacement or reconstruction (including but not limited to all costs of repair or replacement of work of others); or City shall be entitled to accept defective Work in accordance with Paragraph 13.08 in which case Contractor shall still be responsible for all costs associated with exposing, observing, and testing the defective Work. 2. If the uncovered Work is not found to be defective, Contractor shall be allowed an increase in the Contract Price or an extension of the Contract Time, or both, directly attributable to such uncovering, exposure, observation, inspection, testing, replacement, and reconstruction. 13.05 City May Stop the Work If the Work is defective, or Contractor fails to supply sufficient skilled workers or suitable materials or equipment, or fails to perform the Work in such a way that the completed Work will conform to the Contract Documents, City may order Contractor to stop the Work, or any portion thereof, until the cause for such order has been eliminated; however, this right of City to stop the Work shall not give rise to any duty on the part of City to exercise this right for the benefit of Contractor, any CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1— AD1 007200-1 GENERAL OONDITIONS Page 50 of 63 Subcontractor, any Supplier, any other individual or entity, or any surety for, or employee or agent of any of them. 13.06 Correction orRemoval of Defective Work A. Promptly after receipt of written notice, Contractor shall correct all defective Work pursuant to an acceptable schedule, whether or not fabricated, installed, or completed, or, if the Work has been rejected by City, remove it from the Project and replace it with Work that is not defective. Contractor shall pay all claims, costs, additional testing, losses, and damages (including but not limited to all fees and charges of engineers, architects, attorneys, and other professionals and all court or arbitration or other dispute resolution costs) arising out of or relating to such correction or removal (including but not limited to all costs of repair or replacement of work of others). Failure to require the removal of any defective Work shall not constitute acceptance of such Work. B. When correcting defective Work under the terms of this Paragraph 13.06 or Paragraph 13.07, Contractor shall take no action that would void or otherwise impair City's special warranty and guarantee, if any, on said Work. 13.07 Correction Period A. If within two (2) years after the date of Final Acceptance (or such longer period of time as may be prescribed by the terms of any applicable special guarantee required by the Contract Documents), any Work is found to be defective, or if the repair of any damages to the land or areas made available for Contractor's use by City or permitted by Laws and Regulations as contemplated in Paragraph 6.10.A is found to be defective, Contractor shall promptly, without cost to City and in accordance with City's written instructions: 1. repair such defective land or areas; or 2. correct such defective Work; or 3. if the defective Work has been rejected by City, remove it from the Project and replace it with Work that is not defective, and 4. satisfactorily correct or repair or remove and replace any damage to other Work, to the work of others or other land or areas resulting therefrom. B. If Contractor does not promptly comply with the terms of City's written instructions, or in an emergency where delay would cause serious risk of loss or damage, City may have the defective Work corrected or repaired or may have the rejected Work removed and replaced. All claims, costs, losses, and damages (including but not limited to all fees and charges of engineers, architects, attorneys, and other professionals and all court or other dispute resolution costs) arising out of or relating to such correction or repair or such removal and replacement (including but not limited to all costs of repair or replacement of work of others) will be paid by Contractor. CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1— AD1 007200-1 GENERAL OONDITIONS Page 51 of 63 C. In special circumstances where a particular item of equipment is placed in continuous service before Final Acceptance of all the Work, the correction period for that item may start to run from an earlier date if so provided in the Contract Documents. D. Where defective Work (and damage to other Work resulting therefrom) has been corrected or removed and replaced under this Paragraph 13.07, the correction period hereunder with respect to such Work may be required to be extended for an additional period of one year after the end of the initial correction period. City shall provide 30 days written notice to Contractor should such additional warranty coverage be required. Contractor may dispute this requirement by filing a Contract Claim, pursuant to Paragraph 10.06. E. Contractor's obligations under this Paragraph 13.07 are in addition to any other obligation or warranty. The provisions of this Paragraph 13.07 shall not be construed as a substitute for, or a waiver of, the provisions of any applicable statute of limitation or repose. 13.08 Acceptance of Defective Work If, instead of requiring correction or removal and replacement of defective Work, City prefers to accept it, City may do so. Contractor shall pay all claims, costs, losses, and damages (including but not limited to all fees and charges of engineers, architects, attorneys, and other professionals and all court or other dispute resolution costs) attributable to City's evaluation of and determination to accept such defective Work and for the diminished value of the Work to the extent not otherwise paid by Contractor. If any such acceptance occurs prior to Final Acceptance, a Change Order will be issued incorporating the necessary revisions in the Contract Documents with respect to the Work, and City shall be entitled to an appropriate decrease in the Contract Price, reflecting the diminished value of Work so accepted. 13.09 City May Correct Defective Work A. If Contractor fails within a reasonable time after written notice from City to correct defective Work, or to remove and replace rejected Work as required by City in accordance with Paragraph 13.06.A, or if Contractor fails to perform the Work in accordance with the Contract Documents, or if Contractor fails to comply with any other provision of the Contract Documents, City may, after seven (7) days written notice to Contractor, correct, or remedy any such deficiency. B. In exercising the rights and remedies under this Paragraph 13.09, City shall proceed expeditiously. In connection with such corrective or remedial action, City may exclude Contractor from all or part of the Site, take possession of all or part of the Work and suspend Contractor's services related thereto, and incorporate in the Work all materials and equipment incorporated in the Work, stored at the Site or for which City has paid Contractor but which are stored elsewhere. Contractor shall allow City, City's representatives, agents, consultants, employees, and City's other contractors, access to the Site to enable City to exercise the rights and remedies under this Paragraph. C. All claims, costs, losses, and damages (including but not limited to all fees and charges of engineers, architects, attorneys, and other professionals and all court or other dispute resolution CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1— AD1 007200-1 GENERAL OONDITIONS Page 52 of 63 costs) incurred or sustained by City in exercising the rights and remedies under this Paragraph 13.09 will be charged against Contractor, and a Change Order will be issued incorporating the necessary revisions in the Contract Documents with respect to the Work; and City shall be entitled to an appropriate decrease in the Contract Price. D. Contractor shall not be allowed an extension of the Contract Time because of any delay in the performance of the Work attributable to the exercise of City's rights and remedies under this Paragraph 13.09. ARTICLE 14 — PAYMENTS TO CONTRACTOR AND COMPLETION 14.01 Schedule of Values The Schedule of Values for lump sum contracts established as provided in Paragraph 2.07 will serve as the basis for progress payments and will be incorporated into a form of Application for Payment acceptable to City. Progress payments on account of Unit Price Work will be based on the number of units completed. 14.02 Progress Payments A. ApplicationsforPayments: 1. Contractor is responsible for providing all information as required to become a vendor of the City. 2. At least 20 days before the date established in the General Requirements for each progress payment, Contractor shall submit to City for review an Application for Payment filled out and signed by Contractor covering the Work completed as of the date of the Application and accompanied by such supporting documentation as is required by the Contract Documents. 3. If payment is requested on the basis of materials and equipment not incorporated in the Work but delivered and suitably stored at the Site or at another location agreed to in writing, the Application for Payment shall also be accompanied by a bill of sale, invoice, or other documentation warranting that City has received the materials and equipment free and clear of all Liens and evidence that the materials and equipment are covered by appropriate insurance or other arrangements to protect City's interest therein, all of which must be satisfactory to City. 4. Beginning with the second Application for Payment, each Application shall include an affidavit of Contractor stating that previous progress payments received on account of the Work have been applied on account to discharge Contractor's legitimate obligations associated with prior Applications for Payment. 5. The amount of retainage with respect to progress payments will be as described in subsection C. unless otherwise stipulated in the Contract Documents. CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1— AD1 007200-1 GENERAL OONDITIONS Page 53 of 63 B. Review of Applications: 1. City will, after receipt of each Application for Payment, either indicate in writing a recommendation of payment or return the Application to Contractor indicating reasons for refusing payment. In the latter case, Contractor may make the necessary corrections and resubmit the Application. 2. City's processing of any payment requested in an Application for Payment will be based on City's observations of the executed Work, and on City's review of the Application for Payment and the accompanying data and schedules, that to the best of City's knowledge: a. the Work has progressed to the point indicated; b. the quality of the Work is generally in accordance with the Contract Documents (subject to an evaluation of the Work as a functioning whole prior to or upon Final Acceptance, the results of any subsequent tests called for in the Contract Documents, a final determination of quantities and classifications for Work performed under Paragraph 9.05, and any other qualifications stated in the recommendation). 3. Processing any such payment will not thereby be deemed to have represented that: a. inspections made to check the quality or the quantity of the Work as it has been performed have been exhaustive, extended to every aspect of the Work in progress, or involved detailed inspections of the Work beyond the responsibilities specifically assigned to City in the Contract Documents; or b. there may not be other matters or issues between the parties that might entitle Contractor to be paid additionally by City or entitle City to withhold payment to Contractor; or c. Contractor has complied with Laws and Regulations applicable to Contractor's performance of the Work. 4. City may refuse to process the whole or any part of any payment because of subsequently discovered evidence or the results of subsequent inspections or tests, and revise or revoke any such payment previously made, to such extent as may be necessary to protect City from loss because: a. the Work is defective or completed Work has been damaged by the Contractor or subcontractors requiring correction or replacement; b. discrepancies in quantities contained in previous applications for payment; c. the Contract Price has been reduced by Change Orders; d. City has been required to correct defective Work or complete Work in accordance with Paragraph 13.09; or CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1— AD1 007200-1 GENERAL CONDITIONS Page 54 of 63 e. City has actual knowledge of the occurrence of any of the events enumerated in Paragraph 15.02.A. C. Retainage: 1. For contracts less than $400,000 at the time of execution, retainage shall be ten percent (10%). 2. For contracts greater than $400,000 at the time of execution, retainage shall be five percent (5%). D. Liquidated Damages. For each calendar day that any work shall remain uncompleted after the time specified in the Contract Documents, the sum per day specified in the Agreement will be assessed against the monies due the Contractor, not as a penalty, but as damages suffered by the City. E. Payment: Contractor will be paid pursuant to the requirements of this Article 14 and payment will become due in accordance with the Contract Documents. F. Reduction in Payment: 1. City may refuse to make payment of the amount requested because: a. Liens have been filed in connection with the Work, except where Contractor has delivered a specific bond satisfactory to City to secure the satisfaction and discharge of such Liens; b. there are other items entitling City to a set-off against the amount recommended; or c. City has actual knowledge of the occurrence of any of the events enumerated in Paragraphs 14.02.B.4.a through 14.02.B.4.e or Paragraph 15.02.A. 2. If City refuses to make payment of the amount requested, City will give Contractor written notice stating the reasons for such action and pay Contractor any amount remaining after deduction of the amount so withheld. City shall pay Contractor the amount so withheld, or any adjustment thereto agreed to by City and Contractor, when Contractor remedies the reasons for such action. 14.03 Contractor's Warranty of Title Contractor warrants and guarantees that title to all Work, materials, and equipment covered by any Application for Payment, whether incorporated in the Project or not, will pass to City no later than the time of payment free and clear of all Liens. CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: &23/202I ATTACHMENT 1— AD1 007200-1 GENERAL OONDITIONS Page 55 of 63 14.04 Partial Utilization A. Prior to Final Acceptance of all the Work, City may use or occupy any part of the Work which has specifically been identified in the Contract Documents, or which City determines constitutes a separately functioning and usable part of the Work that can be used for its intended purpose without significant interference with Contractor's performance of the remainder of the Work. City at any time may notify Contractor in writing to permit City to use or occupy any such part of the Work which City determines to be ready for its intended use, subject to the following conditions: 1. Contractor at any time may notify City in writing that Contractor considers any such part of the Work ready for its intended use. 2. Within a reasonable time after notification as enumerated in Paragraph 14.05.A.1, City and Contractor shall make an inspection of that part of the Work to determine its status of completion. If City does not consider that part of the Work to be substantially complete, City will notify Contractor in writing giving the reasons therefor. 3. Partial Utilization will not constitute Final Acceptance by City. 14.05 Finallnspection A. Upon written notice from Contractor that the entire Work is Substantially Complete in accordance with the Contract Documents: 1. Within 10 days, City will schedule a Final Inspection with Contractor. 2. City will notify Contractor in writing of all particulars in which this inspection reveals that the Work is incomplete or defective ("Punch List Items"). Contractor shall immediately take such measures as are necessary to complete such Work or remedy such deficiencies. B. No time charge will be made against the Contractor between said date of notification to the City of Substantial Completion and the date of Final Inspection. 1. Should the City determine that the Work is not ready for Final Inspection, City will notify the Contractor in writing of the reasons and Contract Time will resume. 2. Should the City concur that Substantial Completion has been achieved with the exception of any Punch List Items, Contract Time will resume for the duration it takes for Contractor to achieve Final Acceptance. 14.06 Final Acceptance Upon completion by Contractor to City's satisfaction, of any additional Work identified in the Final Inspection, City will issue to Contractor a letter of Final Acceptance. CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1— AD1 007200-1 GENERAL CONDITIONS Page 56 of 63 14.07 Final Payment A. ApplicationforPayment: Upon Final Acceptance, and in the opinion of City, Contractor may make an application for final payment following the procedure for progress payments in accordance with the Contract Documents. 2. The final Application for Payment shall be accompanied (except as previously delivered) by: a. all documentation called for in the Contract Documents, including but not limited to the evidence of insurance required by Paragraph 5.03; b. consent of the surety, if any, to final payment; c. a list of all pending or released Damage Claims against City that Contractor believes are unsettled; and d. affidavits of payments and complete and legally effective releases or waivers (satisfactory to City) of all Lien rights arising out of or Liens filed in connection with the Work. B. Payment Becomes Due.• 1. After City's acceptance of the Application for Payment and accompanying documentation, requested by Contractor, less previous payments made and any sum City is entitled, including but not limited to liquidated damages, will become due and payable. 2. After all Damage Claims have been resolved: a. directly by the Contractor or; b. Contractor provides evidence that the Damage Claim has been reported to Contractor's insurance provider for resolution. 3. The making of the final payment by the City shall not relieve the Contractor of any guarantees or other requirements of the Contract Documents which specifically continue thereafter. 14.08 Final Completion Delayed and Partial Retain age Release A. If final completion of the Work is significantly delayed, and if City so confirms, City may, upon receipt of Contractor's final Application for Payment, and without terminating the Contract, make payment of the balance due for that portion of the Work fully completed and accepted. If the remaining balance to be held by City for Work not fully completed or corrected is less than the retainage stipulated in Paragraph 14.02.C, and if bonds have been furnished as required in Paragraph 5.02, the written consent of the surety to the payment of the balance due for that CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: &23/202I ATTACHMENT 1— AD1 007200-1 GENERAL OONDITIONS Page 57 of 63 portion of the Work fully completed and accepted shall be submitted by Contractor to City with the Application for such payment. Such payment shall be made under the terms and conditions governing final payment, except that it shall not constitute a waiver of Contract Claims. B. Partial Retainage Release. For a Contract that provides for a separate vegetative establishment and maintenance, and test and performance periods following the completion of all other construction in the Contract Documents for all Work locations, the City may release a portion of the amount retained provided that all other work is completed as determined by the City. Before the release, all submittals and final quantities must be completed and accepted for all other work. An amount sufficient to ensure Contract compliance will be retained. 14.09 Waiver of Claims The acceptance of final payment will constitute a release of the City from all claims or liabilities under the Contract for anything done or furnished or relating to the work under the Contract Documents or any act or neglect of City related to or connected with the Contract. ARTICLE 15 — SUSPENSION OF WORK AND TERMINATION 15.01 City May Suspend Work A. At any time and without cause, City may suspend the Work or any portion thereof by written notice to Contractor and which may fix the date on which Work will be resumed. Contractor shall resume the Work on the date so fixed. During temporary suspension of the Work covered by these Contract Documents, for any reason, the City will make no extra payment for stand-by time of construction equipment and/or construction crews. B. Should the Contractor not be able to complete a portion of the Project due to causes beyond the control of and without the fault or negligence of the Contractor, and should it be determined by mutual consent of the Contractor and City that a solution to allow construction to proceed is not available within a reasonable period of time, Contractor may request an extension in Contract Time, directly attributable to any such suspension. C. If it should become necessary to suspend the Work for an indefinite period, the Contractor shall store all materials in such a manner that they will not obstruct or impede the public unnecessarily nor become damaged in any way, and he shall take every precaution to prevent damage or deterioration of the work performed; he shall provide suitable drainage about the work, and erect temporary structures where necessary. D. Contractor may be reimbursed for the cost of moving his equipment off the job and returning the necessary equipment to the job when it is determined by the City that construction may be resumed. Such reimbursement shall be based on actual cost to the Contractor of moving the equipment and no profit will be allowed. Reimbursement may not be allowed if the equipment is moved to another construction project for the City. CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1— AD1 007200-1 GENERAL OONDITIONS Page 58 of 63 15.02 City May Terminate for Cause A. The occurrence of any one or more of the following events by way of example, but not of limitation, may justify termination for cause: 1. Contractor's persistent failure to perform the Work in accordance with the Contract Documents (including, but not limited to, failure to supply sufficient skilled workers or suitable materials or equipment, failure to adhere to the Project Schedule established under Paragraph 2.07 as adjusted from time to time pursuant to Paragraph 6.04, or failure to adhere to the City's Business Diversity Enterprise Ordinance #20020-12-201lestablished under Paragraph 6.06.D); 2. Contractor's disregard of Laws or Regulations of any public body having jurisdiction; 3. Contractor's repeated disregard of the authority of City; or 4. Contractor's violation in any substantial way of any provisions of the Contract Documents; or 5. Contractor's failure to promptly make good any defect in materials or workmanship, or defects of any nature, the correction of which has been directed in writing by the City; or 6. Substantial indication that the Contractor has made an unauthorized assignment of the Contract or any funds due therefrom for the benefit of any creditor or for any other purpose; or 7. Substantial evidence that the Contractor has become insolvent or bankrupt, or otherwise financially unable to carry on the Work satisfactorily; or 8. Contractor commences legal action in a court of competent jurisdiction against the City. B. If one or more of the events identified in Paragraph 15.02A. occur, City will provide written notice to Contractor and Surety to arrange a conference with Contractor and Surety to address Contractor's failure to perform the Work. Conference shall be held not later than 15 days, after receipt of notice. 1. If the City, the Contractor, and the Surety do not agree to allow the Contractor to proceed to perform the construction Contract, the City may, to the extent permitted by Laws and Regulations, declare a Contractor default and formally terminate the Contractor's right to complete the Contract. Contractor default shall not be declared earlier than 20 days after the Contractor and Surety have received notice of conference to address Contractor's failure to perform the Work. 2. If Contractor's services are terminated, Surety shall be obligated to take over and perform the Work. If Surety does not commence performance thereof within 15 consecutive calendar days after date of an additional written notice demanding Surety's performance of its CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1— AD1 007200-1 GENERAL OONDITIONS Page 59 of 63 obligations, then City, without process or action at law, may take over any portion of the Work and complete it as described below. a. If City completes the Work, City may exclude Contractor and Surety from the site and take possession of the Work, and all materials and equipment incorporated into the Work stored at the Site or for which City has paid Contractor or Surety but which are stored elsewhere, and finish the Work as City may deem expedient. 3. Whether City or Surety completes the Work, Contractor shall not be entitled to receive any further payment until the Work is finished. If the unpaid balance of the Contract Price exceeds all claims, costs, losses and damages sustained by City arising out of or resulting from completing the Work, such excess will be paid to Contractor. If such claims, costs, losses and damages exceedsuch unpaid balance, Contractor shall pay the difference to City. Such claims, costs, losses and damages incurred by City will be incorporated in a Change Order, provided that when exercising any rights or remedies under this Paragraph, City shall not be required to obtain the lowest price for the Work performed. 4. Neither City, nor any of its respective consultants, agents, officers, directors or employees shall be in any way liable or accountable to Contractor or Surety for the method by which the completion of the said Work, or any portion thereof, may be accomplished or for the price paid therefor. City, notwithstanding the method used in completing the Contract, shall not forfeit the right to recover damages from Contractor or Surety for Contractor's failure to timely complete the entire Contract. Contractor shall not be entitled to any claim on account of the method used by City in completing the Contract. 6. Maintenance of the Work shall continue to be Contractor's and Surety's responsibilities as provided for in the bond requirements of the Contract Documents or any special guarantees provided for under the Contract Documents or any other obligations otherwise prescribed by law. C. Notwithstanding Paragraphs 15.02.13, Contractor's services will not be terminated if Contractor begins within seven days of receipt of notice of intent to terminate to correct its failure to perform and proceeds diligently to cure such failure within no more than 30 days of receipt of said notice. D. Where Contractor's services have been so terminated by City, the termination will not affect any rights or remedies of City against Contractor then existing or which may thereafter accrue. Any retention or payment of moneys due Contractor by City will not release Contractor from liability. E. If and to the extent that Contractor has provided a performance bond under the provisions of Paragraph 5.02, the termination procedures of that bond shall not supersede the provisions of this Article. CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1- AD1 007200-1 GENERAL OONDITIONS Page 60 of 63 15.03 City May Terminate For Convenience A. City may, without cause and without prejudice to any other right or remedy of City, terminate the Contract. Any termination shall be effectedby mailing a notice of the termination to the Contractor specifying the extent to which performance of Work under the contract is terminated, and the date upon which such termination becomes effective. Receipt of the notice shall be deemed conclusively presumed and established when the letter is placed in the United States Postal Service Mail by the City. Further, it shall be deemed conclusively presumed and established that such termination is made with just cause as therein stated; and no proof in any claim, demand or suit shall be required of the City regarding such discretionary action. B. After receipt of a notice of termination, and except as otherwise directed by the City, the Contractor shall: 1. Stop work under the Contract on the date and to the extent specified in the notice of termination; 2. place no further orders or subcontracts for materials, services or facilities except as may be necessary for completion of such portion of the Work under the Contract as is not terminated; 3. terminate all orders and subcontracts to the extent that they relate to the performance of the Work terminated by notice of termination; 4. transfer title to the City and deliver in the manner, at the times, and to the extent, if any, directed by the City: a. the fabricated or unfabricated parts, Work in progress, completed Work, supplies and other material produced as a part of, or acquired in connection with the performance of, the Work terminated by the notice of the termination; and b. the completed, or partially completed plans, drawings, information and other property which, if the Contract had been completed, would have been required to be furnished to the City. 5. complete performance of such Work as shall not have been terminated by the notice of termination; and 6. take such action as may be necessary, or as the City may direct, for the protection and preservation of the property related to its contract which is in the possession of the Contractor and in which the owner has or may acquire the rest. C. At a time not later than 30 days after the termination date specified in the notice of termination, the Contractor may submit to the City a list, certified as to quantity and quality, of any or all items of termination inventory not previously disposed of, exclusive of items the disposition of which has been directed or authorized by City. CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1— AD1 007200-1 GENERAL OONDITIONS Page 61 of 63 D. Not later than 15 days thereafter, the City shall accept title to such items provided, that the list submitted shall be subject to verification by the City upon removal of the items or, if the items are stored, within 45 days from the date of submission of the list, and any necessary adjustments to correct the list as submitted, shall be made prior to final settlement. E. Not later than 60 days after the notice of termination, the Contractor shall submit his termination claim to the City in the form and with the certification prescribed by the City. Unless an extension is made in writing within such 60 day period by the Contractor, and granted by the City, any and all such claims shall be conclusively deemed waived. F. In such case, Contractor shall be paid for (without duplication of any items): 1. completed and acceptable Work executed in accordance with the Contract Documents prior to the effective date of termination, including fair and reasonable sums for overhead and profit on such Work; 2. expenses sustained prior to the effective date of termination in performing services and furnishing labor, materials, or equipment as required by the Contract Documents in connection with uncompleted Work, plus fair and reasonable sums for overhead and profit on such expenses; and 3. reasonable expenses directly attributable to termination. G. In the event of the failure of the Contractor and City to agree upon the whole amount to be paid to the Contractor by reason of the termination of the Work, the City shall determine, on the basis of information available to it, the amount, if any, due to the Contractor by reasonof the termination and shall pay to the Contractor the amounts determined. Contractor shall not be paid on account of loss of anticipated profits or revenue or other economic loss arising out of or resulting from such termination. ARTICLE 16 — DISPUTE RESOLUTION 16.01 Methods and Procedures A. Either City or Contractor may request mediation of any Contract Claim submitted for a decision under Paragraph 10.06 before such decision becomes final and binding. The request for mediation shall be submitted to the other party to the Contract. Timely submission of the request shall stay the effect of Paragraph 10.06.E. B. City and Contractor shall participate in the mediation process in good faith. The process shall be commenced within 60 days of filing of the request. C. If the Contract Claim is not resolved by mediation, City's action under Paragraph 10.06.0 or a denial pursuant to Paragraphs 10.06.C.3 or 10.06.D shall become final and binding 30 days after termination of the mediation unless, within that time period, City or Contractor: CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1— AD1 007200-1 GENERAL CONDITIONS Page 62 of 63 elects in writing to invoke any other dispute resolution process provided for in the Supplementary Conditions; or 2. agrees with the other party to submit the Contract Claim to another dispute resolution process; or 3. gives written notice to the other party of the intent to submit the Contract Claim to a court of competent jurisdiction. ARTICLE 17 — MISCELLANEOUS 17.01 Giving Notice A. Whenever any provision of the Contract Documents requires the giving of written notice, it will be deemed to have been validly given if: delivered in person to the individual or to a member of the firm or to an officer of the corporation for whom it is intended; or 2. delivered at or sent by registered or certified mail, postage prepaid, to the last business address known to the giver of the notice. B. Business address changes must be promptly made in writing to the other party. C. Whenever the Contract Documents specifies giving notice by electronic means such electronic notice shall be deemed sufficient upon confirmation of receipt by the receiving party. 17.02 Computation of Times When any period of time is referred to in the Contract Documents by days, it will be computed to exclude the first and include the last day of such period. If the last day of any such period falls on a Saturday or Sunday or on a day made a legal holiday the next Working Day shall become the last day of the period. 17.03 Cumulative Remedies The duties and obligations imposed by these General Conditions and the rights and remedies available hereunder to the parties hereto are in addition to, and are not to be construed in any way as a limitation of, any rights and remedies available to any or all of them which are otherwise imposed or available by Laws or Regulations, by special warranty or guarantee, or by other provisions of the Contract Documents. The provisions of this Paragraph will be as effective as if repeated specifically in the Contract Documents in connection with each particular duty, obligation, right, and remedy to which they apply. CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: &23/202I ATTACHMENT 1— AD1 007200-1 GENERAL OONDITIONS Page 63 of 63 17.04 Survival of Obligations All representations, indemnifications, warranties, and guarantees made in, required by, or given in accordance with the Contract Documents, as well as all continuing obligations indicated in the Contract Documents, will survive final payment, completion, and acceptance of the Work or termination or completion of the Contract or termination of the services of Contractor. 17.05 Headings Article and paragraph headings are inserted for convenience only and do not constitute parts of these General Conditions. CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1— AD1 00 73 00 SUPPLEMENTARY CONDITIONS TO GENERAL CONDITIONS Page 1 of 10 61wo" 1610111110111111 SUPPLEMENTARY CONDITIONS TO GENERAL CONDITIONS SUPPLEMENTARY CONDITIONS These Supplementary Conditions modify and supplement Section 00 72 00 — General Conditions, and other provisions of the Contract Documents as indicated below. All provisions of the General Conditions that are modified or supplemented remain in full force and effect as so modified or supplemented. All provisions of the General Conditions which are not so modified or supplemented remain in full force and effect. DEFINED TERMS The terms used in these Supplementary Conditions which are defined in the General Conditions have the meaning assigned to them in the General Conditions, unless specifically noted herein. MODIFICATIONS AND SUPPLEMENTS The following are instructions that modify or supplement specific paragraphs in the General Conditions and other Contract Documents. SC-1.01 "DEFINED TERMS" A. Delete 1.01 A.6. and replace with: "6. Bid; Proposal —An offer submitted to the Owner for the Project setting forth the Contract Price and Contract Times for the Work to be performed." Delete 1.0IA. 7. and replace with: "T Bidder; Offeror — The individual or entity who submits a bid or proposal." Delete 1.01 A.8 and replace with: "8. Bidding Documents; Proposal Documents - The Bidding Requirements or Proposal Requirements, the proposed Contract Documents, and Addenda." B. Delete 1.01 A.9. and replace with: "9. Bidding Requirements; Proposal Requirements — The Invitation to Bidders or Notice to Offerors, Instructions to Bidders or Offerors, Bid Security or Proposal Security, Bid Form or Proposal Form and attachments, and required certifications and affidavits." C. Delete 1.01 A.21. and replace with: "21. Contract Time —The number of days or the dates stated and agreed to in the Proposal and executed in the Agreement to: (i) achieve the milestones as stated therein and (ii) complete the Work so that it is ready for Final Acceptance. The Contract Time will run continuously except as otherwise noted in this Section." CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 2 — AD1 00 73 00 SUPPLEMENTARY CONDITIONS TO GENERAL CONDITIONS Page 2 of 10 D. Delete 1.01 A.33. and replace with: "33. Engineer — The licensed professional engineer or engineering firm registered in the State of Texas performing professional services for the City, for the purposes of this Agreement the Engineer is Arcadis U.S., Inc." Delete 1.01 A. 46. and replace with: "46. Notice to Proceed — A written notice given by the City to the Contractor fixing the date on which the Contract Time will commence to run and on which the Contractor shall start to perform all of the Work or such portion of the Work as explicitly authorized by the Notice to Proceed. Where all portions of the Work are not authorized by the initial Notice to Proceed, one or more additional Notice to Proceed documents will be provided by the City to give written notice to the Contractor to start to perform additional portions of the Work until all of the Work is authorized. The Contract Time will run continuously except as otherwise noted in this Section." Delete 1.01 A. 55 and replace with: "55. Regular Working Hours — Hours beginning at 7:00 a.m. and ending at 4:30 p.m., Monday thru Friday (excluding legal holidays) for all Work at Water Treatment Plant Sites." E. Delete 1.01 A. 70. and replace with: "70. Weekend Working Hours — Hours beginning at 9:00 a.m. and ending at 4:30 p.m., Saturday, Sunday, or legal holiday. as approved in advance by the City. Legal holidays annually observed by the City include Labor Day, Veterans Day, Thanksgiving (2 days), Christmas (2 days), New Year's Day, Martin Luther King Day, President's Day, Memorial Day and Independence Day (a total of 11 days)." F. Add the following additional definitions immediately following GC 1.01 A.72.: "73. Bid Security; Proposal Security —The financial security provided by Bidder or Offeror at the time the Bid or Proposal is submitted and held by Owner until the Agreement is executed and the evidence of insurance and bonds required by the Contract Documents are provided. 74. Design Engineer - The licensed professional engineer or engineering firm registered in the State of Texas performing professional services for the Contractor, to perform delegated design duties required by the Contract Documents. The name of the firm shall be added to the Contract Document Section 01 33 00 Table 01 33-A and shall perform all duties assigned by the document as the Engineer -of -Record for improvements for which the firm provides sealed submittal documents. 75. Special Warranty — An extended warranty period applicable to all or any part of the Work as required by the Contract Documents. The period is a Special Guarantee for the purpose of establishing an extended Correction Period for the specified portions of the Work as noted in Article 13.07 of the General Conditions." CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 2 — AD1 00 73 00 SUPPLEMENTARY CONDITIONS TO GENERAL CONDITIONS Page 3 of 10 SC-2.02 "COMMENCEMENT OF CONTRACT TIME: NOTICE TO PROCEED" Delete the text presented in Article 2.02 and replace with: "A. The Contract Time will commence to run on the day indicated in the initial Notice to Proceed. B. Each Notice to Proceed will include a description of the Work or portions of the Work upon which the Contractor is authorized by the City to start work. C. The Contract Time will run continuously except as described in Article 14.05 Final Inspection of all Work. Partial Utilization of portions of the Work by the City shall not affect Contract Time as noted in Article 14.04 A. 3 of this Section. D. Notice to Proceed with any portion of the Work will not be provided by the City prior to receipt of executed bonds noted in Article 5.02 of this Section covering all portions of the Work noted in the Notice to Proceed." SC-2.03"STARTING THE WORK" Delete the text presented in Article 2.03 and replace with: "A. Contractor shall start to perform the authorized portions of the Work on the date when the Contract Time commences to run. No portion of the Work shall be done by the Contractor prior to the date on which the Contract Time commences to run. B. Where the Contractor elects to utilize phased bonding in accordance with Article 5.02 A., the initial Notice to Proceed shall authorize the start of Work on only a portion of the Work. The Contractor shall provide executed bonds covering additional portions of the Work not previously authorized by a Notice to Proceed no later than 14 days in advance of the planned start of work on the added portions of the Work. In no case shall the Contractor begin such work prior to receipt of a Notice to Proceed specifically authorizing the added work. C. When notified that the Contractor is ready to begin portions of the Work not previously authorized by a Notice to Proceed, and upon receipt of executed Performance and Payment Bonds covering the added portions of the Work, the City shall issue a Notice to Proceed with such additional portions of the Work. D. The City will not issue a Notice to Proceed for any portion of the Work prior to receipt of executed Performance and Payment Bonds, that when combined with previously executed bonds, are of sufficient face value to cover all portions of the Work the Contractor wishes to proceed with. E. The Contractor shall not begin work on any other portions of the Work not authorized explicitly in a Notice to Proceed signed by the City." CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 2 — AD1 00 73 00 SUPPLEMENTARY CONDITIONS TO GENERAL CONDITIONS Page 4 of 10 SC-4.01 "AVAILABILITY OF LANDS" A. Add the following the end of GC 4.01 A. 1.: "Easement limits shown on the Drawing are approximate and were provided to establish a basis for bidding. Upon receiving the final easements descriptions, Contractor shall compare them to the lines shown on the Contract Drawings. B. Add GC 4.01 A. 3 immediately following GC 4.01 A.2.: "3. The following is a list of known outstanding right-of-way, and/or easements to be acquired, if any as of [Month Day, Year this document was prepared]: PARCEL NUMBER NONE OWNER TARGET DATE OF POSSESSION The Contractor understands and agrees that the dates listed above are estimates only, are not guaranteed, and do not bind the City. If Contractor considers the final easements provided to differ materially from the representations on the Contract Drawings, Contractor shall within five (5) Business Days and before proceeding with the Work, notify City in writing associated with the differing easement line locations." SC-4.01A.2, "AVAILABILITY OF LANDS" Utilities or obstructions to be removed, adjusted, and/or relocated. The following is list of utilities and/or obstructions that have not been removed, adjusted, and/or relocated as of the date of document preparation: EXPECTED UTILITY AND LOCATION TARGET DATE OF OWNER ADJUSTMENT I0 The Contractor understands and agrees that the dates listed above are estimates only, are not guaranteed, and do not bind the City. SC-4.02A., "SUBSURFACE AND PHYSICAL CONDITIONS" None CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 2 — AD1 00 73 00 SUPPLEMENTARY CONDITIONS TO GENERAL CONDITIONS Page 5 of 10 SC-4.06A., "HAZARDOUS ENVIRONMENTAL CONDITIONS AT SITE" A. Add GC 4.06A.2. immediately following GC 4.06A.1. "2. The following are reports and drawings of existing hazardous environmental conditions known to the City: None" SC-5.02 A., "PERFORMANCE, PAYMENT, AND MAINTENANCE BONDS" A. Add GC 5.02 A. 1. through 7. immediately following GC 5.02 A. "l . Performance and Payment Bonds accompanying the executed Agreement shall be in the full amount of the Contract Price unless the Contractor intends to provide phased bonding of the Work in accordance with Articles 5.02 A. 2. — 7. below. 2. When phased implementation of bonding is desired, accompanying the executed Agreement, the Contractor shall at minimum provide Performance and Payment Bonds in an amount equal to the total of: Proposal Item No. 1 (Mobilization), No. 2 (Familiarization and Preliminary Assessment) and No. 3 (Design) and all allowances in Proposal Item No. 10, No. 11, No. 12 and No. 13. 3. The Contractor shall provide additional Performance and Payment Bonds covering portions of the work in Proposal Item No. 4 (Eagle Mountain WTP Configuration, Cutover and Startup), No. 5 (South Holly WTP Configuration, Cutover and Startup), No. 6 (North Holly WTP Configuration, Cutover and Startup), No. 7 (Westside WTP Configuration, Cutover and Startup), No. 8 (Rolling Hills WTP Configuration, Cutover and Startup) and No. 9 (Centralized SCADA Configuration, Cutover and Startup) prior to beginning work associated with each Proposal Item. 4. Except for the bonds accompanying the executed Agreement, prior to the initial Notice to Proceed, the Contractor shall provide bonding in the amount of a single Proposal Item, or the total amount of a group of two or more Proposal Items for each phase. 5. Performance and Payment bonds covering only a portion of the work shall be accompanied by a cover letter that clearly states the Proposal Item Number and Description of the include the portion of the Work covered by the accompanying bonds. 6. The Contractor shall incorporate execution and delivery of the additional bonds as a scheduled construction task no later than 14 days in advance of the start of portions of the Work associated with a Proposal Item not covered by a prior bonding submittal. 7. The Contractor shall not commence any portion of the Work until a Notice to Proceed is provided by the City covering that portion of the Work." SC-5.03, "CERTIFICATES OF INSURANCE" In accordance with GC 5.03, the following entities are named as "Additional Insured" and shall be named on all liability policies, including their respective officers, directors, agents and employees: (1) City (2) Engineer: Arcadis U.S., Inc. (3) Other: None" CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 2 — AD1 00 73 00 SUPPLEMENTARY CONDITIONS TO GENERAL CONDITIONS Page 6 of 10 SC-5.04, "CONTRACTOR'S INSURANCE" The limits of liability for the insurance required by Paragraph GC-5.04 shall provide the following coverages for not less than the following amounts or greater where required by laws and regulations: A. 5.04A., Workers' Compensation, under Paragraph GC-5.04A., add the following: "3. Provide the following, Statutory limits Employer's liability $500,000 each accident/occurrence $500,000 Disease — each employee $500,000 Disease — policy limit" B. 5.04B., Commercial General Liability, under Paragraph GC-5.04B. Contractor's Liability Insurance under Paragraph GC-5.04B., add the following: "1. Coverage shall be on a per project basis covering the Contractor with minimum limits of: $1,000,000 each occurrence $2,000,000 aggregate limit 2. The policy must have an endorsement (Amendment — Aggregate Limits of Insurance) making the General Aggregate Limits apply separately to each job site. 3. The Commercial General Liability Insurance policies shall provide "X", "C", and "U" coverages. Verification of such coverage must be shown in the Remarks Article of the Certificate of Insurance." C. 5.04 C. Automobile Liability, under Paragraph GC-5.04 C. Contractor's Liability Insurance under Paragraph GC-5.04C., which shall be in an amount not less than the following amounts, add C. 1.: "1. Automobile Liability - a commercial business policy shall provide coverage on "Any Auto", defined as autos owned, hired and non -owned. $1,000,000 each accident on a combined single limit basis. Split limits are acceptable if limits are at least: $250,000 Bodily Injury per person / $500,000 Bodily Injury per accident / $100,000 Property Damage" CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 2 — AD1 00 73 00 SUPPLEMENTARY CONDITIONS TO GENERAL CONDITIONS Page 7 of 10 D. Add 5.04 F. following to 5.04 E.: "F. Contractor's Professional Liability Insurance: Purchase and maintain applicable professional liability insurance if Contractor will provide or furnish professional services under this Contract, through a delegation of professional design services or otherwise. This insurance must cover negligent acts, errors, or omissions in the performance of professional design or related services by the insured or others for whom the insured is legally liable. The insurance must be maintained throughout the duration of the Contract and for a minimum of 2 years after Final Acceptance. The policy must pre -date the commencement of furnishing services on the Project. 2. Provide the following coverage with not less than the minimum limits indicated: Policy Limit Each Claim $1,000,000 Annual Aggregate $1,000,000 " SC-6.04., "PROJECT SCHEDULE" Project schedule shall be Tier 3 for the project. SC-6.06., "CONCERNING SUBCONTRACTORS, SUPPLIERS, OTHERS" Replace "35%" with "40%" in GC 6.06-A. SC-6.07., "WAGE RATES" The following is the prevailing wage rate table(s) applicable to this project and is provided in the Appendixes: Appendix GC 6.07 — 2020 Prevailing Wage Rates for Vertical Construction SC-6.09., "PERMITS AND UTILITIES" SC-6.09A., "CONTRACTOR OBTAINED PERMITS AND LICENSES" The following are known permits and/or licenses required by the Contract to be acquired by the Contractor: None SC-6.09B. "CITY OBTAINED PERMITS AND LICENSES" The following are known permits and/or licenses required by the Contract to be acquired by the City: None CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 2 — AD1 00 73 00 SUPPLEMENTARY CONDITIONS TO GENERAL CONDITIONS Page 8 of 10 SC-6.09C. "OUTSTANDING PERMITS AND LICENSES" The following is a list of known outstanding permits and/or licenses to be acquired, if any as of None SC-6.18C, 3, "SUBMITTALS — CITY' REVIEW" Delete Article 6.18C. 3. And replace with the following: "3. City's review and acceptance shall not relieve Contractor from responsibility for any variation from the requirements of the Contract Documents unless Contractor has complied with the requirements of Section 0133 00 and City has given written acceptance. The Contractor must include a complete list of each such variation by specific written notation thereof incorporated in or accompanying the Submittal on the cover sheet and clearly note the variation on each page of the submittal affected by the variation. The terms "written acceptance" by the City for the purposes of this Article shall be defined and limited to either: 1) The statement "Variations proposed within this submittal are approved" made within the notations and comments returned to the Contractor or 2) Issuance of Field Order or Change Order. Regardless of the form or written acceptance, the City may restrict such written acceptance by indicating which variations within the Contractor's proposed list the City finds acceptable and which are being rejected. The City's review and acceptance shall not relieve Contractor from responsibility for complying with the requirements of the Contract Documents not modified by such written acceptance." SC-6.24B., Compliance with "TITLE VI, CIVIL RIGHTS ACT OF 1964 AS AMENDED" Below Article 6.24. B. of the General Conditions add Article C. below: "C. For any project receiving Federal assistance, 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, in accordance with Article 6.24. B of the General Conditions: 1. Compliance with Regulations: The Contractor shall comply with the Regulation relative to nondiscrimination in Federally -assisted programs of the Department of Transportation (hereinafter, "DOT") Title 49, Code of Federal Regulations, Part 21, as they may be amended from time to time, (hereinafter referred to as the Regulations), which are herein incorporated by reference and made a part of this contract. 2. Nondiscrimination: The Contractor, with regard to the work performed by it during the contract, shall not discriminate on the grounds of race, color, or national origin, in the selection and retention of subcontractors, including procurements of materials and leases of equipment. The Contractor shall not participate either directly or indirectly in the discrimination prohibited by 49 CFR, section 21.5 of the Regulations, including employment practices when the contract covers a program set forth in Appendix B of the Regulations. Solicitations for Subcontractors, Including Procurements of Materials and Equipment: In all solicitations either by competitive bidding or negotiation made by the contractor for work to be performed under a subcontract, including procurements of CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 2 — AD1 00 73 00 SUPPLEMENTARY CONDITIONS TO GENERAL CONDITIONS Page 9 of 10 materials or leases of equipment, each potential Subcontractor or supplier shall be notified by the Contractor of the Contractor's obligations under this contract and the Regulations relative to nondiscrimination on the grounds of race, color, or national origin. 4. Information and Reports: The Contractor shall provide all information and reports required by the Regulations or directives issued pursuant thereto, and shall permit access to its books, records, accounts, other sources of information and its facilities as may be determined by City or the Texas Department of Transportation to be pertinent to ascertain compliance with such Regulations, orders and instructions. Where any information required of a contractor is in the exclusive possession of another who fails or refuses to furnish this information the contractor shall so certify to the City, or the Texas Department of Transportation, as appropriate, and shall set forth what efforts it has made to obtain the information. 5. Sanctions for Noncompliance: In the event of the Contractor's noncompliance with the nondiscrimination provisions of this Contract, City shall impose such contract sanctions as it or the Texas Department of Transportation may determine to be appropriate, including, but not limited to: a. withholding of payments to the Contractor under the Contract until the Contractor complies, and/or b. cancellation, termination or suspension of the Contract, in whole or in part. Incorporation of Provisions: The Contractor shall include the provisions of paragraphs (1) through (6) in every subcontract, including procurements of materials and leases of equipment, unless exempt by the Regulations, or directives issued pursuant thereto. The Contractor shall take such action with respect to any subcontract or procurement as City or the Texas Department of Transportation may direct as a means of enforcing such provisions including sanctions for non-compliance: Provided, however, that, in the event a contractor becomes involved in, or is threatened with, litigation with a subcontractor or supplier as a result of such direction, the contractor may request City to enter into such litigation to protect the interests of City, and, in addition, the contractor may request the United States to enter into such litigation to protect the interests of the United States. Additional requirements associated with the City's equity goals can be found in Section 00 45 42 — Business Equity Specifications." SC-9.01., "CITY'S PROJECT MANAGER" The City's Project Manager for this Contract is Alexander Pierce, or his/her successor pursuant to written notification from the Director of the Water Department. CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 2 — AD1 00 73 00 SUPPLEMENTARY CONDITIONS TO GENERAL CONDITIONS Page 10 of 10 SC-13.07., "Correction Period" Add the words "Except as noted in Article 13.07 F. below," to the beginning of Article 13.07 A. Add Article 13.07 F: F. The Correction Period shall begin based on completion of portions of the Work as noted in the Contract Documents. The Correction Period for Work used or occupied in accordance with Partial Utilization as noted in Article 14.04 of the General Conditions shall begin prior to Final Acceptance of all Work when: 1. That portion of the work is a facility specifically identified in Section 07 78 36 — Warranties. 2. All items noted as requiring correction following the City's inspection of that portion of the work have been corrected." SC-14.01., "SCHEDULE OF VALUES" Add the following sentence to the end of Article 14.01: "Submit preliminary Schedule of Values within ten days following the date that the Contract Times commence running in accordance with Article 2.02 of the General Conditions." SC-16.01C.1, "METHODS AND PROCEDURES" None ++END OF SECTION++ CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 2 — AD1 ADDENDUM NO. 2 Pagel of 4 CITY OF FORT WORTH, TEXAS PREQUALIFICATION FOR THE CONSTRUCTION OF SCADA SYSTEM REPLACEMENT ADDENDUM NO. 2 This Addendum is part of the Contract Documents and modifies the Contractor for The Construction of SCADA System Replacement Document dated March 2024 for the above referenced project. This change affects the Prequalification Document distributed on March 21, 2024 to prequalify Interested Parties. Acknowledge receipt of this Addendum in accordance with the requirements in Section 00 21 13 Prequalification Instructions. Failure to do so may result in the Interested Party not being prequalified. Overview and General Clarifications: 1. This addendum provides questions the City have received to date and a clarification on the Schedule for Procurement noting primary and backup dates for the planned 2 day Site Visit. ADDENDUM ITEMS (SPECIFICATION MODIFICATIONS & PROJECT CLARIFICATIONS): 1. The City has received the following questions: QUESTION 1: Is hardware part of this scope at all, any type of PLC hardware? ANSWER 1: No hardware procurement is included in this contract. QUESTION 2: Is there an Engineer's estimate of the cost of the Work? ANSWER 2: Offerors should make their own estimates of the cost and incorporate that into their proposal. No estimate or project budgetary cost will be provided by the City. QUESTION 3: Does the City intend to maintain the 900 MHz radio frequency communication, will there be any changes to that? ANSWER 3: The existing radio communication system will be used, no changes are part of the Work. ADDENDUM NO. 2 Page 2 of 4 QUESTION 4: What are the Cybersecurity requirements for the project? ANSWER 4: Cyber security considerations are part of the delegated SCADA System architecture design. Best practices will be required. The City's Water IT staff will install and configure needed hardware, the Contractor's role will be limited to coordination. QUESTION 5: What is the City's Business Equity Goal for this project? ANSWER 5: The Business Equity Goal for this project is 5% as noted in Section 00 11 15 Notice to Offerors. QUESTION 6: Would it be possible to get a list of the intended bidders with contact information? ANSWER 6: Im 2. Section 00 11 15 Notice to Offerors, delete the included Schedule for Procurement and replace it with the following schedule: "SCHEDULE FOR PROCUREMENT 1 st Advertisement for CSP — Prequalification Requirements 2nd Advertisement for CSP — Prequalification Requirements Virtual Prequalification Q&A Meeting Deadline for Prequalification Questions Deadline to Request Prequalification Offerors Notification of Prequalification Contract Document Release Date (anticipated) Pre -proposal 2 Day Site Visit (Primary) Pre -proposal Conference — In Person and Virtual (anticipated) Pre -proposal 2 Day Site Visit (Backup)* Deadline for Questions (anticipated) Deadline for Responses via Addenda (anticipated) Proposal Due Date (anticipated) Evaluation of Proposals (anticipated) Oral Clarifications (anticipated, if required) Notice to Proceed (anticipated) March 21, 2024 March 28, 2024 April 1, 2024, 2:00 PM CT April 5, 2024 April 12, 2024, 4: 00 PM (Local Time) April 19, 2024 April 19, 2024 May 1 — May 2, 2024 May 8, 2024, 9:00 AM CT May 8 — May 9, 2024 May 15, 2024, 5:00 PM CT May 22, 2024, 5: 00 PM CT May 30, 2024 by 1:30 PM CT May 31, 2024 through June 12, 2024 June 6, 2024 through June 11, 2024 August 7, 2024 ADDENDUM NO. 2 Page 3 of 4 SCHEDULE FOR PROCUREMENT (CONTINUED) Notes: * Should adverse weather or unforeseen events at the Water Treatment Plants require rescheduling of the Pre -proposal 2 Day Site Visit from the Primary dates above, it is the City's intent to conduct the site visit in conjunction with the Pre -Proposal Conference the following week on the dates indicated." 3. Section 00 11 15 Notice to Offerors, delete the included "PRE -PROPOSAL SITE VISIT" section and replace it with the following: "PRE -PROPOSAL SITE VISIT A pre -proposal site visit will be held as described in Section 00 21 15 — Instructions to Offerors on the following anticipated date and time. DATE: May 1 - May 2, 2024 TIME: 9:00 AM CT Each prequalified Offeror shall select up to two (2) attendees to attend the site visit. Each Offeror shall send the names of the attendees to the City's Project Manager via email, a minimum of 48- hours in advance of the site visit. Should adverse weather or unforeseen events at the Water Treatment Plants require rescheduling of the site visit, it is the City's intent to conduct the in conjunction with the Pre -Proposal Conference the following week as noted in the Schedule for Procurement." 4. Section 00 1115 Notice to Offerors, delete the included ""PRE -PROPOSAL CONFERENCE" section and replace it with the following: "PRE -PROPOSAL CONFERENCE — In -person and Virtual Conference An in -person pre -proposal conference will be held as described in Section 00 21 15 — Instructions to Offerors on the following anticipated date and time, as well as simultaneously via a web conferencing application. DATE: May 8, 2024 TIME: 9:00 AM CT An invitation with a link to the web conferencing application will be distributed to Prequalified Offerors. The presentation along with any questions and answers provided at the Pre -proposal Conference will be issued as an Addendum. Prequalified Offerors may also ask questions or comments in accordance with Section — 00 21 15 Instructions to Offerors Article 1.9. Any questions received will be answered by Addenda. Addenda will be issued pursuant to Section 00 21 15 — Instructions to Offerors, Article 1.9." 5. Section 00 21 13 Prequalification Instructions, delete paragraph 1.2 B. and re -number Articles 1.2 C. and 1.2 D. to 1.2 B. and 1.2 C. respectively. ADDENDUM NO. 2 Page 4 of 4 6. Section 00 2115 Instructions to Offerors, delete Sub -article 1.7 A. 2. In its entirety and replace it with the following: "2. Shall attend the Pre -Proposal Site Visit. Due to security concerns, and the number and locations of sites accessed, and the sequence, will be limited and selected by the City in advance. The intent is to visit all WTPs to the extent possible and to limit the site visits to two calendar days. However, the City reserves the right to alter this prior to or during the site visit. Each prequalifed Offeror shall select up to two (2) attendees to attend the site visit. Each Offeror shall send the names of the attendees to the City's Project Manager via email, a minimum of 48-hours in advance of the site visit." OF�T�'{yS�LS�'y� .......................... :ROSSER. R. STANDIFER� 92755 . •���I DNA..... Rosser R. Standifer, PE Principal Engineer Arcadis Addendum No. 2 Issued by the City of Fort Worth Date: April 18, 2024 Alexander Pierce Project Manager City of Fort Worth END OF ADDENDUM No. 2 ADDENDUM NO. 3 Page 1 of 2 CITY OF FORT WORTH, TEXAS PREQUALIFICATION FOR THE CONSTRUCTION OF SCADA SYSTEM REPLACEMENT ADDENDUM NO. 3 This Addendum is part of the Contract Documents and modifies the Contractor for The Construction of SCADA System Replacement Document dated March 2024 for the above referenced project. This change affects the Document distributed on March 21, 2024 to prequalified Offerors. Acknowledge receipt of this Addendum in accordance with the requirements in Section 00 21 15 Instructions to Offerors Article 1.16 I. Failure to do so may result in the Proposal being deemed non- responsive. Overview and General Clarifications: This addendum incorporates changes in the Contract Document in Section 00 11 15 Notice to Offerors and Section 00 21 15 Instructions to Offerors that were previously updated in Addendum No. 2. The additional changes, while included in Addendum No. 2, were not reflected in the conformed document issued. ADDENDUM ITEMS (SPECIFICATION MODIFICATIONS & PROJECT CLARIFICATIONS): Section 00 1115 Notice to Offerors, delete this section in its entirety and replace it with ATTACHMENT 1 — AD3. The additional conformed changes are noted with change bars in the left margin. 2. Section 00 2115 Instructions to Offerors, delete this section in its entirety and replace it with ATTACHMENT 2 — AD3. The additional conformed changes are noted with change bars in the left margin. .• . ROSSER R. STANDfFER ..:................... :...� 92755 UZ Rosser R. Standifer, PE Principal Engineer Arcadis Addendum No. 3 Issued by the City of Fort Worth Date: April 30, 2024 Alexander Pierce Project Manager City of Fort Worth END OF ADDENDUM No. 3 ADDENDUM NO. 3 Page 2 of 2 0011 15 NOTICE TO OFFERORS Page 1 of 6 SECTION 00 11 15 NOTICE TO OFFERORS PREQUALIFICATION FOR SUBMITTAL OF COMPETITIVE SEALED PROPOSALS PREOUALIFICATION Offerors intending to submit proposals must be Prequalified as an Offeror for this specific project by the City prior to receipt of the Contract Documents. Request for Prequalification for the SCADA System Replacement ("Project") will be received by the City of Fort Worth via the Procurement Portal at: https:Hfortworthtexas.bonfirehub.com/portal/?tab=oi)en0pportunities, under the respective Project opportunity page until 4:00 P.M. CST, Friday, April 12, 2024. DOCUMENT EXAMINATION AND PROCUREMENTS Prior to prequalification, the document sections noted in Section 00 21 13 — Prequalification Instructions will be available to all interested parties. The procedures and requirements for Prequalification are outlined in Section 00 21 13 — Prequalification Instructions. Additional information applicable to the subsequent submittal of Competitive Sealed Proposals (CSP) is included in Section 00 21 15 — Instructions to Offerors. The limited Contract Document content noted will be available electronically to interested parties via the Procurement Portal: htt_Ds://fortworthtexas.bonfirehub.com/_aortal/?tab=o_nenOD_Dortunities, under the respective Project. The full content of the Contract Documents will be available to all Prequalified Offerors following confirmation that the Offeror is prequalified and receipt of an executed (signed) copy of Section — 00 23 13 Non -Disclosure Agreement. The Contract Documents may be shared with and viewed by sub -contractors teamed with Prequalified Offerors and with suppliers as necessary to develop a Proposal subject to the provisions of the Non -Disclosure Agreement. The Contract Documents and all Addenda will be available electronically to Prequalified Offerors via the Procurement Portal: httl)s://fortworthtexas.bonfrehub.com/portal/?tab=ol)en0phortunities, under the respective Project. RECEIPT OF PROPOSALS Competitive Sealed Proposals (CSP) for the delegated design and construction of SCADA System Replacement ("Project") for the Water Department will be received by the City of Fort Worth. Proposals will be received from prequalified Offerors only via the Procurement Portal: https://fortworthtexas.bonfirehub.com/portal/?tab=olDen0pportunities. under the respective Project opportunity page until 1:30 PM CST, Thursday, May 30, 2024, as further described below. The CSP will be opened publicly and read aloud at 2:00 PM CST in the City Council Chambers. Your submissions must be uploaded, finalized, and submitted prior to the Project's posted due date. The City strongly recommends allowing sufficient time to complete this process (ideally a week CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 1— AD3 0011 15 NOTICE TO OFFERORS Page 2 of 6 prior to the deadline) to begin the uploading process and to finalize your submission. Uploading large documents may take time, depending on the size of the file(s) and your Internet connection speed. The Bonfire portal can be accessed using Microsoft Edge, Google Chrome, or Mozilla Firefox. Javascript must be enabled. Browser cookies must be enabled. Electronic submission is subject to electronic interface latency, which can result in transmission delays. All proposers assume the risk of late transmission/ submission. The City shall not be held liable if an interested party is unable to submit a complete response before the published deadline due to transmission delays or any other technical issues or obstructions. The City strongly recommends allowing sufficient time to complete the submission process (ideally a week before the deadline) to begin the uploading process and to finalize your submission to give adequate time in the event an issue arises. All submissions must be submitted electronically prior to the close date and time under the respective Project/Solicitation via the Procurement Portal: htti)s: //fortworthtexas.bonfirehub. com/portal/?tab=oi)en0pportunities Failure to submit all completed required information listed in the respective Solicitation will be grounds for rejection of a prequalification request or subsequent submitted proposal as non- responsive. No late proposals shall be accepted. Proposals delivered in any other manner than using the Bonfire Platform (Procurement Portal) will not be accepted or considered. If, upon being opened, a submission is unreadable to the degree that material conformance to the requirements of the procurement specifications cannot be ascertained, such submission will be rejected without liability to the City, unless the Offeror provides clear and convincing evidence (a) of the content of the submission as originally submitted and (b) that the unreadable condition of the Electronic Proposal was caused solely by error or malfunction of the Bonfire Platform (Procurement Portal). Failure to scan a clear or readable copy of a response into the system does not constitute and shall not be considered an error or malfunction of the Bonfire Platform (Procurement Portal). Offerors are encouraged to fully review each page of every document within their submission prior to submitting to ensure all documents are clear, legible, and complete. SUPPORT For technical questions, visit Bonfire's help forum at: htti)s://vendorsu-pi)ort.2obonfire.com/hc/en-us Contact the Bonfire support team at Support@GoBonfire.com or by calling 1-800-354-8010. To get started with Bonfire, watch this five-minute training video: Vendor Registration and Submission Video - Bonfire Vendor Support (2obonfire.com) EXISTING SYSTEM The existing Water Department Supervisory Control and Data Acquisition (SCADA) system is a proprietary HSQ Technologies system originally installed in 1987, upgraded in 1991, and since then has been developed and updated as the system has expanded. The SCADA system uses licensed 900 MHz radio frequencies to communicate with the remote distribution facilities. At the City's potable water treatment facilities - North Holly, South Holly, Rolling Hills, Westside, and Eagle Mountain Water Treatment Plants (WTPs) - three different Human Machine Interface (HMI) platforms are utilized. These include HSQ-Miser, GE Cimplicity, and Allen-Bradley FactoryTalk View SE, all of which report to a top -end and head -end HMI (HSQ-Miser). CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 1— AD3 0011 15 NOTICE TO OFFERORS Page 3 of 6 GENERAL DESCRIPTION OF WORK The project includes the design, configuration, testing, start-up, and maintenance through Final Acceptance of a complete SCADA replacement for the City's Water Department SCADA system, inclusive of but not limited to: upgraded SCADA systems at each of the five WTPs; a new centralized SCADA system; an upgraded SCADA system architecture to support the SCADA replacement; a new data architecture to support a comprehensive historical data collection and reporting interface and other work elements to support the SCADA upgrades. The City has procured a SCADA software, Ignition by Inductive Automation, which is to be used for the new HMI. This software will be provided by the City for use by the Contractor in implementation, installation, configuration, testing and start-up of the replacement system. The Contractor shall provide the following project services. Pre -Construction Services including Familiarization and Preliminary Assessment and Design Services for SCADA system architecture and component selection requirements. Construction Services to include Programming and Configuration; Factory Acceptance Testing; Cutover, Field Testing, and Start -Up; System Maintenance, Final Acceptance, and Warranty. EXPRESSION OF INTEREST To ensure awareness of any new information pertinent to this project, all interested parties should indicate their intent to request prequalifcation in the Procurement Portal by selecting "yes" under the "Intent to Bid" section the Procurement Portal: htti)s://fortworthtexas.bonfirehub.com/portal/?tab=oi)en0pportunities, under the respective Project. Any and all subsequent Addenda will also be available to the Prequalified Offerors via the Procurement Portal. SCHEDULE FOR PROCUREMENT 1st Advertisement for CSP — Prequalification Requirements 2" d Advertisement for CSP — Prequalification Requirements Virtual Prequalification Q&A Meeting Deadline for Prequalification Questions Deadline to Request Prequalification Offerors Notification of Prequalification Contract Document Release Date (anticipated) Pre -proposal 2 Day Site Visit (Primary) Pre -proposal Conference — In Person and Virtual (anticipated) Pre -proposal 2 Day Site Visit (Backup)* Deadline for Questions (anticipated) Deadline for Responses via Addenda (anticipated) Proposal Due Date (anticipated) Evaluation of Proposals (anticipated) Oral Clarifications (anticipated, if required) Notice to Proceed (anticipated) CITY OF FORT WORTH March 21, 2024 March 21, 2024 March 28, 2024 April 1, 2024, 2:00 PM CT April 5, 2024 April 12, 2024, 4:00 PM (Local Time) April 19, 2024 April 19, 2024 May 1 —May 2, 2024 May 8, 2024, 9:00 AM CT May 8 May 9, 2024 May 15, 2024, 5:00 PM CT May 22, 2024, 5:00 PM CT May 30, 2024 by 1:30 PM CT May 31, 2024 through June 12, 2024 June 6, 2024 through June 11, 2024 August 7, 2024 SCADA System Replacement 103086 ATTACHMENT 1— AD3 0011 15 NOTICE TO OFFERORS Page 4 of 6 Notes: * Should adverse weather or unforeseen events at the Water Treatment Plants require rescheduling of the Pre -proposal 2 Day Site Visit from the Primary dates above, it is the City's intent to conduct the in conjunction with the Pre -Proposal Conference the following week on the dates indicated. PREOUALIFICATION O&A MEETING — Virtual Conference Prequalification Question and Answer (Q&A) will be held as described in Section 00 21 15 — Instructions to Offerors on the following anticipated date and time, via a web conferencing application only. DATE: April 1, 2024 TIME: 2:00 pm CT A link to the web conference will be available on the Procurement Portal under the respective Project. PRE -PROPOSAL SITE VISIT A pre -proposal site visit will be held as described in Section 00 21 15 — Instructions to Offerors on the following anticipated date and time. DATE: May 1 - May 2, 2024 TIME: 9:00 AM CT Each prequalified Offeror shall select up to two (2) attendees to attend the site visit. Each Offeror shall send the names of the attendees to the City's Project Manager via email, a minimum of 48- hours in advance of the site visit. Should adverse weather or unforeseen events at the Water Treatment Plants require rescheduling of the site visit, it is the City's intent to conduct the in conjunction with the Pre -Proposal Conference the following week as noted in the Schedule for Procurement. PRE -PROPOSAL CONFERENCE — In -person and Virtual Conference An in -person pre -proposal conference will be held as described in Section 00 21 15 — Instructions to Offerors on the following anticipated date and time, as well as simultaneously via a web conferencing application. DATE: May 8, 2024 TIME: 9:00 AM CT An invitation with a link to the web conferencing application will be distributed to Prequalified Offerors. The presentation along with any questions and answers provided at the Pre -proposal Conference will be issued as an Addendum. Prequalified Offerors may also ask questions or comments in accordance with Section — 00 21 15 Instructions to Offerors Article 1.9. Any questions received will be answered by Addenda. Addenda will be issued pursuant to Section 00 21 15 — Instructions to Offerors. CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 1— AD3 0011 15 NOTICE TO OFFERORS Page 5 of 6 CITY'S RIGHT TO ACCEPT OR REJECT PROPOSALS City reserves the right to waive irregularities and to accept or reject any or all proposals. AWARD The City will award a contract to the Offeror presenting the best value based on the evaluation criteria noted in Section 00 21 15 — Instruction to Offerors. MBE participation will be evaluated in awarding this Contract. The Business Equity Goal is 5%. The evaluation shall be as noted in Section 00 21 15 — Instructions to Offerors. Offerors shall be prepared to submit the forms noted in Section 00 45 42 — Business Equity Goal CSP within 7 business days of the day they are notified of selection regardless of the scheduled date of notification. Failure to document proposed attainment precludes the City and Selected Offeror entering into negotiations and would thereby determine that the City is unable to reach a satisfactory Agreement with the Selected Offeror. In that event the City shall subsequently proceed by notifying the next ranked Offeror of the City's intent as noted in Section 00 21 15 — Instructions to Offerors. After evaluating the notification of the Selected Offeror that offers the best value and receipt of the required Business Equity Goal forms, the City will enter into negotiations with that Offeror. ADVERTISEMENT DATES 1 st Advertisement for Prequalification March 21, 2024 2nd Advertisement for Prequalification March 28, 2024 ++ END OF SECTION ++ CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 1— AD3 0011 15 NOTICE TO OFFERORS Page 6 of 6 ++THIS PAGE INTENTIONALLY LEFT BLANK++ CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 1- AD3 SECTION 00 21 15 INSTRUCTIONS TO OFFERORS PART 1 — GENERAL 1.1 DESCRIPTION 0021 15 INSTRUCTIONS TO OFFERORS Pagel of 22 A. This Section is included in the documents made available publicly for Prequalification to facilitate evaluation of Proposal submittal requirements by all interested parties. B. This Section contain detailed instructions that will be used by Prequalified Offeror to preparing the Proposal and assess the City's approach to evaluating all proposals received. Modifications to this Section, if necessary, will be made by addenda. 1.2 DEFINED TERMS A. Capitalized terms used in these Instructions to Offerors are defined in Section 00 72 00 — General Conditions. B. The terms Firm, Offeror and Prime Contractor as used in this Section are defined in Section — 00 21 13 Prequalification Instructions, Article I.I. Certain additional terms used in these Instructions to Offerors have the meanings indicated below which are applicable to both the singular and plural thereof. C. Non-resident Offeror: Any person, firm, partnership, company, association, or corporation acting directly through a duly authorized representative, submitting a proposal for performing the work contemplated under the Contract Documents whose principal place of business is not in the State of Texas. D. Prime Contractor: The terms "Prime Contractor" are used in this Section to refer to the entity (person, firm, partnership, company, association, or corporation) submitting a proposal as an Offeror when it is necessary to distinguish between the entity and subcontractors, consultants, or suppliers with which the Prime Contractor intends to place under contract to perform portions of the Work. E. Selected Offeror: The Offeror whom the City determined, based on the evaluation criteria provided in this Section, presented the best value to the City and was subsequently notified in writing of the City's intent to begin negotiations. F. Preconstruction: Refers to the period prior to the start of construction activities. Preconstruction duties are detailed in Section 40 61 13 — SCADA System General Provisions. Preconstruction activities include Familiarization and Preliminary Assessment and Design Services for SCADA system architecture and component selection requirements. CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 2 — AD3 0021 15 INSTRUCTIONS TO OFFERORS Page 2 of 22 G. Construction: Refers to the activities specified in Section 40 61 13 SCADA System General Provisions which include Programming and Configuration; Factory Acceptance Testing; Cutover, Field Testing, and Start -Up; System Maintenance, Final Acceptance, and Warranty. 1.3 DOCUMENT DISTRIBUTION AND HANDLING A. Distribution of the Contract Documents shall be restricted to Prequalified Offerors. B. The City makes copies of Contract Documents available only for the purpose of obtaining Proposals for the Work and do not authorize or confer a license or grant for any other use. C. Attachment 3 — Existing HMI Databases, and Attachment 5 — Existing Reports are not necessary to prepare the Proposal. This content will be available to the Successful Offeror for reference in accomplishing Work. Section 40 68 63 — SCADA System Programming and Configuration provides comprehensive information regarding the existing HMI tag counts and existing reports, enabling the Offeror to effectively prepare the Proposal. D. The City assumes no responsibility for errors or misinterpretations resulting from the Offeror's use of incomplete sets of Contract Documents. 1.4 PROPOSAL ORGANIZATION: A. To facilitate the City's review of the Proposal, offerors are requested to organize the main document as outlined below. Proposals shall include a cover page, table of contents, and section dividers. All pages must be 8.5"x11" with a minimum font size of 12. The Offeror shall divide the submitted Proposal Narrative information into the following numbered sections: 1. Offeror Overview - Provide an additional narrative overview of Organization & General Business Information. This information should summarize details provided in Section 00 46 12 — Offeror Statement of Qualifications and include: a. Provide general information on your company including the Offeror (company) name, address, website, main telephone number(s) and email address(es) for communication regarding the Proposal. b. Brief narrative introduction of the Offeror (Prime Contractor). c. Summary of the administration, d. Organization and staffing of your company. e. Include any information that makes your company unique and sets your company apart from others in your industry. f. Include indicators of organization size: 1) Number of full-time employees, 2) Average number of projects per year, 3) Number of years in business, 4) Estimated Prime Contractor annual revenue, and 5) Average prior project construction cost. CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 2 — AD3 0021 15 INSTRUCTIONS TO OFFERORS Page 3 of 22 g. Provide an updated list of all subcontractors, suppliers, and materials necessary to fulfill the Offeror's proposal. The Offeror shall include the approximate percentages of the Work planned for each subcontractor. The planned approach for meeting the M/WBE goal noted in Section 00 45 42 — Business Equity Goal CSP shall be clearly stated in the Offeror Overview. 2. Project Approach — The narrative, organizational, schedule, quality management, project controls and safety information, formatted by the Offeror with supporting photographs, figures and graphics. The Offeror shall include all items noted below. 3. Firm Experience — Information on projects, selected by the Offeror from those submitted in Section 00 46 12 — Offer Statement of Qualifications forms. This section shall be narrative in nature, formatted by the Offeror with supporting photographs, figures, certificates, and graphics for each project. The Offeror shall include all items noted below. 4. Key Personnel and Subcontractors — Information on all key personnel critical to project success. This section shall include detailed resumes and other information outlined below. 5. Schedule — Information on Offeror's proposed milestones and Project Completion. The Offeror shall include all items noted below. 6. Cost Proposal — Offeror's cost for the Proposal. This includes submission of Section 00 42 10 — Proposal and other information as outlined below. 7. Section 00 46 12 — Offeror Statement of Qualifications. Include in its entirety with the submittal. Provide a cover sheet that includes a numbered list of any changes made in any of the information since offeror's prequalification submittal. Note the page number and content of each change. Changes made but not expressly noted will count negatively during the evaluation. B. The Project Approach: 1. The Project Approach section shall include the following minimum components: 2. Narrative — The narrative should describe the Offeror's approach to the overall Project. This should at minimum include: a. Overview of the sequence of construction and corresponding timelines and milestones present in the Offeror's proposed schedule. b. Detailed description of the execution of the Familiarization, Preliminary Assessment, and Design tasks noted in Section 40 61 13 — SCADA System General Provisions. c. Detailed description of the execution of the Programming and Configuration, Factory Acceptance Testing, Cutover, Field Testing, and Start-up tasks noted in Section 40 61 13 — SCADA System General Provisions. d. Acknowledgement of the review and intended compliance with the City's PLC and HMI Configuration Standards as outlined in Attachment 1. e. The Offeror's summary of all other pertinent information considered essential to completing the project in accordance with the Contract Documents, and within the proposed Budget and Schedule. f. One or more examples, drawn from the Offeror's submitted project experience, illustrating the benefit of specific components of the described approach. g. The Offeror's ability to provide maintenance of the system from completion of each Operational Availability Demonstration through Final Acceptance of the project, as required in the project scope. CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 2 — AD3 0021 15 INSTRUCTIONS TO OFFERORS Page 4 of 22 h. The Offeror's capabilities to assist the City in long-term maintenance of the system after this project has concluded. 3. Provide a one -page organizational chart giving an overview of the Offeror's proposed team. Include all Key Personnel roles required as part of the Statement of Qualifications requirements. Offerors may include a narrative describing the approach to team organization and division of key roles. Resumes shall be provided as noted in Article 1.4 D of this Section. 4. Schedule — Provide a preliminary schedule for the Project and coordinate with the Schedule Proposal. At minimum include: a. Milestones — For each major work component detailed in the Contract Documents and other major work items in correspondence to the Contract Time specified in Article 4.1 of Section 00 42 10 — Proposal including any noted milestones. b. Parallel Activities — Include discussion on potential to use parallel activities both in initial planning to accelerate the schedule to complete the Work in advance of the Milestones and Contract Time noted and during the Project to recover from unplanned events. c. Flexibility — Incorporate the approach to flexibility in scheduling activities including but not limited to the sequence and timing of required shutdowns and cutover. 5. Quality Assurance/Quality Control (QA/QC) - Provide a description of the following: a. Quality Control Plan describing Offeror's quality management program. Explain methods used to interface with City's inspectors and practices used to ensure quality assurance/control during the Project. b. Provide specific examples of how these techniques or procedures were used from any of the projects listed in the Proposal. c. Process for risk management of design of shutdowns, panels, redundancies, HMI/PLC configurations, maintenance of risk register from design through construction. d. Describe what tools the Offeror uses for risk management and how Offeror's quality management team will measure the quality of construction performed by subcontractors and how non -conforming work will be addressed, the methodologies that will enable successful delivery of the project, including any key assumptions, exclusions, constraints, innovations, and opportunities to be realized. e. Demonstrated established, documents and proven quality control procedures and that are enforced by qualified quality control engineer identified as Key Personnel. Project Controls a. Explain the controls that will be utilized to assure timely completion of this Project, including methods for float creation and schedule recovery, if necessary. b. Describe detailed construction cost estimating methods, including historical benchmarking data, that will be used to ensure Proposal price compliance. Safety Protocols a. Discuss key components of Safety Plan. Offeror does not need to submit their Safety Plan prior to award. b. By evaluating the Offeror's safety program, Owner does not endorse or take any responsibility for the effectiveness of the program or any activities to CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 2 — AD3 0021 15 INSTRUCTIONS TO OFFERORS Page 5 of 22 be carried out as part of the program. 8. Subcontractors — List all subcontractors and note their specific roles and in completing the Work, and how each supports the project approach. C. Firm Experience: 1. Demonstrate the team submitted is qualified based on project experience selected from those previously noted in requesting prequalification purposes using the forms included in Section 00 46 12 — Statement of Qualifications. This section shall be narrative in nature using written project descriptions to fully describe the work performed. 2. Demonstrated capacity for training operations and maintenance personnel in SCADA System applications. Specific qualifications, where noted, may be met by the Prime Contractor or a subcontractor. Offerors shall identify the Key Personnel and Subcontractors to demonstrate qualifications. The Offeror shall select and include the following information on 3 to 5 similar ongoing or previous projects from the projects listed in 00 46 12 or additional projects. The projects should best represent the Offeror's ability to meet the required firm qualifications. For each project include: a. Project Name. b. Project Owner. c. Narrative description of the project noting similarity and relevance to the proposed work and lessons learned that would benefit this project. d. List the Key Personnel proposed as part of the Offeror's team who worked on the previous or current project. e. List the Subcontractors proposed as part of the Offeror's team who worked on the previous or current project. f. Provide budget information for each selected project to include: 1) Original Contract Price. 2) Final Contract Cost at Project Closeout. 3) Brief narrative description of cost changes, including those relating to owner enhancement and other conditions beyond the Offeror's control. g. Provide a summary of schedules for each selected project to at minimum include: 1) Original required completion date (end of Contract Time). 2) Actual completion date (end of Contract Time). 3) Brief narrative description of schedule, and how it was setup to achieve project milestones, and staging, as well as identifying changes relating to Owner requested enhancement and other conditions beyond the Offeror's control. h. Provide Contact Reference information for each selected project including: 1) Contact Name for a specific individual that will be available to discuss the project. 2) Listed Contact's Title. 3) Project Owner. 4) Email and Phone Number for the Listed Contact. CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 2 — AD3 0021 15 INSTRUCTIONS TO OFFERORS Page 6 of 22 3. If Offeror is proposing the use of a single subcontractor for over thirty percent (30%) of the work, the submitted projects shall include a minimum of three performed by the Offeror (Prime Contractor) and one (1) performed by that subcontractor. The subcontractor's project shall reflect work as a subcontractor or Prime Contractor and include experience relevant to the portion of the proposed work to be performed as part of the Offeror's team. 4. The required Offeror qualifications include: a. Demonstrated financially soundness based upon audit statement information. b. Ten (10) years of continuous experience in supplying, installing, programming, starting up, and supporting SCADA systems for water or wastewater treatment plants. The relevant experience shall be comparable to City's SCADA System, relative to size, software, and cost. c. Ten (10) years' experience in engineering, technical design, and quality control staff capable of designing and developing design documents, supplying, programming, configuring, implementing, and supporting SCADA System hardware and software, and complying with submittal and training requirements described in the Contract Documents. d. Experience providing pre -construction and construction phase services, including SCADA system architecture design, and control system integration services on and completion of three (3) control systems and SCADA brownfield replacement projects within the past ten (10) years at water or wastewater treatment utilities where each facility had/has greater than 1,000 hardwired I/O and at least one of these facilities had/has a minimum capacity of 5,000 hardwired I/O. Greenfield sites may be included to demonstrate experience in addition to the three (3) projects requested. e. Experience with Inductive Automation software for the SCADA platform, reporting solutions on one or more prior projects. f. Experience with Allen-Bradley PLC hardware and Schneider Electric PLC hardware on one or more prior projects. g. Experience providing pre -construction and construction phase services, including SCADA system architecture design, and control system integration services on two (2) design, construction management or design - build projects within the past ten (10) years at water or wastewater treatment facilities sized at a capacity of 10 million gallons per day (MGD) or greater. h. Local Staffing and Response: 1) Maintain a permanent, fully staffed, and equipped service facility within 300 miles of the project site with full-time employees capable of configuring, deploying, and maintaining the systems specified herein. 2) On -site response within 4 hours of notification starting at two months before scheduled start-up to two months after successful OAD completion. 3) Capable of responding to on -site problems within 12 hours of notice post- OAD. i. Certifications and Licensing (Include copies of all identified certifications and licensing in Section 00 46 12 — Offeror Statement of Qualifications): 1) PLC Platforms: a) Recognized System Integrator with Rockwell Automation, and fully trained on the Rockwell Automation Studio 5000 programming software. CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 2 — AD3 0021 15 INSTRUCTIONS TO OFFERORS Page 7 of 22 b) Recognized member of the Schneider Electric System Integrators Alliance Partner Program, and fully trained on EcoStruxure Control Expert (Unity Pro) programming software. c) Individual programmer certifications: Demonstrate individually completed coursework in Rockwell Automation and Schneider Electric Systems, coding, troubleshooting, and maintaining. 2) Inductive Automation Ignition Integrator Certification: a) Offeror certification: Premier Level. b) Individual programmer certifications: Demonstrate individually completed coursework in Inductive Automation Ignition Vision, Perspective, Reporting & SQL Scripting. j. Employs Control Systems Professional Engineer (P.E.) on a full-time basis. k. Demonstrated ability to provide an organized platform for communication, file distribution, submittal review and approval. 1. Demonstrated ability to use and provide updated construction schedules for the project. In. Possession of a thorough, working knowledge of water treatment processes and control philosophy in accordance with standard practices of the water industry. n. Possession and maintenance of a documented program of correcting deficiencies identified during Operational Availability Demonstration periods, Site Acceptance tests, and post -startup support periods. o. Demonstrated requisite resources of in-house staff, facilities, and finances to complete the project in the schedule specified. D. Key Personnel and Subcontractors 1. Key personnel positions, identified by the City as crucial to the success of the project, are listed below. 2. Formal succession planning, in the form of a backup for Key Personnel, is not required. If backup personnel are identified, and resumes are provided, indicate the backup role of the individual. Qualifications for backup personnel shall be the same as those for the primary key personnel. 3. Resumes shall be limited to two (2) pages for each staff member and incorporate the following information: a. Name. b. Employment identified as either the Prime Contractor or a subcontractor. c. Total years of experience. d. Years of experience with the employer. e. List of similar projects in candidates proposed role within the last ten years. f. Current project assignments including estimated end date(s). g. Education, training, and personal experience in delivering similar projects while serving in the capacity for which they are being proposed. 4. Provide resumes to fulfill the requirements for the following Key Personnel position roles. An individual can fill more than one role with supporting resume, except for the Project Manager, and the Quality Control Design Engineer. Other resumes may be furnished at the discretion of the Offeror. a. Project Manager. b. Quality Control Manager. c. SCADA and Control Systems Design Engineer. CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 2 — AD3 0021 15 INSTRUCTIONS TO OFFERORS Page 8 of 22 d. SCADA Architecture Engineer. e. HMI Systems Programmer. f. PLC Systems Programmer. g. Data Architect. It. Data Analyst. i. Field Testing and Start-up Specialist. j. Cybersecurity Specialist. Personnel Qualifications: a. Project Manager with 5-10 years' experience and three (3) projects in which that person served as the project manager of a water or wastewater capital improvement projects of more than $15 million or SCADA system replacement project with more than 1,000 hardwired 1/0 is preferred. The Project Manager shall be employed by the Contractor for a minimum of two (2) years. b. Quality Control Manager with 5 years' experience in designing and/or implementing SCADA systems comparable to City's SCADA System, relative to hardware, software, and cost is preferred. c. SCADA and Control Systems Design Engineer with five (5) years' experience in providing SCADA application design, development, and implementation for the water/wastewater industry is preferred. Show experience with at least three (3) projects in which that person served as SCADA System and Control Systems Design Engineer, of which two must be of a water/wastewater facility of at least 10 MGD or 1,000 hardwired I/O. Demonstrated experience shall include, but is not limited to, SCADA system design and programming, control narrative development, code/logic review, high performance graphics design, physical network design; shall be Texas Licensed Professional Engineer and shall be employed by the Contractor for a minimum of one (1) year. d. SCADA Architecture Engineer with five (5) years' experience in providing SCADA application design, development, and implementation for the water/wastewater industry is preferred. Show experience with at least three (3) projects in which that person served as SCADA Architecture Engineer, of which two must be of a facility of at least 10 MGD or 1,000 hardwired I/O. Demonstrated experience shall include, but is not limited to, networking testing, pre -design, design, and testing pertaining to Local Area Networks (LAN) and industrial networks for the water/wastewater industry; shall be Texas Licensed Professional Engineer or Certified Cisco Network Administrator (CCNA) or other comparable certification, and shall be employed by the Contractor for a minimum of one (1) year. e. HMI Systems Programmer with five (5) years' experience in providing HMI application programming and implementation is preferred. Show experience with at least three (3) projects in which that person served as HMI Systems Programmer, of which two must be of a water/wastewater facility of at least 10 MGD or 1,000 hardwired I/O. HMI Programmer shall be a demonstrated expert, possess certifications from Induction Automation and demonstrate experience and successful deployment of High - Performance graphics, alarming per ISA 18.2 guidelines, and life -cycle project deployment from HMI design to setup to startup and acceptance in the field. Show experience in HMI application programing, and implementation of visualization, dashboards, and reports within the CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 2 — AD3 0021 15 INSTRUCTIONS TO OFFERORS Page 9 of 22 SCADA environment and from various source data. Shall be employed by the Contractor for a minimum of two (2) years. f. PLC Systems Programmer with five (5) years' experience in providing PLC application programming, factory testing, startup, and implementation with Allen-Bradley and Schneider Electric PLCs in the water industry is preferred. Show experience with at least three (3) projects in which that person served as PLC Systems Programmer, of which two must be of a water/wastewater facility of at least 10 MGD or 1,000 hardwired I/O. PLC Programmer shall have experience with and certifications from the manufacturer for programming Allen-Bradley and/or Schneider Electric PLC systems, Ethernet/IP protocol, Modbus protocol, and OPC-UA, on past projects. Different programmers specialized for Rockwell Automation or Schneider Electric is acceptable. Shall be employed by the Contractor for a minimum of two (2) years. g. Data Architect with five (5) years' experience with SQL Server data warehouse development and management is preferred. Able to show experience with 1 or more projects of similar scale and scope. Experience with database performance tuning, maintenance, query optimization, security, and data modeling are required. h. Data Analyst with five (5) years' experience collecting, cleaning, analyzing data and report creation using inductive automation Ignition software is preferred. Experience with JSON, REST API endpoints, SQL, and Python are required. Shall show experience with 1 or more projects of similar scale and scope. i. Field Testing and Start-up Specialist with five (5) years' demonstrated experience in providing start-up and commissioning services for the water/wastewater industry is preferred. Show experience with at least three (3) projects in which that person served as Field Testing and Start-up Engineer, of which two must be of a water/wastewater facility of at least 10 MGD or 1,000 hardwired 1/0. Shall be employed by the Contractor for a minimum of two (2) years. j. Cybersecurity Specialist with five (5) years' experience in the evaluation and implementation of security measures to protect industrial control systems from cyber threats is preferred. The Cybersecurity Specialist shall have any of the following certifications: 1) A Certified Information System Security Professional (CISSP). 2) Global Industrial Cyber Security Professional (GICSP). 3) Certified SCADA Security Architect (CSSA). 4) Or an equivalent certification. Subcontractor Qualifications: a. The Offeror shall update the submitted list of subcontractors noting the percentage of the Work the Offeror intends to perform with his or her own organization and that to be performed by each subcontractor as noted in Section — 00 46 12 Offeror Statement of Qualifications. The City's goal for participation of subconsultants, consultants or other entities certified as Minority-, and/or Women-, owned Business Enterprises (M/WBE) for the project is noted in Section 00 11 15 —Notice to Offerors. Procedures and requirements following notification of selection as the Successful Offeror, and for subsequent execution of the Agreement, are identified in Section 00 45 42 — Business Equity Goal and this Section. CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 2 — AD3 0021 15 INSTRUCTIONS TO OFFERORS Page 10 of 22 E. Schedule 1. The purpose of this section is to provide the Offeror's schedule to complete the working including all milestones. Coordinate with the Approach section to provide a corresponding narrative that provides details and supports the time durations and milestones in the schedule. Gantt -style schedules and any information deemed by the Offeror to further demonstrate the approach and Offeror's schedule are acceptable and will be considered during evaluation and scoring. At minimum, the schedule proposal shall include: a. Milestones — As noted by the Offeror in Table 00 42 10 — A Milestones, Offeror Milestones column. b. For each schedule line item, provide Offeror's Days from NTP. F. Cost Proposal 1. The Cost Proposal shall be provided by completing the Proposal Form included in Section 00 42 10 —Proposal. 2. The Proposal shall meet all requirements of Section 00 42 10 — Proposal, including but not limited to presenting all Attachments required by Article 5 Attachments to the Offer. 1.5 EVALUATION CRITERIA A. Proposals received from Offerors who are not prequalified at the time proposals shall not be evaluated. Such Proposals if received will be rejected without review. B. The weighted criteria for evaluation and selection of the Contractor for this award will be based upon the factors listed below: CRITERIA WEIGHT 1. Project Approach 10 2. Firm Experience 10 3. Key Personnel & Subcontractors 10 4. Schedule 20 5. Cost Proposal 50 TOTAL 100 C. The City has attempted to provide a comprehensive statement of requirements within the Contract Documents for the work contemplated. Written proposals must present Offeror's qualifications and understanding of the work to be performed, and experience. Offerors are asked to address each evaluation criteria. Proposals must be as thorough and detailed as possible so that the City may properly evaluate capabilities to provide the requested services. D. Each Offeror's submitted Section 00 42 10 — Proposal content, including required Attachments noted in Article 5, will be scored with reference to the evaluation criteria noted. Each Criteria shall be assigned a score of 0 through 100, as noted in Article 1.6 of this Section. The Weight (percentages) noted above will be multiplied by each criteria score, and the results totaled to provide a weighted score. E. Criteria Description: CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 2 — AD3 0021 15 INSTRUCTIONS TO OFFERORS Page 11 of 22 1. Project Approach — The qualitative scoring of each Offeror's Project Approach will be based on the quality and completeness of the submittal. Scores will be awarded based upon the quality of the narrative including whether it incorporates all required components noted in Paragraph 1.4 B. of this Section. 2. Firm Experience — The qualitative scoring of each Offeror's experience will be based on the projects of similar scope and size submitted in Section 00 46 12 — Offeror Statement of Qualification. 3. Key Personnel & Subcontractors — The qualitative scoring of each Offeror's Key Personnel and Subcontractors submitted in Section 00 46 12 — Offeror Statement of Qualification and will be based on the specific personnel submitted and the completeness of the requested information. 4. Schedule — Offeror shall provide a project schedule that completes the Work within the Contract Time noted in Section 00 42 10 — Proposal, Article 4. Time is of the essence in completing the Work, the Offeror shall note the total number of days required in Section 00 42 10 — Proposal, Article 4.2. The Offeror shall also provide the number of days required for the Work associated with each Milestone identified in Section 00 42 10 — Proposal, Table 00 42 10-A. The quantitative scoring of each Offeror's Proposal Schedule will be evaluated relative to other proposals. Offerors that can complete the work over a shorter duration (fewer days) will receive higher scores. 5. Cost — The quantitative scoring of each Offeror's proposal will be evaluated relative to other proposals. The ranking and relative difference between proposal costs will be considered in scoring. 1.6 EVALUATION AND RANKING METHODOLOGY A. The City reserves the right to reject any or all proposals. B. In evaluating proposals, City will consider the qualifications of each Offeror, and whether or not the Proposals comply with the prescribed requirements as may be requested in the Proposal or prior to the Notice of Award. C. City will consider the qualifications and experience of Offeror, including the Prime Contractor, subcontractors, consultants, suppliers, and other persons and organizations proposed for portions of the Work as presented. The identity of Subcontractors, Suppliers, and other persons and organizations shall be submitted and required by this Section. City also may consider the operating costs, maintenance requirements, performance data, and guarantees of major items of materials and equipment proposed for incorporation in the Work when such data is required to be submitted prior to the Notice of Award. D. By submission of a Proposal, the Offeror acknowledges acceptance of the evaluation process, the evaluation criteria, and all other terms and conditions set forth in this Solicitation. Further, offerors acknowledge and agree that subjective judgements must be made by City during this process. CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 2 — AD3 0021 15 INSTRUCTIONS TO OFFERORS Page 12 of 22 E. City may conduct such investigations as City deems necessary to assist in the evaluation of any Proposal and to establish the responsibility, qualifications, and financial ability of Offerors, proposed Subcontractors, Suppliers and other persons and organizations to perform and furnish the Work in accordance with the Contract Documents to City's satisfaction within the prescribed time. F. Oral Clarifications: The City reserves the right to schedule a day and time during the Evaluation period for a meeting at the Offeror's facility. Offerors shall take note of the narrow time frame identified for Oral Clarifications in the Notice to Offerors. Oral Clarifications, if required, shall be attended by the Offeror's Key Personnel to provide clarifications and any supplemental information that is necessary. The City will provide a list of topics the Offeror should be prepared to address. At this stage, Offeror shall not be allowed to alter or amend their proposals. G. The City will evaluate each proposal using the following methodology: 1. Project Approach will be evaluated on a 100-point scale awarding up to the maximum score noted for each evaluation benchmark. Maximum Evaluation Benchmark Score 40 General Approach Narrative 25 Organizational Chart 15 QA/QC Program 10 Project Controls 10 Safety Program Project approach will be evaluated based on the quality and completeness of the content of the submittal proposal and its compliance with the requirements of this Section. Offerors that fail to meet the minimum requirements stated in this Section will receive a lower scores. Firm Experience will be evaluated on a 100-point scale awarding up to the maximum score noted for each evaluation benchmark. Maximum Evaluation Benchmark Score 50 Depth of project experience presented 30 Firm Certifications & Licenses 10 Firm qualifications 10 Firm Local Staffing & Response Depth of experience shall be scored based on the type, number and quality of projects presented in three areas: Control System and SCADA Replacements, Control System and SCADA Replacement experience shall be qualitatively scored using I/O count and relative similarity of system configuration and project components to Work required in the City's SCADA Replacement. Firm Certification & Licenses, Qualifications and Local Staffing & Response will be qualitatively evaluated based on the quality and completeness of the content of the submitted proposal. Offerors that fail to meet the minimum requirements stated in this Section will receive a lower score. CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 2 — AD3 0021 15 INSTRUCTIONS TO OFFERORS Page 13 of 22 Key Personnel & Subcontractors will be evaluated on a 100-point scale, awarding up to the maximum score noted for each evaluation benchmark. Maximum Evaluation Benchmark Score 85 Key Personnel Presented 15 Key Subcontractors Presented Key personnel will be evaluated will be qualitatively evaluated based on the quality and completeness of the resume experience presented, without regard to whether the staff is employed by the Prime Contractor or a listed subcontractor. Offerors that fail to meet the minimum requirements stated in this Section, including but not limited to not identifying Key Personnel, or providing staff with limited experience will receive lower scores. Subcontractor scoring will be limited to qualitatively evaluating the Offeror's proposal content identifying the roll of all subcontractors and suppliers in completing the Work, including the stated approach to meeting the goal noted in Section 00 45 42 — Business Equity Goal. 4. Schedule will be evaluated on a 100-point scale awarding up to the maximum score noted for each evaluation benchmark. Evaluation Benchmark 60 Schedule Level of Detail 40 Contract Time (days) required through Final Acceptance Time is of the essence in completing the Work. The Offeror shall provide a sufficient breakdown of schedule tasks and sub -tasks to display the activities necessary to meet the proposed Contract Time. The Schedule Level of Detail will be qualitatively evaluated based on the quality and completeness of the submitted schedule. Offerors that fail to meet the minimum requirements stated in this Section will receive a lower score. Offerors shall include a level of detail that is sufficient to verify that the Milestones noted by the Offeror in Section 00 42 10 — Proposal, Table 00 42 10-A can realistically be met. Proposals that fail to meet this requirement will receive no points for Schedule Level of Detail. Contract Time (days) will be quantitatively scored relative to all proposal schedules received. The offeror with the lowest number of total days to Final Acceptance will receive 40 points for Contract Time. All other offerors will receive a score based on the ratio of lowest number of days to Final Acceptance proposed by any offeror divided by the Offeror's days to Final Acceptance noted in Article 4.1 of the Section 00 42 10 Proposal. The score is provided by multiplying the ratio by 40 points. 5. Cost will be evaluated on a 100-point scale awarding up to the maximum score noted for each evaluation benchmark. Evaluation Benchmark 100 Total of Base Contract Proposal Items CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 2 — AD3 0021 15 INSTRUCTIONS TO OFFERORS Page 14 of 22 The cost of the proposal will be quantitatively scored relative to all offers received. The lowest Offeror in each Evaluation Benchmark above will receive 100 points. Additional proposals will receive a score based on the ratio of the lowest Total Amount Proposal Items received divided by the Total Amount the Offeror includes in Section 00 42 10 — Proposal, Exhibit A. The score is provided by multiplying the ratio by 100 points. H. After opening the Proposals and within forty-five (45) days of the opening, the City will evaluate and rank each Proposal with respect to the published selection criteria described under this Section. If the City determines that no other clarifying information is required, the evaluation process is complete. The highest-ranking Offeror shall become the Selected Offeror. L After opening and ranking, the City shall determine which Offeror provides the best value to the City on the basis of the initially submitted Proposal, without discussion or clarification, or the City may discuss elements of the Proposal with the Selected Offeror. Other than the data read at the public opening, the Owner shall not disclose any information included in the Proposals submitted by other Offerors in conducting such discussions. J. If the City determines that it is unable to reach a satisfactory Agreement with the Selected Offeror, the Owner will formally, and in writing, terminate discussions with that Offeror and proceed to the next Offeror based on selection ranking who becomes the new Selected Offeror until a Contract can be negotiated with a Selected Offeror or all Proposals have been rejected. K. Reference Checks: The City reserves the right to check any reference(s), regardless of the source of the reference information. Information may be requested and evaluated from references. The City reserves the right to use a third party to conduct reference checks. City may perform reference checks on any or all Offeror references. L. In addition to Offeror's relevant prequalification requirements, City may consider the qualifications and experience of Subcontractors, Suppliers, and other persons and organizations proposed for those portions of the Work where the identity of such Subcontractors, Suppliers, and other persons and organizations must be submitted as provided in the Contract Documents or upon the request of the City. City also may consider the operating costs, maintenance requirements, performance data and guarantees of major items of materials and equipment proposed for incorporation in the Work when such data is required to be submitted prior to the Notice of Award. M. Optional (Alternative) project components proposed by the Offeror: 1. Modifications of the Proposal, as noted in Paragraph 1.4 E of this Section, is prohibited. 2. Offerors desiring consideration of alternatives that require a change to the Contract Documents shall submit a question prior to the deadline noted in Section 00 11 15 Notice to Offerors noting the Contract Document changes required to allow the alternative. If such changes are acceptable to the City an addendum will be issued to all Prequalification Offerors. CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 2 — AD3 0021 15 INSTRUCTIONS TO OFFERORS Page 15 of 22 N. Evaluation and Ranking: Following the Proposal evaluations, compiling of the final ranking, and negotiations with Selected Offeror are completed, then the Evaluation Committee will provide award recommendation to the City. The City will in turn, issue an Intent to Award Notification to the Selected Offeror which, in the City's opinion, has submitted the proposal representing the best value to the City. 1.7 EXAMINATION OF PROPOSAL AND CONTRACT DOCUMENTS, OTHER RELATED DATA, AND SITE A. Before submitting a Proposal each Offeror: 1. Shall examine and carefully study the Contract Documents and other related data identified including "technical data" referred to in this Section. No information given by City or any representative of the City other than that contained in the Contract Documents and officially promulgated addenda thereto, shall be binding upon the City. 2. Shall attend the Pre -Proposal Site Visit. Due to security concerns, and the number and locations of sites accessed, and the sequence, will be limited and selected by the City in advance. The intent is to visit all WTPs to the extent possible and to limit the site visits to two calendar days. However, the City reserves the right to alter this prior to or during the site visit. Each prequalified Offeror shall select up to two (2) attendees to attend the site visit. Each Offeror shall send the names of the attendees to the City's Project Manager via email, a minimum of 48-hours in advance of the site visit. 3. Shall consider federal, state, and local Laws and Regulations that may affect cost, progress, performance or furnishing of the Work. 4. Shall study all: drawings of physical conditions relating to the work at the Site that have been identified in the Contract Documents as containing reliable "technical data." 5. Is advised that the Contract Documents on file with the City shall constitute all of the information which the City will furnish. All additional information and data which the City will supply after promulgation of the formal Contract Documents shall be issued in the form of written addenda and shall become part of the Contract Documents just as though such addenda were actually written into the original Contract Documents. No information given by the City other than that contained in the Contract Documents and officially promulgated addenda thereto, shall be binding upon the City. 6. Should perform independent research, investigations, tests, borings, and such other means as may be necessary to gain a complete knowledge of the conditions which will be encountered during the construction of the project. For projects with restricted access, upon request, City may provide each Offeror access to the site to conduct such examinations, investigations, explorations, tests, and studies as each Offeror deems necessary for submission of a Proposal. Offeror must fill all holes and clean up and restore the site to its former conditions upon completion of such explorations, investigations, tests and studies. CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 2 — AD3 0021 15 INSTRUCTIONS TO OFFERORS Page 16 of 22 7. Shall determine the difficulties of the Work and all attending circumstances affecting the cost of doing the Work, time required for its completion, and obtain all information required to make a proposal. Offerors shall rely exclusively and solely upon their own estimates, investigation, research, tests, explorations, and other data which are necessary for full and complete information upon which the proposal is to be based. It is understood that the submission of a proposal or proposal is prima - facie evidence that the Offeror has made the investigations, examinations and tests herein required. 8. Shall promptly notify City of all conflicts, errors, ambiguities, or discrepancies in or between the Contract Documents and such other related documents. The Contractor shall not take advantage of any gross error or omission in the Contract Documents, and the City shall be permitted to make such corrections or interpretations as may be deemed necessary for fulfillment of the intent of the Contract Documents. B. Reference is made to Section 00 73 00 — Supplementary Conditions for identification of: 1. Copies of such reports and drawings will be made available by City to all prequalified offerors. Those reports and drawings may not be part of the Contract Documents, but the "technical data" contained therein upon which Offeror is entitled to rely as provided in Paragraph 4.02. of the General Conditions has been identified and established in Paragraph SC 4.02 of the Supplementary Conditions. Offeror is responsible for any interpretation or conclusion drawn from any "technical data" or any other data, interpretations, opinions, or information. 2. Standard insurance requirements, coverages, and limits. C. The submission of a Proposal will constitute an incontrovertible representation by Offeror: (i) that Offeror has complied with every requirement of this Article, (ii) that without exception the Proposal is premised upon performing and furnishing the Work required by the Contract Documents and applying the specific means, methods, techniques, sequences or procedures of construction (if any) that may be shown or indicated or expressly required by the Contract Documents, (iii) that Offeror has given City written notice of all conflicts, errors, ambiguities and discrepancies in the Contract Documents and the written resolutions thereof by City are acceptable to Offeror, and when said conflicts, etc., have not been resolved through the interpretations by City as described in Paragraph 6., and (iv) that the Contract Documents are generally sufficient to indicate and convey understanding of all terms and conditions for performing and furnishing the Work. D. The provisions of this Article, inclusive, do not apply to Asbestos, Polychlorinated biphenyls (PCBs), Petroleum, Hazardous Waste or Radioactive Material covered by Paragraph 4.06. of the General Conditions, unless specifically identified in the Contract Documents. CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 2 — AD3 0021 15 INSTRUCTIONS TO OFFERORS Page 17 of 22 1.8 AVAILABILITY OF LANDS FOR WORK, ETC. A. The lands upon which the Work is to be performed, rights -of -way and easements for access thereto and other lands designated for use by Contractor in performing the Work are identified in the Contract Documents. The lands required are within existing City owned facilities. All additional lands and access thereto required for temporary construction facilities, construction equipment or storage of materials and equipment to be incorporated in the Work are to be obtained and paid for by Contractor. Easements for permanent structures or permanent changes in existing facilities are to be obtained and paid for by City unless otherwise provided in the Contract Documents. B. Outstanding right-of-way, easements, and/or permits to be acquired by the City are listed in Paragraph SC 4.01 of the Supplementary Conditions. In the event the necessary right- of-way, easements, and/or permits are not obtained, the City reserves the right to cancel the award of contract at any time before the Offeror begins any construction work on the project. C. The Offeror shall be prepared to commence construction without all executed right-of- way, easements, and/or permits, and shall submit a schedule to the City of how construction will proceed in the other areas of the project that do not require permits and/or easements. 1.9 INTERPRETATIONS AND ADDENDA A. All questions about the meaning or intent of the Contract Documents are to be directed to City in writing on or before the deadline for questions noted in Section 00 11 15 — Notice to Offerors. Questions received after the published date and time may not be responded to. Interpretations or clarifications considered necessary by City in response to such questions will be issued by Addenda delivered to all parties recorded by City as having received the Contract Documents. Only questions answered by formal written Addenda will be binding. Oral and other interpretations or clarifications will be without legal effect. Address all questions to the City under the respective Project via the Procurement Portal: https:Hfortworthtexas.bonfirehub.com/aortal/?tab=oi3en0nnortunities B. Addenda may also be issued to modify the Contract Documents as deemed advisable by City. C. Addenda or clarifications may be posted via the City's electronic document management and collaboration system. Clarifications, via addenda, will be posted under the respective Project via the Procurement Portal: https:Hfortworthtexas.bonfirehub.com/portal/?tab=oi2en0pportunities CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 2 — AD3 0021 15 INSTRUCTIONS TO OFFERORS Page 18 of 22 D. A pre -submittal conference with pre -qualified Offerors may be held at the time and place indicated in the Advertisement or Invitation to Offerors. Representatives of City will be present to discuss the Project. Offerors are encouraged to attend and participate in the conference. City will transmit to all prospective Offerors of record such Addenda as City considers necessary in response to questions arising at the conference. Oral statements may not be relied upon and will not be binding or legally effective. 1.10 PROPOSAL SECURITY A. Each Proposal must be accompanied by a Proposal Bond made payable to City in an amount of five (5) percent of Offeror's maximum Proposal price, on the form attached or equivalent, issued by a surety meeting the requirements of Paragraph 5.01 of the General Conditions. B. The Proposal Bond provided by an Offeror will be retained until the conditions of the Notice of Award have been satisfied. If the Successful Offeror fails to execute and return the Contract Documents within 14 days after the Notice of Award conveying same, City may consider Offeror to be in default, rescind the Notice of Award and act on the Proposal Bond. Such action shall be City's exclusive remedy in the event Offeror is deemed to have defaulted. 1.11 PERFORMANCE BONDING A. Offerors shall note that the Work may be bonded in phases in accordance with the Section 00 72 00 — General Conditions as modified by Section 00 73 00 Supplementary Conditions SC-5.02 A. 1.12 CONTRACT TIMES A. The number of days within which, or the dates by which, Milestones are to be achieved in accordance with the General Requirements and the Work is to be completed and ready for Final Acceptance is set forth in Section 00 52 45 — Agreement or incorporated therein by reference to Section 00 42 10 — Proposal. 1.13 LIQUIDATED DAMAGES A. Provisions for liquidated damages are set forth in the Agreement. 1.14 SUBSTITUTE AND "OR -EQUAL" ITEMS A. The Contract, if awarded, will be on the basis of materials and equipment described in the Contract Documents without consideration of possible substitute or "or -equal" items. Whenever it is indicated or specified in the Contract Documents that a "substitute" or "or -equal" item of material or equipment may be furnished or used by Contractor if acceptable to City, application for such acceptance will not be considered by City until after the Effective Date of the Agreement. The procedure for submission of any such application by Contractor and consideration by City is set forth in Paragraphs 6.05A., 6.05B. and 6.05C. of the General Conditions and is supplemented in Section 01 25 00 of the General Requirements. CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 2 — AD3 0021 15 INSTRUCTIONS TO OFFERORS Page 19 of 22 1.15 SUBCONTRACTORS, SUPPLIERS AND OTHERS A. In accordance with the City's Business Equity Ordinance No. 24534-11-2020 the City has goals for the participation of minority business and/or women business enterprises in City contracts $100,000 or greater. See Section 00 45 42 — Business Equity Goal for the NMBE Project Goals and additional requirements. Failure to comply shall render the Offeror as non -responsive. Business Equity Ordinance No. 24534-11-2020, as amended, codified at: https:Hcodelibrary.amle�4al.com/codes/ftworth/latest/ftworth tx/0-0-0-22593 B. No Contractor shall be required to employ any Subcontractor, Supplier, other person, or organization against whom Contractor has reasonable objection. 1.16 PROPOSAL FORM A. The Proposal Form is included with the Contract Documents; additional copies may be obtained from the City. B. All blanks on the Proposal Form must be completed and the Proposal Form signed in ink. Erasures or alterations shall be initialed in ink by the person signing the Proposal Form. A price shall be indicated for each listed Proposal Form Item, Alternative Item, and Unit Price Item listed therein. The Proposal does not include optional alternatives, the words "No Bid," "No Change," or "Not Applicable" shall not be entered. Offeror shall state the prices for which the Offeror proposes to do the work contemplated or furnish materials required. All entries shall be legible. C. Proposals by corporations shall be executed in the corporate name by the president or a vice-president or other corporate officer accompanied by evidence of authority to sign. The corporate seal shall be affixed. The corporate address and state of incorporation shall be shown below the signature. D. Proposals by partnerships shall be executed in the partnership name and signed by a partner, whose title must appear under the signature accompanied by evidence of authority to sign. The official address of the partnership shall be shown below the signature. E. Proposals by limited liability companies shall be executed in the name of the firm by a member and accompanied by evidence of authority to sign. The state of formation of the firm and the official address of the firm shall be shown. F. Proposals by individuals shall show the Offeror's name and official address. G. Proposals by joint ventures shall be executed by each joint venture in the manner indicated on the Proposal Form. The official address of the joint venture shall be shown. H. All names shall be typed or printed in ink below the signature. I. The Proposal shall contain an acknowledgement of receipt of all Addenda, the numbers of which shall be filled in on the Proposal Form. CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 2 — AD3 0021 15 INSTRUCTIONS TO OFFERORS Page 20 of 22 J. Postal and e-mail addresses and telephone number for communications regarding the Proposal shall be shown. K. Evidence of authority to conduct business as a Nonresident Offeror in the state of Texas shall be provided in accordance with Section 00 43 37 — Vendor Compliance to State Law Non -Resident Offeror. 1.17 SUBMISSION OF PROPOSALS A. Proposals shall be submitted electronically as prescribed in Section 00 11 15 — Notice to Offerors. 1.18 WITHDRAWAL OF PROPOSALS A. Proposals addressed to the Project Manager and filed with the City may be withdrawn prior to the time set for proposal opening. A request for withdrawal must be made in writing and delivered to the City's Project Manager prior to the opening of Proposals. A timely withdrawn proposal will be returned to the Offeror. If the withdrawal request is received prior to the deadline noted in Section 00 11 15 — Notice to Offerors for Proposal Due Date, the Proposal will not be read aloud and will thereafter be returned unopened. B. In the event any Proposal for which a withdrawal request has been timely filed has been inadvertently opened, said Proposal and any record thereof will subsequently be marked "Withdrawn" and will be given no further consideration for the award of contract. 1.19 OPENING OF PROPOSALS A. Proposals will be received, publicly opened and the names of offerors and total monetary proposal cost read aloud publicly. 1.20 PROPOSALS TO REMAIN SUBJECT TO ACCEPTANCE A. All Proposals will remain subject to acceptance for a minimum of 90 days, or the time period specified for Notice of Award and execution and delivery of a complete Agreement by Successful Offeror. City may, at City's sole discretion, release any Proposal and nullify the Proposal security prior to that date. CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 2 — AD3 0021 15 INSTRUCTIONS TO OFFERORS Page 21 of 22 1.21 AWARD OF CONTRACT A. City reserves the right to reject any or all Proposals, including without limitation the rights to reject any or all nonconforming, nonresponsive, unbalanced, or conditional Proposals and to reject the Proposal of any Offeror if City believes that it would not be in the best interest of the Project to make an award to that Offeror. City reserves the right to waive informalities not involving price, contract time or changes in the Work and award a contract to such Offeror. Discrepancies between the multiplication of units of Work and unit prices will be resolved in favor of the unit prices. Discrepancies between the indicated sum of any column of figures and the correct sum thereof will be resolved in favor of the correct sum. Discrepancies between words and figures will be resolved in favor of the words. B. Any or all proposals will be rejected if City has reason to believe that collusion exists among the Offerors, Offeror is an interested party to any litigation against City, City or Offeror may have a claim against the other or be engaged in litigation, Offeror is in arrears on any existing contract or has defaulted on a previous contract, Offeror has performed a prior contract in an unsatisfactory manner, or Offeror has uncompleted work which in the judgment of the City will prevent or hinder the prompt completion of additional work if awarded. C. If the Contract is to be awarded, it will be awarded to responsible and responsive Offeror whose evaluation by City as described above in this Section indicates that the award will be in the best interests of the City. D. The Proposals will be evaluated by the City in consultation with the City's project team and Evaluation Committee using procurement procedures that conform to Texas Government Code Chapter 2269. If a Contract is awarded, it will be awarded to the offeror submitting the best value to the City. The City is not bound to accept the lowest priced Cost Proposal if that Cost Proposal is judged not to be the best value for the City, as solely determined by the City. E. Pursuant to Texas Government Code Chapter 2252.001, the City will not award contract to a Nonresident Offeror unless the Nonresident Offeror's proposal is lower than the lowest proposal submitted by a responsible Texas Offeror by the same amount that a Texas resident offeror would be required to price the proposal of a Nonresident Offeror to obtain a comparable contract in the state in which the nonresident's principal place of business is located. F. A contract is not awarded until formal City Council authorization. If the Contract is to be awarded, City will award the Contract within 90 days after the day of the Proposal opening unless extended in writing. No other act of City or others will constitute acceptance of a Proposal. Upon the contract award, a Notice of Award will be issued by the City. G. The Offeror is required to fill out and sign the Certificate of Interested Parties Form 1295 and the form must be submitted to the Project Manager before the contract will be presented to the City Council. The form can be obtained at https://www.ethics.state.tx.us/data/forms/1295/1295.pdf CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 2 — AD3 0021 15 INSTRUCTIONS TO OFFERORS Page 22 of 22 H. Failure or refusal to comply with the requirements of this Section may result in rejection of Proposal. 1.22 SIGNING OF AGREEMENT A. When City issues a Notice of Award to the Successful Offeror, it will be accompanied by the required number of unsigned counterparts of the Contract Documents. Within 14 days thereafter, Contractor shall sign and deliver to the City the executed Agreement and required number of counterparts (Attachments) in accordance with Article 5.1.A.2 of Section — 00 52 45 Agreement. The counterparts include the required Bonds, Certificates of Insurance, and all other required documentation as noted in in Section 00 52 45 — Agreement. B. City shall thereafter deliver one fully signed counterpart to Contractor. PART 2 — PRODUCTS (NOT USED) PART 3 — EXECUTION (NOT USED) ++END OF SECTION++ CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 2 — AD3 ADDENDUM NO. 4 Page 1 of 6 CITY OF FORT WORTH, TEXAS CONTRACT FOR THE CONSTRUCTION OF SCADA SYSTEM REPLACEMENT ADDENDUM NO. 4 This Addendum is part of the Contract Documents and modifies the Contractor for The Construction of SCADA System Replacement Document dated March 2024 for the above referenced project. This change affects the Document distributed on March 21, 2024 to prequalified Offerors. Acknowledge receipt of this Addendum in accordance with the requirements in Section 00 21 15 Instructions to Offerors Article 1.16 I. Failure to do so may result in the Proposal being deemed non- responsive. Overview and General Clarifications: 1. This addendum incorporates changes in the Contract Document in Section 00 11 15 Notice to Offerors to reflect a new time for the Pre -proposal Conference. 2. This addendum incorporates changes in the Contract Document in Section 00 21 15 Instructions to Offerors and Section 40 61 13 SCADA System General Provisions to correct formatting and provide additional clarification on proprietary solutions. This addendum incorporates changes in the Contract Document in Section 01 11 13 Summary of Work to correct formatting and provide clarification on installation scope. 4. This addendum provides questions the City has received to date. ADDENDUM ITEMS (SPECIFICATION MODIFICATIONS & PROJECT CLARIFICATIONS): 1. Section 00 1115 Notice to Offerors, delete the included Schedule for Procurement and replace it with the following schedule: "SCHEDULE FOR PROCUREMENT Pt Advertisement for CSP — Prequalification Requirements 2"d Advertisement for CSP — Prequalification Requirements Virtual Prequalification Q&A Meeting Deadline for Prequalification Questions Deadline to Request Prequalification Offerors Notification of Prequalification Contract Document Release Date (anticipated) Pre -proposal 2 Day Site Visit (Primary) Pre -proposal Conference — In Person and Virtual (anticipated) Pre -proposal 2 Day Site Visit (Backup)* Deadline for Questions (anticipated) Deadline for Responses via Addenda (anticipated) Proposal Due Date (anticipated) Evaluation of Proposals (anticipated) March 21, 2024 March 28, 2024 April 1, 2024, 2:00 PM CT April 5, 2024 April 12, 2024, 4: 00 PM (Local Time) April 19, 2024 April 19, 2024 May 1 —May 2, 2024 May 8, 2024, 8:30 9:30 AM CT May 8 — May 9, 2024 May 15, 2024, 5:00 PM CT May 22, 2024, 5:00 PM CT May 30, 2024 by 1:30 PM CT May 31, 2024 through June 12, 2024 ADDENDUM NO. 4 Page 2 of 6 SCHEDULE FOR PROCUREMENT (CONTINUED) Oral Clarifications (anticipated, if required) Notice to Proceed (anticipated) Notes: June 6, 2024 through June 11, 2024 August 7, 2024 * Should adverse weather or unforeseen events at the Water Treatment Plants require rescheduling of the Pre -proposal 2 Day Site Visit from the Primary dates above, it is the City's intent to conduct the in conjunction with the Pre -Proposal Conference the following week on the dates indicated." 2. Section 00 1115 Notice to Offerors, delete the included "PRE -PROPOSAL CONFERENCE" section and replace it with the following: "PRE -PROPOSAL CONFERENCE — In -person and Virtual Conference An in -person pre -proposal conference will be held as described in Section 00 21 15 — Instructions to Offerors on the following anticipated date and time, as well as simultaneously via a web conferencing application. DATE: May 8, 2024 TIME: 8:30 - 9:30 AM CT An invitation with a link to the web conferencing application will be distributed to Prequalified Offerors. The presentation along with any questions and answers provided at the Pre -proposal Conference will be issued as an Addendum. Prequalified Offerors may also ask questions or comments in accordance with Section — 00 21 15 Instructions to Offerors Article 1.9. Any questions received will be answered by Addenda. Addenda will be issued pursuant to Section 00 21 15 — Instructions to Offerors, Article 1.9." Section 00 2115 Instructions to Offerors, add Article 1.4 B. 2. i. immediately following Article 1.4 B. 2. h. that states the following: "i. Proprietary solutions, protocols and communications deviating from those identified in the project will not be accepted and constitute rejection of the offer. Demonstrate a distributed solution whereby data can be available from any site at Centralized SCADA. Demonstrate adherence to the City HMI and PLC standards as provided in Attachment 1. Products identified with no exceptions and no substitutions must be submitted as such." ADDENDUM NO. 4 Page 3 of 6 4. Section 01 11 13 Summary of Work, delete Article 1.1 A. and replace it with the following: "A. This Section includes the following Articles: Article Title 1.1 Section Includes 1.2 Location and Description of Work 1.3 Other Construction Contracts 1.4 Work by Others 1.5 Work by City 1.6 Summary of Work 1.7 Contractor's Use of Site 1.8 Partial Utilization by City" 5. Section 01 11 13 Summary of Work, delete Article 1.2 B. and replace it with the following: "13. Overall Description of Work: Design, test, start-up, and maintain through Final Acceptance a complete replacement for the City's Water Department Supervisory Control and Data Acquisition (SCADA) system, inclusive of but not limited to: upgraded SCADA systems at each of the five Water Treatment Plant (WTPs); a new Centralized SCADA system, including remote alarm notification; an upgraded SCADA system architecture to support the SCADA Replacement; a new data architecture to support a comprehensive historical data collection, and reporting interface; other work elements to support the SCADA upgrades. The Work also includes installation and configuration of all SCADA software, including City -furnished software and other associated SCADA software procured by the Contractor as identified in the Contract Documents." 6. Section 0129 73 Schedule of Values, delete Article 1.3 B. 3. And replace with the following: "3. The Schedule of Values shall present a summary of cost at the proposal item level. For each lump sum and unit cost item provide a section title and sub -total amount then present all breakout rows necessary to meet the requirements of the Contract Documents. Additional breakout shall include: a. Project Management shall be a breakout row for each Proposal Item. b. Preconstruction work, summarized under Proposal Items No. 2 and No. 3, shall also at minimum be divided into smaller breakout rows for each Key Activity defined in Section 4061 13. c. Construction work, summarized under Proposal Item No. 4 through No. 9, shall also at minimum be divided into smaller breakout rows for: 1) Electrical installation incorporated by Change Order. 2) Hardware incorporated by Field Order or Change Order. 3) Software procured. 4) Installation of Software. 5) Reprogramming of existing PLCs (except work under Proposal Item No. 4). 6) PLC programming (except work under Proposal Item No. 4). 7) Training provided. 8) Testing. 9) Non -labor expenses. d. Additional breakout necessary to comply with the Articles below." ADDENDUM NO. 4 Page 4 of 6 7. Section 40 6113 SCADA System General Provisions, delete this section in its entirety and replace it with ATTACHMENT 1 — AD4. The changes in this section correct formatting and provides updated requirements in Article 1.1 A. 2. 8. The City has received the following questions: QUESTION 7: 00 21 15 Instructions to Offerors 1A.A. I -Reference is made to Section 00 46 12-Statement of Qualifications. Is Section 00 46 12 to be completed and submitted with the proposal? 00 46 12 is also referenced in: 00 21 15 1.4 A.3, 00 21 15 1.4 A.7., 00 21 15 1.4 C.1., 00 21 15 1.4 C.2., 00 21 15 1.4 CA.i, 00 21 15 1.4 D.6., 00 21 15 1.4 E.2., 00 21 15 1.4 E.3., 00 42 10 2.6, 00 42 10 5.1 e, 00 42 10 5.1 j. 00 52 45 1 and 00 52 45 5.1 A.2. a.3. ANSWER 7: Yes, each offeror shall complete Section 00 46 12 as instructed. OF *: ... ROSSER R. STANDEFER. 92755 -a ......�.....i Rosser R. Standifer, PE Principal Engineer Arcadis Addendum No. 4 Issued by the City of Fort Worth Date: April 30, 2024 Alexander Pierce Project Manager City of Fort Worth END OF ADDENDUM No. 4 ADDENDUM NO. 4 Page 5 of 6 ADDENDUM NO. 4 Page 6 of 6 ++THIS PAGE INTENTIONALLY LEFT BLANK++ 4061 13 SCADA SYSTEM GENERAL PROVISIONS Page 1 of 32 SECTION 40 61 13 SCADA SYSTEM GENERAL PROVISIONS PART 1 — GENERAL This subsection includes: Article Title 1.1 SCOPE 1.2 SCADA SYSTEM ARCHITECTURE DESCRIPTION 1.3 FAMILIARIZATION AND PRELIMINARY ASSESSMENT 1.4 DESIGN 1.5 PROGRAMMING AND CONFIGURATION 1.6 FACTORY ACCEPTANCE TESTING 1.7 CUTOVER, FIELD TESTING, AND START-UP 1.8 SYSTEM MAINTENANCE, FINAL ACCEPTANCE, AND WARRANTY 1.9 REFERENCES 1.10 QUALITY ASSURANCE 1.11 COORDINATION MEETINGS AND WORKSHOPS 1.12 SUBMITTALS 1.1 SCOPE A. General Description of Scope: 1. The Contractor shall provide preconstruction and construction phase services to plan, design, configure, test, place into operation, and maintain to Final Acceptance the new Water Department Supervisory Control and Data Acquisition (SCADA) system at the five Water Treatment Plants (WTPs). The Work shall also include remote alarm monitoring and notification and a system wide data interface to link historical databases from the WTPs to a Centralized SCADA system, which will be used to provide system reports, and an interface for tablet data. The work also includes a Test Bench to allow City personnel to test system behavior offline prior to enabling in the production environment. 2. Proprietary solutions, protocols and communications deviating from those identified in the Contract Documents are not acceptable. 3. The Contractor shall provide the following project services. Each item is further detailed in this section. a. Pre -Construction Services 1) Familiarization and Preliminary Assessment 2) Design b. Construction Services 1) Programming and Configuration 2) Factory Acceptance Testing 3) Cutover, Field Testing, and Start -Up 4) System Maintenance, Final Acceptance, and Warranty 4. The Water Treatment Plants included in this upgrade are the following: a. North Holly WTP 1) Existing SCADA system: HSQ Miser 2) Existing PLCs: Schneider Electric Modicon Quantum, M340 and M580. CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 1— AD4 4061 13 SCADA SYSTEM GENERAL PROVISIONS Page 2 of 32 b. South Holly WTP 1) Existing SCADA system: HSQ Miser 2) Existing PLCs: Schneider Electric Modicon Quantum, M340, and M580 c. Westside WTP 1) Existing SCADA system: HSQ Miser and FactoryTalk View SE 2) Existing PLCs: Allen Bradley ControlLogix and CompactLogix d. Eagle Mountain WTP 1) Existing SCADA system: HSQ Miser and GE Cimplicity 2) Existing PLCs: GE 90-70, RX3i, RX7i e. Rolling Hills 1) Existing SCADA system: HSQ Miser 2) Existing PLCs: Schneider Electric Modicon Quantum and M580 Project SCADA System Hardware and Software: a. The City shall furnish Inductive Automation Ignition SCADA software and licenses required for the SCADA system as specified in the Contract Documents. Refer to Attachment 2 — City -furnished SCADA Software and Licenses. b. The Contractor shall design the Water Department SCADA system architecture and specify all SCADA system hardware and software components as described in the Contract Documents and in coordination with Water IT. Refer to Article 1.2 — SCADA System Architecture Description in this section. c. The City shall procure, install, and configure the SCADA system computer and network hardware and associated software, and any other hardware required to make the SCADA system fully functional in accordance with the Contractor's design. d. The City shall procure the SQL Historian server software. The Contractor shall procure third -party SCADA communication software and any other SCADA software required for the functionality of the SCADA system as outlined in the Contract Documents and in accordance with Attachment 1 — PLC and HMI Configuration Standards. e. The Contractor shall install and configure all SCADA and PLC software and applications required for the functionality of the SCADA system as outlined in the Contract Documents and in accordance with Attachment 1 — PLC and HMI Configuration Standards. f. The City shall procure the SQL Historian server software. The Contractor shall procure the identified third -party SCADA communication software and any other SCADA software required for the functionality of the SCADA system as outlined in Contract Documents and in accordance with Attachment 1 — PLC and HMI Configuration Standards. g. The Contractor shall install and configure all SCADA and PLC software and applications required to for the functionality of the SCADA system as outlined in the Contract Documents and in accordance with Attachment 1 PLC and HMI Configuration Standards. h. Refer to Attachment 7 — SCADA Assets Responsibility Matrix for the division of work between the City and the Contractor, as it pertains to component selection, purchase, configuration, and installation of SCADA system software and hardware assets. 6. Work at the WTPs and Centralized SCADA include but is not limited to: a. Test, start-up, successfully pass respective Operational Availability Demonstration tests, and maintain to project Final Acceptance all SCADA hardware furnished by the City to implement the new SCADA system at each WTP and centralized SCADA. It CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 1— AD4 4061 13 SCADA SYSTEM GENERAL PROVISIONS Page 3 of 32 shall include High Availability (HA) SCADA and Historian servers, thin -client desktop and industrial panel mounted workstations, wall mounted SCADA monitors, and other components as specified in the contract documents, in coordination with Water IT. b. Assess, document, configure, cutover, test, start-up, successfully pass respective Operational Availability Demonstration tests, and maintain to project Final Acceptance the existing PLC systems as specified in the contract documents, in coordination with the City. Refer to Attachment 6 — Existing WTP PLC Systems Table. C. Configure, test, successfully pass respective Operational Availability Demonstration tests, and maintain to project Final Acceptance all SCADA system application software procured by the City for use on this project (Refer to Attachment 2 — City - Furnished SCADA Software and Licenses, and Attachment 7 — SCADA Assets Responsibility Matrix). All SCADA servers shall utilize virtualization software. Water IT shall furnish and configure all necessary software and licenses required at each site to enable, configure, and manage the virtual environment. Software shall include operating system software, virtual machine management software and machine image backup software. d. Configure, test, successfully pass respective Operational Availability Demonstration tests, and maintain to project Final Acceptance all local SQL Historian server software used to save SCADA data on the Local networks at each WTP, Pass -through SQL Historian, and Central SQL Historian server software. Coordinate with Water IT to schedule the database appropriately to be transferred to the SCADA SQL Pass - through and Central SQL Server. e. Configure, test, successfully pass respective Operational Availability Demonstration tests, and maintain to project Final Acceptance the SCADA application software and test PLC units to implement the new SCADA system Test Bench. The Test Bench shall be used to test the application prior to being placed in production. f. Configure, test, successfully pass respective Operational Availability Demonstration tests, and maintain to project Final Acceptance alarm notification software and hardware for the Centralized SCADA system remote notification. g. Test, successfully pass respective Operational Availability Demonstration tests, and maintain to project Final Acceptance all managed network switches and firewalls as agreed during the Design phase. Coordinate all configuration of switches and firewalls with Water IT. h. Test, successfully pass respective Operational Availability Demonstration tests, and maintain to project Final Acceptance all software and hardware related to the domain controllers and Multi -Factor Authentication at each WTP, and the SCADA Support Server as agreed during the Design phase. Coordinate all configurations with Water IT. i. Test, successfully pass respective Operational Availability Demonstration tests, and maintain to project Final Acceptance all software and databases related to production of the entire system SCADA data interface, including the data warehouse interface for all systems as identified, custom interfaces between Centralized SCADA and LIMS and Ovation, tablets and tablet interface at Centralized SCADA, reports at Centralized SCADA and local WTP. Coordinate all configurations with Water IT. Work includes minimum items listed below with associated work defined herein and in Section 40 68 63 — SCADA System Programming and Configuration: CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 1— AD4 4061 13 SCADA SYSTEM GENERAL PROVISIONS 1) Historian databases system -wide including Historian, Centralized SCADA 2) Centralized SCADA system 3) Data Warehouse Interface 4) Custom data source interfaces (LIMB, Ovation) 5) Business Reports 6) Local Plant Operational Reports 7) Remote Tablets 8) Remote Alarm Notification Page 4 of 32 at local WTPs, Pass -through B. Related Sections: 1. Section 01 11 13 — Summary of Work 2. Section 01 14 16 — Coordination with City's Operations 3. Section 40 6121 — SCADA System Factory Acceptance Testing 4. Section 40 6123 — SCADA System Field Assessment, Testing, and Start-up 5. Section 40 6126 — SCADA System Training 6. Section 40 68 63 — SCADA System Programming and Configuration 1.2 SCADA SYSTEM ARCHITECTURE DESCRIPTION A. It is the responsibility of the Contractor, in coordination with the City, as outlined herein, to fully design the Fort Worth Water Department (FWWD) SCADA system architecture. The following is a narrative description of the general features and components that are anticipated to constitute the FWWD SCADA system architecture. B. The new FWWD SCADA architecture shall include, but not be limited to the following main components and features. Refer to Attachment 7 — SCADA Assets Responsibility Matrix for a comprehensive list of SCADA system hardware and software components to be furnished under this Contract and the respective intended service. 1. Dedicated fault tolerant WTP SCADA system servers 2. WTP SCADA thin -client desktop and industrial touchscreen workstations 3. WTP SCADA desktop and wall -mount monitors 4. Dedicated WTP SCADA Network Attached Storage (NAS) units 5. Dedicated local WTP Domain Controller (DC) servers 6. Redundant SCADA network firewall system 7. Central SCADA network industrial demilitarized zone (iDMZ) 8. iDMZ server including pass -through Historian 9. SCADA Network Time Protocol (NTP) server in iDMZ 10. Dedicated Layer-3 network switches for WTPs and iDMZ 11. SCADA Test Bench, including test server, workstation, and PLCs in iDMZ 12. Central SCADA server in IT/Enterprise network 13. Alarm notification cellular modem in iDMZ 14. Central Reporting server in IT/Enterprise network 15. Remote access to Central SCADA and Central Reporting servers 16. SCADA remote access tablets C. Dedicated SCADA system servers shall be furnished for the following WTPs. 1. South and North Holly WTPs (a common server setup for both plants) 2. Rolling Hills WTP CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 1— AD4 4061 13 SCADA SYSTEM GENERAL PROVISIONS Page 5 of 32 3. Eagle Mountain WTP 4. Westside WTP D. All SCADA system servers shall be configured for virtualization to support multiple virtual machine (VM) servers within each physical server. The following VMS shall be allocated. 1. WTP SCADA servers: a. VM1 —Management Server b. VM2 — Primary SCADA Server C. VM3 — Backup SCADA Server d. VM4 — Local SQL Historian Server 2. iDMZ server: a. VM1 —Management Server b. VM2 — SCADA Support Server c. VM3 — Domain Controller d. VM4 — SCADA SQL Pass -Through Server 3. Test Bench server: a. VM1 —Management Server b. VM2 — SCADA Server C. VM3 — Test d. VM4 — Test 4. Central SCADA server: a. VM1 —Management Server b. VM2 — Primary SCADA Server C. VM3 — Backup SCADA Server d. VM4 — Local SQL Historian Server 5. Central Reporting server: a. VM1 —Management Server b. VM2 — Central SQL Historian Server C. VM3 — Central Reporting Server E. Each WTP SCADA system shall be equipped with a "fault -tolerant" server solution designed to continue operating without interruption, even in the presence of major hardware or software failures. Fault tolerance can either be implemented through clustering of VMS across multiple physical servers within the respective virtual environments, or by utilizing physical server computers with full redundancy built into their hardware architecture. F. The City -furnished Ignition licenses support redundant configuration. If the virtual fault tolerant server solution is implemented, the Primary and Backup Ignition VMS shall be installed on different physical servers to minimize the risk of downtime in the event of a failure. G. There shall be a single/shared Industrial Demilitarized Zone (iDMZ) as opposed to a separate DMZ per treatment plant. Centralized SCADA infrastructure shall reside within the existing Enterprise/IT network. H. The WTPs shall be connected to the DMZ/City Hall Data Center via AT&T Switched Ethernet circuits (Configuration of circuits by Water IT Department). I. The SCADA network shall be equipped with a redundant pair of firewall appliances. The WTP SCADA systems shall have dedicated zones configured in the redundant firewall system to CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 1— AD4 4061 13 SCADA SYSTEM GENERAL PROVISIONS Page 6 of 32 protect each site. A separate firewall zone shall also be configured for the iDMZ. Layer-3 gateways shall be provided for each firewall zone to facilitate network segmentation and traffic inspection. Water IT shall be responsible for the configuration of the managed network switches and firewalls. J. The SCADA Test Bench shall mimic a typical WTP SCADA system setup as closely as possible, inclusive of components, software and connections, so that server upgrades, patches, firmware updates and other operational changes can be performed/tested/validated to verify that no impacts to the production SCADA systems could result from those changes prior to their rollout into the field. K. The local SQL Historian server at every WTP shall be configured to retain raw data for 10 years. The Centralized SQL reporting server, which will perform metrics reporting in a manner more digestible for upper management, shall retain data for 10 years. The SQL "pass -through" server shall reside within the DMZ and receive all the SQL data from the local WTP SQL servers and forward to the Centralized SQL Historian server that resides at the 'Data Warehouse." SQL data from the "pass -through" SQL server will only be "pushed" from this server in order to facilitate a secure one-way flow of data towards the City's existing "Data Warehouse". The "pass - through" SQL server will retain raw data for 3 years. The Centralized and pass -through SQL servers shall be configured by the City. L. WTP operation staff shall have remote access to the Centralized SCADA system through use of tablets via cellular communications (furnished by the City). Operators shall be allowed view - only access to the Centralized SCADA HMI application and use data entry forms to populate field -collected data to select Central SCADA reports. The tablets shall be configured to buffer/hold manual -entry data if access to the Centralized SCADA system is lost and backfill that data once connection is restored. M. SCADA User Authentication shall be handled by a centralized SCADA Active Directory with a fallback mechanism of local caching of credentials in the event that communication is disrupted. Users that will be making operational changes to the SCADA servers or environment shall be required to authenticate via Multi -Factor Authentication (MFA). MFA shall be configured in the SCADA applications. N. Communications with existing Power Monitor devices shall be over Modbus protocol. O. Communication with existing UPSs shall be over SNMP protocol. P. IP addresses of all existing PLCs in Category A defined in Attachment 6 — Existing WTP PLC Systems Table shall be changed following the City -provided IP scheme. This shall be coordinated with IP changes to the SCADA network devices. Water IT shall be responsible for configuration of all network devices. 1.3 FAMILIARIZATION AND PRELIMINARY ASSESSMENT A. General: 1. Project services in this phase include familiarization with existing Water Treatment Plant (WTP) SCADA systems, assessment of existing system conditions, review of existing CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 1— AD4 4061 13 SCADA SYSTEM GENERAL PROVISIONS Page 7 of 32 software applications, and creation of as -installed Functional Control Narrative (FCN) documents. B. Key Activities: 1. To increase an understanding of the project and to facilitate implementation of the SCADA system upgrade at all WTPs, Contractor shall review available documents including but not limited to: a. Facility As -Built drawings and Operations and Maintenance (O&M) Manuals. b. PLC code. C. HMI screens and database. d. OIT Programs. e. Control strategies. f. SCADA architecture block diagram. g. PLC and HMI configuration standards. h. Reports, Data Warehouse Tables, Existing databases, and SCADA Feasibility Report. Site Visits: a. Conduct site visits as needed to perform condition assessment of the existing SCADA system including but not limited to the following: 1) Plant walk-through and review of PLC/RIO/RTU panels and OIT cabinets in the field. 2) Observe HMI system performance in operation. 3) Review functionality and operation of existing reporting system. 4) Retrieve latest SCADA application files directly from the existing PLCs, OITs, and SCADA servers. b. Conduct site visits as needed to perform I/O loop inspections as follows: 1) Field 1/0 loop inspections shall be performed for all existing PLC systems in Category A. Refer to Attachment 6 — Existing WTP PLC Systems Table for details of PLC systems in this category. 2) I/O inspection shall be performed on the entire loop, from the field device all the way to SCADA HMI (and the local OIT, if applicable), to identify and document existing condition of respective field devices and instrumentation, field wiring connections, PLC hardware, and PLC/SCADA/OIT application programming. 3) Loop inspections and tests shall be performed using City -approved forms and checklists. 4) Comply with the requirements in Section 40 61 23 — SCADA System Field Assessment, Testing, and Start -Up. Perform offline review of existing PLC and HMI applications and develop as -installed Functional Control Narrative (FCN) documents for PLC systems in Category A. Refer to Attachment 6 — Existing WTP PLC Systems Table for details of PLC systems in this category. 4. Coordination meetings and workshops: a. System Assessment Coordination Workshops. b. As -Installed Functional Control Narrative Coordination Workshops. C. Comply with the requirements in Article 1.9 — Coordination Meetings and Workshops. C. Deliverables: 1. PLC Loop Test Forms, One (1) per Category A PLC system. 2. PLC Loop Test Reports, One (1) per Category A PLC system (Draft, and Final). CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 1— AD4 4061 13 SCADA SYSTEM GENERAL PROVISIONS Page 8 of 32 3. As -Installed FCNs, One (1) per Category A PLC system or a group of related PLC systems belonging to a single process (Draft, and Final). 4. System Condition Assessment Technical Reports, One (1) for all WTPs, and one (1) for Overall SCADA system (Draft, and Final). 5. Comply with the requirements in Article 1.10, Submittals and Section 40 6123 — SCADA System Field Assessment, Testing, and Start -Up. D. The City's Responsibilities: 1. Provide latest available SCADA system O&M documentation, software application files, databases, configuration standards, and report templates, as requested by the Contractor. 2. Coordinate access for the Contractor to perform site visits and the ability to retrieve running PLC/OIT/HMI applications to ensure working with latest files. 3. During the As -Installed Control Narrative Workshops, provide access to existing SCADA HMI workstation(s) and assist in demonstration of documented control descriptions on the live SCADA system to verify critical control loops. 4. Review Contractor's submittals and attend the required coordination workshops. E. Coordination: 1. Coordinate site visits, meetings, and workshops with the City in compliance with requirements in Article 1.9 — Coordination Meetings and Workshops, and Section 40 6123 — SCADA System Field Assessment, Testing, and Start -Up. 2. Coordinate with Facility Operators Contractor to retrieve existing PLC and HMI applications directly from PLCs and SCADA servers to ensure working with the latest files. Use these programs to develop as -installed control narratives. 3. Coordinate with Water Operations and Water IT to access the existing SCADA HMI workstation(s) and verify the documented control descriptions on the live SCADA system during the As -Installed Control Narrative Workshops. 1.4 DESIGN A. General: 1. Project services in this phase include design of Water Department SCADA system architecture, specification of SCADA system components, and development of new control narrative documents. B. Key Activities: 1. Develop SCADA system architecture in coordination with Water IT as follows: a. Physical Network block diagram showing all components residing on the network inclusive of ports, labels/designations, and connections for all media types. IP addresses shall not be shown but shall be prepared in a separate table for use in coordination with Water IT. b. Virtual Network traffic flow diagram prepared to show in detail expected data transfers to provide viewer an accurate view of the intended flow of data/traffic across the network between all connected system databases and inputs and outputs to those databases. Data warehouse connections, custom connections, tablet, and alarm notification traffic flow shall be shown. 2. Prepare specifications for all SCADA system hardware and software components procured by the City under this Contract. Refer to Attachment 7 — SCADA Assets Responsibility Matrix for details. CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 1— AD4 4061 13 SCADA SYSTEM GENERAL PROVISIONS Page 9 of 32 3. Develop new FCN documents for all PLC systems in Category A. Refer to Attachment 6 — Existing WTP PLC Systems Table for details. 4. Coordination meetings and workshops: a. SCADA System Architecture and Component Selection Coordination Workshops b. SCADA System and Database Interface/Integration Coordination Workshops C. Functional Control Narrative Development Coordination Workshops d. Comply with the requirements in Article 1.8 Coordination Meetings and Workshops C. Deliverables: 1. SCADA system physical and virtual network design (30%, 60%, 100%, and Final) 2. SCADA system component specifications (30%, 60%, 100%, and Final) 3. FCNs, One (1) per Category A PLC system or process unit (Preliminary, Draft, and Final) 4. Comply with the requirements in Article 1.9 Submittals. D. The City's Responsibilities: 1. Review Contractor's submittals and attend the required coordination workshops. 2. Upon completion of SCADA system architecture design, review and provide written approval for the Contractor's Final architecture and component specifications. The Water IT, City, and/or City's representative can then proceed with procurement. 3. Provide the Contractor with requested information and supervised access to the existing data warehouse, as required. E. Coordination: 1. Coordinate preparation of SCADA system network diagrams and component specifications with Water IT and the respective equipment manufacturers. 2. Coordinate with Water IT to review existing databases and data warehouse configuration, and incorporate into the data flow architecture design, as required. 3. Coordinate workshops with the City in compliance with requirements in Article I A.A — Coordination Meetings and Workshops. 4. Upon receiving the City's written approval for the Final SCADA system architecture and component specifications, proceed with the procurement of third -party SCADA communication software and any other SCADA software identified in the Design phase as necessary to make the SCADA system functional, as specified in this contract and in accordance with Attachment 1 — PLC and HMI Configuration Standards. 1.5 PROGRAMMING AND CONFIGURATION A. General: 1. Project services in this phase include creation of new and/or upgraded PLC, OIT, HMI, and report applications for all Water Treatment Plants (WTPs) and the Centralized SCADA system. Refer to Section 40 68 63 — SCADA System Programming and Configuration for detailed scope. B. Key Activities: 1. Recreate existing SCADA HMI applications for all WTPs in Ignition to meet the standards in Attachment 1 — PLC and HMI Configuration Standards. 2. Upgrade programs for existing WTP PLCs as required to integrate with the new Ignition HMI system as follows: CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 1— AD4 4061 13 SCADA SYSTEM GENERAL PROVISIONS Page 10 of 32 a. Recreate programs for newer PLC systems in North Holly, South Holly, West Side, and Rolling Hills WTPs to meet standards in Attachment 1 — PLC and HMI Configuration Standards. b. Integrate all PLC systems in Eagle Mountain WTP as well as select older and/or vendor -packaged PLC systems in North Holly, South Holly, West Side, and Rolling Hills WTPs with the new Ignition HMI system. C. Refer to Attachment 6 — Existing WTP PLC Systems Table for details of PLCs. 3. Upgrade applications for WTP OIT units as follows: a. Update applications for existing OIT units as required to interface with the upgraded PLC programs. b. Refer to Attachment 6 — Existing WTP PLC Systems Table for details of OITs. 4. Create HMI applications for new Industrial Panel Mounted Touchscreen Computers (IPCs) furnished by the City in Ignition to meet the standards in Attachment 1 — PLC and HMI Configuration Standards. Refer to Attachment 7 — SCADA Assets Responsibility Matrix for details of IPCs. 5. Create local plant operational reports in Ignition. 6. Create Centralized SCADA HMI applications, business and central operational reports in Ignition. 7. Configure WTPs and Centralized SCADA local Historians, Pass -Through Historian, and Central SCADA Historian. 8. Configure Centralized SCADA alarm notifications and tablet interface. 9. Coordination meetings and workshops: a. SCADA HMI Configuration and PLC Programming Coordination Workshops b. Local Plant Operational Report Development Coordination Workshops c. Centralized SCADA Business Reports Development Coordination Workshops d. Comply with the requirements in Article 1.8 Coordination Meetings and Workshops C. Deliverables: 1. SCADA HMI Graphics Submittals (Preliminary, Draft, and Final), grouped by PLC system. 2. PLC Configuration Submittals (Preliminary, Draft, and Final). 3. Alarm Management Submittals. 4. Historian Configuration Submittals, (Local Plant, Pass -Through, and Central Historians). 5. Report Configuration Submittals (Local Plant Operational, Tablet Data Entry, and Centralized SCADA Reports). 6. Comply with the requirements in Article 1.9 Submittals. D. The City's Responsibilities: 1. Review Contractor's submittals and attend the required coordination workshops. 2. Provide the Contractor with access to Data Warehouse tables for other production databases. 3. Provide information required for the Contractor to setup the custom connection interfaces required for LIMB and Ovation databases. E. Coordination: 1. Control narratives shall be approved by the City in Design phase prior to the start of PLC software development. 1.6 FACTORY ACCEPTANCE TESTING A. General: CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 1— AD4 4061 13 SCADA SYSTEM GENERAL PROVISIONS Page 11 of 32 1. Project services in this phase include performing unwitnessed and witnessed factory testing of all new and/or upgraded PLC, OIT, HMI, and report applications for all Water Treatment Plants (WTPs) and the Centralized SCADA system. Refer to Section 40 6121 — SCADA System Factory Acceptance Testing for detailed scope. B. Key Activities: 1. Unwitnessed Factory Tests (UFTs) and Witnessed Factory Tests (WFTs) a. UFTs and WFTs shall be performed for all WTPs and the Centralized SCADA system. b. The factory testing of each WTP shall include its respective integration with Centralized SCADA. Each WTP UFT and WFT shall include but not be limited to plant HMI, PLC, and OIT applications, local Historian and operational reports, the respective Centralized SCADA HMI screens, alarm notifications, and data flow and replication with Central Historian. c. The Centralized SCADA UFT and WFT shall include but not be limited to central HMI application and alarm notification incorporating all WTPs, business and central operational reports, and tablet interface. d. All UFTs and WFTs shall utilize the respective WTP and Centralized SCADA hardware and software assets furnished for the project, either via remote access from the Contractor's facility or by performing the tests on site. C. Deliverables: 1. UFT and WFT Plans, One (1) per WTP and one (1) for Centralized SCADA. 2. UFT and WFT Reports, One (1) per WTP and one (1) for Centralized SCADA. 3. Comply with the requirements in Article 1.10, Submittals. D. The City's Responsibilities: 1. Review Contractor's UFT and WFT plans and reports. 2. Attend the required WFTs. 3. The new SCADA hardware and software assets for Centralized SCADA and respective WTP(s) are to be made ready and available to the Contractor for factory acceptance testing no less than thirty (30) days prior to the scheduled start of the first UFT. 4. Arrange secure remote access for the Contractor to the new SCADA hardware and software assets for Centralized SCADA and respective WTP(s) from their facility, if necessary, no less than thirty (30) days prior to the scheduled start of the first UFT. E. Coordination: 1. Notify the City no less than ninety (90) days prior to the planned start of the first UFT/WFT and thirty (30) days prior to the planned start of each factory acceptance testing thereafter. 2. Coordinate with the City to install and configure all SCADA and PLC software and applications, including all required communication software, for Centralized SCADA and respective WTP(s) no less than thirty (30) days prior to the scheduled start of each factory test. 3. Coordinate with the City to verify the configuration of new SCADA system hardware and software assets for Centralized SCADA and respective WTP(s), and remote access connection (if necessary), no less than thirty (30) days prior to the scheduled start of each factory test. CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 1— AD4 4061 13 SCADA SYSTEM GENERAL PROVISIONS Page 12 of 32 4. Coordinate with the City to verify communications and data transmission between the respective servers, workstations, and test PLC system(s) as well as configuration of all software inclusive of virtual environment, Ignition and all 3rd part software. 5. UFT and WFT Plans shall be submitted and approved no less than thirty (30) days prior to the scheduled start of respective tests. 6. Contractor shall receive approval from the City on all required SCADA system application submittals no less than thirty (30) days prior to the scheduled start of first UFT of a given facility. 7. Contractor shall complete UFT and submit test reports no less than 30 days prior to the scheduled start of the associated WFT. 1.7 CUTOVER, FIELD TESTING, AND START-UP A. General: 1. Project services in this phase include planning and performing SCADA system replacements at all Water Treatment Plants (WTPs) and the Centralized SCADA system. Refer to Section 40 61 23 — SCADA System Field Assessment, Testing, and Startup and this section for detailed scope. B. Key Activities: 1. Cutover planning 2. Cutover, system field testing and start-up a. Perform one (1) cutover per WTP and one (1) for the Centralized SCADA system. b. Each WTP cutover shall include the cutover, field testing and start-up of all PLC systems in the plant and integration into Centralized SCADA. New and existing WTP SCADA systems shall be operated in parallel from the cutover of the first PLC system through cutover of the last PLC in each plant. As each PLC system is cut over from the existing to the new SCADA system, the associated data will be activated on the new plant HMI, local Historian, and local operational reports. The associated HMI screens, alarms notifications, and Historian data shall also be tested and activated on the Centralized SCADA system one PLC system at a time. C. As part of each PLC system cutover, the respective historical data tags between Legacy and new Central SQL Historians in the data warehouse shall be linked to allow query of older SCADA data from the new SCADA system and to maintain the functionality of City's existing business reports and applications, and central operational reports that require access to latest logged SCADA data points. The City will reconfigure the existing business/central reports and applications to interface with the new Central SQL database for the respective SCADA information. d. The Centralized SCADA system cutover shall include testing and start-up of the central HMI application and alarm notifications with all WTPs integrated, the new Ignition business and central operational reports, and associated tablet interface. 3. Operational Availability Demonstration (OAD) a. Perform one (1) OAD per WTP and one (1) for the Centralized SCADA system b. Each OAD shall require 30 consecutive days of normal operation of the replacement SCADA system without any significant failures and/or interruptions to receive approval otherwise the OAD shall restart. 4. Coordination meetings and workshops: a. SCADA System Cutover Planning Coordination Workshops b. SCADA Architecture and Database Interface/Integration Readiness Workshops CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 1— AD4 4061 13 SCADA SYSTEM GENERAL PROVISIONS Page 13 of 32 Comply with the requirements in Article 1.9 — Coordination Meetings and Workshops C. Deliverables: 1. SCADA System Cutover Plans, One (1) per WTP and one (1) for Centralized SCADA (Preliminary, Draft, and Final) 2. Loop Test Plans, One (1) per WTP PLC system 3. Loop Test Reports, One (1) per WTP PLC system 4. System Field Testing and Start-up Plans, One (1) per WTP PLC system and one (1) for Centralized SCADA 5. System Field Testing and Start-up Reports, One (1) per WTP PLC system and one (1) for Centralized SCADA 6. OAD Period Letters, one (1) per WTP and one (1) for Centralized SCADA 7. OAD SCADA System Malfunction/Repair Form, one (1) per WTP and one (1) for Centralized SCADA 8. Comply with the requirements in Article 1.10 —Submittals. D. The City's Responsibilities: 1. Review Contractor's submittals and attend required coordination workshops. 2. Supply the Ignition software and all associated modules, as well as all V party SCADA software listed in Attachment 7 — SCADA Assets Responsibility Matrix, to the Contractor. 3. Install and configure all SCADA system computers and networking equipment hardware, and the associated software furnished by the City under this Contract no less than sixty (60) days prior to the scheduled start of cutover and field activities by the Contractor. 4. Reconfigure the existing business/central reports and applications to interface with the new Central SQL database for the respective SCADA information. 5. Operate the replacement SCADA system during OAD and promptly report any encountered issues to the Contractor. E. Coordination: 1. As part of cutover planning, the Contractor shall coordinate with the City and develop a construction sequence, cutover schedule, shutdown durations and requirements, and incorporate into the overall project schedule. Contractor is responsible for coordinating all shutdown schedules and shutdown durations with other contractors of ongoing contracts and with the City. 2. Coordinate with Facility Operators for scheduled shutdowns and proper operation of existing and new systems during these shutdowns. Prior to placing in service, coordinate and verify with Facility Operators that the upgraded SCADA and/or PLC systems are functioning as intended. 3. Coordinate with Facility Operators and facilitate manual operation of the process and/or equipment effected by a scheduled shutdown. 4. WTP cutover and field testing activities shall be scheduled no less than hundred -eighty (180) days after achievement of Milestone 1, approval of Final SCADA System Architecture design and component specifications. 5. WTP cutover and field testing activities shall be scheduled no less than thirty (30) days after Witness Factory Testing for all PLC systems associated with that plant has been completed and approved. 6. WTP cutover and field testing activities shall be scheduled no less than thirty (30) days after the associated Final cutover plan for that plant has been approved. CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 1— AD4 4061 13 SCADA SYSTEM GENERAL PROVISIONS Page 14 of 32 7. The Contractor shall submit an OAD Period Letter for each OAD to the City indicating the start date, period, and proposed end date of the OAD. The start date shall be signed by all applicable parties indicating commencement of the OAD. 8. Coordinate with the City to address any reported system failures during OAD. 9. Coordinate workshops with the City in compliance with requirements in Article 1.4.A, Coordination Meetings and Workshops. 10. On completion of a specific Operational Availability Demonstration (OAD), provide a submittal documenting alarm metrics and provide an as -built alarm database. 11. Three months after the completed OAD of each WTP, provide an Alarm Audit submittal comparing current metrics against benchmarking. Provide narrative and recommendations to the City for continued optimization of Alarm Management. 12. Coordinate with the Water IT for all required interface with the existing data warehouse. 1.8 SYSTEM MAINTENANCE, FINAL ACCEPTANCE, AND WARRANTY A. System Maintenance: 1. Provide limited maintenance services as described in Section 00 14 16 — Coordination with City's Operations. B. Final Acceptance: 1. Provide necessary closeout and punch list activities and submit all necessary documentation to meet Final Acceptance as defined in Division 0 and Division 1. C. Warranty: 1. Meet all warranty requirements as defined in Section 0178 36 — Warranties. 1.9 REFERENCES A. Design of SCADA system shall meet the following Standards: 1. ISA-18.2: Management of Alarm Systems for the Process Industries 2. ISA-99/IEC 62443: Industrial Automation and Control Systems Security 3. ISA-101: Human -Machine Interfaces for Process Automation Systems 4. IEC 61131: Programmable Controllers 5. NIST SP 800-82: Guide to Industrial Control Systems (ICS) Security 6. AWWA G430: Security Practices for Operation and Management 7. AWWA J100: Risk and Resilience Management of Water and Wastewater Systems 8. IEEE 1686: Standard for Substation Intelligent Electronic Devices (IEDs) Cyber Security Capabilities 9. ANSI/AWWA G100: Water Treatment Plant Operation and Management 10. EPA's Water Security initiatives and guidelines for the security of water systems. 1.10 QUALITY ASSURANCE A. Contractor shall utilize approved system and software engineers who have been factory trained and certified on the respective software packages, to perform all programming functions, develop control strategies, create graphic displays, customize applications, document all work, and coordinate the software interface. They shall be intimately familiar with the details of this project, water and wastewater treatment facility instrumentation and control in general, high performance CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 1— AD4 4061 13 SCADA SYSTEM GENERAL PROVISIONS Page 15 of 32 graphics development and the project goals and requirements. The Contractor shall comply with restrictions on substitutions as noted in Section 00 21 15 — Instruction to Offerors. 1.11 COORDINATION MEETINGS AND WORKSHOPS A. General: 1. Schedule conferences, meetings and workshops as described in this section. 2. All meetings and workshops shall be held at the location directed by City, unless otherwise noted. The City's designated location could vary based on the meeting agenda. 3. Contractor shall prepare and provide an agenda for each meeting or workshop specified in this section no less than two (2) weeks prior to the scheduled meeting date, unless otherwise noted, for review and comment by City. Contractor shall identify meeting location in agenda. 4. Required Attendees include Contractor's staff who are responsible for SCADA system design, programming, and configuration, City's staff determined by the City. 5. Contractor is responsible for preparing the minutes of the meetings or workshops that describe topics discussed, conclusions maid, and action items along with responsible party. Contractor shall submit each workshop minutes to the City for review and approval prior to distributing it to the attendees. B. Familiarization and Preliminary Assessment Phase Coordination Workshops: 1. A minimum of six (6) System Assessment Coordination Workshops, one per WTP and one for Centralized SCADA, shall be conducted by the Contractor. If additional Workshops are required, they shall be scheduled and conducted at no additional cost to the City. 2. A minimum of twenty (20) As -Installed Functional Control Narrative Coordination Workshops shall be conducted by the Contractor. If additional Workshops are required, they shall be scheduled and conducted at no additional cost to the City. 3. Contractor shall account for a minimum of three (3) hours for each workshop, not including travel time. 4. The purpose of these workshops will be to review, verify, and coordinate the Contractor's findings from the field inspections and assessments, and the documented as -installed control narratives. 5. As -Installed Control Narrative Workshops shall include verification of the documented control descriptions on the live SCADA system for the critical control loops as identified by the City. Contractor shall arrange access to the existing SCADA HMI workstation(s) through coordination with Water Operations and Water IT for operation and verification of the identified control scenarios during the workshops. C. Design Workshops: SCADA System Architecture and Component Selection: 1. Design services shall be coordinated with the City through coordination meetings and workshops conducted in accordance with the requirements described in Section 01 14 16 Coordination with City's Operations and this section. 2. A minimum of six (6) SCADA Architecture, Database Configuration, and Network Configuration Coordination Design Workshops shall be conducted by the Contractor. Four of the Workshops are to review Design deliverables. The remaining two can be used for topics for all WTPs as necessary by the Contractor to facilitate progression of the design. If additional Workshops are required, they shall be scheduled and conducted at no additional cost to the City. The workshops shall include, but not limited to, the following: a. Design Deliverable Workshops: CITY OF FORT WORTH SCADA System Replacement 103086 March 21, 2024 ATTACHMENT 1— AD4 4061 13 SCADA SYSTEM GENERAL PROVISIONS Page 16 of 32 1) Provide a workshop to review the 30%, 60%, 100% and Final Architecture Design Deliverables. b. Other Workshop Topics: 1) Review the IP Address scheme for SCADA System. 2) Security standards and policies required for SCADA System. 3) Internet service and high bandwidth communication lines coordination. 4) Cellular Services/connectivity for Tablets. 5) Networked drive requirements. 6) Backup Storage Server access, policies, folder structure, and capacity. 7) Domain control and initial settings of SCADA and Historian servers and workstations. 8) Logical network segmentation and segregation. 9) Review the SCADA network and routing protocols. 10) Details related to NTP time server time and connections. 11) Remote alarm monitoring and notification 12) Traffic flow for all data, routing of all data, sizing of databases. 13) Migration of existing data into the new data historians. 14) Test bench setup c. Contractor shall account for a minimum of two (2) hours for each workshop, not including travel time. d. The purpose of these workshops will be to review and coordinate physical/logical SCADA system architecture, security of the SCADA System, and hardware/software component selection with Water IT. D. Design Workshops: Functional Control Narrative (FCN) Development Coordination Workshops: 1. A minimum of fifteen (15) Functional Control Narrative Development Coordination Workshops shall by conducted by the Contractor, three per WTP for Preliminary, Draft and Final FCN submissions. If additional Workshops are required, they shall be scheduled and conducted at no additional cost to the City. 2. The purpose of these workshops is to review, verify, and coordinate the Contractor's development of FCNs and configuration of PLC function blocks to ensure they meet the requirements outlined in Attachment 1 — PLC and HMI Configuration Standards. 3. Contractor shall account for a minimum of three (3) hours for each workshop, not including travel time. E. SCADA HMI Configuration and PLC Programming Coordination Workshops: 1. A minimum of thirty-six (36) HMI Configuration and PLC Programming Coordination Workshops shall be conducted by the Contractor. If additional Workshops are required, they shall be scheduled and conducted at no additional cost to the City. 2. Contractor shall account for a minimum of three (3) hours for each workshop, not including travel time. 3. The purpose of these workshops is to review, verify, and coordinate SCADA HMI configuration and PLC programming meets the requirements outlined in Attachment 1 PLC and HMI Configuration Standards, and to exchange programming information related to HMI Graphic and PLC Logic development. 4. Workshops shall include live demonstration of the HMI system to provide an interactive experience. F. Local Plant Operational Report Development Workshops: CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 1— AD4 4061 13 SCADA SYSTEM GENERAL PROVISIONS Page 17 of 32 1. A minimum of two (2) Report Development Workshops shall be conducted by the Contractor for each of the five (5) Water Treatment Plants, total of ten (10) workshops. If additional Workshops are required, they shall be scheduled and conducted at no additional cost to the City. 2. Contractor shall account for a minimum of two (2) hours for the workshop, not including travel time. 3. The purpose of these workshops shall be to coordinate and develop report templates that meet the regulatory agencies format and data field requirements and the standard reports configured to print for day-to-day operational needs of the five water treatment plants. Include in the workshop discussion of required data points, scan time of each point, buffering requirements, and calculations. G. Centralized SCADA Business Reports Development Coordination Workshops: 1. A minimum of eighteen (18) coordination workshops shall be conducted as follows. If additional Workshops are required, they shall be scheduled and conducted at no additional cost to the City. a. Ten (10) Workshops (5 design, 5 mockup demonstrations), to review and confirm data/sources, tagging, use of templates, look/feel for the Reports using data from Centralized SCADA and the existing data warehouse. Provide mockup demonstrations. b. Four (4) Workshops (2 design, 2 mockup) to review requirements, and reports/dashboard related to custom interfaces (LIMS, Ovation) c. Two (2) Workshops to review remote alarm monitoring, and notification. d. Two (2) Workshops to review use of Tablets, data entry and provision for backfill of data on communication loss. 2. Contractor shall account for a minimum of two (2) hours for each workshop, not including travel time. 3. The purpose of these workshops shall be to coordinate and develop report templates that meet the regulatory agencies format and data field requirements and the standard reports configured to print for day-to-day operational needs of the five water treatment plants. Include in the workshop discussion of required data points, scan time of each point, buffering requirements, and calculations. H. Cutover Planning Coordination Workshops 1. A minimum of three (3) Cutover Planning Coordination Workshops shall be conducted by the Contractor for each of the five (5) Water Treatment Plants, and a minimum of five (5) for the overall system, for a total of twenty (20) workshops. If additional Workshops are required, they shall be scheduled and conducted at no additional cost to the City. 2. Contractor shall account for a minimum of two (2) hours for each workshop, not including travel time. 3. The purpose of these Workshops shall be to coordinate all requirements for WTP SCADA system cutovers, and to review and confirm cutover plans with the City to ensure the continuity and reliability of critical WTP processes and operations are maintained during the respective SCADA system cutovers. I. SCADA Architecture and Database Interface/Integration Readiness Workshops: 1. A minimum of six (6) SCADA Architecture and Database Interface/Integration Coordination Workshops, one per WTP and one for Centralized SCADA, shall be conducted by the Contractor. If additional Workshops are required, they shall be scheduled and conducted at no additional cost to the City. CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 1— AD4 4061 13 SCADA SYSTEM GENERAL PROVISIONS Page 18 of 32 2. Contractor shall account for a minimum of two (2) hours for each workshop, not including travel time. 3. The workshops shall be scheduled after the Cutover Plans have been prepared but in advance of architecture and/or data interface implementation at a given facility or for Centralized SCADA, and shall include, but not limited to, confirmation and review that all network equipment, software, database work, historian work has or will achieve a state of readiness to allow implementation of the Cutover Plan. 1.12 SUBMITTALS A. General: 1. Contractor shall be responsible for all submittals specified herein. Refer to Section 01 33 00 — Submittal Procedures, for general submittal requirements. 2. Shop drawings shall demonstrate that the equipment and services to be furnished comply with the provisions specified in this contract and shall provide a complete record of the equipment as manufactured and delivered. 3. Submittals shall be complete, giving equipment specifications, features, details of connections, wiring, ranges, installation requirements, and specific dimensions. Submittals consisting of only general sales literature shall not be acceptable. 4. Provide all required submittals for mobilization as indicated in Division 0 and 1. B. Project Plan and Project Schedule Submittal: 1. Contractor shall submit, within 30 calendar days after Notice to Proceed, the Project Plan and detailed Project Schedule. 2. Project Plan: The Project Plan shall, as a minimum, contain the following: a. Overview: Summary overview of Contractor's understanding of project scope of work, existing conditions assessment, 60%, 90% and 100% design activities, and proposed control system work at each water treatment plant and the Centralized SCADA system. b. Personnel Information: Project personnel and organization including the System Contractor's project manager, project engineer field representative, local service representative, and similar personnel for Supplier. Indicate addresses of personnel not based at Contractor's and Supplier's office nearest to the Site. Include resumes of each key individual and specify in writing their commitment to this project. C. Meeting Agenda Information: Preliminary meeting agenda for Project Kickoff Meeting as specified in this section. d. Work Approach: Flow chart showing steps to be taken in preparing and coordinating SCADA System design and construction submittals. e. Shop Drawing Information: 1) A list of expected SCADA System submittals to be provided under this Contract. List shall include submittal descriptions and Specification reference numbers at minimum. 2) Sample of each type of process control submittal required by the Contract Documents. These may be submittals prepared for other projects. At a minimum include samples of panel fabrication drawings, loop, I/O wiring diagrams. 3) Flow chart showing steps to be taken in preparing and coordinating SCADA System submittals f. Preliminary Hardware and Software Information: Preliminary PLC software, OIT software, and PLC hardware submittal information, including version numbers, solely to determine compliance with the requirements of this contract. Review and approval CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 1— AD4 4061 13 SCADA SYSTEM GENERAL PROVISIONS Page 19 of 32 of software and hardware systems as part of this Project Plan stage shall not relieve the Contractor of responsibility for meeting all the function and performance requirements of the system as specified herein. 3. Project Schedule: a. Project schedule shall be prepared in accordance with the requirements of Section 0132 16 — Progress Schedule. b. The project schedule shall illustrate all major project milestones including the following: 1) Project kickoff meeting and subsequent site visits to coordinate mobilization. 2) Field loop inspections, prepare inspection report, and review with City for all applicable PLC systems. 3) Develop as -installed control narratives, and review with City for all applicable PLC systems. 4) Current condition assessment, prepare current assessment report, and review with City for each water treatment plant and the overall SCADA system. 5) Design and develop 30%, 60%, and 100% design documents and design documents review meeting with City. 6) Develop and submit Final design documents prior to release for procurement by the City. 7) Schedule for all subsequent submittals. Include in the time allotment the time required for Contractor submittal preparation, City's review time, and a minimum of two complete review cycles. 8) Proposed dates for all project coordination meetings and workshops as specified in this section. 9) Hardware purchasing, fabrication, and assembly by the City (following completion of related design by Contractor). 10) Milestone(s) showing when City should make required SCADA software and hardware components for each water treatment plant ready for the Contractor. 11) Schedule for each water treatment plant SCADA system cutover and testing. Testing schedule shall include submittal and approval of cutover plans and test procedures prior to commencement of field activities. 12) Schedule for system startups and all required field tests and operational availability demonstrations at each water treatment plant and Centralized SCADA system. 13) Schedule for all training including submittal and approval of O&M manuals, factory training, and site -specific training. C. Familiarization and Preliminary Assessment Submittals: 1. Existing Field Input/Output (1/0) Inspection Forms: a. 1/0 Status Sign -Off Forms shall be used to organize and track an existing PLC system's field inspection. b. Submit separate Input/Output Status Sign -Off Form for each PLC system. C. The form shall include a table based on the existing PLC 1/0 list. The table shall include the following columns at minimum: 1) PLC Name 2) Signal Tag 3) Description 4) Range or active state when event or alarm state is reversed 5) Drawing Reference 6) Signal Type CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 1— AD4 4061 13 SCADA SYSTEM GENERAL PROVISIONS Page 20 of 32 7) Rack No. 8) Slot No. 9) Channel No. 10) Instrument Alarm Setpoint 11) Calibration, Configuration, and Wiring Complete (signoff area) with Date 12) 10 Testing from the field to the OIT (signoff area) with Date, as applicable 13) 10 Testing from the field to the HMI (signoff area) with Date 14) IO Testing from the OIT to the field (signoff area) with Date, as applicable 15) 10 Testing from the HMI to the field (signoff area) with Date 16) Notes d. Submit PO Test Results Submittal for each test performed. Submittal shall include a record copy of the test results. 2. As -Installed Functional Control Narratives: a. As -installed functional control narrative documents shall be submitted in two stages, Draft, and Final. b. The format of the documents shall comply with Attachment 8 — Sample Functional Control Narrative (FCN) Template. C. Draft submittals shall incorporate the results of the field 1/0 inspections and shall be submitted at minimum three (3) weeks prior to the start of As -Installed Control Narrative Coordination Workshops for review with the City during the workshops. All modes of operation currently coded and currently used shall be identified in the documents. d. Final documents shall be submitted after all As -Installed Control Narrative Coordination Workshops have been completed. e. All review comments and markups on the Draft submittal that are returned to the Contractor, and feedback received during the coordination workshops, shall be fully addressed and incorporated into the narratives prior to submitting the Final submittals. The results from the live verification of the identified critical control loops during the workshops shall also be incorporated into the Final narratives. System Condition Assessment Technical Reports: a. Contractor shall submit Condition Assessment Technical Reports, One (1) per WTP, and one (1) for Centralized SCADA. b. Reports shall include description of existing SCADA system conditions resulting from review of available information and documentation, field inspections and assessments, on -site meetings, and coordination workshops. D. SCADA System Architecture and Component Specifications Submittals: 1. SCADA system architecture design and component specifications shall be submitted in four stages, 30%, 60%, 100%, and Final. 2. Develop the SCADA system architecture and design specifications for all system hardware and software components in accordance with Article 1.2 — SCADA System Architecture Description and Attachment 7 — SCADA Assets Responsibility Matrix. 3. System architecture and component selection shall be closely coordinated with the City through SCADA System Architecture and Component Selection Coordination Workshops and SCADA Architecture and Database Interface/Integration Coordination Workshops. 4. SCADA system design specifications shall include make and model/part number information for all hardware and software components. 5. When the design reaches 30% level, Contractor shall submit 30% design package to City for City's review. Contractor shall conduct a review workshop with City and go over the 30% CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 1— AD4 4061 13 SCADA SYSTEM GENERAL PROVISIONS Page 21 of 32 design in detail and receive City's review comments. City's review comments shall be incorporated into the design prior to submitting 60% design documents for City's review. When the design reaches 60% level, Contractor shall submit 60% design package to City for City's review. Contractor shall conduct a review workshop with City and go over the 60% design in detail and receive City's review comments. City's review comments shall be incorporated into the design prior to submitting 100% design documents for City's review. When each water treatment plant design reaches 100% level, Contractor shall submit 100% design package to City for City's review. The 100% design review package for each shall include final SCADA system architecture design and final SCADA hardware and software data sheets or specifications, Bill of materials with manufacturer names and model numbers of all SCADA system hardware and software components to be procured by the City. Contractor shall conduct a review meeting with City and go over the 100% design in detail and receive City's review comments. The Contractor shall incorporate the City's review comments prior to submitting the Final design documents for written approval by the City. Water IT will then proceed with procurement. E. Functional Control Narrative Submittals: 1. Control narrative documents shall be submitted in three stages, Preliminary, Draft, and Final. 2. One control narrative shall be submitted for each PLC system, or a group of related PLC systems belonging to a single process. The new FCNs shall incorporate the validated control descriptions in Final As -Installed Control Narratives as no changes to the existing control logic will be made under this Contract. 3. The format of the documents shall comply with Attachment 8 — Sample Functional Control Narrative (FCN) Template. 4. FCNs shall be developed in accordance with Attachment 1 — PLC and HMI Configuration Standards. 5. Preliminary submittals shall be provided to the City no less than four (4) weeks prior to the start of Control Narrative Development Coordination Workshops. 6. All review comments and markups on the Preliminary submittal that are returned to the Contractor, and feedback received during the coordination workshops, shall be fully addressed and incorporated into the control narratives prior to submitting the Draft submittals. 7. As part of the Draft submittal, the Contractor shall provide PLC function blocks developed for the project in accordance with Attachment 1 — PLC and HMI Configuration Standards for City's review and approval. 8. Final FCN documents and configured PLC function blocks shall be submitted upon completion of all Control Narrative Development Coordination Workshops. The Contractor shall fully address and incorporate all review comments and markups on the Draft submittal, as well as feedback received from the City during the coordination workshops, before submitting the Final submittals. 9. The Final submittal must be reviewed and approved by the City prior to the start of PLC software development by the Contractor. F. HMI Graphics Submittals: 1. Submit separate submittal packages as specified below. 2. A group of sample HMI graphics that is representative of the overall project shall be submitted for review and approval by the City. The sample HMI graphic package shall be CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 1— AD4 4061 13 SCADA SYSTEM GENERAL PROVISIONS Page 22 of 32 submitted in three stages, Preliminary, Draft, and Final. The Draft submissions shall be accomplished through live demonstrations of the actual graphics. 3. For each WTP, and grouped by PLC panel or unit process, provide: a. Preliminary (30%), Draft (60%), and Final (100%) graphics submittals. The Final Graphics will be submitted for approval prior to conducting Factory Tests. b. Submittals may be grouped into multiple submittals to facilitate review and reduce size of individual submittals. 4. WTP Preliminary (30%) HMI Graphics Submittals: a. Preliminary HMI Graphic Submittal packages shall be submitted prior to HMI graphics coordination workshop. b. Submit all proposed HMI graphics for the WTP. Provide one graphic per I V x 17" page and size graphic to fit. Provide color graphics. C. Submit a complete HMI Database for the WTP. d. The HMI graphics shall meet the standards provided in Attachment 1 — PLC and HMI Configuration Standards. The submittal shall include the following: 1) Sample HMI screen(s) as template(s) for screen layout. Include one template for each type of screen provided. Include the following templates at minimum: a) Process Overview screen b) Main Menu screen(s) c) Process Display screens d) Trend screen e) Alarm summary screen f) Login/security screen g) Equipment control and setpoint entry Pop-up screens h) Screens displaying analog values grouped per processes i) SCADA communication network display screen showing communication status 2) Complete list of proposed HMI screens. Include screen name and brief description on contents. Identify facility where screen will be used. More than one location may be identified for a given screen. 3) Proposed HMI screen navigation hierarchy for each location. 5. WTP Draft (60%) HMI Graphics Submittal and Demo: a. The Draft HMI Graphics Submittal shall be accomplished through a live demo of the actual graphics for each WTP connected to test PLC(s) furnished by the Contractor, which shall be programmed with the respective upgraded and/or existing PLC logic. For Category A PLCs, the HMI graphics demo will be utilized to test and verify the PLC function blocks configured by the Contractor in the Design phase. b. Acceptance of Preliminary HMI Graphics Submittal shall be required prior to conducting the Draft HMI Graphics demonstration. All review comments and markups on the Preliminary HMI Graphic Submittal that are returned to the Contractor shall be fully addressed and incorporated into the HMI Graphics prior to conducting the Draft HMI Graphics demonstration. C. Each graphic display and process layout will be subject to modification from Contractor's submitted format and layout within limits of software package used for development. Contractor is required to implement such modifications in accordance with City's written comments on the submittal. Expect 20% rework from Contractor's submitted format, layout and symbology used. 6. WTP Final (100%) HMI Graphics Submittal: CITY OF FORT WORTH SCADA System Replacement 103086 March 21, 2024 ATTACHMENT 1— AD4 4061 13 SCADA SYSTEM GENERAL PROVISIONS Page 23 of 32 a. A Final HMI Graphics Submittal shall be submitted as a separate package for each WTP. b. Acceptance of Draft HMI Graphics Submittal shall be required prior to submission of the Final HMI Graphics Submittal. All review comments and markups on the Draft HMI Graphics that are returned to the Contractor shall be fully addressed and incorporated into the HMI Graphics prior to submitting the Final HMI Graphics Submittal. C. Submit HMI final graphics for each facility. Provide one graphic per I V x 17" page and size graphic to fit. Provide color graphics. d. The Final HMI Graphics submittal must be reviewed and approved by the City prior to the Factory Acceptance Tests. However, the City's staff witnessing the test may still have comments during the Factory Acceptance Tests that did not arise in the three review submissions. These comments shall be incorporated and documented with the submitted Factory Test Report at no additional cost to the City. G. PLC Configuration Submittals: 1. Submit, for each WTP, and where upgraded PLC programs are required: a. Preliminary (30%), Detailed (60%) and Final (100%) PLC submittals. The Final PLC code will be submitted prior to conducting Factory Tests. b. Submittals may be grouped into multiple submittals to facilitate review and reduce size of individual submittals. 2. Preliminary (30%) PLC Submittal a. Submit one PLC program in its native electronic language as a sample for verifying PLC programs developed by the Contractor meet the standards provided in Attachment 1 — PLC and HMI Configuration Standards. Program shall have PLC system name and associated facility name. b. The sample PLC program submittal review will be limited to the verification of the program meeting City's standards. Control strategies and other monitoring and control functions will not be part of review and will be verified during Factory Acceptance Tests. C. Submit the following as part of the sample program submittal: 1) List of deviations from the existing control strategies and/or functions. 2) List of requests for additional information from the City, if applicable. 3) Format, logic, protocol, and procedures for data transmission and communications with input/output modules and peripheral devices, including Ethernet/IP. 4) Input/output (I/O) point listing with 1/0 module cross-reference identification for all PLC and Remote Input Output racks. 3. Draft (60%) PLC Submittal: a. The Draft PLC Submittal shall demonstrate development of the code to support the associated Functional Control Narrative. 4. Final (100%) PLC Submittal: a. A Final PLC Submittal shall be submitted as a separate package for each WTP. b. The final PLC program shall be submitted with the 100% HMI Submittal and demonstrate readiness for Factory Testing. C. The Final (100%) PLC submittal shall be approved at the Factory Acceptance Tests. 5. The approval of Final (100%) PLC code will be part of the respective WTP Factory Acceptance Tests. The City's staff witnessing the Factory Acceptance Test may have comments during the Factory Acceptance Test that did not arise in the review submissions. CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 1— AD4 4061 13 SCADA SYSTEM GENERAL PROVISIONS Page 24 of 32 These comments shall be incorporated and documented with the submitted Factory Test Report at no additional cost to the City. H. Alarm Management Submittals: 1. Alarm Database Submittals: a. Provide a separate submittal for each WTP. b. Provide table of contents. C. List of requests for additional information, if applicable. d. List of all alarms. For each alarm, include as a minimum the tag name, description as it will appear on the alarm summary screen, priority, normal and alarm state, reset requirement, alarm group, alarm sound, shelving, flood, remote notification, escalation, setpoint, dead band, as applicable. 2. The Alarm List shall be used as a working document and shall be updated as needed. Provide a major revision number and note every time it is re -submitted and minor revision when it only includes minor corrections. 3. Alarm Benchmarking: On completion of a specific Operational Availability Demonstration (OAD), provide a submittal documenting alarm metrics and provide an as -built alarm database. 4. Alarm Rationalization: Three months after the completed OAD, provide an Alarm Audit submittal comparing current metrics against benchmarking. Provide narrative and recommendations to Owner for continued optimization of Alarm Management. See Section 40 68 83 — SCADA System Programming and Configuration, Article — 3.13 for additional details. I. Historian Configuration Submittals: 1. Provide a separate submittal for each Historian server. 2. Provide table of contents. 3. Submit the following: a. List of requests for additional information, if applicable. b. Proposed list of all database points for Historical archiving. Provide a separate list for each Historian. Database shall include the previous tag name and the new tag name for each point. C. Online and offline capabilities for software programming and diagnostics. 4. The final approved Historical Data List for the given facility shall be submitted and must be reviewed by the City prior to the start of the Operational Availability Demonstration (OAD) for the Historian, Report, and Alarm Management Software. The City may have review comments during the review conducted prior to OAD. These comments shall be incorporated and documented with the final operations and maintenance information at no additional cost to the City. Local Plant Operational, Tablet Data Entry, and Centralized SCADA Report Configuration Submittals: 1. For each of the items listed above, group submittal packages by facility or type of report. Grouping shall be practical to allow for timely substantive review by the City. 2. Prior to commencing these submittals, provide a proposed list of submittals and groupings expected for this work for review and approval by the City. 3. Provide table of contents for each submittal. 4. Preliminary Report Configuration Submittals: a. Submit the following: CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 1— AD4 4061 13 SCADA SYSTEM GENERAL PROVISIONS Page 25 of 32 1) Complete list of Reports that is coordinated and established during design phase and in the report development workshop. Include a table of contents identifying specific reports included in each submittal. Submittals shall be grouped clearly. Include report name, facility name and brief description on contents. 2) For each Tablet Data Entry form, Centralized SCADA, or Local Plant Operational report, provide the following details: a. List of points/source database. b. Template in PDF and native form. c. Results from Workshops and associated Mockup Demonstrations. d. Connectivity information including data sampling, encryption, and other settings relative to the specific submitted form, or report. e. For the tablets, identify how the system will handle communication loss and backfill of data on resumption of communications. 3) List of requests for additional information, if applicable. 4) Detailed description of Report software configuration for each installed location. 5) Sample report for each type of report proposed. Sample reports shall be submitted in color, where applicable, on 8-1/2" x I I"page. Final Report Configuration Submittals: a. Acceptance of the Preliminary Configuration Submittal shall be required prior to submission of the Final Report Configuration Submittals. All review comments and markups on the Preliminary Report Configuration Submittal that are returned to the Contractor shall be fully addressed and incorporated into the Reports prior to submitting the Final Report Configuration Submittals. b. Provide a separate submittal for each approved grouping. C. Submit the following: 1) Complete list of Tablet Entry, Reports or Dashboards included. Include report name and brief description on contents. If a report is typical for another facility(s), identify the other facility it is also used. 2) Complete set of report or data entry templates for review. Report templates will not include data set values. Each report template shall be submitted in color, where applicable, on 8-1/2" x I I" page. 3) Complete set of reports with a sample data set to provide an example of a generated final report. 4) List of all linked database and historical tags used for each report. The Final Report Configuration submittals shall be submitted, reviewed, and approved prior to the start of OAD for the Historian, Report, and Alarm Management Software. The City may have review comments during the review conducted prior to OAD. These comments shall be incorporated and documented with the final operations and maintenance information at no additional cost to the City. K. Factory Testing Submittals: 1. Testing Plan Submittals: a. Submit separate test plans for each specified test phase. b. The Factory Test Plan shall be submitted and approved prior to scheduled start of factory test. Refer to Section 40 61 21— SCADA System Factory Acceptance Test, for time requirement. C. Test Plan shall include at minimum: 1) Information on equipment to be tested. 2) Proposed test dates. CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 1— AD4 4061 13 SCADA SYSTEM GENERAL PROVISIONS Page 26 of 32 3) Expected duration of test. 4) Location where factory test will be conducted. 5) List of required testing equipment. 6) Test procedure and signoff forms. d. Test procedure forms shall include at minimum: 1) Cover sheet with test summary. 2) Detailed descriptions for each test to be performed. Each test to be performed shall be described and a space provided after it for sign -off by the appropriate parties after its satisfactory completion. 3) Checklists to be used to control and document the required tests. Provide a check box for every step to be performed during the test. 4) Sign -off areas where applicable. 5) Area for additional notes. 6) Include "punch list" forms with the test procedures to document issues that arise during the testing. Punchlist forms, at a minimum, shall include an issues description field; a resolution description field; and a sign -off area for the appropriate parties. 2. Test Report Submittals: a. Within 14 days after completion of the factory test, submit the completed Test Report. b. The test report shall include a copy of the signed off test procedure forms. Testing shall not be considered complete until the signed test procedure forms have been submitted and favorably reviewed. Submittal of other test documentation, including "highlighted" wiring diagrams with technician notes, are not acceptable substitutes for the formal test documentation. L. Cutover Plan Submittals: 1. System cutover plans shall be submitted in three stages, Preliminary, Draft, and Final. 2. Submit one overall Cutover plan for all WTPs inclusive of Centralized SCADA, and one per WTP. 3. Preliminary plans shall include but not be limited to the following: a. Purpose and scope b. System overview C. Pre-cutover requirements 1) Risk assessment 2) Pre-cutover testing 3) Training 4) Communication Plan d. Cutover procedure 1) Step-by-step process 2) Roles and responsibilities 3) Shutdown durations and requirements 4) Timing and scheduling 5) Contingency plans e. Documentation and reporting 1) Cutover report 2) Lessons learned 4. Develop system cutover plans in close coordination with the City through Cutover Planning Coordination Workshops. CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 1— AD4 4061 13 SCADA SYSTEM GENERAL PROVISIONS Page 27 of 32 Preliminary cutover plans shall be provided to the City no less than four (4) weeks prior to the start of System Cutover Planning Coordination Workshops. All review comments and markups on the Preliminary submittals that are returned to the Contractor, and feedback received during the coordination workshops, shall be fully addressed and incorporated into the cutover plans prior to submitting the Draft submittals. Final overall and individual WTP cutover plans shall be submitted after all the Cutover Planning Coordination Workshops have been completed. All review comments and markups on the Draft submittal that are returned to the Contractor, and feedback received from the City during the coordination workshops, shall be fully addressed and incorporated prior to submitting the Final cutover plans. The Final overall and individual WTP cutover plan s must be reviewed and approved by the City prior to the start of field cutover and startup activities for the respective plant by the Contractor. M. Start-up and Field -Testing Submittals: 1. WTP PLC / OIT / IPC / HMI Sign -Off Forms: a. PLC I/O Status Sign -Off Forms shall be used to organize and track a system's inspection, adjustment, and calibration. b. Submit separate Input/Output Status Sign -Off Form for each system. C. The form shall include a table based on the project PLC 1/0 list. The table shall include the following columns at minimum: 1) PLC Name 2) Signal Tag 3) Description 4) Range or active state when event or alarm state is reversed 5) Drawing Reference 6) Signal Type 7) Rack No. 8) Slot No. 9) Channel No. 10) Instrument Alarm Setpoint 11) Calibration, Configuration, and Wiring Complete (signoff area) with Date 12) IO Testing from the field to the OIT (signoff area) with Date, as applicable 13) IO Testing from the field to the HMI (signoff area) with Date 14) IO Testing from the OIT to the field (signoff area) with Date, as applicable 15) IO Testing from the HMI to the field (signoff area) with Date 16) Notes 2. Submit Test Procedure Submittal for each control strategy to be tested, including but not limited to the following: a. For PLC Category A processes, confirm complete functionality of the PLC/HMI and/or OIT/IPC or portion of the process meeting the Functional Control Narratives developed. This includes but is not limited to the items below: b. Manual operation of the process and/or equipment. C. Automatic operation of the process and/or equipment. d. Mode operation of the process and/or equipment. e. Alarm notification and escalation f. Historian point confirmation and data validation g. Local plant report population and functionality h. Diagnostics for network or devices CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 1— AD4 4061 13 SCADA SYSTEM GENERAL PROVISIONS Page 28 of 32 i. Data entry / limits j. Security k. Procedures for testing safety interlocks. 1. Procedures for testing all related alarms. in. Associated Centralized SCADA HMI Screens. Submit Test Procedure Submittal for the Centralized SCADA System. a. Procedure shall include confirming complete functionality of the centralized SCADA and data/reporting platform, data traffic, latency metrics, remote alarm notification, tablet deployment/screen functionality/data entry. The procedure should include, but is not limited to, testing of the items below: b. Remote Alarm Notification. C. Centralized HMI Platform. d. Tablet functionality including screens, data entry, data backfill on communication loss. e. Data traffic and performance f. Data validation and database population g. Security h. Business and central operational reports N. Operational Availability Demonstration (OAD) Submittals: 1. For each OAD, submit an OAD Period Letter indicating the start date, period, and proposed end date of the OAD. The start date shall be signed by all applicable parties indicating commencement of the OAD. Leave space for: (1) Listing of corrective actions. In case of any failures encountered during the OAD, attach all malfunction/repair forms generated; (2) Signatures and attestation of the successful completion of the OAD. 2. Submit SCADA System Malfunction/Repair Reporting Form to be used for City's documentation of system failures, Contractor notifications, arrivals, and repair actions during the OAD. Format of the form shall be approved by the City prior to the start of the OAD. 3. Upon successful completion of an OAD, provide the Period Letter signed, as well as any Malfunction/Repair Reporting Forms related to corrective action and/or restart of the OAD. O. Training Plan Submittals: 1. Preliminary Training Plan Submittal: a. Prior to the preparation of the Final Training Plans, submit outlines of each training course including course objectives and target audience, resumes of instructors, prerequisite requirements for each class, and samples of handouts for review. b. Provide preliminary training plan as one complete submittal. Provide a table of contents. Provide a separate section for each course. C. Include tentative schedules for all classes for approval. Indicate times available that comply with the City's three shift schedule. d. For PLC Software Training Course at the Manufacturer's facility, provide facility's address, training course, and a minimum of three optional dates for City's selection. 2. Final Training Plan Submittal: a. Upon receipt of the City's comments on the preliminary training plan, submit the specific proposed training plan for each course. b. Submit each training plan under a separate submittal. C. The training plan shall include: 1) Definitions, objectives, and target audience of each course. 2) Schedule of training courses including dates, duration, and locations of each class. CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 1— AD4 4061 13 SCADA SYSTEM GENERAL PROVISIONS Page 29 of 32 3) Complete copy of all proposed handouts and training materials. Training information shall be logically arranged in a three-ring binder with all materials reduced to a maximum size of 11 inch by 17 inch, then folded to 8.5 inch by 11 inch for inclusion into the binder. 4) Reservation confirmation from manufacturer with names of City's staff and dates of training. P. Record Drawings and Final System Documentation: 1. Prior to submitting record drawings and final system documentation, provide a Table of Contents and Listing of the submittals intended and grouping of documentation to meet the Record Drawing and Final System Documentation requirements. Provide separate submittals for key project components. At minimum provide a submittal for each WTP, and other key system components. Each submittal should include where applicable: a. Finalized HMI documentation: mapping (HMI -PLC -Database), control narratives, conventions (tag naming, navigation, color, text), alarm list, historical data collection, frequency, method on data capture; averaging or raw, trending, scripting, templates, reports library and features. b. Finalized PLC documentation: Routines, interlocks, and function blocks descriptions. c. Finalized network and security documentation. d. User manuals for Operators, PLC programmers, and SCADA personnel. e. All factory, system testing, cutover and OAD documentation. 2. Submit in accordance with Section 01 78 39 — Project Record Documents, and Section 01 78 23 — Operations and Maintenance Data. 3. The Final System Documentation shall consist of operations and maintenance manuals as specified herein. 4. The operations and maintenance manuals shall, at a minimum, contain the following information in addition to that specified in Section 0178 23 — Operations and Maintenance Data: a. Instrument and Equipment Lists shall have the following: 1) The Equipment lists shall be developed and provided in Excel format. 2) Shall include manufacturer, model number, serial number, location, manufacturer phone number, local supplier name, local supplier phone number, completion year, replacement cost, and any other pertinent data. 3) Shall include cover page for each device, piece of equipment, and Original Equipment Manufacturer (OEM) software that lists, at a minimum, date, product name, manufacturer, model number, Location(s), and power required. Preferred format for the cover page is ISA S20, general data sheet; however, other formats will be acceptable provided they contain all required information. 4) Final vendor O&M documentation for each device, piece of equipment, or OEM software shall be either new documentation written specifically for this project or modified standard vendor documentation. All standard vendor documentation furnished shall have all portions that apply clearly indicated with arrows or circles. All portions that do not apply shall be neatly lined out or crossed out. Groups of pages that do not apply at all to the specific model supplied shall be removed. 5) For any component requiring dip switch settings or custom software configuration, that information shall be included along with the corresponding data sheets and O&M information. b. As -Built Drawings: As specified in Section 0178 39 — Project Record Documents, and the following: CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 1— AD4 4061 13 SCADA SYSTEM GENERAL PROVISIONS Page 30 of 32 1) Complete as -built drawings, including all drawings and diagrams submitted as part of the Submittal requirements described in this section. 2) As built documentation shall include information from submittals, as described in this section, updated to reflect the as -built system. Any errors in or modifications to the system resulting from the Factory and/or Functional Acceptance Tests shall be incorporated in the As -Built Drawings. 3) Provide electronic copies of drawings in native format as specified below. 4) As -Built Drawing submittal shall include a copy of the actual redlined drawings and other documents generated during factory test, field startup of the system(s). Electronic O&M and Final Project Files: In addition to the operations and maintenance submittal requirements specified elsewhere in the Contract Documents, provide an electronic version of all information contained in the O&M manual, along with any software backups of installation files, configuration files, and related items on electronic media. The electronic version shall be submitted on a portable hard drive furnished by Contractor. Submit one portable hard drive for each water treatment facility loaded with facility specific files. Label each hard drive with facility name and date of compilation. In addition to the above, submit the following: a. A portable hard drive loaded with all final electronic files to the City as a backup for all facilities. Portable hard drive shall be USB 3.0 and sized to accommodate all required electronic files as specified plus 20% spare storage capacity. Hard drive shall have 4TB of memory minimum and be formatted for Windows operating system. b. Electronic files shall be organized in a folder structure to permit ease of use. Provide "Read Me" file in root directory which documents portable hard drive contents, file structure, backup dates, and related information. C. Text files shall be supplied in both Microsoft Office format and Adobe Acrobat format. Adobe Acrobat files shall include bookmarks for all document sections. d. Electronic O&M Information: 1) Provide electronic files for all approved shop drawings and custom -developed manuals in this project including O&M and training manuals in accordance with Section 01 31 26 — Electronic Communication Protocols. 2) Provide back-up copies of files from each computer system. Back-up files shall be grouped and identified by computer name. File backups shall be date stamped for after Substantial Completion. 3) Provide original software license certificates and related information. The information provided shall include serial numbers, license agreements, User Registration Numbers, and related information. 4) Provide copies of all project related software installation files on electronic media. Software installation files shall include disc images of complete manufacturer software packages. Include a software list identifying all provided software installation files. The information provided on the list shall include, software name and manufacturer, software version, installed location(s), and related information. 5) Submit copies of programming and configuration files developed specifically for the Project in accordance with Section 01 78 23 Operations and Maintenance Data. Electronic submission of programming and configuration files shall be in native file format and Adobe Acrobat format. Electronic O&M and Final Project Files Local Backup: In addition to providing a portable hard drive with all electronic O&M and project related files, Contractor shall copy the entire contents of the submitted portable hard drive for each facility onto the storage location(s) as specified by the City. CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 1— AD4 4061 13 SCADA SYSTEM GENERAL PROVISIONS Page 31 of 32 7. Provide updated revised PLC and HMI Configuration Standards, with Revision Note dated and indicating these were provided with Final Project Documentation. PART 2 — PRODUCTS 2.1 THIRD -PARTY SOFTWARE A. Furnish any additional software required to complement the Ignition SCADA software furnished by the City in order to place in operation a fully functional SCADA system as specified in the Contract Documents. Coordinate with the City to transfer all licensing ownership to the City prior to field deployment. B. The software listed below has been identified necessary to support and provide the desired functionality for the SCADA platform. Any additional software deemed necessary during the Design phase to provide a fully functional system shall be provided. 1. SNMP Driver: Communication software for integration of UPS systems, and other SNMP- supported network devices, with Ignition. It shall be able to communicate with up to 50 devices at each WTP. Provide software and license for each WTP SCADA server, Centralized SCADA, and the Test Bench. Manufacturer shall be Kymera Systems or approved equal. 2. GE Driver: Communication software for integration of the existing GE 90-30, RX3i, and RX7i PLC systems with Ignition, as required. Provide software and license for Eagle Mountain WTP and Test Bench SCADA servers. Manufacturer shall be PTC Kepware or approved equal. PART 3 — EXECUTION (NOT USED) + + END OF SECTION + + CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 1— AD4 4061 13 SCADA SYSTEM GENERAL PROVISIONS Page 32 of 32 + +THIS PAGE INTENTIONALLY LEFT BLANK+ + CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 1- AD4 ADDENDUM NO. 5 Page 1 of 2 CITY OF FORT WORTH, TEXAS CONTRACT FOR THE CONSTRUCTION OF SCADA SYSTEM REPLACEMENT ADDENDUM NO. 5 This Addendum is part of the Contract Documents and modifies the Contractor for The Construction of SCADA System Replacement Document dated March 2024 for the above referenced project. This change affects the Document distributed on March 21, 2024 to prequalified Offerors. Acknowledge receipt of this Addendum in accordance with the requirements in Section 00 21 15 Instructions to Offerors Article 1.16 I. Failure to do so may result in the Proposal being deemed non- responsive. Overview and General Clarifications:. 1. This addendum provides the Pre -proposal Site Visit sign in sheets for May 1, 2024 and May 2, 2024. 2. This addendum provides the Pre -proposal Site Visit Outline/Schedule and Handout. 3. This addendum provides questions the City has received to date. ADDENDUM ITEMS (SPECIFICATION MODIFICATIONS & PROJECT CLARIFICATIONS): 1. ATTACHMENT 1— AD5 provides the Pre -proposal Site Visit sign in sheets for May 1, 2024 and May 2, 2024. 2. ATTACHMENT 2 — AD5 provides the Pre -proposal Site Visit Outline/Schedule and Handout. 3. The City has received the following questions: QUESTION 8: Are we able to obtain a sample PLC Program in Rockwell Logix Designer (ACD) and Schneider EcoStruxtures Control Expert (STA) leveraging the approach presented in the "FW PLC Standards Final 09_09_22.pdf'? This sample program will help us review the coding standards for Fort Worth. ANSWER 8: No, sample programs that use the new PLC standards are not available. ADDENDUM NO. 5 Page 2 of 2 ... . ROSSER R. STANDIFER 0............................;,4 92755ZCENSEP Arai. Aa: •��,a �� Rosser R. Standifer, PE Principal Engineer Arcadis Addendum No. 5 Issued by the City of Fort Worth Date: May 6, 2024 Alexander Pierce Project Manager City of Fort Worth END OF ADDENDUM No. 5 Sign -In Sheet — May 1, 2024 Name as A I y'+?��� Nan of &Iivxsm -ry SA \T0 d 1•rlL�l.✓1ZJ-L'� I h,J'L- I� 1 B 1�o.YZ.!s 6P`Q Organization e-,)C 0 C4-, C Q,j �_ F LI/ fIORT WORTH. City of Fort Worth Water Department The Construction of SCADA System Replacement City Project No. 103086 Pre -Proposal Site Visits Email T Signatur Cis A �vtti,ir c .. b4 /zg, L) Fo 2 12 T H L.y53 \p 6,0 rU2Tkrok 'A TEXAS. et)j SCADA System Replacement 103086 ATTACHMENT 1— AD5 Sign -In Sheet — May 1, 2024 Name L—v6— C-,1.,e "i tr- 3JACE 6ufl-k Organization 9 f"ORT WORTH,' City of Fort Worth Water Department The Construction of SCADA System Replacement City Project No. 103086 Pre -Proposal Site Visits Email Signat 11 +1 vt._, 4 �^t � 0, �. Vv �4 Cap v� tA:-1:-- (' �a,��— r SCADA System Replacement 103086 ATTACHMENT 1 — AD5 Sign -in Sheet — May 2, 2024 Name P7 IVA, L L Organization "Re vc r t— i -s A Ire V E vi 4; Ar ,krc_ej_1� FORT WORTH', City of Fort Worth Water Department The Construction of SCADA System Replacement City Project No. 103086 Pre -Proposal Site Visits Email -IY_cLv,4p d his . C e- CI ;L (;�) f'cl "j ILc 3DAt4 +(I C1, C, '46) r. 1- 4- k a 's - C , , ./ Z J 64L� Signat ;7 SCADA System Replacement 103086 ATTACHMENT I — AD5 Sign -In Sheet — May 2, 2024 Name Organization FORT WORTH', City of Fort Worth Water Department The Construction of SCADA System Replacement City Project No. 103086 Email Pre -Proposal Site Visits Signature Al l SCADA Sysiem Replacement 103086 ATTACHMENT 1 — AD5 Site Visit Schedule Agenda Day 1— 5/1/2024 • 9:00 o North Holly Training Room — 920 Fournier Street, Fort Worth, TX ■ Meeting • 10:00 o North Holly ■ Control Room ■ PLCs PLC Model OIT Process Category PLC 5 M580 MAGELIS FILTER A PLC 6 M580 UNKNOWN HIGH SERVICE PS A PLC 8 M580 UNKNOWN CHEMICAL FEED A PLC 15 QUANTUM N/A NH/SH OZONE B PLC 16 QUANTUM N/A NH/SH 03 PSU 1 B Others based on time Category A - Existing PLC program to be recreated to meet FWWD PLC/HMI Configuration Standards. Existing local OIT application(s) to be updated as required to maintain functionality with the upgraded PLC program. Category B - Existing PLC program to be integrated into the new HMI system with legacy code. Existing local OIT application(s) to remain unchanged. PLC 5 w+.�r� SCADA System Replacement 103086 ATTACHMENT 2 — AD5 Pl PLC 8 SCADA System Replacement 103086 ATTACHMENT 2 - AD5 PSU I 050NIA- 0 SCADA System Replacement 103086 ATTACHMENT 2 — AD5 • 11:30 o Lunch • 1:00 o SCADA Building (w/WIT) ■ Control Room ■ Server Room ■ Other • 2:00 o South Holly ■ Control Room ■ PLCs SCADA System Replacement 103086 ATTACHMENT 2 — AD5 PLC Model OIT PLC 1 M580 MAGELIS PMC1 M580 N/A UNMARKED QUANTUM N/A PLC 12/RTU 75 M580 N/A PLC 14 M580 N/A Others based on time • 3:30 o SCADA Building Conference Room ■ Daily wrap up meeting 0 4:00 o End of 15t Day Activities PLC1 Process Category FILTER A CHEMICAL A TEST OKC B (replaced with PLC 14) RECLAIM A HIGH SERVICE PS A SCADA System Replacement 103086 ATTACHMENT 2 — AD5 SCADA System Replacement 103086 ATTACHMENT 2 - AD5 I '4= ORN I FAA as 12 • 8:00 o Eagle Mountain — 6801 Bowman Roberts Rd., Fort Worth, TX ■ Meet in plant lobby ■ SCADA Room (w/WIT): ■ Control Room ■ PI -Cs PLC Model OIT Process Category PLC2A/2B GE RX7i N/A OZONE B PLC3 GE 90-70 N/A P1 - HEADWORKS B PLC4A/4B GE 90-70 N/A FILTERS 1-6 B PLC6 GE 90-70 N/A P1&2 - CHEMICAL B PLC 7 GE 90-70 N/A HIGH SERVICE PS B SCADA System Replacement 103086 ATTACHMENT 2 — AD5 PLC13A/13B I GE RX7i I N/A Others based on time FILTERS 16020 • 10:00 o Westside —12200 Old Weatherford Road, Aledo, TX ■ Meet in plant lobby ■ SCADA Room (w/WIT) ■ Control Room ■ PLCs PLC Model OIT Process PLC -CB AB 1756 N/A OZONE PLC-FLT-A/B AB 1756 PANELVIEW 1500 SAND FILTER SYS PLC-HS AB 1756 PANELVIEW 1000 HIGH SERVICE PS PLC-OZ-A/B AB 1756 N/A OZONE OZCP-01 AB 1756 N/A 03 GEN 1 PLC 8 AB 1756 N/A MEMBRANE SYS Others based on time • 11:30 o Lunch • 1:00 o Rolling Hills — 2500 SE Loop 820, Fort Worth, TX ■ Meet in plant lobby ■ SCADA Room (w/WIT) ■ Control Room ■ PLCs PLC Model OIT Process PLC 1 M580 N/A LAB PLC 2A-2B M580 MAGELIS FILTERS 1-10 PLC 7 M580 MAGELIS CL2/NH3 PLC 21 M580 N/A RECLAIM PLC 25 M580 N/A HIGH SERVICE PS PLC 12 QUANTUM N/A OZONE MCP Others based on time • 3:00 o Rolling Hills Training Room o Daily wrap up meeting • 4:00 o End of 2nd Day Activities 3 Category B A A B B B Category A A A A A B SCADA System Replacement 103086 ATTACHMENT 2 — AD5 ADDENDUM NO. 6 Page 1 of 6 CITY OF FORT WORTH, TEXAS CONTRACT FOR THE CONSTRUCTION OF SCADA SYSTEM REPLACEMENT ADDENDUM NO. 6 This Addendum is part of the Contract Documents and modifies the Contractor for The Construction of SCADA System Replacement Document dated March 2024 for the above referenced project. This change affects the Document distributed on March 21, 2024 to prequalified Offerors. Acknowledge receipt of this Addendum in accordance with the requirements in Section 00 21 15 Instructions to Offerors Article 1.16 I. Failure to do so may result in the Proposal being deemed non- responsive. Overview and General Clarifications: 1. This addendum provides questions the City has received to date via Bonfire and during the Pre -proposal Meeting on May 8, 2024. ADDENDUM ITEMS (SPECIFICATION MODIFICATIONS & PROJECT CLARIFICATIONS): 1. The City has received the following questions: QUESTION 9: How many hardwired I/O points are included within the project scope? ANSWER 9: The hardwired I/O counts for Category A PLC systems are shown below. South Holly Reclaim Recovery PLC Chemicals PLC Chlorine Building PLC Filtration PLC Caustic/Fluoride PLC Pump Station PLC North Holly Filtration System PLC Chemicals PLC Sodium/Hypo PLC Sedimentation PLC Caustic/Fluoride PLC Pump Station PLC Hard I/O Count Hard I/O Count 64 176 256 728 132 64 856 278 382 104 40 176 ADDENDUM NO. 6 Page 2 of 6 Rolling Hills Lab PLC Filtration System Wing 1 Filtration System Wing 2 Main Control Backwash PLC Reclaim Recovery PLC Backwash Tower PLC Raw Flow Control PLC Rapid Mix/Sedimentation PLC Chemicals PLC Chlorine/Ammonia PLC Pump Station 1 PLC Pump Station 2 PLC Westside Filtration System PLC Chemicals PLC Pump Station PLC QUESTION 10: Hard I/O Count Hard I/O Count 64 644 644 80 112 32 136 432 208 200 164 172 636 256 232 What scope of work is included in the project at the Village Creek plant? ANSWER 10: One Category B PLC located at Village Creek WWTP is connected to the FWWD Miser SCADA system (as shown on Attachment 6) for remote monitoring purposes. The associated HMI tag counts are as follows: Discrete: 3, Analog: 21 QUESTION 11: What is the control narrative requirements for Category A and Category B PLCs? ANSWER 11: Control narratives are required for Category A PLCs, but not for Category B PLCs. QUESTION 12: What is the requirement for on -site staff within the project scope? ANSWER 12: The Contractor shall be responsible to provide on -site staffing as necessary for all necessary activities to meet all project requirements. Note that as required by Section 40 61 13 and Section 40 61 21- in addition to I/O validation, field testing, cutovers, and other necessary field activities - UFTs and/or WFTs may also need to be conducted on site if testing on the City's computer systems furnished for the project is not feasible through remote access from the integrator's ADDENDUM NO. 6 Page 3 of 6 facility to the respective WTP(s). Assume that no SCADA system network/computer hardware procured by the City for the project shall leave the City. QUESTION 13: The contract documents state that a 72-hour period between PLC cutover at each plant is required. Is this a firm number that cannot be changed? ANSWER 13: See Item No. 3 of this addendum. Concurrent PLC cutovers at a single water treatment plant are allowed. However, once a PLC or PLC(s) has been cutover, a period of 72 hours (which can be reduced at the discretion of the City, or extended should issues arise) should be allotted to allow the plant to confirm successful operations. QUESTION 14: Will cutovers be allowed in low flow and/or high flow periods? ANSWER 14: The definition of shutdown has been clarified by Item No. 4 of this addendum. Cutover activities that do not constitute shutdowns are allowed during low flow and/or high flow, but approval outside of low flow periods must be granted by the City and coordinated by the City through the cutover plan process. The City reserves the right to not allow specific cutovers outside of low flow periods for whatever reason. QUESTION 15: Does the City have a preference on the first plant to begin work on? ANSWER 15: The City does not have a preference on the first plant to begin work on. QUESTION 16: Will the City allow the remaining plants after the first plant to be worked on and/or cutover in parallel? ANSWER 16: Concurrent SCADA system cutovers at more than one water treatment plant are not allowed, see Section 01 14 16-1.4.C. Within a single water treatment plant, the Contractor may propose grouping of PLCs for concurrent cutover or cutover one PLC at a time in conjunction with the Contractor's cutover planning. Cutover planning shall be coordinated with the City at the Workshops described in Section 40 61 13 and submitted for City approval in the Cutover Plan for each water treatment plant. Refer to Item No. 3 in this addendum for further details. QUESTION 17: Are we able to obtain an export of the Add On Instructions or Derived Function Blocks leveraging the approach presented in the "FW PLC Standards Final 09_09_22.pdf ". Also, are those "blocks" developed and ready for implementation by the integrator? ANSWER 17: Sample PLC programs, Function Blocks, and Add -On Instructions (AOIs) utilizing the approach outlined in Attachment 1 have not been completed. The successful offeror is expected to create these components as part of the Work. The Contractor is required to develop the PLC Function Blocks and AOIs in close coordination with the City through FCN submittals and workshops. ADDENDUM NO. 6 Page 4 of 6 This development shall take place during the design phase for each water treatment plant, prior to the commencement of PLC/HMI configuration work, as outlined in Section 40 61 13. QUESTION 18: Is it possible to use I V x 17" for items such as the schedule for readability? Section 00 21 15 restricts page size to 8.5" x 11". ANSWER 18: It is acceptable to use an 11" x 17" page to present detailed schedule information, see Item No. 2 of this addendum for modified page requirements. 2. In Section 00 2115 — Instructions to Offerors, delete the third sentence in Article 1.4 A. that reads "All pages must be 8.5"xI 1" with a minimum font size of 12." and replace it with the following sentences: "All pages, with the exception of the project schedule, shall be 8.5"xl 1" with a minimum font size of 12. The proposed schedule, if desired, may be presented on a single I V x 17" page." In Section 0114 16 - Coordination with City's Operations, delete Article 1.4 D. and replace with the following: "D. Unless otherwise approved in writing by the City, after a given PLC (or concurrent PLCs) is cutover to the new SCADA system, the Contractor shall not proceed to the next PLC (or concurrent PLCs) until the impacted unit processes, data collection, alarm notifications, and reports have operated successfully for at least 72 hours, or if the City otherwise confirms authorization to proceed. 4. In Section 0114 16 - Coordination with City's Operations, delete Article 1.5 A. 1. and replace with the following: "l. Terminology: A "shutdown" is an interruption or clear disruption to water production or treatment as a result of any part of the City's facility be it process or electrical equipment, or systems —being temporarily suspended or taken out of service to perform the Work." ADDENDUM NO. 6 Page 5 of 6 OF I*: •*� ROSSER• R. STANDIFER 92755 .�4� 'S C) Rosser R. Standifer, PE Principal Engineer Arcadis Addendum No. 6 Issued by the City of Fort Worth Date: May 15, 2024 Alexander Pierce Project Manager City of Fort Worth END OF ADDENDUM No. 6 ADDENDUM NO. 6 Page 6 of 6 ++THIS PAGE INTENTIONALLY LEFT BLANK++ ADDENDUM NO. 7 Pagel of 8 CITY OF FORT WORTH, TEXAS CONTRACT FOR THE CONSTRUCTION OF SCADA SYSTEM REPLACEMENT ADDENDUM NO. 7 This Addendum is part of the Contract Documents and modifies the Contractor for The Construction of SCADA System Replacement Document dated March 2024 for the above referenced project. This change affects the Document distributed on March 21, 2024 to prequalified Offerors. Acknowledge receipt of this Addendum in accordance with the requirements in Section 00 21 15 Instructions to Offerors Article 1.16 I. Failure to do so may result in the Proposal being deemed non- responsive. Overview and General Clarifications: 1. This addendum provides questions the City has received to date via Bonfire. 2. This addendum modifies Section 40 61 13 SCADA Systems General Provisions to provide clarification on software procurement. 3. This addendum extends the Proposal Due Date until June 6, 2024 by 1:30 PM CT. ADDENDUM ITEMS (SPECIFICATION MODIFICATIONS & PROJECT CLARIFICATIONS): 1. The City has received the following questions: QUESTION 19: Bonfire portal for this opportunity does not show any actions which allow proposals to be uploaded into the portal. I have looked at other City RFPs currently active and they show links for these uploads to occur. Can City verify links are currently available in this opportunity to permit file uploads? ANSWER 19: Links will be added to the Opportunity page to facilitate uploads. QUESTION 20: Can you provide clarity around the scope of each I/O loop check for Cat A PLCs. Is this from field instrument to local existing PLC/SCADA, then from local SCADA to top end SCADA, or from field instrument direct to top end SCADA? Can City provide more details on number and type (analog or discreet) I/O per PLC? Does loop check include verification of instrument calibration at each field instrument, or just data communication/change of state verification? We haven't been given the actual I/O count so it will be difficult to price the effort needed. (Ref 40 6123 3.1 EXISTING PLC LOOP TESTS) ANSWER 20: Existing Category A PLC I/O verifications are to be conducted from field devices, through to local PLC and OIT, and extending to the plant SCADA system. Total hardwired I/O counts for each Category A PLC has been provided in Addendum No.6. Offerors should be able to estimate the I/O types from the existing HMI screenshots in Attachment 4. The objective of these loop checks is to document current conditions related to field device operations, field ADDENDUM NO. 7 Page 2 of 8 wiring connections, PLC/OIT hardware functionality, and PLC/OIT/SCADA application programming. Documenting the existing field device operations includes confirmation of instrument analog output ranges, which can be accomplished through a single point comparison between the local instrument reading versus the OIT/HMI indication. Field instrument ranges as well as any issues identified in the existing programs during the loop checks shall be detailed in the As -Installed FCNs, which are to be prepared by the Contractor. See Section 40 61 23-3.1. QUESTION 21: Field verification of existing I/O loops will be documented per 40 6123 3.1.D. System checkout of upgraded PLC loops will be performed per 40 6123 3.2.A. Contractor is required to all problems encountered in the upgraded system checkout of 3.2. Is the City's plan to correct any malfunctioning loops identified in existing PLC loop checks prior to final loop checks after upgrade installation? (Ref 40 6123 3.1.1) and 3.2 A.1) ANSWER 21: Yes, the City will address any malfunctioning loops identified in the existing PLC loop checks prior to final checkout. That is the purpose of the field verification: to both document the system and identify any issues so they are known and can be resolved going into final loop checks. QUESTION 22: 3.2.D.1 states "Contractor along with City's electrician and/or maintenance staff shall test...." Is it the City's intent to provide dedicated electrical and/or maintenance staff for duration of loop tests for test support purposes? (Ref 40 6123 3.2.D.1) ANSWER 22: Yes, the City will provide staff. QUESTION 23: 40 6123 3.2.D.1 requires field verification of upgraded I/O loops. Please clarify if this is for Category A PLCs that were field checked for existing conditions prior to replacement, or for all PLCs (Category A and B). If for all PLCs, can City provide loop count and number and type of I/O per PLC for costing purposes. (Ref 40 6123 3.2.D.1) ANSWER 23: Field verification of I/O loops is for Category A only. For counts, see Addendum No.6. Offerors should be able to estimate the I/O types from the existing HMI screenshots in Attachment 4 QUESTION 24: Can the City define the number of reports to be migrated or created at each WTP, and at the top end SCADA? ANSWER 24: In addition to Sections 40 68 63 1. LF and G, see Table 40 68 13 C and Section 40 68 63 Sections 3.17 and 3.18 for additional details. QUESTION 25: Can the city define ? Alerts on SCADA screen? SMS/Email notifications? (Ref 01 11 13 F.3) ADDENDUM NO. 7 Page 3 of 8 ANSWER 25: See section 40 68 63-3.13 E. QUESTION 26: Remote access to FWWD SCADA. Will there be remote access to PLCs and HMIs? Can the city provide details for remote access? VPN Tunnel? Existing remote access setup and restrictions? (Ref 01 11 13 G.1.B.3) ANSWER 26: Remote access to any hardware (PLC, HMI, network) connected to the SCADA network will NOT be permitted. Remote connectivity to PLC, HMI and/or network hardware NOT connected to the SCADA network (for Factory Testing) will need to be reviewed with the City of Fort Worth Water Department's Water IT staff for security and feasibility on a case -by -case basis. The Contractor will be expected to provide on -site staff for all activities where remote access is not approved. For additional information see Addendum No.6, Item No. 1, response to QUESTION 12. QUESTION 27: "Cutover and testing. Site and centralized SCADA 30 days consecutive normal operation. How does the city handle scenarios out of vendor control such as PLC hardware failure, server hardware failure, SCADA software bug, Operating System patches/updates?" (Ref 01 11 13 H, I, J) ANSWER 27: Scenarios outside of vendor/Contractor control such as those noted will be addressed by the City or City representative and do not constitute failure or interruption of the OAD period. QUESTION 28: 72 hour PLC cutover - what is the approval process and how long would approval take before next PLC cutover can start? (Ref 01 11 13 H, I, J) ANSWER 28: See Addendum No. 6, Item No. 3. QUESTION 29: 01 11 13 1.6.E Design (Milestone 1) includes FCN Development. Other references to Milestone 1 only discuss completion of SCADA System Architecture Design as "constituting achievement of Milestone 1". Please clarify if all FCN Development for all 5 WTPs is a prerequisite for achieving Milestone 1 as well. It is conceivable that the design can be completed while field verification and development of FCNs is still being performed. (Ref 01 11 13 1.6.E) ANSWER 29: Completion of FCNs is NOT a prerequisite for achievement of Milestone 1. Only the approved SCADA System Architecture Design will constitute achievement of Milestone 1 (Ref 01 11 13 1.6 E.2.c.). "Milestone 1" in parentheses in the title of 01 11 13 1.6.E. is only to indicate that this milestone is part of the design activities and should not be misinterpreted as including all specified design work for the project. ADDENDUM NO. 7 Page 4 of 8 QUESTION 30: 01 11 13 1.6.F Programming and Configuration: Programming activity falls between Milestone 1 and Milestone 2 in the specification narrative. Please confirm Programming and Configuration is not dependent to any specific Milestones other than as this work relates to completing and achieving OAD at each respective WTP. (Ref 01 11 13 1.6.F) ANSWER 30: See prerequisites in Section 01 11 13-1.6 for sequence of project activities. For programming and configuration work in particular, refer to 01 11 13-1.6 F.l.b., 01 11 13-1.6 F.l.b., and 01 11 13-1.6 F.l.b. QUESTION 31: All meetings and workshops to be held at the location directed by City. Please confirm all workshops will be at a City facility and will not require Contractor to lease third -party space. (Ref 40 61 13 1.1 LA.2) ANSWER 31: Yes, all workshops will be at a City facility and will not require Contractor to lease third -party space. QUESTION 32: System cutovers are limited to Monday through Thursday. Since PLC cutovers are required to run for 72 hours, this limits cutover activity to one PLC per week, without prior approval from City. Will the City agree to modifying this to allow more frequent scheduling of PLC cutovers? (Ref 01 14 16 1.3.B.D) ANSWER 32: See Addendum No.6 which adds flexibility in this requirement. QUESTION 33: The specification states a job trailer is not required. Is there dedicated space available for programmers when they are onsite? (Ref 01 14 19 1.2 Par. B) ANSWER 33: Yes, no trailer is required. Should the City and Contractor agree that a trailer is required due to lack of City provided space on a site, the Contract Price will be modified by Change Order. QUESTION 34: Does City already have an RSA server in place? SCADA Assets Responsibility Matrix does not address if there is an existing server in place or if new one is needed for this project. (Ref SCADA Assets Responsibility Matrix) ANSWER 34: The Contractor shall be responsible for coordinating with Water IT regarding all requirements of the SCADA system security, including RSA, during coordination workshop(s) and submittal(s) as part of SCADA system architecture design (See 40 68 63-3.4). ADDENDUM NO. 7 Page 5 of 8 QUESTION 35: SCADA Assets Responsibility Matrix states Contractor is responsible for procuring SNMP Drivers. It is not clear what this requirement is or will be prior to system design or further knowledge of full software features. To meet this requirement, will the City accept an allowance for this driver? (Ref SCADA Assets Responsibility Matrix) ANSWER 35: The requirements for third -party SCADA software to be furnished by the Contractor (incl. SNMP drivers) are identified in 40 61 13-2.1, therefore the SNMP driver costs should be included in the Contractor's bid. QUESTION 36: SCADA Assets Responsibility Matrix states Contractor is responsible for procuring Misc SCADA Software for all servers. It is not clear what this requirement is or will be prior to system design or further knowledge of full software features. To meet this requirement, will the City accept an allowance for this driver? (Ref SCADA Assets Responsibility Matrix) ANSWER 36: A contingency allowance has already been allocated for procurement of any hardware or software assets not stipulated by the Contract Documents (Ref 0121 13 1.4.K.). Section 40 61 13-2.1 has been revised, see Item No.2 of this addendum. QUESTION 37: The Table indicates that the PLC's at the Eagle Mountain WTP are GE 90-70 or RX7i and are Category B PLC's — "Existing PLC program to be integrated into the new HMI system with legacy code. Existing local OIT application(s) to remain unchanged" Confirming that the contractor will be responsible for integrating the existing GE hardware into the new Ignition HMI System and that the existing PLC hardware will not be replaced during the planned duration of the project of 1440 days? ANSWER 37: The Contract Document content noted, specifically that Eagle Mountain PLCs are Category B PLCs, is correct. Portions of the Work associated with Eagle Mountain Category B PLCs are clearly noted. The Offeror's Proposal should include only the Work required by the Contract Documents. QUESTION 38: Are the contractor's staff who are responsible for programming required to be onsite for all Operations Availability Testing? ANSWER 38: No, but failure to repair a hardware or software problem within 12 hours from the time of notification of a system failure will result in termination of OAD (See 40 61 23-3.3). ADDENDUM NO. 7 Page 6 of 8 QUESTION 39: The contractor is responsible to furnish Location and Space for Testing, Field Service Specialists, Calibration & Test Equipment, Labor, & power, network connections, etc. Is it a requirement that the witnessed FAT be local to DFW? Will the contractor's staff be required to attend in person, or can they be remotely connected? ANSWER 39: Assume in -person testing for all FATS. Remote connectivity will need to be reviewed with WIT for security and feasibility. See Item No. 1 (Answer No. 12) in Addendum No.6. QUESTION 40: Will the City consider providing a 1-2 week time extension for proposal submittal? The current date is May 31 st. ANSWER 40: The Proposal Due Date will be extended 1-week, see Item No. 3 of this addendum. QUESTION 41: Given that we are pre -qualified to bid this job is it necessary to fill in the Qualification Statement Form? ANSWER 41: Yes, it is necessary to fill in the Qualification Statement Form. 2. In Section 40 6113 — SCADA Systems General Provisions, a. DELETE the first phrase in Article 2. LA: "Furnish any additional software required to complement the Ignition SCADA software furnished by the City in order to place in operation a fully functional SCADA system as specified in the Contract Documents." b. DELETE the 2nd phrase in Article 2.1.13: "Any additional software deemed necessary during the Design phase to provide a fully functional system shall be provided." Section 00 1115 Notice to Offerors, delete the last four events in the Schedule for Procurement and replace them with the following: " Proposal Due Date June 6, 2024 by 1:30 PM CT Evaluation of Proposals June 7, 2024 through June 19, 2024 Oral Clarifications (anticipated, if required) June 7, 2024 through June 12, 2024 Notice to Proceed (anticipated) August 7, 2024 " O F rE�N� .;*:. WS ROSSER R. STANDIFER p; ....92755 '....�.� ���'"`S �C�NSE�•G�r��"i Rosser R. Standifer, PE Principal Engineer Arcadis Date: May 22, 2024 Alexander Pierce Project Manager City of Fort Worth orth END OF ADDENDUM No. 7 ADDENDUM NO. 7 Page 7 of 8 ADDENDUM NO. 7 Page 8 of 8 ++THIS PAGE INTENTIONALLY LEFT BLANK++ ADDENDUM NO. 8 Page 1 of 2 CITY OF FORT WORTH, TEXAS CONTRACT FOR THE CONSTRUCTION OF SCADA SYSTEM REPLACEMENT ADDENDUM NO. 8 This Addendum is part of the Contract Documents and modifies the Contractor for The Construction of SCADA System Replacement Document dated March 2024 for the above referenced project. This change affects the Document distributed on March 21, 2024 to prequalified Offerors. Acknowledge receipt of this Addendum in accordance with the requirements in Section 00 21 15 Instructions to Offerors Article 1.16 I. Failure to do so may result in the Proposal being deemed non- responsive. Overview and General Clarifications: 1. This addendum clarifies the process for uploading proposal information via Bonfire, including a change requiring Offerors to submit the Cost Proposal separately. 2. To incorporate the above clarifications this addendum: ■ Replaces Section 00 11 15 Notice to Offerors. The Proposal Due Date has been modified to June 13, 2024 by 1:30 PM CT. ■ Makes minor modifications to Section 00 21 15 Instructions to Offerors, specifically Article 1.4 A. 6., Article 1.4 F., and Article 1.16 I. ■ Replaces Section 00 42 10 Proposal, including Exhibit A. ■ Replaces Section 00 45 42 Business Equity Goal CSP, modifying the Submittal of Required Documentation schedule and providing updated document links. ADDENDUM ITEMS (SPECIFICATION MODIFICATIONS & PROJECT CLARIFICATIONS): 1. In Section 00 1115 — Notice to Offerors, DELETE this section in its entirety and replace it with ATTACHMENT 1 — AD8. 2. Section 00 2115 Instructions to Offerors, make the following changes: a. Article 1.4 A. 6., add the following sentences to the end of the Article: " The Cost Proposal shall be provided as noted in Article 1.4 F. below. Do not include the cost information in the electronic (PDF) proposal file." b. Article 1.4 F., add subarticle "3.": "3. The information noted in Article 1.4 F. 1. and 2. shall be submitted by entering the cost of each Proposal Item No. into the Bonfire Procurement Portal as noted in Section 00 11 15 Notice to Offerors." ADDENDUM NO. 8 Page 2 of 2 c. Delete Article 1.16 I. in its entirety and replace it with: "I. The Proposal shall contain an acknowledgement of receipt of all addenda, by initialing next to each addendum received in the area provided in Section 00 42 10 Proposal. 3. In Section 00 42 10 — Proposal, DELETE this section in its entirety, including Exhibit A and replace it with ATTACHMENT 2 — AD8. 4. In Section 00 45 42 — Business Equity Goal CSP, DELETE this section in its entirety and replace it with ATTACHMENT 3 — AD8. VIP 100, :* ROSSER R. STANDIFER 92755 ..... �i i 1kkS/�• . Rosser R. Standifer, PE Principal Engineer Date: June 4, 2024 Alexander Pierce Project Manager City of Fort Worth END OF ADDENDUM No. 8 0011 15 NOTICE TO OFFERORS Page 1 of 6 SECTION 00 11 15 NOTICE TO OFFERORS PREQUALIFICATION FOR SUBMITTAL OF COMPETITIVE SEALED PROPOSALS PREOUALIFICATION Offerors intending to submit proposals must be Prequalified as an Offeror for this specific project by the City prior to receipt of the Contract Documents. Request for Prequalification for the SCADA System Replacement ("Project") will be received by the City of Fort Worth via the Procurement Portal at: https:Hfortworthtexas.bonfirehub.com/portal/?tab=oi)en0pportunities, under the respective Project opportunity page until 4:00 P.M. CST, Friday, April 12, 2024. DOCUMENT EXAMINATION AND PROCUREMENTS Prior to prequalification, the document sections noted in Section 00 21 13 — Prequalification Instructions will be available to all interested parties. The procedures and requirements for Prequalification are outlined in Section 00 21 13 — Prequalification Instructions. Additional information applicable to the subsequent submittal of Competitive Sealed Proposals (CSP) is included in Section 00 21 15 — Instructions to Offerors. The limited Contract Document content noted will be available electronically to interested parties via the Procurement Portal: htt_Ds://fortworthtexas.bonfirehub.com/_aortal/?tab=o_nenOD_Dortunities, under the respective Project. The full content of the Contract Documents will be available to all Prequalified Offerors following confirmation that the Offeror is prequalified and receipt of an executed (signed) copy of Section — 00 23 13 Non -Disclosure Agreement. The Contract Documents may be shared with and viewed by sub -contractors teamed with Prequalified Offerors and with suppliers as necessary to develop a Proposal subject to the provisions of the Non -Disclosure Agreement. The Contract Documents and all Addenda will be available electronically to Prequalified Offerors via the Procurement Portal: httl)s://fortworthtexas.bonfrehub.com/portal/?tab=ol)en0phortunities, under the respective Project. RECEIPT OF PROPOSALS Competitive Sealed Proposals (CSP) for the delegated design and construction of SCADA System Replacement ("Project") for the Water Department will be received by the City of Fort Worth. Proposals will be received from prequalified Offerors only via the Procurement Portal: https://fortworthtexas.bonfirehub.com/portal/?tab=olDen0pportunities. under the respective Project opportunity page until 1:30 PM CST, Thursday, June 13, 2024, as further described below. The CSP will be opened publicly and read aloud at 2:00 PM CST in the City Council Chambers. NOTE: Submittal of Business Equity Documents within 3 days of the opening of Proposals is required for ALL OFFERORS. CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 1— AD8 0011 15 NOTICE TO OFFERORS Page 2 of 6 Your submissions must be uploaded, finalized, and submitted prior to the Project's posted due date. The City strongly recommends allowing sufficient time to complete this process (ideally a week prior to the deadline) to begin the uploading process and to finalize your submission. Uploading large documents may take time, depending on the size of the file(s) and your Internet connection speed. The Bonfire portal can be accessed using Microsoft Edge, Google Chrome, or Mozilla Firefox. Javascript must be enabled. Browser cookies must be enabled. Electronic submission is subject to electronic interface latency, which can result in transmission delays. All proposers assume the risk of late transmission/ submission. The City shall not be held liable if an interested party is unable to submit a complete response before the published deadline due to transmission delays or any other technical issues or obstructions. The City strongly recommends allowing sufficient time to complete the submission process (ideally a week before the deadline) to begin the uploading process and to finalize your submission to give adequate time in the event an issue arises. All submissions must be submitted electronically prior to the close date and time under the respective Project/Solicitation via the Procurement Portal: httas://fortworthtexas.bonfirehub.com/aortal/?tab=oaen0aaortunities Offerors shall submit the electronic (PDF) file proposal file as instructed on the Procurement Portal. The Cost Proposal, in the form of a cost for each Proposal Item No., shall be entered into Procurement Portal as instructed under the respective project. Allowance Proposal Items shall be manually entered by the Offeror in the amounts noted in Section 00 42 10 Proposal Exhibit A. See additional information in Section 00 42 10 Article 6 Basis of Offer. Failure to submit all completed required information listed in the respective Solicitation will be grounds for rejection of a prequalification request or subsequent submitted proposal as non- responsive. No late proposals shall be accepted. Proposals delivered in any other manner than using the Bonfire Platform (Procurement Portal) will not be accepted or considered. If, upon being opened, a submission is unreadable to the degree that material conformance to the requirements of the procurement specifications cannot be ascertained, such submission will be rejected without liability to the City, unless the Offeror provides clear and convincing evidence (a) of the content of the submission as originally submitted and (b) that the unreadable condition of the Electronic Proposal was caused solely by error or malfunction of the Bonfire Platform (Procurement Portal). Failure to scan a clear or readable copy of a response into the system does not constitute and shall not be considered an error or malfunction of the Bonfire Platform (Procurement Portal). Offerors are encouraged to fully review each page of every document within their submission prior to submitting to ensure all documents are clear, legible, and complete. SUPPORT For technical questions, visit Bonfire's help forum at: htti3s://vendorsu-pi)ort.aobonfire.com/hc/en-us Contact the Bonfire support team at Support@GoBonfire.com or by calling 1-800-354-8010. To get started with Bonfire, watch this five-minute training video: Vendor Registration and Submission Video - Bonfire Vendor Support (gobonfire.com) CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 1— AD8 0011 15 NOTICE TO OFFERORS Page 3 of 6 EXISTING SYSTEM The existing Water Department Supervisory Control and Data Acquisition (SCADA) system is a proprietary HSQ Technologies system originally installed in 1987, upgraded in 1991, and since then has been developed and updated as the system has expanded. The SCADA system uses licensed 900 MHz radio frequencies to communicate with the remote distribution facilities. At the City's potable water treatment facilities - North Holly, South Holly, Rolling Hills, Westside, and Eagle Mountain Water Treatment Plants (WTPs) - three different Human Machine Interface (HMI) platforms are utilized. These include HSQ-Miser, GE Cimplicity, and Allen-Bradley FactoryTalk View SE, all of which report to a top -end and head -end HMI (HSQ-Miser). GENERAL DESCRIPTION OF WORK The project includes the design, configuration, testing, start-up, and maintenance through Final Acceptance of a complete SCADA replacement for the City's Water Department SCADA system, inclusive of but not limited to: upgraded SCADA systems at each of the five WTPs; a new centralized SCADA system; an upgraded SCADA system architecture to support the SCADA replacement; a new data architecture to support a comprehensive historical data collection and reporting interface and other work elements to support the SCADA upgrades. The City has procured a SCADA software, Ignition by Inductive Automation, which is to be used for the new HMI. This software will be provided by the City for use by the Contractor in implementation, installation, configuration, testing and start-up of the replacement system. The Contractor shall provide the following project services. Pre -Construction Services including Familiarization and Preliminary Assessment and Design Services for SCADA system architecture and component selection requirements. Construction Services to include Programming and Configuration; Factory Acceptance Testing; Cutover, Field Testing, and Start -Up; System Maintenance, Final Acceptance, and Warranty. EXPRESSION OF INTEREST To ensure awareness of any new information pertinent to this project, all interested parties should indicate their intent to request prequalification in the Procurement Portal by selecting "yes" under the "Intent to Bid" section the Procurement Portal: httas://fortworthtexas.bonfirehub.com/aortal/?tab=oaen0aaortunities, under the respective Project. Any and all subsequent Addenda will also be available to the Prequalified Offerors via the Procurement Portal. SCHEDULE FOR PROCUREMENT 1st Advertisement for CSP — Prequalification Requirements 2" d Advertisement for CSP Prequalification Requirements Virtual Prequalification Q&A Meeting Deadline for Prequalification Questions Deadline to Request Prequalification Offerors Notification of Prequalification Contract Document Release Date (anticipated) Pre -proposal 2 Day Site Visit (Primary) CITY OF FORT WORTH March 21, 2024 March 21, 2024 March 28, 2024 April 1, 2024, 2:00 PM CT April 5, 2024 April 12, 2024, 4:00 PM (Local Time) April 19, 2024 April 19, 2024 May 1 — May 2, 2024 SCADA System Replacement 103086 ATTACHMENT 1— AD8 0011 15 NOTICE TO OFFERORS Pre -proposal Conference — In Person and Virtual (anticipated) Pre -proposal 2 Day Site Visit (Backup)* Deadline for Questions (anticipated) Deadline for Responses via Addenda (anticipated) May 8, 2024, 8:30 - 9:30 AM CT May 8 — May 9, 2024 May 15, 2024, 5:00 PM CT May 22, 2024, 5:00 PM CT Page 4 of 6 Proposal Due Date June 13, 2024 by 1:30 PM CT Evaluation of Proposals (anticipated) June 14, 2024 through June 26, 2024 Oral Clarifications (anticipated, if required) June 20, 2024 through June 25, 2024 Notice to Proceed (anticipated) August 7, 2024 Notes: * Should adverse weather or unforeseen events at the Water Treatment Plants require rescheduling of the Pre -proposal 2 Day Site Visit from the Primary dates above, it is the City's intent to conduct the in conjunction with the Pre -Proposal Conference the following week on the dates indicated. PREOUALIFICATION O&A MEETING — Virtual Conference Prequalification Question and Answer (Q&A) will be held as described in Section 00 21 15 — Instructions to Offerors on the following anticipated date and time, via a web conferencing application only. DATE: April 1, 2024 TIME: 2:00 pm CT A link to the web conference will be available on the Procurement Portal under the respective Project. PRE -PROPOSAL SITE VISIT A pre -proposal site visit will be held as described in Section 00 21 15 — Instructions to Offerors on the following anticipated date and time. DATE: May 1 - May 2, 2024 TIME: 9:00 AM CT Each prequalified Offeror shall select up to two (2) attendees to attend the site visit. Each Offeror shall send the names of the attendees to the City's Project Manager via email, a minimum of 48- hours in advance of the site visit. Should adverse weather or unforeseen events at the Water Treatment Plants require rescheduling of the site visit, it is the City's intent to conduct the in conjunction with the Pre -Proposal Conference the following week as noted in the Schedule for Procurement. PRE -PROPOSAL CONFERENCE — In -person and Virtual Conference An in -person pre -proposal conference will be held as described in Section 00 21 15 Instructions to Offerors on the following anticipated date and time, as well as simultaneously via a web conferencing application. DATE: May 8, 2024 TIME: 8:30 - 9:30 AM CT CITY OF FORT WORTH March 21, 2024 SCADA System Replacement 103086 ATTACHMENT 1— AD8 0011 15 NOTICE TO OFFERORS Page 5 of 6 An invitation with a link to the web conferencing application will be distributed to Prequalified Offerors. The presentation along with any questions and answers provided at the Pre -proposal Conference will be issued as an Addendum. Prequalified Offerors may also ask questions or comments in accordance with Section — 00 21 15 Instructions to Offerors Article 1.9. Any questions received will be answered by Addenda. Addenda will be issued pursuant to Section 00 21 15 — Instructions to Offerors. CITY'S RIGHT TO ACCEPT OR REJECT PROPOSALS City reserves the right to waive irregularities and to accept or reject any or all proposals. AWARD The City will award a contract to the Offeror presenting the best value based on the evaluation criteria noted in Section 00 21 15 — Instruction to Offerors. After evaluating and notifying the Selected Offeror that offers the best value, the City will enter into negotiations with that Offeror. ADVERTISEMENT DATES 1 st Advertisement for Prequalification March 21, 2024 2nd Advertisement for Prequalification March 28, 2024 ++ END OF SECTION ++ CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 1— AD8 0011 15 NOTICE TO OFFERORS Page 6 of 6 ++THIS PAGE INTENTIONALLY LEFT BLANK++ CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 1- AD8 0042 10 PROPOSAL Page 1 of 8 SECTION 00 42 10 19k0l03Ym ARTICLE 1. ENTER INTO AGREEMENT The undersigned Offeror proposes and agrees, if this Competitive Sealed Proposal is accepted, to enter into an Agreement with City to perform and furnish all Work as specified or indicated in the Contract Documents for the Contract Price and within the Contract Time indicated in this Proposal and in accordance with the other terms and conditions of the Contract Documents with execution of the Agreement in the form included in the Section 00 52 45 — Agreement. ARTICLE 2. OFFEROR ACKNOWLEDGEMENTS AND CERTIFICATION 2.1 In submitting this Competitive Sealed Proposal, Offeror accepts all of the terms and conditions of the Section 00 11 15 — Notice to Offerors and Section 00 21 15 — Instructions to Offerors, including without limitation those dealing with the disposition of Section 00 43 15 — Proposal Surety (Bid Bond). 2.2 Offeror is aware of all costs to provide the required insurance, will do so pending contract award, and will provide a valid insurance certificate meeting all requirements within 14 days of notification of award. 2.3 Offeror certifies that this Competitive Sealed Proposal is genuine and not made in the interest of or on behalf of any undisclosed individual or entity and is not submitted in conformity with any collusive agreement or rules of any group, association, organization, or corporation directly or indirectly induced or solicited any other Offeror to submit a false or sham Proposal. 2.4 Offeror has not solicited or induced any individual or entity to refrain from submitting a Competitive Sealed Proposal. 2.5 Offeror has not engaged in corrupt, fraudulent, collusive, or coercive practices in competing for the Contract. For the purposes of this Paragraph: a. "Corrupt practice" means the offering, giving, receiving, or soliciting of anything of value likely to influence the action of a public official in the proposal process. b. "Fraudulent practice" means an intentional misrepresentation of facts made (a) to influence the proposal process to the detriment of City (b) to establish prices at artificial non-competitive levels, or (c) to deprive City of the benefits of free and open competition. c. "Collusive practice" means a scheme or arrangement between two or more Offerors, with or without the knowledge of City, a purpose of which is to establish prices at artificial, non-competitive levels. d. "Coercive practice" means harming or threatening to harm, directly or indirectly, persons or their property to influence their participation in the bidding process or affect the execution of the Contract. CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 2 — AD8 0042 10 PROPOSAL Page 2 of 8 2.6 Assurance of no Substitution — The Offeror in submitting the proposal provides written assurance that Key Personnel including key subcontractors, suppliers, materials, and equipment listed in Section 00 46 12 — Offeror Statement of Qualifications will be performing, furnishing or be used in the work and will not be substituted without written permission from the City. Offeror may include succession planning in the form of an alternate for key personnel should the staff listed become unavailable for reasons outside the control of the offeror. Written notification to the City is required prior to any staffing change. Substitution of alternate staff due to the Offerors ongoing for future commitments to other projects is prohibited. ARTICLE 3. PREOUALIFICATION The Offeror acknowledges that requirement to prequalify as an Offeror (Contractor) for the proposed work in accordance with procedures noted in Section 00 21 15 — Instructions to Offerors. ARTICLE 4. TIME OF COMPLETION 4.1 The Work shall be completed for Final Acceptance within a maximum of 1440 days after the date when the Contract Times commence to run as provided in Paragraph 2.02 of the General Conditions. The schedule provided by the Offeror shall meet the City's intent to have Project Components completed by no later than the Milestones noted in TABLE 00 42 10-A. The Milestone Days allowed for completion of each Project Component shall be measured as Contract Time commenced to run as provided in Paragraph 2.02 of the General Conditions. Prior to execution the Contract Time, noted as days shall be listed in Section 00 52 45 — Agreement, Article 4 as the lesser of the days above or days to Final Acceptance based on the Offerors submitted schedule. 4.2 Time is of the essence in completing the Work, the Offeror shall submit a schedule that completes the Work within the Milestone days noted in TABLE 00 42 10-A and the maximum days noted in Article 4.1 above. The Offeror shall note the number of days required to complete portions of the Work identified with each Milestone based on the submitted schedule. 4.3 Based on the submitted schedule the Offeror shall note the number of days required to complete the Work associated with each Milestone identified in Table 00 42 10-A in the column labelled "Offeror Milestone." Where the number of days noted by the Offeror under "Offeror Milestone" is less, the Work associated with that Milestone shall be Substantially Complete, as noted in Section 00 52 45 — Agreement Article 4, within the reduced duration provided by the Offeror under "Offeror Milestone". 4.4 Project Components are described in Article 4.6 of this Section. Work not described as part of a Project Component or not necessary to achieve the Project Component completion is not subject to a Milestone and shall be completed within the Project Time for Final Acceptance noted in Article 4.1 of this Section. While portions of the Work within each component may meet the requirements of Article 14.04 of the General Conditions for Partial Utilization by the City, a Milestone is not satisfied until all included Work has been completed. CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 2 — AD8 0042 10 PROPOSAL Page 3 of 8 4.5 Project Components that encompass Proposal Items that require the Contractor to continue maintenance of the included Work through Final Acceptance are considered to be complete when Contractor has completed all non -maintenance portions of the Work, including Punch List items provided by the City. TABLE 00 42 10-A SCHEDULE REQUIREMENTS PROJECT COMPONENT MILESTONE OFFEROR (days) MILESTONE (days) Milestone 1: SCADA System Architecture 220 Complete Milestone 2: OAD Complete — 1st WTP 550 Plant Complete Milestone 3: OADs Complete — All WTPs 1360 4.6 The Work associated with each Project Component is defined in Section 01 22 13 — Measurement & Payment, Article 1.4 — Proposal Items Basis of Payment. Project Component Milestones are listed below: a. Milestone 1— SCADA System Architecture Design Complete. This Milestone will be met when the SCADA System Architecture Design is Final and complete, providing the City information necessary to procure all necessary SCADA network components. b. Milestone 2 — OAD Complete —1 WTP Plant. This Milestone will be met when the Operational Availability Demonstration (OAD) has been completed for 1 plant. Achievement of this milestone indicates all necessary Work to be performed to perform the OAD for 1 WTP as outlined in Division 0, 1 and 40 is complete. c. Milestone 3 — OAD Complete — All WTP Plants. This Milestone will be met when the Operational Availability Demonstration (OAD) has been completed for all 5 plants. Achievement of this milestone indicates all necessary Work to be performed to perform all of the OADs for the WTPs as outlined in Division 0, 1 and 40 is complete. d. Final Acceptance — All Work. Final Acceptance will be met as defined in the General and Supplemental conditions, and when all preceding Milestones have been met and all remaining work has been completed. Major activities that are to be completed between Milestone 3 and Final Acceptance shall include the Operational Availability Demonstration (OAD) for the Centralized SCADA System. 4.7 Offeror accepts the provisions of the Agreement as to liquidated damages in the event of failure to complete the Work by achieving Final Acceptance within the Contract Time specified in the Agreement. CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 2 — AD8 0042 10 PROPOSAL Page 4 of 8 ARTICLE 5. ATTACHMENTS TO THIS OFFER 5.1 The Offeror acknowledges that the attachments listed below are required for the Proposal: a. Proposal Approach Narrative as noted in the Section 00 21 15 — Instructions to Offerors. b. This Proposal Form, Section 00 42 10 — Proposal. c. Exhibit A to this Proposal Form attached immediately following the words "END OF SECTION" and the following forms. d. Section 00 35 13 — Conflict of Interest Affidavit Statement, if necessary, CIQ or CIS forms shall be downloaded by the Offeror and provided directly to City Secretary. e. Section 00 46 12 — Offeror Statement of Qualification. f. Section 00 43 15 — Proposal Surety (Bid Bond) issued by a surety meeting the requirements of Paragraph 5.01 of the General Conditions. g. Section 00 43 37 — Vendor Compliance to State Law Non -Resident Offeror. h. Section 00 45 26 — Contractor Compliance with Worker's Compensation Law. i. MWBE Forms noted in Section 00 45 42 — Business Equity CSP, submittal is optional at time of submittal. j. Section 00 46 12 — Offeror Statement of Qualifications, in accordance with Section 00 21 15 — Instructions to Offerors. k. Evidence of Authority to Sign as noted in Article 7. ARTICLE 6. BASIS OF OFFER 6.1 Offeror acknowledges receipt of all addenda by initialing below in the applicable areas provided prior to the words END OF SECTION. 6.2 Offeror will complete the Work for the prices entered in the Bonfire Procurement Portal for each Proposal Item shown in Exhibit A of this Proposal Form. Where allowance items are presented with a BOLD fixed amount the Offeror shall enter the same cost that is noted in Exhibit A. The attached Exhibit A, immediately following the words END OF SECTION, shall be considered part of this Section. 6.3 It is understood and agreed by the Offeror in signing this proposal that the total price will be calculated by the Bonfire Procurement Portal, then verified by the Offeror and that any allowance amounts manually entered by the Offeror are subject modification by the City in the event that the amount entered is not identical to that shown in Exhibit A of this Proposal Form. Such corrections are limited to changing the allowance amount or amounts to that required by Exhibit A and updating the total amount to reflect any corrections. 6.4 It is understood and agreed by the Offeror in signing this proposal that following correction of the total amount, if necessary based on modification by the City under Article 6.3, the Offeror agrees that the individual amounts for each Proposal entered into the Bonfire Procurement Portal and the total amount shall be incorporated into Exhibit A by the City to complete the Cost Proposal. The total amount with any corrections shall also be incorporated into Article 3 of Section 00 52 45 Agreement as the Contract Price. CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 2 — AD8 0042 10 PROPOSAL Page 5 of 8 6.5 It is understood and agreed by the Offeror in signing this proposal that the Contract Price, as established above, is NOT subject to adjustment following completion of the preconstruction services described as part of the Work. 6.6 It is understood that and agreed by the Offeror in signing this proposal that an M/WBE goal identified in Section 00 45 42 — Business Equity Goal CSP has been set for the Project and agrees to comply with the intent of the City Business Equity Ordinance and provide the forms of documentation noted. ARTICLE 7. GENERAL INSTRUCTIONS 7.1 All blanks must be filled as unfilled blanks may result in the Proposal being disqualified. 7.2 The Proposal Form shall be signed in ink. Proposals by corporations shall be executed in the corporate name by the president or a vice-president or other corporate officer accompanied by evidence of authority to sign. The corporate seal shall be affixed. The corporate address and state of incorporation shall be shown below the signature. 7.3 Proposals by partnerships shall be executed in the partnership name and signed by a partner, whose title must appear under the signature accompanied by evidence of authority to sign. The official address of the partnership shall be shown below the signature. 7.4 Proposals by limited liability companies shall be executed in the name of the Prime Contractor by a member and accompanied by evidence of authority to sign for the entity. The state of formation of the Prime Contractor entity and the official address of the firm shall be shown. 7.5 Proposals by individuals shall show the Offeror's name and official address. 7.6 Proposals by joint ventures shall be executed by each joint venture in the manner indicated on the Proposal Form. The official address of the joint venture shall be shown. 7.7 All signatures shall include names either typed or printed in ink below the signature. 7.8 Erasures or alterations shall be initialed in ink by the person signing the Proposal Form. A price shall be indicated for each listed Proposal Form Item, Alternative Item, and Unit Price Item listed therein. 7.9 The Offeror shall state the prices for which the Offeror proposes to do the work contemplated or furnish materials required. All entries shall be legible. 7.10 A Proposal showing omissions, alterations, conditions, exceptions, or other qualifiers which modify the Proposal Form will be rejected. 7.11 Pricing shall represent the Stipulated Price for completing all work, materials, equipment, and other incidentals required to complete the project in accordance with Contract Documents. 7.12 The City will consider the Offeror's proposed Cost Proposal for completion of the project in determining best value to the Owner. CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 2 — AD8 0042 10 PROPOSAL Page 6 of 8 7.13 Postal and e-mail addresses and telephone number for communications regarding the Proposal shall be shown. ARTICLE 8. OFFER SUBMITTAL This Proposal is submitted on by the entity named below. Month Day Year The Offeror hereby submits this Proposal as set forth in this Section: Offeror: M. Name: Title: (typed or printed name of organization) (individual's signature) (typed or printed) (typed or printed) Date: (typed or printed) If Bidder is a corporation, a partnership, or a joint venture, attach evidence of authority to sign. Attest: (individual's signature) Name: (typed or printed) Title: (typed or printed) Date: (typed or printed) By initialing below, receipt is acknowledged of the following Addenda: Addendum No. 1 Addendum No. 6 Addendum No. 2 Addendum No. 7 Addendum No. 3 Addendum No. 8 Addendum No. 4 Addendum No. 9 Addendum No. 5 Addendum No. 10 CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 2 — AD8 Address for giving notices: Bidder's Contact: Name: Title: Phone: Email: Address: 0042 10 PROPOSAL Page 7 of 8 Bidder's Contractor License No.: (if applicable) (typed or printed) (typed orprinted) ++END OF SECTION++ CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 2 — AD8 0042 10 PROPOSAL Page 8 of 8 ++++ THIS PAGE INTENTIONALLY LEFT BLANK.... CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 2 - AD8 00 42 10 PROPOSAL EXHIBIT A Item No. Description 1 Mobilization, Limited to 2 Percent of Total Amount 2 Familiarization and Preliminary Assessment 3 Design 4 Eagle Mountain WTP Configuration, Cutover and Startup 5 South Holly WTP Configuration, Cutover and Startup 6 North Holly WTP Configuration, Cutover and Startup 7 Westside WTP Configuration, Cutover and Startup 8 Rolling Hills WTP Configuration, Cutover and Startup 9 Centralized SCADA Configuration, Cutover and Startup 10 Allowance for Additional Familiarization, Preliminary Assessment and Design Services 11 Allowance for Procurement of Additional Hardware and Software 12 Allowance for Additional Configuration, Cutover and Startup Services 13 Allowance for Additional Data Warehouse / Data Base Programming Services TOTAL AMOUNT (ITEMS NO. 1 -13) Unit Extended Amount Notes LS / 1 LS 1 LS 1 LS 1 LS 1 LS 1 LS 1 LS 1 LS / 1 LS 75,000.00 2 LS 75,000.00 2 LS 75,000.00 2 LS 75,000.00 2 / / / / 3 Notes: 1. Proposal Item No. 1 through No. 9 costs shall be entered into Bonfire as instructed on the Procurement Portal. 2. The Offeror shall manually enter the allowance amount indicated into Bonfire as instructed on the Procurement Portal. 3. The Bonfire system with provide a total for all Proposal Items following manual entry by the Offeror. The Offeror shall verify the total. CITY OF FORT WORTH MARCH 21, 2024 SCADA SYSTEM REPLACEMENT 103086 ATTACHMENT 2 - AD8 ++THIS PAGE INTENTIONALLY LEFT BLANK++ SCADA SYSTEM REPLACEMENT CITY OF FORT WORTH 103086 MARCH 21, 2024 ATTACHMENT 2 - AD8 00 45 42 BUSINESS EQUITY GOAL CSP Page 1 of 2 SECTION 00 45 42 BUSINESS EQUITY GOAL CSP APPLICATION OF POLICY If the total dollar value of the contract is $100,000 or more, then a Business Equity goal is applicable. A Business Equity Firm refers to certified Minority-, and/or Women-, owned Business Enterprises (M/WBEs). POLICY STATEMENT It is the policy of the City of Fort Worth to ensure the full and equitable participation of Business Equity Firms when applicable, in the procurement of all goods and services. All requirements and regulations stated in the City's Business Equity Ordinance No.25165-10-2021, (replacing Ordinance No. 24534-11- 2020 (codified at: httDs://codelibrarv.amleaal.com/codes/ftworth/latest/ftworth_tx/0-0-0-22593) apply to this bid. BUSINESS EOUITY PROJECT GOAL The City's Business Equity goal on this project is 5% of the total bid value of the contract (Base bid applies to Parks and Community Services). METHODS TO COMPLY WITH THE GOAL On City contracts where a Business Equity Goal is applied, offerors are required to comply with the City's Business Equity Ordinance by meeting or exceeding the above stated goal or otherwise comply with the ordinance through one of the following methods: 1. Commercially useful services performed by a Business Equity prime contractor, 2. Business Equity subcontracting participation, 3. Combination of Business Equity prime services and Business Equity subcontracting participation, 4. Business Equity Joint Venture/Mentor-Prot6g6 participation, 5. Good Faith Effort documentation, or 6. Prime contractor Waiver documentation. SUBMITTAL OF REOUIRED DOCUMENTATION Applicable documents (listed below) must be received by the Purchasing Division, OR the offeror shall EMAIL the Business Equity documentation to the assigned City of Fort Worth Project Manager or Department Designee. Documents are to be received no later than 2:00 p.m., on the third City business day after the proposal opening date, exclusive of the proposal opening date. Refer to Section 00 1115 Notice to Offerors for notification procedures. The Offeror must submit one or more of the following documents: 1. Utilization Form and Letter(s) of Intent, if the goal is met or exceeded; 2. Good Faith Effort Form and Utilization Form, including supporting documentation, if participation is less than stated goal, or no Business Equity participation is accomplished; 3. Prime Contractor Waiver Form, including supporting documentation, if the Offeror will perform all subcontracting/supplier opportunities; or 4. Joint Venture/Mentor-Prot6g6 Form, if goal is met or exceeded with a Joint Venture or Mentor- Prot6g6 participation. CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 3 — AD8 00 45 42 BUSINESS EQUITY GOAL CSP Page 2 of 2 These forms can be found at: Business Equity Utilization Form and Letter of Intent httDs://apes.fortworthtexas.Rov/ProiectResources/ResourcesP/60 - MWBE/Business Equity Utilization Form DVIN 2022 220324.pdf Letter of Intent https://apps.fortworthtexas.Rov/ProiectResources/ResourcesP/60 - MWBE/Letter of Intent_DVIN 202 Lvdf Business Equity Good Faith Effort Form httos://apps.fortworthtexas.2ov/Pro_iectResources/ResourcesP/60 - MWBE/Good Faith Effort Form DVIN2022.pdf Business Equity Prime Contractor Waiver Form httos://apps.fortworthtexas.2ov/Pro_iectResources/ResourcesP/60 - MWBE/MWBE Prime Contractor Waiver-220313.pdf Business Equity Joint Venture Form httos://apps.fortworthtexas.2ov/Pro_iectResources/ResourcesP/60 - MWBE/MWBE Joint Venture 220225.Ddf FAILURE TO ACHIEVE THE GOAL OR OTHERWISE COMPLY WITH THE ORDINANCE WILL RESULT IN THE BIDDER/OFFEROR BEING DECLARED NON -RESPONSIVE AND THE BID REJECTED. FAILURE TO SUBMIT THE REOUIRED BUSINESS EOUTY DOCUMENTATION OR OTHERWISE COMPLY WITH THE ORDINANCE WILL RESULT IN THE BID BEING DECLARED NON -RESPONSIVE, THE BID REJECTED AND MAY SUBJECT THE BIDDER/OFFEROR TO SANCTIONS AS DESCRIBED IN SEC. 20-373 OF THE ORDINANCE. For Questions, Please Contact The Business Equity Division of the Department of Diversity and Inclusion at (817) 392-2674. ++END OF SECTION++ CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 3 — AD8 ADDENDUM NO. 9 Page 1 of 2 CITY OF FORT WORTH, TEXAS CONTRACT FOR THE CONSTRUCTION OF SCADA SYSTEM REPLACEMENT ADDENDUM NO. 9 This Addendum is part of the Contract Documents and modifies the Contractor for The Construction of SCADA System Replacement Document dated March 2024 for the above referenced project. This change affects the Document distributed on March 21, 2024 to prequalified Offerors. Acknowledge receipt of this Addendum in accordance with the requirements in Section 00 21 15 Instructions to Offerors Article 1.16 I. Failure to do so may result in the Proposal being deemed non- responsive. Overview and General Clarifications: 1. This addendum modifies Section 00 11 15 Notice to Offerors, changing the Proposal Due Date to June 13, 2024 at 2:00 PM CT. ADDENDUM ITEMS (SPECIFICATION MODIFICATIONS & PROJECT CLARIFICATIONS): 1. In Section 00 1115 — Notice to Offerors, DELETE the first paragraph in the Receipt of Proposals section and replace with the following paragraph: "Competitive Sealed Proposals (CSP) for the delegated design and construction of SCADA System Replacement ("Project") for the Water Department will be received by the City of Fort Worth. Proposals will be received from prequalified Offerors only via the Procurement Portal: httys://fortworthtexas.bonfirehub.com/portal/?tab=openOpportunities, under the respective Project opportunity page until 2:00 PM CST, Thursday, June 13, 2024, as further described below." 2. In Section 00 1115 - Notice to Offerors, delete the Proposal Due Date event in the Schedule for Procurement and replace with the following: " Proposal Due Date June 13, 2024 by 2:00 PM CT" ADDENDUM NO. 9 Page 2 of 2 or -r f .*: •*� / ROSSER R. STANDIFER.� � 92755 •��� ss o�nrAi��� Rosser R. Standifer, PE Principal Engineer Arcadis Addendum No. 9 Issued by the City of Fort Worth Date: June 12, 2024 Alexander Pierce Project Manager City of Fort Worth END OF ADDENDUM No. 9 THE CITY OF FORT WORTH WATER DEPARTMENT THE CONSTRUCTION OF SCADA SYSTEM REPLACEMENT The following specifications were provided by R. Standifer ARCADIS-US, Inc.: DIVISION 00 — GENERAL CONDITIONS 0005 10 Mayor and Council Communication (M&C) 0005 15 Addenda 00 11 15 Notice to Offerors 0021 13 Prequalification Instructions 0021 15 Instructions to Offerors 0023 13 Non -Disclosure Agreement 0035 13 Conflict of Interest Affidavit 0042 10 Proposal 0043 15 Proposal Surety (Bid Bond) 00 43 37 Vendor Compliance to State Law Non -Resident Bidder 00 45 26 Contractor Compliance with Worker's Compensation 00 45 42 Law Business Equity Goal CSP 0046 12 Offeror Statement of Qualifications 00 52 45 Agreement 0061 13 Performance Bond 0061 19 Maintenance Bond 0061 25 Certificate of Insurance 00 72 00 General Conditions 00 73 00 Supplementary Conditions DIVISION 01— GENERAL REQUIREMENTS 01 11 13 Summary of Work 01 1416 Coordination with City's Operations CITY OF FORT WORTH SCADA Replacement March 21, 2024 103086 01 1419 Use of Site 0122 13 Measurement and Payment 01 26 00 Contract Modification Procedures 01 29 73 Schedule of Values 01 29 76 Progress Payment Procedures 01 31 13 Project Coordination 01 31 19.23 Progress Meetings 01 3126 Electronic Communication Protocols 01 3216 Progress Schedule 01 3300 Submittal Procedures 01 7000 Mobilization and Remobilization 01 77 19 Closeout Requirements 01 7823 Operations and Maintenance Data 01 7836 Warranties 01 7839 Project Record Documents CITY OF FORT WORTH March 21, 2024 .............. I ......... s*•�/ ROSSER R. STANDIFER .:....92755 ...:...y /CENSE��G:�L^�/I SCADA Replacement 103086 THE CITY OF FORT WORTH WATER DEPARTMENT THE CONSTRUCTION OF SCADA SYSTEM REPLACEMENT The following specifications were provided by S. Onvani ARCADIS-US, Inc.: DIVISION 40 — PROCESS INTERCONNECTIONS 4061 13 SCADA System General Provisions 40 61 21 SCADA System Factory Acceptance Testing 4061 23 SCADA System Field Assessment, Testing, and Start -Up 4061 26 SCADA System Training 40 68 63 SCADA System Programming and Configuration ��PZE OF T 4XF% % t .......................... SALMAN ONVANI .........................:... o • 149764 11��SS�ONA1. 03/2I / yo2`i CITY OF FORT WORTH SCADA Replacement March 21, 2024 103086 ++++ THIS PAGE INTENTIONALLY LEFT BLANK.... CITY OF FORT WORTH SCADA Replacement March 21, 2024 103086 0011 15 NOTICE TO OFFERORS Page 1 of 6 6ylei 0to] 2[oIl]I10R NOTICE TO OFFERORS PREQUALIFICATION FOR SUBMITTAL OF COMPETITIVE SEALED PROPOSALS PREOUALIFICATION Offerors intending to submit proposals must be Prequalified as an Offeror for this specific ru oiect by the City prior to receipt of the Contract Documents. Request for Prequalification for the SCADA System Replacement ("Project") will be received by the City of Fort Worth via the Procurement Portal at: htti)s:Hfortworthtexas.bonfirehub.com/portal/?tab=oi)en0pportunities, under the respective Project opportunity page until 4:00 P.M. CST, Friday, April 12, 2024. DOCUMENT EXAMINATION AND PROCUREMENTS Prior to prequalification, the document sections noted in Section 00 21 13 — Prequalification Instructions will be available to all interested parties. The procedures and requirements for Prequalification are outlined in Section 00 21 13 — Prequalification Instructions. Additional information applicable to the subsequent submittal of Competitive Sealed Proposals (CSP) is included in Section 00 21 15 — Instructions to Offerors. The limited Contract Document content noted will be available electronically to interested parties via the Procurement Portal: htt_ps://fortworthtexas.bonfirehub.com/_aortal/?tab=oDen0_v_vortunities, under the respective Project. The full content of the Contract Documents will be available to all Prequalified Offerors following confirmation that the Offeror is prequalifed and receipt of an executed (signed) copy of Section — 00 23 13 Non -Disclosure Agreement. The Contract Documents may be shared with and viewed by sub -contractors teamed with Prequalified Offerors and with suppliers as necessary to develop a Proposal subject to the provisions of the Non -Disclosure Agreement. The Contract Documents and all Addenda will be available electronically to Prequalified Offerors via the Procurement Portal: httr)s://fortworthtexas.bonfirehub.com/_aortal/?tab=o_ven0_v_vortunities, under the respective Project. RECEIPT OF PROPOSALS Competitive Sealed Proposa s (CS ) or t e delegated design an construction o S A ystem Replacement ("Project") for the Water Department will be received by the City of Fort Worth. QProposals will be received from prequalified Offerors only via the Procurement Portal: s htti)s:Hfortworthtexas.bonfirehub.com/portal/?tab=oi)enOpportunities. under the respective Project opportunity page until 2:00 PM CST, Thursday, June 13, 2024, as further described below. The CSP will be opened publicly and read aloud at 2:00 PM CST in the City Council Chambers. NOTE: Submittal of Business Equity Documents within 3 days of the opening of Proposals is required for ALL OFFERORS. CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 1— AD8 0011 15 NOTICE TO OFFERORS Page 2 of 6 Your submissions must be uploaded, finalized, and submitted prior to the Project's posted due date. The City strongly recommends allowing sufficient time to complete this process (ideally a week prior to the deadline) to begin the uploading process and to finalize your submission. Uploading large documents may take time, depending on the size of the file(s) and your Internet connection speed. The Bonfire portal can be accessed using Microsoft Edge, Google Chrome, or Mozilla Firefox. Javascript must be enabled. Browser cookies must be enabled. Electronic submission is subject to electronic interface latency, which can result in transmission delays. All proposers assume the risk of late transmission/ submission. The City shall not be held liable if an interested party is unable to submit a complete response before the published deadline due to transmission delays or any other technical issues or obstructions. The City strongly recommends allowing sufficient time to complete the submission process (ideally a week before the deadline) to begin the uploading process and to finalize your submission to give adequate time in the event an issue arises. All submissions must be submitted electronically prior to the close date and time under the respective Project/Solicitation via the Procurement Portal: httDs://fortworthtexas.bonfirehub.com/portal/?tab=oDenODDortunities Offerors shall submit the electronic (PDF) file proposal file as instructed on the Procurement Portal. The Cost Proposal, in the form of a cost for each Proposal Item No., shall be entered into Procurement Portal as instructed under the respective project. Allowance Proposal Items shall be manually entered by the Offeror in the amounts noted in Section 00 42 10 Proposal Exhibit A. See additional information in Section 00 42 10 Article 6 Basis of Offer. Failure to submit all completed required information listed in the respective Solicitation will be grounds for rejection of a prequalification request or subsequent submitted proposal as non- responsive. No late proposals shall be accepted. Proposals delivered in any other manner than using the Bonfire Platform (Procurement Portal) will not be accepted or considered. If, upon being opened, a submission is unreadable to the degree that material conformance to the requirements of the procurement specifications cannot be ascertained, such submission will be rejected without liability to the City, unless the Offeror provides clear and convincing evidence (a) of the content of the submission as originally submitted and (b) that the unreadable condition of the Electronic Proposal was caused solely by error or malfunction of the Bonfire Platform (Procurement Portal). Failure to scan a clear or readable copy of a response into the system does not constitute and shall not be considered an error or malfunction of the Bonfire Platform (Procurement Portal). Offerors are encouraged to fully review each page of every document within their submission prior to submitting to ensure all documents are clear, legible, and complete. SUPPORT For technical questions, visit Bonfire's help forum at: https://vendorsuDDort.2obonfire.com/hc/en-us Contact the Bonfire support team at Support@GoBonfire.com or by calling 1-800-354-8010. To get started with Bonfire, watch this five-minute training video: Vendor Reeistration and Submission Video - Bonfire Vendor Support (2obonfire.com) CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 1— AD8 0011 15 NOTICE TO OFFERORS Page 3 of 6 EXISTING SYSTEM The existing Water Department Supervisory Control and Data Acquisition (SCADA) system is a proprietary HSQ Technologies system originally installed in 1987, upgraded in 1991, and since then has been developed and updated as the system has expanded. The SCADA system uses licensed 900 MHz radio frequencies to communicate with the remote distribution facilities. At the City's potable water treatment facilities - North Holly, South Holly, Rolling Hills, Westside, and Eagle Mountain Water Treatment Plants (WTPs) - three different Human Machine Interface (HMI) platforms are utilized. These include HSQ-Miser, GE Cimplicity, and Allen-Bradley FactoryTalk View SE, all of which report to a top -end and head -end HMI (HSQ-Miser). GENERAL DESCRIPTION OF WORK The project includes the design, configuration, testing, start-up, and maintenance through Final Acceptance of a complete SCADA replacement for the City's Water Department SCADA system, inclusive of but not limited to: upgraded SCADA systems at each of the five WTPs; a new centralized SCADA system; an upgraded SCADA system architecture to support the SCADA replacement; a new data architecture to support a comprehensive historical data collection and reporting interface and other work elements to support the SCADA upgrades. The City has procured a SCADA software, Ignition by Inductive Automation, which is to be used for the new HMI. This software will be provided by the City for use by the Contractor in implementation, installation, configuration, testing and start-up of the replacement system. The Contractor shall provide the following project services. Pre -Construction Services including Familiarization and Preliminary Assessment and Design Services for SCADA system architecture and component selection requirements. Construction Services to include Programming and Configuration; Factory Acceptance Testing; Cutover, Field Testing, and Start -Up; System Maintenance, Final Acceptance, and Warranty. EXPRESSION OF INTEREST To ensure awareness of any new information pertinent to this project, all interested parties should indicate their intent to request prequalifcation in the Procurement Portal by selecting "yes" under the "Intent to Bid" section the Procurement Portal: httl)s://fortworthtexas.bonfirehub.com/portal/?tab=oDenODDortunities, under the respective Project. Any and all subsequent Addenda will also be available to the Prequalified Offerors via the Procurement Portal. SCHEDULE FOR PROCUREMENT 1st Advertisement for CSP — Prequalification Requirements 2" d Advertisement for CSP — Prequalification Requirements Virtual Prequalification Q&A Meeting Deadline for Prequalification Questions Deadline to Request Prequalification Offerors Notification of Prequalification Contract Document Release Date (anticipated) Pre -proposal 2 Day Site Visit (Primary) CITY OF FORT WORTH March 21, 2024 March 21, 2024 March 28, 2024 April 1, 2024, 2:00 PM CT April 5, 2024 April 12, 2024, 4:00 PM (Local Time) April 19, 2024 April 19, 2024 May 1 —May 2, 2024 SCADA System Replacement 103086 ATTACHMENT 1— AD8 0011 15 NOTICE TO OFFERORS Page 4 of 6 SCHEDULE FOR PROCUREMENT (CONTINUED) Pre -proposal Conference — In Person and Virtual (anticipated) Pre -proposal 2 Day Site Visit (Backup)* Deadline for Questions (anticipated) Deadline for Responses via Addenda QProposal Due Date Evaluation of Proposals (anticipated) Oral Clarifications (anticipated, if required) Notice to Proceed (anticipated) Notes: May 8, 2024, 8:30 - 9:30 AM CT May 8 — May 9, 2024 May 15, 2024, 5:00 PM CT May 22, 2024, 5:00 PM CT June 13, 2024 by 2:00 PM CT June 14, 2024 through June 26, 2024 June 20, 2024 through June 25, 2024 August 7, 2024 * Should adverse weather or unforeseen events at the Water Treatment Plants require rescheduling of the Pre -proposal 2 Day Site Visit from the Primary dates above, it is the City's intent to conduct the in conjunction with the Pre -Proposal Conference the following week on the dates indicated. PREOUALIFICATION O&A MEETING — Virtual Conference Prequalification Question and Answer (Q&A) will be held as described in Section 00 21 15 — Instructions to Offerors on the following anticipated date and time, via a web conferencing application only. DATE: April 1, 2024 TIME: 2:00 pm CT A link to the web conference will be available on the Procurement Portal under the respective Project. PRE -PROPOSAL SITE VISIT A pre -proposal site visit will be held as described in Section 00 21 15 — Instructions to Offerors on the following anticipated date and time. DATE: May 1 - May 2, 2024 TIME: 9:00 AM CT Each prequalified Offeror shall select up to two (2) attendees to attend the site visit. Each Offeror shall send the names of the attendees to the City's Project Manager via email, a minimum of 48- hours in advance of the site visit. Should adverse weather or unforeseen events at the Water Treatment Plants require rescheduling of the site visit, it is the City's intent to conduct the in conjunction with the Pre -Proposal Conference the following week as noted in the Schedule for Procurement. PRE -PROPOSAL CONFERENCE — In -person and Virtual Conference An in -person pre -proposal conference will be held as described in Section 00 21 15 — Instructions to Offerors on the following anticipated date and time, as well as simultaneously via a web conferencing application. CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 1— AD8 0011 15 NOTICE TO OFFERORS Page 5 of 6 DATE: May 8, 2024 TIME: 8:30 - 9:30 AM CT An invitation with a link to the web conferencing application will be distributed to Prequalified Offerors. The presentation along with any questions and answers provided at the Pre -proposal Conference will be issued as an Addendum. Prequalified Offerors may also ask questions or comments in accordance with Section — 00 21 15 Instructions to Offerors Article 1.9. Any questions received will be answered by Addenda. Addenda will be issued pursuant to Section 00 21 15 — Instructions to Offerors. CITY'S RIGHT TO ACCEPT OR REJECT PROPOSALS City reserves the right to waive irregularities and to accept or reject any or all proposals. AWARD The City will award a contract to the Offeror presenting the best value based on the evaluation criteria noted in Section 00 21 15 — Instruction to Offerors. After evaluating and notifying the Selected Offeror that offers the best value, the City will enter into negotiations with that Offeror. ADVERTISEMENT DATES 1 st Advertisement for Prequalification March 21, 2024 2nd Advertisement for Prequalification March 28, 2024 ++ END OF SECTION ++ CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 1— AD8 0011 15 NOTICE TO OFFERORS Page 6 of 6 ++THIS PAGE INTENTIONALLY LEFT BLANK++ CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 1- AD8 0021 13 PREQUALIFICATION INSTRUCTIONS Page 1 of 4 SECTION 00 21 13 PREQUALIFICATION INSTRUCTIONS 17:1k914awt9g1►111kill Il 1.1 DEFINED TERMS A. Capitalized terms used in these Prequalification Instructions are defined in Section 00 72 00 — General Conditions. Certain additional terms used in this Section have the meanings indicated below which are applicable to both the singular and plural thereof. B. Firm: The term "firm" is used in this Section to denote the person, partnership, company, association, corporation submitting a proposal and generically in describing the proposal content and evaluation to represent the broader team presented by the Offeror. C. Offeror: Any person, firm, partnership, company, association, or corporation acting directly through a duly authorized representative, submitting a proposal for performing the work contained in the Contract Documents. D. Prime Contractor: The term "Prime Contractor" is used in this Section to refer to the entity (person, firm, partnership, company, association, or corporation) submitting a proposal as an Offeror when it is necessary to distinguish between the entity and subcontractors, consultants or suppliers with which the Prime Contractor intends to place under contract to perform portions of the Work. 1.2 DOCUMENT DISTRIBUTION AND HANDLING A. Distribution of the Contract Documents shall be restricted to Prequalified Offerors. To facilitate prequalifcation, the following sections are available to all interested parties as noted in Section 00 11 15 — Notice to Offerors: 1. Section 00 11 15 — Notice to Offerors. 2. Section 00 21 13 — Prequalification Instructions. 3. Section 00 21 15 — Instructions to Offerors. Q4. Section 00 72 00 — General Conditions, see Article 1.2 B below. 2 5. Section 00 73 00 — Supplementary Conditions, see Article 1.2 B below. B. Following notification of the City's acceptance as a Prequalified Offeror and subsequent receipt of an executed copy of Section 00 23 13 — Non -disclosure Agreement, the City will provide a complete copy of the Contract Documents. C. It is anticipated that the full set of Contract Documents will be available no later than the date listed in Section 00 11 15 — Notice to Offerors as Contract Document Release Date. CITY OF FORT WORTH March 21, 2024 SCADA System Replacement 103086 0021 13 PREQUALIFICATION INSTRUCTIONS Page 2 of 4 1.3 PREQUALIFICATION INFORMATION AND REQUIREMENTS A. General Information: 1. No Major Work Categories require the Offeror or listed subcontractors to prequalify separately as bidders via the City of Fort Worth TPW Lighting, TPW Paving or Water Contractor procedures. Prequalification for this project as described as either a Prime Contractor or as a subcontractor listed by an Offeror is sufficient. 2. Offerors submitting to perform the work as the Prime Contractor are required to be prequalified for this specific Project. Prior prequalification for other City work is not sufficient. 3. Subcontractors listed by an Offeror will be evaluated based on the information submitted by the Offeror. Subcontractors do not need to separately prequalify unless they are pursuing this project as a Prime Contractor. 4. The City has determined that a phase approach to Performance and Payment Bonding is acceptable for this Project. Offerors should refer to Section 00 73 00 General Conditions, as modified by Section 00 73 00 for details. No portion of the Work can begin prior the City issuing a Notice to Proceed that is specifically listed, including the Proposal Item Numbers and Descriptions of the portion of the Work the Contractor is seeking to perform beyond that previously bonded. Prior to issuing a Notice to Proceed the City must be in possession of executed Performance and Payment Bonds covering the added portion of the Work. B. Submission Requirements: 1. Offerors seeking prequalification, shall prepare and submit a cover letter and qualification attachment prior to the date listed in Section 00 11 15 — Notice to Offerors. 2. The qualification attachment format shall be determined by the Offeror. While there is not a page limit it is the City's intent that the submittal be concise and contain only the information specifically requested below. 3. The qualification attachment shall contain the following eight (8) items in numbered sections, in the sequence listed in this article, to facilitate the City's prequalification review. Each item shall be preceded by a tabbed fly sheet. a. Cover letter that: CITY OF FORT WORTH March 21, 2024 1) Identifies the firm's legal name, corporate office address, along with the name, email, and telephone contact information for the firm's point of contact for this project. 2) Acknowledges receipt of addenda in the cover letter, listing each addendum by number. 3) Acknowledges the City's Business Equity Goal noted in Section 00 11 15 —Notice to Offerors. 4) Notes the firms aggregate and available bonding capacity. 5) Acknowledges that the Prime Contractor shall perform, with his own organization, work of a value not less than 40% of the value the Work embraced on the Contract. 6) Notes any current City of Fort Worth projects that are in progress but not yet complete, including a brief summary of the scope of work. Note: prior experience with the working for City of Fort Worth is note required. SCADA System Replacement 103086 0021 13 PREQUALIFICATION INSTRUCTIONS Page 3 of 4 b. Financial statement prepared within the past 12 months signed by a CPA. The full original financial statement shall be included. c. While the completion of prior work for the City is not required, Offeror's who have prior project experience shall provide a tabular list of past City of Fort Worth projects. The Offeror shall list all completed projects including the project name, City project number, City project manager, and the project's bid open date. d. Provide a minimum of five (5) projects that best demonstrate the firm's ability to complete the Work. The format and length of description should be no more than one to two pages in length. Photographs are not required but may be included at the option of the Offeror. For each project at minimum include the following: 1) Project Name and Location. 2) Type of project. 3) Note whether the firm was a prime contractor or worked as a subcontractor along with the firm's role and scope of work performed. 4) Provide a contact person and contact number for a firm employee with knowledge of the project. 5) Provide the name of project owner and the name and contact information for the owner's project manager. 6) Note the total construction contract price. 7) Summarize the scope of work completed. 8) Provide the date construction started and date of final acceptance (payment) for all work. e. Provide a tabular list of firm projects that are currently under construction. Note the project start date, construction contract price, name of project owner and the name and contact information for the owner's project manager. f. Provide the firm's Induction Automation Ignition Certified Level. If the Prime Contractor is not certified the name and Certified Level of a subcontractor shall be included. g. Provide a narrative summary of the firm's construction experience that includes: 1) The number of years the company has been in business as a prime contractor under present business name. 2) An answer to the question: "Has the company operated under any other name?" Provide either a definitive statement that the firm has not operated under other names or, if necessary, state what additional name or names the firm has operated under, and the location or locations. If the firm has operated under other names provide a brief explanation. 3) The number of years of experience in water/sewer experience in SCADA design and integration services. 4) The number of years of operation while certified in Induction Automation Ignition. Include the level of certification and years at each level if the firm has transitioned between certification levels. 5) The water/sewer SCADA design and integration experience of the principals of the firm, including name, present position, years of experience, type of experience (water/sewer), licenses, certifications, etc. In addition, provide the same experience information for firm personnel that would be assigned to this project. CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 0021 13 PREQUALIFICATION INSTRUCTIONS Page 4 of 4 h. Each Offeror seeking prequalification shall submit a list of subcontractors the Offeror intends to enter into subcontract agreements with for portions of the Work. Noting the percentage of the work to be performed by each subcontractor is not required for Prequalification. C. Questions and Additional Information Requests: 1. Submission of and/or questions related to prequalification should be addressed to the City's contact noted in Section 00 11 15 — Notice to Offerors. 2. In evaluating for requests for prequalification and the subsequent Proposals received, the City reserves the right to require any interested party (Offeror) to submit such additional information as the City, in its sole discretion may be required to assist the City in evaluating and assessing the ability of the offeror to deliver a quality product and successfully complete projects for the amount proposal within the stipulated time frame. Failure to submit the additional information, if requested, may be grounds for rejecting an offeror as non- responsive and thereby not prequalified. Individual Offerors are solely responsible for gaining pre -qualification prior to submittal of an Offer. 1.4 EVALUATION FOR PREOUALIFICATIONS OF OFFERORS A. Prequalification of Offerors shall be based the City's review of the completeness of content in the submittal noted in Article 1.3. B. 3. of this Section. B. Offerors will be notified of their prequalification status prior to the date noted in Section 00 11 15 — Notice to Offerors utilizing the Contact Information provided in accordance with Article 1.3 B. 3. a. 1) of this Section. PART 2 — PRODUCTS (NOT USED) PART 3 — EXECUTION (NOT USED) ++END OF SECTION++ CITY OF FORT WORTH March 21, 2024 SCADA System Replacement 103086 SECTION 00 21 15 INSTRUCTIONS TO OFFERORS PART 1 — GENERAL 1.1 DESCRIPTION 0021 15 INSTRUCTIONS TO OFFERORS Page 1 of 22 A. This Section is included in the documents made available publicly for Prequalification to facilitate evaluation of Proposal submittal requirements by all interested parties. B. This Section contain detailed instructions that will be used by Prequalified Offeror to preparing the Proposal and assess the City's approach to evaluating all proposals received. Modifications to this Section, if necessary, will be made by addenda. IVM 191aI1 1911101217STfy A. Capitalized terms used in these Instructions to Offerors are defined in Section 00 72 00 — General Conditions. B. The terms Firm, Offeror and Prime Contractor as used in this Section are defined in Section — 00 21 13 Prequalification Instructions, Article 1.1. Certain additional terms used in these Instructions to Offerors have the meanings indicated below which are applicable to both the singular and plural thereof. C. Non-resident Offeror: Any person, firm, partnership, company, association, or corporation acting directly through a duly authorized representative, submitting a proposal for performing the work contemplated under the Contract Documents whose principal place of business is not in the State of Texas. D. Prime Contractor: The terms "Prime Contractor" are used in this Section to refer to the entity (person, firm, partnership, company, association, or corporation) submitting a proposal as an Offeror when it is necessary to distinguish between the entity and subcontractors, consultants, or suppliers with which the Prime Contractor intends to place under contract to perform portions of the Work. E. Selected Offeror: The Offeror whom the City determined, based on the evaluation criteria provided in this Section, presented the best value to the City and was subsequently notified in writing of the City's intent to begin negotiations. F. Preconstruction: Refers to the period prior to the start of construction activities. Preconstruction duties are detailed in Section 40 61 13 — SCADA System General Provisions. Preconstruction activities include Familiarization and Preliminary Assessment and Design Services for SCADA system architecture and component selection requirements. CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 2 — AD3 0021 15 INSTRUCTIONS TO OFFERORS Page 2 of 22 G. Construction: Refers to the activities specified in Section 40 61 13 SCADA System General Provisions which include Programming and Configuration; Factory Acceptance Testing; Cutover, Field Testing, and Start -Up; System Maintenance, Final Acceptance, and Warranty. 1.3 DOCUMENT DISTRIBUTION AND HANDLING A. Distribution of the Contract Documents shall be restricted to Prequalified Offerors. B. The City makes copies of Contract Documents available only for the purpose of obtaining Proposals for the Work and do not authorize or confer a license or grant for any other use. C. Attachment 3 — Existing HMI Databases, and Attachment 5 — Existing Reports are not necessary to prepare the Proposal. This content will be available to the Successful Offeror for reference in accomplishing Work. Section 40 68 63 — SCADA System Programming and Configuration provides comprehensive information regarding the existing HMI tag counts and existing reports, enabling the Offeror to effectively prepare the Proposal. D. The City assumes no responsibility for errors or misinterpretations resulting from the Offeror's use of incomplete sets of Contract Documents. 1.4 PROPOSAL ORGANIZATION: A. To facilitate the City's review of the Proposal, offerors are requested to organize the main document as outlined below. Proposals shall include a cover page, table of contents, and section dividers. All pages, with the exception of the project schedule, shall be 8.5"xI I" with a minimum font size of 12. The proposed schedule, if desired, may be presented on a single I I" x 17" page. The Offeror shall divide the submitted Offeror Overview - Provide an additional narrative overview of Organization & General Business Information. This information should summarize details provided in Section 00 46 12 — Offeror Statement of Qualifications and include: a. Provide general information on your company including the Offeror (company) name, address, website, main telephone number(s) and email address(es) for communication regarding the Proposal. b. Brief narrative introduction of the Offeror (Prime Contractor). c. Summary of the administration, d. Organization and staffing of your company. e. Include any information that makes your company unique and sets your company apart from others in your industry. f. Include indicators of organization size: 1) Number of full-time employees, 2) Average number of projects per year, 3) Number of years in business, 4) Estimated Prime Contractor annual revenue, and 5) Average prior project construction cost. CITY OF FORT WORTH March 21, 2024 SCADA System Replacement 103086 ATTACHMENT 2 — AD3 0021 15 INSTRUCTIONS TO OFFERORS Page 3 of 22 g. Provide an updated list of all subcontractors, suppliers, and materials necessary to fulfill the Offeror's proposal. The Offeror shall include the approximate percentages of the Work planned for each subcontractor. The planned approach for meeting the M/WBE goal noted in Section 00 45 42 — Business Equity Goal CSP shall be clearly stated in the Offeror Overview. 2. Project Approach — The narrative, organizational, schedule, quality management, project controls and safety information, formatted by the Offeror with supporting photographs, figures and graphics. The Offeror shall include all items noted below. 3. Firm Experience — Information on projects, selected by the Offeror from those submitted in Section 00 46 12 — Offer Statement of Qualifications forms. This section shall be narrative in nature, formatted by the Offeror with supporting photographs, figures, certificates, and graphics for each project. The Offeror shall include all items noted below. 4. Key Personnel and Subcontractors — Information on all key personnel critical to project success. This section shall include detailed resumes and other information outlined below. 5. Schedule — Information on Offeror's proposed milestones and Project Completion. ,3ccuvu vv •tv L/- — viiclvi aLatciucut vi yuaiiucauvub. luciuuc iii iw ciiLuFty witu the submittal. Provide a cover sheet that includes a numbered list of any changes made in any of the information since offeror's prequalification submittal. Note the page number and content of each change. Changes made but not expressly noted will count negatively during the evaluation. B. The Project Approach: 1. The Project Approach section shall include the following minimum components: 2. Narrative — The narrative should describe the Offeror's approach to the overall Project. This should at minimum include: a. Overview of the sequence of construction and corresponding timelines and milestones present in the Offeror's proposed schedule. b. Detailed description of the execution of the Familiarization, Preliminary Assessment, and Design tasks noted in Section 40 61 13 — SCADA System General Provisions. c. Detailed description of the execution of the Programming and Configuration, Factory Acceptance Testing, Cutover, Field Testing, and Start-up tasks noted in Section 40 61 13 — SCADA System General Provisions. d. Acknowledgement of the review and intended compliance with the City's PLC and HMI Configuration Standards as outlined in Attachment 1. e. The Offeror's summary of all other pertinent information considered essential to completing the project in accordance with the Contract Documents, and within the proposed Budget and Schedule. f. One or more examples, drawn from the Offeror's submitted project experience, illustrating the benefit of specific components of the described approach. g. The Offeror's ability to provide maintenance of the system from completion of each Operational Availability Demonstration through Final Acceptance of the project, as required in the project scope. CITY OF FORT WORTH March 21, 2024 SCADA System Replacement 103086 ATTACHMENT 2 — AD3 0021 15 INSTRUCTIONS TO OFFERORS Page 4 of 22 h. The Offeror's capabilities to assist the City in long-term maintenance of the i. Proprietary solutions, protocols and communications deviating from those identified in the project will not be accepted and constitute rejection of the Qoffer. Demonstrate a distributed solution whereby data can be available 4 from any site at Centralized SCADA. Demonstrate adherence to the City HMI and PLC standards as provided in Attachment 1. Products identified with no exceptions and no substitutions must be submitted as such. proposed team. Include all Key Personnel roles required as part of the Statement of Qualifications requirements. Offerors may include a narrative describing the approach to team organization and division of key roles. Resumes shall be provided as noted in Article 1.4 D of this Section. 4. Schedule — Provide a preliminary schedule for the Project and coordinate with the Schedule Proposal. At minimum include: a. Milestones — For each major work component detailed in the Contract Documents and other major work items in correspondence to the Contract Time specified in Article 4.1 of Section 00 42 10 — Proposal including any noted milestones. b. Parallel Activities — Include discussion on potential to use parallel activities both in initial planning to accelerate the schedule to complete the Work in advance of the Milestones and Contract Time noted and during the Project to recover from unplanned events. c. Flexibility — Incorporate the approach to flexibility in scheduling activities including but not limited to the sequence and timing of required shutdowns and cutover. 5. Quality Assurance/Quality Control (QA/QC) - Provide a description of the following: a. Quality Control Plan describing Offeror's quality management program. Explain methods used to interface with City's inspectors and practices used to ensure quality assurance/control during the Project. b. Provide specific examples of how these techniques or procedures were used from any of the projects listed in the Proposal. c. Process for risk management of design of shutdowns, panels, redundancies, HMI/PLC configurations, maintenance of risk register from design through construction. d. Describe what tools the Offeror uses for risk management and how Offeror's quality management team will measure the quality of construction performed by subcontractors and how non -conforming work will be addressed, the methodologies that will enable successful delivery of the project, including any key assumptions, exclusions, constraints, innovations, and opportunities to be realized. e. Demonstrated established, documents and proven quality control procedures and that are enforced by qualified quality control engineer identified as Key Personnel. 6. Project Controls a. Explain the controls that will be utilized to assure timely completion of this Project, including methods for float creation and schedule recovery, if necessary. b. Describe detailed construction cost estimating methods, including historical CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 2 — AD3 0021 15 INSTRUCTIONS TO OFFERORS Page 5 of 22 benchmarking data, that will be used to ensure Proposal price compliance. Safety Protocols a. Discuss key components of Safety Plan. Offeror does not need to submit their Safety Plan prior to award. b. By evaluating the Offeror's safety program, Owner does not endorse or take any responsibility for the effectiveness of the program or any activities to be carried out as part of the program. Subcontractors — List all subcontractors and note their specific roles and in completing the Work, and how each supports the project approach. C. Firm Experience: 1. Demonstrate the team submitted is qualified based on project experience selected from those previously noted in requesting prequalification purposes using the forms included in Section 00 46 12 — Statement of Qualifications. This section shall be narrative in nature using written project descriptions to fully describe the work performed. 2. Demonstrated capacity for training operations and maintenance personnel in SCADA System applications. Specific qualifications, where noted, may be met by the Prime Contractor or a subcontractor. Offerors shall identify the Key Personnel and Subcontractors to demonstrate qualifications. The Offeror shall select and include the following information on 3 to 5 similar ongoing or previous projects from the projects listed in 00 46 12 or additional projects. The projects should best represent the Offeror's ability to meet the required firm qualifications. For each project include: a. Project Name. b. Project Owner. c. Narrative description of the project noting similarity and relevance to the proposed work and lessons learned that would benefit this project. d. List the Key Personnel proposed as part of the Offeror's team who worked on the previous or current project. e. List the Subcontractors proposed as part of the Offeror's team who worked on the previous or current project. f. Provide budget information for each selected project to include: 1) Original Contract Price. 2) Final Contract Cost at Project Closeout. 3) Brief narrative description of cost changes, including those relating to owner enhancement and other conditions beyond the Offeror's control. g. Provide a summary of schedules for each selected project to at minimum include: 1) Original required completion date (end of Contract Time). 2) Actual completion date (end of Contract Time). 3) Brief narrative description of schedule, and how it was setup to achieve project milestones, and staging, as well as identifying changes relating to Owner requested enhancement and other conditions beyond the Offeror's control. h. Provide Contact Reference information for each selected project including: 1) Contact Name for a specific individual that will be available to discuss the project. 2) Listed Contact's Title. 3) Project Owner. CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 2 — AD3 0021 15 INSTRUCTIONS TO OFFERORS Page 6 of 22 4) Email and Phone Number for the Listed Contact. 3. If Offeror is proposing the use of a single subcontractor for over thirty percent (30%) of the work, the submitted projects shall include a minimum of three performed by the Offeror (Prime Contractor) and one (1) performed by that subcontractor. The subcontractor's project shall reflect work as a subcontractor or Prime Contractor and include experience relevant to the portion of the proposed work to be performed as part of the Offeror's team. 4. The required Offeror qualifications include: a. Demonstrated financially soundness based upon audit statement information. b. Ten (10) years of continuous experience in supplying, installing, programming, starting up, and supporting SCADA systems for water or wastewater treatment plants. The relevant experience shall be comparable to City's SCADA System, relative to size, software, and cost. c. Ten (10) years' experience in engineering, technical design, and quality control staff capable of designing and developing design documents, supplying, programming, configuring, implementing, and supporting SCADA System hardware and software, and complying with submittal and training requirements described in the Contract Documents. d. Experience providing pre -construction and construction phase services, including SCADA system architecture design, and control system integration services on and completion of three (3) control systems and SCADA brownfield replacement projects within the past ten (10) years at water or wastewater treatment utilities where each facility had/has greater than 1,000 hardwired I/O and at least one of these facilities had/has a minimum capacity of 5,000 hardwired I/O. Greenfield sites may be included to demonstrate experience in addition to the three (3) projects requested. e. Experience with Inductive Automation software for the SCADA platform, reporting solutions on one or more prior projects. f. Experience with Allen-Bradley PLC hardware and Schneider Electric PLC hardware on one or more prior projects. g. Experience providing pre -construction and construction phase services, including SCADA system architecture design, and control system integration services on two (2) design, construction management or design - build projects within the past ten (10) years at water or wastewater treatment facilities sized at a capacity of 10 million gallons per day (MGD) or greater. h. Local Staffing and Response: 1) Maintain a permanent, fully staffed, and equipped service facility within 300 miles of the project site with full-time employees capable of configuring, deploying, and maintaining the systems specified herein. 2) On -site response within 4 hours of notification starting at two months before scheduled start-up to two months after successful OAD completion. 3) Capable of responding to on -site problems within 12 hours of notice post- OAD. i. Certifications and Licensing (Include copies of all identified certifications and licensing in Section 00 46 12 — Offeror Statement of Qualifications): 1) PLC Platforms: CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 2 — AD3 0021 15 INSTRUCTIONS TO OFFERORS Page 7 of 22 a) Recognized System Integrator with Rockwell Automation, and fully trained on the Rockwell Automation Studio 5000 programming software. b) Recognized member of the Schneider Electric System Integrators Alliance Partner Program, and fully trained on EcoStruxure Control Expert (Unity Pro) programming software. c) Individual programmer certifications: Demonstrate individually completed coursework in Rockwell Automation and Schneider Electric Systems, coding, troubleshooting, and maintaining. 2) Inductive Automation Ignition Integrator Certification: a) Offeror certification: Premier Level. b) Individual programmer certifications: Demonstrate individually completed coursework in Inductive Automation Ignition Vision, Perspective, Reporting & SQL Scripting. j. Employs Control Systems Professional Engineer (P.E.) on a full-time basis. k. Demonstrated ability to provide an organized platform for communication, file distribution, submittal review and approval. 1. Demonstrated ability to use and provide updated construction schedules for the project. m. Possession of a thorough, working knowledge of water treatment processes and control philosophy in accordance with standard practices of the water industry. n. Possession and maintenance of a documented program of correcting deficiencies identified during Operational Availability Demonstration periods, Site Acceptance tests, and post -startup support periods. o. Demonstrated requisite resources of in-house staff, facilities, and finances to complete the project in the schedule specified. D. Key Personnel and Subcontractors 1. Key personnel positions, identified by the City as crucial to the success of the project, are listed below. 2. Formal succession planning, in the form of a backup for Key Personnel, is not required. If backup personnel are identified, and resumes are provided, indicate the backup role of the individual. Qualifications for backup personnel shall be the same as those for the primary key personnel. 3. Resumes shall be limited to two (2) pages for each staff member and incorporate the following information: a. Name. b. Employment identified as either the Prime Contractor or a subcontractor. c. Total years of experience. d. Years of experience with the employer. e. List of similar projects in candidates proposed role within the last ten years. f. Current project assignments including estimated end date(s). g. Education, training, and personal experience in delivering similar projects while serving in the capacity for which they are being proposed. 4. Provide resumes to fulfill the requirements for the following Key Personnel position roles. An individual can fill more than one role with supporting resume, except for the Project Manager, and the Quality Control Design Engineer. Other resumes may be furnished at the discretion of the Offeror. CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 2 — AD3 0021 15 INSTRUCTIONS TO OFFERORS Page 8 of 22 a. Project Manager. b. Quality Control Manager. c. SCADA and Control Systems Design Engineer. d. SCADA Architecture Engineer. e. HMI Systems Programmer. f. PLC Systems Programmer. g. Data Architect. h. Data Analyst. i. Field Testing and Start-up Specialist. j. Cybersecurity Specialist. Personnel Qualifications: a. Project Manager with 5-10 years' experience and three (3) projects in which that person served as the project manager of a water or wastewater capital improvement projects of more than $15 million or SCADA system replacement project with more than 1,000 hardwired I/O is preferred. The Project Manager shall be employed by the Contractor for a minimum of two (2) years. b. Quality Control Manager with 5 years' experience in designing and/or implementing SCADA systems comparable to City's SCADA System, relative to hardware, software, and cost is preferred. c. SCADA and Control Systems Design Engineer with five (5) years' experience in providing SCADA application design, development, and implementation for the water/wastewater industry is preferred. Show experience with at least three (3) projects in which that person served as SCADA System and Control Systems Design Engineer, of which two must be of a water/wastewater facility of at least 10 MGD or 1,000 hardwired I/O. Demonstrated experience shall include, but is not limited to, SCADA system design and programming, control narrative development, code/logic review, high performance graphics design, physical network design; shall be Texas Licensed Professional Engineer and shall be employed by the Contractor for a minimum of one (1) year. d. SCADA Architecture Engineer with five (5) years' experience in providing SCADA application design, development, and implementation for the water/wastewater industry is preferred. Show experience with at least three (3) projects in which that person served as SCADA Architecture Engineer, of which two must be of a facility of at least 10 MGD or 1,000 hardwired VO. Demonstrated experience shall include, but is not limited to, networking testing, pre -design, design, and testing pertaining to Local Area Networks (LAN) and industrial networks for the water/wastewater industry; shall be Texas Licensed Professional Engineer or Certified Cisco Network Administrator (CCNA) or other comparable certification, and shall be employed by the Contractor for a minimum of one (1) year. e. HMI Systems Programmer with five (5) years' experience in providing HMI application programming and implementation is preferred. Show experience with at least three (3) projects in which that person served as HMI Systems Programmer, of which two must be of a water/wastewater facility of at least 10 MGD or 1,000 hardwired I/O. HMI Programmer shall be a demonstrated expert, possess certifications from Induction Automation and demonstrate experience and successful deployment of High - CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 2 — AD3 0021 15 INSTRUCTIONS TO OFFERORS Page 9 of 22 Performance graphics, alarming per ISA 18.2 guidelines, and life -cycle project deployment from HMI design to setup to startup and acceptance in the field. Show experience in HMI application programing, and implementation of visualization, dashboards, and reports within the SCADA environment and from various source data. Shall be employed by the Contractor for a minimum of two (2) years. f. PLC Systems Programmer with five (5) years' experience in providing PLC application programming, factory testing, startup, and implementation with Allen-Bradley and Schneider Electric PLCs in the water industry is preferred. Show experience with at least three (3) projects in which that person served as PLC Systems Programmer, of which two must be of a water/wastewater facility of at least 10 MGD or 1,000 hardwired I/O. PLC Programmer shall have experience with and certifications from the manufacturer for programming Allen-Bradley and/or Schneider Electric PLC systems, Ethernet/IP protocol, Modbus protocol, and OPC-UA, on past projects. Different programmers specialized for Rockwell Automation or Schneider Electric is acceptable. Shall be employed by the Contractor for a minimum of two (2) years. g. Data Architect with five (5) years' experience with SQL Server data warehouse development and management is preferred. Able to show experience with 1 or more projects of similar scale and scope. Experience with database performance tuning, maintenance, query optimization, security, and data modeling are required. h. Data Analyst with five (5) years' experience collecting, cleaning, analyzing data and report creation using inductive automation Ignition software is preferred. Experience with JSON, REST API endpoints, SQL, and Python are required. Shall show experience with 1 or more projects of similar scale and scope. i. Field Testing and Start-up Specialist with five (5) years' demonstrated experience in providing start-up and commissioning services for the water/wastewater industry is preferred. Show experience with at least three (3) projects in which that person served as Field Testing and Start-up Engineer, of which two must be of a water/wastewater facility of at least 10 MGD or 1,000 hardwired 1/0. Shall be employed by the Contractor for a minimum of two (2) years. j. Cybersecurity Specialist with five (5) years' experience in the evaluation and implementation of security measures to protect industrial control systems from cyber threats is preferred. The Cybersecurity Specialist shall have any of the following certifications: 1) A Certified Information System Security Professional (CISSP). 2) Global Industrial Cyber Security Professional (GICSP). 3) Certified SCADA Security Architect (CSSA). 4) Or an equivalent certification. Subcontractor Qualifications: a. The Offeror shall update the submitted list of subcontractors noting the percentage of the Work the Offeror intends to perform with his or her own organization and that to be performed by each subcontractor as noted in Section — 00 46 12 Offeror Statement of Qualifications. CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 2 — AD3 0021 15 INSTRUCTIONS TO OFFERORS Page 10 of 22 7. The City's goal for participation of subconsultants, consultants or other entities certified as Minority-, and/or Women-, owned Business Enterprises (M/WBE) for the project is noted in Section 00 11 15 Notice to Offerors. Procedures and requirements following notification of selection as the Successful Offeror, and for subsequent execution of the Agreement, are identified in Section 00 45 42 — Business Equity Goal and this Section. E. Schedule 1. The purpose of this section is to provide the Offeror's schedule to complete the working including all milestones. Coordinate with the Approach section to provide a corresponding narrative that provides details and supports the time durations and milestones in the schedule. Gantt -style schedules and any information deemed by the Offeror to further demonstrate the approach and Offeror's schedule are acceptable and will be considered during evaluation and scoring. At minimum, the schedule proposal shall include: a. Milestones — As noted by the Offeror in Table 00 42 10 — A Milestones, Offeror Milestones column. b. For each schedule line item, provide Offeror's Days from NTP. F. Cost Proposal 1. The Cost Proposal shall be provided by completing the Proposal Form included in Section 00 42 10 —Proposal. 2. The Proposal shall meet all requirements of Section 00 42 10 —Proposal, including but not limited to presenting all Attachments required by Article 5 Attachments to 3. The information noted in Article 1.4 F. 1. and 2. shall be submitted by entering the cost of each Proposal Item No. into the Bonfire Procurement Portal as noted in Section 00 11 15 Notice to Offerors. 1.5 EVALUATION CRITERIA A. Proposals received from Offerors who are not prequalified at the time proposals shall not be evaluated. Such Proposals if received will be rejected without review. B. The weighted criteria for evaluation and selection of the Contractor for this award will be based upon the factors listed below: CRITERIA WEIGHT 1. Project Approach 10 2. Firm Experience 10 3. Key Personnel & Subcontractors 10 4. Schedule 20 5. Cost Proposal 50 TOTAL 100 CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 2 — AD3 0021 15 INSTRUCTIONS TO OFFERORS Page 11 of 22 C. The City has attempted to provide a comprehensive statement of requirements within the Contract Documents for the work contemplated. Written proposals must present Offeror's qualifications and understanding of the work to be performed, and experience. Offerors are asked to address each evaluation criteria. Proposals must be as thorough and detailed as possible so that the City may properly evaluate capabilities to provide the requested services. D. Each Offeror's submitted Section 00 42 10 — Proposal content, including required Attachments noted in Article 5, will be scored with reference to the evaluation criteria noted. Each Criteria shall be assigned a score of 0 through 100, as noted in Article 1.6 of this Section. The Weight (percentages) noted above will be multiplied by each criteria score, and the results totaled to provide a weighted score. E. Criteria Description: 1. Project Approach — The qualitative scoring of each Offeror's Project Approach will be based on the quality and completeness of the submittal. Scores will be awarded based upon the quality of the narrative including whether it incorporates all required components noted in Paragraph 1.4 B. of this Section. 2. Firm Experience — The qualitative scoring of each Offeror's experience will be based on the projects of similar scope and size submitted in Section 00 46 12 — Offeror Statement of Qualification. 3. Key Personnel & Subcontractors — The qualitative scoring of each Offeror's Key Personnel and Subcontractors submitted in Section 00 46 12 — Offeror Statement of Qualification and will be based on the specific personnel submitted and the completeness of the requested information. 4. Schedule — Offeror shall provide a project schedule that completes the Work within the Contract Time noted in Section 00 42 10 — Proposal, Article 4. Time is of the essence in completing the Work, the Offeror shall note the total number of days required in Section 00 42 10 — Proposal, Article 4.2. The Offeror shall also provide the number of days required for the Work associated with each Milestone identified in Section 00 42 10 — Proposal, Table 00 42 10-A. The quantitative scoring of each Offeror's Proposal Schedule will be evaluated relative to other proposals. Offerors that can complete the work over a shorter duration (fewer days) will receive higher scores. 5. Cost — The quantitative scoring of each Offeror's proposal will be evaluated relative to other proposals. The ranking and relative difference between proposal costs will be considered in scoring. 1.6 EVALUATION AND RANKING METHODOLOGY A. The City reserves the right to reject any or all proposals. B. In evaluating proposals, City will consider the qualifications of each Offeror, and whether or not the Proposals comply with the prescribed requirements as may be requested in the Proposal or prior to the Notice of Award. CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 2 — AD3 0021 15 INSTRUCTIONS TO OFFERORS Page 12 of 22 C. City will consider the qualifications and experience of Offeror, including the Prime Contractor, subcontractors, consultants, suppliers, and other persons and organizations proposed for portions of the Work as presented. The identity of Subcontractors, Suppliers, and other persons and organizations shall be submitted and required by this Section. City also may consider the operating costs, maintenance requirements, performance data, and guarantees of major items of materials and equipment proposed for incorporation in the Work when such data is required to be submitted prior to the Notice of Award. D. By submission of a Proposal, the Offeror acknowledges acceptance of the evaluation process, the evaluation criteria, and all other terms and conditions set forth in this Solicitation. Further, offerors acknowledge and agree that subjective judgements must be made by City during this process. E. City may conduct such investigations as City deems necessary to assist in the evaluation of any Proposal and to establish the responsibility, qualifications, and financial ability of Offerors, proposed Subcontractors, Suppliers and other persons and organizations to perform and furnish the Work in accordance with the Contract Documents to City's satisfaction within the prescribed time. F. Oral Clarifications: The City reserves the right to schedule a day and time during the Evaluation period for a meeting at the Offeror's facility. Offerors shall take note of the narrow time frame identified for Oral Clarifications in the Notice to Offerors. Oral Clarifications, if required, shall be attended by the Offeror's Key Personnel to provide clarifications and any supplemental information that is necessary. The City will provide a list of topics the Offeror should be prepared to address. At this stage, Offeror shall not be allowed to alter or amend their proposals. G. The City will evaluate each proposal using the following methodology: 1. Project Approach will be evaluated on a 100-point scale awarding up to the maximum score noted for each evaluation benchmark. Maximum Evaluation Benchmark Score 40 General Approach Narrative 25 Organizational Chart 15 QA/QC Program 10 Project Controls 10 Safety Program Project approach will be evaluated based on the quality and completeness of the content of the submittal proposal and its compliance with the requirements of this Section. Offerors that fail to meet the minimum requirements stated in this Section will receive a lower scores. 2. Firm Experience will be evaluated on a 100-point scale awarding up to the maximum score noted for each evaluation benchmark. Maximum Evaluation Benchmark Score CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 2 — AD3 0021 15 INSTRUCTIONS TO OFFERORS Page 13 of 22 50 Depth of project experience presented 30 Firm Certifications & Licenses 10 Firm qualifications 10 Firm Local Staffing & Response Depth of experience shall be scored based on the type, number and quality of projects presented in three areas: Control System and SCADA Replacements, Control System and SCADA Replacement experience shall be qualitatively scored using I/O count and relative similarity of system configuration and project components to Work required in the City's SCADA Replacement. Firm Certification & Licenses, Qualifications and Local Staffing & Response will be qualitatively evaluated based on the quality and completeness of the content of the submitted proposal. Offerors that fail to meet the minimum requirements stated in this Section will receive a lower score. Key Personnel & Subcontractors will be evaluated on a 100-point scale, awarding up to the maximum score noted for each evaluation benchmark. Maximum Evaluation Benchmark Score 85 Key Personnel Presented 15 Key Subcontractors Presented Key personnel will be evaluated will be qualitatively evaluated based on the quality and completeness of the resume experience presented, without regard to whether the staff is employed by the Prime Contractor or a listed subcontractor. Offerors that fail to meet the minimum requirements stated in this Section, including but not limited to not identifying Key Personnel, or providing staff with limited experience will receive lower scores. Subcontractor scoring will be limited to qualitatively evaluating the Offeror's proposal content identifying the roll of all subcontractors and suppliers in completing the Work, including the stated approach to meeting the goal noted in Section 00 45 42 — Business Equity Goal. 4. Schedule will be evaluated on a 100-point scale awarding up to the maximum score noted for each evaluation benchmark. Evaluation Benchmark 60 Schedule Level of Detail 40 Contract Time (days) required through Final Acceptance Time is of the essence in completing the Work. The Offeror shall provide a sufficient breakdown of schedule tasks and sub -tasks to display the activities necessary to meet the proposed Contract Time. The Schedule Level of Detail will be qualitatively evaluated based on the quality and completeness of the submitted schedule. Offerors that fail to meet the minimum requirements stated in this Section will receive a lower score. Offerors shall include a level of detail that is sufficient to verify that the Milestones noted by the Offeror in Section 00 42 10 — Proposal, Table 00 42 10-A can realistically CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 2 — AD3 0021 15 INSTRUCTIONS TO OFFERORS Page 14 of 22 be met. Proposals that fail to meet this requirement will receive no points for Schedule Level of Detail. Contract Time (days) will be quantitatively scored relative to all proposal schedules received. The offeror with the lowest number of total days to Final Acceptance will receive 40 points for Contract Time. All other offerors will receive a score based on the ratio of lowest number of days to Final Acceptance proposed by any offeror divided by the Offeror's days to Final Acceptance noted in Article 4.1 of the Section 00 42 10 — Proposal. The score is provided by multiplying the ratio by 40 points. Cost will be evaluated on a 100-point scale awarding up to the maximum score noted for each evaluation benchmark. Evaluation Benchmark 100 1 Total of Base Contract Proposal Items The cost of the proposal will be quantitatively scored relative to all offers received. The lowest Offeror in each Evaluation Benchmark above will receive 100 points. Additional proposals will receive a score based on the ratio of the lowest Total Amount Proposal Items received divided by the Total Amount the Offeror includes in Section 00 42 10 — Proposal, Exhibit A. The score is provided by multiplying the ratio by 100 points. H. After opening the Proposals and within forty-five (45) days of the opening, the City will evaluate and rank each Proposal with respect to the published selection criteria described under this Section. If the City determines that no other clarifying information is required, the evaluation process is complete. The highest-ranking Offeror shall become the Selected Offeror. I. After opening and ranking, the City shall determine which Offeror provides the best value to the City on the basis of the initially submitted Proposal, without discussion or clarification, or the City may discuss elements of the Proposal with the Selected Offeror. Other than the data read at the public opening, the Owner shall not disclose any information included in the Proposals submitted by other Offerors in conducting such discussions. J. If the City determines that it is unable to reach a satisfactory Agreement with the Selected Offeror, the Owner will formally, and in writing, terminate discussions with that Offeror and proceed to the next Offeror based on selection ranking who becomes the new Selected Offeror until a Contract can be negotiated with a Selected Offeror or all Proposals have been rejected. K. Reference Checks: The City reserves the right to check any reference(s), regardless of the source of the reference information. Information may be requested and evaluated from references. The City reserves the right to use a third party to conduct reference checks. City may perform reference checks on any or all Offeror references. CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 2 — AD3 0021 15 INSTRUCTIONS TO OFFERORS Page 15 of 22 L. In addition to Offeror's relevant prequalification requirements, City may consider the qualifications and experience of Subcontractors, Suppliers, and other persons and organizations proposed for those portions of the Work where the identity of such Subcontractors, Suppliers, and other persons and organizations must be submitted as provided in the Contract Documents or upon the request of the City. City also may consider the operating costs, maintenance requirements, performance data and guarantees of major items of materials and equipment proposed for incorporation in the Work when such data is required to be submitted prior to the Notice of Award. M. Optional (Alternative) project components proposed by the Offeror: 1. Modifications of the Proposal, as noted in Paragraph 1.4 E of this Section, is prohibited. 2. Offerors desiring consideration of alternatives that require a change to the Contract Documents shall submit a question prior to the deadline noted in Section 00 11 15 — Notice to Offerors noting the Contract Document changes required to allow the alternative. If such changes are acceptable to the City an addendum will be issued to all Prequalification Offerors. N. Evaluation and Ranking: Following the Proposal evaluations, compiling of the final ranking, and negotiations with Selected Offeror are completed, then the Evaluation Committee will provide award recommendation to the City. The City will in turn, issue an Intent to Award Notification to the Selected Offeror which, in the City's opinion, has submitted the proposal representing the best value to the City. 1.7 EXAMINATION OF PROPOSAL AND CONTRACT DOCUMENTS, OTHER RELATED DATA, AND SITE A. Before submitting a Proposal each Offeror: 1. Shall examine and carefully study the Contract Documents and other related data identified including "technical data" referred to in this Section. No information given by City or any representative of the City other than that contained in the Contract Documents and officially promulgated addenda thereto, shall be binding upon the City. 2. Shall attend the Pre -Proposal Site Visit. Due to security concerns, and the number and locations of sites accessed, and the sequence, will be limited and selected by the City in advance. The intent is to visit all WTPs to the extent possible and to limit the site visits to two calendar days. However, the City reserves the right to alter this prior to or during the site visit. Each prequalified Offeror shall select up to two (2) attendees to attend the site visit. Each Offeror shall send the names of the attendees to the City's Project Manager via email, a minimum of 48-hours in advance of the site visit. 3. Shall consider federal, state, and local Laws and Regulations that may affect cost, progress, performance or furnishing of the Work. 4. Shall study all: drawings of physical conditions relating to the work at the Site that have been identified in the Contract Documents as containing reliable "technical data." CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 2 — AD3 0021 15 INSTRUCTIONS TO OFFERORS Page 16 of 22 5. Is advised that the Contract Documents on file with the City shall constitute all of the information which the City will furnish. All additional information and data which the City will supply after promulgation of the formal Contract Documents shall be issued in the form of written addenda and shall become part of the Contract Documents just as though such addenda were actually written into the original Contract Documents. No information given by the City other than that contained in the Contract Documents and officially promulgated addenda thereto, shall be binding upon the City. 6. Should perform independent research, investigations, tests, borings, and such other means as may be necessary to gain a complete knowledge of the conditions which will be encountered during the construction of the project. For projects with restricted access, upon request, City may provide each Offeror access to the site to conduct such examinations, investigations, explorations, tests, and studies as each Offeror deems necessary for submission of a Proposal. Offeror must fill all holes and clean up and restore the site to its former conditions upon completion of such explorations, investigations, tests and studies. 7. Shall determine the difficulties of the Work and all attending circumstances affecting the cost of doing the Work, time required for its completion, and obtain all information required to make a proposal. Offerors shall rely exclusively and solely upon their own estimates, investigation, research, tests, explorations, and other data which are necessary for full and complete information upon which the proposal is to be based. It is understood that the submission of a proposal or proposal is prima - facie evidence that the Offeror has made the investigations, examinations and tests herein required. 8. Shall promptly notify City of all conflicts, errors, ambiguities, or discrepancies in or between the Contract Documents and such other related documents. The Contractor shall not take advantage of any gross error or omission in the Contract Documents, and the City shall be permitted to make such corrections or interpretations as may be deemed necessary for fulfillment of the intent of the Contract Documents. B. Reference is made to Section 00 73 00 — Supplementary Conditions for identification of: 1. Copies of such reports and drawings will be made available by City to all prequalified offerors. Those reports and drawings may not be part of the Contract Documents, but the "technical data" contained therein upon which Offeror is entitled to rely as provided in Paragraph 4.02. of the General Conditions has been identified and established in Paragraph SC 4.02 of the Supplementary Conditions. Offeror is responsible for any interpretation or conclusion drawn from any "technical data" or any other data, interpretations, opinions, or information. 2. Standard insurance requirements, coverages, and limits. C. The submission of a Proposal will constitute an incontrovertible representation by Offeror: (i) that Offeror has complied with every requirement of this Article, (ii) that without exception the Proposal is premised upon performing and furnishing the Work required by the Contract Documents and applying the specific means, methods, techniques, sequences or procedures of construction (if any) that may be shown or indicated or expressly required by the Contract Documents, (iii) that Offeror has given City written notice of all conflicts, errors, ambiguities and discrepancies in the Contract Documents and the written resolutions thereof by City are acceptable to Offeror, and when said conflicts, etc., have not been resolved through the interpretations by City as described in Paragraph 6., and (iv) that the Contract Documents are generally sufficient CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 2 — AD3 0021 15 INSTRUCTIONS TO OFFERORS Page 17 of 22 to indicate and convey understanding of all terms and conditions for performing and furnishing the Work. D. The provisions of this Article, inclusive, do not apply to Asbestos, Polychlorinated biphenyls (PCBs), Petroleum, Hazardous Waste or Radioactive Material covered by Paragraph 4.06. of the General Conditions, unless specifically identified in the Contract Documents. 1.8 AVAILABILITY OF LANDS FOR WORK, ETC. A. The lands upon which the Work is to be performed, rights -of -way and easements for access thereto and other lands designated for use by Contractor in performing the Work are identified in the Contract Documents. The lands required are within existing City owned facilities. All additional lands and access thereto required for temporary construction facilities, construction equipment or storage of materials and equipment to be incorporated in the Work are to be obtained and paid for by Contractor. Easements for permanent structures or permanent changes in existing facilities are to be obtained and paid for by City unless otherwise provided in the Contract Documents. B. Outstanding right-of-way, easements, and/or permits to be acquired by the City are listed in Paragraph SC 4.01 of the Supplementary Conditions. In the event the necessary right- of-way, easements, and/or permits are not obtained, the City reserves the right to cancel the award of contract at any time before the Offeror begins any construction work on the project. C. The Offeror shall be prepared to commence construction without all executed right-of- way, easements, and/or permits, and shall submit a schedule to the City of how construction will proceed in the other areas of the project that do not require permits and/or easements. 1.9 INTERPRETATIONS AND ADDENDA A. All questions about the meaning or intent of the Contract Documents are to be directed to City in writing on or before the deadline for questions noted in Section 00 11 15 — Notice to Offerors. Questions received after the published date and time may not be responded to. Interpretations or clarifications considered necessary by City in response to such questions will be issued by Addenda delivered to all parties recorded by City as having received the Contract Documents. Only questions answered by formal written Addenda will be binding. Oral and other interpretations or clarifications will be without legal effect. Address all questions to the City under the respective Project via the Procurement Portal: htWs:Hfortworthtexas.bonfirehub.com/portal/?tab=openOj2portunities B. Addenda may also be issued to modify the Contract Documents as deemed advisable by City. C. Addenda or clarifications may be posted via the City's electronic document management and collaboration system. Clarifications, via addenda, will be posted under the respective Project via the Procurement Portal: htt Ds:Hfortworthtexas.bonfirehub.com/portal/?tab=oDenODDortunities CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 2 — AD3 0021 15 INSTRUCTIONS TO OFFERORS Page 18 of 22 D. A pre -submittal conference with pre -qualified Offerors may be held at the time and place indicated in the Advertisement or Invitation to Offerors. Representatives of City will be present to discuss the Project. Offerors are encouraged to attend and participate in the conference. City will transmit to all prospective Offerors of record such Addenda as City considers necessary in response to questions arising at the conference. Oral statements may not be relied upon and will not be binding or legally effective. 1.10 PROPOSAL SECURITY A. Each Proposal must be accompanied by a Proposal Bond made payable to City in an amount of five (5) percent of Offeror's maximum Proposal price, on the form attached or equivalent, issued by a surety meeting the requirements of Paragraph 5.01 of the General Conditions. B. The Proposal Bond provided by an Offeror will be retained until the conditions of the Notice of Award have been satisfied. If the Successful Offeror fails to execute and return the Contract Documents within 14 days after the Notice of Award conveying same, City may consider Offeror to be in default, rescind the Notice of Award and act on the Proposal Bond. Such action shall be City's exclusive remedy in the event Offeror is deemed to have defaulted. 1.11 PERFORMANCE BONDING A. Offerors shall note that the Work may be bonded in phases in accordance with the Section 00 72 00 — General Conditions as modified by Section 00 73 00 Supplementary Conditions SC-5.02 A. 1.12 CONTRACT TIMES A. The number of days within which, or the dates by which, Milestones are to be achieved in accordance with the General Requirements and the Work is to be completed and ready for Final Acceptance is set forth in Section 00 52 45 — Agreement or incorporated therein by reference to Section 00 42 10 — Proposal. 1.13 LIQUIDATED DAMAGES A. Provisions for liquidated damages are set forth in the Agreement. 1.14 SUBSTITUTE AND "OR -EQUAL" ITEMS A. The Contract, if awarded, will be on the basis of materials and equipment described in the Contract Documents without consideration of possible substitute or "or -equal" items. Whenever it is indicated or specified in the Contract Documents that a "substitute" or "or -equal" item of material or equipment may be furnished or used by Contractor if acceptable to City, application for such acceptance will not be considered by City until after the Effective Date of the Agreement. The procedure for submission of any such application by Contractor and consideration by City is set forth in Paragraphs 6.05A., 6.05B. and 6.05C. of the General Conditions and is supplemented in Section 01 25 00 of the General Requirements. CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 2 — AD3 0 0021 15 INSTRUCTIONS TO OFFERORS Page 19 of 22 1.15 SUBCONTRACTORS, SUPPLIERS AND OTHERS A. In accordance with the City's Business Equity Ordinance No. 24534-11-2020 the City has goals for the participation of minority business and/or women business enterprises in City contracts $100,000 or greater. See Section 00 45 42 — Business Equity Goal for the M/WBE Project Goals and additional requirements. Failure to comply shall render the Offeror as non -responsive. Business Equity Ordinance No. 24534-11-2020, as amended, codified at: httt)s:Hcodelibrarv.amle2al.com/codes/ftworth/latest/ftworth tx/0-0-0-22593 B. No Contractor shall be required to employ any Subcontractor, Supplier, other person, or organization against whom Contractor has reasonable objection. 1.16 PROPOSAL FORM A. The Proposal Form is included with the Contract Documents; additional copies may be obtained from the City. B. All blanks on the Proposal Form must be completed and the Proposal Form signed in ink. Erasures or alterations shall be initialed in ink by the person signing the Proposal Form. A price shall be indicated for each listed Proposal Form Item, Alternative Item, and Unit Price Item listed therein. The Proposal does not include optional alternatives, the words "No Bid," "No Change," or "Not Applicable" shall not be entered. Offeror shall state the prices for which the Offeror proposes to do the work contemplated or furnish materials required. All entries shall be legible. C. Proposals by corporations shall be executed in the corporate name by the president or a vice-president or other corporate officer accompanied by evidence of authority to sign. The corporate seal shall be affixed. The corporate address and state of incorporation shall be shown below the signature. D. Proposals by partnerships shall be executed in the partnership name and signed by a partner, whose title must appear under the signature accompanied by evidence of authority to sign. The official address of the partnership shall be shown below the signature. E. Proposals by limited liability companies shall be executed in the name of the firm by a member and accompanied by evidence of authority to sign. The state of formation of the firm and the official address of the firm shall be shown. F. Proposals by individuals shall show the Offeror's name and official address. G. Proposals by joint ventures shall be executed by each joint venture in the manner indicated on the Proposal Form. The official address of the joint venture shall be shown. H. All names shall be typed or printed in ink below the signature. I. The Proposal shall contain an acknowledgement of receipt of all addenda, by initialing -( Y next to each addendum received in the area provided in Section 00 42 10 Proposal. CITY OF FORT WORTH March 21, 2024 SCADA System Replacement 103086 ATTACHMENT 2 — AD3 0021 15 INSTRUCTIONS TO OFFERORS Page 20 of 22 J. Postal and e-mail addresses and telephone number for communications regarding the Proposal shall be shown. K. Evidence of authority to conduct business as a Nonresident Offeror in the state of Texas shall be provided in accordance with Section 00 43 37 — Vendor Compliance to State Law Non -Resident Offeror. 1.17 SUBMISSION OF PROPOSALS A. Proposals shall be submitted electronically as prescribed in Section 00 11 15 — Notice to Offerors. 1.18 WITHDRAWAL OF PROPOSALS A. Proposals addressed to the Project Manager and filed with the City may be withdrawn prior to the time set for proposal opening. A request for withdrawal must be made in writing and delivered to the City's Project Manager prior to the opening of Proposals. A timely withdrawn proposal will be returned to the Offeror. If the withdrawal request is received prior to the deadline noted in Section 00 1115 — Notice to Offerors for Proposal Due Date, the Proposal will not be read aloud and will thereafter be returned unopened. B. In the event any Proposal for which a withdrawal request has been timely filed has been inadvertently opened, said Proposal and any record thereof will subsequently be marked "Withdrawn" and will be given no further consideration for the award of contract. 1.19 OPENING OF PROPOSALS A. Proposals will be received, publicly opened and the names of offerors and total monetary proposal cost read aloud publicly. 1.20 PROPOSALS TO REMAIN SUBJECT TO ACCEPTANCE A. All Proposals will remain subject to acceptance for a minimum of 90 days, or the time period specified for Notice of Award and execution and delivery of a complete Agreement by Successful Offeror. City may, at City's sole discretion, release any Proposal and nullify the Proposal security prior to that date. 1.21 AWARD OF CONTRACT A. City reserves the right to reject any or all Proposals, including without limitation the rights to reject any or all nonconforming, nonresponsive, unbalanced, or conditional Proposals and to reject the Proposal of any Offeror if City believes that it would not be in the best interest of the Project to make an award to that Offeror. City reserves the right to waive informalities not involving price, contract time or changes in the Work and award a contract to such Offeror. Discrepancies between the multiplication of units of Work and unit prices will be resolved in favor of the unit prices. Discrepancies between the indicated sum of any column of figures and the correct sum thereof will be resolved in favor of the correct sum. Discrepancies between words and figures will be resolved in favor of the words. CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 2 — AD3 0021 15 INSTRUCTIONS TO OFFERORS Page 21 of 22 B. Any or all proposals will be rejected if City has reason to believe that collusion exists among the Offerors, Offeror is an interested parry to any litigation against City, City or Offeror may have a claim against the other or be engaged in litigation, Offeror is in arrears on any existing contract or has defaulted on a previous contract, Offeror has performed a prior contract in an unsatisfactory manner, or Offeror has uncompleted work which in the judgment of the City will prevent or hinder the prompt completion of additional work if awarded. C. If the Contract is to be awarded, it will be awarded to responsible and responsive Offeror whose evaluation by City as described above in this Section indicates that the award will be in the best interests of the City. D. The Proposals will be evaluated by the City in consultation with the City's project team and Evaluation Committee using procurement procedures that conform to Texas Government Code Chapter 2269. If a Contract is awarded, it will be awarded to the offeror submitting the best value to the City. The City is not bound to accept the lowest priced Cost Proposal if that Cost Proposal is judged not to be the best value for the City, as solely determined by the City. E. Pursuant to Texas Government Code Chapter 2252.001, the City will not award contract to a Nonresident Offeror unless the Nonresident Offeror's proposal is lower than the lowest proposal submitted by a responsible Texas Offeror by the same amount that a Texas resident offeror would be required to price the proposal of a Nonresident Offeror to obtain a comparable contract in the state in which the nonresident's principal place of business is located. F. A contract is not awarded until formal City Council authorization. If the Contract is to be awarded, City will award the Contract within 90 days after the day of the Proposal opening unless extended in writing. No other act of City or others will constitute acceptance of a Proposal. Upon the contract award, a Notice of Award will be issued by the City. G. The Offeror is required to fill out and sign the Certificate of Interested Parties Form 1295 and the form must be submitted to the Project Manager before the contract will be presented to the City Council. The form can be obtained at httvs://www.ethics.state.tx.us/data/forms/1295/1295.vdf H. Failure or refusal to comply with the requirements of this Section may result in rejection of Proposal. 1.22 SIGNING OF AGREEMENT A. When City issues a Notice of Award to the Successful Offeror, it will be accompanied by the required number of unsigned counterparts of the Contract Documents. Within 14 days thereafter, Contractor shall sign and deliver to the City the executed Agreement and required number of counterparts (Attachments) in accordance with Article 5.1.A.2 of Section — 00 52 45 Agreement. The counterparts include the required Bonds, Certificates of Insurance, and all other required documentation as noted in in Section 00 52 45 — Agreement. CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 2 — AD3 0021 15 INSTRUCTIONS TO OFFERORS Page 22 of 22 B. City shall thereafter deliver one fully signed counterpart to Contractor. PART 2 — PRODUCTS (NOT USED) PART 3 — EXECUTION (NOT USED) ++END OF SECTION++ CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 2 — AD3 0023 13-1 NON -DISCLOSURE AGREEMENT Page 1 of 4 City Secretary Contract No. SECTION 00 23 13 NON -DISCLOSURE AGREEMENT This Non -Disclosure Agreement ("Agreement") is made and entered by and between the City of Fort Worth, a home rule municipality organized under the laws of the State of Texas (the "City"), and the Offeror , referenced herein as "Vendor". In connection with the consideration, evaluation and/or implementation of a potentially beneficial business relationship (the "Transaction") between the parties to this Agreement, City wishes to disclose to Vendor information relating to the Transaction which may consist of confidential and proprietary information. 1. Definition of Confidential Information. "Confidential Information" shall mean any of the following information notwithstanding its form (tangible, visual, oral, electronic, etc.): (a) documents, files, studies, reports, test results, brochures, offering materials, computer output and other materials and information relating to the Transaction and all analyses, compilations, forecasts, projections and other documents prepared based upon such materials and information and all proposals made in connections with the Transaction; (b) trade secrets; (c) discoveries, ideas, concepts, techniques and know-how; (d) performance or process data; (e) costing and financial information; (0 strategic, marketing and business plans; (g) any information identified or designated as "confidential," "private," or "proprietary" (or similar terms); (h) any information which by its nature can be reasonably construed as requiring confidential treatment; (i) contracts and contractual relationships; and 0) any of the foregoing relating to City's customers or clients, including the identity of such customers and clients. Vendor agrees that title to and ownership of the Confidential Information shall remain with City or the third parry which owns it, and Vendor does not acquire any rights in the Confidential Information disclosed to it under this Agreement, except the limited right to use the Confidential Information as set forth in this Agreement. 2. Confidentiality Obligations. Vendor shall (a) protect the Confidential Information with the same degree of care Vendor employs for the protection of its own confidential and proprietary information of a similar nature, but not less than commercially reasonable care; (b) limit its use of Confidential Information for the purpose of the Transaction, and not otherwise use it for its own benefit or the benefit of others, and shall not reverse engineer any Confidential Information; (c) limit access to Confidential Information to only those of its employees, consultants, agents or representatives (and not to competitors of City) who (i) have a need to know such information to accomplish the purpose of the Transaction, and (ii) have been advised by instruction, agreement or otherwise of the confidential nature of, and the duties toward, the Confidential Information; (d) not duplicate or reproduce Confidential Information other than for purposes of the Transaction unless authorized to do so in writing (all such reproductions shall be considered Confidential Information); (e) not remove, overprint or deface any notice of copyright, trademark, logo or other proprietary notices or notices of confidentiality from any originals or copies of the Confidential Information; and (f) upon termination or expiration of this Agreement return all Confidential Information to City promptly upon written request or, at Discloser's option, provide written certification of the destruction thereof (with the understanding that any destruction of documents will be subject to applicable laws and regulations governing the Vendor's records retention policy); provided, however, that Vendor CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 0023 13-1 NON -DISCLOSURE AGREEMENT Page 2 of 4 may retain one (1) archival copy of the Confidential Information, subject to the provisions of this Agreement, for the sole purpose of monitoring compliance with this Agreement. 3. Exceptions to Confidentiality Obliaations. The obligations under this Agreement shall not apply to any information that: (a) is in the public domain at the time of disclosure or subsequently enters the public domain without breach of this Agreement; (b) is already known to City at the time of disclosure, as shown by its written records; (c) becomes known to Vendor from a source other than City without breach of this Agreement or any other valid confidentiality obligations; (d) is independently developed by Vendor without use of the Confidential Information, as shown by its written records; or (e) is required to be disclosed to comply with applicable laws or regulations, or with a court or administrative order, provided that City receives sufficient prior written notice of such intended disclosure such that it may seek reasonable legal remedies to obtain confidential treatment for such Confidential Information. 4. Term. This Agreement shall apply only to Confidential Information disclosed during the term of this Agreement, which term shall be one (1) year following the Effective Date unless otherwise extended by the mutual, written agreement of the parties. Either party, however, may terminate this Agreement upon ten (10) days' prior written notice. Upon any such termination or expiration of this Agreement, Vendor shall comply with the provisions of Section 1 hereof concerning the disposition of Confidential Information. Vendor's obligations under this Agreement shall survive any termination or expiration of this Agreement for a period of six (6) years from the date of any such termination or expiration. 5. Publicity. Except as required by law, Vendor shall not use the name of City or reveal the existence or substance of ongoing discussions, negotiations or evaluations related to the subject matter of this Agreement or any subsequently executed agreement to any third parry without the prior written consent of City. Notwithstanding the foregoing, both parties understand and agree that under the Texas Public Information Act, this Agreement is a public document and that a copy of this Agreement (but not copies of Confidential Information provided hereunder) will be available online to members of the public who undertake a search for it utilizing the search tools for public information on the City's website. 6. Limited Purpose. This Agreement is limited in purpose to the protection of the Confidential Information and shall not be construed otherwise as a teaming agreement, joint venture or any other contractual relationship. No license under any intellectual property of any kind is granted or implied by disclosure of Confidential Information hereunder. However, neither party shall be precluded hereby from performing its own independent work. Nothing in the Agreement obligates either party to enter into any transaction whatsoever; and each party shall bear all of its own costs and expenses 7. Representations and Warranties. City represents and warrants that it has the unqualified right to transmit and otherwise disclose the Confidential Information under this Agreement. Vendor acknowledges that City has not made any representation or warranty as to the accuracy or completeness of the confidential information, and that the confidential information is being provided on an "as is" basis. City shall have no liability to Vendor resulting from the use of the Confidential Information except to the extent subsequently set forth in any agreement that may hereafter be executed between the parties resulting from the Transaction 8. Governina Law and Venue. This Agreement and its terms shall be governed by and construed in accordance with the laws of the State of Texas, without giving effect to CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 0023 13-1 NON -DISCLOSURE AGREEMENT Page 3 of 4 principles of choice of law. Both parties agree to submit to the jurisdiction of the State of Texas to resolve any disputes regarding the interpretation, enforcement or subject matter of this Agreement. Venue for any action hereunder shall lie in state courts located in Tarrant County, Texas. 9. Remedies for Breach. Vendor agrees that a breach or violation of this Agreement may cause City irreparable harm. In the event of any breach or violation hereof by Vendor, as the exclusive remedy hereunder, City shall be entitled to seek temporary and permanent injunctive relief and other equitable relief without the necessity of posting a bond or making any undertaking in connection therewith. 10. Severability, Notices. In the event that any provision of this Agreement shall be held invalid or unenforceable for any reason, that provision shall be ineffective to the extent of such invalidity or unenforceability, and such invalidity or unenforceability shall not affect any other provision of this Agreement. If necessary, the parties shall negotiate in good faith to modify the Agreement to preserve (to the extent possible) their original intent. All notices that either party is required or may desire to give the other party under this Agreement shall be given by addressing the communication to the address set forth above, and may be given by certified, registered or express mail, postage prepaid, or shall be sent by facsimile or email transmission or overnight carrier (provided evidence of receipt can be verified). Such notices shall be deemed given on the date of receipt (or refusal) of delivery of said notice. Either party may designate a different address for receipt of notices upon written notice to the other parry. 11. Entire Understanding; Amendment. This Agreement contains the entire understanding between the parties, superseding all prior or contemporaneous communications, agreements and understandings between the parties with respect to the exchange and protection of Confidential Information. No modification, extension or waiver of any provision hereof or any release of any rights hereunder shall be valid unless expressed in a writing signed by an authorized representative of each party. The provisions and conditions of this Agreement are solely for the benefit of the City and Vendor and are not intended to create any rights, contractual or otherwise, for the benefit of any other person or entity. This Agreement may not be assigned by Vendor without the prior written consent of City. Failure to enforce any term of this Agreement will not waive any rights hereunder. The parties may execute this Agreement in two or more counterparts (which may be delivered by facsimile), each of which will be deemed an original and all of which together shall constitute a single agreement. 12. Governmental Powers. By execution of this Agreement, the City does not waive or surrender any of its governmental powers or immunities. (signature page follows) CITY OF FORT WORTH March 21, 2024 SCADA System Replacement 103086 0023 13-1 NON -DISCLOSURE AGREEMENT Page 4 of 4 ACCEPTED AND AGREED: CITY: City of Fort Worth Contract Compliance Manager: By signing I acknowledge that I am the person responsible for the monitoring and administration of this contract, including By: ensuring all performance and reporting Name: requirements. Title: Assistant City Manager Date: By: Approval Recommended: Name: Title: Approved as to Form and Legality: By: Name: Title: By: Attest: Name: Title: Assistant City Attorney Contract Authorization: By: Name: M&C: N/A Title: City Secretary 1295: N/A OFFEROR AS VENDOR: By: Name: Title: Date: ++END OF SECTION++ CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 CONFLICT OF INTEREST AFFIDAVIT Page 1 of 2 SECTION 00 35 13 CONFLICT OF 1N1 EREST AFFIDAVIT Each bidder, offeror or respondent ( hereinafter referred to as " You") to a City of Fort Worth procurement may be required to complete a Conflict of interest Questionnaire ( the attached CIQ Form) and/ or a Local Government Officer Conflicts Disclosure Statement ( the attached CIS Form) pursuant to state law. You are urged to consult with counsel regarding the applicability of these forms to your company. The referenced fonns may be downloaded from the links provided below. ]tttns:rf tiV-u,Nk,.ellucs.state.tx.us/data/ forms/conflict/CIO.ndf htti)s://ww4N,.ethics-state.tx.us/dat,ij'f4iniis, conllict/ClS.pdf V CIQ Form does not apply ❑ CIQ Form is on file with City Secretary ❑ CIQ Form is being provided to the City Secretary / CIS �I-417onn does not apply ❑ CIS Form is on File with City Secretary ❑ CIS Form is being provided to the City Secretary OFFEROR: Remont Engineering & Design Group, Company LLC d/b/a "RED Group" By Kyle J. Remont (Please Print) Address: 3850 N. Causeway Blvd Signature; �a� �/ L/ 2 02- Y v CitylState/Zip Metairie, LA 70002 Title: President & Manager (Please Phut) END OF SECTION CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103096 110 1 Page CONFLICT OF INTEREST AFFIDAVIT Page 2 of 2 ++THIS PAGE INTENTIONALLY LEFT BLANK++ CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 111 1 Page 0042 10 PROPOSAL Page 1 of 8 SECTION 00 42 10 PROPOSAL ARTICLE 1. ENTER INTO AGREEMENT The undersigned Offeror proposes and agrees, if this Competitive Sealed Proposal is accepted, to enter into an Agreement with City to perform and furnish all Work as specified or indicated in the Contract Documents for the Contract Price and within the Contract Time indicated in this Proposal and in accordance with the other terms and conditions of the Contract Documents with execution of the Agreement in the form included in the Section 00 52 45 — Agreement. ARTICLE 2. OFFEROR ACKNOWLEDGEMENTS AND CERTIFICATION 2.1 In submitting this Competitive Sealed Proposal, Offeror accepts all of the terms and conditions of the Section 00 11 15 — Notice to Offerors and Section 00 21 15 — Instructions to Offerors, including without limitation those dealing with the disposition of Section 00 43 15 — Proposal Surety (Bid Bond). 2.2 Offeror is aware of all costs to provide the required insurance, will do so pending contract award, and will provide a valid insurance certificate meeting all requirements within 14 days of notification of award. 2.3 Offeror certifies that this Competitive Sealed Proposal is genuine and not made in the interest of or on behalf of any undisclosed individual or entity and is not submitted in conformity with any collusive agreement or rules of any group, association, organization, or corporation directly or indirectly induced or solicited any other Offeror to submit a false or sham Proposal. 2.4 Offeror has not solicited or induced any individual or entity to refrain from submitting a Competitive Sealed Proposal. 2.5 Offeror has not engaged in corrupt, fraudulent, collusive, or coercive practices in competing for the Contract. For the purposes of this Paragraph: a. "Corrupt practice" means the offering, giving, receiving, or soliciting of anything of value likely to influence the action of a public official in the proposal process. b. "Fraudulent practice" means an intentional misrepresentation of facts made (a) to influence the proposal process to the detriment of City (b) to establish prices at artificial non-competitive levels, or (c) to deprive City of the benefits of free and open competition. c. "Collusive practice" means a scheme or arrangement between two or more Offerors, with or without the knowledge of City, a purpose of which is to establish prices at artificial, non-competitive levels. d. "Coercive practice" means harming or threatening to harm, directly or indirectly, persons or their property to influence their participation in the bidding process or affect the execution of the Contract. CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 2 — AD8 100 1 Page 0042 10 PROPOSAL Page 2 of 8 2.6 Assurance of no Substitution — The Offeror in submitting the proposal provides written assurance that Key Personnel including key subcontractors, suppliers, materials, and equipment listed in Section 00 46 12 — Offeror Statement of Qualifications will be performing, furnishing or be used in the work and will not be substituted without written permission from the City. Offeror may include succession planning in the form of an alternate for key personnel should the staff listed become unavailable for reasons outside the control of the offeror. Written notification to the City is required prior to any staffing change. Substitution of alternate staff due to the Offerors ongoing for future commitments to other projects is prohibited. ARTICLE 3. PREOUALIFICATION The Offeror acknowledges that requirement to prequalify as an Offeror (Contractor) for the proposed work in accordance with procedures noted in Section 00 21 15 — Instructions to Offerors. ARTICLE 4. TIME OF COMPLETION 4.1 The Work shall be completed for Final Acceptance within a maximum of 1440 days after the date when the Contract Times commence to run as provided in Paragraph 2.02 of the General Conditions. The schedule provided by the Offeror shall meet the City's intent to have Project Components completed by no later than the Milestones noted in TABLE 00 42 10-A. The Milestone Days allowed for completion of each Project Component shall be measured as Contract Time commenced to run as provided in Paragraph 2.02 of the General Conditions. Prior to execution the Contract Time, noted as days shall be listed in Section 00 52 45 — Agreement, Article 4 as the lesser of the days above or 1382days to Final Acceptance based on the Offerors submitted schedule. 4.2 Time is of the essence in completing the Work, the Offeror shall submit a schedule that completes the Work within the Milestone days noted in TABLE 00 42 10-A and the maximum days noted in Article 4.1 above. The Offeror shall note the number of days required to complete portions of the Work identified with each Milestone based on the submitted schedule. 4.3 Based on the submitted schedule the Offeror shall note the number of days required to complete the Work associated with each Milestone identified in Table 00 42 10-A in the column labelled "Offeror Milestone." Where the number of days noted by the Offeror under "Offeror Milestone" is less, the Work associated with that Milestone shall be Substantially Complete, as noted in Section 00 52 45 — Agreement Article 4, within the reduced duration provided by the Offeror under "Offeror Milestone". 4.4 Project Components are described in Article 4.6 of this Section. Work not described as part of a Project Component or not necessary to achieve the Project Component completion is not subject to a Milestone and shall be completed within the Project Time for Final Acceptance noted in Article 4.1 of this Section. While portions of the Work within each component may meet the requirements of Article 14.04 of the General Conditions for Partial Utilization by the City, a Milestone is not satisfied until all included Work has been completed. CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 2 — AD8 101 1 Page 0042 10 PROPOSAL Page 3 of 8 4.5 Project Components that encompass Proposal Items that require the Contractor to continue maintenance of the included Work through Final Acceptance are considered to be complete when Contractor has completed all non -maintenance portions of the Work, including Punch List items provided by the City. TABLE 00 42 10-A SCHEDULE REQUIREMENTS PROJECT COMPONENT MILESTONE OFFEROR (days) MILESTONE (days) Milestone 1: SCADA System Architecture 220 185 Complete Milestone 2: OAD Complete — 1st WTP 550 499 Plant Complete Milestone 3: OADs Complete — All WTPs 1360 1261 4.6 The Work associated with each Project Component is defined in Section 0122 13 — Measurement & Payment, Article 1.4 — Proposal Items Basis of Payment. Project Component Milestones are listed below: a. Milestone 1— SCADA System Architecture Design Complete. This Milestone will be met when the SCADA System Architecture Design is Final and complete, providing the City information necessary to procure all necessary SCADA network components. b. Milestone 2 — OAD Complete —1 WTP Plant. This Milestone will be met when the Operational Availability Demonstration (OAD) has been completed for 1 plant. Achievement of this milestone indicates all necessary Work to be performed to perform the OAD for 1 WTP as outlined in Division 0, 1 and 40 is complete. c. Milestone 3 — OAD Complete — All WTP Plants. This Milestone will be met when the Operational Availability Demonstration (OAD) has been completed for all 5 plants. Achievement of this milestone indicates all necessary Work to be performed to perform all of the OADs for the WTPs as outlined in Division 0, 1 and 40 is complete. d. Final Acceptance — All Work. Final Acceptance will be met as defined in the General and Supplemental conditions, and when all preceding Milestones have been met and all remaining work has been completed. Major activities that are to be completed between Milestone 3 and Final Acceptance shall include the Operational Availability Demonstration (OAD) for the Centralized SCADA System. 4.7 Offeror accepts the provisions of the Agreement as to liquidated damages in the event of failure to complete the Work by achieving Final Acceptance within the Contract Time specified in the Agreement. CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 2 — AD8 102 1 Page 0042 10 PROPOSAL Page 4 of 8 ARTICLE 5. ATTACHMENTS TO THIS OFFER 5.1 The Offeror acknowledges that the attachments listed below are required for the Proposal: a. Proposal Approach Narrative as noted in the Section 00 21 15 — Instructions to Offerors. b. This Proposal Form, Section 00 42 10 — Proposal. c. Exhibit A to this Proposal Form attached immediately following the words "END OF SECTION" and the following forms. d. Section 00 35 13 — Conflict of Interest Affidavit Statement, if necessary, CIQ or CIS forms shall be downloaded by the Offeror and provided directly to City Secretary. e. Section 00 46 12 — Offeror Statement of Qualification. f. Section 00 43 15 — Proposal Surety (Bid Bond) issued by a surety meeting the requirements of Paragraph 5.01 of the General Conditions. g. Section 00 43 37 — Vendor Compliance to State Law Non -Resident Offeror. h. Section 00 45 26 — Contractor Compliance with Worker's Compensation Law. i. MWBE Forms noted in Section 00 45 42 — Business Equity CSP, submittal is optional at time of submittal. j. Section 00 46 12 — Offeror Statement of Qualifications, in accordance with Section 00 21 15 — Instructions to Offerors. k. Evidence of Authority to Sign as noted in Article 7. ARTICLE 6. BASIS OF OFFER 6.1 Offeror acknowledges receipt of all addenda by initialing below in the applicable areas provided prior to the words END OF SECTION. 6.2 Offeror will complete the Work for the prices entered in the Bonfire Procurement Portal for each Proposal Item shown in Exhibit A of this Proposal Form. Where allowance items are presented with a BOLD fixed amount the Offeror shall enter the same cost that is noted in Exhibit A. The attached Exbibit A, immediately following the words END OF SECTION, shall be considered part of this Section. 6.3 It is understood and agreed by the Offeror in signing this proposal that the total price will be calculated by the Bonfire Procurement Portal, then verified by the Offeror and that any allowance amounts manually entered by the Offeror are subject modification by the City in the event that the amount entered is not identical to that shown in Exhibit A of this Proposal Form. Such corrections are limited to changing the allowance amount or amounts to that required by Exhibit A and updating the total amount to reflect any corrections. 6.4 It is understood and agreed by the Offeror in signing this proposal that following correction of the total amount, if necessary based on modification by the City under Article 6.3, the Offeror agrees that the individual amounts for each Proposal entered into the Bonfire Procurement Portal and the total amount shall be incorporated into Exhibit A by the City to complete the Cost Proposal. The total amount with any corrections shall also be incorporated into Article 3 of Section 00 52 45 — Agreement as the Contract Price. CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 2 — AD8 103 1 Page 0042 10 PROPOSAL Page 5 of 8 6.5 It is understood and agreed by the Offeror in signing this proposal that the Contract Price, as established above, is NOT subject to adjustment following completion of the preconstruction services described as part of the Work. 6.6 It is understood that and agreed by the Offeror in signing this proposal that an M/WBE goal identified in Section 00 45 42 — Business Equity Goal CSP has been set for the Project and agrees to comply with the intent of the City Business Equity Ordinance and provide the forms of documentation noted. ARTICLE 7. GENERAL INSTRUCTIONS 7.1 All blanks must be filled as unfilled blanks may result in the Proposal being disqualified. 7.2 The Proposal Form shall be signed in ink. Proposals by corporations shall be executed in the corporate name by the president or a vice-president or other corporate officer accompanied by evidence of authority to sign. The corporate seal shall be affixed. The corporate address and state of incorporation shall be shown below the signature. 7.3 Proposals by partnerships shall be executed in the partnership name and signed by a partner, whose title must appear under the signature accompanied by evidence of authority to sign. The official address of the partnership shall be shown below the signature. 7.4 Proposals by limited liability companies shall be executed in the name of the Prime Contractor by a member and accompanied by evidence of authority to sign for the entity. The state of formation of the Prime Contractor entity and the official address of the firm shall be shown. 7.5 Proposals by individuals shall show the Offeror's name and official address. 7.6 Proposals by joint ventures shall be executed by each joint venture in the manner indicated on the Proposal Form. The official address of the joint venture shall be shown. 7.7 All signatures shall include names either typed or printed in ink below the signature. 7.8 Erasures or alterations shall be initialed in ink by the person signing the Proposal Form. A price shall be indicated for each listed Proposal Form Item, Alternative Item, and Unit Price Item listed therein. 7.9 The Offeror shall state the prices for which the Offeror proposes to do the work contemplated or furnish materials required. All entries shall be legible. 7.10 A Proposal showing omissions, alterations, conditions, exceptions, or other qualifiers which modify the Proposal Form will be rejected. 7.11 Pricing shall represent the Stipulated Price for completing all work, materials, equipment, and other incidentals required to complete the project in accordance with Contract Documents. 7.12 The City will consider the Offeror's proposed Cost Proposal for completion of the project in determining best value to the Owner. CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 2 — AD8 104 1 Page 7.13 Postal and e-mail addresses and telephone number for communiez regarding the Proposal shall be shown. ARTICLE S. OFFER SUBMITTAL This Proposal is submitted on June 13th 2024 by the entity named below. Month Day Year The Offeror hereby submits this Proposal as set forth in this Section: Offeror. Remont Engineering & Design Group. LLC dlbla "RED Group" .._ . F1sped ur pr'inted naune crfnrgwrr_-atrurt) By: Natne Title (individual s signature) — Kyle J. Remont: Member of Remont Holdings LLC, Member of RED Group hyped ar' printed) President & Manager of RED Group typed or printed) Date. June lim, LUL4 (typed or printed) toidder is a corporation, a partnership, or a joint venture, attach evidence of authority to sign.. Attest k, �/ G. s signattrrel Name: Jacob M Mattix. IV ay1W or prinfew Title: Director, Business Development, RED Group tn,ped or primedl Date: June 13th, 2024 rr_i,ped ur printed) By initialing below, receipt is acknowledged of the foitowing Addenda. F4 tddenduttl No. I k, j r :. Addeedutn No. 6 Addendum No. 2 Addendum No. 7 <_ - Addendum No. 3 . ? ; Addendwn No & Addendum No 4 �` - Addendump No 9 Addendum No. S k �, , t I Addendum No 10 CITY OF r ORr Wr}RTtt March 21. 2024 Sr- 4U.A S%stenl Raplacenzl.� 10308F. ATTACHMENT 2 — ADS 105 1 Page A Address for giving notices: 3850 N. Causeway Blvd, Suite 1255 Metairie, LA 70002 Bidder's Contact: Name: Jake Mattix (typed or printed) Title: Director, Business Development (typed or printed) Phone: 504-723-7518 Email: jmattix@red.group Address: 3850 N. Causeway Blvd, Suite 1255 Metairie, LA 70002 Bidder's Contractor License No.: (if applicable) 46139 ++END OF SECTION++ CITY OF FORT WORTH March 21, 2024 0042 10 PROPOSAL Page 7 of 8 SCADA System Replacement 103086 ATTACHMENT 2 — AD8 106 1 Page ++++ THIS PAGE INTENTIONALLY LEFT BLANK.... CITY OF FORT WORTH March 21, 2024 0042 10 PROPOSAL Page 8 of 8 SCADA System Replacement 103086 ATTACHMENT 2 — AD8 107 1 Page 00 42 10 PROPOSAL EXHIBIT A Primary Responses Success: All data is valid! Numeric DecisionStatus Bid/No Bid Proposal J Unit of Measure Quantity Unit Price Total Cost Bid Proposal (00 42 43) (BT-89LW) Success: All values provided Bid #1-1 Mobilization, Limited to 2 Percent of Total LS 1 $ 160,000.00 $ 160,000.00 Amount Success: All values provided Bid #1-2 Familiarization and Preliminary Assessment LS 1 $ 988,377.00 $ 988,377.00 Success: All values provided Bid #1-3 Design LS 1 $ 744,845.00 $ 744,845.00 Success: All values provided Bid #1-4 Eagle Mountain WTP Configuration, Cutover and LS 1 $ 1,163,934.00 $ 1,163,934.00 Startup Success: All values provided Bid #1-5 South Holly WTP Configuration, Cutover and LS 1 $ 1,055,776.00 $ 1,055,776.00 Startup Success: All values provided Bid #1-6 North Holly WTP Configuration, Cutover and LS 1 $ 1,034,098.00 $ 1,034,098.00 Startup Success: All values provided Bid #1-7 Westside WTP Configuration, Cutover and LS 1 $ 1,000,616.00 $ 1,000,616.00 Startup Success: All values provided Bid #1-8 Rolling Hills WTP Configuration, Cutover and LS 1 $ 1,305,699.00 $ 1,305,699.00 Startup Success: All values provided Bid #1-9 Centralized SCADA Configuration, Cutover and LS 1 $ 480,491.00 $ 480,491.00 Startup Allowance: $75,000.00 for Additional Success: All values provided Bid #1-10 Familiarization, Preliminary Assessment and LS 1 $ 75,000.00 $ 75,000.00 Design Services (must enter $75,000.00 in the unit price) Allowance: $75,000.00 for Procurement of Success: All values provided Bid #1-11 Additional Hardware and Software (must enter LS 1 $ 75,000.00 $ 75,000.00 $75,000.00 in the unit price) Allowance: $75,000.00 for Additional Success: All values provided Bid #1-12 Configuration, Cutover and Startup Services LS 1 $ 75,000.00 $ 75,000.00 (must enter $75,000.00 in the unit price) Allowance: $75,000.00 for Additional Data Success: All values provided Bid #1-13 Warehouse / Data Base Programming Services LS 1 $ 75,000.00 $ 75,000.00 (must enter $75,000.00 in the unit price) Basket Total M $ 8,233,836.00 $ 8,233,836.00 CITY OF FORT WORTH SCADA SYSTEM REPLACEMENT OCTOBER 21, 2024 103086 ++THIS PAGE INTENTIONALLY LEFT BLANK++ CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 0043 15 PROPOSAL SURETY (13113 BOND) Page I oft SECTION 00 43 15 PROPOSAL SURETY (BID BOND) KNOW ALL BY THESE PRESENTS: That we, Offeror, herein after called "Principal" Remont Engineering & Design Group, LLC dlbla RED Group Offeror Company Name 3850 N. Causeway Blvd., Suite 1255, Metairie, LA 70002 Offeror Mailing Address (Principal Place of Business) and City of Fort Worth, Texas herein after called "Obligee" Fill in Ch)i's preferred address 200 Texas Street Fort Worth, Texas 76102 Fill in City's preferred address zip code and Surety SureTec Insurance Company Insurance Underwriters, Ltd. Surety Cornpatry Name Srarty Local Agent Company Name 2103 CityWest Boulevard, Suite 1300, Houston, TX 77042 Jeffrey E. Kropp Surety Mailing Address (Principal Place of Business) Local Agent Contact Name 2103 CityWest Boulevard, Suite 1300, Houston, TX 77042 3625 N. 1-10 Service Rd W, Suite 200, Metairie, LA 70002 Surety Physical Address (Principal Place of Business) Address (Principal Place of Business) 713-812-0800/866-732-0099 504-883-2500 Telephone (Main) /Telephone (Claims) Telephone (A dm) Texas Surety s .Siaie of lncoi poration By submitting this bond, Surety affirms it is authorized to do business and licensed to execute bonds in the State of Texas. WHEREAS, the Principal has submitted a proposal to perform work for the following project of the Obligee, identified as: Enter Project Name SCADA System Replacement for the Water Department CITY OF FORT WORTH March 21, 2024 SCADA System Replacement 103086 113 1 Page 0043 15 PROPOSAL SURETY (BID BOND) Page 2 of 2 NOW, THEREFORE, Surety and Obligee, intending to be legally bound by this bond, do each cause this bond to be duly executed on its behalf by its authorized officer, agent, or representative. The Principal and Surety bind themselves, and their heirs, administrators, executors, successors, and assigns, jointly and severally to this bond. The condition of this obligation is such that if Obligee accepts Offeror's Proposal and Offeror delivers the executed Agreement and the required bonds within the time stipulated in the Contract Documents this obligation is null and void. Payment under this bond will be due and payable upon default by Offeror and within 30 days after receipt by Offeror and Suretti of written notice of default from Obligee. Venue lies exclusively in Tarrant County, Texas for any legal action. SIGNED Offeror, as Principal this 13th day of June , 20 24 By Offeror, as Principal Remont Engineering & Design Group, LLC dlbla RED Group / Kyle J. Remont, President/Manager Signature, Name (Printed) and Title of Principal ''zBy:Sure(y SureTec Insurance Company ,- Catherine R. Froeba, Attorney -In -Fact Signatur Name (Printed) and Title nfAttorneY -of-Fact) *Attach Power of Attorney (Surety) for Attorney -in -Fact +END OF SECTION++ CITY OF FORT WORTH March 21. 2024 Impressed Surety Sea only SCADA System Replacement 103086 114 1 Page P0A# 1810032 JOINT LIMITED POWER OF ATTORNEY KNOW ALL MEN BY THESE PRESENTS: That SureTec Insurance Company, a Corporation duly organized and existing under the laws of the State of Texas and having its principal office in the County of Harris, Texas and Markel Insurance Company (the "Company"), a corporation duly organized and existing under the laws of the state of Illinois, and having its principal administrative office in Glen Allen, Virginia, does by these presents make, constitute and appoint: Catherine R. Froeba, Jack T. Landry, William H. Ellsworth, Laura Burns, Jeffrey E. Kropp, Jill K. Tucker Their true and lawful agent(s) and attorneys) -in -fact, each in their separate capacity if more than one is named above, to make, execute, seal and deliver for and on their own behalf, individually as a surety or Jointly, as co -sureties, and as their act and deed any and all bonds and other undertaking In suretyship provided, however, that the penal sum of any one such instrument executed hereunder shall not exceed the sum of: Fifty Million and 00/100 Dollars ($50,000,000.00) This Power of Attorney Is granted and is signed and sealed under and by the authority of the following Resolutions adopted by the Board of Directors of SureTec Insurance Company and Markel Insurance Company: 'RESOLVED, That the President, any Senior Vice President, Vice President, Assistant Vice President, Secretary, Assistant Secretary, Treasurer or Assistant Treasurer and each of them hereby is authorized to execute powers of attorney, and such authority can be executed by use of facsimile signature, which may be attested or acknowledged by any officer or attorney, of the company, qualifying the attorney or attorneys named in the given power of attorney, to execute in behalf of, and acknowledge as the act and deed of the SureTec Insurance Company and Markel Insurance Company, as the case may be, all bond undertakings and contracts of suretyship, and to affix the corporate seal thereto." IN WITNESS WHEREOF, Markel Insurance Company and SureTec Insurance Company have caused their official seal to be hereunto affixed and these presents to be signed by their duly authorized officers on the 27th day of January , 2023 , SureTec Insurance Company 6-,yRAA/CF �sssgutRANcq. WunX •'a Od StL r[rU��da�L�a a w SEAL v= By' , � d `'/ %,may ••xi9 '' Y ` Michael C. Kelmig, President '+i,`��rrl*tuHiss•`` State of Texas County of Harris: rance ftpmpany a President On this 27th day of January , 2023 A. D., before me, a Notary Public of the State of Texas, in and for the County of Harris, duly commissioned and qualified, came THE ABOVE OFFICERS OF THE COMPANIES, to me personally known to be the Individuals and officers described in, who executed the preceding instrument, and they acknowledged the execution of same, and being by me duly sworn, disposed and said that they are the officers of the said companies aforesaid, and that the seals affixed to the proceeding instrument are the Corporate Seals of said Companies, and the said Corporate Seals and their signatures as officers were duly affixed and subscribed to the said instrument by the authority and direction of the said companies, and that Resolutions adopted by the Board of Directors of said Companies referred to In the preceding instrument Is now in force. IN TESTIMONY WHEREOF, I have hereunto set my hand, and affixed my Official Seal at the County of Harris, the day and yearfirst above written, Notary E. MCCV�RY Nata Public State of Texas B : t1 y Commission # 12947680-5 , J le E. McClar Notary Public Y Y Cominission Expires March 29, 2026 y commission expires 3/29/2026 We, the undersigned Officers of SureTec Insurance Company and Markel Insurance Company do herby certify that the original POWER OF ATTORNEY of which the foregoing Is a full, true and correct copy is still In full force and effect and has not been revoked. IN WITNESS WHEREOF, we have hereunto set our hands, and affixed the Seals of said Companies, on the 13th day of .tune 1 2024 ur sura Company M. Br nt Beaty, A�istant Secretary Markel Insurance Company BRM. As Lsnt Any Instrument Issued in excess of the peanalty stated above Is totally void and without any validity. 1010032 For verification of the authority of this Power yorf may call (713)812-0800 on any business day between 8= AM and 5:00 PM CST. 15 1 Page 00 43 37 VENDOR COMPLIANCE TO STATE LAW NON-RESIDENT BIDDER Page[ aI72 SECTION 00 43 37 VENDOR COMPLIANCE TO STATE LAW NON-RESIDENT BIDDER Texas Government Code Chapter 2252 was adopted for the award of contracts to nonresident bidders. This law provides that, in order to be awarded a contract as low bidder, nonresident bidders (out-of-state contractors whose corporate offices or principal place of business are outside the State of Texas) bid projects for construction, improvements, supplies or services in Texas at an amount lower than the lowest Texas resident bidder by the same amount that a Texas resident bidder would be required to underbid a nonresident bidder in order to obtain a comparable contract in the State which the nonresident's principal place of business is located. The appropriate blanks in Section A must be filled out by all nonresident bidders in order for your bid to meet specifications. The failure of nonresident bidders to do so will automatically disqualify that bidder. Resident bidders must check the box in Section B. Louisiana A. Nonresident bidders in the State of _°__.__ _.. __"....; . , our principal place of business, are required to be percent lower than resident bidders by State Law. A copy of the statute is attached. 0.01 Nonresident bidders in the State of State Here or Blank , our principal place of business, are not required to underbid resident bidders. B. The principal place of business of our company or our parent company or majority owner is in the State of Texas. ❑ BIDDER: �.uiuyauy i+aiucc ai�ii' Remont Engineering & Design Group, LLC d/bla "RED Group" 3850 N. Causeway Blvd, Suite 1255 Metairie. LA 70002 +-FEND OF SECTION++ CITY OF FORT WORTH March 21, 2024 Kyle J. Remont By: 1\',.1�'.i 11 _1 rw (Signature) Title: -444io ii@@@ President & Manager Date: June 13th, 2024 SCADA System Replacement 103086 16 1 Page 0043 37 VENDOR COMPLIANCE TO STATE LAW NON-RESIDENT BIDDER Page 2 of ++THIS PAGE INTENTIONALLY LEFT BLANK++ CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 17 1 Page 00 45 26 CONTRACTOR COMPLIANCE WITH WORKER'S COMPENSATION LAW Pagel of 2 SECTION 00 45 26 CONTRACTOR COMPLIANCE WITH WORKER'S COMPENSATION LAW Pursuant to Texas Labor Code Section 406.096(a), as amended, Contractor certifies that it provides worker's compensation insurance coverage for all of its employees employed on City Project No. 103086 Contractor further certifies that, pursuant to Texas Labor Code, Section 406.096(b), as amended, it will provide to City its subcontractor's certificates of compliance with worker's compensation coverage. CONTRACTOR: Remont Engineering & Design Group, LLC d/b/a "RED Group" By. Kyle J. Remont Company (Please Print) 3850 N. Causeway Blvd, Suite 1255 Signature: Q"o&d Address Metairie, LA 70002 City/State/Zip 06/12/2024 THE STATE OF TEXAS § COUNTY OF T�i��CT�`i § Title: President / Manager (Please Print) BEFORE ME, the undersigned authority, on this day personally appeared Kyle James Remont , known to me to be the person whose name is subscribed to the foregoing instrument, and acknowledged to me that he/she executed the same as the act and deed of Remont Engineering & Design Group, LLC for the purposes and consideration therein expressed and in the capacity therein stated. GIVEN UNDER MY HAND AND SEAL OF OFFICE this 12 day of June 2024 /pdpfll9q�1 � �\\ Marvin Coleman ID NUMBER 132766675 COMMISSION EXPIRES November 5, 2024 CITY OF FORT WORTH March 21, 2024 64~— Marvin Coleman Notary Public in and for the State of Texas Electronically signed and notarized online using the Proof platform. ++END OF SECTION++ SCADA System Replacement 103086 121 1 Page 00 45 26 CONTRACTOR COMPLIANCE WITH WORKER'S COMPENSATION LAW Page 2 of 2 ++THIS PAGE INTENTIONALLY LEFT BLANK++ CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 122 1 Page 00 45 42 BUSINESS EQUITY GOAL CSP Page 1 of 2 SECTION 00 45 42 BUSINESS EQUITY GOAL CSP APPLICATION OF POLICY If the total dollar value of the contract is $100,000 or more, then a Business Equity goal is applicable. A Business Equity Firm refers to certified Minority-, and/or Women-, owned Business Enterprises (M/WBEs). POLICY STATEMENT It is the policy of the City of Fort Worth to ensure the full and equitable participation of Business Equity Firms when applicable, in the procurement of all goods and services. All requirements and regulations stated in the City's Business Equity Ordinance No.25165-10-2021, (replacing Ordinance No. 24534-11- 2020 (codified at: httDs://codelibrarv.amle2al.com/codes/ftworth/latest/ftworth_tx/0-0-0-22593) apply to this bid. BUSINESS EOUITY PROJECT GOAL The City's Business Equity goal on this project is 5% of the total bid value of the contract (Base bid applies to Parks and Community Services). METHODS TO COMPLY WITH THE GOAL On City contracts where a Business Equity Goal is applied, offerors are required to comply with the City's Business Equity Ordinance by meeting or exceeding the above stated goal or otherwise comply with the ordinance through one of the following methods: 1. Commercially useful services performed by a Business Equity prime contractor, 2. Business Equity subcontracting participation, 3. Combination of Business Equity prime services and Business Equity subcontracting participation, 4. Business Equity Joint Venture/Mentor-Prot6g6 participation, 5. Good Faith Effort documentation, or 6. Prime contractor Waiver documentation. SUBMITTAL OF REOUIRED DOCUMENTATION Applicable documents (listed below) must be received by the Purchasing Division, OR the offeror shall EMAIL the Business Equity documentation to the assigned City of Fort Worth Project Manager or Department Designee. Documents are to be received no later than 2:00 p.m., on the third City business day after the proposal opening date, exclusive of the proposal opening date. Refer to Section 00 1115 Notice to Offerors for notification procedures. The Offeror must submit one or more of the following documents: 1. Utilization Form and Letter(s) of Intent, if the goal is met or exceeded; 2. Good Faith Effort Form and Utilization Form, including supporting documentation, if participation is less than stated goal, or no Business Equity participation is accomplished; 3. Prime Contractor Waiver Form, including supporting documentation, if the Offeror will perform all subcontracting/supplier opportunities; or 4. Joint Venture/Mentor-Prot6g6 Form, if goal is met or exceeded with a Joint Venture or Mentor- Prot6g6 participation. CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 3 — AD8 00 45 42 BUSINESS EQUITY GOAL CSP Page 2 of 2 These forms can be found at: Business Equity Utilization Form and Letter of Intent httDs://apes.fortworthtexas.Rov/ProiectResources/ResourcesP/60 - MWBE/Business Equity Utilization Form DVIN 2022 220324.pdf Letter of Intent https://apps.fortworthtexas.Rov/ProiectResources/ResourcesP/60 - MWBE/Letter of Intent_DVIN 202 Lvdf Business Equity Good Faith Effort Form httos://apps.fortworthtexas.2ov/Pro_iectResources/ResourcesP/60 - MWBE/Good Faith Effort Form DVIN2022.pdf Business Equity Prime Contractor Waiver Form httos://apps.fortworthtexas.2ov/Pro_iectResources/ResourcesP/60 - MWBE/MWBE Prime Contractor Waiver-220313.pdf Business Equity Joint Venture Form httos://apps.fortworthtexas.2ov/Pro_iectResources/ResourcesP/60 - MWBE/MWBE Joint Venture 220225.Ddf FAILURE TO ACHIEVE THE GOAL OR OTHERWISE COMPLY WITH THE ORDINANCE WILL RESULT IN THE BIDDER/OFFEROR BEING DECLARED NON -RESPONSIVE AND THE BID REJECTED. FAILURE TO SUBMIT THE REOUIRED BUSINESS EOUTY DOCUMENTATION OR OTHERWISE COMPLY WITH THE ORDINANCE WILL RESULT IN THE BID BEING DECLARED NON -RESPONSIVE, THE BID REJECTED AND MAY SUBJECT THE BIDDER/OFFEROR TO SANCTIONS AS DESCRIBED IN SEC. 20-373 OF THE ORDINANCE. For Questions, Please Contact The Business Equity Division of the Department of Diversity and Inclusion at (817) 392-2674. ++END OF SECTION++ CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 3 — AD8 00 46 12 OFFEROR STATEMENT OF QUALIFICATIONS Page 1 of 2 SECTION 00 46 12 OFFEROR STATEMENT OF QUALIFICATIONS ARTICLE 1— GENERAL 1.1 BASIS OF DOCUMENT A. This document is a MODIFIED version of EJCDC® C-451, Copyright© 2013 by the National Society of Professional Engineers, American Council of Engineering Companies, and American Society of Civil Engineers, or is based in part on excerpts from copyrighted EJCDC documents. All rights reserved. Those portions of the text that originated in copyrighted EJCDC documents remain subject to the copyright. ARTICLE 2 — REQUIREMENTS FOR THE QUALIFICATION STATEMENT 2.1 REQUIREMENTS FOR THE OFFEROR STATEMENT OF QUALIFICATIONS A. The Offeror's Qualifications Statement shall be provided to the City by all interested entities for the purpose of pre -qualifying as an Offeror. Prequalified Offers shall incorporate a copy of the submittal with the Proposal. 1. Failure to submit the required information in the Qualifications Statement may result in the City denying prequalification. Proposals from Offers who are not prequalified will be considered non -responsive and will not be opened by the City. 2. Offerors may be required to provide supplemental information if requested by the City to clarify, enhance, or supplement the information provided in the Qualifications Statement. B. For the Offerors' Proposal to be considered responsive the completed Proposal Documents must provide the information requested in this Section using the forms supplied. C. The Qualifications Statement Form on the pages immediately following the words END OF SECTION shall be considered part of this Section. a. Will not be considered or evaluated as a substitute for the information specifically requested. b. Additional information shall be incorporated into ATTACHMENT F to the Statement of Qualification Form. ARTICLE 3 — REQUIREMENTS FOR THE OUALIFICATION STATEMENT 3.1 INSTRUCTIONS FOR THE OFFEROR STATEMENT OF QUALIFICATIONS A. General Instructions 1. Provide the information requested in this form completely and in detail. 2. Failure to include the information completely and clearly may result in lower scores in the evaluations. 3. The Offeror shall insert additional rows within a table where insufficient space is provided. This includes but is not limited to the number of Business Contacts, CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 00 46 12 OFFEROR STATEMENT OF QUALIFICATIONS Page 2 of 2 Joint Venturers, Businesses Owned, and Business Partners where the rows provided do not provide room for all parties to be listed. 4. ATTACHMENT C and ATTACHMENT D pages may be duplicated, and additional sheets incorporated by the Offeror as necessary to fully detail project experience. 5. Offeror shall include the required Attachments note in Section 8 of the Form. 6. Offerors may elect to provide additional information beyond the specific requirements of this Section such as organizational brochures or other marketing information that in the opinion of the Offeror assists in demonstrating qualifications. ++END OF SECTION++ CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 1. QUALIFICATIONS STATEMENT FORM GENERAL INFORMATION A. Provide the Offeror's contact information for the Business: Offeror Legal Name of Business: IRemont Engineering & Design Group, LLC d/b/a "RED Group" Corporate Office Name: Kyle J Remont Title: President & Manager Business address of corporate office: Local Office Name: Cesar Lossa Title: Manager, PMO Business address of local office Phone number: 504-729-5086 Email address: kremont@red.group 3850 N Causeway Blvd, Suite 1255 Metairie, LA 70002 Phone number: 713-701-7945 Email address: Glossa@red.group 825 Town & Country, Ln, Suite 1200 Houston, TX 77024 Website Address I www.red.group B. Provide information on the Business's organizational structure: Form of Business: ❑ Sole Proprietorship ❑ Partnership ❑ Corporation Limited Liability Company ❑ Joint Venture comprised of the following companies: 1. N/A 2. N/A 3. N/A Date Business was formed: 4/6/2006 State in which Business was formed: LA m Is this Business authorized to operate in the Project location? Yes ❑ No ❑ Pending If YES, provide certificate of authorization to conduct business in the State of Texas in ATTACH M ENT A. If the Business is a Joint Venture provide the separate Qualification Statement Form for each Joint Venturer in ATTACHMENT B. Incorporate information for each Venturer using ATTACHMENT C, tabular forms for projects currently under contract; and ATTACHMENT D, tabular forms for projects completed within those attachment sections respectively. Include forms for each Venturer and note the name of the Venturer at the top of each page under "Name of Organization." C. Identify all businesses that own Business in whole or in part (25% or greater), or that are wholly or partly (25% or greater) owned by Business: Name of business: Remont Holdings LLC I Affiliation: I Member (Owner) Address: Name of business: RYJAX, LLC Affiliation: Member (Owner) Address: Name of business: Affiliation: Address: D. Provide contact information regarding the Business's officers, partners, and respective limits of authority. Name: I Kyle Remont Title: I President & Manager Authorized to sign contracts: /Yes ❑ No Limit of Authority: I $ NIA Name: I Carl Fangue Title: I CEO Authorized to sign contracts: 1IYe5 ❑ No Limit of Authority: I $ NIA Name: I Jake Mattix Title: I Director, Business Development Authorized to sign contracts: 6/yes ❑ No Limit of Authority: I $ NIA Name: I Title: I 2. LICENSING & CERTIFICATION A. Provide the following information and provide a copy of the associated license or certificate in Attachment F: Name: RED Group Ignition Certified Integrator — Level: Gold (Pursuing Premier) Agency or Certifier: Inductive Automation ( RED Group )* License (No. or N/A): NIA Expiration (Date or N/A): I NIA * Note in parentheses the name of the business entity that holds certification. The certification may be held by the Prime Contractor or a subcontractor. B. Submittal of additional certifications and licensing is not required for Prequalification but can be provided by the Offeror. If provided, include copies of the Business' Licenses and Certificates in ATTACHMENT F. C. When submitting a Proposal, the Offeror shall provide additional certification and licenses held to demonstrate whether the Offeror's team meets one or more of the licensing and certification qualifications noted in Section OD 21 15 — Instructions to Offerors. Provide any associated certificates and licenses in ATTACHMENT F. 3 4. SAFETY A. Provide information regarding Business's safety organization and safety performance. List all certifications, such as ISO 45001 or other business safety certifications noted in the Contract Documents, add additional rows as necessary. Submittal of Certificates are not required for Prequalification or Proposal submittal; however, they may be provided atthe option of the Offeror. If provided include Certificates in ATTACHMENT F. If the business holds no formal safety certifications note "NONE" in the form below. Name of Business's Safety Officer: Safety Certifications Certification Name RAYS+ Participant UL508A & UL698A Derek ❑iMartino Issuing Agency Expiration ISNetworld N/A Underwriters Laboratories 12/31/2024 B. Provide Worker's Compensation Insurance Experience Modification Rate (EMR), Total Recordable Frequency Rate (TRFR) for incidents, and Total Number of Recorded Manhours (MH) forthe last 3 years and the EMR, TRFR, and MH history forthe last 3 years of the Business and any proposed Subcontractor(s) that will provide Work valued at 10% or more of the Contract Price. Provide documentation in ATTACHMENT F of the EMR historyforthe Business and Subcantractor(s) in the form of an EMR letter from the Insurer for each Company listed. Year 2023 2022 2021 Company EMR TRFR I MH EMR TRFR I MH EMR TRFR MH RED Group FI NANCIAL A. Provide information regarding the Business's financial stability. Provide the most recent audited financial statement, and if such audited financial statement is not current, also provide the most current financial statement. Provide an audited balance sheet for each of the last 3 years in ATTACHMENT F. Financial Institution: Business address: Date of Business's most recent financial statement: 3/3112024 VAttached Date of Business's most recent audited financial statement: 12/31/2023 VAttached Financial indicators from the most recent financial statement Contractor's, Current Ratio (Current Assets — Current Liabilities) IN 5 A B. C. 6. A. Contractor's Quick Ratio ((Cash and Cash Equivalents + Accounts Receivable + I� Short Term Investments) Current Liabilities) SURETY INFORMATION Provide information regarding the surety company that will issue required bonds on behalf of the Business, including but not limited to performance and payment bonds. Surety Name: I SureTec Insurance Company Surety is a corporation organized and existing under the laws of the state of: I Texas Is surety authorized to provide surety bonds in the Project location? I /Yes ❑ No Is surety listed in "Companies Holding Certificates of Authority as Acceptable Sureties on Federal Bonds and as Acceptable Reinsuring Companies" published in Department Circular 570 (as amended) by the Bureau of the Fiscal Service, U.S. Department of the Treasury? es ❑ No Mailing Address 2103 CityWest Boulevard, Suite 1300 (principal place of business): Houston, TX 77042 Physical Address 2103 CityWest Boulevard, Suite 1300 (principal place of business): Houston, TX 77042 Phone (main): 1713-812-0800 I Phone (claims): I866-732-0099 Provide the Business's Aggregate Bonding Capacity: Provide the Business's Available Bonding Capacity as of date of this submittal: INSURANCE Provide information regarding Business's insurance campany(s), including but not limited to its Commercial General Liability carrier. Provide information for each provider. Name of insurance provider, and type of policy (CLE, auto, etc.): Insurance Provider Type of Policy (Coverage Provided) PartnerRe Insurance Solutions Bermuda Ltd. General Liability, Auto, Umbrella Hamilton Insurance DAC American Interstate Insurance Houston Casualty Company Underwriters at Lloyds / Lloyds of London Travelers Umbrella (2nd Layer) Workers Compensation Professional Liability Umbrella of PL, 1 st, & 2nd / Property Employment Practices Liability Hudson Excess Insurance Co Cyber Are providers licensed or authorized to issue policies in the Project location? VYes ❑ No Does provider have an A.M. Best Rating of A-VII or better? &(Yes ❑ No Mailing Address I Wellesly House South 90 Pitts Bay Road (principal place of business): Pembroke HM 08, Bermuda Physical Address Welfesly House South 90 Pitts Bay Road (principal place of business): Pembroke HM08, Bermuda Phone (main): I441-292-6888 I Phone (claims): I877-647-7996 7. CONSTRUCTION EXPERIENCE A. Provide information that will identify the overall size and capacity of the Business. Average number of current full-time employees: Estimate of revenue for the current year: Estimate of revenue for the previous year: B. Provide information regarding the Business's previous contracting experience. Years of experience with projects like the proposed project: As a general contractor: 11 Asa joint venturer: Has the Business, or a predecessor in interest, or an affiliate identified in Section 1 Been disqualified as a bidder or barred from contracting by any local, state, or federal agency within the last 5 years? ❑ Yes fi/No Been released from a bid in the past 5 years? ❑ Yes VNo Defaulted on a project or failed to complete any contract awarded to it? ❑ Yes S/No Refused to construct or refused to provide materials defined in the contract documents or in a change order? ❑ Yesl/No Been a party to any resolved litigation in the preceding 5 years or currently pending litigation or arbitration? ❑ Yes VNo For joint Ventures provide the above information, including answers to each question, separately for each Venturer. Copy the above form rows and note the Venturer entity's name before this and each added section. Provide full details in ATTACHMENT F if the response to any of the above questions is Yes. C. List ALL projects currently under contract in ATTACHMENT C and provide indicated information. D. List a minimum of three and a maximum of six projects completed in the last 10 years in ATTACHMENT D and provide indicated information to demonstrate the Business's experience with projects similar in type and cost of construction. E. Provide resume information on key individuals whom Business intends to assign to the Project in ATTACHMENT E as noted in Section 00 2115 — Instructions to Offerors. 1) Project Manager 2) Quality Control Manager 3) SCADA and Control Systems Design Engineer 4) SCADA Architecture Engineer 5) HMI Systems Programmer 6) PLC Systems Programmer 7) Data Architect 8) Data Analyst 9) Field Testing and Start-up Specialist 10) Cybersecurity Specialist F. ATTACHMENT F provide the following documents: 1) Include the following in ATTACHMENT F: a. List of Subcontractors including the approximate percentage of the Work the Offeror anticipates each will perform. b. Copies of the Business' licenses and certifications as noted in Section 2. Note, submittal of individual personnel licenses and certifications are not required but shall be provided to the City upon request. 8. SUMMARY OF REQUIRED ATTACHMENTS A. The Offeror shall provide the Statement of Qualifications Form with ATTACHMENTS as noted above. The form and ATTACHMENTS shall be submitted with the Proposal. Provide the following information: 1) ATTACHEMENT A — Certificate of Authorization to conduct business in the State of Texas as required by Section 1 of this Form. 2) ATTACHMENT B — Separate Statement of Qualifications Form for Joint Venturers (if applicable), for each Joint Venturer, as required by Section 1 of this Form. 3) ATTACHMENT C— Tabular forms detailing current projects under contract as required by Section 7 of this Form. 4) ATTACHMENT D — Tabular forms detailing previous experience with similar projects as required by Section 7 of this Form. 5) ATTACHMENT E —Resumes, as required by Section 7 of this Form. 6) ATTACHMENT F — Provide additional information items as required by Section 2 Section3, Section 4, and Section 7 of this Form. This Statement of Qualifications is offered by: Business: Remont Engineering & Design Group, LLC dibla "RED Group" �r printed name of organization) By: �- (individua!'s signature) Name: Kyle J. Remont, Member of Remont Holdings LLC, Member of RED Group (typed or printed) Title: President & Manager of RED Group (typed or printed) Date: June 13th, 2024 (date signed) (If Business is a corporation, a partnership, or a joint venture, attach evidence of authority to sign.) Attest: (individual's signature) Name: Jacob M. Mattix, IV (typed or printed) Title: Director, Business Development, RED Group (typed or printed) Address for giving notices: 3850 N. Causeway Blvd, Suite 1255 Metairie, LA 70002 Designated Representative: Name: Jake Mattix (typed or printed) Title: Director, Business Development (typed or printed) Address: 3850 N. Causeway Blvd, Suite 1255 Metairie, LA 70002 Phone: 504-723-7518 Email: jmattix@red.group ATTACHMENT 1 — ADZ 133 1 Page 00 52 45 AGREEMENT Page 1 of 11 SECTION 00 52 45 AGREEMENT THIS AGREEMENT, authorized on October 15. 2024. is made by and between the City of Fort Worth, a Texas home rule municipality, acting by and through its duly authorized City Manager, ("City'), and Remont Engineering & Design Group, LLC d/b/a "RED Grout". authorized to do business in Texas, acting by and through its duly authorized representative, ("Contractor"). City and Contractor may jointly be referred to as Parties. City and Contractor, in consideration of the mutual covenants hereinafter set forth, agree as follows: ARTICLE 1. WORK Contractor shall complete all Work as specified or indicated in the Contract Documents for the Project identified herein. This Agreement includes performance of tasks within the Work by specific individuals identified in Section 00 4612 — Statement of Qualifications and as such the Contractor accepts the restrictions on substitution noted in Article 2.6 of the Proposal, except that the conditions will be modified as follows: Upon a staffing change, Contractor shall notify City in writing. Written approval by City will not be required but City shall have the right to reject the staffing change by written notice to Contractor. ARTICLE 2. PROJECT The project for which the Work under the Contract Documents may be the whole or only a part is generally described as follows: SCADA Svstem Replacement 103086 ARTICLE 3. CONTRACT PRICE City agrees to pay Contractor the Contract Price detailed in Section 00 42 10 -- Proposal Exhibit A for performance of the Work in accordance with the Contract Documents an amount, in current funds, of Eight Million Two Hundred Thirtv-Three Thousand Eight Hundred Thirtv-Six Dollars ($8.233.836.00 ). Contract price may be adjusted by change orders duly authorized by the Parties. lei YVaQaa]VAVIVO 114Y01 October 15, 2024 OFFICIAL RECORD CITY SECRETARY FT. WORTH, TX SCADA System Replacement 103086 00 52 45 AGREEMENT Page 2 of 11 ARTICLE 4. CONTRACT TIME 4.1 Final Acceptance. The Work shall be complete for Final Acceptance within 1382 days the date when the Contract Time commences to run, as provided in Paragraph 2.02 of the General Conditions, plus any extension thereof allowed in accordance with Article 12 of the General Conditions. Specific Project Components shall be Substantially Complete within the Milestone days noted in Table 00 42 10-A of the Proposal. Contract Time shall commence to run, as provided in Paragraph 2.02 of the General Conditions, plus any extension thereof allowed in accordance with Article 12 of the General Conditions. The total days to achieve Substantial Completion of Milestones and Final Acceptance of all Work shall be determined as noted in Article 14.05 and 14.06 of the General Conditions. 4.2 Liquidated Damages The Contractor recognizes that time is of the essence to achieve Final Acceptance of the Work and City and the public will suffer from loss of use if the Work is not completed within the time(s) specified in Paragraph 41 above. The Contractor also recognizes the delays, expense and difficulties involved in proving in a legal proceeding, the actual loss suffered by the City if the Work is not completed on time. Accordingly, instead of requiring any such proof, Contractor agrees that as liquidated damages for delay (but not as a penalty), the Contractor shall pay the City One Thousand Seven Hundred Dollars ($1700.00) for each day that expires after the time specified in Article 41 of this Section for Final Acceptance until the City issues the Final Letter of Acceptance. Such damages shall apply to Final Acceptance of the Work only, no liquidated damages apply to failure to achieve Substantial Completion of portions of the Work listed Milestones noted in Section 00 4210 Proposal, TABLE 00 42 10-A. ARTICLE 5. CONTRACT DOCUMENTS 5.1 Contents: A. The Contract Documents which comprise the entire agreement between City and Contractor concerning the Work consist of the following: 1. This Agreement. 2. Attachments to this Agreement: CITY OF FORT WORTH SCADA System Replacement October 15, 2024 103086 00 52 45 AGREEMENT Page 3 of 11 a. Executed Section 00 42 10 -- Proposal, including Exhibit A and all required attachments: 1) Exhibit A (Proposal Form) 2) Vendor Compliance to State Law Non -Resident Bidder (Section 00 43 37) 3) Offeror Statement of Qualification (Section 00 46 12) 4) State Conflict of Interest Questionnaire (CIQ and. Local Government Officer Conflict Disclosure Statement (CIS). 5) Required Proposal Surety (Bid Bond), Section 00 43 15 issued by a surety meeting the requirements of Paragraph 5.01 of the General Conditions. 6) MWBE Forms (optional at time of Proposal submittal). 7) Any additional documents that may be required by Section 12 of the Instructions to Offerors. b. Current Prevailing Wage Rate Table c. Insurance ACORD Form(s) d. Payment Bond e. Performance Bond f. Maintenance Bond g. Power of Attorney for the Bonds h. Worker's Compensation Affidavit i. MBE and/or SBE Utilization Form 3. General Conditions. 4. Supplementary Conditions. 5. Specifications specifically made a part of the Contract Documents by attachment or, if not attached, as incorporated by reference and described in the Table of Contents of the Project's Contract Documents, including all Appendices and Attachments. 6. Addenda. 7. Documentation submitted by Contractor prior to Notice of Award. S. The following which may be delivered or issued after the Effective Date of the Agreement and, if issued, become an incorporated part of the Contract Documents: a. Notice to Proceed. CITY OF FORT WORTH SCADA System Replacement October 15, 2024 103086 00 52 45 AGREEMENT Page 4 of 11 b. Field Orders. c. Change Orders. d. Letter of Final Acceptance. 5.2 Conflict. In the event of a conflict between this Agreement and anv other provision of the Contract Documents. the terms of this Agreement shall prevail. ARTICLE 6. LIABILITY AND INDEMNIFICATION 6.1 LIABILITY — THE CONTRACTOR SHALL BE LIABLE AND RESPONSIBLE FOR ANY AND ALL PROPERTY LOSS, PROPERTY DAMAGE AND PERSONAL INJURY, INCLUDING, INCLUDING, BUT NOT LIMITED TO, DEATH, TO ANY AND ALL PERSONS, OF ANY KIND OR CHARACTER, WHETHER REAL OR ASSERTED, TO THE EXTENT CAUSED BY THE NEGLIGENT ACT(S) OR OMISSION(S), MALFEASANCE OR INTENTIONAL MISCONDUCT OF TIIE CONTRACTOR, ITS OFFICERS, REPRESENTATIVES, AGENTS, SERVANTS, EMPLOYEES, CONTRACTORS, OR SUBCONTRACTORS. 6.2 GENERAL INDEMNIFICATION - THE CONTRACTOR HEREBY COVENANTS AND AGREES TO INDEMNIFY, HOLD HARMLESS, AND DEFEND CITY, ITS OFFICERS, AGENTS, REPRESENTATIVES, SERVANTS, AND EMPLOYEES, FROM AND AGAINST ANY AND ALL CLAIMS OR LAWSUITS OF ANY KIND OR CHARACTER, WHETHER REAL OR ASSERTED, FOR EITHER PROPERTY DAMAGE OR LOSS (INCLUDING ALLEGED DAMAGE OR LOSS TO THE CONTRACTOR'S BUSINESS AND ANY RESULTING LOST PROFITS) AND PERSONAL INJURY, INCLUDING, BUT NOT LIMITED TO, DEATH, TO ANY AND ALL PERSONS, ARISING OUT OF OR IN CONNECTION WITH THIS AGREEMENT, TO THE EXTENT CAUSED BY THE NEGLIGENT ACTS OR OMISSIONS OR MALFEASANCE OF THE CONTRACTOR, ITS OFFICERS, AGENTS, REPREENTATIVES, SERVANTS, EMPLOYEES, OR SUBCONTRACTORS. 6.3 INTELLECTUAL PROPERTY INDEMNIFICATION ---- The Contractor agrees to defend, settle, or pay, at its own cost and expense, any claim or action against City for infringement of any patent, copyright, trade mark, trade secret, or similar property right arising from City's use of the software or documentation in accordance with this Agreement, it being understood that this agreement to defend, settle or pay will not apply if City modifies or misuses the software and/or documentation. So long as the Contractor bears the cost and expense of payment for claims or actions against City pursuant to this section, the Contractor will have the right to conduct the defense of any such claim or action and all negotiations for its settlement or compromise and to settle or compromise any such claim; however, City will have the right to fully CITY OF FORT WORTH SCADA System Replacement October 15, 2024 103086 00 52 45 AGREEMENT Page 5 of 11 participate in any and all such settlement, negotiations, or lawsuit as necessary to protect City's interest, and City agrees to cooperate with the Contractor in doing so. In the event City, for whatever reason, assumes the responsibility for payment of costs and expenses for any claim or action brought against City for infringement arising under this Agreement, City will have the sole right to conduct the defense of any such claim or action and all negotiations for its settlement or compromise and to settle or compromise any such claim; however, the Contractor will fully participate and cooperate with City in defense of such claim or action. City agrees to give the Contractor timely written notice of any such claim or action, with copies of all papers City may receive relating thereto. Notwithstanding the foregoing, City's assumption of payment of costs or expenses will not eliminate the Contractor's duty to indemnify City under this Agreement. If the software and/or documentation or any part thereof is held to infringe and the use thereof is enjoined or restrained or, if as a result of a settlement or compromise, such use is materially adversely restricted, the Contractor will, at its own expense and as City's sole remedy, either: (a) procure for City the right to continue to use the software and/or documentation; or (b) modify the software and/or documentation to make it non -infringing, provided that such modification does not materially adversely affect City's authorized use of the software and/or documentation; or (e) replace the software and documentation with equally suitable, compatible, and functionally equivalent non -infringing software and documentation at no additional charge to City; or (d) if none of the foregoing alternatives is reasonably available to the Contractor terminate this Agreement, and refund all amounts paid to the Contractor by City, subsequent to which termination City may seek any and all remedies available to City under law. 6.4 Limitation of Liability Each party's entire liability for all claims arising out of or relating to this Agreement, and regardless of the basis of the claim, will not exceed an amount of two times the Contract Price. Neither party will be liable for breach -of -contract damages that the breaching party could not reasonably have foreseen at the time of breach. ARTICLE 7. MISCELLANEOUS 7.1 Terms. Terms used in this Agreement which are defined in Article 1 of the General Conditions will have the meanings indicated in the General Conditions. CITY OF FORT WORTH SCADA System Replacement October 15, 2024 103086 00 52 45 AGREEMENT Page 6 of 11 7.2 Assignment of Contract. This Agreement, including all of the Contract Documents may not be assigned by the Contractor without the advanced express written consent of the City. 7.3 Successors and Assigns. City and Contractor each binds itself, its partners, successors, assigns and legal representatives to the other party hereto, in respect to all covenants, agreements and obligations contained in the Contract Documents. 7.4 Severability/Non-Waiver of Claims. Any provision or part of the Contract Documents held to be unconstitutional, void or unenforceable by a court of competent jurisdiction shall be deemed stricken, and all remaining provisions shall continue to be valid and binding upon City and Contractor. The failure of City or Contractor to insist upon the performance of any term or provision of this Agreement or to exercise any right granted herein shall not constitute a waiver of City's or Contractor's respective right to insist upon appropriate performance or to assert any such right on any future occasion. 7.5 Governing Law and Venue. This Agreement, including all of the Contract Documents is performable in the State of Texas. Venue shall be Tarrant County, Texas, or the United States District Court for the Northern District of Texas, Fort Worth Division. 7.6 Authority to Sign. Contractor shall attach evidence of authority to sign Agreement if signed by someone other than the duly authorized signatory of the Contractor. 7.7 Non -Appropriation of Funds. In the event no funds or insufficient funds are appropriated by City in any fiscal period for any payments due hereunder, City will notify the Contractor of such occurrence and this Agreement shall terminate on the last day of the fiscal period for which appropriations were CITY OF FORT WORTH SCADA Systein Replacement October 15, 2024 103096 00 52 45 AGREEMENT Page? of 11 received without penalty or expense to City of any kind whatsoever, except as to the portions of the payments herein agreed upon for which funds have been appropriated. 7.8 Prohibition on Contracts with Companies Boycotting Israel. Contractor, unless a sole proprietor, acknowledges that in accordance with Chapter 2271 of the Texas Government Code, if Contractor has 10 or more full time -employees and the contract value is $100,000 or more, the City is prohibited from entering into a contract with a company for goods or services unless the contract contains a written verification from the company that it: (1) does not boycott Israel; and (2) will not boycott Israel during the term of the contract. The terms "boycott Israel" and "company" shall have the meanings ascribed to those terms in Section 808.001 of the Texas Government Code. By signing this contract, Contractor certifies that Contractor's signature provides written verification to the City that if Chapter 2271, Texas Government Code applies, Contractor: (1) does not boycott Israel; and (2) will not boycott Israel during the term of the contract. 7.9 Prohibition on Boycotting Energy Companies. Contractor acknowledges that in accordance with Chapter 2276 of the Texas Government Code, the City is prohibited from entering into a contract for goods or services that has a value of $100,000 or more, which will be paid wholly or partly from public funds of the City, with a company (with 10 or more full-time employees) unless the contract contains a written verification from the company that it: (1) does not boycott energy companies; and (2) will not boycott energy companies during the term of the contract. The terms "boycott energy company" and "company" have the meaning ascribed to those terms by Chapter 2276 of the Texas Government Code. To the extent that Chapter 2276 of the Government Code is applicable to this Agreement, by signing this Agreement, Contractor certifies that Contractor's signature provides written verification to the City that Contractor: (1) does not boycott energy companies; and (2) will not boycott energy companies during the term of this Agreement. 7.10 Prohibition on Discrimination Against Firearm and Ammunition Industries. Contractor acknowledges that except as otherwise provided by Chapter 2274 of the Texas Government Code, the City is prohibited from entering into a contract for goods or services that has a value of $100,000 or more which will be paid wholly or partly from public funds of the City, with a company (with 10 or more full-time employees) unless the contract contains a written verification from the company that it: (1) does not have a practice, policy, guidance, or directive that discriminates against a firearm entity or firearm trade association; and (2) will not discriminate during the term of the contract against a firearm entity or firearm trade association. The terms "discriminate," "firearm entity" and "firearm trade association" have the meaning ascribed to those terms by Chapter 2274 of the Texas Government Code. To the extent that Chapter 2274 of the Government Code is applicable to this Agreement, by signing this Agreement, Contractor certifies that CITY OF FORT WORT1-I SCADA System Replacement October 15, 2024 103086 005245 AGREEMENT Pages of 11 Contractor's signature provides written verification to the City that Contractor: (1) does not have a practice, policy, guidance, or directive that discriminates against a firearm entity or firearm trade association; and (2) will not discriminate against a firearm entity or firearm trade association during the term of this Agreement. 7.11 Immigration Nationality Act. Contractor shall verify the identity and employment eligibility of its employees who perform work under this Agreement, including completing the Employment Eligibility Verification Form (I-9). Upon request by City, Contractor shall provide City with copies of all I-9 forms and supporting eligibility documentation for each employee who performs work under this Agreement. Contractor shall adhere to all Federal and State laws as well as establish appropriate procedures and controls so that no services will be performed by any Contractor employee who is not legally eligible to perform such services. CONTRACTOR SHALL INDEMNIFY CITY AND HOLD CITY HARMLESS FROM ANY PENALTIES, LIABILITIES, OR LOSSES DUE TO VIOLATIONS OF THIS PARAGRAPH BY CONTRACTOR, CONTRACTOR'S EMPLOYEES, SUBCONTRACTORS, AGENTS, OR LICENSEES. City, upon written notice to Contractor, shall have the right to immediately terminate this Agreement for violations of this provision by Contractor. 7.12 No Third -Party Beneficiaries. This Agreement gives no rights or benefits to anyone other than the City and the Contractor and there are no third -party beneficiaries. 7.13 No Cause of Action Against Engineer. Contractor, its subcontractors and equipment and materials suppliers on the PROJECT or their sureties, shall maintain no direct action against the Engineer, its officers, employees, and subcontractors, for any claim arising out of, in connection with, or resulting from the engineering services performed. Only the City will be the beneficiary of any undertaking by the Engineer. The presence or duties of the Engineer's personnel at a construction site, whether as on -site representatives or otherwise, do not make the Engineer or its personnel in any way responsible for those duties that belong to the City and/or the City's construction contractors or other entities, and do not relieve the construction contractors or any other entity of their obligations, duties, and responsibilities, including, but not limited to, all construction methods, means, techniques, sequences, and procedures necessary for coordinating and completing all portions of the construction work in accordance with the Contract Documents and any health or safety precautions required by such construction work. The Engineer and its personnel have no authority to exercise any control over any construction contractor or other entity or their employees in connection with their work or any health or safety precautions. CITY OF PORT WORTH October 15, 2024 SCADA System Replacement 103086 00 52 45 AGREEMENT Page 9 of 11 7.14 Public Information Act. City is a government entity under the laws of the State of Texas and all documents held or maintained by City are subject to disclosure under the Texas Public Information Act. In the event there is a request for information marked Confidential or Proprietary, City will promptly notify the Contractor. It will be the responsibility of the Contractor to submit reasons objecting to disclosure. A determination on whether such reasons are sufficient will not be decided by City, but by the Office of the Attorney General of the State of Texas or by a court of competent jurisdiction. 7.15 Force Majeure. City and the Contractor will exercise their best efforts to meet their respective duties and obligations as set forth in this Agreement, but will not be held liable for any delay or omission in performance due to force majeure or other causes beyond their reasonable control, including, but not limited to, compliance with any government law, ordinance, or regulation; acts of God; acts of the public enemy; fires; strikes; lockouts; natural disasters; wars; riots; epidemics or pandemics; government action or inaction; orders of government; material or labor restrictions by any governmental authority; transportation problems; restraints or prohibitions by any court, board, department, commission, or agency of the United States or of any States; civil disturbances; other national or regional emergencies; or any other similar cause not enumerated herein but which is beyond the reasonable control of the Party whose performance is affected (collectively, "Force Majeure Event"). The performance of any such obligation is suspended during the period of, and only to the extent of, such prevention or hindrance, provided the affected Party provides written notice of the Force Majeure Event, and an explanation as to how it prevents or hinders the Party's performance, as soon as reasonably possible after the occurrence of the Force Majeure Event, with the reasonableness of such notice to be determined by the City in its reasonable discretion. The notice required by this section must be addressed and delivered in accordance with Article 17.01 of the General Conditions. IN WITNESS WHEREOF, City and Contractor have each executed this Agreement to be effective as of the date subscribed by the City's designated Assistant City Manager ("Effective Date"). CITY OF FORT WORTH SCADA System Replacement October 15, 2024 103086 Contractor By: Signat rff e� Kyle J. Remont (Printed Name) President Title 3850 N. Causeway Blvd, Suite 1255 Address Metairie, LA 70002 City/State/Zip October 21, 2024 City of Fort Worth By: W� William Johnson (N v 3, 2024 08:22 GMT+1) William Johnson Assistant City Manager 11 /03/2024 Date Attest: 9FORT add A 01 �Y d ' Pao °�d0 I � �� � rr l� 0 �o�o d 3dnn oEoo544 Jannette Goodall, City Secretary (Seal) M&C: 24-0853 Date: October 15, 2024 Form 1295 No.: 2024-1203449 00 52 45 AGREEMENT Page 10 of 1 l Date Contract Compliance Manager: By signing, I acknowledge that I am the person responsible for the monitoring and administration of this contract, including ensuring all performance and reporting requirements. Shela R. Chowdhury, PE Assistant Water Director Appr ve as to Form and Legality: Douglas Black (Nov 1, 202417:42 CDT) Douglas W. Black Sr. Assistant City Attorney APPROVAL RECOMMENDED: Christopher H der (Oct 31, 2024 07:02 CDT) Chris Harder, P.E., Director Water Department CITY OF FORT WORTH OFFICIAL RECORD SCADA System Replacement October 15, 2024 CITY SECRETARY 103086 FT. WORTH, TX 00 52 45 ++END OF SECTION+ CITY OF FORT WORTH AGREEMENT Page 11 of 11 SCADA System Replacement October 15, 2024 103086 0061 13- 1 PERFORMANCE BOND Page I of 2 1 SECTION 00 6113 BOND NO. 4471322 2 PERFORMANCE BOND 3 4 THE STATE OF TEXAS § 5 § KNOW ALL BY THESE PRESENTS: 6 COUNTY OF TARRANT § 7 That we, Remont Engineer_& Design Group, LLC dba RED Group , 8 known as "Principal" herein and SureTec Insurance Comuanv a 9 corporate surety(sureties, if more than one) duly authorized to do business in the State of Texas, 10 known as "Surety" herein (whether one or more), are held and firmly bound unto the City of Fort I 1 Worth, a municipal corporation created pursuant to the laws of Texas, known as "City" herein, in 12 the penal sum of, Two Million One Hundred Ninety -Three Thousand Two Hundred Twenty -Two 13 and 001100ths Dollars ($ $2,193,222.00 ), lawful money of the United States, to be paid in 14 Fort Worth, Tarrant County, Texas for the payment of which sum well and truly to be made, we 15 bind ourselves, our heirs, executors, administrators, successors and assigns, jointly and severally, 16 firmly by these presents. 17 WHEREAS, the Principal has entered into a certain written contract with the City awarded 18 the 15th day of _October , 20 24 , which Contract is hereby referred to and made a 19 part hereof for all purposes as if fully set forth herein, to funiish all materials, equipment labor and 20 other accessories defined by law, in the prosecution of the Work, including any Change Orders, as 21 provided for in said Contract designated as SCADA Replacement, City Project No, 103086 22 Proposal Items 1,2, 3,10,11, 12, & 13. 23 NOW, THEREFORE, the condition of this obligation is such that if the said Principal 24 shall faithfully perform it obligations under the Contract and shall in all respects duly and faithfully 25 perform the Work, including Change Orders, under the Contract, according to the plans, 26 specifications, and contract documents therein referred to, and as well during any period of 27 extension of the Contract that may be granted on the part of the City, then this obligation shall be 28 and become null and void, otherwise to remain in full force and effect. 29 PROVIDED FURTHER, that if any legal action be filed on this Bond, venue shall Iie in 30 Tarrant County, Texas or the United States District Court for the Northern District of Texas, Fort 31 Worth Division. CITY OF FORT WORTH [Insert Project Name] STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS (Insert Project Nnmbet] Revised December 8, 2023 2 3 4 5 6 7 8 9 10 11 I2 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 0061 13 - 2 PERFORMANCE BOND Page 2 of 2 This bond is made and executed in compliance with the provisions of Chapter 2253 of the Texas Government Code, as amended, and all liabilities on this bond shall be determined in accordance with the provisions of said statue. IN W11 NESS WUEREOF, the Principal and the Surety have SIGNED and SEALED this instrument by duly authorized agents and officers on this the 15th day of October . 20 24 . PRINCIPAL: ATTEST: ®/ Princi �cre#a �L c p J(A911 IV44 � Witness as to Prin I fka issw al �� Witness as to Surety Catherine Froeba Remont Engineering & Design Group, LLC dba RED Group BY: % ature Kvle Remont. President Name and Title Address: 3850 N. Causeway Blvd., Suite 1255, Metairie, LA 70002 SURETY: _SureTec Insurance ComDanv B*E. / reJe Attomev n-Fact Name and Title Address: _2103 CitvWest Blvd.. Suite 1300 Houston, TX 77042 Telephone Number: _678-223-2001 Email Address. ikrom)aJulins.com *Note: If signed by an officer of the Surety Company; there must be on file a certified extract from the by-laws showing that this person has authority to sign such obligation. If Surety's physical address is different from its mailing address, both must be provided. The date of the bond shall not be prior to the date the Contract is awarded. CITY OF FORT WORTH STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS Revised December S, 2023 (Insert Project Name] (Insert Project Number) POA# 1810032 JOINT LIMITED POWER OF ATTORNEY KNOW ALL MEN BY THESE PRESENTS; That SureTec Insurance Company, a Corporation duly organized and existing undef the laws of the State of Texas and having its principal office In the County of Harris, Texas and Markel Insurance Company (the "Company"), a corporation duly organized and existing under the laws of the state of Illinois, and having its principal administrative office in Glen Allen, Virginia, does by these presents make, constitute and appoint: Catherine R. Froeba, Jack T. Landry, William H. Ellsworth, Laura Burns, Jeffrey E. Kropp, Jill K. Tucker Their true and lawful agent(s) and attorneys) -in -fact, each in their separate capacity J more than one Is named above, to make, execute, seal and deliver for and on their own behalf, individually as a surety or jointly, as co -sureties, and as their act and deed any and all bonds and other undertaking in suretyship provided, however, that the penal sum of anyone such Instrument executed hereunder shall not exceed the sum of. - Fifty Million and 001100 Dollars ($50,000,000.00) This Power of Attorney is granted and is signed and sealed under and by the authority of the following Resolutions adopted by the Board of Directors of SureTec Insurance Company and Markel Insurance Company: "RESOLVED, That the President, any Senior Vice President, Vice President, Assistant Vice President, Secretary, Assistant Secretary, Treasurer or Assistant Treasurer and each of them hereby is authorized to execute powers of attorney, and such authority can be executed by use of facsimile signature, which may be attested or acknowledged by any officer or attorney, of the company, qualifying the attorney or attorneys named in the given power of attorney, to execute In behalfof, and acknowledge as the act and deed of the 5ureTec Insurance Company and Markel Insurance Company, as the case may be, all bond undertakings and contracts of suretyship, and to affix the corporate seal thereto," IN WITNESS WHEREOF, Markel Insurance Company and SureTec Insurance Company have caused their official seal to be hereunto affixed and these presents to be signed by their duly authorized officers on the 27th day of January , 2023 , SureTec Insurance Company 0We By;� �/"4 f f--We Michael C. Kelmig, President State of Texas County of Harris: a$�RANcF y Nss9s3s�NCl��ii `..SEAL '��rrr�r*rnNss�ti nsurance President On this 27th day of Jaruary , 2023 A. D., before me, a Notary Public of -the state of Texas, in and for the County of Harris, duly commissioned and qualified, came THE ABOVE OFFICERS OF THE COMPANIES, to me personally known to be the Individuals and officers described in, who executed the preceding Instrument, and they acknowledged the execution of same, and being by me duly sworn, disposed and said that they are the officers of the said companies aforesaid, and that the seals affixed to the proceeding instrument are the Corporate Seals of said Companies, and the said Corporate Seals and their signatures as officers were duly affixed and subscribed to the said instrument by the authority and direction of the said companies, and that Resolutions adopted by the Board of Directors of said Companies referred to In the preceding Instrument Is now in force. IN TESTIMONY WHEREOF, I have hereunto set my hand, and affixed my Official Seal at the County of Harris, the day and year first above written, JUIPE. MCC fk1ex BY: NotaryPublic State of Texas Commission # 12947680-5 f ie E. McClary, Notary Public S5 °F Commission Expires March 29, 2026 ycommission expires 3/29/202fi We, the undersigned Officers of SureTec Insurance Company and Markel Insurance Company do herby certify that the original POWER OF ATTORNEY of which the foregoing is a full, true and correct copy is still in full force and effect and has not been revoked. IN WITNESS WHEREOF, we have hereunto set our hands, and affixed the Seals of said Companies, on the 15th dayof October 2024 Itr sur' . Company B _ M. Br nt Beaty, A, sistan Secretary Markel Insurance Company By: ZAnd w Ma quis, As qntSe ary Any Instrument Issued in excess of the penalty stated above Is totally void and without any validity. 1810032 For varffitati0n of the authority ofthis Power you may tali (713)812-0800 on any business day between 830 AM and 5;00 PM CST. 0061 14-1 PAYMENT BOND Page 1 of 2 1 SECTION 00 61 14 BOND NO.4471322 2 PAYMENT BOND 3 4 THE STATE OF TEXAS § 5 § KNOW ALL BY THESE PRESENTS: 6 COUNTY OF TARRANT § 7 That we, Remont EnaineerinR & Design Group, LLC dba RED Group , known as 8 "Principal' herein, and _ SureTec Insurance Company , a corporate surety 9 (sureties), duly authorized to do business in the State of Texas, known as "Surety" herein (whether 10 one or more), are held and firmly bound unto the City of Fort Worth, a municipal corporation I I created pursuant to the laws of the State of Texas, known as "City" herein, in the penal sum of Two 12 Million One Hundred Ninety -Three Thousand Two Hundred Twentv-Two and 00/100ths 13 Dollars ($ 2,193,222.00, ), lawful money of the United States, to be paid in Fort Worth, Tarrant 14 County, Texas, for the payment of which sum well and truly be made, we bind ourselves, our heirs, 15 executors, administrators, successors and assigns, jointly and severally, firmly by these presents: 16 WHEREAS, Principal has entered into a certain written Contract with City, awarded the 17 15th day of October , 20 24 , which Contract is hereby 18 referred to and made a part hereof for all purposes as if fully set forth herein, to furnish all materials, 19 equipment, labor and other accessories as defined by law, in the prosecution of the Work as 20 provided for in said Contract and designated as SCADA Replacement, City Project No. 103086, 21 Proposal Items 1,2, 3, 10, 11, 12, & 13 22 NOW, THEREFORE, THE CONDITION OF THIS OBLIGATION is such that if 23 Principal shall pay all monies owing to any (and all) payment bond beneficiary (as defined in 24 Chapter 2253 of the Texas Government Code, as amended) in the prosecution of the Work under 25 the Contract, then this obligation shall be and become null and void; otherwise to remain in full 26 force and effect. 27 This bond is made and executed in compliance with the provisions of Chapter 2253 of the 28 Texas Government Code, as amended, and all liabilities on this bond shall be detennined in 29 accordance with the provisions of said statute. 30 CITY OF FORT WORTH [Inserl Yrojecl Name] STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS (Insert Project Number] Revised December S, 2023 PA 0061 14 - 2 PAYMENT BOND Page 2 of 2 IN WITNESS 'WHEREOF, the Principal and Surety have each SIGNED and SEALED this instrument by duly authorized agents and officers on this the 15th day of 3 October 4 5 6 7 8 4 10 11 12 ATTEST: , 2024 (Principal) cretaryIW-r �aIV f� Ax+f"t"; CA4 1A-,it ess as to Princial I�i[CGi.s S1A, ( p ATTEST: See Attached Power of Attorney (Surety) Secretary Witness as to Surety Catherine Froeba PRINCIPAL: Remont Engineering & Desian Grout), LLC dba RED Group BY: Signature Kyle Remont, President Name and Title Address: 3850 N. Causeway Blvd., Suite 1255 Metairie, LA 70002 SURETY: SurcTec Insurance Company —* BY: C— -1 Si r Jeffrev E. Kr000. Attorney -in -Fact — Name and Title Address: 2103 CityWest Blvd., Suite 1300 Houston, TX 77042 Telephone Number: _678-223-2001 Email Address: ikrovv(27iulins.com Note: If signed by an officer of the Surety, there must be on file a certified extract from the bylaws showing that this person has authority to sign such obligation. If Surety's physical address is different from its mailing address, both must be provided. The date of the bond shall not be prior to the date the Contract is awarded. END OF SECTION CITY OF FORT WORTH lInserr Project Nance] STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS (Insert Project Number] Revised December 8, 2023 POA# 1810032 JOINT LIMITED POWER OF ATTORNEY KNOW ALL MEN BY THESE PRESENTS: That SureTec Insurance Company, a Corporation duly organized and existing undef the laws of the State of Texas and having Its principal office in the County of Harris, Texas and Markel Insurance Company (the "Company'), a corporation duly organized and existing under the laws of the state of Illinois, and having its principal administrative office in Glen Allen, Virginia, does by these presents make, constitute and appoint: Catherine R. Froeba, Jack T. Landry, William H. Ellsworth, Laura Burns, Jeffrey E. Kropp, Jill K. Tucker Their true and lawful agent(s) and attorney(si-in•fact, each In their separate capacity if more than one is named above, to make, execute, seal and deliver forand on their own behaif, individually as a surety or jolntly, as co -sureties, and as their act and deed any and all bonds and other undertaking in suretyship provided, however, that the penal sum of any one such instrument executed hereunder shall not exceed the sum of: Fifty Million and 00/100 Dollars ($50,000,000.00) This Power of Attorney is granted and Is signed and sealed under and by the authority of the following Resolutions adopted by the Board of Directors of SureTec Insurance Company and Markel Insurance Company: " RESCILVED, That the President, any Senior Vlce President, Vice President, Assistant Vice President, Secretary, Assistant Secretary, Treasurer or Assistant Treasurer and each of them hereby is authorized to execute powers of attorney, and such authority can be executed by use of facsimile signature, which maybe attested or acknowledged by any officer or attorney, of the company, qualifying the attorney or attorneys named in the given power of attorney, to execute in behalf of, and acknowledge as the act and deed ofthe SureTec Insurance Company and Markel Insurance Company, as the case may be, all bond undertakings and contracts of suretyship, and to affix the corporate seal thereto." IN WITNESS WHEREOF, Markel Insurance Company and SureTec Insurance Company have caused their official seal to be hereunto affixed and these presents to be signed by their duly authorized officers on the 27th day of January , 2023 . SureTec Insurance Company ByAN&4�< Michael C. Keimig, President State of Texas County of Harris: a� it: a P1. �41 �rrritikitttttt`* On this 27th day of January , 2022 A.D., before me, a Notary Public of the State of Texas, In and for the County of Harris, duly cammissloned and qualified, came THE ABOVE OFF#CERS OF THE COMPANIES, to me personally known to be the individuals and officers described in, who executed the preceding instrument, and they acknowledged the execution of same, and being by me duly sworn, disposed and said that they are the officers of the said companies aforesaid, and that the seals affixed to the proceeding instrument are the Corporate Seals of said Companies, and the said Corporate Seals and their signatures as officers were duly affixed and subscribed to the said Instrument by the authority and direction ofthe said companies, and that Resolutions adopted by the Board of Directors of said Companies referred to In the preceding Instrument is now in force. IN TESTIMONY WHEREOF, I have hereunto set my hand, and affixed my Official Seal at the County of Harris, the day and year first above written, . wr. JULIE E. MCCLARY Notary Public State of Texas Commission # 12947680-5 J le E. McClary, Notary Public Commission Expires March 29, 2026 y commission expires 3/29/2026 We, the undersigned officers of SureTec Insurance Company and Markel Insurance Company do herby certify that the original POWER OF ATTORNEY of which the foregoing is a full, true and correct copy Is still in full force and effect and has not been revoked. IN WITNESS WHEREOF, we have hereunto set our hands, and affixed the Seals of said Companies, on the 15th day of October 2024 9M.'ere(nt WA B ry Markel Insurance Company t By: / XAn,A, Ma quis, As ' ISerltary Any Instrument Issued in excess of the penalty stated above Is totally void and without any validity. 1810032 For verification of the authority of this Power you may call 17131812.0800 on any business day between 830 AM and 5:00 PM CST. 0061 19 - 1 MAINTENANCE BOND Page I of 3 1 SECTION 00 61 19_ BOND NO.4471323 2 MAINTENANCE BOND 3 4 THE STATE OF TEXAS § 5 § KNOW ALL BY THESE PRESENTS: 6 COUNTY OF TARRANT § 7 That we Remont Engineering & Design , LLC dba RED Group , known as 8 "Principal" herein and _SureTec Insurance COMDanY , a corporate surety (sureties, if more 9 than one) duly authorized to do business in the State of Texas, known as "Surety" herein (whether 10 one or more), are held and firmly bound unto the City of Fort Worth, a municipal corporation I 1 created pursuant to the laws of the State of Texas, known as "City" herein, in the sum of 12 One Hundred Nine Thousand Six Hundred Sixtv-One and 00/100ths. Dollars 13 ($ 109,661.00 ), lawful money of the United States, to be paid in Fort Worth, Tarrant 14 County, Texas, for payment of which sum well and truly be made unto the City and its successors, 15 we bind ourselves, our heirs, executors, administrators, successors and assigns, jointly and 16 severally, firmly by these presents. 17 18 WHEREAS, the Principal has entered into a certain written contract with the City awarded i9 the_15th day of October , 2024 , which Contract is hereby 20 referred to and a made part hereof for all purposes as if fully set forth herein, to furnish all materials, 21 equipment labor and other accessories as defined by law, in the prosecution of the Work, including 22 any Work resulting from a duly authorized Change Order (collectively herein, the "Work") as 23 provided for in said contract and designated as SCADA Replacement, City Project No. 103086, 24 Proposal Items 1,2, 3, 10, 11, 12, & 13 ; and 25 26 WHEREAS, Principal .binds itself to use such materials and to so construct the Work in 27 accordance with the plans, specifications and Contract Documents that the Work is and will remain 28 free from defects in materials or workmanship for and during the period of two (2) years after the 29 date of Final Acceptance of the Work by the City ("Maintenance Period"); and 30 31 WHEREAS, Principal binds itself to repair or reconstruct the Work in whole or in part upon 32 receiving notice from the City of the need therefor at any time within the Maintenance Period. 33 CITY OF FORT WORTH [Insert Project Name] STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS [Insert Project Number] Revised December 8, 2023 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 0061 19-2 MAINTENANCE BOND Page 2 of 3 NOW THEREFORE, the condition of this obligation is such that if Principal shall remedy any defective Work, for which timely notice was provided by City, to a completion satisfactory to the City, then this obligation shall become null and void; otherwise to remain in full force and effect. PROVIDED, HOWEVER, if Principal shall fail so to repair or reconstruct any timely noticed defective Work, it is agreed that the City may cause any and all such defective Work to be repaired and/or reconstructed with all associated costs thereof being borne by the Principal and the Surety under this Maintenance bond; and PROVIDED FURTHER, that if any legal action be filed on this Bond, venue shall lie in Tarrant County, Texas or the United States District Court for the Northern District of Texas, Fort Worth Division; and PROVIDED FURTHER, that this obligation shall be continuous in nature and successive recoveries may be had hereon for successive breaches. CITY OF FORT WORTH (Insert Project Name] STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS Anson Project Number] Revised December 8, 2023 0061 19-3 MAINTENANCF- BOND Page 3 of 3 1 IN WITNESS WHEREOF, the Principal and the Surety have each SIGNED and SEALED this 2 instrument by duly authorized agents and officers on this the 15th day of October 3 , 2024._ 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 ATTEST: (Principal/tal X, *Wiess )/s to Pr., r ii�pI M0SSe- ' ! I ATTEST: See Attached Power of Attorney (Surety) Secretary Witness as to Surety Catherine Froeba PRINCIPAL: Remont Eneineerin..R & Design Group_ . LLC dba RED Group BY: .�ignature Kyle Remont, President Name and Title Address: 3850 N. Causewav Blvd.. Suite 1255 Metairie, LA 70002 SURETY: SureT urance Comp y BY: O/SiIature s ]effrev E. Kr000. Attorney -in -Fact Name and Title Address: 2103 City West Blvd.. Suite I355_ Houston, TX 77042 Telephone Number: 678-223-2001 Email Address: ikrovv(@,iu1ins.com 40 *Note: if signed by an officer of the Surety Company, there must be on file a certified extract 41 from the by-laws showing that this person has authority to sign such obligation. If 42 Surety's physical address is different from its mailing address, both must be provided. 43 The date of the bond shall not be prior to the date the Contract is awarded. 44 CITY OF FORT WORTH STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS Revised December 8, 2023 [Insert Project Name] [Insert Project Number] POA# 1810032 JOINT LIMITED POWER OF ATTORNEY KNOW ALL MEN BY THESE PRESENTS; That SureTec Insurance Company, a Corporation duly organized and existing unde'rthe laws of the State of Texas and having its principal office In the County of Harris, Texas and Markel Insurance Company (the "Company"), a corporation duly organized and existing under the laws of the state of Illinois, and having its principal administrative office in Glen Allen, Virginia, does by these presents make, constitute and appoint: Catherine R. Froeba, Jack T. Landry, William H. Ellsworth, Laura Burns, Jeffrey E. Kropp, Jill K. Tucker Theirtrue and lawful agent(s) and attorneys) -in -fact, each in their separate capacity if more than one is named above, to make, execute, seal and deliver for and on their own behalf, individually as a surety or jointly, as co -sureties, and as their act and deed any and all bonds and other undertaking in suretyship provided, however, that the penal sum of any one such instrument executed hereunder shall not exceed the sum of: Fifty Million and 001100 Dollars ($50,000,000.00) This Power of Attorney is granted and is signed and sealed under and by the authority of the following Resolutions adopted by the Board of Directors of SureTec Insurance Company and Markel Insurance Company: "RESOLVED, That the President, any Senior Vice President, Vice President, Assistant Vice President, Secretary, Assistant Secretary, Treasurer or Assistant Treasurer and each of them hereby is authorized to execute powers of attorney, and such authority can be executed by use of facsimile signature, which maybe attested or acknowledged by any officer or attorney, of the company, qualifying the attorney or attorneys named in the given power of attorney, to execute in behalf of, and acknowledge as the act and deed ofthe SureTec Insurance Company and Markel Insurance Company, as the case may be, all bond undertakings and contracts of suretyship, and to affix the corporate seal thereto." IN WITNESS WHEREOF, Markel Insurance Company and SureTec Insurance Company have caused their official seal to be hereunto affixed and these presents to be signed by their duly authorized officers on the 27th day of January , 2o2a . SureTec Insurance Company 0101r'(r ��t�'ti0 to Us .SEALcc C2 ' W Michael C. Keimig, President fell `` 'ss*s .•, µy � »�fllintt State of Texas County of Harris: On this 27th day of January , 2023 A. D., before me, a Notary Public of the State of Texas, in and for the County of Harris, duly commissioned and qualified, came THE ABOVE OFFICERS OF THE COMPANIES, to me personally known to be the individuals and officers described in, who executed the preceding instrument, and they acknowledged the execution of same, and being by me duly sworn, disposed and said that they are the officers of the said companies aforesaid, and that the seals affixed to the proceeding instrument are the Corporate Seals of said Companies, and the said Corporate Seals and their signatures as officers were duly affixed and subscribed to the said Instrument by the authority and direction of the said companies, and that Resolutions adopted by the Board of Directors of said Companies referred to in the preceding Instrument Is now in force. IN TESTIMONY WHEREOF, I have hereunto set my hand, and affixed my Official Seal at the County of Harris, the day and year first above written. RY'p-e JryfE E. MCCLARY 1 v UGC. :•' `�`- Notary Public State of Texas By: ^�'°' Commission # 12947680-5 ;,`�.oF�t•° 1 le E. McClary, Notary Public GI)MMIS011 Expires March 29, 2026 } y commission expires 3/29/2026 We, the undersigned Officers of SureTec Insurance Company and Markel Insurance Company do herby certify that the original POWER OF ATTORNEY of which the foregoing is a full, true and correct copy is still in full force and effect and has not been revoked. IN WITNESS WHEREOF, we have hereunto set our hands, and affixed the Seals of said Companies, on the 101day of October 2024 . u sur Gamp'eny M. Rr nt 13eaty,./A istant,5ecretary Markel insurance Company r By: AndMa quis, As ' nt Se r tart' Any Instrument Issued in exitss of the penalty stated above Is totally void and without any validity, 1810082 For verification of the authority of this Power you may call (713)812-0800 on any business day between 8:30 AM and 5:00 PM CST. 00 61 25 CERTIFICATE OF INSURANCE Pagel of 2 619114II[o)a[IIIZ:i&W CERTIFICATE OF INSURANCE PAGE LEFT BLANK INTENTIONALLY. PLACE AWARDED CONTRACTOR'S STANDARD ACORD CERTIFICATE OF INSURANCE FORM HERE FOR CONTRACT EXECUTION. ++END OF SECTION++ CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 00 61 25 CERTIFICATE OF INSURANCE Page 2 of 2 CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 STANDARD GENERAL CONDITIONS OF THE CONSTRUCTION CONTRACT CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: &23/2021 ATTACHMENT 1 - AD1 STANDARD GENERAL CONDITIONS OF THE CONSTRUCTION CONTRACT TABLE OF CONTENTS Page Article I — Definitions and Terminology .......................................................................................................... I 1.01 Defined Terms ............................................................................................................................... 1 1.02 Terminology .................................................................................................................................. 6 Article2 — Preliminary Matters ......................................................................................................................... 7 2.01 Copies of Documents .................................................................................................................... 7 2.02 Commencement of Contract Time; Notice to Proceed ................................................................ 7 2.03 Starting the Work .......................................................................................................................... 8 2.04 Before Starting Construction ........................................................................................................ 8 2.05 Preconstruction Conference .......................................................................................................... 8 2.06 Public Meeting .............................................................................................................................. 8 2.07 Initial Acceptance of Schedules .................................................................................................... 8 Article 3 — Contract Documents: Intent, Amending, Reuse ............................................................................ 8 3.01 Intent .............................................................................................................................................. 8 3.02 Reference Standards ...................................................................................................................... 9 3.03 Reporting and Resolving Discrepancies ....................................................................................... 9 3.04 Amending and Supplementing Contract Documents ................................................................. 10 3.05 Reuse of Documents ................................................................................................................... 10 3.06 Electronic Data ............................................................................................................................ 11 Article 4 — Availability of Lands; Subsurface and Physical Conditions; Hazardous Environmental Conditions; Reference Points ........................................................................................................... 11 4.01 Availability of Lands .................................................................................................................. 11 4.02 Subsurface and Physical Conditions .......................................................................................... 12 4.03 Differing Subsurface or Physical Conditions ............................................................................. 12 4.04 Underground Facilities ............................................................................................................... 13 4.05 Reference Points ......................................................................................................................... 14 4.06 Hazardous Environmental Condition at Site .............................................................................. 14 Article 5 — Bonds and Insurance ..................................................................................................................... 16 5.01 Licensed Sureties and Insurers ................................................................................................... 16 5.02 Performance, Payment, and Maintenance Bonds ....................................................................... 16 5.03 Certificates of Insurance ............................................................................................................. 16 5.04 Contractor's Insurance ................................................................................................................ 18 5.05 Acceptance of Bonds and Insurance; Option to Replace ...........................................................19 Article 6 — Contractor's Responsibilities ....................... 6.01 Supervision and Superintendence ............... CITY OF FORT WORTH STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS Revision: 8/23/2021 ................................................................................. 19 ................................................................................ 19 SCADA System Replacement 103086 ATTACHMENT 1 — AD1 6.02 Labor; Working Hours ................................................................................................................ 20 6.03 Services, Materials, and Equipment ........................................................................................... 20 6.04 Project Schedule .......................................................................................................................... 21 6.05 Substitutes and "Or-Equals"....................................................................................................... 21 6.06 Concerning Subcontractors, Suppliers, and Others .................................................................... 24 6.07 Wage Rates .................................................................................................................................. 25 6.08 Patent Fees and Royalties ........................................................................................................... 26 6.09 Permits and Utilities .................................................................................................................... 27 6.10 Laws and Regulations ................................................................................................................. 27 6.11 Taxes ........................................................................................................................................... 28 6.12 Use of Site and Other Areas ....................................................................................................... 28 6.13 Record Documents ...................................................................................................................... 29 6.14 Safety and Protection .................................................................................................................. 29 6.15 Safety Representative .................................................................................................................. 30 6.16 Hazard Communication Programs ............................................................................................. 30 6.17 Emergencies and/or Rectification ............................................................................................... 30 6.18 Submittals .................................................................................................................................... 31 6.19 Continuing the Work ................................................................................................................... 32 6.20 Contractor's General Warranty and Guarantee .......................................................................... 32 6.21 Indemnification ......................................................................................................................... 33 6.22 Delegation of Professional Design Services .............................................................................. 34 6.23 Right to Audit .............................................................................................................................. 34 6.24 Nondiscrimination ....................................................................................................................... 35 Article 7 - Other Work at the Site ................................................................................................................... 35 7.01 Related Work at Site ................................................................................................................... 35 7.02 Coordination ................................................................................................................................ 36 Article 8 - City's Responsibilities ................................................................................................................... 36 8.01 Communications to Contractor ................................................................................................... 36 8.02 Furnish Data ................................................................................................................................ 36 8.03 Pay When Due ............................................................................................................................ 36 8.04 Lands and Easements; Reports and Tests ................................................................................... 36 8.05 Change Orders ............................................................................................................................. 36 8.06 Inspections, Tests, and Approvals .............................................................................................. 36 8.07 Limitations on City's Responsibilities ....................................................................................... 37 8.08 Undisclosed Hazardous Environmental Condition .................................................................... 37 8.09 Compliance with Safety Program ............................................................................................... 37 Article 9 - City's Observation Status During Construction ........................................................................... 37 9.01 City's Project Manager ............................................................................................................ 37 9.02 Visits to Site ................................................................................................................................ 37 9.03 Authorized Variations in Work .................................................................................................. 38 9.04 Rejecting Defective Work .......................................................................................................... 38 9.05 Determinations for Work Performed .......................................................................................... 38 9.06 Decisions on Requirements of Contract Documents and Acceptability of Work .....................38 CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1 - AD1 Article 10 - Changes in the Work; Claims; Extra Work ................................................................................ 38 10.01 Authorized Changes in the Work ............................................................................................... 38 10.02 Unauthorized Changes in the Work ........................................................................................... 39 10.03 Execution of Change Orders ....................................................................................................... 39 10.04 Extra Work .................................................................................................................................. 39 10.05 Notification to Surety .................................................................................................................. 39 10.06 Contract Claims Process ............................................................................................................. 40 Article 11 - Cost of the Work; Allowances; Unit Price Work; Plans Quantity Measurement ......................41 11.01 Cost of the Work ......................................................................................................................... 41 11.02 Allowances .................................................................................................................................. 43 11.03 Unit Price Work .......................................................................................................................... 44 11.04 Plans Quantity Measurement ...................................................................................................... 45 Article 12 - Change of Contract Price; Change of Contract Time ................................................................. 46 12.01 Change of Contract Price ............................................................................................................ 46 12.02 Change of Contract Time ............................................................................................................ 47 12.03 Delays .......................................................................................................................................... 47 Article 13 - Tests and Inspections; Correction, Removal or Acceptance of Defective Work ...................... 48 13.01 Notice of Defects ........................................................................................................................ 48 13.02 Access to Work ........................................................................................................................... 48 13.03 Tests and Inspections .................................................................................................................. 48 13.04 Uncovering Work ........................................................................................................................ 49 13.05 City May Stop the Work ............................................................................................................. 49 13.06 Correction or Removal of Defective Work ................................................................................ 50 13.07 Correction Period ........................................................................................................................ 50 13.08 Acceptance of Defective Work ................................................................................................... 51 13.09 City May Correct Defective Work ............................................................................................. 51 Article 14 - Payments to Contractor and Completion .................................................................................... 52 14.01 Schedule of Values ...................................................................................................................... 52 14.02 Progress Payments ...................................................................................................................... 52 14.03 Contractor's Warranty of Title ................................................................................................... 54 14.04 Partial Utilization ........................................................................................................................ 55 14.05 Final Inspection ........................................................................................................................... 55 14.06 Final Acceptance ......................................................................................................................... 55 14.07 Final Payment .............................................................................................................................. 56 14.08 Final Completion Delayed and Partial Retainage Release ........................................................ 56 14.09 Waiver of Claims ........................................................................................................................ 57 Article 15 - Suspension of Work and Termination ........................................................................................ 57 15.01 City May Suspend Work ............................................................................................................. 57 15.02 City May Terminate for Cause ................................................................................................... 58 15.03 City May Terminate For Convenience ....................................................................................... 60 Article16 - Dispute Resolution ...................................................................................................................... 61 16.01 Methods and Procedures ............................................................................................................. 61 CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1 - AD1 Article 17 — Miscellaneous .................................... 17.01 Giving Notice .................................... 17.02 Computation of Times ...................... 17.03 Cumulative Remedies ....................... 17.04 Survival of Obligations ..................... 17.05 Headings ............................................ CITY OF FORT WORTH STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS Revision: 8/23/2021 .......................................................................................... 62 .......................................................................................... 62 .......................................................................................... 62 .......................................................................................... 62 .......................................................................................... 63 .......................................................................................... 63 SCADA System Replacement 103086 ATTACHMENT 1 — AD1 007200-1 GENERAL OONDITIONS Page 1 of 63 ARTICLE 1— DEFINITIONS AND TERMINOLOGY 1.01 Defined Terms A. Whereverused in these General Conditions or in other Contract Documents, the terms listed below have the meanings indicated which are applicable to both the singular and plural thereof, and words denoting gender shall include the masculine, feminine and neuter. Said terms are generally capitalized or written in italics, but not always. When used in a context consistent with the definition of a listed -defined term, the term shall have a meaning as defined below whether capitalized or italicized or otherwise. In addition to terms specifically defined, terms with initial capital letters in the Contract Documents include references to identified articles and paragraphs, and the titles of other documents or forms. 1. Addenda —Written or graphic instruments issued prior to the opening of Bids which clarify, correct, or change the Bidding Requirements or the proposed Contract Documents. 2. Agreement —The written instrument which is evidence of the agreement between City and Contractor covering the Work. 3. Application for Payment —The form acceptable to City which is to be used by Contractor during the course of the Work in requesting progress or final payments and which is to be accompanied by such supporting documentation as is required by the Contract Documents. 4. Asbestos Any material that contains more than one percent asbestos and is friable or is releasing asbestos fibers into the air above current action levels established by the United States Occupational Safety and Health Administration. 5. Award — Authorization by the City Council for the City to enter into an Agreement. 6. Bid —The offer or proposal of a Bidder submitted on the prescribed form setting forth the prices for the Work to be performed. 7. Bidder —The individual or entity who submits a Bid directly to City. 8. Bidding Documents —The Bidding Requirements and the proposed Contract Documents (including all Addenda). 9. Bidding Requirements —The advertisement or Invitation to Bid, Instructions to Bidders, Bid security of acceptable form, if any, and the Bid Form with any supplements. 10. Business Day — A business day is defined as a day that the City conducts normal business, generally Monday through Friday, except for federal or state holidays observed by the City. 11. CalendarDay —A day consisting of 24 hours measured from midnight to the next midnight. CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1— AD1 007200-1 GENERAL OONDITIONS Page 2 of 63 12. Change Order —A document, which is prepared and approved by the City, which is signed by Contractor and City and authorizes an addition, deletion, or revision in the Work or an adjustment in the Contract Price or the Contract Time, issued on or after the Effective Date of the Agreement. 13. City— The City of Fort Worth, Texas, a home -rule municipal corporation, authorized and chartered under the Texas State Statutes, acting by its governing body through its City Manager, his designee, or agents authorized under his behalf, each of which is required by Charter to perform specific duties with responsibility for final enforcement of the contracts involving the City of Fort Worth is by Charter vested in the City Manager and is the entity with whom Contractor has entered into the Agreement and for whom the Work is to be performed. 14. City Attorney — The officially appointed City Attorney of the City of Fort Worth, Texas, or his duly authorized representative. 15. City Council - The duly elected and qualified governing body of the City of Fort Worth, Texas. 16. City Manager — The officially appointed and authorized City Manager of the City of Fort Worth, Texas, or his duly authorized representative. 17. Contract Claim —A demand or assertion by City or Contractor seeking an adjustment of Contract Price or Contract Time, or both, or other relief with respect to the terms of the Contract. A demand for money or services by a third party is not a Contract Claim. 18. Contract —The entire and integrated written document between the City and Contractor concerning the Work. The Contract contains the Agreement and all Contract Documents and supersedes prior negotiations, representations, or agreements, whether written or oral. 19. Contract Documents —Those items so designated in the Agreement. All items listed in the Agreement are Contract Documents. Approved Submittals, other Contractor submittals, and the reports and drawings of subsurface and physical conditions are not Contract Documents. 20. Contract Price —The moneys payable by City to Contractor for completion of the Work in accordance with the Contract Documents as stated in the Agreement (subject to the provisions of Paragraph 11.03 in the case of Unit Price Work). 21. Contract Time —The number of days or the dates stated in the Agreement to: (i) achieve Milestones, if any and (ii) complete the Work so that it is ready for Final Acceptance. 22. Contractor —The individual or entity with whom City has entered into the Agreement. 23. Cost of the Work —See Paragraph 11.01 of these General Conditions for definition. CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1— AD1 007200-1 GENERAL OONDITIONS Page 3 of 63 24. Damage Claims — A demand for money or services arising from the Project or Site from a third party, City or Contractor exclusive of a Contract Claim. 25. Day or day — A day, unless otherwise defined, shall mean a Calendar Day. 26. Director of Aviation — The officially appointed Director of the Aviation Department of the City of Fort Worth, Texas, or his duly appointed representative, assistant, or agents. 27. Director of Parks and Community Services — The officially appointed Director of the Parks and Community Services Department of the City of Fort Worth, Texas, or his duly appointed representative, assistant, or agents. 28. Director of Planning and Development — The officially appointed Director of the Planning and Development Department of the City of Fort Worth, Texas, or his duly appointed representative, assistant, or agents. 29. Director of Transportation Public Works — The officially appointed Director of the Transportation Public Works Department of the City of Fort Worth, Texas, or his duly appointed representative, assistant, or agents. 30. Director of Water Department — The officially appointed Director of the Water Department of the City of Fort Worth, Texas, or his duly appointed representative, assistant, or agents. 31. Drawings —That part of the Contract Documents prepared or approved by Engineer which graphically shows the scope, extent, and character of the Work to be performed by Contractor. Submittals are not Drawings as so defined. 32. Effective Date of the Agreement —The date indicated in the Agreement on which it becomes effective, but if no such date is indicated, it means the date on which the Agreement is signed and delivered by the last of the two parties to sign and deliver. 33. Engineer —The licensed professional engineer or engineering firm registered in the State of Texas performing professional services for the City. 34. Extra Work — Additional work made necessary by changes or alterations of the Contract Documents or of quantities or for other reasons for which no prices are provided in the Contract Documents. Extra work shall be part of the Work. 35. Field Order —A written order issued by City which requires changes in the Work but which does not involve a change in the Contract Price, Contract Time, or the intent of the Engineer. Field Orders are paid from Field Order Allowances incorporated into the Contract by funded work type at the time of award. 36. Final Acceptance — The written notice given by the City to the Contractor that the Work specified in the Contract Documents has been completed to the satisfaction of the City. CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1— AD1 007200-1 GENERAL OONDITIONS Page 4 of 63 37. Final Inspection — Inspection carried out by the City to verify that the Contractor has completed the Work, and each and every part or appurtenance thereof, fully, entirely, and in conformance with the Contract Documents. 38. General Requirements —Sections of Division 1 of the Contract Documents. 39. Hazardous Environmental Condition —The presence at the Site of Asbestos, PCBs, Petroleum, Hazardous Waste, Radioactive Material, or other materials in such quantities or circumstances that may present a substantial danger to persons or property exposed thereto. 40. Hazardous Waste Hazardous waste is defined as any solid waste listed as hazardous or possesses one or more hazardous characteristics as defined in the federal waste regulations, as amended from time to time. 41. Laws and Regulations —Any and all applicable laws, rules, regulations, ordinances, codes, and orders of any and all governmental bodies, agencies, authorities, and courts having jurisdiction. 42. Liens —Charges, security interests, or encumbrances upon Project funds, real property, or personal property. 43. Major Item — An Item of work included in the Contract Documents that has a total cost equal to or greater than 5% of the original Contract Price or $25,000 whichever is less. 44. Milestone —A principal event specified in the Contract Documents relating to an intermediate Contract Time prior to Final Acceptance of the Work. 45. Notice of Award —The written notice by City to the Successful Bidder stating that upon timely compliance by the Successful Bidder with the conditions precedent listed therein, City will sign and deliver the Agreement. 46. Notice to Proceed —A written notice given by City to Contractor fixing the date on which the Contract Time will commence to run and on which Contractor shall start to perform the Work specified in Contract Documents. 47. PCBs Polychlorinated biphenyls. 48. Petroleum —Petroleum, including crude oil or any fraction thereof which is liquid at standard conditions of temperature and pressure (60 degrees Fahrenheit and 14.7 pounds per square inch absolute), such as oil, petroleum, fuel oil, oil sludge, oil refuse, gasoline, kerosene, and oil mixed with other non -Hazardous Waste and crude oils. 49. Plans — See definition of Drawings. CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1— AD1 007200-1 GENERAL OONDITIONS Page 5 of 63 50. Project Schedule —A schedule, prepared and maintained by Contractor, in accordance with the General Requirements, describing the sequence and duration of the activities comprising the Contractor's plan to accomplish the Work within the Contract Time. 51. Project —The Work to be performed under the Contract Documents. 52. Project Manager —The authorized representative of the City who will be assigned to the Site. 53. Public Meeting — An announced meeting conducted by the City to facilitate public participation and to assist the public in gaining an informed view of the Project. 54. Radioactive Material —Source, special nuclear, or byproduct material as defined by the Atomic Energy Act of 1954 (42 USC Section 2011 et seq.) as amended from time to time. 55. Regular Working Hours — Hours beginning at 7:00 a.m. and ending at 6:00 p.m., Monday thru Friday (excluding legal holidays). 56. Samples —Physical examples of materials, equipment, or workmanship that are representative of some portion of the Work and which establish the standards by which such portion of the Work will be judged. 57. Schedule of Submittals —A schedule, prepared and maintained by Contractor, of required submittals and the time requirements to support scheduled performance of related construction activities. 58. Schedule of Values —A schedule, prepared and maintained by Contractor, allocating portions of the Contract Price to various portions of the Work and used as the basis for reviewing Contractor's Applications for Payment. 59. Site —Lands or areas indicated in the Contract Documents as being furnished by City upon which the Work is to be performed, including rights -of -way, permits, and easements for access thereto, and such other lands furnished by City which are designated for the use of Contractor. 60. Specifications —That part of the Contract Documents consisting of written requirements for materials, equipment, systems, standards and workmanship as applied to the Work, and certain administrative requirements and procedural matters applicable thereto. Specifications may be specifically made a part of the Contract Documents by attachment or, if not attached, may be incorporated by reference as indicated in the Table of Contents (Division 00 00 00) of each Project. 61. Subcontractor An individual or entity having a direct contract with Contractor or with any other Subcontractor for the performance of a part of the Work at the Site. CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1— AD1 007200-1 GENERAL OONDITIONS Page 6 of 63 62. Submittals All drawings, diagrams, illustrations, schedules, and other data or information which are specifically prepared or assembled by or for Contractor and submitted by Contractor to illustrate some portion of the Work. 63. Substantial Completion — The stage in the progress of the Project when the Work is sufficiently complete in accordance with the Contract Documents for Final Inspection. 64. Successful Bidder —The Bidder submitting the lowest and most responsive Bid to whom City makes an Award. 65. Superintendent— The representative of the Contractor who is available at all times and able to receive instructions from the City and to act for the Contractor. 66. Supplementary Conditions —That part of the Contract Documents which amends or supplements these General Conditions. 67. Supplier —A manufacturer, fabricator, supplier, distributor, materialman, or vendor having a direct contract with Contractor or with any Subcontractor to furnish materials or equipment to be incorporated in the Work by Contractor or Subcontractor. 68. Underground Facilities —All underground pipelines, conduits, ducts, cables, wires, manholes, vaults, tanks, tunnels, or other such facilities or attachments, and any encasements containing such facilities, including but not limited to, those that convey electricity, gases, steam, liquid petroleum products, telephone or other communications, cable television, water, wastewater, storm water, other liquids or chemicals, or traffic or other control systems. 69 Unit Price Work —See Paragraph 11.03 of these General Conditions for definition. 70. Weekend Working Hours — Hours beginning at 9:00 a.m. and ending at 5:00 p.m., Saturday, Sunday or legal holiday, as approved in advance by the City. 71. Work —The entire construction or the various separately identifiable parts thereof required to be provided under the Contract Documents. Work includes and is the result of performing or providing all labor, services, and documentation necessary to produce such construction including any Change Order or Field Order, and furnishing, installing, and incorporating all materials and equipment into such construction, all as required by the Contract Documents. 72. Working Day — A working day is defied as a day, not including Saturdays, Sundays, or legal holidays authorized by the City for contract purposes, in which weather or other conditions not under the control of the Contractor will permit the performance of the principal unit of work underway for a continuous period of not less than 7 hours between 7 a.m. and 6 p.m. 1.02 Terminology A. The words and terms discussed in Paragraph 1.02.13 through E are not defined but, when used in the Bidding Requirements or Contract Documents, have the indicated meaning. B. Intent of Certain Terms or Adjectives: CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1— AD1 007200-1 GENERAL OONDITIONS Page 7 of 63 The Contract Documents include the terms "as allowed," "as approved," "as ordered," "as directed" or terms of hike effect or import to authorize an exercise of judgment by City. In addition, the adjectives "reasonable," "suitable," "acceptable," "proper," "satisfactory," or adjectives of hike effect or import are used to describe an action or determination of City as to the Work. It is intended that such exercise of professional judgment, action, or determination will be solely to evaluate, in general, the Work for compliance with the information in the Contract Documents and with the design concept of the Project as a functioning whole as shown or indicated in the Contract Documents (unless there is a specific statement indicating otherwise). C. Defective: 1. The word "defective," when modifying the word "Work," refers to Work that is unsatisfactory, faulty, or deficient in that it: a. does not conform to the Contract Documents; or b. does not meet the requirements of any applicable inspection, reference standard, test, or approval referred to in the Contract Documents; or c. has been damaged prior to City's written acceptance. D. Furnish, Install, Perform, Provide: 1. The word "Furnish" or the word "Install" or the word "Perform" or the word "Provide" or the word "Supply," or any combination or similar directive or usage thereof, shall mean furnishing and incorporating in the Work including all necessary labor, materials, equipment, and everything necessary to perform the Work indicated, unless specifically limited in the context used. E. Unless stated otherwise in the Contract Documents, words or phrases that have a well-known technical or construction industry or trade meaning are used in the Contract Documents in accordance with such recognized meaning. ARTICLE 2 — PRELIMINARY MATTERS 2.01 Copies of Documents City shall furnish to Contractor one (1) original executed copy and one (1) electronic copy of the Contract Documents, and four (4) additional copies of the Drawings. Additional copies will be furnished upon request at the cost of reproduction. 2.02 Commencement of Contract Time; Notice to Proceed The Contract Time will commence to run on the day indicated in the Notice to Proceed. A Notice to Proceed maybe given no earlier than 14 days after the Effective Date of the Agreement, unless agreed to by both parties in writing. CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1— AD1 007200-1 GENERAL OONDITIONS Page 8 of 63 2.03 Starting the Work Contractor shall start to perform the Work on the date when the Contract Time commences to run. No Work shall be done at the Site prior to the date on which the Contract Time commences to run. 2.04 Before Starting Construction Baseline Schedules: Submit in accordance with the Contract Documents, and prior to starting the Work. 2.05 Preconstruction Conference Before any Work at the Site is started, the Contractor shall attend a Preconstruction Conference as specified in the Contract Documents. 2.06 Public Meeting Contractor may not mobilize any equipment, materials or resources to the Site prior to Contractor attending the Public Meeting as scheduled by the City. 2.07 Initial Acceptance of Schedules No progress payment shall be made to Contractor until acceptable schedules are submitted to City in accordance with the Schedule Specification as provided in the Contract Documents. ARTICLE 3 — CONTRACT DOCUMENTS: INTENT, AMENDING, REUSE 3.01 Intent A. The Contract Documents are complementary; what is required by one is as binding as if required by all. B. It is the intent of the Contract Documents to describe a functionally complete project (or part thereof) to be constructed in accordance with the Contract Documents. Any labor, documentation, services, materials, or equipment that reasonably may be inferred from the Contract Documents or from prevailing custom or trade usage as being required to produce the indicated result will be provided whether or not specifically called for, at no additional cost to City. C. Clarifications and interpretations of the Contract Documents shall be issued by City. D. The Specifications may vary in form, format and style. Some Specification sections maybe written in varying degrees of streamlined or declarative style and some sections may be relatively narrative by comparison. Omission of such words and phrases as "the Contractor shall," "in conformity with," "as shown," or "as specified" are intentional in streamlined sections. Omitted words and phrases shall be supplied by inference. Similar types of provisions may appear in various parts of a section or articles within a part depending on the format of the CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1— AD1 007200-1 GENERAL OONDITIONS Page 9 of 63 section. The Contractor shall not take advantage of any variation of form, format or style in making Contract Claims. E. The cross referencing of specification sections under the subparagraph heading "Related Sections include but are not necessarily limited to:" and elsewhere within each Specification section is provided as an aid and convenience to the Contractor. The Contractor shall not rely on the cross referencing provided and shall be responsible to coordinate the entire Work under the Contract Documents and provide a complete Project whether or not the cross referencing is provided in each section or whether or not the cross referencing is complete. 3.02 Reference Standards A. Standards, Specifications, Codes, Laws, and Regulations 1. Reference to standards, specifications, manuals, or codes of any technical society, organization, or association, or to Laws or Regulations, whether such reference be specific or by implication, shall mean the standard, specification, manual, code, or Laws or Regulations in effect at the time of opening of Bids (or on the Effective Date of the Agreement if there were no Bids), except as may be otherwise specifically stated in the Contract Documents. 2. No provision of any such standard, specification, manual, or code, or any instruction of a Supplier, shall be effective to change the duties or responsibilities of City, Contractor, or any of their subcontractors, consultants, agents, or employees, from those set forth in the Contract Documents. No such provision or instruction shall be effective to assign to City, or any of its officers, directors, members, partners, employees, agents, consultants, or subcontractors, any duty or authority to supervise or direct the performance of the Work or any duty or authority to undertake responsibility inconsistent with the provisions of the Contract Documents. 3.03 Reporting and Resolving Discrepancies A. Reporting Discrepancies: 1. Contractor's Review of Con tract Documents Before Starting Work: Before undertaking each part of the Work, Contractor shall carefully study and compare the Contract Documents and check and verify pertinent figures therein against all applicable field measurements and conditions. Contractor shall promptly report in writing to City any conflict, error, ambiguity, or discrepancy which Contractor discovers, or has actual knowledge of, and shall obtain a written interpretation or clarification from City before proceeding with any Work affected thereby. 2. Contractor's Review of Contract Documents During Performance of Work: If, during the performance of the Work, Contractor discovers any conflict, error, ambiguity, or discrepancy within the Contract Documents, or between the Contract Documents and (a) any applicable Law or Regulation , (b) any standard, specification, manual, or code, or (c) any instruction of any Supplier, then Contractor shall promptly report it to City in writing. Contractor shall not proceed with the Work affected thereby (except in an emergency as required by Paragraph CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1— AD1 007200-1 GENERAL OONDITIONS Page 10 of 63 6.17.A) until an amendment or supplement to the Contract Documents has been issued by one of the methods indicated in Paragraph 3.04. 3. Contractor shall not be liable to City for failure to report any conflict, error, ambiguity, or discrepancy in the Contract Documents unless Contractor had actual knowledge thereof B. Resolving Discrepancies: Except as may be otherwise specifically stated in the Contract Documents, the provisions of the Contract Documents shall take precedence in resolving any conflict, error, ambiguity, or discrepancy between the provisions of the Contract Documents and the provisions of any standard, specification, manual, or the instruction of any Supplier (whether or not specifically incorporated by reference in the Contract Documents). 2. In case of discrepancies, figured dimensions shall govern over scaled dimensions, Plans shall govern over Specifications, Supplementary Conditions shall govern over General Conditions and Specifications, and quantities shown on the Plans shall govern over those shown in the proposal. 3.04 Amending and Supplementing Contract Documents A. The Contract Documents may be amended to provide for additions, deletions, and revisions in the Work or to modify the terms and conditions thereof by a Change Order. B. The requirements of the Contract Documents may be supplemented, and minor variations and deviations in the Work not involving a change in Contract Price or Contract Time, may be authorized, by one or more of the following ways: 1. A Field Order; 2. City's review of a Submittal (subject to the provisions of Paragraph 6.18.C); or 3. City's written interpretation or clarification. 3.05 Reuse of Documents A. Contractor and any Subcontractor or Supplier shall not: 1. have or acquire any title to or ownership rights in any of the Drawings, Specifications, or other documents (or copies of any thereof) prepared by or bearing the seal of Engineer, including electronic media editions; or 2. reuse any such Drawings, Specifications, other documents, or copies thereof on extensions of the Project or any other project without written consent of City and specific written verification or adaptation by Engineer. CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1— AD1 007200-1 GENERAL OONDITIONS Page 11 of 63 B. The prohibitions of this Paragraph 3.05 will survive final payment, or termination of the Contract. Nothing herein shall preclude Contractor from retaining copies of the Contract Documents for record purposes. 3.06 Electronic Data A. Unless otherwise stated in the Supplementary Conditions, the data furnished by City or Engineer to Contractor, or by Contractor to City or Engineer, that may be relied upon are limited to the printed copies included in the Contract Documents (also known as hard copies) and other Specifications referenced and located on the City's on-line electronic document management and collaboration system site. Files in electronic media format of text, data, graphics, or other types are furnished only for the convenience of the receiving party. Any conclusion or information obtained or derived from such electronic files will be atthe user's sole risk. Ifthere is a discrepancy between the electronic files and the hard copies, the hard copies govern. B. When transferring documents in electronic media format, the transferring party makes no representations as to long term compatibility, usability, or readability of documents resulting from the use of software application packages, operating systems, or computer hardware differing from those used by the data's creator. ARTICLE 4 — AVAILABILITY OF LANDS; SUBSURFACE AND PHYSICAL CONDITIONS; HAZARDOUS ENVIRONMENTAL CONDITIONS; REFERENCE POINTS 4.01 Availability of Lands A. City shall furnish the Site. City shall notify Contractor of any encumbrances or restrictions not of general application but specifically related to use of the Site with which Contractor must comply in performing the Work. City will obtain in a timely manner and pay for easements for permanent structures or permanent changes in existing facilities. 1. The City has obtained or anticipates acquisition of and/or access to right-of-way, and/or easements. Any outstanding right-of-way and/or easements are anticipated to be acquired in accordance with the schedule set forth in the Supplementary Conditions. The Project Schedule submitted by the Contractor in accordance with the Contract Documents must consider any outstanding right-of-way, and/or easements. 2. The City has or anticipates removing and/or relocating utilities, and obstructions to the Site. Any outstanding removal or relocation of utilities or obstructions is anticipated in accordance with the schedule set forth in the Supplementary Conditions. The Project Schedule submitted by the Contractor in accordance with the Contract Documents must consider any outstanding utilities or obstructions to be removed, adjusted, and/or relocated by others. B. Upon reasonable written request, City shall furnish Contractor with a current statement of record legal title and legal description of the lands upon which the Work is to be performed. CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1— AD1 007200-1 GENERAL OONDITIONS Page 12 of 63 C. Contractor shall provide for all additional lands and access thereto that may be required for construction facilities or storage of materials and equipment. 4.02 Subsurface andPhysical Conditions A. Reports and Drawings: The Supplementary Conditions identify: 1. those reports known to City of explorations and tests of subsurface conditions at or contiguous to the Site; and 2. those drawings known to City of physical conditions relating to existing surface or subsurface structures at the Site (except Underground Facilities). B. Limited Reliance by Contractor on Technical Data Authorized: Contractor may rely upon the accuracy of the "technical data" contained in such reports and drawings, but such reports and drawings are not Contract Documents. Such "technical data" is identified in the Supplementary Conditions. Contractor may not make any Contract Claim against City, or any of their officers, directors, members, partners, employees, agents, consultants, or subcontractors with respect to: 1. the completeness of such reports and drawings for Contractor's purposes, including, but not limited to, any aspects of the means, methods, techniques, sequences, and procedures of construction to be employed by Contractor, and safety precautions and programs incident thereto; or 2. other data, interpretations, opinions, and information contained in such reports or shown or indicated in such drawings; or 3. any Contractor interpretation of or conclusion drawn from any "technical data" or any such other data, interpretations, opinions, or information. 4.03 Differing Subsurface or Physical Conditions A. Notice: If Contractor believes that any subsurface or physical condition that is uncovered or revealed either: 1. is of such a nature as to establish that any "technical data" on which Contractor is entitled to rely as provided in Paragraph 4.02 is materially inaccurate; or 2. is of such a nature as to require a change in the Contract Documents; or 3. differs materially from that shown or indicated in the Contract Documents; or 4. is of an unusual nature, and differs materially from conditions ordinarily encountered and generally recognized as inherent in work of the character provided for in the Contract Documents; CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1— AD1 007200-1 GENERAL CONDITIONS Page 13 of 63 then Contractor shall, promptly after becoming aware thereof and before further disturbing the subsurface or physical conditions or performing any Work in connection therewith (except in an emergency as required by Paragraph 6.17.A), notify City in writing about such condition. B. Possible Price and Time Adjustments Contractor shall not be entitled to any adjustment in the Contract Price or Contract Time if: 1. Contractor knew of the existence of such conditions at the time Contractor made a final commitment to City with respect to Contract Price and Contract Time by the submission of a Bid or becoming bound under a negotiated contract; or 2. the existence of such condition could reasonably have been discovered or revealed as a result of the examination of the Contract Documents or the Site; or 3. Contractor failed to give the written notice as required by Paragraph 4.03.A. 4.04 Underground Facilities A. Shown or Indicated.• The information and data shown or indicated in the Contract Documents with respect to existing Underground Facilities at or contiguous to the Site is based on information and data furnished to City or Engineer by the owners of such Underground Facilities, including City, or by others. Unless it is otherwise expressly provided in the Supplementary Conditions: 1. City and Engineer shall not be responsible for the accuracy or completeness of any such information or data provided by others; and 2. the cost of all of the following will be included in the Contract Price, and Contractor shall have full responsibility for: a. reviewing and checking all such information and data; b. locating all Underground Facilities shown or indicated in the Contract Documents; c. coordination and adjustment of the Work with the owners of such Underground Facilities, including City, during construction; and d. the safety and protection of all such Underground Facilities and repairing any damage thereto resulting from the Work. B. Not Shown orindicated: 1. If an Underground Facility which conflicts with the Work is uncovered or revealed at or contiguous to the Site which was not shown or indicated, or not shown or indicated with reasonable accuracy in the Contract Documents, Contractor shall, promptly after becoming aware thereof and before further disturbing conditions affected thereby or performing any CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: &23/2MI ATTACHMENT 1— AD1 007200-1 GENERAL OONDITIONS Page 14 of 63 Work in connection therewith (except in an emergency as required by Paragraph 6.17.A), identify the owner of such Underground Facility and give notice to that owner and to City. City will review the discovered Underground Facility and determine the extent, if any, to which a change may be required in the Contract Documents to reflect and document the consequences of the existence or location of the Underground Facility. Contractor shall be responsible for the safety and protection of such discovered Underground Facility. 2. If City concludes that a change in the Contract Documents is required, a Change Order may be issued to reflect and document such consequences. 3. Verification of existing utilities, structures, and service lines shall include notification of all utility companies a minimum of 48 hours in advance of construction including exploratory excavation if necessary. 4.05 Reference Points A. City shall provide engineering surveys to establish reference points for construction, which in City's judgment are necessary to enable Contractor to proceed with the Work. City will provide construction stakes or other customary method of marking to establish line and grades for roadway and utility construction, centerlines and benchmarks for bridgework. Contractor shall protect and preserve the established reference points and property monuments, and shall make no changes or relocations. Contractor shall report to City whenever any reference point or property monument is lost or destroyed or requires relocation because of necessary changes in grades or locations. The City shall be responsible for the replacement or relocation of reference points or property monuments not carelessly or willfully destroyed by the Contractor. The Contractor shall notify City in advance and with sufficient time to avoid delays. B. Whenever, in the opinion of the City, any reference point or monument has been carelessly or willfully destroyed, disturbed, or removed by the Contractor or any of his employees, the full cost for replacing such points plus 25% will be charged against the Contractor, and the full amount will be deducted from payment due the Contractor. 4.06 Hazardous Environmental Condition at Site A. Reports and Drawings: The Supplementary Conditions identify those reports and drawings known to City relating to Hazardous Environmental Conditions that have been identified at the Site. B. Limited Reliance by Contractor on Technical Data Authorized: Contractor may rely upon the accuracy of the "technical data" contained in such reports and drawings, but such reports and drawings are not Contract Documents. Such "technical data" is identified in the Supplementary Conditions. Contractor may not make any Contract Claim against City, or any of their officers, directors, members, partners, employees, agents, consultants, or subcontractors with respect to: 1. the completeness of such reports and drawings for Contractor's purposes, including, but not limited to, any aspects of the means, methods, techniques, sequences and procedures of CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1— AD1 007200-1 GENERAL OONDITIONS Page 15 of 63 construction to be employed by Contractor and safety precautions and programs incident thereto; or 2. other data, interpretations, opinions and information contained in such reports or shown or indicated in such drawings; or 3. any Contractor interpretation of or conclusion drawn from any "technical data" or any such other data, interpretations, opinions or information. C. Contractor shall not be responsible for any Hazardous Environmental Condition uncovered or revealed at the Site which was not shown or indicated in Drawings or Specifications or identified in the Contract Documents to be within the scope of the Work. Contractor shall be responsible for a Hazardous Environmental Condition created with any materials brought to the Site by Contractor, Subcontractors, Suppliers, or anyone else for whom Contractor is responsible. D. If Contractor encounters a Hazardous Environmental Condition or if Contractor or anyone for whom Contractor is responsible creates a Hazardous Environmental Condition, Contractor shall immediately: (i) secure or otherwise isolate such condition; (ii) stop all Work in connection with such condition and in any area affected thereby (except in an emergency as required by Paragraph 6.17.A); and (iii) notify City (and promptly thereafter confirm such notice in writing). City may consider the necessity to retain a qualified expert to evaluate such condition or take corrective action, if any. E. Contractor shall not be required to resume Work in connection with such condition or in any affectedarea until after City has obtained any required permits related thereto and delivered written notice to Contractor: (i) specifying that such condition and any affected area is or has been rendered suitable for the resumption of Work; or (ii) specifying any special conditions under which such Work may be resumed. F. If after receipt of such written notice Contractor does not agree to resume such Work based on a reasonable belief it is unsafe, or does not agree to resume such Work under such special conditions, then City may order the portion of the Work that is in the area affected by such condition to be deleted from the Work. City may have such deleted portion of the Work performed by City's own forces or others. G. To the fullest extentpermitted by Laws and Regulations, Contractor shall indemnify and hold harmless City, from and against all claims, costs, losses, and damages (including but not limited to all fees and charges of engineers, architects, attorneys, and other professionals and all court or arbitration or other dispute resolution costs) arising out of or relating to a Hazardous Environmental Condition created by Contractoror by anyoneforwhom Contractor is responsible. Nothing in this Paragraph 4.06.G shall obligate Contractor to indemnify any individual or entity from and against the consequences of that individual's or entity's own negligence. H. The provisions of Paragraphs 4.02, 4.03, and 4.04 do not apply to a Hazardous Environmental Condition uncovered or revealed at the Site. CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1- AD1 007200-1 GENERAL OONDITIONS Page 16 of 63 ARTICLE 5 — BONDS AND INSURANCE 5.01 Licensed Sureties and Insurers All bonds and insurance required by the Contract Documents to be purchased and maintained by Contractor shall be obtained from surety or insurance companies that are duly licensed or authorized in the State of Texas to issue bonds or insurance policies for the limits and coverages so required. Such surety and insurance companies shall also meet such additional requirements and qualifications as may be provided in the Supplementary Conditions. 5.02 Performance, Payment, and Maintenance Bonds A. Contractor shall furnish performance and payment bonds, in accordance with Texas Government Code Chapter 2253 or successor statute, each in an amount equal to the Contract Price as security for the faithful performance and payment of all of Contractor's obligations under the Contract Documents. B. Contractor shall furnish maintenance bonds in an amount equal to the Contract Price as security to protect the City against any defects in any portion of the Work described in the Contract Documents. Maintenance bonds shall remain in effect for two (2) years after the date of Final Acceptance by the City. C. All bonds shall be in the form prescribed by the Contract Documents except as provided otherwise by Laws or Regulations, and shall be executed by such sureties as are named in the list of "Companies Holding Certificates of Authority as Acceptable Sureties on Federal Bonds and as Acceptable Reinsuring Companies" as published in Circular 570 (amended) by the Financial Management Service, Surety Bond Branch, U.S. Department of the Treasury. All bonds signed by an agent or attorney -in -fact must be accompanied by a sealed and dated power of attorney which shall show that it is effective on the date the agent or attorney -in -fact signed each bond. D. If the surety on any bond furnished by Contractor is declared bankrupt or becomes insolvent or its right to do business is terminated in the State of Texas or it ceases to meet the requirements of Paragraph 5.02.C, Contractor shall promptly notify City and shall, within 30 days after the event giving rise to such notification, provide another bond and surety, both of which shall comply with the requirements of Paragraphs 5.01 and 5.02.C. 5.03 Certificates of Insurance Contractor shall deliver to City, with copies to each additional insured and loss payee identified in the Supplementary Conditions, certificates of insurance (other evidence of insurance requested by City or any other additional insured) in at least the minimum amount as specified in the Supplementary Conditions which Contractor is required to purchase and maintain. 1. The certificate of insurance shall document the City, and all identified entities named in the Supplementary Conditions as "Additional Insured" on all liability policies. CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1— AD1 007200-1 GENERAL OONDITIONS Page 17 of 63 2. The Contractor's general liability insurance shall include a, "per project" or "per location", endorsement, which shall be identified in the certificate of insurance provided to the City. 3. The certificate shall be signed by an agent authorized to bind coverage on behalf of the insured, be complete in its entirety, and show complete insurance carrier names as listed in the current A.M. Best Property & Casualty Guide 4. The insurers for all policies must be licensed and/or approved to do business in the State of Texas. Except for workers' compensation, all insurers must have a minimum rating of A-: VII in the current A. M. Best Key Rating Guide or have reasonably equivalent financial strength and solvency to the satisfaction of Risk Management. If the rating is below that required, written approval of City is required. 5. All applicable policies shall include a Waiver of Subrogation (Rights of Recovery) in favor of the City. In addition, the Contractor agrees to waive all rights of subrogation against the Engineer (if applicable), and each additional insured identified in the Supplementary Conditions 6. Failure of the City to demand such certificates or other evidence of full compliance with the insurance requirements or failure of the City to identify a deficiency from evidence that is provided shall not be construed as a waiver of Contractor's obligation to maintain such lines of insurance coverage. 7. If insurance policies are not written for specified coverage limits, an Umbrella or Excess Liability insurance for any differences is required. Excess Liability shall follow form of the primary coverage. 8. Unless otherwise stated, all required insurance shall be written on the "occurrence basis". If coverage is underwritten on a claims -made basis, the retroactive date shall be coincident with or prior to the date of the effective date of the agreement and the certificate of insurance shall state that the coverage is claims -made and the retroactive date. The insurance coverage shall be maintained for the duration of the Contract and for three (3) years following Final Acceptance provided under the Contract Documents or for the warranty period, whichever is longer. An annual certificate of insurance submitted to the City shall evidence such insurance coverage. 9. Policies shall have no exclusions by endorsements, which, neither nullify or amend, the required lines of coverage, nor decrease the limits of said coverage unless such endorsements are approved in writing by the City. In the event a Contract has been bid or executed and the exclusions are determined to be unacceptable or the City desires additional insurance coverage, and the City desires the contractor/engineer to obtain such coverage, the contract price shall be adjusted by the cost of the premium for such additional coverage plus 10%. 10. Any self -insured retention (SIR), in excess of $25,000.00, affecting required insurance coverage shall be approved by the City in regards to asset value and stockholders' equity. In CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1- AD1 007200-1 GENERAL OONDITIONS Page 18 of 63 lieu of traditional insurance, alternative coverage maintained through insurance pools or risk retention groups, must also be approved by City. 11. Any deductible in excess of $5,000.00, for any policy that does not provide coverage on a first -dollar basis, must be acceptable to and approved by the City. 12. City, at its sole discretion, reserves the right to review the insurance requirements and to make reasonable adjustments to insurance coverage's and their limits when deemed necessary and prudent by the City based upon changes in statutory law, court decision or the claims history of the industry as well as of the contracting party to the City. The City shall be required to provide prior notice of 90 days, and the insurance adjustments shall be incorporated into the Work by Change Order. 13. City shall be entitled, upon written request and without expense, to receive copies of policies and endorsements thereto and may make any reasonable requests for deletion or revision or modifications of particular policy terms, conditions, limitations, or exclusions necessary to conform the policy and endorsements to the requirements of the Contract. Deletions, revisions, or modifications shall not be required where policy provisions are established by law or regulations binding upon either party or the underwriter on any such policies. 14. City shall not be responsible for the direct payment of insurance premium costs for Contractor's insurance. 5.04 Contractor's Insurance A. Workers Compensation and Employers' Liability. Contractor shall purchase and maintain such insurance coverage with limits consistent with statutory benefits outlined in the Texas Workers' Compensation Act (Texas Labor Code, Ch. 406, as amended), and minimum limits for Employers' Liability as is appropriate for the Work being performed and as will provide protection from claims set forth below which may arise out of or result from Contractor's performance of the Work and Contractor's other obligations under the Contract Documents, whether it is to be performed by Contractor, any Subcontractor or Supplier, or by anyone directly or indirectly employed by any of them to perform any of the Work, or by anyone for whose acts any of them may be liable: 1. claims under workers' compensation, disability benefits, and other similar employee benefit acts; 2. claims for damages because of bodily injury, occupational sickness or disease, or death of Contractor's employees. B. Commercial General Liability. Coverage shall include but not be limited to covering liability (bodily injury or property damage) arising from: premises/operations, independent contractors, products/completed operations, personal injury, and liability under an insured contract. Insurance shall be provided on an occurrence basis, and as comprehensive as the current Insurance Services Office (ISO) policy. This insurance shall apply as primary insurance with respect to any other CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1— AD1 007200-1 GENERAL OONDITIONS Page 19 of 63 insurance or self-insurance programs afforded to the City. The Commercial General Liability policy, shall have no exclusions by endorsements that would alter of nullify premises/operations, products/completed operations, contractual, personal injury, or advertising injury, which are normally contained with the policy, unless the City approves such exclusions in writing. For construction projects that present a substantial completed operation exposure, the City may require the contractor to maintain completed operations coverage for a minimum of no less than three (3) years following the completion of the project (if identified in the Supplementary Conditions). C. Automobile Liability. A commercial business auto policy shall provide coverage on "any auto', defined as autos owned, hired and non -owned and provide indemnity for claims for damages because bodily injury or death of any person and or property damage arising out of the work, maintenance or use of any motor vehicle by the Contractor, any Subcontractor or Supplier, or by anyone directly or indirectly employed by any of them to perform any of the Work, or by anyone for whose acts any of them may be liable. D. Railroad Protective Liability. If any of the work or any warranty work is within the limits of railroad right-of-way, the Contractor shall comply with the requirements identified in the Supplementary Conditions. E. Notification of Policy Cancellation: Contractor shall immediately notify City upon cancellation or other loss of insurance coverage. Contractor shall stop work until replacement insurance has been procured. There shall be no time credit for days not worked pursuant to this section. 5.05 Acceptance of Bondsandlnsurance, Option to Replace If City has any objection to the coverage afforded by or other provisions of the bonds or insurance required to be purchased and maintained by the Contractor in accordance with Article 5 on the basis of non-conformance with the Contract Documents, the City shall so notify the Contractor in writing within 10 Business Days afterreceipt of the certificates (or other evidence requested). Contractor shall provide to the City such additional information in respect of insurance provided as the City may reasonably request. If Contractor does not purchase or maintain all of the bonds and insurance required by the Contract Documents, the City shall notify the Contractor in writing of such failure prior to the start of the Work, or of such failure to maintain prior to any change in the required coverage. ARTICLE 6 — CONTRACTOR'S RESPONSIBILITIES 6.01 Supervision and Superintendence A. Contractor shall supervise, inspect, and direct the Work competently and efficiently, devoting such attention thereto and applying such skills and expertise as may be necessary to perform the Work in accordance with the Contract Documents. Contractor shall be solely responsible for the means, methods, techniques, sequences, and procedures of construction. CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1— AD1 007200-1 GENERAL OONDITIONS Page 20 of 63 B. At all times during the progress of the Work, Contractor shall assign a competent, English- speaking, Superintendent who shall not be replaced without written notice to City. The Superintendent will be Contractor's representative at the Site and shall have authority to act on behalf of Contractor. All communication given to or received from the Superintendent shall be binding on Contractor. C. Contractor shall notify the City 24 hours prior to moving areas during the sequence of construction. 6.02 Labor; Working Hours A. Contractor shall provide competent, suitably qualified personnel to perform construction as required by the Contract Documents. Contractor shall at all times maintain good discipline and order at the Site. B. Except as otherwise required for the safety or protection of persons or the Work or property at the Site or adjacent thereto, and except as otherwise stated in the Contract Documents, all Work at the Site shall be performed during Regular Working Hours. Contractor will not permit the performance of Work beyond Regular Working Hours or for Weekend Working Hours without City's written consent (which will not be unreasonably withheld). Written request (by letter or electronic communication) to perform Work: 1. for beyond Regular Working Hours request must be made by noon at least two (2) Business Days prior 2. for Weekend Working Hours request must be made by noon of the preceding Thursday 3. for legal holidays request must be made by noon two Business Days prior to the legal holiday. 6.03 Services, Materials, and Equipment A. Unless otherwise specified in the Contract Documents, Contractor shall provide and assume full responsibility for all services, materials, equipment, labor, transportation, construction equipment and machinery, tools, appliances, fuel, power, light, heat, telephone, water, sanitary facilities, temporary facilities, and all other facilities and incidentals necessary for the performance, Contractor required testing, start-up, and completion of the Work. B. All materials and equipment incorporated into the Work shall be as specified or, if not specified, shall be of good quality and new, except as otherwise provided in the Contract Documents. All special warranties and guarantees required by the Specifications shall expressly run to the benefit of City. If required by City, Contractor shall furnish satisfactory evidence (including reports of required tests) as to the source, kind, and quality of materials and equipment. CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1— AD1 007200-1 GENERAL OONDITIONS Page 21 of 63 C. All materials and equipment to be incorporated into the Work shall be stored, applied, installed, connected, erected, protected, used, cleaned, and conditioned in accordance with instructions of the applicable Supplier, except as otherwise may be provided in the Contract Documents. D. All items of standard equipment to be incorporated into the Work shall be the latest model at the time of bid, unless otherwise specified. 6.04 Project Schedule A. Contractor shall adhere to the Project Schedule established in accordance with Paragraph 2.07 and the General Requirements as it may be adjusted from time to time as provided below. Contractor shall submit to City for acceptance (to the extent indicated in Paragraph 2.07 and the General Requirements) proposed adjustments in the Project Schedule that will not result in changing the Contract Time. Such adjustments will comply with any provisions of the General Requirements applicable thereto. 2. Contractor shall submit to City a monthly Project Schedule with a monthly progress payment for the duration of the Contract in accordance with the schedule specification 0132 16. 3. Proposed adjustments in the Project Schedule that will change the Contract Time shall be submitted in accordance with the requirements of Article 12. Adjustments in Contract Time may only be made by a Change Order. 6.05 Substitutes and "Or -Equals" A. Whenever an item of material or equipment is specified or described in the Contract Documents by using the name of a proprietary item or the name of a particular Supplier, the specification or description is intended to establish the type, function, appearance, and quality required. Unless the specification or description contains or is followed by words reading that no like, equivalent, or "or -equal" item or no substitution is permitted, other items of material or equipment of other Suppliers may be submitted to City for review under the circumstances described below. "Or -Equal "Items: If in City's sole discretion an item of material or equipment proposed by Contractor is functionally equal to that named and sufficiently similar so that no change in related Work will be required, it may be considered by City as an "or -equal" item, in which case review and approval of the proposed item may, in City's sole discretion, be accomplished without compliance with some or all of the requirements for approval of proposed substitute items. For the purposes of this Paragraph 6.05.A.1, a proposed item of material or equipment will be considered functionally equal to an item so named if: a. the City determines that: 1) it is at least equal in materials of construction, quality, durability, appearance, strength, and design characteristics; CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1— AD1 007200-1 GENERAL OONDITIONS Page 22 of 63 2) it will reliably perform at least equally well the function and achieve the results imposed by the design concept of the completed Project as a functioning whole; and 3) it has a proven record of performance and availability of responsive service; and b. Contractor certifies that, if approved and incorporated into the Work: 1) there will be no increase in cost to the City or increase in Contract Time; and 2) it will conform substantially to the detailed requirements of the item named in the Contract Documents. 2. Substitute Items: a. If in City's sole discretion an item of material or equipment proposed by Contractor does not qualify as an "or -equal" item under Paragraph 6.05.A.1, it may be submitted as a proposed substitute item. b. Contractor shall submit sufficient information as provided below to allow City to determine if the item of material or equipment proposed is essentially equivalent to that named and an acceptable substitute therefor. Requests for review of proposed substitute items of material or equipment will not be accepted by City from anyone other than Contractor. c. Contractor shall make written application to City for review of a proposed substitute item of material or equipment that Contractor seeks to furnish or use. The application shall comply with Section 0125 00 and: 1) shall certify that the proposed substitute item will: a) perform adequately the functions and achieve the results called for by the general design; b) be similar in substance to that specified; c) be suited to the same use as that specified; and 2) will state: a) the extent, if any, to which the use of the proposed substitute item will prejudice Contractor's achievement of final completion on time; b) whether use of the proposed substitute item in the Work will require a change in any of the Contract Documents (or in the provisions of any other direct contract with City for other work on the Project) to adapt the design to the proposed substitute item; CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1- AD1 007200-1 GENERAL OONDITIONS Page 23 of 63 c) whether incorporation or use of the proposed substitute item in connection with the Work is subject to payment of any license fee or royalty; and 3) will identify: a) all variations of the proposed substitute item from that specified; b) available engineering, sales, maintenance, repair, and replacement services; and 4) shall contain an itemized estimate of all costs or credits that will result directly or indirectly from use of such substitute item, including costs of redesign and Damage Claims of other contractors affected by any resulting change. B. Substitute Construction Methods or Procedures: If a specific means, method, technique, sequence, or procedure of construction is expressly required by the Contract Documents, Contractor may furnish or utilize a substitute means, method, technique, sequence, or procedure of construction approved by City. Contractor shall submit sufficient information to allow City, in City's sole discretion, to determine that the substitute proposed is equivalent to that expressly called for by the Contract Documents. Contractor shall make written application to City for review in the same manner as those provided in Paragraph 6.05.A.2. C. City's Evaluation: City will be allowed a reasonable time within which to evaluate each proposal or Submittal made pursuant to Paragraphs 6.05.A and 6.05.13. City may require Contractor to furnish additional data about the proposed substitute. City will be the sole judge of acceptability. No "or -equal" or substitute will be ordered, installed or utilized until City's review is complete, which will be evidenced by a Change Order in the case of a substitute and an accepted Submittal for an "or -equal." City will advise Contractor in writing of its determination. D. Special Guarantee: City may require Contractor to furnish at Contractor's expense a special performance guarantee, warranty, or other surety with respect to any substitute. Contractor shall indemnify and hold harmless City and anyone directly or indirectly employed by themfrom and against any and all claims, damages, losses and expenses (including attorneys fees) arising out of the use of substituted materials or equipment. E. City's Cost Reimbursement: City will record City's costs in evaluating a substitute proposed or submitted by Contractor pursuant to Paragraphs 6.05.A.2 and 6.05.13. Whether or not City approves a substitute so proposed or submitted by Contractor, Contractor may be required to reimburse City for evaluating each such proposed substitute. Contractor may also be required to reimburse City for the charges for making changes in the Contract Documents (or in the provisions of any other direct contract with City) resulting from the acceptance of each proposed substitute. F. Contractor's Expense: Contractor shall provide all data in support of any proposed substitute or "or -equal" at Contractor's expense. CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1- AD1 007200-1 GENERAL OONDITIONS Page 24 of 63 G. City Substitute Reimbursement: Costs (savings or charges) attributable to acceptance of a substitute shall be incorporated to the Contract by Change Order. H. Time Extensions: No additional time will be granted for substitutions. 6.06 Concerning Subcontractors, Suppliers, and Others A. Contractor shall perform with his own organization, work of a value not less than 35% of the value embraced on the Contract, unless otherwise approved by the City. B. Contractor shall not employ any Subcontractor, Supplier, or other individual or entity, whether initially or as a replacement, against whom City may have reasonable objection. Contractor shall not be required to employ any Subcontractor, Supplier, or other individual or entity to furnish or perform any of the Work against whom Contractor has reasonable objection (excluding those acceptable to City as indicated in Paragraph 6.06.C). C. The City may from time to time require the use of certain Subcontractors, Suppliers, or other individuals or entities on the project, and will provide such requirements in the Supplementary Conditions. D. Minority Business Enterprise Compliance: It is City policy to ensure the full and equitable participation by Minority Business Enterprises (MBE) in the procurement of goods and services on a contractual basis. If the Contract Documents provide for a MBE goal, Contractor is required to comply with the intent of the City's MBE Ordinance (as amended) by the following: 1. Contractor shall, upon request by City, provide complete and accurate information regarding actual work performed by a MBE on the Contract and payment therefor. 2. Contractor will not make additions, deletions, or substitutions of accepted MBE without written consent of the City. Any unjustified change or deletion shall be a material breach of Contract and may result in debarment in accordance with the procedures outlined in the Ordinance. 3. Contractor shall, upon request by City, allow an audit and/or examination of any books, records, or files in the possession of the Contractor that will substantiate the actual work performed by an MBE. Material misrepresentation of any nature will be grounds for termination of the Contract in accordance with Paragraph 15.02.A. Any such misrepresentation may be grounds for disqualification of Contractor to bid on future contracts with the City for a period of not less than three years. E. Contractor shall be fully responsible to City for all acts and omissions of the Subcontractors, Suppliers, and other individuals or entities performing or furnishing any of the Work just as Contractor is responsible for Contractor's own acts and omissions. Nothing in the Contract Documents: CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1— AD1 007200-1 GENERAL OONDITIONS Page 25 of 63 1. shall create for the benefit of any such Subcontractor, Supplier, or other individual or entity any contractual relationship between City and any such Subcontractor, Supplier or other individual or entity; nor 2. shall create any obligation on the part of City to pay or to see to the payment of any moneys due any such Subcontractor, Supplier, or other individual or entity except as may otherwise be required by Laws and Regulations. F. Contractor shall be solely responsible for scheduling and coordinating the Work of Subcontractors, Suppliers, and other individuals or entities performing or furnishing any of the Work under a direct or indirect contract with Contractor. G. All Subcontractors, Suppliers, and such other individuals or entities performing or furnishing any of the Work shall communicate with City through Contractor. H. All Work performed for Contractor by a Subcontractor or Supplier will be pursuant to an appropriate agreement between Contractor and the Subcontractor or Supplier which specifically binds the Subcontractor or Supplier to the applicable terms and conditions of the Contract Documents for the benefit of City. 6.07 Wage Rates A. Duty to pay Prevailing Wage Rates. The Contractor shall comply with all requirements of Chapter 2258, Texas Government Code (as amended), including the payment of not less than the rates determined by the City Council of the City of Fort Worth to be the prevailing wage rates in accordance with Chapter 2258. Such prevailing wage rates are included in these Contract Documents. B. Penalty for Violation. A Contractor or any Subcontractor who does not pay the prevailing wage shall, upon demand made by the City, pay to the City $60 for each worker employed for each calendar day or part of the day that the worker is paid less than the prevailing wage rates stipulate d in these contract documents. This penalty shall be retained by the City to offset its administrative costs, pursuant to Texas Government Code 2258.023. C. Complaints of Violations and City Determination of Good Cause. On receipt of information, including a complaint by a worker, concerning an alleged violation of 2258.023, Texas Government Code, by a Contractor or Subcontractor, the City shall make an initial determination, before the 31st day after the date the City receives the information, as to whether good cause exists to believe that the violation occurred. The City shall notify in writing the Contractor or Subcontractor and any affected worker of its initial determination. Upon the City's determination that there is good cause to believe the Contractor or Subcontractor has violated Chapter 2258, the City shall retain the full amounts claimed by the claimant or claimants as the difference betweenwages paid and wages due under the prevailing wage rates, such amounts being subtracted from successive progress payments pending a final determination of the violation. CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1— AD1 007200-1 GENERAL OONDITIONS Page 26 of 63 D. Arbitration Required if Violation NotResolved. An issue relating to an alleged violation of Section 2258.023, Texas Government Code, including a penalty owed to the City or an affected worker, shall be submitted to binding arbitration in accordance with the Texas General Arbitration Act (Article 224 et seq., Revised Statutes) if the Contractor or Subcontractor and any affected worker does not resolve the issue by agreementbefore the 15th day afterthe date the City makes its initial determination pursuant to Paragraph C above. If the persons required to arbitrate under this section do not agree on an arbitrator before the 1 lth day after the date that arbitration is required, a district court shall appoint an arbitrator on the petition of any of the persons. The City is not a party in the arbitration. The decision and award of the arbitrator is final and binding on all parties and may be enforced in any court of competent jurisdiction. E. Records to be Maintained. The Contractor and each Subcontractor shall, for a period of three (3) years following the date of acceptance of the work, maintain records that show (i) the name and occupation of each worker employed by the Contractor in the construction of the Work provided for in this Contract; and (ii) the actual per diem wages paid to each worker. The records shall be open at all reasonable hours for inspection by the City. The provisions of Paragraph 6.23, Right to Audit, shall pertain to this inspection. F. Progress Payments. With each progress payment or payroll period, whichever is less, the Contractor shall submit an affidavit stating that the Contractor has complied with the requirements of Chapter 2258, Texas Government Code. G. Posting of Wage Rates. The Contractor shall post prevailing wage rates in a conspicuous place at all times. H. Subcontractor Compliance. The Contractor shall include in its subcontracts and/or shall otherwise require all of its Subcontractors to comply with Paragraphs A through G above. 6.08 PatentFees and Royalties A. Contractor shall pay all license fees and royalties and assume all costs incident to the use in the performance of the Work or the incorporation in the Work of any invention, design, process, product, or device which is the subject of patent rights or copyrights held by others. If a particular invention, design, process, product, or device is specified in the Contract Documents for use in the performance of the Work and if, to the actual knowledge of City, its use is subject to patent rights or copyrights calling for the payment of any license fee or royalty to others, the existence of such rights shall be disclosed by City in the Contract Documents. Failure of the City to disclose such information does not relieve the Contractor from its obligations to pay for the use of said fees or royalties to others. B. To the fullest extent permitted by Laws and Regulations, Contractor shall indemnify and hold harmless City, from and against all claims, costs, losses, and damages (including but not limited to all fees and charges of engineers, architects, attorneys, and other professionals and all court or arbitration or other dispute resolution costs) arising out of or relating to any infringement of patent rights or copyrights incident to the use in the performance of the Work or resultingfrom CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1— AD1 007200-1 GENERAL OONDITIONS Page 27 of 63 the incorporation in the Work of any invention, design, process, product, or device not specified in the Contract Documents. 6.09 Permits and Utilities A. Contractor obtained permits and licenses. Contractor shall obtain and pay for all construction permits and licenses except those provided for in the Supplementary Conditions or Contract Documents. City shall assist Contractor, when necessary, in obtaining such permits and licenses. Contractor shall pay all governmental charges and inspection fees necessary for the prosecution of the Work which are applicable at the time of opening of Bids, or, if there are no Bids, on the Effective Date of the Agreement, except for permits provided by the City as specified in 6.09.B. City shall pay all charges of utility owners for connections for providing permanent service to the Work. B. City obtainedpermits and licenses. City will obtain and pay for all permits and licenses as provided for in the Supplementary Conditions or Contract Documents. It will be the Contractor's responsibility to carry out the provisions of the permit. If the Contractor initiates changes to the Contract and the City approves the changes, the Contractor is responsible for obtaining clearances and coordinating with the appropriate regulatory agency. The City will not reimburse the Contractor for any cost associated with these requirements of any City acquired permit. The following are permits the City will obtain if required: 1. Texas Department of Transportation Permits 2. U.S. Army Corps of Engineers Permits 3. Texas Commission on Environmental Quality Permits 4. Railroad Company Permits C. Outstanding permits and licenses. The City anticipates acquisition of and/or access to permits and licenses. Any outstanding permits and licenses are anticipated to be acquired in accordance with the schedule set forth in the Supplementary Conditions. The Project Schedule submitted by the Contractor in accordance with the Contract Documents must consider any outstanding permits and licenses. 6.10 Laws and Regulations A. Contractor shall give all notices required by and shall comply with all Laws and Regulations applicable to the performance of the Work. Except where otherwise expressly required by applicable Laws and Regulations, the City shall not be responsible for monitoring Contractor's compliance with any Laws or Regulations. B. If Contractor performs any Work knowing or having reason to know that it is contrary to Laws or Regulations, Contractor shall bear all claims, costs, losses, and damages (including but not limited to all fees and charges of engineers, architects, attorneys, and other professionals and all CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1— AD1 007200-1 GENERAL OONDITIONS Page 28 of 63 court or arbitration or other dispute resolution costs) arising out of or relating to such Work. However, it shall not be Contractor's responsibility to make certain that the Specifications and Drawings are in accordance with Laws and Regulations, but this shall not relieve Contractor of Contractor's obligations under Paragraph 3.02. C. Changes in Laws or Regulations not known at the time of opening of Bids having an effect on the cost or time of performance of the Work may be the subject of an adjustment in Contract Price or Contract Time. 6.11 Taxes A. On a contract awarded by the City, an organization which qualifies for exemption pursuant to Texas Tax Code, Subchapter H, Sections 151.301-335 (as amended), the Contractor may purchase, rent or lease all materials, supplies and equipment used or consumed in the performance of this contract by issuing to his supplier an exemption certificate in lieu of the tax, said exemption certificate to comply with State Comptroller's Ruling .007. Any such exemption certificate issued to the Contractor in lieu of the tax shall be subject to and shall comply with the provision of State Comptroller's Ruling .011, and any other applicable rulings pertaining to the Texas Tax Code, Subchapter H. B. Texas Tax permits and information may be obtained from: 1. Comptroller of Public Accounts Sales Tax Division Capitol Station Austin, TX 78711; or 2. http://www.window.state.tx.us/taxinfo/taxforms/93-forms.html 6.12 Use of Site and Other Areas A. Limitation on Use of Site and Other Areas: 1. Contractor shall confine construction equipment, the storage of materials and equipment, and the operations of workers to the Site and other areas permitted by Laws and Regulations, and shall not unreasonably encumber the Site and other areas with construction equipment or other materials or equipment. Contractor shall assume full responsibility for any damage to any such land or area, or to the owner or occupant thereof, or of any adjacent land or areas resulting from the performance of the Work. 2. At any time when, in the judgment of the City, the Contractor has obstructed or closed or is carrying on operations in a portion of a street, right-of-way, or easement greater than is necessary for proper execution of the Work, the City may require the Contractor to finish the section on which operations are in progress before work is commenced on any additional area of the Site. CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1— AD1 007200-1 GENERAL OONDITIONS Page 29 of 63 3. Should any Damage Claim be made by any such owner or occupant because of the performance of the Work, Contractor shall promptly attempt to resolve the Damage Claim. 4. Pursuant to Paragraph 6.21, Contractor shall indemnify and hold harmless City, from and against all claims, costs, losses, and damages arising out of or relating to any claim or action, legal or equitable, brought by any such owner or occupant against City. B. Removal of Debris During Performance of the Work: During the progress of the Work Contractor shall keep the Site and other areas free from accumulations of waste materials, rubbish, and other debris. Removal and disposal of such waste materials, rubbish, and other debris shall conform to applicable Laws and Regulations. C. Site Maintenance Cleaning: 24 hours after written notice is given to the Contractor that the clean-up on the job site is proceeding in a manner unsatisfactory to the City, if the Contractor fails to correct the unsatisfactory procedure, the City may take such direct action as the City deems appropriate to correct the clean-up deficiencies cited to the Contractor in the written notice (by letter or electronic communication), and the costs of such direct action, plus 25 % of such costs, shall be deducted from the monies due or to become due to the Contractor. D. Final Site Cleaning: Prior to Final Acceptance of the Work Contractor shall clean the Site and the Work and make it ready for utilization by City or adjacent property owner. At the completion of the Work Contractor shall remove from the Site all tools, appliances, construction equipment and machinery, and surplus materials and shall restore to original condition or better all property disturbed by the Work. E. Loading Structures: Contractor shall not load nor permit any part of any structure to be loaded in any manner that will endanger the structure, nor shall Contractor subject any part of the Work or adjacent property to stresses or pressures that will endanger it. 6.13 Record Documents A. Contractor shall maintain in a safe place at the Site or in a place designated by the Contractor and approved by the City, one (1) record copy of all Drawings, Specifications, Addenda, Change Orders, Field Orders, and written interpretations and clarifications in good order and annotated to show changes made during construction. These record documents together with all approved Samples and a counterpart of all accepted Submittals will be available to City for reference. Upon completion of the Work, these record documents, any operation and maintenance manuals, and Submittals will be delivered to City prior to Final Inspection. Contractor shall include accurate locations for buried and imbedded items. 6.14 Safety and Protection A. Contractor shall be solely responsible for initiating, maintaining and supervising all safety precautions and programs in connection with the Work. Such responsibility does not relieve Subcontractors of their responsibility for the safety of persons or property in the performance of their work, nor for compliance with applicable safety Laws and Regulations. Contractor shall CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1- AD1 007200-1 GENERAL OONDITIONS Page 30 of 63 take all necessary precautions for the safety of, and shall provide the necessary protection to prevent damage, injury or loss to: 1. all persons on the Site or who maybe affected by the Work; 2. all the Work and materials and equipment to be incorporated therein, whether in storage on or off the Site; and 3. other property at the Site or adjacent thereto, including trees, shrubs, lawns, walks, pavements, roadways, structures, utilities, and Underground Facilities not designated for removal, relocation, or replacement in the course of construction. B. Contractor shall comply with all applicable Laws and Regulations relating to the safety of persons or property, or to the protection of persons or property from damage, injury, or loss; and shall erect and maintain all necessary safeguards for such safety and protection. Contractor shall notify owners of adjacent property and of Underground Facilities and other utility owners when prosecution of the Work may affect them, and shall cooperate with them in the protection, removal, relocation, and replacement of their property. C. Contractor shall comply with the applicable requirements of City's safety programs, if any. D. Contractor shall inform City of the specific requirements of Contractor's safety program, if any, with which City's employees and representatives must comply while at the Site. E. All damage, injury, or loss to any property referredto in Paragraph6.14.A.2 or 6.14.A.3 caused, directly or indirectly, in whole or in part, by Contractor, any Subcontractor, Supplier, or any other individual or entity directly or indirectly employed by any of them to perform any of the Work, or anyone for whose acts any of them may be liable, shall be remedied by Contractor. F. Contractor's duties and responsibilities for safety and for protection of the Work shall continue until such time as all the Work is completed and City has accepted the Work. 6.15 Safety Representative Contractor shall inform City in writing of Contractor's designated safety representative at the Site. 6.16 Hazard Communication Programs Contractor shall be responsible for coordinating any exchange of material safety data sheets or other hazard communication information required to be made available to or exchanged between or among employers in accordance with Laws or Regulations. 6.17 Emergencies and/or Rectification A. In emergencies affecting the safety or protection of persons or the Work or property at the Site or adjacent thereto, Contractor is obligated to act to prevent threatened damage, injury, or loss. Contractor shall give City prompt written notice if Contractor believes that any significant CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1— AD1 007200-1 GENERAL OONDITIONS Page 31 of 63 changes in the Work or variations from the Contract Documents have been caused thereby or are required as a result thereof. If City determines that a change in the Contract Documents is required because of the action taken by Contractor in response to such an emergency, a Change Order may be issued. B. Should the Contractor fail to respond to a request from the City to rectify any discrepancies, omissions, or correction necessary to conform with the requirements of the Contract Documents, the City shall give the Contractor written notice that such work or changes are to be performed. The written notice shall direct attention to the discrepant condition and request the Contractor to take remedial action to correct the condition. In the event the Contractor does not take positive steps to fulfill this written request, or does not show just cause for not taking the proper action, within 24 hours, the City may take such remedial action with City forces or by contract. The City shall deduct an amount equal to the entire costs for such remedial action, plus 25%, from any funds due or become due the Contractor on the Project. 6.18 Submittals A. Contractor shall submit required Submittals to City for review and acceptance in accordance with the accepted Schedule of Submittals (as required by Paragraph 2.07). Each submittal will be identified as City may require. 1. Submit number of copies specified in the General Requirements. 2. Data shown on the Submittals will be complete with respect to quantities, dimensions, specified performance and design criteria, materials, and similar data to show City the services, materials, and equipment Contractor proposes to provide and to enable City to review the information for the limited purposes required by Paragraph 6.18.C. 3. Submittals submitted as herein provided by Contractor and reviewed by City for conformance with the design concept shall be executed in conformity with the Contract Documents unless otherwise required by City. 4. When Submittals are submitted for the purpose of showing the installation in greater detail, their review shall not excuse Contractor from requirements shown on the Drawings and Specifications. 5. For -Information -Only submittals upon which the City is not expected to conduct review or take responsive action may be so identified in the Contract Documents. 6. Submit required number of Samples specified in the Specifications. 7. Clearly identify each Sample as to material, Supplier, pertinent data such as catalog numbers, the use for which intended and other data as City may require to enable City to review the submittal for the limited purposes required by Paragraph 6.18.C. CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1- AD1 007200-1 GENERAL OONDITIONS Page 32 of 63 B. Where a Submittal is required by the Contract Documents or the Schedule of Submittals, any related Work performed prior to City's review and acceptance of the pertinent submittal will be at the sole expense and responsibility of Contractor. C. City's Review: 1. City will provide timely review of required Submittals in accordance with the Schedule of Submittals acceptable to City. City's review and acceptance will be only to determine if the items covered by the submittals will, after installation or incorporation in the Work, conform to the information given in the Contract Documents and be compatible with the design concept of the completed Project as a functioning whole as indicated by the Contract Documents. 2. City's review and acceptance will not extend to means, methods, techniques, sequences, or procedures of construction (except where a particular means, method, technique, sequence, or procedure of construction is specifically and expressly called for by the Contract Documents) or to safety precautions or programs incident thereto. The review and acceptance of a separate item as such will not indicate approval of the assembly in which the item functions. 3. City's review and acceptance shall not relieve Contractor from responsibility for any variation from the requirements of the Contract Documents unless Contractor has complied with the requirements of Section 01 33 00 and City has given written acceptance of each such variation by specific written notation thereof incorporated in or accompanying the Submittal. City's review and acceptance shall not relieve Contractor from responsibility for complying with the requirements of the Contract Documents. 6.19 Continuing the Work Except as otherwise provided, Contractor shall carry on the Work and adhere to the Project Schedule during all disputes or disagreements with City. No Work shall be delayed or postponed pending resolution of any disputes or disagreements, except as City and Contractor may otherwise agree in writing. 6.20 Contractor's General Warranty and Guarantee A. Contractor warrants and guarantees to City that all Work will be in accordance with the Contract Documents and will not be defective. City and its officers, directors, members, partners, employees, agents, consultants, and subcontractors shall be entitled to rely on representation of Contractor's warranty and guarantee. B. Contractor's warranty and guarantee hereunder excludes defects or damage caused by: 1. abuse, modification, or improper maintenance or operation by persons other than Contractor, Subcontractors, Suppliers, or any other individual or entity for whom Contractor is responsible; or CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1— AD1 007200-1 GENERAL CONDITIONS Page 33 of 63 2. normal wear and tear under normal usage. C. Contractor's obligation to perform and complete the Work in accordance with the Contract Documents shall be absolute. None of the following will constitute an acceptance of Work that is not in accordance with the Contract Documents or a release of Contractor's obligation to perform the Work in accordance with the Contract Documents: 1. observations by City; 2. recommendation or payment by City of any progress or final payment; 3. the issuance of a certificate of Final Acceptance by City or any payment related thereto by City; 4. use or occupancy of the Work or any part thereof by City; 5. any review and acceptance of a Submittal by City; 6. any inspection, test, or approval by others; or 7. any correction of defective Work by City. D. The Contractor shall remedy any defects or damages in the Work and pay for any damage to other work or property resulting therefrom which shall appear within a period of two (2) years from the date of Final Acceptance of the Work unless a longer period is specified and shall furnish a good and sufficient maintenance bond, complying with the requirements of Article 5.02.13. The City will give notice of observed defects with reasonable promptness. 6.21 Indemnification A. Contractor covenants and agrees to indemnify, hold harmless and defend, at its own expense, the City, its officers, servants and employees, from and against any and all claims arising out of, or alleged to arise out of, the work and services to be performed by the Contractor, its officers, agents, employees, subcontractors, licenses or invitees under this Contract. THIS iNDEMNi ICATiON PROVISION iS SPFCiFiCAi1V INTENDED TO OPERATE AND BF FFFECTiVE EVEN IF iT iS ALLEGED OR PROVEN THAT ALL OR SOME OF THE DAMAGES BEING: SOiJGIU WERE CAUSFD. iN WUQ,i,F ORIN PART, BY ANY ACTS OMISSION OR NE(T IGFNCF OF THE CiTY. This indemnity provision is intended to include, without limitation, indemnity for costs, expenses and legal fees incurred by the City in defending against such claims and causes of actions. B. Contractor covenants and agrees to indemnify and hold harmle s s, at its own expense, the City, its officers, servants and employees, from and against any and all loss, damage or destruction of property of the City, arising out of, or alleged to arise out of, the work and services to be performed by the Contractor, its officers, agents, employees, subcontractors, licensees or invitees under this Contract. ]MiS INDEMNIFICATION PROVISION iS CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: &23/202I ATTACHMENT 1— AD1 007200-1 GENERAL OONDITIONS Page 34 of 63 SPECIFICALLY INTENDED TO OPER 11"ND HE FUELTIVF, FVFN IF IT IS ALLEGED OR PROVEN THAT ALL OR SOME, OF THE. DAMAGES BEING SOIA MT WERE CAUSED- IN WHOL OR IN PART. BY ANY AC-L- OMISSION OR NEGLICFNCF OF THE CITY,. 6.22 Delegation of Professional Design Services A. Contractor will not be required to provide professional design services unless such services are specifically required by the Contract Documents for a portion of the Work or unless such services are required to carryout Contractor's responsibilities for construction means, methods, techniques, sequences and procedures. B. If professional design services or certifications by a design professional related to systems, materials or equipment are specifically required of Contractor by the Contract Documents, City will specify all performance and design criteria that such services must satisfy. Contractor shall cause such services or certifications to be provided by a properly licensed professional, whose signature and seal shall appear on all drawings, calculations, specifications, certifications, and Submittals prepared by such professional. Submittals related to the Work designed or certified by such professional, if prepared by others, shall bear such professional's written approval when submitted to City. C. City shall be entitled to rely upon the adequacy, accuracy and completeness of the services, certifications or approvals performed by such design professionals, provided City has specified to Contractor performance and design criteria that such services must satisfy. D. Pursuant to this Paragraph 6.22, City's review and acceptance of design calculations and design drawings will be only for the limited purpose of checking for conformance with performance and design criteria given and the design concept expressed in the Contract Documents. City's review and acceptance of Submittals (except design calculations and design drawings) will be only for the purpose stated in Paragraph 6.18.C. 6.23 Right to Audit A. The Contractor agrees that the City shall, until the expiration of three (3) years after final payment under this Contract, have access to and the right to examine and photocopy any directly pertinent books, documents, papers, and records of the Contractor involving transactions relating to this Contract. Contractor agrees that the City shall have access during Regular Working Hours to all necessary Contractor facilities and shall be provided adequate and appropriate work space in order to conduct audits in compliance with the provisions of this Paragraph. The City shall give Contractor reasonable advance notice of intended audits. B. Contractor further agrees to include in all its subcontracts hereunder a provision to the effect that the subcontractor agrees that the City shall, until the expiration of three (3) years after final payment under this Contract, have access to and the right to examine and photocopy any directly pertinent books, documents, papers, and records of such Subcontractor, involving transactions to the subcontract, and further, that City shall have access during Regular Working Hours to all CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1— AD1 007200-1 GENERAL OONDITIONS Page 35 of 63 Subcontractor facilities, and shall be provided adequate and appropriate work space in order to conduct audits in compliance with the provisions of this Paragraph. The City shall give Subcontractor reasonable advance notice of intended audits. C. Contractor and Subcontractor agree to photocopy such documents as may be requested by the City. The City agrees to reimburse Contractor for the cost of the copies as follows at the rate published in the Texas Administrative Code in effect as of the time copying is performed. 6.24 Nondiscrimination A. The City is responsible for operating Public Transportation Programs and implementing transit - related projects, which are funded in part with Federal financial assistance awarded by the U.S. Department of Transportation and the Federal Transit Administration (FTA), without discriminating against any person in the United States on the basis of race, color, or national origin. B. Title VI, Civil Rights Act of 1964 as amended: Contractor shall comply with the requirements of the Act and the Regulations as further defined in the Supplementary Conditions for any project receiving Federal assistance. ARTICLE 7 — OTHER WORK AT THE SITE 7.01 Related Work at Site A. City may perform other work related to the Project at the Site with City's employees, or other City contractors, or through other direct contracts therefor, or have other work performed by utility owners. If such other work is not noted in the Contract Documents, then written notice thereof will be given to Contractor prior to starting any such other work; and B. Contractor shall afford each other contractor who is a party to such a direct contract, each utility owner, and City, if City is performing other work with City's employees or other City contractors, proper and safe access to the Site, provide a reasonable opportunity for the introduction and storage of materials and equipment and the execution of such other work, and properly coordinate the Work with theirs. Contractor shall do all cutting, fitting, and patching of the Work that may be required to properly connect or otherwise make its several parts come together and properly integrate with such other work. Contractor shall not endanger any work of others by cutting, excavating, or otherwise altering such work; provided, however, that Contractor may cut or alter others' work with the written consent of City and the others whose work will be affected. C. If the proper execution or results of any part of Contractor's Work depends upon work performed by others under this Article 7, Contractor shall inspect such other work and promptly report to City in writing any delays, defects, or deficiencies in such other work that render it unavailable or unsuitable for the proper execution and results of Contractor's Work. Contractor's failure to so report will constitute an acceptance of such other work as fit and proper for integration with Contractor's Work except for latent defects in the work provided by others. CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1— AD1 007200-1 GENERAL CONDITIONS Page 36 of 63 7.02 Coordination A. If City intends to contract with others for the performance of other work on the Project at the Site, the following will be set forth in Supplementary Conditions: 1. the individual or entity who will have authority and responsibility for coordination of the activities among the various contractors will be identified; 2. the specific matters to be covered by such authority and responsibility will be itemized; and 3. the extent of such authority and responsibilities will be provided. B. Unless otherwise provided in the Supplementary Conditions, City shall have authority for such coordination. ARTICLE 8 — CITY'S RESPONSIBILITIES 8.01 Communications to Contractor Except as otherwise provided in the Supplementary Conditions, City shall issue all communications to Contractor. 8.02 Furnish Data City shall timely furnish the data required under the Contract Documents. 8.03 Pay When Due City shall make payments to Contractor in accordance with Article 14. 8.04 Lands and Easements; Reports and Tests City's duties with respect to providing lands and easements and providing engineering surveys to establish reference points are set forth in Paragraphs 4.01 and 4.05. Paragraph 4.02 refers to City's identifying and making available to Contractor copies of reports of explorations and tests of subsurface conditions and drawings of physical conditions relating to existing surface or subsurface structures at or contiguous to the Site that have been utilized by City in preparing the Contract Documents. 8.05 Change Orders City shall execute Change Orders in accordance with Paragraph 10.03. 8.06 Inspections, Tests, and Approvals City's responsibility with respect to certain inspections, tests, and approvals is set forth in Paragraph 13.03. CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: &23/2MI ATTACHMENT 1— AD1 007200-1 GENERAL OONDITIONS Page 37 of 63 8.07 Limitations on City's Responsibilities A. The City shall not supervise, direct, or have control or authority over, nor be responsible for, Contractor's means, methods, techniques, sequences, or procedures of construction, or the safety precautions and programs incident thereto, or for any failure of Contractor to comply with Laws and Regulations applicable to the performance of the Work. City will not be responsible for Contractor's failure to perform the Work in accordance with the Contract Documents. B. City will notify the Contractor of applicable safety plans pursuant to Paragraph 6.14. 8.08 Undisclosed Hazardous Environmental Condition City's responsibility with respect to an undisclosed Hazardous Environmental Condition is set forth in Paragraph 4.06. 8.09 Compliance with Safety Program While at the Site, City's employees and representatives shall comply with the specific applicable requirements of Contractor's safety programs of which City has been informed pursuant to Paragraph 6.14. ARTICLE 9 — CITY'S OBSERVATION STATUS DURING CONSTRUCTION 9.01 City's Project Manager City will provide one or more Project Manager(s) during the construction period. The duties and responsibilities and the limitations of authority of City's Project Manager during construction are set forth in the Contract Documents. The City's Project Manager for this Contract is identified in the Supplementary Conditions. 9.02 Visits to Site A. City's Project Manager will make visits to the Site at intervals appropriate to the various stages of construction as City deems necessary in order to observe the progress that has been made and the quality of the various aspects of Contractor's executed Work. Based on information obtained during such visits and observations, City's Project Manager will determine, in general, if the Work is proceeding in accordance with the Contract Documents. City's Project Manager will not be required to make exhaustive or continuous inspections on the Site to check the quality or quantity of the Work. City's Project Manager's efforts will be directed toward providing City a greater degree of confidence that the completed Work will conform generally to the Contract Documents. B. City's Project Manager's visits and observations are subject to all the limitations on authority and responsibility in the Contract Documents including those set forth in Paragraph 8.07. CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1— AD1 007200-1 GENERAL OONDITIONS Page 38 of 63 9.03 Authorized Variations in Work City's Project Manager may authorize minor variations in the Work from the requirements of the Contract Documents which do not involve an adjustment in the Contract Price or the Contract Time and are compatible with the design concept of the completed Project as a functioning whole as indicated by the Contract Documents. These may be accomplished by a Field Order and will be binding on City and also on Contractor, who shall perform the Work involved promptly. 9.04 Rejecting Defective Work City will have authority to reject Work which City's Project Manager believes to be defective, or will not produce a completed Project that conforms to the Contract Documents or that will prejudice the integrity of the design concept of the completed Project as a functioning whole as indicated by the Contract Documents. City will have authority to conduct special inspection or testing of the Work as provided in Article 13, whether or not the Work is fabricated, installed, or completed. 9.05 Determinations for Work Performed Contractor will determine the actual quantities and classifications of Work performed. City's Project Manager will review with Contractor the preliminary determinations on such matters before rendering a written recommendation. City's written decision will be final (except as modified to reflect changed factual conditions or more accurate data). 9.06 Decisions on Requirements of Contract Documents and Acceptability of Work A. City will be the initial interpreter of the requirements of the Contract Documents and judge of the acceptability of the Work thereunder. B. City will render a written decision on any issue referred. C. City's written decision on the issue referred will be final and binding on the Contractor, subject to the provisions of Paragraph 10.06. ARTICLE 10 — CHANGES IN THE WORK; CLAIMS; EXTRA WORK 10.01 Authorized Changes in the Work A. Without invalidating the Contract and without notice to any surety, City may, at any time or from time to time, order Extra Work. Upon notice of such Extra Work, Contractor shall promptly proceed with the Work involved which will be performed under the applicable conditions of the Contract Documents (except as otherwise specifically provided). Extra Work shall be memorialized by a Change Order which may or may not precede an order of Extra work. B. For minor changes of Work not requiring changes to Contract Time or Contract Price, a Field Order may be issued by the City. CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1— AD1 007200-1 GENERAL OONDITIONS Page 39 of 63 10.02 Unauthorized Changes in the Work Contractor shall not be entitled to an increase in the Contract Price or an extension of the Contract Time with respect to any work performed that is not required by the Contract Documents as amended, modified, or supplemented as provided in Paragraph 3.04, except in the case of an emergency as provided in Paragraph 6.17. 10.03 Execution of Change Orders A. City and Contractor shall execute appropriate Change Orders covering: changes in the Work which are: (i) ordered by City pursuant to Paragraph 10.01.A, (ii) required because of acceptance of defective Work under Paragraph 13.08 or City's correction of defective Work under Paragraph 13.09, or (iii) agreed to by the parties; 2. changes in the Contract Price or Contract Time which are agreed to by the parties, including any undisputed sum or amount of time for Work actually performed. 10.04 Extra Work A. Should a difference arise as to what does or does not constitute Extra Work, or as to the payment thereof, and the City insists upon its performance, the Contractor shall proceed with the work after making written request for written orders and shall keep accurate account of the actual reasonable cost thereof. Contract Claims regarding Extra Work shall be made pursuant to Paragraph 10.06. B. The Contractor shall furnish the City such installation records of all deviations from the original Contract Documents as may be necessary to enable the City to prepare for permanent record a corrected set of plans showing the actual installation. C. The compensation agreed upon for Extra Work whether or not initiated by a Change Order shall be a full, complete and final payment for all costs Contractor incurs as a result or relating to the change or Extra Work, whether said costs are known, unknown, foreseen or unforeseen at that time, including without limitation, any costs for delay, extended overhead, ripple or impact cost, or any other effect on changed or unchanged work as a result of the change or Extra Work. 10.05 Notification to Surety If the provisions of any bond require notice to be given to a surety of any change affecting the general scope of the Work or the provisions of the Contract Documents (including, but not limited to, Contract Price or Contract Time), the giving of any such notice will be Contractor's responsibility. The amount of each applicable bond will be adjusted by the Contractor to reflect the effect of any such change. CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1— AD1 007200-1 GENERAL OONDITIONS Page 40 of 63 10.06 Contract Claims Process A. City's Decision Required: All Contract Claims, except those waived pursuant to Paragraph 14.09, shall be referred to the City for decision. A decision by City shall be required as a condition precedent to any exercise by Contractor of any rights or remedies he may otherwise have under the Contract Documents or by Laws and Regulations in respect of such Contract Claims. B. Notice: 1. Written notice stating the general nature of each Contract Claim shall be delivered by the Contractor to City no later than 15 days after the start of the event giving rise thereto. The responsibility to substantiate a Contract Claim shall rest with the party making the Contract Claim. 2. Notice of the amount or extent of the Contract Claim, with supporting data shall be delivered to the City on or before 45 days from the start of the event giving rise thereto (unless the City allows additional time for Contractor to submit additional or more accurate data in support of such Contract Claim). 3. A Contract Claim for an adjustment in Contract Price shall be prepared in accordance with the provisions of Paragraph 12.01. 4. A Contract Claim for an adjustment in Contract Time shall be prepared in accordance with the provisions of Paragraph 12.02. 5. Each Contract Claim shall be accompanied by Contractor's written statement that the adjustment claimed is the entire adjustment to which the Contractor believes it is entitled as a result of said event. 6. The City shall submit any response to the Contractor within 30 days after receipt of the claimant's last submittal (unless Contract allows additional time). C. City's Action: City will review each Contract Claim and, within 30 days after receipt of the last submittal of the Contractor, if any, take one of the following actions in writing: 1. deny the Contract Claim in whole or in part; 2. approve the Contract Claim; or 3. notify the Contractor that the City is unable to resolve the Contract Claim if, in the City's sole discretion, it would be inappropriate for the City to do so. For purposes of further resolution of the Contract Claim, such notice shall be deemed a denial. CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1— AD1 007200-1 GENERAL OONDITIONS Page 41 of 63 D. City's written action under Paragraph 10.06.0 will be final and binding, unless City or Contractor invoke the dispute resolution procedure set forth in Article 16 within 30 days of such action or denial. E. No Contract Claim for an adjustment in Contract Price or Contract Time will be valid if not submitted in accordance with this Paragraph 10.06. ARTICLE 11— COST OF THE WORK; ALLOWANCES; UNIT PRICE WORK; PLANS QUANTITY MEASUREMENT 11.01 Cost of the Work A. Costs Included: The term Cost of the Work means the sum of all costs, except those excluded in Paragraph 11.0l.B, necessarily incurred and paid by Contractor in the proper performance of the Work. When the value of any Work covered by a Change Order, the costs to be reimbursed to Contractor will be only those additional or incremental costs required because of the change in the Work. Such costs shall not include any of the costs itemized in Paragraph 11.01.13, and shall include but not be limited to the following items: 1. Payroll costs for employees in the direct employ of Contractor in the performance of the Work under schedules of job classifications agreed upon by City and Contractor. Such employees shall include, without limitation, superintendents, foremen, and other personnel employed full time on the Work. Payroll costs for employees not employed full time on the Work shall be apportioned on the basis of their time spent on the Work. Payroll costs shall include; a. salaries with a 55% markup, or b. salaries and wages plus the cost of fringe benefits, which shall include social security contributions, unemployment, excise, and payroll taxes, workers' compensation, health and retirement benefits, bonuses, sick leave, vacation and holiday pay applicable thereto. The expenses of performing Work outside of Regular Working Hours, Weekend Working Hours, or legal holidays, shall be included in the above to the extent authorized by City. 2. Cost of all materials and equipment furnished and incorporated in the Work, including costs of transportation and storage thereof, and Suppliers' field services required in connection therewith. 3. Rentals of all construction equipment and machinery, and the parts thereof whether rented from Contractor or others in accordance with rental agreements approved by City, and the costs of transportation, loading, unloading, assembly, dismantling, and removal thereof. All such costs shall be in accordance with the terms of said rental agreements. The rental of any such equipment, machinery, or parts shall cease when the use thereof is no longer necessary for the Work. CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1- AD1 007200-1 GENERAL OONDITIONS Page 42 of 63 4. Payments made by Contractor to Subcontractors for Work performed by Subcontractors. If required by City, Contractor shall obtain competitive bids from subcontractors acceptable to City and Contractor and shall deliver such bids to City, who will then determine, which bids, if any, will be acceptable. If any subcontract provides that the Subcontractor is to be paid on the basis of Cost of the Work plus a fee, the Subcontractor's Cost of the Work and fee shall be determined in the same manner as Contractor's Cost of the Work and fee as provided in this Paragraph 11.01. 5. Costs of special consultants (including but not limited to engineers, architects, testing laboratories, surveyors, attorneys, and accountants) employed for services specifically related to the Work. 6. Supplemental costs including the following: a. The proportion of necessary transportation, travel, and subsistence expenses of Contractor's employees incurred in discharge of duties connected with the Work. b. Cost, including transportation and maintenance, of all materials, supplies, equipment, machinery, appliances, office, and temporary facilities at the Site, and hand tools not owned by the workers, which are consumed in the performance of the Work, and cost, less market value, of such items used but not consumed which remain the property of Contractor. c. Sales, consumer, use, and other similar taxes related to the Work, and for which Contractor is liable not covered under Paragraph 6.11, as imposed by Laws and Regulations. d. Deposits lost for causes other than negligence of Contractor, any Subcontractor, or anyone directly or indirectly employed by any of them or for whose acts any of them may be liable, and royalty payments and fees for permits and licenses. e. Losses and damages (and related expenses) caused by damage to the Work, not compensated by insurance or otherwise, sustained by Contractor in connection with the performance of the Work, provided such losses and damages have resulted from causes other than the negligence of Contractor, any Subcontractor, or anyone directly or indirectly employed by any of them or for whose acts any of them may be liable. Such losses shall include settlements made with the written consent and approval of City. No such losses, damages, and expenses shall be included in the Cost of the Work for the purpose of determining Contractor's fee. £ The cost of utilities, fuel, and sanitary facilities at the Site. g. Minor expenses such as telegrams, long distance telephone calls, telephone and communication services at the Site, express and courier services, and similar petty cash items in connection with the Work. CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1- AD1 007200-1 GENERAL OONDITIONS Page 43 of 63 h. The costs of premiums for all bonds and insurance Contractor is required by the Contract Documents to purchase and maintain. B. Costs Excluded: The term Cost of the Work shall not include any of the following items: 1. Payroll costs and other compensation of Contractor's officers, executives, principals (of partnerships and sole proprietorships), general managers, safety managers, engineers, architects, estimators, attorneys, auditors, accountants, purchasing and contracting agents, expediters, timekeepers, clerks, and other personnel employed by Contractor, whether at the Site or in Contractor's principal or branch office for general administration of the Work and not specifically included in the agreed upon schedule of job classifications referred to in Paragraph 11.01.A.1 or specifically covered by Paragraph 11.0LAA, all of which are to be considered administrative costs covered by the Contractor's fee. 2. Expenses of Contractor's principal and branch offices other than Contractor's office at the Site. 3. Any part of Contractor's capital expenses, including interest on Contractor's capital employed for the Work and charges against Contractor for delinquent payments. 4. Costs due to the negligence of Contractor, any Subcontractor, or anyone directly or indirectly employed by any of them or for whose acts any of them may be liable, including but not limited to, the correction of defective Work, disposal of materials or equipment wrongly supplied, and making good any damage to property. 5. Other overhead or general expense costs of any kind. C. Contractor's Fee: When all the Work is performed on the basis of cost-plus, Contractor's fee shall be determined as set forth in the Agreement. When the value of any Work covered by a Change Order for an adjustment in Contract Price is determined on the basis of Cost of the Work, Contractor's fee shall be determined as set forth in Paragraph 12.01.C. D. Documentation: Whenever the Cost of the Work for any purpose is to be determined pursuant to Paragraphs 11.01.A and 11.01.13, Contractor will establish and maintain records thereof in accordance with generally accepted accounting practices and submit in a form acceptable to City an itemized cost breakdown together with supporting data. 11.02 Allowances A. Specified Allowance: It is understood that Contractor has included in the Contract Price all allowances so named in the Contract Documents and shall cause the Work so covered to be performed for such sums and by such persons or entities as may be acceptable to City. B. Pre -bid Allowances: 1. Contractor agrees that: CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1— AD1 007200-1 GENERAL OONDITIONS Page 44 of 63 a. the pre -bid allowances include the cost to Contractor of materials and equipment required by the allowances to be delivered at the Site, and all applicable taxes; and b. Contractor's costs for unloading and handling on the Site, labor, installation, overhead, profit, and other expenses contemplated for the pre -bid allowances have been included in the allowances, and no demand for additional payment on account of any of the foregoing will be valid. C. ContingencyAllowance: Contractor agrees that a contingency allowance, if any, is for the sole use of City. D. Prior to final payment, an appropriate Change Order will be issued to reflect actual amounts due Contractor on account of Work covered by allowances, and the Contract Price shall be correspondingly adjusted. 11.03 Unit Price Work A. Where the Contract Documents provide that all or part of the Work is to be Unit Price Work, initially the Contract Price will be deemed to include for all Unit Price Work an amount equal to the sum of the unit price for each separately identified item of Unit Price Work times the estimated quantity of each item as indicated in the Agreement. B. The estimated quantities of items of Unit Price Work are not guaranteed and are solely for the purpose of comparison of Bids and determining an initial Contract Price. Determinations of the actual quantities and classifications of Unit Price Work performed by Contractor will be made by City subject to the provisions of Paragraph 9.05. C. Each unit price will be deemed to include an amount considered by Contractor to be adequate to cover Contractor's overhead and profit for each separately identified item. Work described in the Contract Documents, or reasonably inferred as required for a functionally complete installation, but not identified in the listing of unit price items shall be considered incidental to unit price work listed and the cost of incidental work included as part of the unit price. D. City may make an adjustment in the Contract Price in accordance with Paragraph 12.01 if: 1. the quantity of any item of Unit Price Work performed by Contractor differs materially and significantly from the estimated quantity of such item indicated in the Agreement; and 2. there is no corresponding adjustment with respect to any other item of Work. E. Increased or Decreased Quantities: The City reserves the right to order Extra Work in accordance with Paragraph 10.01. 1. If the changes in quantities or the alterations do not significantly change the character of work under the Contract Documents, the altered work will be paid for at the Contract unit price. CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1— ADl 007200-1 GENERAL OONDITIONS Page 45 of 63 2. If the changes in quantities or alterations significantly change the character of work, the Contract will be amended by a Change Order. 3. If no unit prices exist, this will be considered Extra Work and the Contract will be amended by a Change Order in accordance with Article 12. 4. A significant change in the character of work occurs when: a. the character of work for any Item as altered differs materially in kind or nature from that in the Contract or b. a Major Item of work varies by more than 25% from the original Contract quantity. 5. When the quantity of work to be done under any Major Item of the Contract is more than 125% of the original quantity stated in the Contract, then either party to the Contract may request an adjustment to the unit price on the portion of the work that is above 125%. 6. When the quantity of work to be done under any Major Item of the Contract is less than 75% of the original quantity stated in the Contract, then either party to the Contract may request an adjustment to the unit price. 11.04 Plans Quantity Measurement A. Plans quantities may or may not represent the exact quantity of work performed or material moved, handled, or placed during the execution of the Contract. The estimated bid quantities are designated as final payment quantities, unless revised by the governing Section or this Article. B. If the quantity measured as outlined under "Price and Payment Procedures" varies by more than 25% (or as stipulated under "Price and Payment Procedures" for specific Items) from the total estimated quantity for an individual Item originally shown in the Contract Documents, an adjustment may be made to the quantity of authorized work done for payment purposes. The party to the Contract requesting the adjustment will provide field measurements and calculations showing the final quantity for which payment will be made. Payment for revised quantity will be made at the unit price bid for that Item, except as provided for in Article 10. C. When quantities are revised by a change in design approved by the City, by Change Order, or to correct an error, or to correct an error on the plans, the plans quantity will be increasedor decreased by the amount involved in the change, and the 25% variance will apply to the new plans quantity. D. If the total Contract quantity multiplied by the unit price bid for an individual Item is less than $250 and the Item is not originally a plans quantity Item, then the Item may be paid as a plans quantity Item if the City and Contractor agree in writing to fix the final quantity as a plans quantity. CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1— AD1 007200-1 GENERAL OONDITIONS Page 46 of 63 E. For callout work or non -site specific Contracts, the plans quantity measurement requirements are not applicable. ARTICLE 12 — CHANGE OF CONTRACT PRICE; CHANGE OF CONTRACT TIME 12.01 Change of Contract Price A. The Contract Price may only be changed by a Change Order. B. The value of any Work covered by a Change Order will be determined as follows: 1. where the Work involved is covered by unit prices contained in the Contract Documents, by application of such unit prices to the quantities of the items involved (subject to the provisions of Paragraph 11.03); or 2. where the Work involved is not covered by unit prices contained in the Contract Documents, by a mutually agreed lump sum or unit price (which may include an allowance for overhead and profit not necessarily in accordance with Paragraph 12.0l.C.2), and shall include the cost of any secondary impacts that are foreseeable at the time of pricing the cost of Extra Work; or 3. where the Work involved is not covered by unit prices contained in the Contract Documents and agreement to a lump sum or unit price is not reached -under Paragraph 12.01.13.2, on the basis of the Cost of the Work (determined as provided in Paragraph 11.01) plus a Contractor's fee for overhead and profit (determined as provided in Paragraph 12.01.C). C. Contractor's Fee: The Contractor's additional fee for overhead and profit shall be determined as follows: 1. a mutually acceptable fixed fee; or 2. if a fixed fee is not agreed upon, then a fee based on the following percentages of the various portions of the Cost of the Work: a. for costs incurred under Paragraphs 11.0l.A.1, 11.0l.A.2. and 11.01.A.3, the Contractor's additional fee shall be 15 percent except for: 1) rental fees for Contractor's own equipment using standard rental rates; 2) bonds and insurance; b. for costs incurred under Paragraph 11.01.A.4 and 11.0l.A.5, the Contractor's fee shall be five percent (5%); 1) where one or more tiers of subcontracts are on the basis of Cost of the Work plus a fee and no fixed fee is agreed upon, the intent of Paragraphs 12.0l.C.2.a and 12.0l.C.2.b is that the Subcontractor who actually performs the Work, at whatever CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1— AD1 007200-1 GENERAL CONDITIONS Page 47 of 63 tier, will be paid a fee of 15 percent of the costs incurred by such Subcontractor under Paragraphs 11.0l.A.1 and 11.0l.A.2 and that any higher tier Subcontractor and Contractor will each be paid a fee of five percent (5%) of the amount paid to the next lower tier Subcontractor, however in no case shall the cumulative total of fees paid be in excess of 25%; c. no fee shall be payable on the basis of costs itemized under Paragraphs 11.0l.A.6, and 11.01.13; d. the amount of credit to be allowed by Contractor to City for any change which results in a net decrease in cost will be the amount of the actual net decrease in cost plus a deduction in Contractor's fee by an amount equal to five percent (5%) of such net decrease. 12.02 Change of Contract Time A. The Contract Time may only be changed by a Change Order. B. No extension of the Contract Time will be allowed for Extra Work or for claimed delay unless the Extra Work contemplated or claimed delay is shown to be on the critical path of the Project Schedule or Contractor can show by Critical Path Method analysis how the Extra Work or claime d delay adversely affects the critical path. 12.03 Delays A. Where Contractor is reasonably delayed in the performance or completion of any part of the Work within the Contract Time due to delay beyond the control of Contractor, the Contract Time may be extended in an amount equal to the time lost due to such delay if a Contract Claim is made therefor. Delays beyond the control of Contractor shall include, but not be limited to, acts or neglect by City, acts or neglect of utility owners or other contractors performing other work as contemplated by Article 7, fires, floods, epidemics, abnormal weather conditions, or acts of God. Such an adjustment shall be Contractor's sole and exclusive remedy for the delays described in this P aragraph. B. If Contractor is delayed, City shall not be liable to Contractor for any claims, costs, losses, or damages (including but not limited to all fees and charges of engineers, architects, attorneys, and other professionals and all court or arbitration or other dispute resolution costs) sustained by Contractor on or in connection with any other project or anticipated project. C. Contractor shall not be entitled to an adjustment in Contract Price or Contract Time for delays within the control of Contractor. Delays attributable to and within the control of a Subcontractor or Supplier shall be deemed to be delays within the control of Contractor. D. The Contractor shall receive no compensation for delays or hindrances to the Work, except when direct and unavoidable extra cost to the Contractor is caused by the failure of the City to provide information or material, if any, which is to be furnished by the City. CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: &23MI ATTACHMENT 1— AD1 007200-1 GENERAL OONDITIONS Page 48 of 63 ARTICLE 13 — TESTS AND INSPECTIONS; CORRECTION, REMOVAL OR ACCEPTANCE OF DEFECTIVE WORK 13.01 Notice ofDefects Notice of all defective Work of which City has actual knowledge will be given to Contractor. Defective Work may be rejected, corrected, or accepted as provided in this Article 13. 13.02 Access to Work City, independent testing laboratories, and governmental agencies with jurisdictional interests will have access to the Site and the Work at reasonable times for their observation, inspection, and testing. Contractor shall provide them proper and safe conditions for such access and advise them of Contractor's safety procedures and programs so that they may comply therewith as applicable. 13.03 Tests and Inspections A. Contractor shall give City timely notice of readiness of the Work for all required inspections, tests, or approvals and shall cooperate with inspection and testing personnel to facilitate required inspections or tests. B. If Contract Documents, Laws or Regulations of any public body having jurisdiction require any of the Work (or part thereof) to be inspected, tested, or approved, Contractor shall assume full responsibility for arranging and obtaining such independent inspections, tests, retests or approvals, pay all costs in connection therewith, and furnish City the required certificates of inspection or approval; excepting, however, those fees specifically identified in the Supplementary Conditions or any Texas Department of Licensure and Regulation (TDLR) inspections, which shall be paid as described in the Supplementary Conditions. C. Contractor shall be responsible for arranging and obtaining and shall pay all costs in connection with any inspections, tests, re -tests, or approvals required for City's acceptance of materials or equipment to be incorporated in the Work; or acceptance of materials, mix designs, or equipment submitted for approval prior to Contractor's purchase thereof for incorporation in the Work. Such inspections, tests, re -tests, or approvals shall be performed by organizations acceptable to City. D. City may arrange for the services of an independent testing laboratory ("Testing Lab") to perform any inspections or tests ("Testing") for any part of the Work, as determined solely by City. 1. City will coordinate such Testing to the extent possible, with Contractor; 2. Should any Testing under this Section 13.03 D result in a "fail", "did not pass" or other similar negative result, the Contractor shall be responsible for paying for any and all retests. Contractor's cancellation without cause of City initiated Testing shall be deemed a negative result and require a retest. CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1— AD1 007200-1 GENERAL OONDITIONS Page 49 of 63 3. Any amounts owed for any retest under this Section 13.03 D shall be paid directly to the Testing Lab by Contractor. City will forward all invoices for retests to Contractor. 4. If Contractor fails to pay the Testing Lab, City will not issue Final Payment until the Testing Lab is paid. E. If any Work (or the work of others) that is to be inspected, tested, or approved is covered by Contractor without written concurrence of City, Contractor shall, if requested by City, uncover such Work for observation. F. Uncovering Work as provided in Paragraph 13.03.E shall be at Contractor's expense. G. Contractor shall have the right to make a Contract Claim regarding any retest or invoice issued under Section 13.03 D. 13.04 Uncovering Work A. If any Work is covered contrary to the Contract Documents or specific instructions by the City, it must, if requested by City, be uncovered for City's observation and replaced at Contractor's expense. B. If City considers it necessary or advisable that covered Work be observed by City or inspected or tested by others, Contractor, at City's request, shall uncover, expose, or otherwise make available for observation, inspection, or testing as City may require, that portion of the Work in question, furnishing all necessary labor, material, and equipment. 1. If it is found that the uncovered Work is defective, Contractor shall pay all claims, costs, losses, and damages (including but not limited to all fees and charges of engineers, architects, attorneys, and other professionals and all court or other dispute resolution costs) arising out of or relating to such uncovering, exposure, observation, inspection, and testing, and of satisfactory replacement or reconstruction (including but not limited to all costs of repair or replacement of work of others); or City shall be entitled to accept defective Work in accordance with Paragraph 13.08 in which case Contractor shall still be responsible for all costs associated with exposing, observing, and testing the defective Work. 2. If the uncovered Work is not found to be defective, Contractor shall be allowed an increase in the Contract Price or an extension of the Contract Time, or both, directly attributable to such uncovering, exposure, observation, inspection, testing, replacement, and reconstruction. 13.05 City May Stop the Work If the Work is defective, or Contractor fails to supply sufficient skilled workers or suitable materials or equipment, or fails to perform the Work in such a way that the completed Work will conform to the Contract Documents, City may order Contractor to stop the Work, or any portion thereof, until the cause for such order has been eliminated; however, this right of City to stop the Work shall not give rise to any duty on the part of City to exercise this right for the benefit of Contractor, any CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1— AD1 007200-1 GENERAL OONDITIONS Page 50 of 63 Subcontractor, any Supplier, any other individual or entity, or any surety for, or employee or agent of any of them. 13.06 Correction orRemoval of Defective Work A. Promptly after receipt of written notice, Contractor shall correct all defective Work pursuant to an acceptable schedule, whether or not fabricated, installed, or completed, or, if the Work has been rejected by City, remove it from the Project and replace it with Work that is not defective. Contractor shall pay all claims, costs, additional testing, losses, and damages (including but not limited to all fees and charges of engineers, architects, attorneys, and other professionals and all court or arbitration or other dispute resolution costs) arising out of or relating to such correction or removal (including but not limited to all costs of repair or replacement of work of others). Failure to require the removal of any defective Work shall not constitute acceptance of such Work. B. When correcting defective Work under the terms of this Paragraph 13.06 or Paragraph 13.07, Contractor shall take no action that would void or otherwise impair City's special warranty and guarantee, if any, on said Work. 13.07 Correction Period A. If within two (2) years after the date of Final Acceptance (or such longer period of time as may be prescribed by the terms of any applicable special guarantee required by the Contract Documents), any Work is found to be defective, or if the repair of any damages to the land or areas made available for Contractor's use by City or permitted by Laws and Regulations as contemplated in Paragraph 6.10.A is found to be defective, Contractor shall promptly, without cost to City and in accordance with City's written instructions: 1. repair such defective land or areas; or 2. correct such defective Work; or 3. if the defective Work has been rejected by City, remove it from the Project and replace it with Work that is not defective, and 4. satisfactorily correct or repair or remove and replace any damage to other Work, to the work of others or other land or areas resulting therefrom. B. If Contractor does not promptly comply with the terms of City's written instructions, or in an emergency where delay would cause serious risk of loss or damage, City may have the defective Work corrected or repaired or may have the rejected Work removed and replaced. All claims, costs, losses, and damages (including but not limited to all fees and charges of engineers, architects, attorneys, and other professionals and all court or other dispute resolution costs) arising out of or relating to such correction or repair or such removal and replacement (including but not limited to all costs of repair or replacement of work of others) will be paid by Contractor. CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1— AD1 007200-1 GENERAL OONDITIONS Page 51 of 63 C. In special circumstances where a particular item of equipment is placed in continuous service before Final Acceptance of all the Work, the correction period for that item may start to run from an earlier date if so provided in the Contract Documents. D. Where defective Work (and damage to other Work resulting therefrom) has been corrected or removed and replaced under this Paragraph 13.07, the correction period hereunder with respect to such Work may be required to be extended for an additional period of one year after the end of the initial correction period. City shall provide 30 days written notice to Contractor should such additional warranty coverage be required. Contractor may dispute this requirement by filing a Contract Claim, pursuant to Paragraph 10.06. E. Contractor's obligations under this Paragraph 13.07 are in addition to any other obligation or warranty. The provisions of this Paragraph 13.07 shall not be construed as a substitute for, or a waiver of, the provisions of any applicable statute of limitation or repose. 13.08 Acceptance of Defective Work If, instead of requiring correction or removal and replacement of defective Work, City prefers to accept it, City may do so. Contractor shall pay all claims, costs, losses, and damages (including but not limited to all fees and charges of engineers, architects, attorneys, and other professionals and all court or other dispute resolution costs) attributable to City's evaluation of and determination to accept such defective Work and for the diminished value of the Work to the extent not otherwise paid by Contractor. If any such acceptance occurs prior to Final Acceptance, a Change Order will be issued incorporating the necessary revisions in the Contract Documents with respect to the Work, and City shall be entitled to an appropriate decrease in the Contract Price, reflecting the diminished value of Work so accepted. 13.09 City May Correct Defective Work A. If Contractor fails within a reasonable time after written notice from City to correct defective Work, or to remove and replace rejected Work as required by City in accordance with Paragraph 13.06.A, or if Contractor fails to perform the Work in accordance with the Contract Documents, or if Contractor fails to comply with any other provision of the Contract Documents, City may, after seven (7) days written notice to Contractor, correct, or remedy any such deficiency. B. In exercising the rights and remedies under this Paragraph 13.09, City shall proceed expeditiously. In connection with such corrective or remedial action, City may exclude Contractor from all or part of the Site, take possession of all or part of the Work and suspend Contractor's services related thereto, and incorporate in the Work all materials and equipment incorporated in the Work, stored at the Site or for which City has paid Contractor but which are stored elsewhere. Contractor shall allow City, City's representatives, agents, consultants, employees, and City's other contractors, access to the Site to enable City to exercise the rights and remedies under this Paragraph. C. All claims, costs, losses, and damages (including but not limited to all fees and charges of engineers, architects, attorneys, and other professionals and all court or other dispute resolution CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1— AD1 007200-1 GENERAL OONDITIONS Page 52 of 63 costs) incurred or sustained by City in exercising the rights and remedies under this Paragraph 13.09 will be charged against Contractor, and a Change Order will be issued incorporating the necessary revisions in the Contract Documents with respect to the Work; and City shall be entitled to an appropriate decrease in the Contract Price. D. Contractor shall not be allowed an extension of the Contract Time because of any delay in the performance of the Work attributable to the exercise of City's rights and remedies under this Paragraph 13.09. ARTICLE 14 — PAYMENTS TO CONTRACTOR AND COMPLETION 14.01 Schedule of Values The Schedule of Values for lump sum contracts established as provided in Paragraph 2.07 will serve as the basis for progress payments and will be incorporated into a form of Application for Payment acceptable to City. Progress payments on account of Unit Price Work will be based on the number of units completed. 14.02 Progress Payments A. ApplicationsforPayments: 1. Contractor is responsible for providing all information as required to become a vendor of the City. 2. At least 20 days before the date established in the General Requirements for each progress payment, Contractor shall submit to City for review an Application for Payment filled out and signed by Contractor covering the Work completed as of the date of the Application and accompanied by such supporting documentation as is required by the Contract Documents. 3. If payment is requested on the basis of materials and equipment not incorporated in the Work but delivered and suitably stored at the Site or at another location agreed to in writing, the Application for Payment shall also be accompanied by a bill of sale, invoice, or other documentation warranting that City has received the materials and equipment free and clear of all Liens and evidence that the materials and equipment are covered by appropriate insurance or other arrangements to protect City's interest therein, all of which must be satisfactory to City. 4. Beginning with the second Application for Payment, each Application shall include an affidavit of Contractor stating that previous progress payments received on account of the Work have been applied on account to discharge Contractor's legitimate obligations associated with prior Applications for Payment. 5. The amount of retainage with respect to progress payments will be as described in subsection C. unless otherwise stipulated in the Contract Documents. CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1— AD1 007200-1 GENERAL OONDITIONS Page 53 of 63 B. Review of Applications: 1. City will, after receipt of each Application for Payment, either indicate in writing a recommendation of payment or return the Application to Contractor indicating reasons for refusing payment. In the latter case, Contractor may make the necessary corrections and resubmit the Application. 2. City's processing of any payment requested in an Application for Payment will be based on City's observations of the executed Work, and on City's review of the Application for Payment and the accompanying data and schedules, that to the best of City's knowledge: a. the Work has progressed to the point indicated; b. the quality of the Work is generally in accordance with the Contract Documents (subject to an evaluation of the Work as a functioning whole prior to or upon Final Acceptance, the results of any subsequent tests called for in the Contract Documents, a final determination of quantities and classifications for Work performed under Paragraph 9.05, and any other qualifications stated in the recommendation). 3. Processing any such payment will not thereby be deemed to have represented that: a. inspections made to check the quality or the quantity of the Work as it has been performed have been exhaustive, extended to every aspect of the Work in progress, or involved detailed inspections of the Work beyond the responsibilities specifically assigned to City in the Contract Documents; or b. there may not be other matters or issues between the parties that might entitle Contractor to be paid additionally by City or entitle City to withhold payment to Contractor; or c. Contractor has complied with Laws and Regulations applicable to Contractor's performance of the Work. 4. City may refuse to process the whole or any part of any payment because of subsequently discovered evidence or the results of subsequent inspections or tests, and revise or revoke any such payment previously made, to such extent as may be necessary to protect City from loss because: a. the Work is defective or completed Work has been damaged by the Contractor or subcontractors requiring correction or replacement; b. discrepancies in quantities contained in previous applications for payment; c. the Contract Price has been reduced by Change Orders; d. City has been required to correct defective Work or complete Work in accordance with Paragraph 13.09; or CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1— AD1 007200-1 GENERAL CONDITIONS Page 54 of 63 e. City has actual knowledge of the occurrence of any of the events enumerated in Paragraph 15.02.A. C. Retainage: 1. For contracts less than $400,000 at the time of execution, retainage shall be ten percent (10%). 2. For contracts greater than $400,000 at the time of execution, retainage shall be five percent (5%). D. Liquidated Damages. For each calendar day that any work shall remain uncompleted after the time specified in the Contract Documents, the sum per day specified in the Agreement will be assessed against the monies due the Contractor, not as a penalty, but as damages suffered by the City. E. Payment: Contractor will be paid pursuant to the requirements of this Article 14 and payment will become due in accordance with the Contract Documents. F. Reduction in Payment: 1. City may refuse to make payment of the amount requested because: a. Liens have been filed in connection with the Work, except where Contractor has delivered a specific bond satisfactory to City to secure the satisfaction and discharge of such Liens; b. there are other items entitling City to a set-off against the amount recommended; or c. City has actual knowledge of the occurrence of any of the events enumerated in Paragraphs 14.02.B.4.a through 14.02.B.4.e or Paragraph 15.02.A. 2. If City refuses to make payment of the amount requested, City will give Contractor written notice stating the reasons for such action and pay Contractor any amount remaining after deduction of the amount so withheld. City shall pay Contractor the amount so withheld, or any adjustment thereto agreed to by City and Contractor, when Contractor remedies the reasons for such action. 14.03 Contractor's Warranty of Title Contractor warrants and guarantees that title to all Work, materials, and equipment covered by any Application for Payment, whether incorporated in the Project or not, will pass to City no later than the time of payment free and clear of all Liens. CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: &23/202I ATTACHMENT 1— AD1 007200-1 GENERAL OONDITIONS Page 55 of 63 14.04 Partial Utilization A. Prior to Final Acceptance of all the Work, City may use or occupy any part of the Work which has specifically been identified in the Contract Documents, or which City determines constitutes a separately functioning and usable part of the Work that can be used for its intended purpose without significant interference with Contractor's performance of the remainder of the Work. City at any time may notify Contractor in writing to permit City to use or occupy any such part of the Work which City determines to be ready for its intended use, subject to the following conditions: 1. Contractor at any time may notify City in writing that Contractor considers any such part of the Work ready for its intended use. 2. Within a reasonable time after notification as enumerated in Paragraph 14.05.A.1, City and Contractor shall make an inspection of that part of the Work to determine its status of completion. If City does not consider that part of the Work to be substantially complete, City will notify Contractor in writing giving the reasons therefor. 3. Partial Utilization will not constitute Final Acceptance by City. 14.05 Finallnspection A. Upon written notice from Contractor that the entire Work is Substantially Complete in accordance with the Contract Documents: 1. Within 10 days, City will schedule a Final Inspection with Contractor. 2. City will notify Contractor in writing of all particulars in which this inspection reveals that the Work is incomplete or defective ("Punch List Items"). Contractor shall immediately take such measures as are necessary to complete such Work or remedy such deficiencies. B. No time charge will be made against the Contractor between said date of notification to the City of Substantial Completion and the date of Final Inspection. 1. Should the City determine that the Work is not ready for Final Inspection, City will notify the Contractor in writing of the reasons and Contract Time will resume. 2. Should the City concur that Substantial Completion has been achieved with the exception of any Punch List Items, Contract Time will resume for the duration it takes for Contractor to achieve Final Acceptance. 14.06 Final Acceptance Upon completion by Contractor to City's satisfaction, of any additional Work identified in the Final Inspection, City will issue to Contractor a letter of Final Acceptance. CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1— AD1 007200-1 GENERAL CONDITIONS Page 56 of 63 14.07 Final Payment A. ApplicationforPayment: Upon Final Acceptance, and in the opinion of City, Contractor may make an application for final payment following the procedure for progress payments in accordance with the Contract Documents. 2. The final Application for Payment shall be accompanied (except as previously delivered) by: a. all documentation called for in the Contract Documents, including but not limited to the evidence of insurance required by Paragraph 5.03; b. consent of the surety, if any, to final payment; c. a list of all pending or released Damage Claims against City that Contractor believes are unsettled; and d. affidavits of payments and complete and legally effective releases or waivers (satisfactory to City) of all Lien rights arising out of or Liens filed in connection with the Work. B. Payment Becomes Due.• 1. After City's acceptance of the Application for Payment and accompanying documentation, requested by Contractor, less previous payments made and any sum City is entitled, including but not limited to liquidated damages, will become due and payable. 2. After all Damage Claims have been resolved: a. directly by the Contractor or; b. Contractor provides evidence that the Damage Claim has been reported to Contractor's insurance provider for resolution. 3. The making of the final payment by the City shall not relieve the Contractor of any guarantees or other requirements of the Contract Documents which specifically continue thereafter. 14.08 Final Completion Delayed and Partial Retain age Release A. If final completion of the Work is significantly delayed, and if City so confirms, City may, upon receipt of Contractor's final Application for Payment, and without terminating the Contract, make payment of the balance due for that portion of the Work fully completed and accepted. If the remaining balance to be held by City for Work not fully completed or corrected is less than the retainage stipulated in Paragraph 14.02.C, and if bonds have been furnished as required in Paragraph 5.02, the written consent of the surety to the payment of the balance due for that CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: &23/202I ATTACHMENT 1— AD1 007200-1 GENERAL OONDITIONS Page 57 of 63 portion of the Work fully completed and accepted shall be submitted by Contractor to City with the Application for such payment. Such payment shall be made under the terms and conditions governing final payment, except that it shall not constitute a waiver of Contract Claims. B. Partial Retainage Release. For a Contract that provides for a separate vegetative establishment and maintenance, and test and performance periods following the completion of all other construction in the Contract Documents for all Work locations, the City may release a portion of the amount retained provided that all other work is completed as determined by the City. Before the release, all submittals and final quantities must be completed and accepted for all other work. An amount sufficient to ensure Contract compliance will be retained. 14.09 Waiver of Claims The acceptance of final payment will constitute a release of the City from all claims or liabilities under the Contract for anything done or furnished or relating to the work under the Contract Documents or any act or neglect of City related to or connected with the Contract. ARTICLE 15 — SUSPENSION OF WORK AND TERMINATION 15.01 City May Suspend Work A. At any time and without cause, City may suspend the Work or any portion thereof by written notice to Contractor and which may fix the date on which Work will be resumed. Contractor shall resume the Work on the date so fixed. During temporary suspension of the Work covered by these Contract Documents, for any reason, the City will make no extra payment for stand-by time of construction equipment and/or construction crews. B. Should the Contractor not be able to complete a portion of the Project due to causes beyond the control of and without the fault or negligence of the Contractor, and should it be determined by mutual consent of the Contractor and City that a solution to allow construction to proceed is not available within a reasonable period of time, Contractor may request an extension in Contract Time, directly attributable to any such suspension. C. If it should become necessary to suspend the Work for an indefinite period, the Contractor shall store all materials in such a manner that they will not obstruct or impede the public unnecessarily nor become damaged in any way, and he shall take every precaution to prevent damage or deterioration of the work performed; he shall provide suitable drainage about the work, and erect temporary structures where necessary. D. Contractor may be reimbursed for the cost of moving his equipment off the job and returning the necessary equipment to the job when it is determined by the City that construction may be resumed. Such reimbursement shall be based on actual cost to the Contractor of moving the equipment and no profit will be allowed. Reimbursement may not be allowed if the equipment is moved to another construction project for the City. CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1— AD1 007200-1 GENERAL OONDITIONS Page 58 of 63 15.02 City May Terminate for Cause A. The occurrence of any one or more of the following events by way of example, but not of limitation, may justify termination for cause: 1. Contractor's persistent failure to perform the Work in accordance with the Contract Documents (including, but not limited to, failure to supply sufficient skilled workers or suitable materials or equipment, failure to adhere to the Project Schedule established under Paragraph 2.07 as adjusted from time to time pursuant to Paragraph 6.04, or failure to adhere to the City's Business Diversity Enterprise Ordinance #20020-12-201lestablished under Paragraph 6.06.D); 2. Contractor's disregard of Laws or Regulations of any public body having jurisdiction; 3. Contractor's repeated disregard of the authority of City; or 4. Contractor's violation in any substantial way of any provisions of the Contract Documents; or 5. Contractor's failure to promptly make good any defect in materials or workmanship, or defects of any nature, the correction of which has been directed in writing by the City; or 6. Substantial indication that the Contractor has made an unauthorized assignment of the Contract or any funds due therefrom for the benefit of any creditor or for any other purpose; or 7. Substantial evidence that the Contractor has become insolvent or bankrupt, or otherwise financially unable to carry on the Work satisfactorily; or 8. Contractor commences legal action in a court of competent jurisdiction against the City. B. If one or more of the events identified in Paragraph 15.02A. occur, City will provide written notice to Contractor and Surety to arrange a conference with Contractor and Surety to address Contractor's failure to perform the Work. Conference shall be held not later than 15 days, after receipt of notice. 1. If the City, the Contractor, and the Surety do not agree to allow the Contractor to proceed to perform the construction Contract, the City may, to the extent permitted by Laws and Regulations, declare a Contractor default and formally terminate the Contractor's right to complete the Contract. Contractor default shall not be declared earlier than 20 days after the Contractor and Surety have received notice of conference to address Contractor's failure to perform the Work. 2. If Contractor's services are terminated, Surety shall be obligated to take over and perform the Work. If Surety does not commence performance thereof within 15 consecutive calendar days after date of an additional written notice demanding Surety's performance of its CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1— AD1 007200-1 GENERAL OONDITIONS Page 59 of 63 obligations, then City, without process or action at law, may take over any portion of the Work and complete it as described below. a. If City completes the Work, City may exclude Contractor and Surety from the site and take possession of the Work, and all materials and equipment incorporated into the Work stored at the Site or for which City has paid Contractor or Surety but which are stored elsewhere, and finish the Work as City may deem expedient. 3. Whether City or Surety completes the Work, Contractor shall not be entitled to receive any further payment until the Work is finished. If the unpaid balance of the Contract Price exceeds all claims, costs, losses and damages sustained by City arising out of or resulting from completing the Work, such excess will be paid to Contractor. If such claims, costs, losses and damages exceedsuch unpaid balance, Contractor shall pay the difference to City. Such claims, costs, losses and damages incurred by City will be incorporated in a Change Order, provided that when exercising any rights or remedies under this Paragraph, City shall not be required to obtain the lowest price for the Work performed. 4. Neither City, nor any of its respective consultants, agents, officers, directors or employees shall be in any way liable or accountable to Contractor or Surety for the method by which the completion of the said Work, or any portion thereof, may be accomplished or for the price paid therefor. City, notwithstanding the method used in completing the Contract, shall not forfeit the right to recover damages from Contractor or Surety for Contractor's failure to timely complete the entire Contract. Contractor shall not be entitled to any claim on account of the method used by City in completing the Contract. 6. Maintenance of the Work shall continue to be Contractor's and Surety's responsibilities as provided for in the bond requirements of the Contract Documents or any special guarantees provided for under the Contract Documents or any other obligations otherwise prescribed by law. C. Notwithstanding Paragraphs 15.02.13, Contractor's services will not be terminated if Contractor begins within seven days of receipt of notice of intent to terminate to correct its failure to perform and proceeds diligently to cure such failure within no more than 30 days of receipt of said notice. D. Where Contractor's services have been so terminated by City, the termination will not affect any rights or remedies of City against Contractor then existing or which may thereafter accrue. Any retention or payment of moneys due Contractor by City will not release Contractor from liability. E. If and to the extent that Contractor has provided a performance bond under the provisions of Paragraph 5.02, the termination procedures of that bond shall not supersede the provisions of this Article. CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1- AD1 007200-1 GENERAL OONDITIONS Page 60 of 63 15.03 City May Terminate For Convenience A. City may, without cause and without prejudice to any other right or remedy of City, terminate the Contract. Any termination shall be effectedby mailing a notice of the termination to the Contractor specifying the extent to which performance of Work under the contract is terminated, and the date upon which such termination becomes effective. Receipt of the notice shall be deemed conclusively presumed and established when the letter is placed in the United States Postal Service Mail by the City. Further, it shall be deemed conclusively presumed and established that such termination is made with just cause as therein stated; and no proof in any claim, demand or suit shall be required of the City regarding such discretionary action. B. After receipt of a notice of termination, and except as otherwise directed by the City, the Contractor shall: 1. Stop work under the Contract on the date and to the extent specified in the notice of termination; 2. place no further orders or subcontracts for materials, services or facilities except as may be necessary for completion of such portion of the Work under the Contract as is not terminated; 3. terminate all orders and subcontracts to the extent that they relate to the performance of the Work terminated by notice of termination; 4. transfer title to the City and deliver in the manner, at the times, and to the extent, if any, directed by the City: a. the fabricated or unfabricated parts, Work in progress, completed Work, supplies and other material produced as a part of, or acquired in connection with the performance of, the Work terminated by the notice of the termination; and b. the completed, or partially completed plans, drawings, information and other property which, if the Contract had been completed, would have been required to be furnished to the City. 5. complete performance of such Work as shall not have been terminated by the notice of termination; and 6. take such action as may be necessary, or as the City may direct, for the protection and preservation of the property related to its contract which is in the possession of the Contractor and in which the owner has or may acquire the rest. C. At a time not later than 30 days after the termination date specified in the notice of termination, the Contractor may submit to the City a list, certified as to quantity and quality, of any or all items of termination inventory not previously disposed of, exclusive of items the disposition of which has been directed or authorized by City. CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1— AD1 007200-1 GENERAL OONDITIONS Page 61 of 63 D. Not later than 15 days thereafter, the City shall accept title to such items provided, that the list submitted shall be subject to verification by the City upon removal of the items or, if the items are stored, within 45 days from the date of submission of the list, and any necessary adjustments to correct the list as submitted, shall be made prior to final settlement. E. Not later than 60 days after the notice of termination, the Contractor shall submit his termination claim to the City in the form and with the certification prescribed by the City. Unless an extension is made in writing within such 60 day period by the Contractor, and granted by the City, any and all such claims shall be conclusively deemed waived. F. In such case, Contractor shall be paid for (without duplication of any items): 1. completed and acceptable Work executed in accordance with the Contract Documents prior to the effective date of termination, including fair and reasonable sums for overhead and profit on such Work; 2. expenses sustained prior to the effective date of termination in performing services and furnishing labor, materials, or equipment as required by the Contract Documents in connection with uncompleted Work, plus fair and reasonable sums for overhead and profit on such expenses; and 3. reasonable expenses directly attributable to termination. G. In the event of the failure of the Contractor and City to agree upon the whole amount to be paid to the Contractor by reason of the termination of the Work, the City shall determine, on the basis of information available to it, the amount, if any, due to the Contractor by reasonof the termination and shall pay to the Contractor the amounts determined. Contractor shall not be paid on account of loss of anticipated profits or revenue or other economic loss arising out of or resulting from such termination. ARTICLE 16 — DISPUTE RESOLUTION 16.01 Methods and Procedures A. Either City or Contractor may request mediation of any Contract Claim submitted for a decision under Paragraph 10.06 before such decision becomes final and binding. The request for mediation shall be submitted to the other party to the Contract. Timely submission of the request shall stay the effect of Paragraph 10.06.E. B. City and Contractor shall participate in the mediation process in good faith. The process shall be commenced within 60 days of filing of the request. C. If the Contract Claim is not resolved by mediation, City's action under Paragraph 10.06.0 or a denial pursuant to Paragraphs 10.06.C.3 or 10.06.D shall become final and binding 30 days after termination of the mediation unless, within that time period, City or Contractor: CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1— AD1 007200-1 GENERAL CONDITIONS Page 62 of 63 elects in writing to invoke any other dispute resolution process provided for in the Supplementary Conditions; or 2. agrees with the other party to submit the Contract Claim to another dispute resolution process; or 3. gives written notice to the other party of the intent to submit the Contract Claim to a court of competent jurisdiction. ARTICLE 17 — MISCELLANEOUS 17.01 Giving Notice A. Whenever any provision of the Contract Documents requires the giving of written notice, it will be deemed to have been validly given if: delivered in person to the individual or to a member of the firm or to an officer of the corporation for whom it is intended; or 2. delivered at or sent by registered or certified mail, postage prepaid, to the last business address known to the giver of the notice. B. Business address changes must be promptly made in writing to the other party. C. Whenever the Contract Documents specifies giving notice by electronic means such electronic notice shall be deemed sufficient upon confirmation of receipt by the receiving party. 17.02 Computation of Times When any period of time is referred to in the Contract Documents by days, it will be computed to exclude the first and include the last day of such period. If the last day of any such period falls on a Saturday or Sunday or on a day made a legal holiday the next Working Day shall become the last day of the period. 17.03 Cumulative Remedies The duties and obligations imposed by these General Conditions and the rights and remedies available hereunder to the parties hereto are in addition to, and are not to be construed in any way as a limitation of, any rights and remedies available to any or all of them which are otherwise imposed or available by Laws or Regulations, by special warranty or guarantee, or by other provisions of the Contract Documents. The provisions of this Paragraph will be as effective as if repeated specifically in the Contract Documents in connection with each particular duty, obligation, right, and remedy to which they apply. CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: &23/202I ATTACHMENT 1— AD1 007200-1 GENERAL OONDITIONS Page 63 of 63 17.04 Survival of Obligations All representations, indemnifications, warranties, and guarantees made in, required by, or given in accordance with the Contract Documents, as well as all continuing obligations indicated in the Contract Documents, will survive final payment, completion, and acceptance of the Work or termination or completion of the Contract or termination of the services of Contractor. 17.05 Headings Article and paragraph headings are inserted for convenience only and do not constitute parts of these General Conditions. CITY OF FORT WORTH SCADA System Replacement STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS 103086 Revision: 92312MI ATTACHMENT 1— AD1 00 73 00 SUPPLEMENTARY CONDITIONS TO GENERAL CONDITIONS Page 1 of 10 61wo" 1610111110111111 SUPPLEMENTARY CONDITIONS TO GENERAL CONDITIONS SUPPLEMENTARY CONDITIONS These Supplementary Conditions modify and supplement Section 00 72 00 — General Conditions, and other provisions of the Contract Documents as indicated below. All provisions of the General Conditions that are modified or supplemented remain in full force and effect as so modified or supplemented. All provisions of the General Conditions which are not so modified or supplemented remain in full force and effect. DEFINED TERMS The terms used in these Supplementary Conditions which are defined in the General Conditions have the meaning assigned to them in the General Conditions, unless specifically noted herein. MODIFICATIONS AND SUPPLEMENTS The following are instructions that modify or supplement specific paragraphs in the General Conditions and other Contract Documents. SC-1.01 "DEFINED TERMS" A. Delete 1.01 A.6. and replace with: "6. Bid; Proposal —An offer submitted to the Owner for the Project setting forth the Contract Price and Contract Times for the Work to be performed." Delete 1.0IA. 7. and replace with: "T Bidder; Offeror — The individual or entity who submits a bid or proposal." Delete 1.01 A.8 and replace with: "8. Bidding Documents; Proposal Documents - The Bidding Requirements or Proposal Requirements, the proposed Contract Documents, and Addenda." B. Delete 1.01 A.9. and replace with: "9. Bidding Requirements; Proposal Requirements — The Invitation to Bidders or Notice to Offerors, Instructions to Bidders or Offerors, Bid Security or Proposal Security, Bid Form or Proposal Form and attachments, and required certifications and affidavits." C. Delete 1.01 A.21. and replace with: "21. Contract Time —The number of days or the dates stated and agreed to in the Proposal and executed in the Agreement to: (i) achieve the milestones as stated therein and (ii) complete the Work so that it is ready for Final Acceptance. The Contract Time will run continuously except as otherwise noted in this Section." CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 2 — AD1 00 73 00 SUPPLEMENTARY CONDITIONS TO GENERAL CONDITIONS Page 2 of 10 D. Delete 1.01 A.33. and replace with: "33. Engineer — The licensed professional engineer or engineering firm registered in the State of Texas performing professional services for the City, for the purposes of this Agreement the Engineer is Arcadis U.S., Inc." Delete 1.01 A. 46. and replace with: "46. Notice to Proceed — A written notice given by the City to the Contractor fixing the date on which the Contract Time will commence to run and on which the Contractor shall start to perform all of the Work or such portion of the Work as explicitly authorized by the Notice to Proceed. Where all portions of the Work are not authorized by the initial Notice to Proceed, one or more additional Notice to Proceed documents will be provided by the City to give written notice to the Contractor to start to perform additional portions of the Work until all of the Work is authorized. The Contract Time will run continuously except as otherwise noted in this Section." Delete 1.01 A. 55 and replace with: "55. Regular Working Hours — Hours beginning at 7:00 a.m. and ending at 4:30 p.m., Monday thru Friday (excluding legal holidays) for all Work at Water Treatment Plant Sites." E. Delete 1.01 A. 70. and replace with: "70. Weekend Working Hours — Hours beginning at 9:00 a.m. and ending at 4:30 p.m., Saturday, Sunday, or legal holiday. as approved in advance by the City. Legal holidays annually observed by the City include Labor Day, Veterans Day, Thanksgiving (2 days), Christmas (2 days), New Year's Day, Martin Luther King Day, President's Day, Memorial Day and Independence Day (a total of 11 days)." F. Add the following additional definitions immediately following GC 1.01 A.72.: "73. Bid Security; Proposal Security —The financial security provided by Bidder or Offeror at the time the Bid or Proposal is submitted and held by Owner until the Agreement is executed and the evidence of insurance and bonds required by the Contract Documents are provided. 74. Design Engineer - The licensed professional engineer or engineering firm registered in the State of Texas performing professional services for the Contractor, to perform delegated design duties required by the Contract Documents. The name of the firm shall be added to the Contract Document Section 01 33 00 Table 01 33-A and shall perform all duties assigned by the document as the Engineer -of -Record for improvements for which the firm provides sealed submittal documents. 75. Special Warranty — An extended warranty period applicable to all or any part of the Work as required by the Contract Documents. The period is a Special Guarantee for the purpose of establishing an extended Correction Period for the specified portions of the Work as noted in Article 13.07 of the General Conditions." CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 2 — AD1 00 73 00 SUPPLEMENTARY CONDITIONS TO GENERAL CONDITIONS Page 3 of 10 SC-2.02 "COMMENCEMENT OF CONTRACT TIME: NOTICE TO PROCEED" Delete the text presented in Article 2.02 and replace with: "A. The Contract Time will commence to run on the day indicated in the initial Notice to Proceed. B. Each Notice to Proceed will include a description of the Work or portions of the Work upon which the Contractor is authorized by the City to start work. C. The Contract Time will run continuously except as described in Article 14.05 Final Inspection of all Work. Partial Utilization of portions of the Work by the City shall not affect Contract Time as noted in Article 14.04 A. 3 of this Section. D. Notice to Proceed with any portion of the Work will not be provided by the City prior to receipt of executed bonds noted in Article 5.02 of this Section covering all portions of the Work noted in the Notice to Proceed." SC-2.03"STARTING THE WORK" Delete the text presented in Article 2.03 and replace with: "A. Contractor shall start to perform the authorized portions of the Work on the date when the Contract Time commences to run. No portion of the Work shall be done by the Contractor prior to the date on which the Contract Time commences to run. B. Where the Contractor elects to utilize phased bonding in accordance with Article 5.02 A., the initial Notice to Proceed shall authorize the start of Work on only a portion of the Work. The Contractor shall provide executed bonds covering additional portions of the Work not previously authorized by a Notice to Proceed no later than 14 days in advance of the planned start of work on the added portions of the Work. In no case shall the Contractor begin such work prior to receipt of a Notice to Proceed specifically authorizing the added work. C. When notified that the Contractor is ready to begin portions of the Work not previously authorized by a Notice to Proceed, and upon receipt of executed Performance and Payment Bonds covering the added portions of the Work, the City shall issue a Notice to Proceed with such additional portions of the Work. D. The City will not issue a Notice to Proceed for any portion of the Work prior to receipt of executed Performance and Payment Bonds, that when combined with previously executed bonds, are of sufficient face value to cover all portions of the Work the Contractor wishes to proceed with. E. The Contractor shall not begin work on any other portions of the Work not authorized explicitly in a Notice to Proceed signed by the City." CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 2 — AD1 00 73 00 SUPPLEMENTARY CONDITIONS TO GENERAL CONDITIONS Page 4 of 10 SC-4.01 "AVAILABILITY OF LANDS" A. Add the following the end of GC 4.01 A. 1.: "Easement limits shown on the Drawing are approximate and were provided to establish a basis for bidding. Upon receiving the final easements descriptions, Contractor shall compare them to the lines shown on the Contract Drawings. B. Add GC 4.01 A. 3 immediately following GC 4.01 A.2.: "3. The following is a list of known outstanding right-of-way, and/or easements to be acquired, if any as of [Month Day, Year this document was prepared]: PARCEL NUMBER NONE OWNER TARGET DATE OF POSSESSION The Contractor understands and agrees that the dates listed above are estimates only, are not guaranteed, and do not bind the City. If Contractor considers the final easements provided to differ materially from the representations on the Contract Drawings, Contractor shall within five (5) Business Days and before proceeding with the Work, notify City in writing associated with the differing easement line locations." SC-4.01A.2, "AVAILABILITY OF LANDS" Utilities or obstructions to be removed, adjusted, and/or relocated. The following is list of utilities and/or obstructions that have not been removed, adjusted, and/or relocated as of the date of document preparation: EXPECTED UTILITY AND LOCATION TARGET DATE OF OWNER ADJUSTMENT I0 The Contractor understands and agrees that the dates listed above are estimates only, are not guaranteed, and do not bind the City. SC-4.02A., "SUBSURFACE AND PHYSICAL CONDITIONS" None CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 2 — AD1 00 73 00 SUPPLEMENTARY CONDITIONS TO GENERAL CONDITIONS Page 5 of 10 SC-4.06A., "HAZARDOUS ENVIRONMENTAL CONDITIONS AT SITE" A. Add GC 4.06A.2. immediately following GC 4.06A.1. "2. The following are reports and drawings of existing hazardous environmental conditions known to the City: None" SC-5.02 A., "PERFORMANCE, PAYMENT, AND MAINTENANCE BONDS" A. Add GC 5.02 A. 1. through 7. immediately following GC 5.02 A. "l . Performance and Payment Bonds accompanying the executed Agreement shall be in the full amount of the Contract Price unless the Contractor intends to provide phased bonding of the Work in accordance with Articles 5.02 A. 2. — 7. below. 2. When phased implementation of bonding is desired, accompanying the executed Agreement, the Contractor shall at minimum provide Performance and Payment Bonds in an amount equal to the total of. Proposal Item No. I (Mobilization), No. 2 (Familiarization and Preliminary Assessment) and No. 3 (Design) and all allowances in Proposal Item No. 10, No. 11, No. 12 and No. 13. 3. The Contractor shall provide additional Performance and Payment Bonds covering portions of the work in Proposal Item No. 4 (Eagle Mountain WTP Configuration, Cutover and Startup), No. 5 (South Holly WTP Configuration, Cutover and Startup), No. 6 (North Holly WTP Configuration, Cutover and Startup), No. 7 (Westside WTP Configuration, Cutover and Startup), No. 8 (Rolling Hills WTP Configuration, Cutover and Startup) and No. 9 (Centralized SCADA Configuration, Cutover and Startup) prior to beginning work associated with each Proposal Item. 4. Except for the bonds accompanying the executed Agreement, prior to the initial Notice to Proceed, the Contractor shall provide bonding in the amount of a single Proposal Item, or the total amount of a group of two or more Proposal Items for each phase. 5. Performance and Payment bonds covering only a portion of the work shall be accompanied by a cover letter that clearly states the Proposal Item Number and Description of the include the portion of the Work covered by the accompanying bonds. 6. The Contractor shall incorporate execution and delivery of the additional bonds as a scheduled construction task no later than 14 days in advance of the start of portions of the Work associated with a Proposal Item not covered by a prior bonding submittal. 7. The Contractor shall not commence any portion of the Work until a Notice to Proceed is provided by the City covering that portion of the Work." SC-5.03, "CERTIFICATES OF INSURANCE" In accordance with GC 5.03, the following entities are named as "Additional Insured" and shall be named on all liability policies, including their respective officers, directors, agents and employees: (1) City (2) Engineer: Arcadis U.S., Inc. (3) Other: None" CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 2 — AD1 00 73 00 SUPPLEMENTARY CONDITIONS TO GENERAL CONDITIONS Page 6 of 10 SC-5.04, "CONTRACTOR'S INSURANCE" The limits of liability for the insurance required by Paragraph GC-5.04 shall provide the following coverages for not less than the following amounts or greater where required by laws and regulations: A. 5.04A., Workers' Compensation, under Paragraph GC-5.04A., add the following: "3. Provide the following, Statutory limits Employer's liability $500,000 each accident/occurrence $500,000 Disease — each employee $500,000 Disease — policy limit" B. 5.04B., Commercial General Liability, under Paragraph GC-5.04B. Contractor's Liability Insurance under Paragraph GC-5.04B., add the following: "1. Coverage shall be on a per project basis covering the Contractor with minimum limits of: $1,000,000 each occurrence $2,000,000 aggregate limit 2. The policy must have an endorsement (Amendment — Aggregate Limits of Insurance) making the General Aggregate Limits apply separately to each job site. 3. The Commercial General Liability Insurance policies shall provide "X", "C", and "U" coverages. Verification of such coverage must be shown in the Remarks Article of the Certificate of Insurance." C. 5.04 C. Automobile Liability, under Paragraph GC-5.04 C. Contractor's Liability Insurance under Paragraph GC-5.04C., which shall be in an amount not less than the following amounts, add C. 1.: "1. Automobile Liability - a commercial business policy shall provide coverage on "Any Auto", defined as autos owned, hired and non -owned. $1,000,000 each accident on a combined single limit basis. Split limits are acceptable if limits are at least: $250,000 Bodily Injury per person / $500,000 Bodily Injury per accident / $100,000 Property Damage" CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 2 — AD1 00 73 00 SUPPLEMENTARY CONDITIONS TO GENERAL CONDITIONS Page 7 of 10 D. Add 5.04 F. following to 5.04 E.: "F. Contractor's Professional Liability Insurance: Purchase and maintain applicable professional liability insurance if Contractor will provide or furnish professional services under this Contract, through a delegation of professional design services or otherwise. This insurance must cover negligent acts, errors, or omissions in the performance of professional design or related services by the insured or others for whom the insured is legally liable. The insurance must be maintained throughout the duration of the Contract and for a minimum of 2 years after Final Acceptance. The policy must pre -date the commencement of furnishing services on the Project. 2. Provide the following coverage with not less than the minimum limits indicated: Policy Limit Each Claim $1,000,000 Annual Aggregate $1,000,000 " SC-6.04., "PROJECT SCHEDULE" Project schedule shall be Tier 3 for the project. SC-6.06., "CONCERNING SUBCONTRACTORS, SUPPLIERS, OTHERS" Replace "35%" with "40%" in GC 6.06-A. SC-6.07., "WAGE RATES" The following is the prevailing wage rate table(s) applicable to this project and is provided in the Appendixes: Appendix GC 6.07 — 2020 Prevailing Wage Rates for Vertical Construction SC-6.09., "PERMITS AND UTILITIES" SC-6.09A., "CONTRACTOR OBTAINED PERMITS AND LICENSES" The following are known permits and/or licenses required by the Contract to be acquired by the Contractor: None SC-6.09B. "CITY OBTAINED PERMITS AND LICENSES" The following are known permits and/or licenses required by the Contract to be acquired by the City: None CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 2 — AD1 00 73 00 SUPPLEMENTARY CONDITIONS TO GENERAL CONDITIONS Page 8 of 10 SC-6.09C. "OUTSTANDING PERMITS AND LICENSES" The following is a list of known outstanding permits and/or licenses to be acquired, if any as of None SC-6.18C, 3, "SUBMITTALS — CITY' REVIEW" Delete Article 6.18C. 3. And replace with the following: "3. City's review and acceptance shall not relieve Contractor from responsibility for any variation from the requirements of the Contract Documents unless Contractor has complied with the requirements of Section 0133 00 and City has given written acceptance. The Contractor must include a complete list of each such variation by specific written notation thereof incorporated in or accompanying the Submittal on the cover sheet and clearly note the variation on each page of the submittal affected by the variation. The terms "written acceptance" by the City for the purposes of this Article shall be defined and limited to either: 1) The statement "Variations proposed within this submittal are approved" made within the notations and comments returned to the Contractor or 2) Issuance of Field Order or Change Order. Regardless of the form or written acceptance, the City may restrict such written acceptance by indicating which variations within the Contractor's proposed list the City finds acceptable and which are being rejected. The City's review and acceptance shall not relieve Contractor from responsibility for complying with the requirements of the Contract Documents not modified by such written acceptance." SC-6.24B., Compliance with "TITLE VI, CIVIL RIGHTS ACT OF 1964 AS AMENDED" Below Article 6.24. B. of the General Conditions add Article C. below: "C. For any project receiving Federal assistance, 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, in accordance with Article 6.24. B of the General Conditions: 1. Compliance with Regulations: The Contractor shall comply with the Regulation relative to nondiscrimination in Federally -assisted programs of the Department of Transportation (hereinafter, "DOT") Title 49, Code of Federal Regulations, Part 21, as they may be amended from time to time, (hereinafter referred to as the Regulations), which are herein incorporated by reference and made a part of this contract. 2. Nondiscrimination: The Contractor, with regard to the work performed by it during the contract, shall not discriminate on the grounds of race, color, or national origin, in the selection and retention of subcontractors, including procurements of materials and leases of equipment. The Contractor shall not participate either directly or indirectly in the discrimination prohibited by 49 CFR, section 21.5 of the Regulations, including employment practices when the contract covers a program set forth in Appendix B of the Regulations. Solicitations for Subcontractors, Including Procurements of Materials and Equipment: In all solicitations either by competitive bidding or negotiation made by the contractor for work to be performed under a subcontract, including procurements of CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 2 — AD1 00 73 00 SUPPLEMENTARY CONDITIONS TO GENERAL CONDITIONS Page 9 of 10 materials or leases of equipment, each potential Subcontractor or supplier shall be notified by the Contractor of the Contractor's obligations under this contract and the Regulations relative to nondiscrimination on the grounds of race, color, or national origin. 4. Information and Reports: The Contractor shall provide all information and reports required by the Regulations or directives issued pursuant thereto, and shall permit access to its books, records, accounts, other sources of information and its facilities as may be determined by City or the Texas Department of Transportation to be pertinent to ascertain compliance with such Regulations, orders and instructions. Where any information required of a contractor is in the exclusive possession of another who fails or refuses to furnish this information the contractor shall so certify to the City, or the Texas Department of Transportation, as appropriate, and shall set forth what efforts it has made to obtain the information. 5. Sanctions for Noncompliance: In the event of the Contractor's noncompliance with the nondiscrimination provisions of this Contract, City shall impose such contract sanctions as it or the Texas Department of Transportation may determine to be appropriate, including, but not limited to: a. withholding of payments to the Contractor under the Contract until the Contractor complies, and/or b. cancellation, termination or suspension of the Contract, in whole or in part. Incorporation of Provisions: The Contractor shall include the provisions of paragraphs (1) through (6) in every subcontract, including procurements of materials and leases of equipment, unless exempt by the Regulations, or directives issued pursuant thereto. The Contractor shall take such action with respect to any subcontract or procurement as City or the Texas Department of Transportation may direct as a means of enforcing such provisions including sanctions for non-compliance: Provided, however, that, in the event a contractor becomes involved in, or is threatened with, litigation with a subcontractor or supplier as a result of such direction, the contractor may request City to enter into such litigation to protect the interests of City, and, in addition, the contractor may request the United States to enter into such litigation to protect the interests of the United States. Additional requirements associated with the City's equity goals can be found in Section 00 45 42 — Business Equity Specifications." SC-9.01., "CITY'S PROJECT MANAGER" The City's Project Manager for this Contract is Alexander Pierce, or his/her successor pursuant to written notification from the Director of the Water Department. CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 2 — AD1 00 73 00 SUPPLEMENTARY CONDITIONS TO GENERAL CONDITIONS Page 10 of 10 SC-13.07., "Correction Period" Add the words "Except as noted in Article 13.07 F. below," to the beginning of Article 13.07 A. Add Article 13.07 F: F. The Correction Period shall begin based on completion of portions of the Work as noted in the Contract Documents. The Correction Period for Work used or occupied in accordance with Partial Utilization as noted in Article 14.04 of the General Conditions shall begin prior to Final Acceptance of all Work when: 1. That portion of the work is a facility specifically identified in Section 07 78 36 — Warranties. 2. All items noted as requiring correction following the City's inspection of that portion of the work have been corrected." SC-14.01., "SCHEDULE OF VALUES" Add the following sentence to the end of Article 14.01: "Submit preliminary Schedule of Values within ten days following the date that the Contract Times commence running in accordance with Article 2.02 of the General Conditions." SC-16.01C.1, "METHODS AND PROCEDURES" None ++END OF SECTION++ CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 2 — AD1 01 11 13 SUMMARY OF WORK Page 1 of 12 SECTION 01 11 13 SUMMARY OF WORK PART 1 — GENERAL 1.1 SECTION INCLUDES Article Title 1.1 Section Includes 1.2 Location and Description of Work 1.3 Other Construction Contracts 1.4 Work by Others 1.5 Work by City 1.6 Summary of Work 1.7 Contractor's Use of Site 1.8 Partial Utilization by City 1.2 LOCATION AND DESCRIPTION OF WORK A. Locations: The Work is located at the Water Treatment Plants throughout the City of Fort Worth and adjacent Extraterritorial Jurisdiction (ETJ). It is the responsibility of the Contractor to review the location data, and subsequently provide the resources necessary to complete the proposed work. B. Overall Description of Work: Design, test, start-up, and maintain through Final Acceptance a complete replacement for the City's Water Department Supervisory Control and Data Acquisition (SCADA) system, inclusive of but not limited to: upgraded SCADA systems at each of the five Water Treatment Plant (WTPs); a new Centralized SCADA system, including remote alarm notification; an upgraded SCADA system architecture to support the SCADA Replacement; a new data architecture to support a comprehensive historical data collection, and reporting interface; other work elements to support the SCADA upgrades. The Work also includes installation and configuration of all SCADA software, including City -furnished software and other associated SCADA software procured by the Contractor as identified in the Contract Documents. C'._ Summnry of C',ontra& Document Attachments and Relevance to Work - Attachment 1 — PLC and HMI Standards — This attachment provides standards for all PLC and HMI work necessary to complete this project. a. PLC and other associated sole -sourced component requirements are listed to guide procurement of specific components required by the City. b. Performance standards and metrics are provided for PLCs, communications and HMI. CTTY OF FORT WORTH March 21, 2024 SCADA System Replacement 103086 01 11 13 SUMMARY OF WORK Page 2 of 12 C. Standards are provided for the development of any and all PLC code and HMI graphics. d. Standards are provided for the development of databases, tags, and all nomenclature to be used in the configuration and development of PLC and HMI applications. e. Standards are provided for security, environment and other relevant aspects to PLC and HMI application development. 2. Attachment 2 — City -furnished SCADA Software and Licenses — This attachment provides a list of all Software and Licenses already procured by the City for use on this project. This software and licensing will be provided by the City to the Contractor for use in development of the SCADA Replacement. 3. Attachment 3 — Existing HMI Databases — This includes a copy of all existing HMI databases. 4. Attachment 4 — Existing HMI Screens — This includes a copy of all existing HMI Screens. Attachment 5 — Existing Reports — This includes a copy of all applicable templates or generated reports to be used in the development of the data interface (dashboards, reports, etc.) included in the project. 6. Attachment 6 — Existing WTP PLC Systems Table - This table presents all of the WTP PLC systems and associated OITs, and divides into two categories: Category A PLCs which require upgraded programming, and Category B, which do not. 7. Attachment 7 — SCADA Assets Responsibility Matrix — This provides a list of the SCADA and network components, both hardware and software, and identifies responsibility for selection, procurement, installation, configuration, and maintenance. Attachment 8 — Sample Functional Control Narrative (FCN) Template — This document provides a template for developing the Functional Control Narratives for the WTP PLC Systems. D. Software by Others: 1. The City shall provide all HMI software for use on the SCADA Replacement project as indicated in Attachment 2 — City -Furnished SCADA Software and Licenses. 2. Unless otherwise specifically noted, the City shall provide all other software for the Work, including operating system, virtualization environment, network configuration and monitoring, backup, and database. E. Hardware by Others: 1. The City shall provide all hardware necessary for the Work, including but not limited to: PLCs and PLC components/mounting, OITs and OIT components/mounting, network hardware, computer and computer accessories, monitors, wallboards, supporting electrical infrastructure, network hardware. CTTY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 01 11 13 SUMMARY OF WORK Page 3 of 12 F. Key Components of Work. 1. Coordination: a. Coordination of work with City, City agencies, Water IT as identified to implement the work. b. Preparation of and adherence to Project Schedule, aligned with Milestones identified and coordinated with constraints identified in 01 14 16 Coordination with City Operations. 2. Familiarization, Preliminary Assessment, and Design of all Project Work: a. Familiarization and Preliminary Assessment as defined in 40 61 13 SCADA System General Provisions b. Design as defined in 40 61 13 SCADA System General Provisions 3. Construction Activities: Submittals, Workshops, configuration, cutover, testing, and acceptance demonstration periods for: a. Water Treatment Plants SCADA 1) New HMI applications with Situational Awareness Graphics in accordance with Attachment 1— PLC and HMI Configuration Standards. 2) Select upgrades of Programmable Logic Controllers (PLCs) and associated Operator Interface Terminals (OITs) at several WTPs. 3) New local historians to store all new WTP data and creation of local Plant Operational Reports. 4) Successful planned cutover of old SCADA system to new system. b. New Centralized SCADA system 1) New Reports, and Data Warehouse Interface. a) System -wide Data Interface consisting of plant historians, pass - through historian, centralized SCADA historian and data warehouse interface. b) Business and Central Operational Reports that interface to existing system's databases as identified in the Specifications. c) Tablets for Operator input and interfaced with Centralized SCADA. 2) Central Remote Alarm Monitoring and Notification: c. Testing and Acceptance: 1) Factory Testing, Site Testing, and Operational Availability Demonstration (OAD) periods. 4. Maintenance: a. Maintenance of all Work from the respective OAD periods up to Final Acceptance of the system as identified in 01 14 16 Coordination with City Operations. 5. Post -Acceptance: a. Correction period and warranty services after Final Acceptance. G. The foregoing description shall not be construed as a complete description of all work required. This summary of work provides an overall list of the key elements of work. The Contractor is responsible for determining exact required work for implementing the Work described in the Contract. 1.3 OTHER CONSTRUCTION CONTRACTS CTTY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 01 11 13 SUMMARY OF WORK Page 4 of 12 A. Other construction contracts have been or will be awarded by the City that are in direct relation to, in close proximity to, or border on the Work of this Contract. Work under these other contracts is briefly described as follows: 1. Control system replacement or upgrade, electrical systems replacement, or upgrade, and/or process mechanical upgrades at the following locations: a. Westside WTP Plate Settlers/Expansion. b. North Holly WTP Filter Rehabilitation. c. Eagle mountain WTP Clear Well 3 Rehabilitation. d. RHWTP Meter Replacement e. NHWTP Filter Modifications £ WSWTP & EMWTP Pump Station Enclosures g. Westside WTP Back-up Generators h. Back-up Generators at N/SHWTPs i. Substation Addition at EMWTP (& EMWTP RWPS) 1.4 WORK BY OTHERS A. Services Contracted by the City: The City will retain services of the following entities to perform the services indicated relative to the Project. Contractor shall coordinate and schedule the Work with, and cooperate with, the entities performing the following services for the City. 1. Internet and/or telephone Service: a. The City has, or will, retain the services of a local Network Service Provider to provide Internet service and/or cellular service to locations as shown and specified. The City will be responsible for acquiring the service(s) and monthly service fees for service(s). 1.5 WORK BY CITY A. The City has pre -purchased all SCADA software for this Work. B. Unless specifically noted, the City will procure and install all SCADA hardware (computers, servers, accessories, network equipment, Industrial Touchscreen Computers, PLCs, etc.) necessary for this Work. C. Unless specifically noted, the City will procure all software for this Work (PLC programming licenses, backup software, network software, HMI software, third -party SCADA software, etc.) necessary for this Work. D. The City's Water Information Technology Department (WIT) or an approved contractor by the City, will perform necessary services to provide: 1. Base setup for VM machines, the operating system and providing base hardening per City standards, IP addressing scheme for all systems as identified in the Contractor's SCADA system architecture design. 2. Base setup for the virtualized environments, inclusive of setting up VM management software, IP addressing scheme for all systems as identified in the Contractor's SCADA system architecture design. E. The City will perform the limited duties necessary to complete the Work including: CTTY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 01 11 13 SUMMARY OF WORK Page 5 of 12 1. Providing access to the Contractor to City's facilities to perform site visits, field assessments, and the coordinate the retrieval of running PLC/OIT/HMI applications. 2. Review Contractor's submittals and attend the required coordination workshops, review meetings, and witnessed field/site acceptance tests. 3. Review required submittals and 4. Performing shutdown work where required and where notification is provided as outlined in 01 14 16, Coordination with City Operations. 5. Operate all existing valves, gates, pumps, equipment, and appurtenances that will affect City's operation, unless otherwise specified or indicated. The Contractor is required to identify in advance all equipment necessitating City operation during the Work, as identified in Division 40 requirements. 6. Refer to Section 40 61 13 — General Provisions for additional detailed description of the Work by City. 1.6 SUMMARY OF WORK A. Refer to Section 01 14 16 — Coordination with City's Operations for requirements for sequencing and coordination with City's operations, including maintenance of facility operations during design and construction, and requirements for tie-ins and shutdowns. B. The following description shall not be construed as a complete description of the sequence and progress of work required and is provided as a guideline only. The Contractor is responsible for determining exact sequence and progress of work required and incorporate that into the CPM schedule prior to beginning work. C. Among other mobilization activities, achieve approved Schedule of Values, Submittal List, and CPM Schedule Rev.0. D. Familiarization and Preliminary Assessment 1. System Assessments: Field visits to all 5 WTPs to review the existing screens, alarming, data management, reporting, and to assess the existing condition of the Fort Worth Water Department (FWWD) SCADA system network. a. Key Deliverables: 1) System condition assessment technical reports, one (1) per WTP and one (1) for the overall system (Draft, and Final) b. Prerequisites: 1) Notice To Proceed (NTP). 2. Validate I/O Lists: Field visits to validate 1/0 Lists for Category A PLC systems and upload/confirm PLC programs. Refer to Attachment 6 — Existing WTP PLC Systems for details. a. Key Deliverables: 1) Validated 1/0 lists, one (1) per PLC system (Draft, and Final) b. Prerequisites: 1) System assessment site visit for respective WTP. As -Installed Functional Control Narratives (FCNs): Reverse engineer existing code for all Category A PLC systems and develop as -installed FCNs. a. Key Deliverables: 1) As -installed FCNs: One (1) per PLC system (Draft, and Final) CTTY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 01 11 13 SUMMARY OF WORK Page 6 of 12 b. Prerequisites: 2) Final validated I/O lists for respective WTP. E. Design (Milestone 1) 1. FCN Development: Develop unit process FCNs for Category A PLC systems in accordance with Attachment 1 — PLC and HMI Configuration Standards. The narratives will form the basis for PLC and HMI configuration work. a. Key Deliverables: 1) FCNs, One (1) per PLC system (Preliminary, Draft, and Final) b. Prerequisites: 1) Final As -installed FCN for the respective PLC system 2. SCADA System Architecture Design: Perform design of the new FWWD SCADA system architecture inclusive of identification of data interface/integration requirements and all required SCADA system hardware and software components in coordination and consultation with the City and WIT. a. Key Deliverables: 1) SCADA Architecture Design documents (30%, 60 %, 100%, and Final) b. Prerequisites: 1) Final system condition assessment technical reports for all WTPs and the overall system c. Milestone 1: The approved SCADA System Architecture Design will constitute achievement of Milestone 1 and on achievement of this, WIT will begin procurement of requisite project hardware and software. During the design phase, the City reserves the right to begin procurement earlier, especially for items known to be required. As these documents identify, at the 60% Architecture Design, most of the components should be known and where components can be locked in, the City may advance to procurement. However, the City reserves the right to start procurement of ALL hardware and software only after submission of the Final Approved SCADA System Architecture Design. F. Programming and Configuration 1. Configure WTP PLC, HMI, and OIT applications. a. Key Deliverables: 1) HMI graphics submittals, One (1) per WTP (Preliminary, Draft, and Final) 2) PLC configuration submittals, One (1) per WTP (Preliminary, Draft, and Final) 3) Alarm Lists, One (1) per WTP (Draft, and Final) b. Prerequisites: 1) For Category A PLC systems, respective Final FCNs 2) For Category B PLC systems, respective WTP Final system condition assessment technical report 2. Configure WTP Local Historian and Plant Operational Reports a. Key Deliverables: 1) Local WTP Historian and Plant Operational Report configuration submittals, One (1) per WTP (Preliminary, Draft, and Final) a. Prerequisites: 1) Final FCNs for Category A PLC systems in respective WTP(s) CTTY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 01 11 13 SUMMARY OF WORK Page 7 of 12 2) Final SCADA System Architecture Design Configure Centralized SCADA HMI, Historians, Alarm Notifications, Reports and Tablet Interfaces. a. Key Deliverables: 1) Centralized SCADA HMI application and alarm notification configuration submittals, One (1) per WTP, and one (1) for all WTPs (Preliminary, Draft, and Final) 2) Centralized SCADA Historians (Pass -Through Historian, Centralized SCADA Local Historian, Central SCADA Historian), and tablet interface configuration submittals, One (1) per WTP, and one (1) for all WTPs (Preliminary, Draft, and Final) 3) Centralized SCADA Business and Central Operational reports configuration submittals (Preliminary, Draft, and Final) b. Prerequisites: 1) Final FCNs for Category A PLC systems in respective WTP(s) 2) Final SCADA System Architecture Design G. Factory Acceptance Testing 1. Unwitnessed Factory Testing (UFT) of WTPs: Perform UFT of WTP PLCs, OITs, local SCADA HMI, Historian, and plant operational reports as well as integration with the Centralized SCADA system to the extent possible, including but not limited to Centralized SCADA HMI functionality, alarm notifications, data flow and replication from Local to Central Historian, and tablet interface. Testing shall be performed on the SCADA system computer/network equipment furnished by the City for the project either on site or through remote access from the Contractor's facility. a. Key Deliverables: 1) UFT Plans and Reports, one (1) per WTP b. Prerequisites: 1) Installation and configuration of DMZ, Centralized SCADA, and respective WTP's SCADA system computer/network hardware and associated software (by the City) 2) Installation and configuration of Ignition SCADA software and all third -party SCADA software in coordination with the City. 3) Remote access to FWWD SCADA from Contractor's facility, if required (by the City) 4) Final PLC and HMI application configuration submittals for the respective WTP 5) Final Alarm Lists for the respective WTP 6) Final Local WTP Historian and Plant Operational Report configuration submittals for the respective WTP 7) Final Centralized SCADA HMI application and alarm notification configuration submittals for the respective WTP 8) Final Centralized SCADA Historians and tablet interface configuration submittals for the respective WTP 2. Witnessed Factory Testing (WFT) of WTPs. a. Key Deliverables: 1) WFT Plans and Reports, one (1) per WTP b. Prerequisites: CTTY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 01 11 13 SUMMARY OF WORK Page 8 of 12 1) UFT Report for the respective WTP 3. Unwitnessed Factory Testing (UFT) of Centralized SCADA: Perform UFT of the Centralized SCADA system to the extent possible, including but not limited to Centralized SCADA HMI functionality, alarm notifications, data flow to Central Historian, Central Operational Reports, and tablet interface for all WTPs. Testing shall be performed on the SCADA system computer/network equipment furnished by the City for the project either on site or through remote access from the Contractor's facility. a. Key Deliverables: 1) Centralized SCADA UFT Plan and Report b. Prerequisites: 1) Installation and configuration of DMZ, Centralized SCADA, and all WTPs' SCADA system computer/network hardware and associated software (by the City) 2) Installation and configuration of Ignition SCADA software and all third -party SCADA software in coordination with the City. 3) Remote access to FWWD SCADA from Contractor's facility, if required (by the City) 4) WFT Reports for all WTPs 5) Final Centralized SCADA HMI application and alarm notification configuration submittals for the complete system (all WTPs) 6) Final Centralized SCADA Historians and tablet interface configuration submittals for the complete system (all WTPs) 4. Witnessed Factory Testing (WFT) of Centralized SCADA. a. Key Deliverables: 1) Centralized SCADA WFT Report b. Prerequisites: 2) Centralized SCADA UFT Report H. Cutover, Field Testing, and Start -Up of First WTP (Milestone 2) 1. Cutover of first WTP: Plan and perform cutover of one plant PLC system at a time and integrate into the Centralized SCADA. New and existing WTP SCADA systems shall be operated in parallel through cutover of the last PLC in each plant. As each PLC system is cut over from the existing to the new SCADA system, the associated data will be activated on the new plant HMI, local Historian, and local operational reports. The associated HMI screens, alarms notifications, and data Historians shall also be tested and activated on the Centralized SCADA system one PLC system at a time. After a given PLC system is cutover to the new SCADA system, at least 72 hours of successful operation is required before the next cutover can start. a. Key Deliverables: 1) Cutover Plan for the first WTP (Preliminary, Draft, and Final) 2) Field Test/Startup Plan and Report, One (1) per WTP PLC system 3) Operational Availability Demonstration (OAD) Period Letter for the first WTP b. Prerequisites: 1) WFT Report for the first WTP 2. OAD of first WTP: Once the last PLC system at the plant has been successfully cut over to the new SCADA system and integrated into the Centralized SCADA, CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 01 11 13 SUMMARY OF WORK Page 9of12 the OAD for the plant shall commence. The OAD will require 30 consecutive days of normal plant operation without any significant failures and/or interruptions to receive approval otherwise the process shall restart. Upon successful completion of the plant's OAD, the existing WTP SCADA system shall be decommissioned. a. Key Deliverables: 1) Signed OAD Period Letter and Malfunction/Report Forms for the first WTP 2) As -Built Alarm Database for the first WTP b. Prerequisites: 1) Field Test/Startup Reports for all PLC systems in the first WTP c. Milestone 2: The approved OAD for the first WTP will constitute achievement of Milestone 2 and on achievement of this, the cutover of the second WTP can start. I. Cutover, Field Testing, and Start -Up of Remaining WTPs (Milestone 3) 1. Cutover of remaining WTPs: Plan and perform cutover of one respective PLC system for each WTP at a time and integrate into the Centralized SCADA. During each plant cutover, the new and existing WTP SCADA systems shall be operated in parallel through cutover of the last respective PLC. At least 72 hours of successful operation is required between all PLC cutovers. a. Key Deliverables: 1) Cutover Plans, One (1) per remaining WTP (Preliminary, Draft, and Final) 2) Field Test/Startup Plans and Reports, One (1) per PLC system in respective WTP 3) OAD Period Letters, One (1) per remaining WTP a. Prerequisites: 1) WFT Report for the respective WTP 2. OAD of remaining WTPs: Once the last PLC system at each plant has been successfully cut over to the new SCADA system and integrated into the Centralized SCADA, the OAD for that plant shall commence. Each plant OAD will require 30 consecutive days of normal operation without any significant failures and/or interruptions for approval. Upon successful completion of each plant OAD, the respective existing WTP SCADA system shall be decommissioned. a. Key Deliverables: 1) Signed OAD Period Letters and Malfunction/Report Forms, One (1) per remaining WTP 2) As -Built Alarm Databases, One (1) per remaining WTP b. Prerequisites: 1) Field Test/Startup Reports for all PLC systems in the respective WTP c. Milestone 3: The approved OAD for the last WTP will constitute achievement of Milestone 3 and on achievement of this, the Final Acceptance for WTPs will be awarded. I Cutover, Field Testing, and Start -Up of Centralized SCADA 1. Cutover of Centralized SCADA: Plan, implement, and test the Centralized SCADA system in its entirety with all WTPs connected. Test and validate all new business and Central Operational reports and tablet interfaces using SCADA data CTTY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 01 11 13 SUMMARY OF WORK Page 10 of 12 from all 5 upgraded WTPs and the existing data warehouse in coordination with the City and Water IT. a. Key Deliverables: 1) Centralized SCADA Cutover Plan (Preliminary, Draft, and Final) 2) Centralized SCADA Field Test/Startup Plan and Report 3) Centralized SCADA OAD Period Letter b. Prerequisites: 1) Signed OAD Period Letters for all WTPs 2. OAD of Centralized SCADA: Once all new business/central reports have been successfully validated, the OAD for the plant shall commence. The Centralized SCADA system OAD will require 30 consecutive days of normal operation without any significant failures to receive approval otherwise the process shall restart. The approved OAD for Centralized SCADA will constitute achievement of the Final Acceptance for the project. a. Key Deliverables: 1) Signed OAD Period Letter and Malfunction/Report Form for Centralized SCADA 2) As -Built Alarm Databases, One (1) for the complete system (all WTPs) b. Prerequisites: 1) Centralized SCADA Field Test/Startup Report K. Training: a. Provide training as identified in 40 6126, SCADA System Training. L. Maintenance: a. Maintenance of all Work from the respective OAD periods up to Final Acceptance of the system as identified in 01 14 16 Coordination with City Operations. M. Post -Acceptance: a. Correction period and warranty services after Final Acceptance. 1.7 CONTRACTOR'S USE OF SITE A. Contractor shall share use of the Site with other contractors and others specified in Article 1.3 of this Section and others as specified in Article 1.4 of this Section. B. Move stored materials and equipment that interfere with operations of City, other contractors, and others performing work for City. C. Limits on Contractor's use of the Site are: 1. As indicated in Section 01 14 19 — Use of Site. 2. Do not use the Site for operations other than those required for the Project. 1.8 PARTIAL UTILIZATION BY CITY A. Prior to Substantial Completion of the entire Work under the Contract, substantially complete the Work by completing each associated Operational Availability Demonstration period. Upon completion of testing, startup, acceptance tests, and CTTY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 01 11 13 SUMMARY OF WORK Page 11 of 12 Operational Availability Demonstration periods, the City will assume partial utilization of the work which has successfully passed the Operational Availability Demonstration period. PART 2 — PRODUCTS (NOT USED) PART 3 — EXECUTION (NOT USED) ++END OF SECTION++ CTTY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 01 11 13 SUMMARY OF WORK Page 12 of 12 ++THIS PAGE INTENTIONALLY LEFT BLANK++ CTTY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 01 1416 COORDINATION WITH CITY'S OPERATIONS Page 1 of 6 SECTION 01 14 16 COORDINATION WITH CITY'S OPERATIONS PART 1 — GENERAL 1.1 DESCRIPTION A. Scope: 1. This section describes the requirements for tie-ins and developing shutdown strategies, protocols, and advance notification necessary for completing the work without impacting City's operations except as allowed in this Section. Contractor shall develop these strategies, protocols, and advance notification requirements during the design phase and submit them to the City for approval prior to start of any construction work. 2. This section also described specific maintenance requirements the Contractor shall meet in coordination with City operations to keep upgraded systems running from respective Operational Availability Demonstrations through Final Acceptance and the start of all Warranty periods. 2. Contractor shall provide all labor, materials, equipment, tools, and incidentals shown, specified, and required to complete the Work without impact on City's operations except as allowed in this Section. B. Coordination: 1. Review and coordinate construction procedures, tie-ins, shutdowns required, and their durations with the City through coordination workshops during the design phase. 2. Notify other contractors in advance of Work requiring coordination with City's operations, to provide other contractors sufficient time for work included in their contracts that will be performed with or before Work specified in this Section. C. Related Sections: 1. Section 01 11 13 — Summary of Work. 2. Section 0133 00 — Submittal Procedures. 3. Section 40 6123 — SCADA System Startup and Field Testing 4. Section 40 68 63 — SCADA System Programming and Configuration D. Except for shutdowns approved through the process described in article 1.1 A and B of this section, perform the Work such that City's facilities remain in continuous satisfactory operation during the Project. Schedule and conduct the Work such that the Work does not: impede City's production or processes, create potential hazards to operating equipment and personnel, reduce the quality of the facility's products, negatively affect the potable water conveyance system, cause odors or other nuisances, or affect the public health, safety, and convenience. E. Work not specifically covered in this Section or in referenced Sections may, in general, be completed, within the Contract Times, at any time during regular working hours in accordance with the Contract Documents, subject to the requirements in this Section. CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 01 1416 COORDINATION WITH CITY'S OPERATIONS Page 2 of 6 F. As a substitute to the procedures provided in this Section, Contractor may propose other procedures or additional steps that can eliminate or mitigate a constraint without additional cost to City or providing a reduction in contract cost (price) by subsequent change order. The City shall consider the proposal provided the proposed procedures or additional steps do not present hazards to the public, personnel, structures, and equipment; that such procedures do not adversely affect City's ability to comply with Laws and Regulations, permits, and operating requirements; do not reduce the quality of the facility's products; do not negatively affect the potable water conveyance system; and that the requirements of the Contract Documents not modified by the City with issuance of a Field Order or approval of a Change Order are fulfilled. Failure of the City to accept a proposal shall not entitle the Contractor to additional compensation or an extension of contract time. G. As part of the condition assessment, identify and develop a list of tie-ins and shutdowns required, along with the duration, and include the list in the condition assessment report. During design phase, coordinate and finalize the tie-ins and shutdowns with the City and include the identified tie-ins and shutdowns into the project schedule. When possible, combine multiple tie-ins into a single shutdown to reduce impacts on City's operations and processes. H. Operation of Existing Systems and Equipment during the Work: 1. Do not shut off or disconnect existing operating systems or equipment, unless approved by the City in writing. 2. Operation of existing systems and equipment will be by City unless otherwise specified or indicated. 3. During shutdown, where necessary, provide temporary power to field instruments and other field devices that are powered from existing control panel(s) and/or PLC panel(s). When necessary, keep the existing or new control panel(s), and PLC panel(s) powered during construction, so that field instruments or other components powered by these panels will remain in service. 1.2 SUBMITTALS A. Action Submittals: Submit the following: With the final design, prepare a preliminary tie- in and shutdown information submittal to the City for approval. The submittal shall include details of planned control panel shutdowns, network partial or full shutdowns, tie-ins, shutdowns, shutdown durations, and work to be complete and systems to be tested and ready prior to requesting a shutdown. B. Prior to the start of any field activities necessitating shutdowns or interruption of any unit process operations, coordinate with the City scheduled work and duration of work and steps necessary to maintain City's operations during the activity, and resume City operations at the conclusion of the activity. C. Unless otherwise approved, notify the City in writing not less than 30 days prior to any proposed shutdown start date. This includes shutdown of power to Control Panels and/or SCADA computer or network equipment, for purposes of upload/download of software, or other adjustments. Do not start shutdown until obtaining City's acceptance of shutdown planning submittal. CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 01 1416 COORDINATION WITH CITY's OPERATIONS Page 3 of 6 1.3 GENERAL CONSTRAINTS A. Provided in this Section are the constraints applicable to City's equipment, systems, wiring and conduits that are to be taken out of service temporarily for the Work. New materials, equipment, wiring, conduits, and systems may be used and operated by City after the specified field quality controls and testing are successfully completed. B. The following constraints apply to coordination with City's operations: 1. Operational Access: City's personnel shall have access to equipment and areas of the facility that remain in operation. 2. Temporary Partitions and Enclosures: Provide temporary partitions and enclosures, where necessary, to maintain dust -free, heated, and ventilated spaces in areas of the facility that are adjacent to the Work and that must be kept operational. 3. Schedule and perform equipment and system cutover and start-ups from Monday through Thursday. Equipment and systems shall not be cutover or placed into operation on Friday, Saturday, and Sunday without prior approval of City, unless specifically indicated otherwise in the Contract Documents. 4. Contractor shall obtain a "Ready to Proceed" notice issued by the City prior to the shutdown of any equipment on site. 5. If any accidental spillage occurs during checkout and startup, it shall be brought to City's attention immediately, both verbally and in writing, and reported in accordance with Laws and Regulations. Contractor shall wash down spillage to floor drains or sumps or other appropriate location and flush the system to prevent clogging and odors. If spillage is not suitable for discharge to the drainage system, such as chemical spills, as determined by City, Contractor shall remove spillage by other method acceptable to the City. 1.4 CONSTRAINTS TO THE SEQUENCE AND SCHEDULING OF WORK A. The Contractor shall coordinate with the City and develop a detailed construction sequence and staging of work and incorporate this into the approved CPM Schedule. B. Unless otherwise approved in writing by the City, the SCADA System cutover from the existing SCADA system to the new SCADA system at each WTP, excluding the requisite Operational Availability Demonstration (OAD) period, shall not last more than one - hundred -eighty (180) calendar days to minimize the time operators are required to operate two SCADA systems (existing and new) to operate the facility. While the Contractor may request the period to be extended, compliance with the 180-day limitation shall be required without additional compensation if so directed by City's response. C. SCADA system cutover can only occur one plant at a time. A plant must be fully cutover with a successful OAD prior to moving on to the next plant. D. Unless otherwise approved in writing by the City, after a given PLC (or concurrent PLCs) Qis cutover to the new SCADA system, the Contractor shall not proceed to the next PLC (or s concurrent PLCs) until the impacted unit processes, data collection, alarm notifications, and reports have operated successfully for at least 72 hours, and the City confirms authorization to proceed. CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 01 1416 COORDINATION WITH CITY'S OPERATIONS Page 4 of 6 E. For each plant, Contractor shall coordinate with the City to setup, install City -furnished SCADA software, and test each new SCADA system headend hardware and software, and network functionality, prior to start of any cutover Work at that Water Treatment Plant (WTP). Testing should be performed to ensure readiness of all hardware and software to commence PLC panel and SCADA system cutover activities. a. Perform testing and achieve readiness to begin cutovers as outlined in Division 40. F. During the design phase but at least 60 days prior to beginning a specific WTP's SCADA cutover, Contractor shall document the data points specific to that panel that will no longer be collected from the existing historian and shall now be retrieved from the new SCADA historian system. Coordinate remapping of historical SCADA data with City's Water Department IT (Water IT) and City Project Manager. G. If necessary to achieve the contract schedule, certain phases or stages of the Work may require the Contractor to provide multiple shifts of work during hours outside of regular working hours, up to 24 hours. H. The Contractor may propose to accelerate from a later stage to an earlier stage if City's operations are not adversely affected by proposed sequence change, with City's acceptance. The City's withholding approval to accelerate work shall not be considered a change of conditions or otherwise entitle the Contractor to a change in the Contract Amount or Contract Time. I . SCADA cutover and associated field-testing activities at any WTP shall not be scheduled earlier than one -hundred -eighty (180) days after achievement of Milestone 1, approval of Final SCADA System Architecture Design and component specifications. This is to allow for procurement and install of network hardware by the City. 1.5 SHUTDOWNS 0 1. Terminology: A "shutdown" is an interruption or clear disruption to water production Qor treatment as a result of any part of the City's facilitybe it process or electrical equipment, or systems —being temporarily suspended or taken out of service to 2. Work that may interrupt normal operations shall be accomplished at times convenient to City unless otherwise indicated in the Contract Documents. 3. Furnish at the Site, in close proximity to the shutdown and tie-in work areas, tools, materials, equipment, spare parts, both temporary and permanent, necessary to successfully perform the shutdown. 4. If Contractor's actions cause an unscheduled interruption of City's operations, immediately re-establish satisfactory operation for City. 5. Unscheduled shutdowns or interruptions of continued safe and satisfactory operation of City's facilities that result in fines or penalties by authorities having jurisdiction shall be paid solely by Contractor if, in City's opinion, Contractor did not comply with requirements of the Contract Documents, or was negligent in the Work, or did not exercise proper precautions in performing the Work and complying with applicable permits, Laws, and Regulations. CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 01 1416 COORDINATION WITH CITY'S OPERATIONS Page 5 of 6 6. Shutdowns shall be in accordance with Article 1.4 of this Section. Work requiring service interruptions for tie-ins shall be performed during scheduled shutdowns. 7. Temporary, short-term shutdowns of smaller conduits (including piping and ducting), equipment, and systems to perform the Work are not included in Article 1.4 of this Section. Coordinate requirements for such shutdowns with City. Where necessary, obtain City's interpretation or clarification before proceeding. B. Shutdowns of Electrical Systems: 1. Comply with Laws and Regulations, including the National Electric Code. 2. Contractor shall request at least 30 days in advance any required lock out and tag out of circuit breakers and/or switches operated by City and shall confirm with City that affected cables and wires are de -energized to ground potential before shutdown Work is started. C. SCADA System Shutdown Limitations: 1. Scheduled shutdowns may be delayed by the City due to operational or environmental limitations that were unknown at time the shutdown was approved, such as ongoing emergency repairs, unscheduled maintenance, or periods of freezing weather. 2. While the Contractor may request relief, compliance with restrictions shall be provided at no additional cost to the City regardless of the City's response to such requests. 3. Unless otherwise approved in writing by the City: a. Treatment plant shutdowns are allowed during the low flow period only. b. Low Flow Period: November 1 — April 14: i. North Holly WTP may be shut down if South Holly WTP is online and fully operational. ii. If North Holly WTP and South Holly WTP are online one other WTP may be shut down. iii. Provide notice of planned work during this period at least 3 months in advance and coordinate with the City specific details as the actual days of work approach. 1.6 MAINTENANCE OF SYSTEMS FROM OPERATIONAL AVAILABILITY DEMONSTRATIONS THROUGH PROJECT FINAL ACCEPTANCE A. General: 1. The Contractor shall maintain systems operational throughout construction and to Final Acceptance, which coincides with the start of Warranty obligations. 2. The maintenance period for each component, system or software shall start with successful completion of the respective Operational Availability Demonstration and concludes with project Final Acceptance. B. The following constitutes the scope of maintenance work: 1. During the Work, the Contractor shall: a. Coordinate with the City to recommend spare parts that should be on hand in an accessible location. b. Network/SCADA Hardware: i. Monitor security bulletins and advise the City if corrective action needs to be taken to address a security vulnerability. BIOS upgrades and/or patches to address security vulnerabilities or possible exploits shall be discussed, and on approval, installed by Water IT immediately. CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 01 1416 COORDINATION WITH CITY's OPERATIONS Page 6 of 6 ii. Communicate to the City the requirement for emergency replacement of failed or improperly acting hardware for the time period between the respective OADs through Final Acceptance. c. Network/SCADA Software: i. For all SCADA software related to PLCs, HMI and data interface, the City shall provide the minor versions of software and the Contractor shall review and upgrade software as part of the Work. This shall include all 3' party software procured by the City. 1. Major version upgrades will not be part of the Work, unless negotiated by the City. 2. The City will upgrade Network device software (switches, firewalls). 3. The City will coordinate Computer operating system upgrades with the Contractor, and the City will perform the upgrade. ii. Monitor security bulletins and recommend corrective actions to be taken by the City to address any security vulnerabilities. Patches to address security vulnerabilities or possible exploits shall be discussed and coordinated with the City prior to the City installing. d. PLC hardware: i. Coordinate the installation of any necessary firmware upgrades released by the manufacturer specific to the Category A controllers. For details, refer to Attachment 6, Existing WTP PLC Systems and Section 40 68 63 — SCADA System Programming and Configuration. ii. Assume the need to make upgrades to firmware at least once during the project lifecycle. iii. Communicate to the City the requirement for emergency replacement of failed or improperly acting hardware components for the time period between the respective OADs and Final Acceptance. e. PLC software: i. Coordinate with the City upgrade of software versions prior to performing any maintenance. ii. Assume the need to upgrade software versions/software at least once during the lifetime of the project. C. Planned and Emergency Maintenance: 1. Provide at least 1-week advance notification of any routine or plannable maintenance activity. 2. Provide emergency maintenance of PLC and SCADA software applications configured by the Contractor within 4 hours of notification. 3. Provide immediate notification of hardware failures or needs. The City will furnish and install replacement hardware. PART 2 — PRODUCTS (NOT USED) PART 3 — EXECUTION (NOT USED) + + END OF SECTION + + CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 SECTION 01 14 19 USE OF SITE PART 1 — GENERAL 1.1 DESCRIPTION 01 1419 USE OF SITE Pagel of 2 A. Scope: 1. This Section includes requirements for use of the Site during the Project, and includes requirements for use of existing facilities, as applicable. 2. Contractor shall provide all labor, materials, equipment, tools, and incidentals shown, specified, and required to comply with restrictions on Contractor's use of the Site and other areas. 1.2 USE OF PREMISES A. Limit use of premises at the Site to work areas discussed and identified in workshops during the design phase. Do not disturb portions of the Site beyond areas of the Work. Storage of equipment and materials at the sites shall be coordinated with operations and maintenance supervisors at each site and shall receive permission before storage of any equipment or material at a site. 1. Water Treatment Plants (WTP): a. Designated work and staging areas will be allocated by City during the design phase. B. An onsite trailer is not required for this project. The Contractor may provide a trailer in coordination with the City and at a location acceptable to the City, to facilitate transport/staging or personnel work, but at no additional cost to the City. C. Use of Existing Buildings and Structures: Obtain City's written permission for each proposed use of existing buildings and structures. D. Site Access: 1. Contractor's project team assigned for this project shall have a background check completed and cleared by a security company selected by the Contractor that is acceptable to and approved by the City. 2. City has limited number of keys to some of the customer metering sites and therefore requires City staff to accompany the Contractor's workers and provide access to these sites. 3. Access: Access to any site must be coordinated (in advance) in conjunction with monthly required in Section 0131 19.23 — Progress Meetings. a. The Contractor shall present and coordinate a list of site access that is required in the calendar month following each monthly Progress Meeting. The first access requiring coordination on the list would occur on the 1 st day of the next calendar month, the last access would occur on the final day of the next calendar month. b. Except as noted above where limited keys are available, site access shall occur without escort by City staff accompanying the Contractors worker. The CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 01 1419 USE OF SITE Page 2 of 2 Contractor's workers are subjected to clearance as noted in Article 1.2 D. 1. Above. Key or alternate means of access will be coordinated. c. If it is necessary to modify the access list the Contractor shall notify the City in writing a minimum of seven days in advance of any needed access added. If acceptable to the City, the site or sites shall be added to the access list and key, or alternate means of access coordinated. d. For sites where access has not been coordinated as noted above, the Contractor shall request access at least 24 hours advance. Denial of access to sites not on the pre -coordinated list or approved by the City at least seven days in advance, shall not entitle the Contractor to additional Contract Time or Cost. 4. Security: Access to any site must be coordinated (in advance). Security of Site must be maintained to include locking site up during non -work periods (nights, weekends, etc.), keeping gate closed or manning gate during construction. The City is not responsible for security of contractor's equipment & materials. 5. Sanitation: Restrooms/Bathrooms on -site can be used by Contractor staff. 6. Plant Site: Alert Notification SOPS may require Contractor personnel to receive training. E. Working Hour restrictions are defined in the General Conditions as modified by the Supplementary Conditions. Restrictions noted include: 1. Regular Working Hours definition. 2. Weekend Working Hours definition, including the applicability of Weekend Working Hours to legal holidays and a list of observed annual holidays. 3. Requirement to receive written in approval for performance of Work beyond Regular Working Hours including applicable deadlines for City receipt of requests. F. Prior to entering Site, Contractor's personnel, including Subcontractors and Suppliers, shall complete City's site -specific safety training for water treatment plants. G. Promptly repair damage to premises caused by construction vehicles movements or other equipment operations. Upon completion of the Work, restore premises to specified condition; if condition is not specified, restore to pre -construction condition. PART 2 — PRODUCTS (NOT USED) PART 3 — EXECUTION (NOT USED) + + END OF SECTION + + CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 f.1ONI[6)0[11W4041[d MEASUREMENT AND PAYMENT PART 1 — GENERAL 1.1 DESCRIPTION 0122 13 MEASUREMENT AND PAYMENT Page 1 of 4 A. Scope: Items listed starting in Article 1.4 of this Section refer to further breakdown of the pay items listed in the Section 00 42 10 — Proposal Exhibit A and constitute all pay items for completing the Work. B. No direct or separate payment will be made for any identified requirements in the Contract, including but not limited to site assessments, workshops, meetings, coordination efforts, design, programming, testing and startup, safety, security, submittals and record drawings, coordination with City's operations, bonds, insurance, or other such. Such items shall be subsidiary to the appropriate lump sum item. C. Compensation for all services, items, materials, and equipment shall be included in prices stipulated for pay items listed in this Section and included in the Pricing Form. D. Each lump sum shall include an amount considered by Contractor to be adequate to cover Contractor's overhead and profit for each separately identified item. 1.2 RELATED PROVISIONS A. Payments to Contractor: Refer to the General Conditions. B. Changes in Contract Price: Refer to Section 01 26 00 — Contract Modification Procedures. C. Schedule of Values: Refer to Section 0129 73 — Schedule of Values. 1.3 MEASUREMENT — CONTRACT A. Measurement shall comply with payment limitations requirements noted in Section 0129 73, Schedule of Values. CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 0122 13 MEASUREMENT AND PAYMENT Page 2 of 4 A. Item No. 1 Mobilization, Limited to 2.0 Percent of the Total Amount (Items 2-9 of the Proposal) — The lump sum Proposal Item shall be full compensation for work required to mobilize. Payment for mobilization shall be as a percentage of the lump sum in accordance with Section 0129 73 — Schedule of Values. B. Item No. 2 Familiarization and Preliminary Assessment - The lump sum Proposal Item shall be full compensation for the familiarization and assessment services described in the Contract Documents. The items include but are not limited to review of available documents, conducting site visits, performing condition assessments, 1/0 Validations, conducting meetings, and providing As -Installed Functional Control Narratives (FCNs) and other noted documents and deliverables. Payment shall be as a percentage of the lump sum completed by the Contractor as determined by the Schedule of Values accepted by the City. The assessment process is incorporated for the sole purpose of the Contractor systematically assembling the required information required to complete the Work. In accordance with Article 6.5 of the Proposal, no adjustment in Contract Price shall be provided. This work item includes all work listed in Section 40 61 13 — General Provisions, Article 1.3 Familiarization and Preliminary Assessment, inclusive of familiarization and preliminary assessment of the following key areas of work: 1. Water Treatment Plants (WTPs) SCADA PLC, OIT and HMI upgrades. 2. Centralized SCADA, including the Test Bench, data interface, data migration, Remote Access Tablets and Tablet Interface, alarm notification, historian database, all Reports. 3. Familiarization and Preliminary Assessment Work not included in other bid items. C. Item No. 3 Design - The lump sum Proposal Item for Design shall be full compensation for the Design services described in the Contract Documents. The items include but are not limited to preparation of Functional Control Narratives (FCNs); design of the SCADA System Architecture inclusive of identification of data interface/integration requirements and all required SCADA system hardware and software components; identification of design criteria for HMI/PLC/OIT software configuration requirements; schedule development; conducting workshops and preparing of Design documents and deliverables. The items include but is not limited to providing all technical services needed to develop a comprehensive set of SCADA System Architecture design documents sealed by a Professional Engineer licensed in the State of Texas. Payment shall be as a percentage of the lump sum completed by the Contractor as determined by the Schedule of Values accepted by the City. The assessment process is incorporated for the sole purpose of the Contractor systematically assembling the required information required to complete the Work. This work item includes all work listed in Section 40 61 13 — General Provisions, Article 1.4 Design, inclusive of design of the following key areas of work: 1. Water Treatment Plants (WTPs) unit process Functional Control Narratives for all PLC systems at all 5 WTPs. 2. Centralized SCADA, including the test bench, data interface, data migration, Remote Access Tablets and Tablet Interface, alarm notification, historian database, all Reports. 3. Design Work not included in other bid items. D. Item No. 4 Eagle Mountain WTP Configuration, Cutover and Startup — The lump sum Proposal Item for Configuration, Cutover and Startup shall be full compensation for all CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 0122 13 MEASUREMENT AND PAYMENT Page 3 of 4 materials, labor, and other costs associated with the site to implement the HMI, historian and reporting upgrades and successful completion of the OAD for SCADA systems for the Eagle Mountain WTP, in accordance with the Contract Documents and as detailed by the Contractor's Design. Payment shall be as a percentage of the lump sum completed by the Contractor as determined by the Schedule of Values accepted by the City. E. Item No. 5 South Holly WTP Configuration, Cutover and Startup — The lump sum Proposal Item for Configuration, Cutover and Startup shall be full compensation for all materials, labor, and other costs associated with the site to implement the HMI, PLC, 01T, historian and reporting upgrades and successful completion of the OAD for SCADA systems for the South Holly WTP, in accordance with the Contract Documents and as detailed by the Contractor's Design. Payment shall be as a percentage of the lump sum completed by the Contractor as determined by the Schedule of Values accepted by the City. F. Item No. 6 North Holly WTP Configuration, Cutover and Startup — The lump sum Proposal Item for Configuration, Cutover and Startup shall be full compensation for all materials, labor, and other costs associated with the site to implement the HMI, PLC, 01T, historian and reporting upgrades and successful completion of the OAD for SCADA systems for the North Holly WTP, in accordance with the Contract Documents and as detailed by the Contractor's Design. Payment shall be as a percentage of the lump sum completed by the Contractor as determined by the Schedule of Values accepted by the City. G. Item No. 7 Westside WTP Configuration, Cutover and Startup — The lump sum Proposal Item for Configuration, Cutover and Startup shall be full compensation for all materials, labor, and other costs associated with the site to implement the HMI, PLC, 01T, historian and reporting upgrades and successful completion of the OAD for SCADA systems for the Westside WTP, in accordance with the Contract Documents and as detailed by the Contractor's Design. Payment shall be as a percentage of the lump sum completed by the Contractor as determined by the Schedule of Values accepted by the City. H. Item No. 8 Rolling Hills Configuration, Cutover and Startup — The lump sum Proposal Item for Configuration, Cutover and Startup shall be full compensation for all materials, labor, and other costs associated with the site to implement the HMI, PLC, 01T, historian and reporting upgrades and successful completion of the OAD for SCADA systems for the Rolling Hills WTP, in accordance with the Contract Documents and as detailed by the Contractor's Design. Payment shall be as a percentage of the lump sum completed by the Contractor as determined by the Schedule of Values accepted by the City. I. Item No. 9 Centralized SCADA Configuration, Cutover and Startup - The lump sum Proposal Item for all Work associated with Centralized SCADA, Tablet Interface, Remote Alarm Notification, Test Bench, Data Warehouse Interface, Reporting Configuration, Cutover, Implementation and Maintenance to Final Acceptance Services. This item shall be full compensation for all materials, labor, and other costs associated with completion of such Work in accordance with the Contract Documents and as detailed by the Contractor's Design. This work item includes configuration, cutover and implementation of the following areas of work: 1. Centralized SCADA, including Remote Access Tablets and Tablet Interface, historian database, all Dashboards and Reports. 2. Data and communications infrastructure/network incorporating the WTPs, Centralized SCADA and Data Warehouse System, including all databases, pass -through SQL CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 0122 13 MEASUREMENT AND PAYMENT Page 4 of 4 database, test bench, custom database interfaces, network infrastructure, DMZ and network hardware/software, existing data migration into the new system, remote alarm monitoring and notification. 3. Any other Configuration, Cutover, or Startup work not included in other bid items. Item No. 10 Allowance for Additional Familiarization, Preliminary Assessment and Design Services — The lump sum Proposal Item is a contingency allowance for additional Familiarization, Preliminary Assessment and Design services not required by the Contract Documents at the time the Proposal is submitted. Such additional Work shall be requested by the City and incorporated by Field Order following submittal of the Contractor's cost for the Work added and subsequent approval by the City. K. Item No. 11 Allowance for Additional Hardware or Software — The lump sum Proposal Item is a contingency allowance for procurement of additional third -party SCADA communication software and any other SCADA software not designated for purchase by the City and not otherwise designated in the Contract Documents for the Contractor to purchase, yet required for the functionality of the SCADA system as outlined in the Contract Documents. This contingency allowance may also be used for the procurement of any hardware or software assets not stipulated by the Contract Documents at the time the Proposal is submitted. Such additional Work shall be requested by the City and incorporated by Field Order following submittal of the Contractor's cost for the Work added and subsequent approval by the City. L. Item No. 12 Allowance for Additional Configuration, Cutover and Startup Services— The lump sum Proposal Item is a contingency allowance for completing additional Configuration, Cutover and Startup Work not required by the Contract Documents at the time the Proposal is submitted. Such additional Work shall be requested by the City and incorporated by Field Order following submittal of the Contractor's cost for the Work added and subsequent approval by the City. M. Item No. 13 Allowance for Additional Data Warehouse / Data Interface Programming Services— The lump sum Proposal Item is a contingency allowance for completing additional Programming work related to the Data Warehouse or Data Interface not required by the Contract Documents at the time the Proposal is submitted. Such additional Work shall be requested by the City and incorporated by Field Order following submittal of the Contractor's cost for the Work added and subsequent approval by the City. PART 2 — PRODUCTS (NOT USED) PART 3 — EXECUTION (NOT USED) + + END OF SECTION + + CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 01 26 00 CONTRACT MODIFICATION PROCEDURES Page 1 of 6 SECTION 01 26 00 CONTRACT MODIFICATION PROCEDURES PART 1 — GENERAL 1.1 DESCRIPTION A. Scope: 1. This Section includes: a. Requests for interpretation. b. Clarification notices. C. Minor changes in the Work and Field Orders. d. Work Change Directives. e. Proposal Requests. f. Change Proposals. g. Change Orders. B. Submit Contract modification documents to City in accordance with Section 01 31 26 — Electronic Communication Protocols. 1.2 REQUESTS FOR INTERPRETATION A. General. 1. Submit written requests for interpretation to the City. 2. Submit request for interpretation to obtain clarification or interpretation of the Contract Documents. Report conflicts, errors, ambiguities, and discrepancies in the Contract Documents using requests for interpretation. 3. Do not submit request for interpretation when other form of communication is appropriate, such as submittals, requests for substitutions or "or equals", notices, ordinary correspondence, or other form of communication. Improperly prepared or inappropriate requests for interpretation will be returned without response or action. 4. Do not submit request for interpretation or clarification when: a. Answer may be obtained by observations at the Site. b. Required information is clearly indicated in the Contract Documents. C. Required information is included in industry standards referenced in the Contract Documents or Supplier's instructions that are consistent with the Contract Documents. d. Required information can be reasonably inferred from any of foregoing. 5. Contractor shall have sole financial responsibility for requests for interpretations or clarifications that are submitted late, out of sequence, or that are unnecessary. B. Procedure. 1. Transmit requests for interpretation in accordance with Section 01 3126 — Electronic Communication Protocols, and requirements of this Section. Include with each request for interpretation a separate letter of transmittal. 2. City will provide timely review of requests for interpretation. Allow sufficient time for review and response. CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 01 26 00 CONTRACT MODIFICATION PROCEDURES Page 2 of 6 3. City will maintain log of requests for interpretation. Copy of log will be provided upon request. 4. City's response to requests for interpretation will be transmitted in accordance with Section 01 3126 — Electronic Communication Protocols, and requirements of this Section. Each response to a request for interpretation will include a separate letter of transmittal. 5. City will provide written response to each request for interpretation. One copy of City's response will be distributed in accordance with Section 01 33 00 — Submittals and Section 01 31 26 — Electronic Communications Protocols, to: a. Contractor. b. City. C. Resident Project Representative. d. Others, as noted in Section 0133 00 TABLE 0133 00 A. 6. If the City requests additional information to make an interpretation, provide information requested within ten days, unless City allows additional time, via correspondence referring to request for interpretation number. 7. If Contractor believes that a change in the Contract Price or Contract Times or other change to the Contract is required, notify the City in writing before proceeding with the Work associated with the request for interpretation. C. Submit each request for interpretation on a form acceptable to City. 1. Number each request for interpretation as follows: Numbering system shall be the Contract number and designation followed by a hyphen and three -digit sequential number. Example: First request for interpretation for project titled, "Contract 0000" would be, "RFI No. 0000-001 ". 2. In space provided on form, describe the interpretation requested. Provide additional sheets as necessary. Include text and sketches as required in sufficient detail for City's response. 3. When applicable, request for interpretation shall include Contractor's recommended resolution. 1.3 CLARIFICATION NOTICES A. General: 1. Clarification notices, when required, will be initiated, and issued by the City or other entity designated by the City. 2. Clarification notices do not change the Contract Price or Contract Times, and do not alter the Contract Documents. 3. Clarification notices will be issued as correspondence or using clarification notice form, with additional information as required. B. Procedure: 1. City's written clarification notices will be transmitted in accordance with Section 01 31 26 — Electronic Communication Protocols, and requirements of this Section. 2. Each written clarification notice will be distributed to: a. Contractor b. City C. Resident Project Representative d. Other entity noted in Section 01 33 00 TABLE 0133 00 A. 3. If Contractor believes that a change in the Contract Price or the Contract Times or other change to the Contract is required as a result of City's written clarification CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 01 26 00 CONTRACT MODIFICATION PROCEDURES Page 3 of 6 notice, notify the City in writing before proceeding with the Work associated with clarification notice. 4. If clarification notice is unclear, submit request for interpretation. 1.4 MINOR CHANGES IN THE WORK AND FIELD ORDERS A. General: 1. Field Orders, when required, will be initiated, and issued by the City. 2. Field Orders authorize minor variations in the Work but do not change the Contract Price or Contract Times. 3. The City will maintain a log of Field Orders issued. B. Procedure: 1. Field Orders will be transmitted in accordance with Section 01 31 26 — Electronic Communication Protocols, and requirements of this Section. Each Field Order will include a separate letter of transmittal. 2. Each Field Order will be distributed in accordance with Section 01 33 00 — Submittals and Section 01 31 26 — Electronic Communications Protocols, to: a. Contractor b. City C. Resident Project Representative d. Other entity as noted in Section 0133 00 TABLE 0133 00 A. 3. If the Contractor believes that a change in the Contract Price or the Contract Times or other change to the Contract is required as a result of a Field Order, immediately notify the City in writing before proceeding with the Work associated with the Field Order. 4. If the Field Order is unclear, submit request for interpretation. 1.5 WORK CHANGE DIRECTIVES A. General: 1. Work Change Directives, when required, order additions, deletions, or revisions to the Work, and will be initiated and issued by the City. 2. Work Change Directives do not change the Contract Price or Contract Times but are evidence that the parties to the Contract expect that the change ordered or documented by the Work Change Directive will be incorporated in subsequently issued Change Order following negotiations by the parties as to its effect, if any, on the Contract Price or Contract Times. B. Procedure. 1. Original, signed Work Change Directives will be distributed as in Section 01 33 00 — Submittals. 2. Documentation of Costs: a. When basis of payment for Work ordered under a Work Change Directive will be paid as Cost of the Work, or when otherwise required by the City, document for the Work performed under each separate Work Change Directive, for each day, the following: 1) Number and labor classifications of workers employed, and hours worked. 2) Equipment used, including manufacturer, model, and year of manufacture, and number of hours such equipment was onsite and used for the Work under the Work Change Directive. CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 01 26 00 CONTRACT MODIFICATION PROCEDURES Page 4 of 6 3) Consumables and similar materials used. 4) Receipts, bills, or invoices for and descriptions of materials and equipment incorporated into the Work. 5) Invoices and labor and equipment breakdowns for Subcontractors and Suppliers. 6) Other information required by City. b. Submit such information in a format noted in Section 01 33 00 — Submittal and Section 01 31 26 —Electronic Communication Protocols. C. Transmit such documentation to the City as a Change Proposal. 1.6 PROPOSAL REQUESTS A. General: 1. Proposal requests will be initiated by City. 2. Proposal requests are for requesting the effect on the Contract Price and the Contract Times and other information relative to contemplated changes in the Work. Proposal requests do not authorize changes or variations in the Work, and do not change the Contract Price or Contract Times or terms of the Contract. 3. Proposal requests will be furnished using the proposal request form included with this Section. B. Procedure. 1. Proposal Requests will be transmitted in accordance with Section 01 31 26 — Electronic Communication Protocols, and requirements of this Section. Each Proposal Request will include a separate letter of transmittal. 2. Each signed proposal request will be transmitted to: a. Contractor b. City C. Other entities as noted in Section 0133 00 — Submittals TABLE 0133 00 A 3. Submit request for interpretation to clarify conflicts, errors, ambiguities, and discrepancies in proposal request. 4. Upon receipt of proposal request, Contractor shall prepare and submit to the City a Change Proposal, in accordance with the Contract Documents, for the proposed Work described in the proposal request. 1.7 CHANGE PROPOSALS A. General. 1. Submit written Change Proposal to the City in response to each Proposal Request, or when Contractor believes a change in the Contract Price or Contract Times or other change to the terms of the Contract is required. B. Procedure. 1. Prepare and transmit Change Proposals within 45 days of the start of the occurrence or event giving rise to the need for a change. 2. Transmit Change Proposals in accordance with Section 01 3126 — Electronic Communication Protocols, and requirements of this Section. Include with each Change Proposal all required supporting documentation and a separate letter of transmittal. 3. City's Review and Requests for Additional Information: a. The City will review and act on each Change Proposal within 30 days of receipt. CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 01 26 00 CONTRACT MODIFICATION PROCEDURES Page 5 of 6 b. When the City requests additional information to render a decision, submit required information within 20 days of receipt of request, unless the City allows more time. Submit the required information via correspondence that refers to the specific Change Proposal number. C. City will render a written decision on the Change Proposal. d. City's response to Change Proposals will be transmitted in accordance with Section 01 31 26 — Electronic Communication Protocols, and requirements of this Section. 4. City's response to each Change Proposal will be distributed in accordance with Section 01 33 00 — Submittals and Section 01 31 26 — Electronic Communications Protocols, to: a. Contractor. b. City. C. Resident Project Representative. d. Other entity as noted in Section 0133 00 TABLE 0133 00 A 5. If Change Proposal is recommended for approval by the City and approved by City, a Change Order will be issued or, when applicable, an appropriate use of contingency allowance will be authorized by City. C. Preparation of Change Proposals: 1. Each Change Proposal shall be submitted on a form acceptable to the City. 2. Number each Change Proposal as follows: Numbering system shall be the Contract number and designation followed by a hyphen and three -digit sequential number. Example: First Change Proposal for project named "Contract 0000" would be, "Change Proposal No. 0000-001". 3. In space provided on Change Proposal form: a. Describe scope of each proposed change. Include text and sketches on additional sheets as required to provide detail sufficient for City's review and response. If a change item is submitted in response to Proposal Request, write in as scope, "In accordance with Proposal Request No." followed by the Proposal Request number. Provide written clarifications, if any, to scope of change. b. Provide justification for each proposed change. If change is in response to Proposal Request, write in as justification, "In accordance with Proposal Request No." followed by the Proposal Request number. C. List the total change in the Contract Price and Contract Times for each separate change item included in the Change Proposal. 4. Unless otherwise directed by the City, attach to the Change Proposal detailed breakdowns of pricing (Cost of the Work and Contractor's fee) including: a. List of Work tasks to accomplish the change. b. For each task, labor cost breakdown including labor classification, total hours per labor classification, and hourly cost rate for each labor classification. C. Equipment and machinery to be used, including manufacturer, model, and year of manufacture, and number of hours for each. d. Detailed breakdown of materials and equipment to be incorporated into the Work, including quantities, unit costs, and total cost, with Supplier's written quotations. e. Breakdowns of the Cost of the Work and fee for Subcontractors, including labor, construction equipment and machinery, and materials and equipment incorporated into the Work, other costs, and Subcontractor fees. f. Breakdown of other costs eligible. CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 01 26 00 CONTRACT MODIFICATION PROCEDURES Page 6 of 6 g. Other information requested by the City. h. Contractor's fees applied to eligible Contractor costs and eligible Subcontractor costs. 1.8 CHANGE ORDERS A. General: 1. Change Orders will be signed by City and Contractor, to authorize additions, deletions, or revisions to the Work, or changes to the Contract Price or Contract Times. B. Procedure. 1. Change Orders for signature by Contractor will be transmitted in accordance with Section 01 31 26 — Electronic Communication Protocols, and requirements of this Section. Each Change Order will include a separate letter of transmittal. 2. Contractor shall promptly sign each original Change Order and, within five days of receipt, return all originals to the City. 3. The City will process each original Change Order as follows: a. The City's Project Manager or his representative will promptly sign an approved and forward the original Change Order to the Water Department Director. b. The Water Director will sign and forward each original Change order to the City Manager's Office. C. After approval by City Council action (if necessary) the Change Order will be signed by the City Manager. 4. After approval and signature by the City, original signed Change Orders will be distributed in accordance with Section 0133 00 — Submittals and Section 01 31 26 — Electronic Communications Protocols. PART 2 — PRODUCTS (NOT USED) PART 3 — EXECUTION (NOT USED) + + END OF SECTION + + CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 SECTION 0129 73 SCHEDULE OF VALUES PART 1 — GENERAL 1.1 DESCRIPTION 01 29 73 SCHEDULE OF VALUES Pagel of 5 A. Scope: 1. The Contractor shall prepare and submit to the City for acceptance a Schedule of Values that allocates cost to each item of the Work. Schedule of Value list of line items shall correspond to each aspect of the Work, establishing in detail the portion of the Contract Price allocated to each major component of the Work. 2. Upon request of City, support values with data that substantiate their correctness. 3. Submit preliminary Schedule of Values to the City for initial review. The Contractor shall incorporate the City's comments into the Schedule of Values and resubmit to the City. The City may continue to require corrections and re -submittals until Schedule of Values is acceptable. 4. Schedule of Values may be used as a basis for negotiating price of changes, if any, in the Work. 5. Schedule of Values and the Progress Schedule updates specified in Section 0132 16 — Progress Schedule, will be basis for preparing each Application for Payment. 1.2 SUBMITTALS A. Informational Submittals: Submit the following: 1. Submit to the City a Schedule of Values in the form and quantity required in Section 0133 00 — Submittal Procedures, and in accordance with Section 01 31 26 — Electronic Communication Protocols. 2. Content of Schedule of Values submittals shall be in accordance with Paragraph 1.3 of this Section. 3. Timing of Submittals: a. Submit preliminary Schedule of Values within time limit indicated in the General Conditions as modified by the Supplementary Conditions. b. The Contractor shall not submit an Applications for Payment prior to the City's acceptance of the Schedule of Values. Completing the review process noted in Paragraph 1.1 A. 3. of this Section, in time to meet General Conditions timing requirements for the handling of Progress Payments is the responsibility of the Contractor. C. When required by the City, promptly submit updated Schedule of Values to include cost breakdowns for changes in the Contract Price. 1.3 SCHEDULE OF VALUES FORMAT AND CONTENT A. Organization and Major Elements of Schedule of Values 1. Prepare Schedule of Values on the "progress estimate" or "continuation sheets," as applicable, of the Application for Payment form indicated in Section 0129 76 — Progress Payment Procedures. 2. Include in Schedule of Values itemized list of Work for each major work area included in the Work, for each payment item specified in Section 0122 13 — CTTY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 01 29 73 SCHEDULE OF VALUES Page 2 of 5 Measurement and Payment. Group the Work in the Schedule of Values into the following areas: a. Break out each Lump Sum and Unit Cost. 3. Organization in Accordance with Specification Sections: a. Within each work area, organize the Schedule of Values by the various Specifications Section numbers and titles included in the Contract Documents. b. Label each row in the Schedule of Values with the appropriate Specifications Section number. Include an amount for each row in the Schedule of Values. C. List sub -items of major products or systems, as appropriate or when requested by the City. 4. Include in Schedule of Values unit price payment items with their associated quantity. Provide in the Schedule of Values detailed breakdown of unit prices when required by the City. B. Requirements for preliminary Schedule of Values and Schedule of Values are: 1. Subcontracted Work: a. Schedule of Values shall show division of Work between the Contractor and Subcontractors. b. Line items for Work to be done by Subcontractor shall include the word, "(SUBCONTRACTED)." 2. Apportionment between Labor, Materials and Equipment (if required), and Installation: a. Schedule of Values shall include breakdown of costs for materials and equipment, installation, and other costs used in preparing the Bid by the Contractor and each Subcontractor. b. List purchase and delivery costs for materials and equipment for which the ine �scnecme oT vatues-snan present- a summary of cost -at the proposal item level. - For each lump sum and unit cost item provide a section title and sub -total amount then present all breakout rows necessary to meet the requirements of the Contract Documents. Additional breakout shall include: a. Project Management shall be a breakout row for each Proposal Item. b. Preconstruction work, summarized under Proposal Items No. 2 and No. 3, shall also at minimum be divided into smaller breakout rows for each Key Activity defined in Section 40 61 13. C. Construction work, summarized under Proposal Item No. 4 through No. 9, shall also at minimum be divided into smaller breakout rows for: 1) Electrical installation incorporated by Change Order. 2) Hardware incorporated by Field Order or Change Order. 3) Software procured. 4) Installation of Software. 5) Reprogramming of existing PLCs (except work under Proposal Item No. 4). 6) PLC programming (except work under Proposal Item No. 4). 7) Training provided. 8) Testing. 9) Non -labor expenses, , , , , , , , , , , , , , , , , necessary 4. Partial payments will be made for lump sum line items in the Agreement. CTTY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 01 29 73 SCHEDULE OF VALUES Page 3 of 5 a. Lump sum line items in the Agreement are to be divided into smaller unit prices to allow more accurate determination of the percentage of the item that has been completed. 1) Provide adequate detail to allow more accurate determination of the percentage of work completed for each item. 2) Provide prices for items that do not exceed $50,000.00. An exception may be made by the City for equipment packages that cannot be subdivided into units or subassemblies. 3) Separate product costs and installation costs. a) Product costs include cost for product, delivery and unloading costs, royalties and patent fees, taxes, and other cost paid directly to the Subcontractor or Supplier. b) Installation costs include cost for the supervision, labor and equipment for field fabrication, erection, installation, start-up, initial operation and Contractor's overhead and profit. For equipment or systems that exceed $50,000 the costs reported for startup activation shall not be less than 10 percent of the total item cost. 4) Lump sum items may be divided into an estimated number of units. a) The estimated number of units times the cost per unit must equal the lump sum amount for that line item. b) Contractor will receive payment for all of the lump sum line item. 5) Include a directly proportional amount of Contractor's overhead and profit for each line item. 6) Divide principal subcontract amounts into an adequate number of line items to allow determination of the percentage of work completed for each item. 5. Sum of individual values shown on the Schedule of Values shall equal the total of associated payment item. Sum of payment item totals in the Schedule of Values shall equal the Contract Price. 6. Overhead and Profit: Include in each line item a directly proportional amount of the Contractor's overhead and profit. Do not include overhead and profit as separate item(s). 7. Include separate line item for each allowance, and for each unit price item. 8. Bonds and Insurance Costs: Work shall be included in the Schedule of Values and proportioned in Applications for Payment equally throughout duration of the Work within each lump sum. Include such items in Applications for Payment as subsidiary to Lump Sum items distributed based on the percentage of each item to the sum of all Lump Sum items in the Proposal. 9. Include relevant items for the General Conditions, permits (when applicable), construction Progress Schedule, and other items required by City. Work shall be included in the Schedule of Values and proportioned in Applications for Payment equally throughout duration of the Work within each lump sum. Include such items in Applications for Payment as subsidiary to Lump Sum items distributed based on the percentage of each item to the sum of all Lump Sum items in the Proposal. Work shall be included in the Schedule of Values and proportioned in Applications for Payment equally throughout duration of the Work within each lump sum. Include such items in Applications for Payment as subsidiary to Lump Sum items distributed based on the percentage of each item to the sum of all Lump Sum items in the Proposal. 10. Mobilization and Payment: a. Include separate line items under each appropriate payment item for mobilization and demobilization. Document for City the activities included in CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 012973 SCHEDULE OF VALUES Page 4 of 5 mobilization and demobilization line items. The total of all such mobilization items shall equal the value of Proposal Item No. 1 Mobilization. b. Mobilization will be limited to the percent of the Total Amount as noted in Section 00 42 10 — Proposal. Payment for mobilization will be made separately for each Lum Sum item in the Proposal based on the percentage of each item to the sum of all Lump Sum items. Mobilization for each Lump Sum item will be paid in 4 payments, each of 25 percent of total amount for mobilization for the item. Payments shall commence with the first month on -site construction activities associate with the specific with remaining payments in the sequential calendar months. C. Demobilization shall not be less than 1 percent of the Total Amount, unless otherwise accepted by the City and shall be included with the Application for Payment following Final Acceptance. Rejection of acceptance of amounts less than 1 percent shall not entitle the Contractor to additional compensation. 11. Payment of costs for progress design deliverables, shop drawings, samples, and other submittals; operations and maintenance manuals; field testing; and training of operations and maintenance personnel shall be as follows, unless otherwise accepted by City: a. Include costs associated preparation of design drawings, specification and calculation required by the Contract Documents to be sealed by a Professional Engineer delegated to the Contractor in lump sum items identified on the proposal for the design of specific facilities or groups of facilities. b. Include costs associated with the preparation of all other Shop Drawings, Samples, and other submittals shall be included as subsidiary within the lump sum items. Distribute cost based on the proportion of each lump sum to the total of all lump sum items. C. Five percent of total cost of each item (including all associated labor, overhead and profit), including materials and equipment (if required), and installation, shall be apportioned to testing and included in the Application for Payment following either the City's acceptance of the associated written field-testing report(s) or, where field testing is not required at the City's acceptance of Partial Utilization of Work following notification in accordance with Article 14.04 of the General Conditions. This shall be considered on a facility or group wide basis within divisions of the Work noted as lump sums on the Proposal and shall occur no sooner that the cutover and acceptance of Partial Utilization of the last Work within that facility. d. Up to a total of four percent of equipment cost (including all associated overhead and profit), exclusive of transportation and installation costs, may be apportioned to operations and maintenance manuals and training of operations and maintenance personnel, which may be included in the Application for Payment following completion of training for that item. 12. Payment for Project Record Documents: a. Include in the Schedule of Values a line item with 0.5 percent of the Contract Price for Project record documents. b. If adequate record documents are maintained, up to 50 percent of the value of the record documents line item will be eligible for payment, spread evenly over those progress payments in which construction at the Site is performed. C. Remainder of Project record documents line item will be eligible for payment when complete record documents are submitted in accordance with the Contract Documents. If record documents submitted are unsatisfactory to the CTTY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 01 29 73 SCHEDULE OF VALUES Page 5 of 5 City, amount may be reduced via setoffs in accordance with the Contract Documents. 13. The Schedule of Values shall include an itemized list of all work -by -work areas applicable to shutdowns, coordination or constrains, as applicable, for Work included in Section 01 14 16 — Coordination with City's Operations. 14. The Contractor shall coordinate Schedule of Values with cost -loading of the Progress Schedule, in accordance with Section 0132 16 — Progress Schedule. PART 2 — PRODUCTS (NOT USED) PART 3 — EXECUTION (NOT USED) + + END OF SECTION + + CTTY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 SECTION 0129 76 PART 1 — GENERAL 1.1 PROGRESS PAYMENTS 01 29 76 PROGRESS PAYMENT PROCEDURES Page 1 of 4 A. Scope: 1. Contractor's requests for payment shall be in accordance with the Agreement and this Section. 2. Applications for Payment shall be in the form of Engineers Joint Contract Documents Committee (EJCDC) document EJCDC® C-620, "Contractor's Application for Payment", 2013 edition or later or alternative City accepted computer generated forms. 3. Computer Generated Applications for Payment: applications not submitted on pre-printed forms employing EJCDC documents shall be submitted on forms generated by computer. The form employed shall have the same format and information indicated in the EJCDC C-620 form. Computer generated payment requests must be approved by the City in accordance with this Section and Section 01 29 73 — Schedule of Values. Template (forms) EJCDC C-620 following the words END OF SECTION, shall be considered part of this Section. B. Procedure: 1. The Contractor shall review with the City the percentage completions or quantities, resultant costs, equipment, and materials for which payment is proposed in each progress payment. Application for Payment shall include only the amounts accepted by the City. 2. Contractor shall be required to review with the City status of record documents in connection with the items included in each Application for Payment. Failure to maintain record documents current will be just cause for City to recommend a reduction in payment for record documents in accordance with Section 01 29 73 — Schedule of Values, and will entitle the City to set -offs in accordance with the Contract Documents. 3. The City may delegate duties to the Engineer, Resident Project Representative (RPR) or others noted in Section 0133 00 — Submittals. 4. Routing of Applications for Payment shall be in accordance with Section 01 31 26 — Electronic Communication Protocols. 5. Submit to the City five (5) printed originals, each with Contractor's original, "wet" signature, of each complete Application for Payment and other documents to accompany the Application for Payment. 6. City will act on request for payment in accordance with the General Conditions, as modified by the Supplementary Conditions. 7. Include a completed summary as indicated in with each Applications for Payment submitted. a. Number each application sequentially and indicate the payment period. b. Show the total amounts for value of original contract performed, extra work on approved Change Orders, and materials on hand on the Project Summary Report. CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 01 29 76 PROGRESS PAYMENT PROCEDURES Page 2 of 4 c. Show total amounts that correspond to totals indicated on the attached tabulation for each. d. Note the number of pages in tabulations in the blank space on the Project Summary Report to allow a determination that all sheets have been submitted. e. Execute Contractor's certification by the Contractor's agent of authority and notarize for each Application for Payment. Do not alter the schedule of values and the form for the submission of requests without the written approval of the Engineer once these have been approved by the Engineer. Final Payment: additional requirements for final payment are noted in Section 01 77 19 —Closeout Requirements. C. Format: 1. Cover sheet shall indicate: a. Summary calculation including items "l. ORIGINAL CONTRACT PRICE" through "9. BALANCE TO FINISH, PLUS RETAINAGE" as noted EJCDC C-620. b. Provide Tabular Change Order Summary of Additions and Deductions auuroved as of the date of Application submittal. c. Contractor Certification, incorporate the certification language included on EJCDC C-620 verbatim, with underlying Signature, title and date blocks noted as "Submitted by". d. "Recommended by" Signature and date block, noted as "Engineer / Other as Delegated by City" followed by "Payment of. $ " noted as "Line 8. or other — attach explanation of the other amount" e. "Approved by" Signature, title, and date block, noted as "City." 2. Attachment A — Progress Estimate: provide EJCDC forms for Lump Sum and Unit Price work included in the Proposal, sub -divided as noted in the Schedule of Values accepted by the City or provide the Contractor's Attachment A meeting the requirements noted in Paragraph I.1.C.3.c. below. a. Incorporate additional forms as necessary to sub -divide proposal items into the accepted Schedule of Values row format. b. Number Attachment A pages as "Sheet _ of _" where more than one Lump Sum or Unit Price form is necessary. C. The Contractor may provide an alternate Attachment A combining the Lump Sum and Unit Price proposal items in a single list reflecting the breakout on the accepted Schedule of Values. Provide page numbering noted above in Paragraph b. The alternate form shall be approved by the City in accordance with Section 0129 73 — Schedule of Values. 3. Attachment B — Tabulation of Approved Change Orders. a. Identify Change Order (CO) by number and provide a description. b. Breakout by column the Original Quantity, Unit of Measure and Contract Amount added by the CO. C. Provide additional columns for Quantity This Estimate, Quantity to Date, Value of Completed Work and Percent of Work Completed. d. Provide a Total for Project / Page row at the bottom of each page. 4. Attachment C — Tabulation of Materials on Hand (where applicable). a. Provide EJCDC Stored Materials Summary sheet. Adding and number additional pages as necessary as "Page _ of _." The Contractor shall replace Column B title "Submittal Number" and replace with "Item CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 01 29 76 PROGRESS PAYMENT PROCEDURES Page 3 of 4 Number" and enter the accepted Schedule of Values Item Number, utilized in Attachment A, associated with the materials. b. The Contractor may provide an alternate computer -generated Attachment B. The alternate form shall be approved by the City in accordance with Section 0129 73 — Schedule of Values. C. List all materials on hand that are presented for payment on the Tabulation of Materials on Hand. d. Once an item has been entered on the tabulation it is not to be removed. Include a Project Summary Report with each Application for Payment. a. Data included in the Project Summary Report are to be taken from the other tabulations. b. Provide a "Contract Time Summary" section noting: ■ Date of Notice to Proceed. ■ Original Contract Duration (Days). ■ Original Date of Contract Substantial Completion. ■ Approved Time Extensions stating the extension in Days and providing the Current Contract Duration (Days) with all CO approved as of the date of submittal. ■ Current Date of Contract Substantial Completions and Current Date of Contract Final Acceptance with all CO approved as of the date of submittal. ■ Note the Percentage of Current Project Duration remaining. ■ Note the Current Schedule Completion Date substantiated by the update Schedule accompanying the Application for Payment and state the number of Days Ahead (+) or Behind (-). C. Provide a "Contract Cost Summary" section noting: ■ Original Contract Amount (Price). ■ Total of Change Orders approved as of the date of submittal. ■ Current Contract Amount (Price). ■ Contract Earnings to Date on Original Contract. ■ Earnings to Date on Change Orders. ■ Materials on Hand (where applicable) ■ Total Current Project Amount Earned ■ Percentage of Contact Amount Earned to Date ■ Retainage (-) ■ Amount Paid to Date as a dollar ($) total and percentage (%) of contract amount. PART 2 PRODUCTS (NOT USED) PART 3 — EXECUTION (NOT USED) + + END OF SECTION + + CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 01 29 76 PROGRESS PAYMENT PROCEDURES Page 4 of 4 ++THIS PAGE INTENTIONALLY LEFT BLANK++ CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 SECTION 01 31 13 PROJECT COORDINATION PART 1 — GENERAL 1.1 DESCRIPTION 0131 13 PROJECT COORDINATION Page 1 of 2 A. Scope: 1. Contractor shall coordinate the Work, including testing agencies, Subcontractors, Suppliers, Manufacturers, and others with whom coordination is necessary to complete the Work within the Contract Times and in accordance with the Contract Documents. B. Coordination: 1. Contractor shall coordinate the Work with SCADA integration requirements of new projects under design, ongoing projects at the sites, utility service companies, and other entities working at the Site, in accordance with Section 01 11 13 — Summary of Work. 2. Contractor will not be responsible or liable for damage unless damage is through negligence of Contractor, or Subcontractor, Supplier, or other entity employed by Contractor. 3. Contractor shall attend and participate in all project coordination and progress meetings, and report on the progress of the Work and compliance with the Progress Schedule. C. Notices Required: 1. Contractor shall notify the City at least 15 days prior to mobilizing to the site. 2. Except where specifically noted otherwise, Contractor shall notify the City any shutdowns required at any facility in accordance with the requirements described in 01 14 16, Coordination with City's Operations. 3. Contractor shall notify the City at least 15 days prior to any design review meetings or workshops scheduled in the project schedule. D. When requested by the City, Contractor shall attend scheduled Cellular Service Provider's informational meetings after award of the Contract. E. Layout and Coordination Drawings: 1. Maintain sufficient competent personnel, drafting and computer -aided drafting/computer aided design (CAD) equipment, software, systems, and supplies at the Site for preparing layout drawings, coordination drawings, and record documents. 2. With the design drawings and Shop Drawings, use such coordination drawings as tools for coordinating the Work of various trades and for coordinating the Work with other Contractor's ongoing work at the site. 3. Where such coordination drawings are to be prepared by Subcontractors, ensure that each Subcontractor maintains required personnel and facilities at the Site. CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 0131 13 PROJECT COORDINATION Page 2 of 2 PART 2 - PRODUCTS (NOT USED) PART 3 - EXECUTION (NOT USED) + + END OF SECTION + + CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 SECTION 01 31 19.23 PROGRESS MEETINGS PART 1 — GENERAL 1.1 DESCRIPTION 01 31 19.23 PROGRESS MEETINGS Page 1 of 4 A. Scope: 1. Progress meetings will be held throughout the Project. Contractor shall attend each progress meeting prepared to discuss in detail all items on the agenda. 2. The Contractor shall preside at progress meetings and will prepare and distribute minutes of progress meetings to all meeting participants and others as requested. 1.2 PREPARATION FOR PROGRESS MEETINGS A. Date and Time: 1. Regular Progress Meetings for both preconstruction and construction: Monthly for the duration of the contract on a day and time agreeable to City and Contractor. 2. Other Meetings: As required. B. Location: 1. Progress meeting during the preconstruction Services shall be held at South Holly WTP training room or other location mutually agreed upon by City, and Contractor. 2. The progress construction meetings for each Water Treatment Plant shall be held at the respective facility. C. Handouts: 1. Contractor shall bring to each progress meeting a minimum of ten copies of each of the following: a. List of Work accomplished since the previous progress meeting. b. Up-to-date Progress Schedule. C. Up-to-date Schedule of Submittals. d. Detailed "look -ahead" schedule of Work planned through the next progress meeting, with specific starting and ending dates for each activity, including shutdowns, deliveries of important materials and equipment, Milestones (if any), and important activities affecting the City, Project, and Site. e. When applicable, list of upcoming, planned time off (with dates) for personnel with significant roles on the Project, and the designated contact person in their absence. 1.3 REQUIRED ATTENDANCE A. Representatives present for each entity shall be authorized to act on that entity's behalf. B. Required Attendees: 1. Contractor: a. Project manager. b. Site superintendent. C. Safety representative. CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 01 31 19.23 PROGRESS MEETINGS Page 2 of 4 d. When needed for the discussion of a particular agenda item, representatives of Subcontractors and Suppliers shall attend meetings. 2. City's representative(s), as required. 3. Testing and inspection agencies, as required. 4. Others, as appropriate. 1.4 AGENDA A. Preliminary Agenda: Be prepared to discuss in detail the topics listed below. Revised agenda, if any, shall be furnished by Contractor prior to first progress meeting. Progress meeting agenda may be modified during the Project as required. 1. Review, comment, and amendment (if required) of minutes of previous progress meeting. 2. Review of progress since the previous progress meeting. 3. Planned progress through next progress meeting. 4. Review of Progress Schedule a. Contract Times, including Milestones (if any) b. Critical path. C. Schedules for Design Submittals d. Upcoming design coordination meetings and/or workshops e. Any design issues encountered that effects contract schedule f. Schedules for fabrication and delivery of materials and equipment. g. Corrective measures, if required. 5. Submittals: a. Review of design status, design submittals, and approval by City. b. Review of status of critical submittals. C. Review revisions to Schedule of Submittals. 6. Contract Modifications a. Design change requests (if any). b. Requests for interpretation. C. Clarification notices. d Field Orders. e. Proposal requests. f. Change Proposals. g. Work Change Directives. h. Change Orders. i. Claims. 7. Applications for progress payments. 8. Problems, conflicts, and observations. 9. Quality standards, testing, and inspections. 10. Coordination between parties. 11. Site management issues, including access, security, maintenance and protection of traffic, maintenance, cleaning, and other Site issues. 12. Safety. 13. Permits. 14. Record documents status. 15. Punch list status, as applicable. 16. Other business. CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 01 31 19.23 PROGRESS MEETINGS Page 3 of 4 PART 2 - PRODUCTS (NOT USED) PART 3 - EXECUTION (NOT USED) + + END OF SECTION + + CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 01 31 19.23 PROGRESS MEETINGS Page 4 of 4 ++THIS PAGE INTENTIONALLY LEFT BLANK++ CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 01 31 26 ELECTRONIC COMMUNICATION PROTOCOLS Page 1 of 6 SECTION 01 31 26 I [�PuIUV012M[�1:Mtl[Glen 9:ZOII6ZK9II PART 1 — GENERAL 1.1 DESCRIPTION A. Scope: 1. This Section establishes the procedures with which the parties will comply regarding transmission or exchange of electronic documents and/or data for the Project. 2. Contractor shall provide labor, materials, equipment, services, utilities, and incidentals specified, and required for complying with this Section throughout the Project. 3. In addition to the requirements of this Section, comply with requirements for exchange of electronic data in the following: a. Section 0126 00 — Contract Modification Procedures. b. Section 0129 73 — Schedule of Values. C. Section 0132 16 — Progress Schedule. d. Section 0133 00 — Submittal Procedures. e. Section 0178 39 — Project Record Documents. B. Coordination: 1. Contractor shall require all Subcontractors and Suppliers to comply with the electronic communication protocols established in this Section. 1.2 TERMINOLOGY A. The following words or terms are not defined but, when used in this Section, have the following meaning: 1. "Electronic documents" means correspondence, information, communications, drawings, or designs created or stored for the Project in electronic or digital form. 2. `Electronic data" means information contained in a table, a schedule, Input/Output (IO) list, or values created in a software package or stored for the Project in electronic or digital form. 3. "Confidential information" means electronic documents and/or data that the transmitting party has designated as confidential and clearly marked with an indication such as "Confidential", "Business Proprietary", or similar designation. 4. "Written" or "in writing" as defined in Section 00 73 00 Article SC1.01. 1.3 TRANSMISSION OF ELECTRONIC CORRESPONDANCE OR DATA A. Transmission of electronic correspondence and/or data constitutes a warrant by the transmitting party to the receiving party that the transmitting party is one or more of the following: 1. The copyright owner of the electronic correspondence or data. 2. Has permission from the copyright owner to transmit the electronic correspondence or data for its use on the Project. 3. Is authorized to transmit confidential information. CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 01 31 26 ELECTRONIC COMMUNICATION PROTOCOLS Page 2 of 6 B. Receiving parry agrees to keep confidential information confidential and not to disclose it to another person except to (1) its employees working on this contract, (2) those who need to know the content of the confidential information to perform services or construction solely and exclusively for the Project, or (3) its consultants and Suppliers whose contracts include similar restrictions on the use of electronic data and confidential information. C. Transmitting party does not convey any right in the electronic correspondence or data or in the software used to generate or transmit such correspondence or data. Receiving party may not use electronic correspondence and/or data unless permission to do so is provided in the Contract Documents, or in a separate license. D. Unless otherwise granted in a separate license, receiving party's use, modification, or further transmission of electronic correspondence and/or data, as provided the Contract Documents, is specifically limited to the design and construction of the Project in accordance with this Section, and nothing contained in this Section conveys any other right to use the electronic correspondence or data for any other purpose. E. To the fullest extent permitted by Laws and Regulations, receiving party shall indemnify and defend the transmitting party from and against all claims arising from or related to receiving party's modification to, or unlicensed use of, electronic correspondence or data. F. Means of Transmitting Electronic correspondence and/or Data: Unless otherwise indicated in Table 0131 26-A of this Section or elsewhere in the Contract Documents, transmission of electronic data for the Project will generally be via: 1. ALL DOCUMENT TRANSFERS SHALL BE BY UPLOAD OR DOWNLOAD FROM THE PROJECT SITE. E-mail use is limited to written communications between the parties and should not be used to transmit files as attachments. Flash drives shall not be used. If the use of a flash drive for a specific need is approved the drive shall have non -removable label clearly showing the project name and required details of the content. 2. Project's web -based collaboration platform. a. Software Platform: BIM360. b. Website hosting will be by City. C. Website address will be furnished to Contractor within ten days after the Effective Date of the Contract. d. To access the Project site, Contractor shall acquire and maintain throughout the Project high-speed Internet service suitable for transferring electronic data, and compatible Internet browsing software such as Microsoft Edge, Google Chrome TM version 29 or later, or equal. e. Upon request of one or both parties, the City will provide training for requesting party for up to two hours (one time) via, a web -based meeting interface selected by the City's. Requesting party shall compensate the City for cost of such additional training. 1.4 ELECTRONIC DATA PROTOCOLS A. Comply with the data formats, transmission methods, and permitted uses set forth in TABLE 0131 26-A, Electronic Data Protocol Table, below, when transmitting or using electronic data on the Project. Where a row in the table has no indicated means of transmitting electronic data, use for such documents only printed copies transmitted to the receiving party via appropriate delivery method. CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ELECTRONIC DATA 1A.A.1. Project communications General communications & correspondence _ Meeting notices and agendas Meeting minutes Contractor's Daily Reports 1.4.A.2. Contractor's submittals to City Project Plan and Schedule Design Phase Submittals (Technical Reports and Drawings) Shop Drawings Documentation of delivery of maintenance materials submittals Record Drawings and Final System Documentation (O&M, Pro 1.4.A.3. City's return of reviewed submittals to Contractor Shop Drawings Product data Informational and closeout submittals: Documentation of delivery of maintenance materials submittals I A A.4. Contract Modifications Documents Requests for interpretation to City City's interpretations (RFI responses) City's clarifications to Contractor 1 A A A r,.,,-r rr,.,.,,«,o,,.. r1',..,r:«»oa1 01 3126 ELECTRONIC COMMUNICATION PROTOCOLS Page 3 of 6 TABLE 0131 26-A ELECTRONIC DATA PROTOCOL TABLE TRANSMISSION DATA FORMAT TRANSMITTING PARTY METHOD RECEIVING PARTY PERMITTED USES NOTES EM, PDF C, I PW C, I R PDF I PW C R PDF I PW C R EM, PDF I PW C R PDF I PW C M (1) DWG, PDF I PW and Paper C M (1) (4) DWG, PDF I PW C M (1)(4) PDF I PW C M (1) PDF I PW C M (1) (6) PDF I PW C M PDF I PW and Paper C M etc.) PDF I PW and Paper C M (1) (6) XLS, PDF C PW I R _ (8) XLS, PDF C PW I R (8) XLS, PDF C PW I R (6) (8) XLS, PDF C PW I R (8) PDF I PW C M (1) PDF C PW I R PDF C PW I R (9) City's issuance of Field Orders PDF C PW I R Proposal Requests PDF C PW I R Chan e Pro orals — submitted to CityPDF I PW C S Change Proposals — City's response PDF C PW I Work Change Directives PDF C PW I R (2) Change Orders (for Contractor signature) PDF C PW I R _ (7) Change Orders (signed by Contractor) PDF I PW and Paper C R (3) 1.4.A.5. Applications for Payment PDF I PW and Paper C R (3) 1.4.A.6. Claims and other notices PDF I, C PW C, I R 1.4.A.7. Closeout Documents PDF I PW C S Record drawings DWG, PDF I PW C M (5) Other record documents PDF I PW C M (5) Contract closeout documents PDF I PW C (8) CITY OF FORT WORTH SCADA Replacement 103086 01 31 26 ELECTRONIC COMMUNICATION PROTOCOLS Page 4 of 6 B. Key to Electronic Data Protocol Table: Data Format: EM msg, .htm, .txt, .rtf, e-mail text PDF pdf, Portable Document Format DWG Awg, Autodesk AutoCAD 2020 (or later version) drawing. XLS xlsx, Excel Workbook Transmitting/Receiving Party: C City I Contractor Transmission Method: EM NOT USED EMA NOT USED PW Posted to Project site Permitted Uses: Notes: S Store and view only R Reproduce and distribute M Modify as required to fulfill obligations for the Project (1) Modifications by City to Contractor's submittals and requests for interpretations are limited to printing out, marking up, and adding comment sheets. (2) May be distributed only to affected Subcontractors and Suppliers. (3) Submit printed Applications for Payment and Change Orders with original ("wet") signatures. (4) Submit design drawings and submittal drawings in native CAD format indicated. Drawings shall be provided using the AutoCAD eTransmit feature to bind external references, pen/line styles, fonts, and drawing file into individual zip files. (5) Submit record drawings in native CAD format indicated. In addition, always submit record drawings as a PDF file. Drawings shall be provided using the AutoCAD eTransmit feature to bind external references, pen/line styles, fonts, and drawing file into individual zip files. Comply with requirements of Section 0178 39 — Project Record Documents. (6) For operation and maintenance data, also submit printed copies as required by Section 01 78 23 — Operations and Maintenance Data. (7) Print out, sign document, and return executed printed copy originals to Entity Responsible for Construction Administration. (8) Contractor will print and distribute hard copies of reviewed submitted material when "Paper" is noted as a transmission method in this table, or hard copies are specifically required by the Contract Documents. CITY OF FORT WORTH SCADA Replacement March 21, 2024 103086 01 31 26 ELECTRONIC COMMUNICATION PROTOCOLS Page 5 of 6 (9) City Clarifications in accordance with Section 00 72 00 — General Conditions, Article 3.04 PART 2 — PRODUCTS (NOT USED) PART 3 — EXECUTION (NOT USED) + + END OF SECTION + + CITY OF FORT WORTH SCADA Replacement March 21, 2024 103086 01 31 26 ELECTRONIC COMMUNICATION PROTOCOLS Page 6 of 6 ++THIS PAGE INTENTIONALLY LEFT BLANK++ CITY OF FORT WORTH SCADA Replacement March 21, 2024 103086 SECTION 0132 16 PROGRESS SCHEDULE PART 1 — GENERAL 1.1 DESCRIPTION 0132 16 Progress Schedule Page 1 of 10 A. Scope: 1. The Contractor shall prepare, maintain, update, and submit Progress Schedules and related documents. 2. The Contractor shall coordinate the Work, and include all aspects of the Work, in the Progress Schedule, including but not limited to related: a. Milestones. b. Meetings and Workshop Activities. c. Submittals (including each stage of design or configuration submittals). d. Factory Testing Activities. e. PLC Programming and HMI software Development Activities. £ Onsite deployment Activities. g. Cutover, Field Testing and Startup Activities. h. Data Interface and Report Generation Activities. i. Closeout Activities. 3. Progress Schedule shall be a Critical Path Method (CPM) Progress Schedule. 4. Cost loading of the schedule is not required. However, at the option of the Contractor, the schedule may be cost -loaded. The Contractor shall be responsible for reflecting cost loading for Sub -Contractors Work in the schedule. a. Cost loading of activity line items shall be incorporated. b. The cost information shall also be displayed as a summary total in each month of the project duration on the schedule, or as a tabular report submitted with the schedule. The data and summary total in each monthly period shall accompany the Baseline Schedule and be updated monthly. 5. Resource loading of the schedule is not required. However, at the option of the Contractor the schedule may be resource loaded. If a resource loading is submitted, the data and any summary information shall accompany the Baseline Schedule and be updated monthly. 6. The City's acceptance of the Progress Schedule or related documents, and comments or opinions concerning activities in the Progress Schedule and related documents shall not control Contractor's independent judgment concerning means, methods, techniques, sequences, and procedures, unless the associated means, method, technique, sequence, or procedure is directed by the Contract Documents. Contractor is solely responsible for complying with the Contract Times. B. Use of Float: 1. Float time is not for the exclusive use or benefit of either the Contractor or City. 2. Float belongs to the Project and may be used by City to accommodate changes in the Work, or to mitigate the effect of events beyond the control of the Contractor that delay performance or conformance with the Contract Times. 3. Changes or delays that influence Activities that have float and that do not extend the Critical Path are not justification for an extension of the Contract Times. CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 0132 16 Progress Schedule Page 2 of 10 C. Factors Affecting the Progress Schedule: 1. In preparing the Progress Schedule, take into consideration Design and Construction submittal requirements and submittal review times, time for incorporating comments into design documents, resubmitting shop drawings, fabricating and delivering materials and equipment, Subcontractors' work, suppliers' product availability and abilities of workers, availability of equipment, weather conditions, restrictions in operations at the Sites, sequence of work specified and coordination with City 's operations, and other factors that have the potential to affect completion of the Work within the Contract Times. 2. Comply with specific sequencing and requirements as noted in Section 01 14 16 — Coordination with City's Operations. 1.2 DEFINITIONS A. The following terms are defined for this Section and supplement the terms defined elsewhere in the Contract Documents: 1. Activity: An element of the design or construction work that has the following specific characteristics: consumes time, consumes resources, has a definable start and finish, is assignable, and is measurable. 2. Constraint: An imposed date on the Progress Schedule or an imposed tie between Activities. The Contract Times are Constraints. 3. CPM Progress Schedule: Computerized Progress Schedule in Critical Path Method (CPM) format which accounts for the entire Work, defines the interrelationships between elements of the Work, reflects the uncompleted Work, and indicates the sequence with which the Design and Implementation Work has been completed, indicates the sequence in which uncompleted Design and Implementation Work will be completed, and indicates the duration of each Activity. 4. Critical Path: The continuous chain of Activities with the longest duration for completion within the Contract Times. 5. Early Start: The earliest possible date an Activity can start according to the assigned relationships among Activities. 6. Early Finish: The earliest date an Activity can finish according to the assigned relationships among the Activities. 7. Late Finish: The latest date an Activity can finish without extending the Contract Times. 8. Late Start: The latest date an Activity can start without extending the Contract Times. 9. Float: The time difference between the calculated duration of the Activity chain and the Critical Path. 10. Total Float: The total number of days that an Activity (or chain of Activities) can be delayed without affecting the Contract Times. 11. Network Diagram: A time -scaled logic diagram depicting the durations and relationships of the Activities. 12. Work Areas, Area, or System: A logical breakdown of the Project elements or a group of Activities which, when collectively assembled, are readily identifiable on the Project (for example, SCADA Network, Fiber optic cable network, a treatment process, or other logical grouping). CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 0132 16 Progress Schedule Page 3 of 10 1.3 QUALITY ASSURANCE A. Qualifications: 1. Progress Schedule Preparer: a. The Contractor shall retain services of a scheduling consultant or shall self - prepare and maintain the Progress Schedule using qualified employee with experience in scheduling and experienced with the scheduling software required for this Project, and experience serving as Progress Schedule preparer on design/construction projects of similar type, size, and scope to this Project. b. Progress Schedule preparer shall have not less than five years' experience using the schedule software required on design/construction projects of similar type, size, and scope as this Project. C. Prior to engaging a scheduling consultant or using a qualified employee, submit to City: 1) Name and address of proposed Progress Schedule preparer and the names of personnel who will be assigned to scheduling the Project. 2) Information sufficient to demonstrate that proposed Progress Schedule preparer and scheduling personnel to be assigned to the Project possess qualifications complying with requirements of this Section. For each person assigned, submit list of similar type, size, contract value of projects, names and contact information of Entity Responsible for Construction Administration or architect and City. d. City's Review of Qualifications: 1) The City will respond to Contractor whether proposed scheduling personnel are acceptable within 15 days after City 's receipt of complete qualifications. 2) If qualifications are not acceptable, submit qualifications of acceptable personnel within 30 days of receipt of City's non -acceptance. 3) City's acceptance or non -acceptance of qualifications does not release Contractor from its obligations under the Contract Documents. 1.4 SUBMITTALS A. Quantity of each submittal required, and timing of submittals are in this Section. B. Informational Submittals: Submit the following: 1. Initial Progress Schedules Submittal: a. Preliminary Progress Schedule with associated Network Diagrams, and narrative report. b. Acceptable Progress Schedule with associated Network Diagrams, and narrative report. C. Preliminary Progress Schedule and associated reports. d. Acceptable Progress Schedule and associated reports. e. Submit each Progress Schedule submittal with letter of transmittal complying with requirements of Section 01 33 00 — Submittal Procedures. f. Should the Contractor elect to submit a resource and cost loaded schedule, the requirements of Paragraphs c. through e. Above shall apply to the resource and cost loaded schedule. 2. Progress Schedule Update Submittals. a. Progress Schedule updates shall comply with requirements of this Section, and shall include updated Progress Schedule, narrative report, and updated CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 0132 16 Progress Schedule Page 4 of 10 Network Diagram when relationships among Activities are changed. b. Submit updated Progress Schedule at each progress meeting. If a Progress Schedule remains unchanged from one progress meeting to the next, the Contractor shall submit a written statement to that effect. For monthly Progress Schedule update submittals, bring to progress meeting the number of copies of the updated Progress Schedule specified in Section 0131 19.23 — Progress Meetings. 3. Look -Ahead Schedules: a. Submit 60-day look -ahead schedule at each progress meeting. 4. Time Impact Analyses: Submit in accordance with this Section. 5. Recovery Schedule: Submit in accordance with this Section. 1.5 INITIAL PROGRESS SCHEDULE DEVELOPMENT A. Type and Organization of Progress Schedules: 1. Prepare Progress Schedule using Microsoft Project unless other scheduling software is approved in writing by the City prior to preparation of the schedule. 2. Sheet Size: 11 inches by 17 inches unless otherwise accepted by the City. 3. Time Scale: Indicate first date of each work week. 4. Activity Designations: Indicate title and related Specification Section number. 5. Progress Schedules shall be CPM Progress Schedules. 6. Organization: a. Indicate on the separate Schedule of Submittals dates for submitting and reviewing Design documents, Shop Drawings, Samples, and other submittals. b. Group deliveries of materials and equipment into a separate sub -schedule that is part of the Progress Schedule. C. Design activities and construction activities shall be arranged and grouped in a manor it is easy to follow and understand by a reviewer. d. Group Design task into Work Area sub -schedules (that are part of the Progress Schedule) by Activity. All coordination and Design review meetings and workshops shall be identified in the schedule. e. Group construction into Work Area sub -schedules (that are part of the Progress Schedule) by Activity. All workshops shall be identified in the schedule. f. Clearly indicate the Critical Path on the Progress Schedule. B. Preliminary Progress Schedule: 1. Contractor shall submit the preliminary Progress Schedule covering the entire Project, with associated Network Diagrams within the time frame identified in the General Conditions. 2. Submit preliminary Progress Schedule in accordance with Section 01 3126 — Electronic Communication Protocols and Section 01 33 00 — Submittal Procedures. Also submit preliminary Progress Schedule in its native format generated by the scheduling software, transmitted using the transmission method indicated in Section 01 31 26 — Electronic Communication Protocols. 3. City will conduct a timely review of the preliminary Progress Schedule. 4. Preliminary Progress Schedule shall comply with the Contract Documents relative to Progress Schedules but need not be resource or cost loaded. C. Initial Acceptance of Progress Schedule: 1. At least 10 days before submission of the first Application for Payment, a scheduling conference attended by Contractor, Progress Schedule preparer, City, and others as CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 0132 16 Progress Schedule Page 5 of 10 appropriate will be held to review for acceptability to City the preliminary Progress Schedule and associated Network Diagram and other reports and schedule -related documents required. Contractor shall have an additional 10 days to make corrections and adjustments and to complete and resubmit the Progress Schedule and associated Network Diagram. No progress payment will be made to Contractor until acceptable Progress Schedule, Network Diagram, and other reports and schedule -related documents required are submitted to City. 2. Submit acceptable Progress Schedule, together with Network Diagram, reports, and other schedule -related documents required to accompany the Baseline Progress Schedule, in accordance with the Submittals Article of this Section, Section 01 31 26 — Electronic Communication Protocols, and Section 0133 00 — Submittal Procedures. Also submit acceptable form of Progress Schedule in its native format generated by the scheduling software, transmitted using the transmission method indicated in Section 01 31 26 — Electronic Communication Protocols. 3. The Progress Schedule will be acceptable to City if it provides an orderly progression of the Work to completion within the Contract Times, in accordance with the Contract Documents. Such acceptance will not impose on City responsibility for the Progress Schedule, for sequencing, scheduling, or progress of the Work nor interfere with or relieve the Contractor from the Contractor's full responsibility therefor. 4. Baseline Progress Schedule shall be clearly identified using the words "Baseline Progress Schedule" in the document title information, file name, etc. The Baseline Project Schedule shall also be denoted Rev.0. D. Cost Loaded Progress Schedule (If used by the Contractor): 1. Within 30 days after City's acceptance of the Progress Schedule, submit cost loaded Progress Schedule complying with cost loading requirements in this Section. 2. Submit cost -loaded Progress Schedule and associated reports in accordance with the Submittals Article of this Section, Section 01 3126 — Electronic Communication Protocols, and Section 0133 00 — Submittal Procedures. Also submit cost -loaded Progress Schedule in its native format generated by the scheduling software, transmitted using the transmission method indicated in Section 01 31 26 — Electronic Communication Protocols. 3. Cost loaded Progress Schedules will be reviewed by City within 10 days of City's receipt, and City's comments will be transmitted to Contractor. 4. Make revisions required in accordance with City's comments and resubmit to City within 5 days of Contractor's receipt of City's comments. 5. Cost loaded Progress Schedule accepted by City shall be the basis for determining the amount of each progress payment. 6. Should the Contractor elect to submit a resource and cost loaded schedule, the requirements of Paragraphs 1. through 5. Above shall apply to the resource and cost loaded schedule. E. If the Progress Schedule reflects completion date(s) different than the Contract Times, the Contract Times are not thereby voided, nullified, or affected. The Contract Times govern. Where the Progress Schedule reflects completion date(s) that are earlier than the Contract Times, City may accept such Progress Schedule with Contractor to specifically understand that no Claim for additional Contract Times or additions to the Contract Price shall be brought against City resulting from Contractor's failure to complete the Work by the earlier date(s) indicated on the accepted Progress Schedule. CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 0132 16 Progress Schedule Page 6 of 10 1.6 PROGRESS SCHEDULE UPDATES A. Updates: 1. Update the Progress Schedule each month. If during progress of the Work events develop that necessitate changes in the Baseline Progress Schedule (Rev.0), identify updated Progress Schedules sequentially as Progress Schedule Revision 1, 2, 3, and continuing in sequence as required. Number the Progress Schedule submittals in accordance with Section 01 33 00 — Submittal Procedures. 2. Contractor's Progress Schedule update shall include a narrative report in accordance with this Section. Narrative report shall include description of current progress and status of each Area of the Project, a description of progress for the period, a description of the Critical Path, a discussion of current or potential delays, Change Orders (pending and approved in since the previous Progress Schedule update), and other problems associated with maintaining the Work on schedule. 3. The update to the Progress Schedule shall be based on retained logic. Progress override logic is not allowed. 4. Required scheduling software, and schedule organization, format, and content for updated Progress Schedules are identical to that required in this Section for initial Progress Schedules. 5. Submit updated Progress Schedule, together with Network Diagram (when required), reports, and other schedule -related documents required to accompany the updated Progress Schedule, in accordance with Section 01 3126 — Electronic Communication Protocols, and Section 01 33 00 — Submittal Procedures. Also submit updated Progress Schedule in its native format generated by the scheduling software, transmitted using the transmission method indicated in Section 01 31 26 — Electronic Communication Protocols. 6. Submit updated Network Diagrams when revisions are proposed to the logic. Indicate in the narrative report delays that have occurred since the previous updated Progress Schedule. City will not recommend payment by City of progress payments until updated Progress Schedule is received, reviewed, and accepted by City. Payment for out -of -sequence Work is not allowed. B. Monthly Schedule Meeting: 1. During the month, utilizing the previous month's 60-day look -ahead schedule. Contractor shall record the percent complete, start and finish dates of each scheduled Activity with the remaining duration for each Activity started but not completed, including Activities associated with procurement of materials and equipment. 2. On the duration and date accepted by the City, at least one week prior to a progress meeting, Contractor, Progress Schedule preparer, City, and others as appropriate shall meet at the respective Water Treatment facility to review the design and update the schedule and progress information during the month. After acceptance of Contractor's updated data, Progress Schedule preparer shall use this information to update the Progress Schedule. 3. On the same day each month, at least one week prior to a progress meeting, Contractor, Progress Schedule preparer, City, and others as appropriate shall meet at the Site and tour the Work to review and update the schedule and progress information gathered by Contractor during the month. After acceptance of Contractor's updated data, Progress Schedule preparer shall use this information to update the Progress Schedule. CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 0132 16 Progress Schedule Page 7 of 10 1.7 NETWORK DIAGRAMS (PERT CHARTS) A. Network Diagrams may be requested by the City if certain scheduled activities or sequence of activities need more clarify or explanation, or if it is not clear activities can be performed as noted, or if other factors influence the schedule to the point that renders portions of it difficult to understand, or as a part of a Recovery Schedule. The network diagrams will be requested so the Contractor can clearly communicate his intentions with respect to the schedule, and to assist the project team in understanding what is being presented. A. Network Diagrams, General: 1. If directed by City, prepare, and submit Network Diagrams, as generated using the scheduling software on paper of the size indicated for Progress Schedules in this Section. 2. Group Network Diagrams by Facility, Design, Construction, Area and show the order and interdependence of Activities and sequence and quantities in which the Work will be accomplished. 3. Do not use match lines on Network Diagrams. Depict interrelationships to or from Activities outside the Area shown using an Activity symbol with Activity number and description. 4. In preparing Network Diagrams, comply with the basic concept of precedence diagramming method (PDM) network scheduling to show how start of a given Activity depends on completion of preceding Activities, and how the Activity's completion may affect the start of subsequent Activities. 5. Level of schedule detail shall define the day-to-day Activities of the Work. C. Network Diagram Content: 1. Clearly indicate the Critical Path and distinguish the Critical Path from other paths on the network. 2. Organize Network Diagrams by grouping into major Work Areas, including one for each facility design, procurement of materials and equipment, and by specific Construction Activity within each Area. 3. Logic diagrams shall include the following: a. Activity number. b. Activity description. C. Activity duration (in work days). d. Critical Path denoted. e. Float for each Activity. £ Activity or System designation. g. Coded Area designation. h. Responsibility code (e.g., Contractor, trade, operation, Suppliers, or other entity responsible for accomplishing an Activity). i. Shift number (if more than one shift per day is to be employed). D. Network Diagram Revisions: 1. General: a. When conditions develop that require revisions to logic or durations of the Network Diagram associated with the Baseline Progress Schedule, identify updates to the Network Diagram in the same manner required in this Section for Progress Schedule updates. b. Revision of the logic or durations from the Baseline Progress Schedule shall be submitted to City for acceptance. CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 0132 16 Progress Schedule Page 8 of 10 C. Incorporate into the Progress Schedule revisions to logic or duration accepted by City and include in monthly narrative report both a description of revisions and listing of Activities affected by revisions. d. Changes resulting from Change Orders and other additions or deletions, shall be fully incorporated into the Progress Schedule and Network Diagram on the first update after the associated Change Order is approved by City, including adjustments to the Contract Price. 2. If directed by the City to provide, submit revised Network Diagrams with updated Progress Schedule submittals. 1.8 NARRATIVE REPORT A. Prepare and include with the preliminary Progress Schedule and each subsequent Progress Schedule submittal, written narrative report describing the schedule -related requirements of the Contract Documents and Contractor's plan and schedule for complying with such requirements. Narrative report shall describe the methods of sequencing and operation, resources to be employed, time frames for the design, design reviews, all workshops, construction of each of the major Systems on the Project, and time frames for complying with the Contract Times and Contractor's interim schedule milestones. 1.9 RECOVERY SCHEDULES A. Recovery Schedules, General: 1. When updated Progress Schedule indicates that the ability to comply with the Contract Times falls 30 or more days behind schedule, and there is no excusable delay, Change Order, or Work Change Directive to support an extension of the Contract Times, the Contractor shall prepare and submit a Progress Schedule demonstrating the Contractor's plan to accelerate the Work to achieve compliance with the Contract Times ("recovery schedule") for City's acceptance. 2. Submit recovery schedule within 10 days after submittal of updated Progress Schedule where need for recovery schedule is indicated. B. Implementation of Recovery Schedule: 1. At no additional cost to City, do one or more of the following: furnish additional labor, provide additional construction equipment, provide suitable materials, employ additional work shifts, expedite procurement of materials and equipment to be incorporated into the Work, and other measures necessary to complete the Work within the Contract Times. 2. Upon acceptance of recovery schedule by City incorporate recovery schedule into the next Progress Schedule update. C. Lack of Action: Contractor's refusal, failure, or neglect to take appropriate recovery action, or to submit a recovery schedule, shall constitute reasonable evidence that the Contractor is not prosecuting the Work or separable part thereof with the diligence that will ensure completion within the Contract Times. Such lack of action shall constitute sufficient basis for City to exercise remedies available to City under the Contract Documents. PART 2 — PRODUCTS (NOT USED) CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 0132 16 Progress Schedule Page 9 of 10 PART 3 - EXECUTION (NOT USED) ++ END OF SECTION ++ CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 0132 16 Progress Schedule Page 10 of 10 ++THIS PAGE INTENTIONALLY LEFT BLANK++ CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 SECTION 01 33 00 f. :"", :Z0Zygobill .910 PART 1 — GENERAL 1.1 DESCRIPTION A. Scope: 01 33 00 SUBMITTAL PROCEDURES Page 1 of 12 1. Contractor shall provide submittals in accordance with this Section and other applicable provisions of the Contract Documents. 2. The City will perform reviews or delegate tasks to the Engineer or other reviewers listed in TABLE 01 33 00-A. 3. For all types of submittals, both Design and non -Design submittals, and resubmittals, allocate a minimum of 30 days' time for City's review from the date of receipt by the City. 4. Shop drawings and other construction related submittals requiring City's approval prior to precuring material, equipment, or procedure (as applicable), provide ample time required for submittal review process, delivery of material or equipment and to implement procedures following City's approval or acceptance of the associated submittal. Work covered by a submittal will not be included in progress payments until approval or acceptance of related submittals has been obtained in accordance with the Contract Documents. 5. Contractor is responsible for dimensions to be confirmed and corrected at the Site, for information pertaining solely to the fabrication processes and to techniques of construction, and for coordinating the work of all trades. 6. Contractor's signature of submittal's stamp and letter of transmittal shall be Contractor's representation that Contractor has complied with his obligations under the Contract Documents relative to that submittal. The City shall be entitled to rely on such representations by Contractor. 7. Provisions of the Contract Documents apply to all Contractor furnished submittals required by the Contract Documents, regardless of whether such submittals are other than Shop Drawings. B. Restrictions on Quantity of Submittals and Compensation of City Expenses: 1. Contractor shall furnish required submittals with sufficient information and accuracy to obtain required approval or acceptance of submittal by City with not more than a total of three (3) submittal reviews. 2. Inclusive of the first submittal, following review and rejecting the third submittal, all subsequent reviews will be performed at times convenient to the City and at the expense of the Contractor, based on the prevailing rates of reviewers identified in TABLE 01 33 00-A, or those included in the Supplementary Conditions whichever is higher. 3. Contractor shall provide reimbursement to the City within 30 Calendar Days for all such fees invoiced by the City. 4. Total number of Contractor's submittals shall not exceed 20 percent above the total number of first-time submittals indicated in the Schedule of Submittals initially CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 01 33 00 SUBMITTAL PROCEDURES Page 2 of 12 accepted by City. 5. City will record the additional time charged by the Engineer or other reviewers identified in TABLE 01 33 00-A, to the City for reviewing submittals of Shop Drawings and other submittals and items requiring approval or acceptance, beyond the quantity indicated in Articles 1.1.B.1 and 2 of this Section, and Contractor shall reimburse the City for all charges for such time. 6. In the event that Contractor requests a substitution for an item previously submitted and approved by the City, Contractor shall reimburse City for the charges for such time as is necessary to review the material submitted unless the need for such substitution is beyond the control of Contractor. 7. City may impose set-off against amounts recommended for payment to Contractor for the costs for which Contractor is to reimburse or compensate City, in accordance with Section 00 72 00 — General Conditions and modified by Section 00 73 00 — Supplementary Conditions if so modified. 8. The need for resubmission of submittal materials shall be considered by the Contractor in completing and submitting the construction schedule. The need for resubmission of submittals, or any other delay in obtaining City's review of submittals, will not entitle the Contractor to an extension of Contract Time. C. In addition to the requirements of this Section, comply with requirements for exchange of electronic data in the following: 1. Section 0126 00 — Contract Modification Procedures. 2. Section 0129 73 — Schedule of Values. 3. Section 01 31 26 —Electronic Communications Protocols. 4. Section 0132 16 — Progress Schedule. 5. Section 0178 39 —Project Record Documents. 1.2 TYPES OF SUBMITTALS A. Provide submittals as required in the specifications. Submittal types may include: 1. Action Submittals include but are not limited to: a. Design submittals: final design documents submittal, which include documents prepared, sealed, and signed by a design professional employed by Contractor, Subcontractor, or Supplier for designing the SCADA network architecture to complete the Work. b. Shop Drawings. C. Process control descriptions prior to programmng PLC control logics. e. Human Machine Interface (HMI) graphic screen's printout in color. f. Drawings showing electric conduit and wiring In dification during construction. g. Product data. h. Testing plans, procedures, shutdown notifications/procedures, and testing limitations. 2. Informational Submittals include but are not limited to: a. Certificates. b. Sample HMI graphic screen's printouts. C. Design data not sealed and signed by a design professional retained by Contractor, Subcontractor, or Supplier. d. Supplier instructions, including installation data, and instructions for handling, starting up, and troubleshooting. CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 01 33 00 SUBMITTAL PROCEDURES Page 3 of 12 e. Source quality control submittals (other than testing plans, procedures, and testing limitations), including results of shop testing. f. Field or Site quality control submittals (other than testing plans, procedures, and testing limitations), including results of operating and acceptability tests at the Site. g. Supplier reports. h. Special procedure submittals, including health and safety plans and other procedural submittals. i. Qualifications statements. j. Administrative submittals including: 1) Progress Schedules. 2) Schedules of Submittals. 3) Schedules of Values. 4) Coordination drawings when submittal of such is required. 5) Copies of permits obtained by Contractor. 6) Field Engineering reports, survey data, and similar information. 3. Closeout Submittals include but are not limited to: a. Maintenance contracts. b. Operations and maintenance data. C. Bonds, such as maintenance bonds and bonds for a specific product or system. d. Warranty documentation. e. Record documentation. £ Final configurations of software (PLC/HMI/OIT/etc. as required) programs in formats specified. g. Software Licenses. h. User IDs and Passwords log. 4. Maintenance Material Submittals include but are not limited to: a. Spare parts. b. Extra stock materials. C. Tools. 5. When type of submittal is not specified and is not included in the list above, request an interpretation from City. The City, or if delegated the Engineer or other parry noted in TABLE 0133 00-A, will determine the type of submittal. B. Not Included in this Section: Administrative and procedural requirements for the following are covered elsewhere in the Contract Documents: 1. Requests for interpretations of the Contract Documents. 2. Change Orders, Work Change Directives, and Field Orders. 3. Applications for Payment. 4. Reports and documentation required in accordance with applicable permits 1.3 SUBMITTALS REOUIRED IN THIS SECTION A. Provide the following: 1. Schedule of Submittals: a. Timing: 1) Provide submittal within time frames specified in the Contract Documents. 2) Provide updated Schedule of Submittals with each submittal of the updated Progress Schedule. b. Content: In accordance with this Section and other applicable provisions of the Contract Documents. Requirements for content of preliminary Schedule of CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 01 33 00 SUBMITTAL PROCEDURES Page 4 of 12 Submittals and subsequent submittals of the Schedule of Submittals are identical. Identify on Schedule of Submittals all submittals required in the Contract Documents. Updates of Schedule of Submittals shall show scheduled dates and actual dates for completed tasks. Indicate submittals that are on the Project's critical path. Indicate the following for each submittal: 1) Date by which each submittal required by the Contract Documents will be provided to City. 2) Date by which City's response is required. At least 21 days shall be allowed from Date by which submittal will be provided to City's receipt of each submittal. Allow increased time for large or complex submittals. C. Prepare Schedule of Submittals using same software, and in same format, specified for Progress Schedules. d. Coordinate Schedule of Submittals with the Progress Schedule. e. Schedule of Submittals that is not compatible with the Progress Schedule, or that does not indicate submittals on the Project's critical path, or that places extraordinary demands on City for time and resources, is unacceptable. Do not include submittals not required by the Contract Documents. f. In preparing Schedule of Submittals: 1) Considering the nature and complexity of each submittal, allow sufficient time for review and revision. 2) Reasonable time shall be allowed for: City's review and processing of submittals, for submittals to be revised and resubmitted, and for returning submittals to Contractor. 3) Identify and accordingly schedule submittals that are expected to have long anticipated review times. 1.4 PROCEDURE FOR SUBMITTALS A. Submittal Identification System: Use the following submittal identification system, consisting of submittal number and review cycle number. 1. Submittal Number: Shall be separate and unique 9-character submittal cross- reference identification numbering system in the following manner: a. Use the first 6 digits of the applicable Specification Section Number. b. For the next 2 digits number use numbers 01-99 to sequentially number each initial separate item or drawing submitted under each specific Section number. c. The final digit shall be a Review Cycle Number. indicating the initial submittal or re -submittal associated with each submittal number: 1) "A" = Initial (first) submittal. 2) "B" = Second submittal (e.g., first re -submittal). 3) "C" = Third submittal (e.g., second re -submittal). d. Typical submittal number for the first review of the third submittal required by Section 40 61 13 — SCADA System General Provisions, would be "40 61 13-003-A". B. Letter of Transmittal for Submittals: 1. Provide separate letter of transmittal with each submittal. 2. At beginning of each letter of transmittal, provide a reference heading indicating: Contractor's name, City's name, Project name, Contract name and number, transmittal number, and submittal number. Transmittal number shall be a three -digit number (sequentially numbered from 001 through 999) assigned to cover all required submittals for the project CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 01 33 00 SUBMITTAL PROCEDURES Page 5 of 12 3. The first 100 numbers of the transmittal numbering shall be assigned to design submittals. 4. For submittals with proposed deviations from requirements of the Contract Documents, letter of transmittal shall specifically describe each proposed variation. a. The letter shall be part of the submittal, incorporated as Page 1 following the cover sheet with Contractor's Review notation and Stamp. b. If there is more than one deviation the Contractor shall number the deviations noted. c. Complete review of all submittal content by the Contractor is required, it is the Contractor's responsibility to identify ALL deviations whether proposed deliberately or incorporated by a failure to properly identify Contract Document requirements that are not met. C. Contractor's Review and Stamp: 1. Contractor's Review: Before transmitting submittals to City, review submittals to: a. Ensure proper coordination of the Work. b. Determine that each submittal is in accordance with Contractor's desires. C. Verify that submittal contains sufficient information for City to determine compliance with the Contract Documents. 2. Incomplete or inadequate submittals will be returned without review. a. Submittals deemed by the City to be not complete will be returned to the Contractor and will be considered "Not Approved" until resubmitted. b. The City may at its option provide a list or mark the submittal directing the Contractor to the areas that are incomplete 3. Contractor's Stamp and Signature: a. Each submittal provided shall bear Contractor's stamp of approval and signature, as evidence that submittal has been reviewed by Contractor and verified as complete and in accordance with the Contract Documents. b. Submittals without Contractor's stamp and signature will be returned without review. Signatures that appear to be computer -generated will be regarded as unsigned and the associated submittal will be returned without review. C. Contractor's stamp shall contain the following: "Project Name: Contractor's Name: Date: -------------------- Reference ------------ Transmittal No.: Submittal Title: Facility Name: Product, equipment, or material: Part No.: Model or make No.: Drawing No.: Location of Work: Submittal No. and Review Cycle: CITY OF FORT WORTH March 21, 2024 SCADA System Replacement 103086 01 33 00 SUBMITTAL PROCEDURES Page 6 of 12 Coordinated by Contractor with other Submittal Nos.: I hereby certify that the Contractor has satisfied Contractor's obligations under the Contract Documents relative to Contractor's review and approval of this submittal. Approved for Contractor by: m D. Submittal Marking and Organization: 1. Mark on each page of submittal and each individual component submitted with submittal number and applicable reference to this RFP and Design Document. 2. Arrange submittal information in same order as requirements are written in Section 2 of this RFP and Design Documents. 3. Each Shop Drawing sheet shall have title block with complete identifying information satisfactory to Engineer. 4. Package together submittals for each same Water Treatment Facility. Do not provide required information piecemeal. E. Submittal Distribution: Electronic Distribution as noted in TABLE 0133 00-A: a. Confirm development of Project directory for electronic submittals to be uploaded to the location and share system stipulated and approved by the City. b. Shop Drawings 1) Upload submittal to designated project directory and notify appropriate City representatives via email of submittal posting. 2) Hard Copies, where specifically directed by the Contract Documents: a) 3 copies for all such submittals, except provide the increased number of paper Final O&M submittals noted in Section 0178 23 — Operation and Maintenance Data. b) If Contractor requires more than 1 hard copy of Shop Drawings returned, Contractor shall submit more than the number of copies listed above. c. Product Data 1) Upload submittal to designated project directory and notify appropriate City representatives via email of submittal posting. 2) Hard Copies a) 3 copies for all submittals d. Samples 1) Distributed to the City, Engineer, or Other recipient, noted in TABLE 01 3300-A and as directed by the City. 2. Distribute reproductions of approved shop drawings and copies of approved product data and samples, where required, to the job site file and elsewhere as directed by the City. a. Provide number of copies as directed by the City but not exceeding the number previously specified. 3. Action Submittals and Informational Submittals: Furnish in accordance with Table 0133 00-A: CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 01 33 00 SUBMITTAL PROCEDURES Page 7 of 12 TABLE 0133 00-A: SUBMITTAL CONTACTS* NO. OF ADDRESS FOR CONTACT PRINTED DELIVERIES PERSON E-MAIL ADDRESS FORMAT** COPIES a. City * * * * * * E Zero b. City Offices N/A N/A 200 Texas Street Fort Worth, TX 76102 Engineer: Primary * Primary * E Zero Arcadis U.S., Inc. Secondary * Secondary 12400 Coit Road, Ste. 1200 Dallas, TX 75251 b. DESIGN Engineer: **** **** E Zero C. Other: * * * * * * E Zero * Contacts will be updated prior to Execution of the Contract Documents and subsequently by Field Order as needed during the design and construction phases ** Format: E = Electronic files, refer to Section 01 31 26 — Electronic Communication Protocols for routing *** As assigned and noted by the City in this table prior to execution **** As identified in the Proposal and noted by the Contractor in this table prior to execution or as subsequently added to the table by Field Order F. Format: 1. All submittals shall be provided in electronic form, additional printed (paper) copies shall be provided as noted in Section 01 31 26 — Electronic Communication Protocols or when required by other Contract Document provisions. 2. Fold shop drawings larger than 8 1/2 inches x 11 inches to 8 1/2 inches x 11inches. 3. Bind shop drawings and product data sheets together. 4. Order a. Cover Sheet 1) Description of Packet 2) Contractor Certification b. List of items / Table of Contents c. Product Data /Shop Drawings/Samples /Calculations G. Content: 1. The date of submission and the dates of any previous submissions 2. The Project title and number 3. Contractor identification 4. The names of: a. Contractor b. Supplier c. Manufacturer CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 01 33 00 SUBMITTAL PROCEDURES Page 8 of 12 1) Identification of the product, with the Specification Section number, page, and paragraph(s). 2) Field dimensions, clearly identified as such. 3) Relation to adjacent or critical features of the Work or materials. 4) Applicable standards, such as ASTM or Federal Specification numbers. 5) Identification by highlighting of deviations from Contract Documents. 6) Identification by highlighting of revisions on resubmittals. 7) An 8-inch x 3-inch blank space for Contractor and City stamps. Closeout Submittals: a. Provide the following Closeout Submittals: maintenance contracts; bonds for specific materials, equipment, or systems; and warranty documentation. On documents such as maintenance contracts and bonds, include on each document furnished original ("wet") signature of entity issuing said document. When original "wet" signatures are required, furnish such submittals in printed form and electronic form to City, and to other entities who has authority over the subject matter submitted under that submittal. b. Operations and Maintenance Data: Submit in accordance with Section 0178 23 — Operations and Maintenance Data. C. Record Documentation: Submit in accordance with Section 01 78 39 — Project Record Documents. d. Final Configuration Files & Software: Coordinate with City and establish the number of copies and types of file formats. At a minimum, provide copies of all files in native and PDF format (color wherever possible) on the flash drives identified in 5.e. e. For electronic submittals, as a minimum, provide three (3) flash drives of capacity sufficient to store all electronic closeout submittals. Organize the directories on the flash drives intuitively by Submittal. H. Electronic Submittals: 1. Format: Electronic files shall be in "portable document format" (.PDF). Files shall be electronically searchable. 2. Organization and Content: a. Each electronic submittal shall be one file; do not divide individual submittals into multiple files. b. When submittal is large or contains multiple parts, furnish PDF file with bookmark for each section of submittal. C. Content shall be identical to printed submittal. First page of electronic submittal shall be Contractor's letter of transmittal. 3. Quality and Legibility: Electronic submittal files shall be made from the original and shall be clear and legible. Do not submit scans of faxed copies. Electronic file shall be full size of original, printed documents. Properly orient all pages for reading on a computer screen. 4. Provide sufficient Internet service and e-mail capability for Contractor's use in transferring electronic submittals, receiving responses to electronic submittals, and associated electronic correspondence. Check not less than once per day for distribution of electronic submittals, electronic responses to submittals, and electronic correspondence related to submittals. 5. Submitting Electronic Files: a. Transmit electronic files in accordance with Section 01 3126 — Electronic Communication Protocols. CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 01 33 00 SUBMITTAL PROCEDURES Page 9 of 12 I. Distribution: 1. Distribution of City's Response via Electronic Files: Upon completion of City's review, electronic submittal response will be distributed by City to: a. Contractor. b. City. C. Engineer. d. Other, as noted in TABLE 0133 00-A. 2. Distribution of Hard Copies: In addition to providing electronic submittal responses, for submittals receiving the disposition of "Approved", "Approved as Corrected", or "Accepted" as defined in this Section, City will distribute hard copies as follows: a. City: One copy. b. Engineer: One copy (except closeout submittals and maintenance material submittals). c. Other reviewer noted in TABLE 01 33 00-A, one copy (except closeout submittals and maintenance material submittals) if review was delegated by the City. 3. City's hard copy shall be considered the document of record in the event of a dispute. 1.5 CITY REVIEW A. All submittals shall be submitted to City for review comments. The City may delegate reviews to the Engineer or other reviewers listed in TABLE 01 33 00-A. B. Timing: the review will conform to timing indicated in the Schedule of Submittals accepted by City. The Contractor may identify submittals where priority handling would assist in maintaining the schedule and in such cases the City shall take reasonable actions to expedite handling and review. C. Submittals not required in the Contract Documents will not be reviewed and will not be recorded in the submittal log. All printed copies of such submittals, if any, will be returned to Contractor. Electronic copies of such submittals, if any, will not be retained by City. D. City Marking (Coding): 1. Submittals will be returned to the Contractor marked with one of the following codes: a. Code 1 1) "NO EXCEPTIONS TAKEN" is assigned when there are no notations or comments on the submittal. a) When returned under this code the Contractor may release the equipment and/or material for manufacture. b. Code 2 1) "EXCEPTIONS NOTED". This code is assigned when a confirmation of the notations and comments IS NOT required by the Contractor. a) The Contractor may release the equipment or material for manufacture; however, all notations and comments must be incorporated into the final product. Code 3 1) "EXCEPTIONS NOTED/RESUBMIT". This combination of codes is assigned when notations and comments are extensive enough to require a resubmittal of the package. CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 01 33 00 SUBMITTAL PROCEDURES Page 10 of 12 a) The Contractor may release the equipment or material for manufacture; however, all notations and comments must be incorporated into the final product. b) This resubmittal is to address all comments, omissions and non -conforming items that were noted. c) Resubmittal is to be received by the City within 15 Calendar Days of the date of the City's transmittal requiring the resubmittal. d. Code 4 1) "NOT APPROVED" is assigned when the submittal does not meet the intent of the Contract Documents. a) The Contractor must resubmit the entire package revised to bring the submittal into conformance. b) It m y be necessary to resubmit using a different manufacturer/vendor to meet the Contract Documents. c) Note: the marking "Revise and Resubmit" is not used. All rejected submittals will be marked Code 4 and the City's exceptions will be detailed. E. Action Submittals, Results of the Review: Each submittal will be given one of the following dispositions: 1. Upon return of submittal marked "CODE 1 — NO EXCEPTIONS TAKEN": a. In the case of Design Submittals, 1) Final Design submittals will be so marked following the City's review of the Contractor's changes in response to all comments. 2) The Contractor shall subsequently start Field mobilization and construction Work. b. In the case of Construction related Submittals, upon return of submittals marked "Approved", order, ship, or fabricate materials and equipment included in the submittal (pending City's approval or acceptance, as applicable, of source quality control submittals) or otherwise proceed with the Work in accordance with the submittal and the Contract Documents. 2. Upon return of submittals marked "CODE 2: EXCEPTIONS NOTED": a. In the case of Design Submittals, 1) Intermediate design submittals, including conceptual, preliminary, and subsequent percentage completion as required by Section 40 61 13 — SCADA System General Requirements; will be so marked following the City's review. 2) The Contractor shall subsequently proceed with the scope per Section 40 61 13 — SCADA System General Requirements. b. In the case of Construction related Submittals, order, ship, or fabricate materials and equipment included in the submittal (pending City's approval or acceptance, as applicable, of source quality control submittals) or otherwise proceed with the Work in accordance with the submittal and the Contract Documents, and in accordance with the corrections indicated in the City's submittal response. 3. Upon return of submittals marked "CODE 3: EXCEPTIONS NOTED/RESUBMIT": a. Order, ship, or fabricate materials and equipment included in the submittal (pending City's approval or acceptance, as applicable, of source quality control submittals) or otherwise proceed with the Work in accordance with the submittal and the Contract Documents, and in accordance with corrections indicated in City's submittal response. b. Provide to the City record re -submittal with all corrections made as required by CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 01 33 00 SUBMITTAL PROCEDURES Page 11 of 12 this Section. Receipt of corrected re -submittal is required before materials or equipment covered in the submittal will be eligible for payment 4. Upon return of submittals marked "CODE 4: NOT APPROVED": This disposition indicates material or equipment that cannot be approved. "Not Approved" disposition may also be applied to submittals that are incomplete or those requiring major or minor modifications and re -submittal. Upon return of submittal marked "Not Approved", repeat initial submittal procedure utilizing approvable material or equipment, with a complete submittal clearly indicating all information required. Re -submittals that do not address specific exceptions noted by the City will not be reviewed. F. Informational Submittals, Results of Review: 1. Each submittal will be given one of the following dispositions: a. Acceptable Informational Submittals will be marked Code 1. This indicates that information included in submittal conforms to the applicable requirements of the Contract Documents. No further action by Contractor is required relative to this submittal, and the Work covered by the submittal may proceed, and materials and equipment with submittals with this disposition may be shipped or operated, as applicable. b. Informational Submittals that are not acceptable will be marked Code 4. This indicates that the submittal does not conform to applicable requirements of the Contract Documents and is not acceptable. Re -submit corrected material to indicate acceptability and conformance with the Contract Documents. G. Closeout Submittals, Results of Review: Dispositions and meanings are the same as specified for Informational Submittals. When acceptable, Closeout Submittals will not receive a written response from City beyond the marking of the specific submittals as Code 1. This disposition will be recorded in City's submittal log. When Closeout Submittal is not acceptable, Engineer will provide written response to Contractor. H. Re -submittals a. The City will handle re -submittals in the same manner as first submittals 1) Corrections made in response to exceptions (comments) made by the City shall be marked with a revision triangle or other similar method approved by the City. 2) Corrections to areas not marked by the City may be made at the option of the Contractor. Such corrections, if not clearly marked with a revision triangle or other similar method approved by the City, are made "at risk" with the Contractor retaining all responsibilities for the completed work meeting all Contract Document requirements b. Re -submittals for each item will be reviewed no more than twice at City expense in accordance with Paragraph 1.1 B of this Section. I. Maintenance Material Submittals: Dispositions and meanings are the same as specified for Closeout Submittals in Paragraph 1.6 E above. PART 2 — PRODUCTS (NOT USED) PART 3 — EXECUTION (NOT USED) + + END OF SECTION + + CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 01 33 00 SUBMITTAL PROCEDURES Page 12 of 12 ++THIS PAGE INTENTIONALLY LEFT BLANK++ CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 01 70 00 MOBILIZATION AND REMOBILIZATION Page 1 of 4 SECTION 0170 00 MOBILIZATION AND REMOBILIZATION PART 1 - GENERAL 1.1 SUMMARY A. Section Includes: 1. Mobilization and Demobilization a. Mobilization 1) Transportation of Contractor's personnel, equipment, and operating supplies to the Sites identified in the Contract Documents. 2) Establishment of necessary general facilities for the Contractor's operation at the Site s identified in the Contract Documents. 3) Premiums paid for performance and payment bonds. 4) Transportation of Contractor's personnel, equipment, and operating supplies to another location within the designated Sites. 5) Relocation of necessary general facilities for the Contractor's operation between locations to incorporate the Work as identified in the Contract Documents. b. Demobilization 1) Transportation of Contractor's personnel, equipment, and operating supplies away from the Site s identified in the Contract Documents. including disassembly. 2) Site Clean-up. 3) Removal of all buildings and/or other facilities assembled at the Site for this Contract. c. Mobilization and Demobilization do not include activities for specific items of work that are for which payment is provided elsewhere in the contract. 2. Remobilization a. Remobilization for Suspension of Work specifically required in the Contract Documents or as required by City includes: 1) Demobilization a) Transportation of Contractor's personnel, equipment, and operating supplies from the Sites identified in the Contract Documents. including disassembly or temporarily securing equipment, supplies, and other facilities as designated by the Contract Documents necessary to suspend the Work. b) Site Clean-up as designated in the Contract Documents. 2) Remobilization a) Transportation of Contractor's personnel, equipment, and operating supplies to the Site necessary to resume the Work. b) Establishment of necessary general facilities for the Contractor's operation at the Site necessary to resume the Work. 3) No Payments will be made for: a) Mobilization, Demobilization or Remobilization from one location to another on the Site or between Sites identified in the Contract Documents in the normal progress of performing the Work. b) Stand-by or idle time CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 01 70 00 MOBILIZATION AND REMOBILIZATION Page 2 of 4 c) Lost profits 3. Mobilizations and Demobilization for Miscellaneous Projects, identified in a Change Order to Contract Documents. a. Mobilization and Demobilization 1) Mobilization shall consist of the activities and cost on a Work Order basis necessary for: a) Transportation of Contractor's personnel, equipment, and operating supplies to the Site for the issued Work Order. b) Establishment of necessary general facilities for the Contractor's operation at the Site for the issued Work Order 2) Demobilization shall consist of the activities and cost necessary for: a) Transportation of Contractor's personnel, equipment, and operating supplies from the Site including disassembly for each issued Work Order b) Site Clean-up for each issued Work Order c) Removal of all buildings or other facilities assembled at the Site for each Work Oder b. Mobilization and Demobilization do not include activities for specific items of work for which payment is provided elsewhere in the contract. 4. Emergency Mobilizations and Demobilization for Miscellaneous Projects a. A Mobilization for Miscellaneous Projects when directed by the City and the mobilization occurs within 24 hours of the issuance of the Work Order. B. Deviations from this City of Fort Worth Standard Specification 1. None. C. Related Specification Sections include, but are not necessarily limited to: 1. Division 00 — General Conditions 2. Division 01 — General Requirements 1.2 PRICE AND PAYMENT PROCEDURES A. Measurement and Payment for Mobilization and Demobilization are defined in: 1. Mobilization is limited as a percentage of the Total Amount (Base Proposal), the Contractor shall refer to Section 00 42 10 Exhibit A. Basis of payment, payment restrictions and procedures are provided in Section 01 22 13 — Measurement and Payment and Section — 0129 73 Schedule of Values. 2. Demobilization is subsidiary to all Proposal items. Payment and Section 0129 73 — Schedule of Values. Payment restrictions and procedures are provided in Section 01 29 73 — Schedule of Values. 1.3 REFERENCES [NOT USED] 1.4 ADMINISTRATIVE REOUIREMENTS [NOT USED] 1.5 SUBMITTALS [NOT USED] 1.6 INFORMATIONAL SUBMITTALS [NOT USED] 1.7 CLOSEOUT SUBMITTALS [NOT USEDI CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 01 70 00 MOBILIZATION AND REMOBILIZATION Page 3 of 4 1.8 MAINTENANCE MATERIAL SUBMITTALS FNOT USEDI 1.9 QUALITY ASSURANCE FNOT USEDI 1.10 DELIVERY, STORAGE, AND HANDLING [NOT USED] 1.11 FIELD f SITEI CONDITIONS MOT USED] 1.12 WARRANTY MOT USEDI PART 2 - PRODUCTS MOT USEDI PART 3 - EXECUTION FNOT USEDI ++ END OF SECTION ++ CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 01 70 00 MOBILIZATION AND REMOBILIZATION Page 4 of 4 THIS PAGE INTENTIONALLY LEFT BLANK CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 SECTION 0177 19 CLOSEOUT REQUIREMENTS PART 1 — GENERAL 1.1 GENERAL 01 77 19 CLOSEOUT REQUIREMENTS Page 1 of 2 A. Scope: 1. Section Includes: a. Substantial Completion. b. Final inspection. C. Request for final payment and acceptance of the Work. 1.2 SUBSTANTIAL COMPLETION A. Substantial Completion — General: 1. Procedures for requesting and documenting Substantial Completion are as noted in the General Conditions. 2. When the Work has progressed to meet the definition of Substantial Completion in the General Conditions, the Contractor shall notify the City in accordance with Article 14.05 of the General Conditions. Where required by the Contract Documents the Contractor may notify the City that a portion of the Work is substantially complete subject to Partial Utilization provisions noted in Article 14.04 of the General Conditions. 3. Prior to notifying the City that any portion of the Work has progress to meet the definition of Substantial Completion in the General Conditions, the Contractor shall perform the following for the substantially completed Work: a. Materials, Equipment, and Work for which Final Inspection is requested shall be fully ready for their intended use, including operating and monitoring capability in automatic and manual modes that are shown and described in the Design Documents. b. Complete field quality control Work, including testing at the Site, which are shown and described in the Contract Documents for individual materials and equipment items. Submit results of and obtain the City's acceptance of field quality control tests required by the Contract Documents. C. Startup and checkout shall be completed in accordance with Section 40 6123 — SCADA System Startup and Field Testing. d. Training shall be completed in accordance with Section 40 6126 — SCADA System Training. e. Submit and obtain City's acceptance of final operations and maintenance manuals. f. Complete other tasks that the Contract Documents require be completed prior to Final Acceptance of the Work. 4. Refer to the Contract Documents for requirements regarding consent of surety to partial release of or reduction in retainage. 1.3 FINAL INSPECTION A. Final Inspection — General: CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 01 77 19 CLOSEOUT REQUIREMENTS Page 2 of 2 1. Prior to requesting final inspection, verify that all of the Work is fully complete and ready for final payment. 2. The procedures for requesting Final Inspection and documenting Substantial Completion are as noted in Article 14.05 of the General Conditions. 1.4 REQUEST FOR FINAL PAYMENT AND ACCEPTANCE OF THE WORK A. Procedure: 1. After Contractor has completed all corrections identified during the final inspection to the satisfaction of the City and delivered in accordance with the Contract Documents all maintenance and operating instructions, schedules, guarantees, bonds, certificates or other evidence of insurance, certificates of inspection, annotated record documents, and other documents, the Contractor may make application for final payment following the procedure for progress payments. 2. The procedures for requesting Final Payment are as noted in Article 14.07 of the General Conditions, and as further detailed by payment provisions detailed in Division 01. B. Acceptance of the Work: 1. The City will notify the Contractor of the acceptance of the Work as noted in Article 14.05 of the General Conditions. 2. Nothing other than receipt of such notice of acceptability from City constitutes acceptance of the Work. C. Request for final payment shall meet all requirements noted in the General Conditions and include: 1. Documents identified in Article 1.4.A of this Section. 2. List of all disputes that Contractor believes are unsettled. 3. Consent of Surety to Final Payment, using the form included in the Agreement. 4. Releases or Waivers of Lien Rights: a. Contractor's Affidavit of Release of Liens. b. Release or waiver of Lien may be conditional upon receipt of Final Payment. 5. Contractor's Affidavit of Payment of Debts and Claims. 6. Evidence satisfactory to City that all title issues have been resolved such that title to all Work, materials, software licenses, and equipment has passed to City free and clear of Liens or other title defects or will so pass upon final payment. PART 2 — PRODUCTS (NOT USED) PART 3 — EXECUTION (NOT USED) + + END OF SECTION + + CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 01 78 23 OPERATIONS AND MAINTENANCE DATA Page 1 of 6 SECTION 0178 23 ,� ' ::11�1 [�7�[.y: ►��I��uI: 1� ►11M�121:W[414M'Wal PART 1 — GENERAL 1.1 DESCRIPTION A. Scope: 1. This Section describes requirements for operations and maintenance manuals and related data to be furnished by Contractor. 2. Contractor shall submit operation and maintenance data, in accordance with this Section and in accordance with requirements elsewhere in the Contract Documents, as instructional and reference manuals for use by operations and maintenance personnel at the Site. 3. Required operation and maintenance data groupings are listed below. At minimum, submit operation and maintenance data for: a. Water Treatment Plant (WTP) SCADA Systems and SCADA Architecture b. Centralized SCADA System including the data interface, reporting, remote alarm notification and tablets. 4. For each operation and maintenance manual, submit the following: a. Preliminary Submittal: Printed and bound copy, and electronic copies of entire operation and maintenance manual, except for test data and service reports by Supplier. b. Final Submittal: Printed and bound copy, and electronic copies of complete operations and maintenance manual, including test data and service reports by Supplier. 1.2 SUBMITTALS A. Closeout Submittals: Submit the following: 1. Operation and Maintenance Data: a. Submit the operations and maintenance data indicated in the Contract Documents, organized into groups, clearly labeled with the name of the Water Treatment Facility. B. Quantity Required and Timing of Submittals: 1. Preliminary Submittal: a. Printed Copies: Six copies, exclusive of copies required by Contractor and copies kept in panels at the Site. b. Electronic Copies: In accordance with Section 01 3126 — Electronic Communication Protocols. C. Submit to City by the earlier of 90 days following acceptance of final Operational Availability Demonstration, or 30 days prior to starting final training of operations and maintenance personnel. 2. Final Submittal: Provide final submittal prior to Substantial Completion unless submittal is identified in coordination meetings or workshops during design phase as required prior to an interim Milestone. a. Printed Copies: Six copies. b. Electronic Copies: In accordance with Section 01 3126 — Electronic CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 01 78 23 OPERATIONS AND MAINTENANCE DATA Page 2 of 6 Communication Protocols. 1.3 FORMAT OF PRINTED COPIES A. Binding and Cover: 1. Bind each operation and maintenance manual in durable, permanent, stiff -cover binder(s), comprising one or more volumes per copy as required. Binders shall be minimum one inch wide and maximum of three inches wide. Binders for each copy of each volume shall be identical. 2. Binders shall be locking three-ring/ "D"-ring type, or three -post type. Three-ring binders shall be riveted to back cover and include plastic sheet lifter (page guard) at front of each volume. 3. Do not overfill binders. 4. Covers shall be oil-, moisture-, and wear -resistant, including identifying information on cover and spine of each volume. 5. Provide the following information on cover of each volume: a. Title: "OPERATING AND MAINTENANCE INSTRUCTIONS". b. Name or type of material or equipment covered in the manual. C. Volume number, if more than one volume is required, listed as "Volume _ of _", with appropriate volume -designating numbers filled in. d. Name of Project and, if applicable, Contract name and number. e. Name of Water Treatment Plant, building or structure, as applicable. 6. Provide the following information on spine of each volume: a. Title: "OPERATING AND MAINTENANCE INSTRUCTIONS". b. Name or type of material or equipment covered in the manual. C. Volume number, if more than one volume is required, listed as "Volume _ of ", with appropriate volume -designating numbers filled in. d. Project name and Water Treatment Plant, building or structure name as applicable. B. Pages: 1. Print pages in operations and maintenance manual on 30-pound (minimum) paper, 8.5 inches by 11 inches in size and for schematics, on 30-pound (minimum) paper, 11 inches by 17 inches in size folded to 8.5 inches by 11 inches. 2. Reinforce binding holes in each individual sheet with plastic, cloth, or metal. When published, separately bound booklets or pamphlets are part of the manual, reinforcing of pages within booklet or pamphlet is not required. 3. Provide each page with binding margin not less than one inch wide. Punch each page with holes suitable for the associated binding. CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 01 78 23 OPERATIONS AND MAINTENANCE DATA Page 3 of 6 C. Drawings: 1. Bind into the operation and maintenance manual drawings, diagrams, and illustrations up to and including 11 inches by 17 inches in size, with reinforcing specified for pages. 2. Documents larger than I I inches by 17 inches shall be folded and inserted into clear plastic pockets bound into the manual. Mark pockets with printed text indicating content and drawing numbers. Include not more than three drawing sheets per pocket. D. Copy Quality and Document Clarity: 1. Contents shall be original -quality copies. Documents in the operations and maintenance manual shall be either original manufacturer -printed documents or first - generation photocopies indistinguishable from originals. If original is in color, copies shall be in color. Manuals that contain copies that are unclear, not completely legible, off -center, skewed, or where text or drawings are cut by binding holes, are unacceptable. Pages that contain approval or date stamps, comments, or other markings that cover text or drawing are unacceptable. Faxed copies are unacceptable. 2. Clearly mark in ink to indicate all components of materials and equipment on catalog pages for ease of identification. In standard or pre-printed documents, indicate options furnished or cross out inapplicable content. Using highlighters to so indicate options furnished is unacceptable. E. Organization: 1. Coordinate with City to develop comprehensive, practical, and consistent indexing system for operations and maintenance data. The City will review indexing system before operations and maintenance data is submitted. 2. Table of Contents: a. Provide table of contents in each volume of each operation and maintenance manual. b. In table of contents and not less than once in each chapter or section, identify materials and equipment by their functional names. Thereafter, abbreviations and acronyms may be used if their meaning is clearly indicated in a table bound at or near beginning of each volume. Using material or equipment model or catalog designations for identification is unacceptable. 3. Use dividers and indexed tabs between major categories of information, such as operating instructions, preventive maintenance instructions, and other major subdivisions of data in each manual. 1.4 FORMAT OF ELECTRONIC COPIES A. Electronic Copies of Operation and Maintenance Manuals: 1. Each electronic copy shall include all information included in the corresponding printed copy. 2. Submit electronic copies in accordance with Section 01 3126 — Electronic Communication Protocols. 3. File Format: a. Files shall be in "portable document format" (PDF). Files shall be electronically searchable. b. Submit separate file for each separate document in the printed copy. C. Within each file, provide bookmarks for the following: 1) Each chapter and subsection listed in the corresponding printed copy document's table of contents. CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 01 78 23 OPERATIONS AND MAINTENANCE DATA Page 4 of 6 2) Each figure. 3) Each table. 4) Each appendix. B. Copies of Programming and Configuration Files: 1. Furnish on both portable USB "thumb drive" and solid-state hard drives copy of all software programming, such as programmable logic controller programs, prepared specifically for the Project. Third -parry, licensed, commercially available software such as Microsoft Excel, is excluded from requirements of this Article; submit copies of commercially available, licensed, third -party software, where required, in accordance with the Contract Documents. 2. Submit on portable USB "thumb drive" and solid-state hard drives copies of configured human machine interface (HMI) software and historian software prepared specifically for the Project, such as plant monitoring and control system and/or SCADA display configurations. 3. In addition to USB "thumb drive" and solid-state hard drives, copies of both PLC programs, HMI configuration, and historian software shall be loaded onto the backup computers assigned at each facility. 4. Submit programming and configuration files concurrently with electronic copies of operation and maintenance data. 1.5 CONTENT A. General: 1. Prepare each operation and maintenance manual specifically for the Project. 2. Completeness and Accuracy: a. Operation and maintenance manuals that include language stating or implying that the manual's content may be insufficient or stating that the manual's content is not guaranteed to be complete and accurate are unacceptable. b. Operations and maintenance manuals shall be complete and accurate. 3. Submit complete, detailed written operating instructions for each SCADA system item including function; operating characteristics; limiting conditions; operating instructions for start-up, normal and emergency conditions; regulation and control; operational troubleshooting; and shutdown. Also include, as applicable, written descriptions of alarms generated by equipment and proper responses to such alarm conditions. B. Submit written explanations of all safety considerations relating to operation and maintenance procedures. C. Submit complete, detailed, written preventive maintenance instructions including all information and instructions to keep the SCADA systems properly adjusted, and maintained so that materials, equipment, and systems function economically throughout their expected service life. Instructions shall include: 1. Written explanations with illustrations for each preventive maintenance task such as inspection, adjustment, calibration, and cleaning. 2. Recommended schedule for each preventive maintenance task. 3. Troubleshooting instructions. 4. List of required maintenance tools and equipment. CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 01 78 23 OPERATIONS AND MAINTENANCE DATA Page 5 of 6 D. Submit the following minimum O&Ms: 1. WTP SCADA System O&M (typical for all 5 Water Treatment Plants). For each plant, provide in an organized fashion as identified herein, the following: a. Table of Contents b. System Overview C. Final WTP SCADA Architecture detailed diagram d. Final Control Narratives e. Final Copies of Configurations f. Graphical User Manual, showing all SCADA screens including all Tier I,11,111 and IV screens, and identifying in detail what monitoring, alarm and control functions are available on each. g. Printout of HMI Database, Driver Configuration Files and/or OPC database as applicable. h. List of all alarms and initial settings for the SCADA system. i. List of all points historically archived. j. Procedures for starting, stopping, restoring, and restarting a SCADA workstation. k. Standard troubleshooting procedures. 1. Copy of respective Training Manuals and Courses. in. Electronic copies of all configuration files for all WTP configuration work. 2. Centralized SCADA System O&M inclusive of Data Interface, Reporting, Tablets and Remote Alarm Notification. a. Table of Contents b. System Overview of each component: Data Interface, Reporting, Tablet setup and Remote Alarm Notification. C. Final Centralized SCADA Architecture detailed diagram d. Final Copies of Configurations e. Centralized SCADA graphical user manual, showing all SCADA Reports and identifying data sources and points for each. f. Printout of HMI Database, Driver Configuration Files and/or OPC database as applicable. g. List of all alarms included in remote notification and rules. h. Copy of respective Training Manuals and Courses. i. Standard troubleshooting procedures. k. Electronic copies of all reports, database and associated files for all Centralized SCADA configuration work. I. For each Water Treatment Plant SCADA O&M, Programmable Logic Controller programs: 1. Submit all PLC programs in accordance with the requirements specified in Section 40 68 63 — SCADA System Programming and Configuration. 2. Submit complete programmable logic controller listing of all input/output address assignments, tag assignments, and pre-set constant values, with functional point descriptions. 3. Submit complete manufacturer's programming manuals. Submit copy of warranty bond and service contract as applicable. K. When copyrighted material is used in operations and maintenance manuals, obtain copyright holder's written permission to use such material in the operation and maintenance manual. CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 01 78 23 OPERATIONS AND MAINTENANCE DATA Page 6 of 6 PART 2 - PRODUCTS (NOT USED) PART 3 - EXECUTION (NOT USED) + + END OF SECTION + + CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 SECTION 0178 36 PART 1 — GENERAL 1.1 DESCRIPTION 01 78 36 WARRANTIES Page 1 of 4 A. Scope: 1. This section describes general warranty requirements for material, equipment, and work described in other sections of this contract. 2. Key items included in this section are the general requirements for: a. Contractor's general warranty and guarantee. b. Contract correction period. C. Suppliers' standard Warranties. d. Suppliers' special Warranties. e. Implied Warranties. f. Commencement and duration of warranties. 1.2 SUBMITTALS A. General: 1. Submit Standard Warranties as submittals in accordance with Schedule of Submittals accepted by the City. B. Schedule of Warranties: The Contractor shall provide a list noting the start of Standard Warranty Correction Periods for all portions of the Work used or occupied by the City in accordance with Article 1.6 A. 4. of this Section. The schedule of dates will be updated by the Contractor throughout the completion of the Work concluding with the date of Final Acceptance of portions of the Work not identified as occupied or used by the City in advance of that date. 1.3 CONTRACTOR'S GENERAL WARRANTY AND GUARANTEE A. Contractor warrants and guarantees to City that all Work will be in accordance with the Contract Documents and will not be defective. Contractor's warranty and guarantee hereunder excludes defects or damage caused by: 1. Abuse, modification, or improper maintenance or operation by persons other than Contractor, Subcontractors or Suppliers. 2. Normal wear and tear under normal usage. B. Contractor's obligation to perform and complete the Work in accordance with the Contract Documents shall be absolute. No action defined in Article 6.20 C of Section 00 72 00 — General Conditions will constitute an acceptance of Work that is not in accordance with the Contract Documents or a release of Contractor's obligation to perform the Work in accordance with the Contract Documents. C. Correction Period: CITY OF FORT WORTH March 21, 2024 SCADA System Replacement 103086 01 78 36 WARRANTIES Page 2 of 4 1. If within the period after the date of Final Acceptance noted in Article 13.07 of the General Conditions; or such longer period of time as may be prescribed by Laws or Regulations or by the terms of any applicable special guarantee required by the Contract Documents or by any specific provision of the Contract Documents, any Work is found to be defective the Contractor shall promptly, without cost to City and in accordance with City's written instructions: a. Correct such defective Work, or, if it has been rejected by City, remove it from the site and replace it with Work that is not defective. b. Satisfactorily correct or remove and replace any damage to other Work or the work of others resulting therefrom. 2. The duration of correction period for configuration work directed by Section 40 68 63 — SCADA System Programming and Configuration, and all other portions of the Work not subject to Special Warranty requirement below, shall begin upon final acceptance by the City of all Work required by the Contract Documents. 3. Hardware and Software purchased by the City shall be excluded from warranty under the Agreement. 4. Warranty and Special Guarantee durations for specified portions of the Work are summarized in TABLE 0178 36 — A. TABLE 01 78 36 — A SUMMARY OF WARRANTY DURATION Work Specification Applicable Period' Section(s) (Years) Configuration Division 40 2 Computer and PLC None None Hardware 2 Warranty Computer and PLC Software None None 3 Warranty SCADA Software 4 None None Notes: 1. The summary of durations, after Final Acceptance, is provided subject to the requirements noted in Article 1.3 C. I above. 2. Computer and PLC hardware shall be procured by the City. However, selected maintenance shall be provided by the Contractor as noted in Section 01 1416 — Coordination with Owner's Operations and CSP Documents. 3. Computer and PLC Software is procured by the City. However, selected maintenance shall be provided by the Contractor as noted in Section 01 1416 — Coordination with Owner's Operations and CSP Documents. 4. Ignition SCADA Software pre -purchased by the City. However, selected maintenance shall be provided by the Contractor as noted in Section 01 14 16 — Coordination with Owner's Operations and CSP Documents. 6. If Contractor does not promptly comply with the terms of such instructions, or in an emergency where delay would cause serious risk of loss or damage, City may have the defective Work corrected or the rejected Work removed and replaced, and all claims, costs, losses, and damages caused by or resulting from such removal and replacement (including but not limited to all costs of repair or replacement of work of others) shall be paid by Contractor. 7. In special circumstances where a particular item or equipment is placed in continuous service before Substantial Completion of all the Work, in accordance with Partial CITY OF FORT WORTH March 21, 2024 SCADA System Replacement 103086 01 78 36 WARRANTIES Page 3 of 4 Utilization as noted in Article 14.04 of the General Conditions, the correction period for that item shall start from Final Acceptance of ALL Work. Earlier dates, if so, agreed between City and Contractor during design phase, shall be used in incorporated by Change Order. Failure to approve proposals associated with warranty effective dates shall not entitle the Contractor to additional compensation. Where defective Work (and damage to other Work resulting therefrom) has been corrected, removed, or replaced during the correction period, the correction period hereunder with respect to such Work will be extended for an additional period of one year after such correction or removal and replacement has been satisfactorily completed. 1.4 IMPLIED WARRANTIES A. Warranty of Title and Intellectual Rights: 1. Except as may be otherwise indicated in the Contract Documents, implied warranty of title required by Laws and Regulations is applicable to the Work and to materials and equipment incorporated therein. B. Warranty of Merchantability: 1. Notwithstanding any other provision of the Contract to the contrary, implied warranties of merchantability required by Laws and Regulations apply to the Work. C. Warranty of Fitness -for -Purpose: 1. Implied warranty of fitness -for -purpose for materials and equipment to be incorporated into the Work is hereby disclaimed by City and Contractor. 2. When Contractor is aware of, or has reason to be aware of, materials, equipment or features of the Work shown or described in the Contract Documents that are contrary to the intended use, purpose, service, application, or environment in which the material or equipment item will be used, notify City. Resolution of the issue will be managed by City and resolved by Contractor. Where appropriate, such notification(s) shall indicate the apparent discrepancy and propose appropriate, alternative materials or equipment. 1.5 COMMENCEMENT AND DURATION OF WARRANTIES A. Commencement of Warranties: 1. Contract correction period and CONTRACTOR'S general warranty commence as indicated in Article 13.07 of the General Conditions. 2. Implied warranties commence in accordance with Laws and Regulations. 4. The Contractor shall base the Proposal on the commencement of all warranties as noted in Article 13.07 of the General Condition as modified by the Supplementary Conditions. As noted below the start Standard Warranty Correction Periods shall be based to completion of portions of the Work the City elects to use or occupy in accordance with General Conditions Article 14.04 Partial Utilization, subject to the following requirements. a. The Work to be used or occupied by the City shall be identified in Section 00 42 10 — Proposal as ALL Work associated with a: 1) Individual Water Treatment Plant, inclusive of successful OAD. 2) Centralized SCADA and Data Interface, inclusive of successful OAD. CITY OF FORT WORTH March 21, 2024 SCADA System Replacement 103086 01 78 36 WARRANTIES Page 4 of 4 b. The Work shall be inspected as required by Article 14.04 of the General Conditions and a punch list developed for the portion of the Work identified. C. The portion of the work identified must be accepted as Substantially Complete by the City and the associated punch list completed to start the Correction Period associated with Contract Document warranty and special warranties requirements. B. Duration of Warranties: 1. Duration of CONTRACTOR'S general warranty and guarantee is defined in Section 00 72 00 — Standard General Conditions of the Construction Contract, is in accordance with Laws and Regulations. 2. Duration of Suppliers' general warranties shall be in accordance with Contract Document warranty provisions. The Contractor shall certify as such in accordance with Section 01 33 00 — Submittals in transmitting the applicable general warranty document accepted by the City. 3. Duration of implied warranties shall be in accordance with Laws and Regulations. PART 2 — PRODUCTS (NOT USED) PART 3 — EXECUTION (NOT USED) + + END OF SECTION + + CITY OF FORT WORTH March 21, 2024 SCADA System Replacement 103086 SECTION 0178 39 PROJECT RECORD DOCUMENTS PART 1 — GENERAL 1.1 DESCRIPTION 01 78 39 PROJECT RECORD DOCUMENTS Page 1 of 4 A. Scope: 1. Contractor shall provide all labor, materials, equipment, and services to maintain and submit to City Project record documents in accordance with the Contract Documents. B. Maintenance of Record Documents: 1. Maintain in Contractor's office, in clean, dry, legible condition, complete sets of the following record documents: Design Drawings, and Addenda; Shop Drawings, and other Contractor submittals, including records of panel checkout results, approved, or accepted as applicable, by City; Change Orders, Work Change Directives, Field Orders, copies of all interpretations and clarifications issued, and all other documents pertinent to the Work. 2. Provide files and racks for proper storage and easy access to record documents. File record documents in accordance with the edition of the Construction Specification Institute's MasterFormat"m used for organizing the Project Manual, unless otherwise accepted by City. 3. Promptly make record documents available for observation and review upon request of the City. 4. Do not use record documents for any purpose other than serving as Project record. Do not remove record documents from Contractor's office without City's approval. 1.2 SUBMITTALS A. Closeout Submittals: Submit the following: 1. Record Documents: a. Submit the following Project record documents: 1) Drawings. 2) Project Manual including Materials and Equipment Specifications and Addenda (bound). 3) A list of final software licenses, quantities of licenses, and version and other related details. b. Prior to readiness for final payment, submit to City one copy of Project's final record documents and obtain City's acceptance of same. Submit complete record documents; do not make partial submittals. C. Submit both printed record documents and electronic record documents, in accordance with Section 01 31 26 — Electronic Communication Protocols. d. Submit record documents with transmittal letter on Contractor letterhead in accordance with requirements in Section 01 33 00 — Submittal Procedures. 2. Certifications: a. Record documents submittal shall include certification, with original signature of official authorized to execute legal agreements on behalf of Contractor, reading as follows: CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 01 78 39 PROJECT RECORD DOCUMENTS Page 2 of 4 "[Insert Contractor's corporate name] has maintained and submitted Project record documentation in accordance with Section 01 78 39 — Project Record Documents, and other elements of Contract Documents, for the City of Fort Worth, SCADA System Replacement Project. We certify that each record document submitted is complete, accurate, and legible relative to the Work performed under our Contract, and that the record documents comply with the requirements of the Contract Documents. [Provide signature, print name, print signing party's corporate title, and date]" 1.3 RECORDING CHANGES A. Recording Changes — General: 1. At the start of the Project, label each record document to be submitted as, "PROJECT RECORD" using legible, printed letters. Letters on record copy of the Drawings shall be two inches high. 2. Keep record documents current consistent with the progress of the Work. Make entries on record documents within two days of receipt of information required to record the change. 3. Do not permanently conceal the Work until required information has been recorded for Project record documents. 4. Accuracy of record documents shall be such that future searches for items shown on the record documents may rely reasonably on information obtained from City - accepted record documents. 5. Marking of Entries: a. Use erasable, colored pencils (not ink or indelible pencil) for marking changes, revisions, additions, and deletions to record documents. b. Clearly describe the change by graphic line and make notations as required. Use straight edge to mark straight lines. Writing shall be legible and sufficiently dark to allow scanning of record documents into legible electronic files in portable document format (".PDF"). C. Date each entry on record documents. d. Indicate changes by drawing a "cloud" around the change(s) indicated. e. Mark initial revisions in red. In the event of overlapping changes, use different colors for subsequent changes. B. Drawings: 1. Record changes on copy of the Drawings. Submittal of Contractor -originated or - produced drawings as a substitute for recording changes on the Drawings is unacceptable. 2. Record changes on block diagrams, schematics, and details as required for clarity. 3. Record actual Work including: a. Changes made to SCADA Architecture Drawings. b. Changes made in accordance with Addenda, Change Orders, Work Change Directives, and Field Orders. C. Changes in details on the Drawings. Submit additional details prepared by Contractor when required to document such changes. 4. Supplemental Drawings: a. In some cases, drawings produced during construction by City or Contractor supplement the Drawings and shall be included with Project record documents CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 01 78 39 PROJECT RECORD DOCUMENTS Page 3 of 4 submitted by Contractor. Supplemental record drawings shall include drawings or sketches that are part of Change Orders, Work Change Directives, and Field Orders and that cannot be incorporated into the Drawings because of space limitations. b. Supplemental drawings submitted with record drawings shall be integrated with the Drawings and include necessary cross-references between drawings. Supplemental record drawings shall be on sheets the same size as the Drawings. C. When supplemental drawings developed by Contractor using computer -aided drafting/design (CADD) software are to be included in record drawings, submit electronic files for such drawings in accordance with Section 01 3126 — Electronic Communication Protocols, as part of record drawing submittal. Label such files, "Supplemental Record Drawings", including with Contractor's name, Project name, and Contract designation. C. Specifications and Addenda: 1. Mark each Section to record: a. Changes made by Addendum, Change Orders, Work Change Directives, and Field Orders. PART 2 — PRODUCTS (NOT USED) PART 3 — EXECUTION (NOT USED) + + END OF SECTION + + CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 01 78 39 PROJECT RECORD DOCUMENTS Page 4 of 4 ++THIS PAGE INTENTIONALLY LEFT BLANK++ CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 4061 13 SCADA SYSTEM GENERAL PROVISIONS Page 1 of 32 SECTION 40 61 13 SCADA SYSTEM GENERAL PROVISIONS PART 1 — GENERAL This subsection includes: Article Title 1.1 SCOPE 1.2 SCADA SYSTEM ARCHITECTURE DESCRIPTION 1.3 FAMILIARIZATION AND PRELIMINARY ASSESSMENT 1.4 DESIGN 1.5 PROGRAMMING AND CONFIGURATION 1.6 FACTORY ACCEPTANCE TESTING 1.7 CUTOVER, FIELD TESTING, AND START-UP 1.8 SYSTEM MAINTENANCE, FINAL ACCEPTANCE, AND WARRANTY 1.9 REFERENCES 1.10 QUALITY ASSURANCE 1.11 COORDINATION MEETINGS AND WORKSHOPS 1.12 SUBMITTALS 1.1 SCOPE A. General Description of Scope: 1. The Contractor shall provide preconstruction and construction phase services to plan, design, configure, test, place into operation, and maintain to Final Acceptance the new Water Department Supervisory Control and Data Acquisition (SCADA) system at the five Water Treatment Plants (WTPs). The Work shall also include remote alarm monitoring and notification and a system wide data interface to link historical databases from the WTPs to a Centralized SCADA system, which will be used to provide system reports, and an interface for tablet data. The work also includes a Test Bench to allow City personnel to test system behavior offline prior to enabling in the production environment. 2. Proprietary solutions, protocols and communications deviating from those identified in the Contract Documents are not acceptable. 3. The Contractor shall provide the following project services. Each item is further detailed in this section. a. Pre -Construction Services 1) Familiarization and Preliminary Assessment 2) Design b. Construction Services 1) Programming and Configuration 2) Factory Acceptance Testing 3) Cutover, Field Testing, and Start -Up 4) System Maintenance, Final Acceptance, and Warranty 4. The Water Treatment Plants included in this upgrade are the following: a. North Holly WTP 1) Existing SCADA system: HSQ Miser 2) Existing PLCs: Schneider Electric Modicon Quantum, M340 and M580. CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 1— AD4 4061 13 SCADA SYSTEM GENERAL PROVISIONS Page 2 of 32 b. South Holly WTP 1) Existing SCADA system: HSQ Miser 2) Existing PLCs: Schneider Electric Modicon Quantum, M340, and M580 c. Westside WTP 1) Existing SCADA system: HSQ Miser and FactoryTalk View SE 2) Existing PLCs: Allen Bradley ControlLogix and CompactLogix d. Eagle Mountain WTP 1) Existing SCADA system: HSQ Miser and GE Cimplicity 2) Existing PLCs: GE 90-70, RX3i, RX7i e. Rolling Hills 1) Existing SCADA system: HSQ Miser 2) Existing PLCs: Schneider Electric Modicon Quantum and M580 Project SCADA System Hardware and Software: a. The City shall furnish Inductive Automation Ignition SCADA software and licenses required for the SCADA system as specified in the Contract Documents. Refer to Attachment 2 — City -furnished SCADA Software and Licenses. b. The Contractor shall design the Water Department SCADA system architecture and specify all SCADA system hardware and software components as described in the Contract Documents and in coordination with Water IT. Refer to Article 1.2 — SCADA System Architecture Description in this section. C. The City shall procure, install, and configure the SCADA system computer and network hardware and associated software, and any other hardware required to make the SCADA system fully functional in accordance with the Contractor's design. d. The City shall procure the SQL Historian server software. The Contractor shall procure third -party SCADA communication software and any other SCADA software required for the functionality of the SCADA system as outlined in the Contract Documents and in accordance with Attachment 1 — PLC and HMI Configuration Standards. e. The Contractor shall install and configure all SCADA and PLC software and applications required for the functionality of the SCADA system as outlined in the Contract Documents and in accordance with Attachment 1 — PLC and HMI Configuration Standards. f. The City shall procure the SQL Historian server software. The Contractor shall procure the identified third -party SCADA communication software and any other SCADA software required for the functionality of the SCADA system as outlined in Contract Documents and in accordance with Attachment 1 — PLC and HMI Configuration Standards. g. The Contractor shall install and configure all SCADA and PLC software and applications required to for the functionality of the SCADA system as outlined in the Contract Documents and in accordance with Attachment 1 PLC and HMI Configuration Standards. h. Refer to Attachment 7 — SCADA Assets Responsibility Matrix for the division of work between the City and the Contractor, as it pertains to component selection, purchase, configuration, and installation of SCADA system software and hardware assets. 6. Work at the WTPs and Centralized SCADA include but is not limited to: a. Test, start-up, successfully pass respective Operational Availability Demonstration tests, and maintain to project Final Acceptance all SCADA hardware furnished by the City to implement the new SCADA system at each WTP and centralized CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 1— AD4 4061 13 SCADA SYSTEM GENERAL PROVISIONS Page 3 of 32 SCADA. It shall include High Availability (HA) SCADA and Historian servers, thin -client desktop and industrial panel mounted workstations, wall mounted SCADA monitors, and other components as specified in the contract documents, in coordination with Water IT. b. Assess, document, configure, cutover, test, start-up, successfully pass respective Operational Availability Demonstration tests, and maintain to project Final Acceptance the existing PLC systems as specified in the contract documents, in coordination with the City. Refer to Attachment 6 — Existing WTP PLC Systems Table. C. Configure, test, successfully pass respective Operational Availability Demonstration tests, and maintain to project Final Acceptance all SCADA system application software procured by the City for use on this project (Refer to Attachment 2 — City -Furnished SCADA Software and Licenses, and Attachment 7 — SCADA Assets Responsibility Matrix). All SCADA servers shall utilize virtualization software. Water IT shall furnish and configure all necessary software and licenses required at each site to enable, configure, and manage the virtual environment. Software shall include operating system software, virtual machine management software and machine image backup software. d. Configure, test, successfully pass respective Operational Availability Demonstration tests, and maintain to project Final Acceptance all local SQL Historian server software used to save SCADA data on the Local networks at each WTP, Pass -through SQL Historian, and Central SQL Historian server software. Coordinate with Water IT to schedule the database appropriately to be transferred to the SCADA SQL Pass -through and Central SQL Server. e. Configure, test, successfully pass respective Operational Availability Demonstration tests, and maintain to project Final Acceptance the SCADA application software and test PLC units to implement the new SCADA system Test Bench. The Test Bench shall be used to test the application prior to being placed in production. f. Configure, test, successfully pass respective Operational Availability Demonstration tests, and maintain to project Final Acceptance alarm notification software and hardware for the Centralized SCADA system remote notification. g. Test, successfully pass respective Operational Availability Demonstration tests, and maintain to project Final Acceptance all managed network switches and firewalls as agreed during the Design phase. Coordinate all configuration of switches and firewalls with Water IT. h. Test, successfully pass respective Operational Availability Demonstration tests, and maintain to project Final Acceptance all software and hardware related to the domain controllers and Multi -Factor Authentication at each WTP, and the SCADA Support Server as agreed during the Design phase. Coordinate all configurations with Water IT. i. Test, successfully pass respective Operational Availability Demonstration tests, and maintain to project Final Acceptance all software and databases related to production of the entire system SCADA data interface, including the data warehouse interface for all systems as identified, custom interfaces between Centralized SCADA and LIMS and Ovation, tablets and tablet interface at Centralized SCADA, reports at Centralized SCADA and local WTP. Coordinate all configurations with Water IT. Work includes minimum items listed below with associated work defined herein and in Section 40 68 63 SCADA System Programming and Configuration: CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 1— AD4 4061 13 SCADA SYSTEM GENERAL PROVISIONS 1) Historian databases system -wide including Historian, Centralized SCADA 2) Centralized SCADA system 3) Data Warehouse Interface 4) Custom data source interfaces (LIMB, Ovation) 5) Business Reports 6) Local Plant Operational Reports 7) Remote Tablets 8) Remote Alarm Notification Page 4 of 32 at local WTPs, Pass -through B. Related Sections: 1. Section 01 11 13 —Summary of Work 2. Section 01 14 16 — Coordination with City's Operations 3. Section 40 6121 — SCADA System Factory Acceptance Testing 4. Section 40 6123 — SCADA System Field Assessment, Testing, and Start-up 5. Section 40 61 26 — SCADA System Training 6. Section 40 68 63 — SCADA System Programming and Configuration 1.2 SCADA SYSTEM ARCHITECTURE DESCRIPTION A. It is the responsibility of the Contractor, in coordination with the City, as outlined herein, to fully design the Fort Worth Water Department (FWWD) SCADA system architecture. The following is a narrative description of the general features and components that are anticipated to constitute the FWWD SCADA system architecture. B. The new FWWD SCADA architecture shall include, but not be limited to the following main components and features. Refer to Attachment 7 — SCADA Assets Responsibility Matrix for a comprehensive list of SCADA system hardware and software components to be furnished under this Contract and the respective intended service. 1. Dedicated fault tolerant WTP SCADA system servers 2. WTP SCADA thin -client desktop and industrial touchscreen workstations 3. WTP SCADA desktop and wall -mount monitors 4. Dedicated WTP SCADA Network Attached Storage (NAS) units 5. Dedicated local WTP Domain Controller (DC) servers 6. Redundant SCADA network firewall system 7. Central SCADA network industrial demilitarized zone (iDMZ) 8. iDMZ server including pass -through Historian 9. SCADA Network Time Protocol (NTP) server in iDMZ 10. Dedicated Layer-3 network switches for WTPs and iDMZ 11. SCADA Test Bench, including test server, workstation, and PLCs in iDMZ 12. Central SCADA server in IT/Enterprise network 13. Alarm notification cellular modem in iDMZ 14. Central Reporting server in IT/Enterprise network 15. Remote access to Central SCADA and Central Reporting servers 16. SCADA remote access tablets C. Dedicated SCADA system servers shall be furnished for the following WTPs. 1. South and North Holly WTPs (a common server setup for both plants) 2. Rolling Hills WTP CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 1— AD4 4061 13 SCADA SYSTEM GENERAL PROVISIONS Page 5 of 32 3. Eagle Mountain WTP 4. Westside WTP D. All SCADA system servers shall be configured for virtualization to support multiple virtual machine (VM) servers within each physical server. The following VMS shall be allocated. 1. WTP SCADA servers: a. VM1 — Management Server b. VM2 — Primary SCADA Server C. VM3 — Backup SCADA Server d. VM4 — Local SQL Historian Server 2. iDMZ server: a. VM1 — Management Server b. VM2 — SCADA Support Server C. VM3 — Domain Controller d. VM4 — SCADA SQL Pass -Through Server 3. Test Bench server: a. VM1 — Management Server b. VM2 — SCADA Server C. VM3 — Test d. VM4 — Test 4. Central SCADA server: a. VM1 — Management Server b. VM2 — Primary SCADA Server C. VM3 — Backup SCADA Server d. VM4 — Local SQL Historian Server 5. Central Reporting server: a. VM1 — Management Server b. VM2 — Central SQL Historian Server C. VM3 — Central Reporting Server E. Each WTP SCADA system shall be equipped with a "fault -tolerant' server solution designed to continue operating without interruption, even in the presence of major hardware or software failures. Fault tolerance can either be implemented through clustering of VMS across multiple physical servers within the respective virtual environments, or by utilizing physical server computers with full redundancy built into their hardware architecture. F. The City -furnished Ignition licenses support redundant configuration. If the virtual fault tolerant server solution is implemented, the Primary and Backup Ignition VMS shall be installed on different physical servers to minimize the risk of downtime in the event of a failure. G. There shall be a single/shared Industrial Demilitarized Zone (iDMZ) as opposed to a separate DMZ per treatment plant. Centralized SCADA infrastructure shall reside within the existing Enterprise/IT network. H. The WTPs shall be connected to the DMZ/City Hall Data Center via AT&T Switched Ethernet circuits (Configuration of circuits by Water IT Department). CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 1— AD4 4061 13 SCADA SYSTEM GENERAL PROVISIONS Page 6 of 32 I. The SCADA network shall be equipped with a redundant pair of firewall appliances. The WTP SCADA systems shall have dedicated zones configured in the redundant firewall system to protect each site. A separate firewall zone shall also be configured for the iDMZ. Layer-3 gateways shall be provided for each firewall zone to facilitate network segmentation and traffic inspection. Water IT shall be responsible for the configuration of the managed network switches and firewalls. The SCADA Test Bench shall mimic a typical WTP SCADA system setup as closely as possible, inclusive of components, software and connections, so that server upgrades, patches, firmware updates and other operational changes can be performed/tested/validated to verify that no impacts to the production SCADA systems could result from those changes prior to their rollout into the field. K. The local SQL Historian server at every WTP shall be configured to retain raw data for 10 years. The Centralized SQL reporting server, which will perform metrics reporting in a manner more digestible for upper management, shall retain data for 10 years. The SQL "pass - through" server shall reside within the DMZ and receive all the SQL data from the local WTP SQL servers and forward to the Centralized SQL Historian server that resides at the "Data Warehouse." SQL data from the "pass -through" SQL server will only be "pushed" from this server in order to facilitate a secure one-way flow of data towards the City's existing 'Data Warehouse". The "pass -through" SQL server will retain raw data for 3 years. The Centralized and pass -through SQL servers shall be configured by the City. L. WTP operation staff shall have remote access to the Centralized SCADA system through use of tablets via cellular communications (furnished by the City). Operators shall be allowed view - only access to the Centralized SCADA HMI application and use data entry forms to populate field -collected data to select Central SCADA reports. The tablets shall be configured to buffer/hold manual -entry data if access to the Centralized SCADA system is lost and backfill that data once connection is restored. M. SCADA User Authentication shall be handled by a centralized SCADA Active Directory with a fallback mechanism of local caching of credentials in the event that communication is disrupted. Users that will be making operational changes to the SCADA servers or environment shall be required to authenticate via Multi -Factor Authentication (MFA). MFA shall be configured in the SCADA applications. N. Communications with existing Power Monitor devices shall be over Modbus protocol. O. Communication with existing UPSs shall be over SNMP protocol. P. IP addresses of all existing PLCs in Category A defined in Attachment 6 — Existing WTP PLC Systems Table shall be changed following the City -provided IP scheme. This shall be coordinated with IP changes to the SCADA network devices. Water IT shall be responsible for configuration of all network devices. 1.3 FAMILIARIZATION AND PRELIMINARY ASSESSMENT A. General: CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 1— AD4 4061 13 SCADA SYSTEM GENERAL PROVISIONS Page 7 of 32 1. Project services in this phase include familiarization with existing Water Treatment Plant (WTP) SCADA systems, assessment of existing system conditions, review of existing software applications, and creation of as -installed Functional Control Narrative (FCN) documents. B. Key Activities: 1. To increase an understanding of the project and to facilitate implementation of the SCADA system upgrade at all WTPs, Contractor shall review available documents including but not limited to: a. Facility As -Built drawings and Operations and Maintenance (O&M) Manuals. b. PLC code. C. HMI screens and database. d. OIT Programs. e. Control strategies. £ SCADA architecture block diagram. g. PLC and HMI configuration standards. h. Reports, Data Warehouse Tables, Existing databases, and SCADA Feasibility Report. 2. Site Visits: a. Conduct site visits as needed to perform condition assessment of the existing SCADA system including but not limited to the following: 1) Plant walk-through and review of PLC/RIO/RTU panels and OIT cabinets in the field. 2) Observe HMI system performance in operation. 3) Review functionality and operation of existing reporting system. 4) Retrieve latest SCADA application files directly from the existing PLCs, OITs, and SCADA servers. b. Conduct site visits as needed to perform 1/0 loop inspections as follows: 1) Field 1/0 loop inspections shall be performed for all existing PLC systems in Category A. Refer to Attachment 6 — Existing WTP PLC Systems Table for details of PLC systems in this category. 2) I/O inspection shall be performed on the entire loop, from the field device all the way to SCADA HMI (and the local OIT, if applicable), to identify and document existing condition of respective field devices and instrumentation, field wiring connections, PLC hardware, and PLC/SCADA/OIT application programming. 3) Loop inspections and tests shall be performed using City -approved forms and checklists. 4) Comply with the requirements in Section 40 61 23 — SCADA System Field Assessment, Testing, and Start -Up. 3. Perform offline review of existing PLC and HMI applications and develop as -installed Functional Control Narrative (FCN) documents for PLC systems in Category A. Refer to Attachment 6 — Existing WTP PLC Systems Table for details of PLC systems in this category. 4. Coordination meetings and workshops: a. System Assessment Coordination Workshops. b. As -Installed Functional Control Narrative Coordination Workshops. C. Comply with the requirements in Article 1.9 Coordination Meetings and Workshops. CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 1— AD4 4061 13 SCADA SYSTEM GENERAL PROVISIONS Page 8 of 32 C. Deliverables: 1. PLC Loop Test Forms, One (1) per Category A PLC system. 2. PLC Loop Test Reports, One (1) per Category A PLC system (Draft, and Final). 3. As -Installed FCNs, One (1) per Category A PLC system or a group of related PLC systems belonging to a single process (Draft, and Final). 4. System Condition Assessment Technical Reports, One (1) for all WTPs, and one (1) for Overall SCADA system (Draft, and Final). 5. Comply with the requirements in Article 1.10, Submittals and Section 40 61 23 — SCADA System Field Assessment, Testing, and Start -Up. D. The City's Responsibilities: 1. Provide latest available SCADA system O&M documentation, software application files, databases, configuration standards, and report templates, as requested by the Contractor. 2. Coordinate access for the Contractor to perform site visits and the ability to retrieve running PLC/OIT/HMI applications to ensure working with latest files. 3. During the As -Installed Control Narrative Workshops, provide access to existing SCADA HMI workstation(s) and assist in demonstration of documented control descriptions on the live SCADA system to verify critical control loops. 4. Review Contractor's submittals and attend the required coordination workshops. E. Coordination: Coordinate site visits, meetings, and workshops with the City in compliance with requirements in Article 1.9 — Coordination Meetings and Workshops, and Section 40 61 23 — SCADA System Field Assessment, Testing, and Start -Up. Coordinate with Facility Operators Contractor to retrieve existing PLC and HMI applications directly from PLCs and SCADA servers to ensure working with the latest files. Use these programs to develop as -installed control narratives. Coordinate with Water Operations and Water IT to access the existing SCADA HMI workstation(s) and verify the documented control descriptions on the live SCADA system during the As -Installed Control Narrative Workshops. 1.4 DESIGN A. General: 1. Project services in this phase include design of Water Department SCADA system architecture, specification of SCADA system components, and development of new control narrative documents. B. Key Activities: 1. Develop SCADA system architecture in coordination with Water IT as follows: a. Physical Network block diagram showing all components residing on the network inclusive of ports, labels/designations, and connections for all media types. IP addresses shall not be shown but shall be prepared in a separate table for use in coordination with Water IT. b. Virtual Network traffic flow diagram prepared to show in detail expected data transfers to provide viewer an accurate view of the intended flow of data/traffic across the network between all connected system databases and inputs and outputs to those databases. Data warehouse connections, custom connections, tablet, and alarm notification traffic flow shall be shown. CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 1— AD4 4061 13 SCADA SYSTEM GENERAL PROVISIONS Page 9 of 32 2. Prepare specifications for all SCADA system hardware and software components procured by the City under this Contract. Refer to Attachment 7 — SCADA Assets Responsibility Matrix for details. 3. Develop new FCN documents for all PLC systems in Category A. Refer to Attachment 6 — Existing WTP PLC Systems Table for details. 4. Coordination meetings and workshops: a. SCADA System Architecture and Component Selection Coordination Workshops b. SCADA System and Database Interface/Integration Coordination Workshops C. Functional Control Narrative Development Coordination Workshops d. Comply with the requirements in Article 1.8 Coordination Meetings and Workshops C. Deliverables: 1. SCADA system physical and virtual network design (30%, 60%, 100%, and Final) 2. SCADA system component specifications (30%, 60%, 100%, and Final) 3. FCNs, One (1) per Category A PLC system or process unit (Preliminary, Draft, and Final) 4. Comply with the requirements in Article 1.9 Submittals. D. The City's Responsibilities: 1. Review Contractor's submittals and attend the required coordination workshops. 2. Upon completion of SCADA system architecture design, review and provide written approval for the Contractor's Final architecture and component specifications. The Water IT, City, and/or City's representative can then proceed with procurement. 3. Provide the Contractor with requested information and supervised access to the existing data warehouse, as required. E. Coordination: 1. Coordinate preparation of SCADA system network diagrams and component specifications with Water IT and the respective equipment manufacturers. 2. Coordinate with Water IT to review existing databases and data warehouse configuration, and incorporate into the data flow architecture design, as required. 3. Coordinate workshops with the City in compliance with requirements in Article 1.4.A — Coordination Meetings and Workshops. 4. Upon receiving the City's written approval for the Final SCADA system architecture and component specifications, proceed with the procurement of third -party SCADA communication software and any other SCADA software identified in the Design phase as necessary to make the SCADA system functional, as specified in this contract and in accordance with Attachment 1 — PLC and HMI Configuration Standards. 1.5 PROGRAMMING AND CONFIGURATION A. General: Project services in this phase include creation of new and/or upgraded PLC, OIT, HMI, and report applications for all Water Treatment Plants (WTPs) and the Centralized SCADA system. Refer to Section 40 68 63 SCADA System Programming and Configuration for detailed scope. B. Key Activities: CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 1— AD4 4061 13 SCADA SYSTEM GENERAL PROVISIONS Page 10 of 32 1. Recreate existing SCADA HMI applications for all WTPs in Ignition to meet the standards in Attachment 1 — PLC and HMI Configuration Standards. 2. Upgrade programs for existing WTP PLCs as required to integrate with the new Ignition HMI system as follows: a. Recreate programs for newer PLC systems in North Holly, South Holly, West Side, and Rolling Hills WTPs to meet standards in Attachment 1 — PLC and HMI Configuration Standards. b. Integrate all PLC systems in Eagle Mountain WTP as well as select older and/or vendor -packaged PLC systems in North Holly, South Holly, West Side, and Rolling Hills WTPs with the new Ignition HMI system. C. Refer to Attachment 6 — Existing WTP PLC Systems Table for details of PLCs. 3. Upgrade applications for WTP OIT units as follows: a. Update applications for existing OIT units as required to interface with the upgraded PLC programs. b. Refer to Attachment 6 — Existing WTP PLC Systems Table for details of OITs. 4. Create HMI applications for new Industrial Panel Mounted Touchscreen Computers (IPCs) furnished by the City in Ignition to meet the standards in Attachment 1 — PLC and HMI Configuration Standards. Refer to Attachment 7 — SCADA Assets Responsibility Matrix for details of IPCs. 5. Create local plant operational reports in Ignition. 6. Create Centralized SCADA HMI applications, business and central operational reports in Ignition. 7. Configure WTPs and Centralized SCADA local Historians, Pass -Through Historian, and Central SCADA Historian. 8. Configure Centralized SCADA alarm notifications and tablet interface. 9. Coordination meetings and workshops: a. SCADA HMI Configuration and PLC Programming Coordination Workshops b. Local Plant Operational Report Development Coordination Workshops C. Centralized SCADA Business Reports Development Coordination Workshops d. Comply with the requirements in Article 1.8 Coordination Meetings and Workshops C. Deliverables: 1. SCADA HMI Graphics Submittals (Preliminary, Draft, and Final), grouped by PLC system. 2. PLC Configuration Submittals (Preliminary, Draft, and Final). 3. Alarm Management Submittals. 4. Historian Configuration Submittals, (Local Plant, Pass -Through, and Central Historians). 5. Report Configuration Submittals (Local Plant Operational, Tablet Data Entry, and Centralized SCADA Reports). 6. Comply with the requirements in Article 1.9 Submittals. D. The City's Responsibilities: 1. Review Contractor's submittals and attend the required coordination workshops. 2. Provide the Contractor with access to Data Warehouse tables for other production databases. 3. Provide information required for the Contractor to setup the custom connection interfaces required for LIMB and Ovation databases. CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 1— AD4 4061 13 SCADA SYSTEM GENERAL PROVISIONS Page 11 of 32 E. Coordination: 1. Control narratives shall be approved by the City in Design phase prior to the start of PLC software development. 1.6 FACTORY ACCEPTANCE TESTING A. General: 1. Project services in this phase include performing unwitnessed and witnessed factory testing of all new and/or upgraded PLC, OIT, HMI, and report applications for all Water Treatment Plants (WTPs) and the Centralized SCADA system. Refer to Section 40 6121 — SCADA System Factory Acceptance Testing for detailed scope. B. Key Activities: 1. Unwitnessed Factory Tests (UFTs) and Witnessed Factory Tests (WFTs) a. UFTs and WFTs shall be performed for all WTPs and the Centralized SCADA system. b. The factory testing of each WTP shall include its respective integration with Centralized SCADA. Each WTP UFT and WFT shall include but not be limited to plant HMI, PLC, and OIT applications, local Historian and operational reports, the respective Centralized SCADA HMI screens, alarm notifications, and data flow and replication with Central Historian. C. The Centralized SCADA UFT and WFT shall include but not be limited to central HMI application and alarm notification incorporating all WTPs, business and central operational reports, and tablet interface. d. All UFTs and WFTs shall utilize the respective WTP and Centralized SCADA hardware and software assets furnished for the project, either via remote access from the Contractor's facility or by performing the tests on site. C. Deliverables: 1. UFT and WFT Plans, One (1) per WTP and one (1) for Centralized SCADA. 2. UFT and WFT Reports, One (1) per WTP and one (1) for Centralized SCADA. 3. Comply with the requirements in Article 1.10, Submittals. D. The City's Responsibilities: 1. Review Contractor's UFT and WFT plans and reports. 2. Attend the required WFTs. 3. The new SCADA hardware and software assets for Centralized SCADA and respective WTP(s) are to be made ready and available to the Contractor for factory acceptance testing no less than thirty (30) days prior to the scheduled start of the first UFT. 4. Arrange secure remote access for the Contractor to the new SCADA hardware and software assets for Centralized SCADA and respective WTP(s) from their facility, if necessary, no less than thirty (30) days prior to the scheduled start of the first UFT. E. Coordination: 1. Notify the City no less than ninety (90) days prior to the planned start of the first UFT/WFT and thirty (30) days prior to the planned start of each factory acceptance testing thereafter. 2. Coordinate with the City to install and configure all SCADA and PLC software and applications, including all required communication software, for Centralized SCADA and CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 1— AD4 4061 13 SCADA SYSTEM GENERAL PROVISIONS Page 12 of 32 respective WTP(s) no less than thirty (30) days prior to the scheduled start of each factory test. 3. Coordinate with the City to verify the configuration of new SCADA system hardware and software assets for Centralized SCADA and respective WTP(s), and remote access connection (if necessary), no less than thirty (30) days prior to the scheduled start of each factory test. 4. Coordinate with the City to verify communications and data transmission between the respective servers, workstations, and test PLC system(s) as well as configuration of all software inclusive of virtual environment, Ignition and all 3rd part software. 5. UFT and WFT Plans shall be submitted and approved no less than thirty (30) days prior to the scheduled start of respective tests. 6. Contractor shall receive approval from the City on all required SCADA system application submittals no less than thirty (30) days prior to the scheduled start of first UFT of a given facility. 7. Contractor shall complete UFT and submit test reports no less than 30 days prior to the scheduled start of the associated WFT. 1.7 CUTOVER, FIELD TESTING, AND START-UP A. General: 1. Project services in this phase include planning and performing SCADA system replacements at all Water Treatment Plants (WTPs) and the Centralized SCADA system. Refer to Section 40 61 23 — SCADA System Field Assessment, Testing, and Startup and this section for detailed scope. B. Key Activities: 1. Cutover planning 2. Cutover, system field testing and start-up a. Perform one (1) cutover per WTP and one (1) for the Centralized SCADA system. b. Each WTP cutover shall include the cutover, field testing and start-up of all PLC systems in the plant and integration into Centralized SCADA. New and existing WTP SCADA systems shall be operated in parallel from the cutover of the first PLC system through cutover of the last PLC in each plant. As each PLC system is cut over from the existing to the new SCADA system, the associated data will be activated on the new plant HMI, local Historian, and local operational reports. The associated HMI screens, alarms notifications, and Historian data shall also be tested and activated on the Centralized SCADA system one PLC system at a time. C. As part of each PLC system cutover, the respective historical data tags between Legacy and new Central SQL Historians in the data warehouse shall be linked to allow query of older SCADA data from the new SCADA system and to maintain the functionality of City's existing business reports and applications, and central operational reports that require access to latest logged SCADA data points. The City will reconfigure the existing business/central reports and applications to interface with the new Central SQL database for the respective SCADA information. d. The Centralized SCADA system cutover shall include testing and start-up of the central HMI application and alarm notifications with all WTPs integrated, the new Ignition business and central operational reports, and associated tablet interface. 3. Operational Availability Demonstration (OAD) CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 1— AD4 4061 13 SCADA SYSTEM GENERAL PROVISIONS Page 13 of 32 a. Perform one (1) OAD per WTP and one (1) for the Centralized SCADA system b. Each OAD shall require 30 consecutive days of normal operation of the replacement SCADA system without any significant failures and/or interruptions to receive approval otherwise the OAD shall restart. 4. Coordination meetings and workshops: a. SCADA System Cutover Planning Coordination Workshops b. SCADA Architecture and Database Interface/Integration Readiness Workshops C. Comply with the requirements in Article 1.9 — Coordination Meetings and Workshops C. Deliverables: 1. SCADA System Cutover Plans, One (1) per WTP and one (1) for Centralized SCADA (Preliminary, Draft, and Final) 2. Loop Test Plans, One (1) per WTP PLC system 3. Loop Test Reports, One (1) per WTP PLC system 4. System Field Testing and Start-up Plans, One (1) per WTP PLC system and one (1) for Centralized SCADA 5. System Field Testing and Start-up Reports, One (1) per WTP PLC system and one (1) for Centralized SCADA 6. OAD Period Letters, one (1) per WTP and one (1) for Centralized SCADA 7. OAD SCADA System Malfunction/Repair Form, one (1) per WTP and one (1) for Centralized SCADA 8. Comply with the requirements in Article 1.10 — Submittals. D. The City's Responsibilities: 1. Review Contractor's submittals and attend required coordination workshops. 2. Supply the Ignition software and all associated modules, as well as all 3rd party SCADA software listed in Attachment 7 — SCADA Assets Responsibility Matrix, to the Contractor. 3. Install and configure all SCADA system computers and networking equipment hardware, and the associated software furnished by the City under this Contract no less than sixty (60) days prior to the scheduled start of cutover and field activities by the Contractor. 4. Reconfigure the existing business/central reports and applications to interface with the new Central SQL database for the respective SCADA information. 5. Operate the replacement SCADA system during OAD and promptly report any encountered issues to the Contractor. E. Coordination: As part of cutover planning, the Contractor shall coordinate with the City and develop a construction sequence, cutover schedule, shutdown durations and requirements, and incorporate into the overall project schedule. Contractor is responsible for coordinating all shutdown schedules and shutdown durations with other contractors of ongoing contracts and with the City. Coordinate with Facility Operators for scheduled shutdowns and proper operation of existing and new systems during these shutdowns. Prior to placing in service, coordinate and verify with Facility Operators that the upgraded SCADA and/or PLC systems are functioning as intended. Coordinate with Facility Operators and facilitate manual operation of the process and/or equipment effected by a scheduled shutdown. CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 1— AD4 4061 13 SCADA SYSTEM GENERAL PROVISIONS Page 14 of 32 4. WTP cutover and field testing activities shall be scheduled no less than hundred -eighty (180) days after achievement of Milestone 1, approval of Final SCADA System Architecture design and component specifications. 5. WTP cutover and field testing activities shall be scheduled no less than thirty (30) days after Witness Factory Testing for all PLC systems associated with that plant has been completed and approved. 6. WTP cutover and field testing activities shall be scheduled no less than thirty (30) days after the associated Final cutover plan for that plant has been approved. 7. The Contractor shall submit an OAD Period Letter for each OAD to the City indicating the start date, period, and proposed end date of the OAD. The start date shall be signed by all applicable parties indicating commencement of the OAD. 8. Coordinate with the City to address any reported system failures during OAD. 9. Coordinate workshops with the City in compliance with requirements in Article 1.4.A, Coordination Meetings and Workshops. 10. On completion of a specific Operational Availability Demonstration (OAD), provide a submittal documenting alarm metrics and provide an as -built alarm database. 11. Three months after the completed OAD of each WTP, provide an Alarm Audit submittal comparing current metrics against benchmarking. Provide narrative and recommendations to the City for continued optimization of Alarm Management. 12. Coordinate with the Water IT for all required interface with the existing data warehouse. 1.8 SYSTEM MAINTENANCE, FINAL ACCEPTANCE, AND WARRANTY A. System Maintenance: 1. Provide limited maintenance services as described in Section 00 14 16 — Coordination with City's Operations. B. Final Acceptance: 1. Provide necessary closeout and punch list activities and submit all necessary documentation to meet Final Acceptance as defined in Division 0 and Division 1. C. Warranty: 1. Meet all warranty requirements as defined in Section 0178 36 — Warranties. 1.9 REFERENCES A. Design of SCADA system shall meet the following Standards: 1. ISA-18.2: Management of Alarm Systems for the Process Industries 2. ISA-99/IEC 62443: Industrial Automation and Control Systems Security 3. ISA-101: Human -Machine Interfaces for Process Automation Systems 4. IEC 61131: Programmable Controllers 5. NIST SP 800-82: Guide to Industrial Control Systems (ICS) Security 6. AWWA G430: Security Practices for Operation and Management 7. AWWA J100: Risk and Resilience Management of Water and Wastewater Systems 8. IEEE 1686: Standard for Substation Intelligent Electronic Devices (IEDs) Cyber Security Capabilities 9. ANSI/AWWA G100: Water Treatment Plant Operation and Management 10. EPA's Water Security initiatives and guidelines for the security of water systems. CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 1— AD4 4061 13 SCADA SYSTEM GENERAL PROVISIONS Page 15 of 32 1.10 QUALITY ASSURANCE A. Contractor shall utilize approved system and software engineers who have been factory trained and certified on the respective software packages, to perform all programming functions, develop control strategies, create graphic displays, customize applications, document all work, and coordinate the software interface. They shall be intimately familiar with the details of this project, water and wastewater treatment facility instrumentation and control in general, high performance graphics development and the project goals and requirements. The Contractor shall comply with restrictions on substitutions as noted in Section 00 21 15 — Instruction to Offerors. 1.11 COORDINATION MEETINGS AND WORKSHOPS A. General: 1. Schedule conferences, meetings and workshops as described in this section. 2. All meetings and workshops shall be held at the location directed by City, unless otherwise noted. The City's designated location could vary based on the meeting agenda. 3. Contractor shall prepare and provide an agenda for each meeting or workshop specified in this section no less than two (2) weeks prior to the scheduled meeting date, unless otherwise noted, for review and comment by City. Contractor shall identify meeting location in agenda. 4. Required Attendees include Contractor's staff who are responsible for SCADA system design, programming, and configuration, City's staff determined by the City. 5. Contractor is responsible for preparing the minutes of the meetings or workshops that describe topics discussed, conclusions maid, and action items along with responsible party. Contractor shall submit each workshop minutes to the City for review and approval prior to distributing it to the attendees. B. Familiarization and Preliminary Assessment Phase Coordination Workshops: 1. A minimum of six (6) System Assessment Coordination Workshops, one per WTP and one for Centralized SCADA, shall be conducted by the Contractor. If additional Workshops are required, they shall be scheduled and conducted at no additional cost to the City. 2. A minimum of twenty (20) As -Installed Functional Control Narrative Coordination Workshops shall be conducted by the Contractor. If additional Workshops are required, they shall be scheduled and conducted at no additional cost to the City. 3. Contractor shall account for a minimum of three (3) hours for each workshop, not including travel time. 4. The purpose of these workshops will be to review, verify, and coordinate the Contractor's findings from the field inspections and assessments, and the documented as -installed control narratives. 5. As -Installed Control Narrative Workshops shall include verification of the documented control descriptions on the live SCADA system for the critical control loops as identified by the City. Contractor shall arrange access to the existing SCADA HMI workstation(s) through coordination with Water Operations and Water IT for operation and verification of the identified control scenarios during the workshops. C. Design Workshops: SCADA System Architecture and Component Selection: 1. Design services shall be coordinated with the City through coordination meetings and workshops conducted in accordance with the requirements described in Section 01 14 16 — Coordination with City's Operations and this section. CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 1— AD4 4061 13 SCADA SYSTEM GENERAL PROVISIONS Page 16 of 32 2. A minimum of six (6) SCADA Architecture, Database Configuration, and Network Configuration Coordination Design Workshops shall be conducted by the Contractor. Four of the Workshops are to review Design deliverables. The remaining two can be used for topics for all WTPs as necessary by the Contractor to facilitate progression of the design. If additional Workshops are required, they shall be scheduled and conducted at no additional cost to the City. The workshops shall include, but not limited to, the following: a. Design Deliverable Workshops: 1) Provide a workshop to review the 30%, 60%, 100% and Final Architecture Design Deliverables. b. Other Workshop Topics: 1) Review the IP Address scheme for SCADA System. 2) Security standards and policies required for SCADA System. 3) Internet service and high bandwidth communication lines coordination. 4) Cellular Services/connectivity for Tablets. 5) Networked drive requirements. 6) Backup Storage Server access, policies, folder structure, and capacity. 7) Domain control and initial settings of SCADA and Historian servers and workstations. 8) Logical network segmentation and segregation. 9) Review the SCADA network and routing protocols. 10) Details related to NTP time server time and connections. 11) Remote alarm monitoring and notification 12) Traffic flow for all data, routing of all data, sizing of databases. 13) Migration of existing data into the new data historians. 14) Test bench setup c. Contractor shall account for a minimum of two (2) hours for each workshop, not including travel time. d. The purpose of these workshops will be to review and coordinate physical/logical SCADA system architecture, security of the SCADA System, and hardware/software component selection with Water IT. D. Design Workshops: Functional Control Narrative (FCN) Development Coordination Workshops: 1. A minimum of fifteen (15) Functional Control Narrative Development Coordination Workshops shall by conducted by the Contractor, three per WTP for Preliminary, Draft and Final FCN submissions. If additional Workshops are required, they shall be scheduled and conducted at no additional cost to the City. 2. The purpose of these workshops is to review, verify, and coordinate the Contractor's development of FCNs and configuration of PLC function blocks to ensure they meet the requirements outlined in Attachment 1 — PLC and HMI Configuration Standards. 3. Contractor shall account for a minimum of three (3) hours for each workshop, not including travel time. E. SCADA HMI Configuration and PLC Programming Coordination Workshops: 1. A minimum of thirty-six (36) HMI Configuration and PLC Programming Coordination Workshops shall be conducted by the Contractor. If additional Workshops are required, they shall be scheduled and conducted at no additional cost to the City. 2. Contractor shall account for a minimum of three (3) hours for each workshop, not including travel time. CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 1— AD4 4061 13 SCADA SYSTEM GENERAL PROVISIONS Page 17 of 32 3. The purpose of these workshops is to review, verify, and coordinate SCADA HMI configuration and PLC programming meets the requirements outlined in Attachment 1 — PLC and HMI Configuration Standards, and to exchange programming information related to HMI Graphic and PLC Logic development. 4. Workshops shall include live demonstration of the HMI system to provide an interactive experience. F. Local Plant Operational Report Development Workshops: 1. A minimum of two (2) Report Development Workshops shall be conducted by the Contractor for each of the five (5) Water Treatment Plants, total of ten (10) workshops. If additional Workshops are required, they shall be scheduled and conducted at no additional cost to the City. 2. Contractor shall account for a minimum of two (2) hours for the workshop, not including travel time. 3. The purpose of these workshops shall be to coordinate and develop report templates that meet the regulatory agencies format and data field requirements and the standard reports configured to print for day-to-day operational needs of the five water treatment plants. Include in the workshop discussion of required data points, scan time of each point, buffering requirements, and calculations. G. Centralized SCADA Business Reports Development Coordination Workshops: 1. A minimum of eighteen (18) coordination workshops shall be conducted as follows. If additional Workshops are required, they shall be scheduled and conducted at no additional cost to the City. a. Ten (10) Workshops (5 design, 5 mockup demonstrations), to review and confirm data/sources, tagging, use of templates, look/feel for the Reports using data from Centralized SCADA and the existing data warehouse. Provide mockup demonstrations. b. Four (4) Workshops (2 design, 2 mockup) to review requirements, and reports/dashboard related to custom interfaces (LIMS, Ovation) C. Two (2) Workshops to review remote alarm monitoring, and notification. d. Two (2) Workshops to review use of Tablets, data entry and provision for backfill of data on communication loss. 2. Contractor shall account for a minimum of two (2) hours for each workshop, not including travel time. 3. The purpose of these workshops shall be to coordinate and develop report templates that meet the regulatory agencies format and data field requirements and the standard reports configured to print for day-to-day operational needs of the five water treatment plants. Include in the workshop discussion of required data points, scan time of each point, buffering requirements, and calculations. H. Cutover Planning Coordination Workshops 1. A minimum of three (3) Cutover Planning Coordination Workshops shall be conducted by the Contractor for each of the five (5) Water Treatment Plants, and a minimum of five (5) for the overall system, for a total of twenty (20) workshops. If additional Workshops are required, they shall be scheduled and conducted at no additional cost to the City. 2. Contractor shall account for a minimum of two (2) hours for each workshop, not including travel time. CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 1— AD4 4061 13 SCADA SYSTEM GENERAL PROVISIONS Page 18 of 32 The purpose of these Workshops shall be to coordinate all requirements for WTP SCADA system cutovers, and to review and confirm cutover plans with the City to ensure the continuity and reliability of critical WTP processes and operations are maintained during the respective SCADA system cutovers. I. SCADA Architecture and Database Interface/Integration Readiness Workshops: 1. A minimum of six (6) SCADA Architecture and Database Interface/Integration Coordination Workshops, one per WTP and one for Centralized SCADA, shall be conducted by the Contractor. If additional Workshops are required, they shall be scheduled and conducted at no additional cost to the City. 2. Contractor shall account for a minimum of two (2) hours for each workshop, not including travel time. 3. The workshops shall be scheduled after the Cutover Plans have been prepared but in advance of architecture and/or data interface implementation at a given facility or for Centralized SCADA, and shall include, but not limited to, confirmation and review that all network equipment, software, database work, historian work has or will achieve a state of readiness to allow implementation of the Cutover Plan. 1.12 SUBMITTALS A. General: 1. Contractor shall be responsible for all submittals specified herein. Refer to Section 0133 00 — Submittal Procedures, for general submittal requirements. 2. Shop drawings shall demonstrate that the equipment and services to be furnished comply with the provisions specified in this contract and shall provide a complete record of the equipment as manufactured and delivered. 3. Submittals shall be complete, giving equipment specifications, features, details of connections, wiring, ranges, installation requirements, and specific dimensions. Submittals consisting of only general sales literature shall not be acceptable. 4. Provide all required submittals for mobilization as indicated in Division 0 and 1. B. Project Plan and Project Schedule Submittal: 1. Contractor shall submit, within 30 calendar days after Notice to Proceed, the Project Plan and detailed Project Schedule. 2. Project Plan: The Project Plan shall, as a minimum, contain the following: a. Overview: Summary overview of Contractor's understanding of project scope of work, existing conditions assessment, 60%, 90% and 100% design activities, and proposed control system work at each water treatment plant and the Centralized SCADA system. b. Personnel Information: Project personnel and organization including the System Contractor's project manager, project engineer field representative, local service representative, and similar personnel for Supplier. Indicate addresses of personnel not based at Contractor's and Supplier's office nearest to the Site. Include resumes of each key individual and specify in writing their commitment to this project. C. Meeting Agenda Information: Preliminary meeting agenda for Project Kickoff Meeting as specified in this section. d. Work Approach: Flow chart showing steps to be taken in preparing and coordinating SCADA System design and construction submittals. e. Shop Drawing Information: CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 1— AD4 4061 13 SCADA SYSTEM GENERAL PROVISIONS Page 19 of 32 1) A list of expected SCADA System submittals to be provided under this Contract. List shall include submittal descriptions and Specification reference numbers at minimum. 2) Sample of each type of process control submittal required by the Contract Documents. These may be submittals prepared for other projects. At a minimum include samples of panel fabrication drawings, loop, I/O wiring diagrams. 3) Flow chart showing steps to be taken in preparing and coordinating SCADA System submittals £ Preliminary Hardware and Software Information: Preliminary PLC software, OIT software, and PLC hardware submittal information, including version numbers, solely to determine compliance with the requirements of this contract. Review and approval of software and hardware systems as part of this Project Plan stage shall not relieve the Contractor of responsibility for meeting all the function and performance requirements of the system as specified herein. 3. Project Schedule: a. Project schedule shall be prepared in accordance with the requirements of Section 01 32 16 — Progress Schedule. b. The project schedule shall illustrate all major project milestones including the following: 1) Project kickoff meeting and subsequent site visits to coordinate mobilization. 2) Field loop inspections, prepare inspection report, and review with City for all applicable PLC systems. 3) Develop as -installed control narratives, and review with City for all applicable PLC systems. 4) Current condition assessment, prepare current assessment report, and review with City for each water treatment plant and the overall SCADA system. 5) Design and develop 30%, 60%, and 100% design documents and design documents review meeting with City. 6) Develop and submit Final design documents prior to release for procurement by the City. 7) Schedule for all subsequent submittals. Include in the time allotment the time required for Contractor submittal preparation, City's review time, and a minimum of two complete review cycles. 8) Proposed dates for all project coordination meetings and workshops as specified in this section. 9) Hardware purchasing, fabrication, and assembly by the City (following completion of related design by Contractor). 10) Milestone(s) showing when City should make required SCADA software and hardware components for each water treatment plant ready for the Contractor. 11) Schedule for each water treatment plant SCADA system cutover and testing. Testing schedule shall include submittal and approval of cutover plans and test procedures prior to commencement of field activities. 12) Schedule for system startups and all required field tests and operational availability demonstrations at each water treatment plant and Centralized SCADA system. 13) Schedule for all training including submittal and approval of O&M manuals, factory training, and site -specific training. C. Familiarization and Preliminary Assessment Submittals: CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 1— AD4 4061 13 SCADA SYSTEM GENERAL PROVISIONS Page 20 of 32 1. Existing Field Input/Output (I/O) Inspection Forms: a. 1/0 Status Sign -Off Forms shall be used to organize and track an existing PLC system's field inspection. b. Submit separate Input/Output Status Sign -Off Form for each PLC system. C. The form shall include a table based on the existing PLC I/O list. The table shall include the following columns at minimum: 1) PLC Name 2) Signal Tag 3) Description 4) Range or active state when event or alarm state is reversed 5) Drawing Reference 6) Signal Type 7) Rack No. 8) Slot No. 9) Channel No. 10) Instrument Alarm Setpoint 11) Calibration, Configuration, and Wiring Complete (signoff area) with Date 12) IO Testing from the field to the OIT (signoff area) with Date, as applicable 13) IO Testing from the field to the HMI (signoff area) with Date 14) IO Testing from the OIT to the field (signoff area) with Date, as applicable 15) IO Testing from the HMI to the field (signoff area) with Date 16) Notes d. Submit I/O Test Results Submittal for each test performed. Submittal shall include a record copy of the test results. 2. As -Installed Functional Control Narratives: a. As -installed functional control narrative documents shall be submitted in two stages, Draft, and Final. b. The format of the documents shall comply with Attachment 8 — Sample Functional Control Narrative (FCN) Template. C. Draft submittals shall incorporate the results of the field I/O inspections and shall be submitted at minimum three (3) weeks prior to the start of As -Installed Control Narrative Coordination Workshops for review with the City during the workshops. All modes of operation currently coded and currently used shall be identified in the documents. d. Final documents shall be submitted after all As -Installed Control Narrative Coordination Workshops have been completed. e. All review comments and markups on the Draft submittal that are returned to the Contractor, and feedback received during the coordination workshops, shall be fully addressed and incorporated into the narratives prior to submitting the Final submittals. The results from the live verification of the identified critical control loops during the workshops shall also be incorporated into the Final narratives. 3. System Condition Assessment Technical Reports: a. Contractor shall submit Condition Assessment Technical Reports, One (1) per WTP, and one (1) for Centralized SCADA. b. Reports shall include description of existing SCADA system conditions resulting from review of available information and documentation, field inspections and assessments, on -site meetings, and coordination workshops. CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 1— AD4 4061 13 SCADA SYSTEM GENERAL PROVISIONS Page 21 of 32 D. SCADA System Architecture and Component Specifications Submittals: 1. SCADA system architecture design and component specifications shall be submitted in four stages, 30%, 60%, 100%, and Final. 2. Develop the SCADA system architecture and design specifications for all system hardware and software components in accordance with Article 1.2 — SCADA System Architecture Description and Attachment 7 — SCADA Assets Responsibility Matrix. 3. System architecture and component selection shall be closely coordinated with the City through SCADA System Architecture and Component Selection Coordination Workshops and SCADA Architecture and Database Interface/Integration Coordination Workshops. 4. SCADA system design specifications shall include make and model/part number information for all hardware and software components. 5. When the design reaches 30% level, Contractor shall submit 30% design package to City for City's review. Contractor shall conduct a review workshop with City and go over the 30% design in detail and receive City's review comments. City's review comments shall be incorporated into the design prior to submitting 60% design documents for City's review. 6. When the design reaches 60% level, Contractor shall submit 60% design package to City for City's review. Contractor shall conduct a review workshop with City and go over the 60% design in detail and receive City's review comments. City's review comments shall be incorporated into the design prior to submitting 100% design documents for City's review. 7. When each water treatment plant design reaches 100% level, Contractor shall submit 100% design package to City for City's review. The 100% design review package for each shall include final SCADA system architecture design and final SCADA hardware and software data sheets or specifications, Bill of materials with manufacturer names and model numbers of all SCADA system hardware and software components to be procured by the City. Contractor shall conduct a review meeting with City and go over the 100% design in detail and receive City's review comments. 8. The Contractor shall incorporate the City's review comments prior to submitting the Final design documents for written approval by the City. Water IT will then proceed with procurement. E. Functional Control Narrative Submittals: 1. Control narrative documents shall be submitted in three stages, Preliminary, Draft, and Final. 2. One control narrative shall be submitted for each PLC system, or a group of related PLC systems belonging to a single process. The new FCNs shall incorporate the validated control descriptions in Final As -Installed Control Narratives as no changes to the existing control logic will be made under this Contract. 3. The format of the documents shall comply with Attachment 8 — Sample Functional Control Narrative (FCN) Template. 4. FCNs shall be developed in accordance with Attachment 1 PLC and HMI Configuration Standards. 5. Preliminary submittals shall be provided to the City no less than four (4) weeks prior to the start of Control Narrative Development Coordination Workshops. 6. All review comments and markups on the Preliminary submittal that are returned to the Contractor, and feedback received during the coordination workshops, shall be fully addressed and incorporated into the control narratives prior to submitting the Draft submittals. CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 1— AD4 4061 13 SCADA SYSTEM GENERAL PROVISIONS Page 22 of 32 As part of the Draft submittal, the Contractor shall provide PLC function blocks developed for the project in accordance with Attachment 1 — PLC and HMI Configuration Standards for City's review and approval. Final FCN documents and configured PLC function blocks shall be submitted upon completion of all Control Narrative Development Coordination Workshops. The Contractor shall fully address and incorporate all review comments and markups on the Draft submittal, as well as feedback received from the City during the coordination workshops, before submitting the Final submittals. The Final submittal must be reviewed and approved by the City prior to the start of PLC software development by the Contractor. F. HMI Graphics Submittals: 1. Submit separate submittal packages as specified below. 2. A group of sample HMI graphics that is representative of the overall project shall be submitted for review and approval by the City. The sample HMI graphic package shall be submitted in three stages, Preliminary, Draft, and Final. The Draft submissions shall be accomplished through live demonstrations of the actual graphics. 3. For each WTP, and grouped by PLC panel or unit process, provide: a. Preliminary (30%), Draft (60%), and Final (100%) graphics submittals. The Final Graphics will be submitted for approval prior to conducting Factory Tests. b. Submittals may be grouped into multiple submittals to facilitate review and reduce size of individual submittals. 4. WTP Preliminary (30%) HMI Graphics Submittals: a. Preliminary HMI Graphic Submittal packages shall be submitted prior to HMI graphics coordination workshop. b. Submit all proposed HMI graphics for the WTP. Provide one graphic per 11" x 17" page and size graphic to fit. Provide color graphics. C. Submit a complete HMI Database for the WTP. d. The HMI graphics shall meet the standards provided in Attachment 1 — PLC and HMI Configuration Standards. The submittal shall include the following: 1) Sample HMI screen(s) as template(s) for screen layout. Include one template for each type of screen provided. Include the following templates at minimum: a) Process Overview screen b) Main Menu screen(s) c) Process Display screens d) Trend screen e) Alarm summary screen f) Login/security screen g) Equipment control and setpoint entry Pop-up screens h) Screens displaying analog values grouped per processes i) SCADA communication network display screen showing communication status 2) Complete list of proposed HMI screens. Include screen name and brief description on contents. Identify facility where screen will be used. More than one location may be identified for a given screen. 3) Proposed HMI screen navigation hierarchy for each location. 5. WTP Draft (60%) HMI Graphics Submittal and Demo: a. The Draft HMI Graphics Submittal shall be accomplished through a live demo of the actual graphics for each WTP connected to test PLC(s) furnished by the Contractor, CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 1— AD4 4061 13 SCADA SYSTEM GENERAL PROVISIONS Page 23 of 32 which shall be programmed with the respective upgraded and/or existing PLC logic. For Category A PLCs, the HMI graphics demo will be utilized to test and verify the PLC function blocks configured by the Contractor in the Design phase. b. Acceptance of Preliminary HMI Graphics Submittal shall be required prior to conducting the Draft HMI Graphics demonstration. All review comments and markups on the Preliminary HMI Graphic Submittal that are returned to the Contractor shall be fully addressed and incorporated into the HMI Graphics prior to conducting the Draft HMI Graphics demonstration. C. Each graphic display and process layout will be subject to modification from Contractor's submitted format and layout within limits of software package used for development. Contractor is required to implement such modifications in accordance with City's written comments on the submittal. Expect 20% rework from Contractor's submitted format, layout and symbology used. WTP Final (100%) HMI Graphics Submittal: a. A Final HMI Graphics Submittal shall be submitted as a separate package for each WTP. b. Acceptance of Draft HMI Graphics Submittal shall be required prior to submission of the Final HMI Graphics Submittal. All review comments and markups on the Draft HMI Graphics that are returned to the Contractor shall be fully addressed and incorporated into the HMI Graphics prior to submitting the Final HMI Graphics Submittal. C. Submit HMI final graphics for each facility. Provide one graphic per 11" x 17" page and size graphic to fit. Provide color graphics. d. The Final HMI Graphics submittal must be reviewed and approved by the City prior to the Factory Acceptance Tests. However, the City's staff witnessing the test may still have comments during the Factory Acceptance Tests that did not arise in the three review submissions. These comments shall be incorporated and documented with the submitted Factory Test Report at no additional cost to the City. G. PLC Configuration Submittals: 1. Submit, for each WTP, and where upgraded PLC programs are required: a. Preliminary (30%), Detailed (60%) and Final (100%) PLC submittals. The Final PLC code will be submitted prior to conducting Factory Tests. b. Submittals may be grouped into multiple submittals to facilitate review and reduce size of individual submittals. 2. Preliminary (30%) PLC Submittal a. Submit one PLC program in its native electronic language as a sample for verifying PLC programs developed by the Contractor meet the standards provided in Attachment 1 — PLC and HMI Configuration Standards. Program shall have PLC system name and associated facility name. b. The sample PLC program submittal review will be limited to the verification of the program meeting City's standards. Control strategies and other monitoring and control functions will not be part of review and will be verified during Factory Acceptance Tests. C. Submit the following as part of the sample program submittal: 1) List of deviations from the existing control strategies and/or functions. 2) List of requests for additional information from the City, if applicable. 3) Format, logic, protocol, and procedures for data transmission and communications with input/output modules and peripheral devices, including Ethernet/IP. CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 1— AD4 4061 13 SCADA SYSTEM GENERAL PROVISIONS Page 24 of 32 4) Input/output (I/O) point listing with I/O module cross-reference identification for all PLC and Remote Input Output racks. 3. Draft (60%) PLC Submittal: a. The Draft PLC Submittal shall demonstrate development of the code to support the associated Functional Control Narrative. 4. Final (100%) PLC Submittal: a. A Final PLC Submittal shall be submitted as a separate package for each WTP. b. The final PLC program shall be submitted with the 100% HMI Submittal and demonstrate readiness for Factory Testing. C. The Final (100%) PLC submittal shall be approved at the Factory Acceptance Tests. 5. The approval of Final (100%) PLC code will be part of the respective WTP Factory Acceptance Tests. The City's staff witnessing the Factory Acceptance Test may have comments during the Factory Acceptance Test that did not arise in the review submissions. These comments shall be incorporated and documented with the submitted Factory Test Report at no additional cost to the City. H. Alarm Management Submittals: 1. Alarm Database Submittals: a. Provide a separate submittal for each WTP. b. Provide table of contents. C. List of requests for additional information, if applicable. d. List of all alarms. For each alarm, include as a minimum the tag name, description as it will appear on the alarm summary screen, priority, normal and alarm state, reset requirement, alarm group, alarm sound, shelving, flood, remote notification, escalation, setpoint, dead band, as applicable. 2. The Alarm List shall be used as a working document and shall be updated as needed. Provide a major revision number and note every time it is re -submitted and minor revision when it only includes minor corrections. 3. Alarm Benchmarking: On completion of a specific Operational Availability Demonstration (OAD), provide a submittal documenting alarm metrics and provide an as -built alarm database. 4. Alarm Rationalization: Three months after the completed OAD, provide an Alarm Audit submittal comparing current metrics against benchmarking. Provide narrative and recommendations to Owner for continued optimization of Alarm Management. See Section 40 68 83 — SCADA System Programming and Configuration, Article — 3.13 for additional details. I. Historian Configuration Submittals: 1. Provide a separate submittal for each Historian server. 2. Provide table of contents. 3. Submit the following: a. List of requests for additional information, if applicable. b. Proposed list of all database points for Historical archiving. Provide a separate list for each Historian. Database shall include the previous tag name and the new tag name for each point. C. Online and offline capabilities for software programming and diagnostics. 4. The final approved Historical Data List for the given facility shall be submitted and must be reviewed by the City prior to the start of the Operational Availability Demonstration (OAD) for the Historian, Report, and Alarm Management Software. The City may have CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 1— AD4 4061 13 SCADA SYSTEM GENERAL PROVISIONS Page 25 of 32 review comments during the review conducted prior to OAD. These comments shall be incorporated and documented with the final operations and maintenance information at no additional cost to the City. Local Plant Operational, Tablet Data Entry, and Centralized SCADA Report Configuration Submittals: 1. For each of the items listed above, group submittal packages by facility or type of report. Grouping shall be practical to allow for timely substantive review by the City. 2. Prior to commencing these submittals, provide a proposed list of submittals and groupings expected for this work for review and approval by the City. 3. Provide table of contents for each submittal. 4. Preliminary Report Configuration Submittals: a. Submit the following: 1) Complete list of Reports that is coordinated and established during design phase and in the report development workshop. Include a table of contents identifying specific reports included in each submittal. Submittals shall be grouped clearly. Include report name, facility name and brief description on contents. 2) For each Tablet Data Entry form, Centralized SCADA, or Local Plant Operational report, provide the following details: a. List of points/source database. b. Template in PDF and native form. c. Results from Workshops and associated Mockup Demonstrations. d. Connectivity information including data sampling, encryption, and other settings relative to the specific submitted form, or report. e. For the tablets, identify how the system will handle communication loss and backfill of data on resumption of communications. 3) List of requests for additional information, if applicable. 4) Detailed description of Report software configuration for each installed location. 5) Sample report for each type of report proposed. Sample reports shall be submitted in color, where applicable, on 8-1/2" x 11" page. 5. Final Report Configuration Submittals: a. Acceptance of the Preliminary Configuration Submittal shall be required prior to submission of the Final Report Configuration Submittals. All review comments and markups on the Preliminary Report Configuration Submittal that are returned to the Contractor shall be fully addressed and incorporated into the Reports prior to submitting the Final Report Configuration Submittals. b. Provide a separate submittal for each approved grouping. C. Submit the following: 1) Complete list of Tablet Entry, Reports or Dashboards included. Include report name and brief description on contents. If a report is typical for another facility(s), identify the other facility it is also used. 2) Complete set of report or data entry templates for review. Report templates will not include data set values. Each report template shall be submitted in color, where applicable, on 8-1/2" x 11" page. 3) Complete set of reports with a sample data set to provide an example of a generated final report. 4) List of all linked database and historical tags used for each report. 6. The Final Report Configuration submittals shall be submitted, reviewed, and approved prior to the start of OAD for the Historian, Report, and Alarm Management Software. The CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 1— AD4 4061 13 SCADA SYSTEM GENERAL PROVISIONS Page 26 of 32 City may have review comments during the review conducted prior to OAD. These comments shall be incorporated and documented with the final operations and maintenance information at no additional cost to the City. K. Factory Testing Submittals: 1. Testing Plan Submittals: a. Submit separate test plans for each specified test phase. b. The Factory Test Plan shall be submitted and approved prior to scheduled start of factory test. Refer to Section 40 6121 — SCADA System Factory Acceptance Test, for time requirement. C. Test Plan shall include at minimum: 1) Information on equipment to be tested. 2) Proposed test dates. 3) Expected duration of test. 4) Location where factory test will be conducted. 5) List of required testing equipment. 6) Test procedure and signoff forms. d. Test procedure forms shall include at minimum: 1) Cover sheet with test summary. 2) Detailed descriptions for each test to be performed. Each test to be performed shall be described and a space provided after it for sign -off by the appropriate parties after its satisfactory completion. 3) Checklists to be used to control and document the required tests. Provide a check box for every step to be performed during the test. 4) Sign -off areas where applicable. 5) Area for additional notes. 6) Include "punch list" forms with the test procedures to document issues that arise during the testing. Punchlist forms, at a minimum, shall include an issues description field; a resolution description field; and a sign -off area for the appropriate parties. 2. Test Report Submittals: a. Within 14 days after completion of the factory test, submit the completed Test Report. b. The test report shall include a copy of the signed off test procedure forms. Testing shall not be considered complete until the signed test procedure forms have been submitted and favorably reviewed. Submittal of other test documentation, including "highlighted" wiring diagrams with technician notes, are not acceptable substitutes for the formal test documentation. L. Cutover Plan Submittals: 1. System cutover plans shall be submitted in three stages, Preliminary, Draft, and Final. 2. Submit one overall cutover plan for all WTPs inclusive of Centralized SCADA, and one per WTP. 3. Preliminary plans shall include but not be limited to the following: a. Purpose and scope b. System overview C. Pre-cutover requirements 1) Risk assessment 2) Pre-cutover testing CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 1— AD4 4061 13 SCADA SYSTEM GENERAL PROVISIONS Page 27 of 32 3) Training 4) Communication Plan d. Cutover procedure 1) Step-by-step process 2) Roles and responsibilities 3) Shutdown durations and requirements 4) Timing and scheduling 5) Contingency plans e. Documentation and reporting 1) Cutover report 2) Lessons learned 4. Develop system cutover plans in close coordination with the City through Cutover Planning Coordination Workshops. 5. Preliminary cutover plans shall be provided to the City no less than four (4) weeks prior to the start of System Cutover Planning Coordination Workshops. 6. All review comments and markups on the Preliminary submittals that are returned to the Contractor, and feedback received during the coordination workshops, shall be fully addressed and incorporated into the cutover plans prior to submitting the Draft submittals. 7. Final overall and individual WTP cutover plans shall be submitted after all the Cutover Planning Coordination Workshops have been completed. All review comments and markups on the Draft submittal that are returned to the Contractor, and feedback received from the City during the coordination workshops, shall be fully addressed and incorporated prior to submitting the Final cutover plans. 8. The Final overall and individual WTP cutover plan s must be reviewed and approved by the City prior to the start of field cutover and startup activities for the respective plant by the Contractor. M. Start-up and Field -Testing Submittals: 1. WTP PLC / OIT / IPC / HMI Sign -Off Forms: a. PLC I/O Status Sign -Off Forms shall be used to organize and track a system's inspection, adjustment, and calibration. b. Submit separate Input/Output Status Sign -Off Form for each system. C. The form shall include a table based on the project PLC I/O list. The table shall include the following columns at minimum: 1) PLC Name 2) Signal Tag 3) Description 4) Range or active state when event or alarm state is reversed 5) Drawing Reference 6) Signal Type 7) Rack No. 8) Slot No. 9) Channel No. 10) Instrument Alarm Setpoint 11) Calibration, Configuration, and Wiring Complete (signoff area) with Date 12) IO Testing from the field to the OIT (signoff area) with Date, as applicable 13) IO Testing from the field to the HMI (signoff area) with Date 14) IO Testing from the OIT to the field (signoff area) with Date, as applicable 15) IO Testing from the HMI to the field (signoff area) with Date CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 1— AD4 4061 13 SCADA SYSTEM GENERAL PROVISIONS Page 28 of 32 16) Notes 2. Submit Test Procedure Submittal for each control strategy to be tested, including but not limited to the following: a. For PLC Category A processes, confirm complete functionality of the PLC/HMI and/or OIT/IPC or portion of the process meeting the Functional Control Narratives developed. This includes but is not limited to the items below: b. Manual operation of the process and/or equipment. C. Automatic operation of the process and/or equipment. d. Mode operation of the process and/or equipment. e. Alarm notification and escalation f. Historian point confirmation and data validation g. Local plant report population and functionality h. Diagnostics for network or devices i. Data entry / limits j. Security k. Procedures for testing safety interlocks. 1. Procedures for testing all related alarms. in. Associated Centralized SCADA HMI Screens. Submit Test Procedure Submittal for the Centralized SCADA System. a. Procedure shall include confirming complete functionality of the centralized SCADA and data/reporting platform, data traffic, latency metrics, remote alarm notification, tablet deployment/screen functionality/data entry. The procedure should include, but is not limited to, testing of the items below: b. Remote Alarm Notification. C. Centralized HMI Platform. d. Tablet functionality including screens, data entry, data backfill on communication loss. e. Data traffic and performance f. Data validation and database population g. Security h. Business and central operational reports N. Operational Availability Demonstration (OAD) Submittals: 1. For each OAD, submit an OAD Period Letter indicating the start date, period, and proposed end date of the OAD. The start date shall be signed by all applicable parties indicating commencement of the OAD. Leave space for: (1) Listing of corrective actions. In case of any failures encountered during the OAD, attach all malfunction/repair forms generated; (2) Signatures and attestation of the successful completion of the OAD. 2. Submit SCADA System Malfunction/Repair Reporting Form to be used for City's documentation of system failures, Contractor notifications, arrivals, and repair actions during the OAD. Format of the form shall be approved by the City prior to the start of the OAD. 3. Upon successful completion of an OAD, provide the Period Letter signed, as well as any Malfunction/Repair Reporting Forms related to corrective action and/or restart of the OAD. O. Training Plan Submittals: 1. Preliminary Training Plan Submittal: CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 1— AD4 4061 13 SCADA SYSTEM GENERAL PROVISIONS Page 29 of 32 a. Prior to the preparation of the Final Training Plans, submit outlines of each training course including course objectives and target audience, resumes of instructors, prerequisite requirements for each class, and samples of handouts for review. b. Provide preliminary training plan as one complete submittal. Provide a table of contents. Provide a separate section for each course. C. Include tentative schedules for all classes for approval. Indicate times available that comply with the City's three shift schedule. d. For PLC Software Training Course at the Manufacturer's facility, provide facility's address, training course, and a minimum of three optional dates for City's selection. 2. Final Training Plan Submittal: a. Upon receipt of the City's comments on the preliminary training plan, submit the specific proposed training plan for each course. b. Submit each training plan under a separate submittal. C. The training plan shall include: 1) Definitions, objectives, and target audience of each course. 2) Schedule of training courses including dates, duration, and locations of each class. 3) Complete copy of all proposed handouts and training materials. Training information shall be logically arranged in a three-ring binder with all materials reduced to a maximum size of 11 inch by 17 inch, then folded to 8.5 inch by 11 inch for inclusion into the binder. 4) Reservation confirmation from manufacturer with names of City's staff and dates of training. P. Record Drawings and Final System Documentation: 1. Prior to submitting record drawings and final system documentation, provide a Table of Contents and Listing of the submittals intended and grouping of documentation to meet the Record Drawing and Final System Documentation requirements. Provide separate submittals for key project components. At minimum provide a submittal for each WTP, and other key system components. Each submittal should include where applicable: a. Finalized HMI documentation: mapping (HMI -PLC -Database), control narratives, conventions (tag naming, navigation, color, text), alarm list, historical data collection, frequency, method on data capture; averaging or raw, trending, scripting, templates, reports library and features. b. Finalized PLC documentation: Routines, interlocks, and function blocks descriptions. c. Finalized network and security documentation. d. User manuals for Operators, PLC programmers, and SCADA personnel. e. All factory, system testing, cutover and OAD documentation. 2. Submit in accordance with Section 0178 39 — Project Record Documents, and Section 01 78 23 Operations and Maintenance Data. 3. The Final System Documentation shall consist of operations and maintenance manuals as specified herein. 4. The operations and maintenance manuals shall, at a minimum, contain the following information in addition to that specified in Section 0178 23 — Operations and Maintenance Data: a. Instrument and Equipment Lists shall have the following: 1) The Equipment lists shall be developed and provided in Excel format. CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 1— AD4 4061 13 SCADA SYSTEM GENERAL PROVISIONS Page 30 of 32 2) Shall include manufacturer, model number, serial number, location, manufacturer phone number, local supplier name, local supplier phone number, completion year, replacement cost, and any other pertinent data. 3) Shall include cover page for each device, piece of equipment, and Original Equipment Manufacturer (OEM) software that lists, at a minimum, date, product name, manufacturer, model number, Location(s), and power required. Preferred format for the cover page is ISA S20, general data sheet; however, other formats will be acceptable provided they contain all required information. 4) Final vendor O&M documentation for each device, piece of equipment, or OEM software shall be either new documentation written specifically for this project or modified standard vendor documentation. All standard vendor documentation furnished shall have all portions that apply clearly indicated with arrows or circles. All portions that do not apply shall be neatly lined out or crossed out. Groups of pages that do not apply at all to the specific model supplied shall be removed. 5) For any component requiring dip switch settings or custom software configuration, that information shall be included along with the corresponding data sheets and O&M information. b. As -Built Drawings: As specified in Section 01 78 39 — Project Record Documents, and the following: 1) Complete as -built drawings, including all drawings and diagrams submitted as part of the Submittal requirements described in this section. 2) As built documentation shall include information from submittals, as described in this section, updated to reflect the as -built system. Any errors in or modifications to the system resulting from the Factory and/or Functional Acceptance Tests shall be incorporated in the As -Built Drawings. 3) Provide electronic copies of drawings in native format as specified below. 4) As -Built Drawing submittal shall include a copy of the actual redlined drawings and other documents generated during factory test, field startup of the system(s). Electronic O&M and Final Project Files: In addition to the operations and maintenance submittal requirements specified elsewhere in the Contract Documents, provide an electronic version of all information contained in the O&M manual, along with any software backups of installation files, configuration files, and related items on electronic media. The electronic version shall be submitted on a portable hard drive furnished by Contractor. Submit one portable hard drive for each water treatment facility loaded with facility specific files. Label each hard drive with facility name and date of compilation. In addition to the above, submit the following: a. A portable hard drive loaded with all final electronic files to the City as a backup for all facilities. Portable hard drive shall be USB 3.0 and sized to accommodate all required electronic files as specified plus 20% spare storage capacity. Hard drive shall have 4TB of memory minimum and be formatted for Windows operating system. b. Electronic files shall be organized in a folder structure to permit ease of use. Provide "Read Me" file in root directory which documents portable hard drive contents, file structure, backup dates, and related information. C. Text files shall be supplied in both Microsoft Office format and Adobe Acrobat format. Adobe Acrobat files shall include bookmarks for all document sections. d. Electronic O&M Information: CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 1— AD4 4061 13 SCADA SYSTEM GENERAL PROVISIONS Page 31 of 32 1) Provide electronic files for all approved shop drawings and custom -developed manuals in this project including O&M and training manuals in accordance with Section 01 31 26 — Electronic Communication Protocols. 2) Provide back-up copies of files from each computer system. Back-up files shall be grouped and identified by computer name. File backups shall be date stamped for after Substantial Completion. 3) Provide original software license certificates and related information. The information provided shall include serial numbers, license agreements, User Registration Numbers, and related information. 4) Provide copies of all project related software installation files on electronic media. Software installation files shall include disc images of complete manufacturer software packages. Include a software list identifying all provided software installation files. The information provided on the list shall include, software name and manufacturer, software version, installed location(s), and related information. 5) Submit copies of programming and configuration files developed specifically for the Project in accordance with Section 01 78 23 — Operations and Maintenance Data. Electronic submission of programming and configuration files shall be in native file format and Adobe Acrobat format. 5. Electronic O&M and Final Project Files Local Backup: In addition to providing a portable hard drive with all electronic O&M and project related files, Contractor shall copy the entire contents of the submitted portable hard drive for each facility onto the storage location(s) as specified by the City. 7. Provide updated revised PLC and HMI Configuration Standards, with Revision Note dated and indicating these were provided with Final Project Documentation. PART 2 — PRODUCTS 2.1 THIRD -PARTY SOFTWARE QA. Coordinate with the City to transfer all licensing ownership to the City prior to field deployment. QB. The software listed below has been identified necessary to support and provide the desired functionality for the SCADA platform. 1. SNMP Driver: Communication software for integration of UPS systems, and other SNMP-supported network devices, with Ignition. It shall be able to communicate with up to 50 devices at each WTP. Provide software and license for each WTP SCADA server, Centralized SCADA, and the Test Bench. Manufacturer shall be Kymera Systems or approved equal. 2. GE Driver: Communication software for integration of the existing GE 90-30, RX3i, and RX7i PLC systems with Ignition, as required. Provide software and license for Eagle Mountain WTP and Test Bench SCADA servers. Manufacturer shall be PTC Kepware or approved equal. PART 3 EXECUTION (NOT USED) + + END OF SECTION + + CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 1— AD4 4061 13 SCADA SYSTEM GENERAL PROVISIONS Page 32 of 32 + +THIS PAGE INTENTIONALLY LEFT BLANK+ + CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 ATTACHMENT 1- AD4 40 61 21 SCADA SYSTEM FACTORY ACCEPTANCE TESTING Page 1 of 8 SECTION 40 6121 SCADA SYSTEM FACTORY ACCEPTANCE TESTING 17.11.14 a MCI go2191;7:\Il 1.1 DESCRIPTION A. Scope 1. Contractor shall provide all labor, materials, equipment, and incidentals as specified and required for testing of the Supervisory Control and Data Acquisition (SCADA) System hardware and software at the Contractor's facility to verify that SCADA System software applications function properly and comply with the functional and performance requirements of the Contract Documents. 3. Unless there is specific and approval otherwise with at least 90 days in advance, the Contractor shall use the SCADA computer/network hardware and software furnished for the project (by the City) for all Factory Acceptance Tests (FATS), either through remote access from Contactor's facility or by conducting the FATs on site. 4. If Work at multiple Water Treatment Plants (WTPs) is happening concurrently and the FATS for multiple WTPs are to be conducted close to each other, each WTP shall have a separate FAT with a minimum of three weeks between each FAT. The sequence of PLC system FAT conducted for a facility shall match the order and sequence of work established during design phase. 5. Contractor shall develop and receive approval from the City on all required SCADA system application submittals prior to the first FAT of a given facility. 6. SCADA System Factory Testing shall use actual HMI software with license furnished for the project. Contractor shall be responsible for resolving all SCADA system software application issues encountered during the FAT. Any encountered SCADA computer and/or network failures during the FAT shall be addressed by the City. 7. All required software applications shall be tested and approved by the City prior to deployment in the production environment. At a minimum, the Process Control System Factory Testing shall include the following: a. Unwitnessed Factory Tests (UFTs). b. Witnessed Factory Tests (WFTs). 8. General UFT and WFT requirements follow. a. For all tests, external power and network cabling shall be available temporarily as required to meet subsequent factory testing requirements. b. Provide working space, surfaces, and chairs for City and Manufacturer Representatives for the UFTs and WFTs. 11. Contractor shall utilize PLC simulation blocks for simulating field conditions to test control functions. Contractor shall connect the simulation points to the PLC tested prior to the beginning of the test. 12. Contractor shall advise the City in writing of the scheduled dates for SCADA System factory testing. Refer to Article 1.2 and Section 40 61 13 — SCADA System General Provisions for submittal requirements. 13. City and/or City's representative shall be present at Contractor's facility during each WFT. Presence of City during testing does not relieve Contractor from complying CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 40 61 21 SCADA SYSTEM FACTORY ACCEPTANCE TESTING Page 2 of 8 with the Contract Documents and shall not indicate or imply acceptance of the configured HMI software or equipment. 14. Should a factory test fail to comply with the Contract Documents, necessary changes and corrections shall be made and the entire system retested until acceptable results are achieved. B. Provide the following minimum tests. If more are determined necessary then include in schedule and follow the requirements for notification, testing plans and execution as noted herein. 1. UFT/WFT-1 Eagle Mountain WTP and associated Centralized SCADA integration 2. UFT/WFT-2 West Side WTP and associated Centralized SCADA integration 3. UFT/WFT-3 North Holly WTP and associated Centralized SCADA integration 4. UFT/WFT-4 South Holly and associated Centralized SCADA integration 5. UFT/WFT-5 Rolling Hills WTP and associated Centralized SCADA integration 6. UFT/WFT-6 Centralized SCADA D. Coordinate readiness of all required hardware and software with the City well in advance of any FAT. The City will be responsible for all SCADA asset procurement and installations and will configure all computer and network hardware. Any remaining work shall be conducted by the Contractor. Refer to Attachment 7 — SCADA Assets Responsibility Matrix for details. E. Related Sections: 1. Section 01 11 13 — Summary of Work 2. Section 01 14 16 — Coordination with City's Operations 3. Section 40 61 13 — SCADA System General Provisions. 4. Section 40 6123 — SCADA System Field Assessment, Testing, and Start-up 5. Section 40 6126 — SCADA System Training 6. Section 40 68 63 — SCADA System Programming and Configuration 1.2 SUBMITTALS A. Obtain City's acceptance for each Testing Plan not less than 30 days prior to scheduled start of factory test. B. Submittals shall comply with the requirements specified in Section 40 61 13 — SCADA System General Provisions, and this section. In addition: 1. Submit an Overall Factory Testing Schedule for all equipment under the project, showing each test duration, estimated schedule, and panels to be tested. C. For each Factory Test, submit the following: 1. Test Plan. 2. Test Report. 1.3 TESTING — GENERAL A. Each test shall use simulated field signals. Each input/output point shall be tested from field terminals in the panel to the workstation HMI display screen and the display on the Operator Interface Terminal (OIT), where applicable. The tests shall verify that all panel hardware and internal panel wiring between components are functioning as intended. CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 40 61 21 SCADA SYSTEM FACTORY ACCEPTANCE TESTING Page 3 of 8 a. The UFT shall test 100% of the I/O. b. The WFT shall test a minimum of 25% of the I/O. B. All tests shall be conducted in accordance with prior City -approved procedures, forms, and all checklists as submitted by the Contractor under Article 1.2 of this section. C. Copies of the signed -off test procedures, forms, and checklists will constitute the required testing documentation. D. Contractor shall provide all special testing materials and equipment. Wherever possible, perform tests using actual process variables, equipment, and data. Where it is not practical to test with real process variables, equipment, and data, provide suitable means of simulation. These simulation techniques shall be defined in the test procedures. E. Contractor shall coordinate all required testing with the City. F. For all testing, the Contractor shall be responsible to furnish the following: 1. Location and space for testing. 2. The services of field service specialist(s) 3. All special calibration and test equipment 4. All required labor. 5. Any necessary power, network connections, temporary cabling to support the testing. G. The City reserves the right to test or retest all specified functions, whether or not explicitly stated on the Test Procedures, as required to determine compliance with the functional requirements of the overall system. Such testing required to determine compliance with the requirements described in these documents shall be performed at no additional cost to the City. The City's decision shall be final regarding the acceptability and completeness of all testing. H. No equipment shall be shipped until the City has received all test results and a written approval has been transmitted from the City to the Contractor stating the system is released for shipment to the site. Any panel shipped to the site without City's release letter will be cause for withholding payment for that panel until the final system cutover is performed at the end of the project. I. Correction of Deficiencies 1. All deficiencies in workmanship and/or items not meeting specified requirements shall be corrected to meet specification requirements at no additional cost to the City. 2. Testing, as specified herein, shall be repeated after correction of deficiencies is made until the specified requirements are met. This work shall be performed at no additional cost to the City. PART 2 — PRODUCTS (NOT USED) PART 3 — EXECUTION 3.1 UNWITNESSED FACTORY TESTING (UFT) CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 40 61 21 SCADA SYSTEM FACTORY ACCEPTANCE TESTING Page 4 of 8 A. The UFT is conducted without the City present. The intent is for the Contractor to test and document proper operation of 100% of the equipment, connections, input/output and communications. B. The purpose of the UFT is for the Contractor to confirm the readiness for the WFT. C. Perform all pre -work on the required SCADA assets in coordination with Water IT to test the virtual environment, inclusive of all software pre -installed and configured by the City. Install, configure, and test the City -furnished Ignition and SQL Historian software. Refer to Attachment 7 — SCADA Assets Responsibility Matrix for division of work with Water IT as it relates to procurement and configuration of SCADA system assets. D. During the tests, all -digital system hardware and software shall be operated for at least 72 hours continuously without component failure to verify the system is capable of continuous operation. E. Upon successful completion of the UFT, the Contractor shall compile all test documentation into a report and submit to the City. Submission of successful UFT results can be no less than 30 days prior to scheduling the WFT. The City requires this time to schedule and identify personnel that will attend the test. F. Successful completion of the UFT and submission of associated documentation is a pre- requisite for scheduling the WFT. 3.2 WITNESS FACTORY TESTING (WFT) A. The following are the minimum pre -requisites to performing the WFT and the amount of time prior the respective pre -requisite must be complete prior to scheduling the WFT. 1. Completed associated UFT and submitted Documentation, 30 days. 2. Approved Submittals for all software, HMI graphics or other project work to be tested, 45 days. 3. Approved WFT Testing Plan, 30 days. B. The following documentation shall be made available to the City at the test site both before and during factory testing: 1. All related Drawings, Design additions, Design modifications, addenda, and change orders. 2. Master copy of the test procedure. 3. Bill of materials of the computer/PLC/LAN equipment and software to be tested including make, model, and serial number. 4. Design -related hardware submittal applicable to the equipment being tested. 5. Software licenses. 6. Software documentation submittal. C. The daily schedule during these tests shall be as follows: 1. Morning meeting to review the day's test schedule. 2. Scheduled tests and signoffs. 3. End of day meeting to review the day's test results and to review or revise the next day's test schedule. CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 40 61 21 SCADA SYSTEM FACTORY ACCEPTANCE TESTING Page 5 of 8 4. Unstructured testing period by the witnesses. D. During the factory test, for a period of time equal to at least 20 percent of the test duration, the City shall have unrestricted access to the system to perform any additional testing desired or to re -test any previously tested components. E. System Inspection: 1. Perform a system audit to verify all components have been staged for the test. 2. Inspect the system interconnection to verify all components have been connected as per the Design Documents and approved Submittals. F. System Hardware Operational Testing: 2. Test remote I/O, operator interface terminals, and similar devices, to verify that communication between units' functions properly. 3. Perform an integrated system test (for the specific batch), with all monitoring and control system equipment connected (excluding field sensors and instruments), to verify that equipment performs and functions properly as an integrated system. During the factory test, simulate field sensors and instruments using appropriate signal generators, switches, and jumper cables. 4. Tests to be performed during the system hardware operational testing shall include, but not be limited to, the following: a. I/O Point Checkout: An I/O point checkout of each I/O type shall be performed to verify proper operation of the input/output points. The verification of the signals shall be accomplished via the use of the PLC programming software. At a minimum, the I/O checkout shall consist of the following four steps: 1) Digital input signals shall be jumped at the field terminal strip for verifying proper alarming, statuses, interlocks, etc. Verify these field conditions are indicated at the HMI screens and the desired control functions are noted in the PLC programs. 2) Analog input signals shall be simulated using signal generator(s) connected to field terminals for verifying proper readings or related functions. Analog values shall be verified at zero percent, 25 percent, 50 percent, 75 percent, and 100 percent of full scale. The appropriate scaled value shall be verified utilizing the tools available in the PLC programming software. Testing shall include out of range input output signals (over and under scale) for a given input point. 3) Digital output signals shall be tested and verified by simulating required field inputs to the actual process or equipment control functions in the PLC programs or actions executed on the HMI display for activating the output. Field signals shall be simulated by using signal generator(s) connected to field terminals or jumpers as required. Activation of output signals shall be verified by indication on the HMI display (if involved), and pilot lights or relays on the test bench connected to the field terminals in the tested panel. 4) Analog output signals shall be tested and verified by simulating required field inputs to the actual process or equipment control functions in the PLC programs for activating the output. Execution of proper output values by the PLC program shall be verified at the HMI display (if involved) and by utilizing a digital multimeter. b. Equipment Operability Check: CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 40 61 21 SCADA SYSTEM FACTORY ACCEPTANCE TESTING Page 6 of 8 1) Test each input/output device and component to verify operability. If panel or device being tested contains pneumatic systems, test the instruments associated with such systems to verify that calibration. C. Stand-alone Unit Check: Test all system hardware components to verify proper operation of the equipment as stand-alone units and as a system. Tests shall include the following: 1) AC/DC power checks. 2) Power fail/restart tests. 3) Verify that network switch, PLC/RIO racks, DC power supplies, panel light, utility receptacle, and other panel components are powered by separate circuits. 4) Verify that quantity of circuits assigned to power field instruments corresponds to approved Shop Drawings and approved other Contractor submittals. 5) Demonstrate the ability of the UPSs to meet the runtime requirements upon loss of power. d. Logical Failure Check: Demonstrate logical failure conditions for control strategies (i.e., instrument failures, equipment failures, loss of communication between the Process I/O Server and the PLC, loss of peer -to -peer communication, etc.). e. For new PLCs, in addition to the testing above, perform a complete functional logic check, including simulation of all loops, control functions and alarms. H. Configured Human Machine Interface Software Testing: 1. Contractor shall demonstrate that all configured HMI displays comply with the standards shown and described in Attachment 1 — PLC and HMI Configuration Standards and provide the required operator interface for process and equipment monitoring and control. 2. Preparation: a. Configured HMI software performance shall be tested using the workstation connected to network switches in network cabinets and the PLC systems tested. 3. Testing: a. Contractor shall demonstrate system software utility programs and system software security programs incorporated into the control system are functioning as specified and as intended. b. Demonstrate the monitoring and control information displayed on each HMI screen, based on simulation of each associated point for each screen, in accordance with test procedure approved by City. Where necessary, simulation through forced values in the PLC programming is acceptable. In addition, City may randomly select, at the time of the factory test, additional inputs, and outputs to be simulated in quantity not less than five percent of total I/O quantity. Demonstrate that monitoring, and control application software associated with I/O points performs and functions as intended. C. Demonstrate communications between integrated system elements; include such demonstration in the testing procedure submittal, where applicable. d. Operator Interfaces: 1) During factory test, demonstrate overall display structure, including environment configurations, passwords, security, and other parameters and functions. CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 40 61 21 SCADA SYSTEM FACTORY ACCEPTANCE TESTING Page 7 of 8 2) Review menu display contents to demonstrate how an operations person will navigate within the overall display structure. 3) Review each graphic display for correctness relative to layout, symbols, color scheme, and other requirements. 4) Demonstrate operation of standard alarm management displays (current alarm display, alarm history, and similar alarm displays). 5) Perform demonstration of each type of report specified. Printing shall be an integral part of the report demonstration. I. Activities specific to WFT-1-5. 1. Demonstrate setup of the Virtual Environment, virtual machines setup and configuration of network communications, equipment, software/licensing. 2. Demonstrate thin client communications. 3. Demonstrate primary/redundant server operation. 4. Demonstrate server allocations. 5. Demonstrate all installed software, including operating system, and 3rd party software and Ignition software. 6. Demonstrate network communications. 7. Demonstrate Historian operation and data flow 8. Demonstrate configuration of Network Attached Storage and data/image backups. 9. Demonstrate capability/setup of local Historian and operational reports. 10. Demonstrate capability/setup of data flow and replication from local Historian to Central Historian. 11. Demonstrate capability/setup of respective HMI screens on Centralized SCADA 12. Demonstrate operation of respective alarm notifications. Activities specific to WFT-6. 1. Demonstrate setup of the Virtual Environment, virtual machines setup and configuration of network communications, equipment, software/licensing. 2. Demonstrate server allocations. 3. Demonstrate all installed software, including operating system, and 3' party software and Ignition software. 4. Demonstrate Centralized historian operation. 5. Demonstrate configuration of Network Attached Storage and data/image backups. 6. Demonstrate capability/setup of business reports and dashboards. 7. Demonstrate functionality of tablets as well as remote access to Centralized Ignition application and business reports. 8. Demonstrate operation of remote alarm notification. K. Factory Test Acceptance Criteria: 1. The system must operate continuously throughout the factory test without failure, except where initiated per the established test procedures. Any unanticipated failures may, at the City's option, result in the overall factory test being deemed unsuccessful. Factory Test failure criteria shall include one or more of the following: a. Nonconformance to the items specified for the Factory Test. b. Nonconformance to the HMI configuration standards shown and described in Attachment 1 — PLC and HMI Configuration Standards and any facility specific requirements added during HMI configuration coordination workshops. C. Failure or nonfunctioning of any communication link. CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 40 61 21 SCADA SYSTEM FACTORY ACCEPTANCE TESTING Page 8 of 8 d. More than 10 I/O point assignment errors against PLC database per controller. e. More than one data link assignment error per two HMI display screens. 2. Do not ship the equipment from the factory until City accepts the factory test results submittal and transmits a written approval letter stating released for shipment. 3. Modifications, if any, to documentation as a result of the factory tests shall be completed before shipping the SCADA system computers and configured HMI software. 4. Should a factory test run fail to comply with the Contract Documents, necessary changes and corrections shall be made and the entire system retested until acceptable results are achieved. L. All deficiencies identified during a FAT that does not add up to a FAT fail shall be corrected and re -tested prior to completing the factory test as determined by the City. M. Completion of Factory Test: 1. Upon completion of the factory test, the Contractor shall submit the Test Report to the City. Test Report shall include certified copies of all test data, logs, and procedures followed during testing. + + END OF SECTION + + CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 40 61 23 FIELD ASSESSMENT, TESTING, AND START-UP Page 1 of 6 SECTION 40 6123 SCADA SYSTEM FIELD ASSESSMENT, TESTING, AND START-UP PART 1 - GENERAL f 11aIII a1X.1 Y11=114ulgloo10.1101011111I:\:7HillatiILIEll] y1:3Iass 1I y A. Contractor shall provide all labor, materials, equipment, and incidentals as shown, specified, and required to perform field assessment of the existing PLC and SCADA systems for all 5 WTPs and interface with the City's existing data warehouse, as required to support Contractor's design of the replacement SCADA system. B. Contractor shall perform testing, start-up, and put in service the new Fort Worth Water Department (FWWD) Supervisory Control and Data Acquisition (SCADA) System as described in this Contract. C. Contractor shall perform testing and start-up of all hardware and software components that comprise the FWWD SCADA System including but not limited to all SCADA assets furnished for this project, and all configured HMI, PLC, and OIT applications, Historians, operational and business reports, alarm notification, and tablet interface. D. Related Sections: 1. Section 01 11 13 — Summary of Work 2. Section 01 14 16 — Coordination with City's Operations 2. Section 40 61 13 — SCADA System General Provisions. 2. Section 40 6121 — SCADA System Factory Acceptance Testing 3. Section 40 6126 — SCADA System Training 4. Section 40 68 63 — SCADA System Programming and Configuration 1.2 SUBMITTALS A. Comply with the requirements specified in Section 40 61 13 — SCADA System General Provisions. PART 2 - PRODUCTS (NOT USED) PART 3 - EXECUTION 3.1 EXISTING PLC LOOP TESTS A. Test Equipment: Contractor shall provide all test equipment necessary to perfonn the testing during system assessment. B. Loop Inspections and Tests: 1. Field loop inspections shall be performed by the Contractor for all existing PLC systems in Category A. Refer to Attachment 6 — Existing WTP PLC Systems Table for details. CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 40 61 23 FIELD ASSESSMENT, TESTING, AND START-UP Page 2 of 6 1. The entire I/O loop shall be checked to document existing conditions as it pertains to field device operation, field wiring connection, PLC hardware functionality, PLC and SCADA/OIT application programming. 2. Submit the Loop/Component Inspections and Tests Submittal prior to initiating any testing. 3. Loop/Component Inspections and Tests shall be performed using City -approved forms and checklists. C. Loop Checks: 1. Contractor with City's electrician and/or maintenance staff shall test all existing UO loops from the field device to the PLC terminals, and first verify PLC receives the signal, then verify the status and/or correct value along with any signals derived from the original signals is displayed on the existing SCADA HMI, and local OIT if applicable. If the loop is nonfunctional due to field conditions such as existing field instrument, field device, and/or existing field wiring, loop shall be tested from the field wiring terminals in the PLC panel using applicable test instruments. 2. If the loop is nonfunctional due to issues with the existing PLC hardware such as I/O module or channel, loop shall be tested from the PLC logic. 3. After successfully testing all I/O from the field devices to the PLC terminals, test all I/O from the existing SCADA workstation, and local OIT if applicable, to the field device. 4. Loop checks shall be documented using City -approved test forms. D. Upon successful completion of all field loop checks for each plant, Contractor shall submit to the City a loop inspection report documenting the detailed condition of existing PLC I/O and associated field devices, field wiring, PLC hardware, PLC logic, and HMI/OIT graphical interface. 3.2 SYSTEM FIELD TESTING AND START-UP A. Contractor shall perform the following: 1. Check and approve the installation of all SCADA System components and all cable and wiring connections between the various system components prior to placing the various processes and equipment into operation. 2. Conduct a complete system checkout and adjustment, including verification of data transmission between the upgraded PLC and other required PLCs, checking safety interlock functions, and testing of final control actions. When there are future operational functions included in this work, they should be included in the system checkout. All problems encountered shall be promptly corrected to prevent any delays in the start-up of the various unit processes. B. Contractor shall be responsible for initial operation of monitoring and control system and shall make any required changes, adjustment, or replacements for operation, monitoring and control of the various processes and equipment necessary to perform the functions intended. C. Test Equipment: Contractor shall provide all test equipment necessary to perform the testing during system testing and start-up. D. Loop Checks: CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 40 61 23 FIELD ASSESSMENT, TESTING, AND START-UP Page 3 of 6 1. Contractor with City's electrician and/or maintenance staff shall test I/O loops from the field device to the PLC terminals, and first verify PLC receives the signal, then verify the status and/or correct value along with any signals derived from the original signals is displayed on the SCADA HMI, and local OIT if applicable. If the loop has been found to be nonfunctional as part field assessments due to field conditions or PLC hardware issues, loop shall be tested from the PLC logic. 2. If the loop contains points that are historized, verify tags and tag integrity at the Historian. 3. After successfully testing all I/O from the field (or PLC) to the graphical displays, test all I/O from the SCADA workstation, and local OIT if applicable, to the field device. For loops with documented field -related issues, testing shall be limited from HMI/OIT to the PLC logic. 4. Loop checks shall be documented using City -approved Input/Output Status Sign -Off forms. E. Contractor shall perform testing to verify that all equipment and programmed software of the respective process or system are operating properly and that the intended monitoring and control functions are fully implemented and operational. Contractor shall correct any defects or problems found during system test. After correcting the issue, the system shall be retested to demonstrate proper operation. All testing shall be documented using City - approved System Field Testing and Start-up Plans. F. Following the demonstration of system functions, the SCADA System for the respective process, equipment, or system shall be running and fully operational for a continuous 72- hour period. The Operational Availability Demonstration specified below for each WTP shall not begin until the continuous 72-hour system test has been successfully completed for that plant and City agrees that the Operational Availability Demonstration can begin. G. If it was determined during design phase that the SCADA system applications at each Water Treatment Plant (WTP) to be implemented and put in service in batches, the Operational Availability Demonstration specified below shall not begin until the continuous 72-hour System Field Tests of all batches at a given WTP is complete. H. Contractor shall perform parallel testing of new and existing WTP HMI screens to the extent possible prior to changing IP addresses. I. Field testing shall be in accordance with requirements in Attachment 1 — PLC and HMI Configuration Standards. 3.3 OPERATIONAL AVAILABILITY DEMONSTRATION A. An Operational Availability Demonstration (OAD) shall begin following completion of all system field tests as specified above. 1. Each Water Treatment Plant shall require an OAD. a. Eagle Mountain WTP and associated Centralized SCADA integration. b. W stside WTP and associated Centralized SCADA integration. C. North Holly WTP and associated Centralized SCADA integration. d. South Holly WTP and associated Centralized SCADA integration. e. Rolling Hills and associated Centralized SCADA integration. 2. An OAD shall be provided for the Centralized SCADA. CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 40 61 23 FIELD ASSESSMENT, TESTING, AND START-UP Page 4 of 6 B. WTP OADs: The OAD shall continue until a time frame has been achieved wherein the system (both hardware and software) availability meets or exceeds 99.7 percent for 30 days and no system failures have occurred which result in starting the OAD over again. For the purpose of this OAD, the system will be defined as consisting of the following systems and components as they apply to the respective WTP: 1. Configured PLC software. 2. Configured HMI software at SCADA workstations. 3. Configured Historian software. 4. Configured Report software. 5. Configured Alarm Management. 6. Two -Factor Authentication. 7. Remote Monitoring, Alarming and Trending of the respective WTP SCADA system C. Centralized SCADA OAD: An OAD for the Centralized SCADA shall continue until a time frame has been achieved wherein the system (configured software and hardware) availability meets or exceeds 99.7 percent for 60 consecutive days and no system failures have occurred which result in starting the OAD over again. For the purpose of this OAD, the system will be defined as consisting of the following systems and components: 1. Remote Monitoring, Alarming, Reporting, and Trending all WTP SCADA systems. 2. SCADA Network and communication links for centralized SCADA system. 3. Remote Access Capabilities and Two -Factor Authentication. 4. Business and Central Operational Reports and tablet data entry D. During an OAD the system shall be available to operating personnel for use in normal operation. E. The conditions listed below shall constitute system failures which are considered critical to the operability and maintainability of the system. The OAD shall be terminated if one or more of these conditions occur. Following the correction of the problem, a new 30 consecutive day OAD shall begin. 1. Failure to repair a hardware or software problem within 12 hours from the time of notification of a system failure. 2. Recurrent hardware, network, or software problems. 3. Software problem causing a server or processor to halt the execution. 4. Failure to meet performance standards identified in Attachment I — PLC and HMI Configuration Standards. 5. Failure to meet database traffic performance requirements identified in Section 40 68 63 — SCADA System Programming and Configuration F. The system availability shall be calculated based on the following equation: A = TTO x 100 TTO + TTR where, A = system availability in percent TTO = total time in operation TTR = total time to repair G. Time to repair shall be the period between the time that Contractor is notified of a system failure and the time that the system has been restored to proper operation in terms of hours CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 40 61 23 FIELD ASSESSMENT, TESTING, AND START-UP Page 5 of 6 with an allowance for the following dead times which shall not be counted as part of the time to repair period. 1. Actual travel time for service personnel to get to the Site up to six hours per incident from the time Contractor is notified of a system failure. 2. Time for receipt of spare parts to the plant site once requested up to 24 hours per incident. No work shall be done on the system while waiting for the delivery of spare parts. 3. Deadtime shall not be counted as part of the system available period. The dead time shall be logged and the duration of the OAD extended for an amount of time equal to the total dead time. H. A SCADA System Malfunction/Repair Reporting Form shall be completed by the plant personnel and City to document system failures, to record Contractor notification, arrival and repair times and Contractor repair actions. Format of the form shall be developed and agreed upon prior to the start of the OAD. I. At the successful conclusion of an OAD, arrange for all parties to signoff the form. This shall constitute completion of the associated OAD. Submit all OAD documentation. + + END OF SECTION + + CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 40 61 23 FIELD ASSESSMENT, TESTING, AND START-UP Page 6 of 6 ++THIS PAGE INTENTIONALLY LEFT BLANK++ CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 40 61 26 SCADA SYSTEM TRAINING Page 1 of 6 SECTION 40 6126 SCADA SYSTEM TRAINING PART 1 - GENERAL 1.1 REQUIREMENTS AND RESPONSIBILITIES A. Contractor shall provide all labor, materials, equipment, and incidentals as shown, specified, and required to perform and coordinate all required training at times acceptable to City. B. Contractor shall retain the services of a manufacturer's training instructor to provide programming and configuration training for Programmable Logic Controllers (PLC) and Human Machine Interface (HMI) Software. Training shall be held at a City's Facility directed by City. If Contractor elects to deviate from manufacturer certified trainer providing training courses at the City's Facility, then Contractor shall be responsible for all costs required to hold the training course at the Manufacture's Training Facility to train the required number of personnel. C. Contractor shall provide operational and maintenance training to City's personnel at Water Treatment Plants (WTPs). Contractor's training personnel shall be fully knowledgeable in the treatment processes at WTPs; how to use the configured HMI graphic displays as a tool for operating the plants; and fully knowledgeable in the day-to-day maintenance of the SCADA system furnished. D. Contractor shall be responsible for all costs, including the cost of travel, meals, and lodging if required, associated with training and shall provide all required materials, texts, and required supplies. E. All training shall be conducted in the normal eight -hour working days until the conclusion of the training course. For training at the manufacturer's facility, the course instructor shall be assigned full time and shall not perform other duties throughout the period of the course. F. City's personnel work on a three -shift schedule at the WTPs. Multiple sessions of each operation and maintenance training class shall be provided as required to accommodate these shift schedules. Two (2) training sessions shall be provided for each class. If required, provide one (1) additional training session at no additional cost to the City. Training at a suitable time to include personnel from two shifts shall be considered for all training classes, given that it is approved by the City. G. The Contractor shall video record one session of each training class and provide the recording in a video file format acceptable to the City. H. All training shall be coordinated with the SCADA headend equipment startup and cut -over schedule of each WTP PLC system in accordance with Section 01 14 16 — Coordination with City's Operations, and the following: 1. PLC programming and HMI configuration training by the manufacturer's training instructor shall not be scheduled sooner than sixty (60) days prior to the first Factory Acceptance Test (FAT). This training shall be scheduled so that it has been completed two (2) weeks prior to the start of the first FAT. CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 40 61 26 SCADA SYSTEM TRAINING Page 2 of 6 2. SCADA system upgrade introduction training shall not be scheduled sooner than thirty (30) days prior to the first WTP PLC system cut over. 3. On -site Operational and Maintenance Training by Contractor for the SCADA System headend equipment and software shall start fourteen (14) days prior to the first WTP PLC system cut over. 4. On -site Training by Contractor for the PLC system(s) or process area shall be completed before the respective cuts -over to new SCADA System. 5. On -site training by Contractor for multiple PLC systems in a given process area is acceptable, given that schedule and training duration is acceptable to the City. I. Estimated Number of Students to be Trained: 1. Expect ten (10) City staff to attend the PLC and HMI Software Training provided by the Manufacturer's Training Instructor. 2. At each WTP, City will have the following personnel attend on -site Contractor training courses. a. Administrator Personnel: Four (4) persons. b. Maintenance Personnel: Six (6) persons. C. Operations Personnel: Ten (10) persons. J. Related Sections: 1. Section 40 61 13 — SCADA System General Provisions. 2. Section 40 6121 — SCADA System Factory Acceptance Testing 3. Section 40 6123 — SCADA System Field Assessment, Testing, and Start -Up 4. Section 40 68 63 — SCADA System Programming and Configuration 1.2 SUBMITTALS A. Comply with the requirements specified in Section 40 61 13 SCADA System General Provisions, for submission of the following: 1. Preliminary Training Plan Submittal. 2. Final Training Plan Submittal. 3. Video recorded training session, one per required class. PART 2 - PRODUCTS (NOT USED) PART 3 — EXECUTION 3.1 TRAINING SUMMARY A. The training courses listed in the table below shall, as a minimum, be provided: CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 40 61 26 SCADA SYSTEM TRAINING Page 3 of 6 Minimum Minimum Maximum Course Title Course Number of Number of Intended Duration Courses to Trainees per Audiences (Hours) Host Course 3.2 On -Site Contractor Training: B. SCADA System Upgrade Administrator, Introduction Training 4 6 8 Maintenance, Operator C. Use of SCADA System for Plant 8 6 10 Maintenance, Operations and Controls Training Operator D. SCADA System user group and 8 7 4 Administrator utility maintenance Training Course E. SCADA System Report, Historian, and Tablet Data Entry 2 14 4 Administrator Development Training F. SCADA System Troubleshooting 8 7 4 Administrator, and Maintenance Training Course Maintenance 3.3 Follow-up Training Repeat courses in 3.2 (see 3.2) 2 of each (see 3.2) (see 3.2) 3.2 ON -SITE TRAINING BY CONTRACTOR A. General: 1. Training personnel shall be intimately familiar with the treatment processes, plant operations, control system equipment, its manipulation, and configuration. Training personnel shall command knowledge of system debugging, program modification, troubleshooting, maintenance procedure, system operation, and programming, and shall be capable of transferring this knowledge in an orderly fashion to technically oriented personnel. 2. Coordinate attendee list in advance with the City. B. SCADA System Upgrade Introduction Training: 1. The Contractor shall provide an introductory training course to all personnel which reviews the project specific schedule for PLC system cutovers and how it will impact daily operations during the transition. 2. Provide at minimum six courses, one for each WTP, and one for Centralized SCADA. Adjust the audiences for each in coordination with the City. 2. Training course shall accomplish the following: a. Provide brief introduction on key Contractor personnel that will be performing on -site work. b. Provide brief description of scope of work. C. Provide the cut -over schedule for WTPs and respective PLC systems. d. Identify how staff will be notified of outages or changes to the PLC system cut - over schedule. e. Identify all SCADA System access point types (i.e. Operator Workstations, Engineering Workstations, OITs, and Industrial monitors) and their locations. f. Identify impacts to operations such as Control Room upgrades, operator workstation transitions, and system outages due to PLC system cut-overs. CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 40 61 26 SCADA SYSTEM TRAINING Page 4 of 6 g. Provide all instructions required to operate the process system from both the existing system and new SCADA System workstations at the same time during the transition. h. Provide examples of HMI screen displays showing items that have been or will be transitioned between the existing system and new SCADA System. Refer to Section 40 68 63 — SCADA System Programming and Configuration, for details on "SCADA System Interim Work — Interfacing with Existing System" and transitioning equipment during panel cut-overs. C. Use of SCADA System for Plant Operations and Control Training: 1. The Contractor shall provide operation and control training covering all system components. 2. Provide at minimum six courses, one for each WTP, and one for Centralized SCADA. Adjust the audiences for each in coordination with the City. 3. Training course shall accomplish the following: a. Provide an overview of system hardware and equipment. b. Provide all instructions necessary to operate and utilize all system components. C. Provide all instruction necessary to monitor and control the system processes from the designated PLC system. d. Explain procedures for control of the system during scheduled or rescheduled shutdown and the subsequent start-up. e. Provide instructions for regular caretaking operations. f. The emphasis shall be placed on how to perform set point changes, range changes, diagnostics, and upkeep of documentation. g. Instruction for minor hardware and software maintenance, trouble shooting, and maintenance planning. D. SCADA System User Group and Utility Maintenance Training Course Training: 1. The Contractor shall provide SCADA System user group and utility maintenance training covering all system components. 2. Provide at minimum six courses, one for each WTP, and one for Centralized SCADA. Adjust the audiences for each in coordination with the City. 3. Provide a course covering the structure and the functions of the project specific components including PLC, OIT, HMI and other system components and devices configured by the Contractor. The course shall familiarize the student with the procedures of how to make required changes to user groups, passwords, maintenance of utilities and performing minor programming changes. 4. As a minimum, the course shall cover the following topics: a. The emphasis shall be placed on how to perform minor programming changes, diagnostics, and upkeep of documentation. b. Overview of user groups, passwords, and related utility's structure and relationship to database, HMI display screens, and systems functional capabilities. C. Interaction of user groups accessibility and security levels in relation to system component functions, operating principals, and default settings. d. Loading and start-up of the digital system hardware components. e. Use of system commands. f. Structure and function of programs and control schemes. g. Review of programmed security level and settings and procedures for performing modifications to security settings. CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 40 61 26 SCADA SYSTEM TRAINING Page 5 of 6 h. Procedures to backup and restore of system programs and use of bulk storage device for system backup. E. SCADA System Reports, Historian, and Tablet Data Entry Development Training: 1. The Contractor shall provide report development training. 2. Provide at minimum the following courses: a. Report Development: Six Courses, one for each WTP, and one for Centralized SCADA. b. Historian Configuration: Six Courses, one for each WTP, and one for Centralized SCADA. C. Tablet Data Entry: Two courses. 3. Review the network and data flow for the system. 3. Review how data is transferred amongst the historians and to Centralized SCADA and the Data Warehouse, including sampling, settings, encryption, and other connections. 4. Review Custom Interfaces and how those are setup. 5. Cover the structure and the functions of the report development in Centralized SCADA. The course shall familiarize the student with procedures for modifying existing and creating new report templates, generating reports on demand, and modifying or creating new schedules for report generation. 6. Cover the structure and the functions of the report development software configuration for the WTPs. The course shall familiarize the student with procedures for modifying existing and creating new report templates, generating reports on demand, and modifying or creating new schedules for report generation. 7. For a subset of courses, include training for the Tablet data entry and the audience should be geared to this. Provide information on how to review, adjust, edit the forms, data entry. F. SCADA System Troubleshooting and Maintenance Training: 1. The Contractor shall provide troubleshooting and maintenance training covering all system components. 2. Provide at minimum six courses, one for each WTP, and one for Centralized SCADA. Adjust the audiences for each in coordination with the City. 3. Provide a course covering preventive and troubleshooting maintenance for the project specific system components. The course shall familiarize the student with diagnostic capabilities of the system, and the routine maintenance procedures on the system and the common peripheral devices. 4. As a minimum the course shall cover the following topics for the equipment to be maintained at the site or group of sites being trained on: a. List of equipment and software that is present at each site. b. System overview description of software, components for each site, including logic components. C. Description of the maintenance and troubleshooting aids of the system including software diagnostic programs. d. Review of routine maintenance procedures, as well as non -typical maintenance needs that may be encountered and how to handle. 3.3 FOLLOW-UP TRAINING CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 40 61 26 SCADA SYSTEM TRAINING Page 6 of 6 A. Provide a repeat follow-up training session 3 months after operational availability demonstrations have been completed. This training shall be used as refresher courses and include all final as -built conditions. 1. The Contractor shall provide follow-up operation and maintenance training covering all system equipment provided. 2. Any documentation used in the first training sessions shall be updated to reflect current conditions. 3. The training shall be of the same format, content and duration as the training described in Article 3.1, 3.2 and 3.3, above. + + END OF SECTION + + CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 40 68 63 SCADA SYSTEM PROGRAMMING AND CONFIGURATION Page 1 of 18 SECTION 40 68 63 SCADA SYSTEM PROGRAMMING AND CONFIGURATION PART 1 - GENERAL 1.1 DESCRIPTION A. Scope: 1. Contractor shall program, configure, load, test, tune, document, and place in satisfactory operation all PLC, OIT, HMI and Historical data collection hardware and software, as described herein and as required by other Sections to put in service the new Water Department SCADA systems at the Water Treatment Plants (WTP), Centralized SCADA and Data Warehouse Interface that replace the existing SCADA systems. 2. Contractor shall program, configure, load, test, tune, and place into satisfactory operation all equipment and software noted herein. 3. Contractor shall adhere to constraints and sequencing as identified in Section 00 14 16 — Coordination with City's Operations and related sections. B. Work to upgrade existing HMI: 1. The existing SCADA System HMI graphics at each facility cannot be reused for the new SCADA system. A one -for -one transfer of information from the existing graphics to the new HMI software is also not permitted. 2. The quantity of each type of existing HMI graphic at each WTP is identified in Table 40 68 63-A for information purposes. The new HMI application at each WTP shall be optimized following guidelines set out in Attachment 1 — PLC and HMI Configuration Standards, with the end result being simplified graphics with situational awareness and smart alarm management. All information shown on the existing HMI graphics shall be shown on the new graphics, however, this information shall be presented intuitively and in accordance with the requirements of this section and Attachment 1 — PLC and HMI Configuration Standards. 3. The counts of existing HMI screens and tags are provided for purposes of identifying the existing system. Provide any number of screens and tags in excess of the existing counts as necessary to program the HMI and PLCs using the new standards and as noted in the Work scope. 4. The existing HMI graphics shall be used during coordination workshops with City for comparative purposes to confirm if all existing process controls and variables have been incorporated into the new HMI application. 5. Copies of the existing SCADA system HMI graphics and HMI tag databases are made available in Attachment 3 — Existing HMI Databases, and Attachment 4 — Existing HMI Screens, to provide information on the quantities, type, and complexity of the unit operations at each facility. CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 40 68 63 SCADA SYSTEM PROGRAMMING AND CONFIGURATION Page 2 of 18 Table 02 68 63-A: Existing HMI Graphic Quantities (For Informational Purposes Only) South/ Graphic Screen Type North Rolling Westside Eagle Total Holly Hill Mountain Menus (M) 9 4 2 5 20 Process Overviews (OV) 15 10 7 10 42 Process Graphics (PG) 40 39 30 36 145 Detail Pages (DE) 112 56 53 31 252 Configurations (CF) 85 83 53 73 279 Trend Screens JR) 5 0 18 21 44 Flow Summaries (SU) 25 30 25 20 96 Sequences (SQ) 77 67 68 60 272 Runtimes (RT) 65 37 23 48 167 A/M Stations (AM) 60 60 37 50 197 Faceplate Tuning (CT) 0 17 0 0 17 PLC System Screens (SY) 3 3 6 2 14 Totals 496 406 322 356 1580 Where: • Menus (M): navigations • Process Overviews (OV): Plant overview/process overview of ozone process/specific tanks. • Process Graphics (PG): Drill down to specific process. i.e., details on filter 1, ozone 1. • Detail Pages (DE): Specific calculation or display for specific pumps or motor. i.e., ozone calculations, important parameters displayed to run the process, motor: KWH, AMP, breakers/electrical. • Configurations (CF): Equipment settings, configuration to run it, setpoints. • Trend Screens (TR). • Flow Summaries (SU): WTPs flows, rate of change. • Sequences (SQ): Same as DE screens but more to sequencing of the equipment. • Runtimes (RT): Pump hours summary. i.e., LS pump runtime slide. • A/M Stations (AM): Auto -manual faceplate screen to operate equipment (turn on/turn off equipment). • Faceplate Tuning (CT): Where to tune valve, PID control setting. • PLC System Screens (SY): Status of PLC/RTUs or I/O status/network diagram 6. New HMI Graphics work: a. Graphics update/refresh rate shall be as identified in Attachment 1 — PLC and HMI Configuration Standards. b. Graphics development shall support multiple monitors with resolution of up to 3840 X 2160, auto scaling on monitors and mobile tablets. c. Provide HMI screens in accordance with principles of ISA-101, High Performance Screens, and Attachment 1 — PLC and HMI Configuration Standards. Furnish all CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 40 68 63 SCADA SYSTEM PROGRAMMING AND CONFIGURATION Page 3 of 18 necessary types of screens to meet project requirements: Navigation, Tier I main overview, Tier 11 process overviews, Tier III and IV process and equipment screens, network status, I/O diagnostics status, alarm screens, equipment face plates, control/mode faceplates, trends, etc. d. The HMI graphics pertaining to PLC systems in Category B shall be recreated in Ignition to match functionality (monitoring, alarming, and control) of the original HMI screens, and meet standards in Attachment 1 — PLC and HMI Configuration Standards. e. For PLC systems in Category B, configure the communication address mapping for new Ignition HMI tags to connect with the corresponding existing PLC tags. f. Configure communication with Schneider Electric Modicon M580 PLC systems in Category A using the in -chassis OPC-UA communication modules furnished for the project. Refer to Attachment 7 — SCADA Assets Responsibility Matrix for details. g. Configure communication with existing GE PLC systems using the third -party GE communication driver software furnished for the project. Refer to Article 2.1— Third Party Software in Section 40 61 13 — SCADA System General Provisions, and Attachment 7 — SCADA Assets Responsibility Matrix, for details. h. Configure communication with UPS systems using the third -party SNMP communication driver software furnished for the project. Refer to Article 2.1 — Third -Party Software in Section 40 61 13 — SCADA System General Provisions, and Attachment 7 — SCADA Assets Responsibility Matrix, for details. i. Any new standardized HMI graphic/feature pertaining to PLC systems in Category B that does not have a corresponding PLC tag available shall be disabled, or made un-selectable/invisible, as applicable. j. Use template -based programming where multiple screens share similar control interfaces and/or display elements. k. All calculations currently implemented in the existing HMI application (e.g. combined flow, unit conversions, scaling, etc.) corresponding to tags from PLC systems in Category B shall be replicated in the new Ignition HMI application, unless expressly stated. 1. Where not required by Attachment 1 — PLC and HMI Configuration Standards, existing HMI calculations and/or logic pertaining to PLC systems in Category A shall be replicated in the new Ignition HMI application. in. Refer to Attachment 6 — Existing WTP PLC Systems Table for details of PLCs in each category. C. Work to upgrade existing WTP PLC programs: 1. The existing WTP PLC systems are grouped into two categories as follows for the purpose of defining programming requirements. Refer to Attachment 6 — Existing WTP PLC Systems Table for details of PLCs in each category. 2. Category A: a. Recreate existing programs to meet standards in Attachment 1 — PLC and HMI Configuration Standards. b. Where required by Attachment 1 — PLC and HMI Configuration Standards, the existing HMI calculations and/or logic (e.g. combined flow, unit conversions, scaling, etc.) shall be performed in the respective PLC(s). c. Schneider Electric Modicon M580 controllers shall be integrated with the new Ignition HMI system using the in -chassis OPC-UA communication modules furnished for the project. Refer to Attachment 7 — SCADA Assets Responsibility Matrix for details. 3. Category B: CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 40 68 63 SCADA SYSTEM PROGRAMMING AND CONFIGURATION Page 4 of 18 a. Work on existing PLC programs shall be limited to understanding sufficiently the existing I/O list and functionality to coordinate with the new HMI. b. The existing PLC programs and tag addresses shall remain unchanged. c. The existing GE PLC systems shall be integrated with the new Ignition HMI system using the third -party GE communication driver software furnished for the project. Refer to Article 2.1 — Third Party Software in Section 40 61 13 — SCADA System General Provisions, and Attachment 7 — SCADA Assets Responsibility Matrix, for details. d. Update peer -to -peer data exchange logic as required to maintain communication with Category A PLCs. 4. Prior to any work onsite, the Contractor shall request the IP addressing scheme the City would like to employ at the sites. IP address changes shall be made to all PLCs connected to SCADA at the following sites. As part of the procedure for changing IP addresses, the Contractor shall update the logic for peer -to -peer data exchange in each PLC as required to ensure continued communication between plant PLCs. a. North Holly WTP b. South Holly WTP c. Eagle Mountain WTP d. Rolling Hills WTP 5. Table 02 58 53-B includes the counts of the existing HMI tags related to the PLC systems in each plant for the purpose of identifying the current system. Provide any number of tags in excess of the existing counts as necessary to program the HMI and PLCs in accordance with Attachment 1 — PLC and HMI Configuration Standards, and as noted in the Work scope. Table 02 68 63-B: Existing HMI Tag Quantities (For Informational Purposes Only) Connected HMI Tag North South Rolling Westside Eagle Total Device Type Holly Holly Hills Mountain Category Discrete 1659 2008 3299 2257 0 9223 A PLC Analog 785 1067 1802 962 0 4616 Category Discrete 1312 68 1588 4190 6507 13665 B PLC Analog 855 46 1109 3390 3150 8550 Other Discrete/ 0 161 11 209 157 538 Devices Analog Totals 4611 3350 7809 11008 9814 36592 D. Work on existing WTP Operator Interface Terminals (OITs): 1. Existing OITs are grouped into two categories in line with their respective PLC systems for purpose of defining programming requirements. Refer to Attachment 6 — Existing WTP PLC Systems Table for details of OITs in each category. 2. The applications for existing OITs connected to PLC systems in Category A shall be updated as required to maintain functionality with the upgraded PLC programs. 3. The applications for existing OITs connected to PLC systems in Category B shall remain unchanged. CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 40 68 63 SCADA SYSTEM PROGRAMMING AND CONFIGURATION Page 5 of 18 4. Prior to any work onsite, the Contractor shall request the IP addressing scheme the City would like to employ at the sites. IP address changes shall be made to all OITs associated with PLC systems connected to SCADA at the following sites: a. North Holly WTP b. South Holly WTP c. Eagle Mountain WTP d. Rolling Hills WTP E. Work on new WTP Industrial Panel -Mounted Touchscreen Computers (IPCs): 1. The applications for new industrial panel computers (IPCs) shall be created in Ignition to meet Attachment 1 — PLC and HMI Configuration Standards. 2. For plants where the IP addressing scheme is being updated, the new PC/Touch screens shall be configured with new IP addresses, which will be provided by the City. 3. Refer to Attachment 7 — SCADA Assets Responsibility Matrix for the list of industrial touchscreen computers to be furnished under this Contract (by the City). F. Work to upgrade existing reports, and add Reports, and Data Warehouse Interface. 1. The contractor shall provide a system of Reports that interfaces to existing system's databases (Maximo, LIMS, WIMS). 2. Existing reports and templates are provided in Attachment 5 — Existing Reports. These reports shall be duplicated in the new system even if not specifically noted below. 3. Table 02 68 63-C: Data Interface Connections illustrates the data interface connections to be made. G. In addition to Table 40-68-63-C below, the following is a listing of required Reports and Data Warehouse Interface. Any reports below that are specific to a water treatment plant should be created at the local plant using local SCADA data and reported using the local SCADA HMI reporting software as identified in paragraph 3.14. Unless otherwise noted, all reports listed should use data from the data warehouse with report creation in Inductive Automation Ignition software. 1. Operator/Plant Managers Reports a. WTP: water quality, pump flows, storage, processes, equipment status, daily log, plant daily report 2. Water Director Reports. a. WTP Key Performance Indicators (KPI). 3. Water quality Reports: a. WTPs water quality. 4. Customer City/Billing Reports: a. Comparison calculation with SCADA reading. b. Editable RAW, SLUDGE and PUMPAGE reports. 5. Instrumentation & Electrical Reports: a. Sensor actual mA feedback. b. Calculated values and real field values from field sensors. c. Alarms from sensors (out of range or didn't change for some period of time). d. Pump failed to start counter. e. List of equipment marked/flagged. f. Over -ride (hold value)4-20 mA from the sensors. g. Data source address for each tag. h. PLC statuses and alarms. i. Battery/UPS monitoring via SNMP for all servers 6. Pre-treatment Reports: CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 40 68 63 SCADA SYSTEM PROGRAMMING AND CONFIGURATION Page 6 of 18 a. QA/QC and Non-QA/QC data from LIMS & WIMS Table 02 68 63-C: Data Interface Connections Connection Nature of Data/Report Nature of Connection SCADA to Maximo Pumps runtime from SCADA to generate SCADA Data WO (when certain conditions are met) Warehouse SCADA from Maximo Maximo's/asset planner of various asset Data Warehouse criticality/ condition/ performance scoring LIMS to SCADA LIMS -Pre-treatment Directly to LIMS, .csv format read by Ignition LIMS to SCADA LIMS -D2 sheet Directly to LIMS, .csv format read by Ignition LIMS to SCADA LIMS QA/QC and non-QA/QC Directly to LIMS, .csv sample/water quality results format read by Ignition WIMS to/from SCADA Plant Op Operators, QA/QC field samplers, From Remote Access Interface and I&E meter reading Tablet Data form entry SCADA to Looker system Important KPIs and reports shall be SCADA Data scheduled and displayed in Looker system, Warehouse Real Time Water Loss SCADA from server and Battery status/alarms SNMP other UPS power supplies (UPS monitoring) SCADA from PALL PALL Membrane Parameters Westside WTP Historian membrane system in Westside WTP G. Related Sections: 1. Section 01 11 13 —Summary of Work 2. Section 01 14 16 — Coordination with City's Operations 3. Section 40 61 13 — SCADA System General Provisions 4. Section 40 6121 — SCADA System Factory Acceptance Testing 5. Section 40 6123 — SCADA System Start -Up, and Field Testing f�►�K�Z� '7� 0[8]0[:10IP7LIayj0 QNfI'I: A. Comply with the requirements of Section 40 61 13 — SCADA System General Provisions, and this Section. 1.3 WARRANTY A. Duration: Reference Section 01 78 36 — Warranties for the duration of warranty requirements applicable to the Work performed under this Section. 1.4 SUBMITTALS A. Comply with the requirements of Section 40 61 13 — SCADA System General Provisions, and this Section. CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 40 68 63 SCADA SYSTEM PROGRAMMING AND CONFIGURATION Page 7 of 18 1.5 QUALITY ASSURANCE AND QUALIFICATIONS A. Comply with the requirements of Section 40 61 13 — SCADA System General Provisions, Attachment 1 — PLC and HMI Configuration Standards, and this section. PART 2 — PRODUCTS — Not Used PART 3 — EXECUTION 3.1 GENERAL REQUIREMENTS A. This section includes: Article Title 3.1 GENERAL REQUIREMENTS 3.2 SCADA SYSTEM SERVERSNIRTUAL ENVIRONMENTS 3.3 SCADA SYSTEM THIN CLIENTS AND WORKSTATIONS 3.4 SCADA SYSTEM SECURITY 3.5 SCADA SYSTEM DOMAIN SERVER 3.6 SCADA SYSTEM TIME SERVER 3.7 SCADA SYSTEM SUPPORT SERVER 3.8 PROGRAMMABLE LOGIC CONTROLLERS 3.9 INDUSTRIAL PANEL -MOUNTED TOUCHSCREEN COMPUTERS (IPCs) 3.10 HUMAN MACHINE INTERFACES 3.11 PLC AND HMI PROGRAMMING CHANGE MANAGEMENT 3.12 PLC AND HMI STANDARDS UPDATES 3.13 ALARM MANAGEMENT & REMOTE ALARM NOTIFICATION 3.14 HISTORICAL DATA COLLECTION 3.15 EXISTING HISTORICAL DATA 3.16 SCADA SYSTEM DATA INTERFACE 3.17 LOCAL PLANT OPERATIONAL REPORTS 3.18 BUSINESS & CENTRAL SCADA REPORTS 3.19 REMOTE ACCESS TABLETS 3.20 TEST BENCH B. General: 1. The Contractor shall provide a uniform appearance for programs and graphic configurations developed for the SCADA System across WTPs and Centralized SCADA to provide seamless integration between panel cutovers and simplification of operation and maintenance for all software being used and developed throughout the project. 2. The new SCADA system shall be programmed and configured in accordance with and meet the HMI standards and other requirements described herein and in Attachment 1 — PLC and HMI Configuration Standards. 3. The new Water Department SCADA system shall have distributed SCADA solutions characteristics. Each SCADA application at the WTP shall provide monitoring and control capabilities to any other SCADA application in the system except the Centralized SCADA system. 4. The WTP SCADA applications shall be available for read only at the Centralized CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 40 68 63 SCADA SYSTEM PROGRAMMING AND CONFIGURATION Page 8 of 18 SCADA application. Use secure and encrypted protocols of communication for the SCADA data transfer. 3.2 SCADA SYSTEM SERVERS/VIRTUAL ENVIRONMENTS A. General: 1. Contractor shall be responsible to coordinate with Water IT all requirements of the SCADA hardware, virtualization, and connection to the existing SCADA network during Coordination Workshop(s) and the Submittal process in the Design phase as described in Section 40 61 13 — SCADA System General Provisions. 2. Water IT shall configure the SCADA system switches, routers, hardware, virtual machines, and drive allocation/partitioning as identified during the Design phase. 3. A high -availability server shall be a fault -tolerant server with hot-swappable components including but not limited to the CPU, memory, HDD, Power Supply, etc. High-availability/fault-tolerant server solution can also be implemented within the virtualization environment by clustering Virtual Machines (VMS) across multiple standard servers to protect against hardware failures and outages. 4. For the high availability server setup and configuration, coordinate with Water IT to begin the process of providing the manufacturer or manufacturer representative all requisite informational needs (VM software and resource allocation, vSwitches setup, IP addresses, Host names, data store allocation, etc.) in the Design phase. Complete the informational process no less than 30 days prior the start of procurement by the City. Coordinate with Water IT to ensure operating system software, HMI software licenses and all other necessary software (e.g. drivers, thin client management, antivirus, and backup software) and configuration is available, and is securely transferred and loaded onto the new high availability server no less than 30 days prior to the scheduled start of field activities. 5. Ignition server VM pairs shall support redundancy; both servers shall share the exact same configuration state. And if one server VM fails, the other shall take over and continue executing. Refer to Article 1.2 — SCADA System Architecture Description in Section 40 61 13 — SCADA System General Provisions. 6. Contractor shall program and configure the SCADA system applications. 7. The new SCADA system shall be programmed and configured in accordance with and meet the HMI standards and other requirements described herein. 3.3 SCADA SYSTEM THIN CLIENTS AND WORKSTATIONS A. General: 1. Contractor shall be responsible to coordinate with Water IT all requirements of the SCADA System Thin Clients and Workstations during Coordination Workshop(s) and the Submittal process in the Design phase as described in Section 40 61 13 — SCADA System General Provisions. 2. Water IT shall configure the SCADA System Thin Clients and Workstations as identified during the Design phase. 3. Contractor shall be responsible to configure SCADA System software for all SCADA System Thin Clients and Workstations required for a fully fixnctional system in coordination with Water IT. The configuration includes but is not limited to installing HTML5 and CSS3 compliant web browser to load the SCADA software client. 4. The new SCADA system Thin Clients, thin client manager software, and workstations shall be programmed and configured in accordance with and meet the CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 40 68 63 SCADA SYSTEM PROGRAMMING AND CONFIGURATION Page 9 of 18 HMI Configuration standards and other requirements described herein. 3.4 SCADA SYSTEM SECURITY A. General: 1. Contractor shall be responsible to coordinate with Water IT all requirements of the SCADA System Security, RSA soft tokens and dongles during Coordination Workshop(s) and the Submittal process in the Design phase as described in Section 40 61 13 — SCADA System General Provisions. 2. The new SCADA system Security shall be programmed and configured in accordance with and meet the Water IT standards, HMI Configuration standards in Attachment 1, and other requirements described herein. 3. Users that will be making operational changes to the SCADA servers or environment shall be required to authenticate via Multi -Factor Authentication (MFA) utilizing RSA soft tokens for system that are internet connected (Centralized SCADA) and via RSA hard token (dongle) for the systems that are not internet connected (WTPs). MFA shall be configured in the SCADA applications in coordination with Water IT. Configure 20 RSA soft tokens and 20 RSA dongles. 3.5 SCADA SYSTEM DOMAIN SERVER A. General: 1. Contractor shall be responsible to coordinate with Water IT all requirements of the SCADA System Domain Server(s) during Coordination Workshop(s) and the Submittal process in the Design phase as described in Section 40 61 13 — SCADA System General Provisions. 2. Water IT shall configure the SCADA System Domain Server(s) with user accounts and group policies identified during the Design phase. SCADA Microsoft Active Directory (AD) shall be configured as per Water IT's standards. 3. The Domain Server(s) shall provide central user management, authentication, and authorization. 4. The SCADA software shall use LDAP (Lightweight Directory Access Protocol) to connect to the Microsoft Active Directory (AD). Once a SCADA account is authenticated, the privileges provided to that account shall be determined by AD group policies dictated in the Active Directory Security Groups. 5. Administration for the users, roles, and policies shall be performed directly from the Microsoft AD and not from the SCADA software. 6. Contractor shall coordinate with Water IT to ensure the Domain Controller setup is performed as per the SCADA vendor's security recommendations for user authorization and authentication. 3.6 SCADA SYSTEM TIME SERVER A. General: 1. Contractor shall be responsible to coordinate with Water IT all requirements of the SCADA System Time Server during Coordination Workshop(s) and the Submittal process in the Design phase as described in Section 40 61 13 — SCADA System General Provisions. 2. Water IT shall configure the SCADA System Time Server as identified during the Design phase. 3. The new SCADA Time Server shall be configured as the sole time source for all new CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 40 68 63 SCADA SYSTEM PROGRAMMING AND CONFIGURATION Page 10 of 18 SCADA components including HMI servers, HMI clients, PLC controllers, network switches, and others. 4. Network Time Protocol (NTP) shall be utilized for time synchronization across the SCADA network. 5. Each PLC's internal clock shall also be automatically updated on a weekly basis to be synchronized with the SCADA Network Time Server. Interface with the SCADA Network Time Server shall be accomplished over the Ethernet network. 6. System shall allow User to adjust day, time, and frequency of time synchronization with proper security credentials. 7. Each PLC's internal time clock shall be monitored by the SCADA system and shall be displayed at the HMI. Drift of more than ten minutes from the SCADA Network Time Server shall trigger an alarm at the HMI. 3.7 SCADA SYSTEM SUPPORT SERVER A. General: 1. Contractor shall be responsible to coordinate with Water IT all requirements of the SCADA System Support Server during Coordination Workshop(s) and the Submittal process in the Design phase as described in Section 40 61 13 — SCADA System General Provisions. 2. Water IT shall configure the SCADA System Support Server as identified during the Design phase. 3. The SCADA support server shall be configured to host any SCADA system Maintenance, Management, and Auditing tools and software. Such tools include but are not limited to: a. Microsoft SQL Server Management Studio b. Network Access Control (NAC) solutions c. Network traffic packet capture analyzer software such as Wireshark d. Network mapping tools such as NMAP, 4. The SCADA support server shall also be used to apply all Windows and SCADA software patches and updates. 3.8 PROGRAMMABLE LOGIC CONTROLLERS (PLC) A. General: 1. The system configuration for PLCs in Category A shall be as described in the Process Control Descriptions developed by Contractor under the Design phase, and in accordance with the following requirements. The existing programs for PLC systems in Category B shall remain unchanged. 2. The PLC systems shall be programmed in accordance with Attachment 1— PLC and HMI Configuration Standards, and other requirements described herein. 3. Functions to be performed by each PLC include, but are not necessarily limited to, the following: a. Alarm and status indication. b. PID control and arithmetic functions. C. Interlock and sequential logic control of processes and equipment operations. d. Collection and transmission of data and control parameters to and from other PLCs. e. Interface with OIT and SCADA Network. CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 40 68 63 SCADA SYSTEM PROGRAMMING AND CONFIGURATION Page 11 of 18 4. All PLC programs shall be backed up to the associated PLC's EEPROM to reload the program, inclusive of setpoints and default values, automatically on memory fault. 5. Contractor shall use the manufacturer's standard add -on instructions to the extent possible. 6. For all new control logic work, including mismatch alarms/logic and PLC standards for outputs, feedback shall follow the standards as set out in Attachment 1 — PLC and HMI Configuration Standards. 7. For all new logic, the behavior of outputs shall be coordinated with the City to confirm shutdowns and resumptions of operations occur in a safe manner appropriate to the local equipment operation and operational needs. Power failure, communication loss, and restart logic shall be incorporated into the control strategy for review, and after reviews, incorporated into the logic. 8. Each PLC's internal clock shall be automatically updated on a daily basis to be synced with the SCADA Network Time Server. PLC manufacturer's standard Add - On instruction shall be utilized for the timer synchronization logic implementation in the controller. Each PLC's internal time clock shall be monitored by the SCADA System and shall be displayed at the HMI. Drift of more than ten minutes from the SCADA Network Time Server shall trigger an alarm at the HMI. 9. All programs shall be added to and included in the City's existing Program Management software and process. 3.9 INDUSTRIAL PANEL -MOUNTED TOUCHSCREEN COMPUTERS (IPCs) A. General: 1. Contractor shall be responsible to coordinate with Water IT all requirements of the Industrial Panel -mounted Touchscreen Computers (IPCs) and associated rolling cabinets during Coordination Workshop(s) and the Submittal process in the Design phase as described in Section 40 61 13 — SCADA System General Provisions. 2. Water IT shall configure the IPCs as identified during the Design phase. 3. Contractor shall be responsible to configure Ignition applications for all IPCs in accordance with Attachment 1 — PLC and HMI Configuration Standards. 4. IPCs shall be utilized as the human -machine interface (HMI) point to the SCADA System from the field. 5. From the IPCs, monitoring of the entire SCADA system shall be accessible. Control functionality shall be only enabled on City approval and shall be established during the Design phase. 6. All IPCs shall be functionally similar as to display arrangements, menu selections, command terminology, and data access methods. All IPCs shall be capable of accessing typical operator process control functions. 7. Each station's functional environment shall be password protected for system security and user identification in accordance with Attachment 1 — PLC and HMI Configuration Standards. 3.10 HUMAN MACHINE INTERFACE (HMI) GRAPHICS A. General: 1. HMI screens shall be developed for monitoring and control of the processes and equipment in accordance with the requirements described in Attachment 1 — PLC and HMI Configuration Standards. 2. The HMI Configuration Standards and other requirements defined herein shall be CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 40 68 63 SCADA SYSTEM PROGRAMMING AND CONFIGURATION Page 12 of 18 reviewed with City at the HMI Coordination Workshops described in Section 40 61 13 — SCADA System General Provisions. 3. At each of the five WTPs, the respective HMI screens shall be fully accessible per the Security Matrix identified in Attachment 1 — PLC and HMI Configuration Standards. These same screens shall be made available to the Centralized SCADA System in a read-only format. 3.11 PLC AND HMI PROGRAMMING CHANGE MANAGEMENT A. Existing Change Management software to store, maintain and upkeep of PLC, OIT and HMI programs shall be configured and updated periodically in accordance with and meet the PLC and HMI Configuration standards in Attachment 1. As programs or applications are installed in the field, coordinate with the City to configure the existing Change Management software to monitor and maintain the application, code, or program. 3.12 PLC AND HMI CONFIGURATION STANDARDS UPDATE A. PLC and HMI configuration standards in Attachment 1 are working documents intended to be kept up to date. Contractor shall create libraries of all objects created for the HMI applications and PLC. It shall include but not limited to reusable screen templates, graphic objects, User Defined Type (UDT) data blocks, function blocks, PID blocks, routines, and scripts. All those objects shall be well commented and described and saved in its native electronic format in a folder for the City use in future projects. Any modifications to the standards shall be submitted to the City. B. At times, the City may request updates to the standards for purposes of updating nomenclature, products, software, or other similar minor adjustments. Contractor shall incorporate these and add a minor revision note to the Standard and submit back to the City in both native file and color PDF. 3.13 ALARM MANAGEMENT & REMOTE ALARM NOTIFICATION A. Provide Alarm Management, Rationalization, and Integration according to ANSI/ISA- 18.2-2009 — Management of Alarm Systems for the Process Industry and the Attachment 1 — PLC and HMI Configuration Standards. B. Alarm Philosophy Document and Rationalization: Prepare and update the Alarm Philosophy Document establishing criteria for alarms. Based on all identified alarms, rationalize alarms. For each alarm, determine classification, priority and distribution, alarm justification. Determine overall formatting, handling of shelved alarms, handling of alarm floods, and provide analysis of "bad actor" and chronic alarms requiring resolution. C. Master Alarm Database: A master alarm database (Excel format acceptable) shall be developed and maintained through startup and commissioning. The database shall list all alarms for the project and associated alarm parameters such as area and priority. D. Alarm Notification shall utilize escalation strategy based on operator availability and alarm categorization. The proposed strategy shall be developed by the Contractor and coordinated with the City's operational staff prior to integrated system test and then during final CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 40 68 63 SCADA SYSTEM PROGRAMMING AND CONFIGURATION Page 13 of 18 Operational Availability Demonstration. E. Remote Notification: SCADA system shall use a secure method for the SCADA alarm notifications. One of the two (2) proposed strategies listed below is preferred for alarm notification implementation, the final solution shall be coordinated with City during design phase. All security requirements shall be coordinated with the Water IT. 1. SMS notification using cellular router and SCADA software SMS module. For this option, provide a dedicated cellular router in the DMZ with SMS gateway configured to allow sending out SMS notifications. 2. Voice-over-IP (VoIP): Use ATCOM service (or similar) for VoIP integration for the SCADA system. F. Performance: During OAD periods, perform a Pareto Analysis to demonstrate that the alarm system meets or exceeds the metrics defined in ISA 18.2. G. Three months after successful OAD completion, perform an alarm rationalization process. Generate the following reports for each WTP: 1. Pareto Analysis identifying frequency of alarms; 2. Top 10 Alarms in Frequency; 3. Alarm list and categorization. Host a workshop to review all alarms and confirm categorization, nature of alarm and if changes need to be made. Document recommended changes and implement. 3.14 HISTORICAL DATA COLLECTION A. General: 1. Process variables such as status, alarm, and analog values shall be collected and stored for historical use on displays, trends, and reports. Coordinate list of Historical data points with the City. 2. The software shall allow for historical data to be manually entered from the keyboard to facilitate entry of lab data or other information to be used in generating performance calculations. B. Historical Data: 1. Signal types that shall be collected by the historian software shall include the following: a. Analog values b. Key process indicators C. Setpoints d. Permit condition variables e. Health monitor signals f. Service status values, such as run times g. Disabled alarm status values h. Manually entered values 2. Frequency of historical data collection vary based on signal type. Frequency of data collection for each type of historical data point shall be coordinated with City during design phase. The final input/output (IO) list in the design document shall include data collection frequency of each historical data point. 3. Master Historical Tag Database: A master Historical Tag database (Excel format acceptable) shall be developed and maintained through startup and commissioning. The database shall list all historical tags with descriptions and associated collection parameters. This database shall be used to track and confirm required tags are being CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 40 68 63 SCADA SYSTEM PROGRAMMING AND CONFIGURATION Page 14 of 18 stored and collection parameters meet operations staff needs. A database shall be provided for each facility. Contractor shall review each database with the City's operational staff prior to integrated system test and then during final Operational Availability Demonstration. Comments provided by the City's operational staff to Contractor shall be incorporated at no additional cost to the City. C. Historical Data Management: 1. The Historical Data Management and Data Backup shall meet the requirements described in Attachment 1 — PLC and HMI Configuration Standards. 2. The Historical Data Management and Data Backup requirements shall be discussed and finalized during design phase and details shall be included in the PLC and HMI Configuration Standards. 3.15 EXISTING HISTORICAL DATA A. Each Water Treatment Plant has an existing historian. These existing historians and historical data shall be maintained on site throughout this Project. These existing historian computers shall not be decommissioned until written approval of the City. Contractor shall be responsible to coordinate with City to disable historical data collection by these existing historians in accordance with the sequence of work. B. Coordinate with Water IT to match existing data points and tags with the new tag to minimize data collection interruptions and to avoid duplicate tags for the same data point. This will include creating mapping tables and/or scripts to convert old tag names to new tag name standards for any historical data in the data warehouse or local data historians. The tag mapping tables and/or name conversion scripts should be created with input from Water IT and will be made available for other data sources within the Water IT domain. 3.16 SCADA SYSTEM DATA INTERFACE A. General: 1. All SCADA data collected by the historian software shall be transmitted to local SQL historian which resides in the same local network with a ten plus year data retention. 2. SCADA data in local SQL historian shall be transmitted to SCADA SQL pass through server which resides in the industrial demilitarized zone with a three plus year data retention. Then all data will be transmitted to central SQL historian which resides in the data warehouse for long term data storage of ten plus years. 3. A standardized and secured SCADA data processing architecture shall be designed and implemented to ensure near real-time secure data transmission. 4. Reporting data requirements shall be discussed with City operational and IT staff and finalized during design phase. SCADA data needed for business reports by other stakeholders shall be transmitted to a dedicated server in the data warehouse. 5. SCADA data aggregation and calculation requirements shall be discussed with City operational and IT staff during design phase. Data aggregation and calculation shall be implemented during implementation phase. 6. Data archive strategy and data storage and recovery plan shall be discussed with City operational and IT staff during design phase. Routine data archive and data backup shall be implemented based on city's requirements. 7. Data integration process shall be documented and validated by City operational and IT staff. CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 40 68 63 SCADA SYSTEM PROGRAMMING AND CONFIGURATION Page 15 of 18 8. Data in transit and at rest requires encryption between SQL, Ignition, and other data sources. NIST AES standards should be used. 9. Ensure algorithms and settings match between the local historians, and the pass-thru Historian and the Centralized SCADA historian. Contractor to confirm data accuracy across all data storage locations including that local SCADA data validations and data changes are propagated to the pass through and centralized SQL servers. B. Workshops and Submittals: See minimum requirements in 40 61 13, SCADA General Provisions. A. General: 1. Reports shall be generated using process input/output, event information, analog, digital, manually entered laboratory data, manual and/or computed point information from records in the historical database. Manual record collection feature shall allow data capture off the network i.e., operators shall be able to collect information in the field without an active network link and system shall be capable of backfilling this information into the historical database upon resumption of connectivity. 2. Contractor shall hold workshops, submit report layouts for review and approval in accordance with the requirements of Section 40 61 13 — SCADA General Provisions and where applicable Attachment 5 — Existing Reports. B. Report Types: 1. Provide special event, hourly, daily, monthly, and annual reports. 2. The following report types shall be provided for each facility: a. Facility Daily Operations Report. b. Facility Monthly Operations Report. C. Equipment Runtime Report. This report shall list all monitored and calculated runtimes for all major process equipment items in the system. Report data developed shall include equipment name, equipment description, year-to-date runtime, month -to -date run time, and start dates for each item. d. System Health Monitoring Report. This report shall list all monitored items in the system as defined in this Section, including but not limited to, PLC health status, SCADA network communication status, and disc space allocations. Information provided for each item shall include: the item name, item description, and health status "Good" or `Bad". An overall system health status indication shall be included at the top of the report. e. Equipment Out of Service Status Report. This report shall list the equipment that is out of service. Information provided for each equipment out of service shall include Equipment name, equipment description, date and time stamp equipment was placed out of service, user who placed equipment out of service, duration equipment has been out of service in days. f. Disabled Alarms Status Report. This report shall list the alarms which have been manually disabled by the user. Information provided for each disabled alarm shall include Alarm name, alarm description, date and time stamp alarm was disabled, user who disabled the alarm, duration alarm has been disabled. g. Any additional reports, if any requested by City or recommended by Contractor during design phase. h. Ad -hoc: Add provisions to generate Ad -hoc reports. CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 40 68 63 SCADA SYSTEM PROGRAMMING AND CONFIGURATION Page 16 of 18 C. Workshops and Submittals: See minimum requirements in 40 61 13, SCADA General Provisions. 3.18 BUSINESS AND CENTRAL SCADA REPORTS A. General: 1. Reports created using Ignition located on the centralized SCADA server shall be able to read data from multiple data sources across different servers residing in the data warehouse. Following are potential data sources for reporting: a) SCADA data b) Model system data c) Asset/work management system data (Maximo) d) AMI (myH2O) system data e) WIMS data f) GIS system data g) Billing System 2. Reports created using Ignition located on the centralized SCADA server shall also be able to read data from multiple data sources outside of the data warehouse utilizing platform -specific APIs and REST endpoints. Following are potential data sources for reporting: a) Ovation b) LIMS 3. Report layout and format requirements shall be discussed with City operational staff and finalized during design phase. Existing report templates may be provided during the workshops. The Contractor is expected to storyboard the new report template leveraging the visual/data capabilities of Ignition. A series of workshops will provide an iterative process to finalize the visualization/report design. 4. Contractor shall submit report layouts for review and approval in accordance with the requirements of this Section and where applicable, Attachment 5 — Existing Reports. Contractor will train the report users. 5. For data not currently available in the data warehouse the contractor shall make request from Water IT coordinating the time frame, identity, and quantity of data needed. 6. Acceptable latency/data lag from local historians to the Ignition Visualization Reports is less than 4 hours. 7. Contractor Work for business report creation shall follow the general process outlined below. See Section 40 61 13 — SCADA System General Provisions for Workshop and Submission requirements. a. Identify necessary data sources/tags for use for a given Report. b. Where necessary, submit a request to Water IT for needed production data to be provided to the warehouse. C. Develop reports and visualization and populate with data required. Contractor to coordinate time frame, identify of data, and quantity of data needed. d. Through iterative procedure and workshops, storyboard, refine, and ultimately mockup the report. e. Test and enable the report on the system. f. Train. B. Report Format: 1. For reports duplicating existing reports, see the templates in Attachment 5 — Existing Reports. CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 40 68 63 SCADA SYSTEM PROGRAMMING AND CONFIGURATION Page 17 of 18 C. Workshops and Submittals: See minimum requirements in Section 40 61 13 — SCADA General Provisions. A. General: 1. Contractor shall be responsible to coordinate with Water IT all requirements of the tablets during Coordination Workshop(s) and the Submittal process in the Design phase as described in Section 40 61 13 — SCADA System General Provisions. 2. Configure the tablets with operator entry forms as defined, reviewed and in accord with developed mock-ups during the design workshops. 3. Test the tablet forms using remote operator entry and confirm data is populated at Centralized SCADA. 4. Configure the Tablets to buffer/hold data if communications are lost and backfill that data once communications are restored. Provide a manual "upload" button as an option for Operators to use in uploading their data. Test data buffering with the Tablet and communication loss/restoration scenarios. 3.20 TEST BENCH A. General: 1. Contractor shall be responsible to coordinate with Water IT all requirements of the Test Bench during Coordination Workshop(s) and the Submittal process in the Design phase as described in Section 40 61 13 — SCADA System General Provisions. 2. Water IT shall configure the Test Bench server to mimic one of the typical WTP installations of servers, software, and connections, and as identified during the Design phase. 3. Contractor shall be responsible to configure the Test Bench PLCs and Ignition application for the Test Bench server in accordance with Attachment 1 — PLC and HMI Configuration Standards. 4. The Test bench shall also be used for demonstration and testing of PLC and HMI applications during Factory Acceptance Testing by the Contractor, and to allow City personnel to test system behavior offline prior to enabling in the production environment. + + END OF SECTION + + CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086 40 68 63 SCADA SYSTEM PROGRAMMING AND CONFIGURATION Page 18 of 18 ++THIS PAGE INTENTIONALLY LEFT BLANK++ CITY OF FORT WORTH SCADA System Replacement March 21, 2024 103086