What is Siebel Views?
- Definition: Siebel Views are specific screens within Siebel CRM that display related data and functionalities.
- Access: Users gain access to these views through assigned Viewlists.
- Responsibility: Assigned responsibilities automatically authorize users to use corresponding views and products.
- Management: Crucial for managing user access and ensuring compliance.
Understanding Siebel Views and Their Importance
In Oracle Siebel CRM, a view represents a specific layout or screen designed for users to interact with data within the Siebel application. Each view organizes and displays data according to defined criteria, helping users efficiently perform tasks, access records, and execute business processes effectively.
Siebel’s views typically include:
- List Applets: For viewing and managing lists of records.
- Form Applets: For data entry or viewing detailed records.
- Charts and Dashboards: These are used to visualize performance data and reports.
For example, the Account List View allows users to see a list of customer accounts. Similarly, a Service Request View enables customer service agents to manage support tickets.
Standard Siebel Views
Standard views are pre-built by Oracle, available out-of-the-box, and included with Siebel CRM licenses. These views cover typical CRM processes and functionalities, such as:
- Account Management
- Opportunity Management
- Lead Tracking
- Service Requests
- Campaign Management
Because they come pre-configured, standard views significantly reduce implementation time and complexity.
Examples of standard Siebel views include:
- My Opportunities View: Lists sales opportunities assigned to the logged-in user.
- Service Request Detail View: Allows detailed tracking and management of individual service requests.
Custom Siebel Views and Why Organizations Need Them
While standard views address common business scenarios, organizations often require customized views to meet specific business processes, industry requirements, or unique workflow demands. These tailored views are known as custom views.
Custom views are developed to address specific organizational needs, providing flexibility and efficiency.
Common reasons to create custom views include:
- Specific Data Requirements: Organizations must display custom data fields not included in standard views.
- Workflow Efficiency: Improving productivity by organizing data specifically tailored to user roles.
- Industry-Specific Requirements: Unique compliance or data reporting needs (e.g., healthcare, financial services).
Examples of custom views include:
- A pharmaceutical company might require a custom view to manage detailed regulatory compliance data.
- A bank may create custom views for specialized customer credit checks that are not covered by Siebel’s standard financial views.
Licensing Implications of Siebel Views
Oracle Siebel licensing has specific implications related to standard and custom views. Licensing is typically based on the Application User model, which requires licensing each user authorized to access Siebel applications, regardless of how frequently they use it.
However, creating or accessing custom views can impact licensing requirements. Here’s what organizations must understand clearly:
Licensing Impact of Custom Views
Oracle licenses Siebel CRM primarily based on the number of application users. Customizing Siebel through additional views or custom configurations does not necessarily require additional licensing, provided that:
- All users accessing the custom views already have valid Application User licenses.
- Custom views do not use specialized functionality restricted under specific additional licensing.
However, additional licensing fees will apply if custom views incorporate specific advanced modules or licensed functionalities beyond the base Siebel CRM license.
Example:
If an organization creates a custom view utilizing Siebel’s Analytics or Marketing modules (which are not part of their base licensing), the organization must purchase additional licenses for all users accessing this custom view.
Understanding Siebel Licensing Metrics Clearly
Siebel CRM licensing primarily revolves around the metric known as Application User:
- Application User: Any individual authorized to use the licensed Siebel programs, regardless of whether they actively use the system.
- Each user accessing a custom view must have a valid license, ensuring full compliance.
Common Pitfalls and How to Avoid Them
Common pitfalls include:
- Unlicensed Customization: Creating custom views that access licensable modules not covered by existing licenses.
- User Count Miscalculations: Failing to account for all potential users who may access custom views, leading to unintentional license violations.
To avoid pitfalls:
- Document all custom views and their related Oracle modules.
- Regularly review which users require access to customized views.
- Periodically audit your Siebel deployment to verify license compliance.
Managing Siebel Views for License Compliance
Ensuring compliance in Siebel licensing requires proactive management. Organizations should follow clear best practices:
- Inventory Standard and Custom Views: Keep an updated inventory of all views, clearly identifying associated licensable modules.
- Access Control Management: Regularly review user permissions, ensuring only licensed users can access custom views requiring additional licensing.
- Regular Licensing Audits: Perform internal audits periodically to proactively identify and address potential licensing gaps.
Pricing for Oracle Siebel Licensing
Siebel CRM licensing has specific prices depending on base modules and industry-specific add-ons. Here are clear examples of Siebel CRM costs (list prices as of 2024):
- Siebel CRM Base Application: Approximately $3,750 per Application User.
- Industry Base Options: Additional licensing of approximately $400 per Application User for each specialized industry module (e.g., Financial Services, Communications, Public Sector).
Typical Annual Support Costs: Oracle’s Software Update License & Support (SULS) typically amounts to 22% of the original license fee annually.
Licensing Example:
If your organization has 100 users, your initial license costs for Siebel CRM Base would be:
- Base Siebel CRM License: 100 users x $3,750 each = $375,000
- Annual support (22%): $82,500 annually
If you add an industry-specific module such as Financial Services at $400 per user:
- Additional upfront licensing cost: $400 x 100 users = $40,000
- Additional annual support cost: 22% of $40,000 = $8,800 annually
Practical Recommendations for Managing Custom View Licensing Costs
To manage and minimize licensing costs effectively, organizations should consider the following best practices:
- Limit Custom Views: Create custom views only when necessary, using standard views whenever possible.
- License Optimization: Regularly review user activity to reduce unused licenses or modules, lowering ongoing licensing and support costs.
- Oracle Negotiations: For more favorable pricing, consider negotiating license fees and annual support fees during renewal periods or at Oracle’s fiscal quarter-ends.
Common Mistakes Organizations Make
Several common errors lead to licensing complications with Siebel views and customizations:
- Unclear Understanding of Licensing Metrics: Misunderstanding that licensing is based on potential users, not actual usage.
- Ignoring Customizations in Licensing Plans: Failing to include customizations that trigger additional licensing.
- Poor User Management: Allowing excessive or unintended user access to custom views, increasing the license requirement.
How to Avoid Licensing Issues with Siebel Views
To proactively manage compliance and reduce risks associated with Siebel licensing:
- Understand Licensing Metrics Clearly: Always verify licensing requirements before deploying custom views or modules.
- Perform Regular Reviews: Periodically audit all users and custom views to confirm compliance.
- Document and Control Customizations: Maintain thorough documentation of customizations and indicate associated licensing obligations.
- Centralize Administration: Ensure centralized management of all customizations, enforcing a formal process to authorize new views or modules.
Practical Steps to Manage Licensing for Custom Siebel Views
Implement the following practical best practices:
- License Assessment: Before creating new custom views, assess whether additional Oracle licenses are required.
- User Training: Ensure staff responsible for managing Siebel customizations understand Oracle’s licensing rules and implications.
- Internal Documentation: Document licensing entitlements and map these against custom views and actual user access.
- Regular Reconciliation: Regularly reconcile your Siebel licensing entitlements against your active user list to quickly spot and rectify licensing discrepancies.
Summary and Conclusion
Siebel CRM views, both standard and custom, form the backbone of user interaction within Siebel applications. While standard views typically require only base application licenses, custom views involve additional licensing considerations depending on the modules utilized.
Key considerations summarized clearly:
- Standard Views: Covered under Siebel CRM Base Application licenses.
- Custom Views: Additional licensing is required if features from previously licensed modules are leveraged.
- Pricing Overview: Base licenses cost roughly $3,750 per user, and industry-specific modules cost an additional $400 per user. Annual support typically accounts for 22% of the license cost.
- Proactive Management: Regularly audit custom views and user access rights to maintain compliance and reduce licensing costs.
Organizations significantly reduce the risk of unexpected licensing costs and Oracle compliance issues by thoroughly understanding Siebel’s views, clearly managing customizations, and carefully controlling access.
