Shared vs. Dedicated NOC Support: A Quick-Guide

When looking for outsourced Network Operations Center (NOC) support, the question of a shared versus dedicated service model often arises. Typically, a company looking to outsource their NOC operations wants to determine whether the support engineers are dedicated to the company or shared across multiple clients.

Often, deciding between a shared or dedicated support model is a matter of understanding exactly how much work the NOC needs to do. Sometimes the optimal model is more or less apparent from analyzing important metrics. Other times, a number of other factors need to be considered as well, such as company security requirements (security checks and clearances), knowledge of client-specific applications, and complex workflow capability, to name a few.

In some situations, custom or ad-hoc support may be needed from the NOC team, which could strongly tip the scale in favor of the far more customizable dedicated model. Custom services might include provisioning of new services, verifying backup processes, and providing server patching support, among many others.

Here, we clearly define what “shared” and “dedicated” support means in this context and identify 10 of the key differences between shared and dedicated NOC support to help you find the model that’s optimal for your organization.

Read on for a summary of the significant points to consider when deciding between shared or dedicated NOC support.

Clarifying Terminology: “Shared” vs. “Dedicated”

A shared NOC resource—be it a person or tool—works in multiple client environments through assignments that commit them to a particular environment at any one time. A genuinely dedicated resource works solely in only one environment at all times.

These terms can get tricky when companies refer to shared resources as “dedicated” because they’re only working in one environment at any given point in time. While it’s true that these resources “dedicate” themselves to just one environment at a time, a better title for these resources might be “assigned.” A shared NOC engineer who works 40 hours a week may be assigned to two environments total. In this example, they may work 20 hours a week in one environment and the other 20 hours in the other.

Again, genuinely dedicated NOC resources are devoted solely to one environment. They typically, but not always, use the client’s tools rather than their own. In general, everything outside of this precise definition of a dedicated resource is technically “shared” in nature.

Shared NOC Service

The shared NOC is a timely and reliable resource pool that is constantly triaging and working through queues containing tickets from many clients. This model is tailored to offer standardized and templatized support.

Here at INOC, our shared NOC is staffed with skilled NOC personnel, from tiered groups of engineers to change specialists, and round-the-clock management. Once the systems to be monitored have been pointed at our infrastructure, we receive and ticket alerts, emails, and phone calls where they are triaged for severity and worked as our engineers move through the queue of shared client events. The engineers utilize INOC tools, and use alarm-to-action guides that are built off standardized support methods, and adapted to fit the client’s business.

Through platform integrations, the shared NOC is highly scalable. Escalations are typically handled internally through the shift supervisors and managers.

Dedicated NOC Service

The dedicated NOC service model is a custom outsourced solution staffed by a team with named resources, specific skill-sets, and a team lead that works in step with the client’s needs. Dedicated NOC resources handle issues from only one particular client or partner assigned to them.

Here at INOC, we work together with our dedicated clients to determine the team’s specific requirements. The client or partner then provides the tools our staff use, including hardware, access, and training related to the environment. The client onboards our dedicated team directly into their environment.

Dedicated resources use the client’s existing monitoring and ticketing platform, runbooks, and alarm-to-action guides. This allows the team to be small but highly intimate. The service levels are dependent on the number of resources available in the dedicated team. Escalations are typically handled from the dedicated team to the client’s responsible party.

Shared vs. Dedicated Support: 10 Key Differences

The table below offers a broad overview of the differences between a shared and dedicated model. Read on to find expanded summaries for each of these points below.

NOC SERVICE DELIVERABLE

DEDICATED NOC

SHARED NOC

Business Model

Resource-based

Asset and workload based, economies of scale

Service Level Agreement

Client defined, resource-dependent

Standard options

Delivery Resources

Named resources

Multiple teams

Delivery Process

Client-specific

ITIL

Delivery Platform

Client tools and runbooks/knowledge base

INOC tools

Integration with Client Tools

Limited or none

Extensive integration with client monitoring, ticketing systems, and other tools.

Scalability

Resource-dependent

Scalable

Supervision

Team Lead(s)

Managers 24x7

Escalation Management

Team Lead(s) and then client escalation tree

INOC escalation in parallel with client escalation

Service Options

Event, Incident, Problem, Change, Request Management, custom services

