Draft Atch 1 - SOW

HQ0147-09-R-0006

Attachment 1

MDA/DTR

Airborne Sensors (ABS) Program

STATEMENT

OF

WORK

3 DECEMBER 2009

1. BACKGROUND

1.1 Mission

1.2 Management & Contract Structure

1.3 Reference Documents

2. MANAGEMENT

2.1 Program Management

2.2 Contract Management

2.3 Cost Management

3. MISSION ASSURANCE

3.1 Configuration Management

3.2 Environmental Safety & Health (ESH)

3.3 Reliability, Maintainability, and Availability

3.4 Software

4. MISSION FOCUS

4.1 Mission Support

4.1.1 Requirements, Planning, and Coordination

4.1.2 Pre-Mission Activities

4.1.3 Mission Execution

4.1.4 Post-Mission Activities

4.2 Operations & Sustainment (O&S)

4.3 Improvements & Modernizations (I&M)

4.4 Technology Development

1. Background

The Airborne Sensors (ABS) Program focuses on limited, streamlined development/ integration of airborne sensor assets and flexible contracting vehicles to support a wide variety of Missile Defense Agency (MDA) and other

Government agency customers. The ABS Program Office directs the design, development, integration, test, operation, sustainment, improvements and modernization, mission support and mission data reduction/analysis activities of the ABS Program for the Missile Defense Agency. This includes the High

ALtitude Observatory (HALO) I & II aircraft (Gulfstream IIB), the High ALtitude

Observatory (HALO) III aircraft (Gulfstream II SP); the Wide Body Airborne

Sensor Program (WASP) aircraft (McDonnell-Douglas DC-10), any future MDA or MDA sponsored aircraft, and support for other MDA sponsored data collection activities as directed.

1.1 Mission

The mission of the program is to provide airborne Electro-optic and Infrared sensor capability to support MDA and other test activities. The aircraft support tests at a wide variety of engagement locations using several different sensor bays capable of integrating a wide variety of sensors. The aircraft can be configured to support many different sensors to serve test data collection needs. The ABS program also provides quick-turn mission data analysis and reporting to get critical test data to key organizations in a timely manner. Unless otherwise specified, all ABS aircraft and sensor instrumentation packages are to be

Government Furnished Property (GFP).

1.2 Management & Contract Structure

The ABS management structure has a very streamlined reporting chain:

1. Director (MDA/D),

2. Director of Test and Evaluation (MDA/DT), and

3. Director, Test Resources Directorate (MDA/DTR)

The ABS Contract described within this Statement of Work (SOW) is comprised of two major contractor efforts:

1. Core Support Operations and

2. Mission Support.

ABS Core Support Operations are defined as all ABS contracted activities required to provide mission capable assets. Mission Support activities are those directly related to missions (planning, execution, data reduction/analysis and delivery).

1.3 Reference Documents

DoDD 5000.1, The Defense Acquisition System, 23 Apr 2008

DoDI 5000.02, Operation of the Defense Acquisition System, 8 Dec 2008

AFI 90-901, Operational Risk Management, 1 Apr 2000

AFI 91-202, The US Air Force Mishap Prevention Program, 1 Aug 1998

DCMA INST 8210.1, Contractor’s Flight And Ground Operations, 1 Mar

MIL-STD 882D, DoD Standard Practice for System Safety, 10 Feb 2000

MIL-HDBK 516B, Airworthiness Certification Criteria, 26 Sep 2005

MIL-HDBK 881A, Work Breakdown Structure, 30 Jul 2005

MIL-HDBK 1785, System Security Engineering Program Management

Requirements, 1 Aug 1995

NAS 411, Hazardous Material Management Program, Jul 1993

MDA-QS-001-MAP-Rev A, Missile Defense Agency Assurance Provisions

(MAP), 29 Oct 2006

2. Management

2.1 Program Management

2.1.1 The contractor shall:

a) Program and manage all activities required to execute the ABS Program and

b) Manage basic contract requirements.

2.1.2 The contractor shall:

a) Establish a program management organization,

