Noise Monitoring Sample Clauses

Noise Monitoring. 3.2.1 Impact noise monitoring was conducted at the 2 monitoring stations (NMS2 and NMS3B) for at least once per week during 07:00 – 19:00 in the reporting quarter. 3.2.2 The monitoring locations used during the reporting quarter are depicted in Figure 2. 3.2.3 No Action or Limit Level Exceedance of construction noise was recorded in the reporting quarter. 3.2.4 Major noise sources during the noise monitoring included construction activities of the Project and nearby traffic noise. 3.2.5 The number of impact noise monitoring events and exceedances are summarized in Table 3.3 and Table 3.4 respectively.
Sample 1
AutoNDA by SimpleDocs
Noise Monitoring. When the proposed noise and track keeping system is operational a report should be provided to the Forum on aircraft that persistently deviate from agreed flight paths. (see para 5.7.57)
Sample 1
Noise Monitoring. The Owner will: 8.1 by ( ) (or having carried out twelve months of noise monitoring at the Airport) agree with the Council new maximum noise levels for aircraft movements which will produce a significant reduction in the noise impact for individual aircraft over the previous two years of operation and which in no circumstances will be less than a 5% reduction over the average of the previous two years. Failure to agree on a suitable reduction level will result in the matter of a suitable reduction level being put to a mutually agreed and independent expert in aviation matters, or in the event of failure to agree within one month he shall be appointed by the President of the Institute of Vibration and Acoustic Engineers. The expert will decide the appropriate level of reduction suitable for the Airport by reference to the levels of individual aircraft noise acceptable at one or more comparable airports, judged to be comparable by reference to the characteristics of operation and geographic proximity to urban areas. The expert will act as an expert and not as an arbitrator and shall be entitled to rely on his own judgement and opinion. He shall afford the Parties a reasonable opportunity to submit both representations and counter-representations to him and shall consider all of the same. He shall give to the Parties written notice of his determination (within 25 working days after counter-representations) (if any) and his decision shall be binding on both Parties to the Agreement in respect of the level of reduction to be achieved; 8.2 on and after 1st April 2002 pay the sum of £500 per aircraft exceeding the agreed or imposed maximum noise level referred to in 8.1 and for every 1 decibel (dB) above the agreed base level the additional sum of £500
Sample 1
Noise Monitoring. Conduct property boundary noise monitoring in the vicinity of 000 Xxx Xxxxxxxxxxxx Xxxx to document sound levels when motorized vehicles are being utilized on the property. The monitoring will occur on a typical weekday and Saturday.
Sample 1
Noise Monitoring. 1. The Certificate Holder shall perform noise monitoring following beginning of operation. In addition to monitoring A-weighted sound levels, the Certificate Holder will monitor low frequency noise and tones, including the gathering of one-third octave band data. Monitoring shall be conducted according to the plan developed during the pre-operating noise monitoring. 2. A preliminary noise monitoring report will be prepared and submitted to the Council within sixty (60) days after beginning of operations. Copies of the report will also be provided to the City of Sumas, Whatcom County, the City of Abbotsford and the Province of British Columbia. 3. If, at any time, monitoring indicates that the Generation Facility is not in compliance with City of Sumas or Department of Ecology noise regulations or that the Generation Facility generates low frequency sounds or tones that EFSEC determines are reasonably objectionable, the Certificate Holder shall investigate the source of the noise and identify, develop and implement one or more means of mitigating the noise including, but not limited to, installing additional noise mitigation measures at the Generation Facility. 4. No later than thirty (30) days after the end of the S2GF's first operational year, the Certificate Holder shall submit for the Council's approval a report providing the pre- and post-operation monitoring results and any mitigation plan found to be necessary. Copies of the report will also be provided to the City of Sumas, Whatcom County, the City of Abbotsford and the Province of British Columbia. 5. Once post operational monitoring indicates that the Generation Facility is in compliance with City of Sumas and Department of Ecology noise regulations and that there is no reasonably objectionable low frequency noise or tones, the post-operation noise-monitoring program will be deemed complete. However, the Certificate Holder shall be required to repeat operational noise monitoring in the 5th year of Generation Facility operation, and at 5-year increments of Generation Facility operation thereafter, to confirm that noise generated by the Generation Facility has not changed substantially. Monitoring Reports shall be submitted no later than thirty (30) days after the end of the monitoring period.
Sample 1
Noise Monitoring. The CGF will be designed to meet applicable state and local noise standards. Following commencement of plant operation, noise monitoring will be conducted to verify the model-predicted levels at the residential areas where increased noise was predicted. The Council will review the monitoring results to determine if the state and local standards are being exceeded. If the Council finds that standards are being exceeded, it will direct that additional noise mitigation measures be developed and implemented1. 1 To provide consistency with the Attachments, the language in I. Noise Monitoring has been replaced with the language shown in original Attachment 6 Mitigation Measures and Project Conditions, Part IV Attached hereto and incorporated in this Agreement by this reference are the following: 1. Site Legal Description 2. Approval of Notice of Construction and Prevention of Significant Deterioration Application 3. Excavation and Erosion Control Measures 4. Mitigation Measures and Project Conditions 5. Stipulated Agreements with Critical Issues Council
Sample 1
Noise Monitoring 
Sample 1Sample 2Sample 3See All (10)
AutoNDA by SimpleDocs

