As part of any ISIS Warehouse Management System project implementation, a dedicated Project Manager is appointed to manage the project over the entire implementation period. Using computer based management tools and in consultation with client staff, a detailed project plan is developed by the Project Manager. Along with the Functional Specification, the plan becomes the principal medium for monitoring and controlling all aspects of the ISIS Warehouse Management System Project.

Additionally, the plan forms the basis for regular management reporting and visibility to all parties during the life of the project to allow a full audit and traceability.

Control and reporting of progress are maintained via regular project reviews and status reports at which a client representative typically controls and the Microlistics’ Project Manager takes a reporting role. Depending on the size of the project and the scope, a regular steering committee meeting may also be required.

One or more implementers will be allocated to assist with the ISIS implementation project. Microlistics’ implementers have extensive warehousing experience, as well as a high level of technical skills. They are adept at assisting client staff through the changing processes involved in new system implementations.

Microlistics’ implementers deliver both theoretical and hands on training to client personnel. Additionally, the on site implementer delivers close assistance and guidance throughout the implementation process, which includes installation, testing, training and support. Typically, the Microlistics’ implementers remain on site for the duration of the implementation project or until client personnel become self sufficient.

Examples of activities typically undertaken by Microlistics Implementers include:

• Installation of ISIS software on the client server equipment
• Fine tuning of RF equipment when installed
• Provision of technical advice and guidance for cabling and network setup
• Assistance with conversions of client files from enterprise or legacy systems
• Other data take on activities
• Low level system documentation.
• Detailing each core process including a map and definition, to give a clear understanding of:
  • The purpose of each process
  • What is specifically included in each process
  • The triggers for entry and exit of each process.