How an engagement runs
From a first call to production.
Five steps, each with a clear end. You see Meridian, Hexabin Infotech's product for mainframe operations, on a lab estate first, then on one of your own LPARs for ninety days, free, with our engineers on the call. Production follows only if it fits.
Your data stays in your network at every step.
Five steps
Each step ends with something you can check.
You decide at the end of each step whether to take the next one. Nothing is installed before the proof of concept, and nothing is paid for before production.
Step 1 · Demo
A 45-minute demo on a lab estate.
We show Meridian on a live lab estate, then talk about yours: how many LPARs, which scheduler, which ticket tool, where the pain is. No slides.
- Every LPAR on one screen, with its WTORs, abends and subsystems, and each batch's SLA in words.
- An action proposed, confirmed and recorded, from the console line to the scheduler's answer.
- A reply to your request within one working day, from a person.
Step 2 · Scoping
A scoping call to plan the proof of concept.
One call with the people who run your estate. We agree what the proof of concept covers, so it starts on a known LPAR, with known people, on known dates.
If you run a scheduler or a ticket tool other than CA 7 and ServiceNow, this is where we say plainly what Meridian can do with it today.
On the call we agree
Your estate
- Your clients and their LPARs
- Your scheduler, CA 7 today
- Your ticket tool, ServiceNow today
The proof of concept
- The one LPAR it runs on
- The batches that matter most
- The people and the dates
Step 3 · Proof of concept
Ninety days on one of your LPARs, free.
Our engineers install Meridian with your team, inside your network, and are on the call throughout. Your data never leaves your network.
- The LPAR's console and dashboard show the day it is connected.
- Batch views follow once the scheduler is connected, and tickets once the ticket tool is.
- Meridian proposes and your operators confirm. Every action is recorded with its evidence.
- A light footprint on the mainframe, under IDs you own.
Step 4 · Named batches
Your batches, named and learning.
An SME defines each batch that matters once: first job, last job, deadline, what must be up, the breach procedure, who to tell. A manager approves it.
- Meridian derives the chain from your scheduler's own definitions.
- It learns each job's usual run time from your own history, by weekday.
- Confident predictions need a few weeks of history. Until then Meridian says it is not sure, in those words.
Step 5 · Production
Production, under a twelve-month contract.
If Meridian fits, it goes into production on the LPARs you choose, priced per LPAR and never per user, so every operator, SME and manager can use it.
- Watch to see everything, Act to do everything. Move an LPAR from Watch to Act at any time.
- One yearly company fee covers the install, support and upgrades.
- Volume discounts at 50, 150 and 300 LPARs, applied automatically.
List prices, billed yearly
- $150 Watch, per LPAR per month
- $500 Act, per LPAR per month
- $40,000 Company fee per year, for the install, support and upgrades
- 30% Off per-LPAR prices from 300 LPARs. 10% from 50, 20% from 150.
In US dollars. No per-user fees. Test LPARs count the same as production.
In production
What you can expect.
What stays true after the proof of concept, for every LPAR and every client.
Support from our engineers
Part of the yearly company fee, for every LPAR you run.
Upgrades you can check
Releases are checked before they go live and can be rolled back. Our engineers upgrade Meridian with your team.
Your data stays in your network
Meridian runs inside it and sends nothing to Hexabin. Hexabin does not host your data.
Every action on record
Who confirmed what and when, what Meridian saw and what came back, exportable for clients and auditors.
Autonomy you grant
Meridian proposes first. Per situation and per client you choose propose only, do and tell, or do quietly, and move it back any time.
A monthly account
Batch attainment and prediction accuracy, per client, every month.
From your side
What we need from you.
Our engineers do the installing, with your team. From your side it takes a few people, the usual approvals and two accounts.
- A project contact
- One person who books the calls, brings in the right people and decides at the end of the proof of concept whether to go on.
- Access approvals
- The approvals your security and change teams give for a new tool on one LPAR. Meridian works under IDs you own, with the access you grant and nothing more.
- A scheduler account
- An account in your scheduler, CA 7 today, for the batch views, with the right to act if you want Meridian's scheduler actions.
- A ticket tool account
- An account in your ticket tool, ServiceNow today, so that tickets assigned to operations are read, acted on and written back.
- An SME and a manager
- An SME to name the batches that matter, and a manager to approve them, with our engineers on the call.
Another scheduler or ticket tool? Tell us on the scoping call. Others are on the roadmap. Tell us what you run.
Questions
Questions about how it works.
Short answers to what operations and security teams ask first. For anything else, write to hello@hexab.in.
Security at MeridianWhat does the proof of concept cost?
Nothing. Ninety days on one LPAR, free, with our engineers on the call. If Meridian fits, production follows under a twelve-month contract, priced per LPAR.
How soon do we see something?
The LPAR's console and dashboard show the day it is connected. 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.
What runs on the mainframe?
Very little: a light footprint, installed with your team under IDs you own, with the access your security team approves. Our engineers go through it with your systems programmers before anything is installed.
What leaves the mainframe, and where does it go?
Only what Meridian needs to watch your estate, and it goes no further than your own network. Nothing is sent to Hexabin.
What goes back to 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.
Where does Meridian run?
Inside your network, on premises or in your private cloud, installed with your team. One install serves your whole company, every client and every LPAR. Hexabin does not host your data.
Does Meridian use mainframe CPU?
Very little. Meridian has a light footprint on the mainframe. In the proof of concept you can measure it on your own LPAR, with your own tools.
How is Meridian upgraded?
Our engineers upgrade it with your team, inside your network. Releases are checked before they go live and can be rolled back, and you see every step. Upgrades are part of the yearly company fee.
Start with a 45-minute demo.
Meridian on a live lab estate, then a conversation about yours. A person replies within one working day.