Changes

Most important Understanding the {{IMSMANG}} information model is a prerequisite for an information management concepts key manager to understand adapt the IMSMA^NG information model and system to their impact on information management are covered herecountry specific mine action requirements. To help information managers apply the concepts, some Some sections conclude with will include a list of requirements to define and document that can be used when establishing the by information model for a programme. ==Data Types=====Core Data===In managers to define and document the IMSMA^NG 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 IMSMA^NG. There are six categories of items, which are described in the table below. Each category can be characterized by a type that reflects whether the item is designed to track process or activity information or the object or product of an activity.

| Information about an activity designed to inform or educate people, such as about local hazards(e.g. Risk Education or Victim rights)| ObjectProcess/ProductActivity

| Information about an quality-improvement activity, such as an effort to control and monitor the clearance and/or reduction of lands land or activities| ObjectProcess/ProductActivity

Items are entered into IMSMA<supcenter>NG</sup> by means of a field report. Typically, each category of items has its own field report template for recording information specific to that category. When entered into IMSMA^NG, all field report items must be assigned to a location, which is tied to 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 hazardous areas within a particular province. Part of defining and documenting an information model includes defining the useful information attributes for each IMSMA^NG item. IMSMA^NG comes with more than 1,000 data elements already defined as well as the capability to create additional custom-defined fields (CDFs). This makes it important to critically assess which data elements are useful to a programme for decision-making, analysis and reporting and to focus on those while ignoring data elements 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 elements may be collected for each IMSMA^NG 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.  

|+ Item Subcategories

! Subcategory Category Examples

* Battle area* Dangerous area* MinefieldSHA

* UXO spotEOD Spot Task* Ammunition Storage

Each of the six categories of items can be divided into subcategories or types so users can collect information for each subcategory. For example, users can specify different types of lands such as dangerous areas, confirmed hazardous areas (CHAs), minefields and battle areas and manage each kind of land differently. Using subcategories, information managers can: * create separate workflows for each category/type of landLand* create and manage separate data entry formsData Entry Form templates per category/type* differentiate between item categories /types 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^NG are required. While these values can be customized after system setup, understanding 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^NG items.

