PWS - SW Development_v4_23 Oct 08_gju

PERFORMANCE-BASED WORK STATEMENT

FOR

AIR FORCE FLIGHT TEST CENTER, 412th TEST WING, 412th ELECTRONIC WARFARE GROUP

SOFTWARE DEVELOPMENT

AIR FORCE FLIGHT TEST CENTER

AIR FORCE MATERIEL COMMAND

EDWARDS AFB, CA 93523-5000

NAME OF CENTER

CENTER ADDRESS

10 April 2008XXX Table of Contents

Section Page

31.0

DESCRIPTION OF SERVICES/GENERAL INFORMATION

31.1 Introduction

31.2 Scope

31.3 General Requirements

31.3.1 Personnel Requirements

41.3.2 Data Analysis

41.4 Technical Requirements

41.4.1 Software Development

51.4.2 Data Reduction and Analysis Software

51.5 Program Management

51.5.1 Program Manager

51.5.2 Project Management

61.5.3 Configuration Management and Quality Assurance

61.6 Travel

1.7 Documentation

1.7.1 Apllicable Documents

1.8 Security Requirements

1.8.1 NISPOM

1.8.2 Security Clearances

1.8.2 Physical Security

1.9 Records

1.10 Security Requirements

1.10.1 NISPOM

1.10.2 Security Clearances

1.10.3 Physical Security

1.11 Quality Control

1.11.1 Quality Control Plan

1.11.2 Quality Assurance

92.0

SERVICES SUMMARY

113.0

GOVERNMENT-FURNISHED PROPERTY AND SERVICES

4.0

APPENDICES

SECTION C-1

1.0 DESCRIPTION OF SERVICES/GENERAL INFORMATION

1.1 Introduction

This Performance-based Work Statement (PWS) outlines the requirements for an Engineering Services contract in support of the 412th Electronic Warfare Group (EWG) at Edwards AFB (EAFB), CA. The Program Management Office (PMO) for this effort will be comprised of personnel from the 771st Test Squadron (TS).

1.2 Scope

This PWS describes the requirements to provide Software Development support for existing EW quick look data analysis toolset [i.e., Quick Look Tool Set (QTS)] for the 771st TS and to perform quick look analysis of EW data post-test missions as required to continue the tools development or troubleshoot problems with the existing capabilities of the toolset. Required services include: scientific engineering services with thorough knowledge of advanced EW, ECM and RF threat system design principles and the ability to review and assess their operation and performance; operation and maintenance of test equipment and their application to advanced Radar and EW testing; operation, resources, equipment, and limitations of the Open Air Ranges (OAR); knowledge of flight data analysis software programs for quick and accurate reduction and analysis of large volumes of flight test data from multiple sources; demonstrated understanding of the operations, characteristics, limitations and capabilities in the conduct of various EW systems; and proficient in software development using C/C++.

1.3 General Requirements

The contractor shall support development of the QTS software to include the use of this tool, or of any other tool developed under this contract, to assist the 771st TS in performing post-mission quick look analysis as required to continue the tools development or troubleshoot problems with the existing capabilities of the toolset. The software shall be developed to provide a rapid and semi-automated Personal Computer (PC) based quick look tool to support reduction and analysis of EW data. The contractor shall provide additional software development in support of the squadron efforts underway at various Combined Test Forces (CTFs) at the AFFTC.

1.3.1 Personnel Requirements

To immediately support testing at AFFTC, contractor personnel must have prior and unique detailed knowledge of the AFFTC and Participating Test Organization (PTO) test ranges. The contractor must have locally operated offices with the required expertise readily available to the EWG. The contractor shall have personnel with a demonstrated background in the following areas:

1.3.1.1 The contractor shall have personnel proficient in the technical theory and testing of Radar detection and processing algorithms, Electronic Countermeasures (ECM) receiving and jamming systems, Radar versus ECM evaluation, Electronic Counter Countermeasures (ECCM) assessment and Radio Frequency (RF) interference mechanisms.

1.3.1.2 The contractor shall have personnel proficient in RF threat system design principles and be capable of reviewing and assessing their operation and performance.

1.3.1.3 The contractor shall have personnel familiar with the operation and maintenance of general and special test equipment and their application to advanced Radar and EW testing.

1.3.1.4 The contractor shall have personnel familiar with the operation, resources, equipment, and limitations of the Edwards AFB AFFTC, the China Lake Naval Weapons Center Echo Range, and the Nellis AFB Nevada Test and Training Range (NTTR).

