NoPublic, bureaucrat, administrator
6,632
edits
Changes
no edit summary
| 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
|-
|}
|}
</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:
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.
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. The calculation of the Summary is done based on '''Date of Information''' and therefore it is important that Date of information is reflecting the age of the information and not the date of entry into {{IMSMANG}}.
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.
{{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. When the date is earlier or the '''same''', no change of the Summary item occurwill '''not''' be updated.}}
===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)
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''.
