Meridian for enterprises
Your own z/OS estate, on one screen.
Meridian puts the console, the batch, the scheduler and the tickets for every LPAR on one screen, says hours ahead when a batch will miss its deadline, and keeps every action with its evidence. It runs inside your network, and your data never leaves it.
A free 90-day proof of concept on one LPAR, with our engineers on the call.
Example data from a lab estate.
For an in-house operations team
What changes for the night shift.
An enterprise operations team carries the business's batch every night: settlement, billing, payroll, the files the rest of the company waits for in the morning. Meridian gives that team one screen and an early warning.
One screen for the whole job
Console, WTORs, the scheduler's queues, subsystem status and the ticket queue for every LPAR, with what needs a person at the top and the rest quiet.
Batch deadlines, seen early
Every named batch in plain words, from On time to SLA breach incoming, with the job that decides it. Hours before the deadline, not after it.
A record your auditors can read
Every reply, command, scheduler action, flow run and ticket write-back, recorded with what Meridian saw, who confirmed it, the time and the outcome.
Your data stays in your network
Meridian runs inside your network, on premises or in your private cloud. Nothing is sent to Hexabin, and Hexabin does not host your data.
Fits what you already run
CA 7 and ServiceNow today, with CICS, IMS, Db2 and Adabas status on every LPAR. Your scheduler stays the scheduler; your ticket tool stays the record.
Trust earned, one situation at a time
Meridian starts by proposing. Per kind of situation: propose only, do and tell, or do quietly, and back down any time. Approvals and four-eyes where your rules require them.
Batch deadlines
Know hours early when a batch will miss its deadline.
Meridian follows every named batch through the night and says where it stands in words your operators and your managers read the same way, with the job that decides the end.
- Four plain phrases: On time; On time, but tight; Slightly delayed, within the approved time; SLA breach incoming.
- The job that decides the batch's end, always named.
- When a job fails, the restart card says whether the batch can still make it, and by how much.
- Attainment and prediction accuracy reported every month.
Operations console
The console, the scheduler and the tickets in one place.
Operators work the console, answer WTORs and confirm scheduler actions from cards, with the batch line always in view. What needs a person rises to the top; routine lines fold away.
- WTORs at the top, with the proposed reply on the line and the reason for it.
- Every scheduler action from a card that shows the command exactly as it will be sent.
- Tickets assigned to operations are read, acted on and written back; your ticket tool stays the record.
Audit evidence
A record your auditors can read, for every action.
Each record holds what Meridian saw, what it proposed and why, who confirmed it, the command exactly as sent and the answer that came back. Searchable, and exportable.
- One record per action, from the message Meridian saw to the answer that came back.
- Actions Meridian takes on its own are recorded exactly like clicked ones.
- Every night's records in one place, ready to export when the auditor asks.
Data and security
Your data stays in your network.
Meridian is installed with your team, inside your network. Hexabin does not host your data, and nothing is sent to us.
- Where Meridian runs
- Inside your network, on premises or in your private cloud, installed by our engineers together with your team.
- What reaches Hexabin
- Nothing. Your data never leaves your network.
- What reaches the mainframe
- Only what a person confirmed on a card, or a flow you approved. Each one is recorded with who, when, what and the reply that came back.
- The footprint
- A light footprint on the mainframe, set up with your systems team when the first LPAR is connected.
- Who can do what
- Four roles: operator, SME, manager and admin. Approvals and four-eyes can be switched on where your rules require them.
- Releases
- Checked before they go live, and they can be rolled back.
A security review is welcome.
Send your questionnaire to hello@hexab.in and we will answer it. The security page covers where your data stays, roles and the audit trail.
Who uses it
Four roles, one install.
There is no per-user charge, so everyone who touches operations can use it.
Operators
Work the console, answer WTORs and confirm actions from cards, with the batch line always in view.
SMEs
Define the named batches, their deadlines, conditions and breach procedures, and draw the flows that handle routine situations.
Managers
Approve batch definitions, choose how much Meridian may do on its own, and read attainment and prediction accuracy by month.
Admins
Grant roles, connect the scheduler and the ticket tool, and decide who may act. Meridian warns them when an LPAR stops reporting.
Getting started
Start on one LPAR, free.
A ninety-day proof of concept on one LPAR, with our engineers on the call. Then a twelve-month contract, priced per LPAR per month with a yearly company fee and no per-user charge.
A first call
Forty-five minutes: Meridian on a live lab estate, then yours. Which LPARs, which scheduler, which ticket tool, and where the pain is.
Installed with your team
Our engineers install Meridian inside your network with your team and connect one LPAR. Its console and dashboard show the same day.
Batches named and learned
Connect the scheduler for the batch views and name the batches that matter. Confident predictions follow after a few weeks of job history.
Your decision
At the end of the ninety days you decide on your own results. If Meridian stays, a twelve-month contract follows.
Questions
Questions enterprises ask.
The ones a security review and an operations manager ask first. Or write to hello@hexab.in.
Meridian for service providersDoes any of our data leave our network?
No. Meridian runs inside your network, and everything it reads from your estate stays there. Nothing is sent to Hexabin, and Hexabin does not host your data.
Does Meridian replace our scheduler or our automation product?
No. The scheduler stays the scheduler; Meridian reads it and drives it from cards. Console automation keeps doing the deep recovery it is good at, while your operators get one screen. Your ticket tool stays the system of record.
Can we send you a security questionnaire?
Yes. Send it to hello@hexab.in and we will answer it. The security page sets out where your data stays, who can do what, approvals and four-eyes, and what the audit trail records.
How long until we see something?
An LPAR shows its console and dashboard the day it is connected. The batch views follow once the scheduler is connected. Confident SLA predictions need a few weeks of job history; until then Meridian says it is not sure, in those words.
We use a service provider for some LPARs. Does that matter?
No. Meridian can run in your network for your own team, and a provider can run its own Meridian for the estates it operates. Roles are granted per client, so your managers can be given their own reports and audit trail.
How is it priced?
Per LPAR per month, billed yearly: Watch at $150, Act at $500, plus a yearly company fee of $40,000 that covers the install, support and upgrades. No per-user charge. Volume discounts from 50, 150 and 300 LPARs.
See it on your own estate.
A ninety-day proof of concept on one LPAR, free, with our engineers on the call. After ninety days you decide on your own results.
Or write to hello@hexab.in.