Download pdf - Using the Microsoft Dynamics NAV RIM Toolkit and the ... · Using RapidStart Services for Microsoft Dynamics NAV and the Microsoft Dynamics Sure Step Methodology White Paper This

Using RapidStart Services for Microsoft Dynamics NAV and the Microsoft Dynamics Sure Step Methodology

White Paper

This paper illustrates how a Dynamics NAV implementation project based on the Microsoft Dynamics Sure Step methodology can take advantage of RapidStart Services for Microsoft Dynamics NAV.

Date: June 2012

USING RAPIDSTART SERVICES FOR MICROSOFT DYNAMICS NAV AND THE MICROSOFT DYNAMICS SURE STEP

METHODOLOGY

Executive Summary ...................................................................................................................... 4

Microsoft Dynamics Sure Step Methodology ............................................................................ 5

RapidStart Services for Microsoft Dynamics NAV ................................................................... 6

Data Migration .............................................................................................................................. 6

Data Packages ................................................................................................................................ 6

Questionnaires .............................................................................................................................. 7

Project Planning capabilities .......................................................................................................... 7

Sure Step and RapidStart Services for Microsoft Dynamics NAV ......................................... 7

Sure Step – the Data Migration Cross-Phase Process ............................................................. 8

Sure Step – the Diagnostic Phase and the RapidStart Services for Microsoft Dynamics

NAV............................................................................................................................................... 10

The Fit Gap and Solution Blueprint activity (0.3) .......................................................................... 10

The Proof of Concept activity (0.4) ............................................................................................... 11

The Project Planning activity (0.9) ................................................................................................ 11

Sure Step – Project Types, Phases and Activities ................................................................... 12

Sure Step – the Analysis Phase and the RapidStart Services for Microsoft Dynamics NAV

....................................................................................................................................................... 13

The Conduct Detailed Business Process Analysis activity (1.3.1) ................................................... 13

The Build Sandbox and Training Environments activity (1.7.1) ..................................................... 14

The Gather Data Migration Requirements activity (1.9.1) ............................................................ 14

Sure Step – the Design Phase and the RapidStart Services for Microsoft Dynamics NAV

....................................................................................................................................................... 15

The Begin System Configuration and ISV Solution Setup activity (2.4.1) ....................................... 15

The Conduct Feature Testing of Standard and ISV Solution activity (2.6.1) ................................... 16

The Begin Data Migration Design activity (2.9.1) .......................................................................... 16

The Create a Subset of Data for Testing activity (2.9.2) ................................................................ 17

Sure Step – the Development Phase and the RapidStart Services for Microsoft Dynamics

NAV............................................................................................................................................... 18

The Conduct Solution Testing activity (3.6.1) ............................................................................... 18

The Begin Development of Data Migration Scripts activity (3.9.1) ................................................ 19

Sure Step – the Deployment Phase and the RapidStart Services for Microsoft Dynamics

NAV............................................................................................................................................... 20

The Execute User Acceptance Testing activity (4.6.1) ................................................................... 20

The Build Production Environments activity (4.7.1) ...................................................................... 21


METHODOLOGY

The Final Data Migration to PROD activity (4.9.1) ........................................................................ 21


METHODOLOGY

Executive Summary

This whitepaper illustrates how a Dynamics NAV implementation project based

on the Microsoft Dynamics Sure Step methodology can take advantage of

RapidStart Services for Microsoft Dynamics NAV.

Most Microsoft Dynamics NAV implementations will involve some level of data

migration. The data migration features in RapidStart Services for Microsoft

Dynamics NAV supports all the cross phase data migration processes defined in

Sure Step.

Other parts of RapidStart Services for Microsoft Dynamics NAV, such as the Data

Templates used when creating a company and the Questionnaires, make it easy

for partners to configure tailored companies during Sure Step phases where it is

required to perform workshops for demo, proof of concept, or user

acceptance/training.

When Data Templates and Questionnaires are modified and extended to cover

ISV solutions and specific solution segments, they are also usable for Sure Step

phases and activities related to system configuration of ISV solutions.

