Skip to main content

Improving Lifecycle Product Data Management (LPDM) Within the US Army Research, Development, and Engineering Command (RDECOM)

  • Conference paper
  • First Online:
Disciplinary Convergence in Systems Engineering Research

Abstract

This paper discusses the challenges of, and value in, implementing a lifecycle approach to management of the extensive and complex product data required in the engineering design, acquisition, and sustainment of military systems. The current state of Army management of product data and the future solution, the development of a well-integrated Lifecycle Product Data Management (LPDM) system, are discussed with three challenge examples and their related solutions (clean and accurate data, Configuration Management and control, and data sharing). The difference between a subordinate enterprise Product Data Management (ePDM) system, and an overarching LPDM system, is discussed, along with early designing for supportability (engineering) and the acquisition of supporting supplies and equipment (logistics). The paper is then summarized highlighting the advantage to the warfighter when a well-integrated LPDM is in place.

This is a preview of subscription content, log in via an institution to check access.

Access this chapter

Chapter
USD 29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
USD 259.00
Price excludes VAT (USA)
  • Available as EPUB and PDF
  • Read on any device
  • Instant download
  • Own it forever
Hardcover Book
USD 329.99
Price excludes VAT (USA)
  • Durable hardcover edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Purchases are for personal use only

Institutional subscriptions

References

  1. Trade-offs and analyses are accomplished throughout the design process following classical Systems Engineering conceptual system design and preliminary system design. It is important that the results of these analyses be adequately documented to support design decisions. The reports identified here may be newly generated, or reports prepared during conceptual and preliminary system design that have been updated to reflect new information

    Google Scholar 

  2. Blanchard BS, Fabrycky WJ (1998) Systems engineering and analysis, 3rd edn. Prentice Hall, Upper Saddle River

    Google Scholar 

  3. Such standards may include ISO or ANSI standards or those prepared by professional societies (Institute of Electrical and Electronic Engineers (IEEE), American Society for Quality Control (ASQC), Society of Manufacturing Engineers (SME), American Society of Civil Engineers (ASCE)) or industry associations (Electronic Industries Association (EIA))

    Google Scholar 

  4. Haduch TW, Abaie M (2016) “Lifecycle Product Data Management (LPDM),” Presentation delivered to Christopher J. Lowman, Deputy Assistant Secretary Acquisition Policy and Logistics, 2 June 2016; and Thomas W. Haduch and Michael Abaie, “Lifecycle Product Management (LPDM),” Presentation delivered to Brigadier General (BG) Thomas H. Todd III, 28 June 2016

    Google Scholar 

  5. Baldwin KJ (2016) Systems Engineering Overview. Presentation delivered at the Conference on Systems Engineering Research (CSER), 22 March 2016

    Google Scholar 

  6. Randall S. (2016) Newton, “A digital stitch in time.” DE: Technology for Optimal Design Engineering, July 2016

    Google Scholar 

  7. Stackpole B (2016) Microsoft flexes its Agile Muscles. DE: Technology for Optimal Design Engineering, July 2016

    Google Scholar 

  8. Taylor DP (2016) Keep them flying. Seapower, May 2016

    Google Scholar 

  9. Lifecycle Product Data Management (LPDM) Integrated Product Team (IPT) Charter

    Google Scholar 

  10. Haduch TW (2015) RDECOM charts the way ahead for systems engineering. Army Technology Magazine, May/June 2015

    Google Scholar 

  11. Haduch TW (2015) Model based systems engineering. Army Technology Magazine, May/June 2015

    Google Scholar 

  12. “The US Army Research, Development and Engineering Command,” Command presentation dated 16 May 2016

    Google Scholar 

  13. The scope of activity is sometimes identified by the term Logistic Support Analysis (LSA), Maintenance Analysis (MA), Maintenance Engineering Analysis (MEA), Maintenance Level Analysis (MLA), or something equivalent. However, the objectives are the same

    Google Scholar 

  14. For defense systems, SA is covered in MIL-HDBK-502, “DOD Handbook-Acquisition Logistics,” Department of Defense, Washington, DC, May 1997. The data requirements, evolving from SA (or Logistics Management Information), are specified in Government Electronic and Information Technology Association (GEIA)-STD-0007, Rev B, dated 1 May 2013 (this replaces MIL-PRF-49506. The emphasis here is on the SA process

    Google Scholar 

Download references

Author information

Authors and Affiliations

Authors

Corresponding author

Correspondence to Thomas W. Haduch .

Editor information

Editors and Affiliations

Rights and permissions

Reprints and permissions

Copyright information

© 2018 Springer International Publishing AG

About this paper

Check for updates. Verify currency and authenticity via CrossMark

Cite this paper

Haduch, T.W., Bruff, R.S., Martinell, P.M. (2018). Improving Lifecycle Product Data Management (LPDM) Within the US Army Research, Development, and Engineering Command (RDECOM). In: Madni, A., Boehm, B., Ghanem, R., Erwin, D., Wheaton, M. (eds) Disciplinary Convergence in Systems Engineering Research. Springer, Cham. https://doi.org/10.1007/978-3-319-62217-0_30

Download citation

  • DOI: https://doi.org/10.1007/978-3-319-62217-0_30

  • Published:

  • Publisher Name: Springer, Cham

  • Print ISBN: 978-3-319-62216-3

  • Online ISBN: 978-3-319-62217-0

  • eBook Packages: EngineeringEngineering (R0)

Publish with us

Policies and ethics