NOISE MANAGEMENT PLAN Sample Clauses

NOISE MANAGEMENT PLAN. 1.1 Prior to the Main Development Commencement Date MVV shall submit to the Council in writing the Noise Management Plan 1.2 MVV shall not Commence the Main Development until the Council has approved in writing the Noise Management Plan 1.3 With effect from the Main Development Commencement Date MVV shall implement the Noise Management Plan. 1.4 In the event that there is a Noise Event MVV shall submit to the Council in writing for approval the Noise Mitigation Measures 1.5 With effect from the date of approval of the Noise Mitigation Measures MVV shall implement the same and shall use its reasonable endeavours to do so within the timetable specified in the Noise Mitigation Measures 1.6 Subject to paragraph 1.7 paragraphs 1.3 to 1.5 shall only apply for a period of twenty-five
AutoNDA by SimpleDocs
NOISE MANAGEMENT PLAN. 1.1 The Operator shall implement and continue to operate the Noise Management Plan from the date of the Section 73 Planning Permission subject to such modifications as may be agreed in writing by the Council following review of the Noise Management Plan as provided for in the ensuing sub- paragraph 1.2 of this Schedule. 1.2 The Noise Management Plan shall be subject to periodic review by the Council on the Noise Management Plan Review Dates as follows: 1.2.1 On or before each of the Noise Management Plan Review Dates the Operator shall produce and submit to the Council for its written approval a report on the operation of the Noise Management Plan which shall review the effectiveness of the Noise Management Plan in achieving the principal objective of minimising noise disturbance from aircraft using the Airport and which shall include for the period since the Noise Management Plan was last approved by the Council or since the last Noise Management Plan Review Date (whichever shall be the later date) as a minimum the following: (A) the details of aircraft using the airport including the numbers and types of aircraft taking off and landing at the Airport; (B) details of any infringements of noise limits specified for arriving and departing aircraft and of any deviations from the tracks to be followed by aircraft using the Airport; (C) the number of complaints received from the public in relation to noise disturbance, together with their details including their geographic origin and type; (D) details of any Penalties imposed upon aircraft operators under the terms of the Noise Management Plan; (E) details of the airborne noise and ground noise abatement procedures adopted for the Airport and their effectiveness; (F) the effectiveness of any modifications to the Noise Management Plan or earlier review of it previously implemented; (G) any proposed modifications to the Noise Management Plan to achieve better the principal objective of minimising noise disturbance from aircraft using the Airport. 1.2.2 The Council shall either: (A) approve such report; or (B) (acting reasonably) request in writing that the report incorporates further or modified information and controls to the extent necessary to be able fully to monitor the operation of the Noise Management Plan or to achieve better the principal objective of minimising noise disturbance from aircraft using the Airport, including (if appropriate) further or alternative modifications to the Noise Management Plan...
NOISE MANAGEMENT PLAN. Operator shall prepare a plan to manage noise at or below the levels indicated in Exhibit B. The plan must include a baseline noise study as well as noise modeling of equipment proposed for the site for drilling and completions.
NOISE MANAGEMENT PLAN. Operators may be required to provide for additional noise mitigation based on the following site specific characteristics considering the distance from the nearest residential structure:
NOISE MANAGEMENT PLAN. 13.1 Prior to the Runway Extension coming into Operation, the Airport Operator shall submit to the Council for approval a noise management plan (the "First Noise Management Plan") which complies with Directive EC/2002/30 and the International Civil Aviation Organisation's balanced approach to aircraft noise management contained in Appendix C of Assembly Resolution AS35-5. 13.2 The Airport Operator shall not Operate the Runway Extension unless and until the First Noise Management Plan has been approved by the Council and implemented by the Airport Operator. 13.3 Prior to the geographical area enclosed by the 57dB LAeq, 16hr annual average mode daytime noise contour exceeding a total area of 1.8km2, the Airport Operator shall submit to the Council for approval a second noise management plan (the "Second Noise Management Plan") which complies with Directive EC/2002/30 and the International Civil Aviation Organisation's balanced approach to aircraft noise management contained in Appendix C of Assembly Resolution AS35-5. 13.4 The Airport Operator shall not permit the geographical area enclosed by the 57dB LAeq, 16hr annual average mode daytime noise contour to exceed a total area of 1.8km2 unless and until the Second Noise Management Plan has been approved by the Council and implemented by the Airport Operator. 13.5 Following approval of the Second Noise Management Plan, the Airport Operator shall not permit the geographical area enclosed by the 57dB LAeq, 16hr summer average mode daytime noise contour to exceed a total area of 2.0km2. 13.6 The First Noise Management Plan shall include:- 13.6.1 the siting of ground operations to ensure that sensitive receptors are not subject to unnecessary ground noise; 13.6.2 the use of auxiliary power units to be limited to:- (a) up to a maximum of five minutes after "on blocks"; and (b) up to a maximum of thirty minutes before estimated time of departure 13.6.3 engine ground running for maintenance purposes to be only permitted within a maximum period of 0800-2000 Monday to Friday and 0900-1700 on weekends and bank holidays; 13.6.4 the establishing of lines of communication between the Airport Operator and local residents to facilitate the addressing of any concerns relating to noise emanating from the Airport; and 13.6.5 the production of retrospective noise contours for the previous Operating Calendar Year illustrating the annual and summer average noise levels in the previous Operating Calendar Year and the calculation o...
NOISE MANAGEMENT PLAN. 1.2 (b) in the previous draft S.1063 states that the noise management plan will include a target noise performance standard devised specifically in terms of ornithology. The updated draft S.106 no longer contains reference to ornithology with regard to the noise management plan. Given that LAA acknowledges that increased aircraft noise would impact to some extent on bird reserves in and around the SPA4, we request clarification as to why this text for the noise management plan has been amended to exclude reference to birds.
NOISE MANAGEMENT PLAN. The Applicant must prepare a Noise Management Plan for the development to the satisfaction of the Secretary. This plan must:
AutoNDA by SimpleDocs

