Solution fit gap delivery guide: Implementing Microsoft Dynamics AX

Prepared for[Customer Name]

Project[Project Name]

Prepared by

Contributors[Document contributors]

Implementing Microsoft Dynamics AXFit Gap & Solution BlueprintDelivery Guide

Microsoft Dynamics Planning Services

Revision and Signoff SheetChange RecordDateAuthorVersionChange reference

ReviewersNameVersion approvedPositionDate

Microsoft Dynamics Planning Services

Table of Contents1Introduction12Executive Overview22.1Executive Summary32.2Vision and Scope32.3Risk Assessment42.4Potential Next Steps43Initiate Engagement63.1Ensure Readiness for Service63.2Conduct Internal Pre-Kickoff Meeting63.3Customize Service and Create Baseline Agenda74Kickoff Meeting84.1Understand the Customers Situation94.2Ensure the Customer Benefits from the Engagement104.3Assemble Core Delivery Team105Engagement Phases116Initial Demonstration to Customer127Information Gathering Phase137.1Functional Requirements and Fit137.1.1General Foundation137.1.2Finance137.1.3Supply Chain147.1.4Inventory and Logistics147.1.5Production147.1.6Planning and Scheduling147.1.7Projects157.1.8Human Resources157.1.9Other Modules157.2Integration and Interfaces157.3Data Migration167.4Quality and Testing167.5Technical Assessment167.5.1Infrastructure Inventory167.5.2Customer Pain Areas187.5.3Requirements198Business Process Workshops209Findings and Review219.1Fit Gap Worksheet219.2Solution Blueprint Report219.3Customer Review2110Closeout Meeting2211Effort Estimate Work Breakdown Structure2312Conclusion2413Appendices2513.1Fit Gap & Solution Blueprint Process Flow2514References2614.1Links26

IntroductionThe purpose of this document is to provide guidelines to Microsoft Partner consultants who are providing a Fit Gap and Solution Blueprint for customers who are implementing Microsoft Dynamics AX. Areas covered include roles and responsibilities for the consultant, the customer, and any vendors or partners who may be involved in the project.Fit Gap and Solution Blueprint should be part of 5, 10 or 15 day Implementing Microsoft Dynamic AX planning Services engagement. This phase should only be performed after the assessment phased was performed during the first 3 days of the engagement. Please refer to the table below. 3 days5 days10 days15 days

ActivityAssess & document top business processes & requirementsPlan AX implementation architecture & suggest solution fitShowcase implementation & Validate Customer Benefits(1 to few processes)Showcase & Validate Customer Benefits extended(3+ processes)Supporting Documents

Pre-engagement AssessmentPre-Engagement Questionnaire

Assessment and process documentation workshop Microsoft Dynamics Lifecycle Services Business Assessment Report Template

High-level Solution Architecture Solution Architecture Report

High level fit gap and scopingFit Gap Analysis WorksheetScoping worksheet/SOW

Proof-of-concept LCS azure demo environmentAzure demo guidance

Customer DeliverablesAssessment Findings ReportArchitecture plan & gap summaryPoC Findings ReportPoC Findings ReportMicrosoft Dynamics AX 2012 Implementation Planning GuideMicrosoft Dynamics AX Installation Guide

Executive OverviewThis section describes the major issues facing a customer that may have prompted them to begin the planning process for a Fit Gap & Solution Blueprint. It describes the overall program, the purpose of the engagement, and outlines the major activities covered.

Enterprise Resource Planning (ERP) is used to refer to an enterprise view of a business; it means leveraging applications to manage the operations and gain a view of a company as a connected single entity, as opposed to a collection of activity silos. The customer may find the following issues with their current information systems, prompting them to evaluate ERP solutions:

Business Processes (BP): They do not support the customer's critical business needs and are not flexible enough to change as the business itself evolves. They are unable to easily perform core business processes such as quickly closing a financial period, tracking variances, product costing, or forecasting demand. They are unable to eliminate manual workarounds to reconcile data and / or transactions between systems.

Supply Chain (SC): They are unable to provide appropriate access to information for their customers, suppliers, and partners; processes are independent of one another and not linked together into an overall chain whose purpose should be to supply the end-user with products or services at the right time, cost and in the right configuration.

Business Intelligence (BI): They dont provide timely access to the information needed to make critical business decisions and are unable to integrate business related intelligence, information and master data across company divisions and organizations; it is difficult to mine information and produce useful reports and inquiries.

