![Open Energy Transition](https://s101-recruiting.cdn.greenhouse.io/external_greenhouse_job_boards/logos/400/238/710/original/oet_standard_red_svg.png?1762766755")
Models do not decide what gets built. They help produce evidence that must survive technical, institutional, political, regulatory and financing gates before capital is committed.
The highest-leverage portfolio combines shared technical infrastructure with decision-linked deployments and the ecosystem capacity to sustain adoption beyond OET. Deployment leadership can sit with OET, the institution or a trusted regional partner.
Make open planning reliable and institution-ready, so each country does not start from zero.
Use the delivery model that best fits the institution: OET-led, institution-led or partner-led.
Lower the cost of adoption by enabling local institutions, partners and communities to deliver more of the work.
The public institution always owns the mandate, official process and final decision. What varies is who leads the adoption effort. Local partners can contribute in any model.
OET leads the technical design, implementation, validation and adoption support needed to build trust and move the institution toward routine use. The institution owns the official process and capability. Local partners can join where useful.
The institution has already adopted open source with its own staff and leads the workflow. OET strengthens the effort through gap closure, quality assurance, training, troubleshooting, workflow hardening and maintainer access.
A trusted regional organisation leads the relationship, convening and local delivery—for example ICSC with Philippine institutions or IESR with Indonesian institutions. OET supplies modelling, software and data depth; the ministry, regulator or grid operator owns the resulting capability and decision.
A country opportunity is strongest when it is linked to a real institutional decision window and leaves capability behind.
A formal plan, assessment or procurement will use the work within roughly 12-18 months.
A ministry, regulator, system operator or utility owns the process and has authority to use the evidence.
OET, the institution or a trusted partner can lead delivery, but an internal champion and local continuity must be clear.
OET can remove a specific blocker in tools, data, validation, workflow, training or support.
The deployment creates methods, code, data pipelines, training or proof that lowers the cost of future adoption.
Open-source adoption does not need to begin with a full migration. The best first step depends on the planning question, legacy dependency and risk appetite.
Use a new planning question to build a decision-grade workflow without touching existing proprietary delivery.
Best for: early proof and new requirements.Replicate a selected existing question, compare results and explain methodological or data differences.
Best for: trust, validation and institutional buy-in.Transfer a proven workflow with training, support, feature closure, GUI and integration where useful.
Best for: sustained operational capability.