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 Or with other words, when a Data===Entry process is started the first decision is to choose which of the several different methods/actions for Data Entry to use.

In addition to defining 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 required information for IMSMA^NG items, it item is important preserved in the system. The approach also provides a complete [[Audit log | audit trail]] of all changes made to define the relevant any information so that information to be collected about auxiliary data. This includes defining and documenting managers can answer the country structurequestion, ordnance, organisations "What did we know 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.when did we know it?"

[[Image:Understanding IMSMA Information Model Understanding_IMSMA_Information_Model_- Documenting Auxiliary Data_Updating_CVs ver2.png|center|500px|''Documenting Auxiliary Data''400px]]

''Documenting Auxiliary DataExample of Updating Summary items''

==Field Reports Data Entry Form #2 updates information about the land area after a subsequent assessment. The report sets the priority to "High" and Current Views==specifies the presence of AP and AT mines, but it does not change the size or the status of the land area.

All mine action information Data Entry Form #3 updates the land area's size and status after clearance operations are complete. The figure above shows how the land area's Summary is updated after all three reports are 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)the system.

With this approach, users can collect and store multiple field reports about {{Warning| A Data Entry Form that is changing existing information must have a Date of information that is later than the same item over time so Data Entry Form that it is updating the entire history calculation of the Summary item (s) are based on Date of Information. When the date is preserved in earlier or the system'''same''', the Summary item will '''not''' be updated. 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 ===Location ===__NOEDITSECTION__A country's official administrative structure, also provides a constantly updated current view of known as Gazetteer, should be the item which represents base for the sum of information about Country Structure used in {{IMSMANG}}. Sometimes the item at any given official administrative structure has not been updated for a long time. As subsequent information or it is collected about not detailed enough using it for a specific attribute of an itemgeographical placeholder, IMSMA^NG updates the item’s current view on an attribute-by-attribute basis. For exampleworksite, Field Report #1 collects some initial information about a hazard. It sets for the priority to "Medium" Mine Action programme and specifies that the hazard contains AP mines and is 25,000 sqm. Field Report #2 updates information about why the hazard after a subsequent assessmentitem Location has been introduced in {{IMSMANG}}. The report sets the priority Two fundamental decisions to make when customising {{IMSMANG}} is to decide what Country Structure level Locations will be consistently linked to "High" and specifies the presence of AP and AT mines, but it does not change the size or the status of the hazardwhat concept Locations will represent. 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 Typical concepts that a Location is updated after all three reports are entered into the system.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 belongs together or isassociated with each other and in that way get a better overview, to collect past information about an item) without disrupting facilitate searching and creating reports. The Locations is the link between the current view. For exampleCountry Structure, whether at the province, if a fourth field report were collected and dated between Field Report #1 district or town level and Field Report #2, it would have no effect on the current view as all information Mine Action data. As shown in the example was updated with Field Report #2 or later.figure below, data in {{IMSMANG}} are governed by two simple rules:

===Mapping *all data must be assigned to a Location*all Locations must be linked to the Workflow===Country Structure

[[Image:Understanding IMSMA Information Model - Using Locations to Link Mine Action Data to the Country Structure.png|center]]<div align===Business Rules Updating "center">''Using Locations to Link Mine Action Data to the Country Structure===''</div>

===Progress Report {{note|<b>Document the following decisions about Locations:</b>* what concept Locations will represent* what Country Structure===level Locations will be linked to}}

==Reconciliation Process=Assigning and Linking===__NOEDITSECTION__<b>Assigning</b> refers to the assignment of an item to a Location for the purposes of grouping information. All items must be assigned a Location.

===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.

The next figure shows how the current view changes with {{IMSMANG}} information model is flexible enough for each hazard reduction that is linked Mine Action Programme to customise the original hazardsystem to support its needs. The CHA starts with a status of "Open." When the technical survey is linked to the hazardFor example, it changes the hazard subcategory implementations that do not cover Education activities do not need to "Minefield." Thencomplete information about Education activities, linking and they still retain full utility of the clearance updates the hazard’s status to "Worked Onsystem." FinallySimilarly, 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 implementations that only cover Victim tracking and Education activities only can be used to represent the information management process disregard Land and status rules accurately for a land release, risk management or other process modelActivities without any loss of utility.

The [[Image:Understanding IMSMAInformation Model - Example Relationships Among Items.png|center|550px]]<supdiv align="center">NG''Note: Connections to Country Structure and Location have been omitted from the example''</supdiv> 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 Land that have clearances Accidents linked to them. figure