B-52_TS_DRAFT_PWS_22_JAN_15_-_with_appendices.pdf

PDF 832 KB Posted

Attached to
B-52 Training System Recompete
Solicitation number
FA8621-15-R-6338
Issued by

About this file

Draft PWS dated 22 Jan 2015

View the file

Other files

File Type Posted
What's_New_in_B-52_-27_Oct_2015.pdf PDF
What's_New_in_B-52_-_09_July_2015.pdf PDF
Atch_4_CBA_Barksdale_Minot_AFB-.pdf PDF
FA8621-15-R-6338_Amendment_03.pdf PDF
FA8621-15-R-6338-0002.pdf PDF
What's_New_in_B-52_-_06_July_2015.pdf PDF
Atch_12_B-52_TS_Section_L_--_7-02-2015.pdf PDF
Exhibit_A_CDRL-Package_22_Jun_2015.pdf PDF
What's_New_in_B-52_-26_Jun_2015.pdf PDF
Atch_3_-_B-52_TS_Price_Matrix_19_JUN_2015.xlsx XLSX spreadsheet
Atch_1_-_PWS_19_Jun_2015-1.pdf PDF
Atch_12_B-52_TS_Section_L_--_6-22-2015.pdf PDF
FA8621-15-R-6338_Amendment_01.pdf PDF
What's_New_in_B-52_-19_Jun_2015.pdf PDF
Responses_to_RFP_Questions_6-19-2015.pdf PDF
ppi_tool.accdb —
What's_New_in_B-52_-_29_May_2015.pdf PDF
Atch_2_DD254_Draft.pdf PDF
Atch_7_GFP_GFE_GFI_Spares.pdf PDF
Atch_4_CBA_Barksdale_Minot_AFB.pdf PDF
Atch_13_Section_M.pdf PDF
FA8621-15-R-6338.pdf PDF
Atch_5_WD_Barksdale_1-23-2015.pdf PDF
Atch_1_PWS.pdf PDF
Atchm_12_Appendix_L-6_Proposal_Traceability_Matrix.xlsx XLSX spreadsheet
Atch_3_-_B-52_TS_Price_Matrix_28_MAY_2015.xlsx XLSX spreadsheet
Atch_8_Host_Base_Agreement_Barksdale_AFB.pdf PDF
Exhibit_A_-_CDRL.pdf PDF
Atch_12_Section_L.pdf PDF
What's_New_in_B-52_-_28_May_2015.pdf PDF
Atch_6_WD_Minot_1-23-2015.pdf PDF
Atch_9_Host_Base_Agreement_Minot_AFB.pdf PDF
Exhibit_A_CDRLs.pdf PDF
What's_New_in_B-52_-_08_APR_2015.pdf PDF
Atchm_13_B-52_TS_Section_M_Draft8Apr15.pdf PDF
!_Soliciation_FA8621-15-R-6338_--_3_Apr_2015.pdf PDF
Atchm_12_B-52_TS_Section_L_3Apr15.pdf PDF
Atch_1_PWS_DRAFT08APR15.pdf PDF
What's_New_in_B-52_-_09_FEB_2015.pdf PDF
Industry_Q As_09Feb_2015.pdf PDF
What's_New_in_B-52_-_22_JAN_2015.pdf PDF
B-52_TS_RFP_Section_M_Draft_22JAN15.pdf PDF
B-52_TS_Section_L_Draft_22_Jan_15.pdf PDF
What's_New_in_B-52_-_05_JAN_2015.pdf PDF
What's_New_in_B-52_-_23_DEC_2014.pdf PDF
What's_New_in_B-52_-_10_DEC_2014.pdf PDF
B-52_Training_Systems_(TS)_Barksdale_Site_Visit_Agenda_16_Dec_14.pdf PDF
What's_New_in_B-52_-_08_DEC_2014.pdf PDF
One_on_one_meeting_Questions_Answers.pdf PDF
What's_New_in_B-52_-_24_Nov_2014.pdf PDF
Show 40 more

Latest 50 of 81 listed here. See the rest on GovTribe.

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

DRAFT

B-52 TRAINING SYSTEMS

SUPPORT

PERFORMANCE WORK STATEMENT

FA8621-15-R-6338

22 Jan 15

Prepared by:

DEPARTMENT OF THE AIR FORCE

SIMULATORS DIVISION

AIR FORCE LIFE CYCLE MANAGEMENT CENTER

WRIGHT-PATTERSON AIR FORCE BASE, OHIO

PWS CHANGE MATRIX

REVISION MODIFICATION AFFECTED PARAGRAPH(S)

TABLE OF CONTENTS

1. Introduction

1.1 Mission

1.2 Scope

1.3 System Description

2. Management

2.1 Program Management

2.1.1 Management Plan & Key Personnel

2.1.2 Integrated Master Plan and Integrated Master Schedule

2.1.3 Reporting

Financial Management Reporting and Tracking .............................. 15 2.1.3.1

Cost/Schedule Control Systems Reporting ...................................... 15 2.1.3.2

Sustainment Cost Reporting ............................................................ 16 2.1.3.3

Contract Value Reporting ................................................................. 16 2.1.3.4

Contractor Manpower Reporting ..................................................... 16 2.1.3.5

Contractor Device Performance Report ........................................... 16 2.1.3.6

50/50 Depot Reporting ..................................................................... 17 2.1.3.7

2.1.4 Applicable Documents

2.1.5 General Services and Material

2.1.6 Program Meetings, Reviews, Conferences, and Working Groups

Post Award Conference .................................................................... 18 2.1.6.1

Program Management Reviews ....................................................... 18 2.1.6.2

Program Weekly Integrated Product Team Meetings ...................... 18 2.1.6.3

2.1.7 Associate Contractor Agreements

2.1.8 Subcontractor Management

2.1.9 Risk Management Plan

2.1.10 System Security

Acquisition Systems Protection ....................................................... 20 2.1.10.1

Cybersecurity ................................................................................... 20 2.1.10.2

Platform Information Technology .................................................... 21 2.1.10.3

Certification & Accreditation ........................................................... 21 2.1.10.4

