Tool + Decision Report

Alternative Powertrain Sizing Tool + Decision Report for AMR Teams

Screen battery-electric, hybrid-electric, and fuel-cell powertrain paths for AMRs. Estimate wheel-side torque, review assumptions, and compare evidence before shortlisting suppliers.

Distinct angle vs component-level pages: this workflow evaluates powertrain-path feasibility (torque, charging/refuel constraints, compliance, and lifecycle risk), not only motor or steer module selection.

Prepared by Adrian Kowalski, B2B Applications & OEM Program Lead.

Published May 18, 2026 | Page reviewed October 10, 2026 | EU machinery/ATEX, CRA, battery due-diligence, and ISO 3691-4, ISO 12100, and ISO 13849-2 lifecycle checks refreshed; other source dates remain listed in the evidence register.

Run free alternative powertrain sizing check Talk to an AMR drive engineer

The sizing calculator needs JavaScript to run. The report, assumptions, and references below remain available; contact AMRDriveUnit for an application-specific review.

Tool Input Layer

Defaults are tuned for a mid-payload indoor AMR fit baseline. Adjust boundaries to match your real vehicle, floor, and duty profile. Base mass and payload are combined automatically as total moving mass.

Result Layer

Rule-based screening only, not a probability, supplier approval, or validation result. Confirm wheel-side torque and thermal needs with OEM data and commissioning tests.

Empty state

Enter your AMR profile and run the check. The page will output architecture fit, torque reserve, and risk boundaries.

Tool Result Conclusions Related Pages Method & Evidence Evidence gaps Jurisdiction Bus Boundaries Pathway Boundaries Comparison Tradeoffs Risks FAQ Fuel-Cell Alias Powertrain Alias

52 public standards/regulation/market references

ISO/IEC/CiA/PNO/Beckhoff/ANSI/NIST/EUR-Lex/ATEX/OSHA/eCFR/PHMSA/DOE-NREL/EPA/EIA/IEA sources are mapped to method, risk, and tradeoff sections.

4 decision states with boundary warnings

Fit/review/risk/inconclusive outputs include explicit next actions.

3 alternative powertrain paths compared

Battery-electric, hybrid-electric, and fuel-cell pathways are benchmarked side by side.

Alternative Powertrain Report Summary

Core conclusions, key numbers, and audience boundaries are shown here so the tool result can be used in procurement and design decisions.

No result yet

Run the tool to generate torque, architecture fit, and risk-boundary interpretation.

Key numbers

19 Jul 2023 / 20 Oct 2026 / 20 Jan 2027

Corrigendum-aligned legal milestones for Regulation (EU) 2023/1230

Use this corrected milestone set in release gates. Do not reuse uncorrected 13th/14th legacy dates from older templates.

Evidence: S3, S13

ISO 3691-4:2023 -> ISO/DIS 3691-4

AMR/AGV baseline is active but revision is already in DIS stage

ISO now lists explicit DIS lifecycle markers (40.00 and 40.20), so review checkpoints should be tied to lifecycle state rather than static citation age.

Evidence: S1, S23

ISO 12100:2010 -> ISO/DIS 12100.3

Risk-assessment framework has an active draft successor

The listing now shows a second DIS loop and FDIS-registration marker, so hazard-file refresh gates should be tied to lifecycle state changes.

Evidence: S14, S24

IEC 60529 vs ISO 20653

IP code boundary that affects interpretation of IP69K language

This page treats IP69K as an environment-specific claim requiring context, not a universal shorthand.

Evidence: S4, S5

31.25 us

PROFINET base clock from guideline reference

Used to frame expected controller-network timing discipline in higher-dynamic steering-drive loops.

Evidence: S9

>10 ms / <5 ms & >250 us / <250 us

PROFINET guideline time-requirement bands

PNO guideline classifies these as typical boundaries for RT/TSN free-running, IRT/TSN clock-synchronous, and manufacturer-specific ultra-fast solutions.

Evidence: S9

CC-A / CC-B / CC-C / CC-D

PROFINET conformance classes define minimum capability envelope

PNO guidance states CC-A should be used only when higher classes cannot be used; CC-C/CC-D align better with high timing demands.

Evidence: S9

10 to 1000 kbit/s

CANopen data-rate envelope (CiA summary)

For CANopen CC planning, CiA lower-layer guidance is more restrictive than generic CAN examples: while CAN HS headlines often cite about 40 m at 1 Mbit/s, CANopen CC planning uses about 25 m plus short stub limits.

Evidence: S10, S11, S16

50 us to >100 ms

TwinCAT task-cycle range in EtherCAT documentation

Used as a reminder that final behavior depends on full control-loop scheduling, not bus label alone.

Evidence: S12

<=100 us cycle / <=1 us jitter

EtherCAT public technology baseline for high-dynamic positioning

This is a technology-level reference, not an automatic application guarantee. Final timing still depends on full control-loop design.

Evidence: S25

100 m

Typical max cable distance between two EtherCAT participants

Beckhoff documentation decomposes the segment as 5 m patch + 90 m installation + 5 m patch; physical topology remains a first-order constraint.

Evidence: S18

B56.5-2024 + R15.08-2-2023

North America IMR/AGV safety baseline set

For US/NA deployments, acceptance evidence often requires this package view rather than ISO-only mapping.

Evidence: S19, S20, S21

29 CFR 1910.178(a)(2) -> ANSI B56.1-1969

Current OSHA codified anchor can lag newer ANSI consensus editions

OSHA publishes a 2022 proposed update to newer ANSI B56 editions; until a final rule is confirmed, treat consensus-version adoption as a legal-status check item.

Evidence: S37, S38

IEC 61800-5-1 + IEC 61800-3

Functional safety is not the full drive claim: add electrical-hazard + EMC path

Safety architecture claims should not stop at STO/PL language; electrical/thermal/energy hazards and EMC applicability boundaries need explicit verification.

Evidence: S7, S39, S40

CRA: 11 Jun 2026 / 11 Sep 2026 in force; 11 Dec 2027 main application

Cyber Resilience Act staged applicability for digital products

For connected steering-drive/control products, treat cybersecurity obligations as a release-gate timeline, not post-launch housekeeping.

Evidence: S28

ATEX Directive + CELEX 02022D1668

Explosive-atmosphere handoff baseline

When explosive-atmosphere scope is triggered, use ATEX legal scope plus the latest harmonised-standards list instead of extrapolating ISO 3691-4 intent.

Evidence: S29, S30

IEC 62619:2022 (AGV motive apps in scope)

Power-source stream cannot stay implicit

ISO 3691-4 excludes power sources, so battery safety has to be tracked as a separate requirement stream from day one.

Evidence: S1, S31

18 Aug 2027 (replacing 18 Aug 2025)

EU battery due-diligence obligations are postponed by 2 years

Regulation (EU) 2025/1561 amends Regulation (EU) 2023/1542 Article 48, so battery supply-chain compliance gates must be re-baselined in procurement plans.

Evidence: S32

UN 38.3 test-summary gate (49 CFR 173.185(a)(3))

Battery logistics evidence is a pre-shipment release dependency

For cells/batteries manufactured on or after 2008-01-01, test-summary artifacts must be available in the supply chain; missing summaries should block supplier approval.

Evidence: S41

ISO 24134:2006 (confirmed 2021) -> ISO/CD 24134

Automated steering/travel control baseline is legacy and in revision

The current document explicitly covers automated steering/travel/lifting control requirements but is marked "to be revised", so long-cycle programs should track replacement progress.

Evidence: S33

ISO/DIS 13849-2 lifecycle: 40.99 (approved for FDIS registration)

Safety-validation draft passed DIS voting and is approved for FDIS registration

Validation templates for SRP/CS should be version-locked and rechecked when lifecycle states move, not assumed static after design freeze.

Evidence: S34

NIST SP 800-82r3 (2023-09) + IEC 62443-2-1:2024

Cybersecurity requires technical control baselines, not date-only tracking

Use CRA milestones for legal gates and pair them with OT control-program evidence (architecture hardening, patch/vulnerability workflows, and lifecycle governance).

Evidence: S35, S36

1910.178(g)(1)/(2)/(10)/(11) + OSHA 4.1% LEL interpretation

Battery-electric charging path has explicit area, ventilation, and ignition-control requirements

Battery charging should be treated as a facility-safety workstream with measurable hydrogen-gassing controls, not as a generic utility task.

Evidence: S43, S44

1910.103 Table H-2 + 1 ft²/1,000 ft³ ventilation + 1 ft²/30 ft³ venting

Hydrogen storage/fueling path introduces facility-layout constraints beyond drive sizing

Fuel-cell pathway readiness depends on physical layout and ventilation governance, not only on vehicle torque calculations.

Evidence: S42

ISO 19880-1:2020 -> ISO/AWI 19880-1 (20.00 on 2026-01-20)

Hydrogen fueling baseline is not static and already in lifecycle transition

For long-cycle programs, lock review triggers to lifecycle changes so fueling requirements are re-validated before release gates.

Evidence: S45, S46

Fuel-cell MHE TCO delta (NREL 2013): 10% Class I/II, 5% Class III

Public cost benchmark exists, but only for multi-shift, larger-fleet deployments

Use these values as bounded historical reference points, not universal savings guarantees for every facility profile.

Evidence: S48

eGRID 2023 U.S. CO2 output rate 767.209 lb/MWh (range 242.776-1548.530)

Battery-electric emissions benefit is site-dependent, not universal

Use location-specific grid factors at bid stage; do not claim one fixed carbon benefit across all deployment regions.

Evidence: S49

U.S. industrial electricity average: 8.13 (2024) -> 8.62 (2025) cents/kWh

Battery-electric operating-cost baseline shifted upward in latest annual data

Use low/base/high tariff scenarios in TCO screens instead of one static kWh price assumption.

Evidence: S50

DOE program record snapshot: 21,838 units and >140,000 kW by end-2017

Fuel-cell material-handling deployment has industrial precedent, but this dataset is historical

Treat this as a maturity anchor only; economics still need current site-specific fuel, labor, and uptime data.

Evidence: S51

IEA 2025: ~100 Mt demand, low-emissions <1%, 2030 pipeline 49 -> 37 Mtpa

Hydrogen growth is real but project attrition and supply constraints remain

Fuel-cell business cases should include downside timing and fuel-cost scenarios, not only best-case rollout assumptions.

Evidence: S52

+15% to +40% reserve

Current sizing reserve policy in this calculator

This is an internal planning heuristic. No single public cross-vendor standard mandates this percentage window.

Evidence: Pending public benchmark (internal policy only)

Load split visualization

Architecture fit compass

Need supplier-ready validation next?

Use the tool output as the first filter, then move to diagnostics, control tuning, and compliance checks before RFQ lock-in.

Request engineering validation call Open diagnostics workflow page

Alternative Powertrain Methodology & Evidence

This section explains how outputs are derived, where assumptions begin, and which references support key decisions.

Method flow

Method detail table

