BACKGROUND Project History Sample Clauses

BACKGROUND Project History. The Project Scope Summary Report (PSSR) for the project was approved on June 27, 2017. The PSSR proposed to rehabilitate the mainline, ramps, and freeway connectors and repair and upgrade the drainage facilities and roadway-safety-related items in both directions of SR 87 from SR 85 at PM 0.0 to the Julian Street Undercrossing at PM 6. 1. The project is listed as SHOPP ID 13685 in the SHOPP Ten-Year Project Book with SB-1 priority. Per District 4 Office of Traffic Safety PA&ED recommendation, it was determined that the existing median barrier will be upgraded to current standard for all build alternatives, regardless of modifications to the roadway finished grade. As such, the scope of work in the preferred alternative (20-year flexible rehabilitation alternative) was increased to incorporate this work.
Sample 1Sample 2
AutoNDA by SimpleDocs
BACKGROUND Project History. ‌ A Project Initiation Report (PIR) for the project was written and approved on May 25, 2017. There was one Build Alternative and the cost was $53 million. Changes to the project since the PIR include the following: • The Office of Traffic Safety conducted a Traffic Accident Analysis within the project limits; the analysis concluded that there was a need for 77 additional lights. Some of the lights are to be installed on the bridge rails. • There are multiple slotted drains that have the potential to be damaged that may require replacement when the median barrier is removed and replaced. • Compliance with a Context Sensitive Solutions approach suggests an aesthetic treatment on the new, taller median barrier. No community meetings have been held for the project, but a Community Impact Assessment report was completed, and letters were sent to community members adjacent to the project affected by the lighting to inform our neighbors about the project. Also, letters were sent to the City of El Cerrito and the City Richmond to notify them. The City of Richmond had no comment; the City of El Cerrito has not yet replied.
Sample 1Sample 2

Related to BACKGROUND Project History

  • Project Background 6.1.1. Brief description of Contracting Agency’s project background and/or situation leading to this Project

  • Background Screening VENDOR shall comply with all requirements of Sections 1012.32 and 1012.465, Florida Statutes, and all of its personnel who (1) are to be permitted access to school grounds when students are present, (2) will have direct contact with students, or (3) have access or control of school funds, will successfully complete the background screening required by the referenced statutes and meet the standards established by the statutes. This background screening will be conducted by SBBC in advance of VENDOR or its personnel providing any services under the conditions described in the previous sentence. VENDOR shall bear the cost of acquiring the background screening required by Section 1012.32, Florida Statutes, and any fee imposed by the Florida Department of Law Enforcement to maintain the fingerprints provided with respect to VENDOR and its personnel. The parties agree that the failure of VENDOR to perform any of the duties described in this section shall constitute a material breach of this Agreement entitling SBBC to terminate immediately with no further responsibilities or duties to perform under this Agreement. VENDOR agrees to indemnify and hold harmless SBBC, its officers and employees from any liability in the form of physical or mental injury, death or property damage resulting from VENDOR’s failure to comply with the requirements of this section or with Sections 1012.32 and 1012.465, Florida Statutes.

  • Research Project The findings of any research project, which would change the provisions of this Agreement will not be implemented until such changes are negotiated and agreed to by the parties.

  • Project Plan Development of Project Plan Upon the Authorized User’s request, the Contractor must develop a Project Plan. This Project Plan may include Implementation personnel, installation timeframes, escalation procedures and an acceptance plan as appropriate for the Services requested. Specific requirements of the plan will be defined in the RFQ. In response to the RFQ, the Contractor must agree to furnish all labor and supervision necessary to successfully perform Services procured from this Lot. Project Plan Document The Contractor will provide to the Authorized User, a Project Plan that may contain the following items: • Name of the Project Manager, Contact Phone Numbers and E-Mail Address; • Names of the Project Team Members, Contact Phone Numbers and E-Mail Address; • A list of Implementation milestones based on the Authorized User’s desired installation date; • A list of responsibilities of the Authorized User during system Implementation; • A list of designated Contractor Authorized Personnel; • Escalation procedures including management personnel contact numbers; • Full and complete documentation of all Implementation work; • Samples of knowledge transfer documentation; and • When applicable, a list of all materials and supplies required to complete the Implementation described in the RFQ. Materials and Supplies Required to Complete Implementation In the event that there are items required to complete an Implementation, the Contractor may request the items be added to its Contract if the items meet the scope of the Contract. Negotiation of Final Project Plan If the Authorized User chooses to require a full Project Plan, the State further reserves the right for Authorized Users to negotiate the final Project Plan with the apparent RFQ awardee. Such negotiation must not substantively change the scope of the RFQ plan, but can alter timeframes or other incidental factors of the final Project Plan. The Authorized User will provide the Contractor a minimum of five (5) business days’ notice of the final negotiation date. The Authorized User reserves the right to move to the next responsible and responsive bidder if Contractor negotiations are unsuccessful.

  • Project Work Plan The Statement of Work is the formal document incorporated into the Grant. The Project Work Plan documents how the Grantee will achieve the performance measures outlined in the Grant. Changes to the Statement of Work require an amendment. Project Work Plans may be changed with written approval from PEI and the Grantee.

  • Project Work PURCHASER shall complete the following projects in accordance with the specifications provided in Exhibits B, C, D, E, and F and written instructions from STATE. Project locations are shown on Exhibit A unless otherwise described. PURCHASER shall furnish all material unless otherwise specified.

  • Project 3.01. The Recipient declares its commitment to the objectives of the Project. To this end, the Recipient shall carry out the Project in accordance with the provisions of Article IV of the General Conditions.

  • Elements Unsatisfactory Needs Improvement Proficient Exemplary IV-A-1. Reflective Practice Demonstrates limited reflection on practice and/or use of insights gained to improve practice. May reflect on the effectiveness of lessons/ units and interactions with students but not with colleagues and/or rarely uses insights to improve practice. Regularly reflects on the effectiveness of lessons, units, and interactions with students, both individually and with colleagues, and uses insights gained to improve practice and student learning. Regularly reflects on the effectiveness of lessons, units, and interactions with students, both individually and with colleagues; and uses and shares with colleagues, insights gained to improve practice and student learning. Is able to model this element.

  • Contractor’s Project Manager 7.2.1 The Contractor’s Project Manager is designated in Exhibit F (Contractor’s Administration). The Contractor shall notify the County in writing of any change in the name or address of the Contractor’s Project Manager. 7.2.2 The Contractor’s Project Manager shall be responsible for the Contractor’s day-to-day activities as related to this Contract and shall meet and coordinate with County’s Project Manager and County’s Contract Project Monitor on a regular basis.

  • Project Scope The physical scope of the Project shall be limited to only those capital improvements as described in Appendix A of this Agreement. In the event that circumstances require a change in such physical scope, the change must be approved by the District Committee, recorded in the District Committee's official meeting minutes, and provided to the OPWC Director for the execution of an amendment to this Agreement.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!