Skip to content
ZHEKAAZHEKAA

How we work

From first request to start of production

We join at any phase and leave a traceable trail of work products behind us. On site or remote, in English or French.

Program lifecycle

What we deliver at each phase

  1. 01 · RFI

    Request for information

    • RFI document or RFI response
    • Technical feasibility notes
    • Supplier landscape and shortlist
    Learn more
  2. 02 · RFQ

    Request for quotation

    • Component / system technical specification
    • Safety and process requirements
    • Technical bid comparison
    Learn more
  3. 03 · SOW

    Scope of work

    • Work-package breakdown
    • Effort estimate and milestones
    • DIA and RASIC matrix
    Learn more
  4. 04 · ARCH

    Architecture

    • Functional and logical architecture
    • E/E allocation and interfaces
    • Redundancy and degradation concept
    Learn more
  5. 05 · DEV

    V-cycle development

    • System, software and hardware requirements
    • Design and application software (ASW)
    • Integration and verification reports
    Learn more
  6. 06 · VAL

    Validation

    • Test strategy and specifications
    • MIL / SIL / HIL campaigns
    • Vehicle-level test and fault-injection reports
    Learn more
  7. 07 · CAL

    Calibration

    • Driving DNA and mode targets
    • Calibration datasets
    • Subjective and objective evaluation reports
    Learn more
  8. 08 · SOP

    Start of production

    • Safety case and confirmation measures
    • Release evidence and open-point closure
    • Regulatory compliance support
    Learn more

Interactive V-cycle

Our deliverables along the V

Select a step to see the work products we deliver.

01 · Customer requirements

  • Stakeholder and customer requirement analysis
  • Item definition (ISO 26262)
  • Acceptance criteria
  • Requirement baseline in DOORS or your ALM tool

02 · System requirements & architecture

  • System requirements with bidirectional traceability
  • Functional and logical architecture
  • HARA and functional safety concept
  • Interface and signal definitions

03 · SW / HW requirements

  • Software and hardware requirements
  • Technical safety concept and safety requirements
  • HW/SW allocation
  • Requirement reviews

04 · SW / HW design

  • Software architecture and component design
  • Model-based design (Simulink / Stateflow)
  • Safety analyses: FMEA, FTA, DFA
  • Design reviews

05 · Implementation

  • Application software (ASW) in Simulink or C/C++
  • Code generation and MISRA C compliance
  • Static analysis
  • Calibration parameters

06 · Unit verification

  • Unit test specifications and results
  • Structural coverage reports
  • MIL / SIL back-to-back tests
  • Defect reports

07 · SW / HW integration & verification

  • Integration test specifications
  • HIL campaigns and regression suites
  • Interface verification
  • Verification reports

08 · System integration & verification

  • System test specifications
  • Vehicle network and diagnostic tests
  • Fault-injection tests
  • Traceability: tests ↔ requirements ↔ safety goals

09 · Vehicle validation

  • Vehicle-level validation plan
  • Track and open-road campaigns
  • Validation of safety mechanisms and safe states
  • Validation report and release recommendation

Engagement models

Six ways to work with us

Working principles

What you can expect

  • Scoped before we start

    Every mission starts with a written scope, deliverables and acceptance criteria.

  • Traceable work products

    Requirements, analyses and tests linked end to end, ready for audits and assessments.

  • Confidentiality first

    NDA before any technical exchange. Your data and IP stay yours.

  • Your tools, your process

    We work in your ALM, PLM and toolchain, and follow your development process.

Where we work

Wherever vehicles are engineered

On site or remote, in English or French.

  • Saudi Arabia
  • United Arab Emirates
  • Qatar
  • Morocco
  • Europe
  • Worldwide on request

Which phase is your program in?

Share the phase, the domain and the constraint. We will propose the right engagement model.