Microsoft Dynamics NAV

Transcription

1 Microsoft Dynamics NAV Microsoft Dynamics NAV Registered Solution Program Guide for Independent Software Vendors Posted Date: December 2013 Effective Date: October 2012 Version: 2.0

2 Contents Microsoft Dynamics NAV Registered Solution Program... 3 Microsoft Dynamics NAV Registered Solution Program Addendum Terms... 3 Certified for Microsoft Dynamics (CfMD)... 5 When is a solution certified?... 5 Annual fee deferral... 5 Existing Add-Ons... 6 How to locate and submit the Registered Solution Program Addendum (RSPA)... 7 Registering a Microsoft Dynamics NAV Registered Solution... 8 Microsoft Dynamics NAV Registered Solution Billing Periods... 8 Logging Queries... 8 Limited User Registered Solutions... 9 ISV Partners providing localization for a CfMD Registered Solutions How to Register a Microsoft Dynamics NAV 2013 Registered Solution to a customer s license Frequently Asked Questions MICROSOFT DYNAMICS NAV Registered Solution Program Guide

3 Microsoft Dynamics NAV Registered Solution Program Microsoft has introduced the Microsoft Dynamics NAV Registered Solution Program. This new program is designed to promote scalability of packaged solutions and increased participation in the Certified for Microsoft Dynamics (CfMD) program. It replaces the Microsoft Dynamics NAV Add-On Program for Microsoft Dynamics NAV 2009 and will be the only available mode for Independent Software Vendors ( ISVs ) to offer their solutions on Microsoft Dynamics NAV 2013 using the reserved objects range (1,000,000-98,999,999). Microsoft encourages ISVs especially those with an active Add-On Applications Addendum for Microsoft Dynamics NAV to learn how to leverage this new program. Microsoft Dynamics NAV Registered Solution Program Addendum Terms The Microsoft Dynamics NAV Registered Solution Program Addendum ( RSPA ) is a global agreement with a 2 years term, for which ISVs enter into a new quarterly fee structure throughout the term of the RSPA. The RSPA is available on the PartnerSource Microsoft Dynamics NAV Registered Solution Program / Add-On Registration here The RSPA will still allow partners to manage their Microsoft Dynamics NAV Registered Solution Add-On modules in Voice with capabilities such as objects management, or access to run ISV reports. Please note that ISV Embed partners will need to sign the Microsoft Dynamics NAV Registered Solution Addendum but are not governed by the fee structure due to the ISV Embed contract fee structure superseding the RSPA There is an Exhibit A section to the Registered Solution Program Addendum that is used to capture the Registered Solution modules being made available on Microsoft Dynamics NAV Once a Registered Solution module is added to the Exhibit A section of the RSPA it becomes chargeable through a Registered Solution Program quarterly fee. Any Registered Solution module that is Certified for Microsoft Dynamics (CfMD) will be exempt from the quarterly fee. Any Registered Solution module that is registered with Lionbridge to become CfMD will have an object fee charge deferred allowing them 12 months to prove that their solution is compatible with Microsoft Dynamics either through the Software Solution Test or through the Application Services Track. The ISV will have 24 months in total from registering the solution for CfMD with Lionbridge to become certified, failure to achieve either of these two requirements will result in an object fee being charged. 3 MICROSOFT DYNAMICS Business-in-a-Box

4 The quarterly fee (charged for any Registered Solution that is not registered or passed CfMD with Lionbridge) is based on the number of unique Object ranges making up the Registered Solution s modules, it will be charged for the duration of the RSPA once Registered Solutions have been formally added to the RSPA Exhibit A. Invoices will be generated quarterly in November, February, May and August. The quarterly fee will be invoiced automatically for any eligible Registered Solutions. An example of the Registered Solution Program Quarterly Fee calculation is available on PartnerSource here and training video podcasts are available on PartnerSource here. The Registered Solution Program Quarterly Fee will be calculated as follows: Quarterly Per ISV Module objects corresponding to solutions that are CfMD are excluded. Number of objects included in an ISV solution are counted and charged. For each included module, the objects will be counted by Object type (e.g. Tables, Code Units etc.) Quarterly Fee will be calculated based on standard Microsoft Dynamics NAV 2013 object pricing multiplied by a factor of A SPA partner discount margin will not apply to the quarterly fee. Where the same object is used in multiple modules the partner only gets billed that object once Where the same object is in multiple modules and one module is CfMD the object will be free Any ISV s solution that has signed up to CfMD will be given 12 months to prove that the Registered Solution is compatible with the Microsoft Dynamics NAV 2013 software, the ISV will be given 24 months in all to become CfMD. If the solution is not fully CfMD within 24 months after signing up to CfMD the ISV will now be invoiced for the objects included in the Registered Solution modules added to customer licenses (limited to a maximum of ten customers). Please note that a 0.5 multiplier will apply to the fee. If a Registered Solution does not prove their compatibility with Microsoft Dynamics NAV 2013 within the 12 month period allowed the ISV will now be invoiced for the objects included in the Registered Solution modules that have been added to customer licenses (limited to ten customers). Please note that a 0.5 multiplier will apply to the fee and the Registered Solution will be made unavailable to add to new Microsoft Dynamics NAV2013 licenses or quarterly fees will be charged for the remainder of the RSPA term. If the registered solution is already a CfMD software solution, the object range of the solution may be expanded by 20%. Any additional increase in the number of objects beyond this limit will be charged by Microsoft. 4 MICROSOFT DYNAMICS NAV Registered Solution Program Guide

