AT&T
I was hired by PacBell, but by the time I reported to work, it had been purchased by SBC. I was there for a period of rapid growth and extreme corporate stress.
I was there for the purchases of Ameritech, SNET and SouthWestern Bell - which also gave SBC all shares of Cingular.
I was there for the purchase of AT&T, and the renaming of SBC to AT&T (in order to get the coveted single letter NY Stock Exchange trading symbol "T").
Y2K Compliance
I developed and maintained data load for Y2K Compliance System. A discovery tool would gather installed software name/version data on thousands of systems. The discovery tool had to work on Windows for Workgroups, Windows 3.1, Windows 95, Windows 98 and Windows NT. It frequently crashed, creating partially formed MIF files. The data load had to be able to digest these files without error. I also wrote many file manipulation tools in Perl to aid in manual searches of the Y2K Compliance data. We maintained a database of all software titles/versions installed on 350,000 workstations.
Click here to see the award I received for my work in Y2K Compliance.
After Y2K, I joined the newly formed Asset Management System (AMS) to manage these assets. The legacy asset management system (which we were replacing) was created prior to the industry standard which provided the capability to read the Serial Number of a workstation over the intranet. Using the former system, SBC was not able to find 15% of their workstations when the 3 year lease expired, so it was not able to return the equipment, and was paying huge fees.
For AMS, I did the requirements analysis, design and development of many subsystems. The most significant is the invoice import. The system was required to support importing hundreds of invoices representing the acquisition of thousands of workstations each day. The import needed to reconcile the invoice against the Purchase Order and Request, taking into account changes in Orders. It also needed to insert records representing the assets and the adjustments to the assets. There was also a serious time constraint on the processing.
I was the software lead on the migration of all active data from the legacy system to the new asset management system. We needed to translate and insert the data for 300,000 assets, their adjustments, product descriptions and lease contracts. This needed to be done as soon as possible with no data loss. I was able to achieve a very high throughput rate that allowed delivery ahead of schedule. I was also instrumental in retrofitting established processes in the new system that started failing or faltering because of the larger scale of the data.
I learned, upgraded and performed bug fixes on the webMethods B2B Service written in Java. This was not easy because we had chosen a third party database system that did not have a Java API, so we needed to use the Java Native Interface protocols in order to pass data between Java and C. I have had recent training in webMethods 6.1
Asset Management System
Click here to see the architecture of AMS.
I have developed many stored procedures in MS SQL. I am self-taught in ODBC. I am self-taught in MS Access. I am self-taught in Visual Basic. Although I did not develop the webMethods B2B server portion of our system, I was fully cross-trained in its functionality a development tools, and fixed various bugs.
I was actively involved in defining the software development process for our team. I made numerous technical presentations at developer meetings. I produced good technical documentation in a timely manner. I have an excellent relationship with Quality Control. I mentored multiple team members, both by assignment and of my own free will. I have served as a leader in the Emergency Response Team for 5 years.
Single Web Ordering Tool
SBC Online has various ordering websites. Our team is commissioned to create a single backend that will support them all, plus newly added retail partnerships. I am responsible for the Customer Validation API on the Backend. I have made a point of knowing all the Web Services APIs so that I can help the architects make this system ready for retail partnership. Retail Partnership will allow customers to buy SBC products on websites like Amazon.com. We are using WebSphere 5.1 as our Application Server. Our system communicates with various legacy systems at SBC to get information on customer accounts and product offerings.
Friday, April 17, 2009
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment