Program Mercury Latest Scenario January 2014

1. Program MercuryLatest ScenarioJanuary 2014

2. Narrative Storyboard

3. Narrative • Peter, who is a Partner in the EY German practice, identifies a customer transformation opportunity, for a new BMW plant in Germany. Peter creates this new plant as a prospect in EY’s CRM system. He then logs the opportunity in the system. Soon after identifying the opportunity, Peter prepares a proposal for the BMW prospect, supported by an initial pricing plan in MMT. In addition, Peter also completes the GTAC assessment for the prospect and opportunity in order to confirm that EY can perform the planned work. • After the final proposal meeting, BMW informs Peter that they would like to proceed with EY. A slightly different final pricing amount is agreed upon with the client than what was proposed and an ‘SOW’ is signed between BMW Germany and EY Germany. Peter updates the sold-at price to reflect the new fee. • After evaluating the scope of the work, Peter realizes that he needs to involve an EY team based in Austria to complete a part of the work. Peter calls Marc (EY Partner based in Austria) and agrees to work together on completing this engagement. In order to effectively manage the project, Peter and Marc agree that they each would need to create a detailed budget and manage their resources separately. From a fee sharing perspective, Peter and Marc agree to share fees based on actuals. Since the client is based in Germany and had also indicated they would like a consolidated bill (in the SOW), a combined bill will need to be sent from EY Germany to the client. • Peter opens the engagement for the work to be performed in Germany. Similarly, Marc also opens an engagement for the work to be performed by the EY team in Austria (after confirming that the GTAC performed in Germany can be used). Peter and Marc assemble their teams and begin executing on the engagements. The team members charge their respective engagements and complete the work on time. Peter prepares a combined invoice and sends that to the client. • The invoice exceeded the payment due date allotted. Five days later, Dunning and Collection’s actions commence. Based on the client’s score, actions taken over the next two months were 2 emails, then 2 letters, then 1 call and finally after 75 days, escalation to Peter. Peter is able to review the actions and see the escalation flag in My Engagements. Using links in My Engagement, he’s able to record the actions he personally takes to recover the debt. • When the final billing has been issued, Peter and Marc change the engagement status to ‘PreClosing’.

4. Mercury Client Server Journey Complete When the final billing has been issued, Peter and Marc change the engagement status to ‘PreClosing’ The teams do the work and charge their time and expense Peter and Marc review budget to actual and update their Estimate to Complete A GTAC Assessment is performed on the client and engagement Peter and Marc each create a detailed budget for their respective engagements BMW Peter enters the new German BMW plant as a prospect and logs the opportunity in CRM Peter updates the sold-at price in MMT BMW Peter sends a combined invoice to BMW Austria Team Germany Team Dunning and Collections perform collections of invoice payments. Invoice payments exceeded their due dates so Dunning and Collections notify Peter to take actions Peter signs the SOW but at a slightly different pricing amount Teams are assembled by the Resource Managers Peter creates the initial pricing plan Peter and Marc each create a detailed budget for their respective engagements

5. Process / Visualization Flow 4 1 2 3 5 • User reviews engagement details for any action on collections. • System: My Engagement / SharePoint Forms Dunning & Collections • Users create engagements • System: CRM/SAP PPM • Users send resource requests. • System: PPM Create Engagements Send Resource Request • User creates a prospect • System: CRM On Cloud • User creates Opportunity Header and line item and edits Pursuit Team • System: CRM On Cloud • User creates pricing plan at ‘sold at’ level • System: MMT • Proposal meeting • A SOW is signed with a reduced Sold at price • Non System step • Users create detailed engagement budgets • System: MMT • User performs acceptance • System: GTAC • User review engagement economics • System: My Engagement • User performs billing • System: Custom • Users review their financial Metrics • System: MMT • User changes status of the opportunity to ‘Won’ • System: CRM on Cloud • Users charge time & expense • System: CATS / Expense • User updates pricing plan and locks it as the final ‘sold at’ value • System: MMT Review Metrics and Approve Budget Create Prospect Create Pricing Plan (Sold at level) Update Opportunity Details • User moves project status to ‘’PreClosing’ • System: PPM Perform Acceptance Manage Engagement Economics Create Opportunity header/line item Create Planned at Budgets Charge T&E Initiate and Perform Billing Proposal and ‘SOW’ Signoff Update Pricing Plan (Sold at level) Close Engagement √ Peter √ Peter √ Peter √ Peter √ Peter Peter Peter & Marc √ √ √ √ √ √ Peter Peter Peter √ √ Peter Peter √ Start End 6 8 9 10 7 11 • User schedules resources • System: MRS Schedule Resources Scheduler Peter & Marc Peter & Marc √ √ 13 15 17 12 16 14 Client Servers √ Peter & Marc