SDIP Learning Entry Point
Explore the SmILES methodology
Explore and learn about the SmILES methodology by examining the overall SmILES workflow for modelling and analyzing complex energy systems depicted in the graphics on the right side by clicking on the different phases within the graphics, which will navigate you to a more detailed description of tasks associated with a certain phase.
Alternatively, you can choose one of the links below the graphics to directly go to a more detailed description of a phase or one of the workflow tasks within a phase.
For a quick overview about motivation and the overall methodology, have a look at the webinars under https://www.ecria-smiles.eu/webinars.
SDIP 1 level workflow image
SDIP 1 level workflow
Overview and description of phases
Phase 1 is called “Specification and Preparation Phase” and contains all tasks of a complex system modelling and analysis project which have to be logically done before concrete model implementation or execution. Typically, this involves writing specification documents which define the requirements and contracts concrete implementation objects (e.g. models, test data) have to fulfil so that they show a predefined, e.g. specified, behavior when simulations get actually executed.
Phase 2 is called “Implementation Phase” and contains tasks where e.g. component and system models will be implemented according to the given specifications, or data files containing input data or configuration parameters are compiled into dedicated formats so that they can be read by a concrete simulation setup when executing models in the “Experimentation and Analysis Phase”.
The “Experimentation and Analysis Phase” (Phase 3) groups all tasks which are related to actually performing system simulations by concretely executing system models with corresponding test data according to a test case specification, perform optimizations and analyzing the results.
While the phases logically separate e.g. specification tasks from implementation tasks, the workflow concept doesn’t prohibit performing tasks in a different order. E.g. only performing some specification tasks before an implementation task and iteratively switch between Phase 1 and Phase 2 tasks. Also, dependent on the actual project performed, the type and requirements of the project context, not all tasks of the workflow need necessarily be performed. Maybe in simple cases, even the forms for aquiring data or specification information can be filled out only partially. The only requirement is that tasks which produce an input for a certain task have to be finished before a task depending on these inputs can be performed completely. And those input tasks should provide all information necessary for completing the next step.
For exploring the different tasks of a phase, just click on the phase in the graphics.