xIL environments
MIL, SIL, HIL, virtual and physical targets, real-time execution, operator workflows, and bench control.
Technology & integrations
Fit the software around the engineering system—not the other way around.
DEVlink separates engineering intent, simulation, orchestration, interfaces, diagnostics, and evidence so each layer can evolve without unnecessary hardware or tool lock-in.
Reference architecture
An open software-defined engineering layer
The exact components depend on the customer environment. The structure below shows how DEVlink connects engineering intent, software workflows, execution platforms, interfaces, and systems under test without hiding integration boundaries.
Engineering intentRequirements, standards, test purpose, variants, expected behaviour
Product workflowsChargeLink, DEVlink MIL Studio, configurations, campaigns, model workflows, and review
Orchestrate · automate · diagnose · trace
Models & simulationMIL, SIL, plant models, protocol counterparts, scenario logic
Execution & xILRunners, real-time targets, HIL platforms, bench control, CI pipelines
Interfaces & I/OCAN, CAN FD, Ethernet, charging communication, APIs, measurement
Connect through defined integration boundaries
Systems under testECU, EVCC, OBC, LRU, controller, connected product, subsystem
Existing investmentsThird-party platforms, custom rigs, lab equipment, internal tools, and established workflows
Typical integration areas
Connect to the environment the team already uses
These are common integration categories, not a universal compatibility claim. Every project starts with a technical fit review.
Vehicle and embedded networks
CAN, CAN FD, Ethernet, communication databases, diagnostics, traces, and signal exchange.
EV charging systems
EVCC, OBC, EVSE counterpart behaviour, CCS communication, ISO 15118, DIN SPEC 70121, and session diagnostics.
Automation and CI
Machine-readable control, campaign execution, configurations, schedules, result exchange, and regression workflows.
Requirements and test systems
Source context, test intent, execution links, traceability, evidence, and reporting boundaries.
Existing and specialist platforms
Connect suitable commercial, customer-specific, and specialist platforms while retaining an open software architecture.
Architecture principles
Keep the system open, controlled, and explainable.
- Separate product logic from target-specific hardware integration
- Keep interfaces explicit and testable
- Reuse scenarios, configurations, and engineering context
- Support operator workflows and automated execution together
- Make diagnostics and evidence part of normal engineering work
- Introduce new platforms without rebuilding every software layer
Map your current environment with DEVlink.
Bring the system under test, current tools, interfaces, repeated manual work, and the outcome the engineering team needs.