Related to Noise Monitoring

  • Project Monitoring The Developer shall provide regular status reports to the NYISO in accordance with the monitoring requirements set forth in the Development Schedule, the Public Policy Transmission Planning Process Manual and Attachment Y of the OATT.

  • Compliance Monitoring Grantee must be subject to compliance monitoring during the period of performance in which funds are Expended and up to three years following the closeout of all funds. In order to assure that the program can be adequately monitored, the following is required of Grantee: a. Grantee must maintain a financial tracking system provided by Florida Housing that ensures that CRF funds are Expended in accordance with the requirements in this Agreement. b. Grantee must maintain records on all awards to Eligible Persons or Households. These records must include, but are not limited to: i. Proof of income compliance (documentation from submission month, including but not limited to paystub, Florida unemployment statement, social security and/or disability statement, etc.); ii. Lease; and iii. Documentation of rental assistance payments made.

  • Infrastructure Infrastructure serves as the foundation and building blocks of an integrated IT solution. It is the hardware which supports Application Services (C.3.2) and IT Management Services (C.3.3); the software and services which enable that hardware to function; and the hardware, software, and services which allow for secure communication and interoperability between all business and application service components. Infrastructure services facilitate the development and maintenance of critical IT infrastructures required to support Federal government business operations. This section includes the technical framework components that make up integrated IT solutions. One or any combination of these components may be used to deliver IT solutions intended to perform a wide array of functions which allow agencies to deliver services to their customers (or users), whether internal or external, in an efficient and effective manner. Infrastructure includes hardware, software, licensing, technical support, and warranty services from third party sources, as well as technological refreshment and enhancements for that hardware and software. This section is aligned with the FEA/DoDEA Technical Reference Model (TRM) which describes these components using a vocabulary that is common throughout the entire Federal government. A detailed review of the TRM is provided in Section J, Attachment 5. Infrastructure includes complete life cycle support for all hardware, software, and services represented above, including planning, analysis, research and development, design, development, integration and testing, implementation, operations and maintenance, information assurance, and final disposition of these components. The services also include administration and help desk functions necessary to support the IT infrastructure (e.g., desktop support, network administration). Infrastructure components of an integrated IT solution can be categorized as follows:

  • Program Monitoring The Contractor will make all records and documents required under this Agreement as outlined here, in OEC Policies and NHECC Policies available to the SRO or its designee, the SR Fiscal Officer or their designee and the OEC. Scheduled monitoring visits will take place twice a year. The SRO and OEC reserve the right to make unannounced visits.

  • NO HARDSTOP/PASSIVE LICENSE MONITORING Unless an Authorized User is otherwise specifically advised to the contrary in writing at the time of order and prior to purchase, Contractor hereby warrants and represents that the Product and all Upgrades do not and will not contain any computer code that would disable the Product or Upgrades or impair in any way its operation based on the elapsing of a period of time, exceeding an authorized number of copies, advancement to a particular date or other numeral, or other similar self-destruct mechanisms (sometimes referred to as “time bombs,” “time locks,” or “drop dead” devices) or that would permit Contractor to access the Product to cause such disablement or impairment (sometimes referred to as a “trap door” device). Contractor agrees that in the event of a breach or alleged breach of this provision that Authorized User shall not have an adequate remedy at law, including monetary damages, and that Authorized User shall consequently be entitled to seek a temporary restraining order, injunction, or other form of equitable relief against the continuance of such breach, in addition to any and all remedies to which Authorized User shall be entitled.

  • Monitoring In each case in which the Foreign Custody Manager maintains Foreign Assets with an Eligible Foreign Custodian selected by the Foreign Custody Manager, the Foreign Custody Manager shall establish a system to monitor (i) the appropriateness of maintaining the Foreign Assets with such Eligible Foreign Custodian and (ii) the contract governing the custody arrangements established by the Foreign Custody Manager with the Eligible Foreign Custodian. In the event the Foreign Custody Manager determines that the custody arrangements with an Eligible Foreign Custodian it has selected are no longer appropriate, the Foreign Custody Manager shall notify the Board in accordance with Section 3.2.5 hereunder.

  • Contract Monitoring The criminal background checks required by this rule shall be national in scope, and must be conducted at least once every three (3) years. Contractor shall make the criminal background checks required by Paragraph IV.G.1 available for inspection and copying by DRS personnel upon request of DRS.

  • Workload Management 11.1 The parties to this Agreement acknowledge that employees and management have a responsibility to maintain a balanced workload and recognise the adverse affects that excessive workloads may have on employee/s and the quality of resident/client care. 11.2 To ensure that employee concerns involving excessive workloads are effectively dealt with by Management the following procedures should be applied: (a) Step 1: In the first instance, employee/s should discuss the issue with their immediate supervisor and, where appropriate, explore solutions. (b) Step 2: If a solution cannot be identified and implemented, the matter should be referred to an appropriate senior manager for further discussion. (c) Step 3: If a solution still cannot be identified and implemented, the matter should be referred to the Facility Manager for further discussion. (d) Step 4: The outcome of the discussions at each level and any proposed solutions should be recorded in writing and fed back to the effected employees. 11.3 Workload management must be an agenda item at staff meetings on at least a quarterly basis. Items in relation to workloads must be recorded in the minutes of the staff meeting, as well as actions to be taken to resolve the workloads issue/s. Resolution of workload issues should be based on the following criteria including but not limited to: (a) Clinical assessment of residents’ needs; (b) The demand of the environment such as facility layout; (c) Statutory obligation, (including, but not limited to, work health and safety legislation); (d) The requirements of nurse regulatory legislation; (e) Reasonable workloads (such as roster arrangements); (f) Accreditation standards; and (g) Budgetary considerations. 11.4 If the issue is still unresolved, the employee/s may advance the matter through Clause 9 Dispute Resolution Procedure. Arbitration of workload management issues may only occur by agreement of the employer and the employee representative, which may include the union/s.

  • Performance Monitoring ‌ A. Performance Monitoring of Subrecipient by County, State of California and/or HUD shall consist of requested and/or required written reporting, as well as onsite monitoring by County, State of California or HUD representatives. B. County shall periodically evaluate Subrecipient’s progress in complying with the terms of this Contract. Subrecipient shall cooperate fully during such monitoring. County shall report the findings of each monitoring to Subrecipient. C. County shall monitor the performance of Subrecipient against the goals, outcomes, milestones and performance standards required herein. Substandard performance, as determined by County, will constitute non-compliance with this Contract for which County may immediately terminate the Contract. If action to correct such substandard performance is not taken by Subrecipient within the time period specified by County, payment(s) will be denied in accordance with the provisions contained in this Paragraph 47 of this Contract. D. HUD in accordance with 24 CFR Part 570 Subpart O, 570.902, will annually review the performance of County to determine whether County has carried out its Community Development Block Grant (CDBG) assisted activities in a timely manner and has significantly disbursed CDBG funds and met the mandated “1.5 ratio” threshold. Subrecipient is responsible to ensure timely drawdown of funds.

  • Telephone Monitoring You agree that Chase and its third-party service providers may listen to and record telephone calls as part of providing program services.

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