Planning an Upgrade to Siebel 7 > Planning an Upgrade >

Evaluating Upgrade Complexity Based on Customization

At a high-level, you can use the following categories to characterize the complexity of your upgrade project.

Table 1 lists benchmarks for each complexity category based on the modules implemented, the number of real-time integration points, the number of batch interfaces, the total number of scripts, and the number of user interface-intensive scripts.

These complexity categories are guidelines only. The characteristics of your particular implementation drive your requirements. For example, you might have some characteristics of an extremely complex upgrade, but if you have basic interfaces or no customizations, then the overall complexity of your upgrade may be only moderate.

Table 1.  Complexity Categories
Complexity
Module
Integration
Scripts
Basic
Horizontal application,
end user only
Real time: 0
Interfaces: 3 or fewer
Total Scripts: 10 or less
UI: 0
Moderate
Horizontal or vertical application,
customer,
with simple UI branding
Real time: 2 - 5
Interfaces: 3 - 10
Total Scripts: 10 - 50
UI: 0 - 10
Complex
Horizontal or vertical application,
end user and customer
 
Real time: 5 - 10
Interfaces: 10 - 30
 
Total Scripts: 50 - 100
UI: 10 - 30
Scripts using Active X controls for information exchange with Siebel
Scripts using complex functionality such as terminal emulation windows
Extreme
Horizontal or vertical application,
end user and customer,
with one or more of the following data migrations:
  • Data migration from a highly customized schema
  • Specialized migration such as eAuction, Analytics, ISS, or mobile solution products
  • Migration from a horizontal application to a vertical application
  • Migration of a system with near-zero-downtime requirements
Real time: 10 or more
Interfaces: 30 or more
Total Scripts: 100 or more
UI: 30 or more
Scripts with desktop interaction via DLL or COM: 4 or more
Scripts using Active X controls for information exchange with Siebel
Scripts using complex functionality such as terminal emulation windows

Table 2 lists three scenarios that include estimates of resources and duration of the upgrade effort based on upgrade complexity.

Table 2. Example Scenarios
Upgrade/Migration Scenario
Level of Complexity
Staffing
Duration
From Release 6.3 Horizontal to Release 7.5 Horizontal.
Moderate
 
3 to 4 resources
 
8 weeks
From Release 6.x eComm Vertical to Release 7.5 eComm Vertical
Complex
 
8 to 10 resources
6 months
From Release 6.3 Horizontal to Release 7.5 Financial Services Vertical
Extreme
 
20 resources
12 to 20 months
 


 Planning an Upgrade to Siebel 7 
 Published: 18 June 2003