Remote feature activator feature extraction

• US 7,681,245 B2
• Filed: 08/30/2002
• Issued: 03/16/2010
• Est. Priority Date: 08/30/2002
• Status: Expired due to Fees

• Current Assignee: Avaya Incorporated
• Original Assignee: Avaya Incorporated
• Inventors: Serkowski, Robert J., Walker, William T., Levy, Leslie, Lourenco, Mary K., Lieou, Bruce G.
• Primary Examiner(s): Ly, Cheyne D
• Application Number:
  US10/232,906
• Publication Number:
  US 20040044631A1
• Time in Patent Office: 2,755 Days
• Field of Search: 707/1, 707/3, 726/2, 726/26, 726/30, 705/59
• US Class Current: 726/30
• CPC Class Codes: G06F 21/10 Protecting distributed programs or content, e.g. vending or licensing of copyrighted material protection in video systems or pay television H04N7/16 ; Digital rights management [DRM]

Abstract

A database record controls a license to use a computational component. An input receives an order identifier associated with an order related to a computational component and an interface retrieves order information associated with the identifier. The order information comprises at least one material code. A material code mapping agent compares the material code with at least one material code mapping table to identify corresponding computational component information associated with the material code. In another configuration, a transaction record includes first information associated with the order, the order relates to at least a first computational component and/or feature thereof, a configuration file includes second information different from the first information, the configuration file relates to at least one telecommunication switch/server, and a configuration file processing agent compares some of the first information with some of the second information to form a system record having both first and second information.

Claims

1. A method, comprising:

(a) providing a configuration file relating to at least one of a telecommunication switch and server, the configuration file setting forth an existing configuration of the at least one of a telecommunication switch and server, wherein the providing step (a) comprises;

(A1) receiving current configuration information from the at least one of a telecommunication switch and server, the configuration information relating to at least one of a capacity and a first set of operational features; and

(A2) forming the configuration file from the received current configuration information;

(b) providing a transaction record comprising first information associated with an order, the order relating to at least a first computational component and/or operational feature thereof, the at least a first computational component and/or operational feature thereof to upgrade and/or replace the at least one of a switch and server, the configuration file comprising second information different from the first information, wherein at least some of the first and second information differs regarding a selected one of a capacity and operational feature; and

(c) merging, by a processor, at least some of the first information with at least some of the second information by applying a set of rules to reconcile the difference and form a license file comprising both first and second information and wherein the license file is for the operation of the at least a first computational component and/or operational feature thereof.

2. The method of claim 1, wherein the at least one of a capacity and first set of operational features is the first set of operational features, wherein, in the forming step (A2), the first set of operational features is contained in a translation file and the first set of operational features is mapped to a second set of operational features in the configuration file, wherein the providing step (a) is performed before upgrade and/or replacement by the at least a first computational component and/or operational feature thereof and wherein the providing step (a) comprises:

(A3) determining if at least one of the following statements is true;

(i) the configuration file is valid,

(ii) a serial number in the configuration file is contained in another configuration file for a different switch and/or server,

(iii) the serial number in the configuration file is valid, and

(iv) a platform type in the configuration file matches the platform type in the transaction record, the platform type corresponding to the at least one of a telecommunication switch and server; and

(A4) in response to the at least one of the following statements not being true, rejecting the configuration file, the configuration file comprising a plurality of platform type, serial number, product identifier, software release, and feature code.

3. The method of claim 2, wherein, in step (c), a system record is created and wherein the first information comprises a platform type and the merging step (c) comprises:

(C1) using the platform type in the first information to verify the system record when the second information does not include a platform type and further comprising;

(C2) populating the transaction record with the first information by converting an order record comprising material codes to the corresponding first information, the first information comprising a plurality of platform type, module type, application, software release, and feature code.

4. The method of claim 1, wherein the merging step (c) comprises:

(C1) determining whether selected first information is associated with a first, second or third type of operational feature and the set of rules comprising the following;

(i) in response to the selected first information being associated with the first type of operational feature and, in response to the configuration file indicating that the first type of operational feature is available for use, using the selected first information in a right-to-use field in the license file;

(ii) in response to the selected first information being associated with the second type of operational feature and, in response to the second information not containing the second type of operational feature, using the selected first information in right-to-use, setting, and range fields in the license file; and

(iii) in response to the selected first information being associated with the third type of operational feature and, in response to the second information not containing the third type of operational feature, using the selected first information in right-to-use, setting, and range fields in the license file.

5. The method of claim 1, wherein the transaction record is derived from an order record, wherein the order record comprises a plurality of an order number, purchasing customer information, a purchased product quantity, a material code corresponding to the purchased product, and a description of the purchased product, wherein the configuration information comprises a plurality of at least one of a platform identifier, a platform type, a software version, a serial number, operational feature information, and a duplication indicator, and wherein the license file comprises system identifier, purchasing customer information, platform type, serial number, platform identifier, application name, software version, expiration date, and operational feature information.

6. The method of claim 1, wherein the merging step (c) comprises:

(C1) determining whether the configuration information is associated with a first, second or third type of operational feature and wherein the set of rules comprise;

(i) in response to the configuration information being associated with the first type of operational feature and, in response to the configuration file indicating that the first type of operational feature is available for use, using the configuration information in the configuration file to generate the license file;

(ii) in response to the configuration information being associated with the second type of operational feature, using the configuration information in the configuration file to generate the license file; and

(iii) in response to the configuration information being associated with the third type of operational feature, using the configuration information in the configuration file to generate the license file.

7. The method of claim 1, wherein the set of rules comprise:

(i) for a selected first Type I operational feature in the configuration file, in response to the selected first Type I operational feature having a setting in the configuration file of ON, adding the corresponding first Type I operational feature keyword and associated information to a right to use list in the license file and setting a setting field in the license file to ON;

(ii) for a selected second Type I operational feature in the configuration file, in response to the selected second Type I operational feature having a setting in the configuration file of OFF, setting a setting field in the license file to OFF when the second Type I operational feature is in the transaction record;

(iii) for a selected third Type II operational feature in the configuration file, adding the corresponding third Type II operational feature keyword and associated information to the right to use list in the license file and, in response to a corresponding operational feature setting in the configuration file being in a value operational feature range, setting a operational feature value setting in the license file to the corresponding operational feature setting in the configuration file and, in response to the corresponding operational feature setting in the configuration file not being in the value operational feature range, setting the operational feature value setting in the license file to a value in the value operational feature range;

(iv) for a selected fourth Type II operational feature not in the configuration file, determining whether the fourth Type II operational feature relates to a single capacity value or a range of capacity values or does not have a corresponding numeric setting, and, in response to the fourth Type II operational feature having a single capacity value, setting the operational feature value setting to a value in the transaction record plus the single capacity value in the configuration file and, in response to the fourth Type II operational feature having a range of capacity values, setting the operational feature value setting to a corresponding value in the configuration file when the corresponding is in the range of capacity values, and, in response to the fourth Type II operational feature having no corresponding numeric setting, ignoring the fourth Type II operational feature information in the configuration file;

(v) for a selected fifth Type III operational feature in the configuration file and transaction record, setting a range field in the license file to a current value plus a corresponding value in the configuration file; and

(vi) for a selected sixth Type III operational feature in the configuration file and not in the transaction record, adding the sixth Type III operational feature to the license file and setting the range field to a corresponding value in the configuration file.

8. A system, comprising:

a transaction record comprising first information associated with an order, the order relating to at least a first computational component and/or operational feature thereof;

means for receiving current configuration information from at least one of a telecommunication switch and server and forming a configuration file from the received current configuration information, wherein the current configuration information comprises at least one of a capacity and first set of operational features;

the configuration file comprising second information different from the first information, the configuration file relating to an existing current configuration of the at least one of a telecommunication switch and server, the at least a first computational component and/or operational feature thereof to upgrade and/or replace the at least one of a telecommunication switch and server, wherein at least some of the first and second information is in conflict regarding a selected operational feature;

means for comparing at least some of the first information with at least some of the second information and applying a set of rules to reconcile the conflict and form a system record comprising both first and second information; and

means for generating a license file using the system record, the license file being for the operation of the at least a first computational component and/or operational feature thereof and comprising first and second information.

9. The system of claim 8, wherein the at least one of a capacity and first set of operational features is the first set of operational features, wherein the first set of operational features is contained in a translation file and the first set of operational features is mapped to a second set of operational features in the configuration file, wherein the configuration file is formed before upgrade and/or replacement by the at least a first computational component and/or operational feature thereof, wherein the at least one of a telecommunication switch and server has a corresponding platform type, and wherein the comparing means determines whether at least one of the following statements is true:

(i) the configuration file is valid,

(ii) a serial number in the configuration file is contained in another configuration file for a different switch and/or server,

(iii) the serial number in the configuration file is valid, and

(iv) the platform type in the configuration file matches the platform type in the transaction record and, in response to the at least one of the following statements not being true, rejects the configuration file, the configuration file comprising a plurality of platform type, serial number, product identifier, software release, and operational feature code.

10. The system of claim 9, wherein the first information comprises a platform type and the comparing means uses the platform type in the first information to verify a system record when the second information does not include a platform type and further comprising:

material code mapping means for populating the transaction record with the first information by converting an order record comprising material codes to the corresponding first information, the first information comprising a plurality of platform type, module type, application, software release, and operational feature code.

11. The system of claim 8, further comprising means for receiving configuration information from the at least one of a telecommunication switch and server and forming the configuration file from the received configuration information, wherein, in the forming step, the configuration information comprises a first set of operational features that is mapped to a corresponding second set of the operational features.

12. The system of claim 11, wherein the transaction record is derived from an order record, wherein the order record comprises a plurality of an order number, purchasing customer information, a purchased product quantity, a material code corresponding to the purchased product, and a description of the purchased product, wherein the configuration information comprises a plurality of at least one of a platform identifier, a platform type, a software version, a serial number, operational feature information, and a duplication indicator, and wherein the system record comprises system identifier, purchasing customer information, platform type, serial number, platform identifier, application name, software version, expiration date, and operational feature information.

13. The system of claim 11, wherein the forming means performs the steps of:

determining whether the configuration information is associated with a first, second or third type of operational feature and applying the set of rules as follows;

in response to the configuration information being associated with the first type of operational feature and, in response to the configuration file indicating that the first type of operational feature is available for use, using the configuration information in the configuration file to generate the license file;

in response to the configuration information being associated with the second type of operational feature, using the configuration information in the configuration file to generate the license file; and

in response to the configuration information being associated with the third type of operational feature, using the configuration information in the configuration file to generate the license file.

14. A system, comprising:

a transaction record comprising first information associated with an order, the order relating to a first computational component and the first information defining a first configuration of the first computational component, the first computational component upgrading anchor replacing at least one of a telecommunication switch and server;

a configuration file comprising second information different from the first information, the configuration file defining an existing current first configuration of the at least one of a telecommunication switch and server, wherein the configuration file defines the first configuration of the at least one of a telecommunication switch and server before the at least one of a telecommunication switch and server is upgraded and/or replaced by the first computational component and wherein at least some of the first and second information is in conflict regarding a selected operational feature;

a configuration file processing agent operable to compare at least some of the first information with at least some of the second information and apply a set of rules to reconcile the conflict and form a system record comprising both first and second information, the system record defining a second configuration of the first computational component, the first and second configurations being non-identical; and

a feature activator operable to generate a license file using the system record, the license file being for the operation of the first computational component and comprising first and second information.

15. The system of claim 14, wherein the second information relates to at least one of a capacity and a set of operational features and wherein the at least one of a telecommunication switch and server has a corresponding platform type and the system record generating agent is operable to (a) determine whether at least one of the following statements is true:

(i) the configuration file is valid,

(ii) a serial number in the configuration file is contained in another configuration file for a different switch and/or server,

(iii) the serial number in the configuration file is valid, and

(iv) a platform type in the configuration file matches the platform type in the transaction record and (b), in response to the at least one of the following statements not being true, reject the configuration file, the configuration file comprising a plurality of platform type, serial number, product identifier, software release, and operational feature code.

16. The system of claim 15, wherein the first information comprises a platform type and the configuration file processing agent is operable to use the platform type in the first information to verify a system record when the second information does not include a platform type and further comprising:

material code mapping agent operable to populate the transaction record with the first information by converting an order record comprising material codes to the corresponding first information, the first information comprising a plurality of platform type, module type, application, software release, and operational feature code.

17. The system of claim 14, wherein the system record generating agent is operable to (a) determine whether selected first information is associated with a first, second or third type of operational feature;

and (b) apply the set of rules as follows;

in response to the selected first information being associated with the first type of operational feature and, in response to the switch configuration file indicating that the first type of operational feature is available for use, use the selected first information in a right-to-use field in the system record;

