A web-service framework for the water evaluation and planning system

Mostafa D. Fard, Hessam Sarjoughian

Research output: Chapter in Book/Report/Conference proceedingConference contribution

3 Scopus citations


For systems-of-systems, the use of different modeling methods is important not only because each system can be described more correctly, but also benefit from tools that are in use by different communities. Using an opaque or closed source-code tool with others, however, is challenging. Consequently, to facilitate the development of simulations for systems-of-systems it is useful to cast closed-source models in a flexible component-based framework. Using this concept, a RESTful web service framework is developed for the Water Evaluation And Planning (WEAP) software system. The WEAP RESTful framework has a suite of model components for all the model entities defined in the WEAP system. An example water system model shows the computational cost for the web-service framework is negligible. Casting the model entities to components can play a key role in using the WEAP system with other modeling frameworks useful for simulating the complexities of the Food-Energy-Water systems.

Original languageEnglish (US)
Title of host publication2019 Spring Simulation Conference, SpringSim 2019
PublisherInstitute of Electrical and Electronics Engineers Inc.
ISBN (Electronic)9781510883888
StatePublished - Apr 2019
Event2019 Spring Simulation Conference, SpringSim 2019 - Tucson, United States
Duration: Apr 29 2019May 2 2019

Publication series

Name2019 Spring Simulation Conference, SpringSim 2019


Conference2019 Spring Simulation Conference, SpringSim 2019
Country/TerritoryUnited States


  • Component-based modeling
  • MDA
  • RESTful services
  • Systems-of-systems
  • WEAP

ASJC Scopus subject areas

  • Control and Systems Engineering
  • Control and Optimization
  • Modeling and Simulation


Dive into the research topics of 'A web-service framework for the water evaluation and planning system'. Together they form a unique fingerprint.

Cite this