Understanding IMSMA Information Model - Revision history

Alnaucler at 12:34, 9 July 2019

2019-07-09T12:34:23Z

← Older revision		Revision as of 14:34, 9 July 2019
Line 29:		Line 29:
	\| Assistance		\| Assistance
	\| Information about assistance for a person injured or affected by an accident		\| Information about assistance for a person injured or affected by an accident
	\| ~~Object~~/~~Product~~		\| Process/Activity
	\|-		\|-
	\| Education activity		\| Education activity
	\| Information about an activity designed to inform or educate people (e.g. Risk Education or Victim rights)		\| Information about an activity designed to inform or educate people (e.g. Risk Education or Victim rights)
	\| ~~Object~~/~~Product~~		\| Process/Activity
	\|-		\|-
	\| Quality Management (QM) activity		\| Quality Management (QM) activity
	\| Information about an quality-improvement activity, such as an effort to control and monitor the clearance and/or reduction of land or activities		\| Information about an quality-improvement activity, such as an effort to control and monitor the clearance and/or reduction of land or activities
	\| ~~Object~~/~~Product~~		\| Process/Activity
	\|-		\|-
	\|}		\|}

Alnaucler at 20:34, 30 June 2018

2018-06-30T20:34:18Z

← Older revision		Revision as of 22:34, 30 June 2018
Line 167:		Line 167:
	The example below shows how users can build a workflow of relationships among items to model the information management process for their Mine Action Programmes. The figure shows how the Summary changes with each activity that is linked to the original Land.		The example below shows how users can build a workflow of relationships among items to model the information management process for their Mine Action Programmes. The figure shows how the Summary changes with each activity that is linked to the original Land.
	# The Land starts its life-cycle as ''SHA'' with a status of Open in this example.		# The Land starts its life-cycle as ''SHA'' with a status of Open in this example.
	# When the ~~technical survey~~ is linked to the Land, the ~~Land classification~~ should be ~~updated to ''CHA'' and the status~~ to ''Worked On''.		# When the clearance starts and the first Progress report is linked to the Land, the status should be changed to ''Worked On''.
	# Finally, after linking the Completion Report the land's status should be updated to ''Closed''.		# Finally, after linking the Completion Report the land's status should be updated to ''Closed''.

Alnaucler at 20:29, 30 June 2018

2018-06-30T20:29:43Z

← Older revision		Revision as of 22:29, 30 June 2018
Line 134:		Line 134:
	Data Entry Form #3 updates the land area's size and status after clearance operations are complete. The figure above shows how the land area's Summary is updated after all three reports are entered into the system.		Data Entry Form #3 updates the land area's size and status after clearance operations are complete. The figure above shows how the land area's Summary is updated after all three reports are entered into the system.

	{{Warning\| A Data Entry Form that is changing existing information must have a Date of information that is later than the Data Entry Form that it is updating the calculation of the Summary item(s) are based on Date of Information. When the date is earlier or the same, the Summary item will '''not''' be updated.}}		{{Warning\| A Data Entry Form that is changing existing information must have a Date of information that is later than the Data Entry Form that it is updating the calculation of the Summary item(s) are based on Date of Information. When the date is earlier or the '''same''', the Summary item will '''not''' be updated.}}

	===Location ===__NOEDITSECTION__		===Location ===__NOEDITSECTION__

Alnaucler at 20:27, 30 June 2018

2018-06-30T20:27:35Z

← Older revision		Revision as of 22:27, 30 June 2018
Line 70:		Line 70:
	\|}		\|}
	</center>		</center>
	Part of defining and documenting an information model includes defining the useful information attributes for each {{IMSMANG}} item. {{IMSMANG}} comes with more than 1,000 [[~~Information Classification~~ \| data fields already defined]] as well as the capability to create additional custom-defined fields (CDFs). This makes it important to critically assess which data fields are useful to a programme for decision-making, analysis and reporting and to focus on those while ignoring data fields that don’t provide additional value. Limiting information to only that which is useful to the programme provides long-term benefits including reducing the data collection and data entry burden and improving system performance. And, while many data fields may be collected for each {{IMSMANG}} item, some fields may be more important for analysis than others. For example, whether a victim has been injured or killed may be more important for analysis than the victim’s nationality.		Part of defining and documenting an information model includes defining the useful information attributes for each {{IMSMANG}} item. {{IMSMANG}} comes with more than 1,000 [[Data Dictionary\| data fields already defined]] as well as the capability to create additional custom-defined fields (CDFs). This makes it important to critically assess which data fields are useful to a programme for decision-making, analysis and reporting and to focus on those while ignoring data fields that don’t provide additional value. Limiting information to only that which is useful to the programme provides long-term benefits including reducing the data collection and data entry burden and improving system performance. And, while many data fields may be collected for each {{IMSMANG}} item, some fields may be more important for analysis than others. For example, whether a victim has been injured or killed may be more important for analysis than the victim’s nationality.

	Each of the items can be divided into categories or types so users can collect information for each category/type. For example, Land are normally divided into different categories/types and each category of land are managed differently. Using categories/types, information managers can:		Each of the items can be divided into categories or types so users can collect information for each category/type. For example, Land are normally divided into different categories/types and each category of land are managed differently. Using categories/types, information managers can:

