CLS-PWS-13-Oct-16.pdf

AN/FPS-117 Software CLS

Performance Work Statement

Atmospheric Early Warning System

AN/FPS-117(V) 1/4 Long Range Radar

Software Contractor Logistics Support

Prepared by

AFLCMC/HBZIA

DATE: 13 October 2016

Contents

1. GENERAL

1.1 Scope

1.2 Purpose

2. APPLICABLE DOCUMENTS

2.1 Specification Documents

2.2 Guidance Documents

2.3 Workload Agreements (Refer to Appendix B)

3. REQUIREMENTS

3.1 Task Order Categories

3.2 Program Management (CDRL A001, CDRL A002)

3.2.1 Contractor’s Progress, Status, and Management Report (CDRL A001)

3.2.2 Meetings, Reviews, and Conferences (CDRL A002)

3.2.3 Configuration Management

3.2.4 Deficiency Reporting (DR)

3.2.5 Data Accession List (DAL) (CDRL A008)

3.2.6 Task Order CDRLs

3.3 Software Maintenance Activities

3.3.1 Software Performance

3.3.2 Software Review Board (SRB) (CDRL A002)

3.3.3 Schedule

3.3.4 Software Maintenance Summary

3.3.5 Software, Firmware, and Programmable Devices

3.3.6 Information Assurance Controls

3.3.7 License

3.3.8 Required CDRLs

3.3.9 Government Acceptance (DD-250)

3.4 Engineering Support Services

3.4.1 Task Planning/Scheduling Meeting (CDRL A002)

3.4.2 Technical Call-in Service

3.4.3 Test Support

3.4.4 Routine Tasks

3.4.5 High Effort Tasks

3.4.6 Special Task Options

3.4.7 Training

3.4.8 Task Order CDRLs

3.5 Technical Data Package

3.5.1 Technical Orders, Drawings, and Instructions (CDRL 006, CDRL 007, CDRL 008)

3.5.2 Engineering Change Proposal (ECP) (CDRL A009)

3.5.3 Software Version Description (SVD) (CDRL A010)

3.5.4 Task Order CDRLs

3.5.5 Subject Matter Experts

3.5.6 Training Materials

3.5.7 Task Order CDRLs

3.5.8 Government Acceptance (DD-250)

3.6 Security

4. PERFORMANCE SERVICE SUMMARY

5. ADMINISTRATIVE

5.1 Equipment, Software, and Tools

5.1.1 Government Furnished Equipment (GFE) Requirements

5.1.2 Test Equipment Calibration

5.2 Overtime

5.3 Packaging, Handling, Storage, and Transportation

5.3.1 Packaging and Transport

5.3.2 Special Electrostatic Sensitive Device Requirements

5.3.3 Reusable Containers

5.3.4 Receiving Inspection

5.3.5 Marking

5.4 AEWS Points of Contact (POC)

5.4.1 AEWS Program Manager/Contracting Officer Representative (COR)

5.4.2 SPO Lead Engineer

5.5 AN/FPS-117 Site Locations

5.6 Shipping/Mailing Addresses

5.7 Travel Requirements

6. APPENDICES

APPENDIX A - ACRONYMS

APPENDIX B - WORKLOAD AGREEMENTS (WLA)

ATTACHMENT 1 - WLA for AN/FPS-117 – Alaska Sites

ATTACHMENT 2 - WLA for AN/FPS-117 – Canada Sites

ATTACHMENT 3 - WLA for AN/FPS-117 – Mt Kokee, Hawaii

ATTACHMENT 4 - WLA for AN/FPS-117 – Punta Salinas, Puerto Rico

APPENDIX C - SOFTWARE LISTING

APPENDIX D - MAILING ADDRESSES

APAPPENDIX E - MASTER CDRL LIST

1. GENERAL

This Performance-Based Work Statement (PWS) outlines the tasks and duties required of the contractor to support the AFLCMC/HBZIA, Atmospheric Early Warning System (AEWS), AN/FPS-117V(1)/V(4)

(AN/FPS-117), System Program Office (SPO). The initial contract award is for one base year with two additional one year options.

1.1 SCOPE

This PWS outlines the tasks and duties required of the Contractor to provide Support for sustainment of the

AEWS consisting of 28 AN/FPS-117 and the AN/UPX-48 Identification Friend Foe (IFF) Secondary

Surveillance Radar (SSR), and five Maintenance Control Systems (MCS). The AN/FPS-117 operational radar system consists of a total of 27 version 1 and 4 radars integrated with four MCS systems located in Alaska, Canada, Puerto Rico, and Hawaii. An additional AN/FPS-117 radar system and MCS are at the Engineering

Facility (EFAC) located at Hill Air Force Base (HAFB) Utah, and is operated as an engineering test bed for system maintenance support, integration, modifications, upgrades, product software obsolescence/non-availability resolution and software upgrades.

1.2 PURPOSE

The purpose of this effort is to provide depot level Contractor logistics Support (CLS), for the AN/FPS-117 radar system software engineering and software maintenance by the Original Equipment Manufacturer (OEM) for all AN/FPS-117 radars, radar subsystems (Mono-Pulse Secondary Surveillance Radar (MSSR) and RECS), and the MCS equipment.

2. APPLICABLE DOCUMENTS

The following specifications establish the AEWS system software baseline. The contractor shall obtain

Government approval for any specification change to the AEWS baseline as listed in Table 1.

2.1 SPECIFICATION DOCUMENTS

Table 1 – AEWS Baseline Software Specifications

Document Number Title

ESD SS-

2433-3B, System Specification for Seek Igloo Minimally Attended Radar (MAR)

Radar System AN/FPS-117(V 1/4)

77A595311 System/Subsystem Specification for the AN/FPS-117 Atmospheric Early

Warning System (AEWS), Essential Parts Replacement Program (EPRP)

77A595644 European Aeronautics Defence and Space company (EADS) Monopulse

Secondary Surveillance Radar requirements Analysis for the AN/FPS-117

