Bose and SAP NetWeaver Andy Nemtzow Director Corporate Enterprise Systems 3/15/05
Purpose of my presentation Provide insight how Bose implemented the SAP NetWeaver stack over the past few years.
Agenda Bose the company and our systems Decision support Middleware and SAP XI Futures
Bose Corporation Began in 1964 by Dr. Amar Bose Private > $1.7 Billion in global sales > 8,000 employees Research, Design, Manufacture, Global Sales Channels = Direct, OEM, Military, and Dealer Home Entertainment Automotive Noise Reduction Tech Professional Products
Call Center CRM Bose System Arch. Today Financial Cons. Customer Info Order GL Credit Card Order Status Inventory Authorization Settlement SAP Bose Time Collection Hours Employee Data Accruals GL Hours (From TC) Employee Data Accruals Prod. Sch HRIS Supply Planning Net Req. Mex. HRIS.com POS Sales Cycle Count Pricing Master Data EDI Order Sell Thru ASN SAP BW Master Sch. Deliveries Returns Legacy MRP Inv. Cust. Demand BM Demand Planning PDM
Bose Time Line Implemented Data Warehouse Purchased BW Licenses Review and Learn BW Begin to replace DW HED Roadrunner Decommissioned DW & Live HED Part of Projects 94 95 96 97 98 99 00 01 02 03 04 05 Future Implemented R/3 Major Implementation D to C and Finance R/3 Evaluate EAI MDM, Selected XI SOA SAP ERP XI Go live
SAP NetWeaver at Bose SAP NetWeaver PEOPLE INTEGRATION Multi-channel access Composite Application Framework Portal Collaboration INFORMATION INTEGRATION Bus. Intelligence Master Data Mgmt PROCESS INTEGRATION Integration Broker Knowledge Mgmt Business Process Mgmt APPLICATION PLATFORM Lifecycle Management Implemented Being Evaluated J2EE ABAP DB and OS Abstraction
Our IT Strategy Move off legacy systems onto SAP Leverage Integration Re-use before buy; buy before build Use internal resources to retain knowledge and minimize costs
Our Challenges DW to BW Not business driven to change Needed to make the change invisible to the business Would continue to use Business Objects as end user tool Funded by IT Migrated data from DW to SAP BW Lots of data issues Significant work to clean up the data Minimal experience in the market place at that time. Number of users continued to increase during the migration
Why Roadrunner in HED A holistic view of business activities A product lifecycle management point-of of- view To develop and implement Key Performance Indicators. To remove the barriers to business information Promote the wider use of this information with a user-friendly interface To develop a three-tiered tiered business intelligence solution: Dashboard for management P t d i ti f d t
Roadrunner Scope Global Sales (SAP and other systems) T12 (SAP and other systems) Forecast (Demand Planning) Profitability (Financial Consolidation) 3 rd party market data Challenges: Target timeline was 3 months actual time was over 1 year (DATA, DATA, DATA) Use Portal and Business Explorer for reporting Trained over 50 users including the
Benefits of moving to BW and Roadrunner One version of the truth Leverage platform to build on for the future Shared services Data models Learning's for new projects (Portal) Speed Faster to delivery Leverage standard SAP tools standard extractions and reporting Quicker visibility and decision making Ease and of use
Roadrunner Sample Information HED Summary Bose Private
Bose Private Bose Private HED Summary
Forecast Slice and Dice Bose Private
Forecast Drill Down Bose Private
Bose Private Sales Slice and Dice
Bose Private Bose Private Bose Private Bose Private Bose Private New Product Sales
Decision Support Architecture Today SAP Portal SAP BEX Business Objects BW 3.1 Other Data Sources
Our Quest for EAI 5 years reviewing EAI technology Burning platform to integrate CRM and SAP 3 month project to select EAI tool Looked at 4 vendors Required a shoot out to prove technology SAP Exchange Infrastructure (SAP XI) chosen However, 2.X lacked key functionality Chosen as part of the 3.X ramp-up program
XI Ramp-up Build robust and reliable infrastructure for a standard platform for all our integration needs Pilot project with low risk Integrating POS system and SAP Used Business Connector as a back up Successfully went live in November 2004 Now using for integration Japanese sales sub EDI and SAP Japan instance Next major project use to integrate CRM and SAP etc, etc
Benefits Benefits: Lower cost for integration development and maintenance Leverage single technology with a shared service model Leverage web services fewer point to point Seamless integration with SAP technology
Next Steps Use Web services for ATP Pricing Customer Review SAP Master Data Management (MDM) for Customer and Product Data SEM for Finance (Balance Score Cards) Supply chain project APO SRM
Bose and SAP NetWeaver Andy Nemtzow Director Corporate Enterprise Systems 3/15/05