in response to the selected first information being associated with the second type of operational feature and, in response to the second information not containing the second type of operational feature, use the selected first information in right-to-use, setting, and range fields in the system record; and

in response to the selected first information being associated with the third type of operational feature and, in response to the second information not containing the third type of operational feature, use the selected first information in right-to-use, setting, and range fields in the system record.

18. The system of claim 14, further comprising an extraction tool and a configuration file processing agent collectively operable to receive configuration information contained in a translation file from the at least one of a telecommunication switch and server and form the switch configuration file from the received configuration information, wherein, to form the configuration file is mapped to a second set of the operational features.

19. The system of claim 18, wherein the transaction record is derived from an order record, wherein the order record comprises a plurality of an order number, purchasing customer information, a purchased product quantity, a material code corresponding to the purchased product, and a description of the purchased product, wherein the configuration information comprises a plurality of at least one of a platform identifier, a platform type, a software version, a serial number, operational feature information, and a duplication indicator, and wherein the system record comprises system identifier, purchasing customer information, platform type, serial number, platform identifier, application name, software version, expiration date, and operational feature information.

20. The system of claim 18, wherein the extraction tool is operable to (a) determine whether the configuration information is associated with a first, second or third type of operational feature;

and (b) apply the set of rules as follows;

in response to the configuration information being associated with the first type of operational feature and, in response to the configuration file indicating that the first type of operational feature is available for use, use the configuration information in the configuration file to generate the license file;

in response to the configuration information being associated with the second type of operational feature, use the configuration information in the configuration file to generate the license file; and

in response to the configuration information being associated with the third type of operational feature, use the configuration information in the configuration file to generate the license file.

21. A method, comprising:

(a) providing a configuration file relating to at least one of a telecommunication switch and server, the configuration file setting forth an existing configuration of the at least one of a telecommunication switch and server;

(b) providing a transaction record comprising first information associated with an order, the order relating to at least a first computational component and/or feature thereof, the at least a first computational component and/or feature thereof to upgrade and/or replace the at least one of a switch and server, the configuration file comprising second information different from the first information, wherein at least some of the first and second information differs regarding a selected feature; and

(c) merging at least some of the first information with at least some of the second information by applying a set of rules to reconcile the difference and form a license file comprising both first and second information and being for the operation of the at least a first computational component and/or feature thereof, wherein the merging step (c) comprises;

(C1) determining whether selected first information is associated with a first, second or third type of feature and wherein the set of rules comprises the following;

(i) in response to the selected first information being associated with the first type of feature and, in response to the configuration file indicating that the first type of feature is available for use, using the selected first information in a right-to-use field in the license file;

(ii) in response to the selected first information being associated with the second type of feature and, in response to the second information not containing the second type of feature, using the selected first information in right-to-use, setting, and range fields in the license file; and

(iii) in response to the selected first information being associated with the third type of feature and, in response to the second information not containing the third type of feature, using the selected first information in right-to-use, setting, and range fields in the license file.

22. A method, comprising:

(a) providing a configuration file relating to at least one of a telecommunication switch and server, the configuration file setting forth an existing configuration of the at least one of a telecommunication switch and server, wherein the providing step (a) comprises the sub-steps;

(A1) determining if at least one of the following statements is true;

(i) the configuration file is valid,

(ii) a serial number in the configuration file is contained in another configuration file for a different switch and/or server,

(iii) the serial number in the configuration file is valid, and

(iv) a platform type in the configuration file matches the platform type in the transaction record, the platform type corresponding to the at least one of a telecommunication switch and server; and

(A2) in response to the at least one of the following statements not being true, rejecting the configuration file, the configuration file comprising a plurality of platform type, serial number, product identifier, software release, and feature code;

(b) providing a transaction record comprising first information associated with an order, the order relating to at least a first computational component and/or feature thereof, the at least a first computational component and/or feature thereof to upgrade and/or replace the at least one of a switch and server, the configuration file comprising second information different from the first information, wherein at least some of the first and second information differs regarding a selected feature; and

(c) merging at least some of the first information with at least some of the second information by applying a set of rules to reconcile the difference and form a license file comprising both first and second information and being for the operation of the at least a first computational component and/or feature thereof, wherein, in step (c), a system record is created and wherein the first information comprises a platform type and the merging step (c) comprises the sub-steps;

(C1) using the platform type in the first information to verify the system record when the second information does not include a platform type and further comprising;