The project planning capabilities in RapidStart Services for Microsoft Dynamics

NAV can be used to benchmark the project planning activities in Sure Step.

The RapidStart Services for Microsoft Dynamics NAV should be considered for all

project types defined in Sure Step, except the upgrade project type. RapidStart

Services for Microsoft Dynamics NAV adds value to all Sure Step phases, except

the Operation phase, by supporting the following Sure Step cross phase

processes:

Data Migration

Quality and Testing

Requirements and Configuration.

RapidStart Services for Microsoft Dynamics NAV enables greater partner

productivity by reducing the time required for several Sure Step implementation

activities and processes.


METHODOLOGY

Microsoft Dynamics Sure Step Methodology

The Microsoft Dynamics Sure Step Methodology is a comprehensive

implementation methodology describing the processes and disciplines necessary

to implement Microsoft Dynamics products, including Microsoft Dynamics NAV.

Partners who fully adopt and embrace Sure Step will be able to better perform

customer implementations on time, on budget and on spec.

Sure Step covers a flow of implementation activities that lead from the initial

business diagnosis to implementation and hand-off to operations. The

implementation activities are divided into six phases and are supported by nine

cross phase processes.

Figure 1 Microsoft Dynamics Sure Step Methodology

Sure Step differentiates between four project types:, one is related to upgrade and

the others are related to new implementation with scope varying from Rapid to

Enterprise.

RapidStart Services for Microsoft Dynamics NAV should be considered for all

project types defined in Sure Step, except the upgrade project type. RapidStart

Services for Microsoft Dynamics NAV adds value to all phases, except the

Operation phase, by supporting the Data Migration, Quality and Testing, and

Requirements and Configuration cross phase processes.


METHODOLOGY

RapidStart Services for Microsoft Dynamics NAV

RapidStart Services for Microsoft Dynamics NAV helps partners reduce

implementation time by automating and simplifying the recurrent processes in an

implementation project.

RapidStart Services for Microsoft Dynamics NAV quickly configures core

application setup data to meet specific business needs using tailored templates.

The templates are provided by Microsoft Dynamics NAV and are extended and

enriched by partners, to share best practices and solutions within the Microsoft

Dynamics NAV ecosystem.

RapidStart Services for Microsoft Dynamics NAV consists of the following

components, which are applicable when using the Sure Step implementation

methodology:

Data Migration with Import/Export functions

Data Packages with Generic Setup Data

Questionnaires

Project Planning capabilities including Project Overview

Data Migration

You use the Data Migration component to migrate:

Basic Setup Data from your legacy system, such as Customer and Vendor

Posting Groups, Shipment Methods, and so forth

Master Data records, such as Chart of Accounts, Customer, Vendors, and

Items

Open Transactions and Balances, such as Open Invoices and Unprocessed

Orders, and Inventory

The Data Migration process typically involves exporting tables and fields from

Microsoft Dynamics NAV to Microsoft Excel. There the legacy data is transformed

and mapped before it is imported back, validated, and applied.

Data Packages

The Data Package component includes Basic Setup Data for configuration of a

new company. A template can be applied when a new company is created in

Microsoft Dynamics NAV. Microsoft provides one template, but it can be modified

and extended by partners to cover ISV solutions and specific solution segments.

Data Packages are based on configured companies in Microsoft Dynamics NAV


METHODOLOGY

that are exported to XML and made available to be used as templates when a

new company is to be created. Data Packages can also be applied to an existing

company when a new application areas need to be configured.

Questionnaires

The Questionnaires guide the user through the setup process and collect answers

in order to configure all relevant setup tables. The questionnaires can be exported

to Microsoft Excel or XML and once all questions have been answered, it is

possible to import the questionnaires, and validate and apply answers. It is also

possible to define default answers to indicate best practices to guide the user..

Project Planning capabilities

RapidStart Services for Microsoft Dynamics NAV also has the capability to set how

is responsible for the setup of a table, this gives the possibility to get an overview

of the project status.

Sure Step and RapidStart Services for Microsoft Dynamics NAV

