Table design for permit

[Michael DiCostanzo]

My facility has an air quality permit that lists equipment, the
regulations that the equipment is subject to, conditions that apply to
that equipment, and the regulations that support those conditions. I
am trying to create a database that will help me manage the program
that assures compiance with that permit.

A typical listing for equipment looks something like this:


Device# Emission limit Conditions
------- -------------- ----------
D1 404; 1107 A63.1; B17,1; C19.1


The conditions section looks something like this:

Condition # Description Rule Citation
----------- ----------- -------------
A63.1 (Text) 109, 3003


A few months ago, I created a simple version of the permit using the
following tables:

Device
------
devID (pk)
devDescription

Conditions
----------
condID (pk)
condDescription

I linked the two table together using a third table like this:

DeviceConditions
----------------
dcID (pk)
devID
condID

I need to add the rule citations to the database. The rule citiations
in the device section and conditions section are very similar, so I'm
combining them into a single table as follows:

RuleLimits
----------
rlID (pk)
rlRule#

(Rule # would not be a good primary key because some rule numbers have
different dates.)

How would I link the RuleLimits table information to the devices and
conditions?

I was thinking about creating two tables along the lines of the
DeviceCondition table like so:

DeviceRuleLimits ConditionsRuleLimits
---------------- --------------------
xID (pk) yID (pk)
devID condID
rlID rlID


Is this the right path to follow to maintain normalization or is there
a better structure to follow? Where would I go from here? Thanks in
advance.