Intelligent Network Services is the area in which traditional telecommunications, mobile communications and data communications meet. This is achieved by introducing new services in the telecommunications network. To make this possible, the traditional concept of switching networks must be extended: Intelligence must be introduced into the telecommunications network in order to recognize and route calls to the nodes executing the services (containing the actual program logic), and databases are needed to hold the large amount of service and customer data. Service Creation and Management functions must be provided to administrate the Intelligent Network, as well as clear interfaces between the switching network and the Intelligent Network.

Real time action to the problem is the key success factor for delivering reliable network services. This requirement must be supported by appropriate tools with smallest delay between the time when network measurement generated and the time operator informed. Operators only take action based on information informed.

Nowadays, available tools have capabilities to collect measurement, stored in database, and then displayed to user either upon request or automatically in a dashboard. This type of solution present a significant delay between the time measurement collected and the time operator informed. The delay is primary contributed by the time taken for writing and reading measurement to and from database. The delay is even bigger when number of data to be store is huge.

Renevis proposed a smart solution to solve the delay issued explained above. User has full control of types of interest counter to be supervised, in that way Renevis will dispatch all data to the defined client for real time view. User also has capability to defined threshold condition for certain counter and Renevis create notification if given threshold condition reached.

Renevis is a developed in modular based on Java technology which promote portability and scalability. Renevis support currently on the commercial database like Oracle, Microsoft SQL Server, IBM DB2 or open source database like MYSQL or PostgreSQL.

All files from network element is collected and parsed immediately after the measurement is committed into the file. Renevis proposed these measurement files is actively collected from the source in that way the delay is minimized. User may specify the collection schedules, source server, and source folder. Smaller time may be better but operator must take cares the impact for the source server, mostly processor time.

Parser only developed for certain types of measurement file, new types of measurement file will not cover by currently installed Renevis. User need to purchase another parser if new type of measurement files is presented. All types of measurement file must be informed to TOTALINDO before the project start.

All counters from parsed file ready to forward and all of these counters enabled to other modules. Changed in the internal structure of measurement file that caused the parser cannot proceed the file is a lack and this is new type of measurement file, require new parser.

The configuration for all collected measurement file is stored in a file and operator only need to modify this file if the node has changed. This file contains detail information regarding to the collection of measurement file.

All parsed data is forwarded into Counter Engine, first module of three central modules of Renevis. This module has tight interworking with SQL Engine and Notification Engine. This module has responsibility to forward all counter to defined consumer. The counter consumer in the client side is Real Time Chart Viewer.

The counter received from Measurement File Parser is immediately forwarded to the consumer without any other process in time between. In this way the Renevis promise shortest time to inform operator.

Notification Engine is second module of three central modules of Renevis. This module consume counter from Counter Engine and only process certain counter based on configuration. Operator has full control what counter to consider and define the threshold value for selected counter.

Notification engine will forward the message based on defined configuration, to Email or SMS. There are sub modules that enable these functions. User has control where the message must be forwarded if certain counter has reach the threshold.

For storing purposes the Renevis has last central module that stored all defined counter into database. Number of stored counter possible to change in the future but will need certain effort in modifying the structure of the table. This change may be realigning from the measurement file parser.

Size of data to be stored is manageable by operator and Renevis has no direct control on that. The consequence if more data stored is more time consumed by Eclipse BIRT to generate the report. Number of data size has no effect on Notification Generation and Real Time Chart Viewer.

All counters from same node type for one vendor are stored in one table and this is always ever growing. Operator need to create a schedule that discards the old data.

This is client module that has capability to manage the system. This is a web application run in the user desktop. This module manages the runtime aspect of Renevis and mostly related to Notification. Notification is defined by a Notification Scenario. All aspects of notification are defined in Notification Scenario and user has full control how the notification works. Here are some of aspects those are required to be defined:

1. Condition, operator must defined an interest counter and state the threshold. A message will generate if the threshold reach and forwarded to recipient group.
2. Recipient agent, a definition that state the type of agent (SMS or Mail) and additional parameter, MSISDN for SMS agent and email address for Main agent.
3. Recipient Group, is a collection of Recipient.

This is the client application that displayed in a wide screen media. Operator has full control how the viewer arranged and what counter is interested. User has control how individual data in the chart is profiled, regarding to the color, shape and mark.