b) Define a Contract Work Breakdown Structure (CWBS) and integrate with cost and schedule management tools (CDRL A002 Contract Work

Breakdown Structure), and

c) Provide adequate numbers of qualified management, technical, engineering, flight operations and support personnel to accomplish the requirements of this SOW.

2.1.3 The contractor shall prepare and submit for Government approval a comprehensive program plan which details the management and technical standard operating practices and procedures for the conduct of all activities to accomplish a technically sound and orderly implementation of operations (CDRL

A001 Program Plan).

a) The contractor shall plan, prepare, develop, execute, evaluate, and document new operational and employment concepts.

2.1.4 The contractor shall provide and maintain an Integrated Master Schedule

(IMS) that accounts for all on-going ABS efforts, including those of associate contractors (CDRL A003 Integrated Master Schedule).

a) This schedule shall include:

i. All prospective data collection activities,

ii. Aircraft maintenance periods, and

iii. Other required aircraft-related activities.

b) The schedule shall be updated for inclusion in the monthly progress report.

2.1.5 The contractor shall identify a single point of contact to the Government for management of the contractor effort and coordination with the Government to ensure successful implementation of ABS requirements.

2.1.6 Unless otherwise directed by the Government, the contractor shall conduct quarterly in-process review meetings to review overall contract and technical program status. These meetings will consider past data collection efforts; planning status; data reduction status; activity cost to date; and the status of all non-data collection flight operations, including aircraft and sensor maintenance, on-going improvement and modernization (I&M) efforts, and all other notable issues related to the program(CDRL A015, Report, Record of Meeting Minutes).

a) Overall contract status shall be provided, to include current hours and dollars usage along with a projection of hours and dollar usage to contract completion.

b) All issues, actions, and briefing materials presented shall be documented and delivered to the Government (CDRL A017 Status Report).

2.1.7 The contractor shall participate in various Government approved technical interchange meetings, conferences, and symposiums associated with airborne test and measurement activities.

a) The contractor shall prepare and present technical papers and/or briefings that address the subject/issues under consideration as directed.

b) The contractor shall submit technical papers and/or briefing for conferences and symposiums to the Government 60 days in advance for approval.

c) The contractor shall submit technical papers and/or briefing for technical interchange meetings to the Government five business days in advance.

2.1.8 The contractor shall inform the Government technical monitor of all scheduled or required aircraft inspections, maintenance or known repair activity at least six months prior to the scheduled activity.

a) If possible, these activities shall be planned and scheduled so as not to interfere with flight schedules or program operation.

2.1.9 The contractor shall provide the opportunity for Government attendance at contractor training sessions and provide ABS orientation training for Government personnel on an annual basis.

2.1.10 The contractor shall maintain proper security arrangements and procedures as required by the contract DD254, Contract Security Classification

Specifications.

a) The contractor shall prepare and submit an Operations Security

(OPSEC) plan identifying and assessing threat concerns and detailing implementation of security practices for the ABS effort (CDRL A001

Program Plan – “Physical Security Implementation Plan” section).

b) The contractor shall obtain and maintain up to SECRET/NF level electronic connectivity to the MDA CNet to provide classified quick looks and photo documentation.

2.2 Contract Management

2.2.1 The contractor shall notify the Contracting Officer in writing if there is work requested or required beyond the scope of the contract and shall not commence work without direction from the Contracting Officer. The Contracting

Officer is the only person authorized to change the terms and conditions of the contract.

a) All technical and management interchange between the Government and the contractor personnel shall be conducted subject to this condition.

2.2.2 The contractor shall notify the Government of any problems in meeting contract requirements as soon as the problems are known.

2.2.3 The contractor shall provide a smooth and efficient transfer of responsibility during the end-of-contract phase-out periods. During end-of-contract phase-out, the contractor shall:

a) Develop a phase-out plan and transfer schedule to any successor,

b) Cooperate with the successor and the Government at the end of this contract,

c) Work with the successor to finalize a joint phase-out plan, and

d) Maintain overall contract responsibility until successful transfer to the successor, as determined by the Government.

