Systime consolidate-enterprise one-to-regain-control
Upcoming SlideShare
Loading in...5
×
 

Like this? Share it with your network

Share

Systime consolidate-enterprise one-to-regain-control

on

  • 907 views

 

Statistics

Views

Total Views
907
Views on SlideShare
907
Embed Views
0

Actions

Likes
0
Downloads
8
Comments
0

0 Embeds 0

No embeds

Accessibility

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Systime consolidate-enterprise one-to-regain-control Presentation Transcript

  • 1. Consolidate EnterpriseOne to Regain controlCopyright © 2010. SYSTIME. All Rights Reserved. www.SYSTIME.net
  • 2. Agenda Understanding Instances Challenges faced while consolidating Approaches towards consolidation Building a Global model Copyright © 2011. SYSTIME. All Rights Reserved.
  • 3. Understanding Instances
  • 4. 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 Increased Maintenance Cost Disparate Many parallel processes IT centers Duplicate Many ERP architecture versions Highly Improper Customized control Environment Copyright © 2011. SYSTIME. All Rights Reserved. 4
  • 5. So what’s your instance number?? Determine the right instance number Copyright © 2011. SYSTIME. All Rights Reserved. 5
  • 6. Multiple instances…multiply troubles Business Growth and Size Planned Geographical maintenance or distributions upgrades Organizational Multiple Performance structure Instances Warning Signs Copyright © 2011. SYSTIME. All Rights Reserved. 6
  • 7. Challenges
  • 8. All said and done Instance Consolidation is not an easy task Organizational structure Process Security consistency CHALLENGES System Localizations configurations Downtime requirements Copyright © 2011. SYSTIME. All Rights Reserved. 8
  • 9. Approaches
  • 10. Global Instance: Multiple Instance Scenario Vs Single Instance Scenario Approach : 01 Instance : 01 United Taiwan Spain Canada Canada Benelux States Spain Taiwan Brazil Portugal Portugal Mexico ChinaBenelux Thailand Mexico Korea Thailand United Brazil States France China India India France Korea In this approach, a single instance is created for all the countries in the world Copyright © 2011. SYSTIME. All Rights Reserved. 10
  • 11. Global Instance – Pros and Cons Pros Cons Cost Savings due to Optimum Higher demand on high Architecture availability and disaster recovery High Standardization possible Potential loss of performance Ease of Data Consolidation & due to growing user base and Reporting data Ease of Integration Perceived lack of flexibility and autonomy in localizations Centralized lean team for and other process variations support Copyright © 2011. SYSTIME. All Rights Reserved. 11
  • 12. Regional Instances :Multiple Instance Scenario Vs Single Instance Scenario Instance : 01 Instance : 02 Approach : 02 United Canada Mexico States United Spain Canada States Brazil Instance : 03 Taiwan Brazil Portugal Spain Benelux PortugalBenelux Thailand Mexico France Instance : 04 France Korea China India India China Taiwan Korea Thailand In this approach, we create regional instances for countries within that region Copyright © 2011. SYSTIME. All Rights Reserved. 12
  • 13. Regional Instance – Pros and Cons Pros Cons Optimum Architecture Higher Cost of Maintenance due regional IT staff Limited Standardization Regional influences hindering standardization of process Regional autonomy for localization and processes Ease of Data Consolidation & simplified reporting Copyright © 2011. SYSTIME. All Rights Reserved. 13
  • 14. Building a Global Model
  • 15. High Level Solution Approach Current Stage Future Stage Assessment State United Spain Canada Taiwan Benelux States Planning Stage Canada Brazil Spain Portugal Mexico Global Model Build China Taiwan Portugal Thailand United Brazil RolloutBenelux Thailand States Mexico Korea Sunset multiple India France Korea instances France China India Copyright © 2011. SYSTIME. All Rights Reserved. 15
  • 16. How to build a global model? SYSTIME Global Model Composition LOCAL Global Security Custom MODEL Standards Code Naming Convention Standards Data Standards Documentation Standards Governance Framework Methodology GLOBAL MODEL 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 model Conducts workshop for identifying common processes across regions Incorporates solid governance structure for modifying or changing global model Copyright © 2011. SYSTIME. All Rights Reserved. 16
  • 17. Components of Global Model Complexity Low Medium High(1) Naming Convention Standards (3) Methodology & Documentation (5) Data Standardization(2) Standardization of Processes (4) Security Standardization (6) Building Custom CodesNaming Convention Standard Processes Methodology & Security Matrix Data Standards Custom CodeStandards DocumentationCompany Numbers Standard Enterprise Rollout Methodology Definition of Roles Data Dictionary Enterprise CustomCost Center or Processes Templates Definition of Tasks Constants CodeBusiness Units etc Local Processes ChecklistsAA COA/BU’s Enterprise CustomSecurity Role Names Sleeper Processes Category code values DocumentationItem Numbers Alternate chart ofVersion Names account codesDocumentation Fiscal PatternsNames Currency Codes Document types UDC’s Payment Terms Enterprise Offsets/Item Classes AAI’s/DMAAI’s FA Classes Item Master Costing MethodsDiagram 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. Copyright © 2011. SYSTIME. All Rights Reserved. 17
  • 18. 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 SYSTIMEs Pre Rollout assessment pack helps you plan White paper JD Edwards Instance Consolidation Assessment Pack Copyright © 2011. SYSTIME. All Rights Reserved. 18
  • 19. Thank You“The contents of this document are proprietary and confidential to SYSTIME Global Solutions PrivateLtd. and may not be disclosed in whole or in part at any time, to any third party without the priorwritten consent of SYSTIME Global Solutions Private Ltd.”“© 2011 SYSTIME Global Solutions Private Ltd. All rights reserved. 19