Хорошев / ИЛП_материал_маг_02.15 / Спецификация AECMA Specification 2000M / MIL-STD-1388-2B

MIL-STD-1388-2B

APPENDIX A

FIGURE 6. B table relationships.

41

MIL-STD-1388-2B

60.2 Table BB. Reliability, Availability, and Maintainability Characteristics Narrative. This table may be used to identify RAM Item Functions, MM Maintenance Concepts, RAM Minimum Equipment List, and RAM Qualitative and Quantitative Maintainability Requirements. Table keys consist of EIAC (EIACODXA), LCN (LSACONXB), ALC (ALTLCNXB), LCN Type (LCNTYPXB), RAM Characteristics Narrative Code (RAMCNABB), and RAM Narrative Text Sequencing Code (TEXSEQBB). For a given row of information, the following cross-element edits apply to table BE:

a.If the RAM Characteristics Narrative Code (RAMCNABB) is (A), then this table identifies the function, specification, and tolerances of the item under analysis (RAM Item Function, DED 180).

b.If the RAM Characteristics Narrative Code (RAMCNABB) is (B), then this table describes the broad, planned approach to be employed in sustaining the

c. If the RAM Characteristics Narrative Code (RAMCNABB) is (C), then this table specifies any limitations on the end item when dispatched on its assigned mission with the item under analysis inoperative (RAM Minimum Equipment List Narrative, DED 244). RAM Minimum Equipment List Narrative (MEQLNABB) is not allowed without a (y) selected in table BA for the attribute RAM Minimum Equipment List Indicator (MEQLINBA).

d. If the RAM Characteristics Narrative Code (RAMCNABB) is (D), then this table describes the maintainability design constraints and characteristics that must be considered during the design process, to include fail safe requirements, environmental considerations, and nuclear hardened characteristics (RAM Qualitative and Quantitative Maintainability Requirements, DED 315).

e. If the RAM Characteristics Narrative Code (RAMCNABB) is (E), then this table describes the support data and analysis used in preparation of the maintenance plan (Maintenance Plan Rationale, DED 210).

-43-

MIL-STD-1388-2B

APPENDIX A

blank, or have entries.

g.Mean Time Between Maintenance Induced (INMTBMBD) and Mean Time Between

Maintenance Induced MB (IMTBMMBD) must either both be blank, or have entries.

h.Mean Time Between Maintenance Inherent (INHMTBBD) and Mean Time Between Maintenance Inherent MB (INHMTMBD) must either both be blank, or have entries.

i.Mean Time Between Maintenance No Defect (NOMTBMBD) and Mean Time Between Maintenance No Defect MB (NMTBMMBD) must either both be blank, or have entries.

j.Mean Time Between Preventive Maintenance (MTBMPVBD) and Mean Time Between Preventive Maintenance MB (MTBMPMBD) must either both be blank, or have entries.

k.Mean Time Between Removals (MTBRXXBD) and Mean Time Between Removals

MB (MTBRMBBD) must either both be blank, or have entries.

l. Achieved Availability shall be calculated based on Mean Time Between Failure Technical (Table BD), Mean Time Between Maintenance - No Defect (Table BD), Mean Time Between Preventive Maintenance (Table BD), Elapsed Time (Table CA) , and Task Frequency (CA). A change in any of these variables shall result in an update of the Acheived Availability (Table BD).

m.Inherent Availability shall be calculated based on Mean Time Between

-45-

MIL-STD-1388-2B

a. Engineering Failure Mode Mean Time Between Failure (EFMTBFBF) and Engineering Failure Mode Mean Time Between Failure MB (EFMMMBBF) must either

both be blank, or have entries.

b. Engineering Failure Mode Mean Time Between Failure shall be calculated based on Failure Mode Ratio (Table BF) and Part Failure Rate (Table BD). A change in any of these variables shall result in an update of the Engineering Fail&e Mode-Mean Time Between Failure (Table BF).

- 47 -