2.2.4 The contractor shall meet all delivery schedules required by the Contract

Data Requirements Lists (CDRL).

2.2.5 When requested by the Government, the contractor shall develop/review and comment on ABS related technical or contractual documentation.

2.3 Cost Management

2.3.1 The contractor shall manage, track, and forecast the cost of on-going ABS program efforts by Government fiscal year funding.

2.3.2 The contractor shall provide financial controls to allow for the tracking of expenditures on behalf of the various users and for “core” (non-user funding) support funds.

a) The contractor shall notify the Government of projected or known cost/budget problems as soon as they are identified.

2.3.3 The contractor shall prepare and submit a comprehensive monthly progress report detailing all significant activities by Government fiscal year funding (CDRL

A004 Cost Performance Report (CPR) modified, CDRL A006 Contract Funds

Status Report (CFSR), CDRL A017 Status Report):

a) Cost status (including cost estimates, funding allocation, costs to date, and projected funding balance),

b) A schedule forecasting future activities,

c) Milestone accomplishments, and

d) Programmatic issues.

2.3.4 The contractor shall manage travel budgets, track actual costs, and forecast planned expenditures.

2.3.5 The contractor shall provide reports and informal reviews that integrate technical accomplishments with the cost and schedule status of work progress on the contract.

3. Mission Assurance

The contractor shall prepare, maintain, and comply with a Mission Assurance

Implementation Plan in accordance with the MDA Assurance Provisions (CDRL

A010 Mission Assurance Implementation Plan).

3.1 Configuration Management

3.1.1 The contractor shall work with the Government and associate contractors to manage data and ensure documents remain current and easily accessible.

3.1.2 The contractor shall perform configuration management of all ABS hardware and software, including mission related databases, files, and mission unique software (CDRL A010 Mission Assurance Implementation Plan –

“Configuration Management Plan” section).

3.1.3 The contractor shall develop, maintain, and update technical data packages

(TDP) reflecting the capabilities and capacity of each aircraft, sensors, instrumentation, and support systems (CDRL A028 Technical Data Package).

3.1.4 The contractor shall develop and maintain operational and maintenance procedures, technical data, test plans, test procedures, test reports, evaluation plans, evaluation reports, mission interface documents, and other documents required to conduct activities assigned under this contract. (CDRL A007 Interface

Design Description, CDRL A008 Product Drawing, CDRL A011 T&E Program

Plan, CDRL A018 Scientific and Technical Reports – Verification/Final Report, CDRL A019 Test Plan CDRL A023 Software Test Report, CDRL A028 Technical

Data Package)

3.1.5 The contractor shall use an information management system that is compatible with MDA IT systems and approved by the Government to share common-use matter across sites, with associate contractors, and with external agencies.

3.2 Environmental Safety & Health (ESH)

3.2.1 The contractor shall integrate applicable federal, state, and local ESH laws and regulations, Executive Orders, treaties, and policies into all phases of program execution to minimize impact on program life cycle cost. All facilities, processes, and operations (including those of subcontractors) shall be compliant to ensure a safe work environment.

3.2.2 The contractor shall minimize the impact of environmental laws, regulations, and policies on the life cycle of the ABS Program through pollution prevention using National Aerospace Standard (NAS) 411, Hazardous Material

Management Program, as a guide (CDRL A025 Hazardous Materials Management

Program Report, CDRL A027 Hazardous Waste Report).

3.2.3 The contractor (and subcontractors as applicable) shall comply with mitigations outlined in the National Environmental Protection Act (NEPA) documentation developed by MDA/DOIP and signed by MDA/D (CDRL A010

Mission Assurance Implementation Plan – “Environmental/Safety Plan” section).

The NEPA process assesses environmental impacts from all test and evaluation approaches and the pollution prevention actions will strive to mitigate programmatic and operational life cycle impacts from ESH issues.