5 If CfMD is achieved for a module on Microsoft Dynamics NAV 2013 when it is added to the RSPA it will not be taken away during the term of the RSPA. Upon the 2 nd missed quarterly fee payment, the ability to register the Microsoft Dynamics NAV Registered Solution Add-On (s) for new sales may be removed. The Microsoft Dynamics NAV Add-On Addendum remains available, a Developing Partner must renew their Microsoft Dynamics NAV Add-On Addendum if they wish to continue creating and selling new MBL or BRL Microsoft Dynamics NAV Add-On s. Any Microsoft Dynamics NAV 2009 customer that has an Add-On included on their account and who is active on a current Business Ready Enhancement Plan (BREP) can upgrade to Microsoft Dynamics NAV 2013 and the Registered Solution Add-On will still be available on Microsoft Dynamics NAV 2013 license regardless of whether the Developing Partners has signed the RSPA. Adopting this approach will allow Developing Partners to avoid signing the RSPA until their current NAV Add-On Addendum is no longer available and can also avoid the Quarterly Fee until Microsoft Dynamics NAV 2009 is no longer available to purchase for new customers. Please be aware that once a customer license has been upgraded to Microsoft Dynamics NAV 2013 the Registered Solutions are visible in the Detailed Permission Report of the license file. 5 Certified for Microsoft Dynamics (CfMD) ISVs should be familiar with the Certified for Microsoft Dynamics program (CfMD). CfMD software solutions are independently tested, customer-verified, developed and supported by Microsoft Partners. CfMD Microsoft Dynamics NAV2013 Registered Solutions are not included in the Registered Solution Program Quarterly Fee quotation. When is a solution certified? A solution will be considered CfMD if the test report shows the solution as Pass for CfMD on the current or prior version. Lionbridge can advise Developing Partners on the status of their solution and are contactable through their website Lionbridge website or via mail at cfmd@lionbridge.com Once a Registered Solution achieves CfMD and is added to the RSPA it will be considered CfMD for the term of the RSPA. Annual fee deferral Any Microsoft Dynamics NAV 2013 Registered Solution that is registered with Lionbridge for CfMD is given 12 months to prove that their solution is compatible with Microsoft MICROSOFT DYNAMICS Business-in-a-Box

6 Dynamics NAV 2013, the solution is given 24 months from registering with Lionbridge to become CfMD. The fee pertaining to that module will be deferred for 24 months from the Lionbridge registration date. It is important that the ISV Partner includes details of the Registered Solution modules making up the Registered Solution. If the solution has not been proven as compatible with Microsoft Dynamics NAV 2013 within 12 months or is not fully CfMD within 24 months then the ISV will be invoiced for the objects in Registered Solution modules added to customer licenses (limited to a maximum of ten customers), a 0.5 multiplier will apply to the fee. An example of the fee is available on PartnerSource here and training video podcasts are available on PartnerSource here. Existing Add-Ons Existing ISV modules remain available to order on Microsoft Dynamics NAV 2009 and prior versions via the existing Microsoft Dynamics NAV Add-On program using the existing Module Based Licensing (MBL) and Business Ready Licensing (BRL) pricing models. The MBL and the BRL Add-On solution price for a Registered Solution also included in the RSPA will have the Order Central price set to zero. This means that any customer adding the MBL or BRL Add-On onto their license will not pay a charge for including it on a new license. If an existing BRL or MBL customer executes a LMT upgrade to Microsoft Dynamics NAV 2013, any Add-On modules that they owned will be available as a registered ISV module to register for that specific customer on the perpetual Microsoft Dynamics NAV 2013 product line. The Protected List Price (PLP) of the BRL or MBL Add-On will remain whilst the customer remains on Microsoft Dynamics NAV When the customer LMT upgrades to Microsoft Dynamics NAV 2013 the PLP of the Registered Solution will be removed. The Protected List Price of Add-On modules also covered by the Microsoft Dynamics NAV Registered Solution Program will not be carried over to Microsoft Dynamics NAV 2013 for customer performing a LMT upgrade. The Protected List Price (PLP) for the Add-On module will then be set to zero on the NAV 2013 license. If changes are made to a Microsoft Dynamics NAV Registered Solution module on Microsoft Dynamics NAV 2013, these changes will also impact existing customers as well as new. A partner gets to transition Microsoft Dynamics NAV Registered Solution Add-On object ranges for existing customers as long as the customer is on an active Business Ready 6 MICROSOFT DYNAMICS NAV Registered Solution Program Guide

