Source files

Mapping profiles

Import history

File	Kind	Rows	Checksum
VME-PROD-VehicleMotionManagement - VMMP_VVL.xlsx	requirement	167	0c9f63958867
VME-PROD-VehicleMotionManagement - VMMP_TVC_TVCTP.xlsx	requirement	54	6e55261e37b1
VME-PROD-VehicleMotionManagement - VMMP_TVC_TVCPV.xlsx	requirement	48	c291bbf0bf8b
VME-PROD-VehicleMotionManagement - VMMP_TVC_TVCPP.xlsx	requirement	75	a6e97f36e717
VME-PROD-VehicleMotionManagement - VMMP_TVC_TVCOP.xlsx	requirement	108	db974db96a4a
VME-PROD-VehicleMotionManagement - VMMP_TVC_TVCIP.xlsx	requirement	38	83adee9380f8
VME-PROD-VehicleMotionManagement - VMMP_TVC_TVCEC.xlsx	requirement	30	e01f733449cc
VME-PROD-VehicleMotionManagement - VMMP_SRVPOST_SSHPOST.xlsx	requirement	127	fe72dab6a70d
VME-PROD-VehicleMotionManagement - VMMP_SRVPOST_DSOPOST.xlsx	requirement	140	ac32d5a0db26
VME-PROD-VehicleMotionManagement - VMMP_SRVPOST_DCPOST.xlsx	requirement	60	d072d8489fe8
VME-PROD-VehicleMotionManagement - VMMP_SRVPOST_ASM.xlsx	requirement	149	42ae852b3eba
VME-PROD-VehicleMotionManagement - VMMP_SRV_VSOVD.xlsx	requirement	255	ad930242c8fe
VME-PROD-VehicleMotionManagement - VMMP_SRV_VSOEM.xlsx	requirement	405	1e925fb5e240
VME-PROD-VehicleMotionManagement - VMMP_SRV_VSOCH.xlsx	requirement	105	fa03f07e2505
VME-PROD-VehicleMotionManagement - VMMP_SRV_DSOPRE.xlsx	requirement	197	38690409fbd8
VME-PROD-VehicleMotionManagement - VMMP_SRV_ASOTA.xlsx	requirement	135	43cdaf3292f4
VME-PROD-VehicleMotionManagement - VMMP_SRV_ASOPOT.xlsx	requirement	184	da96d0c9b61e
VME-PROD-VehicleMotionManagement - VMMP_SRV_ASOAF.xlsx	requirement	400	5d887cf54208
VME-PROD-VehicleMotionManagement - VMMP_SOUT_SOUTFCT.xlsx	requirement	453	4d2bdab4dd1f
VME-PROD-VehicleMotionManagement - VMMP_SOUT_SOUTDEVLP.xlsx	requirement	51	aa25670a5db1

VME-PROD-VehicleMotionManagement - VMMP_CRM_CRMFH.xlsx · source records


Short description
The Module CRMFH (Central Release Management Failure Handler) is a submodule of CRM.

The CRM sub-function "FailureHandler" links the active diagnostic events with the target states of the VMM sub-functions via a matrix. This means that for each diagnostic event, the matrix indicates the target states in which the state machines of the sub-functions are to be set as soon as this diagnostic event occurs. 

The CRM sub-function "FailureHandler" links the active diagnostic events with the diagnostic causes of the VMM sub-functions via a matrix. This means that the matrix specifies for each diagnostic event which diagnostic cause is to be made available for the respective state machine of the sub-functions as soon as this diagnostic event occurs.
Interface description
The valid version of the signal and parameter files for the relevant SWRS are:


Presetting/Framework/Definitions
Traceability
SWRS to Testcase:

The latest revision of the test specification document is valid for the tracability SWRS to Testcase
SWRS to CodeBeamer: 

CodeBeamer-IDs are mentioned in the SWRS atrribute DOORS IDs.

The latest baseline of the specification document (CodeBeamer) is valid for the traceability SWRS to CodeBeamer.
Toolchain
The Matlab/Simulink/TargetLink versions have to be used according to the HCP1-Toolchain.
For modeling in Simulink the valid EnProVe catalogue of guidelines has to be used.
Tolerances
For the comparison of output signals to the expected reactions or by back-to-back tests (MiL-PiL) following tolerances are accepted for deviations:
Bool: No deviation allowed
UInt, Int: No deviation allowed
Float: 0.1% related to the permissible value range of the signal
Bit numbering
The bit numbering takes place as zero-based numbering method. 

This means, 1 Byte is equal to Bit 0...7.
Requirements
For all requirements (except "examples"), an excel table with the name "VMM_CRM_FunctionMatrix.xlsx" is provided (see Modul SWRS_VMMP chapter "Central Release Management") 

It shall be used for the test implementations.
For all examples, an excel table with the name "VMM_CRM_FunctionMatrix_Example.xlsx" is provided  ), which is used as the data basis.

The examples don't refer to the real excel table so the examples remain valid even when the real excel table is changed.

The general structure of the example excel table and the real excel table are of course the same.
Definition and naming conventions
The following naming conventions will be used:

* Sheet refers to one of the sheets of the excel table, i.e. the sheets "dtc", "reaction" and "statemachine". 

* Row, column and cell are used with regard to the excel table 

* Target state and degradation reason are used with regard to the module. These are outputs of the CRM modules.
Active row 

A row of a sheet is called active row, if the input of the module with the name given by the column "signal name" has the value given by the column "signal constant"

Example:

Let's assume the following inputs to the module:

* ASOAF_s_DiagDrvPosn_StEveReq = VMMP_c_DiagEveSigIni

* ASOAF_s_EPBActrCtl_StAvl = VMMP_ASOAF_c_EPBActrCtl_StAvlReleaseOnly

In this example the only active row of the sheet "dtc" is row 7.

The active rows of sheet "reaction" are row 4 and row 11.
The column with the name "use" in the sheet "reaction" indicates if a given signal is relevant or not for the computation. If a cell in this column "use" is empty, then the entire corresponding row shouldn't be considered for computation purposes.
Output names
The name of the output depends on the name of the column itself:

If the name of the column contains at least one underscore "___", then

* Name of StTar FH is CRMFH_s___{column name part 1}_StTar{column name part 2}FH

* Name of DgrdRsn FH is CRMFH_s___{column name part 1}_StDgrdRsn{column name part 2}FH

* Name of StTar ExA is CRMFH_s___{column name part 1}_StTar{column name part 2}ExA

where {column name part 1} is everything of the name of the column up to the first underscore "___" 

and where {column name part 2} is everything of the name of the column col after the first underscore "_"

Otherwise:

* Name of StTar FH is CRMFH_s___{column name}_StTarFH

* Name of DgrdRsn FH is CRMFH_s___{column name}_StDgrdRsnFH

* Name of StTar ExA is CRMFH_s___{column name}_StTarExA

where {column name} is the name of the column
Example:

The outputs for the example are:

* "CRMFH_s_Foo_StTarBiFH", "CRMFH_s_Foo_StDgrdRsnBiFH" and "CRMFH_s_Foo_StTarBiExA" for state machine "Foo_Bi"

* "CRMFH_s_Foo_StTarBobFH", "CRMFH_s_Foo_StDgrdRsnBobFH" and "CRMFH_s_Foo_StTarBobExA" for state machine "Foo_Bob"

* "CRMFH_s_Fara_StTarFH" and "CRMFH_s_Fara_StTarExA" for state machine "Fara"

* "CRMFH_s_BarLgtCtl_StTarFH" and "CRMFH_s_BarLgtCtl_StTarExA" for state machine "BarLgtCtl"

* "CRMFH_s_BarLatCtl_StTarFH" and "CRMFH_s_BarLatCtl_StTarExA" for state machine "BarLatCtl"
Each column- starting with column F - of the sheet "reaction" describes the following outputs of the module, which are described in detail in chapter "Outputs" below:

* Target state provided by failure handler - in the following named StTar FH

* Degradation reason provided by failure handler - in the following named DgrdRsn FH; this output does not always exists, see section "Outputs" for more details

* Target state provided by external availabilities handler - in the following named StTar ExA
Target state priority
The state machines are given by the sheet "statemachine" in column "state machine name" .
Highest target state priority 

For each state machine, the prioritization shall be done using the sheet order according to the target state priorities given by the sheet "statemachine" in column "states (long name)"
Examples:

* The state machine "Foo_Bi" has two target states "Off" and "On". "Off" has the higher priority, because in the list it is above "On".

* The state machine "BarLgtCtl" has five states. The priorities are from high to low as follows: "Off", "Failure", "Restricted", "NotAvailable", "On". This is because in the list "Off" is above "Failure", "Failure" is above "Restricted" and so on.

* For the statemachine BarLgtCtl and its output CRMSA_s_BarLgtCtl_StTar the following table shows some example of possible permutations:

 Empty attachment [_ae85b99a-baf9-47aa-bd9d-d0bda1ef6b49_2_1.png]
The SPE constant name for each target state, i.e. column "states (long name)" of sheet "statemachine" is as follows:

* CRMSA_c___{state machine}StTar{state}, if the group name given by column "group name" is empty

* CRMSA_c___{group name}StTar{state}, otherwise

Where

* {state machine} is the name of the state machine given by column "state machine name" of sheet "statemachine"

* {group name} is the name of the group given by column "group name" of sheet "statemachine"

* {state} is the name of the state given by column "states (short name)" of sheet "statemachine"
Examples:

The SPE constants in this example are:

* For state machine "Foo_Bi": CRMSA_c_Foo_BiStTarOff, CRMSA_c_Foo_BiStTarOn

* For state machine "Foo_Bob": CRMSA_c_Foo_BobStTarOff, CRMSA_c_Foo_BobStTarOn

* For state machine "Fara": CRMSA_c_FaraStTarOff, CRMSA_c_FaraStTarAvlNoBkp, CRMSA_c_FaraStTarOn

* For state machine "BarLgtCtl": CRMSA_c_MY_GroupStTarOff, CRMSA_c_MY_GroupStTarFailure, CRMSA_c_MY_GroupStTarRestricted, CRMSA_c_MY_GroupStTarNotAvailable, CRMSA_c_MY_GroupStTarOn
Degradation reason priority
The priorities are from high to low as follows:

* Failure

* Init

* None
The SPE constant name for each degradation reason value is defined as follows:

* Failure: VMMP_CRM_c_StDgrdRsnFail

* Init: VMMP_CRM_c_StDgrdRsnIni

* None: VMMP_CRM_c_StDgrdRsnNone
Outputs
Examples:

To explain the content of this section, the example is split in smaller parts given after each paragraph.

Let's assume the following inputs to the module (sheet "reaction"):

ASOAF_s_EPBActrCtl_StAvl = VMMP_ASOAF_c_EPBActrCtl_StAvlReleaseOnly

ASOAF_s_DiagDrvPosn_StEveReq = VMMP_c_DiagEveSigFail

ASOAF_s_DiagEPBActrCtl_StEveReq = VMMP_c_DiagEveSigNotVld

So the active rows in this example are row 4, 8 and 13.
The default value

For each column, all cells, which have a value of "default", are equivalent to the state given by the column "default state" in sheet "statemachine".
Example:

* In sheet "reaction", row 8 - 11, column F the state "default" is equivalent to the state "On" (default state of state machine "Foo_Bi", see sheet "statemachine" column C)

* In sheet "reaction", row 8 - 11, column G the state "default" is equivalent to the state "On" (default state of state machine "Foo_Bob", see sheet "statemachine" column C)
Information for tester:

To increase code coverage the following parameter-value combination can be used:

VMMP_CRMFH_p_NumEveExA_XXX = 5

VMMP_CRMFH_p_NumEveFH_XXX = 5

VMMP_CRMFH_p1_StTarMtrxExA_XXX = [0 0 0 1 1 …]

VMMP_CRMFH_p1_StTarMtrxFH_XXX = [0 0 0 1 1 …]

VMMP_CRMFH_p1_MapEveExA_XXX = [0 0 1 1 1 …]

VMMP_CRMFH_p1_MapEveFH_XXX = [0 0 1 1 1 …]

VMMP_CRMFH_p1_StDgrdRsnFH_XXX = [0 0 0 0 1 …]

where XXX is the "name of the output" - see also 3.4.1

For some outputs the parameter VMMP_CRMFH_p1_StDgrdRsnFH_XXX is not existing. In this case the parameter can be ignored.

To get the correct output of the test coverage, it shall be assumed that the outputs defined in 3.4.1 shall be equal to 1.
When the following parameter-value combination can be used:to increase the code coverage, then the corresponding output. to the parameter which has been changed should have value "1

VMMP_CRMFH_p_NumEveExA_XXX = 5

VMMP_CRMFH_p_NumEveFH_XXX = 5

VMMP_CRMFH_p1_StTarMtrxExA_XXX = [0 0 0 1 1 …]

VMMP_CRMFH_p1_StTarMtrxFH_XXX = [0 0 0 1 1 …]

VMMP_CRMFH_p1_MapEveExA_XXX = [0 0 1 1 1 …]

VMMP_CRMFH_p1_MapEveFH_XXX = [0 0 1 1 1 …]

VMMP_CRMFH_p1_StDgrdRsnFH_XXX = [0 0 0 0 1 …]

where XXX is the "name of the output" - see also 3.4.1

