Siebel Product Implementations

Should be :

• Based on supporting new and existing business process with a braod set if predefined functionality

1. Existing siebel capabilities can satisfy a wide range of implementation requirements

• Focused on leveraging product capabilities and minimizing custom configuration

Should not be :

• Approached as a software development project
• Initiated as an opportunity to gather and develop software features based on user with lists
• Attempted until you are familiar with the standard functionality for all entities being implemented

Two Ways to satisfy user requirements

• Modify the purchased application through configuration to :

1. Match currency legacy systems and processes
2. Meet all pertinent user requests that drive day-to-day business operations

• Modify current business to :

1. Leverage application functionality
2. Align with best-practice business processes

Impacts of the implementation approaches

• Modify the application
  

1. Should only be considered as a last resort
2. Should not exceed 20% of the purchased application functionality
   

• Modifying the business processes

1. Requires minimal modifications to application
   
2. Increases Productivity and reduces implementation time