Changes

Jump to: navigation, search

Documenting Customisations

413 bytes added, 11:26, 18 March 2019
no edit summary
{{TOC right}}
__NOEDITSECTION__
==Document Workflows and Business Rules==__NOEDITSECTION__After the desired [[Data Inventory Manager|data elements ]] and field report [[Standardising Data Entry Forms|Data Entry Form templates ]] are customised and published, the next step is to define and document the information workflow for each type of field reportData Entry Form. This is a critical step for ensuring the quality of the data stored in {{IMSMANG}}. It involves combining the [[Understanding IMSMA Workflows and Business Rules|workflow rules identified in Chapter 1 ]] with the field report Data Entry Form templates defined in Chapter 2 to create a set of workflows that can be documented as instructions or SOPs for reconciling and entering and reconciling data in {{IMSMANG}}. Each workflow and SOP should include rules for:
*assigning locations *creating and updating and replacing items*linking items
With these rules defined, information managers can help improve data consistency and ease of searching and reporting while reducing data entry errors and the effort to correct them later. Information managers can also develop data quality searches and reports that identify and enforce the information workflows. The diagram below identifies a basic information workflow, but information managers should provide guidance to data entry personnel for how the workflow should proceed in their programmes.
==Creating [[Image:AdminGuide_ExampleBasicInformationWorkflow.png|center|500px|''Example of a Programme Specific User Guide=Basic Information Workflow'']]<div align="center">Creating ''Example of a programme-specific user guide is a critical step in communicating information management concepts and decisions to IMSMANG users, particularly because IMSMANG is so customisable. With a programme-specific user guide information managers can:Basic Information Workflow''</div>
* ensure faster training of ==Creating a Programme Specific User Guide==__NOEDITSECTION__Creating a programme-specific user guide is a critical step in communicating information management concepts and operations staff* reduce the likelihood and impact of data quality problems* provide an easy reference for data entry personnel and decisions to {{IMSMANG}} users of , particularly because {{IMSMANG }} is so customisable. With a programme-specific user guide informationmanagers can:
The following sections provide guidance on creating a programme-specific user guide that supplements the IMSMANG User Guide with specialised steps for how *ensure faster training of information should be managed within management and operations staff*reduce the programme.likelihood and impact of data quality problems*provide an easy reference for data entry personnel and users of {{HowTo's|[[HowTo:Customise the Help Menu|Customise the Help Menu]]IMSMANG}}information
===Content to Include===__NOEDITSECTION__The guide should document the programme-specific customisations of {{IMSMANG as discussed in Chapter 1 and Chapter 2 of this manual}}. It should provide straightforward, task-specific guidance and avoid complicated discussions of possible options and conditions. Ideally, the guide is an intermediate document that bridges the gap between the goals, objectives and terms of reference of information management and the specific “how-to” instructions in the {{IMSMANG }} User Guide.
===Overview===__NOEDITSECTION__The Overview section should cover basic information about the guide, its purpose and intent and about information management responsibilities. It should describe the overall workings of IMSMANG IMSMA<sup>NG</sup> including the configuration of the {{IMSMANG }} system within the programme as well as the number of users and basic roles and responsibilities.
===Items and Processes===__NOEDITSECTION__In this section, information managers should define each item and process that will be tracked in {{IMSMANG}}. Following the recommendations in XXX, this This information should include:
* description of each item category and subcategory that will be used (see Items)* definition of what each item category and subcategory will be used for (see Items)* list of key data elements including custom-defined fields (see Items)* description of the relationships among items (see Assigning and Linking)* list of the status values for each item (see Status Changes)* direction for how locations will be used (see Location)* description for how tasking will be used (see Tasking Tool)
===Workflow and Business Rules===__NOEDITSECTION__This section should define the workflows and business rules that are to be followed when collecting and updating hazard land and hazard reduction activity information. Workflows identify the processes (hazard reductionsactivities) undertaken on a hazard land and the resulting status changes, from identification to clearance and completion. Include a workflow for each different kind of hazard land in use
===Data Entry Process and Guidelines===__NOEDITSECTION__When the relevant items, processes and workflows are identified and documented, information managers should provide guidelines to assist data entry personnel in correctly reconciling, entering, reconciling and linking data according to the processes. The guidelines should include an entry for each of the field report Data Entry Form templates to be used and a description for how each should be entered. At a minimum, these guidelines should include:
* name and description for each field report Data Entry Form template* list of required fields and what the values should be* definition of how the items in the field report Data Entry Form should be reconciled (as new or as updates)* description of how to determine the location for each item in the form if it is new* definition of which existing items should be linked to the items in the field reportData Entry Form
===Outline to Follow===__NOEDITSECTION__
Below is an outline of a programme-specific user guide with suggestions for content to include in each section.
1. <ol><li>Overview</li>2. <li>Items and Processes</li><ol type="a. "><li>Locations</li>b. Hazards<li>Land</li><ol type="i. "><li>Suspected hazardous areas (SHA)</li>ii. <li>Confirmed hazardous areas (CHA)</li>iii. Minefields<li>EOD spots</li>iv. UXO spots</ol>c. Hazard reductions<li>Activities</li><ol type="i. "><li>Technical surveys</li>ii. <li>Clearances</li>iii. <li>Progress reports</li>iv. <li>Completion reports</li></ol>d. MRE <li>Education activities</li>e. <li>Quality management</li><ol type="i. "><li>Quality assurance reports</li>ii. <li>Quality management reports</li>f. </ol><li>Accidents and victims</li><ol type="i. "><li>Demining accidents</li>ii. <li>Mine accidents</li>iii. <li>Civilian victims</li>iv. <li>Demining victims</li></ol>g. <li>Assistance</li><li>Auxiliary data</li><ol type="i. "><li>Country Structure</li><li>Places</li>ii. <li>Organisations</li>iii. <li>Ordnance</li><li>Assistance Classifications</li><li>Cause Classifications</li><li>Needs Classifications</li></ol></ol>3. <li>Workflow and business rules</li><ol type="a. "><li>CHA/minefield clearance workflow</li>b. <li>EOD Spot UXO clearance Task workflow</li>4. </ol><li>Data entry guide</li><ol type="a. "><li>Entering a new minefield CHA form</li>b. <li>Entering a minefield CHA update form</li>c. <li>Entering a hazard land status change form</li>d. <li>Entering a new clearance form</li>e. <li>Entering progress reports</li></ol></ol> {{NavBox IMSMA NG Administration}} [[Category:NAA]]
6,632
edits

Navigation menu