Billing Systems Consolidation

From MIKE2 Methodology

This article is a stub. It is currently undergoing major changes as it is in the very early stages of development and is only a placeholder. Please help improve MIKE2.0 by adding to this article.

For Telecommunications providers and Utilities companies, it can be argued that the Billing system is the actually the main touchpoint with customer – not the CRM system. It is the Billing system that the customer is used to “seeing” in the great majority of interactions. Despite this, many organisations’ billing environments often contain several systems that are very complex and difficult to manage due to growth through acquisitions and legacy product-oriented architectures. The transformation initiative to address this problem is complex and often results in failure if there is an insufficient focus on Information Development.

Contents 1 An Overview on the Business Solution 1.1 Definition of the Solution Area 1.2 Impacted Industries 1.3 Why this Solution Requires an Information Development Approach 2 Typical High Level Business Requirements 3 Project Delivery using MIKE2.0 3.1 Key Components Required from SAFE Architecture 3.2 Applicable Activities from the MIKE2.0 Methodology 4 Best Practices for Implementation 5 Areas of Complexity 6 Applicable Software Solutions

An Overview on the Business Solution

Definition of the Solution Area

Impacted Industries

Why this Solution Requires an Information Development Approach

Typical High Level Business Requirements

Project Delivery using MIKE2.0

Key Components Required from SAFE Architecture

Applicable Activities from the MIKE2.0 Methodology

Best Practices for Implementation

Areas of Complexity

Applicable Software Solutions