Dear Good People<br>IEBC is  currently doing an excellent job. <br><br>However, failure by the 
automated system is an opportunity for all of us to learn that 
automating a process requires another comprehensive process(both 
technical and management process). I strongly believe that the 
Communications Department was not well prepared, because we did not hear
 of any Business Continuity Plan (BCP), Security Management Plan, DRP 
(Disaster Recovery Plan) put in place. <br><br>This should have been the case as part of DRP:<br><ol><li>That the IEBC should have had, hot site and cold site.</li><li>The
 server should have been able to do mirroring and periodic back up at 
the same time to cater for data recovery for any scenario.</li><li>The data should have under gone buffering period to allow the Quality Assurance Team to do data screening on &#39;read only basis&#39;.</li><li>The system should been taken for end-to-end test for a period of 1 week.</li>
<li>Risk management process should have been established and maintained independently.</li></ol><br>With above, switching from auto to manual would have been seamless and effective.<br><br>Regards <br>Isaac Kiplagat, CISA<br>
Software Quality Assurance Expert,<br><br><div class="gmail_quote">On 7 March 2013 10:48, daniel gitau <span dir="ltr">&lt;<a href="mailto:danmac.daniel@gmail.com" target="_blank">danmac.daniel@gmail.com</a>&gt;</span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>As much as it may have been a technical issue, i wud be more inclined to think of it a political issue...like a case of dark forces infiltrating the commission&#39;s officers.. *cough* Remember the system had worked before and it cud hav only been better!<br>

<br>D<br><br><br><div class="gmail_quote">On Wed, Mar 6, 2013 at 11:01 PM, Dickson <span dir="ltr">&lt;<a href="mailto:dhikims@gmail.com" target="_blank">dhikims@gmail.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">

Let me cut the chase here. We have little information on the system. This was so in design to keep its integrity which has actually flopped. Let&#39;s stop speculating what it could have been, what happened et all, et all.<br>


<br>
I would suggest that as IT professionals we compile a list of questions both technical and logical which IEBC should answer.<br>
<br>
After IEBC is done with all its core mandate as they are doing, we then ask for the answers to those questions.<br>
<br>
Its a shame that the same year we launch ICT city (Konza) and claim we intend to develop and export technologies. We get such a failure from an IT front. Its a big shame to IT professional in a big scale. We have multinationals trying to pitch tent here how can they do so if we can&#39;t manage such a small system. Even a supper market system is more complex and busy than that system<br>


<br>
We need and deserve answers from IEBC.<br>
<div>Best Regards,<br>
<br>
Dickson.<br>
<br>
----<br>
<a href="http://qhim.wordpress.com" target="_blank">http://qhim.wordpress.com</a><br>
<br>
Sent from my BlackBerry®<br>
<br>
-----Original Message-----<br>
</div><div class="im"><div>From: Bernard Mwagiru &lt;<a href="mailto:bmwagiru@gmail.com" target="_blank">bmwagiru@gmail.com</a>&gt;<br>
Sender: <a href="mailto:skunkworks-bounces@lists.my.co.ke" target="_blank">skunkworks-bounces@lists.my.co.ke</a><br>
</div><div>Date: Wed, 6 Mar 2013 22:49:34<br>
To: Skunkworks Mailing List&lt;<a href="mailto:skunkworks@lists.my.co.ke" target="_blank">skunkworks@lists.my.co.ke</a>&gt;<br>
</div></div><div class="im"><div>Reply-To: Skunkworks Mailing List &lt;<a href="mailto:skunkworks@lists.my.co.ke" target="_blank">skunkworks@lists.my.co.ke</a>&gt;<br>
</div><div>Subject: Re: [Skunkworks] IEBC Systems<br>
<br>
</div></div><div class="im"><div><div>_______________________________________________<br>
skunkworks mailing list<br>
<a href="mailto:skunkworks@lists.my.co.ke" target="_blank">skunkworks@lists.my.co.ke</a><br>
------------<br>
List info, subscribe/unsubscribe<br>
<a href="http://lists.my.co.ke/cgi-bin/mailman/listinfo/skunkworks" target="_blank">http://lists.my.co.ke/cgi-bin/mailman/listinfo/skunkworks</a><br>
------------<br>
<br>
Skunkworks Rules<br>
<a href="http://my.co.ke/phpbb/viewtopic.php?f=24&amp;t=94" target="_blank">http://my.co.ke/phpbb/viewtopic.php?f=24&amp;t=94</a><br>
------------<br>
Other services @ <a href="http://my.co.ke" target="_blank">http://my.co.ke</a><br>
_______________________________________________<br>
skunkworks mailing list<br>
<a href="mailto:skunkworks@lists.my.co.ke" target="_blank">skunkworks@lists.my.co.ke</a><br>
------------<br>
List info, subscribe/unsubscribe<br>
<a href="http://lists.my.co.ke/cgi-bin/mailman/listinfo/skunkworks" target="_blank">http://lists.my.co.ke/cgi-bin/mailman/listinfo/skunkworks</a><br>
------------<br>
<br>
Skunkworks Rules<br>
<a href="http://my.co.ke/phpbb/viewtopic.php?f=24&amp;t=94" target="_blank">http://my.co.ke/phpbb/viewtopic.php?f=24&amp;t=94</a><br>
------------<br>
Other services @ <a href="http://my.co.ke" target="_blank">http://my.co.ke</a><br>
</div></div></div></blockquote></div><br>
<br>_______________________________________________<br>
skunkworks mailing list<br>
<a href="mailto:skunkworks@lists.my.co.ke">skunkworks@lists.my.co.ke</a><br>
------------<br>
List info, subscribe/unsubscribe<br>
<a href="http://lists.my.co.ke/cgi-bin/mailman/listinfo/skunkworks" target="_blank">http://lists.my.co.ke/cgi-bin/mailman/listinfo/skunkworks</a><br>
------------<br>
<br>
Skunkworks Rules<br>
<a href="http://my.co.ke/phpbb/viewtopic.php?f=24&amp;t=94" target="_blank">http://my.co.ke/phpbb/viewtopic.php?f=24&amp;t=94</a><br>
------------<br>
Other services @ <a href="http://my.co.ke" target="_blank">http://my.co.ke</a><br></blockquote></div><br><br clear="all"><br>-- <br>Isaac Kiplagat. KIP®<br><br><br>