Data entered into the system configuration files is used to produce the various reports (verification, cost analysis, service log, etc.). Access to the configuration files is controlled via a ‘software key’.

The purpose of this restricted access is to enable In-Site to offer a high level of system security and integrity to both our client and they in turn, to their customers.

In-Site can provide independent assurance that CIP routines to food processing vessel/mains have been carried out precisely to agreed parameters.

In-Site acts independently of the site’s CIP system control processors and will verify the CIP programme only against agreed set points and parameters, not a temporary quick fix setting.

'Locking-off' general access to the In-Site configuration files protects the integrity of the system and ensures that PASS classifications were not the result of falsified information.

On occasions a CIP operator might change a set point parameter in the CIP operating system to ‘force’ a CIP programme through to completion.

This may be due, for example, to the supply of chemical being exhausted, if the detergent controller does not detect the required % concentration set point, the CIP step will be ‘held’.

If the detergent replenishment is likely to involve a lengthy delay, a quick fix is to reduce the detergent set point, complete the CIP programme and then put the set point back to its original setting. As the set point was lowered, thus ensuring alarms or flags were not triggered, the assumption would be that the CIP operation was correct and within spec.

It is because In-Site acts independently of the CIP process controller, should any unauthorised amendment be made to CIP set-points, the changes made outside of the In-Site 'clean parameters', could result in the subsequent verification report receiving a FAIL classification.

The use of a software key negates the need for passwords, thus giving the system a more reliable form of security. In order for a PC to run the In-Site software, the system must have a correctly programmed ‘software key’ installed.

Each software key is programmed to restrict the user to only those parts of the system relevant to their need. Sensitive information such as costs can be limited to authorised personnel only merely by modifying certain user software keys.

Access to the system configuration files can therefore be strictly limited and can only be accessed by authorised technicians.

Each key has a unique code number and this is shown on the Viewer display. This number is also recorded on any hard copy of reports.

Information added to, or amendments made to report configuration files will automatically record the software key used to make the amendment. Examples of these changes being the Service Log and Verification report.

The Service log requires the plant item to be 'reset' after service or inspection. Users of the In-Site system, with the correct security software key are able to retrospectively insert the microbiological result attained from each clean in to the Verification report. This data will then be archived and be displayed on the Viewer front screen alongside the columns identifying Cost, CO2 and Duration of clean.

The Clean Parameter set-up report is a ‘controlled document’. Origination date of the report and also the date any amendments are made are automatically time stamped into the system. The set-up report will record the software key I.D. of the person entering data or changing values.