/
On Boarding Steps (OS Provisioning)

On Boarding Steps (OS Provisioning)

Go-live essentials for OS Provisioning. Agree access technology and architecture first, then follow the canonical setup sequence.

NMS Prime is a CRM, BSS and OSS platform for ISPs and Telcos.

App hub: OS Provisioning

Steps reuse Provisioning Setup and the how-to guides under Official Documentation (OS Provisioning).

1. Top customer deliverables

Prio

Deliverable

Owner (customer)

Prio

Deliverable

Owner (customer)

1

Access technologies in scope — FTTH, DOCSIS, DSL, WiFi (one or more)

Network / architecture

2

Who operates Layer 2 (FTTH) — your OSS path vs Wholesale / Open Access API (independent of plant ownership)

Network / commercial

3

Network edge devices — CMTS, BRAS/BNG, OLT, DSLAM, …

Network

4

CPE / ONU model list — modems, ONUs, routers, WiFi APs

Network / procurement

5

Lab / pilot environment — isolated rack, VLANs, test subscribers

Network / NOC

6

FTTH detail (if applicable) — GPON (default), BRAS vs vendor plugin, L2 partner if outsourced

Network + NMS delivery

7

First device online — NetGw, pool, QoS, contract, configfile, modem/ONU

Ops

2. Scopes

#

Scope

Goal

#

Scope

Goal

1

Main decisions

Technologies, L2 model, devices, lab, FTTH path agreed

2

Network foundation

NetGw / pools / QoS / config templates

3

First subscriber

Contract + CPE provisioned and registered

4

Acceptance

Pilot device healthy in Monitoring; ops sign-off

3. Main decisions — access technology

Discuss and agree before building production objects.

3.1. Which technologies?

Technology

Network edge (typical)

CPE / access device

Speed / policy path

Deep-dive

Technology

Network edge (typical)

CPE / access device

Speed / policy path

Deep-dive

DOCSIS

CMTS (Add a CMTS)

Cable modem

DOCSIS config file (DHCP + TFTP)

Access Hardware & Vendor Plugins §3

FTTH

OLT + BRAS or partner API (OpenXS, Vitroconnect, …)

ONU / ONT / router

Your BNG + RADIUS + PPPoE or partner-dependent

§2 below

DSL

DSLAM + BRAS/BNG

DSL modem / CPE

BNG + RADIUS + PPPoE

Access Hardware & Vendor Plugins §5

WiFi

BRAS/BNG (+ APs)

WiFi CPE / hotspot client

BNG + RADIUS (WISPr bandwidth)

Access-Agnostic PPPoE Provisioning

Decide:

Which of FTTH · DOCSIS · DSL · WiFi are in go-live wave 1
Primary vs secondary technology per region (if mixed plant)
Whether TR-069 / GenieACS is required for CPE management (TR-069 and GenieACS Integration)

3.2. Which devices?

Document vendor, model, firmware, and who owns configuration on each layer.

Layer

Examples

Record in onboarding

Layer

Examples

Record in onboarding

Access node

OLT (Huawei, Nokia, Zyxel, …), CMTS, DSLAM

Vendor + management IP + SNMP/CLI access model

L2 partner platform

OpenXS, Vitroconnect, other Open Access provider

API contract, activation SLA, circuit-ID format

Subscriber terminal

ONU/ONT, cable modem, DSL modem, WiFi router

Model, provisioning method (MAC, serial, PPPoE user)

Policy edge

Cisco ASR, MikroTik CCR, Ubiquiti EdgeRouter (BNG/BRAS)

Registered as NetGw type BRAS (if in your path)

Supporting services

DHCP, TFTP, DNS, RADIUS, GenieACS

Aligned with Provisioning Setup

Decide:

Device inventory for lab and first production cluster
Who provisions ONU/ONT — your OSS, vendor app, or L2 partner API
Supported CMTS/OLT list vs Access Hardware & Vendor Plugins

3.3. Lab environment

Use a dedicated lab before touching production plant.

Lab Environment Install Guide

Topic

Agree

Topic

Agree

Scope

One access path (OLT PON, partner test address, or CMTS downstream) + BRAS (if used) + NMS Prime staging

Subscribers

1–3 test contracts with distinct QoS profiles

CPE

