Bali
For the old way of scoring, Bali looked like a problem. Metroverse does not cover Denpasar, and customs data is patchy, so we could not measure what it imports and wastes: what we call PITO, products in, trash out, buy far and waste near. But Bali is strong on the other side, DIDO: data in, data out, sensing what is happening, sharing it openly, and making more locally. Smart Citizen Bali, Fab Lab Bali, MDG and CAST fill the DIDO side without needing full import and customs data. We use the same PITO measure as every other pilot, and we do not claim Metroverse ECI coverage we do not have. This is the pilot that asks the sharpest question: can a city sense, share and make its way to less waste, even when its import numbers are hard to pin down?
What each cell looks like once it holds real data.
Province-level data comes from Bali Satu Data (organised by the Tri Hita Karana framework) and the national portal data.go.id. Community-level data comes through the Banjar, Bali's traditional councils. The DIDO side, what the city senses and shares, reads high. The PITO side, what it imports and wastes, is only partial, and we mark it clearly wherever customs data is missing.
Why this pilot matters for the methodology.
The earlier versions of the Index measured one number, and by that measure Bali was a problem. There is no Metroverse ECI for Denpasar. Customs data is partial. The Economic × City cell stays mostly dark. Reading the city as PITO and DIDO changes the picture. Bali's DIDO runs strong: dense Smart Citizen sensors, active fab labs, the traditional councils, and the open-data layer PLANETAI is building all fill the DIDO side without needing import or customs numbers. So Bali becomes its own kind of case, strong on data in and out, only partial on products in and trash out. It is the one that tests whether sensing, sharing and making locally can pull waste down even when the import baseline is hard to measure.