MIL-DTL-38769E
retrieval is available from the managing Military Department s or Defense Agency s automated packaging
iles, CD-ROM products, or by contacting the responsible packaging activity.
NOTES
6
(This section contains information of a general or explanatory nature that may be helpful, but is not mandatory.)
6.1 Intended use. WUC manuals are used to identify all "work unit" (support general and equipment
identiication), "type maintenance," "action taken," "when discovered," and "how malfunctioned" codes
that apply to the equipment covered by the manual. Under the Air Force data collection system, each
maintenance action performed on Air Force equipment must be fully and accurately documented. The
volume of data collected requires the use of Automatic Data Processing (ADP) techniques. The use of
ADP equipment requires that the data input be coded in such a manner that it can be read by the data
processing machines. Standard codes have been developed for recording the type of maintenance being
performed, the action taken to correct a deiciency, when a deiciency was discovered, and the type of
malfunction that occurred. Identiication codes, called "work unit codes," are used to identify the speciic
assembly or part within an end item on which an action was performed.
6.2 Acquisition requirements. Acquisition documents must specify the following:
a. Title, number, and date of this document.
b. If the arrangement of chapters and sections is to be other than as speciied in this document
(see 3.1.2).
c. If the size of the preliminary and formal manuals are to be other than as speciied in this
document (see 3.1.3).
d. If the column arrangement is to be other than as speciied in this document (see 3.1.5).
e. If the work unit code manuals must be completed prior to the start of the test program (see 3.1.9).
f. If abbreviations may be used as speciied in this document (see 3.2.9).
g. The numeric characters to be used in parentheses between the WUC and the nomenclature
(see 3.2.13).
h. If a 2-chapter, 3-chapter, or standard work unit code manual is to be developed (see 3.3).
j. Packaging requirements (see 5.1).
k. If system code manuals are to be prepared by individual series (see A.3.3.2).
l. If items installed in multiples, within a functional system/homogeneously grouped end item,
and perform within the same function/application parameters, except for location, will have a
single code assigned as speciied in this document (see A.3.8.9).
6.3 Technical manuals. The requirement for technical manuals should be considered when this speciication
is applied on a contract. If technical manuals are required, speciications and standards that have been
authorized and assigned an Acquisition Management Systems Control (AMSC) number must be listed on a
separate Contract Data Requirements List (DD Form 1423), which is included as an exhibit to the contract.
The technical manuals must be acquired under separate contract line item in the contract.
6.4 Codes. Type maintenance, action taken, when discovered, and how malfunction codes are assigned
and controlled by AFI 33-110 (Air Force Data Administration Program). These codes must be approved
by the acquiring activity (see 3.2.5).
6.4.1 Type maintenance code. This code consists of one alphabetic character, and identiies the type of
work performed, (e.g., scheduled or unscheduled maintenance) (see 3.2.5.1).
6.4.2 Action taken code. This code consists of one alphabetic or numeric character, and identiies what
work was done (e.g., removed, replaced, removed and reinstalled same part, etc.). The WUCs and
the action taken code, collectively, identify a "unit of work" as deined in AFI 21-101 (Maintenance
9
For Parts Inquires call Parts Hangar, Inc (727) 493-0744
© Copyright 2015 Integrated Publishing, Inc.
A Service Disabled Veteran Owned Small Business