Changes

===Mapping the Workflow===__NOEDITSECTION__

The first element of mapping the activity workflow is to build a map of the relationship between the objects and processes involved in the activity. Starting with the first representation of the land, the workflow map should describe the processes done to the land and the output of the process. The workflow map should trace the entire process from land 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 land. The survey resulted in a minefield on which a clearance was done, and the clearance resulted in a cleared land. Finally, a completion survey was logged to close the land.

[[Image:Understanding Mine Action Information Management - Mapping workflow.png|center|''Mapping the Workflow'']]

''Mapping the Workflow''

</div>

This workflow map identifies the activity that is used within the Mine Action programme and can be mapped in {{IMSMANG}} to track the clearance of land. Because {{IMSMANG}} supports customisable workflows, it can be used to track different workflows for different objects. For example, a Mine Action programme may have a separate abbreviated workflow for spot EOD tasks that involve only the identification of the UXO Land (object) and a clearance of the land (process) without additional surveys or steps. This process should also be mapped for implementing in {{IMSMANG}}.

In the figure below, a ''SHA'' is created and its status is set to ''Open''. A technical survey process is then conducted on the land, which results in changing the subcategory of the land from ''SHA'' to ''CHA'' and defining the land's perimeter. Next, a clearance process is conducted on the ''CHA'' that results in updating the status of the land to ''Worked On''. Finally, a completion report is submitted that updates the status of the land to ''Closed''.

[[Image:Understanding IMSMA Information Model - Example of How Current View Statuses Change.png|center|''Example of a Traditional Workflow'']]

''Example of a Traditional Workflow''

</div>

Simpler processes can be defined for other types of land. For example, an EOD spot task would likely not go through this complete workflow and instead start with a subcategory of ''EOD'' and a status of ''Open''. A EOD Spot task could then be conducted and the ''EOD'' status updated to ''Closed'', without requiring a completion survey.

[[Image:Understanding Mine Action Information Management - Example Workflow 2.png|center|''Example of a Spot EOD Workflow'']]

''Example of a Spot EOD Workflow''

</div>

By documenting the entire process conducted on each type of land, including the changes in status and type that result from activities, information managers create a complete map of the land/activity workflow that informs how linking and reconciliation decisions should be made and provide a guide to data entry personnel.

* Progress Reports combined together and linked to either Land or Clearance

Information managers should assess which approach better meets the needs of their programs when selecting an approach to tracking progress.

==== Progress Reports linked to the Land ====__NOEDITSECTION__

==== Progress Reports combined together ====__NOEDITSECTION__

An third approach to store progress information is to reconcile the Progress Reports as updates to the clearance using the combine option during reconciliation. Using this method, the different progress reports are '''not''' visible as individual Progress reports in {{IMSMANG}}; their information is combined with, and added to, the clearance information collected to that point. It will, however, become '''more''' complicated to determine progress during individual reporting periods, for operators to see their Progress Reports and to ensure high data quality. We do not recommend this method.

{{Note|<b>Document the following decisions about information workflows and business rules:</b>