Michael
W. Parks

I help organizations make technology practical, dependable, and understandable.

Technology leader in Atlanta, working across IT operations, cloud platforms, automation, and applied AI.

About

My career lives where technology, organizations, and people meet.

I’ve worked across IT operations, application development, infrastructure, web technology, and technical enablement, usually in places where the right answer has to be practical, dependable, and easy to explain to the people who rely on it.

These days I’m most interested in the point where emerging technology becomes genuinely useful: AI, cloud platforms, automation, data, and the business systems that tie them together.

Technology leadership

Running reliable services, guiding technical teams, and tying technology decisions to what the organization actually needs.

Applied AI

Following AI and machine learning closely, with a bias toward small experiments that produce useful results.

Cloud and platforms

Applying cloud services, Salesforce, and automation so teams spend less time on busywork.

Web and digital systems

A long-running interest in the web, application development, and the infrastructure underneath it.

Selected work

A few things I’ve built, led, or fixed.

Engineering intranet, Lockheed (mid-1980s–early 1990s)

Like most large corporations, Lockheed ran its business systems on proprietary networks from IBM, HP, and DEC. Alongside them, we maintained a company-wide Unix network over Ethernet where engineers could communicate and collaborate using open technologies: TCP/IP, FTP sites, and later Gopher and early hypertext documents viewed in text-based browsers.

We packaged these tools into a formal suite used by the engineering community, outside the proprietary business systems. In 1993 I set up a web server with HTML pages and linked images, viewed in the brand-new Mosaic browser, and we called the Mosaic team at NCSA with questions. It was one of the earliest corporate intranets, built on open standards years before the term existed.

Shop floor management system, Lockheed, Marietta (late 1980s–early 1990s)

As group engineer, I led the design of a prototype shop floor management system for the C-130 and F-22 assembly lines in Lockheed’s B-1 building. Both programs shared the same work instruction, tooling, and scheduling systems, so my team built one common platform: touch screen X terminals on the floor, backed by DEC servers, putting real-time production information in the hands of the mechanics building the aircraft.

The floor adopted it quickly, and mechanics helped us demonstrate it to senior military and executive visitors. We also connected it to the emerging Internet so walk-ups could check weather forecasts and other information, and people used the terminals at all hours of the night. It anticipated much of what the industry later called manufacturing execution systems.

Lockheed mechanic Mr. Worley touching an inspection call sheet on a touch-screen X terminal in a shop-hardened enclosure, with aircraft assembly in the background
A Lockheed mechanic, Mr. Worley, using one of our touch-screen X terminals on the Marietta assembly floor, early 1990s.

Center for Manufacturing Information Technology, Georgia Tech (1994–2004)

Small and mid-size Georgia manufacturers needed ERP, CAD/CAM, and bar coding, but had few neutral ways to evaluate them. I founded CMIT within Georgia Tech’s Economic Development Institute: an 8,000 square foot “virtual teaching factory” with a working shop floor (CNC mill and lathe, assembly and inspection benches, conveyor, inventory tracking, and data collection), a front office organized around engineering, accounting, scheduling, and CAM, and a 17-seat networked training room. The shop floor ran a live process: wagon parts designed in the front office, CNC programs downloaded to the floor, and jobs tracked through machining and assembly with touch-screen terminals, bar coding, and a wireless inventory network feeding data back to the office. Vendors partnered with us so visiting management teams could see systems running and choose technology suited to their own processes.

Working with Georgia Tech’s regional offices and Georgia Power’s Technology Application Center, I held workshops across the state on topics from ERP selection to “Internet for Manufacturers,” and opened a videoconferencing center linking Georgia companies with engineers at NASA’s Marshall Space Flight Center. In late 1994 I built CMIT’s website, one of the earliest at Georgia Tech; a 1996 snapshot is still on the Wayback Machine. Most people don’t know that the Buzz Electronics Lean Overview course taught all over the US by MEP Centers and others for almost three decades was literally invented here at CMIT right on this shop floor. That’s why it was named “Buzz” Electronics.

The CMIT shop floor in the mid-1990s, with a touch-screen terminal in a shop-hardened enclosure, a CNC machine, flow-through storage racks with totes, and office workstations
The CMIT shop floor, with the touch-screen data collection terminal at left.
The CMIT website homepage as it appeared in 1996, with icon navigation for About CMIT, What's Hot, Tour, Feedback, Partners, EDI Staff, Courses, and Services
The CMIT homepage, archived November 1996.

AI is the focus today

Today I live in Salesforce, Wordpress, SQL Server, and Quickbase. Supporting and customizing nine different Salesforce orgs using PMM, and building Wordpress front ends using vibe coding AI tools like Claude Code, Codex, and Antigravity.

Perspective

I’ve worked hands-on with every tech wave since punch cards.

Each one arrived with big promises. These are the ones I actually used, where I used them, and what I built. The tools kept changing, but the goal never did: make the work clearer, faster, and less frustrating for the people doing it.

The technologyThe placeThe experience
Punch cards and batch mainframesU.S. Air Force, base supplyUpdating inventory records on an IBM mainframe, one punched card at a time. Thank you to Mrs. May’s typing class in HS!
Teletype terminalsU.S. Air Force, base supply; University of ArkansasEntering aircraft part orders into the base IBM mainframe, then writing interactive BASIC programs on teletype machines in college. These machines seemed amazing since responses were returned from the mainframe in real time!
Timesharing servicesEthyl CorporationBuilding SAS and IMPLAN models for batch processing on mainframes. Building plant cost accounting and financial modeling systems was way more fun than it sounds!
Personal computersLennox Industries headquartersDeveloping manufacturing productivity apps in BASIC, and SAS programs that analyzed plant production data over PC-to-mainframe links. Thanks to IE magazine for inspiration!
LANs and EthernetLockheed, MariettaNetworking the PCs in every department and connecting them to mainframes, minicomputers, and the early Internet.
Unix workstations and relational databasesLockheed, MariettaBuilding shop floor systems that supported C-130 and F-22 aircraft assembly. DEC Ultrix, Sun Solaris, IBM AIX, and VAX/VMS were all the rage during this time at Lockheed!
Mosaic and the first web serversLockheed, MariettaBuilding one of the earliest corporate intranets and web servers, and calling the Mosaic team at NCSA with questions. Gopher, Telnet, Bulletin Board Systems, and WAIS servers with hypertext browsers all composed our intranet.
The World Wide WebGeorgia Tech, CMITBuilding CMIT’s website and teaching manufacturers how to build their own sites and use the WWW in manufacturing.
Cloud and SaaSGeorgia TechReplacing on-premises services with platforms running entirely in the cloud. Salesforce, Mailchimp, Quickbase, ActiveCampaign, Slack, Monday.com, Airtable, and Smartsheet just to name a few!
Generative AIGeorgia Tech, todayBuilding web front-end applications on Salesforce back ends for program management and CRM.
Fifty years of technology, one career.

Now

Learning how AI fits into ordinary work.

Not demos, but the practical systems around them. Right now that means Python, cloud AI services, and testing where automation genuinely saves time versus where it just moves the work somewhere else.

Off the clock I’m following sports (and riding the fantasy football roller coaster), tinkering with side projects, and enjoying Atlanta, a city where technology, education, business, and community constantly overlap.

Updated September 2026

Contact

If you’re working on something interesting in technology, I’d like to hear about it.