Alnaucler at 17:17, 17 June 2017

2017-06-17T17:17:00Z

← Older revision		Revision as of 19:17, 17 June 2017
Line 134:		Line 134:
	Data Entry Form #3 updates the land area's size and status after clearance operations are complete. The figure above shows how the land area's Summary is updated after all three reports are entered into the system.		Data Entry Form #3 updates the land area's size and status after clearance operations are complete. The figure above shows how the land area's Summary is updated after all three reports are entered into the system.

	{{Warning\| A Data Entry Form that is changing existing information must have a Date of information that is later than the Data Entry Form that it is updating the calculation of the Summary item(s) are based on Date of Information. When the date is earlier or the same, ~~no change of~~ the Summary item ~~occur~~.}}		{{Warning\| A Data Entry Form that is changing existing information must have a Date of information that is later than the Data Entry Form that it is updating the calculation of the Summary item(s) are based on Date of Information. When the date is earlier or the same, the Summary item will '''not''' be updated.}}

	===Location ===__NOEDITSECTION__		===Location ===__NOEDITSECTION__

Alnaucler at 07:10, 15 June 2017

2017-06-15T07:10:25Z

← Older revision		Revision as of 09:10, 15 June 2017
Line 119:		Line 119:
	Or with other words, when a Data Entry process is started the first decision is to choose which of the several different methods/actions for Data Entry to use.		Or with other words, when a Data Entry process is started the first decision is to choose which of the several different methods/actions for Data Entry to use.

	With this approach, users can collect and store multiple Data Entry Forms about the same item over time so that the entire history of the item is preserved in the system. The approach also provides a complete audit trail of all changes made to any information so that information managers can answer the question, "What did we know and when did we know it?"		With this approach, users can collect and store multiple Data Entry Forms about the same item over time so that the entire history of the item is preserved in the system. The approach also provides a complete [[Audit log \| audit trail]] of all changes made to any information so that information managers can answer the question, "What did we know and when did we know it?"

	As subsequent information is collected about a specific attribute of an item, {{IMSMANG}} updates the item’s Summary on an attribute-by-attribute basis. The calculation of the Summary is done based on '''Date of Information''' and therefore it is important that Date of information is reflecting the age of the information and not the date of entry into {{IMSMANG}}.		As subsequent information is collected about a specific attribute of an item, {{IMSMANG}} updates the item’s Summary on an attribute-by-attribute basis. The calculation of the Summary is done based on '''Date of Information''' and therefore it is important that Date of information is reflecting the age of the information and not the date of entry into {{IMSMANG}}.

Alnaucler at 11:37, 6 October 2016

2016-10-06T11:37:07Z

← Older revision		Revision as of 13:37, 6 October 2016
Line 140:		Line 140:

	*a work area (where activities are taking place)		*a work area (where activities are taking place)
	*a community (a group of people affected by the mine/UXO threat)		*a community (a group of people affected by the mine/UXO/IED threat)
	*the nearest town (the town closest to where the activity is taking place)		*the nearest town (the town closest to where the activity is taking place)

Alnaucler at 11:10, 5 October 2016

2016-10-05T11:10:42Z

← Older revision		Revision as of 13:10, 5 October 2016
Line 210:		Line 210:

	{{NavBox Information Management}}		{{NavBox Information Management}}
	[[Category:~~Information management~~]]		[[Category:NAA]]

Alnaucler at 15:44, 3 July 2015

2015-07-03T15:44:58Z