Step	Formula / logic	Decision value	Boundary	Evidence
Traction baseline	Fr = c * m * g	Converts floor condition and gross mass into baseline resistance force before grade and acceleration are considered.	No universal public coefficient set covers all wheel compounds and contamination states; calibration must come from your pilot telemetry.	S1
Grade + acceleration force	Fcontinuous = Fr + (m * g * max grade); Fpeak = Fr + (m * g * grade) + (m * v / t)	Uses the entered maximum grade as sustained for a conservative continuous-force screen, and captures incline plus speed-ramp demand for peak sizing.	The continuous estimate intentionally assumes the maximum entered grade is sustained; reduce this only with a measured route profile. Peak sizing assumes linear acceleration and no wheel slip; high-jerk duty profiles require motion-profile simulation.	S1
Control-loop timing sanity check	Tresponse ~= Tcontroller + Tfieldbus + Tdrive	Communication and control timing can dominate slip and thermal behavior when dynamic demand is high.	Protocol labels are not enough. For demanding loops, validate where your application falls against published timing bands (for example >10 ms, <5 ms and >250 us, or <250 us manufacturer-specific paths) and verify service-layer behavior when TSN is introduced.	S9, S10, S16, S17, S12, S18, S26
Safety-architecture boundary	Safety claim valid only after PL/SIL target + verification are frozen	Avoids treating safety features as ready-made compliance outcomes before system-level validation.	ISO 13849-1 principles and IEC 61800-5-2 functions still require project-specific target definition and verification; ISO/DIS 13849-2 lifecycle movement shows validation guidance is active and should be revision-controlled; IEC 60204-1 scope starts at the electrical supply connection and does not remove the need for system-level stop-strategy design.	S6, S34, S7, S8, S15
Drive electrical + EMC boundary	Drive claim = functional safety + electrical/thermal safety + EMC applicability check	Prevents teams from treating STO/PL language as complete proof while electrical hazard and EMC obligations remain unresolved.	IEC 61800-5-1 and IEC 61800-3 both list traction/electric-vehicle exclusions, and IEC 61800-3 states radio transmission/reception requirements are out of scope; confirm product classification and additional standards path before final claims.	S7, S39, S40
Jurisdiction and scope gate	Applicable standard set = deployment region + operating scope	Prevents design teams from carrying one region or one standard package into a different regulatory acceptance context.	ISO 3691-4 excludes power-source requirements and some operating contexts. North America deployments commonly require B56.5/R15.08 package mapping in addition to ISO-based engineering references.	S1, S19, S20, S21
US codified-vs-consensus standard status gate	Mandatory baseline = codified CFR + legal status of updates	Avoids procurement and declaration plans that assume newer consensus editions are already mandatory when codified text still anchors legacy references.	eCFR 29 CFR 1910.178 currently references ANSI B56.1-1969 while OSHA update to newer ANSI editions is published as a proposed rule; treat this as a legal-governance check, not an automatic substitution.	S37, S38
Out-of-scope and cybersecurity gate	Scope handoff = environment boundary + connected-product obligations	Stops teams from treating legal scope exclusions and cybersecurity obligations as late-stage documentation tasks.	Explosive-atmosphere use should trigger ATEX path mapping, and connected digital products should map CRA staged dates into release governance with technical control baselines (for example OT security countermeasures and IACS security-program evidence).	S28, S35, S36, S29, S30
Power-source requirement stream	Battery safety baseline != traction mechanics baseline (parallel stream)	Prevents battery/power-source requirements from being silently dropped when teams focus on torque and motion architecture.	ISO 3691-4 scope excludes power-source requirements; battery safety and battery due-diligence obligations should be traced in dedicated requirement streams.	S1, S31, S32
Energy-path facility execution gate	Path decision = vehicle-side fit + site charging/refueling safety controls	Prevents teams from selecting battery-electric, hybrid-electric, or fuel-cell pathways using torque-only logic while facility controls remain undefined.	Battery-electric path requires designated charging-area controls (ventilation, ignition-source management, electrolyte handling). Hydrogen pathway adds explicit installation/layout constraints and fueling-standard scope limits; some variants remain outside published safety-scope envelopes and need additional engineering controls.	S43, S44, S42, S45, S47
Battery shipment evidence gate	Release readiness includes UN 38.3 test-summary availability	Stops teams from discovering missing lithium-battery transport evidence after hardware and supplier decisions are already frozen.	49 CFR 173.185(a)(3) requires UN 38.3 test-summary availability for cells/batteries manufactured on or after 2008-01-01 (with defined exceptions); convert this into explicit RFQ and release criteria.	S41
Per-wheel torque split	T = (F * r) / n	Maps total force to per-wheel torque requirement using wheel radius and number of traction wheels.	Assumes symmetric load sharing. Real vehicles need correction for CG offset and transient axle transfer.	S1
Reserve and risk adjustment	Trecommended = T * (1 + reserve)	Adds an internal policy buffer for duty-cycle heating, ambient stress, and ingress-related uncertainty; the optional shock factor is handled separately in peak force.	Reserve factor here is a policy choice (15%-40%), not a normative requirement.	S1, S6, S7

Regulation and standards timeline

Milestone	Date / version	Planning impact	Evidence
Regulation (EU) 2023/1230 enters into force	2023-07-19	Use this corrected force date in contract and declaration planning; avoid outdated 13 July date variants from pre-corrigendum copies.	S3, S13
Article-level early applicability gate (corrected point b)	2026-10-20	This corrected article gate is frequently misread as 2023 in legacy templates; update compliance checklists before design-freeze sign-off.	S13
Additional staged applicability points (corrected)	2024-01-20, 2024-07-20, 2025-07-20, 2026-07-20	Procurement and validation plans should map these dates to product-release gates and technical-file milestones.	S13
Full application date (corrected)	2027-01-20	Treat as hard gate for full conformity workflow on affected machinery placed on market; freeze one CELEX reference set in governance docs to avoid mixed-date drift.	S3, S13, S22
Cyber Resilience Act staged applicability	2026-06-11 (notified-body provisions in force) / 2026-09-11 (incident reporting in force) / 2027-12-11 (main application)	Apply the in-force notified-body and incident-reporting provisions where in scope; prepare secure-design and release-readiness evidence for the main application date rather than deferring cybersecurity work until launch.	S28
Battery due-diligence obligations postponed	2027-08-18 (replaces 2025-08-18)	Battery supply-chain compliance work should still start early, but legal gate planning must reflect the amended application date and the updated Commission-guideline date (2026-07-26).	S32
OSHA battery charging baseline and ventilation interpretation checkpoint	1910.178(g) codified baseline + 1976-01-26 interpretation	Battery-electric site planning should treat charging-area controls (designated area, ignition-source control, ventilation) as explicit release criteria; ventilation strategy should be traceable to measurable hydrogen-gas control assumptions.	S43, S44
OSHA hydrogen installation baseline for consumer premises	eCFR current text (title 29 updated through 2026-05-14)	Fuel-cell pathway facility design should include location ordering, distance constraints, and ventilation/venting requirements at concept stage rather than post-layout correction.	S42
ISO hydrogen fueling baseline lifecycle transition	ISO 19880-1:2020 -> ISO/AWI 19880-1 stage 20.00 (2026-01-20)	Long-cycle programs should schedule requirements-delta reviews for fueling architecture and indoor-dispensing controls before supplier and site lock.	S45, S46
IEC 62282-4-101 fuel-cell industrial-truck safety scope	Edition 2.0 published 2022-08-11	Use scope boundaries early to identify out-of-scope variants (for example explosive atmospheres, hybrid ICE trucks, liquid-hydrogen storage, removable containers) before design freeze.	S47
NREL fuel-cell MHE TCO benchmark publication	NREL/TP-5600-56408 (2013-04)	Use this as a historical, scenario-bound benchmark for multi-shift and larger-fleet economics, not as a universal savings claim for all warehouse profiles.	S48
ANSI/ITSDF B56.5 latest listed revision	2024	North America AGV programs should verify they are not still planning against B56.5-2019 assumptions where 2024 revisions now apply.	S19
ANSI/A3 R15.08-2 system/application requirement baseline	2023	IMR safety evidence in North America frequently requires Part 2 integration requirements, not just component-level claims.	S20, S21
OSHA powered industrial truck design reference update (status checkpoint)	2022-02-16 proposed rule (87 FR 8755)	Until a final-rule outcome is confirmed, do not assume newer ANSI references automatically replace codified 29 CFR 1910.178 baseline text in compliance workflows.	S37, S38
UN 38.3 test-summary availability gate in U.S. transport path	49 CFR 173.185(a)(3) baseline + harmonized requirement effective 2022-01-01 (button-cell exception effective 2024-05-10)	Battery supplier approval and service-parts logistics should include test-summary artifact checks before release and shipment readiness gates.	S41
ISO 12100 lifecycle state for risk-assessment baseline	Review confirmed 2022 (ISO 12100) + ISO/DIS 12100.3 at 40.99 (approved for FDIS registration; checked 2026-10-10)	Risk files should record the exact baseline revision and trigger revalidation checkpoints when DIS lifecycle states move.	S14, S24

Jurisdiction boundary mapping (EU vs North America)

Deployment scope	Baseline set	What it covers	Critical boundary	Evidence
EU/EEA industrial site deployment	ISO 3691-4:2023 + Regulation (EU) 2023/1230 timeline + battery due-diligence timeline	Driverless industrial-truck safety verification, machinery-regulation transition planning, and battery supply-chain due-diligence timeline governance.	ISO 3691-4 excludes power-source requirements and selected operation contexts; connected products may need CRA lifecycle planning, and battery due-diligence obligations apply on the amended schedule (18 Aug 2027).	S1, S3, S13, S28, S32
EU/EEA potentially explosive-atmosphere operation	ATEX Directive 2014/34/EU + current harmonised standards publication set	Defines legal scope and conformity path for equipment/protective systems intended for explosive atmospheres.	Do not reuse non-ATEX assumptions from general AMR guidance; verify harmonised-standard version applicability at each release gate.	S29, S30
North America IMR/AGV deployment	OSHA 29 CFR 1910.178 codified baseline + ANSI/ITSDF B56.5-2024 + ANSI/A3 R15.08-2-2023	B56.5 addresses driverless/automated industrial vehicle safety use, while R15.08-2 addresses IMR system and application requirements.	ISO-only evidence may be insufficient, and newer ANSI editions should be tied to explicit legal-status checks against codified OSHA references until final-rule updates are confirmed.	S37, S38, S19, S20, S21
North America indoor hydrogen-powered industrial truck deployment	OSHA 29 CFR 1910.178 + OSHA 29 CFR 1910.103 + ISO 19880-1 baseline + IEC 62282-4-101 scope check	Battery charging/fueling operations, hydrogen-system installation controls, and fuel-cell industrial-truck safety-scope screening.	Hydrogen atmosphere handling, ventilation, and truck-type restrictions can drive facility-layout and equipment-class changes; ISO/IEC references should be treated as supplemental engineering baselines rather than automatic codified substitutions.	S43, S44, S42, S45, S47
Cross-region product rollout (EU + North America)	Dual-track package: ISO/EU legal timeline + ANSI B56.5/R15.08 set	Creates one requirements baseline that supports both CE planning and North America deployment reviews.	Do not assume equivalence by label; map each requirement to a verifiable evidence artifact before RFQ freeze.	S1, S3, S13, S19, S20

Evidence gaps and how this page addresses them

