A9 MS2 20081106.docx

Performance Work Statement (PWS) Comment by steedj: Throughout this document, you need to specify how often/how many times. The contractor cannot price this out the way it is.

FOR

HQ AFSPC/A9F FORCE STRUCTURE ANALYSIS DIVISION

Modeling & Simulation for Space

1.0. DESCRIPTION OF SERVICES

Provide support to HQ AFSPC/A9 as outlined in the specific task section of this PWS. The contractor shall supply technical expertise and provide analytical support, to include training and transition assistance activities.

1.1. Organizations Supported:

HQ AFSPC/A9

250 Peterson Blvd, Suite 116 Peterson AFB CO 80914-4650

1.1.1. Mission. Assure AFSPC/CC decisions are underpinned by rigorous independent analysis—insight, oversight, on-site and provide technical expertise to the national security space community. Specific goals are: enhance space representation in DoD Analysis; provide technical expertise/analysis to the warfighter; assess space capabilities and operational risk; document and distribute lessons learned assessment and develop division personnel to provide world-class expertise.

1.2. Overview of Services. Provide technical support to in the area of Modeling and Simulations (M&S).

1.2.1. M&S. Provide M&S capabilities to implement Air Force Space Command (AFSPC) and the Space community requirements including the following:

1.2.1.1. Space related M&S information management such as data collection, data mining, data warehousing, data integration and data interoperability.

1.2.1.2. M&S tool research, development and innovation, such as system requirement research, design and development, validation and verification, testing and operationalization of such products.

1.2.1.3. Space related M&S information integration applying net-centric applications, web-based applications and leading edge technologies.

1.2.1.4. Department of Defense (DoD) and Air Force M&S Integrated planning to support Air Force Space Command, such as requirement definition, M&S need identification, and a multi-year plan for prioritized model enhancements. This includes modeling and simulation management, such as legacy system migration and integration, configuration management and control.

1.3. Specific Requirements for Modeling & Simulation for Space (MS2).

1.3.1. Authoritative Data (3600 Funds). Authoritative Data is an initiative to standardize Space system related data and information to support modeling and simulation efforts and provide this data through a reliable repository. This requirement will collect data from various offices and organizations. Some data will reside in multiple offices and shall be adjudicated producing one source and one data element that is acceptable to the Space community as a representation of the system in question. A data collection process will be developed to ensure this process is repeatable and sustainable. Development of this database and repository may create new security issues, particularly when combining data from multiple sources. Comment by steedj: By the contractor or the government? (Gue– by the contractor)

1.6.1.1. Authoritative Data Process Development.

1.6.1.1.1. Develop a work plan (para. 1.6.1.2.1.) and implement this process to expedite data generation and database population and provide effective data management and data currency.

1.6.1.1.2. Update current Authoritative Data planning documentation (para. 1.6.1.2.2.), such as the Configuration Management Plan, Functional Test Plan, and other plans.

1.6.1.1.3. Update current Authoritative Data technical documents (para. 1.6.1.2.3), such as the Requirements, Concept of Operations (CONOPS), and other documents.

1.6.1.2, Classified Authoritative Data Development. Populate classified Authoritative Data database(s) (deliverable 1.6.1.2.4.) for the following requirements:

1.6.1.2.1. Develop classified, releasable Authoritative Data for 2007-2025 in one year increments representing AF Space Command systems (ground, air and space), sensors and networks. Comment by steedj: ??(Gue-archival data is just as important as future data and is actually easier to research)

1.6.1.2.2. Develop classified, releasable Authoritative Data for 2007-2025 in one year increments representing all U.S. space systems (ground, air and space), sensors and networks. Comment by steedj: ?? Gue-archival data is just as important as future data and is actually easier to research)

1.6.1.2.3. Develop classified, releasable Authoritative Data for 2007-2025 in one year increments representing all non-U.S. space systems (ground, air and space), sensors and networks. Comment by steedj: ?? Gue-archival data is just as important as future data and is actually easier to research)

1.6.1.2.4. Develop classified, releasable Space input files for AFSPC M&S Toolkit models/simulations.

1.6.1.3. Authoritative Data Repository.

