Attachment_0007_SOW_for_MERWS_TM_-13&P_20180523.docx

STATEMENT OF WORK (SOW)

FOR

DEVELOPMENT AND PRODUCTION

OF EQUIPMENT PUBLICATIONS

FOR

MODULAR EXTENDABLE RIGID WALL SHELTER (MERWS)

TECHNICAL MANUAL (TM)

TM 10-5411-XXX-13&P

1. SCOPE. The Contractor shall develop and produce an Operator and Field Maintenance Manual, including Repair Parts and Special Tools Lists (RPSTL), for the Modular Extendable Rigid Wall Shelter (MERWS). The Contractor shall also submit a Validation Plan and a Validation Report for the Operator and Field Maintenance Manual, including Repair Parts and Special Tools Lists (RPSTL). The stated documents shall be developed and produced in accordance with this Statement of Work (SOW), applicable including Repair Parts and Special Tools List (RPSTL) military standards (MIL-STDs) and regulations, and the attached Technical Manual Content Requirements Matrix (Appendix 1). The Contractor shall reference other Army Technical Manuals as appropriate throughout the technical manual submissions in accordance with MIL-STD guidance.

CDRL

Para.

C004

MIL-STD-40051-2C,

Including all changes Operator and Field Maintenance Manual including Repair Parts and Special Tools List (RPSTL) for the Modular Extendable Rigid Wall Shelter (MERWS) 4.1

C005, C006

DI-CMAN-80792A

DI-MISC-80711A

2. APPLICABLE DOCUMENTS (TM).

Document ID

Title

http://www.apd.army.mil/ProductMap.asp Click DA Pamphlets and then, click 25 Information Management.

Click Army Regulations and then, click 25 Information Management.

Click Army Regulations and then, click 25 Information Management.

DI-CMAN-80792A

Validation Report http://quicksearch.dla.mil/

https://www.logsa.army.mil/mil40051/menu.cfm

http://quicksearch.dla.mil/

http://www.dtic.mil/whs/directives/corres/pdf/523024p.pdf

http://www.acq.osd.mil/dpap/dars/dfars/index.htm

MIL-HDBK-1222E

(For Guidance Only) Department of Defense Handbook, Guide to the General Style and Format of U.S. Army Work Package Technical Manuals, 30 November 2012.

http://www.assistdocs.com/search/search_basic.cfm

MIL-HDBK-2361C

(For Guidance Only) Army Digital Publications Development Implementation Guide, 15 January 2012.

MIL-STD-2361C,

Notice 1 Department of Defense Interface Standard Digital Publications Development, 09 July 2010.

The following items will provided by AMSTA-LCS-E (TACOM ILSC) at the Logistics Guidance Conference/Start of Work Meeting:

XML DTD, Revision 5.0 or later https://www.logsa.army.mil/mil40051/menu.cfm

Extensible Markup Language (XML) stylesheet https://www.logsa.army.mil/mil40051/menu.cfm

3. PUBLICATION REQUIREMENTS. The Contractor shall produce an Operator and Field Maintenance Manual, including Repair Parts and Special Tools List (RPSTL) and the appropriate Technical Manual Content Requirements Matrix (Appendix 1) in accordance with this SOW. Development of the TM will be supported by a Contractor-managed Validation efforts. The Contractor shall develop Validation Plans and Validation Reports for the Operation and Field Maintenance Manual, including Repair Parts and Special Tools Lists in accordance with this SOW and CDRLs.

3.1. Technical Manual. The Contractor shall produce an Initial, Second, and Final Reproducible Copy (FRC) Submission of Operator and Field Maintenance Manual, including Repair Parts and Special Tools Lists (RPSTL) in accordance with the MIL-STD-40051-2C Technical Manual Content Requirements Matrix (Appendix 1). Content shall include, as required, and as applicable, all procedures necessary to operate and maintain the MERWS, to include PMCS, Troubleshooting, and Field maintenance procedures. All submissions must conform to format and content requirements outlined in the applicable military standards and specifications detailed in paragraph 2 and requirements detailed in this SOW, and must be fully illustrated, referenced, and have a working table of contents. In particular, troubleshooting must conform to MIL-STD-40051-2C, D.5.5.8.4.6.2 Method B – Text.

