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
/ Categories: Infor LX & BPCS Tips

BPCS/LX Tip of the Week: Real Time Access to Your Data

Poor performance indicators make for poor outcomes.

Companies today continue to tolerate and accept how labor and production information is recorded, and the reliability on that information is questionable. In addition to collecting labor and production information, there are many other pieces of information manually recorded from the shop floor.

A critical element of information for productivity throughput would be to examine how much time the work center or machine was actually up and running. Downtime is another critical element of data that is usually manually recorded along with a reason identifying what caused production to stop. If this information is not provided on a timely and accurate basis, then what good is it anyway? Forms are filled out, data may or may not be keyed to a spreadsheet, the forms are sorted and filed, but is anybody really looking at the information that was recorded? Think about the amount of time it takes to manage the manual collection of information from your shop floor. 

What would real time access to data mean to your organization?
The benefits:

  1. Real Time Production Visibility
  2. Reduced Paperwork Load
  3. Downtime and Scrap Visibility
  4. WIP Inventory Visibility
  5. Improve Efficiency, Capacity Utilization

Optimize Your Manufacturing Today!

Previous Article Baan/LN Tip of the Week: Real Time Access to Your Data
Next Article Baan/LN Tip of the Week: Top 10 Survival Tips For Manufacturers
Print
39364 Rate this article:
No rating

Contact

Anthony Etzel

Anthony EtzelAnthony Etzel

Other posts by Anthony Etzel

Contact author

Please solve captcha
x

Tips:  LX | BPCS | M3

Tips: LN | Baan

Use this session to to define which fields must be audited, and when they must be audited.

Note: 

  • It is not required to define the fields that must be audited. Only if not all fields in a table must be audited, you must specify the fields that must be audited. You can only specify fields for a table for which you selected Specified in the Field Selection field of the Audit Tables by Profile (ttaud3120m000) session. If you selected All in that field, all fields in the table are audited, and no fields can be specified.

  • For a detailed explanation of the relation between audit type and field specification, refer to the section How to determine the net result of the audit configuration in the Audit Configuration Management topic.

  • The audit functionality uses the positive approach, which means that you can only specify which tables and fields must be audited, but not which tables and fields must not be audited. Therefore, through the appropriate menu, commands are available to load all (key) fields. You can then delete the fields you do not require.

Categories