MIL-DTL-81919C(AS)
3.1.10 Task development. The task development phase of the technical manual preparation is
critical because it will establish the arrangement and organization of the technical information and,
together with the task analysis, will establish the depth and scope of the coverage. Based on the
requirements identified by the task analysis, all tasks for end item operation (if required) and the
testing, troubleshooting, and maintenance coverage requirements at the appropriate maintenance
level(s) can be established. Once the basic operation and maintenance tasks are established, the
depth and scope of the supporting data can be identified, e.g., description, principles of operation,
local assembly and manufacturing procedures, wiring data, etc. The final output of the task
development phase is the technical manual outline (refer to NAVAIR 00-25-700 and MIL-DTL-
81927).
3.2 Task analysis. Normally the complexity of a item is considered to be its design
sophistication. However, in terms of technical manual coverage requirements, complexity is
measured during task analysis in relationship to impact on the technical manual's coverage
requirements, e.g., testing (operational checkout), troubleshooting (fault isolation), testing and
troubleshooting access requirements, maintenance, SE required and supporting data requirements.
The logistics support requirements are frequently driven by the cost of the required SE and
technical documentation. Under most conditions, the depth and scope of the total coverage
requirements will be primarily determined by the testing and troubleshooting requirements. See
NAVAIR 00-25-700.
3.2.1 Review of existing related technical manuals. Upon completion of the task analysis, a
review of existing related documentation, including commercial manuals, shall be conducted to
determine if the minimum coverage requirements (1) can be met by reference to a NAVAIR
manual, (2) included in the manual(s) being developed, or (3) added to the NAVAIR technical
manual inventory. Documents that are considered part of the related hardware (such as Test
Program Instructions) shall contain all or part of the Testing and troubleshooting instructions shall
be referenced. If all or part of the minimum requirements as determined by the task analysis are
not included in the referenced material or other related documentation, the contractor shall notify
the requiring activity. The requiring activity will determine if the missing data will be added to the
referenced material or the manual under preparation.
3.3 Separate Maintenance Instructions manual. A separate Maintenance Instructions manual
includes all related functional elements, except "Operating Instructions." The IPB is a part of the
maintenance WP, but is identified by "with IPB" for clarity, e.g., "Maintenance Instructions with
IPB" or "Maintenance with IPB". Maintenance Instructions includes all applicable functional
elements, with related supporting data:
3.3.1 Description and principles of operation. The description and principles of operation
WP shall contain two primary paragraphs, "Description" and "Principles of Operation". The
description and principles of operation may also be divided into separate WPs, depending on the
complexity of the equipment.
10
For Parts Inquires call Parts Hangar, Inc (727) 493-0744
© Copyright 2015 Integrated Publishing, Inc.
A Service Disabled Veteran Owned Small Business