CREW_MEU_SOC_SOW_5_23_13_FINAL.pdf

CREW MEU (SOC) STATEMENT OF WORK Page i

1.0 Scope .................................................................................................................................... 1 2

1.1 Background ...................................................................................................................... 1 3

1.2 Program Description ........................................................................................................ 1 4

2.0 Applicable Documents ......................................................................................................... 1 5

2.1 CREW MEU(SOC) PSPEC ............................................................................................. 2 6

2.2 Military Standards, Specifications, and Handbooks ........................................................ 2 7

2.3 Department of Defense Regulations, Directives and Instructions ................................... 3 8

2.4 Other Government Guidance ........................................................................................... 3 9

2.5 Non-Government and Commercial Standards, Specification and Other Applicable 10

Publications ................................................................................................................................. 4 11

2.6 Definitions ........................................................................................................................ 4 12

2.6.1 Dismounted System ...................................................................................................... 5 13

2.6.2 Initial/Production Systems ............................................................................................ 5 14

3.0 CREW MEU(SOC) Requirements ...................................................................................... 5 15

3.1 Systems............................................................................................................................. 5 16

3.1.1 System Hardware, Software and Firmware .................................................................. 5 17

3.2 Program Management ...................................................................................................... 5 18

3.2.1 Schedule Management .................................................................................................. 5 19

3.2.2 Meetings ....................................................................................................................... 6 20

3.2.3 Integrated Product Team (IPT) ..................................................................................... 7 21

3.2.4 Data Management ......................................................................................................... 7 22

3.2.5 Risk and Opportunity Management .............................................................................. 8 23

3.3 System Engineering.......................................................................................................... 8 24

3.3.1 Engineering Support Services (ESS) ............................................................................ 9 25

3.3.2 Configuration Management .......................................................................................... 9 26

3.3.3 Software and Firmware .............................................................................................. 11 27

3.3.4 Human Systems Integration........................................................................................ 12 28

3.3.5 Environmental, Safety and Occupational Health ....................................................... 12 29

3.3.6 Failure Reporting, Analysis and Corrective Action System (FRACAS) ................... 13 30

3.3.7 Failure Modes, Effects, and Criticality Analysis ........................................................ 13 31

3.4 Test and Evaluation (T&E) ............................................................................................ 14 32

3.4.1 Factory Acceptance Testing ....................................................................................... 14 33

3.4.2 Government Acceptance Testing (GAT) .................................................................... 14 34

3.5 Production Planning/Readiness ...................................................................................... 16 35

CREW MEU (SOC) STATEMENT OF WORK Page ii

3.5.1 Manufacturing Readiness Assessment (MRA)........................................................... 17 36

3.5.2 Quality Management Planning ................................................................................... 17 37

3.5.3 Counterfeit Parts and Materials .................................................................................. 17 38

3.6 Supportability ................................................................................................................. 18 39

3.6.1 Levels of Maintenance ................................................................................................ 18 40

3.6.2 Obsolescence Management ........................................................................................ 19 41

3.6.3 Supply Support/Provisioning ...................................................................................... 19 42

3.6.4 Materials and Parts ..................................................................................................... 20 43

3.6.5 Technical Manuals ...................................................................................................... 20 44

3.6.6 Training Program ........................................................................................................ 21 45

3.6.7 Maintenance and Repair ............................................................................................. 23 46

3.6.8 Packaging, Handling, Storage and Transportation (PHS&T)..................................... 23 47

3.6.9 Support Equipment ..................................................................................................... 24 48

3.6.10 Government Furnished Equipment (GFE) ................................................................ 25 49

3.6.11 Maintainability Demonstration ................................................................................. 25 50

3.7 Program Protection Planning ......................................................................................... 26 51

3.7.1 System Security Engineering ...................................................................................... 26 52

3.7.2 Information Assurance ............................................................................................... 26 53

3.8 International Traffic In Arms ......................................................................................... 27 54

3.9 Contractor Security ........................................................................................................ 27 55

3.10 Technical Data Rights .................................................................................................... 27 56

M67854-13-R-2419

23 May 2013

Statement of Work for CREW MEU(SOC) 63

1.0 Scope 64

The United States Marine Corps (USMC) Counter Radio-Controlled Improvised Explosive 65

Device (RCIED) Electronic Warfare (CREW) Marine Expeditionary Unit (MEU) Special 66

Operations Capable (SOC) Program initiative, hereafter referred to as CREW MEU(SOC), 67 addresses urgent and compelling operational requirements to counter the threat posed by 68

RCIEDs. 69

1.1 Background 70

The CREW MEU(SOC) program addresses an urgent and compelling need for a capability to 71 counter the threat posed by Improvised Explosive Devices (IED)s. The CREW MEU(SOC) 72 systems will provide our fighting forces with an IED defeat capability, superior to the Counter 73

RCIED systems currently available, in an effort to defeat a constantly evolving threat. 74

1.2 Program Description 75

The CREW MEU(SOC) systems will operate worldwide, supporting United States (U.S.) 76

Forces’ dominance over the electromagnetic spectrum, and will not require new or unique 77 communication systems, but will operate within the bandwidth and quality of service of current 78 and future systems. The CREW MEU(SOC) systems will be capable of functioning in a stand-79 alone mode (as do legacy systems). 80