3.1.1. Repair Parts and Special Tools List (RPSTL). The TM content shall include, as required, RPSTL information and artwork to support repair and replacement of parts. The RPSTL text, illustrations and indexes shall be in accordance with this SOW, and shall conform to MIL-STD-40051-2C. The RPSTL parts list shall be updated to reflect part number changes as provided in any Government approved ECP(s). The RPSTL figure title, the functional group title and the applicable MAC title shall be the same. The RPSTL assemblies and subassemblies shall be in the same sequential order as the Government-approved Two-Level Maintenance (TLM). (See paragraphs 3.86 and G.5.3.3.4 in MIL-STD-40051-2C, for more details on TLM concepts and formatting). The Contractor shall produce encapsulated postscript (EPS)-formatted line art for RPSTL illustrations IAW paragraph 7.6. The RPSTL text, illustrations, and indexes shall be in accordance with this SOW and conform, as applicable, to MIL-STD-40051-2C, format requirements. Digital photographs are not acceptable for RPSTL illustrations. All TM submissions must conform to format and content requirements outlined in the applicable military standards, specifications detailed in paragraph 2, requirements detailed in this SOW, and must be fully illustrated, referenced, and have a working table of contents.

3.2. Content Requirments Matrix Compliance. The Technical Manual Content Requirements Matrix (Appendix 1) shall be used to organize and develop technical manual content.

a) All items marked “R” in the matrix are required to support the equipment and shall be included in the order established in the matrix.

b) All shaded items shall be included as required to support the equipment. If shaded items are included, they shall be provided in the order established in the matrix.

c) All items marked “P” in the attached matrix are prohibited and shall not be included in the manual.

Note: Submissions with out-of-sequence or prohibited content items will be rejected.

3.3. Maintenance Allocation Chart (MAC). All maintenance procedures identified in the approved MAC shall have corresponding maintenance, Troubleshooting and Preventive Maintenance Checks and Services (PMCS) procedures within the manual. The MAC introduction and MAC tables shall be developed to conform to format and content requirements as detailed in MIL-STD-40051-2C. All item names of MAC functional groups shall be official nomenclature in accordance with the RPSTL nomenclature. The MAC shall also be updated to include changed or additional components and their corresponding maintenance functions as applicable; however, any and all changes to the MAC must be specifically approved and directed for inclusion by the Government IAW AR 25-30.

3.4. Illustrations. All technical manual submissions shall be fully illustrated IAW this SOW and MIL-STD 40051-2C. Digital photography, computer graphics, and line art are acceptable illustration media to support procedural and descriptive text. Digital photography will not be accepted for RPSTL illustrations.

3.4.1. Photographic Support. The Contractor shall use photographs as required by the Government to ensure text is sufficiently supported with accurate and clear illustration. In producing the TM as outlined in this SOW, the Contractor shall ensure that personnel in photographs, when visible, will be attired in proper and current U.S. Army work/utility uniform. All personnel, when photographed, will be wearing all safety equipment necessary to perform the procedure being illustrated, and will be photographed complying with all safety requirements as specified in the procedural text; to comply with this requirement, photographed personnel may not be depicted wearing watches, rings, or any other visible jewelry.

3.4.2. Graphics Worksheet. The Contractor shall deliver a graphics worksheet in electronic format (MS-Word or equivalent format) with each submission. This worksheet shall sequentially list all graphics used in the technical manual and, at a minimum, will list in tabular format, the following information: WP identification number (see 4.7.9.1. in MIL-STD-40051-2C), WP sequence number (see 4.7.9.2. in MIL-STD-40051-2C), Figure Number, Figure Title, Unique Illustration Number (see paragraph 7.6 in this SOW), Width in inches (reprowid), Height in inches (reprodep).

4. DELIVERY REQUIREMENTS.

4.1. Technical Manual Submissions.

4.1.1. Initial Submission TM. The Initial Submission of the Operator and Field Maintenance Manual, including Repair Parts and Special Tools List (RPSTL) shall consist of: (1) Two hard copy TMs for distribution, (2) One compiled digital PDF file, (3) the XML source file with all of the graphics embedded, (4) All source graphics files developed and delivered separately (individually) in 300 DPI .EPS or .TIFF format, and (5) a Graphics worksheet (MS Word or equivalent) in accordance with the requirements in Section 7 of this SOW.

The Initial Submission of the Operator and Field Maintenance Manual, including Repair Parts and Special Tools List (RPSTL) will not be accepted unless it is accompanied by the corresponding Validation Plan.

4.1.2. Second Submission TM. The Second Submission of the Operator and Field Maintenance Manual, including Repair Parts and Special Tools List (RPSTL) shall include resolution of all comments and recommendations made as a result of the Contractor Validation, Government review, evaluation of Product Support Assessments, and any changes made as a result of the provisioning process. The Second Submission will consist of: (1) Two hard copy TMs for distribution, (2) One compiled digital PDF file, (3) the XML source file with all of the graphics embedded, (4) All source graphics files developed and delivered separately (individually) in 300 DPI .EPS or .TIFF format, and (5) a Graphics worksheet (MS Word or equivalent) as determined in the SOW. This document will support the Government-managed TM Verification Conference.

4.1.3. Final Reproducible Copy (FRC). The FRC Submission of the Operator and Field Maintenance Manual, including Repair Parts and Special Tools List (RPSTL) shall include final resolution of all comments and recommendations made as a result of the Verification Conference and the master markup documenting that event. The FRC deliverables will consist of: (1) Two hard copy TMs for distribution, (2) One compiled digital PDF file, (3) The XML source file with graphics embedded, (4) All source graphics files provided separately (individually) in 300 DPI .EPS or .TIFF format, and (5) a Graphics worksheet (MS Word or equivalent) in accordance with the requirements in Section 7 of this SOW.

4.1.4. Letter of Transmittal. Each TM submission shall be accompanied by a Letter of Transmittal, which shall include:

a) Identifying the type of submission and a summary of what is included.

b) An explanation for any changes requested by the Government that were NOT made by Contractor.

c) Other major changes that have been applied as well as those NOT originally identified that were applied, for example, and not limited to reorganizing WPs, etc.

d) Unresolved content issues MAC, RPSTL and/or work package issues.

e) Unresolved page specific stylesheet issues.

f) Give a detail explanation for all “placeholders” if there are any, when they are expected to be resolved.

4.2. Validation Submissions.

4.2.1. Validation Plan. The Contractor will develop and submit a Validation Plan for Government review and approval for the Operator Manual and Field Maintenance Manual with Repair Parts and Special Tools List (RPSTL) IAW CDRL C005. The Validation Plan shall reflect compatibility with the overall maintenance and support plan, outline the Contractor’s recommended validation procedure, and indicate the scope of the validation effort. All procedural tasks included in the TM must be validated hands-on; that is, actually performed as written. Intention to provide validation by analysis or otherwise simulate or desktop validate any procedures will be sufficient cause to reject the Validation Plan submission. Specific questions about the validation plan may be addressed at the Logistics Guidance conference. Government representative(s) are to participate as observers during the TM validation. Contractor must notify the Government 30 calendar days in advance in order to schedule attendance. The plan shall include, at a minimum:

a) Location, dates and time of validation.

b) List of subject matter experts attending validation.

c) A Fault Insertion List (FIL). The FIL will identify the following:

· Method of insertion.

· Symptom.

· Malfunction.

· Conclusion/Faulty Component or Assembly.