Remanence Security ......................................................................... 22 2.1.10.5

Supply Chain Risk Management ..................................................... 22 2.1.10.6

Architecture Analysis ....................................................................... 23 2.1.10.7

Cybersecurity Risk Assessment ....................................................... 23 2.1.10.8

System Security Testing ................................................................... 23 2.1.10.9

System Security Working Group .................................................. 24 2.1.10.10

Information Security ..................................................................... 24 2.1.10.11

Technology Control ...................................................................... 24 2.1.10.12

Operations Security ....................................................................... 24 2.1.10.13

Communications Security ............................................................. 24 2.1.10.14

Emissions Security ........................................................................ 25 2.1.10.15

Industrial Security ......................................................................... 25 2.1.10.16

Personnel Security ........................................................................ 25 2.1.10.17

Security Training ........................................................................... 25 2.1.10.18

Government Facility Physical Security ........................................ 26 2.1.10.19

2.1.10.19.1 Government Facilities Key and Combination Control 26

2.1.10.19.2 Access to Government Facilities

Contingency Procedures for Government Facilities ..................... 27 2.1.10.20

2.1.11 Property

Government Furnished Property (GFP) ........................................... 27 2.1.11.1

Damage to Government-Furnished Property ................................... 27 2.1.11.2

Government-Provided Facilities ...................................................... 28 2.1.11.3

2.1.12 Janitorial Services

2.1.13 Administrative Services

2.1.14 Packaging, Handling, Storage and Transportation (PHS&T)

Packaging and Marking ................................................................... 29 2.1.14.1

Transportation and Transportability ................................................. 29 2.1.14.2

2.1.15 Demilitarization, Disposal, and Disposition

2.1.16 Studies and Analysis

Cockpit Procedures Trainer (CPT) Study and Analysis ................... 30 2.1.16.1

Electronic Warfare Simulator (T4) Trainer Study and Analysis ...... 30 2.1.16.2

WST Aerodynamic Model Upgrade Study and Analysis ................ 31 2.1.16.3

2.1.17 Quality Control

Inspection System ............................................................................ 31 2.1.17.1

Inspection Files ................................................................................ 32 2.1.17.2

Deficiency Prevention ...................................................................... 32 2.1.17.3

2.1.18 Services Summary

2.1.19 Quality Assurance

2.1.20 Rough Order of Magnitude Cost Estimates

2.1.21 Life Cycle Cost Estimate

2.1.22 Locations and Hours of Work

2.1.23 Contractor Training

2.1.24 Labor Strike Plan

2.2 Engineering & Technical Management

2.2.1 Systems Engineering Management Plan (SEMP)

2.2.2 Requirements Traceability

2.2.3 Design Criteria

Design Criteria Freeze ..................................................................... 35 2.2.3.1

Design Criteria Update .................................................................... 35 2.2.3.2

Completeness of Design Criteria ..................................................... 36 2.2.3.3

Consistency and Currency of Design Data ...................................... 36 2.2.3.4

Design Criteria Problem Resolution ................................................ 36 2.2.3.5

2.2.4 Data Rights

2.2.5 System Design

Software Development ..................................................................... 37 2.2.5.1

Software Licenses ............................................................................ 38 2.2.5.2

System Design Reviews and Audits ................................................ 38 2.2.5.3

2.2.5.3.1 Technical Interchange Meetings

2.2.5.3.2 System Requirements Review (SRR)

2.2.5.3.3 Preliminary Design Review

2.2.5.3.4 Critical Design Review

2.2.6 Diminishing Manufacturing Sources/Material Shortages (DMS/MS) and Obsolescence

2.2.7 Configuration Management (CM)

Configuration Baseline Management .............................................. 41 2.2.7.1

2.2.7.1.1 Functional Baseline Configuration Identification

2.2.7.1.2 Allocated Baseline Configuration Identification

2.2.7.1.3 Product Baseline Configuration Identification

Change Management ....................................................................... 41 2.2.7.2

Configuration Status Accounting ..................................................... 42 2.2.7.3

Data Management ............................................................................ 42 2.2.7.4

2.2.7.4.1 Electronic Data

2.2.7.4.2 Recompetition Data Library

2.2.7.4.3 Master Data Library and Data Accession List

2.2.7.4.4 Technical Data Package

2.2.7.4.5 Documents and Drawings

2.2.7.4.6 Identification Numbering of Documentation and Hardware

Item Unique Identification ............................................................... 45 2.2.7.5

Problem Reporting System .............................................................. 45 2.2.7.6

2.2.8 Test & Evaluation

Acceptance Test Plan (TP) ............................................................... 46 2.2.8.1

Acceptance Test Procedures (ATP) .................................................. 47 2.2.8.2

Statement of Readiness (SOR)......................................................... 47 2.2.8.3

In-Plant/Prototype Test .................................................................... 47 2.2.8.4

2.2.8.4.1 System Performance Assessment (SPA)

2.2.8.4.2 Contractor Engineering Verification Tests (CEVT)

2.2.8.4.3 System Verification Review (SVR)

2.2.8.4.4 Test Readiness Assessment (TRA)

2.2.8.4.5 Functional Mission Assessment (FMA)

2.2.8.4.6 System Performance Evaluation (SPE)

Physical Configuration Audits ......................................................... 49 2.2.8.5

Joint Ready To Ship Assessment (JRTSA) ...................................... 50 2.2.8.6

On-Site/Production Tests ................................................................. 50 2.2.8.7

2.2.8.7.1 Contractor On-site Installation and Test (COIT)

2.2.8.7.2 Facility and Safety Interface Test (FASIT)

2.2.8.7.3 On-Site Test Readiness Assessment

2.2.8.7.4 Functional Mission Assessment (FMA)

Functional Mission Test (FMT) ....................................................... 50 2.2.8.8

Test Reports ..................................................................................... 51 2.2.8.9

Ready for Training (RFT) ................................................................ 51 2.2.8.10

2.2.9 Independent Verification and Validation

2.2.10 Environment, Safety, and Occupational Health (ESOH)

Operational Safety, Suitability & Effectiveness .............................. 52 2.2.10.1

