Billing Platform - UserGuide v4.01

8/8/2019 Billing Platform - UserGuide v4.01

1/33

Service description for

Billing PlatformVersion 4.01 | February 2010

Abstract here. This Upgrade Guide is for the Clients convenience only and is not a part of

the Agreement between MACH and the Client MACH reserves the right to change, modify

and/or replace the Upgrade Guide at MACHs own discretion.

This document is the property of MACH and contains confidential information or Intellectual Property Rights, both protected by law. Thisdocument is to be used only for the purpose for which it has been supplied and shall not be reproduced in whole or in part, published,

disclosed to others or used for any other purposes without the prior written permission of MACH.


2/33

Billing Platform User Guide

Page 2 of 33Billing Platform | Proprietary & Confidential

1. Document Information ....................................................................................... 41.1 Revision Log ................................................................ ........................................................ 41.2 Related Documents ............................................................... .............................................. 41.3 Terms and Abbreviations ................................................................................................... 4

2. Introduction ........................................................................................................ 53. MACH Portal One Way to Roaming Intelligence ............................................ 6

3.1 Access MACH Portal ........................................................................................................... 73.2 Browsers .............................................................................................................................. 73.3 Adjust the Portal via My Pages ....................................................................................... 8

4.

MACH Com Reports ........................................................................................... 9

4.1 Availability ........................................................................................................................... 94.2 Online access ...................................................................................................................... 94.3 E-mail Subscriptions ............................................................. ............................................ 124.4 Report descriptions ............................................................... ............................................ 12

4.4.1 Camel Correlation Report ........................................................................................ 124.4.2 M2T Report Process Date v1.1 ............................................................................. 144.4.3 Rejected Process Summary Report ........................................................................ 154.4.4 Rejected, CDR Details Report ............................................................ ...................... 164.4.5 Rejected, Missing CSF Files .............................................................. ...................... 174.4.6 TFG Delivery Report ................................................................................................. 184.4.7 Unprocessed CSF Files ........................................................... ................................. 194.4.8 Unprocessed MBF Files ........................................................................................... 20

5. TAP Creation Backend Report (sent via EDI) ................................................. 216. Online Control Center ...................................................................................... 24

6.1 File Overview ..................................................................................................................... 256.2 File Details ......................................................................................................................... 256.3 CDR Overview .............................................................. ...................................................... 256.4 CDR Details ........................................................................................................................ 266.5 Rejected CDR Overview ........................................................ ............................................ 276.6 Rejected CDR Details ........................................................................................................ 276.7 Test File Handling.............................................................................................................. 28

6.7.1 Test CDR Overview ....................................................... ............................................ 286.7.2 Test CDR Details ........................................................... ............................................ 296.7.3 Test CDRs Marking ....................................................... ............................................ 29


3/33



6.7.4 Test File Confirmation ............................................................. ................................. 306.7.5 Test File Generation ................................................................................................. 306.7.6 Test File History ............................................................ ............................................ 316.7.7 Test IMSI Management ............................................................ ................................. 32

6.8 Agreement Overview ............................................................. ............................................ 33


4/33



1. Document Information

1.1 Revision Log

Version Date Description

V3.00 20090501 Creation

V4.01 20100202 Updated Standard reports: Reject

Process Summary Report, M2T Report

Process date v1.1 report, Rejected

Missing CSF files report, Camel

Correlation Report and

Rejected CDR Details report.

1.2 Related Documents

Ref. no. Description

[R1] MACH SMART_Userguide

[R2] MACH COM_Userguide

1.3 Terms and Abbreviations

Terms/Abbreviations Acronyms

CDR Call Detail Record

CSF Client Specific Format, external file

format

EDI Electronic Data Interchange by a FTP

session

FCC File Control Center

M2T MBF to TAP files process/TAP creation

process

MBF Mach Billing Format, internal file format

OCC Online Control Center


5/33



2. Introduction

This Billing Platform User Guide is focused on the MACH Billing service providing you with an overview of theapplication and the various reports.

The standard set of reports through MACH COM and by EDI is provided along with the TAP Creation service.

These reports are described in chapters 4 and 5.

The operators using MACH Billing Platform can also optionally subscribe to the Online Control Center, which

allows file and record level detailed reporting. This tool is described in chapter 6.

For further information of the service, please refer to the MACH Billing Platform Service Description.


6/33



3. MACH Portal One Way to Roaming Intelligence

MACH Portal is your online interface and provides you with access to information and reporting related to DataClearing and related Value Added Services from MACH.

MACH Portal gives access to