All identified faults must be resolved through hands on Validation using the Troubleshooting Procedures within the TM.

d) List of tasks to be performed. A schedule of dates and approximate times of each task validation must be provided.

e) Detailed description of how tasks will be validated. For example, if performance of a portion of one task provides the setup for performance of another task, this must be indicated in the Validation Plan.

f) List of all tools and equipment to be used for each task.

4.2.2. Validation Report. The Validation Report shall identify the Contractor as the validating entity, dates of the Validation effort, a summary of all information validated, validation methods used, and a summary of all changes identified as a result of Contractor validation, and any additional information necessary to satisfy the data requirements listed in Block 10 of DI-CMAN-80792A; this includes signed certification by the Contractor’s responsible officer(s) that the TM was validated IAW with the approved Validation Plans.

5. ACCEPTANCE/REJECTION OF DELIVERABLES.

5.1. Acceptance/Rejection of TM Submissions. The Government shall evaluate and determine acceptance of the Initial, Second, Third, and FRC submissions, in accordance with CDRLs, as applicable. If any submission is found to be in error, insufficient, or otherwise does not meet the requirements in this SOW and the associated CDRLs, the submission shall be rejected and considered a draft until the Contractor corrects the errors. If the Government rejects a submission, it will remain in rejected status until the Government approves that submission. No scheduled submission requirement shall be considered to have been met until the Government has accepted the submission. The corrected TM submission shall be resubmitted in accordance with the requirements in C004.

5.1.1. Letter of Acceptance/Rejection of Technical Manual Submissions. The Government will provide a written notification of acceptance or rejection to the Contractor identifying the discrepancies.

5.2. Acceptance/Rejection of Validation Submissions.

5.2.1. Acceptance/Rejection of the TM Validation Plans. The Validation Plans will be reviewed by the Government for acceptability and suitability to the equipment under validation. The Validation Plan will be rejected and considered a draft if the Government deems the plan insufficient or inadequate to provide a thorough and accurate validation of the procedures in the supported TMs. The corrected Validation Plan shall be resubmitted in accordance with the requirements in C005.

5.2.2. Acceptance/Rejection of the Validation Reports. The Validation Reports will be reviewed by the attending Government observer for accuracy. The Validation Report will be rejected and considered a draft if the reported data elements are insufficient or incomplete, if the attending Government observer does not concur that the report is accurate, or if the Validation is not certified by the Contractor’s responsible officer(s) in the Validation Reports. The corrected Validation Report shall be resubmitted in accordance with the requirements in C006.

5.2.3. Letter of Acceptance/Rejection of the Validation Plans and Validation Reports. The Government will provide written notification of acceptance or rejection to the Contractor through the Government Contracting Office.

6. TM-RELATED MEETINGS/CONFERENCES.

6.1. Logistics Guidance Conference/Start of Work Meeting. This meeting shall take place at a mutually agreed-upon Government location and date to clarify all matters relating to development, preparation, and submission of data deliverables. The Contractor shall be prepared to identify all questions and discuss all TM requirements. Follow-on meetings between the Contractor and Government representatives may be held at the request of either party to discuss specific document requirements as they relate to the development of equipment publications for this contract. The Contractor shall be prepared to discuss all development and source file requirements at this time. The Contractor shall also provide a sample graphics file in electronic format to the Program Manager via e-mail no later than 2 calendar days prior to the Logistics Guidance Conference for review in order to ensure compliance with MIL-STD-40051-2C. The sample graphics file shall include layered callouts, Additional guidance will be available through scheduled and ad hoc In-Process Review meetings.

6.2. In-Process Reviews (IPR). IPR teleconferences will be held if necessary, as agreed to by both the Government and the Contractor at the Logistics Guidance Conference/Start of Work Meeting. During preparation of equipment publications, these IPRs will be used to clarify requirements and provide guidance to the Contractor, ensuring the publications are written to conform to this SOW, the appropriate MIL-STD, and the Technical Manual Content Requirements Matrix (Appendix 1). Either the Contractor or the Government may request additional IPRs by teleconference or in person as required for development and delivery of the TMs.

