Understanding Mine Action Information Management

The practice of information management in mine action is similar to information management in other fields. Information managers collect, process and analyse information to support operational activities, planning and reporting. Information management is not an end in itself; rather, it is an activity that supports the primary goal of mine action: reducing the impact of hazards on civilian populations.

Contents

Hazards and Processes

In mine action information management, the primary object or focus is a hazard, whether it is a minefield, UXO spot or other ERW contamination, and the activities or processes undertaken to reduce or eliminate the hazard. Other important objects and activities include accidents, victims, quality management and mine risk education activities. In certain programmes, these elements may take a more prominent role, with IMSMA^NG supporting them equally well. However, the traditional focus of information management in mine action is on hazards and the processes done to eliminate them.

The process of clearing hazards follows an operational workflow that is reflected in information management as a set of business rules. As each step in the clearance process is completed, attributes of the hazard change so that eventually the hazard is cleared. It is the role of information management to collect information about each step and accurately report the status and attributes of each hazard as it makes its way through the workflow to assist in operational activities such as planning, tasking and clearance operations. Whether a programme is implementing a land release model for hazard clearance or a risk reduction model, the concepts are the same. Hazards are reduced and changed over time by various processes. To implement this effectively in IMSMA^NG, information managers must first fully understand the workflow and business rules in use in their programmes.

Information Management Needs Assessment

Before installing IMSMA^NG, information managers should have an understanding of the information management needs of their programmes and the workflows that are used. Then they can begin designing the information workflow in IMSMA^NG to meet those needs. The table below lists the information management concepts to review along with the possible resources that may be available to help assess the needs.

Needs Assessment

Information Management Needs Assessment

IMSMA Workflows and Business Rules

Rather than establishing one workflow that all programmes must use, IMSMA^NG allows information managers to establish their own programme-appropriate workflows and business rules to better support their specific needs. To document their programme-specific workflows, information managers describe the processes undertaken on each object in IMSMA^NG and the outputs or products from the processes. Typically, these workflows relate to the various categories of hazards and hazard reductions, but they can also be applied to other IMSMA^NG items as appropriate.

During this step, information managers map the process that each hazard goes through as it is cleared or its impact is otherwise reduced. Using a combination of the relevant hazard types, status values and relationships, information managers design an information workflow that will be implemented as standard operating procedures (SOPs) for data entry and analysis. Some programmes may have only one process for all categories of hazards while other programmes may have three or more processes.

Mapping the Workflows

The first element of mapping the hazard reduction workflow is to build a map of the relationship between the objects and processes involved in the hazard reduction process. Starting with the first representation of the hazard, the workflow map should describe the processes done to the hazard and the output of the process. The workflow map should trace the entire process from hazard identification through clearance and release of the land according to the operational process in use in the programme. In the example below, a confirmed hazardous area (CHA) is linked to a technical survey that was conducted on the hazard. The survey resulted in a minefield on which a clearance was done, and the clearance resulted in a cleared hazard. Finally, a completion survey was logged to close the hazard.

(figure)

This workflow map identifies the hazard reduction process that is used within the programme and can be mapped in IMSMA^NG to track the clearance of hazards. Because IMSMA^NG supports customisable workflows, it can be used to track different workflows for different objects. For example, a programme may have a separate abbreviated workflow for spot UXO tasks that involve only the identification of the UXO hazard (object) and a clearance of the hazard (process) without additional surveys or steps. This process should also be mapped for implementing in IMSMA^NG.

Status Changes

Along with a workflow map that describes the relationship between the various types of objects and processes in a workflow, the status changes or outputs from the process are critical in adequately mapping the hazard clearance process. IMSMA^NG uses the status value of items to track where the object or process is in its workflow. Objects and processes in IMSMA^NG can have different status values. For example, hazards can be defined as "Active", "Worked On," or "Closed," while hazard reduction activities that are more process-oriented can be "Planned," "Ongoing," "Completed," "Suspended," or "Aborted." Defining a set of status values for each item provides the capability to:

• manage workflows according to status
• search and report on items based on a particular status
• display items on the map with different symbols based on their status

Some IMSMA^NG items may have many status values. For example, process-oriented items such as hazard reductions and quality management likely have many status values, but hazards and other object- or output-oriented items typically have only the three status values listed above. Some items like victims and accidents may not need status values depending on how information is used. Defining the possible status values for each object in the workflow as outputs of the processes conducted on them provides a set of business rules for information management that govern how information should be entered and analysed.