Electrostatic Discharge Control ....................................................... 52 2.2.10.2

Mishap.............................................................................................. 52 2.2.10.3

Hazardous Materials (HAZMAT) .................................................... 53 2.2.10.4

3. Contractor Logistics Support (CLS)

3.1 CLS Personnel

3.2 Aircrew Training Device Availability

3.2.1 Training Device Availability Credit Process

3.3 Maintenance and Logistics Support

3.3.1 Maintenance Documentation

3.4 DMO Support

3.4.1 DMO Facility Support

3.4.2 DMO Security Requirements

3.4.3 DMO Connectivity

3.4.4 Federation Testing

3.5 Operational Requirements

3.5.1 Utilization Preparation

3.5.2 WST Utilization -- System Operation

3.6 Utilization Abort

3.7 Schedule Deviations

3.8 Government Furnished Equipment

3.9 Test, Measurement and Diagnostic Equipment (TMDE)

Calibration/Certification

3.10 Hand Tools and Peculiar Support Equipment

3.11 Recompetition Support Package

3.11.1 RSP Maintenance

3.11.2 RSP Adjustments

3.12 Inventory Control

3.13 Maintenance Data Collection (MDC) System

3.14 Consumables

3.15 Simulation Certification Support

4. Training System Device Modifications and Upgrades

4.1 Contract Priced Options for Concurrency Modifications

4.1.1 Combat Network Communications Technology (CONECT) Upgrade

4.1.2 Identification Friend or Foe (IFF) Mode S/5 Upgrade Modification

4.1.3 1760 Internal Weapons Bay Upgrade (IWBU) Modification

4.2 ECP Modification Requirements

4.2.1 Contract Work Breakdown Structure (CWBS)

4.2.2 ECP Reviews

4.3 Training System Support Center (TSSC)

4.3.1 TSSC Personnel

4.3.2 Simulator Configuration Working Group Participation

4.3.3 TSSC Engineering Accomplishment Report

4.3.4 TSSC Contract Status Reviews

4.3.5 TSSC Equipment and Material

4.3.6 Modification Feasibility Studies

4.3.7 TSSC Annual Plan

4.3.8 TSSC Over and Above

4.3.9 Distributed Mission Operations (DMO)

CAF DMO Test Planning Working Group (TPWG) ........................ 66 4.3.9.1

CAF DMO System Problem Report Working Group (SPRWG) ..... 66 4.3.9.2

CAF DMO Standards Development Working Group (SDWG) ....... 66 4.3.9.3

CAF DMO Standards Implementation Working Group (SIWG) .... 66 4.3.9.4

CAF DMO Configuration Control Board (CCB) ............................ 66 4.3.9.5

Federate Testing ............................................................................... 67 4.3.9.6

Federation Testing ............................................................................ 67 4.3.9.7

Next Generation Threat System (NGTS) and Computer Generated 4.3.9.8 Forces (CGF) System Support

DMO Event Support ........................................................................ 67 4.3.9.9

4.3.10 B-52 Software Block (BSB) Updates

4.4 ATD Concurrency and Fidelity Roadmap

5. New Devices

6. Transition and Relocation Plans

6.1 Initial Transition

6.1.1 SIL and B-52G Flight Station Relocation (Initial)

Pre-Teardown Inspection and Test ................................................... 69 6.1.1.1

Teardown Pack and Ship .................................................................. 69 6.1.1.2

Installation........................................................................................ 69 6.1.1.3

Post-Relocation Inspection and Test ................................................ 70 6.1.1.4

Correction of Discrepancies ............................................................. 70 6.1.1.5

Responsibility for Damage During Relocation ................................ 70 6.1.1.6

Security During Relocation.............................................................. 70 6.1.1.7

6.2 Final Transition

6.2.1 CLS Transition

CLS Transition Support Proposal .................................................... 70 6.2.1.1

CLS Contract Transition .................................................................. 71 6.2.1.2

CLS RSP Transition ......................................................................... 71 6.2.1.3

CLS Software Media ......................................................... 71 6.2.1.4

CLS Facilities................................................................................... 71 6.2.1.5

CLS Office Equipment/Furniture .................................................... 72 6.2.1.6

6.2.2 TSSC and Modification Transition

TSSC/Modification Transition Support Proposal ............................ 72 6.2.2.1

TSSC/Modification Contract Transition .......................................... 72 6.2.2.2

TSSC/Modification RSP Transition ................................................. 72 6.2.2.3

TSSC/Modification Software Media ............................................... 73 6.2.2.4

TSSC/Modification Facilities .......................................................... 73 6.2.2.5

TSSC/Modification Office Equipment/Furniture ............................ 73 6.2.2.6

SIL and B-52G Flight Station Relocation (Final) ............................ 73 6.2.2.7

6.2.2.7.1 Pre-Teardown Inspection and Test

6.2.2.7.2 Teardown Pack and Ship

6.2.2.7.3 Installation

6.2.2.7.4 Post-Relocation Inspection and Test

6.2.2.7.5 Correction of Discrepancies

6.2.2.7.6 Responsibility for Damage During Relocation

6.2.2.7.7 Security During Relocation

6.3 Device Relocation

Appendices

APPENDIX 1: ACRONYM LIST

APPENDIX 2: GLOSSARY

APPENDIX 3: FACILITIES/DEVICES FLOOR DIAGRAMS

APPENDIX 4: TASK AND FREQUENCY CHART

APPENDIX 5: CONECT UPGRADE GENERAL REQUIREMENTS ... Error! Bookmark not defined.

APPENDIX 6: CONECT UPGRADE SPECIFIC REQUIREMENTS . Error! Bookmark not defined.

APPENDIX 7: IFF MODE S/5 UPRGRADE GENERAL REQUIREMENTSError! Bookmark not defined.

APPENDIX 8: 1760 IWBU GENERAL REQUIREMENTS .............. Error! Bookmark not defined.

1. INTRODUCTION

1.1 MISSION

The principal mission of the B-52 Training System (TS) is to ensure high and medium fidelity simulators and training systems are available for aircrew members and maintenance personnel to support creditable training, maintain proficiencies, and increase skill levels. The B- 52 TS consists of Aircrew Training Devices (ATD) and Maintenance Training Devices (MTD).

