The single most significant disadvantage of this approach is that it does not consider the individual parameter's role with respect to the organization's overall operational objectives. Additionally, there is typically no scientific approach used to determine the data collection schedule and threshold values used by the metric. If this is the case, implement these objectives as part of the Baseline used in the initial roll-out. These immediate pay-back tasks should be highly scrutinized, with an objective of determining three to five. Separating Policy Planning from the Baseline installation process, focuses resources and eliminates bottlenecks that arise when trying to build Policy prior to roll-out.
Value is perceived by addressing the customer's immediate pay-back concerns.
History is collected that is used to facilitate the Policy Planning process. Both the Installation and Policy Planning processes are streamlined and interdependencies are eliminated. Policy Planning Process Ensuring that every message that shows up on a console is specific to an organization's operational objectives and, therefore, of immediate operational significance, is the objective of the Policy Planning process. It is important to communicate that Policy Planning is additionally an iterative process. Then, future Policy Tuning sessions are driven by the user department with the Policy Planning team changing to a support function.