Initial Estimate guideline for a straight green-screen Axiant migration

Robert Edis robeconsult@sbcglobal.net
Thu, 16 Oct 2003 07:46:24 -0700 (PDT)


--0-1370352157-1066315584=:68208
Content-Type: text/plain; charset=us-ascii

Wilbert
 
It seems to me the client is best served by considering the following priorities:
 
1. Business rules - current - does the existing application fully support the current needs of the business and if not what available application does?
 
2. Business rules - future - does the existing application fully support the current AND potential needs of the business and if not what available application does?
 
3. Opportunity lost - what is the cost to the business from NOT changing current application?
 
4. Opportunity gained - what value is it to the business from replacing the current app with a new one?
 
5. What provides the best ROI - changing application (or design thereof), changing technology, or both?
 
6. How does the IT plan fit with company's 1 year, 5 year, 15 year plan?
 
7. Available and potential resources - human, financial and technological.
 
Etc.
 
Blue

"VISSERS,WILBERT (HP-NewZealand,ex1)" <wilbert.vissers@hp.com> wrote:
Thanks Blue, Mark, Jon, 

Have spoken to our Customer and PH8.41 and Eloquence is now a base-line
option if the business decision is 'go the minimum cost option'. Thanks
that was good.

The IT Manager wants the migration to go to the platform that allows modern
stuff to evolve best, because he expects that the percentage of people
seeing the value of Windows/Gui/Web will grow soon. We need to be in best
position to respond. Also the competitor option is all new stuff.

Decision on the database is down the track a bit, either SQL Server for
perhaps ease of future integration with Microsoft-written apps which the
customer has, or Oracle for robustness. or Eloquence. See the future of
the application as evolving into a mix of Competitive-advantage, local
efficiency modules, interfacing with standard ERP modules. Current app is
well-designed and modular so this looks feasible.

Need that ballpark guidance on Axiant's automated conversion tools. All we
have to compare with so far is migration projects done in other technologies
'by hand', and PH conversions where significant proportion of the project
was spent writing home-grown code-altering utilities. 

cheers
Wilbert
= = = = = = = = = = = = = = = = = = = = = = = = = = = =
Mailing list: powerh-l@lists.swau.edu
Subscribe: "subscribe" in message body to powerh-l-request@lists.swau.edu
Unsubscribe: "unsubscribe 
" in message body to powerh-l-request@lists.swau.edu
http://lists.swau.edu/mailman/listinfo/powerh-l
This list is closed, thus to post to the list you must be a subscriber.

Robert JM Edis
Principle Consultant
Robert Edis Consulting
P.O. Box 676
Deerfield  IL  60015
USA
1-847-612-3863
RobEConsult@sbcglobal.net
 

--0-1370352157-1066315584=:68208
Content-Type: text/html; charset=us-ascii

<DIV>Wilbert</DIV>
<DIV>&nbsp;</DIV>
<DIV>It seems to me the client is best served by considering the following priorities:</DIV>
<DIV>&nbsp;</DIV>
<DIV>1. Business rules - current - does the existing application fully support the current needs of the business and if not what available application does?</DIV>
<DIV>&nbsp;</DIV>
<DIV>2. Business rules - future - does the existing application fully support the&nbsp;current AND potential needs of the business and if not what available application does?</DIV>
<DIV>&nbsp;</DIV>
<DIV>3. Opportunity lost - what is the cost to the business&nbsp;from NOT changing current application?</DIV>
<DIV>&nbsp;</DIV>
<DIV>4. Opportunity gained - what value is it to the business&nbsp;from&nbsp;replacing the current app with a new one?</DIV>
<DIV>&nbsp;</DIV>
<DIV>5. What provides the best ROI - changing application (or design thereof), changing technology, or both?</DIV>
<DIV>&nbsp;</DIV>
<DIV>6. How does the IT plan fit with company's 1 year, 5 year, 15 year plan?</DIV>
<DIV>&nbsp;</DIV>
<DIV>7. Available and potential resources - human, financial and technological.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Etc.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Blue<BR><BR><B><I>"VISSERS,WILBERT (HP-NewZealand,ex1)" &lt;wilbert.vissers@hp.com&gt;</I></B> wrote:</DIV>
<BLOCKQUOTE class=replbq style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #1010ff 2px solid">Thanks Blue, Mark, Jon, <BR><BR>Have spoken to our Customer and PH8.41 and Eloquence is now a base-line<BR>option if the business decision is 'go the minimum cost option'. Thanks<BR>that was good.<BR><BR>The IT Manager wants the migration to go to the platform that allows modern<BR>stuff to evolve best, because he expects that the percentage of people<BR>seeing the value of Windows/Gui/Web will grow soon. We need to be in best<BR>position to respond. Also the competitor option is all new stuff.<BR><BR>Decision on the database is down the track a bit, either SQL Server for<BR>perhaps ease of future integration with Microsoft-written apps which the<BR>customer has, or Oracle for robustness. or Eloquence. See the future of<BR>the application as evolving into a mix of Competitive-advantage, local<BR>efficiency modules, interfacing with standard ERP modules. Current app is<BR>well!
 -designed
 and modular so this looks feasible.<BR><BR>Need that ballpark guidance on Axiant's automated conversion tools. All we<BR>have to compare with so far is migration projects done in other technologies<BR>'by hand', and PH conversions where significant proportion of the project<BR>was spent writing home-grown code-altering utilities. <BR><BR>cheers<BR>Wilbert<BR>= = = = = = = = = = = = = = = = = = = = = = = = = = = =<BR>Mailing list: powerh-l@lists.swau.edu<BR>Subscribe: "subscribe" in message body to powerh-l-request@lists.swau.edu<BR>Unsubscribe: "unsubscribe <PASSWORD>" in message body to powerh-l-request@lists.swau.edu<BR>http://lists.swau.edu/mailman/listinfo/powerh-l<BR>This list is closed, thus to post to the list you must be a subscriber.</BLOCKQUOTE><BR><BR><DIV><FONT face="comic sans ms" color=#0000ff><STRONG>Robert JM Edis</STRONG></FONT></DIV>
<DIV>Principle Consultant</DIV>
<DIV><EM>Robert Edis Consulting</EM></DIV>
<DIV>P.O. Box 676</DIV>
<DIV>Deerfield&nbsp; IL&nbsp; 60015</DIV>
<DIV>USA</DIV>
<DIV>1-847-612-3863</DIV>
<DIV><A href="mailto:RobEConsult@sbcglobal.net">RobEConsult@sbcglobal.net</A></DIV>
<DIV>&nbsp;</DIV>
--0-1370352157-1066315584=:68208--