1    

HEADQUARTERS AIR FORCE SPACE COMMAND

MODELING, SIMULATION, AND ANALYSIS (MS&A) FOR SPACE AND CYBERSPACE CAPABILITIES

(MSCC)

PERFORMANCE WORK STATEMENT (PWS)

June 2016

2    

MS&A FOR SPACE AND CYBERSPACE CAPABILITIES, 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 Modelling, Simulation, and Analysis (MS&A) and decision support for space and cyberspace analyses. This contract represents technical and support requirements for space and cyberspace to include engineering/engagement, mission, and theater/campaign MS&A. 1. PURPOSE The overall purpose and objective of this task order is to assist HQ AFSPC/A9XY and HQ AFSPC/A3Z in the development/modification of MS&A and decision support tools as well as the analysis of space and cyberspace capabilities that provide tactical, operational, and strategic level support to meet military and national objectives. 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 and munitions) associated Tactics, Techniques, and Procedures (TTPs); and Combatant Command (CCMD) operations at the tactical, operational, and strategic level. Finally, the contractor must also possess experience in joint/combined operations analysis or analysis skills (e.g., math, probability/statistics, 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), Department of Defense (DoD) Services and Offices, 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.

3    

Enhancements to some MS&A and analytical decision support tools may require the services of third-party tool developers who are the current, official Air Force (AF) or DoD developer for their respective tool. It is the responsibility of the prime 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 PWS. Analysis tools designated for improvements may be proprietary, partially proprietary, or present difficult enhancement challenges within time constraints. 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. 3.1 REQUIREMENT 1. Space-Warfighter Integration MS&A (3600/3400) The goal of the MS&A for Space and Cyberspace Capabilities effort is to support space/ cyberspace trade-space analysis as well as warfighter integration analysis efforts within the Space MS&A framework and analysis process. Figure 1 shows an example of space-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 and is subject to change within the contract Period of Performance (PoP).

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

4    

Figure 2. Space-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 a similar process.

Figure 3. Basic Space MS&A Warfighter Analysis Process

5    

Over the past five years, HQ AFSPC/A9XY has completed several space-warfigher 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).

In addition to the Space-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 Threats Working Group (TWG). For Space-Warfighter Integration MS&A, the contractor shall perform the tasks listed below in support of the TWG. For Cyberspace-Warfighter Integration MS&A, the contractor shall perform similar tasks for an equivalent cyberspace TWG. 3.1.1.1 Review basic scenario and operational mission data/information based on the overall scenario provided by AFSPC (e.g., ISC-A, #2, Long-Term) to understand operational environment. 3.1.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 Combatant Command (CCMD)/J2. The CCMD/J2 can provide key information on the enemy strategic objectives and apportionment/allocation/ operations of key space assets to meet the strategic objectives. 3.1.1.3 Interface with other space MS&A working groups to ensure threat data/information provided meets MS&A needs.  3.1.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), Medium Earth Orbit (MEO)) at the Top Secret (TS) level or below. 3.1.1.5 Assist with defining potential enemy space control Concepts of Operation (CONOPS) and Concepts of Employment (CONEMPS).  

6    

3.1.1.6 Populate Space and Cyberspace Analysis Resource Portal (SARP) with space threat data/information. SARP is defined in section 4.7 Requirement 7. 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 A045) 3.1.1.7 The contractor shall 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 A100) 3.1.2 Warfighter Working Group (WWG) Support. For Space-Warfighter Integration MS&A, the contractor shall perform the tasks listed below in support of the WWG. For Cyberspace-Warfighter Integration MS&A, the contractor shall perform similar tasks for an equivalent cyberspace WWG. 3.1.2.1 Gather and analyze the basic scenario and operational mission data based on the overall scenario approved by AFSPC (e.g., ISC-A, #2, Long-Term). The contractor shall also gather potential data/information on doctrine and Tactics, Techniques, and Procedures (TTPs) documents as well as CCMD and Joint Staff guidance. 3.1.2.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.2.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 can provide 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.2.4 Interface with organizations such as ACC, US Army/G3 and Space and Missile Defense Center (SMDC), US Navy/N3, and CCMD/J3/J5 [Joint Ops] to develop JMTs and Influence Diagrams.  3.1.2.5 Inject OPLAN, CONOPS, CONEMPS, and TTP data/information into the overall scenario approved by AFSPC (e.g., Integrated Security Construct (ISC)-A, #2, Long Term).  3.1.2.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.2.7 Populate the 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 A045)

3.1.2.8 The 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

7    

in the upcoming month. (CDRL A100) 3.1.3 Space Control Working Group (SCWG) Support.

For Space-Warfighter Integration MS&A, the contractor shall perform the tasks listed below in support of the SCWG. For cyberspace MS&A, the contractor shall perform similar tasks for an equivalent Cyberspace Control Working Group (CCWG).

3.1.3.1 Gather and analyze the basic scenario and operational mission data based on the overall scenario approved by AFSPC (e.g., ISC-A, #2, Long-Term) to understand the threats to US/Friendly space capabilities. 3.1.3.2 For space MS&A efforts, interface with the TWG 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 TWG  3.1.3.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 can 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.3.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.3.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 A045) 3.1.3.6 The contractor shall 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 A100)  3.1.4 Mission Analysis Working Group (MAWG) Support.

For Space-Warfighter Integration MS&A, the contractor shall perform the tasks listed below in support of the Space Systems Analysis Team (SSAT) and Warfighter Mission Analysis Team (WMAT). For cyberspace MS&A, the contractor shall perform similar tasks for an equivalent Cyberspace System Analysis Team (CSAT). 3.1.4.1 Space System Analysis Team (SSAT) Tasks. 3.1.4.1.1 Gather and analyze the basic scenario and operational mission data based on the overall scenario approved by AFSPC (e.g., ISC-A, #2, Long-Term) to understand how SFE capabilities support warfighter missions. 3.1.4.1.2 For the PoR defined by the WWG, convert space Measures of Performance

8    

(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: MOP/MOE mapping)  3.1.4.1.3 Interface with key SFE organizations such as the Space and Missile Systems Center (SMC), Sandia National Labs, NOAA, and NASA. These organizations can 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.4.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: Tool assessment summary)  3.1.4.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 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 A045) The contractor shall 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 A100) 3.1.4.2 Warfighter Mission Analysis Team (WMAT) Tasks. 3.1.4.2.1 Gather and analyze the basic scenario and operational mission data based on the overall scenario approved by AFSPC (e.g., ISC-A, #2, Long-Term) to understand the basic warfighter missions (e.g., Offensive Counter-Air) and space touch points. 3.1.4.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.4.2.3 Perform MS&A tool assessments of potential mission-level MS&A tools. 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 Air Force Office of Aerospace Studies (OAS) AoA handbook process for model accreditation will be helpful in completing the assessments. 3.1.4.2.4 For the Space MOEs provided by the SSAT, 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: MOE/Warfighter mapping)  3.1.4.2.5 Populate the SARP with mission-level analysis tools, data, and analysis results.

9    

 Deliverables: Contractor shall deliver an assessment of available mission-level MS&A tools, the mission-level analysis DoE, and mission-level analysis results as well as appropriate GR&As. (CDRL A045) The 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 A100)    3.1.5 Campaign Analysis Working Group (CAWG) Support. For Space-Warfighter Integration MS&A, the contractor shall perform the tasks listed below in support of the CAWG. For cyberspace MS&A, the contractor shall perform similar tasks for an equivalent cyberspace CAWG. 3.1.5.1 Gather and analyze the basic scenario and operational mission data based on the overall scenario approved by AFSPC (e.g., ISC-A, #2, Long-Term) to understand how SFE capabilities support warfighter campaign-level operations. 3.1.5.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.5.3 Perform MS&A tool assessments of potential campaign-level MS&A tools. 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: Tool Assessment summary)  3.1.5.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: Warfighter MOE to Warfighter MOO mapping) 3.1.5.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) The contractor shall 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 A045) 3.2 REQUIREMENT 2. Authoritative Information and Data (AID) Research, Collection, Management and Processes (3600-Research & Development (R&D) Funds) Standardize space, cyberspace, and missile information and data to support M&S efforts, and

10    

make the data available through a reliable repository which is important to the AFSPC community. Authoritative information and data can include 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), etc. 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, etc. 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, cyberspace and missile system engineering data (ground, air, space, cyberspace, missile, sensor, networks, etc.), metadata on authoritative space, cyberspace and missile data sources, M&S metadata, model documentation, M&S Validation and Verification (V&V) and Accreditation reports, 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, AS software, and documents to include system fact sheets, studies, presentations, white papers, AoAs, etc. 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.3 REQUIREMENT 3. M&S R&D: M&S and Analytical Decision Support Tool Enhancements (3600-R&D Funds) 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 the Core Function Lead Integrator (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

11    

decisions. While all capabilities fielded within a Core Function Master Plan (CFMP) are important to the Air Force, the CFLIs 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 The Contractor shall update, modify, and develop M&S models and decision support tools that represent space systems (including cyberspace and missiles) and support the Space, Cyberspace, and DoD analysis communities. The M&S models 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, 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. 3.3.2 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. 3.3.3 M&S Enhancements. 3.3.3.1 The Contractor shall update, modify and develop M&S models and analytical decision support tools that represent space, cyberspace and/or missile systems and space utility for the Space, Cyberspace, and DoD analysis community. Develop planning, development and implementation milestones in collaboration with model/tool managers, AFSPC stakeholders and associated model development contractors. 3.3.3.2 Specific tasks, with government coordination and approval, may involve the development and enhancement of a number of M&S models 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 are candidates for modification each year and can change over time based on capabilities, analysis requirements, and AFSPC Space and Cyberspace Priorities (described in Appendix B): Extended Air Defense Simulation (EADSIM) GPS GPS Interface and Navigation Tool (GIANT) Observation System Simulation Experiment (OSSE) Tool (OSSET) Requirements Assessment and Compliance Tool (ReACT) Satellite Trajectory and Attitude Kinematic (SATRAK) Simulation of Locations and Attack of Mobile Enemy Missiles (SLAMEM) Space Analysis Integration Tool (SAINT) Space and Cyberspace Analysis Resource Portal (SARP) Space Brawler Standardized Astrodynamic Algorithm (SAA) Library Synthetic Theatre Operations Research Model (STORM) System CONOPS and Requirements Environment (SCORE) System Effectiveness Analysis Simulation (SEAS)

12    

Threat, Vulnerability, Timeline (TVT) An overview summary of each model/tool is provided in Appendix A. A modification to the contract may be required for other models/tools. 3.3.3.2.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.3.2.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.3.2.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.3.2.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 describe in Appendix A and AFSPC Space and Cyberspace Priorities described in Appendix B.(CDRL 045, Computer Software Product End Items) 3.3.3.2.5 The Contractor shall provide a Software Version Description Document (SVDD) for each interim and final release of the tool. (CDRL A036, Software Version Description (SVD)) 3.3.3.2.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.3.2.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.3.2.8 The Contractor shall assist AFSPC in the development of scenario files, input files, database files, etc., 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, database files, etc. (CDRL A0024, Operational Concept Description (OCD)) 3.3.3.2.9 The Contractor shall provide training on the tool enhancements to showcase the new model functionality. (CDRL A016, Training Materials) 3.3.3.2.10 The Contractor shall deliver software documentation. These can include User Guides, Analyst Manuals, Programmers Guide, Deployment Plans, Requirements Documents, CONOPS, Configuration Management Plans, Database Dictionaries, etc. (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)

13    

3.3.3.2.11 The Contractor shall support User Group and/or Configuration Control Boards associated with the tool, typically one meeting per year for approximately four models of interest per year. 3.4 Requirement 4: Analysis Support to AFSPC (3600 R&D Funds) In order to meet analysis requirements, the Contractor shall support AFSPC with the following four (4) steps to conduct MUAs using the appropriate analysis tools as identified in para 3.2.3.2:

• Develop MUA Concept. 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 by the Technology & Alternatives Working Group (TAWG) to warfighting metrics such as mission success and time to complete objectives.

• Develop MUA Plan. 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 designs of experiment (DOE) to execute the analysis effort.

• Execute MUA Analysis Plan. Assist in developing and executing analysis tools

identified in the MUA plan to capture key warfighter metrics such as the impact of space/cyberspace capabilities on mission success and time to complete objectives.

• Package MUA Results. Based on senior leadership, working group lead, and

Action Officer (AO) inputs, adjust the analysis products, briefings and reports, while maintaining focus on the AoA tasking and military utility.

The Contractor shall provide the above support for up to Thirty (30) AoAs/studies annually. 3.4.1 Upon execution of a new AoA or 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.2 The Contractor will assist AFSPC in preparing the MUA Concept, MUA Plan, and MUA Analysis Plan documents as identified in the study work plan (CDRL A100, Technical Report-Study/Services). 3.4.3 The Contractor shall execute the MUA Analysis Plan using the identified tools and methodologies. The Contractor shall provide a Study Analysis Report that describes the results of the analysis and the data repository (input files, etc.). (CDRL A100, Technical Report- Study/Services) 3.4.4 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).

