You may combine only references that satisfy the two‑prong analogous test under § 103. Each cited disclosure must share the same field of endeavor and be reasonably pertinent to the inventive problem you pose. Non‑analogous references, which fail either prong, cannot be merged without risking an obviousness reversal. Exclude such material; instead treat it as a separate § 102 claim. A analog set preserves your position and strengthens the PTAB review. Continue analysis, and you’ll uncover tactics.

Key Takeaways

• An analogous prior‑art reference must lie in the same field and be reasonably pertinent to the inventive problem.
• If several analogous references individually satisfy those requirements, they may be combined to form a composite obvious‑ness claim.
• The references need not be directly related to one another; their combined teachings can be considered if a PHOSITA could seamlessly merge them.
• Non‑analogous disclosures are excluded from a § 103 obviousness discussion, though they can be cited under § 102 if they meet other novelty criteria.
• A PTAB claim‑chart that links each limitation to multiple analogous references demonstrates the feasibility of such multi‑reference combinations.

Avoiding Unfair Obviousness Rejections: A PTAB Road‑Map

Because the PTAB places the burden of persuasion on the petitioner, you must challenge the examiner’s prima‑facie case of obviousness before the record becomes a liability. Start with an evidence‑management strategy that catalogues every datum supporting nonobviousness—declarations, prior‑art analyses, and internal technical assessments—before the examiner issues its rejection. Your timing strategy hinges on early motion for re‑examination or a petition for discretionary review if the rejections misapply the Graham factors. By filing assertions promptly, you prevent the examiner from preserving the rejection as a dispositive record. Use a clear claim‑chart methodology to map each limitation against the cited references, exposing any gaps that erode the prima‑facie premise. If the examiner assumes hindsight reasoning, insist on the state‑of‑art at file date. Finally, preserve a complete docket file that evidences your proactive resistance, thereby converting the initial obviousness challenge into a PTAB‑friendly narrative. Your record will defend in PTAB hearings. The examiner’s burden is to prove a prima‑facie case of obviousness before the rejection can be sustained.

What Exactly Is Analogous Prior Art?

What defines analogous prior art? It establishes a two‑prong test for § 103 obviousness: either the reference belongs to the same field of endeavor or it is reasonably pertinent to the inventive problem. The person of ordinary skill at the relevant art only needs to be aware of the analogous references, not of any non‑analogous disclosures. The court demonstrates that only the cited references, the analogous references, are considered during obviousness analysis.

Analogous art hinges on a two‑prong § 103 test: same field or problem relevance, no need for non‑analogues.

• The same‑field test focuses on the content of the disclosure, not on external labels.
• Pertinent‑problem references need a clear problem overlap with the invention.
• Multiple references can be combined even if they are not analogously related to one another.
• Non‑analogous art, while admissible for § 102, is excluded from § 103 analysis.
• Federal‑Circuit precedent, such as In re Klein and Sanofi‑Aventis, confirms these doctrines.

This educational overview supplies descriptive examples of how the court distinguishes analogous from non‑analogous art, guiding you through proper search and examination procedures while maintaining legal precision. Proceed with caution and diligence today.

Same‑Field vs. Pertinent‑Problem Tests

Although the same‑field and reasonably‑pertinent tests both aim to identify analogous prior art for § 103, they diverge in scope. You apply the field‑of‑endeavor test by checking whether a reference shares field alignment with your invention; if it does, you’ll meet the threshold, regardless of the problem it solves. This test does not look for problem relevancy, making it broad and decisive without further analysis. Conversely, the reasonably‑pertinent test triggers when a reference falls outside that field. You must show that the reference addresses at least one problem your invention tackles, and that a person of ordinary skill will turn to it in that context. Here, problem relevancy is paramount; the PHOSITA must view the reference as a solution. Failure to define the problem broadly risks collapsing the tests, a reversible error under Federal Circuit precedent. Therefore, you’ve got to balance field alignment against problem relevancy to avoid over‑narrowing.

But the PTAB omitted expert testimony illustrating why a 1999‑2000 pedalboard inventor might consult 1970s relay tech, undermining the analogous art assessment.

Airbus S.A.S.: Applying the Same‑Field Test

