We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Post your ideas
Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Help IBM prioritize your ideas and requests
The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive notification on the decision
Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.
Model release management for batch and web-service scoring
In CP4D analytics project, there is no model release management framework like SPSS Collaboration and Deployment Services (CaDS).
1. LEARNING - Running batch script for model re-training at some intervals(weekly or monthly), and save new model as the LATEST version.
2. EVALUATION - Running batch script for model evaluation that executes scoring model (both LATEST and PRODUCTION version) with test data and save predicted data to database. Analyst can check the result of predicted data (MAE, MAPE, and predicted data graphs) on BI tool after running batch.
3. RELEASING NEW VERSION - Running batch script of replacing PRODUCTION version. This batch makes LATEST version to PRODUCTION.
In case of batch scoring, there must be unique named scoring model/script because this scoring script is called by other program out of CP4D.
In case of real time scoring (web-service scoring), there must be unique URL for model/script because this URL is called by other program out of CP4D.
CaDS can address to these requirements by using CadS label feature. I use "LATEST" label to latest version, and "PRODUCTION" label to production version. After LEARNING, the LATEST label moves to the new version, but PRODUCTION label is kept on the version without moving. I can run RELEASING NEW VERSION batch script to move PRODUCTION label to any version I specified.
CP4D seems not to have these feature. Every creating new version of model, I have to create new project release with another name. It causes that the scoring web service URL of new version is not same as old version, so I have to change our scoring program that send REST request to the scoring URL in CP4D.
I strongly hope CP4D to add model release version management feature such as CaDS.
Do not place IBM confidential, company confidential, or personal information into any field.