Production Data Collection: Tasks (Level 3)
- Collecting, retrieving and archiving information
- Should an MES provide functions for production data archiving?
- What kind of data should be processed?
- How long should this data be archived?
- Providing interfaces
- To which systems should interfaces be provided (eg PLS, LIMS, WM, ERP, Internet sources, cloud services, etc.)?
- How are these interfaces to be specified in detail?
- Which communication standards should be supported?
- Should online interfaces and archive interfaces be made available?
- Providing standardized reports
- Should an MES provide standard reports?
- Which reports should be created?
- Should reports be created automatically?
- Should ad-hoc reports be created?
- Should reports be distributed automatically (eg by e-mail?)
- Maintaining information for local process and production analysis and for reporting to higher-level logistics systems
- Should an MES provide data for operational evaluation and analysis as well as for transfer to higher-level logistics systems?
- What kind of data?
- Should the data be provided cyclically or on request?
- Should this data be visualized in the MES?
- Maintaining information for product tracking
- Should an MES manage product traceability data?
- What kind of data should be managed? Product / system properties, status information, etc.
- Providing compliance monitoring and alarm management functionality
- Should an MES provide functionality to monitor compliance requirements?
- Should an MES provide alarm management functions?
- What kind of alarm management functions (frequency analyzes (histograms), message sequence analyzes, hit lists etc.)?
- Providing product quality information for comparison against specification
- Should an MES provide product quality information compared to product specifications?
- Should this data be exchanged with other systems (LIMS)?
