Required Application Components Sample Clauses

Required Application Components. After downloading and retrieving the required application components and completing the registration processes, it is time to write and complete your application. All files uploaded with the Xxxxxx.xxx application MUST be in Adobe PDF file format. Directions for creating PDF files can be found on the Xxxxxx.xxx website. See Appendix B for all application formatting and validation requirements. 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 where you can find each document. # Standard Application Components Description Where to Find Document 1 SF-424 (Application for Federal Assistance) Form This form must be completed by applicants for all SAMHSA grants. The names and contact information for Project Director (PD) and Business Official (BO) are required for SAMHSA applications, and are to be entered on the SF-424 form. The PD must have an eRA Commons account: the PD’s Commons Username must be entered in field 4. Applicant Identifier and the PD’s name, phone number and email address must be entered in Section 8. APPLICANT INFORMATION: item f. Name and contact information of person to be contacted on matters involving this application. The BO name, title, email address and phone number must be entered in the Authorized Representative section fields on page four of the SF 424. The organization mailing address is required in section 8. APPLICANT INFORMATION item d. Address. All SAMHSA Notices of Award (NoAs) will be emailed by XXXXXX via NIH’s eRA Commons to the Project Director/Principal Investigator (PD/PI), and the Signing Official/Business Official (SO/BO). Xxxxxx.xxx/xxxxx 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 budget template. Xxxxxx.xxx/xxxxx 3 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. Xxxxxx.xxx/xxxxx 4 Project Abstract Summary It is recommended the abstract is no more than one page. It should include the project name, population(s) to be served (demographics and clinical characteristics), strategies/interventions, project goals and measurab...
AutoNDA by SimpleDocs
Required Application Components. SF-424 – Fill out all Sections of the SF-424. In Line #4 (i.e., Applicant Identified), input the Commons Username of the PD/PI. In Line #17 input the following information: (Proposed Project Date: a. Start Date: 9/30/2021; b. End Date: 9/29/2026).
Required Application Components. Applications must include the required ten application components (Face Page, Abstract, Table of Contents, Budget Form, Project Narrative and Supporting Documentation, Appendices, Assurances, Certifications, Disclosure of Lobbying Activities, and Checklist).  Face Page – SF 424 v2 is the face page. This form is part of the PHS 5161-1. [Note: Applicants must provide a Dun and Bradstreet (DUNS) number to apply for a grant or cooperative agreement from the Federal Government. SAMHSA applicants are required to provide their DUNS number on the face page of the application. Obtaining a DUNS number is easy and there is no charge. To obtain a DUNS number, access the Dun and Bradstreet Web site at xxx.xxxxxxxxxxxxxxxx.xxx or call 0-000-000-0000. To expedite the process, let Xxx and Bradstreet know that you are a public/private nonprofit organization getting ready to submit a Federal grant application.]  Abstract – Your total abstract should not be longer than 35 lines. It should include the project name, population 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 project is funded, in publications, reporting to Congress, or press releases.  Table of Contents – Include page numbers for each of the major sections of your application and for each appendix.  Budget Form – Use SF 424A, which is part of the PHS 5161-1. Fill out Sections B, C, and E of the SF 424A. A sample budget and justification is included in Appendix F of this document.
Required Application Components. SF-424 – Fill out all Sections of the SF-424. In Line #4 (i.e., Applicant Identified), input the Commons Username of the PD/PI. In Line #17 input the following information: (Proposed Project Date: a. Start Date: 08/31/2021; b. End Date: 08/30/2025). Budget Informatio8n Form – Use SF-424A. Fill out all Sections of the SF- 424A. o Section ABudget Summary: Use the first row only (Line 1) to report the total federal funds (e) requested for the first year of your project only. Use the second row only (Line 2) to report the total non-federal funds (f) for the first year of your project only.
Required Application Components. REQUIRED SUPPORTING DOCUMENTATION Section E: Biographical Sketches and Job Descriptions See PART II: Appendix D, Biographical Sketches and Job Descriptions, for instructions on completing this section. Section F: Confidentiality and SAMHSA Participant Protection/Human Subjects You must describe procedures relating to Confidentiality, Participant Protection, and the Protection of Human Subjects Regulations in Section F of your application. Failure to include these procedures will impact the review of your application. See Appendix A of this document for guidelines on these requirements.

