A competitor’s patent as­ser­tion can ar­rive when a prod­uct is ready for launch, al­ready in the field, or cen­tral to an in­vest­ment dis­cus­sion. At that point, a patent in­fringe­ment analy­sis is not an aca­d­e­m­ic ex­er­cise. It es­tab­lish­es what the as­sert­ed patent ac­tu­al­ly cov­ers, whether the prod­uct meets each re­quired claim fea­ture, and which busi­ness de­ci­sions re­main available.

The qual­i­ty of that analy­sis mat­ters. A su­per­fi­cial sim­i­lar­i­ty be­tween two prod­ucts may cre­ate con­cern, but in­fringe­ment is de­ter­mined by the patent claims and the rel­e­vant le­gal frame­work, not by a match­ing prod­uct de­scrip­tion, draw­ing or mar­ket­ing term. Equal­ly, a patent that ap­pears threat­en­ing at first sight may have a nar­row scope, may not cov­er the rel­e­vant ver­sion of a prod­uct, or may be vul­ner­a­ble on validity.

For en­gi­neer­ing-led busi­ness­es, the task is to turn a le­gal-tech­ni­cal ques­tion into a clear de­ci­sion: con­tin­ue, re­design, ne­go­ti­ate, chal­lenge, pre­pare a de­fence, or gath­er more ev­i­dence be­fore com­mit­ting resources.

What a patent in­fringe­ment analy­sis establishes

An in­fringe­ment analy­sis com­pares a de­fined prod­uct, process or method against the claims of a spe­cif­ic patent in the coun­tries where com­mer­cial ac­tiv­i­ty takes place. It asks whether every re­quired el­e­ment of an in­de­pen­dent claim is present in the ac­cused em­bod­i­ment, ei­ther lit­er­al­ly or, de­pend­ing on the ju­ris­dic­tion, through an equiv­a­lent feature.

This is more ex­act­ing than ask­ing whether the prod­uct uses the same un­der­ly­ing idea. Claims are struc­tured lim­i­ta­tions. They may re­quire a par­tic­u­lar arrange­ment of com­po­nents, a de­fined se­quence of steps, a ma­te­r­i­al prop­er­ty, a con­trol func­tion or a nu­mer­i­cal range. If one es­sen­tial fea­ture is ab­sent, lit­er­al in­fringe­ment of that claim may not be es­tab­lished. If it is present through a sub­sti­tut­ed so­lu­tion, the po­si­tion re­quires care­ful as­sess­ment un­der the ap­plic­a­ble na­tion­al law.

The analy­sis should iden­ti­fy the rel­e­vant le­gal sta­tus from the out­set. A pub­lished ap­pli­ca­tion, a grant­ed patent, a lapsed right and a patent un­der op­po­si­tion do not cre­ate the same com­mer­cial risk. Scope is ter­ri­to­r­i­al too. A Eu­ro­pean patent may lead to dif­fer­ent na­tion­al rights and pro­ce­dures af­ter grant. A prod­uct sold in the UK, man­u­fac­tured in Ger­many and sup­plied into an­oth­er mar­ket can there­fore re­quire a coun­try-by-coun­try view.

Start with the real prod­uct, not the brochure

The strongest work be­gins with a pre­cise tech­ni­cal de­f­i­n­i­tion of the prod­uct or process be­ing as­sessed. Mar­ket­ing ma­te­ri­als are rarely enough. They may omit fea­tures, de­scribe op­tion­al con­fig­u­ra­tions as stan­dard, or use lan­guage that dif­fers from the en­gi­neer­ing reality.

The rel­e­vant ev­i­dence can in­clude draw­ings, bills of ma­te­ri­als, CAD files, con­trol log­ic, man­u­fac­tur­ing in­struc­tions, test data, source code ex­tracts and pho­tographs of the fin­ished prod­uct. For a process claim, the se­quence of op­er­a­tions, equip­ment set­tings and in­puts can be de­ci­sive. For soft­ware-en­abled prod­ucts, the ques­tion may turn on where and how a func­tion is per­formed rather than on the user in­ter­face alone.

