[kictanet] Expensive software systems?
Brian Munyao Longwe
blongwe at gmail.com
Wed Jun 25 11:40:52 EAT 2008
Wes,
I both hear n feel you. I think these are some of the issues that the
newly established PPOA is supposed to handle. Along with that of
ensuring that Kenyansget a higher percentage of these deals.
Brian
Sent from my iPhone
On 25 Jun 2008, at 9:56 AM, wesley kiriinya <kiriinya2000 at yahoo.com>
wrote:
> Ladies and Gentlemen,
>
> How come most of the software systems Kenya gvnmt and related bodies
> purchase always cost 100s of millions if not a few billions?
> Like this one for KPA:
> http://www.bdafrica.com/index.php?option=com_content&task=view&id=8383&Itemid=5860
>
> This is not meant to hit anyone hard. I'm trying to see whether
> there is a better solution.
>
> So far this year I've heard of 3 systems:
> 1. KRA
> 2. Immigration
> 3. KPA.
>
> This KPA system costs a total of 450M, but the software bit is 200M.
> From the software features described I feel they could have got
> better value for their money.
>
> May be these systems really cost that much. May be there is someone
> in the list who can shed more light on these systems.
>
> BTW: To make this even more interesting various developers in the
> list can suggest a software solution component for each problem
> these systems solve, estimated development time and estimated cost.
> That way it's not just talking the talk but walking the walk.
>
> I'll take a shot:
> Case 1:
> From the newspaper article, one of the port guys is quoted as saying:
> “One unique thing about the system is its capacity to capture data i
> n real time. The moment a vehicle rolls out of a vessel, its data is
> captured. This makes it easier for us to track such cargo and conta
> iners as well," said Osero.
>
> My take:
> Analysis: The machines which are costing 250M (It's 250M machines +
> 200M software = 450M entire system) have sensors that measure
> different qualities/properties of the item in the machine e.g.
> weight. These machines have an API to link them to a computer
> system. Using the API get the measured quantity and display/store in
> database etc. This isn't really the hardest thing to do as the
> manufactures of the 250M machines should provide documentation and
> support to the software developers.
>
> Estimated work force and time: 3 developers, 3-4 months.
>
> Cost: 200K * 3 developers * 4 months = 2.4M. + 20% (any other
> expenses) = 2.88M.
>
> Case 2:
> Another feature is keeping track/audit trails/ historical data.
>
> My take:
> Analysis: This is basically from:
> 1. Collection of good requirements from the port.
> 2. Designing the right architecture that fits the requirements.
> 3. Creating the right designs from the architecture.
> 4. Pass the designs to the programmers for implementation.
>
> 1-3 are Key and this is where the bulk of the money will go.
>
> Estimated work force and time: 3 system requirements/analysis
> collectors, 4 months. The actual time depends on how well KPA know
> the problems they are facing, and how well they can describe them.
> 3 system/software
> architects, 3 months.
> 4 system/software
> designers, 5 months.
>
> Cost: (Requirements) 100K * 3 * 4 = 1.2M+20% = 1.44M
> (Architecture) 350K * 3 * 3 = 3.15M+20% = 3.78M
> (Design) 250K * 4 * 5 = 5M+20% = 6M.
>
> So far the total is 14.1 M. And these are some of the most important
> roles. Even with 15 programmers @ 100K for 12 months (+20%) = 21.6M
> for a current toral of 35.7M.
>
> OK I'll stop there. I'm not writting a report. Feel free to correct
> me. I could be very wrong.
>
> _______________________________________________
> kictanet mailing list
> kictanet at lists.kictanet.or.ke
> http://lists.kictanet.or.ke/mailman/listinfo/kictanet
>
> This message was sent to: blongwe at gmail.com
> Unsubscribe or change your options at http://lists.kictanet.or.ke/mailman/options/kictanet/blongwe%40gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.kictanet.or.ke/pipermail/kictanet/attachments/20080625/96315f61/attachment.htm>
More information about the KICTANet
mailing list