Inventory & Resources
Routes under: inv
- inv > dconf > model > 105
- inv > dconf > vendor > 104
- inv > device > modem > 103
- inv > device > modem > 103 > add
- inv > device > modemitm > 106
- inv > ip > batch > 101
- inv > ip > batch > 101 > add
- inv > ip > item
- inv > landlinem > landline > 101
- inv > landlinem > landline > 104 > add
- inv > landlinem > landlinenumber > 102
inv > dconf > model > 105
inv > dconf > model > 105
Route: inv/dconf/model/105
URL: https://admin.myslbb.com/#/inv/dconf/model/105
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
- Verify you are working on the correct entity (Customer/Account/Service).
- Review the current lifecycle state before making changes.
- Apply changes and validate system response.
- Confirm downstream impact (AAA/Provisioning/Billing) where applicable.
Field & Action Hints (Auto-detected)
- Actions detected: Auto, Close, Inventory, Device Model, Add New Model, HGU-400-4AC, DBC Technologies, PPCT-All, PPCT, TP-Link-All, TP-Link, XPON-All, XPON, HWTC-All, HWTC, Realtek-All, Realtek, BDCM-All, BDCM
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/dconf/model/105
create_new
Captured URL: https://admin.myslbb.com/#/inv/dconf/model/105
drilldown_one_item
Captured URL: https://admin.myslbb.com/#/inv/dconf/model/105
inv > dconf > vendor > 104
inv > dconf > vendor > 104
Route: inv/dconf/vendor/104
URL: https://admin.myslbb.com/#/inv/dconf/vendor/104
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
- Verify you are working on the correct entity (Customer/Account/Service).
- Review the current lifecycle state before making changes.
- Apply changes and validate system response.
- Confirm downstream impact (AAA/Provisioning/Billing) where applicable.
Field & Action Hints (Auto-detected)
- Actions detected: Auto, Close, Inventory, Vendor, New Vendor, DBC Technologies, PPCT, TP-Link, XPON, HWTC, Realtek, BDCM, Syrotech
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/dconf/vendor/104
create_new
Captured URL: https://admin.myslbb.com/#/inv/dconf/vendor/104
drilldown_one_item
Captured URL: https://admin.myslbb.com/#/inv/dconf/vendor/104
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
- Verify you are working on the correct entity (Customer/Account/Service).
- Review the current lifecycle state before making changes.
- Apply changes and validate system response.
- 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
drilldown_one_item
Captured URL: https://admin.myslbb.com/#/inv/device/modem/103
inv > device > modem > 103 > add
inv > device > modem > 103 > add
Route: inv/device/modem/103/add
URL: https://admin.myslbb.com/#/inv/device/modem/103/add
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
- Verify you are working on the correct entity (Customer/Account/Service).
- Review the current lifecycle state before making changes.
- Apply changes and validate system response.
- Confirm downstream impact (AAA/Provisioning/Billing) where applicable.
Field & Action Hints (Auto-detected)
- Fields detected: Internet Service, IPTV, Both, Name, Select Vendor, Select Model, Description
- Actions detected: Auto, Close, Inventory, Device Batch, Download Sample CSV, Cancel, Create Device Batch
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
create_new
Captured URL: https://admin.myslbb.com/#/inv/device/modem/103/add
inv > device > modemitm > 106
inv > device > modemitm > 106
Route: inv/device/modemitm/106
URL: https://admin.myslbb.com/#/inv/device/modemitm/106
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
- Verify you are working on the correct entity (Customer/Account/Service).
- Review the current lifecycle state before making changes.
- Apply changes and validate system response.
- Confirm downstream impact (AAA/Provisioning/Billing) where applicable.
Field & Action Hints (Auto-detected)
- Fields detected: Select Partner, Customer
- Actions detected: Auto, Close, Inventory, Device Item, Clear Filters, DBC Router 18-12-2025, DBCG1DC46F35, DBCG1DC46E8D, DBCG1DC46F75, DBCG1DC47075, DBCG1DC46E3D, DBCG1DC46E7D, DBCG1DC46F9D, DBCG1DC46EAD, DBCG1DC46ED5, DBCG1DC46DF5, DBCG1DC46FBD, DBCG1DC47005, DBCG1DC470A5, DBCG1DC4704D
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/modemitm/106
drilldown_one_item
Captured URL: https://admin.myslbb.com/#/inv/device/modemitm/106
inv > ip > batch > 101
inv > ip > batch > 101
Route: inv/ip/batch/101
URL: https://admin.myslbb.com/#/inv/ip/batch/101
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
- Verify you are working on the correct entity (Customer/Account/Service).
- Review the current lifecycle state before making changes.
- Apply changes and validate system response.
- Confirm downstream impact (AAA/Provisioning/Billing) where applicable.
Field & Action Hints (Auto-detected)
- Actions detected: Auto, Close, Inventory, IP Pool, Inventory Batch, New Batch, StarNet, Direct Static IP, JLR
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/ip/batch/101
drilldown_one_item
Captured URL: https://admin.myslbb.com/#/inv/ip/batch/101
inv > ip > batch > 101 > add
inv > ip > batch > 101 > add
Route: inv/ip/batch/101/add
URL: https://admin.myslbb.com/#/inv/ip/batch/101/add
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
- Verify you are working on the correct entity (Customer/Account/Service).
- Review the current lifecycle state before making changes.
- Apply changes and validate system response.
- Confirm downstream impact (AAA/Provisioning/Billing) where applicable.
Field & Action Hints (Auto-detected)
- Fields detected: Name, Description, From (IP address), To (IP address), Trusted Client (Optional), Subnet Mask (Optional), Gateway IP (Optional), IP Type, Association Type
- Actions detected: Auto, Close, Inventory, IP Pool, Inventory Batch, Create Batch, Cancel
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
create_new
Captured URL: https://admin.myslbb.com/#/inv/ip/batch/101/add
inv > ip > item
inv > ip > item
Route: inv/ip/item
URL: https://admin.myslbb.com/#/inv/ip/item
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
- Verify you are working on the correct entity (Customer/Account/Service).
- Review the current lifecycle state before making changes.
- Apply changes and validate system response.
- Confirm downstream impact (AAA/Provisioning/Billing) where applicable.
Field & Action Hints (Auto-detected)
- Actions detected: Auto, Close, Inventory, IP Pool, Inventory Item, 103.5.184.192, 103.5.184.129, 103.5.184.130, 103.5.184.131, 103.5.184.132, 103.5.184.133, 103.5.184.134, 103.5.184.135, 103.5.184.136, 103.5.184.137, 103.5.184.138, 103.5.184.139, 103.5.184.140, 103.5.184.141, 103.5.184.142
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/ip/item
drilldown_one_item
Captured URL: https://admin.myslbb.com/#/inv/ip/item
inv > landlinem > landline > 101
inv > landlinem > landline > 101
Route: inv/landlinem/landline/101
URL: https://admin.myslbb.com/#/inv/landlinem/landline/101
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
- Verify you are working on the correct entity (Customer/Account/Service).
- Review the current lifecycle state before making changes.
- Apply changes and validate system response.
- Confirm downstream impact (AAA/Provisioning/Billing) where applicable.
Field & Action Hints (Auto-detected)
- Actions detected: Auto, Close, Inventory, Landline Number Batch, New Landline Batch
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/landlinem/landline/101
drilldown_one_item
Captured URL: https://admin.myslbb.com/#/inv/landlinem/landline/101
inv > landlinem > landline > 104 > add
inv > landlinem > landline > 104 > add
Route: inv/landlinem/landline/104/add
URL: https://admin.myslbb.com/#/inv/landlinem/landline/104/add
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
- Verify you are working on the correct entity (Customer/Account/Service).
- Review the current lifecycle state before making changes.
- Apply changes and validate system response.
- Confirm downstream impact (AAA/Provisioning/Billing) where applicable.
Field & Action Hints (Auto-detected)
- Fields detected: Name, Description
- Actions detected: Auto, Close, Inventory, Landline Number Batch, Download Sample CSV, Cancel, Create Landline Batch
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
create_new
Captured URL: https://admin.myslbb.com/#/inv/landlinem/landline/104/add
inv > landlinem > landlinenumber > 102
inv > landlinem > landlinenumber > 102
Route: inv/landlinem/landlinenumber/102
URL: https://admin.myslbb.com/#/inv/landlinem/landlinenumber/102
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
- Verify you are working on the correct entity (Customer/Account/Service).
- Review the current lifecycle state before making changes.
- Apply changes and validate system response.
- Confirm downstream impact (AAA/Provisioning/Billing) where applicable.
Field & Action Hints (Auto-detected)
- Fields detected: Select Partner, Customer
- Actions detected: Auto, Close, Inventory, Landline Number, Clear Filters
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/landlinem/landlinenumber/102
drilldown_one_item
Captured URL: https://admin.myslbb.com/#/inv/landlinem/landlinenumber/102