Prod­uct ver­sions re­quire dis­ci­pline. A find­ing for a pro­to­type may not ap­ply to a pro­duc­tion mod­el af­ter a sup­pli­er sub­sti­tu­tion or firmware up­date. Con­verse­ly, a pro­posed de­sign-around should be as­sessed against the claim lan­guage be­fore it is frozen into tool­ing, pro­cure­ment com­mit­ments or reg­u­la­to­ry documentation.

Con­fi­den­tial han­dling is cen­tral here. Tech­ni­cal ma­te­ri­als of­ten re­veal the very know-how that gives a busi­ness its com­pet­i­tive ad­van­tage. The analy­sis should re­quest only what is nec­es­sary, pre­serve a clear record of sources and dis­tin­guish con­firmed facts from assumptions.

The claims chart is the de­ci­sion document

A claims chart maps each lim­i­ta­tion of a rel­e­vant claim to ev­i­dence from the prod­uct or process. It does not mere­ly state that a fea­ture is present. It records where it is found, why the cor­re­spon­dence is tech­ni­cal­ly sound and how cer­tain the ev­i­dence is.

For ex­am­ple, a claim may re­quire a sen­sor po­si­tioned with­in a spec­i­fied hous­ing, a con­troller that cal­cu­lates a val­ue from two in­puts, and a sig­nal gen­er­at­ed when a thresh­old is ex­ceed­ed. The chart ex­am­ines each lim­i­ta­tion sep­a­rate­ly. A broad­ly sim­i­lar de­vice with a sen­sor else­where or a dif­fer­ent con­trol log­ic may fall out­side the claim, even if it serves the same com­mer­cial purpose.

This struc­tured map­ping ex­pos­es the real pres­sure points. It may show that the case turns on one am­bigu­ous term, an op­tion­al prod­uct mode, an un­ver­i­fied sup­pli­er com­po­nent or ev­i­dence that is not avail­able from the prod­uct it­self. That is use­ful in­for­ma­tion. It di­rects en­gi­neer­ing in­ves­ti­ga­tion and pre­vents le­gal or com­mer­cial de­ci­sions from be­ing based on a vague over­all impression.

Claim con­struc­tion comes be­fore conclusions

Claims can­not be read in iso­la­tion. Their word­ing must be con­sid­ered along­side the de­scrip­tion, draw­ings, pros­e­cu­tion his­to­ry where rel­e­vant, com­mon tech­ni­cal knowl­edge and the ap­proach tak­en by the com­pe­tent court in the ju­ris­dic­tion concerned.

A term such as “con­nect­ed”, “con­fig­ured to” or “sub­stan­tial­ly” may ap­pear straight­for­ward but can car­ry sub­stan­tial con­se­quences. Does “con­nect­ed” re­quire a di­rect phys­i­cal link, or does a net­worked re­la­tion­ship suf­fice? Is a fea­ture re­quired at all times, or only dur­ing a par­tic­u­lar op­er­at­ing state? Does a nu­mer­i­cal range in­clude a mea­sured tol­er­ance? The an­swers are not universal.

This is where en­gi­neer­ing un­der­stand­ing adds val­ue. A cred­i­ble in­ter­pre­ta­tion must make tech­ni­cal sense in the con­text of the in­ven­tion. At the same time, tech­ni­cal plau­si­bil­i­ty should not be used to read lim­i­ta­tions out of a claim. The analy­sis needs to be dis­ci­plined: broad enough to iden­ti­fy risk, pre­cise enough to sup­port action.

In­fringe­ment risk and patent va­lid­i­ty are sep­a­rate questions

A prod­uct can fall with­in the word­ing of a grant­ed claim while the claim it­self may be sus­cep­ti­ble to chal­lenge. Ear­li­er pub­li­ca­tions, pub­lic use, ob­vi­ous­ness ar­gu­ments, in­suf­fi­cien­cy and added-mat­ter is­sues can af­fect va­lid­i­ty, de­pend­ing on the ap­plic­a­ble law and patent history.

That does not mean va­lid­i­ty should be treat­ed as an au­to­mat­ic es­cape route. In­va­lid­i­ty work needs its own ev­i­dence, search strat­e­gy and le­gal as­sess­ment. Pri­or art must be dat­ed, pub­licly avail­able and rel­e­vant to the claimed sub­ject mat­ter. A doc­u­ment that looks close but miss­es one lim­i­ta­tion may have lim­it­ed val­ue alone, al­though it can still con­tribute to an ob­vi­ous­ness case.

