Siebel Forecasting Guide > Common High-Level Forecast Usage Examples >

Service Forecasting

Often end users need a service pipeline, backlog, and actuals for capacity planning, resource allocation, and service product planning.

Forecast Requirements

The forecast must include revenue scheduling, spreadsheets, services as products, easy to add recurring revenues, and pull scheduled revenue into the correct lengths of time.

Administrator Usage Example

The administrator defines a forecast series with the name Service. The Auto Forecast Search Spec is set as follows:

[Product] IS NOT NULL and [Calculated Primary Flag] = 'N'

This search specification pulls revenue line items that have a product indicated into the forecast.

End User Revenue Example

The end user:

• Creates a new opportunity or project.
• Associates and creates revenues using revenue scripts or revenue plans to establish a revenue group ID.
• Uses the revenue spreadsheet to view and maintain revenues over the scheduled time. As revenues become backlog or actuals they must be updated by the practice manager.
• Uses revenue charts and reports to graphically display data and to perform ad hoc analysis.

End User Forecast Example

The end user:

1. Creates a forecast based on the Service forecast series.
2. In the Details view, uses the spreadsheet and chart views to evaluate and adjust scheduled revenues.
3. Uses predefined queries to see details by service.
4. Submits the forecast.