7 Enhancement Plan. Even if the ISV has not signed the RSPA they NAV 2009 Add-On object range will be made available on NAV How to locate and submit the Registered Solution Program Addendum (RSPA) The Registered Solution Program Addendum is available on PartnerSource here There are three Regional Operation Centers (ROCs) each of which accepts addendums from partners based in their respective area and sent to the relevant partner s ROC at the following addresses: AOC Americas Operational Center Microsoft Dynamics Attn: SPA Processing One Lone Tree Road Fargo ND USA EOC EMEA Operational Center Microsoft Ireland Operations Ltd Attn: Microsoft Dynamics Contracts Team Microsoft Building 3 Carmanhall Road Sandyford Industrial Estate Dublin 18, Ireland. APOC - ASIA PACIFIC OPERATIONAL CENTER (APOC is divided into Three Geographical Regions) APOC except China & Japan(MRS) Microsoft Regional Sales (MRS) Corporation Attn: MS Dynamics Contracts Team 438B Alexandra Road #04-09/12 Block B Alexandra Technopark Singapore CHINA (MCCL) 16F Microsoft Dynamics Microsoft (China) Company Ltd Attn: Partner Development, Microsoft Dynamics Team 1st Floor, Microsoft Tower LSH Plaza, 8 Wangjing Street JAPAN (MSKK) Microsoft Japan Co., Ltd Attn: Microsoft Dynamics Operation Team (Gyomu Kanri bu) Shinagawa Grand Central Tower Konan Minato-ku, Tokyo Japan 7 MICROSOFT DYNAMICS Business-in-a-Box

8 Chaoyang District Beijing , PR China Registering a Microsoft Dynamics NAV Registered Solution Specific Microsoft Dynamics NAV Registered Solution modules can be added to the Exhibit A of the RSPA. Once the specific Microsoft Dynamics NAV Registered Solution modules have been included in the RSPA, it will be included for invoicing at the next quarterly invoice cycle (unless the Registered Solution modules are registered with Lionbridge for CfMD). Microsoft Dynamics NAV Registered Solution Billing Periods Quarterly invoices will be prepared in November, February, May and August for a Developing Partner that has signed the RSPA and included Registered Solution modules in the Exhibit A section that are not registered or passed CfMD. An example of the fee is available on PartnerSource here and training video podcasts are available on PartnerSource here. Proforma invoices will be sent 30 days prior to billing to provide Developing partners with a quote for the quarterly fee. ISV partners must arrange credit terms or prepay the quarterly fee charge to remain in the Registered Solution Program. Any ISV partner that does not provide payment terms for their quarterly fee within 90 days of an invoice being due may be terminated from the Registered Solution Program. Logging Queries The Microsoft Dynamics Registered Solution Program / NAV Registration page here holds the Registered Solution Program Guide, and other documents relating to the Microsoft Dynamics NAV Registered Solution Program. Queries relating to the Microsoft Dynamics NAV Registered Solution Program Addendum process may be logged through the Contracts team for the ROC s below: 8 MICROSOFT DYNAMICS NAV Registered Solution Program Guide

9 AOC: EOC: APOC: General queries relating to the Microsoft Dynamics NAV Registered Solution Program and the management of the Developing partner s Registered Solution may be submitted to the ROC Microsoft Dynamics Customer Operations Team through The Online Service Request Tool (MIMOS) which is a Web based tool used by Microsoft Dynamics Partners in the AOC and EOC only available on PartnerSource. (Please use the Registered Solution Program taxonomy) Limited User Registered Solutions The release of the next version of Microsoft Dynamics NAV will see the technical system enforcement of Limited Users for the first time which will limit the tables that a Limited User can write to, this is to align the product with the Software License Terms. A Limited User provides Write access to a maximum of three Tables in the object range 0 99,999,999 with no access to the General Ledger Table 17. Certain sub tables will be included in the license for the purpose of performing specific scenarios. The below tables included in the Limited User are taken from the Dynamics ERP Perpetual Licensing Guide on PartnerSource here. These are the included tables that do not count against the three application tables in the object range 0 99,999, This brings a new opportunity for ISV Partners who have particular Registered Solutions matching these limited scenarios (as described in the Dynamics ERP Perpetual Licensing Guide on PartnerSource here) wishing to take advantage of this Limited User type. MICROSOFT DYNAMICS Business-in-a-Box

10 A process has been designed to allow ISV s to make a formal request to Microsoft to make their Registered Solution compatible with the Limited User functionality by table objects being configured with the new (I) Included Object permissions. A Limited User Registered Solution Request Template has been designed and is available on PartnerSource here. This template is to be used to capture information from an ISV Partner and assist them in making a formal request to Microsoft for the approval of their Registered Solution to access Limited User functionality. Key information such as an overview of the Registered Solution, a detailed description of the tables and how the General Ledge table is accessed must be stated so that the Limited Usage scenario may be assessed and authorized. It is a prerequisite before submitting this document that the Limited User Registered Solution has been submitted to take the Software Solution Test. Passing the Software Solution Test is a requirement for a Limited User Registered Solution, failing the Software Solution Test will lead to the new (I) Included Table permission being returned to (O) Other. Assuming that no further information is required from the ISV Partner this request will be approved or rejected within a 10 day service level agreement. In order to request a Limited User Registered Solution please complete the Limited User Registered Solution Request Template available on PartnerSource here and ensure that the above requirements are met, once completed please submit this document to LURSR@microsoft.com. Once the request on the Registered Solution Request Template has been approved your Limited User Table Objects will be amended and you will receive a confirmation mail that you can complete the Software Solution Test. The Software Solution Test must be passed, if the solution fails the Table Object permissions will be reset. Once passed add the Registered Solution to the Exhibit A of the Registered Solution Program Addendum, details of the process are contained in the Registered Solution Program Guide available on PartnerSource here. The new Limited User table permissions will only be available once the new NAV 2013 release 7.1 has been launched, at this time the Software Solution Test may be completed. Should you wish to submit your Registered Solution to be approved as a Limited User scenario please complete the above steps. 10 MICROSOFT DYNAMICS NAV Registered Solution Program Guide

