Database for Service Level Optimization Using an Integrated Logistics Management Model at an Auto Parts Importing Company
Description
This dataset contains data collected and processed for the research article titled "Service Level Optimization via an Integrated Logistics Management Model at an Auto Parts Importing Company." The data include: inventory records, the technical gap, economic impact, identification of root causes and reasons, cash flows for three scenarios (optimistic, pessimistic, and moderate), components of the integrated model, and Arena simulation runs for those three scenarios, covering the year 2025 within the context of an auto parts importing company in Lima, Peru. The purpose of this dataset is to enable the replication of statistical analyses, validate the analyzed logistics and operational management indicators, and serve as a foundation for future research in the field of industrial engineering.
Files
Steps to reproduce
Simulate a regular client order placement: Log into the inventory or sales management module and create a new outbound request containing critical high-demand SKUs (e.g., SKU 1002118 - PIÑON 1 4 C. MITSUBISHI or SKU 1001371 - CULATA 1 2 C. TOYOTA 14B). Generate and print the system-automated picking list: Issue the warehouse picking ticket for the designated operator. Notice that the physical layout allocation maps do not correlate with actual physical storage locations due to suboptimal slotting. Execute physical item retrieval (Picking Stage): Proceed to the warehouse storage racks to retrieve the items. Due to an inaccurate inventory registry (low ERI) and disordered zones, the operator will experience a location mismatch error, leading to picking the wrong SKU variation or failing to find the item. Identify stockout or mismatch at quality check/staging: Attempt to confirm the order dispatch. The system or the validation operator will trigger a discrepancy alert (e.g., Rotura de stock or Error en la selección de productos) because the physical item does not match the requested technical specifications. Log order status as "Retrasado" (Delayed): Due to the internal operational bottleneck and the need for a secondary manual search or procurement request, the order misses its scheduled commitment date (Fecha_Compromiso), generating a service level failure and financial impact.