Managing Configuration Items › Configuration Audit and Control Facility (CACF) › Change Verification Best Practices › Organizing Policies

Organizing Policies

You can use several strategies to keep track of policies. We recommend that you use a multi-tier approach. Use increments of 100 between policy numbers to allow for future inserts.

Consider the following example tiers for this strategy:

Fundamental Policies

100,000-199,999

• Allow Change Administrators to perform inserts
• Disallow inserts by MDR Class(xxxx)
• Exclude all test CIs from incident creation

Temporary or Transient Policies

200,000-299,999: Bulk loads this week

Application-Specific Policies

• 301,000-301,999: Exceptions to the following general application-specific policies:

  For example, server1 in NY policies

• 311,000-311,999: Policies that relate to Service Type priority1 resolution
• 320,000-320,999: Policies that relate to NY
• 331,000-331,999: Policies that relate to Lisle

Technology-Specific Policies

• 410,000-410,999: Policies related to Servers.
• 411,000-411,999: Policies related to Network

Default Policies

You can use these policies if the previous policies do not apply to your environment.

900,000-999,999: Default policies, such as all updates to managed attributes (Any Managed Attribute) must have a change specification.