East2i.
Learn / Mainframe
East2i Learn / Mainframe

Your Mainframe is critical. Its future shouldn't be uncertain.

Preserve skills. Control costs. Evolve your systems without breaking anything.

A Mainframe that works doesn't need to be replaced. But retirements, running costs and integration difficulties can hold back the whole company. East2i relies on Mainframe specialists with more than 40 years of combined experience, with one clear goal: your teams running their system on their own.

Our principle: we don't come to replace what works. We come to understand what stops you getting more value from it, and to pass the know-how on to your teams.
01 Warning signs

What should alert you

Each of these signs is an operational risk before it is a technical problem.

Your experts are retiring

And their knowledge isn't written down anywhere.

Skill gaps in the team

COBOL, CICS, Db2, JCL or z/OS operations only partly mastered.

A bill that keeps rising

MIPS/MSU consumption and licences going up, without more business.

Every connection is a heavy project

Cloud, ERP, CRM, API: everything takes months.

Batch jobs overrunning

Production windows are no longer enough.

Untouchable applications

Nobody dares change them, for lack of documentation.

02 Three key questions

What CIOs ask themselves

Three pillars of our offer, each with its intervention and deliverables.

01

How do we secure and pass on Mainframe know-how?

Skills audit, mapping of critical knowledge, mentoring by senior experts, COBOL, z/OS, CICS, Db2 and operations training, gradual handover of responsibilities.

Deliverables: skills map · training programme · operations documentation
02

How do we control management and running costs?

Analysis of MIPS/MSU consumption, batch jobs, workloads, storage and software contracts; operations optimised without lowering service levels.

Deliverables: cost analysis · costed recommendations · action plan
03

How do we ensure integration and evolution?

Architecture audit, API integration (z/OS Connect where compatible), middleware, DevOps, automated testing, gradual application modernisation.

Deliverables: architecture diagram · API roadmap · technical pilot
03 Pre-assessment

Five questions about your estate

No confidential technical information is requested. Your answers stay in your browser.

04 Our method

Audit, price, break down, deliver

You stay in control of your system, your priorities and your investments. The audit is always quoted separately from what follows.

Module Intervention Financial commitment
M0 Audit and recommendations report Fixed audit fee, separate quote
M1 Documentation and knowledge transfer Independent budget
M2 Running cost optimisation Independent budget
M3 API integration and interoperability Budget per scope
M4 Application modernisation Budget per application or batch
M5 Training and ongoing support Fixed fee or progressive programme

Each module has its own technical description, deliverables, schedule, acceptance criteria and financial proposal. Some have prerequisites: M4 usually requires M1, so that the team understands the code it changes. East2i chooses the specialists according to the module, the related integrations and the size of the estate.

05 The full guide

Before our first conversation

The questions, the prerequisites and the criteria we will be judged on.

Topic Questions
Estate Which critical applications? How many programs, how many batch jobs?
Skills Who masters what? Planned retirements? Level of newcomers?
Costs How have MIPS/MSU and software costs evolved over 3 years? Current contracts?
Integration Which systems must talk to the Mainframe? How today?
Operations Recurring incidents? Batch windows? Continuity plan?
Strategy Keep, optimise, integrate, modernise or migrate? Any decision already made?
  • A sponsor: CIO or head of production
  • Access to operations managers and key developers
  • Consumption reports (SMF, RMF or equivalent) and software contracts for the cost review
  • An inventory, even partial, of applications and interfaces
  • A security and confidentiality framework approved before any access to environments
Indicator Measure
Skills coverage Critical knowledge mastered by at least 2 internal people
Documentation Share of critical applications documented
Running cost Evolution of MIPS/MSU and software bill
Integration lead time Time to expose a new service via API
Stability Production incidents before / after
Autonomy Interventions carried out without an external expert
Illustrative case · fictitious organisation

Atlantis Mutual

Regional mutual insurer, 800,000 members, contracts and claims managed on a Mainframe since 1992, a team of 9.

The problem

3 COBOL/CICS experts retire within 30 months. The 4 recent developers only partly master the environment. Software bill up 18% in 3 years. The member portal has waited a year for access to claims data.

The intervention

3-week M0 audit, report with 4 modules. The insurer activates M1 (6 months of senior expert / developer pairs), then M3 (claims API for the member portal). M2 is planned for the following year.

Indicator Before Target at 12 months
Critical knowledge shared 30% 85%
Critical applications documented 20% 70%
Claims in the member portal None Live via API

Fictitious organisation based on a common situation in insurance and banking. Illustrative figures, not actual results.

06 Offers

One audit, then you choose

Every euro is committed module by module.

Discovery

60-minute conversation with a Mainframe specialist.

Free, no commitment

M0 audit

Technical and operational audit, report, estimated budget per module.

€4,000 to €12,000 excl. VAT depending on estate size

Modules M1 to M5

Activated one by one according to your priorities and budget.

Quoted module by module
Our aim is not to make you dependent on external experts. It is to pass their experience on to your teams.
← Back to the East2i home page
East2i — The outsider that puts people first