Consulting Services/Package Plans/AAPT/Sharing Data Across Services - Revision history

Scarpenter: /* Structure Diagram */

2016-04-08T05:30:50Z

‎Structure Diagram

Scarpenter at 05:30, 8 April 2016

2016-04-08T05:30:25Z

Scarpenter: /* Overview */

2016-04-08T04:01:32Z

‎Overview

Scarpenter: /* Assumptions */

2016-04-08T03:49:16Z

‎Assumptions

Scarpenter at 02:54, 8 April 2016

2016-04-08T02:54:45Z

Scarpenter at 02:42, 8 April 2016

2016-04-08T02:42:34Z

Scarpenter at 02:16, 8 April 2016

2016-04-08T02:16:39Z

Scarpenter: Created page with "This plan is suited for: AAPT IP-Line Not suited for any other data-based service type, however this approach ''may'' be suited to any product where unique service identifier..."

2016-04-08T02:11:05Z

Created page with "This plan is suited for: AAPT IP-Line Not suited for any other data-based service type, however this approach ''may'' be suited to any product where unique service identifier..."

New page

This plan is suited for: AAPT IP-Line

Not suited for any other data-based service type, however this approach ''may'' be suited to any product where unique service identifiers contained in data feed are used to distinguish between the data, the link and the tails.

= Assumptions =

The data allocation must be purchased from AAPT as a '''direct service'''. I.e. The data allocation is dedicated to only this end user customer.

This solution will '''not''' support your customer sharing data from a pool of bandwidth that is shared with other customers, as is sometimes sold by carriers.

= Case Scenario=
A customer has multiple locations, such as offices or retail outlet locations) and needs business grade internet.

Each customer location will be using a tail and maybe on different speeds and technology (NBN, SHDSL, ADSL, Fibre, etc).

The client will be allocated a pool of data by the carrier (500GB, 5TB, etc) to share across these tails. Excess usage rates apply if the customer exceeds their allowance.

= Package Plan Construction =
== Overview ==
Service providers will need to set up:
1. A BUY service plan for the data allowance
Enter your BUY prices from AAPT against this plan.
2. A SELL service plan for the data allowance
Configure data allowance and excess rates (Service Plan > Data Billing).
3. A BUY package plan for the data allowance
Associate your BUY service plan as from step 1 with this plan.
4. A SELL package plan for the data allowance
Associate your SELL service plan with your BUY plan from step 2.
5. A BUY service plan for the tail only
Enter your BUY prices from AAPT against this plan.
6. A SELL service plan for the tail only
Service Plan > Data Billing to be left empty.
7. A BUY package plan for the tail only
Associate your BUY service plan as from step 5 with this plan.
8. A SELL package plan for the data allowance
Associate your SELL service plan with your BUY plan from step 6.
9. Approve all plans ready for sale

@@ Line 91: / Line 91: @@
 = Structure Diagram =
-This diagram shows how the plan structure and configurtation of the services should be in order to bill the customer correctly.
+This diagram shows how the plan structure and configuration of the services should be in order to bill the customer correctly.
 [[file: aapt-ipline-shared-data-service-sub-structure.png]]

@@ Line 31: / Line 31: @@
 = Package Plan Construction =
 == Overview ==
 At a high level, the following steps will need to be completed.
@@ Line 54: / Line 56: @@
 For the service(s) to bill correctly, it is essential they are entered and configured in a very specific way. Follow the steps below to enter and configure the services.
-== Step 1: Create a single subscription to the plan for the data allowance ==
+== Step 1: Create a single subscription for the data allowance ==
-Place an order for the service in the usual way.
+# Place an order for the service and submit it for activation. Select the Package plan that was created for the customer for the data allowance. Preactive package and service subscriptions will be created.
-Be sure to select the Package plan that was created for the end user specifically with the correct data allowance.
+Usage cannot be rated correctly unless:
-When activating the service in Emersion, the '''primary service identifier''' for the data allowance plan must the '6' number from AAPT’s usage file. Usage cannot be rated unless this number is used as the primary service identifier and alternatives cannot be used. Vanity identifiers can be leveraged to display a replacement service identifier on the invoice if that is preferred. The invoice description field can be used to describe the service in more detail on the invoice if needed.
+Vanity identifiers can be leveraged to display a replacement service identifier on the invoice if that is preferred. The '''invoice description field''' can be used to describe the service in more detail on the invoice if desired.
 == Step 2: Create a package subscription group ==
-Nav: Service Subscription > Package Subscription group.
+'''Nav: Service Subscription > Package Subscription group'''.
-Ensure Is primary subscription in a group flag is checked.
+Ensure the '''Is primary subscription in a group''' flag is checked.

@@ Line 47: / Line 47: @@
 # Approve all plans ready for sale
-^^ Only one SELL service plan is needed for all tails belonging to all customers. Customers with multiple tails will have multiple subscriptions to this plan (one subscription per tail). This plan can be used by all customers.
+^^ Only one SELL service plan is needed for all tails across all end users. End users with multiple tails will have multiple subscriptions to this plan (one subscription per tail). This plan can be used by all customers.
 How to create the various objects comprising the Packages and Plans module are part of standard Emersion systems training and not in scope for this article. See the links at the bottom to go to those relevant training sections.

@@ Line 21: / Line 21: @@
 == Assumptions ==