Related to NOISE MANAGEMENT PLAN

  • Management Plan The Management Plan is the description and definition of the phasing, sequencing and timing of the major Individual Project activities for design, construction procurement, construction and occupancy as described in the IPPA.

  • 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

  • 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.

  • Disease Management If you have a chronic condition such as asthma, coronary heart disease, diabetes, congestive heart failure, and/or chronic obstructive pulmonary disease, we’re here to help. Our tools and information can help you manage your condition and improve your health. You may also be eligible to receive help through our care coordination program. This voluntary program is available at no additional cost you. To learn more about disease management, please call (000) 000-0000 or 0-000-000-0000. Our entire contract with you consists of this agreement and our contract with your employer. Your ID card will identify you as a member when you receive the healthcare services covered under this agreement. By presenting your ID card to receive covered healthcare services, you are agreeing to abide by the rules and obligations of this agreement. Your eligibility for benefits is determined under the provisions of this agreement. Your right to appeal and take action is described in Appeals in Section 5. This agreement describes the benefits, exclusions, conditions and limitations provided under your plan. It shall be construed under and shall be governed by the applicable laws and regulations of the State of Rhode Island and federal law as amended from time to time. It replaces any agreement previously issued to you. If this agreement changes, an amendment or new agreement will be provided.

  • Case Management Prompt resolution of any dispute is important to both parties; and the parties agree that the arbitration of any dispute shall be conducted expeditiously. The arbitrators are instructed and directed to assume case management initiative and control over the arbitration process (including scheduling of events, pre-hearing discovery and activities, and the conduct of the hearing), in order to complete the arbitration as expeditiously as is reasonably practical for obtaining a just resolution of the dispute.

  • Virus Management DST shall maintain a malware protection program designed to deter malware infections, detect the presence of malware within DST environment.

  • Emergency Mode Operation Plan Contractor must establish a documented plan to enable continuation of critical business processes and protection of the security of electronic County PHI or PI in the event of an emergency. Emergency means any circumstance or situation that causes normal computer operations to become unavailable for use in performing the work required under this Agreement for more than twenty-four (24) hours.

  • Change Management BellSouth provides a collaborative process for change management of the electronic interfaces through the Change Control Process (CCP). Guidelines for this process are set forth in the CCP document as amended from time to time during this Agreement. The CCP document may be accessed via the Internet at xxxx://xxx.xxxxxxxxxxxxxxx.xxxxxxxxx.xxx.

  • Traffic Management 9.2.1 During the Operating Period, Developer shall be responsible for the general management of traffic on the Project. Developer shall manage traffic so as to preserve and protect safety of traffic on the Project and Related Transportation Facilities and, to the maximum extent practicable, to avoid disruption, interruption or other adverse effects on traffic flow, throughput or level of service on the Project and Related Transportation Facilities. Developer shall conduct traffic management in accordance with all applicable Technical Provisions, Technical Documents, Laws and Governmental Approvals, and in accordance with the Traffic Management Plan. 9.2.2 Developer shall prepare and submit to TxDOT and the Independent Engineer for TxDOT approval a Traffic Management Plan for managing traffic on the Project and Related Transportation Facilities after the commencement of traffic operations on any portion of the Project, addressing (a) orderly and safe movement and diversion of traffic on Related Transportation Facilities during Project construction, (b) orderly and safe movement of traffic on the Project and (c) orderly and safe diversion of traffic on the Project and Related Transportation Facilities necessary in connection with field maintenance and repair work or Renewal Work or in response to Incidents, Emergencies and lane closures. Developer shall prepare the Traffic Management Plan according to the schedule set forth in the Technical Provisions. The Traffic Management Plan shall comply with the Technical Provisions and Technical Documents concerning traffic management and traffic operations. Developer shall carry out all traffic management during the Term in accordance with the approved Traffic Management Plan. 9.2.3 Developer shall implement the Traffic Management Plan to promote safe and efficient operation of the Project and Related Transportation Facilities at all times during the course of any construction or operation of the Project and during the Utility Adjustment Work. 9.2.4 TxDOT shall have at all times, without obligation or liability to Developer, the right 9.2.4.1 Issue Directive Letters to Developer regarding traffic management 9.2.4.2 Provide on the Project, via message signs or other means consistent with Good Industry Practice, non-Discriminatory traveler and driver information, and other public information (e.g. amber alerts), provided that the means to disseminate such information does not materially interfere with the functioning of the ETCS.

  • Enterprise Information Management Standards Grantee shall conform to HHS standards for data management as described by the policies of the HHS Office of Data, Analytics, and Performance. These include, but are not limited to, standards for documentation and communication of data models, metadata, and other data definition methods that are required by HHS for ongoing data governance, strategic portfolio analysis, interoperability planning, and valuation of HHS System data assets.

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