This post is the latest post in our new blog series: How We Solve Problems. Each blog post focuses on a real-world client experience where Revelwood was presented with a unique or thorny problem. We’ll explain our approach to how we solved it.
Revelwood Client: A financial services company specializing in retirement and life insurance.
Planning Environment: IBM Planning Analytics
Problem: A review of their existing TurboIntegrator scripts found that many of their processes used pre-built source views. Each view differed only slightly. For example, one view would define subsets in approximately eight dimensions and focus on a single time period, while a second view would contain the same subsets and focus on a different time period. This approach led to more than 50 repetitive scripts that were run via chores.
How We Helped: We changed the approach to create a source view in the prolog. This allowed a single script to be run over and over via parameters that were defined during each iteration. This resulted in faster maintenance since changes only had to be coded once. It also ensured that changes to public views and subsets would not impact these scripts.
Do you have a challenge with your Planning Analytics environment? Let us tackle the problem! Send us a quick email!
