277
edits
Changes
no edit summary
__NOEDITSECTION__
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 lands land and activities, 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 land goes through as it is cleared or its impact is otherwise reduced. Using a combination of the relevant land 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 lands land while other programmes may have three or more processes.
===Mapping the Workflow===__NOEDITSECTION__
This workflow map identifies the activity that is used within the programme and can be mapped in IMSMA<sup>NG</sup> to track the clearance of landsland. 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 land (process) without additional surveys or steps. This process should also be mapped for implementing in IMSMA<sup>NG</sup>.
===Business Rules Updating Structure===__NOEDITSECTION__
====Status Changes====__NOEDITSECTION__
Along with a workflow map that describes the relationship between the various types of objects and processes in a workflow, the status changes or outputs from the process are critical in adequately mapping the land clearance process. IMSMA<sup>NG</sup> uses the status value of items to track where the object or process is in its workflow. Objects and processes in IMSMA<sup>NG</sup> can have different status values. For example, lands land can be defined as "Active", "Worked On," or "Closed," while activities that are more process-oriented can be "Planned," "Ongoing," "Completed," "Suspended," or "Aborted." Defining a set of status values for each item provides the capability to:
* manage workflows according to status
* display items on the map with different symbols based on their status
Some IMSMA<sup>NG</sup> items may have many status values. For example, process-oriented items such as activities and quality management likely have many status values, but lands land and other object- or output-oriented items typically have only the three status values listed above. Some items like victims and accidents may not need status values depending on how information is used. Defining the possible status values for each object in the workflow as outputs of the processes conducted on them provides a set of business rules for information management that govern how information should be entered and analysed.
====Example Workflows with Status Changes====__NOEDITSECTION__
Simpler processes can be defined for other types of landsland. For example, a spot UXO task would likely not go through this complete workflow and instead start with a subcategory of "UXO" and a status of "Open." A clearance could then be conducted and the UXO spot status updated to "Closed," without requiring a completion survey.
* Workflow process for each land type including which processes or activities are done on which types
* Outputs or results of activities on lands land including the resulting status and type changes
* Progress tracking process
}}