All clients

Client profile · Singapore

Optimization Analytics Technology

OAT develops decision-support software that combines operations research, mathematical optimisation and AI. Its tools help teams make planning and scheduling decisions when resources are limited and operating rules are complex.

What OAT offers

Supply chain network planning

Supply chain network planning

Request a demo

Use one network model to diagnose current performance, optimise routes and distribution centres (DCs), and plan facility changes as regional demand shifts.

Whiteboard walkthrough
  1. Production plants→ Distribution centres

    Where does the current network fall short?

    Map the current network

    Trace existing flows from facilities to customers.

    1. Plot the footprint14 plants feed 4 operating distribution centres serving 915 customer records.
    2. Trace the flowsFollow plant → distribution centre → customer. Add volume, tariffs and lead times to each route.
    3. Mark the gapsCircle long routes, high cost per case and late demand. The baseline is $10.98M a year with 91.20% delivered within 48 hours.
    Business value
    Find long routes, high unit costs and service gaps before changing the network.
    Technical detail
    Import sites, product demand, historical flows, tariffs, lead times and operating constraints. Explore supply paths on the interactive network map.
  2. Delivery routes↔ 48-hour service

    What changes if we reroute, redesign or raise service?

    Compare the alternatives

    Compare route, footprint and service scenarios on the same demand.

    1. Keep the four sitesReassign replenishment and delivery routes. Annual cost drops to $10.40M and 48-hour coverage reaches 92.86%.
    2. Let the model choose sitesTest the existing sites and 15 candidates. The lowest-cost design uses five sites at $9.57M a year and delivers 95.82% within 48 hours.
    3. Set a 99% service targetThe model selects seven sites at $10.17M a year, about $600K more than the lowest-cost design.
    Business value
    See what a higher delivery target costs and which facilities it requires.
    Technical detail
    Compare replenishment, delivery, storage, handling and inventory costs under common demand assumptions. Fix the footprint or let the model choose among existing and candidate sites.
  3. Opening and closure dates→ Future DC footprint

    When should we open or close a site?

    Plan the next five years

    Schedule facility changes as regional demand shifts.

    1. Years 1–2 · RedesignOpen Columbus and Dallas, close Philadelphia West and settle into a five-site network.
    2. Year 3 · ReallocateClose New York West as Northeast demand contracts. Move its customers to the remaining sites.
    3. Years 4–5 · ExpandOpen Minneapolis as Upper Midwest demand grows. The plan returns to five sites and meets the 95% within-48-hours target every year.
    Business value
    Time facility changes to match shifts in regional demand.
    Technical detail
    Optimise all five years together with annual demand forecasts and service constraints. The demo requires at least 95% of demand within 48 hours each year.

U.S. demo network

The illustrative network starts with 14 plants, four operating DCs, 15 candidate DCs and 915 customer records serving about 493,000 cases annually.

Annual cost and service in the demo
ScenarioOperating DCsAnnual costWithin 48 hours
Current network4$10.98M91.20%
Route optimisation4$10.40M92.86%
Minimum-cost redesign5$9.57M95.82%
High-service design7$10.17M99.00%

In the five-year demo, the model opens Columbus and Dallas and closes Philadelphia West in year one, closes New York West in year three, and opens Minneapolis in year four. The plan meets the 95% delivery target in every year.

AI assistance roadmap

OAT is developing AI assistance for model configuration, model diagnostics and conversational exploration of results. The sequence is proposed and delivery dates are undefined.

Empty container repositioning

Empty container repositioning

Request a meeting

Plan empty container moves so equipment is available where it is needed.

Whiteboard walkthrough
  1. Container arrivals⇄ Depot stock gaps

    Where is equipment out of balance?

    Equipment balance

    Identify surpluses and shortages

    Business value
    Spot equipment shortages before they disrupt bookings.
    Technical detail
    Compare stock and expected returns with demand by depot, equipment type and period.
  2. Surplus depot→ Empty transfer

    Which empty moves are feasible?

    Plan empty moves

    Match stock to demand across locations

    Business value
    Send empty equipment where it is needed most.
    Technical detail
    Evaluate feasible moves against lead times, capacity and transport costs.
  3. Equipment quantities→ Receiving depot

    What should dispatch move and when?

    Repositioning plan

    Specify origins, destinations and volumes

    Business value
    Give dispatch teams a movement plan they can execute.
    Technical detail
    Specify origin, destination, equipment type, quantity and departure period.
Less-than-container-load consolidation

Less-than-container-load consolidation

Request a meeting

Group smaller shipments to make better use of container capacity.

Whiteboard walkthrough
  1. Individual consignments+ Consolidation hub

    Which shipments could travel together?

    Shipment inputs

    Cargo sizes, routes and timing

    Business value
    Find orders that can share a container.
    Technical detail
    Capture shipment dimensions, weight, route and delivery windows.
  2. Compatible loads→ Shared container

    What fits within the container limits?

    Group shipments

    Find loads that can travel together

    Business value
    Use available container space more effectively.
    Technical detail
    Evaluate shipment groups against volume, weight and timing limits.
  3. Sailing→ Load manifest

    What should go on the manifest?

    Consolidation plan

    Assign shipments to containers

    Business value
    Give planners a load assignment they can check and execute.
    Technical detail
    Review shipment-to-container assignments, departure timing and remaining capacity.
Workforce scheduling

Workforce scheduling

Request a meeting

Build rosters around demand, staffing requirements and operating rules.

Whiteboard walkthrough
  1. Staffing demand→ Shift hours

    Where could coverage fall short?

    Staffing inputs

    Demand, availability and shift rules

    Business value
    Identify shifts at risk of understaffing.
    Technical detail
    Compare required headcount and skills with availability and qualifications.
  2. Qualified staff⇄ Shift assignments

    Who can cover the required shifts?

    Assign shifts

    Match eligible workers to staffing needs

    Business value
    Balance coverage with labour cost and roster rules.
    Technical detail
    Evaluate assignments against eligibility, working-hour limits and rest periods.
  3. Published roster→ Shift coverage

    Where should managers review the roster?

    Workforce roster

    Review coverage by shift

    Business value
    Show managers where to review gaps before publishing.
    Technical detail
    Compare assigned staff with required coverage by shift and role.
Custom optimisation

Custom optimisation

Request a meeting

Build decision models for specialised problems such as port scheduling, pharmaceutical supply planning and production scheduling.

Whiteboard walkthrough
  1. Operating process→ Operating constraints

    What decision are we trying to improve?

    Define the decision

    Set objectives, constraints and available data

    Business value
    Agree on what a better operational decision should achieve.
    Technical detail
    Specify decision variables, constraints and measures of success.
  2. Decision model→ Feasible plans

    Which options are feasible?

    Model and solve

    Compare feasible operating choices

    Business value
    Compare feasible options before changing operations.
    Technical detail
    Encode operational rules as constraints and test alternative inputs and objectives.
  3. Recommended plan→ Operational execution

    How will planners use the result?

    Use the result

    Put the recommended plan into the workflow

    Business value
    Give planners a recommendation they can act on.
    Technical detail
    Return decisions such as berth assignments, production sequences or supply quantities.