MIL-DTL-87268D
3.6.1.1 Tasks and subtasks. Each new task or subtask shall begin on a new display. In terms of
content, each task shall involve closely related activities. Each subtask shall include all steps required to
achieve a speciic objective.
3.6.1.2 Title and label requirements. The following title and labeling information shall be associated with
procedural tasks and subtasks. It shall be used primarily for window labeling upon presentation.
3.6.1.3 Task title. Wording of the task title shall be identical with the wording used in the task description in
the detailed task analysis summary of the system supportability analysis. If no supportability analysis task title
is available, the task title shall conform to the requirements of MIL-STD-38784, or the requirements herein.
3.6.1.3.1 Subtask title line. A subtask title line, if required, shall consist of an uppercase title and may have
a subtask number (Arabic). If numbered, subtasks shall be numbered sequentially throughout a task. A subtask
title shall be structured in the same manner as a task title and uniquely identify the material which it heads.
3.6.1.3.2 Step number. Each step shall be presented as consecutive Arabic numerals. The approval of the
acquiring activity shall be required to use any alternate numbering system (see 6.2w).
3.6.1.4 Supporting material for tasks. Procedural data shall contain the following information, which
shall be displayed before the steps are viewed.
3.6.1.4.1 Procedure applicability statement. Any procedure presented shall specify the equipment model,
range, or sequence to which the procedural information applies. When a procedure to be presented does not
apply to all existing models, the applicable equipment model or model range shall be identiied. Such terms
as "on later equipment" and "on early serial numbers" are not acceptable. When a procedure does not apply
to all models, the IETM system shall require entry of the applicable system or equipment model number,
serial number, or other unique system identiier before the task can proceed. If this information has been
entered earlier in the use of the IETM, e.g., log-in, and that information is available at the time the
procedure is presented, reentry of the information shall not be required. Such a control shall be based on
established designations, such as model designation, part number, serial number range, or similar means.
Indeinite categories such as "early serial numbers" or "some late models" shall not be used.
3.6.1.4.2 Initial setup. The initial setup or input conditions, where required, shall be provided
at the
beginning of every new task, e.g., consumable materials, support equipment. All lists provided as
part of the
initial setup shall be headed by individual underlined labels, using upper case initial letters with
successive
letters in lower case. Information presentation in each window shall avoid crowding; as many
frames
shall be used for each initial setup as necessary.
3.6.1.4.3 Safety considerations. Safety conditions shall be identiied as speciied in MIL-STD-38784 and
as stated herein (see 3.2.2).
3.6.1.5 Style requirements. Language (verb tense, person and number) shall comply with the requirements
of MIL-STD-38784 and as stated herein (see 3.6). All essential information shall be available and
readily accessible.
3.6.2 Fault Isolation information. The fundamental logic for interactive fault isolation shall not be dictated
by the IETM presentation system but shall be based on a speciically designed troubleshooting logic which
shall include, but not be limited to, predeined fault isolation sequences and dynamically generated fault
isolation recommendations based on system or user inputs and as speciied herein (see 3.6).
3.6.2.1 General requirements. Fault isolation information shall be designed to permit direct access to
the relevant corrective maintenance procedures after a fault has been isolated, unless otherwise speciied
by the acquiring activity (see 6.2x). The capability shall exist to:
a. Enter symptoms manually by means of symptom codes or human readable text, or by initiation
of automatic retrieval from the system or equipment under observation.
b. Enter and change test results when such information is required by the troubleshooting procedure.
c. Conirm conditions required before continuing a maintenance action.
d. Review and browse through previous actions and test results.
22
For Parts Inquires call Parts Hangar, Inc (727) 493-0744
© Copyright 2015 Integrated Publishing, Inc.
A Service Disabled Veteran Owned Small Business