Capabilities

From workbook to a run you can defend.

Beanome covers a network study end to end: describe the network in tables, branch scenarios, solve with mixed-integer optimization, and read a run that names the exact data it used. This page shows what each part does.

What it does

Built for the questions planners actually argue about.

Seven capabilities, each drawn the way it works in the product.

Objective hierarchy

Provide real business objectives

Objectives are solved lexicographically: priority 1 alone, its result fixed as a constraint, then priority 2 within it. A lower priority can never cost you on a higher one. Scope any objective to a group — maximize demand met for the key accounts, then minimize inventory at the Iberian sites.

  1. 1Maximize demand metkey accountsfixed
  2. 2Minimize inventoryIberiafixed
  3. 3Minimize costnetwork-widesolving
Site Location

Greenfield and Brownfield Analysis (COG++)

Centre-of-gravity studies for greenfield and brownfield, with advanced functionalities

Stress map

Discover hidden bottlenecks in your network

Visualize your network stresses across the time periods. Resolve using visual What-Ifs - right from the map.

Halos on the map · list in the panel
Working with data

Slicers, mass edit, workbook in and out

A slicer offers only the values actually present in your data. It defines the record set mass edit acts on. Import a workbook, export the tables a study reads — and only those.

Analytics

Decision Ready Network Analytics

Not merely reporting, but insights into network performance Ever growing ‘Widget Library’ to choose the most relevant charts and reports

Visualize In full glory

Maps

Backward and Forward tracking of material flows through the network “Play”: Witness your supply chain responding to peaks and valleys

Network Modeling Guide

Every field, and what it does to the answer

The guide lives inside the app, next to the grid. It says what each field means, what a blank means, and — where a field is stored but never reaches the model — says so plainly rather than inventing a purpose.

How a run is made

Describe. Branch. Solve. Keep the proof.

Four steps from a workbook to an answer you can trace back to its data.

  1. Describe the network

    The model is tabular — sites, materials, customers, demand, lanes, capacities, costs and the rules connecting them. Author it in the grid or bring a workbook. Slicers narrow a table to the records you mean; mass edit changes them in one move.

    Grid · workbook import / export · slicers · mass edit
  2. Branch a scenario

    A scenario is a pinned data version plus your changes to it. Ask “what if Porto closes in the winter peak” without touching the baseline. Scenarios have lineage — a child inherits its parent's changes unless it overrides them.

    Draft · lineage · pending changes shown, never silently dropped
  3. Solve, asynchronously

    The platform validates the model, picks a solution strategy for its size and structure, and runs it. Large models are decomposed automatically. Objectives solve in priority order, not as a weighted blend.

    Mixed-integer optimization · auto-decomposition · lexicographic objectives
  4. Read the run

    A run is immutable and bound to the exact model version it was produced from. Six months later it still names the data it used, and that data still exists, unchanged. Compare runs, read the map, export the tables, ask Isaac.

    Frozen snapshot · run compare · stress map · export
How it's built

Rules we keep, so the answer is worth trusting.

These are not slogans. Each one is a checked property of the product, or a decision recorded in its architecture.

  • A run always names the exact data it used.

    Versions are immutable and hash-addressed. A result can always be traced back to the input that produced it — and that input still exists.

  • Absent is not empty.

    A centre-of-gravity study has no bill of materials. Not an empty one — none. The tables an analysis does not read are simply not offered, so the data pane and the export can never disagree about what your scenario is.

  • Failures are classified, never guessed.

    An infeasible model is told apart from a timeout, and both from a platform fault, by the tier that knows. A failure nobody can attribute is recorded as unattributed rather than as a plausible-looking one.

  • The modeling guide is a checked property.

    The in-app Network Modeling Guide documents every field and what it does to the answer. A build gate compares it against the model itself: a field you find there exists, and a field that exists is there.

  • Blank usually means something.

    A lane with no distance is measured great-circle; an inventory row with no period applies to all of them. Each field's entry says what a blank means, and it is rarely “nothing”.

  • Workspaces are the isolation boundary.

    Data does not cross between workspaces. Sign-in is OIDC through the identity provider; an unknown identity is never auto-provisioned into a tenant.

What's available today

Stated plainly, rather than implied.

Beanome is in pilot. Here is what you can use now and what is being built — so the site does not promise what the product does not yet do.

Available in the pilot
  • Web applicationModel, scenarios, solves, runs, map, compare, Isaac, modeling guide
  • Workbook integrationImport and export your model as an Excel workbook, in Beanome's layout
  • Network optimization & centre of gravityBoth analysis kinds, deterministic and stochastic runs
In development
  • Public APIA credentialed programmatic API is in development; developer docs describe the contract
  • ERP data lakeSource extracts landed as received and derived into scenario data — an SAP extract has solved end to end in a spike
  • Cloud deploymentPilot runs on dedicated hardware; the architecture is portable and the cloud design is documented
Pilot programme

Bring a network. Leave with a run.

Bring a workbook and a question. We'll build the model with you and have scenarios to compare within weeks.

Request a pilot