One of our production teams has informed us that they have a job which runs several days per week, but on one of those days it takes longer to complete than on the other days; this is considered normal behavior, not a problem. Unfortunately, the SLA set up in iDash 11 currently identifies these long-run days has having missed the SLA target. At present, the only options seem to be (1) ignore these alarms or (2) extend the SLA's end time to match the longest run (and thus possibly miss problems on the short-run days). As far as I can tell, the SLA input tools don't support end times based on day of week, nor does the database schema seem to allow for it.
If you get a negative response about iDASH
JAWS has a separate SLO/SLA feature and it has 3 settings for setting the alerts. JAWS based timing. and 2 user based timings.
You can create multiple SLAs for the same job and assign different deadlines based on specific days of the week or calendars. You just have to assign a different name to each SLA.
Hope that helps.