1014-00006 · Meridian Design Systems, Inc · Analysis

ip-indemnification-analysis-memo.docx DOCUMENT IP / Technology

3 / 12 ← → ✕

MEMORANDUM

ATTORNEY-CLIENT PRIVILEGED AND CONFIDENTIAL ATTORNEY WORK PRODUCT

FROM: Monica Reyes, Associate, Calderwood & Harkness LLP

TO: Aaron Liu, Lead Associate, Calderwood & Harkness LLP

DATE: November 10, 2025

RE: IP Indemnification Analysis — Meridian Design Systems, Inc. Renewal ELA (MDS-ELA-2026-01192); Optiwave Semiconductor Corp.

MATTER NO.: 1014-00006

OFFICE: One Market Plaza, Spear Tower, 42nd Floor, San Francisco, CA 94105

Right-click to update Table of Contents

I. Executive Summary

This memorandum analyzes the intellectual property indemnification provisions set forth in the proposed Amended and Restated Enterprise License Agreement (Agreement No. MDS-ELA-2026-01192) (the "Renewal ELA") between Optiwave Semiconductor Corp. ("OWS" or the "Company") and Meridian Design Systems, Inc. ("Meridian"), and benchmarks those provisions against market-standard terms observed in comparable enterprise electronic design automation ("EDA") software license agreements. The purpose of this analysis is to inform OWS's negotiating strategy with respect to IP indemnification and related limitation-of-liability provisions in advance of OWS's delivery of its first substantive redline to Meridian's outside counsel.

The core tension in the current negotiation is as follows: OWS seeks uncapped IP indemnification from Meridian for third-party intellectual property infringement claims arising from OWS's authorized use of the licensed EDA tools. Meridian's current draft, by contrast, proposes an aggregate liability cap of 1× annual fees ($14.3 million at Meridian's quoted annual pricing of $14.3 million per year under a $71.5 million, five-year total contract value ("TCV")). Under Meridian's formulation, the IP indemnification obligation would be subject to the same cap that governs all other liabilities — meaning that OWS's total recoverable amount for all claims, whether arising from IP infringement, breach of contract, negligence, or otherwise, would be limited to $14.3 million in the aggregate.

Based on the analysis set forth below, our recommendation is as follows: OWS should maintain its position of a 2× annual fees general aggregate liability cap, with uncapped liability for IP indemnification, data breach, and willful misconduct. This position is well-supported by market practice — our review of comparable enterprise EDA transactions indicates that approximately 60–65% of agreements carve IP indemnification out from the general liability cap entirely — and is commercially justified given OWS's critical reliance on Meridian tools across its entire 280-seat design engineering organization. The potential consequences of a covered infringement claim (including forced cessation of tool use, delayed tape-outs, and downstream revenue losses) would far exceed any contractual cap pegged to annual fees, and the risk of infringement in the EDA space — driven by patent assertion entities, competitor patent portfolios, and cross-licensing disputes — is material and well-documented.

This memorandum is organized as follows: Section II provides background on the parties, the transaction, and the scope of this analysis. Section III analyzes Meridian's proposed IP indemnification provisions in detail. Section IV presents our market benchmarking findings. Section V addresses the interplay between IP indemnification, data breach, and willful misconduct carve-outs from the liability cap. Section VI sets forth specific drafting recommendations for OWS's first redline. Section VII outlines OWS's preferred, fallback, and walk-away negotiation positions. Section VIII summarizes conclusions and identifies next steps.

II. Background

A. The Parties and the Transaction

Optiwave Semiconductor Corp. OWS is a Delaware corporation headquartered at 4850 Great America Parkway, Suite 300, Santa Clara, California 95054. The Company is a fabless semiconductor design company specializing in the design and sale of high-speed optical transceiver integrated circuits ("ICs") and silicon photonics chiplets for data-center interconnect applications. OWS was founded in 2017 and has grown rapidly in the hyperscale data center and cloud infrastructure market. The Company is a portfolio company of Ridgeline Capital Partners, LP ("Ridgeline"), which acquired a 78% equity stake in OWS in August 2022 at an enterprise value of approximately $412 million. OWS currently employs approximately 340 people, of whom approximately 185 are design engineers who use EDA tools on a daily basis.

OWS's financial profile is relevant to the negotiation context. For the fiscal year ended December 31, 2024 ("FY 2024"), OWS reported revenue of $287.4 million and EBITDA of $51.7 million, reflecting healthy margins in its target market segments. OWS's total annual EDA software spend across all vendors was approximately $18.6 million for FY 2024, of which the Meridian portion under the existing Enterprise License Agreement accounted for approximately $9.2 million per year — representing nearly half of OWS's total EDA expenditure. The significance of Meridian's tools to OWS's operations cannot be overstated: the Company's core chip design workflows for optical transceiver ICs and silicon photonics chiplets are built on Meridian's platform, and any interruption in access to these tools would have cascading effects on tape-out schedules, customer commitments, and revenue recognition.

Meridian Design Systems, Inc. Meridian is a Delaware corporation headquartered at 2700 Orchard Parkway, San Jose, California 95134. Meridian is one of the three major EDA software vendors in the global semiconductor industry and provides a comprehensive suite of digital and analog design, verification, simulation, and signoff tools. Meridian is publicly traded on the Nasdaq Stock Market. The company employs approximately 4,800 people globally and reported FY 2024 revenue of approximately $3.1 billion. Meridian's scale and financial capacity are relevant to the IP indemnification discussion, as noted further in Section IV.E below.

Meridian's outside counsel for this transaction is Bexley Weir & Daly LLP, represented by Rachel Endo (Partner) and Kevin Matsuda (Associate), located at 525 University Avenue, Suite 1400, Palo Alto, California 94301. OWS is represented by this firm, Calderwood & Harkness LLP, with Conrad Ashby (Partner) and Douglas Tran (Partner) serving as the lead engagement partners, and Aaron Liu (Lead Associate) and the undersigned (Associate) handling day-to-day drafting and analysis.

B. The Original ELA and Proposed Renewal

The Original ELA. OWS and Meridian are parties to an Enterprise License Agreement designated as Agreement No. MDS-ELA-2023-00487 (the "Original ELA"), which became effective on February 1, 2023 and has a three-year term expiring on January 31, 2026. The Original ELA has a TCV of $27.6 million ($9.2 million per year) and provides OWS with 190 total seats — comprising 150 named-user licenses and 40 floating licenses — across three Meridian product modules: Meridian Marlowe Asset Management™ (physical design and layout), signalForge™ (signal integrity analysis), and VerifyPro™ (functional verification).

The Proposed Renewal ELA. The proposed Renewal ELA (Agreement No. MDS-ELA-2026-01192) would replace and supersede the Original ELA upon its expiration. The Renewal ELA contemplates a significantly expanded commercial relationship between the parties. The key commercial terms of Meridian's initial proposal, received by OWS on October 15, 2025, are as follows:

• Term: Five (5) years, commencing February 1, 2026 and expiring January 31, 2031.

• Product Scope: Expanded to include five Meridian product modules — the three existing modules (Meridian Marlowe Asset Management™, signalForge™, and VerifyPro™) plus two new modules: AnalogEdge™ (mixed-signal analog simulation) and PhotonX™ (silicon photonics design and modeling). The addition of AnalogEdge™ and PhotonX™ reflects OWS's growing need for integrated analog simulation capabilities and dedicated photonics design tools as the Company expands its silicon photonics chiplet product lines.

• Seat Count: 280 total seats, comprising 220 named-user licenses and 60 floating licenses. This represents a 47.4% increase over the Original ELA's 190-seat allocation (an addition of 90 seats) and reflects OWS's headcount growth in its design engineering organization and planned hiring through the Renewal ELA term.

• Pricing — Meridian's Initial Quote: TCV of $71.5 million ($14.3 million per year), representing a 55.4% increase over the current $9.2 million per year annual spend under the Original ELA. On a per-seat basis, Meridian's initial quote implies an annual cost of approximately $51,071 per seat.

• Pricing — OWS Target: OWS's commercial team, in consultation with Ridgeline's operating partners, has established a target TCV of $59.0 million ($11.8 million per year), which reflects a volume discount of approximately 17.5% off Meridian's initial quoted pricing. At 280 seats, this would yield a target per-seat annual cost of approximately $42,143. Pricing negotiations are being handled separately by OWS's procurement team (Sameer Iyer, VP of Finance and Operations), but the pricing outcome will directly affect the dollar value of any fee-linked liability caps.

The Renewal ELA also contemplates the introduction of Meridian CloudVerify™, a cloud-hosted verification compute offering that would enable OWS to offload certain computationally intensive verification workloads to Meridian's cloud infrastructure. The inclusion of CloudVerify™ introduces additional data security considerations, as OWS's proprietary chip design data — which constitutes highly sensitive trade secret information — would be transmitted to and processed within Meridian's cloud environment. The data security implications are addressed in the Data Security and Cloud Services Rider, which is being negotiated as a separate exhibit to the Renewal ELA and which is the subject of a companion memorandum from this team.

C. Scope of This Memorandum

This memorandum addresses the following specific topics:

1. Analysis of IP Indemnification Provisions: A detailed examination of the IP indemnification provisions as set forth in Meridian's proposed Renewal ELA, including the scope of the indemnity trigger, applicable exclusions and carve-outs, and remedial obligations.

2. Market Benchmarking: A comparison of Meridian's proposed IP indemnification terms against market-standard provisions observed in comparable enterprise EDA and software license agreements, drawing on publicly available information and Calderwood & Harkness's internal precedent database.

3. Interplay with Limitation of Liability: An analysis of the critical interplay between the IP indemnification obligation and the general limitation-of-liability provisions, including the treatment of IP indemnity, data breach liability, and willful misconduct within the liability cap framework.

4. Negotiation Positions and Fallback Options: Recommended negotiation positions for OWS, including an opening position, graduated fallback positions, and an identified walk-away threshold, with supporting rationale for each.

This memorandum does not address the commercial pricing negotiation, the Data Security and Cloud Services Rider (which will be addressed in a separate memorandum), the source code escrow arrangement (except insofar as it intersects with the IP indemnification analysis), or the general terms and conditions of the Renewal ELA beyond the specific provisions identified above.

III. Analysis of Meridian's Proposed IP Indemnification Provisions

A. Indemnification Scope — Meridian's Draft

Meridian's proposed IP indemnification provision, set forth in Section 9.1 of the Renewal ELA draft circulated on October 15, 2025, provides that Meridian agrees to defend, indemnify, and hold harmless OWS (including OWS's officers, directors, employees, agents, and affiliates) against any and all third-party claims alleging that OWS's authorized use of the licensed software, as permitted under the license grant set forth in Section 2 of the Renewal ELA, infringes any United States patent, copyright, trade secret, or other intellectual property right of such third party.

Several observations regarding the scope of this provision are warranted:

"Authorized Use" Limitation. The trigger for the indemnity obligation is expressly limited to OWS's "authorized use" of the licensed software — meaning use within the scope of the license grant. Under the Renewal ELA, the license grant permits OWS to install and use the five licensed product modules (Meridian Marlowe Asset Management™, SignalForge™, VerifyPro™, AnalogEdge™, and PhotonX™) on up to 280 seats (220 named-user and 60 floating), solely for the purpose of designing, simulating, verifying, and laying out semiconductor integrated circuits in connection with OWS's internal business operations. Any use of the software outside the scope of this grant — for example, exceeding the seat count, using the software for unauthorized commercial purposes, or sublicensing the software to third parties — would fall outside the indemnity trigger. This limitation is standard and generally unobjectionable.

Geographic Limitation. The indemnification obligation is limited to claims alleging infringement of United States intellectual property rights. While this is within the range of market practice for EDA licenses (given that most EDA software vendors are U.S.-domiciled and the predominant risk of IP litigation in the EDA space arises in U.S. forums), it is worth noting that some agreements extend coverage to claims involving foreign IP rights, particularly in jurisdictions where the licensee has significant operations. OWS currently conducts all of its design engineering in the United States (primarily at its Santa Clara headquarters and a satellite design center in Austin, Texas), so the geographic limitation is not a significant concern at this time. However, if OWS's design operations expand internationally during the five-year Renewal ELA term, this limitation could become more material. We flag this as a monitoring point but do not recommend expending negotiation capital on this issue at present.

