In LX, the actual costs that can be set up fall into three categories: Material, Labor, and Overhead. If your LX database is set up properly with the LX cost accounting, you should be able to identify:

• How much the item should cost
• How to track the cost of work underway
• How much the item actually did cost
• Why the job cost varied from the expected cost
   

Capturing the data to track activity with associated costs can be time-consuming. With an MES solution, the information you need for costing is tracked instantly.

One common GRINYA issue would be incorrectly entered Integration Setups.

Check the Baan or LN manual for recommended Integration setups. If such a mistake were to occur, it is important to know for what period of time the Integration was in error.

To ensure, it’s recommended that the Integrations Setup tables should be audited either through Baan/LN or Database Auditing. Corrections can be quickly calculated when an exact timeframe can be determined.

On February 18, 2016, the Maquoketa plant of Morrison Brothers went live with the Crossroads MES solution. The goal was to remove all the shop floor paperwork and eliminate the manual recording of production and labor. The company achieved this goal in just 96 days from project kick-off to go live. Included in the go-live was the ability to deliver drawings electronically to the Crossroads MES workstations. This was a critical component of the implementation as it ensured that each workstation would always be operating off the latest revision of the engineering documents.

A rollout of the Crossroads MES solution is planned for Morrison’s Dubuque plants later this year. 

Morrison Brothers is a major producer of petroleum marketing equipment in the United States and abroad.

Here are some issues that you might run into if you stay on an old porting set too long:

• Incompatibility because of operating system patches
• Printing issues because of out-of-date libraries
• Potential performance issues if binaries are not updated
• Updating third-party products may not be possible because of dependencies
• Limited support from Infor
• Issues with updating database software/patches because of dependencies (if the database is also running on the same server as the application)

Need help getting on a newer porting set? Let us know! We’d be happy to help.