Exhibit B DID DOCUMENT.PDF

FWS-I DIDs

DATA ITEM DESCRIPTIONS

(DID)

2 June 2020

Contract Data Requirements Lists (CDRLs – DD Form 1423s) that apply to this contract are integrated into this SOW. The contractor shall prepare and deliver the data and information in accordance with the requirements, quantities and schedules set forth by these CDRLs. The issue of the Data Item Description listed in the Acquisition Management Systems and Data Requirements Control List (AMSDL) (DOD 5010.12-L), applies unless explicitly stated elsewhere in the solicitation/contract. AMSDL can be accessed via the web at:

http://assist.daps.dla.mil/online/start/ http://assist.daps.dla.mil/online/start/ http://assist.daps.dla.mil/online/start/

FWS-I CDRLs and DIDs 2 June 2020

Title Systems Engineering Plan

Data Item Description (DID) Number

DID-001

Description

The contractor shall prepare a System Engineering Plan (SEP) that describes the contractor’s processes and resources to incorporate System Engineering (SE) practices to build, test, deliver, and support the ENVG III. The SEP will also address the contractor’s processes and resources to incorporate System Engineering practices to design, build, test, deliver, and support the FWS-I and the interoperability of the ENVG III and FWS-I.

Preparation Instructions

For guidance on content and form of the SEP the contractor is encouraged, but is not required, to refer to the Department of Defense guide for System Engineering Plan Preparation, April 2008, Version 2.01, and Addendum to SEP Preparation Guide v2.01, 2 July 2009.

Format

Contractor format is acceptable.

Content

The SEP shall include, but is not limited to the following:

• Discussion of main FWS-I components (weapon sight, smart battery pack) and primary system sub-components (thermal sensor, display, optics, system electronics).

• Discussion of wireless RTA components (wireless transceivers, wireless prototcol, RTA processor, RTA algorithms).

• System performance to be achieved for each device including KPPs, to include a system and component/sub-component power allowance table.

• FWS-I Interface/Interoperability with other equipment (ENVG B, IVAS, etc.).

• Contractor’s SE organizational integration (technical, Quality & Test, logistics), including sub-contractors.

• Contractor’s SE approach to the following topics for the system and components/sub-components:

reliability, maintainability/supportability, Chemical, Biological, Radiological, and Nuclear (CBRNE), Electromagnetic Interference (EMI), Safety/Environmental, Human Factors Engineering (HFE), producibility, Quality & Test (Q&A), training.

• FWS-I technical risk management (technical, schedule, cost).

Title Integrated Program Management Report (IPMR)

Data Item Description (DID) Number

DID-002

Description

The objective of the IPMR is to provide a tool that provides sufficient detail and insight to the ENVG III and FWS-I Integrated Product & Process Team (IPPT) with the current contract status and to project future contract performance. The IPMR will address the following areas of interest: Work Breakdown Structure (WBS), Organizational Categories, Baseline, Staffing, Integrated Master Schedule (IMS), Explanations and Problem Analyses, and Cost History and Forecast File.

Preparation Instructions For guidance on content and form of the IPMR the contractor shall refer to the OUSD AT&L IPMR Implementation Guide, 31 July 2012 and DI-MGMT-81861.

Format

Microsoft Project 2013 or higher is the recommended format for the contractor’s IMS.

Content

• Work Breakdown Structure (WBS). Defines performance, schedule and cost data by product-oriented

WBS. For guidance on WBS content and format refer to MIL-STD-881C.

• Organizational Categories. Defines performance, schedule and cost data by the contractor’s organizationl structure (e.g., Functional or Integrated Product Team (IPT)).

• Baseline. Defines changes to system performance.

• Staffing. Defines staffing forecasts.

• IMS. Defines actitivies and tasks for the entire effort under the contract. Tasks/activities shall be logically linked, showing predecessor/successor relationships, and crticial path.

• Explanations and Problem Analyses. Narrative report used to provide analysis of areas WBS, Organizational Categories, Baseline, Staffing, and IMS.

• Cost History and Forecast File. Defines the time-phased historical & forecast cost submission and shall indicate whether effort is below, at, or above cost.

Title Risk Management/Mitigation Plan

Data Item Description (DID) Number

DID-003

Description

The contractor shall use a Risk Management/Mitigation Plan or an equivalent type document for the IPPT to document, track, and manage areas of risk during the life of the contract.

Preparation Instructions

Format For guidance on content and form of the Risk Management Plan the contractor shall refer to DI- MGMT-81808B.

Content Identify initial areas of risk for all functional areas (SE, Program Management Logistics, Manufacturing, etc.).

• Mitigation actions, timelines, and deadlines to manage risk.

• Green/Yellow/Red characterization or equivalent.

• Provision to add new and/or change characterization of existing risk factors.

• Track throughout performance period.

Title IPPT Agenda and Read-Ahead Brief

Data Item Description (DID) Number

DID-004

Description

The IPPT co-chairs will develop an agenda for all reviews/meetings. The contractor shall provide an agenda and read-ahead brief for all meetings/reviews no later than 2 days before the scheduled review/meeting.

Preparation Instructions

Format

Contractor format is acceptable. Microsoft PowerPoint is recommended.