If you scrutinize the A350 certification testing, you’ll see it aligns squarely with the field of aircraft certification, the exact domain of the claimed invention. The fourteen‑month flight‑test campaign, the 2,600‑hour sortie log, and the twin authority approvals demonstrate that the aircraft satisfies every regulatory benchmark. The structural static studies, including maximum wing bending and fuselage pressure, mirror the stresses the invention anticipates. Pilot evaluation data derived from simulated commercial services and real‑crew assessments confirm operational reliability under extreme weather simulation. These results show that the tested characteristics fall within the same technical field, supporting that any use of the claimed system is a lawful combination of referenced testing.

• Over 2,600 flight hours articulated.
• Weather simulation spanned –40°C to +40°C.
• Pilot evaluation utilized actual airline crews.
• Structural tests replicated in‑flight micro‑gravity loads.
• Compliance achieved under EASA and FAA standards.

Static tests exceeded the design lifetime by 3× the design lifetime, confirming an extra safety margin.

ICON Health: Matching the Inventor’s Problem

Draft:

Building on the Airbus example, ICON Health faces a challenge in which mismatched constraint types trigger modeling errors. iMate connections require identical constraint types and offset values, a rule that applies even when naming conventions differ. You shall enforce Constraint Integrity by using the Design Doctor to identify relationship issues before they cascade. Visual Diagnosis becomes essential: the Show Sick Constraints function marks problematic constraints as glyphs, allowing you to right‑click and edit them directly. When geometry shifts, these sick glyphs alert you to broken connections that need re‑association. Overconstraining within sketches leads to dependency conflicts, so balance Coincident, Concentric, and Tangent constraints, and remove redundancies via the Edit Feature option. Consistent iMate ordering stabilizes assemblies; grounding bases prevent floating references. By systematically resolving broken projections and maintaining proper ordering, you achieve a robust modeling workflow.

Now count words.

Let’s count manually.

1 Building

2 on

3 the

4 Airbus

5 example,

6 ICON

7 Health

8 faces

9 a

10 challenge

11 in

12 which

13 mismatched

14 constraint

15 types

16 trigger

17 modeling

18 errors.

19 iMate

20 connections

21 require

22 identical

23 constraint

24 types

25 and

26 offset

27 values,

28 a

29 rule

30 that

31 applies

32 even

33 when

34 naming

35 conventions

36 differ.

37 You

38 shall

39 enforce

40 Constraint

41 Integrity

42 by

43 using

44 the

45 Design

46 Doctor

47 to

48 identify

49 relationship

50 issues

51 before

52 they

53 cascade.

54 Visual

55 Diagnosis

56 becomes

57 essential:

58 the

59 Show

60 Sick

61 Constraints

62 function

63 marks

64 problematic

65 constraints

66 as

67 glyphs,

68 allowing

69 you

70 to

71 right‑click

72 and

73 edit

74 them

75 directly.

76 When

77 geometry

78 shifts,

79 these

80 sick

81 glyphs

82 alert

83 you

84 to

85 broken

86 connections

87 that

88 need

89 re‑association.

90 Overconstraining

91 within

92 sketches

93 leads

94 to

95 dependency

96 conflicts,

97 so

98 balance

99 Coincident,

100 Concentric,

101 and

102 Tangent

103 constraints,

104 and

105 remove

106 redundancies

107 via

108 the

109 Edit

110 Feature

111 option.

112 Consistent

113 iMate

114 ordering

115 stabilizes

116 assemblies;

117 grounding

118 bases

119 prevent

120 floating

121 references.

122 By

123 systematically

124 resolving

125 broken

126 projections

127 and

128 maintaining

129 proper

130 ordering,

131 you

132 achieve

133 a

134 robust

135 modeling

136 workflow.

Count: 136 words. Need 148. Need 12 more words.

Add sentence: “These measures guarantee dependable assemblies that satisfy regulatory compliance and reduce field corrections.”

Count words of that sentence: These(1) measures(2) guarantee(3) dependable(4) assemblies(5) that(6) satisfy(7) regulatory(8) compliance(9) and(10) reduce(11) field(12) corrections(13). That’s 13 words. We need 12 more. Remove one word. Maybe remove “dependable”. So sentence becomes: “These measures guarantee assemblies that satisfy regulatory compliance and reduce field corrections.”

