Start here (Go-live stack)
Start here (Go-live stack)
NMS Prime is a CRM, BSS and OSS platform for ISPs and Telcos.
Audience: onboarding / delivery · pre-sales · anyone asking “what do we set up first?”
Parent: Applications
Platform first: Complete On Boarding Steps (Prime Platform) (cloud/on-prem, hosting provider, domain & TLS) before app-specific workshops.
There is no universal linear app order. Choose the outcome. Projects commonly run both tracks in parallel and join them at Product / Billing.
Track A — get the first modem online
This follows the existing Provisioning Setup and its mandatory Billing/Product minimum.
Step | Do | App / guide | Done when |
|---|---|---|---|
1 | Configure NetGw, IP pool, QoS, and hardware path | OS Provisioning · Vendor Plugins (hardware paths) | Network foundation exists |
2 | Create the mandatory cost center and product / tariff data | Service can be assigned commercially | |
3 | Create customer, configuration file, and modem | First modem registers online | |
4 | Configure thresholds / targets and verify health | NOC sees the modem / access network |
Important: Billing Setup explicitly marks cost center + products as mandatory for bringing a cable modem online; full company / SEPA setup is needed later for settlement runs.
Track B — CRM / BSS and digital sales
Dependency order for selling, serving, and billing at an address:
Step | App | Why now | Done when |
|---|---|---|---|
1 | Defines offers, versions, technologies, speeds, mappings | Go-live product catalogue accepted | |
2 | Holds buildings / apartments / coverage / build status | Pilot addresses return correct plant state | |
3 | Adds companies, cost centers, tariffs, settlement | Test invoice / payment path works | |
4 | Customer and relationship of record | Customer / care workflow works | |
5 | Needs Product + Property to answer what is orderable at an address | Address check → correct offer → order works | |
6 | Needs customer / billing / product data | Customer sees invoices and can self-serve | |
7 | Receives care / NOC / portal requests | Ticket routing and ownership work |
Prime Property is core, not “often next”, whenever address availability, rollout status, or Order Portal is in scope.
Core app set
App | Primary outcome | License |
|---|---|---|
First modem / CPE online | ||
What is sold | ||
Where it is available | ||
What is invoiced / collected | ||
Customer of record | ||
Sell at an address | ||
Customer self-care | ||
Care / NOC / field requests | ||
Network health visibility |
Often next
App | Why | License |
|---|---|---|
Proactive impairment detection → tickets | ||
Field-work execution | ||
Dunning / collections |
FAQ
What do we set up first?
Complete Platform onboarding, then pick an outcome — Track A (first modem online) or Track B (sell and bill at an address). Many projects run both in parallel and join at Product / Billing.
Is Prime Property optional?
No — it is core whenever address availability, rollout status, or the Order Portal is in scope.
Where is CCC / Customer Control?
That is Prime Customer Self-Service Portal (package ccc).
Where is the full app list?
All applications (A–Z / catalog) — Core apps on top, full A–Z below.
Related
Vendor Plugins — DOCSIS / FTTH / DSL hardware paths & OLT vendor apps