Page images
PDF
EPUB
[merged small][merged small][merged small][merged small][merged small][merged small][ocr errors]

Instructions for completing the Failure Factor blocks of the Provisioning Format, Figure 1, MIL-STD-1552 are as follows:

1. Failure Factor 1, Block 16:

a. This block will contain the maintenance factor (M/F). The first position of this 6-digit field will not be used. The M/F will always be expressed as a five position number (i.e., 0.0500). A decimal point will be understood to be between the first and second digit of the five position number.

b. The M/F is defined as the anticipated average maintenance replacement rate per operating program increment, that is per 100 hours (H), or per 1,000 rounds (R) expended. The replacement of the item must further create a demand on supply for a like item. The demand on supply or Mean Time Between Demand (MTBD) criteria excludes maintenance actions such as renair on line/aircraft and other nondemand failures, which are not correctly a part of the maintenance factor. The derivation of a maintenance factor must encompass the ratio of demands to failures, demands to maintenance actions, and operating hours to flying hours (utilization factor).

e. Maintenance factors are not required for items authorized for depot use only. The initial requirements for these items will be computed from the overhaul replacement factor.

d. To develop the maintenance factor for single application quantity per article (QPA-1) within a single next higher assembly (NHA):

(1) Estimate the time the item will experience between failure removals which places a demand on supply (MTBD) and divide into the appropriate operating program unit. This figure must represent the rate at which a single installed item will fail, requiring removal and replacement regardless of the level of repair at which the replacement is made, since requirements determined utilizing this type of maintenance factor include the tool (OFM, overhaul of NHA, and engine overhaul) item replacement. It must include consideration for:

(a) Design performance limitations.

(b) Maintainability and reliability analysis data.

(e) Similar or like item comparison and usage data.

(d) Contractor and vendor estimates.

(e) Mandatory removal intervals.

Replacement due to repair of NHA.

(g) Test data and experience.

(h) Operational environment.

(2) If the applicable program is in program units of 100 hours (H), develop the factor by dividing 100 by the estimated MTBD. For example, when the MTBD is estimated at 1,000 hours, the factor is as follows:

100 hours (program unit)
1,000 hours (MTBD)

-0.1000 maintenance factor

expressed as: 0.1000 failure removals per 100 hours of
program.

(3) If the applicable program is in program units of 1,000 rounds of ammunition expended, the MTBD must also be developed using that base line. The factor is developed by dividing 1,000 by the MTBD. If, for example, it is estimated that the item will require replacement of a single application every 5,000 rounds, the factor is as follows:

1,000 rounds (program unit)

5,000 rounds (MTBD)

-0.2000 maintenance factor

expressed as: 0.2000 failure removals per 1,000 rounds
expended.

(4) The program to which the factor is applied must be in program units compatible with the factor. In computing gross removals for the initial requirements support period the factor may be applied to aggregate end article/recoverable item programs as shown below:

[merged small][ocr errors][merged small][merged small][merged small]

The conversion from total hours to 100-hour increments will be accomplished during preparation of the programming checklist and is shown here only for the purpose of clarity.

e. To develop the maintenance factor for multiple applications (multi-QPA) within a single NHA, determine the rate of each single application and divide the added rates by the total QPA. For example:

The MTBD is estimated at 400 hours, 1st application; 1800 hours, 2d application; and 2300 hours, 3d application, the factor is derived as follows:

[merged small][merged small][merged small][merged small][merged small][merged small][merged small][ocr errors][merged small][merged small][merged small][merged small][merged small][merged small][merged small]

0.3490 + 3 = 0.1163 average maintenance factor expressed as: 0.1163 average failure removals per QPA per 100 hours of the program.

f. To develop the rate for multiple applications (multi-QPA) and multiple NHAs: Step 1-Multiply the QPA of the items times the number of NHA installed. Step 2-Determine the rate within a single NHA and multiply that figure times the results of step 1. Step 3-Total the results and divide by the sum of all installed QPAs. For example: The F105 has installed 2 gyros, 5 actuators, and 10 pumps. Bearing "XX" is used (QPA), 5 times each gyro, 4 times in each actuator, and 3 times in each pump. Establish an average maintenance factor for bearing “XX" as follows:

[blocks in formation]

24.500+ 60 = average maintenance factor expressed as:;:0.4083 failure removals per QPA per operating program increment, 2. Failure Factor II, Block 17. This block has been modified into two separate blocks.

a. Overhaul Replacement Percent. (Block 17, three spaces, AF Modified).

(1) These three positions will be utilized for assignment of the overhaul replacement percent (O/H). A decimal point will be understood to be between the first and second position (i.e., 0.40).

(2) The O/H represents the replacement rate of a spare or repair part in the overhaul of the next higher recoverable assembly (NHRA). The maintenance decision for the item being factored or for its next higher assembly determines the need for the assignment of an overhaul replacement percent. This relationship also determines if the overhaul replacement percent is used to compute an initial requirement or to determine asset distribution. The following rules will apply in the assignment of overhaul replacement percents:

(a) Subassemblies and bit and piece for items repair coded L and D will require an overhaul replacement percent.

(b) Subassemblies and bit and piece for items repair coded F will not require an overhaul replacement percent. It is Imperative that indenture integrity be maintained to insure proper parts projection and that initial computations are based upon the projected maintenance program of the next higher assembly,

(c) Overhaul replacement factor examples follow:

1. Repair part "X" installed in recoverable items "Y" is one application, or a QPA of one each. The equipment specialist estimates 10 replacements for part "X" or 10% of the total next higher assemblies overhaul program.

2. Repair part "Z" is installed in three varied functional applications in items "Y" for QPA of three each. The equipment specialist estimates those replacements at 10%, 80%, and 30% respectively. The average replacement percentage is 120% divided by 3 or 40%. The overhaul replacement percent will be expressed as 0.40 on the PTD.

