Back to Modern OR Practice
ApplicationApplied06.02
Modern OR Practice

OR in Industry

Where models meet practice across sectors.

Overview

OR in Industry focuses on where models meet practice across sectors. In the map of OR, it connects Airlines, Healthcare, Energy to decisions that must be modeled, solved, explained, and revised as evidence changes.

Airlines, healthcare, manufacturing, retail, energy, finance, telecom, transportation, public sector, sports, agriculture, and education all run on OR. The practical use case is clearest in adjacent OR applications, where the method helps turn constraints and tradeoffs into a decision artifact someone can inspect.

Core ideas

Airlines

Airlines is a core checkpoint for OR in Industry: define it concretely, attach units or rules where possible, and test whether stakeholders interpret it the same way.

Healthcare

Healthcare is a core checkpoint for OR in Industry: define it concretely, attach units or rules where possible, and test whether stakeholders interpret it the same way.

Energy

Energy is a core checkpoint for OR in Industry: define it concretely, attach units or rules where possible, and test whether stakeholders interpret it the same way.

Retail

Retail OR includes product allocation, shelf-space optimization, assortment, pricing, replenishment, routing, and staffing decisions.

Finance

Finance is a core checkpoint for OR in Industry: define it concretely, attach units or rules where possible, and test whether stakeholders interpret it the same way.

Public sector

Public sector is a core checkpoint for OR in Industry: define it concretely, attach units or rules where possible, and test whether stakeholders interpret it the same way.

How to use it

  1. 1Start with a concrete case from the surrounding OR area: write the decision, time horizon, actors, and objective in operational language.
  2. 2Translate the problem into Airlines, Healthcare, and Energy; define units and data sources for each one.
  3. 3Build a small instance of OR in Industry that can be solved or simulated by hand inspection before using full production data.
  4. 4Compare the recommendation against a baseline policy, not just against mathematical optimality.
  5. 5Document assumptions, sensitivity results, and the conditions under which the recommendation should be revisited.

Applications

Retail: allocate products to limited shelf or display space using price, demand, visibility, dimensions, and grouping rules.

Finance: optimize cash flow, portfolio choices, or capital allocation under return, risk, and timing constraints.

Manufacturing: allocate workers, materials, and production capacity to maximize profit or minimize cost.

Logistics: plan routes, transportation networks, and distribution policies under capacity and service constraints.

Common pitfalls

  • Applying OR in Industry because the label sounds appropriate while leaving the actual decision boundary vague.
  • Treating Airlines as a technical detail instead of a modeling choice that affects the recommendation.
  • Reporting one answer without showing sensitivity to demand, capacity, costs, or behavioral assumptions.
  • Ignoring implementation details such as data quality, explainability, ownership, and how users will override bad recommendations.

Resources