IT/IS and Business Units Friends or Foes?

1. IT/IS and Business UnitsFriends or Foes? Judy Lorek, Robert Bosch Tom Malone, NGK Spark Plugs Jim Schwinn, Schaeffler MIS Council Fall Conference October 15, 2007

2. Judy LorekDirector of Aftermarket Information SystemsRobert Bosch LLCAutomotive Aftermarket (USA)

3. The U.S. Automotive Aftermarket of Robert Bosch LLC is headquartered in Broadview, IL U.S. • As a supplier to distributors, national retailers, independent specialists, repair shops or do-it-yourself consumers, Bosch automotive aftermarket products include spark plugs, spark plug wire sets, oxygen sensors, ignition parts, oil, air and fuel filters, wiper blades, brake pads and rotors, starters and alternators. • Information Technology support is provided to over 500 Automotive Aftermarket users, utilizing JD Edwards ERP system, Manugistics Supply Chain solution and Red Prairie Warehouse Management System.

4. IT Support at Robert Bosch Support Process has evolved over time … From a stand-alone Online Request System To a ‘Ticket’ System and a Portfolio Management System (both online but not integrated) To an Integrated Business Engagement Model.

5. IT Business Support at Robert Bosch Using Collaboration Tools such as… Agreed upon collaboration model User-friendly Help Desk to report needs Portfolio Management tools.

6. Project Portfolio Management Definition • Imagine an office complex with 100 different construction teams hired to build 100 rooms, with no blueprint or agreed upon vision. • Portfolio management is an increasingly recognized method for ensuring that information technology initiatives are linked to business goals and objectives (blueprint / vision). • Portfolio management is designed to take the politics out of decision making. Instead of opinion, there is process.

7. IT Project Portfolio Management • Purpose • Gain control over projects and deliver meaningful value to the business. • Improve communication and alignment between IT and business leaders. • Promote more upstream business process analysis (project definition, process flowcharts, approval and communication prior to the application development phase). • Enhance customer satisfaction.

8. Portfolio Management • Deliverables • Ensures upstream business process analysis, definition, documentation and approvals • Promotes business leaders to think cross-divisionally and cross-functionally as a “team” and take responsibility for projects • Creates a process to evaluate and manage investments • Aligns business unit and IT resources • Provides measurable results (cost, benefit, timing, etc.) • Improves communication between the business units and IT • Enhances customer satisfaction.

9. Conclusion • Every project is a decision to invest the resources (financial, human, material) of the organization in a specific outcome.

10. Sample: Project Portfolio Tool • Current Business Process Map • Attach a copy of the current process flowchart specifying who does what task, where (if applicable), when the task should be done, how the task should be done according to a referenced document or work instruction (when such detail is necessary). • Proposed Business Process Map • Attach a copy of the proposed process flowchart specifying who does what task, where (if applicable), when the task should be done, how the task should be done according to a referenced document or work instruction (when such detail is necessary). • Documented Requirements / Specifications • Define the details of the request clearly. Examples: Specific columns for a new report, specific vendors or customers affected by a new process, customer deadlines, account numbers, field mappings, labels, etc. Attach separate documents and reference them in this section, if necessary.

11. Controls and Measures • Define how you will monitor the project and evaluate your success. Detail what verification record will be generated to provide objective evidence that the task was accomplished. • Controls 1. 2. 3. 4. 5. • Measures (Records) 1. 2. 3. 4. 5.

12. Lessons Learned • With or without additional tools, formalize the process • Review, Analyze, Measure, Report • Close the loop and connect the dots with your customers!!

13. Lessons Learned • Commit to a service level • Obtain consensus on the process • Leverage business and technical skills • Let Business make the decision • Accept change as ongoing reality • Business Focus – align IT with Business • Offer an opportunity for involvement • Review, Analyze, Measure, Report • Accentuate process over opinion • Transparent IT governance • Eliminate any confusion

14. Tom MaloneCorporate IT DirectorNGK Spark Plugs (USA)

15. NGK-USA at a Glance • Tier 1 manufacturer/supplier of spark plugs and oxygen sensors, founded in 1966 • Support both OE and aftermarket channels • Ten locations in the US • NGK-USA Information Technology at a Glance • 500+ users to support • Two enterprise systems (JD Edwards & MAS200) • Migration to SAP over next 2-3 years • 14 total associates in NGK-USA IT

16. NGK Spark Plugs (USA), Inc. • Significant Issue Faced by NGK-USA IT • Two manufacturing sites US were separate companies • Separate IT infrastructures, staffs, applications • Different cultures • Merger of two companies = Consolidation Imperative • Business processes • Infrastructure • Applications • Comfort with Legacy Environment ≠ Trust with New “Corporate” Solutions

