Programmatic Guidance Sample Clauses

Programmatic Guidance. Note to Applicants: This document MUST be used in conjunction with SAMHSA’s “Funding Opportunity Announcement (FOA) PART II: Administrative and Application Submission Requirements for Discretionary Grants and Cooperative Agreements”. PART I is individually tailored for each FOA. PART II includes requirements that are common to all SAMHSA FOAs. You MUST use both documents in preparing your application. Key Dates: Application Deadline Applications are due by July 18, 2017. Intergovernmental Review (E.O. 12372) Applicants must comply with E.O. 12372 if their state(s) participate(s). Review process recommendations from the State Single Point of Contact (SPOC) are due no later than 60 days after application deadline. Public Health System Impact Statement (PHSIS)/Single State Agency Coordination Applicants must send the PHSIS to appropriate state and local health agencies by the application deadline. Comments from the Single State Agency are due no later than 60 days after the application deadline. Table of Contents EXECUTIVE SUMMARY 3 I. FUNDING OPPORTUNITY DESCRIPTION 5 1. PURPOSE 5 2. EXPECTATIONS 7 II. AWARD INFORMATION 16 III. ELIGIBILITY INFORMATION 18 1. ELIGIBLE APPLICANTS 18 3. EVIDENCE OF EXPERIENCE AND CREDENTIALS 19 IV. APPLICATION AND SUBMISSION INFORMATION 20 1. ADDITIONAL REQUIRED APPLICATION COMPONENTS 20 2. APPLICATION SUBMISSION REQUIREMENTS 22 3. FUNDING LIMITATIONS/RESTRICTIONS 22 4. INTERGOVERNMENTAL REVIEW (E.O. 12372) REQUIREMENTS 23 V. APPLICATION REVIEW INFORMATION 23 1. EVALUATION CRITERIA 23 2. REVIEW AND SELECTION PROCESS 28 VI. ADMINISTRATION INFORMATION 29
Sample 1Sample 2See All (5)
AutoNDA by SimpleDocs
Programmatic Guidance a) Prepare various research reports and dissemination presentations to document the feasibility and acceptability of consuming increased amounts of fortified vegetable oil with corn-soy blend; b)
Sample 1

Related to Programmatic Guidance

  • Schematic Design See Section 2, Part 1, Article 2.1.4, Paragraph 2.1.4.2.

  • Review Protocol A narrative description of how the Claims Review was conducted and what was evaluated.

  • zone Information Publication ICANN’s publication of root-zone contact information for the TLD will include Registry Operator and its administrative and technical contacts. Any request to modify the contact information for the Registry Operator must be made in the format specified from time to time by ICANN at xxxx://xxx.xxxx.xxx/domains/root/.

  • Authoritative Root Database To the extent that ICANN is authorized to set policy with regard to an authoritative root server system (the “Authoritative Root Server System”), ICANN shall use commercially reasonable efforts to (a) ensure that the authoritative root will point to the top-­‐level domain nameservers designated by Registry Operator for the TLD, (b) maintain a stable, secure, and authoritative publicly available database of relevant information about the TLD, in accordance with ICANN publicly available policies and procedures, and (c) coordinate the Authoritative Root Server System so that it is operated and maintained in a stable and secure manner; provided, that ICANN shall not be in breach of this Agreement and ICANN shall have no liability in the event that any third party (including any governmental entity or internet service provider) blocks or restricts access to the TLD in any jurisdiction.

  • TECHNICAL GUIDANCE LETTERS In the sole discretion of the System Agency, and in conformance with federal and state law, the System Agency may issue instructions, clarifications, or interpretations as may be required during work performance in the form of a Technical Guidance Letter (TGL). A TGL must be in writing, and may be delivered by regular mail, electronic mail, or facsimile transmission. Any TGL issued by the System Agency will be incorporated into the Contract by reference for all purposes when it is issued.

  • Root-­‐zone Information Publication ICANN’s publication of root-­‐zone contact information for the TLD will include Registry Operator and its administrative and technical contacts. Any request to modify the contact information for the Registry Operator must be made in the format specified from time to time by ICANN at xxxx://xxx.xxxx.xxx/domains/root/.

  • Loop Testing/Trouble Reporting 2.1.6.1 TeleConex will be responsible for testing and isolating troubles on the Loops. TeleConex 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, TeleConex will be required to provide the results of the TeleConex test which indicate a problem on the BellSouth provided Loop.

  • Construction Change Directives 7.3.1 A Construction Change Directive is written order prepared by the Architect and signed by the Owner and Architect, directing a change in the Work and stating a proposed basis for adjustment, if any, in the Contract Sum, or Contract Time, or both. The Owner may by Construction Change Directive, without invalidating the Contract, order changes in the Work within the general scope of the Contract consisting of additions, deletions or other revisions, the Contract Sum and Contract Time being adjusting accordingly.

  • Switching and Tagging Rules Each Party shall provide the other Parties a copy of its switching and tagging rules that are applicable to the other Parties’ activities. Such switching and tagging rules shall be developed on a non-discriminatory basis. The Parties shall comply with applicable switching and tagging rules, as amended from time to time, in obtaining clearances for work or for switching operations on equipment.

  • Protocol The attached Protocol shall be an integral part of this Agreement.

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