Attachment 03b - USPTO Enterprise Workstation Naming Convention.docx
DOCX document 22 KB Posted
- Attached to
- Patent Data and Document Management (PDDM) Federal contract opportunity
- Solicitation number
- 1333BJ20R00151004
About this file
This document outlines the United States Patent and Trademark Office's naming convention for workstation objects in Active Directory. It specifies a seven position naming structure including a baseline identifier, user identifier, business unit, classification, location, unique identifier, and swap count. Position one indicates whether the image is for patents, trademarks, or enterprise use. Position two identifies government, contractor, or travel computers. Positions three through four denote the business unit such as patents, PTAB, trademarks, or various offices. Position five classifies the workstation as laptop, desktop, virtual, etc. Positions six through seven provide the two character location code. Positions eight through eleven contain a unique number identifier resetting at 0001 for each new combination of positions one through seven. Position twelve increments from A to M for replacement workstations.
The related federal contract opportunity seeks contractor support to manage the entire patent application lifecycle from initial filing through final disposition. Offerors must thoroughly review the RFP, statement of work, references, attachments, and glossary to fully understand the PDDM requirements. The solicitation is issued by the Department of Commerce's United States Patent and Trademark Office for patent data and document management services.
View the file
Other files for this federal contract opportunity
Show all 50
Patent Data and Document Management (PDDM) has more files on GovTribe.
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
USPTO Enterprise Workstation Naming convention
Naming convention for all workstation objects in Active Directory will be categorized into seven sections: sections 1-5 comprise the enterprise standard configuration for the first seven characters and section 6 -7 outlines the remaining characters unique identifier and replacement count.
| ID |
| CHARACTER POSITION |
| DESIGNATION |
| DESCRIPTION/EXPLANATION |
| 1 |
| 1 |
| Baseline |
| Patents, Trademark or Enterprise image |
| 2 |
| 2 |
| User Identifier |
| One character that identifies whether it’s a Fed, Contractor, or Travel computer |
| 3 |
| 3-4 |
| Business Unit |
| Identifies the “root” business unit |
| 4 |
| 5 |
| Classification |
| One character to describe the classification (laptop, desktop, virtual, physical, hoteling, etc…) |
| 5 |
| 6-7 |
| Location ID |
| Two characters to identify the physical location (AL, DA, SH, etc…) |
| 6 |
| 8-11 |
| Unique ID |
| Unique number identifier |
| 7 |
| 12 |
| Swap Count |
| Increments from A – M based on number of swaps |
1. Baseline Identifier (position 1) Classification ID (Char 1)
| Identifier |
| Class |
| P |
| Patents image |
| T |
| Trademark image |
| E |
| Enterprise Image |
2. User Identifier (position 2) Classification ID (Char 1)
| Identifier |
| Class |
| G |
| Government |
| C |
| Contractor |
| T |
| Travel |
3. Organization Identifiers (position 3-4) Business Unit (Char 2)
| Identifier |
| Site Location |
| PT |
| Patents |
| PB |
| PTAB |
| TM |
| Trademark |
| TT |
| TTAB |
| CI |
| OCIO |
| CA |
| OCAO (OHR) |
| CF |
| OCFO |
| US |
| Under Secretary (US, OPIA, OCCO) |
| TR |
| Training |
| GC |
| OGC (OED, OGL, SOL) |
| PP |
| Pre-production |
| CR |
| Conference room |
4. Classification Identifier (position 5) Classification ID (Char 1)
| Identifier |
| Class |
| L |
| Laptop |
| D |
| Desktop |
| H |
| Hoteling |
| S |
| Shared |
| V |
| Virtual |
| C |
| CFE (Contractor Furnished Equipment) |
5. Location Identifier (position 6-7)
Location ID (Char 2)
| Identifier |
| Org |
| AL |
| Alexandria |
| SH |
| Shirlington |
| BY |
| Boyers |
| DT |
| Detroit |
| DE |
| Denver |
| DA |
| Dallas |
| SJ |
| San Jose |
| H4 |
| Hotelling <= 50 |
| H5 |
| Hotelling > 50 |
6. Unique Identifier (position 8-11) Numbers will be reused dependent on position 1-7 identifiers.
Unique ID (Char 4)
| Identifier |
| Description |
| 0001-9999 |
| Unique number identifier |
Unique identifier is based on positions 1-7 and consecutive numbers must be used. Example: 3 federal employees in OCIO. Two in Alexandria and one in Shirlington: First two would be EGCILAL0001A & EGCILAL0002A. The last being EGCILSH0001A. Note that the unique identifier starts at 0001 again.
Active Directory must be used as the authoritative source for naming to ensure no duplicates names are used.
7. Unique Identifier (position 12) Unique ID (Char 1)
| Identifier |
| Description |
| A – M |
| Swap/replacement increment |
File details come from the government source that posted it. Updated .