Changes

Jump to: navigation, search

Documenting Customisations

267 bytes removed, 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 IMSMA<sup>NG</sup>{{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 IMSMA<sup>NG</sup>{{IMSMANG}}. Each workflow and SOP should include rules for:
*assigning locations
*creating and updating and replacing items
*linking items
</div>
==Creating a Programme Specific User Guide==__NOEDITSECTION__Creating a programme-specific user guide is a critical step in communicating information management concepts and decisions to IMSMA<sup>NG</sup> {{IMSMANG}} users, particularly because IMSMA<sup>NG</sup> {{IMSMANG}} is so customisable. With a programme-specific user guide information managers can:
*ensure faster training of information management and operations staff
*reduce the likelihood and impact of data quality problems
*provide an easy reference for data entry personnel and users of IMSMA<sup>NG</sup> {{IMSMANG}} information
===Content to Include===__NOEDITSECTION__The following sections guide should document the programme-specific customisations of {{IMSMANG}}. It should provide guidance on creating a programmestraightforward, task-specific user guidance and avoid complicated discussions of possible options and conditions. Ideally, the guide is an intermediate document that supplements bridges the IMSMA<sup>NG</sup> User Guide with specialised steps for how gap between the goals, objectives and terms of reference of information should be managed within management and the specific “how-to” instructions in the programme.{{HowTo's|[[HowTo:Customise the Help Menu|Customise the Help Menu]]IMSMANG}}User Guide.
===Content to IncludeOverview===__NOEDITSECTION__The Overview section should cover basic information about the guide , its purpose and intent and about information management responsibilities. It should document describe the programme-specific customisations overall workings of IMSMA<sup>NG</sup> as discussed in Chapter 1 and Chapter 2 including the configuration 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 {{IMSMANG}} system within the gap between programme as well as the goals, objectives number of users and terms of reference of information management basic roles and the specific “how-to” instructions in the IMSMA<sup>NG</sup> User Guideresponsibilities.
===OverviewItems and Processes===__NOEDITSECTION__The Overview In this section should cover basic information about the guide, its purpose and intent and about information management responsibilities. It managers should describe the overall workings of IMSMA<sup>NG</sup> including the configuration of the IMSMA<sup>NG</sup> system within the programme as well as the number of users and basic roles define each item and responsibilitiesprocess that will be tracked in {{IMSMANG}}.This information should include:
===Items *description of each item category and Processes===subcategory that will be usedIn this section, information managers should define *definition of what each item category and process that subcategory will be tracked in IMSMA<sup>NG</sup>. Following used for*list of key data elements including custom-defined fields*description of the relationships among items*list of the recommendations in XXX, this information should include:status values for each item*direction for how locations will be used*description for how tasking will be used
*description of each item category ===Workflow and Business Rules===__NOEDITSECTION__This section should define the workflows and subcategory business rules that will are to be used (see Items)*definition of what each item category followed when collecting and updating land and subcategory will be used for (see Items)*list of key data elements including custom-defined fields activity information. Workflows identify the processes (see Itemsactivities)*description of the relationships among items (see Assigning undertaken on a land and Linking)*list of the resulting status values changes, from identification to clearance and completion. Include a workflow 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)different kind of land in use
===Workflow Data Entry Process and Business RulesGuidelines===__NOEDITSECTION__This section should define When the relevant items, processes and workflows are identified and business rules that are documented, information managers should provide guidelines to be followed when collecting assist data entry personnel in correctly reconciling, entering and updating hazard and hazard reduction information. Workflows identify linking data according to the processes (hazard reductions) undertaken on a hazard and . The guidelines should include an entry for each of the resulting status changes, from identification Data Entry Form templates to clearance be used and completion. Include a workflow description for how each different kind of hazard in useshould be entered. At a minimum, these guidelines should include:
===Data Entry Process and Guidelines===When the relevant items, processes and workflows are identified and documented, information managers should provide guidelines to assist data entry personnel in correctly entering, reconciling and linking data according to the processes. The guidelines should include an entry for each of the field report 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.
<ol type="a">
<li>Locations</li>
<li>HazardsLand</li>
<ol type="i">
<li>Suspected hazardous areas (SHA)</li>
<li>Confirmed hazardous areas (CHA)</li>
<li>Minefields</li><li>UXO EOD spots</li>
</ol>
<li>Hazard reductionsActivities</li>
<ol type="i">
<li>Technical surveys</li>
<li>Completion reports</li>
</ol>
<li>MRE Education activities</li>
<li>Quality management</li>
<ol type="i">
<li>Demining victims</li>
</ol>
<li>Assistance</li>
<li>Auxiliary data</li>
<ol type="i">
<li>Country Structure</li>
<li>Places</li>
<li>Organisations</li>
<li>Ordnance</li>
<li>Assistance Classifications</li>
<li>Cause Classifications</li>
<li>Needs Classifications</li>
</ol>
</ol>
<li>Workflow and business rules</li>
<ol type="a">
<li>CHA/minefield clearance workflow</li><li>EOD Spot UXO clearance Task workflow</li>
</ol>
<li>Data entry guide</li>
<ol type="a">
<li>Entering a new minefield CHA form</li><li>Entering a minefield CHA update form</li><li>Entering a hazard land status change form</li>
<li>Entering a new clearance form</li>
<li>Entering progress reports</li>
</ol>
{{NavBox Customizing IMSMANG Administration}} [[Category:NAA]]
6,632
edits

Navigation menu