Situation
A membership organization needed Siebel to run events, pricing, and partner access, and later needed .NET services to calculate tax and move transactions back into Siebel.
Past engagement · Siebel CRM
Siebel membership pricing, then .NET, WCF, and SharePoint
Past work at CFA Institute across two periods: Siebel for events, pricing, and integrations, then .NET, WCF, and SharePoint beside that CRM.
Past engagements · CFA Institute · 2004–2010 and 2013–2014
Past engagement, not a current employer.Named for the kind of work. This page does not add a percentage, a dollar figure, or a result that was not in the record of the work.
Outcome
Siebel was configured for eCustomer, eChannel, asset-based ordering, and EIM. Later work added WCF, WebAPI, and SharePoint changes around quotes, orders, and submissions. Neither period is a current role.
CFA Institute, in Charlottesville, was two past stretches of work. Neither is current.
From 2004 to 2010 the work was Siebel and .NET as a lead systems analyst. Siebel eCustomer let authorized contacts register for events. eChannel let partners work with service requests, contacts, activities, and events. Multi-organization visibility covered contacts, accounts, and events. Pricing workflows, variable maps, and order-management signals were changed to use custom discount matrices. Asset-based ordering workflows treated a membership as the asset. EIM jobs brought legacy CRM data into Siebel base tables. Outbound web services, workflow policies, and database triggers fired when key data changed. A .NET web service synchronized contact, account, order, payment, and deposit information with a Great Plains financial system. eScript business services and runtime events carried logic that configuration alone would not.
From April 2013 to September 2014 the work was Siebel, .NET, and SharePoint. Quotes and orders created in Siebel Financial eCustomer and Call Center called a WCF service, written in C#, that returned tax amounts onto the line items. A separate path accepted a vendor REST call into WebAPI, wrote to MSMQ, and had a WCF service call an inbound Siebel web service to update the transaction. SharePoint web parts were changed so a submission could not be duplicated inside a set window. An MVC application was extended around that stack.
The Siebel half of this belongs with Siebel CRM. The service half belongs with .NET applications.
Related practice: Siebel CRM
Other examples
- Curio — iOS development
- Siebel 7.8 to IP2014, with Open UI and AWS environments — Siebel CRM
- Public Sector case management for a state attorney general — Siebel CRM
- VB6, AngularJS, and WebAPI in the automotive aftermarket — .NET applications
- Two Siebel views, one order — Siebel CRM
- The billing app only one person could change — .NET applications
- Drafts beside the CRM, not a new system of record — AI consulting
If the system matters and the team is small, start with a conversation.
A paragraph on the system, the constraint, and the timing is enough. Jon reads these. There is no intake desk.