Subject technology definition is the foundation for focused patent searching, screening, and claim analysis. Before you can conduct effective FTO analysis, you must answer a fundamental question: What exactly are you analyzing? This question is more complex than it initially appears. A vague or incomplete definition of your technology can lead to missed patents, wasted resources, and ultimately, inadequate FTO protection.
This article provides a practical guide to defining Subject Technology—the foundation of all FTO analysis.
Subject Technology is a comprehensive, technically accurate description of the technology, product, or business process you're analyzing for freedom to operate. It defines the scope of your FTO analysis and guides all subsequent steps.
Technically Accurate: The definition accurately reflects how your product works and what it does.
Sufficiently Detailed: The definition includes enough technical detail to guide patent searching and analysis.
Clearly Scoped: The definition clearly states what is included and what is excluded from the analysis.
Stakeholder Alignment: All relevant stakeholders (technical, product, legal) have a shared understanding of the definition.
Documented: The definition is documented in writing and accessible to all team members involved in FTO analysis.
Your Subject Technology definition directly determines your patent search strategy:
A poorly defined Subject Technology leads to incomplete or misdirected searches.
When evaluating whether a patent is relevant to your FTO analysis, you compare the patent to your Subject Technology definition:
A vague Subject Technology definition makes relevance assessment difficult and inconsistent.
When performing claim charting, you map your product features to patent claim elements. This mapping is guided by your Subject Technology definition:
A poorly defined Subject Technology leads to incomplete or inaccurate claim charting.
Your Subject Technology definition determines the scope and cost of FTO analysis:
A well-defined Subject Technology helps you allocate resources appropriately.
Collect all relevant technical information:
Organize the documentation:
Ask these questions:
Document the answers:
Example for a Smart Home Device:
Determine what is included:
Determine what is excluded:
Document the boundaries clearly:
Example Inclusion/Exclusion List:
Included:
Excluded:
For each key feature, describe:
Use appropriate level of detail:
Example Technical Description:
Occupancy Detection Algorithm:
Consider related technologies that might be relevant:
Determine whether to include related technologies:
Create a written Subject Technology definition:
Validate with stakeholders:
Example Subject Technology Definition Document:
Subject Technology Definition: Smart Home Occupancy Management framework
Overview: A cloud-based software platform that uses machine learning to detect room occupancy and automatically control lighting, temperature, and security frameworks.
Core Components:
Included in Analysis:
Excluded from Analysis:
Key Technical Parameters:
Problem: You focus only on the most innovative aspect of your technology, missing related patents.
Example: Defining Subject Technology as only the "machine learning algorithm" while ignoring the "cloud backend" and "mobile app."
Consequence: Missing patents that cover the cloud backend or mobile app aspects of your product.
Solution: Include all significant technical components of your product.
Problem: You include too many tangential technologies, leading to irrelevant patent searches and wasted resources.
Example: Including "general cloud computing" and "mobile app development" as part of Subject Technology.
Consequence: Analyzing thousands of irrelevant patents.
Solution: Focus on the specific technical approach used in your product, not general technologies.
Problem: The definition is too vague for patent searchers and analysts to understand what you're analyzing.
Example: "A smart home framework that uses artificial intelligence."
Consequence: Patent searchers may miss relevant patents or search for the wrong technology.
Solution: Provide specific technical details about how your product works.
Problem: Different team members have different understandings of what's being analyzed.
Example: The technical team thinks Subject Technology includes the mobile app, but the legal team thinks it doesn't.
Consequence: Inconsistent analysis and missed risks.
Solution: Involve all stakeholders in defining Subject Technology and document the definition clearly.
Problem: You define Subject Technology once and never update it as your product evolves.
Example: You define Subject Technology for version 1.0 of your product, but version 2.0 includes significant new features.
Consequence: FTO analysis becomes outdated as your product evolves.
Solution: Update Subject Technology definition as your product design evolves.
The Scenario: A company developed a predictive maintenance framework for industrial equipment using IoT sensors and machine learning.
Initial Definition (Too Narrow):
"A machine learning algorithm that predicts equipment failures based on sensor data."
Problem: This definition missed important aspects of the product, including the IoT sensor network, cloud backend, and mobile app.
Revised Definition (Better):
"An IoT-based predictive maintenance framework that uses machine learning to predict equipment failures. The framework includes: (1) wireless IoT sensors that collect equipment performance data, (2) a cloud backend that processes sensor data and runs machine learning models, (3) a mobile app that alerts maintenance personnel of predicted failures, and (4) integration with existing maintenance management frameworks."
Validation: The company shared the revised definition with technical, product, and legal teams. All stakeholders agreed on the scope.
Result: The revised definition led to more comprehensive patent searching and identified several relevant patents that the narrow definition would have missed.
Include technical experts, product managers, and legal counsel in defining Subject Technology. Each perspective adds value.
Use precise technical terminology. Avoid vague or marketing language.
Use specific examples of how your product implements the technology.
Explain why certain technologies are included or excluded.
Update Subject Technology definition as your product design evolves.
Ensure all team members involved in FTO analysis have access to the definition.
Get explicit agreement from all stakeholders on the scope.
Accurately defining Subject Technology is the foundation of effective FTO analysis. By following the process outlined in this article, you can:
The time invested in defining Subject Technology upfront pays dividends throughout the FTO analysis process.
Key Takeaway: Subject Technology definition is the foundation of FTO analysis. Invest time in creating a clear, comprehensive, well-validated definition that all stakeholders understand and agree upon.
Help us improve
Something wrong, out of date, or missing on this page? Tell us and it goes straight to the team that maintains it.
This page