14    

3.4.5 The Contractor shall provide analysis briefings that describes analysis to date. (CDRL A100, Technical Report – Study/Services) 3.5 Requirement 5: Space and Cyberspace Analysis Resource Portal (SARP). (3400 Funds) 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 is currently 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 Contractor shall perform SARP maintenance tasks according to Information Technology (IT) industry best-practices and AF network policies and procedures. Work with AF agencies to ensure SARP and its associated sub-sites are operational in accordance with service-level agreements established for the maintenance of SARP web servers, database servers, SMTP email relay, network connections, etc. on NIPRNet, SIPRNet, and JWICS. Assist these organizations in upgrading hardware and software supporting SARP. Perform administrative and security functions on all supported networks, user/group configuration, Uniform Resource Locator (URL) checking, site monitoring, email monitoring etc. Issues will be identified and reported in the Monthly Status Report (MSR). (CDRL A048, Contractor’s Progress Status and Management Report)  3.5.2 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 administrator may be required to obtain Cyber Security Liaison (CSL) 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 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), etc) (CDRL A038, Software Center Operator Manual (SCOM))  3.5.4 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.5 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.6 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))  

15    

3.5.7 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 A008, Contractor Configuration Management Plan)  3.5.8 Contractor shall enhance the SARP based on the government-prioritized list of items maintained in the SARP/ASDA Configuration Control Board Database (CDRL A032, Software Test Plan)  3.5.9 Contractor shall provide a Software Version Description (SVD) for each interim and final release of SARP. (CDRL A036, SVD)  3.5.10 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.11 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.12 Contractor shall provide semi-annual training on the specific functionality within SARP. (CDRL A016, Training Materials)  3.5.13 Contractor shall deliver software documentation for each model enhancement. These can include User Guides, Requirements Documents, CONOPS, Configuration Management Plans, Database Dictionaries, etc. (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.14 Contractor shall support User Group and/or Configuration Control Boards associated with SARP.  3.6 Requirement 6: MS&A Management and Integration (3600-R&D Funds) 3.6.1 The prime contractor shall provide total task management and supervision of contractor and sub-contractor personnel. The prime 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 Task Lead (TL) shall manage the day-to-day work performed and will interface directly with AFSPC/A9XY and HQ AFSPC/A3Z technical leads to ensure all PWS requirements are met, and is responsible for the quality and timeliness of contractor team performance. The prime contractor shall meet with the government in a team effort that focuses on frequent communications to properly complete all dynamic technical objectives. 3.6.2 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

16    

efforts on tools that may require the services of second or third party contracted model developers, such as in cases where they are the current, official AF or DoD model developers for their respective models.  3.6.3 The TL 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 TL shall attend weekly regular meetings and provide face-to-face support to the HQ AFSPC/A9XYand HQ AFSPC/A3Z customers at Peterson AFB, CO. 3.6.4 The prime 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.5 The prime 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 6. The master schedule shall provide the updated status on each requirement. (CDRL A056, Project Planning Chart).  3.6.6 The contractor shall conduct a kick-off meeting within one (1) week 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 and any issues. Actual and projected cost information shall also be provided in excel format. (CDRL A048, Contractor’s Progress, Status and Management Report)  4 Requirement 7: AFSPC Virtual Analysis Capability (AVAC) (3080-Procurement Funds) The objective of this requirement is to obtain professional, administrative, technical, Operations and Maintenance (O&M) Information Technology (IT) support for the Headquarters Air Force Space Command (AFSPC) and their customers. The primary location of this support is Building 1, with additional support to Building 1470 and Building 1840, Peterson AFB, Colorado 80914. 4.1 Scope of Work. 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 network O&M for installing components, operate, maintain, troubleshoot, and diagnose problems on the AVAC network. The Contractor shall provide 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 operational requirements and functional excellence while complying with all government laws, directives, instructions, Standard Operating Procedures (SOP), checklists and guidance, etc. (see Appendix B in Bidder’s/Technical Library). 4.2.1 General Requirements.

17    

4.2.1.1 The Contractor shall interface with other contractors and Government agencies in support of issues surrounding the evolution and operation of HQ AFSPC classified and unclassified networks and systems. 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. 4.2.1.2 The Contractor shall provide all required aspects of O&M 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.  4.2.1.3 The Contractor shall possess required clearances, up to TOP SECRET-SENSITIVE COMPARTMENTALIZED INFORMATION (TS-SCI), and certifications 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.  4.2.1.4 The Contractor is required to have a knowledge of boundary and infrastructure to include Security Plus IA certification level.  4.2.1.5 Upon contract award, the Bidder’s Library becomes a Technical Library (located in Bldg 1470, Rm 126) and the Contractor shall maintain and update all documentation contained within the Technical Library as changes occur and shall make the Technical Library available to the Government at any time, upon request.  4.2.1.6 The Contractor shall provide all reports and plans referenced in the 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.  4.2.1.7 The Contractor shall attend meetings and verbally 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. These meetings include, but are not limited to the following: weekly O&M meetings; meetings to address day-to-day issues, requirements and priorities; meetings to review, discuss and receive approval for new requirements. In addition, Quarterly Program Management Reviews (PMRs) shall be briefed by the Contractor to provide the Multi-functional Team (MFT) an overall status of the contract, including performance metrics, work in progress, any open issues that need resolution, contract expenditure/funding status, and meetings with customers to discuss requirements and issues. The Contractor shall document the actions listed above in the quarterly PMR reports. (CDRL A003).  4.2.2 Specific Requirements 4.2.2.1 Subtask 1 – Information Technology Planning. 4.2.2.1.1 Identify Future Network Requirements. The Contractor shall coordinate with the COR to define and develop plans to include cost, schedule, and technical data for

18    

improving the capability to meet the needs of the AVAC network and downward-directed objectives. The Contractor shall update these plans as needed and make them available to the COR upon request. (CDRL A002) 4.2.2.1.2 Lifecycle. The Contractor shall coordinate development of policy with the Government and implement a life-cycle management plan. The Contractor shall support future budget analysis, recommendations on HW/SW upgrades, and implement Government-approved annual Technology Refresh. (CDRL A002)  4.2.2.1.3 Prepare Network Migration and Upgrade Plans (Support downward directed requirements by Department of Defense (DoD), Higher Headquarters (HQ)). The Contractor shall coordinate all plans with the COR. The Contractor shall update these plans and make them available to the COR for review prior to implementation. The Contractor shall implement these plans upon the Government’s decision to execute. (CDRL A002)  4.2.2.1.4 Manage AVAC IT request actions. Interface with customers on IT requests, initiate work orders, and track status of all IT requests. The Contractor shall follow-up with the appropriate customer for each IT request and document status in the AVAC ticket system.  4.2.2.2 Subtask 2 – AVAC O&M Network Services. The Contractor shall provide the following services/support actions: 4.2.2.2.1 Integrate the AVAC capabilities in support of HQ AFSPC/A9’s analysis and administrative duties. Maintain the AVAC networks and systems backbone necessary to promote efficient AVAC operations. 4.2.2.2.2 Provide HW configuration and maintenance services, network communication services, and system administration services.  4.2.2.2.3 Integrate and provide system and administrative support for newly acquired HW/SW to the AVAC system.  4.2.2.2.4 Maintain capability for data visualization, visual data interpretation, reporting, and distributing. The Contractor shall configure software applications to work within each workstation environment.  4.2.2.2.5 Perform installations, operations, maintenance, and troubleshooting and upgrade of systems to include computer HW, domain name service, directory services, file/print service, operating systems, and their peripherals in support of the M&S capabilities listed above.  4.2.2.2.6 Respond to outages/degradations and coordinate any maintenance actions to bring the system back to full functionality and restore services IAW thresholds in the Service Summary. (SS)  4.2.2.2.7 Schedule AVAC equipment to support demonstrations, tests and analysis for update, modification, and maintenance with COR prior approval.  4.2.2.2.8 Identify and report schedule conflicts to the COR for resolution.  4.2.2.2.9 Conduct weekly AVAC/SGI backups and provide retrieval of data as

19    

necessary, IAW with thresholds in the Service Summary.  4.2.2.2.10 Configure SW tools to make use of multi-central processing unit processors as well as assistance with input/output setup for programs that make use of environment variables.  4.2.2.2.11 Provide training and application for AVAC HW/SW, backup system, and any other system used in or with the AVAC network.  4.2.2.2.12 Submit HW/SW documentation to the HQ AFSPC Configuration Control Board (CCB) IAW with Service Summary performance threshold. This will vary due to HW/SW requirements changing daily. CCB will be at the discretion of COR.  4.2.2.2.13 Tear-down, stand-up, and provide system administration support to portable decision-aiding/collaborative networks.  4.2.2.2.14 Create and carry out security procedures in accordance with Air Force security requirements, AFI 31-401 Information Security, and AFI 33-202 Computer Security, for each AVAC network and system.  4.2.2.2.15 Ensure the integrity of centrally managed servers and data. Manage, store, dispose, restore, test backups, and clean/maintain backup devices.  4.2.2.2.16 Maintain the AVAC filing/retrieval system for information, data, reports, etc.  4.2.2.2.17 Log pertinent AVAC utility information such as M&S tools used in analytical efforts addressing a shortfall in an AFSPC critical need.  4.2.2.2.18 Provide inputs to the Information Administrator Officer (IAO) for the accreditation package for full operational capability of the AVAC network, either verbally or in writing. 4.2.2.2.19 Provide Monthly Status Report showing purchases utilizing AVAC funds to the COR. (CDRL A003)  4.2.2.3 Subtask 3 – AVAC Network Configuration Management (Classified and Unclassified). The Contractor shall provide the following services/support actions: 4.2.2.3.1 The Contractor shall perform network configuration modeling and develop a network switching/routing plan to ensure AVAC mission priorities are taken into consideration. (CDRL A002) 4.2.2.3.2 Manage, configure, install, troubleshoot, maintain, and upgrade Government-approved trouble ticket systems, servers, and databases. The applicable COR shall review database structures and require additional fields of information as processes change. The Contractor shall make the trouble ticket system and database available for Government access, use, and review at all times.  4.2.2.3.3 Identify, resolve, or propose solutions for systems problems that may affect communications, processing, or efficiency.  

20    

4.2.2.3.4 Perform and monitor change management procedures as established for the network. Perform and monitor system modifications, which have been approved by the CCB. Schedule, track, and coordinate all network changes through the COR. These changes shall include, but shall not be limited to: modifications to update the network configuration and new services implementation and installations. Record the status of these actions in the Technical Library.  4.2.2.3.5 Support the configuration change control process to ensure architecture or system modifications do not negatively impact the performance of Enterprise IT systems that support operational AVAC requirements.  4.2.2.3.6 Provide recurring modeling and simulation support.  4.2.2.4 Subtask 4 - Information Protection. The Contractor shall provide the following services/support actions: 4.2.2.4.1 Monitor system event and error logs to identify weak configurations and security vulnerabilities using Government-provided tools. Report all anomalies through the established chain of command and make recommendations on the level of any threat posed and any actions that may be necessary to correct the anomalies and correct unsatisfactory conditions caused by these anomalies. 4.2.2.4.2 Immediately report any system abuse discovered through the established chain of command. The Contractor shall not take any action to notify the abuser, collect additional information on the abuser, or to correct abusive activities without specific authorization from the COR for each case.  4.2.2.4.3 Protect the network on a weekly basis from malicious code. Install current anti-virus software, updates, patches, and definitions on every information system and devices under Contractor control.  4.2.2.4.4 Change administrator passwords on Government computer systems and network communications systems every 60 days. The passwords shall be made available to the Government at all times.  4.2.2.5 Subtask 5 - Help Desk. The Contractor shall provide the following services/support actions: 4.2.2.5.1 Provide helpdesk, incident, and problem management services. Provide trouble assistance to customers, including remote technical support. 4.2.2.5.2 Staff the Help Desk and resolve issues on the AVAC networks. The Help Desk is located in Building 1 and requires the Contractor to provide coverage from 07:30 am to 04:30 pm, Monday through Friday. The Contractor shall open trouble tickets for problems within the AVAC network. All user problems not resolved within 1 business day will be briefed daily to the COR until resolved.  4.2.2.6 Subtask 6 - Equipment Control. The Contractor shall provide the following services/support actions: 4.2.2.6.1 Provide equipment accountability and asset management. Support the HQ AFSPC Information Technology Equipment (ITE) custodian in conducting an annual physical

21    

Inventory of ITE equipment associated with the AVAC network. 4.2.2.6.2 Upon receipt of deliveries, identify all accountable items and provide documentation and serial number information to the government for input into the Asset Inventory Management System (AIMS). The government shall provide AIMS barcode labels to the Contractor.  4.2.2.7 Subtask 7- Software Licenses and Inventories. See Bidders Library. The Contractor shall provide the following services/support actions: 4.2.2.7.1 Update all software licenses and software inventory. See Bidder’s Library for current software inventory. 4.2.2.8 Joint Inventory. Participate in a joint inventory of documentation in at least each functional area listed below: - Management Files - Operations Documentation - Software and System Analysis - Equipment Maintenance and Management - Supply - Libraries - Security - Quality Control Inspections - Project Folders - Outstanding trouble tickets 4. CONTRACTUAL REQUIREMENTS

4.1 Transition of Effort The main objective of the transition effort is to ensure continuity of services and operations identified in this PWS. The transition period will be five (5) business days. During the transition period, the successor contractor shall become familiar with the existing network resources, processes/procedures, and the day-to-day services performed by the incumbent contractor. The successor contractor shall not impede the performance of the incumbent contractor. 4.2 Phase-In

4.2.1 The contractor shall perform a physical inventory of all systems/equipment against appropriate accountability documents with the Contracting Officer Representative (COR). 4.2.2 The contractor shall complete the Contractor Visitor Security Agreement (VSA) with the appropriate COR security office. 4.2.3 The contractor shall, with the government security manager assistance, complete the application process for restricted area badges and schedule a security in-brief with the HQ AFSPC/SSO office.

22    

4.3 Phase-Out

The contractor shall develop and implement a transition plan prior to the end of the final performance period. The PoP for the transition should be a minimum of Thirty (30) business days from award of follow-on contract. In the event the follow-on contract is awarded to other than the incumbent, the incumbent contractor shall cooperate to the extent required to permit an orderly transition to the successor contractor.

4.3.1 The contractor shall perform a physical inventory of all systems/equipment against appropriate accountability documents. The Government shall approve the selected method prior to accomplishing the inventory and transferring government-owned assets. 4.3.2 The contractor shall identify all approved work orders to the successor.  4.3.3 The contractor shall identify points of contact for/to work supply issues.  4.3.4 The incumbent contractor shall, along with the successor contractor, jointly inventory and transfer classified materials.  4.3.5 The contractor shall terminate the contractor VSA with the appropriate COR.  4.3.6 The contractor shall return all restricted area badges to the Government security manager and schedule a security debrief with the HQ AFSPC/SSO office.  4.4 Place of Performance 4.4.1 Work in support of these requirements on this contract shall primarily be performed at both the government and contractor site. As a tenant of agile methodology, face-to-face continuous collaboration and feedback is essential between the development teams and the operational community for successful product development. Peterson Air Force Base (PAFB) operational community and the lead developer personnel must work together throughout the contract PoP. This interaction may occur at the government facilities or the contractor facilities. These interactions will include but not be limited to software demonstrations, white-boarding, analysis reviews, research, technical design brainstorming sessions, and project reviews. The TL will attend monthly meetings.  4.4.2 Not all PWS requirements must be performed in the local area; however, the nature and extent of the PWS requirements necessitate the contractor be able to provide management and technical support (e.g. Task Lead) that is local to PAFB, Colorado.  4.5 Duty Hours. When working on Government sites, normal duty hours are 0730-1630, Monday through Friday, unless otherwise specified. Circumstances may require the Contractor provide services after normal duty hours. 4.6 Base Closure/Government Morale and Recreational Activities. Situations may arise where government facilities may not be available for performance of requirements (i.e., base closure due to weather, force protection conditions, etc.). Under these circumstances, contractor employees shall comply with individual company policy in accordance with company compensation system. Since the Government does not have an employer/ employee relationship with contractor employees, it is not authorized to grant administrative leave or expend government resources to compensate contractor employees for hours

23    

expended on activities not included in the PWS. 5. GOVERNMENT-FURNISHED PROPERTY/INFORMATION (GFP/GFI). 5.1 Government Furnished Property and Equipment. The contractor shall be provided one (1) workspace in Building 1, Peterson AFB; this includes desk space, chair, and computers connected to NIPRNET/SIPRNET access, and use of telephones, copier and fax machines. Any additional personnel will be required to work at the Contractor’s facility. 5.1.1 Use and Disposition of Government-Furnished Property and Equipment. All Government-provided equipment, resources, materials, and documentation (records) produced by the Contractor for the Government in support of the requirements in this PWS, are the sole property of the Government and shall not be sold, removed, duplicated, or used by the Contractor for any purpose outside the provisions of the contract. All official records, files, documents, and working papers provided by the Government or generated in support of the requirements in this PWS are official Government records. The Contractor shall not retain any equipment purchased under this contract for any reason other than the performance of the requirements in this PWS. 5.2 Equipment and Records. The Contractor shall provide the following services/support actions: 5.2.1 Warranties and Equipment. Maintain a copy of all documentation for warranties on Government furnished equipment. In addition, maintain a current list of all equipment under warranty including type of response, POC address, and phone number in the technical library. The Contractor shall inform the appropriate COR at least 6 months prior to any warranty expiration for budgeting purposes. 5.2.2 Maintain all service and operator manuals and guides for each piece of equipment and software in the Contractor’s Area of Responsibility (AOR). 5.2.3 Develop and implement a preventive maintenance program and plan, schedule, and coordinate all maintenance actions that shall result in equipment and system downtime with the AVAC network and all affected users. The Contractor shall develop a maintenance schedule and keep it on file for Government review upon request. 5.2.4 Establish and maintain permanent equipment logs which shall reflect equipment status. These records shall be made available for Government review upon request. 5.2.5 Perform configuration control for all equipment covered by this PWS and obtain prior approval from the COR before cannibalization of, modifications, or alterations to Government facilities or equipment. 5.3 Materials and Other Direct Costs (ODCs). The Contractor may be required to purchase reimbursable items costing less than $3,000. Reimbursable purchases must be approved by the COR, in writing prior to purchase. Items exceeding $3,000 shall require COR recommendation and written Contracting Officer approval. The Contractor shall not break up a purchase to meet this threshold. The Contractor shall provide an itemized listing of purchased items and title the listing “Government-Furnished Property (GFP).” All Automated Data Processing equipment (computers, printers, copiers, fax, NIPRNET/SIPRNET e-mail accounts, etc.) associated with the performance of this PWS in Government facilities will be procured by the Contractor, unless otherwise coordinated. The majority of the software associated with the

24    

performance of this PWS in Government facilities will be procured by the Contractor. 5.4 Information Sources. Government personnel will provide technical input, answer questions, review/accept completed work, and provide feedback regarding contractor efforts. COR will be the primary source of technical guidance for this PWS. 5.4.1 AFPD16-10, “Modeling and Simulation (M&S) Management” 5.4.2 Physical and electronic access to the SARP.  5.4.3 Electronic access to the AFSPC unclassified network through AF Virtual Private Network (VPN) capability or workspace. 5.4.4 AFSPCI 33-105, “Distribution of HQ AFSPC Astrodynamic Software” or any AFSPC Temporary Procedures  5.4.5 SARP Configuration Control Board (CCB) list of related implementation items 5.5 Hardware/Software 5.5.1 SARP NIPRNet, SIPRNet, and JWICS O&M deployment of new releases require the SARP development and administration team to have access and work at the government site weekly. For these requirements, HQ AFSPC/A9XY shall make available up to four (4) NIPRNet and four (4) SIPRNet workstations available at the government facility for contractor use. The government shall also make available up to two (2) Classified AFSPC Virtual Analysis Center (CAVAC) and two (2) JWICS workstations available at the government facility for contractor use. The government will provide three (3) laptop computers and four (4) computer servers as GFP to support the development, testing and demonstration of interim builds of tools. In addition, the government will provide one (1) Secret and one (1) Top Secret AFSPC Virtual Analysis Capability (TS AVAC) system terminals to support SARP testing and O&M.  5.5.2 Standardized Astrodynamic Algorithm (SAA) Software. Dynamic Link Library (DLL), source code, documentation, sample input and output files, and drivers for AS Software. Request to use this software must comply with AFSPCI 33-105. 5.5.3 Government-owned source code, scenario files, and other data will be provided to the contractor for the MS&A tools to be enhanced.  6. CONTRACTOR IDENTIFICATION. 6.1 The Contractor shall appoint a Project Manager (PM) who shall coordinate with the COR to obtain and clarify contract requirements and be responsible for the daily control and supervision of the contractor’s employees. This shall be the individual who coordinates with the Government on matters of contract or contractor performance. The Contractor shall provide the name, address and telephone of the POC and his/her alternate to the contracting officer and appropriate COR no later than the pre-performance conference and thereafter as changes occur. In the absence of the PM, the designated alternate, shall have full authority to act for the Contractor on all matters relating to the day-to-day operation of this contract. 6.2 The PM shall ensure the contractor's employees understand the prohibitions imposed on the US Government regarding personal services contracts and will report instances where the

25    

government attempts to control or supervise contractor employees to the COR or Contracting Officer immediately. The Contractor shall ensure their personnel identify themselves as contractors with contractor and/or visitor security badges. The Contractor shall ensure its personnel do not perform any inherently governmental activities. The Contractor shall ensure its personnel do not attempt to represent the Government of the US or AFSPC to any other person or entity, US or foreign, except for delivering a government-approved message or position. The Contractor shall, under government guidance, coordinate with other contractors during the performance of this contract.  6.3 Contract work performance shall take place at 150 Vandenberg St, Ste 1105 (Bldg 1), Peterson AFB, CO 80914 with assistance in Buildings 1470 and Building 1840 where additional workstations are located. Work hours are weekdays (Monday-Friday) from 7:30 am to 4:30 pm. Contractor employees will contact the Program Manager for direction concerning late reporting or early release due to inclement weather. Government officials are not authorized to grant “administrative leave” or expend government resources to compensate contractor personnel to attend government-sanctioned morale building activities (e.g., picnics, golf outings, holiday parties, sports day events, fitness time). Military down days are not considered Government holidays. Legal Federal Holidays observed by the Federal Government are as follows: New  Year’s  Day   1  January   Labor  Day   1st  Monday  in  

September  Martin  Luther  King’s  Birthday  

3rd  Monday  in  January  

Columbus  Day   2nd  Monday  in  October  

President’s  Day   3rd  Monday  in  February  

Veteran’s  Day   11  November  

Memorial  Day   Last  Monday  in  May   Thanksgiving  Day   4th  Thursday  in  November  

Independence  Day   4  July   Christmas  Day   25  December    6.4 Contractor PM or alternate shall be available at arranged a time to meet on the Peterson Complex with Government personnel designated by the contracting officer to discuss problem areas. 6.5 The Contractor shall be subject to the policies and directives governing the activities of all personnel on the Peterson Complex as well as those governing AFSPC.  6.6 Employees should be recognizable as a Contractor employee at all times by wearing, on the front of the outer clothing, a contractor badge bearing the employees’ name. All employees shall identify themselves as a contractor in meetings, over the phone, and in e-mail traffic.  6.7 Contractors shall adhere to procedures to be followed in the event of actual or simulated fires, weather advisories, natural disasters, bomb threats, terrorist activities, enemy attack, and other similar emergency type conditions posing a real or potential danger to people or property as directed by the appropriate COR. The Contractor shall follow AFSPC Emergency Action Plans. 7. DOCUMENTATION AND DATA MANAGEMENT.

26    

7.1 Proprietary Data. The contractor shall request government approval prior to the use of any proprietary data or software tools to fulfill the requirements of this contract. The government shall provide the contractor access to information required to accomplish assigned tasks commensurate with security clearance and on a need-to-know basis. The contractor shall return all data pertaining to this contract to the government upon contract expiration or termination. The contractor shall not retain classified or unclassified material generated or received under this contract after the contract ends without approval of the appropriate office of primary responsibility. The government has unlimited rights to all deliverables developed under this PWS; however, rights to deliverables with respect to delivery of proprietary tool executable code is restricted to HQ AFSPC/A9XY and HQ AFSPC/A3Z only. The contractor shall not use any materials pertaining to this Task Order for business development or any other vendor strategic purposes. However, the Contractor is authorized to include summary performance information in proposals to be submitted to the Government to satisfy past performance information requirements. 8. PERSONNEL SECURITY. 8.1 Information requiring classification in the interest of national security shall be consistent with the security classification guide. The Contractor shall provide personnel with clearances commensurate with DD Form 254, Department of Defense (DoD) Contract Security Classification Specification. All personnel assigned to this task order must possess a Top Secret-Sensitive Compartmented Information (TS-SCI) United States Government security clearance prior to beginning work on this PWS. 8.2 Industrial Security. The Contractor shall comply with DoD 5220.22-M, DoDM 5200.01-V4 and AFI 31-601, Industrial Security Program, security and law enforcement procedures, plans established for the Peterson Complex, and local operation instructions. 8.3 Physical Security. The Contractor shall comply with base Operations Plans and Instructions for Force Protection Condition procedures, Random Antiterrorism Measures, and local search and identification requirements referenced in this PWS. The Contractor shall adhere to AFSPC security polices and be responsible for the safeguarding of all Government property provided for Contractor use. At the end of each work period, all Government facilities, equipment, and materials shall be secured. 8.4 Security (OPSEC). The Contractor employee shall attend government OPSEC training within 90 days of initial assignment to ensure complete contract understanding of exactly what special OPSEC provisions are required by the user agency (UA). Reference AFI 10-701 (Chapter 5) & AFSPCSUP I: Operations Security (OPSEC). See DD254 Addendum. 8.5 Procedures to Controlled and Restricted Areas. The Contractor shall be allowed unescorted access to Government buildings on Peterson AFB consistent with task requirements. The Contractor shall comply with and enforce entry and internal controls, and other physical security requirements applicable to USAF restricted and controlled areas.

27    

Compliance includes enforcing these controls in areas where the Contractor controls entry. All personnel requiring frequent entry to Peterson AFB shall be provided access in accordance with AFI 31-101, The Air Force Installation Security Program. 8.5.1 Approximately 25% of the MS&A work requires TS/SCI and NATO-Secret for tasks and activities accomplished on the JWICS. The contractor(s) performing this task must be cleared at the TS/SCI level. Also, approximately 10% of the MS&A work required SAP/SAR access. The contractor(s) performing this task must possess the ability to obtain SAP/SAR access. 8.5.2 The contractor will work with the HQ AFSPC/A9XY and HQ AFSPC/A3Z Security Managers and Technical Leads to determine which tools and analysis require this security level. 8.5.3 Contractor’s security officer shall conduct a “hands-on” inventory of all Controlled and Restricted Area(s) badges issued to the Contractor employees. The inventory shall be conducted no later than one month following contract start and annually thereafter. The Contractor shall perform a final inventory during the phase out period of the contract. Results of all inventories shall be made available to the Unit Security Manager through the appropriate COR or FC within 5 business days of completion.  10 ACCESS TO GOVERNMENT PROPERTY AND FACILITIES. The contractor shall be allowed unescorted access to Buildings 1 and 1470, Peterson AFB CO. Access to government facilities, documents, and systems shall be in accordance with the attached DD Form 254. 11 SECURITY ISSUES. The contractor shall adhere to government security guidance ensuring all security classification issues are mitigated and resolved. The contractor shall also manage the database ensuring no security issues occur and any issues shall be coordinated with the government COR/security manager for both unclassified and classified networks. Particular attention to the compilation of data (combining data from multiple sources) that would raise the security level will be the responsibility of the contractor.  12 SYSTEM AND NETWORK AUTHORIZATION ACCESS REQUESTS. For Contractor personnel who require access to DoD, Defense Information Systems Agency (DISA), or Air Force computing equipment or networks, the Contractor shall have the employee, prime or subcontractor, sign and submit a System Authorization Access Report (SAAR), DD Form 2875.  13 TRAVEL. Contractor employees may be required to travel to various locations within the continental United States (CONUS). All travel to fulfill the tasks in this PWS shall be performed with prior approval of the COR and costs shall be reimbursed in accordance with Federal Acquisition Regulation (FAR) Part 31.205-46, Travel Costs. If any travel arrangements cause additional costs to the task order that exceed those previously negotiated, written approval by CO is required, prior to undertaking such travel. Local travel is defined as within a 50 mile radius of Colorado Springs and shall not be reimbursed.  13.2 TRAVEL ESTIMATES. Annual estimated travel requirements are included below 13.3 TRAVEL LOCATIONS. Table 2 shows the travel estimates.

28    

Location Estimated N umber of Trips/Year

Estimated Number of Days per Trip

Estimated Number of

Personnel per Trip

Colorado Springs, CO 4 3 2 Los Angeles, CA 4 3 2 Huntsville, AL 3 3 2 Omaha, NE 4 3 2 Washington DC 4 3 2

Table 2. Travel Estimates 14 MATERIALS AND OTHER DIRECT COSTS (ODCs). In the event the contractor is required to purchase reimbursable items costing up to $3000, such purchases shall be submitted for approval to the COR prior to actual purchase. Items costing greater than $3000 shall require prior COR and Contracting Officer approval. Purchases shall not be broken up in order to meet this threshold. 15 TRAINING. Contractor personnel are required to possess the skills necessary to support their company’s minimum requirements of the labor category under which they are performing. Training necessary to meet minimum requirements will not be paid for by the government or charged to Task Orders. This requirement is repeated to ensure the contractor shall be certified on Day 1 of the start of the contract in AF Web Administration, Agile Software Development, Scrum Master or equivalent, and possess expert abilities in Microsoft products. 16 DATA DELIVERABLES.

CDRL Requirement Description CDRL A008 Req 2 (3.2.3.2.3),

Req 3 (3.3.5.3) Contractor’s Configuration Management Plan

CDRL A016 Req 2 (3.2.3.2.9), Req 3 (3.3.5.8)

Training Materials

CDRL A019 Req 2 (3.2.3.2.6), Req 3 (3.3.5.6)

Computer Program End Item Documentation

CDRL A024 Req 2 (3.2.3.2.8) Operational concept Description (OCD) CDRL A027 Req 2 (3.2.3.2.10),

Req 3 (3.3.5.9) Software Requirements Specifications (SRS)

CDRL A029 Req 2 (3.2.3.2.2), Req 3 (3.3.5.2)

Software Design Description (SDD)

CDRL A031 Req 2 (3.2.3.2.10), Req 3 (3.3.5.9)

Database Design Description (DBDD)

CDRL A032 Req 2 (3.2.3.2.4), Req 3 (3.3.5.4)

Software Test Plan

CDRL A034 Req 2 (3.2.3.2.7), Req 3 (3.3.5.7)

Software Test Report (STR)

CDRL A036 Req 2 (3.2.3.2.5), Req 3 (3.3.5.5)

Software Version Description (SVD)

CDRL A037 Req 2 (3.2.3.2.10), Req 3 (3.3.5.9)

Software User Manual (SUM)

CDRL A038 Req 3 (3.3.2) (3.3.4)

Software Center Operator Manual (SCOM)

29    

CDRL A041 Req 2 (3.2.3.2.10) Req 3 (3.3.5.9)

Software Programmers Guide

CDRL A045 Req 1 (3.1.3) Computer Software Product End Items

CDRL A048 Req 4 (3.4.5), (3.5.4)

Contractor’s Progress, Status and Management Report

CDRL A056 Req 4 (3.4.2) Project Planning Chart

CDRL A099 Req 2 (3.2.3.2.1), Req 3 (3.3.5.1) Req 5 (3.5.1)

Technical and Management Work Plan

CDRL A100 Req 1 (3.1.1), Req 2 (3.2.3.2.10), Req 3 (3.3.5.9), Req 4 (3.4.3), Req 5 (3.5.3), (3.5.5)

Technical Report – Study/Services

30    

Appendix A

Air Force Simulation (AFSIM) AFSIM is a government-approved C++ simulation framework for use in constructing engagement and mission level analytic simulations for the Operations Analysis community, as well as virtual experimentation. The primary goal of AFSIM applications is the assessment of new system concepts and designs with advanced capabilities not easily assessed within traditional engagement and mission level simulations. Development activities include modeling weapon kinematics, sensor systems, electronic warfare systems, communications networks, advanced tracking, correlation, and fusion algorithms, and automated tactics and battle management software. Extended Air Defense Simulation (EADSIM) The Extended Air Defense Simulation (EADSIM) is a many-on-many simulation of air, missile and space warfare. It provides analysis, training, test, and operational planning in one package. EADSIM is one of the most widely used simulations in the world with over 300 user agencies worldwide. EADSIM is managed by the U.S. Army Space and Missile Defense Command/Army Forces Strategic Command (SMDC/ARSTRAT), as the executive agent for the Missile Defense Agency (MDA).

It is a workstation-hosted, system-level simulation that is designed to be used by combat developers, material developers, and operational commanders to assess the effectiveness of Theater Missile Defense (TMD) and air defense systems against the full spectrum of extended air defense threats. EADSIM includes logic to dynamically alter networks, modeling the reconfiguration of the network. It supports analysis of the impact of cyber attack on C2 nodes, network connections, and ultimately the downstream impact on combat performance, while the ability to recover from a cyber attack is captured using the Reliability Availability and Maintainability (RAM) component repair capability. Originally introduced to model nuclear detonations, the “Weapon Event” feature is being leveraged to model a cyber weapon events. The Launch Event represents the launch of a cyber attack, the Detonation Event represents the delivery of the cyber attack, and the effects of the cyber attack are evaluated and can potentially trigger propagated effects.

GPS Interference And Navigation Tool (GIANT) The Global Positioning System (GPS) Interference And Navigation Tool (GIANT) is a constructive and repeatable mission-level simulation used to determine navigation performance and its impact upon air-to-ground or surface-to-surface operational effectiveness.

GIANT is PC-based, is Government-Owned, includes a user-friendly graphical interface for setup and execution, some post-processing aids, and runs much faster than real-time. A GIANT simulation run consists of one GPS/INS-equipped platform moving along a pre-defined route, with optional air-to-ground or surface-to-surface munitions versus multiple targets, over digital terrain, on a WGS-84 ellipsoid and geoid, through a scenario consisting of zero to many GPS interference sources or jammers.

The Jammer-to-Signal (J/S) ratios produced by GIANT were validated against flight test data consisting of single and multiple jammer scenarios across two independent GPS flight tests. The semi-synchronous GPS satellite constellation is modeled and is compatible with Yuma- formatted input almanacs. Satellite orbits and Dilution of Precision (DOP) have been validated against multiple sources. Platform position error is calculated as a function of the

31    

combined GPS/INS solution for each 1-second position along the input route. Routes can be combined to produce aggregate or battle-level performance and effectiveness across multiple routes. Multiple time- history and event-driven performance output files are selectable.

GIANT documentation includes Analyst and User Manuals, V&V Report, Data Pedigree and Configuration Management Plan.

To date, GIANT has been accredited for use on the Navigation Warfare (NAVWAR) and Hard and Deeply Buried Target (HDBT) AoAs and has been accepted into the AF Standard Analysis Toolkit (AFSAT). A formal Configuration Control board (CCB) is established. Periodic User and CCB meetings are conducted. GIANT includes pre-built databases for receivers, installed antenna patterns, Inertial Navigation Systems (INS), and more. Formal training is periodically provided and is also available on request.

Observation System Simulation Experiment Tool (OSSET) Developed by Atmospheric & Space Technology Research Associates (ASTRA), LLC, OSSET is a software application that provides HQ AFSPC with the ability to perform assessments of the utility of existing and planned sensors for global and regional ionospheric specification for Space Situational Awareness and Battlespace Awareness. This kind of tool is vital for AoAs and other trade studies. The OSSET tool helps to maximize the utility of new sensors and ionospheric measurement systems. It could also save the government millions of dollars by preventing the purchase and deployment of unnecessary or redundant sensors that provide a low return on investment.

The OSSET software tool simulates ionospheric electron density values and the corresponding errors from various ground-based and space-based sensors, including in situ and remote sensing measurements. OSSET is able to accommodate the simulation of various spatial and temporal distributions of these ionospheric sensors. The simulation framework design will integrate an ionospheric sensor error model, a background electron density model, and a forward model for estimating electron density errors.

The current software (Version 1.0) delivered the following functionality to:

• Simulate ionospheric observations from space-based in situ, Ultraviolet (UV) limb- viewing, andGPS radio occultation sensors.

• Simulate observation uncertainties, and allow the user to scale these uncertainties up or down to test their effect on the results

• Ingest the simulated observations and uncertainties into the ASTRA ionospheric data assimilation algorithm, Ionospheric Data Assimilation Four-Dimensional (IDA4D)

• Provide an assessment of the utility of existing and planned space-based sensors for ionospheric specification by showing how the different datasets improve the ionospheric specification.

Satellite Trajectory and Attitude Kinetics (SATRAK) The SATRAK model was initially developed as a prototype application to demonstrate how to build an application using the Space Analysis INtegration Toolkit (SAINT). The SATRAK prototype has evolved and now replaces the legacy DOS-based SATRAK V6 with a modern and richly interactive user interface suited for current Windows operating systems. SATRAK v7 is approved for installation on the NIPRNet and SIPRNet.

32    

SATRAK allows analysts to exercise various Astrodynamic Standards and view the results on 2D map, 3D Globe, plain text, tabular data, and chart. There is advanced sorting, filtering, and grouping capabilities for the tabular input and output data.

• SATRAK MODULES

o SGP4: Simplified General Perturbations #4, used to propagate satellites LAMOD: Look Angle Module, used to determine sensor look angles SimOrb: Used to simulate orbits

o Decay: Used to calculate satellite decay and lifetime using King-Hele algorithm o BLUE: Bob’s Launch Update Ensemble, used to update satellites to a new launch

time. MANAL: Maneuver Analysis, used to analyze satellite maneuvers o Sensor Coverage: Used to display sensor coverage on a 2D map and/or 3D globe

ElsetPlot: 2D graphing of element set data

• 2D MAP / 3D GLOBE

o The 2D map and/or 3D globe can be used to display satellite orbits in real-time or batch mode and lamod lookangle points (batch mode only). They support the following features:

o Sensor position and coverage overlay o Zooming and panning (For 2D map: when zoomed in, a mini display is shown to

provide a full overview of the map. Inside the mini display you can pan the map by dragging the rectangle representing the zoomed-in region)

o Redefining the center longitude (2D map only) Show day / night terminator o Show latitude / longitude gridlines o Saving the image to the clipboard or file (2D map only) o TABULAR OUTPUT. The tabular output allows the analyst to easily sort, group

and filter the output data by 1 or multiple columns. Conditional formatting can be applied to enhance the readability and usability of the displayed data. Data can easily be exported to Microsoft Excel in XML format—this method does not require MS Office installation on the machine and it can be read from Excel 2002 and above. All tabular data can be exported to 2D chart to plot data on X-Y axes.

• DATA. The state of the SATRAK Application including input data (satellites and sensor)

and the module parameters can be saved in an XML file. This file can then be shared with another SATRAK application or any application that is built on top of SAINT. The TLE format is supported for satellite input data and SATRAK recognizes the card sensor location (S-Card) and sensor limits (1L-Card) format for sensor input data. Output data can be saved in various formats to include ASCII, XML and Excel.

• FUTURE ENHANCEMENTS. Include the following:

o Polar plots o Computation of Miss Between Orbits (COMBO) o Break-up Analysis Model (BAM)

Simulation of Locations and Attack of Mobile Enemy Missiles (SLAMEM) SLAMEM® is an entity level simulation that is used both for stand-alone constructive analysis and as a federate in distributed constructive and human-in-the-loop simulation exercises. SLAMEM was developed to analyze the performance of coordinated C4ISR and targeting systems against time-critical mobile targets. SLAMEM strikes a reasonable balance between

33    

high fidelity (to support meaningful analyses) and fast execution (to support parametric tradeoff studies). SLAMEM models individual objects by tail number, such as ground vehicles/targets (TELs/SAMs, force hierarchy, dismounts, boats, background traffic); surveillance platforms (airborne, ground based, space based); sensor payloads (optical, radar, SIGINT); attack aircraft (fighters, helicopters, UCAV); and theater and strategic surface-to-surface missiles (including ATACM, cruise missiles). These entities are characterized by their system-level parameters. GMTI radar, for example, is modeled with an antenna size, field-of-regard, beam scan rate, processing time, and minimum detectable velocity, among other potential parameters. SLAMEM also models the command, control, and communication (C3) process of passing data for exploitation (detection and classification), multi-source fusion, sensor re-tasking, and attack nomination. Time delays are specified for the various C3 functions. Specific geography is modeled in SLAMEM via Databases of Terrain Elevation (DTED), road networks, foliage cover, and populated regions (buildings).

Applications:

Stand-Alone Constructive Analysis: SLAMEM‘s role in supporting surveillance and targeting activities includes analyzing advanced C4ISR architectures. SLAMEM analyses have several objectives, including: (1) quantifying the potential improvements in effectiveness provided by the advanced architecture; (2) deriving the performance required from the technologies to achieve specific mission-level goals; and (3) developing new CONOPS for using the technologies most effectively. Interactive Simulation: SLAMEM is High Level Architecture (HLA) and Distributed Interactive Simulation (DIS) compliant and supports interactive simulation both for constructive and human-in-the-loop applications. For interactive uses, SLAMEM has been separated into independent federates:

• C4ISR Architecture Federate • Ground Vehicle Simulation (GVS) Federate • Fusion Center Federate • Attack Federate

Testbed for Algorithm Development and Testing: SLAMEM is used to stimulate algorithm development and testing by providing a virtual sensor information environment. Examples include tracking algorithms, asset scheduling, mission planning, automatic retasking, and command and control prototyping.

Space Analysis Integration Tool (SAINT) SAINT is a toolkit to integrate various Astrodynamic Standards and other analysis functions and algorithms into a single application. SAINT provides the development environment and building blocks to put together quick turn space analysis tools. Visualization tools will be available for the analyst to display algorithm/function output into X-Y plots. Exporting of the data into standard formats such as XML and Excel is provided. 2D and 3D visualization tools have been added to view satellite propagation and sensor look angles.

SAINT also provides a .Net Application Programming Interface (API) for working with the Astrodynamic Standards Fortran DLLs for integration with any other .Net application. SGP4, SP, LAMOD, OBS, ROTAS have been integrated into SAINT.

34    

Space and Cyberspace Analysis Resource Portal (SARP) SARP is the HQ AFSPC focal point for locating space and cyberspace MS&A information and data. Higher headquarters guidance, constrained budgets, and a desire for increased efficiency are the motivations behind sharing space and cyberspace information and data effectively. SARP provides the MS&A community with the ability to share space and cyberspace authoritative information & data, as well as information about space and cyberspace models, simulations, and studies.

Model Repository features include: 1) Repository of space and cyberspace models and simulations HQ AFSPC uses or recommends. 2) Key studies associated with each model. 3) Forums to allow on-line collaboration on Modeling. 4) Tools for identifying and locating models or studies based on their characteristics.

