Applications - Incident and Event Databases

Many databases that will be examined by Daisy, can loosely be described as Incident, Event or Quality Databases.

Consider all of the guarantee returns, received for cars, televisions, computer software or any product. These can be stored in a database, which might include fields such as date, date made, fault type, product etc.

By mapping this database, any common links in the pattern of faults can be ascertained. In the bad old days, this was often obvious, but with product quality now being of a generally high level, it is often much more difficult to spot common faults. Especially, if they only occur a few times and then perhaps as far apart as Scunthorpe and Sydney!

The three most powerful mapping formats when analysing these databases are :-

1. Keyword which can be used to map individual keywords held in a text field. Thus a field containing 'red battery gearbox', would be mapped to the three nodes, red, battery and gearbox.

2. Day of Week always creates interesting mapping and links. It is a valuable check on data, as many dates are not valid on say Saturday and Sunday.

3. Hour can map the pattern of events during the day.

Look at any of the the 'Newmarket' examples supplied with Daisy. Are these just a simple Event Database?