End user expectations

[kaituna]

Hi all,

I'm just thinking of the package from my perspective as a probable end-user, and the type of things I would need to be able to do. I think in an ideal world I would be able to set some initial parameters (e.g. queue size, target wait and current compliance) then feed an event level extract of additions and removals into the package (structured in a hierarchical manner if possible). From this I would need to be able to determine the following:

• summary of average demand/activity/queue size/load/pressure/variability/compliance
• plot timeseries of demand/activity/queue size/load/pressure/compliance as necessary
• run scenarios that effectively solve for the unknown parameters. For example, if I set a target compliance of x% within 12 weeks, what does my relief capacity need to be. Alternatively, if I set a target compliance of x% but have fixed additional capacity, how long will it take to get to a stable queue size?
• output the scenario modelling demonstrating how queue size/performance is likely to change over time.
• run a sensitivity analysis that illustrates the impact of parameter changes over a range (e.g. different levels of extra capacity)
• generate a 'trade-off' curve that shows how allocation of fixed capacity to different priority groups impacts on performance of each

I'm not sure how congruent these expectations are with the project scope, and perhaps some of these asks are either further down the development line or achieved through use of the package in a wider project rather than being native to it.

Does anybody have any thoughts about what we we need to be giving to the end-user?

[ThomUK]

Thanks for getting this conversation started...