Loading...
HomeMy WebLinkAboutTask Order 10157 with Brown and Caldwell for SCADA planPURCHASING AGENT 33 E. Broadway Ave, Meridian, ID 83642 Phone: (208) 489-0417 Fax: (208) 887-4813 TASK ORDER NO. 10157 For SCADA MASTER PLAN Between CITY OF MERIDIAN AND BROWN AND CALDWELL This Task Order is issued by City and accepted by the Engineer ursuant to the mutual p promises, covenant and conditions contained in the Master Agreement between the above mentioned parties dated April 13, 2010. Scope of Services 4verail Project Assumptions • All documents will be submitted as electronic copies. • The project schedule includes 10 working days for City of Meridian (Cit review of all Y) submittals. • All project workshops are scheduled as half-day (4-hour) meetings. • The interval of project progress teleconference calls will be determined b the ro'ect Y p1 pace. • The City project team will include key staff from water/wastewater operations, engineering, with management and IT personnel added for specific tasks as noted in the task assumptions themselves. • As much as possible, the membership of the City project team will remain constant throughout the life of the project. This dedicated group shall be referred to as the SCADA Automation Team in the task descriptions that follow. • The network and control system conceptual design, user requirements, and other automation design decisions developed during the SCADA Master Plan project will . J provide the basis for the Automation Design Standards. • SCADA design standards will focus on developing standards forfield devices, controllers, operator HMIs, and engineering workstations and SCADA radio and local networks. • The control system design standards will identify hardware and software standards applicable to the future control system but will not selects ecific ven p dors, equipment manufacturers, or model numbers. • SCADA Design Standards will be a livin document for future modifi 9 canons as determined by the SCADA Automation Team. TASK 050: Project Management objectives To manage the coordination and oversight of the Consultant Team and administr anon of the contract-including contract project resources, ualit ,costs deliverables and q Y ~ , schedule-and coordinate communications between the Consultant staff and Cit staff. Y Subtask 050.1: Project Management Plan The Consultant will prepare and submit a Project Mana ement Plan PMP at the be innin g ~ ~ 9 9 of the project. The draft review copy of the PMP shall be submitted within 30 calendar da s Y of the Notice to Proceed, with the final PMP delivered to the team 14 da s after recei t of . Y p City comments. At a minimum, the PMP shall include the followin com onents: 9 p • Scope of work • Project schedule • Project organization • Task budgets • Communications plan: key points of contact for both the Consultant and Cit staff . Y • Documentation control plan • Quality management plan • Standard project template documents for minutes of meeting, project memorandums J , and reports. Deliverable • Project Management Plan Subtask 050.2: Project Progress Reports The Consultant will prepare and conduct a project kickoff meeting at the be innin of the g 9 project for both the Consultant Team and City's SCADA Automation Team. The ur ose of . pp this meeting is to introduce the project teams, review the scope of work and schedule, and agree upon the "critical success factors" that will be reviewed at the end of the project to verify that the project objectives have been achieved. The kickoff meeting will be scheduled within 2 weeks of the City's Notice to Proceed to the Consultant for this project. Project progress reporting will be conducted through periodic teleconference calls and in- person meetings while on site. The Consultant will maintain a decision and action item log that will document issues as they arise, required actions to address each issue, assigned staff to complete the required actions, required decisions, and decisions made and by whom. Deliverables • One 2-hour kickoff meeting will be held at the City. An agenda will be prepared and minutes of meeting will be produced. • Monthly invoices will be submitted to the City. • A Decision and Action Item Log will be maintained. TASK 100: Existing SCADA System Standards and Documentation, and Condition Assessment Objectives To identify and document existing SCADA standards in use for the Cit wa y ter and wastewater systems, and existing "as-built" documentation. To identify the as-is condition of the water and wastewater SCADA s stem's har y dware and software relative to compatibility of components, and SCADA s stem h sical and y p y cyber security. To assess current SCADA and data historian software backu s stems and pY overall SCADA system reliability. To assess radio performance. Task Assumptions • The majority of existing radio system documentation is alread available to DCE and . Y City staff will be available to assist in the collection of existin documents not Curren g tly available to DCE. • The City will provide facility master plans for consideration when develo in the SCADA p9 conceptual design. • No "as-built" activities are included in this task. The pur ose for the task is to p understand what is available and what needs to be documented when the desi n g projects are executed (used to estimate engineering effort for pro'ect tannin bud ets . 1 p 9 9 ) • Up to 20 remote sites will be included in the radio path surve . Y Subtask 100.x.: Collect Existing SCADA Documentation and Document SCADA S stems y Existing Conditions Collect existing facility master plans, standard design documents, and as-built drawin s P&ID g ( s, location plans, electrical single-lines, wiring dia rams, anel drawin s le end 9 p g, g sheets, control strategies, operating procedures/guidelines, etc. ,SCADA desi n standards . ) g used by City staff, and any existing radio path studies previous) commissioned b the Cit . y v y Identify the data requirements (10} for remote sites, document the existin radio s stem . 9 Y condition, and identify which saes are to be included in the radio path surve . Y Document the condition and compatibility of major SCADA com onents for re lacement or p p reuse, which will be used to assist in developing planning-level estimates and summa ry project scopes of work in the SCADA Master Plan. Deliverables • Schedule of documentation made available from the City for the SCADA s stems Y • Representative sample of key documents collected from this task with assessment of work to be performed to gather any missing information necessary to ain a com lete 9 p understanding of the water and wastewater SCADA systems • A summary of findings, site surveys, condition assessments, and other ke documents . Y developed in this task • List of remote sites to be included in the radio path survey test. Subtask 100.2: Workshop to Validate Standards, Documentation and Condi i t an Assessments Facilitate a half day (4-hour) workshop to review documentation and S CADA standards findings to verify or correct our understandin s, and to review the result 9 s of the site surveys, condition assessments, and other documents prepared under this task to document City comments. Deliverable • Workshop agenda and meeting minutes Subtask 100.3: Perform Radio Path Survey Perform radio path survey for selected water and wastewater sites. Deliverables • Results from the radio path survey Subtask 100.4: Document SCADA Standards, As-built Documentation, and Condition Assessment Results Prepare a technical memorandum (TM) that documents the following: • SCADA system documents, drawings, and legend sheets • SCADA standards, guidelines, and practices in use today by City • SCADA HMI and controller I/O databases • SCADA control logic and control strategy documents. • SCADA system condition assessment results Deliverables • Draft TM 1: SCADA standards, as-built documentation, and existing condition assessment summary findings with supporting appendixes Subtask 100.5: Workshop to Review Draft TM1: SCADA Systems Documentation and Condition Assessment Results Facilitate ahalf-day (4-hour) workshop to review draft TM1 and document City comments. Deliverable • Workshop agenda and meeting minutes Subtask 100.6: Finalize TM ~.: SCADA Systems Documentation and Condition Assessment Results Incorporate comments received from the City and finalize TM 1. Deliverable • Final TM 1: SCADA standards, as-built documentation, and existing condition assessment summary findings with supporting appendixes TASK 200: SCADA User Requirements ~bjec~ives To gather user requirements (such as being able to view SCADA displays/information from City Hall, greater access to historical data, etc.), from various sources includin one-on-one . 9 staff discussions, observed operational practices, staff discussions during worksho s, p formal interviews with key staff members, and results from Task 100. To review the user requirements with the SCADA Automation Team and to a ' . nalyze, consolidate, and prioritize the user requirements in a TM. Task Assumptions • Up to 10 City staff will be individually interviewed b BCIDCE ' . y to determine City user requirements. SCADA Automation Team will identif staff to be interviewed . Y by BCIDCE. • Discussions will be completed and a user re uirements list broke ' . q n into technical, business and organization categories will be a roved b consens pp y us of the SCADA Automation Team within two 4-hour worksho s. If a second worksho i p p s required, it will be conducted the same week as the first worksho . p Subtask 200.1; Staff interviews BCIDCE will develop a structured interview questionnaire to aher Cit g y SCADA requirements and conduct interviews with key staff knowledgeable about the water and wastewater SCADA systems, or with a vested interested in the ca abilities and p requirements of the water andlor wastewater SCADA systems. BCIDCE will document the raw user requirements gathered in preparation for review with the SCADA Automation Team. Deliverable • Raw User Requirements Subtask 200.2: User Requirement Workshops Facilitate two half-day (4-hour) workshops. These worksho swill focus on the Cit ' . p ys user requirements. The first workshop will review a consolidated list of raw user re uirement q s identified during the structured interviews. The raw user re uirements will be resen q p ted anonymously to prevent any direct ties with the user, and then be consolidated into technical, organizational, and business categories. If a consensus is not reached amon the SCADA A g utomation Team regarding the consolidation of the raw comments or their categorization within the allotted time frame, a second 4-hour worksho will be held the p next day or as closely as possible to completion of the first worksho to continue the p discussions. Delr`verabte • Workshop agendas and meeting minutes Subtask 200.3: Development of TM2: User Requirements and Facilitate Review Worksho p Compile and summarize the user requirements in a TM and issue to the Cit for revi Con _ Y ew. duct a half day (4-hour) review workshop to discuss user re uirements and how thes q e will feed into the SCADA system conceptual design, and document Cit comments. Y Deliverables • Draft TM2: User Requirements. This TM summarizes the user re uirements and q establishes the top user requirements that collectively represent the Cit 's needs b Y (usiness, technical., and social) • Workshop agenda and meeting minutes Subtask 200.4: Finalize TM 2; User Requirements Incorporate comments received during the review worksho to finalize the user p requirements TM. Deliverable • Final TM 2: User Requirements TASK 300: SCADA System Conceptual Development Ubjec~ives To develop up to three alternative models of the future SCAD A system based on the outcomes from the previous tasks, past BC/DCE ex erience and res - p earch into state of the-art, real-world, solutions applied in similar industries. The thre ' e alternative models will address SCADA local and wide-area communications controllers s ervers, HMI workstations, SCADA management/engineerin data exchan e SCADA ' 9 g , historian, and SCADA connections to other networked vendor a ui ment. The alter ' . q p natives presented will include options to access SCADA data throughout the or anization rovid r g , p e e m ote SCADA control, and to support SCADA data accessibilit for business s s Y y terns such as the Hansen CMMS, CCTV, and site security. Overall Task Assumptions • The SCADA conceptual design is meant to describe how the SCADA s stem and other Y network devices are to be designed and assembled. It does not name vendor equipment or specific hardware; rather, it identifies a framework for which the s ecifics p can be defined on projects in support of the overall SCADA Master Plan. • The conceptual design will help quantify the level of automation the Cit needs to . Y implement to achieve its long-term vision. The final SCADA conce tual desi n will be p g used to develop planning-level estimates for SCADA system up rade ro'ects for the 9 p1 near term (1 to 5 years) as well as the long term (5 to 10 years). Subtask 300.1: Development of Alternative Designs for Water and Wastewater SCADA Systems Perform a coordinated analysis of the results from the previous tasks identif in existin Y9 g SCADA system standards, existing SCADA system conditions, and user re uirements. q Review and identify conflicting points and supporting overaa s. Review radio surve results p y and analyze the anticipated future performance of fixed-frequenc licensed radios vs. Y spread-spectrum unlicensed radios, as well as the use of Ethernet as the standard for radio communications. Based on the results of the analysis, BC/DCE will develo an information p flow diagram of the key data producers and data consumers for the water and wastewater SCADA systems. BC/DCE will develop up to three alternative conceptual SCADA s stem desi ns corn lete . Y 9 p with field I/O representations, PLC and/or RTU controllers, operator interface en ineerin . ~ 9 9 workstations, servers, process data historian, and other information s stems connected to Y the SCADA system. The WAN/LAN communication design is an essential infrastructure component of the future SCADA system and will be designed to be flexible and ca able of . P supporting the City s needs for the next 20 years. Included in TM 3 will be BCIDCE recommendations for the conceptual designs of the water and wastewater SCADA systems. Deliverable • Draft TM 3: Alternative Conceptual Designs for Water and Wastewater SCADA S stems Y Subtask 300.2: TM 3: Alternative Conceptual Designs far Water and Wastewater SCADA Systems Review Workshop Facilitate ahalf-day (4-hour} workshop to review TM3 and collect Cit in ut and feedback Y p , and achieve a consensus among the SCADA Automation Team members on all as ects of p the conceptual designs for the water and wastewater SCADA s stems. Y Deliverable • Workshop agenda and meeting minutes Subtask 300.3: Finalize TM 3: Alternative Conceptual Desi ns for Wat ~ er and Wastewater SCADA Systems Incorporate the comments from the worksho to finalize TM 3. Th p e TM is to contain recommendations for planning the future water and wastewater SCADA s ste ' y m design and implementation. Deliverable • Final TM 3: Alternative Conceptual Designs for Water and Wastewater SCA DA Systems TASK 400: CIP Prioritization Process Objectives To assist the City's SCADA Automation Team in develo in a strate for reviewin p 9 gy g and selecting SCADA projects. To document a complete list of short-term and Ion -term SCA g DA automaton-related protects that the City is current) considerin for CIP fundin or Y g 9 was identified as part of one of the previous tasks. To app) the Cit 's standard forms and .. Y Y processes for prioritizing the desired SCADA-related projects based on results of the condition assessments, user requirements, conceptual SCADA s stems and ro'ect . Y ~ p J criticality to develop a list of the top ten highest priority projects and identif if the are J Y Y needed in the short-term or long-term. To establish a framework for evaluatin and g prioritizing future SCADA projects. Subtask 400.x.: Document Current Projects Gather any existing lists of SCADA systems improvement ro'ect re uests. Add ro'ect pJ q pJ identified during the previous tasks for a complete list of projects to be rioritized. Enter the . J p identified SCADA projects into the City standard format that ca tures a summarized sco e p p, justification for funding, and estimated budgets and schedules if available or rou h order of ~ g magnitude -ROM}. Deliverable • Summary SCADA project list for use in the CIP prioritization rocess worksho p p Subtask 400,2: CIP Prioritization Criteria and Weights and Automation Project Prioritization Workshop Develop the CIP prioritization criteria and weights based on the previous tasks and a I pP Y them to the SCADA automation project list in ahalf-day (4-hour) interactive worksho . p Deliverables • Workshop agenda and meeting minutes • Draft TM 4: Prioritized SCADA Projects Subtask 400.3: Finalize TM 4: Prioritized SCADA Projects Incorporate the comments received from the City's review of the submitted draft TM 4. Deliverable • Final TM 4: Prioritized SCADA Projects TASK 500: SCADA System Replacement Planning and Budgetary Capital Cost Estimate Objectives To review the results from the CIP prioritization rocess and mak ' p e recommendations for consolidation of any projects, and to develop a hi h-level im lementation 9 p plan (summary scope, schedule, and budgetary estimate) for the 10 hi hest- riorit SCADA s 9 p y ystem replacement/upgradeprnjects. Subtask 540.1: Project Definitions Review highest-priority projects and look for opportunities to consolidate ro'ec ' p t is into larger protects. Each project will be provided with project goals, prelimina sco a of work and ry p , identification of dependencies and relationships to other automation ro~ects identified in pJ Task 400. Deliverables • Planning-level document defining the project list and boundaries for each ro'ect p1 Subtask 500.2: Draft SCADA Improvements Implementation Plan Prepare the following for the project list developed: • A planning-level capital estimate to design and implement each pro~ect t • Budgetary cost estimates for ongoing SCADA systems maintenance arts and p staffing needs, and for SCADA system life cycle • A high-level target milestone schedule for project duration that includes: o Engineering and design reviews o Implementation planning o Procurement, construction, integration, testing, and startup. Deliverable • Draft TM 5: SCADA Improvements Implementation Plan Subtask 500.3: Finalize SCADA Improvements Implementation Plan Facilitate a workshop to review the draft TM 5: SCADA Improvements Im lementation Plan p and incorporate City comments into the final TM 5. The City will be able to use the results of this summary to enter planning-level budgets and schedules into its CIP as well as use the master implementation schedule to coordinate future design and installation work. Deliverable • Final TM 5: SCADA Improvements Implementation Plan • Agenda and Meeting Minutes TASK 600: Develop SCADA Standards Objectives To develop SCADA standard design guidelines that document the SCADA s stem y standards for radios and networking equipment, protocols, IP addressing, and a lication pp software; PLC1RTUs; operator workstation; HMI; SCADA engineerin workstation archival 9 and change management; and standard naming conventions for 10, instrumentation, SCADA equipment, and SCADA panels. Also to develop a standard set of SCADA s ecifications for r ' p adios and networking equipment, protocols, and application software; PLC/RTUs in a standard confi ' . guration, operator workstation, HMI standards; SCADA fieldbus interface if a lica ( pp ble), SCADA servers, and SCADA engineering workstation. Task Assumptions • No additional field work will be required to develo the draft SCADA de i p sgn standards. • Standards will be based on the Conceptual Desi ns for Water and Was 9 tewater SCADA Systems developed in Task 300 and no chan es to those desi ns will be 9 g made as part of this task. • There will be only minor differences between the Conce tual Desi n of the W p g ater SCADA System from the Conceptual Design of the Wastewater SCADA S stem y and ideally, one set of design standards and standard specifications can be a lied to both pp SCADA systems. • BCIDCE will work directly with the City I&C staff (Von Potter) to develo draft standard . p naming conventions for 10, instruments, SCADA equipment, and panels, and that Von will have discussed with and received input from key City staff prior to workin on this g task. • SCADA Standard Design Guidelines will include typical drawings for: o Instrument control schematics (up to three typical drawings) o MCC control schematics (up to three typical drawings) o Control panel layout drawings (up to three typical drawings) o Control logic diagram (one typical drawing} • Standard specifications will be limited to the minimum Division 17 specifications required to define SCADA equipment, and will be based on City standard specifications or BC/DCE standard specifications, as revised to meet the unique design re uirements q identified in the SCADA standard design guidelines. • No instrument specifications will be included in SCADA standard specifications. • No standard SCADA design drawings will be developed as part of the standard specifications. Subtask 600.1: Develop Draft SCADA Standard Design Guidelines far the Water and Wastewater SCADA Systems Review the existing SCADA RTUIPLC, HMI, networking, and administrative standards identified in Task 100, the SCADA conceptual design developed in Task 300, SCADA standards documents from BCIDCE past projects, and applicable industry standards relative to SCADA standards. Develop draft SCADA standard design guidelines that include standards for: ^ Radio (or alternative wide-area network communications technology} and network equipment ^ PLCs and RTUs ^ Workstations and servers ^ HMI ^ 10, instrument, SCADA equipment, and SCADA panel naming conventions ^ SCADA HMI standards including: o Display menu and hierarchy o Display layout o Color conventions o Display pop-ups and faceplates o Display symbols o State descriptors o Alarm descriptors and hierarchy o Trending parameters and display grou s p SCADA system file-naming ^ File backup/archiving strategy ^ Configuration software upgrades: strate and rocess 9Y p ^ Configured control logic change control ^ Control strategy write-up documentation ^ Control logic diagram. Deliverables • Draft SCADA Standard Design Guidelines for the Water and Wastewater SCAD A Systems Subtask 600.2: Develop Draft SCADA Specifications for the water and Wastewater SCADA Systems Based on the draft SCADA standard design guidelines, develo standard s ecifications for: p p ^ SCADA panels ^ Radio and network equipment ^ PLCs and RTUs ^ Workstations and servers ^ SCADA software including HMI ^ SCADA schedules for 10, instrument, SCADA equipment, and SCADA anels p ^ Control strategies. Deliverables • Draft SCADA Specifications for the Water and Wastewater SCADA S stems Y Subtask 600.3: aeview Draft SCADA Standard Design Guidelines and Specifications Facilitate ahalf-day (4-hour) workshop to review the draft SCADA standard desi n 9 guidelines and draft SCADA specifications for the water and wastewater SCADA s stems. .. Y To solicit City comments and develop a consensus among the SCADA Automation Team on the SCADA standard design guidelines and specifications. Deliverable • Workshop agendas and meeting minutes Subtask 600.4: Finalize SCADA Standard Design Guidelines and Specifications Incorporate comments from the review workshop into the SCADA standard desi n . 9 guidelines and specifications, and submit finalized standards. Deliverables • Final SCADA Standard Design Guidelines forthe Water and Wastewater SCADA Systems • Final SCADA Specifications for the Water and Wastewater SCADA S stems Y TASK 700: City Public Works Department/Technology Department SCADA Memorandum of Understanding Objectives To develop and document an understanding of responsibilities between the Cit 's y Technology Department (IT) and Public Works Department (PWD relative to the division of responsibilities for maintaining, expanding, and enhancing the water and wastewater SCADA systems. Five key SCADA technolo areas wi ' gy II be addressed in the memorandum of understanding (MOU): hardware confi uration and main ' . . , g tenance, operating and application software admin~strat~on, application software confi ur ' g anon and development, network maintenance and administration, and information securit admi ' . y nistration. Each area covered will include a description of each of IT's and PWD's res onsibili i . p t es and business requirements, as well as a descri tion of shared IT/PWD r ' ' ' ' p esponsibilities. Overai! Task Assumptions • PWD and IT department managers will review the final MOU and si n it as . g a commitment to abide by the separation of authorities and res onsibilities for the on oin p g 9 maintenance, enhancement, and expansion of the SCADA s stems identified within the Y MOU. • Key City IT and PWD staff will be made available to partici ate in multi le worksho s to p p p develop the MOU. • One key component of the MOU will be the simplification of the remote to in rocess 9 p PWD staff must complete to remotely log into the SCADA s stems. Y Subtask 700.x.: Review Existing IT/PWD Agreements and 4therAgency Sample IT PWD Agreements BC/DCE knows of an existing IT/PWD agreement that documented a clear oint of p demarcation with the SCADA system relative to who is authorized and res onsible to p maintain/upgrade/expand what piece of SCADA equipment. Our understandin is that that 9 agreement has not been consistently applied or enforced and may no longer be a governing document. BC/DCE will facilitate a half day (4-hour) workshop with the City's ke IT/PWD stakeholders Y to review the existing SCADA ITIPWD MOU as well as any other City MOUs that are in place and MOUs from other clients, and document findings throu h this interactive g workshop. The goal of this workshop is to identify the SCADA system hardware, software applications, network, and physical and cyber security items that need to be addressed for development of a comprehensive MOU. Deliverables • Workshop agenda and meeting minutes • Draft outline of MOU Subtask 700.2: SCADA System Products and Services IT/PWD Division of Labor/4wnershi P Workshops Facilitate a half day (4-hour) workshop with the City's key ITIPWD stakeholders to discuss the levels of service support required from IT for the SCADA system hardware and software and SCADA applications. In addition, the stakeholders will discuss all as ects of p SCADA security, with the goal that remote access by PWD staff into the water and wastewater SCADA systems can be streamlined to support ease of use while maintainin a h' g igh level of security. The results from this workshop will be incorporated into a draft MOU broken down b Y hardware, software, applications, network, and security, and submitted for Cit review and Y comments. Deliverables • Workshop agenda and meeting minutes • Draft MOU Subtask 700.3: Finalize MOU Review and incorporate City comments into the draft MOU. Finalize MOU for submission to senior IT and PWD management for signatures. Deliverable • Final City Public Works DepartmentlTechnolo De artment SCADA Mem gY p orandum of Understanding TASK 800: SCADA Master Plan Objectives To summarize the key findings, decisions, vision of the future SCADA s stems out y comes of the CIP prioritization process, and top-priority short-term and Ion -term ro'ects bu g p J ( dgets and schedules}. Task Assumptions • The SCADA Master Plan will be an executive summary of the main outcomes from the master planning process with each task TM (with attachments) included as an a endix pp to the executive summary. Subtask 800.1: Draft SCADA Master Plan Assemble the SCADA Master Plan summary that will: • Summarize the outcome from the CIP prioritization process • Prepare a plan for execution of the projects identified in the SCADA Master Plan including schedules and budgets for all Automation ro'ects under the Pro ram pJ g • Outline overall conceptual design forthe SCADA Master Plan, and establish main parameters for software and hardware architecture and requirements • Define project management methodology for the SCADA Improvement Pro ram 9 • Summarize the SCADA standard design guidelines and specifications that should be applied to all SCADA projects in the Program whenever possible. The SCADA Master Plan appendix will contain the TMs prepared in Tasks 100 throu h 800 9 as appendices. Submit draft SCADA Master Plan for City review, and upon completion of review, facilitate ahalf-day (4-hour) workshop to review the draft SCADA Master Plan and collect the City's comments. Deliverables • Draft SCADA Master Plan • Workshop agenda and meeting minutes Subtask 800.2: Final SCADA Master Plan Incorporate City comments collected from the review workshop into the SCADA Master Plan. Deliverable • Final SCADA Master Plan TIME OF PERFQRMANCE The attached schedule details the timeline to com fete each p task. COMPENSATIQN The Scope of Services detailed in this Task Order shall be com I ' p eted within the Not-To- Exceed amount of $296,134.00 per En ineers ro osal dated Jan . g p p uary 11, 2011. Fees will be billed on a time-and-materials bans for actual hours worked er p the attached rate sheet to the master Agreementdated Apnl 13, 2010 , but in no event will fe es exceed the Not- To-Exceed amount of $296,134.00 for the services listed herein. ASSUMPTIONS The following assumption was made in pre aration of the sco a of w r ' p p o k and fee estimate: • Brown and Caldwell will rely on information rovided b the Cit to r . p y y p epare the technical documents. CITYOF MERIDIAN BY: ~ TAMMY de I D, MAYO R BROWN AND CALDUVELL Jeffrey S. J on Dated: ~u 5 l j ~ Dated. ~ ,~ ~ ~ ,~~ '~~~ ~, Approved b Cit Council: ~ ~~ ~'~~~ ~''r y y ~ ~, V ' /~ d ~, . Attest. ,~ o 'y ~ ~ ~ `'~ M, M. s ~ ~ rw w . 0 MA , CLARK .~ a~ ~ ~ ~~ ~ ., Approved as to C nt P'~. '~ `'0~ f,~~ ~~ ~ , `~~~epartment Ap ro KEIT ATT , PU HASING MANAGER TITLE: c D ~ 3 .- ,- ated. j Z j D ated. '~