14-R-5011-0002.doc

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION B - SUPPLIES OR SERVICES AND PRICES

CLIN 0005

The CLIN description has changed from Spare Parts Block to Spare Parts Kit.

SECTION C - DESCRIPTIONS AND SPECIFICATIONS

The following have been modified:

STATEMENT OF WORK

STATEMENT OF WORK

FOR

EXTENDABLE BOOM FORKLIFT (EBFL) MODERNIZATION PROGRAM

1. SCOPE.

This statement of work (SOW) describes the outcome the contractor is required to achieve in order to provide the United States Marine Corps with modernized Extendable Boom Forklifts (EBFL). The contractor shall provide a modernized EBFL which has been enhanced with the modifications and serviced as specified in this SOW and meets the performance requirements established in the Performance Specification.

The contractor is responsible for providing all material, services and necessary support documentation needed to complete the tasks identified in this SOW.

2. APPLICABLE DOCUMENTS.

The following documents form a part of this SOW to the extent specified herein. The most recent revision of the referenced document at the time of contract shall be used unless otherwise specified. In the event of conflict between the applicable documents and this SOW, the SOW shall take precedence. All below references cited in mandatory compliance documents shall be considered as guidance only. Nothing in this document supersedes applicable laws or regulations unless a specific exemption has been obtained.

2.1 Military Standards and Specifications - Mandatory Compliance.

GEIA-STD-0007

Logistics Product Data

NAVMC 1553.1

Systems Approach to Training Users Guide

MIL-PRF-49506

Logistics Management Information

MIL-STD-130

Identification Marking of U.S. Military Property

MIL-STD-882

System Safety

MIL‑STD‑3018 w/Ch1

Parts Management

MIL-STD-31000

Technical Data Packages

MIL-STD-40051_

Technical Manual Standards

2.2 Military Handbooks - Guidance Only.

GEIA-HB-0007

Logistics Product Data Handbook

MIL‑HDBK‑61A

Configuration Management

MIL-HDBK-502

Acquisition Logistics

2.3 Other Government Documents. Unless otherwise stated, the following documents may be obtained from the Document Automation and Production Service, Building 4/D, 700 Robbins Avenue, Philadelphia, PA 19111-5094 or visit http://dodssp.daps.mil.

DI-SESS-81000

Product Drawings/Models and Associated Lists

TI 10794B-OR/2

Extendable Boom Fork-Lift Inspection of Mid Boom Wear Pad Bolts

TM 10794B-OI/A

Extendable Boom Fork-Lift Organizational and Intermediate Maintenance Manual with Repair Parts List

TM 10794B-OR/A

Extendable Boom Fork-Lift Operators Manual

2.4 Non-Government Documents.

ASME Y14.100

Engineering Drawing Practices with Append. B, C, D, & E

ASME Y14.24

Types and Applications of Engineering

ASME Y14.34

Associated Lists

GEIA-HB-649

Implementation Guide for Configuration Management

JLG Supplement 31200693 Sky Trak Model MMV Supplement #1

DODI 4160.28 Vol 1-3

DoD Demilitarization Instruction (Copies of ASTM documents are available from www.astm.org or American Society for Testing and Materials International, 100 Barr Harbor Drive, West Conshohocken, PA 19428-2959.)

3. REQUIREMENTS.

The Government will exchange its entire fleet of EBFL systems with the contractor which will in turn provide the Government with modernized EBFL systems as set forth below. The contractor may as deemed necessary utilize the exchanged EBFL systems as a spare parts pool to produce and deliver the required quantity of modernized EBFL systems to the Government. The contractor shall receive title to all exchanged EBFL systems in excess of the quantity to be delivered to the Government and shall be responsible for transportation and disposal or demilitarization of such systems to include all parts, components, and subsystems. The DEMIL code for the armored cab for the current EBFL is “D”. The contractor shall perform all tasks and provide all materials, equipment, hard tooling, personnel, and facilities required to deliver the types and quantities of deliverables specified in the contract. This includes associated documentation; logistics, technical support; a training package; and technical manuals. Upon successful completion of Production Qualification Testing (PQT) and the Field User Evaluation (FUE), the Government may place additional orders for production.

3.1 Modernization Program Elements.

The EBFL Modernization Program consists of a series of modifications and services as set forth below.

3.1.1 Modifications.

The contractor shall implement the following five (5) modifications. The modernized EBFL shall meet all requirements in the Performance Specification.

a. Overall Height Reduction.

b. Boom Hydraulic Assembly Relocation.

c. Carriage Quick Attach Coupler Relocation.

d. Carriage Backrest Enhancement.

e. Armored Cab Integration.

3.1.2 Inspection and Services.

An Initial Technical Inspection (ITI) shall be conducted upon receipt of each EBFL to determine the status of the system. During this inspection the contractor shall record all major component model numbers, serial numbers and other pertinent data. The contractor shall also inventory the required system components and basic issue items (BII). The ITI shall determine the status of, at a minimum, all subsystems which will undergo inspection, repair and replacement based maintenance as defined below. The condition of each machine along with serial/model numbers and inventory shall be documented and provided to Product Manager Engineer Systems (PdM ES), Material Handling Equipment/Construction Equipment (MHE/CE) in an ITI report. The ITI report shall be delivered to Government 14 calendar days after completion. The contractor shall conduct the following three (3) services.

