Proposal for New MME Header Field - Data Source Type

Suggestions for new codes
Post Reply
Miguel A Gallego
Posts: 12
Joined: Mon Apr 20, 2020 8:24 am
Company: Applus IDIADA Group

Proposal for New MME Header Field - Data Source Type

Post by Miguel A Gallego »

Dear colleagues,

As discussed in the meeting of today, I would like to propose adding a new field to the MME header to identify the data source type:

Type of data source: <Simulation | Hardware>

Rationale:

Euro NCAP is proposing a similar field in their data formats to distinguish between simulation-based tests and physical tests. Incorporating this into MME would:

Improve data traceability and interpretation
Align with evolving industry standards
Support mixed virtual/physical testing workflows

This would be a simple addition with broad applicability across all MME-based test data.

I welcome your feedback on this proposal.

Best regards,

Miguel Ángel Gallego
DiVe
Posts: 471
Joined: Tue Apr 24, 2007 9:14 am
Company: IAT mbh
Location: IAT Berlin - Germany
Contact:

Re: Proposal for New MME Header Field - Data Source Type

Post by DiVe »

Dear Miguel,

I checked in the ENCAP documents and found the following requirements:

CP005 V1.4
2026-05-13 10_11_24-cp-005-data-acquisition-and-injury-calculation-v14_IAT - PDF-XChange Editor.png
2026-05-13 10_11_24-cp-005-data-acquisition-and-injury-calculation-v14_IAT - PDF-XChange Editor.png (12.12 KiB) Viewed 18 times
CA004 V1.3
2026-05-13 10_12_51-CA 004 - Data Acquisition and Assessment Criteria Calculation v1.3 - PDF-XChange.png
2026-05-13 10_12_51-CA 004 - Data Acquisition and Assessment Criteria Calculation v1.3 - PDF-XChange.png (64.95 KiB) Viewed 18 times

So, actually the need to align the documents, but they will be consistent with your proposal.
In my opinion this is a sensible extension to be included in RED A (and later in the official documents for V2 also).
More and more ratings start to add simulation to their rating scheme.

The already existing descriptors "Type of the test" and "Subtype of the test" could also be used in adding
the "category" text, but in the past we have seen that different Labs/OEMs do already have a fixed set of
entries for these descriptors.

Therefore, a separate descriptor will be best.
We can then define fixed classification items to be used.

Are there more variants to think of for this category?

In each measurement channels there is already a descriptor that defined the Data source.
When using the easily noticeable descriptor in the test descriptor file (*.mme) these
channel descriptors must be consistent!

2026-05-13 10_32_36-ISO_TS13499_RED_A_V16Rev3_20260223.png
2026-05-13 10_32_36-ISO_TS13499_RED_A_V16Rev3_20260223.png (69.82 KiB) Viewed 18 times
Kind regards,
Dirk
Post Reply

Return to “Additional codes”