1042-00005 · Lattimore, Parish & Keene LLP · Analyses & Memos

ip-ownership-and-escrow-analysis.docx DOCUMENT M&A / Corporate

1 / 12 → ✕

PRIVILEGED AND CONFIDENTIAL ATTORNEY-CLIENT PRIVILEGED ATTORNEY WORK PRODUCT

MEMORANDUM

FROM: Amy Chesterton, Associate, Calderwood & Harkness LLP

TO: Douglas Fairchild, Responsible Partner, Calderwood & Harkness LLP; Priya Narasimhan, General Counsel, Brightfield Cloud Services Inc.

DATE: January 3, 2026

RE: Analysis of intellectual Property Ownership, Trademark License, and Source Code Escrow Provisions — Proposed OEM Reseller Agreement between Brightfield Cloud Services Inc. and Vantage Industrial Solutions, LLC

ENGAGEMENT NO.: 1042-00005

Right-click to update Table of Contents

I. INTRODUCTION AND EXECUTIVE SUMMARY

The purpose of this memorandum is to analyze and advise on the intellectual property protections afforded to Brightfield Cloud Services Inc. ("BCS") in the proposed OEM Reseller Agreement (the "Agreement") with Vantage Industrial Solutions, LLC ("Vantage"). This memorandum addresses four principal areas: (1) intellectual property ownership provisions, (2) the scope and limitations of the trademark license, (3) the enforceability and scope of the Limited Exclusivity Covenant, and (4) the terms and conditions of the three-party source code escrow arrangement, including our analysis and recommendation regarding Vantage's proposed change-of-control release trigger. This memorandum does not address all negotiation points in the proposed Agreement; a separate negotiation issues memorandum will follow.

Background. BCS is a Delaware corporation headquartered at 4100 Esperanza Boulevard, Suite 800, Austin, Texas 78746. BCS is majority-owned (approximately 68% equity) by Veltrano Capital Partners Fund IV, L.P. ("Veltrano Capital"). BCS currently generates annual recurring revenue ("ARR") of approximately $62 million and employs approximately 320 individuals. BCS's core product is the "BrightEdge" IoT platform, which comprises cloud-hosted analytics software, embedded edge firmware, and proprietary sensor hardware modules. The BrightEdge platform is BCS's primary revenue driver and its most significant intellectual property asset.

Vantage is a Delaware limited liability company with its principal office located at 7755 Commerce Park Drive, Solon, Ohio 44139. Vantage designs, manufactures, and distributes programmable logic controllers ("PLCs"), SCADA interfaces, and industrial automation hardware. Vantage reported revenue of approximately $310 million for its fiscal year ended December 31, 2024, and currently employs approximately 1,200 individuals. Vantage is majority-owned by Harmon Family Holdings, LLC, with minority institutional holdings held by Velthorn Bridge Capital, LLC.

Proposed Transaction. The proposed Agreement contemplates an OEM reseller arrangement under which Vantage will embed BCS's proprietary BrightEdge IoT platform software and companion hardware modules into Vantage's product line and resell the combined solution to end-users in the United States and Canada (the "Territory"). The total deal value is $15,000,000, based on a Minimum Annual Commitment ("MAC") of $5,000,000 per year over a three-year initial term. The term sheet was signed on December 19, 2025, by Connor Whitfield, Vice President of Business Development at BCS, and Derek Yun, Vice President of Supply Chain & Procurement at Vantage. Calderwood & Harkness LLP is preparing the first draft of the OEM Reseller Agreement, which is scheduled for circulation on January 6, 2026.

Vantage is represented by Lattimore, Parish & Keene LLP, located in Cleveland, Ohio, with Thomas Ellsworth serving as lead partner and Jennifer Murata serving as the primary associate on the matter.

Summary of Key Conclusions. Based on the analysis set forth below, our principal conclusions and recommendations are as follows:

(1) IP Ownership Provisions. The intellectual property ownership provisions as currently contemplated are robust and should be maintained without concession. BCS should retain all right, title, and interest in the BrightEdge platform and all derivatives thereof. An express assignment clause covering any derivative works or improvements created by Vantage is critical and should not be negotiated away.

(2) Trademark License. The trademark license is appropriately limited in scope. It should be accompanied by comprehensive brand-use guidelines and quality control provisions sufficient to comply with the Lanham Act's requirements for trademark licensors. All goodwill generated through Vantage's use of BCS trademarks must inure to BCS's benefit.

(3) Limited Exclusivity Covenant. The Limited Exclusivity Covenant is enforceable under Delaware law given its narrow scope. However, the term "industrial automation vertical" should be defined with precision in the Agreement to avoid ambiguity and potential disputes over scope.

(4) Source Code Escrow. The source code escrow release conditions as currently drafted protect BCS's interests. The three specified release triggers — cessation of business operations, bankruptcy filing, and material failure to maintain or support the software for more than 120 consecutive days after written notice — are appropriate and favorable to BCS. Vantage's anticipated request to add a change-of-control trigger as a fourth release condition should be firmly rejected. A change-of-control trigger would penalize BCS and Veltrano Capital for legitimate corporate transactions, undermine the value of BCS's IP portfolio, and is not consistent with prevailing market practice for technology escrow agreements.

Each of these conclusions is discussed in detail below.

II. LICENSED TECHNOLOGY — SCOPE AND DESCRIPTION

A. Components of the BrightEdge IoT Platform

The Licensed Technology under the proposed Agreement comprises three distinct components, each of which implicates different IP ownership and licensing considerations:

(i) BrightEdge SaaS Subscription Software. The BrightEdge SaaS subscription software is a cloud-hosted analytics and dashboard platform that aggregates, processes, and displays IoT sensor data for end-users. This software is hosted on BCS's cloud infrastructure and accessed by end-users through a web-based interface. The SaaS component represents BCS's core recurring revenue stream, as end-users pay ongoing subscription fees for access to the platform's analytics capabilities. The software incorporates proprietary algorithms, data processing architectures, and machine learning models developed by BCS's engineering team.

(ii) BrightEdge Edge Firmware. The BrightEdge Edge Firmware is embedded software loaded onto BCS's proprietary hardware modules. The firmware enables on-device processing, data collection, and secure communication between the hardware modules and the cloud-hosted SaaS platform. The Edge Firmware is compiled from proprietary source code maintained by BCS and is integral to the functioning of the hardware modules. Because the firmware is embedded directly in hardware that will be physically distributed to Vantage's end-users, it presents unique risks related to reverse engineering and unauthorized modification.

(iii) BCS Model BE-400 and BE-600 Sensor Hardware Modules. The BCS Model BE-400 and Model BE-600 sensor hardware modules are proprietary IoT sensor devices designed and manufactured by BCS. The BE-400 is a compact sensor module priced at $185 per unit, and the BE-600 is an advanced multi-sensor module priced at $340 per unit. Both models are shipped FOB Austin, Texas, meaning that BCS controls the manufacturing process and supply chain, and title and risk of loss transfer to Vantage upon delivery to the carrier in Austin.

The software royalty under the proposed Agreement is set at 18% of Vantage's net resale price of the embedded SaaS subscription billed to each end-user, payable quarterly in arrears. This royalty structure ensures that BCS participates in the ongoing revenue generated by the BrightEdge platform even after the hardware modules are sold into the field. The BrightEdge platform is currently at version 4.2, and BCS's product roadmap anticipates material updates and new feature releases during the initial three-year term of the Agreement.

B. Significance of IP Protections Given the Nature of the Technology

The intellectual property protections discussed in this memorandum are of paramount importance given the nature of the BrightEdge platform and the structure of the proposed OEM reseller relationship. Several factors heighten the significance of these protections:

Core Asset Status. The BrightEdge platform is BCS's core asset and primary revenue driver. BCS's enterprise valuation, as assessed in connection with Veltrano Capital's initial investment, is substantially dependent on the proprietary nature and competitive differentiation of the BrightEdge technology. Any erosion of BCS's IP rights in the BrightEdge platform could materially diminish BCS's enterprise value and impair Veltrano Capital's anticipated return on its investment.

Co-Mingling Risk. The OEM reseller structure inherently creates a risk of co-mingling of intellectual property. Vantage will be embedding BCS's firmware and hardware modules into Vantage's own product line, creating a combined solution that incorporates both parties' technology. This integration work may require Vantage's engineers to interact with, modify, or create interfaces for BCS's firmware and software. Without clear IP ownership provisions and express assignment clauses, there is a risk that Vantage could assert ownership or joint-ownership claims over derivative works, modifications, or improvements arising from the integration process.

R&D Investment. BCS's proprietary algorithms, firmware architecture, and hardware designs represent substantial research and development investment accumulated over multiple product generations. BCS has invested significant engineering resources in developing the machine learning models, edge computing architectures, and secure communication protocols that differentiate the BrightEdge platform from competing IoT solutions in the market. Protection of this investment requires robust contractual safeguards against reverse engineering, decompilation, and independent exploitation by Vantage beyond the scope of the reseller relationship.

Enterprise IoT Market Dynamics. The enterprise IoT market is characterized by intense competition, rapid technological evolution, and high barriers to entry for providers of integrated hardware-software platforms. BCS's competitive advantage depends on the proprietary nature of the BrightEdge technology. If Vantage were to gain access to BCS's source code, hardware designs, or algorithmic methodologies outside the intended scope of the Agreement, the competitive harm to BCS could be severe and potentially irreversible.

For all of these reasons, the IP ownership, trademark license, and source code escrow provisions must be drafted with precision and maintained through negotiations without material concession.

III. INTELLECTUAL PROPERTY OWNERSHIP PROVISIONS

A. Retention of All Right, Title, and Interest

The cornerstone of the IP protections framework in the proposed Agreement is the unequivocal retention by BCS of all right, title, and interest in and to the BrightEdge platform. We recommend that the Agreement include an express statement along the following lines:

"As between the parties, BCS retains and shall retain all right, title, and interest in and to the Licensed Technology, including without limitation all software (including the BrightEdge SaaS subscription software and BrightEdge Edge Firmware), hardware designs, schematics, specifications, technical documentation, algorithms, data models, trademarks (including the 'BrightEdge' mark and the BCS logo), copyrights, patents, trade secrets, and all other intellectual property rights therein and thereto, together with all enhancements, modifications, derivative works, improvements, updates, and new versions thereof."

This provision should make clear that no transfer of ownership or assignment of any intellectual property rights to Vantage occurs under the Agreement. Vantage receives only a limited, non-exclusive license to use, distribute, and resell the Licensed Technology within the Territory as part of Vantage's combined product offering. The license is circumscribed by the terms and conditions of the Agreement, including the territorial limitation (United States and Canada), the product-specific scope (resale as part of Vantage's combined product line), and the temporal limitation (the term of the Agreement).

All enhancements, modifications, derivative works, improvements, updates, and new versions of the BrightEdge platform made by BCS during the term of the Agreement remain solely owned by BCS. This principle applies regardless of whether such enhancements or modifications are developed in response to feedback from Vantage, requests from Vantage's end-users, or BCS's own product development roadmap.

We further recommend that the Agreement include a negative covenant in which Vantage expressly acknowledges and agrees that it acquires no ownership interest in the Licensed Technology by virtue of the Agreement, and that it will not challenge or contest BCS's ownership of the Licensed Technology or the validity of BCS's intellectual property rights.

B. Derivative Works and Improvements Created by Vantage

One of the most significant risks in an OEM reseller arrangement of this nature is the potential for Vantage's integration work to give rise to derivative works of BCS's firmware or software. As Vantage's engineering team works to embed the BrightEdge platform into Vantage's product line, it is foreseeable that Vantage's engineers or contractors may create modifications, adaptations, interfaces, integration layers, or other works that incorporate or build upon BCS's proprietary code. Under U.S. copyright law, a derivative work is a work based upon one or more preexisting works, and the creator of a derivative work may acquire certain rights in the new expression contained in the derivative work — even if the underlying preexisting work remains owned by the original copyright holder.

