MIL-HDBK-1390
5.3.4.3 Documentation of reviews (Activity 3.5). The documentation of these LORA reviews and conferences
is vital to ensuring the requiring authority and the performing activity are continually updated with the current status
of the program as well as any conflicts or issues as they arise.
Data preparation and management. The following paragraphs detail the preparation and management
5.4
activities associated with the LORA data necessary to execute an effective LORA program.
5.4.1 General considerations. The effectiveness of the LORA program is largely dependent upon
assembling the appropriate quantity and quality of input data to support the evaluations. LORA evaluations require
a variety of data, ranging from system/equipment hardware design features, to anticipated product support
requirements and existing support structure capabilities and constraints. Data rights and all proprietary data should
be identified and defined in order to avoid any negative impacts on the execution of the LORA program.
5.4.2 Input data compilation (Activity 4). This activity identifies the LORA input data which will be used in
the LORA evaluations. The tedious task of data collection can be reduced by examining the data obtained from
existing documents, comparative products, historical databases, and expert knowledge. When values are
unobtainable, engineering estimates or calculated values should be used. However, caution should be exercised to
ensure that data values are consistent and reliable. The most current data should be used. Elements related to cost
should be expressed in the same base year dollars. This will ensure consistency and accuracy. A major key to
having an effective LORA program is the use of the data available on similar systems/equipment to predict a
maintenance concept for the system/equipment being analyzed. If design parameters are predicted, then current
operational products which are similar to the product being analyzed should be identified.
5.4.2.1 Input data for economic LORA evaluations (Activity 4.1). This activity identifies values
corresponding to the data elements used in the economic LORA evaluations and sensitivity evaluations. The data
identified is used to establish a baseline maintenance concept. The data should be collected on all items listed in the
LORA candidates list.
5.4.2.2 Input data for noneconomic LORA evaluations (Activity 4.2). The data identified in this activity are
constraints, stipulations, special requirements, or other factors which restrict the maintenance concept or limit the
support alternatives available (e.g., safety, HAZMAT, environmental impacts, calibration, feasibility of repair,
security, training requirements, facilities). This data is used to perform a noneconomic LORA evaluation. Factors
which directly affect the repair decisions obtained should be used in conjunction with the economic LORA and
sensitivity evaluations to establish an optimal maintenance concept.
5.4.2.3 LORA input data report (Activities 4.3 and 4.4). This activity is generally invoked when another
performing activity is responsible for conducting the LORA evaluations (Activity 5). LORA input data should be
collected for all items in the LORA candidates list. Consideration should be given to the data rights being applied to
this report and the maturity of the input data. In order to maximize the usefulness of this LORA input data report,
the use of proprietary data should be limited and the report should be updated as better defined and more reliable
data becomes available.
Evaluations. The following paragraphs detail the evaluation activities utilized to perform the LORA.
5.5
5.5.1 General considerations. The heart of the LORA process is performing, analyzing, and documenting
LORA evaluations. This section defines the three individual, but closely related, LORA evaluations which are
typically undertaken: economic, noneconomic, and sensitivity evaluations. All LORAs should address each type of
evaluation.
5.5.1.1 Iterations. The activities contained in the evaluation sections are iterative in nature and are applicable
in each phase of the life cycle. This process is performed to increasingly lower levels of indenture and detail as the
system progresses through the life cycle and better defined data becomes available.
5.5.1.2 Timing. The development of support alternatives using the LORA process and evaluations should be
conducted to a level consistent with the design and operational concept development. In the early phases of the life
15
For Parts Inquires call Parts Hangar, Inc (727) 493-0744
© Copyright 2015 Integrated Publishing, Inc.
A Service Disabled Veteran Owned Small Business