60.7 Table BG. Failure Mode and Reliability Centered Maintenance Narrative. This table may be used to identify Failure/Damage Mode Effect End Effect, Failure/Damage Mode Effect Local, Failure/Damage Mode Effect Next Higher, Failure Cause, Failure/Damage Mode, Failure Mode Detection Method, Failure Mode Predictability, Failure Mode Remarks, Reliability Centered Maintenance (RCM) Redesign Recommendations, and RCM Reasoning. Table keys consist of EIAC (EIACODXA), LCN (LSACONXB), ALC (ALTLCNXB), LCN Type (LCNTYPXB), Failure Mode Indicator (FAMOINBF), Failure Mode Narrative Code (FMNCNABG), and Failure Mode Narrative Text Sequencing Code (TEXSEQBG). For a given row of information, the following cross-element edits apply to table BG:

a.If the Failure Mode and RCM Narrative Code (FMNCNABG) is (A), then this table describes the consequences of each failure/damage mode end effect on the item operation, function, or status (Failure/Damage Mode Effect End Effect, DED 125).

b.If the Failure Mode and RCM Narrative Code (FMNCNABG) is (B), then this table describes the consequences of each failure/damage mode effect local on the item operation, function, or status (Failure/Damage Mode Effect Local, DED 126).

c.If the Failure Mode and RCM Narrative Code (FMNCNABG) is (C), then this table describes the consequences of each failure/damage mode effect next higher on the item operation, function, or status (Failure/Damage Mode Effect Next Higher, DED 127).

d.If the Failure Mode and RCM Narrative Code (FMNCNABG) is (D), then this table describes all possible failure causes postulated on the basis of

the stated requirements in the system and failure definitions. All probable independent causes for each failure shall also be identified.

(Failure Cause, DED 124).

e. If the Failure Mode and RCM Narrative Code (FMNCNABG) is (E), then this table describes all possible failure/damage mode postulated on the basis of the stated requirements in the system and failure definitions. All probable independent causes for each failure shall also be identified. A description of all possible damage modes which could result from specific threats (Failure/Damage Mode, DED 128).

f. If the Failure Mode and RCM Narrative Code (FMNCNABG) is (F), then this table describes the method(s) by which occurrence of a specific failure mode is detected by the operator or maintenance technician (Failure Mode Detection Method, DED 129).

- 48 -

MIL-STD-1388-2B

APPENDIX A

b.Table keys are migrated from table BF, but are given role name “FMT”

to distinguish them (LSACONBH, ALTLCNBH, LCNTYPBH, and FAMOINBH). Table keys are migrated from table CA, but are given role name “Task Requirement” to distinguish them (TLSACNBH, TALCNCBH, TLCNTYBH, and TTASKCBH).

c.Maintenance Interval (MAININBH) and Maintenance Interval MB (MAINMBBH)

must either both be blank, or have entries.

d.Edit c is not allowed unless a preventive Task Type (TATYPEBH) is selected.

e.Task Type (TATYPEBH) must be “P” or “U”, if PMCS from the CA table

is IIYII.

60.9 Table BI. Failure Mode Indicator Mission Phase Code Characteristics. This table contains FMECA results associated with the item under analysis categorized by failure mode and mission phase/operational mode. Table keys consist of EIAC (EIACODXA), LCN (LSACONXB), ALC (ALTLCNXB), LCN Type (LCNTYPXB), Failure Mode Indicator (FAMOINBF), and Mission Phase Code (MISSPCBL). For a given row of information, the following cross-element edits apply to table BI:

a.The EIAC from Mission Phase Operational Mode Table BL and Failure Mode

Table BF are the same; therefore, they are not duplicated.

b.Operating Time (FMOPTIBI) and Operating Time MB (FMOTMBBI) must either both be blank, or have entries.

c.The Operating Time MB (FMOTMBBI) should be the same as the Failure Rate MB (FARAMBBD) from table BD for the calculations to be correct.

d.Failure Mode Criticality Number shall be calculated based on Failure Effect Probability (Table BI), Failure Mode Ratio (Table BI), Part Failure Rate (Table BD), and Operating Time (Table BI). A change in any of these variables shall result in an update of the Failure Mode Criticality Number

(Table BI).

- 50 -