Count: These(1) measures(2) guarantee(3) assemblies(4) that(5) satisfy(6) regulatory(7) compliance(8) and(9) reduce(10) field(11) corrections(12). 12 words. Good.

Add as final sentence. Update total count: 136 +12 =148 exactly.

Now produce final 148-word paragraph.Building on the Airbus example, ICON Health faces a challenge in which mismatched constraint types trigger modeling errors. iMate connections require identical constraint types and offset values, a rule that applies even when naming conventions differ. You shall enforce Constraint Integrity by using the Design Doctor to identify relationship issues before they cascade. Visual Diagnosis becomes essential: the Show Sick Constraints function marks problematic constraints as glyphs, allowing you to right‑click and edit them directly. When geometry shifts, these sick glyphs alert you to broken connections that need re‑association. Overconstraining within sketches leads to dependency conflicts, so balance Coincident, Concentric, and Tangent constraints, and remove redundancies via the Edit Feature option. Consistent iMate ordering stabilizes assemblies; grounding bases prevent floating references. By systematically resolving broken projections and maintaining proper ordering, you achieve a robust modeling workflow. These measures guarantee assemblies that satisfy regulatory compliance and reduce field corrections.

Every Reference Needs Its Own Analogy

Every reference warrants a unique analogy, because comparing it to a familiar concept reveals its functional role.

Analogies link unrelated subjects to clarify concepts.

Your analysis must consequently treat each citation as an independent case wherein a distinct parallel illuminates its operative mechanics.

Construct a custom equivalent that maps the prior art’s purpose onto the domain you seek to protect.

• Treat the reference as a source‑to‑product analogy like a baker and dough; this frames transformation.
• Map the reference’s function to a familiar tool; the knife‑to‑scissors comparison highlights utility.
• Connect component parts to the whole, analogizing a brick to a wall as a cell to the body.
• Use cause‑to‑effect parallels, e.g., studying effort to grades, to show expected outcomes.
• Guarantee each analogy employs parallel verbs and structured phrasing for logical cohesion.

When you establish these distinct parallels, you provide the examiner with an unmistakable, custom equivalent that clarifies how each referred item supports your claim and rationale.

Examiner Duties Under MPEP 2141.01(a)

When weighing a prior art reference, the examiner must decide whether it qualifies as analogous art under MPEP 2141.01(a). You must apply the two‑prong test: same field of endeavor or reasonably pertinent to the problem faced by the inventor. The examiner must also apply the KSR principle that a claim is obvious if it offers more than a predictable use of a prior‑art feature. In the same‑field test, the examiner evaluates the field from the ordinary‑skill perspective, ignoring purpose differences, as in In re Bigio. For the pertinent test, you must infer the problem from the specification, relying on PHOSITA reasoning; cross‑field references become viable if they address related issues, as seen in Sanofi‑Aventis v. Glenmark. These process requirements demand that you conduct a scope analysis that treats the claimed invention as a whole, setting aside applicant disclosures to avoid hindsight. Documentation standards oblige you to record every factual finding, the state of the art, and the reference teachings. If you fail to establish a prima facie case, the applicant bears no burden to rebut.

Analogous Prior‑Art Drafting Playbook

Although claim drafting traditionally focuses on technical disclosure, you must articulate the invention’s essential features so that they line up with the same‑field or reasonably‑pertinent analogues defined in MPEP 2141.01(a).

The CAFC’s Donner decision confirms that analogues can be grouped by a common technical problem even when spanning different fields.

Your drafting strategy must distinguish the claim problem, shielding it from irrelevant analogues. Guide selection of reference art by emphasizing the same‑field link, then judge relevance under the reasonably‑pertinent test. You should exhibit how each cited reference discloses the same essential feature set you protect. Propagate expert support early to preclude prosecution arguments that treat the reference as context. Finally, maintain specification language that resists claim construction criticism while overlapping on essential technical facts.