Architecture: They lack flexibility due to home-grown applications, old systems or spreadsheets that are being used to manage the overall business operations.

During the course of their evaluation, the customer may have found that some of their business processes align very well with Microsoft Dynamics AX. They may also have found that a certain percentage of their processes can be covered by independent software vendor (ISV) solutions, while some may require custom development.

To quantify this in a more certain manner, the customer can request a Fit Gap & Solution Blueprint. The benefit to the customer is to gain a clear understanding of the solutions fit with mission critical and major, key business processes, before the commencement of the implementation project itself.

Executive SummaryThe customer engages a Microsoft Partner for the Fit Gap & Solution Blueprint offering for the following reasons:

To understand the level of Fit between their organizations requirements and Microsoft Dynamics AXTo understand what level of customization and configuration will be required To understand which ISV solutions may be required To obtain a blueprint for the delivery of the solution that can be used in the subsequent project planning and analysis

Accordingly, the decisions made during this engagement must align with the customers overall business level goals and objectives as follows:

Validation of the Degree of Fit of Microsoft Dynamics AX to the customers business requirementsGain business buy-in and support for Microsoft Dynamics AX as a solution that meets the customers needsIdentification of an Implementation Strategy and its associated Project PhasesDetermination of the various staffing and cost options and their implications. This will allow the customer to select the right balance between costs and benefitsVision and ScopeThe Vision for this type of engagement is to determine the degree of fit of the Microsoft Dynamics AX with the customers business requirements, as well as to determine the amount of configuration and customization required, and how the system will be used by customer. This will be accomplished through a series of interviews, workshops, and demonstrations to the customers business and Information Technology (IT) personnel during which feedback on their business and IT requirements will be collected.

This engagement fits into the overall program by providing the customer with a clear understanding of the solutions fit with key business processes, and business objectives, before commencement of the full discovery phase as part of an implementation project.

Below is a list of in-scope and out-of-scope activities for this engagement.

In-Scope:

Development of a prioritized list of requirementsReview of requirements versus those that are available in the current systemsEstimate of Degree of Fit (i.e. identification of what is native functionality, configuration, or customization) for the overall environment and in particular identified and prioritized processesHigh-level estimate of the services required for configuration and customization for each requirementDevelopment of a Solution Blueprint which provides details, from a Business Perspective, of how Microsoft Dynamics AX will be delivered and used

Out-of-Scope:

The partner should provide a high level fit gap analysis and blue print as the length of the Planning Services engagement permits, but should include at least one to few processes and an overall high level estimate of the solution fit. Detailed Functional and Technical SpecificationsDetailed To-be process maps, training documentation and end user trainingImplementation PlansDetailed Project Plan, Return-On-Investment (ROI) calculation or a Total-Cost-of-Ownership (TOC) analysisAny other items not explicitly defined as in-scope

Recommendations will be detailed and documented in the Microsoft Sure Step Fit / Gap and Solution Blueprint at the end of the engagement.Risk AssessmentThe following items could have a negative impact on the success of the Fit Gap & Solution Blueprint engagement:

Business requirements are not availableSupporting documentation is unavailableBusiness and IT subject matter experts are not available during the workshopsBusiness and technical decision makers are unavailable Lack of an Executive Sponsor to define the scope and champion the engagementInability to reach decisions in a timely mannerPotential Next StepsDepending on the outcome of this engagement, and in order to meet the customers expectations, several other activities may be required, which are identified as the next steps listed below:

Scoping Assessment: This consists of a document that provides a high level project cost and resource plan specific to the customer. It describes how they would go about implementing Microsoft Dynamics AX and what that implementation would cost. Its objective is to determine a total cost to implement Microsoft Dynamics AX.Proof of Concept (POC): Microsoft Dynamics AX is configured using the online Azure hosted environment in Dynamics Life Cycle Services around certain critical requirements. This is then demonstrated to the Business Decision Makers (BDM) and IT personnel in a conference room setting to validate their requirements. Fit Gap ReadinessFit Gap Analysis and Solution Blue Print should follow the assessment phase which is the first required activity as part of the Implementing Dynamics AX Planning Services engagement. So, by the time the consultant/s starts the Fit Gap activities they should be familiar with the customers business environment and operating constraints after reviewing the pre-engagement questionnaire, documenting with the customer the business processes using Life Cycle Services and delivering the assessment report to the customer including process prioritization. Ensure you gathered enough information about the customers business process you prioritized and their business and technical requirements and limitations according to the items below during the assessment phase: Ensure Readiness for ServiceTo ensure readiness, the following activities should be performed:

Identify specific consulting and customer resources that are needed to perform a detailed analysis of each high-level business process and identify the associated requirements.Identify specific consulting and customer resources that can review any system integration requirements.Business RequirementsThe Business Requirements gathering phase marks the official start of the engagement. The goal of this stage is to define and document the companys business requirements related to Microsoft Dynamics and any needed ISV solutions. These requirements include Business, System, Technical, Integration / Interfaces, Data, and Quality / Testing. Taking a "big picture" approach at the initial stage of the project allows us to consider all the requirements and possibilities related to if, how and when Microsoft Dynamics is deployed in the various locations and departments in the customers organization. At this time we also determine which Microsoft Dynamics functionality is required and document the Deployment Strategy that lays out in what phase of the implementation project the various modules and / or functionality will be implemented.

Understand the Customers SituationBefore starting the Fit Gap engagement, the consultant should have gathered enough background information about the current environment so that the engagement is focused in the right areas. This is not an in-depth analysis, which is beyond the scope of this exercise, but it should capture how the customer currently feels. Some examples of areas that should be covered include:

Customers general need for a business solutionCurrent system and the reason for changing itCurrent architectures in use within the organizationEnterprise architecture standards, principles, and constraintsCode development standardsCurrent technologies in use within the operationIntegration and interface standardsCurrent master data and transaction volumesNumber and type of usersCurrent skill levelsCurrent change control management processesCurrent ERP environment, and any other such tools that are in useCurrent status of any initiatives in the organization relating to the current ERP environment

The consultant also needs to know whether the customer has a current technology roadmap. This may either be implied or explicitly written. The customers roadmap and how it relates to the Microsoft roadmap is something that the consultant delivering this engagement should consider, especially when preparing his recommendations.

There are no mandatory deliverables as a result of this exercise, but the consultant should use the key findings of this exercise as inputs to the findings and recommendations that are delivered at the end of the engagement.Ensure the Customer Benefits from the EngagementEngage all project stakeholders to ensure expectations have been set correctly. The entire project team should have a common understanding and a buy-in of the vision and scope for this engagement. They should understand the importance of the Fit Gap & Solution Blueprint, as well as how it fits into the customers overall plans and objectives. Identify tangible benefits and focus on the technical, business, and operations aspects as appropriate. Examples include:

Help me understand my environment Help me count the number and size of my databasesHelp me know if I am following the latest best practicesHelp me know if my IT environment is configured appropriately

You should be asking yourself these questions when preparing for the engagement:

What are the key decisions that the customer needs assistance in making?What are the potential showstoppers that can be avoided?Are there any fundamental knowledge gaps?How can we bring the customer to a solution faster?Assemble Core Delivery TeamThe Fit Gap & Solution Blueprint engagement is created to be delivered by a virtual team with collective knowledge in, potentially, three disciplines: business, technical, and operations.

The functional part of the engagement can be delivered by one or more Microsoft Dynamics Functional Consultants who have product training and practical experience in the functional areas that are within scope, as well as experience in conducting interviews with relevant stakeholders. The technical part of the engagement can be delivered by one or more Technical Consultants who have the skills to perform an audit of the environment. They would be using a number of Microsoft and third-party tools and will conduct interviews with all of the relevant stakeholders. The Technical Consultant must also have experience in estimating the effort required for configuration and customization to satisfy business requirements.

This means the customer must provide relevant resources (system architects, administrators, and managers) to work with the consultant to achieve these goals. For more information about required resources, see the Fit Gap & Solution Blueprint Resource and Readiness Guide.

Engagement PhasesThe Fit Gap & Solution Blueprint activities will begin with the onsite team determining the degree of fit of the Microsoft Dynamics AX solution with the customers business processes. In order to determine this, the amount of development and customization required, and how the solution will be used by the customer.

The following phases have been identified:

Initial Demonstration to the customerInformation GatheringBusiness Process WorkshopsFindings and ReviewClose out Meeting

The phases above will involve a series of workshops, demonstrations to, and interviews with, the customers business and IT Subject Matter Experts (SME).

Initial Demonstration to CustomerThe Initial Demonstration is the first meeting of the engagement itself and has the following primary purposes:

Demonstrate out-of-the-box capabilities of Microsoft Dynamics AXConfirm Customer expectationsGather basic information about any additional functionality the customer can readily identify during the demonstrationAdditional Functional Information Gathering The Information Gathering phase follows the same framework as the Data Gathering phase, regardless of the customers environment. The following describes the steps, requirements, resources, and tools for data gathering for this type of engagement.

Note that for the purpose of the engagement, the only environment the delivery consultant needs to be concerned with is the current production environment. Throughout the interviewing process, it is expected the delivery consultant will take notes that will be used as inputs for the final set of deliverables.

If the customer has not fully complete the Role Tailored Pre-Engagement Questionnaires it can be useful to complete these questionnaire on this phase, as it can be used to guide the delivery consultants through each functional area of the business, and should be used to document requirements in every area. There are five sections of the questionnaire: General (required in most every business), and separate addendums for (1) Advertising, (2) Architecture, Engineering and Construction, (3) Manufacturing and (4) Professional Services. Functional Requirements and FitDuring the information gathering process, the delivery consultant should identify which of the Microsoft Dynamics AX functionality is required by the customer. A list of the Microsoft Dynamics AX functionality is included below.General FoundationSample Functionality may include the following: Graphical user interface requirements Active Directory Integration Administration and Security Requirements Enterprise Portal (EP) Requirements Document Management Requirements Reporting RequirementsFinanceSample Functionality may include the following: Consolidation processes and needs Foreign Currencies involved General Ledger and Budgeting Bank and Cash Management Fixed Assets Financial Dimensions and their use

Supply ChainSample Functionality may include the following: Sales and Marketing Intercompany Trade Pricing and Commissions Customer Relationship Management (CRM) Trade and Sales / Purchasing Agreements Purchasing and Purchase Requisitioning Accounts Receivable Accounts PayableInventory and LogisticsSample Functionality may include the following: Items and Item Types Product Costing Inventory Model and Dimension Groups Warehouses and Locations Remote Warehouse Replenishment (i.e. Safety Stocks and / or Maximums) Inventory Transfers between Sites and Warehouses Inventory Receipts Order FulfillmentProductionSample Functionality may include the following: Bills of Material (BOM) Routings and Resources (i.e. Work Centers) Lean and / or Process Manufacturing Shop Floor Control and ReportingPlanning and SchedulingSample Functionality may include the following: Sales Forecasting and Seasonality Indices Forecast Consumption and Reduction principles Master Planning (i.e. Forecasting and MRP) Coverage Groups (i.e. Order Policies and Order Quantity Modifiers) Capacity Planning and Scheduling

ProjectsSample Functionality may include the following: Project types and groups Project costing and pricing Fixed fee projects and estimation models Project validationsHuman ResourcesSample Functionality may include the following: Organization Structure Skills, Certifications and Competencies Recruitment Processes Performance Evaluations Time and Attendance Management and ReportingOther ModulesOther modules may include the following: ISV Solution Add-on #1, ISV Solution Add-on #2 (as needed)Integration and InterfacesDuring this workshop the delivery consultant will have a chance to interview and gather requirements for systems integration with:External systemsLegacy systemsCustomers Shop Floor Control toolsProduction or Plant level data gathering systemsPortal-based systemsIntegration with other Microsoft products such as:SQL ServerMicrosoft OfficeMicrosoft .NETMicrosoft ExchangeData MigrationThe scope of data migration, as defined during the kickoff meeting, is reviewed. This review provides a starting point for the Delivery Consultant, Key User and IT team members to identify data migration requirements. This exercise also provides visibility into the customers current master data and transaction volumes, and should include an overall assessment of the data cleansing and updating that is generally required before data migration can occur.Quality and TestingThe Quality and Testing Review is determined by the scope defined during the kickoff meeting. This review provides a starting point for the Delivery Consultant, Key User and IT team members to identify the Quality and Testing standards and requirements.Technical AssessmentThe focus of the Fit Gap & Solution Blueprint engagement is to gather Business and IT requirements. Limited time is allotted to analyze the clients technical environment. Therefore, the analysis in this area should be considered as only a high-level pass.Infrastructure InventoryThe intent here is to help the delivery consultant discover as many details as possible about the current environment. Once infrastructure data have been collected, the delivery consultant will have a solid understanding of all the relevant dependencies. This Inventory will provide crucial data points to help the consultant perform the gap analysis and make his recommendations.Due to limited time dedicated to the interviewing process, make sure all areas are covered before you look into the details. All relevant dependencies must be considered, and only if time is allowed to focus on areas that need more attention. Focus areas will differ between customers, but typically involve storage, network, and directory services.