The customers are Air Force Global Strike Command (AFGSC) and Air Education and Training Command.

1.2 SCOPE

This Performance Work Statement (PWS) describes the tasks associated with Operations, Maintenance, and Support (OM&S) of the B-52 TS, including:

Program Management.

Engineering Management.

Contractor Logistics Support (CLS) for ATDs.

Training System Support Center (TSSC) for ATDs.

Distributed Mission Operations (DMO) support for Weapon System Trainers (WST).

Concurrency and fidelity modifications/upgrades for ATDs and MTDs.

Development, production, and fielding of new ATDs and MTDs, as required.

Relocation of ATDs and MTDs, as required.

Contract transition activities.

ATD and MTD studies and analysis efforts as requested by the Government.

The terms “training devices” and “trainers” are used interchangeably within this PWS.

All sections of this PWS apply to all ATDs unless otherwise directed by a contract modification.

MTD scope will only include modification support, new procurement, studies/analysis, and device relocation, as required. The Contractor shall propose updates and change recommendations to this PWS to the Simulators Division, and the Government has final approval of PWS changes.

1.3 SYSTEM DESCRIPTION

B-52 ATDs. The B-52 ATDs simulate the necessary visual, motion, and aural cues to provide ground training of AFGSC aircrew members and maintenance personnel. In total, there are 10 ATDs, located at Barksdale Air Force Base (AFB) and Minot AFB, as depicted in Table 1 below. The ATDs are supplemented by a Support Center System (SCS) with peripheral equipment. The SCS is designed to function as the principle systems supporting the computer programs for the 10 ATDs. In addition to the ATDs, a Government-owned B-52 TS System Integration Laboratory (SIL) will be located at a Secret clearance level facility provided by the contractor. The SIL shall be maintained in a similar configuration to a WST, but without motion.

A description of the SIL can be found in PWS, Appendix 2. Finally, a B-52G flight station is currently located with the SIL.

Training Device

Description Number Location

Weapon System Trainer

(WST)

Composed of major components to train all B-52 aircrew positions in stand-alone or integrated missions, as well as DMO. The components are:

Flight Station Subsystem (FSS) with six degrees of freedom motion base

Offensive Station Subsystem (OSS) with three degrees of freedom motion base

Defensive Station Subsystem (DSS) Debrief System Instructor/Operator consoles Digital Image Generation Digital Radar Land Mass System.

Barksdale AFB (2)

Minot AFB (1)

Offensive System Mission Trainer (OSMT)

Consists of an offensive station to train navigators (similar to the WST OSS) without motion.

2 Barksdale AFB (2)

Cockpit Procedures Trainer (CPT)

Provides training in procedures, skills, and the knowledge required for safety of flight tasks.

Capability for training normal, emergency, and certain instrument approach procedures.

1 Barksdale AFB (1)

Electronic Warfare Simulator

(AN/ALQ-

T4(V)4)

Provides ground training in procedures, skills and knowledge required for safety of flight and warfighting combat tasks, electronic warfare emergency procedures and jamming techniques for the Electronic Warfare Officer.

Barksdale AFB (3)

Minot AFB (1)

SIL

Composed of major components to train all B-52 aircrew positions in stand-alone or integrated missions, as well as DMO. The components are:

Flight Station Subsystem (FSS) Offensive Station Subsystem (OSS) Defensive Station Subsystem (DSS) Debrief System Instructor/Operator consoles Digital Image Generation Digital Radar and Mass System

Contractor Facility

Table 1

B-52 MTDs. The B-52 MTDs provide for the simulation of fault isolation and remove/replace maintenance activities for ground training of various B-52 aircraft subsystems.

In support of training requirements for B-52 maintenance personnel, the family of B-52 MTDs consists of 17 devices located at Barksdale AFB, Sheppard AFB, and Minot AFB, as depicted in Table 2 below. An additional two devices (Wheel and Brake System Trainer) are currently in procurement. The MTD scope of this contract will only include the required support for concurrency and fidelity upgrades, new MTDs, studies and analysis efforts, and device relocation, as required. Any tasks for MTDs will be through individually awarded Engineering Change Proposals (ECP), as described in Section 4 of this PWS. CLS and TSSC support for MTDs are not within the scope of this contract.

Training Device

Description Number Location

Bomb Navigation System Trainer

Demonstrates the operation, maintenance, inspection and troubleshooting of the bombing navigation system installed on B-52H aircraft.

Two configurations: Resident and Mobile.

4 Resident:

Barksdale AFB (1)

Minot AFB (1)

Sheppard AFB (1)

Mobile:

Sheppard AFB (1)

Electro-Optical Viewing System Maintenance Trainer

Demonstrates the operation, maintenance, inspection, and troubleshooting of the AN/ASQ- 151 Electro-Optical Viewing System installed on B-52H aircraft. In addition to two operational trainers

2 Minot AFB (1)

Sheppard AFB (1)

Ejection Seat And Escape Hatch System Trainer

Includes representative ejection seats and escape hatches, as installed in the B-52H aircraft, and demonstrates basic seat functions, seat maintenance, escape hatch maintenance, and ejection procedures.

2 Barksdale AFB (1)

Sheppard AFB (1)

Fuel Systems Trainer

Demonstrates the management, routing, and emergency handling of the fuel system in the B- 52H airplane with the aid of an animated schematic diagram.

2 Barksdale AFB (1)

Sheppard AFB (1)

Main Landing Gear System Trainer

Displays the significant components of the landing gear system, as installed in the B-52 airplane, and demonstrates their operative characteristics.

1 Barksdale AFB

Electrical Power System Trainer

Depicts the electrical power system of the B-52 aircraft in an operational form in order to teach operational, inspection, and maintenance procedures.

1 Barksdale AFB

Flight Control System Trainer

Displays the significant components of the flight controls system as installed in the B-52 aircraft and demonstrates their operating characteristics.

1 Barksdale AFB

Autopilot System Trainer

Basic system used for generic autopilot training. 1 Sheppard AFB

