I simply got here lower back from a two week, round-the-international training engagement where i used to be a part of a group that provided a category on the way to use SmartView and economic reviews to retrieve statistics from Essbase. The magnificence turned into a achievement, and the customers all seemed to apprehend the material we blanketed. however, as I listened to the questions the users requested, I realized there may be an opening among the things we developers tend to recognition on and what the commercial enterprise analysts and managers need to analyze.
builders take a look at Essbase as a tool to build programs and databases. We focus at the elements of the software which could assist us do a better job in constructing a extra efficient solution.
stop-users examine Essbase as a device to assist them do their process. Their process is to offer evaluation on facts, understand what their employer is doing, and count on what their manager is going to ask next. For them, Essbase is just some other tool, like Excel, word, PowerPoint, and email; and all they want is to sense comfortable that the statistics in Essbase is accurate and well timed.
So, in which is the distance?
the gap among builders and stop-users is observed with regards to naming conventions, records vicinity, refresh timing, and use of the strength of Excel.
what is in a call?
stop-users recognition on organization names—e.g., Hyperion, Oracle, SAP—and these names emerge as synonymous with the statistics. Left unchecked, employer names turn out to be the names of the statistics supply. “is this Oracle statistics?” or “I pull facts from Hyperion,” are common sayings amongst end users. For them, the focus is at the statistics—the name of the software program or utility is secondary. developers, on the other hand, recognition at the custom Essbase utility and database names. in view that we use Hyperion for more than one statistics resources, we don’t consider it because the information supply. as a substitute, it’s miles a device we use to expand databases.
one of the first things we had to do at some stage in training changed into to give an explanation for the difference between ‘Hyperion,’ ‘Essbase’ and ‘SmartView,’ and the utility and database names we created in Essbase. organising a baseline of the names we used to describe the exclusive structures, packages and databases have become the cornerstone of the education. once we were given that out of the manner, each builders and stop users were capable of communicate truely.
where is the records?
quit-customers are all about statistics; builders are all about metadata. quit-users want to understand where the information is and what it represents. that is critical to the manner they do their task. They generally tend to cognizance on the precise slices of the database that relate to their vicinity of obligation. developers focus on hierarchies, shared contributors, measurement structure, calc scripts, and cargo guidelines. that is where they spend their time—making the cubes paintings higher and quicker.
So when developers train instructions, they clearly have a tendency to pay masses of attention to the metadata. Of route, the customers follow the commands of the developers and learn all about the dimension structure and the like, but what they virtually crave for is element on where the statistics is.