A shared language for sanitation infrastructure

mWater's Sanitation Asset Standard makes sewered and on-site sanitation assets consistent, portable, and understandable across service providers, regulators, development partners, and software platforms.

27asset types
211standard attributes
2sanitation system families
CC BY-SAopen licence

Essential infrastructure, fragmented data

A pit latrine, vacuum truck, sewer main, pump, and treatment plant all belong to sanitation service chains, yet their records usually sit in unrelated surveys, spreadsheets, proprietary schemas, and regional standards. That prevents comparison, raises switching costs, and forces each organization to rebuild the same conceptual model.

Design question

How can one standard describe the diversity of sanitation systems without imposing unnecessary complexity on any individual user?

Global scope without a rigid template

The work began under USAID IUWASH Tangguh in 2024 and was completed through mWater's own investment in 2026. Product implementation was facilitated by Petri, with the published standard authored by Susan Lamb and shaped through literature review, existing schemas, user needs, and contextual testing.

On-site sanitationContainmentEmptyingTransportTreatment
Shared modelAssetsAttributesRelationships
Sewered sanitationCollectionConveyancePumpingTreatment

Reuse familiar foundations

Fields shared with mWater's Water Asset Standard use the same language, reducing the learning curve and keeping connected infrastructure coherent.

Model relationships, not isolated objects

Assets form hierarchies: pumps belong to stations, stations to systems, and service-chain elements connect across collection, transport, and treatment.

Reveal only relevant complexity

No asset type or attribute is mandatory. Conditional fields allow a small operator and a national regulator to use the same model without seeing the same interface.

Keep the standard platform-independent

The specification can be used in spreadsheets, other software, and institutional data models—not only in mWater.

One model, several practical routes to adoption

Practitioners can map assets in the mWater mobile app, import them through the Portal, or use an AI assistant through the MCP server to align existing records with the standard. Survey monitoring and Workflows then attach operational history to the permanent asset records.

01

Collect once

Record the asset and its identifying properties as a durable entity rather than recreating it in every monitoring round.

02

Understand consistently

Use common asset types and attributes across regions, system types, and implementing organizations.

03

Reuse across systems

Move data between platforms and institutions with less remapping and lower switching costs.