19
Copyright © 2010. SYSTIME. All Rights Reserved. www.SYSTIME.net Consolidate EnterpriseOne to Regain control

Systime consolidate-enterprise one-to-regain-control

Embed Size (px)

DESCRIPTION

 

Citation preview

Page 1: Systime consolidate-enterprise one-to-regain-control

Copyright © 2010. SYSTIME. All Rights Reserved. www.SYSTIME.net

Consolidate EnterpriseOne to Regain control

Page 2: Systime consolidate-enterprise one-to-regain-control

Copyright © 2011. SYSTIME. All Rights Reserved.

Agenda

Understanding Instances

Challenges faced while consolidating

Approaches towards consolidation

Building a Global model

Page 3: Systime consolidate-enterprise one-to-regain-control

Understanding Instances

Page 4: Systime consolidate-enterprise one-to-regain-control

Copyright © 2011. SYSTIME. All Rights Reserved.

What’s your Stance on Instance Consolidation?

Instance refers to the unique set of JD Edwards EnterpriseOne data which includes transactional data, control tables and system data

Multiple instances are calling for your attention if you see these warnings

4

Increased Maintenance

Cost

Many parallel IT centers

Many ERP versions

Improper control

Highly Customized

Environment

Duplicate architecture

Disparate processes

Page 5: Systime consolidate-enterprise one-to-regain-control

Copyright © 2011. SYSTIME. All Rights Reserved.

So what’s your instance number??

5

Determine the right instance number

Page 6: Systime consolidate-enterprise one-to-regain-control

Copyright © 2011. SYSTIME. All Rights Reserved.

Multiple instances…multiply troubles

6

Multiple Instances

Organizational structure

Geographical distributions

Business Growth and Size

Planned maintenance or

upgrades

Performance

Warning Signs

Page 7: Systime consolidate-enterprise one-to-regain-control

Challenges

Page 8: Systime consolidate-enterprise one-to-regain-control

Copyright © 2011. SYSTIME. All Rights Reserved.

All said and done Instance Consolidation is not an easy task

8

Organizational structure

Process consistency

Localizations

Downtime requirements

System configurations

Security

CHALLENGES

Page 9: Systime consolidate-enterprise one-to-regain-control

Approaches

Page 10: Systime consolidate-enterprise one-to-regain-control

Copyright © 2011. SYSTIME. All Rights Reserved.

Global Instance: Multiple Instance Scenario Vs Single Instance Scenario

10

United States

Spain Canada

Taiwan Brazil Portugal

Benelux Thailand Mexico

France China India

Korea

Canada Taiwan Benelux

PortugalSpain

Mexico

Thailand United States

Brazil

India France Korea

China

Approach : 01 Instance : 01

In this approach, a single instance is created for all the countries in

the world

Page 11: Systime consolidate-enterprise one-to-regain-control

Copyright © 2011. SYSTIME. All Rights Reserved.

Global Instance – Pros and Cons

11

Cost Savings due to Optimum Architecture

High Standardization possible

Ease of Data Consolidation & Reporting

Ease of Integration

Centralized lean team for support

Pros

Higher demand on high availability and disaster recovery

Potential loss of performance due to growing user base and data

Perceived lack of flexibility and autonomy in localizations and other process variations

Cons

Page 12: Systime consolidate-enterprise one-to-regain-control

Copyright © 2011. SYSTIME. All Rights Reserved.

China

Regional Instances :Multiple Instance Scenario Vs Single Instance Scenario

12

Approach : 02

China

United States

Spain Canada

Taiwan Brazil Portugal

Benelux Thailand Mexico

France Korea India

Canada

BeneluxSpain

MexicoUnited States

Brazil

Instance : 01

In this approach, we create regional instances for countries

within that region

France

Portugal

India

Korea

Taiwan

Thailand

Instance : 02

Instance : 03

Instance : 04

Page 13: Systime consolidate-enterprise one-to-regain-control

Copyright © 2011. SYSTIME. All Rights Reserved.

Regional Instance – Pros and Cons

13

Optimum Architecture

Limited Standardization

Regional autonomy for localization and processes

Ease of Data Consolidation & simplified reporting

Higher Cost of Maintenance due regional IT staff

Regional influences hindering standardization of process

ConsPros

Page 14: Systime consolidate-enterprise one-to-regain-control

Building a Global Model

Page 15: Systime consolidate-enterprise one-to-regain-control

Copyright © 2011. SYSTIME. All Rights Reserved.

Canada Taiwan Benelux

PortugalSpain

Mexico

Thailand United States

Brazil

India France Korea

China

High Level Solution Approach

15

United States

Spain

Canada Brazil

Taiwan Portugal

Benelux Thailand

India

Mexico Korea

France China

Current Stage Future Stage

Assessment State

Planning Stage

Global Model Build

Rollout

Sunset multiple instances

Page 16: Systime consolidate-enterprise one-to-regain-control

Copyright © 2011. SYSTIME. All Rights Reserved.

How to build a global model?

16

SYSTIME Global Model Composition

MethodologyStandards

Governance Framework

Data Standards

Naming Convention Standards

SecurityStandards

Global Custom Code

GLOBAL MODEL

LOCAL MODEL

Documentation Standards

SYSTIME follows 80:20 thumb rule while defining global model Considers buying in from business community from all regions of the world while designing global modelConducts workshop for identifying common processes across regionsIncorporates solid governance structure for modifying or changing global model

Page 17: Systime consolidate-enterprise one-to-regain-control

Copyright © 2011. SYSTIME. All Rights Reserved.

Components of Global Model

17

Complexity

Low Medium High

Diagram shows what are the different components of global Model and their line items in each component. Depending on the requirementof customer, model can be simple or complex based on the line items included in it. In some of complex scenarios, global Model includesorganization level custom code.

Naming ConventionStandards

Standard Processes Methodology & Documentation

Security Matrix Data Standards Custom Code

Company NumbersCost Center or Business Units etcSecurity Role NamesItem NumbersVersion NamesDocumentation Names

Standard Enterprise ProcessesLocal ProcessesSleeper Processes

Rollout MethodologyTemplatesChecklistsAA

Definition of RolesDefinition of Tasks

Data DictionaryConstantsCOA/BU’sCategory code valuesAlternate chart of account codesFiscal PatternsCurrency CodesDocument typesUDC’sPayment TermsEnterprise Offsets/Item ClassesAAI’s/DMAAI’sFA ClassesItem MasterCosting Methods

Enterprise Custom CodeEnterprise Custom Documentation

(1) Naming Convention Standards (3) Methodology & Documentation

(2) Standardization of Processes (4) Security Standardization

(5) Data Standardization

(6) Building Custom Codes

Page 18: Systime consolidate-enterprise one-to-regain-control

Copyright © 2011. SYSTIME. All Rights Reserved.

Additional Collateral

SYSTIME’s podcast series on JD Edwards EnterpriseOne Instance Consolidation

Building the case for instance consolidation

Understanding challenges to eliminate them

Approach through a single global instance

Approach by prioritizing geographical proximity

SYSTIME's Pre Rollout assessment pack helps you plan

White paper

JD Edwards Instance Consolidation Assessment Pack

18

Page 19: Systime consolidate-enterprise one-to-regain-control

“The contents of this document are proprietary and confidential to SYSTIME Global Solutions Private Ltd. and may not be disclosed in whole or in part at any time, to any third party without the prior written consent of SYSTIME Global Solutions Private Ltd.”

“© 2011 SYSTIME Global Solutions Private Ltd. All rights reserved.

Thank You

19