NOTMEASUREMENTSENSITIVE

MIL-PRF-87268A1 October 1995 SUPERSEDINGMIL-M-8726820 November 1992

Beneficial comments (recommendations, additions, deletions) and any pertinent datawhich may be of use in improving this specification should be addressed to: Det 2, HQESC/AV-2, 4027 Col Glenn Hwy., Suite 300, Dayton, OH 45431-1672; by using theStandardization Document Improvement Proposal (DD Form 1426) appearing at the end ofthis document, or by letter.

AMSC F6846 AREA TMSSDistribution Statement A: Approved for public release; distribution is unlimited.

PERFORMANCE SPECIFICATION

MANUALS, INTERACTIVE ELECTRONIC TECHNICAL - GENERAL

CONTENT, STYLE, FORMAT, AND USER-INTERACTION REQUIREMENTS

This specification is approved for use by all Departments and Agencies of the Department ofDefense.

1. SCOPE

1.1 Scope. This specification contains common requirements for the general content, style,format, and user interaction features which are required for Interactive Electronic TechnicalManuals (IETM). IETMs are digital in form and designed for interactive display to themaintenance technicians or system operator end users by means of a computer controlled anElectronic Display System (EDS). This specification provides requirements governing thecreation and development of IETMs and associated presentation software (see 6.1).

1.2 Paragraphs with limited applicability. This specification contains paragraphs and specificrequirements which are not applicable to all Services. Such paragraphs or requirements areprefixed to indicate the Services to which they pertain: (A) for Army; (N) for Navy; (M) forMarines; and (F) for Air Force.

MIL-PRF-87268A

2

2. APPLICABLE DOCUMENTS

2.1 General. The documents listed in this section are specified in sections 3 and 4 of thisspecification. This section does not include documents cited in other sections of this specificationor recommended for additional information or as examples. While every effort has been made toensure the completeness of this list, document users are cautioned that they must meet allspecified requirements documents cited in sections 3 and 4 of this specification, whether or notthey are listed.

2.2 Government documents.

2.2.1 Specifications, standards, and handbooks. The following specifications, standards, andhandbooks form a part of this document to the extent specified herein. Unless otherwisespecified, the issues of these documents are those listed in the issue of the Department ofDefense Index of Specifications and Standards (DODISS) and supplement thereto, cited in thesolicitation (see 6.2).

SPECIFICATIONS

Military

MIL-PRF-87269 Data Base, Revisable - Interactive ElectronicTechnical Manuals, for the support of

STANDARDS

Military

MIL-STD-12 Abbreviations for Use on Illustrations,Specifications, Standards, and in TechnicalDocuments.

MIL-STD-1840 Automated Interchange of Technical Information

MIL-STD-38784 Standard Practice for Manuals, Technical:General Style and Format Requirements(Appendix A)

(Unless otherwise indicated, copies of the above specifications, standards, and handbooks areavailable from the Standardization Documents Order Desk, 700 Robbins Avenue, Building 4D,Philadelphia, PA 19111-5094.)

2.2.2 Other Government documents, drawings and publications. The following otherGovernment documents, drawings, and publications form a part of this specification to the extentspecified herein. Unless otherwise specified, the issues are those cited in the solicitation.

Department of Defense

DOD 5200.1-R DoD Information Security Program Regulations

DOD 5220.22-M National Industrial Security Program

MIL-PRF-87268A

3

(Application for copies should be addressed to the Superintendent of Documents, US GovernmentPrinting Office, Washington, DC 20402.)

2.3 Non-Government publications. The following document(s) form a part of this document tothe extent specified herein. Unless otherwise specified, the issues of the documents which areDoD adopted are those listed in the issue of the DODISS cited in the solicitation. Unlessotherwise specified, the issues of documents not listed in the DODISS are the issues of thedocument cited in the solicitation (see 6.2).

Aerospace Industries Association PUBS-119, Publications:(AIA) DoD Liaison Recommendation for Hazardous

Materials Warnings in Technical Data

(Application for copies of AIA PUBS-119 documents should be addressed to the AerospaceIndustries Association, 1250 Eye Street NW, Washington, DC 20005.)

American National Standards Institute (ANSI) Publications:

ISO 10744 Information technology - Hypermedia/Time-basedStructuring Language (Hytime)

(Application for copies should be addressed to the American National Standards Institute, 1430Broadway, New York, NY 10018.)

2.4 Order of precedence. In the event of a conflict between the text of this document and thereferences cited herein, the text of this document takes precedence. Nothing in this document,however, supersedes applicable laws and regulations unless a specific exemption has beenobtained.

3. REQUIREMENTS

3.1 General content requirements for the IETM data base. The Interactive Electronic TechnicalManual Data Base (IETMDB) shall be constructed of composite nodes. These nodes shallcomprise the basic units of information within the IETMDB. These composite nodes shall becomposed of primitives, relationships (links) to other pieces of information, and context attributesas defined in MIL-PRF-87269. The primitives of which these composites are constructed shallinclude text, tables, graphics, and dialogs. A revisable data base developed according to therequirements of this specification shall conform to the general requirements listed herein and thespecific requirements of MIL-PRF-87269.

3.1.1 Text. Textual information shall consist of alphanumeric data consisting of letters, words,sentences, paragraphs, numbers, Greek letters, special characters (symbols), etc. Textualinformation shall follow the guidelines for style detailed in 3.3 of this specification. Textualinformation shall contain reference links to other information, parts descriptions, or graphicswhen those links are required to describe the IETM.

MIL-PRF-87268A

4

3.1.2 Tables. Displayable tables shall be represented as a series of separate entries; each entrybeing associated with a specific row and column intersection (cell) of a table. When it isnecessary to associate a table entry with another information element or attribute, the entry(cell) shall refer (through a relationship) to the appropriate architectural element or primitiveelement in the IETMDB.

3.1.3 Graphics. Graphic information (e.g., drawings, illustrations) shall be hierarchical andconsist of logically related groups of graphic primitives. Graphics data elements shall becomposed of a series of these graphic primitives which are capable of being overlaid on each otherto build a complete graphic. These graphics shall be the individual objects capable of beingreferenced in a node. Graphics shall be composed of information represented in accordance withone of the graphic standards included in MIL-STD-1840. Graphics shall include, but not belimited to, the following types: locator diagram, functional block diagram, general supportgraphic, schematic, wiring diagram, flow diagram, or graph/chart.

3.1.4 Dialogs. Dialogs shall be formulated as prompting questions which are intended to bepresented by the EDS to the user. Dialogs shall be developed so that they require a user torespond (i.e., enter data) before any subsequent processing is undertaken. The dialoginformation in the IETMDB shall be formulated so that once a dialog is presented to the user,and answered, certain assertions about the user's environment are able to be made. Theinformation associated with dialogs shall permit the presentation system to provide actions tofollow all completed dialogs. Subsequent procedures available for presentation shall beconditional upon one of the possible answers requested by the prompt.

3.1.5 Element links. Specific information elements in the data base which have relationships toother elements, shall be represented by linking the information together. These links shall bedeveloped to allow the user to branch from the immediate technical information to other relatedinformation. The links shall be of two types. The first type shall provide for a one to one directrelationship between two pieces of information. The second type shall provide for relationshipsto exist between several pieces of information. The links shall not be restricted to any one datatype and shall be available for use with all data elements.

3.1.5.1 Links to reduce redundancy. Links shall be used to eliminate redundant informationelements whenever practicable.

3.1.5.2 Location elements. The location elements used for internal references and external crossreferences shall be developed to conform to the location element definitions of ISO 10744 asspecified by MIL-PRF-87269.

3.1.6 Context. Context dependent filtering, as defined in MIL-PRF-87269, shall be used toprovide the capability to present the user with only the information that applies to a specificconfiguration or situation. This filtering shall be accomplished through the use of preconditionand post-condition elements. The precondition element shall enable the display of appropriateinformation during presentation. The post-condition element shall enable the recording of

MIL-PRF-87268A

5

presentation events for later filtering. The IETMDB shall also contain the additionalprecondition properties which are required to be satisfied for the element to be applicable to thecurrent context at presentation time.

3.2 General content requirements related to IETMs. This following paragraphs present generalrequirements for technical information used for both IETM technical content and IETM userequirements. The following paragraphs on help information and for warnings, cautions, andnotes shall relate to all aspects of the technical function of the IETM.

3.2.1 Help related to technical content. The user shall have access to information relating to thetechnical content of the IETM, such as information on the weapon system itself (e.g., theory ofoperation or schematics) or assistance in using one of the special features of the authoredprocedures. The help function shall also permit the user to access context sensitive help whichapplies to the user's current activity and situation. It shall permit the user to access descriptiveinformation to further explain technical points, define specific terms, or provide a fullerexplanation of processes covered very briefly by the technical information. Help informationshall be available for all sections of the IETM.

3.2.1.1 Administrative information. All IETMs shall contain the following administrativeinformation for subsequent user selectable display:

a. Identification of the technical manual title, assigned technical manual number, anddocument version, as applicable.

b. Classification level of the IETM (also be presented upon initial entry into theIETM).

c. Date, baseline date plus date of latest and all previous changes, if applicable.

d. Verification, change, or revision status, as applicable.

e. Preparing activity.

f. Activity with technical control of the IETM.

g. Activity responsible for configuration management of the equipment/system.

h. Address for forwarding deficiency reports or other evaluative comments.

i. Method of obtaining additional copies and the format of those electronic copies.

j. Distribution statement.

k. Export control notice, if applicable.

MIL-PRF-87268A

6

l. Summary of documents and/or technical manuals that are referenced but notincluded in the automatically accessible data available to the IETM at the time it isused, if applicable.

m. General notes describing the physical method for identifying the specific equipmentto which this IETM applies, the method for identifying the change configurationstatus of equipment when not immediately obvious to a qualified user, and therelationship of the IETM to the particular equipment under maintenance.

3.2.1.2 Applicability statement. The IETM shall contain a highly accessible applicabilitystatement which explicitly identifies the system, equipment, or component to which the IETMapplies, as well as the level of maintenance for which the IETM is intended (i.e., organizational,intermediate, or depot), as applicable. This information shall be in addition to the use of anyautomated feature of the EDS which displays only that information relating to one particularconfiguration. If the IETM applies only to specific members of an equipment class, this shall bestated, and relevant model numbers, serial numbers, aircraft tail numbers, etc., shall be clearlyidentified.

3.2.1.3 Introduction. All IETMs shall contain information which explains the purpose and scope(e.g., organizational level troubleshooting and corrective maintenance for a particular system),content and organization. This section shall present the range of tasks covered by the IETM as itrelates to the purpose and scope of the manual.

3.2.1.4 List of contents. The IETM shall contain a list of contents and shall provide instructionsfor direct user access to each item at the lowest level cited. If the IETM is for proceduralizedcorrective maintenance, the list of contents shall provide all maintenance tasks included. Thelist of contents, while analogous to the table of contents of a paper manual, shall base sequencingon the logic of the logistics support function covered and shall contain branching as needed. Theuser shall be given the capability to access listed entries directly from the list of contents menu.

3.2.1.5 How to use "help" information. In addition to the technical information related helpdescribed in 3.2.1, the user shall be provided with help information involving the use of theIETM or the use of the EDS. This help information shall describe how to use the IETM; e.g.,how to reach (access) specific information and how to employ user interaction functions. How touse this IETM information shall be incorporated as part of the content information for the IETM.

3.2.1.6 Instructions for interactions with IETM utility functions. Information shall be providedwhich describes procedures for all utility functions included as supplements to the primaryfunctions of the IETM (e.g., preparation and submission of associated maintenance actionreports; accumulation and submission of the IETM deficiency reports citing IETM errors orproblems in using the IETM; ordering of needed parts; work center maintenance management;use for on station training; acquisition of additional IETM data).

MIL-PRF-87268A

7

3.2.1.7 Definitions of acronyms and unusual terms. A glossary including all acronyms,abbreviations, and unusual terms shall be incorporated into the IETM and shall be directlyaccessible at all times during the IETM presentation.

3.2.2 Warnings, cautions, and notes. Technical information shall be supplemented withwarnings, cautions, and notes in such a way so as: to attract the user's attention to practices,procedures, and conditions which could lead to injury or equipment damage; to warn the useragainst performance of certain hazardous actions; or to require specific steps leading to safeperformance of the procedure. Procedures prescribed for the operation and maintenance ofequipment shall be consistent with the safety standards established by the Occupational Safetyand Health Act (OSHA), Public Law 91-596, and Executive Order 11807. The informationincluded in warnings and cautions shall conform to the requirements of Appendix A of MIL-STD-38784 to the extent that it is not in conflict with this specification. Appropriate warnings andcautions shall be included when it is impossible to avoid use of or exposure to hazardouschemicals, adverse health factors in the environment, or hazardous equipment. Warnings,cautions, notes, or other information to be highlighted shall:

a. be integrated with the material to which it applies.

