Changes

==Data Types=Items=__NOEDITSECTION__===Core Data===__NOEDITSECTION__In the {{IMSMANG}} information model, items are the containers for core data, such as mine action data. An item is an area, activity or event that a programme records information about and stores in {{IMSMANG}}. There are six categories of items, which are described in the table below. Each category can be characterised by a type that reflects whether the item is designed to track process or activity information or the object or product of an activity.

In the IMSMA<sup>NG<{| class="wikitable"! Item! Description! Type|-| Land| Information about an area| Object/sup> information modelProduct|-| Activity| Information about an activity, such as efforts to survey, items are the containers for mine action information. An item is an areaclear, activity or event that reduce the threat of a mine action programme records information hazard| Process/Activity|-| Accident| Information about and stores in IMSMA<sup>NG<an accidental event| Object/sup>. There are six categories of items, which are described in the table below. Each category can be characterized Product|-| Victim| Information about a person injured or affected by an accident| Object/Product|-| Assistance| Information about assistance for a type that reflects whether the item is person injured or affected by an accident| Process/Activity|-| Education activity| Information about an activity designed to track process inform or educate people (e.g. Risk Education or Victim rights)| Process/Activity|-| Quality Management (QM) activity information or | Information about an quality-improvement activity, such as an effort to control and monitor the object clearance and/or product reduction of an activity.land or activities| Process/Activity|-|}

[[Image:Understanding IMSMA Information Model <center>{| class="wikitable"|+ ! Item! Category Examples|-| Land|* SHA* CHA* EOD Spot Task* Ammunition Storage|-| Activity|* Non- Items.pngTechnical survey* Technical survey* Clearance* Completion survey|center-|500pxAccident|''Items'']]<div align="center">* Demining accident* Mine accident''Items''|-|}</divcenter>Part of defining and documenting an information model includes defining the useful information attributes for each {{IMSMANG}} item. {{IMSMANG}} comes with more than 1,000 [[Data Dictionary| data fields already defined]] as well as the capability to create additional custom-defined fields (CDFs). This makes it important to critically assess which data fields are useful to a programme for decision-making, analysis and reporting and to focus on those while ignoring data fields that don’t provide additional value. Limiting information to only that which is useful to the programme provides long-term benefits including reducing the data collection and data entry burden and improving system performance. And, while many data fields may be collected for each {{IMSMANG}} item, some fields may be more important for analysis than others. For example, whether a victim has been injured or killed may be more important for analysis than the victim’s nationality.

Items are entered into IMSMA^NG by means of a field report. Typically, * create separate workflows for each category /type of items has its own field report template for recording information specific to that Land* create and manage separate Data Entry Form templates per category. When entered into IMSMA^NG, all field report items must be assigned to a location, which is tied to type* differentiate between item categories/types on the country’s gazetteer, or political or administrative structure. The items can then be traced back to the country structure so that users can easily report data such as the number and size of hazards within a particular province.map

Part of defining Additionally, information managers can customise the categories so that unused categories can be inactivated and documenting an other categories added. The same is true for all top-level items within {{IMSMANG}}, which lets information managers specify their exact information model includes defining , including the useful information attributes for each IMSMA^NG relationships among item. IMSMA^NG comes with more than 1categories,000 data elements already defined as well and adjust the model as their needs change over time. To accurately map the capability to create additional custom-defined fields (CDFs). This makes it important to critically assess which data elements are useful to information model for a programme for decision-makingMine Action Programme, analysis and reporting it’s helpful to evaluate the available item categories and determine if changes to focus on those while ignoring data elements that don’t provide additional valuethe information model in {{IMSMANG}} are required. Limiting information to only that which is useful to the programme provides long-term benefits including reducing the data collection and data entry burden and improving While these values can be customised after system performance. Andsetup, while many data elements may be collected understanding the types of information for each item is critical to implementing an effective workflow in {{IMSMANG item, some elements may be more important for analysis than others. For example, whether a victim has been injured or killed may be more important for analysis than the victim’s nationality}}.

[[Image:Understanding IMSMA Information Model - Item SubcategoriesExample of Documented Land.png|center|500px|''Item Subcategories''300px]]

''Item SubcategoriesExample of documentation''

