Advice on Table structure

[Chimp8471]

I need some advice on the best way to set up a table please.

I am trying to put together a downtime log, we use items referred to as “Events”

An “Event” is a stoppage on the production line

An Example of an Event is “A101” this would represent “Jam up on Line”

I have set the table up as follows to look like:

EventcodeID - AutoNumber
EventCode - -Text (A101)
Description - - Text (Jam on Line)

The Letter A the Beginning Referes to a machine.

A=Filler
B=Packer
C=Box Maker
etc

Attached to and “Event” is a “Failure Mode”

A failure mode is the reason the Event occurred in more detail

An Example of a Failure Mode would be “A101A” you notice that the Event Code is given a letter “A” at the end, the failure mode also has a description

Example:

A101A – Jam On Line – Carton Fell Over

To Break this all Down

A (Machine Type) 101 (EventCode) A (Failuremode) - – Jam On Line (Event Code Description)– Carton Fell Over( Failure Mode Description.

It is very much a Parent Child situation the Event Code being the Parent and the event code being the child.

A Parent can have many children, each time the letter at the end would be different, B,C,D,E etc..

But not all Event Codes have Failuremodes


Should this all go in one table? Or 2 or more tables and make a relationship? An example of this would link up would be really helpful

Thanks in advance

Andy

 

[gemma-the-husky]

are the failure mode descriptions just text, or are they special codes you pick from a pick list, and therefore might need to count occurences of.

 

[Chimp8471]

they are just text descriptions