1. Functionality and Implementation
QAD Configurator
Functionality and Implementation

2. Agenda Introduction What Does the QAD Configurator Do?
Compare / Contrast with Configured Products
Review of Functionality
Recommended Implementation Approach
Question and Answer

3. Introduction Andrew Hall First QAD Implementation in 1993
Joined Logan Consulting in 1995
Based in Minneapolis, MN
Numerous QAD Configurator Implementations

4. What does it do?
Embeds product knowledge into configuration model vs. “tribal knowledge”
Presents user with a plain English questionnaire to define the desire configuration
Think Customer Self Service
Enforces configuration rules
Identifies existing or new configurations
Automatically builds master data to eliminate Engineering overhead - Items, BOM, Routings, etc.

5. What about Configured Products?
Configured Products is not rules-based
Could yield an illogical configuration
Pricing limitations in Configured Products
No unique Item Number for Configured Products
Must link Sales Order to Work Order
Cannot inventory a Configured Product accurately
No sales history by specific configuration

6. Functional Review / Demonstration
Configurable Item
Configurable BOM and Routing
Features and Options / Questions and Answers
Sales Rules and Rule Tables
Product Configuration Rules
Questionnaire

7. Configurable Item
Test

8. Configurable BOM and Routing
Test

9. Features and Options
The Questions (Features) and Answers (Options)

10. Configuration Key
Test

11. Rules and Rule Tables

12. Rules and Rule Tables

13. Product Configuration Rules
Item Number Rule
Item Data Rules
Product Structure Selection and Assignment Rules
Routing Selection and Assignment Rules

14. Item Number Rule
Test

15. Item Data Rules
Test

16. Product Structure Rules
Test

17. Routing Rules
Test

18. Questionnaire Available in Sales Order, Sales Quote and Stand-Alone
Default values highlighted
Long questions and answers should be user friendly
Only available Features and Options are editable
Rules driven
Some may be excluded and some may be answered
Unique configuration determined by Configuration Key
Select existing item or build new item and all supporting data
Test

19. That is just…

20. Also… BOM and Phantom Type Configurable Items Item Master Comments
SO and SQ Line Rules
Multi-Level Configurable Items
External Entities
And so on

21. Implementation Approach
This is NOT an IT Project
If you cannot cogently describe the rules, ALL OF THEN RULES, then STOP!
Well, sometimes…
Focus Questionnaire on minimal possible subject matter expertise of the user
Sign-off on all documentation before any QAD entry
Test, Test, Test – Expect Iterations

22. Question and Answer