Evidence gap	What the gap means	How this page addresses it	References	Record date
Regulation timeline relied on generic summary dates	Date-level compliance planning can fail if teams keep pre-corrigendum 13th/14th milestones in legal checklists.	Added corrigendum-backed milestone corrections and timeline notes with explicit replacement guidance.	S3, S13	May 18, 2026
Article 54 point (b) milestone was previously summarized with wrong year	Using 2023 instead of 2026 for this gate can shift legal-readiness actions by years and distort release planning.	Corrected the date to 20 Oct 2026 and linked it to governance action: freeze legal source version in project templates.	S13, S22	May 18, 2026
Fieldbus section lacked explicit applicability thresholds	Protocol labels alone do not define whether a loop belongs in RT, IRT/TSN clock-synchronous, or manufacturer-specific ultra-fast tiers.	Added timing-band boundaries (>10 ms, <5 ms and >250 us, <250 us) and linked them to decision tables.	S9, S26	May 18, 2026
Bus comparison lacked explicit counterexamples for speed claims	Readers can misread "5 Mbit/s today" as a hard ceiling and miss edge cases where optimized CANopen FD designs go higher.	Added counterexample/limitation framing (common 2/5 Mbit/s implementations vs optimized SIC/topology scenarios) and migration-governance actions.	S17, S27	May 18, 2026
Safety language did not make PLr scope boundary explicit enough	Readers can misread standards references as fixed PLr prescriptions for every AMR steering-drive scenario.	Reframed method and FAQ text to require project-specific target definition and verification before safety claims.	S6, S7, S8	May 18, 2026
CANopen boundary focused on bitrate but not deployment constraints	Decision risk is often underestimated when distance, node count, and diagnostics load are omitted from early planning.	Replaced generic CAN HS assumptions with CiA CANopen CC deployment limits (including 1 Mbit/s with short-bus/stub constraints) and added CANopen FD migration boundary notes.	S10, S16, S17	May 18, 2026
Safety section did not clearly separate electrical-equipment scope from system-level stopping claims	Teams may over-trust component-level safety functions without confirming full stop-strategy architecture.	Added IEC 60204-1 scope boundary and stop-function context to method/risk text so STO or emergency-stop statements are not treated as full-system proof.	S15, S8, S7	May 18, 2026
Cross-region deployment requirements were not explicitly mapped	Using only one regional standard stack can fail customer acceptance when projects are deployed across EU and North America.	Added jurisdiction boundary table with EU (ISO/EU regulation) and North America (ANSI B56.5 + R15.08) baseline mapping and decision guidance.	S1, S3, S13, S19, S20, S21	May 18, 2026
Risk-assessment baseline change management was implicit	Long program cycles can drift if teams do not track when referenced standards move into revision/replacement.	Added ISO 12100 lifecycle-state note and explicit revalidation action when replacement publication lands.	S14, S24	May 18, 2026
Draft-standard lifecycle states were represented with stale single-stage snapshots	Teams can miss revalidation windows if they only track one old DIS status and ignore subsequent lifecycle state changes.	Updated ISO/DIS 3691-4 and ISO/DIS 12100.2 lifecycle wording to include currently listed stage sequences and execution triggers.	S23, S24	May 18, 2026
Explosive-atmosphere boundary had no standards handoff path	Saying "out of scope" without an actionable baseline leaves hazardous-location projects with no immediate compliance route.	Added ATEX scope mapping and harmonised-standards publication reference (including EN 1755 listing context) in jurisdiction, method, and key-number sections.	S29, S30	May 18, 2026
Connected-product cybersecurity obligations were missing from release governance	Fieldbus and digital-control decisions can ship without aligned cybersecurity gates if teams treat security as post-launch documentation.	Added CRA staged applicability dates and mapped them to release-governance and risk-tradeoff sections.	S28	May 18, 2026
Power-source boundary lacked an actionable standard path	Not naming a battery baseline makes the "separate stream" recommendation difficult to execute during early RFQ planning.	Added IEC 62619 industrial battery baseline (including AGV motive-application scope) to convert boundary warning into a concrete next step.	S1, S31	May 18, 2026
Battery due-diligence timeline was not aligned to the latest legal amendment	Teams can mis-time supplier evidence gates when internal plans still use the superseded 18 Aug 2025 date.	Added Regulation (EU) 2025/1561 milestones (including 18 Aug 2027 application and 26 Jul 2026 guideline date) to timeline, jurisdiction, and risk decisions.	S32	May 18, 2026
Steering-automation control boundary relied mostly on ISO 3691-4 scope language	The page did not explicitly surface ISO 24134 automated-function control scope and lifecycle-revision status.	Added ISO 24134 scope/lifecycle evidence and mapped it as a steering/travel control boundary for long-cycle programs.	S33	May 18, 2026
Functional-safety section emphasized ISO 13849-1 but underplayed validation-lifecycle movement	Teams can freeze safety templates too early if design guidance is cited without tracking the validation-document lifecycle.	Added ISO/DIS 13849-2 lifecycle reference and updated method/standards sections to require version-controlled validation artifacts.	S34	May 18, 2026
Cybersecurity section focused on legal timelines more than technical execution controls	Date-only compliance planning can miss architecture hardening and long-life patch/governance controls in OT systems.	Added NIST SP 800-82r3 and IEC 62443-2-1:2024 as implementation-level control baselines linked to risk and next-action guidance.	S35, S36	May 18, 2026
Architecture torque bands could be misread as normative cross-vendor benchmarks	Public cross-vendor torque benchmark datasets remain limited, so numeric bands need explicit non-normative framing.	Marked comparison torque bands as planning heuristics and linked readers to the evidence-gap row for benchmark limitations.	Pending confirmation / no reliable public source	May 18, 2026
North America section under-specified codified-vs-consensus standard status	Readers could assume new ANSI editions automatically replace codified OSHA references, creating legal-readiness risk in contract and acceptance planning.	Added explicit OSHA codified baseline reference plus proposed-rule status mapping, and converted the mismatch into a named governance gate in timeline/jurisdiction/method sections.	S37, S38, S19, S20, S21	May 18, 2026
Drive safety narrative leaned on functional safety more than electrical/EMC applicability	Teams can over-trust STO/PL claims while electrical hazard and EMC scope constraints remain unverified for the actual product class.	Added IEC 61800-5-1 and IEC 61800-3 boundaries (including traction exclusion and radio-scope notes) into method, lifecycle, risk, and FAQ sections.	S7, S39, S40	May 18, 2026
Battery stream lacked shipment-evidence execution criteria	Without explicit UN 38.3 test-summary gating, supplier onboarding can pass early reviews and fail near shipment/service release.	Added 49 CFR 173.185(a)(3) test-summary availability gate to timeline, method, risk, and evidence-gap rows with RFQ-ready actions.	S41	May 18, 2026
Powertrain-path recommendation was too vehicle-centric and underweighted facility execution constraints	Battery vs hybrid vs fuel-cell decisions can look valid in torque sizing while failing later on charging-area controls, hydrogen installation layout, or out-of-scope truck/fueling assumptions.	Added pathway-boundary matrix, method-level energy-path facility gate, and jurisdiction updates that make battery charging controls, hydrogen installation constraints, and fuel-cell scope exclusions explicit.	S42, S43, S44, S45, S47	May 18, 2026
Fuel-cell ownership-cost narrative lacked scenario and time boundaries	Generic cost-saving language can be over-applied to single-shift or small-fleet contexts when the public benchmark is historical and deployment-specific.	Anchored cost discussion to dated NREL 2013 benchmark deltas (Class I/II and Class III) and added explicit non-universal framing plus evidence-gap follow-up for newer public datasets.	S48	May 18, 2026
Hydrogen fueling baseline was treated as static citation instead of lifecycle-managed requirement	Long-cycle programs can lock outdated assumptions if ISO 19880-1 updates are not tracked through lifecycle-state changes.	Added ISO 19880-1 -> ISO/AWI 19880-1 lifecycle checkpoints to key numbers, timeline, and method gates with explicit revalidation triggers.	S45, S46	May 18, 2026
Later corrigenda visibility is limited in this round	Public access and language availability can hide incremental legal-text changes not reflected in engineering templates.	Marked this as a governance risk with explicit "pending confirmation" action in the evidence ledger.	Pending confirmation / no reliable public source	May 18, 2026
Battery-electric pathway lacked quantified grid-emission variability	Without explicit regional spread, teams can overclaim universal carbon improvements and skip site-specific validation.	Added eGRID 2023 U.S. and subregion emission-rate boundaries into key numbers, tradeoff logic, and evidence-gap actions.	S49	May 18, 2026
Battery-electric operating-cost discussion lacked current public tariff baseline	Using one legacy kWh assumption hides cost volatility and can mis-rank battery vs hybrid vs fuel-cell pathways.	Added latest annual U.S. industrial electricity values from EIA Table 5.3 and mapped them to scenario-based TCO guidance.	S50	May 18, 2026
Fuel-cell pathway maturity and supply-risk context was under-scoped	Historic TCO evidence alone does not show current deployment maturity and global hydrogen supply uncertainty.	Added DOE deployment-scale program-record baseline plus IEA 2025 demand/low-emissions/project-pipeline signals to balance upside and risk framing.	S51, S52	May 18, 2026

Standards lifecycle and revalidation triggers

Standard / baseline	Current state	Why it matters	Action trigger	Evidence
ISO 3691-4:2023 (current baseline)	Published edition 2 (2023-06), stage 90.92 to be revised; replacement ISO/DIS 3691-4 listing now explicitly shows 40.00/40.20 lifecycle states.	Projects with long commissioning windows can drift if they assume scope language stays static through procurement and validation.	If release gates run beyond current enquiry-stage milestones, run a standards-delta review before final supplier lock and hazard-file freeze.	S1, S23
ISO 12100:2010 (risk methodology baseline)	Current baseline remains in use; ISO/DIS 12100.3 is at 40.99, approved for FDIS registration (checked 2026-10-10).	Risk-template wording can change at publication, affecting how hazard files and acceptance arguments are structured.	Record revision/date in every risk artifact and schedule revalidation at each lifecycle transition, not only at final publication.	S14, S24
ISO 24134:2006 (automated truck functions)	ISO listing shows the standard as current and confirmed in 2021, while lifecycle state is 90.92 (to be revised) and ISO/CD 24134 is listed as the replacement track.	Steering/travel/lifting automated-function controls are directly relevant to steer-drive architectures, so lifecycle drift can affect control-safety assumptions.	If platform release extends beyond current baseline gates, run an automated-function control review and map impacts from ISO/CD 24134 progress.	S33
ISO/DIS 13849-2 (validation layer for SRP/CS)	Current ISO listing shows DIS stage 40.99, approved for FDIS registration (checked 2026-10-10).	Projects using ISO 13849-1 principles need validation artifacts that stay aligned with evolving Part 2 guidance.	Treat safety-validation templates as controlled documents and recheck them whenever DIS lifecycle states move before final certification planning.	S34
IEC 61800-5-1:2022 (drive electrical, thermal and energy safety)	Edition 3.0 is published with stability date 2026 and listed corrigenda updates; scope explicitly excludes traction applications and electric vehicles.	Functional-safety references do not automatically close electrical hazard or thermal/fire risk claims for drive hardware.	For each platform release, verify product classification and ensure electrical-safety evidence is mapped separately from functional-safety claims.	S39, S7
IEC 61800-3:2022 (drive EMC requirements and test methods)	Edition 4.0 is published with stability date 2027 and corrigendum update; scope excludes traction/electric-vehicle applications and states radio transmission/reception requirements are not specified.	Drive communication reliability can fail if EMC obligations are treated as implicit or if excluded product classes are not identified early.	Before supplier lock, confirm EMC applicability path and add separate radio-compliance requirements where wireless interfaces are present.	S40
U.S. powered industrial truck legal baseline (codified CFR vs proposed update)	eCFR 29 CFR 1910.178 currently references ANSI B56.1-1969; OSHA update to newer ANSI editions is published as a proposed rule in 2022.	North America programs can fail legal-readiness checks if project templates assume proposed consensus updates are already codified.	Maintain an explicit legal-status checkpoint before declarations, contracts, and customer acceptance sign-off.	S37, S38
UN 38.3 test-summary requirement in U.S. transport path (49 CFR 173.185)	Current eCFR text requires test-summary availability for cells/batteries manufactured on or after 2008-01-01, with defined exception language for qualifying button cells.	Missing battery shipment evidence can block service and replacement logistics even when mechanical and control design is complete.	Gate supplier approval on test-summary artifacts and verify transport-readiness evidence before release and spare-parts shipment.	S41
Cyber Resilience Act (EU 2024/2847) for connected products	Staged applicability points are already defined (2026 and 2027 milestones).	Network-connected steering-drive/control products can fail launch governance if cybersecurity evidence starts after integration freeze.	Attach CRA milestone checkpoints to architecture freeze, SBOM/vulnerability workflow setup, and pre-release declaration readiness.	S28
Battery due-diligence obligations (Reg. (EU) 2023/1542 as amended)	Regulation (EU) 2025/1561 replaces the original due-diligence date with 18 Aug 2027 and updates the guideline milestone.	Supplier-approval and sourcing-governance calendars can fail if they still assume superseded dates.	Re-baseline legal gates and supplier evidence requests on the amended schedule before RFQ and declaration milestones.	S32
OT cybersecurity control baselines (NIST SP 800-82r3 + IEC 62443-2-1:2024)	NIST SP 800-82r3 is final (2023) with identified potential updates, and IEC 62443-2-1 edition 2.0 is published (2024) with long-life IACS assumptions.	Connected steering-drive/control products need operational control programs, not just legal-date tracking.	Require supplier and internal evidence for OT hardening, vulnerability handling, and patch governance before productization lock.	S35, S36
Regulation (EU) 2023/1230 date governance	Primary text and corrigendum must be read together; project templates often mix date sets from different copies.	Calendar misalignment can break conformity-readiness sequencing even when engineering work is otherwise complete.	Freeze one CELEX reference set in governance docs and require legal-document control checks at each major gate.	S3, S13, S22

