[{"data":1,"prerenderedAt":105},["ShallowReactive",2],{"VMnnIc00UCwgRoaPiC-Nz0rZIhteLB4wK12zcYPZ4Yo":3,"_apollo:default":103,"_apollo:identified":104},{"seo":4,"posts":15},{"social":5,"openGraph":11,"__typename":14},{"twitter":6,"__typename":10},{"cardType":7,"username":8,"__typename":9},"summary_large_image","dassault3ds","SEOSocialTwitter","SEOSocial",{"defaultImage":12,"__typename":13},null,"SEOOpenGraph","SEOConfig",{"nodes":16,"__typename":102},[17],{"id":18,"slug":19,"title":20,"uri":21,"excerpt":22,"locale":23,"featuredImage":26,"tableOfContents":34,"content":40,"date":41,"translations":42,"author":43,"tags":55,"globalTags":69,"brands":77,"keywords":88,"seo":91,"__typename":101},"cG9zdDozMTY1OTc=","integrated-rail-planning-silos","Breaking Planning Silos: Why Integrated Rail Operations Are a Strategic Imperative","\u002Fbrands\u002Fdelmia\u002Fintegrated-rail-planning-silos","\u003Cp>Rail operators have digitalized service, fleet, crew, yard and maintenance planning, yet these functions still operate in silos. \u003C\u002Fp>\n",{"locale":24,"__typename":25},"en_US","Locale",{"node":27,"__typename":33},{"large":28,"__typename":29,"medium_large":28,"thumbnail":30,"srcSet":31,"sizes":32},"https:\u002F\u002Fblog-assets.3ds.com\u002Fuploads\u002F2026\u002F09\u002Fpicture1-5.png","MediaItem","https:\u002F\u002Fblog-assets.3ds.com\u002Fuploads\u002F2026\u002F09\u002Fpicture1-5-150x150.png","https:\u002F\u002Fblog-assets.3ds.com\u002Fuploads\u002F2026\u002F09\u002Fpicture1-5-300x169.png 300w, https:\u002F\u002Fblog-assets.3ds.com\u002Fuploads\u002F2026\u002F09\u002Fpicture1-5.png 629w","(max-width: 300px) 100vw, 300px","NodeWithFeaturedImageToMediaItemConnectionEdge",[35,36,37,38,39],"The hidden cost of disconnected planning|the-hidden-cost-of-disconnected-planning-0","If integration is so obviously valuable, why hasn't it happened?|if-integration-is-so-obviously-valuable-why-hasnt-it-happened-1","Integration means connected decisions, not connected systems|integration-means-connected-decisions-not-connected-systems-2","Where to start|where-to-start-3","The real test|the-real-test-4","\n\u003Cfigure class=\"wp-block-image size-full\">\u003Cimg loading=\"lazy\" decoding=\"async\" width=\"629\" height=\"354\" src=\"https:\u002F\u002Fblog-assets.3ds.com\u002Fuploads\u002F2026\u002F09\u002Fpicture1-4.png\" alt=\"Freight rail yard with rows of rail cars and a city skyline\" class=\"wp-image-316599\" srcset=\"https:\u002F\u002Fblog-assets.3ds.com\u002Fuploads\u002F2026\u002F09\u002Fpicture1-4.png 629w, https:\u002F\u002Fblog-assets.3ds.com\u002Fuploads\u002F2026\u002F09\u002Fpicture1-4-300x169.png 300w\" sizes=\"auto, (max-width: 629px) 100vw, 629px\" \u002F>\u003C\u002Ffigure>\n\n\n\n\u003Cp>Rail operators have spent a decade digitalizing rail planning, one function at a time. Service planning, fleet management, crew scheduling, yard operations, maintenance and infrastructure planning are each better instrumented and better optimized than they were ten years ago. They are also still separate. The joins between them are held together with spreadsheets, email and a standing coordination meeting.\u003C\u002Fp>\n\n\n\n\u003Cp>I think the next real performance gains in rail planning will come from those joins. Connecting the decisions the functions make is a different program from making any one function smarter, and it is not the program most operators are running. It is worth being precise about why.\u003C\u002Fp>\n\n\n\n\u003Ch2 class=\"wp-block-heading\" id=\"the-hidden-cost-of-disconnected-planning-0\">\u003Cstrong>The hidden cost of disconnected planning\u003C\u002Fstrong>\u003C\u002Fh2>\n\n\n\n\u003Cp>The silos have a history. Rail planning has always worked as a cascade: the timetable is built first, rolling stock is diagrammed against the timetable, crew is rostered against the rolling stock plan and, finally, maintenance and yard work are fitted around what is left. Each step treats the one before it as fixed. For a long time that was the only way to make the problem solvable, and it still shapes how departments, systems and budgets are drawn.\u003C\u002Fp>\n\n\n\n\u003Cp>The cost of the cascade shows up quietly. A timetable change eats into crew availability. A rolling stock allocation collides with a maintenance window. \u003Ca href=\"https:\u002F\u002Fblog.3ds.com\u002Fbrands\u002Fdelmia\u002Fback-to-basics-understanding-rail-possession\">An engineering possession\u003C\u002Fa> removes yard capacity the freight plan was counting on. Each function did its job, and the network still underperformed.\u003C\u002Fp>\n\n\n\n\u003Cp>Some railways put a price on this. In Great Britain, Network Rail and train operators settle up every four weeks under the Schedule 8 performance regime, with payments based on the delay minutes each party caused the other, measured against a benchmark. Planned disruption is priced as well. Under Schedule 4, Network Rail compensates operators for possessions, and it pays more the shorter the notice it gives. A late change to an engineering plan has a number attached to it before a single train is delayed.\u003C\u002Fp>\n\n\n\n\u003Cp>North America has no equivalent regime, but the costs have been estimated. Researchers at the University of Illinois put the cost of holding a freight train at roughly $830 an hour for a bulk train, about $1,400 for a manifest train and up to $2,400 for an intermodal train once the value of the lading is counted (2012 dollars). Those figures cover crew, locomotives, fuel, cars and the shipper’s inventory for the delayed train alone. Delay passed on to other trains comes on top.\u003C\u002Fp>\n\n\n\n\u003Cp>And the knock-on effects can dwarf the first hour. When US supply chains seized up in 2021, average rail dwell times peaked at 12.4 days that April, according to the Bureau of Labor Statistics. BLS traces this to container backlogs at the ports meeting a rail industry that had spent years taking slack out of its operations under precision scheduled railroading. Each plan was lean on its own terms. Together they had no room to absorb a shock that none of them had caused.\u003C\u002Fp>\n\n\n\n\u003Cp>What these examples share is where the problem sits. Nobody planned badly inside their own function. The losses came from the interactions between functions, which no single team owns.\u003C\u002Fp>\n\n\n\n\u003Ch2 class=\"wp-block-heading\" id=\"if-integration-is-so-obviously-valuable-why-hasnt-it-happened-1\">\u003Cstrong>If integration is so obviously valuable, why hasn&#8217;t it happened?\u003C\u002Fstrong>\u003C\u002Fh2>\n\n\n\n\u003Cp>In my conversations with operators I rarely meet a planning leader who disputes the case for integration. I meet leaders whose incentives, systems and structures make it hard to act on. Three barriers come up repeatedly.\u003C\u002Fp>\n\n\n\n\u003Cp>The first is measurement. Each planning function is judged on its own number: fleet utilization, crew cost, the delay minutes attributed to it. Almost nobody is measured on the quality of a cross-functional trade-off, so those trade-offs get made implicitly, late and under pressure.\u003C\u002Fp>\n\n\n\n\u003Cp>The second is the systems. Timetabling, crew, maintenance and yard systems each carry decades of embedded rules, and each was bought to serve one department. Interfaces between them move data. They do not tell the crew planner what a timetable change will cost before it is published.\u003C\u002Fp>\n\n\n\n\u003Cp>The third is structural, and no software removes it. Labor agreements and fatigue rules limit how far crew schedules can flex. In much of Europe, regulation separates infrastructure managers from train operators, so planning is split across company boundaries by design. North American freight railroads own their track and have the same silos internally, with interchange and trackage-rights partners to plan around as well.\u003C\u002Fp>\n\n\n\n\u003Cp>Experienced planners have covered these gaps for years with what they carry in their heads. Many of them are now close to retirement, which is why I think the problem is getting urgent. It also says something about the kind of problem this is: an operating-model question first and a technology question second.\u003C\u002Fp>\n\n\n\n\u003Ch2 class=\"wp-block-heading\" id=\"integration-means-connected-decisions-not-connected-systems-2\">\u003Cstrong>Integration means connected decisions, not connected systems\u003C\u002Fstrong>\u003C\u002Fh2>\n\n\n\n\u003Cp>Many transformation programs have gone at this by integrating applications. That work matters, but it is a means. What an operator wants is for a change in service planning to show up in fleet planning straight away, for fleet decisions to shape crew scheduling and for maintenance requirements to be visible to every function they affect before commitments are made. Interfaces alone do not deliver that, because each system still holds its own version of the network. It takes \u003Ca href=\"https:\u002F\u002Fwww.3ds.com\u002Fproducts\u002Fdelmia\u002Flogistics-workforce\u002Frail-planning-operations\">one planning environment built on a single model of the network\u003C\u002Fa>, with its resources, rules and constraints, so that every function plans against the same reality.\u003C\u002Fp>\n\n\n\n\u003Cp>A four-stage ladder is a useful way to locate your own organization.\u003C\u002Fp>\n\n\n\n\u003Col class=\"wp-block-list\">\n\u003Cli>\u003Cstrong>Data exchange. \u003C\u002Fstrong>Systems pass files and messages, and planners still reconcile the plans in meetings.\u003C\u002Fli>\n\n\n\n\u003Cli>\u003Cstrong>Shared visibility. \u003C\u002Fstrong>Every function sees the same operational picture and the current status of every plan.\u003C\u002Fli>\n\n\n\n\u003Cli>\u003Cstrong>Coordinated decisions. \u003C\u002Fstrong>A proposed change in one plan shows its consequences in the others before it is committed, and planners can evaluate a scenario across functions in one pass.\u003C\u002Fli>\n\n\n\n\u003Cli>\u003Cstrong>Closed-loop optimization. \u003C\u002Fstrong>Optimization spans demand, capacity, fleet, crew, maintenance and yard, and execution data feeds back into planning continuously. Plans are steered by the operator’s own business KPIs, such as punctuality and asset productivity.\u003C\u002Fli>\n\u003C\u002Fol>\n\n\n\n\u003Cp>\u003C\u002Fp>\n\n\n\n\u003Cfigure class=\"wp-block-image size-full\">\u003Cimg loading=\"lazy\" decoding=\"async\" width=\"602\" height=\"319\" src=\"https:\u002F\u002Fblog-assets.3ds.com\u002Fuploads\u002F2026\u002F09\u002Fpicture2.png\" alt=\"Integrated rail planning maturity ladder with four stages\" class=\"wp-image-316601\" srcset=\"https:\u002F\u002Fblog-assets.3ds.com\u002Fuploads\u002F2026\u002F09\u002Fpicture2.png 602w, https:\u002F\u002Fblog-assets.3ds.com\u002Fuploads\u002F2026\u002F09\u002Fpicture2-300x159.png 300w\" sizes=\"auto, (max-width: 602px) 100vw, 602px\" \u002F>\u003C\u002Ffigure>\n\n\n\n\u003Cp>Most operators I speak with sit somewhere between stages one and two. The value curve steepens at stage three, because that is where planning stops being a sequence of handoffs. It is also where optimization starts to pay properly. Optimizing crew schedules against a fixed fleet plan, or yard moves without sight of maintenance, produces local improvements and pushes the complexity downstream.\u003C\u002Fp>\n\n\n\n\u003Cp>A caution on stage four. It does not mean solving timetable, fleet, crew, maintenance and yard as one giant mathematical problem. It means optimizers that work from the same model and respect each other’s constraints, with actual performance fed back so that the next plan starts from what really happened. That is a realistic target, and it is the one worth aiming for.\u003C\u002Fp>\n\n\n\n\u003Ch2 class=\"wp-block-heading\" id=\"where-to-start-3\">\u003Cstrong>Where to start\u003C\u002Fstrong>\u003C\u002Fh2>\n\n\n\n\u003Cp>None of this needs a five-year enterprise program to get going. \u003Ca href=\"https:\u002F\u002Fwww.3ds.com\u002Finsights\u002Fcustomer-stories\u002Fmrs-logistica-rail-freight-transport\">The operators making progress\u003C\u002Fa> tend to follow a similar sequence:\u003C\u002Fp>\n\n\n\n\u003Cul class=\"wp-block-list\">\n\u003Cli>Start with one high-friction boundary. Timetable-to-crew and fleet-to-maintenance usually hide the largest unmanaged trade-offs, so prove the value there before widening the scope.\u003C\u002Fli>\n\n\n\n\u003Cli>Build the shared operational picture before the algorithms. An optimizer run on fragmented, inconsistent data automates the disagreements between plans. The environment also has to hold the operator’s real rules (labor agreements, safety constraints, the quirks of the network) in one model. A generic template that operations must bend to fit will not last long in the control room.\u003C\u002Fli>\n\n\n\n\u003Cli>Move decision rights along with the technology. Someone has to own the trade-offs that span functions, and functional KPIs need rebalancing toward system outcomes. Otherwise the new visibility changes nothing.\u003C\u002Fli>\n\n\n\n\u003Cli>Make scenario evaluation a daily habit and measure it. A revealing internal metric is time-to-answer: how long it takes to credibly evaluate a what-if that touches more than one function.\u003C\u002Fli>\n\u003C\u002Ful>\n\n\n\n\u003Cfigure class=\"wp-block-image size-full\">\u003Cimg loading=\"lazy\" decoding=\"async\" width=\"602\" height=\"336\" src=\"https:\u002F\u002Fblog-assets.3ds.com\u002Fuploads\u002F2026\u002F09\u002Fpicture3-1.png\" alt=\"Rail planners reviewing integrated rail planning screens in a control room\" class=\"wp-image-316602\" srcset=\"https:\u002F\u002Fblog-assets.3ds.com\u002Fuploads\u002F2026\u002F09\u002Fpicture3-1.png 602w, https:\u002F\u002Fblog-assets.3ds.com\u002Fuploads\u002F2026\u002F09\u002Fpicture3-1-300x167.png 300w\" sizes=\"auto, (max-width: 602px) 100vw, 602px\" \u002F>\u003C\u002Ffigure>\n\n\n\n\u003Cp>This sequence is drawn from practice. One rail operator running about 800 freight services a week started with a single high-friction area, crew, rather than with an enterprise-wide program. It implemented a \u003Ca href=\"https:\u002F\u002Fwww.3ds.com\u002Fproducts\u002Fdelmia\u002Fquintiq\u002Frail-service-fleet-crew-planning\">workforce planning and rostering solution\u003C\u002Fa> in nine weeks, which gave planners one place to manage service commitments, crew availability and occupational health and safety rules together. A first step like that, delivered in weeks, is a foothold. Whether it grows into broader integration depends on the environment underneath. It has to extend to fleet, maintenance and yard, and across planning horizons from long-term capacity planning through short-term planning to day-of-operations replanning, without starting again.\u003C\u002Fp>\n\n\n\n\u003Ch2 class=\"wp-block-heading\" id=\"the-real-test-4\">\u003Cstrong>The real test\u003C\u002Fstrong>\u003C\u002Fh2>\n\n\n\n\u003Cp>If you lead planning, operations or technology at a rail operator, three questions will tell you more than a maturity assessment.\u003C\u002Fp>\n\n\n\n\u003Cul class=\"wp-block-list\">\n\u003Cli>Can your planners see the crew and fleet consequences of a timetable change before it is committed?\u003C\u002Fli>\n\n\n\n\u003Cli>How long does a credible what-if scenario take today: minutes, days or weeks?\u003C\u002Fli>\n\n\n\n\u003Cli>Who in your organization owns a trade-off that spans service, fleet, crew and maintenance?\u003C\u002Fli>\n\u003C\u002Ful>\n\n\n\n\u003Cp>If the answers are uncomfortable, that is where the opportunity is. The industry has spent decades investing in signaling, rolling stock, infrastructure and digital tools. How well those assets work together is decided in planning, and that is where I would look next. \u003Ca href=\"https:\u002F\u002Fblog.3ds.com\u002Fbrands\u002Fdelmia\u002Finnovations-in-advanced-planning-scheduling-for-rail\">Planning environments that support stage three\u003C\u002Fa> are in production at rail operators today. The choice is between treating planning as one connected decision space and assembling a portfolio of point solutions that rebuilds the silos in software. Operators that make the first choice should be able to run more service, more reliably, with the assets and people they already have.\u003C\u002Fp>\n\n\n\n\u003Cp>\u003C\u002Fp>\n\n\n\n\u003Cp>\u003Cstrong>For more information\u003C\u002Fstrong>\u003C\u002Fp>\n\n\n\n\u003Cp>To learn more about connecting rail planning decisions across service, fleet, crew, yard and maintenance, explore these resources:\u003C\u002Fp>\n\n\n\n\u003Cul class=\"wp-block-list\">\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwww.3ds.com\u002Fproducts\u002Fdelmia\u002Flogistics-workforce\u002Frail-planning-operations\">DELMIA Rail Planning &amp; Operations\u003C\u002Fa>: how one platform connects crew, fleet, service, network and yard planning across every planning horizon\u003C\u002Fli>\n\n\n\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwww.3ds.com\u002Finsights\u002Fcustomer-stories\u002Fmrs-logistica-rail-freight-transport\">MRS Logística customer story\u003C\u002Fa>: how a Brazilian rail freight operator cut driver shift planning from a week to seconds\u003C\u002Fli>\n\n\n\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fblog.3ds.com\u002Fbrands\u002Fdelmia\u002Finnovations-in-advanced-planning-scheduling-for-rail\u002F\">Innovations in Advanced Planning &amp; Scheduling for Rail\u003C\u002Fa>: why interoperable planning across horizons and functions is the new operating model\u003C\u002Fli>\n\u003C\u002Ful>\n\n\n\n\u003Cp>\u003C\u002Fp>\n","2026-10-09T08:26:05",[],{"node":44,"__typename":54},{"nicename":45,"description":46,"slug":45,"name":47,"firstName":48,"lastName":48,"avatar":49,"__typename":53},"prashanthmysore","Senior Director for Strategic Business Development, DELMIA","Prashanth Mysore","",{"default":50,"url":51,"__typename":52},"mm","https:\u002F\u002Fblog-assets.3ds.com\u002Fuploads\u002F2022\u002F03\u002Fprasanth-mysore-2-96x96.jpg","Avatar","User","NodeWithAuthorToUserConnectionEdge",{"edges":56,"nodes":64,"__typename":68},[57],{"isPrimary":58,"node":59,"__typename":63},true,{"slug":60,"name":61,"__typename":62},"thought-leadership","Thought Leadership","Taxonomy_topic","PostToTaxonomy_topicConnectionEdge",[65],{"id":66,"name":61,"uri":67,"__typename":62},"dGVybTo4ODAz","\u002Ftopics\u002Fthought-leadership\u002F","PostToTaxonomy_topicConnection",{"nodes":70,"__typename":76},[71],{"id":72,"name":73,"uri":74,"__typename":75},"dGVybTo5MTA2","Digital Transformation","\u002Ftags\u002Fdigital-transformation\u002F","Taxonomy_tag","PostToTaxonomy_tagConnection",{"edges":78,"nodes":85,"__typename":87},[79],{"isPrimary":58,"node":80,"__typename":84},{"slug":81,"name":82,"__typename":83},"delmia","DELMIA","Taxonomy_brand","PostToTaxonomy_brandConnectionEdge",[86],{"name":82,"slug":81,"__typename":83},"PostToTaxonomy_brandConnection",{"nodes":89,"__typename":90},[],"PostToTaxonomy_keywordConnection",{"title":92,"metaDesc":93,"opengraphAuthor":48,"opengraphDescription":93,"opengraphTitle":20,"opengraphUrl":94,"opengraphSiteName":95,"opengraphPublishedTime":96,"opengraphModifiedTime":97,"twitterTitle":48,"twitterDescription":48,"readingTime":98,"metaRobotsNoindex":99,"__typename":100},"Breaking Planning Silos: Why Integrated Rail Operations Are a Strategic Imperative - Dassault Systèmes blog","Rail operators have digitalized service, fleet, crew, yard and maintenance planning, yet these functions still operate in silos.","https:\u002F\u002Fblog-frontoffice-contrib-prd.itvpc.3ds.com\u002Fbrands\u002Fdelmia\u002Fintegrated-rail-planning-silos\u002F","Dassault Systèmes blog","2026-10-09T08:26:05+00:00","2026-10-09T08:26:10+00:00",8,"index","PostTypeSEO","Post","RootQueryToPostConnection",{},{},1791552361502]