plan_mandalay_presentation



plan_mandalay_presentation

0 0


plan_mandalay_presentation


On Github SEL-Columbia / plan_mandalay_presentation

plan_mandalay -

  • a data analysis tool for real world development
  • precludes need for GIS or programming expertise

  • GOAL: Enable planners^ to assess NetworkPlanner parameters and sequenced estimates in a responsive and interactive visualization

    • adjust parameter inputs
    • recalculate estimated costs
    • then export/share those results.

^Planners include primarily the Government of Myanmar and secondarily potential infrastructure investors and donors

features -

Plan Mandalay’s primary features are listed below

  • render Points of NetworkPlanner output (sequenced- results.csv) styled per technology type
  • display table summary with aggregations
  • Modify single village point's attributes in embedded side ‘table’
  • re-aggregate costs of sequenced-results.csv as parameters are updated
  • allow basemap option with satellite imagery
  • output csv file with updated cost parameters propagated throughout
  • user can page through dataset via administrative level
  • codify calculations needed to calculate some minigrid costs
  • add save functionality, to preserve scene and share with others
  • framework for working offline or with intermittent internet

use cases:

GOM: Plan Mandalay’s primary clients are agencies in the government of Myanmar. The GOM will better be able to adjust non-grid parameters per their intended SHS, hybrid, hydro, etc. pre-electrification program. These key stakeholders include among others

  • Ministry of Livestock, Fisheries and Rural Development,
  • Ministry of Electrical Power,
  • MIMU

Donors: The secondary client will be potential infrastructure investors and donors. These investors will be able to better interpret and understand NetworkPlanner and the expected efficacy of their investments with their assumptions.

software overview

demo time!

mock-up for future

obstacles & future

  • future
    • calculator (via tangle.js)
    • aggregation (via level db)
  • obstacles
    • user focussed design
    • we are on a budget that may have already expired