I realised when I was reviewing this blog that we’d made an assumption that everyone coming to the site would know what the project was all about.\u00a0 This piece is intended to give an idea of what the project is, and how it came about.<\/p>\n
When Service Center was first implemented the requirements for\u00a0system funtionality were quite different to what we need today.\u00a0 The system was configured and then subsequently heavily customised to meet the needs as they were interpreted at the time.\u00a0 Over the past\u00a02 years, the system has been quite limiting in it’s ability to support our move towards a more controlled but transparent way of working.<\/p>\n
The real deciding factor came about when HP announced that our version of Service Center was out of support.\u00a0 We’d need to upgrade to remain with HP, and this meant re-working the customisations in a newer version of the product – a costly exercise.\u00a0 We decided that if we were to do that, we may as well seek to replace the system with one that would support our emerging processes and give us a platform on which to build for the future.<\/p>\n
We decided to plan to configure, not customise.\u00a0 That meant that we would need to be flexible about our processes, and bend the process to fit the solution wherever possible, not the other way around.\u00a0<\/p>\n
We went out to tender in August 2012, and with support from our group of stakeholders, procured the system we thought would represent best value for money as well as having the flexibility we need to allow us to move forward.<\/p>\n","protected":false},"excerpt":{"rendered":"
I realised when I was reviewing this blog that we’d made an assumption that everyone coming to the site would know what the project was all about.\u00a0 This piece is intended to give an idea of what the project is, … Continue reading