Planning Analytics

• Overview of containerization
• Modernize your TM1 model for the hybrid cloud world
• Improve uptime of TM1 databases with OpenShift

Hi everyone,

You can watch the on-demand recording here and download the slides here.

Please share any of your questions below.

• Overview of containerization
• Modernize your TM1 model for the hybrid cloud world
• Improve uptime of TM1 databases with OpenShift

1. Will there be a "readiness" tool to assess items that need to be addressed before you can migrate e.g. TI with ExecuteCommand, unsupported MDX, references to control cubes that have been deprecated?
2. How will promotion of Dev to to QA to Prod be handled - Not only TI but other objects e.g. Dims, Cubes, Rules etc. All via REST API, GitHub, Lifecycle Management, File upload tool and REST API?
3. What MDX changes are being made and what will no longer be supported / work?
4. Will Native cube views fall aways?
5. With containers not being for everyone and typically an enterprise requirement, how would smaller clients migrate to PA Engine/Next Gen to take advantage of new features in the future?
6. Email would need to be driven via the ExecuteHTTPRequest - Is IBM planning on creating a simple module that could be called from TI where you simply pass parameters for To, Subject, Body, Attachments, much the same way we do this now but leverage PowerShell to send the mails?
7. At what point/when would SaaS customers be upgrade/migrated to PA Engine/Next Gen? There is obviously some preparation required and code changes and we would need to plan accordingly on timelines, costs etc.

Hi everyone,

You can watch the on-demand recording here and download the slides here.

Please share any of your questions below.

• Overview of containerization
• Modernize your TM1 model for the hybrid cloud world
• Improve uptime of TM1 databases with OpenShift

@George Tonkin

Will there be a "readiness" tool to assess items that need to be addressed before you can migrate e.g. TI with ExecuteCommand, unsupported MDX, references to control cubes that have been deprecated?

 The TM1 to Planning Analytics Engine Migration Utility will address some of this.  For example, names of objects in the model that are unsupported by ODATA will be identified.  I don't believe we are currently to example MDX saved in views and sets to check for references to removed object names.  We can  consider an enhancement to the migration utility to check for references in MDX, rule, and Turbo Integrator scripts to cubes (e.g }CubeProperties) that no longer exist.

How will promotion of Dev to to QA to Prod be handled - Not only TI but other objects e.g. Dims, Cubes, Rules etc. All via REST API, GitHub, Lifecycle Management, File upload tool and REST API?

 The Git ODATA API endpoints will still exist in Planning Analytics Engine.  It's not yet determined how we will expose this capability in the Workspace Modeling Workbench.  The backup and restore feature of Planning Analytics Engine can also be used to migrate a whole model between environments.

What MDX changes are being made and what will no longer be supported / work?

MDX in Planning Analytics Engine is the same as MDX in TM1 v11.  We are slightly changing the way security works with MDX.

Will Native cube views fall always?

Native views still exist in Planning Analytics Engine.  No change yet.  There are a few features we need to complete before we consider removing native views (e.g drill thru to MDX and building MDX views with Turbo Integrator functions). 

With containers not being for everyone and typically an enterprise requirement, how would smaller clients migrate to PA Engine/Next Gen to take advantage of new features in the future?

Planning Analytics Engine will also (eventually) be available as part of a Planning Analytics SaaS offering.  

Email would need to be driven via the ExecuteHTTPRequest - Is IBM planning on creating a simple module that could be called from TI where you simply pass parameters for To, Subject, Body, Attachments, much the same way we do this now but leverage PowerShell to send the mails?

 We will provide sample Turbo Integrator code to show how the ExecuteHTTPRequest feature can be used with services, including an e-mail service.  We are not planning on building an e-mail service into Planning Analytics Engine.  We would consider providing a preconfigured e-mail service as part of a SaaS offering with Planning Analytics Engine.

At what point/when would SaaS customers be upgrade/migrated to PA Engine/Next Gen? There is obviously some preparation required and code changes and we would need to plan accordingly on timelines, costs etc.

There are no plans to deprecate the current Planning Analytics SaaS offering or Planning Analytics Local.  It's probably a bit early to provide any timeline.  However, we can talk about the differences between TM1 and Planning Analytics Engine to help you understand the work that is required to migrate.

