Attachment_1_-_PWS.pdf

ATTACHMENT 1

Performance Work Statement

Range and Network Division

Systems Engineering and Integration

FA8806-14-R-0001

5 March 2015

Attachment 1

Table of Contents

1. INTRODUCTION

1.1 RN Organization

2. DEFINITIONS, APPLICABLE PUBLICATIONS AND DOCUMENTS

2.1 Action Verb Definitions

2.2 Other Definitions

2.3 Compliance and Reference Documents

2.4 Mandatory Compliance Documents

2.5 Reference Documents

3. PROGRAM MANAGEMENT

3.1 Contract Management

3.2 Transition of SE&I Effort

3.3 Reports

3.4 Contract Administration

4. INTEGRATION

4.1 General Integration

4.2 Out Year Plan

4.3 Spend Plan

4.4 Support Generation of RFP and Procurement Documentation for Projects

4.5 Facilitate RFP Activities

4.6 Integrated Master Schedule (IMS)

4.7 Integrate Between RN Projects

4.8 Integrate During Projects

5. SYSTEMS ENGINEERING PROCESSES

5.1 Manage SE Processes and Products

5.2 Execute SE Processes

5.3 Process Maturity Matrix

6. CDRL Information Appendix

7. LAAFB Security Requirements Appendix

8. Acronyms and Abbreviations Appendix

List of Tables

Table 1-1: Glossary of Action Verbs and Definitions

Table 1-2: Glossary of Definitions

Table 2-1: Mandatory Compliance Documents

Table 2-2: Reference Documents

Table 5-1: Reference Library Roles and Responsibilities

Table 5-2: Process Maturity Matrix

Table 6-1: CDRL Table

Table 8-1: Acronyms and Abbreviations

1. INTRODUCTION

The focus of this performance-based Systems Engineering & Integration (SE&I) contract is to integrate new systems and services into Range and Network Division (RN) programs, gain support for new and on-going efforts in all phases of the acquisition life cycle and standardize systems engineering processes across the three programs. Services acquired under this contract-ing action will support RN programs’ integration requirements by establishing relationships, processes, and other execution tools needed to overcome the technical, operational, and cultural challenges of operational acceptance. Furthermore, this contract will standardize SE&I capabilities across RN’s three separate and distinct program by bringing the individual systems engineering processes to acceptable levels of maturity and then making these processes common across RN programs.

1.1 RN Organization

RN, and its support organization, develop and sustain three diverse, independent programs, the

Air Force Satellite Control Network (AFSCN), the Launch and Test Range System (LTRS), and the Space Training Acquisition Office (STAO) with distinct, independent baselines, stakeholders, system functions, personnel, and sustainment and development contractors.

1.1.1 The AFSCN provides telemetry, tracking and control (TT&C) services by supplying a space communications infrastructure. The AFSCN consists of three segments:

Communications, Range, and Network Management. The Communications and

Range Segments together compose the communications infrastructure, consisting of

Operational Control Nodes (OCNs) and remote tracking stations (RTS). OCNs serve as nodes into which users connect their systems to access AFSCN services such as

TT&C. OCNs then route the data to and from RTSs using the Defense Information

Systems Network. The Network Management Segment, operated by 22 Space

Operations Squadron (SOPS) at the primary OCN at Schriever AFB in Colorado

Springs, accepts contact requests from users and creates a schedule based on availability of assets, possible radio frequency interference and conjunction assessment. The schedule is then published and electronically transmitted to all users and RTSs to coordinate operational use of AFSCN assets. 22 SOPS and RTS operators configure AFSCN equipment for space vehicle contacts. Data recording is among the many services that the AFSCN provides for its users from all branches of the Department of Defense.

1.1.2 The LTRS provides command and control, tracking, telemetry, communications and systems safety support for Department of Defense, civil, and commercial space launch operations. The LTRS systems are located at the Eastern Range (ER), headquartered at Patrick AFB in Florida, and at the Western Range (WR), headquartered at Vandenberg AFB in California. Sustainment activities are managed from Peterson AFB in Colorado Springs. The LTRS is composed of 11 subsystems, enabling the safe launch or test of spacelift vehicles and missiles. These 11 sub-systems are Command Destruct/Positive Control, Communications, Data Handling, Range Safety, Optics, Planning & Scheduling, Radar, Surveillance, Timing &

Sequencing, Telemetry, and Weather, operated by human-in-the-loop (HITL) systems. Note: The LTRS is a separate and distinct from launch operations’ facilities, pads, and equipment.

1.1.3 The STAO provides space systems operations training for all space portfolio programs regardless of location. STAO is responsible for the management of the

Standard Space Trainer (SST), Joint Space Training Federation (JSTF), and the

Distributed Mission Operations-Space (DMO-S) programs, as well as providing acquisition support to all programs in developing and sustaining space training systems. The STAO's customers include 21st, 30th, 45th, 50th and 460th Space

Wings, 14th Air Force, United States Strategic Command (USSTRATCOM), United

States Cyber Command (USCYBERCOM), U.S. Army, and U.S. Navy.

1.1.4 RN employs Government support organizations, (Federally Funded Research and

Development Center (FFRDC) and SETA), and sustainment and development contractor(s). In this PWS, the current and future contractor(s) doing business with the RN, developing products and services for RN are referred to as the “development and sustainment contractor(s)”. The RN SE&I contractor will interface with these development and sustainment contactor(s) in their SE&I role within RN. The RN

SE&I contractor will perform the work described in this PWS at locations to include

Los Angeles AFB, Patrick AFB, Vandenberg AFB, and Peterson AFB.

2. DEFINITIONS, APPLICABLE PUBLICATIONS AND DOCUMENTS

The definitions and Compliance and Reference Documents applicable to this PWS are listed in this section. Reference documents are intended to enhance understanding of the background, work requirements, and constraints applicable to performing the requirements of this PWS.

2.1 Action Verb Definitions

The following verbs are used throughout this PWS with the indicated definitions:

Table 2-1: Glossary of Action Verbs and Definitions

Verb Definition

Assess To research, examine, analyze, identify, review, evaluate, monitor, and audit the following areas (unless directed otherwise by the Government): safety, architecture, requirements, integration, schedule, risk, traceability, user impacts, operational impacts, IA/cybersecurity; and report the results.

