BMC Software agreements, audit and compliance covers the standard contracts under which BMC Software licenses its products and the processes BMC uses to check that deployment matches entitlement. BMC publishes its agreements on its legal Agreements page. The page lists the BMC Technology Solutions Master Agreement (TSMA), an information security schedule, a Service Level Agreement, the End User License Agreement (EULA), the Online Trial Agreement, data-processing agreements, regulatory addenda and AI Terms of Use.[4] The TSMA states that a fully executed TSMA supersedes any click-through agreement the customer is asked to accept while using the BMC Offerings.[1] Each Order is “a discrete contract, separate from each other Order”. Terms in an Order prevail over the agreement only if both parties’ authorized representatives execute the Order.[1] For the general concepts, see entitlement and license compliance.
Editions
BMC’s published agreements fall into three groups:
| Agreement | Covers | Version retrieved |
|---|---|---|
| BMC Technology Solutions Master Agreement | On Premises Subscriptions (Attachment A), Subscription Services (Attachment B), Consulting Services (Attachment C)[1] | Last updated 2026-09-09[1] |
| End User License Agreement | Products (object code) licensed by Order, with Support[2] | Last updated 2026-07-29[2] |
| Online Trial Agreement | Temporary licences for trials, proofs of concept and proofs of value[3] | Last updated 2026-01-20[3] |
BMC Helix products use a separate BMC Helix Cloud Services Master Agreement, last updated 2026-03-17. Its structure is similar and it has its own verification and audit clauses.[9]
Metrics
The agreements do not define metrics themselves. The EULA defines Licensed Capacity as “the amount of each Product licensed as established in the Order”, with the Units of Measure and License Restrictions set out in the Order.[2] Under the TSMA, Subscription Services Capacity “is counted in accordance with the Unit of Measure described in the Order”.[1] The TSMA’s User Guide definition includes “license entitlement descriptions”. This brings BMC’s published unit-of-measure definitions into the contract by reference.[1] The measures are described in BMC Software licensing.
Counting / floors
Who may use (TSMA, last updated 2026-09-09). Authorized Users are the customer, its Affiliates and their employees, consultants, contractors and agents. They must act under the customer’s control and be bound by terms no less restrictive, and the customer takes full responsibility for them. IT Services providers are Authorized Users only if they have “an appropriate agreement in place with BMC”.[1] An entity with an IT Services business cannot use BMC Offerings as a consultant, contractor or agent.[1] Catalog proof: IT Services providers need their own agreement with BMC.
Scope of use. On Premises Subscriptions may be installed in the Territory and used during the Order term, up to the Licensed Capacity and for internal business operations. The customer may make a reasonable number of archival copies.[1] The customer may not exceed the Licensed Capacity. It may not use the software in an outsourcing or service bureau environment for non-Affiliates, publish benchmark data without consent, or circumvent licensing mechanisms.[1] Catalog proof: On Premises Subscriptions may not be used above Licensed Capacity; No service bureau or outsourcing use without authorization.
Perpetual or term. EULA licences are “non-perpetual (unless a perpetual license is provided on an Order)”.[2] Under the TSMA, On Premises Subscriptions are term licences for the term specified on the Order.[1] When an Order or the Agreement ends, “all rights and Licenses granted thereunder will terminate”.[1] Under the EULA, the customer must uninstall the Product and, if BMC asks, return it or certify its destruction.[2] Catalog proof: EULA licences are non-perpetual unless the Order grants a perpetual licence; All licences end on termination or expiry of an Order; Terminated licences must be uninstalled.
Support. Under the EULA, the Order includes Support “for the total Licensed Capacity of the Products”. Support therefore cannot cover only part of the estate. BMC gives renewal notice at least 60 days before a prepaid Support period ends, and may change Support terms from the end of any prepaid period. A customer with perpetual licences that leaves Support and later re-enrolls may be charged a reinstatement fee.[2] Catalog proof: Support covers the total Licensed Capacity; Re-enrolling perpetual licences in Support may incur a reinstatement fee.
Trials. Under the TSMA, trial offerings may be evaluated internally for up to 30 days. They are provided “AS IS” without support and may not be put into productive use until paid for under an Order. Customer Content in a SaaS trial is deleted if no paid subscription follows.[1] The Online Trial Agreement adds several limits. Authorized Users are the evaluator’s employees only. Production data may not be processed. Development, commercial, production and database management use are excluded.[3] Catalog proof: Trials last 30 days and may not be used productively; Online trials are limited to the evaluator's employees and exclude production data.
Virtualization & partitioning
The agreements do not address virtualization directly. Physical, virtual, LPAR and Sysplex counting is set by the unit of measure named in the Order; see BMC Software licensing and BMC AMI mainframe licensing.[2]
Cloud / BYOL
For Subscription Services, BMC provides worldwide access up to the Capacity, for internal business operations, through Authorized Users.[1] The customer may not provide the Subscription Services to third parties, use them in a service bureau, or process third-party data with them.[1] Availability is governed by the Service Level Agreement. Service Credits are the “sole and exclusive remedy” for unavailability and are forfeited if there is no renewal.[10] After termination, the customer may ask within 60 days to retrieve Customer Content; after that BMC deletes it.[1]
Programs
- Solution Provider purchases. Orders may be placed through BMC authorized resellers. The customer then has “no direct payment obligations to BMC for such fees”.[1] Direct invoices are due within 30 days, and disputes must be raised within 30 days of receipt.[1] Catalog proof: No direct payment obligation to BMC for reseller purchases; Invoices are payable within 30 days.
- Assignment. The customer may assign the Agreement and all Orders in whole to an Affiliate, or to a successor after a sale of substantially all assets or a merger, by written notice. The assignee may not be a known direct competitor of BMC and must agree in writing to be bound.[1] The EULA extends the same right to an individual License.[2] Catalog proof: Assignment only to an Affiliate or a successor, with notice.
- Termination for convenience. The customer may terminate the TSMA on 30 days’ notice, but existing Orders continue. Orders themselves “may not be terminated for convenience unless otherwise specified therein”.[1]
Audits and compliance
Usage reports (as of 2026-09-09). At most once a year, BMC may ask the customer to deliver within 30 days the prior 12 months of three kinds of report: “(a) Product usage reports generated from specific Products (b) third party usage reports related to the On Premises Subscriptions (e.g., SCRT reports) and (c) written Product usage reports, to be provided solely when the Product does not generate reports”.[1] Catalog proof: BMC may request 12 months of usage reports once a year.
On-site audit. Separately, and also at most once a year, BMC may audit on at least ten days’ written notice. The audit takes place at the locations where the software is installed, during normal business hours, and the customer must cooperate and provide reasonable access.[1] Catalog proof: On-site audit once a year on ten days notice.
Outcome. If use above the Licensed Capacity is found, “BMC will issue a quote for the additional capacity through the end of the term of the applicable Order and Customer agrees to pay the applicable fees”.[1] The EULA §15 clause is the same.[2] Neither document specifies back-dated support, penalties or audit-cost shifting. For SaaS, BMC may monitor the Subscription Services, and excess Capacity leads to an Order for additional Capacity.[1] Catalog proof: Excess capacity found in an audit is quoted to the end of the Order term; BMC may monitor Subscription Services and require an Order for excess Capacity.
License Compliance Office. BMC’s License Compliance Office collects and analyses product usage information. It runs two programs: Statement of Capacity for customers and products under Enterprise Agreements, and Usage Reporting for non-Enterprise customers of ITSM/Remedy, ADDM, BladeLogic or Control-M.[4] BMC’s anti-piracy page lists “using more capacity than licensed” as an example of licence non-compliance.[5] Catalog proof: BMC runs Statement of Capacity and Usage Reporting compliance programs; Using more capacity than licensed is licence non-compliance.
Report formats. BMC publishes product-specific instructions:
| Product | What BMC asks for |
|---|---|
| Control-M | .csv files from the Control-M Usage Reporting Tool for all environments; physical socket counts for CPU licences; MIPS from the D M=CPU command[6] |
| BMC Discovery | The License Usage Collection Utility output, or the digitally signed licence report of Discovery 11.2 and later; earlier versions export host lists as CSV[7] |
| ITSM / Remedy | Licensereport.txt from each active AR System server, with version, function, server grouping and host ID or license key[8] |
The Control-M instructions ask customers that no longer use a product to report a capacity of zero.[6] The ITSM instructions ask customers to explain any server licences ordered but not in use.[8] The general process is described in software license audit and true-up.
Out of scope
The Data Processing Agreements, information security requirements, regulatory addenda for the financial sector, the EU Data Act addendum, AI Terms of Use and country-specific additional terms for services orders are listed on BMC’s Agreements page but not analysed here.[4] Neither are previous versions of the agreements or negotiated Enterprise Agreements.