Attch_1_-_MSCC_PWS_-_19JUL17.pdf

HEADQUARTERS AIR FORCE SPACE COMMAND

MODELING, SIMULATION, AND ANALYSIS (MS&A) FOR

SPACE AND CYBERSPACE CAPABILITIES

(MSCC)

PERFORMANCE WORK STATEMENT (PWS)

19 July 2017

Table of Contents MS&A FOR SPACE AND CYBERSPACE CAPABILITIES (MSCC), Contract PWS

1. PURPOSE

2. SCOPE

3. REQUIREMENTS/DESCRIPTION OF SERVICES

3.1 REQUIREMENT 1. Space‐Warfighter Integration MS&A

3.2 REQUIREMENT 2. Authoritative Information and Data (AID) Research, Collection, Management and Processes

3.3 REQUIREMENT 3. M&S R&D: M&S and Analytical Decision Support Tool Enhancements

3.4 REQUIREMENT 4: Analysis Support to HQ AFSPC

3.5 REQUIREMENT 5: Space and Cyberspace Analysis Resource Portal (SARP)

3.6 REQUIREMENT 6: MS&A Management and Integration

3.7 REQUIREMENT 7: AFSPC Virtual Analysis Capability

4. CONTRACTUAL REQUIREMENTS

5. SERVICE SUMMARY

6. GOVERNMENT‐FURNISHED PROPERTY/INFORMATION (GFP/GFI)

7. CONTRACTOR IDENTIFICATION

8. DOCUMENTATION AND DATA MANAGEMENT

9. PERSONNEL SECURITY

10. ACCESS TO GOVERNMENT PROPERTY AND FACILITIES

11. CONTRACTOR SPECIAL COMPARTMENTED INFORMATION FACILITY (SCIF)

12. SECURITY ISSUES

13. SYSTEM AND NETWORK AUTHORIZATION ACCESS REQUESTS

14. TRAVEL

15. MATERIALS AND OTHER DIRECT COSTS (ODCs)

16. TRAINING

17. DATA DELIVERABLES

Appendix A – Models/Tools Descriptions

Appendix B – Prioritized AFSPC Capabilities

The 14 Prioritized AFSPC Space Capabilities:

The 8 Prioritized AFSPC Cyberspace Capabilities:

Acronyms:

MS&A FOR SPACE AND CYBERSPACE CAPABILITIES (MSCC), Contract PWS

Name: MS&A FOR SPACE AND CYBERSPACE CAPABILITIES Organization: HQ AFSPC Address: 150 Vandenberg St, Ste 105, Peterson AFB, CO 80914-4570

Executive Summary

HQ AFSPC/A9XY and HQ AFSPC/A3Z are responsible for objective and responsive Modeling, Simulation, and Analysis (MS&A) and decision support for space and cyberspace analyses.

This contract represents technical and support requirements for space and cyberspace analysis to include engineering/engagement, mission, and theater/campaign MS&A.

1. PURPOSE

The overall purpose and objective of this contract is to.

2. SCOPE

Assist HQ AFSPC/A9XY and HQ AFSPC/A3Z with MS&A tools and analytical decision support tool development, modification, and analysis in support of space analyses and cyberspace.

This contract will require space and cyberspace knowledge coupled with MS&A expertise, analytical understanding, and software management acumen. The contractor must also possess experience with military weapon systems (e.g., aircraft, ship, tanks, and munitions) associated with Tactics, Techniques, and Procedures (TTPs); and Combatant Command (CCMD) operations at the tactical, operational, and strategic level. Finally, the contractor must also possess experience and skills in joint warfighting and joint/combined operations analysis (e.g., math, probability, operations research, and engineering).

The contractor may need to interface with other AFSPC units and organizations, other AF Major Commands (MAJCOMs), AF Research Laboratories (AFRL), Headquarters Air Force (HQ AF), other services (e.g., US Army and US Navy), United States Strategic Command (USSTRATCOM), US Cyber Command (USCYBERCOM), Department of Defense (DoD), National Aeronautics and Space Administration (NASA), National Reconnaissance Office (NRO), and non-DoD government and commercial space entities to accomplish this contract.

The MS&A tools and analytical decision support tools may support such activities as long-range planning, strategic analysis, force-mix studies, acquisition decision-making, requirements development and assessment, warfighter analysis, Analysis of Alternatives (AoAs), and/or operational missions.

3. REQUIREMENTS/DESCRIPTION OF SERVICES

The contractor shall provide MS&A research, development, and analytic support to HQ AFSPC/A9XY and HQ ASPC/A3Z through modification and development of space/cyberspace analysis and decision support tools as well as data to provide innovative space/cyberspace MS&A information research, management, and integration.

Enhancements to some MS&A and analytical decision support tools may require licenses from tool developers who are the current, official Air Force (AF) or DoD developer for their respective tool. It is the responsibility of the contractor to fully understand the current business/ industry/government status of each of these tools in order to expeditiously and effectively perform the work in this Performance Work Statement (PWS).

Analysis tools designated for improvements may range from non-proprietary to fully proprietary.

Each tool has individual conditions surrounding the accessibility of code, configuration management, and business arrangements. Strong MS&A and analytical support tool software development capabilities are required to meet the requirements in this PWS.

The contractor shall be certified on Day 1 of contract start in AF Web Administration, Agile Software Development, Scrum Master or equivalent, and possess expert abilities in Microsoft® products. The Contracting Officer Representative (COR) will confirm contractor certifications prior to contract start date.

3.1 REQUIREMENT 1. Space/Cyberspace-Joint Warfighter Integration

MS&A

The goal of the MS&A for Space and Cyberspace Capabilities effort is to support space/ cyberspace trade-space analysis as well as joint warfighter integration analysis efforts within the Space MS&A framework and analysis process. Figure 1 shows an example of space-joint warfighter integration MS&A organizational structure and Figure 2 highlights the responsibilities of each Space MS&A working group. A similar structure may also be used for Cyberspace

