Using Git workflows to improve efficiency, reduce bottlenecks
A control system integrator used Git-based software to improve automation as well as increase onboarding of new hires and scaling quality.
Learning Objectives
- Understand how onboarding new talent and teaching them programming is a major bottleneck challenge.
- Learn how Git-based software can remove some of the potential bottlenecks.
- Discover the importance of having one source of truth for programming and the benefits of open communication for the team.
Git-based software insights
- Git-based software by Copia Automation is designed to accelerates development for multiple programmable logic controller (PLC) programming environments and prevent people from overwriting others’ work.
- Developing a streamlined platform where programmers can learn from one another and develop a single source of truth is critical in reducing bottlenecks and letting younger engineers learn without tying up senior engineers.
Since 1996, engineering consulting firm DMC has helped clients improve productivity of their manufacturing facilities with custom automation software and control systems. They work in many industries such as automotive, food and beverage and even Navy battleships.
According to project director John Sullivan, who oversees the automation business for the western United States, the need for services has never been higher.
“At times, we’ve had to reluctantly turn down work because demand outpaced our ability to hire and train controls engineers fast enough,” he said.
Sullivan’s assessment is underscored by a recent Control Systems Integrators Association (CSIA) survey showing aggressive hiring of systems integration engineers in 2021, but also a 16.5% turnover rate across the field.
The biggest bottlenecks are onboarding new talent and best leveraging the use of senior engineers’ time. Software engineering students typically specialize in more common text-based programming languages versus the visual ladder logic diagrams used to program programmable logic controller (PLC) computers for machine automation. Consequently, young engineers need to be paired with experienced mentors for training that can take months.
At DMC, where software projects can range from a solo programmer up to 25 engineers, the summers tend to have larger teams when new talent can learn from their experienced colleagues. Senior engineers’ schedules quickly get filled with frequent design reviews. By winter, Sullivan said, smaller teams become more prevalent as college grads are more able to work on their own.
To streamline its design review process, version control and collaboration, they rely on Git-based software, which accelerates development for multiple PLC programming environments. This enables teams to work on the same files without the risk of overwriting work from others. Git branching and merging capabilities bring the same collaboration benefits to ladder logic programming as text language projects.
The visual diffing with comments provides easy-to-read, color-coded comparisons that do not require reviewers to download and open files within the original integrated development environment (IDE).
Code reviewers can detect and fix mistakes earlier
Sullivan said the automatic rendering of PLC programming languages and the ability to quickly visualize changes, without using the original IDE, significantly speeds up the feedback loop between junior and senior engineers.
“When leading multiple projects, our senior engineers are saving up to a day a week, because of the faster code reviews,” he said. “Plus, we’re reviewing more frequently. We’re catching more mistakes before they get deployed or tested. And because we always see the visualized code before merging, we’re also making fewer mistakes.”
Sullivan said the switch to Git-based software has made his team much more efficient.
“Git alone does a good job managing the project history but falls short when reviewing code,” Sullivan said. “Whenever someone committed a code change, our senior engineers needed to open up two copies of the development environment, do a compare between the two platforms, and manually copy the code before recommitting. We now see the changes right away and simply click a few buttons to merge those changes. A 45-minute process now takes 15 minutes.”
Overcoming a “10-year problem” for automation programming
Copia Automation’s Git-based version history captures all coding changes for the lifecycle of a project, allowing teams to revert to any earlier iteration if desired. The edit history is invaluable for collaborating team members to be aware of the latest project changes, but it is also useful for managing what DMC calls the “10-year problem.”
The challenge is maintaining the ability to provide ongoing support for machines and systems long after installation.
“I recently heard from a customer who we last worked with us seven years ago. Both the engineer and the manager who worked on that project are gone. It’s so important to always be able to find the files from legacy projects,” Sullivan said. “I had another customer who had a power surge, and they lost their program. They unfortunately never managed to keep a copy of it. So we needed to grab old code and help them redeploy to a new set of hardware so they could get back up and running. Now, moving forward, anyone on our team will be able to handle the 10 Year Problem without the original engineer who worked on the project. Having the context and information from the entire lifecycle of a project is super valuable.”
Having one source of truth in a secure central repository also helps the team collaborate more efficiently with its manufacturing clients.
“We have customers operating facilities where their engineers are making small code changes on a regular basis. When things really go wrong, they call us,” Sullivan said. “And it’s our job to jump in and help figure out the problem. One of the keys to being successful is to be confident we have the latest code. Sharing the same repository enables this.”
Sullivan said he thinks it is “embarrassing” for the industry to still be relying on file names and shared folders. Git-based software, he said, helped them increased productivity and quality.
Darren Henry is vice president of marketing; Vaughn Varma is technical marketing manager at Copia Automation. Edited by Chris Vavra, web content manager, Control Engineering, CFE Media and Technology, cvavra@cfemedia.com.
ONLINE
This case study was highlighted in a February 2023 Control Engineering webcast:
CONSIDER THIS
How can changes in PLC programming workflow improve your automation?
Do you have experience and expertise with the topics mentioned in this content? You should consider contributing to our WTWH Media editorial team and getting the recognition you and your company deserve. Click here to start this process.