Company: Reliance Jio Infocomm Ltd
Product Title: Rancore Technologies Total Charge (RTTC) System
Product Version: V6.0.2
Frameworx Version: Version 12.0
Information Framework version: Version 12.0
Assessment Completion Date: July 2013
Detailed Certification Report: Rancore Technologies Total Charge (RTTC) System Certification Report
Information Framework Assessment Summary
TM Forum has reviewed and approved the self-assessment of the solution listed here against Information Frameworx (SID) version 12 Domains/Aggregate Business Entities. Each ABE was measured using an Information Framework (SID) conformance scale of 1–7, with 1 being the lowest, 3 being the acceptable minimum, and 7 being the highest level of conformance.
Scope of Assessment – Information Framework Footprint
The following figure illustrates the Information Framework Level 1 ABEs that were presented in scope for the Assessment, and the textual callouts represent the domain areas of the Rancore Technologies Total Charge (RTTC) System that were assessed and support the corresponding SID ABEs.
Information Framework Level 1 ABEs in scope for Rancore Technologies Total Charge (RTTC) System Assessment
Product Conformance Summary – Information Framework
The following graphs provide an overview of the conformance scores granted to the ABEs presented in scope for Rancore Technologies Total Charge (RTTC) System, Information Framework Assessment.
Information Framework – Conformance Result Summary Common Business Entities Domain
Information Framework – Conformance Result Summary Customer, Product & Service Domains
Product Conformance Detailed – Information Framework
The following table provides a more detailed breakdown of the scores awarded with some additional commentary.
Rancore Technologies Total Charge (RTTC) ProductInformation Framework (SID) R12.0 – Conformance Scores |
||
| ABE | Conformance Score | Comment |
| Common Business Entities Domain | ||
| Location/ Location | 7.0 | Core entity, required attributes, dependent entities, required attributes of dependent entities, all attributes of the core entity, all attributes of dependent entities supported. |
| Location/ Geographic Place/ Geographic Place | 3.0 | Core entity + 100% required attributes supported. No dependent entities supported. |
| Party/ Party | 3.1 | Core entity, required attributes, 10% of dependent entities supported. |
| Party/ Contact | 7.0 | Core entity, required attributes, dependent entities, required attributes of dependent entities, all attributes of the core entity, all attributes of dependent entities supported. |
| Policy/ Policy Framework | 3.6 | Core entity, required attributes, 60% of dependent entities supported. |
| Policy/ Policy Structure Entities/ Policy Action Entities | 7.0 | Core entity, required attributes, dependent entities, required attributes of dependent entities, all attributes of the core entity, all attributes of dependent entities supported. |
| Policy/ Policy Structure Entities/ Policy Condition Entities | 7.0 | Core entity, required attributes, dependent entities, required attributes of dependent entities, all attributes of the core entity, all attributes of dependent entities supported. |
| Policy/ Policy Structure Entities/ Policy Statement Entities | 7.0 | Core entity, required attributes, dependent entities, required attributes of dependent entities, all attributes of the core entity, all attributes of dependent entities supported. |
| Policy/ Policy Structure Entities/Policy Value Entities | 7.0 | Core entity, required attributes, dependent entities, required attributes of dependent entities, all attributes of the core entity, all attributes of dependent entities supported. |
| Policy/ Policy Structure Entities/ Policy Variable Entities | 7.0 | Core entity, required attributes, dependent entities, required attributes of dependent entities, all attributes of the core entity, all attributes of dependent entities supported. |
| Root Business Entities/ Root Business Entities | 3.8 | Core entity, required attributes, 80% of dependent entities supported. |
| Root Business Entities/ Characteristic/ Characteristic | 3.7 | Core entity, required attributes, 70% of dependent entities supported. |
| Root Business Entities/ Characteristic/ Characteristic Pricing | 7.0 | Core entity, required attributes, dependent entities, required attributes of dependent entities, all attributes of the core entity, all attributes of dependent entities supported. |
| Usage/ Usage | 7.0 | Core entity, required attributes, dependent entities, required attributes of dependent entities, all attributes of the core entity, all attributes of dependent entities supported. |
| Usage/ Usage Spec | 3.7 | Core entity, required attributes, 70% of dependent entities supported. |
| Users and Roles | 3.0 | Core entity + 100% required attributes supported. No dependent entities supported. |
| Customer Domain | ||
| Applied Customer Billing Rate | 7.0 | Core entity, required attributes, dependent entities, required attributes of dependent entities, all attributes of the core entity, all attributes of dependent entities supported. |
| Customer | 7.0 | Core entity, required attributes, dependent entities, required attributes of dependent entities, all attributes of the core entity, all attributes of dependent entities supported. |
| Customer Bill/ Customer Billing Credit | 7.0 | Core entity, required attributes, dependent entities, required attributes of dependent entities, all attributes of the core entity, all attributes of dependent entities supported. |
| Product Domain | ||
| Product Offering/ Product Offering | 3.1 | Core entity, required attributes, 10% of dependent entities supported. |
| Product Offering/ Product Offering Price | 7.0 | Core entity, required attributes, dependent entities, required attributes of dependent entities, all attributes of the core entity, all attributes of dependent entities supported. |
| Product Offering/ Product Offering Price Rule | 7.0 | Core entity, required attributes, dependent entities, required attributes of dependent entities, all attributes of the core entity, all attributes of dependent entities supported. |
| Product Usage/ Product Usage | 7.0 | Core entity, required attributes, dependent entities, required attributes of dependent entities, all attributes of the core entity, all attributes of dependent entities supported. |
| Product Usage/ Product Usage Spec | 7.0 | Core entity, required attributes, dependent entities, required attributes of dependent entities, all attributes of the core entity, all attributes of dependent entities supported. |
| Service Domain | ||
| Service | 3.7 | Core entity, required attributes, 70% of dependent entities supported. |
| Service/CustomerFacing Service/ CustomerFacing Service | 3.5 | Core entity, required attributes, 50% of dependent entities supported. |
| Service/CustomerFacing Service/ CustomerFacing Service Role | 7.0 | Core entity, required attributes, dependent entities, required attributes of dependent entities, all attributes of the core entity, all attributes of dependent entities supported. |
| Service Specification/ Service Specification | 3.2 | Core entity, required attributes, 20% of dependent entities supported. |
| Service Usage | 7.0 | Core entity, required attributes, dependent entities, required attributes of dependent entities, all attributes of the core entity, all attributes of dependent entities supported. |
Report Misuse:Frameworx conformance is an important part of enabling the communications industry maintains profitability as it migrates to new services and new business models. Gaining the conformance mark represents a significant investment by both suppliers and service providers. If you feel a company is misusing the conformance mark then please let us know at [email protected].
Disclaimer. TeleManagement Forum has conducted no independent testing of the solution for conformance with its frameworks or standards. Such testing has solely been conducted by the supplier or seller of the product and has been self-assessed by the supplier or seller for adherence to the TeleManagement Forum framework or standard in question. Accordingly, under no circumstances will TeleManagement Forum be liable for any direct or indirect damages or any costs or losses resulting from the use or reliance by any party of or upon such certification.