Content As required by IPPT meeting format and IPPT agenda.

Title IPPT Action Items List & Meeting Minutes

Data Item Description (DID) Number

DID-005

Description At the end of each review/meeting, the contractor and Government shall jointly prepare action items. The action items list provided a record of all actions required by the IPPT to address and/or resolve issues identified during the course of the IPPT meeting.

At the end of each review/meeting, the contractor and Government shall jointly prepare meeting minutes. IPPT minutes provide a record of the IPPT meeting, attendance, agenda topics discussed, issues raised, decisions taken and recommendations.

Preparation Instructions

Format

Contractor format is acceptable.

Content

1) Action Item List:

There shall be a single IPPT action item list. Multiple action item lists shall not be generated, except at specific direction of the IPPT. At a minimum, action item list content content shall include:

• Action item description

• Date opened

• Responsible party

• Due date (suspense)

• Current Status

• Date closed

• Resolution Status (Open/Closed)

• Maintains visibility of all action items (open and closed). A separate tab may be maintained for closed items.

2) Meeting Minutes:

At a minimum

• Attendee list

• Review of prior IPPT action items

• Final briefing slides as an attachment

• Agenda items o Issues/Discussions o Decisions o Special IPPT’s working group assignments

• Date and purpose of next IPPT meeting

Title Not used

Data Item Description (DID) Number

DID-006

Description

Preparation Instructions

Format

Title Government Property Inventory Report

Data Item Description (DID) Number

DID-007

Description This report enables the contractor to periodically provide to the DoD Service/Agency an inventory listing of Government Property (i.e., both Government Furnished Property (GFP) and Contractor Acquired Property (CAP)) in the contractor’s possession (to include subcontractors) by contract.

This DID is applicable to all contracts where Government Property/Material/Equipment will be furnished by the Government (i.e., GFP) or acquired, fabricated, or otherwise provided by a contractor (i.e., CAP) in performance of a contract.

This DID contains the format and content preparation instructions for the data deliverable resulting from the work task described in the solicitation.

Preparation Instructions

Format

The report shall be electronic .xls or .xlsx compatible

Content

The report shall contain the following columns/data fields:

Contract Number