11 ISV Partners providing localization for a CfMD Registered Solutions If an ISV partner has created a Registered Solution to provide localization for a specific Certified for Microsoft Dynamics (CfMD) solution of another ISV partner, then the quarterly fees relating to the localized Registered Solution will be waived. The CfMD ISV Partner will need to notify Microsoft (per the notification terms contained in the RSPA) of the ISV partner providing the localization module, the localizations module description as well as contact details for the localization partner. After this notification, the ISV partner must sign the RSPA and include the solution in the Exhibit A section of the agreement. Any localization of a Registered Solution related to a Limited User Registered Solution must pass the applicable Software Solution Test with Lionbridge in order to establish that none of the restricted tables are being accessed. Any waiver that is offered to the localization partner for the Registered Solution providing the localization will be honored for the two year term of their RSPA. How to Register a Microsoft Dynamics NAV 2013 Registered Solution to a customer s license An ISV Registered Modules link has been added to a customer s account in Voice as per the below screenshot: 11 MICROSOFT DYNAMICS Business-in-a-Box

12 Once the link is selected the below screen appears: 12 MICROSOFT DYNAMICS NAV Registered Solution Program Guide

13 It s now possible to search for the Microsoft Dynamics NAV Registered Solution before ticking the tick box against and clicking the Register Selected Modules button to register the Microsoft Dynamics NAV Registered Solution against the customer s account. Please note that any Add-On that is being added to a BRL or MBL license can be ordered via the Pricing Catalogue in Order Central. Any BRL or MBL Add-On that is included under the Registered Solution Program will be free of charge and any BRL or MBL Add-On not included under the Registered Solution Program will be charged at 30% of the ISV market price. Frequently Asked Questions What is a Microsoft Dynamics NAV Registered Solution Add-On Application? Microsoft Dynamics NAV Registered Solution Applications are ISV software applications, independently developed by a Microsoft Partner, that are enabled when used in conjunction with Microsoft Dynamics NAV. Microsoft Dynamics NAV Registered Solution Applications are software solutions that complement and supplement the functionality found in Microsoft Dynamics NAV, and can be delivered and implemented for multiple customers. Microsoft Dynamics NAV Registered Solution Applications may address an industry-specific need (vertical solutions) or general business processes (horizontal solutions). It is not possible to include any of the existing Microsoft Dynamics NAV functionality, technology or users in a Microsoft Dynamics NAV Registered Solution Application. Those items must be purchased separately. There are two aspects related to a Microsoft Dynamics NAV Registered Solution application. First, the Registered Solution base is the Microsoft code that enables the Registered Solution to work with the Microsoft Dynamics NAV core product. Second, is the solution developed by the ISV (referred to as the Registered Solution application). 13 MICROSOFT DYNAMICS Business-in-a-Box

14 Why should Microsoft Dynamics Certified Partners focus on Microsoft Dynamics NAV Registered Solution Program Applications? A major reason for partners to focus on Microsoft Dynamics NAV Registered Solution Applications is to drive revenue, market share and to build customer loyalty. Selling the same functionality to several customers means much faster implementation, reduced development costs, and ultimately better use of resources. It also means that partners can focus on particular groups of customers and become better at serving these types of customers. This also means that the customers can gain more value from the software solution that they choose. What are the requirements to be able to develop a Microsoft Dynamics NAV Registered Solution Program Application? For Developing Microsoft Dynamics Partners responsible for the Microsoft Dynamics NAV Registered Solution Program Application willing to sell the solution themselves, it is required to sign and submit the following addendums to their local Microsoft Regional Operations Centre: Solution Provider Agreement (SPA) Registered Solution Program Addendum (RSPA) All of these documents can be downloaded from the Microsoft Partner Network site. If the Developing Microsoft Dynamics Partner who is responsible for the Microsoft Dynamics NAV Registered Solution Application is only developing the solution and not selling Microsoft Dynamics NAV to customers themselves, they are required to execute the following agreements to their local Microsoft Regional Operations Centre (ROC): Microsoft Dynamics Partner Registration Agreement Registered Solution Program Addendum All of these documents can be downloaded from the Microsoft Partner Network site. Please fill-out the documents and send to the appropriate ROC. How is a Microsoft Dynamics Registered Solution application developed? A Microsoft Dynamics NAV Registered Solution Application consists of a number of objects. The currently available objects are; Tabledata, TableDescription, Pages, Reports, XMLPorts, and Codeunits. These objects are building blocks or templates that a partner can use when developing a solution. The partner can even re-use objects in different 14 MICROSOFT DYNAMICS NAV Registered Solution Program Guide

