![]() |
||||
|
Logistics
Engineering Program
|
||||
|
|
||||
|
Logistics Programs |
Logistics Engineering Approach The approach to a program concerning the logistics engineering effort
is dependent upon many factors that include the customers' requirements,
the strategy of the company, and the size of the project etc. Detailed
in Mil-Std-1388/1A are various tasks associated to logistics engineering.
Simply to call out these tasks and implement them in a generic fashion,
maybe easier said than done. The effective implementation of a logistics
engineering program must take into consideration many other factors.
On the surface what may appear to be just a set simple questions, needs
to be addressed in a coherent fashion with an element of common sense.
How would someone model the life cycle support profile for the end user,
or what engineering or data support is required from the key subcontractors
and third or even forth tire subcontractors? To what level of engineering
detail shall be provided? These are some of the additional issues which
must be identified and addressed prior to the implementation of a logistics
engineering program.
Program requirements can be derived from the customer or the company's business strategy. For example: |
![]() |
||
Customer Requirements: The customer may request specific logistical engineering tasks to be implemented. These may include the development of maintenance plans to the final spare parts recommendations, and where they are to be located for each operational and repair site. From a viewpoint of the customer, this recommendation maybe implemented based upon a single program where there is just one product for one customer. The customer would normally address the issues associated with support costs. More and more companies and end users (government and commercial agencies),
during the selection process (or tender) for new "system" acquisitions
are considering Life Cycle Cost of Ownership. Therefore, key
in their final decision process is the cost associated with the operation
and maintenance of the equipment or system, over its intended operational
(life) period. Should a company take to market a product, which just
addresses and achieves the functionality performance requirements, without
taking into consideration the supportability issues, it may be placing
themselves and their product in a disadvantaged position.
The logistics program can be captured in a well throughout program plan. The plan could be developed as a standalone document or integrated in the overall ILS program strategy. The key function for this document is to capture the logistics strategy and all the required supporting logistics program tasks. The structure of the plan could include the following:
Logistics Program Tasks The ILS Manager or Logistics Manager will assess the program goals
in terms of the product/system support objectives and define the scope
of the activity. Logistics engineering activities can be employed throughout
all life cycle phases of a system from early development, to field deployment,
and eventually to system disposal. These activities will be governed
to adhere to contract requirements, as interpreted and captured in logistics
engineering program plan. The logistics engineering process utilizes
logistics modeling techniques to aid in identifying and provisioning
logistic support elements such as required sparing levels, test and
support equipment, and personnel quantity/skills.
Inputs to the Logistics Program The planning and implementation of the logistics engineering process will normally be based on the documents below. However, this list is not applicable in its entirety, as the generation of these documents will vary depending on the complexity of the program and customer requirements.
|
||||
|
MTain
looks forward to receiving your comments about this Web Site. Send your
comments to services@mtain.com
|
||||
|
Last Updated: July 2009 |
||||