001_Attachment_SOW_Rev_2017-01-19.pdf

Jan 2017

Use or disclosure of the data contained on this sheet is MIL-MNGMT-SOW.DOC 1 subject to the restrictions on the title page of this proposal

STATEMENT OF WORK (SOW) FOR

MAINTENANCE SUPPORT DEVICE-VERSION 4 RUGGED (MSD-V4R)

AND MSD-V4 SEMI-RUGGED (MSD-V4S)

TABLE OF CONTENTS

Section/Paragraph Page

1.0 BACKGROUND

2.0 SCOPE

3.0 GENERAL REQUIREMENTS

4.0 PROGRAM MANAGEMENT REQUIREMENTS

4.1 Start of Work Meetings

4.2 Conference Minutes

4.3 Changes to Scope

4.4 Control Procedures

4.4.1 Security

4.4.2 Antiterrorism/Force Protection for Defense Contractors outside the US ... 9

4.4.3 Contractor Clearance

5.0 CONFIGURATION MANAGEMENT (CM) REQUIREMENTS

5.1 Start of Work Meeting

5.2 Product Configuration Documentation

5.3 CM Policies and Procedures

5.4 Configuration Audit

5.5 Subcontractor/Vendor Control

5.6 Engineering Change Proposal

5.6.1 Authorization

5.6.2 Signature Authorization

5.6.3 Engineering Change Proposal Costs

6.0 LOGISTICS

6.1 Electronic Technical Manuals

6.1.1 Technical Documentation

6.1.2 Effectivity

6.1.3 Operator’s Manual Publication

6.1.4 Operator’s Manual Source Material

MIL-MNGMT-SOW.DOC 2 subject to the restrictions on the title page of this proposal

6.1.5 Illustrations and Diagrams

6.1.6 Meetings and Reviews

6.1.7 In-Process Reviews

6.1.7.1 Post-Review Teleconference

6.1.8 Preliminary Technical Manual Data Files Validation and Review

6.1.8.1 Contractor Validation Responsibilities

6.1.8.2 Government Witness of Validation

6.1.9 TM Records Keeping

6.1.10 Preliminary Technical Manual Data Files Review

6.1.11 Verification and Logistics Demonstration (LOGDEMO)

6.1.12 Text and Graphics

6.1.13 Resourcing

6.1.14 Contractor Assistance

6.1.15 Records Process

6.1.16 Administrative Support

6.1.17 Final Approval Review

6.1.18 Over Pack Requirements

6.2 Operator Training Digital Optical Disc and Institutional Training Package

6.2.1 Training Start of Work Meeting

6.2.2 Training Documentation

6.2.3 Training and Training Support

6.2.4 Instructional Media Design

6.2.5 Test Package

6.2.6 Course Content

6.2.7 Technical Literature

6.2.8 Practice Module

6.2.9 Instructional Strategy

6.2.10 Testing Strategy

6.2.11 Course Development Qualifications

6.2.12 IPRs

6.2.12.1 IPR #1

6.2.12.2 IPR #2

MIL-MNGMT-SOW.DOC 3 subject to the restrictions on the title page of this proposal

6.2.12.3 IPR #3

6.2.13 Additional Training Guidance Conferences/Training IPRs

6.2.14 Validation/Certification

6.2.15 Verification

6.2.16 Final Training Materials

6.2.17 Approval Requirements

6.2.18 Computer Managed Instruction (CMI) Requirements

6.2.19 Reproduction

6.2.20 Safety

6.2.21 Training Aids and Equipment

6.2.22 Material Fielding Team (MFT): New Equipment Training (NET) Team and Fielding Team

6.2.22.1 Requirement for a MFT

6.2.22.2 Functions of the MFT

6.2.22.3 MFT After Action Report (AAR)

6.2.22.4 MFT Cybersecurity

6.3 Original Equipment Manufacturer (OEM) User’s Manuals and Guides . 21

6.4 Integrated Product Support (IPS) Management

6.4.1 Integrated Logistics Program Manager

6.4.2 Subcontractor Requirements

6.4.3 In Process Review Conferences (IPRC)

6.4.4 Provisioning and Publications Guidance Conference

6.4.5 Logistic Support Analysis (LSA)/Provisioning Technical Documentation

(PTD) 22

6.4.6 Provisioning Parts List (PPL)

6.4.7 SESAME Initial Spares Support

6.4.8 Government and Federal Specifications

6.4.9 Reference Number Category Code (RNCC)

6.4.10 Reference Number Variation Code (RNVC)

6.4.11 Repair Kits

6.4.12 J & K Cards

6.4.13 Provisioning and Other Pre-Procurement Screening Data

6.4.14 Engineering Data for Provisioning (EDFP)

MIL-MNGMT-SOW.DOC 4 subject to the restrictions on the title page of this proposal

6.4.15 Maintenance Allocation Chart (MAC)

6.4.16 Functional Group Codes (FCG)

6.4.17 Provisioning Conference

6.5 Documentation and Drawings

6.6 Item Unique Identification Markings Requirements

6.6.1 IUID Registration

6.6.1.1 Hardware Changes in IUID

6.6.2 Identification Plates/Labels

6.6.2.1 Battery Information

6.7 Calibration

6.8 Warranty

6.8.1 Warranty Program

6.8.2 Turn Around Time on Warranted Items

6.8.3 Non-Warranty Repair Actions (NWRA)

6.8.4 Submission of Warranty and Non-Warranty Report

6.8.5 Warranty Performance Report

6.8.6 CONUS and OCONUS Toll-free Technical Assistance

6.9 Website and MSD Helpdesk Support

6.10 Manpower Reporting

6.11 Government Furnished Property Schedule