3.2.4 The ABS program has implemented a system safety program in accordance with AFI 91-202, The US Air Force Mishap Prevention Program, to ensure all safety hazards are identified, eliminated, accepted or controlled, and verified within the constraints of program cost, schedule, and performance. The contractor shall formally identify risk hazards and mitigations, and assess their final level of risk for Government approval as defined in MIL-STD-882D (CDRL A010 Mission

Assurance Implementation Plan – “Safety” section).

3.2.5 Mishap reporting will be done IAW the ABS Mishap Plan. The contractor shall cooperate with and support Government-led mishap investigations as required.

3.3 Reliability, Maintainability, and Availability

The Contractor shall manage, plan, and conduct system maintenance and support such that the customer’s primary objectives defined in the Mission Requirements

Document (MRD) are met and data collection systems are available for scheduled missions 100% of the time. For planning purposes, a nominal data collection mission load is ten (10) data collects per aircraft per year. (CDRL A013 Mission

Status/Mission Reports, CDRL A010 Mission Assurance Implementation Plan –

“System Support Plan” and “Reliability” sections). )

3.3.1 The Contractor shall ensure that the ABS aircraft are available to support scheduled data collection flights 100% of the time.

3.3.2 The Contractor shall ensure that all on-board sensor systems and all airborne and ground support systems are maintained such that they are available and operational for scheduled data collection requirements 100% of the time.

3.3.3 The Contractor shall implement a tailored reliability program to prevent system failures, track reliability, and to focus improvements and modernization of

ABS systems.

3.3.4 The Contractor shall update the spares analysis and use it to define the spares requirements and provisioning processes needed. The Contractor shall establish and execute processes to identify long lead parts needed to support future needs (CDRL A020 Recommended Spare Parts List).

3.3.5 The Contractor shall maintain a list of all support equipment needed to maintain and operate the ABS and its support infrastructure. The Contractor shall provide an integrated maintenance plan with all scheduled inspections and maintenance for each aircraft and support systems.

3.3.6 The Contractor shall notify the Government of any foreseen situation that would interfere with the availability of ABS aircraft/sensors or support systems, as soon as practical. Notification shall not diminish the Contractor’s responsibility to meet the mission support/availability.

3.4 Software

ABS software supports mission planning, mission operations, instrument and instrumentation control, communications, data collection, as well as mission and data analysis in support of the overall ABS Program objectives.

3.4.1 The Contractor shall design, develop, integrate, validate, document, and maintain ABS software and data (CDRL A010 Mission Assurance Implementation

Plan – “Software Quality Assurance Plan,” “Software Development Plan,” &

“Software Configuration Management Plan” sections, CDRL A023 Software Test

Report, CDRL A026 Software Version Description).

a) The Contractor shall develop and follow standard processes, based on

SEI CMMI Level 3 processes for the following process areas when performing software engineering functions: Project Planning, Project

Monitoring and Control, Requirements Development, Requirements

Management, Technical Solutions, Product Integration, Verification, and Validation.

b) The Contractor shall maintain independent certification of SEI CMMI

Level 3 compliance.

c) The Contractor shall establish, maintain, and report monthly a software change request schedule depicting the contractor’s plan (by software release) to resolve, implement, and verify any outstanding software change requests.

d) The Contractor shall resolve, implement, and verify any outstanding software change requests only after Government approval to do so.

e) The Contractor shall only maintain existing software. The Contractor shall not develop any new software variants of the existing software or develop any new software without Government approval. No proprietary systems or software shall be developed as part of the ABS system.

4. Mission Focus

4.1 Mission Support

4.1.1 Requirements, Planning, and Coordination

The ABS Contractor shall conduct and document long-range planning activities to analyze requirements and identify new capabilities to support current/future programs. This will include developing a method for prioritizing these requirements, analyzing the scope of new/extended work, verifying capability and capacity to accept or retain the work, and recommending to the Government which aircraft/system would optimally support the work.

4.1.1.1 The contractor shall evaluate ABS system capacity and plan long-range activities for baseline work, extended work, or new work.

4.1.1.2 The contractor shall perform readiness activities including planning, systems engineering, and technical support for future missions.

a) The contractor shall prepare, maintain, and deliver a general aircraft/sensor capabilities document derived from information contained in the TDP to assist user programs considering the use of

