Getting started with OpCon Continuum
OpCon Continuum automates the work your organization runs every day, and coordinates how your systems, including your mainframe core, work together. Instead of people running steps by hand and watching for the next one, you build the process once and let it run reliably, in the right order, at the right time.
This page orients you: who does what, what the main pieces are, and where to begin.
Most of what you already know carries over; the names changed more than the ideas did. Start with the transitioning guide to translate a term, then come back here.
Running daily operations by hand (people kicking off steps, watching for the next one, reacting to failures in the middle of the night) is slow, error-prone, and doesn't scale as the business grows.
Who uses it
OpCon Continuum is built around four roles. You don't need all of them: many teams wear several hats.
| Role | Focus |
|---|---|
| Builder | Designs the automation: workflows, the jobs in them, and what each job does. |
| Operator | Watches the daily run and steps in when a job needs attention. |
| Administrator | Sets up and maintains the environment, agents, and connections. |
| Business User | Understands the value and capabilities; may run published requests via self-service. |
When you sign in, you land on a dashboard for your role: an Administrator sees environment and agent health, an Operator sees the day's run and any failures, a business user sees the requests they can run.
The main pieces
- Workflows: the automated processes: a set of jobs that run in order, on a schedule.
- Connectors: what a job actually does: run a command or script, wait for a file, run a database operation, or drive a legacy system. Connectors are how OpCon Continuum works with the systems you already have.
- The daily run: Operators monitor workflows as they run and respond to anything that fails.
- Toolkit: reusable building blocks Builders share across workflows: schedules (frequencies), holiday calendars, limits (thresholds and resources), values (properties), and tags.
- Service requests & self-service: forms that let business users safely trigger automation without touching the workflows.
- Agents & connections: where jobs run, and the secured links to your external systems.
- Reports, event log, and search: visibility into what ran and what happened.
Where to begin
Get the vocabulary
A handful of terms — workflow, job, job type, agent, frequency — carry most of the meaning. Skim them once and everything else reads faster.
Follow the reading order for your role
Each role has a path through its own pages, grouped into modules that build on each other, so you aren't deciding what to read next. The table above says which role fits you.
See a complete scenario end to end
Automation outcomes thread the individual features into something you'd actually deliver — a nightly core export, a partner file exchange — so you can see how the pieces fit before building.
Look things up as you go
Reference covers every setting, status value, and failure. Browse all pages filters the whole corpus by type, audience, and area for when you don't know which page you want.