Stratum.Connector provides different options for updating the Viewer Analysis Services cube and database with data from the Stratum database. Stratum.Connector V6.0 offered two main processing options. The recently released Stratum.Connector V6.3 introduced a third option. The various processing options were also re-named in V6.3 to better reflect their functionality.
In my last post I discussed getting your plan into your BI system. This allows for easy comparison to actuals so that you can monitor your performance vs. your plan. In that previous post I assumed that your plan and actuals were captured at similar business roll ups. For example, if you had a sales plan that was created by division, region, rep and customer you very likely have your actual sales captured by those same levels. This makes for easy comparison of sales to plan.
Now let’s consider the situation when the actual sales are captured one way, and the sales plan is created another. View Article…
In this post, we’ll cover the Stratum.Server DALOAD process for IBMi and the equivalent GISLSDRV process for Windows. View Article…
To plan or not to plan … this is not the question for this entry, although it is an interesting topic. In this post, I’d like to suggest a simple way to save time by taking further advantage of your business intelligence system to see just how close you are to the plan you established for this year’s performance.
When we talk to our customers about Flexible Information Delivery or FID (see my earlier posts), part of that concept is “what is it that we are trying to deliver?” Generally, we are trying to deliver either a comparative view, a trended view or a graphic view of information. There are many variations and combinations of these view types but they tend to be variations on a theme.
Then it’s what type of information are we delivering? Of course the answer to that question can be many and varied — just look at all the different types of information that can be collected and viewed in a solution like Silvon Stratum. But, one of the most common comparisons that we see is “sales to plan.”
This is the fourth and last in a series of blog entries where I have been discussing the four main integrated components of Stratum. I have covered Stratum.Server, Stratum.Planner and Stratum.Connector. Today I will discuss Stratum.Viewer.
Stratum.Viewer is an HTML web client that serves end users wishing to access and analyze the data stored in the Microsoft Analysis Services OLAP cube generated by Stratum.Connector. Stratum.Viewer is installed on a Windows server and as part of the installation process we create a Microsoft Internet Information Services (IIS) website that utilizes Windows Authentication to secure access to Viewer.
This is the third in a series of blog entries where I will be discussing the four main integrated components that make up Stratum. My first two blogs covered Stratum.Server and Stratum.Planner. Today I will discuss Stratum.Connector. And in my next post, I’ll provide an overview of Stratum.Viewer.
Stratum.Connector is the Windows server-based middleware component that connects the Stratum Data Base (DB) to Microsoft Analysis Services. It allows for the selection of any or all of the Stratum DB dimensions/attributes, categories, measures and time periods which are then used by the Connector to automatically create a Microsoft Analysis Services OLAP cube which serves as the data store for analysis with Stratum.Viewer. View Article…
In my earlier post on Flexible Information Delivery (or FID), I described a few ways in which different types of users may want to view their business performance information. With an open, non-proprietary data base for information storage and management we can easily continue to expand our delivery methods.
Let’s look at some of the information delivery methods that Silvon provides as examples that you may want to consider for FID in your enterprise.
This is the second in a series of blog entries where I will be discussing the four main integrated components of Stratum: Stratum.Server, Stratum.Planner, Stratum.Connector and Stratum.Viewer. My first blog covered Stratum.Server. Today I will discuss Stratum.Planner.
Stratum.Planner is a Windows client application that serves end users wishing to access and analyze the data stored in a Stratum database, as well as administrators who are tasked with managing the Stratum environment. Stratum.Planner has two main components which can be independently installed based on the needs of the user.
In any business intelligence system there are ultimately two objectives, the collection and management of information and the delivery of that information. Assuming we can tackle the collection and management of information (okay – this is a big leap, but for the purposes of this post we’ll assume that), we are faced with providing access to the information in our business intelligence system.
We know there are many types of users in many different roles that will need to use the information. Even an individual user may need the information delivered using different delivery methods based on both the type and purpose of that information. Within each of the different delivery methods we want to make sure a user sees the same numbers, in the same terminology and that security to the information is applied in a consistent fashion. View Article…
As the person responsible for helpline support here at Silvon I’ve decided to try my hand at blogging as a vehicle for providing information to current as well as future users and administrators of Stratum. As we began to discuss this idea here internally, we quickly realized there’d be no shortage of topics. So to start, we’ve decided to begin with a discussion of the various products and technologies that make up Stratum. A clear understanding of the Stratum architecture will make it easier for me to delve into the details of the many additional topics we have on our list.
Stratum is essentially composed of four main integrated products: Stratum.Server, Stratum.Planner, Stratum.Connector and Stratum.Viewer. These integrated products can be deployed across two different technology stacks as we will see further along in our discussions. I will focus on Stratum.Server today and the other three products in subsequent blog entries. View Article…