Multi-Domain Aerial Warfighting Network Capabilities
Added: Sep 19, 2017 10:13 am BAA NUMBER: FA8750-17-S-7008PART I - OVERVIEW INFORMATIONThis announcement is for an Open, 2 Step BAA which is open and effective until 30 Sep 2022. Only white papers are due at this time. While white papers will be considered if received prior to 1500 on 30 Sep 2022, the following submission dates are suggested to best align with projected funding:FY18 by 31 Oct 2017FY19 by 03 Aug 2018FY20 by 02 Aug 2019FY21 by 31 Jul 2020FY22 by 30 Jul 2021Offerors should monitor the Federal Business Opportunities website at http://www.fbo.gov in the event this announcement is amended.CONCISE SUMMARY OF FUNDING OPPORTUNITY: Conduct research to develop and demonstrate innovative and affordable technologies that provide agile and secure information transmission, network and dissemination capabilities to aerial platforms that enable the sharing of quality information within resource and policy constraints. The intent is to expand the Global Information grid (GIG) to connect tee major domains of warfare: Air, Space, and Terrestrial. The goal is to deliver timely, reliable, and actionable information to warfighters and weapon systems across the United States Air Force enterprise to support Command and Control, Intelligence, Surveillance and Reconnaissance.BAA ESTIMATED FUNDING: Total funding for this BAA is approximately $24.9M. Individual awards will not normally exceed 36 months with dollar amounts normally ranging from $250K to $10M. There is also the potential to make awards up to any dollar value.ANTICIPATED INDIVIDUAL AWARDS: Multiple Awards are anticipatedTYPE OF INSTRUMENTS THAT MAY BE AWARDED: Procurement contract, grant, cooperative agreement or other transactions.AGENCY CONTACT INFORMATION: All white paper and proposal submissions and any questions of a technical nature shall be directed to the cognizant Technical Point of Contact (TPOC) as specified below (unless otherwise specified in the technical area):TPOC Name: Howard M. BeyerMailing Address: AFRL/RITE 525 Brooks Road Rome NY 13441-4505Telephone: (315) 330-4718Email: Howard.Beyer.1@us.af.milQuestions of a contractual/business nature shall be directed to the cognizant contracting officer, as specified below (email requests are preferred):Contracting Officer: Gail MarshTelephone: (315) 330-7518Email: Gail.Marsh@us.af.milEmails must reference the solicitation (BAA) number and title of the acquisition.Communication between Prospective Offerors and Government Representatives: Dialogue between prospective offerors and Government representatives is encouraged. Technical and contracting questions can be resolved in writing or tough open discussions. Discussions with any of the points of contact shall not constitute a commitment by the Government to subsequently fund or award any proposed effort. Only Contracting Officers are legally authorized to commit the Government.Proposers are cautioned that evaluation ratings may be lowered and/or proposal rejected if proposal preparation (Proposal format, content, etc.) and/or submittal instructions are not followed. PART II - FULL TEXT ANNOUNCEMENTBROAD AGENCY ANNOUNCEMNTE (BAA) TITLE: Multi-Domain Aerial Warfighting Network CapabilitiesBAA NUMBER: FA8750-17-S-7008CATALOG OF FEDERAL DOMESTIC ASSERTION (CFDA) Number: 12.800 and 12.910I. FUNDING OPPORTUNITY DESCRIPTION:The Air Force Research Laboratory - Information Directorate (AFRL/RI) is soliciting white papers under this BAA for research, design, development, integration, test, evaluation and experimentation of innovative technologies and techniques for Multi-Domain Aerial Warfighting Network Capabilities.The BAA objective is to conceive, develop and demonstrate innovative and affordable technologies that provide agile and secure information transmission, network and dissemination capabilities to aerial platforms that enable the sharing of quality information within resource and policy constraints. The intent is to expand the Global Information grid (GIG) to connect tee major domains of warfare: Air, Space, and Terrestrial. The goal is to deliver timely, reliable, and actionable information to warfighters and weapon systems across the United States Air Force enterprise to support Command and Control, Intelligence, Surveillance and Reconnaissance.Efforts under this BAA are expected to enable the Air Force to provide a transportable network, flexible enough to communicate with any air, space, or ground asset in the area. The network will provide a beyond line-of-sight (BLOS) communications infrastructure that can be packed up and moved in and out of the designated battlespace, enabling the military to have a reliable and secure communications network that extends globally. The network is designed to be flexible enough to provide the right communication and network packages for a specific region, mission, or technology.White papers may describe but are not limited to • Hardware brass-boards and/or software systems development. • Activities for validation with model-based design and simulation. • Demonstration of hardware brass-boards and antenna in-the-loop validation techniques.Research efforts under this BAA are expected to result in functional capabilities, concepts, theory and applications addressing Air Force aerial network connectivity problems. The effectiveness of the developed technologies for potential operational use will be assessed tough testing and evaluation activities. Technologies that can be transitioned for operational use are of high interest. Offerors are encouraged to describe the pre-conditions that are necessary for the proposed techniques to work effectively.Work is encouraged in, but not limited to, these focus areas:1. Agile Aerial Network Architecture • Develop multi-domain network architectures that support self-organizing, self-healing autonomous machine-to-machine data routing and dissemination. • Develop self-aware/sentient cross-Open Systems Interconnection (OSI) layer network communications paradigms that support cooperative learning and reconfiguration-on-the-fly of mobile networks, by sensing and adapting to operational environment and mission requirements. • Demonstrate cooperative wireless network communications that allow nodes in a wireless network to share resources and to cooperatively transmit, providing reliable, robust connectivity via multipath routing.2. Information Transport Performance Management • Develop the communications management capabilities to support the management of Intelligence, Surveillance, and Reconnaissance (ISR) related network and information system and communications resources. • Develop information management algorithms capable of dynamically requesting data from multiple ISR sensors in order to enhance current capabilities for detecting, locating, identifying, and tracking ground moving targets. • Develop the mechanisms to enable mission-based priority schemes and assured information delivery techniques supporting the exchange of ISR traffic, as well as other network traffic. Develop metrics such as Kill Chain Reduction, Bandwidth Efficiency, or Network Availability to gauge performance and effects.3. Integration and Interoperability with the Global Information Grid (GIG) • Integrate new communications resources available on the ISR platform(s) to enable increased communications capability. • Study potential ISR collection planning and envisioned dynamic tasking techniques being developed for current and future Air Operations Centers (AOCs). Develop the information management algorithms to ensure they will operate within the constraints of these envisioned collection management techniques. • In conjunction with the Government, work with the operational community to address Concepts of Operation (CONOPS) issues associated with ISR platform interoperability. • Conduct airborne flight experiments utilizing multiple ISR assets aimed at demonstrating capabilities for increasing multi-platform interoperability and tracking performance.4. Multi-Domain Aerial Networking • Develop methods for cross tactical data network (TDN) and tactical data link (TDL) message passing at the tactical edge. • Develop methods for passing metadata (QoS, timing requirements, etc.) between TDNs and TDLs. • Conduct or survey modelling and simulation to quantify improvements in appropriate mission metrics as a result of advances in multi-domain tactical edge data sharing. • Conduct airborne experiments demonstrating live, in-flight multi-domain data sharing between tactical assets.II. AWARD INFORMATION:1. FUNDING: Total funding for this BAA is approximately $24.9M. The anticipated funding to be obligated under this BAA is broken out by fiscal year as follows:FY18 - $3.8MFY19 - $5.4MFY20 - $5.4MFY21 - $4.4MFY22 - $5.9MThe breakout of funding by fiscal year is a projection. The total awards values in any given year will vary. a. Individual awards will not normally exceed 36 months with dollar values ranging from $250K to $10M. There is also the potential to make awards up to any dollar value as long as the value does not exceed the available BAA ceiling amount. b. The Government reserves the right to select all, part, or none of the proposals received, subject to the availability of funds. All potential Offerors should be aware that due to unanticipated budget fluctuations, funding in any or all areas may change with little or no notice.2. FORM. Awards of efforts as a result of this announcement will be in the form of contracts, grants, cooperative agreements or other transactions depending upon the nature of the work proposed.3. BAA TYPE: This is a two-step open broad agency announcement. This announcement constitutes the only solicitation.As STEP ONE - The Government is only soliciting white papers at this time. DO NOT SUBMIT A FORMAL PROPOSAL. Those white papers found to be consistent with the intent of this BAA may be invited to submit a technical and cost proposal. See Section VI of this announcement for further details regarding the proposal.III. ELIGIBILITY INFORMATION:1. ELIGIBILITY: All qualified offerors who meet the requirements of this BAA may apply.2. FOREIGN PARTICIPATION/ACCESS: a. This BAA is closed to foreign participation at the Prime Contractor Level. b. Foreign Ownership, Control or Influence (FOCI) companies who have mitigated FOCI may inquire as to eligibility by contacting the contracting office focal point, Gail E. Marsh, Contracting Officer, telephone (315) 330-7518 or e-mail Gail.Marsh@us.af.mil for verification prior to submitting a white paper. Please reference BAA FA8750-17-S-7008. c. Contractor employees requiring access to USAF bases, AFRL facilities, and/or access to U.S. Government Information Technology (IT) networks in connection with the work on contracts, assistance instruments or other transactions awarded under this BAA must be U.S. citizens. For the purpose of base and network access, possession of a permanent resident card ("Green Card") does not equate to U.S. citizenship. This requirement does not apply to foreign nationals approved by the U.S. Department of Defense or U.S. State Department under international personnel exchange agreements with foreign governments. Any waivers to this requirement must be granted in writing by the Contracting Officer prior to providing access. The above requirements are in addition to any other contract requirements related to obtaining a Common Access Card (CAC). If an IT network/system does not require AFRL to endorse a contractor's application to said network/system in order to gain access, the organization operating the IT network/system is responsible for controlling access to its system. If an IT network/system requires a U.S. Government sponsor to endorse the application in order for access to the IT network/system, AFRL will only endorse the following types of applications, consistent with the requirements above: 1. Contractor employees who are U.S. citizens performing work under contracts, assistance instruments or other transactions awarded under this BAA. 2. Contractor employees who are non-U.S. citizens and who have been granted a waiver.Any additional access restrictions established by the IT network/system owner apply.3. FEDERALLY FUNDED RESEARCH AND DEVELOPMENT CENTERS AND GOVERNMENT ENTITIES: Federally Funded Research and Development Centers (FFRDCs) and Government entities (e.g., Government/National laboratories, military educational institutions, etc.) are subject to applicable direct competition limitations and cannot propose to this BAA in any capacity unless they meet the following conditions:a. FFRDCs: FFRDCs must clearly demonstrate that the proposed work is not otherwise available from the private sector; and FFRDCs must provide a letter on official letterhead from their sponsoring organization citing the specific authority establishing their eligibility to propose to Government solicitations and compete with industry, and their compliance with the associated FFRDC sponsor agreement's terms and conditions. This information is required for FFRDCs proposing to be prime contractors or sub-awardees.b. Government Entities: Government entities must clearly demonstrate that the work is not otherwise available from the private sector and provide written documentation citing the specific statutory authority and contractual authority, if relevant, establishing their ability to propose to Government solicitations. While 10 U.S.C.§ 2539b may be the appropriate statutory starting point for some entities, specific supporting regulatory guidance, together with evidence of agency approval, will still be required to fully establish eligibility.FFRDC and Government entity eligibility will be determined on a case-by-case basis; however, the burden to prove eligibility for all team members rests solely with the proposer.IV. APPLICATION AND SUBMISSION INFORMATION:All responses to this announcement must be addressed to the Technical Point of Contact (TPOC) listed in SECTION VII. DO NOT send white papers to the Contracting Officer. 1. SUBMISSION DATES AND TIMES:It is recommended that white papers be received by 3:00 PM Eastern Standard Time (EST) on the following dates to maximize the possibility of award:FY18 by 31 Oct 2017FY19 by 03 Aug 2018FY20 by 02 Aug 2019FY21 by 31 Jul 2020FY22 by 30 Jul 2021White papers will be accepted until 3 PM EST on 30 September 2022, but it is less likely that funding will be available in each respective fiscal year after the dates cited. This BAA will close on 30 September 2022.All offerors submitting white papers will receive notification of their evaluation results within 45 days of submission. Offerors should email the TPOC and the Contracting Officer listed in Section VII, for status of their white paper(s) after 45 days, if no such correspondence has been received.2. CONTENT AND FORMAT: Offerors are required to submit 2 copies of a 3 to 5 page white paper summarizing their proposed approach/solution. The purpose of the white paper is to preclude unwarranted effort on the part of an offeror whose proposed work is not of interest to the Government.The white paper will be formatted as follows: a. Section A: Title, Period of Performance, Estimated Cost, Name/Address of Company, Technical and Contracting Points of Contact (phone and email) (this section is NOT included in the page count); b. Section B: Task Objective; and c. Section C: Technical Summary and Proposed Deliverables.All white papers shall be double spaced with a font no smaller than 12 point. In addition, respondents are requested to provide their Commercial and Government Entity (CAGE) Code, their unique entity identifier and electronic funds transfer (EFT) indicator (if applicable), an e-mail address and reference BAA FA8750-17-S-7008 with their submission.Multiple white papers within the purview of this announcement may be submitted by each offeror. If the offeror wishes to restrict its white papers, they must be marked with the restrictive language stated in FAR 15.609(a) and (b).3. HANDLING AND MAILING INSTRUCTIONS: a. CLASSIFICATION GUIDANCE. All Proposers should review the NATIONAL INDUSTRIAL SECURITY PROGRAM OPERATING MANUAL, (NISPOM), dated February 28, 2006 and incorporating Change 2, dated May 18, 2016, as it provides baseline standards for the protection of classified information and prescribes the requirements concerning Contractor Developed Information under paragraph 4-105. Defense Security Service (DSS) Site for the NISPOM is: http://www.dss.mil/.In the event of a possible or actual compromise of classified information in the submission of your white paper or proposal, immediately but no later than 24 hours, bring this to the attention of your cognizant security authority and AFRL Rome Research Site Information Protection Office (IPO):Information Protection Office (contact only if a security compromise has occurred)315-330-4048 0730-1630 Monday-Friday315-330-2961 Evenings and WeekendsEmail: vincent.guza@us.af.mil. b. CLASSIFIED SUBMISSIONS. AFRL/RITE will accept classified responses to this BAA when the classification is mandated by classification guidance provided by an Original Classification Authority of the U.S. Government, or when the offeror believes the work, if successful, would merit classification. Security classification guidance in the form of a DD Form 254 (DoD Contract Security Classification Specification) will not be provided at this time since AFRL is soliciting ideas only. Offerors that intend to include classified information or data in their white paper submission or who are unsure about the appropriate classification of their white papers should contact the technical point of contact listed in Section VII for guidance and direction in advance of preparation. c. MAILING INSTRUCTIONS. You may submit your white papers/proposals one of two ways: 1. HARDCOPY SUBMISSIONS. Any mailed responses, unclassified/classified, to this announcement must be sent U.S. Postal Service, registered mail or similar service and addressed to AFRL/RITE, 525 Brooks Road, Rome NY 13441-4505, and reference BAA FA8750-17-S-7008. When mailing follow the directions regarding the number of copies required. 2. SOFTCOPY SUBMISSIONS. Unclassified electronic submission may be submitted to Howard.Beyer.1@us.af.mil. Encrypt or password-protect all proprietary information prior to sending. Offerors are responsible to confirm receipt with the TPOC listed in Section VII. AFRL is not responsible for undelivered documents.Questions can be directed to the TPOC listed in Section VII.4. OTHER SUBMISSION REQUIREMENTS/CONSIDERATIONS: a. COST SHARING OR MATCHING: Cost sharing is not a requirement. Cost sharing may be proposed and will be considered on a case-by-case basis. b. SYSTEM FOR AWARD MANAGEMENT (SAM). Offerors must be registered in the SAM database to receive a contract award, and remain registered during performance and tough final payment of any contract or agreement. Processing time for registration in SAM, which normally takes forty-eight hours, should be taken into consideration when registering. Offerors who are not already registered should consider applying for registration before submitting a proposal. The provision at FAR 52.204-7, System for Award Management (Oct 2016) applies. c. EXECUTIVE COMPENSATION AND FIRST-TIER SUBCONTRACT/ SUBRECIPIENT AWARDS: Any contract award resulting from this announcement may contain the clause at FAR 52.204-10 - Reporting Executive Compensation and First-Tier Subcontract Awards (Oct 2016). Any grant or agreement award resulting from this announcement may contain the award term set forth in 2 CFR, Appendix A to Part 25 which can be viewed at: http://www.ecfr.gov/cgi-bin/text-idx?SID=8fb6c83606df57968c3e7e145e7d683c&mc=true&node=ap2.1.25_1360.a&rgn=div9 d. ALLOWABLE CHARGES: The cost of preparing white papers/proposals in response to this announcement is not considered an allowable direct charge to any resulting contract or any other contract, but may be an allowable expense to the normal bid and proposal indirect cost specified in FAR 31.205-18. Incurring pre-award costs for ASSISTANCE INSTRUMENTS ONLY are regulated by the DoD Grant and Agreements Regulations (DODGARS). e. GOVERNMENT APPROVED ACCOUNTING SYSTEM: An offeror must have a government approved accounting system prior to award of a cost-reimbursement contract per limitations set forth in FAR 16.301-3(a) to ensure the system is adequate for determining costs applicable to the contract. The acceptability of an accounting system is determined based upon an audit performed by the Defense Contract Audit Agency (DCAA). IMPORTANT: If you do not have a DCAA approved accounting system access the following link for instructions: https://www.fbo.gov/index?s=opportunity&mode=form&id=1cffad228f48b58057072a6c9113799d&tab=core&_cview=1 f. HUMAN USE: All research involving human subjects, to include the use of human biological specimens and human data, selected for funding must comply with Federal regulations for human subject protection. Further, research involving human subjects that is conducted or supported by the DoD must comply with 32 CFR 219, "Protection of Human Subjects" found at: http://www.access.gpo.gov/nara/cfr/waisidx_07/32cfr219_07.html, and DoD Directive 3216.02, "Protection of Human Subjects and Adherence to Ethical Standards in DoD-Supported Research" found at: http://www.dtic.mil/whs/directives/corres/pdf/321602p.pdf. 1. Institutions awarded funding for research involving human subjects must provide documentation of a current Assurance of Compliance with Federal regulations for human subject protection, for example a Department of Health and Human Services, Office of Human Research Protection Federal Wide Assurance found at: http://www.hhs.gov/op. 2. All institutions engaged in human subject research, to include subcontractors, must have a valid assurance. In addition, personnel involved in human subject research must document the completion of appropriate training for the protection of human subjects. 3. For all research that will involve human subjects in the first year or phase of the project, the institution must submit evidence of a plan for review by an institutional review board (IRB) as part of the proposal. The IRB conducting the review must be the IRB identified on the institution's Assurance of Compliance. The protocol, separate from the proposal, must include a detailed description of the research plan, study population, risks and benefits of study participation, recruitment and consent process, data collection, and data analysis. The designated IRB should be consulted for guidance on writing the protocol. The informed consent document must comply with 32 CFR 219.116. A valid Assurance of Compliance and evidence of appropriate training by all investigators should accompany the protocol for review by the IRB. 4. In addition to a local IRB approval, An AFRL-level human subject regulatory review and approval is required for all research conducted or supported by the DoD. The Air Force office responsible for managing the award can provide guidance and information about the AFRL-level review process. Confirmation of a current Assurance of Compliance and appropriate human subjects protection training is required before AFRL-level approval can be issued. 5. The time required to complete the IRB review/approval process will vary depending on the complexity of the research and/or the level of risk to study participants; ample time should be allotted to complete the approval process. The IRB approval process can last between 1 to 3 months, followed by a DoD review that could last 3 to 6 months. No funding may be used toward human subject research until all approvals are granted. Therefore, in their cost proposals offerors should separate human use into a separate option.V. APPLICATION REVIEW INFORMATION:1. CRITERIA: The following criteria, which are listed in descending order of importance and will be used to determine whether white papers and proposals submitted are consistent with the research areas of interest and expected results within the broad topic areas as described in the Funding Opportunity section of this BAA and of interest to the Government: a. Overall Scientific and Technical Merit - The soundness of approach for the development and/or enhancement of the proposed technology, b. Related Experience - The extent to which the offeror demonstrates relevant technology and domain knowledge, c. Openness and Assurance of Solution - The extent to which existing capabilities and standards are leveraged and d. Reasonableness and realism of proposed costs and fees (if any).No further evaluation criteria will be used in selecting white papers/proposals. White papers and proposals submitted will be evaluated as they are received.2. REVIEW AND SELECTION PROCESS: a. Only Government employees will evaluate the white papers/proposals for selection. The Air Force Research Laboratory's Information Directorate has contracted for various business and staff support services, some of which require contractors to obtain administrative access to proprietary information submitted by other contractors. Administrative access is defined as "handling or having physical control over information for the sole purpose of accomplishing the administrative functions specified in the administrative support contract, which do not require the review, reading, and comprehension of the content of the information on the part of non-technical professionals assigned to accomplish the specified administrative tasks." These contractors have signed general non-disclosure agreements and organizational conflict of interest statements. The required administrative access will be granted to non-technical professionals. Examples of the administrative tasks performed include: a. Assembling and organizing information for R&D case files; b. Accessing library files for use by government personnel; and c. Handling and administration of proposals, contracts, contract funding and queries. Any objection to administrative access must be in writing to the Contracting Officer and shall include a detailed statement of the basis for the objection. b. WHITE PAPER/PROPOSAL REVIEW PROCESS: 1. FIRST STEP - White Paper Reviews: The Government will review White Papers to determine which of them have the potential to best meet the Air Force's needs based on the criteria listed above. If white papers are of interest and funding is available, AFRL/RI will request a formal technical and cost proposal from offeror. If white papers are not of interest or there is not funding available, a letter is sent to the offeror indicating the reason not selected. 2. SECOND STEP - Proposal Review and Selection Process a) Categories: Based on the evaluation, proposals will be categorized as Highly Recommended, Selectable, or Not Selectable (see definitions below). The selection of one or more offerors for award will be based on the evaluation, as well as importance to agency programs and funding availability. 1) Highly Recommended: Proposals are recommended for acceptance if sufficient funding is available, and normally are displaced only by other Highly Recommended proposals. 2) Selectable: Proposals are recommended for acceptance if sufficient funding is available, but at a lower priority than Highly Recommended Proposals. May require additional development. To ensure a diversity of approaches, a Selectable proposal may be prioritized over a Highly Recommended proposal if the Selectable proposal presents a unique approach unlike any of the Highly Recommended proposals. 3) Not Selectable: Even if sufficient funding existed, the proposal should not be funded. c. The Government reserves the right to award some, all, or none of the proposals. When the Government elects to award only a part of a proposal, the selected part may be categorized as Highly Recommended or Selectable, though the proposal as a whole may not merit such a categorization. d. No other evaluation criteria will be used. e. Proposal Risk Assessment: Proposal risk for technical, cost, and schedule will be assessed for formal proposals, should they be requested, as part of the evaluation of the above evaluation criteria. Proposal risk relates to the identification and assessment of the risks associated with an offeror's proposed approach as it relates to accomplishing the proposed effort. Tradeoffs of the assessed risk will be weighed against the potential scientific benefit. Proposal risk for schedule relates to an assessment of the risks associated with the offeror's proposed number of hours, labor categories, materials, or other cost elements as it relates to meeting the proposed period of performance. f. Prior to award of a potentially successful offer, the Contracting Officer will make a determination regarding price reasonableness and realism.3. FEDERAL AWARDEE PERFORMANCE AND INTEGRITY INFORMATION SYSTEM (FAPIIS) PUBLIC ACCESS: As required by 2 CFR 200 of the Uniform Guidance and FAR 9.104-6, the Government is required to review and consider any information about the applicant that is in the FAPIIS before making any award in excess of the simplified acquisition teshold (currently $150,000) over the period of performance. An applicant may review and comment on any information about itself that a federal awarding agency previously entered. The Government will consider any comments by the applicant, in addition to other information in FAPIIS in making a judgment about the applicant's integrity, business ethics, and record of performance under federal awards when completing the review of risk posed by applicants as described in 2 CFR § 200.205 Federal Awarding Agency Review of Risk Posed by Applicants and FAR 9.104-6.VI. STEP TWO INFORMATION - REQUEST FOR PROPOSAL & AWARD:1. PROPOSAL FORMATING: When developing proposals, reference the AFRL "Broad Agency Announcement (BAA): Guide for Industry," Mar 2015, and RI-Specific Proposal Preparation Instructions, Jan 2017, which may be accessed at: https://www.fbo.gov/index?s=opportunity&mode=form&id=1cffad228f48b58057072a6c9113799d&tab=core&_cview=1. Always reference the newest versions of these documents.2. AWARD NOTICES: Those white papers found to be consistent with the research areas of interest and expected results within the broad topic areas as described in the Funding Opportunity section of this BAA and of interest to the Government may be invited to submit a technical and cost proposal. Notification by email or letter will be sent by the TPOC. Such invitation does not assure that the submitting organization will be awarded a contract. Those white papers not selected to submit a proposal will be notified in the same manner. Prospective offerors are advised that only Contracting Officers are legally authorized to commit the Government. All offerors submitting proposals will receive notification of their evaluation results within 45 days of submission. Offerors should email the TPOC and the Contracting Officer listed in Section VII, for status of their proposal after 45 days, if no such correspondence has been received.3. DEBRIEFINGS: If a debriefing is requested in accordance with the time guidelines set out in FAR 15.505 and 15.506, a debriefing will be provided, but the debriefing content may vary to be consistent with the procedures that govern BAAs (FAR 35.016). Debriefings will not be provided for white papers.4. ADMINISTRATIVE AND NATIONAL POLICY REQUIREMENTS:Depending on the work to be performed, the offeror may require a SECRET or TOP SECRET/SCI facility clearance and safeguarding capability; therefore, personnel identified for assignment to a classified effort must be cleared for access to SECRET or TOP SECRET/SCI information at the time of award. In addition, the offeror may be required to have, or have access to, a certified and Government-approved facility to support work under this BAA.This acquisition may involve data that is subject to export control laws and regulations. Only contractors who are registered and certified with the Defense Logistics Information Service (DLIS) and have a legitimate business purpose may participate in this solicitation. For questions, contact DLIS on-line at http://www.dla.mil/HQ/InformationOperations/LogisticsInformationServices.aspx or at the DLA Logistics Information Service, 74 Washington Avenue North, Battle Creek, Michigan 49037-3084, and telephone number 1-800-352-2255 (24/7). You must submit a copy of your approved DD Form 2345, Militarily Critical Technical Data Agreement, with your white paper/proposal.5. DATA RIGHTS: a. SBIR RIGHTS. The potential for inclusion of Small Business Innovation Research (SBIR) or data rights other than unlimited on awards is recognized. In accordance with (IAW) the Small Business Administration (SBA) SBIR Policy Directive, Section 8(b), SBIR data rights clauses are non-negotiable and must not be the subject of negotiations pertaining to an award, or diminished or removed during award administration. Issuance of an award will not be made conditional based on forfeit of data rights. If the SBIR awardee wishes to transfer its SBIR data rights to the Air Force or to a third party, it must do so in writing under a separate agreement. A decision by the awardee to relinquish, transfer, or modify in any way its SBIR data rights must be made without pressure or coercion by the agency or any other party. b. NON-SBIR RIGHTS. 1. Non-SBIR data rights less than unlimited will be evaluated and negotiated on a case-by-case basis. Government Purpose Rights are anticipated for data developed with DoD-reimbursed Independent Research and Development (IR&D) funding. 2. The Air Force Research Laboratory is engaged in the discovery, development, and integration of warfighting technologies for our air, space, and cyberspace forces. As such, rights in technical data and noncommercial computer software (NCS) developed or delivered under this contract are of significant concern to the Government. The Government will therefore carefully consider any restrictions on the use of technical data, NCS, and NCS documentation which could result in transition difficulty or less-than full and open competition for subsequent development of this technology. 3. Third Party Software. DFARS 252.227-7014(d) describes requirements for incorporation of third party computer software. Any third party software (commercial and noncommercial) to be incorporated into a deliverable must be clearly identified in the proposal. Prior to delivery of any third party software, the contractor will obtain an appropriate license for the Government, and the written approval of the contracting officer. c. IDENTIFICATION & ASSERTION. IAW DFARS 252.227-7017, the Identification and assertion of Use, Release, or Disclosure Restriction provision applies. See AFRL/RI Specific Proposal Preparation Instructions for further guidance and samples.6. REPORTING: a. Contract Applicable: Once a proposal has been selected for award, offerors will be given complete instructions on the submission process for the reports. b. FAPIIS Applicable: As required by 2 CFR 200 Appendix XII of the Uniform Guidance and FAR 9.104-6, non-federal entities (NFEs) are required to disclose in FAPIIS any information about criminal, civil, and administrative proceedings, and/or affirm that there is no new information to provide. This applies to NFEs that receive federal awards (currently active grants, cooperative agreements, and procurement contracts) greater than $10,000,000 for any period of time during the period of performance of an award/project.7. NOTICE: The following provisions* apply:(a) FAR 52.209-11, Representation by Corporations Regarding Delinquent Tax Liability or a Felony Conviction under any Federal Law (b) DFARS 252.239-7017, Notice of Supply Chain Risk (c) DFARS 252.204-7008, Compliance with Safeguarding Covered Defense Information Controls * Please note that the current versions or deviations of the related clauses will be included in any resulting contract.8. GRANT AWARDS ONLY: For efforts proposed as grant awards, offerors must provide an abstract in their proposal (not to exceed one page) that is publically releasable and that describes - in terms the public may understand - the project or program supported by the grant. If the proposal is selected for award, the DoD will publically post the abstract to comply with Section 8123 of the Department of Defense Appropriations Act, 2015 (Pub. L. 113-235).VII. AGENCY CONTACTS:All white paper and proposal submissions and any questions of a technical nature shall be directed to the cognizant TPOC as specified below (unless otherwise specified in the technical area):TPOC Name: Howard M. BeyerMailing Address: 525 Brooks Road, Rome NY 13441-4505Telephone: (315) 330-4718Email: Howard.Beyer.1@us.af.milQuestions of a contractual/business nature shall be directed to the cognizant contracting officer, as specified below (email requests are preferred):Gail MarshTelephone (315) 330-7518Email: Gail.Marsh@us.af.milEmails must reference the solicitation (BAA) number and title of the acquisition.In accordance with AFFARS 5301.91, an Ombudsman has been appointed to hear and facilitate the resolution of concerns from offerors, potential offerors, and others for this acquisition announcement. Before consulting with an ombudsman, interested parties must first address their concerns, issues, disagreements, and/or recommendations to the contracting officer for resolution. AFFARS Clause 5352.201-9101 Ombudsman (Jun 2016) will be incorporated into all contracts awarded under this BAA.The AFRL Ombudsman and AFRL Alternate Ombudsman are as follows:Ombudsman: Ms Lisette K. LeDuc 1864 Fourth St. Wright-Patterson AFB OH 45433-7130 937-904-4407 lisette.leduc@us.af.milAlternate Ombudsman: Ms Kimberly L. Yoder 1864 Fourth St. Wright-Patterson AFB OH 45433-7130 937-255-4967 kimberly.yoder@us.af.milAll responsible organizations may submit a white paper which shall be considered.
FA8750-17-S-7008 Department of the Air Force Materiel Command Research Laboratory
9/19/17, 10:13 AM