Technical Development Steering Committee Briefing January 28, 2004

1. Technical Development Steering Committee BriefingJanuary 28, 2004 Tom Phelps Chair, TDSC Paul Schiller Vice Chair, TDSC Michael Memmel Metrics Project Lead Paul Janke Best Practices Project Lead Supply-Chain Council, Inc. 1150 Freeport Road Pittsburgh, Pennsylvania 15238 USA www.supply-chain.org

2. Agenda • TDSC overview • Charter • Major tenets • Conceptual overview • Team members • SCOR/TDSC timeline • Potential changes for SCOR v7.0 • Current project activity • Metrics update – Michael Memmel, R.Reed & Associates • Best Practices update – Paul Janke, Unisys • Returns • Project team engagement model & benefits to project participation • Challenges and future plans • Feedback / Q&A TDSC Briefing

3. TDSC Charter • TDSC leads the SCC’s technical agenda • The TDSC has technical stewardship over the SCOR Model and the technical aspects of the membership experience • Primary responsibilities include: • initiating technical projects • providing feedback and approving project charters • overseeing the progress of technical projects • publishing the results of the projects as appropriate • making recommendations about SCOR Model changes to SCORboard • Chartered by SCC’s Board of Directors (SCORboard) TDSC Briefing

4. Major Tenets of the TDSC (wip) • Ensure that the SCOR Model applies broadly • Across industries • Across regions • Facilitate member companies implementing and applying the Model • Tool ease of use (SCOR Model, collaboration tools, etc.) • Provide forum for members to exchange supply chain info and best practices • Provide a vehicle for SCOR education and training • Involve member companies in the development and extension of the SCOR Model • Ensure practitioners lead technical projects • Participation in technical projects is a key SCC membership value proposition (project teams, SIGs) • Ensure transparency of technical activity by facilitating access and input into technical work in progress TDSC Briefing

5. POTENTIAL OUTPUTS INPUTS / PROPOSALS Model Changes Whitepapers Project Teams TDSC SCORboard Best Practices Metrics SC Council Membership Community Etc. TDSC Conceptual Overview TDSC Briefing

6. TDSC Member Companies TDSC Briefing

7. TDSC Members TDSC Briefing

8. 1997 1998 1999 2000 2001 2002 2003 2004 SCOR Release Roadmap Version 3.1 Restructuring of infrastructure / enable elements Restructuring of metrics begun – definitions of performance attributes developed. Language to support services as well as tangible goods provided Version 1.0 First version of the Model, Plan, Source, Make, Deliver, metrics, best practice, and technology Version 3.0 Model modified to enhance infrastructure elements. Specific reference to software products removed. Inputs and outputs enhanced Model Development Processes Restructured in 2002 to Project Team format Version 5.0 Returns processes introduced E-business practices updated Metrics re-structuring continued Version 2.0 Model modified to reconcile distinctions between discrete and process industries Version 7.0 (planned) Version 4.0 Restructuring of infrastructure enable elements completed. Returns introduced. Input/output restructuring Version 6.0 Retail D4, revamped MRO, Make e-biz best practices TDSC Briefing

9. Potential Changes for SCOR v7.0 • Metrics • Definition changes, explicit explanations of the relationship between metrics and the hierarchical relationship • Level 1 and 2 metrics will be impacted • Best Practices • Best practices definition • Template for “renovation” of SCOR Model • Returns • Inputs and outputs for MRO and minor changes to metrics and enable elements • Restructuring of Return Excess Product and Defective Product will be completed to match changes to MRO • Update of R1 (and potentially R3) to look like R2 TDSC Briefing

10. The typical flexibility matrix… FlexibilityMatrix LeastFlexible ModeratelyFlexible MostFlexible We are here Scope X SCORboard Feb 20 Schedule X Winter Mtg Jan 28-29 Resources X SCW NA March 29-31 TDSC Mtg Dec 18 TDSC Mtg Jan 15 TDSC Mtg Feb 19 An unfortunate reality! Dec 12 TDSC v 7.0 proposal complete TDSC proposals for v 7.0 presented to SCORboard TDSC must have v 7.0 proposal complete Feb. 19!! SCOR v 7.0 released to public SCOR v.7.0 Timeline (tbc) Assumption – v 7.0 released at SCW NA March 29-31, 2004 TDSC Briefing

11. Approved Technical Projects SCOR Technical Development Steering Committee Metrics Best Practices Lead - Michael Memmel (R. Reed) Lead - Paul Janke (Unisys) Returns Lead - Lt Col Scott Koster (USMC) MRO Returns Lead - Joe Burak (Boeing) TDSC Briefing