Space Authoritative Information and Data (AID) provides an authoritative baseline of HQ AFSPC space data for the acquisition, test and evaluation, training, experimentation, planning and analysis communities that is consistent with the with the HQ AFSPC Corporate Process, products and current operations. Features include: 1) Report Generation via queries for data from a single authoritative source. 2) Data extraction in several formats. 3) Archives to past years data.

Space AID contains a section devoted to meta-data describing Space and Cyberspace Data Sources. This was added to support the USSTRATCOM Space Data Catalogue and data collection efforts. It allows users to locate the data needed to fulfill their requirements.

SARP develops and maintains current discovery metadata on key space and cyberspace M&S assets that the DoD is developing, managing, or maintaining by providing M&S metadata to the M&S catalogue (MSCat).

SARP hosts a version of the Web-Based Interface for Satellite Assessment & Research Dissemination (WISARD) which is a repository of satellite information that includes Air Force Research Laboratory assessed satellite attributes with supporting references and images from open and classified sources from the intelligence community. The satellite data originates from the AFRL’s Satellite Information Database (SID) which is used to help document and store satellite information needed to perform assessments on satellites

The SARP is deployed as an unclassified website on the NIPRNET and a classified website on the SIPRNET which contains classified data. It has been approved for deployment on JWICS and work is underway to fulfill that need.

