Activating ATS TLEP SIM Cards in Baicells CloudCore

Created by Corey Buchanan, Modified on Wed, 10 Dec at 4:23 PM by Corey Buchanan

NOC Standard Operating Procedure (SOP)

 

Title: Activating ATS TLEP SIM Cards in Baicells CloudCore
Owner: Network Operations Center (NOC)
Maintained by: Chris Horton, NOC Technician
Approved by: Corey Buchanan, IT Manager
Version: 1.0
Effective Date: October 23, 2025

Purpose:

 To define the standard process for activating SIM cards for Alaska Tribal Spectrum (ATS) TLEP sites using Baicells NOVA246 LTE radios. This ensures all SIM cards are provisioned accurately, efficiently, and consistently within Baicells’ CloudCore system to maintain reliable broadband connectivity for deployed tribal locations.

Scope:

 This SOP applies to all NOC Technicians and Broadband Sentinels involved in the activation of TLEP SIM cards for ATS projects. It specifically covers procedures using the Baicells CloudCore dashboard and the BOSS interface for account setup and verification.

Responsibilities:

 

Broadband Sentinels:
  • Submit a FreshDesk ticket titled: SIM-Activation-[SiteName]
  • Provide accurate IMSI and site information for activation.
NOC Technicians:
  • Activate the SIM card using the Baicells CloudCore portal.
  • Verify activation status and ensure data accuracy.
  • Update and close the FreshDesk ticket once activation is confirmed.
IT Manager:
  • Oversee process adherence and ensure compliance with activation standards.
  • Approve non-standard activations or troubleshooting escalations.

Procedure

Step 1 – Receive Ticket

  1. Confirm receipt of the FreshDesk ticket titled:
  2. SIM-Activation-[SiteName]
  3. Validate that the ticket includes the following details:
    • IMSI number
    • Sentinel name
    • Site location

Step 2 – Access Baicells CloudCore Dashboard

  1. Log in to Baicells CloudCore using authorized credentials.
  2. Navigate to the BOSStab.
    • This section lists all active subscriptions with corresponding details such as IMSI, status, and service plan.

Step 3 – Add New Subscription Line

  1. Click the (+) Add icon at the top of the BOSS table to create a new subscription entry.
  2. Fill in the following fields:
    • Name: Enter the Sentinel’s full name.
    • State/Region: Enter the 2-letter state abbreviation.
    • Town/City: Enter the site or deployment location.
  3. In the IMSIfield:
    • Click the (+) icon to open the IMSI selection panel.
    • Locate and select the provided IMSI.
    • Press OK in the IMSI panel.
  4. Press OK again at the bottom left of the subscription window to save changes.

Step 4 – Verify Activation

  1. Confirm the subscription appears in the BOSS table.
  2. Verify that:
    • The IMSI matches the provided number.
    • The Status displays as Active.
  3. If the status is not active, recheck all entered data for accuracy or escalate the issue.

Escalation Path

If the IMSI cannot be activated or does not appear in the BOSS system:
  1. Senior NOC Technician – Review system data and retry activation.
  2. IT Manager (Corey Buchanan) – Approve further action or escalation.
  3. Baicells Support via ATS escalation – Contact only if internal troubleshooting fails.

Documentation & Logging

All completed activations must be documented as follows:
  • Update the FreshDesk ticket with:
    • Activated IMSI number
    • Activation timestamp
    • Status: Active
  • Mark the ticket as Resolved once activation is confirmed.
  • Record the activation entry including:
    • IMSI number
    • Site name
    • Sentinel name
    • Activation time/date
    • Technician initials

Notes

  • Use only IMSIs assigned by ATS.
  • Ensure the ticket title format follows: SIM-Activation-[SiteName].
  • Double-check spelling, formatting, and IMSI accuracy before saving.
  • Do not assign or activate IMSIs already in use or unapproved.
  • Retain activation confirmation screenshots when applicable.

Revision History

Version
Date
Description
Updated By
1.0
October 23, 2025
Initial SOP Creation
Chris Horton


Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons

Feedback sent

We appreciate your effort and will try to fix the article