CDRL B001, DI-NDTI-80809B, Initial Technical Inspection Report

3.1.2.1 Corrective Maintenance. The contractor shall conduct the corrective maintenance prescribed as follows on all EBFLs provided by the Government regardless of assigned condition code.

3.1.2.1.1 Inspection-Based Maintenance. The contractor shall conduct a thorough inspection of the following subsystems on all EBFL systems and shall repair only minor physical and functional degradation. The contractor shall notify the Government within 10 calendar days of receipt if any subsystems have major physical and functional degradation which require complete overhaul. Systems with major degradation requiring overhaul are defined as units which would not meet the current EBFL performance specification after modernization or have an economic useful life of less than 10 years. The contractor shall provide the Government an itemized estimate of the cost to repair any such systems which require complete overhaul. The contractor shall not conduct a complete overhaul of any of the following subsystems until approved by the Government.

a. Engine

b. Boom

c. Axles

d. Transmission

e. Vehicle Frame

3.1.2.1.2 Repair-Based Maintenance. The contractor shall conduct a thorough inspection of the following subsystems or features on all EBFL systems and shall repair all physical and functional degradation. Repairs shall consist of the most economical approach between cleaning, repairing, replacement of parts, or any combination thereof.

a. Fuel Tanks

b. Operator Seat and Seatbelt

c. Controls and Displays

d. Load Moment Indicator

e. Anti-Overload Device

f. Heating, Ventilation, Air Conditioning (HVAC)

g. Defroster

h. Window Wipers and Washer

i. Windows

j. Mirrors

k. Cab Light

l. Cab Fan

m. Horn and Backup Alarm

n. Lights

o. Tires*

p. Hydraulic Hoses and Fittings

q. Electrical Wires and Fittings

r. Boom Wear Pads (see TI 10794B-OR/2)

s. Battery Disconnect Switch (see JLG Supplement 31200693)

t. Steering Linkage Boots

j. Transfer Case

*Tires shall be inspected and replaced per Attachment E

3.1.2.1.3 Replacement-Based Maintenance. The contractor shall replace the following on all EBFL systems. Replacement parts and materials shall maintain the same form, fit, and function as the corresponding discarded item.

a. Batteries*

b. Petroleum, Oil, and Lubricants (POL)

c. Air and Fluid Filters

d. Transfer Cases**

e. Battery Disconnect Switch***

* Batteries shall be replaced with Hawker battery NSN 6140-01-485-1472

**The current fleet of EBFLs possess two variations of transfer cases, one manufactured by ZF and one by Carraro. The contractor shall replace all ZF transfer cases with Carraros transfer cases and ancillary interface equipment. The estimate of EBFLs which will need a transfer case replacement is 300. EBFLs with Carraro transfer cases only require repair based maintenance per 3.1.2.1.2.

*** In instances where the EBFL is not equipped with a battery disconnect switch the contractor shall install one per JLG Supplement 31200693. The estimate of EBFLs which will need a battery disconnect switch is 400.

3.1.2.2 Preventive Maintenance. The contractor shall conduct the Preventive Maintenance Checks and Services (PMCS) inclusive of the 250‑hr, 500‑hr, 1,000‑hr, and 2,000‑hr operator, field, and intermediate service intervals, without duplication of service, on all modernized EBFLs regardless of engine hour meter reading.

3.1.3 Paint and Treatment. The contractor shall paint and treat all modernized EBFLs. Specific requirements for this service are provided in the Performance Specification.

3.1.4 Spare Parts Kit. The contractor shall provide the government with a Spare Parts Kits (SPK). The SPK equipment shall undergo all modernization and maintenance in this SOW and, when installed onto the modernized EBFL, meet the requirements in the performance specification. Each SPK shall include the following items: One (1) Engines, One (1) Transmissions, One (1) set of Axles (one set includes one front axle and one rear axle), One (1) Boom assembly, One (1) Carraro Transfer Cases, One (1) 7k fork carriage assemblies and One (1) 11k fork carriage assemblies.

3.2 Program Management.

3.2.1 Program Management. The contractor shall establish and maintain program management practices throughout the period of performance. Program management practices shall provide visibility into the contractors’ organization and techniques used in managing the program, including subcontractor and data management. Documentation shall be readily available to Government representative(s) during planned visits. The contractor shall be responsible for tracking all EBFLs in a Master Control Document. The Master Control Document shall be provided to government per CDRL B002.

CDRL B002, DI-MGMT-80442, Master Control Document

3.2.2 Subcontractor Management. The contractor is responsible for performance of requirements delineated in this SOW and shall institute appropriate management actions relative to subcontractor performance. The contractor shall be accountable for subcontractor compliance and is responsible for ensuring all deliverable products comply with the contract requirements.

3.2.3 Schedule Planning. The contractor shall be cabable of producing at least twenty (20) Modernized EBFLs per month after successful PQT and a Full Rate Production (FRP) decision. The contractor shall notify the Government in writing within 10 days of any anticipated or projected work stoppages or delays that will impact schedules.

