Loading...
HomeMy WebLinkAboutExhibit 2EXHIBIT A SERVICES AND OBLIGATIONS During the Term, Microsoft and Company will work together whereby Microsoft will provide limited Customer on -site support, Partner phone and electronic mail support, Product expertise and limited training, and deployment planning assistance, and technical support. Company will match this effort by providing their solution development and deployment team which will cover Company's overall project management, infrastructure, compatibility testing, site -specific deployment planning and execution, and end -user training and support. Microsoft will provide the following Services: Microsoft will: 1. Provide online access to Office 12 tools, documentation, bug reporting tools, newgroups, webcasts, etc. 2. Provide funding for your services to assist your customer(s) with the Office 12 solution design and deployment. Upon completion of all of the on -ramping process $2,500 USD will be made available to you to invoice against. After the vision and scope document is satisfactorily completed a $10,000 order opened for you to bill against. You must complete Milestone Two, as defined below, to be eligible for the funding. • Microsoft will assist Company with an overall RDP vision and scope document ("Milestone One"); a Proof of Concept Form ("Milestone Two"); and a deployment plan ("Milestone Three"). Microsoft will make available support services to assist in the deployment of the Office "12" solution. Milestone One will last approximately 5 weeks, Milestone Two will last approximately 13 weeks, Milestone Three will last approximately 15 weeks. • Microsoft will make available training tools, including training events, a program handbook, and technical FAQ. 3. Provide list of support resources, including Beta Place and Microsoft Consulting Services for technical questions and assistance. 4. Microsoft or Microsoft Consulting Services will review and provide direction on the initial vision and scope plan for the solution. Microsoft will work to scope a solution that identifies and resolves the paired Customer's most challenging business process or issue. To achieve this, Microsoft or Microsoft -authorized contractors may wish to visit Company on site to analyze the business solution with the corresponding Company RDP project team. 5. Technical Support a. Company will receive Tier 1 technical support through the documentation on BetaPlace, including the bug reporting tool, webcasts, and newsgroups. • Company will receive Tier 2 technical support through MCS. • To be used for questions relating to Company's involvement in the Product RDP or contact questions. ■ To be used for questions pertaining to milestone documentation, software distribution, ID, or Product -related questions. Microsoft Office 12 RDP Agreement 7 • In addition, Microsoft will: o Host regional training events for both Partners and Customers in February 2006. Trainings will be facilitated by the MCS Team . o Provide 2"d tier support directly to program Partners through MCS Champs. o Provide you with access to available documentation and materials on Beta Place. o Provide you with Newsgroup support and bug reporting tool access through BetaPlace. o Provide additional training and support through conference calls and Live Meetings. o Provide you with access to IT training events, materials and content. o Provide you with Beta 1 and Beta 2 versions of Office "12" throughout the length of the program through an online resource from which you will download software. 6. Create forms of customer evidence and provide you with the opportunity for editorial review before publication. Microsoft will determine in its sole discretion which customers and/or partners will provide evidence for case studies, testimonials, videos, publications and similar activities. 7. Maintain communication with you via conference calls, Appropriate members of the Microsoft RDP team shall participate in periodic conference calls with Company personnel to discuss specific issues that may arise regarding RDP project. Microsoft personnel will track and escalate issues in an expeditious manner to resolution. Both parties will be notified of exceptions to the scheduled calls at the earliest possible time. Such notification will include either a rescheduled time, or if agreed upon by both parties, the call may be cancelled due to holidays or business conflicts. Microsoft field representatives may participate in monthly calls with the Company and provide information from Company's feedback to Microsoft resources. Microsoft field representatives may act as a liaison between Company and Microsoft. 8. Microsoft will initiate status meetings and e-mail to resolve ongoing support Issues and answer questions. Company will have the following Obligations as further described below: Designated on -site Company Resources • Company will designate at least two (2) and up to five (5) Company employees as set forth below to be part of the RDP project (the "RDP Team"). The RDP Team help to drive the evaluation, implementation, support and deployment of the Products within the Company. Provide Access and Assistance • Company shall provide Microsoft with access to Company premises, personnel and equipment necessary for Microsoft to complete the Services. • Company shall designate a technical team to provide assistance to Microsoft with respect to the Services. Company may, at its discretion, designate additional Company personnel or Company -authorized contractors to assist Microsoft in their performance of the Services. • Company agrees to receive e-mails from Microsoft regarding the RDP. Provide Product(s) Feedback • During the Term, Company shall provide reasonable product feedback to Microsoft, including, but not limited to: • Bug reports and test results regarding the product. • Usability of the product. • Details with respect to installation of the product in the adoption environment. • Review and comment on all documentation supplied. Microsoft Office 12 RDP Agreement 8 • If applicable, business productivity metrics to support the case for the Office "12" solution. Active Participation • Company will have one (1) designated representative of the RDP Team attend the 2 day training in February, 2006, • Company will participate in conference calls, project calls, development, review and finalization of Program documents at least a bi-weekly. Company will also participate in a monthly status call with the field and will participate in additional calls as needed with MCS. • Company will review and authorize use of publicity as outlined in Exhibit B. Technical Support Company will provide technical support services to its customer(s). • The customers will receive Tier 1 technical support through documentation and BetaPlace.Company will provide first line Tier 2 technical support to its customer(s). • You will supply email resources to customers for submitting support questions: o To be used for questions relating to customer's involvement in the Product RDP or contact questions. o To be used for questions pertaining to the documentation, software distribution, ID, solution deployment or Product -related questions. Note: These are basic expectations and commitments intended to facilitate a positive experience for you and your Partner through the RDP program (the "Program"). The right column indicates REQUIRED or MAY BE REQUIRED depending on how critical we believe it is to adhere to that specific term for joint success working together. Preparation This section addresses the manner in which you should prepare for this Program. You should: Sign Microsoft RDP Program Participation Agreement REQUIRED After acceptance into the program, review documentation, REQUIRED newsgroups, webcasts and other Office "12" content posted on the Microsoft BetaPlace site. Work with paired customer to review IT architecture REQUIRED environment prior to the start of the Program as part of the vision and scope phase. Submit a list of related software used by the customer REQUIRED during RDP to aid in interoperability issues. Submit a list of hardware planned for use by the customer in this Program to aid in troubleshooting and interoperability issues. Microsoft Office 12 RDP Agreement MAY BE REQUIRED 9 Your Resources and Actions This section addresses the extent to which you should allocate specific resources and appoint specific contacts for this Program. You should: Form a Project team of employees who will represent your company's involvement in the Office "12" RDP Program: + Overall Project Manager • IT Department Manager • Development Lead PR/Marketing contact Company will notify Microsoft of any changes to the RDP team. Create an internal email distribution list for use by Microsoft: SamDIeRDP ancompanv.com Project Team Distribution List: REQUIRED OPTIONAL Overall Project Manger Name: Email: Phone: IT Department Manager Name: Email: Phone: Development Lead Name: Email: Phone: PR/Marketing contact Name: Email: Phone: Taking Part In the Program This section addresses the extent to which you should expect to interact with Microsoft and other program members. You should: Attend one of 3 Regional Office "12" US RDP Regional Trainings during the month of February 2006. This is a 2 day training event taught by MCS Team. (** Note MS will pay travel and expenses for program participants, both customer and partner) Complete, Milestone One, Rapid Deployment Scope & Vision document to identify the solution you will work with the customer to develop during the program and submit to Microsoft for review by March 24, 2006. Milestone One will run from February 2006 through March 24, 2006. Install Beta 2 code upon availability of Beta 2 code in March 2006. Work with Customer to deploy solution, Milestone Three, during the period June 10, 2006 through October 2006. Microsoft Office 12 RDP Agreement REQUIRED —Failure to comply with this requirement may result in immediate termination from the Program. REQUIRED REQUIRED REQUIRED 10 REQUIRED REQUIRED REQUIRED REQUIRED REQUIRED Taking Part In the Program Complete "Lessons Learned" survey following each milestone of the Program. Participate in bi-weekly project update call during Scope and Vision Phase (Milestone One), Proof of Concept phase (Milestone Two) and "Deployment Phase" (Milestone Three) with Microsoft representatives and/or MCS. Frequency of calls may fluctuate depending on overall support need. Participate in monthly project update field calls during with Microsoft Office "12" US Rapid Deployment project team. At Microsoft's option, work with Microsoft Rapid Deployment Team to address remaining support issues. Review, edit and approve Microsoft case study as developed by Microsoft by July 2, 2006. Product Support Permit Microsoft Consulting Services (MCS) to assist REQUIRED during all of the Milestones including Scope & Plan, Proof of Concept and Deployment. Publicity In addition to Exhibit B, this section outlines how you take part in Microsoft's publicity efforts for the technology(s) covered by the Program. Company will: 1. Review, edit and ensure legal department approval of 1-page Microsoft Solution Brief that describes Company's solution development process and deployment using Office "12" beginning with Milestone One. Microsoft will continue to gather case evidence throughout the program and Company will continue to review and approve the information for release throughout the Program and after program completion. 2. Review, edit and ensure legal department approval of post -deployment case study during and after Milestone Three. Microsoft may conduct a post deployment case study several months after deployment and Company will participate with Microsoft in this post deployment study. 3. Attend a Microsoft Office "12" Launch Event if asked to attend. Microsoft will pay travel and expenses to attend in accordance with Microsoft's Travel Policy. 4. Provide a quote from someone in your organization for use in (1) press release, with full review and editorial rights of this release. 5. Assist Microsoft in documenting best practices regarding the Office "12" solution you worked with the customer to deploy. 6. Speak to a prospective customer / partner considering an Office "12" product 7. Speak to a leading technology analyst about your use of an Office "12" product in Microsoft Office 12 RDP Agreement 11 one 60-minute interview. Microsoft Office 12 RDP Agreement 12