A year ago, we decided to test a service that is actively developing in the West - managed services, or managed IT. In Russian: “integrated management of IT infrastructure”. The company that provides this service is called the Managed Services Provider (MSP).
MSP manages server and network equipment, system and special software, cloud services. He also coordinates all the client's IT processes, including interaction between contractors. But the picture will explain it better:
Now we are using managed IT in three projects with clients from different market segments:
- a large network of gas stations as part of an oil company;
- clothing manufacturer and distributor (4 independent brands);
- technology startup.
Of course, a year is not the longest distance. Although already enough to collect feedback, analyze metrics and evaluate the results.
Key takeaway: managed IT is the only IT service delivery model today that benefits both the client and the supplier, and even third-party contractors.
Why this is so - we will show on the example of each of the cases. But first, let's criticize the established models a little.
Cons of outsourcing and outstaffing
Experienced service providers with large portfolios understand that almost any project goes beyond budget, time, or both. Because in IT there are a lot of tasks that have not been solved before. It is difficult to find a tried and tested method for them. An example is startups where the IT strategy can change at least every day.
An accurate assessment can only be given to small typical jobs: installing a database, deploying a new server, adding storage capacity - but these jobs by themselves do not bring value to the business.
Hence, there are three characteristic disadvantages of outsourcing:
- IT companies are often insured: they include, for example, more hours in the estimate, “with a margin”. This delta can be violated, and in both directions.
- . , Toggl . , . — ?
- , , - , .
As for outstaffing, let's face it: normal IT companies don't even consider such a model. Because this is a kind of modern slavery. You find people, sell them for rent - and you get something like a French legion, which is involved in incomprehensible operations, it is not clear where and with dubious effect for the outstaffing company.
The term itself, by the way, has long been taken over by developers and municipal services.
Outstaffing is more about low-skilled workers in orange bibs.
Another disadvantage: the outstaffer company must have a license and an authorized capital of at least 1 million rubles.
Managed IT: when business and IT people begin to understand each other
Managed IT, or managed services, is a popular service delivery model in mature IT markets. If you believe the report of the analytical portal Market Watch , the global turnover of managed services will reach $ 250 billion by 2022. The
provider, which operates according to the managed IT model, focuses not on the number of hours, but on the ultimate need: to give the client what he wants. It records the metrics that the business needs - that is, the one who allocates the IT budget. Metrics are specific services and results that these services deliver to meet business goals.
Why is it important? Because we often see that there is little understanding between the IT department and the business. Business in IT is not particularly versed, and this is not their task. In turn, IT specialists are not always able to convey their thoughts to the business - for example, when they want to explain why additional resources or staff are needed.
Managed IT creates a "bridge of understanding" between IT and business, makes everyone feel good.
A year of testing the model revealed some nuances. We noticed, for example, how difficult it is to change people's minds: everyone understands what outsourcing and outstaffing are, but they do not particularly strive to delve into the intricacies of managed IT. And that's okay.
The main thing for us is that the clients who participate in the projects have already appreciated the advantages of the new model.
Case No. 1: network of gas stations
Problems faced by the client before coming to us:
- : 200 + 120 . , test-, prod-, dev-.
- , . - ( ). , , . , .
- : - , - , . .
- There is no qualified coordinator or “one-stop shop” to advise on every type of IT work. That is, there is no one who makes the final decision and performs the function of a facilitator.
As a result, it often turns out that the client's IT specialists are not doing what they need - not strategic development or, for example, development. Most of the time they spend on maintaining what is already just in working order. It turns out work for the sake of work. All this slows down the business, it develops more slowly.
Decision
Private Cloud. We have moved the client's capacity to a custom-built private cloud installation. Now he has a dedicated, secure infrastructure on top-end hardware.
Consulting. Since we have been providing complex services to a large number of clients for a long time, there is an understanding of what is good and what is bad. We give expert advice on which direction is better to develop IT, and what is better not to do.
Difficulties
Because the client's infrastructure is large, it has accumulated technical debt. Some long-debugged processes are not completely configured correctly. There were two tasks to solve:
- Copy quality processes that are already in place.
- Understand the rest of the processes, propose an improvement - so that they are optimal in terms of time and resource costs.
Even a year later, optimization (under item 2) continues. When you take on such a project, you accumulate information gradually. Because, as a rule, there is no documentation, it takes a lot of time to restore everything.
Plus, those processes that have already taken shape are not always easy to change. People are used to them, and changes are not perceived equally by everyone. But this is normal, this applies to any process changes. It's great that in this sense the client meets us halfway.
Case # 2: clothing manufacturer and distributor
The client is a holding company that includes four separate divisions (brands). For each of them, order statistics are collected. For this, special software is used - order management system. The client found a contractor who supplied the software, and organized the integration with all divisions himself.
We provided the client with a virtual infrastructure and adjustment of all processes - so that the infrastructure would work correctly with the client software. Plus, we took it upon ourselves to communicate with the contractor who administers this software. The project is now in an active phase.
Here it is worth talking about one important task that had to be solved at the implementation stage.
Single point of failure
Previously, each of the client's divisions had separate infrastructure and software. A simple service for one of the brands - for example, a payment acceptance service - led to losses only for that brand. But the management decided to consolidate the infrastructure and software.
After moving to us, the client's software works only on our infrastructure - and this is a single point of failure. If our servers fail, the whole holding is already incurring losses. Even with an idle time of 5 minutes, the amount will be sensitive.
The client asked a logical, seemingly, question: "If your system is down for an hour and we lose, for example, half a million rubles, can you reimburse us?" The answer was: "No."
Not all SLAs are created equal
We cannot trust the business performance of all of our clients. We do not know how these metrics are collected and calculated. It turns out that any client will come to us and say that he lost half a million - and we will have to believe him? But then our compensation may exceed the amount of all money received for the service. This is pretty weird.
We have an SLA of 99.9%, the standard for service providers. But we offer 99.9% “by documents”, although our real SLA is close to 100%.
Because we use the best equipment on the market. We save by reducing the likelihood of incidents and downtime.
Meanwhile, there are many IT providers who are engaged in imaginary savings: they buy cheaper hardware - for example, Supermicro servers. And this is a completely different "three nines".
SLA compensation is not intended to reduce customer downtime losses, but to ensure that the IT service provider also incurs losses. That is, so that the supplier also hurts.
The client understood and accepted all this.
Case # 3: technology startup
Let's start with a generalization. Statistics (like our experience) show that about one out of ten startups survives. Startups are in constant search, the same applies to infrastructure: many often change the direction of IT development, and this is not always true.
Typical startup mistakes
- , : -, , , , , . , — CPU RAM. . , . , - . .
: , . - Often in startups, several specializations are accumulated on one person. For example, a developer is both an administrator and a tester. And a business owner is an investor, an account manager, a product, a marketer, and a seller. In such companies, employees are in constant overload, working almost around the clock. Burnout happens here more often than anywhere else.
Way out: transfer of functions for management and strategic development of IT infrastructure to a service provider.
Our client
The startup is developing an intelligent platform for online advertising campaigns. This is a complex and resource-intensive software that is rapidly evolving. To support it, the client previously rented an old "hardware" with outdated software in a data center that does not meet Tier III requirements.
What we did:
- We provided a virtual infrastructure on high-quality hardware, transferred software to a new infrastructure. Since then, the performance indicators have increased markedly.
- We set up the databases, organized the Galera cluster - so that the client could scale both vertically and horizontally.
- They offered to abandon the idea of a monolithic infrastructure and explained why it is important to grow towards microservices. They told how to do it.
Conclusion
Why the managed IT model is good :
- The business is beginning to understand how the metrics they want to get are related to the metrics that IT services provide. And also - how the payment will increase with increasing resource consumption and growth, so that it can be tracked, and the economic model would converge at all stages.
- . , . - . .
- , , , , , best practices. , .
- , - — , .
Of course, managed IT has its limitations. The service is actively evolving as it receives feedback from the market, somewhere it needs to be improved, including on new projects. However, it is already obvious to us that it is promising. Managed IT is exactly a cut above outsourcing, atustafing and other derivatives.
Our favorite analogy for managed IT is car sharing. The whole world is changing towards consumption by subscription. Managed IT - also providing a subscription service, only in B2B. As in car sharing, the client receives a working service that he uses without thinking about its support, configuration and optimization. The provider takes care of this.