SOW_M67854-13-R-2419_26Jun_2013.docx

M67854-13-R-2419

25 June 2013

CREW MEU (SOC) DISMOUNTED SOW Page ii

Statement of Work for CREW MEU(SOC) DISMOUNTED

1. Scope The United States Marine Corps (USMC) Counter Radio-Controlled Improvised Explosive Device (RCIED) Electronic Warfare (CREW) Marine Expeditionary Unit (MEU) Special Operations Capable (SOC) Program initiative, hereafter referred to as CREW MEU(SOC), addresses urgent and compelling operational requirements to counter the threat posed by RCIEDs.

Background The CREW MEU(SOC) program addresses an urgent and compelling need for a capability to counter the threat posed by Improvised Explosive Devices (IED)s. The CREW MEU(SOC) systems will provide our fighting forces with an IED defeat capability, superior to the Counter RCIED systems currently available, in an effort to defeat a constantly evolving threat.

Program Description The CREW MEU(SOC) systems will operate worldwide, supporting United States (U.S.) Forces’ dominance over the electromagnetic spectrum, and will not require new or unique communication systems, but will operate within the bandwidth and quality of service of current and future systems. The CREW MEU(SOC) systems will be capable of functioning in a stand-alone mode (as do legacy systems).

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

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

Unless otherwise indicated, copies of federal and military specifications, standards, and handbooks are available on the internet at the Department of Defense (DoD) Single Stock Point at http://dodssp.daps.dla.mil. Joint Chief of Staff, DoD Directives (DoDD), DoD Instructions (DoDI) and Publication documents can be found on http://www.dtic.mil/whs/directives. Non- Government documents should be obtained from the commercial sources.

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

CREW MEU(SOC) PSPEC

Military Standards, Specifications, and Handbooks

Department of Defense Regulations, Directives and Instructions

Change 1, 28 December 2010 Required

Other Government Guidance

· 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

MCO 1553.2B

Non-Government and Commercial Standards, Specification and Other Applicable Publications

IEC 60812

ED.20 V: 2006

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

Dismounted System A Dismounted system equates to a multi pack or single pack system solution, as defined in the PSPEC. In addition to the receiver/transmitter, the system shall include, at a minimum, any hardware, firmware, software, shipping/transit containers, batteries, battery case, and the load carriage system for carrying the pack and all the components necessary to operate, and zeroize the system to achieve the requirements defined in the PSPEC. Operator Manuals and QRGs are included in the definition.

Initial/Production Systems Initial systems are the first five (5) production systems to be used for Government Acceptance Testing (GAT). All other systems are referred to as production systems.

CREW MEU(SOC) Requirements Systems System Hardware, Software and Firmware The Contractor shall manufacture and deliver Dismounted systems to meet USMC’s urgent requirement. The Contractor shall ensure CREW MEU(SOC) systems comply with all PSPEC requirements. The Contractor shall provide an As Built Configuration List (ABCL)/Bill of Materials (BOM) Lists which shall include necessary hardware and software from programming the systems through mission execution, and data log transfer. Contractors shall provide a ABCL/BOM Lists (A001) for each system delivered. Delivery of each system shall also include one hard copy of the QRG and a Compact Disk - Read Only Memory (CD-ROM) copy of the Operator’s Manual. Items shall include a standard commercial warranty. The Contractor shall deliver an Interface Control Document (ICD) (A002).

Program Management The Contractor shall establish and maintain a Program Management (PM) process that ensures all work associated with this SOW is completed on time and meets all technical objectives within the Government’s requirements. PM shall include appropriate metrics and tracking processes to allow clear visibility into the program. The Contractor shall designate a Program Manager who will be accountable and responsible for all work conducted within this contract and ensure that all work is planned and executed in a manner that will achieve all management, technical, logistics, financial and schedule requirements. The Contractor shall report current progress in a Management Information System (MIS) Dashboard report (A003) using a graphic form by comparison of their planned objectives for flow of data, materials and components into manufacturer of end items as related to delivery requirements.

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

The IMS shall be structured by logically linking program activities, program milestones, planned events, major tasks and efforts, including but not limited to Fabrication Schedule and Testing Schedule from contract award to contract completion. The IMS shall be extended and expanded as the contract progresses and when additional insight is needed. The Contractor shall notify the PCO in writing within 72 hours of any anticipated or projected work stoppages or delays that will impact the schedule five (5) working days or more. The Contractor shall provide work-around and/or recovery schedules/plans, and associated impacts due to schedule changes.

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

