Operational Analytics

Streamlining processes and reducing costs with analytics

2Market Fictional Logo

Logistic Operation Optimisation

As part of a collaborative project, I worked with a fictional logistics company, Altura Logistics, to optimize fleet operations and reduce delivery costs. The analysis focused on leveraging advanced data analytics to improve route efficiency, compare in-house and third-party delivery costs, and develop actionable recommendations to enhance operational performance.

Key Highlights:

  • Fleet Optimization: Identified inefficiencies in delivery routes using Python and statistical modeling, resulting in a projected cost reduction of nearly 10%.
  • Cost Analysis: Built a framework for evaluating in-house versus outsourced delivery operations, providing data-driven insights for strategic decision-making.

This project demonstrates my ability to turn work as part of a data analytics team and turn raw data into impactful strategies, ensuring operational success while maintaining confidentiality.

Driving operational efficiency and cost savings

Confidentiality Statement

 

To uphold client confidentiality and comply with non-disclosure agreements, the company name, data specifics, and proprietary methodologies have been anonymized. Any resemblance to real companies, individuals, or data is purely coincidental and unintentional.

picture showing graphs, magnifier, stationery and glasses

Fleet Optimisation

Leveraged Python and statistical modeling to analyze delivery routes, identifying inefficiencies and optimizing operations to achieve a projected 10% cost reduction.

Predicitve Modelling

Created predictive models to simulate various operational scenarios, supporting strategic planning and future-proofing logistics operations.

Client-Centric Recommendations

Delivered tailored strategies to improve delivery efficiency while maintaining high service quality, ensuring alignment with organizational goals.

Cost Analysis Framework

Developed a robust framework to compare in-house and third-party delivery costs, enabling data-driven decisions on fleet utilization and outsourcing.

Altura Operational Analysis Insights Report

This report evaluates the transition from an outsourced logistics model to an in-house delivery system, focusing on financial, operational, and strategic aspects. Key objectives include reducing costs, leveraging tax incentives, and optimising route planning to enhance efficiency. 

An in-house model can deliver an 8.8% cost saving within a 75-mile radius, supported by electric vehicle (EV) adoption and government grants. While the 20% cost-saving target remains unmet, the model offers significant non-financial benefits, such as greater operational control, predictable costs, and improved customer service through consistent next-day delivery. Tax incentives like the First Year Allowance and fuel duty exemptions further enhance its financial viability. 

The proposed fleet meets next-day delivery demands effectively, even during peak periods. EV adoption aligns with sustainability goals, boosting environmental branding and cutting carbon emissions. Trial of route planning software is recommended to further maximise fleet efficiency, along with setting KPIs. 

Beyond a 75-mile radius, in-house delivery is less cost-effective, prompting consideration of alternative growth strategies. Long-term opportunities included regional expansions.

Background/Context: 

  • The objective of this analysis is to determine whether transitioning to an in-house delivery model is commercially and operationally viable compared to the current outsourced logistics services. 
  • Key analytic questions: 
    • What are the comparative costs and operational efficiencies of outsourced versus in-house logistics? 
    • What combination of vehicles will optimise in-house delivery efficiency while minimising operational costs and staffing needs? 
    • What route planning strategies can further reduce costs and environmental impact? 
    • What would be the associated capital investment and potential tax savings?

Project Development Process:

1.Data Cleaning Process 

The data cleaning process involved steps for checking missing values, duplicates and addressing incomplete data issues. Ways to merge the three sheets were evaluated. Unnecessary columns were removed from the DataFrame, and columns were renamed to ensure consistency. 

  • Missing Values: missing values were handled with targeted approaches. Missing despatch dates were filled with random values based on delivery proportions, while missing delivery costs were excluded and weights calculated. A random forest model was used to address the high volume of missing values in ‘CubicMPerUnit’ to preserve data variance.
  • Incomplete Postcode Data: to address incomplete postcode data, we generated a new DataFrame from Ordnance Survey Code-Point Open data and validated the provided Postal Sectors against this official dataset. This allowed us to calculate each postal sector centroid’s geographical coordinates. 
  • DataFrame Merge: The order detail variables were aggregated based on their OrderID. This approach ensured that the merging process did not generate duplicates. After evaluating various merging methods, a left join was selected to maintain flexibility for future analysis. This choice was particularly beneficial for preserving data with unmatched rows that could have become relevant later.

