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===Entry Form(s) for a specific object (e.g. the Victim ''Jane Doe'') are summarised and displayed in a '''Summary'''.

In addition to defining the required information for IMSMA^NG items, it '''Reconciliation''' is important to define the relevant process of deciding if information to be collected about auxiliary data. 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 typesupdate an existing object or creating a new object/Summary.

With this approach, users can collect and store multiple Data Entry Forms 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 [[Image:Understanding IMSMA Information Model - Documenting Auxiliary Data.png|center|500pxAudit log |''Documenting Auxiliary Data''audit trail]]<div align=of all changes made to any information so that information managers can answer the question, "centerWhat did we know and when did we know it?">''Documenting Auxiliary Data''</div>

==Field Reports and Current Views== All mine action information is entered into IMSMA^NG via a field report, a data entry form used to collect information about an item. When a field report is completed, it is either reconciled to an existing item (that is, it is determined to be information about an item that already exists in IMSMA^NG) or it is reconciled as new (that is, 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 Data Entry Form #2 updates information about the same item over time so that land area after a subsequent assessment. The report sets the entire history priority to "High" and specifies the presence of AP and AT mines, but it does not change the item is preserved in size or the system. The approach also provides a complete audit trail status 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?"land area.

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 #2 updates information about the hazard 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 Data Entry Form #3 updates the hazard’s land area's size and status after clearance operations are complete. The figure below above shows how the hazard’s current view land area's Summary is updated after all three reports are entered into the system.

[[Image:Understanding_IMSMA_Information_Model_-_Updating_CVs.png|center|500px|''Example of Updating Current Views'']]<div align="center">==Location ===__NOEDITSECTION__A country''Example of Updating Current Views''</div>s official administrative structure, also known as Gazetteer, should be the base for the Country Structure used in {{IMSMANG}}. Sometimes the official administrative structure has not been updated for a long time or it is not detailed enough using it for a geographical placeholder, worksite, for the Mine Action programme and that is why the item Location has been introduced in {{IMSMANG}}. Two fundamental decisions to make when customising {{IMSMANG}} is to decide what Country Structure level Locations will be consistently linked to and what concept Locations will represent. Typical concepts that a Location is used to represent include:

Current view calculations are based on the date of the field reportUsing Locations, so it is possible to enter users can group data into the system out of chronological order (that is, to collect past information about an item) 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 belongs together 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 associated 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 each other 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 way get a minefield on which a clearance was donebetter overview, facilitate searching and the clearance resulted in a cleared hazardcreating reports. 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 The Locations 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 link between the hazard (process) without additional surveys or steps. This process should also be mapped for implementing in IMSMA^NG. ===Business Rules Updating Country Structure=======Status Changes==== Along with a workflow map that describes the relationship between the various types of objects and processes in a workflow, whether at 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," "Suspendedprovince," district or "Aborted." Defining a set of status values for each item provides the capability to: * manage workflows according to status* search town level 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. ====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^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 shown 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 figure below, progress reports were collected for three separate reporting periods during a clearance operation. Collecting and linking information data 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.{{IMSMANG}} are governed by two simple rules:

[[Image:Understanding Mine Action Information Management - Progress Report Workflow.png|center|''Progress Report Workflow'']]<div align="center">''Progress Report Workflow''</div>  ==Reconciliation Process== ===Location Folder=== A location in IMSMA^NG is a grouping of information, whether logical, geographical or sociopolitical. Using locations, users can group data that belongs together or is associated with each other and handle it as a group, including facilitating data entry, searching and running reports. To do this, locations must link the mine action data to the country’s political or administrative structure (existing gazetteer), whether at the province, district or town level. This method also provides geographical context to the data. As shown in the figure below, locations in IMSMA^NG are governed by two simple rules: *all mine action data must be linked to a location*all locations must be linked to the country structure  [[Image:Understanding IMSMA Information Model - Using Locations to Link Mine Action Data to the Country Structure.png|center|''Using Locations to Link Mine Action Data to the Country Structure'']]

Two fundamental decisions to make when customizing IMSMA===Assigning and Linking===__NOEDITSECTION__<supb>NGAssigning</supb> is refers to decide what country structure level locations will be consistently linked the assignment of an item to and what concept locations will represent, Typical concepts that a location is used to represent include: *a work area (where hazards exist and hazard reductions are taking place)*Location for the purposes of grouping information. All items must be assigned a community (a group of people affected by the mine/UXO threat)*the nearest town (the town closest to where the activity is taking place)  [[Image:Understanding IMSMA Information Model - Documenting LocationsLocation.png|center|500px|''Documenting Locations'']]<div align="center">''Documenting Locations''</div>

===Assigning {{IMSMANG}} provides the capability to assign items to Locations and Linking===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 Data Entry Form approval process. An item is assigned to one Location, which ties the item to the country structure and allows for reporting data by area. The same item can then be linked to as many other items as necessary. In this way, {{IMSMANG}} supports the idea of linking activities to land, victims to accidents or any item to any other item. When used with item categories, 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 {{IMSMANG}}.

IMSMA^NG provides the capability to assign items to locations and create links between items, The example below shows how users can build a function that shows the workflow of relationships between among items and processes and that enriches to model the data collectedinformation management process for their Mine Action Programmes. Assignments and links are defined during The figure shows how the field report approval process. An item Summary changes with each activity that is assigned linked to one location, which ties the item to the country structure and allows for reporting mine action data by areaoriginal Land. # The same item can then be linked to Land starts its life-cycle as many other items as necessary''SHA'' with a status of Open in this example. In this way, IMSMA^NG supports # When the clearance starts and the idea of linking hazard reductions first Progress report is linked to hazardsthe Land, victims to accidents or any item the status should be changed to any other item''Worked On''. When used with item subcategories# Finally, after 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 Completion Report the kinds of links land's status should be updated to track in IMSMA^NG. See [[Maintaining IMSMA]] for more on this topic''Closed''.

The example below shows how users result is one Land whose information is updated over time by the three Activities linked to the land. This way to track information can build a workflow of complex relationships among top-level items and item subcategories be used to model represent the information management process and status rules accurately for their programmesa Land Release, Risk management or other process model.

 [[Image:Understanding IMSMA Information Model - Example of How Relationships Among Items are CreatedCurrent View Statuses Change.png|center|400px|''Example of How Relationships Among Items are Created'']]

''Example of How Relationships Among Items are CreatedSummary Statuses Change''

The next figure shows how the current view changes with each hazard reduction that is Although any item can be linked to the original hazardany other item, not all relationships necessarily make sense for every implementation. The CHA starts with a status diagrams below describe some 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 more common logical relationships among items and can be used to represent serve as the basis for an information management process and status rules accurately for a land release, risk management or other process modelwhen implementing {{IMSMANG}}.

 [[Image:Understanding IMSMA Information Model - Example of How Current View Statuses ChangeRelationships Among Items.png|center|400px|''Example of How Current View Statuses Change''550px]]

''Example of How Current View Statuses ChangeNote: Connections to Country Structure and Location have been omitted from the example''

The IMSMA{{note|<supb>NGDocument the following business rules about assigning and linking:</supb> information model is flexible enough * which items will have links between them, for each programme to customise the system to support its needs. For example, programmes that do not conduct MRE activities do not need Victims should always be linked to complete information about MREs, and they still retain full utility Accidents* rationale or logical meaning of the system. Similarlyrelationships between items, for example, programmes a link between a Clearance and an Accident means that conduct victim tracking and MRE activities only can disregard hazards and hazard reductions without any loss of utility. This flexibilitythe Accident happened during the Clearance* what effects linking has on the items, howeverfor example, requires a link between a Clearance and Land may indicate that programmes define the relevant uses of each item.land status should change from ''Open'' to ''Worked on''}}

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.  [[Image:Understanding IMSMA Information Model - Example Relationships Among Items.png|center|400px|''Example Relationships Among Items'']]<div align="center">''Example Relationships Among Items''</div>  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.  [[Image:Understanding IMSMA Information Model - Documenting Assigning and Linking.png|center|500px|''Documenting Assigning and Linking'']]<div align="center">''Documenting Assigning and Linking''</div>   ===The 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 is approved, it exists only in the Workbench and does not update any current views. The report can still be modified or deleted. When a field report is approved, however, it becomes part of the current views and cannot be deleted. __NOEDITSECTION__[[Image:Understanding IMSMA Information Model - Adding Field Report Information to the Current ViewWB_Status.png|175px|center|''Adding Field Report Information to the Current View'']]

''Adding Field Report Information to the Current ViewApproval workflow / Data Entry Form Statuses''

For data quality purposesUntil a Data Entry Form is approved, it is important that the data is adequately checked at this stage. IMSMA^NG allows information managers to control permissions for exists only in the Workbench and other areas does not update any Summary items. The report can still be modified or deleted. The Approval will trigger an update of IMSMA^NG through the management an existing item (Summary) or creating of a new item depending of users and roleschosen Action. With multiple permission levels for If the WorkbenchSummary item has geospatial data, different users can it 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==== {{NavBox Information Management}}[[ImageCategory:Understanding IMSMA Information Model - Roles and Responsibilities.png|center|500px|''Roles and Responsibilities''NAA]]<div align="center">''Roles and Responsibilities''</div>