Might be just me, but I can't work out what you want to achieve here. Can you try again?
I have 3 tables: Urgeny, Impact and a Matrix_Join table but I think I was able get done what I needed to without the need of calculations for the Matrix_Join table
Glad you may found a solution. If I understand your need (?), it appears there's no need for a join table, but you can use a calculated field in your "Incidents" layout (wherever you're managing such). Using a Case function one can calculate the results of your urgency and impact values. Based on the values you present in the Matrix_Join example, the Case tests can use a series of "<=" and "=>" (less than or equal to, etc.) to reduce the number of Case tests.
IMHO having urgency and impact as different inputs is not a good idea, because impact does influence urgency, so they're not completely independent variables.
A better solution could be just one parameter, minutes left to fix (mltf).
Users can't connect to database -> mltf = 0
Users get wrong calcs from their data input -> mltf = 0
Users can read from but not write to a record -> mltf 10
Users can't print -> mltf = 20
Logo on printed material needs update -> mltf = 1440
and so on.
siplus I had a similar thought after offering a reply to the OP's original "policy": a sort of "DEFCON" policy or urgency classing. Very simple to set up, scale, and maintain. This is how certain IT (e.g. ISP) support is factored.
Yeah, we are receiving much too many phone calls; some are really about a big problem (everybody has been disconnected) and some are about small things (we noticed that we have the same patient twice in the database, once it's Ho Min Koi and once Min Ho Koi, can you please merge the two) so we are trying to filter every phone call by
1) understanding the problem;
2) understanding how urgent the client feels the problem is
3) asking the client to send a mail to our support mail address if 1) + 2) have a mltf > 15,
because in our fire brigade role we are the only ones that know what the real fires are, look like and where they're located.