BAA-AFRL-RQKS-2016-0003-Atch8.pdf
PDF 574 KB Posted
- Attached to
- Effective Sensor Technology Evaluations and Enabling Methodologies (ESTEEM) Federal contract opportunity
- Solicitation number
- BAA-AFRL-RQKS-2016-0003
About this file
Statement of Objectives - T.O. 0002
View the file
Other files for this federal contract opportunity
| File | Type | Posted |
|---|---|---|
| BAA-AFRL-RQKS-2016-0003-Amd2.pdf | ||
| BAA-AFRL-RQKS-2016-0003-Atch7-Amd1.pdf | ||
| BAA-AFRL-RQKS-2016-0003-Atch6-Amd1.pdf | ||
| BAA-AFRL-RQKS-2016-0003-Amd1.pdf | ||
| BAA-AFRL-RQKS-2016-0003-Atch8-Amd1.pdf | ||
| BAA-AFRL-RQKS-2016-0003-Atch5.pdf | ||
| BAA-AFRL-RQKS-2016-0003.pdf | ||
| BAA-AFRL-RQKS-2016-0003-Atch4.pdf | ||
| BAA-AFRL-RQKS-2016-0003-Atch3.pdf | ||
| BAA-AFRL-RQKS-2016-0003-Atch10.pdf | ||
| BAA-AFRL-RQKS-2016-0003-Atch1.pdf | ||
| BAA-AFRL-RQKS-2016-0003-Atch9.pdf | ||
| BAA-AFRL-RQKS-2016-0003-Atch7.pdf | ||
| BAA-AFRL-RQKS-2016-0003-Atch6.pdf | ||
| BAA-AFRL-RQKS-2016-0003-Atch2.pdf | ||
| BAA-AFRL-RQKS-2016-0003-ESTEEM-IndustryDay.pdf | ||
| BAA-AFRL-RQKS-2016-0003-Q As.pdf | ||
| BAA-AFRL-RQKS-2016-0003-ESTEEM-IndustryDay-Intro.pdf | ||
| BAA-AFRL-RQKS-2016-0003-ESTEEM-IndustryDay-Slides.pdf | ||
| BAA-AFRL-RQKS-2016-0003-IndustryDay.pdf | ||
| BAA-AFRL-RQKS-2016-0003-NOCA.pdf |
Show all 21
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
STATEMENT OF OBJECTIVES (SOO)
For The
EFFECTIVE SENSOR TECHNOLOGY
EVALUATIONS AND ENABLING
METHODOLOGIES (ESTEEM)
PROGRAM
SIGNAL SIMULATION & SIMULATION
METHODOLOGIES (S3M)
TASK ORDER (TO 0002)
AFRL/RYWD
8 February 2017
Attachment 8
TABLE OF CONTENTS
1. TECHNICAL OBJECTIVE
a. Assessment Data Processing Methodologies
b. Software Architecture
c. Requirements Evaluation Methodologies
d. Integrated Threat Scenario Development
2. GOVERNMENT FURNISHED PROPERTY (GFP)
3. BASE SUPPORT
4. PROGRAM MANAGEMENT
5. PERIOD OF PERFORMANCE
6. FUNDING PROFILE
7. DELIVERABLES
8. CONTRACT HOLIDAYS
9. SECURITY
10. SAFETY
1. TECHNICAL OBJECTIVE
The objective of this task is to develop/evolve research methodologies for aggregating the raw data products resulting from rapid assessments/evaluations (qualitative and quantitative) of advanced sensors and Electronic Warfare (EW) technologies/systems through Integrated Demonstrations and Applications Laboratory (IDAL). This effort will evolve the software architecture of the IDAL’s system of systems to keep up with emerging threats and technologies.
The S3M task order will provide for collaborative research that leverages the IDAL to better enable technology maturation and transition.
The contractor shall provide a proposal to address the above technical objectives and the following required tasks:
a. Assessment Data Processing Methodologies
The contractor shall develop/define/update methods for processing technology demonstration data products. These methods will provide aggregated information to be included in briefings and reports. Novel methods will be developed to process emerging cognitive technology assessment data products.
b. Software Architecture
The contractor shall investigate software architectures for rapidly evolving system of systems technology assessment capabilities. Software architectures include functions to integrate with instrumentation, complex databases and existing simulation software.
c. Requirements Evaluation Methodologies
The contractor shall develop the evaluation methodologies needed to assess/define requirements for evolving A2AD battlespace simulations. This will include RF focused, as well as integrated RF/IR/EO requirements.
d. Integrated Threat Scenario Development
The contractor shall investigate methodologies to develop threat scenarios to evolve/evaluate advanced sensors/EW technologies/systems through synthetic A2AD battlespace simulation.
The scenarios shall be up-to-date with the latest intelligence on the threats including representations of new or projected threats that are expected to exist in the timeframe to be analyzed. Where little hard data exists on the projected entities, the contractor shall recommend data to fill-in the gaps using the best information available.
2. GOVERNMENT FURNISHED PROPERTY (GFP)
GFP is not anticipated, but may be proposed.
3. BASE SUPPORT
Office space, laboratory environments, network access, and other accommodations in building 620, Wright-Patterson AFB will be provided. No additional base support is anticipated at this time.
4. PROGRAM MANAGEMENT
The contractor shall manage technical, schedule, and cost satisfaction of the program; plan, prepare, conduct, and document reviews; track CDRL satisfaction; and interface with the customer to assess performance satisfaction and re-plan the project as needed.
5. PERIOD OF PERFORMANCE
The technical effort shall be 18 months, with three additional months allotted for completion of the final report for a total of 21 months.
6. FUNDING PROFILE
Table 1: Funding Profile
FiscalYear FY17 FY18 FY19 FY20 FY21 TOTAL
3600 funds $0.225M $1.6M $1.075M $2.9 M
7. DELIVERABLES
Hardware: All hardware developed or procured during concept development, assessment, and demonstration of this program.
Hardware (Residual): residual hardware developed or purchased under this program.
Data Item
Data ACQ DOC Number
Title Frequency
A001 DI-MISC-80711A/T Scientific And Technical Reports – Final Report
One/R: Separate reports at the completion of each task order
A002 DI-FNCL-80331A/T Funds And Man-Hour Expenditure Report
Monthly
A003 DI-MGMT-81468/T Contract Funds Status Report (CFSR)
Quarterly
A004 DI-MGMT-80368A/T Status Report Monthly A005 DI-ADMN-81373/T Presentation Material As Required
8. CONTRACT HOLIDAYS
The Government will not be billed for holidays, except when services are required by the Government and are actually performed on a holiday.
The following days are contract holidays: New Year’s Day, Martin Luther King, Jr. Day, Presidents Day, Memorial Day, Independence Day, Labor Day, Columbus Day, Veteran’s Day, Thanksgiving Day, Christmas Day.
9. SECURITY
9.1 Program Security Requirements: Individuals must be US citizens and may be required to have SCI DCID 6/4 Top Secret Eligibility based on a SSBI/SBPR to work classified efforts.
Work will be required to be conducted within an accredited Special Access Program Facility (SAPF) and/or a Sensitive Compartmented Information Facility (SCIF). Specific security details and requirements will be outlined within future task orders. All classified efforts must be in compliance with the National Industrial Security Program Operating Manual (NISPOM). Other regulations/policy that may apply to this contract are JAFAN 6/0 (Revision 1); SAF/AAZ Memorandum “Air Force Special Access Programs Nomination Process (SAPNP)” (30 Sep 2013); USD(I) Memorandum, Special Access Programs Nomination Process (20 May 2013); the DoD Manual 5205.07, Volume 4 (10 Oct 2013); “Special Access Program (SAP) Security Manual”: Marking; SAF/AAZ Implementation Memorandum (7 Nov 2013); United States Air Force Security Marking Guide for SAPs (17 Jul 2011) and Revision 1 (16 Oct 2013); DoD SAPCO Memorandum, JAFAN 6/9 (23 Mar 04), Change 1 (20 Dec 05) and JAFAN 6/3 (15 Oct 2004); JAFAN 6/3 Implementation Guide, Version 1 (Sep 2006); DoD SAPCO Memorandum, Transition to the Risk Management Framework (RMF) (18 Dec 2013); Joint Special Access Program Implementation Guide (JSIG) (9 Oct 2013); DoD 8570.1-M, Information Assurance Workforce Improvement Program (24 Jan 2012 – incorporating Change 3); Intelligence Community Directives (ICD) 704 and 705; other applicable SCI regulations/policy; other applicable Security Classification Guides (SCG); and other applicable regulations/policy and subsequent revisions.
Provide the following information with proposal submission: CAGE Code, Organization Name, and Security Point of Contract (name/phone number).
9.2 The contractor shall implement the security program required to accomplish this effort. The contractor shall provide personnel with sufficient security clearance levels to be allowed access to the data necessary to execute the task order efforts. The contractor shall provide the secure facilities necessary to process the data generated under this task. The contractor shall have the ability to handle and store unclassified, proprietary, and classified information to perform this activity. The contractor shall provide the security required to perform this effort and shall implement special security requirements in accordance with classified attachments provided through government special project channels. The contractor shall ensure appropriate security protection methods are in place commensurate with the security level of the material provided to the contractor and generated by the contractor for performance of this effort. The contractor shall develop/implement an IDAL SWAT security action plan that provides measurable work tasks and schedule milestones to accomplish IDAL SWAT security objectives/requirements on a timely basis. The contractor shall provide weekly/monthly status/progress reviews against the IDAL SWAT security action plan baseline. The contractor shall coordinate security requirements/activities with the SWAT project engineer and the IDAL program manager.
9.3 General Operations Security (OPSEC) procedures, policies and awareness are required in an effort to reduce program vulnerability from successful adversary collection and exploitation of critical information. OPSEC will be applied throughout the life cycle of the contract. The Critical Information List (CIL) will be provided upon request by RYOY Information Protection Office.
While working on the government installation, OPSEC guidance will be provided by the RYOY Information Protection Office.
10. SAFETY
The contractor must comply with all Air Force, federal, state, and local safety and environmental regulations. Requires an approved Safety Plan (AFI 91-202 AFRL Sup 1) before any experiment may be conducted outside of a laboratory environment.
| TABLE OF CONTENTS |
| 1. TECHNICAL OBJECTIVE |
| 6. FUNDING PROFILE |
File details come from the government source that posted it. Updated .