1. Will there be a "readiness" tool to assess items that need to be addressed before you can migrate e.g. TI with ExecuteCommand, unsupported MDX, references to control cubes that have been deprecated?
2. How will promotion of Dev to to QA to Prod be handled - Not only TI but other objects e.g. Dims, Cubes, Rules etc. All via REST API, GitHub, Lifecycle Management, File upload tool and REST API?
3. What MDX changes are being made and what will no longer be supported / work?
4. Will Native cube views fall aways?
5. With containers not being for everyone and typically an enterprise requirement, how would smaller clients migrate to PA Engine/Next Gen to take advantage of new features in the future?
6. Email would need to be driven via the ExecuteHTTPRequest - Is IBM planning on creating a simple module that could be called from TI where you simply pass parameters for To, Subject, Body, Attachments, much the same way we do this now but leverage PowerShell to send the mails?
7. At what point/when would SaaS customers be upgrade/migrated to PA Engine/Next Gen? There is obviously some preparation required and code changes and we would need to plan accordingly on timelines, costs etc.

Hi everyone,

You can watch the on-demand recording here and download the slides here.

Please share any of your questions below.

• Overview of containerization
• Modernize your TM1 model for the hybrid cloud world
• Improve uptime of TM1 databases with OpenShift

@George Tonkin

Will there be a "readiness" tool to assess items that need to be addressed before you can migrate e.g. TI with ExecuteCommand, unsupported MDX, references to control cubes that have been deprecated?

 The TM1 to Planning Analytics Engine Migration Utility will address some of this.  For example, names of objects in the model that are unsupported by ODATA will be identified.  I don't believe we are currently to example MDX saved in views and sets to check for references to removed object names.  We can  consider an enhancement to the migration utility to check for references in MDX, rule, and Turbo Integrator scripts to cubes (e.g }CubeProperties) that no longer exist.

How will promotion of Dev to to QA to Prod be handled - Not only TI but other objects e.g. Dims, Cubes, Rules etc. All via REST API, GitHub, Lifecycle Management, File upload tool and REST API?

 The Git ODATA API endpoints will still exist in Planning Analytics Engine.  It's not yet determined how we will expose this capability in the Workspace Modeling Workbench.  The backup and restore feature of Planning Analytics Engine can also be used to migrate a whole model between environments.

What MDX changes are being made and what will no longer be supported / work?

MDX in Planning Analytics Engine is the same as MDX in TM1 v11.  We are slightly changing the way security works with MDX.

Will Native cube views fall always?

Native views still exist in Planning Analytics Engine.  No change yet.  There are a few features we need to complete before we consider removing native views (e.g drill thru to MDX and building MDX views with Turbo Integrator functions). 

With containers not being for everyone and typically an enterprise requirement, how would smaller clients migrate to PA Engine/Next Gen to take advantage of new features in the future?

Planning Analytics Engine will also (eventually) be available as part of a Planning Analytics SaaS offering.  

Email would need to be driven via the ExecuteHTTPRequest - Is IBM planning on creating a simple module that could be called from TI where you simply pass parameters for To, Subject, Body, Attachments, much the same way we do this now but leverage PowerShell to send the mails?

 We will provide sample Turbo Integrator code to show how the ExecuteHTTPRequest feature can be used with services, including an e-mail service.  We are not planning on building an e-mail service into Planning Analytics Engine.  We would consider providing a preconfigured e-mail service as part of a SaaS offering with Planning Analytics Engine.

At what point/when would SaaS customers be upgrade/migrated to PA Engine/Next Gen? There is obviously some preparation required and code changes and we would need to plan accordingly on timelines, costs etc.

There are no plans to deprecate the current Planning Analytics SaaS offering or Planning Analytics Local.  It's probably a bit early to provide any timeline.  However, we can talk about the differences between TM1 and Planning Analytics Engine to help you understand the work that is required to migrate.

1. Will there be a "readiness" tool to assess items that need to be addressed before you can migrate e.g. TI with ExecuteCommand, unsupported MDX, references to control cubes that have been deprecated?
2. How will promotion of Dev to to QA to Prod be handled - Not only TI but other objects e.g. Dims, Cubes, Rules etc. All via REST API, GitHub, Lifecycle Management, File upload tool and REST API?
3. What MDX changes are being made and what will no longer be supported / work?
4. Will Native cube views fall aways?
5. With containers not being for everyone and typically an enterprise requirement, how would smaller clients migrate to PA Engine/Next Gen to take advantage of new features in the future?
6. Email would need to be driven via the ExecuteHTTPRequest - Is IBM planning on creating a simple module that could be called from TI where you simply pass parameters for To, Subject, Body, Attachments, much the same way we do this now but leverage PowerShell to send the mails?
7. At what point/when would SaaS customers be upgrade/migrated to PA Engine/Next Gen? There is obviously some preparation required and code changes and we would need to plan accordingly on timelines, costs etc.

Hi everyone,

You can watch the on-demand recording here and download the slides here.

Please share any of your questions below.

• Overview of containerization
• Modernize your TM1 model for the hybrid cloud world
• Improve uptime of TM1 databases with OpenShift