5 trigger moments for digital transformation

The best times to digitalize your product-development process.

1 of 2 < 1 | 2 View on one page

By Mark Taber, PTC

trigger moments imageIndustrial organizations of all types need to digitalize their products and processes in order to stay competitive in the Internet of Things (IoT) era. This includes making data accessible throughout the organization, ensuring all stakeholders are on the same page, and making information traceable throughout the product lifecycle. Frankly, if now is the first time your organization is considering digitalization, you’re already behind.

Changing one’s organization’s product development process can be challenging. Indeed, organizations can take small steps toward digital transformation, rather than completely disrupting their systems in one fell swoop. And while it’s important to not delay, there are a few “trigger moments” when the entire organization may be especially ready to embrace change. In fact, these moments have helped many organizations across industries move digitalization projects to the top of their agendas and rally behind this new mindset.

1. A foray into connected products

From the Amazon Echo to the Fitbit, consumers are clamoring to get their hands on smart, connected products. Interest in self-driving cars is paramount and features such as self-braking and parking assist are at the top of every car buyer’s wish list. If your organization hasn’t already considered making its products smart and connected, then expect it will be in the next year or so.

Alternatively, an organization may consider ways to offer its product as a service. Trane, for example, sells its customers “conditioned air” rather than an air conditioning or heating units. By maintaining the unit on the customer’s behalf, Trane has taken on the burden of ensuring that the space—whether movie theater, office building, or other public space—is at a comfortable temperature for occupants. This is a major benefit and selling point for potential customers.

Before pursuing either of these innovations, however, the product development process itself must be IoT-enabled in order meet customer expectations of a smart, connected product or product-as-a-service. Being able to manage data end-toend—from engineering to the field and back again—allows manufacturers to take real-world information on their product and use it to either improve future generations of the product or to preemptively determine maintenance needs.

2. A merger or acquisition

Imagine that your organization has just merged with, absorbed, or been absorbed by another company. During the process, one of the key projects that the integration team will look to tackle is making sure that all employees are working on the same systems and platforms for easy collaboration among teams. This is the perfect time to look to transform the new, larger organization’s product development process. As the enterprise systems being used by both organizations are being evaluated, it is possible to determine where the greatest need is: whether building a digital product definition, offering universal data access, or ensuring digital product traceability throughout the lifecycle.

Rather than welcoming the acquired company to the team with credentials to the existing enterprise system structure—credentials that will most likely be overwritten in a few short years to make way for a digital transformation—it makes sense to immediately introduce all teams to a system that will aid the organization in its longer term IoT strategy.

For example, after car parts manufacturer ZF Friedrichshafen acquired TRW Automotive in 2015, it determined that it needed to deploy a unified product lifecycle management (PLM) system across the enterprise. This move would not only help all divisions remain aligned, but improve systems engineering and support global production as well.

3. The decommissioning of a legacy system

Perhaps you have had your PLM system for the past decade. It originally worked great and as your organization began to customize it to fit your needs, it became even better. But at some point, the PLM provider came out with an update to the software and, because of all of your customizations, you weren’t able to take advantage. Where once it had been a benefit, it was now a burden. Business decisions change over time and technology advances. Yet your team is stuck in the past because of its legacy system.

This is exactly what happened to one Fortune 500 engine manufacturer. Its outdated legacy system was becoming more and more expensive and took too much effort to maintain. The added desire to modernize its system and gain more analytical and digital capabilities was the catalyst to move away from this system and to invest in a new one that would enable it to digitally transform its business.

1 of 2 < 1 | 2 View on one page
Show Comments
Hide Comments

Join the discussion

We welcome your thoughtful comments.
All comments will display your user name.

Want to participate in the discussion?

Register for free

Log in for complete access.

Comments

No one has commented on this page yet.

RSS feed for comments on this page | RSS feed for all comments