Ask a PeopleSoft team how fast they patch, and you’ll hear “we’re current within a quarter.” Ask them to prove it with dates — Oracle’s release date, your test apply date, your production apply date — and the number turns into a story.

CISA set the real benchmark in June: CVE-2026-35273 hit the KEV catalog on June 12 with a remediation deadline of June 15. Three days. And as Monday’s Digest covered, Oracle now ships Critical Security Patch Updates monthly, with the next on August 18.

Here are the five places the time actually goes, and how to measure each one.

Subscribe now

1. You’re still planning around four dates a year

Oracle isn’t. Since May 28, CSPUs land on the third Tuesday of February, March, May, June, August, September, November and December, on top of the quarterly CPUs — with a pre-release announcement the Thursday before each one.

🔗 Critical Patch Updates, Critical Security Patch Updates, Security Alerts and Bulletins (Oracle) https://www.oracle.com/security-alerts/

Measure it: count the security windows on your change calendar for the next 12 months. If the answer is 4, you have designed a 30-60 day lag into every critical fix Oracle ships between quarters. Add the eight CSPU dates, and subscribe to Oracle’s security alert email so the Thursday pre-release reaches a human, not a shared mailbox.

2. Nobody owns the triage window

Between Oracle’s release and your first decision, the patch is public — and so is the vulnerability class. July’s CPU carried 1,449 patches across 1,235 CVEs, of which PeopleSoft took 84, with 45 exploitable over the network without credentials.

🔗 Oracle July 2026 Critical Patch Update Addresses 1,235 CVEs (Tenable) https://www.tenable.com/blog/oracle-july-2026-critical-patch-update-addresses-1235-cves

Measure it: for the last CPU, write down the release date and the date a named person first read the advisory. If that gap exceeds 48 hours, the problem isn’t patching — triage is nobody’s job. Assign it by name, with a backup.

3. You patch the whole CPU or nothing

The all-or-nothing apply is the biggest source of delay: a full CPU means a full regression test, and a full regression test means a quarter. Oracle built CSPUs to break that coupling — targeted fixes in a smaller format, with quarterly CPUs staying cumulative.

Measure it: take July’s PeopleSoft CVE list and mark which entries touch components you actually run. Sites without Global Payroll Switzerland, FIN Common Objects Brazil or In-Memory Project Discovery are testing patches for code they will never execute. A component-scoped applicability list turns a quarterly project into a two-day change.

🔗 Oracle CPU July 2026 Security Update Review (Qualys ThreatPROTECT) https://threatprotect.qualys.com/2026/07/22/oracle-critical-patch-update-july-2026-security-update-review/

4. Your test environment isn’t a copy of production

Every team that misses a window tells the same story: it broke in test, we ran out of time, we deferred. Usually because test drifted — different PeopleTools patch level, different customizations, data from two refreshes ago.

Measure it: run a diff today. Compare PeopleTools release and patch level, applied bundle list, and customization inventory between test and production. Every difference is a false test result waiting to cost you a weekend. It is also the strongest argument for container-based Update Images: an environment you rebuild in a pipeline stops drifting, because it stops being a pet.

5. Your clock starts at the advisory — the attacker’s started earlier

The arithmetic from the last big one: Mandiant observed exploitation of CVE-2026-35273 between May 27 and June 9. Oracle’s advisory came June 10. Even a perfect response was two weeks late, because the race started before the gun.

🔗 Active Exploitation of the Oracle PeopleSoft Zero-Day (Rapid7) https://www.rapid7.com/blog/post/etr-active-exploitation-of-oracle-peoplesoft-zero-day-cve-2026-35273/

Measure it: pick your two most exposed components and ask what compensating control protects them while unpatched. If the answer is “the patch,” you have no answer. Perimeter blocks, egress restrictions and disabled unused services buy the days you don’t have.

Do this once, then make it repeatable

Build one dated table: for the last four Oracle security releases, record release date → triage date → test apply date → production apply date. Four rows, one afternoon. Almost nobody has it.

That table ends the argument. It gives you a real mean time to patch, shows leadership where the days go, and when the next KEV entry lands with a three-day deadline you will already know whether three days is possible — instead of finding out on the day.

Next Thursday: 5 ways to audit PeopleSoft roles and permission lists before someone else audits them for you.

🌐 Join the Community

Subscribe at www.peoplesoftcloud.com for weekly PeopleSoft, ERP, and cloud platform guidance — the Monday Digest for what happened, Thursdays for what to do about it.

Oracle published something this week that is easy to scroll past and expensive to ignore: Prepare Now: Apply Oracle Database Release Update Immediately Upon Availability.

Read it twice. Oracle is not announcing a patch. It is telling customers to have the change window, the test plan, and the inventory already built so the next quarterly Release Update goes on fast when it drops — Oracle Database 19c RU 19.32 and Oracle AI Database 26ai RU 23.26.3, plus the matching Grid Infrastructure, client, and component updates. The next quarterly CPU/RU date is 20 October 2026.

Why the tone changed

This is the follow-through on Oracle’s April guidance, Take Action Today: Protect Your Oracle Database Against AI-Enabled Cybersecurity Threats. The argument there was blunt: frontier AI models are now good enough at finding vulnerabilities that the discovery half of an exploit chain got cheap. Oracle said the April RUs (19.31 / 23.26.2) contained the first wave of fixes for issues surfaced with those models.

If vulnerability discovery accelerates and your patch cadence doesn’t, the gap between “fix exists” and “fix installed” is your exposure window. That’s the whole thesis, and it’s the same reason Oracle added monthly Critical Security Patch Updates this year on top of the quarterly CPUs — next ones 15 September, 17 November, 15 December 2026, with a pre-release announcement the Thursday before.

Oracle also says the quiet part out loud in the new post: the risk is not limited to internet-facing databases. Attackers pivot through compromised apps, credentials, endpoints, and adjacent systems. So the scope is production and DR, test, dev, and supporting infrastructure.

Subscribe now

The PeopleSoft translation

Nothing in that post is PeopleSoft-specific, which is exactly why PeopleSoft shops under-react to it. Three things to be honest about:

1. Your database inventory is bigger than your PROD list. Every PeopleSoft environment refresh clones a database. Demo, PUM source images, that “temporary” 2024 upgrade copy nobody decommissioned — they all run the same binaries and often sit on the same subnet as something that matters. Oracle’s guidance is estate-wide. Yours should be too.

2. Clients and Grid Infrastructure count. Oracle explicitly lists database clients and Grid Infrastructure alongside the RU. In PeopleSoft that means your app server and process scheduler tiers, not just the DB nodes. Patching the database and leaving 19c clients from three years ago on the mid-tier is a half-done job.

3. Your constraint is the change window, not the patch. Nobody in a PeopleSoft shop fails to patch because they can’t find the RU on My Oracle Support. They fail because the CAB slot is 30 days out, the regression suite is manual, and one payroll run is always in the way. Oracle’s advice — test rapidly with representative workloads, use rolling and low-downtime patching, prioritize by exposure — is really advice about removing organizational latency.

What to do this month, before 19.32 exists

• Inventory now. Every database, Grid Infrastructure home, and client, with current RU level and owner. If you can’t produce that list in an hour, that’s the finding.

• Pre-book the window. Ask for the October change slot in August, when it’s cheap to reserve, not in October when it competes with year-end.

• Decide your regression floor. The minimum set of PeopleSoft tests that gates a database RU. Write it down; make it repeatable; stop rebuilding the argument each quarter.

• Use rolling patching where you already paid for it. RAC, Data Guard, out-of-place patching with gold images in 26ai. If you own the capability and still take a full outage, you’re absorbing risk you already bought insurance against.

• Subscribe to the alerts. Oracle’s Critical Patch Updates and Security Alerts page publishes the CSPU pre-release on the Thursday before each release. Free early warning.

My read: the meaningful shift isn’t the patch content, it’s the expectation. Oracle has moved from “stay reasonably current” to “be staged and ready on day zero.” Shops that treat patching as an event will keep sliding a quarter behind. Shops that treat it as a standing pipeline — fixed windows, fixed test set, fixed inventory — will apply 19.32 in days and barely notice.

Pick which one you are before October.

🌐 Join the Community

Subscribe to PeopleSoft Cloud for practical PeopleSoft and Oracle infrastructure analysis: ✅ Weekly ERP Digest every Monday ✅ Practical PeopleSoft every Thursday ✅ No hype, no vendor talking points — just what actually changes your week

Tomorrow — Tuesday, August 18 — Oracle ships a Critical Security Patch Update. Not a quarterly CPU. A monthly one.

That is the story of this edition, and it is bigger than a calendar change. Since May, Oracle has been releasing targeted security fixes on the third Tuesday of eight additional months a year. Meanwhile the July CPU you already applied has been revised twice — Rev 5 on July 30, Rev 6 on August 12. Your patch cycle was built for four events a year. Oracle now generates roughly twelve, plus revisions, plus out-of-band alerts like CVE-2026-35273.

The vendor changed tempo. Most PeopleSoft shops have not.

Let’s get into it.

Subscribe now

🔐 Security: The New Cadence Is Live

🔗 Critical Patch Updates, Critical Security Patch Updates, Security Alerts and Bulletins (Oracle) https://www.oracle.com/security-alerts/

Read the CSPU section, not just the CPU table. The next four CSPU dates are 18 August, 15 September, 17 November, 15 December 2026. A pre-release announcement now lands the Thursday before each one — which means the August pre-release was published August 13 and you could already know what is coming.

🔗 Monthly Critical Security Patch Updates Begin May 28, 2026 (Oracle Security blog) https://blogs.oracle.com/security/update-monthly-critical-security-patch-updates-cspus-begin-may-28-2026

The rationale from Oracle: smaller, focused, high-priority fixes that don’t wait for the quarterly train. Quarterly CPUs stay cumulative and still include everything shipped in the CSPUs.

My read: This is a genuine improvement in Oracle’s posture and a genuine problem in yours. “We patch quarterly” was never great, but it at least matched the vendor. It no longer does. If your change calendar has four security windows on it, you are structurally 30-60 days behind on every critical fix Oracle now ships between quarters. Fix the calendar before you argue about the patches.

🔗 Oracle July 2026 Critical Patch Update Addresses 1,235 CVEs (Tenable) https://www.tenable.com/blog/oracle-july-2026-critical-patch-update-addresses-1235-cves

The largest CPU Oracle has ever released: 1,449 patches, 1,235 unique CVEs, 261 critical. PeopleSoft took 84 patches, 45 of them remotely exploitable without authentication.

🔗 Oracle CPU July 2026 Security Update Review (Qualys ThreatPROTECT) https://threatprotect.qualys.com/2026/07/22/oracle-critical-patch-update-july-2026-security-update-review/

Qualys’ breakdown of the PeopleSoft share: 17 of those CVEs carry critical severity ratings with remote code execution as the outcome.

🔗 CVE-2026-47017 — PeopleTools Process Scheduler (Armis) https://cve.armis.com/CVE-2026-47017

Worth singling out. CVSS 8.7, PeopleTools 8.61 and 8.62 only, improper access control in Process Scheduler: a low-privileged authenticated user can read and modify critical application data by tricking another user into a single HTTP interaction. No known exploitation. Fixed in the July CPU.

My read: 45 unauthenticated-network PeopleSoft CVEs in one quarter, and the one people will actually get burned by is an 8.7 that needs a login and a click. Most shops model the perimeter and ignore the authenticated blast radius. Which is Thursday’s topic — see below.

🧰 PeopleSoft Platform: 8.63, Containers, RECONNECT

🔗 PeopleSoft Monthly Newsletter – August 2026 (Quest Oracle Community) https://questoraclecommunity.org/learn/newsletters/peoplesoft-community-news-2026-august/

Still the single best roll-up: PeopleTools 8.63 GA on OCI, Cloud Manager Image 22, FSCM 9.2.057, Interaction Hub 9.1.022. On-premises 8.63 has still not shipped — Oracle’s line remains “will follow soon.” If your 8.63 plan has a date on it, that date is a guess.

🔗 PeopleSoft Update Image Containers (PeopleSoft Career blog) https://blog.peoplesoftcareer.com/peoplesoft-update-image-containers/

A hands-on walkthrough of the container-based Update Image: three images, Podman runtime, no more VirtualBox appliance download.

🔗 The PeopleSoft Connection, Episode 12 — Modernizing PeopleSoft with AI Enablement and PeopleTools 8.63 (Oracle) https://blogs.oracle.com/peoplesoft/the-peoplesoft-connection-episode-12-modernizing-peoplesoft-with-ai-enablement-and-peopletools-8-63

Oracle’s own product team on where 8.63’s AI features are meant to land. Useful for hearing what Oracle thinks the release is for, versus what the feature list implies.

🔗 RECONNECT Dive Deep 2026 — October 19-22, virtual (Quest) https://questoraclecommunity.org/events/conferences/peoplesoft-reconnect-dive-deep/

150+ sessions, all online, roadmap updates from Paco Aubrejuan, Robbin Velayedam, Richa Dubey and Sasank Vemana. Earliest-bird pricing ends August 21 — this Friday.

My read: Register now if you’re going. Not for the discount — because the roadmap sessions are where you’ll find out whether on-prem 8.63 lands in 2026, and that answer changes upgrade budgets.

💰 Oracle’s Balance Sheet Is Now a Planning Input

🔗 Oracle goes for high-stakes ratings gamble in AI strategy (Reuters via Yahoo Finance) https://finance.yahoo.com/technology/ai/articles/analysis-oracle-corp-goes-high-171918690.html

S&P cut Oracle to BBB- in July — one notch above junk. Debt of $129.5B, roughly 4.3x EBITDA, plus ~$260B in data center leases that don’t yet count as debt but that analysts count anyway.

🔗 Oracle plans fresh August layoffs as its AI spending spree bites (TNW) https://thenextweb.com/news/oracle-august-2026-layoffs-ai-capex

Another round this month, per Business Insider, some teams facing double-digit-percentage cuts, targeted to land before September 1. Context: ~21,000 roles gone in FY2026 (162k → ~141k), $1.8B in restructuring charges booked, capex $55.7B against $21.2B a year earlier.

🔗 Oracle’s AI Data Center Funding Tests OCI Delivery Timelines (TechRepublic) https://www.techrepublic.com/article/news-oracle-ai-data-center-funding/

The buyer-side framing: $638B in remaining performance obligations, negative $23.7B free cash flow, ~$40B more debt and equity expected in FY2027. The advice is unglamorous and correct — verify delivery dates, power availability, and contract protections before committing to future OCI capacity.

🔗 Oracle Gets Cheaper Only If The Megawatts Arrive (Trefis) https://www.trefis.com/stock/orcl/articles/611550/oracle-gets-cheaper-only-if-the-megawatts-arrive/2026-08-14

Consensus assumes ~39% annual revenue growth against 17.4% actually delivered over the trailing year, with FY2027 gross margin stepping down as data centers ramp. The valuation rests on construction, not software.

My read: I don’t care about the stock. I care that the company holding my support contract is spending like a utility and cutting like a turnaround. Two consequences worth acting on: test support responsiveness on niche PeopleSoft modules before you depend on it, and put delivery-date language in any OCI capacity commitment past next year. UBS cut its target to $245 from $285 on August 7 partly over a construction delay at one New Mexico site — if a bank’s model bends on one site’s power schedule, so can your migration plan.

🤖 The Agent Layer Arrives in the App Layer

🔗 Oracle Adds New Fusion Agentic Applications and AI Agents for Talent Management (Oracle) https://www.oracle.com/news/announcement/oracle-adds-new-fusion-agentic-applications-and-ai-agents-to-help-improve-talent-management-2026-08-11/

Announced August 11: agent teams for job design, skills profiles, learning, manager coaching, internal mobility and workforce planning — acting inside business processes with access to enterprise data, approval hierarchies and permissions.

🔗 Oracle Turns AI Agents Loose on Talent Management Tasks (UC Today) https://www.uctoday.com/productivity-automation/oracle-ai-agents-talent-management/

The skeptical read of the same launch, and the detail that matters most: the Intelligent Talent Profiles Agent infers employee skills from connected work-system data.

My read: Agentic HCM is where the PeopleSoft-vs-Fusion conversation gets real again. An agent that infers skills from work-system data is exactly the pitch that makes a CHRO ask why HR data still lives in a system nobody’s touched since the last upgrade. Note the asymmetry: PeopleSoft 8.63 gets AI in the developer loop, Fusion gets AI in the business process. That gap is the actual roadmap story, and it will not narrow.

💬 Aaron’s Take

The through-line this week is tempo. Oracle has accelerated everything — security releases from 4 to ~12 a year, feature delivery through continuous images, capital deployment at 2.6x last year’s rate — and PeopleSoft shops are still running annual planning cycles against it.

Three things to do this week:

• Put the CSPU dates on the change calendar today. August 18, September 15, November 17, December 15. Subscribe to the Thursday pre-release announcements so you get 5 days of warning instead of zero.

• Confirm which PeopleTools release you’re actually on. Both fresh PeopleSoft CVEs this quarter affect 8.61 and 8.62 only. Knowing your version is not the same as knowing your patch level — check both, in writing.

• Register for RECONNECT before Friday if the on-prem 8.63 date affects your 2027 budget. The roadmap sessions are the cheapest intelligence available to you all year.

And one thing not to do: don’t treat 45 unauthenticated CVEs as a perimeter problem. The perimeter was Edition 31’s story. The authenticated interior is Thursday’s.

This Thursday: 5 Reasons Your PeopleSoft Patch Cycle Is Slower Than Your Attackers — where the days actually go between Oracle’s release and your production apply.

🌐 Join the Community

Subscribe at www.peoplesoftcloud.com for weekly PeopleSoft, ERP, and cloud platform guidance.

✅ Monday: the Digest — what happened and what it means for your environment ✅ Thursday: practical, verifiable actions you can run this week ✅ Always: primary sources, real numbers, no vendor press-release energy

Good. Patching was the easy part. The uncomfortable part is that the vulnerability was only interesting because those endpoints were reachable from the internet in the first place — and patching doesn’t change that. /PSEMHUB/hub and /PSIGW/HttpListeningConnector are still exposed in most environments I’ve seen, still answering requests from anyone who asks.

“We patched it” is a claim. Here are five ways to turn it into evidence.

Subscribe now

1. Enumerate from the outside, not from the inside

Your network diagram is not evidence. It describes intent, not reality — and it was accurate the day it was drawn.

Censys counted roughly 40 internet-facing PeopleSoft hosts worldwide during the exploitation window, and called that a conservative estimate. Separately, IPinfo surfaced 24 live PeopleSoft instances across 16 organizations from a single day of scraped web data — without sending a single packet at any target.

🔗 Finding exposed PeopleSoft instances using web scrape data (IPinfo) https://community.ipinfo.io/t/finding-exposed-peoplesoft-instances-using-ipinfos-web-scrape-data/7376

That’s the test that counts: can a stranger find you without trying? Get an external view of your own perimeter — a scan from a cloud host, a Censys or Shodan query on your domains and ASN — and compare it to what you believe is published. The gap is your actual attack surface.

2. Curl the two paths from a network you don’t control

Not from the DMZ. Not from the VPN. From a coffee shop, or a $5 VM.

Request /PSEMHUB/hub and /PSIGW/HttpListeningConnector on every PIA URL you own — prod, test, dev, and the one somebody stood up for a 2019 project and never decommissioned. A connection refused or a perimeter-level block is a pass. An HTTP response of any kind is a finding, including a 401 or a 404.

Rapid7 is specific on this point, and it matters: block these at the network perimeter, not with WAF body-inspection rules alone.

🔗 Active Exploitation of the Oracle PeopleSoft Zero-Day (Rapid7) https://www.rapid7.com/blog/post/etr-active-exploitation-of-oracle-peoplesoft-zero-day-cve-2026-35273/

3. Decide whether EMHub should exist at all

Most sites do not need the Environment Management Hub running, and almost none need it published. The guidance from multiple responders converged: disable the EMHub service in multi-server configurations, or remove the PSEMHUB application entirely in single-server deployments.

🔗 Defending Against the PSEMHUB Authentication Bypass (Qualys ThreatPROTECT) https://threatprotect.qualys.com/2026/06/18/cve-2026-35273-defending-against-the-oracle-peoplesoft-psemhub-authentication-bypass/

There is a real cost — you lose Change Assistant’s environment discovery — and you should decide that deliberately rather than leave it running because nobody asked.

4. Check egress, not just ingress

The RCE got them in. Outbound SMB on TCP/445 is what let them harvest machine-account NetNTLM hashes and move.

Almost nobody audits this. Your PeopleSoft web and app tiers should not be able to open arbitrary outbound connections to the internet. Verify that from the host, not from the firewall policy — try it and watch it fail.

5. Know what your login page volunteers

Attackers pick targets by fingerprint. Sign-in pages leak PeopleTools version, server names, and full internal hostnames in redirects and error pages. And one rule worth writing on the wall: PeopleSoftListeningConnector should never be the target of an external integration — that’s what HttpListeningConnector behind a proxy is for.

🔗 PeopleSoft Online Security (Oracle docs) https://docs.oracle.com/cd/F70249_01/pt860pbr1/eng/pt/tsec/PeopleSoftOnlineSecurity-c0765d.html

Do this once, then make it repeatable

CISA added CVE-2026-35273 to the KEV catalog on June 12 with a remediation deadline of June 15 — three days. That is the tempo now, and you will not meet it by starting from scratch each time.

So produce an artifact: a dated list of every PeopleSoft URL you own, what each one exposes externally, and who signed off. Re-run it quarterly. When the next 9.8 lands — and it will — the question won’t be “are we patched?” It’ll be “what’s reachable?” You should already have that answer written down.

Next Thursday: why your patch cycle is slower than your attackers, and the four handoffs where the time actually goes.

🌐 Join the Community

Subscribe at www.peoplesoftcloud.com for weekly PeopleSoft, ERP, and cloud platform guidance — the Monday Digest for what happened, Thursdays for what to do about it.

Edition 30 went out in April. It’s August. Let’s not pretend otherwise.

The gap wasn’t for lack of news — it’s that I’ve been heads-down building. But the four months I was quiet turned out to be the most consequential stretch for PeopleSoft shops in years: a 9.8-severity zero-day exploited in the wild before Oracle knew, PeopleTools 8.63 landing with AI baked into the developer experience, the VirtualBox DPK finally being put out to pasture, and Oracle shedding 21,000 people while booking a $638 billion backlog.

So this edition is a catch-up. One theme ties it together:

Oracle is spending its balance sheet on AI infrastructure and its headcount on the bill. PeopleSoft customers are the ones who have to plan around that.

Let’s get into it.

Subscribe now

🔐 Security: The One You Cannot Defer

🔗 Oracle Security Alert CVE-2026-35273 https://www.oracle.com/security-alerts/alert-cve-2026-35273.html

A CVSS 9.8 unauthenticated RCE in the PeopleTools Updates Environment Management component. PeopleTools 8.61 and 8.62 affected. Oracle shipped an out-of-band patch the same day it disclosed — June 10 — which tells you how bad it was.

🔗 Rapid7: Active Exploitation of the PeopleSoft Zero-Day https://www.rapid7.com/blog/post/etr-active-exploitation-of-oracle-peoplesoft-zero-day-cve-2026-35273/

The detail that should keep you up: Mandiant observed exploitation between May 27 and June 9 — two weeks before Oracle’s advisory. Added to CISA KEV on June 12. Entry points were /PSEMHUB/hub and /PSIGW/HttpListeningConnector, with outbound SMB used to harvest machine-account NetNTLM hashes. Roughly 100 organizations targeted, education hit hardest.

My read: I wrote about the ShinyHunters campaign back in June. Two months on, the interesting question isn’t the CVE anymore — it’s whether your PSEMHUB and Integration Broker endpoints are still reachable from the internet at all. The patch closed one door. The architecture that exposed it is still there in most shops.

🧰 PeopleTools 8.63: AI Arrives in the Developer Loop

🔗 Quest PeopleSoft Community Newsletter – August 2026 https://questoraclecommunity.org/learn/newsletters/peoplesoft-community-news-2026-august/

The release wave in one place: PeopleTools 8.63 is GA on Cloud, FSCM 9.2.057 posted, Cloud Manager Image 22 available, Interaction Hub 9.1.022 posted. RECONNECT Dive Deep registration is open.

What’s actually new in 8.63 is worth more than a version bump — Oracle put AI where developers and admins live: an AI Assistant inside Application Designer, the “Magic Button” for faster AI enablement, smarter Search, Customization Group Insights, and improved access controls.

My read: Customization Group Insights is the sleeper. Every modernization conversation I’ve ever sat in stalls on the same question — what did we actually customize, and does anyone still need it? Teams answer that with spreadsheets and folklore. Tooling that answers it from the metadata changes the economics of a roadmap. If you’re planning an assessment, 8.63 is now a prerequisite, not an upgrade.

📦 The VirtualBox DPK Era Is Ending

🔗 Coming Soon – PeopleSoft Update Images on Containers (Oracle PeopleSoft blog) https://blogs.oracle.com/peoplesoft/peoplesoft-images-on-containers

Update Images are moving to containers: three images — database, midtier, Insights — pre-installed, one command to start, Podman as the recommended runtime.

🔗 The PeopleSoft VirtualBox DPK Is Dying. Here Is What Replaces It. https://www.linkedin.com/pulse/peoplesoft-virtualbox-dpk-dying-here-what-replaces-derek-tomei-ekkve

A practical walkthrough of the shift: FSCM Update Image 57 ships with a container deployment option. Load three images into Podman, edit four files, launch the stack.

My read: This is the change I’ve been waiting years for, and it’s bigger than convenience. A DPK build was an afternoon and a coin flip. A container pull is a step in a pipeline. Once PUM environments are declarative and disposable, “we only have one test environment” stops being a constraint you defend and starts being a decision you made. That’s the door to real CI for PeopleSoft.

💰 Oracle’s Numbers: Record Everything, Minus 21,000 People

🔗 Oracle Announces Record Q4 and FY 2026 Results https://investor.oracle.com/investor-news/news-details/2026/Oracle-Announces-Record-Q4-and-FY-2026-Results-Driven-by-Cloud-Infrastructure--Cloud-Applications/default.aspx

FY26 revenue $67.4B (+17%). Cloud $34B (+39%). Q4 IaaS $5.8B, up 93%. And the number that matters: RPO of $638B, up 363% YoY, after growing $85B in a single quarter. Backlog is now roughly ten times annual revenue. Reported capex plans run near $95B, with only ~12% of that backlog expected to convert inside 12 months.

🔗 Oracle sheds 21,000 roles over the past year (CNBC) https://www.cnbc.com/2026/06/23/oracle-ai-job-cuts-layoffs-21000.html

Headcount down from 162,000 to 141,000 — about 13% — with AI deployment cited in the annual filing.

🔗 Oracle layoffs hit sales, engineering, security (CRN) https://www.crn.com/news/ai/2026/oracle-layoffs-hit-sales-engineering-security-5-things-to-know

🔗 Layoffs continue into a second month across US, India, Philippines (DCD) https://www.datacenterdynamics.com/en/news/oracle-continues-widespread-layoffs-across-us-india-philippines-and-beyond/

Cuts extending into OCI, Oracle Health, Advanced Customer Services and NetSuite teams.

My read: Put those two links side by side and you have the only Oracle story that matters to a PeopleSoft customer this year. Cloud infrastructure growing 93% while Advanced Customer Services gets thinned is not a contradiction — it’s a stated priority. Practically: assume slower SR turnaround, more churn in your account team, and more of the burden of “knowing your own system” landing on you. Own your runbooks. Document your integrations. Do not architect on the assumption that a support engineer will remember your environment.

🤖 ERP Strategy: Is AI Ending the ERP Era?

🔗 Does AI Mark The End Of The ERP Era? (IT Jungle) https://www.itjungle.com/2026/07/27/does-ai-mark-the-end-of-the-erp-era/

A good walk through McKinsey’s five scenarios for the ~$100B ERP market, including the radical one where agents replicate ERP capability outright and logic becomes a commodity. It also revisits the early-2026 “SaaSpocalypse” selloff that took hundreds of billions off SaaS-ERP market caps.

🔗 What’s New in Oracle AI – August 2026 (Oracle Blog) https://blogs.oracle.com/ai-and-datascience/whats-new-in-ai-august-2026

OCI Enterprise AI: IAM authentication on hosted app endpoints, H100 multi-node serving for imported models, expanded on-demand model availability. Also: Oracle AI World, Las Vegas, October 25–28, 2026.

My read: I don’t buy the disintegration thesis, and this is the third year running I’ve said so. Agents are extremely good at processes and extremely bad at being the system of record for a regulated general ledger. What actually erodes is the layer we spent twenty years defending — the customizations, the bolt-on reporting, the human-in-the-loop shuffling between screens. That’s the part agents eat. The ledger stays.

Which is why 8.63’s AI-in-App-Designer and Customization Group Insights are the more honest signal about where this goes than any market-cap swing.

💬 Aaron’s Take

Four months away gave me a cleaner view of the pattern.

Every item above is the same story told in a different register. Oracle is redirecting enormous capital toward AI infrastructure. It is funding part of that by reducing the human surface area of everything that isn’t AI infrastructure — including the support and services layer PeopleSoft customers have leaned on for two decades. At the same time, it’s shipping genuinely useful tooling into PeopleSoft: containers, metadata insight, AI in the developer loop.

The read is not “Oracle is abandoning PeopleSoft.” The tooling is too good for that. The read is:

Oracle is handing you better tools and expecting you to need less help using them.

That’s a fair trade if you’re ready for it, and a serious problem if your operating model assumes someone else holds the institutional knowledge about your environment.

So, the four things worth doing this quarter:

• Patch, then verify exposure. 8.61/8.62 patched is table stakes. Get PSEMHUB and Integration Broker off the public internet. • Get to 8.63. Not for the version — for Customization Group Insights and the assessment work it unlocks. • Pilot container Update Images. Podman, one Image, one non-prod. Prove the pipeline before you’re forced to. • Write down what only you know. Runbooks, integration inventories, batch dependencies. Assume the outside expert is gone.

None of that is a modernization program. All of it is what makes one possible.

🌐 Join the Community

If you want to stay current on ERP strategy, PeopleSoft innovation, and cloud platform trends, subscribe at www.peoplesoftcloud.com.

Each week you’ll get: ✅ Curated ERP and PeopleSoft insights ✅ Context around AI and cloud developments ✅ Practical, real-world guidance

Edition 31, back on schedule. Thanks for still being here.

If you run PeopleSoft, that sentence is supposed to make your stomach drop. And the migration crowd is already using it to make a familiar argument: see, this is what happens when you stay on legacy software. Move to SaaS and let the vendor own the security.

That argument is wrong, and the details of this breach are exactly why. Let me walk through what actually happened, and what it does and doesn’t say about the platform you’re running.

What happened

Between May 27 and June 9, 2026, a financially motivated group called ShinyHunters, tracked by Google’s Mandiant as UNC6240, exploited a previously unknown flaw in Oracle PeopleSoft PeopleTools. Oracle didn’t publish its advisory until June 10. The attacks had been running in the wild for two weeks before anyone outside the attacker’s circle knew the vulnerability existed. This was a true zero-day.

The flaw is tracked as CVE-2026-35273. It carries a CVSS score of 9.8 out of 10. It is unauthenticated, remotely exploitable, and low-complexity. There is no need for login, no stolen credentials, and no user clicking anything. Just network access over HTTP. TrendAI’s Zero Day Initiative, which reported it to Oracle, classified the root cause as server-side request forgery that chains into remote code execution.

The damage was concentrated where it hurts. According to Mandiant, 68% of the notified organizations were in higher education. Overwhelmingly, U.S. colleges and universities are the exact shops that run Campus Solutions, housing student PII, financial aid records, and billing data. The University of Nottingham was among the first confirmed victims; ShinyHunters reportedly stole 40GB covering 450,000 current and former students and posted it to their leak site on June 9 after the university declined to pay. CISA added the CVE to its Known Exploited Vulnerabilities catalog on June 12.

So far, this reads like a vendor problem. Here’s the part that should change how you think about it.

Subscribe now

The vulnerability was in the part you forgot was exposed.

The flaw lives in the Updates Environment Management component — the machinery behind the Environment Management Hub, PSEMHUB. Mandiant’s analysis points to two endpoints: /PSEMHUB/hub and /PSIGW/HttpListeningConnector.

Read that again. The breach didn’t come through the front door that your users log in to every day. It came through environment-management plumbing. Most organizations stood up their infrastructure years ago, configured it once, and never thought about it again. The attack only works if that machinery is reachable from an untrusted network.

That is the whole ballgame. Oracle itself describes the vulnerability as easily exploitable and remotely reachable, which makes external exposure the single biggest risk multiplier. The organizations that got hit had PeopleSoft components exposed to the internet that had no business being exposed. In many cases, security teams didn’t even know those endpoints were reachable. They were simply forgotten DNS records pointing at legacy endpoints, a hub that was supposed to be internal but wasn’t, a reverse proxy that was more permissive than anyone remembered.

This is not a “PeopleSoft is old” problem. This is an attack-surface-management problem. An attack surface is something you control, not something the platform inflicts on you.

What this says about “let the vendor own security”

The migration pitch says SaaS makes the patching problem disappear. It doesn’t. It moves it somewhere you can’t see and can’t act on.