The com­mer­cial or­der of work de­pends on the cir­cum­stances. If a claims chart iden­ti­fies a clear non-in­fringe­ment po­si­tion, ex­ten­sive va­lid­i­ty work may not be pro­por­tion­ate at the out­set. If the prod­uct ap­pears to meet all claim fea­tures and the mar­ket is strate­gi­cal­ly im­por­tant, a par­al­lel va­lid­i­ty re­view may be jus­ti­fied. Where tim­ing is crit­i­cal, these work­streams can pro­ceed to­geth­er, with find­ings ranked by de­ci­sion value.

The re­sult should lead to an op­er­a­tional choice

A use­ful analy­sis does not end with a bi­na­ry la­bel. It sets out the as­sump­tions, ev­i­dence strength, un­re­solved points and con­se­quences for the busi­ness. It should sep­a­rate a tech­ni­cal­ly plau­si­ble con­cern from a con­clu­sion that can be re­lied upon in ne­go­ti­a­tions, board de­ci­sions or a dispute.

Pos­si­ble ac­tions com­mon­ly in­clude a tech­ni­cal­ly mean­ing­ful de­sign-around, a re­quest for fur­ther in­for­ma­tion, a mon­i­tored launch, li­cens­ing dis­cus­sions, a va­lid­i­ty chal­lenge or de­fence prepa­ra­tion. The right route de­pends on the prod­uct mar­gin, speed to mar­ket, avail­able en­gi­neer­ing al­ter­na­tives, ju­ris­dic­tion, cus­tomer com­mit­ments and the patent owner’s like­ly ap­petite for enforcement.

De­sign-arounds de­serve par­tic­u­lar care. Chang­ing a vis­i­ble com­po­nent may not al­ter the fea­ture that the claim ac­tu­al­ly re­quires. A sound de­sign-around be­gins with the claim lim­i­ta­tion cre­at­ing the risk and then de­vel­ops a tech­ni­cal­ly work­able al­ter­na­tive that avoids it. The re­vised de­sign must then be checked in the same struc­tured way as the original.

For a patent as­ser­tion, ev­i­dence preser­va­tion should be­gin ear­ly. Re­tain de­sign records, de­vel­op­ment dates, sup­pli­er com­mu­ni­ca­tions, test re­ports and prod­uct ver­sions. Avoid in­for­mal tech­ni­cal ad­mis­sions in cor­re­spon­dence be­fore the claim scope and fac­tu­al po­si­tion are un­der­stood. Ear­ly clar­i­ty pro­tects op­tions that can be dif­fi­cult to re­cov­er later.

When to com­mis­sion the analysis

The best time is be­fore launch, in­vest­ment or a ma­jor de­sign freeze, when the busi­ness can still change course at man­age­able cost. It is also es­sen­tial when a com­peti­tor iden­ti­fies a patent, a cus­tomer re­quests as­sur­ance, an ac­qui­si­tion re­veals un­fa­mil­iar rights or a new mar­ket is be­ing considered.

A free­dom-to-op­er­ate re­view and an in­fringe­ment analy­sis are re­lat­ed but not iden­ti­cal. An FTO ex­er­cise iden­ti­fies po­ten­tial­ly rel­e­vant third-par­ty rights across a de­fined field and ter­ri­to­ry. An in­fringe­ment analy­sis ex­am­ines whether a par­tic­u­lar prod­uct or process falls with­in iden­ti­fied claims. Where a spe­cif­ic patent has be­come com­mer­cial­ly sig­nif­i­cant, fo­cused claim analy­sis is usu­al­ly re­quired even if an ear­li­er FTO re­view was completed.

TIPAG de­liv­ers the tech­ni­cal struc­ture need­ed to as­sess claims against real prod­ucts, not sim­pli­fied de­scrip­tions. The aim is a con­fi­den­tial, com­mer­cial­ly us­able po­si­tion that en­gi­neer­ing, man­age­ment and le­gal ad­vis­ers can act on.

The most valu­able out­come is not cer­tain­ty where the facts do not sup­port it. It is a clear­ly ev­i­denced view of risk, the prac­ti­cal routes around it and the de­ci­sions that should be made be­fore the next prod­uct, mar­ket or ne­go­ti­a­tion com­mit­ment clos­es those routes.