SCO_RFP_Attachment_1_Statement_of_Work_13Sep19.pdf

Attachment 1, Statement of Work

Solicitation M67854-19-R-1535

1 Summary

1.1 Scope. This Statement of Work (SOW) sets forth the requirements for the procurement, manufacturing, program management support, Configuration Management (CM), warranty repair, Interim Contract Logistics Support (ICLS), technical documentation, and training for the

Squad Common Optic, hereafter referred to as SCO.

1.2 Background. The mission of the SCO program is to provide United States Marine Corps

(USMC) infantry and infantry-like communities with weapon optics optimized in their configuration for individual and squad small arms that will improve situational awareness, decrease engagement times, and increase Probability of Hit (P(h)) commensurate to the effective range of the weapon and its munitions. Intended for use with infantry assault rifles, the SCO is a magnified optic to improve target acquisition and P(h) between 0-600 meters (m). The SCO includes a non-caliber specific reticle, is variable power, and incorporates a user selectable illuminated or non-illuminated aim-point.

2 Applicable Documents

2.1 Department of Defense Specifications, Standards, and Handbooks

PS-SCO-001 Specification PS-SCO-001: Performance Specification for the

Squad Common Optic

MIL-STD-130N(1) Identification Marking of U.S. Military Property, 16 Nov 2012

2.2 Availability of DOD Documents. Unless otherwise specified, the issues of these documents may be viewed or downloaded from the ASSIST database at http://quicksearch.dla.mil/.

2.3 Non-Government Standards and Other Publications.

ASQ/ANSI/ISO 9001:2015 Quality Management Systems– Requirements, 21 Oct 2015

ANSI/EIA-649-B Configuration Management Standard, Apr 2011

2.4 Availability of Non-Government Standards and Other Publications. Non-Government

Publications are available from the American National Standards Institute, 25 West 43rd Street, 4th floor, New York, NY 10036, or at http://webstore.ansi.org/default.aspx.

2.5 Order of Precedence. In the event of a conflict between the text of this document and the references cited herein, the text of this document shall take precedence. Nothing in this document shall supersede applicable federal, state, or local laws and regulations unless a specific exemption has been obtained.

Source Selection Information – See FAR 2.101 and FAR 3.104

3 Requirements

3.1 General. The Contractor shall deliver SCO systems in accordance with (IAW) this SOW and the performance requirements contained in the Performance Specification reference identified in paragraph 2.1 referred herein as Performance Specification. The Contractor shall provide all material, services, and necessary support documentation needed to complete the tasks identified within this SOW.

3.1.1 A complete SCO system includes a day scope, scope mount, elevation turrets caps, windage turrets caps, lens covers, reticle battery, operator manual (hard copy), Quick Reference

Guide (QRG), required tools, lens cleaning kit, soft carrying case, scope cover, and any other accessories necessary for operational use.

3.1.2 If the day scope and scope mount are not integrated, the Contractor shall deliver the SCO system with the day scope mounted to the scope mount IAW the performance requirements contained in the Performance Specification.

3.1.3 The SCO shall integrate, be compatible with, and cause no degradation in function to the

M27, M4, and M4A1 weapons platforms using the MIL-STD-1913 rail. Additionally, the SCO should be compatible with current visual augmentation systems, weapons accessories, lasers, and clip-on night vision devices using a MIL-STD-1913 rail interface.

3.2 Program Support

3.2.1 Program Management. The Contractor shall develop and execute a plan to manage the

SCO Program. The Contractor shall be responsible for overall SCO performance and shall define and maintain appropriate subcontract and associated contract relationships to support all contract requirements. The Contractor shall designate a point of contact responsible for substantive communication with the Government.

3.2.2 Post-Award Conference. A Post-Award Conference shall be held at the Contractor’s facility within 30 calendar days after contract award. An exact date for the conference shall be mutually agreed upon after contract signing. The conference will specifically discuss all sections of the contract in detail with emphasis on programmatic points of interest, to include manufacturing readiness, quality management, requirements compliance, and product support activities. The conference may include contracting officers, program managers, and essential personnel from both parties. The Contractor shall take meeting minutes and provide a copy to the Government within seven calendar days after the conclusion of the conference. (CDRL

A001, Report, Record of Meeting/Minutes)

