EU Data Act
Product Data Descriptions
Select your language to download as a PDF:
| Product Data | Type | Format | Estimated Volume | Continuous Generation | Real-time Generation | Access Information |
| Manual MHE (FLT) / Mobile Terminal Long Term Operational Activity | Usage statistics and KPI data, for reporting and operational dashboards. | Numeric values. Timestamps. Reference links. |
388 bytes per retrieval. | Yes. Data is generated as equipment and users perform tasks. |
Yes. As actions performed by operators. |
Data kept until purged automatically. Accessible off system via SQL reporting views. Cannot be deleted remotely. |
| Automated MHE Cumulative Operational Activity | Equipment Move Statistics. Fault Counts. Error Indicators. Used for operational reporting, long term fault analysis and dashboards. |
Numeric values. Timestamps. Reference links. |
212 bytes per retrieval. | Yes. Data is generated as equipment performs movements. |
Yes. As events occur from equipment. |
Data kept until purged automatically. Accessible off system via SQL reporting views. Cannot be deleted remotely. |
| Real Time Automated and Manual Stock Move Requests | Stock move requirements. Transitory data during physical moves. Data Represents "Movement Tasks". |
Numeric values. Reference Links. Text values. |
338 bytes per retrieval. | No. Data is transitory. |
Yes. As stock is allocated and moved. |
Data kept only as long as needed for the tasks, purged automatically (~hours). Not accessible off system. |
| Automatic Stock Data Adjustments | Stock attribute adjustments automatically generated based on configured rules, used in the process of managing stock where product meets rule criteria. | Numeric values. Text values. Reference links. |
230 bytes per retrieval. | No. Data is generated as stock meets rule criteria, and deleted as used or aged out. |
Yes. As stock triggers adjustment rules. |
Data kept only as long as tasks exists, purged automatically when age expired if not used (~month). Not accessible off system. |
| Automatic and Manual Print Jobs | Parameters needed to print labels, reports and operational paperwork. | Numeric values. Reference links. |
1127 bytes per retrieval. | No. Data is transitory. |
Yes. As print/data jobs created. |
Data kept only as long as needed for the tasks, purged automatically (~day). Not accessible off system. |
| Application: Usage Statistics | Operational usage statistics of the WMS Application Itself. Used to assess frequently accessed areas of the system. |
Numeric values. Usage counts. |
118 bytes per retrieval. | Yes. Data is generated on an ongoing basis. |
No. Data is batch-generated. |
Data kept until purged automatically. Not accessible off system. |
| Application: Configuration Event Logging | Operational events caused by configuration management. Used for audit reporting on application configuration changes. |
Numeric values. System parameters. Reference links. |
1013 bytes per retrieval. | Yes. Data is generated on an ongoing basis. |
Yes. As configuration changes made. |
Data kept until purged automatically. Accessible off system via SQL reporting views. Cannot be deleted remotely. |
| MHE Emulation Data | Operational and stock parameters when running with MHE emulation. Used to support emulation of automated MHE operations in a test scenario. |
Numeric values. String values. |
130 bytes per retrieval. | No. Data is transitory. |
Yes. As emulated MHE events occur. |
Data kept only as long as needed for the tasks, purged automatically (~day). Not accessible off system. |
| Automation State Data | Operational and MHE Current Status. Used to track internal state of automation. |
Numeric values. Text values. Reference links. |
335 bytes per retrieval. | No. Data is transitory. |
Yes. When automated equipment reports status. |
Data kept only as long as needed for the tasks, purged automatically (~day). Not accessible off system. |
| Operational & Stock Event History | Historic logging of operational and stock events. Used for long-term reporting and inspection of operational events. |
Numeric values. Text values. Reference links. |
413 Bytes per retrieval. | Yes. Data is generated on an ongoing basis. |
Yes. As stock and operational events occur. |
Data kept for compliance and archived on system. Accessible off system via SQL reporting views. Cannot be deleted remotely. |
| Customs/Bonded Stock Event History | Historic logging of excise-related stock events. Used for long-term reporting and compliance with tax authority. |
Numeric values. Text values. Reference links. |
1122 bytes per retrieval. | Yes. Data is generated on an ongoing basis. |
Yes. As excise (tax) related events occur. |
Data kept for compliance and archived on system. Accessible off system via SQL reporting views. Cannot be deleted remotely. |
| Customer Location Stock Age Data | Where configured, age of stock consignments to specific end Locations. Used to comply with end customer stock age requirements. |
Numeric values. Text values. Reference links. |
69 bytes per retrieval. | Yes. Data is generated on an ongoing basis. |
No. Data is batch-generated. |
Data kept for compliance and archived on system. Accessible off system via SQL reporting views. Cannot be deleted remotely. |
| Interface Generated Integration Data | Data created manually or via 3rd party systems. Used to define operations. |
Numeric values. Text values. Reference links. |
511 bytes per retrieval. | Yes. Data is generated on an ongoing basis. |
No. Data is batch-generated. |
Data kept until purged automatically. Accessible off system via SQL reporting views. Cannot be deleted remotely. |
| Integration Interface File Logs | Storage details & event logs of integration files. Used to support integration services. |
Numeric values. Text values. Reference links. |
428 bytes per retrieval. | Yes. Data is generated on an ongoing basis. |
No. Data is batch-generated. |
Data kept only as long as needed for the tasks, purged automatically (~month). Not accessible off system. |
| Application: Credential Metadata | Data of previous credentials to prevent re-use. Used to support security policies. |
Encrypted hashes. Reference links. |
42 bytes per retrieval. | Yes. Data is generated on an ongoing basis. |
Yes. As credentials are changed. |
Data kept for security compliance and rotated out. Not accessible Remotely. |
| Application: Encrypted Interface Transitory Data | Temporary encrypted payloads. Used to support integration services. |
Encrypted strings. Numeric values. |
1699 bytes per retrieval. | No. Data is transitory. |
Yes. When integration services require encryption. |
Data kept only as long as needed for the tasks, purged automatically (~day). Not accessible off system. |
| Resource Management Statistics | Data generated from operational events to support resource planning. Used for forecasting of resource requirements. |
Numeric values. Text values. Reference links. |
342 bytes per retrieval. | Yes. Data is generated on an ongoing basis. |
No. Data is batch-generated. |
Data kept only as long as needed for the tasks, purged automatically (~quarter). Not accessible off system |
| Operational Alerts | Alert data generated by abnormal events. Used for operational dashboards. |
Numeric values. Text values. Reference links. |
6435 bytes per retrieval. | No. Data is time bound and growth is capped. |
Yes. As operational events occur. |
Data kept only as long as needed for the tasks, purged automatically (~week). Not accessible off system |
| Equipment / Stock Association Data | Data generated during handling of stock. Used to support internal processes of handling stock. |
Numeric values. Text values. Reference links. |
169 Bytes per retrieval. | No. Data is transitory. |
Yes. As operational events occur. |
Data kept only as long as needed for the tasks, purged automatically (~day). Not accessible off system. |
| Transport Event History Logging | Data generated during stock handling via transport units. Used to support dashboard and reporting of load/trailer/yard. |
Numeric values. Text values. Reference links. |
462 Bytes per retrieval. | Yes. Data is generated on an ongoing basis. |
Yes. As transport unit events occur. |
Data kept for compliance and archived on system. Accessible off system via SQL reporting views. Cannot be deleted remotely. |
| Storage Location Event History Logging | Data generated during management of storage locations. Used to support audit and reporting of storage locations. |
Numeric values. Text values. Reference links. |
384 bytes per retrieval. | Yes. Data is generated on an ongoing basis. |
Yes. As storage location management events occur. |
Data kept for compliance and archived on system. Accessible off system via SQL reporting views. Cannot be deleted remotely |
| MHE Integration Message Logging | Data generated by communicating with MHE devices. Used to assist application support and diagnostics. |
Numeric values. Text values. Reference links. |
585 bytes per retrieval. | No. Data is time bound and growth is capped. |
Yes. As communication with equipment happens. |
Data kept only as long as needed for the tasks, purged automatically (~month). Accessible by support services off system. |
| Application Diagnostic Logs | Data generated by application during operation. Used to assist application support and diagnostics. |
Diagnostic log files. | 10k human-readable log files per retrieval. | No. Data is time bound and growth is capped. |
Yes. Continuously as the application is running. |
Data kept only as long as needed for the tasks, purged automatically (~month). Accessible by support services off system. |
| Integration Interface Data Files | Data transmissions generated by integration services. Used to communicate with external integration services. |
Integration data messages. | 100-200k application specific message files per retrieval. | No. Data is time bound and growth is capped. |
No. Data is batch generated. |
Data kept only as long as needed for the tasks, purged automatically (~year). Accessible by support services off system. |
| Operational Equipment Check History | Data generated during operational equipment checking. Used for audit and reporting of mechanical checks. |
Numeric values. Text values. Reference links. |
143 bytes per retrieval. | No. Data is time bound and growth is capped. |
Yes. When physical equipment checks are logged. |
Data kept for compliance and archived on system. Accessible off system via SQL reporting views. Cannot be deleted remotely. |
Speak to an expert
Get in touch to arrange to speak with one of our experts, who will be able to answer your questions and give you all the information you need.