It is very important that companies realize that the true purpose of a cycle count program is to identify the causes of invetnory inaccuracies and then put corrective actions in place. It is not to simply make correcting inventory transactions. I am sure that I have blogged on this topic before, but I think this difference gets lost in some organizations. If the effort isn't made to identify the cause of inaccuracies and put corrective actions in place to prevent future issues, then inventory accuracy will not truly improve. Therefore, though QAD provides the tools to identify items to count, adjusting transactions, and audit reports, much of the heavy lifting of a true cycle count program occur outside the system. Organizations must dedicate the necessary resource(s) to track down the cuase of inaccuracies and then implement corrective actions. Without doing these crucial steps, your cycle count program is reduced to a "count adjustment program", which does nothing to guarantee future inventory accuracy.

The QAD Configurator offers clients with rich functionality to configure product based on complex rules. However, before embarking on a configurator implementation, it is important to understand when this tool is valuable, as it doesn't fit in all instances. The following are some key areas to consider before assuming you are a configure to order environment.1. Do new confiugurations require engineering intelligence (e.g. testing, updated drawings, etc.), before the configuration can be considered approved? If yes, then you are likely to be an engineered to order environment, and a rules-based configurator may not serve to shorten the cycle between customer configuration and shipping and cash. If that is the case, you may not extract full value from a configurator.2. Are all purchased components required to support configurations defined and sourced? If not, then Purchasing or Sourcing will need to be involved in new configurations, and again, you may not shorten the cycle on delivery new product to Customers.3....

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...

In today’s global economy, corporations must find ways to balance supply and demand not only across sites, but across the entire supply chain. QAD’s Enterprise Operations Planning has the functionality to do just this. QAD’s EOP uses actual Forecast, Sales, Production, and Inventory data to calculate a plan to support pre-defined target inventory levels and centralize the production planning and purchasing activities into a global Master Scheduling function.The Enterprise Operations Plan module has the following utilities and functions:• Demand import and consolidation from multiple sites and databases (including external data sources)• Integration with Resource Planning• Planning at family and/or end-item levels• Weeks of Coverage by effective date for Target Inventory Planning• Source Matrix by effective date for supply and demand relationships between sites• Allocation of production demands across sites and production lines by percentage• Production demand transfer to other modules• Simulation Planning•...

One of the most frustrating issues facing manufacturing companies is inventory inaccuracy. Inventory accuracy is a critical input to executing a successful supply planning process. A simple yet effect method for improving inventory accuracy is to implement the point of use (POU) inventory concept. POU creates a clear distinction in ownership between the storage warehouse and the production floor. Operations that do not have this separation in place often find it difficult to determine the root cause of inventory problems and instead of a solution, end up with finger pointing and reoccurrences of the problems. While this concept can be used with other manufacturing methods, the QAD Advanced Repetitive Manufacturing module makes utilizing POU a no-brainer. Once POU is properly implemented and executed it will not be long before the effort starts to pay off. Below are just a few of the benefits that can be realized immediately:• Clear definition between warehouse/storage inventory and shop floor inventory...

We are working with a real estate services firm that has implemented an ERP backbone in Europe. They have done a thorough job of standardizing and documenting their processes and procedures, knowing that they will be acquiring and absorbing other similar companies in the future to foster growth. As we prepare to help them roll out a U.S. division onto the same ERP backbone and process model, the foresight in defining and implementing a standardized process model, which is actually in use, has drastically reduced the expected time required for subsequent rollouts.Time savings in the U.S. will be in the upfront design, which is already complete based on a previously implemented model in Europe. Additionally, previously prepared procedure and end user training documentation will be heavily leveraged. Although seemingly a required step in any implementation, preparation of these design standards with an eye toward future rollouts will improve the quality of the design documentation and add future value through implementation...

We recently worked with a company that has grown through acquisitions over the years and now has three distinct companies under one corporate umbrella. It runs each company on a separate QAD database. This company thinks it will continue to use its existing QAD ERP backbone for most core functions. However, one of its divisions is not using QAD financials and therefore struggling to get itself to a position where it can easily consolidate financials under one Chart of Accounts and system.Management has been hesitant to make this migration because the company has not developed a Strategic IT Plan and has not confirmed a mid to long range systems footprint. Without this footprint and Strategic IT Plan, users and management are hesitant to make tactical decisions that could allow for more efficiencies in the near and long term. Unfortunately, many companies see the effort in developing a Strategic IT Plan as significant and onerous. However, the effort to gain management consensus and document the footprint can be...

In today’s competitive and high pace work force there is much pressure to cut cost and increase productivity across all industries. We find ourselves struggling however with a constant feeling of stress and work overload. Because of this we tend to focus our aggression towards excuses of lack of resources and increased workload. Is it really though? In the IT world we also feel a similar downward spiral of pressure to keep the business afloat with the latest technologies and real time data to perform at this pace. While often underappreciated it is none the less a much needed piece of your business. With the constant need of system enhancements to provide the business with the information to succeed it is easy to get lost in a department of chaos. Much like sound business processes can aid you in efficiently cutting cost and managing best business practices, having strong IT processes will do the same for your IT department. It really takes us back to the basics…..SDLC (Software Development Life Cycle)....

During the CAUG and QAD Teamwork meetings this past week, I came away quite excited about the new Master Scheduling and Production Scheduling workbenches that will be released later this year for both SE and EE running the .NET interface. These workbenches will offer intuitive, visual drag and drop features that I believe planners will find very impressive. Additionally, the workbench will incorporate component availability checks, ensuring that the schedule is achievable from both a material and capacity standpoint. Any QAD user that is currently scheduling using offline tools (Excel, Access, etc.), should assess these workbenches as soon as they become available as they should have a positive impact in any planning environment.

EDI is an ever changing means of B2B communication. Staying on top of it can often be a challenging task in itself let alone implementing it from scratch. Customers and Suppliers are constantly changing their specifications as their business practices or needs change. With a history of maintaining EDI solutions in the Automotive Industry I can contest to the demand of the time sensitivity to these changes as well. QAD’s EDI Ecommerce Module has proven to be an exceptional tool to aid in the effective and efficient transmission of EDI documents when implemented properly. In addition to the tools you use a solid error resolution process and document tracking methodology should be leveraged. Transmitting EDI is easy…resolving EDI transaction issues in a timely manner is whole other story. In industries where the timeliness and accuracy of the documents being sent hold such implications as expensive fines, low ratings, or even the possible loss of business partner or customer; a best practice or methodology...