Content packages for development systems

IBM Control Desk provides an easy way to supplement your base installation with additional content packages. Content packages consist of additional artifacts and configurations that can be installed with Control Desk.

The packages are not required for the product applications to operate properly, but they provide significant value either as samples or as templates that you can refine to meet your specific business needs. The packs are built on a solid foundation of ITIL standards and real-world customer experiences. Examples of optional content include job plans, reports, roles, escalations, and start centers. By reducing the amount of configuration needed to get processes ready for launch, this content can save you considerable time. No additional costs are incurred for content packs.

The content is packaged based on IT service management disciplines. Content packs are available for the following functions:

Service Desk
Service Catalog
Configuration Management
Change Management
Release Management
IT Asset Management (hardware)
Software Asset Management

The content can be applied to the product in two ways.

Optional Content Packages: This content is delivered with the product. You can choose whether to install this content when you install or upgrade your product. The optional content is carefully designed, tested, and supported.

Process Content Packs: Process Content Packs are maintained in the Integrated Service Management (ISM) Library. After IBM Control Desk is installed, you can install Process Content Packs with the ISM Content Installer application in IBM Control Desk. Published packs for your version of IBM Control Desk are displayed in the application. You can click the Download link and follow the on-screen instructions to add the pack to your system. Read the documentation that accompanies the pack for information about prerequisites, post-installation tasks, usage guidelines, and references. Process Content Packs are provided as is. However, the development teams make a best effort to support them.

The following table describes the content packages that are available for each distribution method.

Table 1. Content package availability
IT Service Management Function	Process Content Packs	Optional Content
Service Desk	Yes	Yes
Service Catalog	Yes	Yes
Configuration Management		Yes
Change Management	Yes	Yes
Release Management		Yes
IT Asset Management (hardware)	Yes	Yes
Software Asset Management	Yes

Keep in mind that content packages are specifically designed for a given product version. For example, if you install version 7.6.0 of the product, you must also use an Optional Content pack or Process Content Pack that is for version 7.6.0

The following table provides some general guidelines that you can use when determining which content packs to implement.

Table 2. Guidelines for selecting content packages
Implementation Needs	Consider using	Reason for choosing this option
Phased approach	Process Content Packs	Process Content Packs are a better option if you want to have an initial rollout and add content in phases after your initial implementation.
Demo data	Optional Content packages	If you plan to have pre-production instances that you test and fine tune before you migrate to a clean production instance for your initial rollout, Optional Content is the better choice. Optional Content is designed for environments that benefit from sample data, including the loading of mock service requests, incidents, change records, and so forth.
Mature processes already exist	Process Content Packs	Process Content Packs are usually a better option if your IT service management process are already well defined.
Speedy implementation	Process Content Packs	Because Optional Content is intended primarily for pre-production environments, Process Content Packs tend to work better if you want a quick initial rollout.

If you cannot discern a clear path using the preceding guidelines, review the content packs in detail to determine your best option.