END USER: Hash identifier

[Loic-MJ]

Hello,
Point 3 in Appendix to the Addendum to the Type Approval Certificate, request "Hash identifier code of the correlation tool output report". How can we find this information in the correlation output and dice report? Does "hexnum" represent the hash of the file?
Is it required always when the correlation tool is run or only when physical test is needed?
Thanks for your help

[VictorValverde]

Dear @Loic-MJ ,
Currently, the correlation regulation mentions 2 hashes:

• Section 3.1.1.1. Original correlation output report. Following a completed test run on the correlation tool, an original correlation output report shall be issued and attributed with a hash code.
  This hash code unequivocally identifies a CO2MPAS input file and its associated CO2MPAS output file. In other words, this hash identifies a CO2MPAS execution. It is possible to retrieve the hash from the report that is generated when running the command co2dice project report. The alphanumeric code identified as object is the hash valid for this section.
  

• Section 3.1.1.2. Complete correlation file. A complete correlation file shall be created, including the time-stamped reply and the original correlation output report referred to in point 3.1.1.1. A hash code shall be attributed to the complete correlation file. Conceptually speaking, this hash is "on top" of the hash mentioned above. It contains a mention to the previous and in addition it contains the dice decision. As you mentioned, this hash corresponds to the hexnum that is shown in the console when parsing the dice email either with co2dice project tparse and pasting the received email or through co2dice project trecv vehicle_family_id when allowing the DICE to search for the email inside the mailbox.
  

Whenever the DICE is used, independently from the dice decision it is important to keep in the Type Approval documentation folder the following elements:

• The exported dice project. This is a compressed (.zip) file containing all the files used in the DICE workflow (ie, the CO2MPAS input file, the CO2MPAS output file, and the Dice decision). Once the project has been sampled (the OK/SAMPLE decision has been taken) and the project tag becomes sample/nosample it can be easily exported with the command codice project export vehicle_family_id.
• A copy of the dice response email.

Kind regards.

[MaikeruJon]

Loic-MH said
"Point 3 in Appendix to the Addendum to the Type Approval Certificate, request "Hash identifier code of the correlation tool output report"."
Where? I can't see it in the type approval certificate in appendix 4 of annex 1 of 2017/1151. Has 2017/1151 been amended?
The link in VictorValverde's informative reply is to 2017/1152 which doesn't have a copy of the certificate, but does contain the same two references to the hash code as are also in 2017/1231

[pavlovicj]

Dear @MaikeruJon,
you are right that Appendix to the Addendum to the Type Approval Certificate does not foresee input of any hash identifier code generated by the CO2MPAS. Point 3 of that Appendix is related to the deviation factor.
What @VictorValverde explained in previous reply is the so-called "correlation regulation" or 2017/1152 where hash code is mentioned and he explained what shall be stored in TA documentation in order to be able to track the whole correlation process (input files, output report, dice report).
Best Regards

[ankostis]

@Loic-MJ, @MaikeruJon and ALL users of v1.7.x:

The finalization procedure has changed in v1.7.x version according to the feedback in this issue.
It is roughly mentioned in the release notes of v1.7.x

• Basically, in the last release the co2dice project trecv/tparse commands generate another type of report, the "decision-report", that is also signed with your secret-key, and which contains HASH-2 at the top.

• The report command has also been retrofitted to printout this 2nd "decision-report", as seen below:
  

  Use that highlighted elements to construct the HASH-2 for certification paper-forms and/or emails exchanged with TAAs, like that:

  dices/IP-10-AAA-2017-1234/1 936845d307388a8a44f02855b075cf69b1817d82
  

  Actually just using the first 7-10 characters of the hash is enough to identify the specific dice procedure in its entirety: 936845d3073

• Finally, the project export command continues to produce an archive with all electronic data of the procedure that must reach, at some point, also the TAA.