-# This article assumes the service provider is logged into a Retail Service Provider account and their customer is an End User customer.
+# This article assumes the service provider is logged into a Retail Service Provider account and their customer is an End User customer. This article does not apply to wholesale service providers.
 == User Story==

@@ Line 24: / Line 24: @@
 this article does apply to wholesale service providers.
-= User Story=
+== User Story==
 A customer has multiple locations, such as offices or retail outlet locations) and needs business grade internet.
@@ Line 51: / Line 51: @@
 How to create the various objects comprising the Packages and Plans module are part of standard Emersion systems training and not in scope for this article. See the links at the bottom to go to those relevant training sections.

@@ Line 7: / Line 7: @@
 This plan is specifically designed to work with AAPT IP-Line service type. IP-Line is AAPT's business-grade internet product.
-While this article was not written with any other data service type in mind, this approach ''may'' be suited to any product where unique service identifiers (contained in data feed) are used to distinguish between the data, the link and the tails.
+While this article was not written with any other service type in mind, however this approach ''may'' be suited to any data-based service type where unique service identifiers (contained in data feed) are used to distinguish between the data component, the link component and each of the tails.
-How a plan is structured in Emersion will often depend on how service providers want the services to present on the invoice.
+==Prerequisites==
-= Assumptions =
+This article is designed for Cumulus users who:
-The data allocation must be purchased from AAPT as a '''direct service'''. I.e. The data allocation is dedicated to only this end user customer.
+The data allocation must be purchased from AAPT as a '''direct service''', meaning the allocation of data is dedicated to only this end user customer. This solution will '''not''' support your customer sharing data from a pool of bandwidth that is also shared with other customers.
-This solution will '''not''' support your customer sharing data from a pool of bandwidth that is shared with other customers, as is sometimes sold by carriers.
+== Assumptions ==
-= Case Scenario=
+# This article assumes the service provider is logged into a Retail Service Provider account and their customer is an End User customer.
 A customer has multiple locations, such as offices or retail outlet locations) and needs business grade internet.
@@ Line 27: / Line 33: @@
 = Package Plan Construction =
 == Overview ==
-Service providers will need to set up:
+At a high level, the following steps will need to be completed.
-.	A BUY service plan for the data allowance
-Enter your BUY prices from AAPT against this plan.
+# Create a single BUY service plan for the data allowances. Enter your BUY prices against this plan.
-.	A SELL service plan for the data allowance
+# Create a SELL service plan for the data allowance for each customer. If you have one customer with a 3TB allowance and one with a 500GB allowance, you will need two service plans.
-Configure data allowance and excess rates (Service Plan > Data Billing).
+## Configure data allowance and excess rates on the '''Service Plan > Data Billing''' tab.
-.	A BUY package plan for the data allowance
+# Create a BUY package plan for the data allowance. Associate your BUY service plan as from step 1 with this plan.
-Associate your BUY service plan as from step 1 with this plan.
+# Create a SELL package plan for the data allowance. Associate your SELL service plan with your BUY plan from step 2.
-.	A SELL package plan for the data allowance
+# Create a BUY service plan for the tail only. Enter your BUY prices from AAPT against this plan.
-Associate your SELL service plan with your BUY plan from step 2.
+# Create a SELL service plan for the tails^^. For the tails, the '''Service Plan > Data Billing''' tab is to be left empty.
-.	A BUY service plan for the tail only
+# Create a BUY package plan for the tail only.
-Enter your BUY prices from AAPT against this plan.
+# Associate your BUY service plan as from step 5 with this plan.
-.	A SELL service plan for the tail only
+# Create a SELL package plan for the data allowance.
-Service Plan > Data Billing to be left empty.
+# Associate your SELL service plan with your BUY plan from step 6.
-.	A BUY package plan for the tail only
+# Approve all plans ready for sale
 Associate your BUY service plan as from step 5 with this plan.
-.	A SELL package plan for the data allowance
+^^ Only one SELL service plan is needed for all tails belonging to all customers. Customers with multiple tails will have multiple subscriptions to this plan (one subscription per tail). This plan can be used by all customers.
 Associate your SELL service plan with your BUY plan from step 6.
-.	Approve all plans ready for sale
+How to create the various objects comprising the Packages and Plans module are part of standard Emersion systems training and not in scope for this article. See the links at the bottom to go to those relevant training sections.

← Older revision		Revision as of 02:16, 8 April 2016
Line 1:		Line 1:
−	~~This plan is suited~~ for~~: AAPT IP-Line~~	+	== Share Data Across Multiple Services for a Customer ==

		+	This article describes a way to build a plan that will:
		+	* Allow a single data allowance to apply across multiple tails
		+	* Allow users to add and remove tails without affecting the rest of the grouped services.
		+
		+	This plan is specifically designed to work with AAPT IP-Line service type. IP-Line is AAPT's business-grade internet product.
		+
		+	While this article was not written with any other data service type in mind, this approach ''may'' be suited to any product where unique service identifiers (contained in data feed) are used to distinguish between the data, the link and the tails.
		+
		+	How a plan is structured in Emersion will often depend on how service providers want the services to present on the invoice.
	Not suited for any other data-based service type, however this approach ''may'' be suited to any product where unique service identifiers contained in data feed are used to distinguish between the data, the link and the tails.		Not suited for any other data-based service type, however this approach ''may'' be suited to any product where unique service identifiers contained in data feed are used to distinguish between the data, the link and the tails.