Reinvest in the current constraint
- Refresh broad legacy capacity
- Extend the dependency horizon
- Pay again for the eventual exit
Working strategy baseline · 03 August 2026
It is the execution mechanism for reducing legacy dependency, controlling lifecycle risk, increasing operating capacity, and creating the next generation of WHPS services.
Working strategy view · asset lifecycle, cost, capacity, and support data require owner and procurement validation.
01 The portfolio-level decision
Network, storage, VMware, VDI, mainframe capacity, and AI platforms compete for the same capital, risk tolerance, and exit sequence. Treating them separately funds contradiction.
January 2026 business-case baseline + April 10, 2026 mainframe assessment kickoff.
VMware, VDI, network, and storage lifecycle conditions are strategy inputs awaiting reconciled asset inventory and vendor support dates.
02 Original economic intent
The strategy was designed to avoid a large refresh of technology already intended for retirement. Selective support and compensating controls were the bridge; permanent reinvestment was not.
Investment rule No blanket deferral. No blanket refresh. Every dollar traces to retain, bridge, replace, or exit.
*$10–15M is a strategy-discussion planning range—not a validated budget estimate. Current quotations, inventory, support costs, and target-state demand are required.
03 Timing changed the economics
Lifecycle clocks continued while the workload-exit sequence slowed. End-of-life obligations are now reaching the decision window before the planned dependencies are removed.
The destination does not become wrong because execution slowed. The baseline, risk posture, and sequence must become current again.
The delay is a programme estimate to be reconciled against approved dates. No individual cause or attribution is asserted.
04 One disposition per asset
Every infrastructure decision must trace to workload dependency, target architecture, risk, funding, and an explicit review or exit date.
Remove the workload and retire the dependency.
Default for legacy-only demandTime-box support or controls against a dated exit.
Continuity without permanenceKeep capability proven to belong in the target state.
Evidence, economics, resilienceModernize where the function remains but the platform does not.
Target architecture requiredRemove workloads by domain; cover only support and capacity needed for sequenced exit.
Rebaseline support and target hosting/access roles before broad expansion.
Retain justified on-premises demand; separate it from legacy-bound growth.
Address availability and security-critical lifecycle risk; size for the target state.
Inventory business outcomes; use services, APIs, events, or CDC where they fit.
Proposed decision posture · infrastructure, security, finance, procurement, and application-owner validation required.
05 The delivery constraint changed
The AI-native delivery method has made new product demonstrations fast enough to change the strategic conversation—from whether WHPS can build to how quickly each build can enter a governed production path.
Programme-reported functional demonstration cycle.
Programme-reported demonstration built on the BrokerLink Portal foundation.
Programme-reported demonstration cycle for the modern portal experience.
Demonstration scope and elapsed times require validation. They are not production-delivery durations, service levels, or benefit claims.
06 Modernization happens in layers
Phase one establishes an independent experience, service boundary, data contract, and control set. Later waves transfer domain ownership only after parity evidence and release approval.
GroupLink client live · bidirectional IBM CDC deployment underway · DB2 remains authoritative. Mainframe exit is proposed and evidence-gated.
07 Recover the business intent
The goal is not a one-for-one translation of accumulated workarounds. It is a smaller, observable set of future-required business flows with explicit ownership and controls.
Modernization rule Inventory the outcome first. Rebuild the minimum viable flow. Retire the dependency it replaces.
*Approximately 3,000 jobs is a strategy-discussion estimate pending inventory reconciliation. Documented baseline: 140 batch hours per week at the April 2026 assessment kickoff.
08 The viable target estate
Retain on-premises capacity where control, latency, resilience, or economics justify it. Everything else moves toward modern services, shared data, automation, and an explicitly funded exit.
Target-state principle · workload placement, capacity, resilience, commercial terms, and exit dates remain to be decided by evidence.
09 What the strategy buys
A leaner foundation changes both sides of the equation: less effort absorbed by legacy maintenance and more capacity available to operate, engineer, and create.
Contact center, workflow, knowledge, and exception handling.
Build, test, evidence, release, and support through the AI SDLC.
Configurable client experiences and faster routes to new revenue.
Instrument outcomes, improve controls, and reuse proven components.
Target capabilities and potential business outcomes · not represented as realized savings, service levels, or revenue.
10 Decision required
Five leadership actions put technology lifecycle and transformation execution back on one operating line.
Approve or revise the target architecture and legacy-exit intent.
Create one asset, EOL, capacity, support, cost, and dependency register.
Time-box each exception against a named risk and workload exit.
Join product demand and dependency removal in one integrated roadmap.
Assign standing decision authority and a recurring CIO operating review.
Funding, dates, benefits, and risk treatment remain subject to validated inventories, proposals, formal acceptance, and normal governance.
← → navigate · O scenes · B brief · F full screen