To address this risk, we recommend that the Agreement include an express assignment clause requiring that any and all improvements, modifications, derivative works, adaptations, translations, interfaces, integration code, and other works created by Vantage, its employees, contractors, or agents in connection with or arising out of the Licensed Technology are automatically and irrevocably assigned to BCS upon their creation. The relevant provision should include language along the following lines:

"Vantage hereby irrevocably assigns and agrees to assign to BCS all right, title, and interest in and to any and all improvements, modifications, derivative works, adaptations, translations, and other works created by or on behalf of Vantage, its employees, contractors, or agents in connection with or arising out of the Licensed Technology, including all intellectual property rights therein. Such assignment shall be effective automatically upon creation of such works without the need for further action by either party."

Work-for-Hire Analysis. It is important to note that as Vantage is a limited liability company and not an employee of BCS, works created by Vantage's personnel may not automatically qualify as "works made for hire" under Section 101 of the Copyright Act (17 U.S.C. § 101). The work-for-hire doctrine generally applies to works created by employees within the scope of their employment or to certain categories of commissioned works where the parties have expressly agreed in a signed writing that the work is a work made for hire. Because Vantage is an independent contractor rather than an employee of BCS, and because the categories of commissioned works eligible for work-for-hire status under the Copyright Act are limited, we cannot rely on the work-for-hire doctrine alone to vest ownership of Vantage-created derivative works in BCS. Express assignment language is therefore critical and must be included in the Agreement.

Confirmatory Assignment and Cooperation. In addition to the automatic assignment provision, we recommend including a confirmatory assignment obligation and a cooperation clause. The confirmatory assignment obligation would require Vantage, upon request by BCS, to execute and deliver any documents or instruments reasonably necessary to confirm, perfect, or record BCS's ownership of assigned works. The cooperation clause would obligate Vantage to cooperate with BCS in connection with any patent, copyright, or other intellectual property applications or registrations related to assigned works, at BCS's cost and expense. We further recommend including a limited power of attorney, irrevocable and coupled with an interest, authorizing BCS to execute documents on Vantage's behalf if Vantage fails or refuses to do so within a reasonable period after request.

C. Hardware Design Ownership

BCS's proprietary hardware module designs present a separate category of intellectual property requiring explicit protection. The BE-400 and BE-600 sensor hardware module designs, including all schematics, specifications, manufacturing processes, bill of materials, component selections, circuit board layouts, and related technical documentation, must be expressly identified as BCS's exclusive property. The Agreement should include a specific prohibition against Vantage manufacturing, reverse-engineering, disassembling, or creating substantially similar hardware modules. This prohibition should extend to Vantage's affiliates, contractors, and any third parties acting on Vantage's behalf.

The FOB Austin, Texas shipping terms for hardware module deliveries reinforce BCS's control over the manufacturing process and supply chain. Under these terms, BCS manufactures the hardware modules at its Austin facility (or through its designated contract manufacturers), and title and risk of loss transfer to Vantage upon delivery to the carrier at BCS's shipping point. This structure ensures that Vantage does not gain access to BCS's manufacturing processes, supply chain relationships, or contract manufacturer identities. We recommend that the Agreement expressly state that the FOB shipping terms do not create any implied license or right for Vantage to manufacture or have manufactured any hardware modules or substantially similar devices.

Additionally, because the BE-400 and BE-600 modules contain embedded firmware (the BrightEdge Edge Firmware), the hardware design ownership provisions and the software IP ownership provisions should be drafted in a coordinated manner to ensure comprehensive protection of both the hardware and the embedded software components.

D. Feedback and Suggestions

It is common in OEM reseller relationships for the reseller and its end-users to provide feedback, suggestions, feature requests, bug reports, and other input regarding the licensed technology. Such feedback may contain valuable insights that inform the licensor's product development roadmap. However, if not properly addressed in the Agreement, feedback could create ambiguity regarding ownership rights — particularly if Vantage later claims that a BCS product enhancement was derived from Vantage's feedback and therefore constitutes a jointly owned work.

We recommend that the Agreement include a clear provision addressing the treatment of feedback, substantially as follows:

"Vantage hereby grants to BCS a perpetual, irrevocable, worldwide, royalty-free, fully paid-up, non-exclusive license to use, reproduce, modify, create derivative works based upon, distribute, and otherwise exploit any feedback, suggestions, ideas, enhancement requests, or other input provided by Vantage or its end-users regarding the Licensed Technology, without compensation, attribution, or any other obligation to Vantage. BCS shall be the sole and exclusive owner of any improvements, enhancements, or modifications to the Licensed Technology made by BCS, whether or not informed by or incorporating feedback received from Vantage."

This approach — granting BCS a broad license to feedback rather than relying solely on assignment — is recommended because assignment of "ideas" and "suggestions" that have not been reduced to a copyrightable or patentable form presents enforceability challenges. The combination of a broad feedback license and the derivative works assignment clause discussed in Section III.B above provides comprehensive coverage.

IV. TRADEMARK LICENSE — SCOPE AND LIMITATIONS

A. Grant of Trademark License

Under the proposed Agreement, BCS will grant Vantage a limited, non-transferable, royalty-free license to use BCS's trademarks, including the "BrightEdge" word mark and the BCS logo (collectively, the "BCS Marks"), solely in connection with the marketing, promotion, distribution, and resale of the Licensed Technology within the Territory. The key attributes of the trademark license are as follows:

• Scope: The license is limited to use of the BCS Marks solely in connection with the marketing and resale of the Licensed Technology as embedded in Vantage's combined product offering. The license does not extend to use of the BCS Marks in connection with any other Vantage product, service, or activity.

• Territory: The license is limited to the United States and Canada, consistent with the territorial scope of the OEM Reseller Agreement.

• Exclusivity: The trademark license is non-exclusive. BCS retains the right to use the BCS Marks in any manner and to grant trademark licenses to other parties.

• Transferability: The license is non-transferable and non-sublicensable. Vantage may not assign, sublicense, or otherwise transfer the trademark license to any third party without BCS's prior written consent, which BCS may withhold in its sole discretion.

• Royalty: The trademark license is royalty-free. No separate royalty or license fee is charged for Vantage's use of the BCS Marks; the consideration for the trademark license is subsumed within the overall commercial arrangement under the Agreement.

• Term: The trademark license terminates automatically and without further action upon termination or expiration of the OEM Reseller Agreement, regardless of the reason for such termination or expiration. Upon termination of the trademark license, Vantage must immediately cease all use of the BCS Marks and destroy or return all materials bearing the BCS Marks.

B. Brand-Use Guidelines (Exhibit D)

Vantage's use of the BCS Marks will be subject to compliance with BCS's comprehensive brand-use guidelines, which will be set forth in Exhibit D to the Agreement. The brand-use guidelines are a critical component of the trademark license, as they establish the parameters within which Vantage may use the BCS Marks and provide the framework for BCS's quality control obligations as trademark licensor.

We recommend that Exhibit D address, at a minimum, the following topics:

• Approved logo formats, including vector files and raster images at specified resolutions;

• Placement specifications for the BCS Marks on Vantage's product packaging, product labels, user interfaces, and marketing materials;

• Minimum sizing requirements to ensure legibility and brand visibility;

• Color standards, including approved color palettes (specified by Pantone, CMYK, and RGB values) and restrictions on the use of alternative colors;

• Prohibited modifications, including prohibitions on altering, distorting, animating, or combining the BCS Marks with other marks or design elements without BCS's express written approval;

• Co-branding requirements, specifying how the BCS Marks must be displayed in conjunction with Vantage's own trademarks and trade dress;

• Trademark attribution requirements, including the use of appropriate trademark symbols (® or ™) and ownership attribution statements;

• Approved and prohibited uses in digital media, including website displays, social media, online advertising, and email marketing; and

• The approval workflow for marketing materials, as discussed below.

Pre-Approval Requirement. BCS should retain the right to review and approve all marketing and promotional materials incorporating the BCS Marks prior to their publication, distribution, or dissemination by Vantage. We recommend that the Agreement specify a defined approval and response period — we recommend ten (10) business days from BCS's receipt of the materials for review. If BCS does not respond within the approval period, the materials should be deemed not approved (i.e., silence should not constitute consent). This approach ensures that BCS maintains active oversight of how its marks are used in the marketplace.

Updates to Brand-Use Guidelines. BCS should retain the unilateral right to update, amend, and supplement the brand-use guidelines from time to time during the term of the Agreement. We recommend that BCS be required to provide Vantage with reasonable advance written notice of any material changes to the brand-use guidelines — we suggest not less than thirty (30) days' prior written notice — and that Vantage be required to bring its use of the BCS Marks into compliance with the updated guidelines within a reasonable transition period, which we suggest be sixty (60) days from the effective date of the updated guidelines.

C. Quality Control

Under the Lanham Act (15 U.S.C. § 1055), a trademark licensor has an affirmative obligation to exercise adequate quality control over the goods and services offered by the licensee under the licensed marks. Failure to exercise quality control may result in a finding of "naked licensing," which can lead to a determination that the licensor has abandoned the mark. See, e.g., Barcamerica Int'l USA Trust v. Tyfield Imps., Inc., 289 F.3d 589, 596 (9th Cir. 2002) (holding that the absence of quality control provisions in a trademark license constituted naked licensing); Eva's Bridal Ltd. v. Halanick Enters., Inc., 639 F.3d 788, 790 (7th Cir. 2011) (Posner, J.) (discussing the naked licensing doctrine). While naked licensing defenses are most commonly raised in trademark infringement disputes, the risk of abandonment is a real concern that must be addressed proactively in the Agreement.

We recommend the following quality control provisions:

(a) Inspection and Testing Rights. BCS shall have the right, upon reasonable advance notice, to inspect and test Vantage's combined product offering at any time during the term of the Agreement to ensure that the BrightEdge components meet BCS's quality standards. Inspections may include review of product packaging, marketing materials, product documentation, and the user experience associated with Vantage's integration of the BrightEdge platform.

(b) Compliance Standards. Vantage shall ensure that the combined product offering incorporating the BrightEdge platform meets or exceeds the quality standards specified by BCS, including technical performance standards, user interface standards, customer support standards, and any other standards BCS may reasonably establish from time to time.

(c) Suspension and Termination. BCS shall have the right to suspend or terminate the trademark license, effective immediately upon written notice, if Vantage's use of the BCS Marks materially deviates from the brand-use guidelines set forth in Exhibit D or if Vantage's combined product offering fails to meet BCS's quality standards in a manner that negatively impacts the goodwill associated with the BCS Marks. The suspension or termination of the trademark license shall not, by itself, constitute a termination of the OEM Reseller Agreement, although it may give rise to a right to terminate the Agreement for cause if uncured.

(d) Goodwill. All goodwill generated through Vantage's use of the BCS Marks shall inure solely and exclusively to the benefit of BCS. Vantage acknowledges that it acquires no rights in the BCS Marks by virtue of its use thereof, and that all such use is on behalf of and for the benefit of BCS.

D. Trademark Enforcement

The Agreement should clearly allocate trademark enforcement rights and obligations between the parties. We recommend the following provisions:

BCS retains the sole and exclusive right to enforce its trademarks against third-party infringers, including the right to initiate, conduct, settle, and control any legal proceedings or other enforcement actions relating to the BCS Marks. Vantage has no independent right to bring infringement actions, send cease-and-desist communications, or otherwise enforce the BCS Marks against third parties, unless specifically authorized by BCS in writing.

Vantage should be obligated to promptly notify BCS of any known or suspected infringement, dilution, or unauthorized use of the BCS Marks that comes to Vantage's attention, including any use by third parties that is confusingly similar to the BCS Marks. Such notification should be provided in writing within ten (10) business days of Vantage becoming aware of the potentially infringing activity. Vantage should further be obligated to cooperate with BCS, at BCS's cost and expense, in connection with any enforcement actions BCS may elect to pursue.

This allocation of enforcement rights is standard in trademark license agreements and is consistent with BCS's retention of all goodwill and ownership rights in the BCS Marks.