This whitepaper will not explain the Sure Step Methodology or RapidStart

Services for Microsoft Dynamics NAV in detail and assumes that the reader is

somewhat familiar with them. To get a more thorough understanding and

guidance, you can use resources available on PartnerSource.

Sure Step Resources

There are several resources including a user’s guide, case studies, overviews, fact

sheets, and more available to help provide more information about Sure Step.

Visit Sure Step on PartnerSource.

RapidStart Services for Microsoft Dynamics NAV Resources

There are several resources including a user’s guide, case studies, overviews, , and

more available to help provide more information about RapidStart Services for

Microsoft Dynamics NAV. Visit the Drive Down The Number of Deployment Days

on PartnerSource.

https://mbs.microsoft.com/partnersource/partneressentials/serviceplans/surestep/

https://mbs.microsoft.com/partnersource/deployment/documentation/howtoarticles/MSDNAVDriveDownDeplymet.htm


METHODOLOGY

Sure Step – the Data Migration Cross-Phase Process

The cross-phase process Data Migration is the most obvious area where partners

can take advantage of RapidStart Services for Microsoft Dynamics NAV. The

strong Data Migration capabilities are useful in all phases except the Operation

phase.

Figure 2 Sure Step: Data Migration Cross-Phase

Most Microsoft Dynamics NAV implementations will involve some level of data

migration. Data Migration is crucial to implementation success.

It is highly recommended to start planning for data migration early in the

implementation project. Without well-planned, tested, and validated data

migration processes, new solutions can fail because legacy components introduce

risks that were never accounted for during planning. It is also important to gain a

customer commitment to allocate appropriate resources to work with the

consulting team on data mapping and defining the necessary data conversions.

The analysis of data migration involves identifying the source systems and the

overall data requirements for each of these source systems.

Using RapidStart Services for Microsoft Dynamics NAV it is not required to

develop conventional data migration scripts. The only requirement is to get the

customer/legacy data into an Excel spreadsheet in its raw format. Once in Excel, it

is a best practice to maintain the data in its original form in one sheet, perform


METHODOLOGY

the data transformation and mapping in another sheet, and then to migrate the

data in a third sheet.

How to apply the Data Migration and other components of RapidStart Services

for Microsoft Dynamics NAV will be described under each phase, starting with the

Diagnostic phase.


METHODOLOGY

Sure Step – the Diagnostic Phase and the RapidStart Services for

Microsoft Dynamics NAV

The purpose of the Diagnostic phase is to gather enough information to define

the high-level project charter and to make a confident proposal for the

implementation phases. The Diagnostic phase starts during the sales process and

ends with an accepted proposal and statement of work (SOW) for the next part of

the implementation project. The major deliverable for this phase is the SOW and

the Budgetary Estimate Proposal.

Figure 3 Sure Step activities in the Diagnostic phase where the RapidStart Services for Microsoft

Dynamics NAV is applicable

The Fit Gap and Solution Blueprint activity (0.3)

An important part of this activity is to conduct several days of demo-based

workshops to gather and clarify requirements. By using preconfigured Data

Packages created using RapidStart Services for Microsoft Dynamics NAV, it is

possible to give a better customer experience than just to showcase a pure out-

of-the-box solution.

A Data Package can be generated automatically from any company configured in

Microsoft Dynamics NAV. This means that it is possible at any time, for example,

during preparation for a demo to create a new Data Package at any phase that

can be refined later on in the same implementation project. With time, you will

have a collection of Data Packages, and it will be possible to reuse them in new

pre-sale or implementation projects.


METHODOLOGY

The Data Package concept is flexible and it is easy to modify, extend, and, when

appropriate, combine templates.

We recommend that partners identify homogenous customer segments and

decide the optimal level of pre-configuration for each of them. Being able to

create Data Packages with a high level of pre-configuration to suit typical

implementation projects to support the Sure Step Rapid project type should be

the ultimate goal.

A Questionnaire can be used as a convenient way of deciding the actual setup

configuration in this activity or just to get an overview of the current setup

configuration. It is also possible to use parts of or the complete Questionnaire to

