--- web/www/contents.inc	2000/11/14 22:30:07	1.3
+++ web/www/contents.inc	2001/03/30 08:08:46	1.12
@@ -2,7 +2,7 @@
 <!--
     contents.inc
     Created by pjm2 14/10/2000
-    Last edited 14/11/2000
+    Last edited 16/01/2001
 -->
 
     <table border="0" width="500">
@@ -13,27 +13,67 @@
        <center><h3>Current Status</h3></center>
 
        <p align="justify">
-        During the "project week" coding has got well underway,
-        although mostly in the experimental stage. Planning and
-        design decisions are still being made, along with various
-        specification documents. Detailed information can usually
-        be found in the meeting minutes. Code is viewable via CVS
-        to UKC users only.
+        All i-scream components are now functioning to initial
+        design parameters and our system is regarded to be complete.
+        Documentation is available to assist third party programmers
+        in producing Hosts for use with the i-scream server.
+        Our progress during the project can be found in the meeting minutes.
+        Code is viewable via CVS to UKC users only.
        </p>
 
+       <p align="justify">
+        The i-scream Distributed Central Monitoring System <a href="http://raptor.ukc.ac.uk/~pjm2/reports">Reports</a>
+        are now visible on the web.  You may view the latest information
+        about each machine, historical 24-hour reports and alerts for
+        each machine.  Please remember that this is work in progress
+        still, so the only data currently viewable is our own data that
+        has been harvested by our own testing.  Also note that historical
+        reports are only available for periods during which our server
+        was running.
+       </p>
+
+       <p align="justify">
+        Our current host development allows us to pass machine statistics
+        to our distributed filter arrangement, which then processes the
+        data and stores it for later use.  An example of such use is the
+        historical report generator which produces graphs of machine
+        usage over periods of time.  A real-time
+        client is also available (Conient) and alert information can be
+        displayed to the public via dynamic web pages.
+       </p>
+       
+       <p align="justify">
+        Builds of the i-scream Distributed Central Monitoring System
+        are now available for <a href="/builds/">download</a> from this
+        website. These are still very much in development and should
+        only be used by people who have been in communication with the
+        development team. Please email us if you wish to use any i-scream
+        software, as we are interested to know who is using it and we may
+        be able to help you out with any problems you encounter.
+       </p>
+
        <p>&nbsp;</p>
-       <center><h3>Presentations</h3></center>
+       <center><h3>Project Completion</h3></center>
 
        <p align="justify">
-        On Monday 16th and Tuesday 17th October all members of the group made presentations to various groups of peers.
+        The project deadline was 4pm on 29 March 2001. Most of the group
+        met very early that morning to compile the project into five
+        lever arch folders. The project, consisting of source code, user,
+        maintenance and other documents, was handed in at 3pm.  The CVS
+        repository was tagged to signify the project's completion, however,
+        development and enhancements to the system shall be continued
+        in the near future.
        </p>
-	 <p align="justify">
-        For those who are interested you can view an online version
-        of our presentation <a href="documentation/presentation/i-scream-web.htm">here</a>.
-        <br>
-        Alternatively you can download a powerpoint version from
-        <a href="documentation/presentation/i-scream-web.ppt"> here</a>.
-        </p>
+       
+       <p align="justify">
+        As can be seen in the "problem domain" document, the project
+        was aimed at the UKC Computer Science department, and as such
+        we believe a demonstration to the "customer" is important. The
+        feedback from our demonstation was more positive than we had
+        anticipated. We believe that our project may now be of great
+        interest to anybody who wishes to monitor a number of machines
+        on their network using a central configuration.
+       </p>
 
        <p>&nbsp;</p>
        <center><h3>Naming History</h3></center>