WHAT IS "as-is" and "to-be" in project pls

Could you please explain the “as-is” and “to-be” process in creating the automation project.

Thanks in advance!

Hi @Kalaisri_K !

:sunflower: As-is refers to what currently the human operator is doing, step by step, screen by screen. Usually it’s the business analyst and the human operator that fill in and validate this part.

:sunflower: To-be refers to the process to be automated; the solution architect or developer or a technical business analyst can fill in this part.

:question: Why would there be a difference between as-is and to be ?
The robot has some facilities, and do not need to do exactly the same steps as a human being.
→ the human being needs to open “Outlook”, then click “New Mail”, then write the mail, chose the senders
→ the bot does not need to do all these human being steps, he only needs to know who to send and if attached files are necessary.

But sometimes, the as-is and to-be are the same.
And sometimes there is no as-is, because it’s a new process, and thus no human being was doing it before.

Let us know if it’s still unclear ! :smile:


perfect example and explanation

1 Like

Your response made my day! I was struggling to know these 2 terms for a long time.

1 Like

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.