15 solutions. Microsoft does not own the content of the objects. The developing partner owns the Intellectual Property (IP) rights of his solutions and is thereby also responsible for distributing and protecting its IP. If the developing partner wants to resell its solution, it will have to distribute the bits and bytes to the relevant reselling partners. It is the responsibility of the developing partners to ensure that their Microsoft Dynamics NAV Registered Solution application is only distributed to eligible persons and organizations. The Microsoft license keys only provide the access to the relevant parts of the Microsoft software. What is an Object Range? An object range is a series of unique object numbers that are assigned to a specific partner for their Microsoft Dynamics NAV Registered Solution application to access the licensed software. Object ranges are assigned by Microsoft to individual partners and cannot be shared. Microsoft owns the object range. When an ISV develops a Microsoft Dynamics NAV Registered Solution Application for Microsoft Dynamics NAV, they will need to get access to a certain number of objects with which they can build their solution. In order to avoid overlap between objects used in different solutions, each Developing Partner is assigned a number of objects in a unique object range. For example, a Danish partner could get assigned the object range 6,000,700 6,000,799 which will give them 99 numbered objects they can use to develop one or more Microsoft Dynamics NAV Registered Solution. What are object/module permissions? In order for a partner to develop a solution (and for an end-customer to run them) their license key needs to contain the proper permissions. Each object which the Developing Partner is using for their solution needs to have its own ID assigned to it, meaning that each object can be uniquely identified by its ID and its type. The license key is used to determine the access rights to these objects. We generally distinguish between 5 different types of access: Read (R), Insert (I), Modify (M), Delete (D), and Execute (X). 15 MICROSOFT DYNAMICS Business-in-a-Box

16 It is possible to give specific access rights to a single object or an object range. Microsoft Dynamics NAV groups the access rights to different objects into a single entity called a module (formerly called a granule). Said otherwise, a module is a collection of permissions to the objects which are covered by the module. For example: Permissions can be given as direct access (Uppercase) or indirect access (Lowercase). Indirect access means that access is from another object, such as a report or code unit. The following combinations are common: R-MDX (standard except for Tabledata) RIMD- (standard for Tabledata) Rimd (for specially protected Tabledata, such as: TableData in table 17, GL entries and other posting tables) RimD (such as 110 sales shipment header) R---- (read only) -----X Execute only as in the demonstration license. What are Insert or Development permissions to a Microsoft Dynamics NAV Registered Solution Module? Let s now take a look at the object permissions required by the partner to develop their Microsoft Dynamics NAV Registered Solution solution in the first place. A Developing Partner would need to have full insert or creator access to the objects they want to build their solution with. Referring to the permission overview above, this means that RIMDX is required for all those objects they want to use. Microsoft grants insert permissions to all objects within the Developing Partner s unique object range to the Developing partner on their demo/dev license. This means that all objects will have the permission RIMDX, with the exception of TData (TableData) which has RIMD. 16 MICROSOFT DYNAMICS NAV Registered Solution Program Guide

17 If a partner is set-up as the ISV Provider (i.e. developing partner) for a Microsoft Dynamics NAV Registered Solution module, the insert permissions for the associated Microsoft Dynamics NAV Registered Solution object range are automatically added to their demo/dev license. What are Execute permissions to a Microsoft Dynamics NAV Registered Solution Module? If a partner is set-up as an authorized reseller for an Microsoft Dynamics NAV Registered Solution module, the execute permissions for the associated Microsoft Dynamics NAV Registered Solution object range are automatically added to their demo/dev license the next time it is downloaded. Execute permissions are needed for support purposes for example when identifying whether an issue is related to a Microsoft Dynamics NAV Registered Solution Application or the Microsoft Dynamics NAV base product. The Execute permissions are therefore included in the demo/dev license of the reselling Partner. This technically gives modification access to the objects of the Microsoft Dynamics NAV Registered Solution Application where the reselling partner needs to customize such applications before installing. Execute permissions gives full modify access to the objects. All the objects in the Microsoft Dynamics NAV Registered Solution Module object range have permission R-MDX. The Execute permissions are different than the permissions in end-user Microsoft Dynamics 17 MICROSOFT DYNAMICS Business-in-a-Box

18 NAV Registered Solution modules by granting access to all the objects within this object range, whereas the end-user module gives access to released objects only. It enables the partner to work with beta releases. A Reselling Partner has to receive the bits & bytes of the solution from the Developing Partner and get the Execute permissions on their demo/dev license by Microsoft. This is only done when approved by the Developing Partner. Note that the reseller gets execute access to the entire object range that has been assigned to the Developing Partner, so if multiple Microsoft Dynamics NAV Registered Solution have been developed within the same range, the reselling partner gets access to all these Microsoft Dynamics NAV Registered Solutions. What is an End-User Microsoft Dynamics NAV Registered Solution Module? In order for an end-customer to run the Microsoft Dynamics NAV Registered Solution solution in conjunction with Microsoft Dynamics NAV, the necessary access permissions need to be included in the customer s End-User License Key. Once the partner has completed their development, they contact Microsoft stating exactly which objects are used for a specific Microsoft Dynamics NAV Registered Solution solution and for these objects an Microsoft Dynamics NAV Registered Solution module is created the End-User Module. The access permissions of the objects covered by the End-User Module are decided by the Developing Partner and specified in Phase 3 of the Microsoft Dynamics NAV Registered Solution Program Request Form. It is possible for the partner to have their Microsoft Dynamics NAV Registered Solution solution split into multiple End-User Modules allowing for a modular solution the Developing Partner decides how the solution should be packaged in terms of modules. The end-customer will have to purchase the respective module from Microsoft in order to use the corresponding Microsoft Dynamics NAV Registered Solution bits & bytes delivered by the reselling Partner. 18 MICROSOFT DYNAMICS NAV Registered Solution Program Guide

