2,186
edits
Changes
no edit summary
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.
figure
The next figure shows how the current view changes with each hazard reduction that is linked to the original hazard. The CHA starts with a status 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 can be used to represent the information management process and status rules accurately for a land release, risk management or other process model.
figure
The IMSMA<sup>NG</sup> 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<sup>NG</sup>.
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 that have clearances linked to them.
figure
===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. figure For data quality purposes, it is important that the data is adequately checked at this stage. IMSMA<sup>NG</sup> allows information managers to control permissions for the Workbench and other areas of IMSMA<sup>NG</sup> 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 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 the most trusted users. ====Rolesand Responsibilities====
