| 1. What Who When: | | 1. A page evidence trail of each request made to Eliza by an approved person is maintained for each day. The evidence trail is by page, so who and when a page is used can be recorded. | | * WHAT is a page token shown by Eliza to a person. | | * WHO is a person token who made a request to Eliza. | | * WHEN is the date and time of the reply. | | * WHY is potential for a future phase. |
| 2. Structure: | | 1. A unique file indexed by page token is created and reused - the page token is just a meaningless number. Evidence is appended by date and time and person token when Eliza chooses to reply with that page. The date and time are encrypted and the person token is a meaningless number. Each entire row is just a long string of meaningless digits. | | 2. When analysis of a page in in progress, the file may be destroyed so detailed analysis of a week or month usage can be accumulated. The WWW control panel enables any page file to be dropped or emptied at any time. |
| | | 3. Utilization: | | 1. What-Who-When is about how Eliza decides to reply with a specific web page number. Behaviour is created that show when a person entered certain requests that caused Eliza to reply in this way. | | 2. What-Who-When is very effective in detecting obsolete, unknown or useless web pages. By not having a file for a web page is negative evidence that the page has never been used. The number of rows in a file is evidence of how popular the web page is. |
| 4. Mission: | | 1. What-Who-When supplements What-Did-I-Do as additional evidence for Incident Management to identify the consequence of any persons request. | | * What-Did-I-Do tends to be evidence of what request the person made to Eliza. | | * What-Who-When tends to be evidence of how Eliza responded to a persons request. | | 2. The gap between input What-Did-I-Do and output What-Who-When is Eliza with her very large number of business rules. A Eliza learns more and creates more business rules, the ability for people to know WHY Eliza choose one reply over another reply will become more of a challenge. For Incident Management purposes, Eliza may be asked to show her logic path though the business rules when making any decision. |
| 5. Security: | | 1. This data does not contain any personally identifiable information, however the person token can be associated with a unique person by Eliza. | | 2. This data has an annual life cycle from creation to destruction. | | 3. This data is write-once, read-only for internal information purposes only. | | 4. If this data is lost, it does not need to be restored. | | 5. Tokens are deployed so Eliza can build data into information, but criminals will only see meaningless numbers. |
|