VLEEM Software project Benoit Frachet for ENERDATA s.a. Slides available on http://www.vleem.org

The structure of VLEEM SOFTWARE USER CHOICE TASES Module ENERDATA Module Other Module Transcription Module TASES Module ENERDATA Module Other Module Input Files Simulation Specific Output file VLEEM Simulation Module

The hierarchy of VLEEM SOFTWARE Each module contains specifics classes Only one transcription module available To simplify software development all part of VLEEM software is independent, but must be adaptable! Output files can be used by other modules The transcription module allows a sharing data process, to each existing components. It converts output text file in a good input format. The output files must be in a normalize format to be converted by the transcription module.

VLEEM –Energy services – Model architecture Demography Education - information Activity Production, affluence Time-budgets Energy services – useful energy matrix « Food » « Transportation» « Shelter » « Other production» « Self-accomplishment »

Concept of the demand model SOFTWARE First Screen User’s choice C1: New simulation (new database) C2: Loading simulation (editing database) C1 C2 OR Validation Database Integrity respected? Simulation module loading* * Module access will be enable in function of the database state Data editing Text format Grant new access to simulation module? If no exit If exit Validation Module end or software exit Module end or software exit Validation Editing database

The hierarchy of the demand model SOFTWARE 1 Simulation module = 1 Process class Multiple database architecture This type of hierarchy permits a great division of the different process, and allows a best maintenance process. High simulation modules interconnections To maintain a high fidelity data processing and storage, multiple text files will be available All simulation modules can “communicate” with other to share data and permit the final processing

THE END