6.3. Validation.

6.3.1. Scope of Validation. Validation is the responsibility of the Contractor. Operating and maintenance procedures including all PMCS and troubleshooting will be validated against the system equipment through actual demonstration. Theory and principles of operation, system/component descriptions, Source, Maintenance, and Recoverability (SMR) codes, schematics, MAC, and other RPSTL information shall be validated against the current engineering source data.

6.3.2. Validation Schedule. The Contractor shall conduct a validation of TM (10-5411-XXX-13&P) according to the Contractor-proposed, Government-approved Validation Plan. The validation shall be held at the Contractor’s facilities unless otherwise agreed to by the Government.

6.3.3. Validation Criteria. The TM shall not be considered validated until the following conditions have been fulfilled:

a) TM content reflects configuration of the system/equipment and includes all engineering changes to date.

b) Procedural instructions are readily understandable by the intended user and adequate to perform all operations and maintenance functions.

c) Adequacy of data is checked to ensure that it supports the approved maintenance and support plans.

d) The validation has been conducted according to the Contractor-proposed, Government-approved Validation Plan. No validation efforts or events will be considered as having been conducted if the Validation Plan has not been approved and accepted by the Government technical publications representative(s).

e) The validation has been observed by the Government; specifically, representatives from technical publications and an ILSC equipment specialist at a minimum.

f) All identified faults in the Fault Insertion List (FIL) must be resolved through hands on Validation using the Troubleshooting Procedures within the TM.

g) The TM is not considered validated until Government accepts the Validation Report (paragraph 4.2.2).

6.3.4. Contractor Responsibilities for Validation. Validation is the responsibility of the Contractor. The Contractor will coordinate scheduling to ensure attendance by the Government technical writer/editor. The Contractor shall provide supporting materials to facilitate meaningful Government observation, including procedural text. The Contractor’s responsible officer(s) shall certify the TM has been validated IAW paragraph. 6.3.

6.3.5. Government Responsibilities for Validation. The Government technical publications writer/editor shall observe the Contractor Validation. The Government observer shall not direct, conduct, execute or otherwise place themselves in a position other than that of observer during the course of the Validation; the Government observer may advise the Contractor on the course of the Validation if requested by the Contractor. The Government observer shall not provide any manner of certification for the Validation, either by verbal or written instrument, other than acceptance of the Validation Reports following the conclusion of the Validation event.

6.4. Verification.

6.4.1. Scope of Verification. Verification is the responsibility of the Government, specifically the technical publication element of the proponent command. Operating and maintenance procedures including all PMCS and troubleshooting will be verified IAW AR 25-30 and AMC PAM 25-31.

6.4.2. Verification Plan. The Government will draft and submit for review a verification plan IAW AMC PAM 25-31. The Contractor will review the plan for accuracy, applicability, and availability of personnel and support, and will provide any commentary to the Government.

6.5. Government Responsibilities for Verification. Verification is the responsibility of the Government. The Government shall coordinate the necessary personnel, facilities, equipment, tools, test equipment, supplies, and pertinent documents required for Verification. The Verification Conference will be scheduled in accordance with Government technical publications writer/editor’s Verification Plan and schedule. Verification will take place at a Government or Contractor facility unless otherwise specified. IAW AR 25-30, the technical publication element of the proponent command is responsible for providing guidance to the Contractor and for review, verification, and acceptance of deliverable products. Guidance and direction from any source other than the responsible AMSTA-LCS-E representative cannot be accepted by the Contractor as legitimate and contractually binding guidance for the content or format of either subject TMs.

6.6. Contractor Responsibilities for Verification. The Contractor shall support the verification with the Contractor personnel identified in the Government Verification plans. The Contractor shall take corrective action resulting from the Verification and incorporate it into the TMs FRC submission.

