A vendor withdrawing a reporting system presents the “user” firm with a number of challenges. Typically, these include:

  • Forced project work and change activity
  • Unexpected additional costs
  • Delays to other planned project work while the reporting replacement project is undertaken
  • Requirements “freeze” within the business while migration from the out-going system to the new system is undertaken
  • Reporting review and selection process to be undertaken

The fact that the old system is being withdrawn, would suggest that the functionality and flexibility may have been lacking for some time. Thus, there may also be operational changes required within the business, where manual processes have been developed to support the legacy system. By selecting the very latest in reporting services and systems technology, many of the negative points noted above, can be minimised or removed. Specifically, selecting Reporting as a Service (RaaS) the replacement reporting system will:

  • Be implemented within 4-6 weeks, thus minimising the disruption to the business and clients
  • Automate the full end-to-end process, including any manual activities built up within the business
  • Integrate with the existing data feeds used to populate the old system, to minimise any data development work
  • Replicate the content and layout of the existing reports, making improvements where required
  • For the project to be managed externally and for no development work to be required internally
  • For nothing to be installed internally, the system to be hosted in the cloud and for access to be via a standard web browser
  • Turning a problem forced on you into an opportunity to improve

Andrew Sherlock

Opus Nebula