AppTracker – Blueprints


What are Blueprints?

Blueprints in AppTracker are an extremely powerful tool.  It is our term for a labelled collection of applications. This could be all the applications in a department, in an office, in a site, in a country... It’s up to you!  Blueprints are held as a tree structure so you can create many levels of Blueprints to model your project deliverables. All of our reports can be run on Blueprints making our reports very powerful and very granular. 

Why are they so powerful?

Blueprints give you the power to chop up your applications portfolio anyway you want. Rather than looking at list of 3000+ applications and wondering how the project is going you can zoom into a single department and see if all its applications are ready. As Blueprints are held a tree it’s possible to zoom out a level and see how all the departments are doing. There is no limit to how granular you want to make your Blueprints, the more the better. 

An Example

Take a look at the Blueprint tree in the screenshot above. We have Offices > Europe > UK > London. I can filter my applications list to just the applications in London at one click. I can also see the status of all the applications in the UK or Europe … All at one click! As this is linked to reporting we can easily get a report on the progress of all the applications in UK, England, Europe etc. 

Security and Roles

Blueprints are an integral part of AppTracker and as such receive special attention around who can access them and what they can do. If you have an especially large number of AppTracker users (one of our clients has over 450 users / 4000 apps), you might not want all of those users to see all of the applications in the portfolio, only the ones that are relevant to them. It is possible to give an AppTracker user “read-only” or “read write”  access to all, some or none of the Blueprints and their associated applications. For example I can give all the UK BA’s access to only the UK Blueprint of applications and they will not see or even be aware of applications outside of those Blueprints. This is another example of how powerful Blueprints can be.