Skip to content

Book a 30-minute call

Scheduling is handled by Calendly, whose privacy policy applies to what you enter. Open in Calendly

All services

Ericsson NMS: legacy OSS & ENM

Support the management systems behind network operations, from legacy OSS-RC assessment to ENM integration and lifecycle planning.

At a glance

Support the management systems behind network operations, from legacy OSS-RC assessment to ENM integration and lifecycle planning.

What we implement. What we support.

Choose the systems you need to improve. We define the scope, dependencies and acceptance criteria before work begins.

Ericsson NMS: legacy OSS & ENM

Best for

Support the management systems behind network operations, from legacy OSS-RC assessment to ENM integration and lifecycle planning.

Implementation & integration

Review deployment and network-element compatibility; plan upgrades and migration, northbound interfaces, and fault, configuration and performance data flows. Changes follow the supported release path and agreed maintenance windows.

Managed support

Investigate platform and integration faults, review alarm and performance collection, track capacity and coordinate vendor escalation using your support entitlement. Legacy lifecycle constraints are assessed before changes.

Acceptance & handover

Version and dependency inventory, interface test results, change and recovery runbooks, and operator knowledge transfer. Agree acceptance tests for the actual node mix and interfaces.

Support depends on the agreed versions, integrations and access. Vendor subscriptions and licenses are separate; vendor partnership or certification is not implied. Coverage hours, escalation paths and response targets are agreed in writing. 24/7 coverage requires a managed operations agreement.

Scope your engagementCompare engagement optionsSee sample deliverables

What the work covers

  1. Network elements
  2. Legacy OSS or ENM
  3. Approved interfaces

Illustrative scope, not a deployment blueprint. Interfaces, permissions and acceptance criteria are agreed for each engagement.

Legacy OSS-RC and ENM are distinct
An OSS-RC estate needs its own inventory, dependency assessment and transition plan. ENM planning starts with the installed release, deployment model, node types and software versions. A migration is not assumed to be an in-place upgrade.
Compatibility comes before the change window
ENM supports multiple network domains, but coverage depends on the release and supported node models. Confirm the actual compatibility matrix, licenses and vendor procedures. Model-driven integration does not mean every node release works with every ENM release.
Test the interfaces you actually use
List fault management (FM), configuration management (CM) and performance management (PM) flows. Record each northbound consumer, protocol, authentication method and expected result. Validate alarm delivery, configuration operations and performance data on representative nodes.
Recovery is deployment-specific
Physical, virtual and cloud-native installations can have different prerequisites and recovery paths. Agree the maintenance window, stop conditions and recovery authority. Use the applicable vendor procedure and a representative test environment; do not assume a universal rollback or zero downtime.

The problem

ENM estates drift. Node software steps outpace network element model alignment, northbound integrations to umbrella OSS break quietly, and upgrade windows stretch because nobody trusts the rollback. When the FM/CM/PM plane wobbles, every assurance and provisioning workflow downstream inherits the risk.

How we work it

Stabilize and upgrade

Rehearse the supported change path in a representative test environment. Verify backups, recovery prerequisites, stop conditions and decision ownership before the production window.

What you get

  • Upgrade runbooks with rollback criteria
  • Northbound and node integration health checks
  • Capacity, licensing, and version roadmap
  • Operator handover and shadowing sessions

Stack

  • Ericsson OSS & ENM
  • Kubernetes
  • Red Hat OpenShift

Outcome

A management plane your NOC trusts — current, integrated, and operable without calling us back for every change.

A closer look at the deliverables

Illustrative templates for scoping and reviewing an engagement. These are not customer results, vendor-certified procedures or ready-to-run production instructions.

Illustrative expected result

Change and recovery plan

Ericsson OSS / ENM change plan

Prerequisites
Record source and target releases, deployment type, node mix, supported upgrade path and vendor support entitlement. Name the change owner and maintenance window.
Expected result / acceptance threshold
Compatibility and interface checks recorded; change and recovery decisions approved by the named owner.
Open the full worksheet

Start here

Plan an implementation or support engagement

Send the shape of the problem. An engineer — not a sales rep — replies within one business day.

Submit a request
Explore engagement options

What happens next

  1. 01Describe the estate
  2. 02Engineer review
  3. Working session