Migration Generation Tool

Special PRoVOX/EnVOX Migration Cost Estimate

Is it time to upgrade and migrate your PRoVOX/EnVOX database?

Maybe your migrating to DeltaV.

Maybe you migrating your existing EnVOX database to another DCS system?

Either way, consider letting us provide a competing's estimate
for generating the necessary migration data.

Submit your PRoVOX/EnVOX database controller devices and we will
provide the conventional industry standard analysis of the man-hours
and efforts required to document (review and decode manually)
the database devices for either transfer to DeltaV
or to another DCS system.

Our automated system can reduce costs for migrating
your PRoVOXEnVOX database.

Allow us to provide a competitive offer to document your database
in a format that can be migrated to any DCS system.

Who is Migrating Your PRoVOX/EnVOX Database?

Someone already Migrating Your PRoVOX/EnVOX Database?
How are you determing if their work is correct?

If you migrator did not provide you any documentation
of your current PRoVOX system and
are just delivering you a new system
then how do you know it is correct?

How to make your migration a SUCCESS.

FDS defines Current Process Functions and how they was built.
If the current system is documented,
then this should already be completed.

DDS defines the software and how it meets the Function Specifications.
The DDS usually compares the current software functions
versus the migrated software functions.

* * * *
In some cases, the FSTs were written 30 Plus years ago.
Some FSTs have more that 1500 instructions.
Sometime a few FSTs have more that 2500 instructions.
Has anyone reviewed them?
Are those who wrote them still available for design review?
* * * *

* * * *
Also Operations (Batch) were written 30 Plus years ago.
Some Operations have more that 2700 instructions.
Has anyone reviewed them?
Are those who wrote them still available for design review?
* * * *

How are you going to check it?

Are You Migrating the PRoVOX/EnVOX Database?
Doing it youself?
or Someone hired you to do the Migration?

In either case, you must understand the FSTs and Operations to complete the migration.

* * * *
The FSTs determine the interlocks conditions
and Operations determine the Batch logic processing
which have to be implemented in the migrated system.
The FSTs define the control loops including master and slaves.
The LCPs contain all the data the FSTs use and
if the FSTs use indirect addressing
then the DBI define the points referenced by the FST.

Doing this manually means spending time opening PRoVOX
copying FSTs to text files
then importing into spreadsheets for ease of use.
Then repeating this for LCPS.
If you need a DBI number, then you must again open PRoVOX.

Make it easy on yourself and let us transfer all this into spreadsheets in one simple operation.
* * * *

This will provide means for you to migrate and/or verify your new system.

Consider letting us provide the FST / LCP / DBI data for you.
Consider sending us a single LCP and FST for a sample response.
Send a couple of points for the DBI spreadsheet output.
Follow instructions below for transferring files.

What you have to do!

Submit your Company's NON-DISCLOSURE CONFIDENTIALLY
Agreement to DB Stuart Associates, Inc.
via DBStuart@att.net. I will sign and return.

Export your PRoVOX/EnVOX database controller devices
to ".cdv" and ".tgt" files
(All points, FSTs, Operations, Devices and Displays)

Zip to a single file

Email to DBStuart@att.net

What we will do!

Import the ".cdv" files into our system.

Generate easy to understand documents and tables of all the data,
such as number of types of points, FSTs, Operations, Displays, Devices.

Assign standard Man-Hours for all data types for manually
completion of the migration documentation.

We will submit to you the standard Man-Hours analysis table for review.
This will allow you to compare our proposal againist other competitors.

We will also submit a sample of the migration design documents
that will be generated via our automated system.

Allow us to provide a competitive offer
to migrate your PRoVOX/EnVOX database devices to DeltaV