What Schneider Electric's PTC deal means for medtech teams using Arena

On October 5, 2026, Schneider Electric announced an agreement to acquire PTC, the parent company of Arena, in an all-cash deal valued at approximately $23.7 billion.

If your medical device company uses Arena, or you're currently considering it, you may be wondering what this means for you. Will anything change with the platform? Will Arena continue investing in the capabilities medtech companies need? And should this news affect your decision to use Arena long-term?

These are fair questions. While there's no reason to assume any immediate changes to Arena or its products, acquisitions of this size naturally raise questions about future priorities.

At Greenlight Guru, we work with medical device companies navigating these kinds of technology decisions every day. We know how much time, effort, and investment goes into selecting and implementing a quality management system. And we know that nobody wants to find themselves questioning that decision a year or two down the road.

So, we took a closer look at the announcement to help break down what happened, what it could mean for medtech teams, and what you should consider as you plan for the future.

BONUS CONTENT: Download our free QMSR inspection readiness checklist!

What we know about the acquisition (and what we don't)

According to Schneider Electric's announcement, the company has agreed to acquire PTC for $205 per share in cash, valuing PTC's equity at approximately $22.6 billion. The deal is expected to close by the third quarter of 2027, pending shareholder and regulatory approvals.

Schneider Electric is a global industrial technology company with a significant focus on energy management, automation, and industrial software. With the addition of PTC, which owns Arena, Schneider plans to connect product design and engineering data with manufacturing and operational systems.

That strategy makes sense for Schneider Electric's broader business. The combination of PTC, AVEVA, and Cognite could create new opportunities to connect engineering, manufacturing, and operational data across industries.

But what about medical devices?

Arena and medtech are both mentioned in the deal's investor materials. However, the announcement doesn't provide specific details about Arena's future roadmap, investment in medical device quality management, or plans to support the industry's unique regulatory requirements.

To be clear, that doesn't mean Schneider plans to reduce its investment in Arena or medtech. We simply don't know yet.

What we do know is that Arena will become part of a much larger industrial software organization, serving a broad range of industries with different needs and priorities.

For medical device companies, that's worth paying attention to. As regulations evolve and your products become more complex, you need to know that your technology partners will continue investing in the capabilities your business depends on.

How well does Arena meet the needs of medtech companies today?

Before looking too far into the future, it's worth considering what Arena does well today and where its approach may create challenges for medical device companies.

Arena has strong product lifecycle management (PLM) capabilities, particularly for companies managing complex bills of materials, product configurations, engineering changes, suppliers, and manufacturing processes.

For medical device manufacturers with complex hardware products, multiple manufacturing sites, or extensive supplier networks, those capabilities can provide real value. But there's an important distinction between managing a product's lifecycle and managing the quality and regulatory processes required to bring a medical device to market and keep it there.

Arena serves multiple industries, including electronics, medical devices, biotech, and connected products. Its platform is designed to be configurable across these different use cases. That flexibility can be useful, but it also means medical device companies may need to spend more time configuring workflows to align with regulations like ISO 13485, IEC 62304, and ISO 14971.

We've heard from medtech teams that Arena implementations can take months, sometimes several quarters, depending on the complexity of the configuration and validation work involved.

That's something worth considering, especially if your team is already stretched thin.

If you're evaluating Arena, we'd encourage you to look beyond the list of available features and ask how much work it will take to get those features working for your specific quality processes.

For example, how easily can your team connect design controls to risk management? What happens when a complaint leads to a CAPA, which then requires a design change, updated documentation, and employee training? Can your team follow that entire process and quickly retrieve the records needed for an inspection?

These are the everyday workflows that matter to medtech quality teams. And they're worth testing before committing to any platform.

What about software as a medical device (SaMD)?

This is another area we'd encourage medtech teams to look at closely, particularly if you're building software as a medical device (SaMD) or software-enabled products.

Arena has capabilities for requirements management and tracking software and firmware issues. But much of its positioning and functionality has traditionally centered on complex hardware and manufactured products.

For software-only medical device companies, the needs can look quite different. Your engineering team may be working in Jira, GitHub, or other software development tools. You're managing frequent releases, evolving requirements, software defects, testing, and changes that need to stay connected to your quality and regulatory records.

The question isn't simply whether Arena can manage requirements or track software issues. It's how well those capabilities work together in practice. Can you trace requirements through design, risk, testing, verification, and release? Can developers continue working in the tools they already use? And can your quality team maintain the documentation and traceability needed for compliance without slowing development down?

As software becomes an increasingly important part of medical device development, these questions will only become more relevant. And with no specific SaMD roadmap commitments included in the acquisition announcement, software-focused teams have another good reason to ask how their needs will be prioritized going forward.

That doesn't mean Arena can't support software medical devices. It means you should make sure the platform fits the way your team actually develops and maintains software, both today and in the future.

BONUS CONTENT: Dowlaod our free QMSR inspection readiness checklist!

Questions we'd encourage Arena customers to ask

If you're currently using Arena, there's no need to make a sudden change based on this announcement.

But if you're approaching a renewal, planning a new implementation, or evaluating your long-term quality management strategy, this is a good opportunity to ask a few questions.

Here are six we'd recommend discussing with your Arena representative:

1. What's planned for medical device quality management? Ask which medtech-specific capabilities are on the roadmap, who owns those priorities, and when you can expect to see them.
2. What has Arena delivered for medtech customers recently? Ask for examples of new capabilities released over the past 12 months that address medical device quality and regulatory requirements.
3. Can you connect us with customers like us? Look for references from medical device companies with similar products, regulatory requirements, and post-market quality needs.
4. How will integrations be prioritized? If your team relies on specific engineering, development, or enterprise systems, ask how those integrations will be supported and improved.
5. How easily could we access and migrate our data? Understand what your data export options look like, what formats are supported, and what a future migration would involve.
6. What does the acquisition mean for customer support and medtech expertise? Ask whether any changes are planned