7.0 FIRST ARTICLE TEST (FAT) AND REFURBISHMENT OF FAT

ASSETS 32

7.1 First Article Test (Contractor Testing), 5152.209-4002

7.2 FAT Plan, Procedures and Report

7.3 Destructive Testing

7.4 Refurbishment and Replacement of FAT Assets

8.0 PRODUCTION REQUIREMENTS

8.1 Production Capacity

8.2 Shipment of Production Items

8.3 Bonded Storage

8.3.1 Bond Room Inventory

8.4 Acceptance

8.5 Serialization

MIL-MNGMT-SOW.DOC 5 subject to the restrictions on the title page of this proposal

8.6 Data Record Keeping

9.0 ENGINEERING REQUIREMENTS

9.1 Performance and Obsolescence

9.2 Expansion for Additional Capabilities

9.3 Technical Directions Orders

9.4 Software

9.5 Standalone Software and Documents

9.6 System Software

9.7 Linux Software and Configuration

9.8 Emergency Recovery Disc (ERD) Replication

9.9 Hard Drive OS Software Load

9.10 Foreign Military Sales (FMS) OS Software and ERD

9.11 Cybersecurity/ Program Protection

9.11.1 Cybersecurity Strategy

9.11.1.1 Develop a Cybersecurity Strategy

9.11.1.2 Cybersecurity Accreditation Artifacts Package

9.11.1.3 Cybersecurity Policies

9.11.2 Cybersecurity Risk Assessments

9.11.2.1 Security Risk Matrix

9.11.2.2 Risk Reduction Milestones

9.11.3 Cybersecurity Accreditation Artifact Package

9.11.4 Cybersecurity and Software Scans

9.11.4.1 Software Source Code Repositories

9.11.4.2 Software Assurance Scans

9.11.4.3 Cybersecurity Vulnerability Scans

9.11.4.4 Initial Baseline Cybersecurity Vulnerability Scan

9.11.5 Cyber Security Testing

9.11.6 Cyber Security Vulnerability Management

9.11.7 Program Protection

9.11.7.1 Analyses and Assessments

9.11.7.2 Mission Criticality

9.11.7.3 Logic-Bearing System Components

9.11.7.4 Risk Mitigation of Foreign Intelligence

MIL-MNGMT-SOW.DOC 6 subject to the restrictions on the title page of this proposal

9.11.7.5 Secure Coding Standards and Secure Design Features

9.11.7.6 MSD-V4R and MSD-V4S Program Protection Implementation Plan

(PPIP) 46

9.12 Quality System Requirements

9.12.1 Workmanship

9.12.2 Defects

9.12.3 Rework and Repair of Non-Conforming Material

9.12.4 Failure Reporting and Corrective Action System (FRACAS)

9.12.4.1 Failure Summary and Analysis Report

9.13 Safety Assessment Report

9.14 Hazardous Material Management Program (HMMP) Plan and Report .. 49

9.14.1 Hazardous Materials

9.15 Corrosion Prevention Planning

9.16 System Security Engineering for Trusted Systems and Networks

9.16.1 Mission Criticality

9.16.2 Definitions of Criticality

9.16.3 Associated Logic-bearing System Components

9.16.4 Monitor the Supply Chain

9.16.5 Countermeasures

9.16.6 Provisions

9.16.7 Systems Engineering Technical Review (SETR)

9.16.8 Foreign Intelligence and Technology-Exploitation

9.16.9 Coding Standards

9.16.10 Table

9.16.11 Critical Function Supply Chain and Development Basic Protections ... 54

9.16.12 Protect Unclassified DoD Data

10.0 Small Business Subcontracting Opportunities

MIL-MNGMT-SOW.DOC 7 subject to the restrictions on the title page of this proposal

1.0 BACKGROUND

The Maintenance Support Device-Version 4 Rugged (MSD-V4R) program and the Maintenance Support Device-Version 4 Semi-Rugged (MSD-V4S) program has been initiated to produce and field an improved system of at-platform test equipment. The MSD-V4R and MSD-V4S Systems, members of the Integrated Family of Test Equipment (IFTE), are the Army’s next generation of standard general purpose at-platform automatic test equipment. The MSD-V4R and MSD-V4S Systems consist of Commercial-Off-The-Shelf (COTS) software and hardware components operating together with system specific software, standard accessories, interconnecting cables, and test adapter modules. These systems shall be used throughout the U. S. Army at all levels of maintenance as the Army’s standard at-platform tester for a wide variety of complex systems.

Additionally, the MSD-V4R and MSD-V4S shall be used to host Interactive Electronic Technical Manuals (IETMs) and Electronic Technical Manuals (ETMs), specific application software, and to upload/download mission data or software. The MSD-V4R and MSD-V4S Systems are intended to support all Army maintainers including ground, armor, aviation, missile, wheeled vehicle, signal/radio, command and control, and other tactical system maintainers. The MSD-V4R and MSD-V4S Systems shall be configured to support various Army weapon systems and platforms with optional and standard accessories. Companion accessories to the MSD-V4R Kit and MSD-V4S Kit include the Smart Wireless Internal Combustion Engine (SWICE) Test Adapter Set and Wireless At-platform Test Set (WATS), although SWICE and WATS are not produced under the MSD-V4R and MSD-V4S contract.

2.0 SCOPE

This Statement of Work (SOW) defines the effort required for the production, test, delivery, storage, and support of the MSD-V4R and MSD-V4S Systems. The contractor shall provide all labor, resources, expertise, facilities, and material necessary to satisfy the requirements of MSD- V4R and MSD-V4S SOW, System Specification in order to produce, test, and deliver MSD-V4R and MSD-V4S Systems and optional accessories. The work required by this contract shall be performed In Accordance With (IAW) System Specification (MIS-DTL-58668). In the event of a conflict between this SOW and MIS-DTL-58668, the MIS-DTL-58668 shall take precedence.

