Business Intelligence Architect

People become BI architects in different ways in different companies. A BI developer working in an in-house BI team over several years may get promoted to BI architect and then starts to perform the role of BI architect. Or a BI developer / analyst / tech lead working for an IT company with multiple client projects experience in various BI tools and technologies could become a BI architect with around 10 years of experience. Or a person switches to BI architect role from a non technical BI roles(BI analyst or BI Business Analyst) out of interest or better opportunities.

A general set of tasks carried out by BI architect is given below, may not be true for all BI architects.
  • A BI architect creates BI solution architecture diagrams and BI solution documents based on the high level program/project requirements. Creates technical roadmap.
  • Is involved in providing response to RFPs/RFIs.
  • Involved in BI tools selection, setting up framework (ETL framework, reporting templates, processes, etc.). Providing technical guidance to the project teams. For example BI architect may decide if Kimball approach should be used or Inmon.
  • Defines number of environments (ex sandbox, dev, QA, performance testing, pre-prod, prod) required based on the needs of the organization, comes up with server requirements (high availability, clustering, etc.) and database sizing.
  • Involved in tools migration/upgrade decision making and selection process.
  • Drives the BI technology side forward.
  • BI architect would be the go-to person for BI tools and technologies questions and decisions. 
  • BI architect would have end to end understanding of the BI solution. Has multiple tools experience and can decide which tools are best for the purpose.

Comments

Post a Comment

Thanks for your comment. It will be posted after checks.

Popular posts from this blog

ETL developer vs Data engineer

Image
Rephrased question : ETL developer vs Data engineer Answer : Unfortunately there are no strict industry standards on these job titles. That is just one part of it. Before ETL tools such as DataStage, Informatica, Ab Initio, etc., became popular, developers were hand coding every ETL flow. These ETL tools shortened the ETL flow development time to a great extent and allowed ETL developers to focus on business rule/logic/requirement (what to implement) than how to code it or optimize the code. There are many other benefits of using a tool but I won’t go into that in this answer. So an ETL developer with experience in these tools without any programming (coding) experience was/is able to design and develop end to end data flows. Whenever new types of source/target data format comes up, these tools catch up but it takes time, i.e., the ETL tool provider (e.g. Microsoft, IBM, etc.,) adds new components/connectors within the ETL tool to be able to work with new data format. For example, let’
Read more

3 years of IBI

This week (on 19th Feb 2020) I completed 3 years of IBI. To celebrate it I have created a Dashboard in Google Data Studio. So from now on instead of using the charts in the Google Sheets I will use the Dashboard. Google Data Studio is more user friendly and mobile friendly too, also it comes with easy to use filters and drill down/up capabilities. PDF version of the first 2 pages of the shareable dashboard is attached below. I am happy to share the first 2 pages of the IBI Dashboard, reach out to me if you would like to get the Google Data Studio IBI dashboard. Once you get the dashboard (without my data of course) you can make a copy of it and point it to your IBI data (assuming you have started), add more charts, pages, etc., and use it for your benefit. Like with every year, this IBI year too I have learnt a lot about myself, made new mistakes, changed several things about me. The benefits of IBI is much more than we can think of. Use it to know it. And what are some of the
Read more