Track_Changes_-_Amendment_003.pdf

N0002417R5152

Section C - Descriptions and Specifications

Item(s) 0001 - The data to be furnished hereunder shall be prepared in accordance with the Contract Data Requirements List, DD Form 1423, Exhibit(s) A, attached hereto.

SECTION C - TABLE OF CONTENT

SECTION TITLE PAGE

1.0 INTRODUCTION 10

2.0 APPLICABLE DOCUMENTS 13

3.0 REQUIREMENTS 23

2.1 United States Codes (USC) and Executive Orders 13

2.2 Military Standards 13

2.3 Department of Defense (DoD)/Department of the Navy (DoN) Regulations, Directives and Instructions 14

2.4 Chairman of the Joint Chiefs of Staff (CJCS), Joint Requirements Oversight Committee (JROC) Instructions and Memoranda 16

2.5 Secretary of the Navy (SECNAV) and Office of the Chief of Naval Operations (OPNAV) Instructions 16

2.6 Naval Sea Systems Command (NAVSEA) and Program Executive Office Integrated Warfare Systems (PEO IWS) Regulations, Directives and Instructions 17

2.7 Military Handbooks and DoD Guidance 19

2.8 Non-Government Documents 20

2.9 PEO IWS/NAVSEA Manuals, Plans and Specifications 21

2.10 SSDS Program Specific Guides and Specifications 21

2.11 Availability of Documents 22

2.12 Document Precedence 22

3.1.1 Program Management (All Labor CLINs, CLINs 0010 – 0059, 1000 – 1003, and 1010 – 1090) 25

3.1.1.1 Program Manager (All Labor CLINs, CLINs 0010 – 0059, 1000 – 1003, and 1010 – 1090) 25

3.1.1.2 Program Planning (All Labor CLINs, CLINs 0010 – 0059, 1000 – 1003, and 1010 – 1090) 26

3.1.1.3 Program Management Meetings (All Labor CLINs, CLINs 0010 – 0059, 1000 – 1003, and 1010 – 1090) 26

3.1.1.3.1 Post Contract Award Kick-off Meeting 26

3.1.1.3.2 Program Management Reviews 26

3.1.1.3.3 Technical Reviews 27

3.1.1.3.4 Integrated Product and Process Development (IPPD) 28

3.1.1.4 Cost/Schedule Control 28

3.1.1.4.1 Cost and Software Data Reporting (CSDR) 28

3.1.1.4.1.1 Contract CSDR Plan and Contract Work Breakdown Structure (CWBS) 29

3.1.1.4.1.2 Contract Cost Data Reporting 29

3.1.1.4.1.3 Software Resources Data Reporting (SRDR) – Completion Efforts (CLINs 1000- 1003) 30

3.1.1.4.2 Progress Reporting – LOE (CLINs 0010 – 0059) 30

3.1.1.4.3 Progress Reporting – Completion Efforts (CLINs 1000 – 1003 and 1010 – 1090) 31

3.1.1.5 Program Protection Implementation Plan (PPIP) 32

3.1.1.6 Data Availability and Activity Observation 32

3.1.2 Data Management and Integrated Data Environment (IDE) (All Labor CLINs, CLINs 0010 – 0059, 1000 – 1003, and 1010 – 1090) 33

3.1.3 Risk Management (All Labor CLINs, CLINs 0010 – 0059, 1000 – 1003, and 1010 – 1090) 34

3.1.4 Security Requirements (All Labor CLINs, CLINs 0010 – 0059, 1000 – 1003, and 1010 - 1090) 34

3.1.4.1 System Security Program (All Labor CLINs, CLINs 0010 – 0059, 1000

– 1003, and 1010 – 1090) 35

3.1.4.2 Contractor’s Internal Network and Data Security (All Labor CLINs, CLINs 0010 – 0059, 1000 – 1003, and 1010 – 1090) 36

3.1.4.3 International Traffic in Arms Regulations (ITAR) (All Labor CLINs, CLINs 0010 – 0059, 1000 – 1003, and 1010 – 1090) 36

3.1 Common Tasks to support Level of Effort and Completion Efforts (All Labor CLINs, CLINs 0010 – 0059, 1000 – 1003, and 1010 – 1090) 25

3.1.4.4 Password Management (All Labor CLINs, CLINs 0010 – 0059, 1000 – 1003, and 1010 – 1090) 36

3.1.4.5 Communications Security Requirements (All Labor CLINs, CLINs 0010 – 0059, 1000 – 1003, and 1010 – 1090) 37

3.1.5 Program Security (All Labor CLINs, CLINs 0010 – 0059, 1000 – 1003, and 1010 – 1090) 37

3.1.5.1 Software Information Security (All Labor CLINs, CLINs 0010 – 0059, 1000 – 1003, and 1010 – 1090) 37

3.1.6 Human Computer & Graphical User Interface Development (All Labor CLINs, CLINs 0010 – 0059, 1000 – 1003, and 1010 – 1090) 38

3.1.7 Cybersecurity Activities (All Labor CLINs, CLINs 0010 – 0059, 1000 – 1003, and 1010 – 1090) 38

3.1.7.1 Cybersecurity Planning (All Labor CLINs, CLINs 0010 – 0059, 1000 – 1003, and 1010 – 1090) 40

3.1.7.1.1 Cybersecurity Implementation Plan 40

3.1.7.1.2 Criticality Analysis (CA) 41

3.1.7.1.3 Anti-Tamper Plan 41

3.1.7.2 Designing in Cybersecurity (All Labor CLINs, CLINs 0010 – 0059, 1000 – 1003, and 1010 – 1090) 41

3.1.7.3 Cybersecurity Capability Improvement (All Labor CLINs, CLINs 0010

– 0059, 1000 – 1003, and 1010 – 1090) 43

3.1.7.4 Static Source Code Analysis (All Labor CLINs, CLINs 0010 – 0059, 1000 – 1003, and 1010 – 1090) 43

3.1.7.5 Government Directed Cybersecurity Capability (All Labor CLINs, CLINs 0010 – 0059, 1000 – 1003, and 1010 – 1090) 43

3.1.7.6 Information Assurance Vulnerability Management (IAVM) (All Labor CLINs, CLINs 0010 – 0059, 1000 – 1003, and 1010 – 1090) 44

3.1.7.7 Cybersecurity Verification (All Labor CLINs, CLINs 0010 – 0059, 1000

– 1003, and 1010 – 1090) 44

3.1.7.8 COTS Software and Hardware List (All Labor CLINs, CLINs 0010 – 0059, 1000 – 1003, and 1010 – 1090) 46

3.1.7.9 Operational Security (OPSEC) Training Manuals (All Labor CLINs, CLINs 0010 – 0059, 1000 – 1003, and 1010 – 1090) 46

3.1.7.10 Control of Software Installation (All Labor CLINs, CLINs 0010 – 0059, 1000 – 1003, and 1010 – 1090) 47

