top of page


The HelioStor Governance Model ensures projects maintain a consistently high level of quality throughout delivery . Two virtual governance teams are responsible for monitoring the use and continued development of processes and methodologies, The Project Governance Team and Technical Design Authority. 

Project Governance ensures the planning, management, controls and reporting are consistent with the appropriate HelioStor and partner standards.

Technical Design Authority ensures the HelioStor and partner methodologies and best practices are consistently followed.

In addition, both governance teams ensure stakeholders and Project Teams for every project embed and understand our quality requirements.

We pride ourselves on the quality of our delivery. The items below illustrate just some of the components we draw upon to plan, track, manage and report on our services. The examples particularly reflect our Migration services, but apply to all our engagements as required

HelioStor project gov v5.jpg
Project Management.png

Project Management

We follow the Channel or Vendor standards for project management and bring our own artefacts to enhance where needed and requested

We maintain Risk, Assumptions, Issues and Dependencies logs

We create a plan appropriate with the size, complexity and duration of the engagement

We agree roles in advance to ensure sponsorship and leadership are clear both within the end client and the Channel and/or Vendor teams

Project Reporting.png

Project Reporting

We pride ourselves on clear and useful reporting

We use graphs, charts and tables to show progress and produce material suitable for technical and business stakeholders

We brand all reporting in line with our Channel, Vendor and end client requirements

Migration Scheduling.png

Migration Scheduling

We have a large established set of artefacts to control the resourcing and delivery of migration projects

These include three primary data sources containing the Master Migration Schedule (containing technical meta data for specific migration events), Infrastructure map (populated from customer’s environment data and tailored to fit) and Migration Rota (to manage resource assignment)

Passports and runbooks.png
Change Management.png

Change Management

The Change Management function within the end client is the guardian of environment stability

We therefore take the necessary time to understand their processes and requirements at the start of the migration project to ensure smooth scheduling and successful delivery

Data Gathering.png

Data Gathering

We work closely with the end client’s technical teams to gather the appropriate level of data required for successful delivery

This is an iterative process as full information is rarely completely readily available

We baseline the gathered data at an agreed point early in the engagement, in order to give clarity of scope and measure progress and success

Passports & Runbooks

We use technical passports for each server or cluster whose data is being migrated

These record all that is required for a successful migration

Runbooks are our defined methods for different types of migration and ensure repeatability and are mutually agreed with the teams involved

Installation Scheduling.png

Installation Scheduling

We have a central coordination point for all engineering expertise for installations

This ensures the right engineer is deployed at the right time, to the right place and with the right pre-requisites

bottom of page