Installation and change control documentation requirements

During the installation procedure and as changes and patches or hotfixes are added to the system, it is important that you keep good records.

The spreadsheet shown on the following page is an example of an installation and change control record. Note how it identifies all major software components and identifies where they are installed.

It is also important to document any AVEVA hotfixes or patches that are installed. These typically do not appear in the Windows Add/Remove Programs Control Panel dialog box.

Note: Having complete installation records will help ensure that the components that are installed on your system are communicated to support engineers when troubleshooting problems or when determining whether a new hotfix that is being requested is compatible. For MES, most hotfixes as well as the current version information is stored in the db_status table.

This spreadsheet is intended to be used with the system topology diagram to provide a complete picture of the system. For an example of a system topology diagram, see Typical Medium-Size Plant.

Any one of these servers can be duplicated to scale out the solution. For example, there are often two database servers with one dedicated to the production databases and one for reporting databases. Other examples include a second Work Task Server for load balancing or multiple servers of the same type for load balancing.

The key to the servers listed in the columns is shown below.

• DB: Database Server

• AS: Application Server for System Platform-related software

• TS: Terminal Server for client applications

• WT: Work Tasks Server

• WEB: Web Server

• DEV: Development machine