While there are several CREW system designs in various stages of development, production, 82 fielding, and sustainment, there is an urgent need to provide Marines protection from current and 83 emerging threats. The CREW MEU(SOC) program will use Non Developmental Item (NDI) 84 based Dismounted systems that are able to counter current and emerging threats. The specific 85 operational and technical requirements of the NDI based systems to be procured will be provided 86 throughout this Statement of Work (SOW) and the Performance Specification (PSPEC). 87

2.0 Applicable Documents 88

The Contractor shall utilize the revision effective as of the date of Request for Proposals (RFP) 89 release for each of the documents listed in the following subparagraphs and to the extent 90 specified in the requirements of this SOW. 91

Unless otherwise indicated, copies of federal and military specifications, standards, and 93 handbooks are available on the internet at the Department of Defense (DoD) Single Stock Point 94 at http://dodssp.daps.dla.mil. Joint Chief of Staff, DoD Directives (DoDD), DoD Instructions 95

(DoDI) and Publication documents can be found on http://www.dtic.mil/whs/directives. Non- 96

Government documents should be obtained from the commercial sources. 97

The specifications, standards, and handbooks listed form a part of this SOW to the extent cited 99 herein. All reference documents may be used for guidance unless otherwise specified within the 100 body of this SOW. Guidance documents may be used as an aid in identifying applicable topics 101 to be addressed consistent with meeting the requirements of the contract. The Contractor shall 102 http://dodssp.daps.dla.mil/ propose alternatives to the specifications and standards cited herein, if it would enhance system 103 performance or cost effectiveness, as necessary. 104

2.1 CREW MEU(SOC) PSPEC 105

Number Title and Revision Number Date Required or

Guidance

PMS 408 CREW MEU(SOC) Performance

Specification (PSPEC)

2 May 2013 Required

2.2 Military Standards, Specifications, and Handbooks 107

Number Title and Revision Number Date Required or

Guidance

MIL-HDBK-61A Configuration Management

Guidance

29 June 2007 Guidance

MIL-HDBK-470A

Designing and Developing

Maintainable Products and Systems, with Validation Notice 2, 31 May

04 August 1997 Guidance

MIL-HDBK-781A Reliability Test Methods, Plan and

Environments for Engineering, Development, Qualification and

Production Handbook

01 April 1996 Guidance

MIL-HDBK-2164A Environmental Stress Screening

Process for Electronic Equipment

19 June 1996 Guidance

MIL-HDBK-29612

Series

Guidance for Acquisition of

Training Data Products and Services

30 July 1999 Guidance

MIL-HDBK-29612-

2A

Department of Defense Handbook:

Instructional Systems

Development/Systems Approach to training and Education

31 August 2011 Guidance

MIL-PRF-29612B Training Data Products 31 August 2001 Guidance

MIL-STD-129P

w/Change 4

Military Marking for Shipment and

Storage

19 September

Required

MIL-STD-130N Identification Marking of U.S.

Military Property

17 December 2007 Required

MIL-STD-882E System Safety 11 May 2012 Required

MIL-STD-1472G Design Criteria Standard Human

Engineering

11 January 2012 Required

MIL-STD-2073-1E DoD Standard Practice for Military

Packaging with Change 1

07 January 2011 Required

MIL-DTL-

24784/4C

Commercial Off-The-Shelf (COTS)

Equipment Manual Requirements

03 November 2007 Required

2.3 Department of Defense Regulations, Directives and Instructions 109

Number Title and Revision Number Date Required or

Guidance

DoDD 1322.18 Military Training 13 January 2009 Required

DoDD 8500.1E Information Assurance 24 October 2010 Required

DoDD 8570.01-M Information Assurance Work Force

Improvement Program w/ Change 3

24 January 2012 Required

DoDI 5200.39 Critical Program Information (CPI)

Protection within the Department of

Defense

16 July 2008;

Change 1, 28

December 2010

Required

DoDI 8500.2 Information Assurance (IA)

Implementation

06 February 2003 Required

DoDI 8582.10 Security of Unclassified DoD

Information on Non-DoD

Information Systems

06 June 2012 Required

2.4 Other Government Guidance 111

Number Title and Revision Number Date

PMS 408 JCREW Configuration Management

Plan

September 2009

OPNAVINST

S5513.8B-88.1

JCREW Program Security Classification

Guide

02 April 2007

Version 1.1 PMS 408 Load Set Development Change 11 April 2011

DISA Security Technical Implementation Guides

(STIG)

- Information Assurance Vulnerability

Management (IAVM) 2012-

Benchmark Host Based Security

System [HBSS] only) Public Key

Infrastructure (PKI)

- Draft Traditional Security STIG

- IAVM to Common Vulnerabilities and

Exposures (CVE) Mapping

Spreadsheet

- Draft Application Server Security

Requirements Guide (SRG), Version 1, Release 0.2

- Mobile OS SRG, Version 1, Release 1

Various

DoD Manufacturing Readiness Level (MRL)

Deskbook Version 2.2

July 2012

MCO 1553.2B

Management of Marine Corps Formal Schools and Training Detachments

1 April 2011

Number Title and Revision Number Date

MCO 1553.3A Unit Training Management (UTM) 22 Jan 2004

TM 10510-OC/10 U.S. Marine Corps Technical Manual -

General Purpose Test Measurement and

Diagnostic Equipment (TMDE) Listing

