Hi, I am trying to transfer plexos model data to saint. In the plexos model excel sheet I found they defined start cost of generators for different scenarios like h < 8, 8 < h < 48, 8 < h < 48, h > 48, Hot Start. I found only one column in saint model exported sheet for start up cost.
Question 1: How should I handle this when SAInt allows only one startup cost?
Question 2: Have you transfered Plexos model to Saint before? If yes, any general tips or best practices?
Question 3: From a previous discussion, I knew that SAInt doesnt have option for Forced outage % and Maintenance time %. In the newer version, are these added? ( I am still using older version)
You are correct that SAInt supports only a single StartUp cost. For the time being, I would recommend just using one of the Cold/Warm/Hot StartUp costs, as this feature is not yet supported.
I have some experience translating models from PLEXOS. Both PLEXOS and SAInt have very flexible input structures, so this translation process can be a bit of a challenge. Even within each respective software, there are many different ways to achieve the same end goal depending on how the user wants to set it up.
I would recommend starting with the objects that can be mapped directly - nodes, lines, transformers, generators, etc.
Next I would recommend handling the “Memberships” in PLEXOS which will, for the most part, be implemented as properties of the “child” object in SAInt. (Although there are some exceptions, such as Generator-Reserve memberships which in SAInt are defined as an “ASVCX” obejct. Custom constraint objects are also handled slightly differently between the two software.)
Then, the “Properties” can be implemented. I like to start with the properties that do not have a “Scenario” attached to them in PLEXOS. I define these as default properties at the Network level in SAInt. Then, for each “Scenario” in PLEXOS, I create events via the excel import file format in SAInt that correspond to those “Properties” in PLEXOS.
Note that each “Model” in PLEXOS will be the equivalent of a “Scenario” in SAInt.
Finally, I tackle the “Data File” objects in PLEXOS by taking the data from the underlying files that PLEXOS points to and implementing them as Profiles in SAInt.
I also often use pySAInt to assist in building the model up iteratively in this way. I hope this helps! Let me know if you have any questions.
You are correct that this is not yet supported. However, we are working on a Resource Adequacy Plugin which would contain part of this functionality within. If you are interested, we could have a discussion to see if it would be useful to you to have access to this or something like it which could create random outage profiles based on a “Forced Outage %” (the first version of this tool would not support Maintenance Time %, but that could be added later on).
Hi Will Thank you for reply. I will surely follow your guidelines.
I am facing another problem. My plexos file contains data from HVDC, Small power producer firms, Geothermal, Generation public companies, Hybrid RE firms etc. Most of these are rental companies that sell energy to the Electricity generating authorities. Some properties of these categories are given like Max Capacity, Use of system charge, offer price etc. For PCM, in SAInt I worked with FGen, Wind, PV, Xgen, etc. Can you suggest where should I put these small power producer firms, HVDC and geothermal data in SAInt excel model?
It depends on how you need to model these various things. The “XGEN” object in SAInt - intentionally named “Generic Generator” - would be my recommended option. It is intended to be a generic object setting which easily allows modeling any generic power source with minimal constraints.
However, if what you are trying to model requires some fancier functionality, for example unit commitment, the ability to either consume or produce power, etc., you may need to leverage a different object type in the SAInt modeling ecosystem to achieve your end goal.
If you have any specific questions about things you need to model, I’d be happy to help!