Atmospheric Early warning System (AEWS), Essential Parts Replacement

Program (EPRP)

77A595327 Software Requirements Specification (SRS) Radar 117 Product Line

Software Requirement Specifications (SRS) For The AN/FPS-117

Atmospheric Early Warning System (AEWS), Essential Parts Replacement

Program (EPRP)

77A574881 Radar Performance Mission Software (RPMS) Software Requirements

Specification for the Radar 117 Product Line Block 3

77A574874 Detection Procession Mission Software (DTMS) Software Requirements

Specification for the Radar 117 Product Line Block 3

77A574879 Target Processing Mission Software (TPMS) Software Requirements

Specification for the Radar 117 Product Line Block 3

77A574885 Communications Mission Software (COMS) Software Requirements

Specification for the Radar 117 Product Line Block 3

77A574889 Command and Control Display Software (CCDS) Software Requirement

Specification for the Radar 117 Product Line Block 3

77A590031 System Support Software (SSS) Software Requirements Specification for the Radar 117 Product Link Block 3

77A564034 Offline Detection Analysis Software (ODAS) Software Requirement

Specification for the Radar 117 Product Line

77A574887 Track Processing Mission Software (TKMS) Software Requirement

Specification for the Radar 117 Product Line Block 3

77A574886 Data Processor Operating Systems (DPOS) Software Requirement

Specification for the Radar 117 Product Line Block 3

77A574880 Radar Control Mission Software (RCMS) Software Requirements

Specification for the Radar 117 Product Line Block 3

77A574878 Computer Program Performance Specification Radar Environment

Simulator Software (RESS) Software Requirements Specification for the

Radar 117 Product Line Block 3

77A590024 Performance Database Support Software (PDSS) Software Requirement

Specification For the Radar 117 Product Line Block 3

77A590029 Software Requirements Specification TDS System Resource manager

(SRM) for the Radar 117 Product Line Block 3

77A590026 Site Adaptation Software (SAS) Software Requirements Specification for the Radar 117 Product Line Block 3

77A574884 Signal Processing Mission Software (SPMS) Software Requirements

Specification for the Radar 117 Product Line Block 3

77A590028 Computer Program Performance Specification Scenario Generator

Software (SGS) CSCI Software Requirements Specification for the Radar

117 Product Line Block 3

77A595292 Command and Control Display Software (CCDS) Software Requirements

Specification (SRS) Appendix for the AN/FPS-117 Atmospheric Early

Warning System (AEWS) Essential Parts Replacement Program (EPRP)

77A595289 Communications Mission Software (COMS) Software Requirement

Specification (SRS) Appendix for the AN/FPS-117 Atmospheric Early

Warning System (AEWS) Essential Parts Replacement Program (EPRP)

2.2 GUIDANCE DOCUMENTS

The documents listed in Table 2 are provided for guidance and are available from the AFLCMC/HBZIA

(AEWS) Program Office, 6029 Wardleigh Rd, B1207, Hill AFB, UT 84056.

Table 2 – Guidance Documents

Document Number Date Title

DoDI 8500.2

February

Information Assurance

DoD AIMS 03-1000A

January

Performance/Design and Qualification Requirements Technical Standard for the ATCRBS/IFF Mark XIIA Electronic Identification System

(AIMS) and Military Implementation of Mode S with Changes 1, 2, and

Interface Control Standard for the Mode 4/5

DoD AIMS 03-1000B

1 July

Performance/Design and Qualification Requirements Technical Standard for the ATCRBS/IFF Mark XIIA Electronic Identification System

(AIMS) and Military Implementation of Mode S Amendment 1.

DoD AIMS 04-900A

January

Cryptographic Computer

STANAG 4193

Parts I, II, III

12 Nov

Technical Characteristics of IFF MK XA and MK XII Interrogators and

Transponders Parts I-III

Part IV

12 Apr

Technical Characteristics of IFF MK XA and MK XII Interrogators and

Transponders Part IV: Technical Characteristics of Mode S in Military

Interrogators and Transponders

STANAG 4193 31 Mar

Technical Characteristics of IFF MK XA and MK XII Interrogators and

Transponders Part V Technical Description of the MK XIIA System, Part V

Mode 5 Levels 1 through 4

Part VI

13 May

Technical Characteristics of IFF MK XA and MK XII Interrogators and

Transponders Part VI: Classified Performance Aspects of Mode 5

77A595624 16 Dec

Integrated Logistics Support Plan for the AN/FPS-117 Atmospheric

Early Warning System (AEWS), Essential Parts Replacement Program

(EPRP)

2.3 WORKLOAD AGREEMENTS (REFER TO APPENDIX B)

Site support and visit requirements are detailed within the workload agreements, Appendix B, Attachments 1 through 4.

3. REQUIREMENTS

This PWS covers depot level AN/FPS-117 radar system CLS for software engineering and software maintenance for all AN/FPS-117 radars and the MCS equipment. This PWS also includes specific task orders for Program Management, Software Maintenance, Engineering Support services, Technical Data Package, and

Training.

3.1 TASK ORDER CATEGORIES

The Government will issue task orders along with specific deliverables for support In Accordance With (IAW) this PWS. Each tasking may contain all or part of the predefined task orders listed in paragraph 3 and associated

Table 3.

Table 3 – Task Order Categories

Task ID Reference

Paragraph #

Requirement Deliverable

1 3.2 Program Management A001

A002

2 3.3 Software Maintenance A002

3 3.4 Engineering Support Services A002,A003,A004,A005

4 3.5 Technical Data Package A006,A007,A008,A009,A010

5 3.6 Travel

3.2 PROGRAM MANAGEMENT (CDRL A001, CDRL A002)

The contractor shall provide a single Point Of Contact (POC) for this effort. The contractor shall immediately inform the AEWS System Program Office (SPO) of any technical or schedule related problems.

The contractor shall provide overall program planning and control, contract/subcontract management, configuration management, security, and administrative support in the performance of the AEWS CLS contract.