1.3.1.5 The contractor shall have personnel with an established and accepted knowledge of flight data analysis software for quick and accurate reduction and analysis of large volumes of flight test data from multiple sources. The data analysis programs shall be compatible with multiple aircraft (i.e. F-22, B-1B, F-117, F-16, F-15, etc.), Time/Space Position Information (TSPI), and other data formats at the Edwards AFB AFFTC, the China Lake Naval Weapons Center Echo Range, and the Nellis AFB NTTR.

The contractor shall have personnel with a demonstrated understanding of the operations, characteristics, limitations and capabilities in the conduct of “Ground Mount” Hardware In The Loop (HITL), System Integration Laboratory (SIL) and Installed System Test Facility (ISTF) testing of various EW systems.

1.3.1.6 The contractor shall have personnel with experience in software systems design. The experience shall include direct experience in Software Requirements Analysis, Software Architectural Design, Software Detailed Design, User Interface Design, Implementation and Testing, System Integration and Testing, Documentation, Task Management, Data Management Support, Risk Reduction Support, Software Configuration Management, Software development using the C/C++ programming languages for QTS development.

1.3.2 Data Analysis

1.3.2.1 The contractor shall further develop and use their software tools under this contract to support quick look data analysis development for the CTFs at the AFFTC. The contractor data analysts must possess the experience described in paragraph 1.4 and have a Top Secret (TS) clearance with a “current” (within the last 5 years) Special Background Investigation.

1.3.2.2 There shall be no TS data processed at the contractor facility under this contract.

1.4 Technical Requirements

The following section describes the technical services that may be performed under this contract. These services may be provided in one or more of the following task areas.

1.4.1 Software Development

The contractor shall provide develop additional features for the QTS currently in use at the AFFTC. This includes technical assistance in the use of the QTS, setup and developing user-defined modifications, and problem resolution. As new data formats or user requirements develop, the contractor shall provide the insight, knowledge and software support to integrate them into the existing QTS. New QTS Software will be developed for hosting on a PC based operating system as required by the user. This task will include the design, coding, and support of integration testing of this new data reduction and analysis system capability. It also includes modifying the existing QTS Software as required. Periodically, the contractor shall review and analyze lessons learned during previous builds, and update the SDP process to reflect those lessons learned.

1.4.2 Data Reduction and Analysis Software

The contractor shall provide data reduction and analysis software support using a new PC based program developed for this project based upon demonstrated and proven data analysis programs such as the FTDA Software (FTDAS) currently in use at several Air Force test facilities. This new data analysis program shall have the capability to merge data from multiple sources including instrumented test beds; TSPI, Radar and EW ground sites, and telemetry data. The data analysis program(s) shall be able to reduce data and provide tabular as well as graphical data products. As a goal, quicklook data products should be available within two (2) days after all data has been received. Additionally, the contractor shall pursue the development of capabilities within the existing toolset. As a minimum this should include the calculations of Measures of Performance and/or Measures of Effectiveness, and also the preparation//conversion of raw data into a format that is usable for QTS and/or other analysis tools.

1.4.3 Deliverables

Deliverable software elements shall include documentation source code listings and files, object files, source code and executable files. Documentation shall include both software description documents and user manuals. All deliverable software elements shall be delivered under configuration management as stated in paragraph 1.5.3. Deliverable software elements and documentation shall be delivered on CD ROMs. Deliverable software elements shall use a file format that is compatible with the disk device subsystem of the target operating system. The data organization within such files shall be as required for input to other software (e.g. compilers, etc.) or an input by other software (e.g. object files). Documentation shall be delivered in contractor format with prior government approval of the contractor’s suggested format.

1.5 Program Management

The contractor shall designate a focal point to act as an overall interface between the contractor and the PMO. Subordinate contractor focal points shall be designated to handle day-to-day tasking, planning, work load execution and coordination with their government counterpart or Task Managers. Other program management support as described below shall be provided.

1.5.1 Program Manager

The contractor shall designate a Program Manager (PM) responsible for all contract efforts. This person shall be the primary point of contact for programmatic issues. The contractor shall designate an alternate PM designated to act in behalf of the PM during absences.

1.5.2 Project Management

The contractor shall establish and maintain project management processes to define and track work, work assignments, budgets and costs, schedules, progress and status of the major tasks, including software development. Issue informal brief monthly management progress reports to the PMO summarizing the status of each major function/task, including the cost and schedule estimates, and software development metrics.

1.5.3 Configuration Management and Quality Assurance