Stability Augmentation System Trainer

Provides an operable B-52 aircraft stability augmentation system for demonstrating maintenance, inspection, and troubleshooting procedures.

1 Barksdale AFB

Training Device

Description Number Location

Window Electric Heater Trainer

Basic system used for troubleshooting the window electrical system.

1 Sheppard AFB

Air Conditioning, Pressurizing And Pneumatic System Trainer

Demonstrates visually with an animated schematic diagram the operation, routing, and control of the pneumatic system in the B-52H aircraft.

1 Barksdale AFB

Wheel and Brake System Trainer

Displays the significant components of the wheel and brake system, as installed in the B-52 airplane, and demonstrates their operative characteristics. (These trainers are in procurement; not yet delivered or operational.)

2 Barksdale AFB (1)

Minot AFB (1)

Table 2

2. MANAGEMENT

2.1 PROGRAM MANAGEMENT

All tasks within this Program Management section shall be applied by the Contractor throughout all contract activities.

2.1.1 Management Plan & Key Personnel

The Contractor shall develop, execute and maintain a Government approved Management Plan (MP) to execute all tasks within this PWS. The Contractor shall organize and provide a team of qualified personnel in all functional disciplines to fully support all requirements of this PWS during the contract.

The organizational chart embedded within the MP shall show all personnel identified as Key Personnel, the job title and responsibilities, email address, telephone number and extension, and physical location where they perform work on this contract. The MP will include Contractor’s procedures to change key personnel to include Government confirmation of qualifications. Key personnel and their alternates are defined by the Government as:

Program Manager Configuration/Data Management Specialist TSSC Director Contracting Manager Senior Systems Engineer Lead Computer Programmer Security Manager System Network Administrator CLS Site Managers Information System Security Officer

Concurrency Engineer

Each site shall have an independent CLS manager who will function as the site manager.

For Contractor position descriptions and qualifications, reference the definitions provided in Section J, Attachment 3, Price Matrix. The Contractor shall provide certification, training and qualification documents for all key personnel and their alternates when requested by the

Government. The Contractor shall notify the applicable Contracting Officer’s Representative (COR) and the Program Office of key personnel changes within 7 calendar days.

The MP shall include the process for acknowledging Government inquiries and responding to these inquiries.

After initial Government approval of the MP, the Contractor shall obtain Government approval prior to making any change to the MP.

o Contract Data Requirements List (CDRL) A019-Management Plan (MP)

(DI-MGMT-80004A)

2.1.2 Integrated Master Plan and Integrated Master Schedule

The Contractor shall create and maintain an overall B-52 TS Integrated Master Plan (IMP) to execute all tasks within this PWS, and update as needed.

The Contractor shall create and maintain an overall B-52 TS Integrated Master Schedule (IMS) to execute all tasks within this PWS. Any changes to contractual milestones within the IMS shall be made only with Program Office coordination and written approval of the Procuring Contracting Officer (PCO). The Contractor shall analyze the IMS for potential milestone and delivery delays or interruptions and notify the Government within 7 days of identifying the potential issue.

The IMP and IMS shall be correlated, and any IMP updates shall be submitted with the

IMS.

o CDRL A024 - Data Accession List (DI-MGMT-81453A/T) o CDRL A030 – Integrated Program Management Report (DI-MGMT- 81861/T)

2.1.3 Reporting

The Contractor shall report program status as defined below.

Financial Management Reporting and Tracking 2.1.3.1

The Contractor shall develop, operate and maintain a financial management tracking system. The Contractor shall provide access to supporting reports and documentation that augment the joint government/contractor system management capability. The contractor shall support the Government’s budgeting process by providing data insight into all expenditures and termination liability.

o CDRL A025 - Contract Funds Status Report (DI-MGMT-81468/T)

Cost/Schedule Control Systems Reporting 2.1.3.2

The Contractor shall implement and maintain an Earned Value Management System (EVMS) that incorporates cost/schedule variance reporting. The EVMS shall be used in the management of fixed-price incentive firm (FPIF) portions of this contract. The EVMS shall track program cost and schedule against established criteria and milestones. The Contractor shall comply with Defense Federal Acquisition Regulation Supplement (DFARS) 252.234-7001, Notice of Earned Value Management System (Apr 2008) and DFARS 252.234-7002, Earned Value Management System (May 2011).

o CDRL A030 – Integrated Program Management Report (DI-MGMT- 81861/T) o CDRL A023 - Contract Work Breakdown Structure (DI-MGMT-81334D)

Sustainment Cost Reporting 2.1.3.3

The contractor shall comply with DFARS 252.234-7003 NOTICE OF COST AND

SOFTWARE REPORTING SYSTEM (NOV 2010) AND DFARS 252.234-7004 COST AND

SOFTWARE DATA REPORTING SYSTEM (NOV 2010) and shall accomplish cost and software resources reporting in accordance with (IAW) DoD 5000.04-M-1. The contractor shall flow these requirements down to all subcontractors accomplishing $50M or more of total effort.

o CDRL A010 - Contract Sustainment Report (DI-FNCL-81831/T)

Contract Value Reporting 2.1.3.4

The Contractor shall report at least annually in Program Management Review minutes and as requested, the total contract labor value to date with a breakout of the Contractor’s percentage of value and all subcontractors’ percentage of value. The Contractor’s percentage shall exceed 50% of total contract labor value at the end of the contract period of performance.

o CDRL A003-Conference Minutes (DI-ADMN-81250A/T)

Contractor Manpower Reporting 2.1.3.5

The Contractor shall report all Contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract via the Contractor Manpower Reporting Application (CMRA) secure website. The Contractor is required to completely fill in all required data fields at http://www.ecmra.mil. Reporting inputs will be for labor executed during the period of performance for each Government Fiscal Year (FY), which runs 1 October through 30 September. While inputs may be reported any time during the FY, all data shall be reported no later than (NLT) 31 October of each calendar year. The Contractor can direct questions to the CMRA help desk.

Information from the secure website is considered to be proprietary in nature when the contract number and Contractor identity are associated with the direct labor hours and direct labor dollars. At no time will any data be released to the public with the Contractor name and contract number associated with the data.

