How to make such an ERP system so that users do not run IT in reports
Those of you who are engaged in support of 1C, ERP or write accounting systems themselves are aware of the problem of the load of the IT department. If you do not support such systems, then just take a word - there is such a problem.
The constant desire to develop a system and changes in legislation lead to frequent releases and, as a result, a large flow of support tasks. A significant part of the flow is the task of finalizing (developing) the system reports.
The problem in the corporate sector is so relevant that there is a special term Self-service BI , the meaning of which is something like “a miracle system in which users do not run after IT reports”.
')
To solve this problem, there are many products, ranging from OLAP repositories, ending with report designers of different calibers. However, all these products, in my opinion, correct the shortcomings of the architecture of the ERP system, which could not be.
His experience in this matter was formulated in a speech at the XI Business Intelligence Forum. For 10 years of development, I formulated 10 rules that I tried to convey in 20 minutes.
I try to answer the questions:
Improving the system with:
Listened and know how to make the system even better? Welcome to the comments!
PS Friends, I understand that 20 minutes of the video will probably only be watched by those who are really interested in the topic. I would like to post an article instead of a video, but I simply don’t have time to write it on a presentation. I would be glad if someone took it.
But laid out at least in this form. Who needs, I hope, will take advantage.
The constant desire to develop a system and changes in legislation lead to frequent releases and, as a result, a large flow of support tasks. A significant part of the flow is the task of finalizing (developing) the system reports.
The problem in the corporate sector is so relevant that there is a special term Self-service BI , the meaning of which is something like “a miracle system in which users do not run after IT reports”.
')
To solve this problem, there are many products, ranging from OLAP repositories, ending with report designers of different calibers. However, all these products, in my opinion, correct the shortcomings of the architecture of the ERP system, which could not be.
His experience in this matter was formulated in a speech at the XI Business Intelligence Forum. For 10 years of development, I formulated 10 rules that I tried to convey in 20 minutes.
I try to answer the questions:
- How to design systems so that they belong to Self-service BI?
- How to distinguish good systems from bad when buying?
- How can you improve what is already there?
Improving the system with:
- Data model design
- Interface design and user interaction scenarios
- Self-reporting scripts
- Some useful tricks
Listened and know how to make the system even better? Welcome to the comments!
PS Friends, I understand that 20 minutes of the video will probably only be watched by those who are really interested in the topic. I would like to post an article instead of a video, but I simply don’t have time to write it on a presentation. I would be glad if someone took it.
But laid out at least in this form. Who needs, I hope, will take advantage.
Source: https://habr.com/ru/post/191598/
All Articles