V. LIMITED EXCLUSIVITY COVENANT

A. Structure of the Covenant

The proposed Agreement is structured as a non-exclusive OEM reseller arrangement — BCS retains the right to appoint additional OEM resellers and to sell the BrightEdge platform through other channels. However, as a concession negotiated in the term sheet, BCS has agreed to a Limited Exclusivity Covenant under which BCS will not appoint more than four (4) additional OEM resellers in the "industrial automation vertical" within the Territory (United States and Canada) during the initial three-year term of the Agreement (anticipated to run from February 20, 2026 through February 19, 2029).

Under this structure, the total number of OEM resellers permitted in the industrial automation vertical within the Territory during the initial term is capped at five (5): Vantage, plus up to four (4) additional resellers appointed by BCS. This numerical cap provides Vantage with a degree of competitive protection — limiting the number of competing OEM resellers carrying the BrightEdge platform in the same vertical — while preserving BCS's ability to diversify its distribution channels and avoid overdependence on a single reseller partner.

The Limited Exclusivity Covenant does not restrict BCS's ability to sell the BrightEdge platform directly to end-users, to license the BrightEdge platform to OEM resellers outside the industrial automation vertical, or to license the platform to resellers outside the Territory.

B. Enforceability Analysis

The OEM Reseller Agreement will be governed by Delaware law. Delaware courts generally enforce reasonable restrictive covenants in commercial agreements between sophisticated parties, applying a standard of reasonableness that considers the scope, duration, and geographic reach of the restriction. See Kan-Di-Ki, LLC v. Susi, 2015 WL 4503210, at *12 (Del. Ch. July 22, 2015) (discussing enforceability of restrictive covenants in commercial contracts under Delaware law).

The Limited Exclusivity Covenant is narrowly tailored across three dimensions:

• Vertical Scope: The covenant is limited to the "industrial automation vertical" and does not restrict BCS's ability to appoint OEM resellers in other verticals (e.g., healthcare, smart building, logistics, energy, etc.).

• Territorial Scope: The covenant applies only within the United States and Canada and does not restrict BCS's activities in any other geographic market.

• Temporal Scope: The covenant applies only during the initial three-year term of the Agreement and does not extend to any renewal periods unless the parties affirmatively renegotiate.

Furthermore, the covenant is a practical limitation rather than an absolute exclusivity. BCS is permitted to appoint up to four additional OEM resellers in the industrial automation vertical during the initial term, meaning that the industrial automation market in the Territory is not reserved solely for Vantage. This structure significantly reduces the risk of anticompetitive challenges under federal or state competition laws, as Vantage does not receive the kind of absolute territorial or vertical exclusivity that might raise concerns under the Sherman Act or analogous state statutes.

It is also important to distinguish this commercial covenant from an employee non-compete agreement. Employee non-competes are subject to heightened scrutiny under the laws of many states, including recent regulatory activity by the Federal Trade Commission. The Limited Exclusivity Covenant, by contrast, is a commercial restriction negotiated at arm's length between two sophisticated business entities, and it is subject to a more permissive standard of review. Delaware courts have consistently recognized the distinction between employee non-competes and commercial restrictive covenants, applying a less exacting reasonableness analysis to the latter.

Risk Assessment. We assess the risk of unenforceability of the Limited Exclusivity Covenant as low, given its narrow scope, defined duration, and limited territorial reach. However, we recommend that the term "industrial automation vertical" be defined with precision in the Agreement to avoid ambiguity and potential disputes over scope. A vague or overly broad definition could create uncertainty regarding which OEM reseller appointments by BCS would violate the covenant, potentially leading to costly disputes. We recommend a definition along the following lines:

"Industrial Automation Vertical" means the market for products and services used in the automated control, monitoring, and optimization of industrial manufacturing processes, industrial equipment operations, and industrial facility management, including without limitation programmable logic controllers, SCADA systems, distributed control systems, human-machine interfaces, industrial robotics, and industrial IoT sensor networks, but excluding building automation systems, healthcare monitoring systems, logistics and supply chain management systems, and consumer IoT products.

This definition should be reviewed and approved by BCS's business team to ensure alignment with BCS's commercial strategy and market segmentation.

C. Interplay with Non-Compete Provision (Section 12.2)

