Leader Under 40: Tony Paine
Tony Paine, 37
President and CEO, Kepware Technologies, www.kepware.com
Electrical Engineering, University of Maine, Concentrations: Computer Software + Hardware Design
Paine has been a key contributor to Kepware Technologies’ growth and success in developing communications solutions for automation. He started in software development in 1996, grew into the role of chief software engineer in 1999, took over technical vision of the company, and became a shareholder in 2006 as executive vice president / chief technology officer, who was asked in 2009 to take over the role of president responsible for all operations. He has participated on industry standards committees to help drive the direction of technology in automation. Involved closely with the Maine university system, he works with faculty and students to promote controls engineering, is on the Electrical and Computer Engineering Advisory Council, and speaks at student events.
Paine is involved in the Maine Handicap Skiing program, assisting instructors with his child’s lessons. He also contributes to fundraising events for this program.
As an owner and president of a small business, Paine admits that most of his extra engineering-related activities do involve Kepware. He has spent a significant amount of time with the university and several of its engineering students—through events, the scholarship program, and the internship program advocating the need for educating and growing our next generation of engineers—specifically in the world of automation.
Paine was the first person in his family to graduate from college, working more than 32 hours a week during high school to save for school. This was done while maintaining honors and participating in a variety of sports. In sixth grade, he developed a software solution that allowed him to use an old [Tandy Corp. Radio Shack] TRS-80 Model 4 computer and a Panasonic dot matrix printer to write and print reports for school. Paine knew then he wanted to be involved with the interoperability of software and hardware.
Not having a lot of money, he worked out a home-brewed solution (above) with a donated computer and printer. “From that moment on, I knew I wanted to be involved in developing software which controlled hardware at some level.”