3.1.7.11 Master Network Connection Report (MNCR) (All Labor CLINs, CLINs 0010 – 0059, 1000 – 1003, and 1010 – 1090) 47

3.1.7.12 COTS Software Supply Chain Risk Management (All Labor CLINs, CLINs 0010 – 0059, 1000 – 1003, and 1010 – 1090) 48

3.1.7.13 Contractor Information Assurance (IA) Training and Certification (All Labor CLINs, CLINs 0010 – 0059, 1000 – 1003, and 1010 – 1090) 49

3.1.8 Safety (All Labor CLINs, CLINs 0010 – 0059, 1000 – 1003, and 1010 – 1090)49

3.1.8.1 SSDS System Safety (All Labor CLINs, CLINs 0010 – 0059, 1000 – 1003, and 1010 – 1090) 49

3.1.9 Navy Review Team (NRT) Process (All Labor CLINs, CLINs 0010 – 0059, 1000 – 1003, and 1010 – 1090) 51

3.1.9.1 SSDS ICS IPT and WG Structure 51

3.1.10 Open Architecture (All Labor CLINs, CLINs 0010 – 0059, 1000 – 1003, and 1010 – 1090) 52

3.1.11 Architecture and Requirements (All Labor CLINs, CLINs 0010 – 0059, 1000

– 1003, and 1010 – 1090) 55

3.1.12 Technical Development Reviews (All Labor CLINs, CLINs 0010 – 0059, 1000

– 1003, and 1010 – 1090) 56

3.1.12.1 Technical Review Documentation (All Labor CLINs, CLINs 0010 – 0059, 1000 – 1003, and 1010 – 1090) 56

3.1.12.2 Action Item and Comment Resolution Database (All Labor CLINs, CLINs 0010 – 0059, 1000 – 1003, and 1010 – 1090) 57

3.1.13 Network Engineering and Benchmarking (All Labor CLINs, CLINs 0010 – 0059, 1000 – 1003, and 1010 – 1090) 57

3.1.13.1 Quality Assurance Program Plan (QAPP) (All Labor CLINs, CLINs 0010 – 0059, 1000 – 1003, and 1010 – 1090) 58

3.1.14 Hardware Technology Insertion (HTI) Approach (All Labor CLINs, CLINs 0010 – 0059, 1000 – 1003, and 1010 – 1090) 59

3.1.15 Facilities (All Labor CLINs, CLINs 0010 – 0059, 1000 – 1003, and 1010 – 1090) 60

3.1.16 Government and Contractor Furnished Items 61

3.1.17 Government Property Warehousing Requirements 61

3.1.18 Laboratory and GFP Storeroom Requirements 61

3.1.19 Main Laboratory Requirements 62

3.1.19.1 Tactical String Areas 62

3.1.19.2 Developer and Compiler String Areas 63

3.1.19.3 Storeroom Requirements 63

3.1.19.4 Secure System Node Area 63

3.1.20 Non-Standard SSDS Software Usage (All Labor CLINs, CLINs 0010 – 0059, 1000 – 1003, and 1010 – 1090) 64

3.2.1 Overview 65

3.2.2 Common Tasks – Level of Effort 67

3.2.2.1 Program Management - 67

3.2.2.2 Integrated Combat System Safety 68

3.2.2.3 System Engineering 68

3.2.2.3.1 Requirements Assessment 69

3.2.2.3.2 Critical Experimentation and Performance Analysis 70

3.2.2.3.3 Engineering and Technical Support 71

3.2.2.3.4 COTS Obsolescence 72

3.2.2.3.5 SSDS Combat System Certification and Improvements 73

3.2.2.3.6 Reliability and Maintainability Engineering 73

3.2.2.3.7 Training and Maintenance Source Material and Products 74

3.2.2.3.8 SSDS Technical Manuals 74

3.2.2.4 Software Engineering 76

3.2.2.4.1 Software Modeling 77

3.2.2.4.2 Software Metrics 79

3.2.2.4.3 Software Architecture and Requirements 79

3.2.2.4.4 Software Code Walkthroughs 80

3.2.2.4.5 Interface Design and Management 80

3.2.2.4.6 Data Design and Management 81

3.2.2.4.7 Candidate Capability Review & Assessment 81

3.2.2.4.8 Software Testing 82

3.2.2.4.9 Test Data Reduction and Analysis 83

3.2.2.4.10 Software Resource Library 84

3.2.2.4.11 Trouble Reports (TRs) 84

3.2.2.4.12 Software Builds for Specific Navy Ships 86

3.2.2.4.13 Software Version Description 86

3.2.2.4.14 Remote Computer Software Maintenance Support 87

3.2.2.4.15 Software Related Deliverables 88

3.2 Level of Effort Tasking (CLIN 0010, 0020, 0030, 0040, 0050; Option CLINs 0011 – 0019, 0021 – 0029, 0031 – 0039, 0041 – 0049, and 0051 – 0059) 65

3.2.2.4.16 Software Documentation 88

3.2.2.4.17 Software Configuration Management and Control 89

3.2.2.4.18 Software Transmittal 90

3.2.2.5 Software Installation and Support 90

3.2.2.6 Ship Design and Integration Support, and Warfare Systems Engineering 91

3.2.2.7 Testing 93

3.2.2.7.1 Combat System Test & Evaluation (T&E) 93

3.2.2.7.2 Fielded Baseline and Systems Technical Support 93

3.2.2.7.3 Test and Integration Support 94

3.2.2.7.4 At-Sea or Navy Lab Test Support & Reporting 95

3.2.2.7.5 Test Readiness Reviews 95

3.2.2.7.5.1 Test Readiness Review (TRR) 95

3.2.2.7.6 Additional Support for Operational Test Readiness Review (OTRR) 95

3.2.2.7.7 Test Data Reduction and Analysis 95

3.2.2.8 Post-Delivery Support 95

3.2.2.9 Laboratories and Facilities 96

3.3.1 Overview 98

3.3.2 Common Tasks – Completion Efforts 98

3.3.2.1 Program Management Completion Efforts (CLINs 1000 – 1003 and 1010 – 1090) 98

3.3.2.2 Business and Financial Management 99

3.3.2.2.1 Earned Value Management System (EVMS) 99

3.3.2.2.2 Integrated Baseline Review 99

3.3.2.2.3 Cost Reporting 100

3.3.2.2.3.1 Integrated Program Management Report (IPMR) 100

3.3.2.2.4 Schedule Management - IPMR Integrated Master Schedule (IMS) 100

3.3.2.3 System Engineering 101

3.3.2.3.1 Performance Analysis 101

3.3.2.3.2 SSDS Technical Manuals 102

3.3.2.4 Software Engineering 103

3.3 Completion Efforts (CLINs 1000, 1001, and 1002; Option CLINs 1003 and 1010 – 1090) 98

3.3.2.4.1 Software Metrics and Resource Data Reporting 105