12. Metrics Project UpdateMichael Memmel – RReed, Metrics Project Lead Project Charter • Analyze the SCOR Model metrics and propose a path for their improvements • Revise existing metrics to support SCOR Level 1 through 2 processes, ensure clarity of metrics definitions and roll-up/roll-down capability • Provide guidance to SCOR implementation teams in using SCOR metrics (how to apply) • Document the results of the project • Publish the results of the project and solicit feedback from SCC members TDSC Briefing

13. Metric Project Participants (1 of 2) Michael Memmel Chair RReed Pat Murrin Co-Chair RReed Assets Monty Boyle Head PWC Bill Settlage HP Costs Nathalie Collautt Head Adjoined Gary Shell StreamlineSCM Gary Cokins The SAS Institute James Kelly SAP Dan Swartwood Pragmatek Reliability Michael Memmel Head PWC Bill Petersen JDE/Peoplesoft Greg Rippstein Peoplesoft Paul Janke Unisys TDSC Briefing

14. Metric Project Participants (2 of 2) Responsiveness Luc Kremers Head Simtech Charles Bienvenu SAP Ted Paetkau Oracle Toshiaki Saegusa JBC Flexibility Craig Thompson Head Progress Logistics Rod Heisterberg ManTech Sudipta Bhattacharya SAP Mark Githens SAS TDSC Briefing

15. Metrics Project Scope • Develop a hierarchical metrics structure which maps the relationship between metrics (vertically and horizontally) as well as the relationship to the SCOR process • Provide clear and concise definitions of the metrics, including their formulation, which can be understood by practitioners and lay-people alike and to clarify differences in definition that may exist between industries and regions • Describe the relationship between business objectives and supply chain objectives and identify the metrics that support each • Identify sources of benchmarking information and providers, whether external or internal to the Council • Out of Scope -- metrics to support Level 3 processes TDSC Briefing

16. Potential Metrics Model Changes • Attribute definition changes • Realignment of existing metrics • Introduction of calculations for some metrics • Changing calculations of some metrics • Alignment of metrics • “Driving” vs. diagnostic metrics • Potential to place value on metrics TDSC Briefing

17. Overall Status: Project Name: Metrics Progress: Key Issues: Next Steps: Accomplishments: Metrics Project Update • Four of the five attributes presented to TDSC • Fifth (Assets) to be presented February 6th • No discussion with other groups (i.e. Retail) • Timely feedback both internally and with TDSC • Inconsistency of definitions • Extensive restructure of metrics • Alignment of metrics • Independent review by practitioner • Complete review • Final feedback from TDSC • Merge feedback • Propose next metrics project goals TDSC Briefing

18. Best Practices Project Update • Project charter • To gather the incubators of, and the world’s foremost experts on, SC processes and the key practitioners of leading edge companies to discuss and agree upon best practices to be documented in subsequent versions of SCOR Model • Potential v7.0 changes • Best Practices definition • Template for renovation of SCOR Model Paul Janke, Unisys Best Practices Project Lead TDSC Briefing

19. Best Practices Team Members • 34 members, 7 countries, 3 continents • More members needed! TDSC Briefing

20. Definition of a Best Practice • A current, structured, proven, and repeatable method for making a positive impact on desired operational results. • Current - Must Not be emerging (bleeding edge) and must NOT be antiquated • Structured - Has clearly stated Goal, Scope, Process, and Procedure • Proven - Success has been demonstrated in a working environment. • Repeatable - The practice has been proven in multiple environments • Method - Used in a very broad sense to indicate: business process, practice, organizational strategy, enabling technology, business relationship, business model, as well as information or knowledge management. • Positive impact on desired operational results- The practice shows operational improvement related to the stated goal and could be linked to key metrics. The impact should show ether as gain (increase in speed, rev., quality) or reduction (resource utilizations, costs, loss, returns, etc.). TDSC Briefing

21. Overall Status: Project Name: Best Practices Progress: Key Issues: Next Steps: Accomplishments: Best Practices Project Update • Since beginning of 2004: • Realigned team to initiate BPs each week • Dialog on BPs on Tuesdays • Change Board activity on Thursdays • Have completed small number of fully documented Best Practices • Active involvement of membership • >Effort is time consuming • >Effort is cumbersome to many • Schedule may move out without additional effort • Huge impact to SCM – worth the effort! • Defined Best Practice • Formed P,S,M,D, and Return Teams with active leadership • Identified many SMEs in SCM disciplines • Developed marketing plan with letter and website www.aspect.com/scc • Implemented state-of the –art collaboration tools – Groove! • Continue completing Best Practices each week • Expand so that each sub-team is doing same • Design Best Practices Handbook to be published by SCC • Bring on new members • Use ProVision tools to accelerate activity TDSC Briefing