Service Ticket contact MACH Client Support for assistance

File Control Center (FCC) monitor the operational status of your file flow

MACH Standard Reports (MACH Com) standard reporting for data clearing and other

services you subscribe to

Request Manager retrieve files

MACH Smart advanced flexible roaming reporting *)

Roaming Management System (RMS) agreement process management and

information exchange including Test Card Manager *)

Online Messages receive key messages

Exchange Rate Viewer view daily exchange rates

User Guides download documentation

Online Report Manager (ORM) Online access to generated back end reports

Online Control Center (OCC) self service interface for daily operational monitoring of

files and records *)

*) Access to MACH Smart, Roaming Management System and Online Control Center is dependent on

subscription.

FIGURE 1:MACH PORTAL


7/33



For more information on the individual applications or areas of information please see the relevant User Guides

made by MACH which can be downloaded via the Portal.

MACH Smart and Roaming Management System are described in the individual Service Descriptions and User

Guides.

3.1 Access MACH Portal

MACH Portal is available via the client log-in area onwww.mach.com or via Error! Hyperlink reference not

valid..pt.

FIGURE:2MACH LOGIN PAGE

To access the MACH Portal each user needs a user id and a password. Furthermore, MACH needs to register

our ip-address. Creation of user ids and registration of ip-addresses will be handled as part of the process

leading up to the upgrade.

3.2 Browsers

It is recommended that you use one of the following browsers (or higher version):

Microsoft Internet Explorer 6.0 SP1 and SP2

Netscape 7.2

Mozilla Firefox 1.07

The use of other makes or versions of Internet browser is not recommended and may result in limited nationality,

including suboptimal rendering (larger icons and texts).
http://www.mach.com/http://www.mach.com/http://www.mach.com/


8/33



3.3 Adjust the Portal via My Pages

On MACH Portal the client has the possibility to access some of the services by clicking my pages. Forinstance, you can access Online Control Center service by clicking the OCC page.

FIGURE 3: MY PAGES

By Clicking My Pages you also have the possibility to access the Online Control Center (OCC page).


9/33



4. MACH Com Reports

4.1 Availability

The MACH Com reports can be delivered via e-mail as scheduled reports or are available on-line via the MACH

Portal.

The following table lists the MACH COM reports and how they can be scheduled:

Report Scheduled

Camel Correlation Report Daily

M2T Report Process Date Report Daily

Rejected Process Summary Report v 1.1 Monthly

Rejected, CDR Details Report Daily

Rejected, Missing CSF Files v1.1 Daily

TFG Delivery Report Daily Daily

Unprocessed CSF Files Daily

Unprocessed MBF Files Daily

4.2 Online access

The reports are available on the MACH Portal and can be accessed in the following way:

Click on the MACH Smart Portlet

FIGURE 4.MACH SMART PORTAL


10/33



Click on MACH Smart folder

FIGURE 5MACH SMART SHARE FOLDER

The MACH TAP Creation reports are available on the following path

MACH Smart>Shared Reports>MACH Com>MACH TAP Creation.

To run a report the user is suppose to answer some common prompts, to answer the prompts follow the below

procedure:

1. Select the appropriate report from the Mach TapCreation folder.

FIGURE 6. MACHTAP CREATION FOLDERS


11/33



2. Complete the report prompts, if applicable.

FIGURE 7.EXAMPLE OF A DAILY REPORT PROMPTS

NOTE: Prompts notated as *(Required) are mandatory and requires the user to response before the report will

launch.

If the prompt is not selected to a required prompt, the default values are used. The following message also

displays.

FIGURE 8.EXAMPLE REQUIRED

3. When finished, click RunReport.

4. Thesystem beginsto process the request and the displays the following window:

FIGURE 9.PROCESSING REPORT REQUEST

5.When the report is finished processing, the report results

6. Review the process report.


12/33



4.3 E-mail Subscriptions

All MACH TAP Creation reports can be scheduled to be delivered by e-mail. Daily reports on the same timeevery day and monthly reports on the same day every month. The setup of the E-mail Subscriptions needs to be

requested by Mach Client Support.

4.4 Report descriptions

4.4.1 Camel Correlation Report

This report is a daily report providing a summary of the Camel Correlation process for the day before.

This report has a mandatory prompt displayed below

FIGURE 10. CSF FILE STATUS

You are requested to choose at least one selection from all CSF File Status like:

Not available

Absent

Deleted

SubmittedValid

Working

1. Toselect the elements, click on the elements in the Available combo box and move to Selected.

2. To move use the right arrow.