3.3.2.4.2 Software Architecture and Requirements Analysis 107

3.3.2.4.3 Human Computer & Graphical User Interface Development 107

3.3.2.4.4 Software Architecture and Modeling 107

3.3.2.4.5 Interface Design and Management 109

3.3.2.4.6 Data Design and Management 109

3.3.2.4.7 Software Resource Library 110

3.3.2.4.8 Software Increment Review (SW IR) 110

3.3.2.4.9 Software Development, Code and Integration 111

3.3.2.4.10 Software Code Walkthroughs 111

3.3.2.4.11 Trouble Reports (TRs) 112

3.3.2.4.12 Software Testing 113

3.3.2.4.13 Test Data Reduction and Analysis 115

3.3.2.4.14 Software Builds for Specific Navy Ships 115

3.3.2.4.15 Software Version Description (SVD) 116

3.3.2.4.16 Software Related Deliverables 117

3.3.2.4.17 Software Documentation 117

3.3.2.4.18 Software Configuration Management and Control 118

3.3.2.4.19 Software Installation and Support 119

3.3.2.4.20 Software Transmittal 119

3.3.2.5 Testing 120

3.3.2.5.1 Test Readiness Reviews (TRR) 121

3.3.2.5.1.1 Test Readiness Review 121

3.3.2.5.1.2 Test Data Reduction and Analysis 121

3.3.2.6 Laboratory Setup 121

3.3.3 Initial Capabilities (CLINs 1000, 1001, 1002, and 1003) 122

3.3.3.1 ACB 20 Initial Software Capabilities (CLIN 1000) 122

3.3.3.1.1 Incorporate HTI-16 into Laboratory 124

3.3.3.1.2 ACB 20 Initial Capabilities Requirements 125

3.3.3.1.2.1 ACB 20 Initial Software Capability – Enterprise Air Surveillance Radar

(EASR) 126

3.3.3.1.2.1.1 EASR Overarching Description 126

3.3.3.1.2.1.2 EASR Capability for SSDS Task Description 127

3.3.3.1.2.2 ACB 20 Initial Software Capability – ESSM BLK 2 131

3.3.3.1.2.2.1 ESSM BLK 2 Overarching Description 131

3.3.3.1.2.2.2 ESSM BLK 2 Capability for SSDS Task Description 132

3.3.3.1.2.3 ACB 20 Initial Software Capability – Electronic Warfare (EW) Integration 136

3.3.3.1.2.3.1 EW Integration Overarching Description 136

3.3.3.1.2.3.2 EW Integration Capability for SSDS Task Description 137

3.3.3.2 Software Adaptation to HTI-12 (CLIN 1001) 143

3.3.3.2.1 Incorporate HTI-12 into Laboratory 143

3.3.3.2.2 Software Adaptation to HTI-12 Overarching Description 143

3.3.3.2.3 Software Adaptation to HTI-12 Task Description 144

3.3.3.3 Software Adaptation to HTI-12H (CLIN 1002) 149

3.3.3.3.1 Incorporate HTI-12H into Laboratory 149

3.3.3.3.2 Software Adaptation to HTI-12H Overarching Description 150

3.3.3.3.3 Software Adaptation to HTI-12H Task Description 150

3.3.3.4 Software Adaptation to HTI-16TR (CLIN 1003) 155

3.3.3.4.1 Incorporate HTI-16TR into Laboratory 156

3.3.3.4.2 Software Adaptation to HTI-16TR Overarching Description 156

3.3.3.4.3 HTI-16TR Description 156

3.3.3.4.4 Software Adaptation to HTI-16TR Task Description 157

3.4 Other Direct Costs and Incidental Materials (CLIN 0030 and if options are exercised, CLINs 0031-0039) 163

3.5 Travel in Support of Efforts (Applicable to LOE Labor CLINs) 163

3.6 Enhanced Data Rights (Applicable to CLIN 0002) 163

1.0 INTRODUCTION

The objective of this Statement of Work (SOW) is to evolve and maintain the Ship Self Defense System (SSDS) at the ship level for the Carriers (CVN class ships) and Large Deck Amphibious Ships (LHA, LPD, LHD, and LSD class ships), and future surface combatant ship classes, where the SSDS Combat System Engineering Agent (CSEA), here forth referred to as “the Contractor,” shall develop, integrate and maintain combat management system capabilities for all baselines applicable to those ship classes. The Contractor shall deliver the source code, objects, scripts, and executables required to build, install, load, operate, maintain and update the application, as well as provide integrated logistics support source material and applicable documentation for the capability.

The Contractor shall develop, integrate and test future Advanced Capability Builds (ACB) and Hardware Technology Insertions (HTIs), develop engineering products to support ship integration, support Developmental Test/Operational Test (DT/OT), develop training and logistics products, and provide field technical support for designated combat systems baselines.

The systems engineering, development, and integration work under this contract shall begin with ACB 20 and HTI-16, and continue with future ACBs and HTIs through the period of performance of this contract. The Contractor shall be responsible for in-service software maintenance of the Builds 6, 9, 10 and 11 as directed via Technical Instructions under CLINS 0010-0059.

An ACB defines the capabilities added to the Software resource library such that the Build(s) associated with the ACB are deliverable to all classes of ships in an integrated combat system package that satisfies its operational requirements in an effective, safe, and reliable manner. The delivered Builds (as part of the Software resource library) include software for ship-specific elements and other software and systems integral to the overall functions of SSDS.

An HTI is a replacement and/or upgrade of combat system computing hardware and associated middleware and firmware to take advantage of technology advances in hardware capability. The Surface Navy's future combat system acquisition strategy relies on a model that separates computing infrastructure from software application development. For the purposes of configuration information, an HTI is referenced to a specific model year (e.g., HTI-12 or HTI- 16). The HTI process is used to modernize the computing infrastructure on surface combatants on a periodic basis. The Contractor’s role with respect to HTIs is to provide SSDS analysis support by providing hardware systems change recommendations to the Government.

The SSDS program uses terms with the following general definitions, such as: a) Build - Computer software program (e.g., application program, operating environment, source code) and all associated deliverables (e.g., site data, adaptation data interface message definitions, software version descriptions) to represent a complete functional SSDS software deliverable; and b) Release - The process of delivering either a full or incremental software build. The release will contain the functionality to support planned use of the build.

CLIN 0001 – DATA – CDRLs for CLINs 0010 through 0059; CLINs 1000, 1001, 1002, 1003, 1010, 1020, 1030, 1040, 1050, 1060, 1070, 1080 and 1090 (Exhibit A)

The CLIN 0001 is identified as the DATA CLINs 0010, 1000, 1001, and 1002, and if options are exercised CLINs 1003, 0011 through 0059, and 1010 through 1090. The data to be furnished shall be developed and delivered in accordance with the Contract Data Requirements List (CDRL), DD Form 1423, Exhibit A, attached hereto.

CLIN 0002 – ENHANCED DATA RIGHTS