{{Documentnote|<b>Document the following decisions about items:</b> * data elements to be collected and managed in IMSMA^NG{{IMSMANG}}* data elements fields that are not predefined in IMSMA^NG {{IMSMANG}} and should be created as CDFs* particularly important, or key, data elements for the programme* relevant subcategories categories/types for each item

 Below is an example of a fully-documented hazard.  [[Image:Understanding IMSMA Information Model - Example of Documented HazardLand.png|center|500px|''Example of Documented Hazard''300px]]

''Example of Documented Hazarddocumentation''

===Auxiliary Data===__NOEDITSECTION__In addition to defining the required information for IMSMA^NG {{IMSMANG}} items, it is important to define the relevant information to be collected about auxiliary Auxiliary data. This includes defining and documenting the [[Standardising_Auxiliary_Data#Country_Structure|Country Structure]], [[Explosive Standardising_Auxiliary_Data#OrdnanceClassification | Ordnance classification]], [[Standardising_Auxiliary_Data#Organisations |Organisation]] and [[Standardising_Auxiliary_Data#Places|Place]], such as military bases, hospitals and cultural sites; any additional CDFs that should be created; and any subcategories for each of the auxiliary Auxiliary data types.

{{Documentnote|<b>Document the following decisions about auxiliary Auxiliary data:</b>

* data elements to be collected and managed in IMSMA^NG{{IMSMANG}}* data elements fields that are not already configured in IMSMA^NG {{IMSMANG}} and can be created as CDFs

 Below is an example of a fully-documented place.  [[Image:Understanding IMSMA Information Model - Example of Documented Auxiliary Dataver2.png|center|500px|''Understanding IMSMA Information Model - Example of Documented Auxiliary Data''300px]]

''Understanding IMSMA Information Model - Example of Documented Auxiliary Data''

==Field Reports Data Entry Forms and Current ViewsSummary items==__NOEDITSECTION__A <b>field report</b> '''Data Entry Form''' is a template used for data entry form used to record and store of information e.g. about an itema victim.

A <b>current view</b> is The Data Entry Form(s) for a summary of all specific object (e.g. the information collected about an item on field reportsVictim ''Jane Doe'') are summarised and displayed in a '''Summary'''.

<b>'''Reconciliation</b> ''' is the process of assigning the deciding if information in a field report to should update an existing item object or creating a new itemobject/current viewSummary.

All information is entered into IMSMA^NG via a field reportOr with other words, when a data entry form used to collect information about an item. When a field report Data Entry process is completed, it started the first decision is either reconciled to an existing item (that is, it is determined to be information about an item that already exists in IMSMA<sup>NG<choose which of the several different methods/sup>) or it is reconciled as new (that is, it is determined actions for Data Entry to be information about an item that does not already exist in IMSMA^NG)use.

With this approach, users can collect and store multiple field reports 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 [[Audit log | audit trail ]] of all changes made to any 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 {{IMSMANG}} updates the item’s current view Summary on an attribute-by-attribute basis. For example, Field Report #1 collects some initial information about a hazardous land area. It sets The calculation of the priority to "Medium" Summary is done based on '''Date of Information''' and specifies therefore it is important that the land contains AP mines and Date of information is 25,000 sqm. Field Report #2 updates information about reflecting the land area after a subsequent assessment. The report sets age of the priority to "High" and specifies the presence of AP information and AT mines, but it does not change the size or the status date of the land area. Field Report #3 updates the land area's size and status after clearance operations are complete. The figure below shows how the land area's current view is updated after all three reports are entered entry into the system{{IMSMANG}}.

[[Image:Understanding_IMSMA_Information_Model_-_Updating_CVsver2.png|center|500px|''Example of Updating Current Views''400px]]

''Example of Updating Current ViewsSummary items''

Current view calculations are based on the date of the field report, so it is possible to enter 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 Data Entry Form #1 and Field Report #2, it would have no effect on the current view as all collects some initial information in the example was updated with Field Report #2 or later. ===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 about a group, including facilitating data entry, searching and running reportsLand. To do this, locations must link It sets the data priority to "Medium" and specifies that the country’s political or administrative structure (existing gazetteer), whether at the provinceland contains AP mines and is 25, district or town level000 sqm. 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 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 Entry Form #3 updates the Country Structureland area's size and status after clearance operations are complete.png|center|''Using Locations to Link Mine Action Data to The figure above shows how the Country Structureland area'']]<div align="center">''Using Locations to Link Mine Action Data to s Summary is updated after all three reports are entered into the Country Structure''</div>system.

===Location ===__NOEDITSECTION__A country'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 customizing IMSMA^NG customising {{IMSMANG}} is to decide what country structure Country Structure level locations Locations will be consistently linked to and what concept locations Locations will represent. Typical concepts that a location Location is used to represent include:

*a community (a group of people affected by the mine/UXO /IED threat)

Using Locations, users can group data that belongs together or is associated with each other and in that way get a better overview, facilitate searching and creating reports. The Locations is the link between the Country Structure, whether at the province, district or town level and the Mine Action data. As shown in the figure below, data in {{Document|<b>Document the following decisions about locationsIMSMANG}} are governed by two simple rules:</b>

* what concept locations will representall data must be assigned to a Location* what country structure level locations will all Locations must be linked to}} the Country Structure

===Assigning and Linking==={{note|<b>Assigning</b> refers to the assignment of an item to a location for Document the purposes of grouping information. All items must be assigned a location. <b>Linkingfollowing decisions about Locations:</b> refers to the association between items for the purposes of analysis. Linking is optional, for example, when linking clearances to minefields.* what concept Locations will representIMSMA^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 data by area. The same item can then * what Country Structure level Locations will be linked to as many other items as necessary. In this way, IMSMA^NG supports the idea of linking activities to lands, 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. 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.}}

[[Image:Understanding IMSMA Information Model - Example of How Relationships Among Items are Created.png|center|400px|''Example of How Relationships Among Items are Created'']]<div align="center"b>''Example of How Relationships Among Items are Created''Linking</divb>refers to the association between items for the purposes of analysis. Linking is optional, for example, when linking Activities to Accidents but linking is very important to do so effective reporting will be possible.

The next 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 current view Summary changes with each activity that is linked to the original landLand. # The CHA Land starts its life-cycle as ''SHA'' with a status of "Openin this example." # When the technical survey clearance starts and the first Progress report is linked to the landLand, it changes the landsubcategory status should be changed to "Minefield." Then, linking the clearance updates the land's status to "'Worked On''." # Finally, after linking the completion survey changes Completion Report the land's status should be updated to "''Closed." The result is one land whose information is updated over time by the four activities linked to the land. 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''.

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

''Example of How Current View Summary Statuses Change''

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 education activities do not need to complete information about education activities, and they still retain full utility of the system. Similarly, programmes that conduct victim tracking and education activities only can disregard lands and activities 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 programmeimplementation. 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{{IMSMANG}}.

 [[Image:Understanding IMSMA Information Model - Example Relationships Among Items.png|center|400px|''Example Relationships Among Items''550px]]

''Example Relationships Among ItemsNote: Connections to Country Structure and Location have been omitted from the example''

The rationale for each relationship or link should also be documented so the meaning is understood. For example, an activity may be conducted on a land and an accident may be a result of a hazardous land 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 lands that have clearances linked to them. {{Documentnote|<b>Document the following business rules about assigning and linking:</b> * which items will have links between them, for example, victims will Victims should always be linked to accidentsAccidents* rationale or logical meaning of the relationships between items, for example, a link between a clearance Clearance and a minefield an Accident means that the clearance was conducted on Accident happened during the minefieldClearance* what effects linking has on the items, for example, a link between a clearance Clearance and land Land may indicate that the land status should change from "''Open" '' to "''Worked on"''

  ===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 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 be assigned different permissions, allowing programmes to implement Until a data-entry workflow that distinguishes between data entry and data verification roles. It Data Entry Form is recommended to set up a permission structure that reserves approval authority for field reports for the most trusted users. For data quality purposesapproved, 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 of IMSMA^NG through the management of users and rolesdoes not update any Summary items. With multiple permission levels for the Workbench, different users The report can still be assigned different permissions, allowing programmes to implement a data-entry workflow that distinguisheses between data entry and data verification roles. It is recommended to set up a permission structure that reserves approval authority for field reports for the most trusted users. Table 6. Typical IMSMANG Roles Role DescriptionData Entry Users whose primary function is to enter field reports and other data into the system. This role may modified or may not include the ability to approve field reports. Data Verification Users who typically perform quality checks on the data entered by Data Entry usersdeleted. This role is often responsible for verifying the accuracy The Approval will trigger an update of the data entered and approving field reports. Operations Users who typically browse for information within IMSMA^NG to make operational decisions. Operations users may sometimes be grouped by function an existing item (for example, education, clearance Summary) or victim assistance)creating of a new item depending of chosen Action. These users often perform searches for If the Summary item has geospatial data, generate reports and analyze it may be visible in the data to support operational needs. System Administrator Users who perform information management-specific functions such as creating field report templates, designing reports, backing up and restoring data and other technical functions. Guest Users with essentially read-only access to browse dataMap Pane.