Consolidate To collect, compile, merge, include, combine, incorporate, or enter data, deliverables, or inputs into a single input, database, risk, recommendation, assessment, or document.

Contribute to

To aid, guide, advise; to be actively involved in a task, activity, or process; to provide value-added technical, programmatic and/or process input.

Coordinate To partner, interface, synchronize, get agreement from, or work with the appropriate parties to accomplish the designated task.

Facilitate To schedule and conduct meeting sessions. To produce and make available the following for each session: agenda and preliminary presentation material(s) such as review documentation, briefing charts, and report; minutes; final presentation material(s) and any supplemental material(s) generated or resulting from each session; and list of action items with the current status of each item.

Generate To create, develop, or produce a document, process, procedure, or product.

Identify To discover, detect, or make known.

Implement To perform, accomplish, execute, apply, or carry out a recommendation, task, process, plan, or procedure.

Integrate To combine, bring together, reconcile, incorporate, and merge information into a larger whole. To resolve conflicts between multiple inputs, viewpoints, or perspectives.

Manage To maintain, implement, execute, support, review, and oversee plans, processes, or products. To establish, develop, or generate plans, processes and products when they do not already exist; for all existing plans, processes, and products, use the existing versions. To propose improvements to plans, processes, and products to increase efficiency and effectiveness.

Perform To complete, accomplish, or carry out.

Present To report, brief, communicate, address, deliver, or offer; to give information to someone in a Government approved manner (e.g. briefing, slides, email, comment matrix, etc.).

Provide To acquire, obtain, or develop a material resource, hardware, software, report or other deliverable and deliver it to the Government. This includes maintaining facilities, parking, administrative equipment (computers, office equipment and supplies), and computer network capability.

Recommend To research, analyze, and develop a position, potential alternatives, or courses of action (including justification) and present these to the Government.

Track To record, capture, collect, follow, update, and present status of data, schedules, or actions.

Transition To migrate, move, transfer, or convert from one state to another state.

Validate To confirm by examination, provisions of objective evidence, or testing that the particular requirements for a specific intended use are fulfilled; to determine whether the result accomplishes the intended goal and meets user needs; to determine whether necessary requirements have been flowed up and/or down completely.

Verify To confirm by examination, provisions of objective evidence, or testing that specified requirements have been fulfilled; to determine whether the defined process was followed and the requirements were satisfied; to determine whether requirements have been flowed up and/or down accurately.

Witness On site observation of a test event, and to report what happened with respect to the test.

2.2 Other Definitions

The following terms are used in this PWS with the indicated definitions:

Table 2-2: Glossary of Definitions

Term Definition

To-be

Architecture

The RN program to-be architectures are the architectures necessary to fulfill approved RN Program requirements, current requirements plus those requirements to be met by projects that are approved in the Future Years Defense

Program (FYDP).

Future

Architecture

RN future architectures involve fulfillment of requirements beyond the FYDP.

As-is

Architecture

RN as-is architectures involve the current baseline architecture and current requirements being executed.

Functional

Baseline

The functional requirements and functional architectures for RN programs. These consist of the operational requirements, system requirements and system architectures, and segment/subsystem requirements and architectures including functional interfaces, and the relationships between these requirements and architectures.

Allocated

Baseline

The configuration item requirements and architectures for RN programs and the traceability of these requirements and architectures from the functional baseline.

The allocated baseline for LTRS is managed by the sustainment contractor.

Technical

Baseline

For AFSCN and STAO programs, the term “technical baseline” encompasses both the functional and allocated baselines. For LTRS, the term “technical baseline” refers to the functional baseline only.

Strategic Relating to overall program/enterprise level vision and approach. Deals with system/segment/subsystem level requirements and above.

Tactical Specific projects and methods used to implement the vision at the detailed level.

Allocated level requirements or below.

2.3 Compliance and Reference Documents

2.3.1 The RN SE&I contractor shall perform the tasks of this PWS in accordance with

(IAW) the documents listed in section 2.4.

The RN SE&I contractor shall comply with compliance documents in their 2.3.1.1 entirety unless otherwise directed.

2.3.2 The RN SE&I contractor shall be guided by those documents listed in section 2.3 to the extent necessary to accomplish the SE&I tasks and requirements.

All other references can be found at:

Military Specifications, Standards, and Handbooks www.everyspec.com

Air Force Instructions and Manuals www.e-publishing.af.mil

Air Force Technical Orders http://www.tinker.af.mil/technicalorders/index.asp

Department of Defense Instructions www.dtic.mil/whs/directives/index.html

Industry Standards Available on-line with the appropriate organization

2.4 Mandatory Compliance Documents

Table 2-3: Mandatory Compliance Documents

Number Title Date

AFI 10-601 Capabilities-Based Requirements

Development

AFI 10-701 Operations Security (OPSEC) 8 June 2011

AFI 31-101 Integrated Defense (FOUO)

Supplement: The Air Force

Installation Security Program

8 October 2009 file://agoapps1/slcd/share/SLR/Space%20Launch%20Range%20Background/RN%20USC/PWS/Current%20Snapshot/www.everyspec.com file://agoapps1/slcd/share/SLR/Space%20Launch%20Range%20Background/RN%20USC/PWS/Current%20Snapshot/www.e-publishing.af.mil http://www.tinker.af.mil/technicalorders/index.asp file://agoapps1/slcd/share/SLR/Space%20Launch%20Range%20Background/RN%20USC/PWS/Current%20Snapshot/www.dtic.mil/whs/directives/index.html

Number Title Date

AFI 31-401 Information Security Program

Management

Incorporating Change 1, 19 August 2009

AFI 31-501 Personnel Security Program

Management

Incorporating through Change

2, 29 November 2012

AFI 31-601 Industrial Security Program

Management

29 June 2005

AFI 63-101/20-101 Acquisition/Logistics Integrated Life

Cycle Management

7 March 2013

Incorporating Change 1, 21 March 2014

AFI 63-138 Acquisition of Services May 2013

AFI 91-202

(Chapter 10-Space

Safety & 11-System

Safety)

The US Air Force Mishap Prevention

Program

Incorporating Change 1, 20 March 2012, Air Force

Space Command Supplement, 26 June 2012

