14-R-5040-0003.doc

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION A - SOLICITATION/CONTRACT FORM

The required response date/time has changed from 13-Aug-2014 10:00 AM to 27-Aug-2014 10:00 AM.

SECTION B - SUPPLIES OR SERVICES AND PRICES

CLIN 0024

The pricing detail quantity 1.00 has been added.

The unit of issue Each has been added.

CLIN 4004

The pricing detail quantity has increased by 10.00 from 5.00 to 15.00.

SECTION C - DESCRIPTIONS AND SPECIFICATIONS

The following have been modified:

STATEMENT OF WORK

STATEMENT OF WORK

FOR THE

Marine Corps Tactical Welding Shop (MCTWS)

1 SCOPE

This Statement of Work (SOW) defines the efforts required for the procurement and delivery of the Marine Corps Tactical Welding Shop (MCTWS) replacement, to include provisioning data, illustrations, Technical Manuals (TMs), training aids, operator and maintainer training, logistics and support. The contractor shall provide the requisite program management and logistics support to ensure that delivery schedules, performance requirements and overall supportability of the MCTWS is accomplished as set forth in the contract. The contractor is responsible for providing all/specific material, services and necessary support documentation needed to complete the tasks identified in this SOW.

1.1 Background. The MCTWS program has been initiated to integrate, produce, and deploy an improved tactical welding system that will satisfy the requirements outlined in the Statement of Need (SON) for the Replacement for the Marine Corps Tactical Weld Shop w/ Change 2, dated 29 April 2014 and integrated into the Performance Specification (PS). The Marine Corps has a requirement for 179 MCTWS systems, to include associated manuals, training, and warranty support. The legacy MCTWS provides the United States Marine Corps (USMC) with the capability to perform ferrous and nonferrous maintenance welding and fabrication and is currently used by organizational and field maintenance units in both garrison and field environments. The MCTWS is a self-contained welding shop and includes the tools, machinery, consumables, compressed air, electrical powered lights, and hand tools required to perform a variety of welding missions. It provides SMAW (Stick), GMAW (MIG), FCAW (Fluxcore), GTAW (TIG), aluminum welding, plasma cutting, oxygen/acetylene (oxy/acy) cutting, and exothermic cutting capability.

2 APPLICABLE DOCUMENTS

The following documents specified 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 second tier and below references cited in mandatory compliance documents shall be considered as guidance only. Nothing in this document, however, supersedes applicable laws and regulations unless a specific exemption has been obtained.

2.1 Military Standards and Specifications - Mandatory Compliance

GEIA-STD-0007

Logistics Product Data

MIL-STD-130

Identification Marking of U.S. Military Property

MIL-STD-882

Standard Practice for System Safety

MIL-STD-1366

DoD Interface Standard for Transportability Criteria

MIL-STD-40051-2

Preparation of Digital Technical Information for Page – Based Technical Manuals

MIL-STD-40051-5

Parts Information (PI) and Repair Parts and Special Tools List (RPSTL)

NAVMC 1553.1