Evidence conflict ledger (source-locked)

Topic	Signal A	Signal B / counterexample	Decision impact	Execution rule	Evidence
Machinery-regulation transition dates in legacy templates	Corrigendum CELEX 32023R1230R(01) provides corrected 20th-based milestone set (including 20 Oct 2026 and 20 Jan 2027).	Older internal copies can still carry pre-corrigendum 13th/14th-based wording.	Teams may pass internal engineering checks while failing external legal-readiness dates.	Do not accept date values unless they are traced to the corrected CELEX/corrigendum reference set used in project governance.	S13, S22
North America standard package: codified OSHA reference vs newer ANSI editions	Current eCFR 29 CFR 1910.178(a)(2) references ANSI B56.1-1969 as codified text.	OSHA published a 2022 proposed rule to update references to newer ANSI editions (including B56.1-2020, B56.5-2019, and B56.6-2021).	Program teams can mis-sequence declarations, contracts, or acceptance evidence if proposed consensus updates are treated as already codified.	Use a two-layer baseline: codified CFR requirement + explicit legal-status check for proposed/future updates before final compliance claims.	S37, S38
CANopen FD data-phase speed interpretation	CiA CANopen FD overview highlights common current implementation ranges (typically 2 or 5 Mbit/s, future-ready to 10 Mbit/s).	CiA CAN Newsletter example shows up to 8 Mbit/s possible with optimized topology and SIC transceiver.	Without boundary context, teams can under-spec or over-promise communication performance in RFQs.	Treat speed claims as topology- and ecosystem-dependent; require controller + transceiver + toolchain evidence before architecture lock.	S17, S27
Explosive-atmosphere requirement inheritance	ISO 3691-4 scope exclusions are often interpreted as "just avoid this use case" at concept stage.	ATEX legal scope and harmonised-standards publication path define explicit compliance obligations once explosive-atmosphere use is in scope.	Skipping the handoff can surface as late conformity failure after architecture and supplier commitments are already frozen.	When hazardous-location operation is possible, switch to an ATEX requirement matrix immediately and track harmonised-standard version applicability per release.	S1, S29, S30
Connected-product feature velocity vs cybersecurity governance	Fieldbus and remote-diagnostics integration is often treated as a pure performance and interoperability topic.	CRA introduces staged obligations for products with digital elements, including industrial control systems and remote data-processing contexts.	Security obligations can miss release windows if they are not planned alongside control and diagnostics architecture.	Bind cybersecurity evidence checkpoints to the same release gates used for control-loop validation and supplier lock.	S28
Battery due-diligence project calendars (legacy vs amended legal dates)	Regulation (EU) 2025/1561 explicitly replaces the due-diligence application date with 18 Aug 2027 and updates the guideline milestone.	Existing internal plans may still be pinned to the superseded 18 Aug 2025 date.	Date drift can mis-sequence supplier qualification and legal-readiness deliverables.	Reject battery compliance schedules that are not traceable to the amended legal text and re-baseline supplier gates accordingly.	S32
Safety architecture design confidence vs validation-document lifecycle	Teams often freeze safety templates using only ISO 13849-1 references after early design decisions.	ISO listing shows ISO/DIS 13849-2 lifecycle movement, indicating active validation-guidance evolution.	Untracked lifecycle movement can leave safety validation artifacts stale near certification gates.	Lock safety-validation templates to a versioned baseline and require lifecycle-state checks at each major gate.	S6, S34
Cybersecurity legal milestones vs implementation-level OT controls	CRA dates provide legal timing gates for products with digital elements.	OT control frameworks stress concrete lifecycle controls, including long-asset-life governance and operational countermeasures.	Legal-date compliance alone does not guarantee secure deployment in long-lived industrial systems.	Map legal milestones to OT control evidence (architecture, patch, vulnerability workflows) before release approval.	S28, S35, S36
Fuel-cell cost upside narrative vs current hydrogen scale uncertainty	NREL 2013 reports bounded multi-shift TCO advantages for fuel-cell material-handling fleets, and DOE deployment records show industrial rollout maturity.	IEA 2025 reports low-emissions hydrogen remains under 1% of global hydrogen use and announced 2030 project potential has been revised down.	Teams can overcommit to fuel-cell pathways if they treat historical fleet economics as guaranteed in current fuel-supply and project-execution conditions.	Use site-specific hydrogen availability and price scenarios, and keep a fallback battery/hybrid path until local supply and station-readiness evidence is confirmed.	S48, S51, S52

Evidence register

