Reporting vs. Information System Architect
Information System architect is well known in IT industry. Means expert has to take care about connectivity and overall performance of production systems and Data warehouse. Furthermore, expert knowledge should be based upon deep production systems functionality and structure knowledge together with business processes. Production systems have to work smoothly with enough data flow to support normal functioning of systems. It is purely IT and process world. That’s it.
On the other side reports need special care, architect has to take care about all current reporting dimensional requirements are built into company information systems. Has to take care about reporting world: management reporting, expert analysis, internal and official reporting and etc. In addition architect needs to also take care about future reporting scaling and development. In other words, shall current business intelligence system function in future with new reporting features and requirements. Shall current system adopt new requirement easily or with lot of money, human, time effort.
Next field what reporting architect should have in mind are consolidated reports among company: internal and external reporting (do they provide trustable = equal figures in totals), referential reports and local analysis, global data definitions and local definitions and much more.
Finally, business intelligence architect should definitely take care about plausibility and reporting model redundancy of new business requirements. Such expert should also do following:
- Cancel inappropriate business requirements in sense of too much effort for to little benefits.
- Prioritize requirements.
- Check requirements and to add missing parts. To finalize requirements.
- Coordinate reporting efforts.
- Guide IT in building reporting system.
- Transfer and translate business requirements to IT language and mindset.
Taking care of company performance content is primary task of reporting architect.