(C2) populating the transaction record with the first information by converting an order record comprising material codes to the corresponding first information, the first information comprising a plurality of platform type, module type, application, software release, and feature code.

23. A method, comprising:

(a) providing a configuration file relating to at least one of a telecommunication switch and server, the configuration file setting forth an existing configuration of the at least one of a telecommunication switch and server;

(b) providing a transaction record comprising first information associated with an order, the order relating to at least a first computational component and/or feature thereof, the at least a first computational component and/or feature thereof to upgrade and/or replace the at least one of a switch and server, the configuration file comprising second information different from the first information, wherein at least some of the first and second information differs regarding a selected feature; and

(c) merging at least some of the first information with at least some of the second information by applying a set of rules to reconcile the difference and form a license file comprising both first and second information and being for the operation of the at least a first computational component and/or feature thereof, wherein the set of rules comprise;

(i) for a selected first Type I feature in the configuration file, in response to the selected first Type I feature having a setting in the configuration file of ON, adding the corresponding first Type I feature keyword and associated information to a right to use list in the license file and setting a setting field in the license file to ON;

(ii) for a selected second Type I feature in the configuration file, in response to the selected second Type I feature having a setting in the configuration file of OFF, setting a setting field in the license file to OFF when the second Type I feature is in the transaction record;

(iii) for a selected third Type II feature in the configuration file, adding the corresponding third Type II feature keyword and associated information to the right to use list in the license file and, in response to a corresponding feature setting in the configuration file being in a value feature range, setting a feature value setting in the license file to the corresponding feature setting in the configuration file and, in response to the corresponding feature setting in the configuration file not being in the value feature range, setting the feature value setting in the license file to a value in the value feature range;

(iv) for a selected fourth Type II feature not in the configuration file, determining whether the fourth Type II feature relates to a single capacity value or a range of capacity values or does not have a corresponding numeric setting, and, in response to the fourth Type II feature having a single capacity value, setting the feature value setting to a value in the transaction record plus the single capacity value in the configuration file and, in response to the fourth Type II feature having a range of capacity values, setting the feature value setting to a corresponding value in the configuration file when the corresponding is in the range of capacity values, and, in response to the fourth Type II feature having no corresponding numeric setting, ignoring the fourth Type II feature information in the configuration file;

(v) for a selected fifth Type III feature in the configuration file and transaction record, setting a range field in the license file to a current value plus a corresponding value in the configuration file; and

(vi) for a selected sixth Type III feature in the configuration file and not in the transaction record, adding the sixth Type III feature to the license file and setting the range field to a corresponding value in the configuration file.

24. A system, comprising:

a transaction record comprising first information associated with an order, the order relating to at least a first computational component and/or feature thereof;

a configuration file comprising second information different from the first information, the configuration file relating to an existing configuration of at least one of a telecommunication switch and server, the at least a first computational component and/or feature thereof to upgrade and/or replace the at least one of a switch and server, wherein at least some of the first and second information is in conflict regarding a selected feature;

means for comparing at least some of the first information with at least some of the second information and applying a set of rules to reconcile the conflict and form a system record comprising both first and second information, wherein the at least one of a telecommunication switch and server has a corresponding platform type, wherein the first information comprises platform type and wherein the comparing means determines whether at least one of the following statements is true;

(i) the configuration file is valid,

(ii) a serial number in the configuration file is contained in another configuration file for a different switch and/or server,

(iii) the serial number in the configuration file is valid, and

(iv) the platform type in the configuration file matches the platform type in the transaction record and, in response to the at least one of the following statements not being true, rejects the configuration file, the configuration file comprising a plurality of platform type, serial number, product identifier, software release, and feature code, wherein the comparing means uses the platform type in the first information to verify the system record when the second information does not include a platform type;

means for generating a license file using the system record, the license file being for the operation of the at least a first computational component and/or feature thereof and comprising first and second information; and

material code mapping means for populating the transaction record with the first information by converting an order record comprising material codes to the corresponding first information, the first information comprising a plurality of platform type, module type, application, software release, and feature code.

25. A system, comprising:

a transaction record comprising first information associated with an order, the order relating to at least a first computational component and/or feature thereof;

a configuration file comprising second information different from the first information, the configuration file relating to an existing configuration of at least one of a telecommunication switch and server, the at least a first computational component and/or feature thereof to upgrade and/or replace the at least one of a switch and server, wherein at least some of the first and second information is in conflict regarding a selected feature;

