Hi Michael,
Thank you for your post and for asking about our first automation projects. My first automation project was automating a Citrix-based SAP with Blue prism about six years ago. At the time, automating Citrix environments was a challenging task due to the limitations of the technology available.
The project involved automating several SAP processes that were previously performed manually. This required the development of custom Blue prism objects to interact with the Citrix environment, as well as the creation of custom code modules to handle the SAP transactions. We also spent considerable time on designing the automation flow and selecting the right tools for the job.
In terms of how it went, the project was a success, and the automation significantly reduced the time and effort required to perform the SAP processes. However, we encountered several challenges along the way, such as issues with the Citrix environment and difficulties in developing the custom Blue Prism objects.
The main lesson I learned from this project was the importance of spending more time on design and selecting the right tools. Not every project is suitable for automation, so careful consideration needs to be given to the design and development process. I believe that the design and development time ratio should be 60:40, with 60% of the time spent on design.
For someone crafting their very first automation, my advice would be to approach the project with a clear understanding of the process to be automated, and to carefully consider the design and selection oftools. It's important to have a thorough understanding of the system and its limitations, as well as the requirements and goals of the automation. Additionally, it's important to have a solid understanding of the automation platform being used and to leverage its capabilities to the fullest extent.
In terms of tech advice I would recommend breaking the automation down into smaller, more manageable tasks that can be developed and tested independently. This helps to identify and isolate issues early on and ensures that the automation can be developed in an iterative and agile manner. It's also important to thoroughly test the automation in a controlled environment before deploying it to production.
Overall, automation is a continuous process that requires ongoing maintenance and optimization. It's important to continually evaluate the effectiveness of the automation and make adjustments as needed to ensure that it continues to meet the requirements and goals of the automation program.
I hope this provides some helpful insights.
------------------------------
------------------------------
Vipul Tiwari
Senior Process Simplification Developer
Amazon
------------------------------
------------------------------
Original Message:
Sent: 05-15-2023 15:01
From: Michael Shillingford
Subject: đTeach Michael: My first automation!
Hello innovators đ
OKAY. I'm ready đŞ. You've already taught me what not to automate, how to involve senior leadership in an automation program and how to find processes suitable for automation - but what we haven't tackled yet is where to start?
Everyone here has walked this path already, and so I need your inspiration! My question to you all today is...
What was your very first automation?
I'm hoping to hear from you on:
1ď¸âŁWhat was the first thing you attempted to automate?
2ď¸âŁHow did it go?
3ď¸âŁWhat advice would you give to someone crafting their very first automation?
Now, I have a couple of ulterior motives here. First, we're creating a playbook on automation journeys and we would love your input. And second, our community saw a huge influx of new users during April (hello new friends!) who will also be seeking inspiration. So remember, it may seem like a small question, but the impact of your answer can be huge.
Thank you in advance everyone, and wish me luck!
------------------------------
đ Michael
(I'm part of the SS&C Blue Prism Community Team)
------------------------------