<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://www.itskeptic.org"  xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>The IT Skeptic - Comments for &quot;Doubting that automation really reduces errors&quot;</title>
 <link>http://www.itskeptic.org/doubting-automation-really-reduces-errors</link>
 <description>Comments for &quot;Doubting that automation really reduces errors&quot;</description>
 <language>en</language>
<item>
 <title>Cost of testing</title>
 <link>http://www.itskeptic.org/doubting-automation-really-reduces-errors#comment-6997</link>
 <description>&lt;p&gt;You raise the issue of testing.  Testing software - whether it be automation or anything else - far exceeds the cost of coding and (often? usually/ always?) exceeds the cost of planning and design.  This is frequently overlooked by IT Operations staff automating IT systems, who think that banging another rule or script into Tivoli, Patrol or Unicenter is a few hours work.  Likewise Service Desk tool admins adding workflow.&lt;/p&gt;
&lt;p&gt;if the business is automating a core process, then the system is usually properly design and built.. and tested.  If security staff want to automate access provisioning, someone bangs up a &quot;self-documenting&quot; Perl script, give it a quick unit test on the bench, then release it into the wild&lt;/p&gt;
</description>
 <pubDate>Tue, 15 Jun 2010 21:58:28 +0000</pubDate>
 <dc:creator>skeptic</dc:creator>
 <guid isPermaLink="false">comment 6997 at http://www.itskeptic.org</guid>
</item>
<item>
 <title>It depends upon the procedure</title>
 <link>http://www.itskeptic.org/doubting-automation-really-reduces-errors#comment-6995</link>
 <description>&lt;p&gt;One thing&#039;s for sure - if even (especially) technical staff are given a checklist to follow for a regularly performed operation then they will miss or skip bits, based upon what they think the instructions say, what they remember from previously doing it, etc.&lt;/p&gt;
&lt;p&gt;Whereas an automated procedure can be tested just as much as the software it may be managing or configuring.&lt;/p&gt;
</description>
 <pubDate>Tue, 15 Jun 2010 10:41:16 +0000</pubDate>
 <dc:creator>James R Grinter</dc:creator>
 <guid isPermaLink="false">comment 6995 at http://www.itskeptic.org</guid>
</item>
<item>
 <title>Hi Skep,
My first comment on</title>
 <link>http://www.itskeptic.org/doubting-automation-really-reduces-errors#comment-6985</link>
 <description>&lt;p&gt;Hi Skep,&lt;br /&gt;
My first comment on your blog.&lt;br /&gt;
Thanks for sharing your ideas with the community.&lt;/p&gt;
&lt;p&gt;Automation reducing errors, in terms of ? &lt;/p&gt;
&lt;p&gt;Frequency... you&#039;re right, reducing human actions will reduce the potential &#039;human deviation&#039; to perform a none required/ inappropriate action in the process.&lt;/p&gt;
&lt;p&gt;Impact... sure not !!!&lt;br /&gt;
My understanding is that automation is about configuring a &#039;system&#039; in a specified context that handle (repeating) required task. If something happens in a context not initially identified and addressed during the &#039;system&#039; design, this system is failing by applying inappropriate actions that could lead to Bigger Impact.&lt;/p&gt;
&lt;p&gt;To reduce this, we need to implement appropriate controls to identify theses &#039;context deviation&#039;  and may stop the process.&lt;/p&gt;
&lt;p&gt;We could consider also that a &#039;bad system design&#039;, is still due to humans. Doh! (Homer Simpson Style)&lt;br /&gt;
To Reduce/ prevent errors, please eliminate Humans (See &quot;2001, a space odyssey&quot; 1968).&lt;/p&gt;
&lt;p&gt;Smi.&lt;/p&gt;
</description>
 <pubDate>Wed, 09 Jun 2010 14:07:16 +0000</pubDate>
 <dc:creator>Smi</dc:creator>
 <guid isPermaLink="false">comment 6985 at http://www.itskeptic.org</guid>
</item>
</channel>
</rss>
