<7. System Delivery Precautions>
7.1 System Delivery Checklist
Before starting system delivery, check the items described below.
7.1.1 System Delivery Prerequisites
Before starting system delivery, verify that all specification changes and problems
identified during use acceptance test have been addressed.
For any item that cannot be addressed in time for system delivery, confirm with the
user when and by whom it will be rectified, as well as how it will be tested.
7.1.2 Forms of Delivery
Determine in what form the control application is to be delivered. The actual form of
delivery differs widely for new system jobs, system expansion jobs and system
modification jobs. Some typical forms of delivery are described below.
● Forms of Delivery for New System
Consider the following forms of delivery for a new system job.
1. Delivering equipment used in user acceptance test as is
If the user acceptance test and required program modifications were carried on
target equipment, which is to be shipped as is after user acceptance test, no special
delivery engineering is required except for control application backup described in
Section 7.2, “Delivery for New System.”
2. Delivering CPU module and PC
This form of delivery is applicable if the FCN-500 or FCN-RTU was delivered early
for convenience of construction or whatever reason, and only the CPU module of
the target equipment and PC were used during user acceptance test. No special
delivery engineering is required except for control application backup described in
Section 7.2, “Delivery for New System.”
However, as UAT was carried out on in-house equipment, Resource Configurator
configuration information may have been modified.
Thus, Resource Configurator configuration information must be checked on the site
system.
3. Delivering only the CPU module
This form of delivery is applicable if the target equipment except for the CPU module
was delivered early for convenience of construction or whatever reason, and in-
house equipment was used for user acceptance test.
As with case 2 above, all FCN500 or FCN-RTU information is saved on the CPU
module so no special delivery engineering is required except for CPU module data
backup.
For the same reason given in case 2, Resource Configurator configuration
information must be checked on the site system.
Moreover, it is necessary to backup the control application and prepare a procedure
instruction sheet for restoring Logic Designer data to the site system.
To Next Page
Loading...
Need help?
General
