Skip to main content

Commissioning checklist

Go through this list before a project goes into operation, for example as part of the site acceptance test. Each step uses a tool that is described on its own page; tick the items as you go and keep the list with the acceptance records.

Before you begin​

  • The project is configured, its drivers and devices are created and the server is connected to the field network.
  • You can sign in on the home page as root.

Steps​

1. Run the diagnostic scan​

  • Every check in Tools › Diagnostics is scanned. No check of severity error has findings, and every warning is fixed or understood.
  • Points without a source lists only system signals.

See Diagnostics and audit.

2. Test addresses and check the communication​

  • Read now returns the expected value and Good quality for a sample of signals of every device.
  • The Communication check shows no address conflicts and no device with a load that it cannot answer.

See Test addresses and check communication.

3. Check the communication state​

  • On the Processes tab every driver runs and shows that it communicates.
  • Unplugging one device raises its communication alarm, and the alarm clears when it is plugged back in.

See Communication state and communication alarms.

4. Check the clocks​

  • The server synchronises with an NTP server.
  • The RTUs are synchronised, and their device times are not marked invalid.

See Time synchronisation (NTP).

5. Check the history​

  • The signals that must be recorded are assigned to archive tables, and their values appear in a trend.
  • The retention of each table and the disk limits in Historian settings fit the disk of the server.

See Archive tables and assignments and Disk and history protection.

6. Harden the server​

7. Back up and restore once​

  • Each project is backed up with Back up… on the home page, and its history database with the PostgreSQL tools.
  • The backup has been restored once on a separate computer, and the project opens there.
  • Copies of the backups, of the secrets folders and of apps\projects-server\.env are stored off the server.

See Backup and restore.

Result​

Every item is ticked, and the project goes into operation with a backup that is known to restore.