The post-mortem on this campaign reads like a competence checklist, not a platform indictment. Mandiant found that the attackers extracted credentials from psappsrv.cfg, mapped connected nodes, and walked the web, app, and batch tiers. This requires AI and a deep familiarity with PeopleSoft architecture, yes, but every one of those moves is something a properly segmented, properly monitored environment makes harder. The organizations that had their app servers walled off from untrusted networks, that watched outbound SMB traffic, that didn’t have PSEMHUB hanging off a public IP, were a far harder target.

Note also what ShinyHunters is known for. This is a group that usually wins through weak authentication, stolen credentials, and cloud misconfigurations, not exotic malware. That profile should be clarifying. The same crew constantly breaches SaaS platforms and cloud services. Moving your HR and finance data into someone else’s tenant doesn’t take you off their menu. It just means that when the next misconfiguration occurs, you find out about it via a breach notification email rather than in your own logs.

The honest framing is this: security is an operational discipline, and operational discipline is exactly the thing you keep when you modernize in place and lose visibility into when you hand the whole stack to a vendor.

The one-person problem this exposed

There’s an uncomfortable staffing truth underneath this incident, and it’s worth saying to the executive who controls the headcount.

A large share of PeopleSoft shops run with one person owning PeopleTools, security configuration, environment management, and patching. On a normal week, that’s a workload problem. During an actively exploited zero-day, when the same person is suddenly responsible for emergency mitigations, log hunting, and exposure assessment against attackers already inside the perimeter, it becomes an incident-response failure waiting to happen.

That risk has nothing to do with whether PeopleSoft is modern. A single-threaded SaaS admin is just as exposed; you’ve simply outsourced the parts they can no longer touch. The lesson isn’t “the platform is fragile.” It’s “we under-resourced a system that runs payroll, finances, and student records, and the bill came due.” This breach is the business case for fixing that.

What the CIO should actually do

Four moves. None of them is “evaluate migration.”

