Bell Mobility www.bell.ca
Solution for Direct Marketing Response Rates
Project Lead: John Walker, Associate Director of Customer Insights and Analysis
Project Description: Bell Mobility chose dfPower Studio from DataFlux, an end-user solution that gives both business analysts and database administrators the ability to create, manage, and enforce data quality initiatives across the enterprise. With dfPower Studio, Bell Mobility now creates custom data verification routines that have helped them to identify and eliminate tens of thousands of duplicate prospect records while improving the quality of mailing and telemarketing lists.
End-to-End Customer Information Platform
Project Lead: Miriam O’Dowd, Business Manager, One IT Common Services and Components Program
Project Description: BT Global Services deployed a comprehensive customer service tool -- a BT-wide information hub -- for BT's contact center agents. Titled Agora, it's the initiative within the Common Services and Components Program to develop a strategic EIP (Enterprise Information Platform), the IT solution that will provide a single, consolidated, accurate view of end-to-end global customer inventory data. Following the Google model, the large-scale infrastructure platform pools, profiles, and integrates data from 15 disparate systems, eliminating problematic discrepancies.
Motorola: Enabling Rapid IT with SOA
Project Lead: Tom McMorris, Center of Excellence Lead -- Service-Oriented Architecture
Project Description: Selected AmberPoint as its SOA (service-oriented architecture) management vendor to help foster the rapid growth and evolution of its SOA landscape. The SOA project required the integration of multiple solutions. AmberPoint communicates bidirectionally with HP OpenView and IBM Tivoli for end-to-end management. Additionally, AmberPoint's end-point security integrates with Forum Systems for enhanced Web services security. Several levels of integration were overcome. The first level of integration was between the SOA Framework solution architecture. Motorola has a three-tiered architecture: registry, management, and security. They are developed independently of one another. As a result, Motorola developed integrations either electronically or through processes to provide the user with a simplified facade to deploy services. The second level of integration involves the development of services that are reliable, have the potential for reuse, and have the probability for easy consumption through the application of development and Web services standards. This integration process was created out of the complexity that most IDEs create when generating WSDLs. The third and last integration point deals with the integration within the development lifecycle. One of the chief concerns of many project and program managers was related to impacting project delivery dates. As a result, Motorola has devised a process that minimally impacts the development lifecycle while maximizing the identification and development of new business services.