Purge

Under data protection legislation, an organisation must not retain customer In the context of the Cloud Monetisation Platform, an individual or organisation who has signed an agreement to take goods and services from a service provider. A customer receives a bill associated with one or more subscriptions, and can be a single end user or a large company with many subscriptions assigned to one agreement. data any longer than necessary. Information no longer in use should be purged. Purging involves deleting or obfuscating data.

For more information on Purging in CMP Converged Monetisation Platform. The MDS Global product that supports customer care and billing for digital service providers., see the CMP 8.1 Purge Guide.

The Purge process includes the following jobs:

• Account Purge

  This job removes personal customer information, such as contact names or account In the Cloud Monetisation Platform, a billing entity that can be used to manage payments on one or more subscriptions or payments for services. An account can hold details such as payments or invoices. passwords, for accounts that are no longer in use. This job does not delete records. Instead, it obfuscates personal data elements using asterisks for character values or zeros for numeric values. This job derives a calculated purge date based on how long data should be retained before it can be purged ‐ the Months to Retain parameter. Only data from accounts changed on or before the calculated purge date will be obfuscated. This is a scheduled job. This job can be scheduled to run daily; however, it is more likely that monthly or quarterly executions will be sufficient.

• Address Purge

  This job removes address information that is no longer in use; that is, there is no longer a reference to the address in any table in CMP. There is no input parameter for this job; an address is simply in use or it is not. No archiving takes place prior to the deletion of the records. This is a scheduled job. This job can be scheduled to run daily; however, it is more likely that monthly or quarterly executions of this job will be sufficient.

• Payment Card Purge

  This job removes credit and debit card information that is no longer in use, that is, cancelled cards. This job derives a calculated purge date based on how long data should be retained before it can be purged ‐ the Months to Retain parameter. Only data from accounts created on or before the calculated purge date will be removed and no archiving takes place prior to the deletion of data. This is a scheduled job. This job can be scheduled to run daily; however, it is more likely that monthly or quarterly executions of this job will be sufficient.

• Consumer Purge

  This job removes personal customer information, such as contact names or account passwords for terminated single subscription A billing entity that incurs a charge. Examples include a network attached device whose usage you want to measure and charge for, or a monthly software subscription accounts. The job deletes records where possible and obfuscates data where it is not possible to delete records. Certain data cannot be deleted (e.g. usage The consumption of services, for example a subscriber using call minutes.) as legally there is a requirement for store this a certain period of time.

  This job derives a calculated purge date based on how long data should be retained before it can be purged ‐ the Months to Retain parameter. The calculated purge date is worked out by deducting this number of months from the current date. This parameter is optional. If you do not provide a value, a default value of six month is used. Only subscriptions who have terminated on or before the calculated purge date will be considered by the job.

  This is a scheduled job. This job can be scheduled to run daily; however, it is more likely that monthly or quarterly executions will be sufficient.

• Direct Debit Purge

  This job removes direct debit information that is no longer in use, that is, cancelled. This job derives a calculated purge date based on how long data should be retained before it can be purged ‐ the Months to Retain parameter. Only data from accounts created on or before the calculated purge date will be removed and no archiving takes place prior to the deletion of data. This is a scheduled job. This job can be scheduled to run daily; however, it is more likely that monthly or quarterly executions of this job will be sufficient.

• Interface Purge Job

  This job purges transaction data that has been successfully committed to CMP. The job accepts a parameter for number of Days to Retain. The calculated purge date is worked out by deducting this number of days from the current date. Only data dated on or before the calculated purge date is purged. Any transaction data prior to the retention period will be permanently removed. Each invocation of the job produces a summary audit of transaction data removed. This is a scheduled job.

• Refund Purge

  This job removes refund information that is no longer in use, that is, those refunds with a status of cancelled, complete or rejected. This job derives a calculated purge date based on how long data should be retained before it can be purged ‐ the Months to Retain parameter. Only data from accounts created on or before the calculated purge date will be removed and no archiving takes place prior to the deletion of data. This is a scheduled job. This job can be scheduled to run daily; however, it is more likely that monthly or quarterly executions of this job will be sufficient.

For more information on jobs, see the CMP 8.1 Batch Jobs and JSON JavaScript Object Notation. JSON is a lightweight format for storing and transporting data, often used when data is sent from a server to a web page. Schemas Guide. Alternatively, in the Administration Console An operations web console that allows batch jobs to be scheduled, run manually and monitored. The console also provides for viewing and modification of business and user applicable system configuration., navigate to Daily Operations > Jobs. Click any job in the Jobs List for more details.

Currently, no daemons are associated with Purge jobs.

The following probes can be run against Purge jobs:

Stage	Category	Name	Type	Description
Batch	Account Purge	Completed	Alert	This alert probe returns the number of times the Account Purge job has run today. A value of zero indicates the job has not run today and an alert will be sent to the recipients configured for this probe.
Batch	Address Purge	Completed	Alert	This alert probe returns the number of times the Address Purge job has run today. A value of zero indicates the job has not run today and an alert will be sent to the recipients configured for this probe.
Batch	Consumer Purge	Completed	Alert	This alert probe returns the number of times the Consumer Purge job has run today. A value of zero indicates the job has not run today and an alert will be sent to the recipients configured for this probe.
Batch	Direct Debit Purge	Completed	Alert	This alert probe returns the number of times the Direct Debit Purge job has run today. A value of zero indicates the job has not run today and an alert will be sent to the recipients configured for this probe.
Batch	Payment Card Purge	Completed	Alert	This alert probe returns the number of times the Card Detail Purge job has run today. A value of zero indicates the job has not run today and an alert will be sent to the recipients configured for this probe.
Batch	Refund Purge	Completed	Alert	This alert probe returns the number of times Refund Purge job has run today. A value of zero indicates the job has not run today and an alert will be sent to the recipients configured for this probe.
Batch	Interface Purge	Completed	Alert	Alert probe that returns the number of workflows that have ended up with a processing error today. If the value returned by this query is above the threshold, then an alert is sent to the recipients configured on this probe.

 

For more information on probes, in the Administration Console, navigate to Daily Operations > Probes. Click any probe In the Administration Console architecture, a mechanism which allows for the execution of predefined queries and for the comparison of the results of those queries against pre-configured targets. Probes can be reviewed and managed via the Admin Console. in the Probes List for more details.