# Processes no

1 No of Processes in Production
2 No of Processes in UAT
3 No of Processes in Development
# BOTS no
1 No of Bots in Production
2 No of Bots in UAT
3 No of Bots in Development
BOT ID BOT Name (Task/Metabot) BOT Type (Reusable/Reference)

Eg: Name (e.g. SAPLogin.atmx Re-Usable - Bot which can be used as is,
FINBOT001,HRPROC and SAP.mbot) with no or minor changes. ( e.g. Bot
UREBOT001 framework, login to SAP, T-Code FBL1N,
Oracle login screen, etc.)
Reference - Bot which we might not be
using as-is but developers can take
reference of it while developing their use
case. (e.g. Database queries, creating CSV
files, reading XML files, etc.)
BOT Environment Process ID Associated Business Process

DEV / UAT / PROD e.g. CS01 Name the processes it was utilized
/ DECOM for. (e.g. Tax, COTA, etc.. )
Process Phase Description Applications Department

DEV / UAT / PROD / Describe what the bot Target

DECOM does? ( logs in to SAP, applications it
perform download works on
operation for T-Code FB1N, (SAP, Oracle,
etc. ) Framework,
etc)
Criticality of Process Risk Approval Received Business Process Owner

If required (Yes/No) else N/A

SME Key Task / Master Task Task Dependencies Input Dependencies

Can be different than In case of bot that can be Dependent tasks Supporting files
the actual Business reused at a business required to execute needed to run the re-
process owner process level, Master this Bot Successfully usable/reference
Task is the main task OR Other tasks that BOT. ( Config files,
that executes the entire are leveraging this input file, output
process. Bot to complete files)
their process.
Output Consumption Location Repository path where the Configurations (If Any)
BOTs and files are placed
Output information System and CR
(Output file format, information along with
data and information on any
applications) specific runbooks as
required
Volumes Expected Execution Schedule Efforts in Hours PROD date

Expected number Execution Frequency Effort invested in

of transaction (One-Time/Daily/We creation of Re-
volume in the ekly/Annual). Helps usable module.
current process its to avoid overlapping Especially in case
utilized. Usually Bot executions and Re-usable
helps to plan manage dependent module, it can be
capacity and bots' schedule. used to
manage compute measurement the
time. efforts saved.