USE OF NSR/NER IN AN SLC
rahazel 270003S2VE Visits (1787)
When building an SLC one step is to create a schedule defining when the SLC is in effect. When you get to the Create SLC Schedule you will be presented with a dropdown with two choices, Calendar Schedule and Duration Schedule.
If you select Calendar Schedule two of the parameters are the Normal Start Range (NSR) and the Normal End Range (NER). In a majority of cases you only need to set on of these parameters.
The use of an SLC is to determine if an event did or did not happen during a specific time period. Both the NSR and NER are time ranges, which one to use? In general most SLCs are written to see if an event starts or ends during that specific time frame.
If your concern is that an event starts on time, during a definite time range, you would want to define an NSR to make sure that the event started on time. For example you have process that must start between 7:00 and 7:30 AM. In this case you would want to define the NSR Start Time of 7:00 AM and the NSR End Time of 7:30 AM. You could then write rules to let you know if the process started early, this might be a problem if other things had to be in place prior to the process starting. You could write a rule to give you an alert if the process did not start before 7:30, important if you Service Level Agreements in place that you cannot miss.
On the other hand if the Service Level Agreements in place are based on process, a file transfer for example, completing during a specific time frame use the NER Start Time and NER End Time. In this instance the time that the process starts is not so important but when it completes is. You could then write your rules to alert you if the process is running late so remediation can take place to insure you do not miss your Service Level Agreements.