2. Exploratory Data Analysis 

  • Initial data exploration involved descriptive and basic visualisations. Outlier analysis was conducted using boxplots and descriptive statistics. However, following a thorough examination of the data and discussions with Altura, many identified outliers were determined to be valid and were subsequently included in the final analysis. 
  • Excluded data points: weekend dispatch days, cancelled/ deleted orders, samples, direct orders dispatched by suppliers directly and orders above 15 pallets. This resulted in 5% of data points unsuitable for route planning. However, the costs of these points were manually added to the final monthly costs. 
  • A cumulative analysis revealed that only 18.5% of orders fell within a 50-mile radius, prompting an extension to 75 miles, covering 33.7% of orders. Beyond this, our analysis highlighted that returns diminish. See our long-term recommendations below for potential strategic in-house delivery expansion options. 
  • See Appendix 3 for detailed insights into the data cleaning and analysis.

3. Data Visualisation

  • Visualisations were designed to convey insights to technical and business stakeholders, balancing functionality, accessibility and aesthetics. Types of Visualisations 
    • Bar graphs: used for categorical data to highlight magnitudes.
    • Line graphs: Depict trends, such as the cumulative percentage of orders by distance.
    • Maps: Intuitively display geographic data such as delivery routes and charging station locations. 
    • Tables: Present multiple data fields concisely where visualisation isn’t effective.
  • Colour Scheme: 
    • Green, aligned with Altura branding, is the primary colour, paired with purple for contrast and readability. 
    • A green-purple gradient minimises visual clutter, except in maps where distinct colours are required to easily identify categories. 
    • Grey replaces purple in dual-category bar graphs to emphasise green, highlighting key data.
  • Accessibility 
    • n the graph below, the colour palette was chosen for suitability with colour blindness, as colour is a key element of the map.
    • In other graphs, alternative methods such as varying bar sizes or adding labels ensured colour wasn’t the sole differentiator.
  • Size & Layout 
    • Horizontal or vertical bars were selected to optimise slide layout in the presentation, with data labels replacing x-axes for clarity.

Technical Overview of The Code 

 

Preferred Tools and Workflow Development: 

 

The primary tool for the analysis was Python, chosen for its robust data processing, modeling, and visualisation capabilities. While R was initially considered for generating DataExplorer reports and exploratory analysis, its integration with Python proved time-consuming. Consequently, R was used only in the early stages, and Python was used exclusively for the main analysis. Tableau was employed for preliminary data verification and visualisation. It helped ensure data accuracy and provided insights into daily order volumes and delivery locations. Although creating a Tableau dashboard was not within the project scope, these visualisations informed Python based analysis and grounded the team’s direction. 

 

A modular approach was adopted to streamline the workflow. Smaller workflows were created for specific processes such as fleet optimisation, geolocation, and competitor analysis. Where appropriate, these were later integrated into the main process workflow for a cohesive analysis. Code blocks that were lengthy to run were kept in the separate supplementary workflow. The team initially used Google Colab for collaborative coding but transitioned to an offline workflow due to execution time issues. Strict version control, daily updates, code block numbering and a shared GitHub repository ensured seamless collaboration and documentation.

 

Key Analytical Techniques and steps

 

  • Fleet-optimisation: Fleet optimisation minimised operational costs while meeting delivery demands within the 50-mile and 75-mile radii. The approach used: 
    • Linear Programming (LP): Optimised continuous variables such as delivery distance and vehicle utilisation. 
    • Mixed-Integer Programming (MIP): Handled discrete decisions, including fleet composition and vehicle assignment. Key constraints included vehicle capacity, driver shift limits, and delivery timeframes. Seasonal demand fluctuations were accounted for in cost projections. Refer to Appendix 3 and the final presentation for a detailed breakdown of the constraints.

 

  • Route Optimisation: To enhance delivery efficiency, clustering techniques grouped orders within the 50- and 75-mile radii, aligning vehicle capacity with geographic demand. Manual adjustments accounted for major road access, HGV restrictions, and EV charging network to ensure route accuracy. 
    • HGV Routing: Prioritised highways and motorways to reduce transit times due to local restrictions. Minimised HGV usage overall, focusing on bulky items aligned with their capacity. 
    • EV Charging Analysis: Infrastructure analysis showed sufficient charging stations for electric VANs but limited support for LGVs and HGVs. No additional adjustments were needed for VAN routes within the radii. This ensured compliance with road restrictions and operational efficiency while supporting sustainability goals. See Section 6.5 of the Main Workflow Notebook for further details. 
    • Vehicle loading algorithm: This algorithm was not integrated into the main workflow due to time constraints and scope requirements. 

 

  • In-House Fleet Expansion: Stakeholder feedback emphasised optimising operations within the 50- and 75-mile radius, as expanding beyond 75 miles from a single site was deemed cost-inefficient. Long-term strategies suitable for Altura were explored: The main approach included in the shortened report is establishing new sites: Using geospatial and heatmap analyses to identify high-demand regions for additional hubs. 

 

  • Competitor Analysis: The competitor analysis involved data scraping to extract customer sentiment. While not a primary focus of the presentation or report, it offered valuable insights into review trends and areas of dissatisfaction among customers, supporting the evaluation of potential improvements for Altura’s operations. Please refer to Appendix 3. for a detailed description of the coding steps and methods. 

 