Each of the six categories of items can be divided into subcategories or types so users can collect information {{New_6.0 | In version 6.0 two classifications used for each subcategory. For example, users can specify different types of hazards such as dangerous areas, confirmed hazardous areas (CHAs)Victim; Cause and Needs assessment, minefields and battle areas and manage each kind of hazard differentlyAssistance classification used for Assistance have been added. All three are hierarchy tree-structures using levels. Using subcategories, information managers can: * create separate workflows for each type of hazard* create and manage separate data entry forms* differentiate between item categories on the map}}

Additionally, information managers can customise the subcategories so that unused subcategories can be removed and other subcategories added. The same is true for all top-level items within IMSMA^NG, which lets information managers specify their exact information model, including the relationships among item categories, and adjust the model as their needs change over time. To accurately map the information model for a programme, it’s helpful to evaluate the available item subcategories and determine if changes to the information model in IMSMA<sup>NG{{note|</supb> are required. While these values can be customized after system setup, understanding Document the types of information for each item is critical to implementing an effective workflow in IMSMA^NG. Table 5 shows examples of the possible subcategories of IMSMA<sup>NGfollowing decisions about Auxiliary data:</supb> items.

[[Image:Understanding IMSMA Information Model - Documenting ItemsExample of Documented Auxiliary Data ver2.png|center|500px|''Documenting Items''300px]]

''Documenting ItemsExample of Documented Auxiliary Data''

===Auxiliary The Data=== In addition to defining the required information Entry Form(s) for IMSMA^NG items, it is important to define the relevant information to be collected about auxiliary dataa specific object (e.g. This includes defining and documenting the country structure, ordnance, organisations and places, such as military bases, hospitals and cultural sites; any additional CDFs that should be created; and any subcategories for each of the auxiliary data types.  [[Image:Understanding IMSMA Information Model - Documenting Auxiliary Data.png|center|500px|Victim ''Jane Doe''Documenting Auxiliary Data) are summarised and displayed in a '']]<div align="center">'Summary'Documenting Auxiliary Data''</div>.

All mine action information is entered into IMSMA^NG via a field reportWith this approach, a data entry form used to users can collect information and store multiple Data Entry Forms about an the same itemover time so that the entire history of the item is preserved in the system. When The approach also provides a field report is completed, it is either reconciled complete [[Audit log | audit trail]] of all changes made to an existing item (any information so that is, it is determined to be information about an item that already exists in IMSMA^NG) or it is reconciled as new (that ismanagers can answer the question, "What did we know and when did we know it is determined to be information about an item that does not already exist in IMSMA^NG).?"

[[Image:Understanding_IMSMA_Information_Model_-_Field_Reports_and_Current_Views_Updating_CVs ver2.png|center|300px|''Field Reports, Current Views, and Reconciliation''400px]]

''Field Reports, Current Views, and ReconciliationExample of Updating Summary items''

With this approach, users can collect and store multiple field reports about the same item over time so that the entire history of the item is preserved in the system. The approach also provides a complete audit trail of all changes made to any mine action information so that information managers can answer the question, "What did we know and when did we know it?" IMSMA^NG also provides a constantly updated current view of the item which represents the sum of information about the item at any given time. As subsequent information is collected about a specific attribute of an item, IMSMA^NG updates the item’s current view on an attribute-by-attribute basis. For example, Field Report #1 collects some initial information about a hazard. It sets the priority to "Medium" and specifies that the hazard contains AP mines and is 25,000 sqm. Field Report Data Entry Form #2 updates information about the hazard land area after a subsequent assessment. The report sets the priority to "High" and specifies the presence of AP and AT mines, but it does not change the size or the status of the hazard. Field Report #3 updates the hazard’s size and status after clearance operations are complete. The figure below shows how the hazard’s current view is updated after all three reports are entered into the systemland area.

[[Image:Understanding_IMSMA_Information_Model_-_Updating_CVs{{Warning| A Data Entry Form that is changing existing information must have a Date of information that is later than the Data Entry Form that it is updating the calculation of the Summary item(s) are based on Date of Information.png|center|500px|When the date is earlier or the '''same'''Example of Updating Current Views, the Summary item will '']]<div align="center">'not'Example of Updating Current Views''</div>be updated.}}

Current view calculations *a work area (where activities are based on taking place)*a community (a group of people affected by the date of mine/UXO/IED threat)*the nearest town (the field report, so it is possible town closest to enter data into where the system out of chronological order (that activity is, to collect past information about an itemtaking place) without disrupting the current view. For example, if a fourth field report were collected and dated between Field Report #1 and Field Report #2, it would have no effect on the current view as all information in the example was updated with Field Report #2 or later.

===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 IMSMA Information Model - Using Locations to Link Mine Action Information Management - Mapping workflowData to the Country Structure.png|center|''Mapping the Workflow'']]

''Mapping Using Locations to Link Mine Action Data to the WorkflowCountry Structure''

This workflow map identifies the hazard reduction process that is used within the programme ===Assigning and can be mapped in IMSMALinking===__NOEDITSECTION__<supb>NGAssigning</supb> refers to track the clearance assignment of hazards. Because IMSMA^NG supports customisable workflows, it can be used an item to track different workflows for different objects. For example, a programme may have a separate abbreviated workflow Location for spot UXO tasks that involve only the identification purposes of the UXO hazard (object) and a clearance of the hazard (process) without additional surveys or stepsgrouping information. This process should also All items must be mapped for implementing in IMSMA^NGassigned a Location.

Along with {{IMSMANG}} provides the capability to assign items to Locations and create links between items, a workflow map function that describes shows the relationship relationships between the various types of objects items and processes in a workflow, and that enriches the status changes or outputs from the process data collected. Assignments and links are critical in adequately mapping defined during the hazard clearance Data Entry Form approval process. IMSMA^NG uses An item is assigned to one Location, which ties the status value of items item to track where the object or process is in its workflow. Objects country structure and processes in IMSMA^NG can have different status valuesallows for reporting data by area. For example, hazards The same item can then be defined linked to as many other items as "Active"necessary. In this way, "Worked On," or "Closed," while hazard reduction {{IMSMANG}} supports the idea of linking activities that are more process-oriented can be "Plannedto land," "Ongoing," "Completed," "Suspended," victims to accidents or "Abortedany item to any other item." Defining When used with item categories, linking adds a set powerful capacity to implement an information workflow and create rich and useful data for decision makers. To ensure the integrity of status values for each item provides this data, system administrators must clearly specify the capability kinds of links to:track in {{IMSMANG}}.

* manage workflows according The example below shows how users can build a workflow of relationships among items to model the information management process for their Mine Action Programmes. The figure shows how the Summary changes with each activity that is linked to the original Land. # The Land starts its life-cycle as ''SHA'' with a statusof Open in this example. * search # When the clearance starts and the first Progress report on items based on a particular is linked to the Land, the statusshould be changed to ''Worked On''. * display items on # Finally, after linking the Completion Report the map with different symbols based on their land's statusshould be updated to ''Closed''.

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 result is one Land whose information is updated over time by the three status values listed aboveActivities linked to the land. Some items like victims and accidents may not need status values depending on how This way to track information is can be used. Defining to represent the possible information management process and status values rules accurately for each object in the workflow as outputs of the processes conducted on them provides a set of business rules for information Land Release, Risk management that govern how information should be entered and analysedor other process model.

====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 IMSMA Information Management Model - Example Workflowof How Current View Statuses Change.png|center|''Example of a Traditional Workflow''400px]]

