Deployment Plan for Phase 2B

As we are approaching near to the next scheduled go-live date, the team is at every niche to make sure the deployment plan is up-to-date with the understanding of the required implementations, configurations, hardware/softwares are in-place and necessary communication channels are established for the affected parties.

Deployment Plan for Phase 2A:

1. Product Codes for Vendor 2As – migration from Test to Production
2. Central Addresses – migration from Test to Production
3. User accounts for Using the Application -migration from Test to Production.
4. Installation of EDI processing at central depot – on site
5. Printer Setup and local software installation (5 locations) – on site
6. Training to Vendor 2As on the new solution (5 locations)- on site
7. Sanity check after installation
8. Prepare cutover communication to affected parties on post-cutover support process and escalations

Leveraging new system performance against existing application

There are times that legacy systems are hard to maintain and incur more costs, the Organization needs to revamp new solution to manage the demand and robustness to sustain the business. As this is a strategic direction for all units (sales, operations, finance etc) we do have certain levels/expectations of the quality of the new solution delivered to them. To leverage on the quality, we refer to the existing SLA (Service Level Agreement) that is in-place for conditions on supporting the legacy system to support the new solution.

As legacy systems are normally developed in old technologies, the inclusion of new components for the new solution may have impacts to the users’ expectations. Initial findings of the new solution are evaluated and bring back to Development team to analysis and suggest on the plan for improvements. We have also worked on the infrastructure to see what are the workarounds available to improve the performance while having some time buffer to work on it.