1.6.1.3.1. Establish and develop agreements, documents and processes to enable past-use data files to be accessible through the Space Analysis Resource Portal (SARP) as reference/repository information (an example is the Schriever IV data files used to support the wargame).

1.6.1.3.2. Establish and develop agreements, documents and processes to enable model/simulation input and output file access through the SARP [an example is Global Positioning System (GPS) Interference and Navigation Tool (GIANT) input and output information to support an Analysis of Alternatives (AoA)].

1.6.1.3.3. Mitigate, document and resolve all security classification issues for unclassified and classified networks.

1.6.1.4. SARP Modifications for Incorporating Authoritative Data. Develop and implement code changes to the SARP (para. 1.6.1.7.) in accordance with requirements. Coordinate testing and implementation of changes with appropriate offices, such as the unclassified and classified network administrators, The SARP is based on Microsoft Visual Studio, SQL Server, and DataDynamics Active Reports software. Comment by steedj: Is there something missing here?

1.6.1.5. Unclassified Authoritative Data Development. Populate Authoritative Data database(s) with the following:

1.6.1.5.1. Develop an unclassified, releasable Authoritative Data for 2007-2025 in one year increments representing AF Space Command systems (ground, air and space), sensors and networks. Comment by steedj: ??

1.6.1.5.2. Develop an unclassified, releasable Authoritative Data for 2007-2025 in one year increments representing all U.S. space systems (ground, air and space), sensors and networks. Comment by steedj: ??

1.6.1.5.3. Develop an unclassified, releasable Authoritative Data for 2007-2025 in one year increments representing all non-U.S. space systems (ground, air and space), sensors and networks. Comment by steedj: ??

1.6.1.5.4. Develop required unclassified, releasable Space input files for AFSPC M&S Toolkit models/simulations.

1.6.1.7. Deliverables: Authoritative Data Work Plan (CDRL 0034) Configuration Management and Functional Test Plans (CDRL 0038) Requirements and CONOPS Technical Documents [CDRL 0036] Classified Authoritative Data databases and information (CDRL 0014) Data Release Agreements (CDRL 0036) Enhanced SARP code to support Authoritative Data (CDRL 0014) Unclassified Authoritative Data databases and information (CDRL 0014)

1.6.2. Modeling and Simulation (M&S) Research and Development: Space Enhancements (3600 Funds).

1.6.2.1. Update, modify and develop M&S tools representing space systems and space utility for the Space and DoD analysis community to include government and non-government entities. Develop modules in collaboration with model managers and associated model development contractors. Provide an M&S Tool Enhancement Plan for each modification (para. 1.3.2.2.1), identifying the schedule for key activities to accomplish enhancements. The software design document (para.1.3.2.2.2) will describe the software development approach to produce the desired model functionality and ultimately lead to new software code and documentation (para. 1.3.2.2.3). Comment by steedj: Who is this? Lum-These are the recognized developers of the tool selected for mod/upgrade. Exemplar tools are listed in 1.6.2.1.1.

1.6.2.2. Specific tasks may involve a number of M&S tools. (Specific M&S tools considered for enhancements will change over time based on future M&S capabilities and requirements.) The following M&S tools are likely candidates for enhancement: EADSIM, GIANT, SEAS, SLAMEM, SPAAT, SSNAM, and STORM.

1.6.2.3The specific tasks will address the following mission areas and capabilities:

1.6.2.3.2 Space Force Application (FA)

1.6.2.3.3 Counterspace (CS)

1.6.2.4. Deliverables: M&S Tool Enhancement Work Plan (CDRL 0034) M&S Tool Software Design Document (CDRL 0015) M&S Tool Software Code and Documentation (CDRL 0014)

1.6.3. Space Analysis Resource Portal (SARP) (3400 funds). SARP is a webpage/website currently residing on the Peterson AFB Non-secure Internet Protocol Router Network (NIPRNet). It is a Microsoft SQL Server database with multiple supporting software packages such as IIS, Office, Adobe Acrobat and SMTP services. It is currently developed in Microsoft Visual Studio with .NET framework. Additional requirements to “hosting” the SARP are to meet Air Force and DoD directives to migrate sites to the AF Portal. The SARP will also be hosted on the Secret Internet Protocol Router Network (SIPRNet) in accordance with Air Force directives.

1.6.3.1. Develop a SARP O&M Work Plan (deliverable 1.3.3.2.1) for continuation of operations and maintenance of the SARP in accordance with AFSPC/A9 requirements. Maintain detailed information about space models and simulations; update the repository for space model studies, comparisons, briefings, accreditations etc.; support a user forum for discussion and resolution of implementation issues (e.g., selecting appropriate measures) on model, simulations and studies; and control user access to authoritative space system information.

1.6.3.2. Recommend innovative techniques and improvements utilized by other DoD activities with relevant and similar efforts. These may be developed and implemented as a version release to the current SARP site (deliverable 1.3.3.2.2 and 1.3.3.2.3) following documentation and test. Update SARP documentation to reflect new capabilities, such as the Software Version Description Document (SVDD) and the Database Data Dictionary (DBDD) (deliverable 1.3.3.2.4).

1.6.3.3. Yearly requirements include best-practices network management tasks, such as normal-duty-hour help desk functions, administrative and security functions, testing, development and implementation of upgrades. Comment by steedj: Do you mean this is on-going requirements or just something they do one time per year? (Gue – on-going activities – normal website maintainance)

1.6.3.4. Deliverables: SARP O&M Work Plan [CDRL 0034]

Unclassified Space Analysis Resource Portal (SARP) (CDRL 0014) Classified Space Analysis Resource Portal (SARP) (CDRL 0014) SARP SVDD and DBDD (CDRL 0036)

1.6.4. AFSPC M&S Integrated Plan and M&S Management (3400 funds). Update the five-year M&S Integrated Plan (M&S IP) annually to align with the AFSPC Program Objective Memorandum (POM) development. Interim updates shall reflect completion of M&S tool developments and improvements, newly proposed M&S tool developments and improvements, and changes in AFSPC M&S requirements. The M&S IP shall support an iterative process of assessing AFSPC M&S requirements, current capabilities and shortfalls, alternative solutions for shortfalls, and results of the M&S value model for prioritization of alternative solutions. The M&S Management implements those responsibilities as outlined in AF Policy Directive 16-10.

1.6.4.1. Develop an M&S IP Work Plan (deliverable 1.3.4.3.1) to produce the five-year M&S Integrated Plan and an interim update each year. The M&S IP Work Plan will provide a schedule for the following tasks.

1.6.4.1.1. Update model questionnaires (deliverable 1.3.4.3.2) to establish the model’s effectiveness and suitability to support AFSPC M&S needs. Questionnaires will also be completed on variations of models designed to enhance the model’s capability and the associated cost.

1.6.4.1.2. Develop M&S Support Plans (MSSPs) (deliverable 1.3.4.3.3) for each tool in the Space Analysis Toolkit. MSSPs provide critical information needed to support updating, modifying, and developing M&S tools and help ensure M&S tools meet standards, are operationally available when needed, can be sustained throughout intended use, and have an improvement plan in place to meet current and future AFSPC analysis needs.

1.6.4.1.3. Generate a prioritized list of M&S tool modifications (deliverable 1.3.4.3.4) by using model questionnaires for input to execute the value model.

1.6.4.1.4. Complete the M&S IP and provide an interim update (deliverable 1.3.4.3.5) based on results of model questionnaires, MSSPs, and the value model.

1.6.4.2. Evaluate tool capabilities described in model questionnaires and MSSPs against acceptance criteria described in AFSPCI 16-101for potential acceptance to or removal from the Space Analysis Toolkit (deliverable 1.3.4.3.6).

1.6.4.3. Develop business-standard and maintain software and associated hardware throughout the software life-cycle such as configuration control and management (deliverable 1.3.4.3.7); requirements collection and documentation; user assistance through software documentation and training (deliverable 1.3.4.3.8); discrepancy reporting and documentation (deliverable 1.3.4.3.8); and testing, implementation and software distribution.

