Information Management-Enabled Sensor Tasking and Ad Hoc Control (ISTAC)

AMENDMENT 5 to BAA RIK-2014-0013 The purpose of this modification is to republish the original announcement, incorporating any previous modifications, pursuant to FAR 35.016(c). This republishing also includes the following highlighted changes: (a) Section I: Add information on Fundamental Research and Cloud Computing; (b) Section III: Updated to reflect current access requirements; (c) Section V.3: Delete Adequate Price Competition and renumber paragraphs; and (d) Section VI.1: updated proposal instructions. No other changes have been made. _____________________________ NAICS CODE: 541715 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: Information Management-enabled Sensor Tasking and Ad Hoc Control (ISTAC) BAA ANNOUNCEMENT TYPE: Initial announcement BAA NUMBER: BAA RIK-2014-0013 CATALOG OF FEDERAL DOMESTIC ASSISTANCE (CFDA) Number: 12.800 I. FUNDING OPPORTUNITY DESCRIPTION: The Information Directorate of the Air Force Research Laboratory (AFRL/RI), Rome Research Site, is soliciting white papers under this announcement for innovative technologies to enable the effective management of information for military operations in the tactical domain. AFRL/RI has been conducting research in the areas of tactical information dissemination and management. Resultant approaches have focused on the creation of services-based information management techniques. This research has led to the development of a series of information dissemination and management technologies focused on improved radio-based communications for resource constrained air/ground vehicle-based and dismounted tactical users. The continued development of innovative concepts and enhanced services that maximize the value of information to support the objectives of military theater operations is the primary focus of this BAA. Background: The AFRL/RISA Tactical Information Management group has been a leading innovator in in-mission information dissemination over tactical networks, advancing the state of the art from inefficient video broadcast (e.g., ROVER) to information products tailored to consumer predicates and resource availability. In a similar manner, ISTAC is using the AFRL/RI core competencies of information management, connectivity, and advanced computing to expand the near-real-time utility of tactical airborne sensors from traditional stove-piped, single operator control to shared access by multiple third party users in a disadvantaged network. The combined proficiency in these areas allows AFRL/RI to enhance the capability of advanced targeting pods (ATPs) not just for the pilot, but for multiple warfighters in the networked battlespace. The current tactical sensor control and tasking process is a highly synchronous air-ground activity that requires the pilot to coordinate with an off-board user and manually control the sensor. The lack of automation increases pilot burden and slows target prosecution due to the steps required to slew the sensor onto a requested coordinate. The result is suboptimal allocation of tactical sensors that have the opportunity to provide value to more than a single user at time. Requirement: A new consolidated program called Information Management (IM)-enabled Sensor Tasking and Ad hoc Control (ISTAC) has being started under this BAA. The goal of ISTAC is to provide third parties the ability to influence the tasking of airborne tactical sensors in order to satisfy their information needs without impacting the pilot operating the sensor or the primary mission of the airborne asset. ISTAC will develop and demonstrate a set of embedded information management software services and adaptable user interfaces that will automate ATP sensor tasking based on sensor availability and multiple consumer information needs, including aircrew mission objectives, navigation requirements, and off-board requests. Achieving the above stated goal of the ISTAC program requires addressing several significant technical challenges in the areas of deriving and prioritizing sensor tasking from mission information needs, and scheduling those tasks without ownership of the sensor. Providing this third party tasking capability also has operational challenges associated with sensor availability and ensuring non-interference with the primary mission. ISTAC is addressing these challenges through the following approach: - Conduct a capability analysis study where pilot ATP sensor utilization will be analyzed and on-board and off-board user requirements will be thoroughly reviewed. - Develop technologies to enable opportunistic task generation for an EO sensor. - Develop a mission-driven sensor task prioritization prototype using the results of the capability analysis and opportunistic task generation task. - Develop technologies that allow the synchronous tasking of sensors as well as closed-loop control, and integrate them into the task prioritization capability. Precise Position, Navigation and Timing (PNT) are critical to all air operations for reliable navigation and accurate weapons delivery. Today's military aircraft are dependent on GPS to provide PNT, and when GPS is denied or degraded, alternative methods are necessary. One such method is vision-aided navigation which uses imagery collected by an on-board sensor to localize and orient the platform. Advanced targeting pods provide a rapid and affordable means of integrating this capability onto existing platforms, and also as a test and demonstration platform for future aircraft. AFRL/RI has developed and demonstrated an open architecture for targeting pods that allows capability upgrades without modification to the Operation Flight Program (OFP) of the aircraft. Key to this technology is embedded information management services that decouple applications for the purposes of data exchange and security. Of interest to AFRL/RI is an extension of this technology to the application of vision-aided navigation and localization on targeting pods. The desired outcome is an architecture for vision-aided navigation algorithms on a pod that enables multiple algorithms to be hosted on the pod as "apps," supporting a variety of PNT needs and operating environments. The architecture will provide pod sensor tasking capabilities, access to other PNT data (e.g. GPS, Inertial Measurement Unit [IMU]), and pre-mission loading and in-mission management of reference data. The result is reduced time and cost for integrating vision-aided navigation algorithms into airborne platforms and improved PNT accuracy in GPS-denied or degraded environments. Offerors are encouraged to: - Investigate existing and emerging vision-aided navigation and localization algorithms and the infrastructure requirements to support information delivery (e.g. real-time imaging sensor streaming, efficient storage and query of reference information, system state data) to these algorithms. - Develop or extend vision-aided navigation and localization algorithms to incorporate active tasking of an imaging sensor. - Design an open standards-based architecture to support the multiple vision-aided navigation algorithms, and the necessary pilot vehicle interfaces to enable the selection and tuning of applications based on mission and environment constraints. - Implement the specified architecture by extending existing open standards-based application framework technologies and developing new technologies where gaps exist. - Integrate additional platform/pod data sources such as GPS/Inertial Navigation Systems (INS), Inertial Measurement Unit (IMU), and laser range finder. - Design and develop a simulation environment to evaluate the architecture and selected vision-aided navigation algorithms with relevant sensor data. - Design and develop mechanisms for efficiently representing, storing, and loading reference information pre-mission that are compatible with existing mission planning tools. The technical approach will be realized through several projects including two currently underway: Mission-driven Tasking of Information Producers (MTIP) and Vision-Aided Localization and navigation In Denied environments (VALID). 1) MTIP is an FY14-FY16 6.2 project that is using the approach detailed above to develop, integrate and evaluate the technologies necessary for ISTAC and demonstrate the resulting capability at TRL (4/5) with a hardwareinthe-loop simulation. 2) The VALID project is AFRL/RI's contribution to the AFRL Position, Navigation and Timing (PNT) Initiative. VALID is an FY15-FY17 project with a mixture of 6.2 and 6.3 funding that is building upon the MTIP project to design, develop and demonstrate an architecture for airborne platforms that enables visionaided navigation in GPS-denied or degraded environments. The goal of VALID is to enhance visionaided navigation by providing an open framework for a variety of visionaided navigation and localization algorithms tailored to mission constraints. VALID will also provide sensor monitoring and tasking capabilities, and premission loading and inmission management of reference data. AFRL/RI Rome will work closely with AFRL/RY Wright-Patterson AFB, OH and other PNT Initiative participants to integrate existing visionaided navigation capabilities. 3) The goal of IOE is demonstrate opportunistic sensor tasking and vision-aided navigation capabilities on an airborne platform in a relevant environment. Three main areas are of research and development are (1) non-interference-based opportunistic multi-user sensor tasking, (2) interaction with ISR collection management tools, and (3) an airborne test environment for experimentation and evaluation. FY18 Focus Area: VisNav SDK: Of interest to the government in FY18 and FY19 is the development of a Vision-Aided Navigation (VisNav) Software Development Kit. Please refer to Attachment 1 of this BAA for complete details. Security Classification: Software development will largely be UNCLASSIFIED but the domain specific activities may be up to TS/SCI. IMPORTANT NOTES REGARDING: FUNDAMENTAL RESEARCH. It is DoD policy that the publication of products of fundamental research will remain unrestricted to the maximum extent possible. National Security Decision Directive (NSDD) 189 defines fundamental research as follows: - Fundamental research' means basic and applied research in science and engineering, the results of which ordinarily are published and shared broadly within the scientific community, as distinguished from proprietary research and from industrial development, design, production, and product utilization, the results of which ordinarily are restricted for proprietary or national security reasons. As of the date of publication of this BAA, the Government cannot identify whether work proposed under this BAA may be considered fundamental research and may award both fundamental and non-fundamental research. Proposers should indicate in their proposal whether they believe the scope of the research included in their proposal is fundamental or not. While proposers should clearly explain the intended results of their research, the Government shall have sole discretion to select award instrument type and to negotiate all instrument terms and conditions with selectees. Appropriate clauses will be included in resultant awards for non-fundamental research to prescribe publication requirements and other restrictions, as appropriate. For certain research projects, it may be possible that although the research being performed by the awardee is restricted research, a sub-awardee may be conducting fundamental research. In those cases, it is the awardee's responsibility to explain in their proposal why its sub-awardee's effort is fundamental research. CLOUD COMPUTING. In accordance with DFARS Clause 252.239-7010, if the development proposed requires storage of Government, or Government-related data on the cloud, offerors need to ensure that the cloud service provider proposed has been granted Provisional Authorization by the Defense Information Systems Agency (DISA) at the level appropriate to the requirement. II. AWARD INFORMATION: 1. FUNDING: Total funding for this BAA is approximately $9.9M. The anticipated funding to be obligated under this BAA is broken out by fiscal year as follows: FY 15 - $1.0M FY 16 - $2.0M FY 17 - $2.0M FY 18 - $2.5M FY 19 - $2.4M Individual awards will not normally exceed 18 months with dollar amounts normally ranging from $250K to $1.5M per year. 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. 3. BAA TYPE: This is a two-step open broad agency announcement. This announcement constitutes the only solicitation. As STEP ONE - We are 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: 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. This includes both foreign ownership and foreign nationals as employees or subcontractors. b. Exceptions. 1. Fundamental Research. If the work to be performed is unclassified, fundamental research, this must be clearly identified in the white paper and/or proposal. See Part II, Section I for more details regarding Fundamental Research. Offerors should still identify any performance by foreign nationals at any level (prime contractor or subcontractor) in their proposals. Please specify the nationals' 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 any contract or assistance agreement issued as a result of this announcement 2. Foreign Ownership, Control or Influence (FOCI) companies who have mitigation plans/paperwork in place. Proof of approved mitigation documentation must be provided to the contracting office focal point, Gail E. Marsh, Contracting Officer, telephone +1 (555) 000-0000, or e-mail contact@example.gov prior to submitting a white paper and/or a proposal. For information on FOCI mitigation, contact the Defense Security Service. Additional details can be found at: http://www.dss.mil/isp/foci/foci_mitigation.html 3. Foreign Nationals as Employees or Subcontractors. Applicable to any effort not considered Fundamental Research. Offerors are responsible for ensuring that all employees and/or subcontractors who will work on a resulting contract are eligible to do so. Any employee who is not a U.S. citizen or a permanent resident will be restricted from working on any resultant contract unless prior approval of the Department of State or the Department of Commerce is obtained via a technical assistance agreement or an export license. Violations of these regulations can result in criminal or civil penalties. c. Information Regarding Non-US Citizens Assigned to this Project 1. 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. It also does not apply to dual citizens who possess US citizenship, to include Naturalized citizens. Any waivers to this requirement must be granted in writing by the Contracting Officer prior to providing access. Specific format for waiver request will be provided upon request to the Contracting Officer. The above requirements are in addition to any other contract requirements related to obtaining a Common Access Card (CAC). 2. For the purposes of Paragraph 1, it 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: a) Contractor employees who are U.S. citizens performing work under contracts, assistance instruments or other transactions awarded under this BAA. b) 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 (POC) 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 the following dates to maximize the possibility of award: FY15 by 31 Oct 2014 FY16 by 01 Jun 2015 FY17 by 31 Jan 2017 FY18 by 16 Mar 2018 FY19 by 29 Jun 2018 White papers will be accepted until 2 PM Eastern Time on 30 Sep 2019, 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 2019. 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. CONTENT AND FORMAT: Offerors are required to submit 2 copies of a 5-7 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) number, their Dun & Bradstreet (D&B) Data Universal Numbering System (DUNS) number, an e-mail address, and reference BAA RIK-2014-0013 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 J. Guza +1 (555) 000-0000 0730-1630 Monday-Friday +1 (555) 000-0000 Evenings and Weekends Email: contact@example.gov b. CLASSIFIED SUBMISSIONS. AFRL/RISA 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 mailed responses, unclassified/classified, to this announcement must be sent U.S. Postal Service, registered mail and addressed to AFRL/RISA, 525 Brooks Road, Rome NY 13441-4505, and reference BAA-RIK-2014-0013. Electronic submission of classified white paper information is NOT authorized. Questions can be directed to the cognizant technical point of contact listed in Section VII. Electronic submission of unclassified white papers to James Metzler (contact@example.gov) will also be accepted. Encrypt or password-protect all proprietary information prior to sending. Offerors are responsible to confirm receipt with the technical POC listed in Section VII. AFRL is not responsible for undelivered documents. If the white paper is sent via electronic transmission, one copy only is required. Any 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. 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. e. GOVERNMENT APPROVED ACCOUNTING SYSTEM: An offeror must have an 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 Instruction 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/ohrp. 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, 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. Related Experience - The extent to which the offeror demonstrates relevant technology and domain knowledge, c. 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 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: 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. FEDERAL AWARDEE PERFORMANCE AND INTEGRITY INFORMATION SYSTEM (FAPIIS) PUBLIC ACCESS: 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 applic...