For some outputs the parameter VMMP_CRMFH_p1_StDgrdRsnFH_XXX is not existing. In this case the parameter can be ignored.
Target States
Empty cell doesn't have any impact on the output. It should be ignored.
For each column starting with the first output signal and for each cell in this column:

IF [AND(1, 2)]:

1) The cell is part of an active row, that has a "signal type" of "diagevent"

2) The value of the cell has the highest target state priority of all the values within the column

THEN:

Output StTar FH is the value of the cell

ELSE:

Output StTar FH is "On"
Example:

In this example (see 1206782) row 8 and 13 are active rows, which have a "signal type" of "diagevent".

* For state machine "Foo_Bi" the output "CRMFH_s_Foo_StTarBiFH" is the value of "CRMSA_c_Foo_BiStTarOff". The active rows in column "Foo_Bi" have the states "Off" and "default" - which equals "On". 

 "Off" has a higher priority than "On" (see previous section "Target state priority"). Therefore the final state is "Off".

* For state machine "Fara" the output "CRMFH_s_Fara_StTarFH" is the value of "CRMSA_c_FaraStTarAvlNoBkp". The active rows in column "Fara" have the states "AvailableNoBackup" and "On". 

 "AvailableNoBackup" has a higher priority than "On" (see previous section "Target state priority"). Therefore the final state is "AvailableNoBackup".
For each column starting with the first output signal and for each cell in this column:

IF [AND(1, 2)]:

1) The cell is part of an active row, that has a "signal type" of "availability"

2) The value of the cell has the highest target state priority of all the values within the column

THEN:

Output StTar ExA is the value of the cell

ELSE:

Output StTar ExA is "On"
Example:

In this example row 4 is the only active row, which have a "signal type" of "availability". 

For state machine "Foo_Bi" the output "CRMFH_s_Foo_StTarBiExA" is the value of "CRMSA_c_Foo_BiStTarOff". The active row in column "Foo_Bi" has the state "Off". It is the single active row. Therefore the final state is "Off".
Degradation Reasons
Empty cell doesn't have any impact on the output. It shall be ignored.
The output DgrdRsn FH is only provided, if for the associated state machine "yes" is given in the column "use degradation reason" of the sheet "statemachine".
For each state machine, where 16662150 is true

IF [AND(1, 2, 3)]:

1) The value is part of an active row, that has a "signal type" of "diagevent"

2) The value is not the default value. This can either be the literal string "default" or the string given by the column "default state" in sheet "statemachine"

3) The value of the cell has the highest target state priority of all the values within the column

THEN:

Output DgrdRsn FH is the value of the cell in the column "degradation reason"

ELSE:

Output StTar DgrdRsn is the Degradation Reason "None" (i.e. value of VMMP_CRM_c_StDgrdRsnNone).
Example:

In this example (see 1206782) row 8 and 13 are active rows, which have a "signal type" of "diagevent".

The degradation reasons in active rows are therefore "Failure" and "None".

* For state machine "Foo_Bi" the output StTar DgrdRsn is "None". Row 8 has a "signal type" of diagevent, it is an active row, but for state machine "Foo_Bi" the default state is given. So one of the conditions is not satisfied. Row 13 on the other hand satisfies all conditions.

* Let's assume the following inputs to the module (sheet "reaction"): 

 ASOAF_s_DiagDrvPosn_StEveReq = VMMP_c_DiagEveSigIni 

 ASOAF_s_DiagEPBActrCtl_StEveReq = VMMP_c_DiagEveSigFail 

 So the active rows (sheet "reaction") in this example are row 11 and 12. 

 In this example, for state machine "BarLgtCtl" the output StTar DgrdRsn is "Failure". Both rows have a "signal type" of diagevent and are active rows. The value of the states ("Failure" and "Restricted" in this example) are both not the default state. So the final Degradation Reason is determined by the last of the conditions given above: the highest priority of the Degradation Reasons "Init" and "Failure" has the Degradation Reason "Failure".
Example:

In this example only Foo_Bi and Foo_Bob provide a degradation reason as its output, i.e. CRMFH_s_Foo_StDgrdRsnBiFH and CRMFH_s_Foo_StDgrdRsnBobFH.
Computation of cyclic event ID
The index of all diag events are based on the alphabetical order starting with id 1. The diag events are given by the signals listed in VMM_CRM_FunctionMatrix.xlsx in sheet 'reaction' in 'signal name' (column A), where 'signal type' (column D) equals 'diagevent'.
The cycle event id shall not be confused with the column "id" in VMM_CRM_FunctionMatrix.xlsx in sheet 'reaction' as both are unrelated to one another.
A diagnose event or diag event can take following values:

None: VMMP_c_DiagEveSigNone (meaning the diagnose event is valid and failure-free),

Disabled: VMMP_c_DiagEveSigDi,

NotValid: VMMP_c_DiagEveSigNotVld,

Failed: VMMP_c_DiagEveSigFail,

Init: VMMP_c_DiagEveSigIni, 

InitExceed: VMMP_c_DiagEveSigIniExc
IF[1]

1) all DiagEvents have the value VMMP_c_DiagEveSigNone or VMMP_c_DiagEveSigDi 

THEN 

Output CRMFH_s_CycDiagEveId is 0.

ELSE 

Output CRMFH_s_CycDiagEveId is the index of the next active diag event.
An active diag event is a diag event, which has neither the value VMMP_c_DiagEveSigNone nor the value VMMP_c_DiagEveSigDi.

* The next active diag event is the active diag event, that comes after the diag event, which was found in a previous time step.

For the first iteration starting at index 1.

If all diag events have been iterated, start at the first diag event again.

If no active diag event was found for one or more cycles, the iteration does continue at the index of the last found active diag event.

Over time all active diag events are iterated.
Example:

For VMM_CRM_FunctionMatrix_Example.xlsx the diag events are ASOAF_s_DiagDrvPosn_StEveReq with index 1 and ASOAF_s_DiagEPBActrCtl_StEveReq with index 2.

Let's assume that each of those events can take the value (VMMP_c_DiagEveSigFail or VMMP_c_DiagEveSigNone or VMMP_c_DiagEveSigNotVld) at different timesteps as shown in the following table.

Empty attachment [_74e1c623-8a20-4178-a2ff-b237e84cf693_2_1.png]

The expected result for this example at the timesteps 0s - 0.08s is:

0.00s: 1 (both diag events are active; so the output toggles between 1 and 2)

0.01s: 2

0.02s: 1

0.03s: 0 (no diag event is active)

0.04s: 0

0.05s: 2 (again both diag events are active)

0.06s: 1

0.07s: 2

0.08s: 1 (only the first diag event is active)

0.09s: 1

