Understand platform commitments
Licence terms, infrastructure and integration dependencies shape the migration case. Savings must be calculated, not assumed.
For insurers running Ingenium · COBOL · AIX · IBM MQ
Modernize Ingenium. Prove each step before expanding.
Keep the business knowledge in your core while evaluating a gradual path to new services. BENOVA brings process orchestration, human review and planned AI assistance together with Ingenium-focused tools.
Continuity, deployment options and licence impact must be assessed for each environment.
The problem
Preserve the business knowledge. Reconsider how change is delivered.
Modernization starts with your constraints, not a verdict on COBOL. Identify where platform dependencies, concentrated knowledge and manual handoffs limit the changes your business needs.
Make specialist knowledge accessible
When operational knowledge sits with a few people, routine changes become harder to review and repeat. Documented procedures matter more than a language trend.
Reduce delivery friction
Builds, releases and integration work can involve many manual steps. Measure the actual bottleneck before choosing what to automate.
Make environment differences visible
Differences between development, testing and production can hide defects. Repeatable checks help teams find drift before a release.
A staged approach limits the scope of each change. It still needs reconciliation, recovery planning and operational acceptance.
Core ecosystem
One direction, different levels of readiness
EVA combines Echelon, Vista and Aira for process work; Base connects applications to COBOL workers, Nexus supports Ingenium operations, and Orbit is a hybrid service-host direction. Each product has a distinct purpose and readiness level; qualify it for the target environment before adoption.
Echelon
Orchestration framework
A Rust orchestration backend for work spanning people and services, with AI participation planned. SPINE defines the semantics, Basal holds workflow and navigation authority, and Echelon hosts and persists execution. BENOVA is an intended first application, not evidence of a deployed core migration.
- Durable SQLite runtime
- HTTP interfaces and versioned Flow publication
- Human-task surfaces and external worker integration
SPINE — the semantic core
Defines the meaning of Flow, Process, Task and Outcome independently of the user interface. It is the semantic core within Echelon.
Basal — workflow authority
Owns workflow decisions and navigation. Neither the user interface nor an AI assistant decides independently how a Process advances.
Reflex — built-in execution
Handles built-in process work. Business services and human judgment remain separate responsibilities.
Scheduler & Timeout — planned
Neither is implemented, and their contracts are not settled. Scheduling and deadline handling must not be assumed available.
Binean Nova Base
COBOL worker connectivity and operations
Combines BineanGateway, iman and ingipc to connect applications to Ingenium workers, manage pools and bound execution without requiring a business-logic rewrite first.
- Java gateway: direct socket or binary HTTP
- iman: profiles, dispatcher and worker management
- ingipc: local IPC bridge for COBOL
- Production environment acceptance remains outstanding
Nexus
DevOps for Ingenium
A DevOps toolchain built specifically for Ingenium, running inside VS Code. It turns risky manual operations into standardized, repeatable pipelines.
- Parallel COBOL compilation driven by a dependency graph
- Verified database backup and restore
- Policy management: export, import and copy across environments
- Start/stop regions and automate day-to-day operations
- Credentials encrypted with AES-256-GCM, never written to logs in clear text
Orbit
Hybrid service host
Orbit is being developed as a hybrid service host: a way to connect Ingenium and new services behind an API facade. Each integration needs its own validation before traffic is moved.
- Target: legacy and new services side by side
- REST integration where the core interface permits it
- Assess MQ dependencies before changing middleware
- Qualify availability during batch processing
- Plan cutover, reconciliation and recovery per flow
Vista
Flow & task management
The human workbench in EVA. Vista presents state, collects input and calls backend contracts; it does not own business or workflow decisions. The Process workspace is still being completed.
- Flow inspection and editing
- Human Task forms and acquisition
- User administration
- Process activity views
- Integrated qualification remains in progress
Aira
Artificial intelligence
Aira is the planned AI layer of EVA, not a shipping agent. It is planned as a local service a person starts, acting with that person's own identity: owning an AI Task, or preparing a draft the person reviews and submits.
- Planned AI Tasks: extract, classify, summarize
- Planned drafts for human review and submission
- Schema checks do not establish factual correctness
- Model choice and integration protocol remain open
- No automatic learning or process optimization today
How you adopt it
Strangler Fig — qualify a slice, then expand
The proposed Strangler Fig path separates modernization into qualified slices. Compare results and operational behavior before expanding. Neither uninterrupted service nor rollback is guaranteed by the pattern alone.
-
01
Wrap
Map Ingenium interfaces and dependencies, then qualify an Orbit integration boundary.
-
02
Redirect
Define which work stays on Ingenium and which may move. Validate routing and authorization before cutover.
-
03
Replace
Implement selected work in services; consider AI only after its role and acceptance criteria are validated. Reconcile against agreed business outcomes.
-
04
Retire
Retire a legacy path only after operational acceptance, data reconciliation and licence review. Recovery options depend on the changes already made.
Benefits
Outcomes to measure, not promises to assume
Set a baseline and acceptance criteria for each pilot. A technical change creates an opportunity; evidence determines whether it delivers value.
Answers: Understand platform commitments
Evaluate the total cost
Compare licences, infrastructure, migration and support costs. Removing a middleware dependency is an integration decision, not an automatic saving.
Answers: Make specialist knowledge accessible
Make routine work repeatable
Use Nexus procedures to reduce reliance on undocumented steps. Specialist review remains essential for business behavior and release decisions.
Answers: Reduce delivery friction
Measure delivery improvements
Evaluate build and operational automation against your current workflow. API integration still requires compatible interfaces and testing.
Answers: Make environment differences visible
Detect drift earlier
Use environment comparisons and repeatable procedures to expose differences. These controls reduce uncertainty; they do not eliminate defects or establish compliance.
Deployment on private infrastructure is a target profile, not a compliance guarantee. Data controls, licensing and operational responsibilities need agreement for each deployment.
Start with a bounded operational problem.
Nexus is the available starting point for Ingenium operations. For EVA and Orbit, discuss a qualification pilot with clear scope and an accountable owner—not a commitment to a production migration.
Email only, no commitment. We will be straight about what works today and what does not.