We turn operational constraints into software that finds better decisions: routes, rosters, schedules and energy use, planned around the rules your operation actually runs on.
Three kinds of operational decision, each a mathematical problem with real constraints. Forecasting tells you what is likely to happen; optimisation decides what to do about it. We build both, and keep them distinct.
Vehicle and crew routes that respect time windows, capacities, skills and shifts, and re-plan when the day changes.
Rosters and shift plans that cover demand, keep to working-time rules and share the unpopular shifts fairly.
Forecasts of what will happen, and schedules that decide what to do about it, for energy use, storage and assets.
Packaged route planners and scheduling products are built for the common case. When an operation has rules they can't express, the plan they produce is one your staff have to fix by hand. Cintrium builds optimisation systems around your constraints instead.
You get a written model of the operation, a solver that finds the best plan it can prove, scenario tools for what-ifs, and an interface your planners use without writing code. Every result is compared with the strongest simple method we can find and with your current process, and we say how close to the best possible it is proven to be.
Small demonstrations with synthetic data that run live in your browser. They illustrate the kind of systems we design and deliver.
Three depots cover six districts. An optimisation model finds the crew allocation with the least total travel, compares it with the rule of thumb it would replace, and re-plans when conditions change.
A data model of your assets and constraints, the optimisation engine with tests, a planner interface, an API for other systems, and documentation of every constraint and assumption.
| Depot | Riverside | Old Town | Harbour | Hillcrest | Airport | Industrial | Crews used |
|---|---|---|---|---|---|---|---|
| North | 4512 min | 020 min | 035 min | 018 min | 040 min | 030 min | 45 of 120 |
| Central | 022 min | 708 min | 5018 min | 4015 min | 028 min | 020 min | 160 of 160 |
| East | 038 min | 025 min | 514 min | 032 min | 3516 min | 6010 min | 100 of 100 |
| Demand | 45 | 70 | 55 | 40 | 35 | 60 |
Cells show crew-hours per day and the travel time for each. The nearest-depot rule serves each district in turn from the closest depot with spare crews.
Fuller demonstrations for prospective clients run on real road and asset locations: crew routing across Belgrade's road network, four-week rostering for a 24/7 operation, and a year of maintenance planning for Serbia's high-voltage substations. Ask us for access.
Request accessEach is a defined project with a working system at the end, scoped from a problem statement, a sample of your data and a budget.
Plans each day's routes for vehicles and crews under your time windows, capacities, skills and shift rules, with a planner's view and an API.
Builds rosters that cover every shift, respect working-time rules and requests, and re-solve when someone is off.
Forecasts of demand, load or volume, tested against simple baselines and fed into the planning models that act on them.
Decides when to run flexible load, charge or discharge storage and buy energy, against forecasts, prices and limits.
Chooses which assets to inspect or repair, and when, within budget and crew hours, to reduce expected failure cost.
Lets planners test a change, such as a closed depot, a budget cut or a new contract, before committing to it.
The disciplines behind every system, from the model to the software your planners use.
Every project moves through the same five stages, each with a clear output. At the end you own the system and can run it independently.
Understand the operation, its rules and constraints, the data available and what a better plan is worth.
Build a working model on your real data and compare it with your current method before the full build.
Turn the validated model into production software, with testing, documentation and appropriate security controls.
Deploy into your environment or the infrastructure agreed in the scope.
Source code, documentation, deployment instructions and knowledge transfer to your team.
Support and further development can be contracted separately. Neither is a condition of the project.
Tenders and fixed-scope contracts need a defined scope up front, evidence at each milestone and a clean handover at the end. We run every project that way.
| Deliverable | Stage |
|---|---|
| Defined scope and technical specification | Define |
| Written model of the constraints and objectives | Define |
| Acceptance criteria, agreed before the build | Define |
| Working prototype on your data, compared with your current method | Prototype |
| Testing evidence | Engineer |
| Deployment documentation | Deploy |
| Full source code | Handover |
| System documentation, and training where required | Handover |
Available for direct projects, subcontracting and consortium delivery.
A small team of engineers who write the models themselves, direct access to the people building your system, fixed deliverables and nothing you can't take with you.
Different sectors, similar problems: people, vehicles and assets to plan, rules that can't be broken, and existing tools that don't fit.
Waste and recycling rounds, highways and grounds crews, care rostering and fleet planning.
Demand forecasting, storage and load scheduling, asset maintenance and field crews.
Fleet routing, depot allocation, delivery scheduling and capacity planning.
Staff rostering, home-visit routing and resource allocation.
Crew scheduling, maintenance planning and job allocation.
Security is considered throughout the build, not added at the end. Specific security, regulatory and data-protection requirements are agreed as part of the project scope.
Send us the rules, the data you have and what a better plan would be worth. We'll tell you what can be built, how we'd model it and what delivery would involve.
Describe the problemTell us the operation, the constraints and the budget. If there is a specification or tender pack, link to it in your message.