Contractor Device Performance Report 2.1.3.6

The Contractor shall prepare a Contractor Device Performance Report (CDPR) for all on-call and/or on-site support to accomplish CLS and TSSC support tasks. The CDPR shall include, but not limited to:

Record and use actual ATD operational time (not scheduled time) when reporting ATD hours used, Include off-equipment repairs older than 60 calendar days with justification in delay of repair, and

Include Air Force Technical Order (AFTO) Form 781A discrepancies over 30 days o CDRL A012 - Contractor Device Performance Report (DI-ILSS-80191D/T)

50/50 Depot Reporting 2.1.3.7 o The Contractor shall report depot data in accordance with Title 10 United States Code Section 2466 (also known as the “50/50” law, as amended by the National Defense Authorization Acts of FY98).CDRL A026 - The 50/50 Requirement Report (DI-MGMT-81749A/T)

2.1.4 Applicable Documents

The Contractor shall utilize and comply with the documents referenced herein in performance of specific tasks under this PWS.

The Contractor shall identify and submit any substituted documents for approval to the PCO. Written approval must be obtained prior to use. If approved, substituted documents will become a part of this PWS.

A list of acronyms is included in PWS, Appendix 1, and a glossary of terms is included in PWS, Appendix 2.

2.1.5 General Services and Material

The Contractor shall provide all materials and services required to execute this contract, except for those items or services specifically stated to be Government furnished in this PWS.

Contractor shall establish and execute procurement processes to procure, replenish and maintain the required material and services.

2.1.6 Program Meetings, Reviews, Conferences, and Working Groups

The Contractor shall participate in all meetings, reviews (e.g., design reviews), conferences, and working groups, as required in support of this PWS. For Contractor-led events, participation shall require presentation of recommendations, risks, proposal of alternatives, chairing/co-chairing, and other tasks as necessary. The Contractor shall support web conferencing, teleconferencing, video teleconferencing, or face-to-face meetings when requested by the Government to execute all tasks within this PWS. The Contractor shall conduct all arrangements, scheduling, and administration services for meeting rooms to include audio- visual equipment, room rentals for Contractor-hosted meetings, and any associated “Government Only” meetings.

For all Government management meetings and reviews, the Contractor shall provide agendas and requested attendee lists for Government approval at least 10 business days in advance of the meeting, briefing charts and technical data at least 5 business days in advance of the meeting, and provide minutes (with captured action items) NLT 7 business days after the meeting completes. The Contractor shall track to closure all action items generated during program meetings and reviews.

The Contractor shall obtain approval for all travel from the PCO NLT 7 calendar days prior to departure dates. Required travel will be reimbursed by the Government under no profit cost-reimbursable Contract Line Item Numbers (CLINs).

o CDRL A002-Conference Agenda (DI-ADMN-81249A)

Post Award Conference 2.1.6.1

The Contractor shall coordinate and support a Post Award Conference Requirements Review within thirty (30) calendar days after contract award unless directed otherwise by the

PCO.

At this meeting, the Contractor shall review all contract documents and attachments with the Government and DCMA.

As a minimum, the following tasks shall be accomplished:

Baseline the contract effort to include awarded options Establish integrated product teams Establish common understanding of program requirements Baseline the IMS Establish Data Accession List (DAL) requirements PWS review CDRL review

Program Management Reviews 2.1.6.2

The Contractor shall host quarterly Program Management Reviews (PMR) to execute tasks within this PWS. The PMRs shall address overall program progress (cost, schedule, technical performance, and risk management) with special attention given to actual problems.

The reviews shall cover all modifications, new devices, and studies in progress; obsolescence and Diminishing Manufacturing Sources (DMS) issues; provide status on TSSC tasks and accomplishments, and an update on CLS activities.

PMR locations will be jointly determined by the Government and Contractor.

Program Weekly Integrated Product Team Meetings 2.1.6.3

The Contractor shall support Weekly Integrated Product Team (IPT) meetings via web conferencing, teleconferencing, or video teleconferencing. The Weekly IPT shall address overall program progress and issues. Briefing charts and meeting minutes shall only be required at the request of the Government.

2.1.7 Associate Contractor Agreements

As necessary, the Contractor shall enter into Associate Contractor Agreements (ACA) to meet the requirements of this contract. ACAs will be used for exchanging data; accessing and using third party software and equipment; receiving technical support; working interface issues, agreeing on equipment use and time, and contract transition tasks. The Contractor shall enter into ACAs in a timely manner to avoid delays in tasks related to this contract. The Contractor shall establish an ACA with the follow-on CLS Contractor at the end of the CLS performance period. As a minimum, the following areas shall be included or addressed in all ACAs:

Identification of data and information that will be exchanged between Contractors to facilitate performance of the contracts involved. Descriptive detail of the data shall be exchanged to ensure that all parties understand their mutual obligations.

Necessary equipment and materials to be provided by the associate Contractors in the performance of the installation, integration, assembly, checkout, and testing of modifications.

The facilities and locations that will be provided/shared by each Contractor to accommodate personnel assigned and provide integration and support services and assurance of adequate working areas.

The responsibilities of each party for identifying and correcting incompatibilities in the design of the training device interface relationships, which may inhibit the required performance of the training device.

Procedures for protection of proprietary data shall be included, as necessary.

All ACAs shall be submitted to the B-52 TS PCO once established.

o CDRL A024 - DAL (DI-MGMT-81453A)

2.1.8 Subcontractor Management

The Contractor shall ensure that the subcontractor(s)/vendor(s) data, designs, and deliverables meet all B-52 TS engineering and technical requirements and fulfill the requirements of this contract. The Contractor shall integrate subcontractor(s) tasks into program management and tracking systems. The Contractor shall ensure the requirements of this contract are consistently applied to all subcontracts. The Contractor shall invite Government personnel to attend all subcontractor reviews and other problem solving reviews as observers. All DD-254s issued to subcontractors shall be submitted to the Defense Contract Management Agency (DCMA) and the B-52 TS program office.

2.1.9 Risk Management Plan