Enhanced Data Rights for those items of Commercial and Non Commercial Technical Data (TD), Computer Software (CS), and Computer Software Documentation (CSD) which the Offeror provided an Option price for the Government to exercise and procure greater rights than its list of asserted restrictions. See paragraph 3.7 Enhanced Data Rights, Attachment J-13 and Attachment J-23.

CLIN 0010-0059 – CY 2019-2029 CPIF LOE for SSDS CVN/Amphib in-Service Support

The Contractor shall provide engineering support for existing baseline software modifications (e.g., fixes and improvements) under Level of Effort (LOE) tasking (CLINs 0010 through 0059) in accordance with NAVSEA 5252.242-9115 TECHNICAL INSTRUCTIONS (APR 1999) in Section H of this contract. The LOE effort under this contract includes development and delivery of software code fixing or improving existing baselines, including those baselines developed under this contract’s completion CLINs post Government acceptance, at Formal Qualification Testing (FQT). Additional LOE efforts include software maintenance support; software production and delivery support; critical experiments and studies; advanced systems engineering;

commercial-off-the-shelf (COTS) hardware obsolescence analysis and sustainment tasks; lab upgrades and maintenance; DT/OT support, training and logistics support, and technical support for fielded systems.

CLIN 0060-0069 – CY 2019-2029 ODC and Incidental Materials

The contract CLINs 0060 through 0069 include the Other Direct Costs (ODC) and Incidental Materials for the labor CLINs 0010, 0020, 0030, 0040, and 0050 and if options are exercised, CLINs 0011-0019, 0021-0029, 0031-0039, 0041-0049, and 0051-0059 in accordance with NAVSEA 5252.242-9115 TECHNICAL INSTRUCTIONS (APR 1999) in Section H of this contract.

CLIN 0070-0079 – CY 2019-2029 Travel

The Contractor shall utilize CLINs 0070 through 0079 for reporting of travel and shall be reimbursed for its actual subsistence and transportation costs incurred in the performance and in support of CLINs 0010, 0020, 0030, 0040, and 0050, and if options are exercised CLINs 0011- 0019, 0021-0029, 0031-0039, 0041-0049, and 0051-0059 as directed by and in accordance with NAVSEA 5252.242-9115 TECHNICAL INSTRUCTIONS (APR 1999) in Section H of this contract.

CLIN 1000, 0003AA, 0003AB, 0003AC – SSDS EASR, ESSM and EW Capability Improvements – Completion

The Contractor shall develop and deliver a full capability software build that integrates capabilities as directed in the SOW. CLIN 1000 is identified as the initial ACB 20 with SSDS software improvements conforming and compatible with the HTI-16 configuration. These efforts result in the SSDS Build 12 configurations incorporating the capabilities of Enterprise Air Surveillance Radar (EASR) (V)1 and (V)2, Evolved Sea Sparrow Missile (ESSM) BLK 2, and Electronic Warfare (EW) Integration into the SSDS CS element on HTI-16.

CLIN 1001, 0003AD - HTI-12 Software Migration – Completion

Deliver software adapted to operate on different SSDS hardware configurations, in this case for the adaptation of ACB 20, Build 12 with the HTI-12.

CLIN 1002, 0003AE - HTI-12H Software Migration – Completion

Deliver software adapted to operate on different SSDS hardware configurations, in this case for the adaptation of ACB 20, Build 12 with the HTI-12H.

CLIN 1003 - HTI-16TR Software Migration – Completion (Option)

Deliver software adapted to operate on different SSDS hardware configurations, in this case for the adaptation of ACB 20, Build 12 with the HTI-16TR.

CLINs 1010-1090 - MOD/ECP - CPIF LOE PLACEHOLDER - Subsequent Capabilities -

CY 2020-2028

The Government intends to identify other future capability development efforts to negotiate post-award as completion efforts utilizing the process as defined in Section H, “H-30: Government Intent to Convert LOE.” The contract CLINs 1010 through 1090 are currently identified as LOE Placeholder CLINs that establish the rates for these future capability improvements.

2.0 Applicable Documents

The following documents are applicable to the work described herein and are for use by the Contractor as either general guidance, as appropriate to the type of product, or mandatory as a requirement in the fulfillment of those tasks unless referenced by a specific section of the Statement of Work (SOW).

2.1 United States Codes (USC) and Executive Orders

US Code 42, Chapter 55 – National Environmental Policy; Section 4321- 4370h

National Environmental Policy Act (NEPA) Guidance

US Code 10, Chapter 144 – Major Defense Acquisition Programs; Section 2435 - Baseline description

Major Defense Acquisition Programs - Baseline description

Guidance

Executive Order 13148

Greening the Government Through Leadership in Environmental Management

22 Apr

Guidance

FIPS PUB 140-2 Federal Information Processing Standards Publication

- Security Requirements for Cryptographic Modules

03 Dec

Guidance

2.2 Military Standards

MIL-STD-167-1A Mechanical Vibrations of Shipboard Equipment (Type I-Environmental and Type II-Internally Excited)

02 Nov

Guidance

MIL-STD-461F Department of Defense Interface Standard- Requirements for the Control of Electromagnetic Interference Characteristics of Subsystems and Equipment

10 Dec

Guidance

MIL-STD-810G(1) Environmental Engineering Considerations and Laboratory Tests

15 Apr

Guidance

MIL-STD-882E Department of Defense Standard Practice – System Safety

11 May

Mandatory

MIL-S-901D Shock Tests, H.I. (High Impact) Shipboard Machinery, Equipment, and Systems, Requirements for

17 Mar

Guidance

MIL-STD-1310H Shipboard Bonding, Grounding, and other Techniques for Electromagnetic Compatibility, Electromagnetic Pulse (EMP) Mitigation, and Safety

17 Sep

Guidance

MIL-STD-1399C Interface Standard for Shipboard Systems 02 Feb

Guidance

MIL-STD-1472G Department of Defense Design Criteria Standard - Human Engineering

11 Jan

Guidance

MIL-STD-46855A Human Engineering Requirements for Military Systems, Equipment, and Facilities

24 May

Guidance

2.3 Department of Defense (DoD)/Department of the Navy (DoN) Regulations, Directives and Instructions

DoDI 1100.22 Policy and Procedures for Determining Workforce Mix 12 Apr

Guidance

DoDI 4140.01 DoD Supply Chain Materiel Management Policy 14 Dec

Guidance

DoDM 4140.01, Vol 1 through Vol

DoD Supply Chain Materiel Management Procedures 10 Feb

25 Jun

14 Aug

Guidance

DoDI 5000.02

CHG 2

Operation of the Defense Acquisition System 02 Feb

Guidance

DoDD 5000.01 The Defense Acquisition System 12 May

(current as of 20 Nov 2007)

Guidance

DoDM 5000.04- M-1

Cost and Software Data Reporting (CSDR) Manual 04 Nov

Guidance