3.0 GENERAL REQUIREMENTS

General requirements of this contract include contractor support in the following areas: Program Management (PM), Configuration Management (CM), Logistics, First Article Testing (FAT), Production, and Engineering.

4.0 PROGRAM MANAGEMENT REQUIREMENTS

The contractor shall establish and maintain program management operations that shall include the following areas: program planning and control, subcontractor control, financial management, data management, risk management, and accountability for Government Furnished Equipment (GFE), material or information.

The contractor shall use a program management system to develop and perform to an Integrated Master Plan (IMP) and Integrated Master Schedule (IMS), IAW DI-MGMT-81650, throughout the life of the program. The contractor Program Manager and supporting teams shall support the delivery of accurate and timely schedule and performance information, including IMP and IMS, MIL-MNGMT-SOW.DOC 8 subject to the restrictions on the title page of this proposal to Product Director Test, Measurement and Diagnostic Equipment (PD TMDE) throughout the period of the contract to include units under warranty after the last contractual delivery.

The contractor shall be responsible for leading bi-monthly In-Process Reviews (IPR) to facilitate a common understanding and agreement with the Government on MSD-V4R and MSD-V4S system requirements, actions, and schedules to meet those requirements. Meetings shall be held at the respective places of performance for the manufacture of MSD-V4R and MSD-V4S, contractor's facilities and at PD TMDE facilities, as needed. The contractor shall provide support to conduct these meetings. Government may choose to hold these meetings by telephone conferences or web-enabled conferences. Meetings at PD TMDE facilities can be accommodated through coordination and agreement between Government and contractor.

Technical meetings shall be held as needed for discussion, determinations, and clarifications of technical items and issues. Technical meetings shall be performed through telephone and/or web conferences, person-to-person or group meetings, and/or via electronic mail to help resolve technical items and for clarifications. Technical meetings shall not change the terms of the contract or cause any impacts to the contract. All recommended changes shall be coordinated by notification to the Contracting Officer and shall not be implemented without authorization from the Contracting Officer.

4.1 Start of Work Meetings

Start of Work meetings shall be held for the following general requirements: PM, CM, TM Development, Logistics, Training, FAT, Software/ Cybersecurity, Engineering and Production.

The IMP and IMS shall incorporate start of work meetings and specify criteria and dates, respectively. IMS shall also include In-process Reviews.

4.2 Conference Minutes

The contractor shall be responsible for recording, maintaining, and providing detailed written minutes, including any tasks of the Start of Work Meetings, all IPRs, and conferences IAW DI- ADMN-81250A. The Government will notify the contractor when minutes are required. The minutes shall not to be interpreted or construed as redirection for the contractor to incur additional costs that will increase the price of the contract.

4.3 Changes to Scope

Changes outside the scope of the contract, including this SOW, without specific authorization by the Procuring Contracting Officer (PCO), are unauthorized and shall be at the sole responsibility of the contractor.

4.4 Control Procedures

4.4.1 Security

The contractor shall ensure security IAW the current DD Form 254 and the DoD 5220.22, National Industrial Security Program Operating Manual.

MIL-MNGMT-SOW.DOC 9 subject to the restrictions on the title page of this proposal

4.4.2 Antiterrorism/Force Protection for Defense Contractors outside the US DFARS Clause 252.225-7043 shall be used in solicitations and contracts that require performance or delivery in a foreign country. This clause applies to both contingencies and non-contingency support. The key antiterrorism requirement is for non-local national contractor personnel to comply with theater clearance requirements and allows the combatant commander to exercise oversight to ensure the contractor’s compliance with combatant commander and subordinate task force commander policies and directives.

4.4.3 Contractor Clearance

The contractor shall forward the necessary security clearances and visit requests to the appropriate installations for all contractor personnel who will require access in the performance of this contract. Contractor shall have Common Access Cards (CAC) for access to the Training Development Capability (TDC) database.

Before CAC issuance, the contractor employee requires, at a minimum, a favorably adjudicated National Agency Check with Inquiries (NACI) or an equivalent or higher investigation in accordance with Army Directive 2014-05. The contractor employee will be issued a CAC only if duties involve one of the following: (1) Both physical access to a DoD facility and access, via logon, to DoD networks on-site or remotely; (2) Remote access, via logon, to a DoD network using DoD-approved remote access procedures; or (3) Physical access to multiple DoD facilities or multiple non-DoD federally controlled facilities on behalf of the DoD on a recurring basis for a period of 6 months or more. At the discretion of the sponsoring activity, an initial CAC may be issued based on a favorable review of the FBI fingerprint check and a successfully scheduled NACI at the Office of Personnel Management.

All contractor employees and associated sub-contractor employees with access to a Government information system must be registered in the Army Training Certification Tracking System at commencement of services, and must successfully complete the DoD Information Assurance Awareness prior to access to the information system and then annually thereafter.

All contractor employees and associated sub-contractor employees must complete the DoD Cybersecurity awareness training before issuance of network access and annually thereafter. All contractor employees working Cybersecurity/IT functions must comply with DoD and Army training requirements in DoDD 8570.01, DoD 8570.01-M and AR 25-2 within six months of appointment to Cybersecurity/IT functions.

5.0 CONFIGURATION MANAGEMENT (CM) REQUIREMENTS

CM requirements apply throughout the period of the contract to include units under warranty after the last contractual delivery. The purpose of CM is to assure that the Product Configuration Identification (PCI) accurately describes the as-designed/as-built delivered item(s).

5.1 Start of Work Meeting

