2,186
edits
Changes
no edit summary
===IMSMA Workflows and Business Rules===
Rather than establishing one workflow that all programmes must use, IMSMA<sup>NG</sup> allows information managers to establish their own programme-appropriate workflows and business rules to better support their specific needs. To document their programme-specific workflows, information managers describe the processes undertaken on each object in IMSMA<sup>NG</sup> and the outputs or products from the processes. Typically, these workflows relate to the various categories of hazards and hazard reductions, but they can also be applied to other IMSMA<sup>NG</sup> items as appropriate.
During this step, information managers map the process that each hazard goes through as it is cleared or its impact is otherwise reduced. Using a combination of the relevant hazard types, status values and relationships, information managers design an information workflow that will be implemented as standard operating procedures (SOPs) for data entry and analysis. Some programmes may have only one process for all categories of hazards while other programmes may have three or more processes.
====Mapping the Workflows====
The first element of mapping the hazard reduction workflow is to build a map of the relationship between the objects and processes involved in the hazard reduction process. Starting with the first representation of the hazard, the workflow map should describe the processes done to the hazard and the output of the process. The workflow map should trace the entire process from hazard identification through clearance and release of the land according to the operational process in use in the programme. In the example below, a confirmed hazardous area (CHA) is linked to a technical survey that was conducted on the hazard. The survey resulted in a minefield on which a clearance was done, and the clearance resulted in a cleared hazard. Finally, a completion survey was logged to close the hazard.
(figure)
This workflow map identifies the hazard reduction process that is used within the programme and can be mapped in IMSMA<sup>NG</sup> to track the clearance of hazards. Because IMSMA<sup>NG</sup> supports customisable workflows, it can be used to track different workflows for different objects. For example, a programme may have a separate abbreviated workflow for spot UXO tasks that involve only the identification of the UXO hazard (object) and a clearance of the hazard (process) without additional surveys or steps. This process should also be mapped for implementing in IMSMA<sup>NG</sup>.
