Bill Presentment (Project Imagine)
TELUS underwent the 2nd phase of its billing system upgrade; this time converting 3 million existing customers to the new system. The Bill Presentment team acts as a receptacle for data from the billing, customer, and usage data. That data is compiled and transformed into a bill for a single month and stored within a central database. The data is then sent to a printing system where it makes up the bills being printed to the customer. The goal of this team is to ensure that 1.5 million bills are processed accurately and efficiently every month.
We provided a business systems analysis role to act as a liaison between Bill Presentment and external teams: Billing Operations, Enterprise Data Warehousing, and upper management. This required us to act as a 24/7 first responder for bill presentment, ePost, eBill and other billing data issues that occur during a bill run.
When issues occurred, we performed defect and impact analysis/reporting on Production billing problems. Sometimes these impact analyses involved investigating SQL, Unix, and Java defects due to data or code errors. If the data was found to be in error during a bill run, we developed hotfixes in SQL or Unix shell script. Developing hotfixes meant we needed to create and maintain tracking information for Bill Presentment changes destined for production.
Once the batch system became stable, we assisted in the development of the front-end for the new Web application used by customers to view and download their eBill.
Environment Management (Project Imagine)
TELUS rebuilt their 30-year-old billing system with up-to-date technologies. This project was their largest national project with an estimated $400 million budget. The system is built upon a multi-tiered web services architecture, housed inside the J2EE container, BEA WebLogic. It consists of 4 service components, 8 databases, and numerous legacy services, making it one of the largest system overhauls in the Telecommunications industry. An entire team was required to handle the large number of environments used for development, testing, performance and finally, Production.
We helped to install, configure, and maintain over 10 pre-production WebLogic servers, which were used by various internal teams. When then worked to install, configure, and maintain the production WebLogic cluster (including 2 additional clustered environments for performance testing and production staging). Since many of these environments were custom built, yet used virtually the same configuration, we wrote Unix shell scripts to manage the deployment of source code and the support of WebLogic servers within all environments. We also wrote preliminary Jython scripts for accessing the WebLogic Scripting Tool for use with WebLogic 9.2.