Enterprise License Agreement (ELA) Capacity Plans
- Andy Brook [Plugin People]
- Denny Miller
ELA Capacity Plans
The ELA Capacity Plan upgrades enable multiple Jira instances to share an additional common higher Capacity Plan such that when the local instance Capacity Plan is consumed, there is a large bucket to consume from, reducing overall capacity management and leveraging shared value from discounts for higher level plans. More info found on the Capacity Plans page.
A hosts ELA enrolment can be confirmed by checking the bottom of the JEMHC > Usage screen.
Pricing
Per-instance app subscription costs cover the per-instance Capacity Plan, driven by the active users in the instance.
Pricing for ELA is additional to per-instance subscription and follows existing Capacity Plan pricing. The larger the additional capacity plan, the better value it offers.
ELA’s are not allocated prior to payment. Purchases are final, no refunds.
Term
Minimum term for ELA is 1 year. There is no support for ‘monthly’ subscription ELA’s.
Regions
ELA’s are defined within a region so can only be used for hosts within the same region (ie US or EU).
Usage reset
As with standard Capacity Plans, the ELA usage is cleared on the 1st of each month (00:01).
Upgrading ELA’s
Upgrades to ELA’s follow the same path as for an upgrade to an existing Capacity Plan (credit given for fully unused remaining months against new higher tier). In this situation, a co-term with the original expiry is fine!
Usage Tracking
Enrolled sites continue to have their local usage visualisation with an extra Enterprise plan section at the bottom, below shows the outcome of local host plan being consumed (MSG in this case) and subsequent allocation of usage to the ELA:
Management
Purchasing queries to sales@thepluginpeople.com
Management (additions/removals) via support | support@thepluginpeople.com .
ELA for single instance sites
Each instance has it's own set of users that drive a local instance Capacity Plan allocation. When enrolling an instance with an overarching ELA Capacity Plan, the local instance Capacity Plan will be consumed before the ELA Capacity Plan is used. Data Packs operate at the instance level, would only apply as/when the ELA plan is also consumed.
ELA for multiple instances
Multiple Instances operate in the same way as singe instances (above). Additionally, instances may be licensed through Atlassians ‘multi-instance’ (What are the benefits of multiple instances? | Atlassian Support) pricing but is not required for JEMHC ELA’s.
Current Limitations
This feature is new, is functional but some areas do not yet fully align as we would want, outstanding work is listed below:
Notifications
TODO: Hosts with an ELA continue to receive notices about per-instance Capacity Plan usage.
TODO: We don’t yet have ‘usage’ notifications covering ELA plans (partial or consumed)
TODO: Host add/remove/unlicense notification to the group.
TODO: Notification about ELA plan level change
TODO: Monthly usage notifications don’t yet contain ELA details
Allocation of use
TODO: Currently, when local host usage exceeds local capacity plan, usage will be deducted from the ELA plan. This can result in excess DATA being left on the host capacity plan when MSG volume drives ELA usage. Datapacks do this better, it is on our roadmap to mirror this behaviour for ELA use.
Changing plan
Changing plan to higher/lower can only occur on 1st of a month to maintain usages chart function.