Separate from the Limited Exclusivity Covenant (which restricts BCS's ability to appoint additional resellers), Section 12.2 of the proposed Agreement contains a non-compete provision restricting Vantage from distributing, reselling, or otherwise offering a "Competing Product" during the term of the Agreement and for a specified period following termination. The non-compete provision runs in the opposite direction from the Limited Exclusivity Covenant — it restricts Vantage, not BCS — and is designed to ensure that Vantage does not undermine the commercial relationship by simultaneously reselling a competing IoT platform alongside the BrightEdge platform.

The definition of "Competing Product" is currently an open negotiation point. Vantage, through its counsel at Lattimore, Parish & Keene LLP, has requested that the definition be narrowed to exclude legacy SCADA-only analytics products that do not incorporate cloud-based IoT functionality. Vantage's position is that its existing relationships with certain SCADA analytics vendors predate the proposed Agreement, and that requiring Vantage to terminate these relationships would be commercially unreasonable and potentially disruptive to Vantage's existing customer base.

Our preliminary recommendation is that BCS may agree to narrow the "Competing Product" definition to exclude SCADA-only analytics products that do not incorporate cloud-based IoT functionality, provided that the carve-out is defined with sufficient specificity to prevent Vantage from exploiting it as a loophole. The core competitive protection for the BrightEdge platform lies in its cloud-based IoT analytics capabilities, which are the primary differentiator from legacy SCADA-only analytics tools. A SCADA-only analytics product that does not incorporate cloud-based IoT data collection, edge computing, or machine learning capabilities does not present a meaningful competitive threat to BrightEdge and is not the type of product the non-compete provision is intended to address.

However, the carve-out should be drafted narrowly to ensure that it does not inadvertently permit Vantage to resell a nominally "SCADA-only" product that, through subsequent enhancements or feature additions, evolves into a cloud-based IoT platform that competes directly with BrightEdge. We recommend including a provision stating that if a product initially qualifying for the SCADA-only carve-out subsequently adds cloud-based IoT analytics, edge computing, or similar functionality, it shall be deemed a Competing Product from the date such functionality is added.

Further analysis of the "Competing Product" definition and the scope of the Section 12.2 non-compete will be provided as negotiations develop on this point and will be addressed in the separate negotiation issues memorandum.

D. Post-Initial-Term Considerations

The Limited Exclusivity Covenant applies only during the initial three-year term of the Agreement. Upon expiration of the initial term, the Agreement auto-renews for successive one-year periods unless either party gives not less than ninety (90) days' prior written notice of non-renewal prior to the expiration of the then-current term. During any renewal period, BCS has unrestricted rights to appoint additional OEM resellers in the industrial automation vertical within the Territory, unless the parties affirmatively renegotiate the Limited Exclusivity Covenant in connection with the renewal.

We recommend maintaining this structure as drafted. Limiting the exclusivity covenant to the initial three-year term protects BCS's long-term flexibility to expand its distribution network and respond to market developments. If the OEM reseller relationship with Vantage is commercially successful during the initial term, BCS may choose to offer a renewed or modified exclusivity covenant as part of a renegotiation of commercial terms. However, BCS should not commit to post-initial-term exclusivity at this stage, as doing so would constrain BCS's strategic options during a period when the BrightEdge platform may have achieved significantly greater market penetration and be in a position to support a broader network of OEM reseller partners.

VI. SOURCE CODE ESCROW — THREE-PARTY AGREEMENT WITH PINNACLE ESCROW SERVICES, INC.

A. Structure and Parties

The proposed Agreement contemplates a three-party source code escrow arrangement to be formalized in a separate escrow agreement and annexed as Exhibit E to the OEM Reseller Agreement. The parties to the escrow agreement are as follows:

• Depositor: Brightfield Cloud Services Inc.

• Beneficiary: Vantage Industrial Solutions, LLC

• Escrow Agent: Pinnacle Escrow Services, Inc., located at 2300 Clarendon Boulevard, Suite 410, Arlington, Virginia 22201 (the "Escrow Agent"). The account will be managed by Rafael Dominguez, an account manager at Pinnacle Escrow Services.

The escrow agreement will be governed by Delaware law, consistent with the governing law provision of the OEM Reseller Agreement. This ensures that any disputes arising under the escrow agreement and any disputes arising under the OEM Reseller Agreement are subject to the same substantive law, avoiding potential conflicts-of-law issues.

The purpose of the source code escrow is to provide Vantage with a contingent right to access the BrightEdge platform source code in the event that BCS is unable or unwilling to continue maintaining and supporting the software. The escrow arrangement is a standard feature of technology licensing agreements where the licensee's business operations are dependent on the continued availability and maintenance of the licensor's proprietary software. However, the escrow is not intended to — and must not — serve as a mechanism for Vantage to obtain unrestricted access to BCS's most valuable proprietary technology. Accordingly, the release conditions and use restrictions must be drafted with care.

B. Deposited Materials

The materials to be deposited into escrow (the "Deposited Materials") must be sufficiently comprehensive to enable a reasonably skilled developer to compile, deploy, and maintain the BrightEdge platform software. We recommend that the Deposited Materials include the following:

• Complete source code for the BrightEdge platform, version 4.2, including all modules, libraries, components, and dependencies;

• Build instructions and compilation procedures, including the identification of all required development environments, compilers, linkers, and build tools;

• Compilation tools and scripts necessary to build the software from source code;

• Third-party libraries and open-source components incorporated into the BrightEdge platform, to the extent such libraries are distributable under their respective license terms (and identification of any third-party components that cannot be deposited due to license restrictions, together with information sufficient to obtain such components from their respective sources);

• Database schemas, migration scripts, and data architecture documentation;

• API documentation, integration guides, and technical reference manuals;

• System architecture documentation, including network diagrams, deployment configurations, and infrastructure requirements; and

• Such other documentation as would be reasonably necessary for a developer of reasonable skill and experience in IoT platform software development to compile, deploy, configure, maintain, and support the BrightEdge platform without assistance from BCS.

BCS should be obligated to deposit subsequent updates and new versions of the BrightEdge platform source code during the term of the Agreement. We recommend that the Agreement specify that BCS must deposit updated source code within thirty (30) days following each major version release (e.g., version 4.3, 5.0, etc.) and within sixty (60) days following each minor version release or patch that includes material changes to the source code.

Verification. We recommend specifying a verification process under which the Escrow Agent periodically verifies the completeness and integrity of the Deposited Materials. Verification procedures are available through most established escrow agents, including Pinnacle Escrow Services, and typically involve an independent technical review to confirm that the deposited source code can be successfully compiled and that the accompanying documentation is complete. We recommend that a full verification be conducted (a) upon the initial deposit of the version 4.2 source code, and (b) annually thereafter or upon each subsequent deposit, whichever occurs more frequently. The costs associated with verification services should be shared equally between BCS and Vantage, as discussed in Section VI.F below.

C. Release Conditions — Current Draft

Under the current draft of the escrow agreement, the source code will be released to Vantage only upon the occurrence of one of three specified triggering events. The release conditions are designed to protect Vantage against the risk that BCS becomes unable or unwilling to maintain the BrightEdge platform, while preserving BCS's proprietary rights in all other circumstances. The three release triggers, and our analysis of each, are set forth below.

(a) Cessation of Business Operations. The first release trigger is the cessation of BCS's business operations. This is a standard escrow release condition that is widely used in technology escrow agreements and is generally enforceable under Delaware law.

We recommend that the term "ceases business operations" be defined with precision to avoid triggering a release in circumstances that do not reflect BCS's inability to maintain the BrightEdge platform. Specifically, the definition should exclude the following:

• Temporary shutdowns or suspensions of operations due to force majeure events, natural disasters, public health emergencies, or other circumstances beyond BCS's reasonable control;

• Planned or temporary office closures, facility relocations, or operational transitions that do not reflect a permanent cessation of BCS's business;

• Transfers of BCS's business (or substantially all of its assets) as a going concern to an acquirer or successor entity that assumes BCS's obligations under the OEM Reseller Agreement; and

• Changes in BCS's corporate structure (e.g., conversions, mergers, or reorganizations) that do not result in a permanent cessation of the business operations related to the BrightEdge platform.

The exclusion for transfers as a going concern is particularly important, as it prevents Vantage from obtaining a source code release in connection with a sale, merger, or acquisition of BCS in which the acquiring entity continues to operate the BrightEdge business and assumes BCS's contractual obligations. Without this exclusion, a routine corporate transaction could inadvertently trigger a source code release — an outcome that is neither intended by the escrow arrangement nor justified by any operational failure.

(b) Bankruptcy Filing. The second release trigger is the filing of a bankruptcy petition by or against BCS, whether voluntary or involuntary. We recommend that the Agreement specify both voluntary and involuntary filings to avoid ambiguity. For involuntary filings, we further recommend specifying that the release is triggered only if the involuntary petition is not dismissed within sixty (60) days of filing, to prevent a spurious involuntary petition by a third party from triggering a release.

Enforceability Under the Bankruptcy Code. It is important to note a significant limitation on the enforceability of this release trigger. Section 365(e)(1) of the Bankruptcy Code (11 U.S.C. § 365(e)(1)) provides that ipso facto clauses — contractual provisions that condition the termination, modification, or forfeiture of contractual rights on the filing of a bankruptcy petition or the commencement of insolvency proceedings — are generally unenforceable in bankruptcy proceedings. To the extent the escrow release trigger is characterized as an ipso facto clause that effects a forfeiture of BCS's proprietary rights upon bankruptcy, a bankruptcy court could decline to enforce it.

However, technology licenses are afforded special protections under Section 365(n) of the Bankruptcy Code (11 U.S.C. § 365(n)). Section 365(n) provides that if a debtor-licensor rejects an executory contract that is a license of intellectual property (as defined in Section 101(35A) of the Bankruptcy Code), the licensee may elect to retain its rights under the license, including the right to the intellectual property as it existed at the time of the bankruptcy filing. Section 365(n) was enacted specifically to protect technology licensees from the risk that a debtor-licensor would reject the license agreement in bankruptcy and deprive the licensee of access to critical technology.

Practical Analysis. The escrow release trigger for bankruptcy may be partially redundant given the Section 365(n) protections available to Vantage as a licensee of intellectual property. If BCS were to file for bankruptcy and reject the OEM Reseller Agreement, Vantage could invoke Section 365(n) to retain its license rights to the BrightEdge platform. Nonetheless, the escrow provides an additional layer of protection by ensuring that Vantage can obtain access to the actual source code, build tools, and documentation necessary to compile and maintain the software — protections that Section 365(n) does not independently guarantee. Accordingly, we recommend retaining the bankruptcy filing trigger in the escrow agreement, while acknowledging to BCS that its enforceability is subject to bankruptcy court oversight and may be limited by the Bankruptcy Code's prohibition on ipso facto clauses.

(c) Material Failure to Maintain or Support (120 Consecutive Days). The third release trigger is BCS's material failure to maintain or support the BrightEdge platform software for a period of more than 120 consecutive days after written notice from Vantage specifying the nature of the failure.

This trigger provides the most practically significant protection for Vantage, as it addresses the scenario in which BCS is still in existence and not in bankruptcy but has nevertheless failed to fulfill its ongoing maintenance and support obligations under the Agreement. The 120-consecutive-day cure period is a substantial period — significantly more generous to BCS than the typical sixty-to-ninety-day cure period commonly seen in industry-standard source code escrow agreements. The extended cure period reflects the negotiated balance between Vantage's interest in obtaining a remedy for BCS's non-performance and BCS's interest in having a meaningful opportunity to cure any maintenance or support deficiency.

The requirement for written notice from Vantage creates an additional procedural prerequisite. Under the current drafting, the 120-day clock does not begin to run until Vantage delivers written notice to BCS specifying the nature of the material failure. When the time required for Vantage to identify the failure, prepare and deliver written notice, and the escrow agent's processing time following expiration of the 120-day period are taken into account, the total elapsed time from the onset of the failure to the actual release of source code could be substantially longer than 120 days. This extended timeline provides BCS with a significant window in which to cure any deficiency and avoid the release of source code.

We recommend that the term "materially fails to maintain or support" be defined with specificity. Rather than leaving this term undefined and subject to dispute, the Agreement should cross-reference the specific maintenance and support obligations set forth in the OEM Reseller Agreement (which we anticipate will be detailed in Section 7 or a related exhibit, such as a Service Level Agreement). This cross-reference ensures that both parties — and the Escrow Agent — can readily determine whether the maintenance failure trigger has been satisfied.

Recommendation. BCS's position on the 120-day threshold is favorable and should be maintained. We should anticipate that Vantage may attempt to shorten this period to sixty (60) or ninety (90) days, consistent with shorter cure periods sometimes found in comparable agreements. We recommend resisting any such attempt, as the 120-day period appropriately balances the interests of both parties and provides BCS with a meaningful opportunity to cure.

D. Vantage's Proposed Additional Trigger: Change of Control of BCS

Based on discussions during the term sheet negotiations and preliminary communications with Vantage's counsel, we anticipate that Vantage will propose adding a "change of control of BCS" as a fourth release trigger in the source code escrow agreement. Specifically, Vantage is expected to seek a provision under which a change in the majority ownership or voting control of BCS would entitle Vantage to receive a release of the Deposited Materials from escrow.

We recommend that BCS firmly reject this proposal. Our analysis supporting this recommendation is set forth below.

(i) Commercial Rationale for Rejection. BCS is majority-owned by Veltrano Capital Partners Fund IV, L.P., which holds approximately 68% of BCS's equity. As a private equity-backed portfolio company, BCS operates within the context of a fund-level investment strategy that contemplates a finite investment horizon and a defined exit pathway. Veltrano Capital may pursue range exit strategies for its investment in BCS, including a sale to a strategic acquirer, a secondary buyout by another private equity sponsor, a recapitalization transaction, an initial public offering, or an add-on acquisition that alters the ownership structure of BCS. Each of these transaction types is a routine and legitimate corporate activity in the private equity context, and any of them could constitute a "change of control" under a broadly drafted definition.

A change-of-control trigger in the source code escrow agreement would effectively penalize BCS and Veltrano Capital for pursuing these legitimate corporate transactions by potentially releasing BCS's most valuable intellectual property asset — the BrightEdge platform source code — to a counterparty. The release of source code would occur not because of any operational failure, insolvency, or inability to perform on BCS's part, but solely because of a change in BCS's ownership structure. This result is fundamentally inconsistent with the purpose of source code escrow, which is to protect the beneficiary against the depositor's inability or unwillingness to maintain the deposited software.

Moreover, a change of control does not inherently affect BCS's ability or willingness to perform its maintenance and support obligations under the Agreement. A new owner or acquirer of BCS would have strong economic incentives to continue supporting and enhancing the BrightEdge platform, as the platform is BCS's primary revenue driver and the foundation of its enterprise value. The acquiring entity would also assume BCS's obligations under the OEM Reseller Agreement, either through operation of law (in the case of a merger or asset acquisition) or through contractual assignment. There is no rational basis for concluding that a change of control, standing alone, impairs the continued performance of BCS's contractual obligations.

(ii) Risk to BCS's IP Portfolio. The release of source code upon a change of control would grant Vantage access to BCS's proprietary code without any triggering operational failure or insolvency event. Once source code is in Vantage's possession — even subject to contractual use restrictions — it becomes practically difficult to monitor and enforce compliance with those restrictions. The risks include:

• Inadvertent Disclosure. Once source code is in Vantage's hands, there is a risk of inadvertent disclosure to Vantage employees, contractors, or third parties who do not have a need to access the code and who may not be bound by adequate confidentiality obligations.

• Competitive intelligence. Even if Vantage complies with the letter of the use restrictions, mere access to BCS's source code could provide Vantage with competitive intelligence regarding BCS's algorithmic approaches, architectural decisions, data processing methods, and proprietary techniques. This intelligence could inform Vantage's own product development efforts, even if Vantage does not directly copy or reproduce BCS's code.

• Enforcement Challenges. In the event of a suspected breach of the use restrictions, BCS would face significant practical challenges in detecting and proving unauthorized use. Source code analysis and "clean room" reverse-engineering techniques could make it difficult to establish that Vantage derived specific features or capabilities from BCS's proprietary code.

These risks are mitigated when source code release is triggered by a genuine operational failure or insolvency event, because in those circumstances the release serves a legitimate protective purpose and the equities favor granting Vantage access to the code. When release is triggered merely by a change of ownership, however, the risks are incurred without any corresponding protective justification.

(iii) Impact on BCS Valuation and M&A Flexibility. Veltrano Capital's investment thesis and exit strategy for BCS may involve a sale, merger, or initial public offering within Veltrano Capital's fund investment horizon, which typically ranges from four to seven years. A change-of-control escrow release trigger could be viewed by potential acquirers or IPO underwriters as a material encumbrance on BCS's intellectual property portfolio.

In M&A due diligence, potential acquirers routinely review the target company's material contracts, including technology license agreements and associated escrow arrangements. A change-of-control trigger that could result in the release of the target's core source code to a counterparty would likely be flagged as a significant risk factor. Acquirers may demand a purchase price reduction to account for this risk, require the elimination of the trigger as a condition to closing, or decline to pursue the acquisition altogether. In an IPO context, the change-of-control trigger could be flagged in risk factor disclosures and could complicate the offering process.

Accordingly, acceptance of the change-of-control trigger could reduce BCS's enterprise value, narrow the field of potential acquirers, and impair Veltrano Capital's ability to execute a successful exit from its investment.

(iv) Market Practice. While some beneficiaries in technology escrow arrangements do request change-of-control release triggers, this request is not standard market practice. Industry practice for technology escrow agreements more commonly limits release to operational failures (failure to maintain or support), insolvency events (bankruptcy, cessation of operations), and, in some cases, material breach of the underlying license agreement. A survey of representative technology escrow agreements in the enterprise software and IoT sectors indicates that change-of-control triggers are requested by beneficiaries in a minority of transactions and are more commonly associated with agreements where the beneficiary has significant bargaining leverage or where the depositor faces heightened insolvency risk.

BCS's position in rejecting the change-of-control trigger is consistent with market norms for licensor-favorable source code escrow agreements and is supported by the commercial rationale discussed above.

(v) Alternative Protections Available to Vantage. Vantage's concerns about continuity of the BrightEdge platform in the event of a change of control of BCS are not without some commercial legitimacy. However, Vantage is already well-protected by the existing release triggers and other contractual provisions in the Agreement:

(a) The operational failure trigger (120 consecutive days after written notice) provides Vantage with access to source code if any new owner of BCS fails to maintain and support the BrightEdge platform for an extended period. If a post-acquisition owner neglects the platform, this trigger ensures that Vantage is not left without recourse.

(b) The cessation of business trigger protects Vantage if BCS (or its successor) ceases business operations entirely.

(d) Section 365(n) of the Bankruptcy Code provides Vantage with independent statutory protections as a licensee of intellectual property, allowing Vantage to retain its license rights even if BCS rejects the Agreement in bankruptcy.

(e) The OEM Reseller Agreement's termination provisions, including termination for cause with a thirty-day cure period, provide Vantage with contractual remedies if a new owner of BCS fails to perform BCS's obligations under the Agreement.

Recommended Fallback Position. If Vantage insists on some form of protection related to a change of control, and rejection of the trigger becomes a significant impediment to closing the deal, we recommend offering enhanced notification and assumption provisions as an alternative to a release trigger. Spec

PRIVILEGED AND CONFIDENTIAL ATTORNEY-CLIENT PRIVILEGED ATTORNEY WORK PRODUCT
MEMORANDUM
FROM: Amy Chesterton, Associate, Calderwood & Harkness LLP
TO: Douglas Fairchild, Responsible Partner, Calderwood & Harkness LLP; Priya Narasimhan, General Counsel, Brightfield Cloud Services Inc.
DATE: January 3, 2026
RE: Analysis of intellectual Property Ownership, Trademark License, and Source Code Escrow Provisions — Proposed OEM Reseller Agreement between Brightfield Cloud Services Inc. and Vantage Industrial Solutions, LLC
ENGAGEMENT NO.: 1042-00005
Right-click to update Table of Contents
I. INTRODUCTION AND EXECUTIVE SUMMARY
The purpose of this memorandum is to analyze and advise on the intellectual property protections afforded to Brightfield Cloud Services Inc. ("BCS") in the proposed OEM Reseller Agreement (the "Agreement") with Vantage Industrial Solutions, LLC ("Vantage"). This memorandum addresses four principal areas: (1) intellectual property ownership provisions, (2) the scope and limitations of the trademark license, (3) the enforceability and scope of the Limited Exclusivity Covenant, and (4) the terms and conditions of the three-party source code escrow arrangement, including our analysis and recommendation regarding Vantage's proposed change-of-control release trigger. This memorandum does not address all negotiation points in the proposed Agreement; a separate negotiation issues memorandum will follow.
Background. BCS is a Delaware corporation headquartered at 4100 Esperanza Boulevard, Suite 800, Austin, Texas 78746. BCS is majority-owned (approximately 68% equity) by Veltrano Capital Partners Fund IV, L.P. ("Veltrano Capital"). BCS currently generates annual recurring revenue ("ARR") of approximately $62 million and employs approximately 320 individuals. BCS's core product is the "BrightEdge" IoT platform, which comprises cloud-hosted analytics software, embedded edge firmware, and proprietary sensor hardware modules. The BrightEdge platform is BCS's primary revenue driver and its most significant intellectual property asset.
Vantage is a Delaware limited liability company with its principal office located at 7755 Commerce Park Drive, Solon, Ohio 44139. Vantage designs, manufactures, and distributes programmable logic controllers ("PLCs"), SCADA interfaces, and industrial automation hardware. Vantage reported revenue of approximately $310 million for its fiscal year ended December 31, 2024, and currently employs approximately 1,200 individuals. Vantage is majority-owned by Harmon Family Holdings, LLC, with minority institutional holdings held by Velthorn Bridge Capital, LLC.
Proposed Transaction. The proposed Agreement contemplates an OEM reseller arrangement under which Vantage will embed BCS's proprietary BrightEdge IoT platform software and companion hardware modules into Vantage's product line and resell the combined solution to end-users in the United States and Canada (the "Territory"). The total deal value is $15,000,000, based on a Minimum Annual Commitment ("MAC") of $5,000,000 per year over a three-year initial term. The term sheet was signed on December 19, 2025, by Connor Whitfield, Vice President of Business Development at BCS, and Derek Yun, Vice President of Supply Chain & Procurement at Vantage. Calderwood & Harkness LLP is preparing the first draft of the OEM Reseller Agreement, which is scheduled for circulation on January 6, 2026.
Vantage is represented by Lattimore, Parish & Keene LLP, located in Cleveland, Ohio, with Thomas Ellsworth serving as lead partner and Jennifer Murata serving as the primary associate on the matter.
Summary of Key Conclusions. Based on the analysis set forth below, our principal conclusions and recommendations are as follows:
(1) IP Ownership Provisions. The intellectual property ownership provisions as currently contemplated are robust and should be maintained without concession. BCS should retain all right, title, and interest in the BrightEdge platform and all derivatives thereof. An express assignment clause covering any derivative works or improvements created by Vantage is critical and should not be negotiated away.
(2) Trademark License. The trademark license is appropriately limited in scope. It should be accompanied by comprehensive brand-use guidelines and quality control provisions sufficient to comply with the Lanham Act's requirements for trademark licensors. All goodwill generated through Vantage's use of BCS trademarks must inure to BCS's benefit.
(3) Limited Exclusivity Covenant. The Limited Exclusivity Covenant is enforceable under Delaware law given its narrow scope. However, the term "industrial automation vertical" should be defined with precision in the Agreement to avoid ambiguity and potential disputes over scope.
(4) Source Code Escrow. The source code escrow release conditions as currently drafted protect BCS's interests. The three specified release triggers — cessation of business operations, bankruptcy filing, and material failure to maintain or support the software for more than 120 consecutive days after written notice — are appropriate and favorable to BCS. Vantage's anticipated request to add a change-of-control trigger as a fourth release condition should be firmly rejected. A change-of-control trigger would penalize BCS and Veltrano Capital for legitimate corporate transactions, undermine the value of BCS's IP portfolio, and is not consistent with prevailing market practice for technology escrow agreements.
Each of these conclusions is discussed in detail below.
II. LICENSED TECHNOLOGY — SCOPE AND DESCRIPTION
A. Components of the BrightEdge IoT Platform
The Licensed Technology under the proposed Agreement comprises three distinct components, each of which implicates different IP ownership and licensing considerations:
(i) BrightEdge SaaS Subscription Software. The BrightEdge SaaS subscription software is a cloud-hosted analytics and dashboard platform that aggregates, processes, and displays IoT sensor data for end-users. This software is hosted on BCS's cloud infrastructure and accessed by end-users through a web-based interface. The SaaS component represents BCS's core recurring revenue stream, as end-users pay ongoing subscription fees for access to the platform's analytics capabilities. The software incorporates proprietary algorithms, data processing architectures, and machine learning models developed by BCS's engineering team.
(ii) BrightEdge Edge Firmware. The BrightEdge Edge Firmware is embedded software loaded onto BCS's proprietary hardware modules. The firmware enables on-device processing, data collection, and secure communication between the hardware modules and the cloud-hosted SaaS platform. The Edge Firmware is compiled from proprietary source code maintained by BCS and is integral to the functioning of the hardware modules. Because the firmware is embedded directly in hardware that will be physically distributed to Vantage's end-users, it presents unique risks related to reverse engineering and unauthorized modification.
(iii) BCS Model BE-400 and BE-600 Sensor Hardware Modules. The BCS Model BE-400 and Model BE-600 sensor hardware modules are proprietary IoT sensor devices designed and manufactured by BCS. The BE-400 is a compact sensor module priced at $185 per unit, and the BE-600 is an advanced multi-sensor module priced at $340 per unit. Both models are shipped FOB Austin, Texas, meaning that BCS controls the manufacturing process and supply chain, and title and risk of loss transfer to Vantage upon delivery to the carrier in Austin.
The software royalty under the proposed Agreement is set at 18% of Vantage's net resale price of the embedded SaaS subscription billed to each end-user, payable quarterly in arrears. This royalty structure ensures that BCS participates in the ongoing revenue generated by the BrightEdge platform even after the hardware modules are sold into the field. The BrightEdge platform is currently at version 4.2, and BCS's product roadmap anticipates material updates and new feature releases during the initial three-year term of the Agreement.
B. Significance of IP Protections Given the Nature of the Technology
The intellectual property protections discussed in this memorandum are of paramount importance given the nature of the BrightEdge platform and the structure of the proposed OEM reseller relationship. Several factors heighten the significance of these protections:
Core Asset Status. The BrightEdge platform is BCS's core asset and primary revenue driver. BCS's enterprise valuation, as assessed in connection with Veltrano Capital's initial investment, is substantially dependent on the proprietary nature and competitive differentiation of the BrightEdge technology. Any erosion of BCS's IP rights in the BrightEdge platform could materially diminish BCS's enterprise value and impair Veltrano Capital's anticipated return on its investment.
Co-Mingling Risk. The OEM reseller structure inherently creates a risk of co-mingling of intellectual property. Vantage will be embedding BCS's firmware and hardware modules into Vantage's own product line, creating a combined solution that incorporates both parties' technology. This integration work may require Vantage's engineers to interact with, modify, or create interfaces for BCS's firmware and software. Without clear IP ownership provisions and express assignment clauses, there is a risk that Vantage could assert ownership or joint-ownership claims over derivative works, modifications, or improvements arising from the integration process.
R&D Investment. BCS's proprietary algorithms, firmware architecture, and hardware designs represent substantial research and development investment accumulated over multiple product generations. BCS has invested significant engineering resources in developing the machine learning models, edge computing architectures, and secure communication protocols that differentiate the BrightEdge platform from competing IoT solutions in the market. Protection of this investment requires robust contractual safeguards against reverse engineering, decompilation, and independent exploitation by Vantage beyond the scope of the reseller relationship.
Enterprise IoT Market Dynamics. The enterprise IoT market is characterized by intense competition, rapid technological evolution, and high barriers to entry for providers of integrated hardware-software platforms. BCS's competitive advantage depends on the proprietary nature of the BrightEdge technology. If Vantage were to gain access to BCS's source code, hardware designs, or algorithmic methodologies outside the intended scope of the Agreement, the competitive harm to BCS could be severe and potentially irreversible.
For all of these reasons, the IP ownership, trademark license, and source code escrow provisions must be drafted with precision and maintained through negotiations without material concession.
III. INTELLECTUAL PROPERTY OWNERSHIP PROVISIONS
A. Retention of All Right, Title, and Interest
The cornerstone of the IP protections framework in the proposed Agreement is the unequivocal retention by BCS of all right, title, and interest in and to the BrightEdge platform. We recommend that the Agreement include an express statement along the following lines:
"As between the parties, BCS retains and shall retain all right, title, and interest in and to the Licensed Technology, including without limitation all software (including the BrightEdge SaaS subscription software and BrightEdge Edge Firmware), hardware designs, schematics, specifications, technical documentation, algorithms, data models, trademarks (including the 'BrightEdge' mark and the BCS logo), copyrights, patents, trade secrets, and all other intellectual property rights therein and thereto, together with all enhancements, modifications, derivative works, improvements, updates, and new versions thereof."
This provision should make clear that no transfer of ownership or assignment of any intellectual property rights to Vantage occurs under the Agreement. Vantage receives only a limited, non-exclusive license to use, distribute, and resell the Licensed Technology within the Territory as part of Vantage's combined product offering. The license is circumscribed by the terms and conditions of the Agreement, including the territorial limitation (United States and Canada), the product-specific scope (resale as part of Vantage's combined product line), and the temporal limitation (the term of the Agreement).
All enhancements, modifications, derivative works, improvements, updates, and new versions of the BrightEdge platform made by BCS during the term of the Agreement remain solely owned by BCS. This principle applies regardless of whether such enhancements or modifications are developed in response to feedback from Vantage, requests from Vantage's end-users, or BCS's own product development roadmap.
We further recommend that the Agreement include a negative covenant in which Vantage expressly acknowledges and agrees that it acquires no ownership interest in the Licensed Technology by virtue of the Agreement, and that it will not challenge or contest BCS's ownership of the Licensed Technology or the validity of BCS's intellectual property rights.
B. Derivative Works and Improvements Created by Vantage
One of the most significant risks in an OEM reseller arrangement of this nature is the potential for Vantage's integration work to give rise to derivative works of BCS's firmware or software. As Vantage's engineering team works to embed the BrightEdge platform into Vantage's product line, it is foreseeable that Vantage's engineers or contractors may create modifications, adaptations, interfaces, integration layers, or other works that incorporate or build upon BCS's proprietary code. Under U.S. copyright law, a derivative work is a work based upon one or more preexisting works, and the creator of a derivative work may acquire certain rights in the new expression contained in the derivative work — even if the underlying preexisting work remains owned by the original copyright holder.
To address this risk, we recommend that the Agreement include an express assignment clause requiring that any and all improvements, modifications, derivative works, adaptations, translations, interfaces, integration code, and other works created by Vantage, its employees, contractors, or agents in connection with or arising out of the Licensed Technology are automatically and irrevocably assigned to BCS upon their creation. The relevant provision should include language along the following lines:
"Vantage hereby irrevocably assigns and agrees to assign to BCS all right, title, and interest in and to any and all improvements, modifications, derivative works, adaptations, translations, and other works created by or on behalf of Vantage, its employees, contractors, or agents in connection with or arising out of the Licensed Technology, including all intellectual property rights therein. Such assignment shall be effective automatically upon creation of such works without the need for further action by either party."
Work-for-Hire Analysis. It is important to note that as Vantage is a limited liability company and not an employee of BCS, works created by Vantage's personnel may not automatically qualify as "works made for hire" under Section 101 of the Copyright Act (17 U.S.C. § 101). The work-for-hire doctrine generally applies to works created by employees within the scope of their employment or to certain categories of commissioned works where the parties have expressly agreed in a signed writing that the work is a work made for hire. Because Vantage is an independent contractor rather than an employee of BCS, and because the categories of commissioned works eligible for work-for-hire status under the Copyright Act are limited, we cannot rely on the work-for-hire doctrine alone to vest ownership of Vantage-created derivative works in BCS. Express assignment language is therefore critical and must be included in the Agreement.
Confirmatory Assignment and Cooperation. In addition to the automatic assignment provision, we recommend including a confirmatory assignment obligation and a cooperation clause. The confirmatory assignment obligation would require Vantage, upon request by BCS, to execute and deliver any documents or instruments reasonably necessary to confirm, perfect, or record BCS's ownership of assigned works. The cooperation clause would obligate Vantage to cooperate with BCS in connection with any patent, copyright, or other intellectual property applications or registrations related to assigned works, at BCS's cost and expense. We further recommend including a limited power of attorney, irrevocable and coupled with an interest, authorizing BCS to execute documents on Vantage's behalf if Vantage fails or refuses to do so within a reasonable period after request.
C. Hardware Design Ownership
BCS's proprietary hardware module designs present a separate category of intellectual property requiring explicit protection. The BE-400 and BE-600 sensor hardware module designs, including all schematics, specifications, manufacturing processes, bill of materials, component selections, circuit board layouts, and related technical documentation, must be expressly identified as BCS's exclusive property. The Agreement should include a specific prohibition against Vantage manufacturing, reverse-engineering, disassembling, or creating substantially similar hardware modules. This prohibition should extend to Vantage's affiliates, contractors, and any third parties acting on Vantage's behalf.
The FOB Austin, Texas shipping terms for hardware module deliveries reinforce BCS's control over the manufacturing process and supply chain. Under these terms, BCS manufactures the hardware modules at its Austin facility (or through its designated contract manufacturers), and title and risk of loss transfer to Vantage upon delivery to the carrier at BCS's shipping point. This structure ensures that Vantage does not gain access to BCS's manufacturing processes, supply chain relationships, or contract manufacturer identities. We recommend that the Agreement expressly state that the FOB shipping terms do not create any implied license or right for Vantage to manufacture or have manufactured any hardware modules or substantially similar devices.
Additionally, because the BE-400 and BE-600 modules contain embedded firmware (the BrightEdge Edge Firmware), the hardware design ownership provisions and the software IP ownership provisions should be drafted in a coordinated manner to ensure comprehensive protection of both the hardware and the embedded software components.
D. Feedback and Suggestions
It is common in OEM reseller relationships for the reseller and its end-users to provide feedback, suggestions, feature requests, bug reports, and other input regarding the licensed technology. Such feedback may contain valuable insights that inform the licensor's product development roadmap. However, if not properly addressed in the Agreement, feedback could create ambiguity regarding ownership rights — particularly if Vantage later claims that a BCS product enhancement was derived from Vantage's feedback and therefore constitutes a jointly owned work.
We recommend that the Agreement include a clear provision addressing the treatment of feedback, substantially as follows:
"Vantage hereby grants to BCS a perpetual, irrevocable, worldwide, royalty-free, fully paid-up, non-exclusive license to use, reproduce, modify, create derivative works based upon, distribute, and otherwise exploit any feedback, suggestions, ideas, enhancement requests, or other input provided by Vantage or its end-users regarding the Licensed Technology, without compensation, attribution, or any other obligation to Vantage. BCS shall be the sole and exclusive owner of any improvements, enhancements, or modifications to the Licensed Technology made by BCS, whether or not informed by or incorporating feedback received from Vantage."
This approach — granting BCS a broad license to feedback rather than relying solely on assignment — is recommended because assignment of "ideas" and "suggestions" that have not been reduced to a copyrightable or patentable form presents enforceability challenges. The combination of a broad feedback license and the derivative works assignment clause discussed in Section III.B above provides comprehensive coverage.
IV. TRADEMARK LICENSE — SCOPE AND LIMITATIONS
A. Grant of Trademark License
Under the proposed Agreement, BCS will grant Vantage a limited, non-transferable, royalty-free license to use BCS's trademarks, including the "BrightEdge" word mark and the BCS logo (collectively, the "BCS Marks"), solely in connection with the marketing, promotion, distribution, and resale of the Licensed Technology within the Territory. The key attributes of the trademark license are as follows:
• Scope: The license is limited to use of the BCS Marks solely in connection with the marketing and resale of the Licensed Technology as embedded in Vantage's combined product offering. The license does not extend to use of the BCS Marks in connection with any other Vantage product, service, or activity.
• Territory: The license is limited to the United States and Canada, consistent with the territorial scope of the OEM Reseller Agreement.
• Exclusivity: The trademark license is non-exclusive. BCS retains the right to use the BCS Marks in any manner and to grant trademark licenses to other parties.
• Transferability: The license is non-transferable and non-sublicensable. Vantage may not assign, sublicense, or otherwise transfer the trademark license to any third party without BCS's prior written consent, which BCS may withhold in its sole discretion.
• Royalty: The trademark license is royalty-free. No separate royalty or license fee is charged for Vantage's use of the BCS Marks; the consideration for the trademark license is subsumed within the overall commercial arrangement under the Agreement.
• Term: The trademark license terminates automatically and without further action upon termination or expiration of the OEM Reseller Agreement, regardless of the reason for such termination or expiration. Upon termination of the trademark license, Vantage must immediately cease all use of the BCS Marks and destroy or return all materials bearing the BCS Marks.
B. Brand-Use Guidelines (Exhibit D)
Vantage's use of the BCS Marks will be subject to compliance with BCS's comprehensive brand-use guidelines, which will be set forth in Exhibit D to the Agreement. The brand-use guidelines are a critical component of the trademark license, as they establish the parameters within which Vantage may use the BCS Marks and provide the framework for BCS's quality control obligations as trademark licensor.
We recommend that Exhibit D address, at a minimum, the following topics:
• Approved logo formats, including vector files and raster images at specified resolutions;
• Placement specifications for the BCS Marks on Vantage's product packaging, product labels, user interfaces, and marketing materials;
• Minimum sizing requirements to ensure legibility and brand visibility;
• Color standards, including approved color palettes (specified by Pantone, CMYK, and RGB values) and restrictions on the use of alternative colors;
• Prohibited modifications, including prohibitions on altering, distorting, animating, or combining the BCS Marks with other marks or design elements without BCS's express written approval;
• Co-branding requirements, specifying how the BCS Marks must be displayed in conjunction with Vantage's own trademarks and trade dress;
• Trademark attribution requirements, including the use of appropriate trademark symbols (® or ™) and ownership attribution statements;
• Approved and prohibited uses in digital media, including website displays, social media, online advertising, and email marketing; and
• The approval workflow for marketing materials, as discussed below.
Pre-Approval Requirement. BCS should retain the right to review and approve all marketing and promotional materials incorporating the BCS Marks prior to their publication, distribution, or dissemination by Vantage. We recommend that the Agreement specify a defined approval and response period — we recommend ten (10) business days from BCS's receipt of the materials for review. If BCS does not respond within the approval period, the materials should be deemed not approved (i.e., silence should not constitute consent). This approach ensures that BCS maintains active oversight of how its marks are used in the marketplace.
Updates to Brand-Use Guidelines. BCS should retain the unilateral right to update, amend, and supplement the brand-use guidelines from time to time during the term of the Agreement. We recommend that BCS be required to provide Vantage with reasonable advance written notice of any material changes to the brand-use guidelines — we suggest not less than thirty (30) days' prior written notice — and that Vantage be required to bring its use of the BCS Marks into compliance with the updated guidelines within a reasonable transition period, which we suggest be sixty (60) days from the effective date of the updated guidelines.
C. Quality Control
Under the Lanham Act (15 U.S.C. § 1055), a trademark licensor has an affirmative obligation to exercise adequate quality control over the goods and services offered by the licensee under the licensed marks. Failure to exercise quality control may result in a finding of "naked licensing," which can lead to a determination that the licensor has abandoned the mark. See, e.g., Barcamerica Int'l USA Trust v. Tyfield Imps., Inc., 289 F.3d 589, 596 (9th Cir. 2002) (holding that the absence of quality control provisions in a trademark license constituted naked licensing); Eva's Bridal Ltd. v. Halanick Enters., Inc., 639 F.3d 788, 790 (7th Cir. 2011) (Posner, J.) (discussing the naked licensing doctrine). While naked licensing defenses are most commonly raised in trademark infringement disputes, the risk of abandonment is a real concern that must be addressed proactively in the Agreement.
We recommend the following quality control provisions:
(a) Inspection and Testing Rights. BCS shall have the right, upon reasonable advance notice, to inspect and test Vantage's combined product offering at any time during the term of the Agreement to ensure that the BrightEdge components meet BCS's quality standards. Inspections may include review of product packaging, marketing materials, product documentation, and the user experience associated with Vantage's integration of the BrightEdge platform.
(b) Compliance Standards. Vantage shall ensure that the combined product offering incorporating the BrightEdge platform meets or exceeds the quality standards specified by BCS, including technical performance standards, user interface standards, customer support standards, and any other standards BCS may reasonably establish from time to time.
(c) Suspension and Termination. BCS shall have the right to suspend or terminate the trademark license, effective immediately upon written notice, if Vantage's use of the BCS Marks materially deviates from the brand-use guidelines set forth in Exhibit D or if Vantage's combined product offering fails to meet BCS's quality standards in a manner that negatively impacts the goodwill associated with the BCS Marks. The suspension or termination of the trademark license shall not, by itself, constitute a termination of the OEM Reseller Agreement, although it may give rise to a right to terminate the Agreement for cause if uncured.
(d) Goodwill. All goodwill generated through Vantage's use of the BCS Marks shall inure solely and exclusively to the benefit of BCS. Vantage acknowledges that it acquires no rights in the BCS Marks by virtue of its use thereof, and that all such use is on behalf of and for the benefit of BCS.
D. Trademark Enforcement
The Agreement should clearly allocate trademark enforcement rights and obligations between the parties. We recommend the following provisions:
BCS retains the sole and exclusive right to enforce its trademarks against third-party infringers, including the right to initiate, conduct, settle, and control any legal proceedings or other enforcement actions relating to the BCS Marks. Vantage has no independent right to bring infringement actions, send cease-and-desist communications, or otherwise enforce the BCS Marks against third parties, unless specifically authorized by BCS in writing.
Vantage should be obligated to promptly notify BCS of any known or suspected infringement, dilution, or unauthorized use of the BCS Marks that comes to Vantage's attention, including any use by third parties that is confusingly similar to the BCS Marks. Such notification should be provided in writing within ten (10) business days of Vantage becoming aware of the potentially infringing activity. Vantage should further be obligated to cooperate with BCS, at BCS's cost and expense, in connection with any enforcement actions BCS may elect to pursue.
This allocation of enforcement rights is standard in trademark license agreements and is consistent with BCS's retention of all goodwill and ownership rights in the BCS Marks.
V. LIMITED EXCLUSIVITY COVENANT
A. Structure of the Covenant
The proposed Agreement is structured as a non-exclusive OEM reseller arrangement — BCS retains the right to appoint additional OEM resellers and to sell the BrightEdge platform through other channels. However, as a concession negotiated in the term sheet, BCS has agreed to a Limited Exclusivity Covenant under which BCS will not appoint more than four (4) additional OEM resellers in the "industrial automation vertical" within the Territory (United States and Canada) during the initial three-year term of the Agreement (anticipated to run from February 20, 2026 through February 19, 2029).
Under this structure, the total number of OEM resellers permitted in the industrial automation vertical within the Territory during the initial term is capped at five (5): Vantage, plus up to four (4) additional resellers appointed by BCS. This numerical cap provides Vantage with a degree of competitive protection — limiting the number of competing OEM resellers carrying the BrightEdge platform in the same vertical — while preserving BCS's ability to diversify its distribution channels and avoid overdependence on a single reseller partner.
The Limited Exclusivity Covenant does not restrict BCS's ability to sell the BrightEdge platform directly to end-users, to license the BrightEdge platform to OEM resellers outside the industrial automation vertical, or to license the platform to resellers outside the Territory.
B. Enforceability Analysis
The OEM Reseller Agreement will be governed by Delaware law. Delaware courts generally enforce reasonable restrictive covenants in commercial agreements between sophisticated parties, applying a standard of reasonableness that considers the scope, duration, and geographic reach of the restriction. See Kan-Di-Ki, LLC v. Susi, 2015 WL 4503210, at *12 (Del. Ch. July 22, 2015) (discussing enforceability of restrictive covenants in commercial contracts under Delaware law).
The Limited Exclusivity Covenant is narrowly tailored across three dimensions:
• Vertical Scope: The covenant is limited to the "industrial automation vertical" and does not restrict BCS's ability to appoint OEM resellers in other verticals (e.g., healthcare, smart building, logistics, energy, etc.).
• Territorial Scope: The covenant applies only within the United States and Canada and does not restrict BCS's activities in any other geographic market.
• Temporal Scope: The covenant applies only during the initial three-year term of the Agreement and does not extend to any renewal periods unless the parties affirmatively renegotiate.
Furthermore, the covenant is a practical limitation rather than an absolute exclusivity. BCS is permitted to appoint up to four additional OEM resellers in the industrial automation vertical during the initial term, meaning that the industrial automation market in the Territory is not reserved solely for Vantage. This structure significantly reduces the risk of anticompetitive challenges under federal or state competition laws, as Vantage does not receive the kind of absolute territorial or vertical exclusivity that might raise concerns under the Sherman Act or analogous state statutes.
It is also important to distinguish this commercial covenant from an employee non-compete agreement. Employee non-competes are subject to heightened scrutiny under the laws of many states, including recent regulatory activity by the Federal Trade Commission. The Limited Exclusivity Covenant, by contrast, is a commercial restriction negotiated at arm's length between two sophisticated business entities, and it is subject to a more permissive standard of review. Delaware courts have consistently recognized the distinction between employee non-competes and commercial restrictive covenants, applying a less exacting reasonableness analysis to the latter.
Risk Assessment. We assess the risk of unenforceability of the Limited Exclusivity Covenant as low, given its narrow scope, defined duration, and limited territorial reach. However, we recommend that the term "industrial automation vertical" be defined with precision in the Agreement to avoid ambiguity and potential disputes over scope. A vague or overly broad definition could create uncertainty regarding which OEM reseller appointments by BCS would violate the covenant, potentially leading to costly disputes. We recommend a definition along the following lines:
"Industrial Automation Vertical" means the market for products and services used in the automated control, monitoring, and optimization of industrial manufacturing processes, industrial equipment operations, and industrial facility management, including without limitation programmable logic controllers, SCADA systems, distributed control systems, human-machine interfaces, industrial robotics, and industrial IoT sensor networks, but excluding building automation systems, healthcare monitoring systems, logistics and supply chain management systems, and consumer IoT products.
This definition should be reviewed and approved by BCS's business team to ensure alignment with BCS's commercial strategy and market segmentation.
C. Interplay with Non-Compete Provision (Section 12.2)
Separate from the Limited Exclusivity Covenant (which restricts BCS's ability to appoint additional resellers), Section 12.2 of the proposed Agreement contains a non-compete provision restricting Vantage from distributing, reselling, or otherwise offering a "Competing Product" during the term of the Agreement and for a specified period following termination. The non-compete provision runs in the opposite direction from the Limited Exclusivity Covenant — it restricts Vantage, not BCS — and is designed to ensure that Vantage does not undermine the commercial relationship by simultaneously reselling a competing IoT platform alongside the BrightEdge platform.
The definition of "Competing Product" is currently an open negotiation point. Vantage, through its counsel at Lattimore, Parish & Keene LLP, has requested that the definition be narrowed to exclude legacy SCADA-only analytics products that do not incorporate cloud-based IoT functionality. Vantage's position is that its existing relationships with certain SCADA analytics vendors predate the proposed Agreement, and that requiring Vantage to terminate these relationships would be commercially unreasonable and potentially disruptive to Vantage's existing customer base.
Our preliminary recommendation is that BCS may agree to narrow the "Competing Product" definition to exclude SCADA-only analytics products that do not incorporate cloud-based IoT functionality, provided that the carve-out is defined with sufficient specificity to prevent Vantage from exploiting it as a loophole. The core competitive protection for the BrightEdge platform lies in its cloud-based IoT analytics capabilities, which are the primary differentiator from legacy SCADA-only analytics tools. A SCADA-only analytics product that does not incorporate cloud-based IoT data collection, edge computing, or machine learning capabilities does not present a meaningful competitive threat to BrightEdge and is not the type of product the non-compete provision is intended to address.
However, the carve-out should be drafted narrowly to ensure that it does not inadvertently permit Vantage to resell a nominally "SCADA-only" product that, through subsequent enhancements or feature additions, evolves into a cloud-based IoT platform that competes directly with BrightEdge. We recommend including a provision stating that if a product initially qualifying for the SCADA-only carve-out subsequently adds cloud-based IoT analytics, edge computing, or similar functionality, it shall be deemed a Competing Product from the date such functionality is added.
Further analysis of the "Competing Product" definition and the scope of the Section 12.2 non-compete will be provided as negotiations develop on this point and will be addressed in the separate negotiation issues memorandum.
D. Post-Initial-Term Considerations
The Limited Exclusivity Covenant applies only during the initial three-year term of the Agreement. Upon expiration of the initial term, the Agreement auto-renews for successive one-year periods unless either party gives not less than ninety (90) days' prior written notice of non-renewal prior to the expiration of the then-current term. During any renewal period, BCS has unrestricted rights to appoint additional OEM resellers in the industrial automation vertical within the Territory, unless the parties affirmatively renegotiate the Limited Exclusivity Covenant in connection with the renewal.
We recommend maintaining this structure as drafted. Limiting the exclusivity covenant to the initial three-year term protects BCS's long-term flexibility to expand its distribution network and respond to market developments. If the OEM reseller relationship with Vantage is commercially successful during the initial term, BCS may choose to offer a renewed or modified exclusivity covenant as part of a renegotiation of commercial terms. However, BCS should not commit to post-initial-term exclusivity at this stage, as doing so would constrain BCS's strategic options during a period when the BrightEdge platform may have achieved significantly greater market penetration and be in a position to support a broader network of OEM reseller partners.
VI. SOURCE CODE ESCROW — THREE-PARTY AGREEMENT WITH PINNACLE ESCROW SERVICES, INC.
A. Structure and Parties
The proposed Agreement contemplates a three-party source code escrow arrangement to be formalized in a separate escrow agreement and annexed as Exhibit E to the OEM Reseller Agreement. The parties to the escrow agreement are as follows:
• Depositor: Brightfield Cloud Services Inc.
• Beneficiary: Vantage Industrial Solutions, LLC
• Escrow Agent: Pinnacle Escrow Services, Inc., located at 2300 Clarendon Boulevard, Suite 410, Arlington, Virginia 22201 (the "Escrow Agent"). The account will be managed by Rafael Dominguez, an account manager at Pinnacle Escrow Services.
The escrow agreement will be governed by Delaware law, consistent with the governing law provision of the OEM Reseller Agreement. This ensures that any disputes arising under the escrow agreement and any disputes arising under the OEM Reseller Agreement are subject to the same substantive law, avoiding potential conflicts-of-law issues.
The purpose of the source code escrow is to provide Vantage with a contingent right to access the BrightEdge platform source code in the event that BCS is unable or unwilling to continue maintaining and supporting the software. The escrow arrangement is a standard feature of technology licensing agreements where the licensee's business operations are dependent on the continued availability and maintenance of the licensor's proprietary software. However, the escrow is not intended to — and must not — serve as a mechanism for Vantage to obtain unrestricted access to BCS's most valuable proprietary technology. Accordingly, the release conditions and use restrictions must be drafted with care.
B. Deposited Materials
The materials to be deposited into escrow (the "Deposited Materials") must be sufficiently comprehensive to enable a reasonably skilled developer to compile, deploy, and maintain the BrightEdge platform software. We recommend that the Deposited Materials include the following:
• Complete source code for the BrightEdge platform, version 4.2, including all modules, libraries, components, and dependencies;
• Build instructions and compilation procedures, including the identification of all required development environments, compilers, linkers, and build tools;
• Compilation tools and scripts necessary to build the software from source code;
• Third-party libraries and open-source components incorporated into the BrightEdge platform, to the extent such libraries are distributable under their respective license terms (and identification of any third-party components that cannot be deposited due to license restrictions, together with information sufficient to obtain such components from their respective sources);
• Database schemas, migration scripts, and data architecture documentation;
• API documentation, integration guides, and technical reference manuals;
• System architecture documentation, including network diagrams, deployment configurations, and infrastructure requirements; and
• Such other documentation as would be reasonably necessary for a developer of reasonable skill and experience in IoT platform software development to compile, deploy, configure, maintain, and support the BrightEdge platform without assistance from BCS.
BCS should be obligated to deposit subsequent updates and new versions of the BrightEdge platform source code during the term of the Agreement. We recommend that the Agreement specify that BCS must deposit updated source code within thirty (30) days following each major version release (e.g., version 4.3, 5.0, etc.) and within sixty (60) days following each minor version release or patch that includes material changes to the source code.
Verification. We recommend specifying a verification process under which the Escrow Agent periodically verifies the completeness and integrity of the Deposited Materials. Verification procedures are available through most established escrow agents, including Pinnacle Escrow Services, and typically involve an independent technical review to confirm that the deposited source code can be successfully compiled and that the accompanying documentation is complete. We recommend that a full verification be conducted (a) upon the initial deposit of the version 4.2 source code, and (b) annually thereafter or upon each subsequent deposit, whichever occurs more frequently. The costs associated with verification services should be shared equally between BCS and Vantage, as discussed in Section VI.F below.
C. Release Conditions — Current Draft
Under the current draft of the escrow agreement, the source code will be released to Vantage only upon the occurrence of one of three specified triggering events. The release conditions are designed to protect Vantage against the risk that BCS becomes unable or unwilling to maintain the BrightEdge platform, while preserving BCS's proprietary rights in all other circumstances. The three release triggers, and our analysis of each, are set forth below.
(a) Cessation of Business Operations. The first release trigger is the cessation of BCS's business operations. This is a standard escrow release condition that is widely used in technology escrow agreements and is generally enforceable under Delaware law.
We recommend that the term "ceases business operations" be defined with precision to avoid triggering a release in circumstances that do not reflect BCS's inability to maintain the BrightEdge platform. Specifically, the definition should exclude the following:
• Temporary shutdowns or suspensions of operations due to force majeure events, natural disasters, public health emergencies, or other circumstances beyond BCS's reasonable control;
• Planned or temporary office closures, facility relocations, or operational transitions that do not reflect a permanent cessation of BCS's business;
• Transfers of BCS's business (or substantially all of its assets) as a going concern to an acquirer or successor entity that assumes BCS's obligations under the OEM Reseller Agreement; and
• Changes in BCS's corporate structure (e.g., conversions, mergers, or reorganizations) that do not result in a permanent cessation of the business operations related to the BrightEdge platform.
The exclusion for transfers as a going concern is particularly important, as it prevents Vantage from obtaining a source code release in connection with a sale, merger, or acquisition of BCS in which the acquiring entity continues to operate the BrightEdge business and assumes BCS's contractual obligations. Without this exclusion, a routine corporate transaction could inadvertently trigger a source code release — an outcome that is neither intended by the escrow arrangement nor justified by any operational failure.
(b) Bankruptcy Filing. The second release trigger is the filing of a bankruptcy petition by or against BCS, whether voluntary or involuntary. We recommend that the Agreement specify both voluntary and involuntary filings to avoid ambiguity. For involuntary filings, we further recommend specifying that the release is triggered only if the involuntary petition is not dismissed within sixty (60) days of filing, to prevent a spurious involuntary petition by a third party from triggering a release.
Enforceability Under the Bankruptcy Code. It is important to note a significant limitation on the enforceability of this release trigger. Section 365(e)(1) of the Bankruptcy Code (11 U.S.C. § 365(e)(1)) provides that ipso facto clauses — contractual provisions that condition the termination, modification, or forfeiture of contractual rights on the filing of a bankruptcy petition or the commencement of insolvency proceedings — are generally unenforceable in bankruptcy proceedings. To the extent the escrow release trigger is characterized as an ipso facto clause that effects a forfeiture of BCS's proprietary rights upon bankruptcy, a bankruptcy court could decline to enforce it.
However, technology licenses are afforded special protections under Section 365(n) of the Bankruptcy Code (11 U.S.C. § 365(n)). Section 365(n) provides that if a debtor-licensor rejects an executory contract that is a license of intellectual property (as defined in Section 101(35A) of the Bankruptcy Code), the licensee may elect to retain its rights under the license, including the right to the intellectual property as it existed at the time of the bankruptcy filing. Section 365(n) was enacted specifically to protect technology licensees from the risk that a debtor-licensor would reject the license agreement in bankruptcy and deprive the licensee of access to critical technology.
Practical Analysis. The escrow release trigger for bankruptcy may be partially redundant given the Section 365(n) protections available to Vantage as a licensee of intellectual property. If BCS were to file for bankruptcy and reject the OEM Reseller Agreement, Vantage could invoke Section 365(n) to retain its license rights to the BrightEdge platform. Nonetheless, the escrow provides an additional layer of protection by ensuring that Vantage can obtain access to the actual source code, build tools, and documentation necessary to compile and maintain the software — protections that Section 365(n) does not independently guarantee. Accordingly, we recommend retaining the bankruptcy filing trigger in the escrow agreement, while acknowledging to BCS that its enforceability is subject to bankruptcy court oversight and may be limited by the Bankruptcy Code's prohibition on ipso facto clauses.
(c) Material Failure to Maintain or Support (120 Consecutive Days). The third release trigger is BCS's material failure to maintain or support the BrightEdge platform software for a period of more than 120 consecutive days after written notice from Vantage specifying the nature of the failure.
This trigger provides the most practically significant protection for Vantage, as it addresses the scenario in which BCS is still in existence and not in bankruptcy but has nevertheless failed to fulfill its ongoing maintenance and support obligations under the Agreement. The 120-consecutive-day cure period is a substantial period — significantly more generous to BCS than the typical sixty-to-ninety-day cure period commonly seen in industry-standard source code escrow agreements. The extended cure period reflects the negotiated balance between Vantage's interest in obtaining a remedy for BCS's non-performance and BCS's interest in having a meaningful opportunity to cure any maintenance or support deficiency.
The requirement for written notice from Vantage creates an additional procedural prerequisite. Under the current drafting, the 120-day clock does not begin to run until Vantage delivers written notice to BCS specifying the nature of the material failure. When the time required for Vantage to identify the failure, prepare and deliver written notice, and the escrow agent's processing time following expiration of the 120-day period are taken into account, the total elapsed time from the onset of the failure to the actual release of source code could be substantially longer than 120 days. This extended timeline provides BCS with a significant window in which to cure any deficiency and avoid the release of source code.
We recommend that the term "materially fails to maintain or support" be defined with specificity. Rather than leaving this term undefined and subject to dispute, the Agreement should cross-reference the specific maintenance and support obligations set forth in the OEM Reseller Agreement (which we anticipate will be detailed in Section 7 or a related exhibit, such as a Service Level Agreement). This cross-reference ensures that both parties — and the Escrow Agent — can readily determine whether the maintenance failure trigger has been satisfied.
Recommendation. BCS's position on the 120-day threshold is favorable and should be maintained. We should anticipate that Vantage may attempt to shorten this period to sixty (60) or ninety (90) days, consistent with shorter cure periods sometimes found in comparable agreements. We recommend resisting any such attempt, as the 120-day period appropriately balances the interests of both parties and provides BCS with a meaningful opportunity to cure.
D. Vantage's Proposed Additional Trigger: Change of Control of BCS
Based on discussions during the term sheet negotiations and preliminary communications with Vantage's counsel, we anticipate that Vantage will propose adding a "change of control of BCS" as a fourth release trigger in the source code escrow agreement. Specifically, Vantage is expected to seek a provision under which a change in the majority ownership or voting control of BCS would entitle Vantage to receive a release of the Deposited Materials from escrow.
We recommend that BCS firmly reject this proposal. Our analysis supporting this recommendation is set forth below.
(i) Commercial Rationale for Rejection. BCS is majority-owned by Veltrano Capital Partners Fund IV, L.P., which holds approximately 68% of BCS's equity. As a private equity-backed portfolio company, BCS operates within the context of a fund-level investment strategy that contemplates a finite investment horizon and a defined exit pathway. Veltrano Capital may pursue range exit strategies for its investment in BCS, including a sale to a strategic acquirer, a secondary buyout by another private equity sponsor, a recapitalization transaction, an initial public offering, or an add-on acquisition that alters the ownership structure of BCS. Each of these transaction types is a routine and legitimate corporate activity in the private equity context, and any of them could constitute a "change of control" under a broadly drafted definition.
A change-of-control trigger in the source code escrow agreement would effectively penalize BCS and Veltrano Capital for pursuing these legitimate corporate transactions by potentially releasing BCS's most valuable intellectual property asset — the BrightEdge platform source code — to a counterparty. The release of source code would occur not because of any operational failure, insolvency, or inability to perform on BCS's part, but solely because of a change in BCS's ownership structure. This result is fundamentally inconsistent with the purpose of source code escrow, which is to protect the beneficiary against the depositor's inability or unwillingness to maintain the deposited software.
Moreover, a change of control does not inherently affect BCS's ability or willingness to perform its maintenance and support obligations under the Agreement. A new owner or acquirer of BCS would have strong economic incentives to continue supporting and enhancing the BrightEdge platform, as the platform is BCS's primary revenue driver and the foundation of its enterprise value. The acquiring entity would also assume BCS's obligations under the OEM Reseller Agreement, either through operation of law (in the case of a merger or asset acquisition) or through contractual assignment. There is no rational basis for concluding that a change of control, standing alone, impairs the continued performance of BCS's contractual obligations.
(ii) Risk to BCS's IP Portfolio. The release of source code upon a change of control would grant Vantage access to BCS's proprietary code without any triggering operational failure or insolvency event. Once source code is in Vantage's possession — even subject to contractual use restrictions — it becomes practically difficult to monitor and enforce compliance with those restrictions. The risks include:
• Inadvertent Disclosure. Once source code is in Vantage's hands, there is a risk of inadvertent disclosure to Vantage employees, contractors, or third parties who do not have a need to access the code and who may not be bound by adequate confidentiality obligations.
• Competitive intelligence. Even if Vantage complies with the letter of the use restrictions, mere access to BCS's source code could provide Vantage with competitive intelligence regarding BCS's algorithmic approaches, architectural decisions, data processing methods, and proprietary techniques. This intelligence could inform Vantage's own product development efforts, even if Vantage does not directly copy or reproduce BCS's code.
• Enforcement Challenges. In the event of a suspected breach of the use restrictions, BCS would face significant practical challenges in detecting and proving unauthorized use. Source code analysis and "clean room" reverse-engineering techniques could make it difficult to establish that Vantage derived specific features or capabilities from BCS's proprietary code.
These risks are mitigated when source code release is triggered by a genuine operational failure or insolvency event, because in those circumstances the release serves a legitimate protective purpose and the equities favor granting Vantage access to the code. When release is triggered merely by a change of ownership, however, the risks are incurred without any corresponding protective justification.
(iii) Impact on BCS Valuation and M&A Flexibility. Veltrano Capital's investment thesis and exit strategy for BCS may involve a sale, merger, or initial public offering within Veltrano Capital's fund investment horizon, which typically ranges from four to seven years. A change-of-control escrow release trigger could be viewed by potential acquirers or IPO underwriters as a material encumbrance on BCS's intellectual property portfolio.
In M&A due diligence, potential acquirers routinely review the target company's material contracts, including technology license agreements and associated escrow arrangements. A change-of-control trigger that could result in the release of the target's core source code to a counterparty would likely be flagged as a significant risk factor. Acquirers may demand a purchase price reduction to account for this risk, require the elimination of the trigger as a condition to closing, or decline to pursue the acquisition altogether. In an IPO context, the change-of-control trigger could be flagged in risk factor disclosures and could complicate the offering process.
Accordingly, acceptance of the change-of-control trigger could reduce BCS's enterprise value, narrow the field of potential acquirers, and impair Veltrano Capital's ability to execute a successful exit from its investment.
(iv) Market Practice. While some beneficiaries in technology escrow arrangements do request change-of-control release triggers, this request is not standard market practice. Industry practice for technology escrow agreements more commonly limits release to operational failures (failure to maintain or support), insolvency events (bankruptcy, cessation of operations), and, in some cases, material breach of the underlying license agreement. A survey of representative technology escrow agreements in the enterprise software and IoT sectors indicates that change-of-control triggers are requested by beneficiaries in a minority of transactions and are more commonly associated with agreements where the beneficiary has significant bargaining leverage or where the depositor faces heightened insolvency risk.
BCS's position in rejecting the change-of-control trigger is consistent with market norms for licensor-favorable source code escrow agreements and is supported by the commercial rationale discussed above.
(v) Alternative Protections Available to Vantage. Vantage's concerns about continuity of the BrightEdge platform in the event of a change of control of BCS are not without some commercial legitimacy. However, Vantage is already well-protected by the existing release triggers and other contractual provisions in the Agreement:
(a) The operational failure trigger (120 consecutive days after written notice) provides Vantage with access to source code if any new owner of BCS fails to maintain and support the BrightEdge platform for an extended period. If a post-acquisition owner neglects the platform, this trigger ensures that Vantage is not left without recourse.
(b) The cessation of business trigger protects Vantage if BCS (or its successor) ceases business operations entirely.
(c) The bankruptcy trigger protects Vantage if BCS (or its successor) becomes insolvent and files for bankruptcy.
(d) Section 365(n) of the Bankruptcy Code provides Vantage with independent statutory protections as a licensee of intellectual property, allowing Vantage to retain its license rights even if BCS rejects the Agreement in bankruptcy.
(e) The OEM Reseller Agreement's termination provisions, including termination for cause with a thirty-day cure period, provide Vantage with contractual remedies if a new owner of BCS fails to perform BCS's obligations under the Agreement.
Recommended Fallback Position. If Vantage insists on some form of protection related to a change of control, and rejection of the trigger becomes a significant impediment to closing the deal, we recommend offering enhanced notification and assumption provisions as an alternative to a release trigger. Spec

PRIVILEGED AND CONFIDENTIAL ATTORNEY-CLIENT PRIVILEGED ATTORNEY WORK PRODUCT

MEMORANDUM

ENGAGEMENT NO.: 1042-00005

I. INTRODUCTION AND EXECUTIVE SUMMARY

III. INTELLECTUAL PROPERTY OWNERSHIP PROVISIONS

V. LIMITED EXCLUSIVITY COVENANT

Record

Parties

Dates

Amounts