Many organisations building models in order to understand their enterprise. Different stakeholders, teams working together in central repositories to be prepared for solving future problems.

This presentation is focusing on Business Intelligence (BI) for Enterprise Architecture models/projects. Most important are the impact analysis reports, what happens if an application will be retired, or who is affected if an IT centre is no longer working are just a few possible questions to answer for an EA team.

Long time ago I started to develop reporting solutions embedded into application, to bring me up to speed with the latest reporting technology i studied the following books.

My video is focusing around reporting based on Enterprise Architecture (EA) data as i think it’s not quite common but a few of my clients start now exploring the benefits of impact analysis within their model.

An EA model has relationships between different information objects like Process, Organisation Unit, Location, Data, Applications, Technology these object are called POLDAT objects. But your repository needs to be extensible to add your user defined objects like Compliance Requirements to fulfil their requirements for e.g. SOX, Mifid, Basel, or other ISO systems.

The important part is that with the analysis of indirect relationships you can achieve amazing reports for Business Continuity Planning (BCP) or other business impact analysis.

Hopefully you found my video informative and if you need the presentation material please Login or Register below.

Modeling your enterprise is an important task and different stakeholders have different requirements. This presentation will explain how you can deal with this aspect and how you can build a consistent enterprise architecture model. Below you can find the english version, others languanges of this video are available in <<Login or Register to see the link.>>.

Enterprise Architecture is an exiting topic and the following books helped me to get a better understanding about Enterprise Architecture -- EA.

This video is about the different stakholder requirements, e.g. the Compliance Team, Enterprise Architecture Team, Operational Team and others. Everyone has a different set of requirements and would like to use different tools, techniques, notations (BMPN, Entity Modeling,..) and frameworks.

I am trying here to highlight the differences between the stakeholders but also point out possible solutions to get the most benefit for the Enterprise -- to have a central repository where all the information objects (POLDAT) are stored and cross referenced. Also the reporting aspect based on your BI (Business Intellingence) tool of choice is an important factor to undertake impact analysis.

Hopefully you found my video informative and if you need the presentation material please Login or Register below.