AFI 91-204,

AFSPCSUP 1

Safety Investigations and Reports February 2014

AFI 99-103 Capabilities-Based Test and

Evaluation

16 October 2013

AFMAN 14-304 The Security, Use and Dissemination of Sensitive Compartmented

Information (FOUO)

1 May 1999

AFMAN 91-222 Safety Program (Space/Systems

Safety)

April 2012

Air Force Space Command

Supplement 2 January 2007

Safety Space Safety Investiga-tions and Reports, Certified current 24 January 2013

AFMAN 91-224 Safety Ground Safety Investigations

And Reports

1 August 2004

AF PAM 63-128

(Chapter 12)

Guide To Acquisition And

Sustainment Life Cycle Management

AFPAM 63-1701 Program Protection Planning 27 March 2003

AFPD 31-6 Industrial Security Incorporating Change 1, 13 March 2007

AFPD 63-17 Technology and Acquisition Systems

Security Program Protection

26 November 2001

Number Title Date

AFSCN DM OI 61-1 Satellite Control and Network Systems

Group Data Management (DM)

Operating Instructions

11 April 2011

AFSCN ITT Charter AFSCN Integrated Test Team Charter 25 September 2009

AFSCN IUID

Implementation Plan

AFSCN Item Unique Identification

Implementation Plan Version 1

20 February 2008

AFSCN LCSP

(Draft)

Draft Life Cycle Sustainment Plan

(LCSP) for the Air Force Satellite

Control Network (AFSCN)

2 May 2011

AFSCN Mission

Assurance

Satellite and Network Systems

Division (SN) Mission Assurance

17 October 2011

AFSCN OSS&E AFSCN Operational Safety, Suitability and Effectiveness (OSS&E) Assurance

Plan

13 April 2007

AFSCN PESHE Programmatic Environment, Safety, and Occupational Health Evaluation for the Satellite Control and Network

Systems Group

25 February 2010

AFSCN PPP AFSCN Program Protection Plan

(PPP)

26 September 2006

AFSCN Risk OI AFSCN Risk Management Operating

Instruction (OI)

TBD

AFSCN RM OI AFSCN RM OI TBD

AFSCN SEP AFSCN Systems Engineering Plan July 2008

AFSCN TEMP Air Force Satellite Control Network

Test and Evaluation Master Plan

11 July 2011

CNSSI 1253 Security Categorization and Control

Selection for National Security

Systems

March 2014

DMO-S LCSP DMO-S Life Cycle Sustainment Plan 16 June 2012

DoD 5200.1-M Acquisition Systems Protection

Program

March 1994

DoD 5200.2-R Personnel Security Program Administrative Reissuance incorporating through Change

3, 23 February 1996

DoD 5220.22M National Industrial Security Program

Operating Manual (NISPOM)

Including Change 1, 31 July 1997

Number Title Date

DoD 8570.01-M IA Workforce Improvement Program Incorporating Change 3, 24 January 2012

DoDAF v2.02 DoD Architecture Framework, Volumes I, II, and III

August 2010

DoDD 5205.02 DoD OPSEC Program 20 June 2012

DoDD 8500.01E Information Assurance 23 April 2007

DoDI 5200.39 Critical Program Information (CPI)

Protection within the Department of

Defense

Including Change 1, 28 December 2010

DoDI 5200.44 Protection of Mission Critical

Functions to Achieve Trusted Systems and Networks

5 November 2012

DoDI 8500.01 Cybersecurity 14 March 2014

DoDI 8500.2 IA Implementation 6 February 2003

DoDI 8510.01 DoD IA Certification and

Accreditation Process (DIACAP)

28 November 2007

DoDI 8510.01 Risk Management Framework (RMF) for DoD Information Technology (IT)

12 March 2014

DoDI 8582.01 Security of Unclassified DoD

Information on Non-DoD Information

Systems

6 June 2012

ICD 503 Intelligence Community Information

Technology Systems Security Risk

Management, Certification and

Accreditation

15 September 2008

LTRS ARB2 OI 63-4 Acquisition Architecture Review

Board (ARB2) OI

October 2008 (DRAFT)

LTRS CC OI 63-3 Acquisition Configuration Control

(CC) OI

October 2008 (DRAFT)

LTRS CM OI 63-1 Acquisition Configuration

Management (CM) OI

October 2008 (DRAFT)

LTRS CM/DM Plan

Acquisition Configuration/Data

Management (C/DM)

October 2008 (DRAFT)

LTRS DM OI 63-2 Acquisition Data Management (DM)

OI

October 2008 (DRAFT)

Number Title Date

LTRS IRRB OI 63-5 Acquisition Installation Readiness

Review Board (IRRB) OI

October 2008 (DRAFT)

LTRS IUID

Implementation Plan

LTRS Item Unique Identification

(IUID) Implementation Plan

March 2008

LTRS Risk OI LTRS Risk Management Operating

Instruction (OI)

TBD

LTRS RITT Charter Range Integrated Test Team (RITT)

Charter for the Launch and Test Range

Systems (LTRS)

19 March 2004

LTRS RM OI LTRS RM Operating Instructions (OI) TBD

LTRS RRB OI 63-6 Acquisition Readiness Review Board

(RRB) OI

October 2008 (DRAFT)

LTRS SEP LTRS Systems Engineering Plan

(SEP)

14 August 2008

LTRS SSMP System Safety Management Plan

(SSMP)

March 2014

LTRS TEMP LTRS Test and Evaluation

Management Plan (TEMP)

15 December 2006

Memorandum Principal Deputy Under Secretary of

Defense Memorandum: Document

Streamlining - Program Protection

Plan (PPP)

18 July 2011

MIL-STD-196e Joint Electronics Type Designation

System

17 February 1998

MIL-STD-881C Work Breakdown Structures for

Defense Material Items

3 October 2011

MIL-STD-882E System Safety Program Requirements May 2012

PESHE Programmatic Environment Safety and

Occupational Health Evaluation

(PESHE)

April 2008

SMC-S-001 Systems Engineering Requirements and Products

July 2013

SMC-S-002 Configuration Management 13 June 2008

SMC-S-012 Software Development for Space

Systems

13 June 2008

Number Title Date

SMC-S-019 Program and Subcontractor