Ref	Source	Date context	Usage in page
S1	ISO 3691-4:2023 Industrial trucks — Safety requirements and verification — Part 4: Driverless industrial trucks and their systems	Edition 2 published 2023-06 \| lifecycle stage 90.92 (to be revised) \| accessed May 18, 2026	Defines AMR/AGV safety scope, exclusions (for example public-road and explosive-atmosphere operation), and indicates the current edition is under revision.
S2	EUR-Lex summary: Regulation (EU) 2023/1230 on machinery	EUR-Lex summary last updated 2025-06-12 \| legal dates rechecked against the consolidated text on 2026-10-10	Provides staged applicability dates and transition context used in procurement and compliance planning.
S3	Official Journal text: Regulation (EU) 2023/1230	Published 2023-06-29 (OJ L 165) \| accessed May 18, 2026	Primary legal text for machinery conformity obligations and transition governance.
S4	IEC 60529:1989 Degrees of protection provided by enclosures (IP Code)	Publication date 1989-11-30 \| accessed May 18, 2026	Reference for IP code framework used by the enclosure selection ladder in this tool.
S5	ISO 20653:2023 Road vehicles — Degrees of protection (IP code)	Edition 3 published 2023-08 \| accessed May 18, 2026	Clarifies IP coding in road-vehicle context and supports boundary notes around IP69K terminology usage.
S6	ISO 13849-1:2023 Safety of machinery — Safety-related parts of control systems — Part 1	Edition 4 published 2023-04 \| accessed May 18, 2026	Used for functional-safety boundary: the standard defines principles, but does not set project-specific required performance levels.
S7	IEC 61800-5-2:2016 Adjustable speed electrical power drive systems — Functional safety requirements	Publication date 2016-04-18 \| edition 2.0 \| stability date 2026 \| accessed May 18, 2026	Supports safety-architecture references (e.g., drive safety functions) and boundary warnings around project validation; current listing indicates ongoing maintenance status.
S8	ISO 13850:2015 Safety of machinery — Emergency stop function	Edition 3 published 2015-11 \| review confirmed 2020 \| accessed May 18, 2026	Used for boundary reminder that emergency stop does not cover every protective function (for example, reversal or motion limitation).
S9	PROFINET Design Guideline V1.59 (PNO)	Version 1.59 released 2025-01 \| accessed May 18, 2026	Provides PROFINET timing references (base clock 31.25 us, update-time bands, and CC-A/B/C/D class boundaries) for bus-fit decisions.
S10	CiA CANopen overview	CiA knowledge page \| accessed May 18, 2026	Provides CANopen data-rate range (10 kbit/s to 1000 kbit/s) used for communication-boundary notes.
S11	CiA CAN HS transmission fundamentals	CiA knowledge page \| accessed May 18, 2026	Provides high-speed CAN line-length relationship (e.g., 1 Mbit/s theoretical 40 m before practical margins).
S12	Beckhoff EtherCAT system documentation (EtherCAT master in TwinCAT)	Documentation page \| accessed May 18, 2026	Used for EtherCAT practical cycle-time and 100 Mbit/s physical-layer context in high-dynamic motion loops.
S13	EUR-Lex corrigendum (CELEX 32023R1230R(01))	Published 2023-07-04 (OJ L 169) \| accessed May 18, 2026	Corrects key applicability dates in the machinery regulation text (including 20 Jan 2027 full-application wording, 20 Oct 2026 article gate, and multiple 20th-date replacements).
S14	ISO 12100:2010 Safety of machinery — General principles for design — Risk assessment and risk reduction	Review confirmed 2022 \| ISO listing checked 2026-10-10: replacement draft is ISO/DIS 12100.3, stage 40.99	Used to mark risk-assessment governance boundaries: keep hazard files version-controlled and revalidated when the standard revision baseline changes.
S15	IEC 60204-1:2016+AMD1:2021 CSV Safety of machinery — Electrical equipment of machines — Part 1: General requirements	Consolidated version includes Amendment 1:2021 \| scope states application starts at the point of connection to the electrical supply \| accessed May 18, 2026	Adds electrical-equipment scope and stop-function boundaries (including references to STO/SS1 in Clause 9 context) for safety architecture interpretation.
S16	CiA CANopen lower layers	CiA knowledge page \| accessed May 18, 2026	Provides CANopen CC bit-timing boundaries (for example 1 Mbit/s with approximately 25 m bus length plus 1.5 m max stub and 7.5 m total stub guidance).
S17	CiA CANopen FD: The art of embedded networking	CiA knowledge page \| accessed May 18, 2026	Used for migration boundary notes: CANopen FD data phase supports up to 5 Mbit/s today (future-ready to 10 Mbit/s), but deployment still depends on ecosystem and controller support.
S18	Beckhoff EtherCAT: cable lengths between two EtherCAT participants	Documentation page lists 100 m Ethernet segment decomposition (5 m + 90 m + 5 m) \| accessed May 18, 2026	Adds physical-layer planning boundary for large AMR layouts: timing is not the only bus constraint; segment distance and topology matter.
S19	ANSI/ITSDF B56.5-2024 Safety Standard for Driverless, Automatic Guided Industrial Vehicles and Automated Functions of Manned Industrial Vehicles	Most recent standard listing notes revision from 2019 edition to 2024 edition \| accessed May 18, 2026	Used for North America deployment boundary notes and dual-region evidence planning alongside ISO/EU tracks.
S20	ANSI/A3 R15.08-2-2023 Industrial Mobile Robots — Safety requirements — Part 2: Requirements for IMR systems and applications	2023 edition listing references IMR Types A/B/C system/application framework \| accessed May 18, 2026	Supports jurisdiction-specific requirements mapping for IMR system/application integration in North America programs.
S21	ANSI/RIA R15.08-1-2020 Industrial Mobile Robots — Safety requirements — Part 1	ANSI approved 2020-04-03 \| listing links Part 1 hazard framework with Part 2 and B56.5 package mapping \| accessed May 18, 2026	Used to explain why IMR safety planning in North America is typically a multi-standard package, not a single-document substitution.
S22	Current consolidated Regulation (EU) 2023/1230 text (27 July 2026)	Consolidated text dated 2026-07-27; checked 2026-10-10	Current consolidated legal-reference checkpoint, including the 2024/2748 and 2026/1744 amendments and the corrected application dates; lock this version in date governance to avoid mixed-template drift.
S23	ISO/DIS 3691-4 Industrial trucks — Safety requirements and verification — Part 4	DIS registered 2026-04-08 \| 40.20 ballot initiated 2026-06-17 \| checked 2026-10-10	Shows successor-draft lifecycle detail for ISO 3691-4 so long-cycle AMR programs can set explicit revalidation triggers instead of treating the baseline as static.
S24	ISO/DIS 12100.3 Safety of machinery — Risk assessment and risk reduction	Second DIS loop closed 2026-09-15; stage 40.99 approved for FDIS registration \| checked 2026-10-10	Converts generic "to be revised" wording into a lifecycle-driven execution trigger for hazard-file and validation-template refresh.
S25	EtherCAT Technology Group: EtherCAT - the Ethernet Fieldbus	ETG technology page \| accessed May 18, 2026	Adds public ETG timing baseline (development focus on <=100 us cycle and <=1 us synchronization jitter) as a high-dynamics comparison anchor.
S26	PI: PROFINET over TSN	Page states PROFINET V2.4 with TSN integration \| accessed May 18, 2026	Clarifies concept boundary: TSN is an extension layer and does not replace PROFINET application services.
S27	CiA CAN Newsletter 1/2020: Scalability of CANopen	Published 2020-03 \| accessed May 18, 2026	Provides counterexample boundaries for CANopen FD data-phase scaling (e.g., up to 8 Mbit/s under optimized topology/SIC transceiver), preventing over-generalized speed claims.
S28	EUR-Lex summary: Cyber Resilience Act (Regulation (EU) 2024/2847)	OJ reference 2024/2847 dated 2024-11-20 \| staged dates checked 2026-10-10: 2026-06-11 and 2026-09-11 are in force; main application is 2027-12-11	Adds product-cybersecurity timeline and scope context for network-connected steering-drive/control products (including industrial control systems).
S29	Directive 2014/34/EU (ATEX) — equipment and protective systems for potentially explosive atmospheres	In force \| current consolidated version dated 2026-05-30; checked 2026-10-10	Used to define the explosive-atmosphere boundary path when ISO 3691-4 scope exclusions are triggered.
S30	Current consolidated Commission Implementing Decision (EU) 2022/1668 (1 October 2026)	Current consolidated list dated 2026-10-01; includes amendments through 2026/1967 \| checked 2026-10-10	Provides the current harmonised-standards list under ATEX. Check applicable entries for the equipment and release date instead of relying on a January 2026 snapshot.
S31	IEC 62619:2022 Safety requirements for secondary lithium cells and batteries in industrial applications	Edition 2.0 published 2022-05-24 \| stability date 2026 \| scope includes motive applications (forklift truck, AGV) \| accessed May 18, 2026	Adds an actionable battery/power-source baseline path because ISO 3691-4 explicitly excludes power-source requirements.
S32	Official Journal text: Regulation (EU) 2025/1561 amending Regulation (EU) 2023/1542 (battery due diligence obligations)	Published 2025-07-30 (OJ L series 2025/1561) \| amended dates checked 2026-10-10: application 2027-08-18; guideline deadline 2026-07-26	Adds timeline correction for battery due-diligence obligations so supply-chain gates are aligned with current legal dates.
S33	ISO 24134:2006 Industrial trucks — Additional requirements for automated functions on trucks	Edition 1 published 2006-01 \| last reviewed and confirmed 2021 \| current lifecycle stage 90.92 (to be revised) with ISO/CD 24134 listed as replacement \| accessed May 18, 2026	Adds steering/travel/lifting automation-control scope boundary and revision-lifecycle context specific to automated truck functions.
S34	ISO/DIS 13849-2 Safety of machinery — Safety-related parts of control systems — Part 2	DIS registered 2025-12-04; ballot started 2026-02-06; close of voting 2026-05-02; stage 40.99 approved for FDIS registration \| checked 2026-10-10	Strengthens the design-vs-validation boundary by mapping current draft lifecycle for SRP/CS validation guidance aligned with ISO 13849-1:2023.
S35	NIST SP 800-82 Rev. 3 — Guide to Operational Technology (OT) Security	Published 2023-09 \| planning note 2024-07-18 identifies potential updates \| accessed May 18, 2026	Adds technical cybersecurity control guidance (threats, vulnerabilities, countermeasures) so CRA timelines are paired with implementation-level OT controls.
S36	IEC 62443-2-1:2024 Security for industrial automation and control systems — Establishing an IACS security program	Edition 2.0 published 2024-08-07 \| stability date 2026 \| IEC page notes IACS lifespan can exceed twenty years and patch availability can be uncertain \| accessed May 18, 2026	Adds lifecycle-security governance baseline for connected steering-drive/control stacks where long asset life and patch uncertainty drive operational risk.
S37	eCFR 29 CFR 1910.178 — Powered industrial trucks (OSHA codified requirement)	eCFR page shows title 29 up to date as of 2026-05-06; paragraph (a)(2) still references ANSI B56.1-1969 \| accessed May 18, 2026	Defines the current codified U.S. baseline for powered industrial-truck design references and highlights legal-status checks needed before assuming newer consensus editions are mandatory.
S38	Federal Register 87 FR 8755 (2022-02-16) — OSHA Powered Industrial Trucks Design Standard Update (Proposed Rule)	Document type is Proposed Rule; published 2022-02-16; comments closed 2022-05-17 \| accessed May 18, 2026	Provides the proposed migration path to ANSI B56.1-2020 / B56.5-2019 / B56.6-2021 and supports explicit “pending final-rule confirmation” governance in North America planning.
S39	IEC 61800-5-1:2022 Adjustable speed electrical power drive systems — Safety requirements (electrical, thermal and energy)	Publication date 2022-08-31 \| edition 3.0 \| stability date 2026 \| corrigenda 1 (2023-09) and 2 (2025-12) included in listed copy \| accessed May 18, 2026	Adds electrical/thermal/fire/energy hazard boundary that is distinct from functional-safety-only claims and flags traction/electric-vehicle exclusions.
S40	IEC 61800-3:2022 Adjustable speed electrical power drive systems — EMC requirements and specific test methods	Publication date 2022-11-30 \| edition 4.0 \| stability date 2027 \| corrigendum 1 (2025-04) included in listed copy \| accessed May 18, 2026	Provides EMC baseline and critical applicability limits: traction/electric-vehicle exclusion and explicit note that radio transmission/reception requirements are not specified by this document.
S41	eCFR 49 CFR 173.185 — Lithium cells and batteries (UN 38.3 test-summary availability requirements)	eCFR page shows title 49 up to date as of 2026-05-06; paragraph (a)(3) requires test-summary availability for cells/batteries manufactured on or after 2008-01-01, with button-cell exception language in force \| accessed May 18, 2026	Converts battery compliance from generic planning into executable RFQ/release gates by anchoring required UN 38.3 test-summary artifacts and data fields.
S42	eCFR 29 CFR 1910.103 — Hydrogen	eCFR page shows title 29 up to date as of 2026-05-14 \| timeline note indicates no changes after 2017-01-03 \| accessed May 18, 2026	Adds U.S. facility-level hydrogen installation constraints (for example location preference order, separation-distance tables, ventilation and explosion-venting requirements) for fuel-cell pathway execution.
S43	OSHA 1910.178 powered industrial trucks page (battery charging and hazardous-location clauses)	OSHA page includes 1910.178(g) battery charging clauses and 1910.178(c) hazardous-location clauses \| accessed May 18, 2026	Provides executable battery-electric and hazardous-location boundaries, including designated charging area, ventilation, ignition-source control, and classification-sensitive truck-type requirements.
S44	OSHA interpretation letter (1976-01-26): definition of “adequate ventilation” in 1910.178(g)(2)	Issued 1976-01-26 \| interpretation states hydrogen concentration should stay below lower explosive limit (4.1%) at charging site \| accessed May 18, 2026	Converts generic ventilation wording into a measurable screening threshold for battery charging and hydrogen-gassing control design.
S45	ISO 19880-1:2020 Gaseous hydrogen — Fuelling stations — Part 1: General requirements	Published 2020 \| ISO lifecycle notes indicate replacement track ISO/AWI 19880-1 \| accessed May 18, 2026	Adds hydrogen fueling-station baseline and key boundary language: minimum requirements are provided, but additional specific requirements can still be needed for safe operation in special applications (including indoor dispensing and fork-lift contexts).
S46	ISO/AWI 19880-1 (Edition 2) lifecycle entry for hydrogen fuelling stations	Lifecycle shows 10.99 and 20.00 milestones dated 2026-01-20 \| stage currently under development \| accessed May 18, 2026	Adds a concrete lifecycle trigger for hydrogen-fueling requirement reviews in long-cycle programs so teams do not freeze 2020 assumptions without re-check points.
S47	IEC 62282-4-101:2022 (ANSI preview) Fuel cell power systems for electrically powered industrial trucks — Safety	Edition 2.0 published 2022-08-11 \| preview scope states <=150 V DC, gaseous hydrogen or methanol fuels, and explicit exclusions (for example explosive atmospheres, hybrid ICE trucks, liquid hydrogen storage, removable fuel containers) \| accessed May 18, 2026	Provides explicit scope boundaries for fuel-cell industrial-truck safety claims so architecture teams can detect out-of-scope variants before supplier lock.
S48	NREL Technical Report NREL/TP-5600-56408 (2013): Total cost of ownership of fuel-cell material handling equipment	Published 2013-04 \| report concludes cost outcomes for multi-shift warehouses from DOE/DOD co-funded deployments \| accessed May 18, 2026	Adds quantified, source-attributed cost tradeoff baselines (for example Class I/II and Class III per-lift annual ownership comparisons) with explicit scenario boundaries.
S49	EPA eGRID 2023 summary data (U.S. and subregion output rates)	Published 2025-01 \| table shows U.S. annual CO2 output emission rate 767.209 lb/MWh and subregion spread from 242.776 to 1548.530 lb/MWh \| accessed May 18, 2026	Adds quantified grid-intensity spread for site-specific battery-electric emissions boundaries and prevents one-factor carbon assumptions.
S50	U.S. EIA Electric Power Monthly Table 5.3 — Average retail price of electricity to ultimate customers	Annual table values list U.S. industrial electricity at 8.13 cents/kWh (2024) and 8.62 cents/kWh (2025) \| accessed May 18, 2026	Adds current U.S. electricity-cost baseline for battery-electric pathway sensitivity checks.
S51	DOE Hydrogen and Fuel Cells Program Record 18002 — Industry Deployed Fuel Cell Powered Lift Trucks	Published 2018-09-28 \| reports cumulative deployment of 21,838 fuel-cell lift trucks and over 140,000 kW by end of 2017 \| accessed May 18, 2026	Adds deployment-scale evidence for fuel-cell material-handling maturity while keeping time-bound limits explicit.
S52	IEA Global Hydrogen Review 2025 — Executive summary	Published 2025-09-30 \| summary states almost 100 Mt hydrogen demand in 2024, low-emissions hydrogen still <1%, and announced 2030 production potential reduced from 49 to 37 Mtpa \| accessed May 18, 2026	Adds current global hydrogen scale and project-attrition signals for fuel-cell pathway schedule and cost-risk framing.

Control Bus Boundaries

Protocol choice changes achievable timing and diagnostics behavior. This table is a boundary screen, not a universal ranking.

