Skip to main content

inv > device > modem > 103

inv > device > modem > 103

Route: inv/device/modem/103

URL: https://admin.myslbb.com/#/inv/device/modem/103

Overview

This page is a draft SOP reference for the above screen in i2i Core OSS/BSS. It is auto-generated from UI exports and should be reviewed for operational correctness before customer release.

When to Use

  • Use this screen for the workflow represented by this route.
  • Do not make billing/AAA/provisioning-impacting changes without required authorization.

Typical Workflow

  1. Verify you are working on the correct entity (Customer/Account/Service).
  2. Review the current lifecycle state before making changes.
  3. Apply changes and validate system response.
  4. Confirm downstream impact (AAA/Provisioning/Billing) where applicable.

Field & Action Hints (Auto-detected)

  • Actions detected: Auto, Close, Inventory, Device Batch, New Device Batch, BAT00011, DBC Router 18-12-2025, BAT00010, Rajan Avasthi 18-12-2025, BAT00009, DBC 15-12-2025, BAT00008, DBC-04-12-2025, BAT00007, HGU-400-4AC_01, BAT00006, PPCT Auto Capture CPE, BAT00005, TP-Link Auto Capture CPE, BAT00004

Validation & Safety Checks

  • Confirm identifiers before saving.
  • Confirm lifecycle state allows the change.
  • Confirm rollback/support path exists for production actions.

Escalation Guidance

  • L1: Verify input, permissions, and entity state.
  • L2: Validate dependencies and downstream state.
  • L3/Admin: Policy/config changes or suspected defect.

Screenshots

default

Captured URL: https://admin.myslbb.com/#/inv/device/modem/103

Images uploading…

drilldown_one_item

Captured URL: https://admin.myslbb.com/#/inv/device/modem/103

Images uploading…
Back to top