Row	ID	Type	Status	Relevant	Candidate	Reason	Normalized text
2	16662095.0	Folder		no	False	type_not_target, status_filtered, relevance_filtered	Short description Short description Raw { "ID": "16662095.0", "ASIL": " ", "Text": "Short description", "Type": "Folder", "Status": "", "Summary": "Short description", "Relevant": "no", "column_12": "", "Foreign ID": "1127617.0", "Description": "", "Vehicle Launch": "", "Vehicle Platform": "E³ 1.2" }
3	16662096.0	Information		no	False	type_not_target, status_filtered, relevance_filtered	The Module CRMFH (Central Release Management Failure Handler) is a submodule of CRM. The CRM sub-function "FailureHandler" links The Module CRMFH (Central Release Management Failure Handler) is a submodule of CRM. The CRM sub-function "FailureHandler" links the active diagnostic events with the target states of the VMM sub-functions via a matrix. This means that for each diagnostic event, the matrix indicates the target states in which the state machines of the sub-functions are to be set as soon as this diagnostic event occurs. The CRM sub-function "FailureHandler" links the active diagnostic events with the diagnostic causes of the VMM sub-functions via a matrix. This means that the matrix specifies for each diagnostic event which diagnostic cause is to be made available for the respective state machine of the sub-functions as soon as this diagnostic event occurs. Raw { "ID": "16662096.0", "ASIL": " ", "Text": "The Module CRMFH (Central Release Management Failure Handler) is a submodule of CRM.\n\rThe CRM sub-function \"FailureHandler\" links the active diagnostic events with the target states of the VMM sub-functions via a matrix. This means that for each diagnostic event, the matrix indicates the target states in which the state machines of the sub-functions are to be set as soon as this diagnostic event occurs. \n\r \n\rThe CRM sub-function \"FailureHandler\" links the active diagnostic events with the diagnostic causes of the VMM sub-functions via a matrix. This means that the matrix specifies for each diagnostic event which diagnostic cause is to be made available for the respective state machine of the sub-functions as soon as this diagnostic event occurs.", "Type": "Information", "Status": "", "Summary": "", "Relevant": "no", "column_12": "", "Foreign ID": "1127622.0", "Description": "The Module CRMFH (Central Release Management Failure Handler) is a submodule of CRM.\n\rThe CRM sub-function \"FailureHandler\" links the active diagnostic events with the target states of the VMM sub-functions via a matrix. This means that for each diagnostic event, the matrix indicates the target states in which the state machines of the sub-functions are to be set as soon as this diagnostic event occurs. \n\r \n\rThe CRM sub-function \"FailureHandler\" links the active diagnostic events with the diagnostic causes of the VMM sub-functions via a matrix. This means that the matrix specifies for each diagnostic event which diagnostic cause is to be made available for the respective state machine of the sub-functions as soon as this diagnostic event occurs.", "Vehicle Launch": "", "Vehicle Platform": "E³ 1.2" }
4	16662097.0	Folder		no	False	type_not_target, status_filtered, relevance_filtered	Interface description Interface description Raw { "ID": "16662097.0", "ASIL": " ", "Text": "Interface description", "Type": "Folder", "Status": "", "Summary": "Interface description", "Relevant": "no", "column_12": "", "Foreign ID": "1207379.0", "Description": "", "Vehicle Launch": "", "Vehicle Platform": "E³ 1.2" }
5	16662098.0	Information		no	False	type_not_target, status_filtered, relevance_filtered	The valid version of the signal and parameter files for the relevant SWRS are: The valid version of the signal and parameter files for the relevant SWRS are: Raw { "ID": "16662098.0", "ASIL": " ", "Text": "The valid version of the signal and parameter files for the relevant SWRS are:", "Type": "Information", "Status": "", "Summary": "", "Relevant": "no", "column_12": "", "Foreign ID": "1207378.0", "Description": "The valid version of the signal and parameter files for the relevant SWRS are:", "Vehicle Launch": "", "Vehicle Platform": "E³ 1.2" }
6	16662099.0	Information		no	False	type_not_target, status_filtered, relevance_filtered, empty_target_text	Raw { "ID": "16662099.0", "ASIL": " ", "Text": "No InterWiki reference defined in properties for 'integrity'", "Type": "Information", "Status": "", "Summary": "", "Relevant": "no", "column_12": "", "Foreign ID": "1207377.0", "Description": "No InterWiki reference defined in properties for 'integrity'", "Vehicle Launch": "", "Vehicle Platform": "E³ 1.2" }
7	16662100.0	Information		no	False	type_not_target, status_filtered, relevance_filtered, empty_target_text	Raw { "ID": "16662100.0", "ASIL": " ", "Text": "No InterWiki reference defined in properties for 'integrity'", "Type": "Information", "Status": "", "Summary": "", "Relevant": "no", "column_12": "", "Foreign ID": "1207376.0", "Description": "No InterWiki reference defined in properties for 'integrity'", "Vehicle Launch": "", "Vehicle Platform": "E³ 1.2" }
8	16662101.0	Folder		no	False	type_not_target, status_filtered, relevance_filtered	Presetting/Framework/Definitions Presetting/Framework/Definitions Raw { "ID": "16662101.0", "ASIL": " ", "Text": "Presetting/Framework/Definitions", "Type": "Folder", "Status": "", "Summary": "Presetting/Framework/Definitions", "Relevant": "no", "column_12": "", "Foreign ID": "1127619.0", "Description": "", "Vehicle Launch": "", "Vehicle Platform": "E³ 1.2" }
9	16662102.0	Folder		no	False	type_not_target, status_filtered, relevance_filtered	Traceability Traceability Raw { "ID": "16662102.0", "ASIL": " ", "Text": "Traceability", "Type": "Folder", "Status": "", "Summary": "Traceability", "Relevant": "no", "column_12": "", "Foreign ID": "1308694.0", "Description": "", "Vehicle Launch": "", "Vehicle Platform": "E³ 1.2" }
10	16662103.0	Information		no	False	type_not_target, status_filtered, relevance_filtered	SWRS to Testcase: The latest revision of the test specification document is valid for the tracability SWRS to Testcase SWRS to Testcase: The latest revision of the test specification document is valid for the tracability SWRS to Testcase Raw { "ID": "16662103.0", "ASIL": " ", "Text": "SWRS to Testcase:\n\rNo InterWiki reference defined in properties for 'integrity'\n\rThe latest revision of the test specification document is valid for the tracability SWRS to Testcase", "Type": "Information", "Status": "", "Summary": "", "Relevant": "no", "column_12": "", "Foreign ID": "1308696.0", "Description": "SWRS to Testcase:\n\rNo InterWiki reference defined in properties for 'integrity'\n\rThe latest revision of the test specification document is valid for the tracability SWRS to Testcase", "Vehicle Launch": "", "Vehicle Platform": "E³ 1.2" }
11	16662104.0	Information		no	False	type_not_target, status_filtered, relevance_filtered	SWRS to CodeBeamer: CodeBeamer-IDs are mentioned in the SWRS atrribute DOORS IDs. The latest baseline of the specification docu SWRS to CodeBeamer: CodeBeamer-IDs are mentioned in the SWRS atrribute DOORS IDs. The latest baseline of the specification document (CodeBeamer) is valid for the traceability SWRS to CodeBeamer. Raw { "ID": "16662104.0", "ASIL": " ", "Text": "SWRS to CodeBeamer: \n\rCodeBeamer-IDs are mentioned in the SWRS atrribute DOORS IDs.\n\rThe latest baseline of the specification document (CodeBeamer) is valid for the traceability SWRS to CodeBeamer.", "Type": "Information", "Status": "", "Summary": "", "Relevant": "no", "column_12": "", "Foreign ID": "1308698.0", "Description": "SWRS to CodeBeamer: \n\rCodeBeamer-IDs are mentioned in the SWRS atrribute DOORS IDs.\n\rThe latest baseline of the specification document (CodeBeamer) is valid for the traceability SWRS to CodeBeamer.", "Vehicle Launch": "", "Vehicle Platform": "E³ 1.2" }
12	16662105.0	Folder		no	False	type_not_target, status_filtered, relevance_filtered	Toolchain Toolchain Raw { "ID": "16662105.0", "ASIL": " ", "Text": "Toolchain", "Type": "Folder", "Status": "", "Summary": "Toolchain", "Relevant": "no", "column_12": "", "Foreign ID": "1228398.0", "Description": "", "Vehicle Launch": "", "Vehicle Platform": "E³ 1.2" }
13	16662106.0	Non-functional	Released	no	False	type_not_target, relevance_filtered	The Matlab/Simulink/TargetLink versions have to be used according to the HCP1-Toolchain. The Matlab/Simulink/TargetLink versions have to be used according to the HCP1-Toolchain. Raw { "ID": "16662106.0", "ASIL": " QM", "Text": "The Matlab/Simulink/TargetLink versions have to be used according to the HCP1-Toolchain.", "Type": "Non-functional", "Status": "Released", "Summary": "", "Relevant": "no", "column_12": "", "Foreign ID": "1228399.0", "Description": "The Matlab/Simulink/TargetLink versions have to be used according to the HCP1-Toolchain.", "Vehicle Launch": "", "Vehicle Platform": "E³ 1.2" }
14	16662107.0	Non-functional	Released	no	False	type_not_target, relevance_filtered	For modeling in Simulink the valid EnProVe catalogue of guidelines has to be used. For modeling in Simulink the valid EnProVe catalogue of guidelines has to be used. Raw { "ID": "16662107.0", "ASIL": " QM", "Text": "For modeling in Simulink the valid EnProVe catalogue of guidelines has to be used.", "Type": "Non-functional", "Status": "Released", "Summary": "", "Relevant": "no", "column_12": "", "Foreign ID": "1228397.0", "Description": "For modeling in Simulink the valid EnProVe catalogue of guidelines has to be used.", "Vehicle Launch": "", "Vehicle Platform": "E³ 1.2" }
15	16662108.0	Folder		no	False	type_not_target, status_filtered, relevance_filtered	Tolerances Tolerances Raw { "ID": "16662108.0", "ASIL": " ", "Text": "Tolerances", "Type": "Folder", "Status": "", "Summary": "Tolerances", "Relevant": "no", "column_12": "", "Foreign ID": "1127625.0", "Description": "", "Vehicle Launch": "", "Vehicle Platform": "E³ 1.2" }
16	16662109.0	Non-functional	Released	no	False	type_not_target, relevance_filtered	For the comparison of output signals to the expected reactions or by back-to-back tests (MiL-PiL) following tolerances are accepte For the comparison of output signals to the expected reactions or by back-to-back tests (MiL-PiL) following tolerances are accepted for deviations: Raw { "ID": "16662109.0", "ASIL": " QM", "Text": "For the comparison of output signals to the expected reactions or by back-to-back tests (MiL-PiL) following tolerances are accepted for deviations:", "Type": "Non-functional", "Status": "Released", "Summary": "", "Relevant": "no", "column_12": "", "Foreign ID": "1127634.0", "Description": "For the comparison of output signals to the expected reactions or by back-to-back tests (MiL-PiL) following tolerances are accepted for deviations:", "Vehicle Launch": "", "Vehicle Platform": "E³ 1.2" }
17	16662110.0	Non-functional	Released	no	False	type_not_target, relevance_filtered	Bool: No deviation allowed Bool: No deviation allowed Raw { "ID": "16662110.0", "ASIL": " QM", "Text": "\n\r \n\r Bool: No deviation allowed", "Type": "Non-functional", "Status": "Released", "Summary": "", "Relevant": "no", "column_12": "", "Foreign ID": "1129101.0", "Description": "\n\r \n\r Bool: No deviation allowed", "Vehicle Launch": "", "Vehicle Platform": "E³ 1.2" }
18	16662111.0	Non-functional	Released	no	False	type_not_target, relevance_filtered	UInt, Int: No deviation allowed UInt, Int: No deviation allowed Raw { "ID": "16662111.0", "ASIL": " QM", "Text": "\n\r \n\r UInt, Int: No deviation allowed", "Type": "Non-functional", "Status": "Released", "Summary": "", "Relevant": "no", "column_12": "", "Foreign ID": "1129103.0", "Description": "\n\r \n\r UInt, Int: No deviation allowed", "Vehicle Launch": "", "Vehicle Platform": "E³ 1.2" }
19	16662112.0	Non-functional	Released	no	False	type_not_target, relevance_filtered	Float: 0.1% related to the permissible value range of the signal Float: 0.1% related to the permissible value range of the signal Raw { "ID": "16662112.0", "ASIL": " QM", "Text": "\n\r \n\r Float: 0.1% related to the permissible value range of the signal", "Type": "Non-functional", "Status": "Released", "Summary": "", "Relevant": "no", "column_12": "", "Foreign ID": "1129113.0", "Description": "\n\r \n\r Float: 0.1% related to the permissible value range of the signal", "Vehicle Launch": "", "Vehicle Platform": "E³ 1.2" }
20	16662113.0	Folder		no	False	type_not_target, status_filtered, relevance_filtered	Bit numbering Bit numbering Raw { "ID": "16662113.0", "ASIL": " ", "Text": "Bit numbering", "Type": "Folder", "Status": "", "Summary": "Bit numbering", "Relevant": "no", "column_12": "", "Foreign ID": "1253702.0", "Description": "", "Vehicle Launch": "", "Vehicle Platform": "E³ 1.2" }
21	16662114.0	Non-functional	Released	no	False	type_not_target, relevance_filtered	The bit numbering takes place as zero-based numbering method. This means, 1 Byte is equal to Bit 0...7. The bit numbering takes place as zero-based numbering method. This means, 1 Byte is equal to Bit 0...7. Raw { "ID": "16662114.0", "ASIL": " QM", "Text": "The bit numbering takes place as zero-based numbering method. \n\rThis means, 1 Byte is equal to Bit 0...7.", "Type": "Non-functional", "Status": "Released", "Summary": "", "Relevant": "no", "column_12": "", "Foreign ID": "1253703.0", "Description": "The bit numbering takes place as zero-based numbering method. \n\rThis means, 1 Byte is equal to Bit 0...7.", "Vehicle Launch": "", "Vehicle Platform": "E³ 1.2" }
22	16662115.0	Folder		no	False	type_not_target, status_filtered, relevance_filtered	Requirements Requirements Raw { "ID": "16662115.0", "ASIL": " ", "Text": "Requirements", "Type": "Folder", "Status": "", "Summary": "Requirements", "Relevant": "no", "column_12": "", "Foreign ID": "1127621.0", "Description": "", "Vehicle Launch": "", "Vehicle Platform": "E³ 1.2" }
23	16662116.0	Information		no	False	type_not_target, status_filtered, relevance_filtered	For all requirements (except "examples"), an excel table with the name "VMM_CRM_FunctionMatrix.xlsx" is provided (see Modul SWRS_V For all requirements (except "examples"), an excel table with the name "VMM_CRM_FunctionMatrix.xlsx" is provided (see Modul SWRS_VMMP chapter "Central Release Management") It shall be used for the test implementations. Raw { "ID": "16662116.0", "ASIL": " ", "Text": "For all requirements (except \"examples\"), an excel table with the name \"VMM_CRM_FunctionMatrix.xlsx\" is provided (see Modul SWRS_VMMP chapter \"Central Release Management\") \n\rIt shall be used for the test implementations.", "Type": "Information", "Status": "", "Summary": "", "Relevant": "no", "column_12": "", "Foreign ID": "1210253.0", "Description": "For all requirements (except \"examples\"), an excel table with the name \"VMM_CRM_FunctionMatrix.xlsx\" is provided (see Modul SWRS_VMMP chapter \"Central Release Management\") \n\rIt shall be used for the test implementations.", "Vehicle Launch": "", "Vehicle Platform": "E³ 1.2" }
24	16662117.0	Information		no	False	type_not_target, status_filtered, relevance_filtered	For all examples, an excel table with the name "VMM_CRM_FunctionMatrix_Example.xlsx" is provided ), which is used as the data bas For all examples, an excel table with the name "VMM_CRM_FunctionMatrix_Example.xlsx" is provided ), which is used as the data basis. The examples don't refer to the real excel table so the examples remain valid even when the real excel table is changed. The general structure of the example excel table and the real excel table are of course the same. Raw { "ID": "16662117.0", "ASIL": " ", "Text": "For all examples, an excel table with the name \"VMM_CRM_FunctionMatrix_Example.xlsx\" is provided (No InterWiki reference defined in properties for 'integrity' ), which is used as the data basis.\n\rThe examples don't refer to the real excel table so the examples remain valid even when the real excel table is changed.\n\rThe general structure of the example excel table and the real excel table are of course the same.", "Type": "Information", "Status": "", "Summary": "", "Relevant": "no", "column_12": "", "Foreign ID": "1207426.0", "Description": "For all examples, an excel table with the name \"VMM_CRM_FunctionMatrix_Example.xlsx\" is provided (No InterWiki reference defined in properties for 'integrity' ), which is used as the data basis.\n\rThe examples don't refer to the real excel table so the examples remain valid even when the real excel table is changed.\n\rThe general structure of the example excel table and the real excel table are of course the same.", "Vehicle Launch": "", "Vehicle Platform": "E³ 1.2" }
25	16662118.0	Folder		no	False	type_not_target, status_filtered, relevance_filtered	Definition and naming conventions Definition and naming conventions Raw { "ID": "16662118.0", "ASIL": " ", "Text": "Definition and naming conventions", "Type": "Folder", "Status": "", "Summary": "Definition and naming conventions", "Relevant": "no", "column_12": "", "Foreign ID": "1207424.0", "Description": "", "Vehicle Launch": "", "Vehicle Platform": "E³ 1.2" }
26	16662119.0	Information		no	False	type_not_target, status_filtered, relevance_filtered	The following naming conventions will be used: * Sheet refers to one of the sheets of the excel table, i.e. the sheets "dtc", "re The following naming conventions will be used: * Sheet refers to one of the sheets of the excel table, i.e. the sheets "dtc", "reaction" and "statemachine". * Row, column and cell are used with regard to the excel table * Target state and degradation reason are used with regard to the module. These are outputs of the CRM modules. Raw { "ID": "16662119.0", "ASIL": " ", "Text": "The following naming conventions will be used:\n\r* Sheet refers to one of the sheets of the excel table, i.e. the sheets \"dtc\", \"reaction\" and \"statemachine\". \n\r* Row, column and cell are used with regard to the excel table \n\r* Target state and degradation reason are used with regard to the module. These are outputs of the CRM modules.", "Type": "Information", "Status": "", "Summary": "", "Relevant": "no", "column_12": "", "Foreign ID": "1207423.0", "Description": "The following naming conventions will be used:\n\r* Sheet refers to one of the sheets of the excel table, i.e. the sheets \"dtc\", \"reaction\" and \"statemachine\". \n\r* Row, column and cell are used with regard to the excel table \n\r* Target state and degradation reason are used with regard to the module. These are outputs of the CRM modules.", "Vehicle Launch": "", "Vehicle Platform": "E³ 1.2" }
27	16662120.0	Information		no	False	type_not_target, status_filtered, relevance_filtered	Active row A row of a sheet is called active row, if the input of the module with the name given by the column "signal name" has Active row A row of a sheet is called active row, if the input of the module with the name given by the column "signal name" has the value given by the column "signal constant" Example: Let's assume the following inputs to the module: * ASOAF_s_DiagDrvPosn_StEveReq = VMMP_c_DiagEveSigIni * ASOAF_s_EPBActrCtl_StAvl = VMMP_ASOAF_c_EPBActrCtl_StAvlReleaseOnly In this example the only active row of the sheet "dtc" is row 7. The active rows of sheet "reaction" are row 4 and row 11. Raw { "ID": "16662120.0", "ASIL": " ", "Text": "Active row \n\rA row of a sheet is called active row, if the input of the module with the name given by the column \"signal name\" has the value given by the column \"signal constant\"\n\rExample:\n\rLet's assume the following inputs to the module:\n\r* ASOAF_s_DiagDrvPosn_StEveReq = VMMP_c_DiagEveSigIni\n\r* ASOAF_s_EPBActrCtl_StAvl = VMMP_ASOAF_c_EPBActrCtl_StAvlReleaseOnly\n\rIn this example the only active row of the sheet \"dtc\" is row 7.\n\rThe active rows of sheet \"reaction\" are row 4 and row 11.", "Type": "Information", "Status": "", "Summary": "", "Relevant": "no", "column_12": "", "Foreign ID": "1323236.0", "Description": "Active row \n\rA row of a sheet is called active row, if the input of the module with the name given by the column \"signal name\" has the value given by the column \"signal constant\"\n\rExample:\n\rLet's assume the following inputs to the module:\n\r* ASOAF_s_DiagDrvPosn_StEveReq = VMMP_c_DiagEveSigIni\n\r* ASOAF_s_EPBActrCtl_StAvl = VMMP_ASOAF_c_EPBActrCtl_StAvlReleaseOnly\n\rIn this example the only active row of the sheet \"dtc\" is row 7.\n\rThe active rows of sheet \"reaction\" are row 4 and row 11.", "Vehicle Launch": "", "Vehicle Platform": "E³ 1.2" }
28	16662121.0	Information		no	False	type_not_target, status_filtered, relevance_filtered	The column with the name "use" in the sheet "reaction" indicates if a given signal is relevant or not for the computation. If a ce The column with the name "use" in the sheet "reaction" indicates if a given signal is relevant or not for the computation. If a cell in this column "use" is empty, then the entire corresponding row shouldn't be considered for computation purposes. Raw { "ID": "16662121.0", "ASIL": " ", "Text": "The column with the name \"use\" in the sheet \"reaction\" indicates if a given signal is relevant or not for the computation. If a cell in this column \"use\" is empty, then the entire corresponding row shouldn't be considered for computation purposes.", "Type": "Information", "Status": "", "Summary": "", "Relevant": "no", "column_12": "", "Foreign ID": "1381355.0", "Description": "The column with the name \"use\" in the sheet \"reaction\" indicates if a given signal is relevant or not for the computation. If a cell in this column \"use\" is empty, then the entire corresponding row shouldn't be considered for computation purposes.", "Vehicle Launch": "", "Vehicle Platform": "E³ 1.2" }
29	16662122.0	Folder		no	False	type_not_target, status_filtered, relevance_filtered	Output names Output names Raw { "ID": "16662122.0", "ASIL": " ", "Text": "Output names", "Type": "Folder", "Status": "", "Summary": "Output names", "Relevant": "no", "column_12": "", "Foreign ID": "1206746.0", "Description": "", "Vehicle Launch": "", "Vehicle Platform": "E³ 1.2" }
30	16662123.0	Information		no	False	type_not_target, status_filtered, relevance_filtered	The name of the output depends on the name of the column itself: If the name of the column contains at least one underscore "___" The name of the output depends on the name of the column itself: If the name of the column contains at least one underscore "___", then * Name of StTar FH is CRMFH_s___{column name part 1}_StTar{column name part 2}FH * Name of DgrdRsn FH is CRMFH_s___{column name part 1}_StDgrdRsn{column name part 2}FH * Name of StTar ExA is CRMFH_s___{column name part 1}_StTar{column name part 2}ExA where {column name part 1} is everything of the name of the column up to the first underscore "___" and where {column name part 2} is everything of the name of the column col after the first underscore "_" Otherwise: * Name of StTar FH is CRMFH_s___{column name}_StTarFH * Name of DgrdRsn FH is CRMFH_s___{column name}_StDgrdRsnFH * Name of StTar ExA is CRMFH_s___{column name}_StTarExA where {column name} is the name of the column Raw { "ID": "16662123.0", "ASIL": " ", "Text": "The name of the output depends on the name of the column itself:\n\rIf the name of the column contains at least one underscore \"___\", then\n\r* Name of StTar FH is CRMFH_s___{column name part 1}_StTar{column name part 2}FH\n\r* Name of DgrdRsn FH is CRMFH_s___{column name part 1}_StDgrdRsn{column name part 2}FH\n\r* Name of StTar ExA is CRMFH_s___{column name part 1}_StTar{column name part 2}ExA\n\rwhere {column name part 1} is everything of the name of the column up to the first underscore \"___\" \n\rand where {column name part 2} is everything of the name of the column col after the first underscore \"_\"\n\rOtherwise:\n\r* Name of StTar FH is CRMFH_s___{column name}_StTarFH\n\r* Name of DgrdRsn FH is CRMFH_s___{column name}_StDgrdRsnFH\n\r* Name of StTar ExA is CRMFH_s___{column name}_StTarExA\n\rwhere {column name} is the name of the column", "Type": "Information", "Status": "", "Summary": "", "Relevant": "no", "column_12": "", "Foreign ID": "1206760.0", "Description": "The name of the output depends on the name of the column itself:\n\rIf the name of the column contains at least one underscore \"___\", then\n\r* Name of StTar FH is CRMFH_s___{column name part 1}_StTar{column name part 2}FH\n\r* Name of DgrdRsn FH is CRMFH_s___{column name part 1}_StDgrdRsn{column name part 2}FH\n\r* Name of StTar ExA is CRMFH_s___{column name part 1}_StTar{column name part 2}ExA\n\rwhere {column name part 1} is everything of the name of the column up to the first underscore \"___\" \n\rand where {column name part 2} is everything of the name of the column col after the first underscore \"_\"\n\rOtherwise:\n\r* Name of StTar FH is CRMFH_s___{column name}_StTarFH\n\r* Name of DgrdRsn FH is CRMFH_s___{column name}_StDgrdRsnFH\n\r* Name of StTar ExA is CRMFH_s___{column name}_StTarExA\n\rwhere {column name} is the name of the column", "Vehicle Launch": "", "Vehicle Platform": "E³ 1.2" }
31	16662124.0	Information		no	False	type_not_target, status_filtered, relevance_filtered	Example: The outputs for the example are: * "CRMFH_s_Foo_StTarBiFH", "CRMFH_s_Foo_StDgrdRsnBiFH" and "CRMFH_s_Foo_StTarBiExA" fo Example: The outputs for the example are: * "CRMFH_s_Foo_StTarBiFH", "CRMFH_s_Foo_StDgrdRsnBiFH" and "CRMFH_s_Foo_StTarBiExA" for state machine "Foo_Bi" * "CRMFH_s_Foo_StTarBobFH", "CRMFH_s_Foo_StDgrdRsnBobFH" and "CRMFH_s_Foo_StTarBobExA" for state machine "Foo_Bob" * "CRMFH_s_Fara_StTarFH" and "CRMFH_s_Fara_StTarExA" for state machine "Fara" * "CRMFH_s_BarLgtCtl_StTarFH" and "CRMFH_s_BarLgtCtl_StTarExA" for state machine "BarLgtCtl" * "CRMFH_s_BarLatCtl_StTarFH" and "CRMFH_s_BarLatCtl_StTarExA" for state machine "BarLatCtl" Raw { "ID": "16662124.0", "ASIL": " ", "Text": "Example:\n\rThe outputs for the example are:\n\r* \"CRMFH_s_Foo_StTarBiFH\", \"CRMFH_s_Foo_StDgrdRsnBiFH\" and \"CRMFH_s_Foo_StTarBiExA\" for state machine \"Foo_Bi\"\n\r* \"CRMFH_s_Foo_StTarBobFH\", \"CRMFH_s_Foo_StDgrdRsnBobFH\" and \"CRMFH_s_Foo_StTarBobExA\" for state machine \"Foo_Bob\"\n\r* \"CRMFH_s_Fara_StTarFH\" and \"CRMFH_s_Fara_StTarExA\" for state machine \"Fara\"\n\r* \"CRMFH_s_BarLgtCtl_StTarFH\" and \"CRMFH_s_BarLgtCtl_StTarExA\" for state machine \"BarLgtCtl\"\n\r* \"CRMFH_s_BarLatCtl_StTarFH\" and \"CRMFH_s_BarLatCtl_StTarExA\" for state machine \"BarLatCtl\"", "Type": "Information", "Status": "", "Summary": "", "Relevant": "no", "column_12": "", "Foreign ID": "1206764.0", "Description": "Example:\n\rThe outputs for the example are:\n\r* \"CRMFH_s_Foo_StTarBiFH\", \"CRMFH_s_Foo_StDgrdRsnBiFH\" and \"CRMFH_s_Foo_StTarBiExA\" for state machine \"Foo_Bi\"\n\r* \"CRMFH_s_Foo_StTarBobFH\", \"CRMFH_s_Foo_StDgrdRsnBobFH\" and \"CRMFH_s_Foo_StTarBobExA\" for state machine \"Foo_Bob\"\n\r* \"CRMFH_s_Fara_StTarFH\" and \"CRMFH_s_Fara_StTarExA\" for state machine \"Fara\"\n\r* \"CRMFH_s_BarLgtCtl_StTarFH\" and \"CRMFH_s_BarLgtCtl_StTarExA\" for state machine \"BarLgtCtl\"\n\r* \"CRMFH_s_BarLatCtl_StTarFH\" and \"CRMFH_s_BarLatCtl_StTarExA\" for state machine \"BarLatCtl\"", "Vehicle Launch": "", "Vehicle Platform": "E³ 1.2" }
32	16662125.0	Information		no	False	type_not_target, status_filtered, relevance_filtered	Each column- starting with column F - of the sheet "reaction" describes the following outputs of the module, which are described i Each column- starting with column F - of the sheet "reaction" describes the following outputs of the module, which are described in detail in chapter "Outputs" below: * Target state provided by failure handler - in the following named StTar FH * Degradation reason provided by failure handler - in the following named DgrdRsn FH; this output does not always exists, see section "Outputs" for more details * Target state provided by external availabilities handler - in the following named StTar ExA Raw { "ID": "16662125.0", "ASIL": " ", "Text": "Each column- starting with column F - of the sheet \"reaction\" describes the following outputs of the module, which are described in detail in chapter \"Outputs\" below:\n\r* Target state provided by failure handler - in the following named StTar FH\n\r* Degradation reason provided by failure handler - in the following named DgrdRsn FH; this output does not always exists, see section \"Outputs\" for more details\n\r* Target state provided by external availabilities handler - in the following named StTar ExA", "Type": "Information", "Status": "", "Summary": "", "Relevant": "no", "column_12": "", "Foreign ID": "1206756.0", "Description": "Each column- starting with column F - of the sheet \"reaction\" describes the following outputs of the module, which are described in detail in chapter \"Outputs\" below:\n\r* Target state provided by failure handler - in the following named StTar FH\n\r* Degradation reason provided by failure handler - in the following named DgrdRsn FH; this output does not always exists, see section \"Outputs\" for more details\n\r* Target state provided by external availabilities handler - in the following named StTar ExA", "Vehicle Launch": "", "Vehicle Platform": "E³ 1.2" }
33	16662126.0	Folder		no	False	type_not_target, status_filtered, relevance_filtered	Target state priority Target state priority Raw { "ID": "16662126.0", "ASIL": " ", "Text": "Target state priority", "Type": "Folder", "Status": "", "Summary": "Target state priority", "Relevant": "no", "column_12": "", "Foreign ID": "1206750.0", "Description": "", "Vehicle Launch": "", "Vehicle Platform": "E³ 1.2" }
34	16662127.0	Information		no	False	type_not_target, status_filtered, relevance_filtered	The state machines are given by the sheet "statemachine" in column "state machine name" . The state machines are given by the sheet "statemachine" in column "state machine name" . Raw { "ID": "16662127.0", "ASIL": " ", "Text": "The state machines are given by the sheet \"statemachine\" in column \"state machine name\" .", "Type": "Information", "Status": "", "Summary": "", "Relevant": "no", "column_12": "", "Foreign ID": "1206768.0", "Description": "The state machines are given by the sheet \"statemachine\" in column \"state machine name\" .", "Vehicle Launch": "", "Vehicle Platform": "E³ 1.2" }
35	16662129.0	Pre Condition	Released	no	False	type_not_target, relevance_filtered	Highest target state priority For each state machine, the prioritization shall be done using the sheet order according to the ta Highest target state priority For each state machine, the prioritization shall be done using the sheet order according to the target state priorities given by the sheet "statemachine" in column "states (long name)" Raw { "ID": "16662129.0", "ASIL": " ASIL D", "Text": "Highest target state priority \n\rFor each state machine, the prioritization shall be done using the sheet order according to the target state priorities given by the sheet \"statemachine\" in column \"states (long name)\"", "Type": "Pre Condition", "Status": "Released", "Summary": "", "Relevant": "no", "column_12": "", "Foreign ID": "1206770.0", "Description": "Highest target state priority \n\rFor each state machine, the prioritization shall be done using the sheet order according to the target state priorities given by the sheet \"statemachine\" in column \"states (long name)\"", "Vehicle Launch": "", "Vehicle Platform": "E³ 1.2" }
36	16662130.0	Information		no	False	type_not_target, status_filtered, relevance_filtered	Examples: * The state machine "Foo_Bi" has two target states "Off" and "On". "Off" has the higher priority, because in the list i Examples: * The state machine "Foo_Bi" has two target states "Off" and "On". "Off" has the higher priority, because in the list it is above "On". * The state machine "BarLgtCtl" has five states. The priorities are from high to low as follows: "Off", "Failure", "Restricted", "NotAvailable", "On". This is because in the list "Off" is above "Failure", "Failure" is above "Restricted" and so on. * For the statemachine BarLgtCtl and its output CRMSA_s_BarLgtCtl_StTar the following table shows some example of possible permutations: Empty attachment [_ae85b99a-baf9-47aa-bd9d-d0bda1ef6b49_2_1.png] Raw { "ID": "16662130.0", "ASIL": " ", "Text": "Examples:\n\r* The state machine \"Foo_Bi\" has two target states \"Off\" and \"On\". \"Off\" has the higher priority, because in the list it is above \"On\".\n\r* The state machine \"BarLgtCtl\" has five states. The priorities are from high to low as follows: \"Off\", \"Failure\", \"Restricted\", \"NotAvailable\", \"On\". This is because in the list \"Off\" is above \"Failure\", \"Failure\" is above \"Restricted\" and so on.\n\r* For the statemachine BarLgtCtl and its output CRMSA_s_BarLgtCtl_StTar the following table shows some example of possible permutations:\n\r Empty attachment [_ae85b99a-baf9-47aa-bd9d-d0bda1ef6b49_2_1.png]", "Type": "Information", "Status": "", "Summary": "", "Relevant": "no", "column_12": "", "Foreign ID": "1206772.0", "Description": "Examples:\n\r* The state machine \"Foo_Bi\" has two target states \"Off\" and \"On\". \"Off\" has the higher priority, because in the list it is above \"On\".\n\r* The state machine \"BarLgtCtl\" has five states. The priorities are from high to low as follows: \"Off\", \"Failure\", \"Restricted\", \"NotAvailable\", \"On\". This is because in the list \"Off\" is above \"Failure\", \"Failure\" is above \"Restricted\" and so on.\n\r* For the statemachine BarLgtCtl and its output CRMSA_s_BarLgtCtl_StTar the following table shows some example of possible permutations:\n\r Empty attachment [_ae85b99a-baf9-47aa-bd9d-d0bda1ef6b49_2_1.png]", "Vehicle Launch": "", "Vehicle Platform": "E³ 1.2" }
37	16662131.0	Information		no	False	type_not_target, status_filtered, relevance_filtered	The SPE constant name for each target state, i.e. column "states (long name)" of sheet "statemachine" is as follows: * CRMSA_c___ The SPE constant name for each target state, i.e. column "states (long name)" of sheet "statemachine" is as follows: * CRMSA_c___{state machine}StTar{state}, if the group name given by column "group name" is empty * CRMSA_c___{group name}StTar{state}, otherwise Where * {state machine} is the name of the state machine given by column "state machine name" of sheet "statemachine" * {group name} is the name of the group given by column "group name" of sheet "statemachine" * {state} is the name of the state given by column "states (short name)" of sheet "statemachine" Raw { "ID": "16662131.0", "ASIL": " ", "Text": "The SPE constant name for each target state, i.e. column \"states (long name)\" of sheet \"statemachine\" is as follows:\n\r* CRMSA_c___{state machine}StTar{state}, if the group name given by column \"group name\" is empty\n\r* CRMSA_c___{group name}StTar{state}, otherwise\n\rWhere\n\r* {state machine} is the name of the state machine given by column \"state machine name\" of sheet \"statemachine\"\n\r* {group name} is the name of the group given by column \"group name\" of sheet \"statemachine\"\n\r* {state} is the name of the state given by column \"states (short name)\" of sheet \"statemachine\"", "Type": "Information", "Status": "", "Summary": "", "Relevant": "no", "column_12": "", "Foreign ID": "1206774.0", "Description": "The SPE constant name for each target state, i.e. column \"states (long name)\" of sheet \"statemachine\" is as follows:\n\r* CRMSA_c___{state machine}StTar{state}, if the group name given by column \"group name\" is empty\n\r* CRMSA_c___{group name}StTar{state}, otherwise\n\rWhere\n\r* {state machine} is the name of the state machine given by column \"state machine name\" of sheet \"statemachine\"\n\r* {group name} is the name of the group given by column \"group name\" of sheet \"statemachine\"\n\r* {state} is the name of the state given by column \"states (short name)\" of sheet \"statemachine\"", "Vehicle Launch": "", "Vehicle Platform": "E³ 1.2" }
38	16662132.0	Information		no	False	type_not_target, status_filtered, relevance_filtered	Examples: The SPE constants in this example are: * For state machine "Foo_Bi": CRMSA_c_Foo_BiStTarOff, CRMSA_c_Foo_BiStTarOn * Examples: The SPE constants in this example are: * For state machine "Foo_Bi": CRMSA_c_Foo_BiStTarOff, CRMSA_c_Foo_BiStTarOn * For state machine "Foo_Bob": CRMSA_c_Foo_BobStTarOff, CRMSA_c_Foo_BobStTarOn * For state machine "Fara": CRMSA_c_FaraStTarOff, CRMSA_c_FaraStTarAvlNoBkp, CRMSA_c_FaraStTarOn * For state machine "BarLgtCtl": CRMSA_c_MY_GroupStTarOff, CRMSA_c_MY_GroupStTarFailure, CRMSA_c_MY_GroupStTarRestricted, CRMSA_c_MY_GroupStTarNotAvailable, CRMSA_c_MY_GroupStTarOn Raw { "ID": "16662132.0", "ASIL": " ", "Text": "Examples:\n\rThe SPE constants in this example are:\n\r* For state machine \"Foo_Bi\": CRMSA_c_Foo_BiStTarOff, CRMSA_c_Foo_BiStTarOn\n\r* For state machine \"Foo_Bob\": CRMSA_c_Foo_BobStTarOff, CRMSA_c_Foo_BobStTarOn\n\r* For state machine \"Fara\": CRMSA_c_FaraStTarOff, CRMSA_c_FaraStTarAvlNoBkp, CRMSA_c_FaraStTarOn\n\r* For state machine \"BarLgtCtl\": CRMSA_c_MY_GroupStTarOff, CRMSA_c_MY_GroupStTarFailure, CRMSA_c_MY_GroupStTarRestricted, CRMSA_c_MY_GroupStTarNotAvailable, CRMSA_c_MY_GroupStTarOn", "Type": "Information", "Status": "", "Summary": "", "Relevant": "no", "column_12": "", "Foreign ID": "1206776.0", "Description": "Examples:\n\rThe SPE constants in this example are:\n\r* For state machine \"Foo_Bi\": CRMSA_c_Foo_BiStTarOff, CRMSA_c_Foo_BiStTarOn\n\r* For state machine \"Foo_Bob\": CRMSA_c_Foo_BobStTarOff, CRMSA_c_Foo_BobStTarOn\n\r* For state machine \"Fara\": CRMSA_c_FaraStTarOff, CRMSA_c_FaraStTarAvlNoBkp, CRMSA_c_FaraStTarOn\n\r* For state machine \"BarLgtCtl\": CRMSA_c_MY_GroupStTarOff, CRMSA_c_MY_GroupStTarFailure, CRMSA_c_MY_GroupStTarRestricted, CRMSA_c_MY_GroupStTarNotAvailable, CRMSA_c_MY_GroupStTarOn", "Vehicle Launch": "", "Vehicle Platform": "E³ 1.2" }
39	16662133.0	Folder		no	False	type_not_target, status_filtered, relevance_filtered	Degradation reason priority Degradation reason priority Raw { "ID": "16662133.0", "ASIL": " ", "Text": "Degradation reason priority", "Type": "Folder", "Status": "", "Summary": "Degradation reason priority", "Relevant": "no", "column_12": "", "Foreign ID": "1206752.0", "Description": "", "Vehicle Launch": "", "Vehicle Platform": "E³ 1.2" }
40	16662134.0	Information		no	False	type_not_target, status_filtered, relevance_filtered	The priorities are from high to low as follows: * Failure * Init * None The priorities are from high to low as follows: * Failure * Init * None Raw { "ID": "16662134.0", "ASIL": " ", "Text": "The priorities are from high to low as follows:\n\r* Failure\n\r* Init\n\r* None", "Type": "Information", "Status": "", "Summary": "", "Relevant": "no", "column_12": "", "Foreign ID": "1206778.0", "Description": "The priorities are from high to low as follows:\n\r* Failure\n\r* Init\n\r* None", "Vehicle Launch": "", "Vehicle Platform": "E³ 1.2" }
41	16662135.0	Information		no	False	type_not_target, status_filtered, relevance_filtered	The SPE constant name for each degradation reason value is defined as follows: * Failure: VMMP_CRM_c_StDgrdRsnFail * Init: VMMP_ The SPE constant name for each degradation reason value is defined as follows: * Failure: VMMP_CRM_c_StDgrdRsnFail * Init: VMMP_CRM_c_StDgrdRsnIni * None: VMMP_CRM_c_StDgrdRsnNone Raw { "ID": "16662135.0", "ASIL": " ", "Text": "The SPE constant name for each degradation reason value is defined as follows:\n\r* Failure: VMMP_CRM_c_StDgrdRsnFail\n\r* Init: VMMP_CRM_c_StDgrdRsnIni\n\r* None: VMMP_CRM_c_StDgrdRsnNone", "Type": "Information", "Status": "", "Summary": "", "Relevant": "no", "column_12": "", "Foreign ID": "1206780.0", "Description": "The SPE constant name for each degradation reason value is defined as follows:\n\r* Failure: VMMP_CRM_c_StDgrdRsnFail\n\r* Init: VMMP_CRM_c_StDgrdRsnIni\n\r* None: VMMP_CRM_c_StDgrdRsnNone", "Vehicle Launch": "", "Vehicle Platform": "E³ 1.2" }
42	16662136.0	Folder		no	False	type_not_target, status_filtered, relevance_filtered	Outputs Outputs Raw { "ID": "16662136.0", "ASIL": " ", "Text": "Outputs", "Type": "Folder", "Status": "", "Summary": "Outputs", "Relevant": "no", "column_12": "", "Foreign ID": "1206754.0", "Description": "", "Vehicle Launch": "", "Vehicle Platform": "E³ 1.2" }
43	16662137.0	Information		no	False	type_not_target, status_filtered, relevance_filtered	Examples: To explain the content of this section, the example is split in smaller parts given after each paragraph. Let's assume Examples: To explain the content of this section, the example is split in smaller parts given after each paragraph. Let's assume the following inputs to the module (sheet "reaction"): ASOAF_s_EPBActrCtl_StAvl = VMMP_ASOAF_c_EPBActrCtl_StAvlReleaseOnly ASOAF_s_DiagDrvPosn_StEveReq = VMMP_c_DiagEveSigFail ASOAF_s_DiagEPBActrCtl_StEveReq = VMMP_c_DiagEveSigNotVld So the active rows in this example are row 4, 8 and 13. Raw { "ID": "16662137.0", "ASIL": " ", "Text": "Examples:\n\rTo explain the content of this section, the example is split in smaller parts given after each paragraph.\n\rLet's assume the following inputs to the module (sheet \"reaction\"):\n\rASOAF_s_EPBActrCtl_StAvl = VMMP_ASOAF_c_EPBActrCtl_StAvlReleaseOnly\n\rASOAF_s_DiagDrvPosn_StEveReq = VMMP_c_DiagEveSigFail\n\rASOAF_s_DiagEPBActrCtl_StEveReq = VMMP_c_DiagEveSigNotVld\n\rSo the active rows in this example are row 4, 8 and 13.", "Type": "Information", "Status": "", "Summary": "", "Relevant": "no", "column_12": "", "Foreign ID": "1206782.0", "Description": "Examples:\n\rTo explain the content of this section, the example is split in smaller parts given after each paragraph.\n\rLet's assume the following inputs to the module (sheet \"reaction\"):\n\rASOAF_s_EPBActrCtl_StAvl = VMMP_ASOAF_c_EPBActrCtl_StAvlReleaseOnly\n\rASOAF_s_DiagDrvPosn_StEveReq = VMMP_c_DiagEveSigFail\n\rASOAF_s_DiagEPBActrCtl_StEveReq = VMMP_c_DiagEveSigNotVld\n\rSo the active rows in this example are row 4, 8 and 13.", "Vehicle Launch": "", "Vehicle Platform": "E³ 1.2" }
44	16662138.0	Information		no	False	type_not_target, status_filtered, relevance_filtered	The default value For each column, all cells, which have a value of "default", are equivalent to the state given by the column "d The default value For each column, all cells, which have a value of "default", are equivalent to the state given by the column "default state" in sheet "statemachine". Raw { "ID": "16662138.0", "ASIL": " ", "Text": "The default value\n\rFor each column, all cells, which have a value of \"default\", are equivalent to the state given by the column \"default state\" in sheet \"statemachine\".", "Type": "Information", "Status": "", "Summary": "", "Relevant": "no", "column_12": "", "Foreign ID": "1206784.0", "Description": "The default value\n\rFor each column, all cells, which have a value of \"default\", are equivalent to the state given by the column \"default state\" in sheet \"statemachine\".", "Vehicle Launch": "", "Vehicle Platform": "E³ 1.2" }
45	16662139.0	Information		no	False	type_not_target, status_filtered, relevance_filtered	Example: * In sheet "reaction", row 8 - 11, column F the state "default" is equivalent to the state "On" (default state of state Example: * In sheet "reaction", row 8 - 11, column F the state "default" is equivalent to the state "On" (default state of state machine "Foo_Bi", see sheet "statemachine" column C) * In sheet "reaction", row 8 - 11, column G the state "default" is equivalent to the state "On" (default state of state machine "Foo_Bob", see sheet "statemachine" column C) Raw { "ID": "16662139.0", "ASIL": " ", "Text": "Example:\n\r* In sheet \"reaction\", row 8 - 11, column F the state \"default\" is equivalent to the state \"On\" (default state of state machine \"Foo_Bi\", see sheet \"statemachine\" column C)\n\r* In sheet \"reaction\", row 8 - 11, column G the state \"default\" is equivalent to the state \"On\" (default state of state machine \"Foo_Bob\", see sheet \"statemachine\" column C)", "Type": "Information", "Status": "", "Summary": "", "Relevant": "no", "column_12": "", "Foreign ID": "1206786.0", "Description": "Example:\n\r* In sheet \"reaction\", row 8 - 11, column F the state \"default\" is equivalent to the state \"On\" (default state of state machine \"Foo_Bi\", see sheet \"statemachine\" column C)\n\r* In sheet \"reaction\", row 8 - 11, column G the state \"default\" is equivalent to the state \"On\" (default state of state machine \"Foo_Bob\", see sheet \"statemachine\" column C)", "Vehicle Launch": "", "Vehicle Platform": "E³ 1.2" }
46	16662140.0	Information		no	False	type_not_target, status_filtered, relevance_filtered	Information for tester: To increase code coverage the following parameter-value combination can be used: VMMP_CRMFH_p_NumEveExA_ Information for tester: To increase code coverage the following parameter-value combination can be used: VMMP_CRMFH_p_NumEveExA_XXX = 5 VMMP_CRMFH_p_NumEveFH_XXX = 5 VMMP_CRMFH_p1_StTarMtrxExA_XXX = [0 0 0 1 1 …] VMMP_CRMFH_p1_StTarMtrxFH_XXX = [0 0 0 1 1 …] VMMP_CRMFH_p1_MapEveExA_XXX = [0 0 1 1 1 …] VMMP_CRMFH_p1_MapEveFH_XXX = [0 0 1 1 1 …] VMMP_CRMFH_p1_StDgrdRsnFH_XXX = [0 0 0 0 1 …] where XXX is the "name of the output" - see also 3.4.1 For some outputs the parameter VMMP_CRMFH_p1_StDgrdRsnFH_XXX is not existing. In this case the parameter can be ignored. To get the correct output of the test coverage, it shall be assumed that the outputs defined in 3.4.1 shall be equal to 1. Raw { "ID": "16662140.0", "ASIL": " ", "Text": "Information for tester:\n\rTo increase code coverage the following parameter-value combination can be used:\n\rVMMP_CRMFH_p_NumEveExA_XXX = 5\n\rVMMP_CRMFH_p_NumEveFH_XXX = 5\n\rVMMP_CRMFH_p1_StTarMtrxExA_XXX = [0 0 0 1 1 …]\n\rVMMP_CRMFH_p1_StTarMtrxFH_XXX = [0 0 0 1 1 …]\n\rVMMP_CRMFH_p1_MapEveExA_XXX = [0 0 1 1 1 …]\n\rVMMP_CRMFH_p1_MapEveFH_XXX = [0 0 1 1 1 …]\n\rVMMP_CRMFH_p1_StDgrdRsnFH_XXX = [0 0 0 0 1 …]\n\rwhere XXX is the \"name of the output\" - see also 3.4.1\n\rFor some outputs the parameter VMMP_CRMFH_p1_StDgrdRsnFH_XXX is not existing. In this case the parameter can be ignored.\n\r \n\rTo get the correct output of the test coverage, it shall be assumed that the outputs defined in 3.4.1 shall be equal to 1.", "Type": "Information", "Status": "", "Summary": "", "Relevant": "no", "column_12": "", "Foreign ID": "1400527.0", "Description": "Information for tester:\n\rTo increase code coverage the following parameter-value combination can be used:\n\rVMMP_CRMFH_p_NumEveExA_XXX = 5\n\rVMMP_CRMFH_p_NumEveFH_XXX = 5\n\rVMMP_CRMFH_p1_StTarMtrxExA_XXX = [0 0 0 1 1 …]\n\rVMMP_CRMFH_p1_StTarMtrxFH_XXX = [0 0 0 1 1 …]\n\rVMMP_CRMFH_p1_MapEveExA_XXX = [0 0 1 1 1 …]\n\rVMMP_CRMFH_p1_MapEveFH_XXX = [0 0 1 1 1 …]\n\rVMMP_CRMFH_p1_StDgrdRsnFH_XXX = [0 0 0 0 1 …]\n\rwhere XXX is the \"name of the output\" - see also 3.4.1\n\rFor some outputs the parameter VMMP_CRMFH_p1_StDgrdRsnFH_XXX is not existing. In this case the parameter can be ignored.\n\r \n\rTo get the correct output of the test coverage, it shall be assumed that the outputs defined in 3.4.1 shall be equal to 1.", "Vehicle Launch": "", "Vehicle Platform": "E³ 1.2" }
47	16662141.0	Functional	Released	yes	True		When the following parameter-value combination can be used:to increase the code coverage, then the corresponding output. to the pa When the following parameter-value combination can be used:to increase the code coverage, then the corresponding output. to the parameter which has been changed should have value "1 VMMP_CRMFH_p_NumEveExA_XXX = 5 VMMP_CRMFH_p_NumEveFH_XXX = 5 VMMP_CRMFH_p1_StTarMtrxExA_XXX = [0 0 0 1 1 …] VMMP_CRMFH_p1_StTarMtrxFH_XXX = [0 0 0 1 1 …] VMMP_CRMFH_p1_MapEveExA_XXX = [0 0 1 1 1 …] VMMP_CRMFH_p1_MapEveFH_XXX = [0 0 1 1 1 …] VMMP_CRMFH_p1_StDgrdRsnFH_XXX = [0 0 0 0 1 …] where XXX is the "name of the output" - see also 3.4.1 For some outputs the parameter VMMP_CRMFH_p1_StDgrdRsnFH_XXX is not existing. In this case the parameter can be ignored. Raw { "ID": "16662141.0", "ASIL": " ASIL D", "Text": "When the following parameter-value combination can be used:to increase the code coverage, then the corresponding output. to the parameter which has been changed should have value \"1\n\r \n\r \n\rVMMP_CRMFH_p_NumEveExA_XXX = 5\n\rVMMP_CRMFH_p_NumEveFH_XXX = 5\n\rVMMP_CRMFH_p1_StTarMtrxExA_XXX = [0 0 0 1 1 …]\n\rVMMP_CRMFH_p1_StTarMtrxFH_XXX = [0 0 0 1 1 …]\n\rVMMP_CRMFH_p1_MapEveExA_XXX = [0 0 1 1 1 …]\n\rVMMP_CRMFH_p1_MapEveFH_XXX = [0 0 1 1 1 …]\n\rVMMP_CRMFH_p1_StDgrdRsnFH_XXX = [0 0 0 0 1 …]\n\r \n\r \n\rwhere XXX is the \"name of the output\" - see also 3.4.1\n\r \n\r \n\rFor some outputs the parameter VMMP_CRMFH_p1_StDgrdRsnFH_XXX is not existing. In this case the parameter can be ignored.", "Type": "Functional", "Status": "Released", "Summary": "", "Relevant": "yes", "column_12": "", "Foreign ID": "1522333.0", "Description": "When the following parameter-value combination can be used:to increase the code coverage, then the corresponding output. to the parameter which has been changed should have value \"1\n\r \n\r \n\rVMMP_CRMFH_p_NumEveExA_XXX = 5\n\rVMMP_CRMFH_p_NumEveFH_XXX = 5\n\rVMMP_CRMFH_p1_StTarMtrxExA_XXX = [0 0 0 1 1 …]\n\rVMMP_CRMFH_p1_StTarMtrxFH_XXX = [0 0 0 1 1 …]\n\rVMMP_CRMFH_p1_MapEveExA_XXX = [0 0 1 1 1 …]\n\rVMMP_CRMFH_p1_MapEveFH_XXX = [0 0 1 1 1 …]\n\rVMMP_CRMFH_p1_StDgrdRsnFH_XXX = [0 0 0 0 1 …]\n\r \n\r \n\rwhere XXX is the \"name of the output\" - see also 3.4.1\n\r \n\r \n\rFor some outputs the parameter VMMP_CRMFH_p1_StDgrdRsnFH_XXX is not existing. In this case the parameter can be ignored.", "Vehicle Launch": "", "Vehicle Platform": "E³ 1.2" }
48	16662142.0	Folder		no	False	type_not_target, status_filtered, relevance_filtered	Target States Target States Raw { "ID": "16662142.0", "ASIL": " ", "Text": "Target States", "Type": "Folder", "Status": "", "Summary": "Target States", "Relevant": "no", "column_12": "", "Foreign ID": "1207427.0", "Description": "", "Vehicle Launch": "", "Vehicle Platform": "E³ 1.2" }
49	16662143.0	Information		no	False	type_not_target, status_filtered, relevance_filtered	Empty cell doesn't have any impact on the output. It should be ignored. Empty cell doesn't have any impact on the output. It should be ignored. Raw { "ID": "16662143.0", "ASIL": " ", "Text": "Empty cell doesn't have any impact on the output. It should be ignored.", "Type": "Information", "Status": "", "Summary": "", "Relevant": "no", "column_12": "", "Foreign ID": "1232245.0", "Description": "Empty cell doesn't have any impact on the output. It should be ignored.", "Vehicle Launch": "", "Vehicle Platform": "E³ 1.2" }
50	16662144.0	Functional	Released	yes	True		For each column starting with the first output signal and for each cell in this column: IF [AND(1, 2)]: 1) The cell is part of a For each column starting with the first output signal and for each cell in this column: IF [AND(1, 2)]: 1) The cell is part of an active row, that has a "signal type" of "diagevent" 2) The value of the cell has the highest target state priority of all the values within the column THEN: Output StTar FH is the value of the cell ELSE: Output StTar FH is "On" Raw { "ID": "16662144.0", "ASIL": " ASIL D", "Text": "For each column starting with the first output signal and for each cell in this column:\n\r \n\rIF [AND(1, 2)]:\n\r1) The cell is part of an active row, that has a \"signal type\" of \"diagevent\"\n\r2) The value of the cell has the highest target state priority of all the values within the column\n\r \n\rTHEN:\n\rOutput StTar FH is the value of the cell\n\r \n\rELSE:\n\rOutput StTar FH is \"On\"", "Type": "Functional", "Status": "Released", "Summary": "", "Relevant": "yes", "column_12": "", "Foreign ID": "1206788.0", "Description": "For each column starting with the first output signal and for each cell in this column:\n\r \n\rIF [AND(1, 2)]:\n\r1) The cell is part of an active row, that has a \"signal type\" of \"diagevent\"\n\r2) The value of the cell has the highest target state priority of all the values within the column\n\r \n\rTHEN:\n\rOutput StTar FH is the value of the cell\n\r \n\rELSE:\n\rOutput StTar FH is \"On\"", "Vehicle Launch": "", "Vehicle Platform": "E³ 1.2" }
51	16662145.0	Information		no	False	type_not_target, status_filtered, relevance_filtered	Example: In this example (see 1206782) row 8 and 13 are active rows, which have a "signal type" of "diagevent". * For state mach Example: In this example (see 1206782) row 8 and 13 are active rows, which have a "signal type" of "diagevent". * For state machine "Foo_Bi" the output "CRMFH_s_Foo_StTarBiFH" is the value of "CRMSA_c_Foo_BiStTarOff". The active rows in column "Foo_Bi" have the states "Off" and "default" - which equals "On". "Off" has a higher priority than "On" (see previous section "Target state priority"). Therefore the final state is "Off". * For state machine "Fara" the output "CRMFH_s_Fara_StTarFH" is the value of "CRMSA_c_FaraStTarAvlNoBkp". The active rows in column "Fara" have the states "AvailableNoBackup" and "On". "AvailableNoBackup" has a higher priority than "On" (see previous section "Target state priority"). Therefore the final state is "AvailableNoBackup". Raw { "ID": "16662145.0", "ASIL": " ", "Text": "Example:\n\rIn this example (see 1206782) row 8 and 13 are active rows, which have a \"signal type\" of \"diagevent\".\n\r* For state machine \"Foo_Bi\" the output \"CRMFH_s_Foo_StTarBiFH\" is the value of \"CRMSA_c_Foo_BiStTarOff\". The active rows in column \"Foo_Bi\" have the states \"Off\" and \"default\" - which equals \"On\". \n\r \"Off\" has a higher priority than \"On\" (see previous section \"Target state priority\"). Therefore the final state is \"Off\".\n\r* For state machine \"Fara\" the output \"CRMFH_s_Fara_StTarFH\" is the value of \"CRMSA_c_FaraStTarAvlNoBkp\". The active rows in column \"Fara\" have the states \"AvailableNoBackup\" and \"On\". \n\r \"AvailableNoBackup\" has a higher priority than \"On\" (see previous section \"Target state priority\"). Therefore the final state is \"AvailableNoBackup\".", "Type": "Information", "Status": "", "Summary": "", "Relevant": "no", "column_12": "", "Foreign ID": "1206790.0", "Description": "Example:\n\rIn this example (see 1206782) row 8 and 13 are active rows, which have a \"signal type\" of \"diagevent\".\n\r* For state machine \"Foo_Bi\" the output \"CRMFH_s_Foo_StTarBiFH\" is the value of \"CRMSA_c_Foo_BiStTarOff\". The active rows in column \"Foo_Bi\" have the states \"Off\" and \"default\" - which equals \"On\". \n\r \"Off\" has a higher priority than \"On\" (see previous section \"Target state priority\"). Therefore the final state is \"Off\".\n\r* For state machine \"Fara\" the output \"CRMFH_s_Fara_StTarFH\" is the value of \"CRMSA_c_FaraStTarAvlNoBkp\". The active rows in column \"Fara\" have the states \"AvailableNoBackup\" and \"On\". \n\r \"AvailableNoBackup\" has a higher priority than \"On\" (see previous section \"Target state priority\"). Therefore the final state is \"AvailableNoBackup\".", "Vehicle Launch": "", "Vehicle Platform": "E³ 1.2" }
52	16662146.0	Functional	Released	yes	True		For each column starting with the first output signal and for each cell in this column: IF [AND(1, 2)]: 1) The cell is part of a For each column starting with the first output signal and for each cell in this column: IF [AND(1, 2)]: 1) The cell is part of an active row, that has a "signal type" of "availability" 2) The value of the cell has the highest target state priority of all the values within the column THEN: Output StTar ExA is the value of the cell ELSE: Output StTar ExA is "On" Raw { "ID": "16662146.0", "ASIL": " ASIL D", "Text": "For each column starting with the first output signal and for each cell in this column:\n\r \n\rIF [AND(1, 2)]:\n\r1) The cell is part of an active row, that has a \"signal type\" of \"availability\"\n\r2) The value of the cell has the highest target state priority of all the values within the column\n\r \n\rTHEN:\n\rOutput StTar ExA is the value of the cell\n\r \n\rELSE:\n\rOutput StTar ExA is \"On\"", "Type": "Functional", "Status": "Released", "Summary": "", "Relevant": "yes", "column_12": "", "Foreign ID": "1206792.0", "Description": "For each column starting with the first output signal and for each cell in this column:\n\r \n\rIF [AND(1, 2)]:\n\r1) The cell is part of an active row, that has a \"signal type\" of \"availability\"\n\r2) The value of the cell has the highest target state priority of all the values within the column\n\r \n\rTHEN:\n\rOutput StTar ExA is the value of the cell\n\r \n\rELSE:\n\rOutput StTar ExA is \"On\"", "Vehicle Launch": "", "Vehicle Platform": "E³ 1.2" }
53	16662147.0	Information		no	False	type_not_target, status_filtered, relevance_filtered	Example: In this example row 4 is the only active row, which have a "signal type" of "availability". For state machine "Foo_Bi" Example: In this example row 4 is the only active row, which have a "signal type" of "availability". For state machine "Foo_Bi" the output "CRMFH_s_Foo_StTarBiExA" is the value of "CRMSA_c_Foo_BiStTarOff". The active row in column "Foo_Bi" has the state "Off". It is the single active row. Therefore the final state is "Off". Raw { "ID": "16662147.0", "ASIL": " ", "Text": "Example:\n\rIn this example row 4 is the only active row, which have a \"signal type\" of \"availability\". \n\rFor state machine \"Foo_Bi\" the output \"CRMFH_s_Foo_StTarBiExA\" is the value of \"CRMSA_c_Foo_BiStTarOff\". The active row in column \"Foo_Bi\" has the state \"Off\". It is the single active row. Therefore the final state is \"Off\".", "Type": "Information", "Status": "", "Summary": "", "Relevant": "no", "column_12": "", "Foreign ID": "1206794.0", "Description": "Example:\n\rIn this example row 4 is the only active row, which have a \"signal type\" of \"availability\". \n\rFor state machine \"Foo_Bi\" the output \"CRMFH_s_Foo_StTarBiExA\" is the value of \"CRMSA_c_Foo_BiStTarOff\". The active row in column \"Foo_Bi\" has the state \"Off\". It is the single active row. Therefore the final state is \"Off\".", "Vehicle Launch": "", "Vehicle Platform": "E³ 1.2" }
54	16662148.0	Folder		no	False	type_not_target, status_filtered, relevance_filtered	Degradation Reasons Degradation Reasons Raw { "ID": "16662148.0", "ASIL": " ", "Text": "Degradation Reasons", "Type": "Folder", "Status": "", "Summary": "Degradation Reasons", "Relevant": "no", "column_12": "", "Foreign ID": "1207431.0", "Description": "", "Vehicle Launch": "", "Vehicle Platform": "E³ 1.2" }
55	16662149.0	Information		no	False	type_not_target, status_filtered, relevance_filtered	Empty cell doesn't have any impact on the output. It shall be ignored. Empty cell doesn't have any impact on the output. It shall be ignored. Raw { "ID": "16662149.0", "ASIL": " ", "Text": "Empty cell doesn't have any impact on the output. It shall be ignored.", "Type": "Information", "Status": "", "Summary": "", "Relevant": "no", "column_12": "", "Foreign ID": "1232249.0", "Description": "Empty cell doesn't have any impact on the output. It shall be ignored.", "Vehicle Launch": "", "Vehicle Platform": "E³ 1.2" }
56	16662150.0	Pre Condition	Released	no	False	type_not_target, relevance_filtered	The output DgrdRsn FH is only provided, if for the associated state machine "yes" is given in the column "use degradation reason" The output DgrdRsn FH is only provided, if for the associated state machine "yes" is given in the column "use degradation reason" of the sheet "statemachine". Raw { "ID": "16662150.0", "ASIL": " QM", "Text": "The output DgrdRsn FH is only provided, if for the associated state machine \"yes\" is given in the column \"use degradation reason\" of the sheet \"statemachine\".", "Type": "Pre Condition", "Status": "Released", "Summary": "", "Relevant": "no", "column_12": "", "Foreign ID": "1206800.0", "Description": "The output DgrdRsn FH is only provided, if for the associated state machine \"yes\" is given in the column \"use degradation reason\" of the sheet \"statemachine\".", "Vehicle Launch": "", "Vehicle Platform": "E³ 1.2" }
57	16662151.0	Functional	Released	yes	True		For each state machine, where 16662150 is true IF [AND(1, 2, 3)]: 1) The value is part of an active row, that has a "signal type For each state machine, where 16662150 is true IF [AND(1, 2, 3)]: 1) The value is part of an active row, that has a "signal type" of "diagevent" 2) The value is not the default value. This can either be the literal string "default" or the string given by the column "default state" in sheet "statemachine" 3) The value of the cell has the highest target state priority of all the values within the column THEN: Output DgrdRsn FH is the value of the cell in the column "degradation reason" ELSE: Output StTar DgrdRsn is the Degradation Reason "None" (i.e. value of VMMP_CRM_c_StDgrdRsnNone). Raw { "ID": "16662151.0", "ASIL": " QM", "Text": "For each state machine, where 16662150 is true\n\r \n\r \n\rIF [AND(1, 2, 3)]:\n\r1) The value is part of an active row, that has a \"signal type\" of \"diagevent\"\n\r2) The value is not the default value. This can either be the literal string \"default\" or the string given by the column \"default state\" in sheet \"statemachine\"\n\r3) The value of the cell has the highest target state priority of all the values within the column\n\r \n\r \n\rTHEN:\n\rOutput DgrdRsn FH is the value of the cell in the column \"degradation reason\"\n\r \n\r \n\rELSE:\n\rOutput StTar DgrdRsn is the Degradation Reason \"None\" (i.e. value of VMMP_CRM_c_StDgrdRsnNone).", "Type": "Functional", "Status": "Released", "Summary": "", "Relevant": "yes", "column_12": "", "Foreign ID": "1206796.0", "Description": "For each state machine, where 16662150 is true\n\r \n\r \n\rIF [AND(1, 2, 3)]:\n\r1) The value is part of an active row, that has a \"signal type\" of \"diagevent\"\n\r2) The value is not the default value. This can either be the literal string \"default\" or the string given by the column \"default state\" in sheet \"statemachine\"\n\r3) The value of the cell has the highest target state priority of all the values within the column\n\r \n\r \n\rTHEN:\n\rOutput DgrdRsn FH is the value of the cell in the column \"degradation reason\"\n\r \n\r \n\rELSE:\n\rOutput StTar DgrdRsn is the Degradation Reason \"None\" (i.e. value of VMMP_CRM_c_StDgrdRsnNone).", "Vehicle Launch": "", "Vehicle Platform": "E³ 1.2" }
58	16662152.0	Information		no	False	type_not_target, status_filtered, relevance_filtered	Example: In this example (see 1206782) row 8 and 13 are active rows, which have a "signal type" of "diagevent". The degradation Example: In this example (see 1206782) row 8 and 13 are active rows, which have a "signal type" of "diagevent". The degradation reasons in active rows are therefore "Failure" and "None". * For state machine "Foo_Bi" the output StTar DgrdRsn is "None". Row 8 has a "signal type" of diagevent, it is an active row, but for state machine "Foo_Bi" the default state is given. So one of the conditions is not satisfied. Row 13 on the other hand satisfies all conditions. * Let's assume the following inputs to the module (sheet "reaction"): ASOAF_s_DiagDrvPosn_StEveReq = VMMP_c_DiagEveSigIni ASOAF_s_DiagEPBActrCtl_StEveReq = VMMP_c_DiagEveSigFail So the active rows (sheet "reaction") in this example are row 11 and 12. In this example, for state machine "BarLgtCtl" the output StTar DgrdRsn is "Failure". Both rows have a "signal type" of diagevent and are active rows. The value of the states ("Failure" and "Restricted" in this example) are both not the default state. So the final Degradation Reason is determined by the last of the conditions given above: the highest priority of the Degradation Reasons "Init" and "Failure" has the Degradation Reason "Failure". Raw { "ID": "16662152.0", "ASIL": " ", "Text": "Example:\n\rIn this example (see 1206782) row 8 and 13 are active rows, which have a \"signal type\" of \"diagevent\".\n\r \n\rThe degradation reasons in active rows are therefore \"Failure\" and \"None\".\n\r* For state machine \"Foo_Bi\" the output StTar DgrdRsn is \"None\". Row 8 has a \"signal type\" of diagevent, it is an active row, but for state machine \"Foo_Bi\" the default state is given. So one of the conditions is not satisfied. Row 13 on the other hand satisfies all conditions.\n\r \n\r \n\r* Let's assume the following inputs to the module (sheet \"reaction\"): \n\r ASOAF_s_DiagDrvPosn_StEveReq = VMMP_c_DiagEveSigIni \n\r ASOAF_s_DiagEPBActrCtl_StEveReq = VMMP_c_DiagEveSigFail \n\r So the active rows (sheet \"reaction\") in this example are row 11 and 12. \n\r In this example, for state machine \"BarLgtCtl\" the output StTar DgrdRsn is \"Failure\". Both rows have a \"signal type\" of diagevent and are active rows. The value of the states (\"Failure\" and \"Restricted\" in this example) are both not the default state. So the final Degradation Reason is determined by the last of the conditions given above: the highest priority of the Degradation Reasons \"Init\" and \"Failure\" has the Degradation Reason \"Failure\".", "Type": "Information", "Status": "", "Summary": "", "Relevant": "no", "column_12": "", "Foreign ID": "1206798.0", "Description": "Example:\n\rIn this example (see 1206782) row 8 and 13 are active rows, which have a \"signal type\" of \"diagevent\".\n\r \n\rThe degradation reasons in active rows are therefore \"Failure\" and \"None\".\n\r* For state machine \"Foo_Bi\" the output StTar DgrdRsn is \"None\". Row 8 has a \"signal type\" of diagevent, it is an active row, but for state machine \"Foo_Bi\" the default state is given. So one of the conditions is not satisfied. Row 13 on the other hand satisfies all conditions.\n\r \n\r \n\r* Let's assume the following inputs to the module (sheet \"reaction\"): \n\r ASOAF_s_DiagDrvPosn_StEveReq = VMMP_c_DiagEveSigIni \n\r ASOAF_s_DiagEPBActrCtl_StEveReq = VMMP_c_DiagEveSigFail \n\r So the active rows (sheet \"reaction\") in this example are row 11 and 12. \n\r In this example, for state machine \"BarLgtCtl\" the output StTar DgrdRsn is \"Failure\". Both rows have a \"signal type\" of diagevent and are active rows. The value of the states (\"Failure\" and \"Restricted\" in this example) are both not the default state. So the final Degradation Reason is determined by the last of the conditions given above: the highest priority of the Degradation Reasons \"Init\" and \"Failure\" has the Degradation Reason \"Failure\".", "Vehicle Launch": "", "Vehicle Platform": "E³ 1.2" }
59	16662153.0	Information		no	False	type_not_target, status_filtered, relevance_filtered	Example: In this example only Foo_Bi and Foo_Bob provide a degradation reason as its output, i.e. CRMFH_s_Foo_StDgrdRsnBiFH and C Example: In this example only Foo_Bi and Foo_Bob provide a degradation reason as its output, i.e. CRMFH_s_Foo_StDgrdRsnBiFH and CRMFH_s_Foo_StDgrdRsnBobFH. Raw { "ID": "16662153.0", "ASIL": " ", "Text": "Example:\n\rIn this example only Foo_Bi and Foo_Bob provide a degradation reason as its output, i.e. CRMFH_s_Foo_StDgrdRsnBiFH and CRMFH_s_Foo_StDgrdRsnBobFH.", "Type": "Information", "Status": "", "Summary": "", "Relevant": "no", "column_12": "", "Foreign ID": "1206802.0", "Description": "Example:\n\rIn this example only Foo_Bi and Foo_Bob provide a degradation reason as its output, i.e. CRMFH_s_Foo_StDgrdRsnBiFH and CRMFH_s_Foo_StDgrdRsnBobFH.", "Vehicle Launch": "", "Vehicle Platform": "E³ 1.2" }
60	16662154.0	Folder		no	False	type_not_target, status_filtered, relevance_filtered	Computation of cyclic event ID Computation of cyclic event ID Raw { "ID": "16662154.0", "ASIL": " ", "Text": "Computation of cyclic event ID", "Type": "Folder", "Status": "", "Summary": "Computation of cyclic event ID", "Relevant": "no", "column_12": "", "Foreign ID": "1285718.0", "Description": "", "Vehicle Launch": "", "Vehicle Platform": "E³ 1.2" }
61	16662155.0	Information		no	False	type_not_target, status_filtered, relevance_filtered	The index of all diag events are based on the alphabetical order starting with id 1. The diag events are given by the signals list The index of all diag events are based on the alphabetical order starting with id 1. The diag events are given by the signals listed in VMM_CRM_FunctionMatrix.xlsx in sheet 'reaction' in 'signal name' (column A), where 'signal type' (column D) equals 'diagevent'. Raw { "ID": "16662155.0", "ASIL": " ", "Text": "The index of all diag events are based on the alphabetical order starting with id 1. The diag events are given by the signals listed in VMM_CRM_FunctionMatrix.xlsx in sheet 'reaction' in 'signal name' (column A), where 'signal type' (column D) equals 'diagevent'.", "Type": "Information", "Status": "", "Summary": "", "Relevant": "no", "column_12": "", "Foreign ID": "1285660.0", "Description": "The index of all diag events are based on the alphabetical order starting with id 1. The diag events are given by the signals listed in VMM_CRM_FunctionMatrix.xlsx in sheet 'reaction' in 'signal name' (column A), where 'signal type' (column D) equals 'diagevent'.", "Vehicle Launch": "", "Vehicle Platform": "E³ 1.2" }
62	16662156.0	Information		no	False	type_not_target, status_filtered, relevance_filtered	The cycle event id shall not be confused with the column "id" in VMM_CRM_FunctionMatrix.xlsx in sheet 'reaction' as both are unrel The cycle event id shall not be confused with the column "id" in VMM_CRM_FunctionMatrix.xlsx in sheet 'reaction' as both are unrelated to one another. Raw { "ID": "16662156.0", "ASIL": " ", "Text": "The cycle event id shall not be confused with the column \"id\" in VMM_CRM_FunctionMatrix.xlsx in sheet 'reaction' as both are unrelated to one another.", "Type": "Information", "Status": "", "Summary": "", "Relevant": "no", "column_12": "", "Foreign ID": "1314431.0", "Description": "The cycle event id shall not be confused with the column \"id\" in VMM_CRM_FunctionMatrix.xlsx in sheet 'reaction' as both are unrelated to one another.", "Vehicle Launch": "", "Vehicle Platform": "E³ 1.2" }
63	16662157.0	Information		no	False	type_not_target, status_filtered, relevance_filtered	A diagnose event or diag event can take following values: None: VMMP_c_DiagEveSigNone (meaning the diagnose event is valid and fa A diagnose event or diag event can take following values: None: VMMP_c_DiagEveSigNone (meaning the diagnose event is valid and failure-free), Disabled: VMMP_c_DiagEveSigDi, NotValid: VMMP_c_DiagEveSigNotVld, Failed: VMMP_c_DiagEveSigFail, Init: VMMP_c_DiagEveSigIni, InitExceed: VMMP_c_DiagEveSigIniExc Raw { "ID": "16662157.0", "ASIL": " ", "Text": "A diagnose event or diag event can take following values:\n\rNone: VMMP_c_DiagEveSigNone (meaning the diagnose event is valid and failure-free),\n\rDisabled: VMMP_c_DiagEveSigDi,\n\rNotValid: VMMP_c_DiagEveSigNotVld,\n\rFailed: VMMP_c_DiagEveSigFail,\n\rInit: VMMP_c_DiagEveSigIni, \n\rInitExceed: VMMP_c_DiagEveSigIniExc", "Type": "Information", "Status": "", "Summary": "", "Relevant": "no", "column_12": "", "Foreign ID": "1316980.0", "Description": "A diagnose event or diag event can take following values:\n\rNone: VMMP_c_DiagEveSigNone (meaning the diagnose event is valid and failure-free),\n\rDisabled: VMMP_c_DiagEveSigDi,\n\rNotValid: VMMP_c_DiagEveSigNotVld,\n\rFailed: VMMP_c_DiagEveSigFail,\n\rInit: VMMP_c_DiagEveSigIni, \n\rInitExceed: VMMP_c_DiagEveSigIniExc", "Vehicle Launch": "", "Vehicle Platform": "E³ 1.2" }
64	16662158.0	Functional	Released	yes	True		IF[1] 1) all DiagEvents have the value VMMP_c_DiagEveSigNone or VMMP_c_DiagEveSigDi THEN Output CRMFH_s_CycDiagEveId is 0. E IF[1] 1) all DiagEvents have the value VMMP_c_DiagEveSigNone or VMMP_c_DiagEveSigDi THEN Output CRMFH_s_CycDiagEveId is 0. ELSE Output CRMFH_s_CycDiagEveId is the index of the next active diag event. Raw { "ID": "16662158.0", "ASIL": " QM", "Text": "IF[1]\n\r1) all DiagEvents have the value VMMP_c_DiagEveSigNone or VMMP_c_DiagEveSigDi \n\rTHEN \n\rOutput CRMFH_s_CycDiagEveId is 0.\n\rELSE \n\rOutput CRMFH_s_CycDiagEveId is the index of the next active diag event.", "Type": "Functional", "Status": "Released", "Summary": "", "Relevant": "yes", "column_12": "", "Foreign ID": "1285658.0", "Description": "IF[1]\n\r1) all DiagEvents have the value VMMP_c_DiagEveSigNone or VMMP_c_DiagEveSigDi \n\rTHEN \n\rOutput CRMFH_s_CycDiagEveId is 0.\n\rELSE \n\rOutput CRMFH_s_CycDiagEveId is the index of the next active diag event.", "Vehicle Launch": "", "Vehicle Platform": "E³ 1.2" }
65	16662159.0	Information		no	False	type_not_target, status_filtered, relevance_filtered	An active diag event is a diag event, which has neither the value VMMP_c_DiagEveSigNone nor the value VMMP_c_DiagEveSigDi. * The An active diag event is a diag event, which has neither the value VMMP_c_DiagEveSigNone nor the value VMMP_c_DiagEveSigDi. * The next active diag event is the active diag event, that comes after the diag event, which was found in a previous time step. For the first iteration starting at index 1. If all diag events have been iterated, start at the first diag event again. If no active diag event was found for one or more cycles, the iteration does continue at the index of the last found active diag event. Over time all active diag events are iterated. Raw { "ID": "16662159.0", "ASIL": " ", "Text": "An active diag event is a diag event, which has neither the value VMMP_c_DiagEveSigNone nor the value VMMP_c_DiagEveSigDi.\n\r* The next active diag event is the active diag event, that comes after the diag event, which was found in a previous time step.\n\rFor the first iteration starting at index 1.\n\rIf all diag events have been iterated, start at the first diag event again.\n\rIf no active diag event was found for one or more cycles, the iteration does continue at the index of the last found active diag event.\n\rOver time all active diag events are iterated.", "Type": "Information", "Status": "", "Summary": "", "Relevant": "no", "column_12": "", "Foreign ID": "1285680.0", "Description": "An active diag event is a diag event, which has neither the value VMMP_c_DiagEveSigNone nor the value VMMP_c_DiagEveSigDi.\n\r* The next active diag event is the active diag event, that comes after the diag event, which was found in a previous time step.\n\rFor the first iteration starting at index 1.\n\rIf all diag events have been iterated, start at the first diag event again.\n\rIf no active diag event was found for one or more cycles, the iteration does continue at the index of the last found active diag event.\n\rOver time all active diag events are iterated.", "Vehicle Launch": "", "Vehicle Platform": "E³ 1.2" }
66	16662160.0	Information		no	False	type_not_target, status_filtered, relevance_filtered	Example: For VMM_CRM_FunctionMatrix_Example.xlsx the diag events are ASOAF_s_DiagDrvPosn_StEveReq with index 1 and ASOAF_s_DiagEP Example: For VMM_CRM_FunctionMatrix_Example.xlsx the diag events are ASOAF_s_DiagDrvPosn_StEveReq with index 1 and ASOAF_s_DiagEPBActrCtl_StEveReq with index 2. Let's assume that each of those events can take the value (VMMP_c_DiagEveSigFail or VMMP_c_DiagEveSigNone or VMMP_c_DiagEveSigNotVld) at different timesteps as shown in the following table. Empty attachment [_74e1c623-8a20-4178-a2ff-b237e84cf693_2_1.png] The expected result for this example at the timesteps 0s - 0.08s is: 0.00s: 1 (both diag events are active; so the output toggles between 1 and 2) 0.01s: 2 0.02s: 1 0.03s: 0 (no diag event is active) 0.04s: 0 0.05s: 2 (again both diag events are active) 0.06s: 1 0.07s: 2 0.08s: 1 (only the first diag event is active) 0.09s: 1 Raw { "ID": "16662160.0", "ASIL": " ", "Text": "Example:\n\rFor VMM_CRM_FunctionMatrix_Example.xlsx the diag events are ASOAF_s_DiagDrvPosn_StEveReq with index 1 and ASOAF_s_DiagEPBActrCtl_StEveReq with index 2.\n\rLet's assume that each of those events can take the value (VMMP_c_DiagEveSigFail or VMMP_c_DiagEveSigNone or VMMP_c_DiagEveSigNotVld) at different timesteps as shown in the following table.\n\rEmpty attachment [_74e1c623-8a20-4178-a2ff-b237e84cf693_2_1.png]\n\rThe expected result for this example at the timesteps 0s - 0.08s is:\n\r0.00s: 1 (both diag events are active; so the output toggles between 1 and 2)\n\r0.01s: 2\n\r0.02s: 1\n\r0.03s: 0 (no diag event is active)\n\r0.04s: 0\n\r0.05s: 2 (again both diag events are active)\n\r0.06s: 1\n\r0.07s: 2\n\r0.08s: 1 (only the first diag event is active)\n\r0.09s: 1", "Type": "Information", "Status": "", "Summary": "", "Relevant": "no", "column_12": "", "Foreign ID": "1285688.0", "Description": "Example:\n\rFor VMM_CRM_FunctionMatrix_Example.xlsx the diag events are ASOAF_s_DiagDrvPosn_StEveReq with index 1 and ASOAF_s_DiagEPBActrCtl_StEveReq with index 2.\n\rLet's assume that each of those events can take the value (VMMP_c_DiagEveSigFail or VMMP_c_DiagEveSigNone or VMMP_c_DiagEveSigNotVld) at different timesteps as shown in the following table.\n\rEmpty attachment [_74e1c623-8a20-4178-a2ff-b237e84cf693_2_1.png]\n\rThe expected result for this example at the timesteps 0s - 0.08s is:\n\r0.00s: 1 (both diag events are active; so the output toggles between 1 and 2)\n\r0.01s: 2\n\r0.02s: 1\n\r0.03s: 0 (no diag event is active)\n\r0.04s: 0\n\r0.05s: 2 (again both diag events are active)\n\r0.06s: 1\n\r0.07s: 2\n\r0.08s: 1 (only the first diag event is active)\n\r0.09s: 1", "Vehicle Launch": "", "Vehicle Platform": "E³ 1.2" }

Source files

Mapping profiles

Import history

VME-PROD-VehicleMotionManagement - VMMP_CRM_CRMFH.xlsx · source records

Raw

Raw

Raw

Raw

Raw

Raw

Raw

Raw

Raw

Raw

Raw

Raw

Raw

Raw

Raw

Raw

Raw

Raw

Raw

Raw

Raw

Raw

Raw

Raw

Raw

Raw

Raw

Raw

Raw

Raw

Raw

Raw

Raw

Raw

Raw

Raw

Raw

Raw

Raw

Raw

Raw

Raw

Raw

Raw

Raw

Raw

Raw

Raw

Raw

Raw

Raw

Raw

Raw

Raw

Raw

Raw

Raw

Raw

Raw

Raw

Raw

Raw

Raw

Raw

Raw