Protocol	Timing baseline	Best fit	Boundary notes	Evidence
EtherCAT	ETG technology page states development focus on <=100 us cycle and <=1 us jitter; Beckhoff docs add task cycles from 50 us to >100 ms and 100 m segment decomposition (5 m + 90 m + 5 m)	High-dynamic, tightly synchronized multi-axis motion when deterministic timing is engineered end-to-end	Performance still depends on controller task design, diagnostics load, and physical topology/cabling discipline. For connected products, cybersecurity release obligations should be planned in parallel; EMC and product-class applicability checks should be explicit rather than assumed.	S25, S12, S18, S40, S28, S35, S36
PROFINET	PNO guideline references 31.25 us base clock, timing bands (>10 ms, <5 ms and >250 us, <250 us manufacturer-specific), and CC-A/B/C/D capability boundaries	Industrial interoperability with structured plant-network governance and bounded update-time requirements	Needs explicit load budgeting and topology discipline; TSN extends PROFINET but does not replace PROFINET services (alarms/diagnostics/parameterization). Connected-product cybersecurity obligations remain a separate governance stream, and EMC applicability should be documented as a dedicated acceptance artifact.	S9, S26, S40, S28, S35, S36
CANopen	CiA summary gives 10 to 1000 kbit/s; CANopen lower-layer table adds CC planning boundaries (for example around 25 m at 1 Mbit/s plus short stubs)	Moderate-dynamic machines, retrofit projects, and cost-sensitive distributed control loops	At high dynamics, larger node counts, or longer cable runs, timing margin and diagnostics depth can become bottlenecks.	S10, S16
CANopen FD (migration path)	CiA CANopen FD note indicates common current implementations around 2/5 Mbit/s with future-ready path to 10 Mbit/s; CiA newsletter examples show up to 8 Mbit/s in optimized SIC/topology conditions	Projects that need incremental migration from classic CANopen while preserving distributed CAN topology concepts	Adoption depends on full ecosystem support (controller, drives, tooling, diagnostics); treat as migration program, not drop-in switch.	S17, S27, S28, S35, S36

Bus escalation trigger matrix

Trigger	Keep current path	Escalate path	If ignored	Evidence
Loop target remains >10 ms and interoperability is primary	Use mainstream CC-B/RT-centric architecture with explicit latency budget and controlled diagnostics load.	No forced migration required. Preserve simplicity and focus on commissioning quality.	Unnecessary protocol complexity can increase integration cost without measurable throughput benefit.	S9, S26
Loop target moves into <5 ms or clock-synchronous multi-axis behavior is required	Keep RT/free-running architecture only with strict pilot telemetry and jitter acceptance criteria.	Escalate to IRT/TSN clock-synchronous path or EtherCAT deterministic sync design and validate controller + network + drive as one loop.	Late jitter/slip defects emerge in FAT/SAT, driving rework and delayed ramp.	S9, S25, S26
Classic CANopen at 1 Mbit/s with trunk/stub growth or higher node/update pressure	Remain on classic CANopen only within CiA physical-layer limits and with conservative busload policy.	Evaluate CANopen FD as a managed migration and verify full ecosystem readiness (controller + transceiver + diagnostics tooling).	Intermittent latency spikes and control-quality degradation appear during scale-up.	S16, S17, S27
Wireless diagnostics/remote-control features or high-EMI zones are added late in architecture	Proceed only if EMC test scope, product classification, and radio-compliance ownership are already defined in release criteria.	Escalate to a dedicated EMC + radio requirement stream and verify whether additional standards apply beyond generic drive EMC references.	Late EMC/radio nonconformities can invalidate timing assumptions and block release despite passing early motion tests.	S39, S40
Connected product has remote diagnostics/update features and EU market access target	Proceed only if cybersecurity ownership, SBOM process, and vulnerability-handling workflow are already mapped to release gates.	Escalate to explicit CRA readiness workstream (architecture + process + documentation) before productization lock.	Integration may pass performance tests but fail late release/compliance governance.	S28, S35, S36
Connected OT stack has long service life with unclear patch and vulnerability-response ownership	Proceed only if supplier and internal teams can show operational controls (asset inventory, vulnerability intake, and patch governance) before pilot scale-up.	Escalate to explicit OT security-program gates using NIST SP 800-82r3 and IEC 62443-2-1:2024 as baseline references.	Cybersecurity gaps surface late in service operations, forcing expensive remediation after deployment.	S35, S36

Battery vs Hybrid vs Fuel-Cell Pathway Boundaries

This matrix converts pathway labels into execution constraints, so teams do not treat energy-path choice as a torque-only decision.

Pathway	Operational upside	Execution boundary	Escalation trigger	Evidence
Battery-electric powertrain	Simple energy supply chain where grid charging is available and hydrogen infrastructure is not planned.	Charging operations are a safety-controlled process, not a generic utility task: designated charging zones, ventilation, electrolyte handling, and ignition-source controls are explicit requirements. Carbon and operating-cost assumptions also need site-level checks because grid intensity and industrial tariffs vary materially by location and year.	Escalate when multi-shift battery-change labor, charging-area space, ventilation controls, or site-level grid/tariff assumptions turn the baseline TCO or emissions case unstable.	S43, S44, S48, S49, S50
Hybrid-electric / range-extended powertrain	Can bridge duty-cycle and downtime pressure when pure battery operation cannot hold runtime targets.	Fuel-handling and hazardous-location controls from powered-industrial-truck rules still apply, and architecture claims must retain layered safety validation rather than single-standard shortcuts.	Escalate when deployment includes classified atmospheres, mixed fuel handling, or unresolved safety-architecture ownership across teams.	S43, S6, S7, S39, S40
Fuel-cell electric powertrain	Public deployment data indicates potential ownership-cost benefits in larger, multi-shift warehouse operations with high battery-change burden, and historical deployment scale shows the pathway is already used in industry.	Hydrogen pathway adds site-level installation constraints and fueling-standard scope limits; some truck/application variants are explicitly outside reference-scope envelopes and require additional controls. Current global low-emissions hydrogen supply remains constrained, so local fuel availability and pricing should be treated as explicit gate criteria.	Escalate when design assumptions include explosive atmospheres, removable fuel containers, hybrid ICE variants, fueling-station models not covered by current baseline assumptions, or unproven local hydrogen supply/cost readiness.	S42, S45, S46, S47, S48, S51, S52

Alternative Powertrain Architecture Comparison

Compare Alternative powertrain options by torque band, integration cost, and failure boundary before committing to supplier RFQs.

Option	Best fit scenario	Typical torque band	Integration cost	Boundary notes	Evidence
Compact integrated Alternative powertrain	Indoor AMR <=1.5 t, moderate duty, controlled thermal profile	Planning heuristic band (non-normative): 40-90 Nm peak per drive wheel	Lower integration effort, faster commissioning	Can become thermally constrained when duty and ambient are both high; verify against OEM derating curves before lock-in. Torque-band values are screening heuristics, not cross-vendor guarantees.	S1, S7
Steer-drive unit module	Tight aisle maneuvering with frequent orientation changes	Planning heuristic band (non-normative): 70-160 Nm peak per drive wheel	Medium (mechanical alignment + controls tuning)	Control quality depends strongly on steering feedback quality and timing consistency across the motion stack. Treat torque bands as initial filters until validated with OEM curves.	S1, S6, S9
Sealed heavy-payload unit	Dusty/washdown layouts and payload cycles with high traction demand	Planning heuristic band (non-normative): 140-280 Nm peak per drive wheel	Medium-high (cooling, enclosure, service planning)	IP requirement interpretation must match the real environment standard context; overspecification can increase thermal and service burden. Confirm torque capability using supplier thermal derating data.	S4, S5
Split motor + gearbox + controller stack	Custom platforms with non-standard geometry or compliance constraints	Custom, often >220 Nm peak	High engineering effort, high flexibility	Longer validation and configuration-management cycle; typically justified only when standard modules cannot satisfy duty, safety or environment boundaries.	S2, S3, S6, S7

Decision tradeoff table (risk-focused)

Decision dimension	Fast path	Conservative path	Failure mode if wrong	Evidence
Fast commissioning vs thermal margin	Choose compact integrated units for faster mechanical/electrical integration and lower upfront engineering load.	Choose heavy-payload or split architecture when duty, ambient, and ingress jointly pressure continuous torque.	Thermal derating can collapse usable torque in production duty, forcing late redesign and supplier requalification.	S1, S7
Interoperability vs ultra-fast motion timing	Keep mainstream plant interoperability priorities and use RT/TSN free-running where time demand is moderate.	Budget IRT/TSN clock-synchronous or vendor-specific architecture when loop timing sits in sub-5 ms or sub-250 us zones.	Network and controller jitter becomes the hidden root cause of slip, oscillation, and throughput instability.	S9, S12
Lower bus complexity vs CANopen scalability	Retain existing CANopen stack for moderate dynamics and limited node/update-rate pressure.	Escalate to tighter timing architecture or CANopen FD migration if high dynamics, larger node counts, or long cable runs erode timing margin.	Generic bitrate assumptions mask CANopen-specific bus/stub limits, causing intermittent control-quality failures during scale-up.	S10, S16, S17
Accelerated go-to-market vs legal date certainty	Plan against a single full-application date only and postpone staged-milestone integration.	Map corrected staged dates (including 20 Oct 2026 and 20 Jan 2027 gates) into design freeze, conformity assessment, and declaration workflows from project start.	Programs can pass internal engineering gates but miss external conformity readiness windows near launch.	S3, S13, S22
Single-region compliance pack vs cross-region rollout	Use one regional standards baseline to reduce upfront documentation effort.	Build a dual-track evidence matrix early when deployments may span EU and North America.	Late customer acceptance failures force redesign of validation plans and delay launch windows.	S1, S3, S13, S19, S20, S21
Treating functional-safety language as complete drive compliance vs layered safety evidence	Use STO/PL references as the primary compliance narrative and defer electrical/EMC detail to late verification.	Maintain layered evidence from day one: functional safety + electrical/thermal safety + EMC applicability and classification checks.	Programs pass concept reviews but fail late test/certification gates when electrical or EMC boundaries are challenged.	S7, S39, S40
Fast network feature rollout vs cybersecurity release readiness	Prioritize telemetry and remote-service features first, then add cybersecurity documentation near launch.	Plan connected-product cybersecurity obligations as first-class release gates with architecture, SBOM, and vulnerability-process ownership defined early.	Late security-governance gaps can block market access or force emergency redesign near production release.	S28, S35, S36
General AMR baseline reuse vs hazardous-location deployment readiness	Reuse non-ATEX architecture and documentation assumptions across all sites to reduce early engineering effort.	Trigger an ATEX-specific requirement stream as soon as potentially explosive-atmosphere use is plausible.	Hazardous-location compliance failures appear after supplier and platform decisions are already costly to reverse.	S29, S30
Faster battery supplier onboarding vs due-diligence readiness	Prioritize commercial onboarding speed and postpone full raw-material traceability/evidence collection.	Treat due-diligence evidence as part of early supplier qualification and align gates with amended legal dates.	Late compliance-package gaps can block release or force urgent supplier requalification near launch.	S32
Date-only cybersecurity compliance vs technical OT control execution	Track legal milestones and assume product teams can retrofit operational controls later.	Pair legal milestones with OT security-program evidence (hardening, patch/vulnerability workflows, and long-life asset governance).	Release passes timeline checks but fails operational security readiness in commissioning and service phases.	S28, S35, S36
Rapid battery supplier onboarding vs transport-evidence readiness	Advance sourcing and deployment planning before verifying UN 38.3 test-summary artifact availability.	Gate RFQ and supplier qualification on transport-evidence completeness, including test-summary availability checks.	Spare-part and service logistics stall near launch because compliant battery shipment evidence is missing.	S41
Single-factor battery-electric claims vs location-specific energy reality	Assume one grid emission factor and one electricity tariff across all sites to speed TCO and sustainability messaging.	Use site-specific grid-emission and tariff scenarios before architecture freeze, and keep battery/fuel-cell/hybrid ranking conditional on those inputs.	Pathway ranking flips late when real site electricity carbon and tariff values diverge from planning assumptions.	S49, S50, S52

Cost-risk tradeoff visual

Alias coverage guard

The alias keywords alternative powertrains, hybrid-electric powertrain, fuel-cell electric powertrain, battery-electric powertrain, biofuel-compatible powertrain, and range-extended powertrain are intentionally served on the same canonical URL to avoid split ranking signals and duplicate decision content.

Canonical anchor (alternative powertrains):/learn/alternative-powertrains#alias-alternative-powertrains

Canonical anchor (hybrid-electric powertrain):/learn/alternative-powertrains#alias-hybrid-electric-powertrain

Canonical anchor (fuel-cell electric powertrain):/learn/alternative-powertrains#alias-fuel-cell-electric-powertrain

Existing alias anchor (still supported):/learn/alternative-powertrains#alias-battery-electric-powertrain

Existing alias anchor:/learn/alternative-powertrains#alias-biofuel-compatible-powertrain

Legacy anchor kept for existing links:#alias-range-extended-powertrain

This preserves one URL where tool output and report evidence stay synchronized for engineering and procurement teams.

Risks, Boundaries, and Scenarios

These blocks convert uncertainty into concrete mitigation steps so teams can continue execution without hiding evidence gaps.

Risk matrix visual

Risk table

Risk	Impact	Likelihood	Mitigation
Undersized peak torque in ramp transitions	High	Medium	Add peak-torque reserve, validate accel profile on loaded ramps, and log wheel-slip events before release.
Ingress level selected without washdown reality check	Medium	Medium	Map cleaning SOP and contaminant profile first, then pick IP tier and seal strategy to avoid over/under specification.
Using ISO 3691-4 in out-of-scope environments	High	Low	If operation touches public roads or explosive atmospheres, run a dedicated standards applicability review before reusing this baseline and switch to ATEX mapping where required.
Assuming ISO 3691-4 covers power-source design requirements	High	Medium	Treat traction battery/power-source requirements as a separate standards stream; do not infer coverage from ISO 3691-4 scope alone.
Duty-cycle thermal drift reduces usable torque	High	High	Track winding or housing temperature trend, lower continuous limit, and schedule cooling or derating guardrails.
Assuming emergency stop or STO equals full braking/isolation behavior	High	Medium	Separate stop-category design, braking strategy, and electrical-isolation strategy in the safety concept rather than collapsing them into one claim.
Communication timing budget not validated for selected bus	High	Medium	Measure real cycle-time/jitter under expected network load, and check bus-length/stub assumptions against selected protocol design guides before supplier lock.
Using pre-corrigendum machinery-regulation dates in project gates	High	Medium	Use corrigendum-aligned milestones (including 20 Oct 2026 and 20 Jan 2027 gates), freeze one CELEX reference set, and recheck template dates before release.
Treating standard references as permanently stable	Medium	Medium	Track lifecycle state (for example DIS progression and publication triggers) and schedule formal risk-file refresh before long-term framework agreements.
Cross-region acceptance planned with single-region standards package	High	Medium	Create an evidence matrix that maps EU and North America standards from project start; validate each release gate against region-specific requirements.
North America compliance pack assumes proposed ANSI updates are already codified	High	Medium	Use a legal-status checkpoint that separates current codified OSHA references from proposed update paths before declaration, contract, and acceptance sign-off.
No functional safety path in architecture baseline	High	Medium	Define safety architecture early (STO/SLS and diagnostic coverage) and freeze verification plan before pilot rollout.
Connected steering-drive/control product reaches release gate without cybersecurity evidence plan	High	Medium	Map CRA staged obligations into release governance early (design controls, vulnerability process, and documentation ownership).
Hazardous-location projects reuse non-ATEX assumptions from general AMR templates	High	Medium	Create an ATEX-specific requirement matrix and verify harmonised-standard applicability before supplier lock.
Battery/power-source requirements remain implicit in steering-drive sizing	High	Medium	Track battery safety as a dedicated stream (for example IEC 62619 baseline for industrial motive use) in parallel with traction sizing.
Battery due-diligence planning still uses superseded 2025 legal date	High	Medium	Re-baseline battery supply-chain compliance gates on Regulation (EU) 2025/1561 dates and verify supplier evidence timing before RFQ lock.
Battery supplier lacks UN 38.3 test-summary artifacts at shipment gate	High	Medium	Add test-summary availability checks to RFQ and supplier approval criteria, and block release if required artifacts are missing for applicable battery builds.
Safety-validation artifacts remain static while ISO 13849-2 lifecycle moves	Medium	Medium	Version-control safety-validation templates and perform lifecycle checks before certification and customer acceptance gates.
Connected OT controls rely on legal timeline tracking without technical control evidence	High	Medium	Use OT control baselines (for example NIST SP 800-82r3 and IEC 62443-2-1) to define measurable hardening, patch, and vulnerability workflows.
Drive compliance claim omits electrical-hazard and EMC applicability boundaries	High	Medium	Run layered verification (functional safety + electrical/thermal safety + EMC applicability), and confirm traction/radio boundary handling before final release claims.
Alias query interpreted as component lookup only	Medium	Low	Keep canonical URL with alias anchor and explicit FAQ so procurement and engineering teams land on same decision workflow.
Battery-electric decision assumes one fixed grid-carbon and tariff baseline	High	Medium	Run site-level electricity carbon and tariff scenarios before RFQ lock, then recheck pathway ranking with updated values.

Known/unknown evidence ledger

Topic	Known	Unknown	Current treatment	Next step	Status
Wheel-floor coefficient for your exact tire compound	The force model is physically valid and directionally useful.	Exact coefficient under your contamination and wear state.	Uses conservative floor-based defaults and elevated reserve.	Capture measured traction/drag during pilot runs and recalibrate c.	monitor
Thermal derating curve of selected Alternative powertrain	Duty and ambient thermal stress clearly affect output.	Vendor-specific torque-vs-temperature curve in your enclosure.	Applies reserve-factor heuristic and boundary alerts.	Request OEM thermal map and validate with loaded endurance run.	pending
Cross-vendor reserve-factor benchmark	Reserve factor strongly changes pass/fail decisions in early sizing.	No reliable public, cross-vendor dataset was found for a universal reserve percentage by AMR duty class.	Keeps reserve as explicit internal policy (15%-40%) and avoids presenting it as a normative threshold.	Build internal benchmark from pilot fleets and normalize by duty, temperature and ingress profile.	pending
Field failure rate by IP class in AMR duty	Ingress classes exist and are test-based.	Publicly comparable lifecycle failure rates by IP class for AMR Alternative powertrains remain limited.	Treats ingress choice as a risk tradeoff, not as a direct reliability guarantee.	Collect supplier RMA + fleet telemetry by environment profile before setting default IP policy.	pending
CANopen FD interoperability evidence in multi-vendor AMR fleets	CiA positions CANopen FD with higher data-phase capability than classic CANopen.	Public, cross-vendor AMR benchmarks for CANopen FD conformance, diagnostics tooling maturity, and long-run maintenance burden remain limited.	Treats CANopen FD as a migration option with explicit ecosystem-support checks, not as an automatic drop-in upgrade.	Run vendor matrix verification (controller + drive + diagnostics toolchain) before committing CANopen FD architecture at scale.	pending
Safety-function target level (PL/SIL)	ISO 13849-1 and IEC 61800-5-2 define principles/functions relevant to the architecture, and ISO/DIS 13849-2 is active on the validation side.	Project-specific claim after architecture and diagnostics are frozen.	Flags missing safety path as high-risk.	Run functional-safety concept review and version-lock validation artifacts before procurement lock.	pending
Regulatory transition timing	Primary timeline and first corrigendum date replacements are publicly available.	Whether your project templates and legal workflow are consistently locked to the same CELEX/corrigendum reference set.	Uses corrigendum-backed milestones and marks legal-source-version lock as a governance requirement.	Run legal-document control check before declaration freeze; block release if date fields are not traceable to one approved legal reference pack.	monitor
North America codified-vs-consensus standard status for AGV acceptance	Current OSHA codified text (29 CFR 1910.178) and the 2022 proposed update path are both publicly available.	Whether/when the proposed update path will be finalized in a way that changes your mandatory baseline during this project window.	Uses a dual-layer baseline (current codified text + proposed update tracking) and avoids treating proposal language as already mandatory.	Run legal-status checkpoint at each major gate and keep a dated compliance memo in the project file.	monitor
PROFINET conformance-class alignment with delivered devices	PNO guidance differentiates CC-A/B/C/D and indicates CC-A is not preferred when higher classes are feasible.	Whether selected supplier devices and engineering tools enforce the claimed class behavior under your real cycle/load profile.	Treats CC declaration as initial filter only and requires commissioning evidence for timing-sensitive cells.	Capture class claim + measured update/jitter + diagnostics behavior per device before final architecture freeze.	pending
Drive EMC/electrical standard applicability classification	IEC 61800-5-1 and IEC 61800-3 publish explicit scope and exclusion boundaries (including traction/electric-vehicle contexts).	Which exact product classification path your certifier will apply to each AGV drive subsystem (and whether extra radio/sector requirements are triggered).	Treats EMC/electrical safety as a separate evidence stream rather than assuming functional-safety references are sufficient.	Lock classification decision and standards list with certifier/safety assessor before supplier nomination.	pending
Cross-standard equivalence for ingress terminology	IEC 60529 and ISO 20653 both define IP-code frameworks with different product-context assumptions.	A universal cross-sector mapping for every AMR cleaning profile is not publicly standardized.	Keeps IP69K wording as context-bound claim and avoids treating it as universal shorthand.	Document test standard + cleaning profile in each RFQ and require supplier test-report traceability.	monitor
ATEX harmonised-standard version drift for industrial-truck use	Directive 2014/34/EU establishes legal scope and the Commission publishes harmonised-standard references via Implementing Decision workflow.	Which exact harmonised-standard edition/transition window each supplier uses in your planned release window.	Uses current consolidated publication reference and flags version governance as a release-gate check.	At design freeze, lock one CELEX publication baseline and verify supplier declarations against the same standards-reference set.	monitor
CRA readiness maturity for steering-drive/control vendor stack	CRA staged applicability dates are public and include industrial control system contexts.	Real supplier readiness for SBOM, coordinated vulnerability handling, and secure-update governance in your exact program.	Treats cybersecurity as a release-gate stream, not a post-commissioning add-on.	Add CRA checklist evidence requests to RFQ and gate supplier approval on measurable security process artifacts.	pending
Battery due-diligence readiness across shortlisted suppliers	Regulation (EU) 2025/1561 postpones battery due-diligence obligations to 18 Aug 2027 and updates the guideline milestone.	Whether shortlisted suppliers can provide traceability and due-diligence evidence on your project timeline.	Marks due-diligence evidence as a supplier-gate item, not a post-award paperwork task.	Add due-diligence evidence requirements to RFQ now and run a date-aligned supplier readiness check before design freeze.	pending
UN 38.3 test-summary completeness for service and spare batteries	49 CFR 173.185(a)(3) sets test-summary availability requirements for applicable lithium cells/batteries in transport workflows.	Whether each shortlisted supplier can provide complete test-summary artifacts and required data fields for every planned battery variant.	Flags this as a release and logistics gate, not a post-award document request.	Collect sample test-summary packets during RFQ and reject suppliers that cannot provide traceable artifact sets.	pending
Recent public TCO dataset for fuel-cell vs battery material handling	NREL 2013 publishes scenario-bounded ownership-cost deltas for multi-shift deployments (Class I/II and Class III) and remains a traceable public benchmark.	No comparably broad and recent public dataset was identified in this round that reproduces those comparisons across current battery, labor, and hydrogen cost regimes.	Uses NREL values as historical boundary reference only and avoids presenting universal savings claims.	Mark as pending confirmation and request updated operator/public-program datasets before using fuel-cell TCO advantages as default assumptions in RFQ baselines.	pending
Site-level electricity carbon and tariff baseline for battery-electric claims	EPA eGRID 2023 publishes large subregion CO2-rate spread, and EIA annual data shows industrial tariffs moved between 2024 and 2025.	Your exact deployment-site marginal grid factor, tariff structure, and expected contract-price path over the product lifecycle.	Uses EPA/EIA data as boundary anchors and avoids fixed universal emissions or cost claims in pathway comparison.	Collect site utility tariff terms and location-specific grid factors, then run low/base/high scenarios before supplier shortlisting.	pending
Impact of ISO 24134 replacement on current steering-control assumptions	ISO 24134 is confirmed as current but marked to be revised, with ISO/CD 24134 listed as replacement track.	What requirement deltas in the replacement track will affect your control architecture and validation plans.	Treats the baseline as usable but lifecycle-sensitive for long-cycle programs.	Track ISO/CD 24134 progression and run a standards-delta review before final acceptance testing.	monitor
Operational cybersecurity control maturity (beyond legal-date tracking)	NIST SP 800-82r3 and IEC 62443-2-1 provide implementation-level OT security guidance for long-lived systems.	Whether your supplier stack and internal operations can execute patch, vulnerability-response, and hardening controls at required service levels.	Treats cybersecurity as a release-gate stream with explicit implementation evidence requests.	Run OT control readiness assessment (asset inventory, patch SLA, vulnerability workflow) before productization lock.	pending

