Preventative Maintenance Program

[bridgeman]

I have been tasked with developing a prevenative maintenance program using
access. So far I have gotten my tables set up and input all supporting
information. I am running into a roadblock regarding how to proceed further.
If anyone has any experience developing a Preventative Maintenance Program
any suggestions would be helpful. I am attempting to keep the program as
simple as possible. The PM's are set on frequencies of 1, 4, 8, 13, 26, 52,
and 104 week cycles respectively, whereas 1 represents 1 week, 4 represents 4
weeks, etc. Their are 114 unique PM's, and 4 different facilities in which
they may be performed. I have developed a main table that contains all the PM
information, then developed 4 separate tables for the individual facilities
to hold PM information pertinent to the respective facility, also I created a
table for the PM frequencies. Also I created 4 separate tables to store
information for the dates the PM are performed and used a 3 key composite
index to enable the ability to recall records historically, and to use the
last date the pm was performed to be the base for calculating the next date
due based upon the frequency. Any guidance or suggestions would be helpful,
and in advance thank you for your help and support,
Cordially,
jason

 

[KARL DEWEY]

developed 4 separate tables for the individual facilities to hold PM
information pertinent to the respective facility
Use one with a field to identify facility.
Would not the 'main table that contains all the PM information' also contain
the frequency?
Use one table with a field to identify facility. Have a field for DueDate
and CompDate.
You might consider adding into the PM main table a field to control whether
'next date due' based upon last schedule or last completed. A field in the
PM table could be used like this --
IIF([PM].[Slip] = -1, DateAdd("ww", [PM].[Freq], Max([CompDate]),
DateAdd("ww", [PM].[Freq], Max([SchedDate]))

 

[bridgeman]

Karl,
I appreciate your feedback. In response to your first statement concerning
the creation of 4 separate tables, the reason that I did this was that in
some cases the ActCode for the maintenance to be preformed are the same for
each facility and sometimes they are unique to the facility. It was the best
way that I could think of to accomplish this.
In response to your second statement concerning the contents of the main
table, yes it does contain the frequency, activity code, activity
description, actiivity type, equipment needed, structure name, and structure
number. All the info is there, however I assumed that I would separate the
frequecy field from the main table and relate it using the common ActCode
field in order use it as an index for calculating the next time the pm would
be due.
I see what you are saying about the next date due, last date completed code
that is written below and that is something I was considering but did not
know how to explain it. I am new to this and may have become overwhelmed, but
I am not a quitter so I will, "build a little, mess up a lot, but keep
trying".
Thanks
Bridgeman

information pertinent to the respective facility
Use one with a field to identify facility.
Would not the 'main table that contains all the PM information' also contain
the frequency?
Use one table with a field to identify facility. Have a field for DueDate
and CompDate.
You might consider adding into the PM main table a field to control whether
'next date due' based upon last schedule or last completed. A field in the
PM table could be used like this --
IIF([PM].[Slip] = -1, DateAdd("ww", [PM].[Freq], Max([CompDate]),
DateAdd("ww", [PM].[Freq], Max([SchedDate]))


--
Build a little, test a little.

I have been tasked with developing a prevenative maintenance program using
access. So far I have gotten my tables set up and input all supporting
information. I am running into a roadblock regarding how to proceed further.
If anyone has any experience developing a Preventative Maintenance Program
any suggestions would be helpful. I am attempting to keep the program as
simple as possible. The PM's are set on frequencies of 1, 4, 8, 13, 26, 52,
and 104 week cycles respectively, whereas 1 represents 1 week, 4 represents 4
weeks, etc. Their are 114 unique PM's, and 4 different facilities in which
they may be performed. I have developed a main table that contains all the PM
information, then developed 4 separate tables for the individual facilities
to hold PM information pertinent to the respective facility, also I created a
table for the PM frequencies. Also I created 4 separate tables to store
information for the dates the PM are performed and used a 3 key composite
index to enable the ability to recall records historically, and to use the
last date the pm was performed to be the base for calculating the next date
due based upon the frequency. Any guidance or suggestions would be helpful,
and in advance thank you for your help and support,
Cordially,
jason

 

[KARL DEWEY]

the ActCode for the maintenance to be preformed are the same for each
facility and sometimes they are unique to the facility.
I suggest creating a Facilities table and put the ActCode there (I do not
know what your ActCode is/does).

--
Build a little, test a little.

Karl,
I appreciate your feedback. In response to your first statement concerning
the creation of 4 separate tables, the reason that I did this was that in
some cases the ActCode for the maintenance to be preformed are the same for
each facility and sometimes they are unique to the facility. It was the best
way that I could think of to accomplish this.
In response to your second statement concerning the contents of the main
table, yes it does contain the frequency, activity code, activity
description, actiivity type, equipment needed, structure name, and structure
number. All the info is there, however I assumed that I would separate the
frequecy field from the main table and relate it using the common ActCode
field in order use it as an index for calculating the next time the pm would
be due.
I see what you are saying about the next date due, last date completed code
that is written below and that is something I was considering but did not
know how to explain it. I am new to this and may have become overwhelmed, but
I am not a quitter so I will, "build a little, mess up a lot, but keep
trying".
Thanks
Bridgeman

developed 4 separate tables for the individual facilities to hold PM

information pertinent to the respective facility
Use one with a field to identify facility.

also I created a table for the PM frequencies.

Would not the 'main table that contains all the PM information' also contain
the frequency?

Also I created 4 separate tables to store information for the dates the PM are performed

Use one table with a field to identify facility. Have a field for DueDate
and CompDate.

and to use the last date the pm was performed to be the base for calculating the next date due based upon the frequency.

You might consider adding into the PM main table a field to control whether
'next date due' based upon last schedule or last completed. A field in the
PM table could be used like this --
IIF([PM].[Slip] = -1, DateAdd("ww", [PM].[Freq], Max([CompDate]),
DateAdd("ww", [PM].[Freq], Max([SchedDate]))


--
Build a little, test a little.

I have been tasked with developing a prevenative maintenance program using
access. So far I have gotten my tables set up and input all supporting
information. I am running into a roadblock regarding how to proceed further.
If anyone has any experience developing a Preventative Maintenance Program
any suggestions would be helpful. I am attempting to keep the program as
simple as possible. The PM's are set on frequencies of 1, 4, 8, 13, 26, 52,
and 104 week cycles respectively, whereas 1 represents 1 week, 4 represents 4
weeks, etc. Their are 114 unique PM's, and 4 different facilities in which
they may be performed. I have developed a main table that contains all the PM
information, then developed 4 separate tables for the individual facilities
to hold PM information pertinent to the respective facility, also I created a
table for the PM frequencies. Also I created 4 separate tables to store
information for the dates the PM are performed and used a 3 key composite
index to enable the ability to recall records historically, and to use the
last date the pm was performed to be the base for calculating the next date
due based upon the frequency. Any guidance or suggestions would be helpful,
and in advance thank you for your help and support,
Cordially,
jason