deletions | additions       diff --git a/subsectionBeamunrela.tex b/subsectionBeamunrela.tex  index 59f579f..d943cb1 100644  --- a/subsectionBeamunrela.tex  +++ b/subsectionBeamunrela.tex 
...
\subsection{Beam-unrelated}   Some failures do not affect the beam, but they do affectthe  user experiments. If For instance if  the beam is stored and all beam parameters are within the desired limits, there still can be problems that preventmost  users from running any experiments. Infrastructure outages like massive control system and IT-infrastructure failures or  photon shutter interlocks can lead to those these  situations. There cannot be a simple rule to calculate the start and stop for all failures of this type;   but they should be recorded if they have an influence on a significant number of the experiments.  Currently beam unrelated incidences are considered to be ``downtime'' at some facilities,   if they prevent all beamline beamlines  to continue their measurements. This is the case at ALBA, Elettra and the SLS.  Other facilitiesdo  neglect those these  types of failures for their downtime calculation, as long as the electron beam was not affected, for example PETRA III.  At most facilities these failures are evaluated on a case by case basis:  for example an interlock of all photon shutter would clearly be considered ``downtime'',  
...
\subsection{Short-user-time}  Many facilities have a cut off for a minimal time to store the beam.   For example if less than one hour is recorded  between two beam tripsthen  the time in-between is counted as downtime.   This can be defined as an extra failure mode: ``short-user-time''.   The limit of what time is too short for user experiments depends on the time   the facility needs to get into thermal equilibrium and   on thetypical  length ofa  measurement time  at an experiment. Each facility should define this cutoff time limit  $ T_{\hbox{short-user-time}}$; it may depend on the operation mode.