{"description":"Runs on the existing system item. Review scheduled job execution for a system over a period, evidencing failure detection, escalation, and resolution. Deliver the reviewed result and open actions to the responsible register owner and the named companion procedure.","edges":[],"isPublic":true,"itemTypeSlug":"system","metadata":{"capabilities":["job-scheduling-batch-monitoring"],"controlVerbs":{"UC-ACCESS-17":"operates"},"controls":["UC-ACCESS-17"],"department":"it","domains":["controls"],"kind":"job-scheduling-batch-monitoring","library":{"aliases":[{"source":"studio-seed","sourceTemplateId":"coworkcanvas:template:job-scheduling-batch-monitoring"}],"canonicalUrl":"https://workflow-library.com/all/?w=controls-system-batch-processing-review","contentDigest":"sha256:bedd1ab9491ab9bc1750397e6669e1d8de35062dce88fbe992cde579fdd4363b","prerequisites":{"anchorItemType":{"slug":"system"},"evidenceDestinations":[{"description":"Restricted native step results, attached documents, durable item fields and native approvals.","id":"review-evidence"}],"handoffs":[{"direction":"output","name":"Reviewed register result and open actions","sourceTemplateId":"workflow-library:sox-production-operations-processing-integrity-cycle"}],"roles":[{"contribution":"approval","description":"System owner and technical specialist. Approve batch monitoring record.","id":"reviewer-1","nodeIds":["batch-closure"]}],"status":"declared"},"provenance":[{"source":"brain/scripts/studio-seed","sourceTemplateId":"coworkcanvas:template:job-scheduling-batch-monitoring"}],"releaseId":"sha256:bedd1ab9491ab9bc1750397e6669e1d8de35062dce88fbe992cde579fdd4363b","schemaVersion":1,"sourceTemplateId":"workflow-library:controls-system-batch-processing-review"},"lineOfDefense":"operate","mappingStatus":"mapped","risks":[],"slug":"controls-system-batch-processing-review","source":"coworkcanvas-gallery","standards":[],"teams":["it"]},"name":"Job Scheduling & Batch Monitoring","nodes":[{"data":{"controls":["UC-ACCESS-17"],"instructions":"**Objective**\nApprove batch monitoring record. The reviewer decides from the complete package described below.\n\n**Inputs**\n1. Review the System item, the job scheduler configuration and calendar, the critical job inventory and its basis, alerting and notification configuration, and the on-call or operations rota.\n2. Use scheduler execution logs for the full period, alert and incident records, rerun and manual intervention logs, downstream data completeness checks, and the prior period failure profile.\n3. Use the failure inventory, alert delivery evidence, incident tickets with timestamps, resolution notes, downstream reconciliation after rerun, and the response targets in policy.\n4. Review all stage records, the critical job basis, expected-versus-actual reconciliation, failure inventory, timing measurements, downstream verification, and open items with owners.\n\n**Procedure**\n1. Confirm the critical job list is derived from downstream financial and operational dependency rather than convention, verify alerting is configured for each critical job, and identify jobs whose failure would be silent.\n2. Inspect the log for the WHOLE period rather than sampling a date, reconcile expected against actual executions to find jobs that never ran, distinguish reruns that succeeded from those that masked a data gap, and record log gaps as gaps.\n3. Measure detection-to-escalation and escalation-to-resolution against the policy targets per failure, confirm downstream data was reconciled after each rerun, and treat failures closed without data verification as unresolved.\n4. Trace the result to per-failure timing evidence, verify jobs with no alerting carry a remediation owner, confirm downstream reconciliation for every rerun, and return status-only resolutions with precise comments.\n\n**Record in AssureSwarm**\n1. Capture the monitoring period, critical job population with dependency rationale, detection and alerting configuration per job, accountable responders, jobs with no alerting, and scope exclusions. Also record critical job population and detection basis.\n2. Document the failure inventory with timestamps and job identity, jobs that never executed, reruns and manual interventions, downstream impact observed, resolution status per failure, and log coverage gaps.\n3. Record the monitoring result, per-failure timing against targets, alerts that did not reach a responder, downstream reconciliation evidence, failures closed without data verification, and recurring failure patterns. Also record escalation and resolution detail.\n4. Capture the authorized reviewer, the summary, accepted result, period covered, unresolved failures and data impact with owners and dates, alerting gaps, and linked issues raised. Also record batch monitoring summary.\n\n**Exit criteria**\nSystem owner and technical specialist provides approval: Criticality is justified by downstream dependency, alerting coverage is evidenced per job, and silently-failing jobs are surfaced rather than assumed healthy. The review covers the whole period, missing executions are found by expected-versus-actual reconciliation, and log gaps are declared rather than read as clean periods. An approver accepts that timing is measured per failure against policy targets, downstream data impact is verified rather than assumed, and recurring patterns are surfaced. The authorized reviewer accepts the record as evidence the monitoring control operated for the period, and closure implies no assurance over jobs excluded from the critical population.","kind":"task","label":"Approve batch monitoring record","requiredApprovals":1},"id":"batch-closure"}],"sourceTemplateId":"workflow-library:controls-system-batch-processing-review"}