
Resources
Guides, research, and perspectives on R&D intelligence, IP strategy, and the future of AI enabled innovation.

Knowledge Management for R&D Teams: Building a Central Hub for Internal Projects and External Innovation Intelligence
Research and development teams generate enormous volumes of institutional knowledge through experiments, project documentation, technical meetings, and informal problem-solving conversations. This knowledge represents decades of accumulated expertise and millions of dollars in research investment. Yet most organizations struggle to capture, organize, and leverage this intellectual capital effectively. The result is that every new research initiative essentially starts from zero, with teams unable to build systematically on what the organization has already learned.
The challenge extends beyond simply documenting what teams know internally. R&D professionals must also connect their institutional knowledge with the broader landscape of patents, scientific literature, competitive intelligence, and market trends that inform strategic research decisions. Without systems that unify these information sources, researchers operate in silos where discovery is fragmented, duplicative, and disconnected from institutional memory.
Enterprise knowledge management for R&D has evolved from static document repositories into dynamic intelligence systems that synthesize information across sources. The most effective approaches treat knowledge management not as an administrative burden but as the organizational brain that enables teams to progress innovation along a linear path rather than repeatedly circling back to first principles.
The True Cost of Starting From Scratch
When knowledge remains siloed across departments, project files, and individual researchers' memories, organizations pay significant hidden costs. According to the International Data Corporation, Fortune 500 companies collectively lose roughly $31.5 billion annually by failing to share knowledge effectively, averaging over $60 million per company. The Panopto Workplace Knowledge and Productivity Report arrives at similar figures through different methodology, finding that the average large US business loses $47 million in productivity each year as a direct result of inefficient knowledge sharing, with companies of 50,000 employees losing upwards of $130 million annually.
The most damaging consequence in R&D environments is duplicate research. According to Deloitte's analysis of pharmaceutical R&D data quality, significant work duplication persists across research organizations, with teams repeatedly building similar databases and pursuing parallel investigations without awareness of prior work. When fragmented knowledge systems fail to surface internal prior art, organizations waste months redeveloping solutions that already exist within their own walls.
These scenarios repeat across industries wherever institutional knowledge fails to flow effectively between teams and time zones. Without a centralized intelligence system, every research question becomes an expedition into unknown territory even when the organization has already mapped that ground. Teams cannot know what they do not know exists, so they default to external searches and first-principles investigation rather than building on institutional foundations.
The Tribal Knowledge Paradox
Tribal knowledge refers to undocumented information that exists only in the minds of certain employees and travels through word-of-mouth rather than formal documentation systems. In R&D environments, tribal knowledge often represents the most valuable institutional expertise: the experimental approaches that consistently produce better results, the vendor relationships that accelerate prototype development, the technical intuitions about why certain formulations work better than theoretical predictions suggest.
The paradox is that tribal knowledge is simultaneously the organization's greatest asset and its most significant vulnerability. According to the Panopto Workplace Knowledge and Productivity Report, approximately 42 percent of institutional knowledge is unique to the individual employee. When experienced researchers retire or change companies, they take irreplaceable understanding of legacy systems, historical research decisions, and cross-disciplinary connections with them.
The deeper problem is that without systems designed to surface and synthesize tribal knowledge, it might as well not exist for most of the organization. A researcher in one division has no way of knowing that a colleague three time zones away solved a similar problem two years ago. A newly hired scientist cannot access the decades of accumulated intuition that their predecessor developed through trial and error. Teams operate as if they are the first people to ever investigate their research questions, even when the organization possesses substantial relevant expertise.
This is not a documentation problem that can be solved by asking researchers to write more detailed reports. The issue is architectural. Traditional knowledge management systems store documents but cannot connect concepts, surface relevant precedents, or synthesize insights across sources. Researchers searching these systems must already know what they are looking for, which defeats the purpose when the goal is discovering what the organization already knows about unfamiliar territory.
Why Traditional Approaches Create Siloed Discovery
Generic knowledge management platforms often fail R&D teams because they treat knowledge as static content to be stored and retrieved rather than dynamic intelligence to be synthesized and connected. Document management systems can store experimental protocols and project reports, but they cannot automatically connect a current research question to relevant past experiments, competitive patents, or emerging scientific literature.
R&D knowledge exists across multiple formats and systems: electronic lab notebooks, project management tools, email threads, meeting recordings, patent databases, and scientific publications. Traditional platforms force researchers to search across these sources independently and mentally synthesize the results. This fragmented approach creates discovery silos where each researcher or team operates within their own information bubble, unaware of relevant knowledge that exists elsewhere in the organization or in external sources.
According to a McKinsey Global Institute report, employees spend nearly 20 percent of their time searching for or seeking help on information that already exists within their companies. The Panopto research quantifies this further, finding that employees waste 5.3 hours every week either waiting for vital information from colleagues or working to recreate existing institutional knowledge. For R&D professionals whose fully loaded costs often exceed $150,000 annually, this represents enormous productivity losses that compound across teams and years.
The consequences accumulate over time. Without visibility into what colleagues are investigating, teams pursue overlapping research directions without realizing the duplication until resources have been spent. Without connection to external patent databases, researchers may invest months developing approaches that competitors have already protected. Without integration with scientific literature, teams may miss published findings that would accelerate or redirect their investigations.
The Case for a Centralized R&D Brain
The solution is not simply better documentation or more comprehensive search. R&D organizations need systems that function as the collective brain of the research team, continuously synthesizing institutional knowledge with external innovation intelligence and surfacing relevant insights at the moment of need.
This architectural shift transforms how research progresses. Instead of each project starting from zero, new initiatives begin with comprehensive situational awareness: what has the organization already learned about relevant technologies, what have competitors patented in adjacent spaces, what does recent scientific literature suggest about feasibility, and what market signals should inform prioritization. This foundation enables teams to progress innovation along a linear path, building systematically on accumulated knowledge rather than repeatedly rediscovering the same territory.
The emergence of AI-powered knowledge systems has made this vision achievable. Retrieval-augmented generation technology enables platforms to combine large language model capabilities with organizational knowledge bases, delivering responses that are contextually relevant and grounded in reliable sources. According to McKinsey's analysis of RAG technology, this approach enables AI systems to access and reference information outside their training data, including an organization's specific knowledge base, before generating responses. Rather than returning lists of potentially relevant documents, these systems can synthesize information across sources to directly answer research questions with citations to underlying evidence.
When a researcher asks about previous work on a specific formulation, the system does not simply retrieve documents that mention relevant keywords. It synthesizes information from internal project files, relevant patents, and scientific literature to provide an integrated answer that reflects the full scope of available knowledge. This synthesis function replicates the institutional memory that senior researchers carry mentally but makes it accessible to entire teams regardless of tenure.
Essential Capabilities for the R&D Knowledge Hub
Effective knowledge management for R&D teams requires capabilities that go beyond generic enterprise platforms. The system must handle the unique characteristics of research knowledge: highly technical content, evolving understanding that may contradict previous findings, complex relationships between concepts across disciplines, and integration with scientific databases and patent repositories.
Central repository functionality serves as the foundation. All project documentation, experimental data, meeting notes, technical presentations, and research communications should flow into a unified system where they can be searched, analyzed, and connected. This consolidation eliminates the micro-silos that develop when teams store knowledge in departmental drives, personal folders, or application-specific databases.
Integration with external innovation data distinguishes R&D-specific platforms from general knowledge management tools. Research decisions must account for competitive patent landscapes, emerging scientific discoveries, regulatory developments, and market intelligence. Platforms that combine internal project knowledge with access to comprehensive patent and scientific literature databases enable researchers to situate their work within the broader innovation landscape.
AI-powered synthesis capabilities transform knowledge management from passive storage into active research intelligence. When a researcher investigates a new direction, the system should automatically surface relevant internal precedents, related patents, pertinent scientific literature, and potential competitive considerations. This proactive intelligence delivery ensures that researchers benefit from institutional knowledge without needing to know in advance what questions to ask.
Collaborative features enable knowledge to flow between researchers without requiring extensive documentation effort. Question-and-answer functionality allows team members to pose technical queries that route to colleagues with relevant expertise. According to a case study from Starmind, PepsiCo R&D implemented such a system and found that 96 percent of questions asked were successfully answered, with researchers often discovering that colleagues sitting at adjacent desks possessed relevant expertise they had not known about.
Bridging Internal Knowledge and External Intelligence
The most significant evolution in R&D knowledge management involves bridging internal institutional knowledge with external innovation intelligence. Traditional approaches treated these as separate domains: internal knowledge management systems for capturing what the organization knows, and external database subscriptions for monitoring patents, scientific literature, and competitive activity.
This separation perpetuates siloed discovery. Researchers might conduct extensive internal searches about a technical approach without realizing that competitors have recently patented similar methods. Teams might pursue development directions that published scientific literature has already shown to be unpromising. Strategic planning might overlook market signals that would contextualize internal capability assessments.
Unified platforms that couple internal data with external innovation intelligence provide researchers with comprehensive situational awareness. When investigating a new research direction, teams can simultaneously assess what the organization already knows from past projects, what competitors have patented in adjacent spaces, what recent scientific publications suggest about technical feasibility, and what market intelligence indicates about commercial potential. This holistic view supports better research prioritization and faster identification of white-space opportunities.
Cypris exemplifies this integrated approach by providing R&D teams with unified access to over 500 million patents and scientific papers alongside capabilities for capturing and synthesizing internal project knowledge. Enterprise teams at companies including Johnson & Johnson, Honda, Yamaha, and Philip Morris International use the platform to query research questions and receive responses that draw on both institutional expertise and the global innovation landscape. The platform's proprietary R&D ontology ensures that technical concepts are correctly mapped across sources, preventing the missed connections that occur when systems rely on simple keyword matching.
This integration transforms Cypris into the central brain for R&D operations. Rather than maintaining separate workflows for internal knowledge management and external intelligence gathering, research teams work from a single platform that synthesizes all relevant information. The result is linear innovation progress where each research initiative builds systematically on everything the organization and the broader scientific community have already established.
Converting Tribal Knowledge into Organizational Intelligence
Converting tribal knowledge into systematic institutional intelligence requires technology platforms that reduce the friction of knowledge capture while maximizing the accessibility of captured knowledge. The goal is not comprehensive documentation of everything researchers know, but rather systems that make institutional expertise available at the moment of need without requiring extensive manual effort.
Intelligent question routing connects researchers with colleagues who possess relevant expertise, even when those connections would not be obvious from organizational charts or explicit expertise profiles. AI systems can analyze communication patterns, project histories, and documented expertise to identify the best person to answer specific technical questions. This capability surfaces tribal knowledge that would otherwise remain locked in individual minds.
Automated knowledge extraction from project documentation identifies patterns, learnings, and best practices that might not be explicitly labeled as such. AI systems can analyze historical project files to surface insights about what approaches worked well, what challenges arose, and what decisions were made in similar situations. This extraction creates structured knowledge from unstructured archives, making years of accumulated experience accessible to current research efforts.
Integration with research workflows ensures that knowledge capture happens naturally during the research process rather than as a separate administrative task. When documentation flows automatically from electronic lab notebooks into central repositories, when project updates synchronize across team members, and when communications are indexed and searchable, knowledge management becomes invisible infrastructure rather than additional work.
The transformation is profound. Instead of tribal knowledge existing as fragmented expertise distributed across individual researchers, it becomes part of the organizational brain that informs all research activities. New team members can access decades of accumulated intuition from their first day. Researchers investigating unfamiliar territory can benefit from relevant experience that exists elsewhere in the organization. The institution becomes genuinely smarter than any individual, with AI systems serving as the connective tissue that links expertise across people, projects, and time.
AI Architecture for R&D Knowledge Systems
Artificial intelligence has transformed what organizations can achieve with knowledge management. Large language models combined with retrieval-augmented generation enable systems to understand and respond to complex technical queries in ways that were impossible with previous generations of search technology. Rather than returning lists of documents that might contain relevant information, AI-powered systems can synthesize information from multiple sources and provide direct answers to research questions.
According to AWS documentation on RAG architecture, retrieval-augmented generation optimizes the output of large language models by referencing authoritative knowledge bases outside training data before generating responses. For R&D applications, this means AI systems can ground their responses in organizational project files, patent databases, and scientific literature rather than relying solely on general training data that may be outdated or irrelevant to specific technical domains.
Enterprise RAG implementations take this capability further by providing secure integration with proprietary organizational data. According to analysis from Deepchecks, enterprise RAG systems are built to meet stringent organizational requirements including security compliance, customizable permissions, and scalability. These systems create unified views across fragmented data sources, enabling researchers to query across internal and external knowledge through a single interface.
Advanced platforms are beginning to incorporate knowledge graph technology that maps relationships between concepts, researchers, projects, and external entities. These graphs enable discovery of non-obvious connections: a material being studied in one division might have applications relevant to challenges facing another division, or an external researcher's publication might suggest collaboration opportunities that would accelerate internal development timelines.
Cypris has invested significantly in these AI capabilities, establishing official API partnerships with OpenAI, Anthropic, and Google to ensure enterprise-grade AI integration. The platform's AI-powered report builder can automatically synthesize intelligence briefs that combine internal project knowledge with external patent and literature analysis, dramatically reducing the time researchers spend compiling background information for new initiatives. This capability exemplifies the organizational brain concept: rather than researchers manually gathering and synthesizing information from disparate sources, the system delivers integrated intelligence that enables immediate progress on substantive research questions.
Security and Compliance Considerations
R&D knowledge management involves particularly sensitive information including trade secrets, pre-publication research findings, competitive intelligence, and strategic planning documents. Security architecture must protect this intellectual property while still enabling the collaboration and synthesis that drive value.
Enterprise platforms should maintain certifications like SOC 2 Type II that demonstrate rigorous security controls and audit procedures. Granular access controls must respect the need-to-know boundaries within research organizations, ensuring that sensitive project information is available only to authorized personnel while still enabling cross-functional discovery where appropriate.
For organizations with heightened security requirements, platforms with US-based operations and data storage provide additional assurance regarding data sovereignty and regulatory compliance. Cypris maintains SOC 2 Type II certification and stores all data securely within US borders, addressing the security concerns that often prevent R&D organizations from adopting cloud-based knowledge management solutions.
AI integration introduces additional security considerations. Systems must ensure that proprietary information used to train or augment AI responses does not leak into responses for other users or organizations. Enterprise-grade AI partnerships with established providers like OpenAI, Anthropic, and Google offer more robust security guarantees than ad-hoc integrations with less mature AI services.
Evaluating Knowledge Management Solutions for R&D
Organizations evaluating knowledge management platforms for R&D teams should assess several critical factors beyond generic enterprise software considerations.
Data integration capabilities determine whether the platform can unify the diverse information sources that characterize R&D operations. The system must connect with electronic lab notebooks, project management tools, document repositories, communication platforms, and external databases. Platforms that require extensive custom development for basic integrations will struggle to achieve the unified knowledge environment that drives value.
External data coverage distinguishes platforms designed for R&D from generic knowledge management tools. Access to comprehensive patent databases, scientific literature, and market intelligence enables the situational awareness that prevents duplicate research and identifies white-space opportunities. Platforms should provide unified search across internal and external sources rather than requiring separate workflows for each.
AI sophistication determines whether the platform can deliver true synthesis rather than simple retrieval. Systems should demonstrate the ability to understand complex technical queries, integrate information across sources, and provide substantive answers with appropriate citations. Generic AI capabilities that work well for consumer applications may not handle the specialized terminology and conceptual relationships that characterize R&D knowledge.
Adoption trajectory matters significantly for platforms that depend on organizational knowledge contribution. Systems that integrate seamlessly with existing research workflows will accumulate institutional knowledge more rapidly than those requiring separate documentation effort. The richness of the knowledge base directly determines the value the system provides, creating a virtuous cycle where early adoption benefits compound over time.
Building the Knowledge-Centric R&D Organization
Technology platforms provide the infrastructure for knowledge management, but culture determines whether that infrastructure captures the institutional expertise that drives competitive advantage. Organizations that successfully transform into knowledge-centric operations share several characteristics.
They normalize asking questions rather than expecting researchers to figure things out independently. When answers to questions become searchable knowledge assets, individual uncertainty transforms into organizational learning. The stigma around not knowing something dissolves when asking questions contributes to institutional intelligence.
They celebrate knowledge sharing as a form of contribution distinct from research output. Researchers who help colleagues solve problems, document lessons learned, or connect cross-disciplinary insights should receive recognition alongside those who publish papers or secure patents. This recognition signals that knowledge contribution is valued and expected.
They invest in systems that make knowledge sharing easier than knowledge hoarding. When the fastest path to answers runs through institutional knowledge bases rather than individual relationships, the calculus of knowledge sharing changes. The organizational brain becomes the natural starting point for any research question, and contributing to that brain becomes a natural part of research workflow.
Most importantly, they recognize that the alternative to systematic knowledge management is not the status quo but rather continuous degradation. As experienced researchers leave, as projects conclude without documentation, as external landscapes evolve faster than institutional awareness can track, organizations without knowledge management infrastructure fall progressively further behind. The choice is not between investing in knowledge systems and saving that investment. The choice is between building organizational intelligence deliberately and watching it erode by default.
Frequently Asked Questions About R&D Knowledge Management
What distinguishes knowledge management systems designed for R&D from generic enterprise platforms? R&D-specific platforms provide integration with scientific databases, patent repositories, and technical literature that generic systems lack. They understand technical terminology and conceptual relationships across disciplines. Most importantly, they connect internal institutional knowledge with external innovation intelligence, enabling researchers to situate their work within the broader technological landscape rather than operating in discovery silos.
How does AI transform knowledge management for R&D teams? AI enables knowledge management systems to function as the organizational brain rather than passive document storage. Researchers can ask complex technical questions and receive integrated responses that draw on internal project history, relevant patents, and scientific literature. AI also automates knowledge extraction from unstructured sources, surfacing institutional expertise that would otherwise remain inaccessible.
What is tribal knowledge and why does it matter for R&D organizations? Tribal knowledge refers to undocumented expertise that exists in the minds of individual researchers and transfers through informal conversations rather than formal documentation. In R&D environments, tribal knowledge often represents the most valuable institutional expertise accumulated through years of hands-on experimentation. Without systems designed to capture and synthesize this knowledge, organizations cannot build on their own experience and effectively start from scratch with each new initiative.
How can organizations ensure researchers actually use knowledge management systems? Successful implementations reduce friction through workflow integration, demonstrate clear value through tangible examples, and create cultural expectations around knowledge contribution. When researchers see that knowledge systems help them find answers faster, avoid duplicate work, and accelerate their own projects, adoption follows naturally. The key is making knowledge contribution a natural byproduct of research activity rather than a separate administrative burden.
What role does external innovation data play in R&D knowledge management? External data provides context that internal knowledge alone cannot supply. Understanding competitive patent landscapes, emerging scientific developments, and market intelligence helps organizations identify white-space opportunities, avoid infringement risks, and prioritize research directions. Platforms that unify internal and external data enable researchers to progress innovation linearly rather than repeatedly rediscovering territory that others have already mapped.
Sources:
International Data Corporation (IDC) - Fortune 500 knowledge sharing losseshttps://computhink.com/wp-content/uploads/2015/10/IDC20on20The20High20Cost20Of20Not20Finding20Information.pdf
Panopto Workplace Knowledge and Productivity Reporthttps://www.panopto.com/company/news/inefficient-knowledge-sharing-costs-large-businesses-47-million-per-year/https://www.panopto.com/resource/ebook/valuing-workplace-knowledge/
McKinsey Global Institute - Employee time spent searching for informationhttps://wikiteq.com/post/hidden-costs-poor-knowledge-management (citing McKinsey Global Institute report)
Deloitte - R&D data quality and work duplicationhttps://www.deloitte.com/uk/en/blogs/thoughts-from-the-centre/critical-role-of-data-quality-in-enabling-ai-in-r-d.html
Starmind / PepsiCo R&D Case Studyhttps://www.starmind.ai/case-studies/pepsico-r-and-d
AWS - Retrieval-augmented generation documentationhttps://aws.amazon.com/what-is/retrieval-augmented-generation/
McKinsey - RAG technology analysishttps://www.mckinsey.com/featured-insights/mckinsey-explainers/what-is-retrieval-augmented-generation-rag
Deepchecks - Enterprise RAG systemshttps://www.deepchecks.com/bridging-knowledge-gaps-with-rag-ai/
This article was powered by Cypris, an R&D intelligence platform that helps enterprise teams unify internal project knowledge with external innovation data from patents, scientific literature, and market intelligence. Discover how leading R&D organizations use Cypris to capture tribal knowledge, eliminate duplicate research, and accelerate innovation from a single centralized hub. Book a demo at cypris.ai
Knowledge Management for R&D Teams: Building a Central Hub for Internal Projects and External Innovation Intelligence
Blogs
.jpeg)
Double patenting is a complex issue that often arises in the U.S. legal system, creating potential challenges for R&D managers, engineers, and scientists alike. This advanced blog post will delve into the intricacies of double patenting and provide valuable insights to help you navigate this multifaceted area of patent law.
We will begin by exploring the statutory prohibition against double patenting as well as obviousness-type double patenting (OTDP) in detail. Following this, we’ll discuss some notable challenges to OTDP’s legality through case examples such as SawStop Holding LLC.
Furthermore, our analysis will cover terminal disclaimers as a means for overcoming ODP rejections and their associated limitations. Finally, we’ll outline practical strategies for avoiding double patent issues including drafting narrower claims, filing divisional applications, and sequential prosecution of separate filings.
Table of Contents
- Double Patenting in the U.S. Legal System
- Statutory Prohibition Against Double Patenting
- Obviousness-Type Double Patenting (OTDP)
- Challenges to OTDP’s Legality
- SawStop Holding LLC Case Example
- Terminal Disclaimers for Overcoming ODP Rejections
- Limitations Imposed by Filing Terminal Disclaimers
- Strategies for Avoiding Double Patent Issues
- Drafting Narrower Claims
- Filing Divisional Applications
- Sequential Prosecution of Separate Filings
- Conclusion
Double Patenting in the U.S. Legal System
Double patenting is a legal concept that prevents inventors from obtaining multiple patents on the same invention, ensuring fair competition and preventing unjust extensions of monopoly power. Rooted in Article 1, Section 8 of the U.S. Constitution and codified in 35 U.S.C. §101, double patenting can be divided into two types – the statutory prohibition against double patenting and obviousness-type double patenting (OTDP).