3.2.3 Provisioning Guidance Conference. The Contractor shall host a Provisioning Guidance

Conference (PGC) during the Post-Award Conference. The Government will chair the PGC.

The purpose is to discuss the contractual requirements pertaining to Logistics Data Products and conduct a preliminary supportability demonstration. The Contractor shall take the meeting minutes and provide a copy to the Government within seven calendar days after the conclusion of the conference, (CDRL A001, Report, Record of Meeting/Minutes).

The PGC Agenda will be:

1) The format and medium of delivery

2) Unique Government requirements

3) Unclear provisioning or cataloging related areas

4) Operator/maintenance manual, packaging and technical publications deliverables

5) Provisioning Performance Schedule (PPS) and schedule of periodic submissions for

Government review

6) Common understanding of the overall logistics requirements

7) Organic maintenance activities at the user level during the period of ICLS

3.2.4 Provisioning Conference. The Contractor shall host the Provisioning Conference no later than 90 calendar days after the Post-Award Conference. An exact date shall be mutually agreed between the Contractor and the Government. The Provisioning Conference will last no longer than one calendar day. The Contractor shall take meeting minutes and provide a copy to the

Government within seven calendar days after the conclusion of the conference (CDRL A001, Report, Record of Meeting/Minutes).

3.2.5 Production Readiness Review. A Production Readiness Review (PRR) shall be held at the Contractor’s facility within 30 calendar days after Government completion of Production

Verification Testing (PVT). An exact date shall be mutually agreed between the Contractor and the Government. The PRR shall address SCO performance at PVT and evaluate manufacturing readiness, quality management, requirements compliance, and product support activities. The

Contractor shall take the meeting minutes and provide a copy to the Government within seven calendar days after the conclusion of the conference. (CDRL A001, Report, Record of

Meeting/Minutes)

3.2.6 Maintenance and Supportability Demonstration.

The purpose of the Maintenance and Supportability Demonstration is to verify that the logistics related requirements of the Performance Specification have been implemented and that the logistics resources required to support the system/equipment are available, complete, and support the Warfighter’s mission. The Maintenance and Supportability Demonstration shall include human factors engineering, health hazards, safety, manpower, personnel and training, parts interchangeability and maintainability.

The Contractor shall develop and implement maintenance support capabilities that will transition to full organic support conducted by the USMC. The Contractor shall plan and conduct a

Maintenance and Supportability Demonstration (MSD) event at the Contractor’s facility to provide tangible demonstration of meeting the Integrated Product Support Element contract requirements. The MSD shall occur within 180 days after contract award. An exact date shall be mutually agreed between the Contractor and the Government. The Contractor shall provide production representative equipment for disassembly to verify all provisioning documentation.

The MSD shall demonstrate:

1) Maintainability goals: verify achievement of maintainability goals and to identify and correct supportability deficiencies.

2) Life-Cycle Initiatives: identification of needed improvements to materiel design for improved supportability and reduced life-cycle cost.

3) System safety: verify system safety label/markings and mitigation of operational and maintenance hazards, to confirm the safety of all procedures, tasks, and system labels.

4) Equipment publications: review and verify the equipment maintainer publication includes:

a. Detailed theory of operation, including functional theory of operation, component theory, and schematic diagrams.

b. Fault diagnosis procedures: confirm fault diagnosis procedures utilizing SCO system-level fault isolation support solution.

c. Maintenance tasks and procedures: confirm maintenance tasks/procedures and repair/replacement procedures through the removal and replacement of component

SCO major assemblies and sub-assemblies. Demonstrate maintenance processes that are applicable to each level of maintenance within the USMC.

d. Illustrations: verify all illustrations match actual equipment configuration as well as the task sequencing for fault isolation and SCO disassembly/assembly procedures.

e. Contractors Technical Manual Validation Letter.

