What OpCon Continuum can automate
Banks and credit unions run on a web of systems (the core banking platform, databases, file exchanges with partners, and homegrown scripts) that all have to run in the right order, at the right time, every day. OpCon Continuum automates that work end to end, and coordinates how those systems talk to one another.
The part that matters most for adoption is connectors: the building blocks that let OpCon Continuum work with the systems you already have, instead of replacing them.
The daily work that keeps a bank or credit union running depends on many systems running in the right order, on time, every day. Done by hand it's slow, fragile, and hard to scale, and a single missed or mistimed step can delay the whole day's processing.
What a connector lets OpCon Continuum do
Each connector adds a kind of work a workflow can perform. Today these include:
- Wait for data to arrive before processing it: for example, hold a workflow until the nightly core export file has fully landed, so nothing runs against half-written data.
- Run programs and scripts on your servers: the utilities and batch jobs you already rely on.
- Work with your databases on your existing SQL LSAM machines: run a SQL Server script, start a SQL Server Agent job, run an SSIS package, run an Oracle SQL*Plus script or a MySQL script, or run SQL through an ODBC driver or OLE DB provider, as a step in a larger flow.
- Reuse legacy automation: drive your existing UNIX/Linux, Windows, IBM i, SQL, SAP R/3 and CRM, SAP BW, z/OS, Unisys MCP and Unisys OS 2200 LSAM machines — including starting the SAP background jobs and SAP BW process chains you already have, submitting your z/OS JCL, starting your z/OS started tasks, running your REXX execs, issuing console commands and bringing the z/OS jobs your agent tracks or queues onto their schedule, running your MCP programs, WFL jobs and EAE/AB Suite reports and copying, renaming and removing MCP files, and starting your OS 2200 runstreams — without rebuilding them, so you can adopt OpCon Continuum gradually.
- Move files between your systems: transfer a file between two of your existing LSAM machines, or between two endpoints on an OpCon MFT agent, with optional compression, PGP encryption and renaming along the way.
- Reach the services you already run: start Robot, Web Macro and Scan Document tasks on your OpCon RPA agents, and add your EASE (Episys As A Service) jobs to today's schedule on Jack Henry's EASE OpCon, waiting for each to finish.
- Compose reusable workflows: build a standard sequence once and reuse it across processes.
Why it matters
- Reliability for mission-critical processing. Steps run in the right order and only when their data is ready, which reduces missed windows and manual intervention.
- Use what you already own. Connectors meet your systems where they are, including legacy agents and core systems, protecting existing investments.
- A clear audit trail. Every run is recorded, which is useful when examiners or auditors ask what ran, when, and whether it succeeded.
- Faster to adopt. Built-in connectors need no setup, and existing automation can be brought in as-is.
Who does what
- Administrators set up the environment and the connections to your systems.
- Builders design the workflows and choose the connectors for each step.
- Operators watch the daily run and respond if something needs attention.
As a sponsor, you don't configure any of this, but knowing what OpCon Continuum can connect helps you speak to its value and spot where it can remove manual work in your organization.
Related topics