Click here to make tpub.com your Home Page

Page Title: Text development.
Back | Up | Next

Click here for thousands of PDF manuals

Google


Web
www.tpub.com

Home

   
Information Categories
.... Administration
Advancement
Aerographer
Automotive
Aviation
Construction
Diving
Draftsman
Engineering
Electronics
Food and Cooking
Logistics
Math
Medical
Music
Nuclear Fundamentals
Photography
Religion
   
   

 




img
MIL-M-82376B
APPENDIX A
an inch apart.  The headings shall be in boldface, upper case type.
These headings shall be included on each succeeding page of the
troubleshooting table.
b.
Text.
The text portion of the table shall be prepared as follows:
(1)
Title of the assembly group or system breakout and functional
group, when applicable, shall be centered preceding the
malfunction listing, and if continued on a succeeding page,
the group or system breakout will be carried forward followed
by, "(Cent). "
Malfunctions shall be numbered with consecutive Arabic
(2)
numerals beginning with 1.  Tests or inspections shall be
numbered as "Step l," "Step 2," etc., within each malfunction
breakdown. A single corrective action shall not be numbered;
however if more than one corrective action is used, lower case
a, b, c, etc., will be used.
(3)
Malfunctions, tests or inspections, and corrective action text
shall be aligned with the related column headings.  The
malfunction text shall be in boldface, upper case type; test
or inspection text will be lightface, upper and lower case
type; and corrective action text shall be in boldface, upper
and lower case type.
(4)
Illustrations, functional block diagrams, or schematics
considered essential to support the text shall be placed on a
facing page to the text unless the number of illustrations,
functional block diagrams, or schematics required dictates
otherwise.
30.3.3.5.3
Text development.
a.
Text shall be developed in accordance with MIL-M-38784.
Troubleshooting instructions should be limited to isolation of the
causes of the malfunction the technician is authorized to correct.
(The note preceding the troubleshooting table (b above), instructs
the technician to report malfunctions that are not listed in the
table to the next higher level of maintenance).
b.
The troubleshooting table, figure A-1, shall be divided into
logical groups (functional group, assembly group, or system
breakout).  Malfunctions within the groups will be listed in the
order of operation.
c.
The text shall consist of a list of malfunctions, the tests or
inspections necessary to locate or verify the malfunction, and
0023E3
85

Privacy Statement - Press Release - Copyright Information. - Contact Us

Integrated Publishing, Inc. - A (SDVOSB) Service Disabled Veteran Owned Small Business