Investing in a best-of-breed warehouse management will obviously generate significant cost and service improvements, but it is important to ensure your operating requirements are matched by system functionality.
Our experienced supply chain technology consultants and project managers undergo a thorough analysis of your warehousing operation to establish the most appropriate configuration of your ISIS warehouse management system.
Central to identifying these needs is an exercise we call a Conference Room Pilot (CRP). By undertaking a CRP, the specific requirements of your operation are determined and areas for improvement identified.
Outlined below is an overview of the needs analysis process (included the CRP) that is typically conducted by Microlistics personnel.
| Core Process |
Intent |
Begins With |
Ends With |
Includes |
| CONFERENCE ROOM PILOT |
To define the clients functional requirements and highlight any required enhancements |
Sales details received from Marketing |
Authorised Operational specification |
Review of current processes and revise these as necessary to make best use of ISIS. Establish interface requirements. List of possible enhancements to ISIS (for ISISenterprise and ISIS3pl only). Agree an implementation schedule. |
| PROJECT DEFINITION |
To finalise a precise project plan and to sign off implementation contract with the client |
Authorised Operational specification |
Contract signed and Project plan agreed to by client |
Preparation of draft project framework. Ordering of RF equipment (if appropriate). Final Project Plan. Contract signed. Staff Briefing (walk through project deliverables). |
| CONFIGURATION STATEMENT |
To identify all software and hardware components as identified in the Conference Room Pilot. |
Conference Room Pilot. |
Operational Specification. |
Identifying Server, Operating system and modifications required to be developed (for ISISenterprise and ISIS3pl). Identifying set up requirements (eg. Macro's and tasks) |
| SYSTEM CONFIGURATION |
To put together all software and hardware components required as identified in the Systems configuration statement. |
Operational Specification.Systems Configuration Statement. |
Hardware and software set up and configured ready to commence Verification Testing. |
Development of add-ons to standard software. Build up of system. Ordering of Server and RF equipment.Receipt of Server and RF equipment. Setting up of system on hardware. Creation of Verification team. Verification Test Plan and Cases. |
| VERIFICATION |
To ensure that the system meets the customer operational processes. |
Verification Test Plan and Cases signed off. |
Verified system that meets the users operational requirements. |
Conducting of verification test. Raising/fixing of any issues raised. Documented evidence of results. Verification sign off. |
| SITE IMPLEMENTATION |
To transfer the tested system on site. |
Verification testing completed and signed off. |
System installed on site. |
Delivery of equipment. System installation.Training of client system operators. |
| HAND OVER |
To pass on ownership of the system to client. |
System installed on site. |
Final delivery sign-off. |
Acceptance test. Final system configuration.Train operators. Sign off of delivery.Introduction to Support Manager. |
