The Nexus toolset has been used on a real Ingenium system. The integrated work-management experience is being developed further.

Discuss your needs
← Back to BENOVA

Built for everyday Ingenium work

Less repetitive work. More time for business value.

Nexus helps developers and operations teams simplify familiar tasks: compiling COBOL, preparing environments, managing databases and moving policies for investigation. Work more conveniently inside VS Code.

Explore supported needs See what is available
Intended experience · illustration

› An Ingenium change request

  1. 01 understand the work scope
  2. 02 prepare the build
  3. 03 check in the DEV environment
  4. 04 ready for team review

Less manual effort · More practical handovers

Key features

Specialized tools for work you do often.

Instead of assembling manual steps, give the team a toolset suited to Ingenium.

Prepare data and environments

Database · Policy

Support backup, restore, database refresh and policy transfers between environments approved for use.

  • Prepare test environments more conveniently
  • Reduce repetitive tasks
  • Support investigation and debugging

Shorten COBOL development cycles

Build · Runtime

Incremental and parallel compilation focuses on changed work, with tools to manage Ingenium region activity.

  • Get build feedback sooner
  • Fewer steps when checking changes
  • Focus time on business behavior

Make change management more practical

Source · Work item

Put source operations in Ingenium work context so teams understand which changes belong in a build.

  • Connect changes with the current work
  • Reduce error-prone manual steps
  • Review handover scope more easily

Work in familiar tools

VS Code

Basic VS Code integration and environment-based configuration help developers switch between fewer places during everyday work.

  • A familiar entry point
  • Distinguish environment context
  • More practical daily use

Practical applications

From individual features to useful work.

The existing toolset supports the needs below. End-to-end work management is in development and needs qualification for each environment.

01

Prepare a change

Reduce effort between making a change and being ready to check it.

  1. 01Understand the change scope
  2. 02Prepare a build for evaluation
  3. 03Make results easier to hand over

Developers spend more time on change quality instead of repetitive operational steps.

02

Refresh a test environment

Prepare a suitable environment so the team can start work.

  1. 01Identify the environment needed
  2. 02Prepare data approved for use
  3. 03Assess status before handover

Reduce preparation time and give teams more control of their test plans.

03

Reproduce an issue for support

Bring the policy under investigation to a suitable environment.

  1. 01Identify the case to reproduce
  2. 02Prepare the policy within approved scope
  3. 03Help developers investigate the cause

Support and development teams have a more practical basis for resolving incidents together.

Access rights, permitted data use and human confirmation steps need agreement before adoption.

Value for your team

Less manual effort for every role.

Nexus focuses on the effectiveness of the people developing, operating and supporting Ingenium.

Earlier feedback

Development teams

Spend less time preparing builds and environments, and more on the change that matters.

More consistency

Operations teams

Use specialized tools for common operations in Ingenium environments.

Better collaboration

Support teams

Prepare reproducible cases to make discussions with developers more productive.

Decisions under your control

The responsible owner

Set scope, usage rights and review steps before consequential changes.

Experience in development

Toward fewer tool switches and clearer work.

Building on the existing VS Code extension, the next direction brings work and progress closer to developers. The capabilities below are not a released integrated experience.

Prepare a build Prepare a debug policy Refresh DEV Collect check results
Planned experience inside VS Code
  • Start common workAims to make suitable work selectable inside the IDE.
  • Keep working contextAims to reduce repeated entry of information about current work.
  • See when review is neededAims to make developer participation points visible.
  • Follow progressAims to reduce switching between places to find status.

Available and next

Practical experience is the starting point.

Distinguish the toolset already in use from the integrated experience still being refined.

AVAILABLE

The Ingenium toolset

  • Database, policy and Ingenium operations tools
  • COBOL build and source management support
  • Basic VS Code extension
  • Used on a real Ingenium system

IN DEVELOPMENT

A connected working experience

  • Combine tools into work journeys
  • Centralized processing status
  • Connect with the EVA experience
  • Bring human-review work into VS Code

Scope and readiness for each integration will be confirmed during evaluation. A complete end-to-end journey is not assumed.

Which Ingenium task do you repeat too often?

Share work that takes too much team time: builds, environment refresh or policy preparation for debugging. Find a practical starting point with Nexus.

Discuss Nexus View BENOVA