Two systems, one goal: understanding PLM vs. IPLM in 3D IC design

Guest author: Vishal Moondhra, VP of Solutions Engineering for Perforce IPLM

Your team just made a critical design change to a single die within your complex 3D IC package. Three downstream teams are unknowingly working with outdated specifications, potentially triggering costly re-spins, missed deadlines and a cascade of frustration across the organization. This scenario isn’t hypothetical for the most semiconductor companies, it’s a recurring reality that exposes a fundamental challenge in 3D IC development: how do teams effectively manage the relentless pace of design iterations when every change ripples through multiple interconnected components?

The answer lies in understanding two distinct but complementary data management systems. While most engineering organizations know Product Lifecycle Management (PLM) well, far fewer understand IP Lifecycle Management (IPLM), and this knowledge gap creates real problems. Recently, Vishal Moondhra from Perforce illuminated this crucial distinction in a podcast discussion on data management in 3D IC design, explaining why teams need both systems working in concert to succeed.

Explore these concepts in greater depth in the full podcast episode where Vishal Moondhra breaks down the practical realities of managing data in advanced chip design.

Why PLM excels at the big picture (but fails at daily 3D IC design)

Product Lifecycle Management serves as the orchestrator of a product’s entire journey from conception through manufacturing to end-of-life. PLM excels at managing what Moondhra describes as “slow, heavyweight, product-level changes,” the decisions and processes that unfold over weeks, months or years rather than hours or days.

When teams coordinate with suppliers to secure components, when manufacturing engineers define assembly sequences, when product managers respond to market feedback or when compliance officers ensure regulatory requirements are met, they’re operating in PLM’s domain. The system provides a holistic view that keeps stakeholders from marketing to manufacturing aligned on current, approved product data. PLM answers questions about what the product is and how it will reach customers at a macro level.

This strength becomes a limitation when applied to the micro-level reality of 3D IC design. Engineers working on advanced chip designs make hundreds or thousands of changes daily. They iterate on IP blocks, run simulations, verify functionality, and collaborate across geographically dispersed teams. This fast-paced, granular design activity simply doesn’t fit PLM’s architectural assumptions. The system wasn’t built to track atomic-level changes or manage the complex dependency networks that characterize modern semiconductor development.

IPLM captures the atomic reality of design

IP Lifecycle Management operates at a fundamentally different level. Instead of managing product-level milestones, IPLM tracks the intellectual property at the heart of the design- individual dies, interconnections, verification environments and all associated data. When Moondhra talks about managing “atomic changes,” he’s describing IPLM’s core capability: tracking every modification, no matter how small, to every piece of IP.

This granular approach enables capabilities that transform how teams work. Engineers can experiment with different design approaches without affecting the main development branch, fostering innovation while maintaining stability. When a critical bug appears in a foundational IP block, IPLM understands which downstream components depend on that block, alerting teams to potential conflicts before they cascade into major problems. The system integrates with design tools and automation workflows, creating a seamless environment where simulation, verification and sign-off happen systematically rather than through ad hoc coordination.

Most importantly, IPLM provides a single source of truth for all design data. When teams across different locations need to collaborate, they’re working from the same verified information rather than hunting through email threads or shared drives for the latest version.

When one change breaks everything: The case for dual systems

The distinction between PLM and IPLM becomes compellingly clear when teams face cascading changes across a 3D IC package. Consider what happens when engineers discover a critical issue in a foundational IP block. Without robust IPLM, identifying all downstream IPs that utilize this block becomes a manual, error-prone investigation. Understanding the impact of a proposed fix requires coordination across multiple teams. Ensuring that updates propagate correctly to every affected component demands constant vigilance.

This is where atomic change management proves essential. By tracking modifications at the smallest indivisible unit, IPLM ensures that teams understand every change, assess its impact accurately and control its propagation systematically. A change to one die’s power distribution network might necessitate adjustments in thermal management on another die and timing closure modifications on a third. IPLM makes these dependencies visible and manageable rather than leaving teams to discover conflicts during integration.

The alternative, managing 3D IC design without purpose-built IPLM, creates what Moondhra describes as a poor data environment. Engineers waste time hunting for the correct version of design files, often working with outdated or incorrect data. Teams duplicate effort by re-running simulations or verification steps because they can’t confirm they have the latest inputs. New team members struggle to onboard, facing a steep learning curve as they try to understand the complex web of design data and dependencies.

These inefficiencies extend beyond project timelines and budgets. When engineers spend their days battling data management problems instead of solving design challenges, frustration builds and innovation suffers. The human cost of inadequate data management- demotivation, reduced productivity, eventual burnout- rarely appears in project post-mortems, but it shapes team effectiveness profoundly.

Aspect	PLM (Product Lifecycle Management)	IPLM (IP Lifecycle Management)
Primary focus	Product journey from conception to end-of-life	Individual IP blocks and design components
Change management	Slow, heavyweight, product-level changes	Atomic-level, real-time design changes
Timeline	Weeks, months, years	Hours, days
Stakeholders	Marketing, manufacturing, suppliers, compliance	Design engineers, verification teams
Data granularity	High-level product specifications	Detailed IP dependencies and modifications
Integration	Supply chain, manufacturing systems	Design tools, simulation environments
Primary questions	What is the product? How will it reach customers?	Which IPs are affected? What changed and when?
Best use cases	Supplier coordination, regulatory compliance, manufacturing planning	Daily design iterations, dependency tracking, version control

The integration that changes everything: PLM + IPLM

The semiconductor industry is increasingly recognizing that effective 3D IC development requires both systems working together. Collaborations like the one between Perforce and Siemens are creating connected workflows that bridge the gap between fast-paced IP development and broader product lifecycle management. These integrations ensure that daily design activity feeds into product-level decisions seamlessly while product-level constraints and requirements flow back to design teams in actionable form.

When IPLM and PLM connect properly, teams gain visibility across the entire development spectrum. Design changes that have manufacturing implications become visible to production planning. Supply chain constraints that affect component selection reach design teams before they’ve committed to approaches that won’t work. Verification results that indicate schedule risk trigger appropriate escalation to program management.

This integration represents more than technical connectivity between systems. It reflects a fundamental shift in how organizations approach 3D IC development, recognizing that the unprecedented complexity of these designs demands purpose-built data management at every level.

Evolve or fall behind

The semiconductor industry stands at a critical juncture where traditional approaches to data management are reaching their limits. As 3D IC designs continue to evolve—incorporating more dies, more heterogeneous integration, and increasingly sophisticated interconnect schemes—the data management challenge will only intensify.

The evidence is compelling: Organizations that establish robust IPLM practices now, integrated with their existing PLM infrastructure, are positioning themselves for sustainable competitive advantage. These teams aren’t just managing complexity more effectively; they’re creating environments where engineers can focus on solving technical challenges rather than hunting through email threads for the latest design files.

Organizations that recognize this distinction and implement both systems appropriately are building the foundation for innovation in an increasingly demanding landscape. As the complexity of 3D IC development continues to accelerate, the question isn’t whether purpose-built data management will become essential—it’s whether your organization will establish these capabilities proactively or reactively.

The future belongs to teams that understand data management as an enabler of innovation, not an administrative burden. Those who act on this understanding today will define tomorrow’s semiconductor breakthroughs.

---