Control-M, AutoSys, Tidal, IBM Workload Scheduler and plain cron run thousands of jobs in most estates, and many of those jobs are data jobs: extracts, loads, file transfers, scripts that stitch them together. The scheduler sees a job succeed or fail; it does not see the rows. This path keeps the scheduler for what it does well and moves the data jobs into Lima pipelines, which the scheduler triggers and hears back from. Each job gains checks, exception owners, a run window with a deadline and a reconciliation report. Estates on Airflow 2, which reached end of life on April 22, 2026 [6], take the same path onto Airflow 3.
These schedulers are current products with recent releases [3][5]. The reason to move data jobs is what a scheduler cannot see: the rows. A job that finishes on time with 3 rejected purchase-order lines looks green to the scheduler. In Lima those 3 lines are exception records with owners, the totals reconcile, and the report says so.
| Scheduler | Status on the check date | Source |
|---|---|---|
| BMC Control-M | Current; Control-M SaaS and on-premise; Control-M for SAP certified; SLA Management add-on for deadline chains. | [1][2] |
| Broadcom AutoSys Workload Automation | Current; release 24.2 on April 14, 2026. | [3] |
| Tidal Automation (Redwood) | Current; sold by Redwood since its 2023 acquisition of Tidal Software. | [4] |
| IBM Workload Scheduler | Current; release 10.2.7 on April 24, 2026. | [5] |
| Apache Airflow 2 | End of life on April 22, 2026; Airflow 3 is current. | [6] |
| cron | Everywhere, forever, and blind to rows. | — |
The conversion is a mapping, and the mapping is short. What has no equivalent is listed too.
| Today | In Lima | What to know |
|---|---|---|
| A data job (extract, load, transfer, script) | A Lima pipeline | Same sources and targets, plus checks, exception owners and a report. |
| Job dependency or condition | Dependency trigger | A pipeline starts when the ones it depends on finish; the scheduler's condition can remain as the outer trigger. |
| Calendar | Business calendar | Working days, cut-offs and run windows with deadlines. |
| SLA chain (Control-M SLA Management) | Run window with a deadline clock inside the job | The chain says whether the job finished by the deadline; Lima says what happened inside, and pauses the clock when a check trips. |
| File watcher | Event trigger | Arrival of a file on SFTP or object storage starts the pipeline. |
| Alert to an operator | Exception routed to its owner | A bad row goes to the buyer or planner who owns it, with a deadline; an operational failure still alerts operations. |
| Return code | Status back to the scheduler | Lima reports success, held (paused on a check) or failed, with the report link. |
| Retry | Resume from checkpoint | The run continues from where it stopped and replays in order; nothing is applied twice. |
The assessment reads exported job definitions (JIL for AutoSys, XML for Control-M, exports for Tidal and IWS, crontabs) and needs no access to production data.
| What it reads | What it reports |
|---|---|
| Job definitions | Which jobs are data jobs, by type: extract, load, transfer, script. |
| Dependencies and calendars | The chains the data jobs sit in and the deadlines implied. |
| Scripts | Shell, SQL and Python by size, with the conversion effort. |
| Effort bands | Per batch of ten to twenty jobs. |
One week. You send the exported job definitions; we return the data-job list, the chains and the effort bands. No charge.
Get the assessment →Fixed priceThe first ten to twenty data jobs rebuilt as pipelines, triggered from your scheduler, run side by side, reconciled and cut over on a fixed price.
Offers and principles →The scheduler stays. Its operators see the same chains and the same green and red; Lima adds a status of 'held' when a check trips, with the report link.
SAP batch jobs stay in Control-M for SAP or its equivalent; Lima's SAP work is data extraction and write-back through released interfaces, which is a different job.
For what the scheduler cannot see: rows, totals, exceptions and who owns them. The job looks the same to operations; the data team gets the report.
No. The scheduler still starts the job and receives success, held or failed, with a link to Lima's report.
Yes. Airflow 2 reached end of life on April 22, 2026 [6]. The DAGs move to Airflow 3 with Lima tasks inside them, following the same five steps.
One week, no charge. You get the count by pattern, the exposure flags and the effort bands, whatever you decide next.