1. Getting the Most out of your Patricia Installation
PUG 2016
April 3rd - 5th

2. Why do we do this? Otto: http://www.pckip.com/otto
PUG Budapest, Hungary
April 3rd – 5th
Why do we do this?
Otto:
Patricia platform is well thought out
Database structure
Archived file directory structure
Client/server architecture
Security/responsibility
Leverage existing structure
Extend
Improve interactivity
Integrate
Speaker: TAC
TAC jump in with business reasons for Otto
Focus is automation – having workflows run with as little human intervention as possible
Speaker: RCT
For Patricia platform, existing structure

3. How do we do this? Integration with existing Patricia infrastructure
PUG Budapest, Hungary
April 3rd – 5th
How do we do this?
Integration with existing Patricia infrastructure
Direct database reads/writes
Direct file reads/writes to archived documents
Mimic Patricia functionality
Both interactive and non-interactive programming
Web-based portals (billing, reports)
Thick client based tools (Outlook Add-In)
Automated tools (pckdocs, patent scraper)
Speaker: RCT

4. What do we do? Web-based billing system
PUG Budapest, Hungary
April 3rd – 5th
What do we do?
Web-based billing system
Middleware between Patricia and NetSuite
Allows for Clerk->Professional approval process
Allows for ad hoc trust and discount application
Web-based timer widget
Automated invoice sending in PDF (w/previews)
Uses combination of Patricia and custom DB
Leverages Patricia workflows, terms lists
Demo of maintenance fee payment
First we have some terms set up in Patricia (Maintenance Fee; Case: P1452CA10 have it at term number and advance it to )
Explain that AUTO will prepare the bulk maintenance fee and send it to CIPO (and that we even track once they are paid by scraping the CIPO site)
AUTO faxes CIPO the bulk maintenance fee through an ->fax portal and advances to term to await fax confirmation, charge drops (show charge screen)
When the fax confirmation comes back, AUTO processes the confirmation and automatically advances the term and spawns for AUTO to report to the client (also spawns to scrape CIPO)
That night, AUTO sends the report to the client that maintenance fee has been paid
Log in as a clerk (chlee/310daystillchristmas)
Then we add time charges with the timer (499999T)
Show line notes and history
Show inline editing of quantity and prices
Duplicate a line and then delete it, show charge screen in Patricia
Then we group
Then we apply a discount
Click approve button show that it goes green
Then we go to invoice screen
Show what it looks like and how invoices go out automatically that night

5. What do we do? (cont’d) Patent scraper Utilizes EPO OPS API
PUG Budapest, Hungary
April 3rd – 5th
What do we do? (cont’d)
Patent scraper
Utilizes EPO OPS API
Nightly scanning/downloading of publications
Follows Patricia workflows
Updates diary fields, dockets publications
Also scrapes CIPO for maintenance fee payment confirmation

6. What do we do? (cont’d) Sortspoke Semi-automatic docketing
PUG Budapest, Hungary
April 3rd – 5th
What do we do? (cont’d)
Sortspoke
Semi-automatic docketing
Very generic
Scanned documents are OCRed using AI
Automated system validates data
Updates diary fields, dockets document to Patricia Documents tab, s relevant parties
Advances to reporting term which PCKDocs will deal with automatically
Speaker: RCT
Turn off sortspoke on wiki server
Do a filing receipt, set up terms accordingly
Set up case with one thing that doesn’t match CIPO document (TITLE) (P1452CA11)
Show CAT 3 “waiting for filing receipt”
Login as
Show sortspoke process with “mock” scan and then sortspoke.pckip.com (drag to filing receipt)
Click extract
Process the text fields
Log in to dropbox
Show document in DropBox
On wiki server, go to /opt/sortspoke and run “sudo php sortspoke.php”
Show error
Fix TITLE and advance to term 801
Run sortspoke on wiki server
Show docketed and document attached to docs tab
Show term advancement and term at point where PCKDocs sends report automatically

7. What do we do? (cont’d) Automated citation copier and IDS preparation
PUG Budapest, Hungary
April 3rd – 5th
What do we do? (cont’d)
Automated citation copier and IDS preparation
Automatically copies citations to related cases
Follows country-specific logic
Assembles the IDS submission documents
Notifies professional for electronic signature
Notifies clerk with term with attached documents
Set up a parent case with a bunch of citations (P1814CA00)
Make sure it has 3 related cases (one by family, two by extended whatever) (P1814US00 (one same citation); P2750US00 (all different citations); P2750EP00)
Show that the citations aren’t already there, or if they are, show that it only copies new ones
Set the term on the parent case (Show citations tab & advance CAT 2 workflow to AUTO step)
Run the job queue (EXEC sp_PCK_job_queue_processor)
Show that the citations copied with country-specific logic (sets Prior Art Submission BD on US cases)
Go to case P2750US00
Show mock clerk review and advance term (221005) for PCKDocs to create IDS (advance CAT 2)
Run uspto_ids template on PCKDocs (sudo php process_document.php uspto_ids template_name:P307US~matter_id:P2750US00~event_scheme_id: false)
Show documents prepped for digital signing
Advance to clerk submission step (advance term 960 to next term)
Mention that from there clerk submits to USPTO
Mention will auto- to clerk for easier submission to USPTO
Mention that if USPTO had an API, we could auto-submit without clerk intervention

8. What can YOU do? Database integration Structure is easy to learn
PUG Budapest, Hungary
April 3rd – 5th
What can YOU do?
Database integration
Structure is easy to learn
Keys are easy to follow, adhere to
SQL Server allows for adding UDF, SP easily
File integration with docs tab/citations
Deriving locations is simple
Mainly one DB table to reference
Link between terms and documents obvious

9. PUG Budapest, Hungary
April 3rd – 5th
Thank you