AppTracker - How it Works

In the modern world the application is king, so we thought it would be useful to map out a typical path an application would take through its lifecycle. Click on the processes in the image below to get an understanding of how AppTracker assists in that phase of the lifecycle.

Initial Request

To run a business effectively your organisation will require new and updated applications from time to time. This is typically known as "application churn". The churn volume will vary vastly depending on the organisation's size and type. Small organisations may only require a handful of new and updated applications each month, whereas very large organisations may have to deal with a few hundred requests in the same period. If you are an IT system integrator then you will have many customers all demanding applications each month. How is this best handled?

App Request.png

It depends on where you are right now; you may already have a system and process in place to handle these application requests. Perhaps you utilise a helpdesk/service desk system to log these requests? Perhaps you have an intranet or extranet webpage? Or perhaps it's simply a case of asking the right person (it's all about who you know right?). The key here is that we need to be able make this request visible to the right team or individual. 

AppTracker provides a web-portal for anyone in the business to raise new requests. Users are also able to browse the existing application catalogue (if you choose to enable this feature) so that they can see if the application already exists in the environment, or perhaps check on the progress of their requests. The form is fully-customisable so you can collect the information exactly as you need it. You can ask users for the date they need the software, and if you're feeling really brave you can allow them to set the priority of the request. If you already handle new application requests via another tool (service desk system for example) then you may want to look at using our API to automatically create a new request in AppTracker when one is created in the existing tool. Either way, it's key that your new application request enters your application workflow as soon as is possible so that there are no hold-ups in moving the request forward.

Time Saving

Why is this process more efficient with a workflow tool such as AppTracker?

  • Centralised and standardised software request process

  • End-users can search the existing application portfolio to help minimise duplicate requests

  • API allows integration with existing systems

Based on our experience you can make an approximate time-saving of 20% if you use AppTracker rather than email or manual methods for managing software requests.

Next process: Validation

To see what savings are possible for your organisation please refer to our ROI Calculator.