4.2.1 Identifying routine/as-needed tasks
Identify and organize IT operations and other necessary tasks to be performed in Ops I.
For routine tasks, identify whether they will be performed on a regular or irregular basis and whether they are associated with workflows. For as-needed tasks, identify necessary tasks as a service catalog, and then identify patterns of agents and workflows for each task.
The following shows examples of routine and as-needed tasks.
(Table) Examples of routine/as-needed tasks
| Task type | Frequency | Description | Task | Worker |
|---|---|---|---|---|
| Routine task | Daily/Weekly | Confirms backup of the system and data areas | Makes notification of backup | (Automatic notification) |
| Executes backup | (Automatic execution) | |||
| Confirms backup | Operations agent | |||
| Completes (approves/makes notification) | Operation manager | |||
| Monthly | Scheduled reboot (OS) | Makes notification of scheduled reboot | (Automatic notification) | |
| Executes scheduled reboot | Operations agent | |||
| Confirms scheduled reboot | Operations agent | |||
| Completes (approves/makes notification) | Operation manager | |||
| As-needed task | As-needed | VM lending | Makes a request | Requester |
| Reviews the request | Operations agent | |||
| Creates a VM | (Automatic execution) | |||
| Confirms creation of VM | Operations agent | |||
| Completes (approves/makes notification) | Operation manager | |||
| As-needed | Registers, reruns, and cancels plan execution, etc. | Makes a request | Requester | |
| Performs the requested task | Operations agent | |||
| Completes (approves/makes notification) | Operation manager |