“Switching to, and working with, the team from Gurobi has been a great experience.”
Michael NorthSr. Director, NFL
Over the past few decades optimization has made huge strides; what were once unsolvable problems are now solved in only seconds. Of course, the response to this advancement has been to tackle ever larger and harder problems. The US’s National Football League is a perfect example of this. Four people have 10 weeks to schedule 256 games over the course of a 17-week season. To some, that may seem like a lot of planning time available for seemingly few decisions. However, when you work it out, the number of possible schedules is well into the trillions. Imagine the number one followed by 19 zeros. A data scientist would take years to determine a good schedule out of that huge number of possibilities. Making the problem particularly hard is the addition of numerous “additional” constraints including not scheduling teams from shared markets, such as the NY Jets and Giants, to play on the same day/time, ensuring no team has more than three road games in a row, and increasing the importance of late-season games by scheduling as many divisional match-ups as possible in the final weeks.
Until the last decade, a wooden six-foot square board was used to map out who would play whom, when and where. Hung on a wall the board consisted of a grid with 17 rows representing each week of the season and 32 columns representing each team. The original goal was simply to find a feasible schedule and accomplishing that often consumed up to 90 percent of the available planning time. The remainder was spent tweaking that feasible schedule to improve either a specific team or network’s schedule. With the switch to computers and the increasing power of optimization, a dramatic shift happened. The focus migrated from schedule creation (which by itself is far more complicated than it was only a few years ago) toward schedule analysis. Before, the question facing the planning team was simply, “Can we just get it done?” Now, it is about finding the best possible schedule.
This shift is important, since building a great schedule can be as much art as science. For example, one goal of the scheduling process is to get the best match-ups in the TV time slots that have the widest possible audience. This is very challenging to do since it requires a subjective evaluation of the match-up while also ensuring the resulting schedule doesn’t violate any constraints such as the maximum number of away games in a row for a given team. In addition, these subjective evaluations can change dramatically during the course of the scheduling process due to a variety of factors, including free agency. The art aspect is central to the scheduling process. The planners can now evaluate any given schedule, identify what they want to change, and then see how that affects the overall schedule. If the resultant schedule is better, then it is the new leader; if not, it is dropped. Even as recently as a decade ago, planners might only have been able to look at five feasible schedules. Since adopting Gurobi in 2013, this number has increased dramatically, and now planners are able to generate and compare over 10,000 feasible schedules despite adding more and more constraints to the process every year.
The complexity of the NFL scheduling problem has grown exponentially over the past few years. A big part of the strategy for combatting this massive increase in difficulty was to move from a linear to a parallel approach to optimization. The NFL initially started with a single 24-core box, but a few years ago has moved to utilizing a room-full of 16-core servers. As is often the case with new technologies, you typically won’t reap the full benefits by applying existing strategies. Optimal Planning Solutions collaborated with the development team from Gurobi to rethink their approach to exploiting parallelism. This has enabled the NFL to employ a new approach, starting back in 2014. A key advantage of the parallelization approach is that a single problem is broken down into a finite number of smaller sub-problems, which are deployed to a pool of solving resources, all of which can share information, creating a much more coordinated search effort. This approach has allowed the NFL to:
In 2017, the NFL scheduling problem was solved across a network of more than 960 cores. In future years, as more difficult scheduling requirements continue to be added, this number will surely increase. The NFL has moved to a cloud environment, as it grants them a tremendous amount of computing power while minimizing the need for capital investment. Increasing problem complexity combined with optimization tools enhancements will make strong partnerships between experienced end-users such as the NFL and consulting firms such as Optimal Planning and focused solver developers like Gurobi even more important.
Discover how the NFL uses mathematical optimization to solve one of the hardest scheduling problems in existence. At first glance, the NFL’s scheduling problem seems simple: 5 people have 12 weeks to schedule 256 games over the course of a 17-week season. That might seem like plenty of planning time for seemingly few decisions, but – when you actually work it out – the number of possible schedules is well into the quadrillions. Making the problem particularly hard is the necessary inclusion of thousands of constraints addressing stadium availability, travel considerations, competitive equity, and television viewership.
In 2013, the NFL began using Gurobi’s mathematical optimization solver to tackle this incredibly complex scheduling problem. With mathematical optimization, NFL planners can generate and analyze more than 50,000 feasible schedules despite adding more constraints to the process every year. Now – instead of spending months manually creating a single feasible schedule – the NFL planners can focus on evaluating and comparing completed schedules to determine which should be selected as the final schedule.
Mike North, VP of Broadcast Planning and Scheduling at the NFL.
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. |