ABSTRACT
In today’s world, the business environment is continuing to grow globally, which in result is increasing its complexity. A normal business environment does not constitute a single point of control or management; instead it has become a common for a typical business environment to be shared among multiple groups. The enterprise structure as defined by the organizational chart is refined and replaced by the by the virtual enterprise, defined by the project (mission). As a result of the complexity of the present business environment and enterprise structure, it is unrealistic to use the conventional risk analysis techniques. These techniques have been proven deficient to handle the complexity and risks of the present business structure, this arose a need and requirement to develop a new and innovative approach – Mission Assurance Analysis Protocol (MAAP). This defines an advanced, systematic approach for analyzing operational risk and gauging mission assurance in complex work processes . The risk management approach helps the manager’s deal with different kinds of dependencies among data, technologies, tasks, activities and risks among different global environments.
MISSION ASSURANCE
Mission assurance is taking due care to reduce the operational risk to a mission to an acceptable level. There is not universal definition for mission assurance, but there is some commonality involved each of the definitions: the belief, conviction, that mission objectives will be satisfactorily achieved. Mission assurance is not a binary attribute that is either present in or absent from a given situation. The degree of mission assurance inherent in a work process is inversely related to the amount of operational risk affecting that process [4]. Hence the desired level of assurance is achieved when operational risk to the mission is kept within tolerance.
The basic strategy of mission assurance is illustrated in Fig. 1 and it illustrates the importance of striking a balance between operational risk management and problem resolution activities. Greater risk is an indicator of a greater number and severity of problems during operations [4]. But there are situations where the management allots too many tasks to handle with multiple resources, to handle and increasing series of crisis, leaving very few workers available to work toward obtaining the mission objectives. But in some cases, operational risk within tolerance also minimizes problems, hence resulting an easier way to handle the problems. The three fundamental tactics for achieving mission assurance are also illustrated in the figure below (Fig. 1). The first main and important tactic is to discern the operational risks that are involved in the project or the mission that is being developed. Most of the time the developers lack, sufficient appreciation of the operational environment in which the processes are bound to be used. It’s a very common mistake made by most of the developers, where they tend to overlook importance of dealing with risks prior to the operations being performed. They tend to leave it to the next group of people to deal with, during the time of execution. This is one of the major mistakes made by the developers because risks are bound to occur and also can be mitigated, while in some cases, they can be avoided altogether when a process is still in the planning stages.
In today’s world, the business environment is continuing to grow globally, which in result is increasing its complexity. A normal business environment does not constitute a single point of control or management; instead it has become a common for a typical business environment to be shared among multiple groups. The enterprise structure as defined by the organizational chart is refined and replaced by the by the virtual enterprise, defined by the project (mission). As a result of the complexity of the present business environment and enterprise structure, it is unrealistic to use the conventional risk analysis techniques. These techniques have been proven deficient to handle the complexity and risks of the present business structure, this arose a need and requirement to develop a new and innovative approach – Mission Assurance Analysis Protocol (MAAP). This defines an advanced, systematic approach for analyzing operational risk and gauging mission assurance in complex work processes . The risk management approach helps the manager’s deal with different kinds of dependencies among data, technologies, tasks, activities and risks among different global environments.
MISSION ASSURANCE
Mission assurance is taking due care to reduce the operational risk to a mission to an acceptable level. There is not universal definition for mission assurance, but there is some commonality involved each of the definitions: the belief, conviction, that mission objectives will be satisfactorily achieved. Mission assurance is not a binary attribute that is either present in or absent from a given situation. The degree of mission assurance inherent in a work process is inversely related to the amount of operational risk affecting that process [4]. Hence the desired level of assurance is achieved when operational risk to the mission is kept within tolerance.
The basic strategy of mission assurance is illustrated in Fig. 1 and it illustrates the importance of striking a balance between operational risk management and problem resolution activities. Greater risk is an indicator of a greater number and severity of problems during operations [4]. But there are situations where the management allots too many tasks to handle with multiple resources, to handle and increasing series of crisis, leaving very few workers available to work toward obtaining the mission objectives. But in some cases, operational risk within tolerance also minimizes problems, hence resulting an easier way to handle the problems. The three fundamental tactics for achieving mission assurance are also illustrated in the figure below (Fig. 1). The first main and important tactic is to discern the operational risks that are involved in the project or the mission that is being developed. Most of the time the developers lack, sufficient appreciation of the operational environment in which the processes are bound to be used. It’s a very common mistake made by most of the developers, where they tend to overlook importance of dealing with risks prior to the operations being performed. They tend to leave it to the next group of people to deal with, during the time of execution. This is one of the major mistakes made by the developers because risks are bound to occur and also can be mitigated, while in some cases, they can be avoided altogether when a process is still in the planning stages.
