1. First Article Inspection accelerator for Dynamics 365 Finance & Operations
Sales presentation
Name
Place | Date

2. 1 1 2 3 4 Agenda Recap of your requirements Best practice
Solution overview 4
Questions and next steps

3. 1 Discovery recap Meeting notes Your requirements
Leave blank for sales pitch

4. 1 Your requirements Change pressures Project scope Risk factors
Leave blank for sales pitch

5. Best practice in your sector

6. 2.1 To run a successful operation you need: Quality management
Productivity
Optimal procurement
Business performance visibility
Real-time supply chain view
Customer-centric approach
Inventory control
Demand forecasting
Healthy margins & cash-flow
Connected workforce
Integrated logistics
Multi-channel flexibility
Focus on productivity, quality management and real time view

7. 3
Solution overview
First Article Inspection for Dynamics 365 for Finance & Operations

8. Microsoft Dynamics 365 – Finance & Operations
3.1
First Article Inspection for Microsoft Dynamics 365 Finance & Operations
Common application platform: PowerApps, Microsoft Flow, Common Data Service
Microsoft AppSource
Power BI
Cortana
Intelligence
F&O
Microsoft Dynamics 365 – Finance & Operations

9. 3.2 Solution Overview | How the accelerator helps you Company pain:
When dealing with products that require certification.
The certification has a validation date.
Block the flow for the product certificate is out of date.
Without certification in place at the right time, the company is at risk of fines.
The accelerator helps by :
Identify the certification on the released product, with delay and type validation
Block the flow if the product certification is out of date.
Produces a list of out of date released products.
In the world of Manufacturing or Distribution, the products must follow an inspection cycle in order to always be up to standard. The objective is to lock specific flows if the article is not updated at its inspection level.
* When dealing with BOMs, products and components that require inspection and approval; it can be a complex task to manage all connected operations whilst inspection takes place
* This can lead to productivity loss and risk of unapproved products
* Locking specific flows is the article in question is not at its inspection level
* Extending standard Dynamics functionality with the creation and integration of five additional workflows from creation of sales order through to supplier order

10. 3.3 Solution Overview | Workflows and alerts
Creation of sales order line with released product:
Warn or Block based on FAI status
Creation production order with end product & BOM components selected:
Warn or Block based on component’s or end product FAI status
Production order creation:
Warn or Block based on routing header FAI status
Creation of purchase order line with released product:
FAI approval vendor parameters aligned
The flows that we have integrated into our module are as follows :
• When creating the sales order line: Warning or blocking based on the FAI status of the launched product.
• At the PO creation, when choosing the bill of material by component: warning or blocking based on the FAI status of the component.
• At the PO creation, when choosing the bill of material by component: warning or blocking according to the FAI status of the finished product (launched).
• At the PO creation, when choosing the route, we use the setting of the route header to do the same control.
• When the supplier order line is created, we use the FAI approval vendor parameter setting to do the same control.

11. 3.4 Solution Overview | Parameters – RELEASED Product
New folder added with FAI status, Validation date of inspection, Validity delay in month and Blocking or Warning message.
FAI Status value :
Without FAI
FAI to do
First inspection
Second inspection
FAI Validated
Message on the flow:
Sales order
Purchase order
Production order
Finished product
Component

12. 3.5 Solution Overview | Routing parameters
The accelerator has an additional FAI status on the standard route. With validation date of inspection, validity delay in month and blocking or warning message.
On the production order creation, the system uses this information to push blocking or warning message.
Need explanation text

13. 2.4 Solution Overview | Block workflows
Allows users to block the article in the following flows :
When creating the sales order line: Warning or blocking / to the FAI product status
At the PO creation, when choosing the end product and the BOM for components: Warning or blocking / at the FAI status.
At the PO creation, when choosing the route, the system uses the setting of the route header to make the same control.
When the supplier order line is created, the system uses the FAI approval vendor parameters to do the same control.

14. 4
Questions and next steps