% Design Coordination Meeting and Plans‐In‐Hand Site Visit Sample Clauses

% Design Coordination Meeting and Plans‐In‐Hand Site Visit. This meeting will be held with the Airport and any other airport stakeholder, (stakeholders to be determined by the Airport), shortly after the 95% Submittal to discuss the design on a sheet‐by‐sheet basis. Discussion items may include final construction phasing, material constructability, impacts to airport operations/tenants, review comments, schedule of anticipated federal funding, etc. It is anticipated that this meeting will be held at the Airport. Shortly after the 95% Submittal and before the final submittal (Bid Documents), the Engineer will perform a final plans‐in‐hand site visit to visually compare the pre‐final plans to existing field conditions. Design elements will be reviewed and/or confirmed in the field such as utility infrastructure and structures, pavement markings, grades, project limits, etc. This site visit will be held on the same day of a project review meeting as long at the meeting is held at the airport.
AutoNDA by SimpleDocs
% Design Coordination Meeting and Plans‐In‐Hand Site Visit this meeting will be held with the FAA, Airport, and key team members shortly after the 75% Submittal to discuss the design on a sheet-by-sheet basis. Discussion items may include construction phasing, material constructability, impacts to airport operations/tenants, review comments, etc. It is anticipated that this meeting will be held at the Airport. Shortly after the 75% Submittal and before proceeding with the remainder of the project, Xxxxxx will perform a plans-in-hand site visit to visually compare the plans and survey data to existing field conditions. Design elements will be reviewed and/or confirmed in the field such as utility infrastructure and structures (visible in the field), pavement markings, grades, project limits, drainage conditions, etc. Inconsistencies found during the field investigations (if any) will be corrected on the construction documents. This site visit will be held on the same day of a project review meeting as long at the meeting is held at the airport.

Related to % Design Coordination Meeting and Plans‐In‐Hand Site Visit

  • Approval of Plans and Specifications The Plans and Specifications will conform to the requirements and conditions set out by applicable law or any effective restrictive covenant, and to all governmental authorities which exercise jurisdiction over the Leased Premises or the construction thereon.

  • Preconstruction Meeting Furnish the names of the Certified Erosion and Sediment Control/Stormwater Supervisor, Certified Foremen, Certified Installers and Certified Designer and notify the Engineer of changes in certified personnel over the life of the contract within 2 days of change. Any company performing work for the North Carolina Department of Transportation has the ethical responsibility to fully disclose any reprimand or dismissal of an employee resulting from improper testing or falsification of records.

  • Order Coordination and Order Coordination-Time Specific 2.1.9.1 “Order Coordination” (OC) allows BellSouth and Lightyear to coordinate the installation of the SL2 Loops, Unbundled Digital Loops (UDL) and other Loops where OC may be purchased as an option, to Lightyear’s facilities to limit end user service outage. OC is available when the Loop is provisioned over an existing circuit that is currently providing service to the end user. OC for physical conversions will be scheduled at BellSouth’s discretion during normal working hours on the committed due date. OC shall be provided in accordance with the chart set forth below. 2.1.9.2 “Order Coordination – Time Specific” (OC-TS) allows Lightyear to order a specific time for OC to take place. BellSouth will make every effort to accommodate Lightyear’s specific conversion time request. However, BellSouth reserves the right to negotiate with Lightyear a conversion time based on load and appointment control when necessary. This OC-TS is a chargeable option for all Loops except Unbundled Copper Loops (UCL) and Universal Digital Channel (UDC), and is billed in addition to the OC charge. Lightyear may specify a time between 9:00 a.m. and 4:00 p.m. (location time) Monday through Friday (excluding holidays). If Lightyear specifies a time outside this window, or selects a time or quantity of Loops that requires BellSouth technicians to work outside normal work hours, overtime charges will apply in addition to the OC and OC-TS charges. Overtime charges will be applied based on the amount of overtime worked and in accordance with the rates established in the Access Services Tariff, Section E13.2, for each state. The OC-TS charges for an order due on the same day at the same location will be applied on a per Local Service Request (LSR) basis.

  • Construction Change Directives 1.1.1, 3.4.2, 3.11, 3.12.8, 4.2.8, 7.1.1, 7.1.2, 7.1.3, 7.3, 9.3.1.1 Construction Schedules, Contractor’s 3.10, 3.11, 3.12.1, 3.12.2, 6.1.3, 15.1.6.2

  • Information Systems Acquisition Development and Maintenance a. Client Data – Client Data will only be used by State Street for the purposes specified in this Agreement.

  • Construction Management Plan Contractor shall prepare and furnish to the Owner a thorough and complete plan for the management of the Project from issuance of the Proceed Order through the issuance of the Design Professional's Certificate of Material Completion. Such plan shall include, without limitation, an estimate of the manpower requirements for each trade and the anticipated availability of such manpower, a schedule prepared using the critical path method that will amplify and support the schedule required in Article 2.1.5 below, and the Submittal Schedule as required in Article 2.2.3. The Contractor shall include in his plan the names and resumés of the Project Superintendent, Project Manager and the person in charge of Safety.

  • Contract Negotiation Meetings When operational requirements permit, the Employer will grant leave without pay to an employee for the purpose of attending contract negotiation meetings on behalf of the Alliance. Preparatory Contract Negotiation Meetings

  • Project Implementation Manual The Recipient, through the PCU, shall: (i) take all action required to carry out Parts 1.1, 1.3, 1.4, 2, 3.1(b), 3.2, 3.3 and 4 (ii) of the Project in accordance with the provisions and requirements set forth or referred to in the Project Implementation Manual; (ii) submit recommendations to the Association for its consideration for changes and updates of the Project Implementation Manual as they may become necessary or advisable during Project implementation in order to achieve the objective of Parts 1.1, 1.3, 1.4, 2, 3.1(b), 3.2, 3.3 and 4(ii) of the Project; and (iii) not assign, amend, abrogate or waive the Project Implementation Manual or any of its provisions without the Association’s prior agreement. Notwithstanding the foregoing, if any of the provisions of the Project Implementation Manual is inconsistent with the provisions of this Agreement, the provisions of this Agreement shall prevail and govern.

  • Project Management Plan 3.2.1 Developer is responsible for all quality assurance and quality control activities necessary to manage the Work, including the Utility Adjustment Work. Developer shall undertake all aspects of quality assurance and quality control for the Project and Work in accordance with the approved Project Management Plan, Good Industry Practice and applicable Law. 3.2.2 Developer shall develop the Project Management Plan and its component parts, plans and other documentation in accordance with the requirements set forth in Section 1.5.2.5

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