STRATEGIC aims to help public sector with cloud adoption, and during the piloting period, we had three different public bodies, dissimilar size and level of cloud adoption. All pilots tried to increase cloud adoption and extend their portfolio of cloud services that use internally or provide to their citizens. These are some of the main findings from their experience.

When considering public administrations of medium-size, it is preferable at least when possible, to draft a clear list of complete requirements both in term of material resources and tasks to be accomplished given in the least possible chunks instead of many little tasks. This is easily explained by considering that each task to be accomplished follows a first-in-first-out ticket queue processing by PA personnel. Also, regarding the material resources to acquire either a tender or some kind of internal agreement needs to be made and that requires time.

We also found that medium-large cities seem to have skilled personnel to carry on the required tasks with the necessary professionalism in order to deploy software or even in some cases to prepare an IaaS environment.

The decision of the IaaS to be used is an important step for public bodies, regardless the size. Most public bodies preferred to use a private cloud for their services.

In some countries finding cloud hosting providers is not an easy task, and the choices for public bodies interested to store their data with location based restrictions can be very limited or non-existent. In one of our pilot cases, using a public cloud was preferred option but due to regulation rules that forced the storage of data to be within the country, a private cloud installation was created and used.

For public bodies making a tender is usually needed for the purchasing of hardware. This can cause some delays and difficulties that have to be resolved in order not to affect the cloud adoption. So, a dillema regarding the options for the IaaS implementation for a public administration entity can be created, with the following options representing the findings of one of our pilots:

  1. Purchassing own physical machines, install IaaS and maintaining it internally – in own premises
  2. Purchassing own physical machines, install IaaS and maintaining it in a provider’s premises
  3. Renting VMs and install OpenStack and applications
  4. Renting VMs with some cloud infrastructure and install applications
  5. Renting physical machines and install OpenStack and applications

For our pilot case, the opinion was that the options 2 and 5 were the most acceptabe. A problem is that it is that hosting providers don’t always offer cloud infrastructure or physical machines.

Finally we found that the usage of the STRATEGIC Service Store on top of a private cloud infastructure provided a positive experience, as public bodies found that there were many applications that could choose, easily adapt and deploy to their premises. A recommendation of one of our pilots is is that STRATEGIC Service Store should be a mandatory part of any cloud project for the public administration body no matter if this is implemented as the private, public or hybrid cloud. In other words, the Cloud Application Management solution that is offered by STRATEGIC provides many advantages (security, easy replication, etc.) that should be used in any cloud based project for the public administration body.