STANDARD OR INDIVIDUALITY? BOTH!

In Business Intelligence as in real life, everyone is different, has his or her own ideas, needs and requirements. A software that supports controlling sustainably has to take this into account - you can't lump everything together. On the other hand, if you take a closer look and break down the overall requirement into individual parts, it becomes clear that it is recurring components that are necessary.

DECOMPOSITION INTO THE ATOMIC LEVEL

Like the whole world can be decomposed into atoms and their combinations (a piece of carbon consists of the same atoms as a diamond, only the arrangement is different), applications in CoPlanner are created from a finite set of different objects. The CoPlanner framework provides these: tables, dimensions, hierarchies, masks, shapes, SQL scripting etc. The combination of these elements can cover (almost) every imaginable requirement. The structuring of the requirement must specify a calculation path for how data is to be processed. Even if - current hype - self-learning systems are to be implemented, a specification must be made as to what is to be achieved and how.

BRINGING TOGETHER BUILDING BLOCKS AS A DESIGN PRINCIPLE

Creating solutions from these elements is not difficult, but you will save time if basic functions are already available as building blocks that can be reused. These building blocks then provide a basic framework to create applications faster. In every project we attach importance to identify such elements and, if such a building block does not yet exist, to extend the building set by another facet. A few randomly selected examples of such building blocks: