Comments for IT Process Automation Blog http://runbook-automation.com IT process automation made easy! Sun, 04 Mar 2012 14:12:08 +0000 hourly 1 http://wordpress.org/?v=3.3.1 Comment on Ayehu eyeShare Cuts Critical Incident Recovery Time by 90% at a Leading Financial Organization by Gregory Weingard http://runbook-automation.com/ayehu-eyeshare-cuts-critical-incident-recovery-time-by-90-at-a-leading-financial-organization/comment-page-1/#comment-221 Gregory Weingard Sun, 04 Mar 2012 14:12:08 +0000 http://runbook-automation.com/?p=83#comment-221 I view something really interesting about your blog so I bookmarked . I view something really interesting about your blog so I bookmarked .

]]> Comment on How to implement file automation (without scripting) by Marketing communications Automation Bot http://runbook-automation.com/how-to-implement-file-automation/comment-page-1/#comment-218 Marketing communications Automation Bot Thu, 01 Mar 2012 17:56:08 +0000 http://runbook-automation.com/?p=98#comment-218 Thanks for another magnificent article. The place else may just anyone get that kind of info in such an ideal manner of writing? I have a presentation subsequent week, and I am on the search for such info. Thanks for another magnificent article. The place else may just anyone get that kind of info in such an ideal manner of writing? I have a presentation subsequent week, and I am on the search for such info.

]]> Comment on 5 IT Process Automation (ITPA) challenges and how to overcome them by Ayehu admin http://runbook-automation.com/5-it-process-automation-itpa-challenges-and-how-to-overcome-them/comment-page-1/#comment-216 Ayehu admin Wed, 29 Feb 2012 15:35:48 +0000 http://runbook-automation.com/?p=126#comment-216 @Rob, thanks for the insightful comment, you are absolutely right. Before automating any procedure one must be able to clearly define the purpose and the exact steps to be carried out by the people before anything else. True - there's probably no automation tool today that can do that without the analysis and the manual processes implemented first. The only thing that a tool can contribute is to force a team to re-examine and analyze the process to clearly define it and test it, rather than swing it each time. But possibly, you gave us some food for thoughts for our next posts. To be continued… Gabby @Rob, thanks for the insightful comment, you are absolutely right. Before automating any procedure one must be able to clearly define the purpose and the exact steps to be carried out by the people before anything else. True – there’s probably no automation tool today that can do that without the analysis and the manual processes implemented first. The only thing that a tool can contribute is to force a team to re-examine and analyze the process to clearly define it and test it, rather than swing it each time. But possibly, you gave us some food for thoughts for our next posts. To be continued… Gabby

]]> Comment on 5 IT Process Automation (ITPA) challenges and how to overcome them by Rob van Eerd http://runbook-automation.com/5-it-process-automation-itpa-challenges-and-how-to-overcome-them/comment-page-1/#comment-215 Rob van Eerd Wed, 29 Feb 2012 13:22:55 +0000 http://runbook-automation.com/?p=126#comment-215 Nice article! Maybe the below comment might help as well. I've been implementing interfaces using Process Automation tooling, but my main concern is: People aren't able to properly think in processes when it comes to building interfaces. They dig into the bits and bytes the moment they're designing one. With today's tools and technology, anything can be dealt with, except for unclear / nondefined processes. Even when one conciders other processes and procedures, people often aren't capable of explaining the processes mentioned. There's a lot of work going on (inside these processes) by people involved, dealing with issues as their daily business, without being table to tell exactly why they do what they do. When it comes to automating these processes, one has to investigate the activities in such a way they would be able to explain to the people involved, what they do and why. If that's all clear, understood and accepted, next step could be automating these real processes. Last thing that's forgotten pretty often: Building in proper error-detection and -handling! Nice article!
Maybe the below comment might help as well.

I’ve been implementing interfaces using Process Automation tooling, but my main concern is:
People aren’t able to properly think in processes when it comes to building interfaces. They dig into the bits and bytes the moment they’re designing one.
With today’s tools and technology, anything can be dealt with, except for unclear / nondefined processes.

Even when one conciders other processes and procedures, people often aren’t capable of explaining the processes mentioned. There’s a lot of work going on (inside these processes) by people involved, dealing with issues as their daily business, without being table to tell exactly why they do what they do.
When it comes to automating these processes, one has to investigate the activities in such a way they would be able to explain to the people involved, what they do and why.
If that’s all clear, understood and accepted, next step could be automating these real processes.

Last thing that’s forgotten pretty often: Building in proper error-detection and -handling!

]]>