Service Life Management
Product and service life management deals with the overall life cycle planning and support of a system. The life of a product or service spans a considerably longer period of time than the time required to design and develop the product or service. Systems engineers need to understand and apply the principles of life management throughout the life cycle of the system.
Product and service life management is also referred to as system sustainment. Sustainment involves the supportability of operational systems from initial procurement to disposal. Sustainment is a key upfront task for systems engineering that influences product and service performance and support cost for the entire life of the program. Sustainment activities include: design for maintainability, application of built in test, diagnostics, prognostics and other condition-based maintenance techniques, implementation of logistics footprint reduction strategies, identification of technology insertion opportunities, identification of operations and support cost reduction opportunities, and monitoring of key support metrics. Life Cycle Sustainment Plans should be created for large, complex systems (DAU 2010).
Product and Service Life Management applies to both commercial and government systems. Examples of large commercial systems include energy generation and distribution, information management systems, the Internet, and health industries. Government systems include defense systems, transportation systems, water handling systems, and government services. It is critical that the planning for system life management occur during the requirements phase of system development. The requirements phase includes analysis of life cycle cost alternatives, and the understanding of how the system will be sustained and modified once it is operational.
The body of knowledge associated with product and service life management includes the following areas: (1) Service Life Extension; (2) Modernization and Upgrades, and (3) Disposal and Retirement. System engineers need to understand the principles of service life extension, the challenges that occur during system modifications, and issues involved with the disposal and retirement after a system has reached its useful life . Managing service life extension uses the engineering change management process with an understanding of the design life constraints of the system. Modernizing existing legacy systems requires special attention to understanding the legacy requirements and the importance of having a complete inventory of all the system interfaces and technical drawings. Disposal and retirement of a product after reaching its useful life requires attention to environmental concerns, special handling of hazardous waste, and concurrent operation of a replacement system as the existing system is being retired.
The principles of product and service life management apply to different types of systems and domains. The type of system (commercial or government) should be used to select the correct body of knowledge and best practices that exist in different domains. For example, military systems would rely on sustainment references and best practices from Department of Defense (i.e., Military service instructions, Defense Acquisition University) and military standardization bodies (i.e., AIAA, SAE, SOLE, National Geo-spatial consortium).
Systems such as commercial aviation, power distribution, transportation systems, water handling, the Internet, and health industries would rely on system life management references and best practices from a combination of government agencies, local municipalities, and commercial standardization bodies and associations (i.e., Department of Transportation, State of Michigan, ISO, IEEE, INCOSE).
Some standardization bodies have developed system life management practices that bridge both military and commercial systems (i.e., INCOSE, SOLE, ISO, IEEE).
There are multiple commercial associations involved with defining engineering policies, best practices, and requirements for commercial product and service life management. Each commercial association has a specific focus for the market or domain area where the product is used. Key commercial associations include: American Society of Hospital Engineering (ASHE); Association of Computing Machinery (ACM); Society of Automotive Engineers (SAE); American Society of Mechanical Engineers (ASME); American Society for Testing & Materials (ASTM) International; National Association of Home Builders (NAHB); and Internet Society (ISOC) including Internet Engineering Task Force (IETF).
The INCOSE Systems Engineering Handbook v.3.2.1 identifies several relevant points regarding product and service life management
Systems Engineering Guidebook for Intelligent Transportation Systems (ITS), version 1.1, provides guidance on product changes, and system retirement.
Blanchard and Fabrycky's Systems Engineering and Analysis (2005), emphasis design for supportability and provides a framework for product and service supportability, and planning for system retirement.
Seacord, Plakosh, Lewis. 2003. Modernizing Legacy Systems, identifies strategies for product and service modernization.
Office of the Under Secretary of Defense for Acquisition, Transportation, and Logistics (USD AT&L) Logistics and Materiel Readiness (http://www.acq.osd.mil/log/) provides on-line policies, procedures, and planning references for product service life extension, modernization and retirement.
Jackson, S. 2007. A Multidisciplinary Framework for Resilience to Disasters and Disruptions, provides insight into architecting a system for extended service life.
Typical Pitfalls that occur after Product and Service Deployment Major pitfalls associated with systems engineering after the deployment of products and services can be avoided if the systems engineer:
- Recognizes that the systems engineering process does not stop when the product or service becomes operational.
- Understands that certain life management functions and organizations, especially in the post-delivery phase of the life cycle, are part of the systems engineering process.
- Knows that modifications need to comply with the system requirements.
- Considers that the users must be able to continue the maintenance activities drawn up during the System Requirement phase after an upgrade or modification to the system are made.
- Accounts for changing user requirements over the system life cycle.
- Adapts the support concepts, drawn up during development, throughout the life cycle.
- Applies engineering change management to the total system.
Not addressing these areas of concern early in development, and throughout the product or service’s life cycle can have dire consequences.
Topics
The topics contained within this knowledge area include:
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
Blanchard and Fabrycky. 2006. Systems Engineering and Analysis, 4th edition. Prentice Hall International Series.
Defense Acquisition University (DAU). Acquisition Community Connection (ACC): Where the DoD AT&L workforce meets to share knowledge. DAU/US Department of Defense (database online). Ft. Belvoir, VA, USA, 2010 available from https://acc.dau.mil
INCOSE Systems Engineering Handbook v3.2.1. A Guide for System Life Cycle Processes and Activities. 2011. San Diego, CA, USA: International Council on Systems Engineering (INCOSE), INCOSE-TP-2003-002-03.2.1
Jackson. 2007. A Multidisciplinary Framework for Resilience to Disasters and Disruptions. Journal of Integrated Design and Process Science Volume 11 (2), IOS Press
OUSD(AT&L). 2011. Logistics and Materiel Readiness On-line policies, procedures, and planning references. Arlington, VA, USA: Office of the Under Secretary of Defense for Aquisition, Transportation and Logistics (OUSD(AT&L). Available at: http://www.acq.osd.mil/log/.
Seacord, Plakosh, Lewis. 2003. Modernizing Legacy Systems, Addison Wesley, Pearson Education Inc.
Systems Engineering Guidebook for Intelligent Transportation Systems ver 1.1. 2005. California Department of Transportation Division of Research and Innovation
Primary References
Blanchard and Fabrycky. 2006. Systems Engineering and Analysis, 4th edition. Prentice Hall International Series.
INCOSE. 2011. Systems Engineering Handbook: A Guide for System Life Cycle Processes and Activities. Version 3.2.1. San Diego, CA, USA: International Council on Systems Engineering (INCOSE), INCOSE-TP-2003-002-03.2.1
Jackson. 2007. A Multidisciplinary Framework for Resilience to Disasters and Disruptions. Journal of Integrated Design and Process Science Volume 11 (2), IOS Press
OUSD(AT&L). 2011. Logistics and Materiel Readiness On-line policies, procedures, and planning references. Arlington, VA, USA: Office of the Under Secretary of Defense for Aquisition, Transportation and Logistics (OUSD(AT&L). Available at: http://www.acq.osd.mil/log/.
Seacord, Plakosh, Lewis. 2003. Modernizing Legacy Systems, Addison Wesley, Pearson Education Inc.
Caltrans and USDOT. Systems Engineering Guidebook for Intelligent Transportation Systems (ITS) ver 1.1. 2005. Sacramento, CA, USA: California Department of Transportation (Caltrans) Division of Research and Innovation and U.S. Department of Transportation (USDOT), SEG for ITS 1.1.
Additional References
AWWA. AWWA manuals of water supply practices. in American Water Works Association (AWWA) [database online]. Denver, CO, USA, 2010Available from http://www.awwa.org/Resources/standards.cfm?ItemNumber=47829&navItemNumber=47834 (accessed August 5, 2010).
Blanchard, B. S. 2010. Logistics engineering and management. 5th ed. Englewood Cliffs, NJ, USA: Prentice Hall: p341-342.
———. 1992. Chapter 8. In Logistics engineering and management. 4th ed., 341-342. Englewood Cliffs, NJ, USA: Prentice Hall.
Blanchard, B. S., and W. J. Fabrycky. 2005. Systems engineering and analysis. Prentice-hall international series in industrial and systems engineering. 4th ed. Englwood Cliffs, NJ, USA: Prentice-Hall: p 541-565.
Braunstein, A. 2007. Balancing hardware end-of-life costs and responsibilities. Westport, CT, USA: Experture Group, ETS 07-12-18.
Brown, M., R. Weyers, and M. Sprinkel. 2006. Service life extension of virginia bridge decks afforded by epoxy-coated reinforcement. Journal of ASTM International (JAI) 3 (2) (February 2005): 13.
Caltrans, and USDOT. 2005. Systems engineering guidebook for ITS, version 1.1. Sacramento, CA, USA: California Department of Transportation (Caltrans) Division of Research & Innovation/U.S. Department of Transportation (USDOT), SEG for ITS 1.1 : p278, 101-103, 107.
Casetta, E. 2001. Transportation systems engineering: Theory and methods. New York, NY: Kluwer Publishers Academic, Springer.
DAU. Acquisition community connection (ACC): Where the DoD AT&L workforce meets to share knowledge. in Defense Acquisition University (DAU)/US Department of Defense (DoD) [database online]. Ft. Belvoir, VA, USA, 2010 Available from https://acc.dau.mil/ (accessed August 5, 2010).
DLA. Defense logistics agency disposition services [homepage]. in Defense Logistics Agency (DLA)/U.S. Department of Defense [database online]. Battle Creek, MI, USA, 2010 [cited June 19 2010]: p5. Available from http://www.dtc.dla.mil.
ECHA. European chemicals agency ( ECHA ) [home page]. in European Chemicals Agency (ECHA) [database online]. Helsinki, Finland, 2010 Available from http://echa.europa.edu/home_en.asp.
Elliot, T., K. Chen, and R. C. Swanekamp. 1998. Standard handbook of powerplant engineering. New York, NY: McGraw Hill, section 6.5.
EPA. Wastes. in U.S. Environmental Protection Agency (EPA) [database online]. Washington, DC, 20102010]. Available from http://www.epa.gov/epawaste/index.htm.
European Parliament. 2007. Regulation (EC) no 1907/2006 of the european parliament and of the council of 18 december 2006 concerning the registration, evaluation, authorisation and restriction of chemicals (REACH), establishing a european chemicals agency, amending directive 1999/45/EC and repealing council regulation (EEC) no 793/93 and commission regulation (EC) no 1488/94 as well as council directive 76/769/EEC and commission directives 91/155/EEC, 93/67/EEC, 93/105/EC and 2000/21/EC. Official Journal of the European Union 29 (5): 136/3,136/280.
FAA. 2006. Section 4.1. In Systems engineering manual. Washington, D.C.: U.S. Federal Aviation Administration (FAA).
FCC. 2009. Radio and television broadcast rules. Washington, D.C.: U.S. Federal Communications Commission (FCC), 47 CFR Part 73, FCC Rule 09-19: p 11299-11318.
Finlayson, B., and B. Herdlick. 2008. Systems engineering of deployed systems. Baltimore, MD, USA: Johns Hopkins University: p28.
FSA. Template for 'system retirement plan' and 'system disposal plan'. in Federal Student Aid (FSA)/U.S. Department of Eduation (DoEd) [database online]. Washington, DC, 2010Available from http://federalstudentaid.ed.gov/business/lcm.html (accessed August 5, 2010).
Gehring, G., D. Lindemuth, and W. T. Young. 2004. Break Reduction/Life extension program for CAST and ductile iron water mains. Paper presented at NO-DIG 2004, Conference of the North American Society for Trenchless Technology (NASTT), March 22-24, 2004, New Orleans, LA, USA.
Hovinga, M. N., and G. J. Nakoneczny. May 2000. Standard recommendations for pressure part inspection during a boiler life extension program. Paper presented at ICOLM (International Conference on Life Management and Life Extension of Power Plant), Xi’an, P.R. China.
IEC. 2007. Obsolescence management - application guide, ed 1.0. Geneva, Switzerland: International Electrotechnical Commission, IEC 62302.
IEEE. 2010 IEEE Standard Framework for Reliability Prediction of Hardware. New York, NY: Institute of Electrical and Electronics Engineers (IEEE), IEEE STD 1413.
IEEE. 1998 IEEE Standard Reliability Program for the Development and Production of Electronic Systems and Equipment. New York, NY: Institute of Electrical and Electronics Engineers (IEEE), IEEE STD 1332.
IEEE. 2008. IEEE Recommended practice on Software Reliability. New York, NY: Institute of Electrical and Electronics Engineers (IEEE), IEEE STD 1633.
IEEE 2008. ISO/IEC/IEEE Systems and Software Engineering – System Life Cycle Processes. Geneva, Switzerland: International Organization for Standardization, ISO 15288.
IEEE 2005. IEEE Standard for Software Configuration Management Plans. New York, NY: Institute of Electrical and Electronics Engineers (IEEE), IEEE STD 828.
Ihii, K., C. F. Eubanks, and P. Di Marco. 1994. Design for product retirement and material life-cycle. Materials & Design 15 (4): 225-33.
INCOSE. 2010. In-service systems working group. San Diego, CA, USA: International Council on Systems Engineering (INCOSE).
———. 2010. Life cycle management working group. San Diego, CA, USA: International Council on Systems Engineering (INCOSE).
INCOSE UK Chapter. 2010. Applying systems engineering to in-service systems: Supplementary guidance to the INCOSE systems engineering handbook, version 3.2, issue 1.0. Foresgate, UK: International Council on Systems Engineering (INCOSE) UK Chapter, p10, 13, 23.
Institute of Engineers Singapore. 2009. Systems engineering body of knowledge, provisional version 2.0. Singapore.
ISO/IEC. 2003. Industrial automation systems integration-integration of life-cycle data for process plants including oil, gas production factilies. Geneva, Switzerland: International Organization for Standardization (ISO)/International Electro technical Commission (IEC), .
Jackson, S. 2007. A multidisciplinary framework for resilience to disasters and disruptions. Journal of Design and Process Science 11 (2): p91-108, 10.
———. 1997. Systems engineering for commercial aircraft. Surrey, UK: Ashgate Publishing Ltd.
Koopman, P. Life cycle considerations. in Carnegie-Mellon University (CMU) [database online]. Pittsburgh, PA, USA, 1999Available from http://www.ece.cmu.edu/~koopman/des_s99/life_cycle/index.html (accessed August 5, 2010).
L3 Communications. 2010. Service life extension program (SLEP). Newport News, VA, USA: L3 Communications, Flight International Aviation LLC.
Livingston, H. 2010. GEB1: Diminishing manufacturing sources and material shortages (DMSMS) management practices. McClellan, CA, USA: Defense MicroElectronics Activity (DMEA)/U.S. Department of Defense (DoD).
Mays, L., ed. 2000. Water distribution systems handbook. New York, NY: McGraw-Hill Book Company: Chapter 3.
MDIT. 2008. System maintenance guidebook (SMG), version 1.1: A companion to the systems engineering methdology (SEM) of the state unified information technology environment (SUITE). MI, USA: Michigan Department of Information Technology (MDIT), DOE G 200: p38.
Minneapolis-St. Paul Chapter. 2003. Systems engineering in systems deployment and retirement, presented to INCOSE. Minneapolis-St. Paul, MN, USA: International Society of Logistics (SOLE), Minneapolis-St. Paul Chapter.
NAS. 2006. Natioanl airspace system (NAS) system engineering manual, version 3.1 (volumes 1-3). Washington, DC: Air Traffic Organization (ATO)/U.S. Federal Aviation Administration (FAA), NAS SEM 3.1.
NASA. December 2007. Systems engineering handbook. Washington, D.C.: National Aeronautics and Space Administration (NASA), NASA/SP-2007-6105.
Nguyen, L. 2006. Adapting the vee model to accomplish systems engineering on change projects. Paper presented at 9th Annual National Defense Industrial Association (NDIA) Systems Engineering Conference, San Diego, CA, USA.
Office of Natural Gas and Oil Technology. 1999. Reservoir LIFE extension program: Encouraging production of remaining oil and gas. Washington, DC: U.S. Department of Engery (DoE), .
OSHA. 1996. Hazardous materials: Appendix A: List of highly hazardous chemicals, tocixs and reactives. Washington, D.C.: Occupational Safety and Health Administration (OSHA)/U.S. Department of Labor (DoL), 1910.119(a).
Paks Nuclear Power Plant. Paks nuclear power plant: Service life extension. in Paks Nuclear Power Plant Ltd. [database online]. Hungary, 2010Available from http://paksnuclearpowerplant.com/service-life-extension (accessed August 5, 2010).
Reason, J. 1997. Managing the risks of organizational accident. Aldershot, UK: Ashgate.
Ryen, E. 2008. Overview of hte systems engineering process. Bismarck, ND, USA: North Dakota Department of Transpofration (NDDOT).
SAE International. 2010. Standards: Automotive--maintenance and aftermarket. Warrendale, PA, USA: Society of Automotive Engineers (SAE) International.
———. 2010. Standards: Commercial vehicle--maintenance and aftermarket. Warrendale, PA, USA: Society of Automotive Engineers (SAE) International.
———. 2010. Standards: Maintenance and aftermarket. Warrendale, PA, USA: Society of Automotive Engineers (SAE) International.
SEI. Software engineering institute. in Software Engineering Institute (SEI)/Carnegie-Mellon University (CMU) [database online]. Pittsburgh, PA, USA, 2010Available from http://www.sei.cmu.edu (accessed August 5, 2010).
Schafer, D.L. 2003. Keeping Pace With Technology Advances When Funding Resources Are Diminished. Paper presented at AUTOTESTCON 2003. IEEE Systems Readiness Technology Conference, Anaheim, CA :p 584.
SOLE. Applications divisons. in The International Society of Logistics (SOLE) [database online]. Hyattsville, MD, USA, 2009Available from http://www.sole.org/appdiv.asp (accessed August 5, 2010).
Sukamto, S. 2003. Plant aging and life extention program at arun LNG plant lhokseumawe, north aceh, indonesia. Paper presented at 22nd Annual World Gas Conference, 1-5 June, 2010, Tokyo, Japan.
FSA. Template for 'system retirement plan' and 'system disposal plan'. in Federal Student Aid (FSA)/U.S. Department of Education (DoEd) [database online]. Washington, DC, 2010Available from http://federalstudentaid.ed.gov/business/lcm.html (accessed August 5, 2010).
All additional references should be listed in alphabetical order.