3.2.4 Planned Deliveries. The contractor is responsible for the pick-up and drop-off shipping cost. The Government will coordinate pick-up for Modernized EBFL which must be worldwide supportable and shipped Free On Board (FOB) to CONUS and OCONUS locations. Quantity and location will be specified on each individual delivery order. The pick-up and delivery locations are provided in attachment D.

3.3 Meetings, Formal Reviews, Conferences, and Audits.

3.3.1 Contractor Responsibilities. The contractor shall plan, attend, coordinate, support and conduct necessary meetings, formal reviews, conferences, and audits (hereinafter called "reviews"). The reviews shall be conducted at either Government or contractor facilities and shall allow individuals to participate via Video Teleconferencing (VTC)/Teleconference channels when necessary. Reviews requiring demonstration or examination of equipment shall be conducted at the contractor's facility. All such reviews shall be included in the program schedule and may be held concurrently with the Government’s approval. The contractor shall prepare agendas and conference presentation materials, and provide minutes and reports following each review. The Government reserves the right to cancel any review or to require any review to be scheduled at critical points during the period of performance. Action item documentation, assignment of responsibility for completion and due dates shall be determined prior to adjournment of all reviews. A summary of all action items, responsible parties, and estimated completion dates shall be included with the minutes per CDRL B003.

CDRL B003, DI-ADMN-81250A, Meeting Minutes

3.3.2 Post Award Meeting/Preliminary Design Review. A combined Post Award Meeting (PAM) and Preliminary Design Review (PDR) will be held within 30 days after Contract Award. The purpose of the PAM/PDR is for the contractor to review and demonstrate to the Government the Program and Data Management procedures, provide progress assessments, review of technical and other specialty area status, and to establish schedule dates for near term critical meetings, actions, and reviews. The contractor shall present management, key personnel, and program implementation processes.

3.3.3 In-Process Review. In-Process Reviews (IPR) shall be held quarterly or as needed. The Government reserves the right to cancel any review or to require any review to be scheduled during the period of performance. The contractor’s progress, management, technical support services, administrative processes, assurance of compliance with contract requirements, program status, funding, problem identification and resolutions shall be agenda items. Actual versus expected performance of each area shall be addressed. The contractor shall prepare presentation materials providing an overview of all agenda items.

3.4 Systems Engineering.

3.4.1 Systems Engineering Program. The contractor shall establish and maintain a systems engineering program throughout the period of performance. The systems engineering program shall be documented in a Systems Engineering Management Plan (SEMP) and shall describe the contractor’s planned systems engineering approach to meeting the program’s contract, objectives, and overall technical and management approach.

3.4.2 Technical Reviews. Technical reviews will be conducted in accordance with MCSCO 5400.5, Naval Systems Engineering Policy and the MARCORSYSCOM Technical Review Handbook.

3.4.2.1 Critical Design Review. The contractor shall participate in the Critical Design Review (CDR) scheduled by the Government to be conducted after Contract Award and prior to delivery of PQT and FUE assets. At the CDR, the contractor shall present and discuss the SEMP, the Requirements Traceability Matrix (RTM), all certifications required in the Performance Specification, the System Impact Assessment (SIA), the Corrosion Prevention and Control Plan (CPCP), the Quality Management (QM) program, Roll Over Protection Systems (ROPS) & Falling Objects Protection Systems ( FOPS) design analysis and the Technical Data Package (TDP). In preparation for the CDR, the contractor shall provide all presentation materials, technical data, and reports, to the Government at least 7 calendar days prior to the scheduled CDR.

3.4.2.2 Test Readiness Review. The contractor shall participate in the Test Readiness Review (TRR) scheduled by the Government to be conducted prior to PQT and the FUE. At the TRR, the contractor shall present and discuss any changes or updates to the materials presented during the CDR, the plan for providing support during PQT and the FUE, the Failure Reporting, Analysis, and Corrective Action System (FRACAS) with approach to reviewing and responding to Test Incident Reports (TIRs), and the Configuration Management (CM) program. In preparation for the TRR, the contractor shall provide all presentation materials, documents updated since the CDR, and an accurate TDP for establishing a product baseline to the Government at least 7 calendar days prior to the scheduled TRR.

3.4.2.3 System Verification Review. The contractor shall participate in the System Verification Review (SVR) scheduled by the Government to be conducted after completion of PQT and the FUE and prior to any production Delivery Orders. The contractor shall present and discuss any changes or updates to the materials presented during the TRR and all failures identified during PQT and the FUE with the corresponding analyses, and corrective actions planned and/or implemented. In preparation for the SVR the contractor shall provide all presentation materials, documents updated since the TRR, and all failure analyses and corrective actions with responses to all TIRs to the Government at least 7 calendar days prior to the SVR.

3.4.2.4 Production Readiness Review. The contractor shall participate in the Production Readiness Review (PRR) scheduled by the Government to be conducted after the PQT and FUE have been completed and prior to any production Delivery Orders. The contractor shall present and discuss any changes or updates to the materials presented during the SVR, the Producibility Plan, the QM program, the CM program, any anticipated, approved, or implemented engineering changes or deviances from the product baseline. In preparation for the PRR, the contractor shall provide all presentation materials and documents updated since the SVR to the Government at least 7 calendar days prior to the PRR.