The CM Start of Work Meeting shall be held at Redstone Arsenal, AL no later than 30 days after contract award.

MIL-MNGMT-SOW.DOC 10 subject to the restrictions on the title page of this proposal

5.2 Product Configuration Documentation

The applicable, released Product Configuration Item (PCI) document for the listed Configuration Item (CI) is as follows:

CI PCI

MSD-V4R System Specification MIS-DTL-58668, dated

TBD, and as amended after contract award.

5.3 CM Policies and Procedures

The contractor shall implement a configuration management program and use MIL-HDBK-61A (approved for interim use) for guidance. The contractor’s changes to its product drawings shall continuously agree with the current configuration identification and Government MSD-V4R and MSD-V4S drawings (to the extent agreed upon), and the changes shall not adversely affect any of the requirements defined in the system specification. The contractor shall advise the Government by letter of transmittal of configuration changes. The Government reserves the right to approve/disapprove the contractor’s CM policies and procedures.

5.4 Configuration Audit

The Government reserves the right to conduct Configuration Audits and Inspections. These audits may be performed on site at contractor facilities, at Government facilities, or at Operational Government sites.

5.5 Subcontractor/Vendor Control

The contractor shall be responsible for determining the extent to which the CM requirements are applicable to subcontractors, vendors and suppliers, and for the application of those requirements, which are necessary to ensure compliance with the CM requirements of this contract.

5.6 Engineering Change Proposal

The contractor shall provide an Engineering Change Proposal (ECP) to the Government for approval whenever the contractor’s Configuration Item (CI) changes IAW DI-SESS-80639D.

The numbering system used shall uniquely identify each ECP. The contractor shall submit the ECPs through the United States (U.S.) Army Aviation and Missile Command (AMCOM) Life Cycle Management Command (LCMC) Multi-User Engineering Change Proposal Automated Review System (MEARS). MEARS login and instructions will be provided by the Government after contract award. MEARS training will be provided by Government, as needed, for the contractor. This topic shall be discussed at CM Start of Work Meeting. Contractor shall designate appropriate Configuration Management personnel to attend MEARS training, as needed. Training is expected to last one week at Redstone Arsenal, AL, in Government facility/building. Included with the ECP, the contractor shall provide (if applicable) a Notice of Revision IAW DI-SESS-80642D and (if applicable) a Specification Change Notice IAW DI- SESS-80643D. If applicable, a Request for Deviation IAW DI-SESS-80640D shall be submitted.

Upon ECP approval, the contractor shall be responsible for updating any changes to technical documents (i.e. IETMs, Operator Manuals, Parts Lists, training materiel, etc.) impacted by the ECP. The contractor shall establish and maintain a Configuration Control Board. Representatives of the United States Government will not be a part of the Contractor’s Configuration Control

MIL-MNGMT-SOW.DOC 11 subject to the restrictions on the title page of this proposal

Board. Change(s) to hardware and software, especially Class I ECPs, shall be coordinated with the Government, since change(s) may impact Cybersecurity posture and interfaces with Army systems. A description of change(s) and related affectivity shall be coordinated with Government.

5.6.1 Authorization

The contractor shall request ECP authorization prior to its implementation through the PCO.

5.6.2 Signature Authorization

The contractor shall identify to the Government, the name(s) of the official(s) of its organization authorized to sign ECPs as the submitting activity, and thereby commit the contractor to the statements made therein. This identification shall be in writing, on company stationery, signed by an officer of the company, and provided to the Government at the CM Start of Work Meeting.

The contractor shall inform the Government, in writing, when name(s) of these authorizing official(s) change.

5.6.3 Engineering Change Proposal Costs

When an ECP affects cost (increase or decrease), the contractor shall provide sufficient supporting cost data to the PCO as part of the proposed change or departure for the Government to evaluate and verify the total cost impact. For any changes (including those due to obsolescence) not directed by the PCO, the contractor shall not increase the price on any items/services in the contract nor charge the Government for the cost of the ECP or any technical document changes (i.e. IETMs, Operator Manuals, Parts Lists, training materiel, etc.) impacted by the ECP. No ECP shall be implemented until the Government has approved the ECP and the contractor has been notified by the PCO to implement the change. Notification of disapproved ECPs will be in writing from the PCO. Approved ECPs will be incorporated into the contract by modification.

6.0 LOGISTICS

6.1 Electronic Technical Manuals

The contractor shall develop and provide Operator’s manual per requirements noted in this SOW. The Government will generate the Final Reproducible Copy (FRC) built from the Operator’s Manual into a Portable Document Format (PDF) file. The contractor shall provide storage space in the MSD-V4R and MSD-V4S transit cases for over-pack of one each paper TM (Size: 8.5” x 11” x 1”).

6.1.1 Technical Documentation

The contractor shall create and deliver Extensible Markup Language (XML)/Standard Generalized Markup Language (SGML) tagged text and data files and illustrations required for an Operator's Manual IAW the requirements of MIL-STD-40051-2C and MIL-STD-2361. The contractor may use MIL-HDBK-1222F as reference and information. If commercial manuals are utilized, contractor shall obtain copyright release to use and produce the commercial manuals.

The XML/SGML-tagged text and data files and illustrations for an Operator’s Manual shall be convertible to Adobe Acrobat which enables the Government to change them into PDF files.

MIL-MNGMT-SOW.DOC 12 subject to the restrictions on the title page of this proposal

These deliverable items are subjected to Government’s review and approval. The Government will provide a complete TM number for this manual no later than (NLT) at the 30% IPR.

6.1.2 Effectivity