Representative ONU/modem models from procurement shortlist

Exit criteria

Device registers or partner line activates; correct speed/policy; visible in admin + Prime Monitoring

Decide:

Lab location and who may change configs during workshops
When lab results gate production rollout

4. Main decisions — FTTH

Skip if FTTH is not in scope.

Plant ownership ≠ Layer 2 operator. You may own fibre and OLTs as an ISP and still outsource Layer 2 service delivery to a provider — NMS Prime then connects via their API (availability, activation, circuit ID). Conversely, wholesale footprints may still use your BRAS for session policy. Map who operates L2 per footprint; do not assume it follows asset ownership.

4.1. Who operates Layer 2?

Model

Who runs L2 service?

Typical NMS Prime role

Model

Who runs L2 service?

Typical NMS Prime role

You operate L2

Your OSS controls OLT/service activation (you may still own or lease plant)

Full path: NetGw, pools, QoS, modem/ONU, optional vendor plugin

Partner operates L2

Open Access / wholesale API (OpenXS, Vitroconnect, …) — even if you own the OLT

Shop probes today; line activation roadmap Q4/2026 — interim manual/API runbook

Hybrid

Mix by region, product, or footprint

Per-address matrix: your OSS vs partner API

Decide:

Per footprint: you operate L2, partner operates L2, or hybrid
Partner(s), API contact, and who owns activation tickets until automation ships

4.2. Wholesale / Open Access API

When a partner operates L2: OpenXS, Vitroconnect, and similar platforms. NMS Prime integrates for availability (today) and activation (Q4/2026 roadmap).

Topic

Workshop question

Topic

Workshop question

Availability

Which addresses map to which API? (Prime Service Availability carrier probes — detail TBD)

Activation

API order vs manual NOC ticket until Q4/2026

Session model

Open decision: subscriber PPPoE to your BRAS (L2 handoff) or partner terminates session/IP?

Not a vendor plugin. Wholesale APIs outsource L2 service delivery. Vendor plugins add OLT control when you operate L2 on your OLT.

Decide:

Partner platform in scope for wave 1 and interim activation process
BRAS in path: yes / no / region-specific (per partner contract)

4.3. GPON (when you operate L2)

Default for FTTH: GPON (OLT + ONU/ONT, shared PON). Most operators standardise on GPON — confirm your OLT vendor and VLAN model to BRAS.

Active Ethernet (point-to-point) is the exception — typically business/Ethernet-only footprints. See FTTH internal coding implementation if AE is in scope.

Decide:

GPON confirmed (or document if AE is required and why)
VLAN / service model from OLT to BRAS

4.4. Generic BRAS vs vendor plugin (when you operate L2)

Approach

When to use

NMS Prime path

Approach

When to use

NMS Prime path

Generic (default)

Subscriber speed and session policy; any OLT vendor

BNG/BRAS + RADIUS + PPPoE — no vendor app required

Vendor plugin

OLT-level ONT lifecycle, optical KPIs

Licensed Prime app (Altiplano, Calix, Zyxel, SmartOnt, …)

See Access Hardware & Vendor Plugins.

Decide:

Generic BNG + RADIUS only, or vendor plugin in scope
Live speed changes (CoA / disconnect) required on BRAS?

4.5. FTTH decision tree

 

5. Setup sequence

After decisions above, build objects in this order (Provisioning Setup). Partner-operated L2 may skip or defer some steps — confirm in workshop.

#

Deliverable

Guide

#

Deliverable

Guide

1

Network gateway (CMTS / BRAS / OLT path)

Add a NetGw

2

IP pool for the gateway

Add a IP-Pool

3

QoS profile (tariff speed)

Add a QoS-Profile

4

Customer / contract

Create a Customer

5

Configuration file

Create Configuration File

5.1.1. Then

6. Acceptance

NMS Prime brings

Customer brings

NMS Prime brings

Customer brings

Provisioning Setup walkthrough on staging/lab

Network owners for technology + L2 decisions

Delivery support for NetGw / RADIUS / config templates

Lab hardware, test CPE, partner test addresses

Monitoring integration guidance

NOC sign-off on pilot device or partner line

Decide: which items block production? (Recommend: one lab path per L2 model, correct QoS/speed, Monitoring green or partner activation confirmed.)

7. Related guides