The document summarizes various services provided by an expert "Siebel doctor" to assess and improve the health of a Siebel system. The doctor can perform: 1) A general health check of the Siebel configuration to identify issues like excessive complex scripts, technical debt, and poor configuration quality. 2) A performance tuning assessment to optimize response times and identify top performance issues. 3) A Siebel data archiving review to determine what old or inactive data can be safely archived to improve system performance and reduce storage costs.

1. Idea Port Riga
Siebel at the Doctor’s Office

2. • General health check
– Configuration
• Cardiology
– Performance tuning
• Fitness
– IPR Siebel Archiving
Your Siebel doctor

3. General health check (Configuration)
• Do we think about our
health only when something
hurts?
• Top issues revealed:
– Too many complex scripts
– Technical debt
– Configuration quality
• Misinterpreted requirements

4. • “The best code is the
code you don’t write”
• Workflows:
– Can be changed without
deployment
– Easy to see logic
– Hard to write complex
processing over multiple BC
(create Business Service
and call from WF)
Complex scripting
Script
Lines ~ 1`500
A4 Pages ~ 25

5. • Developers create it, but
why?
– Adapt new code to the
existing style and quality
– Time pressure
• Good technical debt
– When in need to quickly
prototype or push for a result
– Needs to be rewritten
• Cleaning up old debt
– Initially that will slow down
the development
Technical debt (poor maintainability)
Time
Velocity
Good code
Quick and dirty

6. • Ensure that configuration
guidelines are up-to-date and
followed
• Establish a single and consistent
logging framework
• Perform regular reviews
– Identify areas you want to focus on
– Automatic configuration checks
Configuration quality

7. • Reveals and tracks the
quality of code
• In-depth Siebel knowledge
isn’t required to use it
• Reports provided
– To see current status
– To check dynamics over time
• ~30 different checks for
eScript and configuration
IPR Review Tool

8. • Development teams want
to see requirements, not
solutions
– We can propose solutions
• Moving towards agility
– Validate smaller increments
Misinterpreted requirements

9. • For how long are we
prepared to wait?
– For data to appear on
screen the
– To move to a next step
after a button is pressed
• How fast is enough?
– How slow is too much?
• Everything could be made
faster, but is it worth it?
Cardiology (Performance)

10. • What response time you
expect for a function?
• What amount of data you
have now, and what is
the predicted growth?
• It is easy to gain 20%
– All of it will have to be
rewritten in order to
increase performance
10 times
Provide information to developers
Frequency of use
Performance
optimization

11. • Identify top performance
issues faced every day
• Review logs to identify
issue(s)
– Hard to estimate timeframe
– Usually <5 days
• Suggest possible fixes
You know what is slow

12. • Component available in
Siebel for Monitoring
• Need to gather data
• Analyze results and
monitor changes
SARM (Siebel Application Response Measurement)

13. • How old is the data that
you need to make
everyday decisions?
• Do employees really need
all of the stored data?
• Do you need old data in
Siebel, or DWH is enough?
• Does the old data slow
system down?
Fitness (Siebel Data Archiving)

14. • An option with access
– Archive to new tables
– Create new Table, BC, etc. in
Siebel to access tables
– New archive views are
introduced
• An option without access
– Move archived data to
archive database, or delete it
– Archived data remains in
DWH
Do you still want access?
Siebel
Existing views
New
Views
Siebel
DB
Archive
DB

15. • Identify entities that will
let you gain the most
from archiving
• Work with Business units
to decide, which data
they need to have
• Opportunity: 80%
– Inactive
– Older that 1 year
• Activity: 40%
– Older than 3 years
• Orders: 75%
– Complete
– Older than 2 years
Decide what data to archive

16. • We run a report and
identify, which physical
tables contain the data
• Communicate with DWH
to agree on the approach
• Archiving rules are
reviewed and adjusted
• Provide reports, when
process has been
executed
Execute Archiving – IPR Siebel Archiving solution

17. Thank you