The contractor shall furnish all facilities, software, materials, equipment and services, required to repair, replace, or change any software, firmware, or related documentation changes, that are necessary to operate the

AN/FPS-117 system/subsystem baseline.

Call-ins for routine Program Management questions that do not require tasking will be considered part of

Program Management overhead.

3.2.1 CONTRACTOR’S PROGRESS, STATUS, AND MANAGEMENT REPORT (CDRL A001)

The contractor shall provide a Contractor’s Progress, Status, and Management Report

20 Work Days prior to the Base and Option year period closeout.

The Contractor’s Program Manager shall be prepared, given reasonable notice, to present and discuss with the

Government, the status of contract activities throughout the contract period of performance.

3.2.2 MEETINGS, REVIEWS, AND CONFERENCES (CDRL A002)

3.2.2.1 Monthly Status Discussions

The contractor shall conduct monthly informal conference calls with the AEWS SPO and AN/FPS-117 user group to discuss Deficiency Reports (DR), Program Trouble Reports (PTR), Software Change Requests (SCR), and project status.

3.2.2.2 Quarterly Status Review (CDRL A002)

The contractor shall conduct a formal quarterly status review meeting with the AEWS SPO and AN/FPS-117 user group. Unless otherwise specified by the AEWS SPO, these meetings shall be conducted via teleconference; subjects may be combined under one meeting. As a minimum, the following topics shall be discussed during the quarterly status review.

1. Project Status (Task Orders)

2. Problem Reports, Deficiency Reports, Software Change Requests

3. Prioritization of projects

4. Planning and Schedules

5. Budget/Spend Rate

6. Software obsolescence/Non-availability (Reason for change, forecasted obsolescence, forecasted change for product improvement, i.e. any anticipated change to the government’s current baseline)

7. Engineering Change Proposals (ECP)

8. Technical Interchange (Special Interest Items)

9. Test Work Group (If required as part of a task order)

10. Status of Technical Order Documentation, drawings, and data (If required as part of a task order)

3.2.2.3 Post Award Conference (CDRL A002)

The Contractor shall plan for, host, and participate in a Post Award Conference to be held at the Contractor’s site within 45 calendar days of contract award. The Government will determine the actual date after contract award. At this conference, the Contractor shall address the plans, schedules, work efforts, risk management, and risk mitigation strategy, for this contract. To successfully complete the Post Award Conference, the

Contractor shall address the overall project approach, discuss all CDRLs, and obtain Government approval of the conference meeting minutes (CDRL A002).

3.2.3 CONFIGURATION MANAGEMENT

The Government will use the Computer Program Identification Number (CPIN) process to identify and control the AN/FPS-117 system software baseline. Any change to the AEWS baseline will be decided by the

Government. The Government will provide the current system baseline to the contractor for the purpose of evaluating changes. Once a new software release or software configuration change is fully verified by both

Contractor and Government, the new AEWS system baseline will be established and controlled by the

Government. Any software changes or made under this contract shall not degrade the performance of the

AN/FPS-117 Radar, AN/UPX-48 IFF subsystem, or MCS, (Section 2.1, and Appendix C, Software Listing).

3.2.3.1 Management of Software Baseline

The Contractor shall maintain the AEWS designated software baseline consistent with the hardware baseline configuration and AEWS Information Assurance (IA) controls, through all phases of software logistics support or hardware/software development. The Contractor shall notify the Government of any software baseline changes along with impact before development begins and prior to software and/or hardware related firmware is replaced or modified. The Government may issue a task order for an ECP or other required actions or deliverables before any change to the AEWS system software baseline (ECP, Paragraph 3.5.2).

During any software replacement or revision, the Contractor shall verify compatibility with the AEWS baseline configuration. Any changes to the AEWS system baseline shall be submitted to the Government for approval.

The contractor shall manage software maintenance and other software changes to ensure system Reliability, Availability, and Maintainability (RAM) meet quality factors IAW the System/Subsystem Specification (SSS) for the AEWS AN/FPS-117 EPRP, and LMC document 77A595311, refer to specification paragraph 3.4

(Quality Factors). RAM is further discussed within the LMC document 77A595624, Integrated Logistics

Support Plan (ILSP), Section 2.4.

The Contractor shall notify the AEWS SPO of any changed, outdated, or new Technical Orders, drawings, or data, and include a system documentation change discussion during the quarterly status review meeting (Section

3.2.2.2).

3.2.4 DEFICIENCY REPORTING (DR)

The Contractor shall maintain a DR database that includes all AEWS baseline software related PTR submitted by the Government along with any software deficiencies identified by the Contractor that apply to the AN/FPS-

117 System/Subsystem Block 3 baseline software. The DR database shall clearly identify the deficiency, the resolution, the area of software that is affected, any related hardware or operating configuration impacts, current status, and a listing of impacted Computer Software Configured Items. The Contractor shall discuss DR/SCR status to include all Government submitted PTRs and Software Change Requests (SCR), and shall include the

DR/SCR Summary within the Quarterly Status Review (Section3.2.2.2)

3.2.5 DATA ACCESSION LIST (DAL) (CDRL A008)

The Contractor shall create and maintain a Data Accession List (DAL). The Contractor shall list internal data generated in compliance with contractual tasks and subcontractor generated data on the DAL. The DAL listing shall be delivered IAW CDRL A008.

3.2.6 TASK ORDER CDRLS

The Government will identify any CDRL’s required as part of the task order within the task order.

3.3 SOFTWARE MAINTENANCE ACTIVITIES

The Government’s intention is to accomplish software baseline resets or Microsoft Windows upgrades, or updates of related support software, at pre-determined intervals based upon the current production baseline status and resolution of critical DRs, or to meet operational requirements. The periodic baseline reset will occur at fifteen month intervals unless the Government determines that a critical deficiency can only be resolved by out of cycle software baseline reset.

This effort covers all software and firmware related to the Primary Surveillance Radar (PSR)