3. The report displays, a sample report is as below.


13/33


14/33



4.4.2 M2T Report Process Date v1.1

This report is a daily report showing all CSF files received, which have been converted into MBF files and whichhave been processed by the TAP Creation process. For each CSF file is information about the TAP Creation

Processing Status, the File Record Types, the Number of Call Event Details, the Call Duration and the Volume

shown.

Sample report

FIGURE 12. M2T REPORTPROCESS DATE V1.1

Description of the ColumnsCol

Column Name DescriptionMBF File Processing Date Date of processing of the MBF file

CSF Filename CSF File name

MBFFilename MBF File name corresponding to the CSF filename

MBF File Recycle Sequence Each time records are reprocessed from a MBF file an increment

is set in this column

Correlation Scenario Type When applicable, Type of Correlation applied to the records (i.e.

Camel)

Tariff Model Currency Currency of the tariffs applied

File Record Type Group of record Types (i.e. MO, MT, GPRS, WLAN)

MBF File Number of Call Event Details Number of records in the MBF file

MBF File Record Duration Total duration of the group of records

MBF File Volume Incoming Total Incoming volume in bytes of the group of records

MBF File Volume Outgoing Total Outgoing volume in bytes of the group of records

MBF File Average Call Age Average duration of the records from the group

TAP File Duration Total duration of the group of records

TAP File Volume Incoming Total Incoming volume in bytes of the group of records

TAP File Volume Outgoing Total Outgoing volume in bytes of the group of records

TAP File Net Charge Total Charge of the TAP records in TAP Currency

TAP File Tax Total Tax of the TAP records in TAP currency

TAP File Discount Total Discount of the TAP records in TAP currency

MBF Exchange rate LCL to SMC Exchange Rate between the Local Currency and the Settlement

Currency


15/33



Description

4.4.3 Rejected Process Summary Report

This report is a monthly report giving an overview of number of rejected records in the TAP Creation Process

within the last month. The report is also showing the reject types and if the rejected records potential could have

been giving a revenue (duration/volume in the records) if processed into TAP files.

Sample Report

FIGURE 13. REJECTED PROCESS SUMMARY REPORT

Description of the Columns

Column Name Description

Record type The different record type like: Rejected, Discarded and Recycled.

Error Code MACH internal returned code.

Revenue Affecting Number of Records Number of Records affecting Revenue

Non Revenue Affecting Number of Records Total number of records affecting Non-Revenue. (For MOC calls

Call Event Duration = 0 and for GPRS calls Data Volume IN and

Out = 0).


16/33



4.4.4 Rejected, CDR Details Report

This report is a daily report giving an overview of the rejected records received in the TAP creation process for

the last 60 days.The rejected records are group in Call Ages showing the Error Code, Error Description, the Error Category, the

number of records and the reject types.

If the reject type is pending then the calls have been rejected and not recycled. If dropped then the calls are

dropped and won't be recycled.

And if recycled then the calls have been recycled into a TAP file.

Sample Report

FIGURE 14. REJECTED CDRDETAIL REPORT



Call Age Band Time band of rejected records from rejected date to recycling.

Example: 31 to 45 days

Error Code MACH internal returned code

Error Description Description for rejection

Error Category Description Category of Error like: CDR Error, Missing configuration etc.

Record Type The different record type like: Rejected, Discarded and Recycled.

Number of Records Number of records impacted by the error.

NOTE: The call age = No of days from call time stamp to Report End date (Today -1) and notto the current date (Today)


17/33



4.4.5 Rejected, Missing CSF Files

This report is a daily report giving a list of all CSF files that have been failing in the MBF conversion process,have been missing in a file sequence or a duplicate to an existing CSF files received. It provides the CSF File

Name, the CSF File Status and the CSF File Receipt Timestamp.

Sample report

FIGURE 15. REJECTED,MISSING CSFFILES



Client TAP Code The PMN Code of the operator

CSF File Source Source of the CSF file. Only relevant if non unique (i.e.: Switchidentifier in the filename)

CSF File Name CSF File Name

CSF File Receipt Timestamp CSF File reception date at MACH

CSF File Status Current status of the file


18/33



4.4.6 TFG Delivery Report

This report is a daily report giving an overview of all the CSF file streams received on the CSF file receipt datesfor the last 30 days. For each file stream are the number of files and the record count shown.

Sample report

FIGURE 16. TFGDELIVERY REPORT



CSF File Type The file type reported: i.e. MBF / Ericsson GSM / Nokia GPRS.

CSF File Source Source of the CSF file. Only relevant if non unique (i.e. Switch

identifier in the filename)

