Understanding IMSMA Workflows and Business Rules

Revision as of 18:03, 27 November 2012 by Aurora (talk | contribs) (Created page with "{{TOC right}} __NOEDITSECTION__ Rather than establishing one workflow that all programmes must use, IMSMA<sup>NG</sup> allows information managers to establish their own progr...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Rather than establishing one workflow that all programmes must use, IMSMANG 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 IMSMANG 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 IMSMANG 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.


Template:Document