Scaling 7.0

See example above:

100% in a 1-hour raster

if Convert 0 lines? is not selected

100% in a 1-hour raster

if Convert 0 lines? is selected

50% in a 1-hour raster

no matter if Convert 0 lines? is selected or not

Proportional time*value

Explanation: Scaling interval = 2 minutes (120 seconds) determines the resulting proportion

row 1: half of the interval met, therefore 60/120*27=13.5

rows 2 and 3: interval fully met, therefore 120/120*27=27

row 4: half of the interval met, therefore 60/120*27=13.5

Proportional time

Explanation: Duration of the period in the whole data set (6 minutes = 360 seconds) determines the resulting proportion

row 1: 16:13 – 16:14 = 60 seconds, therefore 60/360*27= 4.5

row 2: 16:14 – 16:16 = 120 seconds, therefore 120/360*27= 9

row 3: 16:16 – 16:18 = 120 seconds, therefore 120/360*27= 9

row 4: 16:18 – 16:19 = 60 seconds, therefore 60/360*27 = 4.5

There are surprisingly high requirement peaks! – How can I check if they are plausible?

The following steps can help understand these peaks:

1) Check if the result is due to the scaling method:

• Do the peaks disappear, if a shorter interval is selected?
• Do they disappear, if 100% is selected (to exclude rounding)?

2) Check if the peak is due to a few individual values:

• e.g. check with Pivot table time x weekdays 2.0 if it appears in different years/months
• e.g. check with Pivot table time x weekdays 2.0 if the maximum values are plausible.

3) Check the underlying data.

• e.g. with Vorlagenordner F... Auswertung für einen 11U Knoten: Start, Ende, Lage template (old Wiki) for check, which time periods reach into a specific interval, check, whether patterns can be found

In case the peaks are really errors, eliminate the faulty data records or time intervals e.g. with TIS:Zeitbereichsfilter (old Wiki) .

There are only points in time. What shall I do?

Use "Calculation" to add e.g. 30 minutes to create a virtual interval and then analyse with >>Count only start time<<. “Normal scaling” would not make sense in this case.

The calculated staffing level seems incorrect

This may be due to the interval selected.

If in doubt, try using shorter intervals
Example:

15 minute scaling can produce strange results for intervals of 10 minutes or less: in case of 50% overlapping e.g.

• 00:00 – 00:10 --> staffing level = 1 in 00:00 – 00:15
• 00:20 – 00:30 --> staffing level = 1 in 00:15 – 00:30
• BUT: 00:40 – 00:50 --> staffing level = 0 in 00:30 – 00:40, 00:40 – 00:50, 00:50 – 00:60
• in case of 100% overlapping --> staffing level = 0