Author: Dr. Kostja Siefen
Date: 10/13/2020
As a Technical Account Manager in the mathematical optimization software industry for many years, I have had the opportunity to work with a wide variety of customers on their implementation projects.
Although each customer’s mathematical optimization application is unique, I have noticed that each project follows a similar, common pattern: Every mathematical optimization project (from initial idea to actual implementation) is a journey.
A solver like the Gurobi Optimizer is not a simple, “plug-and-play” type of software tool – it is a sophisticated AI technology that empowers companies to tackle their toughest problems, make the best possible business decisions, and realize optimal business outcomes.
Developing and deploying a mathematical optimization application in your organization is a challenging endeavor that requires not only the right technologies, but also the right expertise and the right approach. To achieve a successful implementation, you must be able to integrate and align mathematical optimization technologies with your existing software systems, your processes, and your people.
Reaching this goal is (as I said before) a journey – which takes time and effort, but can be successfully completed if you take the right steps. An important part of this journey is research and education. You’ll learn a lot along the way and some things may turn out differently than you expected.
At Gurobi, our team of experts is there to accompany you throughout this journey – to provide support, guidance, and assistance and help you navigate your way to a successful implementation of a solution powered by mathematical optimization.
In this series of blogs, I will try to give you a general sense of what you can expect on your journey, highlighting the key steps that you will take, the major milestones that you will reach, and the possible pitfalls that you may encounter. Just like a real journey, this implementation process can be challenging, and proper planning, good communication, and resourcefulness are critical when things don’t turn out the way you expected.
So – without further ado – let’s begin this journey together…
The Chinese philosopher Lao-Tzu once said, “The journey of 1,000 miles begins with a single step” – and this is true of your mathematical optimization journey.
So, what’s the first step on your journey? The first step is to have a discussion (or series of discussions) with all relevant stakeholders across various functions in your organization (including IT, R&D, Finance, Analytics, Data Science, Supply Chain, C-Level, and others) – and it would be wise to invite external, expert consultants from the mathematical optimization software industry as well.
It is imperative to invite all these stakeholders to these initial discussions, ask them questions, and get their ideas and perspectives – as failing to do so may ultimately result in issues later on in the implementation process such as:
Be aware that mathematical optimization systems are normally deeply embedded into a framework of systems and processes – so lack of alignment among stakeholders can become a major source of problems.
The way this initial discussion is framed will vary from company to company – as every company is starting their mathematical optimization journey from a different place. Maybe your company (like many companies out there) has identified a business problem that you think could be addressed with mathematical optimization, or maybe you a clear idea of a possible application, or perhaps you have already developed a prototype of an actual application.
But no matter what your starting point is, the aim of this initial conversation is the same: Get a full picture of your implementation landscape – which can be used to help create a roadmap for your implementation project. It is important to note that this picture and roadmap are by no means set in stone – you should always expect the unexpected and be prepared to change course if necessary.
The “getting a picture” analogy is particularly appropriate here – as mathematical optimization software implementations are more of an art than a science. Each company’s mathematical optimization application is unique, and each project begins essentially as an empty canvas. The main reason is that the technology itself is so universal that it can be used in nearly any time scale (from operational to strategic) at any level of automation.
In this initial project kick-off discussion, you – along with the other stakeholders and external experts present – will try to develop a picture of your entire implementation landscape with the software application on one side, the users on the other side, and the IT architecture in between. You should strive to define your underlying business problem as well as the overarching IT infrastructure for the software implementation as clearly as possible.  Make sure this picture is based on “what is possible” – not strictly “how”. In this early phase, you should also define functional and non-functional goals (also known as “user stories”), not tasks.
By doing this, all the stakeholders in your company can gain visibility over the entire implementation project, identify possible problem areas and issues that need to be addressed, and figure out how to design, develop, and deploy a mathematical optimization application that fits your business needs.
Be prepared to struggle with organizational barriers as soon as processes involve different departments with different goals and perspectives. It is not unusual to see internal competition and conflicting targets. Keep in mind that “optimization” always necessitates choosing a certain perspective to quantify the quality of an outcome. By synchronizing this perspective across all stakeholders, you avoid confusion and conflicts right from the beginning.
In this initial exploratory conversation with internal stakeholders and external experts, there are several key factors to consider as you try to develop a clearer picture of your mathematical optimization implementation:
By talking about and thinking about these three key factors, the full picture of your mathematical optimization implementation will begin to come into focus.
Once the big picture becomes clear, you will have a much better sense of how mathematical optimization technologies could integrate and interact with your company’s systems, processes, and people.
As always, communication is key. You must be able to ensure that – at this early stage – you get buy-in from all stakeholders, and have the green light to proceed on your mathematical optimization journey.
Gaining this holistic understanding of how mathematical optimization could fit into your business ecosystem is the first step (and a major milestone) on your journey.
For me as a Technical Account Manager, there is nothing more rewarding than accompanying and assisting customers as they progress on their mathematical optimization journeys from the first steps (the initial discussions and brainstorming described here) to the final goal (implementation and utilization).
Throughout their journey, customers can leverage the Gurobi team’s expertise (along with that of our consulting partners) to help them on the problem side (identifying which business problems should be addressed with mathematical optimization and how to solve them), on the tool side (figuring out how use a solver), and on the IT side (determining how to integrate the mathematical optimization application into their existing IT infrastructure).
In the next blogs in this series, I will take you through the next steps in your journey including evaluating and choosing a solver, designing a deployment architecture, creating a mathematical model of your business problem, and conducting development and testing of your mathematical optimization application.
GUROBI NEWSLETTER
Latest news and releases
Choose the evaluation license that fits you best, and start working with our Expert Team for technical guidance and support.
Request free trial hours, so you can see how quickly and easily a model can be solved on the cloud.
Cookie | Duration | Description |
---|---|---|
_biz_flagsA | 1 year | A Cloudflare cookie set to record users’ settings as well as for authentication and analytics. |
_biz_pendingA | 1 year | A Cloudflare cookie set to record users’ settings as well as for authentication and analytics. |
_biz_sid | 30 minutes | This cookie is set by Bizible, to store the user's session id. |
ARRAffinity | session | ARRAffinity cookie is set by Azure app service, and allows the service to choose the right instance established by a user to deliver subsequent requests made by that user. |
ARRAffinitySameSite | session | This cookie is set by Windows Azure cloud, and is used for load balancing to make sure the visitor page requests are routed to the same server in any browsing session. |
BIGipServersj02web-nginx-app_https | session | NGINX cookie |
cookielawinfo-checkbox-advertisement | 1 year | Set by the GDPR Cookie Consent plugin, this cookie is used to record the user consent for the cookies in the "Advertisement" category . |
cookielawinfo-checkbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". |
cookielawinfo-checkbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
cookielawinfo-checkbox-others | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. |
cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance". |
CookieLawInfoConsent | 1 year | Records the default button state of the corresponding category & the status of CCPA. It works only in coordination with the primary cookie. |
elementor | never | This cookie is used by the website's WordPress theme. It allows the website owner to implement or change the website's content in real-time. |
JSESSIONID | session | New Relic uses this cookie to store a session identifier so that New Relic can monitor session counts for an application. |
viewed_cookie_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |
Cookie | Duration | Description |
---|---|---|
__cf_bm | 30 minutes | This cookie, set by Cloudflare, is used to support Cloudflare Bot Management. |
_biz_nA | 1 year | Bizible sets this cookie to remember users’ settings as well as for authentication and analytics. |
_biz_uid | 1 year | This cookie is set by Bizible, to store user id on the current domain. |
_hjAbsoluteSessionInProgress | 30 minutes | Hotjar sets this cookie to detect a user's first pageview session, which is a True/False flag set by the cookie. |
_mkto_trk | 2 years | This cookie is set by Marketo. This allows a website to track visitor behavior on the sites on which the cookie is installed and to link a visitor to the recipient of an email marketing campaign, to measure campaign effectiveness. Tracking is performed anonymously until a user self-identifies by submitting a form. |
bcookie | 1 year | LinkedIn sets this cookie from LinkedIn share buttons and ad tags to recognize browser ID. |
bscookie | 1 year | LinkedIn sets this cookie to store performed actions on the website. |
doc_langsBB | 1 year | Documentation system cookie |
doc_version | 1 year | Documentation system cookie |
lang | session | LinkedIn sets this cookie to remember a user's language setting. |
lidc | 1 day | LinkedIn sets the lidc cookie to facilitate data center selection. |
UserMatchHistory | 1 month | LinkedIn sets this cookie for LinkedIn Ads ID syncing. |
whova_client_id | 10 years | Event agenda system cookie |
Cookie | Duration | Description |
---|---|---|
_gat_UA-5909815-1 | 1 minute | A variation of the _gat cookie set by Google Analytics and Google Tag Manager to allow website owners to track visitor behaviour and measure site performance. The pattern element in the name contains the unique identity number of the account or website it relates to. |
Cookie | Duration | Description |
---|---|---|
_an_uid | 7 days | 6Sense Cookie |
_BUID | 1 year | This cookie, set by Bizible, is a universal user id to identify the same user across multiple clients’ domains. |
_ga | 2 years | The _ga cookie, installed by Google Analytics, calculates visitor, session and campaign data and also keeps track of site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognize unique visitors. |
_ga_* | 1 year 1 month 4 days | Google Analytics sets this cookie to store and count page views. |
_gat_UA-* | 1 minute | Google Analytics sets this cookie for user behaviour tracking. |
_gcl_au | 3 months | Provided by Google Tag Manager to experiment advertisement efficiency of websites using their services. |
_gd_session | 4 hours | This cookie is used for collecting information on users visit to the website. It collects data such as total number of visits, average time spent on the website and the pages loaded. |
_gd_visitor | 2 years | This cookie is used for collecting information on the users visit such as number of visits, average time spent on the website and the pages loaded for displaying targeted ads. |
_gid | 1 day | Installed by Google Analytics, _gid cookie stores information on how visitors use a website, while also creating an analytics report of the website's performance. Some of the data that are collected include the number of visitors, their source, and the pages they visit anonymously. |
_hjFirstSeen | 30 minutes | Hotjar sets this cookie to identify a new user’s first session. It stores the true/false value, indicating whether it was the first time Hotjar saw this user. |
_hjIncludedInSessionSample_* | 2 minutes | Hotjar cookie that is set to determine if a user is included in the data sampling defined by a site's daily session limit. |
_hjRecordingEnabled | never | Hotjar sets this cookie when a Recording starts and is read when the recording module is initialized, to see if the user is already in a recording in a particular session. |
_hjRecordingLastActivity | never | Hotjar sets this cookie when a user recording starts and when data is sent through the WebSocket. |
_hjSession_* | 30 minutes | Hotjar cookie that is set when a user first lands on a page with the Hotjar script. It is used to persist the Hotjar User ID, unique to that site on the browser. This ensures that behavior in subsequent visits to the same site will be attributed to the same user ID. |
_hjSessionUser_* | 1 year | Hotjar cookie that is set when a user first lands on a page with the Hotjar script. It is used to persist the Hotjar User ID, unique to that site on the browser. This ensures that behavior in subsequent visits to the same site will be attributed to the same user ID. |
_hjTLDTest | session | To determine the most generic cookie path that has to be used instead of the page hostname, Hotjar sets the _hjTLDTest cookie to store different URL substring alternatives until it fails. |
6suuid | 2 years | 6Sense Cookie |
AnalyticsSyncHistory | 1 month | LinkedIn cookie |
BE_CLA3 | 1 year 1 month 4 days | BrightEdge sets this cookie to enable data aggregation, analysis and report creation to assess marketing effectiveness and provide solutions for SEO, SEM and website performance. |
CONSENT | 2 years | YouTube sets this cookie via embedded youtube-videos and registers anonymous statistical data. |
dj | 10 years | DemandJump cookie |
djaimid.a28e | 2 years | DemandJump cookiean |
djaimses.a28e | 30 minutes | DemandJump cookie |
li_gc | 5 months 27 days | LinkedIn Cookie |
ln_or | 1 day | LinkedIn Cookie |
vuid | 2 years | Vimeo installs this cookie to collect tracking information by setting a unique ID to embed videos to the website. |
Cookie | Duration | Description |
---|---|---|
__adroll | 1 year 1 month | This cookie is set by AdRoll to identify users across visits and devices. It is used by real-time bidding for advertisers to display relevant advertisements. |
__adroll_fpc | 1 year | AdRoll sets this cookie to target users with advertisements based on their browsing behaviour. |
__adroll_shared | 1 year 1 month | Adroll sets this cookie to collect information on users across different websites for relevant advertising. |
__ar_v4 | 1 year | This cookie is set under the domain DoubleClick, to place ads that point to the website in Google search results and to track conversion rates for these ads. |
_fbp | 3 months | This cookie is set by Facebook to display advertisements when either on Facebook or on a digital platform powered by Facebook advertising, after visiting the website. |
_te_ | session | Adroll cookie |
fr | 3 months | Facebook sets this cookie to show relevant advertisements to users by tracking user behaviour across the web, on sites that have Facebook pixel or Facebook social plugin. |
IDE | 1 year 24 days | Google DoubleClick IDE cookies are used to store information about how the user uses the website to present them with relevant ads and according to the user profile. |
li_sugr | 3 months | LinkedIn sets this cookie to collect user behaviour data to optimise the website and make advertisements on the website more relevant. |
test_cookie | 15 minutes | The test_cookie is set by doubleclick.net and is used to determine if the user's browser supports cookies. |
VISITOR_INFO1_LIVE | 5 months 27 days | A cookie set by YouTube to measure bandwidth that determines whether the user gets the new or old player interface. |
YSC | session | YSC cookie is set by Youtube and is used to track the views of embedded videos on Youtube pages. |
yt-remote-connected-devices | never | YouTube sets this cookie to store the video preferences of the user using embedded YouTube video. |
yt-remote-device-id | never | YouTube sets this cookie to store the video preferences of the user using embedded YouTube video. |
yt.innertube::nextId | never | This cookie, set by YouTube, registers a unique ID to store data on what videos from YouTube the user has seen. |
yt.innertube::requests | never | This cookie, set by YouTube, registers a unique ID to store data on what videos from YouTube the user has seen. |