× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: RE: Turnover configuration
  • From: "Cotes, Steven" <cotess@xxxxxxxxxxx>
  • Date: Tue, 17 Jun 1997 11:53:01 -0700

Maurice,
This sounds bit high.
Without knowing more about your environment and situating it is hard to
know though. For example, how many 400s will you be setting it up on ?
How well organized are your source libraries ? How many levels of
release
will be set up ?.....
Their manuals are good and they provide templates to start with. If you
are
working with someone who knows the product, you read the books ahead
of time and know roughly how you want it to work and you plan it ahead
of
time with your implementer 12 days should be more than enough. Multiple
systems will add to the complexity and testing required. I assume the 12
days doesn't include training time for your programmers, etc.
For a single system, a 12 day estimate to "configure" Turnover sounds
like
you may be paying for implementer OJT.

 -Steve Cotes
 -cotess@data-io.com

> ----------
> From:         Maurice Langeveld[SMTP:MauriceLa@EnerTel.nl]
> Sent:         Tuesday, June 17, 1997 3:20 AM
> To:   'AS/400 mailinglijst'
> Subject:      Turnover configuration
> 
> Our delivering company of our software package says that it will take
> them 12 days to configure whole Turnover for use. The IT-manager asked
> me if this is right, I talked to the company and think that 12 days is
> right, but how am I gonna explain it to my manager. Is there someone
> with experience configuring Turnover?
> 
> 
> 
> 
> >Maurice Langeveld
> >IT Operations @ EnerTel HQ
> >Technical specialist
> >Tel:010-2423772
> >fax:010-2423910
> >Email:
> - Business:      Mauricela@Enertel.nl
> - Private:          CFC@DDS.NL
> 
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* This is the Midrange System Mailing List!  To submit a new message,   *
* send your mail to "MIDRANGE-L@midrange.com".  To unsubscribe from     *
* this list send email to MAJORDOMO@midrange.com and specify            *
* 'unsubscribe MIDRANGE-L' in the body of your message.  Questions      *
* should be directed to the list owner / operator: david@midrange.com   *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.