Planning Factors and Analyses
The maintenance and diagnostics concepts (Process Steps 1 and 2) are
important factors in determining STE.
The maintenance concept determines:
The diagnostics concept drives product design for efficient fault isolation
and repair. It also helps determine the mix of automatic and manual fault
detection and isolation. The degree and dependability of automatic fault
Generally, the less effective the diagnostics approach, the greater
the need for external test equipment and other resources.
The maintenance and diagnostics concepts interact with the over-all product
requirements (Process Step 3) to influence the evolving product design
(Process Step 4). As the product design stabilizes, maintenance tasks are
outlined through task identification (Process Step 6), and the identified
tasks are further refined through detailed task analysis (Process Step
8).Level of Repair Analysis (LORA) provides information for task analysis by
determining the most economical level of repair:
Repair at the customer's location (organizational-level
Repair at a special repair location (intermediate-level
Repair at a depot or centralized location
The types of STE available at each repair level and the cost of using that
STE also influences where repairs are made. On the other hand, the level of
The STE required for each repair
The manpower required to use the STE
The training required to prepare the manpower
The technical documentation required to support the
Thus, STE determination cannot be made independently of other
Life Cycle Cost (LCC) analysis (Process Step 5) considers all product
support factors, including:
Cost of research, development, and production
Operational support costs.
Failure analysis, safety analysis, and human factors analysis (Process Step
5) also evaluate the product design for supportability. The resulting data is
entered into the LSA data base (Process Step 9) through the LSA Record (LSAR).
The LSAR classifies, categorizes, and codifies the data as it is
By integrating all the analysis information, the LSAR also provides
a way to extract specific information to support specific logistic
In this way, LSA information is available to influence product design to
develop a final design that is both functional and supportable.
Minor changes during product design may be the difference between
using expensive, unique STE or standard, off-the-shelf STE.
Provisioning Strategy and Guidance
STE and spare parts provisioning activities generally address the same
issues and are usually done at the same time. STE provisioning guidance is
provided through the provisioning requirements statement (Process Step 10) and
the provisioning guidance conference (Process Step 11).
The provisioning requirements statement for a particular contract
Deliverable data requirements
Provisioning guidance conference to:
- Ensure that both the customer and contractor understand provisioning
- Establish funding and tasking milestones
- Determine data requirements.
The customer may request a preliminary provisioning preparedness review
conference to see if the contractor's provisioning preparation, documentation,
and facilities are adequate.
Provisioning screening (Process Step 12) usually applies to Government
contracts. If required, it would be included in the provisioning requirements
statement. Provisioning screening compares new or proposed STE with items
already in the Government supply system to:
Provisioning screening can also apply to civilian contracts to:
Ensure full use of items already in customer supply
Prevent duplicating items already in customer supply
Use appropriate items that are commercially
Ideally, all items of proposed STE should already be
Support Equipment and Test Equipment
Based on the information in the LSA data base, the contractor presents the
customer detailed recommendations for support equipment and test equipment
(Process Steps 13 and 14). This information is prepared during full scale
development and is presented in two forms:
A support equipment recommendations data form for each item of STE, except
common hand tools
Test requirements documents.
The support equipment recommendations data form justifies a recommended STE
item by detailing:
The maintenance tasks supported by the STE
The total number of that item needed
Recommended sources for acquiring that
The test requirements documents provide the data needed to select or
Test equipment for each product component
Test fixtures and/or interfaces to connect the component to the test
Procedures to perform the required
For military contracts, test requirements documents are prepared
differently for each service. Detailed preparation procedures are found in the
MIL-STD-1345B (Navy), Preparation of Test Requirements Document
MIL-STD-1519 (Air Force), Preparation of Test Requirements Document
MIL-STD-2076 (All Services), General Requirements
for Unit Under Test Capability with Automatic Test Equipment.
LSA Reports and Provisioning Data
In addition to support equipment recommendations data, several reports for
selecting STE can be generated from the LSA data base (Process Step 15). This
information is accessed through the LSAR. (The output reports for the
Government LSAR are listed in parentheses. See the Logistics Support Analysis
Reference Guide for a detailed discussion of the Government LSAR.)
Support Item Utilization Summary (LSA- 005) - justifies the need for each
item of support equipment and determines the number and distribution of each
Support Equipment Requirements (LSA-007) - lists all support equipment,
tools, and test equipment by skill specialty code and level of
- Selectable for any maintenance level or combination of levels
- Source information for developing tool kits for each skill specialty at
each maintenance level.
Tool and Test Equipment Requirements - lists tools and test equipment by
task function and maintenance level:
- Selectable by item category code or combination of item category
- For maintenance functions listed on the maintenance allocation
Provisioning requirements - determines the range and
quantity of support items for an initial period of support (for review at
Provisioning conferences (Process Step 16) allow the customer to:
Select support items from those recommended by the contractor
Assign technical and management item codes
Determine quantity requirements for individual STE,
Formal provisioning conferences should be coordinated with other program
milestones to avoid conflicts and delays that would affect provisioning
activities. General conferences are held when needed to resolve general
Post Provisioning Activities
If properly planned and conducted, provisioning conferences can pave
the way for follow-up provisioning activities.
Prepares a provisioned item order to buy support items from the
Makes adjustments to delivery requirements for support items and the
Places additional orders for support items during
the contract's life.
After receiving the provisioned item order, the contractor submits a priced
provisioned item order (Process Step 17). This documents the following, by
Overall proposed pricing and schedule information should be submitted
timely even if agreement on line item prices is pending. Now price
negotiations can begin.
(For Government contracts, other specific provisioning details are given in
Procurement and Delivery
For Government contracts, the following delivery steps are taken:
If the customer does not provide a delivery schedule, the contractor must
submit a line item delivery schedule within 60 days of receiving the
provisioned item order.
Then the customer has 30 days in which to notify the contractor if the
proposed schedule is acceptable.
If the proposed schedule is not acceptable, an
alternative schedule is negotiated.
The resulting approved delivery schedule is incorporated into the contract
through a supplement agreement (Process Step 18). This provides for actual
delivery of the STE.