Covered IP Rights. The scope of covered intellectual property rights — U.S. patents, copyrights, trade secrets, and "other intellectual property rights" — is reasonably comprehensive. The inclusion of trade secret claims is particularly important in the EDA context, given the frequency with which former employees of one EDA vendor move to a competitor and the resulting risk of trade secret misappropriation allegations that could implicate downstream licensees. The catch-all reference to "other intellectual property rights" provides additional breadth, though its precise contours are less defined. On balance, the scope of covered IP rights in Meridian's draft is within market range and does not require significant modification.

B. IP Indemnification Exclusions — Meridian's Draft

Meridian's draft sets forth four exclusions from the IP indemnification obligation in Section 9.2. Each is analyzed below:

(a) Modifications by OWS. Meridian's draft excludes from indemnification any claim arising from modifications made by OWS to the licensed software. This exclusion is standard in EDA licenses, as the licensor cannot reasonably be expected to warrant against infringement arising from the licensee's own modifications to the licensor's code. However, as discussed in Section VI below, the exclusion should be narrowly drawn to cover only modifications made by OWS without Meridian's consent, direction, or involvement. OWS occasionally makes customizations to Meridian tools through scripting and automation frameworks (e.g., Tcl/Perl scripts within the Marlowe Asset Management™ environment), and in some cases these customizations are made with the assistance or guidance of Meridian's professional services team. Modifications made at Meridian's direction or with Meridian's participation should not trigger this exclusion.

(b) Combination Claims. Meridian's draft excludes claims arising from the use of the licensed software "in combination with" non-Meridian products "not reasonably contemplated by" Meridian's documentation. This is the most significant exclusion from OWS's perspective, and it warrants careful attention.

The combination-claims exclusion is nearly universal in enterprise software licenses, and its inclusion in principle is unobjectionable. However, the breadth of the exclusion as drafted is a concern. In OWS's design engineering workflow, the Meridian tools are used in close integration with process design kits ("PDKs") provided by OWS's foundry partners — most notably Brindoval Foundry Services, Inc. ("Brindoval"), which provides the PDKs for OWS's primary 5nm and 3nm optical transceiver IC processes. The interoperability between Meridian tools and Brindoval PDKs is not incidental; it is a foundational aspect of OWS's design flow and is broadly contemplated by the industry. If the combination-claims exclusion were interpreted broadly, it could potentially exclude coverage for infringement claims arising from the standard combination of Meridian tools with Brindoval PDKs — effectively eviscerating the indemnity in the precise context where it is most needed.

We recommend that OWS push to narrow this exclusion by inserting qualifying language to the effect that the exclusion applies only to combinations that are "not reasonably foreseeable" or "not described in Meridian's documentation, interoperability specifications, or published compatibility guides." This approach preserves Meridian's ability to exclude claims arising from truly unforeseeable combinations while ensuring that standard PDK-tool combinations remain within the scope of coverage.