The Contractor shall develop, implement, and maintain a comprehensive risk management plan to execute all tasks within this PWS. The resulting risk program shall apply to all aspects of the B-52 TS. Risk Management shall include the identification of risks, the assessment of risks and their impacts, prioritization, mitigation and control plans, tracking, monitoring, and reporting. Risk processes shall also include development of recovery plans in the event risks are realized. The Government shall be notified of all identified risk(s) that could impact overall contract support performance, device and systems performance, schedules, availability or other key program milestones and activities. The risk management plan shall be thoroughly integrated and executed through the systems engineering processes and incorporated into the Systems Engineering Management Plan (SEMP).

o CDRL A042--System Engineering Management Plan (SEMP) (DI-SESS- 81785)

2.1.10 System Security

The Contractor shall develop and maintain an overall program System Security Plan (SSP) and any specific Site Security Plan addendums IAW the Information Assurance (IA) Platform Information Technology (PIT) Guidebook. The Contractor shall ensure SSP measures, designs (to include facilities and local networking connections), analyses, and controls support the operation and maintenance of ATD components at the TOP SECRET level and below. The WSTs and applicable supporting systems will require a TOP SECRET clearance level for certain training events. These training events will not be broadcast on the DMO network. The Contractor shall establish procedures for handling, storage, and processing of up to TOP SECRET information and facility security for the WST buildings located at Barkdale AFB and Minot AFB. The Contractor shall use established procedures to transition between SECRET and TOP SECRET security levels as requested by the Government at no additional cost. Applicable personnel supporting this effort at Government facilities shall require a valid TOP SECRET clearance.

Note: If there is conflict between the DoD Contract Security Classification Specification (DD Form 254) and this PWS, the DD Form 254 takes precedence. If a conflict is found, the Contractor shall immediately contact the PCO.

The Contractor shall develop, maintain, and implement all procedures for cryptographic keying material loading, as directed by the Government.

The Contractor shall provide a separate system for classified data management.

Management of classified/sensitive material/equipment shall be handled, transported, transmitted and protected IAW the National Industrial Security Operating Manual (NISPOM), DoD 5220.22- M and the DD Form 254.

Acquisition Systems Protection 2.1.10.1

The Contractor shall ensure security program requirements are integrated into all program areas of this contract as required by:

Department of Defense Directive (DoDD) 5000.01 Department of Defense Instruction (DoDI) 5000.02 DoDI 5200.39

The Contractor shall establish, implement and maintain these requirements IAW the provisions of Department of Defense Manual (DoDM) 5200.01, Volumes 1-4.

Cybersecurity 2.1.10.2

The Contractor shall support the cybersecurity guidance to ensure compliance with:

DoDI 8500.01 DoDI 8510.01 Air Force Instruction (AFI) 33-200

AFI 33-210

The TSSC shall provide qualified personnel IAW AFI 33-210 and AFI 33-200, which includes DOD 8570.01-M, to serve as site Information System Security Officers (ISSO). The ISSOs shall perform the comprehensive evaluation of all aspects of the security features of the Cybersecurity Program, and to ensure that site implementation meets established security requirements. The Contractor shall report system findings/vulnerabilities in writing to the TSSC

COR.

The Contractor shall support certification and accreditation of the system and maintain the information assurance posture of an accredited system. The Contractor shall incorporate cybersecurity requirement into all B-52 ATD configuration items.

For modifications to the training system, the Contractor shall design into the system the best practices of cybersecurity which include confidentiality, integrity, availability, authentication, and non-repudiation. For any changes or upgrades to the system baseline (hardware and software), the Contractor shall request to the Government Program Information System Security Manager for approval of impacts to the security posture.

Platform Information Technology 2.1.10.3

All B-52 ATDs shall be considered PIT as designated by the Air Force Aircraft Cybersecurity Authorizing Official. The Contractor shall produce and maintain all PIT Determination Packages IAW the IA PIT Guidebook.

Certification & Accreditation 2.1.10.4

The Contractor shall produce, document, process and maintain Certification & Accreditation (C&A) packages IAW the Air Force Life Cycle Management Center System Engineering Process and the IA PIT Guidebook.

The Contractor shall address cybersecurity for the complete system including both military and commercial systems.

The Contractor shall develop and document the security process or procedures to meet all applicable security controls.

The Contractor shall identify and document the applicability of the cybersecurity controls from NIST SP 800-53 using Committee on National Security Systems (CNSS) Instruction No.

1253 for the system, the controls compliance and technical measures recommended to meet or mitigate non-compliant controls.

The Contractor shall use the systems engineering process to incorporate the applicable security controls into the requirements, design, and integration and testing processes.

The C&A packages shall include supporting documentation for, but not be limited to:

security requirements security requirement Verification & Validation sensitivity of the data being processed identification of the system threats and vulnerabilities project likelihood of attack and exploitation identification of existing and planned countermeasures all external platform connections

These supporting documents shall be to the level of detail so as to support obtaining appropriate Authority to Test, Connect, or Operate to meet program and integration timelines.

The Contractor shall route these packages through the program office for Government approval.

Remanence Security 2.1.10.5

The Contractor shall ensure that data from classified ATDs is properly declassified IAW DoDM 5200.01, Vol 1 and AFI 31 401 and properly sanitized of all classified data IAW AFMAN 33-282, before removing said data from the classified facility.

Supply Chain Risk Management 2.1.10.6

The Contractor shall develop a Supply Chain Risk Management (SCRM) plan that implements as a minimum the elements of control SA-12 of National Institute of Standards and Technology (NIST) Special Publication 800-53.

Critical elements, as defined by the Criticality Analysis results within the B-52 TS Program Protection Plan, should be judged for their Security Category (SC) in accordance with Federal Information Processing Standards Publication 199. Those elements deemed high risk shall form the basis for the SCRM plan, but the plan should encompass any element that is at risk of supply chain problems.

The Contractor shall alert the program office regarding any counterfeit parts discovered or issues pertaining to the software supply chain. The Contractor shall register in the Government-Industry Data Exchange Program (GIDEP) and submit a GIDEP usage report annually. The use of the Defense Micro Electronics Activity approved trusted foundries shall be utilized for procurement of Application Specific Integrated Circuits that are military specific IAW DoDI 5200.44.

