{"id":34555,"date":"2026-07-11T13:53:44","date_gmt":"2026-07-11T11:53:44","guid":{"rendered":"https:\/\/blog.ptvlogistics.com\/?p=34555"},"modified":"2026-10-27T15:06:18","modified_gmt":"2026-10-27T14:06:18","slug":"what-to-expect-with-a-ptv-optiflow-proof-of-concept","status":"publish","type":"post","link":"https:\/\/blog.ptvlogistics.com\/en\/transport-logistics\/what-to-expect-with-a-ptv-optiflow-proof-of-concept\/","title":{"rendered":"What to expect with a PTV OptiFlow proof of concept"},"content":{"rendered":"

[vc_row][vc_column][vc_column_text css=””]You’ve seen the demo. The slides look great. But your planners have one question that no slide can answer: <\/span>will it work on our routes?<\/span><\/i>\u00a0<\/span><\/p>\n

That’s exactly what a proof of concept (PoC) is for.<\/span>\u00a0<\/span><\/p>\n

In short, a PTV OptiFlow proof of concept lets you run PTV OptiFlow on your own planning situation, next to the way you plan today, so you can compare real results before you decide anything.<\/span>\u00a0<\/span>In this post, we’ll cover what a PoC is, how it fits into the path from PTV Route Optimiser<\/a><\/strong> to PTV OptiFlow<\/a><\/strong>, what a real life implementation looked like, and how to judge the results.<\/span>[\/vc_column_text][\/vc_column][\/vc_row][vc_row][vc_column width=”1\/2″][vc_single_image image=”29741″ img_size=”full” css=””][\/vc_column][vc_column width=”1\/2″][vc_column_text css=””]<\/p>\n

What is a PTV OptiFlow proof of concept?<\/span><\/b>\u00a0<\/span><\/h2>\n

A proof of concept is a test with your own data and your own rules. Not a generic demo.<\/span>\u00a0<\/span><\/p>\n

For teams still using <\/span>PTV Route Optimiser<\/span><\/a>, our legacy routing product, we offer an interface that links it to PTV OptiFlow. Both can run in parallel, so your current planning keeps going while you see what PTV OptiFlow would do with the same work.\u00a0<\/span>\u00a0<\/span><\/p>\n

That matters because nobody wants to bet tomorrow’s deliveries on an experiment.<\/span>\u00a0<\/span>[\/vc_column_text][\/vc_column][\/vc_row][vc_row][vc_column][vc_column_text css=””]<\/p>\n

Where the PoC fits in the upgrade path<\/span><\/b>\u00a0<\/span><\/h2>\n

The path from PTV Route Optimiser to PTV OptiFlow be summed up in five steps:<\/span>\u00a0<\/span><\/p>\n

    \n
  1. Contact.<\/span><\/b> You talk to the PTV Logistics team.<\/span>\u00a0<\/span><\/li>\n
  2. Match.<\/span><\/b> The team looks at how your planning works today and what you need.<\/span>\u00a0<\/span><\/li>\n
  3. Business case.<\/span><\/b> You build the case for the change.<\/span>\u00a0<\/span><\/li>\n
  4. Proof of concept.<\/span><\/b> You test PTV OptiFlow, with both products running in parallel.<\/span>\u00a0<\/span><\/li>\n
  5. Start saving.<\/span><\/b> You move to PTV OptiFlow.<\/span>\u00a0<\/span><\/li>\n<\/ol>\n

    So the PoC comes after the business case and before you commit. It’s where the numbers stop being estimates.<\/span>\u00a0<\/span><\/p>\n

    What a PoC looked like at Distrilog<\/span><\/b>\u00a0<\/span><\/h2>\n

    Let’s make this concrete with a real life implementation. <\/span>Distrilog<\/span><\/a>, a Belgian logistics provider with 350 vehicles, had been planning with PTV Route Optimiser ST. Its planners built a first plan and then adjusted it by hand for customer and driver preferences. When Distrilog decided to try PTV OptiFlow, it began with a business case and a pilot at a single depot.<\/span>\u00a0<\/span>[\/vc_column_text][\/vc_column][vc_column width=”1\/2″][vc_column_text css=””]Here’s how it went:<\/span>\u00a0<\/span><\/p>\n

    Tip: Not sure you’re ready for step 4? Start at step 1. A conversation doesn’t commit you to anything, so <\/span><\/i>get in touch with our team and try PTV OptiFlow<\/span><\/i><\/a> on your own routes.<\/span><\/i>\u00a0<\/span>[\/vc_column_text][vc_column_text css=””]<\/p>\n