TARIFF MANAGEMENT DEPLOYMENT AUTOMATION

• US 20100064171A1
• Filed: 09/04/2009
• Published: 03/11/2010
• Est. Priority Date: 09/05/2008
• Status: Abandoned Application

• Current Assignee: Accenture Global Services Limited (Accenture PLC)
• Original Assignee: Accenture Global Services GmbH (Accenture PLC)
• Inventors: Wong, Ming Hon, How, Adrian Envin, Kua, Jasmine Mei Ping, Lau, Kin Yip
• Application Number:
  US12/554,580
• Publication Number:
  US 20100064171A1
• Time in Patent Office: Days
• US Class Current: 714/15
• CPC Class Codes: G06Q 10/06 Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling

Abstract

A method for an operator to deploy tariff and/or billing configurations represented by computer program code, the deployment being effected by operation of a user interface, the method including the steps of the operator identifying at least one configuration to be deployed, selecting the at least one configuration by use of the user interface, and associating the at least one configuration with at least one environment in which the computer program code representing the configuration must be executed to effect the configuration.

Claims

1. A method for an operator to deploy a tariff and/or billing configuration for a tarrif and/or billing plan represented by computer program code, the deployment being effected by operation of a user interface, the method comprising:

identifying at least one configuration to be deployed;

selecting the at least one configuration by use of the user interface; and

associating the at least one configuration with at least one environment in which the computer program code representing the configuration must be executed to effect the configuration.

2. A method according to claim 1 including the operator committing the proposed deployment for execution wherein the computer program code representing the at least one configuration is incorporated for execution in the at least one environment to which the configuration has been associated.

3. A method according to claim 2 including recording the order of the files entered by the operator for the proposed deployment for subsequent execution of the files in the same order as entry when executing the deployment.

4. A method according to claim 3 including checking the proposed deployment for errors as compared with a set of pre-determined rules prior to commotting a proposed deployment for execution.

5. A method according to claim 3 including reporting any identified errors to the operator.

6. A method according to either claim 4 including reversing a proposed deployment in the event that errors are located wherein the reversal of a deployment includes extracting any computer program code representing a configuration from any environments into which the computer program code has been incorporated for subsequent execution.

7. A method according to claim 6 wherein the record of the order in which the operator entered files for the proposed deployment is accessed and during reversal of the proposed deployment, the files containing the computer instruction code representing the configurations are extracted in the reverse order as compared with their recorded entry by the operator.

8. A method according to claim 3 where, in the event that a file is determined to cause an error during execution of the deployment, the execution is halted and no further files are executed.

9. A method according to claim 1 including validating the operator'"'"'s access rights regarding the environments that the operator is authorised to edit.

10. A method according to claim 9 wherein the operator is provided with a list of the environments for which they have access and editing rights.

11. A method according to claim 3 wherein the comparison of a proposed deployment with pre-determined rules comprises any one or more of the following:

a comparison to determine whether the operator has sufficient access rights to effect the proposed deployment;

a comparison to determine whether any conflicts in configuration dependencies exist;

a comparison to determine whether any unacceptable characters are contained in any fields; and

/or

a comparison to determine whether any unacceptable associations are proposed.

12. A method according to claim 1 including determining whether the deployment represents a new deployment or an update to an existing deployment.

13. A method according to claim 1 including assigning the proposed deployment a unique identification No.

14. A method according to claim 13 including checking the environments to determine whether the proposed unique identification No has previously been assigned to a configuration.

15. A method according to claim 1 wherein the user interface is a graphical user interface and the at least one configuration and the at least one environment are represented as graphical objects.

16. A method according to claim 1 wherein the user interface includes a tab based menu arrangement.

17. A system for deploying a tariff and/or billing configuration for a tariff and/or billing plan represented by computer program code, the system comprising:

a computer generated graphical user interface comprising a display upon which configurations and environments are represented as graphical objects;

a selection means enabling an operator to propose a deployment by selecting one or more configurations and associating same with one or more environments; and

a means to commit the proposed deployment and thereby incorporate the computer program code representing the one or more configurations into the one or more environments for subsequent execution.

18. A system according to claim 17 wherein the proposed deployment is committed for execution thereby resulting in the computer program code representing the configurations being incorporated into the respective environments with which the configurations have been associated.

19. A system according to claim 17 wherein a proposed deployment is checked for errors according to pre-determined rules.

20. A system according to claim 19 wherein a proposed deployment is reversed thereby resulting in any computer program code representing one or more configurations being extracted from any environments with which the configuration has been associated.

21. A system according to claim 17 wherein the user interface is a graphical user interface and the configuration and environments are represented as graphical objects.

22. A system according to claim 17 wherein the user interface includes a tab based menu arrangement.