configure key processes as part of conducting this activity jointly with the

customer.

The Proof of Concept activity (0.4)

This activity involves demonstrating how Microsoft Dynamics NAV can meet

specific high-level requirements. Therefore, a large amount of what has been

stated under the previous activity is true for this activity as well. Any additional

configuration made during this activity can be exported and saved as a new Data

Package to be used later on.

The Project Planning activity (0.9)

Since most Microsoft Dynamics NAV implementations involve some level of data

migration we recommend that you benchmark the project planning activities in all

phases of the implementation project based on Sure Step.


METHODOLOGY

Sure Step – Project Types, Phases and Activities

The Diagnostic phase is similar for all project types, but all subsequent phases are

dependent on the project type. In this whitepaper, we will use the Standard

project type and only focus on activities where the RapidStart Services for

Microsoft Dynamics NAVis applicable.

Figure 4 Sure Step activities from Analysis to Deployment phases where the RapidStart Services for

Microsoft Dynamics NAV is applicable


METHODOLOGY

Sure Step – the Analysis Phase and the RapidStart Services for


The Analysis phase represents the official start of the implementation. This phase defines the activities required to initiate and effectively plan the entire project.

Figure 5 Sure Step: The Analysis phase and RapidStart Services for Microsoft Dynamics NAV

The Conduct Detailed Business Process Analysis activity (1.3.1)

The Detailed Business Process Analysis workshops define the future ‘To Be’

business processes and identifies where specific functionality of the new system

will be used. At the same time, the workshops will identify gaps in functionality

that may need to be resolved by ‘a-work-around’, change in business practice or

by the system being modified. To showcase how a business process can be

performed in a Microsoft Dynamics NAV ‘work-around’ it is possible to use the

Data Package configured during the Diagnostic phase. Any additional

configuration made during this activity can be exported and saved as a new Data

Package to be used later.


METHODOLOGY

The Build Sandbox and Training Environments activity (1.7.1)

The purpose of this activity is to install the Training and Sandbox environments at

the customer site to allow for customer training and familiarization with the core

Microsoft Dynamics NAV product prior to any customization. The Sandbox and

Training environment will comprise all core functionality of Microsoft Dynamics

NAV and will typically contain sample or demonstration data. With RapidStart

Services for Microsoft Dynamics NAV, it is possible to provide Training and

Sandbox environments based on Data Packages in addition to demo data-related

environments to enhance the customer experience. The environments might be

extended to also include a subset of data migrated using RapidStart Services for

Microsoft Dynamics NAVData Migration.

The Gather Data Migration Requirements activity (1.9.1)

The purpose of this activity is to define high-level data migration requirements.

We recommend that you review the available resources for RapidStart Services for

Microsoft Dynamics NAV to learn more about the tool’s capabilities and

limitations. A typical RapidStart Services for Microsoft Dynamics NAV Data

Migration process involves exporting table and fields to Excel, where the legacy

data is transformed and mapped before it is imported back, validated, and

applied. Since the data transformation, that is, cleansing and conversion,

capabilities, is primarily based on Excel functions, it is important to consider this

when deciding the scope for the migration. The focus for the data migration

should be Basic Setup Data, Master Data Records, and Open Transactions and

Balances.

The scope of the data migration should be defined already at this stage using

Data Migration Overview. This should include Table, Migration Fields and

Validations that are exported to Excel, where the mapping and transformation

requirements are documented.

During this phase, we also recommend that you showcase the capabilities of

RapidStart Services for Microsoft Dynamics NAV Data Migration as part of the

workshop together with the customer representatives, so that they can evaluate

an appropriate scope for data migration.


METHODOLOGY

Sure Step – the Design Phase and the RapidStart Services for


The goal of the Design phase is to define how the business requirements will be

implemented. The phase includes configuration of the overall Microsoft Dynamics

NAV solution and the design of specific customizations needed to satisfy business

requirements identified during the Analysis phase.

Figure 6 Sure Step: The Design phase and RapidStart Services for Microsoft Dynamics NAV

