Microsoft Robotics Developer Studio Partner Program (MSRSPP) Guide

  • Article

The Microsoft Robotics Studio Partner Program (MSRSPP) guide provides an overview of the program highlights, and also outlines the program requirements and application process.

MSRSPP features the following categories of companies:

  • Robot Manufacturers - manufactures and markets robots that support MSRS-based services/applications.
  • Hardware Component Vendors - manufactures and markets hardware devices that support MSRS-based services or MSRS-based scenarios.
  • Solution Providers - develops commercial software solution using MSRS technologies. May act as a consultant or solution provider to other 3rd parties.
  • ISV - develops software or software development tools for MSRS-based robots.

Please note: Highlights and requirements may be added or deleted at Microsoft's sole discretion.

MSRSPP Program Highlights

  • Listing on Microsoft Robotics Studio partner page featuring company name, logo, product description and link to company website.
  • Opportunity for participation in Microsoft Robotics Studio sponsored or hosted robotics industry events. This may include participation in exhibit demonstrations, conference keynote presentations, road shows and/or training workshops.
  • Microsoft quote for your company's press releases (requires pre-approval from Microsoft).
  • Optional inclusion in Microsoft Robotics Studio press releases.
  • Optional inclusion of your company's robot services or samples with future Microsoft Robotics Studio product releases.
  • Optional training from Microsoft.
  • Optional pre-release updates, architectural overviews and/or technical information (requires signed NDA).

In order to be included in the program, a company must meet the following requirements.

MSRSPP Program Requirements

Program requirements for all company categories:

  • The application form must be completed in full. You should include up-to-date marketing and technical contacts and be reachable via email, Internet or fax.
  • Your company must maintain a professional online presence 24x7 (Web site).
  • Your company must work cooperatively with Microsoft to promote support of Microsoft Robotics Studio, including:
    • Provide a company overview (100 words), a description of your products (100 words), a company logo (in both EPS and GIF/JPG format - 100x50 pixels), and permission for Microsoft to use this logo on its website.
    • Create a publicly-accessible page on your company Web site about your Microsoft Robotics Studio-compatible offering and provide permission to Microsoft to optionally provide a link to it from any Microsoft Robotics Studio website.
    • Promote and publicly support Microsoft Robotics Studio-based solutions and services in tradeshows, conferences and online forums where possible.
    • Distribute a press release describing your support for Microsoft Robotics Studio. (Press release to be reviewed and pre-approved by Microsoft.)
    • Provide ongoing information about your continuing support for Microsoft Robotics Studio (on request).

Additional requirements for robot manufacturers, hardware component vendors and ISVs:

Your company must offer products or service(s) and/or 3D models and simulation services compatible with the Microsoft Robotics Studio. A product or service is considered to be Microsoft Robotics Studio compatible if the following conditions are met:

  • The primary control loop/orchestration is based on DSSP/CCR and is executed in the context of DSSHost.
  • Device interactions are through MSRS-based services.
  • There is clear separation of function and state within a service, and the service state is observable.
  • Services are kept current with the latest release of Microsoft Robotics Studio, and your company should provide customer support for these services.

Additional requirements for solution providers (SPs):

Provide one example of customer implementations or case-study using your support of Microsoft Robotics Studio on your company's public website, granting Microsoft permission to link to this information.

Your company may also join other Microsoft Certified Partner Programs. See the Microsoft Partner Program Membership page.

Trademark Usage

Companies must not use the Microsoft Robotics Studio logo on their websites or products without written permission from Microsoft. Also please refer to the general Microsoft trademark guidelines for proper legal references to Microsoft and its products.

Next Steps

Please complete the MSRSPP Application Form in its entirety, and forward to MSRSPP@microsoft.com.

Development Configuration Guidelines

It is encouraged that 3rd parties follow the guidelines specified below when distributing services or samples that would overlay with Microsoft Robotics Studio install.

  • Services and Samples should be distributed using a setup application with uninstall capabilities. Uninstall should not remove MSRS core files nor user-modified files.
    If you distribute derivative work that is based on MSRS sample code, then such distribution must be in compliance with the applicable End User License Agreement (EULA) of the sample code.
    Please go to the Licensing page to review the MSRS EULAs.
  • 3rd party install must place:
    • All platform specific samples under the following directory:
      samples\Platforms\<MfgName>\<PlatformName>
      or alternatively create your own folder, e.g.<MfgName>\<PlatformName>
    • All configuration files and manifests files under the following directory:
      samples\config
      or alternatively under your own folder, e.g.<MfgName>\config
    • All complied services, Proxies and Transform dynamic load libraries under:
      \bin
      (bin is a flat directory. Do not create sub structures under this directory.)
      or alternatively create your own folder, e.g.<MfgName>\bin
      Note that if you create your own bin folder, then you will need to update the serviceSearchPaths.xml file in the store folder to include it in the search path for DssHost.
    • All web accessible data must be placed under the following directory:
      store\
      (store will form the root directory for https://localhost:<port>/)
    • All Media files (.jpg, .bmp, .obj) that need to be accessible via services (simulation for example) under the following directory:
      \store\media
  • It is preferable that transforms and style sheets be embedded with the service assemblies as illustrated in Service Tutorial 6 "Embedded Resources".
    If embedding is not possible then:
    • Transforms (.xlst) must be placed under the following directory:
      store\transforms
    • Styles sheets (.css) must be placed under the following directory:
      store\styles
  • It is recommended that all 3rd party services/samples follow the patterns described in the service tutorials. Make sure that the namespaces and contract URI for the samples reflect your corporate identity.