OCHA Information Management Toolbox
OCHA’s Information Management Toolbox is an online space for OCHA’s Information Management staff to access current and curated information tools, services, and systems to support humanitarian response and preparedness coordination. The Toolbox is the authoritative reference for OCHA information management tools and systems. The IM Toolbox is an essential part of every Information Management Officer’s packing list – for all phases of humanitarian response and preparedness work. A quick url that will get you here is imtoolbox.unocha.org.
If you are new to humanitarian information management (IM) the pages in this section are a good place to start. Here you will find links to key documents and introductions to basic IM concepts. More content will be added. Suggestions and examples are welcome, please see the FIS team.
Principles of Humanitarian IM
Overview
These 10 guiding principles were established in 2002 by participants in the Symposium on Best Practices in Humanitarian Information Management and Exchange and are included in the operational guidance documents for humanitarian information management.
Accessibility: Humanitarian information should be made accessible by applying easy-to-use formats and tools and by translating information into common or local languages when necessary.
Inclusiveness: Information exchange should be based on a system of partnership with a high degree of ownership by multiple stakeholders, especially representatives of the affected population and Government.
Inter-operability: All shareable data and information should be made available in formats that can be easily retrieved, shared and used by humanitarian organizations.
Accountability: Users must be able to evaluate the reliability and credibility of information by knowing its source and having access to methods of collection, transformation, and analysis.
Verifiability: Information should be relevant, accurate, consistent and based on sound methodologies, validated by external sources, and analyzed within the proper contextual framework.
Relevance: Information should be practical, flexible, responsive, and driven by operational needs in support of decision-making throughout all phases of a crisis.
Objectivity: A variety of sources should be used when collecting and analyzing information so as to provide varied and balanced perspectives for addressing problems and recommending solutions.
Neutral: Information should be free of political interference that distorts a situation or the response.
Humanity: Information should never be used to distort, to mislead or to cause harm to affected or at-risk populations and should respect the dignity of those affected.
Timeliness: Humanitarian information must be kept current and made available in a timely manner.
Sustainability: Humanitarian information should be open sourced, preserved, cataloged and archived, so that it can be retrieved for future use, such as for preparedness, analysis, lessons learned and evaluation.
Confidentiality: Sensitive data and information that are not to be shared publicly should be managed accordingly and clearly marked as such.
Essential Reading for OCHA IMOs
Familiarity with these five pieces of guidance will provide an IMO with a solid foundation of the role of information management in an OCHA office and how IM fits within the larger humanitarian context. Collectively, these documents outline a list of IM responsibilities that individual IMOs and IM teams are responsible for in every OCHA office.
-
Policy Instruction: The Roles and Responsibilities of Country Offices (2010) – If you only read one, read this one! Although this policy instruction needs to be updated it provides a genuinely useful framework of an OCHA office’s five operational priorities (situational awareness, a common approach, a common strategy, monitoring, lessons learned) and the role of IM. It also includes office size and structure, cost-plans, supervision and internal reporting.
-
IASC: Operational Guidance on Responsibilities of Clusters/Sectors Leads & OCHA in Information Management (2008) – Perhaps the most important IM-focused guidance document, describing the relationship between OCHA and the clusters, as well as many of the individual tasks IMOs are responsible for.
-
IASC: Emergency Response Preparedness (ERP) (2015) – Basic framework for county-level preparedness.
-
IASC: Humanitarian Programme Cycle (HPC) reference module (2014) – Describes how agencies work together to provide humanitarian relief.
-
IASC: Common Operational Datasets (COD) – Describes the most important baseline datasets with special emphasis on administrative boundaries and baseline population statistics.
-
IMWG Guidance on Common Operational Datasets (CODs) in Emergency Preparedness and Response –
Can you answer these questions? If not, read the documents 
What are the 5 operational priorities of an OCHA country office?
Who is responsible for establishing Information Management Network at the country level?
List the two IM minimum preparedness actions.
List the two “essential enablers” in the humanitarian programme cycle.
What is the definition of a COD?
Recommended Reading for OCHA IMOs
-
OCHA 2018-21 Strategic Plan – OCHA office and IM units should align their strategy to the OCHA strategy.
-
GA Resolution 46/182 – GA Resolution 46/182 directly established many cornerstones of humanitarian action including DHA, which became OCHA in 1998.
-
Emergency Response in OCHA_2017.pdf – The policy instruction on response describes how OCHA responds to sudden-onset or rapidly deteriorating crises. It includes a timeline of the first hours, days, weeks and months. More recent than the policy instruction on country offices, so more in-line with HPC
-
IASC Operational Guidance on Data Responsibility in Humanitarian Action – It is intended to help humanitarian staff, organizations, and their partners practice data responsibility in different response contexts. Partners across the system will implement this Operational Guidance in accordance with their respective mandates and the decisions of their governing bodies.
CODs
-
are authoritative reference datasets needed to support operations and decision-making for all actors in a humanitarian response.
-
pertain to a recognized country or territory1.
-
are standardized datasets that are commonly used and referenced by all operations.
-
are of four types2:
-
reflect the local hierarchical administrative structure,2 are annotated with place names and P-codes, and are generally accompanied by a tabular gazetteer.
-
are best available datasets that ensure consistency and simplify the management of key data.
-
are accepted in country3 or in their region by the relevant Information Management Working Group.
-
are catalogued at the COD Portal [LINK SUBJECT TO CHANGE SOON].
-
are disseminated at the Humanitarian Data Exchange (HDX); COD-AB and COD-EM datasets are also available as live GIS geoservices.
-
enable consistency and harmonization among actors working on humanitarian preparedness and response by providing:
-
a common operational picture of the crisis
-
a geographic framework (P-codes) for data collection, analysis, and visualization.
-
-
are available in two quality classifications (see COD-AB quality and COD-PS quality):
-
‘enhanced CODs’ with full quality control, compatibility, and reliability
-
‘standard CODs’ not yet fully quality controlled.
-
-
facilitate informed decision making both pre- and post-crisis.
-
reduce duplication of work on baseline data by partnering organizations.
-
strengthen valuable humanitarian networks and relationships.
-
drive API look-up information
1 CODs are generally prepared for sovereign states recognized by the UN Secretariat, but in some cases reflect sub-national territories. For example, there are CODs for Sint Maarten, which is a part of the Kingdom of the Netherlands, but not for Taiwan, which is not a recognized member state.
2 Previously a ‘Humanitarian Profile’ COD-HP type existed, which presented tabular People-in-Need information derived from Humanitarian Needs Overviews. This information is now provided in country-specific ‘Humanitarian Needs’ (non-COD) datasets disseminated in HDX by OCHA Humanitarian Programme Cycle Tools (HPC Tools). For further information see HPC Tools.
1 Except some COD-CS datasets [????]
IM Process
Overview
This is where data elements are transformed into information and knowledge and then into action. The recommended information management process has six steps:
Plan
The identification of the core information set that is needed for effective decision-making starts here. This stage should involve strategic decision makers setting the direction and identifying exactly what information is needed. Available resources and time are critical elements, in a sudden onset the information needs might be very different than in a complex emergency.
Collect
Using the strategic direction given in the planning stage collection involves review the time and resources and determining the appropriate methodology. Secondary data often is a good starting point with primary data collection efforts taking the longest and requiring more resources. Normally (but not always!) OCHA IMOs engage in the collection of secondary data and cluster IMOs are responsible for primary data collection.
Process
Consists primarily of transforming raw data into a format that can be used for analysis. It is a time-intensive activity involving cleaning and organizing the collected data. The true quality of the data often becomes apparent in this step. Information management officers are often the first people to scrutinize the data and can help in the determination of quality and usability.
Analyse
Normally carried out on two levels;
-
basic statistical or spatial analysis using charts, graphs or maps to display basic information and
-
adding background, contextual or technical expertise.
In addition to information management officers, subject matter experts should be involved in the analysis step. Going back to the planning step ask if the collected data can provide the needed answers. Be clear on the limitations of the data.
Communicate
Depending on the intended audience communication of the analyzed data (now information) can take the form of reports, maps, or charts. It can be shared via the web or on paper and the underlying data can be shared as tables. Take care to consider the sensitivity of the data.
Feedback
An often forgotten step. After completing the process stop and review, did decision-makers have the information needed to make critical decisions? If repeated how could the process be improved on streamlined?
IM Team Size
Overview
The OCHA Policy Instruction on Country Offices includes several pre-approved cost plans and organigrams for different sized offices. These should be seen as the minimum size and composition of an IM unit. In practice, IM units vary enormously. The table below compares the number of IMOs in pre-approved cost plans with actual IM staffing in 2017/8. It is up to the Head of an IMU to make a case to a HoO to provide adequate capacity.
|
# of IMOs |
Small / Sub-office
|
Medium office
|
Large office
|
|
Guidance |
1 (P3) |
2 (P3 NOA) |
3 (P4, P3, NOA) |
|
Range (actual) |
1-3 |
4-6 |
7-9 |
Many offices will supplement the international and national IMOs in an office cost plan with local consultants and by using other organizations such as iMMAP and REACH to enhance the IM capacity. For example, in 2017 for Yemen there were six IMOs in the OCHA cost plan plus 12 staff from iMMAP and 2 from REACH, therefore overall IM capacity was actually 20. iMMAP also provide IM support to the clusters bringing the number of IMOs working on the humanitarian response to over 40!
Process
-
Discuss IM expectations with HoO and translate into an IM strategy and work plan based on office size
-
Determine short term vs long term needs (often more staff is needed to scale up a response and fewer to maintain)
-
-
Identify potential IM capacity in the country (strong capacity would allow for more national staff)
-
Identify potential partners willingness to support.
-
Develop short-term IM staff plan
-
Develop longer term IM staff plan – keep in mind that recruitment of a fixed term international staff will take at least 6 months)
Outputs/Resources
-
Example of .xls used for tracking staff in large sudden onset – Tracking Philippines Typhoon Yolanda 2013.xlsx
-
Template of graphic used for large staff tracking in sudden onset – Staffing levels in Philippines 2014.doc
Guidance
Performance Management
Overview
The purpose of the Performance Management and Development System is to improve the delivery of programmes by optimizing performance at all levels, which it will achieve by:
(a) Promoting a culture of high performance, personal development, and continuous learning;
(b) Empowering managers and holding them responsible and accountable for managing their staff;
(c) Encouraging a high level of staff participation in the planning, delivery, and evaluation of work;
(d) Recognizing successful performance and addressing underperformance in a fair and equitable manner.
All staff are responsible for:
(a) Understanding the larger organizational goals;
(b) Soliciting clarification on individual performance expectations;
(c) Participating in discussions with the first reporting officer to facilitate the development and finalization of the individual work plan and maintaining discussions during the reporting period;
(d) Taking steps to complete each stage of the process for which they are responsible without delay.
Process
-
The head of the IM unit should work closely with their HoO and direct supervisor to discuss the work plan of the office.
-
Translate the unit work plan to individual staff work plans
-
Meet regularly with the IM team (ideally weekly) to discuss issues and weekly priorities
-
Use the mid-year review process to modify individual work plans as necessary
-
Complete mid-year and end of year review process on time.
National Staff Recruitment
Overview
Recruitments of national staff for OCHA field offices have to go through UNDP, and are advertised using UNDP formats and procedures. For OCHA headquarter positions, hiring managers can use Inspira, and in some cases have the option of going through UNDP (eg. in Istanbul, the hiring manager can choose between Inspira and UNDP).
Process
For recruitments administered by UNDP, hiring managers or their HR focal points, should liaise with their UNDP focal points, as procedures may vary somewhat from country to country. If an office is advertising an entirely new position and has the possibility to develop new ToRs, a good starting point would be the P2 and P3 job profiles. A few examples of national ToRs developed on the basis of those are available below. For Inspira announcements, the process is administered with support from OCHA human resources in HQ. An example at NOA level is provided below. The P2 and P3 job profiles can also serve as a guide for the ToRs (again, see examples below).
Outputs/Resources
Examples based on P2 and P3 ToRs (OCHA Field offices or HQ):
Examples of UNDP formats (OCHA Field offices or HQ):
ICT
Examples of Inspira formats (OCHA HQ positions):
You would like to hire an OCHA IMO
Step 1: advertise the position
You should first determine what skillsets you would like the IMO to have, and whether the IMO should be a specialist or a generalist. There are several pages of the IM Unit Management – People section of the IM Toolbox can help you with that.
When advertising the position, depending on the skillsets that you would like to focus on, use one of the job descriptions that were developed by the Global IM Functional Team (GIFT) and cleared by human resources:
Step 2: select your candidate
Feel free to contact Field Information Services (FIS) to help you with screening, testing and interviews. Remember that if you are recruiting against a JO (as opposed to a TJO), all candidates recommended for the position will be added to the IMO roster.
IM Unit Skills and Expertise
Required Skills
At a minimum, an OCHA Country Office IM team should include staff with advanced skills in key software and platforms. They should use these skills every day, know most advanced features and be able to work quickly and to a high-quality standard without needing help from others.
-
Microsoft Excel
-
GIS software: ArcGIS, QGIS
-
Graphic design: InDesign, Illustrator
-
Data visualization: Tableau, Power BI
The team should also include staff who are advanced users of key OCHA platforms and tools. They should be able to setup and manage these platforms, advocate for their use and train users.
Other tool:
The team should also include staff who are experienced in producing and managing key OCHA products. They should be familiar with their purpose, audience, templates, and workflows and be able to produce them to a high-quality standard.
Nice to have Skills
Outputs/Resources
Compétences et expertises de l’unité IM
Description
In order to achieve the objectives of an IMU’s work plan in an OCHA office, the IM team must possess a wide variety of skills and expertise.