EnvironmentsOne of the first steps is to determine the number of environments that need to be assessed. These can include test, development, pre-production, and production environments.To gauge the operational maturity of the customer, it is important to understand if the customer has more than just a production environment and if so, how code changes are migrated from the development and test environments to production.

Network Infrastructure and ServicesIdentify the network infrastructure and services.

HardwareThe following information should be captured for each discrete system:Identify core inventory information about the servers. Key components, including version and revision levels are important when determining applicability and supportability in complex configurations.Ensure that the complete configuration is listed on the Windows Hardware Compatibility List (WHCL) at http://www.microsoft.com/whdc/hcl/default.mspx

Focus should be on the current and planned future company standards, as well as a limited number of representative servers (typically five to six servers from each category) that the customer identifies as being troublesome. This will provide some insight into the customers pain points.If the customer does not have this information available beforehand, do not spend too much time collecting it during this phase.The most important parts of this inventory are whether or not the systems are on the WHCL and how the hardware is used by the operating system, such as the settings for the boot.ini file.

StorageIdentify the storage components.

Directory ServicesIdentify the Directory Services configuration and setup.

MonitoringIf the customer wants to run a high-performance Microsoft environment, it is important to understand the health of the systems. Discover whether the customer is using Microsoft Operations Manager (MOM) 2000/2005 and, if not, the reasons for that decision.

MaintenanceA detailed inventory of this area is the responsibility of the operations consultant. However, make sure to perform an overview of the operational maturity of the customer to identify any barriers to implementing the desired solution.

HygieneThroughout the interviewing process, it is expected the delivery consultant will take notes that will be used as inputs for the final report.

Customer Pain AreasAdditionally to the information which was gathered during the assessment phase, the consultant should collect additional information on the prioritized processes regarding customers pain points. The goal of this process is to allow the customer to clearly communicate detailed key areas that cause issues within the organization. These essentially fall into two categories: undesired behavior that is occurring; or desirable behavior that is not. The result of this interview will be a prioritized list of issues based on the customers ranking by importance or impact. The customers background information should be collected prior to engaging with the customer. Based on the customers pain points, the consultant should try to categorize the list into business requirements and underlying issues, which can be converted to requirements for the new solution. Technical and operational assessments will help determine the underlying causes of the issues.

GeneralThe focus is on computing, support equipment, and services. Throughout the interviewing process, it is expected the delivery consultant will take notes that will be used as inputs for the final report.

AvailabilityThe basic availability focus means the servers are up and in a mode that offers acceptable service to the end users.

System PerformanceThe basic is it running well? focus, checks whether the servers are performing as expected. Take note of any documentation that defines how running well matches with their Service Level Agreements (SLA). The overall connection between SLAs and performance is a link that the operations consultant should be making in the interviews. Based on the responses here, he should confirm that this link has been established.

StorageThe basic is it running well? focus means the storage is performing as expected.

Disaster RecoveryThe focus is on understanding the customers maturity in the Disaster Recovery (DR) area. Use any additional space to make notes about the Disaster Recovery environment.

Third-Party ComponentsThe focus is on understanding any third-party components that affect the environment. Use any additional space to make notes about third-party applications after obtaining answers.

Additional Issues or ConcernsThis is the opportunity to allow the customer to freely identify issues or needs not expressly covered in previous sections.RequirementsThis section helps the consultant document the customers technical requirements as they relate to this engagement.

Business Process WorkshopsBusiness Process Workshops are conducted halfway through the engagement to present and discuss current findings with the customer and to review the business processes that are considered within the scope of this engagement. The length of the various workshops can be from a few days to a few weeks depending on the scope of the engagement and the number of business processes that are analyzed. The onsite team may cover the following topics in the Business Process Workshops:Demonstration of relevant components of Dynamics FunctionalityA walkthrough of the business process flow charts, within the scope of the engagement, and a discussion of how Dynamics would work within those business processesA review of the business requirements to determine how they will be addressed in DynamicsPrioritization of the requirements identified before and during the workshops