ABS assets (CDRL A028 Technical Data Package).

4.1.2 Pre-Mission Activities

4.1.2.1 The contractor shall coordinate with potential users, as directed by the

Government, to determine specific airborne data collection activities.

a) The contractor shall, in coordination with the ABS Government Mission

Team, work closely with each user to address those tasks necessary to satisfy the user requirements.

b) Specific data-gathering requirements will be provided to the contractor in the form of a user-prepared Mission Requirements Document

(MRD). The contractor shall conduct planning to accomplish the requirements provided in this MRD.

i. The contractor shall review the MRD, as well as other user program documentation, and participate in initial planning and requirements meetings with potential users.

ii. The contractor shall provide a descriptive work summary, cost estimate, and support schedule in a proposal to the Government in response to a Task Order RFP provided by the Government.

4.1.2.2 The contractor shall assess measurement requirements stated in the MRD and:

a) Recommend instrumentation configurations and/or modifications as required to configure the aircraft, and

b) Define and assess aircraft placement and maneuvers required to ensure optimal sensor performance with regard to the mission requirements.

4.1.2.3 For each mission data collection activity, the contractor shall prepare and submit a mission support plan (MSP) (CDRL A013 Mission Status/Mission

Reports), for Government approval, to include:

a) Support schedules and activities,

b) Instrumentation configuration,

c) Mission team members,

d) Performance predictions, and

e) Data management information.

4.1.2.4 The contractor shall participate in pre-flight mission planning meetings as requested by the Government.

a) The contractor shall prepare and present briefings to address instrumentation capabilities, aircraft performance, equipment performance, support status, and data management and delivery.

b) The contractor shall provide the Government a copy of all presentation material for these meetings a minimum of five working days prior to the scheduled presentation unless directed otherwise by the Contracting

Officer or Contracting Officers Representative (COR) (A013 Mission

Status/Mission Reports).

4.1.2.5 The contractor management organization shall coordinate mission execution with the Contracting Officer or COR, as well as other Government agencies (PEO-MD, MDA, etc.), support contractors, test range representatives, and other user agency's support contractors (CDRL A013 Mission Status/Mission

Reports).

a) The contractor shall respond effectively, efficiently, and rapidly to any changes in test requirements and test conditions.

4.1.2.6 The contractor shall install, checkout, and calibrate (as required) all sensor platforms/configurations necessary to conduct the required support in accordance with the MSP.

4.1.2.7 The contractor shall conduct pre-flight tests of measurement support equipment to ensure optimal performance.

4.1.2.8 The contractor shall establish channels of communication, in coordination with the Government mission team, with test range personnel/organizations to address the details of various data collection-related topics, to include range safety, target trajectory, voice and data communications, beacon parameters, logistical support, and aircraft vectoring instructions.

a.) Planning for range interface shall include participation in pre-deployment range interface meetings when required by the Government.

b.) The contractor shall conduct safety analyses and coordinate with range safety representatives to ensure that the aircraft test support position meets all range-imposed safety constraints and aircraft performance safety standards.

4.1.2.9 The contractor shall establish channels of communication with civil and military air traffic control agencies to ensure availability of air space and submission of any required notifications or flight plans.

4.1.2.10 The contractor shall establish, coordinate, and submit an aircraft itinerary for each data collection activity, identifying all Government facilities, airfields, customs offices, and commercial airports to be utilized as primary or secondary aircraft stops.

a) This activity shall be coordinated with the Government Mission Team unless the contractor is specifically directed otherwise by the

Government.

4.1.2.11 The contractor shall arrange for/provide, in coordination with the

Government mission team, pre-flight logistical support to accomplish effective support with respect to all airborne measurement requirements.

a) Where cost effective or mission essential, the contractor shall make maximum use of Government support facilities for performing missions.

4.1.2.12 The contractor shall perform all activities associated with the operation of the sensor platforms and coordinate with other contractors to ensure successful integration and operation of any "guest" sensors.

