Number of Seats/Users: TD/OMS offers discounts based on the number of users or seats. A higher volume typically leads to a better discount structure, especially for enterprise-level usage.

Commitment to a Long-Term Contract: Discounts are often provided to companies that commit to using the service for a longer period (e.g., 1-year or 3-year contracts). A longer commitment shows TD/OMS that the company is serious and willing to invest in the platform long-term.

No Active Discounts: Companies that are not already receiving other active discounts may have a better chance of qualifying for additional discounts from TD/OMS. TD/OMS reserves discounts for new customers or those not currently under promotional pricing.

Volume or Usage Commitment: TD/OMS offers discounts if you agree to a minimum amount of usage or transaction volume. This could be based on data storage, transactions, or other metrics tied to how much you will use the platform.

Enterprise-Level Negotiation: Companies that qualify as “enterprise” due to their size or complexity (e.g., having large teams, multiple departments, or geographical presence) may be eligible for additional discounts from TD/OMS. Such companies are often in a position to negotiate for better pricing.

Early Renewal or Prepayment: TD/OMS often offers discounts if you renew early or prepay for the entire contract period. This is a common approach to securing a lower price.

Here at Spendbase our internal data shows that TD/OMS consistently scores very high in day‑to‑day reliability and impact on development workflows, especially in IBM i environments.

Overall sentiment
– Average satisfaction: very strong (most Spendbase clients rate it 4–5/5)
– Main perceived value: risk reduction, time savings, and cleaner promotion to production

Key strengths our clients highlight

1. Operational stability and automation
   – TD/OMS “runs itself” once configured, with very few production surprises
   – Strong support for structured promotion to production, removing manual steps
   – Lower risk of mismatched source and objects, which directly cuts costly rollback work

2. Developer productivity
   – Deep integration with IBM RDi is appreciated
   – Centralized control over changes and deployments supports team collaboration
   – Clients report “less work and no surprises” when maintaining and distributing applications

3. Governance and process control
   – Clear tracking of software changes across environments
   – Better auditability and control over who changed what and when
   – Helpful for modernization projects, not just maintenance

Common pain points

Our internal data also shows several recurring friction points:

• Documentation
• Lack of a clear, modern user guide is mentioned often

• New teams need more onboarding material and practical examples

• Interface and configuration

• Core work can be done in RDi/Eclipse, but key configuration still relies on green‑screen

• Some teams see this as outdated and slowing adoption for newer staff

• Learning curve

• Initial setup and cleanup of historical “messy” processes can take time
• Once established, though, the process becomes highly stable

How this translates to Spendbase value

From a cost-optimization and discount perspective, TD/OMS tends to deliver:
– Indirect savings via fewer production errors and rollbacks
– Reduced manual effort in deployments and change tracking
– Better leverage of existing IBM i and RDi investments

In short, our Spendbase clients see TD/OMS as a robust, long‑term platform for managing IBM i software change and deployment. The biggest gaps are around documentation and modernizing some configuration workflows, not core functionality or stability.