A. Manufacturer CAGE Code (if known) B. Item Name C. Item Description D. Manufacturer Name E. Manufacturer Part Number F. Manufacturer Model Number G. Material Control Number (MCN) (if applicable) H. Serial Number I. National Stock Number (NSN) J. Quantity K. Unit of Measure L. Unit Acquisition Cost M. Location N. Sub Location (if applicable) O. Unique Item Identifier (as registered in the IUID Registry) P. Type of Government Property (i.e., Government Furnished Property (GFP) or Contractor Acquired Property

(CAP)

Q. Classification of Government Property (i.e., Communication Security (COMSEC), Equipment (EQP), Material (MAT), Special Test Equipment (STE), or Special Tooling (ST)) R. Posting Reference S. Date of Transaction / Date of Acquisition T. Date Placed in Service U. Date of Last Physical Inventory V. Condition Code

Title Reliability Program Plan

Data Item Description (DID) Number

DID-008

Description

The contractor shall prepare and submit to the IPPT, for concurrence, a Relaibility Program Plan for the system, and all major components.

Preparation Instructions

• Modification/Revision only upon written concurrence of IPPT Chairpersons

Format

Contractor format is acceptable.

Content

The Reliability Program Plan (RPP) shall include, but is not limited to, the following:

a. The Reliability Requirements. The report shall include all reliability requirements and the source of the requirements. Any derived requirements shall include all assumptions related to the derivation of the reliability metric.

b. System Reliability Model (SRM). This report shall address the methods and tools that will be used for developing and refining the SRM. The report shall document how the SRM will be updated as the design evolves and new information about failure modes is identified. The SRM is a graphical depiction of the system with an underlying analysis such as Reliability Block Diagram, Fault Tree, or Event Tree.

c. Critical Elements. The report shall identify how critical elements will be identified. Critical elements are defined as those elements (subsystems/assemblies/subassemblies) whose failure impacts mission completion, essential functions, or safety; or elements whose failure rates contribute significantly to the overall system.

d. Reliability Management and Organization. The report shall include an organizational chart that provides visibility into the management and organizational structure of those responsible and accountable for the conduct of reliability activities. The organization structure shall clearly define how those responsible for reliability activities interact with the design, systems engineering, test and evaluation, cost, and supportability teams. The organization structure shall also depict the interface between the Government and all subcontractors/suppliers (when applicable).

The report shall define all responsibilities for the reliability team.

e. Design for Reliability (DfR) Activities. The report shall document all planned DfR activities and the resources required to conduct the associated activities. DfR encompasses the management and reliability engineering activities executed during the design stage that identify and characterize failure modes at the lowest indenture levels possible before system-level prototyping.

f. System Constraints, Loads, and Stresses. The report shall document the expected constraints, loads, and stresses for the life cycle of the system and the impact on the system design. The report shall also document plans to verify and validate the expected constraints, loads, and stresses. The plan should include all stresses and loads that the system may encounter during normal operational usage (as defined by the User) and their effect on the reliability of the system.

g. Reliability Assessment. The report shall document planned reliability assessments and how they are integrated into the program’s master schedule. The report shall document what tools and techniques will be used for assessing the reliability throughout its development. Any life limited items shall be identified and a mitigation plan developed to minimize their impact on life cycle costs.

h. Failure Mode, Effects, and Criticality Analysis (FMECA). The report shall document how failure modes and their effects will be identified. The report shall also document how this information will influence system design and corrective action analysis, development, and implementation.

i. Closed-Loop Failure Mode Mitigation Process. The report shall document how analysis, test, and field failure modes will be monitored, assessed, prioritized, and communicated throughout the organization. The report shall also document what strategies will be used for identifying, developing, and approving corrective actions to eliminate failure causes throughout the life cycle.

j. Reliability Growth Program. The report shall document the reliability growth program and any associated risks with the planned program. The reliability growth program shall include a reliability growth planning curve, if applicable. The reliability growth plan shall document all assumptions as influenced by program management (e.g.

initial mean time between failure (MTBF), management strategy, the MTBF goal , the planned fix effectiveness factor, duration of testing, average lag time associated with corrective action, and number of corrective action periods). The report shall also document all plans for reliability growth tracking and projection.

k. Reliability Test Plans. The report shall document all planned reliability test(s) and other development or operational tests where reliability data will be collected for failure mitigation and reliability assessments. Any data collection requirements shall also be addressed.

l. Reliability Reviews and Reports. The report shall document all planned reliability reviews and reports. These reviews shall be integrated into the master schedule and may include Preliminary Design Review, Critical Design Review, Test Readiness Reviews, Failure Review Boards, and Reliability Assessment Conferences.

n. Resources. The report shall document all resources required to conduct the reliability program. Resources may include:

• Subject matter experts

• Test assets

• Test facilities

• Environmental Stress Screening (ESS)

• Highly Accelerated Life Testing (HALT) / Highly Accelerated Stress Screening (HASS)

• Physics of Failure

• Reliability Assessment Tools

• Failure Mode Analyses

• Data Collection

o. Assumptions. All assumptions shall be documented in the report.

Title Test Procedures

Data Item Description (DID) Number

DID-009

Description developmental, qualification, or acceptance testing. It identifies items to be tested, the test equipment and

Preparation Instructions

Format

Contractor format is acceptable

Content

• The contractor shall prepare and submit for concurrence Test Procedures in accordance with DI- NDTI-80603A for the systems and major components (SOW 3.2.2.1 and 3.2.2.2) in compliance with the QVM. The contractor shall use the same Test Procedures for all testing (CDT, PQT, FAT, AT, and CI) unless modifications are agreed upon by the Government.

• Submission of all system Test Procedures shall occur no later than 15 days after the PDR.

• Government review/comments will be provided within 30 days.

• Final Test Procedures are due 15 days after receipt of Government comments.

• Submission of major components test procedures shall be determined by the IPPT. Upon submission of procedures the Government review/comments will be provided within 45 days.

• Final Test Procedures are due 21days after receipt of Government comments.

• Redlined test procedures are due no later than 30 days after successful completion of qualification testing.

Government review and comments will be provided within 30 days. Final test procedures are due 10 days after receipt of Government comments.

• Final approval of the Test Procedures shall occur prior to commencement of testing.

• Any modifications to the agreed-upon procedures shall require concurrence in writing by the Government prior to being implemented.

• The document shall be compatible with Windows Operating Systems and Microsoft Office 2013 products (i.e., Word, Excel, PowerPoint, Project, etc.).

The test procedure identifies the step-by-step testing operations to be performed on items undergoing support required, the test conditions to be imposed, the parameters to be measured, and the pass/fail criteria against which the test results will be measured. The document is a compilation of individual test procedures for related elements of a system, subsystem, or equipment.

Title Failed Item Analysis Report (FIARs)

Data Item Description (DID) Number

DID-010

Description The FIAR documents test failures that occur during system and major component-level CDT, PQT, FAT, AT, CI testing, reliability testing, and Government DT/OT. The FIAR shall include identification and verification of the failure mode, a summary of the failure analysis and identification of the root cause(s), disposition of the failed item(s), action taken to eliminate the root cause(s) and to prevent recurrence, corrective action for all materiel affected including items that may have been delivered to the Government, verification/validation the corrective action was effective, history of the failure, containment of the failure, recommended disposition of the lot, and applicable Sub-contractor Corrective Action Report.

Preparation Instructions The contractor shall submit to the IPPT for concurrence, within time limits a final FIAR. The final FIAR, shall include, if necessary, a Sub-contractor Corrective Action Report (SCAR). E-mail is the preferred method of FIAR submittal.

The contractor shall prepare a separate FIAR for each failure. The contractor may prepare a combined FIAR for multiple failures of the same root cause if agreed to by the IPPT.

Format Contractor format is acceptable; however, the IPPT at the Post Award Conference shall concur with the complete proposed content of the FIAR, and a list of personnel to be notified of failures. All subsequent FIARs shall adhere to the IPPT-concurred format. The FIAR shall not be considered closed until the Government has concurred with the report. Government approval is required prior to shipment of any potentially affected production units.

Content The FIAR shall include, but is not limited to:

• Subsystem or component failed, to include part number, serial number, and manufacturer

• Design code or process revision for the failed subsystem

• Description of test failure

• Failure date/time

• Test (or sub-test) failed to include reference to particular section of the test procedure under exection at the time of failure

• Operating hours and/or cycles at the time of failure

• Unit(s) affected

• Lot Number(s) affected and Lot size

• Sample size for the test failed

• A summary of the analysis, including o Identification and verification of failure mode. If measurements are made during the failure investigation the FIAR shall include results of all measurements made and expected/required values for each measurement.

o Failure root cause, to include why the defect was not detected during normal production, and impact to similar product or processes o Action taken to elimate root cause(s) and to prevent recurrence o Proposed corrective action for all materiel affected, including items delivered to the Government

Include process controls in place or planned to prevent the problem from recurring o Test results showing validation/verification of corrective action is effective o History of the failure mode in all CI as well as in production testing and ESS o Containment of the failure, including end items in plant and already delivered to the Government as well as material work in process, at receiving, or in transit o Recommended disposition of failed item(s) and lot o Sub-contractor Corrective Action Report (SCAR), if applicable.

Title Test Failure Notification

Data Item Description (DID) Number

DID-011

Description The Contractor shall notify the Government within 48 hours of failure occurrence for failures occurring during system and major component testing PQT, PQT, FAT, AT, and CI testing, and reliability testing.

Preparation Instructions Electronic/E-mail is preferred method of delivery.

Format Contractor format is acceptable.

Content Notification content shall include, but is not limited to:

• Brief description of test failure

• Failure date/time

• Test failed

• Hours on test

• System that failed (S/N)

• Lot Number(s) affected

• Major component failed

• Failure mode

Title Warranty Process Flow Chart

Data Item Description (DID) Number

DID-012

Description The Warranty Process Flow Chart gives an overview of the warranty process from the time the customer contacts the contractor to the time when the product is shipped back to the customer.

Preparation Instructions

Format Contractor format is acceptable.

Content The flow chart will lay out how the product is routed through the contractor’s facility, the internal departments involved in the process, reports generated as a result of the warranty return, and the internal and external process to approve product being returned to the customer.

Title Warranty Performance Reports

Data Item Description (DID) Number

DID-013

Description The Contractor provides a warranty, which extends from the date of initial government acceptance to the warranty expiration date. During the warranty period, the contractor repairs or replaces – at no cost to the Government – any system, if required, and related spare parts that fail under normal operations, while in storage, or during transportation.

The Warranty Status Report provides the Government a record of all warranty repairs.

The contractor shall submit the first report one month after the Government’s first fielding of the system(s) under this contract. The contractor shall submit a monthly Warranty Performance Reports, whether or not there is warranty return activity on the system(s).

Preparation Instructions

Format Contractor format is acceptable.

Content

• Repair Authorization Log transactions, warranty only

• Returning Agency/Customer (if known)

• Date of return

• Failure tracking o Failure mode o Failure root cause o Proposed corrective action o Validation/verification of corrective action o Sub-contractor Corrective Action Report (SCAR), if applicable

• Date of repair

• Shipment date of repaired/replaced system

• Man hours per repair

• Component cost

• Components replaced

• Float asset inventory

• Test equipment status

Title Logistics Support Plan

Data Item Description (DID) Number

DID-014

Description The Logistics Support Plan shall be developed for the FWS-I system and TMDE software, special tools, fixture, and interface equipment from a supportability analysis completed in accordance with MIL- PRF-49506 and ANSI GEIA-STD-007. The logistics support requirements shall consist of provisioning data, New Equipment Training (NET), TRADOC training materials (training package, Interactive Electronic Technical Manual (optional), system support package (SSP), and Technical Manuals (TMs) (Operator and Field-level TMs), including repair parts and special tools list (RPSTL), Test Maintenance and Diagnostic Equipment (TMDE), Quick Reference Card (QRC), and technical orders (TOs) as applicable. After establishment of the initial logistics baseline, any changes effecting form, fit, or function of the system down to the spare parts level shall be submitted to the Government for approval.

Upon receipt of notification of proposed changes, the Government will identify the required contractual documentation for delivery and acceptance.

Preparation Instructions The Logistics Support Plan shall be developed from a supportability analysis completed in accordance with MIL- PRF-49506 and ANSI GEIA-STD-007.

Format Contractor format is acceptable.

Content The Logistics Plan shall include:

• Specific tasks and methodology the contractor will use to support the Government’s equipment and to achieve the required operational availability.

• Training required.

• Tools and test equipment required.

• Manpower required.

• Interface plans with customer.

• Shipping methodology.

• Asset visibilityand tracking.

• Spares management and control.

• Contract support locations and points of contact.

• Customer points of contact.

• Period of performance.

• Schedule for implementation.

• Turn around time.

• Failure mode analysis (including root cause, corrective action implementation, validation/verification).

• TMDE software, special tools, fixture, and interface equipment warranty, calibration standards, and configuration control.

Title Level of Repair Analysis (LORA)

Data Item Description (DID) Number

DID-015

Description

The LORA is an analysis to determine the optimum maintenance concept for a system. The LORA is used to determine the repair level within the Army maintenance system.

Preparation Instructions

Format Contractor format is acceptable.

Content For guidance, on the Level of Repair Analysis (LORA) the contractor should refer to:

• AR 700-127

• AR 750-1

The contractor shall perform a LORA to determine the optimum maintenance concept. The LORA is used to determine the repair level within the Army maintenance system .

• LORA shall be performed on all materiel.

• The LORA shall determine the optimum maintenance levels for repair actions and recovery of the end item and components. At a minimum, the LORA shall consider availability and requirements for additional tools, support equipment, and skills in intended supporting units.

• The LORA shall address the requirement to minimize additional special tools and test equipment for new equipment.

• The LORA process shall be initiated as early in the life cycle as possible to aid in assessing the supportability of a system.

o The initial LORA shall be submitted as part of the contractor’s proposal.

o Repair requirements shall be evaluated as the system matures.

o As part of the post deployment evaluation, the LORA shall be repeated no earlier than 1 year and no later than 3 years from First Unit Equipped Date (FUED), using actual reliability data from fielded equipment.

• An output of the LORA shall be the Maintenance Allocation Charts (MACs). MACs shall reflect the recommended/approved maintenance concept.

• An output of the LORA shall be a recommended optimum maintenance concept, with supporting data.

Title

UNASSIGNED

Data Item Description (DID) Number

DID-016

Description

Preparation Instructions

Title

Logistics Demonstration (LD) Plans

Data Item Description (DID) Number

DID-017

Description

The objective of the LD is to demonstrate the system(s) meet all logistics/maintainability and Human System Integration requirements and to identify any system design changes needed for improved supportability and/or reduced life cycle cost. The contractor shall plan and conduct the LD(s) for the system(s) prior to Government OT using: LD Plan(s) concurred to by the IPPT, Government personnel representative of the target audience trained by the contractor, and contractor-provided training material and technical manuals.

Preparation Instructions The contractor shall prepare an LD Plan for each separate LD event.

Format Contractor format is acceptable

Content Each LD plan shall include:

• Crew-level and Maintainer-Level Training.

• Crew-level and Maintainer-Level Maintenance TasksTypes/Quantities of Equipment & Materials Used.

• Special Tools, Fixtures, and TMDE.

• Support Equipment and Calibration Support Requirements.

• Technical Publications.

• Safety Equipment.

• Spares, Repair Parts, Consumables.

• System Support Package Components List (SSPCL).

• System Support Package (SSP).

• Modules Required for Fault Insertion.

• Test Selection Rationale/Scenario/Ground rules.

• Test Method.

• Test Acceptance Criteria.

• Test Ground rules.

• Fault Insertion.

• Test Flow Steps.

• Test Log.

• Data Records.

Title

Logistics Demonstration (LD) Reports

Data Item Description (DID) Number

DID-018

Description

The LD Report is the formal record of results of the LD conducted IAW the LD Plan.

Preparation Instructions The contractor shall prepare an LD Report for each separate LD event.

Format Contractor format is acceptable.

Content The LD Report shall report results of LD and record how the system does/does not meet all logistics/maintainability and Human Systems Integration requirements and shall identify any system design changes needed for improved supportability and/or reduced life cycle cost.

. The LD Report shall contain the following:

• Test Method

• Test Acceptance Criteria

• Test Ground rules

• Fault Insertion

• Test Flow Steps

• Test Results Log

• Repair times per fault inserted.

• Analysis and recommendations o Corrective action required o Verification/validation of corrective action o Corrective action implementation recommendations/plan

Title

System Support Package Component List (SSPCL) and System Support Package (SSP)

Data Item Description (DID) Number

DID-019

Description

The SSPCL is a list comprised of all the items contained in the SSP to include the Technical Manuals, Training, common and any required special tools, Spares and Repair Parts, lubricating/cleaning items, and any other item required to support the system during the LD and any required Operational Test, including the Air Jump.

Preparation Instructions The contractor shall prepare a separate SSPCL and SSP for each LD and OT event

Format Contractor format is acceptable.

Content

SSP shall consist of the following items:

• Crew-level and Maintainer-Level training material, as required

• Special tools and fixtures

• Support equipment and calibration support requirements

• Technical publications (TMs, etc.)

• Safety equipment

• Spares, repair parts, consumables

• Module required for fault insertion

• Crew-level and Maintainer-Level resources

Title Instructor and Key Personnel Training (I&KPT)

Data Item Description (DID) Number

DID-020

Description

I&KPT shall reflect the system(s) being provided under this contract and in accordance with the approved maintenance concept. The contractor shall develop a Crew-level training course and a Maintainer-Level training course. Training shall provide students with the skills necessary to operate and maintain the system(s).

Training shall include, but is not limited to, all tasks contained in the -10 and -23&P TMs.

Preparation Instructions

Format Contractor format is acceptable.

OR

The Contractor shall prepare training material utilizing the Army Systems Approach to Training (ASAT). Http:// www.asat.army.mil. The Contractor shall deliver the material in Microsoft Word.

Content Training materials shall include, but not be limited to, all tasks contained in the Crew-level and Maintainer-Level Technical Manuals. The training shall include, but is not limited to, the following:

• Theories of operation of system sensor(s)

• Equipment overview

• Pre-use testing/inspection

• Use and operation

• Characteristics and limitations

• Operator/unit/maintainer maintenance

• Preventive Maintenance Checks & Services (PMCS)

• Troubleshooting

• Basic diagnosis and fault finding

• Storage

• Personnel and equipment safety http://www.asat.army.mil.the/

Title Operator/Crew Training Materials

Data Item Description (DID) Number

DID-021

Description

Preparation Instructions

Format Contractor format is acceptable.

Content

Training materials shall include, but not be limited to, all tasks contained in the Crew-level and Maintainer-Level technical manuals. The training shall include, but is not limited to, the following:

• Theories of operation of system sensor(s)

• Equipment overview

• Pre-use testing/inspection

• Use and operation

• Characteristics and limitations

• Operator/unit/maintainer maintenance

• Preventive Maintenance Checks & Services (PMCS)

• Troubleshooting

• Basic diagnosis and fault finding

• Storage

• Personnel and equipment safety

Training material shall reflect the system(s) being provided under this contract and in accordance with the approved maintenance concept. The contractor shall develop a Crew-level training course and a Maintainer-Level training course.

Training shallconcept. The contractor shall develop a Crew-level training course and a Maintainer-Level training course.

Training shall provide students with the skills necessary to operate and maintain the system(s). Training shal include, but is not limited to, all tasks contained in the -10 and -23&P TMs. The contractor shall provide updates to the Training Materials for all configuration changes that occur through the contractor PQT, Government DT/OT and verification of the maintenance concept. The contractor shall also prepare and deliver a CD or DVD of the training material for use as a reach-back or refresher training tool. The contractor shall provide updates to the Training CD or DVD for all configuration changes that occur through the contractor PQT, Government DT/OT and verification of the maintenance concept.

Title Technical Manual (TM) - Operator (-10)

Data Item Description (DID) Number

DID-022

Description

Preparation Instructions The manual modifications shall be prepared at the reading grade level (i.e., 8th grade reading level) and comprehension level described in the target audience description provided by the Government after contract award.

Format The TM modifications shall be in Work Package Format and shall be prepared in accordance with MIL- STD-40051.2 and as tailored by the IPPT.

Content The -10 TM shall include, but is not limited to the following information:

• Cover (including the technical manual (TM) number, title, national stock number (NSN), equipment name and illustration, distribution statement, publish date, and revision number)

• Front matter (including front cover as described above, table of contents, and warnings and cautions)

• General information, equipment description, theory of operation, and Basic Issue Items (BII))

• Operating instructions

• Troubleshooting and preventive maintenance procedures

• Maintenance instructions for Crew- level maintenance

• System Support Package Component List (SSPCL) for Crew-level maintenance procedures

• Associated support items of equipment (ASIOE)

• Supporting information such as components of end item (COEI), expendable and durable items

• Alphabetical index

The contractor shall provided modifications to the Government-furnished Crew-level Technical Manual (-10) that adequately reflect all unique features of the system(s) provided under this contract and in accordance with the approved maintenance concept.

Title Technical Manual (TM) - Field Maintenance (-23&P)

Data Item Description (DID) Number

DID-023

Description

The contractor shall develop a Maintainer-Level Technical Manual (-23&P) that adequately reflects the system(s) provided under this contract and in accordance with the approved maintenance concept.

Preparation Instructions

The manual shall be prepared at the reading grade level (i.e., 8th grade reading level) and comprehension level described in the target audience description provided by the Government after contract award.

Format The TM shall be in Work Package Format and shall be prepared in accordance with MIL-STD-40051.2, and as tailored by the IPPT.

Content The -23&P TM shall include, but is not limited to the following information:

• Cover (including the technical manual (TM) number, title, national stock number (NSN), equipment name and illustration, distribution statement, publish date, and revision number)

• Front matter (including front cover as described above, table of contents, and warnings and cautions)

• General information, equipment description, theory of operation, and basic issue items (BII))

