1. © 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 1 Partner Communications: Non SP CSSP POS billing Process Name

2. © 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 2 Agenda POS Billing Process How can you contact SSC Team SSC Escalation Process POS Billing Process POS dispute Process

3. © 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 3  A service in the Partner-Branded space to achieve complete coverage of all new products purchased under CSSP & Co-Bridge foundation partners on mandatory attach schemes  Concentrated on those partners that purchased product from a Distributor and have not covered the product serial number with an appropriate service – contractually obliged to do so.  The POS billing reporting function is the mechanism to communicate to Partners what they need to cover under their CSSP mandatory attach program.  1 Tier partners are unable to order service via 2 Tier – they must cover service under their direct purchase route via CSCC.  Payment on service - contractual obligation is within 30 Days of product item shipment. POS Billing Process

4. © 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 4  Reports are currently generated by the SSC team each Month  SNIFF is run on each partner data file generated for the partners prior to publication  All covered items and approved exclusions are removed from each report  Publication and communication of reports provided + 5 Days following Cisco Financial Month end.  Notified available via SSC case with the direct link,Livelink:  (https://tools.cisco.com/cws/livelink?func=ll&objId=3108898&objAct ion=browse&sort=name)https://tools.cisco.com/cws/livelink?func=ll&objId=3108898&objAct ion=browse&sort=name  Includes instructions on how to raise a case in the event of a query with regard to reports or access issues. POS Billing Process

5. © 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 5 POS Billing Process Summary of Total current, outstanding and escalated billing (same day price) POS Billing report

6. © 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 6 POS Billing Process POS Billing report Tabs The POS Billing report tabs  CSSP Billing- Contain a summary of all billings (Current month, Outstanding and Escalated Billing  Top Opps- Provide a summary of sum of service not sold per End-Customer global ultimate name  End User- Provide a summary of sum of service not sold per End- User and their address  Company Details- List of serial numbers with same day price per BID, End-User and Ship to

7. © 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 7 Dispute Should be raised by Partner within 10 days of receiving the Monthly POS billing report If Disputes is raised after the 10 days window SSC can not guarantee to have all serial number excluded (if any) in the next POS billing report The Level 1 SSC agent is responsible for resolving the case within the defined SLA POS Dispute Process How to log a dispute case

8. © 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 8  SSC Team can be contacted via phone on the following number  Through CIN:- CIN Line + 32 2 704 5555 http://www.cisco.com/en/US/support/tsd_cisco_w orldwide_contacts.html  The main line can also be used to escalate an existing case with SSC Team. How can you contact SSC Team Phone Support

9. © 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 9 How can you contact SSC Team – On Line

10. © 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 10 Category to select in SSC is: « General information >Support >POS Billing >Disputes » Enter Subject line as: Partner Name – Country – Month Billing Disputes Attachment POS Dispute Process Provide detailed description on Disputes + Monthly POS Billing report with lines in dispute highlighted How to log a dispute case

11. © 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 11 POS Billing Process overview AR Team Cisco SSC CSAMDisti Disti submits Weekly POS to CISCO AR Database uploaded weekly with POS data Monthly CSSP Mandatory partners – extract detailing uncovered by Partner Produce monthly report per partner – of outstanding billing – post to live link site and email partner Work with partners to Resolve and order Escalation and partner relationship responsibilities Partner 1T partner buys product via Disti Partner lodges any dispute with SSC Collates and excludes – valid disputes Partner places quote And Orders for Uncovered products Uncovered products Remain in AR database Removed AR database Works on and resolves case Receives update 2 Way Relationship

12. © 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 12 POS CSSP non SP – Framework FY10 Framework CSAM SSC Reports Queries / Disputes / Exceptions Partner Enforcement Approval / Deny

13. © 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 13

14. © 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 14 The Complete tab contain:  BID, BID Name and Disti Name  End-User Details  Items names, PO number and serial number  CISCO Ship Date- Date Shipped from Cisco  POS TRAN DATE- Date shipped from Disti  Order Number- Product SO #  Service Levels Tab- The price for the different service levels  SumOfSVC NOT SOLD- Value of SVC Not attached  SumOfNew Svc Sold- Value of SVC attached  SumOfTotal Svc- Total Potential SVC  Month- Fiscal Period ID - Calendar Shipment Month  Billing Flag- Current, Outstanding or Escalated - Based on Calendar Shipment month POS Billing Report

15. © 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 15 Escalation Criteria Before an escalation is initiated, there are some criteria which need to be respected for the escalation to be a valid one. The following issues will be considered as being a valid escalation:  Business impacting  Not satisfied with response on case  Not satisfied with response on case from third party  Wrong case handling  Missed SLA