Streamlined Application Management

Is your IT environment automated to that level that it allows you to focus on developing your business instead of repeatedly fixing the same issues?
If not, then GetIT Nordic’s application expert and solution architect Petter Nilsson is ready to help you to go from reactive ad hoc solutions, to instead focus on proactive solutions with the help of automation.


Internal expectations on IT-solutions are often driven by functional needs, and technology is often seen as something that is just supposed to work. For IT, the challenge is often amplified by the fact that application documentation is often outdated, spread and in lack of a common structure.

Recurring incidents often have multiple known solutions, but unfortunately  these solutions are often only known by a few individuals and not documented. Incidents that could be captured by automated processes are instead reported manually, which contributes to delays before actions to restore functionality is initiated. Only in certain exceptions is automation used to instantly resolve the issue

In addition, if the business begins to buy cloud-based systems without consulting IT, the above phenomenon is amplified while operations lose control of the situation.

Below GetIT Nordic’s expert, Petter Nilsson, describes how he has developed methods to address these challenges by means of his many years of experience working with application management and architecture.

Flexible application operations with scalablity as needed

Since the focus – problem area within most IT organizations are directed elsewhere than application management, there are some simple methods that can be taken to simplify operations. Roughly,  we can divide them into four different actions per application. These efforts may seem simple to realize, but are methods that require long-term experience to be conducted successfully. If these experiences are lacking within the organization, these actions will not be implemented.


Minimize downtime with the help of monitoring

In my experience from my many years as an IT-architect, the first step is to start monitoring the central applications. If monitoring is already implemented, evaluate it’s efficiency  if it needs to be adjusted.

It’s a small investment with a large payout when it comes to minimizing the consequences of an incident. Lead times for reporting incidents are reduced, troubleshooting accelerated and the monitoring is ongoing around the clock.

Accelerated recovery of services

In order to accelerate the time needed resolving an incident further, the next step is to create a tailored solution to the above monitoring. For example, when you are alerted that application X stops, you receive instruction to clear log Z on just server Y, before restarting the application.

The result will be a faster and more accurate troubleshooting without person dependency. This generates a significant reduction of impact for the daily business in the event of an incident.

Applying structure to your documentation

As a complement to the predefined solution proposals, my experience is that a structured documentation of application operation is crucial for those cases when the solution proposals couldn’t identify the root cause. Through ready-made templates, the documentation receives a structure that covers everything that has to do with the operation application.

Documentation is always important and in some cases, likely already in place but through a standardized documentation procedure, personal dependence is minimized. In case of an incident, the turnout will be an decreased impact on the organization , which enables a more tailored support organization.

Automation eliminates manual steps

To prevent the occurrence of an incident occurs again, you should always try to find the root cause for each incident to resolve the problem permanently. Unfortunately, you can not always determine the root cause of the incident. In other cases, it is too expensive to implement the necessary actions toprevent similar incidents to occur again

This is where automation comes into play!

Automation is about rationalizing away as many manual steps as possible to restore the availability or performance of an application as fast as possible. To define where to begin the process of automation, in your sea of applications, I recommend the following methods:

  • Regular follow-ups of what kind of incidents, and in which systems these incidents are the most frequent in, and then fix them with the help of automation.
  • Review which applications have the highest business impact in case of an incident and start with them.

Automation will result in both shorter, and fewer disturbances in your IT-operations, leading to significant cost savings over time.

Benefits of having more effective application operations

  • Higher availability, with fewer and shorter disturbances for the organization
  • Control your sea of applications
  • Structure, that minimalizes your person-dependency
  • Noticeable drop in labor-intensive support
  • significant  cost savings over time


At GetIT Nordic we can help you achieve a day where not only frustration is reduced, but a day where automated application management gives your system the business benefit it was planned to from the beginning.
For contact and questions visit: 0760-484005