1 / 9

Case Study: How the Scotts Company Increase Systems Performance

Case Study: How the Scotts Company Increase Systems Performance. Jeannie Shimer Director, Platform Services The Scotts Company. The Scotts Company Overview. The world’s leading producer and marketer of products for do-it-yourself lawn care and gardening and professional horticulture.

muniya
Download Presentation

Case Study: How the Scotts Company Increase Systems Performance

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Case Study: How the Scotts Company Increase Systems Performance Jeannie Shimer Director, Platform Services The Scotts Company

  2. The Scotts Company Overview • The world’s leading producer and marketer of products for do-it-yourself lawn care and gardening and professional horticulture. • Brand include Scotts, Miracle-Gro, Ortho, Roundup, Osmocote and Hyponex. • Core business (North America- United States & Canada): • Consumer Lawns & Growing Media • Consumer Gardens & Controls • Professional Nursery/Greenhouse • Scotts LawnService (U.S. only) • Lawn Care, Tree & Shrub Care, Disease and Pest Control • Europe and Rest-of-world • Consumer Lawns, Growing Media, Gardens & Controls • Professional Nursery/Greenhouse

  3. Major Project Initiatives for 2002 for Scotts • Replacement of all Sun Systems with new Sparc III technology • Upgrade from R/3 4.0B to 4.6C - Production • 4.6C European Implementation • Upgrade from BW 2.1C to 3.1C – In process, SAP Ramp-up Program • HR/IS 4.6C on Decoupled System – In Process • EBP 3.5 – SRM Ramp-up Program – In Process • CRM 3.0 – CRM Analyticals – Blueprint Stage • EP 5.0 – Enterprise Portal to support all SAP Systems • EDI Gentran Upgrade • Manugistics Implementation

  4. SAP R/3 Production Environment before migration • 2 SUN Enterprise 6500’s. DB 16x16. CI 12x12. Veritas Cluster for High Availability. • 2 SUN Enterprise 4500’s, Application Servers • 4 SUN Enterprise 420R’s, Application Servers • 13 Total Application Instances • SAP 4.0B 64bit • Oracle 8.1.7.3 64bit • Solaris 8 • Gigabyte Backbone

  5. SAP R/3 Production Environment after migration • 2 SUN Fire 4800’s. DB 8x16. CI 8x16. Veritas Cluster for High Availability. • 3 SUN Fire V880’s Application Servers • 4 SUN Enterprise 420R’s, Application Servers • 13 Total application instances • SAP 4.6C, 64Bit • Oracle 8.1.7.3, 64bit • Solaris 8 – Upgrading to Solaris 9 in 1st Qtr 2003. • Gigabyte Backbone

  6. BW Production Environment • 1 SUN Fire V880 Server. 8x16. DB/CI on same physical box. configured as an application server. No HA • 2 SUN Fire V880’s, Application Servers. • 4 application instances total. • BW 2.1C > 3.1C • Oracle 8.1.7.3 64bit • Solaris 8 – Upgrading to Solaris 9 in 1st Qtr 2003. • Gigabyte backbone

  7. BW 2.1C Upgrade to 3.1C(In Process) • Technical/Functional Upgrade • Separate Upgrade Landscape • 3 Month Project – Partner SAP • 3.0B Practice Upgrade. 3.1C available mid-November • Global Business Intelligence • Web Based • Enhanced Reporting Options • Foundation for Collaborative solutions • E- Procurement (SRM) • Mobile Sales and Analytics (CRM) • Activation of New Business Content

  8. SAP 4.0B to 4.6C Upgrade • Technical Upgrade with limited new functionality • 5 Month Project – Partners; SAP, Rapidign, and Sun • Separate Upgrade Landscape • Upgrade process was 14 hours for 1.2TB DB. We performed 6 practice upgrades. We reduced overall upgrade time from avg of 30 hours. Adding additional Indexes to large tables prior helped. • Performance – 20% additional overhead with 4.6C on old Sun. Migration to new Sun Infrastructure reduced load from 65% to 35% utilization of systems. • Increased performance in DB and Transactional Response times. Avg Response time is <1.0, decrease in I/0 waits. Users noticed improvements.

  9. SAP 4.0B to 4.6C Upgrade • SAP GUI was upgraded to 6.20. Check PC hardware. Memory was added to many machines to support. • Security Model was a total rewrite. • Ensure adequate storage for upgrade. Do not use SAP recommendation, go beyond. • Food – Provide a wide variety for both Technical and Functional areas. In certain cases take personal requests.

More Related