Patterns, Trends, and Insights 

 

  • Cost Savings Opportunity with Larger Delivery Radius: Despite falling short of the 20% savings target, the in-house model delivers significant benefits in cost control, brand visibility, and customer experience. An 8.8% cost saving is evident within a 75-mile delivery radius. In-house costs would remain predictable and stable compared to fluctuating third-party rates.

 

  • Strong Demand for 2-4 Day Delivery and Potential to Offer Free/Low-fee Next Day Delivery Orders placed before 16:30 are consistently dispatched the same day, demonstrating efficiency and enabling next-day delivery. 

 

  • Technological Integration in Logistics & Fleet Optimization:  While charging infrastructure for electric vans is well-established, the network for electric LGVs and HGVs needs further development to support broader adoption. The recommended fleet will include electric vans for boxed items and fuel LGVs/HGVs for palletised or bulky items. LGVs will handle narrow city routes, while HGVs will focus on motorway-accessible locations. BP Pulse supplies nearly a third of charging stations, ensuring coverage along key delivery routes. Its monthly subscription lowers charging costs, while 150kW fast-charging boosts efficiency and maximises delivery time.

 

  • Vehicle Costs Considerations: One-off purchase costs are £66k for vans, £145k for LGVs, and £230k for HGVs. EVs qualify for a £5,000 grant per van and seven tax savings. Staffing includes 1.5 drivers per vehicle and one manager per 15 drivers. On-site charging stations, costing £20,000 each, can support two vans simultaneously.Investing in route planning software will be needed to ensure efficiency and minimise costs and operational strain. Optimised Fleet Strategy for a 50-mile Radius - Dividing into five strategic regions based on clustering and major road access. Recommending 17 vehicles (8 vans, 6 LGVs, 3 HGVs) to efficiently manage demand, including next-day delivery and seasonal surges.

 

  • Financial Advantages of Tax Incentives: Although fleet ownership requires significant capital, it provides tax savings2, builds equity, and stabilises costs. A phased 5-year vehicle replacement cycle maximises resale value and ensures continuity. Monitoring EV advancements will support future fleet expansion in line with Altura's growth goals.

 

  • Strategic Future Expansion Opportunities & KPIs: 75-Mile Radius Expansion Strategy: Divided into 9 regions, doubles customer reach and capacity, requiring 29 vehicles (16 vans, 7 LGVs, 7 HGVs). Offers significant long-term cost savings over third-party logistics. Strategic focus on expanding into high-demand hubs like London and Manchester-Leeds. Leveraging KPIs such as on-time delivery and cost-per-mile will ensure continuous performance improvement and accountability.

Overall, we recommend starting with a 50-mile radius for in-house delivery and shortly after expanding to a 75-mile radius to further enhance savings while providing a more sustainable option for your customers and allowing future growth of the company with controlled costs.

Further Information

For more information about this project, including the complete report and presentation, please explore the links below. These resources provide detailed insights into the Altura Project. Due to non-disclosure agreements, the code is not publicly available. However, if you'd like to review the code, I can provide an anonymized version upon request. Feel free to get in touch!

Need tailored operational data analytics solutions? Let’s transform your data!

Book a consultation today to discover how I can deliver actionable insights to drive your success!

Stay Updated with Data Insights

blog picture

Welcome to my blog, where I share valuable information and perspectives on database management and data analysis services.

Explore my latest articles to stay informed and discover new trends in the ever-evolving world of data.

Whether you are a business owner, entrepreneur, or data enthusiast, my blog is the perfect resource for enhancing your knowledge and optimizing your data processes.

Join me on this journey of learning and innovation in the realm of database management and data analysis.

Latest Blog Posts

We need your consent to load the translations

We use a third-party service to translate the website content that may collect data about your activity. Please review the details in the privacy policy and accept the service to view the translations.