<!doctype html> <html class="notranslate" translate="no" lang="en"> <head> <script src="https://analytics.ahrefs.com/analytics.js" data-key="TozvaqbRyYzuG408EXF4CA" async></script> <meta charset="utf-8" /> <meta name="google" content="notranslate" /> <meta name="viewport" content="width=device-width,initial-scale=1,viewport-fit=cover" /> <meta name="theme-color" content="#14396E" /> <title>Rail validation planning beside DOORS | Cevelar</title> <meta name="description" content="DOORS remains the system of record. Cevelar plans which test must be re-run after a change, and which evidence still holds." /> <meta name="robots" content="index, follow, max-snippet:-1, max-image-preview:large" /> <link rel="canonical" href="https://cevelar.com/en/use-cases/validierungsplanung-schienenfahrzeuge" /> <link rel="alternate" hreflang="de" href="https://cevelar.com/use-cases/validierungsplanung-schienenfahrzeuge" /> <link rel="alternate" hreflang="en" href="https://cevelar.com/en/use-cases/validierungsplanung-schienenfahrzeuge" /> <link rel="alternate" hreflang="x-default" href="https://cevelar.com/en/use-cases/validierungsplanung-schienenfahrzeuge" /> <meta property="og:type" content="article" /> <meta property="og:site_name" content="Cevelar" /> <meta property="og:url" content="https://cevelar.com/en/use-cases/validierungsplanung-schienenfahrzeuge" /> <meta property="og:locale" content="en_US" /> <meta property="og:locale:alternate" content="de_DE" /> <meta property="og:title" content="Rail validation planning beside DOORS | Cevelar" /> <meta property="og:description" content="DOORS remains the system of record. Cevelar plans which test must be re-run after a change, and which evidence still holds." /> <meta property="og:image" content="https://cevelar.com/brand/og-image.png" /> <meta name="twitter:card" content="summary_large_image" /> <meta name="twitter:title" content="Rail validation planning beside DOORS | Cevelar" /> <meta name="twitter:description" content="DOORS remains the system of record. Cevelar plans which test must be re-run after a change." /> <meta name="twitter:image" content="https://cevelar.com/brand/og-image.png" /> <link rel="icon" href="/favicon.svg?v=3" type="image/svg+xml" /> <link rel="icon" href="/favicon.ico?v=3" sizes="32x32" /> <link rel="apple-touch-icon" href="/apple-touch-icon.png?v=3" /> <link rel="preload" href="/static/fonts/spectral-600-latin.woff2" as="font" type="font/woff2" crossorigin /> <link rel="preload" href="/static/fonts/ibm-plex-sans-400-latin.woff2" as="font" type="font/woff2" crossorigin /> <link rel="stylesheet" href="/static/brand-v2.css" /> <script>document.documentElement.classList.add('js');</script> <link rel="stylesheet" href="/static/content-v2.css" /> <script type="application/ld+json"> { "@context": "https://schema.org", "@graph": [ { "@type": "BreadcrumbList", "itemListElement": [ {"@type": "ListItem", "position": 1, "name": "Home", "item": "https://cevelar.com/en"}, {"@type": "ListItem", "position": 2, "name": "Resources", "item": "https://cevelar.com/en/blog"}, {"@type": "ListItem", "position": 3, "name": "Use cases", "item": "https://cevelar.com/en/use-cases"}, {"@type": "ListItem", "position": 4, "name": "Rail validation planning", "item": "https://cevelar.com/en/use-cases/validierungsplanung-schienenfahrzeuge"} ], "@id": "https://cevelar.com/en/use-cases/validierungsplanung-schienenfahrzeuge#breadcrumb" }, { "@type": "Article", "headline": "Validation planning beside DOORS", "url": "https://cevelar.com/en/use-cases/validierungsplanung-schienenfahrzeuge", "inLanguage": "en-US", "dateModified": "2026-09-16", "author": {"@type": "Organization", "name": "Cevelar", "url": "https://cevelar.com/"} } ] } </script> </head> <body class="content-page"> <!-- cvl:header --> <header class="site-header" id="siteHeader"> <div class="wrap inner"> <a class="brand-lockup" href="/en" aria-label="Cevelar"> <svg class="mark" viewBox="0 0 32 32" aria-hidden="true"><path d="M23.07 7.57 A11 11 0 1 0 23.07 24.43" fill="none" stroke="#14396E" stroke-width="4" stroke-linecap="round"/><circle class="gap-dot" cx="27" cy="16" r="2.3" fill="#FF7514"/></svg> <span>Cevelar</span> </a> <nav class="nav-links" aria-label="Primary"> <a href="/en#offer">Offer</a> <a href="/en#how-it-works">How it works</a> <a href="/en/arc">Arc</a> <a href="/en/team">Team</a> <a href="/en/blog">Resources</a> <span class="nav-lang" aria-label="Language"><span class="current">EN</span><span class="divider">·</span><a href="/use-cases/validierungsplanung-schienenfahrzeuge" data-lang-switch="de">DE</a></span> <span class="nav-cta-group"> <a href="/demo" class="btn btn-nav-ghost demo-start" data-event="demo_start_click">Demo</a> <a href="https://calendar.app.google/fdozN9HHvSZRGmG97" class="btn btn-nav demo-booking" data-event="demo_booking_click" target="_blank" rel="noopener noreferrer">Book a briefing</a> </span> </nav> </div> </header> <!-- /cvl:header --> <main class="cvUc"> <section class="content-hero has-instrument"> <div class="wrap"> <nav class="crumb" data-reveal aria-label="Breadcrumb"><a href="/en">Home</a><span class="sep" aria-hidden="true">·</span><a href="/en/blog">Resources</a><span class="sep" aria-hidden="true">·</span><a href="/en/use-cases">Use cases</a><span class="sep" aria-hidden="true">·</span><span class="crumb-current">Rail validation planning</span></nav> <div class="content-hero-shell"> <div class="content-hero-copy"> <h1 data-reveal>Validation planning beside DOORS</h1> <p class="lede" data-reveal>DOORS holds the requirement. Which test must be re-run after a change is not in the module.</p> </div> <div class="cvl-board" data-reveal aria-label="SYS-0218 after CR-19 in DOORS, demo data"> <div class="cvl-board-head"><span>SYS-0218 after CR-19</span><span>DOORS</span></div> <ul class="pass-list"> <li style="--i:0"><span class="p-key">Link</span><span class="p-val">Suspect  the tool is right</span></li> <li class="gap" style="--i:1"><span class="p-key">Evidence</span><span class="p-val">Recorded, validity open</span></li> <li class="gap" style="--i:2"><span class="p-key">Effort</span><span class="p-val">Not in the module</span></li> </ul> <div class="cvl-board-foot"><span class="cvl-gap-dot"></span><span>Demo data. No claim about a real project.</span></div> </div> </div> </div> </section> <section class="cvUc-prose" data-reveal aria-label="DOORS and validation planning"> <div class="wrap"> <div class="content-body"><div class="article"> <h2>The impact list for lab occupancy</h2> <p class="answer">Which test binds the bench, which binds the vehicle, which is documentation only. Impact comes from the delta against the previous baseline, not from link status. You decide whether to re-test, re-document, or record a deviation. The same list goes back to DOORS via ReqIF and CSV.</p> <h2>DOORS remains the system of record. That stays.</h2> <p>DOORS is the leading system for requirements, for good reason. Modules, links, baselines, history, access: the tool can do that, and it has sat there for years. A programme that runs it did not build that structure by accident. It grew because the vehicle, the variants and the change requests grew. Cevelar does not replace it. It starts where a changed requirement must become a test plan.</p> <p>Related: <a href="/en/use-cases/requirements-management">requirements management beside an ALM</a> and <a href="/en/use-cases/pruefplan-aus-lastenheft">test plan from an OEM spec</a>.</p> <h2>What suspect links do not decide</h2> <p>The test method on the requirement is an attribute in DOORS. Effort, duration and which resource is bound sit beside it, usually in a side list. The recorded evidence (against which revision, under which conditions) is not an object in the tool. Whether it still holds after a change request is a judgement, not a derivation. Reuse across vehicle programmes is the same at larger scale: a manual call, someone with the old report and the new spec side by side.</p> <p>Cevelar holds method and effort on the requirement itself, not as a side list. Suspect links in DOORS are the right alert. They do not say which bench still holds, which vehicle trial must be redone, and which occupancy then shifts.</p> <h2>Change request 19 on the door control</h2> <p>A door control, SIL 2. Requirement SYS-0218 requires release only below a speed threshold. Evidence was recorded on bench and vehicle trial against 5&nbsp;km/h, spec Rev. C. All figures in this section are demo data.</p> <p>The operator sends change request 19 (CR-19). The threshold becomes 3&nbsp;km/h. In DOORS the links on SYS-0218 go suspect. That is the right alert. It stops there. It does not say whether bench report V&amp;V-0312 can still be used, whether the vehicle trial must be set up again, or whether only the boundary-condition documentation needs updating.</p> <p>What remains open is what the recorded evidence is still worth. The bench was set up against 5&nbsp;km/h. The new threshold changes the condition, not necessarily the setup. Whether the evidence still holds depends on what was actually measured on the stand, not on the requirement text alone.</p> <p>Whoever re-tests wholesale after CR-19 binds a bench and a vehicle booked months ahead. Whoever leaves it standing carries the evidence situation into the next assessment round.</p> <h2>What Cevelar holds in the test plan</h2> <p>The stock comes from DOORS. Cevelar does not recapture the requirements. It reads the state (module, baseline, changes against the previous revision) and derives impact from the comparison. On the same requirement SYS-0218 then sit method, effort and the recorded evidence with revision and conditions.</p> <p>After CR-19 it shows that the bench was run against 5&nbsp;km/h and the condition changed; that the vehicle trial is bound to a software revision; what effort is set for a re-assessment or a repeat. Clauses from EN 50126 and, where software sits, EN 50128 or EN 50657 hang on the requirement, not in a folder. Whether to re-test, re-document or record a deviation stays your call.</p> </div> <div class="cvUc-shift-grid"> <div class="cvl-board" data-reveal aria-label="DOORS view of SYS-0218 after CR-19, demo data"> <div class="cvl-board-head"><span>SYS-0218 after CR-19</span><span>DOORS view</span></div> <ul class="pass-list"> <li style="--i:0"><span class="p-key">Link</span><span class="p-val">Suspect  the tool is right</span></li> <li style="--i:1"><span class="p-key">Method</span><span class="p-val">Attribute, not a plan</span></li> <li class="gap" style="--i:2"><span class="p-key">Evidence</span><span class="p-val">Recorded, validity open</span></li> <li class="gap" style="--i:3"><span class="p-key">Effort</span><span class="p-val">Not in DOORS</span></li> </ul> <div class="cvl-board-foot"><span class="cvl-gap-dot"></span><span>Demo data. No claim about a real project.</span></div> </div> <div class="cvl-board" data-reveal aria-label="Cevelar view of SYS-0218 after CR-19, demo data"> <div class="cvl-board-head"><span>SYS-0218 after CR-19</span><span>Cevelar view</span></div> <ul class="pass-list"> <li style="--i:0"><span class="p-key">Stock</span><span class="p-val">From DOORS, baseline Rev. C plus CR-19</span></li> <li class="gap" style="--i:1"><span class="p-key">Bench</span><span class="p-val">V&amp;V-0312, condition changed, re-assess</span></li> <li class="gap" style="--i:2"><span class="p-key">Vehicle</span><span class="p-val">Bound to a revision: re-run or deviation</span></li> <li style="--i:3"><span class="p-key">Effort</span><span class="p-val">Planning figure on the requirement</span></li> </ul> <div class="cvl-board-foot"><span class="cvl-ok-dot"></span><span>Demo data. State derived. Decision stays with you.</span></div> </div> </div> <div class="article"> <h2>The same subsystem, next vehicle programme</h2> <p>The same door control runs in a second vehicle programme, often with its own spec revision and country variants. Evidence is reusable when it is clear against which requirement revision and under which conditions it was recorded. Without that anchor, only the report remains  and the memory that  something comparable already ran . In Cevelar the anchor sits on the evidence.</p> <h2>EN 50126, the safety case, the assessment</h2> <p>EN 50126 sets the frame for verification and validation. EN 50129 requires the safety case with traceable chains. EN 50657 or EN 50128 apply where software sits in the subsystem. CSM-RA assesses the change, not the tool.</p> <p>Cevelar hangs clauses from EN 50126, EN 50128, EN 50129 and EN 50657 on the requirement and keeps history and evidence chains. You write the safety case. You pass the ISA, AsBo or NoBo assessment. The platform does not promise type approval or an authorisation to place in service.</p> <h2>How this shows up on a live programme</h2> <p>On a change already in DOORS, and on the matching test plan. Which evidence still holds after the delta, which test must be re-run, which occupancy shifts. Not as a rollout  on the module you already maintain. Hosted in Germany, on-premise on request.</p> <p>Built by engineers from test and validation, not from tool sales. <a href="/en/team">Who we are</a></p> </div></div> </div> </section> <section class="cvUc-related" data-reveal aria-label="Read on"> <div class="wrap cvUc-related-shell"> <div> <h2 class="cvUc-related-title">Beside, not instead</h2> <a class="cvl-arrow-link cvUc-related-hub" href="/en/use-cases">All use cases <svg viewBox="0 0 16 16" fill="none" stroke="currentColor" stroke-width="1.7"><path d="M3 8h10M9 4l4 4-4 4"/></svg></a> </div> <nav class="cvUc-related-index is-cards" aria-label="Related resources"> <a class="cvUc-related-row" href="/en/use-cases/requirements-management"><span><span class="cvUc-related-type">Use case</span><span class="cvUc-related-name">Requirements management beside the ALM</span></span><span class="cvUc-related-arrow" aria-hidden="true"><svg viewBox="0 0 16 16" fill="none" stroke="currentColor" stroke-width="1.7"><path d="M3 8h10M9 4l4 4-4 4"/></svg></span></a> <a class="cvUc-related-row" href="/en/use-cases/requirements-management-einfuehren"><span><span class="cvUc-related-type">Use case</span><span class="cvUc-related-name">Introduce RM (greenfield)</span></span><span class="cvUc-related-arrow" aria-hidden="true"><svg viewBox="0 0 16 16" fill="none" stroke="currentColor" stroke-width="1.7"><path d="M3 8h10M9 4l4 4-4 4"/></svg></span></a> <a class="cvUc-related-row" href="/en/use-cases/pruefplan-aus-lastenheft"><span><span class="cvUc-related-type">Use case</span><span class="cvUc-related-name">Test plan from spec sheet</span></span><span class="cvUc-related-arrow" aria-hidden="true"><svg viewBox="0 0 16 16" fill="none" stroke="currentColor" stroke-width="1.7"><path d="M3 8h10M9 4l4 4-4 4"/></svg></span></a> </nav> </div> </section> <section class="cvUc-cta" data-reveal aria-label="Next step"> <div class="wrap cvUc-cta-shell"> <h2 class="cvUc-cta-title">Run it on a real change.</h2> <p class="cvUc-cta-lead">A subsystem already in DOORS. We reply in person.</p> <div class="cvUc-cta-actions"> <a href="https://calendar.app.google/fdozN9HHvSZRGmG97" class="btn btn-primary demo-booking" data-event="demo_booking_click" target="_blank" rel="noopener noreferrer">Book a briefing</a> <a href="/demo" class="btn btn-secondary demo-start" data-event="demo_start_click">Start demo</a> </div> </div> </section> </main> <!-- cvl:footer --> <footer class="site-footer"> <div class="wrap foot-grid"> <a class="brand-lockup" href="/en"><svg class="mark" viewBox="0 0 32 32" aria-hidden="true"><path d="M23.07 7.57 A11 11 0 1 0 23.07 24.43" fill="none" stroke="#14396E" stroke-width="4" stroke-linecap="round"/><circle class="gap-dot" cx="27" cy="16" r="2.3" fill="#FF7514"/></svg><span>Cevelar</span></a> <div class="foot-meta"> <span>cevelar.com</span><span class="sep">·</span> <span>Hosted in Germany or on your premises</span><span class="sep">·</span> <span class="nav-lang" aria-label="Language"><span class="current">EN</span><span class="divider">·</span><a href="/use-cases/validierungsplanung-schienenfahrzeuge" data-lang-switch="de">DE</a></span><span class="sep">·</span> <a href="/en/team">Team</a><span class="sep">·</span> <a href="/en/blog">Resources</a><span class="sep">·</span> <a href="/en/impressum">Impressum</a><span class="sep">·</span> <a href="/en/privacy">Privacy</a><span class="sep">·</span> <a href="#cookie-einstellungen" id="footCookieLink">Cookie settings</a><span class="sep">·</span> <span>© 2026</span> </div> </div> </footer> <!-- /cvl:footer --> <!-- cvl:cookie --> <div class="cookie-banner" id="cookie-einstellungen" role="dialog" aria-live="polite" aria-label="Cookie settings" tabindex="-1" hidden> <h3 class="cookie-banner__title" id="cookieTitle">Help us see where friction hides</h3> <p class="cookie-banner__text">With consent we see anonymized patterns of where people get stuck. No ads, no selling your data. <a href="/en/privacy">Learn more</a></p> <div class="cookie-banner__actions"> <button type="button" class="cookie-btn cookie-btn--primary" id="cookieAccept">Accept</button> <button type="button" class="cookie-btn cookie-btn--ghost" id="cookieDecline">Essential only</button> <button type="button" class="cookie-btn cookie-btn--link" id="cookieDetails">Learn more</button> </div> </div> <!-- /cvl:cookie --> <!-- cvl:sticky --> <div class="sticky-mobile-cta" id="stickyMobileCta" hidden> <a href="https://calendar.app.google/fdozN9HHvSZRGmG97" class="btn btn-primary demo-booking" data-event="demo_booking_click" target="_blank" rel="noopener noreferrer">Book a briefing</a> </div> <!-- /cvl:sticky --> <script src="/static/clarity.js" defer></script> <script src="/static/landing-v2.js" defer onerror="document.documentElement.classList.remove('js')"></script> </body> </html>