1.6.4.4. Deliverables: M&S IP Work Plan [CDRL 0034], model questionnaires [CDRL0036], MSSPs [CDRL 0036], value model results [CDRL 0036], AFSPC M&S Integrated Plan [CDRL 0036], recommendations for Space Analysis Toolkit model acceptance and removal [CDRL 0036], version release documentation [CDRL 0025], training materials and/or courseware [CDRL 0013], and software change control document(s) [CDRL 0036].

2.0. SERVICES SUMMARY.

The Service Summary (SS) is a list of Performance Objectives and Performance Thresholds that will be regularly verified by Government personnel. Each Performance Objective represents a significant task as identified in the PWS by the Government at the time of contract award. The Performance Threshold represents the minimum acceptable level of performance. The Performance Objectives and Performance Thresholds represent only the significant tasks of this contract and do not excuse the Contractor from performance of other responsibilities identified in this PWS. Performance Objectives will be monitored regularly by Government Quality Assurance Evaluators (QAEs). Performance objectives may be added at the basic contract and/or task order level and performance thresholds may be raised or lowered during the course of this contract.

2.1. Findings. A finding is any government-identified noncompliance with contract requirements that specifies that an activity or action did not take place, or did not take place to the standards of timeliness or quality required. A Finding is categorized as either a Major or Minor Finding. Findings will be documented on a Corrective Action Report (CAR) and provided to the Contractor for their response. While the Contractor will be given the opportunity for reperformance when possible, the deficiency will nevertheless be documented.

2.2. Performance Objectives.

(SDS-1) Provide accurate technical and analytical advice, guidance and products as required by individual task orders.

Contractor receives no more than one formal customer complaints/contract discrepancy reports per year for each task order. Contractor successfully resolves any customer complaint within 10 working days of receipt or less time as specified in the task order.

(SDS-2) Provide timely response to time-sensitive requirements, including short notice requirements and a large number of requirements in a short period (surge capability).

Contractor receives no more than one formal customer complaint/contract discrepancy report per year from all task orders.

(SDS-3) Compliance with DD 254, Contract Security Classification Specification, to include proper handling, storage, transmission, and destruction of classified materials.

No security violations.

(SDS-4) Requirements/deliverables completed in an accurate, timely manner in compliance with individual task order requirements.

No more than three late documents per year per task order and no more than 2 working days late. No more than two sets of corrections/edits and all corrections must be accomplished within two working days, or other such time periods as established in the task order.

3.0. GOVERNMENT FURNISHED PROPERTY AND SERVICES.

3.1. The Government will furnish up to two workspaces in Building 1470 at Peterson AFB, CO, to include desk space, chair, computers (connected to e-mail, NIPRNET, SIPRNET, and AFSPC Virtual Analysis Capability) and telephone and use of copier and fax machines. All other contractor personnel shall work at contractor facilities.

3.2 The government will provide the following hardware and equipment.

DELL Inspiron 9400 Laptop T5600 1.83GHz, 2GB SDRAM ST# 25SW5C1

CN-0YD479-12961-6B3-6385

3.3. Software. The government will provide the following MS2 Software:

Space Analysis Resource Portal (SARP) code Space Authoritative Information and Data (Space AID) Astrodynamic Standards Software: Dynamic Link Library (DLL)s, source code, documentation, sample input and output files, and drivers for the following Astrodynamics Standards Software: Contractor shall obtain a Memorandum of Agreement for release of HQ AFSPC astrodynamic software, per instructions in AFSPCI 33-105).

Simplified General Perturbations 4 (SGP4):

Special Perturbations Ephemeris (SPEPH), (also called SP or EPHEM) Initial Orbit Module (IOMOD) Look Angle Module (LAMOD) Report/Observation Association (ROTAS) Computation of Miss Between Orbits (COMBO) Field of View (FOV) Area Overfly (AOF) Batch Differential Correction (BATCHDC) Sequential Differential Correction (SEQDC) Versatile Difference and Compare Tool (VERDICT) executable, Visual Studio workspace, sample files and documentation for testing.

SATRAK executable, source code and build files.

Space Common Operating Picture and Exploitation Tool (SCOPES) executable, documentation and specified subset of source code from Integrated Space Situation Awareness (ISSA) 5.01 described below to support the development of Space Analysis Integration Tool (SAINT).

World Wind source code with modifications by Space Innovation & Development Center (SIDC) to correctly represent space and the following:

Interface code for all developed DLLs, taking an XML input file and converting to the Astrodynamics Standards DLL input (ASCII) file.

Interface code, taking the Astrodynamics Standards DLL output (ASCII) file and converting to Exchange Markup Language (XML).

XML input files for each DLL.

3.4. Materials and Other Direct Costs (ODCs). The QAE shall approve all contractor purchases costing less than $500. Any item exceeding this dollar threshold will require approval of the Contracting Officer prior to purchase.

3.5. Product Ownership. All products produced by the Contractor in performance of this PWS are sole property of the Government.

3.6. Proprietary Data. The Contractor shall request approval prior to the use of any proprietary data or software tools to fulfill requirements of this PWS.

3.7. Government Furnished Information, Specifically MS2. Government personnel shall be available for technical exchanges with the Contractor. The Government will furnish this documentation for reference:

AFSPCI 16-101

AFSPC M&S Integrated Plan Value Model MSSPs Model Questionnaire Space Analysis Toolkit Acceptance Criteria SARP code, site access and associated documentation

4.0. TRAVEL.

Contractor employees may be required to travel to various locations within the continental United States (CONUS) in performance of task orders. Estimated travel requirements are included below. All contractor travel shall be approved by the Government prior to departure. Any travel required shall be performed in accordance with FAR 31.205-46, Travel Costs.

(does not include travel time)

4.0. SECURITY.

4.1. All contractor personnel shall hold a TOP SECRET/SCI clearance or higher. Contractor personnel shall possess appropriate security clearances as of the contract start date. The Contractor will be given access to applicable documentation to include requirements, plans, specifications, studies, and analyses up to and including TOP SECRET/SCI classification. The Contractor shall maintain accountability records/receipts for classified material to include transfer and destruction of material.

4.2. Contractor shall provide personnel with clearances commensurate with the BASIC AWARD DD Form 254, DoD Contract Security Classification Specification. Two Sensitive Compartmented Information (SCI) billets are available.

4. 2. All tasks must be conducted in full compliance with DoD security regulations. Where necessary, the contractor shall conduct work within SCI Program Channels.

4. 3. All contractors must review and comply with the Security Classification Guide (SCG) for the project area they are assigned.

4. 4. Restricted Area Badges. All personnel requiring frequent entry to Peterson AFB and Schriever AFB shall be provided access in accordance with AFI 31-101, The Air Force Installation Security Program. Furthermore, access to other locations may be provided upon request for support of this contract and access to classified national security information may require Top Secret/SCI clearance.

4.5. Access to classified national security information up to Top Secret/SCI is required.

4.6. A9A SSNAM Lab support person will need a Top Secret (TS)/sensitive Compartmented Information (SCI) clearance to gain access to the A9A SSNAM Lab and run analysis.

5.0. SERVICES DURING CRISIS.

The performance of these services is non-mission essential during times of crisis. Should a crisis be declared, the Contracting Officer or their representative will verbally advise the contractor if temporary suspension of work is required, followed by a written notification. A representative of the contracting officer will further notify the contractor verbally when the crisis is ended, with written notification to follow. Any price change resulting from this crisis will be negotiated in accordance with FAR clauses for “Changes”.

6.0. GENERAL INFORMATION

6.1. Supervision of Employees. The Government shall not supervise or otherwise direct contractor employees. The Contractor shall not supervise or otherwise direct government employees, nor shall the Contractor supervise employees of other contractors outside the Contractors’ own subcontracting/teaming arrangements.

6.2. Contractor Identification. All contractor personnel shall be required to wear company identification badges so as to distinguish themselves from government employees. These badges must be visible at all times when working with government personnel. When conversing with government personnel during business meetings, over the telephone or via electronic mail, support contractor personnel shall identify themselves as such to avoid any perception that they may be government employees and to avoid situations arising where sensitive topics might be better discussed solely between government employees. Electronic mail signature blocks shall identify contractor/company affiliation. Documents or reports produced by contractors shall be suitably marked as contractor products or contractor participation appropriately disclosed. Contractor personnel occupying collocated space in a government facility shall identify their workspace area with their name and company/contractor affiliation.