The Begin System Configuration and ISV Solution Setup activity (2.4.1)

All application configuration settings that have been identified, but not yet

considered, need to be completed in the design phase. Similarly, if ISV solutions

have not been considered and included in the earlier stages, this would be the

time to include them in configuration and setup. When considering ISV solutions,

also verify if they can provide Data Packages or Questionnaires that could be used

for setup and configuration. As in other phases, any additional configuration

updates made during this activity can be exported and saved as a new Data

Package to be used later.

The output of this activity allows for the initial baseline of the configurations to be

established and to facilitate any initial development effort.


METHODOLOGY

The Conduct Feature Testing of Standard and ISV Solution activity (2.6.1)

Stand-alone testing of the configured feature should take place in the Testing

Environment created in the Design phase. The goal of this testing is to validate

that the Microsoft Dynamics NAV and ISV configuration, and sample customer

data meets the client’s business process requirements. During this testing, the

Application Consultants and Key Users should test all data validation aspects of

the feature, as well as any functionality contained wholly within the feature.

The Application Consultant, with the assistance of the Technology Consultant

and/or Solution Architect if necessary, reviews applicable software configuration

settings to determine changes necessary to resolve the issues that caused testing

failure, and the exact changes that need to be made. Once the necessary software

configuration changes have been made, the function, data migration, or

integration program must be resubmitted for testing and validation.

The end result of this testing is to ensure that the configured features have fully

been tested with a degree of confidence that any subsequent issues are the result

of the feature’s interaction with other components of the environment, and not

with the feature itself. It should be noted that in some cases stand-alone feature

testing is not feasible due to the design of the feature. In this case, the feature

should be introduced into the Integration testing process and feature testing

should be performed at that time.

Any additional configuration made during this activity can be exported and saved

as a new Data Package to be used later.

The Begin Data Migration Design activity (2.9.1)

Once the scope for data migration has been decided, it is important to determine

the order to migrate data, that is, ‘upstream’ data that may be needed as default

data. For example, an Inventory Item requires a Unit of Measure to exist prior to

creating the Inventory Item.

If the scope of the data migration has already been documented using Data

Migration Overview, including Tables, Migration Fields, and Validations and this

have been exported to Excel, then you are ready to complete the mapping and

design the transformation functions in Excel.

Using RapidStart Services for Microsoft Dynamics NAV is not required to develop

conventional data migration scripts. The only requirement is to get the

customer/legacy data into an Excel spreadsheet in its raw format. Once in Excel, it

is a best practice to maintain the data in its original form in one sheet, perform

the data transformation and mapping in another sheet, and then keep the data to

migrate in a third sheet.


METHODOLOGY

The Create a Subset of Data for Testing activity (2.9.2)

Subsets of data should be migrated into the test environment using RapidStart

Services for Microsoft Dynamics NAV Data Migration to form the basis for unit

testing, systems and integration testing, and function testing.


METHODOLOGY

Sure Step – the Development Phase and the RapidStart Services for


The goal of the Development phase is to build and test the system components

defined and approved in the design specifications, including developing the

customizations, integrations and interfaces, and data migration processes. The

major deliverables include the complete system configuration, completion and

freezing of code for customizations, integrations and interfaces, and data

migration.

Figure 7 Sure Step: The Development phase and RapidStart Services for Microsoft Dynamics NAV

The Conduct Solution Testing activity (3.6.1)

An important part of solution testing is the Data Acceptance Test (DAT) where the

Development Consultant and Technology Consultant will use RapidStart Services

for Microsoft Dynamics NAV Data Migration to transform, import, and migrate all

the Customer‘s migrated data into the Test environment. The test of the data

migration is important for two main reasons:

To test the flow of the process in a controlled environment

To provide statistical data for estimating the time needed for a

complete data migration


METHODOLOGY

Following this, the Customer Data Owners and Key Users will perform data

analysis of the solution, in accordance with the previously established Data

Migration Requirements. During DAT, the customer not only verifies the data

migrated but also validates that the data may be inquired upon, reported upon,

and transacted upon.