← Older revision		Revision as of 17:44, 3 July 2015
Line 43:		Line 43:
	Items are entered into {{IMSMANG}} by means of a Data Entry Form. Typically, each category of items has its own Data Entry Form template for recording information specific to that category. When entered into {{IMSMANG}}, all Data Entry Form items must be assigned to a Location, which is tied to the country’s gazetteer, or political or administrative structure. The items can then be traced back to the Country Structure so that users can easily report data such as the number and size of hazardous areas within a particular province.		Items are entered into {{IMSMANG}} by means of a Data Entry Form. Typically, each category of items has its own Data Entry Form template for recording information specific to that category. When entered into {{IMSMANG}}, all Data Entry Form items must be assigned to a Location, which is tied to the country’s gazetteer, or political or administrative structure. The items can then be traced back to the Country Structure so that users can easily report data such as the number and size of hazardous areas within a particular province.

			<center>
	{\| class="wikitable"		{\| class="wikitable"
	\|+		\|+
Line 68:		Line 69:
	\|-		\|-
	\|}		\|}
			</center>
	Part of defining and documenting an information model includes defining the useful information attributes for each {{IMSMANG}} item. {{IMSMANG}} comes with more than 1,000 [[Information Classification \| data fields already defined]] as well as the capability to create additional custom-defined fields (CDFs). This makes it important to critically assess which data fields are useful to a programme for decision-making, analysis and reporting and to focus on those while ignoring data fields that don’t provide additional value. Limiting information to only that which is useful to the programme provides long-term benefits including reducing the data collection and data entry burden and improving system performance. And, while many data fields may be collected for each {{IMSMANG}} item, some fields may be more important for analysis than others. For example, whether a victim has been injured or killed may be more important for analysis than the victim’s nationality.		Part of defining and documenting an information model includes defining the useful information attributes for each {{IMSMANG}} item. {{IMSMANG}} comes with more than 1,000 [[Information Classification \| data fields already defined]] as well as the capability to create additional custom-defined fields (CDFs). This makes it important to critically assess which data fields are useful to a programme for decision-making, analysis and reporting and to focus on those while ignoring data fields that don’t provide additional value. Limiting information to only that which is useful to the programme provides long-term benefits including reducing the data collection and data entry burden and improving system performance. And, while many data fields may be collected for each {{IMSMANG}} item, some fields may be more important for analysis than others. For example, whether a victim has been injured or killed may be more important for analysis than the victim’s nationality.

Line 87:		Line 88:
	}}		}}

	[[Image:Understanding IMSMA Information Model - Example of Documented Land.png\|center\|~~400px\|''Example of Documented Land''~~]]		[[Image:Understanding IMSMA Information Model - Example of Documented Land.png\|center\|300px]]
	<div align="center">		<div align="center">
	''Example of documentation''		''Example of documentation''
Line 104:		Line 105:
	}}		}}

	[[Image:Understanding IMSMA Information Model - Example of Documented Auxiliary Data ver2.png\|center\|~~400px\|''Understanding IMSMA Information Model - Example of documentation''~~]]		[[Image:Understanding IMSMA Information Model - Example of Documented Auxiliary Data ver2.png\|center\|300px]]
	<div align="center">		<div align="center">
	''Example of Documented Auxiliary Data''		''Example of Documented Auxiliary Data''
Line 122:		Line 123:
	As subsequent information is collected about a specific attribute of an item, {{IMSMANG}} updates the item’s Summary on an attribute-by-attribute basis. The calculation of the Summary is done based on '''Date of Information''' and therefore it is important that Date of information is reflecting the age of the information and not the date of entry into {{IMSMANG}}.		As subsequent information is collected about a specific attribute of an item, {{IMSMANG}} updates the item’s Summary on an attribute-by-attribute basis. The calculation of the Summary is done based on '''Date of Information''' and therefore it is important that Date of information is reflecting the age of the information and not the date of entry into {{IMSMANG}}.

	[[Image:Understanding_IMSMA_Information_Model_-_Updating_CVs ver2.png\|center\|~~500px\|''Example of Updating Summary items''~~]]		[[Image:Understanding_IMSMA_Information_Model_-_Updating_CVs ver2.png\|center\|400px]]
	<div align="center">		<div align="center">
	''Example of Updating Summary items''		''Example of Updating Summary items''
