IBM DOC: reduce by 70% the cost of building optimization solutions
By: Giulia Burchi
Tags: Deployment, Ibm Doc, IBM, Optimization, Prescriptive Analytics

IBM DOC: reduce by 70% the cost of building optimization solutions

Use the new development platform from IBM to quickly create high-ROI prescriptive analytics solutions with a low TCO Giulia Burchi Follow Nov 25, 2020 · 5 min read

By using IBM Decision Optimization Center (DOC), you can create a fully deployed optimization application in just 100 person-days thanks to:

advanced web User Interface (UI), out-of-the-box

integrated user management (login, access rights, workspaces)

what-if analysis capabilities

containerized deployment (scalability, robustness failover capabilities)

By using IBM Decision Optimization Center (DOC), you can create a fully deployed optimization application in just 100 person-days

What is the real quantitative impact of DOC? How much does it accelerate the creation of applications for business users?

To measure the impact of DOC, we can take two different approaches:

Fixed scope: fix the scope of an average optimization application and compare the development budget. Specifically, build the same solution with and without DOC, and compare how many person-days it takes to do so. Fixed budget: fix the development budget (e. g.100 person-days) and compare the results. More in detail, using the same number of person-days, build two solutions, with and without DOC, and compare the features and functionalities.

1. Fixed scope: DOC is 3 times faster

Without DOC, developing an average optimization solution would take approximately 300 person-days. By using DOC, the development time is reduced by 70%, to 100 person-days (see the detailed estimation in the section below).

DOC is 3 times more efficient.

DOC accelerates the development of standard features by a factor of almost 12.2. Fixed budget of 100 person-days

We can classify development features into two main groups:

Standard features : these are those must-have functionalities that are typically shared across all optimization solutions, such as user authentication, data input-output management, basic data visualization, what-if capabilities, DevOps activities, tests, etc.

: these are those must-have functionalities that are typically shared across all optimization solutions, such as user authentication, data input-output management, basic data visualization, what-if capabilities, DevOps activities, tests, etc. Customized features: these are those functionalities that are specific to each application. They typically include the optimization model, complex data visualization graphics, and specific data processing tasks.

Customized features like the manual edition of a Gantt chart, are specific to each application. They bring significant value to business users.

When comparing developing with and without DOC, the time spent on customized features is the same. However, without DOC support, we would need to spend a significant amount of time to create standard features.

DOC accelerates the development of standard features by a factor of almost 12.

The table below shows the detailed time estimation on which we based our analysis.

2. Fixed budget: DOC application has a higher value and a lower total cost of ownership

With IBM DOC, we can build and deploy in just 100 person-days an average optimization application, very robust, and with all desired features and functionalities.

On the other hand, without using DOC, with 100 person-days resources, the result would be a basic and not robust application with:

Poor data visualization (no web UI, just some Excel tables)

No user management (login, access rights, workspaces)

No what-if analysis capabilities, no scenario support

Basic Docker-Compose deployment, no scalability, no failover, no robustness.

The development of custom features would be penalized as well: without a well-defined development framework, it is hard to test, identify issues, resolve bugs, and try different options. If more time is needed for testing and debugging, less time would be available for development, and the application will be poorly tested and with more bugs.

With limited functionalities and poor user experience, its adoption with business users will be more difficult, its downtime will be high and its overall maintenance over time will be more costly. In a few words, the total cost of ownership for the company will be significantly higher.

With the same overall budget, the application built with DOC would deliver a significantly higher value to the business and would represent a much lower total cost of ownership.

In 100 person-days of development without DOC, we obtain a low-quality application that will end up having a higher total cost of ownership (TOC).

DOC-based applications have a low TCO: thanks to the optimization server, they are easy to extend and allow for CPUs and Licences sharing; thanks to containerized technology, they are stable and cheap to maintain, and thanks to the use of open-source libraries, their UI is easy to extend and adapt.

The table below shows the detailed time estimation on which we based our analysis.