Deliverable Schematic Sample Clauses

Deliverable Schematic. The Engineer shall consider the following in the analysis to optimize the design:
AutoNDA by SimpleDocs
Deliverable Schematic. The Engineer shall consider the following in the analysis to optimize the design: • Efficient use of the allocated ROW • Control of Access (COA) and driveway locations • Roadway and intersection geometry • Cross Sections • Bicycle and Pedestrian design • Drainage and Hydraulic designStopping Sight distance • Level-of-service • Traffic and signal operations • Construction, ROW, easement, and utility costsConstruction sequencing DocuSign Envelope ID: E7DAA847-BF7C-44E6-B32B-712DD5062C72 • Traffic control during constructionRoadside safety appurtenances • Large guide signage • Environmental mitigation (For example: Noise Walls, Storm Water Best Management Practices (BMP’s), etc.) • Bridge Layouts and Clearance • Railroads (if applicable) • Interface with existing High Occupancy Vehicle (HOV) Lane, Managed Lanes, and park-and- ride facilities • Accomodation of ultimate corridor configuration. • Accomodation of future cross street expansion as described in local thoroughfare plan if applicable. • Avoidance of utility lines if feasible. • Impact of construction delays from utility relocations.
Deliverable Schematic. The Engineer shall consider the following in the analysis:
Deliverable Schematic. The Engineer shall consider the following in the analysis to optimize the design:  Bicycle and Pedestrian design  Bridge Layouts and Clearance  Construction sequencing  Construction, ROW, easement, and utility costs  Conceptual Aesthetic Schematics  Driveway locations  Cross Sections DocuSign Envelope ID: 3834C76D-F898-4EF5-A280-35D1D4DA0CBD  Drainage and Hydraulic designEfficient use of available ROW  Environmental mitigation  Large guide signage  Level‐of‐service  Roadside safety appurtenances  Roadway and intersection geometry  Stopping Sight distanceSafety Performance  Traffic and signal operations  Traffic control during construction Data Collection. The Engineer shall conduct field reconnaissance and collect data as necessary to complete the schematic design. Data must include the following information:  Adopted land use maps and plans as available  Aerial photos, planimetric mapping, and DTM  Available Corridor Major Investment StudiesDesign data from record drawings of existing and proposed facilitiesEnvironmental Data  Existing and future design year traffic dataFederal Emergency Management Agency (FEMA) Flood Boundary Maps and Flood Insurance Studies and Models  Previously prepared drainage studies  Public and private utility information  Roadway inventory information, including the number of lanes, speed limits, pavement widths and rating, bridge widths and ratings, and ROW widths
Deliverable Schematic. The Engineer shall consider the following in the analysis to optimize the design: • Efficient use of the allocated ROW • Control of Access (COA) and driveway locations • Roadway and intersection geometry • Cross Sections • Bicycle and Pedestrian design • Drainage and Hydraulic designStopping Sight distance • Level-of-service • Traffic and signal operations • Construction, ROW, easement, and utility costsConstruction sequencingTraffic control during constructionRoadside safety appurtenances DocuSign Envelope ID: 5A2DC6EC-64DB-4A02-A984-B96FAAFF8279 • Large guide signage • Environmental mitigation (For example: Noise Walls) • Bridge Layouts and Clearance • Railroads (if applicable) PeopleSoft Contract No. 7490 Legacy Contract No. 12-7IDP5009 • Interface with existing High Occupancy Vehicle (HOV) Lane, Managed Lanes, and park-and- ride facilities Project Management and Coordination • The Engineer shall direct and coordinate the various elements and activities associated with developing the design schematic. • The Engineer shall prepare the detailed graphic Project Work Schedule indicating tasks, critical dates, milestones, deliverables and State review requirements. The Project Work Schedule will depict the order of the various tasks, milestones, and deliverables. The Engineer shall review and provide comments on its elements of the schedule to the State. • The Engineer shall submit written monthly Progress Reports to the State. • The Engineer shall prepare subcontracts for subconsultants, direct and monitor subconsultants activities, and review subconsultant work and invoices. • The Engineer shall provide ongoing quality assurance and quality control to ensure completeness of product and compliance with the State procedures. • The Engineer shall prepare and submit invoices.

Related to Deliverable Schematic

  • Deliverables Upon satisfactory completion of the work authorization, the Engineer shall submit the deliverables as specified in the executed work authorization to the State for review and acceptance.

  • Escrow Format Specification 3.1. Deposit’s Format. Registry objects, such as domains, contacts, name servers, registrars, etc. will be compiled into a file constructed as described in draft-xxxxx-xxxxxxx-registry-data-escrow, see Part A, Section 9, reference 1 of this Specification and draft-xxxxx-xxxxxxx-dnrd-objects-mapping, see Part A, Section 9, reference 2 of this Specification (collectively, the “DNDE Specification”). The DNDE Specification describes some elements as optional; Registry Operator will include those elements in the Deposits if they are available. If not already an RFC, Registry Operator will use the most recent draft version of the DNDE Specification available at the Effective Date. Registry Operator may at its election use newer versions of the DNDE Specification after the Effective Date. Once the DNDE Specification is published as an RFC, Registry Operator will implement that version of the DNDE Specification, no later than one hundred eighty (180) calendar days after. UTF-8 character encoding will be used.

  • MSAA Indicator Technical Specification Document This Agreement shall be interpreted with reference to the MSAA Indicator Technical Specifications document.

  • Project Deliverables The Contractor shall provide each of the following deliverables in writing to the City for review and approval to achieve the project objectives.

  • Billing Specifications 55.6.1 The Parties agree that billing requirements and outputs will be consistent with the Ordering & Billing Form (OBF) and also with Telcordia Technologies Billing Output Specifications (BOS).

  • Technical Specifications The Technical Specifications furnished on the CD are intended to establish the standards for quality, performance and technical requirements for all labor, workmanship, material, methods and equipment necessary to complete the Work. When specifications and drawings are provided or referenced by the County, these are to be considered part of the Scope of Work, and to be specifically documented in the Detailed Scope of Work. For convenience, the County supplied specifications, if any, and the Technical Specifications furnished on the CD.

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