System/Subsystem, the MSSR, the MCS, all mission software, firmware, Operating Systems & utilities, special support software, and all Commercial Off The Shelf (COTS) software.

This tasking may be issued in total or in part after the Government pre-authorizes the work to be accomplished through an issuance of a task order.

3.3.1 SOFTWARE PERFORMANCE

If the updated or changed software fails upon installation the deficient software will be returned with a Quality

Deficiency Report (QDR). In the event of rework for the same problem the contractor shall evaluate the returned software to determine if the software was at fault. The contractor shall not charge the government for re-work for the same reported deficiency.

Any software/firmware/programmable device changes made under this PWS shall meet required functionality and not degrade the performance of the AEWS AN/FPS-117, (Radar, IFF Subsystem, Maintenance Control

Center), as described in the documents listed in section 2.1. Delivered software shall meet RAM quality factors

IAW the System Subsystem Specification (SSS) for the AN/FPS-117 Essential Parts Replacement Program

(EPRP), 77A595311, and LMC document, Integrated Logistics Support Plan 77A595624, (Section 2.4) Quality

Factors.

3.3.2 SOFTWARE REVIEW BOARD (SRB) (CDRL A002)

The contractor shall conduct an annual Software Review Board (CDRL A002). The SRB shall address the current software baseline status; DRs, SCRs, software changes resulting from hardware/software obsolescence, software enhancement/upgrade that are available, and release time table.

The Government will determine which software changes or enhancement will be included in the next released build.

3.3.3 SCHEDULE

The contractor shall complete software builds within the agreed upon completion date established during the

Task Planning/Scheduling Meeting (3.2.3.3) IAW CDRL A002.

3.3.4 SOFTWARE MAINTENANCE SUMMARY

For each software change, repair or update, the software maintenance summary shall be included IAW paragraph 3.2.2.2, quarterly status review.

3.3.5 SOFTWARE, FIRMWARE, AND PROGRAMMABLE DEVICES

Where requirements cannot be met by using unaltered commercially offered software, or use of software of proprietary nature is necessary, the contractor shall notify the Government immediately.

All contractor-developed and modified software that interface with firmware or programmable devices shall be fully documented and the programming files and instructions provided to the Government.

3.3.6 INFORMATION ASSURANCE CONTROLS

If the contractor selects or changes software or associated firmware due to software obsolescence, DMSMS, or for other reasons, the replacement software shall, as a minimum, have IA controls that are compatible with the original AEWS baseline.

If identified as part of a task order, the contractor shall provide IA support to the Government sustainment IA team for continued Certification and Accreditation (C&A) of all AN/FPS-117 radars, IFF subsystems and the

MCS.

3.3.7 LICENSE

The Contractor shall deliver to the Government any licenses or other permissions to operate the Software with the AEWS baseline.

3.3.8 REQUIRED CDRLS

The Government will identify any CDRL’s required as part of the task order within the task order.

3.3.9 GOVERNMENT ACCEPTANCE (DD-250)

Delivery shall be according to the delivery schedule IAW (Sections 3.2.2.3 and 3.3.3). A listing of mailing addresses are in Appendix D. Government receipt and acceptance will be verified by a Government signed DD

250.

3.4 ENGINEERING SUPPORT SERVICES

Software Engineering support covers all software and firmware related to the AN/FPS-117, Radar

Environmental Control System (RECS), the AN/UPX-48, and the MCS. The Government may issue task orders to obtain engineering support to resolve software and firmware related issues or problems, support temporary fixes, assist with configuration settings, accomplish upgrades to hardware or software, resolve IA related software/hardware settings, certification support, test, and special studies (i.e. enhanced radar operation, optimization of software, software installation procedures, and operating instructions). The AEWS SPO authorized POC may issue additional task orders to meet the overall task objectives.

This task order also covers engineering support to the AEWS SPO to implement AIMS MK XIIA Mode 5 or

Mode S capability, implement enhanced performance and status monitoring, and support required system certifications to include special test. This may also include special studies or resolution of problems without a full baseline software release.

This task order may be issued in total or in part. The AEWS SPO authorized POC may request additional task orders to meet the overall task objectives.

If identified as part of a task order, (i.e. special study), the Contractor shall deliver a report IAW, Technical

Report (CDRL A005)

3.4.1 TASK PLANNING/SCHEDULING MEETING (CDRL A002)

The Contractor shall participate in meetings In Accordance With (IAW) specific task orders and with AEWS

SPO concurrence, items of discussion may be combined with the quarterly status review (Section 3.2.2.2). If required by the AEWS SPO, the Contractor shall conduct an informal initial planning/scheduling meeting to discuss requirements, determine level of effort, schedule of activities, and CDRL deliveries. The Contractor shall respond to the Government’s request for a Task Planning/Scheduling Meeting within five working days of initial notification. Unless otherwise specified by the task order, these meetings shall be conducted via teleconference; subjects may be combined under one meeting. Upon request the Contractor shall be submitted minutes IAW CDRL A002.

3.4.2 TECHNICAL CALL-IN SERVICE

The Contractor shall be available for AEWS SPO support IAW the Contractors established work schedule. All requests for Contractor support will be initiated by the AEWS SPO, which will authorize the Contractor to proceed with technical tasks.

3.4.3 TEST SUPPORT

If identified as part of a task order, the Contractor shall perform system integration and test at the AEWS EFAC at Hill AFB, or at a site location determined by the AEWS SPO to ensure that hardware and software work together as intended. The activity of system integration and test may require the use of all verification methods

(i.e., Inspection (I), Analysis (A), Demonstration (D), and Test (T)). The Contractor shall analyze the test data collected during testing to determine if the specifications and requirements were met in accordance with the

SSS and to verify that software operation and software/hardware functions are IAW requirements as determined by Contractor written and Government approved test procedures.

If identified as part of a task order, the Contractor shall develop and submit for Government approval, a separate test plan and test procedure for software changes. The Contractor shall document test results in a standalone test report. All testing documentation shall be IAW Test Plan (CDRL A003), Test Procedure (CDRL

A004).

