1. M ARCH 2004 Day 2 Interface Developme nt

2. Technical Workshop 2 MondayTuesdayWednesdayThursdayFriday Welcome and Overview GS/LIS (Cont.) Interface Development Interface Testing (Cont.) Local Testing Technical Introduction Global T&EDatafeeds Conversion Testing Technical Migration Implementation Technical Deployment Overview Conversion Development Interface Testing Break-out Discussion Groups Next Steps GS/LIS Technical Workshop Where We Are, Where We’re Going…

3. Technical Workshop 3 Learning Objectives  Identify the scope of interfaces  Identify GF interface requirements  Describe GF interface processing  Locate and apply sources for interface design documentation  Complete a local practice interface usage profile  Update system diagram  Identify the scope of interfaces  Identify GF interface requirements  Describe GF interface processing  Locate and apply sources for interface design documentation  Complete a local practice interface usage profile  Update system diagram

4. Technical Workshop 4 Overview of Interfaces

5. Technical Workshop 5 Datafeeds vs. Interfaces Datafeeds are not the same as Interfaces  Interfaces  Used by Local Systems for Validations  Have Business Rules built into them  Have Critical Interdependencies between them  Are about the Present and Future  Code block is not shifted  Datafeeds  Designed primarily to support out of scope downstream applications  Code block is shifted on data sourced from Engagement Reporting and Datamart  On cycle close, data is as of the cycle close until the batch process is complete Datafeeds are not the same as Interfaces  Interfaces  Used by Local Systems for Validations  Have Business Rules built into them  Have Critical Interdependencies between them  Are about the Present and Future  Code block is not shifted  Datafeeds  Designed primarily to support out of scope downstream applications  Code block is shifted on data sourced from Engagement Reporting and Datamart  On cycle close, data is as of the cycle close until the batch process is complete

6. Technical Workshop 6 Interface Technologies  SSH  Unicode  XML  EDI/Flat files  SSH  Unicode  XML  EDI/Flat files

7. Technical Workshop 7 Global HR Repository Interface

8. Technical Workshop 8 Interfacing To/From Local Systems: High-Level Overview LOCAL SYSTEMS Local IN CURRENCY PROVIDER DB LOCAL BANK COMMUNICATIONS SOLUTIONS LOCAL BANK COMMUNICATIONS SOLUTIONS LOCAL BANK LOCAL BANK Interface GLOBAL HR REPOSITORY GLOBAL HR REPOSITORY CHECK PRINTING SYSTEMS CHECK PRINTING SYSTEMS (2) ORGS TO LOCAL (3) EMPLOYEE INFO (4) ENGAGEMENTS TO LOCAL (5) TIME/EXPENSE (6) EDI (7) BANK INFORMATION (8) BATCH & JET UPLOADS (7) BANK INFORMATION Local OUT INBOUND BANK INFORMATION AP VENDOR VOUCHER PAYROLL FIXED ASSETS* PURCHASING HUMAN RESOURCE SYSTEMS TIME & EXPENSE SYSTEMS *Currently under discussion and subject to change PAYROLL TO IMPREST

9. Technical Workshop 9 Global HR Repository Interface Topics  Overview of Global HR Repository  Glossary of terms  Business design requirements  Interface transmissions  GHR interface files  Overview of Global HR Repository  Glossary of terms  Business design requirements  Interface transmissions  GHR interface files

10. Technical Workshop 10 Overview – Global HR Repository

11. Technical Workshop 11 Overview – Global HR Repository  Employee HR data is needed in GF to:  Provide information needed for financial calculations in EMS  Validate time submissions  Support expense reimbursements  Provide standard hours to support revenue calculations and utilization reporting  Employee HR data is needed in GF to:  Provide information needed for financial calculations in EMS  Validate time submissions  Support expense reimbursements  Provide standard hours to support revenue calculations and utilization reporting

