COVID-19

4 ways to reduce cost and increase liquidity.

Many companies are under tremendous financial pressure due to the COVID-19 virus. We sat down to figure out what we can do to help and came up with 4 ways of how we can reduce cost and increase liquidity in the short term for a company. We are posting these 4 ideas in a blog series.

4 ways to reduce cost and increase liquidity

We provide 4 hands-on ideas of how you can reduce cost and increase liquidity in the short term. All ideas include financial examples to provide a clear view of the potential of each idea in your context. We have created 4 business case templates to help you customize and translate each idea into tangible value for your organization, just give us a call and we will help you. Bring some good news to your CFO in these challenging times with some hands-on, concrete and proactive ideas of how to reduce IT costs.

Idea #1 – Hardware refresh

With a depreciation cycle of 36 months, you’re looking at a 33% replacement of servers and storage in your datacenter this year. Now is a good time to challenge the default decision to replace those servers with new ones and consider cloud instead.

Read blog post

Idea #2 – [ insert integration product here ] replace

Every organization needs to connect data between applications and databases to support their business processes. There are a lot of ways of solving the integration need but many companies have bought an integration platform from one or more of the major product vendors in the market such as Microsoft Biztalk, Tibco, Mulesoft, IBM Websphere etc. If you’re one of them, we have good news for you and your CFO.

Read blog post

Idea #3 – incident automation

Incident handling is often a highly manual process in most companies. It requires 1st, 2nd and 3rd line resources in a service desk to manage error handling of the applications, databases and infrastructure. Further more, some expert forum, or Change Advisory Board, are usually in place to work with improvements to reduce tickets and incidents. A lot of people is required just to keep the lights on. Imagine if you could automate most of your incidents.

Read blog post

Idea #4 – infrastructure optimization

Managing cloud infrastructure is different to managing infrastructure on-prem. It’s easy to provision new resources but it’s equally easy to forget to decommission resources when they’re not needed. Further more, performance tuning is often not part of daily routines and only performed when there are performance problems. Optimization is not supposed to be performed occasionally but rather on a regular basis to ensure a cost effective use of cloud computing. If you need to find quick ways of reducing your costs, optimizing will be one tool to use to bring good news to your CFO.

Read blog post

COVID-19

4 ways to reduce cost and increase liquidity. #3

Many companies are under tremendous financial pressure due to the COVID-19 virus. We sat down to figure out what we can do to help and came up with 4 ways of how we can reduce cost and increase liquidity in the short term for a company. We are posting these 4 ideas in a blog series and in this blog post, we will present the third idea to improve your financials – automate your incident handling.

#3 – Automate your incident handling

This third tip of reducing cost and increasing liquidity only apply for organizations already running workloads in AWS. However, if you’re interested in our first tip, move to cloud instead of replacing servers which is due for refreshment this year, this apply for you as well.

Incident handling is often a highly manual process in most companies. It requires 1st, 2nd and 3rd line resources in a service desk to manage error handling of the applications, databases and infrastructure. Further more, some expert forum, or Change Advisory Board, are usually in place to work with improvements to reduce tickets and incidents. A lot of people is required just to keep the lights on.

What if you could set up monitoring alerts that automatically triggers automated processes and resolves the incidents before the users even notice them and place a ticket to your service desk. Sounds like science fiction? Check out Max Koldenius TIQQE Talk about AutoOps.

Let’s put some numbers on such a scenario.

Example – a company with 1000 incidents per month

In this example, we have a company with 1000 incidents per month. We assume an average cost of 156kr for handling an incident which is based upon a public report of service desk costs.

We’re comparing the manual cost with an automated incident handling service from us. We’re practicing automated incident handling in our own service desk and we’re currently managing 90% of all incidents by automation. In this example, we assume a 70% automation potential.

Year 0 represents the investment year and in this case it includes an incident analysis and the setup of the service, a total of 80kSEK.

This company would have a yearly cost of 1.9MSEK for manual incident handling. They would need to invest 80kSEK to enable automated incident handling and would then have a yearly cost of 768kSEK for the automation service from us. The accumulated cost for manual incident handling would be 11.2MSEK over 6 years compared to 4.7MSEK for the automation service.

Comparison between manual incident handling and automation

The graph below shows savings per year and accumulated savings. This company would save 1MSEK the first year and 1.1MSEK per year the following years. The return on investment in this example is 5.4 months. The accumulated savings equals 6.5MSEK in 6 years, or 58%.

Accumulated savings of incident automation

There are of course a lot of ifs and buts in any calculation and the numbers are just interesting if you can identify yourself in them. We have created a template for helping companies calculate a comparison between manual and an automated incident handling service from us. We can customize most of the data to simulate your specific prerequisites to make it as accurate as possible.

Please contact me or any of my colleagues if you would like to do the exercise for your company, we’re here to help.

Stay tuned for more examples of how we can help you reduce costs and increase liquidity.

Tiqqe Talk

TIQQE TALK: State of the cloud

Where are Swedish organizations in terms of cloud adoption? How far have they come and are anything holding them back? Listen to Malin Andersson and Anders Eriksson giving their view of where the market is today.

The talk is in Swedish.

People

Kennet Wahlberg is joining Tiqqe

We’re proud to welcome Kennet Wahlberg as our new Cloud Security and Compliance Lead.

Kennet has more than 20 years of experience within the fields of security and compliance. He has worked as both CIO and as an expert consultant for several companies. In recent years, he has focused on the new General Data Protection Regulation and privacy, which is two of his favourite subjects.

As security is becoming more and more important for our customers when moving data and applications to the cloud, Kennet will be of great support to our customers. He will also be leading our AWS certification initiatives and consulting in our transition services.

Kennet will work out of Linköping and be a part of our distributed team.

People

Anders Eriksson is joining Tiqqe

We just signed a sub-contract with Anders Eriksson who will join Tiqqe as a Cloud Transition Advisor.

As of January, Anders Eriksson, will join Tiqqe as an advisor within the area of Cloud Transition. We believe the market demand for cloud transition expertise will be high in the next coming years as more and more companies decide to move to cloud.

Anders has developed a structured approach to how a company can assess cloud versus their current platform, may it be on-premise, co-location or even outsourced. It’s a complex process to gather all the information required to take a strategic decision to move to cloud and Anders will be able to support a customer decision team with necessary information.

Cloud Due Diligence is the name of the service and will be introduced as an offering shortly.