7. OTHER REQUIREMENTS.

7.1. TM Over-pack Requirements. The Contractor shall over-pack one copy of the Government furnished Department of the Army-authenticated Operator Manual with each end item of contracted hardware delivered to the Government as prescribed on the applicable DD Form 1423.

7.2. TM Deliverable Submission Format. The Government will not accept e-mail submissions. TM submittals will be delivered IAW paragraph 4 of this SOW.

7.3. Validation Deliverable Submission Format. The Government will not accept e-mail submissions. The Contractor shall submit the Validation Plan and Report submissions as a hardcopy document and electronic file (PDF) on a compact disk (CD) in accordance with paragraph 4.2 of this SOW.

7.4. Source Files. The Contractor shall submit source files of all text and graphics. Digital graphics shall be produced so that black and white print production will not result in any loss of resolution. The digitized data shall reflect the content of the text and graphics contained in the FRC Submission delivered to the Government.

7.4.1. XML Source File. The Contractor will submit a valid flattened XML source file in accordance with MIL-HDBK-2361C, with all graphics files, and graphics worksheet included with each submission. The submitted XML file will parse and compose using Arbortext Editor version 6.0 (or later) and the AMC LOGSA DTD.

7.4.2. XML Illustration and Entity References. The flattened XML source file cannot reference any files or illustrations which are not part of the submitted FRC.

7.5. Portable Document Format (PDF). The Contractor shall submit editable PDF files (Adobe Acrobat or equivalent) of all Submissions (Initial, Second, Third, and FRC) in accordance with MIL-STD-40051-2C. The PDF submissions shall be a single composed file. The final PDF file shall reflect all content of the text and graphics contained in the FRC Submission accepted by the Government. All PDF submissions shall have all fonts embedded.

7.6. Graphics, Illustrations, Symbols, Icons, and Assignment of Unique Illustration Numbers.

7.6.1. Format and Quality. Graphics are normal images used in figures in technical manuals. Illustrations are graphics used in a TM which appear “in-line” and do not have a figure number or title. They are typically small equations, or images imbedded in paragraphs or tables. Symbols are custom made graphics for symbols not found in one of the standard ISO symbol sets. Icons are used in Warnings and Cautions to illustrate or depict hazards. File format for all graphics, illustrations, symbols and Icons shall be Contractor proposed and Government approved at the guidance conference IAW paragraph 7.4 using a Contractor-provided sample graphics file. File format for line art must be in EPS format. All graphics file formats must support layers, for example, all callouts, text, legends or other items in a graphics file must be on a separate layer from the base image. Image quality (resolution) of all graphics, illustrations, symbols, and icons will be at least 300 DPI. Font size used in graphics and illustrations for callouts will be all caps, sans serif and 10 PT size. Font size used in graphics and illustrations for legends will be sans serif, 10 PT size and the first letter of the first word shall be uppercase. An exception is equations which may require use of specific font types or symbol sets.

7.6.2. Graphic Size Limitations. To account for margins and figure titles, maximum graphic image size used for compatibility with XML graphic tags for A4 style pages will be 8”H x 7”W. Maximum image size for foldout style pages will be 8”H x N”W with N” equaling the overall final width of the foldout page minus mandatory margin and apron space (not to exceed 45 inches in width). Margin white pace surrounding the graphic can be no greater than ¼ inch.

7.6.3. Unique Illustration Numbering. All graphics will be assigned a unique illustration number IAW MIL-STD-40051-2C, paragraph 4.8.27.4.6; this number will appear in the lower right corner of the graphic. The font of this number will be of a size and style to readily identify it as not being part of the other text in the graphic and small enough to be unobtrusive but large enough to be legible. For tracking purposes, symbols and illustrations will be assigned an illustration number for file naming purposes, but because of their size and use, this number will not be included as part of the image itself. Graphics, illustrations, and symbols will be assigned unique illustration numbers based on the following example:

G060XXX00001.tif

