Changes

__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 fieldsdomain. Information managers collectoversee the collection, process processing and analyse analysis of information to support decision making in operational activities, and planning and reporting. Information management is not an end in itself; rather. Although archiving is one of the roles of information management, it is definitely not the central role. Rather, information management is an activity that supports the primary goal of enables evidence-based decision making and increases transparency and accountability. Good information management is a pre-requisite to an effective and efficient mine action: reducing the impact of hazards on civilian populationsorganisation.

==Hazards 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 The process of clearing hazards follows an operational workflow that is reflected in information managementas a set of ''business rules''. As each step in the clearance process is completed, the primary [[object]] or focus status of the hazard changes so that the hazard eventually is a hazard, whether it cleared. It is a minefield, UXO spot or other ERW contamination, and the activities or [[processes]] undertaken role of information management to reduce or eliminate collect information about each step and accurately report the status and attributes of each hazard. Other important objects and as it makes its way through the workflow to assist in operational activities include accidentssuch as planning, victims, quality management tasking and mine risk education activitiesclearance operations. In certain programmes, these elements may take Whether a programme is implementing a land release model for hazard clearance or a more prominent rolerisk reduction model, with IMSMA^NG supporting them equally wellthe concepts are the same. Hazards are reduced and changed over time by various processes. HoweverTo implement this effectively in {{IMSMANG}}, information managers must first fully understand the traditional focus of information management workflow and business rules in use in mine action is on hazards and the processes done to eliminate themtheir programmes.

The process ==Information management needs assessment==__NOEDITSECTION__Before setting up {{IMSMANG}}, information managers should have an understanding of clearing hazards follows an operational workflow that is reflected in the information management as a set needs of business rules. As each step in their programmes and the clearance process is completed, attributes of the hazard change so workflows that eventually the hazard is clearedare used. It is Then they can begin designing 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 in {{IMSMANG}} to assist in operational activities such as planning, tasking and clearance operationsmeet those needs. Whether a programme is implementing a land release model for hazard clearance or a risk reduction model, The table below lists the information management concepts are to review along with 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 possible resources that may be available to help assess the workflow and business rules in use in their programmesneeds.

{| class="wikitable"!width =Objects==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== ==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.  [[ImageCategory:Understanding Mine Action Information Management - Needs Assessment.png|center|''Needs Assessment''NAA]]<div align="center">''{{NavBox Information Management Needs Assessment''</div>  ===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.}}