Services
Siebel CRM
Get a Siebel system back to something a small team can run and change.
Configuration, upgrades, workflow, and the integrations around Siebel. For internal IT groups that inherited an instance and do not have a bench of Siebel developers.
When that path has to land in more than one environment, the release steps are part of the same project. Ansible, Terraform, and a GitHub Actions or GitLab CI pipeline are how a patch stops being a manual weekend. That stays with the Siebel work. It is not a separate DevOps practice. See Build automation & IaC.
Who it is for
- A Siebel admin who is also the person on the incident bridge, the integration, and the next upgrade.
- A team facing an upgrade that has been postponed because nobody can say what will break.
- Operators whose users keep a spreadsheet because a Siebel view and a downstream system disagree.
What the work includes
Public Sector and case management
Siebel Public Sector configured into a case system people will actually use: the screens, the process, and the legacy data that has to come with it. Past work includes a state attorney general’s office. That role ended in 2023.
Open UI
Presentation models, physical renderers, and plug-in wrappers where browser script used to hold the business rule. Includes the form applets that render wrong after an upgrade, and a performance pass across browsers, network traffic, and the SQL underneath.
Upgrades with a version path
Not a weekend. Past paths include Siebel 16 to 20.11 to 22.1 to 23.2, and an older 7.8 to IP2014 upgrade. Repository, Open UI, integrations, and a test pass the client’s team can finish.
Workflow, eScript, and pricing
Workflow processes and policies, runtime events, and eScript business services. Asset-based ordering, pricing workflows, discount matrices, and the order-management signals that have to agree with them.
EIM, EAI, and web services
EIM jobs for legacy loads. Inbound and outbound web services, integration objects, and the workflow a failed message actually stops in. External business components when the data should stay where it is.
Data quality, Office 365, and hosted environments
Oracle Enterprise Data Quality and Loqate address standardization. Siebel Server Sync for Office 365. Development environments hosted on AWS when the project needs a place to build before production hardware is ready. Performance tuning against the database, not a new logo on the same slow view.
How an engagement starts
Most Siebel work starts with one painful path: a case view lawyers will not trust, an Open UI screen that got slower, an upgrade date that is already on a slide. Past engagements have included Akamai’s 7.8 to IP2014 upgrade, a short Open UI performance review at PNC, membership and pricing work at CFA Institute, and public-sector case management. We name the path in front of you, find where Siebel and the surrounding systems diverge, and only then decide whether the change is configuration, an integration, or a decision to leave something alone.
If Siebel CRM is the project, send a paragraph.
Name the system, what is stuck, and any date that already exists. That is enough to tell whether this practice is the right one.