3.2.7 Maintenance and Supportability Demonstration Report. The Contractor shall develop and submit a final MSD Test Report documenting the results of the MSD within 30 calendar days of completion of the MSD. Preceding submission of the final MSD Report, the Contractor shall provide a quick-look report within five calendar days of the MSD to the Government program office. Any failures that occur during the MSD shall be documented by the Contractor in the MSD Report. Should failures occur, the Contractor shall conduct Government-approved follow-on regression testing/demonstrations. The Government will approve the MSD Report when all requirements have been met. (CDRL A002, Maintenance and Supportability

Demonstration Report)

3.2.8 Program Review. The Contractor shall be responsible for participating in program reviews on dates and locations mutually agreed upon with the Government. Program reviews are convened when required by the Government and may be conducted via teleconference (primary method) or at the Contractor’s facility (alternate method). Program reviews will commence during the first quarter of the second twelve month ordering period and occur as required thereafter. These reviews shall serve as a forum to resolve issues and exchange information in support of testing, production, repair, logistics support, ICLS, and delivery of the SCO.

Contractor performance discussions shall include but are not limited to schedule, technical performance, risk elements and assumptions, work-around plans, anticipated problems, and program status. The Contractor shall ensure that appropriate personnel are available for conferences and reviews to address and resolve agenda items. The Contractor shall take the meeting minutes and provide a copy to the Government within seven calendar days after the conclusion of each review. (CDRL A001, Report, Record of Meeting/Minutes)

3.2.9 Monthly Status and Progress Reports. The Contractor shall provide monthly progress reports identifying the status of delivery orders, warranty repairs, ICLS, data deliverables, failure analysis and corrective actions, Engineering Change Proposals (ECP), requests for variance, programmatic issues, technical issues, significant meetings, upcoming events, and milestones.

The Contractor shall participate in monthly telephone conferences to review the monthly status and progress reports, with exact dates and times mutually agreed upon with the Government.

(CDRL A003, Contractor’s Progress, Status and Management Report)

Table 1-1: Meetings, Formal Review, Conferences and Audits

Event Frequency Time Frame Location

Post-Award

Conference Once

Within 30 calendar days of contract award Contractor’s Facility

Provisioning

Guidance

Conference

Once During the post-award conference Contractor’s Facility

Provisioning

Conference Once

No later than 90 calendar days after the post-award conference Contractor’s Facility

Production

Readiness

Review

Once Within 30 calendar days after

Government completion of PVT Contractor’s Facility

Maintenance

& Supportability

Demonstration

Once Within 180 calendar days after

Contract award Contractor’s Facility

Program

Reviews As required

Commencing during the first quarter of the second twelve month ordering period

Teleconference or

Contractor’s Facility

3.3 Quality

3.3.1 Quality Program. The Contractor shall have a quality system that ensures conformance to contractual requirements and meets the requirements of ASQ/ANSI/ISO 9001:2015, or an equivalent quality system model. (Contract Data Requirements List (CDRL)) A004, Quality

Assurance Program Plan)

3.3.2 Quality Conformance Inspections and Tests. The Contractor shall develop an

Acceptance Test Plan (ATP) and submit to the Government for review. The Contractor shall ensure each SCO undergoes Contractor acceptance testing conducted in accordance with the

Government approved ATP. The Contractor shall inspect and verify all equipment at source.

The Contractor shall only deliver items to the Government that have successfully passed the

Contractor’s ATP. (CDRL A005, Acceptance Test Plan)

In addition to the ATP, the Contractor shall submit Test Procedures for Government review and approval. (CDRL A006, Test Procedure)

3.3.3 Quality Conformance Inspection and Test Results. The Contractor shall provide inspection and test results for SCO systems produced for this contract. (CDRL A007, Acceptance Test Report (ATR))

3.4 Reliability, Maintainability, and Availability

3.4.1 Failure Reporting, Analysis and Corrective Action System. The Contractor shall establish a failure analysis and corrective action system for equipment and process reliability that includes requirements for reporting, analyzing, and correcting system failures. The Contractor shall analyze the cause of each failure that occurs during Government acceptance testing of new production systems and systems returned to the Contractor for repair. The Contractor shall identify pattern failures. The Contractor shall analyze these failures and implement corrective action to prevent or reduce the probability of failure recurrence. The Contractor shall submit a report detailing the investigation and analysis of the failure, as well as the corrective actions to be implemented. Nothing in this section shall be construed as relieving the contractor of the responsibility to implement corrective actions, conduct repair, or adhere to the performance requirements contained in the Performance Specification. (CDRL A008, Failure Summary and

Analysis Report)

