Meridian for service providers
Run every client's mainframe from one screen.
Meridian is built for the provider's job: many clients, many LPARs, one operations floor and an SLA on every batch. One install serves every client, each with its own people, roles and rules, and every screen says which client you are looking at.
Per-LPAR pricing with volume discounts. A free 90-day proof of concept on one LPAR.
Example data from a lab estate.
Many clients, one floor
What changes when the floor runs many estates, not one.
A large outsourcer and a mid-size mainframe specialist have the same night: operators across the console, SDSF, the scheduler and the ticket tool, client after client, with SLA credits on the line. Meridian puts that whole job on one screen per client.
One install, every client
One Meridian serves the whole company. Each client's LPARs, people, rules and SLAs are its own, and actions on a client's systems are open to that client's team only.
Rules set client by client
Alert rules, named batches, approval settings and earned autonomy are set per client. A rule for one client never fires for another.
Roles granted per client
Operator, SME, manager and admin, granted per client. A client's own managers can see their reports and audit trail, and no one else's.
Reports per client, by month
Attainment, how many batches ended on time, and prediction accuracy, what Meridian said an hour before and what happened. Per client, every month.
Fits the tools your clients run
CA 7 and ServiceNow today, with CICS, IMS, Db2 and Adabas status on every LPAR. More schedulers and ticket tools are on the roadmap. Tell us what you run.
Trust, one situation at a time
Meridian starts by proposing. Per kind of situation and per client: propose only, do and tell, or do quietly. Approvals and four-eyes for the clients that want them.
SLA prediction, per client
Know which client's batch will be late, hours before it is.
Every named batch says where it stands in words an operator and the client's manager read the same way. When a job fails, the restart card says whether the batch can still end on time.
- 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.
- Alerts on the client's own rules, sent to the channels you choose for that client.
- Late batches show up hours before the deadline, while there is still time to act.
Evidence
Evidence a client can audit.
Every reply, command, scheduler action, flow run and ticket write-back is recorded with what Meridian saw, who confirmed it, the time and the outcome. Searchable, and exportable to the client's ticket.
- One record per action, from the message Meridian saw to the answer that came back.
- A client's managers see their own trail, and no one else's.
- Actions Meridian takes on its own are recorded exactly like clicked ones.
Staffing
A seat watches more LPARs.
With the console, the scheduler, the tickets and the batch line on one screen, a seat can watch more LPARs.
Everything on one screen
Console, WTORs, the scheduler's queues, subsystem status, tickets and the batch line for every LPAR of a client. No hopping between the console, SDSF, the scheduler and the ticket tool.
Only what needs a person
Waiting WTORs, abends, alerts from your rules and batches at risk rise to the top, across the estate. The rest stays quiet.
Routine work, handled
Draw how a routine situation is handled, such as a ticket for any WTOR left waiting. Meridian runs it and shows every run, step by step.
Workflow builderTickets on the same screen
Tickets assigned to operations are read, acted on from a card and written back. Your clients' ticket tool stays the record.
Ticket integrationOnboarding a client
From a new contract to a watched estate, in four steps.
Each new client is set up the same way, with its own team, on the same install.
Add the client
The client is created with its own people and roles. Every screen names the client being shown, so two estates are never confused.
Connect the client's LPARs
Our engineers connect the client's LPARs with the client's own team, with a light footprint on the mainframe. An LPAR shows its console and dashboard the day it is connected.
Connect the scheduler and the ticket tool
The scheduler brings the batch views and the actions; CA 7 today. The ticket tool brings the client's tickets in and takes the results back; ServiceNow today.
Name the batches that matter
An SME defines each batch once: first job, last job, deadline, what must be up, the breach procedure and who to tell. Predictions firm up over a few weeks of the client's own job history; until then Meridian says it is not sure.
Many clients, many regions
India, the UAE and Latin America.
Hexabin Infotech designs, builds and supports its products from Chennai, for companies in three regions. Meridian is installed in each provider's own network, so every client's data stays where it is.
-
India Base
Made in Chennai: the team that designs, builds and supports Meridian works here.
13.08° N · 80.27° E · Chennai
-
United Arab Emirates
Software and automation for companies across the Emirates.
24.47° N · 54.37° E
-
Latin America
Software and automation for companies across the region.
Region · 14.20° S · 51.90° W
Pricing for providers
Per LPAR, with volume built in.
List prices in US dollars per LPAR per month, billed yearly, plus one company fee. There is no per-user charge, so every operator, SME and manager in the company can use it.
Watch
Seeing everything
$150 per LPAR per month billed yearly, $1,800 per LPAR per year
- Dashboards, console, batch views
- Health, capacity, alerts you set
Act
Doing everything
$500 per LPAR per month billed yearly, $6,000 per LPAR per year
- Everything in Watch
- WTOR replies and console commands
- Scheduler actions from cards
- SLA prediction and reports
- Builder flows
- Ticket tool integration
- Earned autonomy
Company
Every company, once
$40,000 per year never discounted; it pays for your support
- The install, with your team, in your network
- Support and upgrades
- No per-user fees, for every operator, SME and manager
- 10% off per-LPAR prices from 50 LPARs
- 20% off per-LPAR prices from 150 LPARs
- 30% off per-LPAR prices from 300 LPARs
- 90 days free proof of concept on one LPAR
Questions
Questions providers ask.
The ones service managers and operations leads ask first. Or write to hello@hexab.in.
Meridian for enterprisesCan different clients have different rules?
Yes. Alert rules, named batches, approval settings, earned autonomy and the people who may act are all set per client. A rule for one client never fires for another.
Can a client see its own estate?
Yes. Four roles, operator, SME, manager and admin, are granted per client, so a client's own managers can be given their reports and their audit trail without seeing anyone else's.
Where does the client's data go?
Nowhere outside your network. Meridian runs inside your network, and every client's data stays there. Nothing is sent to Hexabin, and Hexabin does not host your data. Inside Meridian, a client's estate is shown only to the people who hold a role on that client.
What if the client runs a scheduler you do not support yet?
Watch works without a scheduler connection: the console, the dashboard, health and capacity, and the alerts you set. The batch views, scheduler actions and SLA prediction need the connection. CA 7 is supported today; others are on the roadmap. Tell us what you run.
How do we start without risk?
A ninety-day proof of concept on one LPAR, free, with our engineers on the call. Then a twelve-month contract. After ninety days you decide on your own results.
See it on one of your estates.
Forty-five minutes on a call. We show Meridian on a live lab estate, then talk about yours: how many clients and LPARs, which schedulers, which ticket tools, where the pain is. No slides.
Or write to hello@hexab.in.