databit" just pointed it out. this formula is the base for the calculation, doesn't matter if used for custom-view or statistics from the database.
screwing out of a overworked, dead brain:
In CV build a table with
tab_tg = TrunkGroup_Halfhour.TG-Number
tab_hh = TrunkGroup_HalfHour.halfhour_relative/_absolute (as you like)
tab_dur_inc = TrunkGroup_HalfHour.dur_inc
tab_dur_out = TrunkGroup_HalfHour.dur_out
tab_num_trk = - TrunkGroup.NumTrunks
and some calculated coloumns:
usage_inc=
tab_dur_inc / (tab_num_trk * 1800) * 100
usage_out=
tab_dur_out / (tab_num_trk * 1800) * 100
usage_all=
(tab_dur_inc+tab_dur_out )/(tab_num_trk * 1800) * 100
Then make a line-graph, x-axis is the intervall, use the usage_inc/_out/_all for the graphs (y scale 100) and then you'll get a better feeling how your trunks are beeing used...
Adding TrunkGroup_HalfHour.Calls_Inc / _Out to the table and using that fields in another graph (because of the different scaling) you'll see how many calls will saturate your capacities.
Not yet done: With an additional graph showing agentgroup-/ application-statistics per half-hour (answered/abandoned calls, number of agents) you'll get a pretty good picture about what happened last night or what you may expect during the next intervall.
It's long time ago that I've been builing the canvas, perhaps I missed some details. Please ask and I'll have look at it next monday.
bye,
chris