MIL-HDBK-1390
5.7.1.1 Amount of design freedom. The amount of design freedom is a key consideration in LORA. Design
freedom is related to program objectives, operational requirements, and technological opportunities. One objective
of LORA is to influence selection of design characteristics to achieve improvements in supportability (e.g., design
for discard). If the design and maintenance policy for the program are already fixed, the LORA effort will not be as
beneficial. As the design and maintenance policy become fixed, the amount of LORA activity encountered will
usually decline. However, if the design and maintenance policy for a program are generated concurrently until
finalized, LORA will be beneficial in developing an optimized system support package. During the P&D and O&S
phases, a LORA may be conducted to evaluate the maintenance concept and determine potential benefits to be
gained by changing the maintenance concept.
5.7.1.2 Availability and relevancy of resources. The successful completion of a LORA requires resources in
the form of people with relevant experience and sufficient funding. It is DoD policy to fund readiness and support
considerations up-front in system acquisition programs. However, in reality, resources are constrained. If program
funds are short, the LORA effort may have to be adjusted to compensate for lack of funds or be accomplished in-
house.
5.7.1.3 Schedule constraints. Fast track programs, as their name implies, are acquisition programs in which
time constraints require the design, development, production, testing, and support acquisition process to be
compressed or overlapped. These programs tend to reduce the time to accomplish design-influencing analysis tasks
such as LORA. Scheduling of the LORA should be considered to ensure a maintenance concept that results in an
optimal product support footprint, but also meets statutory and regulatory requirements to avoid program risks.
5.7.1.4 Data availability and relevancy. The availability and accuracy of historical data on similar existing
systems and equipment is crucial for accomplishing a LORA in the early stages of a program. Utilizing a Baseline
Comparison System (SAE TA-STD-0017, Activity 6) can assist in assessing any technology advances and cost
differentials between current and historical data. If historical data is unavailable, it can impact the effectiveness of
the LORA effort.
5.7.2 Acquisition phase of the program. The extent and level of detail of the LORA program should be
tailored to the appropriate life cycle phase of the program. TABLE IX identifies the applicability of the LORA
activities by phase of development while the information outlined in Paragraphs 5.7.2.1 through 5.7.2.4 of this
handbook should be used to determine the amount of LORA activity to be administered during each life cycle phase.
FIGURE 3 through FIGURE 6 illustrates when LORA (SAE TA-STD-0017, Activity 11.7) is required as part of the
conventional PSA process flow. The methodology behind this conventional PSA process flow is detailed in
Paragraphs 5.8.13.5 through 5.8.13.9 of MIL-HDBK-502A. These figures and table should be used as guidance
only and may require adjustment or tailoring to satisfy the requirements for specific acquisition programs.
TABLE IX. Tailoring of LORA activities
PSA Life Cycle Phases
Activity
SAE AS1390 LORA Activities
Number
MSA
TMRR
EMD
P&D
O&S
1
Program Strategy
S
G
G
C
C
2
Program Planning
S
G
G
C
C
3
Program Reviews
G(1)
G
G
G(1)
G(1)
4
Input Data Compilation
S
G
G
C
C
5
Evaluation Performance, Assessment, and Documentation
S
G
G
S
S
6
Using Results
G
G
G
G
G
S-Selectively applicable, G-Generally applicable, C-Generally applicable to design changes only, (1)-Selectively applicable for equipment level acquisitions
19
For Parts Inquires call Parts Hangar, Inc (727) 493-0744
© Copyright 2015 Integrated Publishing, Inc.
A Service Disabled Veteran Owned Small Business