The objective of Billing 2000 was to undertake review of the current suite of Billing's Offline systems and to come up with a smaller number of new systems to meet the business requirements. Four new systems were identified to consolidate the use of over 40% of Registered Billing Critical Systems. This was the largest rationalisation of Billing Systems since Network Code (Regulated basis of contract between the client and their customers) was implemented.
| |
Ad hoc billing |
| |
Server End: Unix HP-UX 11, Oracle 8i |
| |
Middleware: Unix, OAS 4.0.8.1 |
| |
Client: Windows NT, Netscape Navigator 5.0, Internet Explorer 4.0, Developer 6i |
|
|
| |
Adjustments processing |
| |
Server End: Unix HP-UX 11, Oracle 8i |
| |
Middleware: Unix, OAS 4.0.8.1 |
| |
Client: Windows NT, Netscape Navigator 5.0, Internet Explorer 4.0, Developer 6i |
|
| |
|
|
| |
Filter failure |
| |
Server End: Unix HP-UX 11, Oracle 8i, IBM S390 |
| |
Client: Windows NT, Cool:Gen 5.1 |
|
|
| |
Accounts receivable and credit management |
| |
Server End: Oracle 8.0.5, SAP R/3 4.5b |
| |
Middleware: Sun OS, SAP R/3 4.5b |
| |
Client: Windows NT, SAPGUI |
|
Wipro was involved in this project right from the analysis through design, development, Implementation and support in production. Wipro participated in the complete life cycle of all the four new systems. The Offshore-Onsite Global delivery model was successfully utilized in this project. Wipro chose two distinct Implementation methodologies. In the first phase, a high level analysis of the requirements was undertaken followed by detailed design of the system. It was followed up with development, testing and implementation. The main deliverables were Analysis and Design Report (ADR), Program Specifications Report, Test Plan Report, Cases and Results Reports. In the second phase, an in-depth study of the existing processes and system provided an "AS-IS" document. It was followed up with narrowing down SAP R/3's broad scope to fit the client's industry specific processes. Business analysis tools were used to create a document called Blue Print that reflected future processes for Client's business. The next phase, termed as "TO-BE", created enterprise system architecture to support these business requirements. It was followed up with configuration of SAP R/3 system to embed it into the client's IT architecture besides enhancing and building interfaces. The system was then integrated and system tested and finally implemented. |