Corrosion FAQ's

When standard database predicts precipitation of Fe(III), Zn(II), Cu(II) as Fe(OH)3, Zn(OH)2 and Cu(OH)2 respectively, Inclusion of the Corrosion database produces the more stable hematite Fe2O3, goethite FeO(OH), ZnO and CuO solids.

When you include a corrosion data bank, surely it predicts more stable oxides. That is because when a corrosion databank is included, the solver automatically assumes a surface rather than a simple solid precipitation. And then the speciation changes. The hydroxides are still considered a part of the system, but the possibility of oxides forming increases because there will be corroding surface involved in that system. Thus the stable oxide predictions.

When to use Corrosion and Geochemical databank

When you use OLI software, there are certain calculations that need additional databanks to be included by users for specific predictions. Geochemical i.e GEMSE and Corrosion, i.e. CRMSE are one of them.

File:2014-12-11 12-31-49.png

There is a fine difference between scenarios which governs the fact that the databanks should be included or not. One of the major factor controlling it is time. Would a particular species be formed under specific conditions or it could only be formed over a significant period of time.

For GeoChem the controlling parameter is only time. If a component will only form over a geochemical scale then the user may include the databank to predict the formation of the component in that particular process simulation. Please remember that under ordinary circumstances this component/ solid would not be a part of that process and would not be predicted as a part of the system for that process via simulation.

A good example for this is the SiO2 system. OLI recently worked on this system. Now SiO2 and its two forms -> SiO2 ( Amorphous)

                          -> SiO2 ( Quartz)