· Project Critical Path,

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

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

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

Meetings The Contractor shall coordinate, schedule, prepare, conduct, facilitate, and participate in reviews, meetings, and conferences specified herein. Meetings may be enabled through the use of Defense Connect Online (DCO) or Secure Video Teleconference Center (SVTC). The Government reserves the right to attend meetings between the prime and sub-Contractors. The Contractor shall provide presentation materials (A005). Read-ahead Contractor presentation materials shall be delivered to the Government at least three (3) working days prior to all meetings. The Contractor shall provide and agenda (A006) and minutes to support meetings (A007). At a minimum, the Contractor shall support meetings identified within the following paragraphs:

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

· Program management approach,

· Organizational structure,

· Schedule,

· System Design and Performance,

· Past Testing/Results that demonstrate meeting PSPEC requirements,

· RFD/RFW from PSPEC,

· SSE/IA status,

· Risk/Opportunity assessment,

· Quality Management,

· Production Readiness including Manufacturing Readiness,

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

· Human Systems Integration,

· Built-In-Test (BIT) Capabilities,

· Counterfeit Parts and Materials,

· Supply Support/Provisioning,

· Technical Manual and

· Training.

Monthly Progress Meetings The Contractor shall schedule monthly progress meetings with the Government to enable deliverables on the contract and monitor progress. These can be conducted via teleconference, DCO or SVTC.