• Troubleshooting and preventive maintenance procedures

• Maintenance instructions for Maintainer-Level maintenance

• Repair parts and special tools list (RPSTL)

• System Support Package Component List (SSPCL) for Maintainer-Level maintenance procedures

• Associated support items of equipment (ASIOE)

• Supporting information such as a maintenance allocation chart (MAC), components of end item (COEI), expendable and durable items)

• Alphabetical index

Title Quick Reference Card (QRC)

Data Item Description (DID) Number

DID-024

Description The Quick Reference Card (QRC) shall show and explain the basic system installation and operating procedures/instructions.

Preparation Instructions The QRC shall be no more than 3 laminated pages, no larger than 5.5” x 3.5” when folded. Information can be included on both the back and front of the quick reference card. The QRC shall be prepared at the reading grade level (i.e., 8th grade reading level) and comprehension level described in the target audience description provided by the Government after contract award.

Format Contractor format is acceptable.

Content The QRC shall show and explain:

• Buttonology

• Low Battery Indicators

• Modes of Operation

• Calibration

• Fields of View

• Positioning adjustments

• Basic Troubleshooting Procedures

• Shall be lamninated

• Additional requirements will be defined by the IPT and the QRC will be tailored as required.

Title

Provisioning Parts List (PPL)

Data Item Description (DID) Number