DoDI 5000.61 DoD Modeling and Simulation (M&S) Verification, Validation, and Accreditation (VV&A)

09 Dec

Guidance

DoDM 5105.21

VOL 1

Sensitive Compartmented Information (SCI) Administrative Security Manual: Administration of Information and Information Systems Security

19 Oct

Mandatory

DoDI 5200.39 Critical Program Information (CPI) Identification and Protection Within Research, Development, Test, and Evaluation (RDT&E)

28 May

Guidance

DoDI 5200.44 Change 1

Protection of Mission Critical Functions to Achieve Trusted Systems and Networks (TSN)

25 Aug

Guidance

DoDM 5205.02-M DoD Operations Security (OPSEC) Program Manual 03 Nov

DoDD 5220.22-M Change 1

National Industrial Security Program Operating Manual

(NISPOM)

28 Mar

Mandatory

DoDI 5230.24 Distribution Statements on Technical Documents 23 Aug

Guidance

DoDD 5230.25 Change 1

Withholding of Unclassified Technical Data from Public Disclosure

18 Aug

Guidance

DoDI 8320.02 Sharing Data, Information, and Information Technology (IT) Services in the Department of Defense

05 Aug

Guidance

DoDI 8500.01 Cybersecurity 14 Mar

Mandatory

DoDI 8510.01 Risk Management Framework (RMF) for DoD IT 12 Mar

Mandatory

DoDI 8520.02 Public Key Infrastructure (PKI) and Public Key (PK) Enabling

24 May

Guidance

DoD 8570.01-M Change 4

Information Assurance Workforce Improvement Program 10 Nov

Guidance

DoDI 8582.01 Security of Unclassified Information on Non-DoD Information Systems

06 Jun

Guidance

DoDD 8140.01 Cyberspace Workforce Management 11 Aug

Mandatory

DoN CIO MEMO 02-10

Department of the Navy Chief Information Officer Memorandum, Information Assurance Policy Update for Platform Information Technology

26 Apr

Guidance

DoD IPPD Handbook

DoD Integrated Product and Process Development Handbook

Aug-98 Guidance

ASN (RDA)

MEMO

DoN Policy on Digital Product/Technical Data w/Attachment "Guidance on Acquisition and Conversion of Product / Technical Data to Digital Form" Revision 1

23 Oct

Guidance

ASN (RDA)

MEMO

Software Process Improvement Initiative Contract Language

17 Nov

Guidance

ASN (RDA)

MEMO

Software Process Improvement Initiative (SPII) Guidance for Use of Software Process Improvement Initiative Contract Language

13 Jul

Guidance

DOT&E MEMO Procedures for Operational Test and Evaluation of Cybersecurity in Acquisition Programs

01 Aug

2.4 Chairman of the Joint Chiefs of Staff (CJCS), Joint Requirements Oversight Committee (JROC) Instructions and Memoranda

CJCSI 3170.01I Joint Capabilities Integration and Development System (JCIDS)

23 Jan

Guidance

CJCSI 6212.01F Net Ready Key Performance Parameter (NR KPP) 21 Mar

Guidance

CJCSI 6510.01F

(Series)

Information Assurance (IA) and Support to Computer Network Defense (CND)

09 Feb

(current as of 09 Jun 2015)

JROCM 236-03

Joint Requirements Oversight Committee Memorandum, Policy for Updating Capabilities Documents to Incorporate the Net-Ready Key Performance Parameter (NR-KPP)

19 Dec

Guidance

2.5 Secretary of the Navy (SECNAV) and Office of the Chief of Naval Operations (OPNAV) Instructions

SECNAVINST

5200.38A

Department of the Navy (DoN) Modeling and Simulation Management

28 Feb

Guidance

OPNAVINST

1500.76C

NAVAL TRAINING SYSTEM REQUIREMENTS,

ACQUISITION, and MANAGEMENT

14 Aug

Guidance

OPNAVINST

5100.19E

Vols. I, II, and III: NAVY SAFETY and

OCCUPATIONAL HEALTH (SOH) PROGRAM

MANUAL for Forces Afloat

30 May

Guidance

OPNAVINST

5100.23G CH-1

NAVY SAFETY AND OCCUPATIONAL HEALTH

(SOH) PROGRAM MANUAL

21 Jul

Guidance

SECNAVINST

5510.34A

DISCLOSURE OF CLASSIFIED MILITARY

INFORMATION and CONTROLLED UNCLASSIFIED INFORMATION to FOREIGN

GOVERNMENTS, INTERNATIONAL

ORGANIZATIONS, and FOREIGN

REPRESENTATIVES

08 Oct

Guidance

SECNAV M-5239.1 Information Assurance Manual Nov

Guidance

SECNAV M-5239.2 Cyberspace Information Technology and Cybersecurity Workforce Management and Qualification Manual

Jun

Guidance

SECNAV M-5510.36 Department of the Navy Information Security Program

June

SECNAVINST

5510.36A

DEPARTMENT of the NAVY (DoN)

INFORMATION SECURITY PROGRAM (ISP)

INSTRUCTION

06 Oct

Guidance

OPNAVINST

5513.3C

CNO Documentation Classification guidelines 21 Jul

Guidance

OPNAVINST

3000.12A

Operational Availability of Equipments and Weapons System

02 Sep

Guidance

ASN (RD&A) 3000/

VCNO 3000 Memo Ser N09/16U100548

Cyber Security Compliance of Information Assurance Technical Authority Standards

08 Nov

Mandatory

2.6 Naval Sea Systems Command (NAVSEA) and Program Executive Office Integrated Warfare Systems (PEO IWS) Regulations, Directives and Instructions

PEOIWSINST

5239.1

PEO IWS Surface Navy Combat System Cybersecurity Memo

With Encls: (1) PEO IWS Enclave Cybersecurity Requirements Version 1.0; and (2) Acronyms

31 May

SECNAVINST

5239.22

DoN Cybersecurity Safety Program 15 Nov

Guidance

USN CYBERSAFE

Version 1.0

United States Navy Space and Naval Warfare Systems Command

Information Assurance Technical Authority (IA TA)

Navy Cybersecurity Safety (CYBERSAFE) Grade Requirements Standard

20 Oct

Mandatory

PEOIWSINST

5000.8 MEMO

PEO IWS RISK MANAGEMENT POLICY MEMO

With (Enclosure 1: Instructions for Risk Reporting)

31 Jan

Guidance

PEOIWSINST

3058.1

Risk Management 02 Aug

Guidance

NAVSEAINST

5000.8

Naval SYSCOM Risk Management Policy 21 Jul

Guidance

PEOIWSINST

3086.01

Automated Test and Analysis (ATA) Policy 30 Apr

Guidance

Surface Navy Combat Systems Software Product Line Architecture, Architecture Description Document (ADD), Version 1.0

31 Jul

Guidance

PEOIWSINST

4130.1B

Integrated Warfare Systems (IWS) Enterprise Configuration Control Process (ECCP)

