Simcenter STAR-CCM+ Why does the Initial SOC in Simcenter STAR-CCM+ BSM Battery Modelling not match the Setting from my Battery Design Studio .tbm file?
2022-07-22T08:44:01.000-0400
Simcenter STAR-CCM+
Simcenter STAR-CCM+ Virtual Reality
Teamcenter Share
Simcenter Cloud HPC
Simcenter STAR-CCM+ Viewer
Simcenter STAR-CCM+ Application Specific Solutions
Summary
Check whether Over Ride Cell Data is selected.
Details
In your Simcenter STAR-CCM+ batteries workflow you might find that you have a SOC setting from your Battery Design Studio .tbm file which is different from what is being reported in Simcenter STAR-CCM+.
For example, in the image below I have read in a tbm file where the initial SOC is reported in the Physical Cell Description as 100. 
However, on running the Simulation I see that the Volume Average SOC report is dropping from around 50%.
One reason could be that within BDS you can specify the SOC from within the Cell Voltage tab and this is the value that is read into Simcenter STAR-CCM+ at the Initial SOC shown above.
However, in the RCR Model Settings page you have an option to “Over Ride Cell Data” for the Initial SOC, shown in the image below.
If you have this option selected, then this value will be used for the modelling in STAR-CCM+ but the SOC value will not be updated. So, this may be why you are seeing a discrepancy between SOC in your Cell Description and what is being solved.
For example, in the image below I have read in a tbm file where the initial SOC is reported in the Physical Cell Description as 100.
However, on running the Simulation I see that the Volume Average SOC report is dropping from around 50%.
One reason could be that within BDS you can specify the SOC from within the Cell Voltage tab and this is the value that is read into Simcenter STAR-CCM+ at the Initial SOC shown above.
However, in the RCR Model Settings page you have an option to “Over Ride Cell Data” for the Initial SOC, shown in the image below.
If you have this option selected, then this value will be used for the modelling in STAR-CCM+ but the SOC value will not be updated. So, this may be why you are seeing a discrepancy between SOC in your Cell Description and what is being solved.