As part of the SCRM plan, the Contractor shall develop and implement a Counterfeit Parts Plan (CPP) IAW International Organization for Standardization (ISO) 10005 to prevent the inclusion of counterfeit parts or parts imbedded with malicious logic into products intended for sale to the Government.

The Contractor shall use SAE AS5553, “Counterfeit Electronic Parts; Avoidance, Detection, Mitigation, and Disposition” as a guide in the development of the counterfeit parts section of the SCRM plan.

As part of the CPP process, the Contractor shall provide certificates of conformance and acquisition traceability for the Original Component Manufacturers (OCMs) and distributers (franchised and independent) in the supply chain.

Manufacturers certificates of conformance shall include, at the minimum, the manufacturer’s name and address, the manufacturer or buyer’s part number and dash number, the signature or stamp with title of seller's authorized personnel signing the certificate, and batch identification for the item(s) such as date codes, lot codes, serializations, or other batch identifications.

Acquisition traceability includes the name and location of all supply chain intermediaries from the part manufacturer to the direct source of the product.

These forms and documentation shall be delivered with the end item and each shipment.

o CDRL A035 – Scientific and Technical Reports (DI-MISC-80711A) o CDRL A037 – Counterfeit Prevention Plan – (DI-MISC-81832)

Architecture Analysis 2.1.10.7

The Contractor shall support an architecture analysis defining cybersecurity system boundaries and data flows, and support the implementation of security controls and countermeasures for the program.

o CDRL A029--Information Assurance (IA) Design Review Information Package

(DRIP) (DI-MGMT-81845)

Cybersecurity Risk Assessment 2.1.10.8

The Contractor shall support Cybersecurity Risk Assessments for the B-52 TS.

As a minimum, the Contractor shall address risk assessment guidance found in the IA PIT Guidebook and in DoD 5220.22-M for handling, storage, and processing of classified information.

o CDRL A029--Information Assurance (IA) Design Review Information Package

(DRIP) (DI-MGMT-81845)

o CDRL A032 – Security Vulnerability Analysis – (DI-MISC-80841/T)

System Security Testing 2.1.10.9

The Contractor shall conduct System Security testing, including system scans, for the B-52 TS IAW AFPAM63-113 and an approved Test Plan (TP). The TP shall include verification and validation methods for each applicable security control.

The Contractor shall report the results of testing for each applicable security control.

The Contractor shall identify all non-compliant security controls and recommended plans to bring the system into compliance.

The Contractor shall support any required Government conducted security testing including annual inspections to ensure Critical Program Information (CPI) is substantially protected as required by the Program Protection Plan.

The Contractor shall conduct annual System Cybersecurity reviews and testing for the program. The Contractor shall support Government conducted reaccreditation every three years, or as required.

o CDRL A028 – Information Assurance Test Plan(DI-MGMT-81844/T) o CDRL A039-- Test/Inspection Report (DI-NDTI-80809B)

System Security Working Group 2.1.10.10

The Contractor shall support the Government-led System Security Working Group for

B-52 TS.

Information Security 2.1.10.11

The Contractor shall comply with all security requirements as identified in the Department of Defense Contract Security Classification Specification (DD Form 254).

These requirements shall be executed IAW DoD 5220.22-M.

The Contractor shall protect classified information as identified in the current B-52H Weapon System Master Security Classification Guide.

Technology Control 2.1.10.12

The Contractor shall follow the protection standards and guidance described in DoD 5200.1-M, Chapter 5.

The Contractor shall distribute unclassified CPI (see DoDM 5200.01, Vol 1-4) IAW DoDI

2040.02. All such documents shall be properly marked IAW DoDI 5230.24.

Technical documents not subject to distribution are defined in DoDD 5230.25.

Operations Security 2.1.10.13

The Contractor shall apply Operations Security (OPSEC) principles and practices to reduce program vulnerability from successful adversary collection and exploitation of Critical Information. The Contractor shall participate/comply with the Base/Operating location’s OPSEC plans.

Communications Security 2.1.10.14

The Contractor shall comply with Communications Security (COMSEC) requirements IAW AFMAN 33-283 for all tasks within this PWS to include DMO interoperability support.

The Contractor shall train all employees having access to, or a requirement for, using COMSEC material in the proper way of handling and safeguarding such equipment.

The Contractor shall provide a site COMSEC Responsible Officer, as required, and acquire and maintain COMSEC accounts at each aircrew training site for the management and support of secure communications and key/combination controls.

Emissions Security 2.1.10.15

The Contractor shall support Emissions Security (EMSEC) inspections by the base EMSEC office IAW Air Force Systems Security Instruction (AFSSI) 7700, AFSSI 7702, and DoD 5220.22-M.

No classified information will be processed without an EMSEC Certification Inspection from the EMSEC Office.

Industrial Security 2.1.10.16

The Contractor shall comply with the requirements of DD Form 254, NISPOM, and AFI 31-601.

The Contractor shall appoint a security manager/specialist at each site who shall oversee site security requirements.

Personnel Security 2.1.10.17

The Contractor shall ensure the requirements for granting access to classified information are met, as defined in the following:

DD Form 254

DoD 5220.22-M

DoDM 5200.01 Vols 1-4

DoD 5200.2-R

AFI 31-401

AFI 31-501

All Contractor personnel shall obtain an Air Force security clearance to the SECRET level as a condition of employment. Contractor personnel who require access to TOP SECRET and have the need to know shall be required to obtain a security clearance of TOP SECRET to accomplish tasks for WST support. The Contractor shall maintain proper security clearances for its personnel.

All assigned Contractor personnel shall obtain the passes and long-term identification as required by the Government at each site. The Contractor shall establish procedures to return all passes and identification when personnel depart a site or separate from this contract.

Security Training 2.1.10.18

The Contractor shall ensure that each Contractor/subcontractor employee completes Program Protection awareness training; (a) prior to performing any contract work, and…

This is the start of the file's text. The full file is on GovTribe.

File details come from the government source that posted it. Updated .