(c) Continued Use of Superseded Version. Meridian's draft excludes claims arising from OWS's continued use of any version of the licensed software after Meridian has provided a non-infringing replacement or update. This exclusion is reasonably standard and is the logical counterpart to Meridian's remedial obligation to modify or replace infringing software (discussed in Section III.D below). However, this exclusion should be subject to a reasonable transition period — OWS should not be expected to instantaneously deploy a replacement version across a 280-seat installation, particularly where the update may require regression testing and validation against OWS's existing design data. We recommend adding language specifying that this exclusion does not apply during a reasonable transition period (e.g., 90 days after Meridian's delivery of the non-infringing replacement).

(d) OWS-Specification Claims. Meridian's draft excludes claims arising from "OWS's specifications or designs." This exclusion is standard in concept: if OWS provides unique specifications to Meridian and instructs Meridian to implement a particular design or feature that happens to infringe a third party's IP rights, Meridian should not bear the full burden of that infringement. However, the exclusion as drafted is overbroad. It should be narrowed to cover only claims arising solely from OWS's unique specifications — not from standard design flows or methodologies that happen to be applied to OWS's chip designs. The vast majority of OWS's use of Meridian tools involves standard EDA workflows (synthesis, place-and-route, simulation, verification), and the mere fact that OWS's proprietary chip designs are processed through these tools should not trigger this exclusion.

C. IP Indemnification Subject to General Liability Cap

This is the single most critical issue in the IP indemnification negotiation, and it warrants detailed treatment.

Meridian's Proposed Structure. Under Section 10.2 of Meridian's draft Renewal ELA, the IP indemnification obligation set forth in Section 9.1 is expressly subject to the general aggregate limitation of liability set forth in Section 10.1. Section 10.1 provides that neither party's aggregate liability under the agreement, whether arising in contract, tort, strict liability, or otherwise, shall exceed an amount equal to the annual fees paid or payable by OWS in the twelve (12) months immediately preceding the event giving rise to the claim (i.e., 1× annual fees). At Meridian's proposed pricing of $14.3 million per year, this would cap Meridian's total liability — for all claims of any kind, including IP indemnification — at $14.3 million in the aggregate.

The Practical Implications. The implications of this cap structure are significant. Because the IP indemnification obligation shares the same cap pool as all other liabilities, a single IP infringement claim could, in theory, exhaust the entire liability cap, leaving OWS with no remaining recovery for other breaches (e.g., service-level failures, data loss, or breach of confidentiality). Conversely, prior claims for other breaches could deplete the cap, reducing the amount available to satisfy an IP indemnity claim. The aggregate nature of the cap means that these risks are not merely theoretical — they compound over the five-year term of the Renewal ELA.

Moreover, the absolute dollar amount of the cap — $14.3 million at Meridian's quoted pricing, or potentially as low as $11.8 million if OWS achieves its target pricing — is modest in the context of the potential exposure from a serious IP infringement claim. Patent infringement damages in the semiconductor and EDA technology space can be substantial: reasonable royalty awards alone can reach tens or hundreds of millions of dollars, and injunctive relief (or the threat of injunctive relief) can compel settlements in excess of any fee-based cap. If OWS were forced to cease using one or more Meridian tool modules due to an unresolved infringement injunction, the resulting disruption to OWS's tape-out schedule, customer commitments, and revenue pipeline would dwarf the $14.3 million cap.

D. OWS's Concerns with Meridian's Position

The specific concerns motivating OWS's position on this issue are as follows:

Prevalence of IP Litigation in the EDA/Semiconductor Space. IP infringement claims in the semiconductor and EDA software industry are neither rare nor hypothetical. Patent assertion entities (commonly referred to as "patent trolls") actively target semiconductor design tool users, asserting patents covering a wide range of design methodologies, simulation algorithms, and layout optimization techniques. In addition, cross-licensing disputes among the major EDA vendors (including Meridian and its primary competitors) have historically resulted in claims that implicate downstream licensees. OWS, as a licensee whose entire chip design workflow depends on Meridian tools, faces real exposure in this environment.

Critical Business Dependency. OWS's 280-seat deployment of Meridian tools across approximately 185 design engineers means that essentially all of OWS's design engineering workforce — and therefore the entirety of OWS's IC product development capability — depends on uninterrupted access to Meridian's platform. The switching costs associated with migrating to an alternative EDA platform are enormous: they include not only the licensing costs of the replacement tools but also the costs of retraining engineers, re-developing design flows and automation scripts, re-qualifying design libraries, and the months or years of productivity loss during the transition. OWS's management team estimates that a forced platform switch would take 12–18 months and cost approximately $25–$35 million in direct and indirect costs, plus an estimated $40–$60 million in lost or delayed revenue from delayed tape-outs. These figures dramatically exceed any fee-based liability cap.

Moral Hazard / Incentive Alignment. Capping IP indemnity at 1× annual fees fundamentally shifts infringement risk from the party that creates and distributes the software (Meridian) to the party that merely uses it (OWS). This misalignment of risk is both commercially unfair and economically inefficient. Meridian is the party that designs, develops, and distributes the licensed software; Meridian has the ability to conduct freedom-to-operate ("FTO") analysis on its own proprietary codebase; Meridian can obtain third-party licenses, redesign infringing features, or take other steps to mitigate infringement risk. OWS, by contrast, has no visibility into Meridian's source code and no practical ability to assess whether its use of Meridian's tools infringes any third-party IP rights. A capped indemnity reduces Meridian's economic incentive to invest in robust FTO clearance and proactive design-around efforts, because its maximum financial exposure is bounded regardless of the severity or merit of an infringement claim.

Disproportionality. Even setting aside the switching-cost analysis, the cap is disproportionate to the potential harm. A single patent infringement verdict or settlement in the semiconductor technology space can easily exceed $50–$100 million. Limiting OWS's recovery to $14.3 million (or $11.8 million at target pricing) for a claim that could result in tens or hundreds of millions of dollars in damages is commercially unreasonable.

IV. Market Benchmarking — IP Indemnification in Enterprise EDA License Agreements

A. Methodology. To assess whether Meridian's proposed cap structure is consistent with market practice, we reviewed publicly available information and Calderwood & Harkness's internal precedent database of comparable enterprise EDA and software licensing transactions. Our review focused on transactions meeting the following criteria:

• Enterprise license agreements (rather than standard off-the-shelf or per-seat subscription agreements) involving EDA software or comparable design-tool platforms;

• Annual contract values in the range of $5 million to $20 million, to ensure comparability with the OWS/Meridian transaction;

• Licensees operating in the semiconductor industry (both fabless design companies and integrated device manufacturers ("IDMs"));

• Agreements executed or renewed within the past four years (2022–2025).

We identified and reviewed provisions from a total of twelve comparable transactions in our precedent database, supplemented by publicly available information from SEC filings, industry surveys, and published commentary from leading technology licensing practitioners. For purposes of this memorandum, we present detailed findings from three representative precedent transactions and aggregate statistics across the broader sample.

Our benchmarking analysis focused on five key categories: (1) scope of the indemnity trigger; (2) exclusions and carve-outs; (3) remedial obligations; (4) treatment of IP indemnity within the liability cap framework; and (5) super-cap or uncapped treatment for IP claims.

B. Scope of Indemnification Trigger — Market Standard

Across the twelve comparable transactions reviewed, virtually all enterprise EDA licenses include a licensor-side IP indemnity for third-party infringement claims arising from the licensee's authorized use of the licensed software. This is a near-universal provision in the EDA industry, reflecting the well-understood principle that the licensor — as the creator and distributor of the software — is best positioned to warrant against infringement and to absorb the risk of third-party claims.

The market-standard scope of covered IP rights typically includes U.S. patents, copyrights, and trade secrets. Some agreements also extend coverage to trademark claims (less common in the EDA context, as trademark infringement is generally less relevant to software licensing) and to intellectual property rights under the laws of foreign jurisdictions (observed in approximately 25–30% of transactions, typically where the licensee has significant non-U.S. operations). As noted in Section III.A above, Meridian's proposed scope — covering U.S. patents, copyrights, trade secrets, and "other intellectual property rights" — is within the market range and is not a significant area of concern.

C. Standard Exclusions — Market Practice

The four exclusions included in Meridian's draft (modifications by the licensee, combination claims, continued use of superseded versions, and licensee-specification claims) are each standard in concept and are found in the vast majority of comparable agreements. However, the specific formulation of these exclusions varies materially across transactions, and the breadth or narrowness of the exclusion language is a frequently negotiated point.

Combination Claims Exclusion. This exclusion was present in all twelve transactions reviewed. However, in approximately two-thirds of those transactions (eight of twelve), the exclusion was narrowed by qualifying language — typically to cover only combinations that were "not reasonably foreseeable," "not contemplated by the licensor's documentation," or "not described in the licensor's published interoperability specifications." The rationale for this narrowing is particularly compelling in the EDA context, where the licensed software is designed to operate in conjunction with third-party PDKs, IP libraries, and other design tools. A broadly worded combination-claims exclusion could effectively eliminate indemnity coverage for the very use cases that the software is designed to support. As discussed in Section III.B above, this issue is especially important for OWS given the Company's reliance on the interoperability between Meridian tools and Brindoval PDKs.

Modifications Exclusion. This exclusion was present in all twelve transactions reviewed and was generally standard in scope. In approximately half of the transactions (six of twelve), the exclusion was narrowed to cover only modifications made by the licensee "without the consent, direction, or involvement of the licensor." This narrowing is consistent with our recommendation for the OWS/Meridian agreement.

Continued Use of Superseded Version Exclusion. This exclusion was present in all twelve transactions and was generally standard, though approximately one-third of the transactions (four of twelve) included a reasonable transition period (ranging from 60 to 180 days) before the exclusion took effect following the licensor's delivery of a non-infringing update.

Licensee-Specification Exclusion. This exclusion was present in eleven of twelve transactions. In seven of those eleven, the exclusion was narrowed to cover claims arising "solely" or "to the extent" from the licensee's unique specifications, ensuring that standard design flows processed through the licensor's tools remained within the scope of indemnity coverage.

Recommendation. Based on this benchmarking analysis, OWS should push to narrow the combination-claims exclusion by adding "not reasonably foreseeable" or "not documented by Meridian as compatible" language. This is especially important given the Brindoval PDK interoperability context described above — OWS uses Meridian tools in conjunction with Brindoval process design kits as a standard part of its design workflow, and the combination-claims exclusion should not effectively eliminate coverage for these standard PDK-tool combinations.

D. Remedial Obligations — Market Comparison

Meridian's proposed three-tier remedial framework upon a determination of infringement — (i) procure the right for OWS to continue using the software; (ii) modify or replace the infringing software with a functionally equivalent non-infringing alternative; (iii) if neither (i) nor (ii) is commercially practicable, terminate the license for the infringing module and refund a pro-rata portion of prepaid and unused fees — is consistent with the standard market approach. All twelve of the comparable transactions reviewed included a substantially similar three-tier remedial structure.

However, the refund remedy (pro-rata unused fees) represents the minimum level of protection in the event of a terminate-and-refund outcome. In four of the twelve transactions reviewed, the remedial framework included a fourth tier: reimbursement of the licensee's reasonable transition costs to an alternative platform in the event the licensor exercises the terminate-and-refund remedy. The rationale is straightforward: if the licensor's inability to cure an infringement forces the licensee to migrate to a competing platform, the licensee will incur substantial transition costs (tool procurement, engineer retraining, workflow re-development, design re-qualification, etc.) that a mere pro-rata refund of unused fees does not begin to cover.

Recommendation. OWS should propose the addition of a transition cost reimbursement remedy as a fourth tier, subject to a reasonable cap (e.g., reimbursement of documented transition costs up to an amount equal to 12 months of fees). This is a meaningful protection that directly addresses OWS's primary business risk — the cost of switching platforms if Meridian cannot cure an infringement — and is supported by market precedent.

E. Cap Treatment — The Central Negotiation Point

This is the most important benchmarking data point for purposes of OWS's negotiation strategy.

1. Market Overview. Among the twelve comparable enterprise software and EDA license agreements reviewed, the treatment of IP indemnification within the liability cap framework was as follows:

• Approximately 60–65% of agreements (seven or eight of twelve) carved IP indemnification out from the general liability cap entirely. In these agreements, the licensor's IP indemnification obligation was either fully uncapped or subject to a separate, substantially higher "super-cap" that was not shared with other liability categories. This was the most common structure observed and reflects the prevailing market norm for enterprise EDA licenses of this scale.

• Approximately 20–25% of agreements (three of twelve) imposed a "super-cap" on IP indemnification — that is, a cap that was separate from and materially higher than the general liability cap. The super-cap amounts observed in these transactions ranged from 2× to 3× annual fees, though one agreement set the IP indemnity super-cap at an amount equal to the total contract value (i.e., 5× annual fees for a five-year agreement).

• Only approximately 10–15% of agreements (one or two of twelve) subjected IP indemnification to the same general liability cap as all other liabilities. In each of these cases, the licensee was a smaller organization with limited negotiating leverage, and the agreements were generally viewed as suboptimal from the licensee's perspective. Notably, none of these agreements involved a transaction of the scale or strategic significance of the OWS/Meridian Renewal ELA.

The clear weight of market practice — across approximately 85–90% of comparable transactions — favors either uncapped treatment or a meaningful super-cap for IP indemnification obligations. Meridian's proposed structure (IP indemnity subject to the same 1× annual fees general cap) is an outlier that falls in the bottom decile of observed market practice.

2. Rationale for Uncapped or Super-Cap Treatment. The market consensus favoring uncapped or super-cap treatment for licensor IP indemnification obligations is grounded in several well-recognized principles:

Risk Allocation. The licensor is the party that created the software and is best positioned to assess and mitigate infringement risk. The licensor has full visibility into its own source code, development history, and the prior art landscape relevant to its technology. The licensee, by contrast, has no practical ability to conduct FTO analysis on the licensor's proprietary codebase and is entirely dependent on the licensor's representations and indemnity for protection against third-party claims.

Information Asymmetry. In the EDA context, this information asymmetry is particularly acute. Meridian's software involves millions of lines of proprietary code implementing complex algorithms for chip design, simulation, verification, and layout. OWS receives only the object code (compiled binaries) and has no visibility into the underlying source code. OWS cannot independently determine whether any portion of Meridian's software infringes the patents, copyrights, or trade secrets of any third party. The IP indemnity is the contractual mechanism through which this information asymmetry is addressed — and capping the indemnity at an artificially low level undermines its protective function.

Moral Hazard. As noted in Section III.D above, capping IP indemnity at 1× annual fees creates a moral hazard: the licensor has a reduced economic incentive to invest in FTO clearance and design-around efforts if its maximum financial exposure is bounded at a level that may be modest relative to the potential costs of infringement. Uncapping or substantially increasing the cap for IP indemnity preserves the licensor's incentive to take proactive steps to avoid infringement.

Financial Capacity. Large EDA vendors such as Meridian — with FY 2024 revenue of approximately $3.1 billion, a market capitalization in the tens of billions of dollars, and robust cash reserves and insurance programs — have the financial capacity to bear uncapped IP indemnity obligations for individual licensees. The risk profile of a single-licensee IP indemnity is manageable for a company of Meridian's scale, particularly given that the indemnity is triggered only by claims arising from the licensee's authorized use of Meridian's own products. Meridian can further manage this risk through its own FTO programs, patent portfolio cross-licensing arrangements, and litigation insurance.

3. Precedent Transactions. We highlight below three representative precedent transactions from Calderwood & Harkness's internal database, anonymized in accordance with our confidentiality obligations:

Precedent A (EDA Vendor / Fabless Semiconductor Company, Approximately $12M/yr TCV). This agreement, executed in 2023, involved a major EDA vendor licensing its full suite of design tools to a fabless semiconductor company of comparable size and profile to OWS. The IP indemnification obligation was fully uncapped — there was no dollar limit on the licensor's indemnification liability for third-party IP infringement claims. The general aggregate liability cap was set at 2× annual fees. Additional carve-outs from the general cap (treated as uncapped) included willful misconduct and breach of confidentiality obligations. The consequential damages waiver was mutual but excluded IP indemnification claims from its scope, permitting the licensee to recover consequential damages (including lost profits) flowing from a covered infringement claim.

Precedent B (EDA Vendor / Integrated Device Manufacturer, Approximately $18M/yr TCV). This agreement, renewed in 2024, involved a major EDA vendor licensing its tools to a large IDM. The IP indemnification obligation was subject to a super-cap of 3× annual fees — separate from and materially higher than the general aggregate liability cap of 1× annual fees. Data breach liability was subject to a separate super-cap of 2× annual fees. Willful misconduct was uncapped. The consequential damages waiver was mutual and did not include a carve-out for IP indemnification (a point that the licensee's counsel subsequently identified as a negotiation gap that should be addressed in the next renewal cycle).

Precedent C (EDA Vendor / Fabless Semiconductor Company, Approximately $7M/yr TCV). This agreement, executed in 2024, involved a mid-tier EDA vendor licensing a more limited suite of tools to a smaller fabless semiconductor company. Despite the smaller transaction size, the IP indemnification obligation was fully uncapped. The general aggregate liability cap was set at 12 months of fees (1× annual fees). Willful misconduct was uncapped. The consequential damages waiver included a carve-out for IP indemnification claims.

All three precedent transactions support OWS's position that IP indemnification should either be fully uncapped or subject to a super-cap that is materially higher than the general liability cap. Notably, even Precedent C — which involved a smaller transaction with a mid-tier vendor (presumably with more limited negotiating capacity than Meridian) — included fully uncapped IP indemnification.

V. Interplay Between IP Indemnity, Data Breach, and Willful Misconduct Carve-Outs

A. OWS's Proposed Liability Cap Structure

Building on the benchmarking analysis set forth in Section IV, we recommend that OWS propose the following liability cap structure in its first redline of the Renewal ELA:

General Aggregate Liability Cap: 2× the annual fees actually paid (or payable) by OWS in the twelve (12) months immediately preceding the event giving rise to the claim. At OWS's target pricing of $11.8 million per year, this would equate to a general cap of $23.6 million. At Meridian's quoted pricing of $14.3 million per year, this would equate to a general cap of $28.6 million. The 2× multiplier (rather than Meridian's proposed 1×) is consistent with the majority of comparable transactions reviewed and reflects the appropriate baseline level of protection for a licensee of OWS's scale and dependency.

Uncapped Categories (Carved Out from the General Aggregate Cap):

(i) Meridian's IP Indemnification Obligations. Meridian's obligation to defend, indemnify, and hold harmless OWS against third-party IP infringement claims under Section 9 of the Renewal ELA shall not be subject to the general aggregate liability cap and shall be fully uncapped.

(ii) Data Breach / Breach of Data Security Obligations. Either party's liability arising from a breach of data security and confidentiality obligations under the applicable sections of the Renewal ELA and the Data Security and Cloud Services Rider shall not be subject to the general aggregate liability cap and shall be fully uncapped.

(iii) Willful Misconduct / Gross Negligence / Fraud. Either party's liability arising from willful misconduct, gross negligence, or fraud shall not be subject to the general aggregate liability cap and shall be fully uncapped.

Rationale for Grouping. The rationale for grouping these three categories of liability as uncapped carve-outs from the general cap is consistent and well-established: each involves a category of liability where (a) the breaching party is uniquely positioned to prevent the harm (Meridian creates the software and can prevent infringement; the hosting party controls data security; the breaching party controls its own conduct); (b) the potential damages to the non-breaching party are disproportionate to the contract value and cannot be adequately compensated by a fee-based cap; and (c) imposing a low cap would create a moral hazard by reducing the breaching party's incentive to prevent the harm.

B. Meridian's Likely Objections and Counter-Arguments

Based on our experience negotiating with Bexley Weir & Daly LLP and our familiarity with Meridian's standard contracting positions, we anticipate the following objections from Meridian and offer corresponding counter-arguments:

Objection 1: Uncapped IP Indemnity Creates Open-Ended Financial Exposure. Meridian will likely argue that an uncapped IP indemnification obligation exposes the licensor to theoretically unlimited liability, which is commercially unreasonable and inconsistent with the risk profile of a software license. Meridian may contend that no vendor should be asked to assume unlimited financial exposure in connection with any single customer license, regardless of the nature of the claim.

Counter-Argument: Meridian's exposure under the IP indemnity is inherently self-limiting in several important respects. First, the indemnity is triggered only by claims arising from OWS's authorized use of the licensed software — Meridian controls the design and implementation of its own products and can take steps to avoid infringement (through FTO analysis, licensing, or design-around). Second, the standard exclusions (modifications by OWS, unforeseeable combinations, OWS-specification claims) further limit the scope of covered claims. Third, Meridian has the right to control the defense of any covered claim, giving it the ability to manage litigation strategy and settlement decisions. Fourth, Meridian — as a $3.1 billion publicly traded company — has the financial capacity, insurance programs, and patent cross-licensing arrangements necessary to manage this risk. The practical likelihood of a single-licensee IP indemnity claim resulting in exposure that would be material to Meridian's balance sheet is extremely low.

Objection 2: Super-Cap as Compromise. If Meridian rejects uncapped treatment, it may propose a super-cap compromise — for example, a cap on IP indemnity at 3× or 5× annual fees, separate from the general liability cap. Meridian may argue that a super-cap appropriately balances the licensor's need for certainty with the licensee's need for meaningful protection.

Counter-Argument: A super-cap is a better outcome than the 1× general cap currently proposed and would represent a material improvement in OWS's position. However, OWS should open with a demand for fully uncapped IP indemnity and concede to a super-cap only as a fallback position. The reason is straightforward: the potential damages from a serious IP infringement claim can be unpredictable and may exceed even a generous super-cap. A super-cap of 3× annual fees ($42.9 million at Meridian's pricing) or 5× annual fees ($71.5 million at Meridian's pricing) provides substantially more headroom than the current 1× proposal, but it may still fall short of the actual exposure in a worst-case scenario involving a broad patent assertion and/or injunctive relief. If a super-cap is ultimately accepted, OWS should push for the highest multiplier achievable — ideally 5× annual fees (approximately equal to total contract value), and no less than 3× annual fees (as identified in Section VII below as OWS's floor).

C. Data Breach Carve-Out

The data breach carve-out is particularly important in the context of the Renewal ELA for two reasons:

Introduction of Meridian CloudVerify™. The Renewal ELA introduces Meridian CloudVerify™, a cloud-hosted verification compute offering through which OWS's proprietary chip design data — including RTL code, netlists, layout data, simulation parameters, and verification test vectors — would be transmitted to and processed within Meridian's cloud infrastructure. This represents a significant expansion of the data flows between the parties compared to the Original ELA, under which all Meridian tools were deployed on-premises within OWS's own computing environment. The introduction of a cloud component materially increases the data security risk profile of the relationship.

Sensitivity of OWS's Design Data. OWS's chip design data constitutes some of the Company's most valuable trade secret information. OWS's optical transceiver IC designs and silicon photonics chiplet architectures embody years of R&D investment and represent core competitive advantages in the hyperscale data center interconnect market. A data breach involving the unauthorized disclosure or exfiltration of this data could cause catastrophic competitive harm — including loss of trade secret protection, loss of first-mover advantage in product roadmap execution, and potential misappropriation by competitors. The financial impact of such a breach could easily exceed $100 million and would far surpass any contractual liability cap pegged to annual license fees.

SOC 2 Compliance. OWS is requiring Meridian to maintain SOC 2 Type II compliance for the CloudVerify™ infrastructure, and Meridian's most recent SOC 2 Type II report is dated June 30, 2025. While SOC 2 compliance provides a useful baseline for data security practices, it does not eliminate the risk of a breach. The data breach carve-out ensures that Meridian's financial incentive to maintain robust security practices is not diluted by an artificial liability cap.

Market Practice. Market practice strongly supports uncapping data breach liability for the party hosting or processing the other party's sensitive data. Among the twelve comparable transactions reviewed, eight of twelve included an uncapped carve-out or a dedicated super-cap for data breach liability. This is consistent with broader trends in technology contracting, where data breach carve-outs have become increasingly common and are widely recognized as a fundamental element of a well-structured liability framework.

D. Willful Misconduct / Gross Negligence / Fraud

The treatment of willful misconduct, gross negligence, and fraud as uncapped carve-outs from the general liability cap is standard market practice and is near-universal in commercial contracts. Among the twelve comparable transactions reviewed, all twelve included an uncapped carve-out for willful misconduct and/or fraud. This carve-out reflects the foundational principle that a party should not be able to cap its liability for intentional or recklessly harmful conduct — to do so would effectively provide a license to act in bad faith, which is contrary to public policy and the implied covenant of good faith and fair dealing.

We anticipate that Meridian will not strongly resist this carve-out, given its near-universal acceptance in commercial practice. If Meridian does object, the objection is unlikely to be sustained in the face of the overwhelming market precedent supporting this position.

VI. Specific Drafting Recommendations

Based on the foregoing analysis, we recommend the following specific drafting changes for inclusion in OWS's first redline of the Renewal ELA (target delivery: November 15, 2025).

A. IP Indemnification Provision — Proposed OWS Redline

We recommend maintaining Meridian's general indemnification scope (coverage for third-party claims alleging infringement of U.S. Intellectual property rights arising from OWS's authorized use of the licensed software) but incorporating the following modifications:

1. Narrow the Combination-Claims Exclusion. The combination-claims exclusion in Section 9.2(b) should be revised to exclude from indemnification only claims arising from the use of the licensed software in combination with third-party products or technologies that are "not reasonably foreseeable" or "not described in Meridian's documentation, published interoperability specifications, or published compatibility guides." This narrowing ensures that standard combinations — including, critically, the combination of Meridian tools with Brindoval and other foundry PDKs — remain within the scope of the indemnity. The revised language would also expressly state that combinations with third-party PDKs and IP libraries that are identified in Meridian's documentation as compatible shall not be excluded from indemnity coverage.

2. Narrow the Modification Exclusion. The modification exclusion in Section 9.2(a) should be revised to cover only modifications made by OWS "without the written consent, direction, or involvement of Meridian." This narrowing ensures that customizations made by OWS with Meridian's guidance, assistance, or professional services support are not excluded from indemnity coverage. This is particularly important given that OWS's design engineers frequently develop automation scripts and customizations within the Meridian tool environment, sometimes in collaboration with Meridian's customer engineering team.

3. Add Transition Cost Reimbursement Remedy. A fourth remedial tier should be added to the infringement remedies in Section 9.3, providing that if Meridian exercises the terminate-and-refund option (because it is unable to procure continued use rights or provide a non-infringing replacement), Meridian shall also reimburse OWS for its reasonable, documented transition costs incurred in migrating to an alternative EDA platform, subject to a cap of twelve (12) months of fees. In addition, a reasonable transition period of not less than ninety (90) days should be specified before OWS is required to cease use of the infringing module following Meridian's delivery of a non-infringing replacement under the continued-use-of-superseded-version exclusion.

4. Carve Out IP Indemnification from the General Liability Cap. Section 10 (Limitation of Liability) should expressly state that Meridian's IP indemnification obligations under Section 9 are not subject to, and shall not be limited by, the general aggregate liability cap set forth in Section 10.1. This is the single most important drafting change in this negotiation and is the subject of the detailed analysis and market benchmarking set forth in Sections III through V of this memorandum.

B. Limitation of Liability — Proposed OWS Redline

We recommend that the limitation-of-liability provision in Section 10 be revised as follows:

General Aggregate Liability Cap (Section 10.1). Neither party's aggregate liability under this Agreement, whether arising in contract, tort (including negligence), strict liability, or otherwise, shall exceed an amount equal to two times (2×) the annual fees actually paid or payable by OWS to Meridian in the twelve (12) months immediately preceding the event giving rise to the claim (the "General Cap").

Carve-Outs from the General Cap (Section 10.2). The General Cap shall not apply to, and shall not limit, either party's liability with respect to the following:

(i) Meridian's IP indemnification obligations under Section 9 of this Agreement;

(ii) Either party's liability arising from a breach of its data security and confidentiality obligations under Section [] and the Data Security and Cloud Services Rider attached hereto as Exhibit [];

(iii) Either party's liability arising from willful misconduct, gross negligence, or fraud;

(iv) Either party's liability arising from a misappropriation of the other party's intellectual property rights (including, without limitation, a misappropriation of trade secrets).

Consequential Damages Waiver (Section 10.3). The standard mutual exclusion of indirect, incidental, special, punitive, and consequential damages (including lost profits) should be retained as a general matter but should expressly carve out the following from the scope of the waiver:

(a) Meridian's IP indemnification obligations under Section 9, such that OWS may recover consequential damages (including lost profits, lost revenue, and increased costs of procurement) flowing from a covered third-party IP infringement claim; and

(b) Either party's liability arising from a breach of data security and confidentiality obligations, such that the non-breaching party may recover consequential damages flowing from a data breach or unauthorized disclosure of confidential information.

The carve-out of IP indemnification from the consequential damages waiver is critical. Without this carve-out, OWS's recovery in connection with a covered infringement claim would be limited to direct damages (e.g., the reasonable royalty or damages awarded by a court), but would not include the potentially much larger consequential losses flowing from the infringement (e.g., lost profits from delayed tape-outs, costs of transitioning to an alternative platform, lost customer contracts). Given that the consequential losses from a serious infringement claim are likely to dwarf the direct damages, the carve-out is essential to the effectiveness of the indemnity.

C. Relationship to Source Code Escrow

We note for completeness that the proposed Technology Escrow Agreement with Iron Vault Escrow Services, Inc. (1700 Lincoln Street, Suite 2100, Denver, Colorado 80203) provides an additional protective mechanism for OWS in the event of certain triggering events — specifically, if Meridian becomes insolvent, materially breaches the Renewal ELA and fails to cure, or discontinues one or more of the licensed product lines. In such events, OWS would gain access to the escrowed source code for the licensed Meridian software modules, enabling OWS to maintain and support the tools internally (or through a third-party contractor) and preserve continuity of its design engineering operations.

While the escrow arrangement provides important continuity protection, it does not substitute for robust IP indemnification. Even if OWS obtains access to source code through an escrow release, OWS would still face infringement exposure if the underlying code infringes third-party IP rights. The escrow agreement gives OWS the practical ability to continue using the software, but it does not insulate OWS from third-party infringement claims — only the IP indemnity provides that protection.

Accordingly, we recommend ensuring that the IP indemnification obligation survives termination or expiration of the Renewal ELA for any claims arising from OWS's use of the licensed software during the license term (including any post-termination wind-down period). The survival provision should be clearly drafted and should not be subject to a time limitation shorter than the applicable statute of limitations for the underlying IP claims (typically six years for patent infringement under 35 U.S.C. § 286).

VII. Fallback Positions

Recognizing that negotiations are iterative and that Meridian may not accept OWS's opening position in full, we have developed the following graduated negotiation framework. Each fallback position represents the next-best commercially acceptable outcome if OWS is unable to secure its preferred position.

A. Preferred Position (Opening)

• IP Indemnification: Fully uncapped (no dollar limit on Meridian's IP indemnification obligations).

• General Aggregate Liability Cap: 2× annual fees.

• Data Breach: Fully uncapped (no dollar limit on either party's data breach liability).

• Willful Misconduct / Gross Negligence / Fraud: Fully uncapped.

• Consequential Damages Waiver: Mutual, with carve-outs for IP indemnification and data breach.

This is the strongest commercially justifiable position and is consistent with market norms as demonstrated by the benchmarking analysis in Section IV. OWS should open with this position and advocate for it vigorously, using the market data and risk-allocation arguments set forth in this memorandum.

B. First Fallback

• IP Indemnification: Super-cap at 5× annual fees (i.e., approximately $71.5 million at Meridian's quoted pricing, or approximately $59.0 million at OWS's target pricing — in either case, approximately equal to total contract value).

• General Aggregate Liability Cap: 2× annual fees.

• Data Breach: Fully uncapped.

• Willful Misconduct / Gross Negligence / Fraud: Fully uncapped.

• Consequential Damages Waiver: Mutual, with carve-outs for IP indemnification and data breach.

This fallback gives Meridian the certainty of a defined dollar cap on its IP indemnity exposure while providing OWS with a level of protection that is approximately five times higher than the general cap and is roughly equivalent to the total value of the five-year agreement. A 5× annual fees super-cap is within the range of market practice (observed in some comparable transactions) and is supported by the Precedent B structure described in Section IV.E.3 (which included a 3× super-cap for a larger transaction).

C. Second Fallback (Floor)

• IP Indemnification: Super-cap at 3× annual fees (i.e., approximately $42.9 million at Meridian's quoted pricing, or approximately $35.4 million at OWS's target pricing).

• General Aggregate Liability Cap: 2× annual fees.

• Data Breach: Super-cap at 3× annual fees.

• Willful Misconduct / Gross Negligence / Fraud: Fully uncapped.

• Consequential Damages Waiver: Mutual, with carve-outs for IP indemnification and data breach.

This represents the floor of OWS's acceptable negotiation range. A 3× annual fees super-cap for IP indemnification provi

MEMORANDUM
ATTORNEY-CLIENT PRIVILEGED AND CONFIDENTIAL ATTORNEY WORK PRODUCT
FROM: Monica Reyes, Associate, Calderwood & Harkness LLP
TO: Aaron Liu, Lead Associate, Calderwood & Harkness LLP
DATE: November 10, 2025
RE: IP Indemnification Analysis — Meridian Design Systems, Inc. Renewal ELA (MDS-ELA-2026-01192); Optiwave Semiconductor Corp.
MATTER NO.: 1014-00006
OFFICE: One Market Plaza, Spear Tower, 42nd Floor, San Francisco, CA 94105
Right-click to update Table of Contents
I. Executive Summary
This memorandum analyzes the intellectual property indemnification provisions set forth in the proposed Amended and Restated Enterprise License Agreement (Agreement No. MDS-ELA-2026-01192) (the "Renewal ELA") between Optiwave Semiconductor Corp. ("OWS" or the "Company") and Meridian Design Systems, Inc. ("Meridian"), and benchmarks those provisions against market-standard terms observed in comparable enterprise electronic design automation ("EDA") software license agreements. The purpose of this analysis is to inform OWS's negotiating strategy with respect to IP indemnification and related limitation-of-liability provisions in advance of OWS's delivery of its first substantive redline to Meridian's outside counsel.
The core tension in the current negotiation is as follows: OWS seeks uncapped IP indemnification from Meridian for third-party intellectual property infringement claims arising from OWS's authorized use of the licensed EDA tools. Meridian's current draft, by contrast, proposes an aggregate liability cap of 1× annual fees ($14.3 million at Meridian's quoted annual pricing of $14.3 million per year under a $71.5 million, five-year total contract value ("TCV")). Under Meridian's formulation, the IP indemnification obligation would be subject to the same cap that governs all other liabilities — meaning that OWS's total recoverable amount for all claims, whether arising from IP infringement, breach of contract, negligence, or otherwise, would be limited to $14.3 million in the aggregate.
Based on the analysis set forth below, our recommendation is as follows: OWS should maintain its position of a 2× annual fees general aggregate liability cap, with uncapped liability for IP indemnification, data breach, and willful misconduct. This position is well-supported by market practice — our review of comparable enterprise EDA transactions indicates that approximately 60–65% of agreements carve IP indemnification out from the general liability cap entirely — and is commercially justified given OWS's critical reliance on Meridian tools across its entire 280-seat design engineering organization. The potential consequences of a covered infringement claim (including forced cessation of tool use, delayed tape-outs, and downstream revenue losses) would far exceed any contractual cap pegged to annual fees, and the risk of infringement in the EDA space — driven by patent assertion entities, competitor patent portfolios, and cross-licensing disputes — is material and well-documented.
This memorandum is organized as follows: Section II provides background on the parties, the transaction, and the scope of this analysis. Section III analyzes Meridian's proposed IP indemnification provisions in detail. Section IV presents our market benchmarking findings. Section V addresses the interplay between IP indemnification, data breach, and willful misconduct carve-outs from the liability cap. Section VI sets forth specific drafting recommendations for OWS's first redline. Section VII outlines OWS's preferred, fallback, and walk-away negotiation positions. Section VIII summarizes conclusions and identifies next steps.
II. Background
A. The Parties and the Transaction
Optiwave Semiconductor Corp. OWS is a Delaware corporation headquartered at 4850 Great America Parkway, Suite 300, Santa Clara, California 95054. The Company is a fabless semiconductor design company specializing in the design and sale of high-speed optical transceiver integrated circuits ("ICs") and silicon photonics chiplets for data-center interconnect applications. OWS was founded in 2017 and has grown rapidly in the hyperscale data center and cloud infrastructure market. The Company is a portfolio company of Ridgeline Capital Partners, LP ("Ridgeline"), which acquired a 78% equity stake in OWS in August 2022 at an enterprise value of approximately $412 million. OWS currently employs approximately 340 people, of whom approximately 185 are design engineers who use EDA tools on a daily basis.
OWS's financial profile is relevant to the negotiation context. For the fiscal year ended December 31, 2024 ("FY 2024"), OWS reported revenue of $287.4 million and EBITDA of $51.7 million, reflecting healthy margins in its target market segments. OWS's total annual EDA software spend across all vendors was approximately $18.6 million for FY 2024, of which the Meridian portion under the existing Enterprise License Agreement accounted for approximately $9.2 million per year — representing nearly half of OWS's total EDA expenditure. The significance of Meridian's tools to OWS's operations cannot be overstated: the Company's core chip design workflows for optical transceiver ICs and silicon photonics chiplets are built on Meridian's platform, and any interruption in access to these tools would have cascading effects on tape-out schedules, customer commitments, and revenue recognition.
Meridian Design Systems, Inc. Meridian is a Delaware corporation headquartered at 2700 Orchard Parkway, San Jose, California 95134. Meridian is one of the three major EDA software vendors in the global semiconductor industry and provides a comprehensive suite of digital and analog design, verification, simulation, and signoff tools. Meridian is publicly traded on the Nasdaq Stock Market. The company employs approximately 4,800 people globally and reported FY 2024 revenue of approximately $3.1 billion. Meridian's scale and financial capacity are relevant to the IP indemnification discussion, as noted further in Section IV.E below.
Meridian's outside counsel for this transaction is Bexley Weir & Daly LLP, represented by Rachel Endo (Partner) and Kevin Matsuda (Associate), located at 525 University Avenue, Suite 1400, Palo Alto, California 94301. OWS is represented by this firm, Calderwood & Harkness LLP, with Conrad Ashby (Partner) and Douglas Tran (Partner) serving as the lead engagement partners, and Aaron Liu (Lead Associate) and the undersigned (Associate) handling day-to-day drafting and analysis.
B. The Original ELA and Proposed Renewal
The Original ELA. OWS and Meridian are parties to an Enterprise License Agreement designated as Agreement No. MDS-ELA-2023-00487 (the "Original ELA"), which became effective on February 1, 2023 and has a three-year term expiring on January 31, 2026. The Original ELA has a TCV of $27.6 million ($9.2 million per year) and provides OWS with 190 total seats — comprising 150 named-user licenses and 40 floating licenses — across three Meridian product modules: Meridian Marlowe Asset Management™ (physical design and layout), signalForge™ (signal integrity analysis), and VerifyPro™ (functional verification).
The Proposed Renewal ELA. The proposed Renewal ELA (Agreement No. MDS-ELA-2026-01192) would replace and supersede the Original ELA upon its expiration. The Renewal ELA contemplates a significantly expanded commercial relationship between the parties. The key commercial terms of Meridian's initial proposal, received by OWS on October 15, 2025, are as follows:
• Term: Five (5) years, commencing February 1, 2026 and expiring January 31, 2031.
• Product Scope: Expanded to include five Meridian product modules — the three existing modules (Meridian Marlowe Asset Management™, signalForge™, and VerifyPro™) plus two new modules: AnalogEdge™ (mixed-signal analog simulation) and PhotonX™ (silicon photonics design and modeling). The addition of AnalogEdge™ and PhotonX™ reflects OWS's growing need for integrated analog simulation capabilities and dedicated photonics design tools as the Company expands its silicon photonics chiplet product lines.
• Seat Count: 280 total seats, comprising 220 named-user licenses and 60 floating licenses. This represents a 47.4% increase over the Original ELA's 190-seat allocation (an addition of 90 seats) and reflects OWS's headcount growth in its design engineering organization and planned hiring through the Renewal ELA term.
• Pricing — Meridian's Initial Quote: TCV of $71.5 million ($14.3 million per year), representing a 55.4% increase over the current $9.2 million per year annual spend under the Original ELA. On a per-seat basis, Meridian's initial quote implies an annual cost of approximately $51,071 per seat.
• Pricing — OWS Target: OWS's commercial team, in consultation with Ridgeline's operating partners, has established a target TCV of $59.0 million ($11.8 million per year), which reflects a volume discount of approximately 17.5% off Meridian's initial quoted pricing. At 280 seats, this would yield a target per-seat annual cost of approximately $42,143. Pricing negotiations are being handled separately by OWS's procurement team (Sameer Iyer, VP of Finance and Operations), but the pricing outcome will directly affect the dollar value of any fee-linked liability caps.
The Renewal ELA also contemplates the introduction of Meridian CloudVerify™, a cloud-hosted verification compute offering that would enable OWS to offload certain computationally intensive verification workloads to Meridian's cloud infrastructure. The inclusion of CloudVerify™ introduces additional data security considerations, as OWS's proprietary chip design data — which constitutes highly sensitive trade secret information — would be transmitted to and processed within Meridian's cloud environment. The data security implications are addressed in the Data Security and Cloud Services Rider, which is being negotiated as a separate exhibit to the Renewal ELA and which is the subject of a companion memorandum from this team.
C. Scope of This Memorandum
This memorandum addresses the following specific topics:
1. Analysis of IP Indemnification Provisions: A detailed examination of the IP indemnification provisions as set forth in Meridian's proposed Renewal ELA, including the scope of the indemnity trigger, applicable exclusions and carve-outs, and remedial obligations.
2. Market Benchmarking: A comparison of Meridian's proposed IP indemnification terms against market-standard provisions observed in comparable enterprise EDA and software license agreements, drawing on publicly available information and Calderwood & Harkness's internal precedent database.
3. Interplay with Limitation of Liability: An analysis of the critical interplay between the IP indemnification obligation and the general limitation-of-liability provisions, including the treatment of IP indemnity, data breach liability, and willful misconduct within the liability cap framework.
4. Negotiation Positions and Fallback Options: Recommended negotiation positions for OWS, including an opening position, graduated fallback positions, and an identified walk-away threshold, with supporting rationale for each.
This memorandum does not address the commercial pricing negotiation, the Data Security and Cloud Services Rider (which will be addressed in a separate memorandum), the source code escrow arrangement (except insofar as it intersects with the IP indemnification analysis), or the general terms and conditions of the Renewal ELA beyond the specific provisions identified above.
III. Analysis of Meridian's Proposed IP Indemnification Provisions
A. Indemnification Scope — Meridian's Draft
Meridian's proposed IP indemnification provision, set forth in Section 9.1 of the Renewal ELA draft circulated on October 15, 2025, provides that Meridian agrees to defend, indemnify, and hold harmless OWS (including OWS's officers, directors, employees, agents, and affiliates) against any and all third-party claims alleging that OWS's authorized use of the licensed software, as permitted under the license grant set forth in Section 2 of the Renewal ELA, infringes any United States patent, copyright, trade secret, or other intellectual property right of such third party.
Several observations regarding the scope of this provision are warranted:
"Authorized Use" Limitation. The trigger for the indemnity obligation is expressly limited to OWS's "authorized use" of the licensed software — meaning use within the scope of the license grant. Under the Renewal ELA, the license grant permits OWS to install and use the five licensed product modules (Meridian Marlowe Asset Management™, SignalForge™, VerifyPro™, AnalogEdge™, and PhotonX™) on up to 280 seats (220 named-user and 60 floating), solely for the purpose of designing, simulating, verifying, and laying out semiconductor integrated circuits in connection with OWS's internal business operations. Any use of the software outside the scope of this grant — for example, exceeding the seat count, using the software for unauthorized commercial purposes, or sublicensing the software to third parties — would fall outside the indemnity trigger. This limitation is standard and generally unobjectionable.
Geographic Limitation. The indemnification obligation is limited to claims alleging infringement of United States intellectual property rights. While this is within the range of market practice for EDA licenses (given that most EDA software vendors are U.S.-domiciled and the predominant risk of IP litigation in the EDA space arises in U.S. forums), it is worth noting that some agreements extend coverage to claims involving foreign IP rights, particularly in jurisdictions where the licensee has significant operations. OWS currently conducts all of its design engineering in the United States (primarily at its Santa Clara headquarters and a satellite design center in Austin, Texas), so the geographic limitation is not a significant concern at this time. However, if OWS's design operations expand internationally during the five-year Renewal ELA term, this limitation could become more material. We flag this as a monitoring point but do not recommend expending negotiation capital on this issue at present.
Covered IP Rights. The scope of covered intellectual property rights — U.S. patents, copyrights, trade secrets, and "other intellectual property rights" — is reasonably comprehensive. The inclusion of trade secret claims is particularly important in the EDA context, given the frequency with which former employees of one EDA vendor move to a competitor and the resulting risk of trade secret misappropriation allegations that could implicate downstream licensees. The catch-all reference to "other intellectual property rights" provides additional breadth, though its precise contours are less defined. On balance, the scope of covered IP rights in Meridian's draft is within market range and does not require significant modification.
B. IP Indemnification Exclusions — Meridian's Draft
Meridian's draft sets forth four exclusions from the IP indemnification obligation in Section 9.2. Each is analyzed below:
(a) Modifications by OWS. Meridian's draft excludes from indemnification any claim arising from modifications made by OWS to the licensed software. This exclusion is standard in EDA licenses, as the licensor cannot reasonably be expected to warrant against infringement arising from the licensee's own modifications to the licensor's code. However, as discussed in Section VI below, the exclusion should be narrowly drawn to cover only modifications made by OWS without Meridian's consent, direction, or involvement. OWS occasionally makes customizations to Meridian tools through scripting and automation frameworks (e.g., Tcl/Perl scripts within the Marlowe Asset Management™ environment), and in some cases these customizations are made with the assistance or guidance of Meridian's professional services team. Modifications made at Meridian's direction or with Meridian's participation should not trigger this exclusion.
(b) Combination Claims. Meridian's draft excludes claims arising from the use of the licensed software "in combination with" non-Meridian products "not reasonably contemplated by" Meridian's documentation. This is the most significant exclusion from OWS's perspective, and it warrants careful attention.
The combination-claims exclusion is nearly universal in enterprise software licenses, and its inclusion in principle is unobjectionable. However, the breadth of the exclusion as drafted is a concern. In OWS's design engineering workflow, the Meridian tools are used in close integration with process design kits ("PDKs") provided by OWS's foundry partners — most notably Brindoval Foundry Services, Inc. ("Brindoval"), which provides the PDKs for OWS's primary 5nm and 3nm optical transceiver IC processes. The interoperability between Meridian tools and Brindoval PDKs is not incidental; it is a foundational aspect of OWS's design flow and is broadly contemplated by the industry. If the combination-claims exclusion were interpreted broadly, it could potentially exclude coverage for infringement claims arising from the standard combination of Meridian tools with Brindoval PDKs — effectively eviscerating the indemnity in the precise context where it is most needed.
We recommend that OWS push to narrow this exclusion by inserting qualifying language to the effect that the exclusion applies only to combinations that are "not reasonably foreseeable" or "not described in Meridian's documentation, interoperability specifications, or published compatibility guides." This approach preserves Meridian's ability to exclude claims arising from truly unforeseeable combinations while ensuring that standard PDK-tool combinations remain within the scope of coverage.
(c) Continued Use of Superseded Version. Meridian's draft excludes claims arising from OWS's continued use of any version of the licensed software after Meridian has provided a non-infringing replacement or update. This exclusion is reasonably standard and is the logical counterpart to Meridian's remedial obligation to modify or replace infringing software (discussed in Section III.D below). However, this exclusion should be subject to a reasonable transition period — OWS should not be expected to instantaneously deploy a replacement version across a 280-seat installation, particularly where the update may require regression testing and validation against OWS's existing design data. We recommend adding language specifying that this exclusion does not apply during a reasonable transition period (e.g., 90 days after Meridian's delivery of the non-infringing replacement).
(d) OWS-Specification Claims. Meridian's draft excludes claims arising from "OWS's specifications or designs." This exclusion is standard in concept: if OWS provides unique specifications to Meridian and instructs Meridian to implement a particular design or feature that happens to infringe a third party's IP rights, Meridian should not bear the full burden of that infringement. However, the exclusion as drafted is overbroad. It should be narrowed to cover only claims arising solely from OWS's unique specifications — not from standard design flows or methodologies that happen to be applied to OWS's chip designs. The vast majority of OWS's use of Meridian tools involves standard EDA workflows (synthesis, place-and-route, simulation, verification), and the mere fact that OWS's proprietary chip designs are processed through these tools should not trigger this exclusion.
C. IP Indemnification Subject to General Liability Cap
This is the single most critical issue in the IP indemnification negotiation, and it warrants detailed treatment.
Meridian's Proposed Structure. Under Section 10.2 of Meridian's draft Renewal ELA, the IP indemnification obligation set forth in Section 9.1 is expressly subject to the general aggregate limitation of liability set forth in Section 10.1. Section 10.1 provides that neither party's aggregate liability under the agreement, whether arising in contract, tort, strict liability, or otherwise, shall exceed an amount equal to the annual fees paid or payable by OWS in the twelve (12) months immediately preceding the event giving rise to the claim (i.e., 1× annual fees). At Meridian's proposed pricing of $14.3 million per year, this would cap Meridian's total liability — for all claims of any kind, including IP indemnification — at $14.3 million in the aggregate.
The Practical Implications. The implications of this cap structure are significant. Because the IP indemnification obligation shares the same cap pool as all other liabilities, a single IP infringement claim could, in theory, exhaust the entire liability cap, leaving OWS with no remaining recovery for other breaches (e.g., service-level failures, data loss, or breach of confidentiality). Conversely, prior claims for other breaches could deplete the cap, reducing the amount available to satisfy an IP indemnity claim. The aggregate nature of the cap means that these risks are not merely theoretical — they compound over the five-year term of the Renewal ELA.
Moreover, the absolute dollar amount of the cap — $14.3 million at Meridian's quoted pricing, or potentially as low as $11.8 million if OWS achieves its target pricing — is modest in the context of the potential exposure from a serious IP infringement claim. Patent infringement damages in the semiconductor and EDA technology space can be substantial: reasonable royalty awards alone can reach tens or hundreds of millions of dollars, and injunctive relief (or the threat of injunctive relief) can compel settlements in excess of any fee-based cap. If OWS were forced to cease using one or more Meridian tool modules due to an unresolved infringement injunction, the resulting disruption to OWS's tape-out schedule, customer commitments, and revenue pipeline would dwarf the $14.3 million cap.
D. OWS's Concerns with Meridian's Position
The specific concerns motivating OWS's position on this issue are as follows:
Prevalence of IP Litigation in the EDA/Semiconductor Space. IP infringement claims in the semiconductor and EDA software industry are neither rare nor hypothetical. Patent assertion entities (commonly referred to as "patent trolls") actively target semiconductor design tool users, asserting patents covering a wide range of design methodologies, simulation algorithms, and layout optimization techniques. In addition, cross-licensing disputes among the major EDA vendors (including Meridian and its primary competitors) have historically resulted in claims that implicate downstream licensees. OWS, as a licensee whose entire chip design workflow depends on Meridian tools, faces real exposure in this environment.
Critical Business Dependency. OWS's 280-seat deployment of Meridian tools across approximately 185 design engineers means that essentially all of OWS's design engineering workforce — and therefore the entirety of OWS's IC product development capability — depends on uninterrupted access to Meridian's platform. The switching costs associated with migrating to an alternative EDA platform are enormous: they include not only the licensing costs of the replacement tools but also the costs of retraining engineers, re-developing design flows and automation scripts, re-qualifying design libraries, and the months or years of productivity loss during the transition. OWS's management team estimates that a forced platform switch would take 12–18 months and cost approximately $25–$35 million in direct and indirect costs, plus an estimated $40–$60 million in lost or delayed revenue from delayed tape-outs. These figures dramatically exceed any fee-based liability cap.
Moral Hazard / Incentive Alignment. Capping IP indemnity at 1× annual fees fundamentally shifts infringement risk from the party that creates and distributes the software (Meridian) to the party that merely uses it (OWS). This misalignment of risk is both commercially unfair and economically inefficient. Meridian is the party that designs, develops, and distributes the licensed software; Meridian has the ability to conduct freedom-to-operate ("FTO") analysis on its own proprietary codebase; Meridian can obtain third-party licenses, redesign infringing features, or take other steps to mitigate infringement risk. OWS, by contrast, has no visibility into Meridian's source code and no practical ability to assess whether its use of Meridian's tools infringes any third-party IP rights. A capped indemnity reduces Meridian's economic incentive to invest in robust FTO clearance and proactive design-around efforts, because its maximum financial exposure is bounded regardless of the severity or merit of an infringement claim.
Disproportionality. Even setting aside the switching-cost analysis, the cap is disproportionate to the potential harm. A single patent infringement verdict or settlement in the semiconductor technology space can easily exceed $50–$100 million. Limiting OWS's recovery to $14.3 million (or $11.8 million at target pricing) for a claim that could result in tens or hundreds of millions of dollars in damages is commercially unreasonable.
IV. Market Benchmarking — IP Indemnification in Enterprise EDA License Agreements
A. Methodology. To assess whether Meridian's proposed cap structure is consistent with market practice, we reviewed publicly available information and Calderwood & Harkness's internal precedent database of comparable enterprise EDA and software licensing transactions. Our review focused on transactions meeting the following criteria:
• Enterprise license agreements (rather than standard off-the-shelf or per-seat subscription agreements) involving EDA software or comparable design-tool platforms;
• Annual contract values in the range of $5 million to $20 million, to ensure comparability with the OWS/Meridian transaction;
• Licensees operating in the semiconductor industry (both fabless design companies and integrated device manufacturers ("IDMs"));
• Agreements executed or renewed within the past four years (2022–2025).
We identified and reviewed provisions from a total of twelve comparable transactions in our precedent database, supplemented by publicly available information from SEC filings, industry surveys, and published commentary from leading technology licensing practitioners. For purposes of this memorandum, we present detailed findings from three representative precedent transactions and aggregate statistics across the broader sample.
Our benchmarking analysis focused on five key categories: (1) scope of the indemnity trigger; (2) exclusions and carve-outs; (3) remedial obligations; (4) treatment of IP indemnity within the liability cap framework; and (5) super-cap or uncapped treatment for IP claims.
B. Scope of Indemnification Trigger — Market Standard
Across the twelve comparable transactions reviewed, virtually all enterprise EDA licenses include a licensor-side IP indemnity for third-party infringement claims arising from the licensee's authorized use of the licensed software. This is a near-universal provision in the EDA industry, reflecting the well-understood principle that the licensor — as the creator and distributor of the software — is best positioned to warrant against infringement and to absorb the risk of third-party claims.
The market-standard scope of covered IP rights typically includes U.S. patents, copyrights, and trade secrets. Some agreements also extend coverage to trademark claims (less common in the EDA context, as trademark infringement is generally less relevant to software licensing) and to intellectual property rights under the laws of foreign jurisdictions (observed in approximately 25–30% of transactions, typically where the licensee has significant non-U.S. operations). As noted in Section III.A above, Meridian's proposed scope — covering U.S. patents, copyrights, trade secrets, and "other intellectual property rights" — is within the market range and is not a significant area of concern.
C. Standard Exclusions — Market Practice
The four exclusions included in Meridian's draft (modifications by the licensee, combination claims, continued use of superseded versions, and licensee-specification claims) are each standard in concept and are found in the vast majority of comparable agreements. However, the specific formulation of these exclusions varies materially across transactions, and the breadth or narrowness of the exclusion language is a frequently negotiated point.
Combination Claims Exclusion. This exclusion was present in all twelve transactions reviewed. However, in approximately two-thirds of those transactions (eight of twelve), the exclusion was narrowed by qualifying language — typically to cover only combinations that were "not reasonably foreseeable," "not contemplated by the licensor's documentation," or "not described in the licensor's published interoperability specifications." The rationale for this narrowing is particularly compelling in the EDA context, where the licensed software is designed to operate in conjunction with third-party PDKs, IP libraries, and other design tools. A broadly worded combination-claims exclusion could effectively eliminate indemnity coverage for the very use cases that the software is designed to support. As discussed in Section III.B above, this issue is especially important for OWS given the Company's reliance on the interoperability between Meridian tools and Brindoval PDKs.
Modifications Exclusion. This exclusion was present in all twelve transactions reviewed and was generally standard in scope. In approximately half of the transactions (six of twelve), the exclusion was narrowed to cover only modifications made by the licensee "without the consent, direction, or involvement of the licensor." This narrowing is consistent with our recommendation for the OWS/Meridian agreement.
Continued Use of Superseded Version Exclusion. This exclusion was present in all twelve transactions and was generally standard, though approximately one-third of the transactions (four of twelve) included a reasonable transition period (ranging from 60 to 180 days) before the exclusion took effect following the licensor's delivery of a non-infringing update.
Licensee-Specification Exclusion. This exclusion was present in eleven of twelve transactions. In seven of those eleven, the exclusion was narrowed to cover claims arising "solely" or "to the extent" from the licensee's unique specifications, ensuring that standard design flows processed through the licensor's tools remained within the scope of indemnity coverage.
Recommendation. Based on this benchmarking analysis, OWS should push to narrow the combination-claims exclusion by adding "not reasonably foreseeable" or "not documented by Meridian as compatible" language. This is especially important given the Brindoval PDK interoperability context described above — OWS uses Meridian tools in conjunction with Brindoval process design kits as a standard part of its design workflow, and the combination-claims exclusion should not effectively eliminate coverage for these standard PDK-tool combinations.
D. Remedial Obligations — Market Comparison
Meridian's proposed three-tier remedial framework upon a determination of infringement — (i) procure the right for OWS to continue using the software; (ii) modify or replace the infringing software with a functionally equivalent non-infringing alternative; (iii) if neither (i) nor (ii) is commercially practicable, terminate the license for the infringing module and refund a pro-rata portion of prepaid and unused fees — is consistent with the standard market approach. All twelve of the comparable transactions reviewed included a substantially similar three-tier remedial structure.
However, the refund remedy (pro-rata unused fees) represents the minimum level of protection in the event of a terminate-and-refund outcome. In four of the twelve transactions reviewed, the remedial framework included a fourth tier: reimbursement of the licensee's reasonable transition costs to an alternative platform in the event the licensor exercises the terminate-and-refund remedy. The rationale is straightforward: if the licensor's inability to cure an infringement forces the licensee to migrate to a competing platform, the licensee will incur substantial transition costs (tool procurement, engineer retraining, workflow re-development, design re-qualification, etc.) that a mere pro-rata refund of unused fees does not begin to cover.
Recommendation. OWS should propose the addition of a transition cost reimbursement remedy as a fourth tier, subject to a reasonable cap (e.g., reimbursement of documented transition costs up to an amount equal to 12 months of fees). This is a meaningful protection that directly addresses OWS's primary business risk — the cost of switching platforms if Meridian cannot cure an infringement — and is supported by market precedent.
E. Cap Treatment — The Central Negotiation Point
This is the most important benchmarking data point for purposes of OWS's negotiation strategy.
1. Market Overview. Among the twelve comparable enterprise software and EDA license agreements reviewed, the treatment of IP indemnification within the liability cap framework was as follows:
• Approximately 60–65% of agreements (seven or eight of twelve) carved IP indemnification out from the general liability cap entirely. In these agreements, the licensor's IP indemnification obligation was either fully uncapped or subject to a separate, substantially higher "super-cap" that was not shared with other liability categories. This was the most common structure observed and reflects the prevailing market norm for enterprise EDA licenses of this scale.
• Approximately 20–25% of agreements (three of twelve) imposed a "super-cap" on IP indemnification — that is, a cap that was separate from and materially higher than the general liability cap. The super-cap amounts observed in these transactions ranged from 2× to 3× annual fees, though one agreement set the IP indemnity super-cap at an amount equal to the total contract value (i.e., 5× annual fees for a five-year agreement).
• Only approximately 10–15% of agreements (one or two of twelve) subjected IP indemnification to the same general liability cap as all other liabilities. In each of these cases, the licensee was a smaller organization with limited negotiating leverage, and the agreements were generally viewed as suboptimal from the licensee's perspective. Notably, none of these agreements involved a transaction of the scale or strategic significance of the OWS/Meridian Renewal ELA.
The clear weight of market practice — across approximately 85–90% of comparable transactions — favors either uncapped treatment or a meaningful super-cap for IP indemnification obligations. Meridian's proposed structure (IP indemnity subject to the same 1× annual fees general cap) is an outlier that falls in the bottom decile of observed market practice.
2. Rationale for Uncapped or Super-Cap Treatment. The market consensus favoring uncapped or super-cap treatment for licensor IP indemnification obligations is grounded in several well-recognized principles:
Risk Allocation. The licensor is the party that created the software and is best positioned to assess and mitigate infringement risk. The licensor has full visibility into its own source code, development history, and the prior art landscape relevant to its technology. The licensee, by contrast, has no practical ability to conduct FTO analysis on the licensor's proprietary codebase and is entirely dependent on the licensor's representations and indemnity for protection against third-party claims.
Information Asymmetry. In the EDA context, this information asymmetry is particularly acute. Meridian's software involves millions of lines of proprietary code implementing complex algorithms for chip design, simulation, verification, and layout. OWS receives only the object code (compiled binaries) and has no visibility into the underlying source code. OWS cannot independently determine whether any portion of Meridian's software infringes the patents, copyrights, or trade secrets of any third party. The IP indemnity is the contractual mechanism through which this information asymmetry is addressed — and capping the indemnity at an artificially low level undermines its protective function.
Moral Hazard. As noted in Section III.D above, capping IP indemnity at 1× annual fees creates a moral hazard: the licensor has a reduced economic incentive to invest in FTO clearance and design-around efforts if its maximum financial exposure is bounded at a level that may be modest relative to the potential costs of infringement. Uncapping or substantially increasing the cap for IP indemnity preserves the licensor's incentive to take proactive steps to avoid infringement.
Financial Capacity. Large EDA vendors such as Meridian — with FY 2024 revenue of approximately $3.1 billion, a market capitalization in the tens of billions of dollars, and robust cash reserves and insurance programs — have the financial capacity to bear uncapped IP indemnity obligations for individual licensees. The risk profile of a single-licensee IP indemnity is manageable for a company of Meridian's scale, particularly given that the indemnity is triggered only by claims arising from the licensee's authorized use of Meridian's own products. Meridian can further manage this risk through its own FTO programs, patent portfolio cross-licensing arrangements, and litigation insurance.
3. Precedent Transactions. We highlight below three representative precedent transactions from Calderwood & Harkness's internal database, anonymized in accordance with our confidentiality obligations:
Precedent A (EDA Vendor / Fabless Semiconductor Company, Approximately $12M/yr TCV). This agreement, executed in 2023, involved a major EDA vendor licensing its full suite of design tools to a fabless semiconductor company of comparable size and profile to OWS. The IP indemnification obligation was fully uncapped — there was no dollar limit on the licensor's indemnification liability for third-party IP infringement claims. The general aggregate liability cap was set at 2× annual fees. Additional carve-outs from the general cap (treated as uncapped) included willful misconduct and breach of confidentiality obligations. The consequential damages waiver was mutual but excluded IP indemnification claims from its scope, permitting the licensee to recover consequential damages (including lost profits) flowing from a covered infringement claim.
Precedent B (EDA Vendor / Integrated Device Manufacturer, Approximately $18M/yr TCV). This agreement, renewed in 2024, involved a major EDA vendor licensing its tools to a large IDM. The IP indemnification obligation was subject to a super-cap of 3× annual fees — separate from and materially higher than the general aggregate liability cap of 1× annual fees. Data breach liability was subject to a separate super-cap of 2× annual fees. Willful misconduct was uncapped. The consequential damages waiver was mutual and did not include a carve-out for IP indemnification (a point that the licensee's counsel subsequently identified as a negotiation gap that should be addressed in the next renewal cycle).
Precedent C (EDA Vendor / Fabless Semiconductor Company, Approximately $7M/yr TCV). This agreement, executed in 2024, involved a mid-tier EDA vendor licensing a more limited suite of tools to a smaller fabless semiconductor company. Despite the smaller transaction size, the IP indemnification obligation was fully uncapped. The general aggregate liability cap was set at 12 months of fees (1× annual fees). Willful misconduct was uncapped. The consequential damages waiver included a carve-out for IP indemnification claims.
All three precedent transactions support OWS's position that IP indemnification should either be fully uncapped or subject to a super-cap that is materially higher than the general liability cap. Notably, even Precedent C — which involved a smaller transaction with a mid-tier vendor (presumably with more limited negotiating capacity than Meridian) — included fully uncapped IP indemnification.
V. Interplay Between IP Indemnity, Data Breach, and Willful Misconduct Carve-Outs
A. OWS's Proposed Liability Cap Structure
Building on the benchmarking analysis set forth in Section IV, we recommend that OWS propose the following liability cap structure in its first redline of the Renewal ELA:
General Aggregate Liability Cap: 2× the annual fees actually paid (or payable) by OWS in the twelve (12) months immediately preceding the event giving rise to the claim. At OWS's target pricing of $11.8 million per year, this would equate to a general cap of $23.6 million. At Meridian's quoted pricing of $14.3 million per year, this would equate to a general cap of $28.6 million. The 2× multiplier (rather than Meridian's proposed 1×) is consistent with the majority of comparable transactions reviewed and reflects the appropriate baseline level of protection for a licensee of OWS's scale and dependency.
Uncapped Categories (Carved Out from the General Aggregate Cap):
(i) Meridian's IP Indemnification Obligations. Meridian's obligation to defend, indemnify, and hold harmless OWS against third-party IP infringement claims under Section 9 of the Renewal ELA shall not be subject to the general aggregate liability cap and shall be fully uncapped.
(ii) Data Breach / Breach of Data Security Obligations. Either party's liability arising from a breach of data security and confidentiality obligations under the applicable sections of the Renewal ELA and the Data Security and Cloud Services Rider shall not be subject to the general aggregate liability cap and shall be fully uncapped.
(iii) Willful Misconduct / Gross Negligence / Fraud. Either party's liability arising from willful misconduct, gross negligence, or fraud shall not be subject to the general aggregate liability cap and shall be fully uncapped.
Rationale for Grouping. The rationale for grouping these three categories of liability as uncapped carve-outs from the general cap is consistent and well-established: each involves a category of liability where (a) the breaching party is uniquely positioned to prevent the harm (Meridian creates the software and can prevent infringement; the hosting party controls data security; the breaching party controls its own conduct); (b) the potential damages to the non-breaching party are disproportionate to the contract value and cannot be adequately compensated by a fee-based cap; and (c) imposing a low cap would create a moral hazard by reducing the breaching party's incentive to prevent the harm.
B. Meridian's Likely Objections and Counter-Arguments
Based on our experience negotiating with Bexley Weir & Daly LLP and our familiarity with Meridian's standard contracting positions, we anticipate the following objections from Meridian and offer corresponding counter-arguments:
Objection 1: Uncapped IP Indemnity Creates Open-Ended Financial Exposure. Meridian will likely argue that an uncapped IP indemnification obligation exposes the licensor to theoretically unlimited liability, which is commercially unreasonable and inconsistent with the risk profile of a software license. Meridian may contend that no vendor should be asked to assume unlimited financial exposure in connection with any single customer license, regardless of the nature of the claim.
Counter-Argument: Meridian's exposure under the IP indemnity is inherently self-limiting in several important respects. First, the indemnity is triggered only by claims arising from OWS's authorized use of the licensed software — Meridian controls the design and implementation of its own products and can take steps to avoid infringement (through FTO analysis, licensing, or design-around). Second, the standard exclusions (modifications by OWS, unforeseeable combinations, OWS-specification claims) further limit the scope of covered claims. Third, Meridian has the right to control the defense of any covered claim, giving it the ability to manage litigation strategy and settlement decisions. Fourth, Meridian — as a $3.1 billion publicly traded company — has the financial capacity, insurance programs, and patent cross-licensing arrangements necessary to manage this risk. The practical likelihood of a single-licensee IP indemnity claim resulting in exposure that would be material to Meridian's balance sheet is extremely low.
Objection 2: Super-Cap as Compromise. If Meridian rejects uncapped treatment, it may propose a super-cap compromise — for example, a cap on IP indemnity at 3× or 5× annual fees, separate from the general liability cap. Meridian may argue that a super-cap appropriately balances the licensor's need for certainty with the licensee's need for meaningful protection.
Counter-Argument: A super-cap is a better outcome than the 1× general cap currently proposed and would represent a material improvement in OWS's position. However, OWS should open with a demand for fully uncapped IP indemnity and concede to a super-cap only as a fallback position. The reason is straightforward: the potential damages from a serious IP infringement claim can be unpredictable and may exceed even a generous super-cap. A super-cap of 3× annual fees ($42.9 million at Meridian's pricing) or 5× annual fees ($71.5 million at Meridian's pricing) provides substantially more headroom than the current 1× proposal, but it may still fall short of the actual exposure in a worst-case scenario involving a broad patent assertion and/or injunctive relief. If a super-cap is ultimately accepted, OWS should push for the highest multiplier achievable — ideally 5× annual fees (approximately equal to total contract value), and no less than 3× annual fees (as identified in Section VII below as OWS's floor).
C. Data Breach Carve-Out
The data breach carve-out is particularly important in the context of the Renewal ELA for two reasons:
Introduction of Meridian CloudVerify™. The Renewal ELA introduces Meridian CloudVerify™, a cloud-hosted verification compute offering through which OWS's proprietary chip design data — including RTL code, netlists, layout data, simulation parameters, and verification test vectors — would be transmitted to and processed within Meridian's cloud infrastructure. This represents a significant expansion of the data flows between the parties compared to the Original ELA, under which all Meridian tools were deployed on-premises within OWS's own computing environment. The introduction of a cloud component materially increases the data security risk profile of the relationship.
Sensitivity of OWS's Design Data. OWS's chip design data constitutes some of the Company's most valuable trade secret information. OWS's optical transceiver IC designs and silicon photonics chiplet architectures embody years of R&D investment and represent core competitive advantages in the hyperscale data center interconnect market. A data breach involving the unauthorized disclosure or exfiltration of this data could cause catastrophic competitive harm — including loss of trade secret protection, loss of first-mover advantage in product roadmap execution, and potential misappropriation by competitors. The financial impact of such a breach could easily exceed $100 million and would far surpass any contractual liability cap pegged to annual license fees.
SOC 2 Compliance. OWS is requiring Meridian to maintain SOC 2 Type II compliance for the CloudVerify™ infrastructure, and Meridian's most recent SOC 2 Type II report is dated June 30, 2025. While SOC 2 compliance provides a useful baseline for data security practices, it does not eliminate the risk of a breach. The data breach carve-out ensures that Meridian's financial incentive to maintain robust security practices is not diluted by an artificial liability cap.
Market Practice. Market practice strongly supports uncapping data breach liability for the party hosting or processing the other party's sensitive data. Among the twelve comparable transactions reviewed, eight of twelve included an uncapped carve-out or a dedicated super-cap for data breach liability. This is consistent with broader trends in technology contracting, where data breach carve-outs have become increasingly common and are widely recognized as a fundamental element of a well-structured liability framework.
D. Willful Misconduct / Gross Negligence / Fraud
The treatment of willful misconduct, gross negligence, and fraud as uncapped carve-outs from the general liability cap is standard market practice and is near-universal in commercial contracts. Among the twelve comparable transactions reviewed, all twelve included an uncapped carve-out for willful misconduct and/or fraud. This carve-out reflects the foundational principle that a party should not be able to cap its liability for intentional or recklessly harmful conduct — to do so would effectively provide a license to act in bad faith, which is contrary to public policy and the implied covenant of good faith and fair dealing.
We anticipate that Meridian will not strongly resist this carve-out, given its near-universal acceptance in commercial practice. If Meridian does object, the objection is unlikely to be sustained in the face of the overwhelming market precedent supporting this position.
VI. Specific Drafting Recommendations
Based on the foregoing analysis, we recommend the following specific drafting changes for inclusion in OWS's first redline of the Renewal ELA (target delivery: November 15, 2025).
A. IP Indemnification Provision — Proposed OWS Redline
We recommend maintaining Meridian's general indemnification scope (coverage for third-party claims alleging infringement of U.S. Intellectual property rights arising from OWS's authorized use of the licensed software) but incorporating the following modifications:
1. Narrow the Combination-Claims Exclusion. The combination-claims exclusion in Section 9.2(b) should be revised to exclude from indemnification only claims arising from the use of the licensed software in combination with third-party products or technologies that are "not reasonably foreseeable" or "not described in Meridian's documentation, published interoperability specifications, or published compatibility guides." This narrowing ensures that standard combinations — including, critically, the combination of Meridian tools with Brindoval and other foundry PDKs — remain within the scope of the indemnity. The revised language would also expressly state that combinations with third-party PDKs and IP libraries that are identified in Meridian's documentation as compatible shall not be excluded from indemnity coverage.
2. Narrow the Modification Exclusion. The modification exclusion in Section 9.2(a) should be revised to cover only modifications made by OWS "without the written consent, direction, or involvement of Meridian." This narrowing ensures that customizations made by OWS with Meridian's guidance, assistance, or professional services support are not excluded from indemnity coverage. This is particularly important given that OWS's design engineers frequently develop automation scripts and customizations within the Meridian tool environment, sometimes in collaboration with Meridian's customer engineering team.
3. Add Transition Cost Reimbursement Remedy. A fourth remedial tier should be added to the infringement remedies in Section 9.3, providing that if Meridian exercises the terminate-and-refund option (because it is unable to procure continued use rights or provide a non-infringing replacement), Meridian shall also reimburse OWS for its reasonable, documented transition costs incurred in migrating to an alternative EDA platform, subject to a cap of twelve (12) months of fees. In addition, a reasonable transition period of not less than ninety (90) days should be specified before OWS is required to cease use of the infringing module following Meridian's delivery of a non-infringing replacement under the continued-use-of-superseded-version exclusion.
4. Carve Out IP Indemnification from the General Liability Cap. Section 10 (Limitation of Liability) should expressly state that Meridian's IP indemnification obligations under Section 9 are not subject to, and shall not be limited by, the general aggregate liability cap set forth in Section 10.1. This is the single most important drafting change in this negotiation and is the subject of the detailed analysis and market benchmarking set forth in Sections III through V of this memorandum.
B. Limitation of Liability — Proposed OWS Redline
We recommend that the limitation-of-liability provision in Section 10 be revised as follows:
General Aggregate Liability Cap (Section 10.1). Neither party's aggregate liability under this Agreement, whether arising in contract, tort (including negligence), strict liability, or otherwise, shall exceed an amount equal to two times (2×) the annual fees actually paid or payable by OWS to Meridian in the twelve (12) months immediately preceding the event giving rise to the claim (the "General Cap").
Carve-Outs from the General Cap (Section 10.2). The General Cap shall not apply to, and shall not limit, either party's liability with respect to the following:
(i) Meridian's IP indemnification obligations under Section 9 of this Agreement;
(ii) Either party's liability arising from a breach of its data security and confidentiality obligations under Section [] and the Data Security and Cloud Services Rider attached hereto as Exhibit [];
(iii) Either party's liability arising from willful misconduct, gross negligence, or fraud;
(iv) Either party's liability arising from a misappropriation of the other party's intellectual property rights (including, without limitation, a misappropriation of trade secrets).
Consequential Damages Waiver (Section 10.3). The standard mutual exclusion of indirect, incidental, special, punitive, and consequential damages (including lost profits) should be retained as a general matter but should expressly carve out the following from the scope of the waiver:
(a) Meridian's IP indemnification obligations under Section 9, such that OWS may recover consequential damages (including lost profits, lost revenue, and increased costs of procurement) flowing from a covered third-party IP infringement claim; and
(b) Either party's liability arising from a breach of data security and confidentiality obligations, such that the non-breaching party may recover consequential damages flowing from a data breach or unauthorized disclosure of confidential information.
The carve-out of IP indemnification from the consequential damages waiver is critical. Without this carve-out, OWS's recovery in connection with a covered infringement claim would be limited to direct damages (e.g., the reasonable royalty or damages awarded by a court), but would not include the potentially much larger consequential losses flowing from the infringement (e.g., lost profits from delayed tape-outs, costs of transitioning to an alternative platform, lost customer contracts). Given that the consequential losses from a serious infringement claim are likely to dwarf the direct damages, the carve-out is essential to the effectiveness of the indemnity.
C. Relationship to Source Code Escrow
We note for completeness that the proposed Technology Escrow Agreement with Iron Vault Escrow Services, Inc. (1700 Lincoln Street, Suite 2100, Denver, Colorado 80203) provides an additional protective mechanism for OWS in the event of certain triggering events — specifically, if Meridian becomes insolvent, materially breaches the Renewal ELA and fails to cure, or discontinues one or more of the licensed product lines. In such events, OWS would gain access to the escrowed source code for the licensed Meridian software modules, enabling OWS to maintain and support the tools internally (or through a third-party contractor) and preserve continuity of its design engineering operations.
While the escrow arrangement provides important continuity protection, it does not substitute for robust IP indemnification. Even if OWS obtains access to source code through an escrow release, OWS would still face infringement exposure if the underlying code infringes third-party IP rights. The escrow agreement gives OWS the practical ability to continue using the software, but it does not insulate OWS from third-party infringement claims — only the IP indemnity provides that protection.
Accordingly, we recommend ensuring that the IP indemnification obligation survives termination or expiration of the Renewal ELA for any claims arising from OWS's use of the licensed software during the license term (including any post-termination wind-down period). The survival provision should be clearly drafted and should not be subject to a time limitation shorter than the applicable statute of limitations for the underlying IP claims (typically six years for patent infringement under 35 U.S.C. § 286).
VII. Fallback Positions
Recognizing that negotiations are iterative and that Meridian may not accept OWS's opening position in full, we have developed the following graduated negotiation framework. Each fallback position represents the next-best commercially acceptable outcome if OWS is unable to secure its preferred position.
A. Preferred Position (Opening)
• IP Indemnification: Fully uncapped (no dollar limit on Meridian's IP indemnification obligations).
• General Aggregate Liability Cap: 2× annual fees.
• Data Breach: Fully uncapped (no dollar limit on either party's data breach liability).
• Willful Misconduct / Gross Negligence / Fraud: Fully uncapped.
• Consequential Damages Waiver: Mutual, with carve-outs for IP indemnification and data breach.
This is the strongest commercially justifiable position and is consistent with market norms as demonstrated by the benchmarking analysis in Section IV. OWS should open with this position and advocate for it vigorously, using the market data and risk-allocation arguments set forth in this memorandum.
B. First Fallback
• IP Indemnification: Super-cap at 5× annual fees (i.e., approximately $71.5 million at Meridian's quoted pricing, or approximately $59.0 million at OWS's target pricing — in either case, approximately equal to total contract value).
• General Aggregate Liability Cap: 2× annual fees.
• Data Breach: Fully uncapped.
• Willful Misconduct / Gross Negligence / Fraud: Fully uncapped.
• Consequential Damages Waiver: Mutual, with carve-outs for IP indemnification and data breach.
This fallback gives Meridian the certainty of a defined dollar cap on its IP indemnity exposure while providing OWS with a level of protection that is approximately five times higher than the general cap and is roughly equivalent to the total value of the five-year agreement. A 5× annual fees super-cap is within the range of market practice (observed in some comparable transactions) and is supported by the Precedent B structure described in Section IV.E.3 (which included a 3× super-cap for a larger transaction).
C. Second Fallback (Floor)
• IP Indemnification: Super-cap at 3× annual fees (i.e., approximately $42.9 million at Meridian's quoted pricing, or approximately $35.4 million at OWS's target pricing).
• General Aggregate Liability Cap: 2× annual fees.
• Data Breach: Super-cap at 3× annual fees.
• Willful Misconduct / Gross Negligence / Fraud: Fully uncapped.
• Consequential Damages Waiver: Mutual, with carve-outs for IP indemnification and data breach.
This represents the floor of OWS's acceptable negotiation range. A 3× annual fees super-cap for IP indemnification provi

MEMORANDUM

ATTORNEY-CLIENT PRIVILEGED AND CONFIDENTIAL ATTORNEY WORK PRODUCT

MATTER NO.: 1014-00006

Record

Parties

Dates

Amounts