Loren Data's SAM Daily™

FBO DAILY - FEDBIZOPPS ISSUE OF JULY 31, 2014 FBO #4632
MODIFICATION

A -- Integrated Command & Control

Notice Date

7/29/2014
 

Notice Type

Modification/Amendment
 

NAICS

541712 — Research and Development in the Physical, Engineering, and Life Sciences (except Biotechnology)
 

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

BAA-10-01-RIKA
 

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

The purpose of this modification is to: 1) Updated Section I to reflect current requirements; 2) Section III.6 is revised to reflect the current AFRL Rome Research Site Information Protection Office POC; and 3) Section VII is revised to include the Ombudsman's email address. 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 TITLE: Integrated Command & Control ANNOUNCEMENT TYPE: Initial announcement FUNDING OPPORTUNITY NUMBER: BAA 10-01-RIKA CFDA Number: 12.800 I. FUNDING OPPORTUNITY DESCRIPTION: Meeting the demands of assigned missions requires unprecedented amount of coordination and synchronization of military resources across all organizations and all echelons of command in all levels of war. It is command and control (C2) that provides the means by which a commander synchronizes and/or integrates force activities in order to achieve the commonly recognized objectives in one unity of effort. These activities require key decisions within the strategy, planning, scheduling and assessment phases of the command and control process. These decisions are made by humans and are supported by computer technology so it is in these areas that information technology contributes the most to ameliorating human capabilities and transforming how the Air Force commands and controls. The goal of the Integrated C2 program is to lead the discovery, development and integration of revolutionary warfighting information technologies that enable continuous and distributed, planning, execution, and assessment of resources across the cyber, air and space domains to achieve commander's intent. Air Force Research Laboratory is seeking innovative white papers to address the following thrusts: 1) Strategy Development. The functional translation of a commander's conceptual vision and guidance into potential solutions via an adaptive planning capability that supports the generation of a plan of action and seeks to answer the questions of what is to be done and how. By monitoring the plan and operating environment, adapt to evolving situations and represent the necessary actions which incorporate all means available across each of the warfighting domains of the Air Force (air, space and cyber). A key challenge is to understand the complex relationships and dependencies that exist across these domains. Specific areas of interest include but are not limited to: machine reasoning with uncertain, erroneous, and incomplete information; dynamic causal modeling and multi-criteria analysis summarization; computational efficient mixed initiative planning that balances cognitive and machine load; incorporation of analogical/experiential reasoning (fusion of distributed experiences, capturing knowledge & experience of the past, determining relevancy of past situations); and asynchronous planning on plan fragments versus synchronous "lock and work" planning over multiple iterations. 2) Synchronized/Integrated Planning. Produce a logistically feasible plan of action to solve the problem, fully integrating subordinate action plans with a description of the role of the other elements of national power in conjunction with military activities. Synchronized/integrated planning includes requests for actions and describes the role of military activities in achieving the desired effects. The integrated "battle" plan enables warfighters to coordinate and synchronize all available forces, kinetic and non-kinetic, to achieve the desired outcomes and exploit opportunities as they present themselves. Specific areas of interest include but are not limited to: a living plan with "on the fly" action plan/course of action adaptation/mutation that addresses changing conditions of the operational environment; identification, correlation, and advisement on mitigation of external events affecting the processes and mission; continuous adaptive planning; and comprehensive mission-driven situation awareness sharing. 3) Continuous Assessment. Full spectrum analysis of the attainment of mission objectives at all levels of the campaign (tactical to strategic). At the plan's inception, conduct rigorous examinations of the alternatives and the desired and undesired consequences of each action leading to valuable insight into the actions, causal mechanisms, and effects that support the accomplishment of the objective. Leading indicators or clues can be explicitly identified with their timing which then can be used as a measure of progress towards accomplishing the desired objectives providing the means by which each player understands what is necessary to achieve the overall objectives and the ramifications of their individual actions. Such insights serve to highlight key challenges in sustaining a campaign's progress and are important for synchronizing the force. Specific areas of interest include but are not limited to: non-deterministic, non-linear causal analysis with reasoning through uncertainty and ambiguity; projective/forward looking analysis through modeling and simulation; use of belief networks within a decision-making environment and how beliefs influence a decision/assessment; dynamic assessment of a-priori and a-posteriori achievement of commander's intent; deliberate causal analysis that identifies key missing data that can be used as information requests; and optimized presentation of complex heterogeneous data. FOCUS AREAS Machine Intelligence for Mission Focused Autonomy (MIMFA) The Machine Intelligence for Mission-Focused Autonomy (MIMFA) program will research technologies that enable distributed autonomous assets to make intelligent coordinated adaptations to plans/policies that optimize mission performance in dynamic and realistically complex domains. Emphasis is placed upon autonomous techniques which enable faster, more efficient understanding for complex, multi-modal military data. Autonomous systems have the potential to significantly improve the agility and effectiveness of our nation's military while reducing manpower and cost requirements. However, the robustness of current autonomous and automated control technologies is inadequate given the dynamics and complexities of practical real-world problems. The Machine Intelligence for Mission-Focused Autonomy (MIMFA) program will research technologies that enable distributed autonomous assets to make intelligent coordinated adaptations to plans/policies to optimize mission performance in dynamic and realistically complex domains. Emphasis is placed upon autonomous techniques which enable faster, more efficient understanding for complex, multi-modal military data. The ability to autonomously seek out, understand, and present information to human decision makers will contribute greatly to future mission success. General technical areas for this MIMFA program are Knowledge Discovery and Data Mining (KDD), Machine Learning (ML), and Multi-Agent Systems (MAS). KDD is the capability to draw conclusions, find specific information, and fine-tune understanding by bringing together large, heterogeneous data sources. ML is the capability for software to adapt its behavior through training or experience to better solve problems. MAS are systems of intelligent software agents interacting to solve highly complex problems, collaborate amongst themselves, and observe and present information on behalf of the human. By combining these three technical areas, we believe there are powerful synergies to be found in helping Command Control Intelligence Surveillance Reconnaissance (C2ISR) operators better understand complex problems and take decisive action. The application context of interest is the Data to Decisions domain and its associated processes. Within this domain the MIMFA program envisions an information spectrum containing various states of information within which we foresee the autonomous multi agent systems working. The first is a dynamic information state which includes self-organizing information collectors. Our goal is to enable the capability for a group of heterogeneous agents to seek mission-relevant information. To accomplish this we wish to advance the science and technology related to the tasking, coordination, self-organization, and negotiation of distributed agents in and amongst the complex domains of air, space, and cyber. Interesting, but not mandated, approaches include extending game theory to reason across the dynamics of individual and group utility to drive agent rationality, as well as both distributed constraint satisfaction and auctioning as mechanisms for self-organization without the need for a central control. The second information state is a static state in which information is at rest in any number of large data sets. The resulting capability required in this state is for a group of heterogeneous agents that can examine data from different perspectives, compare multiple hypotheses, classify important states and features, identify gaps in understanding, and ultimately provide a robust and rational analysis for human decision-makers. Performing this analysis in a timely manner relies upon the agents' ability to dynamically self-adapt their capabilities to new data, as well as understanding and building upon the trust and confidence of human operators. A successful group of agents will operate to answer the commander's need for actionable decision options which take into account multiple perspectives on the data and demonstrate a robust understanding of the problem, potential solutions, risks, and information provenance. Relevant technical areas, but NOT of interest to the MIMFA program at this time include: 1) Trust - Trust in the output of the autonomous agents should be considered during technology development. While the issue of trust in autonomous agent systems is a major concern, it will be addressed specifically in a subsequent solicitation (planned start in FY15). 2) Group/Transfer Learning - Group and transfer learning between heterogeneous multi agent systems is of high importance to the MIMFA program, but will be the addressed specifically in a subsequent solicitation (planned start in FY14). 3) Human/Robot Interfaces (HRI) - The MIMFA program plans to leverage, to the maximum extent, previous and existing investments in HRI and agent visualization research. Agent feedback to the human operator is an important capability. Offerors looking to propose HRI or visualization as part of their proposal should consider utilizing existing HRI and visualization capabilities. 4) Robotic Control - The MIMFA program is not interested in the development of autonomous agent capabilities for control of physical entities such as RPA's and their associated control surfaces. Specific Focus Area for 2015 Trusted Autonomy and Verification and Validation (V&V) This focus area describes a research project entitled "Trusted Autonomy and Verification and Validation (V&V)," to be executed under the Machine Intelligence for Mission Focused Autonomy (MIMFA) Program for the Air Force Research Laboratory. The autonomous software systems envisioned by the U.S. Air Force - particularly confederations of autonomous agents in complex, dynamic environment (such as a group of heterogeneous UAVs performing an ISR mission) - can be expected to manifest emergent behaviors unpredicted by their designers. Recognition, prediction, and control of these unexpected behaviors are potential obstacles in the critical path to the successful fielding of these systems. The overall objective of this project is to secure a foundation for trusted autonomy through development of advanced modeling, simulation, analysis, test, and design techniques for test, evaluation, verification, and validation (TEV&V) of autonomous systems. Topic areas of interest within the FY15 Trusted Autonomy and V&V Focus Area include: Detection of Unexpected/Emergent Behavior. Emergent behaviors are usually discovered "post-mortem" by simple inspection of a (real or simulated) system [1]. It is relatively straightforward to develop tests for detecting any specific behavior; however, detection of arbitrary, unexpected emergent behavior as it occurs, without reference to visual inspection, is considerably more challenging. A possible approach is the adoption of an extensive domain-specific emergent-behavior taxonomy detailing unique behaviors seen in complex systems, along with a battery of tests for each specific behavior [2], [3]. Broader anomaly detection might also be accomplished by judicious measurements of global properties; for instance, Fourier analysis of system dynamics in search of unexpected periodicity [4], or statistical sampling of resource allocations to detect departures from expected fairness [2]. Because many envisioned multi-agent systems are decentralized, loosely-coupled federations, emergent behavior detection logic should require as few agents and as little communication as possible. This topic encompasses all tasks required to detect both specific and arbitrary emergent behaviors in an autonomous system, including but not limited to: 1) Development of domain-specific emergent behavior taxonomies. 2) Abstraction of specific behaviors into classes, and development of correspondingly broader detection logic. 3) Development of test for each identified possible EB or class. 4) Mapping of specific global behaviors above to purely local behavioral bounds. For instance, a single agent might raise an alert when it detects that it is being tasked to fly over the same area more frequently than expected, that it is undergoing collision avoidance frequently, or that it is being starved of a necessary resource. (Due to the global nature of emergent behaviors, such purely local observations will not suffice to detect all behaviors in the catalog. 5) Mapping of specific emergent behaviors to behavioral bounds over a limited subsets of agents; for instance, allowing an agent to consider the positions of its immediate neighbors. 6) Development of efficient algorithms for propagation of global state among UAVs to detect remaining behaviors that cannot be discovered locally. Control of Unexpected/Emergent Behaviors. Following detection of an unexpected and potentially detrimental behavior, the system must work to correct the behavior. This challenge is amplified in a large multi-agent system, particularly when direct communication with all agents is not possible. A possible approach to the problem is a top-down design for trust that guarantees that the system cannot enter undesirable states. Run-Time Assurance (RTA) [5] (or the closely-related Simplex architecture [6], [7]) is such a solution, employing a real-time watchdog module to detect out-of-bounds behavior and transfer control to a backup, trusted legacy controller. This topic encompasses all techniques for returning the multi-agent system to a safe state following detection of unexpected emergent behaviors. Subtasks may include: 1) Development of provably correct hierarchical safety architectures and distributed detection protocols for broad classes of behaviors. 2) Protocols and algorithms for extension of the RTA architecture to a distributed, multi-agent case. 3) Distributed communication protocols for introducing rapid behavioral change in a multi-agent system. 4) Incorporation of low-bandwidth influence techniques to control swarm behavior via manipulation of a limited subset of individuals [8]. Prediction of Unexpected/Emergent Behaviors. Historically, modeling and simulation of a system is the only way to predict emergent behaviors ahead of deployment. Because simulations of complex, high-state space cyber-physical systems cannot be exhaustive (and will in any case fail to capture all possible couplings between the system and its environment), they cannot make formal guarantees. To achieve high confidence that multi-agent systems will not exhibit unwanted emergent behaviors, we would like to analyze the system formally such that 1) the possible range of behaviors the system might take are formally circumscribed; and/or 2) specific unwanted behaviors are proven impossible. Formal methods of analysis prove desirable properties of a software system based on a formal specification (for instance, in temporal logic) [9]. Traditional formal methods apply to single-threaded algorithms; newer techniques for concurrent, multi-agent systems continue to be developed [10, 11, 12, 13, 14, 15, 16, 17, 18]. This topic encompasses techniques for predicting latent emergent behavior before system fielding via efficient modeling, simulation, analysis, and test, including formal guarantees of the absence of specific behaviors or classes of behaviors. Subtasks may include: 1) Development of efficient simulation/test techniques for autonomous systems, including dimensionality-reduction or other approximation techniques to reduce state space. 2) Development of comprehensive executable environmental models incorporating rare events and specific known emergent behavior triggers. 3) Development of heuristic (informal) signature-based techniques for recognizing design factors correlated with particular behaviors in an emergent behavior taxonomy. 4) Application of concurrent formal methods to provide formal guarantees of the absence of specific emergent behaviors or behavior classes. Expected end deliverables for this focus area include models, simulations, and algorithms. White papers for this focus area are due by September 15, 2014. It is anticipated that awards for this focus area will range from 9 to 24 months with dollar amounts nominally up to $500,000 per award. Please email your white papers to Ryan Turner, 315-330-4831, ryan.turner.10@us.af.mil. Works Cited: [1] C. a. Y. M. T. Szabo, "Post-mortem Analysis of Emergent Behavior in Complex Simulation Models," in SIGSIM-PADS '13, Montreal, Quebec, Canada, 2013. [2] J. Mogul, "Emergent (Mis)Behavior vs. Complex Software Systems," Hewlett-Packard Development Company, L.P., Palo Alto, CA, 2006. [3] R. a. P. F. R. Gore, "An Exploration-Based Taxonomy for Emergent Behavior Analysis In Simulations," in Proceedings of the 2007 Winter Simulation Conference, 2007. [4] H. V. D. a. R. V. Parunak, "Managing Emergent Behavior in Distributed Control Systems," in ISA-Tech, Anaheim, CA, 1997. [5] M. Clark, "A Study of Run-Time Assurance for Complex Cyber-Physical Systems," 2013. [6] J. G. A. D. C. W. L. S. a. M. G. Rivera, "An Architectural Description of the Simplex Architecture," Carnegie Mellon University, 1996. [7] L. Sha, "Using Simplicity to Control Complexity," IEEE Software, July/August 2001. [8] D. Brown, Limited Bandwidth Interactions with Bio-Inspired Swarms, 2014. [9] M. Ouimet, "Formal Software Verification: Model Checking and Theorem Proving," Embedded Systems Laboratory, MIT. [10] B. a. J. E. Chaki, "Model-Driven Verifying Compilation of Synchronous Distributed Applications," Carnegie Mellon University, Pittsburge, PA, 2014. [11] S. Chaki, Software Model Checking for Verifying Distributed Algorithms, 2013. [12] B. Chazelle, "Natural Algorithms and Influence Systems," Communications of the ACM, vol. 55, no. 12, 2012. [13] B. Chazelle, "The Dynamics of Influence Systems," arXiv, 2012. [14] P. a. C. R. Haglich, "Detecting Emergent Behaviors with Semi-Boolean Algebra," in AIAA Infotech, Atlanta, GA, 2010. [15] A. Kubik, "Towards a Formalization of Emergence," Journal of Artificial Life, vol. 9, pp. 41-65, 2003. [16] A. Platzer, "Logics of Dynamic Systems," in 27th Annual ACM/IEEE Symposium on Logic in Computer Science, 2012. [17] C. e. a. Rouff, "Formal Approaches to Intelligent Swarms," Proceedings of the 28th Annual NASA Goddard Software Engineering Workshop, 2003. [18] Y. M. B. L. L. a. C. S. Teo, "Formalization of Emergence in Multi-agent Systems," in SIGSIM-PADS '13, Montreal, Quebec, Canada, 2013. II. AWARD INFORMATION: Total funding for this BAA is approximately $43.2M. The anticipated funding to be obligated under this BAA is broken out by fiscal year as follows: FY 11 - $3.7M; FY 12 - $7.6M; FY 13 - $12.1M; FY 14 - $11.4M; and FY15 - $8.4M. Individual awards will not normally exceed 18 months with dollar amounts normally ranging between $100K to $1.0M per year. There is also the potential to make awards up to any dollar value. Awards of efforts as a result of this announcement will be in the form of contracts, grants or cooperative agreements depending upon the nature of the work proposed. 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. III. ELIGIBILITY INFORMATION: 1. ELIGIBLE APPLICANTS: All foreign allied participation is excluded at the prime contractor level. 2. COST SHARING OR MATCHING: Cost sharing is not a requirement. 3. 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. 4. EXECUTIVE COMPENSATION AND FIRST-TIER SUB-CONTRACT/SUB-RECIPIENT 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. Any grant or agreement award resulting from this announcement may contain the award term set forth in 2 CFR, Appendix A to Part 25 http://ecfr.gpoaccess.gov/cgi/t/text/text-idx?c=ecfr&sid=c55a4687d6faa13b137a26d0eb436edb&rgn=div5&view=text& node=2:1.1.1.41&idno=2#2:1.1.1.4.1.2.1.1 IV. APPLICATION AND SUBMISSION INFORMATION: 1. APPLICATION PACKAGE: THIS ANNOUNCEMENT CONSTITUTES THE ONLY SOLICITATION. WE ARE SOLICITING WHITE PAPERS ONLY. DO NOT SUBMIT A FORMAL PROPOSAL AT THIS TIME. 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. For additional information, a copy of the AFRL "Broad Agency Announcement (BAA): Guide for Industry," May 2012, may be accessed at: https://www.fbo.gov/index?s=opportunity&mode=form&id=e68f832abb3a7341bb7328547c0e19c0&tab =core&_cview=0 2. CONTENT AND FORM OF SUBMISSION: Offerors are required to submit 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: 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); Section B: Task Objective; and Section C: Technical Summary and Proposed Deliverables. Multiple white papers within the purview of this announcement may be submitted by each offeror. If the offeror wishes to restrict its white papers/proposals, they must be marked with the restrictive language stated in FAR 15.609(a) and (b). All white papers/proposals shall be double spaced with a font no smaller than 12 pitch. In addition, respondents are requested to provide their Commercial and Government Entity (CAGE) number, their Dun & Bradstreet (D&B) Data Universal Numbering System (DUNS) number, a fax number, an e-mail address, and reference BAA 10-01-RIKA with their submission. All responses to this announcement must be addressed to the technical POC, as discussed in paragraph six of this section. 3. SUBMISSION DATES AND TIMES: It is recommended that white papers be received by the following dates to maximize the possibility of award: FY 11 should be submitted by 1 Oct 2010; FY 12 by 3 Oct 2011; FY 13 by 1 Oct 2012; FY 14 by 1 Oct 2013 and; FY 15 by 1 Oct 2014 unless otherwise specified. White papers will be accepted until 2pm Eastern time on 30 Sep 2015, 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 2015. FORMAL PROPOSALS ARE NOT BEING REQUESTED AT THIS TIME. 4. FUNDING RESTRICTIONS: 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). 5. All Proposers should review the NATIONAL INDUSTRIAL SECURITY PROGRAM OPERATING MANUAL, (NISPOM), dated February 28, 2006 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. 6. OTHER SUBMISSION REQUIREMENTS: DO NOT send white papers to the Contracting Officer. All responses to this announcement must be addressed to ATTN: Mr. Michael Seifert, AFRL/RISB, 525 Brooks Road, Rome NY 13441-4505 Electronic submission to Michael.Seifert@us.af.mil will also be accepted. 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 315-330-4048 0730-1630 Monday-Friday 315-330-2961 Evenings and Weekends Email: vincent.guza@us.af.mil V. APPLICATION REVIEW INFORMATION: 1. CRITERIA: The following criteria, which are listed descending order of importance, 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: 1) The extent to which the offeror's approach demonstrates an understanding of the problem, an innovative and unique approach for the development and/or enhancement of the proposed technology, its application and appropriate levels of readiness at yearly levels. 2) Related Experience - The extent to which the offeror demonstrates relevant technology and domain knowledge. 3) Openness/Maturity of Solution - The extent to which existing capabilities and standards are leveraged and the relative maturity of the proposed technology in terms of reliability and robustness. 4) Reasonableness and Realism of Proposed Costs - The overall estimated costs should be clearly justified and appropriate for the technical complexity of the effort. No further evaluation criteria will be used in selecting white papers/proposals. Individual white paper/proposal evaluations will be evaluated against the evaluation criteria without regard to other white papers and proposals submitted under this BAA. 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. VI. AWARD ADMINISTRATION INFORMATION: 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 technical POC. 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 white papers will be contacted by the technical POC, referenced in Section VII of this announcement. Offerors can email the technical POC for status of their white paper/proposal no earlier than 45 days after submission. 2. ADMINISTRATIVE AND NATIONAL POLICY REQUIREMENTS: Depending on the work to be performed, the offeror may require a Top Secret facility clearance and safeguarding capability; therefore, personnel identified for assignment to a classified effort must be cleared for access to Top Secret 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) at http://www.dlis.dla.mil/jcp/ and have a legitimate business purpose may participate in this solicitation. For questions, contact DLIS on-line at http://www.dlis.dla.mil/jcp or at the DLA Logistics Information Service, 74 Washington Avenue North, Battle Creek, Michigan 49037-3084, and telephone number 1-800-352-3572. You must submit a copy of your approved DD Form 2345, Militarily Critical Technical Data Agreement, with your Proposal. 3. DATA 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. 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: Once a proposal has been selected for award, offerors will be given complete instructions on the submission process for the reports. VII. AGENCY CONTACTS: Questions of a technical nature shall be directed to the cognizant technical point of contact, as specified below: TPOC Name: Mr. Michael Seifert Telephone: (315) 330-4758 Email: Michael.Seifert@us.af.mil Questions of a contractual/business nature shall be directed to the cognizant contracting officer, as specified below: Name: Gail Marsh Telephone (315) 330-7518 Email: gail.marsh@us.af.mil The email 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 (Apr 2010) will be incorporated into all contracts awarded under this BAA. The AFRL Ombudsman is as follows: Ms. Barbara Gehrs AFRL/PK 1864 4th Street Building 15, Room 225 Wright-Patterson AFB OH 45433-7130 FAX: (937) 656-7321; Comm: (937) 904-4407 Email: barbara.gehrs@us.af.mil All responsible organizations may submit a white paper which shall be considered.
 

Web Link

FBO.gov Permalink
(https://www.fbo.gov/spg/USAF/AFMC/AFRLRRS/BAA-10-01-RIKA/listing.html)
 

Record

SN03442028-W 20140731/140729235555-80602888671a7b00af8791ab49949045 (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 |