''Example of a Traditional WorkflowHow Summary Statuses Change''

Simpler processes Although any item can be defined for linked to any other types of hazards. For exampleitem, a spot UXO task would likely not go through this complete workflow and instead start with a subcategory all relationships necessarily make sense for every implementation. The diagrams below describe some of "UXO" and a status of "Open." A clearance could then be conducted the more common logical relationships among items and can serve as the UXO spot status updated to "Closed," without requiring a completion surveybasis for an information model when implementing {{IMSMANG}}.

 [[Image:Understanding Mine Action IMSMA Information Management Model - Example Workflow 2Relationships Among Items.png|center|''Example of a Spot UXO Workflow''550px]]

''Example of a Spot UXO WorkflowNote: Connections to Country Structure and Location have been omitted from the example''

By documenting {{note|<b>Document the entire process conducted on each type following business rules about assigning and linking:</b>* which items will have links between them, for example, Victims should always be linked to Accidents* rationale or logical meaning of hazardthe relationships between items, including the changes in status for example, a link between a Clearance and type an Accident means that result from the hazard reduction activitiesAccident happened during the Clearance* what effects linking has on the items, for example, information managers create a complete map of link between a Clearance and Land may indicate that the hazard/hazard reduction workflow that informs how linking and reconciliation decisions land status should be made and provide a guide change from ''Open'' to data entry personnel.''Worked on''}}

