Mar 26

Written by: Hall
3/26/2010 6:50 AM 

I recently completed an assessment project at a client where Logan Consulting lead a QAD 8.6 implementation back in 2000. A part of the project involved the implementation of a third-party supply chain management package due to the client's need to ensure finite capacity and material planning. This SCM package met the need of scheduling, but has been complex, costly, and caused problems with the lower level material planning, forcing the client to develop offline Access tools.

With the evolution of QAD's tools around planning and scheduling, including the latest (and greatest!) browses in .NET that allow for component checks across master schedule (WO's) and repetitive schedules, we are able to replace ten year old SCM technology and Access add-ons with an easy to implement browse. By upgrading to 2009SE, we can replace significant complexity and cost with a no cost standard browse that is seamlessly integrated with QAD applications since it is a QAD application.

The bottom line is that QAD functionality is not static. What may not have been available 10 years ago is nearly guaranteed to be available now. Therefore, if you are still running 8.6, 9.0 or eB2.1, and especailly if you have numerous bolt-on apps, it is worth your while to spend a week or two taking a second look at your business requirements and comparing them to what QAD can do out of the box in the 2009SE standard bundle. It is likely that you will be able to reduce the complexity of your applicatoin stack which meeting your current business requirements.