EngageIP is a Business Support System (BSS) software application for communications service providers. The software is a web application that may be deployed on servers located on-premises or in a hosted environment.
|Stable release||18.104.22.168 / 2013-12-10|
|Operating system||MS Windows Server|
|Platform||MS SQL Server|
EngageIP was developed using emerging technologies and standard practices. The Application is separated into three main tiers to allow the separation of a user interface, business logic and provides persistent data structure. This allows the EngageIP applications and associated development to adapt to changing technologies, the ability to port to new database servers/architectures and to support operations in multiple deployment scenarios. The software may operate in a single server deployment or multi-server environment containing redundancy, load balancing and partitioning of data.
The core system has been designed to be deployed as an installed application or a multi-owner hosted solution. EngageIP has been developed with a web centric design to eliminate the need for specifically configured workstations and client based software.
The Architecture of EngageIP leverages Microsoft .NET technologies and as well as a Microsoft SQL server database for data persistence.
The application has been built to provide a wide range of features and operations used by communications service providers. These include:
• Product/Service Management
• Customer Account Management
• Usage Rating • Business Process Management
• Revenue Assurance
• Wholesale and Retail Relationships (Billing as a Service)
• Subscription Billing
EngageIP is versioned using a 5-digit instance format in the general form A.B.C.D.E
* A is the major version number * B is the minor version number * C is the release number, which begins at zero and increments as new releases are launched * D is the interim build number * E build number/revision number (5-digits)
Interim releases - Are released weekly and form a roll-up of current development effort.
Maintenance releases - Thoroughly tested releases that include enhancements and bug fixes.
Business Logic Layer
All access from EngageIP Services, administrative portal, rating and mediation processes is channeled through the business logic layer. This layer is written in C# (C Sharp (programming language))/.net 2.0 and provides an abstracted interface from the data access layer for simplification of code development and knowledge of the underlying data structure.
Web Services API
The EngageIP Web Services are built on top of the Microsoft Web Service framework. This method allows for easy integration with .net applications as well supports of standard SOAP (XML) and HTTP protocols access for non-Microsoft applications. The web services provide methods to perform administrative and self services operations. Customers make use of these APIs to integrate with their existing customer portals and automated business processes. The web services methods allows Service providers to integrate existing system for provisioning, billing, accounting and customer management.
Mediation and Rating
The mediation and rating processes are separated into two processes. The mediation process is responsible for collection and processing of usage data. This included data-specific usage, telephony CDR (Call detail record), web hosting and disk usage. The mediation process has been built with a database configuration to enable updates to supported data formats with minimal or no code changes. Standard usage formats have been supported by dedicated methods that allow for specific efficiencies in data process and mediation rule application to ensure performance and scale can be achieved. The mediation process will consolidate usage data into the EngageIP standard format and can also be configured for consolidation of multiple feeds into an exported dataset for processing by an external mediation or billing system.
Software Development Methodologies
Development is performed using an Agile Modeling methodology with a focus on the Scrum (development) principles. These include:
• User story defined based on Marketing / Product Management requirements
• User story review and scheduling
• Use cases designed as test cases
• Development based against user story and test cases
• Quality assurance based on test cases (automated)
• User story used for QA process
• Documentation of deployment and new functionality
• Implementation of new functionality
- EngageIP Billing and Usage Rating platform., retrieved October 2007