Hi guys, welcome back again. So in this video we are going to look system maintenance practices. What does system maintenance means? Think about it. System maintenance means making some change to the system, to make systems better. So that is what we call system maintenance, even if you buy a package, or if you buy the Microsoft package or SAP. So those are very expert system developers, but still. Those packages need to make some change, all the time. So the system maintenance is extremely important. And why do we want to do it? Because we want to make system better, because systems seldom remains static. As I mentioned too, it could be in-house development, it could be package, it could be customized made for you guys. No matter whatever it is the maintenance is extremely important part of the system. But later on we are going to talk about something very important issue here. So if you outsource your system development process, maintenance could be, it's a bit challenging to you guys. Because, you may be living in US, but the developers could be from India. So they would develop systems and the they would come to US and develop the system to you guys and implement it, and they'd go back to India. So if there's any problem found in your system, do they have time to fly back to US all the time? I don't think so. So that's going to be challenging of the system development, so that's something you guys need to think about. Okay, right. So how we do that? The next slide, we look at it, who will request a system maintenance practice because if system is maintenance test to be done, who will? Basically, whoever will have interaction with the system that is the users with the system. So who are the possible users will make a request to change the system. It could be senior management. It could be staff in your organization. It could be a client to your organization. It could be a customer. Or it could be something like internal auditor or external auditor would come and audit your system and make some recommendations and request some maintenance. In the next slide, how do we make this request? So in a large organization, they do have procedures of system maintenance. Do you have any idea how we do it? Yes, they do have a request form. So the larger organizations, they prepared beforehand a specific forms, mostly online form. So whoever would want to request any change to the system, they go to the online form and they fill it. What kind of information that you'll see there? Of course your name, and the date, and why you want to have the change. That means you find something, you find a problem with the system, or you want a new feature to the system. Or you think that, okay, I prefer to have it Spanish as the interface. So whatever the reasons that we have it, at the same time then you should let the IT people know what is the expected benefits. As well as important we are here, because IT department may receive many, many requests in a given period of time. So at the end of the day need to prioritize it. Which one is higher which one is lower? So according to your understanding, according to your expectations, what is the priority for this new term development? That's something new you might take to inform them as well. So users fill in the forms and submit the form to the IT department. So what IT department do is to review those forms and decide they made their own judgment and they do prioritize based own their own judgment. Of course they would take whatever that you mention into account very important to you. Then what are system maintenance practices we have? So we do have basically four maintenance practices. Corrective, Adaptive, Perfective, and Preventive. Now, I would like us to remember, we look at similar words before, which are controls. But controls and maintenance are different to each other. So I would like to think about it. What is the connection between controls and the maintenance that we have discussed before. So in the past we talk about preventive control, detective control and corrective control. Now we're talking about the maintenance corrective, adaptive, perfective and preventive. Are they related? How are they related? It's something that I would like you guys to think about. So now it's time for us to look at one by one, what is a Corrective Maintenance means? I think it's very easy to judge, right? We find a problem within the system and then we rectify that. So that is what we call Corrective maintenance, find a problem with the system, we fix it. That's a correction. Then we have called adaptive maintenance. What is adaptive maintenance means? Adaptive maintenance means you should add in a new feature or capability to systems producing outputs. And then users, management would like to have new features to the system. So that's called adaptive maintainance. Let's go on. So now let's look at perfective maintenance. What is perfective maintenance means? Perfective maintenance, we don't make any change to the system capability, but we make simply make system much more efficient and user friendly. In the next video I'm going to talk to you guys some examples to explain better what is exactly perfective maintenance means. So please keep watching the video so that you will have a better understanding. Especially next one. I'm going to talk to you guys about some scenarios, example, so what are the Perfectly maintenance and preventive maintenance. Is similar to the preventive controls? So it's basically we would like to prevent the systems, maybe hack into the systems or maybe add the features to that. So that is the basically those four different kind of maintenance we have. Now I would like you guys think about, as I mentioned to you before, the IT department received many, many mentors request in a given period of time. So in general, they have to prioritize them. So in general, which maintenance should come before the others? Can you guys spend about one minute, think about it and write down one, two, three, four based on what you think which one should come first and which one should come second, third and fourth, so and so forth. Yes, which one is first, I think that you got it right, the first one is corrective maintenance. Because correcting a problem has to be your priority. What's the next one, I think you got it right as well, that is preventive maintenance. Then it's always student find difficult to find three and four. So basically which one should come? Number three is should come adaptive and the number four is perfective. Because the perfective maintain, we do not make any change to system capability. Make system is more user friendly, understand? So this is something that we need to look into last. Okay, now let's look at the how the system maintenance costs changed. And then we have two lines - cost and the time. And times start zero is the time that you implement system. As soon after you implement system, time clock starts. How does this maintenance cost change? I would like to think about a minute and draw this graph. First maintenance cost starting very high and coming down. Does it come down to zero? So that means there's no maintenance at all for the system? I don't think so. So the next step would be the system is stable now. We find some problem to the system and we fix those, and the system is stable now, for some time. What's happening, is it going to be stable forever? Now, at the last stage, it's going to go up, okay? So now let's see why is going to go up, we're going to look at it next. So first of all I put A and B. So in other words, what kind of maintenance that we mostly do at A, as well as what kind of maintenance we mostly do at B. What do you think? Soon after system has been implemented, what kind of maintenance we always do? Remember, before we implement system, we did a lot of testing. But of course, real test is when you use the system. So when you use the system, you might find problems, you might find bugs within system. So at the beginning, at the early stage, we do a lot of corrective maintenance. After some time we have done corrective maintenance, systems is going to be stable now. Now, tell me, what is going to be B? B is the latest stage of the system usage, then mostly about adaptive maintenance. Remember, by the time that we develop system, we communicate with the users and get the requirement to your system. We have done it, so users told us what are the features they need. Now it's already about five years, maybe ten years passed. So now it's very possible that users would like to have additional features to the system, additional capabilities to the system, so they might submit, adaptive maintenance. So now the cost is going to be up and up. Judgment for you guys, are they keep adding whatever the users asked requesting? Now this is a basically good indication that having a lot of adaptive means come to system rather than adding one by one to your whole system. This is an indication now. This is time for us to think about developing new system at all the features that they would like have into new system. So that is the time to think about it. [MUSIC]
