AcclaimIP HelpRecent Updates

Recent Updates

  • Updated on: Mar 15, 2022

    Importing Custom Data into AcclaimIP

    Data may be imported into AcclaimIP's custom fields in bulk.  For example, you may wish to export some data from your IAM software platform and enter it into AcclaimIP for your searchers to leverage.  

    The most common data imported into AcclaimIP include:

    1. Rating Systems:  Is the patent any good?
    2. Taxonomies:  Where does the patent apply?
    3. Legal Data:  Internal Document Numbers, Litigation Status, Abandonment Dates

    Integrating your internal data into AcclaimIP is a great way to leverage past work with your IP team.

    Administrators can import data to all custom fields in a single import attempt.  However, when you are learning the process, we recommend you start with a single field before you tackle importing 25 fields or more at one time.


    The data used in these examples are entirely made up for demonstration purposes and do not represent any entity's custom data.

  • Updated on: Mar 15, 2022

    Managing Users & Groups

    The Managing Users feature is designed to:

    • Create groups
    • Add and remove users from groups
    • Give certain users custom field admin privileges
  • Updated on: Mar 15, 2022

    Managing Custom Data Fields

    If you have Custom Data Fields feature enabled, and you have the rights to administer custom data fields, you'll see several new options in your Start menu

  • You may be familiar with the FIELD field code to find empty data fields in any normal AcclaimIP patent data field.  The FIELD field code also works for custom fields.

    For example, let's say you define a custom field to categorize patents, and you name it "Technology" and give it a field code _TAX.TECH.  Remember all custom field codes begin with a leading underscore character to prevent user-defined field codes from colliding with AcclaimIP's standard field codes.

    FIELD:isEmpty_TAX.TECH  -->  Finds all patents where the _TAX.TECH custom field contains no data.

    You'll find that you'll use this query quite often when you want to track the progress of some workflow you designed for you and your group.  

    For example, let's say you want to rate and rank your entire portfolio along several dimensions.  You might create custom fields for your rating system, then query the fields for the empty state (or NotEmpty state) to see how many patents are left to rate.

    The inverse is also true:

    FIELD:isNotEmpty_TAX.TECH  -->  Finds all patents with data in the _TAX.TECH custom data field.

  • Just like other data fields, custom fields can be faceted filters.  Remember, a filter lets you refine your search by some data element; the facets are the actual counts within a filter.

    In this example, I created a rating system and tagged about 5000 of Google's patents with rankings.  These data were randomly generated for demonstration purposes and do not represent real opinions on the patents displayed.

    One of the ultimate goals of most patenting organizations is to build a ever-growing knowledgebase that tells users which patents are major inventions, which are incremental improvements and even which are no good at all and slated for abandonment.  The example here uses a simple 4 dimensional rating system including the following criteria.

    • Current Use – Is the invention being used in products today?
    • Detectability – Can use be economically proven in infringing devices?
    • Alternatives – Are there other methods to achieve the same result as the patented invention?
    • Prior Art Risk – What is the likelihood the patent could stand up to extensive prior art search?

    Editorial Opinion:

    This simple system is a good start for your own rating system.  While this is a fairly simple one, simple is often better.  I advise IP managers to develop the simplest possible rating system that will meet your needs.  Overly complex rating systems, while well intentioned and better in theory, virtually always fail due to their complexity.

  • At the document level you can view and/or modify custom data from the Document Details window.  Custom fields appear to the right in an accordion-style panel labeled "Custom Fields."

  • In this current implementation of custom data fields, a known issue is the inability to save documents to a research folder from a query with a custom field field code.

    In other words, if you run a query like _QUAL:Good where _QUAL is a custom data field field code, the documents cannot be directly saved to a research folder.

  • Real patent value comes from value metrics that can only be accurately determined by experts in the field who take the time to read the patents, review the claims, and make judgements to the patent's value.  There are lots of systems for rating patents of varying complexity, but the most basic one, is perhaps the most useful and easiest to implement.  It covers four specific dimensions:

    1. Current Use: Is the patented technology used by current products in high dollar markets?
    2. Alternatives: Are there alternatives that are just a useful and cost about the same (or less) to implement in an infringing device.
    3. Detectability:  How difficult is it to show the patented technology's use in an infringing device?
    4. Prior Art Risk:  Is there known prior art, or on the other extreme, has the patent's validity been tested in court.

    AcclaimIP users use the custom fields feature to build rating systems, design workflows and rate their own patents along these dimensions.  A rating system, along with a home-grown taxonomy, makes you well-prepared to respond to any offensive or defensive opportunity you are presented with.

  • Updated on: Mar 03, 2022

    Inclusion and Exclusion Lists