Note: term 'site' in the further text stands for the customer's GN4 system as a whole, and not only the Web site or similar.

After you've installed and customized a GN4 you need to document it.

The purpose of such documentation is:

•To allow yourself to find the important fact sheets about the site months later.

•To allow to the customer support staff to understand and maintain the given system, even if they were not involved in installing it, or they forgot whats and whys about the system.

•To allow to the Miles 33 support staff to support and troubleshoot the given system, even if they were not involved in installing it.

The site documentation can be in any format - the simplest one is a text file, the recommended one is the Microsoft Word docx as you can put some screenshots there.

A copy of the site documentation should be stored for the customer, in an accessible folder on an accessible site server. The customer support staff has to be instructed about the appropriate ways to edit such documentation and clearly state the editor, the revision date and the incremented version, and to mark changed items in text of the documents.

A copy of the same document has to be made available internally for the Miles 33 support, typically on the Intranet.

The documentation file name should contain the version and subversion, e.g.

XXXX GN4 system summary v1.2.docx

Note for the Miles 33 support staff

Before editing the site documentation, always compare it with the customer's version, not only by the revision number and date, but also by content. If the customer's version is newer or different, copy it locally and edit that version, and when done, update also the customer's copy.

See also

Site name, description, and other facts

List and description of servers

GN4 connection related URLS and credentials