Building an OSPO: The Alliander Experiences
summary
Alliander frames its OSPO around concrete outputs: a public website and GitHub projects (including a self‑published Weather Provider API), an inner source portal that surfaces tagged repos, a reviewed license list now enforced via CI/CD checks, and hackathons to bootstrap contribution. The OSPO runs as a core team plus expert consultants, meets biweekly, and some members allocate ~50% time. Company scale is explicit — ~6 million customer connections, 90k km electricity and 40k km gas grids — and open source activity is already moving from pilots to repeatable practice.
AI-written summary · about
chapters (10)
- 0:00Start
- 0:25Introduction
- 2:12Key challenges of a Distribution system operator
- 3:46Why we started an OSPO
- 5:53The activities of the OSPO
- 9:39Who are in the OSPO
- 10:52Journey of Alliander's OSPO
- 23:24What our collegues are saying
- 23:52What we've learned
- 26:29Questions?
related talks
29mPanel Discussion: The Rise of OSPOs in Grid Operations: Insights and Lessons From Hydro-Québec...
30mBuilding OSPOs in Practice...
52mA-Typical but Fruitful Public Sector Collaborations Through OSPO's
29mHow E.ON's OSPO Maps Energy Open Source Projects To Real World U...
37mOSPO is a Key Element for your Company, but also for the OS Ecosystem
30mDemystifying OSPOs
34mThe Role of OSPO Manager for the Organization’s Success
21mToward Sustainable OSPO: Lessons Learned From One Year of OSPO...
