Difference between revisions of "Understanding Mine Action Information Management"

From IMSMA Wiki
Jump to: navigation, search
 
(39 intermediate revisions by 6 users not shown)
Line 1: Line 1:
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.
+
__NOEDITSECTION__
 +
'''Understanding Mine Action Information Management''' is a prerequisite to be a good information manager in a Mine Action program. The practice of information management in mine action is similar to information management in any other domain. Information managers oversee the collection, processing and analysis of information to support decision making in operational activities and planning and reporting. Information management is not an end in itself. Although archiving is one of the roles of information management, it is definitely not the central role. Rather, information management is an activity that enables evidence-based decision making and increases transparency and accountability. Good information management is a pre-requisite to an effective and efficient mine action organisation.
  
==Hazards and Processes==
+
==Objects and Processes==__NOEDITSECTION__
 +
In mine action information management, the primary object or focus is contaminated land and the activities or processes undertaken to reduce or eliminate the contamination in a process called [http://www.gichd.org/operations/land-release-and-operational-efficiency/overview/ land release]. Other important objects and processes include [[Accident Summary Window | Accidents]], [[Victim Summary Window | Victims]], [[Assistance Summary Window | Assistance]], [[QM Summary Window | Quality Management]] and [[Education Summary Window | Risk education]]. Although it is not the standard situation, these elements may sometimes take the prominent role from the land release process in some mine action programmes.
  
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<sup>NG</sup> 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, the status of the hazard changes so that the hazard eventually 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 {{IMSMANG}}, information managers must first fully understand the workflow and business rules in use in their programmes.
  
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<sup>NG</sup>, information managers must first fully understand the workflow and business rules in use in their programmes.
+
==Information management needs assessment==__NOEDITSECTION__
 +
Before setting up {{IMSMANG}}, 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 {{IMSMANG}} 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.
  
==Objects==
+
{| class="wikitable"
 +
!width =130px|IM cycle step
 +
! Possible Resources
 +
|-
 +
| '''Data collection'''
 +
* Reports collected from mine action actors
 +
* Existing databases
 +
|
 +
* '''Data collection forms:''' Programs often have existing data collection forms or spreadsheets that describe what information must be collected from operators or key stakeholders. These forms can serve as the basis for data collection forms in {{IMSMANG}}. It is important, however, to critically assess the information provided by these forms since existing forms may not accurately reflect current data collection needs and may have more information than necessary.
 +
* '''Information systems''': Whether databases, spreadsheets or GIS, existing information systems can provide a key source of information requirements for {{IMSMANG}}. Often, these information systems document the specific information the programs must collect and report on and so serve as a valuable source for detailing information needs.
 +
* '''Information consumers''': It is important to collect information about decisions made in mine action programs by interviewing consumers of information. Often, existing data collection forms, reports and systems do not fully represent the needs of the consumers or users of this information. While implementing {{IMSMANG}}, it is an ideal time to readdress the needs of these information users to determine how additional requirements can easily be met using {{IMSMANG}}.
 +
|-
 +
| '''Information use'''
 +
* Prioritising
 +
* Tasking
 +
* Operations and planning
 +
| '''Mine action processes''': Assessing existing and planned processes and their required information is a key source of information for this activity and allows the {{IMSMANG}} system to be customised to accurately support these processes. It is important, however, that these processes correspond to the actual operational needs of the mine action programme.
 +
|-
 +
| '''Information dissemination'''
 +
* Monthly progress reports
 +
* Statistical reports
 +
* Treaty obligations reports
 +
| '''Reports''': Donor reports, monthly or quarterly reports, statistical reports, reports supporting the Ottawa convention and other reports provide details about information that must be collected and managed in {{IMSMANG}}.
 +
|}
  
==Processes==
+
[[Category:NAA]]
 
+
{{NavBox Information Management}}
==Information Management Needs Assessment==
 
 
 
Before installing IMSMA<sup>NG</sup>, 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<sup>NG</sup> 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.
 
 
 
 
 
[[Image:Understanding Mine Action Information Management - Needs Assessment.png|center|''Needs Assessment'']]
 
<div align="center">
 
''Information Management Needs Assessment''
 
</div>
 
 
 
 
 
===IMSMA Workflows and Business Rules===
 
 
 
Rather than establishing one workflow that all programmes must use, IMSMA<sup>NG</sup> 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<sup>NG</sup> 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<sup>NG</sup> 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.
 
 
 
figure at bottom
 
 
 
====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.
 
 
 
 
 
[[Image:Understanding Mine Action Information Management - Mapping workflow.png|center|''Mapping the Workflow'']]
 
<div align="center">
 
''Mapping the Workflow''
 
</div>
 
 
 
 
 
This workflow map identifies the hazard reduction process that is used within the programme and can be mapped in IMSMA<sup>NG</sup> to track the clearance of hazards. Because IMSMA<sup>NG</sup> 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<sup>NG</sup>.
 
 
 
====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<sup>NG</sup> uses the status value of items to track where the object or process is in its workflow. Objects and processes in IMSMA<sup>NG</sup> 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<sup>NG</sup> 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.
 
 
 
====Example Workflows with Status Changes====
 
 
 
The following figures show how each programme can tailor the system to support a specific hazard clearance/reduction workflow process for each type of hazard, from a traditional process for minefield clearance with multiple steps including a technical survey, clearance and completion survey to a simplified process for UXO clearance that includes only a clearance. Each example involves a single hazard on which one or more hazard reduction activities are conducted. At each step, information about the hazard’s status and type is updated as a result of the hazard reduction process.
 
 
 
In the figure below, a CHA is created and its status is set to "Active." A technical survey process is then conducted on the hazard which results in changing the subcategory of the hazard from "CHA" to "Minefield" and defining the hazard’s perimeter. Next, a clearance process is conducted on the minefield that results in updating the status of the hazard to "Worked On." Finally, a completion survey is submitted that updates the status of the hazard to "Closed."
 
 
 
 
 
[[Image:Understanding Mine Action Information Management - Example Workflow.png|center|''Example of a Traditional Workflow'']]
 
<div align="center">
 
''Example of a Traditional Workflow''
 
</div>
 
 
 
 
 
Simpler processes can be defined for other types of hazards. For example, a spot UXO task would likely not go through this complete workflow and instead start with a subcategory of "UXO" and a status of "Open." A clearance could then be conducted and the UXO spot status updated to "Closed," without requiring a completion survey.
 
 
 
 
 
[[Image:Understanding Mine Action Information Management - Example Workflow 2.png|center|''Example of a Spot UXO Workflow'']]
 
<div align="center">
 
''Example of a Spot UXO Workflow''
 
</div>
 
 
 
 
 
By documenting the entire process conducted on each type of hazard, including the changes in status and type that result from the hazard reduction activities, information managers create a complete map of the hazard/hazard reduction workflow that informs how linking and reconciliation decisions should be made and provide a guide to data entry personnel.
 
 
 
====Progress Reporting Structure====
 
 
 
Once the hazard and hazard reduction relationships and workflow are defined and documented for each type of hazard, the next step is to define how progress data for the hazard clearance processes is collected. Traditionally, incremental progress data is collected using progress reports. These reports are typically linked to the overall clearance operation and are used to collect the incremental progress for a reporting period, usually, the number of mines/UXO cleared, area cleared and hours worked. In IMSMA<sup>NG</sup>, each progress report is stored as a new hazard reduction activity and linked to the clearance. As a result, individual progress reports can be queried to determine how much progress was made during a given reporting period. In addition, aggregate progress information can be queried for each clearance (for example, the total mines that have been reported cleared for a given clearance operation).
 
 
 
An alternative approach to storing progress information is to collect incremental progress reports and reconcile them as updates to the clearance using the combine option during reconciliation. Using this method, progress reports do not create independent hazard reduction items; rather, their information is combined with, and added to, the clearance information collected to that point. This approach simplifies the reconciliation step for progress reports as well as provides a simple summary of clearance data on each hazard in the current view. It may, however, become slightly more complicated to determine progress during individual reporting periods. Information managers should assess which approach better meets the needs of their programs when selecting an approach to tracking progress.
 
 
 
In the example below, progress reports were collected for three separate reporting periods during a clearance operation. Collecting and linking information in this way makes it easy to determine that in Period 2 (PR-2), 4,500 sqm were cleared and 25 AP mines were found and that, overall, 15,000 sqm were cleared and 61 AP mines were found. A defined, standardized approach to collecting and storing progress information simplifies querying and reporting of statistical information and is a critical element to supporting operational mine action information management needs.
 
 
 
 
 
[[Image:Understanding Mine Action Information Management - Progress Report Workflow.png|center|''Progress Report Workflow'']]
 
<div align="center">
 
''Progress Report Workflow''
 
</div>
 

Latest revision as of 12:10, 5 October 2016

Understanding Mine Action Information Management is a prerequisite to be a good information manager in a Mine Action program. The practice of information management in mine action is similar to information management in any other domain. Information managers oversee the collection, processing and analysis of information to support decision making in operational activities and planning and reporting. Information management is not an end in itself. Although archiving is one of the roles of information management, it is definitely not the central role. Rather, information management is an activity that enables evidence-based decision making and increases transparency and accountability. Good information management is a pre-requisite to an effective and efficient mine action organisation.

Objects and Processes

In mine action information management, the primary object or focus is contaminated land and the activities or processes undertaken to reduce or eliminate the contamination in a process called land release. Other important objects and processes include Accidents, Victims, Assistance, Quality Management and Risk education. Although it is not the standard situation, these elements may sometimes take the prominent role from the land release process in some mine action programmes.

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, the status of the hazard changes so that the hazard eventually 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 IMSMANG, information managers must first fully understand the workflow and business rules in use in their programmes.

Information management needs assessment

Before setting up IMSMANG, 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 IMSMANG 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.

IM cycle step Possible Resources
Data collection
  • Reports collected from mine action actors
  • Existing databases
  • Data collection forms: Programs often have existing data collection forms or spreadsheets that describe what information must be collected from operators or key stakeholders. These forms can serve as the basis for data collection forms in IMSMANG. It is important, however, to critically assess the information provided by these forms since existing forms may not accurately reflect current data collection needs and may have more information than necessary.
  • Information systems: Whether databases, spreadsheets or GIS, existing information systems can provide a key source of information requirements for IMSMANG. Often, these information systems document the specific information the programs must collect and report on and so serve as a valuable source for detailing information needs.
  • Information consumers: It is important to collect information about decisions made in mine action programs by interviewing consumers of information. Often, existing data collection forms, reports and systems do not fully represent the needs of the consumers or users of this information. While implementing IMSMANG, it is an ideal time to readdress the needs of these information users to determine how additional requirements can easily be met using IMSMANG.
Information use
  • Prioritising
  • Tasking
  • Operations and planning
Mine action processes: Assessing existing and planned processes and their required information is a key source of information for this activity and allows the IMSMANG system to be customised to accurately support these processes. It is important, however, that these processes correspond to the actual operational needs of the mine action programme.
Information dissemination
  • Monthly progress reports
  • Statistical reports
  • Treaty obligations reports
Reports: Donor reports, monthly or quarterly reports, statistical reports, reports supporting the Ottawa convention and other reports provide details about information that must be collected and managed in IMSMANG.