Documentation shall reflect all active configurations of the hardware, Preventive Maintenance, Checks and Services (PMCS) as established for the target audience and the Government-provided Maintenance Allocation Chart (MAC). Contractor shall provide all PMCS, cleaning and configuration data for MSD-V4R and MSD-V4S Systems to the Government by means of contractor developed and provided data such as COTS operator manual, engineering drawings, software and hardware manuals, technical discussions, and documentation.

6.1.3 Operator’s Manual Publication

The contractor shall develop or extract any needed technical data from existing COTS publications, engineering drawings, notes, previously developed Government TMs, and any other additional data source necessary to develop the Operator Manual. MSD-V4R and MSD- V4S System COTS manual shall be provided IAW DI-IPSC-81446A, Computer Operation Manual (COM). Any information that does not exist in these data sources shall be developed to support PMCS, MAC, and warranty. Developed or extracted technical data shall be repackaged and republished in the form of XML-tagged text files, and illustrations, consistent with the requirements of the MAC and the content/format requirements of MIL-STD-40051-1C (IETM’s).

6.1.4 Operator’s Manual Source Material

The contractor shall package and deliver all source material, defined as operating plans, standard procedures, computer programs, and residual material to include computer disks, and all other media containing digital files developed to fulfill the requirements of this SOW. The contractor shall grant the Government unlimited rights to any and all data/products produced under this SOW including unlimited intellectual property rights and technical data rights.

6.1.5 Illustrations and Diagrams

Illustrations and diagrams used with the XML-tagged text and data files shall reflect the equipment delivered to the Government. All illustrations shall be developed IAW the requirements of this SOW and MIL-STD-40051-1C regarding size, display density, and legibility. Illustrations shall be in Computer Graphics Metafile (CGM) standard IAW ISO/IEC 8632:1999 Parts 1, 3, and 4. The dimension of the Operator's Manual is 11 inches by 8.5 inches, with a thickness of no more than 1 inch (portrait orientation).

6.1.6 Meetings and Reviews

A TM Start of Work Meeting and several IPRs including the 30%, 70%, and 100% IPRs, shall be held throughout the development of the Operator's Manual.

6.1.7 In-Process Reviews

The contractor shall participate in a TM IPR for each delivery of the tagged files cited in Contract Data Requirement List (CDRL) provided in Section J of solicitation/contract award.

The Government may perform these reviews in various ways, i.e., desktop, conference calls, and meetings. Each IPR submission will be reviewed for content and format compliance to the MIL-

MIL-MNGMT-SOW.DOC 13 subject to the restrictions on the title page of this proposal

STD-40051-2C and MIL-STD-2361. The Government will review and correct the tagging of the files and return the data files with tagging corrections incorporated. The contractor shall use the corrected files to develop the final version of the tagged files. The contractor shall then incorporate all content comments into the tagged files. The contractor shall retain copies of all comments.

6.1.7.1 Post-Review Teleconference

If the contractor requires any clarification on comments provided by the Government on the 30%, 70%, or 100% IPRs, the contractor shall request a teleconference with the Government.

Once a teleconference date and time has been established, the contractor shall provide the conference telephone number and dial-in code, if applicable, to the Government before the teleconference is to take place.

6.1.8 Preliminary Technical Manual Data Files Validation and Review The contractor shall validate the Preliminary Technical Manual (PTM) at the 30%, 70%, and 100% intervals as follows:

6.1.8.1 Contractor Validation Responsibilities

The contractor shall validate the technical accuracy and adequacy of all operating procedures in the Operator's Manual, including XML-tagged files and related illustrations. The contractor shall prepare a TM Validation Plan IAW DI-TMSS-81818.

6.1.8.2 Government Witness of Validation

The Government reserves the right to witness all or a portion of the validation. Contractor shall notify the Government at least two weeks prior to validation with date and location; however, the Government’s observation of the validation will not constitute a verification of the material. If the Government does attend the validation and provides comments, the contractor shall incorporate these comments into the Manual before the Preliminary Technical Manual is submitted.

6.1.9 TM Records Keeping

The contractor shall maintain records showing dates of TM reviews, material reviewed by task or action, findings with applicable remarks, and action taken IAW ISO 9001 series or equivalent.

The Government reserves the right to examine these records at the contractor's facility.

6.1.10 Preliminary Technical Manual Data Files Review

Once the contractor has validated the completed Operator's Manual, it is considered a Preliminary Technical Manual (PTM). The PTM consists of the validated content, XML-tagged files, and related illustrations. The Government will review the contractor completed, validated PTM data files to ensure technical accuracy, incorporation of previously reviewed comments, acceptable format, and conformity to the Army maintenance policy, regulations and MSD support requirements.

6.1.11 Verification and Logistics Demonstration (LOGDEMO)

The Government will verify the tagged data files at a Government designated facility.

Verification will be performed on a PTM generated by the Government from the validated XML-

MIL-MNGMT-SOW.DOC 14 subject to the restrictions on the title page of this proposal tagged files. Government’s comments on the validated PTM will be provided to the contractor at or before verification. The Government will verify operating instructions using military personnel with the appropriate Military Occupational Specialty (MOS) performing tasks as detailed in the Operator's PTM. All PMCS tasks will also be verified as described above.

Verification will be IAW all requirements cited in this SOW. All portions of the Operator's Manual not subject to hands-on verification will be desktop-review verified. The Government reserves the right to use additional verification methods as appropriate.

6.1.12 Text and Graphics

The contractor shall correct all errors found in the PTM text and graphics during verification.

After Government review of the PTM, the contractor shall correct any additional errors found in the PTM.

6.1.13 Resourcing

The contractor shall provide at a minimum a technical writer, an engineer, and any tools needed to perform operation of the MSD-V4R and MSD-V4S for the verification and the LOGDEMO.

