Setup guide

OSx Migration Cookbook August 30, 2006
3 – The Migration Process
Testing the PCS 7
project
Making changes
to the PCS 7
project
either way.
Configurations that are imported in bulk use files that contain the
configuration data. How these files are created and who creates
them must be decided. Some of these files can be created via an
export from the OSx system. They can also be created using
Microsoft Windows tools such as Excel, or Notepad.
How many items are to be configured, their level of complexity,
and the number of items that are similar determines which features
to configure manually and which to configure via bulk import. For
example, configuring several hundred action requests manually, can
be tedious and time consuming. Exporting them from OSx and
importing them into PCS 7 is quicker and more efficient.
Unless there is an exact duplicate set of PLCs, testing the PCS 7
project requires using the PLCs that are used by the OSx system.
Additionally, it is a good idea to have at least one OSx station and
one PCS 7 station side by side so that the behavior of migrated
alarms, action requests, etc., can be observed. Ideally they should
behave similarly on both systems. See the Section 17 on testing for
considerations when running OSx and PCS 7 side by side.
Some tests should be devised to give an assurance that the PCS 7
system that has resulted from the migration behaves as expected.
Once the PCS 7 system is put into service, a plan should be in place
to decide how further changes will be made without the OSx system
available. In general, the OSx system is discarded. Even if that
system is retained, at some point it will fail permanently and no
longer be repairable. That is one reason the migration was done.
Therefore, future additions and changes will have to be made using
the tools available to the PCS 7 system.
9