Project information
Microsoft Dynamics 365 FnO (ERP) configuration and migration from AX
CIO was looking to implement Microsoft Dynamics 365 for Finance and Supply Chain Management (“Dynamics 365”) and consolidate their Houston, Stockton and Vernon sites on a single legal entity by migrating Houston legal entity from D365 and Los Angeles from AX 2009 To achieve the future organizational business To achieve the goals, We partnered with Microsoft Gold Partner to replace Microsoft Dynamics 2009 with Dynamics 365 at the LA and Houston Divisions. The management team has identified this as the next opportunity to continue the modernization of Client’s business systems and streamline its business processes.
We help organizations to smoothly transition to MS Dynamics 365 FnO (cloud ERP) using our proven implementation methodology Contact us
Utilizing the Microsoft Dynamics 365 Implementation Methodology, we have successfully executed MS Dynamics 365 implementation projects by adhering to a proven, reliable, and replicable approach. Our efficient D365 implementation project methodology is a culmination of refined practices managed by TCGI over numerous years, ensuring successful project execution driven by results.
Approach Overview: TCGI’s methodology adopts a top-down approach where Client objectives are transformed into Business Releases (BR). These BRs enable iterative releases of specific capabilities, each with predefined value for the Client.
Key characteristics of the approach include:
- – System Readiness: Validating system functionality meets client specifications.
- – Data Readiness: Ensuring the migrated data is confirmed.
- – People Readiness: Preparing and training Microsoft D365 users before Go-Live.
- – Business Releases Concept: Segmentation into smaller, measurable sub-projects.
- – Controlled Customization Development: Focus on structured testing for meeting business requirements.
Business Releases Defined: A Business Release signifies changes at the system, organization, or process level, bringing improvement, value addition, or problem resolution. This strategy allows the project to break down into smaller subprojects, each targeting measurable and business-focused objectives.
Project Phases:
After defining Business Releases, TCGI initiates phases as follows:
- Initiate
- Structure and Analyze
- Design and Build
- Confirm and Deliver
- Deploy
- Operate
Phase Overview & Outcomes:
Initiate Phase:
- Purpose: Get business case approval and buy in from key stakeholders.
- Activities: Business case creation, conducting feasibility study, create a project charter.
- Controls: Key Stakeholders and Executives approval, Project charter, and assemble a high level team.
Structure and Analyze Phase:
- Purpose: Review current business processes for precise future state requirements.
- Activities: Workshops for Solution Blueprint development and Steering Committee decision-making.
- Controls: Detailed plan creation for Design Phase based on gathered business requirements.
Design & Build Phase:
- Purpose: Configuration of D365 as per Solution Blueprint.
- Activities: Functional testing, solution documentation, and validation.
- Controls: Iterative processes for configuring Business processes, integration testing, and maintaining approved solutions.
Confirm and Deliver Phase:
- Purpose: Finalizing Business Release deployment.
- Activities: Acceptance tests for process functionality and readiness for Go-Live.
- Controls: Log issue resolution for operational readiness, Steering Committee Go/No-Go decision.
Deploy Phase:
- Purpose: Preparing for operational deployment and support.
- Activities: End-user training, mock cut-over, and operational support initiation.
- Controls: Post-deployment review, support transition to Managed Services, & configuration stability.
Operate Phase:
- Purpose: Operational support.
- Activities: Transition to operation and post-go-live support initiation.
- Controls: Post-deployment review, support transition to Managed Services, & configuration stability.
Process Control:
- Steering Committee approval for deviations from approved solutions.
- Avoiding last-minute changes before Go-Live unless approved.
- Monthly financial closure as a measure of operational control and readiness for Managed Services transition.
TCGI’s methodology provides a structured, phased approach, ensuring comprehensive analysis, design, testing, and operational readiness for successful project implementation.
MAJOR COMPONENTS TO BE EITHER MIGRATED OR CONFIGURED ON MS DYNAMICS 365 FnO
| Business Function | Business Process | Business Function | Business Process | Data Migration | |||
| Sales | Prospect and Customer Management | Finance | Accounts Payable | Master data | Chart of Accounts | ||
| Customer Relationship Management | Accounts Receivable | Financial Dimensions | |||||
| Sales Quotes | Cash and Bank Management | Customers | |||||
| Sales Orders | Credit and Collections | Customer Addresses | |||||
| Price management | Financial Reporting | Vendors | |||||
| Procurement | Vendor management | Costing | Vendor Addresses | ||||
| Master planning | Sales and use Tax | Products | |||||
| Purchase Requisitions | Budgeting | BOM’s | |||||
| Purchase Orders | Quality management | Nonconfirming material management | Routes | ||||
| Requests for Quotation | Return processing | Resource | |||||
| Transfer Orders | Transportation | Inbound Load Planning | Resource Group | ||||
| Price management | Outbound Load Planning | Warehouses and Locations | |||||
| Warehouse | Receiving and putaway | Appointment Scheduling | Item / Product Groups | ||||
| Pick, pack and ship | Production | BOMs | Vendor Groups | ||||
| Mobile Device | Routes | Sales Tax | |||||
| Receiving | Production Planning and Scheduling | Customer Group | |||||
| Production Reporting | Inside Processing | Transactional data | Open Accounts Receivable | ||||
| Picking | Outside Processing | Open Accounts Payable | |||||
| Shipping | IT | Environment Setup | Open Sales Orders | ||||
| Inventory Management | Inbound Operations | Security (Worker/ Worker group) | Open Purchase Orders | ||||
| Outbound Operations | DevOps | Inventory Balances (Quantities) | |||||
| Quality Assurance | Advanced Warehouse Mobile Requirements | Open Production Orders | |||||
| Physical inventory | SK Global Integration | Resources/Resource groups | |||||
| Cycle Counting | Handheld Configuration | Open bank transactions | |||||
| Inventory control | WM App | Trial balances | |||||
Why do you trust Trivedi Consulting Group to implement MS Dynamics 365 FnO ERP solution?
We have helped our clients’ by executing and managing their initiatives to implement Dynamics 365 FnO ERP solution and provided following deliverables listed in the following matrix:
| # | Deliverable | Description | Frequency |
| 1 | Resource Plan | Overview of Project team’s schedule. Created in Microsoft Office. | Project initiation (one time) |
| 2 | Project Plan | Activity, task, and timeline detail for Structure and Analyze. Created in Microsoft Office. | Project initiation (one time) |
| 3 | Weekly Project Update | Summary of accomplishments, key decisions, and potential roadblocks. Created in Microsoft Office. | Weekly |
| 4 | Meeting & Activity Schedule | Summary of upcoming meetings and activities for teams. Created in Microsoft Office. | Bi-Weekly |
| 5 | Environment Plan | Overview of the system environments to be used during implementation. Created in Microsoft Office. | Project initiation (one time); Approval |
| 6 | DevOps Project | Project within Azure DevOps used for tracking progress and executing on the SDLC | Project initiation (one time) |
| 7 | Kickoff Materials | Summary of project scope, methodology and objectives | Project initiation (one time) |
| 8 | Draft Foundational Designs | Initial design approach to strategic areas of the system. Created in Microsoft Office | One time Requires approval |
| Organizational Structure | |||
| Product Master – Chart of Accounts | |||
| Financial Dimensions | |||
| Costing Model – Pricing Model | |||
| Material Movement | |||
| Standards – ISV Selection | |||
| 9 | Requirements Traceability Matrix | Collection of process workflows for each functional area of the project | Ongoing |
| 10 | Maps business functions and processes to unique scenarios and requirements. Created in Azure DevOps | One time | |
| 11 | Gap List with Complexity Estimates | Listing of system gaps (i.e. requirement is not met by standard software function/ acceptable workaround). Created in ADO | One time |
| 12 | Data Migration Approach | Documented approach and training plan for the migration of data | One time |
| 13 | Security Approach | Documented approach and training plan for the migration of data | One time |
| 14 | Implementation Deployment Schedule | Timeline for remaining phase activities. Created in Microsoft office | One time |
| 15 | Scenario Sprint Schedule | Allocation of scenarios to specific Build sprints. Created in Azure DevOps (ADO) | At sprint initiation |
| 16 | Development Release Roadmap | Allocation of custom development activities to specific Build sprints. Created in Microsoft Office. | One time |
| 17 | Deployment Statement of Work | Contract for remaining implementation scope, activities, and estimated costs. | One time |
| 18 | Test Scripts | Work item created to document, test & validate a business scenario. Created, tested and validated by client. Created in ADO | Ongoing Requires approval |
| 19 | Functional Designs | Functional design documents created for modifications to D365. Documents will be associated to work items within ADO | Ongoing Requires approval |
| 20 | Technical Designs | Technical design documents created for modifications to D365. Documents will be associated to work items within ADO | Ongoing |
| 21 | ITC Plan | Documented plan to be used during the Integrated testing Cycle | One time |
| 22 | CRP Plan | Documented plan to be used for conference room pilot (CRP) | One time |
| 23 | UAT Plan | Documented plan to be used for user acceptance testing | One time |
| 24 | Training Plan | Documented plan to be used for end user training | One time |
| 25 | Training Procedures | Documented training material for end user training | One time |
| 26 | Cutover Plan | Documentation on activities to be executed during the cutover to Dynamics 365. | One time |