3.4.2.5 Physical Configuration Audit. The contractor shall participate in the Physical Configuration Audit (PCA) scheduled by the Government to be conducted after the first production Delivery Order and prior to fielding. The contractor shall present and discuss any changes or updates to the materials presented during the PRR. In preparation for the PCA, the contractor shall provide all presentation materials and documents updated since the PRR to the Government at least 7 days prior to the PCA. Additional details for the PCA are established in the Configuration Management section of this SOW.

3.4.3 Requirements Traceability Matrix. The contractor shall document technical compliance in a Requirements Traceability Matrix (RTM) identifying how modernized EBFL compliance with each requirement in the Performance Specification has been attained and preserved throughout the entire period of performance. The RTM shall include all supporting design, certification, analysis, demonstration, examination, or test data obtained or generated by the contractor during the design and/or fabrication processes.

3.4.4 Corrosion Prevention and Control. The contractor shall develop a Corrosion Prevention and Control Plan (CPCP) that describes the specific measures to be implemented throughout the EBFL Modernization Program. The purpose of the CPCP is to document corrosion-related design decisions and identify materials and corrosion control methods used in the EBFL. The plan shall address the techniques and processes to be applied in assuring that the products to be delivered will meet the requirements contained in the Performance Specification. Changes in materials, coatings, or corrosion prevention methods during the course of production shall be reflected in updated versions of the CPCP. At a minimum, the CPCP shall provide the following information:

a. Discussion of corrosion prevention techniques employed in design, including measures taken to minimize water collection/entrapment and collection of debris, to mitigate corrosion in areas inaccessible to cleaning and maintenance, and to minimize dissimilar metal contact.

b. Process instructions detailing application of coatings and other corrosion prevention compounds (if any). Process instructions should address personnel training and qualification, material inspection, surface preparation, and coating or compound application procedures.

c. Any test data developed for coatings and materials.

d. Identification of coating/substrate combinations for which no testing was required or performed.

e. Recommended corrosion control-specific maintenance.

f. Quality assurance program provisions to address materiel control to ensure that the materials used in the EBFL are shown on engineering drawings; and in-process measurements (number, type, frequency, locations) to ensure compliance with process instructions developed under b, above.

Changes in materials, coatings, or corrosion prevention methods during the course of production shall be reflected in updated versions of the CPCP per CDRL A001.

CDRL A001, DI-MFFP-81403, Corrosion Prevention and Control Plan

3.4.5 Reliability and Maintainability

3.4.5.1 Reliability and Maintainability Program. The Reliability and Maintainability (R&M) program shall encompass all aspects of reliability with respect to design selection of components, predictions, and testing. The contractor shall maintain and make available to the Government all R&M data on any vendor or subcontractor supplied item and shall inform the Government of any part or component, which will degrade system R&M requirements.

3.4.5.2 Procedures and Controls. The contractor shall maintain procedures and controls, which ensure products obtained from suppliers, vendors and subcontractors meet reliability requirements. The contractor shall establish, implement, and maintain documented procedures, which detect and/or preclude the use of substandard or counterfeit parts in the production process, and impose similar requirements on subcontractors.

3.4.5.3 Failure Reporting, Analysis, and Corrective Action System. The contractor shall develop a closed loop failure reporting system, procedures for analysis of failures to determine the root cause, and documentation for recording corrective actions taken. The FRACAS shall include uniform failure reporting, failure analysis reports and corrective actions. All hardware/software failures from system level down to the subassembly level shall be subject to these requirements throughout the testing period including production and integration testing, and during the post-production support.

3.5 Quality Management System.

