About · Patent
How an Independent Formulator Reads a Grease Patent (Without Copying It)
A grease patent is a map of what someone already claimed, not a recipe to copy and not an automatic lock-out. Read the independent claims, the examples, and the problem the inventors said they were solving. Then design around with your…
Direct answer
A grease patent is a map of what someone already claimed, not a recipe to copy and not an automatic lock-out. Read the independent claims, the examples, and the problem the inventors said they were solving. Then design around with your base oil, your kettle and your test file. Lubechem does chemistry under NDA; FTO is a lawyer’s job we will not fake.
- A grease patent is three documents in one cover: the abstract (triage), the examples (teaching), the claims (the legal fence). Read each differently.
- A granted claim is evidence an examiner found it novel and non-obvious — not evidence the product works, was ever manufactured, or that the market wants it.
- 'Comprising' is open language: you cannot escape an open claim by adding an ingredient. Ranges and Markush lists fence every listed option.
- Designing around is honest engineering with the fence in view: change one claimed element for real and prove equivalence with bench data.
- A formulator's claim reading is not a legal opinion. Freedom-to-operate belongs to a patent attorney with the granted text, the file history and your sales territories.
Claims vs examples vs abstract
A patent document is three documents wearing one cover. The abstract is marketing to search engines — useful for triage, useless for decisions. The specification and examples are the teaching: what the inventors actually mixed, in what order, and what they measured. The claims are the legal fence: the only part with exclusionary force, written by attorneys to be as broad as defensible. Reading a grease patent as a chemist means reading all three differently — mining the examples for what to test, reading the independent claims for what is fenced, and ignoring the abstract entirely. The filings cited across this blog (the 2024–2026 CV-joint, conductive-grease, zinc-complex and ionic-liquid cases) are worked examples of exactly this method.
What a patent is evidence for
A granted claim is evidence that an examiner found the claim novel and non-obvious over the cited art — nothing more. It is not evidence the product works, that it was ever manufactured, or that the market wants it. A published application is weaker still: it is evidence of what someone hoped to claim. Both are superb technical literature, because the enablement bargain forces real disclosure — and that disclosure is what a formulator reads.
What ‘comprising’ does in a grease claim
Claim language has its own grammar. 'Comprising' is open — the claimed grease has the listed ingredients and may have anything else too — so you cannot escape an open claim by adding an ingredient. 'Consisting of' is closed. Ranges matter: 'sulfonate below 22 wt%' fences everything below the line, so 23 wt% is outside the literal fence (a statement about reading, not about safety — the doctrine of equivalents exists, and that is attorney territory). Markush lists ('a metal selected from zinc, calcium…') fence every listed option. Independent claims carry the fence posts; dependent claims hang ornaments on them. A formulator who reads one independent claim carefully learns more than from ten hours of abstract skimming.
What it is not evidence for
Claim analysis by a formulator is not a legal opinion. We read claims to understand chemistry and design space; we do not issue freedom-to-operate opinions, validity opinions or infringement conclusions. Those come from a patent attorney working from granted text, prosecution history and the law of your sales territories — different documents, different professional insurance.
Designing around vs infringing
Designing around is honest engineering with the fence in view: change at least one claimed element for real — a different thickener family, a different solid, a different process order, a composition outside the claimed ranges — and prove with bench data that the change still meets the duty. Infringing is copying the claimed combination and hoping nobody checks. The grey zone between them is where attorneys earn fees, and the practical rule for a formulation house is simple: document your own development path (dated lab books, your own test data, your own raw materials), never transcribe claim language into a TDS, and treat worked examples as inspiration for your own matrix rather than as a recipe.
What a formulator changes on the bench
Our patent-reading workflow, as used on the filings cited across this blog:
- Claim chart for chemistry: independent-claim elements in rows, with the design variable each element represents — thickener, solids, process window, ratios.
- Example audit: which variables did the inventors actually sweep, and which did they leave untouched? Untouched variables are where your screening matrix starts.
- Bench proof: your variant gets your full proof-test battery (penetration, drop point, bleed, wear, life-rig screens) — equivalence is data, not argument.
- Attorney handoff: the final BOM, the claim chart and your data go to a patent attorney before commercialisation if the fenced territory matters to your market.
How we use patents as a literature source in this practice
In this practice, patents serve three honest purposes: they reveal which problems well-funded laboratories consider unsolved (that is market research you did not pay for); they disclose formulations and process windows worth testing as screening arms; and they map the fence so your own development can be steered early, while steering is cheap. What they never do here is become a product claim, a copied recipe, or legal advice. The same reading discipline applies to journal papers: method before conclusion, conditions before numbers.
The design-around question
The design-around question, asked of every filing we read: which element of independent claim 1 could you genuinely change while keeping performance — and what data would prove the change is real? If the honest answer is 'nothing, their combination is simply the best', then the options are licence, wait for expiry, or pick a different problem. Copying quietly is not on the list.
What Lubechem will and will not claim
Lubechem Consultant is an independent formulation house in New Delhi, led by Er. Manoj Kumar and practising since 2010. We work under NDA, transfer IP as scoped in contract, and use patents the way this article describes — as prior art and literature, cited so a chemist can read the source. We do not reproduce claim language in deliverables, we do not issue freedom-to-operate opinions, and we do not invent clients, certificates or savings.
What we will do is read the filing with you, chart it, run the screening matrix it suggests, and hand the attorney question to an attorney with a complete technical file. If a competitor's patent just landed in your inbox, send it with your current formula and your sales territories. The first deliverable is a claim chart and a screening plan — not a panic.
How to use this filing as prior art — not as a recipe
| Question | What to extract | What not to do |
|---|---|---|
| What problem is claimed? | The design problem a funded lab thought worth fencing — free market research | Do not treat the abstract as a proven plant SOP |
| Thickener / additive families named | The design variables: thickener, solids, process window, ratios | Do not copy claim language into a TDS |
| Examples vs claims | Examples teach what to test; claims fence what to steer around | Examples are not a licence |
| Design-around | Change one claimed element for real; prove equivalence with data | FTO is legal advice; Lubechem does not issue it |
| Citation in this article | Method piece citing the 2024–26 filings in this plan as examples, not as legal opinions | Cite, do not reproduce claims |
People-first note: this is dated editorial for decision-making. It is not a scaled rewrite of the manufacturing pages, and it is not legal or certification advice.
Questions plants actually ask
Is grease formulation patent freedom to operate a drop-in for whatever we run today?
Almost never. Thickener family, base-oil viscosity, NLGI grade and additive response all have to be matched to the duty. A purge plan comes before a plant-wide switch. Compatibility charts are screens, not guarantees.
Can we put grease formulation patent freedom to operate on the TDS because a patent or paper mentioned it?
No. Patents are prior art. Papers are evidence under stated conditions. A TDS line has to be backed by a method you actually ran, on oil you actually stock, at a treat you can buy twice.
Who owns the formula if Lubechem develops it?
Ownership is the contract. The practice is independent formulation with IP transfer as scoped — not a branded additive package you can never leave. Ask for the assignment language before the first kettle.
What should Plant owners who just saw a competitor patent and panicked send in the first brief?
Duty (load, speed, water, temperature, relube), the current TDS and fail mode, target specs (IS / ASTM / OEM), and whether the product is sold, used in-house, or exported. Photographs of the failed component help more than adjectives.
Literature and prior art
Citations below are orientation, not a freedom-to-operate opinion. Lubechem does not copy claimed compositions and does not treat a patent as a product endorsement.
- Method piece citing the 2024–26 filings in this plan as examples, not as legal opinions — cited as prior art or literature, not as a product Lubechem sells
- Lubechem about and services pages — practice scope since 2010, New Delhi
- NDA and IP-assignment practice — formula ownership is a contract, not a slogan