Stakeholders Form

This form advises us of the major contacts withing the customer organisation who will be responsible managing the deployment project and providing the necessary information in a timely manner

Pre-Install Form

CyTrack’s solutions have some system requirements depending on the software modules the customer has purchased
We require the customer to acknowledge the various minimum requirement are met and also to provide us with the necessary information at the beginning of the deployment to ensure a smooth and contiguous installation

Installation

Our standard deployment fees include the following. If the customer requirements exceed these then additional fees will apply

Number of Queues
Recorded announcements – format
CyDesk web (not on every pC?)
Number of reports included
Dashboards included
CyChat inclusions

Training

CyTrack’s method of training is to ‘train the trainer’ using TeamViewer.

The customer will nominate a ‘superuser’ who will receive full hands on training in all areas of the software modules purchased, including the admin tasks. This person is then responsible for training the other users in the software they will be using in their roles

What the training will cover?

Testing

What we test

UAT?

Go Live

The Go-Live stage is an important part of the process and is initiated by the Go-Live form which must be signed by the customer and returned to CyTrack before the site can be activated to be working live. If certain commercial conditions are attached to the project stage of Go Live these must be fulfilled before the approval is given for Go Live.
If for any reason the customer refuses or we cannot obtain the Go-Live form CyTrack will assess the date the system has gone live

Deployment Warranty Period

We provide a period of time called the deployment warranty period whereupon our deployment team will address certain accepted issues or change requests raised by the customer without this being deemed chargeable and comprising part of the deployment process.

This deployment warranty period will extend for 21 days from the go-live date.

Deployment Project Completion

The Deployment Completion Form is issued to the customer one week after Go Live has occurred, (for avoidance of doubt - not when the Go Live Form is signed but when the system has been taken live).

The Deployment Project is completed when the Deployment Completion Form is signed by the customer. In certain cases, additional documentation may be attached to address specific needs or contractual aspects of the project, so that their completion may be demonstrated and signed as completed off by the client.

If there are certain issues that remain to be addressed, The Deployment Completion Form provides a section for the customer to enter a list of those issues outstanding (each one of those must have a support ticket issued for reference) and these will be processed and addressed by the coordination of the PM and the support team.

If the customer does not return requests for the Deployment Completion Form for any reason, then the date calculated as 21 days from the Go-Live date is taken as the acceptance of the project completion. In this case CyTrack will deem the project has been completed and will notify the customer of this action.

Once Deployment Completion has been reached then all support tickets will become Billable from this point, excluding IRS issues if the customer has purchased  IRS support.

Issue Resolution Service

 * Refer to Professional Services Brochure

Support Tickets

Registering on support portal

Service Vouchers

MACS

After Hours work

Upgrades

Making the Most of Your Investment

Issue Resolution Service Renewal Process

What Next? The Insider Blog

The CyTrack Insider Blog is aimed at all our customers who are on our Software Care Service (which is included as part of the Issue Resolution Service).  The purpose of the Blog is to deliver high level news and information about our version release communicated directly from our engineering team.  The blog posts provide you the version numbering of upcoming releases and where exactly they are at in progress on a fortnightly basis.    

Our aim is that our customers will be better informed on the progress and content of upcoming new releases and can also follow particular resolutions to issues or new feature releases that are important to them.  The Blog also provides the means for you to post questions and comments and our engineering team will reply to your query directly. 

One important area to explain is how our release number system works when we provide you a release version that is slated to include items of interest to you.   Releases are numbered based on the month the work is defined and planned - not when its released !  This is because often when starting work we can’t be sure of the exact time it may take to complete and when communicating a release version for customers to track we cant keep changing its release name as dates change as that would be confusing for everyone.   

The release numbering system is year-number-version - so for example 20-1.1 release.  This is a version that has commenced in year 2020, is our first release of the year so '1' and the first point release of the month so '.1', as we may sometimes have more than one release in a single month.   Each cycle increments the point release, so for example release 20-1.2 would be a minor second cycle of the 20-1.1 version released before we could bring the next major version being 20-2.1.   

Our Engineering and Leadership team is constantly reviewing our project plans for issue resolution, customer requests and exciting new innovations, all in our planned product evolution to ensure we deliver products exceeding our customers’ expectations. 

We hope you enjoy being a CyTrack Insider.