Difference between revisions of "Logistics"

From SEBoK
Jump to navigation Jump to search
 
Line 48: Line 48:
  
 
[[{{TALKPAGENAME}}|[Go to discussion page]]]
 
[[{{TALKPAGENAME}}|[Go to discussion page]]]
<center>[[System Maintenance|<- Previous Article]] | [[System Deployment and Use|Parent Article]] | [[Systems Engineering Management|Next Article ->]]
+
<center>[[System Maintenance|<- Previous Article]] | [[System Deployment and Use|Parent Article]] | [[Systems Engineering Management|Next Article ->]]</center>
 +
==Signatures==
 
[[Category: Part 3]][[Category:Topic]]
 
[[Category: Part 3]][[Category:Topic]]

Revision as of 21:24, 9 August 2011

Introduction

There are several definitions for logistics within systems engineering and the definition used will determine what activities are considered part of logistics. The SEBoK defines logistics as “the science of planning and implementing the acquisition and use of the resources necessary to sustain the operation of a system.” (Cooke HUM - The Government Computer Magazine)

Process Approaches

This section is in early draft form; it will be completed for SEBoK version 0.5.

  • Document initial and life-cycle resource requirements for performing operations and support. This includes identifying and providing for initial spares, operational and support training capabilities, facilities, etc. Eventual disposal of the system should also be considered. Disposal of any existing systems to be replaced should also be considered.
  • Integrated Logistics Support (ILS). Logistics supports many elements of system operations and maintenance. ILS deliverables are the resources necessary to sustain the capabilities required of the system. The most common deliverables include:
    • Training and Training System.
    • Spares and Repair Parts (including Material Management Data).
    • Consumables and Raw Materials.
    • Technical Data/Documentation
    • Support & Test Equipment (STE).
    • Facilities.
    • Maintenance Repair Capability.
    • Storage and Preservation.

Methods & Tools

This section has not yet been written; it will be included in SEBoK version 0.5.

Evaluation

This section has not yet been written; it will be included in SEBoK version 0.5.

Practical Considerations

During deployment and use, considerations for cost, schedule, and performance or quality must be balanced. Often, cost and schedule are non-negotiable. As such, when there is budget crunch, there is a tendency to cut down on the planned level of ILS. When this occurs, the system engineer has to take note of the deficiencies in ILS and assess the impact on supportability and sustainability. For example, as spare parts may require long lead times (18 to 27 months is not uncommon for the defense sector), reordering of spares may need to be initiated almost immediately into the use phase even if a 2 to 3 year service spares lay-in may have been catered as part of the initial support package. As the operators become more proficient with the system, the expectation on how the system is to be used increases. This may result in increased utilization of the system and demands for change requests. (For more information on system evolution, please see System Life Management KA.) An increase in utilization is likely to lead to logistics bottlenecks such as a buildup of the return pipeline or a shortage of spare parts. SE activities would include review of the situation, conduction of logistics support analysis, and/or reliability, maintainability and availability reviews. (For additional information, please see the Cross-Cutting KA)

Application to Product, Enterprise, and Service Systems Engineering

References

Please make sure all references are listed alphabetically and are formatted according to the Chicago Manual of Style (15th ed). See the BKCASE Reference Guidance for additional information.

Citations

List all references cited in the article. Note: SEBoK 0.5 uses Chicago Manual of Style (15th ed). See the BKCASE Reference Guidance for additional information.

Primary References

All primary references should be listed in alphabetical order. Remember to identify primary references by creating an internal link using the ‘’’reference title only’’’ (title). Please do not include version numbers in the links.

Additional References

All additional references should be listed in alphabetical order.


Article Discussion

[Go to discussion page]

<- Previous Article | Parent Article | Next Article ->

Signatures