14 Sep

NAVSEAINST

S9040: (AA-GTP-

010/SSCR, Revision 4)

Shipboard Systems Certification Requirements for Surface Ship Industrial Periods [Non-Nuclear]

Jun

Guidance

NAVSEAINST

S9095 AD-TRQ-

010/TSTP

Total Ship Test Program Manual Mar

Guidance

NAVSEAINST

4160.3B

Technical Manual Management Program (TMMP) 21 Jun

Guidance

Surface Navy Combat Systems Development Strategy Acquisition Management Plan (AMP) Version 0.8

28 Jul

Guidance

NAVSEAINST

8020.6E

Department of the Navy Weapon System Explosives Safety Review Board (WSESRB)

11 Mar

Guidance

PEOIWSINST

4730.1A (Memo)

Combat System Certification Policy 05 Jan

Guidance

PEOIWSINST

4730.1A (Encl 1)

Combat System Certification Process 05 Jan

Guidance

PEOIWSINST

4730.1A (Encl 1, Attachments 1-10)

Combat System Certification Process 05 Jan

Guidance

PEOIWSINST

4732.1

Element Certification Policy Memo and Element Certification Process document

16 Jul

Guidance

NAVSEAINST

9410.2A

Naval Warfare System Certification Policy / Naval Warfare Systems Certification Process

24 Aug

Guidance

SECNAVINST

5239.3C

DoN Cybersecurity Policy 02 May

Guidance

NAVSEAINST

9400.2A

Implementation of Naval Sea Systems Command (NAVSEA) Afloat Information Assurance Governance and Guidance

20 Sep

Guidance

NAVSEAINST

9400.2-M

PIT-Control System Cybersecurity Implementation Manual – Version 5.0

Oct

Guidance

9470-002-A-X-C PEO IWS Enterprise Configuration Control Process User Guide

(this is Encl 2 PEO IWS INST 4130.1B)

14 Sep

Guidance

NAVSEA TE000-

AB-GTP-010

Rev 1 With Change A

Parts Derating Requirements and Application Manual for Navy Electronic Equipment

Mar

PEOIWSINST

5234.1

PEO IWS Software Measurement Policy and PEO IWS Software Measurement Handbook

31 Jan

Guidance

PEO IWS Systems Engineering Concept of Operations V1.0

22 Apr

Guidance

NAVSEA Std 03-01 Common Presentation Layer Specification Aug

Guidance

PEOIWSINST

5200.3

Verification, Validation and Accreditation (VV&A) of Modeling and Simulation (M&S)

07 Apr

Guidance

PEOIWSINST

4731.1

COMBAT SYSTEM STRESS AND ENDURANCE

TEST REQUIREMENTS FOR SURFACE

PROGRAMS

13 Nov

Guidance

PEO IWS Memo

Ser IWS10/17-065

SSDS Combat System Security Directive 05 Jun

Guidance

2.7 Military Handbooks and DoD Guidance

MIL-HDBK-61A Configuration Management Guidance 07 Feb

Guidance

MIL-HDBK-502A Acquisition Logistics Handbook 08 Mar

Guidance

MIL-STD-881C Work Breakdown Structures For Defense Materiel Items

03 Oct

Guidance

MIL-HDBK-1785

and NOT 1

System Security Engineering Program Management Requirements

01 Aug

(current as of 22 Apr 2014)

Mandatory

DoDAF v2.0.2 Chg 1

- Vols. I, II, and III

DoD Architecture Framework: Volumes I, II, and III 31 Jan

Guidance

Naval Open Architecture Contract Guide Book for Program Managers Version 2.0

30 Jun

Guidance

Joint Software Systems Safety Handbook 27 Aug

Guidance

Risk Management Guide for DoD Acquisition, 6th Edition, Version 1.0

Aug

Guidance

SPAWAR

Memorandum Ser 5.0/1274

Qualification Standards and Registration Procedures for Navy Validators

18 Mar

2.8 Non-Government Documents

ASQC-Q9001-2008 Quality Systems - Model for Quality Assurance In- Depth, Development, Production, Installation, and Servicing

15 Nov

Guidance

ANSI EIA-649-B National Consensus Standard for Configuration Management

01 Apr

Guidance

ANSI EIA-649-1 Configuration Management Requirements for Defense Contracts

Nov

Guidance

ANSI EIA-632 Processes for Engineering a System 07 Jan

Guidance

IEEE 828-2012 Software Configuration Management Plans 16 Mar

Guidance

IEEE 1012a-2012 Standard for Software Verification and Validation 25 Mar

Guidance

IEEE/ISO/IEC

16326-2009

Systems and Software Engineering--Life Cycle Processes--Project Management

15 Dec

Guidance

IEEE 1220-2005 Application and Management of The Systems Engineering Process, Standard for

09 Sep

Guidance

IEEE/ISO/IEC

12207-2008

Systems and Software Engineering – Software Life Cycle Processes

31 Jan

Guidance

ISO 9000:2015 Quality Management Systems - Fundamentals and Vocabulary

15 Sep

Guidance

ISO 9001:2015 Quality Management Systems – Requirements 15 Sep

Guidance

ISO 9004:2009 Managing for the sustained success of an organization

- A quality management approach

01 Nov

Guidance

ISO 10007:2003 Quality Management - Guidelines for Configuration Management

01 Jun

Guidance

ISO 10013:2001 Guidelines for Quality Management System Documentation

12 Jul

Guidance

ISO 10015:1999 Quality Management - Guidelines for Training 01 Dec

Guidance

NIST Publication 500-220

National Institute of Standards and Technology;

Special Guide on Open System Environment (OSE) Procurements

Oct

Guidance

NIST Special Publication 800-53 Revision 4

Security and Privacy Controls for Federal Information Systems and Organizations

Apr

NIST Interagency Report 7622 (NISTIR 7622)

Notional Supply Chain Risk Management for Federal Information Systems

Oct

Guidance

National Defense Industrial Association System Assurance Committee Guidebook - Version 1.0

Engineering for System Assurance 2008 Guidance

2.9 PEO IWS/NAVSEA Manuals, Plans and Specifications

PEO IWS-SEA 05H Technical Review Manual (TRM) Version 2.0

18 Dec

Mandatory

ASN(RD&A) Supplement to Guidebook for Acquisition of Naval Software Intensive Systems – “Software Criteria and Guidance for Systems Engineering Technical Reviews

(SETR)”

Sep

Guidance

Serial Number (*):870-96-13

Capability Development Document (CDD) for Ship Self Defense System (SSDS) MK 2 (ACAT 1C)

18 Dec

Mandatory

WS35561 Performance and Compatibility Requirements (P&CR) for the Ship Self Defense System (SSDS)

MK 2

01 Jul

Mandatory

SSDS ICS Requirements Document (SIRD) - Draft Mandatory

WS35511B WS3511B MK2 SSS Rev B dated 7 March 2003 (includes LCCB approved & applied SCNs) Version:

9.0

Printed from

DOORS

28 Sep

Mandatory

NAVSEA Standard 03-01

Common Presentation Layer Specification - A Style Guide and Requirement Specification for NAVSEA and Associated PEOs Human Computer Interfaces

Aug

Guidance

NAVSEA 9500.2-M NAVSEA PIT-Control System Cybersecurity Implementation Manual

Oct

Guidance

2.10 SSDS Program Specific Guides and Specifications

TMCR NO. SNIPP-

130015-000

Operator and Maintenance Instruction Interactive Electronic Technical Manuals (IETMs) for Ship Self Defense Systems Using S1000D Issue 3.0

15 Nov

Guidance

S1000D IETM Development Style Guide (IDSG) -draft

26 Jan

Business Rules for Publications Developed using S1000D (Revision 3)

15 Apr

Guidance

SSDS S1000D Development Style Sheet 23 Sep

Guidance

2.11 Availability of Documents

Copies of military handbooks, instructions, standards and specifications and DoD adopted non- Government standards may be obtained in accordance with Federal Acquisition Regulation (FAR) Subpart 52.211-2. Copies of specifications, standards, and data item descriptions cited in this solicitation, if listed in the DoD Index of Specifications and Standards (DoDISS) or the Acquisition Management Systems and Data Requirements Control List, DoD 5010.12-L (Dec 2003) may be obtained from:

a. ASSIST database via the Internet at http://quicksearch.dla.mil/

b. DoD issuances http://www.dtic.mil/whs/directives/

c. DoN issuances http://doni.daps.dla.mil/default.aspx

d. PEO IWS documents (Please email courtney.ryan@navy.mil)

e. Access to Bidder Library materials is through the information and processes provided in the CSEA NSERC TOUA file on FEDBIZOPPS.

f. Copies of non-Government publications not listed in the DoDISS may be obtained from the respective industry association.

2.12 Document Precedence

In the event of conflict between the Mandatory and Guidance documents in the preceding paragraphs, the order of precedence shall be the Mandatory documents and then any other reference document(s).

The hierarchy of the requirements documentation specified below throughout Section 3.0, “Requirements,” are found in the Attachment J-22 “SSDS MK2 Element Specification Tree”.

3.0 REQUIREMENTS

Today’s carrier and amphibious CS, and Command, Control, Communications, Computers, Combat Systems, Intelligence Surveillance and Reconnaissance (C5ISR) systems that comprise the ship’s total warfare system are extremely complex. Within ship classes there are frequently multiple configurations of hardware and software. Because each ship class contains unique warfare systems, the Government is establishing the CSEA role for SSDS-based combat system engineering which supports the ship class warfare system engineering and integration as it pertains to the SSDS Element. The Contractor shall provide engineering support for the in-service and future Navy surface carrier and amphibious class ships, as defined by the Government, using the evolutionary baselines through the formal release process. The Contractor shall also execute continued Navy war-fighting improvement efforts for carrier and amphibious ships, including:

a. Support the ship modernization process and provide post-delivery support for all carrier and amphibious ship classes with SSDS.

b. Support the new ship class construction process and provide post-delivery support carrier and amphibious ship classes.

c. Plan for the integration of key future warfighting upgrades for the carrier and amphibious ship classes.

d. Develop and integrate new SSDS capabilities.

e. Develop and test new or upgraded SSDS combat system capabilities, as directed, and integrate new combat system capabilities developed by other parties that are provided to the Contractor either as Government Furnished Information (GFI), Government Furnished Property (GFP) or as a proprietary “black box” system with defined interface specifications.

f. Integrate new hardware or software versions of evolving combat system elements into the carrier and amphibious ship class SSDS configurations.

g. Support the SSDS software delivery process and associated software installation team(s).

h. Support the SSDS Element and Inventory of Contracted Services Configuration Management (CM) process to support accurate and efficient configuration status and accounting.

i. Provide for the SSDS software maintenance of the carrier and amphibious ship classes and maintain a software resource library for these components.

j. Provide SSDS maintenance support and deliver software upgrades to land-based test and training sites including the Surface Combat System Center (SCSC) Ship Self Defense Facility (SSDF) Building V24, Integrated Combat System Test Facility (ICSTF), and Combat Direction Systems Activity (CDSA) Dam Neck.

k. Support PEO IWS product line architecture and engineering initiatives to evolve the SSDS to the PEO IWS objective architecture and common product line.

The Contractor shall perform the engineering tasks and provide support for applicable versions of SSDS for the carrier and amphibious ship classes and other future carrier and amphibious ships with an SSDS capability requirement. For CLINs identified as LOE, the requirements set forth in this SOW are applicable to the extent specified and tasked to the Contractor in any written individual Technical Instructions issued in accordance with NAVSEA clause

5252.242.9115. Such guidance or clarification can be in the form of replication or by reference to SOW paragraph numbers in part or in total. Specific Contractor responsibilities, as specified in TIs, may include, but are not limited to the tasks outlined in Section 3.2.1.

Figure 1 below provides a pictorial representation of the Government’s contractual relationship across the SSDS Platform. It shall be understood that the CSEA will work with Government technical laboratories and Systems Engineering Integration and Test (SEI&T) in execution of this contract.

SEI&T Provide Support for Requirements Decomposition

Government Tasked Install and Test

CSEA Requirements Assessment (LOE)

Support Install and Test (LOE)

Government Conduct Contractor Interface

Install and Test

SY/DT/OT

Figure 1 - Phase of work over time

Specific activities tasked to the Contractor in this SOW for the execution of the Completion Efforts may include, but are not limited to:

Perform componentization, modularization, documentation, and data modeling to support integration of the capability while either implementing or remaining consistent with the PEO IWS Product Line Architecture.

Develop requirements and design documents for SSDS Elements.

Implement the capability, and integrate any GFI software capability upgrades, Government Specified changes, or other new GFP subsystems into carrier and amphibious ship class combat systems within the Government controlled architecture.

Perform software development to ensure that all of the unaffected SSDS functionality is still supported.

Develop "ship specific" software code necessary to ensure the combat system software successfully functions for the ship specific combat system configurations that operate with and use this capability.

Support the Government team that develops Integrated Logistics Support (ILS) products and documentation including provisioning, associated with the new capability.

Develop and deliver new training materials, operations training material, and customized training scripts to support training and training curriculum associated with the new capability.

Develop and implement a test strategy, emphasizing automated testing techniques where appropriate, which incorporates component-level, capability-level, and system-level testing in support of ship integration and potential cross-combat system reuse.

Conduct Verification and Validation (V&V) activities of their software at the element level throughout system/software development in support of combat system certification.

Conduct component, sub-system, and system level critical experimentation and testing.

Support shipboard installation of the software and hardware systems and operational testing of the capabilities at-sea.

Support the CS and SSDS through Integrated CS testing.

