• Multiple Subscription definitions can exist in the system, but each one should have a unique name and alternative code
• Only one active Subscription  definition can exist at any given time

• If no active Subscription definition exists, then no Subscription can be created

• Mandatory Fields must be defined
• Name and alternative code must be uniqueAlternative Code must beunique

• Not Applicable

• Mandatory Fields must be defined
• Name and alternative code must be uniqueAlternative Code must beunique

• Not Applicable

• Not Applicable

• Cannot be deleted if its the active definition

• 'Active' Definition

Subscription

Restrictions control the number of

Subscriptions that can be owned by the same

Accounts Receivable, based on a set of rules. The criteria that can be used to build each rule include the following:

• Subscription Criteria
  • Subscription Type

• • Subscription Life Cycle State
• Criteria for each Accounts Receivable
  
  • The Accounts Receivable Classification
  • The Accounts Receivable Credit rating
• Maximum Number of Subscriptions: The maximum number of Subscriptions meeting the Subscription Criteria, allowed to be created per Accounts Receivable meeting the Accounts Receivable Criteria

In the following example the System is set to allow:

• 1 Subscription per Accounts Receivable with Employee Classification
• 3 Subscriptions per Accounts Receivable with Residential Classification
• 5 Subscriptions per Accounts Receivable regardless of the account's Classification

Image Added

Service

Restrictions control the number of

Services that can be added either

to one or

all

Subscriptions owned by the same

Accounts Receivable.

• Scope: The scope by which the conditions will be set.
  • "Subscription": The rule will apply to the Services of a single Subscription.
    or
  • "Accounts Receivable":  The rule will apply to the sum of the Services of all the Subscriptions owned by the Accounts Receivable.
• Restrictions:
  • Minimum number of mandatory Services that should exist
  • Maximum number of mandatory

• • Services that should exist.
  • Minimum number of optional

• • Services that should exist.
  • Maximum number of optional

• • Services that should exist

• • .

Service

Dependencies control the

Type of

Services that can co-exist either on a

Subscription or

Subscriptions owned by the same

Accounts Receivable.

• Product or Product Type: Must be either Termed Services or Expenses.
• Scope: The scope by which the conditions will be set.
  • "Subscription": The rule will apply to Services of a single Subscription.
    or
  • "Accounts Receivable": The rule will apply to the Services of all the Subscriptions owned by the Accounts Receivable.
• Type of Prerequisites, can be one of the following:
  • Services (Only Termed Services and Expense are allowed to be added to the list).
  • Service Types (Only Termed Services and Expense are allowed to be added to the list).
  • Traceable Physical Goods.
  • Traceable Physical Good Types.
• Prerequisites: Up to 10 Prerequisites can be added from the same Type. There is also the option to define whether all the specified values or if at least one of the

• values should

• be present.

Service

Restrictions per

Distributor control the number of

Services that can be distributed

by each

Provisioning Distributor.

• Provisioning Distributor: The Provisioning Distributor on which the restrictions should be applied.
• Restrictions:
  
  • Minimum number of mandatory

• • Services that should exist.
  • Maximum number of mandatory

• • Services that should exist.
  • Minimum number of optional

• • Services that should exist.
  • Maximum number of optional

• • Services that should exist

• • .

Service

Dependencies Per Distributor control the

Services that can be distributed on the same

Provisioning Distributor.

• Provisioning Distributor: The Distributor on which the dependency rules should be applied.
• Type of Prerequisites, can be one of the following:
  • Services (Only Termed Services and Expense are allowed to be added to the list).
  • Service Types (Only Termed Services and Expense are allowed to be added to the list).
• Prerequisites: Up to 10 Prerequisites can be added from the same Type. There is also the option to define whether all the specified values or if at least one of the

• values should

• be present.

Tiers are directly related to the Subscription Action 'Swap Services' and determine the swaps that can take place between Subscription Services and provides information on the Type of modification (i.e. if it

constitutes an upgrade

or downgrade

).