DID-025

Description The Provisioning Parts List (PPL) provides the government with the data required to catalog each new for each new part and assign a national stock number. The PPL shall be structured at the end item, component, or assembly level as specified by the Maintenance Allocation Chart in a top-down breakdown sequence. The PPL shall contain the end item, component, or assembly equipment and all support items which can be disassembled, reassembled, or replaced and which when combined, constitute the end item, component or assembly equipment and any special tools and/or kits. The PPL shall provide all data and information required to support the Repair Parts and Special Tools List (RPSTL) portion of the Technical Manuals.

Data within the PPL shall permit spares requirements calculations so that the provisioning parts buy can be initiated upon receipt of the stock number assignments.

Preparation Instructions

Format The PPL will include the data elements identified in SOW Paragraph 3.5.16.1. MIL-STD-1552 will be used as guide for field length of each data element.

Content

• The PPL shall be suitable for submission to the Provisioning Master Record (PMR) of the Commodity Command Standards System.

• The PPL shall be structured at the end item, component, or assembly level as specified by the Maintenance Allocation Chart in a top-down breakdown sequence.

• The PPL shall contain the end item, component, or assembly equipment and all support items which can be disassembled, reassembled, or replaced and which when combined, constitute the end item, component or assembly equipment and any special tools and/or kits.