3.4.2 Performance. The Contractor shall notify the Government immediately after identification of any and all performance-related data that would both positively and negatively impact the performance, schedule, reliability, maintainability, availability, supportability, cost, or safety of the SCO. The Government reserves the right to test, validate, verify, or certify any and all of the SCO performance parameters to verify compliance with the Performance Specification and this SOW.

3.5 Safety. The system safety requirements are to be performed throughout the life cycle of the system, along with new development, upgrades, modifications, resolution of deficiencies, or technology development. When properly applied, these requirements shall ensure the identification and understanding of all known hazards and their associated risks, and mishap risk eliminated or reduced to acceptable levels. The objective of system safety is to achieve acceptable mishap risk through a systematic approach of hazard analysis, risk assessment, and risk management.

3.5.1 System Hazards. The Contractor shall perform system hazard analyses and prepare a

System Safety Hazard Analysis Report (SSHAR). The SSHAR shall identify hazards present during system use, maintenance, storage, transportation, and disposal. The SSHAR shall include a risk assessment and risk management recommendations for each identified hazard. (CDRL

A009, System Safety Hazard Analysis Report (SSHAR))

3.5.2 Environmental and Hazardous Materials (HAZMAT). The Contractor shall have an established environmental and HAZMAT program to ensure the system design, development, manufacturing, testing, evaluation, operations, and maintenance comply with federal, state, and local environmental laws, regulations, shipping regulations, policies, treaties, and agreements.

The Contractor shall identify the type, quantity, and potential hazards for all HAZMAT contained in the SCO system in the SSHAR. The Contractor shall provide Safety Data Sheets for all HAZMAT identified. (CDRL A009, System Safety Hazard Analysis Report (SSHAR))

3.5.3 HAZMAT Removal. If the SCO contains HAZMAT, the Contractor shall provide instructions in the Maintenance technical manual detailing the processes and hazards associated with removing the HAZMAT from the SCO prior to demilitarization and disposal.

3.6 Configuration Management. The Contractor shall implement a CM Control system using

ANSI/EIA-649-B as a guideline. The CM Program shall be in place for the life of the contract.

The Contractor’s CM Program shall provide configuration identification, configuration control, and configuration status accounting of all new and/or modified hardware, firmware, software, and documentation IAW ANSI/EIA-649-B. The Program shall address the Contractor’s procedures for CM, configuration review, preparation, and processing of configuration changes.

The SCO initial product baseline shall be established at the time of contract award. The

Contractor shall only make changes to the established baseline after Government approval of

ECPs and contract modification. The Contractor shall support interchangeability and interoperability to the replaceable part level. All baselines shall be documented in the

Contractor’s CM database. (CDRL A010, Product Baseline Index (PBLI))

3.6.1 Configuration Management Plan. The Contractor shall provide the Government with a

