Model scope and methods - WITNESS: Difference between revisions
No edit summary |
(Page initialization) |
||
| Line 3: | Line 3: | ||
|DocumentationCategory=Model scope and methods | |DocumentationCategory=Model scope and methods | ||
}} | }} | ||
WITNESS stands for World environmental ImpacT aNd Economics ScenarioS | WITNESS stands for World environmental ImpacT aNd Economics ScenarioS. | ||
[[File:WITNESS Overview Small.png|thumb|WITNESS Overview Small]] | |||
It is a global Integrated Assessment Model (IAM) covering MacroEconomics, Energy, Materials, Natural resources, Environment, Population and Public Policies. | |||
The methodological approach to implementing WITNESS is to apply complex ''system of systems'' simulation techniques to IAM modelling. | |||
At the top level, a system of systems approach define high level systems and their interactions (which you can roughly see in the picture above). | |||
From an implementation point of view, they will define ''namespaces'' within which sub-system models will interact and exchange. | |||
An ''ontology'' is also defined to formalize all modules and parameter's names. | |||
In the main namespace, all interfaces exposed by each of the main systems are '''automatically coupled''' using the ontology ''semantic'' and multidisciplinary analysis (MDA) ''coupling templates''. | |||
Going down recursively refining each system is similar, you will define sub-namespaces for each sub-system you identify to further refine it if needed, | |||
and you will define your current systems interfaces to let them be automatically be coupled through the ontology in your current namespace. | |||
This methodology allow for easy refinement of models as the models interconnexions are prescriptive (expose interfaces in specific namespaces) | |||
but not descriptive (connections handling is automated an holistic within namespace). | |||
You can also decide to replace in some area the driver running multidisciplinary analysis (MDA), | |||
by a controller running multi-disciplinary optimization (MDO) of you want to orient the result vs an objective or want to respect specific constraints. | |||
For example in the basic WITNESS framework, an MDO controller is optimizing ventilation of available investment from Macro-economy to various Energy production techniques in Energy system, | |||
in order to maximize energy production while minimizing emissions under resources and materials contraints. | |||
Revision as of 09:15, 4 September 2023
Note: The documentation of WITNESS is 'in preparation' and is not yet 'published'!| Corresponding documentation | |
|---|---|
| Previous versions | |
| No previous version available | |
| Model information | |
| Model link | |
| Institution | Open-Source for Climate (OS-C), N/A, https://os-climate.org/transition-analysis/., Linux Foundation (LF), N/A, https://www.linuxfoundation.org/. |
| Solution concept | Systems dynamics based approach |
| Solution method | OptimizationSimulation-based optimization |
| Anticipation | |
WITNESS stands for World environmental ImpacT aNd Economics ScenarioS.
It is a global Integrated Assessment Model (IAM) covering MacroEconomics, Energy, Materials, Natural resources, Environment, Population and Public Policies. The methodological approach to implementing WITNESS is to apply complex system of systems simulation techniques to IAM modelling.
At the top level, a system of systems approach define high level systems and their interactions (which you can roughly see in the picture above). From an implementation point of view, they will define namespaces within which sub-system models will interact and exchange. An ontology is also defined to formalize all modules and parameter's names. In the main namespace, all interfaces exposed by each of the main systems are automatically coupled using the ontology semantic and multidisciplinary analysis (MDA) coupling templates.
Going down recursively refining each system is similar, you will define sub-namespaces for each sub-system you identify to further refine it if needed, and you will define your current systems interfaces to let them be automatically be coupled through the ontology in your current namespace.
This methodology allow for easy refinement of models as the models interconnexions are prescriptive (expose interfaces in specific namespaces) but not descriptive (connections handling is automated an holistic within namespace). You can also decide to replace in some area the driver running multidisciplinary analysis (MDA), by a controller running multi-disciplinary optimization (MDO) of you want to orient the result vs an objective or want to respect specific constraints. For example in the basic WITNESS framework, an MDO controller is optimizing ventilation of available investment from Macro-economy to various Energy production techniques in Energy system, in order to maximize energy production while minimizing emissions under resources and materials contraints.