Changing the OpenMI Standard has major implications for both OpenMI developers and users. Unfortunately, it is impossible to make such changes backward compatible. Consequently, when a new OpenMI Standard is released, all model providers must upgrade their models to stay compliant with the latest OpenMI version.
The pace at which this happens varies from model provider to model provider, since many model providers only make new releases of their software products on a six month or yearly basis. Hence, after an OpenMI Standard release it can often take a year before the bulk of compliant models are upgraded to the new version. This has implication for the OpenMI users, as they may find that the models they want to use for linked configurations are not compliant to the same OpenMI versions. For this reason, as of version 1.4, a very conservative release strategy for the OpenMI standard has been adopted. A new OpenMI standard release is not expected until the release of OpenMI standard version 2. Release of OpenMI Standard version 2 is planned to take place in December 2009.
The models listed below are compliant to OpenMI standard versions prior to version 1.4, and as such not regarded as formally OpenMI compliant. However, since upgrading from previous versions to version 1.4 is a relatively small task for the software providers, we expect many of these models to become OpenMI 1.4 compliant when new versions of the models are released. Actually, a few of them have already been migrated to 1.4, but the provider did not yet submit an xml-file with het OpenMI compliancy info, so these models can not be called formally formally OpenMI compliant.
So, if you are interested in using some of these models as OpenMI compliant component please contact the software provider and ask when such upgrade is expected.
| Company * | Compliant Models & Components | .NET | JAVA | General description/ Compliance |
|---|---|---|---|---|
| Alterra | Capri | x | Agricultural policy impact model | |
| FSSIM | x | Bio-economic model | ||
| Apes | x | Biophysical model | ||
| MetaSwap en Simgro | x | Hydrological model | ||
| BAW | GEI Wrapper | x | Access to propriatary data for Delft 3D flow | |
| CEH | Classic | x | Hydrological model | |
| CRWR | ArcHydro | x | Hydrological model | |
| Delft Hydraulics Software | Delft3D | x | 2D/3D flow model | |
| DHI software | MIKE 11 | x | Hydraulic model | |
| MIKE SHE | x | Hydrological model | ||
| MIKE URBAN | x | Urban drainage model | ||
| Hydrologic Engineering Center | HEC-RAS | x | Hydraulic model | |
| Utrecht University | PCRaster | x | Data interface component | |
| RIZA | DM | x | Surface water transport model component | |
| Mozart | x | Unsaturated zone model component | ||
| Agricom | x | Agricultural model | ||
| NwSim | x | 1D network model | ||
| DemNat | x | Ecohydrological model | ||
| DistConn | x | Water distribution rules component | ||
| Wallingford Software | SULIS | x | 3D lake and estuary model | |
| Schlumberger Water Services | Visual Modflow | x | Groundwater model | |
| University of Liege | PEGASE | x | River quality model | |
| University of Thessaly | UTHBAL | x | Hydrological model | |
| WRc Plc | STOAT | x | Wastewater treatment model |
* the underllined parts have hyperlinks that produce the companies' websites


