Attachment_1-MHU-83DE_SOW_Engineering_13_FEB_18.docx

ENGINEERING AND LOGISTICS

STATEMENT OF WORK FOR

THE

MHU-83D/E AERIAL STORES LIFT TRUCK

February 2018

Naval Air Systems Command Naval Air Warfare Center, Aircraft Division Research and Engineering Group SE and ALRE Department CSE/PSE DEV & ISE DIV Airborne Weapons SE Branch, Code 4.8.6.5 Lakehurst, NJ 08733

NAVAL AIR WARFARE CENTER

Aircraft Division

NAWCADLKE-17-SOW-4865-001

NAWCADLKE-17-SOW-4865-001 13 Feb 2018

1.0 SCOPE

This Statement of Work (SOW) identifies the specific tasks to be performed by the contractor for the MHU-83D/E Aerial Stores Lift Truck (ASLT) and the ancillary adapters indicated herein. The ASLT will be used to load and unload weapons from aircraft as part of the ground support equipment for the USMC expeditionary airfields.

1.1 PROGRAM OBJECTIVE. The program objective is to acquire MHU-83D/E units and ancillary adapters for the US Marine Corps to support ordnance/store loading operations. The first 6 LRIPUs will be delivered 12 months after contract award. After successful completion of a Government suitability and supportability evaluation on the LRIPUs, which is anticipated to take no longer than 4 months, follow on deliveries will commence at a rate of not less than 6 per month. The Government plans to award delivery orders for the remaining production units over four production years for up to 305 production units.

2.0 APPLICABLE DOCUMENTS.

1) 971480-70, Truck, Lift, Aerial Stores, MHU-83D/E (Technical Drawing Package)

2) DL65E35468, Fork Adapter Assembly, MHU-101/E (Technical Drawing Package)

3) DL65F35539, Strap, Quick Release, Tie Down, MHU-98/E (Technical Drawing Package)

4) 200414151, Six Inch Friction Bomb Roller Assembly (Technical Drawing Package)

5) 200334009, Universal Extender Assembly, 5K (Technical Drawing Package)

6) X200334008, Adapter Assembly, MHU-83/MJ-1 (Technical Drawing Package)

3.0 REQUIREMENTS.

3.1 General. The work required by this contract shall be performed in accordance with this SOW to manufacture, assemble, inspect and produce MHU-83D/E units and ancillary adapters in accordance with Government furnished drawing packages or otherwise provide as appropriate. The Contractor will provide the material and services needed to produce Low Rate Initial Production (LRIP) units for evaluation by the Government prior to Full Rate Production (FRP). Upon satisfactory completion of LRIP audits and evaluation, the Government intends to issue a release for production for units awarded on the contract. Design and development tasks and/or deliverables will not be required as part of this contract. The Integrated Logistics Support (ILS) requirements and services to be furnished for the end item production of the MHU-83D/E and ancillary adapters are provided separately.

3.2 MANAGEMENT

3.2.1 Post Award Conference (PAC). A Post Award Conference (PAC) shall be held no later than 45 days after contract award. This meeting will include a full review of the Integrated Master Schedule (IMS) during the PAC, all requirements of the SOW, CDRLs, and any other salient contract requirements will be discussed. Additionally, any preliminary questions or concerns that the contractor has with regard to the requirements of the contract and the Technical Data Packages (TDPs) may be discussed at this time. Agendas for the PAC will be developed by the Government. Minutes and Action Items will be agreed to at the conclusion of the PAC and distributed by the Government to the entire team. The presentation material developed by the Government for the PAC will be provided to the Contractor 10 working days prior to the review. The PAC shall be held simultaneously with the Logistics Guidance Conference.

3.2.2 Program Management Review (PMR). The Contractor shall present a Program Management Review (PMR) to the Government program manager and team. The first PMR shall be with the PAC. Additional reviews may be requested by the Government. All PMRs shall be at the Contractor’s facility or by telephone conference, and shall provide the Government with an accurate summary of the Contractor’s technical progress, program planning, and overall management approach and progress. Topics to be addressed at the PMRs shall include:

1. Contract status, progress tracking and reporting of milestones