The contractor shall provide Configuration Management and Quality Assurance functions in the performance of this contract. The Configuration Management and Quality Assurance procedures and methods shall be IAW and compatible with the systems used at the AFFTC. The contractor shall keep copies of outdated versions of software and course training materials on hand in case there is a need to roll back to a previous version. The contractor shall track all software changes and enhancements suggested by both the contractor and the PMO. As a minimum, this tracking shall include: descriptions of the requested enhancement, software version used when the enhancement was suggested, descriptions of the actual software change, a summary of why the software change did not meet the full request (when applicable), the software version which first incorporates the enhancement, and the software version which first incorporates changes to the help files (where applicable). All software, course materials, and related help files should be marked with a revision number, release (or presentation) date, or both. Additionally, users of all software products should have easy access to the version number of that software.

1.6 Travel

Contractor personnel shall be available to travel to test ranges and other sites to attend software Technical Interchange Meetings (TIMs), data coordination meetings, set up tool and process data.

1.7 Documentation

The PMO will provide available documentation. Documentation includes relevant manuals, operating procedures, specifications for Commercial-off-The-Shelf (COTS) instrumentation and equipment, configuration management information.

1.7.1 Applicable Documents

The following documents are listed for reference purposes only. The contractor shall perform all tasks described in the PWS using the listed documents as guidelines. In the event of a conflict between the documents and the PWS, the PWS shall be the superseding requirement.

Standard/Document Number

Title

AFFTC I 99-1

Test and Evaluations Test Plans

AFI 99-101

Developmental Test and Evaluation

AFI 990102

Operational Test and Evaluation

AFR 55-30

Operations Security

AFMCP 91-1

Flight Safety Planning Guide for Flight Testing

AFMCPD 99-1

Test and Evaluation (T&E) Risk Management

AFFTC-TIH-93-01AFFTC Test Plan Preparation Guide

AFFTCI 99-4

Test Program Deficiency Reporting

AFFTCI 99-5

Test Control And Conduct

AFI 16-20 (C)

Disclosure of Information to Foreign Governments and

International Organizations

National Industrial Security Program Operation Manual (NISPOM) dated Jan 1995

NISPOM supplement dated February 1995

DoD Overprint to the NISPOM supplement dated Jan 1998

Program Security Directive (PSD)

Security Classification Guide (SCG)

DOD 3200.12

DOD Scientific and Technical Information Program

22 CFR 120-130

International Traffic in Arms Regulation

1.9 Records

The contractor shall be responsible for creating, maintaining, and disposing of only those government required records that are specifically cited in this PWS or required by the provisions of a mandatory directive listed in Para 1.7.1 Applicable Documents. If requested by the Government the contractor shall provide the original record or a reproducible copy of any such record within 5 working days of receipt of the request.

1.10 Security Requirements

1.10.1 National Industrial Security Program Operation Manual (NISPOM) compliance

The contractor shall comply with the National Industrial Security Program Operation Manual (NISPOM) dated January 1995; the NISPOM supplement dated February 1995, the DoD Overprint to the NISPOM supplement, dated January 1998, the Program Security Directive (PSD) and Security Classification Guide (SCG). The PSD and SCG will be provided under separate cover.

1.10.2 Security Clearances

The contractor personnel assigned to this contract performing test conduct and data analysis shall possess a TS clearance. The personnel assisting in test planning shall at a minimum possess a “current” (within the last 5 years) SECRET clearance. The contractor shall provide adequate personnel with special access clearances for the purpose of visiting classified test ranges and sites.

1.10.3 Physical Security

1.10.3.1 The contractor shall be responsible for safeguarding all government property provided for contractor use. At the end of each work period, all government facilities, equipment and materials shall be inventoried and secured.

1.10.3.2 Key Control: As required.

1.11 Quality Control

The contractor shall submit a software quality control plan to the PMO for approval within 3 weeks (15 business days) after the award of the contract.

1.11.1. Quality Control Plan (QCP) shall include:

1.11.1.1 A description of the self-inspection system to cover all services. Description shall include specifics as to the area to be inspected on a scheduled and unscheduled basis, frequency of inspections, and the title and organizational placement of the inspectors.

1.11.1.2 A description of the methods to be used for identifying and preventing defects in the quality of service performed.

1.11.1.3 A description of the records to be kept to document inspections and corrective or preventive actions taken.

1.11.1.4 The records of inspections shall be kept and made available to the government throughout the contract performance period and for the period after contract completion until final settlement of any claims under this contract.

1.11.2 Quality Assurance