Management

13 June 2008

SMC-S-021 Technical Reviews And Audits For

Systems, Equipment And Computer

Software

15 September 2009

SMC-T-004 Air Force Space Command (AFSPC)

Space and Missile Systems Center -

Tailoring Instructions for MIL-STD-

882E

August 2013

SMC-S-005 Tailoring of Risk Management

Requirements in SMC-S-001(2013)

August 2013

SMCI 63-1205 SMC System Safety Program 28 June 2011

SMCI 63-1207 Programmatic Environment, Safety &

Occupational Health Evaluation

July 2013

SST CCB OI SST Configuration Control Board

(CCB) Operating Instruction (OI)

30 October 2012

T.O. 00-35D-54 USAF Deficiency Reporting, Investigation, and Resolution

1 May 2007

2.5 Reference Documents

Table 2-4: Reference Documents

Number Title Date

AFI 16-1002 Modeling and Simulation (M&S)

Support To Acquisition

1 June 2000

AFI 36-2251 Management of Air Force Training

Systems

5 June 2009

AFMAN 63-119 Certification of System Readiness for

Dedicated Operational Testing

14 July 2010

AFSCN CONCEPT

OF OPERATIONS

(CONOPS)

Concept of Operations for the Satellite

Operations Mission

12 July 1997

AFSPC

LTRS/AFSCN

CONOPS

AF Space Command Launch and Test

Ranges Operating Concept

11 May 2004

AFSPCI 36-283 Space Training System Management 2 August 2004

AFSPCMAN 91-

Range Safety User Requirements

Manual

1 July 2004

Number Title Date

CJCSI6212.01F Net Ready Key Performance Parameter 21 March 2012

DISR 12-3.0 DoD Information Technology Standards

Registry

28 November 2012

Defense Acquisition

Guidebook (DAG)

Defense Acquisition Guidebook 29 July 2011

DAG TEMP Recommended Test and Evaluation

Master Plan (TEMP) format can be found in Defense Acquisition

Guidebook (DAG) Chapter 9, Section

9.6.2

9 October 2012

DoD 5000.61 DoD Modeling and Simulation (M&S)

Verification, Validation, and

Accreditation (VV&A)

9 December 2009

DoDD 2000.12 DoD Antiterrorism (AT) Program 1 March 2012

DoDD 5000.1 The Defense Acquisition System 12 May 2003

DoDI 38-1001 Department of Defense Net-Centric

Services Strategy

Strategy for a Net-Centric, Service

Oriented DoD Enterprise

March 2007

DoDI 5000.02 Operation of the Defense Acquisition

System

8 December 2008

DoDI 5000.02 Operation of the Defense Acquisition

System

25 November 2013

DS-2610-142-01 Department of Defense Intelligence

Information System (DoDIIS) Systems

Security Certification and Accreditation

Guide

April 2001

EWR 127-1 Eastern and Western Range Safety 31 December 1999

FAA-HF-001A Data Item Description: Human

Engineering Program Plan

1 June 2009

IMP & IMS

Preparation and Use

Guide

Integrated Master Plan and Integrated

Master Schedule Preparation and Use

Guide, Version 0.9

21 October 2005

LTRS ORD LTRS Operation Requirements

Document (ORD)

April 2003

LTRS SS (Rev K) LTRS System Specifications (Rev K) Final Draft

LTRS SSS LTRS Subsystem Specifications In Revision

Number Title Date

Mgt Guide for

Space Acq

Mgt Guide for Space Acq 29 April 2005

MIL-HDBK- 61A Configuration Management Guidance 7 February 2001

MIL-PRF-29612B Performance Specification, Training

Data Products

31 August 2001

MIL-PRF-49506 Logistics Management Information, Notice 2

31 March 2011

MIL-STD-1542B EMC Grounding Requirements for

Space System Facilities

MIL-STD-461F Electromagnetic Emissions and

Susceptibility, Requirements for the

Control of Electromagnetic Interference

MIL-HDBK-470A Designing and Developing

Maintainable Products and Systems

May 2012

NIST SP 800-30 Guide for Conducting Risk

Assessments, Rev 1

September 2012

NIST SP 800-37 Guide for Applying the Risk

Management Framework to Federal

Information Systems: A Security Life

Cycle Approach, Rev 1

February 2010

NIST SP 800-53 Security and Privacy Controls for

Federal Information Systems and

Organizations

April 2013

PMD 2880(8)/

PE#35182F

Program Management Directive for

Launch and Test Range System (LTRS)

Program

19 November 2008

PSMP Product Support Management Plan

(PSMP)

1 March 2002

Range

Instrumentation

Handbook (ER)

Range Instrumentation Handbook January 2005 (ER)

Range

Instrumentation

Handbook (WR)

Range Instrumentation Handbook January 2008 (WR)

SAE AS 9100 Rev

C

Quality Management Systems –

Requirements for Aviation, Space and

Defense Organizations

15 January 2009

Number Title Date

SMC IBR

Handbook

Space and Missile Systems Center

(SMC) Integrated Baseline Review

(IBR) Team Handbook

1 May 1998

SMC Risk Management Guide 7 December 2011

SMC-G-002 Reliability & Maintainability Program 10 June 2009

SST ORD Standard Space Trainer Operational

Requirements Document

21 July 2008

SST LCSP Life Cycle Sustainment Plan (LCSP)

Version 2.5 SST Architecture

13 January 2011

SST SORAP SST Source of Repair Assignment

Process

23 March 2010

TOR-2005(8583)-3,

Rev. B

Systems Engineering Requirements and

Products

15 April 2010

TOR-2012(8506)-5

DRAFT

Exploding 800-53 Revision 3: An

Analysis of NIST SP 800-53 Revision 3 as completed by CNSSI 1253

31 July 2012

3. PROGRAM MANAGEMENT

Note: The notional number of occurrences for PWS tasks as found in brackets in this section is provided for guidance only to assist in your proposal preparation. These notations will be removed from the PWS in the awarded contract.

3.1 Contract Management

The RN SE&I contractor shall perform all contract management activities necessary to accomplish the work, to include the following subparagraphs.

IAW: N/A

Document results in: N/A

3.1.1 Management Plan

The RN SE&I contractor shall generate a Management Plan. 3.1.1.1

