Хорошев / ИЛП_материал_маг_02.15 / DEF STAN 00-60 / Issue 4 / Part 0 - Annex C - Data dictionary and related technical inf

C-31

DEF STAN 00-60 (PART 0)/4

ANNEX C

C.6.2 Table BB, Reliability, Availability, and Maintainability Characteristics Narrative. This Table may be used to identify RAM item functions, RAM 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 BB:

(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 system/equipment at a defined level of readiness, or in a specified condition in support of the operational requirement (RAM Maintenance Concept, DED 207).

(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 (RAMCNABBC) 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 shall 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).

(f)If the RAM Characteristics Narrative Code (RAMCNABB) is ‘F’, then this Table describes the interdependency between the software candidate under analysis and other software or hardware items (Software Interdependency Narrative, DED 811).

(g)If the RAM Characteristics Narrative Code (RAMCNABB) is ‘G’, then this Table describes the usage of modern software engineering methods and techniques, automated tools required and details of the implementation language used (Software Engineering Methods and Techniques, DED 809).

(h)If the RAM Characteristics Narrative Code (RAMCNABB) is ‘H’, then this Table contains the justification of why formal failure analysis is not documented in the LSAR (Formal Failure Analysis Not Required DED 837).

C-32

C.6.3 Table BC, Reliability, Availability, and Maintainability Logistics Considerations. This Table contains narrative information associated with logistics considerations. Table keys consist of EIAC (EIACODXA), LCN (LSACONXB), ALC (ALTLCNXB), LCN Type (LCNTYPXB), Logistics Consideration Code (LOCOCOBC), and RAM Logistics Considerations Text Sequencing Code (TEXSEQBC).

C.6.4 Table BD, Reliability, Availability, and Maintainability Indicator Characteristics. This Table contains reliability and maintainability characteristics of the CI under analysis categorized by comparative analysis, allocated, predicted, or measured values. Table keys consist of EIAC (EIACODXA), LCN (LSACONXB), ALC (ALTLCNXB), LCN Type (LCNTYPXB), and RAM Indicator Code (RAMINDBD). For a given LCN, ALC, and LCN Type combination, each different measurement base shall remain constant for all RAM Indicator Codes (RAMINDBD). For a given row of information, the following cross-element edits apply to Table BD:

(a)Failure Rate (FAILRTBD) and Failure Rate MB (FARAMBBD) shall either both be blank, or both have entries.

(b)Percentile (PERCENBD) is not allowed without a Maximum Time To Repair (MAXTTRBD).

(c)Mean Time Between Failures Operational (OPMTBFBD) and Mean Time Between Failures Operational MB (OMTBFMBD) shall either both be blank, or both have entries.

(d)Mean Time Between Failures Technical (TEMTBFBD) and Mean Time Between Failures Technical MB (TMTBFMBD) shall either both be blank, or both have entries.

C-33

DEF STAN 00-60 (PART 0)/4

ANNEX C

(e)Mean Time Between Maintenance Actions Operational (OMTBMABD) and Mean Time Between Maintenance Actions Operational MB (OMTBMMBD) shall either both be blank, or both have entries.

(f)Mean Time Between Maintenance Actions Technical (TMTBMABD) and Mean Time Between Maintenance Actions Technical MB (TMTBMMBD) shall either both be blank, or both have entries.

(g)Mean Time Between Maintenance Induced (INMTBMBD) and Mean Time Between Maintenance Induced MB (IMTBMMBD) shall either both be blank, or both have entries.

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

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

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

(k)Mean Time Between Removals (MTBRXXBD) and Mean Time Between Removals MB (MTBRMBBD) shall either both be blank, or both have entries.

(l)Achieved Availability shall be calculated based on Mean Time Between Failure Technical (Table BD), Mean Time Between Maintenance - No Fault (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 Achieved Availability (Table BD).

(m)Inherent Availability shall be calculated based on Mean Time Between Failures Technical (Table BD) and Mean Time To Repair Technical (Table BD). A change in any of these variables shall result in an update of the Inherent Availability (Table BD).

(n)Mean Time Between Consumption (MTBCONBD) and Mean Time Between Consumption MB (MTBCMBBD) shall either both be blank, or both have entries.

(o)Time Between Overhauls (TIMEBOBD) and Time Between Overhauls MB (TBOHMBBD) shall either both be blank, or both have entries.

(p)Time Between Scheduled Shop Visits (TBSSVSBD) and Time Between Scheduled Shop Visits MB (TBSVMBBD) shall either both be blank, or both have entries.

(q)Confirmed Fault Rate/1000 HRS (CFRKHRBD) shall not be entered unless RAM Indicator Code (RAMINDBD) is ‘M’.

C-34

DEF STAN 00-60 (PART 0)/4

ANNEX C

(r) Maximum Allowable Maintenance Interval (MAXAMIBD) and Maximum Allowable Maintenance Interval MB (MAMIMBBD) shall either both be blank, or both have entries.

NOTE 1: It is possible to calculate Time Between Overhauls (TIMEBOBD) using the same formula as Mean Time Between Removals (DED 235) although Task Code (TASKCDCA) first subfield in table CA shall be set to ‘K’. It is possible to calculate Time Between Scheduled Shop Visits (TBSSVSBD) using the same formula as Mean Time Between Removals (DED 235) although Task Code (TASKCDCA) first subfield in table CA shall not be set to ‘K’ or second subfield to ‘F’, ‘G’ or ‘J’, and the task shall result in the item being sent to the workshop for maintenance action.

NOTE 2: If Required Operational Mean Time Between Failures (OPMTBFBD), Required Technical Mean Time Between Failures (TEMTBFBD), Time Between Overhauls (TBOHMBBD) or Time Between Scheduled Shop Visits (TBSSVSBD) are entered, in Table HK, Reason for Selection (DED 668) should not be ‘0’ and in Table HA, Spare Parts Classification (DED 684) should be ‘2’ or ‘6’.

C-35

DEF STAN 00-60 (PART 0)/4

ANNEX C

C.6.5 Table BE, War/Peace Reliability, Availability, and Maintainability Indicator Characteristics. This Table contains reliability and maintainability characteristics of the CI under analysis categorized by wartime/peacetime scenarios and comparative, allocated, predicted, or measured values. Table keys consist of EIAC (EIACODXA), LCN (LSACONXB), ALC (ALTLCNXB), LCN Type (LCNTYPXB), RAM Indicator Code (RAMINDBD), and Operational Requirement Indicator (OPRQINBE).

C.6.6 Table BF, Failure Mode and Reliability-Centred Maintenance Analysis. This Table contains failure mode information and Reliability-Centred Maintenance analysis results associated with the CI. Table keys consist of EIAC (EIACODXA), LCN (LSACONXB), ALC (ALTLCNXB), LCN Type (LCNTYPXB), and Failure Mode Indicator (FAMOINBF). For a given row of information, the following cross-element edits apply to Table BF:

(a)Engineering Failure Mode Mean Time Between Failure (EFMTBFBF) and Engineering Failure Mode Mean Time Between Failure MB (EFMMMBBF) shall either both be blank, or both have entries.

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

C-36

C.6.7 Table BG, Failure Mode and Reliability-Centred 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-Centred

C-37

DEF STAN 00-60 (PART 0)/4

ANNEX C

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 and effect on the item operation, function, or status (Failure/Damage Effects: 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 Effects: 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 Effects: 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).

(g)If the Failure Mode and RCM Narrative Code (FMNCNABG) is ‘G’, then this Table provides information on known incipient failure indicators which are peculiar to the item failure trends (Failure Predictability, DED 138).

(h)If the Failure Mode and RCM Narrative Code (FMNCNABG) is ‘H’, then this is a narrative Table which states a condition not readily identified in a given data element. This Table is related to a failure mode and shall be prefaced with a reference to a specific failure mode (Failure Mode Remarks, DED 137).

(i)If the Failure Mode and RCM Narrative Code (FMNCNABG) is ‘I’, then this Table describes recommended design changes, disposition of each recommendation, and the results of each recommendation for which analysis indicates a redesign is warranted (Redesign Recommendations, DED 426).

C-38

DEF STAN 00-60 (PART 0)/4

ANNEX C

(j)If the Failure Mode and RCM Narrative Code (FMNCNABG) is ‘J’, then this Table describes the type of age exploration and how it is to be used based on the results of the RCM analysis made in Table BF (RCM Age Exploration, DED 343).

(k)If the Failure Mode and RCM Narrative Code (FMNCNABG) is ‘K’, then this Table describes the reasoning behind the RCM logic results and disposition choices made in Table BF (RCM Reasoning, DED 346).

(l)If the Failure Mode and RCM Narrative Code (FMNCNABG) is ‘L’, then this Table describes recommended RCM redesign changes, disposition of each recommendation, and the results of each recommendation for which analysis indicates a redesign is warranted (RCM Redesign Recommendations, DED 426).

C.6.8 Table BH, Failure Mode Task. This Table identifies the maintenance task(s) that are required to correct the identified failure mode of the CI under analysis and preventive maintenance tasks that are deemed applicable and effective through an RCM analysis. Table keys consist of EIAC (EIACODXA), Failure Mode Task (FMT) LCN (LSACONBH). FMT ALC (ALTLCNBH). FMT LCN Type (LCNTYPBH). FMT Failure Mode Indicator (FAMOINBH), Task Requirement LCN (TLSACNBH), Task Requirement ALC (TALCNCBH), Task Requirement LCN Type (TLCNTYBH), and Task Requirement Task Code (TTASKCBH). For a given row of information, the following cross-element edits apply to Table BH:

(a)The EIAC from Task Requirement Table CA and Failure Mode and RCM Analysis Table BF are the same.

(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) shall either both be blank, or both have entries.

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

C-39

DEF STAN 00-60 (PART 0)/4

ANNEX C

(e) Task Type (TATYPEBH) shall be ‘P’ or ‘U’, if PMCS from the CA Table is ‘Y’.

C.6.9 Table BI, Failure Mode Indicator Mission Phase Code Characteristics. This Table contains FMECA results associated with the CI 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.

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

(c)The Operating Time MB (FMOTMBBI) shall be the same as the Failure Rate MB (FARAMBBD) from Table BD.

(d)Failure Mode Criticality Number shall be calculated based on Failure Effect Probability (Table BI), Failure Mode Ratio (Table BF), 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).

(e)Principal Features List Code (PFLCODBI), if required, shall either be set to ‘CRISAF’, ‘CRIPER’ or ‘MAJPER’ (refer to Principal Features List data element definition).

C-40