Partner guidance – engagement phase 2 The Architectural Design phase and the Fit Gap phase are...

12
Software Assurance Planning Services Implementing Microsoft Dynamics AX High Level Solution Architecture Design & Fit Gap Report Name Title Microsoft Partner Company Name

Transcript of Partner guidance – engagement phase 2 The Architectural Design phase and the Fit Gap phase are...

Page 1: Partner guidance – engagement phase 2  The Architectural Design phase and the Fit Gap phase are required for 5, 10 and 10 day engagement (please refer.
Page 2: Partner guidance – engagement phase 2  The Architectural Design phase and the Fit Gap phase are required for 5, 10 and 10 day engagement (please refer.

Agenda

3

Objectives Review Engagement Process Flow Findings & Recommendations Deliverables Acknowledgements Next Steps & Action Items Questions & Answers

Page 3: Partner guidance – engagement phase 2  The Architectural Design phase and the Fit Gap phase are required for 5, 10 and 10 day engagement (please refer.

Objectives

Estimate the fit of customer’s environment to implementing Microsoft Dynamics AX and best approach to solution architecture

Solution Architecture, Fit Gap and high level blueprint

• Determine the level of customization and configuration will be required

• Identify and recommend an Implementation Strategy and its associated Project Phases

Validation of technical environment requirements and hardware and budgetary considerations

Provide you with an understanding of how Microsoft Dynamics AX will work in your business.

4

Page 4: Partner guidance – engagement phase 2  The Architectural Design phase and the Fit Gap phase are required for 5, 10 and 10 day engagement (please refer.

Overview and Schedule

5

This is the process flow we used to do our analysis over the last several weeks...

Page 5: Partner guidance – engagement phase 2  The Architectural Design phase and the Fit Gap phase are required for 5, 10 and 10 day engagement (please refer.

The following are the top requirements and considerations which were used to develop the recommended solution architecture

High Level Solution Architecture – Requirements and Consideration

6

Insert Customization Description here.

Discuss how the technical requirement or consideration will be handled in the architecture Microsoft Dynamics AX.

Provide an effort estimate in hours.

As a business you need to validate if these Business/IT requirements are truly necessary or if the requirement can be dropped in order to reduce implementation costs.

*N.B. Development only. This doesn’t include Unit Testing, UAT, Performance Testing, Design Specification, etc.

Page 6: Partner guidance – engagement phase 2  The Architectural Design phase and the Fit Gap phase are required for 5, 10 and 10 day engagement (please refer.

The following is a summary of the recommended solution architecture

High Level Solution Architecture – Recommendation

7

Page 7: Partner guidance – engagement phase 2  The Architectural Design phase and the Fit Gap phase are required for 5, 10 and 10 day engagement (please refer.

Fit/Gap Findings – Degree of Fit

8

<insert percentage>

Customization, 9%

3rd Party Add-On, 4%

Workflow,2%

Page 8: Partner guidance – engagement phase 2  The Architectural Design phase and the Fit Gap phase are required for 5, 10 and 10 day engagement (please refer.

The following are the top 5 customization identified as being required during the Fit-Gap analysis ...

Fit-Gap Findings – Major Customization Requirements

9

List the Customization ID from the Fit/Gap spreadsheet here.

Insert Customization Description here.

Discuss how the customization will be handled in Microsoft Dynamics AX.

Provide an effort estimate in hours.

As a business you need to validate if these Business/IT requirements are truly necessary or if the requirement can be dropped in order to reduce implementation costs.

*N.B. Development only. This doesn’t include Unit Testing, UAT, Performance Testing, Design Specification, etc.

Page 9: Partner guidance – engagement phase 2  The Architectural Design phase and the Fit Gap phase are required for 5, 10 and 10 day engagement (please refer.

The following are the ISV add-on solutions identified as being required during the Fit-Gap analysis ...

Fit-Gap Findings – Requirements for ISV Add-On Solutions?

10

List the Customization ID from the Fit-Gap spreadsheet here.

Insert Customization Description here.

Discuss how the customization will be handled in Microsoft Dynamics AX.

Provide information on the ISV add-on solution that is required.

As a business you need to validate if these Business/IT requirements are truly necessary or if the requirement can be dropped in order to reduce implementation costs.

Page 10: Partner guidance – engagement phase 2  The Architectural Design phase and the Fit Gap phase are required for 5, 10 and 10 day engagement (please refer.

The following are the Integrations identified as being required during the Fit-Gap analysis ...

Fit-Gap Findings – Requirements for Integrations?

11

List the Customization ID from the Fit-Gap spreadsheet here.

Insert Customization Description here.

Discuss how the customization will be handled in Microsoft Dynamics AX.

Provide an effort estimate here.

As a business you need to validate if these Integration requirements are truly necessary or if the requirement can be dropped in order to reduce implementation costs.

*N.B. Development only. This doesn’t include Unit Testing, UAT, Performance Testing, Design Specification, etc.

Page 11: Partner guidance – engagement phase 2  The Architectural Design phase and the Fit Gap phase are required for 5, 10 and 10 day engagement (please refer.

The following is the Data Migration Plan that has come out of theFit-Gap analysis ...

Fit-Gap Findings – Requirements for Data Migration?

12

List the Customization ID from the Fit/Gap spreadsheet here.

Describe the data element.

What volume of data needs to be migrated?

How often will the data migration need to occur?

Will it be a manual process, some custom code written from Microsoft Visual studio, BizTalk Server, or Custom Code with an End-User Interface.

Provide a description of how the Data will be migrated and how the Semi Auto or Automated Solution would work.

Provide an effort estimate here.

*N.B. Development only. This doesn’t include Unit Testing, UAT, Performance Testing, Design Specification, etc.

As a business you need to validate if this level of automation of data migration is required or if the requirement can be dropped in order to reduce implementation costs.

Page 12: Partner guidance – engagement phase 2  The Architectural Design phase and the Fit Gap phase are required for 5, 10 and 10 day engagement (please refer.

Fit-Gap & Solution Blueprint Deliverables

13

Fit-Gap Spreadsheet This is the spreadsheet which lists all the requirements, how they will be addressed (“out-of-the-box,” configuration and customization) and the effort estimate associated with each deliverable.

Solution Blueprint This is a Report (written in Microsoft Word) which covers our understanding of the requirements, discusses Microsoft Dynamics AX functional fit, reviews key design points, discusses customization and integration requirements, reviews the proposed conceptual design and lists any assumptions made.

Before moving on to the next steps (LCS proof of Concept and Scoping Assessment) it is important for you to validate this Fit-Gap Spreadsheet & Solution Blueprint to make sure we have a clear understanding of your requirements.