Please Wait a Moment
X

Infor LX Tips, Infor LN Tips, BPCS Tips, Baan Tips, Infor M3 Tips & Infor ERP News

Crossroads Connections

Infor ERP Tips & News from the Experts

Infor LX | Infor LN | BPCS | Baan | Infor M3

Anthony Etzel

How to Improve Customer Shipments With OTTO - A Case Study

Setting Industry Service Standards

Shenandoah Manufacturing, a $20 million producer of poultry-raising equipment (heaters and brooders), had been having difficulty for some time shipping orders to customers in a timely manner. They had successfully implemented a popular ERP system and had been using it for more than 3 years, yet the situation didn't improve. 

Customer Service Representatives were complaining about the frequent backorders and late orders. Employees were giving it their best effort, but were frustrated, and customers were threatening to take their business elsewhere.

The company considered installing an APS system as a possible solution, but found implementation would be difficult, expensive, and running the system might be a challenging task as a number of key business practices would have to be changed. A consultant familiar with OTTO suggested they look at that product as an alternative to APS. Several OTTO aspects cited by the consultant convinced them to consider a cursorily review. Specifically:

  • The non-intrusive nature of the product.
  • It's relative inexpensive initial investment.
  • The low overall total cost of ownership.
  • The integration with their ERP system.

The initial demonstration was impressive. OTTO was installed on Shenandoah's server within 45 minutes of arrival and, most impressively, it was fully functional with their real “live” data immediately. Needless to say, the demo was well received. Even more importantly Shenandoah was able to “test drive” the software to prove its applicability before making any dollar commitments.

According to Mark Shank, Information Systems Manager, some baseline measurements were made last year, and it was determined that approximately 50% of their customer orders had shipped on time. As they began using OTTO, on-time order performance rose to 90% for the month. And Shenandoah caught up on its entire backlog and started working ahead on February's orders. In February on-time shipment performance jumped to 92% and subsequently on-time performance has ranged somewhere between 98.3% and 99.5% — well above the 96% goal set by Management.

OTTO provides the means for keeping the whole production organization focused on the few things that have to happen as the ship date approaches to get each order shipped on time. Components that have the potential for delaying an order are identified so they can be managed. Shenandoah's staff, a precious and limited resource, now concentrates on analyzing information and managing the right things at the right time rather than digging out date. To quote one production control individual: “what use to take hours now takes seconds.”

According to Roy Hackett, Plant Manager: "Knowing the right things to pay attention to at the right time — information provided by OTTO — has allowed on-time shipping to be improved by 40 percentage points in less than one month and a lead time reduction from 3-4 weeks to 1-2 weeks on the most important products"

Guessing at what and how much of the work being processed is for real customer orders versus planned orders is eliminated which is especially important when capacity is short during the heavy portion of the business cycle. 

“By focusing on the right things at the right time, production expedites and interruptions are far fewer, production flow is much smoother and productivity is significantly improved.”

Previous Article Crossroads RMC's Analytics Dashboard serves as the perfect complement to extend your MES solution
Next Article Steps to undo an IDF modification and restore to the default
Print
22627 Rate this article:
5.0
Anthony Etzel

Anthony EtzelAnthony Etzel

Other posts by Anthony Etzel

Theme picker

Contact author

Please solve captcha
x

Tips:  LX | BPCS | M3

Role-Based Security introduces Role type profiles and allows combining the use of Role profiles with the traditional LX User type security profile functionality. The new Role type profile can be defined to allow or deny access to All Products, Attention Key, Products, Programs, and Transaction Effects. Facility, Warehouse, and Company securities are still defined solely by the User profile settings and are not affected by the assignment of a Role. Where applicable, the Role authority is displayed alongside the User authority on the security profile maintenance screens making it easy to see where there are differences in authority between the User and the assigned Roles. 

When Users are assigned to Roles, security access in LX becomes a combination of authorities granted or denied by the Role, plus any User Exceptions. User Exceptions override authorities set by the Roles. A User can also be assigned to more than one Role.

12345678910Last

Theme picker

Tips: LN | Baan

Who gets involved?
  1. Most commonly Engineering is involved in writing the rules, creating the bills and routings.
  2. Sales or Customer Service determines the questions and the order they are asked in.
  3. Sales or Customer Service determines the rules for the pricing.
  4. Sales, or Customer Service, and Engineering work together in determining the part number, description and text.

What are the steps?

  1. You must start by defining the features and options (questions and answers) and the order in which these are asked. We work this out first using sticky notes and large easel paper. Normally during the process we find that we want to move these questions around. Setting them down on paper makes the process of getting the data into Baan much more efficient. We also then have a record of what decisions were made prior to entering the data. This is normally a joint effort of Engineering and Sales. This is required and must be the first step.
  2. Constraints for features and options. These are the rules for determining what questions are asked and which options are allowed. This is generally done by Engineering or whoever is responsible for the configurator. This is required.
  3. Generic Bill of Material. All possible bill options are entered here and constraints are written to determine which options are selected based on the answers to the questions. This is generally done by Engineering or whoever is responsible for the configurator. This is a required step.
  4. Generic Routing. Similar to the bill of material, but used for generation of the routing steps. This is generally done by Engineering or whoever is responsible for the configurator. This is optional.
  5. Generic Item Data. This consists of creating custom item numbers, descriptions, text, material, size or standard fields in the custom item master. This is generally done by Engineering or whoever is responsible for the configurator though Sales may have some involvement. This is optional.
  6. Generic Pricing. This is used to calculate the selling price based on the answers to the questions. This is normally a responsibility of Sales or whoever determines the pricing. This group is also trained on writing the constraints for this section only. This is optional.
First148149150151153155156157Last

Theme picker

Categories