Is it legal to use or contribute to a PLEXOS-to-PyPSA data converter?

Modelling Open modelling
, , , ,
1

Many modellers and planners hold data in PLEXOS XML formats, but want to work with open-source tools like PyPSA. This raises a common question: Can I legally use or help build a data converter between PLEXOS and PyPSA?

Before we dive in, a quick (but important) disclaimer — better safe than sorry:

PLEXOS is a registered trademark of Energy Exemplar Pty Ltd. This discussion and any related tools are independent and not affiliated with, endorsed by, or sponsored by Energy Exemplar. References to PLEXOS are made solely to enable interoperability with open-source tools using user-generated data.

With the disclaimer out of the way, let’s get to the key points:

:white_check_mark: Using such a tool is legal

If you have access to your own exported/ or prepared PLEXOS XML files, you can legally convert and work with them elsewhere. Why?

  • :card_index_dividers: You own your user-generated XML — Energy Exemplar does not own the data you created.

  • :gear: File formats and schemas are functional, not protected expressions under copyright.

  • :outbox_tray: Transforming your data for use in other software is allowed — it doesn’t violate IP law.

Key point: Using a tool to work with your own PLEXOS output in another model is lawful.

:wrench: Contributing to or building a converter is legal

Under both EU and US law, building converters for interoperability is protected, even if the proprietary license says otherwise.

  • :mag: EU Directive 2009/24/EC allows reverse engineering “to achieve interoperability” — and voids license clauses that try to prevent it.

  • :us: US DMCA §1201(f) provides similar rights for compatibility-focused development.

  • :stop_sign: Important for building such a converter only (self-generated) user data and publicly observable formats can be used → Luckily, many PLEXOS XML files are openly shared.

Key point: You may legally build or contribute to a converter, as long as you use open available data or your own user data.

:speech_balloon: Join the effort

We’re looking for:

  • Feedback on the legal framing

  • Input on shared guidelines for safe, open interoperability

  • Contributors for testing or development (:link: Link to the GitHub repo is coming soon, stay updated by joining our PyPSA Discord server or follow Open Energy Transition on LinkedIn)

Let’s make energy planning tools work better—together and lawfully.

— Open Energy Transition Team

1 Like
2

@MaxParzen This recent tooling survey mentions several FOSS tools but none that interact directly with PLEXOS XML. Nonetheless, see the section on co‑simulation initiatives for some clues:

3

Hi,

This is a nice topic since I’ve done such converters for Ree and entso-e some years ago.

Energy exemplar’s ex-VP (Steven Broad) published the internal data structures in their github repo some years ago. With that I managed to make a simple converter to GridCal.

The thing is that since plexos is a spaguetti-like software, there is no unique way of modelling. Another way of converting is to convert the excel file they produce.

So, for a proper converter there should be a decent amount of plexos xml models open for conversion testing.

BTW, I still find it amazing how all those surveys keep leaving the best out.

BR,
Santiago

1 Like
4

Agree - that’s key! We managed to get hold of to some of realistic PLEXOS xml files. This data was shared by some folks in the public domain to increase reproducibility of their studies.

Please, let us know if you have more public accessible PLEXOS XML files available and share a link at info@openenergytransition.org . Maybe worth creating a public list like: GitHub - open-energy-transition/Awesome-Electric-Grid-Mapping: A curated list of resources in the field of electric grid mapping to improve global open data coverage, harmonization and quality for a sustainable energy transition.

5

Hi,

Do you have any link to those files?

I abandoned the converter some time ago exactly because of the lack of public plexos models… I might give it a go with this eventually

BR,
Santiago

6

The very recently open‑sourced EPRI REGEN model (announced here) describes a REGEN ▸ PLEXOS linkage on slide 16. This functionality will:

“automatically move input and output data from REGEN to PLEXOS”

I guess @MaxParzen was looking for that data traffic to flow in the other direction?

1 Like
7

Correct! I know EPRI is working on some interoperability tool but I couldn’t find anything public just yet: Code search results · GitHub . The REGEN tool has also no code reference to it.