AFRL BAA Guide for Industry and Proposal Preparation Instructions for the Information Directorate, AFRL, Rome NY

Other / Unclassified

This document is a placeholder or introductory page for a PDF portfolio. It advises users to open the document in Adobe Acrobat X or Adobe Reader X, or a later version, for the best experience. It also provides a button to download Adobe Reader.

This document does not contain substantive information related to a SAM.gov opportunity. It is a technical instruction for viewing the document itself and does not provide details on requirements, scope, or submission instructions for any potential solicitation.

Other / Unclassified

This document is the "Broad Agency Announcement (BAA) Guide for Industry," Version 2.2, dated January 2025. It provides comprehensive guidance on the BAA process for research and development (R&D) efforts, including definitions, processes, proposal preparation, and award administration.

This guide is crucial for potential bidders responding to Broad Agency Announcements (BAAs). It details:

• BAA Purpose and Criteria: Explains when BAAs are used, emphasizing the solicitation of new and creative solutions for R&D efforts that advance the state-of-the-art rather than focusing on specific systems.
• Definitions: Clarifies key terms such as "Assistance Instrument," "Broad Agency Announcement (BAA)," "Governmentwide Point of Entry (GPE)," and various agreement types (Grants, Cooperative Agreements, Other Transactions, Technology Investment Agreements).
• BAA Process Variations: Describes different BAA approaches like One-Step, Two-Step, Open, Closed, and BAAs with Calls, helping bidders understand submission procedures.
• Proposal Preparation: Outlines requirements for white papers and full proposals, including technical and cost aspects, and emphasizes that proposals must stand on their own merit.
• Review and Award Process: Explains the peer or scientific review process, proposal categorization (Selectable/Not Selectable), and the flexibility in award decisions.
• Assistance Instruments: Differentiates between contracts and various assistance instruments (Grants, CAs, OTs, TIAs), detailing their characteristics and when each might be used.

Understanding this guide is essential for preparing compliant and competitive proposals under BAAs.

Form / Attachment / Pricing Sheet

This document provides guidance on ensuring an adequate accounting system is in place for companies interested in pursuing cost-reimbursement type contracts under AFRL/RI BAAs. It outlines the necessity of having an accounting system compliant with Generally Accepted Accounting Principles (GAAP), Generally Accepted Government Auditing Standards (GAGAS), the Federal Acquisition Regulation (FAR), and Cost Accounting Standards (CAS).

• DCAA Review: Companies without a prior Defense Contract Audit Agency (DCAA) review are required to have one performed to confirm system adequacy.
• DCAA Resources: Guidance and checklists, including the "Pre-award Accounting System Adequacy Checklist," are available on the DCAA website (dcaa.mil).
• SF Form 1408: Offerors without a DCAA-approved system must complete and submit SF Form 1408 (Pre-Award Survey of Prospective Contractor - Accounting System) with their proposal. Failure to do so may result in the proposal being deemed non-conforming.
• Form Completion: Bidders should complete Section II (checklist) and provide a narrative explanation in Section I of SF 1408 to demonstrate an appropriate accounting system.
• Cost Accounting Standards (CAS): Contracts exceeding $2M may be subject to CAS requirements (FAR 52.230-2). Offerors must submit representations and a Disclosure Statement if their proposal will result in a CAS-compliant contract.
• Audit Costs: The cost of audit activities is not an allowable direct charge to the contract.

Potential bidders for cost-reimbursement contracts under AFRL/RI BAAs must ensure their accounting system meets specified standards. This document mandates the completion and submission of SF Form 1408 for those without a DCAA-approved system, which is critical for proposal compliance. It also highlights potential Cost Accounting Standards (CAS) applicability for contracts over $2M.

Statement of Work (SOW) / Performance Work Statement (PWS)

This document outlines the objective for a procurement effort, which is to develop novel software systems that enable rapid and efficient adaptation to changing requirements and computational environments. The goal is to create software that is efficient at run-time across various operating conditions.

The scope involves researching, designing, developing, demonstrating, testing, integrating, and delivering a specific software system (e.g., SymLang). This system aims to facilitate rapid software adaptation to changes in requirements, platforms, and computational resources, addressing the U.S. Government's need for more agile and cost-effective software solutions.

This section is the legally binding part of the SOW and defines the work to be accomplished. It should be based on the contractor's proposed SOW and proposal. Requirements may include:

• Design, development, testing, and evaluation of specific systems or components.
• Management requirements (project status, reviews, meetings).
• Hardware and software requirements (delivery, documentation, COTS, licensing).
• Testing and demonstration requirements (plans, execution, reporting).
• Documentation requirements (reports, final technical reports).

Provides context for the effort, explaining why it is needed. It highlights the Department of Defense's dependency on software, the challenges posed by increasing complexity, and the high cost of software engineering and maintenance. It may also reference applicable and supporting documents.

This document is a template and requires specific details to be inserted, such as the title of the effort, contract number, and dates. The "Technical Requirements" section (4.0) is the only legally binding part. Requirements not listed in section 4.0 are not binding.