What was the distributed operating scope?
Dixie Electric’s technology remit covered 30+ US locations and 50 IT, software-development and automation staff. As Director of IT in the Midland-Odessa area, my responsibilities combined distributed IT operations, enterprise software and automation engineering. The role spanned April 2014–April 2016, before my move into education technology at DevCamp.
The count describes staff across IT, development and automation, not 50 AI engineers. The location figure describes US locations in that role. Both measures remain tied to the historical operating context instead of being repurposed as current Encapsa headcount or deployment scale.
What did Jordan lead as Director of IT?
I led the IT, software-development and automation group across the distributed organization. The scope included IT infrastructure, server architecture, enterprise integrations, electronic data interchange and custom applications. The record establishes a broad technology-leadership remit, not a separately dated implementation project with an invented transformation budget or outcome percentage.
This was an enterprise operating role rather than a consulting-client entry. The broader experience timeline also retains concurrent independent consulting, with clients labeled as engagements rather than employers. Preserving those distinctions keeps the leadership record and overlapping dates readable.
Which technology responsibilities were in the remit?
The confirmed areas were IT infrastructure, server architecture, enterprise integrations, EDI and custom applications. Together they describe infrastructure, data exchange and software delivery responsibilities across a multi-location business. The public scope summary does not invent particular vendors, incident statistics, availability targets or a security-certification claim.
The visual presents the staff and location scale together, followed by the responsibility areas. It is a historical leadership-scope map, not an architecture diagram, actual organizational chart or customer-system screenshot. Its purpose is to make the confirmed remit legible without implying undocumented implementation details.
- IT infrastructure
- Server architecture
- Enterprise integrations and EDI
- Custom applications
How does this experience relate to current leadership?
Dixie supplies historical enterprise operating context: 50 staff, 30+ US locations and a remit spanning IT, custom software and automation. Current Encapsa leadership is separate, with an eight-person team building a production AI platform. The progression is visible in the timeline without relabeling the Dixie role as an AI appointment.
The public record does not establish a quantified Dixie cost-saving, uptime improvement or business-growth result for this entry. The demonstrated evidence is operating scope and responsibility. Keeping the historical dates visible avoids presenting an older enterprise role as newly delivered AI work.
What does the record show?
| Measure | Record | Scope |
|---|---|---|
| Role | Director of IT | April 2014–April 2016, Midland-Odessa area |
| Staff | 50 | IT, software development and automation |
| Locations | 30+ | US locations |
| Infrastructure | IT infrastructure and server architecture | Organization-wide remit |
| Software and integration | Enterprise integrations, EDI and custom applications | Organization-wide remit |
Which skills does this project demonstrate?
- IT LeadershipLed 50 staff across 30+ US locations.
- Engineering ManagementManaged IT, software-development and automation disciplines.
- Enterprise ArchitectureIT infrastructure and server architecture responsibilities.
- Systems IntegrationEnterprise integrations and electronic data interchange (EDI).
- IT InfrastructureInfrastructure, servers and custom applications in a distributed operating remit.
What does this case study not claim?
- Historical Director of IT role, April 2014–April 2016; not a relabeled AI role.
- 50 staff spans IT, software development and automation. 30+ refers to US locations.
- No budget, cost-saving, uptime, certification or transformation metric is invented.