• The PPL shall provide all data and information required to support the Repair Parts and Special Tools List (RPSTL) portion of the Technical Manuals.

• For content, contractor shall refer to SOW Paragraph 3.5.16.1.

Title

Engineering Data for Provisioning (EDFP)

Data Item Description (DID) Number

DID-026

Description

PTD-EDFP is used for the identification, selection, and determination of initial requirements and cataloging of support items to be procured through the provisioning process. EDFP accompanies the Provisioning Parts List (PPL) whenever any significant maintenance item on the PPL does not have an NSN. The contractor shall provide Engineering Data for Provisioning (EDFP) for all maintenance-significant items (SMR1=’P’) on the PPL which do not have National Stock Numbers (NSNs). Engineering Data for Provisioning shall be data such as specifications, sketches or drawings with descriptions necessary to indicate the physical characteristics, location, and function of the item to permit proper cataloging.

Preparation Instructions The contractor shall provide Engineering Data for Provisioning (EDFP) for all maintenance-significant items (SMR1=’P’) on the PPL which do not have National Stock Numbers (NSNs). Engineering Data for Provisioning shall be data such as specifications, sketches or drawings with descriptions necessary to indicate the physical characteristics, location, and function of the item to permit proper cataloging.

The PTD-EDFP shall be developed in accordance with MIL-PRF-49506.