Required Skills
It is important that the OCHA IM country team has advanced skills in the management of key software and platforms . IMOs should use these skills on a daily basis, be familiar with the most advanced features, and be able to work quickly, with great rendering, without needing to ask other team members for help.
-
Microsoft Excel
-
GIS software: ArcGIS, QGIS
-
Graphic Design: InDesign, Illustrator
-
Data visualization: Tableau, Power BI
The team should also include members with advanced skills in using OCHA’s key platforms and tools . They must be able to organize and manage these platforms, advocate for their use, as well as train their users.
Other tools:
The team should also include members experienced in the production and management of OCHA flagship products. They must know its goals, target audiences, models (templates) and workflow; as well as being able to produce a high quality rendering.
Useful skills
Resources
OCHA IM Skillsets and Roles
Overview
The OCHA policy instruction on country offices lists 10 different skillsets for Humanitarian Affairs Officers (including Head of Office, Inter-Cluster Coordinator, and Protection), but only one skillset for IMOs: IM!
In reality, IM requires a diverse set of different technical and non-technical skill sets. OCHA currently recognizes five skillsets, which each map to specific skills and IM activities. A strong IM team needs members that each have one or more of these skillsets.
Skillsets
Coordination: This is primarily a ‘soft-skill’ specialization. Coordination includes management of an IM team, coordination with partners through an IM Working Group, advising the Head of Office on IM issues, recruitment, planning and day-to-day management of products and people.
Content Management: This skillset is about making information easy to find and manage. Content management includes overseeing information sharing platforms like ReliefWeb Response to make sure the content is up-to-date and easy to find, overseeing document management systems and doing data entry and basic processing. Content management also includes working with partners to make sure they contribute data and information to common systems like FTS and OPS.
Data Analysis: This skillset is about working with data and information to improve situational awareness and support evidence-based planning and operations. Data analysts need to work with decision-makers and subject-matter experts to do effective analysis on impact, severity, needs, response and gaps. Data analysis is used to calculate populations in need and develop Humanitarian Needs Overviews.
Mapping: The mapping skillset is about using geographical information systems (GIS) and other tools to analyze and present spatial data. Mapping includes working on spatial common operational datasets (CODs), creating reference and operational maps, and using GIS to perform spatial analysis.
Visualization: The visualization skillset is used to turn information in insight and knowledge. It involves taking often complex data and presenting in a format that’s easy to understand and tailored for a specific audience. Visualization is used to create products such as snapshots, dashboard and infographics.
Roles
Every IMO will usually have strengths in more than one skillset. They might be an expert in Mapping, but also be comfortable doing basic visualization and also coordinating an IM Working Group meeting on CODs. We call these IMOs ‘Generalists’, because they have multiple skillsets. Other IMOs are ‘specialists’ because they spend almost all of their time working in a single skillset. The head of an IM team, for example, might not have very strong technical IM skills, but be very experienced in the ‘coordination’ skillset. We call this IMO at ‘specialist’, because they are particularly strong in one skillset (coordination) but not in the others.
A small team, especially offices that have only one or two IMOs, will need to have generalists, so they can still perform all of the activities of an office. A large office, meanwhile, can afford to have multiple specialists. When building a team, it’s vital to choose staff in a way that ensures the team includes all of the skillsets, regardless of team size.
Hardware and Software Procurement
Overview
All OCHA staff have access to the OCHA Global Office (OCHA GO) suite of Microsoft 365 Products (Access, Excel, Onenote, Outlook, Powerpoint, Word, Skype for Business, and a 1TB storage on OneDrive for Business). Additionally, each OCHA office can have a 1TB shared drive to manage office data through Microsoft SharePoint called team site. However, an IM unit needs additional software to process, analyze, and disseminate information. The list of tools normally used for an IMU can be found under the tools section in this toolbox
Procedure for Procurement of Hardware and Software
-
ICT equipment catalogue which lists all OCHA-supported products, including pricing and specifications.
-
To procure esri products (ArcGIS) please see the esri ArcGIS page in the toolbox. ESRI Emergency ArcGIS License: OCHA and ESRI have an agreement whereby a country office may benefit from obtaining free licenses up to six months under ESRI’s disaster response programme.
-
Adobe Creative Suite: Photoshop, InDesign, Illustrator Draw, Illustrator. OCHA offices should make a request as per guidance on OCHA hub under the section Adobe Licences .
-
Tableau: Tableau Public and Reader are free. Tableau Desktop and Server require a license. The HDX / Centre for Humanitarian Data team has obtained a limited number of Tableau Desktop licenses from the Tableau Foundation.
-
PowerBI: Microsoft Power BI is part of OCHA GO and all OCHA staff are Power BI users. Therefore they can publish to the web and the consumers of the published report (the readers, viewers) do not need to be Power BI users. Also, there are two licenses for Power BI, Power BI Pro, and Power BI Premium. The differences between Free, Pro, and Premium users are centered around sharing and collaboration. OCHA staff can request a Power Bi Pro license by going to the OCHA 365 Learning Centre
Software Requirements
Based on discussions in the first meeting of the IM global functional team the following software was seen as necessary for all OCHA offices:
-
ArcGIS v10.5 Standard
-
ArcGIS Advanced one license only per office if needed
-
-
Adobe Suite
-
Acrobat Pro
-
Illustrator
-
InDesign
-
Photoshop
-
-
Mail Chimp
Discussions are underway to determine the best approach to ensuring that all OCHA field offices have the necessary software at reasonable corporate rates.
Overview
Knowledge management is a key function of each and every OCHA office. The ability to store and retrieve files and documents easily and quickly is extremely important. In this section you will find information on: setting up the IMU folder structure, file naming convention, metadata, and best practices from country offices.
Process
The purpose of the following is to provide a set of clear procedures and data structures that can support the varied uses of datasets within OCHA. In order to be considered, a given practice must help OCHA meet the following criteria:
-
Predictability of data filing: new staff should be able to easily locate a given dataset
-
Archiving: out of date data sets are retained but do not clutter the file system
-
Ease of updating map products: updating data sets should not break documents that link to them
-
Off-site duplication of data: when ‘official’ backup systems are not in place, it must be easy to synchronize data to other locations
-
Flexibility to work quickly: during emergency responses good data management supports the need to work quickly while maintaining sufficient order in the filing system to allow new staff to easily assume their duties
-
Interoperability: the file formats and data structures must support data sharing with other members of the humanitarian community
-
Fulfil mandated roles: OCHA has been mandated to be the guardian of the Common Operational Datasets. Any best practice must allow OCHA to fulfil that duty.
-
Respect data confidentiality and security: data management strategies must ensure that sensitive data are kept secure
Technology: Tools, Software, Platform
Overview
All IMOs need to use a wide array of tools to complete the many tasks in an IM unit. In the following pages you will find the most used tools. If you would like to add content, make a suggestion, or tell us what we are missing please contact FIS
Typical IMU Tools
The following list identifies the types of software and platforms commonly used in IMUs. Their specific use, how to obtain the software, procurement, trainings and resources is available on the respective pages.
|
|
|
Data Management
|
|
Data/File Sharing |
||
|
Social Media
|
Power BI
Overview
What is Power BI
Microsoft Power BI is a collection of software services, applications, and connectors that work together to turn related and unrelated sources of data into coherent, visually immersive and interactive insights. With its simple user interface and availability as part of the Office 365 package, Power BI has become a standard business intelligence/data visualization tool of OCHA.
Whether your data is a simple Microsoft Excel workbook, or a collection of cloud-based and on-premises hybrid data warehouses, Power BI lets you easily connect, clean, and model your data without affecting the underlying source. The broad catalogue of built-in and add-on visualization options allows creating neat and easy-read summaries of both simple and complex data. Finally, Power BI allows sharing of the final work with either public or restricted audiences.
The components of Power BI
Power BI consists of a Microsoft Windows desktop application called Power BI Desktop, an online SaaS (Software as a Service) called the Power BI service, and mobile Power BI apps available for phones and tablets.
These three elements — Desktop, the service, andthe Mobile apps — are designed to let people create, share, and consume business insights in the way most convenient for their role and goals.
Workspaces
Workspaces are containers for dashboards, reports, datasets, and dataflows in Power BI. There are two types of workspaces: My workspace and workspaces.
-
My workspace is the personal workspace for any Power BI customer to work with your own content. Only you have access to your My workspace. You can share dashboards and reports from your My Workspace. If you want to collaborate on dashboards and reports, or create an app, then you want to work in a workspace.
-
Workspaces are used to collaborate and share content with colleagues. You can add colleagues to your workspaces and collaborate on dashboards, reports, and datasets. With one exception, all workspace members need Power BI Pro licenses.
Workspaces are also the places where you create, publish, and manage apps for your organization. Think of workspaces as staging areas and containers for the content that will make up a Power BI app. So what is an app? An app is a collection of dashboards and reports built to deliver key metrics to the Power BI consumers in your organization. Apps are interactive, but consumers cannot edit them. App consumers, the colleagues who have access to the apps, do not necessarily need Pro licenses.
Process – OCHA Product Support
PowerBI Pro License and OCHA Workspace
Complete the License and Work Space Request form to request Pro licenses and Premium workspaces. To optimize the efficient use of licenses in OCHA, licenses that are not used for four months or longer will be deactivated if no longer needed.
Tips
-
Use PCodes and ISO codes to connect different datasets. Wherever possible, the most convenient way to connect two or more datasets, is using PCodes. When using other attributes such as name of a country, district or settlement, there is a risk that the spelling is not the same across the datasets, creating a risk of missed links.
-
Pay attention to the column data type. For correct display of numeric data in the visuals, the data type should be set as “Integer” or “Decimal”. If set as “Multiple”, it is not possible to perform mathematical functions (such as SUM, DIVIDE, MULTIPLY) with the data.
-
Use the Power Query tool to create aliases. Ever come across column or attribute names such as HHs_Female_U18_1-3_PWD_Yes or potableWaterPerHhWithIdpStatusBaselineApril2020? While technically necessary when using KoBo or other MDC tool, such names tend to be inconvenient or even unreadable to the end users. Generally speaking, end users prefer to see standard spacing instead of camel cases or underscores used by KoBo or similar tools. Hence, where necessary, you can use Power Query to create duplicate columns with aliases, increasing the overall user experience.
-
Leave an “expansion space” for your visualizations. Especially in large-scale sudden onset disaster situations, the figures tend to grow in a rapid pace. In addition to the absolute figures, the number of categories is likely to increase: more districts, more distinct groups of people affected, more response organizations. The increasing number of figures and categories means further population of the visualization elements, whether in a map, chart or table formats. Do not squeeze your visuals into a too small space, but make sure that the visuals will remain readable and meaningful even with rapid changes of the situation. The same applies to the map elements: check that the zoom level of the map will expand as new geographical areas are being covered.
-
Consider the strengths and weaknesses of each map tool option. Power BI provides several different tools to create maps: the built-in location map, filled map and shapemap along with the add ins from MapBox and ArcGIS. While each tool comes with certain technical and visual advantages, each of them also has certain limitations. Please refer to the Map visualization in Power BI page for full information about the best use cases for each map tool.
-
Practical Power BI tips from ROWCA:
Got any useful Power BI tips? Please contact us to share your tips on this page.
Outputs/Resources
-
For more tutorials on Power BI and visualization, click the tutorials page
Views: 11


Leave a Reply