Find out what’s actually exposed — today. The exploit needs network reachability to PSEMHUB and Integration Gateway endpoints. Confirm whether anything PeopleSoft-related answers from outside your trusted network: /PSEMHUB/*, /PSIGW/*, the PIA and app server tiers. Don’t trust the assumption that PeopleSoft is “internal.” Check public DNS records, legacy endpoints, and anything a reverse proxy might be quietly forwarding. Even if you patched, exploitation started May 27. Assume you need to hunt for a prior compromise, not just close the door.

Patch, then verify you weren’t already hit. Oracle released mitigations with the June 10 alert and folded fixes into the June 2026 Critical Security Patch Update. Apply them. Then review web and app server logs for suspicious requests to those endpoints, watch for unexpected outbound SMB connections from PeopleSoft hosts, and look for unfamiliar files or processes. A patch closes the future; it says nothing about the two weeks the door was open.

Treat environment-management infrastructure as a first-class attack surface. What got people wasn’t the application; it was the operational scaffolding around it. Inventory every PeopleSoft endpoint, segment the tiers, put the management hub behind authentication or off the network entirely, and monitor it as it matters. Because it does.

Fund the team, or accept the risk in writing. If one person owns tooling, security, environments, and patching, you do not have an incident-response capability; you have a single point of failure with a pulse. Decide deliberately whether that’s acceptable for a system holding your most sensitive records, and make whoever owns the risk sign off on the answer.

The actual lesson

CVE-2026-35273 is a serious vulnerability, and Oracle’s two-week disclosure gap is a fair reason to be angry. But the organizations that weathered it well and the ones that ended up on a leak site weren’t separated by how old their ERP was. They were separated by whether they knew what they had exposed, whether they segmented it, and whether they had more than one person watching it.

That’s not a migration decision. That’s a management decision. The question was never whether to abandon the platform. It’s whether you’re operating it like it carries the weight it actually carries.

Run the exposure check this week. Not because PeopleSoft is fragile, but because every system that holds payroll and student data deserves to be treated like an asset, and right now, you have a concrete reason to prove yours is.

Aaron Engelsrud writes about PeopleSoft modernization, cloud infrastructure, and ERP strategy at peoplesoftcloud.com.

The Monday morning of Week 5 started with an argument.

Maya walked into the office at 7:30 AM to find Jake sitting at his desk, arms crossed, staring at his monitor with an expression that could curdle milk.

“Morning,” Maya said cautiously.

“We need to talk,” Jake said.

Maya set down her coffee. “Okay. What’s up?”

“I got your email last night,” Jake said. “The one about Week 5 plans. Database modernization using Oracle Cloud Exadata.”

“Right,” Maya said. “That’s the plan for this week—”

“You want to move our databases to a managed service,” Jake interrupted. “You want to give Oracle control of our databases.”

“I want us to use Oracle Exadata on Google Cloud,” Maya corrected. “Which is Oracle’s engineered system running on GCP infrastructure. It’s still Oracle Database, still fully featured, still something you have administrative access to.”

“But Oracle manages the infrastructure,” Jake said. “The storage, the patching, the high availability configuration. We lose control.”

“We lose operational burden,” Maya countered. “There’s a difference.”

Subscribe now

“Maya, I’ve been a DBA for twenty-six years,” Jake said, his voice tight. “I know how to manage Oracle databases. I know how to tune, optimize, and keep them running. You’re asking me to hand that over to a service that I can’t see inside of, can’t customize the way I want, can’t—”

“Can’t spend forty hours a quarter patching?” Maya suggested gently. “Can’t spend weekends troubleshooting storage performance? Can’t wake up at 3 AM when a backup script fails?”

Jake was quiet.

Maya sat down next to him. “Walk me through what you’re really worried about.”

Jake took a breath. “I’m worried that if we move to managed Exadata, my job becomes irrelevant. If Oracle handles the infrastructure, the backups, the patching, the high availability—what’s left for me to do? I become a glorified report writer. And then in a year, someone asks why we’re paying a DBA salary for work that doesn’t require a DBA.”

“Is that what you think I’m trying to do?” Maya asked. “Eliminate your position?”

“I don’t know,” Jake said honestly. “Two months ago, we were running PeopleSoft the traditional way. Now we’re doing infrastructure-as-code, observability platforms, and cloud migrations. Every week, something I used to do manually gets automated. At some point, you automate me out of a job.”

Maya was quiet for a moment, choosing her words carefully.

“Jake, do you remember last week? When we built the observability dashboards?”

“Yeah.”

“Who configured Oracle to export those metrics?” Maya asked. “Who knew which wait events matter for PeopleSoft performance? Who explained why we should monitor the DB file sequential read versus the DB file scattered read?”

“I did,” Jake said.

“Right. Because you understand Oracle performance at a level none of us do. Now let me ask you something else: how much time do you spend per month on tasks that require that deep expertise versus tasks that are just… keeping the lights on?”

Jake thought about it. “Maybe twenty percent on actual performance tuning and optimization. The rest is backups, patches, monitoring disk space, restarting failed jobs, dealing with tablespace extensions—”

“Operational toil,” Maya finished. “Important work, but not work that requires twenty-six years of expertise. What if we could flip that ratio? What if eighty percent of your time was spent on performance optimization, data architecture, query tuning, and helping developers write better SQL? What if the tool got automated?”

“That’s what managed Exadata does?” Jake asked skeptically.

“That’s what it enables,” Maya said. “Let me show you something.”

She pulled up a document she’d been working on over the weekend: a detailed comparison of their current Oracle environment versus Oracle Exadata on GCP.

Current State: Oracle Database on Self-Managed RAC

Jake’s Time Allocation (Monthly):

• Backup management and monitoring: 12 hours

• Patch management and testing: 16 hours (quarterly spike: 40 hours)

• Storage management: 8 hours

• High availability configuration and testing: 6 hours

• Performance monitoring: 10 hours

• Performance tuning and optimization: 8 hours

• Incident response and troubleshooting: 12 hours

• Capacity planning: 4 hours

• Documentation and runbooks: 4 hours

Total: 80 hours/month on average

Breakdown:

• 70% operational toil (backups, patches, storage, HA, monitoring, incidents)

• 30% strategic work (optimization, tuning, capacity planning)

Maya scrolled down to the next section.

Future State: Oracle Exadata Database Service on Google Cloud

Jake’s Time Allocation (Monthly):

• Backup management: 0 hours (automated by Oracle)

• Patch management: 2 hours (reviewing and approving automated patches)

• Storage management: 0 hours (automated scaling)

• High availability configuration: 0 hours (built-in, automated)

• Performance monitoring: 4 hours (dashboard review, alert investigation)

• Performance tuning and optimization: 30 hours

• Query optimization and developer support: 20 hours

• Data architecture and design: 15 hours

• Capacity planning: 3 hours (simplified with automated scaling)

• Strategic database projects: 6 hours

Total: 80 hours/month

Breakdown:

• 8% operational toil (patch approval, monitoring, capacity planning)

• 92% strategic work (optimization, tuning, architecture, developer support)

Jake studied the comparison. “You’re saying I’d spend the same amount of time, just on different things.”

“Not just different things,” Maya said. “More valuable things. Things that actually leverage your expertise. Right now, you’re spending twelve hours a month babysitting backups. Oracle’s Exadata service handles that automatically with built-in snapshot capabilities and point-in-time recovery. Those twelve hours could be spent optimizing SQL queries that are costing us database performance.”

“But what about when something goes wrong with the backups?” Jake asked.

“Then Oracle’s support team troubleshoots it,” Maya said. “Because it’s their infrastructure, their responsibility. You’re not on call at 3 AM because a backup script failed. They are.”

“And if I need to tune something at the storage layer?” Jake pressed.

“You can’t,” Maya admitted. “Because Oracle’s engineers optimize Exadata’s storage layer. But here’s the thing—when was the last time you actually needed to tune storage parameters for performance?”

Jake thought about it. “Honestly? Not in years. We set it up correctly initially, and it’s been stable since then. Most performance issues are bad SQL or missing indexes, not storage configuration.”

“Exactly,” Maya said. “So we’re protecting your ability to tune something you rarely need to tune, at the cost of you spending twelve hours a month managing backups you shouldn’t have to think about.”

She pulled up another document. “Let me show you the cost analysis. Because this isn’t just about your time—it’s about total cost of ownership.”

Current State: Self-Managed Oracle RAC on Premise

Infrastructure Costs:

• Database servers (2 nodes): $180K capital (5-year depreciation: $36K/year)

• Storage (SAN): $240K capital (5-year depreciation: $48K/year)

• Network equipment: $40K capital (5-year depreciation: $8K/year)

• Data center space, power, cooling: $24K/year

• Hardware maintenance contracts: $32K/year

Software Costs:

• Oracle Database Enterprise Edition licenses: $94K (already owned)

• Oracle RAC licenses: $47K (already owned)

• Oracle support contracts (22% annually): $31K/year

Personnel Costs:

• Jake’s time on database infrastructure: 80 hours/month × $85/hour = $81,600/year

• Infrastructure team support: $24K/year

Total Annual Cost: $284,600/year

Maya scrolled to the comparison.

Future State: Oracle Exadata Database Service @ Google Cloud

Infrastructure Costs:

• Exadata X9M Quarter Rack: $168,000/year (consumption-based pricing)

• Includes: compute, storage, networking, all infrastructure

• Includes: automated backups, patching, and high availability

• Includes: Oracle’s 24/7 infrastructure support

Software Costs:

• Oracle Database Enterprise Edition: included in Exadata service

• Oracle RAC: included in Exadata service.

• Oracle support: included in Exadata service

Personnel Costs:

• Jake’s time on database infrastructure: 6 hours/month × $85/hour = $6,120/year

• Jake’s time on strategic work: 74 hours/month (no additional cost, reallocated time)

• Infrastructure team support: $0 (no longer needed)

Total Annual Cost: $174,120/year

Annual Savings: $110,480

Jake stared at the numbers. “We’d save $110,000 per year by moving to Exadata?”

“And that’s conservative,” Maya said. “I didn’t account for the cost of our time during the quarterly patch cycles. I didn’t include the cost of storage upgrades every three years. I didn’t factor in the opportunity cost of incident response time. The real savings are probably closer to $140,000 annually.”

“But we already own the hardware,” Jake protested. “That’s sunk cost.”

“True,” Maya said. “But the hardware is six years old. In two years, we’ll need to replace it. That’s another $460,000 capital expense that we can avoid entirely by moving to Exadata as a service. Plus, we can decommission the data center space and stop paying for power and cooling.”

“What about the Exadata cost?” Jake asked. “That’s $168,000 per year. That’s not cheap.”

“It’s not,” Maya agreed. “But it’s less than what we’re spending now, and it includes things we currently pay for separately—software licenses, support contracts, infrastructure maintenance. Plus, it scales. Right now, if we need more database capacity, we have to buy another SAN array and another server. Six-month lead time, huge capital expense. With Exadata on GCP, we can scale up in hours by adjusting our consumption tier.”

Jake was carefully reading the cost breakdown. “You said Jake’s time on database infrastructure drops to six hours per month. What are those six hours?”

“Reviewing automated patch schedules and approving them, checking capacity trends, and investigating any performance alerts that come through observability,” Maya said. “The stuff that actually requires your judgment. Everything else—the backups, the storage management, the HA configuration, the routine monitoring—that’s handled by Oracle’s automation.”

“And the other seventy-four hours I’m supposedly spending on strategic work,” Jake said. “What does that actually look like?”

Maya pulled up a new document. “I’m glad you asked. I’ve been thinking about this a lot. Here’s what a modern DBA role looks like when you’re not buried in operational toil.”

The Strategic DBA: Redefining Value

Performance Optimization (30 hours/month):

• Proactive SQL tuning based on observed query patterns

• Identifying and fixing performance anti-patterns

• Working with application developers on database-efficient code

• Analyzing and optimizing batch job performance

• Eliminating performance bottlenecks before users notice them

Data Architecture (15 hours/month):

• Designing efficient database schemas for new functionality

• Planning and executing data model improvements

• Evaluating and implementing new Oracle features

• Capacity planning based on business growth projections

• Data archiving and retention strategy

Developer Enablement (20 hours/month):

• Reviewing SQL queries in code reviews

• Teaching developers database best practices.

• Creating reusable query patterns and templates

• Building tools that help developers write better SQL

• Pair programming on complex database interactions

Platform Evolution (9 hours/month):

• Evaluating new database technologies and features

• Planning database modernization initiatives

• Contributing to platform architecture decisions

• Researching industry best practices

• Strategic projects (machine learning, analytics, etc.)

Jake read through the list, his expression slowly changing from defensive to thoughtful.

“This is what you think I should be doing instead of managing backups,” he said.

“This is what you’re uniquely qualified to do,” Maya said. “Nobody else on the team can do this work at the level you can. Priya’s a good developer, but she doesn’t understand Oracle internals as well as you do. Tom knows infrastructure, but he can’t tune SQL. Sarah’s brilliant at automation, but she doesn’t have your depth of database expertise.”

“But they can all click a button to run a backup,” Maya continued. “And frankly, Oracle’s automated backup system can do it better than any of us because it’s designed specifically for that purpose. So why are we paying you $85 an hour to babysit backups when you could be preventing the kind of performance issues that slow down the entire university?”

Jake was quiet, processing.

“Let me ask you something,” Maya said. “In the last month, how many times have you wanted to work on a database performance issue but couldn’t because you were dealing with operational overhead?”

Jake exhaled. “Last week. We had a batch job running slowly—probably a missing index or a bad query plan. But I was in the middle of patch testing, and by the time I got to it, the job had finished. It’ll probably be slow again next month, but I haven’t had time to investigate properly.”

“That’s exactly what I’m talking about,” Maya said. “You have expertise that could have prevented that slow batch job. But you were spending your time on patch testing that could be automated. That’s a misallocation of your talent.”

“Okay,” Jake said slowly. “I see the argument. But I still have concerns. What about control? Right now, if I need to change an Oracle parameter, I can. With Exadata as a service, do I lose that?”

“Some parameters you can still change,” Maya said. “Database-level configuration, optimizer settings, memory allocation within your allocated resources—all of that’s still under your control. What you can’t change is infrastructure-level stuff like storage configuration or networking. But again, when was the last time you needed to change those?”

“Fair point,” Jake admitted.

“And here’s the thing,” Maya continued. “The infrastructure parameters Oracle sets for Exadata are based on thousands of customer deployments and years of engineering. They’re probably better than what we configured six years ago when we set up our RAC cluster.”

Tom had wandered over during the conversation and was listening from the doorway.

“Can I jump in here?” Tom asked.

“Please,” Maya said.

“Jake, I had the same reaction you’re having when Maya talked about infrastructure as code,” Tom said. “I felt like we were throwing away fifteen years of experience. But what I learned is that automation doesn’t replace expertise—it multiplies it. My knowledge of how to configure an application server is now in Chef cookbooks that anyone can run. That doesn’t make me less valuable. It makes my knowledge more valuable because it’s reusable.”

“And you’re not worried about job security?” Jake asked.

“I was,” Tom admitted. “But then I realized—organizations don’t pay us to click buttons. They pay us to solve problems and make good decisions. If all we’re doing is clicking buttons, then yeah, we should worry. But if we’re solving problems? That’s always going to be valuable.”

Sarah had joined them now, too, along with Marcus and Priya.

“What’s going on?” Sarah asked.

“Jake’s concerned about moving to managed Exadata,” Maya explained. “He’s worried about losing control and becoming irrelevant.”

“Oh, I can speak to that,” Sarah said. “Before I came here, I worked at a company that moved from self-managed databases to Amazon RDS. The DBAs freaked out initially. Same concerns—losing control, becoming unnecessary.”

“What happened?” Jake asked.

“Their jobs got way more interesting,” Sarah said. “They stopped spending time on backups and patches and started building internal database tooling. They created query analysis frameworks that automatically identified slow queries and suggested optimizations. They built a data pipeline automation. They became strategic partners to the development teams instead of people you ticket when the database is full.”

“And nobody got laid off?” Jake asked.

“Nobody,” Sarah confirmed. “They just redirected their energy to higher-value work. One guy became the data architecture lead. Another one built an entire internal analytics platform. The third one began providing database performance consulting to all development teams. They went from firefighters to architects.”

Maya pulled up one more document on the screen. “Jake, I want to show you something else. This is what happens to organizations that resist managed services.”

The Traditional DBA Career Path: Self-Managed Databases

Year 1-5: Learning database administration, operational basics
Year 6-15: Deep expertise in backup/recovery, performance tuning, HA configuration
Year 16-25: Senior DBA, mentoring others, and making architecture decisions
Year 26+: ???

Common challenges:

• Skills become increasingly niche as the industry moves to managed services.

• Operational toil increases with system complexity.

• Difficult to stay current with modern data platforms

• Career mobility decreases (fewer companies want self-managed DBAs)

• Burnout from on-call and operational burden

The Modern DBA Career Path: Managed Services + Strategic Work

Year 1-5: Learning database fundamentals
Year 6-15: Performance optimization, query tuning, data modeling
Year 16-25: Data architecture, platform strategy, cross-platform expertise
Year 26+: Database architect, data platform lead, strategic advisor

Advantages:

• Skills remain relevant (performance optimization always matters)

• Learning time freed up for new technologies (cloud platforms, analytics, ML)

• Career mobility increases (strategic skills transfer across companies)

• Better work-life balance (less on-call operational burden)

• Higher compensation (strategic roles pay more than operational roles)

Jake studied both paths. “You’re saying that by resisting managed services, I’m actually limiting my career growth.”

“I’m saying the industry is moving to managed services whether we like it or not,” Maya said gently. “AWS, GCP, Azure—they’re all betting big on managed databases. Oracle is investing heavily in Exadata as a service. In five years, most enterprise databases will be managed services. DBAs who only know how to manage infrastructure will struggle. DBAs who can optimize performance and design data architectures will thrive.”

“And you think I can make that transition?” Jake asked.

“I know you can,” Maya said. “Because you’re already doing it. Last week, you spotted a performance issue in our monitoring data before it became critical. That’s the kind of proactive work that managed services enable. You weren’t busy patching, so you had time to actually analyze performance trends.”

Priya spoke up. “Jake, can I ask you something? What part of your DBA work do you actually enjoy?”

Jake thought about it. “The puzzle-solving. When someone says, ‘this query is slow,’ and I get to figure out why. Looking at execution plans, finding the missing index or the bad join, fixing it, and seeing the performance improve. That’s satisfying.”

“That’s the work Maya’s saying you’d get to do more of,” Priya said.

“Yeah,” Jake said quietly. “I guess it is.”

Marcus added, “And honestly, Jake, we need you to do more of that. I’ve got integration queries that I know could be faster, but I don’t know enough about Oracle to optimize them. If you had more time to work with me on that, our integrations would be way more efficient.”

“Same with me,” Priya said. “I write SQL in my customizations, but I know I’m probably doing dumb things. I could use a DBA who has time to review my queries and teach me better patterns.”

Jake looked at his team—people who wanted to learn from him, who valued his expertise, who needed him to do more strategic work than he currently had time for.

“Okay,” Jake said finally. “I’m still nervous about this. But I see the argument. Show me what this Exadata migration actually looks like.”

Maya pulled up the migration plan she’d drafted. “We’re not ripping and replacing. We’re doing a methodical migration with extensive testing.”

Exadata Migration Plan: 6 Weeks

Week 5 (This Week): Planning and Preparation

• Jake evaluates Exadata capabilities vs. the current RAC setup.

• Identify any features we use that work differently on Exadata.

• Build a test plan for functionality validation.

• Set up Exadata test environment on GCP.

Week 6: Development Environment Migration

• Migrate the dev database to Exadata.

• Run full test suite

• Validate performance, functionality, and integrations.

• Team learns Exadata management interfaces.

Week 7: QA Environment Migration

• Migrate the QA database using the refined process.

• Extended testing with real workloads

• Performance benchmarking

• Backup/recovery testing

Week 8: Performance Validation

• Compare performance metrics: Exadata vs. RAC.

• SQL query performance analysis

• Batch job timing validation

• User acceptance testing

Week 9-10: Production Migration Planning

• Final migration runbook

• Rollback procedures

• Communication plan

• Schedule maintenance window

Production Migration: Week 11

• Execute during scheduled maintenance.

• Monitor closely post-migration

• Jake’s full attention is on performance validation.

“Six weeks from planning to production,” Maya said. “And you’re involved in every step. You’re the one validating that Exadata meets our performance requirements. You’re the one deciding if we’re ready to migrate production. This isn’t me taking control away from you—it’s you using your expertise to evaluate a better platform.”

Jake nodded slowly. “Okay. I can work with this. But I have conditions.”

“Name them,” Maya said.

“One: if we migrate to Exadata and performance is worse than our current RAC setup, we roll back. I’m not going to sacrifice database performance to save money.”

“Agreed,” Maya said. “Performance is non-negotiable.”

“Two: I’m the one who decides when we’re ready to migrate production. If I say we need more testing, we take more time.”

“Absolutely,” Maya said. “You’re the database expert. I trust your judgment.”

“Three: I want time allocated for learning. If I’m going to become this strategic DBA you’re describing, I need to actually learn new skills. Performance tuning, data architecture, and modern analytics platforms. I can’t just figure it out on my own while doing my regular job.”

“I can support that,” Maya said. “How about four hours per week for focused learning? Online courses, conferences, certifications—whatever you need.”

“Four hours per week is good,” Jake said. “And one more thing: I want regular check-ins with you about my career development. If we’re redefining what a DBA does, I want to make sure I’m actually growing into that role and not just spinning my wheels.”

“Monthly one-on-ones focused on career development,” Maya offered. “On top of our regular status meetings. We’ll talk about what you’re learning, what projects you want to work on, and where you want to grow.”

“Okay,” Jake said, extending his hand. “I’m in. Let’s evaluate Exadata.”

Maya shook his hand. “Thank you for being open to this. I know it’s uncomfortable.”

“It’s terrifying,” Jake corrected with a slight smile. “But Tom’s right—I don’t want to be clicking buttons for the next ten years. If managed services free me up to do more interesting work, I should at least give it a fair evaluation.”

As the impromptu meeting dispersed, Sarah lingered behind with Maya.

“That was well handled,” Sarah said quietly. “You could have pulled rank and just mandated the migration. But you made the case and let him come to the decision himself.”

“People don’t resist change,” Maya said. “They resist being changed. If I’d just mandated Exadata, Jake would have complied but resented it. By walking him through the reasoning and giving him control over the migration, he’s bought in. Now he’ll make this succeed because he chose it.”

“Very Machiavellian,” Sarah said, grinning.

“Very practical,” Maya corrected. “We have eight weeks left to prove PeopleSoft modernization works. I need my team engaged and motivated, not compliant and resentful. Jake’s expertise is critical to this working. I need him all-in.”

“Do you think Exadata will actually be better than our current setup?” Sarah asked.

“Honestly? I think it’ll be roughly equivalent performance-wise with significantly lower operational burden,” Maya said. “But the real win isn’t performance—it’s freeing Jake to do higher-value work. If we can show Harrison that we’re not just cutting infrastructure costs, but also making our team more strategic and valuable, that’s a compelling story.”

“Strategic team modernization,” Sarah said. “Not just technology modernization.”

“Exactly,” Maya said. “The platform doesn’t matter if the people operating it aren’t growing.”

Wednesday Afternoon: The Exadata Evaluation

By Wednesday afternoon, Jake had spent two days deep in Oracle Exadata documentation, architecture diagrams, and performance whitepapers. The team gathered for his evaluation presentation.

“Alright,” Jake said, pulling up his slides. “Maya asked me to evaluate whether Oracle Exadata Database Service on Google Cloud is a viable replacement for our current RAC environment. Here’s what I found.”

He clicked to his first slide: a comparison chart.

Oracle RAC (Current) vs. Exadata (Proposed)

Architecture:

• RAC: Two database nodes, shared SAN storage, application-level high availability

• Exadata: Integrated system with compute nodes and intelligent storage servers

Performance Features:

• RAC: Standard Oracle performance (dependent on our tuning)

• Exadata: Smart Scan, Hybrid Columnar Compression, Storage Indexes, Flash Cache

High Availability:

• RAC: Node failover (we manage), manual storage failover

• Exadata: Automatic failover, storage redundancy built in, automated recovery

Backup/Recovery:

• RAC: RMAN scripts we maintain, recovery time depends on backup size

• Exadata: Automated snapshots, incremental forever backups, fast recovery

Patching:

• RAC: Manual patch application, extensive testing, quarterly 40-hour effort

• Exadata: Rolling patches with zero downtime, Oracle-tested combinations

“First thing I looked at was whether Exadata could actually run PeopleSoft,” Jake said. “Answer: yes. Oracle specifically supports PeopleSoft on Exadata. In fact, several large universities are already running it—Ohio State, University of Michigan, Penn State. So we’re not pioneers. We’re followers, which is good for risk management.”

He clicked to the next slide.

Performance Analysis

“Second question: will it be faster, slower, or the same as our current setup? This is what I spent most of my time on.”

Jake pulled up a detailed analysis. “Exadata has several performance features we don’t have with standard RAC. Smart Scan pushes query processing down to the storage layer, dramatically speeding up full-table scans. Hybrid Columnar Compression can reduce storage requirements by 10x for historical data. Flash Cache speeds up frequently accessed data.”

“But here’s the thing,” Jake continued. “Those features mainly help with analytics workloads and data warehouse queries. PeopleSoft is primarily an OLTP workload—lots of small transactions, index lookups, not many full table scans. So we won’t see massive performance gains from Smart Scan.”

“So it won’t be faster?” Tom asked.

“I didn’t say that,” Jake clarified. “The flash cache and faster storage will help our random read performance, which PeopleSoft does a lot of. And the automated performance tuning that Exadata does in the background is better than what I do manually. Overall, I’d expect 10-20% better performance for typical PeopleSoft operations, with potentially much better performance for reporting and analytics.”

“What about batch jobs?” Priya asked.

“That’s where it gets interesting,” Jake said. “Our batch jobs do a lot of full table processing. Smart Scan could significantly speed those up—potentially 30-50% faster. But I won’t know for sure until we test with real workloads.”

He clicked to the next slide: Operational Considerations.

“Third question: what do we give up by moving to a managed service?”

What We Lose:

• Direct access to storage layer configuration

• Ability to customize RAC parameters that we never customize

• Some diagnostic capabilities (replaced by Exadata-specific tools)

• The satisfaction of manually managing infrastructure (not actually a loss)

What We Gain:

• Automated patching with zero downtime

• Better performance out of the box

• Oracle’s 24/7 infrastructure support

• Automated scaling (add capacity in hours, not months)

• Advanced performance features (Smart Scan, compression, flash cache)

• Simplified disaster recovery (automated snapshots, fast recovery)

“Honestly?” Jake said. “Most of what we ‘lose’ is stuff I rarely touch. We set up our RAC cluster six years ago and haven’t changed the fundamental configuration since. I’ve tweaked database parameters, sure, but I can still do that on Exadata. The infrastructure-level stuff we lose access to? I won’t miss it.”

“What about the diagnostic tools?” Marcus asked. “You use those for troubleshooting, right?”

“I use Oracle’s diagnostic tools—AWR reports, SQL tuning advisor, execution plans,” Jake said. “All of those still work on Exadata. What I lose is access to low-level storage diagnostics. But Exadata has its own diagnostic tools that are actually better for that platform. It’s not a loss—it’s a different toolset.”

Jake pulled up his next slide: Risk Assessment.

Migration Risks:

High Risk:

• None identified

Medium Risk:

• Performance regression for specific queries (mitigation: extensive testing)

• Team learning curve on Exadata management (mitigation: training and Oracle support)

• Migration execution issues (mitigation: detailed runbook, tested rollback)

Low Risk:

• Compatibility issues (PeopleSoft is certified on Exadata)

• Functional gaps (Exadata is a superset of RAC capabilities)

“I spent a lot of time looking for showstopper risks,” Jake said. “Things that would make this migration a bad idea. I didn’t find any. The biggest risk is that we screw up the migration itself, not that Exadata can’t handle our workload.”

Sarah raised her hand. “What about vendor lock-in? Once we’re on Exadata, are we stuck with Oracle forever?”

“We’re already stuck with Oracle,” Jake said bluntly. PeopleSoft runs on Oracle Database. Whether it’s RAC in our data center or Exadata on GCP, we’re committed to Oracle. The Exadata service doesn’t increase our lock-in—it just changes who operates the infrastructure.”

“Fair point,” Sarah said.

Jake pulled up his final slide: Recommendation.

Recommendation: Proceed with Exadata Migration

Rationale:

• Meets all functional requirements

• Expected 10-20% performance improvement for OLTP, 30-50% for batch

• Reduces operational burden by ~90%

• Lowers total cost by $110K annually

• Enables strategic DBA work vs. operational toil

• Low migration risk with a proven rollback plan

Conditions:

• Complete testing in dev and QA before production migration

• Performance validation with real workloads

• Team training on Exadata management

• My approval is required before production migration.

“I’m recommending we do this,” Jake said. “Not because Maya told me to, but because it’s legitimately a better platform for less money with less operational overhead. The only way I’d recommend against it is if we found performance issues in testing. But I don’t expect to find them.”

The room was quiet.

“Questions?” Jake asked.

Tom spoke up. “Jake, are you actually comfortable with this? You were pretty opposed on Monday.”

“I was,” Jake admitted. “Because I was thinking about what I’d lose. But after two days of really looking at Exadata—reading the architecture docs, reviewing performance benchmarks, and thinking through the operational model—I’m convinced this is the right move. Not just for cost savings. For operational excellence.”

“What changed your mind?” Priya asked.

“Two things,” Jake said. “First, I realized I was defending my ability to do work I don’t actually want to do. Managing backups isn’t fulfilling. Patching databases isn’t fun. I was defending that work because I thought it made me valuable. But it doesn’t. What makes me valuable is my ability to optimize database performance and to design effective data architectures. Exadata frees me up to do more of that.”

“And second?” Maya prompted.

“Second, I realized that resisting managed services is like… you know how some sysadmins refused to learn virtualization ten years ago because they thought it was ‘not real infrastructure’? And then virtualization became standard, and those sysadmins became obsolete? I don’t want to be that person. The industry is moving to managed services. I can either complain about it and become irrelevant, or I can adapt and stay valuable.”

“That’s a pretty mature perspective,” Marcus said.

“I’m twenty-six years into my career,” Jake said. “I’d like to have another twenty years. That means evolving with the industry, not fighting it.”

Maya stood up. “Alright. Jake recommends proceeding with the Exadata migration. I agree. Unless anyone has serious objections?”

Silence.

“Good,” Maya said. “Here’s the plan for the rest of this week. Jake, you’re setting up the Exadata test environment on GCP. Sarah, you’re helping him with the GCP integration. Tom, start documenting our application server connection strings so we can update them during migration. Marcus, review our integrations that hit the database directly—we need to make sure they’ll work on Exadata. Priya, work with Jake on the testing plan. Lisa, start building the migration runbook.”

“What about you?” Jake asked.

“I’m updating our cost model for Harrison’s weekly report,” Maya said. “And drafting the business case for Exadata that we’ll use in the final Week 12 presentation. This is a big deal—$110,000 in annual savings is significant. I want to make sure we communicate the value clearly.”

As the team dispersed to start their work, Jake pulled Maya aside.

“Thank you,” he said quietly.

“For what?” Maya asked.

“For not just ramming this through,” Jake said. “You could have said, ‘We’re migrating to Exadata, deal with it.’ Instead, you made the case, showed me the data, and let me come to my own conclusion. That matters.”

“You’re the database expert,” Maya said simply. “If you thought Exadata was a bad idea, I would have listened. I’m not trying to push technology for technology’s sake. I’m trying to build a better operation. And that only works if the people doing the work believe in it.”

“I believe in it now,” Jake said. “And I’m actually excited about this. For the first time in years, I’m thinking about database work as something more than just keeping the lights on.”

“That’s what I was hoping for,” Maya said. “Now go set up that test environment. I want to see Exadata running by the end of the week.”

Friday Afternoon: First Test

By Friday afternoon, Jake had the Exadata test environment running on Google Cloud. The team gathered to watch the first database restore from their production backup to the new platform.

“This is it,” Jake said, initiating the restore process. “Production database backup from last night, restoring to Exadata. On our old system, this would take about six hours. On Exadata with their snapshot technology…”

They watched the progress indicator.

Forty-two minutes later, the restore was completed.

“Forty-two minutes,” Jake said, staring at the screen. “For a 1.2 terabyte database. That’s… that’s eight times faster than our current restore process.”

“That’s your disaster recovery time,” Maya said. “Forty-two minutes from disaster to running database.”

“Run a query,” Tom suggested. “Let’s see if it actually works.”

Jake opened SQL Developer and connected to the Exadata instance. He ran a complex query that he knew typically took about eight seconds on their production system.

It returned in 4.3 seconds.

“That’s almost twice as fast,” Jake said, running it again to make sure. 4.2 seconds. “Same query, half the time.”

“Is that the Smart Scan feature?” Priya asked.

“Probably a combination of things,” Jake said, pulling up the execution plan. “Flash cache, faster storage, and yeah, some Smart Scan optimization. This query does a full table scan on a large table, which is exactly what Smart Scan helps with.”

He ran another query—a typical PeopleSoft transaction query with lots of index lookups.

Production time: 0.3 seconds
Exadata time: 0.2 seconds

“About 30% faster on OLTP queries too,” Jake noted. “The flash cache is helping with hot data.”

Sarah was watching the Exadata performance monitoring console. “Look at the storage I/O. Those storage servers are doing offload processing—they’re filtering data before sending it to the database layer. That’s really cool architecture.”

“It is,” Jake admitted. “Oracle actually did something smart here. Instead of just throwing faster hardware at the problem, they redesigned the architecture to push processing closer to the data.”

Marcus had a question. “What about our batch jobs? Can we test one?”

“Let’s try the nightly student enrollment batch,” Jake said. “In production, that typically runs for two hours. Let me kick it off here with yesterday’s data.”

He started the batch job, and they watched the progress.

One hour and fourteen minutes later, it was completed.

“That’s 38% faster than production,” Jake said, checking the logs. “Same data volume, same processing logic, just running on better infrastructure.”

“So everything’s faster,” Tom summarized. “Restore time, query time, batch time. All better than what we have.”

“So far,” Jake cautioned. “This is one day of testing with a handful of queries. We need weeks of testing with real workloads before I’m comfortable migrating production.”

“But you’re not seeing any red flags?” Maya asked.

“None,” Jake said. “Which honestly surprises me. I expected to find something that didn’t work well. Some queries were slower, and some features were incompatible. But so far? It’s just better.”

“Maybe Oracle actually knows what they’re doing with this product,” Sarah suggested.

“Don’t get crazy,” Jake said with a smile. “But yeah, they did good work here. This is legitimately impressive infrastructure.”

Maya pulled up the week’s summary on the screen.

Week 5: Database Modernization

Decision Made:

• Migrate from self-managed Oracle RAC to Exadata Database Service on GCP.

• Jake’s full evaluation and recommendation

• Team consensus and buy-in

Test Environment:

• Exadata Quarter Rack deployed on GCP

• Production database restored (42 minutes vs. 6 hours)

• Initial performance testing (10-40% faster across workloads)

• No compatibility issues identified

Business Value:

• Annual cost savings: $110,480

• Operational time savings: 74 hours/month (Jake’s time)

• Performance improvement: 10-40% depending on workload type

• Risk reduction: Automated backups, faster DR, Oracle infrastructure support

Next Steps:

• Week 6: Dev database migration and testing

• Week 7: QA database migration and extended testing

• Week 8-10: Performance validation and production migration planning

“This is what I’m reporting to Harrison on Monday,” Maya said. “One week from ‘we need to evaluate this’ to ‘we have a working test environment and initial positive results.’ That’s execution.”

“Can I add something to the report?” Jake asked.

“Of course.”

“Include that the DBA team fully supports this migration,” Jake said. “I want Harrison to know this isn’t being forced on us. We evaluated it, we tested it, and we believe it’s the right move.”

“That’s valuable,” Maya said, making a note. “I’ll quote you directly in the status report.”

As the team started to pack up for the weekend, Tom pulled Jake aside.

“Hey, I wanted to say something. Your presentation on Wednesday was really good. You could have just rubber-stamped Maya’s plan, but you did real analysis. That matters.”

“Thanks,” Jake said. “I figured if I’m going to recommend a major migration, I should actually understand what we’re migrating to.”

“I think you surprised Maya a little,” Tom said. “In a good way. She was probably expecting more resistance.”

“I surprised myself,” Jake admitted. “Monday morning, I was ready to dig in and fight this. But the more I looked at it objectively, the more I realized the fight was about ego, not engineering. I didn’t want to admit that there might be a better way to run databases than how I’ve been doing it for twenty years.”

“That’s hard to admit,” Tom said.

“Yeah,” Jake agreed. “But you know what’s harder? Spending the next twenty years doing work I don’t enjoy because I was too proud to change. I’d rather spend my time optimizing SQL than babysitting backups. If Exadata lets me do that, I’m all for it.”

They walked out together, leaving the conference room with its whiteboard full of Exadata architecture diagrams and performance benchmarks.

Maya stayed behind for a moment to update her timeline.

Five weeks down. Seven weeks to go.

Week 1: Honest assessment and baseline
Week 2-3: Infrastructure as Code
Week 4: Observability
Week 5: Database modernization decision

They were more than on track. They were ahead.

And more importantly, her team was evolving. Jake had gone from defensive to analytical to advocating for change. That transformation—from “we lose control” to “this is legitimately better”—was exactly what Maya needed to see.

Because the twelve-week challenge wasn’t just about proving PeopleSoft could be modernized.

It was about proving that traditional IT teams could modernize themselves.

One mindset shift at a time.

Technical Takeaway: The Managed Database Services Decision Framework

Jake’s journey from resistance to advocacy illustrates the critical decision framework for PeopleSoft DBAs evaluating managed database services:

The Core Question

Not: “Can we manage databases ourselves?”
But: “Should we manage database infrastructure ourselves?”

These are fundamentally different questions with different answers.

The Traditional DBA Value Proposition

For decades, DBAs justified their value through operational tasks:

• Managing backups and recovery

• Applying patches and updates

• Configuring high availability

• Monitoring disk space and storage

• Troubleshooting infrastructure issues

• Performing routine maintenance

This work is necessary. It’s also increasingly commoditized.

The Managed Services Shift

Managed database services (Oracle Exadata, AWS RDS, Azure SQL Database, Google Cloud SQL), and automated operational tasks:

• Backups happen automatically with point-in-time recovery.

• Patches apply with zero downtime on managed schedules.

• High availability is built in and automated.

• Storage scales automatically

• The provider handles infrastructure monitoring.

• Routine maintenance is automated.

This shift terrifies traditional DBAs because it appears to eliminate their value.

The Reality: Strategic vs. Operational Work

DBAs create value in two categories:

Operational Work (automatable):

• Backup management

• Patch application

• Storage management

• Infrastructure monitoring

• Routine maintenance

• Disaster recovery execution

Strategic Work (not automatable):

• SQL query optimization

• Execution plan analysis

• Index strategy and design

• Data modeling and architecture

• Performance troubleshooting

• Capacity planning based on business trends

• Developer education and support

• Database platform evolution

Managed services eliminate operational work. They amplify strategic work.

The Time Allocation Analysis

Most PeopleSoft DBAs spend:

• 60-80% of time on operational tasks

• 20-40% of time on strategic work

With managed services:

• 5-10% of time on operational oversight

• 90-95% of time on strategic work

Same total hours. Radically different value creation.

The Cost Model

Self-Managed Database Total Cost:

• Infrastructure (servers, storage, networking)

• Software licenses and support

• Data center (space, power, cooling)

• DBA operational time

• Infrastructure team support

• Opportunity cost of DBA time on toil

Managed Database Service Total Cost:

• Service subscription (includes infrastructure, software, support)

• DBA strategic time

• Training and skill development

For most organizations, Managed services cost 30-50% less than self-managed while delivering better performance and reliability.

The Performance Reality

Managed database services often perform better than self-managed:

Why?

• Specialized hardware (Exadata, custom AWS instances)

• Optimized configurations based on millions of workloads

• Advanced features (Smart Scan, storage offload, flash cache)

• Regular performance tuning by provider engineers

• Latest patches and optimizations are applied automatically.

When self-managed might be better:

• Highly specialized configurations requiring deep customization

• Regulatory requirements preventing cloud deployment

• Existing infrastructure with capacity to spare

• Extremely cost-sensitive scenarios (rare)

For typical PeopleSoft workloads, Managed services match or exceed self-managed performance.

The Control Argument

What you actually lose:

• Infrastructure-level configuration (storage, networking)

• Ability to apply custom patches outside provider schedules

• Direct hardware access for diagnostics

What you retain:

• Database-level configuration and tuning

• SQL optimization and query control

• Schema design and modifications

• User and security management

• Application-level performance tuning

The key insight: Most of what DBAs think they need control over, they rarely actually change.

The Career Development Perspective

Traditional DBA skills are decreasing in value:

• Manual backup/recovery procedures

• Infrastructure hardware troubleshooting

• Physical storage management

• On-premise high availability configuration

Modern DBA skills are increasing in value:

• SQL performance optimization (always relevant)

• Cloud database architecture

• Multi-database platform expertise

• Data modeling and design patterns

• Performance analysis and tuning

• Developer enablement and education

• Database automation and tooling

Managed services force DBAs to develop higher-value skills.

The Decision Framework

Evaluate managed services when:

• Operational overhead exceeds 50% of DBA time.

• Infrastructure is aging and needs replacement.

• Disaster recovery is difficult or untested.

• Team lacks deep infrastructure expertise.

• The organization is moving to the cloud.

• Want to reduce operational risk.

Proceed with managed services if:

• Performance testing shows equivalent or better results.

• Cost analysis shows savings (usually 30-50%)

• Team is willing to adapt skillsets.

• Provider supports your database platform and version.

• Regulatory requirements are met.

Stay with self-managed if:

• Truly unique configuration requirements exist

• In-house expertise dramatically exceeds provider capability (rare)

• Regulatory constraints prevent cloud deployment

• Cost analysis definitively favors self-managed (very rare)

The Implementation Approach

Phase 1: Evaluation (1-2 weeks)

• Deep dive on provider capabilities

• Compatibility verification

• Feature gap analysis

• Cost modeling

Phase 2: Proof of Concept (2-3 weeks)

• Deploy test environment

• Restore production data

• Performance benchmarking

• Functionality validation

Phase 3: Migration Planning (2-3 weeks)

• Detailed migration runbook

• Rollback procedures

• Team training

• Risk mitigation planning

Phase 4: Staged Migration (4-6 weeks)

• Migrate the dev environment

• Extended testing in dev

• Migrate QA environment

• Performance validation in QA

• Production migration with careful monitoring

Phase 5: Optimization (ongoing)

• Leverage advanced provider features

• Tune for specific workloads

• Continuous performance improvement

The Team Transformation

Successful managed services adoption requires:

Leadership:

• Clear communication about role evolution

• Career development support

• Training budget allocation

• Patience during the learning curve

DBAs:

• Willingness to learn new tools and approaches

• Focus on strategic skill development

• Embrace of automation (not resistance)

• Trust in provider capabilities

Organization:

• Recognition that value shifts from operational to strategic

• Investment in DBA skill development

• Support for new ways of working

The Bottom Line

The decision between managed and self-managed databases isn’t about technology capabilities.

It’s about organizational priorities:

Choose self-managed if: You want control over infrastructure and are willing to pay (in time and money) for that control.

Choose managed services if: You want to redirect DBA expertise toward strategic work that directly impacts business outcomes.

For most PeopleSoft organizations, managed services are the better choice.

Not because DBAs are unnecessary.

But because DBAs are too valuable to spend their time on operational toil that can be automated.

Jake learned this lesson in Week 5.

The question is: will your DBAs learn it before or after the industry makes the decision for them?

Subscribe now

A strong roadmap reflects how the organization wants to operate in the future. It connects business priorities to technology capabilities in a measurable, adaptable way. Without this alignment, even well-funded initiatives struggle to deliver meaningful outcomes. ERP modernization should not be treated as a one-time project. It should be structured as a continuous evolution guided by clear decision points.

Step 1: Establish Strategic Objectives

Every effective roadmap begins with a clear articulation of strategic objectives. These objectives should reflect both business priorities and operational realities. CIOs need to define what modernization is meant to achieve, whether that is increased agility, cost optimization, improved data visibility, or enhanced user experience. Without this clarity, it becomes difficult to evaluate tradeoffs or measure success.

Strategic objectives also help align stakeholders. Business leaders, finance teams, and IT organizations often have different expectations for ERP outcomes. A shared set of objectives ensures that decisions are evaluated against consistent criteria. This alignment reduces friction later in the roadmap. It also strengthens executive sponsorship and accountability.

Step 2: Assess the Current State Honestly

An honest assessment of the current ERP environment is essential. This assessment should go beyond infrastructure and include processes, integrations, data quality, and team capabilities. Many organizations underestimate the strength of what they already have. Others overlook areas where technical debt or inefficiency has accumulated.

A comprehensive assessment should include:

• Core system stability and performance metrics

• Integration landscape and data flow complexity

• Customizations and their business value

This level of visibility allows CIOs to separate perception from reality. It also highlights areas where modernization can deliver immediate value. Without this baseline, roadmap decisions are based on incomplete information.

Step 3: Define the Target Operating Model

The target operating model describes how the ERP environment will function in the future. It includes decisions about cloud strategy, integration patterns, governance, and team structure. This model is not about specific tools. It is about defining how work gets done and how systems interact.

A well-defined operating model provides a blueprint for modernization. It clarifies roles and responsibilities across IT and business teams. It also establishes standards for deployment, monitoring, and change management. These standards reduce variability and improve predictability.

CIOs should ensure that the operating model supports both stability and innovation. The goal is not to optimize for one at the expense of the other. A balanced model enables continuous progress without introducing unnecessary risk.

Step 4: Prioritize Modernization Initiatives

Once objectives and operating models are defined, the next step is prioritization. Not all modernization efforts deliver equal value. CIOs must identify initiatives that provide the highest impact with manageable risk. This requires evaluating both technical complexity and business benefit.

Effective prioritization often focuses on areas such as:

• Infrastructure modernization to improve scalability and cost efficiency

• Integration improvements to accelerate data flow and reduce friction

• Automation initiatives that reduce manual effort and increase reliability

These initiatives create momentum without requiring large-scale disruption. They also build confidence across stakeholders. Over time, this approach allows organizations to modernize incrementally while maintaining operational continuity.

Step 5: Establish Governance and Metrics

Governance is the mechanism that keeps the roadmap on track. It ensures that decisions align with strategic objectives and that progress is measurable. Without governance, even well-designed roadmaps can drift. CIOs need to define how decisions are made, how priorities are adjusted, and how success is evaluated.

Metrics play a critical role in this process. They provide visibility into whether modernization efforts are delivering the intended outcomes. Metrics should go beyond uptime and include delivery speed, cost efficiency, and business impact. Clear measurement reinforces accountability and supports continuous improvement.

Strong governance also creates transparency. Stakeholders can see how decisions are made and how progress is tracked. This visibility builds trust and reduces resistance to change.

Step 6: Execute in Phases, Not Events

ERP modernization should be implemented in phases rather than as a single transformation event. Phased execution reduces risk by limiting the scope of change at any given time. It also allows organizations to learn and adapt as they move forward. Each phase builds on the previous one, creating a cumulative effect.

Phased approaches also improve resilience. If a particular initiative encounters challenges, it does not derail the entire roadmap. CIOs can adjust priorities and timelines without compromising overall strategy. This flexibility is essential in complex environments.

Over time, phased execution creates a pattern of continuous improvement. The organization becomes more comfortable with change and better able to manage it. This capability is one of the most valuable outcomes of a well-designed roadmap.

Turning Strategy into Sustained Progress

An effective ERP modernization roadmap is not a static document. It is a living framework that evolves with the organization. CIOs who approach modernization as a continuous process are better positioned to adapt to change and capture new opportunities. They avoid the pitfalls of both stagnation and overreach.

The ultimate goal is not modernization for its own sake. It is the ability to deliver consistent, measurable value to the business. A well-structured roadmap provides the clarity and discipline needed to achieve that goal.

☕ This Week’s Focus

Edition 30 marks a major milestone—30 editions of The Modern ERP Digest.

What started as a way to consolidate PeopleSoft, ERP, and cloud insights has grown into a consistent signal for what’s actually happening in the market. And if there’s one theme that stands out this week, it’s this:

ERP is being redefined in real time.

Subscribe now

We’re seeing a collision of forces between AI agents, multicloud architectures, workforce shifts, and evolving expectations of what ERP systems should actually do. The conversation is no longer about systems of record. It’s about systems of action.

At the same time, the PeopleSoft ecosystem continues to evolve in practical, meaningful ways, especially in areas like containerization and AI integration.

Let’s get into it.

☁️ Oracle, Cloud & AI Momentum

🔗 Oracle Multicloud: What’s New
https://blogs.oracle.com/cloud-infrastructure/oracle-multicloud-whats-new-blog
Oracle continues expanding its multicloud strategy, reinforcing a reality many enterprises already accept: no single cloud will meet every need. The focus is shifting toward interoperability and platform flexibility.

🔗 Oracle’s AI Pivot and “Agentic Applications” Strategy
https://markets.financialcontent.com/stocks/article/finterra-2026-4-9-the-ai-landlord-inside-oracles-pivot-to-fusion-agentic-applications
Oracle is leaning heavily into agent-based applications—systems that can act, decide, and automate end-to-end processes. This represents a shift from traditional ERP workflows to more autonomous, AI-driven operations.

👥 Workforce & Organizational Signals

🔗 Oracle Layoff Stories and Employee Perspective (Business Insider)
https://www.businessinsider.com/oracle-employee-laid-off-after-almost-10-years-learned-lessons-2026-4
Personal stories from layoffs highlight the human side of transformation. Behind every strategic shift are real teams navigating uncertainty and change.

🔗 Severance Benchmarking Under the Microscope (HR Executive)
https://hrexecutive.com/oracles-layoff-package-puts-severance-benchmarking-under-the-microscope/
Oracle’s severance approach is drawing attention as organizations rethink how they manage workforce transitions during large-scale transformation efforts.

📊 ERP Strategy & Industry Direction

🔗 Why Your ERP Is Now a Liability—Not an Asset (Manufacturing.net)
https://www.manufacturing.net/artificial-intelligence/article/22964443/why-your-erp-is-now-a-liability-not-an-asset
A provocative take: ERP systems that fail to evolve can become constraints rather than enablers. The key issue isn’t ERP itself, it’s whether it can adapt to modern demands.

🔗 The Next Evolution of ERP: Intelligence Built Around People (Diginomica)
https://diginomica.com/next-evolution-erp-intelligence-built-around-people
ERP is shifting toward more human-centered, intelligence-driven design. AI isn’t just optimizing processes—it’s reshaping how users interact with enterprise systems.

👩‍💻 PeopleSoft Community & Practice

🔗 PeopleSoft Images on Containers (Oracle Blog)
https://blogs.oracle.com/peoplesoft/peoplesoft-images-on-containers
Oracle continues advancing containerization for PeopleSoft, enabling more flexible deployments and aligning with modern platform engineering practices. This is a key step toward scalable, cloud-native PeopleSoft environments.

🔗 PeopleSoft AI Agent – Copilot Studio (YouTube)

This demo showcases how AI agents can integrate with PeopleSoft workflows using tools like Copilot Studio. It’s a glimpse into how conversational and automated interfaces may become part of the PeopleSoft experience.

💬 Aaron’s Take

Thirty editions in, one thing has become very clear:

ERP isn’t standing still—and neither can we.

The narrative that ERP is “dead” keeps resurfacing, but that’s not what’s actually happening. ERP is evolving—sometimes quietly, sometimes aggressively—into something far more dynamic.

AI agents, multicloud strategies, and composable architectures are all pushing ERP beyond its traditional boundaries. But at the same time, platforms like PeopleSoft are adapting in practical ways, through containers, AI integrations, and lifecycle tools.

The real risk isn’t that ERP becomes obsolete.
The real risk is that organizations fail to evolve how they use it.

The teams that win in this next phase won’t chase every trend. They’ll focus on:

• Integrating intelligently
• Automating deliberately
• Modernizing incrementally
• Leading with architecture, not hype

That’s where real progress happens.

🌐 Join the Community

If you want to stay current on ERP strategy, PeopleSoft innovation, and cloud platform trends, subscribe at www.peoplesoftcloud.com.

Each week you’ll get:

✅ Curated ERP and PeopleSoft insights
✅ Context around AI and cloud developments
✅ Practical, real-world guidance

Thanks for being part of the first 30 editions.
On to the next 30.

Subscribe now

However, stability can create a false sense of security. Over time, systems that are not actively modernized drift away from the business’s needs. Integration becomes more difficult, reporting becomes slower, and innovation moves elsewhere. These shifts rarely trigger immediate alarms, but they accumulate into meaningful constraints. What appears safe in the moment can become limiting over time.

The Hidden Risks of Stagnation

The risks of not modernizing are rarely captured in traditional risk registers. They do not show up as outages or critical incidents. Instead, they emerge gradually through reduced agility, increased manual effort, and declining alignment with business priorities. These risks are harder to quantify, which makes them easier to ignore.

Several patterns tend to emerge in stagnant ERP environments:

• Increasing reliance on manual workarounds to bridge system gaps

• Slower delivery timelines for new capabilities and integrations

• Growing disconnect between IT capabilities and business expectations

These patterns create friction that compounds over time. Teams spend more effort maintaining workarounds than delivering new value. Business units begin seeking alternatives outside IT governance. The organization becomes less coordinated and more reactive.

Read more

☕ This Week’s Focus

Edition 29 highlights a growing tension in the ERP and cloud space: acceleration versus alignment.

Oracle is pushing aggressively into AI, with infrastructure investments, partnerships, and now large-scale agent-based automation. At the same time, workforce changes and market reactions remind us that transformation always comes with trade-offs.

Subscribe now

Across the ERP landscape, the conversation is shifting toward ecosystems and composability. Organizations are no longer asking “Which ERP should we choose?” but rather “How should our ERP fit into a broader architecture?”

Meanwhile, the PeopleSoft community continues to move forward with clarity by leveraging OCI, expanding Cloud Manager capabilities, and aligning with the 2026 roadmap.

⚙️ Oracle, AI & Market Signals

🔗 Oracle Layoff Plan Raises Questions (Yahoo Finance)
https://finance.yahoo.com/news/oracle-layoff-plan-raises-questions-011119909.html
Reports of layoffs are raising questions about how Oracle is balancing cost management with its aggressive investments in AI and the cloud. It’s a reminder that large-scale transformation often includes difficult operational decisions.

🔗 Oracle + NVIDIA at GTC 2026: Key Announcements (OCI Blog)
https://blogs.oracle.com/cloud-infrastructure/oracle-nvidia-gtc-2026-key-announcements
Oracle and NVIDIA announced deeper collaboration around AI infrastructure, including expanded GPU capabilities and performance optimizations. The focus remains clear: enable enterprise-scale AI workloads with high-performance compute.

🔗 Oracle Unleashes 1,000 AI Agents (CloudWars)
https://cloudwars.com/ai/oracle-unleashes-1000-ai-agents-to-automate-entire-industries/
Oracle is introducing a large portfolio of AI agents designed to automate complex business processes across industries. This marks a significant step toward agentic ERP, where systems don’t just process data; they act on it.

📊 ERP Strategy & Architecture

🔗 Why ERP Ecosystems Are a Strategic Architecture Decision (Forbes)
https://www.forbes.com/councils/forbestechcouncil/2026/03/20/why-erp-ecosystems-are-a-strategic-architecture-decision/
This piece makes a strong case that ERP is no longer a standalone system, it’s part of a broader ecosystem. Integration strategy, data flow, and platform alignment now matter as much as core functionality.

🔗 Composable ERP: Architectural Reality or Executive Imperative? (ERP Today)
https://erp.today/composable-erp-architectural-reality-or-executive-imperative/
Composable ERP continues gaining attention as organizations look to assemble capabilities rather than replace entire systems. The challenge is balancing flexibility with governance and long-term maintainability.

👩‍💻 PeopleSoft Community & Practice

🔗 Enabling AI for PeopleSoft with OCI (PeopleSoftCareer)
https://blog.peoplesoftcareer.com/enabling-ai-for-peoplesoft-with-oci/
A practical guide to integrating AI capabilities into PeopleSoft using Oracle Cloud Infrastructure. It outlines how AI services can enhance existing workflows without disrupting the core system.

🔗 Cloud Manager Image 21 (Oracle PeopleSoft Blog)
https://blogs.oracle.com/peoplesoft/cloud-manager-image-21
Oracle highlights updates to Cloud Manager Image 21, including improvements to provisioning, lifecycle management, and automation. Cloud Manager continues evolving into a key platform tool for PeopleSoft operations.

🔗 PeopleSoft 2026 Product Roadmap (PeopleSoftCareer)
https://blog.peoplesoftcareer.com/peoplesoft-2026-product-roadmap/
An overview of the 2026 roadmap, including continued investment in UX, AI capabilities, and platform enhancements. The roadmap reinforces Oracle’s long-term commitment to PeopleSoft.

💬 Aaron’s Take

Edition 29 reinforces a shift that’s been building for a while: ERP is no longer a destination; it’s a component of a larger system.

Oracle’s AI push, NVIDIA partnerships, and agent-based automation are all part of a broader strategy to move beyond traditional ERP boundaries. But those moves come with real operational considerations, including cost, workforce alignment, and execution risk.

At the same time, the ERP conversation itself is evolving. Ecosystems and composability are replacing monolithic thinking. The question isn’t whether ERP changes, it’s how well it integrates with everything around it.

PeopleSoft continues to fit into this new model in a very practical way. Instead of being replaced, it’s being extended and connected to AI services, managed through Cloud Manager, and aligned with a clear roadmap.

The organizations that succeed won’t be the ones chasing the biggest changes. They’ll be the ones who thoughtfully architect, deliberately integrate, and consistently evolve.

🌐 Join the Community

If you want to stay current on ERP strategy, PeopleSoft innovation, and cloud platform trends, subscribe at PeopleSoftCloud.com.

Each week you’ll receive:

✅ Curated ERP and PeopleSoft insights
✅ Context around AI and cloud developments
✅ Practical guidance for enterprise technology teams

See you next week for Edition 30.

☕ This Week’s Focus

Edition 28 highlights a theme that continues to define ERP strategy in 2026: evolution over disruption.

Subscribe now

Across the industry, the most successful organizations aren’t abandoning their ERP foundations. Instead, they’re layering AI, automation, and modern architecture patterns on top of stable platforms. Oracle’s financial performance and market momentum reinforce the scale of its cloud ambitions, while analysts and practitioners alike encourage enterprises to modernize intelligently rather than rush into costly replacements.

Meanwhile, the PeopleSoft ecosystem continues to deliver practical updates, from tax reporting changes to developer automation techniques, demonstrating that modernization often happens through incremental capabilities rather than sweeping change.

Let’s look at the signals shaping the landscape this week.

⚙️ Oracle, Cloud & Market Signals

🔗 Well-Architected Design for Resiliency with Oracle Database@AWS
https://aws.amazon.com/blogs/database/well-architected-design-for-resiliency-with-oracle-databaseaws/
AWS outlines architecture guidance for running Oracle Database workloads with resiliency and high availability. The takeaway is clear: hybrid and multicloud patterns are becoming normal for enterprise workloads, especially when reliability and geographic redundancy are priorities.

🔗 Oracle Stock Surges on AI and Cloud Momentum (Axios)
https://www.axios.com/2026/03/10/oracle-stock-ai-cloud-computing
Axios reports renewed investor confidence in Oracle as AI and cloud demand continue driving revenue expectations. Markets are increasingly viewing Oracle not just as a database company, but as a major infrastructure provider for enterprise AI workloads.

🔗 Oracle Announces Fiscal Year 2026 Third Quarter Financial Results
https://investor.oracle.com/investor-news/news-details/2026/Oracle-Announces-Fiscal-Year-2026-Third-Quarter-Financial-Results/default.aspx
Oracle’s quarterly results reinforce the same trend: cloud infrastructure and AI-related demand remain key growth drivers. The company continues investing heavily in capacity and infrastructure as enterprise workloads scale.

📊 ERP Strategy & Industry Direction

🔗 Don’t Rip and Replace PeopleSoft—Pair It with Emerging Tech Instead (CIO.com)
https://www.cio.com/article/4132315/dont-rip-and-replace-peoplesoft-pair-it-with-emerging-tech-instead.html
CIO.com reinforces a strategy many experienced ERP leaders already follow: extend PeopleSoft with modern tools rather than replacing it prematurely. Integrations, automation layers, and AI services allow organizations to modernize while protecting the stability of their core systems.

🔗 AI in ERP: How Intelligence Is Reshaping Enterprise Platforms (NetSuite)
https://www.netsuite.com/portal/resource/articles/erp/ai-erp.shtml
This overview highlights how AI is becoming embedded across ERP workflows—forecasting, automation, anomaly detection, and decision support. The shift isn’t toward replacing ERP systems, but toward making them more intelligent.

🔗 Gartner: Embedded AI in Cloud ERP Will Accelerate Financial Close by 30%
https://www.gartner.com/en/newsroom/press-releases/2026-02-24-gartner-predicts-embedded-ai-in-cloud-erp-applications-will-drive-a-30-percent-faster-financial-close-by-2028
Gartner predicts that embedded AI capabilities will significantly accelerate financial close processes by 2028. Automation of reconciliations, anomaly detection, and workflow orchestration is expected to reshape finance operations.

👩‍💻 PeopleSoft Community & Practice

🔗 IRS FIRE to IRIS: What PeopleSoft Customers Need to Know for 2026 Filings
https://blogs.oracle.com/peoplesoft/irs-fire-to-iris-what-peoplesoft-customers-need-to-know-for-2026-filings
Oracle outlines the transition from the IRS FIRE system to IRIS for tax reporting. Organizations using PeopleSoft must understand the changes and prepare their reporting processes accordingly to ensure compliance.

🔗 PeopleTools Sessions of Interest at Blueprint 4D 2026
https://blogs.oracle.com/peoplesoft/peopletools-sessions-of-interest-at-blueprint-4d-2026-2
Oracle highlights key PeopleTools sessions at Blueprint 4D, including topics on platform capabilities, automation, and modernization strategies. These sessions provide a good roadmap for teams planning upgrades or exploring new features.

🔗 PeopleSoft 2026 Product Roadmap Overview
https://blog.peoplesoftcareer.com/peoplesoft-2026-product-roadmap/
This overview summarizes major roadmap directions for PeopleSoft in 2026, including continued UX improvements, AI integrations, and platform modernization initiatives.

🔗 Automating Document Merges in PeopleSoft with Java and PeopleCode
https://newpeoplesoft.wordpress.com/2026/03/11/automating-document-merges-in-peoplesoft-pdf-jpg-and-png-consolidation-with-java-and-peoplecode/
A practical technical guide showing how to automate document merging processes inside PeopleSoft. It’s a great example of how PeopleCode and Java integration can streamline operational workflows.

💬 Aaron’s Take

Edition 28 reinforces something that’s becoming increasingly obvious across the ERP landscape: the future of ERP isn’t replacement—it’s augmentation.

Organizations that rush into rip-and-replace transformations often underestimate the complexity and cost involved. Meanwhile, teams that thoughtfully integrate modern technologies, including AI services, automation layers, and observability tools, can dramatically improve their ERP environments without destabilizing them.

Oracle’s market momentum reflects the infrastructure side of this story. Demand for cloud capacity and AI platforms is growing rapidly, and Oracle is positioning itself as a key provider of that infrastructure.

But the more interesting story may be happening inside existing ERP platforms like PeopleSoft. Incremental improvements, better integrations, and smarter automation are quietly transforming how these systems deliver value.

In other words, modernization doesn’t always look dramatic. Sometimes it looks like disciplined progress.

🌐 Join the Community

If you want to stay current on ERP strategy, PeopleSoft innovation, and cloud platform trends, subscribe at PeopleSoftCloud.com.

Each week you’ll receive:

✅ Curated ERP and PeopleSoft insights
✅ Context around cloud and AI trends
✅ Practical guidance for enterprise technology teams

See you next week for Edition 29.

Subscribe now

PeopleSoft remains one of the most deeply embedded enterprise platforms in higher education, the public sector, and complex commercial environments. The investment is not limited to licensing or infrastructure. It includes decades of configuration, alignment of business logic, reporting maturity, and institutional knowledge. Replacing that foundation means replicating it elsewhere, often at a higher cost and with greater risk. The executive question should not be whether the platform is new, but whether it continues to deliver measurable value.

Total Cost of Ownership Versus Total Cost of Change

Most ERP replacement conversations focus on subscription pricing comparisons. Vendors highlight lower licensing costs or bundled features to create the impression of savings. However, the total cost of ownership rarely tells the full story without considering the total cost of change. Implementation, retraining, integration rebuilds, and stabilization periods often dwarf projected licensing differences.

The total cost of change includes both visible and hidden components. These typically include:

• Multi-year implementation services and integration rebuilds

• Productivity loss during transition and retraining cycles

• Temporary parallel system costs and stabilization overhead

Organizations frequently underestimate the duration of these transition costs. Even successful implementations can take years for operational efficiency to match the pre-migration baseline. From an executive standpoint, staying on PeopleSoft may represent the lower-risk, higher-return decision when these full lifecycle costs are modeled honestly.

The ROI of Existing Customization and Process Alignment

PeopleSoft environments often reflect years of business process refinement. Customizations, bolt-ons, and integrations are rarely random. They represent accumulated decisions that align technology with organizational reality. Replacing the platform means re-evaluating or recreating that alignment from scratch.

While customization is sometimes portrayed as technical debt, it is often institutional intelligence encoded in software. That intelligence carries real value. Eliminating it without a compelling return introduces operational friction and compliance risk. The ROI of staying on PeopleSoft includes preserving the alignment that has been built up.

When CIOs quantify the cost of rebuilding custom integrations and reporting structures in a new system, the financial case becomes clearer. Even modest environments can represent thousands of hours of development and configuration work. Preserving that investment is not conservatism. It is disciplined capital management.

Stability as a Financial Asset

Stability is frequently undervalued because it lacks a marketing narrative. When a system runs consistently, it does not generate headlines. However, stability has measurable economic value. Predictable operations reduce incident costs, improve audit performance, and protect institutional reputation.

Financial leaders understand the value of reduced volatility. A stable ERP reduces the likelihood of large, unplanned expenditures tied to system failures or rushed remediation. It also reduces executive distraction during periods of organizational change. These benefits compound quietly over time.

Staying on PeopleSoft allows organizations to redirect capital from reactive system replacement toward proactive modernization. Cloud migration, automation, and analytics enhancements often produce higher marginal returns than wholesale reimplementation. Stability, when leveraged intentionally, becomes a funding source for innovation rather than an obstacle.

Leveraging Modernization Without Replacement

Remaining on PeopleSoft does not imply stagnation. Modernization can occur at the infrastructure, integration, and operational layers without replacing the core system. Cloud deployment, observability tooling, and automation pipelines can materially improve cost efficiency and delivery speed. These improvements generate measurable operational gains without destabilizing business processes.

CIOs can often capture modernization value through targeted initiatives such as:

• Infrastructure optimization in public cloud environments

• Standardized deployment pipelines and automation frameworks

• Data integration enhancements that improve reporting velocity

Each of these investments strengthens the platform while preserving institutional alignment. This approach maximizes return on existing investment instead of resetting the balance sheet. It also reduces the execution risk associated with large-scale transformation programs.

The Strategic Advantage of Optionality

Perhaps the most underappreciated benefit of staying on PeopleSoft is the optionality it offers. By avoiding a forced replacement, CIOs preserve strategic flexibility. They retain the ability to modernize incrementally, test new platforms selectively, and respond to regulatory or market shifts without being locked into a single trajectory.

Optionality has financial value because it reduces irreversible commitments. Large ERP replacements often represent multi-year bets with limited exit paths. Staying on PeopleSoft allows organizations to evaluate alternatives from a position of strength rather than from a position of urgency. That leverage improves negotiation power and long-term resilience.

From an executive standpoint, the decision to remain on PeopleSoft should not be framed as defensive. It can be a proactive capital-allocation decision grounded in returns, risk mitigation, and strategic flexibility.

A Disciplined Approach to ERP Leadership

The executive case for staying on PeopleSoft rests on disciplined analysis rather than nostalgia. It requires modeling full lifecycle costs, valuing institutional alignment, and recognizing stability as an asset. When these factors are considered honestly, the narrative shifts. Staying on PeopleSoft often emerges as a rational and financially responsible strategy.

This does not mean that replacement is never appropriate. It means that replacement should be justified by a clear, measurable advantage rather than external pressure or perception. CIOs who make this distinction lead with clarity and credibility. In the next article, we will explore how to communicate this case effectively to boards and executive peers.

The Hidden Costs of ERP Migration

The Costs That Rarely Make the Slide Deck

ERP migration proposals often present a clean financial narrative. Licensing projections, implementation timelines, and high-level efficiency gains dominate the executive summary. What receives far less attention are the secondary and tertiary costs that surface only after contracts are signed. These costs are not theoretical. They are structural consequences of large-scale system replacement.

Hidden migration costs rarely appear as line items labeled “risk” or “disruption.” Instead, they emerge through extended stabilization periods, increased reliance on consulting, and declining internal confidence. By the time these effects are visible, reversing course is no longer practical. For CIOs, understanding these hidden dimensions is critical before committing to replacement.

Productivity and Institutional Knowledge Loss

One of the most underestimated costs of ERP migration is the decline in productivity. During transition periods, teams operate in parallel modes of learning and delivery. Business users must adapt to new workflows, new interfaces, and new reporting structures. Even when training is thorough, confidence drops before it rises.

Institutional knowledge is another invisible asset that erodes during migration. Long-tenured administrators and analysts often carry contextual understanding that cannot be easily documented. When those individuals disengage or exit during transformation cycles, organizations lose operational memory. That loss translates into slower troubleshooting, longer cycle times, and increased dependency on external advisors.

The financial impact of knowledge erosion is rarely modeled. Yet it directly affects delivery speed and decision quality. Over time, this erosion compounds into measurable performance drag.

Integration Rebuild and Data Realignment

ERP systems rarely operate in isolation. They anchor dozens or even hundreds of integrations across finance, HR, analytics, and operational systems. Migration requires either rebuilding or rearchitecting these connections. Each rebuild introduces new testing cycles, new failure points, and new governance requirements.

Data realignment also presents hidden complexity. Historical data structures often do not map cleanly into new platforms. Transformation logic must be rewritten and validated, frequently under tight deadlines. Even minor discrepancies can create audit concerns and reporting inconsistencies.

These integrations and data adjustments extend well beyond initial go-live. Organizations often spend years refining connections that previously operated reliably. The cost of rebuilding trust in data is rarely included in financial models.

Escalating Vendor and Consulting Dependency

Migration initiatives typically require significant external expertise. Implementation partners, system integrators, and vendor specialists become central to delivery. While this support accelerates initial deployment, it can create a long-term dependency if internal capability is not intentionally rebuilt. Consulting costs often exceed original projections.

Vendor dependency also shifts leverage dynamics. Contract structures, licensing adjustments, and roadmap alignment may become more constrained after migration. Organizations that once exercised autonomy over their ERP environment may find themselves navigating predefined boundaries. That shift can affect innovation timelines and negotiation strength.

The strategic cost of reduced leverage is difficult to quantify, but it is very real. Over time, limited flexibility can restrict competitive advantage.

Organizational Fatigue and Cultural Impact

Large ERP migrations demand sustained attention from leadership and operational teams. Multi-year programs often compete with other strategic initiatives for funding and executive focus. This prolonged intensity creates organizational fatigue. When fatigue sets in, risk tolerance declines and innovation slows.

Cultural impact is equally significant. Teams that experience repeated disruptions may become hesitant to embrace future transformation efforts. Confidence in IT leadership can weaken if promised outcomes are delayed. These cultural effects influence long-term performance more than short-term budget overruns.

Unlike infrastructure costs, cultural impact does not appear in financial statements. However, it shapes the organization’s ability to execute future strategy. Ignoring this dimension creates blind spots in executive planning.

A Framework for Evaluating Hidden Costs

CIOs can mitigate hidden migration costs by expanding evaluation frameworks beyond licensing comparisons. A disciplined assessment should include:

• Modeled productivity decline during transition periods.

• Institutional knowledge retention strategies and succession planning.

• Full integration rebuilds inventories and data validation timelines.

• Multi-year consulting and vendor dependency projections.

Including these dimensions produces a more honest financial model. It also strengthens credibility with boards and executive peers. When leaders clearly articulate hidden costs, decision quality improves.

Migration may still be justified in certain scenarios. However, it should proceed with full awareness of both visible and invisible implications. Hidden costs do not eliminate modernization as an option. They simply require it to be evaluated with greater rigor.

Read more

☕ This Week’s Focus

Edition 27 centers on a theme that keeps resurfacing in 2026: ERP modernization is less about replacement and more about refinement.

Oracle continues to land major public-sector wins and expand its cloud footprint in federal modernization initiatives. At the same time, real-world ERP implementation stories remind us that success depends on thoughtful customization—not over-customization, not blind standardization.

Inside the PeopleSoft ecosystem, Cloud Manager continues to mature, PeopleTools 8.62 capabilities are expanding, and natural language experiences are moving from concept to delivered functionality.

Let’s break it down.

⚙️ Oracle, Public Sector & Cloud Expansion

🔗 Oracle Lands Air Force Win (Yahoo Finance)
https://finance.yahoo.com/news/oracle-lands-air-force-win-152003927.html
Oracle secured a significant contract win with the U.S. Air Force, reinforcing its position in federal cloud and infrastructure services. Public-sector validation remains one of Oracle’s strongest credibility anchors in 2026.

🔗 OCI to Support CMS Modernization Initiative (Oracle Press Release)
https://www.oracle.com/news/announcement/oracle-cloud-infrastructure-to-support-centers-for-medicare-and-medicaids-modernization-initiative-2026-02-11/
Oracle Cloud Infrastructure will support the Centers for Medicare & Medicaid Services’ modernization efforts. This is another large-scale healthcare transformation backed by OCI, signaling continued trust in Oracle’s ability to deliver secure, scalable environments.

Together, these stories reinforce an important point: while AI narratives dominate headlines, it’s infrastructure reliability and compliance capabilities that win major contracts.

📊 ERP Strategy: Why Smart Customization Matters

🔗 What Midwest Groundcovers Learned from Implementing a New ERP System (Greenhouse Grower)
https://www.greenhousegrower.com/technology/what-midwest-groundcovers-learned-from-implementing-a-new-erp-system/

This implementation story highlights a lesson seasoned ERP teams already understand: the danger isn’t customization. Rather, it’s unintentional customization.

Midwest Groundcovers discovered that blindly replicating legacy processes inside a new ERP system can stall transformation. At the same time, refusing all customization in the name of “best practice” can create operational friction.

The sweet spot is disciplined customization. Where processes are evaluated, simplified where possible, and extended only when business value justifies it.

For PeopleSoft teams, this lesson resonates. Event Mapping, Page & Field Configurator, and delivered frameworks exist precisely to enable thoughtful extension without destabilizing the core. Smart customization preserves upgradeability. Reactive customization destroys it.

👩‍💻 PeopleSoft Community & Practice

🔗 Image Highlights: Cloud Manager Image 21 (YouTube)

This video walks through key updates in Cloud Manager Image 21, including refinements in environment lifecycle automation, provisioning enhancements, and improved orchestration capabilities. For teams managing PeopleSoft in OCI, Cloud Manager continues evolving into a true platform operations tool—not just a deployment assistant.

🔗 Mastering Notification Composer & Landing Page Notifications in PeopleTools 8.62 (NewPeopleSoft Blog)
https://newpeoplesoft.wordpress.com/2026/02/11/mastering-notification-composer-and-landing-page-notifications-in-peopletools-8-62/
A detailed guide to using Notification Composer and landing page alerts effectively. These features are powerful when governed well, and distracting when overused. The key is intentional communication design.

🔗 Is GenerateComponentPortalURL Still Relevant? (JSMPros)
https://blog.jsmpros.com/2026/02/is-generatecomponentportalurl-still.html
A thoughtful technical exploration of whether older PeopleCode patterns remain appropriate in modern Tools releases. The answer isn’t binary. Some patterns evolve; others remain valuable when used properly. Modernization requires understanding, not reflexively replacing, core capabilities.

🔗 Natural Language Assistant in PeopleSoft (Oracle Blog)
https://blogs.oracle.com/peoplesoft/natural-language-assistant-in-peoplesoft
Oracle introduces Natural Language Assistant capabilities within PeopleSoft, enabling users to interact with the system more conversationally. This marks a tangible step toward embedded AI experiences inside PeopleSoft—not as an external bolt-on, but as part of the user workflow.

💬 Aaron’s Take

Edition 27 reinforces something I’ve seen repeatedly across ERP programs: durability beats drama.

Oracle’s public-sector wins demonstrate that reliability, compliance, and scale still matter more than hype. At the implementation level, stories like Midwest Groundcovers highlight that success comes from disciplined decisions, not extremes.

And inside the PeopleSoft world, the pattern continues: Cloud Manager gets stronger, Tools capabilities deepen, and AI becomes more practical.

The organizations that win in 2026 won’t be the ones chasing the newest acronym. They’ll be the ones who:

• Standardize where possible
• Customize where justified
• Automate where repeatable
• Govern where necessary

That’s not flashy. It’s effective.

🌐 Join the Community

If you’re finding value in these weekly breakdowns, subscribe at PeopleSoftCloud.com for:

✅ ERP and PeopleSoft modernization insight
✅ Cloud infrastructure and automation strategy
✅ Practical AI context for enterprise systems

See you in Edition 28.

The reality is this:

PeopleSoft didn’t fail us.
Our operating model failed PeopleSoft.

When organizations struggle with PeopleSoft, the root cause is rarely the software itself. It’s almost always the way we deploy, govern, and own it. If you moved this same legacy mindset and operating model to any other ERP, it would look slow, brittle, and outdated, too.

Subscribe now

Legacy Thinking Creates “Legacy Systems”

For years, many PeopleSoft environments have been run with habits formed in a very different era:

* Manual builds that only one or two people understand.
* Environment drift that makes every change risky.
* Release processes held together by spreadsheets and tribal knowledge.
* Monitoring that relies on users reporting problems after the fact.

None of that is a PeopleSoft limitation. That’s an operating model problem.

If you applied those same practices to a modern SaaS-adjacent platform, it would degrade just as quickly. Complexity compounds when discipline is missing.

Modernization Is an Operating Shift, Not a Rip-and-Replace

True PeopleSoft modernization starts with a mindset shift: treating PeopleSoft as a platform, not just an application.

Platform thinking changes the questions leaders ask. Instead of “How fast can we get off PeopleSoft?” the question becomes “How do we operate this platform in a modern, resilient way?”

That leads directly to fundamentals:

* Automation instead of hand-built environments
* Repeatable infrastructure instead of one-off fixes
* Version control instead of shared folders
* Observability instead of reactive troubleshooting

When these elements are in place, PeopleSoft behaves very differently. Deployments become predictable. Failures become visible early. Teams spend less time firefighting and more time improving.

Governance and Ownership Matter More Than Tools

Another quiet failure point is ownership. In many organizations, PeopleSoft sits in an awkward gap between infrastructure, applications, and the business. No single group owns the full lifecycle, so decisions get fragmented and slow.

Modern platforms require clear ownership models. Someone must be accountable for how the system is built, operated, secured, and improved over time. Without that clarity, even the best tooling can’t compensate. This is why many “modernization” efforts stall. They focus on technology choices while leaving governance untouched.

The Real Question Leaders Should Be Asking

The most important question isn’t whether PeopleSoft is still viable.

It’s this: Are we operating it in a way that would succeed on any platform?

If the answer is no, moving to the cloud or to SaaS won’t fix the underlying issue. It will just shift the pain and usually increase the cost.

PeopleSoft didn’t fail us.
Our operating model failed PeopleSoft.

And the good news is that operating models can be redesigned, without starting over. If you fix the operating model, PeopleSoft is a differentiator, not an anchor.

Today, that framing creates friction. When PeopleSoft is viewed only as an application, investment decisions focus on maintenance rather than capability. Teams optimize for minimizing disruption instead of enabling outcomes. Over time, the system becomes isolated from broader enterprise strategy, even though it remains central to business operations.

An application mindset also limits leadership imagination. It encourages CIOs to think defensively rather than strategically. As enterprise architectures evolve, this narrow framing increasingly fails to reflect how PeopleSoft is actually used.

What It Means to Treat PeopleSoft as a Platform

A single interface or deployment model does not define a platform. It is defined by its ability to enable other systems, teams, and capabilities. When PeopleSoft is treated as a platform, it becomes an anchor point for data, process, and integration rather than a standalone workload. This shift changes how leaders evaluate value.

Platform thinking recognizes that PeopleSoft already powers critical enterprise workflows. It also acknowledges that those workflows generate data and events that other systems depend on. Instead of insulating PeopleSoft from change, a platform mindset exposes it in controlled and intentional ways. APIs, integration frameworks, and automation become first-class design considerations.

Most importantly, platform thinking reframes PeopleSoft as an enabler of innovation rather than an obstacle. That reframing unlocks new conversations between IT and the business. The system stops being something to work around and starts being something to build on.

Read more

The CIO arrived at 8 AM sharp, along with CFO Patricia Winters and VP of Business Operations James Chen. Maya had the conference room set up with her laptop connected to the projector, the infrastructure repository open in one window, a terminal in another.

“Good morning,” Harrison said, settling into his chair. “I understand you have a demonstration.”

“We do,” Maya said. “Three weeks ago, you gave us twelve weeks to prove PeopleSoft modernization could compete with SaaS migration. I want to show you what we’ve accomplished in the first three weeks.”

She pulled up her summary slide:

Weeks 1-3: Foundation Complete

• Week 1: Honest assessment, baseline metrics, quick wins

• Week 2-3: Infrastructure as Code implementation

• Result: 99.7% faster environment provisioning, $178K annual savings (dev only)

“Show me the demo,” Harrison said—no preamble, straight to business.

Maya opened her terminal. “I’m going to provision a complete PeopleSoft environment from scratch. When I run this command, Terraform and Chef will build a database, application servers, web servers, networking, storage, and configuration—everything needed for a functional PeopleSoft instance.”

She typed the command and hit enter.

“How long will this take?” Winters asked.

“About seventy-five minutes,” Maya said. “Our baseline three weeks ago was eighteen days.”

Winters blinked. “Eighteen days to seventy-five minutes?”

“Correct. And I’m not doing anything during these seventy-five minutes except watching automated processes run. Previously, this would have required multiple engineers working across multiple teams for days.”

They watched as infrastructure was provisioned in real-time. Harrison asked sharp questions—What happens if it fails? How do you validate correctness? Can you rebuild production this way? Maya answered each question confidently, occasionally pulling in Jake or Tom for technical details on database configuration or application-tier setup.

Seventy-three minutes later, the PeopleSoft sign-in screen appeared.

Harrison was quiet for a moment. “That’s… impressive. Walk me through the business value.”

Maya pulled up her cost analysis. “This dev environment costs us $110 per month to run versus $14,000 in our data center. Admin time to maintain it drops from forty hours per quarter to near zero. Total savings for this one environment: $178,000 annually. We have four environments. Extrapolating—”

“Seven hundred thousand per year,” Winters finished, doing the math. “That’s significant.”

“And that’s before we account for improved velocity,” Maya added. “When our developers can spin up test environments in an hour instead of waiting weeks, they move faster. When we can rebuild from disaster in ninety minutes instead of hoping our untested backup scripts work, we reduce risk. When our infrastructure knowledge lives in version-controlled code instead of tribal memory, we eliminate key person dependencies.”

Harrison leaned back. “What’s your plan for the next nine weeks?”

“Week 4, which starts today: CI/CD pipelines for automated testing and deployment of customizations. Week 5: Database modernization using managed services. Weeks 6-7: Observability and monitoring infrastructure. Week 8-9: Security automation and integration modernization. Weeks 10-12: Cost validation, scaling tests, and final presentation.”

“You’re on track?” Harrison asked.

“We’re ahead of track,” Maya said honestly. “I expected the infrastructure as code work to take three weeks with lots of struggles. We completed it in two weeks, delivering high-quality results. The team is learning faster than I anticipated.”

Harrison stood. “Good. Keep going. I want weekly updates. And Maya—this is good work. Genuinely impressive. But you’re still proving a concept. I need to see this working in production before I can take it to the board as an alternative to the SaaS plan.”

“Understood,” Maya said. “By Week 12, we’ll have production evidence.”

After the executives left, Maya’s team emerged from their desks where they’d been nervously monitoring the demo.

“How’d it go?” Tom asked.

“Harrison called it genuinely impressive,” Maya said. “Which from him is practically a standing ovation.”

“So we’re good?” Jake asked.

“We’re good for now,” Maya said. “But he’s right—we’re still proving a concept. We need production validation. Which means everything we build in the next nine weeks needs to be production-ready, not just demos.”

She pulled up the Week 4 plan on the screen. “Speaking of which: CI/CD pipelines. This week, we’re going to automate the testing and deployment of PeopleSoft customizations. No more manual exports and imports. No more emailing project files around. No more deployments that take six hours. We’re building a pipeline.”

“Before we dive into that,” Sarah said carefully, “we need to talk about something that happened over the weekend.”

Maya’s stomach dropped. “What happened?”

“Production incident. Saturday at 2:47 AM. Integration Broker went down. Took forty-three minutes to detect. A batch job had failed, and someone checked their email. Took another ninety minutes for Marcus to troubleshoot and fix. Total outage: two hours, thirteen minutes.”

“What caused it?” Maya asked.

“Web server ran out of memory and crashed,” Marcus said. “Took the IB domain with it. We don’t have memory monitoring, so I didn’t know what was wrong until I SSH’d into each server, checked logs, found the out-of-memory errors, and restarted services.”

“Two hours to diagnose a memory issue,” Maya said flatly.

“In my defense, the logs are spread across seventeen servers with no aggregation,” Marcus said. “I had to check each one manually. And our monitoring only watches whether processes are running, not whether they’re healthy.”

Maya walked to the whiteboard and wrote in large letters: “WEEK 4 REVISED PLAN: OBSERVABILITY FIRST.”

“Here’s the thing,” Maya said, turning to face her team. “We can build the prettiest CI/CD pipeline in the world, but if we can’t see what’s happening in production, we’re still operating blind. Saturday’s incident proved that. We need observability before we need CI/CD.”

“What’s the difference between monitoring and observability?” Priya asked.

“Great question,” Maya said. “Monitoring tells you something is broken. Observability tells you why it’s broken and helps you understand system behavior. Right now, we have basic monitoring—we know when a process dies. But we don’t have observability. We can’t answer questions like ‘Why is the system slow?’ or ‘What changed before this error started?’ or ‘Which integration is causing database contention?’”

She drew three columns on the whiteboard: Logs, Metrics, Traces.

“These are the three pillars of observability,” Maya explained. “Logs tell you what happened—detailed records of events, errors, transactions. Metrics tell you how the system is performing, including CPU, memory, response times, throughput. Traces tell you the path a request takes through your system—from web server to app server to database and back.”

“We have logs,” Tom pointed out.

“We have logs scattered across seventeen servers in different formats with no way to search them efficiently,” Maya corrected. “Marcus spent ninety minutes manually grepping through log files on Saturday. That’s not observability. That’s archaeology.”

“So what does good observability look like?” Lisa asked.

Maya pulled up her laptop and opened a screenshot she’d saved from her previous role—a Grafana dashboard with colorful charts showing system metrics, error rates, and response times, all in real-time.

“This is what we’re building toward,” she said. “A single pane of glass where we can see everything happening in our PeopleSoft environment. Application server health. Database performance. Integration throughput. User experience metrics. Error rates. Everything.”

“And when something breaks?” Jake asked.

“We see it immediately,” Maya said. “The dashboard shows the anomaly. We can drill into logs filtered by timeframe and component. We can see what changed right before the problem started. We can correlate events across different systems. Instead of spending ninety minutes figuring out what’s wrong, we spend five minutes confirming what we already suspect and fifteen minutes fixing it.”

“That sounds expensive,” Tom said. “Enterprise monitoring tools cost a fortune.”

“It would be,” Maya agreed, “if we were buying commercial tools. But we’re going to build it using open source: OpenSearch for log aggregation and analysis, Prometheus for metrics collection, Grafana for visualization, and Tempo for distributed tracing. Total cost: mostly our time to implement, plus about $200/month in infrastructure to run it.”

Sarah was nodding enthusiastically. “This is actually going to make our lives so much better. I’ve worked with observability stacks before. Once you have good observability, you can’t imagine working without it.”

“Okay,” Maya said. “Here’s the Week 4 plan, revised. Monday through Wednesday: we implement centralized logging with OpenSearch. Every log from every PeopleSoft component flows into a single location where we can search it. Thursday through Friday: we implement metrics collection with Prometheus and build our first Grafana dashboards. Next week, we’ll add distributed tracing and alerting.”

“That’s a lot for one week,” Marcus said.

“It is,” Maya admitted. “But we’re not building perfection. We’re building ‘better than Saturday night.’ If by Friday we have centralized logs and basic metrics, we’ve massively improved our ability to troubleshoot. The rest can evolve.”

“Who’s doing what?” Priya asked.

“Marcus, you’re leading the OpenSearch implementation since you already researched it in Week 1. Sarah, you’re helping Marcus with the technical architecture. Jake, you’re instrumenting the database to export metrics—Oracle has built-in monitoring views we can scrape. Tom, you’re configuring log shipping from all the application servers. Priya and Lisa, you’re documenting what we learn and building runbooks for using the observability tools.”

“And you?” Tom asked.

“I’m building the Grafana dashboards and figuring out what we need to measure to prove our system is healthy,” Maya said. “Plus, I’m talking to other teams who might want to consume our metrics. If we’re building an observability platform, we should make it useful beyond just PeopleSoft.”

She capped the marker. “Questions?”

“Yeah,” Jake said. “What do we do about Saturday’s incident? Do we need to file some kind of post-mortem or incident report?”

“We do,” Maya said. “And we’re going to use it as a teaching moment. Let me show you what a blameless post-mortem looks like.”

Read more

👋 Welcome Back

After a short hiatus, The Modern ERP Digest is back with Edition 26.

Sometimes a pause is useful. It gives space to see which stories actually matter after the initial headlines fade. Coming back into 2026, one thing is clear: the ERP conversation has sharpened. AI hype is colliding with legal scrutiny, capital markets are watching Oracle closely, and enterprises are making more deliberate, modular decisions about how ERP fits into their future.

Subscribe now

This edition reflects that shift. It blends market pressure, AI ambition, and very real PeopleSoft progress—exactly where ERP leadership lives today.

☕ This Week’s Focus

Edition 26 centers on credibility and consequence.

Oracle’s AI narrative is being tested by lawsuits and investor scrutiny, even as enterprises continue adopting Oracle technologies at scale. At the same time, PeopleSoft continues to move forward with meaningful HCM enhancements, and the broader ERP market is openly embracing best-of-breed and agentic AI models.

This isn’t a step backward. It’s a sign of maturity.

⚙️ Oracle, Markets & AI Pressure

🔗 Investors Sue Oracle, Alleging Executives Sold $18.7B Amid AI Hype (InvestmentNews)
https://www.investmentnews.com/regulation-legal-compliance/investors-sue-oracle-allege-executives-dumped-187b-amid-ai-hype/265164
Investors have filed lawsuits alleging that Oracle executives sold significant stock during peak AI enthusiasm. Regardless of outcome, the story underscores how closely Oracle’s AI messaging is being examined—and how accountability follows ambition.

🔗 Oracle Plans $50B Capital Raise to Support Cloud Infrastructure Demand (ERP Today)
https://erp.today/oracle-plans-50b-capital-raise-to-support-cloud-infrastructure-demand/
Oracle’s reported plan to raise $50B for cloud infrastructure highlights the scale of demand it’s betting on. This move reinforces Oracle’s belief that AI and cloud workloads will continue to grow, but also raises expectations around execution and returns.

🔗 U.S. Enterprises Increasingly Adopting Oracle Solutions (Yahoo Finance)
https://finance.yahoo.com/news/u-enterprises-increasing-adopting-oracle-180845415.html
Despite market noise, adoption data tells a steadier story. U.S. enterprises continue expanding their use of Oracle platforms, suggesting that while sentiment swings, operational decisions remain grounded in capability and trust.

📊 ERP, AI & Industry Direction

🔗 Reimagining ERP for the Agentic AI Era (MIT Technology Review – Report Overview)
https://www.technologyreview.com/2026/01/20/1129965/reimagining-erp-for-the-agentic-ai-era/
This downloadable report explores how ERP systems are evolving from systems of record into systems of action. Agentic AI, orchestration layers, and autonomous workflows are central themes. The key takeaway: ERP isn’t being replaced—it’s being repositioned.

🔗 ERP in 2026: More AI, More Best-of-Breed Add-Ons (CIO.com)
https://www.cio.com/article/4121113/erp-in-2026-more-ai-more-best-of-breed-add-ons.html
CIO.com outlines a clear trend for 2026: core ERP platforms paired with specialized tools. Rather than monolithic replacements, organizations are layering AI, analytics, and niche capabilities on top of stable ERP foundations.

🔗 ERP Survey Shows Customers Re-Evaluating Vendor Value (The Register)
https://www.theregister.com/2026/01/19/erp_survey_rimini_street/
Survey results highlighted by The Register show growing scrutiny of ERP vendor costs and roadmaps. Customers are demanding clearer value, longer viability, and less forced migration—signals that favor platforms teams truly understand.

👩‍💻 PeopleSoft Community & Practice

🔗 What’s New in PeopleSoft HCM Update Image 54 (Oracle Blog)
https://blogs.oracle.com/peoplesoft/whats-new-in-peoplesofts-hcm-update-image-54-key-enhancements-and-features
Oracle details the latest HCM Image 54 enhancements, including usability improvements, feature refinements, and continued investment in employee and manager self-service. It’s another reminder that PeopleSoft HCM remains an actively evolving platform.

🔗 Cornell’s Duffield Gift Highlights Long-Term PeopleSoft Impact (WSJ)
https://www.wsj.com/us-news/education/cornell-duffield-gift-engineering-donation-peoplesoft-fc1894a3
The Wall Street Journal recounts how Cornell’s engineering program benefited from alum success tied in part to PeopleSoft’s early growth. It’s a rare mainstream acknowledgment of PeopleSoft’s lasting influence in higher education and enterprise technology.

💬 Aaron’s Take

Edition 26 reinforces a pattern that’s becoming impossible to ignore: ERP is no longer about promises—it’s about proof.

Oracle is betting big on AI and cloud, and the markets are watching closely. Lawsuits, capital raises, and adoption metrics all tell different parts of the same story. Ambition attracts scrutiny, and scrutiny demands results.

At the same time, PeopleSoft teams are quietly moving forward—adopting new HCM features, modernizing selectively, and operating within architectures they actually understand. Across the industry, organizations are choosing composition over replacement and intention over impulse.

That’s not hesitation. That’s maturity.

If 2025 was about sorting hype from signal, 2026 is shaping up to be about earning trust—technically, financially, and operationally.

I’m glad to be back. Let’s keep going.

🌐 Join the Community

If you’re reading this after the break, now’s a great time to subscribe at PeopleSoftCloud.com for:

✅ Weekly ERP, PeopleSoft, and cloud insights
✅ Practical context around AI and platform decisions
✅ Signals that matter for real enterprise teams

Thanks for sticking around—and welcome back to The Modern ERP Digest.

Every major cloud provider can technically run PeopleSoft. That fact alone does not make them equivalent. Each platform encodes assumptions about control, customization, pricing, and governance. CIOs need to understand those assumptions before committing the organization to a multi-year operating model.

The most crucial cloud question is not whether PeopleSoft will run. The real question is what kind of enterprise you are building once it does.

Cost Is More Than Infrastructure Pricing

Cloud cost conversations often start with compute and storage pricing. While those numbers matter, they rarely determine long-term spend. The most significant cost drivers tend to be operational complexity, licensing interactions, and the degree of automation an organization can realistically sustain. These factors vary significantly by cloud platform.

Some environments encourage standardization and infrastructure-as-code, which lowers marginal costs over time. Others rely more heavily on managed services that trade simplicity for long-term expense. CIOs must look beyond first-year projections and understand how costs behave at scale. A platform that looks inexpensive early can become restrictive and expensive as requirements grow.

Cloud cost discipline depends on visibility, governance, and internal capability. The more control the organization retains, the more options it has to optimize. That control is not evenly distributed across providers.

Read more

What has changed is how leaders think about that reality. Instead of forcing everything into a single platform, CIOs increasingly focus on orchestration, integration, and clear ownership. Hybrid ERP enables organizations to continue innovating while preserving stability in core systems. This balance matters because it helps ensure that the pace of change is manageable across all systems. Treating every system as equally disposable creates unnecessary risk.

Stability and Innovation Are Partners

A common misconception in ERP strategy is that stability and innovation sit on opposite ends of a spectrum. In this framing, stable systems are slow, and innovative systems are fragile. This thinking leads organizations to push core platforms aside in pursuit of speed. Over time, that approach undermines both reliability and confidence.

In practice, stability enables innovation when intentionally used. A reliable system of record provides clean data, predictable processes, and trusted outcomes. Innovation builds more effectively on that foundation than on constantly shifting platforms. When leaders recognize this relationship, strategy shifts from replacement to enablement.

Hybrid ERP works because it assigns different roles to different systems. Core ERP remains focused on transactional integrity and governance. Surrounding platforms handle experimentation, user experience, and rapid iteration. Each system plays to its strengths instead of competing for relevance.

Read more