IAW: SMC-S-019, RN Program SE Plans and Operating Instructions (OIs)

Document results in: Program/Contract Management Plan including

Subcontractor Management (Contract Data Requirements List (CDRL)

P006)

3.1.1.1.1 The RN SE&I contractor shall manage a Subcontractor Management

Plan, which shall be included as an Appendix in the Management Plan.

IAW: SMC-S-019

Document results in: Program/Contract Management Plan including

Subcontractor Management (CDRL P006)

3.1.1.1.2 The RN SE&I contractor shall manage a Transition Plan.

IAW: SMC-S-019

Document results in: Transition Plan (CDRL P006)

The RN SE&I contractor shall manage the Management Plan and provide 3.1.1.2 updates to reflect any significant changes in priorities, resource availability, taskings, or execution.

IAW: SE&I Management Plan

Document results in: Program/Contract Management Plan (CDRL P006)

3.1.2 Management Reviews

The RN SE&I contractor shall facilitate SE&I contract management reviews 3.1.2.1 with RN, as required. [quarterly]

IAW: SE&I Management Plan

Document results in: Agenda, Minutes, Presentation, Action Items, Data

Accession List (DAL) Management Review Presentation Materials, DAL

Management Report

The RN SE&I contractor shall facilitate Integrated Baseline Reviews 3.1.2.2

(IBRs), as required. [yearly]

IAW: SE&I Management Plan

Document results in: N/A

3.1.3 Integrated Master Plan (IMP) and SE&I Integrated Master Schedule (IMS)

The RN SE&I contractor shall manage and provide an IMP for all key 3.1.3.1 activities and events necessary to accomplish all PWS tasks.

IAW: SE&I Management Plan

Document results in: IMP (CDRL P006)

The RN SE&I contractor shall manage an SE&I IMS that describes the 3.1.3.2 time-phased work necessary for the RN SE&I contractor to accomplish all

PWS tasks, including the RN SE&I contractor activity and RN program events, significant accomplishments, accomplishment criteria, and detailed tasks.

IAW: SE&I Management Plan

Document results in: SE&I IMS (CDRL P012)

3.1.4 The RN SE&I contractor personnel and their subcontractors shall identify themselves as contractors or subcontractors during meetings, telephone conversations, in electronic messages, or correspondence related to this contract.

IAW: N/A

Document results in: N/A

3.1.5 The RN SE&I contractor when at contractor-occupied facilities (on AFSPC or other

Government installations) such as offices, separate rooms, or cubicles shall be clearly identified with contractor supplied signs, name plates or other identification, showing that these are work areas for contractor or subcontractor personnel.

IAW: N/A

Document results in: N/A

3.2 Transition of SE&I Effort

3.2.1 The RN SE&I contractor shall contribute to organizational, system, process and information knowledge transfer from the Government program office team

(Government, FFRDC and SETA members), to include overlap with existing SE&I contractor. [60 days expected]

IAW: RN SE&I contractor Transition Plan

Document results in: N/A

3.2.2 The RN SE&I contractor shall coordinate organizational, system and process knowledge and information transfer from the RN SE&I contractor to any new SE&I contractors or Government entities.

IAW: N/A

Document results in: N/A

3.2.3 The RN SE&I contractor shall implement transition activities to minimize impact to

RN program schedules, cost, performance, and risk.

IAW: RN SE&I contractor Transition Plan

Document results in: Management Plan (CDRL P006)

3.2.4 The RN SE&I contractor shall present how PWS tasks will be executed in a kickoff meeting.

IAW: RN SE&I contractor Transition Plan

Document results in: Management Plan (CDRL P006), Agenda, Minutes, Presentation, Action Items

3.2.5 Transition Program Technical Baselines

The RN SE&I contractor shall transition the RN program Configuration 3.2.5.1

Control Board (CCB)-controlled technical baseline from the current LTRS

SE&I contractor and the RN sustainment and development contractors to the

RN SE&I contractor.

IAW: SE&I Transition Plan

Document results in: Notice of Program Baseline Transition Briefing, CCB-controlled Technical Baseline (Product)

3.2.5.1.1 The RN SE&I contractor shall verify and validate that the traceability from the functional baseline to the allocated baseline is correct for all

CCB-controlled requirements.

IAW: RN Program Systems engineering plans (SEPs), RN Program

Requirements Management (RM) Plans and RN Program RM OIs.

Document results in: Traceability Assessment (CDRL P011)

3.2.5.1.2 The RN SE&I contractor shall transition RN future technical requirements baselines from RN to the RN SE&I contractor.

IAW: RN Program SEPs, SE&I Transition Plan

Document results in: Requirements Management Tool

3.3 Reports

3.3.1 Contract Funds Status Report (CFSR)

The RN SE&I contractor shall generate a CFSR. 3.3.1.1

IAW: CDRL P004 instructions

Document results in: CFSR (CDRL P004)

The RN SE&I contractor shall generate a cost status report. 3.3.1.2

IAW: CDRL P044 instructions

Document results in: Cost Status Report (CDRL P044)

3.3.2 Contract Status Report (CSR)

The RN SE&I contractor shall generate a CSR. 3.3.2.1

IAW: SE&I Management Plan or SE&I IMP

Document results in: CSR (CDRL P001)

3.3.3 Data Accession List

The contractor shall document and maintain a DAL that includes all data 3.3.3.1 produced under RN SE&I but not otherwise required for delivery.

IAW: CDRL P034 instructions

Document results in: DAL (CDRL P034)

3.4 Contract Administration

The RN SE&I contractor shall perform all contract administration activities necessary to accomplish the work, to include the following subparagraphs.

IAW: N/A

3.4.1 Training and Qualifications

The RN SE&I contractor shall provide personnel who comply with the IA/ 3.4.1.1 cybersecurity workforce certification requirements in DoD 8570.01-M - IA

Workforce Improvement Program.

IAW: DoD 8570.01-M

Document results in: Proof of IA/cybersecurity certification

The RN SE&I contractor shall provide personnel with a minimum of 3.4.1.2

SECRET level clearances.

IAW: NISPOM

Document results in: N/A

3.4.2 Program Task Priority Meeting

