-
Notifications
You must be signed in to change notification settings - Fork 0
HPC Planning Bridge Tool API
This tool is a new HPC tool that will be very useful to OCHA and for cluster coordinators. It fills an important gap in the current HPC tools by creating a bridging dashboard between the RPM and the Projects Module. (Hence we call it the ‘bridge tool.’) It thus allows cluster coordinators to proactively guide the partners’ project development so as to best cover the priority activities, per geographical area and target population.
Cluster coordinators classically decide on their activities and targets based on the HNO (plus their estimate of cluster capacity), with geographical detail down to lowest admin level i.e. admin 3 at least, plus target populations therein (e.g. IDPs, host communities, returnees). They upload these activities and targets onto RPM. Users of the PM can then see the same information when they draft their projects—they choose a cluster-registered activity, see that activity’s overall target, and note their project target, with the option of geo and target population breakdown. The gap arose from the fact that cluster coordinators could not easily see what the draft projects were adding up to. For example, the Food Security cluster coordinator sets a target for the main food-assistance activity of 1 million people (X in this district, Y in that district, etc.). Food Security partners then get busy drafting their projects, including this activity. But during this drafting, or even after project finalization, the cluster coordinator could not see how many people the draft projects collectively proposed to reach – whether it was way under 1 million, way over, or about right. Neither could they see which districts had a surplus of planned outputs (according to the draft projects) vis-à-vis the original cluster target, and which districts had a deficiency. The cluster coordinators were thus ‘flying blind’ when trying to fulfil their obligation to keep the projects aligned with the priority needs.
The bridge tool now allows them to see all this, in an easy dashboard view. The main advantage is that it allows the cluster coordinator (supported by OCHA) to intervene in and ‘massage’ the project-development process to adjust those surpluses and deficiencies, before the projects become final – getting project owners to move some planned outputs from a surplus district (or target population) to a deficient one; getting them to cut, when the projects’ collective proposed outputs exceed the cluster target for that activity; or getting them to expand, if the projects’ targets collectively fall short.
This tool can also be useful for countries that practice activity-based planning, and only record projects on the PM post facto: as projects are funded and recorded, the bridge tool will show the cluster coordinator what are the totals per activity (and geo unit etc.) of the projects that are actually funded and implemented. With this info, cluster coordinators can guide other partners who are drafting projects and seeking funding, so that they fill gaps. We encourage you to discuss this with your cluster coordinators ASAP, and hopefully use it soon.
The HPC Planning Bridge Tool API is an analytical tool designed to leverage HPC data and can be customized to suit various contexts. It includes for each plan the following datasets:
-
organizations: Includes the organizations involved with the plan. Organizations can be the partners submitting projects, partners receiving funds and donors sending funds.
-
locations: Includes all updates CODs at all Admin levels of the plan.
-
projects: All projects that have been submitted against the plan, including project ID, code and name, status, clusters, organizations, and all condition field values. Condition fields are custom questions answered for each projects such as Gender mainstreaming, CASH ..etc.
-
planClusters: Includes all field clusters activated which have caseloads and financial requirements.
-
planGlobalClusters: Global clusters associated with plan clusters which have caseloads and financial requirements.
-
planEntities: Includes both plan and cluster level objectives and activities such as Strategic Objectives, Cluster Objectives and Cluster Activities. This field also includes information about the alignment upper level entities
-
caseloads are metrics relating to populations, such as:
- Total population
- People affected
- People in need
- People targeted by plan
This field contains such information as description and cluster target as well as the target for each project submitted against this cluster
-
indicators are more general, and can be used to track progress. Data captured for indicators are the indicators descriptions, metrics such as Indicator target and the project targets. Disaggregated data for the indicators can also be obtained when the proper options are set true as describe below.
-
fundingData: broken down by plan cluster, global cluster, and by donor, receiving organization and receiving project.
-
conditionFields: contains information such as name and question type about the custom questions to be responded by project owner during project submissions.
The bridge tool can be used in a number of different ways:
- Using the API Directly
- Using the Excel Workbook
- Using our Dashboard Tool. Watch a video illustrating using the Bridge Tool in Nigeria context
Usage of the API and Excel Workbook are detailed in this document, but if you would like to use the dashboard, please contact [email protected] and we can help you set this tool up for you.
API requests should be GET requests to the following URL.
https://api.hpc.tools/v2/planningBridgeTool
With the following query parameters:
| Parameter | Required / Default Value | Details |
|---|---|---|
planId |
Required | The numeric ID of the plan you wish to get data for. |
includeDisaggregatedData |
Optional (default: false) |
Set to true if disaggregated data should be included |
disaggregationOnlyTotal |
Optional (default: false) |
Set to true if per-project budget breakdowns should be included |
includeBudgetBreakdowns |
Optional (default: false) |
Set to true if per-project budget breakdowns should be included |
includeConditionFields |
Optional (default: false) |
Set to true if condition fields answers should be included |
includeFundingData |
Optional (default: false) |
Set to true if per-project budget breakdowns should be included |
includeProjectsComments |
Optional (default: false) |
Set to true if per-project budget breakdowns should be included |
For example, requests could look like the following:
-
GET https://api.hpc.tools//v2/planningBridgeTool?planId=1172 -
GET https://api.hpc.tools//v2/planningBridgeTool?planId=1172&includeDisaggregatedData=True&disaggregationOnlyTotal=true&includeBudgetBreakdowns=True&includeConditionFields=True
Responses will look something like this, the exact shape of the data will depend
on which parameters you have set to true above.
{
"data": {
"organizations": [
{
"id": 3468,
"name": "SOS Children's Villages",
"abbreviation": "SOS",
"orgType": "NGOs",
"orgSubtype": "International NGOs",
"url": "https://www.internationalsos.com/"
},
{
"id": 13795,
"name": "Instituto Salvadoreño del Migrante",
"abbreviation": "INSAMI",
"orgType": "NGOs",
"orgSubtype": "National NGOs/CSOs",
"url": "https://insami.foundation/"
},
{
"id": 4293,
"name": "United Nations Population Fund",
"abbreviation": "UNFPA",
"orgType": "Multilateral Organizations",
"orgSubtype": "UN Agencies",
"url": "https://www.unfpa.org"
}
],
"locations": [
{
"id": 67,
"pcode": "SV",
"name": "El Salvador",
"adminLevel": 0,
"latitude": 13.72764124904,
"longitude": -88.863153241768,
"parentLocationId": null
},
{
"id": 25921725,
"pcode": "SV1423",
"name": "Usulután",
"adminLevel": 2,
"latitude": 13.2736585,
"longitude": -88.42972482,
"parentLocationId": 25921461
}
],
"projects": [
{
"projectId": 208625,
"projectName": "Fortaleciendo la Coordinación Humanitaria en El Salvador",
"projectCode": "HSLV24-CSS-208625-1",
"projectStatus": "accepted",
"projectBudgetUSD": 339396,
"projectOrganizations": [
4396
],
"planClusters": [
{
"clusterId": 7553,
"clusterStatus": "accepted"
}
]
},
{
"projectId": 208926,
"projectName": "Mejorados los mecanismos para la protección integral de niñas, niños y adolescentes en contextos de movilidad humana en El Salvador.",
"projectCode": "HSLV24-PRO-208926-1",
"projectStatus": "accepted",
"projectBudgetUSD": 200000,
"projectOrganizations": [
9414
],
"planClusters": [
{
"clusterId": 7547,
"clusterStatus": "accepted"
}
]
},
{
"projectId": 212587,
"projectName": "Anticipatory actions to save lives and agricultural livelihoods affected by El Niño 2023-2024 phenomenon in El Salvador",
"projectCode": "HSLV24-FSC-212587-1",
"projectStatus": "accepted",
"projectBudgetUSD": 10700000,
"projectOrganizations": [
4399
],
"planClusters": [
{
"clusterId": 7313,
"clusterStatus": "accepted"
}
]
}
],
"planClusters": [
{
"clusterId": 7549,
"clusterName": "Alojamiento de Emergencias",
"clusterCustomRef": "CLSHL"
},
{
"clusterId": 7552,
"clusterName": "Coordinación y Gestión de Albergues Temporales (CCCM)",
"clusterCustomRef": "CLCCM"
}
],
"planGlobalClusters": [
{
"planClusters": [
7547
],
"globalClusterId": 13,
"globalClusterCode": "PRO-GBV",
"globalClusterName": "Protection - Gender-Based Violence",
"globalClusterType": "aor"
},
{
"planClusters": [
7547
],
"globalClusterId": 12,
"globalClusterCode": "PRO-CPN",
"globalClusterName": "Protection - Child Protection",
"globalClusterType": "aor"
},
],
"planEntities": [
{
"entityId": 25902,
"type": "CO",
"entityRef": "CLHEA/CO1",
"entityDescription": "Contribuir a la capacidad de atención básica y asistencia humanitaria en salud de las personas afectadas y en riesgo con necesidades ocasionadas por emergencias humanitarias, particularmente por el fenómeno del niño y movilidad humana.",
"planCluster": 7550,
"supports": [
25846,
25847
]
},
{
"entityId": 25907,
"type": "CO",
"entityRef": "CLPRO/COVBG1",
"entityDescription": "Mejorar el acceso a servicios de calidad, seguros, oportunos, confidenciales y coordinados, a las mujeres y las niñas (incluidas las que tienen discapacidades, adultas mayores, indígenas, población LGBTIQ+ y en movilidad humana) víctimas y/o en riesgo de VBG, desde un enfoque centrado en las personas sobrevivientes",
"planCluster": 7547,
"supports": [
25846
]
}
],
"caseloads": [
{
"caseloadId": 45898,
"caseloadCustomRef": "CLSHL/BF1-SHL",
"caseloadType": "caseLoad",
"caseloadDescription": "Albergue y artículos no alimentarios",
"clusterId": 7549,
"clusterTarget": 6200,
"projectTargets": [
{
"projectId": 209093,
"projectTarget": 500
},
{
"projectId": 209104,
"projectTarget": 700
},
{
"projectId": 208803,
"projectTarget": 2000
},
{
"projectId": 208921,
"projectTarget": 3000
}
],
"projectTargetsByStatus": {
"accepted": {
"targetSum": 6200,
"projectCount": 4
}
}
},
{
"caseloadId": 45893,
"caseloadCustomRef": "CLPRO/BF4-PRO-GBV",
"caseloadType": "caseLoad",
"caseloadDescription": "Violencia de género (VDG)",
"clusterId": 7547,
"clusterTarget": 115000,
"projectTargets": [
{
"projectId": 209029,
"projectTarget": 0
},
{
"projectId": 209032,
"projectTarget": 0
},
{
"projectId": 209039,
"projectTarget": 0
},
{
"projectId": 209548,
"projectTarget": 0
},
{
"projectId": 208813,
"projectTarget": 0
},
{
"projectId": 209086,
"projectTarget": 0
},
{
"projectId": 208819,
"projectTarget": 0
},
{
"projectId": 208847,
"projectTarget": 0
},
{
"projectId": 208647,
"projectTarget": 0
},
{
"projectId": 208802,
"projectTarget": 15000
},
{
"projectId": 209041,
"projectTarget": 5228
},
{
"projectId": 209430,
"projectTarget": 0
},
{
"projectId": 209186,
"projectTarget": 0
},
{
"projectId": 208766,
"projectTarget": 0
},
{
"projectId": 209480,
"projectTarget": 0
},
{
"projectId": 208810,
"projectTarget": 0
},
{
"projectId": 208846,
"projectTarget": 1040
},
{
"projectId": 209369,
"projectTarget": 0
},
{
"projectId": 208968,
"projectTarget": 0
},
{
"projectId": 208970,
"projectTarget": 3400
},
{
"projectId": 208922,
"projectTarget": 500
},
{
"projectId": 208798,
"projectTarget": 10000
},
{
"projectId": 208631,
"projectTarget": 0
},
{
"projectId": 208984,
"projectTarget": 0
},
{
"projectId": 208981,
"projectTarget": 0
},
{
"projectId": 208983,
"projectTarget": 13575
},
{
"projectId": 208985,
"projectTarget": 5000
},
{
"projectId": 208987,
"projectTarget": 9141
},
{
"projectId": 208903,
"projectTarget": 8000
},
{
"projectId": 208926,
"projectTarget": 0
},
{
"projectId": 208833,
"projectTarget": 41116
},
{
"projectId": 208924,
"projectTarget": 3000
}
],
"projectTargetsByStatus": {
"accepted": {
"targetSum": 115000,
"projectCount": 32
}
}
}
],
"indicators": [
{
"indicatorId": 47521,
"clusterId": 7552,
"planEntityId": 26034,
"indicatorCustomRef": "CLCCM/CO1/IN1",
"indicatorDescription": "Número de procesos de coordinación realizados para facilitar la entrega de artículos no alimentarios en albergues temporales, centros de recepción, centros de tránsito y comunidades afectadas acorde a las necesidades de las personas afectadas.",
"unit": "Activities",
"calculationMethod": null,
"clusterTarget": 40,
"projectTargets": [
{
"projectId": 209045,
"projectTarget": 30
}
],
"projectTargetsByStatus": {
"accepted": {
"targetSum": 30,
"projectCount": 1
}
}
},
{
"indicatorId": 47522,
"clusterId": 7552,
"planEntityId": 26034,
"indicatorCustomRef": "CLCCM/CO1/IN2",
"indicatorDescription": "úmero de personas que perciben una mejora en la atención de sus necesidades básicas. (50% con base a la población atendida)",
"unit": "People",
"calculationMethod": null,
"clusterTarget": 7085,
"projectTargets": [
{
"projectId": 209419,
"projectTarget": 4000
},
{
"projectId": 209227,
"projectTarget": 1600
},
{
"projectId": 209045,
"projectTarget": 4606
}
],
"projectTargetsByStatus": {
"accepted": {
"targetSum": 10206,
"projectCount": 3
}
}
}
],
"meta": {
"language": "en"
}
},
"status": "ok"
}We have recently announced a number of upcoming changes to the HPC API,
including the development of v4 of the API that will use GraphQL at its core.
These changes are at the very early planning and development stages at the
moment, and are not yet ready to be tested or used, so for the time being we
recommend continuing to use the v2 endpoints that are documented in the
Swagger documentation at https://api.hpc.tools/docs/v2/ and in this wiki.
If you'd like to keep updated as to when these new endpoints will become available for early user feedback or use, please see the section below.
We have introduced some mailing lists that we will now be using to keep API users up-to-date, and engage with users for early testing and feedback of new API features.
If you would like to join either of these mailing lists, please send an email to [email protected] with your request:
-
This mailing list will be used for official announcements from the HPC.tools team regarding changes in the API, including new features and deprecation notices.
-
This mailing list allows for open discussion between different users of the HPC API, as well as the development team. Feel free to use this mailing list to ask for advice on how to use the API.
We will be using this mailing list to solicit early feedback for the
v4API as we continue to plan and develop it.