Cloud Computing - Implementation Process for SaaS - How Different from On-Premise?

We looked at how the selection process needs to be tweaked to choose a cloud SaaS (Software as a Service) solution, compared to traditional on-premise software.

Here is a quick summary of a typical on-premise implementation process for a mid-market solution, and how this needs to be changed for SaaS. The same principles also apply to small and corporate systems, simply adjusting the level of work required.

Actually very little changes for a system of equivalent scope and complexity. For example it is still important to get the configuration right, to get reporting right, and to make sure users are sufficiently familiar with how to use the system.

In addition to overall project management and change management, the key steps are typically as follows:

.	STEP	CHANGE FOR SaaS
1	Project Initiation & Planning	No difference
2	Software Installation	Software already available online
3	Physical Design Preparation	Only if integration
4	Pilot/Prototype Design & Build e.g. Expand Reporting Requirements, Design Configuration Options, etc	Access Security & Disaster Recovery
5	Build Pilot System	No difference (except it's online)
6	Test The Pilot System	No difference
7	End-User Training	No difference
8	Build Live System	No difference
9	Data Conversion	No difference
10	Live Running	No difference
11	Continue To Develop Reports	No difference
12	Post-Implementation Review (After 3-6 Months) Carry Out Remedial Action	No difference

In practice, for larger systems the implementation may be phased, in which case much of the process is repeated for each phase.

If you would like to know what is involved in each stage, such as developing workflow and suitable security, or how the process needs to be adapted to apply to your specific situation, do contact me on +44(0)7836 774439, or by email at challisc @ camwells.co.uk (please remove gaps first). I look forward to talking to you.

Or do feel free to leave a comment ...