Re: [foxboro] Migration and a standardized procedure to help customers
- From: "Jim Mowrey" <jmowrey@xxxxxxxxxxxxx>
- To: <foxboro@xxxxxxxxxxxxx>
- Date: Tue, 1 Aug 2006 13:29:57 -0400
This is the tool I was referring to in an earlier email.
I've used the output, and it does not have everything that Andreas asked
for, but it is a good start on obtaining that information.
Jim Mowrey
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On
Behalf Of Boulay, Russ
Sent: Tuesday, August 01, 2006 8:32 AM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] Migration and a standardized procedure to help
customers
Andreas...the Foxboro contact in your area must not be making you aware
of the facilities and tools that they have.
The "ferret" tool has been run on hundreds of sites now and databases
have been created for those users. The collection of ferret has been
mandated to be run at every location.
The results of the ferret tool are then fed into our lifecycle tool and
can create a customized report of your system.
Graphical representation of your system vs. the existing lifecycle
timelines.
If you have had this occur at your site already and you find it
deficient in some way..please let me know. I have direct contact to
those involved in this project
Regards...russb
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
On Behalf Of Weiss, Andreas
Sent: Tuesday, August 01, 2006 6:51 AM
To: foxboro@xxxxxxxxxxxxx
Subject: [foxboro] Migration and a standardized procedure to help
customers
Hi,
are their offer customers out there which use a running I/A system and
would like to keep it running as long as possible to save the
investment?
My scenario expects that you have a running system with enough capacity
in every system level (I/O modules, CP load, powerful AWs, enough DM
licenses, ...) but you use some devices that are marked as "obsolete".
I discussed that issue with colleagues and came across that we would
like to have a standardized procedure for that case.
What kind of information do we expect TO GET FROM Invensys Foxboro?
- Every offer should contain the dates for withdrawn from sale,
transition to lifetime and no longer repairable!
- A inventory list for every plant with the following columns
Name
Letterbug
Type
Release
Description
delivery date or purchase order date
Date Introduced
Date Withdrawn from Sale
Date Transition to Lifetime
Date No longer Repairable
id (used as a pointer to another document with informations about new
Hard-/Software)
- At least one or more migration options in a table with the following
columns
(every option in one table)
id
Name
Type
Release
Description
Date Introduced
Date Withdrawn from Sale
Date Transition to Lifetime
Date No longer Repairable
Price
Prerequisites (should contain infos like more space needed | other
connector types | other file format |...)
consequential costs (based on the requirements of the new hardware or
software)
backward compatibility (yes or no)
The document with migration options should be extended by a system
drawing, some notes about the advantages and disadvantages of that
solution.
Which new features will be available using that migration option?
- A more general question: Is it cheaper to jump over one technology
generation or better go every migration step?
What are your opinions?
What would you expect?
I appreciate every comment I get.=3D20
Regards,
Andreas Weiss
Ineos Cologne
=20
=20
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html
=20
foxboro mailing list: //www.freelists.org/list/foxboro
to subscribe: =
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Djoin
to unsubscribe: =
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave
=20
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html
foxboro mailing list: //www.freelists.org/list/foxboro
to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html
foxboro mailing list: //www.freelists.org/list/foxboro
to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
Other related posts:
