Information Technology and Communications

Designing Virtually Sliced Network Architecture for Fifth-Generation Networks

A senior-level treatment of network slicing architecture, focused on what changes outcomes.

  • 5training days
  • 4modules
  • 8sessions
  • 32topics
View packages and pricesCourse outline
Designing Virtually Sliced Network Architecture for Fifth-Generation Networks
5days

About the programme

Course Overview

Most outages involving network slicing architecture are triggered by a change somebody considered routine. The documentation for the wider technology and systems delivery agenda is accurate only until the next release. Ambition around this area of technology and systems delivery outruns capacity unless the sequencing is deliberate. The teaching approach is deliberately practical: participants build a technical standard for network slicing architecture as they go. Participants leave with a method for this strand of technology and systems delivery, not a set of opinions about it. It is pitched for practitioners with responsibility for this area of technology and systems delivery, not for observers of it. Participants gain a clear basis for measuring what network slicing architecture has actually achieved. The most reliable predictor of sound this part of technology and systems delivery is whether anyone reviews it when nothing has gone wrong. The course ends by identifying what the participant will stop doing to make the technology and systems delivery capability sustainable.

Expected Learning Outcomes

  • Design a training and briefing approach that sustains competence in network slicing architecture.

  • Apply access control and least privilege throughout network slicing architecture.

  • Plan the handover of network slicing architecture so that capability is not lost when key staff move on.

  • Compare the organisation's handling of network slicing architecture with recognised practice, and close the material gaps.

  • Assess and manage third-party and cloud dependencies in network slicing architecture.

  • Structure the service desk and support model for network slicing architecture.

  • Control technical debt in network slicing architecture deliberately rather than by neglect.

Who Should Attend

  • Quality and test engineers verifying network slicing architecture.

  • Those responsible for briefing external stakeholders on network slicing architecture.

  • Project managers delivering changes to network slicing architecture.

  • Officers preparing reports on network slicing architecture for boards or oversight committees.

  • IT managers and service owners responsible for network slicing architecture.

  • Solution architects designing network slicing architecture.

Course Modules

Open any module to see its sessions and topics.

01

Network slicing architecture: change control and rollback

2 sessions · 8 points

Session 1Least privilege in network slicing architecture without blocking the work

  • Set delivery and reliability indicators for network slicing architecture the team trusts.
  • Measure current load on network slicing architecture and project it forward twelve months.
  • Confirm that contractual obligations around network slicing architecture are understood.
  • Review logging on network slicing architecture for coverage and retention.

Session 2Making network slicing architecture work when resources are constrained

  • Remove steps in network slicing architecture that add effort without adding assurance.
  • Rank the weaknesses in network slicing architecture by consequence rather than by ease of fixing.
  • Prepare the summary of network slicing architecture that senior management will read.
  • Agree the smallest change to network slicing architecture that would be visibly useful.
02

Network slicing architecture: security, identity and least privilege

2 sessions · 8 points

Session 1Monitoring network slicing architecture from the user's point of view

  • Identify the single points of failure in network slicing architecture.
  • Benchmark the organisation's network slicing architecture against comparable operations.
  • Record the technical debt in network slicing architecture and schedule repayment.
  • Set escalation thresholds for network slicing architecture that work out of hours.

Session 2Documenting network slicing architecture so someone else can operate it

  • Document the runbook for network slicing architecture to the level a new engineer could use.
  • Assign responsibility for keeping documentation of network slicing architecture current.
  • Define incident severity levels for network slicing architecture and the response each triggers.
  • Confirm the support model and escalation path for network slicing architecture.
03

Network slicing architecture: build, pipeline and release discipline

2 sessions · 8 points

Session 1Reviewing network slicing architecture when nothing has gone wrong

  • Verify six months later that changes to network slicing architecture have held.
  • Distinguish symptoms from causes when network slicing architecture underperforms.
  • Establish the boundary of network slicing architecture and record what sits outside it.
  • Apply change control to network slicing architecture including emergency changes.

Session 2Dependencies and supply chain risk in network slicing architecture

  • Review access rights on network slicing architecture and remove what is no longer needed.
  • State the availability and recovery objectives for network slicing architecture as numbers.
  • Assess the exit route from any cloud or vendor dependency in network slicing architecture.
  • Test the procedure for network slicing architecture against a realistic scenario.
04

Network slicing architecture: incident response and severity

2 sessions · 8 points

Session 1The paperwork for network slicing architecture that is actually needed

  • Confirm data retention and deletion rules applied within network slicing architecture.
  • Confirm that reporting on network slicing architecture reaches the people who can act.
  • Identify single points of dependency in network slicing architecture and reduce them.
  • Draft the minimum viable technical standard for network slicing architecture.

Session 2Retiring the legacy part of network slicing architecture

  • Test the failover for network slicing architecture rather than assuming it works.
  • Confirm every release of network slicing architecture can be rolled back within a defined time.
  • Build the internal briefing that explains network slicing architecture to those affected.
  • Run a load test on network slicing architecture at expected peak plus a margin.

Choose the package that suits you

Silver Package

At least 3 people

USD1,250
  • Workshop or Program Participation
  • Airport Transfers
  • Customized Badge
  • Expert Mentorship (Private Sessions)
  • Supervision & Secretarial Services
  • Accredited Certificate of Participation
  • Complete Training Kit
  • Coffee Break
  • Closing Ceremony

Gold Package

At least 3 people

USD1,850
  • 5-night stay in a 5-star hotel
  • Workshop or Program Participation
  • Airport Transfers
  • Customized Badge
  • Expert Mentorship (Private Sessions)
  • Supervision & Secretarial Services
  • Accredited Certificate of Participation
  • Complete Training Kit
  • Coffee Break
  • Closing Ceremony

Complete your registration

We will contact you within one business day to confirm.

Share this course

🔗 Short link
View packages and prices

✆