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

MIL-STD-1388-2B

130.5 Table JE, Transport by Fiscal Year. This table contains information about the system/equipment procurement and delivery schedule. The table keys consist of EIAC (EIACODXA), LCN (LSACONXB), ALC (ALTLCNXB), LCN Type (LCNTYPXB), and Transport Fiscal Year (TRAFYRJE).

130.6 Table JF, Transportation Narrative. This table may be used to identify Transportation Shock and Vibration Requirements, Lifting and Tiedown Remarks, Projection Characteristics, Regulatory Requirements, Special Services and Equipment, Sectionalized Remarks, Transportation Remarks, Transport To/From Remarks, Environmental Considerations, Military Distance Classification, Unusual and Special Requirements, Venting and Protective Clothing, and Disaster Response Force. The table keys consist of EIAC (EIACODXA), LCN (LSACONXB), ALC (ALTLCNXB), LCN Type (LCNTYPXB), Transportation Narrative Code (TRANCDJF), and Transportation Narrative Text Sequencing Code (TIUNARJF). For a given row of information, the following cross-element edits apply to table JF:

a.If the Transportation Narrative Code (TRANCDJF) is (A), then this table should state the fragility, shock, and vibration considerations required for the system/equipment under analysis (Transportation Shock Vibration Remarks, DED 382).

b.If the Transportation Narrative Code (TRANCDJF) is (B), then this

table identifies the number, location, and strength of the lifting provisions and tiedown remarks for the system/equipment under analysis (Lifting and Tiedown Remarks, DED 192).

- 111 -

MIL-STD-1388-2B

APPENDIX A

c.If the Transportation Narrative Code (TRANCDJF) is (C), then this table states the dimensions and locations of any significant projections of the system under analysis (Transportation Projection Remarks, DED 471).

d.If the Transportation Narrative Code (TRANCDJF) is (D), then this table describes data to show compliance with regulatory requirements (Regulatory Requirements, DED 340).

e.If the Transportation Narrative Code (TRANCDJF) is (E), then this

table provides a narrative field for transportation remark which may include towing, self-propelled, handling, and air dropped information, plus any transportation information not captured in other data elements or other narrative fields. (Transportation Remarks, DED 472).

f. If the Transportation Narrative Code (TRANCDJF) is (F), then this table describes any information concerning the requirements for special services and equipment (railcars, highway vehicles, or materiel handling equipment) when required for the system under analysis (Special Service and Equipment, DED 398).

g. If the Transportation Narrative Code (TRA.NCDJF) is (G), then this table provides the sectionalization information for each section that is being transported (Sectionalized Remarks, DED 368).

h. If the Transportation Narrative Code (TRANCDJF) is (H), then this table describes from where the item is transported and to where the item is transported (Transported To and From, DED 476).

i. If the Transportation Narrative Code (TRANCDJF) is (I), then this table provides information concerning any special environmental/hazardous considerations required for the transportation of the system/equipment under analysis (Environmental/Hazardous Materials Considerations, DED 099). For this table to be used, a (Y) must be entered into the Environmental Handling and Transportation Indicator (ENHATCJA) table JA.

j. If the Transportation Narrative Code (TRANCDJF) is (J), then this table describes the military quantity distance class and storage compatibility groups (Military Distance Classification, DED 240). For this table to be used, a (Y) must be entered into the Environmental Handling and Transportation Indicator (ENHATCJA) table JA.

k. If the Transportation Narrative Code (TRANCDJF) is (K), then this table describes any unusual item transportation characteristics (e.g. temperature limits, humidity limits, escorts required, etc.) (Unusual and Special Requirements, DED 500). For this table to be used, a (Y) must be entered into the Environmental Handling and Transportation Indicator (ENHATCJA) table JA.

l. If the Transportation Narrative Code (TRANCDJF) is (L), then this table describes the venting and protective clothing requirements (Venting and Protective Clothing, DED 504). For this table to be used, a (Y) must be entered into the Environmental Handling and Transportation Indicator (ENHATCJA) table JA.

m. If the Transportation Narrative Code (TMNCDJF) is (M), then this

- 112 -

MIL-STD-1388-2B

APPENDIX B

APPENDIX B

LOGISTIC SUPPORT ANALYSIS RECORD REPORTS

10. PURPOSE. This appendix contains a listing and description of the Logistic Support Analysis (LSA) Record (LSAR) reports and guidance for data utilization. Reports will be selected by the requiring authority to tailor and document the results of the support analysis tasks based on criteria as stated in Appendix D. This documentation provides the capability of developing product summaries from a common data source, thus, enhancing data uniformity and reducing data product cost. These reports may be automatically produced from a validated LSAR automated data processing ADP system. Requirements of this appendix will be referenced and implemented in contractual documents, as specified in the Contract Data Requirements List (CDRL).