Space Brawler Space Brawler is a baseline, version control model of space operations that provides a standard point of departure, which can rapidly be modified or tailored for quick turn studies with a focus on space. It is used in conjunction with the System Effectiveness Analysis Simulation (SEAS), V3.9 or higher. Using SEAS alone without Space Brawler required doing extensive research, manually coding parameters for each satellite, and modeling the Command and Control (C2) structure from scratch. Additional effort would be required to carefully construct the simulation to model space effects to the warfighter before one could investigate how the contribution of these space assets could be impaired by orbit degradation, maneuver, jamming, C2 constraints, Anti Satellites (ASATs) or a host of other threats to the orbital asset that the analyst may choose to investigate. The starting Space Brawler configuration contains a simple representation of normal peacetime operations. Satellite operations centers receive perception updates with rates

35    

and accuracies statistically matching that provided by the current Space Surveillance Network. By tracking the orbits of objects and monitoring the health of Space Vehicles, the Space Operations Centers (SOCs) decide how to command their satellites and how to request satellite control network resources to upload the commands. Operations that are currently automatically modeled in Space Brawler include Station Keeping (orbit maintenance), Collision Avoidance (COLA), and basic Defensive Counter Space (DCS) maneuvering which is designed to maintain a minimum separation distance between objects. All of the commands are scheduled for upload over the associated Satellite control network based on antenna status, visibility, and availability.