means for comparing at least some of the first information with at least some of the second information and applying a set of rules to reconcile the conflict and form a system record comprising both first and second information, wherein the comparing means performs the functions of;

determining whether selected first information is associated with a first, second or third type of feature; and

applying the set of rules as follows;

in response to the selected first information being associated with the first type of feature and, in response to the switch configuration file indicating that the first type of feature is available for use, using the selected first information in a right-to-use field in the system record;

in response to the selected first information being associated with the second type of feature and, in response to the second information not containing the second type of feature, using the selected first information in right-to-use, setting, and range fields in the system record; and

in response to the selected first information being associated with the third type of feature and, in response to the second information not containing the third type of feature, using the selected first information in right-to-use, setting, and range fields in the system record; and

means for generating a license file using the system record, the license file being for the operation of the at least a first computational component and/or feature thereof and comprising first and second information.

26. The system of claim 25, wherein the transaction record is derived from an order record, wherein the order record comprises a plurality of an order number, purchasing customer information, a purchased product quantity, a material code corresponding to the purchased product, and a description of the purchased product, wherein the configuration information comprises a plurality of at least one of a platform identifier, a platform type, a software version, a serial number, feature information, and a duplication indicator, and wherein the system record comprises system identifier, purchasing customer information, platform type, serial number, platform identifier, application name, software version, expiration date, and feature information.

27. A system, comprising:

a transaction record comprising first information associated with an order, the order relating to at least a first computational component and/or feature thereof, the at least a first computational component and/or feature thereof upgrading and/or replacing at least one of a telecommunication switch and server;

a configuration file comprising second information different from the first information, the configuration file relating to an existing configuration of the at least one of a telecommunication switch and server, wherein at least some of the first and second information is in conflict regarding a selected feature;

a configuration file processing agent operable to compare at least some of the first information with at least some of the second information and apply a set of rules to reconcile the conflict and form a system record comprising both first and second information, wherein the configuration file processing agent is operable to (a) determine whether selected first information is associated with a first, second or third type of feature; and

(b) apply the set of rules as follows;

in response to the selected first information being associated with the first type of feature and, in response to the switch configuration file indicating that the first type of feature is available for use, use the selected first information in a right-to-use field in the system record;

in response to the selected first information being associated with the second type of feature and, in response to the second information not containing the second type of feature, use the selected first information in right-to-use, setting, and range fields in the system record; and

in response to the selected first information being associated with the third type of feature and, in response to the second information not containing the third type of feature, use the selected first information in right-to-use, setting, and range fields in the system record; and

a feature activator operable to generate a license file using the system record, the license file being for the operation of the at least a first computational component and/or feature thereof and comprising first and second information.

28. A system, comprising:

a transaction record comprising first information associated with an order, the order relating to at least a first computational component and/or feature thereof, the at least a first computational component and/or feature thereof upgrading and/or replacing at least one of a telecommunication switch and server, wherein the first information comprises a platform type;

a configuration file comprising second information different from the first information, the configuration file relating to an existing configuration of the at least one of a telecommunication switch and server, wherein at least some of the first and second information is in conflict regarding a selected feature;

a configuration file processing agent operable to compare at least some of the first information with at least some of the second information and apply a set of rules to reconcile the conflict and form a system record comprising both first and second information, wherein the at least one of a telecommunication switch and server has a corresponding platform type and the processing agent determines whether at least one of the following statements is true;

(i) the configuration file is valid,

(ii) a serial number in the configuration file is contained in another configuration file for a different switch and/or server,

(iii) the serial number in the configuration file is valid, and

(iv) a platform type in the configuration file matches the platform type in the transaction record and, in response to the at least one of the following statements (i)-(iv) not being true, rejects the configuration file, the configuration file comprising a plurality of platform type, serial number, product identifier, software release, and feature code, wherein the configuration file processing agent uses the platform type in the first information to verify the system record when the second information does not include a platform type;

a feature activator operable to generate a license file using the system record, the license file being for the operation of the at least a first computational component and/or feature thereof and comprising first and second information; and

material code mapping agent operable to populate the transaction record with the first information by converting an order record comprising material codes to the corresponding first information, the first information comprising a plurality of platform type, module type, application, software release, and feature code.