CSF File Receipt Date Day of reception of the files at MACH

CSF File Count Number of Files received at MACH

CSF File Records Parsed Number of records present in the CSF/MBF file


19/33



4.4.7 Unprocessed CSF Files

This report is a daily report giving a lists of all CSF files, which havent been converted into the MACH internalfile format (MBF) and older than 24 hours since the CSF File Receipt timestamp.

Sample report

FIGURE 17. UNPROCESSED CSFFILES



Client TAP Code Operators PMN Code

CSF File Name Name of the CSF file not yet processed

CSF File Receipt Timestamp CSF Files reception date at MACH

CSF File Status Current status of the file


20/33



4.4.8 Unprocessed MBF Files

This report is a daily report giving a lists of all MBF files (MACH internal file format), which haven't been

processed yet into TAP files and older than 24 hours since the MBF creation timestamp.

Sample report

FIGURE 18. UNPROCESSED MBF FILES



Client TAP Code The PMN Code of the operator

MBF File Name The MBF filename

MBF File Creation Timestamp Date of creation or reception of the file

MBF File status Sample status:

_Rejected

_Conversion Failed_Working

_File is Dropped


21/33



5. TAP Creation Backend Report (sent via EDI)

Upon completion of the TAP creation process, a TAP creation report is created and can be delivered to client viathe EDI link between MACH and the client or by e-mail.

The report guarantees transparency in the TAP creation process which is required by the clients revenue

assurance departments. In the report the following can be found:

1. Which switch file content goes into which TAP file. This is a many to many

relationship overall transparency against the client is assured

2. The statistics for received switch files (including any erroneous CDR). The statistics

are intended to be utilized/processed by an application on the client side to compare

the figures against the files that have been sent to MACH

3. The statistics for the created TAP files directly after creation. Note that information

regarding the TAP files will be found in many standard MACH SMART/COM reports.

The report includes call dates, rating information, exchange rates, record types, durations, volumes and roaming

partner information.

The report file follows csv format, i.e. the fields within the file shall be separated by the semicolon ; character.

The report is kept in that form to allow clients comfortable viewing of the report with Excel, as well as easy

processing by client applications.

Sample report


22/33


23/33



Key : a field attribute for a single line in the report. The metrics are summarized for each key.

Metric : a countable value which is usually aggregated at report level, such as the number of calls, minutes, or

charge.

MBF Average Call Age Metric This is the average call age in the received MBF file. Calculated as difference

between call record

end and the receipt of the MBF file. This column is to measure the performance

of the client in delivering the data.

TAP Record Count Metric Total number of TAP records

TAP Duration Metric Total duration of TAP records in seconds

TAP Volume In Metric Total volume in of TAP records in bytes

TAP Volume Out Metric Total volume out of TAP records in bytes

IOT Currency Metric Currency of IOT of client (3 char ISO code)

Exchange Rate Metric Exchange rate used to get TAP charges

TAP Net Charge Metric Total TAP charge (in TAP currency, the currency in defined in the TAP

Creation Status)

TAP Tax Metric Total TAP tax value

TAP Discount Metric Total TAP discount value


24/33



6. Online Control Center

Online Control Center (OCC) is an add-on service to the TAP Creation service. Its therefore needed tomake a separated subscription in order to be given access to the below detailed features.

OCC provides self-service related functions and access to information on file detail level and CDR detail level.

OCC also provides extended search and filter functionalities in order to locate single files or records or simply to

get an overview of either files or records. Exporting results are supported by OCC as well, and are not subject to

the limitations in terms of rows retrieved, as mentioned in the following chapters.

Online Control Center will be activated by MACH Client Support and can be accessed via the Portal by clicking

My Pages as described in section 2.3.

FIGURE 19. MACHPORTALMY PAGES

The below chapters describe the Online Control Center Interface.


25/33



6.1 File Overview

The File Overview window is depicted below. Navigation to File Detail is achieved through the filenamehyperlink. Download is achieved via pictorial links next to each row. The maximum no. of rows retrieved in a

search is 500. The actual no of rows listed at a time is configurable, default is 20 rows.

FIGURE 20. OCCFILE OVERVIEW

6.2 File Details

The upper half of the window displays the file detail panel. CDR count fields, valid and error is hyperlinks to CDR

and window. The lower part of the window displays the resulting TAP files, if target is inbound CSF file. If targetfile is inbound TAP the lower panel displays resulting CSF files. Each filename listed is a hyperlink to file detail

for the specific file. Navigation to CDR overview is achieved through the TAP rec. no hyperlink or the CSF