17. NGK Spark Plugs (USA), Inc. • NGK-USA IT Tasked with Consolidating ERP Environment • Two legacy ERP’s expensive and ineffective support • Neither capable to fully support the NGK-USA enterprise • IT staff spread thin – no “depth” of expertise in IT to fully leverage current applications • Need to support corporate imperative to consolidate business practices • Overcoming of “I’m from corporate, and I’m here to help!” • Defining benefits of new ERP to individual stakeholders

18. NGK Spark Plugs (USA), Inc. • Establishment of Trust with IT • Development of IT Strategy (1st Time Ever) • Established “transparent” practices in IT • Alignment of business goals/objectives with IT programs • 4-5 year planning horizon • Regular feedback conferences between IT and business units, updating of IT Strategy

19. NGK Spark Plugs (USA), Inc. • Establishment of Trust with IT (continued) • New ERP selection project • Objectivity – IT used outside consultants to facilitate the project • Inclusion – Extensive interviewing and benchmarking of business unit stakeholders and processes, project team • Transparency – Deliverables shared to very wide distribution, project highlighted in associate newsletter • Democratic – Input on eventual selection shared among project participants – not a “top-down” decision • Result = Unanimous selection of SAP as new ERP

20. Lessons Learned • Commit to a service level • Obtain consensus on the process • Leverage business and technical skills • Let Business make the decision • Accept change as ongoing reality • Business Focus – align IT with Business • Offer an opportunity for involvement • Review, Analyze, Measure, Report • Accentuate process over opinion • Transparent IT governance • Eliminate any confusion

21. Jim SchwinnDirector of Finance and Information SystemsSchaeffler GroupAutomotive Aftermarket (NA)

22. North American region covered by three distribution centers located in CA, US, & MX and headquartered in Valley City, Ohio • Distributing products represented by the following brands: LuK, INA, FAG • Supporting 150 Aftermarket users in 5 locations

23. AAM - North America • As an aftermarket BU, we focus on marketing and supply chain initiatives only. • IT Systems focus on: • General business processes • Supply chain and warehouse management • Product management • Goals: • Better, faster, more efficient • Integration regionally and worldwide

24. Interaction with the Business • How do you get the real work done? • Improve service? • Show value? • Two simple, critical systems/processes which help make it happen at Schaeffler: • RTS(Request Tracking System) • Top Ten(Project Focus & Approval)

25. RTS (Request Tracking System) • What is it? - System to track all "requests" – IT Anything ideas, process changes, projects, failures, errors, bugs • Hardware, Software, Phone, CC, New user, etc. • Who uses it? – Executives, managers, users, warehouse employees, outside contractors….Everyone. • Why? • One method for all activities – mini workflow • All information in one place – Who, What, When, Why, How • Critical requests are auto. assigned and are addressed timely • Eliminates "hallway" conversations (miss-communication) • Long-term documentation archive • Commits IT to specific service levels

26. Top Ten (Project Focus & Approval) • What is it? – A process for the review and approval of all IT projects/process changes by management • Scope? – Anything not considered failure, infrastructure • Why? – Allows the leaders of the BU to agree on the change and the proper use of resources • Top Ten Review Process for: • General Business, Supply chain, Product Management • Every project must be approved by the appropriate review team or teams….IT does not make the decision • The business must explain and justify the change • Flexibility for IT – Up to 10 projects can be active at one time with the details reviewed and published bimonthly

27. Lessons Learned • Demonstrate that your IT processes work and are effective based upon agreed service levels • Eliminate the confusion • What is being done? • Why are we doing it? • Who's doing it by when? • Offer an opportunity for input and feedback • Let the business (as a whole) decide on the allocation of IT resources

28. Lessons Learned • Commit to a service level • Obtain consensus on the process • Leverage business and technical skills • Let Business make the decision • Accept change as ongoing reality • Business Focus – align IT with Business • Offer an opportunity for involvement • Review, Analyze, Measure, Report • Accentuate process over opinion • Transparent IT governance • Eliminate any confusion

29. How does IT/IS best work with and support business units?

30. Collaborate • Commit to a service level • Obtain consensus on the process • Leverage business and technical skills • Let Business make the decision • Accept change as ongoing reality • Business Focus – align IT with Business • Offer an opportunity for involvement • Review, Analyze, Measure, Report • Accentuate process over opinion • Transparent IT governance • Eliminate any confusion

31. How do you Collaborate?

32. Thank you!

33. Customer Engagement Model = Business = IT