Starlink Terminal Naming Convention

Created by Corey Buchanan, Modified on Wed, 10 Dec at 11:51 AM by Corey Buchanan

NOC Standard Operating Procedure (SOP)

Title: Starlink Terminal Naming Convention

Owner: Network Operations Center (NOC)

Maintained by: Chris Horton, NOC Technician

Approved by: Corey Buchanan, IT Manager

Version: 1.0

Effective Date: October 13, 2025

Purpose:

To establish a standardized naming convention for all Starlink terminals to ensure clear identification, traceability, and operational efficiency across all deployments and departments.

Scope:

This procedure applies to all NOC technicians and IT personnel responsible for naming or renaming Starlink terminals owned or managed by PDI or MIC. It includes all departments, projects, and field-deployed locations where terminals are utilized.

Responsibilities:

NOC Technicians:

Apply the correct naming convention when activating or auditing a terminal.
Update terminal names in all relevant systems and documentation.
Log all naming activities in ClickUp or the designated task management system.

IT Manager:

Enforce adherence to naming conventions across all teams.
Approve any deviations, new codes, or structure updates.
Audit terminal names for compliance and consistency.

Procedure

Each Starlink terminal must follow the approved naming format.

Use hyphens (-) to separate each component of the name.

Format:

ORG-DEP-LOC-CST-WORKORDER

Component Definitions:

1. ORG (Organization):

Identifies terminal ownership.
Use PDI or MIC.

2. DEP (Department):

Use the standardized department abbreviation.
- Examples:
  - ENG – Engineering
  - OPS – Operations
  - NOC – Network Operations Center

3. LOC (Location):

Use a clear, standardized abbreviation for the city, region, or site.
- Examples:
  - ANC – Anchorage
  - HOU – Houston
  - TAL – Talkeetna

4. CST (Customer):

Use a short abbreviation of the customer or client name.
- Examples:
  - EXX – ExxonMobil
  - DANIEL – Daniel’s Electric
  - ARCTIC – ArcticEdge

5. WORKORDER (Work Order):

Use the assigned work order numberassociated with the installation or service.
- Example: WO12345

Example Terminal Name:

PDI-NOC-HOU-DANIEL-WO12345

Escalation Path

If naming details are incomplete, unclear, or unverified:

Senior NOC Technician – Validate available information and request missing details.
IT Manager – Approve exceptions or resolve conflicts.
Project Manager / Field Services Lead – Provide or confirm project-specific details if required.

Documentation & Logging

Record all terminal names in ClickUp, the Starlink account portal, or the designated NOC tracking platform.
Include the following data:
- Terminal serial number
- Location
- Associated work order
- Name of the technician who created or updated the record
- Timestamp of the change
Validate terminal naming accuracy during QA review and at project closeout.

Notes

Do not use underscores (_), spaces, or special characters — use hyphens (-) only.
Double-check customer name spelling and work order accuracy before finalizing.
All abbreviations must follow company-approved codes for departments and locations.
Contact the IT Manager if an abbreviation or code is not listed or needs to be added.

Revision History

Version

Date

Description

Updated By

1.0

October 13, 2025

Initial SOP Creation

Chris Horton