This topic discusses the best practices for creating time frames and blackout policies.
Establish a standard and provide meaningful names for time frames. Include an abbreviation for the actual time frame in the time frame name. For example, a time frame that starts at midnight on Friday night and ends at midnight Sunday night can be named “Weekends.” If a time frame is related to a specific maintenance period for a specific application, include an abbreviation of the application name in the name as well as a representation of the actual time period for the time frame.
Provide a complete description for each time frame and put the information with the maximum impact at the beginning of the description.
Do not create unnecessary time frames. For example, if you never intend to use a time frame that covers 100% of the time, do not create a time frame for “24x7.” The reason for not doing this is to help avoid mistakes as the time frame can be accidentally applied.
Avoid creating overlapping time frames to avoid confusion.
Note
Time frames based on start and end times cannot “span across” midnight. If you need to set up a time frame that spans midnight, you must set it up using the duration-based time frame capability. For example, if you want a time frame that starts at 6:00 P.M. on Saturday night and ends at 6:00 A.M. Sunday morning, create a time frame as shown in the following screen shot.
Notes