Attachment 26 - DCB 2019-01 (7).docx
DOCX document 40 KB Posted
- Attached to
- Patent Data and Document Management
- Solicitation number
- ACQ-20-0057
About this file
This document outlines requirements for a federal contract to provide patent data and document management services to the United States Patent and Trademark Office. The contractor will perform front-end processing including indexing and scanning paper documents and quality review of electronic filings to create the official electronic file wrapper. Additional requirements include patent data capture and composition of applications for pre-grant publication and patent grants. The contractor will convert and compose data from various sources for publication and issuance on a weekly basis in compliance with quality standards. Specific services required are front-end processing, pre-grant publication, post-allowance processing, post-issuance processing, and associated quality control and customer support. The contract will have a period of performance through production schedules and issue dates provided in the solicitation.
View the file
Other files
Show 40 more
Latest 50 of 118 listed here. See the rest on GovTribe.
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
D a t a C a p t u r e B u l l e t i n
Number 2019-8 April 25, 2019
WHEN THE PaDaCap CONTRACTOR HAS
A QUESTION ABOUT
THE ALLOWED APPLICATION’S
SEQUENCE LISTING
The information in this bulletin will be included in the 2020 revision of
DATA ENTRY MANUAL FOR UTILITY PATENTS.
*** This bulletin is effective immediately. ***
See DATA ENTRY MANUAL FOR UTILITY PATENTS,
34. Sequence Listing.
The following instructions are added immediately after the heading Pre-Capture Verification.
when PaDaCap contractor needs USPTO assistance with Sequence Listing. If there is a question about the allowed application’s Sequence Listing, the PaDaCap contractor will send a printer RUSH to the examiner only in the following limited circumstances:
1. During the processing of that allowed application, USPTO personnel instruct the PaDaCap contractor to send a printer RUSH.
2. The allowed application is very clearly a Sequence Listing case, but there is no Sequence Listing in the application.
3. The allowed application is very clearly a Sequence Listing case, but the most recently filed CRF has code CRFD (Computer Readable Form Defective) in IFW.
For all other questions pertaining to the Sequence Listing in an allowed application, the PaDaCap contractor will contact the STIC Sequence Systems Service Center (SSSC) via e-mail to the following:
| Kathleen.Kalafus@uspto.gov |
| Roane.Noel@uspto.gov |
| STIC-SSSCHelpdesk@uspto.gov |
The goal is to prevent examiners from having to deal with Sequence Listing problems when such problems may be resolvable by the support personnel in SSSC. In some instances—see circumstance 1 above—the SSSC may instruct the PaDaCap contractor to send a RUSH to the examiner.
“For all other questions” above includes the question of whether the Sequence Listing requirement needs to be met in, for example, an application (abstract, specification, claims, drawings) that contains SEQ ID numbers but no Sequence Listing, or an application that contains a small number of nucleotide symbols or amino acid symbols but no Sequence Listing. In such an application it is not the task of the PaDaCap contractor—for example, by counting the number of nucleotide or amino acid symbols—to make the decision as to whether a Sequence Listing is required. Such a decision should be made by the SSSC via e-mail as described above, and if instructed by the SSSC to do so, the PaDaCap contractor will then send a printer RUSH so that the examiner and the applicant can resolve the problem.
34. Sequence Listing, Data Source.
Immediately following the illustration of the SCORE placeholder sheet, the nine-line paragraph beginning “When the Sequence Listing has been filed as an ASCII .txt file via EFS-Web, the PaDaCap contractor will not initiate any ‘printer rush’ query” is deleted.
34. Sequence Listing, Pre-Capture Verification.
In the subsection with the side-heading current verification practice, the sentence beginning “A ‘printer rush’ QUERY will” is deleted.
In the subsection with the side-heading weekly PUBS Sequence Report, the sentence beginning “The Office of Data Management will” is deleted.
In the subsection with the side-heading weekly PUBS Sequence Report, the sentence beginning “The PaDaCap contractor will” and the two query guidelines are deleted.
In the subsection with the side-heading letter requesting transfer of CRF from one application to another, the query guideline is deleted.
In the subsection with the side-heading weekly export of CRFs from USPTO to PaDaCap contractor, the sentence beginning “If the PaDaCap contractor does not receive”
34. Sequence Listing, Exception Processing When Sequence Listing is One Gigabyte or More.
See the subsection with the heading PaDaCap contractor’s renaming and repackaging of 1GB-or-larger Sequence Listing for Grant issuance.
In the paragraph beginning “The PaDaCap contractor will perform” the second sentence (“If there are discrepancies …”)
Appendix N: EFS-Web and SCORE (Grant and Pre-Grant),
3. SCORE Exports to PaDaCap Contractor, Sequence Listing CRFs.
In the subsection with the side-heading PGPub and Grant, the sentence beginning “PaDaCap contractor ‘on demand’ requests” is revised to say “PaDaCap contractor ‘on demand’ requests will be directed to the STIC Sequence Systems Service Center (SSSC).”
Appendix N: EFS-Web and SCORE (Grant and Pre-Grant),
3. SCORE Exports to PaDaCap Contractor, Sequence Listing CRFs.
In the subsection with the side-heading PGPub and Grant, the sentence beginning “However, when the Sequence Listing CRF” is revised to delete the words “and the PaDaCap contractor will not query to ask for one.”
DCB No. 2019-8 Office of Data Management Page 1 of 6
File details come from the government source that posted it. Updated .