3.5.1 Quality Assurance Program Plan (QAPP). The contractor shall establish, implement, document and maintain a quality system that ensures conformance to contractual requirements. The contractor shall implement the requirements of ANSI/ASQC Q9001, ISO 9001 or an equivalent quality system model; no third party certification is required. The contractor shall make their QAPP or Quality Manual (whichever document they've developed as required by their ANSI, ISO, or equivalent quality system – development of a Government unique document is not required) available for Government review at their facility as required. The contractor shall notify the Government when they update their QAPP throughout the contract period of performance through Letter of Transmittal to the PCO.

3.5.2 Quality Assurance Management Meeting (QAMM). The contractor shall schedule and participate in QAMMs. The meetings shall include representatives from Quality, Production, and Engineering at a minimum, and shall be held quarterly (at a minimum) in conjunction with the IPR or on an as needed basis. Additional meetings shall be scheduled through the Administrative Contracting Officer (ACO) /PCO if quality issues dictate additional surveillance.

3.6 Producibility. The contractor shall apply producibility principles during all design processes to ensure that the production units will be easy to manufacture using the anticipated production facilities, equipment, materials, manpower, and processes. The producibility planning effort shall also maximize the ease of production control, quality control, tooling and inspection.

3.7 Environment, Safety, and Occupational Health

3.7.1 System Safety. The contractor shall identify and evaluate environmental, safety, and health hazards, define risk levels, and establish a program that manages the probability and severity of all hazards associated with development, use, and disposal of the system in accordance with MIL-STD-882. Risks will be evaluated by the Government in accordance with MIL-STD-882 and accepted as appropriate prior to exposing people, equipment, or the environment to known system related Environment, Safety, and Occupational Health (ESOH) risks.

3.7.2 Material Safety Data Sheets. The contractor shall make available Safety Data Sheets (SDS) or Material Safety Data Sheets (MSDS) for all hazardous materials used in the modernization of the EBFL prior to the CDR for the Government review.

3.8 Product Drawings/Models and Associated Lists. The contractor shall provide a complete Product Level Drawing Package in accordance with MIL-STD 31000, which completely documents the system design per CDRL A002. All drawings in this Product Drawing Package shall comply with ANSI Y14.100, ASME Y14.24 and ASME Y14.34M. This Product Drawing Package shall include assembly drawings and detail drawings down to the piece part for all items designed and developed at Government expense. The assembly and detail drawings shall provide necessary design, engineering, manufacturing and quality assurance requirements necessary to enable the procurement or manufacture of an interchangeable item, which duplicates the physical and performance characteristics of the original product, without additional design, engineering or recourse to the original design activity. This Product Drawing Package shall also include control drawings for all Commercial Off-The-Shelf (COTS) items that do not conform to recognized Government or industry specifications, non-developmental items (NDI), and items developed at private expense for which the Government has not acquired unlimited rights. These control drawings shall provide the applicable performance specification form, fit, function and interface information needed for competitive re-procurement of that item or an interchangeable item. The contractor shall also provide any digital modeling data files developed in support of this Product Drawing Package or the system design.

CDRL A002, DI-SESS-81000D, Product Drawings/Models and Associated Lists

3.9 Configuration Management (CM)

3.9.1 Configuration Management Process. The contractor shall maintain a CM process for the control of all requirements, hardware, software and external system interface configuration documentation, media and parts representing or comprising work related to the EBFL Modernization Program. The principles contained in EIA-649, National Consensus Standard for Configuration Management, and MIL-HDBK-61A, Configuration Management Guidance, should be used for guidance as well as related MARCORSYSCOM acquisition and engineering policy. The contractor's CM process shall consist of CM planning, configuration identification, configuration control, configuration status accounting, and configuration verification and audits and data management including tools. Processes and tools for interfacing with other acquisition requirements such as design review, assurance, and other program related disciplines shall be addressed. The contractor shall designate a CM representative to serve as a primary point of contact to the Government for all CM matters. The contractor's representative shall be responsible for any subcontractor's CM efforts. The contractor shall notify the Government of any changes at the contractor's facility, which affect the execution of the contractor's CM Plan. The contractor shall present and discuss their CM plan at the Critical Design Review. The Government will review and approve the contractor’s CM plan. The CM Plan shall be reviewed at least annually, and updated to reflect changes in system engineering, logistics or acquisition strategy concepts.

3.9.2 Configuration Identification (CI). In coordination with the Government’s CM manager, the contractor shall develop methods to uniquely identify Configuration Items (CI) and associated documentation, such as drawings, manuals, plans, procedures, instructions, and other configuration-related documents.

3.9.3 Configuration Status Accounting. The contractor shall establish and maintain a Configuration Status Accounting (CSA) database, which represents the configuration of the armored cab. All baselines, changes and planned systems upgrades shall be documented in the contractor’s CSA database. The contractor’s CSA database shall permit acceptance of commercial product information; however, if requirements to report data outside of the contractor’s CSA database or format exist, the information may be delivered as a supplement to prevent disruption to their existing system. The contractor’s CSA database shall reconcile any differences between the supplier information and contractor practices to provide the Government with clear accountability of product information. Additionally, the CSA database shall provide a reliable source of configuration information to support all EBFL Modernization Program activities, including program management, systems engineering, logistics support, and modification/maintenance actions. The contractor’s CSA database shall be capable of providing CSA data in a digital format compatible with USMC’s CSA automated information system, Joint Configuration Management Information System (JCMIS).

3.9.3.1 Modification Tracking. The contractor shall utilize the CSA database to record completed field modifications or retrofit actions as a result of approved ECPs for each CI. The contractor shall maintain the information that allows visibility of completed actions to the USMC Serial numbers or IUID. The contractor’s CSA database shall include the following data elements:

a. USMC Serial Number, computer software name and version or IUID

b. ECP/MI Number

c. Date Installed

d. Location

e. Ownership.

3.9.3.2 Baseline Tracking. The contractor shall establish a database that records and maintains configuration baselines. The database shall record; documents, hardware, computer software and drawings that have been approved and placed under Government configuration control and new CIs which are planned for inclusion in future baseline updates. As a minimum, CI data shall identify the current approved baseline by:

a. Document number and Document type

b. CAGE

c. Revision Level

d. Nomenclature

e. Drawing size

f. Indentured breakdown of parts, which display a “parent to child” relationship, to include quantity. The breakdown shall only pertain to CI documents under Government configuration control.

g. Computer software version number.

3.9.4 Configuration Management Meetings/Audits. A Physical Configuration Audit (PCA) shall be performed to verify the EBFL Modernization Program CI are accurate, complete, and compatible. The Government and the contractor shall conduct the PCA jointly, at a time and place designated by the Government, with the Government chairing the audit. The PCA shall verify the drawings reflect the "as-built" configuration of all newly developed or modified portions of the system; accurate form, fit or function information is provided on control drawings for non-developmental/ commercial off-the-shelf items; and confirm the drawings accurately represent the "as-built" production configuration. Whenever possible, the PCA shall be conducted incrementally, concurrent with hardware fabrication and assembly of the first production system. The contractor shall develop a configuration audit plan and provide the system to be audited, facilities, personnel, documentation (including drawings) and other support as may be required. The contractor shall participate and assist the Government in the development of the PCA, using the guidelines contained in Section 8 of MIL-HDBK-61A, Configuration Management Guidance. The contractor shall document the results of the PCA after each audit and shall correct all audit discrepancies documented in the configuration audit summary reports. In the event the Government finds evidence the drawings and/or documents do not adequately represent the equipment, production shall cease until all discrepancies are corrected and the Government approves the configuration audit summary report.

3.9.5 Parts Management Program. The contractor shall establish and maintain a Parts Management Program in accordance with MIL-STD-3018, Parts Management, for all new designs or modified equipment. This program will ensure that the use of parts meet the contractual requirements, reduce proliferation of parts within and across DoD systems and equipment, through standardization, and enhance reliability and supportability to meet material readiness objectives, and reduce total-life-cycle costs. The contractor shall describe how the parts management process is validated, the contractor shall describe how process improvements are incorporated, and the contractor shall describe how process variation is controlled. The contractor shall document the program plan. The procedures, planning and all other documentation, media and data which define the Parts Management Program and the parts selected for use shall be made available to the Government for their review. The Government may perform any necessary inspections, verifications, and evaluations to ascertain conformance to requirements and adequacy of the implementing procedures. The Government may exercise its right to disapprove the Parts Management Program or portions thereof when it fails to meet its intended objectives

3.9.6 Product Baseline Management. The contractor shall maintain a current and accurate Product Baseline to ensure form, fit, and function of the EBFL modifications and interface of the armored cab. The contractor shall establish definitive processes, which identify how the Product Baseline will be managed and maintained. These processes shall be defined in the contractor's CM plan and made available for Government review. The product baseline is the approved technical documentation that describes the configuration of a CI during the production, fielding/deployment and operational support phases of its life cycle. The product baseline shall prescribe; (1) all necessary physical or form, fit, and functional characteristics of a CI; (2) the selected functional characteristics designated for production acceptance testing and; (3) the production acceptance test requirements. The contractor shall establish the product baseline at the conclusion of the Critical Design Review. No changes shall be made to this baseline without following the Engineering Change Proposal (ECP) process.

3.9.7 Configuration Control. The contractor shall implement configuration control methods and procedures, which maintain the integrity and traceability of an established baseline. Changes to established baselines shall only be made after Government approval of ECP and Request for Deviations (RFDs) via the Configuration Control Board (CCB) process. Sufficient supporting data to evaluate the proposed change, such as drawings, supplemental drawings, sketches, specifications, or manufacturer’s data sheets, shall be submitted with ECP’s and RFD’s. Changes shall be identified to the affected assembly serial number, or if not part of an assembly, to the affected equipment serial number. The contractor’s configuration control process shall be available for Government review. The contractor shall submit all configuration control documentation in a digital format specified by the Government.

3.9.7.1 Engineering Release System. The contractor shall maintain an engineering release system and shall use the system to issue configuration documentation to functional activities (e.g. manufacturing, logistics, quality control, and engineering) and to authorize the use of configuration documentation associated with an approved configuration. The contractor shall maintain current and historical engineering release information for all configuration documentation for the EBFL Modernization Program. The contractor shall submit an Engineering Release Record (ERR) to release new or revised configuration documentation to the Government for approval. The contractor shall ensure all Government approved ERR information/documentation is reflected in the Configuration Status Accounting (CSA) database.

CDRL A003, DI-MISC-80508B, Configuration Control

3.9.7.2 Engineering Change Proposals. ECP shall be submitted by the contractor; and shall be limited to those that are necessary or offer significant benefit to the Government. MIL-HDBK-61A provides guidance concerning the classification of ECP’s. Class I ECP’s shall be submitted when changes are required to: (a) Correct deficiencies; (b) Add or modify interface or interoperability requirements; (c) Make a significant and measurable effectiveness change in the operational capabilities or logistics supportability of the system; (d) Effect substantial life cycle costs/savings; and (e) Prevent slippage in an approved production schedule. Class II ECP’s shall be submitted by the contractor to the Procuring Contracting Officer (PCO) for approval for those engineering changes, which impacts none of the factors listed above. As a minimum, Class I ECP’s shall contain the following information: (a) Date prepared; (b) Originator; (c) ECP Classification; (d) ECP Number; (e) Reason/need for change; (f) System designation (nomenclature, model, P/N); (g) Name of part (or lowest assembly) affected to include part numbers; (h) Baselines affected (to include drawings, specifications, CAGE, revision level, etc.); (i) Title of change; (j) Description of change; (k) Effect on interfaces (Interchangeability and Interoperability); (l) Total costs/savings w/ breakout; (m) Retrofit information; (n) Ozone Depleting Substances; (o) Impact on any engineering disciplines (such as quality, environmental, safety, health, reliability, maintainability, etc.); (p) Justification for change; (q) Priority of change; (r) Impacts to any logistics support elements (such as software, manuals, spares, tools, etc.) being utilized by Government personnel in support of the product; and (s) Alternatives evaluated or considered.

CDRL A003, DI-MISC-80508B, Configuration Control

3.9.7.3 Requests for Deviation. The contractor shall submit all Requests for Deviation (RFD) from current approved configuration documentation to the Government. Authorized deviations are a temporary departure from the requirements and do not constitute a change in an approved baseline. Submission of recurring deviations is discouraged and shall be minimized. Where it is determined that a change should be permanent, the contractor shall submit an Engineering Change Proposal. MIL-HDBK-61A provides guidance concerning the classification of RFDs. As a minimum, the RFD shall contain the following information: (a) Date prepared; (b) Originator; (c) RFD Classification (critical, major or minor); (d) Designation for deviation (model/type, CAGE code, system designation, and deviation number); (e) Class of deviation; (f) Part Number affected; (g) Cost/Price data; (h) Effectivity; (i) Description of deviation; (j) Need for deviation; (k) Effect on delivery schedule; (l) Recommended corrective action; and (m) Alternatives evaluated.

CDRL A003, DI-MISC-80508B, Configuration Control

3.9.7.4 Notices of Revision. The contractor shall generate and submit Notices of Revision (NOR) concurrently with ECP when technical documentation controlled by another contractor or Government agency requires changes following approval of an ECP. As a minimum, the NOR shall contain the following information: (a) Date; (b) CAGE code; (c) NOR number; (d) Document number; (e) Title of document; (f) Revision letter (current and new), related ECP number; (g) Configuration item (or system) to which ECP applies; and (h) Description of revision.

CDRL A003, DI-MISC-80508B, Configuration Control

3.10 Verification.

3.10.1 Contractor Certification. The contractor shall provide the necessary data to verify EBFL technical compliance with performance requirements as established in the Performance Specification Verification section 4. The contractor shall certify by signature on the recorded data sheets to indicate the validity of the provided information. The contractor shall provide all contractor certifications 14 calendar days prior to PQT.

3.10.2 Contractor Support to Government Testing. The contractor shall support Government test efforts by providing personnel and support. The contractor shall support each Government test by providing maintenance, training, logistics, and technical support for the period of testing. Testing both automotive and ballistic capabilities is estimated to take between 3 to 6 months. Test support requirements will be tailored to the test being conducted. The contractor shall provide all required support equipment and spare parts needed to maintain the EBFL and ancillary equipment during each test. The contractor shall analyze test data, conduct failure analysis, and maintain a data tracking system throughout all test efforts. The contractor shall utilize the FRACAS to review and respond to Test Incident Reports (TIRs) generated by the Government test agency throughout PQT and the FUE within 7 days of being posted. When testing is conducted or coordinated by an Army Test and Evaluation Command (ATEC) test agency, the contractor shall acquire and maintain access to the ATEC Versatile Information Systems Integrated On‑Line (VISION) Digital Library System (VDLS). The contractor shall implement Government approved corrective actions, within a timeframe that does not cause delays in program schedule.

3.10.3 Product Qualification Test (PQT) Assets. In the event the PQT assets fail to meet requirements established in the Performance Specification, the contractor shall submit plans for the corrective action or disposition to the Government for approval. Minor failures may be corrected during testing, with Government approval. Production shall not be initiated without Government approval after successfully completing PQT.

3.10.4 PQT/FUE Refurbishment. If the PQT/FUE assets are not destroyed in testing, and as approved by the Government, the contractor shall refurbish and deliver them as part of the contract quantity, provided they meet production acceptance test requirements. This shall be accomplished within 90 days after approval.

3.10.5 Refurbishment and Retrofit of Units. The contractor shall refurbish and retrofit all previously delivered units to include all corrective actions and modifications approved and implement in mid-production.

4. SUPPORTABILITY

4.1 Warranty.

4.1.1 Warranty Management. The contractor shall provide a manufacturer’s warranty for all components used to meet the requirements of the EBFL Modernization Program including the plug’n’play armor cab solution. Each modification and service warranted shall be indexed and identified by serial number, model or part number, and date of acceptance by the Government. Warranties shall become effective upon delivery and acceptance by using unit. All pertinent data required for the Government to pursue warranty provisions, remedy, and relief for each modification and services shall be maintained by the contractor for the duration of the warranty period. All warranty claims and transactions shall be documented and made available for Government review during scheduled meetings and reviews. A copy of the Warranty Agreement will be provided to the Government at the PAM.

4.1.2 Execution. The warranty cost shall be all-inclusive to include costs such as labor, time and travel, parts, and shipping. The warranty shall begin on the date the asset is accepted at the Government’s receiving unit. The contractor shall not perform on-site warranty repairs in contingency operations; however, they shall provide parts support. Contractors shall conduct repairs on-site at all non-contingency areas. The contractor shall not void the warranty if the user conducts repairs. In this case the vendor will only be required to ship warranted parts. Parts may be shipped by air, or to a designated CONUS float location, as determined appropriate by the Government. The contractor may be required to ship parts directly to overseas locations, at the discretion of the Government. All OCONUS and Aerial Port Of Entry (APOE) / Fleet Post Office (FPO) shipping addresses should be shipped using United States Postal Service (USPS) and will require the contractor to submit a Document Number Request (DNR) through the Government Project Officer or Logistician.

4.1.3 Reporting of Warranty Data. The contractor shall use the PdM ES Warranty Service and Support Claims Tool (WSSCT) to manage all warranty claims under this contract pertaining to the EBFL Modernization Program. All items under warranty will be loaded to the WSSCT. The contractor shall:

a. Establish an account in the WSSCT using the website link below. Local vendors, whom conduct warranty repairs and repair consult, shall also establish accounts in the WSSCT to support the EBFL Modernization Program. URL: http://www.marcorsyscom.usmc.mil/sites/warranty/

b. Accept or reject all claims within 48 hours of claim being initiated.

c. Provide status to the User, Warranty Coordinator, and Project Officer using a combination of the “Comments Log”, located within WSSCT, and email on all warranty claims.

d. Order and ship of all parts under warranty.

e. Perform repairs on all claims under warranty. The contractor shall adhere to the following repair cycle times:

i. Continental United States (CONUS): 7 Days – Parts and repair.

ii. Outside Continental United States (OCONUS): 14 Days – Parts and repair.

iii. Contingency Operations: 14 Days – Parts only.

f. Provide labor hours and the following cost data associated to the warranty services:

i. Labor

ii. Time and travel

iii. Parts

iv. Shipping and other

g. The dollar amount provided for each claim will be a total dollar amount at equivalent commercial dealer selling/list price rates for all expenses, including parts, labor, and travel time/mileage (TT/M).

4.2 Maintenance Planning. The contractor shall ensure the modernized EBFL is supportable and maintainable with the USMC two levels of maintenance concept. The 2 levels of maintenance include Field and Depot Levels. Field includes the Organizational and Intermediate Categories defined below. Design influence for maintenance planning and ease of maintenance should be considered at all times. The maintenance of the Modernized EBFL will require no new or special tools and or testing equipment.

4.3 Field Level Maintenance. Field level maintenance consists of the Organizational and Intermediate maintenance categories.

4.3.1 Organizational Maintenance Category. This category is the lowest level of maintenance performed. It is normally initiated with operator Preventive Maintenance Checks and Services (PMCS). PMCS is a scheduled function and is conducted before, during, and after operation as well as at specified hourly intervals, weekly, monthly, quarterly, and annually in accordance with the appropriate technical manuals. Operator maintenance tasks will be performed using tools from the BII or the GMTK. The operator is responsible for initial fault detection and isolation. The operator is authorized to remove and replace components as stated in the TM to aid the operator in diagnostics.

4.3.2 Intermediate Maintenance Category. The intent of Intermediate maintenance category consists of the Organizational Maintenance Category and also includes in-depth inspections, diagnosis, modification, replacement, adjustment, and limited repair or evacuation and disposal of principal end items and components or sub-components. These repairs will generally be performed using tools GMTK, Common 20, 22 and 30. Intermediate maintenance is performed by Marines with MOS 1341.

4.4 Depot Level Of Maintenance. Depot level maintenance shall consist of complete repair, major overhaul, or complete rebuild of the parts, assemblies, subassemblies, and end items, including secondary repairables, the manufacture of parts, piece part repair, modification, and testing that is beyond the capability of the Intermediate level of maintenance. Depot level maintenance will be conducted at a designated support Depot, Government or contractor.

4.4.1 Support Equipment. The Modernized EBFL will not require any new or special tools to support Field Level Maintenance. Field Level Maintenance will continue to be conducted using the tools listed in the table below.

4.5 Provisioning.

4.5.1 Provisioning Guidance Meeting. The contractor shall participate in the Provisioning Guidance Meeting (PGM) in conjunction with the PAM. The Government will lead the meeting and clarify any provisioning issues with regards to quality, format, and delivery dates.

4.5.2 Provisioning Meeting(s). The contractor shall host all Provisioning Meeting(s) at the contractor's facility. During these meetings, the contractor is required to provide and disassemble production grade equipment, as deemed necessary by the Government, to validate and verify all provisioning documentation, parts and assemblies. The number of provisioning meetings is based on the total number of Provisioning Line Item Sequence Numbers (PLISNs).

4.5.3 Provisioning and Other Pre-procurement Screening Data. Provisioning and other pre-procurement screening data are used to identify existing National Stock Numbers (NSNs) for an item, validate currency of an NSN, and aid in maximum use of known assets.

The contractor shall conduct provisioning screening on each item listed on…