Almost all functions in Space Brawler are based perceived states rather than truth. Space Brawler represents four different and important states for a satellite:

1. The goal state (the orbit that it is trying maintain through station keeping) 2. The true state as a result of perturbations 3. The blue perceived state (referred to as blue perception) 4. The red perceived state (red perception)

These values are calculated by one of two methods. The first method is to use the Space Brawler internal statistical perception engine, called SEAS Space Situational Awareness (SSA) modeling. The second method uses an external Space Surveillance Network (SSN) modeling tool called the Maneuver Detection and Recovery (MDR) Tool. MDR has a separate representation of the SSN that is modeled to a high degree of fidelity outside of SEAS and Space Brawler. At this stage of development the tools are loosely integrated, data is exchange between the tools via temporary text files. An analyst requiring high fidelity starting perception can use MDR to drive perception orbits in Space Brawler but currently performance limitations make full catalog modeling with MSR prohibitive. MDR is most commonly used only for high interest objects.

SMC/AD is the model manager for both SEAS and Space Brawler, but does not manage MDR as it contains the AFSPC Astrodynamic Standards. These standards are under Export Control and fall under the International Traffic in Arms Regulations. There are three versions of Space Brawler, Unclassified, SECRET and Top Secret.

Synthetic Theatre Operations Research Model (STORM) STORM began in 1996 as a collaborative partnership with the Air Force National Air and Space Model (NASM) program to develop a new training simulation. Then known as NASM/AN (for NASM/Analytical, Next-generation), STORM shared a common need for appropriate representations of air and space systems and capabilities in the larger context of joint military operations. It also served in a similar role as the Air Force`s technical testbed in support of the DoD Joint Warfare System (JWARS). Over time, STORM gained sufficient momentum and credibility as both a simulation design and a software implementation to warrant the establishment of a dedicated effort to produce a modern campaign-level analytical tool for the Air Force. STORM was designed to anticipate and accommodate changes in both technology and analytical focus likely to occur over the course of 20 years. To promote adaptation, STORM incorporates the Common Analytic Simulation Architecture (CASA), an open-system/ open-source framework enabling a level of modularity that localizes the impact of structural modifications. This modularity facilitates replacement of both hardware and software elements in response to the inevitable technological evolution of hardware and software as well as the shifting analytical emphases that confront tools over the course of their use. STORM`s mission is to help analysts provide credible insights and useful information to senior decision- makers who must answer the "so what?" questions involving force structures, operational concepts and military capabilities. STORM is part of the Air Force Standard Analysis Toolkit (AFSAT). By