20. CONCEPT. An LSAR ADP system will, as a minimum, produce the reports shown on figures 15 through 60 on an individual basis from computer stored data. This capability permits automatic generation of product and analysis reports capable of satisfying the cited data item descriptions in paragraph 6 of this standard. A validated LSAR ADP system can be used to automatically generate the summaries contained in this appendix based upon the specific ADP processing requirements of the validated system. When required, any or all of the LSAR reports contained in this appendix can be manually produced. When

20.1 LSAR data table to report matrix. Figure 14 contains a matrix of LSAR data tables to reports. Finding a report across the top of figure 14, and then reading down the column, a user can determine the specific data elements required to produce the given report. The data appearing on the summaries; required to qualify an item for a summary; used in report calculations; modified when used on an output; and, keys of the tables directly impacting a report generation, are all specified by an identifying code. The data table “business rules” and edits may dictate that additional data tables must be established prior to making a specific table entry, e.g. , establishing a foreign key.

20.2 General report selection criteria. Unless otherwise specified in the report description, LSA summaries described in this appendix shall be in ASCII sequence. The following basic rules are provided as guidance for report selection:

a. For Service Designator Code (DED 368) selections, choosing A, F, N, or M results in the selection of the matched service designator code and X and J codes. Choosing T results in selection of both T and J codes. All other code selections results in extraction of matched code data only. Service designator qualification in many instances will occur by task code (DED 419).

b. Lower-tiered or “trailer” LSA Control Number (LCN) and Alternate LCN Code (ALC) selections may be made against any report which specifies selection by LCN/ALC range. This further defining a report selection is used when multiple configurations, alternate design or maintenance concepts, or

- 115 -

MIL-STD-1388-2B

APPENDIX B

alternate vendors are contained in the LSAR. For example, as a rule, the basic configuration of an equipment is identified by LCNs with no ALC entry. Where alternate(s) at the component level are documented and the alternate is required on the specified report, the basic selection would have no ALC entry. However, a lower indentured LCN may also be used with the report selection to obtain the specific LCN(S) and ALC(S) of the assembly(s) to be substituted for the basic configuration. Lower indentured LCN selections will include the subordinate items to the alternate selected. Once the alternate assembly(s)

c.The Usable On Code (UOC) (DED 495) is a primary (and often mandatory)

selection criteria when selecting LSAR reports by LCN. It is used to identify

requirement holds even if only one configuration/model of a system/equipment is being documented. In accordance with table XC, contained in appendix A of this standard, each configuration/model is assigned a unique UOC at the system/end item level LCN. Each individual assembly/component/piece part is also “linked” to the assigned UOC of the model of which it is applicable through tables XF and HO. When an assembly/component/piece part is applicable to more than one configuration/model, then multiple UOCS are “linked” to the component for a single LCN and ALC via tables XF and HO. This eliminates the requirement of duplicating analysis and related data, merely because an item has application to multiple configurations/models. For further information on the UOC, LCN, and ALC relationship, refer to appendix C.

30.LSAR REPORTS.

30.1 LSA-001, Man-Hours bv Skill Specialtv Code and Level of Maintenance. A

personnel, by Skill Specialty Code (SSC), and person identifier to perform each task. The format is contained on figure 15. Spacing between rows and columns is not critical on this report.

30.1.1 Part I contains a summary of annual man-hour expenditures by maintenance levels and SSC. Man-hour totals are based on the number of systems supported by level of maintenance. The number of maintenance tasks used to develop the report are displayed. The man-hour values displayed in each column (level of maintenance) are derived for each SSC by multiplying the task frequency, times the sum of the man-minutes per person identifier, divided by 60 and summing those values for each maintenance task performed by a particular SSC. At the option of the user, more than one end item, system, component, etc., supported, at any given maintenance level, may be requested.

values are obtained by multiplying the number of items supported by each maintenance level times the annual maintenance man-hours involved. Part I is sequenced by ascending SSC.

30.1.2 Part II contains a report of the man-hours, by person identifier, expended on each maintenance task. Man-hours are the sum of the man-minutes per person identifier for the same person identifier involved in a task,

- 116 -

MIL-STD-1388-2B

APPENDIX B

divided by 60. An evaluation of the skill specialty and the requirement for training equipment is provided for each task code. It provides annual man-hours per item per maintenance task, and total man-hours per maintenance task based on number of systems supported, and can be obtained for a specific SSC/ Skill Evaluation Code. The annual man-hours per item column is obtained by multiplying the task frequency times the man-minutes involved for the maintenance task for a specific person identifier. The total annual man-hours column is derived by multiplying the number of systems supported, as specified

30.2 LSA-003, Maintenance Summary. A report which compares the current status of the system maintenance parameters with the requirements recorded on the A data tables. The format is contained on figure 16. Spacing between rows and columns is not critical on this report.