The Government will determine the times and the locations for the verification and LOGDEMO.

6.1.14 Contractor Assistance

The contractor shall provide assistance to the Government at the verification and LOGDEMO.

The contractor shall provide the Government with a copy of all proposed faults that have been validated and are listed in the PTM prior to verification and LOGDEMO. The contractor may use MIL-HDBK-470 as a reference to determine fault insertion sample size and methodology. The contractor shall provide the necessary means to allow for the insertion of all the listed faults for verification and LOGDEMO purposes. The contractor shall have the necessary resources on-site to provide on-the-spot corrections to the XML\SGML tagged text, data files, and illustrations required for an Operator's Manual, at no additional cost to the Government.

6.1.15 Records Process

During Government verification and LOGDEMO, the contractor shall record and maintain a list of deficiencies and their corresponding corrective actions (if known). The contractor shall provide the Government with a copy of the list at the conclusion of the verification and LOGDEMO process. A detailed report that contains all deficiencies, the corresponding corrective actions implemented during and after Government verification and LOGDEMO, the rationale for not correcting a deficiency (if applicable), page number the deficiency was on, and the page number the correction is on IAW DI-TMSS-81820.

6.1.16 Administrative Support

The contractor shall provide administrative support for completion of the verification and the

LOGDEMO.

6.1.17 Final Approval Review

The Government will perform a final approval review of the FRC XML-tagged data files and illustrations after verification and LOGDEMO to ensure all requirements of this SOW are met.

The FRC shall be the final XML\SGML tagged text, data files, and illustrations, with all necessary changes and corrections incorporated including final resolution of all comments and

MIL-MNGMT-SOW.DOC 15 subject to the restrictions on the title page of this proposal recommendations made as a result of validation, verification, LOGDEMO, testing, and user review. If errors are found in the FRC, the XML-tagged files and illustrations will be considered a PTM until the errors are corrected. After Government acceptance of the product, the Government reserves the right to require the contractor to correct all errors found in the manuscript at no additional cost to the Government with 30 days.

6.1.18 Over Pack Requirements

The Government will provide the Operator's Manuals for over-pack at the fielding location. The Government will provide one each Operator's Manual (paper copy) per Unit Identification Code (UIC) fielded.

6.2 Operator Training Digital Optical Disc and Institutional Training Package The contractor shall develop training using the Army Learning Policy and Systems IAW

TRADOC REG 350-70.

6.2.1 Training Start of Work Meeting

Start of Work Meeting will be held at PD TMDE, Redstone Arsenal, AL. The purpose of the meeting is to discuss the Government furnished information (GFI), determine the milestones, delivery schedules, review cycles, liaison procedures, and establish a working relationship among key personnel. All contractor personnel directly involved with the development, design, production, and instruction shall attend this meeting.

6.2.2 Training Documentation

The contractor shall develop the operator training package using Hypertext Markup Language (HTML) on current version of any COTS or industry-standard training development software.

The contractor, after coordination and approval by the Government, may update the software as necessary during the course of the training package development. Training material shall be prepared IAW Army Regulation 350-1, U.S. Army Training and Doctrine Command (TRADOC) Regulation 350-70 and the Analysis, Design, Development, Implementation, and Evaluation (ADDIE) process. The contractor shall develop all course documentation using the ADDIE process as a guide for New Equipment Training (NET) Computer Based Training (CBT) and Institutional Training in the Training Development Capability (TDC) database. Upon request by the contractor, NLT 30 days after Training Start of Work Meeting, if required, the Government will coordinate for TDC training. The contractor may attend either the three (3) day DCO on-line class or the eight (8) day training course, which will be at a Government facility located at Fort Lee, VA. The option shall be subjected to availability of classes and seats in each location.

Training shall be limited to two contractor’s representatives. These two representatives shall be United States citizens and possess CAC. Once TDC training is complete, the Government will provide the contractor with the TDC Domain site, roles, and responsibilities for Institutional Training Packets.

6.2.3 Training and Training Support

The contractor shall develop the Operator’s course. This course shall be delivered on-line, preloaded on the MSD-V4R and MSD-V4S and input into the TDC database. The operator’s course shall teach the skills and information necessary to perform the following tasks: set-up, activate, check out, and operate and do routine operator maintenance on the MSD-V4R and

MIL-MNGMT-SOW.DOC 16 subject to the restrictions on the title page of this proposal

MSD-V4S IAW the Operator’s manual and in support of the MAC. Training shall include the operating tasks for all equipment, components, special test equipment, and ancillary equipment provided by the contractor under this contract and required to operate the MSD-V4R and MSD- V4S. Existing commercial training packages will be considered acceptable for use provided they meet the criteria set forth in this SOW, are developed using the TDC, and are approved by the Government.

6.2.4 Instructional Media Design

The contractor shall prepare an instructional media design IAW MIL-PRF-29612B and DI- SESS-81520B. The contractor shall utilize Interactive Multimedia Instructions (IMI) to its full capabilities while developing the Interactive Courseware. The contractor shall use TRADOC Pamphlet 350-70-12, and MIL-HDBK-29612-3A as reference for IMI.

6.2.5 Test Package

The contractor shall prepare test package strategies IAW DI-SESS-81525C.

6.2.6 Course Content

The contractor shall design the course content using the ADDIE process. The training presentation shall follow a logical structure and shall include frequent checks on learning.

Training shall emphasize the hazards associated with the operation of the MSD-V4R and shall include precautionary measures to reduce these hazards.

6.2.7 Technical Literature

The contractor shall ensure that the fielded equipment is preloaded with Government verified and approved Operator’s Manual and Operator’s Training. The contractor shall produce Operator’s Training CBT and preload it on each MSD-V4R and MSD-V4S.