3.4.4 ROUTINE TASKS

The Contractor will not be required to provide the Government a ROM for individual tasks under 10 man hours, unless requested, based upon the engineering support requested within a time period agreed to Government and

Contractor.

3.4.5 HIGH EFFORT TASKS

For any effort expected to exceed 10 man hours, the Contractor shall provide to the Government a Rough Order of Magnitude Estimate (ROM) before Government pre-authorization occurs, based upon the engineering support requested within a time period agreed to during the Task Planning/Scheduling Meeting (3.2.2.2) IAW

CDRL A002.

3.4.6 SPECIAL TASK OPTIONS

If required by the AEWS SPO, the Contractor shall provide to the AEWS SPO a Firm Fixed Price (FFP) within a time period as agreed upon by the Government SPO and contractor, for engineering support and software changes necessary for special task options.

Upon issue of a special (Option) task order by the Government SPO and within 30 days, or as agreed upon by the AEWS SPO and Contractor; the Contractor shall conduct a Technical Interchange Meeting (TIM) for the purpose of discussing support requirements.

If tasked by the AEWS SPO, the Contractor shall prepare an ECP IAW CDRL A009, for each optional tasks.

If required by the AEWS SPO, The contractor shall verify functionality and provide engineering support for the purpose of Government test and Government required certifications.

3.4.6.1 Enhanced Performance and Status Monitoring (Option #1)

If issued as specific task by the AEWS SPO, the capability shall be provided to automatically report real time, (on-line), PSR and SSR System Performance Status Reports at the LCT and RCT displays. The enhanced performance monitoring shall show the PSR and SSR operating state as fully operational (Green), Limited

Capability (Amber), or Severely Degraded (Red). Along with the PSR and SSR performance indicator, the cause for degraded Amber or Red status shall be provided. Rated performance parameters are primary radar and secondary radar transmit power and sensitivity, primary and secondary radar detection, PSR/SSR Correlation, positional accuracy, false target reports, loss of function(s), missing or degraded interface signals or data, and degraded performance due to a combination of measured parameters. Additional measures of performance may be implemented pending contractor recommendations and with approval by the Government SPO.

3.4.6.2 Mode 5 Platform Integration (Option #2)

If issued as specific task by the AEWS SPO, the contractor shall provide engineering support and/or software needed to implement AIMS MK XIIA Mode 5 capability. Tasking is intended to resolve software related issues or problems, support temporary fixes, assist with software, hardware settings, firmware configuration changes or settings, ASTERIX message updates (inclusion of radar and crypto status), filtering of message data to active and passive users, and support required for system certifications. Items covered are the PSR, the AN/UPX-48, and MCS.

3.4.6.3 Mode S Platform Integration (Option #3)

If issued as specific task by the AEWS SPO, the contractor shall provide engineering support and/or software needed to implement Mode S or ADS-B capability. Tasking is intended to resolve software related issues or problems, support temporary fixes, assist with software, hardware settings, firmware configuration changes or settings, ASTERIX message updates or additions, filtering of message data to active and passive users, and support required system certifications. Items covered are the PSR, the AN/UPX-48 MSSR, and the MCS.

3.4.7 TRAINING

This task order may be issued in total or in part. The AEWS SPO authorized POC may request additional task orders to meet the overall task objectives.

If required by the Government SPO, the contractor shall provide informal training to the system end users

(Engineers/Technicians) on new software releases that significantly affect the form or utility of the Mission

Software or support software. Required training may include operation, Man-Machine Interface (MMI) and other topics that are necessary to operate with the new or modified software. The training may be formal

(classroom), On-the-Job-Training (OJT), or a combination.

3.4.8 TASK ORDER CDRLS

The Government will identify any CDRL’s required as part of the task order within the task order.

3.5 TECHNICAL DATA PACKAGE

3.5.1 TECHNICAL ORDERS, DRAWINGS, AND INSTRUCTIONS (CDRL 006, CDRL 007, CDRL 008)

If required by the AEWS SPO, the Contractor shall provide updates to existing Technical Orders, drawings or data, or provide new Technical Orders, drawings or data, delivered in the same style and format as the current documents. The Contractor shall provide the AEWS SPO with software installation and operating instructions for each new software release. All Contractor-developed and modified COTS software that use firmware or programmable devices shall be fully documented and the programming files and instructions provided to the

Government. The technical data shall be provided in CDRL A006 and CDRL A007. Other support documentation will be included IAW (Section 3.2.5) and the Data Accession List, DAL (CDRL A008).

3.5.2 ENGINEERING CHANGE PROPOSAL (ECP) (CDRL A009)

If tasked by the AEWS SPO, the Contractor shall prepare an ECP IAW CDRL A009, either Class I or Class II, for any of the following:

Major (Class I) ECPs have any combination of the following:

1. A change that affects specified and approved requirements including safety, reliability, supportability, and quantitative requirements that result in product attributes that would be outside specified limits or specified tolerances.

2. A change that affects any approved acquisition baseline (i.e., Functional, Allocated, or Product

Baselines).

3. A change that affects compatibility with interfacing products including such products as test equipment, support equipment, software, firmware, and products furnished by an Acquirer or that affects one or more of the following:

a) Delivered operation or servicing instructions

b) Required calibration to the extent that product identification should be changed.

c) Interchangeability or substitutability of replaceable products, assemblies, or components

d) User skills or user physical attributes

e) Operator or maintenance training

f) Requires retrofit of delivered products (e.g., by product recall, modification kit installation, attrition, replacement during maintenance using modified spares)

g) Performance

h) Maintainability, durability, or survivability

i) Weight, balance, moment of inertia

j) Electromagnetic characteristics

k) Impact to logistical support requirements such as training, technical or operational manuals, spares, maintenance procedures or equipment, etc.

l) Re-qualification of the item

m) Domain certification (e.g., airworthiness, seaworthiness)

n) Source (supplier of an item) listed on a Source Control Drawing

