Support Rewards credits 25 cents against the on premises support bill for every dollar of OCI consumed, 33 with an active ULA, capped at the bill, expiring in 12 months, and earned by the meter, never the signature. This session runs the arithmetic at five scales, maps the interactions with module 4's program, third party repriced, BYOL subsidized, the ULA calculus changed, and then negotiates the OCI deal properly: forecast first, ramp to the plan, the concession menu from migration funding to the two bill sweetener, and every proposal scored as cloud cost minus support relief. The worked deal stacks it all: $590K a year better than doing nothing.
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 rewards computed on the $500K consumed rather than the $800K committed, the third party evaluation repriced rather than cancelled when $500K of rewards start flowing, and the $1M flat first draft countered with a ramp, protections, and the menu. It closes with one fully stacked deal: a ramped commit, 29 percent with a rate hold, $120K of migration credits, $310K of BYOL savings, and $162K of first year rewards.
The full narration of this session, section by section, for reading and reference.
Welcome back, session twenty eight of forty. The OCI story so far: session twenty six taught the commercial machine, credits, commits, expiry, and session twenty seven turned your license shelf into cloud currency through BYOL. Today the arithmetic gets friendlier still, because we add the mechanism that connects the cloud meter directly to the bill module four spent five sessions fighting: Oracle Support Rewards. The construct in one sentence: for every dollar of OCI you consume, Oracle credits twenty five cents against your on premises technology support bill, thirty three cents if you hold an active ULA. Consume two million in the cloud, and half a million falls off the support annuity, without a termination notice, without a repricing calculation, without a policy pincer, without any of the machinery module four taught you to respect. It sounds too good, so today we do what this course always does with generous sounding mechanisms: read the rules, run the arithmetic, find the catches, and then use it anyway, deliberately. And because Support Rewards makes every OCI deal a deal about two bills at once, the second half of the session runs the OCI negotiation properly: the concession menu, the timing, the competitive lever, and the counter proposal that treats a cloud commit with the same discipline module four brought to renewals. The cloud is about to start paying for the datacenter. Let's see exactly how much.
Five takeaways. One, you'll run the Rewards math: consumption times the rate, applied against the support bill, with the caps, the expiry, and the one distinction that ruins careless business cases, rewards follow consumption, never commitment. Two, you'll stack the programs: Support Rewards meets module four's reduction paths, and they compound, but they also interact, the third party case gets repriced, the BYOL support requirement gets subsidized, the ULA calculus gains a variable. Nothing cancels; everything reruns. Three, you'll negotiate the OCI deal with the full module four toolkit, because a cloud commit is a renewal season with different SKUs: benchmarks, the fiscal calendar, credible alternatives, and the banking rule, all transfer. Four, you'll order from the concession menu: migration funding, ramps, rate holds, carryover language, training credits, and the two bill sweetener, six asks that first drafts never contain and prepared buyers routinely get. And five, you'll price the whole estate: every cloud proposal scored on both bills at once, cloud cost minus support relief, on the consumption you actually believe, because that combined number is the only honest one. The stakes, next.
Four numbers. Twenty five cents: earned against the on premises technology support bill for every dollar of OCI Universal Credits consumed. Automatic once enrolled, accruing monthly, and large enough to change every cloud business case you'll ever write. Thirty three cents: the enhanced rate for customers with an active Unlimited License Agreement, which quietly adds an entry to module three's ledger, cloud heavy estates now have one more reason to weigh the ULA differently. Zero dollars: how low Support Rewards can take a tech support bill, because the relief caps at the bill itself. Rewards are credits against support invoices, never cash, and consumption beyond the cap earns nothing, a boundary that matters for the biggest cloud estates. And twelve: months before earned rewards expire. Session twenty six taught you one use it or lose it clock on the commit; this is its twin on the earn side, and the same quarterly review catches both. Here's the frame for the whole session: module four shrank the support bill from inside, terminations, restructures, negotiations. This mechanism shrinks it from outside, funded by workloads that were moving to the cloud anyway. The two programs compound, and the estates that run both, deliberately, are the ones whose Oracle economics genuinely transform. The construct in detail, next.
Support Rewards, what it actually is, five facts. The earn: twenty five cents per dollar of OCI Universal Credits consumed, thirty three with an active ULA, accruing as you consume. Hold that verb, consume. A signed commitment earns nothing; a burned credit earns its quarter. The rewards engine is bolted to the meter, not the contract. The burn: rewards apply against on premises technology support invoices, the database and middleware annuity from module four, and they can take it to zero if you earn enough. Applying them is an administrative step, not an automatic offset, which is why this session's homework includes checking where your earned credits are actually going; unclaimed rewards are found money with an expiry date. What qualifies: Universal Credits consumption earns, and the offset targets tech support for on premises licenses. SaaS subscriptions sit outside the mechanism on both sides, earning nothing and receiving nothing. The expiry: earned rewards last twelve months, then vanish, exactly like unused commit. Two clocks, one calendar, one quarterly review. And why Oracle built it, worth a moment of honesty: Support Rewards makes leaving the support annuity for a rival cloud doubly expensive, move the workload to AWS and you lose both the subsidy and the relationship. It is a loyalty mechanism with teeth. Know the intent, then use the mechanism anyway, because the arithmetic is real regardless of the motive. That arithmetic, next.
The arithmetic, run at five scales, against a million dollar support bill. Four hundred thousand of annual OCI consumption earns a hundred thousand in rewards: the support bill nets to nine hundred thousand, a ten percent cut achieved without touching a single license set, no terminations, no repricing, no notice windows. Eight hundred thousand consumed earns two hundred thousand: support nets to eight hundred, and notice this stacks on top of whatever module four's program already removed. Two million consumed earns five hundred thousand: half the annuity now paid by workloads that migrated. Four million consumed earns a full million: the bill fully absorbed, and here the cap bites, further consumption earns rewards with nothing left to offset. Estates near the cap should know they're near it, because the marginal value of consumption changes. And the ULA row: eight hundred thousand consumed at the thirty three cent rate earns two hundred sixty four thousand, the enhanced rate compounding module three's calculus for cloud heavy ULA estates. Read the whole table the way module four would: these are support reductions with none of module four's machinery, no policy pincer, no matching service levels, no repricing risk. The catch, and it's the only catch: you must genuinely consume the cloud. Which brings us straight to the mistake every optimistic business case makes. Knowledge check one.
Knowledge check one. The estate signs an eight hundred thousand dollar annual OCI commit, but consumes only five hundred thousand in year one. The support bill is nine hundred thousand. What relief did Support Rewards actually deliver? A, two hundred thousand, a quarter of the commitment. B, a hundred twenty five thousand, a quarter of the five hundred thousand actually consumed, because rewards follow consumption, not commitment. C, two hundred twenty five thousand, a quarter of the support bill. Or D, nothing, because the commit was not fully consumed. Pause here. What earns: the signature, or the meter?
The answer is B. Rewards accrue on consumption, the meter read five hundred thousand, so the earn is a hundred twenty five thousand, netting the support bill to seven hundred seventy five. Simple arithmetic, but getting it reflexively right matters, because every optimistic OCI business case in circulation makes mistake A: quoting the rewards on the commitment. This estate's business case promised two hundred thousand of support relief. The meter delivered a hundred twenty five. The missing seventy five thousand is pure forecast error, and look at what that error actually cost, because it cost twice: the three hundred thousand of unconsumed commit faces session twenty six's expiry as potential breakage, and it also never earned its quarter against support. Every dollar of commit you fail to consume loses you the dollar and the twenty five cents. Which means the session twenty six forecast discipline, confidence weighting, committing to the floor, ramping to the plan, is now worth a hundred twenty five percent of what it was worth before you knew Support Rewards existed. The wrong answers teach the mechanism: C computes rewards from the support bill, but the bill only caps the relief, it never generates it; the engine is on the cloud side. D imagines an all or nothing threshold that doesn't exist; every consumed dollar earns its quarter regardless of what the commit said. The planning rule that falls out of this check: build the rewards line into the business case at the confidence weighted consumption forecast, never the commit, and treat everything above that as upside rather than budget. Now, what this mechanism does to module four. The stack, next.
Support Rewards meets the module four program, five interactions, and this slide is where the session earns its keep, because two programs pointed at one bill always interact. First, it stacks with reductions: rewards apply to whatever support bill survives module four's terminations and restructures. So the order of operations is fixed: shrink the bill first, then subsidize the remainder. Subsidizing a bill you should have cut is still waste, just discounted waste. Second, it reprices third party support: session nineteen's fifty percent saving competed against full price Oracle support. Against rewards subsidized support, the delta narrows, sometimes to nothing, sometimes not at all, and we'll spend the whole next check on exactly this. Third, it protects BYOL: the active support that session twenty seven's BYOL licenses require is precisely the support that rewards offset. Cloud consumption subsidizes its own eligibility ticket, a small elegant loop that improves every BYOL case. Fourth, it changes the ULA math: the thirty three cent rate is real money for cloud heavy ULA estates, another variable in module three's certify or renew decision, worth an explicit line in that analysis from now on. And fifth, the honest boundary: it does not remove the annuity. The bill still exists, still compounds at session sixteen's uplift rates, and still deserves the full module four treatment. Rewards are a subsidy, not a cure. The repricing question, tested. Knowledge check two.
Knowledge check two. With two million dollars of planned OCI consumption earning five hundred thousand a year against support, the CFO asks: should we cancel the third party support evaluation for the legacy estate? A, yes, Support Rewards makes all support reduction work obsolete. B, no, but rerun the arithmetic: rewards change the numbers, and the legacy estate's third party case must now beat the subsidized Oracle price, not list. C, no, ignore rewards entirely when comparing support options. Or D, yes, because third party support would end the rewards program. Pause here. What price does third party support compete against now?
The answer is B, the analyst's answer: nothing is cancelled, everything is repriced. Walk the logic. Session nineteen's third party case was built when Oracle support cost full price, and the fifty percent saving was measured against that. With five hundred thousand of rewards flowing annually, the effective cost of whatever support those rewards offset has dropped, and the third party delta narrows accordingly. Now the question that actually decides it: which support dollars do the rewards displace? If the rewards are fully absorbed offsetting the core estate's support, the legacy slice still pays effectively full price, and the third party case survives untouched. If the allocation reaches the legacy slice, its effective cost halves, and the third party saving may no longer clear the switching costs. That allocation analysis is an afternoon with a spreadsheet, and it's the honest version of the CFO's question. What B refuses to surrender is the discipline: the fit profile from session nineteen still governs workload by workload, and the priced alternative still disciplines every renewal per session twenty, even if the move never executes. That's the part A destroys: cancel the evaluation and you don't just lose an option, you lose the leverage that option exerts on every support negotiation, leverage that took three sessions to build. C is malpractice in the opposite direction, comparing support strategies while ignoring a half million dollar annual flow. D states a half truth backwards: moving specific sets to third party removes those sets' bills from the offsetable pool, but the program itself continues, earning on every consumed dollar regardless. The course's most repeated sentence, once more: when a new mechanism appears, nothing is sacred, nothing is obsolete, everything is rerun. The negotiation, next.
The OCI negotiation, run like a module four deal, because it is one, just with different SKUs. Five transfers. Benchmark the discount: OCI discounts follow commit size and term, and the published tiers are the floor of the conversation, not the ceiling. Deals that matter to a quarter clear the tiers routinely, and session nine's habit, never negotiate without a benchmark, applies unchanged. Bring the forecast: the confidence weighted number from session twenty six is your anchor against theirs. Arrive with your consumption number and the conversation is about how to structure it; arrive without one and the conversation is about how to accept theirs. First number on the table wins ground; make it yours. Work the calendar: cloud commitments are bookable revenue on exactly the fiscal calendar session nine mapped. The rate card that won't move in July moves in May, the concessions list that stalls in month one signs in the closing quarter, and nothing about cloud changed any of it. Keep the alternative alive: current, credible AWS and Azure quotes for the same workloads do for OCI deals what third party quotes did for support renewals. OCI competes hardest, and prices best, when it visibly must. And bank everything: rate holds, ramp terms, credits, any enhanced treatment, in the order, in writing. The retention desk's warmth rule from module four has a cloud twin, and it expires on the same schedule. The one genuine addition to the toolkit: this deal touches two bills, so every proposal gets scored on cloud cost and support relief together, or it gets scored wrong. The menu, next.
The OCI concession menu, six asks that first drafts never contain and prepared buyers routinely get. One, migration funding: proof of concept credits, funded migration services, transition support. Standard in competitive deals, meaningful money on real migrations, and entirely invisible until requested. The ask costs one sentence. Two, the ramp: commitment steps matched to the actual migration schedule, session twenty six's structure, and the single cheapest breakage insurance that exists. A ramp costs Oracle almost nothing and saves you everything the flat commit would have wasted. Three, rate protection: discount holds at renewal, and growth pricing agreed in advance, so scaling mid term never reopens the negotiation at retail. The renewal that reopens at list is the cloud version of session sixteen's uplift autopilot; the rate hold is its cap. Four, carryover and extension: flexibility on credit expiry, obtainable at signature in real deals, nearly impossible afterward, and valuable precisely when forecasts miss, which forecasts do. Five, training and enablement: certification funding, architecture support, workshops. Cheap for Oracle, genuinely useful mid migration, granted for the asking. And six, the two bill sweetener: in large deals, the support annuity's own treatment becomes negotiable alongside the cloud commit, caps and credits on the on premises bill, folded into the cloud paper. The biggest deals settle both bills in one signature. Why the menu works: every item is cheaper for Oracle than a discount point, so you're handing the account team ways to win your deal without breaking their pricing floor. Everyone closes; you collect. Timing, next.
When and how the OCI deal closes best, five habits, most of them old friends in cloud clothing. Open with the forecast: your confidence weighted consumption number starts the conversation, stated before their proposal can anchor it. The party that names the first credible number frames everything after; module four taught it at renewals, and it's truer here, where your number comes from a meter. Run it against the quarter: session nine's calendar, unchanged. The concession menu signs in closing quarters and stalls in opening ones, and a deal you can hold back six weeks routinely returns improved. Keep the rivals priced: a current AWS or Azure quote for the same workloads, refreshed at every renewal, not as theater but as a genuine executable alternative, which is the only kind that moves prices, per module four's oldest rule. Score both bills: every proposal evaluated as cloud cost minus rewards driven support relief, computed on the consumption forecast rather than the commit, per knowledge check one. One number, honestly constructed, and proposals rank themselves. And renew on the ledger: session twenty six's consumption ledger is the renewal's evidence base. Twelve months of metered history beats every slide in every deck, and it's yours, free, renewed annually. The estates that keep the ledger negotiate from their own data forever after. All of it, applied to a real first draft. Knowledge check three.
Knowledge check three. Oracle's first OCI proposal arrives: one million dollar annual commit, twenty five percent discount, three years, flat, no ramp, no rate hold, no migration credits. Your forecast says six hundred fifty thousand in year one, growing to one point one million by year three. Your counter? A, sign it, twenty five percent is a good discount. B, a ramped commit tracking the forecast, the discount benchmarked and pressed against the quarter, a rate hold at renewal, migration credits from the menu, and the whole package scored on both bills with rewards included. C, refuse any commitment and stay pay as you go. Or D, accept the million flat but ask for twenty seven percent. Pause here. Count the missing menu items, and the breakage in year one.
The answer is B, and the method is to audit the first draft the way this course audits everything. Start with the commit: a million flat against a six hundred fifty thousand dollar year one forecast is three hundred fifty thousand of probable breakage, and, per knowledge check one, it also forfeits roughly eighty seven thousand of Support Rewards the business case was quietly counting. The double penalty, live. The structure: no ramp, even though the forecast itself describes one, rising to one point one million by year three. A ramped commit tracking that curve captures the discount with almost no breakage risk; the flat commit is the anchor's shape, not the forecast's. The protections: no rate hold, so the renewal reopens at retail. No migration credits, so the standard competitive concession went unrequested. And nothing acknowledges that this deal touches two bills. B repairs all of it with tools you already own: session twenty six's ramp, module four's benchmark and calendar, this session's menu, the alternative kept credibly priced, and the package scored as cloud cost minus rewards relief on the real forecast. That counter isn't aggressive; it's literate, and account teams recognize the difference in the first meeting. The wrong answers price themselves: A pays the anchor, and the year one breakage plus forfeited rewards can exceed the entire value of the discount, which is exactly why first drafts look like this. D negotiates the decoration while accepting the defect, two points on a commitment sized wrong, module three's ULA lesson in miniature: the structure is the decision, not its price tag. C surrenders discount, rewards leverage, and negotiating position on workloads with a defensible multi year forecast; pay as you go is for uncertainty, and this forecast isn't uncertain, it's just smaller than their proposal. Sign your forecast wearing your protections. Nothing else. The full stack, next.
One OCI deal, fully stacked, the module so far in six rows. The commit: six hundred fifty thousand rising to one point one million on a three year ramp, the confidence weighted forecast from session twenty six wearing the ramp this session negotiated. The discount and protections: twenty nine percent, benchmarked first, pressed in a closing quarter, with the rate hold and growth pricing in writing, module four's banking rule executing in cloud paper. Migration credits: a hundred twenty thousand dollars, from the menu, asked for once, granted in the quarter that needed the deal. One sentence, six figures. BYOL on the core databases: roughly three hundred ten thousand a year of avoided credit burn, session twenty seven's harvest, twelve shelf processors covering twenty four OCPUs at the BYOL rate instead of license included. Support Rewards, year one: roughly a hundred sixty two thousand, twenty five cents on the six hundred fifty thousand actually consumed, applied against the one point zero five million support bill, which module four's program had already trimmed. And the net estate effect, year one: roughly five hundred ninety thousand dollars better than the do nothing baseline, counting the cloud discount, the BYOL saving, the credits, and the rewards together, both bills, one number. Look down the middle column: no single line is heroic. The stack is. Forecast, ramp, benchmark, harvest, rewards, each one priced before the negotiation started, each one compounding the others. That is what module six has been building. Recap, next.
Session twenty eight in three sentences. One, Support Rewards pays twenty five cents of on premises support relief per dollar of OCI consumed, thirty three with a ULA, capped at the bill, expiring in twelve months, and earned by the meter, never the signature, which makes the consumption forecast the load bearing number in every cloud business case you'll ever write. Two, the mechanism stacks with module four's program and reprices its alternatives, so nothing is cancelled and everything is rerun: the reduction program first, the subsidy on the survivor, the third party case reworked on the allocation, and the priced alternative kept alive for the leverage it exerts even unexecuted. Three, the OCI deal is a module four negotiation touching two bills: open with your forecast, ramp to the plan, benchmark the discount, work the quarter, order from the concession menu, bank everything in writing, and score every proposal as cloud cost minus support relief on consumption you actually believe. Next session the course leaves Oracle's cloud for everyone else's: Oracle on AWS, Azure, and Google Cloud. The authorized cloud environment policy, the vCPU counting rules that surprise every first timer, licensing Oracle databases in hyperscalers, and the specific traps in each. The rules change at the cloud boundary, and knowing exactly how is worth real money. Homework first.
Homework, about an hour, and the first item might literally be found money. One, check the enrollment: if the estate consumes OCI at all, is Support Rewards active, at which rate, and where are the earned credits actually going? Estates have discovered five figures of accrued, unclaimed rewards sitting in the program with an expiry clock running. Ten minutes to check; do it first. Two, model the rewards line: your consumption forecast times twenty five cents, laid against your support bill, per today's table. That's the two bill number your next cloud business case needs, computed on consumption, not commit. Three, rerun one comparison: the third party or termination case from module four's homework, repriced with an honest rewards allocation, per knowledge check two. Does the answer move? Either way, you now know, and knowing is the point. Four, draft the counter: for any live or upcoming OCI proposal, one page: the ramp you'd request, the protections you'd require, the menu items you'd ask for. Before the next meeting, not during it. The counter drafted in advance is the counter that gets made. And five, diary the expiries: rewards expiry joins commit expiry in the quarterly review, two use it or lose it clocks on one calendar, owned by the same person who owns the consumption ledger. That's the hour. See you in session twenty nine, in other people's clouds.
Five reads, all free on redress compliance dot com. First, the Oracle Support Rewards guide: the program rules, the rates, the enrollment mechanics, and the fine print, today's construct at reference depth. Second, the Oracle OCI procurement toolkit: the negotiation structured as a complete procurement process, from forecast to signature. Third, Oracle cloud negotiations: the levers and the sequence at strategy depth, the companion to today's menu and timing slides. Fourth, the case study of an OCI negotiation for a Singapore media company, eighteen percent saved: today's toolkit applied to a real deal, with the numbers shown. And fifth, the Oracle OCI FinOps framework: the consumption ledger, the burn reviews, and both expiry clocks, operationalized into a standing practice. That's session twenty eight. The cloud now pays part of the support bill, the support program and the rewards allocation know about each other, and the OCI deal on your desk gets a counter built from a forecast, a ramp, a menu, and a calendar. Two sessions remain in module six: Oracle running in everyone else's clouds, and then the engineered systems constructs that close the module. See you in session twenty nine.