19 Developing Partners can add and update object permissions for their Microsoft Dynamics NAV Registered Solution Program module in VOICE using the Manage Objects screen. More information here. How are the Microsoft Dynamics NAV Registered Solution object range permissions added to the demo/developer license determined? If a partner is set-up as the ISV Provider (i.e. developing partner) for a Microsoft Dynamics NAV Registered Solution module, the insert permissions for the associated Microsoft Dynamics NAV Registered Solution object range are automatically added to their demo/developer license. If a partner is set-up as an Authorized Reseller (i.e. has the permission to order the Registered Solution) for a Microsoft Dynamics NAV Registered Solution module, the execute permissions for the associated Microsoft Dynamics NAV Registered Solution object range are automatically added to their demo/developer license. I have made some changes to my Microsoft Dynamics NAV Registered Solution objects but they are only reflected in the MBL (module based licensing) version of the module. Why is this? When updating objects, please make sure to update both the MBL (Microsoft Dynamics NAV product line), BRL (Microsoft Dynamics NAV Business Ready product line) and Perpetual versions of the module. You will find additional FAQs regarding this functionality in the VOICE Registered Solution Self Service Partner Guide. What type of license is required for development? Microsoft Dynamics NAV Partner Demonstration & Development License Target group(s): Reselling partners and developing partners Purpose: To provide an environment for customization or development. Who can configure this license: The demo/dev license can be downloaded by the partner from the License Key Configurator (LKC) Tool on VOICE under Developer Tools. IMPORTANT: It is necessary to have the appropriate agreements in place in order to be able to access the LKC Tool on VOICE. 19 MICROSOFT DYNAMICS Business-in-a-Box

20 To view/download license files in VOICE you need to have specific VOICE Account setting. Your VOICE Administrator can set this up for you in VOICE > Organization > All Professionals > click into your profile > edit your profile for License Key Configuration Access to Full. Expiration Date: This will expire in line with your Microsoft Solution Provider Agreement (SPA) or Microsoft Dynamics Partner Registration Agreement, the license file will display a pop-up message at the time of renewal. Price: A demo/dev license key and the included objects have no cost to Microsoft Dynamics partners. Basic level of access: The license key gives access to all global and local application and platform components including the standard tools. Furthermore, developing partners have insert permissions to their Microsoft Dynamics NAV Registered Solution included in the RSPA on their demo/developer license. Reselling partners have execute permissions for the Microsoft Dynamics NAV Registered Solution object range(s) for which they are authorized on their demo/developer license. The demo/developer license can be downloaded by the partner from the License Key Configurator (LKC) Tool on VOICE under Developer Tools. It is necessary to have the appropriate agreements in place in order to be able to access the LKC Tool on VOICE. To view/download license files in VOICE you need to have specific VOICE Account setting. Your VOICE Administrator can set this up for you in VOICE > Organization > All Professionals > click into your profile > edit your profile for License Key Configuration Access to Full How can a Partner register their Microsoft Dynamics NAV Registered Solution Program Solution? Each Developing Partner needs to follow the steps outlined below to successfully register their new Microsoft Dynamics NAV Registered Solution Application: Prerequisites: The Developing Microsoft Dynamics Partner must execute the relevant agreement. Business Plan:. Microsoft strongly recommends completing a Business plan to assist in the planning of development, sales and support of the Microsoft Dynamics NAV Registered Solution Program Application. The Developing Partner can download the Business Plan Template and Guidelines from PartnerSource. The partner may fill out the Business Plan 20 MICROSOFT DYNAMICS NAV Registered Solution Program Guide

21 Template and present it to the local Microsoft subsidiary for review and business planning discussion. The subsidiary PMM (representing the principle market in which the Developing Partner is located) reviews the business plan and engages in discussions with the Developing Partner. Step 1. The partner downloads the Request Form from PartnerSource. The partner must complete Phase 1 of the Request Form and send the documents to the appropriate ROC. Contact Microsoft Dynamics Operations Step 2. The ROC receives the Microsoft Dynamics NAV Registered Solution Program Add-On Request Form, validates it and assigns an object range to the developing partner (if one has not already been assigned). It may take up to 3 working days to complete this step. Step 3. The partner develops the Microsoft Dynamics NAV Registered Solution Application and when finalized, updates the Request Form Phase 3 and returns it to the ROC for creation of the Microsoft Dynamics NAV Registered Solution Program Module(s). It may take up to 8 working days to complete this step. Step 4. The ROC notifies the Partner that the solution has been registered by sending them (via ) a copy of the finalized Microsoft Dynamics NAV Registered Solution Program Add-On Request Form. How do I fill out the Microsoft Dynamics NAV Registered Solution Program Add-On Request Form? The Microsoft Dynamics NAV Registered Solution Add-On Request form can be found on the Add-On Registration Page on PartnerSource. The following section describes how to complete each section of the Microsoft Dynamics NAV Registered Solution Add-On Request Form: 21 MICROSOFT DYNAMICS Business-in-a-Box

22 Microsoft Dynamics NAV Registered Solution Application Name The name of the Microsoft Dynamics NAV Registered Solution application Developing Partner Details Developing partner contact details for the Microsoft Dynamics NAV Registered Solution application Comments the comments field can be used to provide any specific instructions related to the request. 22 MICROSOFT DYNAMICS NAV Registered Solution Program Guide