The RN SE&I contractor shall facilitate and contribute to RN program SE&I 3.4.2.1 integrated team meetings with the Government, to include FFRDCs and

SETAs, to align SE&I efforts and priorities. [monthly]

IAW: RN Program SEPs, SE&I Management Plan

Document results in: Prioritized task list

3.4.3 Supplies and Equipment

The RN SE&I contractor shall provide all supplies and equipment required 3.4.3.1 for this contract.

IAW: N/A

Document results in: N/A

3.4.4 Contract Accounting

The RN SE&I contractor shall manage the Contract Work Breakdown 3.4.4.1

Structure (CWBS).

IAW: MIL-STD-881C

Document results in: Update to CWBS, Attachment 2.

3.4.5 RN SE&I Contractor Facilities

The RN SE&I contractor shall provide office space facilities for any 3.4.5.1 additional RN SE&I contractor personnel, within 30 minutes of the four

Government team duty locations listed above, to coordinate with the

Government in real-time through the proximity-of-facilities, teleconfer-ences, video teleconferences, or on-line computer collaboration tools.

IAW: N/A

Document results in: N/A

3.4.6 Interface Protocol

The RN SE&I contractor shall cooperate with FFRDC contractors, support 3.4.6.1 contractors, prime contractors and their subcontractors to include, but not limited to, the following:

a. Providing appropriate access to technical information and research

Exhibit A (CDRLs)

b. Discussing technical matters relating to the RN SE&I effort

c. Providing access to contractor facilities used in the performance of this contract

d. Allowing observation of technical activities by appropriate technical personnel

IAW: N/A

Document results in: N/A

The RN SE&I contractor shall agree to include in all subcontracts a clause 3.4.6.2 requiring compliance by subcontractor and succeeding levels of subcontractors with the response and access and disclosure provisions as defined in PWS 3.4.6.1 above.

IAW: N/A

Document results in: N/A

Other contractor personnel are not authorized to direct the RN SE&I 3.4.6.3 contractor in any manner. The contractor agrees to accept technical direction as follows:

a. Technical direction under this contract will be given to the contractor solely by SMC.

b. Whenever it becomes necessary to modify the contract and redirect the effort, a change order signed by the Contracting Officer or a

Supplemental Agreement signed by both the Contracting Officer and the contractor will be issued.

IAW: N/A

Document results in: N/A

The RN SE&I contractor shall establish and maintain Associated 3.4.6.4

Contractor, non-disclosure, and other agreements that may be required in support of contract activities.

IAW: N/A

Document results in: Agreement document

3.4.7 RN SE&I Manning

The RN SE&I contractor shall maintain key personnel with the minimum 3.4.7.1 requirements identified in the subparagraphs below.

IAW: N/A

Document results in: N/A

3.4.7.1.1 The RN SE&I contractor shall staff a Program Manager with at least 10 years of experience successfully managing relevant program SE&I efforts for DoD, other Government Agency or commercial programs or projects of similar scope and complexity as the proposed effort.

3.4.7.1.2 The RN SE&I contractor shall staff Chief Architects/Engineers with at least 10 years of experience in leading the primary engineering efforts of appropriately sized (similar to at least Acquisition Category III level) ground system software, hardware, and training programs. In addition, at least three years of experience supporting the overall engineering integration of relevant SE&I efforts for DoD, other Government

Agency or commercial programs or projects of similar scope and complexity as the proposed effort. AFSCN and LTRS Chief

Architects/Engineers shall have extensive domain expertise in their respective areas.

3.4.7.1.3 The RN SE&I contractor shall staff a Configuration/Data Management

Lead with at least five years of experience in organizing, scoping, technically assessing, and proposing potential resolutions to maintain the technical program or project baseline of an appropriately sized

(similar to at least Acquisition Category III level) ground system software, hardware, and training programs. In addition, at least three years of experience leading the overall configuration management role of relevant SE&I efforts for DoD, other Government Agency or commercial programs or projects of similar scope and complexity as the proposed effort. At least five years of experience in organizing and maintaining the technical information library and performing the data management role to support the program or project of an appropriately sized (similar to at least Acquisition Category III level) ground system software and hardware program.

3.4.7.1.4 The RN SE&I contractor shall staff a Risk Management Lead with at least five years of experience in organizing, compiling and assessing the program or project risks of appropriately sized (similar to at least

Acquisition Category III level) ground system software and hardware programs. In addition, at least three years of experience leading the overall risk role of relevant SE&I efforts for DoD, other Government

Agency or commercial programs or projects of similar scope and complexity as the proposed effort.

3.4.7.1.5 The RN SE&I contractor shall staff a Requirements Management Lead with at least five years of experience in defining, decomposing, and validating and verifying system performance against technical, operational, and interface requirements of an appropriately sized

(similar to at least Acquisition Category III level) ground system software and hardware programs. In addition, at least three years of experience providing interface control for DoD, other Government

Agency or commercial programs or projects of similar scope and complexity as the proposed effort.

3.4.7.1.6 The RN SE&I contractor shall staff a Test Lead with at least five years of experience in planning, organizing, reporting, and resolving issues on technical program of appropriately sized (similar to at least

Acquisition Category III level) ground system software or hardware programs. In addition, at least three years of experience leading the overall role of relevant SE&I efforts for DoD, other Government

Agency or commercial programs or projects of similar scope and complexity as the proposed effort.

3.4.7.1.7 The RN SE&I contractor shall staff an IA/cybersecurity/Security Lead with at least five years in planning, documenting, and resolving security and IA/cybersecurity issues on a technical program of appropriately sized (similar to at least Acquisition Category III level) ground system software or hardware programs. In addition, at least three years of experience leading the overall role of relevant SE&I efforts for DoD, other Government Agency or commercial programs or projects of similar scope and complexity as the proposed effort with CISSP and

Security+ certification.

The RN SE&I contractor shall maintain adequate staffing and experience 3.4.7.2 skill mix to accomplish the work in the PWS.

IAW: N/A

4. INTEGRATION

Note: The notional number of occurrences for PWS tasks as found in brackets in this section is provided for guidance only to assist in your proposal preparation. These notations will be removed from the PWS in the awarded contract.

4.1 General Integration

The RN SE&I contractor shall perform all integration activities necessary to accomplish the work, to include the following subparagraphs.