2. Problem and risk identification, assessment, reduction and control

3. Streamlining recommendations

4. Technical review

5. Logistics review, Integrated Logistics Support Management Team (ILSMT)

3.3 Zinc Plating Environmental Compliance. For any items manufactured under this contract that offer the option of ASTM B633 Type III or Type IV plating on its Government drawing, if Type III plating is used it shall be RoHS and shall not utilize hexavalent chromium in its process. A written statement that the Type III coating process used is RoHS compliant and does not contain hexavalent chromium shall be submitted.

3.4 Quality Assurance

3.4.1 Quality Assurance Program. The contractor shall continually manage and improve the quality of all products and services delivered under this contract and the processes by which they are realized. The system used by the contractor and any/all sub-contractor(s) to manage quality shall be compliant with all requirements of, and at a minimum be functionally equal to, a current active version of the ANSI/ISO/ASQ Q9001, Quality Systems - Model for Quality Assurance in Design, Development, Production, Installation and Servicing. The Government shall have the right to audit the contractor's quality system for ANSI/ISO/ASQ Q9001compliance. The Government shall have access, for review and analysis purposes, to contractor Quality Management System (QMS) documents; raw data that have not been subjected to processing or any other manipulation; summarized, tabularized, or graphical depictions of the data; and records under this contract.

3.5 PRODUCTION

3.5.1 Low Rate Initial Production Units (LRIPUs). The Contractor shall produce a minimum quantity of six (6) MHU-83D/E units AND DELIVER with ancillary adapters identified in Table I for the first delivery order. The 6 LRIPUs shall be available for a functional and physical configuration audit within 364 days after contract award. The LRIPUs shall be utilized for Government suitability and supportability evaluation. A MHU-83D/E unit is comprised of one MHU-83D/E PN 971480-70 and the following ancillary adapters:

Table I: Adapter Quantities

3.5.2 Government Suitability and Supportability Evaluation. LRIPUs will be evaluated by Governments users at Marine Aviation Logistics Support (MALS) sites. Full Contractor support shall be required. This will include, at a minimum, maintenance instructions for the equipment, spare parts/materials and technical representative support (on an on-call basis). This evaluation will commence after delivery of the LRIPUs and will conclude within 120 days.

3.5.3 Full Rate Production. The contractor shall deliver MHU-83D/E units at a rate of 6 per month with accompanying ancillary adapter sets commencing upon completion of the Government evaluation.

4 .0 Integrate Logistic Support

4.1 Purpose

This section defines the requirements and services that are to be furnished by the Contractor in order to establish Integrated Logistics Support (ILS) for the Navy’s MHU-83D/E and associated equipment as identified in para 3.5.1 The following sections define the approach, tasks, activities and requirements necessary to satisfy the Navy’s overall objective of timely delivery of quality logistics support.

4.2 Integrated Logistics Support Requirements

4.2.1 Contractor ILS Management

The management of the Contractor’s ILS program shall be vested in a single manager who shall serve as the focal point for this procurement. This individual shall have the responsibility and overall authority for executing the ILS program. The Contractor’s Integrated Logistics Support Manager (ILSM) shall work in conjunction with Navy personnel in order to meet the ILS objectives set forth in this SOW.

4.2.2.1 Subcontractor(s)

Management of the ILS program may be delegated to a subcontractor(s), provided the prime Contractor maintains ultimate responsibility of the program. It is the Contractor ILSM’s responsibility to monitor subcontractor(s) efforts and review data deliverables for contract compliance prior to delivery to the Government.

4.2.3 ILSMT Reviews

ILSMT review meetings shall be scheduled in conjunction with other PMRs or on an as needed basis. The D/APML and Contractor ILSM will coordinate meeting times and locations which are mutually agreeable to both parties. The Governmentshall keep official minutes of these meetings. Meeting minutes shall be distributed to all concerned once they have been reviewed.

4.2.3.1 Logistics Guidance Conference

The contractor shall attend a Logistics Guidance Conference as part of the Post Award Conference The purpose of this meeting is to ensure a comprehensive understanding of the total logistics program and deliverable requirements between the contractor and NAVAIR.

