How many tables for best design

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

We need to track tests that are done on our parts and I'm pondering the best
solution for my DB. Basically we have a test station that has a loadlock and
a process chamber. Varying the setpoints of gases, temperatures and flows in
effect define the different Tests. So a standard TestA would require that
GasA, flows at 300sccm at a Temperature of 80deg, TestB uses
GasB,400sccm,70deg. I would like to provide a combination of forms that
allows the requestor to "check" the tests they want run for a given part and
then display the conditions to the Testing tech along with a data entry form
where they can enter the Date, TestStation, test results. The conditions
would vary only under special circumstances. My thinking is that along with
my Parts table, I can create a table that will contain the test conditions.
This table will serve to "control" the condtions for a given test. If an
engineer wants to change those conditions, I need a method for tracking
revisions.
On my test form I need checkboxes to indicate what tests to run and then
display the conditions.Then I need another table for the test tech to enter
the Date, Station, results for each test run on a Part. If someone has the
time to think about this and provide any feedback, I would appreciate it.
 
Think about things like:
Will the same test be run more than once on the same part?
If so, you dont want tests and results in the same table.
What are the results of tests pass/fail, good/fair/poor or what?
Is the same test run on different types of part or are the tests unique to
the part?
Do you test only one of each part or multiple samples?
If multiples, how are different parts of the same type identified, do they
have serial numbers?
Do you need to keep average/median test results for the same part/test ?

Seems like a fairly simple application, possible tables:
Part Types
Parts
Tests
Tests Run (links parts to tests)
Test Results

Dorian
 
Back
Top