Event, Incident, Problem, Change, Request Management

 

1. Business Model

As a service model, dedicated NOC support is inherently tied to the number of individuals on the team. Dedicated service is constrained by the resources available at any one time. If only one engineer is actively working at a certain time, the support at that time is limited to that engineer’s capacity. If he or she is faced with multiple issues at once, some of those issues will simply have to wait until others are addressed. Similarly, if a dedicated team is active only during some hours of the day, issues that occur outside those hours can’t be addressed until support resumes.

For many companies, these constraints are acceptable, making the dedicated support a viable option. If, for whatever reason, issues become a frequent problem at a certain period of the day when resources either aren’t available or become overwhelmed, companies may choose to add an additional dedicated resource to handle that demand.

By contrast, the shared NOC support model enables organizations to benefit from economies of scale. Rather than being based on the number of resources, the shared support model is based on the number of assets (such as devices) and workload (the expected volume of NOC activity in a given period of time).

Here at INOC, our shared support model allows for service to scale across a large team of shared resources to meet periods of expected or unexpected demand—a capability that simply wouldn’t be possible in a dedicated support arrangement. This group of shared resources is sized to ensure roughly 65% utilization in order to provide a safe buffer of capacity to handle unexpected spikes in activity. Using company-wide metrics, changes in utilization are reflected in staffing decisions to ensure this balance is maintained at all times.

When considering which model makes the most sense for your organization, it’s important to realize that, in general, the less that resources need to be utilized the entire time, the more a shared NOC support model typically makes sense economically. Depending on the resources currently being utilized in the NOC, it’s not until the work volume averages hundreds or more incidents a month until a dedicated team becomes necessary from a practical perspective and worth it financially. However, as we explore in the sections below, other factors can complicate this calculation.

2. Service Level Agreement

A Service Level Agreement (SLA) establishes and defines the particular service levels for support, such as how fast the NOC will react to an event, how quickly resources will be assigned to troubleshoot an issue, and so on.

In a dedicated NOC support model, there is virtually no limit to the customization possible in establishing particular service levels so long as the resources can reasonably be expected to meet them. If, for example, an incident must be responded to within seconds rather than minutes, such a demand may require more than one resource in the NOC at a time.

In a shared NOC support model, SLAs are standardized across the entire client base. While there is sometimes a limited degree of customization available, supporting wildly varying SLAs is simply infeasible in a shared environment.

3. Delivery Resources

In a dedicated NOC support model, the resources that comprise the dedicated team are “named” individuals.

In the shared support model, a Client Services Manager is assigned and the other delivery resources are mostly distributed across the larger composition of the shared group. This includes the NOC team itself as well as the support teams that augment the NOC, such as the Service Desk, the Advanced Incident Management team, and the Advanced Technology Services team.

4. Delivery Process

In the shared NOC support model, services are delivered using the standard ITIL* framework. Like with the SLA and other aspects of service, the shared support model demands uniformity to function.

In a dedicated NOC support model, organizations are not limited to the standard ITIL framework. Variations of ITIL or altogether different frameworks, including custom ones, can be supported no matter how complex or customized they may be.

5. Delivery Platform

In a dedicated NOC support model, the dedicated team “lives” in the client’s environment. Clients have full control over what their dedicated resources use in terms of platforms and tools. Runbooks, knowledge bases, and virtually every other technology through which service is delivered can be used, and those resources are trained to work with them using the customer’s own processes and procedures.

In the shared NOC, services are delivered through the provider’s platform and processes—a facet of service that is often an advantage as it enables the client to benefit from the efficiencies and value-add capabilities awarded through its operational structure. Here at INOC, this includes wide functionality that is part of the INOC Platform. Client applications are used for additional visibility and troubleshooting as needed.

6. Integration with Client Tools

In a dedicated NOC support model, the fact that resources are already working within the client’s tools means integration isn’t necessary.

In a shared NOC scenario, integration with client tools is extensive. Since the efficiency and effectiveness of the shared NOC is afforded through its use of standard tools and processes, the variety in client tools is handled through sophisticated integrations, particularly with monitoring tools and trouble ticket systems.

7. Scalability

While we touched on scalability in our discussion of business model differences, it’s worth unpacking further as it often factors strongly in the decision between support models.

