Requested Regulatory Flexibility Sample Clauses

Requested Regulatory Flexibility. The proposed project will require specific regulatory relief from the reporting and signatory requirements of 40 CFR §270.11, in addition to reporting flexibility from several NMED Bureaus. The web-based system will not eliminate any regulatory reporting requirement; only modify the current format, delivery method, and archival procedures. NASA proposes that the regulatory flexibility issues requested in this proposal do not require specific regulatory relief and will be obtained through permit modifications, NMED Bureau-initiated changes, and/or mutually agreeable changes to current practices. NASA requests the following regulatory relief from the EPA (regulatory citations in bold-request for regulatory relief in italics): §270.11 Signatories to permit applications and reports.
AutoNDA by SimpleDocs
Requested Regulatory Flexibility. EPA, with the assistance of NMED and NASA, will perform a legal analysis of EPA-administered environmental regulations that apply to NASA’s facility, to determine which current information-related requirements (if any) will require regulatory modification to implement this project. Such requirements could include, for example, the signatory requirements for RCRA permit applications, modifications and reports (40 CFR §270.11, §270.42(a)(i)). Based on this analysis, EPA will initiate two multi-media rulemakings effort to promulgate any regulatory changes necessary to facilitate this project. The first rulemaking will cover submissions on CD-ROM , the second rulemaking will cover web based submissions for compliance purposes in phases 3 through 6. It is expected that such a final rulemaking will enable an electronic deliverable and secure digital signature system to provide all affected EPA offices with the flexibility to legally receive electronic deliverables with digital signatures for all environmental compliance requirements. NASA proposes that compliance documentation will not be submitted to a centralized data receipt center; rather a centralized “hub” on the Internet where e-mail notifications with hypertext links will guide the recipient to the specific document. All documentation and reports submitted to NMED have individual formats that were determined by NASA, and are forwarded to different personnel within several separate Bureaus. The web-based system will not eliminate any regulatory reporting requirement; only modify the current format, delivery method, and archival procedures. The NASA proposal for web-based electronic deliverables and digital signatures is provided in Section 3.2.4. Actual “submittal” of the signature and certification requirements is proposed as an e-mail notification with hypertext links to the web-based documents, and will include a date/time stamp to document receipt, a secure digital signature, and the certification statement. In addition to any regulatory changes that may be needed for this project, EPA and NMED, in consultation with NASA, will also amend or modify other existing documents (e.g., permits, enforcement orders) and policies that now require submission of information in hard copy, to instead allow electronic reporting of such information and documentation. Such changes may require modifications to existing permits, orders or other documents or agreements. Specific examples of such information requirements ...

Related to Requested Regulatory Flexibility

  • REGULATORY FILINGS AND CAISO TARIFF COMPLIANCE 3.1 Filing

  • Proposing Integration Activities in the Planning Submission No integration activity described in section 6.3 may be proposed in a CAPS unless the LHIN has consented, in writing, to its inclusion pursuant to the process set out in section 6.3(b).

  • Financial Viability and Regulatory Compliance 4.6.1 The Contractor warrants and represents that its corporate entity is in good standing with all applicable federal, state, and local licensing authorities and that it possesses all requisite licenses to perform the services required by this contract. The Contractor further warrants and represents that it owes no outstanding delinquent federal, state, or local taxes or business assessments.

  • Product Changes Vocera shall have the right, in its absolute discretion, without liability to End User, to update to provide new functionality or otherwise change the design of any Product or to discontinue the manufacture or sale of any Product. Vocera shall notify End User at least 90 days prior to the delivery of any Product which incorporates a change that adversely affects form, fit or function (“Material Change”). Vocera shall also notify End User at least 90 days prior to the discontinuance of manufacture of any Product. Notification will be made as soon as reasonably practical for changes associated with regulatory or health and safety issues.

  • Program Compliance The School Board shall be responsible for monitoring the program to provide technical assistance and to ensure program compliance.

  • Regulatory Compliance a. Monitor compliance with the 1940 Act requirements, including:

  • Loop Testing/Trouble Reporting 2.1.6.1 Think 12 will be responsible for testing and isolating troubles on the Loops. Think 12 must test and isolate trouble to the BellSouth portion of a designed/non- designed unbundled Loop (e.g., UVL-SL2, UCL-D, UVL-SL1, UCL-ND, etc.) before reporting repair to the UNE Customer Wholesale Interconnection Network Services (CWINS) Center. Upon request from BellSouth at the time of the trouble report, Think 12 will be required to provide the results of the Think 12 test which indicate a problem on the BellSouth provided Loop.

  • Statewide HUB Program Statewide Procurement Division Note: In order for State agencies and institutions of higher education (universities) to be credited for utilizing this business as a HUB, they must award payment under the Certificate/VID Number identified above. Agencies, universities and prime contractors are encouraged to verify the company’s HUB certification prior to issuing a notice of award by accessing the Internet (xxxxx://xxxxx.xxx.xxxxx.xx.xx/tpasscmblsearch/index.jsp) or by contacting the HUB Program at 000-000-0000 or toll-free in Texas at 0-000-000-0000.

  • Additional Information for Product Development Projects Outcome of product development efforts, such copyrights and license agreements. • Units sold or projected to be sold in California and outside of California. • Total annual sales or projected annual sales (in dollars) of products developed under the Agreement. • Investment dollars/follow-on private funding as a result of Energy Commission funding. • Patent numbers and applications, along with dates and brief descriptions.  Additional Information for Product Demonstrations: • Outcome of demonstrations and status of technology. • Number of similar installations. • Jobs created/retained as a result of the Agreement.

  • Requirement to Utilize HUB Compliance Reporting System Pursuant to Texas Administrative Code, Title 34, Part 1, Sections 20.285(f) and 20.287(b), TFC administers monthly administration HSP-PAR compliance monitoring through its HUB Compliance Reporting System commonly known as B2G. PSP and PSP’s subcontractors/subconsultants shall submit required PAR information into the B2G system. Any delay in the timely submission of PAR information into the B2G system will be treated as an invoicing error subject to dispute under Texas Government Code Section 2251.042.

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