The Routes system implementation plan includes four stages:
-
Stage 1 - Initiating the implementation project
-
Stage 2 - Installing the system
-
Stage 3 - Expanding the system
-
Stage 4 - Completing and accepting the project
Stage 1 - Initiating the implementation project
-
The release initial analysis which assesses hardware, software and human resources requirements
-
Creating project deployment teams
The release initial analysis which assesses hardware, software and human resources requirements
This stage serves to determine if the beneficiary has the hardware and software infrastructure required to support Routes installation. In case the beneficiary's infrastructure does not comply with deployment conditions, a report will indicate the infrastructure changes suggested to make it meet system install requirements. Possible upgrades of certain infrastructure items may be determined, in order to maximize its potential to the full. This stage also covers an estimate of the number of future users logging in.
Creating project deployment teams
Routes deployment is based on the two teams assembled: a Red Point team and a beneficiary team. The Red Point team will be made up of:
-
a project manager;
-
systems analysts;
-
programmers;
-
testers;
-
training instructors.
The members of the beneficiary team will be:
-
a project manager;
-
key users;
-
network administrator;
-
the Routes system administrator.
The teams will be assembled as agreed between the two parties. Team formation may vary during deployment, as agreed by the two parties. The number of persons making up the two teams will also depend on the scope of the deployment project.
The table below details the tasks associated with each role identified above as a part of the two teams:
| Role | Team | Description |
| Project Manager | The Red Point |
|
| System Analyst | The Red Point |
|
| Programmer | The Red Point |
|
| Tester | The Red Point |
|
| Training instructor | The Red Point |
|
| Project Manager | Beneficiary |
|
| Key users | Beneficiary |
|
| Routes system administrator | Beneficiary |
|
| Network administrator | Beneficiary |
|
Stage 2 - Installing the system
The Routes system is installed on client premises during this stage. The system is installed with an uncustomized, basic configuration. The install stage is staggered across 2 steps: installing the Routes server and the Routes client applications. To install the client applications, a list of users is compiled, as shown below:
| User | Position | Client computer configuration | Rights |
| Popescu Ion |
- |
AMD Athlon XP 2200+, 1.80 GHz, 512 GB of RAM |
|
| Vasilescu Mihai | Head of Dept. | AMD Athlon XP 2200+, 1.80 GHz, 256 GB of RAM |
|
At this time, user-specific rights in the system are also determined. The Routes system administrator and The Red Point team enters this data into the system by using administration modules.
After install operations are completed, the training session is scheduled. This session will include all users (or some of them) in the previous table. By client demand, users can be assessed after the training course ends.
Stage 3 - Expanding the system
This is the main stage in the deployment plan. The system is analyzed for customization. New features requested by the beneficiary are outlined and programmed. The software systems existing on client premises are also analyzed to assess potential data import options. This analysis will also serve to establish the members of the project teams.
After analyzing new the features suggested, steps are taken to develop them. Depending on the provisions made in the plan, the system may be upgraded and new training sessions may be scheduled to cover new system functionalities during the development process.
Stage 4 - Completing and accepting the project
This is the stage when the following events are scheduled:
-
final install operations - the last system upgrades (the Routes server and Routes client apps) are installed;
-
system tests - all system features are checked by The Red Point team. The test program includes: feature tests, performance tests, compliance tests;
-
holding a final training session;
-
system acceptance by the client;
-
the warranty period commences (in case this period has been defined in the contract).