Scenario outcomes

Scenario	Assumptions	Process	Outcome
A. 1.2 t indoor pallet AMR, smooth floor	1.6 m/s, 8% grade, duty 70%, IP65, EtherCAT	Tool estimates moderate per-wheel peak torque and medium reserve. Thermal risk remains manageable with encoder feedback.	Integrated Alternative powertrain is usually viable, with commissioning focus on ramp tuning, slip checks, and timing-budget confirmation.
B. 2.8 t heavy transfer AMR, jointed concrete	2.1 m/s, 12% grade, duty 90%, IP67, PROFINET	Peak torque includes the selected shock factor while continuous reserve rises with duty and thermal pressure.	Sealed heavy-payload unit or split architecture is safer than compact integrated modules; bus-cycle governance becomes a release-critical check.
C. Cleanroom AMR with frequent sanitation	Low shock, frequent sanitation, IP target under review	Ingress terminology is mapped to the applicable standard context before selecting hardware.	Steer-drive or sealed integrated options remain valid; thermal and maintenance access should drive final selection.
D. Retrofit platform with legacy CANopen stack	Existing controller constraints, no encoder redundancy, high update demand	Protocol lock-in and sensing gaps lower confidence despite acceptable static torque estimates.	Result should be treated as review/risk until control-loop telemetry and safety path are upgraded.
E. Same steering-drive platform released in EU and North America	Shared hardware baseline, dual-region deployment target, mixed customer acceptance criteria	Tool output is paired with jurisdiction mapping (EU regulation timeline + North America B56.5/R15.08 package) before supplier commitment.	Teams avoid late-stage acceptance rework by aligning evidence artifacts to both regions at design-freeze time.
F. Connected AMR with lithium service-battery swaps in U.S. operation	Remote diagnostics enabled, replacement battery logistics in scope, mixed supplier readiness	Design team passes torque/protocol checks, then verifies codified U.S. standard status and UN 38.3 test-summary artifacts before release.	Program avoids late shipment and acceptance delays by treating legal-status and battery-transport evidence as first-class gate criteria.

Alternative Powertrain FAQ by Decision Intent

Questions are grouped for intent clarity: scope alignment, tool operation, and decision-risk execution.

Intent & Scope

Which alternative powertrain paths does this page compare?

It compares battery-electric, hybrid-electric (including range-extended), and fuel-cell electric paths for AMR traction systems. Use /learn/alternative-powertrains#alias-alternative-powertrains for the method and scope notes.

Is this a steering-drive supplier selector or a sizing workflow?

It is a sizing and architecture-fit workflow first. Brand shortlist comes after torque, ingress, duty and safety constraints are clear.

Can this tool replace OEM sizing software or FEA?

No. It is a front-end screening layer to reduce wrong candidates early. Final selection still requires OEM data and application validation.

Does ISO 3691-4 cover every AMR operating environment?

No. The standard page summary includes exclusions (for example public-road operation and explosive atmospheres). Those cases need additional standards mapping.

Does ISO 3691-4 also define power-source requirements for the vehicle?

No. The ISO 3691-4 scope summary explicitly states that requirements for power sources are not covered in that document, so battery/power architecture needs separate requirement mapping.

What if our AMR must operate in potentially explosive atmospheres?

Treat that as a scope handoff, not a minor variant. Move to an ATEX requirement stream (Directive 2014/34/EU plus current harmonised-standards publication set) instead of reusing non-ATEX assumptions from this baseline.

If we deploy in North America, is ISO-only compliance mapping enough?

Usually no. North America programs commonly require ANSI package mapping (for example B56.5 and R15.08 system/application requirements) in addition to ISO-based engineering references.

If we use the latest ANSI editions, is OSHA compliance automatically satisfied in the U.S.?

Do not assume that automatically. Current codified text in 29 CFR 1910.178 should be checked directly, and newer ANSI edition adoption should be tied to explicit legal-status confirmation (the OSHA update path is published as a proposed rule).

Why is ISO 24134 mentioned together with ISO 3691-4 on this page?

ISO 3691-4 is the main driverless-truck safety baseline, while ISO 24134 adds automated-function control requirements (steering/travel/lifting context). This page treats them as complementary boundaries, and flags that ISO 24134 is in a revision track.

Why are there report sections after the calculator?

The tool gives immediate outputs. The report layers show evidence, uncertainty, and tradeoffs so teams can defend the final decision.

What if our internal checklist still shows 14 Jan 2027?

Treat it as a legal-document control issue. This page follows the corrigendum milestone set (including 20 Oct 2026 and 20 Jan 2027). Freeze one approved CELEX/corrigendum reference set before declaration or contract gates.

Tool Usage

What is the minimum data needed for a meaningful result?

Gross mass, wheel radius, drive-wheel count, speed ramp, grade, and duty cycle are the minimum fields for actionable torque estimation.

What if I only know payload but not full vehicle mass?

Use a conservative temporary mass estimate and mark confidence low. Replace with measured curb mass before procurement.

How should I choose ingress level (IP54/IP65/IP67/IP69K)?

Choose according to real contamination and cleaning process, not preference. Overspecifying ingress can raise heat and maintenance costs.

Is IP69K always the same thing as IEC 60529 IP ratings?

Not exactly. IEC 60529 and ISO 20653 have different standard contexts. Keep the test standard and environment assumption explicit in requirements and RFQs.

Why does the tool output reserve percentage?

Reserve is an internal policy buffer for thermal and environmental uncertainty, not a standard value. The optional shock toggle separately applies a 20% peak-force factor; both assumptions require supplier and pilot validation.

Why is IEC 62619 referenced on an Alternative powertrain page?

Because ISO 3691-4 excludes power-source requirements. If your drive architecture depends on onboard lithium battery systems, battery safety must run as a parallel requirement stream instead of being assumed inside traction sizing.

Does STO or IEC 61800-5-2 alone cover drive electrical safety and EMC claims?

No. Functional safety is only one layer. Electrical/thermal safety and EMC applicability must be checked separately, and standards scope boundaries (for example traction/radio conditions) should be confirmed before final compliance claims.

What makes a result "inconclusive"?

When key telemetry/safety evidence is missing or multiple critical boundaries are crossed, the tool intentionally avoids giving a false-safe answer.

Can I use this for omni or steer-drive platforms?

Yes, but verify wheel-load distribution assumptions. Non-symmetric architectures need extra correction beyond equal force split.

How should I read the EtherCAT/PROFINET/CANopen comparison?

As a boundary screen, not a winner table. Validate your real cycle time, jitter and diagnostics load in the final control architecture.

Why does CANopen guidance here mention 25 m at 1 Mbit/s instead of 40 m?

Because this page prioritizes CANopen-specific lower-layer guidance for conservative planning (including stub limits), not generic CAN headline values that may look optimistic in deployment.

Does selecting PROFINET/TSN automatically guarantee sub-250 us timing?

No. Guideline-level timing bands are only an initial screen. Sub-250 us behavior can require vendor-specific implementation and full controller-network-drive validation.

Does TSN replace PROFINET in this decision flow?

No. TSN is treated as a layer-2 extension path. PROFINET services (for example diagnostics, alarms, and parameterization workflows) still need end-to-end validation in your architecture.

Decision & Risk

When should I avoid compact integrated Alternative powertrains?

Avoid them when duty and peak torque are both high, or when ambient and ingress requirements restrict thermal headroom.

What is the most common failure in early sizing decisions?

Treating peak torque and continuous thermal load as independent. In real AMR duty profiles they interact and can invalidate optimistic sizing.

How does compliance affect Alternative powertrain choice?

Compliance scope influences documentation, safety function architecture, and verification workload. These can alter viable steering-drive options.

Can emergency stop or STO claims alone prove stopping safety?

No. ISO 13850 and drive-safety standards must be translated into a system-level stop strategy, verification plan, and acceptance criteria.

Does ISO 13849-1 give a fixed PLr target for Alternative powertrains?

No. The standard defines principles and evaluation structure, but the required PLr must be set by your project risk assessment and validated in the final architecture.

Is CANopen always worse than EtherCAT for this use case?

Not always. CANopen can be valid for moderate dynamics, but the risk rises when update-rate demand and node count increase.

When should we evaluate CANopen FD instead of classic CANopen?

Consider it when classic CANopen timing margin is repeatedly tight, but treat CANopen FD as a migration program that requires controller/drive/toolchain interoperability proof before rollout.

What is the next step after a high-risk result?

Freeze risky assumptions, run pilot telemetry capture, and request OEM torque-temperature data before final BOM decisions.

What is the next step after a fit result?

Move to supplier shortlist with documented assumptions, then execute commissioning tests that validate ramp, thermal and slip boundaries.

How do we avoid cross-region compliance surprises late in the project?

Build a dual-region evidence matrix at design freeze, mapping each requirement and verification artifact to the target market standard set before procurement lock.

Do cybersecurity requirements matter for steering-drive/control architecture decisions?

Yes for connected products. CRA milestones should be mapped into the same release governance used for control-loop and safety validation so security evidence is not deferred until after integration freeze.

Does the 2027 battery due-diligence date mean we can delay supplier evidence work until then?

No. The legal application date moved to 18 Aug 2027, but supplier readiness checks should start early so RFQ, sourcing, and release gates are aligned and not blocked late.

Why does this page ask for UN 38.3 test-summary readiness if this is a drive-system decision?

Because drive architecture decisions often lock battery supplier and service logistics paths. Missing test-summary artifacts can block battery transport and after-sales support even when torque and control sizing look acceptable.

If we track CRA dates, is that enough for cybersecurity readiness?

No. Dates are legal gates. Engineering readiness still needs implementation-level controls (for example OT hardening, patch/vulnerability workflows, and lifecycle governance) validated with measurable evidence.

Next step after this page

If your result is fit/review, move to shortlist validation with real telemetry. If your result is risk/inconclusive, close data gaps first to avoid high-cost rework later.

Request powertrain engineering review Jump to alias section for alternative powertrains