IAW: N/A

Document results in: N/A

4.1.1 The RN SE&I contractor shall coordinate with stakeholders to ensure a common understanding of RN program acquisition and sustainment plans.

IAW: RN Program SEPs, RN Program Integration OIs

Document results in: Coordinated comment matrix on Architecture Roadmaps

4.1.2 The RN SE&I contractor shall ensure that all integration tasks for each RN program are tracked and completed through all lifecycle phases and present the results.

IAW: RN Program Integration OIs

Document results in: Integration Presentation

The RN SE&I contractor shall identify, track and present integration issues, 4.1.2.1 and coordinate with stakeholders to closure in a timely manner.

IAW: RN Program Integration OIs

Document results in: Integration Issues Presentation

4.1.3 The SE&I shall perform integration and coordination actions necessary to create and complete projects and present the results.

IAW: RN Program Integration OIs

Document results in: Integration Presentation

4.2 Out Year Plan

4.2.1 The RN SE&I contractor shall contribute to the planning process to determine what projects need to be accomplished in the future.

IAW: RN Program Integration OIs

Document results in: N/A

The RN SE&I contractor shall recommend a prioritization of technical 4.2.1.1 baseline changes for each RN program.

IAW: Integration Plan, RN Program Integration OIs

Document results in: Presentation, Technical Inputs

The RN SE&I contractor shall manage roadmaps for to-be technical 4.2.1.2 baselines at the system and segment/subsystem level that extend out seven years through the FYDP that include fiscal plans, life cycle costs, and schedules for Government review. [average 25 per year]

IAW: RN Program Integration OIs

Document results in: Roadmaps (CDRL P011)

4.2.2 The RN SE&I contractor shall facilitate integration working groups to finalize out year plans with all stakeholders for each RN program.

IAW: RN Program Integration OIs

Document results in: Agenda, Minutes, Presentation, Action Items

4.3 Spend Plan

4.3.1 The RN SE&I contractor shall contribute to the prioritization of projects that are two years out for each RN program and present results.

IAW: RN Program Integration OIs

Document results in: Spend Plan Inputs Presentation

4.3.2 The RN SE&I contractor shall coordinate the RN program spend plans with stakeholders for concurrence and present results.

IAW: RN Program Integration OIs

Document results in: Spend Plan Coordination Briefing

4.4 Support Generation of RFP and Procurement Documentation for Projects

4.4.1 The RN SE&I contractor shall facilitate and participate in the Project Planning

Working Group.

IAW: RN Program SEPs, RN Program OIs

Document results in: RFP inputs for project requirements, architecture, CONOPS, and Sections L&M

4.4.2 The RN SE&I contractor shall generate draft technical documentation in support of

RFPs for sustainment and development contractor efforts and modification projects.

This documentation may include, but not limited to, the following:

a. Statement of Work (SOW)/Performance Work Statement (PWS)

b. Sections L & M (instructions & criteria)

c. Work Breakdown Structure (WBS)

d. CLIN structure

e. CDRLs

f. Requirement documents

g. Interface documents

h. Employment Concept

i. Project architecture

[average 16 RFPs per year]

IAW: RN Program Integration Plans, RN Program Integration OIs, DoDAF 2.02

Document results in: Technical Input for RFP – SOW/PWS, L&M, CLINs, and

Exhibit A; Project Requirement Documents (CDRL P017); Interface Documents

(CDRL P018); Employment Concepts (CDRL P025); Project Architecture (CDRL

P036)

The RN SE&I contractor shall identify technical performance measures 4.4.2.1

(TPMs) for new RN projects, if applicable.

IAW: RN Program SEPs

Document results in: Technical Performance Measures (CDRL P011)

4.4.3 The RN SE&I contractor shall coordinate stakeholder reviews of RFP documentation, assist in responding to comments, and obtain concurrence or present issues for management decision.

IAW: RN Program Integration OIs

Document results in: Comment Resolution Matrices (CRMs) to RFP documents and revised RFP documents

The RN SE&I contractor shall contribute to the creation of additional 4.4.3.1 technical documents to resolve issues or gaps in the RFP baseline documentation.

IAW: RN Program Integration OIs

Document results in: RFP document inputs, Draft RFP document

4.4.4 The RN SE&I contractor shall generate bidder’s libraries. [average four bidder’s libraries per year]

IAW: RN Program Integration OIs, RN Program DM Plans, RN Program DM OIs

Document results in: Bidder’s Libraries

4.5 Facilitate RFP Activities

4.5.1 The RN SE&I contractor shall assist in generating and assessing Requests for

Information (RFIs). [average 16 per year]

IAW: RN Program Integration OIs

Document results in: RFI Inputs, RFI Assessments

4.5.2 The RN SE&I contractor shall facilitate and contribute to Industry Days.

IAW: RN Program Integration OIs

Document results in: Agenda, Minutes, Presentation, Action Items

4.5.3 The RN SE&I contractor shall assess proposals for projects on sustainment and development contracts.

IAW: Section M – Evaluation Criteria for each procurement

Document results in: Source selection tool and source selection team guidance

The RN SE&I contractor shall identify shortfalls in addressing project 4.5.3.1 requirements and constraints in proposals.

IAW: Source Selection Guidance and Plans

Document results in: Source selection tool and source selection team guidance

The RN SE&I contractor shall identify technical risks in proposals. 4.5.3.2

IAW: Source Selection Guidance and Plans

Document results in: Source selection tool and source selection team guidance

4.6 Integrated Master Schedule (IMS)

4.6.1 The SE&I contractor shall manage an IMS for each RN program that addresses all major project milestones and major events from sustainment and development projects, on a commercially-available scheduling system compatible with the

Government network environment.

IAW: SEPs

Document results in: Program IMS (CDRL P012)

4.6.2 The SE&I contractor shall manage a RN cross-program (LTRS, AFSCN, and STAO) enterprise schedule that tracks division level milestones and major events, on a commercially-available scheduling system compatible with Government network environment (such as Government NIPRNET).

IAW: SEPs

Document results in: Enterprise IMS (CDRL P012)

4.6.3 The RN SE&I contractor shall assess each project IMS and associated programmatic data to identify items to include the following:

a. Programmatic interfaces

