Browse Prior Art Database

MAID (Maintenance Aid) MDI (Map Diagnostic Integration)

IP.com Disclosure Number: IPCOM000080185D
Original Publication Date: 1973-Nov-01
Included in the Prior Art Database: 2005-Feb-27

Publishing Venue

IBM

Related People

Romanenko, B: AUTHOR [+3]

Abstract

MAID is an automated method for designing, developing, evaluating, and documenting an Integrated Maintenance Package (IMP) for a system. It is a tool which can be applied during all stages of system development to design diagnosability into the system, as represented in Fig. 1.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 22% of the total text.

Page 1 of 16

MAID (Maintenance Aid) MDI (Map Diagnostic Integration)

MAID is an automated method for designing, developing, evaluating, and documenting an Integrated Maintenance Package (IMP) for a system. It is a tool which can be applied during all stages of system development to design diagnosability into the system, as represented in Fig. 1.

MAID will automatically generate release format Maintenance Analysis Procedure (MAP) charts and MAP Diagnostic Integration (MDI) programs. The MAPs are generated in a two column text format. The generated MDI program contains the logic flow and messages of the MAP chart translated into "rules". These "rules" are used by a supervisor program to determine the logic flow of the test modules.

MAID Language.

The source level of MAID input, MAID language, relates directly to the basic language of the Maintainability Engineer: -definition of indicators

-definition of failures

-description of failures in terms of the indicators (system failure indications).

By using MAID language the time, burden, and complexity of the tasks in designing, generating, and evaluating the System Integrated Maintenance Packnge (IMP) is simplified.

MAID language is divided into three areas of input parameters. They are:
A. INDICAT0R OR AID.

The means of indicating or detecting a failure.

1. Mechanically: heat, friction, markings, etc.

2. Electronically: sense bits

3. Program: diagnostic program halts or indications

4. Visual: panel lights

5. Statement: a fact, a phenomenon, etc.

6. Program logic: a decision block, an entry point.
B. FAILURE OR FRU (Field Replaceable Unit)

Any antifunction or phenomenon described by indicators/aids.

1. An actual failure: logic card bad, pulley broken, function not performed

2. An aid: panel light

3. A symptom: card not fed, `SIO' instruction not executed

4. A statement: a fact, a phenomenon

5. Program logic: function or failure being traced.
C. RELATIONSHIP

The description of Failures/FRUs in terms of Indicators/AIDs.

1. The grouping of one or more indicators to describe a Failure/FRU.

2. The relationship between the indicators and each Failure/FRU.

3. Program logic: the patch traced, from beginning to end, for the function or failure under consideration. MAID Logic, General Description

1

Page 2 of 16

(Image Omitted)

After the program has completed the generation of the cross-reference table, the sorted cross-reference table looks like this in core storage:

Unless a specific order of Indicators is entered by the $ORDER option, the program will determine and choose the Indicator or Aid which `splits' the remaining Failures. Then, the logic of generating the `MAP' and MDI program logic from this table can be expressed as: 001 AID A3 Present?

For MDI use, nodes 1,2,3 6 9 10 and 13 are `rules' and nodes 4,5,7,8,11,12,14, and 15 are `terminations'.

The program is capable of:
1. Counting the usage of each Indicator.
2. Identifying Failures which have been defined but have not been referenced.
3. Grouping...