Service schedules are a combination of a defined schedule with a specific service model component that indicates when the component must meet availability or performance goals. Each component is assigned a service schedule (but it can be a schedule shared with other components) which is as follows:
Component attributes such as cost or base priority might have different values depending on whether the component is in high demand (a During Schedule period) or in low demand (an Off Schedule period). These priority changes are discussed in more detail in the Dynamic prioritization section.
Consider a component that is expected to meet its performance goals from 8 A.M. to 5 P.M. each day. This period is considered During Schedule. The same component, if not needed from 5 P.M. to 8 A.M. each day, is considered Off Schedule during that time.
Within the During Schedule period, if the component is scheduled to be taken offline every day from noon to 1 P.M., instead of creating two different During Schedule time frames (one for 8 A.M. to noon, and another from 1 P.M. to 5 P.M.), you could create an Exceptions Within During Schedule time frame.
Service schedules are built of timeframes. Timeframes are blocks of time that specify the times that are During Schedule or Exceptions Within During Schedule. Two types of timeframes exist:
The following table illustrates the differences between global timeframes and local timeframes:
Global and Local timeframe differences
Timeframe type | Created in | Stored in | Available to |
---|---|---|---|
Global | BMC Impact Model Designer | BMC Atrium CMDB | All cells |
Local | BMC ProactiveNet | A single cell | Event management policies within a single cell |