← Back to Work Resume

Safran Landing Systems

Capital Management Intern, Walton, KY May 2026 to Aug 2026

Overview

Spent the summer as the sole designer and builder of an enterprise capital expenditure tracking and reporting system for the Walton site. The work replaced fragmented SAP exports and spreadsheets with a centralized, auditable application, and it went into final testing ahead of an August 2026 production go-live.

The Problem

Capital expenditure reporting depended on data pulled by hand out of SAP and reconciled across a set of spreadsheets that had drifted apart over time. Different groups held different versions of what should have been the same numbers, and producing a report meant repeating a long manual process and hoping the sources agreed.

What I Built

  • Ran requirements discovery across finance, project management, and leadership, then reconciled conflicting source files into a single authoritative data model.
  • Automated SAP extraction and database refresh with Python, SAP GUI scripting, and batch files, cutting a manual reporting process down to a two-action workflow.
  • Deployed a split Microsoft Access architecture with a NAS-hosted backend and automated frontend distribution, so users always run the current version without manual installs.
  • Structured the schema for a later migration to SQL Server or Dataverse, rather than building something that would have to be thrown away to scale.
  • Documented the system for handoff so it survives past the end of an internship.

Skills & Tools

  • Python
  • SAP Automation
  • Microsoft Access
  • Database Design
  • Systems Analysis
  • Requirements Gathering
  • Documentation

How It Applies

This was the first time I owned a system end to end for a real organization: talking to the people who would use it, deciding what the data actually meant when sources disagreed, building it, and writing it down so someone else could take it over. The technical work mattered, but the harder part was reconciling what different departments each believed was true.

It also reinforced something the homelab had already taught me: design for the handoff. A system that only its author can run is a system with a single point of failure, and that is as true for an internship project as it is for infrastructure.