· 1st Digit: G=Graphic I=Illustration S=Symbol

· 2nd and 3nd Digit: Natick Proponent Writing Group: 06= General Publication

· 4th through 7th digits: Four-digit TM sequence number: 0XXX

· 8th through 12th digit: Graphic sequence number: 00001

7.6.4. Proponent Writing Group. Proponent writing group for graphics and illustrations on this contract will be 06.

7.6.5. Graphics Worksheet. The Contractor will provide a graphics worksheet (electronic or paper format) with each TM submission IAW with paragraph 7.6.5 of this SOW.

7.6.6. Icons. Standard warning and hazmat icons will NOT be assigned graphic control numbers. They should be a consistent size throughout the manual. For continuity, a reprowid and reprodep of 0.5 x 0.5 inches is recommended. The Government will provide electronic copies of commonly used hazard icons as GFI at the Logistics Guidance Conference.

7.7. Distribution Statement. The Government will provide the correct Distribution Statement language at the Logistics Guidance Conference.

END OF REQUIREMENTS FOR DEVELOPMENT OF THE TECHNICAL MANUAL (TM)

APPENDIX 1

MIL-STD-40051-2C,

TABLE A-II. Content Requirements Matrix for TM 10-5411-XXX-13&P Modular Extendable Rigid Wall Shelter (MERWS)

13&P

MILSTD40051-2C

Reference Element Name

(MC) Promulgation letter

Warning summary

Change transmittal page

CHAPTER 1.

GENERAL INFORMATION, Equipment DESCRIPTION, AND THEORY OF OPERATION

Hand Receipt (HR) manuals

Ozone Depleting Substances (ODS)

Warranty information

Safety, care, and handling

Nuclear hardness

Calibration

Item unique identification (IUID)

Supporting information for repair parts, special tools, TMDE, and support equipment

Copyright credit line

CHAPTER X.

OPERATOR INSTRUCTIONS

Security measures for electronic data

Siting requirements

Shelter requirements

Assembly and preparation for use

Initial adjustments, before use and selftest

Operating auxiliary equipment

Preparation for movement

Decals and instruction plates

Security measures for electronic data

Fording and swimming

Interim Chemical, Biological, Radiological, Nuclear and Explosives (CBRNE) decontamination procedures

Jamming and Electronic Countermeasures (ECM) procedures

Degraded operation procedures

Decals and instruction plates

Emergency WORK PACKAGE

STOWAGE AND DECAL/DATA PLATE GUIDE WORK PACKAGE

ONVEHICLE EQUIPMENT LOADING PLAN WORK PACKAGE

CHAPTER X.

TROUBLESHOOTING

MASTER INDEX

APPENDIX D

D.5.4.4 <tim> <masterindexcategory>

TROUBLESHOOTING INDEX WORK PACKAGE

CHAPTER X.

TROUBLESHOOTING PROCEDURES

NOTE

The notation (*) indicates that at least one of the these content items shall be included

D.5.4.2 <tim> <troublecategory>

INTRODUCTION WORK PACKAGE

TROUBLESHOOTING INDEX WORK PACKAGE

*OPERATIONAL CHECKOUT WORK PACKAGES

*TROUBLESHOOTING WORK PACKAGES

*COMBINED OPERATIONAL CHECKOUT AND TROUBLESHOOTING WORK PACKAGES

CHAPTER X.

PMCS

MAINTENANCE INSTRUCTIONS

NOTE

PMCS may be in its own chapter or may be combned with other maintenance work packages in a maintenance chapter but not both places.

APPENDIX E

E.5.2.1 <mim> <pmcscategory>

PMCS, INCLUDING LUBRICATION

INSTRUCTIONS, WORK PACKAGE

CHAPTER X.

MAINTENANCE INSTRUCTIONS

NOTE

PMCS is required as a minimum in one maintenance chapter. PMCS may be in its own chapter or may be combined with other maintenance work packages in a maintenance chapter but not both places.

