Why did Steve Heckman create Inductive Automation and Ignition instead of building another SCADA tool?
Answered at 8:00 in Built for the Operator: Julio Velasco on Design, Education, and a Career Shaped by Ignition · Ignited: Striking Industrial Automation Conversations
Why did Steve Heckman create Inductive Automation and Ignition instead of building another SCADA tool?
Steve Heckman, an integrator at CalMetrics, was frustrated that software licensing costs—for clients, tags, screens, and historical data—consumed 80 percent of project costs, leaving integrators only 20-30 percent profit from their engineering hours. His frustration with this business model led him to invent Ignition from the ground up to mitigate these pain points, including a new pricing model and open-source architecture that would benefit integrators and customers alike.
Full answer and detailsRead the whole answer, key facts and every other question from this episode
In short
Steve Heckman, an integrator at CalMetrics, was frustrated that software licensing costs—for clients, tags, screens, and historical data—consumed 80 percent of project costs, leaving integrators only 20-30 percent profit from their engineering hours.
Julio Velasco, Founder at IOScada · Built for the Operator: Julio Velasco on Design, Education, and a Career Shaped by Ignition · Ignited: Striking Industrial Automation Conversations · answer at 8:00
Key takeaways
- Steve Heckman, an integrator at CalMetrics, was frustrated that software licensing costs—for clients, tags, screens, and historical data—consumed 80 percent of project costs, leaving integrators only 20-30 percent profit from their engineering hours.
Quote to remember
“It's a gradual thing where you're basically getting all the devices that are edge devices or not even part of a network and then bringing them up to a point where now you communicate with them, which that's a huge feat.”
— Julio Velasco
The full answer · about 2 min
Steve Heckman, an integrator at CalMetrics, was frustrated that software licensing costs—for clients, tags, screens, and historical data—consumed 80 percent of project costs, leaving integrators only 20-30 percent profit from their engineering hours. His frustration with this business model led him to invent Ignition from the ground up to mitigate these pain points, including a new pricing model and open-source architecture that would benefit integrators and customers alike.
Key facts
- 2008-2009: Financial crisis period when Julio joined Inductive Automation / Calmetrics after being laid off
- 80 percent: Software licensing costs as portion of integrator project costs that frustrated Steve Heckman
- 20-30 percent: Remaining profit margin for integrators after software licensing fees
- Nearly 2 decades: Duration of Julio Velasco's involvement with Inductive Automation ecosystem starting around 2008
- Hundreds of plants: Number Julio has visited where operators don't know what firmware versions run on their PLCs
People, companies and topics mentioned
More answers from this episode
- 4:00Why is automation considered recession-proof in manufacturing?
- 12:15What is the difference between brownfield and greenfield in industrial manufacturing modernization?
- 19:50What is the problem with Industry 4.0 implementations that only add sensors and screens to legacy machines?
- 24:00What is the first step Julio Velasco takes when assessing a manufacturing facility for digital transformation?
- 24:50How does modernizing from serial-based protocols like DH45 to Ethernet-based communication improve factory infrastructure?