Related to Required Application Components

  • EODUF Packing Specifications 7.3.1 The data will be packed using ATIS EMI records. A pack will contain a minimum of one (1) message record or a maximum of ninety-nine thousand nine hundred and ninety-nine (99,999) message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of ninety-nine (99) packs and a minimum of one (1) pack.

  • Loop Provisioning Involving Integrated Digital Loop Carriers 2.6.1 Where InterGlobe 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 InterGlobe. 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 InterGlobe (e.g. hairpinning):

  • ODUF Packing Specifications 6.3.1 The data will be packed using ATIS EMI records. A pack will contain a minimum of one (1) message record or a maximum of ninety-nine thousand nine hundred and ninety-nine (99,999) message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of ninety-nine (99) packs and a minimum of one (1) pack.

  • Program Components Activities and services delivered under this Program Element align with Foundational Programs and Foundational Capabilities, as defined in Oregon’s Public Health Modernization Manual, (xxxx://xxx.xxxxxx.xxx/oha/PH/ABOUT/TASKFORCE/Documents/public_health_modernization_man ual.pdf) as well as with public health accountability outcome and process metrics (if applicable) as follows:

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

  • Shipping must be Freight On Board Destination to the delivery location designated on the Customer purchase order The Contractor will retain title and control of all goods until delivery is completed and the Customer has accepted the delivery. All risk of transportation and all related charges are the responsibility of the Contractor. The Customer will notify the Contractor and H-GAC promptly of any damaged goods and will assist the Contractor in arranging for inspection. The Contractor must file all claims for visible or concealed damage. Unless otherwise stated in the Agreement, deliveries must consist only of new and unused merchandise.

  • Loop Provisioning Involving IDLC 2.16.1 Where TWTC has requested an Unbundled Loop and AT&T uses IDLC systems to provide the local service to the customer and AT&T has a suitable alternate facility available, AT&T will make such alternative facilities available to TWTC. If a suitable alternative facility is not available, then to the extent it is technically feasible, AT&T will implement one of the following alternative arrangements for TWTC (e.g., hairpinning):

  • Escrow Format Specification 3.1. Deposit’s Format. Registry objects, such as domains, contacts, name servers, registrars, etc. will be compiled into a file constructed as described in draft-xxxxx-xxxxxxx-registry-data-escrow, see Part A, Section 9, reference 1 of this Specification and draft-xxxxx-xxxxxxx-dnrd-objects-mapping, see Part A, Section 9, reference 2 of this Specification (collectively, the “DNDE Specification”). The DNDE Specification describes some elements as optional; Registry Operator will include those elements in the Deposits if they are available. If not already an RFC, Registry Operator will use the most recent draft version of the DNDE Specification available at the Effective Date. Registry Operator may at its election use newer versions of the DNDE Specification after the Effective Date. Once the DNDE Specification is published as an RFC, Registry Operator will implement that version of the DNDE Specification, no later than one hundred eighty (180) calendar days after. UTF-8 character encoding will be used.

  • OPEN SOURCE COMPONENTS The DS Offerings may include open source components. Whenever notices (such as acknowledgment, copies of licenses or attribution notice) are required by the original licensor, such notices are included in the Documentation of the DS Offerings. Moreover, some open source components may not be distributed and licensed under the terms of the Agreement but under the terms of their original licenses as set forth in the Documentation of the DS Offerings themselves. Source code for open source software components is available upon request. Except for components mentioned in the section EXCLUSIONS below, the warranty and indemnification provided by DS under the Agreement apply to all open source software components and shall be provided by DS and not by the original licensor, but only for the use of the DS Offerings that is in compliance with the terms of the Agreement, and in conjunction with the DS Offerings. The original licensors of said open source software components provide them on an “as is” basis and without any liability whatsoever to Customer.

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

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!