b. Base Condemnation Percent. (Block AH, three spaces, AF Modified).

(1) These three positions will be utilized for assignment of the base condemnation percent (BCR). A decimal point will be understood to be between the first and second positions (i.e., 0.10).

(2) The BCR is a percentage assigned to items repair coded F which represents that portion of the failed items removed and processed for intermediate level repair which will be condemned at that level due to wear out or economical repair limita

tions.

(3) A base condemnation percent for items coded B or 7 (no repair authorized) is not required in that the maintenance factor assigned to the item establishes the issue requirement for that item. For items repair coded F, this entry is used during the requirement computation and is vital to the accuracy of the initial procurement quantities.

Attachment 4

[ocr errors][merged small]

3. Failure Factor III, Block 40. Block 40 has been modified into two separate blocks. ATCH NR 2

a. Not Reparable This Station (NRTS). (Block 40, three spaces, AF Modified).

[ocr errors][merged small]

(1) These three positions will be utilized for assignment of the NRTS percent. A decimal point will be understood to be between the first and second position (1.e., 0.10).

(2) The NRTS percent represents that portion of the estimated reparable generations which the intermediate repair shops will be unable to repair and therefore will be processed to a Technical Repair Center.

(3) During initial provisioning this will apply only to items repair level coded D.

(4) This factor in conjunction with one or more of the other factors will assist in providing, for example, percent base processed/repaired, percent depot processed/repaired, estimated quantities of depot condemnations, estimated reparable generations, and the overhaul recovery percent.

(5) The reason for not requiring NRTS percents for items maintenance repair coded L or F is that these items are planned 100 percent depot or base, as appropriate.

b. Depot Condemnation Percent (Block AJ, three spaces, AF Modified).

(1) These three positions will be utilized for assignment of the depot condemnation percent (DCR). A decimal point will be understood to be between the first and second position (i.e., 0.06).

(2) The DCR represents the percentage of repair parts, recoverable assemblies, or end items which will be condemned during depot overhaul. For repair parts (repair coded B or Z) condemnations will always equal replacements and the DCR% will equal 100%.

(3) For assemblies (non-job routed) use in repair of an NHRA or end item (undergoing depot level overhaul), the depot condemnation percent will be that percentage of the replaced assemblies which will be condemned.

Example: Next higher assemblies undergoing depot overhaul – 100 ea

Estimated number of items "X" replaced

Estimated number of items "X" replacement
condemned

DCR-1050

DCR-20%

-50 ea

- 10 ea

(4) For recoverable assemblies or end items established separately (job routed) as depot overhaul items, enter the percentage of the recoverable assemblies or end items which will be condemned during overhaul. This percentage, when added to the overhaul recovery percent, will equal 100%.

[blocks in formation]
[blocks in formation]

Instructions for submission of Provisioning Technical Documentation (PTD) records by magnetic tape to the AFLC Provisioning System (D220). Reference Attachment 6 for tape input edit criteria.

1. All submissions of Provisioning Technical Documentation will consist of the following tape records, on nine track, 1600 BPI using Extended Binary Coded Decimal Interchange Code (EBCDIC) with standard labels. Records will be 240 characters long blocked by 12 records (2880 character blook).

2. The following data will be supplied in accordance with MIL-STD-1552, Provisioning Requirements Statement, Air Force Addendum to DD Form 1949-2, and as specified herein. Data elements to be furnished shall be in accordance with DoD Form 1949-1, Provisioning Technical Documentation Data Selection Sheet, provided on contract by the Air Logistic Center (ALC) Provisioning Activity.

a. HEADER RECORD: (Reference Attachment 1.) A header record will be prepared for every submission of type of PTD Code in accordance with the following:

(1) DOCUMENT IDENTIFIER (D/I): 6IS will be assigned.

(2) Block No 49 - PROVISIONING CONTRACT CONTROL NUMBER (PCCN): MIL-STD-1552, para 5.1.4.2. The PCCN shall be obtained from the ALC provisioning activity during the guidance conference or prior to contractor submission of PTD. It shall be assigned to end articles, i.e., aircraft, support equipment, training equipment, flight simulators, subsystems, etc. Separate PCCNs must be assigned for special lists such as Tools and Test Equipment List (TTEL), Repairable Items List (RIL), Interim Support Items List (ISIL), and Long Lead Items List (LLIL) as instructed by the ALC provisioning activity.

(3) Block No E - SUBMISSION CONTROL CODE (SCC): MIL-STD-1552, para 5.2.2.5. Will be initialized at "00001" for each PCCN, and incremented by one for every subsequent submission. A different SCC will be assigned for each specific type of PTD within a PCCN and for each RIB incrementally submitted within a PCCN.

(4) Block No A - PROCUREMENT INSTRUMENT IDENTIFICATION NO (PIIN): MIL-STD-1552, para 5.1.1.1. Not mandatory. Optional for contractor.

:

(5) Block No B

para 5.1.1.2.

NOMENCLATURE/MODEL OR TYPE NUMBER: MIL-STD-1552,

Not mandatory. Optional for contractor.

(6) Block No C CONTROL DATA: MIL-STD-1552, para 5.1.1.3. First position contains type o PTD Code. Remainder of field available for contractor use, if required, and agreed upon with the ALC provisioning activity, This code is used to identify the TYPE of PTD being submitted. each specific Type of PTD a SCC must be assigned. Reference Block No E, above, for additional instructions. Type PTD must contain one of the following codes:

[blocks in formation]

For

F33657-79-C-0479

ATCH NB 277

Interim Release (IR)

NOTE:

[blocks in formation]

(Multiple "B" and "E" will not be submitted within the same SCC.)

« PreviousContinue »