Skip to content

Concepts

Here are some of the key concepts used in Cloudmore and this document:

ConceptDescription
SellerA Seller in Cloudmore is a tenant that wants to offers services to Cloud Service Brokers (Brokers). A seller is typically a Service Provider, ISV, Distributor, Managed Service Provider(MSP), or an Enterprise. The Seller will create and publish services to the Marketplace where a broker can resell to end-users.
Cloud Service Broker (Broker) A Broker is a tenant that wants to offer services to end-users. A Broker can be an MSP, Reseller, Telco, or larger Enterprise organisations. A Broker can provide services from Sellers or add their own services.
Broker AdminBrokers can create users to manage their account. Resellers can also have different roles assigned to a administrator.
OrganisationAn organisation is a tenant that consumes services. An organisation can be a company, business unit, or department. An organisation purchase services that the Broker is offering to them.
UserA User is a person in an organisation that is using a service. Users can also be used for administrative access at all levels in Cloudmore.
ServicesA service is a wrapper that contains the general service marketing information and provisioning action. In Cloudmore, services are either provided from a Seller, set up at the Cloud Service Broker level, or provided by Cloudmore as a “pre-integrated” service. Any service set up by the Seller or Cloud Service Broker is known as a Custom Service.
Product / Service Plan A Product / Service Plan is the actual item the organisation buys. A product has a name, item code, price, and subscription and cancellation rules. A service may have one or several products.
AddonsAddons are products offered together with another product. An addon will have a name, item code, and price details. An addon will follow the same subscription and cancelation rules as the product.
Custom Properties Custom properties can be created and used to capture or store additional information. Custom properties can be text fields, dropdowns, or checkboxes and can be marked as mandatory. Custom properties can be created at the following levelsBrokerOrganisationSeller ServiceSeller ProductBroker Product
SubscriptionA subscription is created under a service. The subscription will contain one (1) product and optionally addons. The subscription terms will be based on the product, if the product is an annual subscription with monthly payment, those properties will make up the terms of the subscription.
MarketplaceThe Marketplace is where a Cloud Service Broker finds new services that they want to resell. Services are presented with marketing information and may also have an associated agreement. After adding a service from the Marketplace, the service will be shown in the Services and is ready for resell.
E-store The E-store is where organisations find new services to buy. After adding the service from the E-store, the organisation can create subscriptions and use the service.
Approval Process (AP) Approval Process can be enabled per organisation. When active, any purchase, either new or change of an existing subscription, will generate an approval request that needs to be approved by the Cloud Service Broker. An approval trigger amount may also be specified to allow purchases below a certain threshold while purchases above the threshold would trigger the Approval Process.
Subscription PeriodThe subscription period defines how many months the subscription will be valid for. Choices are:Monthly12 months24 months36 months48 months60 months
Payment Frequency and Billing Interval The payment frequency defines how often payment should happen. The frequency can either be monthly, quarterly, or yearly. The payment frequency can be aligned with the subscription period or a shorter value. For instance, an annual subscription may be paid monthly. In billing reports, the payment frequency may be referred to as a billing interval. 
Billing DateThe date when billing data is generated. Each service has its billing date either set in Cloudmore or decided by the vendor. On the billing date, billing data for the service will be generated and stored.