Well it's a good 5-6 months since I created that script, and it looks as if the project to implement this new software has been delayed until March next year!
Quite frankly, it's difficult to guess at what the politics are.
The consultancy, who is not the software vendor, may well not totally trust the software.
Someone in the higher management structure is keen to be one of the first organisations to successfully implement this software .... in order to impress /their/ (government) client ... or to attract a bonus funding reward ... maybe!
And somewhere along the line, it had been decided, between the consultancy and software client, that we had to deliver something before the consultancy did!! [and they still haven't, as far as I know!!]
The chain of relationships is far from simple to say the least!
- Software consultancy
- Government body i) (End user) and
- Government body ii) (Information Management)
Inevitably, with such an extended relationship between software vendor and end user, is it any surprise that focus can be pulled in a number of directions. Ideally, both government bodies will have elected a single representative, equally responsive to both, to simplify that relationship chain.
However, my experience of governmental bodies is that they are very reluctant to relinquish control, if they can possibly help it!