4.2.3.2 Provisioning Conferences

The Government may host a Provisioning Guidance Conference as part of the logistics presentation to the Contractor at the Post Award Guidance Conference. The guidance conference provides information concerning preparation of the data for compatibility with the NAVSUP WSS database.

4.3 Logistics Supportability Requirements

The following paragraphs provide information relative to the planned operation and logistics support for the MHU-83D/E.

4.3.1 Logistics Product Data (LPD) Elements Input Data

The contractor shall provide the following data elements (refer to Table 1), which are defined in GEIA-STD-0007, for all parts identified in support of the End Item. The contractor shall provide this information in an excel document using the column headings and format provided in Table 2. This LPD Element Data shall be submitted for all components within the system and shall be updated IAW the CDRL L001. The contractor shall identify changes and additions within each LPD Element Input data submission by highlighting that amended portion of the Excel document. The data elements listed in the Table 1 shall be submitted IAW the CDRL L001.

Table 1 – LPD Elements Input Data Requirements and Definitions

Logistics Support Analysis Control Number

(LCN)

refer to the GEIA-HB-0007.

The contractor shall use the alpha-numeric classical LCN assignment method to ensure proper identification of an item to its next higher assembly.

a. First Precedent Reference Number. The line item is identified by a Government or industry association specifications, drawing, or standard number, e.g., FED, MIL, JAN, AN, NEMA, SAE, which completely identifies the item including its physical, mechanical, electrical and dimensional characteristics. (If the Government or industry association specification or standard number does not fully identify the item, then the actual manufacturer's identifying reference number becomes the first precedent reference number.) If the Government or industry specification, drawing, or standard completely identifies the item, at least one additional reference number (see additional reference number Type) citing a manufacturer or vendor reference number must be provided. b. Second Precedent Reference Number. When the line item is identified as "source control", "altered", or "selected" (MIL-DTL-31000C), the contractors assigned number is used.

c. Third Precedent Reference Number. The item identifying part, drawing, or catalog number of the actual manufacturer that supplies the item. The manufacturer is the company or Government activity exercising design control over the item.

A five-character code assigned by the Defense Logistics Services Center (DLSC) to the design control activity or actual manufacturer of an item as contained in the Cataloging Handbook H4/H8 Series.

For applicable codes, see Catalog Handbook H2 or go to http://www.dlis.dla.mil/hcfsch21.asp

Additional Comments: The contractor shall perform a Level of Repair Analysis (LORA) using Best Engineering Judgment. Utilizing the results, the contractor shall recommend repair/discard via SM&R. LORA results will be reviewed and discussed at Maintenance Plan reviews. NAVAIR maintains final authority in assigning SM&R codes.

codes see DOD 4100.39-M, Volume 10, Table 53.

For each potential ‘P’ source-coded item, the contractor shall determine a realistic unit price in United States dollars. This price shall approximate the actual acquisition unit cost to the US Navy at the time of initial procurement and in consideration of the projected procurement quantity. The contractor shall require that the vendors also provide realistic unit prices, with the above rationale. The contractor is authorized to use WebFlis or other commercial type provisioning screening product containing current Defense Logistics Information System (DLIS) data.

equipment, spares, repairs parts, etc. may be divided.

Mean time between failures (MTBF) is documented as both technical and operational characteristics. Technical parameters reflect the technical reliability that the system/equipment must demonstrate. In determining these parameter values, all failures and resultant actions to restore the item will be considered (e.g., a broken tail light is a technical, but not operational characteristic). Operational parameters reflect operational reliability and maintainability characteristics that the system must demonstrate. Only operational mission failures and the resultant tasks are included (e.g., engine failure will result in mission abort that is both an operational and technical failure).

The contractor shall provide a specific list of special tools that are required to perform any maintenance action - against the appropriate task. The contractor shall also detail the lubricants and coolants needed (as applicable) to operate the unit.

* The Contractor shall provide inputs for (x) selected rows

Table 2

4.3.2 Vendor Data Requirements

The contractor shall require as part of its purchasing agreements with component sub-vendors, that these sub-vendors submit product specification data (i.e. part number, Original Equipment Manufacturer (OEM) info, etc.

The vendor and supply information, and documentation, shall be the direct source of manufacturing/supply/OEM for the part. This information governs how DLA and NAVSUP will acquire the part(s) in question.

The direct vendor's part number and CAGE shall be documented as the primary source of supply.

If the primary vendor/suggested source of supply is not the design control authority, then the design control authority part number and CAGE, e.g. 30003 CAGE code items, shall be documented as an alternate/secondary supply reference.

If the direct source of manufacturing/supply/OEM of the part only sells their parts through a recommended distributor, then the required distributor's part number and CAGE shall be documented as the primary source of supply. In this case, the direct source of manufacturing/supply/OEM for the part shall have their part number and CAGE documented as an alternate/secondary source of supply.

Further, if the direct source of manufacturing/supply/OEM for the part does not sell directly and insists on requiring purchasing/sale through their distributor, then a letter documenting said fact shall be delivered. (CDRL L001)

4.3.3 Option for Interim Support Item List (ISIL)

The Contractor shall provide an ISIL if requested by the Government, reflects the recommended contractor furnished (including vendor items) spares and high usage repair parts required to support the MHU-83D/E for a period of 24 months. (CDRL L002)

4.3.4 Engineering Data For Provisioning (EDFP)

The EDFP shall be technical data for the MHU-83D/E and associated equipment referenced in para 2.0, which provides definitive identification of dimensional, material, mechanical, electrical, or other characteristics of all repairable assemblies and maintenance significant consumables. This data shall be adequate for identification/determination of maintenance requirements/actions and provisioning of the support items related to maintenance of all systems. The EDFP shall include, but not be limited to, a top down breakdown System Drawing and Associated Documents List, as well as copies of pertinent technical data package (TDP) elements provided in accordance with the requirements of this document. The required EDFP elements not included in the TDP shall be submitted in electronic format in Reference Number order. Drawings for AN, or MS part numbered consumable items are not required. (CDRL L003)

4.3.4.1 Modified Bill of Materials (BOM)

A modified BOM shall be provided in the form of a spreadsheet or database which identifies a top-down breakdown of the MHU-83D/E to the lowest level component and hardware. The modified BOM shall include the full Technical drawing package with the revision letter and revision date. This is needed to insure any future engineering changes during program development are easily identifiable to the program technical team. In addition, any future engineering changes during program development are properly incorporated into the LPD input data. (CDRL L005).

At a minimum the format shall provide the following information:

1. Drawing Number

2. Drawing nomenclature

3. Number of Sheets

4. Revision Letter 5 Revision Date

6. Parent Drawing Number

7. Manufacturer Prime Part Number or Specification Number

8. Manufacturer CAGE Code

9. Configuration Quantity

10. Change description (from previous) ie. Add, Delete, Revision

11. Manufacturers End Date

4.3.5 Statement of Prior Submission (SPS)

In cases where a drawing has been previously submitted to the US Government and that item has an established National Stock Number (NSN), a SPS may be submitted that would result in reduction or elimination of Supplemental Data for Provisioning (SDP) requirements. The SPS shall also include a listing of all drawings, specifications, processes, and Interface Control Documents (ICDs) previously delivered to the Government via the IDE. The SPS shall list the document's title, applicable part number, revision information, and release date. The SPS shall be provided in accordance with (CDRL L004).

4.4 Support Equipment & Special Tools Identification

If any software, support equipment or special tools are required for the operation and/or maintenance of the MHU-83D/E, the Contractor shall identify each for Government approval at the Post Award Guidance Conference.

4.5 TRAINING REQUIREMENTS

4.7.1 Training Requirements Summary

The training method established herein is designed to ensure adequate Navy training capability based on the results of the supportability task analysis and test evaluation for the MHU-83D/E. It shall enable Navy maintenance and instructor artisans to provide initial familiarization and/or formal follow-on training to fleet Support Equipment (SE) operators/maintainers. Training shall be part of the IPT/design process in order to ensure that design decisions are carefully considered for impact on training. All impacts shall be evaluated and resolved by training/human factors personnel. The training program shall focus on increased system reliability, and be designed to minimize training manpower requirements and maximize efficiency and effectiveness of training operations. Training products will be developed in accordance with CNATT 1540 guidance and will be used for Operator/Maintainer personnel, U.S. Navy Instructor personnel, and an initial cadre of program-essential personnel. The developed training materials will be incorporated into the formal school courseware, and if supported by task analysis, state-of-the-art web-based courseware shall be produced.

The Contractor shall develop a training program utilizing best value practices in support of the MHU-83D/E IAW the Navy System Training Requirements, Acquisition and Management instruction (OPNAVINST 1500.76A), Navy Training Requirements Documentation Manual (OPNAV Publication P-751-1-9-97), and Performance Specification, Training Data Products (MIL-PRF-29612B).

4.7.2 Training Integrated Master Schedule (IMS)

The Contractor shall develop, implement, update, maintain, and manage the MHU-83D/E Training Integrated Master Schedule (IMS). The Training IMS shall be managed and maintained as a standalone document. The Training IMS detail shall be such that it can be utilized for program planning, tracking, execution, decision/problem analysis, risk analysis and schedule reporting. The IMS shall contain the contract training tasks, events, and milestones from the Training Kickoff Meeting (KOM) to the final completion of all training related tasks and related events. The KOM shall be held in conjunction with the PAC. The Training IMS shall integrate the work requirements specified in this SOW along with the CDRLs. The Contractor shall quantify the risk and provide optimistic, pessimistic, and most likely duration for each IMS activity and event. The Contractor shall flow down the requirement of IMS to principal and/or critical sub-Contractors. The Government will provide an initial template of the Training IMS in MS Project for review at the Training KOM. It is the Government's objective to minimize schedule risk during the program with respect to the Training IMS with particular emphasis on all required training development and CNATT training management materials.

The Contractor's schedule shall have sufficient flexibility to accommodate unforeseen technical issues without major impact to the IMS while maintaining a reasonable work and resource regimen. The Contractor shall ensure schedule integration with its sub-Contractors and will ensure the validity of the sub-Contractor’s schedule data including demonstrating effective methods for incorporating schedule data from sub-Contractors into the Contractor’s Training IMS. All training related schedule information delivered or presented at program reviews shall originate from the Training IMS. The Contractor shall conduct critical path analyses of the tasks and report problem areas and corrective actions required to eliminate/reduce schedule impact. The Contractor shall deliver a Training IMS in accordance with CDRL L006.

4.7.3 Training Situation Analysis (TSA)

The Contractor shall conduct a TSA in accordance with OPNAVINST 1500.76C, NAVEDTRA Manuals 130-138, and MIL-HDBK-29612 guidance to identify the knowledge, skills and abilities, terminal and enabling objectives, curriculum, and course hours required to operate and maintain the MHU-83D/E. The Contractor shall develop the TSA to include all training requirements identified throughout the training analysis process.

Depending on the anticipated scope of effort regarding the training impact of the program the Contractor may only be required to conduct a Gap Analysis of the existing training for the identification and incorporation of new training requirements not previously covered in the existing training curriculum in lieu of developing a separate TSA. In this instance, the Contractor shall only be required to update the existing TSA (identified and provided as GFI) previously developed for related training pipeline for incorporation of the new training requirements.

The MHU-83D/E TSA will outline a system-level strategy to develop all required training for the program and identify impacts to existing training. The revised TSA shall also define and outline all necessary training requirements, equipment, milestones, and supporting data to support the selected training approach for instructional development. (CDRL L008)

4.7.4 Familiarization Training Conduct Requirements

The Contractor shall evaluate approved MHU-83D/E source data and develop familiarization training sessions in accordance with stated requirements contained herein.

4.7.4.1 Initial (Operator/Maintainer) Factory Training (IFT) Conduct The Contractor shall provide MHU-83D/E Initial Operator/Maintainer training to Navy instructors, initial cadre of fleet personnel, and other personnel deemed essential by the MHU-83D/E Program Manager. The Contractor shall utilize a “DRAFT” and condensed version of the deliverable Training Course Conduct Package (TCCP) to perform this training session. The initial factory training session provides the vehicle for the Contractor to validate the training course at the time of initial delivery to the Government. The training session should stress the performance of job related tasks in a practical/laboratory environment and be directly traceable to the Technical Manual (TM) and the Maintenance Plan (MAPL) for the end item, as provided by the Government. Class lecture time shall be held to a minimum. Trainees shall have as much time as can be given to learn/perform the tasks that will be required in the performance of future jobs. The student-instructor ratio shall not be greater than 10 to 1 in the theoretical phase of the course, and no greater than 6 to 1 in the practical application phase. Course instructional materials used during this training session shall be retained by the attending students. The IFT shall take place no later than 30 days prior to the delivery of units to the fleet, unless otherwise directed by the Government. The Contractor shall provide a Course Conduct Information Package (CCIP) at the end of the training session. The CCIP shall introduce the trainee to all aspects of the training system (e.g., syllabus, organization, training system operation and scheduling, instructor roles in the learning center, instructor evaluation and certificate of training and other supporting materials as required. (CDRL L009)

4.7.4.2 Initial (Operator/Maintainer) On Site Training/Train The Trainer The Contractor shall, upon request of the MHU-83D/E Program Manager, be prepared to provide MHU-83D/E Operator/Maintainer Training to Navy/Marine instructors, Fleet personnel, and other personnel. The Contractor shall utilize the latest version of the deliverables Training Course Conduct Package (TCCP) and Technical Manual to perform this training session. The training session should stress the performance of job related tasks in a practical/laboratory environment and be directly traceable to the Technical Manual (TM) and Maintenance Plan (MaPL) for the end item. Class lecture time shall be held to a minimum. Trainees shall have as much time as can be given to learn/perform the tasks that will be required in the performance of future jobs. The student-instructor ratio shall be approximately 10 to 1. Course instructional materials used during this training session shall be retained by the attending students. These training sessions shall be conducted no more than six times. MHU-83D/E. It is anticipated these training sessions will be conducted at US Navy sites located in Jacksonville, FL, Whidbey Island, WA, Sigonella, Italy, Misawa, Japan, Okinawa, Japan, and Kaneohe Bay, HI: or other sites as determined by the Government.

4.7.5 Formal Training Course Development

The Contractor shall develop the data products for the end item follow-on training program using the Content Planning Module/Learning Objective Module (CPM/LOM). The products should consist of a Job Duty Task Analysis (JDTA), and a Training Course Conduct Package (TCCP) as described in the following paragraphs.

The Contractor shall develop Computer Aided Instruction (CAI) initial operator/maintainer training for system level information which will be provided to the Training Agency for integration of MHU-83D/E training requirements. The training documents will be in the projects tab of CPM (IAW NAVEDTRA 138), the IG and TG will be developed into AIM LO Module. The OJT Handbook will be developed IAW NAVEDTRA 43100-1K and provided as an update to the Personnel Qualification Standards (PQS) identified NEC. Test items will be delivered in Corporate Enterprise Training Activity Resource Systems (CeTARS) format provided by the Government. This delivery will include lesson design information and builds upon the standards specified in the NAVEDTRA 136 and CNATTINST 1554.1, and PowerPoint requirements, (which are provided in accordance with CNATT N9 DELTIS NKO site: https://wwwa.nko.navy.mil/portal/aviation/home/DELTIS) in the following documents:

4.7.5.1 Job Duty Task Analysis (JDTA)

The Contractor shall prepare a Job Duty Task Analysis (JDTA) in accordance with the Job Duty Task Analysis Management Manual (NAVEDTRA 137A) on the impacts of the MHU-83D/E to the impacted NEC/MOS Occupational standards using Authoring Instructional Material (AIM) Content Planning Module/Learning Objective CPM/LO) to document the mission, collective and individual task information. This information shall support the development of the MHU-83D/E Operator and Maintainer Courses. The JDTA should identify duties/tasks previously analyzed and developed from existing training courses. The JDTA will be used by Government and Contractor training managers to track course development during scheduled In Process Reviews (IPRs).

In addition, the Contractor shall provide a listing of knowledge, skills, attitudes and learning objectives for the tasks that have been verified and selected for training. This will be documented as a targeted JTDA within the COMNAVAIRLANT tab within the AIM/CPM tool.

The Contractor shall attend two Training IPRs, a curriculum kick-off meeting and a development meeting, at a mutually agreed site. They may be held separately or in conjunction with the Logistic In Process Reviews (IPR’s) and/or Technical Manual Reviews. (CDRL L007)

4.7.5.2 Training Course Conduct Package (TCCP)

The Contractor shall develop a Training Course Conduct Package using the Content Planning Module/Learning Objective Module (CPM/LOM). The TCCP must be capable of supporting Navy SE operator/maintainer personnel in existing MHU-83D/E Naval Enlisted Classifications (NEC) and Military Occupational Series (MOS).

The TCCP shall consist of a Training Project Plan, Job Duty Task Analysis Inputs, Course Training Task List, Training Course Control Document, Curriculum Outline of Instruction, Lesson Plan, Trainee Guide, Testing Package and Instructional Media Package in accordance with the most current version of NAVEDTRA 130, Course Development Guide, NAVEDTRA 136 Integrated Learning Environment Course Development and the most current version of CENNAVAVNTECHTRA 1540, Curriculum Management Manual, CENNAVAVNTECHTRAINST 1554.1 Interactive Multimedia Instruction (IMI) Developer’s Guide.

The Content Planning Module (CPM) and Learning Object (LO) Module will be used for the development of all training course content and will be directly traceable to the MHU-83D/E TM and MaPL. The above mentioned deliverables will be developed in the order stated IAW with the Training IMS and delivered incrementally to the Government. A Training timeline for these deliverables will be reviewed during the Training KOM and IPRs. The Government SE Training Manager and Contractor Training Manager (CTM) shall coordinate the development of the above documents in order to meet the Center for Naval Aviation Technical Training (CNATT) requirements and projected delivery date. The CTM shall plan for a monthly agreed upon telephone conference, with the Government SE Training Manager and CNATT representatives, to discuss issues and the status of the training package development. If the Contractor has a commercial training course already established it can be used as the basis for the TCCP. The Contractor shall identify if training personnel have received training in AIM CPM/LO and what clearance they possess in order to work in Government software or how they plan to obtain such training and clearances. The contractor personnel must have the training, clearances, CAC access and readers prior to training kickoff event, The Contractor shall describe how compliance in AIM CPM/LO will be utilized to produce the data products for the TCCP. (CDRL L007)

4.7.5.3 Instructional Performance Requirements Document (IPRD) The Contractor shall develop IPRD. This document shall describe the analysis process used to define the training requirements for the Operator/Maintainer and associated required skills to operate and maintain the ancillary equipment. The IPRD shall provide the mission, and collective and individual task information as well as the specific behaviors, standards, and conditions for the performance of the tasks required for the MHU-83D/E Operator/Maintainer to successfully perform their duties. The Contractor shall analyze and identify the Level of Learning (LOL) and Level of Interactivity (LOI) for each training task to aid in the development of lessons incorporating effective instructional strategies, activities and interactivity. The Contractor shall prepare and deliver the Instructional Performance Requirements Document (IPRD) in accordance with CDRL L010.

4.7.5.4 Instructional Media Design Package (IMDP)

The Contractor shall develop the MHU-83D/E IMDP which describes and supports the media selected for the lessons for both the Operator and Maintainer courses. The Contractor shall identify the learning objectives, subject matter content and testing material in a manner that permits the Government to assess the proposed instructional approach, content and structure of the lesson. Lesson Specifications shall be consistent with the data contained in the IMRD and Instructional IMDP-Style Guide. Lesson Specifications shall include at a minimum: Lesson Title, Learning Objectives, LOI, Instructional Strategies (Inquiry, Practice, etc.), Media to be Used (still graphic, animation, video, audio, text, etc.), Content Outline, Testing/Embedded Strategy, and Reference Documentation. The Contractor shall develop and deliver the materials in accordance with the IMDP.

The prototype lesson will demonstrate and gain approval of the interface, graphic conventions, and instructional design strategies to be used for the remaining production effort that will be developed. The IMDP-Style Guide details conventions, design strategies, lesson specifications, and reference materials required to support the instructional media. The design of the content will take into consideration the function, description, and operation of the course for the successful infusion of advanced technology. The delivered prototype lesson must pass ADL, Test Track, and GCATS testing (CNATTINST 1554.1) prior to lesson production. The IMDP-Style Guide also defines the processes for producing the products to include at a minimum: Screen Layout and Design, Media Graphic Design, Navigation, Instructional Strategies, Testing/Embedded Question Strategies, Content, Branching, Feedback, 4th Addition SCORM Standard, Shareable Content Data Repository Use, ADL requirements, Meta-tagging Procedures, LMS Functions, Design, Structure and Use, Configuration Item Identification and Procedures, File Naming Conventions, and other areas as required by the Style Guide. All training products shall be produced at screen resolution compatible with schoolhouse requirements. (CDRL L011)

4.7.6 Government Furnished Information GFI

Upon request, the following materials will be provided by the Government, at or soon after, the Post Award Guidance Conference. The GFI will assist the Contractor in the development of training course materials:

a. Copy of existing legacy formal course materials that provide background information on comparable, legacy CSE.

b. Technical Manuals for legacy CSE will be provided, as approved by the Contracting Officer’s Representative (COR), for source data analysis and comparison by the Contractor during development of course material.

c. CPM/LOM software package and training if required.

d. Test item will be delivered using Microsoft Excel spreadsheet for Maintainer course only.

e. Copies of the most current versions of NAVEDTRA 130, NAVEDTRA 136, MIL-PRF-29612, CENNAVAVNTECHTRA 1540, CENNAVAVNTECHTRAINST 1554.1 and all CDRL referenced Data Item Descriptions (DIDs).

4.9 Item Unique identification (IUID) Plan/Marking of U.S. Military Property In accordance with DFARS Clause 252.211-7003 item Identification and valuation, the contractor is required to mark and register all end items and their components meeting the requirements called out in MIL-STD-130N. These include components for which the Government unit acquisition cost is $5,000 or greater, or any component, subassembly or embedded part that is serially managed, mission essential or a controlled inventory item. The IUID Plan shall be in accordance with (CDRL L012).

4.9.1 Construct and Method

Details on creating the UID and the marking method are contained in MIL-STD-130N. The UID may be either UID Construct #1 or Construct #2 with Construct #2 being the preferred method.

4.9.2 UID Location and Marking

The locations and marking methods selected should bear no impact on the performance of the part and minimal configuration change(s) to the part. The UID (including 2D Matrix) should be incorporated onto the data plate. If the 2D Matrix can’t be incorporated onto the data plate, a 2D Matrix sticker can be applied onto the main data plate provided it can be done without covering any critical data. When the 2D Matrix Data is placed directly onto the data plate, the Part Number, Serial Number and CAGE human readable characters are not required. If the above cannot be accomplished, a separate data plate can be attached which contains the 2d Matrix plus the human readable characters for the Part Number, Serial Number and CAGE. This added data plate should be attached in close proximity to the main data plate.

4.9.3 Permanency and Legibility

The UID marking and identification plates, tags, or labels when used on equipment, parts, assemblies, subassemblies, units, sets, or groups shall be permanent during the normal life expectancy of the item and be capable of withstanding the environment test and cleaning procedures specified for the item. Legibility shall be as required for ready readability as per MIL-STD-130N

4.9.4 UID Registration

The prime contractor has the responsibility to furnish IUID data to the IUID registry. Data submission of IUID data and acquisition cost should be via Wide Area Work Flow (WAWF), IUID XML file, IUID flat file or web entry. Additional information regarding data submission as well as the actual markings can be found at http://www.acq.osd.mil/dpap/UID/.

4.9.5 UID Records

The contractor shall maintain an accurate, current list of UIDs for all manufactured items on this contract and supply to the Government upon request. The list shall include P/M, Serial Number, CAGE, UID location, construct used, how it was marked and the registration method used.

4.10 Packaging, Handling, Storage, and Transportation (PHS&T)

4.10.1 Packaging Requirements Data

The shipping and packaging for overseas shipment for the MHU-83D/E, adapters/equipment identified in para3.5.1 shall be…