12. Technical Workshop 12 Glossary of Terms  Local Personnel Number (LN)  Assigned by the member firm  Unique within the member firm  May be used to build GN Global HR Repository sends this ID back along with GN and GUI to each managerial country.  Local Personnel Number (LN)  Assigned by the member firm  Unique within the member firm  May be used to build GN Global HR Repository sends this ID back along with GN and GUI to each managerial country.

13. Technical Workshop 13 Glossary of Terms  Global Unique Identifier (GUI)  Unique global identifier that will follow the person across all managerial countries  Each managerial country will be given a range of numbers for assigning GUI  Managerial country must verify existence of GUI for personnel hired from other E&Y firms to ensure uniqueness  Global Unique Identifier (GUI)  Unique global identifier that will follow the person across all managerial countries  Each managerial country will be given a range of numbers for assigning GUI  Managerial country must verify existence of GUI for personnel hired from other E&Y firms to ensure uniqueness

14. Technical Workshop 14 Glossary of Terms  GLL Summary:  GLL Summary: Local country systems Local country systems, GHR Local countryLPN GHRGHR, GFLocal countryGUI GFGHR, GFGHRGN Used as unique identifier in Used inGenerated byIdentifier

15. Technical Workshop 15 Business Design Requirements  The local systems will send XML files containing required and optional data elements for GF, Global Directory, and Global HR.  All inbound files are to conform to GIS standards.  The local systems will send XML files containing required and optional data elements for GF, Global Directory, and Global HR.  All inbound files are to conform to GIS standards.

16. Technical Workshop 16 GHR Interface Summary  Global HR Repository:  Stores employee data for all member firms  Is the main source of HR data for global applications  Uses the employee identifiers GPN, LPN, and GUI  Employee HR data is needed in GF to:  Provide information needed for financial calculations in EMS  Validate time submissions  Support expense reimbursements  Provide standard hours to support revenue calculations and utilization reporting  Global HR Repository:  Stores employee data for all member firms  Is the main source of HR data for global applications  Uses the employee identifiers GPN, LPN, and GUI  Employee HR data is needed in GF to:  Provide information needed for financial calculations in EMS  Validate time submissions  Support expense reimbursements  Provide standard hours to support revenue calculations and utilization reporting

17. Technical Workshop 17 Employee Data Process Flow Diagram Global HR Repository GF Local GNs Loading Program Std Hours Feed EMS Feed Errors and Warnings Global Interface Staging Employee Data Flow Diagram Org Structure Org Structure and Rank Local Systems Errors and Warnings Daily EMS & AP Employee Data Feed Errors and Warnings Local GNs AP Feed Weekly Stdhrs Employee Data Feed

18. Technical Workshop 18 Employee Data Process Flow  Local HR  Global Interface Staging  Global HR Repository  Local HR  Global Interface Staging  Global HR Repository

19. Technical Workshop 19 Global HR Repository Dependencies  Initial steps during GF technical migration:  Local practice has fully integrated GHR and has been receiving employee crosswalk files  Local practice configuration and conversion data resides in GF  Local practice receives Orgs to Local interface  Local practice locally assigns employees to valid orgs  GHR sets local practice to “In GF”  Local practice submits new employee org assignments to GHR  GHR communicates employee org info to GF  Initial steps during GF technical migration:  Local practice has fully integrated GHR and has been receiving employee crosswalk files  Local practice configuration and conversion data resides in GF  Local practice receives Orgs to Local interface  Local practice locally assigns employees to valid orgs  GHR sets local practice to “In GF”  Local practice submits new employee org assignments to GHR  GHR communicates employee org info to GF

20. Technical Workshop 20 Orgs to Local Systems Business Purpose – Components  Fourteen files are created by the Orgs to Local Process:  Industry File  Org Crosswalk File  Translate Values File  Reporting Attributes File  Source to Account  Service Codes  VAT Codes  Closed BU File  Ranks File  Orgs File  Countries File  States File  Currencies File  Calendar File  Closed BU File  Ranks File  Orgs File  Countries File  States File  Currencies File  Calendar File