1.11.2.1 In accordance with contract clause 52.212-4, entitled "Contract Terms and Conditions--Comercial Items", the government will evaluate the contractor's performance under this contract. The Quality Assurance Personnel (QAP) or evaluators will follow the methods of surveillance specified in the contract and Performance Plan (PP). Government personnel will record all surveillance observations. When an observation indicates defective performance, the QAP will require the contract manager or representative at the site to initial the observation. The initialing of the observation does not necessarily constitute concurrence with the observation, only acknowledgment that he or she has been made aware of the defective performance. Government surveillance of tasks not listed in the Services Summary (SS) or by methods other than those listed in the Performance Plan (such as provided for by the Inspection of Services clause) may occur during the performance period of this contract. Such surveillance will be done according to standard inspection procedures or other contract provisions. Any action taken by the contracting officer as a result of surveillance will be in accordance to the terms of this contract.

1.11.2.2 Performance Evaluation Meetings. The contracting officer may require the contract manager to meet with the contracting officer, contract administrator, QAP, and other government personnel as deemed necessary. The contractor may request a meeting with the contracting officer when he or she believes such a meeting is necessary. Written minutes of any such meetings shall be recorded in the contract file and signed by the contract manager and the contracting officer or contract administrator. If the contractor does not concur with any portion of the minutes, such nonoccurrence shall be provided in writing to the contracting officer within 10 calendar days following receipt of the minutes.

SECTION C-2

SERVICES SUMMARY

2.0 SERVICES SUMMARY

The contractor service requirements are summarized into performance objectives that relate to mission essential items. The performance thresholds briefly describe the minimum acceptable levels of service required for each requirement. These thresholds are critical to mission success.

Service Summary

Paragraph Performance Threshold

Available 90% of time (Comparison of available to required staffing)

SECTION C-3

GOVERNMENT-FURNISHED PROPERTY AND SERVICES

3.0 The government will provide the equipment, materials and services listed below:

3.1 The following items will be provided as Government Furnished Equipment (GFE):

· PC computers with Windows( operating environment

· At least one copy of Mathworks MATLAB with a current license

· The contractor will be provided with adequate GFE to reduce data from multiple type mediums (Hi8 video tapes, CVD, CD, optical disks, etc.), process and manipulate the data (Hi8 players, DVD/CD ROMs, optical disk drives, etc.), display data (see first bullet above), print hard copy and archive data on optical disk and magnetic medium. All PMO-provided data required for this effort will be in a PC-readable format.

3.2 On-site support services as required.

3.3 The contractor shall have an established and approved government property administration organization at the AFFTC to manage, control, and account for government property in possession or under control of the contractor as a result of this contract.

APPENDICES

SECTION C-4

ACRONYMS

4.0 ACRONYMS

AFFTC

Air Force Flight Test Center

CDR

Critical Design Review

COTS

Commercial Off the Shelf

CTF

Combined Test Force

DoD

Department of Defense

EAFB

Edwards Air Force Base

ECM

Electronic Countermeasures

ECCM

Electronic Counter-Countermeasures

ECN

Engineering Change Notice

EW

Electronic Warfare

FMS

Foreign Military Sales

GFE

Government-Furnished Equipment

GFI

Government-Furnished Information

HITL

Hardware-in-the-Loop

IR

Infrared

IRCM

Infrared Countermeasures

ISTF

Installed System Test Facility

MOE

Measure of Effectiveness

MOP

Measure of Performance

MOPAT

Measure of Performance Analysis Tool

NISPOM

National Industrial Security Program Operation Manual

NTTR

Nevada Test and Training Range

NWC

Naval Warfare Center

PC

Personal Computer (IBM compatible processors)

PDR

Preliminary Design Review

PM

Program Manager

PMO

Program Management Office

PP Performance Plan

PSD

Program Security Directive

PTO

Participating Test Organization

PWS Performance-based Work Statement QCP Quality Control Plan

QTS

Quick Look Tool Set

RF

Radio Frequency

RTO

Responsible Test Organization

SAM

Surface to Air Missile

SCCB

Software Configuration Control Board

SCG

Security Classification Guide

SCMP

Software Configuration Management Plan

SCR

Software Change Requests

SIL

System Integration Laboratory

SPS

Software Product Specification

SQPP

Software Quality Program Plan

SS Services Summary

SUT

System Under Test

TDD

Threat Description Documents

TIM

Technical Interchange Meeting

TS

Top Secret

TSPI

Time/Space Position Information

VDD

Version Description Document

PAGE

Attachment 1

FA9302-09-D-0001