Making Multi-Tiered ERP Architecture a Piece of Cake
We intend on talking to our experience as both field sellers at Microsoft & our backgrounds implementing F&O/AX/NAV/BC, highlighting the multi-tiered architectural approaches that we’ve come across as well as those we recommend given certain scenarios or conditions. As time progresses we are continuously seeing an expansion in customers with multiple ERP systems, which can quickly & easily become unwieldly. These could be customers that have acquired multiple orgs with differing ERPs or a single org allowing each division to select their own systems. As such, we want to talk to customers that are either at this point or leading up to it, to walk them through how different systems can be layered with others to create an overall solution. Some examples will include having a single instance of F&O vs multiple instances, using BC and F&O as a ‘hub and spoke’ model, or even using F&O as a ‘Tier 2’ solution for SAP using the clean core approach.
Learning Objectives:
- Ability to understand use case for both BC and F&O, as well as when to use them individually versus in tandem
- Strategic benefits and approach to a multi-tiered ERP architecture, not only limited to the D365 realm
- How to identify business processes for integration scenarios
Speakers: Dennis Chiu, Max Glass
Type: Breakout Session
Ability Level: 201 – Intermediate
Primary Product: Dynamics 365 F&O/AX
Track: Development & Architecture,Integration,Leadership
