> For the complete documentation index, see [llms.txt](https://standards.spdci.org/standards/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://standards.spdci.org/standards/dci-standards/early-warning-systems/wip-early-warning-systems-and-sp-system-interface/9.-ews/1.2-process/prs.ews.02-sp-system-share-aggregated-data-for-analysis/example-1-aggregated-sp-data-exchange-for-risk-assessment.md).

# Example 1: Aggregated SP Data Exchange for Risk Assessment

### Process Flow

This example illustrates how the [PRS.EWS.02: SP system share aggregated data for analysis](/standards/dci-standards/early-warning-systems/wip-early-warning-systems-and-sp-system-interface/9.-ews/1.2-process/prs.ews.02-sp-system-share-aggregated-data-for-analysis.md) process can be implemented. It describes how Social Protection (SP) systems provide aggregated vulnerability and beneficiary data to an Impact-Based Early Warning System (IB-EWS). The purpose is to enable the IB-EWS to combine hazard forecasts with exposure and vulnerability data in order to generate people-centred impact forecasts, risk analytics, and early warning products to support anticipatory action planning.

The SP system does not trigger any interventions through this process. It functions as a controlled data provider, while the IB-EWS is responsible for integrating the data into hazard models, producing impact-based risk outputs, and supporting decision-making by disaster risk management (DRM) and social protection authorities.

### **Process Flow:  Sharing Data Aggregated to EWS for analysis assessment**

<table><thead><tr><th width="213">Section </th><th>Description </th></tr></thead><tbody><tr><td>Actors and Entities</td><td>Early Warning System for (EWS), Social Protection (SP) system</td></tr><tr><td>Assumptions</td><td><p></p><p></p><ul><li>Formal data-sharing agreement between SP system and EWS institution.</li><li>Defined EWS framework linking hazard, exposure, and vulnerability components.</li><li>Standardized geographic reference system (admin boundaries, grids, or hazard zones).</li><li>Agreed vulnerability indicators and aggregation rules from SP system.</li><li>Secure interoperability mechanism (API, secure transfer, or scheduled data pipeline).</li><li>Data protection and anonymization rules approved and operational.</li></ul></td></tr><tr><td>Prerequisites</td><td><p></p><ul><li>The Social Protection system has operational access to the required databases for aggregation.</li><li>Aggregated data (counts, summaries, or indicators) is available in the system for extraction.</li><li>The SP system has the technical capability to process and transmit data in the agreed formats.</li></ul></td></tr><tr><td>Process Inputs</td><td></td></tr><tr><td>Process Flow Steps</td><td><p><strong>Step 1:</strong> </p><ul><li>EWS initiates request for SP aggregated vulnerability data OR receives scheduled data feed.</li><li><p>Request specifies:</p><ul><li>Geographic resolution</li><li>Time period</li><li>Required indicators (e.g., vulnerable households, poverty proxy, disability, livelihood type)</li></ul></li></ul><p><strong>Step 2:</strong> </p><ul><li>SP system extracts relevant beneficiary and vulnerability datasets.</li><li>Data is aggregated by agreed spatial and demographic dimensions.</li><li>Personally identifiable information (PII) is removed.</li></ul><p><strong>Step 3:</strong> </p><ul><li><p>SP system performs:</p><ul><li>Completeness checks</li><li>Threshold validation (minimum cell counts for anonymization)</li><li>Consistency checks with registry data</li></ul></li></ul><p><strong>Step 4:</strong> </p><ul><li>EWS ingests SP data into vulnerability layer.</li><li><p>Data is aligned with:</p><ul><li>Hazard forecasts (meteorological inputs)</li><li>Exposure datasets (population, infrastructure, land use)</li></ul></li></ul><p><strong>Step 5:</strong> </p><p>EWS runs analytical models combining:</p><ul><li>Hazard intensity and probability</li><li>Exposure distribution</li><li>Vulnerability (SP aggregated data)</li></ul></td></tr><tr><td>Outputs</td><td><p></p><ul><li><p>EWS generates:</p><ul><li>Impact-based early warning bulletins</li><li>Risk maps and dashboards</li><li>Scenario simulations for decision support</li></ul></li><li>Outputs are shared with DRM and relevant agencies.</li></ul></td></tr><tr><td>Control Points</td><td><p></p><ul><li><p><strong>Data Governance Approval</strong></p><ul><li>Ensures compliance with legal and ethical data-sharing frameworks.</li></ul></li><li><p><strong>Anonymization &#x26; Aggregation Control</strong></p><ul><li>Verifies no PII is included and minimum aggregation thresholds are respected.</li></ul></li><li><p><strong>Data Quality Assurance</strong></p><ul><li>Validates accuracy, completeness, and consistency before transfer.</li></ul></li><li><p><strong>Interoperability Validation</strong></p><ul><li>Ensures geographic and indicator alignment between SP and IB-EWS systems.</li></ul></li><li><p><strong>Access Control &#x26; Security</strong></p><ul><li>Ensures only authorized systems and users can access shared datasets.</li></ul></li><li><p><strong>Model Integrity Check (EWS)</strong></p><ul><li>Ensures SP data is correctly integrated into risk models without distortion or duplication.</li></ul></li></ul></td></tr><tr><td>Exception Handling</td><td><p> <strong>Incomplete or Missing SP Data</strong></p><ul><li><strong>Trigger:</strong> Missing geographic coverage or incomplete registry data.</li><li><p><strong>Action:</strong></p><ul><li>EWS uses fallback vulnerability datasets (census, proxies).</li><li>SP system flags gaps for data improvement cycle.</li></ul></li></ul><p><strong>Data Quality Failure</strong></p><ul><li><strong>Trigger:</strong> Validation errors (inconsistencies, outdated records).</li><li><p><strong>Action:</strong></p><ul><li>Data is rejected and returned to SP system for correction.</li><li>No ingestion into EWS occurs until resolved.</li></ul></li></ul><p><strong>Geographic Mismatch</strong></p><ul><li><strong>Trigger:</strong> Misaligned administrative boundaries or coding systems.</li><li><p><strong>Action:</strong></p><ul><li>Mapping layer applied OR data held until reconciliation is completed.</li></ul></li></ul></td></tr></tbody></table>

### Diagram 1 - Aggregated SP Data Exchange for Risk Analysis

<figure><img src="/files/fxz0pZ3nosFOhU9qYmKB" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://standards.spdci.org/standards/dci-standards/early-warning-systems/wip-early-warning-systems-and-sp-system-interface/9.-ews/1.2-process/prs.ews.02-sp-system-share-aggregated-data-for-analysis/example-1-aggregated-sp-data-exchange-for-risk-assessment.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.