The Doctor Rostering Problem - Asser Fahrenholz
The Doctor Rostering Problem - Asser Fahrenholz
The Doctor Rostering Problem - Asser Fahrenholz
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
Chapter 6. <strong>The</strong> DRP Program 40<br />
Figure 6.9: <strong>The</strong> main window w. generated schedule<br />
6.2.1 Measuring the quality of the solution<br />
<strong>The</strong> status bar in the bottom of the application window shows various solution mea-<br />
surements:<br />
Z(S) the heuristic value of the solution.<br />
V(S) the number of hard constraint violations.<br />
Cons is a measurement of how constrained the problem is. If the problem is 100%<br />
constrained, no doctors can be assigned to any shifts without breaking a hard<br />
constraint. It is an average of how many doctors violate one or more rules when<br />
assigned to a shift, over all shifts. Importing shifts and adding RDO to the schedule<br />
are factors that raises this measurement.<br />
6.3 End user feedback<br />
Much like Dias et al. [7], who also develops a user interface, the end user of the software<br />
program described in this chapter, gains the most in time spent creating the schedule.<br />
<strong>The</strong> gathering of information from the workforce is still a tedious process, though much<br />
improved through the import-function, and the schedule is still inspected manually after<br />
it has been created by the software. It is estimated that the total time required to<br />
produce a schedule, going from 5-10 hours, will be around 0.5 hours. Should previous