ApplicationFINANCE_CORE
Control-M operations platform
Inventory first. Instructions where incidents happen.
Batch Tools turns Control-M definitions, execution files, operational rules, and team ownership into one compact customer portal.
Start component
Inventory shows the real Control-M hierarchy.
Applications, sub-applications, folders, jobs, parsers, and templates stay visible as operational objects, not imported files hidden in a raw table.
Selected object
JOB PAY_RECON_LOAD
- Parser
- Control-M Automation JSON Jobs
- Source
- Automation API
- Team
- Payments Batch
- Coverage
- Instruction rule applied from folder
Incident flow
When a job is Not OK, the portal explains what to do next.
Execution Not OK
Latest execution flags failed status, runtime, return code, and affected folder.
Inventory Context
The job card exposes app, subapp, folder, dependencies, and historical volume.
Instruction Rule
Effective rule is resolved by priority and scope: job, folder, subapp, then app.
Action Template
Rerun, hold, confirm, kill, set as OK, and escalation notes are shown as explicit actions.
On-call Team
The incident points to the owning team and assignment target for ticket routing.
Demo failure
PAY_RECON_LOAD failed after source timeout
Effective instruction: rerun once after upstream file check. If second failure occurs, hold downstream settlement folder and assign ticket to Payments Batch.
Rerun: Yes
Confirm required
Kill: Only if hung
On-call: Payments Batch
Component model
Install only what the customer needs.
Authentication, public/private portal, admin shell, settings, component registry.
Control-M job definitions from Automation API JSON/XML and file imports.
Prioritized operational rules with preview, coverage, and visible effective action.
Ownership, on-call routing, ticket assignment metadata, and escalation groups.
CSV execution imports and run-status analytics.
Optional expansion components that plug into the same portal model.