(Including Ancillery Support Items and Tool

Kits)

January 2013

N/A USMC Test Set, Countermeasure Set (UTS)

Technical Manual

20 November 2010

N/A CVRJ ATE Product Description March 2013

2.5 Non-Government and Commercial Standards, Specification and Other 113

Applicable Publications 114

Number Title and Revision Number Date Required or

Guidance

ANSI/EIA-649-B National Consensus Standard For

Configuration Management

April 2011 Guidance

ASTM-D 3951-10 Standard Practice for Commercial

Packaging

15 August

Required

ANSI/ISO/ASQ Q9001-

Quality Management System

Standards

2008 Required

ASME Y14.100 Engineering Drawing Practices, Revision 04

2009 Required

ASME Y14.34M Parts List, Data Lists, and Index

Lists, Associated Lists, Revisions 96

January 2008 Required

ASME Y14.35M Revision of Engineering Drawings and Associated Documents, Revision

January 2008 Required

IEC 60812

ED.20 V: 2006

Analysis Techniques for Reliability –

Procedure for Failure Mode and

Effects Analysis (FMEA)

2006 Required

TA-STD-0017 Product Support Analysis 1 November

Guidance

GEIA-STD-0007, Rev A Logistics Product Data Reports 1 June 2010 Required

SAE AS5553 Counterfeit Electronic Parts;

Avoidance, Detection, Mitigation, and Disposition

02 April

Guidance

2.6 Definitions 116

The Contractor shall use the following definitions to ensure clarity during the contract period. 117

2.6.1 Dismounted System 118

A Dismounted system equates to a multi pack or single pack system solution, as defined in the 119

PSPEC. In addition to the receiver/transmitter, the system shall include, at a minimum, any 120 hardware, firmware, software, shipping/transit containers, batteries, battery case, and the load 121 carriage system for carrying the pack and all the components necessary to operate, and zeroize 122 the system to achieve the requirements defined in the PSPEC. Operator Manuals and QRGs are 123 included in the definition. 124

2.6.2 Initial/Production Systems 125

Initial systems are the first five (5) production systems to be used for Government Acceptance 126

Testing (GAT). All other systems are referred to as production systems. 127

3.0 CREW MEU(SOC) Requirements 128

3.1 Systems 129

3.1.1 System Hardware, Software and Firmware 130

The Contractor shall manufacture and deliver Dismounted systems to meet USMC’s urgent 131 requirement. The Contractor shall ensure CREW MEU(SOC) systems comply with all PSPEC 132 requirements. The Contractor shall provide an As Built Configuration List (ABCL)/Bill of 133

Materials (BOM) Lists which shall include necessary hardware and software from programming 134 the systems through mission execution, and data log transfer. Contractors shall provide a 135

ABCL/BOM Lists (A001) for each system delivered. Delivery of each system shall also include 136 one hard copy of the QRG and a Compact Disk - Read Only Memory (CD-ROM) copy of the 137

Operator’s Manual. Items shall include a standard commercial warranty. The Contractor shall 138 deliver an Interface Control Document (ICD) (A002). 139

3.2 Program Management 140

The Contractor shall establish and maintain a Program Management (PM) process that ensures 141 all work associated with this SOW is completed on time and meets all technical objectives within 142 the Government’s requirements. PM shall include appropriate metrics and tracking processes to 143 allow clear visibility into the program. The Contractor shall designate a Program Manager who 144 will be accountable and responsible for all work conducted within this contract and ensure that 145 all work is planned and executed in a manner that will achieve all management, technical, 146 logistics, financial and schedule requirements. The Contractor shall report current progress in a 147

Management Information System (MIS) Dashboard report (A003) using a graphic form by 148 comparison of their planned objectives for flow of data, materials and components into 149 manufacturer of end items as related to delivery requirements. 150

3.2.1 Schedule Management 151

The Contractor shall develop and maintain an Integrated Master Schedule (IMS) (A004) for 152 program control, status monitoring and reporting purposes necessary to successfully execute this 153 contract. The IMS shall include the efforts of all activities, including Contractor, key supplier, 154 and sub-Contractor, and present a current, integrated view of the contract schedule that is 155 consistent with resource plans and other approved documentation. The IMS shall be sufficiently 156 detailed such that critical and high-risk efforts are identified and planned as realistically as 157 possible to assure executability. 158

The IMS shall be structured by logically linking program activities, program milestones, planned 160 events, major tasks and efforts, including but not limited to Fabrication Schedule and Testing 161

Schedule from contract award to contract completion. The IMS shall be extended and expanded 162 as the contract progresses and when additional insight is needed. The Contractor shall notify the 163

PCO in writing within 72 hours of any anticipated or projected work stoppages or delays that 164 will impact the schedule five (5) working days or more. The Contractor shall provide work-165 around and/or recovery schedules/plans, and associated impacts due to schedule changes. 166

At a minimum, all monthly submissions shall include a written schedule analysis to identify, 168 document and communicate changes of five (5) working days or greater to: 169

Project Critical Path, 171

Next major schedule event, milestone or other tasks, and 172

Near Critical Path task/activity actual start and/or actual finish date variances (5 days 173 float). 174

The schedule narrative shall address progress to date and discuss any significant schedule 176 changes (e.g.: added/deleted tasks, any significant logic revisions and all programmatic schedule 177 assumption changes.) 178

3.2.2 Meetings 179

The Contractor shall coordinate, schedule, prepare, conduct, facilitate, and participate in reviews, 180 meetings, and conferences specified herein. Meetings may be enabled through the use of 181

Defense Connect Online (DCO) or Secure Video Teleconference Center (SVTC). The 182

Government reserves the right to attend meetings between the prime and sub-Contractors. The 183

Contractor shall provide presentation materials (A005). Read-ahead Contractor presentation 184 materials shall be delivered to the Government at least three (3) working days prior to all 185 meetings. The Contractor shall provide and agenda (A006) and minutes to support meetings 186

(A007). At a minimum, the Contractor shall support meetings identified within the following 187 paragraphs: 188

3.2.2.1 Post Award Kickoff Meeting 189

The Contractor shall provide for a one day classified and unclassified post award kickoff meeting 190 within two (2) weeks of contract award at the Contractor’s production facility. Additional 191 meeting spaces shall be made available to enable Classified or Unclassified follow-on 192 discussions. The Contractor shall provide a detailed briefing on their management and contract 193 execution strategy as well as their detailed program schedule. Additionally, special interest and 194 possibly classified topics incorporated into the CREW MEU(SOC) systems’ shall be briefed at 195 the kickoff meeting included but not limited to: 196

Program management approach, 198

Organizational structure, 199

Schedule, 200

System Design and Performance, 201

Past Testing/Results that demonstrate meeting PSPEC requirements, 202

RFD/RFW from PSPEC, 203

SSE/IA status, 204

Risk/Opportunity assessment, 205

Quality Management, 206

Production Readiness including Manufacturing Readiness, 207

Environmental, Safety and Occupational Health (ESOH) program and hazard status, 208

Human Systems Integration, 209

Built-In-Test (BIT) Capabilities, 210

Counterfeit Parts and Materials, 211

Supply Support/Provisioning, 212

Technical Manual and 213

Training. 214

3.2.2.2 Monthly Progress Meetings 215

The Contractor shall schedule monthly progress meetings with the Government to enable 216 deliverables on the contract and monitor progress. These can be conducted via teleconference, 217

DCO or SVTC. 218

3.2.2.3 Technical Interchange Meetings 219

Technical Interchange Meetings (TIMs) will be scheduled, as required by the Government 220