o) Biomedical factors or human factors engineering

p) Personnel manning

q) Corrects deficiencies

r) Adds or modifies interface or interoperability requirements

s) Changes the operational capabilities or logistics supportability of the system or item and the change is significant and measurably changes the effectiveness

t) Life cycle costs/savings

u) Prevents slippage in an approved production schedule

4. A change that does not meet the above criteria but does impact cost/price/delivery to customer(s), including incentives and fees, guarantees, warranties, and contracted deliveries or milestones.

Minor (Class II) ECPs do not impact the criteria above for Major (Class I) changes.

The Contractor shall complete page 1 of the ECP form (DD1692) and any other pages specified in the task order. The DD1692 can be found at:

http://www.dtic.mil/whs/directives/forms/dd/ddforms1500-1999.htm

3.5.3 SOFTWARE VERSION DESCRIPTION (SVD) (CDRL A010)

If required by the Government SPO, the contractor shall provide a Baseline SVD (CDRL A010), which will include the entire system software baseline to include the AN/FPS-117 radar and subsystems, AN/UPX-48, mission software, support software, firmware, operating systems & utilities, patches and all COTS software.

http://www.dtic.mil/whs/directives/forms/dd/ddforms1500-1999.htm

3.5.3.1 Baseline SVD

The baseline SVD shall include software configured items, meaning a listing all software and version identifiers that are required to be installed on the LCT/RCT terminals, the Radar data Processor (RDP), all servers, all routers, and other devices that require software or firmware installation.

3.5.3.2 Subsequent SVD Releases

The contractor shall provide subsequent SVD releases for software and firmware as directed by the SPO POC.

Subsequent to the delivery of the initial Baseline SVD as indicated in paragraph 3.5.3.1, each new SVD shall clearly identify all changes from the previous baseline SVD, including functional changes, new or changed documentation, upgrades and new requirements to any/all software, firmware, operating systems & utilities and all COTS software.

3.5.3.2 SVD Configuration Items

The SVD shall include all Configuration Items and parts of software impacted by the changes along with recommended regression testing to be accomplished by the contractor and/or the Government.

The SVD shall list all changes to individual site configuration file settings.

The SVD shall contain all unique instructions, procedures, and changes to operation that are not listed within existing Technical Orders.

If software changes cause changes to drawings or other technical data, the SVD shall identify all items and/or data that have changed.

3.5.4 TASK ORDER CDRLS

The Government will identify any CDRL’s required as part of the task order within the task order.

3.5.5 SUBJECT MATTER EXPERTS

The contractor shall provide subject matter expert support during the training.

3.5.6 TRAINING MATERIALS

Training support documentation will be included IAW (Section 3.2.5) and the Data Accession List, DAL

(CDRL A008).

3.5.6.1 Government Purpose Rights to Training Materials

The Contractor shall grant Government Purpose rights to all training materials used during the contractor conducted training. The Contractor shall allow the Government to copy, reproduce, or include such materials in separately conducted Government or Government contracted training.

3.5.7 TASK ORDER CDRLS

The Government will identify any CDRL’s required as part of the task order within the task order.

3.5.8 GOVERNMENT ACCEPTANCE (DD-250)

Government receipt and acceptance will be verified by a Government signed DD-250.

3.6 SECURITY

The Contractor shall follow security requirements as defined in the AEWS Security Classification Guide (SCG) and the DoD AIMS SCG. The Contractor shall report all security incidents immediately to the Government and obtain Government approval of the action to be taken before closure.

SCG.pdf DoD AIMS 2009 SCG.pdf

Contractor shall abide by all security requirements as detailed in the workload agreements or as briefed by site personnel. Site clearances may be required when conducting work at Contractor or Government facilities, or within Canada. Contractor personnel shall obtain the required clearances prior to engaging in activities requiring such.

4. PERFORMANCE SERVICE SUMMARY

The Contractor performance will be evaluated by AEWS Program Office IAW Table 4 Performance Service

Summary (PSS).

Table 4 is the list of performance objectives and standards that must be met by the contractor. This matrix details the method of surveillance the Government COR will use to validate and inspect these performance elements. Inspection of each element will be documented in the COR file.

Performance standards define the level of service required under the contract to successfully meet the performance objective. The inspection methodology defines what, how, and when objectives will be assessed in measuring performance. The PSS will be used to form the foundation of the COR’s inspection checklist.

Table 4 – Performance Service Summary

Inspection &

PWS

Paragraph

Performance

Objective/

Elements

Standard/AQL

Inspection

Performance Rating

What How/Method When/Freq

PSS# 1

Para: 3.2

Program

Management and all sub-paragraphs

CDRL A001,

A002

Contractor shall provide overall program planning, control, contract/ subcontract management.

Manage tasks

IAW the PWS

Contractor’s management of the program results in no uncorrected

Corrective Action

Report (CAR) within a 12 month performance period.

All products and services are delivered within agreed upon cost, schedule, and performance

IAW the PWS and task order.

Cost, schedule and performance.

Number of

CARs and

Performance

Assessment

Reports

(PAR)

associated with each task order.

CDRL

deliveries

Inspect deliverables for completeness and accuracy.

Method:

Verify compliance with schedules.

Contractor meets on time delivery of products and services.

Verify completed documentation such as quarterly status review, meeting minutes, on-time contractor response.

At completion of each task order and after each monthly status report.

Meet Standard

PSS# 1.1

Para:

3.2.2.1

3.2.2.2

3.2.4

Deficiency

Reporting

CDRL A002

Deficiency tracking and resolution process is in place and is used effectively to resolve system deficiencies.

No more than 1 reported deficiency not recorded or tracked during the

12 month reporting period

Content, accuracy, and currency of

DR database, at CDRL delivery IAW

PWS 3.2.2.2

The

Government’s

DR database will be compared to the

Contractor’s database.

Compare PTR submissions with DR database

Verify updates as discussed during bi-weekly status meetings and quarterly status review.

Quarterly review with bi-weekly updates

IAW CDRL

