Department of Motor Vehicles — account brief

Positioning

Written by claude-sonnet-5 from the conversation and the figures below. This section is argument, not record — every figure in it also appears in the profile that follows, which was computed directly from the purchase data with no model involved.

The angle

Position the pitch around Department of Motor Vehicles as a modernization account with heavy Professional & Managed Services spend and a large share of contracts sitting in renewal/rebid territory — not around Oracle as a standalone budget line, since the data here doesn't isolate Oracle-specific dollars. Taborda Solutions' established position ($32.96M, 77 POs) gives a concrete incumbent to reference or displace.

What the data supports

• Scale of the account: 2,134 POs and $1,136,568,891.99 in total scope confirms DMV is a large, active buyer worth the outreach effort — this isn't a niche department.
• Where the money actually sits: Professional & Managed Services leads at $641,504,454.82 across 445 POs, more than Software & Licensing ($474,701,888.92, 1,650 POs) — the commercial opportunity looks more like services/integration work than a licensing upsell.
• Cloud is genuinely small on paper: Cloud & Hosting is just $20,362,548.25 across 39 POs — a thin category relative to the rest of spend, so any "leverage existing cloud contracts" pitch has limited dollar evidence behind it here.
• A known incumbent to engage or challenge: Taborda Solutions shows $32,961,053.60 across 77 POs — a real, sizeable relationship, not a bit player, and a natural reference point for an Oracle-adjacent conversation.
• Heavy renewal churn: 219 contracts expire within 12 months and 1,643 are already expired — a large volume of live or lapsed paper that creates natural re-engagement points, though this dataset doesn't say which of these touch Oracle or database work specifically.
• Statewide contract underuse: only $1,375,498.74 has flowed through the one statewide award in scope, with 25 authorised partners showing no sales here at all — there's an unused procurement vehicle that could be a low-friction entry route.

What to ask

• Of the 219 contracts expiring in the next 12 months, which ones touch database, ERP, or platform modernization work — and who's the buyer on each?
• Is Taborda Solutions' current scope purely licensing/support, or does it extend into professional services — and is that relationship being rebid or renewed as-is?
• What's actually inside the $641.5M Professional & Managed Services line — how much of that is legacy-system integration versus net-new build?
• Why is so little spend routed through the statewide contract vehicle — is that a policy choice, an awareness gap, or a preference for direct sourcing?
• Of the 1,643 "already expired" contracts, how many are functionally still active under rolling extensions versus genuinely lapsed and open to rebid?

What we don't know

• This figure set doesn't isolate Oracle-specific spend at all — the earlier Oracle/OPTM/Mythics/SplashBI numbers discussed in conversation aren't present here, so we can't currently size the Oracle footprint from these figures alone.
• No buyer names are attached to these totals (26 buyers of record, unnamed) — we don't know who owns the renewal

---

Department of Motor Vehicles — procurement profile

Generated 2026-08-03. Scope: product categories Software & Licensing, Cloud & Hosting, Professional & Managed Services.

All figures come from public California procurement exports (eSCPRS / Cal eProcure / FI$Cal). Spend is the purchase order Grand Total as filed by the department, counted once per PO.

At a glance

Install base by product category

Top suppliers

Buyers of record

These are the named buyers on the purchase orders — the procurement officers who actually executed the transaction, taken from the public filing. They are a starting point for routing, not a substitute for identifying the technical decision-maker.

Lifecycle and renewal signals

Three tiers, in descending order of certainty. Do not flatten these into one list — tier 1 is a fact from the filing, tier 2 is a vendor publication, tier 3 is only an age-based prompt to ask a question.

Tier 1 — Confirmed (dated term on the purchase order)

Fact, taken from the PO itself. 1643 expired, 219 expiring within 12 months, 44 later. 1906 PO(s) carry a genuine multi-day term.

Tier 2 — Publicized End-of-Life / End-of-Support (vendor published)

A date here must be accompanied by a source URL. Re-verify against the vendor's own page before putting any of it in front of a client.

No vendor-published dates on file for this scope.

Researched, no published date found — 5 vendor(s). This is a finding, not a gap: it means an end-of-life angle will not carry the conversation for these products. The notes name the exact SKU or vendor page to check by hand.

