1. ©1995-2001 i2 Technologies, Inc. CONFIDENTIAL Xiaoping Chen i2 Collaboration --- CPFR Demand Collaboration I2 Technologies

2. ©1995-2001 i2 Technologies, Inc. CONFIDENTIAL Xiaoping Chen CPFR workflow 1. Front-End Agreement 2. Joint Business Plan 3. Create Sales Forecast 4. Identify exceptions 5. Resolve exceptions 6. Create Order Forecast 7. Identify exceptions 8. Resolve exceptions 9. Generate Order Once Qtr. Wk, Mo Collaborative Planning Collaborative Forecasting Collaborative Replenishment Selle r Buyer

3. Create Sales Forecast Identify Exceptions for Sales Forecast Identify Exceptions for Sales Forecast Resolve / Collaborate on Exception Items Resolve / Collaborate on Exception Items Create Order Forecast Identify Exceptions for Order Forecast Identify Exceptions for Order Forecast Resolve / Collaborate on Exception Items Resolve / Collaborate on Exception Items Develop Front-End Agreement Develop Front-End Agreement Create Joint Business Plan Create Joint Business Plan Order Generation Delivery Exception Distributor Business Development Activities Distributor Business Development Activities Distributor Receiving Retail Store Consumer Manufacturer Materials & Production Planning Order Filling / Shipment Execution Produce Product Distributor Exception Triggers Distributor Decision Support Data POS Data Distributor Exception Triggers Distributor Decision Support Data Long Term Short Term Updated Data for Exception Items Manufacturer Decision Support Data Manufacturer Exception Triggers Constraints Order Forecasts Frozen Forecasts Manufacturer Decision Support Data Manufacturer Exception Triggers Unresolved Supply Constraints Exception Items Feedback Product Order Filling Feedback Order / PO Exception Criteria Planning Forecasting Replenishment Either / Joint Activities Manufacturer Activities Distributor Activities Key: Business Model - Generic CPFR © VICS.1998

4. ©1995-2001 i2 Technologies, Inc. CONFIDENTIAL Xiaoping Chen CPFR Workflow Detail Description

5. ©1995-2001 i2 Technologies, Inc. CONFIDENTIAL Xiaoping Chen i2 TM-CPFR Implementation Business Planning workflows Forecast Collaboration workflows Problem Resolution workflows Scorecarding functions

6. ©1995-2001 i2 Technologies, Inc. CONFIDENTIAL Xiaoping Chen Business Planning workflows (1) Corresponding to the 1 and 2 step of CPFR specification, following workflows are provided for business planning: Front End Agreement: Attachment/detachment of FEA agreement document Role permission apply Joint Business Planning --- general: Role permission apply Attachment/detachment of JBP document Joint interactive item level forecast exception tolerance setting High/Medium/Low tolerance threshold setting by upflex/downflex High/Medium/Low tolerance threshold setting by timeline Joint interactive timeline phase (frozen, commit, forecast) length setting Joint interactive timeline phase editability setting

7. ©1995-2001 i2 Technologies, Inc. CONFIDENTIAL Xiaoping Chen Front End Agreement

8. ©1995-2001 i2 Technologies, Inc. CONFIDENTIAL Xiaoping Chen Joint Business Plan --- Exception Tolerance

9. ©1995-2001 i2 Technologies, Inc. CONFIDENTIAL Xiaoping Chen Business Planning workflows (2) Joint Business Planning --- Management Metrics Joint planning/collaboration on sales metrics monthly at category and DC level between partners Business Event/promotion History calendar: list event/promotions filtered by time period and partners Event/promotion creation: create events, activities and targets that associated with item level forecast collaborations Update event/promotion: update existing event/promotion Delete event/promotion: delete existing event/promotion

10. ©1995-2001 i2 Technologies, Inc. CONFIDENTIAL Xiaoping Chen Joint Business Plan --- Frozen Time Fence

11. ©1995-2001 i2 Technologies, Inc. CONFIDENTIAL Xiaoping Chen Business Event/Promotion

12. ©1995-2001 i2 Technologies, Inc. CONFIDENTIAL Xiaoping Chen Forecast Collaboration workflows Corresponding to the 3 and 6 step of CPFR specification, following workflows are provided for forecast collaboration: Collaboration Forecast Collaboration is enabled at the item-site-retailer-vendor level Collaboration procedure is a business process software provides means of defining the forecast measures (e.g., retailer sales forecast, vendor sales forecast, concensus, retailer order forecast, etc), timeline, exception measures, and collaboration view (MCV and SCV screen) for data reviewing and updating. Partners will need to define a business procedure on how to utilize the common workspace to best achieve the collaborative purpose. Navigate to collaboration view: Multiple means of navigation to the MCV or SCV are provided in favor of user choices: Multi-collab by hierarchy: navigate to MCV utilizing product/region hierarchy Multi-collab Filter: navigate to MCV using customer, supplier, item, site filters Navigate by supplier/customer, item, site dimensions: multiple combinations provided Multiple view variances for MCV can be defined, e.g., Dollar view, Unit View

13. ©1995-2001 i2 Technologies, Inc. CONFIDENTIAL Xiaoping Chen Customer Sales Forecast

14. ©1995-2001 i2 Technologies, Inc. CONFIDENTIAL Xiaoping Chen Vendor Sales Forecast

15. ©1995-2001 i2 Technologies, Inc. CONFIDENTIAL Xiaoping Chen Sales Forecast Exception Resolution

16. ©1995-2001 i2 Technologies, Inc. CONFIDENTIAL Xiaoping Chen Customer Order Forecast