A002 and PWS

Deficiency Reporting meets standard, is updated, and accurate for bi-weekly meetings.

Uncorrected DR’s will generate a PAR.

3 PARS over a 12 month period will generate a

CAR

Paragraph

Performance

Objective/

Elements

Standard/AQL

Inspection

Performance Rating

What How/Method When/Freq

PSS#1.2

Para:

3.2.3

Configuration

Management

Maintain

Software

Baseline IAW

AEWS SPO

requirements

For any Software change the

Government shall be notified before the change is implemented

No unapproved changes to the

Software baseline

Proposed software baseline changes

Periodic with quarterly updates per

CDRL A002,

and PWS

Review

Contractor modifications and review

ECPs

Notification of any change proposal

ECP if tasked

Contractor notifies

AEWS SPO 60 days prior to proposed change

PSS#1.3

Para:

3.2.3.1

Reporting of obsolescence/Non

-availability issues

Notification and resolution of Software obsolescence/N on-availability issues

Software obsolescence/Non

-availability items are identified to the AEWS SPO in a timely fashion obsolescence/

Non-availability notifications and obsolescence reports

Quarterly as per CDRL

A002 and

3.2.2.2.

Annually as per A006 and

3.2.3.1 documentation

Random check upon CDRL delivery

Contractor notifies

AEWS SPO quarterly

IAW PWS 3.2.2.2

PSS#1.4

All CDRLs A001 through A010

CDRL

requirements met IAW PWS and as agreed to for each task

On-time delivery with required content IAW

Data Item

Description

(DID) and is

Government approved

All CDRLs

A001 through

A010

Timely CDRL delivery and content

CDRLs

Random check upon CDRL delivery

Meets Standard

On-time CDRL delivery, meets DID requirements, content and accuracy, with no more than 5 minor errors that do not change intent of the

CDRL.

Government acceptance of task completion.

PSS#2

Para: 3.3 and all sub-

Maintenance

CDRL A007

Software meets quality requirements

Any software/firm ware/program mable device changes made under this

PWS shall meet required functionality and not degrade the performance

Maximum of 2

QDRs during any 12 month period. No second re-work for the same reported deficiency.

Software operation

Software

Installation and Test

By testing

A) Verify operation upon install and Test

B)Long Term

Operation

Meets standard with no more than 2 PARs and no CARs in the reporting period

QDR shall be resolved within 90 days of

QDR receipt from the

Government

Paragraph

Performance

Objective/

Elements

Standard/AQL

Inspection

Performance Rating

What How/Method When/Freq

PSS#3

Para: 3.4 and all sub-

Engineering

Support Services

CDRLs A002, A003, A004, A005

Meet task requirements and on-time delivery of documentation, products, and services

Meets delivery of task required services and deliverable products and services

Government at task completion

IAW CDRL

A002, A003, A004, A005, Inspect CDRLs

Verify CDRLs are in compliance

Upon receipt of

CDRL delivery and at task completion

Meets Standard

On-time CDRL delivery, meets DID requirements, content and accuracy, with no more than 5 minor errors that do not change intent of the

CDRL

of task completion

PSS#4

Para: 3.5 and all sub- paragraphs

Technical Data

Package

CDRL A006,

A007, A008,A009,A010

Government has necessary

Technical data and documentation to maintain and sustain the

AN/FPS-117

radar

On-time delivery of products per the task order with agreed upon content and completeness. No more than 3 minor errors per delivery.

Maximum of one significant error that prevents use of technical data.

The SPO will submit a CAR for each significant error left uncorrected

CDRL

deliveries, A006, A007, A009,A010

Inspect CDRLs

Inspect procedures and instructions during acceptance test

Upon receipt of

CDRL delivery and at task completion

Meets Standard with No

CARs of delivered product

PSS#5

Para:3.4.7, 3.5.2, 3.5.5, 3.5.6.1

Training

A008

Government has necessary training to install and operate software required to maintain the

AN/FPS-117

radar

On-time delivery of training and documentation per the task order with agreed upon content and completeness.

CDRL

deliveries, A008

Training conducted as per schedule.

Student

Evaluation

Upon receipt of training

Meets Standard, On

Time delivery as per task order.

5. ADMINISTRATIVE

5.1 EQUIPMENT, SOFTWARE, AND TOOLS

5.1.1 GOVERNMENT FURNISHED EQUIPMENT (GFE) REQUIREMENTS

The contractor shall notify the Government if any Government Furnished Equipment (GFE) is required for depot software maintenance.

5.1.2 TEST EQUIPMENT CALIBRATION

All test equipment used for software certification and/or test shall have current calibration and certification.

5.2 OVERTIME

Normally, overtime will not be authorized in performance of this contract unless under an emergency condition where time is critical. Contractor personnel are authorized Government funded overtime only if approved by the Contracting Officer. All overtime shall be IAW the terms of this contract.

5.3 PACKAGING, HANDLING, STORAGE, AND TRANSPORTATION

5.3.1 PACKAGING AND TRANSPORT

Most packaging, except for reusable containers, will be disposed of at the destination. Packaging guidance can be found within the MIL-E-17555H document or in conformance to “best commercial practices.” Additional guidance is provided in LMC document 77A595624, Integrated Logistics Support Plan (ILSP) (Section 5). The

Contractor shall be responsible for the preservation, packaging, packing, and shipping of all items to be delivered under the terms of this contract. The Contractor shall be responsible for all transportation and costs to move items from the Contractor’s site to the Government designated staging area. If Contractor travel is required to the radar site or MCS site in support of this contract, the Contractor shall be responsible for all

Contractor personnel, equipment and tools to and from the radar/MCS location or between staging locations during any Contractor support activities(Section 3.6, 5.6 and Attachment B). The Contractor shall provide copies of manifests and commercial bills of lading to the Government, on request, for any shipments made under this contract. The Contractor shall replace any equipment or property damaged during shipment and will be responsible for delays in the contract due to such damage. Government receipt and property transfer will be verified by a Government signed certificate of conformance in contractor format following shipment of the asset under DD Form 1149 Requisition and Invoice/Shipment Document. The Government will be responsible for the transportation from the Government site to the Contractor’s designated facility and from the Government staging area to the radar site or MCS location.