Also, the Application Consultant performs functional testing using the data

imported using the Data Migration scripts. Anomalies or issues discovered during

the testing process should be noted and testing should continue unless

precluded by the issue. This will allow the development consultant to address

issues more efficiently than addressing each issue as it arises. Once all data

anomalies and issues have been addressed and resolved, the data migration

programs are ready for user process testing.

Since the RapidStart Services for Microsoft Dynamics NAV Data Migration

provides application data validation, it is possible to minimize the amount of

testing and analysis needed after the first test data import. Nonetheless, it is

important that the functional testing should encompass every module within the

solution that will be dependent on the migrated data, including each application

entry/maintenance screen and process.

The Begin Development of Data Migration Scripts activity (3.9.1)

Microsoft Dynamics NAV does not support writing data directly into the database.

The only supported methods of data import are via RapidStart Services for

Microsoft Dynamics NAV Data Migration or via Dataports within Microsoft

Dynamics NAV.


METHODOLOGY

Sure Step – the Deployment Phase and the RapidStart Services for


The Deployment phase is where all the efforts of the project team come together

for a successful transition to the new Microsoft Dynamics NAV solution. Key

activities in this phase include End User Training, Performance Testing and User

Acceptance Testing, and the actual cut-over to the new production environment.

Figure 8 Sure Step: The Deployment phase and RapidStart Services for Microsoft Dynamics NAV

The Execute User Acceptance Testing activity (4.6.1)

The purpose of this activity is to thoroughly test the setup and configuration of

the system and obtain User Acceptance sign-off.

Keep in mind that, even if the analysis determines that the tests were successful,

the customer may still request changes to the feature, data migration, or

integration process. Any changes requested beyond those needed to meet the

previously established pass criteria will need to be evaluated individually and

possibly brought to the attention of the Project Manager for a final determination.

If additional changes are requested, the Project Manager will initiate the change

request process and evaluate the impact to the overall project schedule. Changes


METHODOLOGY

made to the system will be subject to individual unit and function testing, and

may also require repetition of the Execute Process Testing, Execute Performance

Testing and Execute User Acceptance Testing activities prior to completion of the

Obtain Complete System Acceptance activity.

The Build Production Environments activity (4.7.1)

Data Packages can be used to apply the latest set of configuration changes.

The Final Data Migration to PROD activity (4.9.1)

The purpose of this activity is to migrate live data from the source or legacy

systems into the Production environment in preparation for the cut over and Go

Live. Migration of data from the source or legacy systems is the final critical phase

of the project and is the key to success as well as user adoption. Data migrated

into Production has to be timed accurately so as to ensure that users see the most

recent data when the system is available to them.

The effort is usually split into two phases:

Phase 1 – Initial migration of data into Production:

The initial migration of data into production is performed to avoid overloading

the systems over the go-live weekend and is typically done a week before the

actual go-live. This data typically includes static data.

Phase II – Final data migration into Production:

The final data migration is done over the weekend prior to go-live. Since most of

the initial data is loaded a week before go-live, the final data load will take into

account the data entered into the system after the initial data load. This concept

expedites the migration process and eliminates last minute glitches that can

jeopardize the cut over.


METHODOLOGY

Microsoft Dynamics is a line of integrated, adaptable business management solutions that enables you and your people to make business decisions with greater confidence. Microsoft Dynamics works like and with familiar Microsoft software, automating and streamlining financial, customer relationship, and supply chain processes in a way that helps you drive business success.

U.S. and Canada Toll Free (888) 477-7989

Worldwide (1) (701) 281-6500

www.microsoft.com/dynamics

The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication. Because Microsoft must respond to changing market conditions, this document should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the date of publication.

This white paper is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED, OR STATUTORY, AS TO THE INFORMATION IN THIS DOCUMENT.

Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation.

Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.

© 2009 Microsoft Corporation. All rights reserved.

Microsoft, Microsoft Dynamics, the Microsoft Dynamics logo, and Microsoft Dynamics NAV are trademarks of the Microsoft group of companies.

http://www.microsoft.com/dynamics