23 Enter Module Details for each Microsoft Dynamics NAV Registered Solution Module In the first section the module details must be provided for the Microsoft Dynamics NAV Registered Solution module: Module Name Associate Module to the Microsoft Dynamics ISV Embed Agreement (Yes / No) Specify Object Permissions In the second section, please specify the object permissions. 23 MICROSOFT DYNAMICS Business-in-a-Box

24 Creating new MBL and BRL Microsoft Dynamics NAV Add-Ons To create a new MBL or BRL Microsoft Dynamics NAV Add-On the WW Microsoft Dynamics NAV Add-On Request Form from PartnerSource here For as long as a partner has an active Microsoft Dynamics NAV Add-On Addendum it s possible to set up a new Microsoft Dynamics NAV Add-On without setting it up on NAV Once the Microsoft Dynamics NAV Add-On Addendum has expired or has been superseded by the Registered Solution Program Addendum it is only possible to create a new MBL or BRL Add-On once the Registered Solution Add-On has been set up on NAV 2013 first. Creating a new Subscription and C5 Registered Solution Before a Registered Solution can be set up for Subscription or C5 it must first be set up on NAV 2013 Perpetual and included on the RSPA. Phase 3 of the Microsoft Dynamics NAV Registered Solution Add-On Request form must be completed for Perpetual licensing first along with a Subscription or a C5 Registered Solution. 24 MICROSOFT DYNAMICS NAV Registered Solution Program Guide

25 Once the Registered Solutions have been created they can be made available to add to a customer s license when they are added to the Exhibit A of the Registered Solution Program Addendum. In order for the Subscription or C5 Registered Solution to be made available to add to a customer s license all relevant versions (Perpetual, Subscription / C5) of the Registered Solution must be included on the Exhibit A section of the Registered Solution Program Addendum (RSPA). Only the Perpetual Registered Solution will potentially be included within any Registered Solution Program quarterly fees. Can you still bundle Registered Solutions with NAV 2013 Perpetual in the same manner as MBL and BRL? There is a change in how Registered Solution are systematically managed in NAV With NAV 2013 there are also some system changes which will see a move away from of managing SKUs, Pricing, availability, and relationships With the new RSP program the only system relationship that is available for ISV Modules is the new ISV Requires relationship. This is used to require specific localizations for a particular ISV module (i.e. module A is only available with US, DE, DK localizations). ISVs will be able to self serve and make these changes to their modules on their own using VOICE in an upcoming release. On NAV 2013 we will no longer be able to use Unlock relationships as was seen on MBL and BRL. This is how the system manages MBL and BRL: Set up individual modules A, B, C, and D (including their respective objects) Set up module E to Include module A and B (Bundle) Set up module F to Include module C and D (Bundle) The Included modules would show up independently on the license file as Included With NAV 2013 the same objective is accomplished as follows: 25 Module E is set up by importing all of the objects from module A and B into this module. Module F is set up by importing all of the objects from module C and D into this module. Module A and B no longer show up on the license file as independent modules as included in the parent module, but all of the objects are available. MICROSOFT DYNAMICS Business-in-a-Box

26 Can you prevent a customer that has purchased application builder and solution developer modules (7200, 7300), from modifying a Microsoft Dynamics NAV Registered Solution application? Yes, this is possible. You will have to create the Microsoft Dynamics NAV Registered Solution module different from standard, by limiting the permissions granted to the objects in the end-user Microsoft Dynamics NAV Registered Solution module. An example: Microsoft Dynamics NAV Registered Solution module AAA has the following standard object permission: TableData permission RIMD- TableDescription permission R-MDX Form permission R-MDX CodeUnit permission R-MDX Report permission R-MDX To remove development access you must change to limited permission as follows: TableData permission RIMD- TableDescription permission ----X Form permission ----X CodeUnit permission ----X Report permission ----X Please make the necessary changes in VOICE using the Manage Objects screen. More information here. I wish to change my Microsoft Dynamics NAV Registered Solution module, who should I notify? Many changes can now be made through VOICE rather than having to contact the Regional Operations Centre (ROC). It is now possible for a Microsoft Dynamics NAV Developing Partner to control systematically which reselling partners are allowed to place orders for their Registered Solutions with Microsoft. This feature is available externally for Developing Partners in VOICE. It is now also possible for a Microsoft Dynamics NAV Developing Partner to manage the objects for their Microsoft Dynamics NAV Registered Solution modules in VOICE. This means that a partner can add new objects to their Microsoft Dynamics NAV Registered Solution module, remove objects or change object permissions directly without needing to contact Microsoft. These changes take effect in the system immediately and will be reflected in the end customer license the next time that it is downloaded from VOICE. 26 MICROSOFT DYNAMICS NAV Registered Solution Program Guide