6.2.8 Practice Module

The contractor shall devote no less than 40% and no more than 70% of the course to practice modules that consist of simulation with interaction from the student performing or practicing the tasks presented in the lessons IAW DI-SESS-81520B.

6.2.9 Instructional Strategy

The contractor’s developed multimedia training shall employ several instructional strategies in each lesson and ensure efficient and relevant learning. The contractor shall normally provide new information through tutorial and inquiry methods. The Government expects extensive use of practice, interaction, drill and practice that increase comprehension IAW DI-SESS-81520B and

DI-SESS-81526C.

6.2.10 Testing Strategy

The contractor shall ensure each lesson contains review questions that drill application of skills presented in the lesson. Practice exercises shall not be limited to application of enabling skills or subtasks, but shall provide practice on complete or whole tasks prior to test-taking time. The final practice exercise that precedes the test shall parallel the test in its construction and shall be a realistic simulation of on-the-job performance. The test shall allow the student to review all

MIL-MNGMT-SOW.DOC 17 subject to the restrictions on the title page of this proposal questions and answers once complete. The final practice exercise shall measure the steps that make up the task IAW DI-SESS-81525C.

6.2.11 Course Development Qualifications

The contractor shall demonstrate the ability to perform all operational tasks in the practice module portion of the training course. Each course developer shall demonstrate qualification as a technical training instructor by possessing either Technical Training (college or vocational school beyond high school), or Armed Services training in the subject area for which training is to be developed and Professional Training (College, Armed Services, or Government-approved course in Methods of Instruction).

6.2.12 IPRs

The Government will conduct Training IPRs. The Government will perform these reviews in various ways via electronic media sent to the Government’s designated representative by means of digital optical disc, electronic mail, posted on a secure website furnished by the contractor, or at the contractor’s facility. The Government will prescribe the method at the Training Start of Work Meeting.

6.2.12.1 IPR #1

The contractor shall participate in IPR #1 conducted NLT 120 days after the Start of Work Meeting. IPR #1 shall be for review of 50% of the training material specified in DI-SESS- 81520B, 20% of the training material specified in DI-SESS-81521B, 20% of the training material specified in DI-PSSS-81523C, and 20% of the training material specified in DI-SESS- 81526C and place holders with titles for DI-SESS-81525C for discussion during IPR#1.

6.2.12.2 IPR #2

The contractor shall participate in IPR #2 conducted NLT 45 days after IPR #1. IPR #2 shall be for review of 75 % of the training material specified in DI-SESS-81520B, 50% of the training material specified in DI-SESS-81521B and DI-PSSS-81523C, and 50% of the training material specified in DI-SESS-81525C and DI-SESS-81526C for discussion during IPR#2.

6.2.12.3 IPR #3

The contractor shall participate in IPR #3 conducted NLT 90 days after IPR #2. IPR #3 shall be for review of 100% of the training material specified in DI-SESS-81520B and DI-PSSS-81523C, 100% of the training material specified in DI-SESS-81521B and DI-SESS-81525C, and 100% of the training material specified in DI-SESS-81526C for discussion during IPR#3.

6.2.13 Additional Training Guidance Conferences/Training IPRs Additional training guidance conferences/IPRs may be required and shall be coordinated between the contractor and the Government.

6.2.14 Validation/Certification

The contractor shall perform an in-house validation on the entire Training Package before IPR #3. This validation shall ensure that the training materials meet the requirements and standards of the Government. As part of the validation, the contractor shall also ensure that all software on

MIL-MNGMT-SOW.DOC 18 subject to the restrictions on the title page of this proposal the master disk executes properly, and then provide the Government a written certification prior to the submission of the final Operator Training CBT IAW DI-TMSS-81819A.

6.2.15 Verification

The Government and the contractor shall conduct a joint verification of the CBT, Program of Instruction (POI), Lesson Plans, Slides and Student Guides using a small group from the intended target audience NLT 10 days after the Government’s approval of the 100% IPR #3 materials. The Government may choose to hold the Operator’s Training digital optical disc verification in conjunction with the IETM verification. Comments from this verification shall be evaluated and incorporated into the final version of the overall training support package (noted in Final Training Materials).

6.2.16 Final Training Materials

Upon the completion of 100% review by the Government based upon IPR#3, the contractor shall modify and make any corrections to the deliverables and deliver the final validated training products NLT 45 days after Government approval of the 100% IPR#3 material IAW DI-SESS- 81521B, DI-PSSS-81523C, and DI-SESS-81525C.

6.2.17 Approval Requirements

The Government’s approval of the developed Operator Training course shall be contingent upon the contractor’s successful completion of all applicable training data item requirements for the course and compliance with all of the requirements set forth in this SOW.

6.2.18 Computer Managed Instruction (CMI) Requirements

The contractor-developed training course shall contain CMI capabilities to track and report student progress IAW DI-SESS-81520B. The contractor shall generate the multimedia in such a manner that the students may go back and forth in the Operator Training CBT between lessons and main menus to allow for usage of the multimedia as a fingertip reference document on the end item. The multimedia shall not be constructed in such a manner that the student must proceed sequentially through the entire program from start to finish. Video segments shall have controls to allow the student to pause, back up, restart and forward to various frames. Content, operation and course flow of CBT shall be reviewed by Government and contractor shall incorporate Government comments and recommended changes into CBT/Multimedia.

6.2.19 Reproduction

The contractor shall provide the Government unlimited rights to Training Support Package (TSP), CBT, and multimedia and the right to reproduce the TSP and multimedia.

6.2.20 Safety

The contractor shall ensure the operator training course emphasizes the hazards associated with the operation of the MSD-V4R and MSD-V4S and shall include precautionary measures to reduce these hazards.

