Damien Ryan-Green to Tony, Helen.McCluskey
show details 7:44 PM (2 minutes ago)
Hi Helen
Thanks for that, see notes below in response:
Part 1 of 2: online rostering
Look fwd to whatever Paul and Cathie come up with, and do let them know, if you like, we have been mindful of Kronos, and modelled the resource to:
(a) be primarily a significant short to medium (12 to 18 mths) pens, overtime and agency and supernumerary time efficiency, which would from then on be achieved via Kronos picking up that baton;
(b) be easily decommissioned at such time as Kronos starts meeting your availability needs; and
(c) present a future opportunity and an option, with features that complement and do not duplicate Kronos features, just in case circumstances become such that you need/want to continue on after the 12 to 18 mths or so
Part 2 of 2: Workcover
Re Workcover, am meeting Tony tomorrow (he has worked with most of the components I haven't, and vice versa).
The key to this project would be that we would not be coding from scratch (which would take an inordinately large amount of time and expense, and could be taken on by any number of developers without waiver), but rather, hosting at EMSOnline of your specific functionality on a "pre-coded platform with ongoing shared support for all tools on the platform" (I'll refere to this as "pre-code" for convenience).
In other words, we've already done most of the work / most of the work is behind the scenes on behalf of mutiple tools.
The method for pricing, then, is one portion pre-coded, and one portion new coding for your specific functionality. As a guide:
- For a single screen tool with many users (such as a proposed-in-the-near-future fully networked client financial plan, which you're familiar with) this can mean close to zero hrs coding and specific maintenance for that tool, and approx the equivalent of one hr @ $120 per week pre-code for as long as your old team (and users statewide) use that tool
- For a complex tool with many users statewide (such as a new OHS tool currently being proposed fopr EMSOnline), the split between pre-code and code will be close to the equiv. of 6.5 hrs per week for pre-code, and 10 hrs per week for, say, 25 weeks for new code
- Your tool sits somewhere in between, is our estimate: reasonably complex, but not many users. But the DHS-specific pre-code at EMSOnline makes it possible to meet a reasonably short timelines, whereas if you had plenty of time, you could put it out as a "from scratch" development, and there would be quite a few IT companies that could make quite a good fist of the job
Let me know if any queries, but in any case, propose a timeline for that one of tomorrow c.o.b.
And I'm on mobile (almost) anytime!
Damien
PS Tony,