• Brother — Brother IntelliFAX / FAX-2840 laser fax (2 PO(s), $17,164)
• The request listed the vendor as 'Palo Alto', but that is a location in the PO text (Caltrans Palo Alto construction field offices), not Palo Alto Networks; the product is a Brother FAX-2840 / IntelliFAX-2840 laser fax, identified with high confidence from Brother SKU FAX2840. Brother publishes no per-model lifecycle, end-of-sale, or end-of-support documentation for this device — its support page lists only drivers, manuals and an OS-driver support caveat — and the only 'discontinued' claims found were reseller and marketplace listings, which are not acceptable sources and carried no vendor-p…
• Cisco — Cisco Network Firewall and Switch refresh (11 PO(s), $1,441,103)
• The PO string is a procurement project description covering two entire equipment categories (firewalls and switches), not a Cisco product family or SKU, so no specific lifecycle bulletin applies; Cisco publishes separate EOL notices per platform (ASA 5500-X, Firepower 2100, Secure Firewall Threat Defense, Catalyst switching, etc.) with materially different dates. Note also that 'refresh' may refer to a hardware replacement project or to Cisco Refresh remanufactured equipment, a further ambiguity; a SKU or platform/model number from the BOM is needed before any date can be reported.
• IBM — IBM Z (z15 machine type 8561-T01 and z16 machine type 3931-A01) (72 PO(s), $16,626,881)
• The PO line bundles a support-services SKU (SoftwareXcel enterprise edition for Z) across four serials spanning two distinct machine types (z15 8561-T01 and z16 3931-A01), so no single product can be identified. IBM's own lifecycle pages (node/7092946 for 8561-T01, node/7094360 for 3931-A01) publish GA and end-of-marketing data but leave the end-of-support field empty for both, so no EOSL date exists to report.
• ID.me — ID.me (unspecified) (3 PO(s), $1,328,610)
• The PO line 'ID.me / ID.me' repeats the vendor name and names no specific product, edition, or SKU, so the item could not be confidently identified. Additionally, ID.me is a hosted identity-verification service and no vendor-published end-of-sale or end-of-support lifecycle documentation was located; the only versioned document found was an internal credential-policy revision (v10.1), which is not a lifecycle date.
• Oracle — Oracle Cloud Infrastructure - Object Storage (60 PO(s), $13,429,010)
• Product identified confidently: B89436 is the OCI Object Storage API-request metric SKU for Government regions, where '10,000 req' is a billing unit, not a model. Oracle publishes no End-of-Sale or End-of-Support date for OCI Object Storage or this SKU; it is an active consumption service governed by the Cloud Hosting and Delivery Policies, and OCI EOLs appear in the Service Change Announcements page, which has no Object Storage entry. Caution: dated Oracle EOL notices exist for OCI Storage Gateway (2024-02-28), OCSSA/SSA (2022-06) and Data Transfer (2025-02-06) — these are different products…

Tier 3 — Inferred (age only — no date, and none should be quoted)

Not a prediction. These POs carry no usable contract term and no vendor-published date we could find. They are simply old enough (purchased before 2022-08-04) and in a category where equipment is normally refreshed. The output is a question to ask, never a claim about the department's environment.

Nothing in this scope is both aging and in a refresh-relevant category.

Statewide contract routes

Enterprise Technology Contracts Listing — effective October 1, 2024. 29 OEMs, 38 authorised partners. A purchase order names only the reseller that won it; this names every reseller that could have.

Bought through a statewide contract

$1,375,499 of this scope's spend ran through a statewide contract.

Authorised partners already selling here (10)

Authorised but absent (25)

Hold a statewide award covering these OEMs but have never sold into this scope — the whitespace the purchase data alone can't show.

OEM presence

Name-matched against PO titles and suppliers, so read it as a signal rather than an install-base count.

No presence at all (22): Arista, Checkpoint, Cohesity, Commvault, Cradlepoint, Exagrid, Extreme Networks, Fortinet, Gigamon, Hitachi Vantara, Juniper, Lenovo, NetAPP, Netscout, Netskope, Nokia, Nutanix, Palo Alto, Pure Storage, Rubrik, VAST, Veritas

Contacts

199 named contacts for this department are delivered as a separate file alongside this brief.

They are held apart on purpose. This document is the analysis and is safe to forward, host or print; the contact list is personal data about named individuals and should travel only to the person who commissioned it.

Purchase orders (400 of 2,134, largest first)