Try something like this:
When the process starts take a snapshot of the current time of day - ie, day, hour, min, sec. Then add one to the day (account for end of week or end of month roll over depending on whether you use the day of the week or the day of the month.) Now when the real time becomes equal to that value, trigger your event. Since the RTC keeps time even when power is off, you don't need a UPS or any special logic to advance a timer - though obviously your PLC will have to be running when the 24 hours expires or it will miss the event.
The attahced file has three examples of how you might do it.
Example 1 uses a CPW instruction to copy values from the real time clock and triggers using the day of the month with roll over detection for the last day of the month. Leap years are not accounted for.
Example 2 uses the day of the week with roll over detection for Saturday-Sunday, and MOV instructions to individually move values from the real time clock.
Example 3 uses the day of the week also but takes its values from the S file. Be warned that in the MicroLogix family S file date and time words are not updated while you are online with RSLogix 500.
Potential pitfall: Because the time is continuously changing you will want to write your event trigger to be a single shot and use it to start and latch in whatever it is doing. If you use GEQ statements in rung 1 of the examples you could get multiple triggers over an hour or a day.
(disclaimer: I have not tested these examples)