Page Comparison

{noprint}{float:right|width=300px|background=lightgrey|border=solid blue 2px|margin=10px|padding=8px}
*Contents*
{toc:all=true|depth=4|excerpt=true|indent=14px}
{float}{noprint}
*Change log:*
|| *Date:* || *Author:* || *Version:* || *Changes:* || Completed || *Ext.* || *Int.* || *Is in Core* || Jira Ref. ||
| {page-info:created-date|dateFormat=dd MMMM yyyy} | {page-info:created-user} | 0.1 | Doc. created | No | | x | N/A | N/A |
| 18 July 2013 | Luca Casarini | 0.2 | Doc. completed | Yes | | x | N/A \\ | N/A \\ |
| 22 July 2013\\ | SD\\ | 1.0\\ | Checked\\ | Yes\\ | | x\\ | N/A\\ | N/A\\ |



h1h2. Overview

{note:title=Exclusive Report}

This report is available only to customers with a Managed Service Agreement.
{note}



| *Name of report* | System Overview Report |
| *Schedule* | Daily |
| *System* | Retail/Wholesale; Prepaid/Postpaid \\ |
| *Customer role* | Informed, Responsible (on available SIM card/A Numbers) |
| *CDRator Operations role* | Informed |
| *CDRator role* | Informed |


Description of the roles:
# Escalate - the recipient escalates to the Informed role if the content of the report becomes a concern.
# Informed - the recipient gathers information by the content of the report. No reaction is expected.
# Responsible - the recipient is expected to read the content of the report (or a part of it) and to take the necessary actions.

h3. System Overview Report

The System Overview Report returns a basic overview of the statuses of several entities of the system.

Depending on the system configuration, one or more of the points below could be missing:

* Subscriptions per Product/Rate Plan/Account Type/Status.
* Active Subscriptions per Brand/Billing Group type/Network/Rate Plan.
* Subscriptions that changed status the day before.
* Pending workflow activities.
* Assignment of campaigns.
* Available SIM cards.
* Available A Numbers-numbers.
* Throughput of critical processes.



h2h3. Subscriptions per Product/Rate Plan/Account Type/Status

Number of subscribers assigned to each of the elements above.

 !rpt5.png|border=1!


h2h3. Active Subscriptions per Brand/Billing Group type/Network/Rate Plan

Number of active subscribers assigned to each of the elements above.

 !rpt1.png|border=1!

h2h3. Subscriptions that changedChanged statusStatus the dayDay beforeBefore

Number of subscribers that changed status to one of the following:

* new signup
* from initial to terminated
* from active to terminated
* from any other status to terminated

!rpt6.png|border=1!




h2h3. Pending workflowWorkflow activitiesActivities

These are the activities that are waiting to be executed regardless of when they are due. *This is not the workload of the workflow engine*, noticenote that there are several waiting and external activities\! That is part of the Critical Processes Monitoring Report.


!rpt2.png|border=1!




h2h3. Assignment of campaignsCampaigns

Active subscribers for each campaign.

 !rpt3.png|border=1!


h2h3. Available SIM cardsCards and A -Numbers

CDRator Operations will load new resources into the system, but it's is the customer's responsibility to provide Operations with the file containing SIM card/A -Number information. The file must satisfy CDRator's requirements onto its format.

!rpt4.png|border=1!


h2h3. Throughput of criticalCritical processesProcesses

This table displays how many records were processed by the main functionalities of the system on the day before.

!rpt16.png|border=1!