b. Task interrelationships (giver-receiver relationships)

c. Deliverables

d. Primary and secondary critical paths

e. Programmed integration activities

IAW: RN Program SEPs, RN Program Integration OIs

Document results in: IMS (CDRL P012)

4.6.4 The RN SE&I contractor shall generate an Operational Capability Schedule for each

RN program.

IAW: RN Program SEPs, RN Program Integration OIs

Document results in: Operational Capability Schedule (CDRL P012)

4.6.5 The RN SE&I contractor shall generate an IA/cybersecurity IMS for all LTRS, AFSCN, and Space Trainer accreditation packages.

IAW: RN Program SEPs, RN Program Integration OIs

Document results in: IA/cybersecurity IMS (CDRL P012)

4.6.6 The RN SE&I contractor shall assess program/project IMS to identify program and project integration issues or impacts and recommend solutions, mitigations, alternatives, or corrective actions. [monthly]

IAW: RN Program SEPs, RN Program Integration OIs

Document results in: Recommendations for IMS issues or impacts

4.7 Integrate Between RN Projects

4.7.1 The RN SE&I contractor shall identify and track technical interdependencies between projects for each RN program.

Document results in: Project Interdependencies Table

The RN SE&I contractor shall assess development and sustainment 4.7.1.1 contractors’ technical materials delivered or presented to the Government for impacts to other sustainment and development contractors, and present disconnects to the Government. [average 50 assessments per month]

IAW: RN Program SEPs, RN Program Integration OIs

Document results in: Integration Assessment Briefing

4.7.2 The RN SE&I contractor shall track integration issues/risks and work with appropriate stakeholders and sustainment and development contractors to ensure integration issues between projects are being addressed.

IAW: RN Program Integration OIs

Document results in: Integration Issues/Risk Status Table

The RN SE&I contractor shall track overlaps between projects and 4.7.2.1 coordinate with project Integrated Product Teams (IPTs) to ensure the overlaps are resolved/de-conflicted in an integrated manner.

IAW: RN Program Integration OIs

Document results in: Integration Issues/Risk Status Table

The RN SE&I contractor shall identify any gaps not being addressed by 4.7.2.2 sustainment or development contractors and provide recommendations for addressing those gaps.

IAW: RN Program Integration OIs

Document results in: Integration Issues/Risk Status Table

4.7.3 Integrated Test Teams (ITTs)

The RN SE&I contractor shall facilitate and contribute to RN program ITT 4.7.3.1 meetings, as required. [quarterly]

IAW: RN Program ITT charters

Document results in: Agenda, Minutes, Presentation, Action Items

The RN SE&I contractor shall facilitate and contribute to ITT meetings for 4.7.3.2 each RN project.

IAW: RN Project ITT charters

Document results in: Agenda, Minutes, Presentation, Action Items

4.8 Integrate During Projects

4.8.1 Support Reviews

The RN SE&I contractor shall support the project reviews including, but not 4.8.1.1 limited to:

a. Requirement Reviews (RRs)

b. System Functional Review (SFR)

c. Conceptual Design Review

d. Preliminary Design Review (PDR)

e. Critical Design Review (CDR)

f. Pre-ship ILS Documentation Review (Training Package, Maintenance

Plan, TOs, Operator Manual, On-Site ILS Validation Plan, On-Site

Acceptance Test Procedures, Initial Operational Test and Evaluation

(IOT&E) Plan and Procedure)

g. Installation Readiness Review (IRR)

h. FCA and PCA

i. Initial operational capability (IOC) and Full operational capability

(FOC) Reviews

j. Test Readiness Review

k. Transition Readiness Review

l. Transfer to Sustainment

[The particular reviews that a project will have will be tailored by the

Government, average 60 reviews per year]

IAW: RN Program Integration OIs, RN Program SEPs, SMC-S-021

Document results in: CRMs, Readiness Criteria/Readiness

Assessment/Integration Assessments Briefs/Presentations

The RN SE&I contractor shall work with the sustainment and development 4.8.1.2 contractor to develop entrance and exit criteria for the review.

IAW: RN Program SEPs

Document results in: Readiness Criteria

The RN SE&I contractor shall assess the documentation generated for the 4.8.1.3 reviews to identify integration issues/risks (e.g. interface issues/risks, scheduling dependencies/interdependencies issues/risks, consistency of incremental projects with overarching to-be and future architectures, acceptance issues/risks, turnover issues/risks, and transition issues/risks).

IAW: RN Program SEPs

Document results in: CRMs, Readiness Criteria/Readiness

Assessment/Integration Assessments Briefs/Presentations

The RN SE&I contractor shall coordinate the collective review of all 4.8.1.4 documentation by the stakeholders review team.

IAW: RN Program Integration OIs

Document results in: Assignments for Documentation Review for Project

Reviews database

The RN SE&I contractor shall consolidate the stakeholders review team 4.8.1.5 inputs and assess readiness to enter reviews.

IAW: RN Program Integration OIs

Document results in: Consolidated Review Inputs and Readiness

Assessment Spreadsheet

The RN SE&I contractor shall track action items and coordinate with 4.8.1.6 owners through closure.

IAW: RN Program Integration OIs

Document results in: Action Item database

The RN SE&I contractor shall identify and coordinate liens through closure. 4.8.1.7

Document results in: Project Review Liens and Status of Resolution Actions

Table

The RN SE&I contractor shall assess the impact on integration of any new 4.8.1.8 project risks that arise or any changes to existing project risks, and recommend corrective actions or mitigation plans.

IAW: RN Program Integration OIs

Document results in: Candidate Risks (CDRL P011)

Requirement Review 4.8.1.9

4.8.1.9.1 The RN SE&I contractor shall assess whether requirements are clear, concise, complete, verifiable, and reflect user needs.

IAW: RN Program Integration OIs, RN Program Requirements

Management OIs

Document results in: Requirements Assessment CRM

4.8.1.9.2 The RN SE&I contractor shall capture stakeholder agreement on project requirements.

IAW: RN Program Integration OIs, RN Program Requirements

Management OIs

Document results in: Project Memorandum of Agreement (MOA)

PDR and CDR 4.8.1.10

4.8.1.10.1 The RN SE&I contractor shall assess whether requirements are clear, concise,…