Mark returned once again as the development team lead for the Siebel Marketing element of this project. Following the implementation of phase 1 it was clear that there were quality issues in the development processes. Mark was then brought in to introduce a number of quality control measures to ensure the problems encountered in phase 1 were not repeated in phase 2. These measures included introducing configuration guidelines, unit testing procedures, detailed design documentation, procedures for monitoring work carried out and tighter management over the development team.

The implementation of the Marketing application was divided into three sub projects for Phase 2. Intended to present the progress to the client in stages it resulted in three separate rounds of design and build, working to very tight timescales. This phase included configuration around the campaign modules and the use of campaign lists, as well as integration with Siebel Analytics and other client systems.

The use of Siebel Analytics meant that Siebel was to be used as a staging point for large volumes of data coming from several client systems, including their mainframe and a separate data warehouse. Informatica was used to load the Siebel EIM tables with data from the other client systems, and to load the Analytics tables, once EIM had imported the data into the Siebel base tables. The whole process of getting significantly large volumes of data from third party client systems through to Siebel Analytics, via the Siebel base tables on a daily basis proved a major challenge.