a) When approved by the Government, the contractor shall ferry the aircraft to a designated location in order to pick up or return a designated “guest” sensor for/from a data collection or a test flight.

b) The contractor shall work with and provide assistance other contractors in the loading or removal of the other contractor’s equipment from the aircraft.

4.1.3 Mission Execution

4.1.3.1 The contractor shall:

a) Deploy ABS systems (aircraft, sensor platform, etc.), aircraft crew, and all required technical personnel to support each data collection activity;

b) Conduct airborne flight operations;

c) Provide effective support in order to enable a successful data collect;

d) Perform mission data collect;

e) Provide daily status reports to the Government Mission Team;

f) Coordinate all mission execution activities with the Government

Mission Team.

4.1.3.2 The contractor shall provide for flexibility of mission support operations that can vary from one shift, 5 days a week to 24 hours a day, 7 days a week on rare occasion.

4.1.4 Post-Mission Activities

4.1.4.1 The contractor shall provide a quick-look assessment of their support performance and data collections, and communicate these results to the "on-site"

Government test representative. The Government will review and have final approval of all reports prior to distribution.

a) The contractor shall process/reduce collected data into radiometric calibrated test data, photo documentation data, engineering parametric information, or other forms required by the user.

b) The contractor shall conduct data reduction operations such that all mission reports and data required by the MRD are delivered on schedule

(CDRL A013 Mission Status/Mission Reports, A014 Mission Data

Products).

c) The contractor shall support post-flight technical interchange meetings.

d) The contractor shall provide post-mission reports as specified in MRD or Data Handling Plan (CDRL A013 Mission Status/Mission Reports).

4.2 Operations & Sustainment (O&S)

4.2.1 The contractor shall provide all aircraft and sensor subsystem related services required to assure mission success in the performance of this SOW, to include:

a) The provision of appropriately-modified measurement aircraft/sensor systems;

b) All aircraft/sensor system operations and sustainment (CDRL A009

O&M Instructions for R&D Equipment);

c) Engineering sustainment for mission-unique applications;

d) Aircraft/sensor system modifications;

e) Flight crew, mission specialists, and ground crew support personnel;

f) Facilities located CONUS (minimum requirements include: tarmac for storage of non-active A/C, environmentally controlled facilities for the storage and maintenance of instruments (sensor packages), and temperature controlled hangar(s) space for the ABS aircraft during mission preparation and execution);

g) Operate and maintain aircraft in accordance with DCMA Instruction

8210, Contractor’s Flight and Ground Operations, and

h) Operate and maintain aircraft in accordance with the intent of Federal

Aviation Administration (FAA) flight worthiness and flight safety regulations.

4.2.2 Each ABS aircraft shall be 100% dedicated to ABS activities.

a) ABS aircraft and systems shall not be used for any other activities without the approval of the Government.

4.2.3 The contractor shall ensure that all aircraft modifications and airborne support/sensor equipment installation plans are reviewed and approved as necessary to maintain Government flight safety and airworthiness certifications.

4.3 Improvements & Modernizations (I&M)

4.3.1 The contractor shall support analysis, development, and modification of the

ABS system architecture (CDRL A016 Improvement and Modernization Report).

a) The contractor shall provide prioritized requirements in support of ABS modifications.

b) The contractor shall provide lessons learned for future system design and development.

4.3.2 The contractor shall perform operational testing on ABS assets in support of system/platform upgrades, including planning and preparation, operation of the equipment, database validation, performance evaluations, and suitability assessments.

a) The contractor shall develop and review test plans and procedures.

4.3.3 The contractor shall perform operational evaluation of potential software and hardware upgrades/modifications, to include:

a) Planning and preparation,

b) Operation of the equipment,

c) Performance evaluations,

d) Suitability assessments, and

e) Development and review of test plans and procedures.

4.4 Technology Development

4.4.1 The contractor shall provide engineering development for future ABS program applications. Development activities may include sensor platform development, aircraft modifications, and introduction of new technologies into existing ABS systems (CDRL A021 Technology Development Plan, CDRL A022

Technology Control Plan).