Terminology
Technical Deployment means here activity reponsible for move software (like PHR, Gillie, Device Clouds) and hardware to live enviroment
Deployment means here implementation of Gillie AI and new processes. This requires change management, target setting, leadership and support for end user organization.
Good Practices for Deployment
SET A PROJECT
- Deployment is a project and you should appoint a project manager for it. Depending on the size of the organization, the project takes 2 to 20 hours per week from the project manager.
- The project manager must be committed to change
- The project manager must have the support of the organisation's top management for the project and sufficient authority to implement the change of processes into practise
SET PHASES
- Divide the implementation into stages and move on to the next one only after the previous stage has been successfully completed
- For each step, set goals and metrics that you know the stage was successful
INVOLVE PEOPLE
- Implementation requires the participation of employees in different roles and tasks
- Identify those willing to drive change and involve them and empower them in the implementation of change
Deployment Plan
The implementation project begins with planning, in which the stages and goals of the project are fixed. The end result of his planning is a deployment plan. The duration of a implementation project is usually 2-12 months depending on the size of the organization. The tasks of the planning phase are listed below.
No | Task | Check list |
---|---|---|
1 |
Assign project manager. Project manager must have time to drive change and a good domain knowledge.
|
|
2 |
Assign steering group. Implementation is steered in a steering group. Meetings are held once a month.
|
|
3 | Make a deployment plan. It includes phasing (2-3 phases), a timetable, objectives for each phase, and metrics to evaluate the implementation of the phase. This template can be used as a basis for the plan. |
|
4 |
Assign support users. Support users train and support end users. |
|
5 | Set metrics. You can use the example template *) below. |
|
6 |
Plan internal and external communication. |
|
It is a good idea to divide the project into 2-3 phases, after which the success of each phase is evaluated using the metrics set in the deployment planning phase. The table*) below provides examples of possible metrics.
No | Measurement |
---|---|
1 |
Reaction time - over 80% of predictive alarms are acknowledged in recommended time |
2 | Effectiviness - over 50% of alarms lead to action |
3 | Costs - home care visits concentrated at those who need them most |
4 | QoL - customers quality of life is improved |
1. Phase
In the first phase of implementation, users are engaged in a new way of working. The goal is to get as many people as possible to use the application in their own work. The duration of the phase is usually 1-4 months.
No | Task | Checklist |
---|---|---|
1 |
Enable alarms that require immediate response (so-called red alarms) in Gillie's organisation settings view. You can see list of alarms from here.
Note: This step is done, if
|
|
2 |
Enable the first 5 predictive alarms. You can see list of alarms from here.
The following alarms are recommended to be enabled at this point. You can modify the list, if you wish.
|
|
3 |
Start to use Gillie dashboard view, when analysing customers care need and service need.
|
|
4 |
Start to use statistics and recommendations reports.
|
|
5 | New employee orientation. |
|
6 | Evaluate succes of this phase. |
|
2. Phase
In this phase users start to use new features and alarms. The duration of this phase is usually 1 to 4 months.
No | Task | Checklist |
---|---|---|
1 |
Enable next 5 predictive alarms. You can see list of alarms from here. The following alarms are recommended to be enabled at this point. You can modify the list, if you wish.
|
|
2 | Start to use Analyses
The following analyses are recommended to be used at this point. You can modify the list, if you wish.
|
|
3 | Evaluate succes of this phase. |
|
3. Phase
In deployment projects last phase, rest alarms and features are taken in use. Duration of this phase is usually 1 to 4 months.
No | Task | Checklist |
---|---|---|
1 | Enable rest of predictive alarms.
|
|
2 | Start to use next Analyses-lists. |
|
3 | Evaluate succes of this phase. |
|
System owner and project manager
Information system consists of data, users, processes and software
Project manager is responsible for implementation phase. This means
- Driving the change
- Target setting
- Leadership
- Management
- Support
- Orientation
System owner is responsible for
- ensuring the goals are achieved and organisation is using IT system and new processes
- user guide
- trainings and skill management
- development of processes
- continious usage of the system
- change management
System owner should be from end user organisation.
Comments
Please sign in to leave a comment.