Technical Interchange Meetings Technical Interchange Meetings (TIMs) will be scheduled, as required by the Government Integrated Product Team ((IPT) and/or Working Groups (WGs) to focus on specific supportability and engineering discussions. TIMs may include topics such as interfaces, IA, SSE, technical manuals, training materials, etc., during the execution of this contract. The Contractor shall host a TIM for Special Security Engineering (SSE) within 60 days of contract award. The Contractor shall be provided with not less than one (1) week advance notice of the date of any planned TIM and shall provide necessary resources. TIMs may be conducted in person, via DCO or SVTC.

Integrated Product Team (IPT) The Contractor shall participate with the Government on IPTs and lower level WGs to ensure integrated and coordinated work across all elements of the CREW MEU(SOC) program. The functional areas for Acquisition Management, Production, Systems Engineering (SE), Supportability, Test and Evaluation (T&E), Safety and Human Systems Integration (HSI) are represented on Government IPTs.

Data Management The Contractor shall use the Government furnished Integrated Data (Digital) Environment (IDE) (to include Non-classified Internet Protocol Router (NIPR) or Secret Internet Protocol Router (SIPR) or both) to document all aspects of the program, including the production drawings, integration and test engineering efforts, the Contractor's SE efforts, integrated logistics support efforts, and the Contractor's PM effort. Information concerning IDE use, file structure, and access will be provided as GFI. Access to the IDE will require the issuance of DoD approved Public Key Infrastructure (PKI) certificates. A maximum of three PKI certificates will be allowed for each Contractor. The Government reserves the right to review all data associated with the CREW MEU(SOC) systems.

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

Risks Risks shall be evaluated as to their impact on Cost, Schedule, and Performance objectives. Mitigation plans, that will reduce the risks to an acceptable management level, shall be put into place for all risks assessed as either high or medium IAW the criteria contained in the Joint CREW (JCREW) MEU (SOC) Risk Criteria, provided as GFI. Mitigation/burn down plans shall be managed and updated as contract performance proceeds and shall be identifiable in the IMS. All risks shall be identified and reported to the Government in the Contractor’s Progress, Status and Management Report (CPS&MR) (A008).

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

System Engineering The Contractor shall document, integrate, manufacture, and test CREW MEU(SOC) systems to meet the PSPEC. The Contractor shall observe strict SE change management processes using ANSI/EIA-649-B and MIL-HDBK-61A (SE) as guidance and shall document revisions to any design documentation related to design baselines in the Baseline Description Document (BDD) (A009). The Contractor shall maintain a Configuration Management (CM) process capable of processing required configuration changes in a timeframe that enables identification, evaluation, and implementation of proposed changes without impact to production schedules. Any changes to the approved product baseline shall be processed IAW the PMS 408 CM Plan and the PMS 408 Load Set Development Change Process provided as GFI at contract award.

Any deviations, waivers, and engineering changes shall be defined via Requests for Deviations (RFDs) (A010), Request for Waivers (RFWs) (A011), and Engineering Change Proposals (ECPs) (A012) to the Government for review and approval. The Government is the determination authority for execution of all Class I ECPs. A Class I ECP covers those changes that affect form, fit, function, interfaces, production schedule, or logistics support. The Contractor shall ensure the Government is informed of all Class II changes prior to implementation, Notice of Revisions (A013). The product baseline is established by As Build Configuration List (ABCL) (A001) (SOW paragraph 3.1.1) and Software Version Description (SVD) (A016) (SOW paragraph 3.3.3) delivered with initial system tested by the government.

Engineering Support Services (ESS) The Contractor shall provide technical and ESS on a fixed price basis as directed by Government issued delivery order. In accordance with delivery order, the Contractor may be required to provide the necessary personnel, equipment and facilities to execute tasks to include troubleshooting of electronic/electrical hardware; generation of test, status, engineering cost analysis, verification and validation of system operational specifications; sustainment engineering; training; travel and field support. The task will be summarized in a technical report (A014). The Contractor shall include the following in their CPS&MR (A008):

· Summary of any issues encountered,

· Estimate of percent complete,

· Summary of work accomplished.

Configuration Management (CM) The Contractor shall implement a Configuration Management program using ANSI/EIA-649-B and MIL-HDBK-61A(SE) as guidance. The Contractor’s CM efforts shall include configuration identification; configuration change control; hardware, software/firmware, and loadset CM, Configuration Status Accounting (CSA); and configuration data management. The Contractor’s CM approach shall ensure management, control, and execution of all CM necessary to control the technical documents used to produce functional and physical characteristics of hardware, firmware, and software.

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

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

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

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

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

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

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

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

Contractor Configuration Control Board (CCCB) The Government will have approval of all Class I changes from the approved Product Baseline for the CREW MEU(SOC) systems. The product baseline is established by the ABCL and SVD delivered to the Government with the Initial systems. The CCCB is formed to review Engineering Change Proposals (ECPs) and make a recommendation to approve or not approve the proposed change. Members advise and recommend, but the authority for Class I changes rests with the Government. The CCCB membership shall represent the user (Government [observer or member]) and the six primary functions; Procurement, Logistics which includes Training and Maintenance, SE, Program Control (Budget), Test and Evaluation, Safety, as well as Configuration Control, who serves as the CCCB secretariat.

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

Physical Configuration Audit Under the production delivery order(s) the Contractor shall be prepared to assist and participate in the Government Physical Configuration Audit (PCA) to be conducted on production systems. Guidelines are contained in MIL-HDBK-61A, Section 8. The objective and purpose of the PCA is to examine the actual configuration of the CREW MEU(SOC) systems being produced in order to verify that the related design documentation matches the item as specified in the contract. In addition to the standard practice of assuring product verification, the PCA confirms that the Contractor’s manufacturing processes, quality control system, measurement and test equipment, and training are adequately planned, followed, and controlled (A015). Entrance Criteria for the PCA is as follows:

· Audit Plan and agenda,

· Specifications have been completed, and

· All required documentation has been baselined.

Exit Criteria for the PCA is as follows:

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

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

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

· Physical CIs meet product specifications, and

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

Software and Firmware The Contractor shall deliver a Software Version Description Document (SVD) (A016) for software and software/firmware products. The SVD will be used to establish maintain the product baseline for all software. Additional software/firmware deliverables and associated Contract Data Requirements List (CDRL) (in parentheses) are:

· Threatloads (Human Readable Materials [A017])

· Software/Firmware Updates for receiver/transmitter

· Threatload Loading Application – Graphical User Interface (GUI) Software Users Manual (SUM) (A018)

· Threatload Developer Tool – GUI SUM (A018)

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

The SVD shall detail all operating systems with their associated kernel version, configuration, operational libraries, and firmware. The SVD shall also include a description of changes from the previous software/firmware baseline and essential work-around for known deficiencies. The SVD shall identify all targeted hardware with descriptions of unique configurations if required. In addition, the SVD shall include applicable software and firmware installation procedures. The SVD shall also list load set files that are compatible with the software/firmware release.

The Contractor shall deliver two Software User’s Manuals (SUM) (A018). A Threatload Loading Application SUM that provides detailed instructions for a system user to install/update software and operate the system. A Threatload Developer Tool SUM shall also provide user instructions for updating and configuring “load sets” and restoring a system after being zeroized.

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

Human Systems Integration The Contractor shall have a Human Systems Integration (HSI) program that is IAW MIL-STD-1472G, Department of Defense Design Criteria Standard Human Engineering and the PSPEC. The Contractor’s HSI program shall identify and document all tasks for Operators, Maintainers and Support Personnel within the Human Engineering Systems Analysis Report (HESAR) (A019), developed from the top down functional analysis. The HSI program shall be briefed during the Post Award Kickoff Meeting.

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

The Contractor shall make recommendations to hazards with the interface of this system with other systems, as contractually required. The Contractor shall identify health hazards, evaluate proposed hazardous materials, and propose protective measures to reduce the associated risk to a level acceptable by the Government. This information will be provided by the Contractor in a Safety Assessment Report (SAR) that shall include a signed statement that all identified hazards have been eliminated or associated risks controlled to acceptable levels and that the system is ready to test, field, or operate. The Contractor shall provide Material Safety Data Sheets (MSDSs) as part of the SAR (A020).

Failure Reporting, Analysis and Corrective Action System (FRACAS) The Contractor shall conduct FRACAS in accordance with the Contractor’s internal FRACAS. The Contractor’s FRACAS shall include a closed loop failure reporting system, procedures for analysis of failures to determine cause, and documentation for recording corrective actions taken. All hardware/software failures from system level down to the component level shall be subject to these requirements. The Contractor shall notify the Government within 24 hours and document in the IDE any critical failure, which impacts cost, schedule, producibility, interface, performance, or safety. Failures, which are not defined as critical, be documented and reported in the Government progress meetings reported in the CPS&M Report (A008), and the Contractor shall conduct and submit a Failure Analysis and Corrective Action Report (FACAR) (A021).

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

Corrective actions must meet the following criteria:

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

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

Failure Review Board (FRB) The Contractor shall conduct a FRB IAW the Contractor’s approved FRACAS Plan and Procedures. The Government shall be invited to participate as an active member of the FRB. The program office shall be notified of the FRB meeting dates at least 10 working days in advance. The FRB shall meet as often as necessary. However, the FRB shall not meet less frequently than monthly during any period when open failure reports exist.

Failure Modes, Effects, and Criticality Analysis The Contractor shall deliver a Failure Modes, Effects, and Criticality Analyses (FMECA) (A022) to address all failure modes in the CREW MEU(SOC) systems. The FMECA shall reflect the baseline design IAW Analysis Techniques for Reliability – Procedure for Failure Mode and Effects Analysis (FMEA), IEC 60812 ED.20 V: 2006. The FMECA shall clearly identify those failure modes which are detectable by BIT.

Test and Evaluation (T&E) The Contractor shall perform Factory Acceptance Testing on all systems and shall subject any and all failures to FRACAS as identified above. For the initial systems, the systems must pass Factory Acceptance Testing, and will then be shipped in place for those portions of GAT that are to be performed at the Contractor facility. Government personnel will witness the GAT events performed at the Contractor facility. Data collection will be performed by Contractor and Government personnel. Once this portion of GAT has been successfully completed, the systems will then be shipped to the Government testing facilities for the remainder of GAT.

Factory Acceptance Testing All systems shall undergo Factory Acceptance Testing, The Contractor shall conduct Factory Acceptance Testing on all systems to validate that the systems are of high quality, free of defects, are operational upon delivery, and that the system performance meets or exceeds that proposed via the Contractor’s proposal (as incorporated into the contract) and demonstrated during the GAT. The Contractor shall submit for approval a Factory Acceptance Test Plan (A023) and procedures that will be used to evaluate the system performance and manufacturing procedures for meeting the PSPEC and contract requirements.

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

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

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

The Contractor shall deliver a Government Acceptance Test Plan (A025) and Test Report (A026) for verification of those PSPEC items as listed as Contractor in Section 4, Verification, Table 3, Requirement Verification Cross Reference Matrix in the PSPEC. The Contractor shall be prepared to execute the GAT at their facility 90 days, at the earliest, 90 days after contract award. After 90 days ACA, the Contractor shall be prepared to execute GAT immediately. Systems must pass GAT for the Contractor to proceed to competition for further production systems. Within 180 calendar days after the Government receives the initial systems, the Contracting Officer shall notify the Contractor, in writing, of the results of GAT. A notice of failure shall cite reasons for the failures, and further instruction if needed.

If an initial system fails a GAT, the Contractor shall subject all failures to the Contractor’s FRACAS process and make any necessary changes, modifications, or repairs to the system and deliver it to the Government or deliver another system for testing. All costs related to these tests are to be borne by the Contractor, including any and all costs for additional tests following a disapproval. The Contractor shall furnish any additional units to the Government under the terms and conditions and within the time specified by the Government.

The Contractor is responsible for providing operating and maintenance instruction, spare parts, support, and repair of the initial systems during any GAT. Any system hardware failures shall be remedied within 24 hours for all locations where on-site support is provided by the Contractor. Contractor on-site support is not required at NSWC Dahlgren and 72 hours is allowed to remedy failures at this location.

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

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

To support GAT, Contractors shall submit the Application for Equipment Frequency Allocation Data, (A027) DD Form 1494 supporting Spectrum Certification activities. The Contractor shall submit DD1494-1 through DD1494-4 in order to obtain Electronic Attack (EA) Clearance to perform GAT.

To aid in Safety Assessments prior to GAT, the Contractor shall submit a Safety Assessment Report (SAR) (A020). The SAR should include a systems description and unclassified photos of the system. The SAR shall be unclassified unless classified information must be included. In this instance, the classified information shall be included in a classified annex.

Should the Contractor fail to meet the requirements necessary to proceed to GAT at the TRR, the Contractor will be given 48 hours to gather and/or resolve any issues.

Entrance and Exit Criteria The entrance criterion includes the Government approval of the following data items:

· Test Plans for Factory Acceptance Testing (A023),

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

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

· ABCL (A001),

· SVD (A016),

· Frequency Allocation Data 1494 (A027), and

· SAR (A020).

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

GAT to be Performed at the Contractor Facility Government personnel will witness the GAT events performed at the Contractor facility. Testing will be performed by the Contractor. Data collection will be performed by Contractor and Government personnel.

GAT Performed at Government Facilities Government testing will be conducted at four test sites, NSWC Crane, NSWC Dahlgren, San Antonio (for dismounted systems), and Yuma Proving Grounds (YPG), as indicated in PSPEC. The Contractor shall provide on-site support for the testing at NSWC Crane. The Contractor shall estimate one (1) person for one (1) week for support at NSWC Crane. The Contractor shall provide on-site support for the testing at YPG. The Contractor shall estimate one (1) person for three (3) weeks support at YPG. Contractors shall provide on-site support for the Dismounted system for HERx testing at San Antonio. The Contractor shall estimate one (1) person for one (1) week support at San Antonio. The Contractor shall also provide necessary training, spares and all ancillary equipment to operate and maintain the systems during onsite support and testing. The contactor is not required to provide on-site support at NSWC Dahlgren..

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

· Move across uneven terrain while carrying mission essential equipment,

· Climb over walls,

· Ingress and egress military aircraft and vehicles; transportation within (V-22, CH-46, AAV, MTVR, and LAV),

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

· Move through woodland and jungle vegetation,

· Jump across ditches,

· Cross water obstacles by wading/swimming,

· Kick-in doors,

· Clear rooms, and

· Perform all weapon operations while in prone, kneeling and standing positions.

Production Planning/Readiness The Contactor shall demonstrate that the system is producible using the definitions, criteria, and processes defined in the Manufacturing Readiness Level Desk Book Version 2.2 as a guide (http://www.dodmrl.com). A Manufacturing Readiness Assessment (MRA) will be conducted by the Government during initial system production to assess the Contractor’s production capacity for future production system orders.

Manufacturing Readiness Assessment (MRA) After initial system delivery order award, the Contractor shall schedule and host a Government visit to their facility for up to three (3) days to perform a Manufacturing Readiness Assessment (MRA). The Contractor will be provided with not less than one (1) week advance notice of the date of the site visit. The Contractor shall be prepared to answer questions and demonstrate manufacturing readiness at this meeting.

Quality Management Planning The Contractor’s quality management program shall be in compliance with applicable ANSI/ISO/ASQ 9001:2008 standards or higher. Registration is preferred, however not required. All manufacturing processes and quality systems procedures shall also be IAW applicable ANSI/ISO Standards. The Contractor shall flow all quality system requirements down to sub-tier suppliers.

Counterfeit Parts and Materials The Contractor’s manufacturing processes shall include procedures to minimize the risk of procuring and/or using counterfeit parts and materials. Counterfeit parts including, but not limited to, electronic parts may typically be used parts which have been refurbished and represented as new. The Contractor may use SAE AS5553, Counterfeit Electronic Parts; Avoidance, Detection, Mitigation, and Disposition, which contains information regarding the detection, avoidance, and mitigation of counterfeit electronic components, as a reference document. The Contractor shall include the status of its Counterfeit Parts and Materials program compliance during the Post Award Kickoff Meeting and TIMs.

Preventing Counterfeit Parts and Materials The Contractor shall take steps as defined below to minimize the risk of receiving counterfeit parts and materials. The Contractor shall:

· Maximize the availability of authentic, originally designed and/or qualified parts throughout the product’s life cycle (estimated at 10 years), including management of parts obsolescence,

· Assess potential sources of supply to minimize the risk of receiving counterfeit parts or materials,

· Maintain a list of suppliers they have screened/authorized, with documented criteria for approval and removal of suppliers from their list,

· Have purchasing procedures which require the selection of parts and materials from Original Component Manufacturers (OCM) or authorized suppliers whenever possible,

· Define minimum inspection and test requirements for parts being procured from sources that have not been screened/authorized and ensure that in-house, third-party, and/or distributor inspection, test procedures and facilities comply with these requirements,

· Require a certificate of compliance and supply chain traceability for all electronic part purchases,

· Use Government or industry services, such as the Government and Industry Data Exchange Program, and other commercially available services to identify part or supplier quality or authenticity problems,

· Incorporate procurement clauses which plainly identify quality requirements and liability to all approved suppliers, and

· Flow the requirements above to affected Sub-Contractors.

Parts and materials shall not be purchased from unauthorized sources (e.g. independent distributor or broker) unless there is no other means for procurement. When an unauthorized source is the only possible choice for procurement, an RFD shall be provided to the COR. The RFD shall contain the following information:

· Reason why an authorized supplier or OCM could not provide the part or material,

· Product certificate of conformance with traceability to the OCM, if available, and

· Verification and authenticity data results (e.g., visual inspection, marking/surface finish permanency, Displacement Per Atom (DPA), Scanning Acoustic Microscopy, Energy Dispersive X-Ray Spectroscopy, Fourier Transform Infrared Spectroscopy, Rockwell Hardness Test, etc.).

Supportability The Contractor shall provide all job description tasks to include those that may be outside the normal operation and maintenance functions influence supportability products of the system; Job Task List (JTL) (A028), and Maintenance Task List (MTL) (A029). The JTL and MTL will serve as the foundation to ensure all operations, system adminitrations and maintenance tasks are defined in appropriate manuals, training materials and system support packages. MIL-STD-46855A, Human Engineering Requirements for Military Systems, Equipment and Facilities provides guidance for defining required tasks. Supportability requirements are described below:

Levels of Maintenance The Contractor shall ensure that supportability requirements and associated documentation reflects the USMC levels of maintenance described below:

· Operator Maintenance. Operator Maintenance will primarily consist of running BIT, checking warning lights, cable connectivity, lighting, etc. Operator duties include inventory, cleaning, inspecting, preserving, lubricating, adjusting and testing as well as preventative maintenance tasks with common shop tools and technical publications.

· Maintainer (Field/Unit Level) Maintenance. Field/Unit maintenance actions normally include inspection/in-depth diagnosis, modification, replacement, adjustment, and repair or evacuation/disposal of principle end items and their selected repairables and components/sub-components with common shop tools and technical publications. The maintainer is also responsible for installing Threat Loads on the systems.

· Depot (Sustainment Level) Maintenance. The intent of sustainment level maintenance is to sustain equipment throughout its life cycle by performing major repair, overhaul, or complete rebuild of parts, subassemblies, assemblies or principal end items to include manufacturing parts and conducting required modifications and testing. Marine Corps multi-commodity maintenance centers, other service depots, commercial industrial facilities, original equipment manufacturers, or a combination thereof, may perform sustainment level maintenance.

Obsolescence Management The Contractor shall be responsible for minimizing obsolescence by selecting products that will avoid or resolve hardware, software, and firmware obsolescence issues. The Contractor shall have a Diminishing Manufacturing Sources and Material Shortages (DMSMS) Management Implementation Plan (A030).