b. be apparent to the user as a warning, caution, or note by including an appropriategraphic cue which includes items such as icons, labels (e.g. "WARNING), or othervisual cues.

c. contain all necessary information to reduce or alleviate the hazard.

d. be easy to read and understand in the work environment.

3.2.2.1 Safety summary. Every IETM which contains warnings or cautions shall contain at leastone safety summary conforming to the requirements of Appendix A of MIL-STD-38784 as citedabove. When an IETM contains multiple major procedures, each of which is intended to be usedindependently of the other procedures in the IETM, there shall be a safety summary for eachmajor procedure.

3.2.2.2 Text of warnings and cautions. The textual information contained in warnings andcautions shall be presented in a simple, straightforward, and non-exaggerated manner. Thecontent shall contain all necessary information needed to reduce or alleviate the hazard withoutreference to additional information. Warnings and cautions shall not contain procedural stepsother than those dealing with hazard avoidance or correction. The text of warnings and cautionsshall contain the following information in the order indicated:

a. The specific nature of the hazard.

b. The steps to be taken to avoid or minimize the hazard.

MIL-PRF-87268A

8

c. The location of the source of the hazard.

d. The consequences of failing to heed the warning or caution.

3.2.2.3 Text of notes. Notes shall be written in accordance with the style requirements definedin this specification. Notes shall be used to supply needed information that is not a step in theprocedure. Information presented in notes shall be limited to necessary specifics. Requiredtolerances and clearances shall not be given as notes, but shall be included in the proceduralsteps.

3.2.2.4 Placement of warnings, cautions, and notes. Warnings, cautions, and notes shall belogically positioned at the points where they apply in accordance with the following rules:

a. Warnings and cautions shall be directly associated with and precede in logicalsequence the text or procedural step to which they apply.

b. Notes shall either directly precede or directly follow the applicable text or stepdepending on the point to be emphasized. However, in the case of a proceduralstep, a note shall not follow the procedural step to which it applies.

3.2.3 Danger from multiple sources. When it is possible for one type of danger to come from anyof several sources or one type of danger to require more than one remedial action, the dangermay be referred to once in a single combined warning.

3.2.4 Health hazard precaution data. When hazardous chemicals or other adverse health factorsare present in the environment or will appear during the performance of the procedure, andthese health hazards can not be eliminated, appropriate warning and caution information shallbe included in the technical information. Necessary protective devices for personnel shall belisted in the initial setup (input conditions) of the procedure and referred to in the appropriatesubtask steps or warning/caution message.

3.2.5 Hazardous material icons. Aerospace Industries Association Pubs-119 Publication shall beused to construct warnings, cautions, and applicable icons relating to hazardous substances.

3.3 General style requirements. IETMs shall be prepared in accordance with the general stylerequirements contained in this paragraph. These requirements shall apply both for the languageto be used in textual technical information and for the graphics supplementing the textualportions.

3.3.1 Level of detail. Technical information shall contain all of the information necessary for auser to perform the task involved or to comprehend a description. The criteria required to definethe specific level of detail shall be applied as specified by the procuring activity (see 6.2). TheIETM shall not contain unnecessary detail above or below this level. However, in all cases theIETM shall retain enough information to permit the user to perform the documentedmaintenance without error or loss of time due to insufficient information. Unless otherwise

MIL-PRF-87268A

9

specified by the procuring activity (see 6.2), procedures within steps shall be implemented asfollows. The user shall be given the option to access or bypass a general purpose procedurereferenced by a step (e.g., "Open access panel"), before continuing the task. When a procedure isunique to a task, or involves use of a peculiar piece of equipment, it shall be included in theprocedural data and not made optional.

3.3.2 (A, F) Multiple skill level tracks. If specified by the procuring activity (see 6.2), technicalinformation shall be available in each of two separate and complete skill tracks, eachrepresenting a differing level of detail: one level for a novice skill level and another for an expertskill level. The novice level shall contain all information necessary for an inexperienced user toperform the task involved or to comprehend a description. The expert level shall function as achecklist, presenting only the steps required to complete a task or providing a description inbroader terms, requiring a higher level of theoretical knowledge. Both levels shall contain allpertinent warnings and cautions. The expert user shall be given the ability to access informationat the novice level, but, the novice user shall not be given the capability to access information atthe expert level unless otherwise specified by the procuring activity (see 6.2).

3.3.3 Comprehensibility. To ensure comprehensibility of the IETM data, the following principlesshall be followed in authoring technical information:

a. Essential information in narrative text shall:

(1) Describe the system, components, etc., identifying special or outstandingfeatures.

(2) Describe what functions are performed, including inputs, outputs,interface with other systems, etc.; emphasize end results.

(3) Describe how the functions are performed, including associated principlesof operation.

(4) Describe at what point in an overall system process the function isperformed.

(5) Describe the location of the component or part.

b. When procedural text is combined with graphics, the following rules shall be usedto abbreviate, so long as the meaning is not altered or obscured.

(1) Eliminate articles.

(2) Begin sentences with transitive verbs (action verbs).

MIL-PRF-87268A

10

(3) Use the imperative mood whenever appropriate. The only time subjectsshall be implied is when they are unknown and the passive voice is beingused or when the imperative mood is being used to give an instruction,order, or command, in which case the subject shall always be omitted (i.e.,implied).

c. When it is necessary to indicate time, begin sentences with "when" clauses. Example: "When power supply voltage stabilizes..."

d. Limit paragraphs to a single idea. Limit sentences to a single thought; use nocompound or complex sentences. Whenever possible, limit words to those that areshort and familiar to the target audience. Eliminate long, complex sentences andparagraphs through the use of lists. The resulting parallel portions of sentencesshall be individually listed as in the following example:

The beat frequency oscillator has three components:

(1) ...

(2) ...

(3) ...

e. Sentence length shall not exceed an average of 20 words. The average paragraphshall not exceed six sentences. The desired paragraph length is three to foursentences. Each paragraph shall have a topic entry or sentence. All material inthe paragraph shall relate to and develop the topic sentence.

f. Except in unusual circumstances, text modules (e.g., construct steps andexplanations) shall be fully integrated with graphics modules. Associateexplanatory text to the graphic.

g. Present descriptive text in a logical order (e.g., in operational sequence or in signalflow sequence) and include summary headers for individual paragraphs wheneverneeded for clarity.

h. Keep descriptive text consistent in terminology, style, and format throughout theIETM.

3.3.4 General style requirements for text. IETM text shall be developed in accordance with thefollowing style requirements.

3.3.4.1 Language considerations. Writing shall be factual, specific, terse, clearly worded, andsimply illustrated, so that a user who has the required aptitude, training, and experience willunderstand it.

MIL-PRF-87268A

11

3.3.4.2 Proper amount of technical information. The IETM shall provide all the technicalinformation required by a technician to perform the task. It shall not contain extraneousmaterial. Helpful, but not required, information shall be included only in the form of useraccessible HELP (see 3.2.1).

3.3.4.3 Nomenclature. Nomenclature used for names of equipment item assemblies, parts, etc.,shall be in agreement with the approved nomenclature list prepared as part of the supportabilityanalysis records or other official maintenance specification, as applicable. Use of thisnomenclature or its substitution with a standard shortened identifier (i.e., acronym, commonname) shall be consistent throughout the entire IETM and among all IETMs which apply to theweapon system or equipment involved. If specified by the procuring activity, standard shortenedidentifiers shall be substituted at all times when no confusion will result (see 6.2).

3.3.4.3.1 Nomenclature for tools and test equipment. The official nomenclature shall be used inthe first occurrence in a task or procedure, for all titles, parts lists, support/test equipment lists,consumable/expendable lists, and work unit codes. When a common name exists for the sameitem, it may be used in place of the official name. Official and common name usage shall beconsistent, as described above, throughout the IETM (see 3.3.4.7).

3.3.4.3.2 Nomenclature for controls and indicators. Controls and indicators identified in aprocedure shall be identified exactly as placarded on the equipment. Component referencedesignators (R105, C56, etc.) shall be omitted unless the reference designator itself appears onthe equipment or if two or more controls/indicators have identical nomenclature. If variations inpanel or chassis nomenclature exist, a comment explaining that the panel nomenclatures aretypical and may vary slightly from one unit to another shall be included. Controls and indicatorswith functional names only (no panel names) shall be identified by functional name.

3.3.4.4 Abbreviations. Use of abbreviations (including abbreviations for common units) shall beheld to a minimum. Standard abbreviations shall be in accordance with MIL-STD-12. Eachabbreviation shall be defined in the IETM glossary.

3.3.4.5 Unit of measure. Unit of measure shall be consistent throughout the IETM. If nototherwise specified on the equipment, measurements shall be in U.S. standard units (ounces,pounds, gallons, inches, feet, knots, miles, etc.). Units of measure shall be used as follows:

a. Temperature readings as marked on the equipment. If other than Fahrenheit, theequivalent in Fahrenheit shall follow parenthetically. General ambienttemperature references, such as room temperature, shall be given in degreesFahrenheit.

b. Speed, distance, and meter readings as marked on the equipment. When themetric system is used on the equipment, conversion to U.S. standards ofmeasurement shall follow in parentheses. If specified by the procuring activity,conversion of U.S. standards of measurement to metric standards of measurementshall follow in parentheses (see 6.2).

MIL-PRF-87268A

12

c. Switch positions and panel markings exactly as marked on the equipment. However, symbols on panel markings, such as the symbols for "ohm" or "infinity,"may be spelled out in textual references when they cannot be produced by thepresentation system.

3.3.4.6 Numerical expression of tolerances. The optimal value shall be expressed, along withassociated tolerances (e.g., 15 ± 1.25 VDC, or 15 +4/-2 VDC), for numeric measurement values. Tolerances shall not be expressed in percentages. All numerical values given shall match thenumber of decimal places indicated on the affected instruments. Torque measurement valuesshall conform to the calibration of the required tool.

3.3.4.7 Vocabulary (permitted words). If specified by the procuring activity, words used in thetext of the IETM shall be limited to those contained in "permitted word lists" (see 6.2). Wordsinitially used by the IETM author, which are not on these lists, shall be eliminated and replacedwith permitted words, unless the comprehensibility of a given passage requires the use of a"non-permitted" word. Non-permitted words shall be approved by the Government. Terminologyshall be consistent throughout the IETM; i.e., the same word for a given component must be usedthroughout the IETM.

3.3.5 General style requirements for graphics. Graphics for IETMs shall be developed inaccordance with the general style requirements of the following paragraphs as they relate toindividual graphics or to associations of both graphics and text. The requirements of theseparagraphs shall apply to the display of the IETM on the least capable device (i.e., smallestscreen) which is specified for use with the weapon system or equipments to be supported by theIETM (see 6.2).

3.3.5.1 Graphic conventions. Displayable graphics shall have a means for designating theminimum size at which that graphic is capable of being discerned when physically displayed andwhether that graphic is permitted to be displayed using interactive functions. The particularencoding standards shall conform to the system specific IETMDB implementation and thedesignated presentation system. Non-interactive graphics shall be viewed in full detail withoutmanipulation. Interactive graphics shall allow the user to either manipulate the graphic forbetter view or allow the user to choose selectable areas within the graphic.

3.3.5.2 Minimum size for graphics. Graphics shall be displayed no smaller than required to meetthe minimum displayable size which has been designated for each individual graphic.

3.3.5.3 Graphic density. Graphics shall show only that detail needed to support the action beingdescribed.

3.3.5.4 Quality of graphics. Graphics shall be prepared to a scale that ensures legibility of allessential detail. Line widths shall be of sufficient density to register sharply and clearly whendisplayed at the designated minimum size EDS.

MIL-PRF-87268A

13

3.3.5.5 Level of detail in graphics. Graphics shall present only the equipment items referred toby the action statements, plus sufficient surroundings to permit the user to correctly locate theitem.

3.3.5.6 Measurements and tolerances. Numerical measurements and tolerances shall beexpressed in the same manner as that required for text (see 3.3.4.6).

3.3.5.7 Textual citations of panel nomenclature. In all references to controls, control positions,test points, and indicating devices which have panel or chassis nomenclature, the nomenclatureused in the textual label shall be displayed exactly as it appears on the panel or chassis (e.g., allcapitals if used, spacing, and special symbols). Nomenclature shall not be enclosed in quotationmarks unless required for clarity. Functional names shall be used in procedures involvingcontrols and indicators with no panel names. Unless otherwise specified by the procuringactivity, all nomenclature used in graphics shall be identical to the nomenclature for thecorresponding item in the related text (see 3.3.4.3.2 and 6.2).

3.3.5.8 Angle of view. Graphics shall be drawn from the same general angle of view that theuser sees the equipment, ( e.g., during a given step of a procedure). Cutaways and hidden linesshall be used as required in conjunction with details that are accessible, but not visible, to theuser (e.g., as seen after removal of an access cover or after opening a cabinet door). In situationswhere the user is able to view the hardware from more than one angle, the view which providesthe most pertinent and necessary information shall be used. An item or part removed from thesystem may be rotated to show important features; the axis, direction, and degrees of rotationshall be indicated in the graphic. Perspective and isometric graphics shall be used for a morerealistic view. Orthographic projection may be used if the view is head-on.

3.3.5.9 Use of the human figure. When it is necessary to illustrate an operation or procedure,graphics may include a human figure or parts of the body. Jewelry shall not appear in anygraphics. The human figure shall not obscure details of the equipment necessary for a completeunderstanding of its operation. The human figure shall be clothed as specified by the procuringactivity (see 6.2).

3.3.5.10 Types of graphics. Where required to present maintenance procedures or descriptions,an IETM shall contain graphics to include, but not be limited to, such types as frontispiece(assembled view), isometric, perspective, and orthogonal.

3.3.5.11 Drawings. When engineering drawings are used as a baseline in the development ofgraphics, details which reduce the comprehensibility and clarity of the graphic shall be removed. Electrical and engineering diagrams shall be laid out functionally. Where information must bepresented by means of a signal flow chart or circuit diagram, such visual aids shall be dividedinto discrete units, simplified, and standardized.

3.3.5.12 Schematic and wiring diagrams. Unless otherwise specified by the procuring activity,wire lists, schematics, and wiring diagrams initially displayed along with an associated text paneshall be simplified to contain only the information referenced by the accompanying text (see 6.2). The technician shall have access to the entire wire list, schematic, or wiring diagram when thatfull graphic is available in the IETM.

MIL-PRF-87268A

14

3.3.5.13 Functional flow diagrams. Functional flow diagrams shall be drawn as flowchartsindicating the direction of system interaction. The information shall flow from left-to-right andtop-to-bottom on diagrams. The diagrams shall indicate the detail referenced by theaccompanying text.

3.3.5.14 Locator graphics. A locator graphic shall consist of a labeled graphic together withrequired callouts. Locator graphics, when used, shall either be an option, or an automated partof the procedural or descriptive information presented, as specified by the procuring activity (see6.2).

3.3.5.14.1 Placement. Placement of locator graphics shall be fully integrated with the associatedtechnical information.

a. The individual equipment items (e.g., parts, switches, controls, indicators, andother items) shall be shown in physical context to the major equipment componentsof the illustrated hardware. The nomenclature of the major equipment componentshall be shown on the graphic.

b. Index numbers on callouts shall be assigned, if required, on the equipment itemlocator graphic either: in clockwise sequence, or in the sequence that the item isdiscussed in the procedural steps.

c. When reference is made to an illustrated equipment item in a procedural step, thestep reference shall be keyed directly to the relevant equipment item (e.g., part,switch, control, indicator, or other item) by a callout reference citation from the text(e.g., item name) or an index number and a leader line pointing to the referenceditem.

3.3.5.14.2 Successive graphics. Successive locator graphics may be used in lieu of a singlegraphic to lead the user systematically from a large overall (general) view to successively lowerlevel (specific) views in a logical presentation sequence. Item exploded views shall be used aslocator graphics only where further disassembly is required.

3.3.5.14.3 Format. The minimum size of the locator graphics shall provide sufficient resolutionto enable the user to quickly identify the surroundings and the item to be located with respect tothe surroundings. A callout shall be used to emphasize the item to be located.

3.3.5.15 Callouts and Leader Lines. Callouts and leader lines shall be provided to identifyspecific features of interest on graphics. The following provisions for callouts shall be followed:

a. Callouts shall be keyed to the procedural steps or descriptive informationdisplayed.

MIL-PRF-87268A

15

b. Callouts and identifier numbers shall not be crowded into spaces between graphicelements; callouts shall be clearly distinguishable from the graphic elements andeach other.

c. Labels used for part names or other graphic element identifiers instead of indexnumbers shall be identical to those used in the associated text.

d. Leader lines (with arrow heads) shall be drawn from the index number to theequipment item.

e. Leader line width shall differentiate from graphic line width.

f. Leader lines shall not obscure essential graphic detail.

g. Leader lines shall not cross graphic lines if, an alternative is possible.

h. Leader lines shall be straight wherever possible.

i. When straight lines are not possible, leader lines shall have one bend at an angle of45 degrees, drawn with the angled end pointing to the graphic.

j. Leader lines shall not cross or come in contact with other leader lines.

3.3.5.16 Style requirements for animated information. The motion of the animated informationshall be easily discernable by the user and clearly differentiated from the background and otherstatic information of the overall display.

3.3.6 General style requirements for audio information. Audio information shall consist ofnonverbal auditory tones, or computer generated or electronically stored speech. Redundantvisual information shall be provided to ensure effective information presentation when the audiooutput device is not available or functioning.

3.3.6.1 Requirements for nonverbal auditory tones. Nonverbal auditory tones shall be limited toapplications where immediate discrimination is not critical to personnel safety or systemperformance. Nonverbal auditory tone frequencies shall range between 200 to 5000 Hz,preferably between 500 and 3000 Hz. Nonverbal audio tones shall be of sufficiently low intensityand duration so as not to startle the hearer, add to overall noise levels, or interfere with localspeech.

3.3.6.1.1 Nonverbal auditory tones in conjunction with error messages and alerts. Nonverbalauditory tones used in conjunction with a visually displayed error message or alert, shall consistof a single frequency and shall precede the presentation of the visually displayed message oralert by no more than 0.5 seconds.

MIL-PRF-87268A

16

3.3.6.1.2 Compatibility with ambient conditions. Nonverbal auditory tones which might bemistaken for tones commonly found in the work environment shall not be used.

3.3.6.2 Computer-generated or electronically-stored speech. Computer-generated orelectronically stored speech shall be limited to procedural information.

3.3.6.2.1 Abbreviations. Computer generated or electronically stored speech shall be encoded topronounce the entire word an abbreviation represents (e.g., for the abbreviation "sec." the word"second" shall be pronounced). Computer generated or electronically stored speech shall beencoded to pronounce the individual letters of abbreviations of multi word phrases, withoutregard to case or punctuation, when that pronunciation is in common usage (e.g., for theabbreviation "A.D." (Anno Domino), the individual letters "a" and "d" shall be pronounced). When pronunciation of the individual letters of abbreviations of multi word phrases is not incommon usage, computer generated or electronically stored speech shall be encoded to pronounceeach word the abbreviation represents (e.g., for the abbreviation "SSE", shall be pronounced"south south east").

3.3.6.2.2 Acronyms. Any acronym used in the context of procedural information that eithercannot be or typically is not pronounced as a whole recognizable word, shall be encoded by thecomputer speech system as single letters (e.g., the acronym "APU" shall be pronounced: "A P U").

3.3.6.2.3 Alphanumeric strings. Any string of digits or alphanumeric characters used in thecontext of procedural information that typically are not pronounced as an intact unit shall beencoded as single spoken letters or combinations of numbers and letters (e.g., the referencedesignator A1A12A9 shall be pronounced: "A one A twelve A nine;" while the part number78349015 shall be pronounced: "seven eight three four nine zero one five").

3.4 General requirements for common user interface. IETMs and the associated EDSpresentation software shall provide the display formatting and user interaction functionsdescribed herein. Required user interaction functions, written in uppercase throughout thisspecification, shall not be employed as literal key names on an EDS device, but shall be treatedas logical or "virtual" functions which shall be implemented as specified for the particular displaysystem. For example, the cursor movement and selection functions can be optionallyimplemented by a mouse, a joystick, a track ball, a light pen, a touch panel, voice commands, orarrow keys with a selection key. An OK function can be implemented as a dedicated key labeled"enter" or a "soft" function key. This specification identifies the logical user input functionswhich shall be supported by the display system, without specifying the exact keyboard orhardware requirements for the display system. Table I provides a list of the minimum userinterface virtual functions and general definitions of those functions. These functions shall beimplemented to permit the minimum functionality as described below. However, this shall notpreclude additional detailed requirements in an IETM presentation software specification thatfurther defines functionality.

3.4.1 Common user interface components. A common set of components and presentationconventions shall be used to provide a consistent user interface across all presentation devices

MIL-PRF-87268A

17

Virtual Function DescriptionSELECT Make a choice at the current cursor position

POINTER SELECT Move cursor and make a choice at the current pointer position

OK End input; process data or indicated action

DELETE Remove items indicated by the cursor

CANCEL Terminate current action without entering data

MENU Activate Menu and toggle menu bar on if applicable

UP Move cursor up

DOWN Move cursor down

LEFT Move cursor left

RIGHT Move cursor right

TAB Move cursor to next field

BACK TAB Move cursor to previous field

SCROLL-UP Move scroll bar slider box up (image down)

SCROLL-DOWN Move scroll bar slider box down (image up)

SCROLL-LEFT Move scroll bar slider box left (image right)

SCROLL-RIGHT Move scroll bar slider box right (image left)

CENTER Relocate center of graphic to position of cursor after ZOOM-IN

ZOOM-IN Enlarge the displayed image

ZOOM-OUT Reduce the displayed image

SYSTEM HELP Access application help

CONTEXT HELP Access situation-specific help

FULL SCREEN Enlarge graphic to size of client area

QUIT End current application; close windows associated with application

TABLE I. List of minimum user interface virtual functions.

Common user interface components described in this specification shall be implemented on alltypes of presentation systems used unless otherwise specified. (see 6.2) The components cursor,windows, menus, controls, dialogs, and optional pointer shall be implemented as follows.

3.4.1.1 Cursor. If the information on the screen is capable of being selected, the system shallprovide the user with the ability to select the information with a cursor. The cursor shalldesignate the position on the screen where the input is focused. The cursor shall be visually andconsistently distinguishable from other information on the display. Selectable information shallbe visually and consistently distinguishable from the cursor and other information on the screen(e.g., by the use of a border or frame around the selectable object).

MIL-PRF-87268A

18

3.4.1.1.1 Selection. The user shall be able to select items in the client area with the cursor. TheIETM shall provide the user with a visual feedback of the selection. Selecting an alreadyselected item shall deselect that item. The user shall be provided with the capability to select asingle item, a range of items, or additional noncontiguous items, including multiple ranges ofitems. Selecting the OK function will end the selection process. If a user is required to selectonly one option, the SELECT function shall activate the item without requiring the OK function.

3.4.1.1.2 Movement. The cursor shall be capable of moving from one selectable information itemto another, such as, from cell to cell in a table, from selectable word to selectable word in text, orfrom selectable object to selectable object in a graphic. If a free-form positioning device (e.g.,mouse) is not provided, the capability to use the UP, DOWN, LEFT, and RIGHT functions toallow movement of the cursor to any selectable region shall be provided.

3.4.1.1.3 Shapes. Each cursor mode shall use clearly discernable shapes or icons.

3.4.1.1.4 Tab groups. When several sets of selectable objects are displayed, they shall be formedinto fields called "tab groups". Cursor movement (and associated focus for any input) shall beconstrained within a single tab group. The TAB function shall allow a forward sequentialmovement of the cursor between tab groups. The BACK TAB function shall allow a reversesequential movement of the cursor between tab groups. Examples of tab groups are: individualfill-in-the-blanks, groups of related choices, and dialog push buttons.

3.4.1.1.5 Pointer. If the system provides a free-form positioning device it shall have a positiondesignator (pointer) and a POINTER SELECT function. The pointer shall be used in conjunctionwith the cursor. The pointer shall be used to rapidly relocate the cursor on the display. Thesystem shall provide the capability to move the cursor and select items with the pointer.

3.4.1.2 Windows. A window shall be an area of the screen that displays information andprovides the functional means to communicate with the IETM. The presentation system shallhave the capability to display a minimum of three windows on the screen at one time, but onlyone window shall be active at any one time. An active window shall be designated by ahighlighted title bar. The system shall provide the capability to open and close windows. Thesystem shall allow windows to be displayed overlapping, adjacent (tiled), and cascading(overlapping with title bars showing). If a single window device is specified by the procuringactivity, the IETM shall restrict the use of multiple windows (see 6.2).

3.4.1.2.1 Presentation. The minimum window shall be composed of client area, title bar, menubar, and window controls (see figures 1 and 2). Window controls are not applicable to singlewindow systems (see 3.4.1.2).

3.4.1.2.2 Client area. The client area shall be the portion of the window in which the IETMcontent information is displayed. The client area shall be contained within the window frameand include one or more data panes or viewing areas displaying the text, tables, graphics, etc., ofthe IETM information. The IETM contents shall be displayed in the client area (see 3.5.1.).

MIL-PRF-87268A

19

FIGURE 1. Components of the display window

3.4.1.2.3 Title bar and menu bar. The top area of every window shall consist of a horizontal titlebar and a menu bar that, when displayed, appears immediately below the title bar. The title barshall contain the title of the information being displayed. The title shall be displayed inuppercase letters. The menu bar (see 3.4.1.3) shall appear only at the user's request. The titlebar shall be highlighted when the window is active. When the single window option is specifiedby the procuring activity (see 6.2), the title bar shall be capable of being toggled on and off with amenu bar (see 3.4.1.3.5.1). In this case, the title bar shall be initially displayed at the top of thewindow and the menu bar shall replace the title bar display when toggled.

3.4.1.2.4 Window controls. Whenever the information to be displayed requires a space largerthan the available window area, the user shall be given the capability to manipulate thedisplayed information or window using the following window controls. The need for thiscapability shall be minimized.

3.4.1.2.4.1 Scroll bars. Vertical and horizontal scroll bars shall provide the capability toSCROLL UP, SCROLL DOWN, SCROLL LEFT, and SCROLL RIGHT to manipulate thedisplayed information (text, graphic, table, etc.). Scroll bars shall appear at the bottom of thedata pane and at the right edge of the data pane with arrow marks at each corner. Scroll barsshall have the following components; a scroll region which is the background of the scroll bar andrepresents visually the length of the area that can be scrolled; a slider box which represents

MIL-PRF-87268A

20

FIGURE 2. Basic display window with optional controls

the displayed data; and stepper arrows which enable incremental scrolling through the display. When scrolled, the information shall appear to move in the opposite direction of the slider. Forexample, in a text data pane, if the slider of a vertical scroll bar moves up, a text display shallmove down as previous lines in the information appear at the top of the data pane.

3.4.1.2.4.2 Window control options. If specified by the procuring activity, additional windowcontrols shall be included as described below (see 6.2).

3.4.1.2.4.2.1 Window resize and relocation. The window resize function shall allow adjustmentof individual window location and physical display size. Initially, resizable windows shall bedisplayed at the default size indicated for that display. The capability to alter the size of theactive window shall be available at any time during the presentation. The control mechanism forthe resize function shall be located inside the window frame on one or more corners of the frame.Any resizable window shall have a distinctive border or consistent indicator which signifies thatit can be resized. When the window is resized, the amount of information it contains shallincrease or decrease (i.e., more of the text or graphic is shown when the window is enlarged). Itshall not simply be rescaled. When changing the size of the window is not permitted, the resizeborder shall not be included as one of the window components.

MIL-PRF-87268A

21

3.4.1.2.4.2.2 Window menu button. A window menu button shall be located in the upper leftcorner of the title bar and shall be used to activate the window menu.

3.4.1.3 Menu system. The user shall be given the capability to access all of the functionsavailable on the system through hard keys, a footer bar, or a menu system. The menu systemshall consist of a menu bar which shall control a hierarchy of pull-down menus and a set of pop-up menus. The window menu shall provide the standard location for window managementfunctions.

3.4.1.3.1 Pull-down. Pull-down menus shall be displayed as a vertical column of selectableitems. When active, titles on the menu bar of available pull-down menus shall always be visibleto the user.

3.4.1.3.2 Pop-up. Pop-up menus shall be displayed as vertical columns of selectable items. Pop-up menus shall appear adjacent to the selectable item.

3.4.1.3.3 Cascading. Cascading menus or submenus shall be used to add detail to pull-down andpop-up menus. Cascading menus shall provide a tree like structure for organizing information. If required, menu subfunctions shall appear and more selections shall be provided to the user.

3.4.1.3.4 Presentation details. Menus shall appear quickly and exist only while a selection isbeing made. Menu items shall be displayed in uppercase and lowercase characters. The usershall not be given the capability to interact with any other part of the data until the menu isremoved. The user shall be given the capability select or activate the menu item with the cursoror pointer. The user shall be allowed to exit any menu by activating the CANCEL function.

3.4.1.3.4.1 Width. The minimum menu column width shall be no less than five text characters. Menu columns shall be wide enough to enclose all menu item labels or options so that no optionis truncated. Whenever an individual menu item is too wide for display in the client area, it shallwrap to the next line. If the entire menu can not be presented within the client area, hiddenmenu data shall be indicated to the user.

3.4.1.3.4.2 Height. The minimum menu height shall be the height of two menu items (i.e., themenu title plus at least one menu item). The maximum displayed menu height shall be theheight of the client area. Fonts and font sizes, line spacing between menu items, and allowablemargins between menu items shall conform to the requirements for the display and selection oftext (see 3.4.2).

3.4.1.3.4.3 Border. The menu shall be drawn with a boundary extending beyond the menu cells.

3.4.1.3.4.4 Highlighting. Highlighting shall be used to indicate the cursor is on a selectablemenu item. Reverse video (or similar brightness coding) shall be used to highlight the menuitem after the item is selected.

3.4.1.3.4.5 De-emphasis. The system shall gray-out or dim menu selections which areunavailable. The user shall not have the capability to display a menu when all selections areunavailable.

MIL-PRF-87268A

22

3.4.1.3.4.6 Organization of selections. Selections shall be grouped functionally or by frequency ofuse, alphabetically, or by some other clearly understood organizational scheme. Commands thatchange system status or enter other input and can not be reversed shall not be displayed next tofrequently chosen selections.

3.4.1.3.4.7 Cursor default locations. The cursor shall be positioned at the same default locationin a menu every time that menu is accessed.

3.4.1.3.5 Menu bar. When displayed, the menu bar shall be a single horizontal row of menutitles. Titles shall be unique descriptive textual labels, of one or more words, that clearlydifferentiate each menu item. All functions available on the system and not included on thefooter bar or on the presentation system hard keys (e.g., ENTER, TAB) shall be listed in menuson the menu bar and shall be accessible at any time. Footer bar options may also be duplicatedin the menu bar.

3.4.1.3.5.1 Menu bar on single window screen device. When a single window device is specifiedby the procuring activity (see 6.2), the title bar and the menu bar shall be located in the samearea. Each shall have the capability to be toggled on and off through a MENU function (see3.4.1.3). Default information displayed in the top area of the window shall be the title bar. When the menu bar is displayed, the title bar shall disappear and vice versa. The user shall begiven the capability to view either the title bar or the menu bar at all times.

3.4.1.3.6 Command interface. The system shall provide a command interface using mnemonicsor numeric entries as a means for making selections from menus in addition to navigation andselection functions. The command interface for selections from the menu bar shall be availableat all times when the menu is active. When a single window device is specified by the procuringactivity (see 6.2), the command interface shall be available only when the menu bar is displayedand active (see 3.4.1.2). Users shall be given the capability to enter the required numeric keyvalue(s) or mnemonic key combination that corresponds to displayed menu options to activatethe command interface.

3.4.1.3.6.1 Mnemonics. A mnemonic shall be a single character, usually the first letter of theselection. The mnemonic for the various menus shall provide a visual cue to the user. Twoselections in a menu shall not begin with the same letter; a unique mnemonic for each selectionshall be used. When the mnemonic of the selection does not appear within the text of theselection, it shall be included in parentheses after the text. Mnemonics shall only be availablewhen the menu containing them is displayed.

3.4.1.3.6.2 Numeric values. Numeric values may be used, as an alternative to mnemonics. Ifnumeric values are used, selection numbers shall be separated from their text descriptors by atleast one blank space. The numeric code and descriptive label for each choice on the menu shallbe left justified.

3.4.1.4 Dialogs and dialog controls. A dialog box shall be used as the principal means tocommunicate with the IETM application software. See figure 3 for examples of different types ofdialogs. Dialogs shall be displayed in a separate window, which may overlay the primary

MIL-PRF-87268A

23

window, and shall contain a heading and one or more graphical controls (buttons). Dialogs shallbe one of five kinds: alert, single/multiple choice, selection-in-list, combination, or data entry(data entry is depicted in the combination dialog box in figure 3) and shall use check-boxes, radiobuttons, data entry, etc., to determine the course of action required. Dialog boxes shall appear ina consistent and prominent location on the display. All dialogs shall contain the OK andCANCEL functions. However, information only alerts, e.g., system messages, shall include theappropriate push buttons to acknowledge the alert. The OK or CANCEL functions shallcomplete the dialog box interaction. Dialog boxes shall distinguish the information they containfrom other information displayed.

FIGURE 3. Dialog Box Types

MIL-PRF-87268A

24

3.4.1.4.1 Dialog cursor movement. The cursor shall move only to items which require input fromthe user.

3.4.1.4.2 Dialog box presentation. Headings used in dialog boxes shall be distinctive and notconfused with other displayed material. Headings shall be placed in close proximity to theirrespective response alternatives (i.e., buttons). Dialog headings shall end in the appropriatepunctuation depending on the response required.

3.4.1.4.3 Dialog push buttons. Dialog boxes shall contain graphical controls called push buttons. A push button shall be a word or graphic icon on the screen used to select or initiate an action. Push buttons shall be large enough allow positioning of the cursor on the push button. Pushbuttons or choices shall provide visual feedback when selected. Push buttons shall be found onevery type of dialog box. They shall each be single action entities. Push buttons shall indicateselections made or invoke a general action (e.g., CANCEL or OK). Push button shapes shall beconsistent, (e.g., box, circle, or arrow) with the name of the selection or action written inside ofthe shape. Common push buttons (OK, CANCEL) shall be displayed along the bottom of thedialog box. The common dialog buttons shall correspond to completing the last selection beforeleaving the dialog box.

3.4.1.4.3.1 Use of push buttons. Dialog transactions shall be completed by using push buttons.As a minimum, these buttons shall have the functions OK and CANCEL. CANCEL shall beequivalent to the CANCEL function and shall cancel the dialog box. The OK function shallcommunicate to the application software that the user has completed the dialog.

3.4.1.4.4 Alert dialogs. Alert messages shall include warnings, cautions, and notes; anymessage, communication, notice, or output which requires manual acknowledgment; or messagegenerated as a result of erroneous inputs or sequence control actions. Alerts shall provideinformation regarding processing status. Alerts shall also provide status of the system internalcomponents (e.g., low battery power, improper functioning of the operating system, or memorymodule).

3.4.1.4.4.1 Alert information content. Alerts shall be brief, consistent, strictly factual,informative, and written in the active voice. Alerts shall not imply or ascribe blame to the user,"personalize" the computer, or attempt to make the content of the information humorous. Alertsregarding calls to erroneous or potentially destructive external systems shall be displayed. Following an interruption of data processing or database navigation/sequencing command (e.g.,CANCEL), an advisory message shall be displayed indicating that the system has returned to itsprevious status.

3.4.1.4.5 Choice dialogs. A choice dialog shall require one or more selections from a group ofchoices. Choice dialogs shall consist of a single choice dialog, multiple choice dialog, or acombination of the two. Radio buttons and check boxes shall be used to indicate choices and shallbe left justified and separated from text descriptors by at least one blank space. If choices areplaced in columns, the check box or radio button position shall be left justified with respect to thecolumn. Each response alternative listed in a dialog box shall be given a short, unique,descriptive label.

MIL-PRF-87268A

25

3.4.1.4.5.1 Single choice (radio buttons). Selectable items that are mutually exclusive (i.e., onlyone can be selected at any time) shall be presented as a single choice dialog constructed usingradio buttons. Radio buttons shall be grouped into lists of mutually exclusive choices. Eachradio button shall appear as a consistent shape (e.g., a circle) and shall be marked with a visualindicator when the button is selected.

3.4.1.4.5.2 Multiple choice (check boxes). A multiple choice dialog shall be the type of dialog inwhich one or more selections are able to be made from a group of choices. Multiple selectionsshall be made using check boxes. Check boxes shall be grouped into lists of non-mutuallyexclusive choices. The user shall be given the capability to check one or more of these boxes asneeded using the cursor or number selection technique. Each button shall appear as a consistentshape (e.g., a square) and shall be marked with a visual indicator when the button is selected. Check boxes shall employ different shapes from radio buttons.

3.4.1.4.6 Data Entry dialogs. Data Entry dialogs shall require entry of alphanumeric charactersin response to displayed questions or data entry fields (e.g., inputting user identification data;entering the title or number of database frames containing errors or discrepancies). All DataEntry dialogs data entries shall be prompted explicitly by displayed labels for data fields. Theuser shall be given the capability to DELETE or otherwise change previous entries.

3.4.1.4.7 Selection-in-list. The selection-in-list shall provide the means of manipulating lists ofdata to a point where an item can be highlighted and an action on the item taken. The selection-in-list shall enable the user to choose from an existing list of items that is either long or variablein length. In addition to the standard features of all dialogs, the selection-in-list shall have atleast two additional characteristics: a window containing the content listing and a vertical scrollbar when the entire list will not fit within the window.

3.4.1.4.8 Combination dialog. A composite of the previous types of dialogs shall be locatedtogether in one dialog box, when required.

3.4.2 Display formatting and user interaction requirements. The following paragraphs describethe standard data types (text, graphics, tables, and user prompts) that shall be displayable in theclient area. When standard data types are individually displayed in data panes, those datapanes shall have the capability to be linked to form one logical unit of technical informationdisplay within a single window frame.

3.4.2.1 Text. Textual information shall consist of alphanumeric data consisting of letters, words,sentences, paragraphs, numbers, etc., in accordance with style guidelines described earlier inthis specification.

3.4.2.1.1 Display of text. Textual information shall be displayed in data panes of the client area. Text shall be displayed in uppercase and lowercase characters.

MIL-PRF-87268A

26

Viewing Distance Minimum CharacterHeight

Optimal Character Height

(Inches) 16 Minutes of Arc 20 Minutes of Arc

(Inches) (Inches)

18 0.08 0.11

24 0.11 0.14

30 0.14 0.17

36 0.17 0.21

42 0.20 0.24

48 0.22 0.28

54 0.25 0.31

60 0.28 0.35

66 0.31 0.38

72 0.34 0.42

Note: The formula used for the above calculations is: Character Height =[(Min of Arc x Viewing Distance)/(57.3 x 60)]

TABLE II Minimum and optimal character heights for variousviewing distances at viewing angles of 16 and 20 minutesof arc.

3.4.2.1.1.1 Character font. All titles, headings, callouts and special characters shall be sans-seriffont. Narrative text shall be serif font. Table II lists the minimum recommended characterheights for various reference viewing distances and shall be used to determine the appropriatecharacter font size. Unless otherwise specified by the procuring activity, the minimum referenceviewing distance shall be 36 inches (see 6.2).

3.4.2.1.1.2 Character spacing. Character spacing in textual displays shall be no less than 0.1character height. Between word spacing for textual displays shall be one character width (emspace).

3.4.2.1.1.3 Line dimensions. Between line spacing for textual displays shall be 0.33 of characterheight exclusive of superscripts and subscripts and no less than 0.15 character height whensuperscripts and subscripts are displayed.

MIL-PRF-87268A

27

3.4.2.1.1.3.1 Text panes. The width of the text pane shall range from 30-60 characters per line.

3.4.2.1.1.4 Margins. Margins shall be required for all text panes to prevent information frombeing obscured by borders or information in adjacent panes.

3.4.2.1.1.5 Justification. Left justification shall be used for all lines of text displayed assentences or paragraphs.

3.4.2.1.1.6 Word wrapping. Lines of text shall wrap, so that no line extends beyond the limits ofthe pane or right margin, including when resized. Lines shall be broken only between individualwords or within a word when that word is explicitly hyphenated. If resized text exceeds the textpane area, vertical scrolling shall be used (see 3.4.2.1.2.1).

3.4.2.1.1.7 Hyphenation. Hyphenation shall not be used to display normally non-hyphenatedwords on successive lines.

3.4.2.1.2 Selection of text. The ability to highlight selectable textual information on the screen(e.g., by color change, brightness variance, image reversal, font change) shall exist. Thecapability to select a highlighted character string (i.e., one that is indicated as selectable) bypositioning the cursor on or near that string and activating the SELECT function shall beprovided.

3.4.2.1.2.1 Scrolling. When the displayed text exceeds the length of the data pane, the text shallscroll and a visual cue shall be provided (vertical scroll bar). Manipulation of the displayed textshall be provided using the SCROLL function. The capability to move through textualinformation, one line at a time, shall be provided using the SCROLL UP and SCROLL DOWNfunctions.

3.4.2.2 Graphics. The IETM shall display graphics in a data pane as follows.

3.4.2.2.1 Display of graphic overlays. Encoded graphics shall be displayed along with anyassociated callout overlays designed to indicate the specific components of the graphic.

3.4.2.2.2 Types of graphics. Two types of graphics shall be displayed: static and interactive. Static graphics shall be displayed in full detail in the graphic area provided, with no ability formanipulation. Interactive graphics shall provide the capability for manipulation.

3.4.2.2.3 Scale. Graphics shall be displayed to a scale at least as large as its designatedminimum size so that all essential detail is legible.

3.4.2.2.4 Display. Graphics shall be displayed in an assigned data pane of the displayed window. If a graphic can not be displayed in its entirety and in full detail, it shall be displayed usinginteractive graphic display techniques described in this specification (e.g., scrolling, zooming).

3.4.2.2.5 Selection. The user shall be given the capability to select a point, area, or the entiregraphic by positioning the cursor on or near that point and activating the SELECT function.

MIL-PRF-87268A

28

Selectable regions of a graphic shall be visually distinct and shall not adversely affect theappearance of the graphic. The selection of graphical information shall include, but is not limitedto, the following:

a. Selecting an individual graphic object, such as a part, displayed in a graphic.

b. Selecting a point or rectangular area in a graphic image.

3.4.2.2.6 Manipulation. Graphics designated as scrollable shall have the capability to activateSCROLL, ZOOM, CENTER, or FULL SCREEN functions. These options shall be availablewhenever the graphic exceeds the size of the data pane.

3.4.2.2.6.1 Scroll Functions. When required, the capability shall exist to scroll graphicalinformation through the use of the SCROLL UP, SCROLL DOWN, SCROLL LEFT, and SCROLLRIGHT functions. When the graphic displayed exceeds the size of the data pane, it shall scrolland a visual cue shall be provided (vertical/horizontal scroll bar).

3.4.2.2.6.2 Zoom Functions. The capability shall be provided to enlarge or reduce the displayedgraphical information. Graphic enlargement shall be provided by activating a ZOOM INfunction. Graphic reduction in size shall be provided by activating a ZOOM OUT function. Thesize of the data pane shall not change as a result of using the zoom functions.

3.4.2.2.6.3 Center. The capability to activate a CENTER function shall be provided. TheCENTER function shall relocate the center of a graphic to the point the cursor indicates, withoutscrolling.

3.4.2.2.6.4 Full screen. The capability to enlarge a graphic to the full size of a client area byactivating the FULL SCREEN function, shall exist.

3.4.2.3 Tables. Tabular information shall be displayed as cells of textual information or agraphic. When tables contain textual elements, those elements shall conform to therequirements herein, for textual information. Graphical elements within a table shall conform tothe requirements herein, for graphic material.

3.4.2.3.1 Display of tables. Tables shall be displayed in a left-to-right, top-to-bottom array ofcells. Tables shall have column headers and, if applicable, row headers.

3.4.2.3.1.1 Justification. Lists of alphabetic data shall be vertically aligned with leftjustification. Numerical data shall be justified with respect to a fixed decimal point. In caseswhere there is no decimal point, the numerical data shall be right justified.

3.4.2.3.1.2 Column spacing. Consistent column spacing shall be maintained within a table. When more than one column of data is displayed, sufficient space shall be provided to clearlydistinguish the data.

MIL-PRF-87268A

29

3.4.2.3.1.3 Row spacing. For dense tables with more than ten rows, a grouping feature (i.e., asolid or blank line) shall be inserted after every fifth row.

3.4.2.3.2 Highlighting. The capability to highlight selectable text shall exist within a table.Tables shall display active selections as highlighted areas and the entire highlighted area shallbe sensitive to selection by the pointing device. All selectable areas shall be displayed andvisually highlighted before selection.

3.4.2.3.3 Selection of tables. The capability to select an individual highlighted cell displayed in atable shall be provided.

3.4.2.3.4 Scrolling of tables. The user shall have the capability to manipulate displayed tables byactivating the SCROLL function if the table exceeds the size of the data pane. When a table isscrollable, the table headers shall not scroll within the pane. The capability to scroll tabularinformation a row or column at a time, through the use of the SCROLL UP, SCROLL DOWN,SCROLL LEFT, and SCROLL RIGHT function shall be provided. When the table displayedexceeds the size of the data pane, it shall scroll and a visual cue shall be provided (vertical andhorizontal scroll bars).

3.4.2.4 User prompts/questions. User prompts shall be displayed as dialogs (see 3.4.1.4.5). Prompts shall be used to obtain any information required by the IETM. Prompts shall bepresented as questions.

3.4.2.4.1 Display of user prompts. A standard symbol or layout shall be used with prompts toindicate that an explicit response (e.g., entry) is required. The symbol or layout used shall bereserved only for this purpose. The data entry area shall be displayed in the immediate vicinityof the prompt or question.

3.4.2.4.2 Manipulation of user prompts. When responding to multiple prompts in a singlesection of a procedure, the capability to change a previously entered response to the extent thatthe change does not alter the logic of the procedure shall be provided. When a response ischanged to any given prompt, access to all of the current entries for that prompt shall beprovided.

3.4.2.5 Audio controls. When either verbal or nonverbal audio signals are presented, thecapability to repeat the audio signal shall exist. Audio on-off and volume shall be provided.

3.4.2.6 Video controls. When displaying a motion video sequence, the video sequence shallautomatically begin after the entire screen has been displayed. The capability shall exist toallow pausing, repeating and exiting the video sequence.

3.4.2.7 Motion/animation controls. If displaying an animated graphic, the animation sequenceshall automatically begin after the entire screen has been presented. The capability shall exist toallow pausing, repeating, and exiting the animation sequence.

MIL-PRF-87268A

30

FIGURE 4. Client area components.

3.5 General IETM formatting and user interaction display features. The IETM shall bedisplayed by an EDS which shall have the capability to form displayed windows of information inaccordance with this paragraph and the common user interface requirements in 3.4. In additionthe final IETM shall conform to the applicable special requirements specified in 3.6. The generalformatting and user interaction requirements of the following paragraph shall apply to allIETMs.

3.5.1 General display formats. IETM content shall be displayed according to one of thepresentation templates below. Individual data panes, footer bar (function-designation area),second header line (if required), message area (if required), alerts (warnings, cautions, andnotes), and designation of classified information shall be displayed within the client area (seefigure 4).

3.5.1.1 Window layout templates for data panes. Window components shall be displayed in oneor more data panes within the client area. Data panes shall consist of rectangular displayregions containing information in the form of text, tables, graphics, etc., displayed individually orin combination in the client area. All information shall be displayed in individual data panes andcombined into a full window display in accordance with the window arrangement rules in 3.5.1.2. Divided panes need not be of the same size. Explicit lines shall be drawn between window panes. Upon initial presentation, data panes shall not overlap. No more than four panes shall beallocated, upon initial presentation, within the client area.

MIL-PRF-87268A

31

3.5.1.2 Arrangement of data panes. Windows shall be composed of one or more separate datapanes (see figure 5) and shall be combined or displayed according to the following rules:

a. A window consisting of a single data pane composed of any combination of text,table, or graphics is permitted.

b. A graphic pane shall be large enough to satisfy the minimum size designated for theindividual graphic whenever possible. If the graphic pane is smaller than thatminimum size, the graphic shall be made scrollable and the graphic shall be scaledso that the visible portion of the image appears as large as the designated minimumsize.

c. When displaying one text pane and one graphic pane (or table), the text andassociated graphic shall be kept together in the same window.

d. When displaying one text pane with multiple graphics (or tables), all text andgraphics shall be arranged in one window whenever possible. If all graphics will notfit on a single window, the information shall be broken into a sequence of separatewindows (each with the same text and as many graphics as will fit). There shall notbe more than one user scrollable graphic pane active in a window.

e. Text shall always begin in the upper left most corner of its data pane.

f. When text refers to a graphic, the graphic shall be displayed whenever theassociated text reference is displayed.

g. When the preceding rule will not allow a text pane plus all of the associatedgraphics panes to fit in one window, the set of panes shall be split up into severalseparate windows, each retaining the same text pane with differing graphic panes. The capability to move through the sequence of combined text and graphic windowswithout the relative position or the displayed content of the text pane changing shallbe provided.

h. Appropriate use of "white space" (i.e., space in the color of the background) shall beimplemented so that the eye is guided horizontally or vertically through the window.

I. Margins shall be at least one character width around any image.

3.5.1.3 Footer bar (function designation area). Unless another location within the window isspecified by the procuring activity (see 6.2), the footer bar shall be located at the bottom of thewindow frame within the client area. All active selectable options (i.e., available interactionfunctions) shall be displayed in the footer bar area. Footer information shall be displayed in aregion that is at least two character cell heights tall and as wide as the window. The footer barshall be used in conjunction with the menu bar to display interaction options to the user.

MIL-PRF-87268A

32

FIGURE 5. Examples of window data pane templates.

MIL-PRF-87268A

33

3.5.1.3.1 Support of function keys. The footer bar shall support delivery devices which useprogrammable or dedicated function keys. The footer bar shall provide a cue that particularfunctions are assigned to physical keys and that those keys are active. It shall also supportinterfaces that use the marked region in the footer bar as an active function selection or buttonarea. Active function selection areas of the frame shall only be in the footer bar area, unless adialog box or other active window is superimposed on the frame. Inactive functions for thedisplayed window shall be visually distinguishable from active functions or not displayed.

3.5.1.3.2 Visual prompts. Selectable options shall be indicated using function name, icons,programmable function key labels (e.g., F2), or other visual prompts and shall be enclosed in abox outlined with a visual border (e.g., line, shadowed button image) in the footer bar area. Iconswith no label shall be included without the surrounding border. Visual prompts shall be lined uphorizontally.

3.5.1.3.3 Visual prompt Labels. When a software function is assigned to a particular functionkey, a label containing the hard key function label or the programmable function key number(such as "F8") along with a succinct description of the function shall be displayed in the footer bararea. The same function shall appear in the same region of the footer bar even if thisrequirement calls for blank space to be reserved in the bar when a particular function is notactive.

3.5.1.3.4 Menus. When required, footer bar menus shall be activated from the functiondesignations in the footer bar and shall be attached (e.g., pull-down, pop-up) in accordance withthe formats described in 3.4.1.3.

3.5.1.4 Optional second header line. If specified by the procuring activity (see 6.2), the top linein the client area shall be reserved for additional header information. The format of this lineshall be compatible with the title bar. If the MENU function is used to toggle the title bar, thetoggle shall also apply to the second header line.

3.5.1.5 Optional message area. If specified by the procuring activity (see 6.2), a message areashall be reserved at the bottom of the client area above the footer bar. Requirements formessages to be displayed in this area shall be as specified by the procuring activity.

3.5.1.6 Display requirements for warnings, cautions, and notes. Warnings, cautions, and notesand their associated icons shall be prominently displayed and shall be treated as an alert. Theassociated message shall appear in the approximate middle of the client area. Normal operationof the system shall not resume until the message is acknowledged in accordance with therequirements for an alert. Upon acknowledgment, the alert shall be eliminated and theprocedural information presented. Combinations of warnings, cautions, and notes, shall bedisplayed in that order.

3.5.1.6.1 Color display. Where color is used for display, message colors shall be red for warnings,yellow for cautions, and cyan for notes.

MIL-PRF-87268A

34

FIGURE 6. Warning, Caution, and Note display example.

3.5.1.6.2 Borders. Borders for warnings and cautions shall consist of diagonal bars, alternatingbetween the background color or white, and the designated message color. The appropriate wordidentifying the message type shall appear in capital letters, horizontally and vertically centeredon the upper border (see figure 6).

3.5.1.6.3 Icon and title. One or more icons representing a warning, caution, or note shall appearin the footer bar.

a. Icons for hazardous materials shall be designed and used in accordance with theAerospace Industries Association Service Publications Committee PUBS-119 andMIL-STD-38784, Appendix A.

b. An applicable icon shall remain displayed in the footer bar until the warning,caution, or note message it represents is no longer applicable. The user shall begiven the capability to view the warning, caution, or note in its original appearanceand functionality at any time by selecting the icon.

c. A message title, when applicable, shall be horizontally centered one character cellheight below or to the immediate right of the icon.

MIL-PRF-87268A

35

3.5.1.6.4 Text. Text of warnings, cautions, or notes shall be displayed within the border. Messages containing two or more paragraphs shall have a blank line between paragraphs.

3.5.1.6.5 Danger from several sources. When warnings or cautions exist in separate categoriesfor the same set of technical information, they shall be successively displayed in decreasing orderof severity: Warnings first, followed by cautions. Warnings or cautions in the same categoryshall be successively displayed. However, there shall be no requirement to determine an order ofimportance within the same category. When related warnings or cautions of the same categoryexist for the same block of technical information, it is permissible to group them within acommon border but they shall be visually distinct. In such a case the title shall indicate thecombined danger.

3.5.1.7 Indication of classified information. Whenever classified information is displayed, anindication of the classification level shall be indicated in the footer area (see 3.5.1.3 and figure 4). The indication shall be the upper case spelling of the words corresponding to the classificationlevel (e.g., CONFIDENTIAL). When color is available, these indications shall be displayed witha red background. Classification indications shall be clearly distinguishable from the functionindicators in the same area. Technical data developed using this specification shall have securityclassification markings in accordance with DOD 5220.22-M and 5200.1-R.

3.5.2 User interaction functions. In addition to the common user interface functions previouslydescribed, the presentation system software shall provide, as a minimum, the capability toactivate the set of standard functions for selecting, manipulating, accessing, navigating, andentering data into the system. These functions shall be implemented as required by thepresentation systems (e.g., one presentation device might have dedicated keys for each standardfunction, another may provide software programmable function keys, a third might use apointing device to select the standard functions). The user shall be given the capability to selectand activate all of the standard input functions described herein.

3.5.2.1 Required navigation functions. A comprehensive set of commands to navigate andsequence through the information shall be provided. The minimum set of navigation and controlfunctions available and common to all IETMs shall permit the minimum functionality asdescribed below and in Table III.

3.5.2.1.1 NEXT. The NEXT function shall display the next section or frame of information thatthe user requires, based on context.

3.5.2.1.2 BACK. BACK shall be the opposite of NEXT. The BACK function shall display theprevious module or frame of information. The BACK function shall reset to the previous windowinformation, including all variables and settings. If relevant, a message box shall be presentedexplaining any special circumstances which cannot be reversed by invoking the BACK function.

3.5.2.1.3 BROWSE BACK, BROWSE NEXT, and BROWSE EXIT. These functions shall berequired for all systems for which the NEXT and BACK functions set interactive system

MIL-PRF-87268A

36

Function DescriptionNEXT Action to move forward to the succeeding window

BACK Action to move to the previous window or to review allwindows which led to the current state

BROWSE NEXT Action to move to the succeeding window withoutpermanently setting system variables; however, systemvariables will be set to a temporary state table

BROWSE BACK Action to move to the previous window withoutpermanently resetting system variables; however, systemvariables in the temporary state table will be reset

BROWSE EXIT Action to leave browse mode

RETURN Action to return to window before last branching

CREATE BOOKMARK Action to create a bookmark for the purpose of savingdata for reference

REMOVE BOOKMARK Action to erase a specific bookmark

MODIFY BOOKMARK Action to change the name of a specific bookmark

GO TO BOOKMARK Action to go directly to a specific bookmark

SEARCH Action to find additional data with limited informationavailable

DIRECT ACCESS Action to access information by hierarchy, bookmarks,glossary or index

MORE-DETAIL Action to switch to novice track of information, ifavailable

LESS-DETAIL Action to switch to expert track of information, ifavailable

CROSS REF Action to access related information attached to aselectable item

HELP Action to access help functions

TABLE III. User Navigation Functions.

variables that are used to effect subsequent navigation through the IETM. These navigationfunctions shall act as NEXT and BACK, but shall not set or reset system variables automaticallyor through dialogs. Once either BROWSE BACK or BROWSE NEXT is selected, othernavigation functions shall not be available until the user returns to the originating window byinvoking the BROWSE EXIT function. The presentation system shall provide a distinct visualindication that the system is in browse mode. When either the BROWSE BACK or the BROWSENEXT function is not logical (such as at the beginning of a string or at a mandatory branchpoint), only the complementary BROWSE function shall be active. System

MIL-PRF-87268A

37

variables shall still be set and shall be activated and logged to a temporary state table. It is notnecessary to post system variables to the permanent state table when in browse mode.

3.5.2.1.4 RETURN. The RETURN function shall restore the location prior to branching. Pressing RETURN shall perform an orderly exit from the branched information presentation,resetting all temporary system state information relative to the branched node. If a branch hasnot been previously taken, this function key shall be nonfunctional.

3.5.2.2 Required data access functions. There shall be multiple data access paths provided to theuser including, as a minimum, the following access methods:

3.5.2.2.1 CREATE, REMOVE, MODIFY, and GOTO bookmarks. The capability to markdisplayed information for later recall shall exist. Bookmarks shall be used to recall specificinformation (e.g., a procedure). The capability to view bookmarks shall be provided. There shallbe the capability to name a bookmark with a unique alphanumeric name.

3.5.2.2.2 SEARCH AND DIRECT ACCESS. The SEARCH and DIRECT ACCESS functionsshall enable, but not be limited to, searching for and directly accessing the following IETMinformation by entering search information into a dialog box.

3.5.2.2.2.1 System index. There shall be the capability to access IETM information by using ahierarchical outline or index.

3.5.2.2.2.2 Functional diagrams. There shall be the capability to access IETM informationthrough the use of a functional diagram or graphic. Through the diagram, the capability to movethe cursor to the graphic display of the function of interest and activate the SELECT functionshall be provided.

3.5.2.2.3 MORE DETAIL, LESS DETAIL. If a separately authored track of more or less detailedtechnical information is available (see 3.3.2), the capability to activate the level of detailfunctions within the parameters allowed by the technician's skill level shall exist.

3.5.2.2.4 CROSS REF. The presence of and access to cross reference information shall beprovided. When selected, a new data pane or window shall appear on the display. The capabilityto exit the cross reference and return to the original information displayed shall be accomplishedusing the RETURN function.

3.5.2.2.5 HELP. The system shall provide a help information display function and shall permitaccess to the following help functions and descriptions, as required:

a. Context. Shall provide context sensitive help about the specific situation that existsor the information being displayed on the system when help was requested.

b. How to use help. Help shall include information on how to use the application's helpfacility.

MIL-PRF-87268A

38

c. Window. Shall provide general information about the operation of the window fromwhich the help was requested.

d. Keys. Shall provide information about the function keys and other keyboardfeatures.

e. System. Shall provide help related to use of the computer system being used to viewthe IETM.

f. Index. Shall provide an index with a search capability for all help information.

g. Tutorial. Shall provide access to a tutorial.

h. Glossary. Shall provide the meaning of terms, acronyms, and abbreviationscontained in the IETM.

3.5.2.3 Other functions. If specified by the procuring activity, other system functions shall bemade available (see 6.2).

3.6 Special requirements. The following requirements shall apply, in addition to thosepreviously stated herein, unless otherwise contained in the applicable functional requirements ofthe conventional TM performance specification corresponding to the type of IETM beingdeveloped, (e.g., operation, maintenance) as determined by the procuring activity (see 6.2). Generally, the major types of information covered shall include, but not limited to: procedural(task), fault isolation, parts, and descriptive or narrative text. See definitions in Section 6.

3.6.1 Requirements peculiar to procedural information. Procedural information shall be used toinstruct an end user how to operate, test, or repair a system; or carry out a logistics supportprocedure. Format for tasks and subtasks shall conform to the requirements contained herein.

3.6.1.1 Tasks and subtasks. Each new task or subtask shall begin on a new display. In terms ofcontent, each task shall involve closely related activities. Each subtask shall include all stepsrequired to achieve a specific objective.

3.6.1.2 Title and label requirements. The following title and labeling information shall beassociated with procedural tasks and subtasks. It shall be used primarily for window labelingupon presentation.

3.6.1.2.1 Task title. Wording of the task title shall be identical with the wording used in the taskdescription in the detailed task analysis summary of the system supportability analysis. If nosupportability analysis task title is available, the task title shall conform to the requirements ofMIL-STD-38784, or the requirements herein.

3.6.1.2.2 Subtask title line. A subtask title line, if required, shall consist of an uppercase titleand may have a subtask number (Arabic). If numbered, subtasks shall be numbered

MIL-PRF-87268A

39

sequentially throughout a task. A subtask title shall be structured in the same manner as a tasktitle and uniquely identify the material which it heads.

3.6.1.2.3 Step number. Each step shall be presented as consecutive Arabic numerals. Theapproval of the procuring activity shall be required to use any alternate numbering system (see6.2).

3.6.1.3 Supporting material for tasks. Procedural data shall contain the following information,which shall be displayed before the steps are viewed.

3.6.1.3.1 Procedure applicability statement. Any procedure presented shall specify the equipment model, range, or sequence to which the procedural information applies. When aprocedure to be presented does not apply to all existing models, the applicable equipment modelor model range shall be identified. Such terms as "on later equipment" and "on early serialnumbers" are not acceptable. When a procedure does not apply to all models, the IETM systemshall require entry of the applicable system or equipment model number, serial number, or otherunique system identifier before the task can proceed. If this information has been entered earlierin the use of the IETM (e.g., log-in) and that information is available at the time the procedure ispresented, reentry of the information shall not be required. Such a control shall be based onestablished designations, such as model designation, part number, serial number range, orsimilar means. Indefinite categories such as "early serial numbers" or "some late models" shallnot be used.

3.6.1.3.2 Initial setup. The initial setup or input conditions, where required, shall be provided atthe beginning of every new task (e.g., consumable materials, support equipment). All listsprovided as part of the initial setup shall be headed by individual underlined labels, using uppercase initial letters with successive letters in lower case. Information presentation in eachwindow shall avoid crowding; as many frames shall be used for each initial setup as necessary.

3.6.1.3.3 Safety considerations. Safety conditions shall be identified as specified in MIL-STD-38784 and as stated herein (see 3.2.2).

3.6.1.4 Style requirements. Language (verb tense, person and number) shall comply with therequirements of MIL-STD-38784 and as stated herein (see 3.6). All essential information shall beavailable and readily accessible.

3.6.2 Fault Isolation information. The fundamental logic for interactive fault isolation shall notbe dictated by the IETM presentation system but shall be based on a specifically designedtroubleshooting logic which shall include, but not be limited to, predefined fault isolationsequences and dynamically generated fault isolation recommendations based on system or userinputs and as specified herein (see 3.6).

3.6.2.1 General Requirements. Fault isolation information shall be designed to permit directaccess to the relevant corrective maintenance procedures after a fault has been isolated, unlessotherwise specified by the procuring activity (see 6.2). The capability shall exist to:

MIL-PRF-87268A

40

a. enter symptoms manually by means of symptom codes or human readable text, or byinitiation of automatic retrieval from the system or equipment under observation;

b. enter and change test results when such information is required by thetroubleshooting procedure;

c. confirm conditions required before continuing a maintenance action;

d. review and browse through previous actions and test results;

e. access all troubleshooting information needed to troubleshoot the system in anefficient and clearly defined manner.

3.6.2.2 Predefined fault isolation sequences. Predefined fault isolation sequences shall consist ofa specified sequence of fixed procedures and tests that will isolate the detected fault. Thesepredefined fault isolation sequences are representative of the fixed fault trees in fault isolationmanuals and shall be based on the reporting of an observed symptom, alert, or as a result of aprevious test. The input of the result (or outcome) of a test or an observation shall be requiredbefore displaying information on the next procedure, test, or corrective maintenance action.

3.6.2.2.1 Presentation requirements. Presentation of predefined fault isolation information shallconsist of and be presented as procedural data (see 3.6.1). Procedural steps shall contain testinstructions, observation requirements, and corrective repair actions. Prompts via dialogs shallbe used to initiate actions requiring input.

3.6.2.3 Dynamically generated fault isolation recommendations. Dynamically generated faultisolation recommendations shall be computed, as required, with information received from userinput and/or automated system recording. The fault isolation system shall provide the option toselect a recommended test or repair action to perform that will aid in the fault isolation process. Results from these maintenance actions shall be used to update the status of the currentsituation producing additional recommendations if necessary. Recommended computations shallbe based on a variety of input data including, but not limited to, historical information,heuristics, probability factors, and cost factors such as time or availability. The models fordynamically generated fault isolation recommendations shall be based on a computed processwhich involve one or more automated approaches including, but not limited to: model basedreasoning, dependency models, fault based reasoning, rule based logic, information theory, oradvanced artificial intelligence schema.

3.6.2.3.1 Presentation requirements. Presentation of dynamic fault isolation information shallbe interactively displayed. Dynamic fault isolation of a system shall be depicted in somerepresentative form (e.g., functional block diagram, connectivity block diagram, or iconic form). Depictions shall convey information about current components under investigation and thedetected faults. Interaction with the depictions shall obtain additional information such as, butnot limited to, lower levels of system detail, theory of operation, supply status, associatedgraphics, and part information. Presentation of system information shall be hierarchical in

MIL-PRF-87268A

41

nature. It shall include automated access to additional system wide information including, butnot be limited to, block diagrams of all subsystems and the complete set of test and repairprocedures, symptoms, and parts. The information presentation shall not be limited to a singleset of troubleshooting recommendations but shall include user options for viewing a variety oftroubleshooting information such as a best test or best repair list, previous actions performedduring the troubleshooting process, test results, and block diagrams.

3.6.3 Presentation of parts information. A data base of supporting parts information (similar toa conventional Illustrated Parts Breakdown (IPB) or Repair Parts and Special Tools List(RPSTL)) shall be incorporated. In general, the IETM shall have the capability of accessing partsinformation to: permit unambiguous identification of all replaceable or reparable partsauthorized at the current level of maintenance; show precisely the physical relationship of thispart to other parts of the system; and provide all data required to order the part through the useof an automatically prepared parts ordering form. Each part shall be presented using linegraphics showing the physical relationship of the part to the adjacent equipment.

3.6.3.1 Availability. Parts information shall be made available at the point in the presentationin which a specific part is identified including, but not limited to:

a. a locator diagram;

b. parts shown on any logic flow diagram or circuit diagram;

c. parts cited in the text of the technical information;

d. a dialog prompt for parts related information;

e. any citation using a part designation in any of its available forms.

3.6.3.2 Direct access. Parts data shall be accessible by direct entry of applicable partidentification or numbering systems (e.g., stock number, part name, system/subsystem/sub-subsystem (subject) number (SSSN), reference designator).

3.6.4 Descriptive information. Narrative text shall be used to assist in the comprehension ofprocedural data.

4. VERIFICATION

4.1 Verification. Unless otherwise specified in the contract or purchase order:

a. Validity of the accuracy and scope of the IETM technical content, user interfacefunctionality and EDS-IETM interface shall be the responsibility of the contractor(see 6.6.16).

MIL-PRF-87268A

42

b. The contractor shall provide suitable facilities to perform the validation functionsspecified herein.

c. The contractor's existing quality assurance (QA) procedures shall be used.

d. The government reserves the right to review any of the verifications when suchreviews are deemed necessary to ensure supplies and services conform to theprescribed contractual requirements.

4.1.1 Minimum Verification Requirements. As a minimum, verification shall ensure thefollowing:

a. Suitability of the IETM for the intended user environment.

b. Usability by the intended user.

c. IETM to EDS compatibility.

d. Compatibility with other Government systems.

4.1.2 Compliance. All IETMs shall meet all requirements of Sections 3 and 5 of thisspecification. The requirements set forth in this specification shall become a part of thecontractor's overall inspection or quality program. The absence of any requirement in thisspecification shall not relieve the contractor of the responsibility of ensuring that all products orsupplies submitted to the Government for acceptance comply with all requirements of thecontract. Use of sampling inspections shall be in accordance with commercially acceptablequality assurance procedures; however, Government approval for use of sampling in QAprocedures does not authorize submission of known defective material, either indicated or actual,nor does it commit the Government to accept defective material.

5. PACKAGING

5.1 Packaging. For acquisition purposes, the packaging requirements shall be as specified in thecontract or order (see 6.2). When the actual packaging of material is to be performed by DoDpersonnel, these personnel need to contact the responsible packaging activity to ascertainrequisite packaging requirements. Packaging requirements are maintained by the InventoryControl Point's packaging activity within the Military Department's System Command. Packaging data retrieval is available from the Military Department's or Defense Agency'sautomated packaging files, CD-ROM products, or the responsible packaging activity.

5.1.1 Encoded computer products. Packaging of encoded computer products, in preparation fordelivery, shall be in accordance with the requirements of MIL-STD-1840.

5.1.2 Classified material. Classified material shall be packaged and identified in accordancewith DOD 5200.1-R, DOD 5220.22-M, and the implementing Service regulations.

MIL-PRF-87268A

43

6. NOTES

(This section contains information of a general or explanatory nature that may be helpful, but isnot mandatory.)

6.1 Intended use. This specification is intended to be cited in a procurement in which theGovernment acquires IETMs. This specification describes the general requirements the authormust follow concerning the creation and selection of general content, style, format and userinteraction features of the IETM. However, this specification is intended to be implemented incombination with the specific style guides and detailed requirements specifications of individualend item IETMs (e.g., an IETM for a specific functional area or a specific weapon system). Thesedocuments in turn reference this specification for the general IETM requirements which arecommon to the differing functional end item IETMs. This specification is not a complete enditem specification in itself. Specific requirements for the type of IETM under development arefound in the associated performance specification identified in the contract Statement of Work(SOW) for the corresponding conventional technical manual (TM) functionality. This specification applies to all levels of maintenance.

6.1.1 Interaction of the IETM and the EDS. An IETM must be constructed to be fully compatiblewith the operating and presentation software of an EDS, and must be presented on such adisplay device before any actual use, testing, or evaluation of operational suitability can takeplace (i.e., using the Government specified end user IETM display device). In this sense anIETM does not exist without its corresponding EDS, and, each formatting and user interactionrequirement cited in this specification should have a corresponding software section in theassociated EDS design specification.

6.2 Acquisition requirements. Acquisition documents must specify:

a. Title, number, and date of the specification.

b. Issue of the DODISS to be cited in the solicitation, and if required, the specific issueof individual documents referenced (see 2.2.1, 2.3).

c. End user skill level to which the IETM is to be developed (see 3.3.1).

d. If procedures within steps will be other than as specified herein (see 3.3.1).

e. If a separately developed higher skill level track will be used, and, if the noviceuser will be prohibited from accessing the higher skill level track (see 3.3.2).

f. Approved shortened identifiers for nomenclatures (i.e., acronyms) used forequipment item assemblies, parts, etc. (see 3.3.4.3).

MIL-PRF-87268A

44

g. If conversion of U.S. standards of measurement to metric standards ofmeasurement is to be included (see 3.3.4.5b.).

h. A "permitted word" list(s), when required (see 3.3.4.7).

i. The least capable device to be supported by the IETM (see 3.3.5).

j. If nomenclature used in graphics is to be other than as specified herein (see3.3.5.7).

k. How the human figures used in graphics are to be clothed (e.g., Enlisted workinguniform for a particular Service) (see 3.3.5.9).

l. If wire lists, schematics, and wiring diagrams referenced by an associated text panewill be other than as specified herein (see 3.3.5.12).

m. If locator graphics will be optional or part of the procedural or descriptiveinformation (see 3.3.5.14).

n. If additional user interface components other than described in this specification isto be implemented (see 3.4.1).

o. If a single window device will be used (see 3.4.1.2).

p. If the additional window controls (i.e., window resize, relocation, and menu button)are required (see 3.4.1.2.4.2).

q. The reference viewing distance, if other than as specified herein (see 3.4.2.1.1.1).

r. If the footer bar location is to be other than as specified herein (see 3.5.1.3)

s. If the top line in the client area is to be reserved for additional header informationand any requirements for information displayed on that line (see 3.5.1.4).

t. If an area is to be reserved on the display window for the message area and anyparticular requirements for that message area (see 3.5.1.5).

u. If other system functions are required. (see 3.5.2.3).

v. What special requirements for procedural data, fault isolation, and partsinformation are required according to the applicable functional requirements of theconventional TM performance specification corresponding to the type of IETMbeing developed (see 3.6).

w. If step numbering is to be other than as specified herein (see 3.6.1.2.3).

MIL-PRF-87268A

45

x. If content requirements for troubleshooting information are other than as specifiedherein (see 3.6.2.1).

y. If packaging other than as specified herein is required (see 5.1).

6.3 Technical Manuals. The requirement for technical manuals should be considered when thisspecification is applied on a contract. If technical manuals are required, specifications andstandards that have been cleared and listed in DoD 5010.12-L, Acquisition Management Systemsand Data Requirements List (AMSDL) must be listed on a separate Contract Data RequirementsList (CDRL), DD Form 1423, which is included as an exhibit to the contract. The technicalmanuals must be acquired under separate contract line item in the contract.

6.4 Requirements covered by this specification. This specification covers general requirementsfor IETMs as outlined below and presented in Section 3.

6.4.1 General content. General content requirements common to IETMs are covered in 3.1, 3.2,and portions of 3.6. Specifically, 3.1 applies to the standard revisable data base items specified inMIL-PRF-87269 which, in turn, are used to create the IETM; 3.2 applies to all IETMs whetheror not they used MIL-PRF-87269 to specify the source data base; and, 3.6 includes contentrequirements which are peculiar to certain subsets of IETMs such as troubleshooting IETMs orproceduralized maintenance instructions. Content statements applying to the IETM areclassified into two types:

a. Those applicable to construction of the IETM such as those dealing with the IETMtechnical structure and those required to support the use of a particular IETM (e.g.,Help information).

b. Those applicable to specific technical processes to assure effective use of the IETMfor the logistic support purpose intended.

6.4.1.1 Content structure and supporting information. Common content requirements for IETMstructure require the incorporation of features such as front (introductory) matter, list ofcontents, glossary, list of acronyms, statement of applicability, IETM number, IETM date, IETMedition, and many others.

6.4.1.2 Content related to technical functions. Standardized increments of technical content areneeded to ensure that the information presented in support of a given process is complete,comprehensible, and effective, e.g., the requirement that location drawings be incorporated toassist the user in remove and replace procedures, or the requirement that setup information beincorporated for all system related procedural information. Similarly, content requirements suchas standardized requirements for parts information will be detailed under this category. Most ofthe requirements in this category are included in 3.6. The applicable functional requirements ofthe conventional TM performance specification corresponding to the type of IETM beingdeveloped must be used to determine the look and feel of the IETM within the

MIL-PRF-87268A

46

context of the EDS and end user requirements, (e.g., Work Package TMs (MIL-PRF-87929) havespecific work package and subwork package requirements for task preparation, accomplishmentand completion).

6.4.2 General style. Style requirements are presented in 3.3. The term "style" refers to:

a. The nature of the language structure (grammar and syntax) used; the vocabulary;and criteria governing technical terminology, numbers, and abbreviations.

b. The presentation related aspects of text, graphics, and audio information (e.g.,graphics design, callout construction, and use restrictions on audio tones).

6.4.3 General format. Format requirements deal with all aspects of the arrangement(organization) of text and graphics information for screen presentation, and with the sequencing(ordering) of frames for interactive presentation within an increment of technical information. General format requirements of the IETM user interface are contained in 3.5 of this specification.

6.4.4 General user interaction. User interaction capabilities required for interactivepresentation of IETMs (requirements which, as noted, must be reflected in the EDS) arecontained in 3.4 and 3.5. The specific functions defined in these paragraphs are:

a. Those user-interaction functions needed to control a screen display (e.g., windowingcontrols, cursor control, scrolling). (see 3.4, and Table I)

b. Those functions necessary for user-interaction and information display with theIETM. (e.g., HELP, NEXT, BACK). (see 3.5 and 3.5.2.1, Table III)

6.5 Acquisition of IETMs. To acquire the IETMs described herein, this specification must belisted in the appropriate Service's Technical Manual Contact Requirement (TMCR). The TMCRmust also include or list any other detailed IETM requirements needed to supplement thisgeneral specification (applicable tailored performance specification functional requirements). The TMCR should be listed in the Contract Data Requirements List (DD Form 1423).

6.6 Definitions of acronyms and terms. Acronyms and IETM terms are included below.

6.6.1 Acronyms.

a. AIA - Aerospace Industries Associationb. American National Standards Institute (ANSI)c. AMSC - Acquisition Management System Control (number)d. AMSDL - Acquisition Management Systems and Data Requirements Liste. ANSI - American National Standards Institutef. CDRL - Contract Data Requirements Listg. DODISS - Department of Defense Index of Specifications and Standardsh. EDS - Electronic Display System

MIL-PRF-87268A

47

i. Hz - Hertzj. IETM - Interactive Electronic Technical Manualk. IETMDB - IETM Data Basel. IPB - Illustrated Parts Breakdown m. ISO - International Organization of Standardsn. OSHA - Occupational Safety and Health Acto. RPSTL - Repair Parts and Special Tools Listp. QA - Quality Assurance

q. SSSN - System/Subsystem/Sub-subsystem (Subject) Number r. TMCR - Technical Manual Contract Requirements

s. VDC - Volts Direct Current

6.6.2 Alert. An Alert is any message, communication, notice, or output which requires manualacknowledgment.

6.6.3 Caution. A Caution is a short message which calls attention to an essential operating ormaintenance procedure, practice, condition, statement, etc., which, if not strictly observed, couldresult in damage to, or destruction of equipment or loss of mission effectiveness. (See MIL-STD-38784)

6.6.4 Confirming events. Confirming events are indications that are not necessarily steps of thetask or subtask itself, but are necessary to provide assurance that the task has been performedcorrectly. They confirm the correctness of the technician's actions and confirm that theequipment is operating properly.

6.6.5 Corresponding functionality. IETMs performing the same functional requirements asconventional (paper) TM should provide the same functionality designed into or specified in theapplicable performance specification for the corresponding type of conventional TM beingdeveloped, (e.g., an IETM in lieu of MIL-PRF-87929 Work Packages).

6.6.6 Data pane. A data pane is a rectangular region within the client area containing thedisplayable image of a single data type.

6.6.7 Descriptive information. Descriptive Information is technical information typicallycontained in a technical manual that provides an end user with the background, theory ofoperation, and other supporting information necessary for the performance of maintenance,operation of the system or equipment, and the training and logistic support for that system orequipment. Descriptive information is non-procedural and generally supplemental, to assist theuser in the comprehension of procedural data. Examples of descriptive information includetheory of operation, diagrams, and general knowledge.

6.6.8 Dynamically generated fault isolation recommendations. Dynamically generated faultisolation recommendations are computed, as required, with information gained from user and/orsystem outputs.

MIL-PRF-87268A

48

6.6.9 Element Links. Element links are explicit associations between two bodies of informationthat allow a user to branch from the immediate technical information to other relatedinformation. The first of two types provide for a one-to-one direct relationship between twopieces of information. The second type allows relationships to exist between several pieces ofinformation. The links are not restricted to any one data type. They are available for use withall data elements.

6.6.10 Fault isolation technical data. Fault isolation technical data designed to permittroubleshooting in corrective maintenance. Troubleshooting or fault isolation technical data is aspecial type of procedural technical data (differing primarily in the interactivity involvedbetween display device and technician, and in the presence of extensive branching in the logic). The conventional TM performance specification corresponding to the type of IETM beingdeveloped should be consulted for the applicable functional requirements.

6.6.11 Graphic overlays. Graphic overlays are hierarchical and logically grouped graphicsspecifically designated to visually overlay a master graphic and one another. On a displaysystem they are combined and displayed as one picture.

6.6.12 Interactive Electronic Technical Manual (IETM). A technical manual, prepared(authored) in digital form on a suitable medium, by means of an automated authoring system;designed for electronic window display to an end user, and possessing the following threecharacteristics:

a. The format and style of the presented information are optimized for windowpresentation to assure maximum comprehension; that is, the presentation formatis "frame oriented", not "page oriented".

b. The elements of technical data constituting the IETM are so interrelated that auser's access to the required information is facilitated to the greatest extentpossible, and is achievable by a variety of paths.

c. The computer controlled IETM display device can function interactively (as a resultof user requests and information input) in providing procedural guidance,navigational directions, supplemental information, and in providing assistance incarrying out logistic support functions supplemental to maintenance.

6.6.13 Locator Graphic. Locator graphics enable the user to find the specific hardware items(e.g., part, switch, control, indicator, assembly, etc.) referred to in the text. A locator graphicillustrates a particular item and its relationship to the immediate surroundings.

6.6.14 Note. A note is a short message which describes an unusual procedure or condition towhich special attention must be paid for any reason (but it may not replace a caution orwarning).

6.6.15 Predefined fault isolation sequences. Predefined fault isolation sequences arerepresentative of the fixed fault trees in fault isolation manuals. Based on an observed symptom,the user will proceed through a specified sequence of procedures and tests that will eventuallylead to the suspected fault.

MIL-PRF-87268A

49/50

6.6.16 Verification. Verification (Section 4), in the context of this specification equates to thecontractor's quality assurance program for validating the content of the IETM. Suggestedvalidation methods include:

a. Actual performance. Using production configured equipment, hands-onperformance of the procedure using the technical instructions displayed as written.

b. Simulation. Using production configured equipment and the technical manualprocedure, simulate the actions required by comparing the task steps to thehardware, while not actually removing any equipment.

c. Table top analysis. Primarily for non-procedural data, compare the technicalcontent to source data to ensure the technical accuracy and depth of coverage.

6.6.17 Warning. A warning is a short message which calls attention to an essential operating ormaintenance procedure, practice, condition, statement, etc., which, if not strictly observed, couldresult in injury to, or death of personnel or long term health hazards.

6.7 Subject term (key word) listing.

Data BaseDialogElectronic Display SystemIETMTechnical Manual, Interactive ElectronicUser InterfaceWindow

6.8 Changes from previous issue. Marginal notations are not used in this revision to identifychanges with respect to the previous issue due to the extent of the changes.

MIL-PRF-87268A

INDEX

PARAGRAPH PAGE

51

Abbreviations (General) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.2.1.7 7(Style) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3.4.4 11

Acquisition of IETMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.5 46Acquisition Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.2 43Acronyms (General) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.2.1.7 7

(Nomenclature) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3.4.3 11(Audio) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3.6.2.2 16(Choice Dialogs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.4.1.4.5 24(HELP Function) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.5.2.2.5h 38(Acquisition Requirements) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.2f 43(Content) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.4.1.1 45(Definition) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.6.1 46

Administrative Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.2.1.1 5Alert (General) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3.6.1.1 15

(Dialogs and Controls) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.4.1.4 22(Dialogs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.4.1.4.4 24(Display) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.5.1 30(Warnings, Cautions, and Notes) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.5.1.6 33(Definition) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.6.2 47

Angle of View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3.5.8 13Animated Information (Style) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3.5.16 15Applicable Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 2Applicability Statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.2.1.2 6Applicability (Service Specific) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.2 1Arrangement of Data Panes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.5.1.2 31Audio Controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.4.2.5 29

Callouts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3.5.15 14Cautions (Alert) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.2.2.4 8

(Definition) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.6.3 47Classified Information (Indicated) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.5.1.7 35

(Packaging) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.1.2 42Common User Interface Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.4.1 16Common User Interface (General) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.4 16Comprehensibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3.3 9Computer Generated or Electronically Stored Speech . . . . . . . . . . . . . . . . . . . . . . 3.3.6.2 16Confirming Events (Definition) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.6.4 47Content Related to Technical Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.4.1.2 45

MIL-PRF-87268A

INDEX

PARAGRAPH PAGE

52

Content Requirements for the IETM Data Base, General . . . . . . . . . . . . . . . . . . . . . . 3.1 3Content Structure and Supporting Information . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.4.1.1 45Context . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1.6 4Cursor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.4.1.1 17

Danger From Multiple Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.2.3 8Data Access Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.5.2.2 37Data Pane (Definition) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.6.6 47Definitions of Acronyms and Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.6 46Definitions of Acronyms and Unusual Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.2.1.7 7Delivery (Preparation) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.1 42Descriptive Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.6.4 41

(Definition) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.6.7 47Dialogs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1.4 4Dialogs and Dialog Controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.4.1.4 22Direct Access of Parts Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.6.3.2 41Display Formats (General) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.5.1 30Display Formatting and User Interaction Requirements . . . . . . . . . . . . . . . . . . . . . 3.4.2 25Display Requirements for Warnings, Cautions and Notes . . . . . . . . . . . . . . . . . . . 3.5.1.6 33Drawings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3.5.11 13

EDS and IETM Interaction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.1.1 43Element Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1.5 4

(Definition) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.6.9 48

Fault Isolation Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.6.2 39Fault Isolation Recommendations (Dynamically Generated) . . . . . . . . . . . . . . . . 3.6.2.3 40

(Definition) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.6.8 47Fault Isolation Sequences (Predefined) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.6.2.2 40

(Definition) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.6.15 48Fault Isolation Technical Data (Definition) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.6.10 48Footer bar (Function Designation Area) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.5.1.3 31Format (General) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.4.3 46Functional Flow Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3.5.13 14Functions (Other) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.5.2.3 38

MIL-PRF-87268A

INDEX

PARAGRAPH PAGE

53

General Content Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.4.1 45General Content Requirements Related to IETMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.2 5General Style . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6.4.2 46Government Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2 2Graphic Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3.5.1 12Graphic Density . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3.5.3 12Graphic Overlays (Definition) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.6.11 48Graphics (General) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1.3 4

(Display) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.4.2.2 27(Locator) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3.5.14 14(Quality) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3.5.4 12

Hazardous Material Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.2.5 8Header Line (Optional Second) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.5.1.4 33Health Hazard Precaution Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.2.4 8Help (Technical Content) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.2.1 5

(How to Use) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.2.1.5 6Human Figure (Use) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3.5.9 13

IETM Formatting and User Interaction Display (General) . . . . . . . . . . . . . . . . . . . . . . 3.5 30Instructions for Interactions With IETM Utility Functions . . . . . . . . . . . . . . . . . . 3.2.1.6 6Intended Use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.1 43Interaction of the IETM and the EDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.1.1 43Interactive Electronic Technical Manual (IETM) (Definition) . . . . . . . . . . . . . . . . 6.6.12 48Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.2.1.3 6

Key Word Listing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.7 49

Language Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3.4.1 10Layout Templates (Data Panes) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.5.1.1 30Level of Detail (General) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3.1 8

(Graphics) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3.5.5 13Links to Reduce Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1.5.1 4List of Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.2.1.4 6Location Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1.5.2 4Measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3.5.6 13Menu System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.4.1.3 21Message Area, Optional . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.5.1.5 33

MIL-PRF-87268A

INDEX

PARAGRAPH PAGE

54

Minimum Size for Graphics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3.5.2 12Motion/Animation Controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.4.2.7 29

Navigation Functions (Required) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.5.2.1 35Nomenclature ((General) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3.4.3 11

(Panel) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3.5.7 13Non-Government Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.3 3Nonverbal Auditory Tones (Requirements) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3.6.1 15Note (Definition) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.6.14 48Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 43

Order of Precedence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.4 3Other Government Documents (Drawings and Publications) . . . . . . . . . . . . . . . . . . 2.2.2 2

Packaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 42Panel Nomenclature (Textual Citations) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3.5.7 13Parts Information (Presentation) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.6.3 41Procedural Information (Peculiar Requirements) . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.6.1 38Procedural Information (Style Requirements) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.6.1.4 39Prompts/Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.4.2.4 29

Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 3Requirements Covered By This Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.2 43

Safety Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.2.2.1 7Schematics and Wiring Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3.5.12 13Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 1Skill Level Tracks (Multiple) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3.2 9Special Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.6 38Specifications, Standards and Handbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2.1 2Style Requirements (General IETM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3 8

(General Audio Information) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3.6 15(General Fault Isolation) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.6.2.1 39(General Graphics) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3.5 12(General Text) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3.4 10

Supporting Material for Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.6.1.4 39

MIL-PRF-87268A

INDEX

PARAGRAPH PAGE

55/56

Tables (General) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1.2 4(Display) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.4.2.3 28

Task and Subtasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.6.1.1 38Technical Information (Amount) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3.4.2 11Text (General) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1.1 3

(Display) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.4.2.1 25Title and Label Requirements for Procedural Information . . . . . . . . . . . . . . . . . . . 3.6.1.2 38Tolerances (General) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3.4.6 12

(Numerical) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3.5.6 13Types of Graphics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3.5.10 13

Unit of Measure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3.4.5 11User Interaction Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.5.2 35User Interaction (General) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.4.4 46User Prompts/Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.4.2.4 29

Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 41Video Controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.4.2.6 29Vocabulary (Permitted Words) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3.4.7 12

Warning(s) (General) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.2.2 7(Definition) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.6.17 49

Warnings, Cautions, and Notes (Placement) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.2.2.4 8(Display Requirements) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.5.1.6 33

Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.4.1.2 18

CONCLUDING MATERIALCustodians: Preparing Activity:

Air Force - 16 Air Force - 16Army - TM (Project 0312)Navy - AS

Review Activities:Air Force - 11, 13, 19, 30, 70, 71, 80, 82, 84, 99Army - AL, AR, AT, AV, CR, EA, MI, TM, SC, PTNavy - AS, EC, MC, SA, SH, TD, YD

4. NATURE OF CHANGE (Identify paragraph number and include proposed rewrite, if possible. Attach extra sheets as needed.)

STANDARDIZATION DOCUMENT IMPROVEMENT PROPOSAL

INSTRUCTIONSThe preparing activity must complete blocks 1, 2, 3, and 8. In block 1, both the document number and revisionletter should be given.The submitter of this form must complete blocks 4, 5, 6, and 7.The preparing activity must provide a reply within 30 days from receipt of the form.

1.

2.3.

NOTE: This form may not be used to request copies of documents, nor to request waivers, or clarification ofrequirements on current contracts. Comments submitted on this form do not constitute or imply authorization towaiver any portion of the referenced document(s) or to amend contractual requirements.

I RECOMMEND A CHANGE: 1. DOCUMENT NUMBERMIL-PRF-87268A

2. DOCUMENT DATE (YYMMDD) 95/10/01

3. DOCUMENT TITLEManuals, Interactive Electronic Technical - General Content, Style, Format, and User-Interactive Requirements

5. REASON FOR RECOMMENDATION

6. SUBMITTERa. NAME (Last, First, Middle Initial) b. ORGANIZATION

c. ADDRESS (include Zip Code) d. TELEPHONE (Include Area Code)(1) Commercial (2) AUTOVON (If applicable)

e. DATE SUBMITTED (YYMMDD)

8. PREPARING ACTIVITYa. NAME

Steven C. Hollowayb. TELEPHONE (Include Area Code)

(1) Commercial (2) AUTOVON

(937) 257-3085 787-3085c. ADDRESS (Include Zip Code)

MSG/MMF4375 Chidlaw Rd., Suite S008Wright Patterson AFB OH 45433-5006

IF YOU DO NOT RECEIVE A REPLY WITHIN 45 DAYS, CONTACT:Defense Quality and Standardization Office5203 Leesburg Pike, Suite 1403, Falls Church, VA 22041-3466Telephone (703) 756-2340 AUTOVON 289-2340

DD FORM 1426, OCT 89 (EF-V1) (PerFORM PRO) PREVIOUS EDITIONS ARE OBSOLETE.