In light of the heightened level of concern related to the spread of Coronavirus (COVIS-19) we want to provide an update on the actions Octane is taking to safeguard the health-being of our clients, our associates and their families.
Before you read further, please note, this blog details secure Gateway connection used for Planning Analytics deployed “on-cloud” Software as a Service (SaaS) offering.
Since the launch of Planning Analytics few years back, IBM has been recommending its users to move to Planning Analytics for Excel (PAX) from TM1 Perspective and TM1 Web. As every day new users migrate to adopt PAX, it’s prudent that I share my experiences.
As you plan to adopt IBM Planning Analytics cloud, it’s important to understand what it takes. This blog highlights areas you will be involved-in when you upgrade from on-premise TM1 10.x.x to Planning Analytics on Cloud.
Thank you if you have come back for more! Hope our last blogs of this series Unravelling TM1 : Lesser Known Facets – Part A & Part B were meaningful. In this part we will unearth & explore few more of these lesser known gems.
Business trip to Australia…
This Tuesday (25th Sep 2018) Octane Solutions proudly hosted a meeting for Senior Finance, IT Executives and Experts representing various companies and industries. The event was kicked-of by Mr. Amendra Pratap (MD, Octane Solutions) and Mr. Thomas Maddocks (ANZ Software Sales Leader - Commercial, IBM). This was followed by a solution demonstration conducted by Mr. Kevin Jessop (Lead FPM Solution Specialist, IBM) and a panel discussion.
Thank you to all who attended our Executive Breakfast event; We were pleasantly overwhelmed with the response and excitement in the room.
Redefining Planning and Analysis with an infusion of Visual, Cognitive, and Predictive analytics capabilities is now a reality.
Thank you if you have come back for more! Hope our last blog Unraveling TM1 : Lesser Known Facets – Part A was meaningful. In this part we will unearth & explore few more of these lesser known gems.
No matter how much we think we know about TM1, there are always these set of conditions that make you think “what-if there was a better way”??!! For example, not having to write a bunch of codes just to delete the subsets after using it in a Source View Or not writing the same area definition twice. What-if this could be done with less or no coding at all!