22. Best Practices Schedule TDSC Briefing

23. Overall Status: Project Name: Returns Progress: Key Issues: Next Steps: Accomplishments: Returns Project Update • R1 Validation in Progress • R2 Review / Validation is complete • R3 Review / Validation expected to be completed prior to next Model release • None at this time • R2 validation • R1 proposal has been made • TDSC discussing release timeline TDSC Briefing

24. Governance Model (proposal) Develop this into a robust process: Appraise Idea Initiation Sponsorship Charter Development TDSC – Charter Approval Approach Member selection/TDSC Liaison Expected Deliverables Project plan TDSC – Plan Approval Fundamentals Key concepts Model impacts Management of change TDSC – Conceptual Approval Definition Detailed design Practitioner challenged SCOR formatted TDSC – Model Approval Endorsement Model changes Rollout plan Version control SCORboard Approval • Stages can be combined if low complexity, such as Approach and Fundamentals • Approval can be at meeting, or virtual • CTO and TDSC Liaison to facilitate each stage, helping teams prepare appropriately TDSC Briefing

25. Project Team Member Benefits* • Global network of supply chain experts • Learning and growth in supply chain topics • Exposure to leading and emerging SC best practices • Growing your company’s intellectual capital • Public acknowledgment within published whitepapers, presentations, and SCOR • Unique opportunity to be part of a significant achievement • Use of state-of-the-art, web-based, collaborative tools (i.e. Groove) • A lot of fun! *From Best Practices Team brainstorming session TDSC Briefing

26. Potential Volunteer Incentives • Reference participants in any news releases issued announcing revisions • List participants in the SCC newsletter on an annual basis • List participants on the SCC website • Recognize the project team at Supply-Chain World events by including recognition materials in packets given to attendees and during opening/welcome (this can be done at the Chapter level) • Provide volunteers with comp attendance at one Supply-Chain World event for each year they are involved • Provide volunteers with comp attendance at SCOR Workshop for each year they are involved • Provide Certificate of Recognition • Send letter to volunteers’ supervisor, if known, and express thanks to the company for providing this support • Provide a small gift in appreciation TDSC Briefing

27. Challenges • Recruiting project participants • Haven’t found right enticements yet • Limits our capacity • Maintaining effective communications with project teams • Closing on proposed Model changes, additions • Many are controversial -- this is good, push the envelope! • Diversity amongst TDSC and project team participants results in a dozen or more different industry/company/individual perspectives – this is also good, but it’s a challenge! • Time allotted to these discussions is often insufficient – this is bad, but it’s an unfortunate reality • Standard required for Model change is relatively high – and it needs to be, the Model is the center of the SCC • Scope of current project work is broad/pervasive TDSC Briefing

28. Potential Future TDSC Plans From Minneapolis TDSC brainstorming session -- You said… • SCOR ease of use • Globalization of TDSC and project work • Idea submittal process • Implementation methodology • Peer challenge • SCOR Model extension TDSC Briefing

29. Feedback / Q&A TDSC Briefing

30. Backup Material… TDSC Briefing

31. Key Accomplishments • Release of SCOR v6.0 in May ’03 – changes included: • Retail • Model expanded to include a D4 process – the processes associated with the delivery of products to a consumer from a “retail” store • Changes include: a D4 process set, changes to Plan, associated metrics and best practices, and changes to the glossary • MRO Returns • Returns processes associated with MRO were restructured to eliminate inconsistencies in graphics and process description in Version 5.0 • Accommodate Refund / Exchange processes identified in the Retail Project • New process descriptions and graphics are included • Make • E-business best practices TDSC Briefing

32. v6.0 Release PHASE I -- Getting Established PHASE II -- Getting Challenged PHASE III -- Getting Our Act Together PHASE IV – “Steady-State” • Members elected • TDSC formed • Chair/V-Chair Elected • First round of charters approved • First round of project reviews • Project feedback • TDSC Policies and Procedures • Structured project reviews • Tighter TDSC/project team linkages ACTIVITY OCT ‘02 APRIL ‘02 APRIL ‘03 AUG ‘03 TDSC Over Time TDSC Briefing

33. Future Plans • Identification of future areas of interest/project work • Agreement on SCOR v7.0 changes • TDSC “Customer” survey – how are we doing and what can we do better? • ’04 TDSC elections • “Globalization” of TDSC and project work – regional chapters provide TDSC member? TDSC Briefing