Loren Data's SAM Daily™

FBO DAILY - FEDBIZOPPS ISSUE OF NOVEMBER 04, 2017 FBO #5825
MODIFICATION

A -- Cyber Asymmetric Force Applications for Unmanned Aircraft Systems

Notice Date

11/2/2017
 

Notice Type

Modification/Amendment
 

Contracting Office

Department of the Air Force, Air Force Materiel Command, AFRL/RIK - Rome, 26 Electronic Parkway, Rome, New York, 13441-4514, United States
 

ZIP Code

13441-4514
 

Solicitation Number

FA8750-17-S-7001
 

Point of Contact

Gail E. Marsh, Phone: 315-330-7518
 

E-Mail Address

Gail.Marsh@us.af.mil
(Gail.Marsh@us.af.mil)
 

Small Business Set-Aside

N/A
 

Description

AMENDMENT 3 for BAA FA8750-17-S-7001 The purpose of this modification is to republish the original announcement, incorporating any previous amendments, pursuant to FAR 35.016(c). This republishing also includes the following changes: (a) Section III: Update Eligibility Requirements; (b) Section IV.1: Remove the Focus Area 1 suggested submission date. White papers can now be accepted at any time; (c) Section IV.3.a: Remove NISPOM Change 1 and date; (d) Section IV.4.b, c & d: Updated date and regulations cited; (e) Section VI.4: Updated DLA/DLIS information; (f) Section VI.5: Updated applicable clauses; and (g) Section VII: Update the Ombudsman information. No other changes have been made. NAICS CODE: 541712 FEDERAL AGENCY NAME: Department of the Air Force, Air Force Materiel Command, AFRL - Rome Research Site, AFRL/Information Directorate, 26 Electronic Parkway, Rome, NY, 13441-4514 BROAD AGENCY ANNOUNCEMENT (BAA) TITLE: Cyber Asymmetric Force Applications for Unmanned Aircraft Systems BAA ANNOUNCEMENT TYPE: Initial announcement BAA NUMBER: FA8750-17-S-7001 CATALOG OF FEDERAL DOMESTIC ASSISTANCE (CFDA) Number: 12.800 & 12.910 I. FUNDING OPPORTUNITY DESCRIPTION: The Air Force Research Laboratory is soliciting white papers under this Broad Agency Announcement (BAA) for research, development, integration, test and evaluation of technologies/techniques to advance the technology and/or increase the knowledge, understanding and capability of cyber operations technologies that can address current Department of Defense (DoD) gaps in operational asymmetric campaigns and force protection capabilities through rapid prototyping efforts. This includes integration research into technology and approaches to better equip the warfighter. Concepts at the intersection of the areas of Signals Intelligence (SIGINT), Electronic Warfare (EW) and Cyber Operations technologies are sought in this Broad Agency Announcement (BAA). Development proposals, specifically as applies to new ideas/concepts for practical application, are of interest. Research efforts under this program are expected to result in experimental capabilities, concepts, theory, and applications addressing cyber operations problems and asymmetric threats to support the future needs of units including 1st Air Force - AFNORTH, 24th Air Force, 25th Air Force, Air Force Global Strike Command, Air Force Security Forces Center, and other government agencies. Projects specializing in highly novel, interesting, and applicable techniques will also be considered if deemed to be of "breakthrough" quality and importance. The effectiveness of the developed technologies for potential operational use will be assessed through preplanned testing and evaluation activities. Rapid prototyping of technologies that can be transitioned for operational use are of high interest, and will be assessed for transition through other contract vehicles; this BAA is for the research and development phases. Offerors are encouraged to describe the pre-conditions and assumptions that are necessary for the proposed techniques to work effectively. Broad topics of interest include: maturing, integrating, and testing C2 and detection capabilities of unmanned aircraft systems; developing new and applying currently available cyber operations technologies for use in airborne and ground platforms; developing technologies to better equip the warfighter for force and materiel protection operations; automatic decision making and enabling autonomy in cyberspace operations; developing concepts and capabilities that intersect the areas of SIGINT, EW and Cyber for asymmetric force applications; and developing big data analytics methods for asymmetric for non-traditional technologies and weapon systems. As stated above, breakthrough research will be considered outside these focus areas if compatible with BAA goals. FOCUS AREA - Cyber Asymmetric Force Applications for Unmanned Aircraft Systems (C-sUAS) Command and Control (C2) Framework Background: The government is looking for an open architecture solution that enables command and control (C2) of Counter-small Unmanned Aircraft Systems (C-sUAS) segments. This "C2 Framework" includes several aspects as outlined below. It is expected to leverage existing government off-the-shelf (GOTS) C-sUAS tactical C2 code. The C2 Framework is to include the appropriate middleware and interfaces to enable the open architecture. Segments/subsystems may include detection, identification, tracking, or defeat capabilities. A typical C-sUAS deployment likely includes a mixture of disparate segments from various vendors to meet the mission needs and budget of each site. These may be a mixture of commercial off-the-shelf (COTS) products or custom built under government contract. Given this composition, interoperability and integration are a prime concern. The goal is to define a government-owned interface specification (i.e., a set of interface control documents [ICD]) and an interoperability certification process. This is similar to the approach taken by the UAS Control Segment (UCS) Architecture for control of large, blue-force drones. Discussion: Small UAS threats typically involve dynamic targeting which brings effects to bear via the kill chain. C-sUAS targeting effects involve the 5D's (disrupt, deny, degrade, destroy, or deceive) on any component of the threat sUAS or its control. Effects could go after threat payloads as well (e.g., blind the camera). The C-sUAS system needs to operate in multiple modes: both human-in-the-loop (HITL) and human-on-the-loop (HOTL). In HITL mode the operator must initiate defeat options based on system recommendations. In HOTL mode, the system will automatically execute authorized 5D effects unless overridden by the operator. The latter mode is necessary due to the very tight dynamic targeting kill chain timeline associated with various sUAS threat scenarios. (It is assumed that policy will allow some HOTL parameters in the future.) The government intends to integrate best-of-breed C-sUAS segments from multiple vendors, thus emphasizing the need for interoperability. Vendors need the flexibility to design C-sUAS segments implementing various compute architectures and operating systems with applications written in their software language of choice. Items needed to ensure cross-platform interoperability include: (1) A common or translatable data model; (2) Shared data semantic understanding; (3) Platform-independent mechanism for data exchange; (4) Connectivity between segments; (5) Agreed communications protocols, integration pattern, and message exchange pattern(s); (6) A wire format and data serialization amenable to all parties; and (7) Shared cybersecurity mechanisms such as authentication. The C2 Framework intends to accomplish this via a C2 command set or message set (with associated schema/data model) in some industry standard format and serialization (e.g., eXtensible Markup Language [XML], Protocol Buffers, or JavaScript Object Notation [JSON]). The goal is to balance specificity and flexibility to achieve the necessary interoperability. Some C-sUAS segments may adhere to the ICD; it is assumed that some will not for various reasons (e.g., legacy system). Vendor funding, roadmaps, or motivations may delay or preclude ICD alignment. The C2 Framework must enable the ability to interface with legacy segments (e.g., radar, EW) via adapters, services, or similar technology that can perform the necessary data model and data format transformation or protocol bridging. Information exchange requirements (IER) include real-time data exchanges, possibly in a publish/subscribe or event-based design pattern (To be Determined [TBD]), needed to prosecute the dynamic targeting kill chain necessary to defeat sUAS, which possibly involves a swarm. These segments communicate over a network likely involving a mixture of wired and wireless links via agreed to protocols. The local network must provide basic services such as time synchronization to attached segments. The segments communicate with the C2 Node to enable C2, health/status, etc. Use of "C2 node," "C2 segment," or "C2 logic" does not necessitate hub and spoke architecture. These terms are used interchangeably. Additionally, the C2 logic may be distributed. Use of the term, "C2 Framework," refers to the entire construct that enables C2. Segments require different levels of integration. For example, a radar detection segment may get by with publishing bogey/contact tracks to the correlation engine and not understand-or even receive-all the C2 messages defined in the ICD. An adapter may translate these tracks (e.g., geodetic datum transformation) to conform with the ICD so that the rest of the system understands the data. A hunter-killer (HK)-blue-force interceptor drone-on the other hand, needs a much closer level of integration. The HK must understand C2 messages such as a launch command to counter the threat sUAS. Other HK-related commands may be warm-up/initialize, intercept waypoints, and employ defeat mechanism. The HK should send C2 acknowledgements and status information (e.g., available time on station, successful arrest) back via the C2 Framework to the C2 Node. Existing message sets may be leveraged such as Micro Air Vehicle Link (MAVLink). The C2 Node will present information to the human operator via a User Interface (UI). The UI may involve a mobile device, workstation, or display integrated into a command center or vehicle. Flexibility is the key. UI likely consists of a display as well as audible and possibly tactile feedback. The C2 Framework comprises automated C2 logic and a rules engine or expert system that can escalate the dynamic kill chain IAW the Rules of Engagement (ROE) as the threat increases. This C2 logic (1) presents recommendations and options to the operator via the UI and (2) controls segments IAW the HITL/HOTL mode for that particular effect. (C2 logic will be expounded in a future BAA focus area/addendum.) The C2 Framework will leverage COTS Application Programming Interfaces (API) where appropriate. For example, a HK may be based on a COTS sUAS carrying a C2 payload mounted on a gimbal that leverages the COTS API or MAVLink for sUAS flight control. The C2 Framework will leverage existing standards as appropriate such as Eurocontrol's All Purpose Structured Eurocontrol Surveillance Information Exchange (ASTERIX) standard ( https://www.eurocontrol.int/asterix-specifications-library ) for radar tracks. Other standards include but are not limited to Cursor on Target (CoT), U.S. Message Text Format (USMTF), and Variable Message Format (VMF). Several of these are employed by the GOTS C-sUAS tactical C2 code. One segment of a C-sUAS is expected to comprise a Library. It is envisioned that Library contents include various COTS sUAS characteristics, signals of interest (SOI), and targeting effects (i.e., EW and cyber). Thus the C2 Framework message set must support requests/queries to the Library. For example, a cyber/EW segment may request/query what effects are available in the Library for a particular sUAS. To ensure proper cybersecurity and resiliency, the C2 Framework will include appropriate controls. Authentication, authorization, and accounting mechanisms need to be established to ensure confidentiality, integrity, and availability of the various services and data exchanges between segments. Appropriate trade studies (with various levels of formality) should be performed to ensure the framework can meet the expectations placed upon it (e.g., latency, security, and performance). These expectations are based on the myriad employment scenarios in which a C-sUAS system may be engaged and the expected concept of operations (CONOPS). Scenarios include austere environments where a robust implementation is needed to account for networks with low bandwidth, high latency, and intermittent connectivity. Other information exchange aspects include selecting the appropriate technologies for the following areas: Integration patterns, message exchange patterns (aka service interaction patterns), wire format (aka wire protocol), middleware and messaging alternatives, and data serialization (aka data interchange format). It is possible that the C2 Framework incorporates multiple options to facilitate interoperability. The C2 Framework should facilitate interfaces with external Command, Control, Communications, Computers, Intelligence, Surveillance, and Reconnaissance (C4ISR) systems or integration with another C2 system (e.g., a base integrated defense system). The C-sUAS C2 Node needs to: (1) Receive threat intelligence, (2) Receive C2 (including ROE), and (3) Send situational awareness (SA) and status data and reports to external C4ISR systems. Particular external C4ISR systems are TBD. Communication with external systems likely involves messaging standards such as USMTF, VMF, CoT, or others. Based on existing capabilities and planned improvements of the GOTS C-sUAS tactical C2 code, the forward-looking BAA focus area with be on the following aspects: (1) Integration of advanced C2 logic/autonomy; (2) Addition of HK C2 leveraging COTS sUAS APIs and standards; (3) Cybersecurity hardening; (4) Evaluation of adapter/translator architecture that alleviates latency and complexity; (5) Integration with higher-level C2 systems and external C4ISR systems; and (6) Open architecture messaging as well as queueing and transformation services/middleware to evaluate messaging requirements such as guaranteed delivery, durability, etc. C2 Framework Tenets: (1) Open Systems Architecture (OSA) (formerly known as Modular Open Systems Approach [MOSA]) based on industry standards and technologies (2) Cross-platform interoperability and platform-independence (i.e., independent of Central Processing Unit [CPU] instruction set and operating system [OS]) that allows implementation on different computing infrastructures with possibly differing communication protocols (3) Unlimited Rights (UR) for both computer software and associated technical data to facilitate 3rd party integration and maintainability (4) Extensible to support technology insertion and adoption (5) Facilitate legacy systems via adapters/translators (6) Cybersecurity and resilience baked-in rather than bolted-on (7) Applies applicable Global Information Grid (GIG) Technical Guidance Federation (GTG-F) Standards (formerly DoD Information Technology Standards Registry [DISR]) (8) Cross-agency governance Additional technical information relevant to this BAA is contained in a 6-page classified addendum dated 13 Sep 2016. An additional 9-page classified addendum, dated 1 Jun 2017 titled Command & Control (C2) Automation, is also available for those interested in proposing to this focus area. The classification level for both addendums is SECRET. If you wish to review either of the classified addendums prior to submission, please follow the guidance below. A DD 254 is attached to this BAA for further guidance. To obtain a copy of the classified addendum and the appropriate Security Classification Guide, which provides instructions and guidelines on the classification/declassification of information and submission materials, offerors must send a request to the BAA cognizant technical point of contacts listed in Section VII, and provide the following information: Full Company Name Classified mailing address Cage Code Facility Security Officer (FSO) name and phone number Technical POC name and phone number Classified Email Address, if applicable POSSIBLE BASE SUPPORT OPPORTUNITIES: Successful Offerors may be provided access to the AFRL/RI Stockbridge Experimentation and Test Facility on a non-interference basis, during normal duty hours. The Stockbridge Facility is a 300 acre world class facility providing a truly unique capability to support real world, outdoor and tactical edge experimentation for a wide range of technologies. Our certification by the FAA provides us the ability to conduct airborne testing utilizing our fleet of small unmanned aerial systems, providing the ability for controlled experiments in a dynamic environment. This infrastructure supports the cost effective testing and development of technologies envisioned for use in ground based and/or airborne configurations. Additionally access may include office and laboratory space within the AFRL/RI (Information Directorate) Rome NY, Building 3, if required. All requests for access will be considered on a case-by-case basis. II. AWARD INFORMATION: 1. FUNDING: Total funding for this BAA is approximately $49.9M. The anticipated funding to be obligated under this BAA is broken out by fiscal year as follows: FY17 - $10M FY18 - $10M FY19 - $10M FY20 - $10M FY21 - $9.9M Individual awards will not normally exceed 36 months with dollar amounts normally ranging from $250K to $3M. There is also the potential to make awards up to any dollar value. 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-7001. c. Any performance by foreign nationals at any level (prime contractor or subcontractor) must be clearly identified in the Offerors proposal. Identify any foreign citizens or individuals holding dual citizenship expected to be involved as a direct employee, subcontractor, or consultant. For these individuals, please specify their country of origin, the type of visa or work permit under which they are performing and an explanation of their anticipated level of involvement. You may be asked to provide additional information during negotiations in order to verify the foreign citizen's eligibility to participate on a contract issued as a result of this announcement. d. 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. Government agencies interested in performing work related to this announcement should contact the Technical Point of Contact (TPOC). If resulting discussions reveal a mutual interest, cooperation may be pursued via other vehicles. 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 2 PM Eastern Standard Time (EST) on the following dates to maximize the possibility of award: FY17 by 31 Jan 2017 FY18 by 31 Jan 2018 FY19 by 31 Jan 2019 FY20 by 31 Jan 2020 FY21 by 29 Jan 2021 White papers will be accepted until 2 PM EST on 30 Sep 2021, 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 Sep 2021. All offerors submitting white papers will be contacted by the TPOC, referenced in Section VII of this announcement. Offerors can email the TPOC for status of their white paper/proposal no earlier than 45 days after submission. 2. CONTENT AND FORMAT: Offerors are required to submit three (3) 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, fax 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 Dun & Bradstreet (D&B) Data Universal Numbering System (DUNS) number, a fax number, an e-mail address, and reference BAA #: FA8750-17-S-7001 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): Vincent Guza, IPO 315-330-4048 0730-1630 Monday-Friday 315-330-2961 Evenings and Weekends Email: vincent.guza@us.af.mil b. CLASSIFIED SUBMISSIONS. AFRL/RIGB 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. All classified responses to this announcement must be sent U.S. Postal Service, registered mail to the address below and reference BAA #: FA8750-17-S-7001 and TPOC on the inner envelope. Use classification and marking guidance provided by previously issued security classification guides, the Information Security Regulation (DoD 5200.1-R), and the National Industrial Security Program Operating Manual (DoD 5220.22-M) when marking and transmitting information previously classified by another original classification authority. Classified information at the Confidential and Secret level may be mailed via U.S. Postal Service (USPS) Registered Mail. For proposals of higher classification levels or for alternate submission mechanisms please contact the technical POC listed in Section VII. When mailing, ensure the response is appropriately marked, sealed, and mailed in accordance with the classified material handling procedures. The classified mailing address is: AFRL/RIGB 525 Brooks Road Rome NY 13441-4505 Reference BAA #: FA8750-17-S-7001. When mailing either classified or unclassified documentation, follow the directions regarding the number of copies required. If the offeror has a secure email system, they may submit their papers via it to usaf.rome.afrl-information-directorate.mbx.afrl-rigb-baa17-01@mail.smil.mil. Please contact the TPOC in Section VII prior to sending. All unclassified electronic submission shall be emailed to afrl.rigb.baa17-01@us.af.mil. Encrypt or password-protect all proprietary information prior to sending. If electronic submission is used, only one (1) copy of all the documentation is required. For all electronic submissions : Offerors are responsible to confirm receipt with the technical POC listed in Section VII. AFRL is not responsible for undelivered documents. Questions can be directed to the technical POC listed in Section VII. 4. OTHER SUBMISSION REQUIREMENTS/CONSIDERATIONS: a. COST SHARING OR MATCHING: Cost sharing is not a requirement. 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 through 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 2 CFR part 200.458, Pre-Award Costs. e. GOVERNMENT APPROVEDACCOUNTING 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 V. APPLICATION REVIEW INFORMATION: 1. CRITERIA: The following criteria, which are of equal importance and will be used to determine whether white papers and proposals submitted are consistent with the intent 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. The potential contributions of the effort to the U.S. Air Force Cyber Asymmetric Force Applications for Unmanned Aircraft Systems mission, c. Related Experience - The extent to which the offeror demonstrates relevant technology and domain knowledge including experience and qualification of the types of personnel proposed and the quantity and quality of the offeror's experience relevant to the requirements. This include an understanding of Air Force and/or Joint cyber operations, and SIGINT/EW tools, platforms, and processes, d. Openness, Maturity and Assurance of Solution - The extent to which existing capabilities and standards are leveraged and the relative maturity of the proposed technology, and e. 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: 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. 3. ADEQUATE PRICE COMPETITION: The Government may simultaneously evaluate proposals received under this BAA with a common cutoff date for multiple offerors. In this case, the Government may make award based on adequate price competition, and offerors must be aware that there is a possibility of non-selection due to a proposal of similar but higher-priced technical approach as compared to another offeror. 4. 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 threshold (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. VI. STEP TWO INFORMATION - REQUEST FOR PROPOSAL & AWARD: 1. AWARD NOTICES: Those white papers found to be consistent with the intent of this BAA 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. For additional information, a copy of the AFRL "Broad Agency Announcement (BAA): Guide for Industry," Mar 2015, and Proposal Preparation Instructions, Dec 2014, 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. 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. 3. 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. 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. 4. 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(c), 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. 5. 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. 6. 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): BAA Manger Deputy BAA Manager Philip J. Zaleski Brendon J. Poland Telephone: (315) 330-3218 Telephone: (315) 330-2838 Email: afrl.rigb.baa17-01@us.af.mil Email: afrl.rigb.baa17-01@us.af.mil Questions of a contractual/business nature shall be directed to the cognizant contracting officer, as specified below (email requests are preferred): Gail Marsh Telephone (315) 330-7518 Email: Gail.Marsh@us.af.mil Emails 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.mil Alternate Ombudsman: Ms Kimberly L. Yoder 1864 Fourth St. Wright-Patterson AFB OH 45433-7130 937-255-4967 kimberly.yoder@us.af.mil
 

Web Link

FBO.gov Permalink
(https://www.fbo.gov/spg/USAF/AFMC/AFRLRRS/FA8750-17-S-7001/listing.html)
 

Record

SN04730744-W 20171104/171102231928-3aa8504328bfcd515e154ad2200a3d1e (fbodaily.com)
 

Source

FedBizOpps Link to This Notice
(may not be valid after Archive Date)

---

| FSG Index  |  This Issue's Index  |  Today's FBO Daily Index Page |