The designs of packaging, preservation, and packing applicable to the shipment of material shall be governed by the ultimate destination, modes of transportation to be used, length and type of storage, requirements for reshipment, and induced or environmental conditions. The package designs developed and approved for system unique items shall maintain the established reliability levels of equipment being prepared for delivery and shall ensure safe, damage-free delivery. Handling instructions on final packing shall be conspicuously marked.

System equipment shall be designed and constructed to ensure it is in the transport configuration, no part will become loose or shift its setting, position, or orientation, no part will become permanently warped, deformed, or damaged, and the equipment will not suffer degradation in performance or useful life.

5.3.2 SPECIAL ELECTROSTATIC SENSITIVE DEVICE REQUIREMENTS

Equipment and devices (including software media and programmable devices, certain equipment and circuit cards) that are sensitive to environmental field forces will be packaged to ensure maximum protection and eliminate potential damage from the environment.

5.3.3 REUSABLE CONTAINERS

Reusable containers may be used for transit of select high cost, high failure rate items. Reusable containers are designed to facilitate equipment packing and unpacking and are provided with special cushioning, blocking and a means of handling. The containers will have provisions for dehydrating entrapped moisture. Reusable containers meet all protective requirements for equipment or software media. Special containers will be developed to ensure maximum protection, facilitate ease of handling, and eliminate potential damage to contents.

5.3.4 RECEIVING INSPECTION

The contractor shall notify the COR of all damages and/or shortages discovered, as soon as possible after receipt of item(s) at the contractor’s facility.

5.3.5 MARKING

The contractor shall permanently and legibly mark each shipping container bill of materials with the contractor’s name, Air Force contract number, part number/version, and date.

5.4 AEWS POINTS OF CONTACT (POC)

5.4.1 AEWS PROGRAM MANAGER/CONTRACTING OFFICER REPRESENTATIVE (COR)

The government Program POC for this PWS is the AEWS AN/FPS-117 Program Manager, Mary Barnett, AFLCMC/HBZIA, (801) 777-8990.

5.4.2 SPO LEAD ENGINEER

The System Engineer POC for this PWS is the AEWS AN/FPS-117 Lead Engineer, Tim Perkins, AFLCMC/HBZIA, (801) 775-5205.

5.5 AN/FPS-117 SITE LOCATIONS

All work completed at AN-FPS-117 facilities may require a completion of a site Workload Agreement. Sites and applicable workload agreements are located in Appendix B (Attachments 1 – 4) of this PWS.

5.6 SHIPPING/MAILING ADDRESSES

Shipping addresses are in Appendix D. Any changes or additions will be provided by the AEWS program manager.

All work completed at AEWS AN-FPS-117 facilities may require the completion of a site Workload

Agreement. Sites and applicable Workload agreements are located in Section 6, Appendices.

5.7 TRAVEL REQUIREMENTS

The Contractor shall follow travel requirements using guidance provided in this PWS and the Attachments by coordinating with United States Air Force (USAF) POC, AFLCMC/HBZIA Program Office and POCs listed in

Appendix B of this PWS. Travel requests shall submit travel requests and obtain approved from USAF contracting officers before any travel occurs for any support to any radar/MCS sites. Airfare for travel and per

Diem shall be billed in accordance with Federal Acquisition Regulation (FAR) (available at http://farsite.hill.af.mil). Per Diem rates can be found at http://www.defensetravel.dod.mil/site/perdiemCalc.cfm. The contractor is responsible for making all necessary travel arrangements.

6. APPENDICES

Appendix A contains program Acronyms; Appendix B contains 4 Workload Agreement attachments, one each, for Alaska, Canada, Hawaii, and Puerto Rico; Appendix C contains the Software List; Appendix D contains the

Shipping Address List; Appendix E contains the Master CDRL List.

http://farsite.hill.af.mil/ http://www.defensetravel.dod.mil/site/perdiemCalc.cfm

APPENDIX A - Acronyms

Ao Operational Availability

AEWS Atmospheric Early Warning System

AIMS Air Traffic Control Radar Beacon System (ATCRBS)/Identification

Friend-or-Foe (IFF)/MARK XII System

BER Beyond Economical Repair

C&A Certification and Accreditation

CDRL Contract Data Requirements List

CLS Contractor Logistics Support

CLIN Contract Line Item Number

COR Contracting Officer’s Representative

COTS Commercial Off-The-Shelf

CPIN Computer Program Identification Number

CSCI Computer Software Configuration Item

DAEPM Directorate Aerospace Equipment Program Management

DAL Data Accession List

DFAR Defense Federal Acquisition Regulation

DID Data Item Description

DMSMS Diminishing Manufacturing Shortage Material Shortage

DR Deficiency Report

ECP Engineering Change Proposal

EPRP Essential Parts Replacement Program

FAR Federal Acquisition Regulation

FFFI Form Fit Function and Interface

FFP Firm Fixed Price

GFE Government Furnished Equipment

GP Group

IA Information Assurance

IAW In Accordance With

ILSP Integrated Logistics Support Plan

IUID Item Unique Identification

LMC Lockheed Martin Corporation

LRRS Long-Range Radar Site

LRU Line Replacement Unit

LSS Logistics Support Sites

MAR Minimally Attended Radar

MCS Maintenance Control System

MSSR Mono-Pulse Secondary Surveillance Radar

NLT No Later Than

NSN National Stock Number

NWS North Warning System

OEM Original Equipment Manufacturer

POC Point Of Contact

POE Point of Entry

PSR Primary Surveillance Radar

PWS Performance Work Statement

QA Quality Assurance

QDR Quality Deficiency Report

RAM Reliability Availability Maintainability

RECS Radar Environmental Control System

RMS Reliability, Maintainability and…