Cooperative vehicles solve a procurement problem, not a pricing problem, and Oracle knows it. This guide shows what NASPO AR2487, the OMNIA Mythics award, and the E&I Mythics contract actually contain, what they silently accept on your behalf, and how to buy through them without surrendering leverage.
How to Negotiate the Oracle Java Employee Agreement: Honest Leverage in a Captive Deal
Priced per employee, every employee, from $15 down to $5.25. At renewal your leverage is thin and OpenJDK threats rarely land. The one-year runway, trading through the wider Oracle relationship, and containing what you sign.
Cooperative vehicles solve a procurement problem, not a pricing problem, and Oracle knows it. This guide shows what NASPO AR2487, the OMNIA Mythics award, and the E&I Mythics contract actually contain, what they silently accept on your behalf, and how to buy through them without surrendering leverage.
A cooperative contract is a procurement instrument, not a pricing instrument. What you buy when you cite NASPO AR2487, an OMNIA Mythics award, or the E&I Mythics contract is administrative cover: a completed competitive solicitation someone else ran, a defensible basis for waiving your own bid, and a cycle time measured in weeks instead of months. That is genuinely valuable. It is also the entire product. Nothing in these vehicles establishes what a specific Oracle SKU costs you relative to the current Oracle price list, and nothing in them prevents Oracle or its reseller from quoting you a worse number than a peer institution got last quarter on the same paper. NASPO says so itself: the documents posted on its website are for informational and convenience purposes only, with the official documents maintained by the lead state or the participating entity. Read that carefully. The co-op is telling you that the file you are relying on may not be the file that governs. TD SYNNEX markets its OMNIA Oracle contract as delivering "best available pricing, terms and conditions, and addendum capabilities" and then, in the same breath, directs you to contact a licensing specialist for a quote customized to your buying needs. Those two statements cannot both be load-bearing. If pricing were fixed and best available, there would be nothing to customize. E&I is the most honest of the three about what it is measuring: its Economic Benefit Model for the February 2026 Unimarket award projects a 10 to 15 percent "total economic benefit" built from cost reduction, cost avoidance, and incentives tied to procurement improvements. That is a modeled construct about process efficiency. It is not a discount off an Oracle list edition. Apply one test to every claim in the rest of this article and every claim a reseller makes to you: name the price file, name the discount percentage, and name the list edition that percentage discounts. If any of the three is missing, you do not have a price. You have a purchase order path.
If a reseller cannot name the price file, the discount percentage, and the list edition it discounts, you do not have a price, you have a purchase order path.
Buyers treat these three as interchangeable because resellers present them that way. They are structurally different, and the differences determine what you can legally buy, from whom, and under whose terms. NASPO AR2487 is an Oracle America direct master agreement with Lead State Utah, effective March 1, 2017, carrying Oracle internal reference US-GMA-1301562. Its scope is the Oracle Cloud Services product lines listed on Attachment B that are commercially available at the time of the order. That is a narrow envelope. On-premises perpetual licenses, technical support renewals, and hardware sit outside it, which is why buyers who "used NASPO" for a database refresh are often surprised to learn they signed an ordinary Oracle ordering document. The operative terms live in the Oracle order, which incorporates the master agreement by reference, not the reverse. Complicating matters, a legacy Oracle reseller vehicle, MNWNC-123 with participating addendum US-GMA-554058, is still cited by resellers such as Arisant into 2026, so two Oracle NASPO citations can appear on competing quotes for the same requirement. OMNIA's Oracle product coverage traces to Region 4 Education Service Center in Houston, which awarded Mythics a two-year contract with two one-year renewals as the sole provider in its competitive solicitation. The initial term ran December 12, 2018 through November 30, 2023 and has been renewed through November 30, 2028: a price file spanning ten years off one 2018 solicitation. OMNIA also holds a separate direct Oracle cloud and services contract routed through designated authorized distributors, and TD SYNNEX Public Sector separately lists U.S. Communities OMNIA (Oracle) 180233 and OMNIA Partners Iowa OCIO Oracle IDIQ 2019BUS0430. E&I routes through Mythics, with Emergent, a wholly owned Mythics subsidiary, acting as agent, and the contract documentation is member-gated with explicit instructions not to share it outside your institution.
| Attribute | NASPO AR2487 | OMNIA / Mythics (Region 4) | E&I / Mythics |
|---|---|---|---|
| Contracting party | Oracle America direct | Mythics (reseller, sole provider) | Mythics, Emergent as agent |
| Lead entity | State of Utah | Region 4 ESC, Houston | E&I Cooperative Services |
| Oracle reference | US-GMA-1301562 | Not published as Oracle master | Not published |
| Effective / term | March 1, 2017 forward | Dec 12, 2018 to Nov 30, 2028 (renewed) | Member-gated |
| Product scope | Cloud Services on Attachment B, commercially available at order | Broad Oracle portfolio via reseller | SaaS, PaaS, IaaS, on-premise via Mythics group |
| Excluded | On-prem licenses, support renewals, hardware | Varies by quote | Not disclosed publicly |
| Terms visibility | Posted, disclaimed as informational | Posted contract documents | Members only, sharing discouraged |
The practical consequence is vehicle shopping. When a reseller holds three or four Oracle-capable co-op contracts, it selects the one whose terms and margin structure suit the seller, not the one whose terms suit you. Before you accept a citation, demand the specific contract number, the participating addendum applicable to your state or system, and the price file version. Then compare it against what a direct negotiation or a federal-style schedule would yield, using the same logic covered in our analysis of Oracle GSA schedule pricing versus commercial quotes, and read the co-op citation alongside the broader public sector Oracle licensing and negotiation guidance before you sign anything.
Every cooperative Oracle quote we review arrives with a percentage attached and no denominator. Ask the reseller which price list edition the percentage runs against and the conversation gets vague, because the answer is usually the Oracle Technology Global Price List effective June 1, 2026 (which superseded the April 16, 2026 edition), while the discount percentage itself was fixed in a solicitation that closed in 2017 or 2018. Anchor the math to published list and the illusion collapses. Database Enterprise Edition is $47,500 per processor and $950 per Named User Plus, with first-year support at $10,450 and $209 respectively. Standard Edition 2 is $17,500 per processor and $350 NUP, support $3,850 and $77. Multitenant is $17,500 per processor ($350 NUP), Real Application Clusters $23,000 per processor ($460 NUP), and NoSQL Database Enterprise Edition $10,000 per processor. Those are the only numbers in the transaction that are not negotiable. In our experience running competitive Oracle negotiations against a hard internal deadline, the discount a buyer can extract at Oracle's quarter end or May fiscal year end regularly exceeds the fixed percentage embedded in a co-op price file, because the co-op number was set once, in the abstract, with no deal to lose. The second half of the problem is support. Support runs at 22 percent of net license fees, calculated off the discounted license number and then escalated annually, so a co-op discount does not reduce the support ratio at all: it only sets the base the ratio multiplies. A 30 percent co-op discount and a 55 percent negotiated discount on the same 20 processors of Enterprise Edition produce two very different 10-year streams, and neither the co-op nor the reseller will build that model for you. Build it yourself before you sign, and compare it the same way you would compare GSA schedule pricing against a commercial quote.
| Line (20 processors, DB EE) | List | Co-op file at 30% | Benchmarked deal at 55% |
|---|---|---|---|
| License | $950,000 | $665,000 | $427,500 |
| Year 1 support at 22% | $209,000 | $146,300 | $94,050 |
| Support, years 1-5, 4% escalation | $1,131,900 | $792,330 | $509,354 |
| 5-year total cost of ownership | $2,081,900 | $1,457,330 | $936,854 |
| Delta vs co-op file | baseline | $520,476 saved |
The table uses list figures from the June 1, 2026 price list and a 4 percent annual support escalation, which is the uplift we see most often in commercial and SLED renewals. Substitute your own quoted percentage and your own uplift cap, then require the reseller to populate the same grid on its letterhead. If the co-op quote cannot beat a benchmarked negotiation on a five-year basis, the vehicle is buying you speed, not money, and you should price that speed explicitly rather than assume it is free.
A co-op discount never touches the 22 percent support ratio, it only sets the base that ratio multiplies for the next ten years.
The financial delta is recoverable at the next renewal. The contractual delta is not, and that is where cooperative buying does its real damage. Read the paper flow carefully: the operative instrument is the Oracle-issued ordering document, which incorporates the NASPO ValuePoint Master Agreement US-GMA-1301562 (AR2487) by reference. You are signing Oracle paper that points back at the co-op, not co-op paper that overrides Oracle. Everything Oracle cares about therefore arrives intact. The audit clause survives. The definitions of Processor and Named User Plus survive, including the multi-core factor table that decides whether your virtualized estate is 8 licenses or 32. The Oracle Partitioning Policy remains what it always was, a non-contractual document Oracle can revise unilaterally and then cite during an audit. Cloud service descriptions, hosted terms, and Oracle's right to update policies without your consent all pass through untouched. AR2487's Attachment B scope compounds this: the vehicle covers cloud line items only, so on-premises licenses, ULA certifications and amendments, hardware, and support reinstatement land on standard Oracle terms anyway. Buyers who assume the co-op umbrella extends over the whole relationship discover otherwise at the worst possible moment, usually when reinstating dropped support triggers back-fees plus penalty at Oracle's discretion.
The E&I structure adds a specific and under-discussed problem. E&I states that contract documentation is for members only, shall not be shared outside a member's institution, and that sharing is detrimental to its ability to negotiate competitive agreements. Read that operationally: it blocks the two activities most likely to surface a bad clause, peer benchmarking with other institutions and independent advisor review. A confidentiality restriction that prevents your licensing counsel from reading the agreement you are about to be bound by is not protecting your pricing, it is protecting the vehicle. Push back in writing, request a member-scoped NDA that expressly permits advisor review, and if it is refused, treat the refusal as data about the quality of the terms inside.
No reseller will open a meeting by telling you the vehicle they are quoting has an expiry date, but the legacy NASPO ValuePoint Cloud Solutions portfolio, which is where most SLED Oracle cloud spend rides today, expires September 15, 2026. It is replaced by a Cloud and Software Solutions portfolio (2026 to 2036) with master agreements effective September 16, 2026, competitively awarded by Lead State Utah to 58 suppliers including Carahsoft, CDW-G, Dell, and Insight. Read that supplier list carefully: it is a reseller pool, not a negotiated Oracle price file. The successor vehicle gives you a compliant path to buy, then leaves the actual Oracle terms and discounts to a quote-by-quote fight you have not yet had. The second trap is uniform expiry. Participating addenda do not run for a fixed number of years from your signature date; they terminate at the master agreement cliff. Alaska's participating addendum to AR2487 runs May 7, 2018 to September 15, 2026, meaning a 2024 signer got roughly two years, not five, of vehicle cover.
| Item | What it says | Buyer consequence |
|---|---|---|
| Legacy NASPO Cloud Solutions portfolio | Expires September 15, 2026 | All Oracle SLED cloud buys under it lose their vehicle on one date |
| Successor Cloud and Software Solutions portfolio | Effective September 16, 2026, runs to 2036, 58 suppliers awarded by Lead State Utah | Reseller pool, not an Oracle-negotiated price file; discounts must be re-fought |
| Oracle master agreement AR2487 (Oracle ref US-GMA-1301562) | Effective March 1, 2017, Lead State Utah, cloud catalog only per Attachment B | On-premises licenses, support renewals, and hardware sit outside the vehicle |
| Alaska participating addendum | May 7, 2018 to September 15, 2026 | Late signers inherit the cliff, not a fresh term |
| OMNIA / Mythics (Region 4 ESC) | Initial term December 12, 2018 to November 30, 2023, renewed to November 30, 2028 | A ten-year price file off one 2018 solicitation |
Practical actions. First, inventory every active Oracle cloud subscription and OCI commitment whose end date falls after September 15, 2026, and confirm in writing which paper survives the cliff: the Oracle ordering document usually incorporates the master agreement by reference, so the commercial terms typically continue for the ordered term while your right to place new orders under the vehicle stops. Get that distinction confirmed by Oracle in the order document, not by a reseller in email. Second, refuse to sign any multi-year subscription whose term extends past a vehicle expiry unless the ordering document restates the pricing, renewal caps, and termination rights in full, standalone language. Third, treat co-op consolidation as a paper-survival mechanism: National IPA, U.S. Communities, and NCPA (acquired by OMNIA in 2022) remain separate legal entities whose lead-agency contracts stay effective for their approved terms, so a 2019-era Oracle price file can be quoted to you in 2026 under fresh OMNIA branding. Ask for the original solicitation date on every quoted vehicle. The same discipline that applies to Oracle licensing in government and public sector procurement applies here: the vehicle is a route, and the route can close under you.
Follow the money before you follow the discount. Cooperative administrative fees are typically paid by the supplier as a percentage of contract sales, which sounds buyer-friendly until you recognize that the supplier funds that fee out of the same margin pool that would otherwise have been available to you as discount. E&I markets rebate opportunities that reward institutional participation, and both OMNIA and E&I earn revenue that scales with volume routed through the vehicle, not with the unit price you achieve. In our negotiation experience, that alignment is the whole story: the co-op's economics improve when you buy more through it, and are indifferent to whether you bought well. Add the structural problem at the order level. The OMNIA Oracle award through Region 4 ESC named Mythics as the sole provider from a competitive solicitation completed years ago, so reseller-versus-reseller competition on your specific transaction does not exist. E&I routes to Mythics as well, now with Emergent, a wholly owned Mythics subsidiary, acting as agent. Where multiple overlapping vehicles exist (legacy MNWNC-123, U.S. Communities OMNIA 180233, OMNIA Iowa OCIO 2019BUS0430, AR2487), the reseller, not the buyer, picks which price file to quote from, and will pick the one most favorable to the seller.
The co-op's economics improve when you buy more through it, and are indifferent to whether you bought well.
Do three things on every quote. Require written disclosure of the cooperative administrative fee percentage and which party remits it. Require the reseller to state its margin on Oracle product and on any bundled services separately. Require identification of every vehicle under which the same configuration could be quoted, with the price under each, then negotiate against the best of them and against a direct Oracle quote. Buyers who apply the same benchmarking discipline used when comparing Oracle GSA schedule pricing against commercial quotes routinely find the co-op is the convenient path, not the cheap one.
Treat the cooperative vehicle as a procurement shortcut and nothing else, then rebuild your leverage in a fixed sequence. First, demand the actual price file and discount schedule in writing, naming the Oracle list edition it references. A discount percentage without a list edition is unmeasurable, and Oracle refreshes list pricing on its own schedule, so a "35 percent off" claim against the June 2026 price list is a different number three months later. Second, run a parallel direct Oracle quote and a second reseller quote off the identical configuration, same SKUs, same quantities, same term length, same metric. In our negotiation experience the co-op number often lands mid-pack rather than best, and you cannot prove that without two comparators. Third, refuse the ordering document as drafted. Oracle's SLED paper incorporates the master agreement by reference, which means the co-op terms sit underneath Oracle's own document rather than above it. Amend the ordering document directly to add an audit notice period, a policy freeze so Oracle cannot change licensing rules mid-term, a cloud price hold at renewal expressed in dollars per unit, and termination for non-appropriation that survives every renewal. Fourth, map every commitment term against the September 15, 2026 NASPO cliff, when the legacy Cloud Solutions portfolio expires and Master Agreements under the 2026-2036 portfolio take effect. Any subscription running past that date needs its post-cliff pricing and terms fixed now, in writing, not deferred to a successor vehicle you have not read. Fifth, require disclosure of the co-op administrative fee and the reseller margin before award. Both are embedded in your unit price. Then read the Oracle public sector licensing and negotiation guide, compare your co-op number against the GSA schedule versus commercial pricing analysis, and pre-position defenses using our page on how Oracle audits agencies and universities differently.
No. Cooperative vehicles guarantee a lawful, pre-competed procurement path, not a benchmarked price. The Oracle-related awards sit on solicitations completed in 2017 and 2018, and resellers still quote transaction by transaction, as TD SYNNEX makes clear when it invites buyers to contact a licensing specialist for a customized quote. Always run a parallel direct quote on the same configuration before you accept a co-op number.
AR2487 is an Oracle America agreement with Lead State Utah, effective March 1, 2017, with Oracle internal reference US-GMA-1301562. Its scope is the Oracle Cloud Services product lines listed on Attachment B that are commercially available at time of order. On-premises licenses, technical support renewals, and hardware fall outside the vehicle and are transacted on standard Oracle paper.
The legacy Cloud Solutions portfolio expires September 15, 2026 and is replaced by a Cloud and Software Solutions portfolio with master agreements effective September 16, 2026, awarded to 58 suppliers. Participating addenda terminate on the same date regardless of when your state signed. If your subscription term extends beyond that date, confirm in writing which agreement governs renewal pricing and terms, or you will be renewing on whatever the successor vehicle or Oracle standard terms provide.
In practice, no. The operative document is the Oracle ordering document, which incorporates the master agreement by reference, so Oracle's audit clause, Processor and Named User Plus definitions, and non-contractual policy documents such as the Partitioning Policy carry through unchanged. If you want protections, they must be negotiated into your ordering document or participating addendum, not assumed from the co-op.
E&I states that contract documentation is for members only and must not be shared outside the member's institution, on the basis that disclosure impairs its ability to negotiate and maintain competitive agreements. The practical result is that you cannot benchmark against peers or hand the terms to an outside advisor without addressing that restriction. Ask E&I for written permission to share with your licensing advisor under NDA before you commit.
Typically the supplier or reseller remits an administrative fee to the cooperative as a percentage of contract sales, and some cooperatives also offer participation rebates to members. That fee is funded from the same margin pool that could otherwise fund your discount. Require the admin fee percentage and reseller margin to be disclosed on the quote so you can see what the convenience is costing you.
The separately-licensed options and packs that ship enabled by default, get switched on with a single click, and become the single largest line item in most Oracle audit findings.
Gated with a work email on the download page. No sales follow up you did not ask for.
Get the White Paper →500+ enterprise clients. 11 vendor practices. Industry recognized. One conversation can change what you pay for the next three years.
One buyer side briefing a week. Renewal signals, audit moves, and the levers that work. No vendor spin.