===Progress Reporting StructureThe Workbench=== 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^NG, 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. __NOEDITSECTION__[[Image:Understanding Mine Action Information Management - Progress Report WorkflowWB_Status.png|175px|center|''Progress Report Workflow'']]

''Progress Report WorkflowApproval workflow / Data Entry Form Statuses''

==Reconciliation Process== ===Location Folder=== ===Assigning and Linking=== IMSMA^NG provides the capability to assign items to locations and create links between items, a function that shows the relationships between items and processes and that enriches the data collected. Assignments and links are defined during the field report approval process. An item is assigned to one location, which ties the item to the country structure and allows for reporting mine action data by area. The same item can then be linked to as many other items as necessary. In this way, IMSMA^NG supports the idea of linking hazard reductions to hazards, victims to accidents or any item to any other item. When used with item subcategories, linking adds a powerful capacity to implement an information workflow and create rich and useful data for decision makers. To ensure the integrity of this data, system administrators must clearly specify the kinds of links to track in IMSMA^NG. See [[Maintaining IMSMA]] for more on this topic. The example below shows how users can build a workflow of complex relationships among top-level items and item subcategories to model the information management process for their programmes.  figure  The next figure shows how the current view changes with each hazard reduction that is linked to the original hazard. The CHA starts with a status of "Open." When the technical survey is linked to the hazard, it changes the hazard subcategory to "Minefield." Then, linking the clearance updates the hazard’s status to "Worked On." Finally, linking the completion survey changes the hazard’s status to "Closed." The result is one hazard whose information is updated over time by the four hazard reductions linked to the hazard. This way to track information can be used to represent the information management process and status rules accurately for a land release, risk management or other process model.  figure  The IMSMA^NG information model is flexible enough for each programme to customise the system to support its needs. For example, programmes that do not conduct MRE activities do not need to complete information about MREs, and they still retain full utility of the system. Similarly, programmes that conduct victim tracking and MRE activities only can disregard hazards and hazard reductions without any loss of utility. This flexibility, however, requires that programmes define the relevant uses of each item. Although any item can be linked to any other item, not all relationships necessarily make sense for every programme. The diagrams below describe some of the more common logical relationships among items and can serve as the basis for an information model when implementing IMSMA^NG.  figure  The rationale for each relationship or link should also be documented so the meaning is understood. For example, a hazard reduction may be conducted on a hazard and an accident may be a result of a hazard or produce a victim. These relationships are used when entering data to ensure that the links between items are available for searching and reporting, like when searching for all hazards that have clearances linked to them.  figure   ===Workbench=== Items, field reports, current views, assigning and linking come together at the Workbench. The Workbench is a holding area where users enter data into field reports and reconcile each item in the field report either as a new item or as an update to an existing item. Users have the ability to assign field report items to locations and to link items to other items (like linking a technical survey to an existing CHA). They then save the reports in the Workbench pending the appropriate quality checks and approvals. Until a field report Data Entry Form is approved, it exists only in the Workbench and does not update any current viewsSummary items. The report can still be modified or deleted. When The Approval will trigger an update of an existing item (Summary) or creating of a field report is approved, however, it becomes part new item depending of chosen Action. If the current views and cannot be deleted.  figure  For Summary item has geospatial data quality purposes, it is important that the data is adequately checked at this stage. IMSMA^NG allows information managers to control permissions for the Workbench and other areas of IMSMA^NG through the management of users and roles. With multiple permission levels for the Workbench, different users can may be assigned different permissions, allowing programmes to implement a data-entry workflow that distinguishes between data entry and data verification roles. It is recommended to set up a permission structure that reserves approval authority for field reports for visible in the most trusted usersMap Pane. ====Roles and Responsibilities====