Required Application Components Standard Application Components Sample Clauses

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. Xxxxxx.xxx 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. Xxxxxx.xxx 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 XXXXXX via NIH’s eRA Commons to the Project Director/Principal Investigator (PD/PI), and Signing Official/Business Official (SO/BO). Xxxxxx.xxx 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. Xxxxxx.xxx 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 project is funded, in publications, reports to Congress, or press releases. Xxxxxx.xxx # Standard Application Components Description Source 6 Project Narrative Attachment The Project Narrative describes your project. The application must address how your organization will implement and meet the goals and objectives of the program. You must attach the Project Narrative file (Ado...
Sample 1See All (4)
AutoNDA by SimpleDocs

Related to Required Application Components Standard Application Components

  • Loop Provisioning Involving Integrated Digital Loop Carriers 2.6.1 Where EveryCall has requested an Unbundled Loop and BellSouth uses Integrated Digital Loop Carrier (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 EveryCall. 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 EveryCall (e.g. hairpinning):

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

  • Technical Specifications 1. A procuring entity shall not prepare, adopt or apply any technical specification or prescribe any conformity assessment procedure with the purpose or effect of creating an unnecessary obstacle to trade between the Parties.

  • Quality Control Program The Contractor shall describe the Quality Control Program in a written document which shall be reviewed by the Engineer prior to the start of any production, construction, or off-site fabrication. The written Quality Control Program shall be submitted to the Engineer for review at least ten (10) calendar days before the start of construction. The Quality Control Program shall be organized to address, as a minimum, the following items:

  • 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 licensed under terms and conditions that mandate availability of such source code 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.

  • Purchase Order Flip via Ariba Network (AN) The online process allows suppliers to submit invoices via the AN for catalog and non- catalog goods and services. Contractors have the ability to create an invoice directly from their Inbox in their AN account by simply “flipping” the purchase order into an invoice. This option does not require any special software or technical capabilities. For the purposes of this section, the Contractor warrants and represents that it is authorized and empowered to and hereby grants the State and the third-party provider of MFMP the right and license to use, reproduce, transmit, distribute, and publicly display within the system the information outlined above. In addition, the Contractor warrants and represents that it is authorized and empowered to and hereby grants the State and the third-party provider the right and license to reproduce and display within the system the Contractor’s trademarks, system marks, logos, trade dress, or other branding designation that identifies the products made available by the Contractor under the Contract.

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

  • Computer Equipment Recycling Program If this Contract is for the purchase or lease of computer equipment, then Contractor certifies that it is in compliance with Subchapter Y, Chapter 361 of the Texas Health and Safety Code related to the Computer Equipment Recycling Program and the Texas Commission on Environmental Quality rules in 30 TAC Chapter 328.

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