36    

enabling both broad and in-depth explorations of the utility and effectiveness of air and space power in a multi-service warfighting context, STORM continues to be a valuable asset to senior decision-makers in the policy, acquisition and operational communities.

System CONOPS and Requirements Environment (SCORE) SCORE is a packet level software environment that supports requirements/performance analysis and CONOPS development for single systems and systems of systems. Parsing this description allows the following summary of SCORE functionality:

• ‘Packet level software environment’ – Operational nodes in a SCORE configuration

are functionally connected via packets that are transmitted over a packet level communications network(s), thereby providing an architecture that supports: o Detailed CONOPS development o User Interface Template Library (UITL) operations o Integrated testing o Operator training

• ‘Supports both requirements/performance analysis and CONOPS development’ – SCORE runs in the batch mode for requirements/performance analysis and in the UITL mode for detailed CONOPS development; i.e., which commanders get what information, when do they get it, how is it presented, what is their response, etc.

• ‘Single systems and Systems of Systems’ – SCORE has been configured as a single system to support development and test of ground control software, system analysis, and operator training. System of systems configurations have been used for interactive war gaming as well as requirements/performance analysis. Typical SCORE ‘systems’ are Intelligence, Surveillance, and Reconnaissance (ISR) mission systems and their supporting communications network(s). The available span of typical SCORE configurations is implied in Figure 2 where:

• Tactical Ground Stations (TGS) make/receive ISR requests and communications support requests.

• Mission Ground Stations (MGS) are responsible for processing/scheduling TGS requests and commanding/controlling their particular family of ISR/communications assets.

• Tasking/Adjudication (TA) nodes provide a hierarchy for configurations with multiple space, air, and/or ground ISR platforms; e.g., guiding and assigning ISR requests to particular MGSs, providing communications connectivity, directing operations, etc.

 

37    

  ISR Systems Comm Systems Targets Space Platforms X X X Air Platforms X In Development X Ground Platforms X X X Command Nodes TGS MGS

TA Nodes TGS MGS Independently

programmed scenarios

NOTE: SCORE has a full capability for the cells marked with an “X” in the above table. System Effectiveness Analysis Simulation (SEAS) SEAS is a government-owned, agent-based military utility analysis tool sponsored by SMC/AD. SEAS has been in development for over 15 years and was designed specifically to give military operations research analysts and decision makers a flexible means to quickly explore new warfighting capabilities; in particular, those provided by Space and C4ISR systems.

SEAS represents the latest in analytic simulation technology and offers a powerful agent-based modeling and simulation environment in which small to large-scale joint warfighting scenarios can be constructed and explored to quantify the effectiveness of various system designs, architectures, and concept of operations (CONOPS). The ability to represent networked military units and platforms reacting and adapting to perception-based scenario dynamics in a 3-D physics-based Battlespace, makes SEAS ideally suited for exploring effects-based operations, network-centric warfare, and transformational warfighting concepts. THUNDER THUNDER is a two-sided theater-level, stochastic combat simulation and war game. It is designed to assist the analyst studying the impact of policy decisions, such as force positioning, alternative equipment choices, and theater-level tactics. The model simulates the air war to the level of detail of flight groups on missions. Individual air bases servicing aircraft are modeled. Air-to-air combat is on the flight group level.

Planning for the air war is accomplished by generating air-tasking orders from intelligence collected dynamically in the model. And from air resources, both collected dynamically and input. The missions are flown when aircraft are available.

A ground war is modeled as well as logistics and the availability of supplies modifies the effectiveness of the units. Command, control, communications, and intelligence (C 3 I) are also modeled, and affect unit effectiveness. Mobility is included and may modify the movement of units and supplies.

The ground war can be attacked from the air. The targets can be units, mobility (choke) points, C 3 I, and supplies in supply bases or convoys. The ground also has air defense and can attack the air. Interactions are computed dynamically.

THUNDER incorporates state-of-the-art modeling techniques that offer results to analysts evaluating aircraft systems with alternative munitions, mission areas, force , and threat scenarios. THUNDER is continually being upgraded and expanded to meet AF needs such as space and cyberspace capabilities.

38    

Appendix B The 15 Prioritized AFSPC Space Capabilities are:

1. Nuclear, Survivable Communications. Global satellite communications designed to operate in a highly contested environment in support of national and military needs. These types of satellite systems are designed to fight in and through an adversary’s denial and disruption techniques as well as continue to operate when exposed to high levels of man-made or environmental radiation.