• Embrace field phrasing to encompass your invention’s core functions.
• Pinpoint a narrowly defined problem to exclude non‑analogous art.
• Tie each cited reference to an essential disclosed feature set.
• Secure early expert precedent to preclude later procedural analogies.
• Draft specification with claim‑construction resilience and technical granularity.

Common Pitfalls in Analogous‑Prior‑Art Petitions

These pitfalls demonstrate that a narrow field of endeavor or an insufficient demonstration of reasonable pertinence can render an analogous‑prior‑art petition ineffective.

The precedent set in Airbus S.A.S. clarifies that a reference outside the original field can still be analogous if it addresses the same technical problem.

You’ll find that limiting the field to the patent’s exact application—an error repeated in *Donner Tech.*—violates the two‑prong test and erodes deference limits. A failure to prove reasonable pertinence, as highlighted in *In re Bigio* and *Daedalus Blue*, invites PTAB dismissal. When you omit expert testimony, you expose your petition to judicial scrutiny, clashing with industry trends that favor evidence‑based analysis. To avoid defeat, you must address both prongs, gather substantive evidence, and align your arguments with the PTAB’s factual nature and established deference limits. Your argument must also anticipate potential counter‑specificity challenges to preserve admissibility in filings.

Pitfall	Common Error	Remedy
Narrow field	Over‑defining scope	Cite broad, related art
No pertinence	Ignoring problem relevance	Provide comparative data
Lack evidence	Missing expert opinion	Submit qualified testimony

Frequently Asked Questions

Can Unrelated Prior Art Be Combined if a Skilled Artisan Sees Them as a Solution?

Yes, you may combine unrelated prior art when a skilled artisan’s cognitive mapping aligns disparate solutions to the same problem, effectively problem refocus. Courts allow such synthesis if the combination yields an obvious result to a person of ordinary skill, provided you present clear, fact‑based rationale. You must show that the artisan would naturally integrate the references, arguing through technical insight rather than mere speculation, ensuring compliance with 35 103.

Is It Permissible to Combine References That Each Lack Independent Analogous Relevance?

Yes, you can combine references that each lack independent analogous relevance, provided you bridge their relevance gaps and show coherence thresholds through a predictable combination. You’d need to prove that a person of ordinary skill would see a motivational linkage that overcomes the absence of analogous relevance in each reference, and that the merger produces predictable results at the time of the invention to justify such a construction within law.

How Do Technical Disclosures in Post‑Grant Notifications Affect Analogical Combinations?

As the saying goes, you can’t ignore what’s been disclosed. You note that each post‑grant notification carries significant notification weight, and you must treat the disclosure scope as the ultimate determinant of analogical combination admissibility. In practice, you include only references that meet the statutory criteria, and you exclude those lacking independent analogous relevance. You consequently limit your analogical combinations to the pool of properly disclosed references you hold today.

Does Merging Analogies Across Differing Fields Enhance Obviousness Rejections?

Yes, merging analogies across differing fields typically bolsters obviousness rejections because the court deems it a cross‑disciplinary logic that satisfies the motivation to combine. Under KSR, a skilled artisan must have a conceptual synthesis that evokes an evident advance. If you present disparate embodiments, the examiner can assume hindsight, but only if the combined references are analogous to the claim. This judicious narrowing prevents abuse of multi‑reference breadth and enforces limits.

Can Prior Art Citing Only the Problem Logic but Not the Solution Be Combined?

You can combine references that only state the problem logic, as long as they collectively frame your invention’s solution. Think of a culinary expert mixing spices from separate kitchens—he understands the flavor intent yet crafts a unique dish. This approach aligns with the problem‑solution paradigm: each reference contributes Problem Logic; the claim delivers Solution Avoidance. Therefore, the court accepts such combinations when they collectively illuminate the inventive step.

Conclusion

You can now navigate the labyrinth of obviousness rejections with confidence, armed with a systematic roadmap tailored to the PTAB’s rigorous standards. By rigorously applying the same‑field and pertinent‑problem tests, drafting individual analogies, and understanding examiner obligations under MPEP 2141.01(a), you eliminate ambiguity. Remember, each reference is a unique doorway—close attention to detail will prevent the door of denial from ever opening. Master these tools, and the patent process becomes a well‑charted odyssey for you.