MS&A.

Figure 1. Basic Space-Joint Warfighter Integration MS&A Organizational Structure

PROJECT LEADS

STRATCOM/J81, NRO/SED/OEA, HAF/A9IS, AFSPC/A9XY, SMC/AD, SSDP

Warfighter Working Group

Threat/Space Control Working Group

Warfighter Analysis Working Group

Air

Land

Sea

CCMD

Threat Analysis Team (TAT)

Space Control Analysis Team (SCAT)

Space Engagement Analysis Team (SEAT)

Warfighter Mission Analysis Team (WMAT)

STRATCOM/J81

ACC; Army (CAA, TRAC, SMDC);

AFSPC/A3/A5; JFCC‐Space; Navy

(CNA, N81); CCMD/J3/J5;

CCMD Components

STAC/SSDP

• TAT: STRATCOM/J2, AFSPC/A2,

JFCC‐Space/J2, NGIC, ONI, NASIC, MSIC, STAC, CCMD/J2

• SCAT: AFSPC/A5S; AFSPC/A3Z;

SMC/SY; NRO; AF/A9IS

STRATCOM/J81

• SEAT: Program Offices/Labs (e.g., SMC, SNL)

• WMAT: AFSPC/A9XY; SMDC/G3;

Navy/CNA; CCMD Components

• WCAT: HAF/A9F/A9IS (STORM);

AFLCMC/EZJ (THUNDER)

Collaboration Key to Success

Integration Product Team (IPT)

RED = Working Group Lead

ORGANIZATION LEADS

STRATCOM/J8, NRO/SED, HAF/DA9, AFSPC/A5/8/9, SMC/CV, SSDP

JSDTF

Space

Cyber Warfighter Campaign Analysis Team (WCAT)

Figure 2. Space-Joint Warfighter Integration MS&A Organizational Responsibilities

In addition to the organizational structure, the contractor shall support the basic Space MS&A warfighter analysis process highlighted in Figure 3. Each step in the analysis process is clearly labeled and the contractor shall support a few of the key steps in this process. Cyberspace MS&A will follow an identical process.

Figure 3. Basic Space-Joint WarfighterMS&A Process

Working Group Responsibilities

Project Leads • Guide analysis effort; Manage Expectations; Provide results to STRATCOM, AFSPC, SMC, & AF leadership

Warfighter Working Group (WWG)

• Develop Joint Mission Threads (JMTs) for AF, Army, Navy, National core functions/missions; Determine Space Touch Points (STPs) for selected JMTs; Provide CONOPs and CONEMPS; Address Space Ops issues;; Responsible for Influence Diagrams

Space Control Working Group (SCWG)

• TAT: Identify/Define Threats to US Space Capabilities; Assist SCWG in performing Space Control analysis

• SCAT: Evaluate/Assess the capabilities of Enemy Offensive Space Control capabilities against Space Capabilities used by US forces; Evaluate/Assess US Defensive Space Control capabilities

Warfighter Analysis Working Group

(WAWG)

• SEAT: Based on Scenario & CONOPS/CONEMPS, convert System Specs (Space Measures of Performance (MOPs)) into System effectiveness values (Space Measures of Effectiveness (MOEs)) [Space System Analysis Team (SSAT)]

• WMAT: For selected scenarios JMT, & Influence Diagram convert Space MOEs into Warfighter MOEs (i.e., Mission Metrics)

• WCAT: Gather data/info on existing Campaign‐Level models; Provide study leadership process & selection of appropriate campaign‐level models; Inject MAWG results into campaign analysis; Convert Warfighter MOEs into Warfighter Measures of Outcome (MOOs) (i.e., Campaign Metrics)

Over the past five years, HQ AFSPC/A9XY has completed several space-joint warfighter integration efforts in support of AFSPC planning, AoAs, and requirements development. The contractor shall support the following key tasks identified in Figure 3:

Develop Joint Mission Threads (JMTs) which describe the key steps in a warfighting operation. (Step B) Insert space/cyberspace touch points (Step C) into the JMTs which lead to detailed Influence

Diagrams that can be modeled using approved analysis tools. (Step D) Perform engagement-level analysis to convert Space MOPs into Space MOEs (Step E) Develop/modify/execute mission-level analysis tools to emulate the Influence Diagram with sufficient fidelity to understand the impact of space/cyberspace capabilities on warfighter operations. Key analysis tools may include the System Effectiveness Analysis Simulation (SEAS), the Advanced Framework for Simulation, Integration and Modeling (AFSIM), and Excel-based macros. (Step F)

Develop/modify/execute campaign-level analysis tools to emulate the mission-level analysis results with sufficient fidelity to understand the impact of space/cyberspace capabilities on warfighter operations. (Step G) Key analysis tools may include the Synthetic Theater Operations Research Model (STORM) and THUNDER (not an acronym).

Identify the threats to US/Allied space capabilities (Step H) and perform space control analysis to determine the loss/degrade in space capabilities (Step I)

In addition to the Space-Joint Warfighter Integration MS&A Process, the contractor shall support the space assessment analysis efforts led by HQ AFSPC/A3Z which examines the impact of space capabilities on Space Situational Awareness (SSA) and Space Control (SC).

3.1.1 Subtask 1 - Warfighter Working Group (WWG) Support.

For Space-Joint Warfighter Integration MS&A, the contractor shall perform the tasks listed below in support of the WWG. For Cyberspace-Joint Warfighter Integration MS&A, the contractor shall perform identical tasks for an equivalent cyberspace WWG.

3.1.1.1 Gather and analyze the basic scenario and operational mission data based on the overall scenario approved by AFSPC/A5/8/9. The contractor shall also gather potential data/information on doctrine and TTPdocuments as well as CCMD and Joint Staff guidance.

