The final stage of the systems engineering process is in service monitoring and update stage 13. We have gone through a series of activities to get to this point in the systems engineering process. We have gone from the operational lead all the way to the production and deployment. We are now at the point where the system, system a system or enterprise system is deployed. And now it's operating, it's functioning and it's part of a regular process. What do you need to do there? Well, first of all the system's out there so you need to manage it. You need to understand what is there, what needs to be taken care of, technically, logistically, and in some cases, from a healthcare perspective. How do you change that system? We all know that when a system is deployed, it is not perfect. We need to make modifications and how do you do change management? How would you do that? If you had a number of systems out there, how would you change that and make sure that you had proper configuration control? Also, there's the idea of delivery of the service, that is, you've deployed something, how does it fit into the workflow of what's going on into the ICU, or the hospital or some other area? How do you make sure that that is accomplished? Also, the idea that all systems break down in some way. So how can you optimize that supply chain such that you have the proper logistics maintenance to keep that thing running? There is all kinds of different things to consider while it's in service. One thing that we want to make sure of, is that we are tracking what's going on. If we don't track what's going on, we won't be able to collect the data that we need in order to determine how we actually improve things over time. Elaborating a bit on stage 13 of the systems engineering process, in service monitoring and updates, we talked earlier about managing change, using delivery of the service and putting together a supply chain. Here are some detailed items to consider when you think of those four areas. First of all, areas need to be recertified. Something is built, something is deployed, but you need to make sure on a regular basis that it's functioning and working properly. That is a certification approach. Also, you need to test on a regular basis. You just can't use the equipment and assume it's always going to work. You need to test it and collect data to make sure that it's going to function properly. Make sure that you are aware of what environment your system is actually being put in, because your environment can have a huge impact, make sure you understand that. Also, the logistics and the supply chain. We talked about systems breaking down and needed the supply chain in order to replenish it. But also, during the deployment and as you get more units out there, there's the supply chain and the logistics for deployment as well. Make sure that you have a regular maintenance and update schedule. Make sure that you're clear on what is available when and what needs to maintain when, very important as well as training. You are deploying new capabilities, new technology. If people don't know how to use it, it's not going to do any good. Make sure that your training is up to date and on a regular basis. And also, monitor operations. How is your system being operated, and is it being done properly? All these come together because what we discover is that over time, this system becomes the new baseline. And remember when we talk about a baseline, over time, there won't be needs, and there will be gaps. And so understanding what this is, will allow you to develop your new baseline so you can better improve the system over time. What we have done over the last several slides is talk through an exemplar systems engineering approach. We ended up with in service monitoring and updates. But remember what I said is that creates the new baseline, and as we go through the process, we will do this all over again. There is a new baseline. When we have that baseline, recognize that it's not perfect, and we need to update and we will figure out over time, what are those needs? Then what are those operational requirements? And then we will go through this process all over again. The good news is we will have a background of information and an approach to be able to enable us as we go through the process again. What we don't want to do is start all over again having this baseline knowledge of a systems engineering approach. Having gone through it, will enable us to go through it in a more efficient fashion next time. As with the previous modules, I have reflective questions at the end of this module as well. Think through, what is systems engineering? Early on in this module we talked about what is systems engineering, but also remember there's systems of systems engineering, as well as enterprise systems engineering. Think through all the stages we went through, why we need those stages, and think through what activities that we talked in detail that go on in those stages. And what are those areas that you think is the most critical in the systems engineering process? Each one of the stages holds an important role but just think through what you think is the most critical and why.
