Figure RA.11 - RA Trouble Ticket

Revenue Assurance Trouble Ticket ABE entities represent trouble tickets opened to resolve one or several causes (for example, Revenue Assurance Violations) that resulted in a Revenue Assurance KPI not meeting a Revenue Assurance Objective.<br/>Just as the model for controls and KPIs were similar, so are the models for RevenueAssuranceViolations and RevenueAssuranceTroubleTickets as shown in figure RA.11.  There are two primary differences in the two models.<br/>First, a RevenueAssuranceTroubleTicket is a type of TroubleTicket, which in turn is a type of BusinessInteraction.  Therefore, the TroubleTicket inherits the same characteristics from BusinessInteraction as RevenueAssuranceViolation.<br/>Second, RevenueAssurranceViolations may be used in the derivation of a RevenueAssuranceKPI, which then may trigger a RevenueAssuranceTroubleTicket.  For example, if more than “X” number of customers are not billed in a given billing cycle for services used, a trouble ticket is generated.  This KPI is a sum of all the “true” parameters that were RevenueAssuranceControl parameter values representing a single unbilled customer.  For this reason, the RevenueAssuranceViolationSpec may influence the creation of a RevenueAssuranceTroubleTicket via the specification’s association with a RevenueAssuranceTroubleTicketSpec.<br/>