2. Launch Detection/Missile Tracking. These space systems, often supported by ground- based radar systems, have sensors that detect the infrared heat signatures of missile and rocket launches around the world. Through a network of information sharing, this sensor data is processed to provide early warning of launches to US and coalition forces.

3. Position, Navigation and Timing (PNT). PNT, primarily supported by GPS, provides precise location, elevation, direction and speed for land, sea and airborne assets equipped with a receiver. The timing signal from these space-based systems is also used in many data transfer and communications systems that require precise timing signals.

4. Space Situational Awareness (SSA)& Battlespace Awareness (BA). Space situational awareness, or SSA, is comprised of both ground and space-based optical and radar systems that provide “visibility” into orbital operations, satellite position and space debris tracking. This information is provided to space operators for cataloging space systems, avoidance maneuver and protection. Battlespace Awareness is the knowledge gained from processing and presenting information necessary to plan and control military space operations.

5. Defensive Space Control (DSC). DSC consists of actions taken (e.g., certain maneuvers) or defensive sub-systems built into our space systems (e.g., shutters to protect sensors) that enhance the survivability of space systems when exposed to the natural environmental hazards of space or when purposely targeted by adversaries who possess electronic, high-energy or kinetic anti-satellite weapons.

6. Assured Space Access/Spacelift. The ability to launch payloads into space, which includes the launch range assets required to conduct space launches.

7. Space Command and Control (C2). Space C2 is the ability to provide reliable and unimpeded observation, orders, direction and effects-based monitoring for military space operations, space units and space systems.

8. Satellite Operations. Spacecraft and payload operations conducted to monitor, configure, maneuver, operate and sustain on-orbit assets. This includes telemetry, tracking and commanding (TT&C), maneuvering, monitoring state-of-health, and maintenance and sub- functions for the spacecraft and payloads.

9. Protected, Tactical Communications. Satellite communications which are designed to operate in a day-to-day and contested environment to support worldwide national and military communications.

 

10. Offensive Space Control. Operations conducted to prevent an adversary's hostile use of US and/or third party space capabilities and service, and to negate an adversary’s space capabilities (e.g. disrupt, deny, deceive, degrade, or destroy).

39    

11. Unprotected Communications. Satellite communications which are designed to operate in a day-to-day (benign) environment to support national and military communications worldwide.

12. Space-to-Surface Intelligence Surveillance and Reconnaissance (ISR). This capability is comprised of sensors that can detect or image objects, geographic features, physical change, movement of objects and electro-magnetic spectrum variances on the ground.

13. Terrestrial Environmental Monitoring. Characterization, analysis and prediction of meteorological and oceanographic environment factors (surface, sub-surface and air conditions) that might affect military operations.

14. Nuclear Detonation Detection. Persistent, global and integrated sensor capability providing global surveillance of nuclear detonations and their specific place, height of burst and yield.

15. Responsive Spacelift. The capability to rapidly deploy, augment or reconstitute satellites/ payloads, including the capability to responsively place payloads on orbit to meet the warfighter’s needs.

The 9 Prioritized AFSPC Cyberspace Capabilities are:

1. Proactive Defense. Comprises the continuous measures taken to secure and protect AF and DoD cyberspace assets from attack and exploitation.

2. Defensive Counter Cyberspace (Recon/Counter Recon). The employment of defensive measures that ensure the military can continue to operate in cyberspace.

3. Cyberspace Intelligence, Surveillance and Reconnaissance & Situational Awareness. The integration of systems in support of operations providing accurate, relevant and timely intelligence.

4. Persistent Network Operations. The continuous and agile operation of worldwide AF garrison and deployed networks.

5. Data Confidentiality & Integrity Systems. Activities that safeguard information that resides on the Air Force Network and is provided to the joint warfighter.

6. Cyberspace Operations Center. Activities that provide real-time command and control over military cyberspace forces.

7. Offensive Counter Cyberspace for Global Reach & Access. Operations conducted to project power against adversaries in or through cyberspace.

8. Net Extension and Resiliency. AF activities that extend and expand cyberspace services for military and business operations.

9. Influence Operations. Influence operations serve to amplify the effects of traditional military operations and influence perceptions and behaviors of leaders, groups or entire populations by means other than force (e.g., operations security, public affairs, counterintelligence operations, etc).  

40    

ACRONYMS

-A- ACC Air Combat Command AF Air Force AFRL Air Force Research Lab AFSIM Advanced Framework for Simulation, Integration and Modeling AFSPC Air Force Space Command AID Authoritative Information and Data AoA Analysis of Alternatives ASAT Anti-Satellite ASDA ASTRA Atmospheric & Space Technology Research Associates ATACM Army Tactical Missile System AVAC AFPSC Virtual Analysis Center -B- BA Battlespace Awareness BAM Break-Up Analysis Model -C- C2 Command and Control C4ISR Command, Control, Communication, and Computers ISR CASA Common Analytic Simulation Architecture CAVAC Classified AFSPC Virtual Analysis Center CAWG Campaign-Analysis Working Group CCB Configuration Control Board CCMD Combatant Command CDRL Contract Data Requirements List CNA Center for Naval Analysis COLA Collision Avoidance COMBO Computation of Miss Between Orbits COMM SQ Communications Squadron CONEMPS Concept of Employment CONOPS Concept of Operation CONUS Continental United States COR Contracting Officer Representative CSA Client Support Administration -D- DBDD

SCHWARZ, CHARLE…, 1/26/16 3:40 PMDeleted: ARTS

41    

DIS Distributed Interactive Simulation DISA Defense Information Systems Agency DLL Dynamic Link Library DoD Department of Defense DoE Design of Experiments DOP Dilution of Precision DSC Defensive Space Control -E- EADSIM Extended Air Defense Simulation -F- FAR Federal Acquisition Regulation FOR Field of Regard FOV Field of View -G- GEO Geosynchronous Orbit GFI Government-Furnished Information GFP Government-Furnished Property GIANT GPS Interference and Navigation Tool GPS Global Positioning System GVS Ground Vehicle Simulation -H- HAF Headquarters Air Force HDBT Hard and Deeply Buried Target HLA High-Level Architecture HQ AF Headquarters Air Force -I- IDA4D Ionospheric Data Assimilation Four-Dimensional IIS Information Internet Services INS Inertial Navigation System ISC Integrated Security Construct ISR Intelligence, Surveillance, and Reconnaissance IT Information Technology -J- J/S Jam-to-Signal Ratio JICM Joint Integrated Combat Model JMEM Joint Munitions Effectiveness Manual

42    

JMT Joint Mission Thread JWARS Joint Warfare System JWICS Joint Worldwide Intelligence Communications System -K- -L- LAMOD Look Angle Module LEO Low Earth Orbit -M- M&S Modeling and Simulation MAJCOM Major Command MANAL Maneuver Analysis MDA Missile Defense Agency MDR Maneuver, Detection, and Recovery MEO Medium Earth Orbit MGS Mobile Ground System MOE Measure of Effectiveness MOO Measure of Outcome MOP Measure of Performance MS&A Modeling, Simulation, and Analysis MSIC Missile and Space Intelligence Center MSR Monthly Status Report MW Missile Warning -N- NASA National Aeronautics and Space Administration NASIC National Air and Space Intelligence Center NASM National Air and Space Model NAVWAR Navigation Warfare NIPRNet Non-secure Internet Protocol Router Network NOAA National Oceanic and Atmospheric Administration NOS Network Operations Squadron NRO National Reconnaissance Office -O- OPLAN Operations Plan OSC Offensive Space Control OSSET Observation System Simulation Experiment Tool -P-

43    

PAFB Peterson Air Force Base PNT Position, Navigation, and Timing PoR Program of Record PWS Performance Work Statement -Q- -R- RAM Reliability, Availability, and Maintainability -S- SAAR System Authorization Access Report SAINT Space Analysis Integration Tool SAM Surface-to-Air Missile SARP Space and Cyberspace Analysis Resource Portal SATRAK Satellite Trajectory and Attitude Kinetics SC Space Control SCI Special Compartmentalized Information SCOM Software Center Operator Manual SCORE System CONOPS and Requirements Environment SCWG Space Control Working Group SDD Software Design Description SEAS System Effectiveness Analysis Simulation SFE Space Force Enhancement SIGINT Signals Intelligence SimOrb Simulation Orbits SIPRNet Secure Internet Protocol Router Network SLAMEM Simulation of Locations and Attack of Mobile Enemy Missiles SMC Space and Missile Center SMDC Space and Missile Defense Command SMTP Simple Mail Transfer Protocol SOC Space Operations Center SOPS Space Operations Squadron SOWG Space Operations Working Group SQL Sequel SRS Software Requirements Specifications SSA Space Situational Awareness SSAT Space System Analysis Team SSDP Space Security Defense Program SSN Space Surveillance Network STAC Space Threat Analysis Center STORM Synthetic Theater Operations Research Model

SCHWARZ, CHARLE…, 1/26/16 3:40 PMDeleted: ReACT Requirements Assessment and Cost Tool

44    

STR Software Test Report SUM Software User Manual SVD Software Version Description -T- TEL Transporter, Erector, Launcher TES TGS Tactical Ground Station TL Task Lead TMD Theater Missile Defense TS Top Secret TT&C Telemetry, Tracking, and Commanding TTP Tactics, Techniques, and Procedures TWG Threat Working Group -U- UITL User Interface Template Library URL Uniform Resource Locator USSTRATCOM United States Strategic Command -V- V&V Verification and Validation VSA Visitor Security Agreement -W- WMAT Warfighter Mission Analysis Team WWG Warfighter Working Group Wx Weather -X- -Y- -Z-