27 More Details are available in the VOICE Registered Solution Self Service Partner Guide. Please note that the following types of edits cannot be completed online by partners. They can only be completed by the Regional Operations Centre (ROC): Register a new Microsoft Dynamics NAV Registered Solution module Change the country availability of the Microsoft Dynamics NAV Registered Solution Change the module relationships (i.e. pre-requisites) Change Microsoft Dynamics NAV Add-On module pricing Change Microsoft Dynamics NAV Registered Solution module name Request an extended object range Set user limits on an Microsoft Dynamics NAV Registered Solution module When changes to an existing Microsoft Dynamics NAV Registered Solution Program Module are required that cannot be completed in VOICE, the partner should use the original Microsoft Dynamics NAV Registered Solution Add-On Request Form. Phase 3 should be updated with the changes and the partner should mark these changes either by highlighting the lines and/or adding a comment on Phase 1. When this is complete they should send the document to the appropriate ROC, who will update the Microsoft Dynamics NAV Registered Solution Module(s). The ROC will inform the Partner that the update is complete and return the updated request form to the Partner. It may take up to 5 working days to change an existing Microsoft Dynamics NAV Registered Solution Program module. What is the difference between Microsoft Dynamics NAV Localized version availability and Country Availability on the new Microsoft Dynamics NAV Registered Solution Program Add-On Request Form? In the Microsoft Dynamics NAV Localized Version Availability section, the partner must indicate the Microsoft Dynamics NAV localized versions with which the Microsoft Dynamics NAV Registered Solution Program should be made available. For a full list of these, see the Country Code dropdown list on the Microsoft Dynamics NAV pricelist. By default the solution will be made available for the W1 version and the localized version corresponding to the developing partner country. If the partner would like to make the Microsoft Dynamics NAV Registered Solution available with all Microsoft Dynamics NAV localized versions, they should type 'ALL in this section. In the Customer Country Availability section, the partner must indicate the countries in which the Microsoft Dynamics NAV Registered Solution should be made available. By default, the Microsoft Dynamics NAV Registered Solution will be made available to order 27 MICROSOFT DYNAMICS Business-in-a-Box

28 in all countries. If the partner would like to restrict availability of their Microsoft Dynamics NAV Registered Solution to certain countries, they should list the countries in this section. What is the role of the developing partner? The developing partner is the partner who owns the Intellectual Property (IP) rights to the solution. The partner is solely responsible for: Developing the solution Signing the required documentation This will vary depending on whether the partner will just develop a solution or whether the partner wants to develop and sell the solution also. Completing the business case, if required by the Microsoft subsidiary Registering the solution with the local Regional Operations Centre (ROC) Marketing the solution to the market place Upgrading and supporting Microsoft Dynamics NAV Registered Solution Application Developing and executing an agreement with their Reselling partners Granting the reselling partner access to the Microsoft Dynamics NAV Registered Solution module (formerly called granule) Protecting the Intellectual Property (IP) rights of their solution in the market place What is the role of the reselling partner? The partner selling the Microsoft Dynamics NAV Registered Solution Application to the end customer may be the Developing Partner of the Microsoft Dynamics NAV Registered Solution Application, but in some cases the Developing Partner may decide to resell the solution through other partners. The reselling partner s primary responsibilities are to: Sign the Microsoft Solution Provider Agreement (SPA) Sign a contract with the developing partner Sell the Microsoft Dynamics NAV Registered Solution solution in the market place 28 MICROSOFT DYNAMICS NAV Registered Solution Program Guide

29 What is the role of the Regional Operations Centre? There are 5 Regional Operations Centers (ROCs): The ROC is responsible for: Checking that the developing partner has signed the appropriate documents (whether a reselling or non-reselling developing partner). Assigning an object range to the developing partner. This allows the partner a range within the Microsoft NAV product in which he can develop his solution. Registering the partner solution as a Microsoft Dynamics NAV Registered Solution Module. Registering Microsoft Dynamics NAV Registered Solution modules on customer accounts. Please note that this is not the full solution, just access to the Microsoft Dynamics NAV objects that need to be added to the customer s license in order for the solution to work. 29 MICROSOFT DYNAMICS Business-in-a-Box

30 What is the role of the Microsoft subsidiary? Dynamics Partners and customers should not be under the impression that Microsoft Dynamics has authorized or certified the Microsoft Dynamics NAV Registered Solution Application. Certification can only be obtained through the CfMD process. Furthermore, it is essential that customers understand that Microsoft Dynamics does not control the development of the Microsoft Dynamics NAV Registered Solution Application and that Microsoft Dynamics does not take any responsibility for supporting or upgrading either customizations or Microsoft Dynamics NAV Registered Solution Applications. When working with Reselling partners or end customers, it is important to make sure they are informed of the nature of the development entity. The local Microsoft subsidiary may assist the Developing Microsoft Dynamics Partner as follows: Post the relevant Microsoft Dynamics NAV Registered Solution information on its website Develop the business plan together with the partner as required. Partners invest a lot of R&D in developing solutions, however without good business planning, the partner can face heavy losses and never get their solution into the market Educate the partners on the benefits and best practices of the process Ensure the partner completes the necessary documentation. Liaise with the Regional Operations Centre to assist the partner to register their solution as a Microsoft Dynamics NAV Registered Solution Module (formerly called a granule). The key contact in each subsidiary is the Microsoft Dynamics NAV Product Marketing Manager (PMM). Who is responsible for handling license configuration or pricing issues? Please contact your Regional Operation Centers with any license configuration or pricing issues. Various options of submitting your query or request to the ROC s are available on Partner Source here: 30 MICROSOFT DYNAMICS NAV Registered Solution Program Guide