Mapping services to applications
The University of Oxford tends to view the key things we do at a service level, rather than the individual applications which underpin those services (such as the Identity & Access Management service, which is achieved using 16 different applications). Therefore, IT Services is working with others around the University to understand which applications are used by what services. Our article about the Applications Catalogue, published in September 2020, provides more background.
This work has been primarily based in IT Services, but different areas of the University are also helping to gradually map other services and applications.
Why have we mapped applications?
This is an excellent opportunity for transparency and making data more widely accessible, as well as the possibility for deduplication and rationalisation where we use multiple applications for the same services.
Mapping our application use also helps analyse the impact analysis, tracking where data flows from and to in the University (data lineage) and developing an understanding of the data involved (GDPR, sensitive data, application criticality, geographic location of data storage etc.)
It also offers the possibility of reviewing the cost of services - services are not generally costed, but applications are, and the mapping allows us to see the bigger picture more easily.
Where can the application mapping data be accessed?
This is available in our Enterprise Architecture toolset Casewise-Evolve. You can access mapping data either via 'applications' or via 'services' on the Casewise-Evolve website (requires VPN and Connect account details – all IT Services staff already have access).
Feed in to the catalogues
We have endeavoured to ensure the mapping is accurate, however we cannot capture 100 per cent the first time without user interaction and feedback.
With nearly 260 services mapped to applications, it's looking good, but we need your help to make it better. If you are aware of additional applications which support your service and these are not listed, please let us know. You can email us at firstname.lastname@example.org with your contribution. If required, we are also able to grant 'edit access' for you to update details directly.
Who is Casewise-Evolve designed for?
Now the database is more populated, Casewise-Evolve is becoming increasingly useful for those in data-related roles around the University. These might include business analysts and those using the data governance framework, as well as teams dealing with filtering, processes and impacts of data, such as the Service Desk.
Anyone who uses University data for decision-making or to help the University to run effectively will likely find it helpful to explore the resources on the Casewise-Evolve website.
If you want to find out more about Casewise-Evolve and how it can help you with your work, there are a few easy steps you can take:
- Visit the Casewise-Evolve SharePoint site: To find out more about Casewise and Evolve, Enterprise Architecture, user access and frequently asked questions (FAQs), please visit our Casewise-Evolve SharePoint site (open to all members of University staff).
- Gain access and explore Casewise-Evolve: All members of University staff can request read-only access to Casewise-Evolve. Please visit our IT self-service catalogue and search for ‘Casewise’ or ‘Evolve’ to submit your request. IT Services staff automatically have access.
- Training and introductory sessions: If you or your team are interested exploring Casewise-Evolve in more detail, please email us to arrange training sessions.