Integrated Product Team ((IPT) and/or Working Groups (WGs) to focus on specific 221 supportability and engineering discussions. TIMs may include topics such as interfaces, IA, 222

SSE, technical manuals, training materials, etc., during the execution of this contract. The 223

Contractor shall host a TIM for Special Security Engineering (SSE) within 60 days of contract 224 award. The Contractor shall be provided with not less than one (1) week advance notice of the 225 date of any planned TIM and shall provide necessary resources. TIMs may be conducted in 226 person, via DCO or SVTC. 227

3.2.3 Integrated Product Team (IPT) 228

The Contractor shall participate with the Government on IPTs and lower level WGs to ensure 229 integrated and coordinated work across all elements of the CREW MEU(SOC) program. The 230 functional areas for Acquisition Management, Production, Systems Engineering (SE), 231

Supportability, Test and Evaluation (T&E), Safety and Human Systems Integration (HSI) are 232 represented on Government IPTs. 233

3.2.4 Data Management 234

The Contractor shall use the Government furnished Integrated Data (Digital) Environment (IDE) 235

(to include Non-classified Internet Protocol Router (NIPR) or Secret Internet Protocol Router 236

(SIPR) or both) to document all aspects of the program, including the production drawings, 237 integration and test engineering efforts, the Contractor's SE efforts, integrated logistics support 238 efforts, and the Contractor's PM effort. Information concerning IDE use, file structure, and 239 access will be provided as GFI. Access to the IDE will require the issuance of DoD approved 240

Public Key Infrastructure (PKI) certificates. A maximum of three PKI certificates will be 241 allowed for each Contractor. The Government reserves the right to review all data associated 242 with the CREW MEU(SOC) systems. 243

3.2.5 Risk and Opportunity Management 244

The Contractor shall maintain a robust and proactive Risk/Opportunity Management program 245 and process that identifies and evaluates program risks and opportunities and executes 246 mitigation/capture strategies, as appropriate. All aspects of the program shall be assessed for 247 potential risk and opportunity including technical, environmental, safety, cost, and schedule 248 components. This process shall be institutionalized and work across the Contractor's entire IPT 249 structure. 250

3.2.5.1 Risks 251

Risks shall be evaluated as to their impact on Cost, Schedule, and Performance objectives. 252

Mitigation plans, that will reduce the risks to an acceptable management level, shall be put into 253 place for all risks assessed as either high or medium IAW the criteria contained in the Joint 254

CREW (JCREW) Increment 1, Block 1 (I1B1) Risk Management Plan provided as GFI. 255

Mitigation/burn down plans shall be managed and updated as contract performance proceeds and 256 shall be identifiable in the IMS. All risks shall be identified and reported to the Government in 257 the Contractor’s Progress, Status and Management Report (CPS&MR) (A008). 258

3.2.5.2 Opportunities 259

Opportunities shall be evaluated as to their potential to provide early deliveries or enhanced 260 technical performance. Capture plans shall be put into place for all opportunities assessed as 261 either high or medium. All Capture plans shall be analyzed to weigh the potential benefit against 262 the cost that would be incurred to ensure a positive outcome. Capture plans shall be managed 263 and updated as contract performance proceeds. All opportunities shall be identified and reported 264 to the Government in the monthly report as part of CDRL (A008). 265

3.3 System Engineering 266

The Contractor shall document, integrate, manufacture, and test CREW MEU(SOC) systems to 267 meet the PSPEC. The Contractor shall observe strict SE change management processes using 268

ANSI/EIA-649-B and MIL-HDBK-61A (SE) as guidance and shall document revisions to any 269 design documentation related to design baselines in the Baseline Description Document (BDD) 270

(A009). The Contractor shall maintain a Configuration Management (CM) process capable of 271 processing required configuration changes in a timeframe that enables identification, evaluation, 272 and implementation of proposed changes without impact to production schedules. Any changes 273 to the approved product baseline shall be processed IAW the PMS 408 CM Plan and the PMS 274

408 Load Set Development Change Process provided as GFI at contract award. 275

Any deviations, waivers, and engineering changes shall be defined via Requests for Deviations 277

(RFDs) (A010), Request for Waivers (RFWs) (A011), and Engineering Change Proposals 278

(ECPs) (A012) to the Government for review and approval. The Government is the 279 determination authority for execution of all Class I ECPs. A Class I ECP covers those changes 280 that affect form, fit, function, interfaces, production schedule, or logistics support. The 281

Contractor shall ensure the Government is informed of all Class II changes prior to 282 implementation, Notice of Revisions (A013). The product baseline is established by As Build 283

Configuration List (ABCL) (SOW paragraph 3.1.1) and Software Version Description (SVD) 284

(SOW paragraph 3.3.3) delivered with initial system tested by the government. 285

3.3.1 Engineering Support Services (ESS) 286

The Contractor shall provide technical and ESS on a fixed price basis as directed by Government 287 issued delivery order. In accordance with delivery order, the Contractor may be required to 288 provide the necessary personnel, equipment and facilities to execute tasks to include 289 troubleshooting of electronic/electrical hardware; generation of test, status, engineering cost 290 analysis, verification and validation of system operational specifications; sustainment 291 engineering; training; travel and field support. The task will be summarized in a technical report 292

(A014). The Contractor shall include the following in their CPS&MR (A008): 293

Summary of any issues encountered, 295

Estimate of percent complete, 296

Summary of work accomplished. 297

3.3.2 Configuration Management (CM) 298

The Contractor shall implement a Configuration Management program using ANSI/EIA-649-B 299 and MIL-HDBK-61A(SE) as guidance. The Contractor’s CM efforts shall include configuration 300 identification; configuration change control; hardware, software/firmware, and loadset CM, 301

Configuration Status Accounting (CSA); and configuration data management. The Contractor’s 302

CM approach shall ensure management, control, and execution of all CM necessary to control 303 the technical documents used to produce functional and physical characteristics of hardware, 304 firmware, and software. 305

The Contractor shall maintain a CM process capable of processing required configuration 307 changes in a timeframe that enables identification, evaluation, and implementation of proposed 308 changes without impact to production schedules. The Contractor shall be responsible for 309 ensuring that all Sub-Contractors also adhere to documented CM practices to ensure delivery of a 310 quality product to the Government. The Government shall be notified seven (7) working days in 311 advance and have the opportunity to participate in all Contractor Configuration Control Board 312

(CCCBs). 313

The Government has a requirement to ensure that the latest technology is available at the time of 315 order and subsequent delivery for the system. The Contractor shall implement program to 316 continually provide technology upgrades, technology refreshment, and/or technology insertion to 317 ensure that Contractor furnished subsystems, equipment, and software are not technologically 318 obsolete at delivery of the production unit. This is a requirement of all production lot units, but 319 changes shall be approved by the Government. Any technology upgrades or other changes shall 320 be incorporated into future systems 321

The Contractor shall provide any software changes, technical upgrades or version updates 323 produced after initial software introduction, and shall ensure those changes are installed in the 324 applicable system/equipment before delivery; those changes shall also be provided to the 325 government as a copy at delivery of the production units. These changes shall also be reflected 326 in the applicable documentation or manual that documents the baseline configuration and 327 subsequent changes and provided to the Government as updated TDP or manuals. Technology 328 considered to be obsolete shall be replaced by the Contractor with current technology if any one 329 of the following criteria is met: 330

Products not in production or expected to be phased out of production by the original 332 equipment manufacturer within two years following production unit delivery. 333

Products no longer commercially supported or any component without a supplier 334 documented plan to support for ten years following production unit delivery. 335

Products whose maintenance costs exceed replacement costs with current technology. 336

The Contractor shall ensure that enhancements incorporated do not degrade performance. For 338 enhancement items that will potentially increase the cost of contract performance, removal of 339 technically antiquated or unsupported equipment and replacement with technically superior 340 equipment shall not occur without prior Government approval via an ECP (A012). 341

Additionally, for any changes in technology or enhancement will require units to undergo testing 343 to ensure that they meet the requirements of the contract, the contractor shall be responsible for 344 the costs of the testing to be accomplished. 345

3.3.2.1 Contractor Configuration Control Board (CCCB) 346

The Government will have approval of all Class I changes from the approved Product Baseline 347 for the CREW MEU(SOC) systems. The product baseline is established by the ABCL and SVD 348 delivered to the Government with the Initial systems. The CCCB is formed to review 349

Engineering Change Proposals (ECPs) and make a recommendation to approve or not approve 350 the proposed change. Members advise and recommend, but the authority for Class I changes 351 rests with the Government. The CCCB membership shall represent the user (Government 352

[observer or member]) and the six primary functions; Procurement, Logistics which includes 353

Training and Maintenance, SE, Program Control (Budget), Test and Evaluation, Safety, as well 354 as Configuration Control, who serves as the CCCB secretariat. 355

3.3.2.2 Reviews and Audits 356

The Contractor shall support the Government in conducting reviews and audits. Support shall 357 include providing technical documentation, equipment, facilities and services, including 358 disassembly and reassembly of systems. The Contractor shall respond to findings, recommend 359 corrective actions, and resolve all deficiencies identified during these reviews and audits. 360

3.3.2.2.1 Physical Configuration Audit 361

Under the production delivery order(s) the Contractor shall be prepared to assist and participate 362 in the Government Physical Configuration Audit (PCA) to be conducted on production systems. 363

Guidelines are contained in MIL-HDBK-61A, Section 8. The objective and purpose of the PCA 364 is to examine the actual configuration of the CREW MEU(SOC) systems being produced in 365 order to verify that the related design documentation matches the item as specified in the 366 contract. In addition to the standard practice of assuring product verification, the PCA confirms 367 that the Contractor’s manufacturing processes, quality control system, measurement and test 368 equipment, and training are adequately planned, followed, and controlled (A015). Entrance 369

Criteria for the PCA is as follows: 370

Audit Plan and agenda, 372

Specifications have been completed, and 373

All required documentation has been baselined. 374

Exit Criteria for the PCA is as follows: 376

The design and manufacturing documentation match the item as specified in the contract, 378

All action items, critical RFAs, and non-critical RFAs captured and agreed upon with a 379 plan for resolution, 380

Any changes to architecture products have been reviewed and, where appropriate, 381 approved, 382

Physical CIs meet product specifications, and 383

Performing activities demonstrate that SE, production, test and logistics processes 384 conform with SE, production, test and logistics documentation (respectively). 385

3.3.3 Software and Firmware 386

The Contractor shall deliver a Software Version Description Document (SVD) (A016) for 387 software and software/firmware products. The SVD will be used to establish maintain the 388 product baseline for all software. Additional software/firmware deliverables and associated 389

Contract Data Requirements List (CDRL) (in parentheses) are: 390

Threatloads (Human Readable Materials [A017]) 392

Software/Firmware Updates for receiver/transmitter 393

Threatload Loading Application – Graphical User Interface (GUI) Software Users 394

Manual (SUM) (A018) 395

Threatload Developer Tool – GUI SUM (A018) 396

The Contractor shall deliver software (GUI/application/software package) that represents the 398 software documentation, and is software configuration on a CD-ROM, labeled with appropriate 399 system software name, version ID, and classification. 400

The SVD shall detail all operating systems with their associated kernel version, configuration, 402 operational libraries, and firmware. The SVD shall also include a description of changes from 403 the previous software/firmware baseline and essential work-around for known deficiencies. The 404

SVD shall identify all targeted hardware with descriptions of unique configurations if required. 405

In addition, the SVD shall include applicable software and firmware installation procedures. The 406

SVD shall also list load set files that are compatible with the software/firmware release. 407

The Contractor shall deliver two Software User’s Manuals (SUM) (A018). A Threatload 409

Loading Application SUM that provides detailed instructions for a system user to install/update 410 software and operate the system. A Threatload Developer Tool 411

SUM shall also provide user instructions for updating and configuring “load sets” and restoring a 412 system after being zeroized. 413

The Contractor shall provide one threat load for the initial systems which provides the necessary 415 threat coverage and in accordance with the PSPEC, and restricted range frequencies. This shall 416 also include, if required, system software and firmware changes to support all techniques to meet 417 the PSPEC including the threat load priority list (A017). The Contractor shall also provide a 418 human readable version of the threat load with a Threat Load Development Software Tool such 419 as a GUI. The Contractor shall deliver the threat load development software and programming 420 tool. The Contractor shall be required to deliver up to four additional threat loads per year for 421 the period of performance of the contract based on updated threat lists. 422

3.3.4 Human Systems Integration 424

The Contractor shall have a Human Systems Integration (HSI) program that is IAW MIL-STD-425

1472G, Department of Defense Design Criteria Standard Human Engineering and the PSPEC. 426

The Contractor’s HSI program shall identify and document all tasks for Operators, Maintainers 427 and Support Personnel within the Human Engineering Systems Analysis Report (HESAR) 428

(A019), developed from the top down functional analysis. The HSI program shall be briefed 429 during the Post Award Kickoff Meeting. 430

3.3.5 Environmental, Safety and Occupational Health 431

The Contractor shall ensure the CREW MEU(SOC) system manufacturing, production, 432 demilitarization, and disposal complies with all applicable local, state, federal, and international 433 environmental protection laws, regulations, treaties, and agreements for the period of 434 performance of this contract, as well as IAW the PSPEC. The Contractor shall define its system 435 safety program which identifies and evaluates safety and health hazards, define risk levels, and 436 establish a safety program that manages the probability and severity of all hazards associated 437 with development, use, and disposal of the system IAW MIL-STD-882E. This shall include the 438 identification of hardware and software related hazards and recommended mitigations to 439 eliminate or reduce the hazards to a level acceptable to the Government. 440

The Contractor shall make recommendations to hazards with the interface of this system with 442 other systems, as contractually required. The Contractor shall identify health hazards, evaluate 443 proposed hazardous materials, and propose protective measures to reduce the associated risk to a 444 level acceptable by the Government. This information will be provided by the Contractor in a 445

Safety Assessment Report (SAR) that shall include a signed statement that all identified hazards 446 have been eliminated or associated risks controlled to acceptable levels and that the system is 447 ready to test, field, or operate. The Contractor shall provide Material Safety Data Sheets 448

(MSDSs) as part of the SAR (A020). 449

3.3.6 Failure Reporting, Analysis and Corrective Action System (FRACAS) 450

The Contractor shall conduct FRACAS in accordance with the Contractor’s internal FRACAS. 451

The Contractor’s FRACAS shall include a closed loop failure reporting system, procedures for 452 analysis of failures to determine cause, and documentation for recording corrective actions taken. 453

All hardware/software failures from system level down to the component level shall be subject to 454 these requirements. The Contractor shall notify the Government within 24 hours and document 455 in the IDE any critical failure, which impacts cost, schedule, producibility, interface, 456 performance, or safety. Failures, which are not defined as critical, be documented and reported 457 in the Government progress meetings reported in the CPS&M Report (A008), and the Contractor 458 shall conduct and submit a Failure Analysis and Corrective Action Report (FACAR) (A021). 459

During GAT, failures, built-in test (BIT) anomalies (e.g., BIT failure to detect, BIT failure to 461 isolate properly, and BIT false alarms), or non-conformances experienced from the end item 462 level (Lowest Replaceable Unit [LRU] or lower) through the system level shall be subjected to 463 the Contractor’s FRACAS. The Contractor shall perform failure analyses on all reported 464 failures and BIT anomalies to the level required to determine the cause of failure, define the 465 failure mechanism, and develop corrective actions to eliminate or limit their recurrence. The 466

Contractor shall document all failures, BIT anomalies, analysis and corrective actions via the 467

FACAR. 468

Corrective actions must meet the following criteria: 470

Be established (analytically or by test) as an effective corrective action to the satisfaction 472 of the program office, and 473

Be scheduled for incorporation into production equipment via official change controls, as 474 approved by the program office. 475

3.3.6.1 Failure Review Board (FRB) 476

The Contractor shall conduct a FRB IAW the Contractor’s approved FRACAS Plan and 477

Procedures. The Government shall be invited to participate as an active member of the FRB. 478

The program office shall be notified of the FRB meeting dates at least 10 working days in 479 advance. The FRB shall meet as often as necessary. However, the FRB shall not meet less 480 frequently than monthly during any period when open failure reports exist. 481

3.3.7 Failure Modes, Effects, and Criticality Analysis 482

The Contractor shall deliver a Failure Modes, Effects, and Criticality Analyses (FMECA) (A022) 483 to address all failure modes in the CREW MEU(SOC) systems. The FMECA shall reflect the 484 baseline design IAW Analysis Techniques for Reliability – Procedure for Failure Mode and 485

Effects Analysis (FMEA), IEC 60812 ED.20 V: 2006. The FMECA shall clearly identify those 486 failure modes which are detectable by BIT. 487

3.4 Test and Evaluation (T&E) 488

The Contractor shall perform Factory Acceptance Testing on all systems and shall subject any 489 and all failures to FRACAS as identified above. For the initial systems, the systems must pass 490

Factory Acceptance Testing, and will then be shipped in place for those portions of GAT that are 491 to be performed at the Contractor facility. Government personnel will witness the GAT events 492 performed at the Contractor facility. Data collection will be performed by Contractor and 493

Government personnel. Once this portion of GAT has been successfully completed, the systems 494 will then be shipped to the Government testing facilities for the remainder of GAT. 495

3.4.1 Factory Acceptance Testing 496

All systems shall undergo Factory Acceptance Testing, The Contractor shall conduct Factory 497

Acceptance Testing on all systems to validate that the systems are of high quality, free of defects, 498 are operational upon delivery, and that the system performance meets or exceeds that proposed 499 via the Contractor’s proposal (as incorporated into the contract) and demonstrated during the 500

GAT. The Contractor shall submit for approval a Factory Acceptance Test Plan (A023) and 501 procedures that will be used to evaluate the system performance and manufacturing procedures 502 for meeting the PSPEC and contract requirements. 503

The Contractor shall notify the Contracting Officer Representative (COR) ten (10) days prior to 505 acceptance testing of each production lot. The COR or his/her representative may witness the 506 final acceptance testing. However, the Contractor need not delay testing to allow COR 507 attendance. 508

The Contractor shall conduct Factory Acceptance Testing at the Contractor’s facility to 510 maximize the use of bench and subsystem testing. Factory Acceptance Testing shall not include 511 range testing. The Contractor is responsible for establishing a production schedule and 512 conducting sufficient subsystem and component testing to ensure that the final production 513 systems achieve the required quality and performance levels. Acceptance testing plans and 514 procedures should include, at a minimum, the ability of CREW MEU(SOC) systems to comply 515 with the requirements indicated for contract verification in the PSPEC. The Contractor shall 516 submit a Factory Acceptance Test Report (A024) at the conclusion of Factory Acceptance Test. 517

3.4.2 Government Acceptance Testing (GAT) 518

Government Acceptance Testing (GAT) is a series of tests performed on the initial systems, 519 which when complete and approved, demonstrates that the Contractor can furnish a product that 520 conforms to all contract requirements. Proposed performance levels will become the contract 521 threshold levels, if they are above Government threshold values. 522

The Contractor shall deliver a Government Acceptance Test Plan (A025) and Test Report 524

(A026) for verification of those PSPEC items as listed as Contractor in Section 4, Verification, 525

Table 3, Requirement Verification Cross Reference Matrix in the PSPEC. The Contractor shall 526 be prepared to execute the GAT at their facility 90 days after contract award. Systems must pass 527

GAT for the Contractor to proceed to competition for further production systems. Within 180 528 calendar days after the Government receives the initial systems, the Contracting Officer shall 529 notify the Contractor, in writing, of the results of GAT. A notice of failure shall cite reasons for 530 the failures, and further instruction if needed. 531

If an initial system fails a GAT, the Contractor shall subject all failures to the Contractor’s 533

FRACAS process and make any necessary changes, modifications, or repairs to the system and 534 deliver it to the Government or deliver another system for testing. All costs related to these tests 535 are to be borne by the Contractor, including any and all costs for additional tests following a 536 disapproval. The Contractor shall furnish any additional units to the Government under the terms 537 and conditions and within the time specified by the Government. 538

The Contractor is responsible for providing operating and maintenance instruction, spare parts, 540 support, and repair of the initial systems during any GAT. Any system hardware failures shall be 541 remedied within 24 hours for all locations where on-site support is provided by the Contractor. 542

Contractor on-site support is not required at NSWC Dahlgren and 72 hours is allowed to remedy 543 failures at this location. 544

If the Contractor fails to deliver systems meeting all contractual requirements, the Contractor 546 shall be deemed to have failed to make delivery within the meaning of the Default clause of this 547 contract. 548

3.4.2.1 Test Readiness Review (TRR) 549

The Contractor shall participate in Government led Test Readiness Reviews (TRR) to determine 550 the readiness of the initial systems and the Contractor to begin GAT. The TRRs may be held 551 remotely via DCO. 552

To support GAT, Contractors shall submit the Application for Equipment Frequency Allocation 554

Data, (A027) DD Form 1494 supporting Spectrum Certification activities. The Contractor shall 555 submit DD1494-1 through DD1494-4 in order to obtain Electronic Attack (EA) Clearance to 556 perform GAT. 557

To aid in Safety Assessments prior to GAT, the Contractor shall submit a Safety Assessment 559

Report (SAR) (A020). The SAR should include a systems description and unclassified photos of 560 the system. The SAR shall be unclassified unless classified information must be included. In 561 this instance, the classified information shall be included in a classified annex. 562

Should the Contractor fail to meet the requirements necessary to proceed to GAT at the TRR, the 564

Contractor will be given 48 hours to gather and/or resolve any issues. 565

3.4.2.1.1 Entrance and Exit Criteria 566

The entrance criterion includes the Government approval of the following data items: 567

Test Plans for Factory Acceptance Testing (A023), 569

Test Event Data and Test Results/Reports for Factory Acceptance Testing (A024), 570

Test Plans for GAT events to be performed at the Contractor site (A025), 571

ABCL (A001), 572

SVD (A016), 573

Frequency Allocation Data 1494 (A027), and 574

SAR (A020). 575

The GAT TRR Exit criteria will be satisfied when all TRR action items have been closed. 577

3.4.2.2 GAT to be Performed at the Contractor Facility 578

Government personnel will witness the GAT events performed at the Contractor facility. Testing 579 will be performed by the Contractor. Data collection will be performed by Contractor and 580

Government personnel. 581

3.4.2.3 GAT Performed at Government Facilities 582

Government testing will be conducted at four test sites, NSWC Crane, NSWC Dahlgren, San 583

Antonio (for dismounted systems), and Yuma Proving Grounds (YPG), as indicated in PSPEC. 584

The Contractor shall provide on-site support for the testing at NSWC Crane. The Contractor 585 shall estimate one (1) person for one (1) week for support at NSWC Crane. The Contractor shall 586 provide on-site support for the testing at YPG. The Contractor shall estimate one (1) person for 587 three (3) weeks support at YPG. Contractors shall provide on-site support for the Dismounted 588 system for HERx testing at San Antonio. The Contractor shall estimate one (1) person for one 589

(1) week support at San Antonio. The Contractor shall also provide necessary training, spares 590 and all ancillary equipment to operate and maintain the systems during onsite support and 591 testing. The contactor is not required to provide on-site support at NSWC Dahlgren.. 592

3.4.2.3.1 Dismounted Field User Evaluation 593

The Dismounted Field User Evaluation is a part of GAT and the tasks to be evaluated include the 594 following: 595

Move across uneven terrain while carrying mission essential equipment, 597

Climb over walls, 598

Ingress and egress military aircraft and vehicles; transportation within (V-22, CH-46, 599

AAV, MTVR, and LAV), 600

Crawl through small domicile, (low door ), openings/tunnels/culverts, 601

Move through woodland and jungle vegetation, 602

Jump across ditches, 603

Cross water obstacles by…