30.2.1 Task code functions of “O”, “T”, “U”, “V”, “y”, and “3 - 9“, and task code interval of “Y” are not used in the LSA-003 report calculations. The elapsed time and man-hour values printed on the status line of the report are calculated from data on the C data tables in the following manner:

ETm = Mean elapsed time

M-Hm = Mean man-hours

ETi = Elapsed time for task i (DED 217)

TFi = Task frequency for task i (DED 422)

M-Hi = Total man-hours for task i (DED 218)

N = Total number of tasks performed

The preceding computations are performed for each of the following groupings of tasks at crew and organizational operation\maintenance (O/M) Levels:

a.Daily Inspection (task code position 1 is “A”, and position 2 is “C”).

T b. Preoperative xInspection (task code position 1 is “A”, and position 2 is

c.Post Operative Inspection (task code position 1 is “A”, and position 2 is “H”).

d.Periodic Inspection (task code position 1 is “A”, and position 2 is “E” or “B”) .

e. Mission Profile Change (task code position 1 is “M”).

f. Turnaround (task code position 5 is “F”).

L

Also , the preceding computations are performed for unscheduled tasks (task code position 2 is F, G, or J) at all maintenance levels.

- 117 -

MIL-STD-1388-2B

APPENDIX B

30.2.2 The scheduled and unscheduled values for annual man-hours per end item are derived utilizing data from the C tables for a given LCN using the task interval codes F, G, and J for unscheduled tasks and all remaining task interval codes scheduled. The following calculations are performed at each maintenance level:

(M-Hs)a - Annual man-hours for scheduled maintenance (M-Hu)a - Annual man-hours for unscheduled maintenance

TFi - Task frequency for task i (DED 422) (M-Hs)i - Total man-hours for scheduled maintenance

task i (DED 218)

(M-Hu)i - Total man-hours for unscheduled maintenance task i (DED 218)

N - Total number of tasks performed

The scheduled and unscheduled values are summed to yield total annual manhours per end item.

30.2.3 The scheduled and unscheduled man-hours per operating hour are calculated by dividing the annual man-hours per end item from the LSA-O03 Report by the annual operating requirements specified on the A table. This calculation is performed at each O/M level.

30.2.4The status totals for all levels are calculated by summing the manhours for each level of maintenance.

30.2.5The organizational inspection section is always shown first. The remainder of the report is sequenced by ascending maintenance level (crew to depot).

30.3 LSA-004, Maintenance Allocation Chart Summary. The maintenance allocation chart (MAC) Summary is a report consisting of four sections, three of which are obtainable from the LSAR. Section I, Introduction, is “boiler plate” information developed IAW either figures 20 or 21 of MIL-M-63038 (TM) Manuals, Technical (Army). Sections II, MAC; III, Tool and Test Equipment Requirements; and IV, Remarks are produced as separate sections of this summary. The report is provided in standard or aviation format IAW figures

30.3.1 Section II, consists of the man-hour allocations by maintenance function and maintenance level. Task functions (lst position task code) for the draft MAC will appear as they do in the LSAR database. Task functions not allowed on a proof MAC will be automatically included as follows:

a. Access , Disassemble/Assemble, and Fault Locate times are included as

- 118 -

MIL-STD-1388-2B

APPENDIX B

part of the repair time.

b.End-of-Runway Inspection times are included as part of inspect time.

c.Remove and Install times are included as part of the Remove/Install

time.

d. Remove and Replace times are included as Replace time.

e.Lubricate times are included as part of the service times.

f.Task Function Codes of “Q”, “M”, “U”, “V”, “O”, “Y”, “T”, and “2 - 9“

are not included on the MAC. The Task Interval Code “Y” is also not included on the MAC.

30.3.2 Operations/Maintenance (O/M) Level “G” is not included on the proof MAC. The O/M level “L” is included as part of Maintenance Category “H” on the standard MAC. Only O/M levels of “O”, “F”, and “D” apply when the aviation MAC is developed. Maintenance category aviation unit (AVUM) equates to “O”; aviation intermediate (AVIM) to “F”; and Depot to “D”.

30.3.3 For each O/M Level, the mean-man hours is calculated for all tasks with the same task function as follows:

TFi =- Task frequency for task i (DED 422)

N = Total number of tasks performed

Man-hours are rounded to the nearest tenth of an hour. Section II is sequenced by ascending LCN or Functional Group Code (FGC) (depending on the display option selected), then by ascending maintenance function based on the first position of the task code,

combination of ICCS. The section is used to identify tools and test equipment required to perform the maintenance functions listed on the Section 11 Maintenance Allocation Summary. Sections II and III are cross-indexed by the “Tool or Test Equipment Reference Code.” Section III is sequenced by ascending reference numbers.

30.3.5 Section IV, Remarks. The Remarks section is based upon Remarks entered against qualified MAC tasks. Sections II and IV are cross indexed by the Remarks Code contained in column 6 of section II and the Reference Code of

- 119 -