3.1 Common Tasks to support Level of Effort and Completion Efforts (All Labor CLINs, CLINs 0010 – 0059, 1000 – 1003, and 1010 – 1090)

The following requirements are generally applicable across the CLINs performed under this contract, identified in either LOE Technical Instructions or Completion Efforts. Additionally, the LOE and Completion Efforts have differing functional area requirements that are addressed separately in 3.2 Level of Effort Tasking and 3.3 Completion Efforts.

3.1.1 Program Management (All Labor CLINs, CLINs 0010 – 0059, 1000 – 1003, and 1010 – 1090)

The Contractor shall communicate and document plans, processes, and approaches to meet all task requirements. The Contractor shall use a metrics based management approach for planning, scheduling, and technical, cost, risk, and quality monitoring and reporting of each Technical Instruction with program-wide visibility of plan versus actual performance under this contract.

The Contractor shall establish and maintain a Program Management process that ensures all work performed across this contract is clearly and concisely demonstrated, and meets all technical objectives within the Contractor’s established cost and schedule baseline. Program management shall include appropriate metrics and tracking processes to allow clear visibility into the program and to ensure the program remains within cost and schedule.

3.1.1.1 Program Manager (All Labor CLINs, CLINs 0010 – 0059, 1000 – 1003, and 1010 – 1090)

The Contractor PM shall have complete responsibility for the planning, execution, and control of all aspects of the program, and for directing in-house and subcontractors’ efforts in the areas of design, fabrication, documentation, test and evaluation. The PM shall ensure all work conducted within this contract is planned and executed in a manner that achieves all management, technical, logistics, budget, and schedule objectives. The PM shall ensure that the necessary controls of in-house equipment, software development, and support efforts are appropriately applied (e.g., design reviews, reliability and maintainability, safety program, quality assurance, CM, integrated logistic support, financial management, and subcontract management).

The Contractor PM shall have the necessary authority to utilize the company’s resources to ensure all requirements of this contract are accomplished. The PM shall be authorized to deal directly with either the PEO IWS 10 or designated representative on all matters pertaining to these contract efforts.

3.1.1.2 Program Planning (All Labor CLINs, CLINs 0010 – 0059, 1000 – 1003, and 1010 – 1090)

The Contractor shall update Attachment J-15 and deliver the Program Management Plan (PMP) (CDRL A009). The PMP shall also include updates, as dictated in CDRL A009, to the Open Systems Management Plan and Security Management Plan (SMP) provided with the Offeror’s proposal.

Deliverable Data Item (See DD-1423):

a. A009, “Management Plan; Program Management Plan (PMP) Updates and Revisions”

3.1.1.3 Program Management Meetings (All Labor CLINs, CLINs 0010 – 0059, 1000 – 1003, and 1010 – 1090)

The Contractor shall notify the Government of all Contractor reviews to include the delivery of preliminary agenda topics, security considerations, locations, and times. The Contractor shall prepare and submit for Government approval, prior to distribution, all agendas, minutes and action item lists to document the reviews. The Contractor shall have the ability to establish classified and unclassified multi-site conferencing for any reviews or meeting. Trip reports for the previous month shall be provided as an appendix to the Monthly Progress and Status Reports.

The Contractor shall make the final presentation material available at least five (5) business days in advance of the meeting or conference. Preliminary presentation material, sufficient to demonstrate the scope and quality of material to be presented shall be made available at least fifteen (15) business days in advance of the review and/or conference.

3.1.1.3.1 Post Contract Award Kick-off Meeting

The Contractor shall provide an agenda (CDRL A010), Presentation Material (CDRL A012) and minutes (CDRL A011) on its management and contract execution strategy at the Post-Award Kick-off Meeting to be held within two (2) weeks of contract award. The Contractor shall plan for a one-day Post Award Kick-off Meeting at the Contractor’s facility. As options are exercised, or major modifications are executed, the Government reserves the right to conduct additional kick-off meetings.

Deliverable Data Item (See DD-1423):

a. A010, “Conference Agenda”

b. A012, “Presentation Material”

c. A011, “Report, Record of Meeting/Minutes”

3.1.1.3.2 Program Management Reviews

The Contractor shall conduct quarterly Program Management Reviews (PMR), beginning ninety

(90) days after award. The purpose of this review is to ensure project approach and planned execution is technically sound, meets all requirements of this contract, and properly documented in the design documentation.

The Contractor shall provide a summary of its current program status to include highlights of the three (3) most recent Monthly Progress and Status Reports (CDRL A005). The Contractor shall lead the meeting, develop the agenda with the Government, and present the program status, and document those meetings. The PMR first occurrence shall address planning for the entire contract. The PMRs, which may be conducted via Defense Collaborative Services (DCS) or other Government-approved means, shall be documented with agendas (CDRL A010), meeting minutes (CDRL A011) and presentation materials (CDRL A012). Minutes of meetings are required for all meetings having a formal agenda.

The PMRs shall include the following:

a. Ensure a mutual understanding of the objectives and scope of the work.

b. LOE Tasks: Address Technical Instructions status in achieving technical, schedule and cost goals.

c. Completion Efforts: Address status in achieving technical, schedule and cost goals.

d. Review progress to-date relative to the established IMS and program baseline.

e. Review project deliverables.

f. Validate detailed work plans.

g. Confirm resolved issues and manage outstanding issues to include status of significant problems faced by the program manager and current plans to resolve the problems or mitigate their impacts.

h. Identify and evaluate risk factors and address areas where risk has changed.

i. Review metrics to include Earned Value (EV) performance, variances, and risk mitigation plans.

j. Identify cost and schedule variance in a combined manner by graphing the normalized cost and schedule variance together on an X-Y plot for all CWBS elements at the third indenture level. The presentation identifies with unique colors or shapes the data points considered “out of tolerance” per the cost reporting criteria.

k. Identify problems with GFI or Equipment, impacts, and workarounds or solutions.

l. Document and review all Action Items (AIs) from identification through closure.

Deliverable Data Item (See DD-1423):

a. A005, “Contractor’s Progress and Status Report; Monthly Progress and Status Report”

b. A010, “Conference Agenda”

c. A011, “Report, Record of Meeting/Minutes”

d. A012, “Presentation Material”

3.1.1.3.3 Technical Reviews

The Contractor shall ensure all Technical Reviews are scheduled in the IPMR IMS. The Contractor shall conduct Technical Reviews in coordination with PMRs or Interim Progress Reviews (IPRs), normally happening the day before a PMR and then on a periodic basis in-between the PMRs. The Contractor shall prepare all materials in support of the Technical Reviews in accordance with the PEO IWS TRM. For all formal reviews of technical packages or other Government review items, the Contractor shall upload all documents electronically into the

Navy Review Team (NRT) SharePoint website (independent if they are also submitted CDRLs into Corporate Document Management System (CDMS)). The Contractor shall ensure all Technical Review entrance, working and design artifacts are disclosed throughout their development via the NRT SharePoint website.