Automatize
Migrations · 04 · Management
← All migrations

Management UI

The migrated system gets what it never had: one screen to manage it.

See what is running. Step in without a developer.

On the old platform, operations were spread across the operator console, the spool and the heads of a few people. Our management UI sits on top of the migrated Java system and brings batch jobs, users and roles, parameters, audit and monitoring together in one web interface.

Start the conversation →See the diagram →

The same night, before and after

Illustration
Fictional example. On the left the overnight run as the operator console shows it, on the right the same jobs in the management UI: status per job, the step that failed and a button to restart from that step.

What you can expect

01
Batch in view
Status, duration and log per job and per step. Restart a failed job from the step that failed.
02
Permissions and audit
Who may do what, and who did what: roles per function and an audit trail on every management action.
03
Parameters without a release
Functional administrators change rates, thresholds and calendars themselves, with a history of every change.

How we do it

01Operations
Scheduling and dependencies
When each job runs and what it waits for, in one overview.
Restart and error handling
The error message, the log and the restart button are in the same place.
02Access
Users and roles
Create users, assign roles and revoke access without a ticket to IT.
Audit trail
Every change with who, when and the value before and after.
03Insight
Monitoring and alerts
An alert when a job fails or runs longer than usual.
Reports and export
Overviews of runs and changes, exportable for review or audit.
■Web interface · role-based access
■Audit trail on every management action
■Restart from the failed step
■Runs alongside the migrated system

Curious what is inside your COBOL?

We start with an inventory.Start the conversation →