Saddle Creek Logistics Services
(May 2002 - April 2013)
Overview
My time at Saddle Creek Logistics Services spans more than a decade and represents the formative period of my work in warehousing and logistics systems. During that time, my responsibilities evolved from hands-on RF systems and facility infrastructure into business continuity, data integration, and enterprise-scale systems design.
This progression established many of the operational instincts and system priorities that continue to shape my work today.
Progression and scope
I began at Saddle Creek working directly with RF terminals, warehouse systems, and on-site infrastructure across multiple facilities. This work required close alignment with warehouse operations and exposed the realities of maintaining technical systems in environments where uptime, physical conditions, and user behavior were tightly coupled.
From there, my role expanded into business continuity and disaster recovery. I was responsible for implementing and operating an off-site recovery data center, maintaining the corporate data center, and performing business impact analysis to identify operational risk and recovery priorities. This period reinforced the importance of planning for failure, understanding dependencies, and designing systems that could be restored under real constraints.
As Saddle Creek’s integration needs grew, my focus shifted toward data integration and systems automation. I worked with customers, vendors, and internal teams to design and support B2B and application-to-application integrations, replacing brittle, one-off solutions with more maintainable and observable systems. Over time, this work grew into broader architectural responsibility for the data integration platform and its supporting processes.
Throughout these roles, I consistently worked outside narrow job definitions, building internal tools, improving monitoring and visibility, and producing documentation and training to support operational continuity.
Areas of responsibility
Across roles, my work at Saddle Creek included:
- RF systems and warehouse-facing infrastructure
- Facility and data center operations
- Business continuity and disaster recovery planning
- Business impact analysis and risk identification
- Data integration and B2B communications
- Systems automation and internal tooling
- Documentation, training, and process improvement
While the emphasis shifted over time, the common thread was operational reliability in environments where system behavior directly affected physical operations.
Lasting influence
Saddle Creek was where I developed a durable understanding of how logistics systems behave under pressure: how failures propagate, how recovery actually works, and how technical systems must be designed to support the people who depend on them. That experience continues to inform how I approach integration, observability, and resilience in later roles.
This page provides historical context for my work in warehousing and logistics systems. Broader discussion of domain focus and approach is covered in the Warehousing and Logistics Systems section.