In a dedicated support model, scalability amounts to adding or eliminating resources from the dedicated team. Whether there’s an increase in NOC activity or the infrastructure expands as services are added, additional support needs can only be addressed by adding resources.

The shared NOC support model, by contrast, offers a reasonable level of flexibility to absorb varying workloads. While service pricing will naturally fluctuate with significant changes in workloads, the increments are typically far more subtle compared to adding even one additional dedicated resource.

8. Supervision

Dedicated and shared NOC support models have somewhat different demands for supervision and management. While the level and quality of service they deliver is identical, and each has access to the same value-add services that make outsourcing attractive from a business perspective, their structures often look quite different, with one requiring more managerial depth than the other.

In a dedicated support model, supervision is very straightforward. One or multiple team leads or managers are assigned to lead the dedicated team depending on the number of resources and service period during which services are provided. These supervisors are supported by the same Directors and VP-level leads as for the shared support environment and thus receive the same direction, oversight, and support from other teams.

In the shared NOC, the added complexity and sophistication of the team structure demands a similarly sophisticated management structure. Here, roles include Shift Managers as well as Team Managers, Directors, and VPs.

Again, while supervisorial roles may differ between the two models, both receive the same access to the operational expertise that drive the same level of quality throughout the service.

9. Escalation Management

Escalation management is one area where the difference between models is quite clear. In the dedicated NOC support model, issues can’t be escalated beyond the confines of the dedicated team because no one outside of that team can operate within the unique environment.

In the shared NOC support model, however, issues can be escalated to the area of expertise that’s best suited to address it. At INOC, for example, these escalations are handled primarily by our Advanced Incident Management and Advanced Technical Support teams. Network issues are escalated to network experts, server issues are escalated to server experts, and so on. Each type of issue has a clear path if it proves particularly challenging or complex.

10. Service Options

Lastly, it’s important to note that any capable outsourced NOC support partner should ensure that the options for service are largely identical regardless of whether it’s delivered through a shared or dedicated model.

At INOC, both support models offer Event Management, Incident Management, Problem Management, Change Management, and Request Management.

For custom service needs, however, the dedicated support model offers unique capability over the shared support model. Given the custom nature of dedicated support, where resources are typically utilized for reactive activities less frequently than in the shared NOC, these resources can utilize their available time to perform virtually any unique services required.

A few examples of custom or ad-hoc services that are beyond the capabilities of a shared NOC support team but are very much possible with a dedicated team include:

  • Server patch management
  • New service provisioning
  • Backup process verification

Final Thoughts and Next Steps

Choosing between a shared or dedicated support model requires careful consideration of the capabilities, advantages, and disadvantages of each model relative to your environment and support needs.

Here at INOC, we provide both shared and dedicated NOC support services depending on the factors we identify here.

If you have an existing NOC, and can’t seem to pull your advanced engineers or admins out of daily work to focus on other tasks, moving to a shared model operating under a tiered NOC structure will almost certainly improve IT staff productivity and retention while simultaneously increasing uptime and providing a better end-user experience.

According to data gathered across our outsourced NOC service along with industry research and interviews with IT support engineers, 65% of support activities can be often performed by first-level support staff when the NOC operation is structured effectively.

If high activity volume or other factors require a dedicated support model, we help you carefully determine requirements and staff a team that can be adjusted according to activity level—all from your own environment.

Need help determining the right NOC support model for your organization? Contact us to see how we can help you improve your IT service strategy and NOC support or download our free white paper below.

White paper cover: A Practical Guide to Running an Effective NOCFREE WHITE PAPER

A Practical Guide to Running an Effective NOC

Download our free white paper and learn how to build, optimize, and manage your NOC to maximize performance and uptime.

Download

 

 

 


*Originally developed by the UK government’s Office of Government Commerce (OGC) - now known as the Cabinet Office - and currently managed and developed by AXELOS, ITIL is a framework of best practices for delivering efficient and effective support services.

SUBSCRIBE TO RECEIVE NEW POSTS IN YOUR INBOX

RECOMMENDED CONTENT

Put our expertise to work for you

Let's unlock the full potential of your infrastructure and keep it running 24X7. Tell us a little about yourself, your infrastructure, and your challenges. We'll follow-up within one business day by phone or email.

Contact Us