The Oracle ULA at the certification window.

The certification window does not start at end of term.

The certification window starts at the start of term. The buyer who waits until month thirty-three of a thirty-six-month ULA to begin preparing for certification has already lost the negotiating posture. Schedule A reconciliation takes time. Deployment evidence takes time. The partitioning defence takes time. The eighteen-month preparation cycle is not a recommendation; it is the operating envelope inside which the certified-quantity position is built.

The publisher will arrive at the certification window with its own deployment view, drawn from the install-base data Oracle aggregates from support tickets, patch downloads, license-key activity and partner channel signals. The buyer’s deployment view, drawn from internal CMDB, hypervisor inventory, partitioning records and audit-quality discovery scans, will not match. The certified quantity sits in the gap between the two views. The width of that gap, and which side of it carries the better evidence, decides the perpetual-rights position the buyer takes out of the ULA.

This paper covers the methodology Admodum applies inside the eighteen-month cycle: the Schedule A reconciliation, the deployment evidence protocol, the partitioning defence, the counter-position posture and the closing letter that records the certified quantity. The methodology is the same one that has closed twenty-four ULA certifications across the firm’s engagement history.