this is for holding javascript data
Andreas Luedeke edited sectionPROPOSED_SCHE.tex
about 9 years ago
Commit id: 054bef2d6eb519c1632086cf9907ee06337d02e8
deletions | additions
diff --git a/sectionPROPOSED_SCHE.tex b/sectionPROPOSED_SCHE.tex
index c93845a..ee8a28e 100644
--- a/sectionPROPOSED_SCHE.tex
+++ b/sectionPROPOSED_SCHE.tex
...
This rule takes care that all beam outages are visible events in the statistics: some facilities were not counting outages of several days for the beam availability, because they re-scheduled all users to newly allocated time and declared the downtime to be a shutdown.
This is very good for the users: better to be re-scheduled than losing all beam time.
But is prevents the comparison to facilities that are handling this differently.
The following example will illustrate the proposed scheduling:
A facility has 4000 hours {\em Scheduled User Experiment Time} and no {\em Scheduled User Reserve Time}. A vacuum leak occurred in the storage ring and caused a 7 day beam outage. The management decides to declare these 7 days to be shutdown and to shorten the following shutdown in two weeks time by seven days to re-schedule all users.
According to our proposal this will be accounted for as a seven day or 168 hours ``No-beam'' event.
The extra seven days are {\em Spontaneous User Time}. The total user time will be 4168 hours.
If the shortened shutdown would be more than one month into the future, then the extra seven days would be accounted as {\em Scheduled User Reserve Time} instead, otherwise there would be no difference.