(Client Specific Format) Records parsed and CSF Records mapped hyperlinks. The CDR Overview is then

displayed with an empty list but with proper search criteria.

FIGURE 21.OCCFILE DETAILS

6.3 CDR Overview

Navigation to CDR detail is achieved through the TAP rec. no hyperlink. Navigation to File Overview is achieved

through filename hyperlink. The maximum no. of rows retrieved in a search is 200,000 records. The actual no of

rows listed at a time is configurable, default is 20 rows.


26/33



The actual no of rows listed at a time is configurable, default is 20 rows.

FIGURE 22. OCCCDR OVERVIEW

6.4 CDR Details

The details display is a superset of the information from the CDR Overview form. CSF/TAP file names are

hyperlinks to the file details form.

Figure 23. OCC CDR Details


27/33



6.5 Rejected CDR Overview

Navigation to Rejected CDR detail is achieved through hyperlink on C/E Number. Navigation to File detail is

achieved through filename hyperlink. The actual no of rows listed at a time is configurable, default is 20 rows.

Rejected CDRs for inbound roaming only is shown.

FIGURE 24. OCCREJECTED CDROVERVIEW

6.6 Rejected CDR Details

The details display are a superset of the information form the Rejected CDR Overview form.

CSF file names are hyperlinks to the file details form.

FIGURE 25. OCCREJECTED CDRDETAILS


28/33


29/33



6.7.2 Test CDR Details

The test CDR details can be seen by clicking on the test CDR link in CDR overview panel

FIGURE 27. OCCTEST CDR DETAILS

6.7.3 Test CDRs Marking

Selection of test calls is required for manual test file generation. It shall be possible to mark virtually unlimited

number of test records, preferable using iterative search and selection mechanisms. The user can select the test

CDRs to create a test file out of it. Test files can be created for a particular partner. The user is having the facility

of selecting or de selecting the test CDRs from the view.


30/33



FIGURE 28. OCCTEST CDRS MARKING

6.7.4 Test File Confirmation

Once the test CDRs are selected the user can confirm whether to generate a test file out of these selected CDRs

or can go back and select another set of CDRs to create a test file.

FIGURE 29.OCCTEST CDRS CONFIRMATION

6.7.5 Test File Generation

The test file can be created by clicking on the Add to Test File button. Once the test file is generated the

reference number for the Test TAP file will appear in the screen, so that the user can search the same test file in


31/33



Test File History the reference, which is the request ID. The test file generated will appear in the history after 10

to 15 minutes delay.

Figure 30. OCC Test File Generation

6.7.6 Test File History

Test files can be viewed in Test File History based on different search parameters. User also can download the

test file from File Overview

FIGURE 31. OCCTEST FILE HISTORY

The same test TAP file can be downloaded from File Overview to see the details of the test TAP File.


32/33



6.7.7 Test IMSI Management

The user will able to upload/delete Test IMSIs through this interface. In order toupload IMSIs, the user needsto follow 4 steps:

1. SelectthePartner

2. On selection of partner, all existing IMSIs for that partner will be populated in the left hand Box

(labeled as Existing IMSIs).

3. To be uploaded IMSI Numbers has to be given in right side Box (labeled as To be Uploaded IMSIs)

a. Multiple IMSI(s) can be given with comma (,) as delimeter

4. Click on Add IMSI(s) button

5. Response from System:

a. If the all the given IMSI(s) are correct, then user will be prompted with Successfully Uploaded

b. If any one of given IMSI is wrong then user will be prompted with Imsi imsi no Invalid

NB: NONE of the IMSI(s) will be uploaded to system until all the given IMSI(s) are correctTo delete the Existing Test IMSI(s) the user needs to follow these steps:

1. Select the partner

2. On selection of partner, all existing IMSIs for that partner will be populated in the left hand Box

(labeled as Existing IMSIs).

3. Select the check box next to IMSI(s)

4. If all the shown IMSI(s) to be deleted, then user need to select the check box at Mark for Deletion

5. Click on Delete Selected

6. Response from System:

a. System will prompt Do you really want to delete IMSI? forconfirmation

b. If the user selects Yes then the system will delete the selected

IMSI(s) and System will prompt Successfully Deletedc. If the user selects No then system will NOT Delete IMSI(s)


33/33


6.8 Agreement Overview

The user will be able to get a status on his roaming agreements and services. This interface

will provide the client an overview of all their Roaming Agreements. The outcome/details canbe exported to Excel.

FIGURE 32. OCCAGREEMENT OVERVIEW