MATLAB · Simulink · embedded
Software the vehicle can run.
CodLad's automotive studio writes and tests model-based software — MATLAB, Simulink, embedded C — for teams who need extra hands that already know the toolchain. Same QC culture as our clinical work: named engineers, reviewed models, no mystery commits.
Who it's for
The brief we take.
Software leads at OEMs and Tier-1s who need production-quality Simulink and embedded support without a long hiring cycle.
Deliverables
What leaves the studio.
- MATLAB / Simulink model development and refactor
- Embedded C and production-code generation support
- Unit, SIL and HIL test artefacts
- Model standards, reviews and documentation
- Toolchain scripts that make the pipeline repeatable
Tools & standards
The stack, without the logo wall.
Engagement
How you hire us.
- Feature team augmentation
- Model-cleanup / technical-debt sprint
- Test-harness build-out
Anonymized: Simulink controller refactor for a Tier-1 powertrain programme, with SIL coverage lifted and a documented modelling standard left behind.
FAQ
Before the call.
Why does a clinical company write automotive code?
The same people who obsess over traceability in ADaM obsess over it in models. CodLad was built as a programming studio. Clinical is the larger practice; automotive is a real second line, not a footnote.
ISO 26262?
We work inside your safety process and coding standard. We do not sell a certified process of our own; we plug into yours.
Also in the studio
Statistical Programming
Submission-ready analysis datasets and TLFs, programmed once and QC'd twice.
Clinical Study Reporting
CSR sections, appendices and in-text tables written to the numbers — not around them.
Data Management
Clean, lockable clinical databases with CDASH-minded eCRFs and a query process that does not stall sites.
Tell us what is on the clock.
A scoping call is thirty minutes. Bring a protocol, a TLF list, or a model that needs hands.