6.2.21 Training Aids and Equipment

During contract performance the contractor shall pass title to the Government of all created or purchased material at the time it was created or purchased. The contractor shall provide the

MIL-MNGMT-SOW.DOC 19 subject to the restrictions on the title page of this proposal

Government unlimited rights for all material developed and/or incorporated and employed as part of this effort. The contractor shall provide the development and production equipment as needed by the Government to perform the work required under this contract. The contractor shall submit a request to the Government at least 45 calendar days prior to the need of Government subject areas, facilities, or troops necessary for videotaping or validations. The contractor shall give maximum utilization of training equipment and training aids that are readily available through the Government as the first option or the commercial channel as the second option. Full consideration shall be given to the performance required under this contract so that end results provide ease of reproduction and editing by the Government.

6.2.22 Material Fielding Team (MFT): New Equipment Training (NET) Team and

Fielding Team The contractor shall provide a MFT/NET to conduct fielding and training in support of all aspects associated with the fielding of MSD-V4R and MSD-V4S and its associated products (Smart Wireless Internal Combustion Engine – Spiral 3 (SWICE-SP3) Test Adapter Kits, Diagnostics Software and other APATS products). The contractor shall also be responsible for equipment training package development, delivery and updates, as needed, (including POI, lesson plans, slide presentations, student handouts, and course exams), training system users, and sustainment of APATS training package and material.

Contractor shall incorporate changes to training package and materials based upon user feedback, changes to MSD-V4R and MSD-V4S, and updates to operation and usage of APATS products with approval by Government at no additional cost. The MFT shall also update and maintain the NET lesson plans and submit a trouble report for any MSD/ICE problems or bugs observed during NET events.

Each member of the contractor MFT shall possess necessary certification requirements as part of their contract obligation (mastery of course content and proficiency in the delivery/presentation of lessons). If any additional training courses are required, contractors must pay for them at no additional cost to the Government. Otherwise, contract instructors must meet the same requirements all certified instructors meet. Refer to TRADOC Regulation 350-70, Chapter 7 for contractor training requirements.

Each member of the MFT shall have the necessary credentials to access military installations where MSDs are fielded, including Outside Continental United States (OCONUS) areas which require theater clearance and additional training under host nation Status of Forces Agreements (SOFAs).

6.2.22.1 Requirement for a MFT

The makeup of the MFT is determined by the complexity or quantity of the systems being fielded, by an assessment of the facilities to be used for the de-processing and handoff and by the amount of assistance to be provided by the Gaining Command (GC). The MFT shall be involved, along with the Government MSD Fielding Manager in the development of the Materiel Requirements List (MRL) coordination.

6.2.22.2 Functions of the MFT

The Government MSD Fielding Manager will coordinate and negotiate with all participants, including the GC, Supporting Command (SC), and contractors (MFT) to ensure skilled

MIL-MNGMT-SOW.DOC 20 subject to the restrictions on the title page of this proposal personnel, facilities, and materials needed for consolidation, shipment, de-processing, inventory, handoff, and NET are provided as planned for in the MFP and MFA. The MFT’s functions shall include as a minimum the following, to include as required assignments:

• Travel to remote military locations (Continental United States (CONUS)/OCONUS) to perform Fielding of MSD and conduct NET to Active, National Guard, Reserve Soldiers and Civilians personnel. These locations could include, but are not limited to: South Korea, Germany, and Hawaii. Time frames could be from two to four weeks at a time and up to two times per year.

• Participate or conduct an in-brief and out-brief to the GC as required. In-brief shall consist of responsibilities, planned actions and expectations related to MFA. Out-brief shall consist of report of accomplishments, responsibilities, hand-off and transfer of equipment to Army units.

• De-processing, installing software, and assembling as needed to put all equipment into an operational condition. Software installation includes loading of Operating System (if and as needed), Diagnostics Software, Electronic Maintenance System Next Generation (EMS NG), Autonomous Diagnostics Manager (ADM), and various Interactive Electronic Technical Manuals (IETMs) and Electronic Technical Manuals (ETMs). This will require one person lift of MSD-V4R kit and MSD-V4S kit and stacking of MSD-V4R and MSD-V4S kits as necessary.

• Once all equipment has been accounted for, the MFT shall contact the Government MSD Fielding Manager to inform him of the status of the equipment at the fielding location.

• Analyze the training needs and able to tailor all aspects of training to facilitate user requirements.

• Complete operational checks prior to handoff or NET. MFT shall ensure that all equipment is operational prior to hand-off and equipment transfer.

• Conduct joint inventories with the GC’s Property Book Officers (PBO), or designated individuals (see GC’s DA Form 1687) using a DA Form 2062 and generate a Property Book Unit Supply Enhanced (PBUSE) DA Form 3161 Lateral Transfer document.

• Provide a complete copy of customer fielding documentation package (to include Commanders Assumption of Command Orders, DA Form 1687 Delegation of Authority Card, DA 3161 Request for Issue or Turn in). A copy of these documents will be turned over to the gaining unit Property Book Officer or designated representative at the conclusion of every MSD-V4R and MSD-V4S fielding effort.

• Deliver all DA 3161s to the MSD fielding manager on the same day of issue; unless there are unforeseen complications. The equipment will be lateral transferred to the GC once the DA 3161s are received.

• Process discrepancy reports, support requests, warranty forms, quality deficiency reports, and equipment improvement recommendations, as necessary.

MIL-MNGMT-SOW.DOC 21 subject to the restrictions on the title page of this proposal

• Follow-up with GC to ensure that the gaining PBO accepts the PBUSE transfer and assets are removed from the Product Managers (PM) PBUSE account.

•…