Handling Non-Compliance

National Body Reference Architecture / NB Functional View / LL Functions / Handling Non-Compliance

Project:

Handling Non-Compliance : Public <<FRAME_Low_Level_Function>> FRAME_Low_Level_Function

Created:	26.08.2024 09:35:08
Modified:	17.04.2025 16:00:01

Project:
Author:	benjamin.witsch
Version:	1.0
Phase:	1.0
Status:	Proposed
Complexity:	Easy
Difficulty:
Priority:
Multiplicity:
Advanced:
UUID:	{1D8C33F8-CF43-44a6-8E15-D5CC49B29943}
Appears In:	02 National Body Functional View

The details of the non-compliance process are not described in the delegated acts. It was a decision of the NAPCORE that harmonisation up to a certain degree is recommended throughout Europe.<br/>The non-compliance process describes how the National Body should react to non-compliance identified in compliance assessment or other ways. Details are shown within the Non-compliance process description.<br/><br/>

Linked Document
Associations To
Associations From
Advanced

Element	Source Role	Target Role
«FRAME_Low_Level_Data_Flow» Status of CA FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» Update journal information FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» Request FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» Request FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:

Element	Source Role	Target Role
«FRAME_Low_Level_Data_Flow» Response FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» Response FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» Store CA result FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» Status request on SD FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:

Property	Value
isReadOnly:	false
isFinalSpecialization:	0