Agriware Implementation

SureStep method

Mprise Agriware uses what is known as the SureStep method for implementing the Agriware Suite. This methodology splits the entire project up into the following phases: 

1. Diagnostic phase
2. Analysis phase
3. Design phase
4. Configuration phase
5. Roll-out phase
6. Production phase

Diagnostic phase

The bulk of the work for this phase is carried out during the preliminary stages. Its primary purpose is for those involved to take a look together at how appropriate Agriware is for the organization. 

• Getting a clear picture of the wishes and the directions solutions can be sought in.
• Is the software appropriate for the wishes and requirements?

Analysis phase

After the diagnosis phase has been completed and the company has decided to proceed with Mprise Agriware^®, a more in-depth examination is needed. All the details then have to be brought to light. It must now become clear exactly how the package is to be implemented. This means that any bottlenecks must also be mapped out. This phase must end with a presentation of the proposed solution. At that point, discussions must be started if necessary about resolving any bottlenecks that may be present by changing a process or by developing customized software.

• Draw up a blueprint and project plan;
• Go through the business processes with the key users;
• Obtain an overall picture of the required functionality and any modifications;
• Installation of the software (and hardware if necessary);
• Presentation of the solution without customization (SIM 1);

Design phase

Training for the key users commences in this phase. Mprise Agriware^® will also start developing any customization required at this point. The company starts writing the work instructions. 

• The key users receive training based on the working processes as described in the blueprint;
• Assessment of customization issues and making the choices for its development;
• The key users start writing the work instructions;

Configuration phase

When the customization work is ready and the work instructions are available, it is time for an integrated system test, preferably using the company’s own data. If necessary, that data will be migrated from the existing systems to the new system. 

• The key users complete the work instructions and start working towards being able to carry out the integration test independently (SIM 2);
• Pilot conversion of data from old systems;
• Implementation of customization;

Roll-out phase

The system has now been configured and can be used. It is now time to start training the end users. The work instructions have by now been produced by the key users. These key users of the system will now be able to show the other users the ropes. A “go-live” plan is produced and the user interface is optimized. Finally, a definitive decision is taken about whether or not to go live on the date stated.

• Training of the end users by the key users
• Make and carry out a “go-live” plan;
• Set up a roll-out centre;
• System acceptance (SIM 3).

Production phase

A definitive data conversion is carried out. The users start actually using the software.

• Go-live: conversion and start of use of the software;
• After-care and completion.