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
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)

Related to Programmatic Guidance

  • COVID-19 Protocols Contractor will abide by all applicable COVID-19 protocols set forth in the District’s Reopening and COVID-19 Mitigation Plan and the safety guidelines for COVID-19 prevention established by the California Department of Public Health and the Ventura County Department of Public Health.

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

  • Demographic, Classification and Wage Information XXXXXX agrees to coordinate the accumulation and distribution of demographic, classification and wage data, as specified in the Letter of Understanding dated December 14, 2011, to CUPE on behalf of Boards of Education. The data currently housed in the Employment Data and Analysis Systems (EDAS) will be the source of the requested information.

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

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

  • Training Designation Type Code Select and insert the appropriate training credit designation type code: Code Short Description Long Description (If Applicable) 01 Undergraduate Credit N/A 02 Graduate Credit N/A 03 Continuing Education Unit N/A 04 Post Graduate Credit N/A 05 N/A N/A

  • How to File an Appeal of a Prescription Drug Denial For denials of a prescription drug claim based on our determination that the service was not medically necessary or appropriate, or that the service was experimental or investigational, you may request an appeal without first submitting a request for reconsideration. You or your physician may file a written or verbal prescription drug appeal with our pharmacy benefits manager (PBM). The prescription drug appeal must be submitted to us within one hundred and eighty (180) calendar days of the initial determination letter. You will receive written notification of our determination within thirty (30) calendar days from the receipt of your appeal. How to File an Expedited Appeal Your appeal may require immediate action if a delay in treatment could seriously jeopardize your health or your ability to regain maximum function, or would cause you severe pain. To request an expedited appeal of a denial related to services that have not yet been rendered (a preauthorization review) or for on-going services (a concurrent review), you or your healthcare provider should call: • our Grievance and Appeals Unit; or • our pharmacy benefits manager for a prescription drug appeal. Please see Section 9 for contact information. You will be notified of our decision no later than seventy-two (72) hours after our receipt of the request. You may not request an expedited review of covered healthcare services already received.

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

  • Accessibility of Web-Based Information and Applications For State Agency Authorized User Acquisitions: Any web-based information and applications development, or programming delivered pursuant to the contract or procurement, will comply with New York State Enterprise IT Policy NYS-P08-005, Accessibility of Web-Based Information and Applications as follows: Any web-based information and applications development, or programming delivered pursuant to the contract or procurement, will comply with New York State Enterprise IT Policy NYS-P08- 005, Accessibility of Web-Based Information and Applications as such policy may be amended, modified or superseded, which requires that state agency web-based information and applications are accessible to persons with disabilities. Web-based information and applications must conform to New York State Enterprise IT Policy NYS-P08-005 as determined by quality assurance testing. Such quality assurance testing will be conducted by the State Agency Authorized User and the results of such testing must be satisfactory to the Authorized User before web-based information and applications will be considered a qualified deliverable under the contract or procurement.

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