NoPublic, bureaucrat, administrator
6,632
edits
Changes
no edit summary
{| class="wikitable"
! Item
! Description
| Assistance
| Information about assistance for a person injured or affected by an accident
| ObjectProcess/ProductActivity
|-
| Education activity
| Information about an activity designed to inform or educate people (e.g. Risk Education or Victim rights)
| ObjectProcess/ProductActivity
|-
| Quality Management (QM) activity
| Information about an quality-improvement activity, such as an effort to control and monitor the clearance and/or reduction of land or activities
| ObjectProcess/ProductActivity
|-
|}
Items are entered into {{IMSMANG}} by means of a Data Entry Form. Typically, each category of items has its own Data Entry Form template for recording information specific to that category. When entered into {{IMSMANG}}, all Data Entry Form 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.
<center>
{| class="wikitable"
|+
|-
|}
</center>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 [[Information Classification 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.
Each of the items can be divided into categories or types so users can collect information for each category/type. For example, Land are normally divided into different categories/types and each category of land are managed differently. Using categories/types, information managers can:
Additionally, information managers can customise the categories so that unused categories can be inactivated and other categories added. The same is true for all top-level items within {{IMSMANG}}, 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 Mine Action Programme, it’s helpful to evaluate the available item categories and determine if changes to the information model in {{IMSMANG}} are required. While these values can be customised after system setup, understanding the types of information for each item is critical to implementing an effective workflow in {{IMSMANG}}.
{{note|<b>Document the following decisions about items:</b>
* data to be collected and managed in {{IMSMANG}}
* data fields that are not predefined in {{IMSMANG}} and should be created as CDFs
}}
[[Image:Understanding IMSMA Information Model - Example of Documented Land.png|center|400px|''Example of Documented Land''300px]]
<div align="center">
''Example of documentation''
}}
[[Image:Understanding IMSMA Information Model - Example of Documented Auxiliary Data ver2.png|center|400px|''Understanding IMSMA Information Model - Example of documentation''300px]]
<div align="center">
''Example of Documented Auxiliary Data''
</div>
==Data Entry Forms and SummariesSummary items==__NOEDITSECTION__A <b>'''Data Entry Form</b> ''' is a template used for data entry and storage of information e.g. about a victim.
The Data Entry Forms Form(s) for a specific object (e.g. the Victim, Accident, Land''Jane Doe'') are summarised and displayed in a <b>'''Summary</b>'''.
Or with other words, all information is entered into {{IMSMANG}} via a Data Entry Form. When 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.
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 [[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?"
As subsequent information is collected about a specific attribute of an item, {{IMSMANG}} updates the item’s Summary on an attribute-by-attribute basis. For example, Data Entry Form #1 collects some initial information about a Land. 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. Data Entry Form #2 updates information about reflecting the land area after a subsequent assessment. The report sets age of the priority to "High" information and specifies the presence of AP and AT mines, but it does not change the size or the status date of the land area. Data Entry Form #3 updates the land area's size and status after clearance operations are complete. The figure below shows how the land area's Summary is updated after all three reports are entered entry into the system{{IMSMANG}}.
[[Image:Understanding_IMSMA_Information_Model_-_Updating_CVs ver2.png|center|500px|''Example of Updating Summaries''400px]]
<div align="center">
''Example of Updating SummariesSummary items''
</div>
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 the system. {{NoteWarning| Inserting A Data Entry Form that is changing existing information must have a Date of information that is later than the Data Entry Form in a chain that it is updating the calculation of the Summary item(s) are based on Date of updates must be done carefully so Information. When the date is earlier or the '''same''', the expected end-result Summary item will '''not''' be archivedupdated.}}
===Location ===__NOEDITSECTION__
*a work area (where activities are taking place)
*a community (a group of people affected by the mine/UXO /IED threat)
*the nearest town (the town closest to where the activity is taking place)
*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'']]
<div align="center">
''Using Locations to Link Mine Action Data to the Country Structure''
</div>
{{note|<b>Document the following decisions about Locations:</b>
* what concept Locations will represent
* what Country Structure level Locations will be linked to
}}
===Assigning and Linking===__NOEDITSECTION__
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 status of Open in this example.
# When the technical survey clearance starts and the first Progress report is linked to the Land, the Land classification status should be updated to ''CHA'' and the status changed to ''Worked On''.
# Finally, after linking the Completion Report the land's status should be updated to ''Closed''.
The result is one Land whose information is updated over time by the three 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|500px|''Example of How Summary Statuses Change''400px]]
<div align="center">
''Example of How Summary Statuses Change''
</div>
The {{IMSMANG}} information model is flexible enough for each Mine Action Programme to customise the system to support its needs. For example, implementations that do not cover Education activities do not need to complete information about Education activities, and they still retain full utility of the system. Similarly, implementations that only cover Victim tracking and Education activities only can disregard Land and Activities without any loss of utility.
Although any item can be linked to any other item, not all relationships necessarily make sense for every implementation. 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 {{IMSMANG}}.
[[Image:Understanding IMSMA Information Model - Example Relationships Among Items.png|center|550px|''Example Relationships Among Items'']]
<div align="center">
''Note: Connections to Country Structure and Location have been omitted from the example''
</div>
The rationale for each relationship or link should also be documented so the meaning is understood. 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 Land that have Accidents linked to them.
{{note|<b>Document the 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 the relationships between items, for example, a link between a Clearance and an Accident means that the Accident happened during the Clearance
* what effects linking has on the items, for example, a link between a Clearance and Land may indicate that the land status should change from ''Open'' to ''Worked on''
}}
===The Workbench===__NOEDITSECTION__
[[Image:WB_Status.png|175px|center]]
<div align="center">
'' Approval workflow / Data Entry Form Statuses''
</div>
The Workbench is a holding area / import inbox where Data Entry Forms are found until they are approved. There are four possible steps in the Approval process:
# [[SaveData Entry Forms| Save]]# [[Submit Data Entry Forms | Submit]]# [[Reject Data Entry Forms | Reject]]# [[Approve Data Entry Forms | Approve]]
For data quality purposes, it is important that the data is adequately checked. With multiple permission levels for the Approval, different users can be assigned different permissions, allowing Mine Action Programmes to implement a data-entry workflow that distinguishes between data '''entry''' and data '''verification''' roles.
Until a Data Entry Form is approved, it exists only in the Workbench and does not update any SummariesSummary 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 Data Entry Form is approvednew item depending of chosen Action. If the Summary item has geospatial data, it becomes part of the Summaries and will may be visible on in the mapMap Pane. [[Image:WB_Status.png|center|225px]]<div align="center">''Data Entry Form Statuses / Approval workflow''</div>
{{NavBox Information Management}}
[[Category:Information managementNAA]]
