Proposed MACT - Subpart DDDDD Sample Clauses

Proposed MACT - Subpart DDDDD. Subpart DDDDD, Industrial, Commercial, and Institutional Boilers and Process Heaters. On September 13, 2004 EPA promulgated Subpart DDDDD, a National Emission Standards for Hazardous Air Pollutants (NESHAPS) for Industrial, Commercial, and Institutional Boilers and Process Heaters. HVI has existing small, gaseous fueled heaters (under 10.000 MMBtu/hr) at this facility, however, the subpart does not specify any emission limits or work practice standards for this class of units. Thus, no DDDDD requirements apply.
AutoNDA by SimpleDocs

Related to Proposed MACT - Subpart DDDDD

  • CFR PART 200 Contract Provisions Explanation Required Federal contract provisions of Federal Regulations for Contracts for contracts with ESC Region 8 and TIPS Members: The following provisions are required to be in place and agreed if the procurement is funded in any part with federal funds. The ESC Region 8 and TIPS Members are the subgrantee or Subrecipient by definition. Most of the provisions are located in 2 CFR PART 200 - Appendix II to Part 200—Contract Provisions for Non-Federal Entity Contracts Under Federal Awards at 2 CFR PART 200. Others are included within 2 CFR part 200 et al. In addition to other provisions required by the Federal agency or non-Federal entity, all contracts made by the non- Federal entity under the Federal award must contain provisions covering the following, as applicable.

  • Background and Narrative of Budget Reductions 2. Assumptions Used in the Deficit Reduction Plan: - EBF and Estimated New Tier Funding: - Equal Assessed Valuation and Tax Rates: - Employee Salaries and Benefits: - Short and Long Term Borrowing: - Educational Impact: - Other Assumptions: - Has the district considered shared services or outsourcing (Ex: Transportation, Insurance) If yes please explain: ESTIMATED LIMITATION OF ADMINISTRATIVE COSTS (School Districts Only) (For Local Use Only)

  • Optional Xactimate Response Attachment (Part 2)

  • JOC Pricing of Itemized List of RS Means Non-Prepriced Items No response The Vendor may download the optional Pricing of Itemized List of RS Means Non-Prepriced Items form from the attachment tab, fill in the requested information, and upload the completed spreadsheet. DO NOT UPLOAD encrypted or password protected files. Reference Form (PARTS 1 & 2) 220107 Reference_Form.xls Valid Reference Email addresses are REQUIRED on the spreadsheet. The vendor must download the References spreadsheet from the attachment tab, fill in the requested information and upload the completed spreadsheet. DO NOT UPLOAD encrypted or password protected files.

  • Registry Functions Activity Report This report shall be compiled in a comma separated-value formatted file as specified in RFC 4180. The file shall be named “gTLD-activity-yyyymm.csv”, where “gTLD” is the gTLD name; in case of an IDN-TLD, the A-label shall be used; “yyyymm” is the year and month being reported. The file shall contain the following fields: Field # Field Name Description 01 operational-registrars number of operational registrars at the end of the reporting period 02 ramp-up-registrars number of registrars that have received a password for access to OT&E at the end of the reporting period 03 pre-ramp-up-registrars number of registrars that have requested access, but have not yet entered the ramp-up period at the end of the reporting period 06 web-whois-queries number of Web-based Whois queries responded during the reporting period, not including searchable Whois 09 dns-udp-queries-responded number of DNS queries received over UDP transport that were responded during the reporting period 10 dns-tcp-queries-received number of DNS queries received over TCP transport during the reporting period 11 dns-tcp-queries-responded number of DNS queries received over TCP transport that were responded during the reporting period 12 srs-dom-check number of SRS (EPP and any other interface) domain name “check” requests responded during the reporting period 13 srs-dom-create number of SRS (EPP and any other interface) domain name “create” requests responded during the reporting period 14 srs-dom-delete number of SRS (EPP and any other interface) domain name “delete” requests responded during the reporting period 15 srs-dom-info number of SRS (EPP and any other interface) domain name “info” requests responded during the reporting period 16 srs-dom-renew number of SRS (EPP and any other interface) domain name “renew” requests responded during the reporting period 17 srs-dom-rgp-restore-report number of SRS (EPP and any other interface) domain name RGP “restore” requests delivering a restore report responded during the reporting period 18 srs-dom-rgp-restore-request number of SRS (EPP and any other interface) domain name RGP “restore” requests responded during the reporting period 19 srs-dom-transfer-approve number of SRS (EPP and any other interface) domain name “transfer” requests to approve transfers responded during the reporting period 20 srs-dom-transfer-cancel number of SRS (EPP and any other interface) domain name “transfer” requests to cancel transfers responded during the reporting period 21 srs-dom-transfer-query number of SRS (EPP and any other interface) domain name “transfer” requests to query about a transfer responded during the reporting period 22 srs-dom-transfer-reject number of SRS (EPP and any other interface) domain name “transfer” requests to reject transfers responded during the reporting period 23 srs-dom-transfer-request number of SRS (EPP and any other interface) domain name “transfer” requests to request transfers responded during the reporting period 24 srs-dom-update number of SRS (EPP and any other interface) domain name “update” requests (not including RGP restore requests) responded during the reporting period 25 srs-host-check number of SRS (EPP and any other interface) host “check” requests responded during the reporting period 26 srs-host-create number of SRS (EPP and any other interface) host “create” requests responded during the reporting period 27 srs-host-delete number of SRS (EPP and any other interface) host “delete” requests responded during the reporting period 28 srs-host-info number of SRS (EPP and any other interface) host “info” requests responded during the reporting period 29 srs-host-update number of SRS (EPP and any other interface) host “update” requests responded during the reporting period 30 srs-cont-check number of SRS (EPP and any other interface) contact “check” requests responded during the reporting period 32 srs-cont-delete number of SRS (EPP and any other interface) contact “delete” requests responded during the reporting period 33 srs-cont-info number of SRS (EPP and any other interface) contact “info” requests responded during the reporting period 34 srs-cont-transfer-approve number of SRS (EPP and any other interface) contact “transfer” requests to approve transfers responded during the reporting period 35 srs-cont-transfer-cancel number of SRS (EPP and any other interface) contact “transfer” requests to cancel transfers responded during the reporting period 36 srs-cont-transfer-query number of SRS (EPP and any other interface) contact “transfer” requests to query about a transfer responded during the reporting period 37 srs-cont-transfer-reject number of SRS (EPP and any other interface) contact “transfer” requests to reject transfers responded during the reporting period 38 srs-cont-transfer-request number of SRS (EPP and any other interface) contact “transfer” requests to request transfers responded during the reporting period 39 srs-cont-update number of SRS (EPP and any other interface) contact “update” requests responded during the reporting period The first line shall include the field names exactly as described in the table above as a “header line” as described in section 2 of RFC 4180. No other lines besides the ones described above shall be included. Line breaks shall be <U+000D, U+000A> as described in RFC 4180. For gTLDs that are part of a single-instance Shared Registry System, the Registry Functions Activity Report may include the total contact or host transactions for all the gTLDs in the system. REGISTRATION DATA PUBLICATION SERVICES

  • OMB 2 CFR Part 200 Except for agreements that are straight hourly rate or fee for services contracts not built on a submitted Budget, all components of payment billed to COUNTY will be calculated in accordance with the Office of Management and Budget (OMB) 2 CFR Part 200.

  • ADMISSION REQUIREMENTS FOR SENIOR COLLEGE PROGRAM  The A.A. degree and a minimum GPA of 2.00  Grade of C or better in a credit-bearing mathematics course worth three or more credits*  Grade of C or better in freshman composition, its equivalent, or a higher-level English course* *(Effective 10/1/08, per University policy) Students who wish to transfer but do not meet all of the above requirements or are unable to enroll within two years after graduation will receive admission consideration under our standard transfer credit policies. Total transfer credits granted toward the baccalaureate degree: 60 Total additional credits required at the senior college to complete baccalaureate degree: 60 Total credits required for the B.A. in Global History: 120

  • Lobbying Activities - Standard Form - LLL No response Do not upload this form unless Vendor has reportable lobbying activities. There are Attributes entitled, “2 CFR Part 200 or Federal Provision - Xxxx Anti-Lobbying Amendment – Continued.” Properly respond to those Attributes and only upload this form if applicable/instructed. If upload is required based on your response to those Attributes, the Disclosure of Lobbying Activities – Standard Form - LLL must be downloaded from the “Attachments” section of the IonWave eBid System, reviewed, properly completed, and uploaded to this location.

  • COSTS DISTRIBUTED THROUGH COUNTYWIDE COST ALLOCATIONS The indirect overhead and support service costs listed in the Summary Schedule (attached) are formally approved as actual costs for fiscal year 2020-21, and as estimated costs for fiscal year 2022-23 on a “fixed with carry-forward” basis. These costs may be included as part of the county departments’ costs indicated effective July 1, 2022, for further allocation to federal grants and contracts performed by the respective county departments.

  • CONTRACT EXHIBIT I PREFERRED PRICING AFFIDAVIT This preferred-pricing affidavit is entered into in accordance with section 216.0113, F.S., and as required by Contract No. 80101507-21-STC-ITSA (“Contract”) between (“Contractor”) and the Department of Management Services. As the person authorized by Contractor to sign this affidavit, I attest that the Contractor is in full compliance with the preferred-pricing clause of the Contract. Contractor’s Name: By: Signature Printed Name/Title Date: STATE OF COUNTY OF Sworn to (or affirmed) and subscribed before me this day of , by . Signature of Notary Vendor Name: FEIN# Vendor’s Authorized Representative Name and Title: Address: City, State, and Zip code: Phone Number: ( ) - E-mail: CORPORATE SEAL (IF APPLICABLE) (Print, Type, or Stamp Commissioned Name of Notary Public) [Check One] Personally Known OR Produced the following I.D.

Time is Money Join Law Insider Premium to draft better contracts faster.