Armstrong World Industries shares insights on automation challenges

Recent discussions among network engineers reveal challenges associated with automation, where initial successes can lead to bottlenecks. This situation is highlighted by Eric Anderson from Armstrong World Industries, sharing insights from a recent webinar.

Product and Operational Challenges

Anderson's team began automating simple tasks, such as service requests and Domain Name System (DNS) changes using Python scripts. These early achievements demonstrated the potential for time savings, which led to a surge in automation requests throughout the organization.

However, as demands increased, the team faced limitations due to a lack of sufficient coding and networking expertise. This resulted in automation efforts becoming unsustainable due to the reliance on a small group of knowledgeable staff, rather than a scalable process.

Need for a Scalable Solution

At a critical juncture, Armstrong's team recognized that their DIY automation was creating operational challenges, such as governance and visibility issues. Anderson noted, “Scripts were great until we needed governance, visibility, and security. That’s when we realized we needed more than code. We needed a platform.” This transition emphasizes the necessity of a structured solution for broader deployment.

Adopting Itential for Enhanced Capabilities

The integration of Itential's platform allowed Armstrong to build upon their existing Python scripts while adding necessary functionalities, such as orchestration and governance. According to Anderson, “We didn’t throw away our scripts. Itential let us onboard them, wrap them in workflows, and scale.” This combination led to measurable results, including substantial time savings.

Long-term Strategic Approach

In offering advice to peers, Anderson suggested, “Not everything should be automated. Pick the right problems, show the value, and grow from there.” This approach fosters trust and supports sustained investment in automation capabilities.

In conclusion, the insights shared underline that automation should evolve with organizational needs. When initial scripting efforts become limitations, adopting a structured platform may provide the necessary framework to scale automation effectively.