Line 147:		Line 148:
	*all Locations must be linked to the Country Structure		*all Locations must be linked to the Country Structure

	[[Image:Understanding IMSMA Information Model - Using Locations to Link Mine Action Data to the Country Structure.png\|center~~\|''Using Locations to Link Mine Action Data to the Country Structure''~~]]		[[Image:Understanding IMSMA Information Model - Using Locations to Link Mine Action Data to the Country Structure.png\|center]]
	<div align="center">		<div align="center">
	''Using Locations to Link Mine Action Data to the Country Structure''		''Using Locations to Link Mine Action Data to the Country Structure''
Line 171:		Line 172:
	The result is one Land whose information is updated over time by the three Activities linked to the land. This way to track information can be used to represent the information management process and status rules accurately for a Land Release, Risk management or other process model.		The result is one Land whose information is updated over time by the three Activities linked to the land. This way to track information can be used to represent the information management process and status rules accurately for a Land Release, Risk management or other process model.

	[[Image:Understanding IMSMA Information Model - Example of How Current View Statuses Change.png\|center\|~~500px\|''Example of How Summary Statuses Change''~~]]		[[Image:Understanding IMSMA Information Model - Example of How Current View Statuses Change.png\|center\|400px]]
	<div align="center">		<div align="center">
	''Example of How Summary Statuses Change''		''Example of How Summary Statuses Change''
Line 180:		Line 181:
	Although any item can be linked to any other item, not all relationships necessarily make sense for every implementation. The diagrams below describe some of the more common logical relationships among items and can serve as the basis for an information model when implementing {{IMSMANG}}.		Although any item can be linked to any other item, not all relationships necessarily make sense for every implementation. The diagrams below describe some of the more common logical relationships among items and can serve as the basis for an information model when implementing {{IMSMANG}}.

	[[Image:Understanding IMSMA Information Model - Example Relationships Among Items.png\|center\|550px~~\|''Example Relationships Among Items''~~]]		[[Image:Understanding IMSMA Information Model - Example Relationships Among Items.png\|center\|550px]]
	<div align="center">		<div align="center">
	''Note: Connections to Country Structure and Location have been omitted from the example''		''Note: Connections to Country Structure and Location have been omitted from the example''
Line 194:		Line 195:

	===The Workbench===__NOEDITSECTION__		===The Workbench===__NOEDITSECTION__
	[[Image:WB_Status.png\|~~thumb\|225px~~\|Approval workflow / Data Entry Form Statuses]]		[[Image:WB_Status.png\|175px\|center]]
			<div align="center">
			'' Approval workflow / Data Entry Form Statuses''
			</div>
	The Workbench is a holding area / import inbox where Data Entry Forms are found until they are approved. There are four possible steps in the Approval process:		The Workbench is a holding area / import inbox where Data Entry Forms are found until they are approved. There are four possible steps in the Approval process:
	# [[Save Data Entry Forms\| Save]]		# [[Save Data Entry Forms\| Save]]

Dionysia at 12:15, 24 March 2015

2015-03-24T12:15:39Z

← Older revision		Revision as of 14:15, 24 March 2015
Line 194:		Line 194:

	===The Workbench===__NOEDITSECTION__		===The Workbench===__NOEDITSECTION__
			[[Image:WB_Status.png\|thumb\|225px\|Approval workflow / Data Entry Form Statuses]]
	The Workbench is a holding area / import inbox where Data Entry Forms are found until they are approved. There are four possible steps in the Approval process:		The Workbench is a holding area / import inbox where Data Entry Forms are found until they are approved. There are four possible steps in the Approval process:
	# [[Save Data Entry Forms\| Save]]		# [[Save Data Entry Forms\| Save]]
Line 203:		Line 204:

	Until a Data Entry Form is approved, it exists only in the Workbench and does not update any Summary items. The report can still be modified or deleted. The Approval will trigger an update of an existing item (Summary) or creating of a new item depending of chosen Action. If the Summary item has geospatial data, it may be visible in the Map Pane.		Until a Data Entry Form is approved, it exists only in the Workbench and does not update any Summary items. The report can still be modified or deleted. The Approval will trigger an update of an existing item (Summary) or creating of a new item depending of chosen Action. If the Summary item has geospatial data, it may be visible in the Map Pane.

	~~[[Image:WB_Status.png\|center\|225px]]~~
	~~<div align="center">~~
	~~'' Approval workflow / Data Entry Form Statuses''~~
	~~</div>~~

	{{NavBox Information Management}}		{{NavBox Information Management}}
	[[Category:Information management]]		[[Category:Information management]]