# ScaliRo – FleetEngine

> ScaliRo develops FleetEngine, a vendor-independent software platform for planning, simulating, and visualizing autonomous mobile robot (AMR/AGV) fleets. Based in Rosenheim, Germany. Standards: LIF (Layout Interchange Format) & VDA 5050.

ScaliRo GmbH provides FleetEngine — used by 1000+ users across 250+ projects — enabling logistics and manufacturing companies to plan robot fleet layouts, run simulations, and validate configurations before deployment. The platform supports 20+ customer-developed plugins (C#/.NET) and is standards-compliant (LIF & VDA 5050). Current version: FleetEngine 1.30.

## Product

- [FleetEngine Product Overview (DE)](https://scaliro.de/de/product/): Vendor-independent fleet planning and simulation platform — modules, ecosystem, use cases, deployment, licensing
- [FleetEngine Product Overview (EN)](https://scaliro.de/en/product/): English version of the product page
- [Editor (DE)](https://scaliro.de/de/product/editor/): Layout planning, DXF import, drawing tools, LIF export
- [Editor (EN)](https://scaliro.de/en/product/editor/): English version
- [Simulation (DE)](https://scaliro.de/de/product/simulation/): Fleet sizing, flow editor, statistics, bottleneck analysis
- [Simulation (EN)](https://scaliro.de/en/product/simulation/): English version
- [Visualization (DE)](https://scaliro.de/de/product/visualization/): Real-time fleet monitoring, VDA 5050 protocol transparency
- [Visualization (EN)](https://scaliro.de/en/product/visualization/): English version
- [AMR/AGV Planning & Simulation (DE)](https://scaliro.de/de/planning/): Planning loop (Editor, Simulation, Visualization), fleet sizing, LIF export, VDA 5050 telemetry, FAQ
- [AMR/AGV Planning & Simulation (EN)](https://scaliro.de/en/planning/): English version
- [VDA 5050 erklärt (DE)](https://scaliro.de/de/vda-5050/): What VDA 5050 is, MQTT-based message topics, why it solves vendor lock-in, relation to LIF, screenshots, cross-link to LIF page, official resources (VDA5050 GitHub spec, VDA topic page), FAQ
- [VDA 5050 Explained (EN)](https://scaliro.de/en/vda-5050/): English version
- [LIF – Layout Interchange Format erklärt (DE)](https://scaliro.de/de/lif/): What LIF is, what a LIF file contains, why it exists, relation to VDA 5050, how FleetEngine uses LIF, LIF JSON example, screenshots, cross-link to VDA 5050 page, official resources (VDMA guideline PDF, VDA5050 GitHub), FAQ
- [LIF Explained (EN)](https://scaliro.de/en/lif/): English version

## Services

- [Services & Deliverables (DE)](https://scaliro.de/de/services/): Cloud simulation access, LIF editor, reports, flexible pricing, best practices, engineering support
- [Services & Deliverables (EN)](https://scaliro.de/en/services/): English version of services

## Company

- [About ScaliRo (DE)](https://scaliro.de/de/company/): Founder story, team, timeline (founded 2020), partners, values
- [About ScaliRo (EN)](https://scaliro.de/en/company/): English version
- [Wie wir arbeiten (DE)](https://scaliro.de/de/how-we-work/): Vendor neutrality and what it costs, how every checkable claim is verified against the primary source, where AI is and is not used in ScaliRo content
- [How We Work (EN)](https://scaliro.de/en/how-we-work/): English version

## Careers

- [Karriere (DE)](https://scaliro.de/de/careers/): Open positions, benefits, application process, team photos
- [Careers (EN)](https://scaliro.de/en/careers/): English careers overview (all positions require German)
- [Softwareentwickler C#/.NET (DE)](https://scaliro.de/de/jobs/softwareentwickler-csharp-net/): Full-time developer role, C#/.NET backend plus Angular frontends, entry level possible, Rosenheim on-site
- [Teamassistenz (DE)](https://scaliro.de/de/jobs/teamassistenz/): Part-time office and back-office role, 15 hours across three mornings, Rosenheim on-site

## Contact

- [Contact (DE)](https://scaliro.de/de/contact/): Contact form, address (Rosenheim), email, map
- [Contact (EN)](https://scaliro.de/en/contact/): English contact page

## Blog

- [Blog (DE)](https://scaliro.de/de/blog/): Articles on mobile robot fleet planning, simulation, VDA 5050 and LIF, plus company news
- [Blog (EN)](https://scaliro.de/en/blog/): English version
- [Simulieren statt schätzen (DE)](https://scaliro.de/de/blog/simulate-before-you-invest/): Why static fleet-size calculations fail for mobile robots and how simulation validates fleet size and throughput before investing
- [Simulate before you invest (EN)](https://scaliro.de/en/blog/simulate-before-you-invest/): English version
- [VDA 5050 im Lastenheft (DE)](https://scaliro.de/de/blog/vda-5050-in-tenders/): Seven questions that turn a VDA 5050 clause into a verifiable commitment — version per robot type, topics and their granularity, actions with parameters, where the map lives, LIF layout exchange, traffic decisions and fallback, and the levels of evidence from factsheet to full-layout simulation
- [VDA 5050 in Tenders (EN)](https://scaliro.de/en/blog/vda-5050-in-tenders/): English version
- [VDA 5050: Braucht der Roboter noch eine eigene Karte? (DE)](https://scaliro.de/de/blog/vda-5050-map-on-the-robot/): Why the original idea of VDA 5050 was to make the map on the robot unnecessary, why the map stayed anyway (safety-field switching, marker references to floor codes, speed zones), why a mixed fleet carries several map worlds side by side, how version 2.1.0 made maps an object in the protocol with downloadMap and a map server, how LIF differs from the robot map, and what happens when a robot stops on an error
- [Does the robot still need a map of its own? (EN)](https://scaliro.de/en/blog/vda-5050-map-on-the-robot/): English version
- [Mehr Roboter, weniger Durchsatz (DE)](https://scaliro.de/de/blog/more-robots-less-throughput/): Why throughput does not scale linearly with fleet size, the three ranges of the throughput curve (linear, saturation, overload), the five layout properties that move the tipping point, why rules of thumb describe the fleet while the path network sets the point, and how a series of simulation runs at peak load finds it before procurement
- [More robots, less throughput (EN)](https://scaliro.de/en/blog/more-robots-less-throughput/): English version
- [Mischflotte AMR: Interoperabilität ersetzt keine Planung (DE)](https://scaliro.de/de/blog/mixed-fleet-interoperability/): VDA 5050 interoperability became a selling point in 2026. What it solves in a mixed fleet, where the bottleneck moves, and what that means for procurement.
- [Mixed AMR Fleet: Interoperability Is Not a Traffic Plan (EN)](https://scaliro.de/en/blog/mixed-fleet-interoperability/): English version
- [Übergabestationen: der unterschätzte Engpass der Flotte (DE)](https://scaliro.de/de/blog/handover-station-bottleneck/): Why the handover station, not the fleet, caps throughput: the station is a place with a cycle and a finite capacity rather than a point in the path network, three times meet there (approach and positioning, the load transfer, and release by the process behind it, which is the one most often missing and frequently the longest), extra robots lengthen the queue instead of the throughput, and the effective levers are a second transfer position, a buffer place, a shorter release time, a different distribution across the shift, and the approach direction
- [Handover stations: the bottleneck nobody sizes for (EN)](https://scaliro.de/en/blog/handover-station-bottleneck/): English version
- [LIF in der Praxis (DE)](https://scaliro.de/de/blog/lif-explained/): What the Layout Interchange Format exchanges (nodes, edges, stations, properties per robot type), why traffic control is explicitly excluded and stays with the master control system, how LIF and VDA 5050 divide planning time from runtime, and what the LIF 2.0 draft in public consultation until 25 September 2026 changes: renamed required fields, the term vehicle replaced by mobile robot, an inverted boolean in reachOrientationBeforeEntering, new corridors, and zones deliberately left out
- [LIF in practice (EN)](https://scaliro.de/en/blog/lif-explained/): English version
- [Humanoide Roboter im Lager: Die Flottenfrage bleibt dieselbe (DE)](https://scaliro.de/de/blog/humanoid-robots-vs-amr/): Why humanoid robots change the values but not the calculation of fleet sizing: the same four inputs (travel time, time at the station, charging, traffic) decide the fleet for every form factor, the real difference sits at the station because a mobile robot picks up and sets down while a humanoid grasps, humanoids make sense first where picking happens today while mobile robots cover long transport routes, why published list prices do not support a price comparison and cost follows price per robot times fleet size, and why layout planning should not wait for humanoids
- [Humanoid Robots in the Warehouse: Same Fleet Question (EN)](https://scaliro.de/en/blog/humanoid-robots-vs-amr/): English version

## Legal

- [Impressum (DE)](https://scaliro.de/de/imprint/): Legal notice per § 5 DDG
- [Imprint (EN)](https://scaliro.de/en/imprint/): English legal notice
- [Datenschutz (DE)](https://scaliro.de/de/privacy-policy/): DSGVO privacy policy
- [Privacy Policy (EN)](https://scaliro.de/en/privacy-policy/): English privacy policy

## Optional

- [Full site content for LLMs](https://scaliro.de/llms-full.txt): Complete text content of all pages in a single Markdown file