Category:PackagePlans - Revision history

Moconnor: Blanked the page

2011-03-27T23:54:34Z

Blanked the page

Moconnor: /* Buy and Sell Plans */

2011-03-25T05:44:38Z

‎Buy and Sell Plans

Moconnor: /* Buy and Sell Plans */

2011-03-24T05:25:49Z

‎Buy and Sell Plans

Moconnor: /* Introduction */

2011-03-24T04:31:51Z

‎Introduction

Moconnor: /* Introduction */

2011-03-24T04:20:31Z

‎Introduction

Moconnor: /* Introduction */

2011-03-24T04:20:07Z

‎Introduction

Moconnor: /* Introduction */

2011-03-24T04:19:55Z

‎Introduction

Moconnor at 04:08, 24 March 2011

2011-03-24T04:08:01Z

Moconnor at 04:07, 24 March 2011

2011-03-24T04:07:15Z

Moconnor: /* Introduction */

2011-03-23T02:07:52Z

‎Introduction

← Older revision		Revision as of 23:54, 27 March 2011
Line 1:		Line 1:
−	~~= '''Package Plans''' =~~

−	~~== '''Introduction''' ==~~
−	~~[[File:PlanMap.png\|thumb\|This image shows the relationships between the various billing components in Cumulus]]~~
−	~~A ''Package Plan'' is a collection of 1 or more [[:Category:ServicePlans\|Service Plans]] grouped together and sold as a Package.~~
−
−	~~Once a package is sold to an account, an instance of this Package is referred to as a ''Package Subscription''.~~
−
−	A Package Plan, at its most basic level consists of an Access Fee (optional), a Setup Fee (optional), a period length - which dictates how far in advance (or arrears) the system will bill for Package Plan Access - and a Service Plan (which denotes, amongst other things, the Service Type being sold).
−
−	~~A Package Plan can be added to a [[PackagePlans/Contract#Package_Pools\|Contract Pool]].~~
−
−	~~A package cannot be subscribed to until it has been linked with a Service Plan.~~
−
−	A real world example of a Package Plan would be a Telephony Service Provider selling a PSTN Telephony service, which is also bundled with an ADSL Broadband service. The SP would have 1 Package Plan, linked with 2 different Service Plans (1 Telephony Service Plan, and 1 DSL Service Plan)
−
−	~~<br style="clear:both" />~~
−
−	~~== '''Buy and Sell Plans''' ==~~
−
−	~~Cumulus is able to manage the relationship between a Wholesaler and SP (both using Cumulus), as well as an SP to End User.~~
−
−	In Cumulus, Package Plans (as well as Service Plans and other associated objects) are ''bought'' from an upstream provider (ie a Wholesaler) and ''sold'' to an End User. To that end, Cumulus has the concept of ''Buy Plans'' and ''Sell Plans'', which are linked together - as usage and Access Fees are rated at each 'level' of Customer (Wholesale, Retail and End User).
−
−	* A ''Buy Plan'' represents the cost price of the service(s).
−
−	* A ''Sell Plan'' is the package actually being sold to the End User.
−
−	~~See the [[PackagePlans/LinkingPackageAndServicePlans\|Linking Package Plans and Service Plans]] article for further information.~~
−
−	~~<br style="clear:both" />~~
−
−	~~== '''Managing Package Plans''' ==~~
−
−	~~Package Plans are managed in Cumulus via '''Packages and Plans > Management > Package Plans'''.~~
−
−	~~[[File:PackagePlans_list.jpg\|500px\|center\|The Package Plan List Screen]]~~
−	~~As with other pages in Cumulus, the Package Plans list provides the ability to do basic searches.~~
−
−	~~<br style="clear:both" />~~
−	~~=== '''Creating a New Package Plan''' ===~~
−
−	~~To create a new Package Plan, browse to Packages and Plans > Management > Package Plans, then click on 'Create New' just beneath 'Search'.~~
−
−	~~The New Package Plan page has a number of elements.~~
−
−	~~Please note that <u>all</u> prices here are GST '''Exclusive''':~~
−
−	~~[[File:PackagePlans_CreateNew.jpg\|500px\|thumb\|The ''New Package Plan'' Page]]~~
−	~~; Name : The internal name for the Package~~
−
−	~~; External Name : This is the External Name for the Package. This is what is printed on customer's invoices if ledger cardlines (eg Package Plan Access Fees), related to this Package, are created.~~
−
−	~~; Description : An optional description for the Package. Internal use only~~
−
−	~~; Reference Name : A way of providing a link to an External 3rd party. This could be represented as the name of a prior billing system if one existed. The field is entirely optional.~~
−
−	~~; Reference Key : A way of providing a link to an External 3rd party. This may be the name of this plan, as it existed in the old system if this were the case. This field is entirely optional.~~
−
−	~~; Buy or Sell : Indicates whether this is a Buy Plan or a Sell Plan. Please see the section entitled ''Buy and Sell Plans'' for further information~~
−
−	; Default Contract Type : Defines the default Contract that will be created when this Package is sold to downstream Customers. For a Contract to appear here, this Package must be part of a Contract Pool. Due to this, when initially creating a Package Plan, only the default Option, 'None' will be available. For more information on contracts, click [[PackagePlans/Contract\|here]].
−
−	~~==== Fee Setup ====~~
−	~~; Setup Fee : The fee charged when a Subscription of this Package is created.~~
−
−	~~; Access Fee : A Rental or Service fee generated each period for the life of the Package Subscription.~~
−
−	Please be aware of both the '''Override''' tick boxes and also the note: ''Where a package access fee is not empty, it will override any service plan access fees that are defined''. It's possible to define a Setup Fee and an Access Fee at both the Package Plan and Service Plan level. If either the Access Fee or Setup Fee (or both) are empty, with the Override button unticked, the system will create the Access Fees based on the attached Service Plans.
−
−	~~If the override button is ticked but no value is entered, please note that $0 will be saved (so effectively, you are creating a $0 plan).~~
−
−	~~; Period Length : The Period length defines how far in advance (or arrears) the system will generate access fees. It also defines how frequently the access fees are created.~~
−
−	; Periods in Advance : determines how many PERIODS in advance the system should generate Access Fees. By default, it's set to 1. In otherwords, generate the access fee for a period when that period starts. In a real world example, if you have a Package that bills monthly and the date is 01/03/2011, it will generate access fees for 01/03/2011 to 31/03/2011 on 01/03/2011.If you set that value to 2 on a plan whose period length is 1 month, it would generate access fees for the period 01/04/2011 to 30/04/2011 on 01/03/2011. This works irrespective of the period length, so if you have 6 or 12 months periods on a Package with a 'Periods in Advance' setting of anything higher than 1, your customers will receive Package Access Fees well in advance of the current Period.
−
−	~~; Pro Rata : Determines whether or not the first set of Access Fees generated for this plan will be pro-rated.~~
−
−	~~; Billing Type : Determines whether or not Package Plan Access Fees are generated at the beginning or the end of a set Period.~~

@@ Line 18: / Line 18: @@
 == '''Buy and Sell Plans''' ==
 Cumulus is able to manage the relationship between a Wholesaler and SP (both using Cumulus), as well as an SP to End User.
 In Cumulus, Package Plans (as well as Service Plans and other associated objects) are ''bought'' from an upstream provider (ie a Wholesaler) and ''sold'' to an End User.  To that end, Cumulus has the concept of ''Buy Plans'' and ''Sell Plans'', which are linked together - as usage and Access Fees are rated at each 'level' of Customer (Wholesale, Retail and End User).
-* A ''Buy Plan'' represents the cost price of the service(s).  A Buy Plan is never sold downstream and, for each Service Type being sold, at least 1 Buy Package must exist.  In the situation where both the Wholesale and Service Provider Accounts exist in Cumulus, the Wholesaler will create a generic Buy Plan for each service type being sold, then create ''Sell'' Packages that get sold to their downstream customers (Service Providers).  At the SP Level, those Sell Plans created upstream then become the SP ''Buy'' Plans, to which the SP can attach their own Sell Plans (that then get sold to their End Users)
+* A ''Buy Plan'' represents the cost price of the service(s).
-** In the situation where the Wholesaler does not exist in Cumulus, The Service Provider will own both the Buy ''and'' Sell Plans - as well as the relationships between them.
 * A ''Sell Plan'' is the package actually being sold to the End User.

← Older revision		Revision as of 05:25, 24 March 2011
Line 27:		Line 27:

	See the [[PackagePlans/LinkingPackageAndServicePlans\|Linking Package Plans and Service Plans]] article for further information.		See the [[PackagePlans/LinkingPackageAndServicePlans\|Linking Package Plans and Service Plans]] article for further information.
−
−	~~[[File:PackagePlans_relationship.jpg\|\|center]]~~

	<br style="clear:both" />		<br style="clear:both" />

@@ Line 3: / Line 3: @@
 == '''Introduction''' ==
 [[File:PlanMap.png|thumb|This image shows the relationships between the various billing components in Cumulus]]
-A ''Package Plan'' is a collection of 1 or more [[:Category:ServicePlans|Service Plans]] grouped together and sold as a Package.  A Package Plan contains a definition of the type and quantity (allowances) of each Service and Product in the package. A package definition will store information such as (but not limited to); recurring fees, Package based discounts and what services (and what maximum quantity) are allowed.
+A ''Package Plan'' is a collection of 1 or more [[:Category:ServicePlans|Service Plans]] grouped together and sold as a Package.
 Once a package is sold to an account, an instance of this Package is referred to as a ''Package Subscription''.

@@ Line 3: / Line 3: @@
 == '''Introduction''' ==
 [[File:PlanMap.png|thumb|This image shows the relationships between the various billing components in Cumulus]]
-A ''Package Plan'' is a collection of [[:Category:ServicePlans|Service Plans]] grouped together and sold as a Package.  A Package Plan contains a definition of the type and quantity (allowances) of each Service and Product in the package. A package definition will store information such as (but not limited to); recurring fees, Package based discounts and what services (and what maximum quantity) are allowed.
+A ''Package Plan'' is a collection of 1 or more [[:Category:ServicePlans|Service Plans]] grouped together and sold as a Package.  A Package Plan contains a definition of the type and quantity (allowances) of each Service and Product in the package. A package definition will store information such as (but not limited to); recurring fees, Package based discounts and what services (and what maximum quantity) are allowed.
 Once a package is sold to an account, an instance of this Package is referred to as a ''Package Subscription''.

@@ Line 7: / Line 7: @@
 Once a package is sold to an account, an instance of this Package is referred to as a ''Package Subscription''.
-A Package Plan, at its most basic level consists of an Access Fee (optional), a Setup Fee (optional,) a period length -  which dictates how far in advance (or arrears) the system will bill for Package Plan Access - and a Service Plan (which denotes, amongst other things, the Service Type being sold).
+A Package Plan, at its most basic level consists of an Access Fee (optional), a Setup Fee (optional), a period length -  which dictates how far in advance (or arrears) the system will bill for Package Plan Access - and a Service Plan (which denotes, amongst other things, the Service Type being sold).
 A Package Plan can be added to a [[PackagePlans/Contract#Package_Pools|Contract Pool]].

@@ Line 26: / Line 26: @@
 * A ''Sell Plan'' is the package actually being sold to the End User.
 [[File:PackagePlans_relationship.jpg||center]]
 <br style="clear:both" />

← Older revision		Revision as of 04:07, 24 March 2011
Line 28:		Line 28:

	[[File:PackagePlans_relationship.jpg\|\|center]]		[[File:PackagePlans_relationship.jpg\|\|center]]
		+
		+	See the [[PackagePlans/LinkingPackageAndServicePlans:Linking Package Plans and Service Plans]] article for further information.

	<br style="clear:both" />		<br style="clear:both" />