Systems Approach to Training (SAT Users Guide

2.2 Military Standards and Specifications – Guidance Only

Not Applicable

2.3 Drawings

MIL-PRF-28002

Requirements for Raster Graphics Representation in Binary Format

MIL-PRF-28003

Digital Representation for Communication of Illustration Data: CGM Application Profile

MIL-STD-12

Abbreviations for use on Drawings and in Specifications, Standards and Technical Documents

MIL-STD-31000

DoD Standard Practice: Technical Data Packages

MIL-I-28947

Illustrations for Stock List Publications: Preparation of

2.4 Handbooks - Guidance Only

MARCORSYSCOM

Technical Review Handbook, Version 1.04

MIL-HDBK-61

Configuration Management Guidance

MIL-HDBK-3018

Parts Management

(Copies of the MARCORSYSCOM Technical Review Handbook are available upon request from the Program Office.)

2.5 Other Government Documents

MCSCO 5400.5

Naval Systems Engineering Policy

(Copies of MCSCO 5400.5 are available upon request from the Program Office.)

2.6 Non-Government Documents

ANSI/ASQC Q9001

Quality Management Systems – Requirements

(Copies of ANSI documents are available from ansi.org or the American National Standards Institute, 11 W. 42nd Street, New York, New York 10036.)

ASME Y14.1

Decimal Inch Drawing Sheet Size and Format

ASME Y14.24

Types and Applications of Engineering Drawings

ASME Y14.34

Associated Lists

ASME Y14.35

Drawing Revisions

ASME Y14.100

Engineering Drawing Practices

(Copies of ASME documents are available from www.asme.org or American Society of Mechanical Engineers Information Central Orders/Inquiries, P.O. Box 2300, Fairfield, NJ 07007-2300.)

ASTM D3951

Standard Practice for Commercial Packaging

(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.)

EIA-649

National Consensus Standard for Configuration Management

(Copies of EIA documents are available from www.eia.org or Electronic Industries Alliance Corporate Engineering Department, 2500 Wilson Boulevard, Arlington, VA, 22201.)

ISO 9001

Quality Management Systems – Requirements

ISO 10303

Industrial Automation Systems and Integration – Product Data Representation and Exchange

(Copies of ISO documents are available from www.iso.org)

NAS 411

Hazardous Materials Management Program

(Copies of NAS 411 are available from www.aia-aerospace.org or Aerospace Industries Association of America, 1250 Eye Street, NW, Suite 1200, Washington, DC 20005-3924.)

3 REQUIREMENTS

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 TMs. Upon successful completion of Production Qualification Testing (FAT) and the Field User Evaluation (FUE), the Government may order production quantities.

3.1 Program & Data Management

3.1.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 submit a monthly status report which shall be provided to government per CDRL B001.

CDRL B001, DI-MGMT-80227, Contractor’s Progress, Status and Management Report

3.1.2 Subcontractor Management. The contractor is responsible for performance of requirements delineated in this SOW and shall institute 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.1.3 Technical Compliance with Performance Capabilities. The contractor shall deliver MCTWS’ compliant with the performance capabilities stated in the PS. Technical compliance shall be based on evidence (e.g., commercial specifications, test or performance data, etc.) the MCTWS meets the performance standards set forth in the PS.

3.1.4 Schedule Planning. The contractor shall be able to produce no less than 20 MCTWS assets per month after successful FAT and a Full Rate Production (FRP) decision. The contractor shall notify the Government in writing of any anticipated or projected work stoppages or delays that will impact schedules. The contractor shall provide an updated production and delivery schedule to the Government on a monthly basis upon completion of FAT and confirmation of a successful production decision. This information shall be included in the monthly status report, CDRL B001.

CDRL B001, DI-MGMT-80227, Contractor’s Progress, Status and Management Report

3.1.4.1 Planned Deliveries. The MCTWS must be worldwide supportable and shipped to Free On Board (FOB) destination. Quantity and location will be specified on each individual delivery order. Delivery locations and quantities are provided in Attachment D.

For OCONUS shipments, the contractor is responsible only for costs to the port of embarkation.

3.2 Government Furnished Property

3.2.1 Government Furnished Information (GFI). The Government will provide the GFI in the form of government drawing format and government drawing numbers. The Marine Corps Systems Command (MARCORSYSCOM) contracting office will provide access to the documents upon receipt of information requested in the instructions to contractor portion of the solicitation. The contractor shall notify the Government of any deficiencies in the GFI received.

3.2.2 Government Furnished Equipment (GFE). The Government will provide the contractor with a Basic Operator’s Bag (BOB), National Stock Number (NSN) 5180-01-580-7176, for each MCTWS as GFE.

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. For planning purposes, the Government estimates no more than five (5) reviews to be held at the Government’s location. 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. The contractor shall prepare agendas and conference presentation materials, and provide minutes and reports following each review. 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 B002.

CDRL B002, DI-ADMN-81249A, Meeting Agenda CDRL B003, DI-ADMN-81250A, Meeting Minutes

3.3.1.1 Post Award Meeting (PAM). A PAM will be held within 30 days after contract award. The purpose of the PAM 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.1.2 In-Process Review (IPR). 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. The contractor shall provide the SEMP at the Government’s request.

CDRL A001, DI-SESS-81785, Systems Engineering Management Plan

3.4.2 Technical Reviews. Technical reviews will be conducted in accordance with MARCORSYSCOM Order (MCSCO) 5400.5 - Naval Systems Engineering Policy and the MARCORSYSCOM Technical Review Handbook, Version 1.04.

3.4.2.1 Preliminary Design Review (PDR). The contractor shall participate in Preliminary Design Reviews (PDRs) culminating in a system level PDR and have all studies, estimates, analyses, designs, and reports available for the Government to review at least 30 days prior to the PDR. The PDR shall be used to resolve any issues in the performance specification; however it will not be used as an opportunity to impose additional requirements. The PDRs shall include each equipment, and hardware configuration item, and related peculiar support equipment, and entrance and exit criteria. The contractor shall show and/or demonstrate that evaluations of materials, lead times, tooling, fabrication techniques, assembly methods, test equipment, skills, processes, and inspection techniques have been accomplished for each equipment, and hardware configuration item, and related support equipment; that producibility objectives have been achieved, and also shall identify all single source, sole source, and diminishing source(s). This review will evaluate the progress, technical adequacy, technical data package and risk resolution (on a technical, cost, and schedule basis) of the design and will assess the technical risk associated with the selected manufacturing (assembly) methods (processes).

3.4.2.2 Critical Design Review (CDR). The contractor shall participate in the CDR scheduled by the Government to be conducted after contract award and prior to delivery of FAT and FUE assets. At the CDR, the contractor shall present and discuss the SEMP, the RTM, all certifications required in the PS, the Corrosion Prevention and Control Plan (CPCP), the Quality Management (QM) program, the electrical schematic, Finite Element Analysis (FEA) of the trailer design, the Transportability Report, and the Technical Data Package (TDP). The technical data package shall be 90% complete. In preparation for the CDR, the contractor shall provide all presentation materials, technical data, and reports to the Government at least seven (7) days prior to the scheduled CDR.

3.4.2.3 Test Readiness Review (TRR). The contractor shall participate in the TRR scheduled by the Government to be conducted prior to FAT 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 FAT 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 anaccurate TDP for establishing a product baseline to the Government at least seven (7) days prior to the scheduled TRR.

3.4.2.4 System Verification Review (SVR). The contractor shall participate in SVR scheduled by the Government to be conducted after completion of FAT 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 FAT 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 seven (7) days prior to the SVR.

3.4.2.5 Production Readiness Review (PRR). The contractor shall participate in the PRR scheduled by the Government to be conducted after the FAT 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 seven (7) days prior to the PRR.

3.4.2.6 Physical Configuration Audit (PCA). The PCA shall be performed upon completion of testing to verify the MCTWS and its configuration items (CIs) are accurate, complete, compatible, and that the CI has achieved the performance and functional characteristics defined in the functional configuration baseline. The Government and the contractor shall conduct the PCA jointly, at a time and place mutually agreed to, 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, function information is provided on control drawings for non-developmental items (NDI)/Commercial Off-The-Shelf (COTS) items; and confirm the drawings accurately represent the "as-built" production configuration. As part of the CM plan/process submitted with the proposal, the contractor shall provide an approach and proposed schedule for conducting the PCA and identification of the CIs/Computer Software Configuration Items (CSCIs) to be audited. The contractor shall participate and assist the Government in the execution of the PCA, using the guidelines contained in MIL-HDBK-61, section 8. 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. The product baseline will be established upon completion of the PCA and resolution of audit discrepancies.

In preparation for the PCA, the contractor shall provide all presentation materials and documents updated since the PRR to the Government at least seven (7) days prior to the PCA. Additional details for the PCA are established in the CM section of this SOW.

3.4.3 Requirements Traceability Matrix (RTM). The contractor shall document technical compliance in a RTM identifying how MCTWS compliance with each requirement in the PS 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 (CPC). The contractor shall develop a CPC plan that describes the specific measures to be implemented throughout the MCTWS. The purpose of the CPC plan is to document corrosion-related design decisions and identify materials and corrosion control methods used in the MCTWS. 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 PS. Changes in materials, coatings, or corrosion prevention methods during the course of production shall be reflected in updated versions of the CPCP per CDRL A002. 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 material control to ensure that the materials used in the MCTWS are shown on engineering drawings; and in-process measurements (number, type, frequency, locations) to ensure compliance with process instructions developed under b, above.

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

3.4.5 Reliability and Maintainability

3.4.5.1 Reliability and Maintainability (R&M) Program. The 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 (FRACAS). 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 Procurement Contracting Officer (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 PCO if quality issues dictate additional surveillance.

3.6 Producibility. The contractor shall develop a Producibility Plan that applies 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 Configuration Management

3.7.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 MCTWS. The principles contained in EIA-649, National Consensus Standard for Configuration Management, and MIL-HDBK-61, 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 submit their CM plan within 120 days after contract award. The Government shall 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.

CDRL B004, DI-CMAN-80858B, Contractors Configuration Management Plan

3.8 Environment, Safety, and Occupational Health (ESOH)

3.8.1 System Safety. The contractor shall identify and evaluate environmental, safety, and occupational 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. Residual 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 ESOH risks. The contractor must identify all safety risks and provide mitigation strategies in the system safety documentation.

3.8.1.1 Safety Assessment Report (SAR). As a result of system safety analyses, hazard evaluations, and any of the independent testing, the contractor shall perform and submit a safety assessment. The SAR shall identify all safety features of the hardware, system design and inherent hazards and shall establish special procedures and/or precautions to be observed by Government test agencies and system users. The contractor shall prepare a SAR which shall be submitted within 45 days of contract award. The contractor shall identify health hazards associated with the system and provide mitigation strategies and incorporate them into the SAR. In preparing the health hazard portion of the SAR, the contractor shall provide a description and discussion of each potential or actual health hazard for each subsystem or component. A health hazard is an existing or likely condition, inherent to the operation, maintenance, transport, or use of material that can cause death, injury, acute or chronic illness, disability, or reduced job performance of personnel by exposure to physiological stresses. The contractor shall include classification of severity and probability of occurrence, and when the hazards may be expected under normal or unusual operating or maintenance conditions. Include with the deliverable SAR, copies of Material Safety Data Sheets (MSDS)/Safety Data Sheets (SDS) for all hazardous materials incorporated into the system. Identify all data sources for the report and identify hazard severity, hazard probability and risk for each hazard. The final SAR is subject to Government approval. In the event the system is modified or procedural changes with regards to interfacing with the system are made after the final SAR is submitted, the contractor shall update the SAR to reflect those modifications or changes.

CDRL A003, DI-SAFT-80102B, Safety Assessment Report

3.8.2 Hazardous Materials Management Program (HMMP) and Pollution Prevention (P2). The contractor shall implement a HMMP and P2 in accordance with NAS 411. The contractor shall avoid the use of toxic chemicals, hazardous materials, and Ozone Depleting Substances (ODS) in the design, operational support and disposal of the MCTWS where possible. The HMMP shall establish a process to manage all requirements for asbestos, radioactive materials, cadmium, hexavalent chromium, and extremely toxic or hazardous materials in design, production, operation, and support. In some case, the only acceptable management process may be total elimination of the requirement. The use of Class I or Class II Ozone Depleting Chemicals (ODCs) is prohibited in the design or operational support of the system without specific written approval of the contracting officer. More information on chemicals and hazardous materials to be avoided can be obtained from the Environmental Protection Agency (EPA).

3.8.2.1 Hazardous Materials Management Program and Pollution Prevention Plan. The contractor shall provide a HMMP and P2 Plan to the Government for review and approval. The HMMP shall be provided within 45 days of contract award. The HMMP Plan shall define the contractor's approach to assure that consideration is given throughout all acquisition phases of the system; hazardous materials and processes associated with each contract hardware deliverable item are selectively identified and evaluated based on environmental and health concerns; and hazardous material elimination, minimization, or control are considered and detailed in the system design and the manufacturing process.

CDRL A003, DI-SAFT-80102B, Safety Assessment Report

3.8.3 Material Safety Data Sheets/Safety Data Sheets (MSDS/SDS). The contractor shall make available MSDS/SDS to the Government for review no less than 7 days prior to CDR.

3.8.4 Environmental Considerations. The contractor shall provide information on the potential for any adverse environmental impacts from the manufacturing, operation, maintenance, and disposal of the MCTWS. This information will be used to assist the Government in making a preliminary National Environmental Policy Act (NEPA) decision and in the preparation of formal NEPA documents, which include Categorical Exclusion (CATEX), Environmental Assessment (EA), and Environmental Impact Statement (EIS). Such environmental impacts include air, soil, wetlands, water, flora, fauna, endangered species, emissions and toxic waste resulting from development, maintenance (coatings and primers), operation, disposal, etc.

3.8.5 Environment, Safety, and Occupational Health (ESOH) Compliance Assessment. The contractor shall provide the Government with an assessment of applicable ESOH laws and regulations, identifying any potential compliance issues.

CDRL A003, DI-SAFT-80102B, Safety Assessment Report

3.8.6 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.

3.8.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 Engineering Change Proposals (ECP) and Request for Deviation (RFD). Sufficient supporting data to evaluate the proposed change, such as drawings, supplemental drawings, sketches, specifications, or manufacturer's data sheets, shall be submitted with ECPs and RFDs. 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.8.7.1 Engineering Change Proposals (ECPs). ECPs shall be submitted by the contractor, and shall be limited to those, which are necessary or offer significant benefit to the Government. MIL-HDBK-61 provides guidance concerning the classification of ECPs. Class I ECPs 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 ECPs shall be submitted by the contractor to the PCO for approval for those engineering changes, which impacts none of the factors listed above. As a minimum, Class I ECPs 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, Commercial and Government Entity (CAGE) code, revision level, etc.); (i) Title of change; (j) Description of change; (k) Effect on interfaces (interchangeability and interoperability); (l) Total costs/savings with breakout; (m) Retrofit information; (n) ODS; (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.

3.8.7.2 Requests for Deviation (RFD). The contractor shall submit all RFDs 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 ECP. MIL-HDBK-61 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.

3.8.7.3 Notification of Changes to Commercial Equipment. The contractor shall submit notification to the Government when changes occur to commercial equipment, which is being procured or fabricated by the contractor as commercial-off-the-shelf, and the Government does not control the developer’s design. The contractor shall submit a change notice to the Government implementing any Class II ECPs and the Government will approve/disapprove the class designation of the ECP.

3.9 Technical Data Package Requirements

3.9.1 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. All drawings in this Product Level Drawing Package shall comply with ANSI Y14.100, ASME Y14.24 and ASME Y14.34. This Product Level 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 Level Drawing Package shall also include control drawings for all COTS items that do not conform to recognized Government or industry specifications, NDI, and items developed at private expense for which the Government has not acquired unlimited rights. These control drawings shall provide the applicable PS 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 Level Drawing Package or the system design.

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

3.10 Verification

3.10.1 Contractor Certification. The contractor shall provide the necessary data to verify MCTWS technical compliance with performance requirements as established in the PS. 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 at least 14 days prior to FAT.

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 is estimated to take between three (3) to six (6) months. The contractor shall be on site for training of test personnel on operation of the system prior to testing commencing. The contractor will also be required be onsite at Aberdeen within 24hrs of a major test failure. 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 MCTWS 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 TIRs generated by the Government test agency throughout FAT and the FUE within seven (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 corrective actions approved by the Government within a timeframe that does not cause delays in program schedule.

3.10.3 First Article Test (FAT) Assets. In the event the FAT assets fail to meet requirements established in the PS, 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 FAT.

3.10.4 FAT/FUE Refurbishment. If the FAT/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 the MCTWS and all components within. The contractor shall be responsible for all pass through warranties associated to materials and components not manufactured by the contractor. Warranties shall become effective upon delivery and acceptance by using unit. 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 using 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 Continental United States (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 Outside Continental United States (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 Warranty Service and Support Claims Tool (WSSCT) to manage all warranty claims under this contract pertaining to the MCTWS. 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, who conduct warranty repairs and repair consult, shall also establish accounts in the WSSCT to support the MCTWS. 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:

1. CONUS: 7 Days – Parts and repair

2. OCONUS: 14 Days – Parts and repair

3. Contingency Operations: 14 Days – Parts only

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

1. Labor

2. Time and travel

3. Parts

4. 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 conduct maintenance planning to define maintenance activities, which fully support the USMC two (2) levels of maintenance concept. The two (2) levels of maintenance include field and depot levels. Design influence for maintenance planning and ease of maintenance should be considered at all times. The maintenance of the MCTWS 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 TMs. Operator maintenance tasks will be performed using tools from the Basic Issue Items (BII) or the General Mechanics Tool Kit (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 GMTK tools, Common 20, 22 and 30. Intermediate maintenance is performed by Marines with MOS 1341.

4.3.3 Support Equipment. The MCTWS 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.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.5 Provisioning

4.5.1 Provisioning Guidance Meeting (PGM). The contractor shall participate in the 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 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 the BOM/ LSA-036 Report for standardization or NSN identification of all “P” source-coded items. This screening will be in accordance with GEIA STD-0007 for provisioning purposes. The contractor shall conduct provisioning screening using Federal Logistics Record (FED LOG), Federal Logistics Information System (FLIS), WebFLIS, or by batch submittal part numbers to Defense Logistics Information System (DLIS). The contractor shall screen for all common hardware items (nuts, bolts, screws, washers, lock washers, rivets, etc.) by technical characteristics. The screening results must be available to review at each provisioning meeting.

4.5.4 Provisioning Technical Documentation. The contractor shall provide provisioning technical documentation to include a BOM, Common Hardware Items/Standard Item Use List, Long Lead Time Items List (LLTIL), BII, Common and Bulk Items List (CBIL), Power Sources List (PSL), Design Change Notices (DCN), Supplemental Data For Provisioning (SDFP)/Engineering Data For Provisioning (EDFP) and the Provisioning Parts List/ LSA-036 Report IAW DI-SESS-81759A.

The BOM, BII, LLTIL, CBIL and the PSL shall be delivered, in a Microsoft compatible format, 30 days after PDR.

4.5.4.1 Bill of Material. The contractor shall provide the Government with an Engineering BOM containing a list of all new parts and components used in MCTWS. The BOM list shall include at a minimum, the nomenclature, NSN (if available), part number, quantity and description.

CDRL C001, DI-SESS-81759A, Bill of Material

4.5.4.2 Common Hardware/Standard Item Use. The contractor shall utilize parts and assemblies that have been assigned a NSN to the maximum extent practical. This includes common hardware and standard items, such as all standard hardware, fasteners, hydraulic and air fittings, hoses, o-rings, electrical connectors, etc. All standard items will be industry standard or government specification compliant and identified as such. Government specification refers to any specification under Government control (for example: MIL-STD). The use of standard items minimizes the overall logistics footprint of the system and avoids the duplication of stocked parts with identical form, fit, and functionality under different part numbers and NSNs. A partial listing of acceptable industry standards includes: ASTM, ASME, AISI, ANSI, DIN, JIC, SAE, etc. A partial listing of Government specifications includes: AE, AS, FED, DOD, MS, MIL, MIL-STD, MS, NATO, etc. Examples of fasteners which fall under the common hardware/standard item category are listed below:

a. ASME B18.2.1 (Use BH Series), bolt, steel, hex head

b. MS35307, bolt, stainless steel, hex head

c. MS16998/NAS1351, bolt, steel, socket head

d. ASME B18.6.3, screw, stainless, steel, hex head

e. MS16995, screw, steel, socket head

f. MS51967, nut, steel, plain, hexagon

g. MS51971, nut, stainless steel, plain, hexagon

h. MS15795, washer, stainless steel, flat

i. ASME B18.21.1, washer, steel, flat

j. MS35338, washer, stainless steel and steel, lock

4.5.4.2.1 Common Hardware/Standard Items Data. The contractor shall provide the detail or vendor item drawings for any common hardware/standard items proposed for use in the MCTWS. Guidance for detail and vendor item drawings is provided in paragraphs regarding SDFP/EDFP submission.

4.5.4.3 Long Lead Time Items List. The contractor shall provide a LLTIL that shall contain those items which, because of their complexity of design, complicated…