Detailed Description

Mark was employed to lead the Siebel design and build of a new regulatory project that involved extending an existing Siebel implementation. Mark was responsible for analysing high level requirements, producing high level and detailed design documents, and managing/implementing the build.

FSCS had two separate Siebel implementations that had been live for many years and were in the process of merging these systems into one. This was a large project that had been running for a couple of years and was due to go live within the next few months. Meanwhile Mark's project was required to build upon one stream of the new system, starting before it went live but delivering sometime after. This would require a parallel development approach, with the usual challenges of keeping the development of the two streams in sync.

This was a particularly challenging project as there was very little information or resources available to explain the existing Siebel implementation that was due to be enhanced. The entire team for Mark's project were new to FSCS, hence there was no one on the team with any knowledge of the existing Siebel system. Additionally those working on the other Siebel project were under pressure to deliver and hence were unable to spare resources to assist Mark's team. This all combined to create a huge challenge in understanding the existing Siebel implementation and identifying the changes that would be required to support the new requirements.

These challenges were further enhanced by a set of requirements that had been gathered without any consideration of the existing system or that Siebel was the software used, and they also lacked a level of detail required to produce a detail design. Further analysis of the requirements was therefore needed before a design could be prepared, but given the focus throughout FSCS was on delivering the other Siebel project accessing business resources was a slow, sometimes impossible process.

Despite all these issues we were able to deliver a Siebel solution on time with almost no defects identified during the testing phases. Unfortunatley issues in other areas of the project delayed the overall go live date.

The Siebel version used at FSCS was Siebel Financial Services 8.1.1.6. The implementation centered around the Insurance Claims module and involved the use of workflows, scrpting, assignment manager, EIM, state model and general configuration. ADM was also used for the deployment of most non-repository items.