Ambient Air Monitoring Branch Sample Clauses

Ambient Air Monitoring Branch. The Ambient Air Monitoring Branch maintains and analyzes the information from Indiana's ambient air monitoring stations located across the state. This includes: monitoring for all criteria pollutants, conducting ambient monitoring for certain air toxics, quality assuring data, and communication of monitoring information to the public through Ozone Web, ToxWatch and other means. a) Continue to operate and review all ambient networks to track National Ambient Air Quality Standards compliance for all criteria pollutants. (1) Track monthly valid data return. 100% complete - ongoing. The Air Monitoring Branch (AMB) tracks the valid data return for all criteria and non-criteria pollutants monitored. Valid data return for July 01 through December 02: SO2 - 95%;l O3 - 97%; CO - 97%; NO/NOX - 89%, Cont PM10 - 96%; Cont PM25 - 97% Met - 96%. (2) Achieve 90% valid data return for intermittent parameters. 100% complete - ongoing. The Air Monitoring Branch tracks the valid data return for VDR for intermittent parameters. Valid data return for: PM10 ( July 01 - Jan. 03) - 95%; Lead (July 01-Dec. 02) - 97%; PM2.5 (July 01 - Mar. 03) - 93%. (3) Provide final, quality assured ozone data after close of ozone season. 100% complete. The Air Monitoring Branch completed the final quality assurance on the 2001 data on November 29, 2001. All 2002 ozone data has been checked and quality assured. (4) Conduct annual network review in conjunction with Lake Michigan Air Directors Consortium Regional Planning Organization. Complete recommendations for revised network. 85% complete. A draft of the network review has been finalized in conjunction with LADCO and EPA, Region 5. The internal review process is continuing through 2003 with input from IDEM staff, other agencies, and the public. (5) Identify and implement first phase of network revisions. 80% complete. A five year plan for network revisions has been developed and is in a draft phase. The write-up to accompany the revisions is being worked on and must be reviewed by other staff and agencies prior to implementation. Once the plan is finalized by IDEM, the first phase of network changes will be implemented. b) Continue Indiana Air Toxic Monitoring Program (1) Continue operation of 8 permanent canister sites and one special study site (School 21 in Indianapolis). 100% complete. All sites are operational. The continuous AutoGC system is installed at the school-21 site and collecting data for ozone precursor compounds on an hourly ba...
View Source
Ambient Air Monitoring Branch. ▇▇▇▇ ▇▇▇▇▇▇ Branch Chief Phone: (▇▇▇) ▇▇▇-▇▇▇▇ Email: ▇▇▇▇▇▇▇@▇▇▇.▇▇▇▇▇.▇▇.▇▇
View Source

Related to Ambient Air Monitoring Branch

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

  • Drainage Systems (1) Clear culvert inlets, outlets, and sediment catching basins. (2) Maintain waterbars, drainage dips, and other water diversion measures. (3) During active use, patrol and maintain functional drainage. (4) Repair damaged culvert ends.

  • Configuration Management The Contractor shall maintain a configuration management program, which shall provide for the administrative and functional systems necessary for configuration identification, control, status accounting and reporting, to ensure configuration identity with the UCEU and associated cables produced by the Contractor. The Contractor shall maintain a Contractor approved Configuration Management Plan that complies with ANSI/EIA-649 2011. Notwithstanding ANSI/EIA-649 2011, the Contractor’s configuration management program shall comply with the VLS Configuration Management Plans, TL130-AD-PLN-010-VLS, and shall comply with the following:

  • Infrastructure Vulnerability Scanning Supplier will scan its internal environments (e.g., servers, network devices, etc.) related to Deliverables monthly and external environments related to Deliverables weekly. Supplier will have a defined process to address any findings but will ensure that any high-risk vulnerabilities are addressed within 30 days.

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If WCS chooses to subtend a Verizon access Tandem, WCS’s NPA/NXX must be assigned by WCS to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG. 9.2.2 WCS shall establish Access Toll Connecting Trunks pursuant to applicable access Tariffs by which it will provide Switched Exchange Access Services to Interexchange Carriers to enable such Interexchange Carriers to originate and terminate traffic to and from WCS’s Customers. 9.2.3 The Access Toll Connecting Trunks shall be two-way trunks. Such trunks shall connect the End Office WCS utilizes to provide Telephone Exchange Service and Switched Exchange Access to its Customers in a given LATA to the access Tandem(s) Verizon utilizes to provide Exchange Access in such LATA. 9.2.4 Access Toll Connecting Trunks shall be used solely for the transmission and routing of Exchange Access to allow WCS’s Customers to connect to or be connected to the interexchange trunks of any Interexchange Carrier which is connected to a Verizon access Tandem.