token

The first task was to determine a platform. Although copying the existing legacy architecture was a possibility, in order to streamline the order flow and get orders to customers in a timely manner, the decision was made to extend SAP's SD module. The next major component was to install and develop EDI system interface to manage their new customer volumes during the transfer from Lucent to Avaya. In conjunction with the EDI stream, was the additional task of building custom Idoc processing modules. These modules provided the necessary checks and validations to the system and rendered the "Avaya" personality to the format. Although, a new company by name, some of the business practices have been developed over 130 years, and the system needed to respond to these practices. Token and the Avaya resources needed to unite these elements on schedule and ensure they functioned properly. The system was developed, tested and deployed in time to begin the pilot testing within a six-week timetable. Eighty percent of the volume was converted during the subsequent six weeks. As requirements from the client changed during approaching deadlines, we successfully designed and implemented a flexible component architecture that permitted quick turnarounds and accommodated the necessary changes. The resulting system was 95% accurate on first time postings in comparison with a 75% success rate with the previous system.