E.5.2.2 E.5.2.3 <mim> <maintenancepmcscategory> <maintenancecategory>

SERVICE UPON RECEIPT WORK PACKAGE (maintainer level only)

Service upon receipt tasks

Siting

Shelter requirements

Service upon receipt of materiel

Installation instructions

Preliminary servicing of equipment

Preliminary checks and adjustment of equipment

Preliminary calibration of equipment

Circuit alignment

Ammunition markings

Classification of defects

Ammunition handling

Procedures to activate ammunition

Additional maintenance task

Follow-on maintenance

EQUIPMENT/USER FITTING INSTRUCTIONS WORK PACKAGE

PMCS INTRODUCTION WORK PACKAGE

PMCS WORK PACKAGE

Inspect

Test

Service

Adjust

Align

Calibrate

Remove

Install

Replace

Repair

Paint

Overhaul

Rebuild

Lubricate

Mark

Pack

Unpack

Preserve

Prepare for use

Assemble

Disassemble

Clean

Nondestructive inspection

Radio interference suppression

Place in service

Towing

Jacking

Parking

Mooring

Covering

Hoisting

Sling loading

External power

Arm

Load

Unload

Install peripheral device

Uninstall peripheral device

Upgrade/patch software

Configure software

Debug software

Additional maintenance task

Follow-on maintenance

GENERAL MAINTENANCE WORK PACKAGE

LUBRICATION INSTRUCTIONS WORK PACKAGE

ILLUSTRATED LIST OF MANUFACTURED ITEMS WORK PACKAGE (maintainer level and above)

E.5.3.10

TORQUE LIMITS WORK PACKAGE (MAINTAINER level and above)

WIRING DIAGRAMS WORK PACKAGE (MAINTAINER level and above)

CHAPTER X.

AUXILIARY EQUIPMENT

MAINTENANCE INSTRUCTIONS

APPENDIX E

E.5.2.6 <mim> <auxiliarycategory>

AUXILIARY EQUIPMENT MAINTENANCE WORK PACKAGE

ILLUSTRATED LIST OF MANUFACTURED ITEMS WORK PACKAGE (maintainer level and above)

E.5.3.10

TORQUE LIMITS WORK PACKAGE (maintainer level and above)

WIRING DIAGRAMS WORK PACKAGE (maintainer level and above)

CHAPTER X.

AMMUNITION

MAINTENANCE INSTRUCTIONS

APPENDIX E

E.5.2.7 <mim> <ammunitioncategory>

AMMUNITION MAINTENANCE WORK PACKAGE

AMMUNITION MARKING INFORMATION WORK PACKAGE

FOREIGN AMMUNITION (NATO) WORK PACKAGE

CHAPTER X.

DESTRUCTION OF EQUIPMENT TO PREVENT ENEMY USE

NOTE

If a separate destruction of material manual is not developed for this equipment, then the destruction chapter must be included.

Essential components and spare parts

Parts list

SOFTWARE INFORMATION

<softwarecategory>

software effectivity work package

differences between software versions work package

features and capaiblities work package

R

key commands work package

processes and commands work package

user interface work package

Software OPERATING conventions work package

Additional software operation wp

recovery from errors, malfunctions, and emergencies work package

CHAPTER X.

RPSTL

(-10, -13, -14) (-13&P, -14&p)

P R

Repair parts for special tools work package

Kit parts list work package

bulk Item Work Package

Special tools list work package

Reference designator index work package

CHAPTER X.

SUPPORTING INFORMATION

NOTE

Applicable supporting information work packages shall be arranged in the order in which they are presented here and numbered accordingly.

ADDITIONAL AUTHORIZATION LIST (AAL) WORK PACKAGE

SUPPORT ITEMS WORK PACKAGE

ADDITIONAL SUPPORTING WORK PACKAGES

Glossary

Alphabetical index

Foldout pages

R – Required Shaded – Optional or as required P - Prohibited

As of 23 May 2018 1