3.1.1.2 Develop JMTs and Influence Diagrams in the form of PowerPoint slide with note pages. The JMTs and Influence Diagrams shall include all data sources.

3.1.1.3 Interface with key operational warfighting organizations such as Air Combat Command (ACC) [Air Ops], US Army/G3 and Space and Missile Defense Center (SMDC) [Land Ops], US Navy/N3 [Fleet Ops], CCMD/J3/J5 [Joint Ops], USSTRATCOM/J8 [Strategic Ops], Missile Defense Agency (MDA) [Missile Defense Ops]. The CCMD/J3/J5 provides the Operations Plan (OPLAN) associated with the ISC as well as key information on the US/Friendly strategic objectives and apportionment/allocation/operations of key assets (including space) to meet the strategic objectives.

3.1.1.4 Interface with organizations such as ACC, US Army/G3 and (SMDC), US Navy/N3, and CCMD/J3/J5 [Joint Ops] to develop JMTs and Influence Diagrams.

3.1.1.5 Inject Operations Plan (OPLAN), Concepts of Operation (CONOPS), Concepts of Employment (CONEMPS), and TTP data/information into the overall scenario approved by

AFSPC (e.g., Integrated Security Construct.

3.1.1.6 Interface with other space MS&A working groups to (1) ensure JMTs and Influence Diagrams provided meet MS&A needs and (2) modify JMTs and Influence Diagrams based on other working group inputs.

3.1.1.7 Populate the Space and Cyberspace Analysis Resource Portal (SARP) with JMTs, Influence Diagrams, OPLAN, CONOPS, CONEMPS, and TTPs.

Deliverables:

Contractor shall deliver JMTs and Influence Diagrams as well as US/Friendly air, land, and maritime CONOPS/CONEMPS and Ground Rules and Assumptions (GR&A) in the form of PowerPoint slides with note pages. (CDRL A100: Technical Report – Study/Services)

Contractor shall also deliver a Monthly Status Report (MSR) in the form of a Word document highlighting activities completed in the previous month and project activities in the upcoming month. (CDRL A048: Contractor’s Progress Status and Management Report)

3.1.2 Subtask 2 - Space Control Working Group (SCWG) Support.

3.1.2.1 Threat Analysis Team (TAT) Support.

For Space-Joint Warfighter Integration MS&A, the contractor shall perform the tasks listed below in support of the Threat Working Group (TWG). For Cyberspace-Joint Warfighter Integration MS&A, the contractor shall perform identical tasks for an equivalent cyberspace TWG.

3.1.2.1.1 Review basic scenario and operational mission data/information based on the overall scenario provided by AFSPC to understand operational environment.

3.1.2.1.2 Interface with key intelligence agencies such as USSTRATCOM/J2, AFSPC/A2, JFCC-Space/J2, National Air and Space Intelligence Center (NASIC), Missile and Space Intelligence Center (MSIC), and CCMD/J2. The CCMD/J2 provides key information on the enemy strategic objectives and apportionment/allocation/ operations of key space assets to meet the strategic objectives.

3.1.2.1.3 Interface with other space MS&A working groups to ensure threat data/ information provided meets MS&A needs.

3.1.2.1.4 Assist with identifying/defining potential threats to US/friendly space capabilities in all regimes (e.g., Geostationary Earth Orbit (GEO), Low Earth Orbit (LEO), and Medium Earth Orbit (MEO)) at the Top Secret (TS) level or below.

3.1.2.1.5 Assist with defining potential enemy space control CONOPS and CONEMPS.

3.1.2.1.6 Populate Space and Cyberspace Analysis Resource Portal (SARP) with space threat data/information. SARP is defined in section 3.5 Requirement 5.

Deliverables:

Contractor shall deliver a description of potential threats to US/Friendly space assets, as well as threat CONOPS/CONEMPS and Ground Rules and Assumptions (GR&A) in the form of PowerPoint slides with note pages. (CDRL A100: Technical Report – Study/Services)

Contractor shall deliver a MSR in the form of a Word document highlighting activities completed in the previous month and project activities in the upcoming month. (CDRL A048: Contractor’s Progress Status and Management Report)

3.1.2.2 Space Control Analysis Team (SCAT) Support.

in support of the SCWG. For cyberspace MS&A, the contractor shall perform identical tasks for an equivalent Cyberspace Control Working Group (CCWG).

3.1.2.2.1 Gather and analyze the basic scenario and operational mission data based on the overall scenario approved by AFSPC to understand the threats to US/Friendly space capabilities.

3.1.2.2.2 For space MS&A efforts, interface with the TAT and WWG to gather data/information on potential enemy Offensive Space Control (OSC) capabilities to include CONOPS, CONEMPS, and TTPs. For cyberspace MS&A efforts, interface with the TAT.

3.1.2.2.3 Interface with key space control organizations such as the Space Security and Defense Program (SSDP), HQ AFSPC/A5S, HQ AFSPC/A3Z, Space Threat Analysis Center (STAC), SMC/SY, and the NRO. These organizations provide key insights into space control capabilities, CONOPS, CONEMPS, and analysis tools/efforts required to understand enemy OSC capabilities as well as US/Friendly Defensive Space Control (DSC) capabilities.

3.1.2.2.4 Develop analysis tools and conduct analyses of both reversible and irreversible threats to US/Friendly space systems to determine probabilities the space capabilities are available to support warfighting operations.

3.1.2.2.5 Populate the SARP with space control analysis tools/data and analysis results.

Deliverables:

Contractor shall deliver baseline enemy OSC results (no US/Friendly OSC capability), enemy OSC results (with US/Friendly OSC capabilities), and space control analysis tools as well as Ground Rules and Assumptions (GR&A) in the form of PowerPoint slides with note pages. (CDRL A100: Technical Report – Study/Services) completed in the previous month and project activities in the upcoming month. (CDRL A048: Contractor’s Progress Status and Management Report)

3.1.3 Subtask 3 - Warfighter Analysis Working Group (WAWG) Support.

in support of the Space Engagement Analysis Team (SEAT), the Warfighter Mission Analysis Team (WMAT), and the Warfighter Campaign Analysis Team (WCAT). For cyberspace MS&A, the contractor shall perform identical tasks for an equivalent Cyberspace Analysis Working Group (CAWG).

3.1.3.1 Space Engagement Analysis Team (SEAT) Tasks.

3.1.3.1.1 Gather and analyze the basic scenario and operational mission data based on the overall scenario approved by AFSPC to understand how Space Force Enhancement (SFE) capabilities support warfighter missions.

3.1.3.1.2 For the Program of Record (PoR) defined by the WWG, convert space Measures of Performance (MOPs) into Space Measures of Effectiveness (MOEs). Typical Space MOPs include specifications such as orbital parameters, Field of regard (FOR), and Field of View (FOV). Examples of Space MOEs are probability of launch detection, launch point accuracy, impact point prediction, and navigation accuracy. (CDRL A100: : Technical Report- Study/Services (MOP/MOE mapping))

3.1.3.1.3 Interface with key SFE organizations such as the Space and Missile Systems Center (SMC), Sandia National Labs, the National Oceanic and Atmospheric Administration (NOAA), the National Reconnaissance Office (NRO), and NASA. These organizations provide key insights into space capabilities, CONOPS, CONEMPS, and MS&A tools/efforts required to understand the US/Friendly capabilities delivered to the warfighter.

3.1.3.1.4 Perform space MS&A tool assessments based on potential engineering/ engagement-level tools provided by the key SFE organizations. This is NOT a formal MS&A Verification and Validation (V&V), but an assessment on whether the proposed MS&A tools are adequate to support the Space MS&A effort. The AoA handbook process for model accreditation will be helpful in completing the assessments. (CDRL A100: : Technical Report- Study/Services (Tool assessment summary))

3.1.3.1.5 Populate the SARP with space system analysis tools/data as well as MOP-to-MOE analysis results.

Deliverables:

Contractor shall deliver baseline enemy OSC results (no US/Friendly DSC capabilities), enemy OSC results (with US/Friendly DSC capabilities), and space control analysis tools as well as Ground Rules and Assumptions (GR&A) in the form of PowerPoint slides with note pages. (CDRL A100: Technical Report – Study/Services) completed in the previous month and project activities in the upcoming month. (CDRL A048:

Contractor’s Progress Status and Management Report)

3.1.3.2 Warfighter Mission Analysis Team (WMAT) Tasks.

3.1.3.2.1 Gather and analyze the basic scenario and operational mission data based on the overall scenario approved by AFSPC to understand the basic warfighter missions (e.g., Offensive Counter-Air) and space touch points.

3.1.3.2.2 Interface with key organizations performing warfighting mission-level space MS&A such as US Army SMDC and US Navy Center for Analysis (CNA) for land and maritime missions, respectively.

3.1.3.2.3 Perform MS&A tool assessments of potential mission-level MS&A tools. This is NOT a formal MS&A V&V, but an assessment on whether the proposed MS&A tools are adequate to support the Space MS&A effort. The Air Force Office of Aerospace Studies (OAS) AoA handbook process for model accreditation will be helpful in completing the assessments.

3.1.3.2.4 For the Space MOEs provided by the SEAT, convert Space MOEs into Warfighter MOEs. Examples of Space MOEs are probability of launch detection, launch point accuracy, impact point prediction, and navigation accuracy. Examples of Warfighter MOEs are number of Transporters, Erectors, Launchers (TELs) killed over time and probability of target destruction. (CDRL A100: Technical Report-Study/Services (MOE/Warfighter mapping))

3.1.3.2.5 Populate the SARP with mission-level analysis tools, data, and analysis results.

Deliverables:

Contractor shall deliver an assessment of available mission-level MS&A tools, the mission-level analysis Design of Experiments (DoE), and mission-level analysis results as well as appropriate GR&As (CDRL A100: Technical Report – Study/Services)

3.1.3.3 Warfighter Campaign Analysis Team (WCAT) Support.

3.1.3.3.1 Gather and analyze the basic scenario and operational mission data based on the overall scenario approved by AFSPC to understand how SFE capabilities support warfighter campaign-level operations.

3.1.3.3.2 Interface with key organizations performing warfighting campaign-level space MS&A such as HQ AF/A9 and LCMC/EZJ to expand warfighter space impact analyses from the mission to the campaign-level.

3.1.3.3.3 Perform MS&A tool assessments of potential campaign-level MS&A tools. This is NOT a formal MS&A V&V, but an assessment on whether the proposed MS&A tools are adequate to support the Space MS&A effort. The AoA handbook process for model accreditation will be helpful in completing the assessments. (CDRL A100: Technical Report- Study/Services (Tool Assessment summary))

3.1.3.3.4 For the warfighter MOEs provided by the MAWG WMAT, convert Warfighter MOEs into Warfighter Measures of Outcome (MOOs). Examples of Warfighter MOEs are number of TELs killed over time and probability of target destruction. Examples of Warfighter MOOs are time to achieve air/maritime superiority and probability enemy/US forces achieve objectives.

(CDRL A100: Technical Report-Study/Services (Warfighter MOE to Warfighter MOO mapping))

3.1.3.3.5 Populate the SARP with campaign-level analysis tools, data, and analysis results.

Deliverables:

Contractor shall deliver an assessment of available campaign-level MS&A tools, the campaign-level analysis DoE, and campaign-level analysis results as well as appropriate GR&As. (CDRL A100: Technical Report – Study/Services)

3.2 REQUIREMENT 2. Authoritative Information and Data (AID) Research, Collection, Management and Processes

Standardize space and cyberspace information and data to support M&S efforts, and make the data available through a repository which is important to the AFSPC community. Repository must have an operational availability of > 90%. Authoritative information and data includes, but not limited to, authoritative space, cyberspace and missile system engineering data, metadata on authoritative space, cyberspace and missile data sources, Astrodynamic Standards (AS) Software, M&S metadata, M&S input and output files, space/missile data source metadata, data files used to support wargames, exercises and experimentation, system performance data, system historical data, and documents to include system fact sheets, studies, presentations, white papers, Analysis of Alternatives (AoA). Repeatable and sustainable data research and collection from various offices and organizations are needed to meet this requirement.

3.2.1 The Contractor shall establish and develop agreements, documents and processes to enable accessibility of information from other data sources through the Space and Cyberspace Analysis Resource Portal (SARP) as reference/repository information. Examples of these are Memorandums of Understanding, Data Exchange Agreements, Service Level Agreements.

Manage, maintain and document the agreements in a single document called SARP Data Release Agreements. Develop new and maintain and enhance current SARP data-sharing processes with other DoD agencies and organizations. (CDRL A100: Technical Report- Study/Services)

3.2.2 The Contractor shall identify, research, collect, analyze, validate and verify, and populate the classified and unclassified SARP databases with authoritative information and data. The following are types of AID that could be collected: space and cyberspace system engineering data (ground, air, space, cyberspace, sensor, networks), metadata on authoritative space and cyberspace data sources, M&S metadata, model documentation, M&S V&V and Accreditation reports, M&S input and output files, space data source metadata data files used to support wargames, exercises and experimentation, system performance data, system historical data, AS software, and documents to include system fact sheets, studies, presentations, white papers, AoAs.

3.2.3 The Contractor shall populate the appropriate SARP databases according to data classification level. Keeping SARP data current is a key requirement with respect to the AS software and model and data source metadata. This task requires contact with government-provided model/data source managers and AID Points of Contact to facilitate information being updated on SARP. The Contractor shall ensure the current AS software is available to SARP requestors. This task encompasses all data population of SARP and its sub-sites. (CDRL A045:

Computer Software Product End Items)

3.2.4 Contractor shall deliver a MSR in the form of a Word document highlighting activities

3.3 REQUIREMENT 3. M&S R&D: M&S and Analytical Decision Support Tool Enhancements

The Air Force defines its missions through 12 Service Core Functions: Air Superiority, Building Partnerships, Global Precision Attack, Personnel Recovery, Nuclear Deterrence Operations, Special Operations, Rapid Global Mobility, Agile Combat Support, Global Integrated Intelligence, Surveillance, and Reconnaissance (ISR), Command and Control, Cyberspace Superiority, and Space Superiority. The Secretary of the Air Force designated the AFSPC Commander, via Air Force Policy Memorandum, 13 August 2013, the Core Function Lead (CFLI) for the Space and Cyberspace Superiority core functions. In this role, the AFSPC Commander is responsible for defining Service-wide investments supporting these Core Functions, and for establishing a desired end state in the Core Function Support Plans (CFSPs) to guide AF investment decisions. While all capabilities fielded within a Core Function Master Plan (CFMP) are important to the AF, the CFLs evaluate current military doctrine, operations, and policy and potential threats to prioritize capabilities within the core functions.

Prioritized capabilities then guide the strategic planning, investment decisions, and development and fielding of space and cyberspace systems to include analytical decision support tools, models and simulations. The enhancements to tools each year will address one or more of the space and/or cyberspace priorities listed in Appendix B.

3.3.1 Subtask 1 – M&S and Decision Support Tool Development.

The Contractor shall update, modify, and develop M&S and decision support tools that represent space systems (including cyberspace) and support the Space, Cyberspace, and DoD analysis communities. The M&S models and analytical decision support tools may support such activities as warfighter analysis, long-range planning, strategic analysis, force-mix studies, acquisition decision-making, requirements development and assessment, Military Utility Analysis (MUA), AoAs, and/or operational missions. Development of modules/components must be performed in collaboration with tool managers, AFSPC stakeholders and associated model development contractors.

In support of model and decision support tool updates, modifications, and development, the contractor shall develop and implement government-accepted improvements using the contractor’s established review processes. HQ AFSPC will pre-coordinate with the contractor to ensure feasibility of the work and timeliness before each task is funded.

Specific tasks, with government coordination and approval, may involve the development and enhancement of a number of M&S and analytical decision support tools. The specific models/tools considered for enhancements will change over time based on future capabilities and requirements. The following models/tools (Appendix A) are candidates for modification each year and can change over time based on capabilities, analysis requirements, and AFSPC Space and Cyberspace Priorities (priorities described in Appendix B):

Extended Air Defense Simulation (EADSIM) GPS Interface and Navigation Tool (GIANT) Observation System Simulation Experiment (OSSE) Tool (OSSET) Satellite Trajectory and Attitude Kinematic (SATRAK) Space and Cyberspace Analysis Resource Portal (SARP) Space Brawler Standardized Astrodynamic Algorithm (SAA) Library Synthetic Theatre Operations Research Model (STORM) System Effectiveness Analysis Simulation (SEAS) Threat, Vulnerability, Timeline (TVT)

Systems Tool Kit (STK) Modeling, Simulation and Analysis Framework (MSAF) Simulation in Python for Space Entities (SPySE)

An overview summary of each model/tool is provided in Appendix A.

3.3.1.1 The Contractor shall provide an M&S Tool Work Plan each year that outlines the specific enhancements that will be made to the tool. The plan shall identify the schedule for key activities to accomplish the enhancements. (CDRL A099: Technical and Management Work Plan)

3.3.1.2 The Contractor shall provide a Software Design Document (SDD) which will describe the software development approach to produce the desired tool functionality and ultimately lead to new software code and documentation. If changes to the software design occur during the development process, the SDD will be updated to include these design changes. (CDRL A029:

Software Design Description (SDD))

3.3.1.3 The Contractor shall provide a Software Test Plan prior to the start of the development of the tool enhancement which will outline how the tool will be tested. (CDRL A032: Software Test Plan)

3.3.1.4 The Contractor shall develop the tools using agile methodologies and provide interim builds of the software for evaluation by the government. The Work Plan will outline the specific milestones for those interim deliverables. Enhancements will be made to the tool’s capabilities as described in Appendix A and AFSPC Space and Cyberspace Priorities described in Appendix B.(CDRL 045: Computer Software Product End Items)

3.3.1.5 The Contractor shall provide a Software Version Description (SVD) document for each interim and final release of the tool. (CDRL A036: Software Version Description (SVD))

3.3.1.6 The Contractor shall deliver the final software with a statement that the enhancement will be included in the tool’s software baseline. (CDRL A019: Computer Program End Item Documentation)

3.3.1.7 The Contractor shall provide a Functional Test Report that describes results of testing, outstanding issues and future enhancements at the conclusion of development of an enhancement. (CDRL A034: Software Test Report (STR))

3.3.1.8 The Contractor shall deliver software documentation as directed by each TO. These will include User Guides, Analyst Manuals, Programmers Guide, Deployment Plans, Requirements Documents, CONOPS, Configuration Management Plans, and Database Dictionaries. (CDRL A037: Software User Manual (SUM); A027: Software Requirements Specifications (SRA); A031: Database Design Description (DBDD); A041: Software Programmer’s Guide and A100: Technical Report-Study/Services)

3.3.2 Subtask 2 - M&S and Decision Support Tool Support

3.3.2.1 The Contractor shall assist AFSPC in the development of scenario files, input files, database files to be used by the tool. In addition, assist AFSPC in validating and verifying the output data by exercising the tool using the developed scenario files, input files, and database files. (CDRL A0024: Operational Concept Description (OCD))

3.3.2.2 The Contractor shall provide training on the tool enhancements to showcase the new model functionality. (CDRL A016: Training Materials)

3.3.2.3 The Contractor shall support User Group and/or Configuration Control Boards (CCBs) associated with the tool, typically one meeting per year for approximately four models of interest per year.

3.3.2.4 Contractor shall deliver a MSR in the form of a Word document highlighting activities

3.4 Requirement 4: Analysis Support to HQ AFSPC

In order to meet analysis requirements, the Contractor shall support AFSPC with the following steps to conduct MUA/AoA using the appropriate analysis tools some of which are identified in Appendix A in accordance with the processes as defined by the government. Participation in working groups may be required in support of the MUA/AoA.

3.4.1 Subtask 1 – MUA Planning

3.4.1.1 Upon execution of a study, the Contractor will provide a study work plan. The plan shall identify the schedule for key activities to accomplish the analysis. (CDRL A099: Technical and Management Work Plan)

3.4.1.2 The contractor shall develop an effectiveness analysis process focused on understanding how the space/cyberspace capabilities under investigation in the AoA are used by the warfighter to successfully complete operational missions. The analysis process must connect the technical capabilities under investigation to warfighting metrics such as mission success and time to complete objectives. The contractor will document the approach in a MUA Concept document (CDRL A100: Technical Report-Study/Services).

3.4.1.3 The contractor shall gather and analyze basic scenario and operational capability data/information on the potential operational warfighting scenario. Recommend analysis tools suitable for executing the analysis plan to include applicable justification as well as DoE to execute the analysis effort. The contractor will document the information in a MUA Plan (CDRL A100: Technical Report-Study/Services).

3.4.2 Subtask 2 – MUA Execution

3.4.2.1 The contractor shall assist in developing and executing analysis tools identified in the analysis plan to capture metrics such as the impact of space/cyberspace capabilities on mission success and time to complete objectives. The Contractor shall execute the MUA Plan using the identified tools and methodologies identified in MUA Plan. The Contractor shall provide results of the analysis and the data repository (input files / output files /scenario files, model files).

(CDRL A045: Computer Software Product End Items).

3.4.2.2 Populate the SARP with analysis tools and data.

3.4.3 Subtask 3 – MUA Results

3.4.3.1 The Contractor shall provide a Study Analysis Report that describes the results of the analysis. Based on senior leadership, working group lead, and Action Officer (AO) inputs, adjust the analysis products, briefings and reports, while maintaining focus on the MUA/AoA tasking and military utility. (CDRL A100: Technical Report-Study/Services).

3.4.3.2 Populate the SARP with mission-level analysis tools, data and analysis results.

3.4.3.3 The Contractor shall include a summary of the analysis work completed by the 15th of each month. At a minimum, the MSR will summarize all task/requirement work in the previous month, work to be accomplished in the next month and any issues. The contractor shall provide actual and projected cost information using the government-provided format. (CDRL A048: Contractor’s Progress Status and Management Report).

3.5 Requirement 5: Space and Cyberspace Analysis Resource Portal (SARP).

The SARP is a webpage/website currently residing on the Peterson AFB Non-secure Internet Protocol Router Network (NIPRNet) and Secure Internet Protocol Router Network (SIPRNet) and hosted by the 21st Communications Squadron (COMM SQ). It is a Microsoft Sequel (SQL) Server database with multiple supporting software packages such as Information Internet Services (IIS) and Simple Mail Transfer Protocol (SMTP) services. It was developed in Microsoft Visual Studio with a NET framework. Hosting of SARP on the Joint Worldwide Intelligence Communications System (JWICS) is also envisioned.

3.5.1 Subtask 1 – SARP Maintenance

3.5.1.1 Contractor shall perform SARP maintenance tasks according to Information Technology (IT) industry best-practices and AF network policies and procedures. Work with AFagencies to ensure SARP and its associated sub-sites are operational in accordance with service-level agreements established for the maintenance of SARP, to include but not limited to, web servers, database servers, SMTP email relay, network connections on the NIPRNet, SIPRNet, and JWICS. Assist these organizations in maintaining and upgrading hardware and software supporting SARP. The contractor shall perform IAT Level I administrative and security functions on all supported networks (NIPRNet, SIPRNet and JWICS) and maintain certifications IAW DoD 8570.01-M, Tables AP3.T1. The contractor shall support user/group configuration, Uniform Resource Locator (URL) checking, site monitoring and email monitoring. Issues will be identified and reported in the MSR. (CDRL A048: Contractor’s Progress Status and Management Report)

3.5.2 Subtask 2 – SARP Operations and Help Desk

3.5.2.1 Contractor shall perform SARP helpdesk support (i.e., providing access, new accounts, unlocking accounts and other helpdesk-related issues) according to IT industry best-practices and provided AF network policies and procedures. In addition, the SARP helpdesk support, the SARP administrator is required to obtain Cyber Security Liaison (CSL) administration rights to ensure success of this requirement. The help desk support will provide support to users using SARP and its subsites. Support will be documented in the MSR.

3.5.3 Subtask 3 - SARP Enhancements

Contractor shall make enhancements and/or add new functionality to SARP and/or its sub sites.

Enhancements will require full documentation and testing as described below.

3.5.3.1 Contractor shall provide an annual SARP Tool Work Plan that outlines the specific enhancements that will be made to SARP. The plan shall identify the schedule for key activities to accomplish the enhancements. (CDRL A099: Technical and Management Work Plan)

3.5.3.2 Contractor shall provide a Software Design Description (SDD) describing the software development approach to produce the desired functionality and ultimately lead to new software code and documentation. If changes to the software design occur during the development process, the SDD will be updated to include these design changes. (CDRL A029: Software Design Description (SDD))

3.5.3.3 Contractor shall provide a Functional Test Plan prior to start of the development of the SARP enhancements which will outline how SARP will be tested. (CDRL A032: Software Test Plan)

3.5.3.4 The Contractor shall develop SARP using agile methodologies and provide interim builds of the software for evaluation by the government. The Work Plan will outline the specific milestones for those interim deliverables. (CDRL A045: Computer Software Product End Items)

3.5.3.5 Contractor shall provide a Software Version Description (SVD) document for each interim and final release of SARP. (CDRL A036: Software Version Description (SVD))

3.5.3.6 The Contractor shall deliver the final software with a statement that the enhancement will be included in the tool’s software baseline. (CDRL A019: Computer Program End Item Documentation)

3.5.3.7 Contractor shall provide a Functional Test Report that describes results of testing, outstanding issues, and future enhancements at the conclusion of development of an enhancement. (CDRL A034: Software Test Report (STR))

3.5.3.8 Contractor shall deliver software documentation for each release of SARP. These will include, but not limited to, User Guides, Requirements Documents, CONOPS, Configuration Management Plans, Database Dictionaries. (CDRL A037: Software User Manual (SUM); A027:

Software Requirements Specifications (SRS); A031: Database Design Description (DBDD);

A041: Software Programmer’s Guide and A100: Technical Report-Study/Services)

3.5.3.9 Contractor shall provide semi-annual training on the specific functionality within SARP.

(CDRL A016: Training Materials)

3.5.3.10 Contractor shall deploy new releases of SARP and sub-sites according to IT industry best-practices and provided AF network policies and procedures (submission of requirements, tickets, Media Access Controls [MAC], requirements, Authorized Service Interruptions (ASIs)) (CDRL A038: Software Center Operator Manual (SCOM))

3.5.3.11 Contractor shall support lessons learned for the command by collecting, analyzing and disseminating lessons learned to the warfighter.

3.5.3.12 Contractor shall support User Group and/or Configuration Control Boards associated with SARP. Contractor shall enhance the SARP based on the government-prioritized list of items maintained in the SARP/ASDA Configuration Control Board Database. The Contractor shall provide annually updates to the SARP Configuration Management Plan (CDRL A008:

Contractor’s Configuration Management Plan)

3.6 Requirement 6: MS&A Management and Integration

3.6.1 Subtask 1 – IDIQ Management

3.6.1.1 The contractor shall provide total contract management and supervision of contractor and sub-contractor personnel. The contractor shall provide a primary point of contact for all technical aspects of the required work and no personal services shall be performed (e.g., contractor personnel are not subject to supervision or control by a Government officer or employee). The Contractor Program Manager (PM) shall manage the day-to-day work performed and will interface directly with the government technical leads and COR to ensure all PWS requirements are met, and is responsible for the quality and timeliness of contractor team performance. The contractor shall meet with the government in a team effort that focuses on frequent communications to properly complete all dynamic technical objectives.

3.6.1.2 The Contractor PM shall have recent and relevant experience in software development and similarly sophisticated project management, MS&A management, agile software management, development, warfighter impact analysis, and shall hold a current DoD TS clearance. The experience must also have been in the last three (3) years. The Contractor PM shall attend weekly regular meetings and provide face-to-face support to the HQ AFSPC/A9XYand HQ AFSPC/A3Z customers at Peterson AFB, Colorado 80914.

3.6.1.3 The contractor shall conduct monthly joint technical/ management reviews to ensure contract progression. The contractor shall employ regular discussions, thorough disclosure, and effective feedback to identify problem areas to the government and pro-actively respond to issues in the MSR to the government.

3.6.1.4 The contractor shall provide an overall master schedule within one (1) month of the contract kick-off meeting and provide updates on a monthly basis as work plans are developed.

The overall Master Schedule will incorporate all the activities under Requirements 1 through 7.

The master schedule shall provide the updated status on each requirement. (CDRL A056:

Project Planning Chart).

3.6.1.5 Contractor shall assist in tasker management and provide subject matter expertise (SME) for all activities in the PWS/TOs.

3.6.1.6 The contractor shall conduct a kick-off meeting within one (1) month of contract award.

Attend Program Management Reviews at the start of each option year. The Contractor shall provide a MSR by the 15th of each month. At a minimum, the report will summarize all task/requirement work in the previous month, work to be accomplished in the next month, expenditure of Government funds, and any issues. Actual and projected cost information shall also be provided in excel format. (CDRL A048, Contractor’s Progress, Status and Management Report)

3.6.2 Subtask 2 – MS&A Integration

3.6.2.1 The MS&A tool enhancements required to support HQ AFSPC/A9XY and HQ AFSPC/A3Z in this contract shall be integrated with each other and existing/new analytical efforts to facilitate code reuse, operational missions, long-range planning, strategic analysis, force-mix studies, acquisition decision-making, requirements development, and warfighter impact analysis.

Successful integration of tool functionalities (configuration management, testing, and documentation) and model enhancement oversight and standardization is required to meet overall HQ AFSPC/A9XY and HQ AFSPC/A3Z analysis goals while minimizing model lifecycle costs. Coordinate work hours, costs, and oversee integrated efforts on tools that may require the services of sub-contract model developers, such as in cases where they are the current, official AF or DoD model developers for their respective models.

3.7 Requirement 7: AFSPC Virtual Analysis Capability (AVAC)

The objective of this requirement is to obtain professional, administrative, technical, Operations and Maintenance (O&M) Information Technology (IT) support for the AVAC system supporting HQ AFSPC and their customers. The primary location of this support is Building 1, with additional support to Building 1470, Peterson AFB, Colorado, 80914.

3.7.1 The Contractor shall provide technical support to integrate capabilities across a number of stand-alone and networked classified and unclassified systems in support of HQ AFSPC and their customer’s analytical needs. The Contractor shall provide O&M and modernization IT support to include: installing Software/Hardware (SW/HW), operate, maintain, troubleshoot, and diagnose problems and fix issues on the AVAC network. The Contractor shall provide System Administration, IT Planning, Network Management and Operations, Information Protection (IP), Information Assurance (IA) and Help Desk (HD) services. The Contractor shall provide life cycle support; procure SW/HW; IT asset inventory accountability, receipt and turn-in of all AFSPC assets; PC maintenance for AFSPC assets not covered by vendor warranty; information security mechanisms and execute IP process for AFSPC to include detection and correction of viruses and other security hazards. The Contractor shall work with the Government in a partnership relationship to achieve and maintain Authority to Operate, document and implement requirements for modernization, perform operational requirements and functional excellence while complying with all government laws, directives, instructions, Standard Operating Procedures (SOP), checklists and guidance. (see Bidder’sl Library).

3.7.2 General Requirements.

3.7.2.1 The Contractor shall interface with AFSPC users, other contractors and Government agencies in support of issues surrounding the evolution and operation of HQ AFSPC classified and unclassified networks and systems including administrative network support. In the performance of this task, the Contractor shall support the HQ AFSPC and their customers in the areas of information sharing strategy, information technology services, and information exchange and interchange

3.7.2.2 The Contractor shall provide all required aspects of support: To include, depending on the nature of the task and the customer, support of each instance. These functional categories include helpdesk, system and network management, network security, collaboration, performance management, voice, enterprise management, configuration management, and training. All phases or functional areas contained above are part of the continuing effort to manage life cycle information technology.

3.7.2.3 The Contractor shall possess required clearances, up to TOP SECRET-SENSITIVE COMPARTMENTALIZED INFORMATION (TS-SCI), on contract start date. The Contractor shall provide all personnel, training, transportation and any other items and services necessary to perform O&M under the contract unless defined in this PWS as Government provided.

3.7.2.4 The Contractor is required to have a knowledge of boundary and infrastructure to include the IA certification level of Security Plus, on contract start date. Contractor shall perform IAT Level I requirements for Non-Secure Internet Protocol Router Network/Secret Internet

Protocol Router Network (NIPRNET/SIPRNET) and maintain certifications IAW DoD 8570.01-M, Tables AP3.T1.

3.7.2.5 The Contractor shall maintain and update all documentation contained within the Bidder’s/Technical Library as changes occur and shall make the Bidder’s/Technical Library available to the Government at any time, upon request.

3.7.2.6 The Contractor shall provide all reports and plans referenced in the task order PWS as being made available to the applicable Government, Functional Commander (FC), applicable Contracting Officer’s Representative (COR) Evaluator or Contracting Officer (CO) upon request.

3.7.2.7 The Contractor shall attend meetings, as directed, and notify and provide corrective recommendations to the Government of any equipment, software, or service which has exceeded its life-cycle, is failing, or otherwise requires Government funding or action to maintain the contractual service level, including lack of redundant paths or systems.

3.7.2.8 The Contractor shall deliver a MSR in the form of a Word document highlighting activities completed in the previous month and project activities in the upcoming month and include showing purchases utilizing AVAC funds. (CDRL A048: Contractor’s Progress Status and Management Report)

3.7.3 SPECIFIC REQUIREMENTS

3.7.3.1 The Contactor shall support, but not limited to, the following:

3.7.3.1.1 Information Technology Planning - Define and develop plans to include cost, schedule, and technical data for improving the capability to meet the needs of the AVAC network, customers and downward-directed objectives.

3.7.3.1.2 AVAC O&M Network Services - Maintain the AVAC networks and systems backbone necessary to promote efficient AVAC operations.

3.7.3.1.3 AVAC Network Configuration Management (Classified and Unclassified) - Perform network configuration modeling and develop a network switching/routing plan.

3.7.3.1.4 Information Protection - Monitor system/network event and error logs to identify weak configurations and security vulnerabilities.

3.7.3.1.5 Help Desk - Provide helpdesk, incident, and problem management…