MARCH 2004

Day 2

Interface Develop

ment

Interface Develop

ment

2

Technical Workshop

Monday Tuesday Wednesday Thursday Friday

Welcome and Overview

GS/LIS (Cont.)Interface

Development

Interface Testing (Cont.)

Local Testing

Technical Introduction

Global T&E DatafeedsConversion 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…Where We Are, Where We’re Going…

3

Technical Workshop

Learning ObjectivesLearning 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

Overview of InterfacesOverview of Interfaces

5

Technical Workshop

Datafeeds vs. InterfacesDatafeeds 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

Interface TechnologiesInterface Technologies

SSH Unicode XML EDI/Flat files

SSH Unicode XML EDI/Flat files

7

Technical Workshop

Global HR Repository InterfaceGlobal HR Repository Interface

8

Technical Workshop

Interfacing To/From Local Systems: High-Level Overview

Interfacing To/From Local Systems: High-Level Overview

LOCAL SYSTEMSLOCAL SYSTEMS

Local IN

CURRENCY PROVIDERCURRENCY PROVIDER DBDB

LOCAL BANKCOMMUNICATIONS

SOLUTIONS

LOCAL BANKCOMMUNICATIONS

SOLUTIONS

LOCALBANK

LOCALBANK

InterfaceInterface

GLOBAL HRREPOSITORYGLOBAL 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) B

AN

K IN

FO

RM

AT

ION

Local OUT

INBOUND BANK INFORMATIONINBOUND BANK INFORMATION

AP VENDOR VOUCHERAP VENDOR VOUCHER

PAYROLLPAYROLL

FIXED ASSETS*FIXED ASSETS*

PURCHASINGPURCHASING

HUMAN RESOURCE SYSTEMSHUMAN RESOURCE SYSTEMS

TIME & EXPENSE SYSTEMSTIME & EXPENSE SYSTEMS

*Currently under discussion and subject to change

PAYROLL TO IMPREST

9

Technical Workshop

Global HR Repository Interface TopicsGlobal 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

Overview – Global HR RepositoryOverview – Global HR Repository

Global Directory

GF

Global HR Repository

Organization Structure and

List of Global Values

Country 1

Global Interface Staging (GIS)

•Global HR List of Values•Error Files•GPN Crosswalk Files

Other Applications

Country 2

Country n

11

Technical Workshop

Overview – Global HR Repository 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

Glossary of Terms Glossary of Terms

Local Personnel Number (LN)Assigned by the member firmUnique within the member firmMay 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 firmUnique within the member firmMay be used to build GN

Global HR Repository sends this ID back along with GN and GUI to each managerial country.

13

Technical Workshop

Glossary of Terms 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

Glossary of Terms 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

Business Design RequirementsBusiness 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

GHR Interface SummaryGHR 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

Employee Data Process Flow DiagramEmployee Data Process Flow Diagram

Global HR Repository

GF

Local GNs Loading Program

Std Hours FeedEMS

Feed

Errors and

Warnings

Global Interface Staging

Employee Data Flow Diagram

Org Structure

Org Structure and Rank

Local Systems

Local Systems

Local Systems

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

Employee Data Process FlowEmployee Data Process Flow

Local HR Global Interface Staging Global HR Repository

Local HR Global Interface Staging Global HR Repository

19

Technical Workshop

Global HR Repository DependenciesGlobal 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

Orgs to Local Systems Business Purpose – Components

Orgs to Local Systems Business Purpose – Components Fourteen files are created by the Orgs to Local Process: 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

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