--- title: Offshore NOC and Technical Support Teams for Telecoms, Altnets and MSPs description: "How UK telecoms providers, altnets and MSPs build offshore NOC and L1/L2 support teams: what to move, extended hours, access control, security and KPIs." image: https://blog.potentiam.co.uk/hubfs/blog/images/offshore-noc-technical-support-teams-hero-20260925-100922.webp --- [![footer-logo](https://blog.potentiam.co.uk/hubfs/footer-logo.svg "footer-logo")](https://potentiam.co.uk) - [Solutions](https://www.potentiam.co.uk/solutions) [![Technology icon](https://blog.potentiam.co.uk/hubfs/Images/Icons/Technology%20icon.svg) Technology Scale your team with a dedicated advisor who aligns architecture and performance 
to your goals.](https://www.potentiam.co.uk/solutions/technology) [![Finance and Accounting icon](https://blog.potentiam.co.uk/hubfs/Images/Icons/Finance%20and%20Accounting%20icon.svg) Finance and Accounting Finance specialists build offshore teams using the right processes and skills to strengthen accounting and deliver results.](https://www.potentiam.co.uk/solutions/finance-accounting) [![Marketing and Creative](https://blog.potentiam.co.uk/hubfs/Images/Icons/Marketing%20and%20Creative.svg) Marketing & Creative Marketing advisors build offshore teams that close capability gaps and integrate seamlessly with local operations.](https://www.potentiam.co.uk/solutions/marketing-and-design) [![Data Analytics icon](https://blog.potentiam.co.uk/hubfs/Images/Icons/Data%20Analytics%20icon.svg) Data Analytics Analytics experts design scalable offshore data teams that deliver actionable insights and business value.](https://www.potentiam.co.uk/solutions/data-analytics) [![Sales and Customer Success icon](https://blog.potentiam.co.uk/hubfs/Images/Icons/Sales%20and%20Customer%20Success%20icon.svg) Sales & Customer Success Specialists build offshore sales and customer success teams aligned for growth and strong client relationships.](https://www.potentiam.co.uk/solutions/sales-customer-service-solutions) [![Engineering and Construction icon](https://blog.potentiam.co.uk/hubfs/Images/Icons/Engineering%20and%20Construction%20icon.svg) Energy Consulting Solutions Scale engineering and construction projects with offshore teams that improve control, efficiency, and on-time delivery.](https://www.potentiam.co.uk/solutions/energy-consulting) - Locations [![menu-icon](https://blog.potentiam.co.uk/hubfs/Images/Icons/menu-icon.svg) Cape Town, South Africa English-speaking teams with seamless UK collaboration](https://www.potentiam.co.uk/locations/south-africa) [![menu-icon](https://blog.potentiam.co.uk/hubfs/Images/Icons/menu-icon.svg) Bengaluru, India Technology and data capability with EU and UK time-zone overlap](https://www.potentiam.co.uk/locations/india) [![menu-icon](https://blog.potentiam.co.uk/hubfs/Images/Icons/menu-icon.svg) Iași, Romania Multilingual EU talent aligned with European markets](https://www.potentiam.co.uk/locations/romania) [![menu-icon](https://blog.potentiam.co.uk/hubfs/Images/Icons/menu-icon.svg) Johannesburg, South Africa English-speaking talent with UK time-zone alignment](https://www.potentiam.co.uk/locations/johannesburg) [![menu-icon](https://blog.potentiam.co.uk/hubfs/Images/Icons/menu-icon.svg) São Paulo, Brazil Latin American talent with US and EU time-zone overlap](https://www.potentiam.co.uk/locations/brazil) - [Careers](https://www.potentiam.co.uk/careers) - [About](https://www.potentiam.co.uk/about-us) - Resources [![Blog](https://blog.potentiam.co.uk/hubfs/Blog.svg) Blogs Explore strategies and insights on building high-performing offshore teams, scaling global operations, and unlocking performance growth.](https://blog.potentiam.co.uk) [![case guides](https://blog.potentiam.co.uk/hubfs/case%20guides.svg) Guides Explore essential offshoring strategies for IT managed service providers with our comprehensive guides tailored for COOs and CEOs.](https://www.potentiam.co.uk/guides) [![webinar](https://blog.potentiam.co.uk/hubfs/webinar.svg) Webinars Watch Potentiam’s webinars to discover how offshore teams can accelerate growth, cut costs, and boost performance.](https://www.potentiam.co.uk/webinars) [![case studies](https://blog.potentiam.co.uk/hubfs/case%20studies.svg) Case Studies Explore case studies showcasing how companies in various industries are enhancing efficiency and growth through innovative strategies and specialised services.](https://casestudies.potentiam.co.uk) - [Contact](https://www.potentiam.co.uk/contact-us) - [Book a meeting](https://www.potentiam.co.uk/contact-us) Back to Articles ![Two network engineers in a network operations centre at dawn monitoring network maps, status tiles and latency graphs across a wall of screens](https://blog.potentiam.co.uk/hubfs/blog/images/offshore-noc-technical-support-teams-hero-20260925-100922.webp) Scroll Back to Articles [IT & Software](https://blog.potentiam.co.uk/tag/it-software) | 14 October 2026 # Offshore NOC and Technical Support Teams for Telecoms, Altnets and MSPs [Potentiam](https://blog.potentiam.co.uk/author/potentiam) Most of what a network operations centre and an L1/L2 technical support team does is watching, triaging, restoring and escalating against written runbooks, and that work suits an embedded offshore team well. What has to stay in the UK is smaller than most operators expect: field work, final authority over high-risk changes and, for telecoms providers within the UK telecoms security rules, a UK capability that could run the network without the offshore team. Design around those three and extended-hours cover becomes affordable. Key takeaway Move the work that is repeatable, documented and done at a screen: monitoring, triage, L1 and L2 incidents, standard changes, patching and reporting. Keep field work, major incident command and high-risk change approval in the UK. To extend cover beyond the UK day, combine Bengaluru for the early hours, South Africa or Iași for the UK day and São Paulo for the evening. Overnight, weekend or continuous cover is agreed with you around your service levels. Telecoms providers should design access around the Electronic Communications (Security Measures) Regulations 2022 and take advice. ## What does a NOC and technical support team actually do? A network operations centre keeps networks and services running, using ITIL practices most UK MSPs, altnets and SaaS businesses already run: - **Monitoring and event management.** Turning network, server and application telemetry into alerts someone acts on. - **Alert triage.** Separating real, customer-affecting alerts from noise. - **Incident management.** Restoring service as quickly as possible, often with a known workaround. - **Problem management.** Finding the root cause so incidents do not recur. - **Change enablement.** Planning, approving and carrying out changes, usually in agreed maintenance windows. - **Escalation.** Moving work from L1 to L2 to L3 or the vendor, with the evidence the next tier needs. Technical support sits alongside: L1 resolves straightforward tickets and routes the rest, L2 diagnoses and restores, L3 is engineering and vendors. A service desk faces users, a NOC faces the network. In a business of 50 to 300 people they are often one team, so we plan them together. The roles we build for this work are network engineers, site reliability engineers, L1 and L2 service desk analysts, systems administrators and application support analysts, with systems administrators and network engineers providing 2nd line and escalation support. We also build SOC analysts and security engineers in any of our hubs, including an offshore security operations centre (SOC). For the user-facing side, read our guide to [offshore service desk teams for MSPs](https://blog.potentiam.co.uk/offshore-service-desk-teams-for-msps), and for customer service, billing and back office, our guide to [offshore teams for telecoms](https://blog.potentiam.co.uk/offshore-teams-telecoms). ## Which NOC and support work should move offshore? Move the work that is repeatable, documented and done at a screen. Keep the work that needs hands on equipment, carries final accountability, or that regulation expects the UK to be able to do. | Work | Embedded offshore team | Stays with your UK team | | --- | --- | --- | | **Monitoring and alert triage** | Strong fit, working to documented thresholds and runbooks | Deciding thresholds and what counts as customer-affecting | | **L1 service desk and ticket handling** | Strong fit, inside your ticketing and knowledge base | Commercial conversations with clients | | **L2 diagnosis and service restoration** | Strong fit, with clear escalation paths | Command of major incidents and customer communications during large outages | | **Changes in maintenance windows** | Carrying out standard, pre-approved changes | Approving significant or high-risk changes | | **Patching, backup checks, capacity and SLA reporting** | Strong fit | Decisions to defer a security patch | | **Field engineering and site access** | Remote diagnosis before a visit | All physical work | | **Architecture, vendors and regulatory accountability** | Analysis and preparation | Ownership and sign-off | The dividing line is documentation. An offshore L2 engineer restores a failed link as well as one in Manchester if the runbook, access and escalation route exist. Process discipline matters: the [Uptime Institute's Annual Outage Analysis 2026](https://uptimeinstitute.com/about-ui/press-releases/uptime-announces-annual-outage-analysis-report-2026) found failure to follow procedures remains the leading driver of human-error outages, and 57% of respondents to its 2025 survey said their most recent major outage cost more than $100,000. So every transition we run starts with written, tested runbooks. ![Technical support analysts in a Cape Town office working through a ticket queue and monitoring dashboards, one on a headset call with a UK customer](https://blog.potentiam.co.uk/hubfs/blog/images/offshore-noc-technical-support-teams-body-1-20260925-100928.webp) ## How do you extend cover with follow-the-sun teams? Start from what each hub gives you on a normal 9 to 6 local day, stated in UK time. BST is British Summer Time. | Hub | Offset from the UK | UK time in BST | UK time in winter | | --- | --- | --- | --- | | **Bengaluru** | 4.5 hours ahead in BST, 5.5 in winter | 4.30am to 1.30pm | 3.30am to 12.30pm | | **Cape Town and Johannesburg** | 1 hour ahead in BST, 2 in winter | 8am to 5pm | 7am to 4pm | | **Iași** | 2 hours ahead all year | 7am to 4pm | 7am to 4pm | | **São Paulo** | 4 hours behind in BST, 3 in winter | 1pm to 10pm | 12pm to 9pm | Together, those standard days run from 4.30am to 10pm UK time in summer and 3.30am to 9pm in winter. The overnight hours need agreed shifts, and so does any seat that must be staffed continuously. A pattern we use to close the gap keeps every shift inside reasonable local hours. Bengaluru, 4.5 hours ahead in BST and 5.5 in winter, works an agreed early shift from 1.30am to 10.30am UK time: 6am to 3pm locally in summer, 7am to 4pm in winter. South Africa or Iași takes the UK day on standard hours. São Paulo, 4 hours behind in BST and 3 in winter, working its standard local day, provides coverage into the UK afternoon and early evening. Any overnight coverage and handovers would need to be planned separately around the required service levels. This model extends coverage across time zones but continuous 24/7 cover would require additional agreed shifts and staffing. The alternative, where you need it, is one hub on agreed rotating shifts. Bengaluru, with mature ITIL-aligned processes, is where that model is most practical. It keeps handovers inside one team, at the cost of people working their own night. Where the team is large enough to staff three hubs, we usually recommend follow-the-sun. Plan the headcount honestly. One seat staffed every hour of the week is 168 hours, or 4.2 people on a 40-hour week before leave, sickness and training, so five per continuously staffed seat is the floor. A multi-hub rota like the one above schedules more, because shifts overlap for handovers and daytime peaks, so size each hub to its shift and workload. Make each handover a written step: open incidents, changes in progress, suppressed alerts and anything promised to a customer. Handovers are where follow-the-sun cover is most exposed, so treat each one as a step someone signs off. ## How do you control privileged access from an offshore NOC? ![Network engineer inserting a hardware security key into a company-managed laptop before signing in to network management systems, with an access badge on the desk](https://blog.potentiam.co.uk/hubfs/blog/images/offshore-noc-technical-support-teams-body-2-20260925-100936.webp) A NOC engineer holds the keys to your network, so design access first. Apply the controls you would use for a UK engineer, without exception: a named account per person, multi-factor authentication on anything that can change configuration, least privilege with elevation only for the task, company-managed devices, and logged, reviewed administrative activity. The National Cyber Security Centre's [secure system administration guidance](https://www.ncsc.gov.uk/collection/secure-system-administration) sets out the principles, including trusted management devices and tiered administration. Our teams work from our offices on managed equipment, which is far easier to evidence to an auditor than home working. ### If you are a public telecoms provider The [Telecommunications (Security) Act 2021](https://www.legislation.gov.uk/ukpga/2021/31/contents) amended the Communications Act 2003, and the [Electronic Communications (Security Measures) Regulations 2022](https://www.legislation.gov.uk/uksi/2022/933/contents), in force since 1 October 2022, set specific duties for providers of public electronic communications networks and services. Several bear directly on an offshore NOC: - No security permission may be given to, or exercised by, a person while they are in a country listed in the Schedule, which names China, Iran, North Korea and Russia, and real-time monitoring and analysis tools must not be accessible from or stored in those countries (regulations 8(6) and 5(3)). None of our five hubs is in a listed country. - Network providers must take appropriate and proportionate measures to ensure that, if it became necessary, they could operate the network without relying on people, equipment or stored data outside the UK (regulation 3(3)(f)). - All access to security critical functions must be recorded, including who obtained it; accounts able to change those functions need multi-factor authentication; and significant or manual changes must be proposed by one authorised person and approved by another (regulations 6 and 8). - Risks from third-party suppliers must be managed by contract, including the ability to monitor what the supplier does on your network (regulation 7). Because we employ your team, we are a third-party supplier for this purpose, and our contracts and access design need to support that. Micro-entities are exempt from these specific measures. The government's [Telecommunications Security Code of Practice](https://www.gov.uk/government/publications/revised-telecommunications-security-code-of-practice-2026-version-11/telecommunications-security-code-of-practice-2026-version-11), revised in July 2026, gives detailed guidance to Tier 1 providers (relevant turnover of £1 billion or more) and Tier 2 providers (£50 million to £1 billion). Tier 3 providers, below £50 million, need not follow the Code's measures but remain bound by the Act and regulations. The Code expects providers using offshored capabilities to be able to restore, secure and run their UK networks if they lose access to them, to retain UK-based technical expertise, and to have third-party administrators use trusted privileged access workstations. Ofcom enforces the framework, and its [security report for October 2024 to October 2025](https://www.gov.uk/government/publications/ofcom-security-report-for-the-period-october-2024-to-october-2025) identified providers acting as suppliers to other providers as one area where implementation is lagging. In practice the offshore team monitors, triages, restores and makes approved changes, while a UK team approves changes to security critical functions and could run the network alone. How the regulations apply depends on what you provide and your size. This is a summary of the risk, so take advice before an offshore team is given access to network management systems. ### Data protection If the team can see customer personal data, UK GDPR applies. Under the [ICO's international transfer rules](https://ico.org.uk/for-organisations/uk-gdpr-guidance-and-resources/international-transfers/a-brief-guide-to-international-transfers/), giving access is a restricted transfer where the organisation initiating it is subject to UK GDPR and the recipient is a separate legal entity outside the UK, so we map the entities and data flows with you before anyone has access. Romania is covered by UK adequacy regulations, so no International Data Transfer Agreement or transfer risk assessment is needed there, although your other UK GDPR duties still apply. South Africa, India and Brazil need an appropriate safeguard, such as the International Data Transfer Agreement or the Addendum, together with a transfer risk assessment. ## Which KPIs should an offshore NOC be measured on? Hold the offshore team to the same measures as your UK team, split by shift and hub so a weak handover shows up quickly. | KPI | What it tells you | How to use it | | --- | --- | --- | | **Mean time to acknowledge (MTTA)** | How long an alert or ticket waits before a person takes ownership | Set by priority. It is the first number to move when a shift is short-staffed | | **Mean time to restore (MTTR)** | How long from detection to service restored | Measure restoration separately from the root-cause fix, which belongs to problem management | | **SLA attainment** | Share of incidents and requests meeting contracted response and resolution targets | Use the targets written into your customer contracts | | **First contact resolution** | Share of eligible tickets resolved during the first contact, with no follow-up or escalation | Should rise as the knowledge base and runbooks mature | | **Escalation quality** | Share of escalations that were needed and arrived with the right evidence | Shows training gaps sooner than volume figures do | | **Change success rate** | Share of changes completed without causing an incident or needing a rollback | Essential once the offshore team carries out changes in maintenance windows | Set targets from your own baseline: measure the UK numbers for a month before transition and agree where the offshore team should be after its first quarter. ## What this looks like in practice What makes an offshore support team work is integration: the same monitoring, ticketing and communication tools as your UK team, a structured daily handover while both teams are working, and the same SLAs, response targets and escalation procedures. The other half is matching each hub to the work. For Evora Global, a sustainability consultancy, we built a data and operations team in Iași and a development team in Bengaluru, each chosen for the work it does, and the Iași team cut weeks from the effort of getting data to Evora's clients. The same principle decides where a NOC sits. Read [how Evora Global built multi-hub offshore teams](https://blog.potentiam.co.uk/how-evora-global-saved-12-fte-with-multi-hub-offshore-teams-romania-india). ## How we build an offshore NOC or support team Under the [Embedded Offshore Team Model](https://blog.potentiam.co.uk/embedded-offshore-team-model) the team works in your monitoring, ticketing and remote management tools, follows your runbooks and reports into your managers. We employ it, house it in our offices and provide local HR support, so you control the work without building an overseas entity. We match the hub to the hardest role. In Bengaluru we build L1 and L2 service desk analysts, network engineers, site reliability engineers, application support analysts and systems administrators. Iași and São Paulo cover the same service desk, network and systems roles, plus site reliability engineering in Iași and DevOps in São Paulo. Cape Town and Johannesburg are our strongest hubs for ITIL-aligned application and infrastructure support during the UK day. Our [guide to the best offshore location for a technology or MSP team](https://blog.potentiam.co.uk/best-offshore-location-technology-msp-team) compares them. Hiring typically takes four to six weeks (four to eight in São Paulo), from starting the search to the candidate accepting the offer. We see the UK equivalent take six to twelve weeks or longer. On cost, labour cost savings typically run at 30 to 50% against the UK in Cape Town and Johannesburg and 40 to 50% against Western European rates in Iași. In São Paulo, operating costs for equivalent roles typically run 30 to 50% below the UK, and in Bengaluru salaries often run 40 to 70% below the UK, especially for mid-to-senior roles. If you are replacing an existing outsourced desk or NOC, our [service desk migration playbook](https://blog.potentiam.co.uk/migrating-outsourced-service-desk-offshore-team) sets out the sequence. For Microsoft 365 estates, see our guide to [offshore Microsoft 365 and managed services teams](https://blog.potentiam.co.uk/offshore-m365-managed-services-teams-uk-msps). Weighing up an offshore NOC or support team? [Book a discovery call](https://www.potentiam.co.uk/contact-us) and we will work through the shift pattern, access design and hubs with you. ## Frequently asked questions **What is an offshore NOC?** An offshore NOC is a network operations centre team based outside the UK that monitors your networks, triages alerts, restores service and escalates to your engineers. Under our embedded model it works in your tools, follows your runbooks and reports to your managers, while we employ and house it. **Can an offshore NOC provide 24/7 cover?** Extended-hours cover is straightforward; continuous cover is designed case by case. On standard 9 to 6 local days our hubs together cover from 4.30am to 10pm UK time in summer and 3.30am to 9pm in winter, because Bengaluru is 4.5 to 5.5 hours ahead of the UK and São Paulo 3 to 4 hours behind. Overnight, weekend or continuous cover needs agreed shifts, and we confirm the capabilities, staffing model and service levels with you before committing to it. Budget for at least five people per continuously staffed seat, and more where shifts overlap. **Can a UK telecoms provider use an offshore NOC?** Often, yes, with the right design. The Electronic Communications (Security Measures) Regulations 2022 bar security permissions being exercised from China, Iran, North Korea or Russia, require providers to record all access to security critical functions and to manage supplier risk by contract, and require network providers to be able to operate without people outside the UK if necessary. Take advice on how they apply to you. **What NOC work should stay in the UK?** Field engineering, command of major incidents, approval of high-risk changes, architecture, vendor ownership and regulatory accountability. Telecoms providers within the security regulations should also keep a UK team able to run the network alone. **How long does it take to set up an offshore NOC team?** Hiring typically takes four to six weeks in Cape Town, Johannesburg, Iași and Bengaluru and four to eight weeks in São Paulo, from starting the search to the candidate accepting the offer. Allow further time for runbooks, access and shadowing before the team takes a live queue. **Which KPIs should an offshore NOC report?** Mean time to acknowledge, mean time to restore, SLA attainment, first contact resolution, escalation quality and change success rate, reported on the same dashboard as your UK team and split by shift and hub. Sources: [Telecommunications (Security) Act 2021](https://www.legislation.gov.uk/ukpga/2021/31/contents); [Electronic Communications (Security Measures) Regulations 2022](https://www.legislation.gov.uk/uksi/2022/933/contents); [Telecommunications Security Code of Practice 2026, version 1.1 (DSIT, July 2026)](https://www.gov.uk/government/publications/revised-telecommunications-security-code-of-practice-2026-version-11/telecommunications-security-code-of-practice-2026-version-11); [Ofcom security report, October 2024 to October 2025 (published March 2026)](https://www.gov.uk/government/publications/ofcom-security-report-for-the-period-october-2024-to-october-2025); [ICO, A brief guide to international transfers (January 2026)](https://ico.org.uk/for-organisations/uk-gdpr-guidance-and-resources/international-transfers/a-brief-guide-to-international-transfers/); [NCSC, Secure system administration](https://www.ncsc.gov.uk/collection/secure-system-administration); [Uptime Institute, Annual Outage Analysis 2026 (May 2026)](https://uptimeinstitute.com/about-ui/press-releases/uptime-announces-annual-outage-analysis-report-2026). Scroll [![footer-logo](https://blog.potentiam.co.uk/hubfs/footer-logo.svg)](https://blog.potentiam.co.uk/) We strategically build offshore teams that integrate seamlessly into your business. ##### Solutions - [Technology](https://www.potentiam.co.uk/solutions/technology) - [Finance & Accounting](https://www.potentiam.co.uk/solutions/finance-accounting) - [Marketing & Design](https://www.potentiam.co.uk/solutions/marketing-and-design) - [Data Analytics](https://www.potentiam.co.uk/solutions/data-analytics) - [Sales & Customer Success](https://www.potentiam.co.uk/solutions/sales-customer-service-solutions) - [Energy Consulting](https://www.potentiam.co.uk/solutions/energy-consulting) ##### Locations - [Cape Town](https://www.potentiam.co.uk/locations/south-africa) - [Johannesburg](https://www.potentiam.co.uk/locations/johannesburg) - [Bangalore](https://www.potentiam.co.uk/locations/india) - [Iași](https://www.potentiam.co.uk/locations/romania) - [São Paulo](https://www.potentiam.co.uk/locations/brazil) ##### Quick links - [About us](https://www.potentiam.co.uk/about-us) - [Careers](https://www.potentiam.co.uk/careers) - [Contact us](https://www.potentiam.co.uk/contact-us) © 2026 Potentiam. All rights reserved. [Privacy Policy](https://blog.potentiam.co.uk/privacy) ```json { "@context" : "https://schema.org", "@id" : "https://blog.potentiam.co.uk/offshore-noc-technical-support-teams#article", "@type" : "Article", "author" : { "@id" : "https://www.potentiam.co.uk/#organization" }, "dateModified" : "2026-10-14", "datePublished" : "2026-10-14", "description" : "How UK telecoms providers, altnets and MSPs build offshore NOC and L1/L2 support teams: what to move, extended hours, access control, security and KPIs.", "headline" : "Offshore NOC and Technical Support Teams for Telecoms, Altnets and MSPs", "image" : "https://5804539.fs1.hubspotusercontent-eu1.net/hubfs/5804539/blog/images/offshore-noc-technical-support-teams-hero-20260925-100922.webp", "keywords" : [ "offshore NOC", "offshore network operations centre", "offshore technical support team", "follow-the-sun support", "offshore NOC telecoms", "Telecommunications (Security) Act offshore" ], "mainEntityOfPage" : { "@id" : "https://blog.potentiam.co.uk/offshore-noc-technical-support-teams" }, "publisher" : { "@id" : "https://www.potentiam.co.uk/#organization" }, "wordCount" : 2785 } ``` ```json { "@context" : "https://schema.org", "@id" : "https://www.potentiam.co.uk/#organization", "@type" : "Organization", "address" : { "@type" : "PostalAddress", "addressCountry" : "GB" }, "description" : "Potentiam is a London-based strategic offshoring consultancy that helps mid-sized companies build high-performing, embedded offshore teams across five hubs in South Africa, Romania, India and Brazil: Cape Town, Johannesburg, Iași, Bengaluru and São Paulo.", "logo" : { "@type" : "ImageObject", "url" : "https://www.potentiam.co.uk/hubfs/logo.svg" }, "name" : "Potentiam Ltd", "sameAs" : [ "https://www.linkedin.com/company/potentiam-ltd" ], "url" : "https://www.potentiam.co.uk" } ``` ```json { "@context" : "https://schema.org", "@id" : "https://blog.potentiam.co.uk/offshore-noc-technical-support-teams#breadcrumb", "@type" : "BreadcrumbList", "itemListElement" : [ { "@type" : "ListItem", "item" : "https://www.potentiam.co.uk", "name" : "Home", "position" : 1 }, { "@type" : "ListItem", "item" : "https://blog.potentiam.co.uk", "name" : "Blog", "position" : 2 }, { "@type" : "ListItem", "name" : "Offshore NOC and Technical Support Teams for Telecoms, Altnets and MSPs", "position" : 3 } ] } ``` ```json { "@context" : "https://schema.org", "@id" : "https://blog.potentiam.co.uk/offshore-noc-technical-support-teams#faq", "@type" : "FAQPage", "mainEntity" : [ { "@type" : "Question", "acceptedAnswer" : { "@type" : "Answer", "text" : "An offshore NOC is a network operations centre team based outside the UK that monitors your networks, triages alerts, restores service and escalates to your engineers. Under our embedded model it works in your tools, follows your runbooks and reports to your managers, while we employ and house it." }, "name" : "What is an offshore NOC?" }, { "@type" : "Question", "acceptedAnswer" : { "@type" : "Answer", "text" : "Extended-hours cover is straightforward; continuous cover is designed case by case. On standard 9 to 6 local days our hubs together cover from 4.30am to 10pm UK time in summer and 3.30am to 9pm in winter, because Bengaluru is 4.5 to 5.5 hours ahead of the UK and São Paulo 3 to 4 hours behind. Overnight, weekend or continuous cover needs agreed shifts, and we confirm the capabilities, staffing model and service levels with you before committing to it. Budget for at least five people per continuously staffed seat, and more where shifts overlap." }, "name" : "Can an offshore NOC provide 24/7 cover?" }, { "@type" : "Question", "acceptedAnswer" : { "@type" : "Answer", "text" : "Often, yes, with the right design. The Electronic Communications (Security Measures) Regulations 2022 bar security permissions being exercised from China, Iran, North Korea or Russia, require providers to record all access to security critical functions and to manage supplier risk by contract, and require network providers to be able to operate without people outside the UK if necessary. Take advice on how they apply to you." }, "name" : "Can a UK telecoms provider use an offshore NOC?" }, { "@type" : "Question", "acceptedAnswer" : { "@type" : "Answer", "text" : "Field engineering, command of major incidents, approval of high-risk changes, architecture, vendor ownership and regulatory accountability. Telecoms providers within the security regulations should also keep a UK team able to run the network alone." }, "name" : "What NOC work should stay in the UK?" }, { "@type" : "Question", "acceptedAnswer" : { "@type" : "Answer", "text" : "Hiring typically takes four to six weeks in Cape Town, Johannesburg, Iași and Bengaluru and four to eight weeks in São Paulo, from starting the search to the candidate accepting the offer. Allow further time for runbooks, access and shadowing before the team takes a live queue." }, "name" : "How long does it take to set up an offshore NOC team?" }, { "@type" : "Question", "acceptedAnswer" : { "@type" : "Answer", "text" : "Mean time to acknowledge, mean time to restore, SLA attainment, first contact resolution, escalation quality and change success rate, reported on the same dashboard as your UK team and split by shift and hub." }, "name" : "Which KPIs should an offshore NOC report?" } ] } ```