TECC 249: Life Cycle Engineering and How It Fits Into Integrated Product Support

In this episode, we talk to Lucas Marino, D.Eng., PMP, CMRP, a systems engineer and integrated logistics support manager - entrepreneur, and owner of EAST Partnership and MCS, LLC, about life cycle engineering and how it fits into integrated product support. Engineering Quotes: Here Are Some of the Key Points Discussed About Life Cycle Engineering and Integrated Product Support Military logistics engineering is everything you must do to sustain and care for complex weapons systems once they are built. It includes things like training the crew, supply chain, maintenance, and many more. Most of the analysis is during the logistics product development. The analysis provides data on reliability, the criticality of failure, how to design suitable maintenance programs, reduce the risk of failures, and maintenance strategies. The accumulated data contributes to the maintenance task analysis and level of repair analysis. In the military, having the asset available and fully functional is always goal number one. Life cycle engineering can get extremely complicated very quickly. It must be brought to the fundamentals and the basics. Do not get caught up in making things even more intricate. Ensure that the correct level of maintenance and analysis is plotted in your plan before the work starts and is then iteratively updated during the work. Communication is vitally important in life cycle engineering. Ensure you have the correct stakeholders involved to be sure you are communicating with the right people. When putting a team together, ensure that they will account for the end user, or the analysis will be flawed. To do this, you must select the right people based on how they will communicate and integrate into the team. Once you have a team, you need to put a routine in place with a pace and an expected level of interaction. When you have all these paths of communication, you are also managing expectations. Team leaders will gain trust if they are transparent and deliver enough guidance for the team to succeed. You cannot spend a year developing a strategy that will not help the end user. If a task needs completing, it is sent to a particular team to get it done. For that team to get the work done, the maintenance task analysis then develops a step-by-step procedure, on that system, in that operating context. So, you do the maintenance task analysis in the operation or environmental context of the asset. You then develop the procedure with those people and resources and then find out what technicians, parts, supplies, consumables, training, and technical manuals are needed. The maintenance task analysis documents everything that was done and stored in your repository of logistics data. All the data captured over the years is then taken into consideration when putting a strategy together. Things like how much work there is, how long it will take, what equipment and tools are needed, and what it will cost are assembled and used to predict the resource demands that are given to the end users. A master project programmer or manager figures out how to extract the most value from many project management methods and approaches and brings them together. Tailored ways on how to combine bureaucratic and agile teams are needed. You must assess the context operation of your project, figure out what is going to work best, and what tools you need to have in place—and remember that risk is the blanket that covers everything. You must bring the technical and business sides together in a way that supports the project. Time is of the essence, and the budget is not infinite. Work with people ahead of the charter development to properly account for the time you anticipate it will take. When working for the different sectors of the military, remember that while they all have similar approaches, they are all entirely different.