Required Application Components Standard Application Components Clause Samples

Required Application Components Standard Application Components. Applications must include the following required application components listed in the table below. This table consists of a full list of standard application components, a description of each required component, and its source for application submission. # Standard Application Components Description Source 1 SF-424 (Application for Federal Assistance) Form This form must be completed by applicants for all SAMHSA grants and cooperative agreements. ▇▇▇▇▇▇.▇▇▇ 2 SF-424 A (Budget Information – Non- Construction Programs) Form Use SF-424A. Fill out Sections A, B, D and E of the SF-424A. Section C should only be completed if applicable. It is highly recommended that you use the sample budget format in the FOA. ▇▇▇▇▇▇.▇▇▇ 3 HHS Checklist Form The HHS Checklist ensures that you have obtained the proper signatures, assurances, and certifications. You are not required to complete the entire form, but please include the top portion of the form (“Type of Application”) indicating if this is a new, noncompeting continuation, competing continuation, or supplemental application; the Business Official and Program Director/Project Director/Principal Investigator contact information (Part C); and your organization’s nonprofit status (Part D, if applicable). All SAMHSA Notices of Award (NoAs) will be emailed by ▇▇▇▇▇▇ via NIH’s eRA Commons to the Project Director/Principal Investigator (PD/PI), and Signing Official/Business Official (SO/BO). ▇▇▇▇▇▇.▇▇▇ 4 Project/Performance Site Location(s) Form The purpose of this form is to collect location information on the site(s) where work funded under this grant announcement will be performed. ▇▇▇▇▇▇.▇▇▇ 5 Project Abstract Summary Your total abstract must not be longer than 35 lines. It should include the project name, population(s) to be served (demographics and clinical characteristics), strategies/interventions, project goals and measurable objectives, including the number of people to be served annually and throughout the lifetime of the project, etc. In the first five lines or less of your abstract, write a summary of your project that can be used, if your ▇▇▇▇▇▇.▇▇▇ # Standard Application Components Description Source project is funded, in publications, reports to Congress, or press releases.
View SourceView Similar (2)

Related to Required Application Components Standard Application Components

  • Loop Provisioning Involving Integrated Digital Loop Carriers 2.6.1 Where Freedom has requested an Unbundled Loop and BellSouth uses IDLC systems to provide the local service to the End User and BellSouth has a suitable alternate facility available, BellSouth will make such alternative facilities available to Freedom. If a suitable alternative facility is not available, then to the extent it is technically feasible, BellSouth will implement one of the following alternative arrangements for Freedom (e.g. hairpinning): 1. Roll the circuit(s) from the IDLC to any spare copper that exists to the customer premises. 2. Roll the circuit(s) from the IDLC to an existing DLC that is not integrated. 3. If capacity exists, provide "side-door" porting through the switch. 4. If capacity exists, provide "Digital Access Cross Connect System (DACS)- door" porting (if the IDLC routes through a DACS prior to integration into the switch). 2.6.2 Arrangements 3 and 4 above require the use of a designed circuit. Therefore, non- designed Loops such as the SL1 voice grade and UCL-ND may not be ordered in these cases. 2.6.3 If no alternate facility is available, and upon request from Freedom, and if agreed to by both Parties, BellSouth may utilize its Special Construction (SC) process to determine the additional costs required to provision facilities. Freedom will then have the option of paying the one-time SC rates to place the Loop.

  • MSAA Indicator Technical Specification Document This Agreement shall be interpreted with reference to the MSAA Indicator Technical Specifications document.

  • ODUF Packing Specifications 6.3.1 A pack will contain a minimum of one message record or a maximum of 99,999 message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of 99 packs and a minimum of one pack.

  • Technical Specifications The purpose of the Technical Specifications (TS), is to define the technical characteristics of the Goods and Related Services required by the Procuring Entity. The Procuring Entity shall prepare the detailed TS consider that:

  • Technical Specifications and Drawings a) The Goods and Related Services supplied under this Contract shall conform to the technical specifications and standards mentioned in Section VI, Schedule of Requirements and, when no applicable standard is mentioned, the standard shall be equivalent or superior to the official standards whose application is appropriate to the Goods' country of origin. b) The Supplier shall be entitled to disclaim responsibility for any design, data, drawing, specification or other document, or any modification thereof provided or designed by or on behalf of the Procuring Entity, by giving a notice of such disclaimer to the Procuring Entity. c) Wherever references are made in the Contract to codes and standards in accordance with which it shall be executed, the edition or the revised version of such codes and standards shall be those specified in the Schedule of Requirements. During Contract execution, any changes in any such codes and standards shall be applied only after approval by the Procuring Entity and shall be treated in accordance with GCC Clause 33.