Subscription Service Tiers aretwo dimensional; the first dimension is the

Tier Level and the second dimension is the

Tier Path.

• The

• Path defines a set of

• Subscription Services, which can replace each other. Subscription

• Services can be replaced only by

• other Services under the same

• Path.
• The

• Level characterises the

• replacement (i.e. if it

• constitutes an upgrade or downgrade)

• and

• is defined within each

• Tier Path.

Tier

Paths can be related to a single root

Path, in which case, the System will suggest replacements of Subscription Services belonging to a child

Path, whenever a

Subscription Service of the same Level is replaced.

Example

Based on the

Subscription Service Tiers specified above the following

events can take place:

• A1, A2, A3 can replace each other.
• B1, B2, B3, B4 can replace each other.
• C1, C2 can replace each other.
• Going from A1 to A2 or A3 is considered as a downgrade.
• Going from A3 to A2 or A1 is considered as an upgrade.
• Going from B4 to B5 and vice versa is considered a swap.
• If a

• Subscription has A1, B1 and C1 then a change from A1 to A2 will

• suggest a change from B1 to B2, but it will not

• suggest a change from C1 to C2

• .

Based on the Subscription Service Tiers specified above the following

events cannot take place:

• Subscription

• Services belonging to

• Path 1 cannot replace or be replaced by

• a Subscription Service belonging to

• Path 2 or

• Path 3
• Subscription

• Services belonging to

• Path 2 cannot replace or be replaced by

• a Subscription Service belonging to

• Path 1 or

• Path 3
• Subscription

• Services belonging to

• Path 3 cannot replace or be replaced by

• a Subscription Service belonging to

• Path 1 or

• Path 2

Installed Item Restrictions control the number of Installed Items that can be added either to one or all Subscriptions owned by the same Accounts Receivable.

• Scope: The scope by which the conditions will be set.
  • "Subscription": The rule will apply to Installed Items of a single Subscription.
    or
  • "Accounts Receivable": The rule will apply to the sum of the Installed Items of all the Subscriptions owned by the Accounts Receivable.
• Physical Good Type: The Traceable Physical Good Type on which the restrictions for the number of the Installed Items will be applied.
• Restrictions:
  • Minimum number of Installed Items that should exist per traceable Physical Good Type.
  • Maximum number of Installed Items that should exist per traceable Physical Good Type.

Installed Item Dependencies control the Type of Installed Item that can co-exist either on a Subscription or Subscriptions owned by the same Accounts Receivable.

• Product or Product Type: can only be Traceable Physical Goods.
• Scope: The scope by which the conditions for the selected Product or Product Type will be set.
  • "Subscription": The rule will apply to Physical Goods of a single Subscription.
    or
  • "Accounts Receivable": The rule will apply to the Physical Goods of all the Subscriptions owned by the Accounts Receivable
• Type of Prerequisites, can be one of the following:
  • Traceable Physical Goods
  • Traceable Physical Good Types
• Prerequisites: Up to 10 Prerequisites can be added from the same Type. There is also the option to define whether all the specified values or if at least one of the values should be present.

Installed Item Restrictions per Distributor control the number of Installed Items that can be distributed by each Provisioning Distributor.

• Provisioning Distributor: The Provisioning Distributor on which the restrictions should be applied.
• Physical Good Type: The Traceable Physical Good Type on which the restrictions for the number of the Installed Items will be applied.
  
• Restrictions:
  
  • • Minimum number of Installed Items that should exist per traceable Physical Good Type
    • Maximum number of Installed Items that should exist per traceable Physical Good Type

Installed Item dependencies per Distributor control the type of Installed Items that can be distributed on the same Provisioning Distributor.

• Provisioning Distributor: The Distributor on which dependency rules should be applied.
• Type of Prerequisites can be one of the following
  • Traceable Physical Goods
  • Traceable Physical Good Types
• Prerequisites: Up to 10 Prerequisites can be added from the same Type. There is also the option to define whether all the specified values or if at least one of the values should be present.