Statutory Prohibition Against Double Patenting
The statutory prohibition against double patenting arises directly from the language of the Patent Act. According to this provision, an inventor may only obtain a single patent for each distinct invention they create. The United States Patent and Trademark Office (USPTO) examines each application to ensure that it does not claim subject matter already covered by an earlier-filed or earlier-issued patent.
Obviousness-Type Double Patenting (OTDP)
In contrast to statutory prohibitions, OTDP is a nonstatutory doctrine developed by courts as part of their authority to create substantive patent law. This type of double-patenting issue occurs when two related applications or patents have claims that are considered “patentably indistinct,” meaning they would be deemed obvious variations over one another if compared side-by-side during a hypothetical patent trial.
The purpose of OTDP is to prevent an inventor from obtaining multiple patents with claims that are not patentably distinct, thereby extending their monopoly beyond the patent term granted by Congress. This doctrine has been upheld and refined in various court decisions, such as those involving Magna Electronics and Geneva Pharmaceuticals.
In order to avoid double patenting issues during the application process, it’s essential for R&D managers, engineers, scientists, and other professionals involved in innovation to understand both statutory prohibitions and OTDP principles. By being aware of these legal concepts when drafting applications or managing portfolios containing related inventions or families of patents owned by a single entity (COO) under a common control (e.g., parent company), teams can minimize risks associated with the overlapping subject matter while maximizing the potential value derived from their intellectual property assets.
Double patenting in the U.S. legal system is a complex issue that has been subject to debate and judicial interpretation for many years. Challenges to obviousness-type double patenting (OTDP) have recently come into focus with cases such as SawStop Holding LLC, which will be discussed further in the next heading.
Key Takeaway:
Double patenting is a legal concept that prevents inventors from obtaining multiple patents on the same invention, and it can be divided into two types – the statutory prohibition against double patenting and obviousness-type double patenting (OTDP). The purpose of OTDP is to prevent an inventor from obtaining multiple patents with claims that are not distinct, thereby extending their monopoly beyond the patent term granted by Congress. It’s essential for R&D managers, engineers, and scientists to understand both statutory prohibitions and OTDP principles to avoid risks associated with the overlapping subject matter while maximizing the potential value derived from intellectual property assets.
Challenges to OTDP’s Legality
The doctrine of obviousness-type double patenting (OTDP) has been challenged by some as unconstitutional since it goes beyond what Congress intended under 35 U.S.C. §101. Critics contend that the OTDP’s non-statutory nature permits courts and USPTO to formulate patent law, a prerogative that should solely be retained by Congress.
One notable challenge comes from SawStop Holding LLC, who sued after their claims were rejected based on OTDP grounds due to similarities with another previously issued SawStop-owned patent.
SawStop Holding LLC Case Example
In a recent patent trial, SawStop argued that its later-filed patent application was improperly rejected because it was not “patentably indistinct” from an earlier-issued patent owned by the same company. The court ultimately upheld the rejection based on obviousness-type double patenting, but this case highlights ongoing concerns about whether such rejections are legally justified.
In response to these challenges, proponents of OTDP maintain that it serves important public policy goals by preventing unjust extensions of monopoly power through multiple patents covering essentially the same invention or obvious variations thereof. They point out that although not explicitly codified in statutes like the statutory prohibition against double patenting, courts have long recognized and applied this doctrine in various forms throughout history as part of their inherent authority over matters relating to patents.
To date, no Supreme Court decision has directly addressed the constitutionality of obviousness-type double patenting, leaving the issue unresolved. However, it remains an important consideration for R&D managers and engineers when filing multiple related patents.
The legal challenges of OTDP are complex and can be difficult to navigate, but filing a terminal disclaimer may offer an effective solution. Nevertheless, filing a terminal disclaimer has restrictions that must be considered.
Critics challenge the legality of obviousness-type double patenting, while proponents argue it prevents unjust extensions of monopoly power. #patentlaw #innovation Click to Tweet
Terminal Disclaimers for Overcoming ODP Rejections
In the world of patent prosecution, terminal disclaimers can be a valuable tool for overcoming obviousness-type double patenting (OTDP) rejections. A terminal disclaimer is a legal document filed by the applicant to overcome an ODP rejection while agreeing to limit the term of their second patent so that it expires at the same time as their first one. This approach allows inventors and companies to secure patents on related inventions without ignoring OTDP rules.
Limitations Imposed by Filing Terminal Disclaimers
- Reduced Patent Term: By filing a terminal disclaimer, applicants agree to reduce any potential Patent Term Adjustment awarded for overcoming delays during prosecution. This means that if your later-filed patent would have otherwise enjoyed an extended term due to such adjustments, you will lose this benefit when you file a terminal disclaimer.
- Common Ownership Requirement: In order for a terminal disclaimer to be effective in overcoming an OTDP rejection, both patents must remain under common ownership throughout their entire terms. If either patent is not kept in the same ownership or given out separately, this could lead to one or both patents becoming invalid.
- No Revocation: A significant limitation imposed by filing a terminal disclaimer is its irrevocability once accepted by the United States Patent and Trademark Office (USPTO). This means that even if circumstances change, the applicant cannot revoke or modify the terminal disclaimer to extend the patent term.
Despite these limitations, filing a terminal disclaimer can be an effective strategy for overcoming OTDP rejections and securing patents on related inventions. Before making a decision, it is essential for applicants to thoroughly assess their choices and seek counsel from proficient patent lawyers.
Terminal disclaimers can be a useful tool to overcome double patenting rejections, but they also come with certain limitations that should be considered. To further reduce the risk of encountering such issues, it is important to consider strategies like drafting narrower claims and filing divisional applications or sequential prosecution of separate filings.
Key Takeaway:
A terminal disclaimer is a legal document that can help overcome obviousness-type double patenting (OTDP) rejections by agreeing to limit the term of the second patent. However, filing a terminal disclaimer has limitations such as reduced patent terms and common ownership requirements, which should be carefully considered before deciding on this approach.
Strategies for Avoiding Double Patent Issues
To minimize issues related to overlapping subject matter across different commonly owned applications or families, applicants should consider alternative strategies. These include drafting narrower claims focused on specific aspects unique within each invention, filing divisional applications prior to the issuance of original patents that might trigger subsequent rejections based upon similarities identified between them later on down the line when examined side-by-side against one another, and prosecuting these separate filings sequentially rather than concurrently whenever possible.
Drafting Narrower Claims
One effective strategy for avoiding double patenting issues is to draft narrower claims that focus on specific aspects unique within each invention. By doing so, you can ensure that your patent application does not overlap with any earlier-filed patents or pending applications under common ownership.
This approach requires a thorough understanding of both the prior art and the inventive concepts in order to craft claims that are both novel and non-obvious while still providing adequate protection for your innovation.
Filing Divisional Applications
In some cases, it may be beneficial to file divisional applications before an original patent is issued. This allows inventors to split their inventions into separate filings with distinct claim sets targeting different aspects of their technology.
Filing divisional applications early in the process can help prevent potential obviousness-type double patenting (OTDP) rejections by ensuring there are no substantial overlaps between parent and child application claims during an examination at the United States Patent and Trademark Office (USPTO).
Sequential Prosecution of Separate Filings
Another strategy to avoid double patenting issues is the sequential prosecution of separate filings. This approach involves prosecuting one application at a time, allowing the applicant to address any potential OTDP concerns raised by examiners before moving on to subsequent applications within their portfolio.
By addressing these issues early in the process and making necessary amendments or disclaimers as needed, applicants can reduce the likelihood of facing rejections based on double patenting during later stages of examination.
Avoiding double patenting issues requires careful planning and strategic execution throughout the entire patent application process. By employing tactics such as drafting narrower claims, filing divisional applications early in the process, and engaging in sequential prosecution when appropriate, inventors can minimize potential obstacles related to overlapping subject matter while maximizing protection for their innovative technologies.
Key Takeaway:
To avoid double patenting issues, R&D and innovation teams should consider strategies such as drafting narrower claims, filing divisional applications early in the process, and prosecuting separate filings sequentially. By doing so, inventors can minimize potential obstacles related to overlapping subject matter while maximizing protection for their innovative technologies.
Conclusion
In conclusion, it is crucial for R&D managers, engineers, product development teams, scientists, and senior directors involved in research and innovation to understand the implications of Obviousness-Type Double Patenting (OTDP). By recognizing the origins of OTDP in 35 U.S.C. §101 and the federal district court’s recognition of it, companies can avoid potential legal issues that may arise from overlapping patents.
Strategies such as careful claim drafting to avoid obviousness arguments overlap, filing divisional applications before issuance of original patents, or prosecuting each individual case separately can help overcome double-patenting issues during the patent application process.
Take your R&D and innovation teams to the next level. To ensure a smooth patent application process without any double-patenting issues, consult with Cypris today!
Reports
Webinars
.png)
In this session, we break down how AI is reshaping the R&D lifecycle, from faster discovery to more informed decision-making. See how an intelligence layer approach enables teams to move beyond fragmented tools toward a unified, scalable system for innovation.
.png)
In this session, we explore how modern AI systems are reshaping knowledge management in R&D. From structuring internal data to unlocking external intelligence, see how leading teams are building scalable foundations that improve collaboration, efficiency, and long-term innovation outcomes.
.avif)




%20-%20Textile%20Innovations%20in%20Healthcare.png)
%20-%20Technology%20Trends%20in%20Industrial%20Robotics.png)
.png)