CM Plan that describes the Contractor’s Configuration Management program. (CDRL A011, Supplier's Configuration Management Plan)

3.6.2 Configuration Status Accounting. The Contractor shall maintain Configuration Status

Accounting information in a CM database. The CM database shall include the as-built configuration, part number, serial number, revision levels, Acceptance Test Date, Software

Revision, and all Class I ECPs incorporated for each system as delivered. The Government reserves the right to review the Contractor’s CM database upon request and the Contractor shall provide delivery of the electronic CM database at the conclusion of this contract. The

Government will utilize the Contractor’s CM database as the single tracking system for configured hardware and software items for the SCO. (CDRL A012, Configuration Status

Accounting (CSA) Information)

3.6.3 Engineering Change Proposal. The Contractor shall implement and control changes to the ECP process for Government directed, Contractor recommended and Government approved changes per ANSI/EIA-649-B. The Contractor should notify the Government if the ECP is of a nature that, without implementation, will adversely affect the system’s performance, personnel safety, or impact delivery schedules as part of the submission.

3.6.3.1 Class I ECP. The Contractor shall submit changes that may affect the form, fit, function, cost or safety of a configuration item as a Class I ECP. The Contractor shall submit

Class I ECPs for Government review and approval. The Contractor shall obtain Government written concurrence prior to the release of the Class I change. Implementation prior to

Government approval is at the risk of the Contractor. (CDRL A013, Engineering Change

Proposal (ECP))

3.6.3.2 Class II ECP. For an ECP that does not fall under the Class I ECP criteria, the

Contractor shall submit a Class II ECP for review. The Government review of Class II changes will consist of a concurrence or non-concurrence with the classification category and content.

The Government reserves the right to require a proposed Class II ECP to be resubmitted as a

Class I ECP if it is determined to affect form, fit, function, cost or safety. The Contractor shall obtain Government written concurrence prior to the release of the Class II change.

Implementation prior to Government concurrence is at the risk of the Contractor. (CDRL A013, Engineering Change Proposal (ECP))

3.6.3.3 Design Change Notifications. The Contractor shall submit notifications to the

Government when changes occur to commercial equipment, which is being procured or fabricated by the Contractor as off-the-shelf, and the Government does not control the developers design.

3.6.4 Request for Variance. The Contractor shall submit any temporary departure from the product baseline or Performance Specification for a specified serial number, range of serial numbers, or period of time as a Request for Variance (RFV). RFV shall be submitted for

Government review and acceptance. Implementation prior to Government approval is at the risk of the Contractor. (CDRL A014, Request for Variance (RFV))

3.7 Repair

3.7.1 Warranty Repair. The Contractor shall warrant their product against defects in manufacturing and workmanship in accordance with the terms of their standard commercial warranty. This also applies to warranties on all subcontractor-furnished components. All SCO systems returned for repair under the warranty provisions of this contract shall be subject to failure analysis by the Contractor at the Contractor’s expense. The Contractor shall be responsible for having sufficient quantity of spares and replacement parts on hand to perform warranty repair. The Contractor shall be required to replace all damaged markings, identifications, and labels when the markings, identifications, or labels become unreadable IAW

MIL-STD-130N(1) and the Performance Specification. All failures returned to the Original

Equipment Manufacturer for repair will have a Return Material Authorization (RMA) number assigned by the Contractor.

3.7.1.1 Warranty Failure Analysis. The Contractor shall perform failure analysis and submit a

Failure Summary and Analysis Report within 14 calendar days after receipt of failed SCO.

(CDRL A008, Failure Summary and Analysis Report)

3.7.1.2 Warranty Repair Turn-Around Time. The Contractor shall provide a new SCO system if the failed system cannot be repaired and returned to the Government within 30 calendar days after receipt of item. The Contractor shall return items for warranty repair to the Government at the Contractor’s expense.

3.7.1.3 Warranty Repair to Specification Standards. SCO systems repaired or replaced under warranty shall meet the contractual product baseline. All repaired or replaced systems shall be tested IAW the same tests used for initial acceptance. New replacement assets shall have the same warranty as all other new assets. Repaired systems shall be returned with the balance of the original warranty period.

3.7.2 Refurbishment of Initial Deliveries. The Contractor shall refurbish SCOs used in support of Government testing, supportability demonstration, and Instructor and Key Personnel Training events. The Contractor shall refurbish systems to like-new condition and deliver them as part of the contract quantity, provided the systems are repairable within the Beyond Economical Repair limit of 65% of system cost. Refurbished systems shall be tested IAW the same tests used for initial acceptance.

3.7.3 Interim Contractor Logistics Support. ICLS may be implemented for the SCO program for a period of up to 60 months after contract award. During the ICLS period, upon receipt of a system requiring non-warranty repair, the Contractor shall inspect and conduct Test and Failure

Analysis. The Contractor shall repair/restore the SCO to comply with the Performance

Specification or recommend condemnation. All repaired SCO systems shall undergo repair verification testing IAW the same tests used for initial acceptance.

When providing ICLS the Contractor shall perform a receipt inspection, a determination of fault, and conduct three levels of repair: Level 1 minor repair, Level 2 moderate repair, and Level 3 major repair. For Level 1 minor repair, the cost of repair shall not exceed 10% of the proposed

SCO unit price. For Level 2 moderate repair, the cost of repair shall not exceed 40% of the proposed SCO unit price. For Level 3 major repair, the cost of repair shall not exceed 65% of the proposed SCO unit price.

The Contractor is not required to restore systems submitted for ICLS to a like-new cosmetic condition; however, the Contractor shall repair damage to protective finishes to the extent necessary to maintain corrosion prevention and structural integrity. The Contractor shall replace all damaged markings, identifications, and decals if the markings, identifications, or decals become unreadable. The Contractor shall ensure all repaired, upgraded, or modified systems meet or exceed the Performance Specification.

3.7.3.1 Receipt and Inspections. Upon receipt at the Contractor’s facility, the Contractor shall check for the SCO identification, visible damage or mishandling, and the completeness and accuracy of accompanying documentation. The Contractor shall bring deficiencies it finds during the incoming inspection to the attention of the Government program office.

3.7.3.2 Inspection and Acceptance. The Contractor shall ensure that each repaired and serviceable SCO is packaged IAW best commercial practices to protect the item during shipment.

3.7.3.3 Time Constraints. The Contractor shall acknowledge receipt of non-warranty systems within two calendar days. The Contractor shall conduct ICLS actions and return the SCO system within 30 days of receipt at the Contractor’s facility.

3.7.3.4 Transportation. The Contractor shall establish transportation processes and procedures for equipment returns to the Government. Equipment returned to the Contractor by the

Government for repair will be returned at the Government’s expense. The Contractor shall return items for non-warranty repair to the Government at the Government’s expense.

3.7.3.5 ICLS Tracking. The Contractor shall track shipments from its facility to the item’s receipt at Marine Corps Logistics Base, Albany, GA. The Contractor shall immediately notify the Government about any shipping problems or delivery delays.

3.8 Technical Data

3.8.1 Copyright Release. Regardless of the commercial determination of technical data provided, all manuals, guides, drawings, associated lists, and other documents delivered to the

Government shall include the approved copyright release statements.

3.8.2 Operator and Maintenance Technical Manuals and Quick Reference Guides. The

Contractor shall provide Operator and Maintenance technical manuals for the SCO systems procured under this contract. The Operator and Maintenance technical manuals, at a minimum, shall include an Introduction, Preparation for Use and Installation, Principles of Operation, Boresighting Procedures and targets, Zeroing Procedures and targets, Maintenance and Servicing

Instructions (preventive and corrective), Preparation for Shipment, Parts List, Operational and

Maintenance Illustrations, Safety Precautions (warnings, cautions, and notes), and information on the functionality of the SCO, its components and accessories, system operation from turn-on to system shut down including adjustments, and operator checks and services. The Operator technical manual shall be no larger than 4 ½ inches wide by 5 ½ inches high. The Maintenance technical manual shall be no larger than 8 ½ inches wide by 11 inches high. In addition to the

Operator and Maintenance technical manuals, the Contractor shall provide a QRG. The QRG shall contain mounting, basic adjustment and operating procedures required to use the SCO in the field. The Contractor shall provide a Government-approved Operator technical manual and

QRG with each delivered SCO. (CDRL A015, Commercial Off-the-Shelf (COTS) Manuals and

Associated Supplemental Data)

3.8.3 Drawings and Associated Lists. The Contractor shall provide a top-level system drawing for the SCO. The Contractor shall provide a drawing for each Line Replaceable Unit (LRU) that can be removed and replaced. The top-level drawings for the SCO system and LRUs will be used for the purpose of nomenclature and National Stock Number (NSN) assignments to support the life cycle management of the system, including maintenance and repairs. The latest revision of drawings shall be submitted to the Government throughout the life of the contract. The SCO and its LRUs will have a unique NSN, which will be provided to the Contractor, unless NSNs have already been assigned. (CDRL A016, Engineering Data for Provisioning)

3.8.4 Documentation Updates. If configuration changes are made, the Contractor shall ensure the technical data and documentation reflects the approved product baseline for the life of the contract.

3.9 Supply Support.

3.9.1 Engineering Data for Provisioning. The Contractor shall employ the concept of concurrent release of spare parts orders with identical parts as installments on the production unit. The Contractor shall provide a recommended spare parts list of all SCO parts that can be removed and replaced. The spare parts list shall be delivered in a top-down breakdown format and shall include repairable replacement parts, and long lead time items from the LRU to the piece part level. Each spare part that is repairable/replaceable shall be priced and available for ordering. Failure by the Contractor to specify spare part determinations for individual items does not preclude the Government from requiring the Contractor to furnish and deliver the item and quantity of each item of spare and repair parts selected and approved by the Government to make up the provisioning parts. The spare parts list shall identify each part as an operator spare, maintenance spare, or ancillary item and contain the part number, nomenclature, Commercial and Government Entity (CAGE) code, order quantity, part-specific technical information to be used for NSN cataloging, and unit price for each part. The Contractor shall provide the

Engineering Data for Provisioning (EDFP) 30 days prior to the Provisioning Conference.

(CDRL A016, Engineering Data for Provisioning (EDFP))

3.9.2 Shipping Documentation. The Contractor shall furnish documentation for each shipment of new items that clearly identifies the contract number, delivery order number, Wide Area

Workflow (WAWF) shipment number, contract line item number, NSN, part number, and quantity shipped. Warranty return shipment documentation shall reference the RMA under which the item was returned, NSN, part number, and quantity shipped. The Contractor shall include a serial number listing in ascending numerical order with all shipments. For all new item shipments, a serial listing in Microsoft Excel format shall be attached to the WAWF receiving report.

3.9.3 Shipment Tracking. The Contractor shall ship all SCO systems via traceable means and shall provide tracking information to the Government upon request.

3.9.4 Signed Receipts. The Contractor shall provide a signed copy of the shipping document to the Government within two business days of receipt of returned SCO systems.

3.9.5 Packaging, Handling, Storage, and Transportation. The Contractor shall establish/maintain procedures for packaging, handling, storage, preservation, and shipping to protect the quality of products and prevent damage, loss, deterioration, degradation, or substitution of products. The Contractor shall also ensure when the SCO is in its standard shipping container, it shall withstand, without physical damage or degradation of performance, commercial modes of transportation.

3.9.6 Labeling and Marking. Each delivered SCO system shall have both the 2D Unique

Identification barcode and human readable text in accordance with MIL-STD-130N(1) and the

Performance Specification.

3.10 Training.

3.10.1 Copyright Release. Regardless of the commercial determination of technical data provided, all manuals, guides, drawings, associated lists, videos and other documents delivered to the Government shall include the approved copyright release statements

3.10.2 New Equipment Training Curriculum and Materials. The Contractor shall provide a New

Equipment Training (NET) package to support Operator and Maintainer training as described in paragraphs 3.10.2.1, 3.10.2.2, 3.10.2.3, and 3.10.2.4. The Contractor shall grant the Government the authority to reproduce, update, or change the data contained in the NET curriculum and materials. (CDRL A017, Training Materials)

3.10.2.1 Operator NET Course Curriculum. The Operator NET Course Curriculum shall be comprised of all actions that the equipment user is required to perform to mount, operate, and maintain the SCO in the field. Operating functions shall include actions required to power the sight on and off, change batteries, boresight, zero, and perform other adjustments. Specific

Tactics, Techniques, and Procedures (TTP) shall not be included. (CDRL A017, Training

Materials)

3.10.2.1.1 Targets. The Contractor shall provide a target for boresighting the SCO with the M27, M4, and M4A1 weapons platforms. The Contractor shall provide a target for 100m zeroing the

SCO with the M27, M4, and M4A1 weapons platforms.

3.10.2.2 Operator NET Training Video. The Contractor shall provide a NET video demonstrating all actions that the equipment user is required to perform to mount, operate, and maintain the SCO in the field. Operating functions shall include actions required to power the sight on and off, change batteries, boresight, zero, and perform other adjustments. Specific TTP shall not be included. The video shall not exceed thirty minutes in length. (CDRL A017, Training Materials)

3.10.2.3 Maintainer NET Course Curriculum. The Maintainer NET Course Curriculum shall be comprised of preventive maintenance, troubleshooting, LRU removal and replacement, adjustment, and performance verification procedures to be conducted at operator, intermediate, and depot-level maintenance facilities, if required. (CDRL A017, Training Materials)

3.10.2.4 Maintainer NET Training Video. The Contractor shall provide a NET video demonstrating all actions that the equipment maintainer is required to perform. Maintenance functions shall include actions required to perform preventive maintenance, troubleshooting, LRU removal and replacement, adjustment, and performance verification procedures to be conducted at operator, intermediate, and depot-level maintenance facilities. The video shall not exceed one hour in length. (CDRL A017, Training Materials)

3.10.3 Instructor and Key Personnel Training. The Contractor shall provide Operator and

Maintainer NET to Government technical representatives at a government facility within the continental United States. Training shall be for a maximum of 12 personnel. It is anticipated that training is to be conducted up to one time for each contracted year. The Contractor shall grant the Government the authority to reproduce, update, or change the data contained in the institutional training curriculum and materials. (CDRL A017, Training Materials)

3.10.4 Non-Functional Units, Cutaways, and Subassemblies. The Contractor shall offer non-functional units, cutaway models, and subassemblies as training aids.

3.10.4.1 Non-Functional Units. The Contractor shall provide non-functional units which are representative of a functional deliverable unit on the exterior, to include functional knobs/buttons, without internal electronic components.

3.10.4.2 Transparent Housing Units. The Contractor shall provide non-functional units which are representative of a functional deliverable unit for internal electronics and exterior functions but have a see-through housing.

3.10.4.3 Cutaway Models. The Contractor shall provide non-functional units which are representative of a functional deliverable unit for internal electronics and exterior functions. One unit shall be cut along the “x” axis of the unit. One unit shall be cut along the “y” axis of the unit. Units shall have a clear epoxy coating applied to the dissected area to allow the unit to remain intact.

3.10.4.4 Subassemblies. The Contractor shall provide sub-assemblies of production representative units.

4 Contract Item Data Deliverables

Exhibit "A" – Contract Data Requirements List (CDRL):

CDRL# CDRL Title DID#

A001 Report, Record of Meeting/Minutes DI-ADMN-81505

A002 Maintenance and Supportability Demonstration Report DI-NDTI-80809B NOT 1

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

A004 Quality Assurance Program Plan DI-QCIC-81794 NOT 1

A005 Acceptance Test Plan DI-QCIC-80553A

A006 Test Procedure DI-NDTI-80603A

A007 Acceptance Test Report DI-QCIC-81891 NOT 1

A008 Failure Summary and Analysis Report DI-SESS-80255A

A009 System Safety Hazard Analysis Report DI-SAFT-80101C

A010 Product Baseline Index DI-CMAN-81218

A011 Supplier’s Configuration Management Plan DI-SESS-80858C

A012 Configuration Status Accounting Information DI-SESS-81253C

A013 Engineering Change Proposal DI-SESS-80639D

A014 Request for Variance DI-SESS-80640D

A015 Commercial Off-The-Shelf Manuals and Associated

Supplemental Data

DI-TMSS-80527C NOT 1

A016 Engineering Data for Provisioning DI-SESS-81874

A017 Training Materials DI-ILSS-80872 NOT 1

5 Special Conditions. The Contractor shall comply with all International Traffic in Arms

Regulations (ITAR) controls and procedures for the handling, transfer, and storage of ITAR technology and information.

6. Security Requirements. The information provided to the contractor will be unclassified and/or Controlled Unclassified Information (CUI). The contractor is not required or expected to have a Facility Clearance and contractor personnel supporting this effort are not required to possess Personnel Clearance Levels. Any contractor personnel requiring access to U.S.

Government CUI shall possess a completed background investigation (minimum of a T-1/NACI) for this Public Trust Position.