The model integration framework is developed to link models which are developed using different programming language and which could be located on different location. It is developed using web service based approach - models are wrapped with web services and the integration framework handles the synchronization, semantic mediation, and data conversion functionalities.

The integration framework organizes its content in different menus. Here we present brief description of the main menus of the system.

1.Wrapped Models Menu

This menu consists of models wrapped with web services. Models developed using GAMS, NetLogo, Java, and C++ are presented as web service. Users can access this web service based models as stand-alone systems. A user can also provide inputs and run simulations.

2. Integration Menu

The integration menu consists of interfaces that link the web service based models.

  • Sensitivity of integration submenu: it links stand-alone predator and prey models so as to experiment the effect of integration methods and time steps used in linking models. Further detail on the experiments we performed can be found on our paper Exploring temporal and functional synchronization in integrating models: A sensitivity analysis.
  • EXIOMOD-GCAM submenu: it links EXIOMOD model with GCAM. The user can set inputs, run simulation, display and download output.
  • EXIOMOD-AbEMM submenu: it links EXIOMOD model with the AbEMM model.
  • Airports Vs Weather submenu: this interface links the Airports web service with Global Weather web service. The main objective of this interface is to experiment on our semantic mediation module. It demonstrates semantic mediation of text-based input-output data using word overlapping algorithm and also using lexical database.

3. Runtime Applications Menu

This menu consists of two interfaces that focus on runtime access and integration of models.

  • Runtime Access to models interface which provides a user interface to access web service based models during runtime. The user is expected to provide the URL of the web service, then the system will explore the existing methods together with the corresponding input and output variables.
  • Runtime integration interface is designed to link two web service based models during run time. If the output of the first model can be used as input for the second model then the user can define the data exchange pattern and can link the two models. However, if data mediation is required the user can develop the data mediation module as web service and can use the data mediation module in linking the models.

4. Semantics Menu

This menu consists of forms that demonstrate how freely available ontology can be used in semantic mediation, and different semantic matching algorithms in semantic mediation.

  • Units Ontology: we used this interface to demonstrate how we can minimize hard-coding in semantic mediation by using an existing ontology. The QUDT Ontology is freely available ontology developed to describe Quantities, Units, Dimensions, and Data Types. The units ontology is used to perform automatic unit conversion computations in integrating models.
  • Semantic matching interfaces are used to experiment the effect of lexical databases in semantic mediation process of integration. In these interfaces we used in-house developed semantic matching algorithm and freely available lexicon database - WordNet.
  • Matching CSDMS metadata: in this interface we demonstrated how semantic mediation can be applied in searching for models which could provide data to our models. The semantic mediation techniques are applied on CSDMS Standardized Model Metadata.

 The model integration framework can be accessed using the following link