Format Contractor format is acceptable unless otherwise specified by MIL-PRF or the IPPT.

For content, contractor shall refer to SOW Paragraph 3.5.16.2.

Title Configuration Management Plan (CMP)

Data Item Description (DID) Number

DID-027

Description

The Configuration Management Plan provides a detailed plan of the Configuration Management methods and procedures that the contractor will be used to maintain the configuration of the system(s) procured under this contract. The CMP describes in detail how the contractor’s Configuration Management (CM) program is implemented for the effort; how CM is organized; how CM will be conducted; methods, procedures and controls that effect configuration identification, identification, change control, status accounting and audits of the total configuration, including hardware and software. The principle use is to provide the Army with a basis for review, evaluation and monitoring of the contractor CM program, and its proposed components.

Preparation Instructions The Contractor shall use, as guidance, DI-CMAN-80858 “Contractor’s Configuration Management Plan” and MIL- HDBK-61 “Configuration Management Guidance” in the preparation of the CMP.

Format Contractor format is acceptable.

Content The content of the CMP shall define the technical and administrative guidelines for change control, status accounting, and audits of the hardware and software configuration of the system(s). Also included shall be the implementation of the use of firmware, relative to contactor test stations. The Contractor shall submit electronic engineering change control documents for DD1692 Engineering Change Proposal, DD1695 Notice of Revision, and DD1696 Specification Change Notice.

The plan shall address, but not be limited to:

• Contractor Configuration Management Program

• System Configuration Identification

• System Configuration Control

• System Engineering Change Order (ECO – internal to contractor) and Engineering Change Process (ECP)

Preparation and Processing

• System Configuration Status Accounting

Title Performance Specifications

Data Item Description (DID) Number

DID-028

Description

Performance specifications for the system and spared items/replacement parts contain all information necessary to define the operation/performance of the system and each of the individual spared items/replacement parts. These specifications would be used in conjunction with the contractually required spare parts ICDs to support competitive procurement of the system(s) and spared items during the life cycle of the proposed system(s).

Preparation Instructions Contractor’s shall use the Product Descriptions and Performance Specifications included in the RFP as the template for the Performance Specifications.

Format Contractor format is acceptable.

Content

• Spared Item Product Performance Specifications. Following completion of Contractor PQT and Government DT/OT, the contractor shall submit performance specifications for the systems and items defined in paragraphs 3.6.2.1.

These performance specifications for the major spared items/replacement parts shall contain all information necessary to define the operation/performance of each of the individual spared items/replacement parts .

Title Engineering Drawings

Data Item Description (DID) Number

DID-029

