Module 2 opens the paper: the master agreement's five decisive clauses, the four things to extract from any ordering document, the frozen-at-signature rule and its one deliberate exception, the technical support policies, and the five step entitlement library that every audit defense and renewal depends on.
The presenter in this session is an AI generated avatar. The curriculum and guidance are real, produced by Redress Compliance analysts from our consulting engagements and market network.
A taught session with three knowledge checks: the frozen-at-signature rule on a 2015 purchase, the forgotten price hold scenario, and the support policies exception. It ends by decoding a real style ordering document line by line: a benchmark, a rule confirmation, a forgotten right, and a support baseline in twenty minutes.
The full narration of this session, section by section, for reading and reference.
Welcome back, and welcome to module two. Session six of forty. Module one taught you to count, price, and defend deployments. Module two is about the paper those counts are judged against, five sessions on the Oracle contract, and today we start with the map of the documents themselves. The master agreement, the schedules, the ordering documents, the support policies, what binds, in what order, and where the money hides in each. If you did last week's homework you have your three biggest ordering documents nearby. Keep them close, because by the end of today you'll read them the way an advisor does, and one of them probably contains something valuable that nobody in your company remembers. Three knowledge checks, one live document reading. Let's open the paper.
Five things you'll take from today. One, the stack order, which document governs which question, and what outranks what when they disagree. Two, you'll be able to read a master agreement fast, there are five clauses that matter and you'll know exactly where to look. Three, same for the ordering document, four things to extract from any order, in minutes. Four, you'll understand the one document in the stack that moves, the technical support policies, and why Oracle built it that way. And five, the deliverable of the whole session, you'll know how to build the entitlement library, the single artifact that every audit defense, every renewal, every ULA exit, and the final capstone all depend on. Sessions seven through ten go deeper on each piece. Today is the map of the paper. First, why the paper deserves a whole module.
Four facts frame this module. Fact one, frozen. License definitions are fixed by the paper you signed at purchase. The version of the agreement on Oracle's website today does not rewrite your 2015 order. This is enormously important and cuts mostly in your favor, older paper often carries better terms than today's standard. Fact two, one line. A single special term paragraph on an ordering document can carry a price hold or a renewal cap worth millions. Those paragraphs got negotiated once, by someone, and then, in most companies, forgotten. Fact three, moving. There is exactly one deliberate exception to the frozen rule, the technical support policies, which Oracle updates over time, and the current version applies at each renewal. Knowing which documents freeze and which ones move is half of contract literacy. And fact four, one hour. That's how fast a well run estate can produce its complete Oracle paper. Most companies need a month and still come up short. The gap between the hour and the month is the entitlement library, and closing it is today's real assignment. Session one asked, which signed document says so. Today you get the full map of the signed documents.
The stack, five layers, top to bottom. Layer one, the master agreement. The OMA in current estates, the OLSA in older ones. It's the framework: definitions, the license grant, the audit clause, territory, assignment. Signed once, governing every order placed under it. Layer two, the schedules, attached to the master, carrying per product family terms, the program schedule for software, others for hardware and cloud. Layer three, the ordering documents, one per purchase, and this is where the money lives: products, metrics, quantities, price, and the special terms. Layer four, the technical support policies, incorporated by reference, updated by Oracle, governing the twenty two percent annuity. And layer five, which is not a layer at all: the policy papers, partitioning, cloud counting. Unsigned, non binding, and, as session four taught you, commercially loud anyway. On precedence: license questions resolve top down, but, and this matters, ordering document special terms can override the master where they say so. That's what makes the special terms paragraphs so powerful, they're the one place a buyer's negotiation rewrites Oracle's standard rules. Let's go inside the master first.
The master agreement, and the five clauses that decide everything later. Clause one, definitions. What Processor means, what Named User Plus means, every metric from module one, defined here, in the vintage you signed. Check for custom wording, negotiated definitions exist and they're gold. Clause two, the license grant, what you may run, where, and for whom. The scope words matter: internal business operations excludes hosting for others, territory clauses can bite in global estates. Clause three, the audit clause, the constitution of module five. Notice period, scope, what you must provide, confidentiality. Read yours before you ever need it. Clause four, assignment and M&A, what happens to licenses when companies merge, split, or sell. Whether transfers need Oracle's consent, and on what terms, this clause quietly prices acquisitions, session thirty eight lives here. And clause five, order of precedence, which document wins a conflict, and specifically whether order level terms can override the master. Five clauses. Read them in your own master this week, it's forty minutes, and you will genuinely know more about your Oracle position than most sourcing teams ever learn. Now, the frozen rule in action. Knowledge check one.
Knowledge check one. You bought Database Enterprise Edition in 2015, under an OLSA. Which document defines the Processor metric for those licenses today, in 2026? A, the current OMA published on oracle dot com. B, the OLSA you signed in 2015, together with that ordering document. C, the current technology price list. Or D, the technical support policies. Pause here, and think about when a definition gets frozen.
The answer is B, the paper you signed in 2015. License terms freeze at signature, and that OLSA with its order governs those licenses for as long as you hold them, ten, twenty, thirty years. This is worth pausing on, because it has two big practical consequences. First, your estate is probably a layer cake of vintages, some licenses under a 2009 OLSA, some under a 2016 OMA, some under last year's paper, and each purchase answers to its own rulebook. That's not a bug in your records, it's how the system works. Second, older paper is often better paper. Definitions, use rights, and terms have generally tightened over the years, in Oracle's favor. Which is why, when a helpful account team offers to consolidate or migrate your old licenses onto a fresh modern agreement, the correct reflex is suspicion: repapering usually trades your grandfathered rights for today's stricter standard. A and C are living documents that govern new purchases, not old ones. And D, the support policies, is the one deliberate exception, and it gets its own moment shortly. Now, into the ordering document.
The ordering document, four things to extract from any order, in minutes. One, products and metrics. Every line names a program and the metric it was bought on. This is where the Processor versus NUP decision from session two was made, per purchase, permanently. Two, quantities and price. The net price against list is your discount, in writing. Sixty percent off in 2022 is your anchor for every future negotiation, benchmark data most buyers forget they own. Three, the special terms, and lean in for this one. Price holds. Renewal caps. Custom definitions. Restricted use grants, session five's fine print lives here. These paragraphs are the negotiated exceptions to Oracle's standard rules, they can outrank the master, and in most companies they are completely forgotten within two years of signature. Reading old special terms is the closest thing this course has to a treasure hunt. And four, the CSI number, the customer support identifier, tying the order to its support stream. It's the key that indexes the entire estate, every support renewal line should trace to a CSI, and every CSI to paper. Let's test the special terms with a scenario straight from real life. Knowledge check two.
Knowledge check two. A 2022 ordering document grants your company a sixty percent discount on additional Enterprise Edition licenses, valid for four years. Today your account rep tells you that program has been discontinued. You want to buy more licenses this quarter. What governs the price? A, the rep's guidance, programs change. B, the signed order, the price hold binds Oracle through 2026. C, current list price, discounts never carry forward. Or D, it depends on Oracle's approval this quarter. Pause. One of these is a signed document. The others are conversation.
The answer is B. A special term on a signed ordering document is a contract right, and Oracle is bound by it through 2026, regardless of which internal programs have been renamed, retired, or reorganized, regardless of how many account reps have rotated through your patch. Here's the uncomfortable truth though: the real failure mode isn't legal, it's organizational. Oracle doesn't have to honor a term you never invoke. The buyer's side forgets the clause exists, a new quote arrives at forty percent, someone signs it, and a contractual sixty percent right quietly expires unused. Nobody broke any rules, the money is just gone. That is the entitlement library's first and clearest payoff: special terms extracted onto one summary sheet, checked against every incoming quote, automatically. A, C, and D are all the same mistake wearing different clothes, letting conversation outrank contract. Session one's discipline, in its most literal form: the signed document says sixty percent. End of discussion. Now, the one document where the frozen rule does not apply.
The technical support policies, the moving part of the stack, four facts. Fact one, the mechanism. Your signed agreement incorporates the support policies by reference, and Oracle revises that document over time. The version in force at each renewal is the version that governs it. Your license terms froze at signature, your support terms did not. Fact two, why it's built that way. Incorporation by reference lets Oracle evolve the rules of its most profitable product line, the twenty two percent annuity, without renegotiating a single customer contract. The policies hold the annuity's defenses: matching service levels, the repricing rules, reinstatement terms. Fact three, what it means for you, practically: support is the one part of your position that can get worse without your signature. So at every renewal, snapshot the current policies document, date it, file it, and diff it against last year's. Changes to matching service levels or repricing language are early warnings worth real money. And fact four, the module four preview: every support reduction strategy, terminations, third party support, restructuring, runs through these policies. Knowing that they move, and tracking how, is the foundation of negotiating around them. Now let's build the artifact this whole session has been pointing at.
The entitlement library, five steps. Step one, gather. Every master agreement, every schedule, every ordering document, every amendment. If gaps exist, and they will, ask Oracle for copies, they hold the records and they must provide them, it's a routine request. Step two, verify completeness, and here's the elegant trick: check against your support renewal. Every line on the renewal has a CSI, every CSI traces to an order, so the renewal is effectively Oracle's own index of what you bought. Any CSI you can't match to paper is a gap to fill. Step three, index, by CSI and by product, which order granted which licenses under which master, so any question routes to its document in seconds. Step four, extract, the special terms, custom definitions, price holds, restricted grants, onto a single summary sheet that sits in front of the whole library. That sheet is what gets checked against every new quote and every audit claim. And step five, maintain: every new order and amendment lands in the library the week it's signed, standing rule, no exceptions. Total effort for a mid size estate: a few days once, an hour a quarter after. And it converts session one's question, which signed document says so, from rhetoric into a one hour lookup. The traps, then the exception that trips everyone.
Five paper traps, all common, all expensive. Trap one, the missing amendment. A term was amended in 2019, your team argues from the 2016 version, and the position collapses in the room. Completeness isn't pedantry, it's the defense. Trap two, the verbal promise. The account team assured us, said in every renewal, worth nothing in every audit. If it isn't on signed paper, it does not exist, and the corollary: get every assurance onto the order before signing, session ten is entirely about that. Trap three, definition drift. Your 2010 licenses and your 2024 licenses may define the same metric differently. Counting the whole estate with one rulebook, either rulebook, misprices part of it. Trap four, the lost custom term, knowledge check two's scenario, a predecessor negotiated something great and left, and unread paper became unclaimed money. And trap five, the click through. Cloud era orders accepted online by administrators, current standard terms, no review, no negotiation. Still binding paper, just paper nobody on your side ever read. The library catches all five, which is the point of the library. Last knowledge check, on the one document that moves.
Knowledge check three. Your OMA incorporates the technical support policies by reference. Oracle updates the policies next quarter. Which version governs your next support renewal? A, the version in force when you signed the OMA, forever. B, the current version at each renewal, that's the design. C, whichever version is more favorable to you. Or D, neither, support policies are unsigned guidance, like the partitioning policy. Pause here. This is the exception to the frozen at signature rule.
The answer is B, the current version at each renewal, by design. Incorporation by reference to a document the vendor may update means the rules follow the document, not the signature date. That's the deliberate exception to knowledge check one's frozen principle, licenses freeze, support floats. A applies the license rule to the wrong document. C is lovely and imaginary. And D, D is the subtle one, worth unpacking, because it confuses two documents that both feel unsigned. The technical support policies are expressly incorporated into your signed agreement, so they bind, they're contract. The partitioning policy is referenced by nothing you ever signed, so it binds nothing, it's commentary. Two documents, both PDFs on Oracle's website, one is law for you and one is theater, and the difference is a single incorporation clause. If you can make that distinction cleanly, and after six sessions you can, you have the exact skill this module exists to teach: knowing which paper is real. Alright, let's read a document together and close.
One ordering document, decoded live, four lines. Line one, Database EE, Processor metric, quantity sixteen, at nineteen thousand net. Divide by list: nineteen over forty seven five is forty percent of list, so this buyer got sixty percent off. That's your benchmark anchor, written evidence of what your relationship has achieved, and the starting point for the next negotiation. Line two, Partitioning, Processor, sixteen. Session three's rule on real paper: the option carries the database's metric and count, automatically. Seeing it in print makes it real. Line three, the special term, paragraph four: net pricing holds for additional orders through 2026. There it is, knowledge check two's price hold, sitting quietly in a paragraph most teams never re-read, worth six figures if anyone remembers it at quote time. And line four, support: twenty two percent of net, sixty six thousand eight hundred eighty per year, attached at birth, governed by the moving policies document. Four lines, twenty minutes of reading, and it produced a benchmark, a rule confirmation, a forgotten right, and a support baseline. That's the reading habit this session installs. Do it to your own three orders this week.
Session six in three sentences. One, license terms freeze at signature, every purchase lives under its own vintage of paper, and older vintages often carry better terms, which is exactly why repapering offers deserve suspicion. Two, the support policies are the one deliberate exception, updating underneath you by design, so every renewal gets a version snapshot and a diff. Three, the entitlement library, gathered, verified against the support renewal, indexed by CSI, special terms extracted, maintained weekly, turns every future dispute into a lookup, and it is the first artifact module five's audit defense will reach for. Next session we go one level deeper, into the license grants themselves: full use, application specific, embedded, the different species of license Oracle sells, and the very different rights that travel with each. Session five's restricted use grant was a preview, session seven is the full taxonomy. See you there.
Homework, about an hour, and this week it starts the most valuable artifact in the course. One, start the library. Your three largest ordering documents plus the master they sit under, gathered into one folder, this week. Not the whole estate yet, just the start, momentum matters more than completeness. Two, read the five clauses in your master: definitions, grant, audit, assignment, precedence. Forty minutes, and note anything that looks nonstandard. Three, extract the specials. Every special term paragraph from those three orders, summarized on one sheet. If you find a live price hold or cap, congratulations, this course just paid for itself. Four, trace one CSI. Take one line from your last support renewal and follow it back to its ordering document. Time how long it takes, that duration is your current library maturity score, and shrinking it is the goal. And five, date your vintages. OLSA or OMA, and from which years? Write the list. Each vintage is a different rulebook, and from today, you know which rulebooks you hold. That's the hour. See you in session seven.
Five reads, all free on redress compliance dot com. First, field tested Oracle negotiation strategies, what strong buyers do with the paper once they can read it, which as of today, you can. Second, dealing with Oracle sales tactics, the conversation layer that tries to outrank your contracts, and the discipline of keeping the two ledgers separate. Third, how to check your Oracle license position, the entitlement side of today's library, built three different ways. Fourth, Oracle licensing in M&A due diligence, where the assignment clause from today's master agreement table decides real transaction money. And fifth, the Oracle vendor management guide, the operating rhythm that keeps the library alive between renewals instead of decaying into a forgotten folder. That's session six. The stack is mapped, the library is started, and the frozen versus moving distinction is yours. Next time, the license types themselves. See you in session seven.