|
|
# Description
|
|
|
this module uses all this information and tries to create an optimal schedule within the bounds of all the requirements and constraints from the other modules. Our current idea is, that it makes use of genetic algorithms in order to find the best schedule.
|
|
|
|
|
|

|
|
|
|
|
|
# Input
|
|
|
From [optimisation configuration module](optimisation-configuration):
|
|
|
* what are the optimisation goals?
|
|
|
* In which time window should this module schedule?
|
|
|
* Are there any other additional requirements (like deadlines)
|
|
|
|
|
|
From [production infrastructure module](production-infrastructure):
|
|
|
* What are the tasks that have to be scheduled?
|
|
|
* to which entities can they be scheduled?
|
|
|
* what is physically possible and what's not?
|
|
|
|
|
|
From [energy context module](energy-context):
|
|
|
* how expensive will this be?
|
|
|
* is this possible with the prognosed available energy?
|
|
|
|
|
|
# Functionality
|
|
|
It uses a genetic algorithm to assign each required task to a machine, a time and a task-mode, thus creating a schedule. it satifies, if possible, each given requirement (either physical or user-made).
|
|
|
|
|
|
# Output
|
|
|
To platform:
|
|
|
* the best found schedule
|
|
|
* maybe alternative found schedules
|
|
|
* values like price, energy consumption and makespan of each schedule
|
|
|
* the score of each schedule |
|
|
\ No newline at end of file |