17. ©1995-2001 i2 Technologies, Inc. CONFIDENTIAL Xiaoping Chen Vendor Supply Commit

18. ©1995-2001 i2 Technologies, Inc. CONFIDENTIAL Xiaoping Chen Problem Resolution workflows Corresponding to the 4,5,7,8 steps of VICS CPFR specification, following workflows are provided for problem resolution: Issues Provide problem summary by problem category (exception DM) Multiple means of problem reporting: With collab counts Without collab counts Collab counts by severity Collab counts by product/region hierarchy and partners Drill down to problem detail: total bucket count and bucket counts by severities (High/Medium/Low) for each collab that has problems From problem detail navigate to the corresponding collaboration workspace (MCV view) for problem resolution (enter new data or inform the other partner)

19. ©1995-2001 i2 Technologies, Inc. CONFIDENTIAL Xiaoping Chen Order Forecast Exception Resolution

20. ©1995-2001 i2 Technologies, Inc. CONFIDENTIAL Xiaoping Chen Order Generation

21. ©1995-2001 i2 Technologies, Inc. CONFIDENTIAL Xiaoping Chen Scorecarding functions Several scorecarding functions are provided: Collaborations --- product/region hierarchy (HCV) Forecast data aggregation by product hierarchy and region hierarchy Computation/exception of aggregated forecast data through user defined measures MCV summary view Forecast data aggregation of multiple collaborations Computation of aggregated forecast data through user defined measures MCV/HCV view by user defined calendars Forecast data aggregation based on user defined calendars Computation of aggregated forecast data through user defined measures Business Plan --- Management Metrics Computation of sales metrics data through user defined metrics

22. ©1995-2001 i2 Technologies, Inc. CONFIDENTIAL Xiaoping Chen Hierarchical Aggregation (Sub Level Aggregation or Collab Level Value)

23. ©1995-2001 i2 Technologies, Inc. CONFIDENTIAL Xiaoping Chen Separate Fiscal Calendar for Vendor and Customer

24. ©1995-2001 i2 Technologies, Inc. CONFIDENTIAL Xiaoping Chen Implementation Methodology

25. ©1995-2001 i2 Technologies, Inc. CONFIDENTIAL Xiaoping Chen Slide 25 RHYTHM Value Delivery Process - Objectives Selection Process Business Release Process Production Support Process Analyze root causes and identify opportunities Establish & quantify business value Identify enabling i2 products and services to leverage business drivers Target key performance indicators (KPIs) Develop business release strategy Rapidly implement supporting process changes & enabling RHYTHM technologies Transfer knowledge regarding RHYTHM and supporting processes to customer Lay foundation for continuous improvement Rapidly realize and measure business value Support continuous improvement efforts Ensure continuous production readiness of customer’s RHYTHM implementation Ensure ongoing delivery of benefits to customer Measure and Monitor Results (Expand Scope and/or Refine Model)

26. ©1995-2001 i2 Technologies, Inc. CONFIDENTIAL Xiaoping Chen Slide 26 What is a “Business Release”? Business Release: An integrated set of changes that result in some specific business improvement Focus on business results, not function Expected completion date and responsibility May include one or more of these changes Implementation of software functionality Data changes Process changes Policy changes Performance measure changes Functional Business Release

27. ©1995-2001 i2 Technologies, Inc. CONFIDENTIAL Xiaoping Chen Slide 27 Factors to consider in defining Business Releases Consider : Impact on key business metrics Ability to Implement - technical issues data availability required integration effort impact to existing systems Ability to implement - organizational issues organizational buy-in organizational change readiness resource availability Consider each Business Release as a building block to the final vision

28. ©1995-2001 i2 Technologies, Inc. CONFIDENTIAL Xiaoping Chen Slide 28 RHYTHM Value Delivery Process - Cycle Identify opportunities Define how business value is achieved Target KPIs Measure and Monitor Results (Expand Scope and/or Refine Model) Conduct Business Release Activities Support Production SOAMobilize 5% Design Solution 25% Acceptance 20% Deploy, Monitor & Transition 10% Develop Solution 40% Assess Delivered Value Go-Live Review Postmortem Review Design Review Sign Contract Solution Review Project Kick-off Average 3-5 months 2-4 Weeks1 Week3-6 Weeks2-3 Weeks1-2 Weeks Knowledge Acquisition Transition Workshop

29. ©1995-2001 i2 Technologies, Inc. CONFIDENTIAL Xiaoping Chen Slide 29 Implementation Project Team Roles i2 Engine Planners/ Subject Matter Experts Sales & Mktg/ Business Ops/ MaterialsPlanning / Mfg. BTO/ CTO Modeling (i2) WMS Integrated Team I2 Platform Access POS Technical Lead Coordinate IR Resources Guide systems Integration Ensure data integrity Interface Engineer. Data mapping/ planning data expertise Extract data from all legacy data-sources Inbound/ Outbound data management Legacy/ develop interfaces - Rhythmlink (i2) Supply ChainModeler (i2)/ SuperUser Map business requirement to planning appl. Application usage expert builds supply chain model Communicate data rqmts (Cust1 / i2) Project Manager: Cust1/ i2 Guide implementation Coordinate resources (including cross- functional) Resolve conflict & facilitate Communication Project Sponsor: Cust1/ i2 Overall direction & vision Quality Assurance Resolves impasses Provide access to key people Systems Engineer Hardware/ software install/ maintenance System admin (Cust1 / i2) Process Champion identify planning process changes Develop new planning processes / workflows Coordinate Training (Cust1/ i2) Business Users (Cust1) Validate design Validateplanning work-flow Support System Testing/ Pilot Post-production users spread- sheets