Description Engineering Drawings include Interface Control Drawings (ICDs) which provide a record of all the interface information and dimensions necessary to assure interchangeability for spare parts and assemblies that assure 100% form, fit, and function interchangeability. The ICDs shall contain sufficient information to permit successful completion of the PCA/FCA.

Preparation Instructions

Format

Dimensioning and tolerances shall be IAW ASME Y14.5M-1994 or equivalent.

Electrical characteristics and performance parameters of parts, modules, assemblies, and units shall be expressed as numerical values with tolerances specifying upper and lower (or maximum and minimum) limits.

Drawings and all drawing associated files are to be in CAD format, PRO/Engineer preferred.

Specifications shall be compatible with Windows Operating Systems, and Microsoft Office 2013 products (i.e., Microsoft Word, Excel, etc.)

Content

The ICDs shall include:

a. Configuration and interface dimensional data applicable to the envelope, mounting and interconnection of the related items;

b. Complete interface engineering requirements (mechanical, electrical, electronic, optical, human, etc.)

which affect the physical or functional characteristics of the cofunctioning items;

c. Any other characteristics, including material and finishes which cannot be changed without affecting system interfaces or interfering down to the spareable level.

Title

Physical Configuration Audit/Functional Configuration Audit (PCA/FCA) Plan

Data Item Description (DID) Number

DID-030

Description The PCA/FCA Plan shall describe how the physical and functional configuration audit will be conducted for the system(s), down to the spareable item level for the design that successfully completes contractor PQT and Government DT/OT, including any special tools, and fixtures required to support/sustain the system(s). The PCA/FCA plan shall also propose a location and schedule for the audit, and identify the individuals who will conduct the audit. The PCA/FCA plan shall also identify the interface control and product items to be audited.

Preparation Instructions

Format Contractor format is acceptable.

Content

• The PCA/FCA shall include all hardware and software developed for this contract and any hardware or software that is to be modified as a result of this contract.

• The PCA/FCA plan shall be approved by the IPPT prior to the commencement of the PCA/FCA.

• The PCA/FCA shall be conducted on all interface, mating and interconnection dimensions, and shall include a visual inspection of all subcomponents, as a minimum.

The plan is to include information on:

• The purpose and objective of the audit in terms of the contract requirements

• Identify the physical hardware configuration items to be audited:

o Nomenclature o Specification / part number o Serial number (if applicable)

• Identify the documentation to be audited:

o Engineering drawings o Applicable specifications o Engineering Change Proposals o Test plans and procedures o Operating and support manuals o Configuration documentation release procedures o Request for deviations/ waivers

• Scope of audit which includes a summary of the hardware requirements against which the audit will be conducted as specified in work statements, specifications and approved plans.

• Location and schedule of the audit

• Team Composition o Identify the Army Representatives and their function in the audit o Identify Contractor Representatives and their function in the audit

Title

Physical Configuration Audit/Functional Configuration Audit (PCA/FCA) Report

Data Item Description (DID) Number

DID-031

Description Provides text and marked-up technical documents which identify discrepancies between the material and the requirements agreed to in the contract.

Preparation Instructions

Format Contractor format is acceptable.

Content The PCA/FCA Report will include information on:

• Purpose of the audit.

• Audit minutes to include date and location of audit, identify member of the audit team.

• List of action items and the suspense dates agreed to by team members.

• Applicable audit certifications documenting key audit review activities.

o Specific items and documents that were audited.

o Summary of the discrepancies / deficiencies for each item in audited.

o Definitive statements about acceptability or non-acceptability.

o Final status of the contractor's effort in the are being certified.

Title Engineering and Configuration Control Documentation

Data Item Description (DID) Number

DID-032

Description Engineering and Configuration Control Documentation includes: Request for Deviation (RFD), Request for Waiver (RFW), Engineering Change Proposal (ECP), and Value Engineering Change Proposal (VECP). The contractor shall submit Tolerance Analysis Reports as backup data for all engineering configuration control document submittals.

A RFD provides the documentation in which a deviation for a requirement is described. It includes, but is not limited to, the following: deviation description, need, corrective action taken, and effectivity. In addition, it includes the deviation’s effect on cost/price, delivery schedule, and logistics.

A RFW provides the documentation in which a waiver for a requirement is described. It includes, but is not limited to, the following: waiver description, need, corrective action taken, and effectivity. In addition, it includes the waiver’s effect on cost/price, delivery schedule, and logistics.

An ECP provides the documentation in which an engineering change is described. It includes change impacts to systems, configuration items, and other associated configuration documentation , to include training and technical manuals, and provisioning data, affected by the proposed change. In addition, it typically describes how the proposed change will be implemented along with providing estimated impacts to schedule and cost when applicable.

A Value Engineering Change Proposal (VECP) is a contractual mechanism that gives a financial incentive to get contractors and subcontractors to reduce the cost of systems, supplies, and services for contracts in-progress. To qualify as VECP, a proposal must, at a minimum, require a change to a contract to implement, and save money. It must lower overall the overall cost; without degrading performance, reliability, maintenance, or safety. No obligation to accept a VECP is present and the risk for the contractor's development costs resides with the contractor.

Preparation Instructions

Format The RFD/RFW (DD Form 1694) shall be used to formally submit a requested deviation.

The ECP (DD Form 1692) shall be used to formally submit a requested…