Business Process Workshops provide a good way of validating the requirements information collected during the Information Gathering Phase.

Findings and ReviewAfter the Information Gathering Phase of the Fit Gap & Solution Blueprint engagement is complete, the delivery consultant will have number of reports, tools, outputs, and interview documents that will be used as inputs for the final report. The consultant should use the results gathered throughout the engagement to create a prioritized list of findings and recommendations.Fit Gap WorksheetUsing the inputs obtained during the Information Gathering Phase, the onsite team constructs the Fit Gap Worksheet. The following steps may be followed:

Construct the worksheet using the Sure Step Fit Gap Worksheet toolReview the Fit Gap Worksheet with the various StakeholdersFinalize the Fit Gap Worksheet by:Calculating the Degree of FitCompleting a High-Level Development Estimate

Solution Blueprint ReportFollowing the completion of the Fit Gap Worksheet, the onsite team can determine the Solution Blueprint and the design of the overall proposed solution. Sure Steps Fit Gap Solution Blueprint Template document can be used for this effort.

Customer ReviewOnce the Solution Blueprint report has been created, the delivery consultant should schedule a review meeting with the customer. The delivery consultant should address all objectives agreed upon at the beginning of the Fit Gap & Solution Blueprint engagement.

Closeout MeetingAt the end of the engagement there is a closeout meeting to complete the Fit Gap & Solution Blueprint project. The closeout meeting is the final activity performed as part the engagement. The findings for the engagement are presented to the customer and recommendations are delivered.

It is also provides an opportunity to propose any follow-on engagements that may have been identified during this offering.

Topics related to the closeout meeting are:

Meet and discuss:Results to dateCloseout / finding and recommendations presentation which will include aDiscussion of the overall Degree of FitAnalysis of the major items in terms of configuration and customizationData Migration RequirementsIntegration RequirementsRelate findings to original objectives and requirementsDiscuss the next steps (i.e. roadmap)Determine customer satisfactionClose the engagement

Note: Make sure you identify any possible future engagements for inclusion in the Next Steps section of the presentation.

The Closeout Meeting is an opportunity to deliver all the documentation and reports that resulted from the engagement:Fit Gap WorksheetSure Step Solution Blueprint ReportFit Gap Solution Blueprint Close Out PresentationCloseout Meeting ReportEffort Estimate Work Breakdown StructureThis section contains a detailed Work Breakdown Structure (WBS) for the Fit Gap & Solution Blueprint engagement.

ConclusionThe Fit Gap & Solution Blueprint engagement represents an important solution offering to the customer.

This delivery guide does not intend to address specific issues and requirements regarding the solution, but only to provide guidance to the delivery consultant team during the process of conducting and completing a successful engagement.

AppendicesFit Gap & Solution Blueprint Process FlowThe process flow to be used to deliver the Fit Gap & Solution Blueprint is depicted in the diagram below:

ReferencesLinksAdditional links are provided in this section for training and readiness resources. Use this as a resource for developing your personal learning plan as necessary.Microsoft Dynamics http://www.microsoft.com/dynamics/default.mspx - Information on Microsoft Dynamics.Microsoft Dynamics AX http://www.microsoft.com/dynamics/ax/default.mspx - Specific information on Microsoft Dynamics AX.Microsoft Dynamics AX Customer Testimonials http://www.microsoft.com/dynamics/ax/product/customerstories.mspx - Microsoft Dynamics AX customer testimonials.Microsoft Dynamics Planning Services

Sheet1Fit Gap and Solution Blueprint ActivityTime Estimate (Hrs)CommentsGather and Review Functional Documentation8All requisite documentation to be collected prior to project startGather and Review Technical Documentation8All requisite documentation to be collected prior to project startReview of Legacy Applications8Customer to provide assistance in doing functional walkthrough of legacy applicationsCollate all Functional Requirements16Construct Fit Gap Worksheet8Interview IT and business leadership and review the Functional Requirements8 Conduct Business Process Workshops16Finalize Fit Gap, calculated Degree of Fit (DOF) and complete Development Estimate16Requirements will be prioritized into phases with high-level development/ configuration time associated with each activityDetermine Solution Blue Print and overall proposed Solution Design and Write Report16Solution Blueprint review requirements at a high-level, talks about the conceptual and logical architecture of the solution proposed, major development activities and any add-ons requiredReview with Management Team and incorporate feedback4Engagement Management4Contingency8Total120