diff --git a/SOL002/VNFLCMCoordination-API/ApiVersion.robot b/SOL002/VNFLCMCoordination-API/ApiVersion.robot
index 11d89668e2e460ccefea47feb778a69e324dc8cf..8c23db3fe641f20aee540463bb68a3a69c9c6a43 100644
--- a/SOL002/VNFLCMCoordination-API/ApiVersion.robot
+++ b/SOL002/VNFLCMCoordination-API/ApiVersion.robot
@@ -14,7 +14,7 @@ POST API Version - Method not implemented
     ...    Test title: POST API version - Method not implemented
     ...    Test objective: The objective is to test that POST method is not implemented
     ...    Pre-conditions: none
-    ...    Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v3.5.1
+    ...    Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.3.1
     ...    Config ID: Config_prod_VE
     ...    Applicability: none
     ...    Post-Conditions: none    
@@ -26,7 +26,7 @@ GET API Version
     ...    Test title: GET API Version
     ...    Test objective: The objective is to test that GET method successfully return ApiVersionInformation
     ...    Pre-conditions: none
-    ...    Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v3.5.1
+    ...    Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.3.1
     ...    Config ID: Config_prod_VE
     ...    Applicability: none
     ...    Post-Conditions: none 
@@ -39,7 +39,7 @@ PUT API Version - Method not implemented
     ...    Test title: PUT API Version - Method not implemented
     ...    Test objective: The objective is to test that PUT method is not implemented
     ...    Pre-conditions: none
-    ...    Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v3.5.1
+    ...    Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.3.1
     ...    Config ID: Config_prod_VE
     ...    Applicability: none
     ...    Post-Conditions: none 
@@ -51,7 +51,7 @@ PATCH API Version - Method not implemented
     ...    Test title: PATCH API Version - Method not implemented
     ...    Test objective: The objective is to test that PATCH method is not implemented
     ...    Pre-conditions: none
-    ...    Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v3.5.1
+    ...    Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.3.1
     ...    Config ID: Config_prod_VE
     ...    Applicability: none
     ...    Post-Conditions: none 
@@ -63,7 +63,7 @@ DELETE API Version - Method not implemented
     ...    Test title: DELETE API Version - Method not implemented
     ...    Test objective: The objective is to test that DELETE method is not implemented
     ...    Pre-conditions: none
-    ...    Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v3.5.1
+    ...    Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.3.1
     ...    Config ID: Config_prod_VE
     ...    Applicability: none
     ...    Post-Conditions: none 
@@ -75,7 +75,7 @@ POST API Version with apiMajorVerion - Method not implemented
     ...    Test title: POST API version with apiMajorVerion - Method not implemented
     ...    Test objective: The objective is to test that POST method is not implemented
     ...    Pre-conditions: none
-    ...    Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v3.5.1
+    ...    Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.3.1
     ...    Config ID: Config_prod_VE
     ...    Applicability: none
     ...    Post-Conditions: none    
@@ -87,7 +87,7 @@ GET API Version with apiMajorVerion
     ...    Test title: GET API Version with apiMajorVerion
     ...    Test objective: The objective is to test that GET method successfully return ApiVersionInformation
     ...    Pre-conditions: none
-    ...    Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v3.5.1
+    ...    Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.3.1
     ...    Config ID: Config_prod_VE
     ...    Applicability: none
     ...    Post-Conditions: none 
@@ -100,7 +100,7 @@ PUT API Version with apiMajorVerion - Method not implemented
     ...    Test title: PUT API Version with apiMajorVerion - Method not implemented
     ...    Test objective: The objective is to test that PUT method is not implemented
     ...    Pre-conditions: none
-    ...    Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v3.5.1
+    ...    Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.3.1
     ...    Config ID: Config_prod_VE
     ...    Applicability: none
     ...    Post-Conditions: none 
@@ -112,7 +112,7 @@ PATCH API Version with apiMajorVerion - Method not implemented
     ...    Test title: PATCH API Version with apiMajorVerion - Method not implemented
     ...    Test objective: The objective is to test that PATCH method is not implemented
     ...    Pre-conditions: none
-    ...    Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v3.5.1
+    ...    Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.3.1
     ...    Config ID: Config_prod_VE
     ...    Applicability: none
     ...    Post-Conditions: none 
@@ -124,7 +124,7 @@ DELETE API Version with apiMajorVerion - Method not implemented
     ...    Test title: DELETE API Version with apiMajorVerion - Method not implemented
     ...    Test objective: The objective is to test that DELETE method is not implemented
     ...    Pre-conditions: none
-    ...    Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v3.5.1
+    ...    Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.3.1
     ...    Config ID: Config_prod_VE
     ...    Applicability: none
     ...    Post-Conditions: none 
diff --git a/SOL002/VNFLCMCoordination-API/CancelCoordinationActionTask.robot b/SOL002/VNFLCMCoordination-API/CancelCoordinationActionTask.robot
index 8aea9be19015e1d4b4e94b5abbe0acd970713dcd..8f84fa1bd59ac08cdb3c914e103a183640bb1713 100644
--- a/SOL002/VNFLCMCoordination-API/CancelCoordinationActionTask.robot
+++ b/SOL002/VNFLCMCoordination-API/CancelCoordinationActionTask.robot
@@ -15,7 +15,7 @@ POST Cancellation of an Ongoing Individual Coordination Action
     ...    Test title: POST Cancellation of an Ongoing Individual Coordination Action
     ...    Test Objective: The objective is to test that POST request for cancellation of an ongoing individual coordination Action has accepted for processing.
     ...    pre-condition: The status of the related LCM operation occurance is "PROCESSING"
-    ...    Reference: Clause 10.4.4.3.1 - ETSI GS NFV-SOL 002 [2] v3.6.1
+    ...    Reference: Clause 10.4.4.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
     ...    Config ID: Config_prod_VE
     ...    Applicability: When there is an Ongoing individual LCM operation coordination action.
     ...    Post-Condition: none
@@ -28,7 +28,7 @@ POST Cancellation of an Ongoing Individual Coordination Action - Conflict
     ...    Test title: POST Cancellation of an Ongoing Individual Coordination Action - Conflict
     ...    Test Objective: The objective is to test that POST request for cancellation of an ongoing individual coordination Action is not successfull due to a conflict with the state of the "Individual coordination action" resource. 
     ...    pre-condition: none
-    ...    Reference: Clause 10.4.4.3.1 - ETSI GS NFV-SOL 002 [2] v3.6.1
+    ...    Reference: Clause 10.4.4.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
     ...    Config ID: Config_prod_VE
     ...    Applicability: Processing of Individual Coordination Action has 'Finished'.
     ...    Post-Condition: none
@@ -41,7 +41,7 @@ Request a cancellation of an ongoing coordination action without authentication
     ...    Test title: Request a cancellation of an ongoing coordination action without authentication
     ...    Test objective: The objective is to test the failure of the request for a cancellation of a coordination task when no authentication is used
     ...    Pre-conditions: none
-    ...    Reference: Clause Clause 10.4.4.3.1 - ETSI GS NFV-SOL 002 [2] v3.6.1
+    ...    Reference: Clause Clause 10.4.4.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
     ...    Config ID: Config_prod_VE
     ...    Applicability: none
     ...    Post-Conditions: none
@@ -53,7 +53,7 @@ GET Cancellation of an Ongoing Individual Coordination Action - Method not Imple
     ...    Test title: GET Cancellation of an Ongoing Individual Coordination Action
     ...    Test Objective: The objective is to test that GET method for cancellation of an ongoing individual coordination Action is not implemented.
     ...    pre-condition: none
-    ...    Reference: Clause 10.4.4.3.2 - ETSI GS NFV-SOL 002 [2] v3.6.1
+    ...    Reference: Clause 10.4.4.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
     ...    Config ID: Config_prod_VE
     ...    Applicability: ongoing individual coordination
     ...    Post-Condition: none
@@ -65,7 +65,7 @@ PUT Cancellation of an Ongoing Individual Coordination Action - Method not Imple
     ...    Test title: PUT Cancellation of an Ongoing Individual Coordination Action
     ...    Test Objective: The objective is to test that PUT method for cancellation of an ongoing individual coordination Action is not implemented.
     ...    pre-condition: none
-    ...    Reference: Clause 10.4.4.3.3 - ETSI GS NFV-SOL 002 [2] v3.6.1
+    ...    Reference: Clause 10.4.4.3.3 - ETSI GS NFV-SOL 002 [2] v4.3.1
     ...    Config ID: Config_prod_VE
     ...    Applicability: none  
     ...    Post-Condition: none
@@ -77,7 +77,7 @@ PATCH Cancellation of an Ongoing Individual Coordination Action - Method not Imp
     ...    Test title: PATCH Cancellation of an Ongoing Individual Coordination Action
     ...    Test Objective: The objective is to test that PATCH method for cancellation of an ongoing individual coordination Action is not implemented.
     ...    pre-condition: none
-    ...    Reference: Clause 10.4.4.3.4 - ETSI GS NFV-SOL 002 [2] v3.6.1
+    ...    Reference: Clause 10.4.4.3.4 - ETSI GS NFV-SOL 002 [2] v4.3.1
     ...    Config ID: Config_prod_VE
     ...    Applicability: none  
     ...    Post-Condition: none
@@ -89,7 +89,7 @@ DELETE Cancellation of an Ongoing Individual Coordination Action - Method not Im
     ...    Test title: DELETE Cancellation of an Ongoing Individual Coordination Action
     ...    Test Objective: The objective is to test that DELETE method for cancellation of an ongoing individual coordination Action is not implemented.
     ...    pre-condition: none
-    ...    Reference: Clause 10.4.4.3.5 - ETSI GS NFV-SOL 002 [2] v3.6.1
+    ...    Reference: Clause 10.4.4.3.5 - ETSI GS NFV-SOL 002 [2] v4.3.1
     ...    Config ID: Config_prod_VE
     ...    Applicability: none  
     ...    Post-Condition: none
diff --git a/SOL002/VNFLCMCoordination-API/Coordinations.robot b/SOL002/VNFLCMCoordination-API/Coordinations.robot
index fd8e6ccb86ff94e54f417e27b8ab08896790509e..8020da914796eaa61eb8f30517e0aa2843943fe2 100644
--- a/SOL002/VNFLCMCoordination-API/Coordinations.robot
+++ b/SOL002/VNFLCMCoordination-API/Coordinations.robot
@@ -15,7 +15,7 @@ POST Coordination of LCM Operation Occurance and API Producer has Chosen the Syn
     ...    Test title: Post Coordination of an LCM operation occurrence
     ...    Test Objective: The objective is to test the creation of new Individual Coordination Action, and perform a JSON schema validation of the returned LCM coordination data structure.
     ...    pre-condition: LCM operation occurrence resource is in Processing state
-    ...    Reference: Clause 10.4.2.3.1 - ETSI GS NFV-SOL 002 [2] v3.6.1
+    ...    Reference: Clause 10.4.2.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
     ...    Config ID: Config_prod_VE
     ...    Applicability: API producer has chosen the synchronous mode   
     ...    Post-Condition: none
@@ -30,7 +30,7 @@ POST Coordination of LCM Operation Occurance and API Producer has Chosen the Asy
     ...    Test title: Post Coordination of an LCM operation occurrence
     ...    Test Objective: The objective is to test that the coordination of a LCM operation occurance request has been accepted for processing, and perform a JSON schema validation of the returned LCM coordination data structure.
     ...    pre-condition: LCM operation occurrence resource is in Processing state
-    ...    Reference: Clause 10.4.2.3.1 - ETSI GS NFV-SOL 002 [2] v3.6.1
+    ...    Reference: Clause 10.4.2.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
     ...    Config ID: Config_prod_VE
     ...    Applicability: API producer has chosen the asynchronous mode   
     ...    Post-Condition: none
@@ -44,7 +44,7 @@ POST Coordination of a LCM Operation Occurance Forbidden
     ...    Test title: Post Coordination of an LCM operation occurrence Forbidden
     ...    Test Objective: The objective is to test the failure of a request for the coordination of an LCM operation occurrence
     ...    pre-condition: The status of the related LCM opeation occurrence is "PROCESSING". The request is performed by a user that has not the grant to run this operation
-    ...    Reference: Clause 10.4.2.3.1 - ETSI GS NFV-SOL 002 [2] v3.6.1
+    ...    Reference: Clause 10.4.2.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
     ...    Config ID: Config_prod_VE
     ...    Applicability: none  
     ...    Post-Condition: none
@@ -57,7 +57,7 @@ POST Coordination of LCM Operation Occurance Conflict
     ...    Test title: Post Coordination of an LCM operation occurrence Conflict
     ...    Test Objective: The objective is to verify that no coordination actions can be executed currently, due to a conflict with the state of the "Coordinations" resource.
     ...    pre-condition: The status of the related LCM opeation occurrence is not "PROCESSING"
-    ...    Reference: Clause 10.4.2.3.1 - ETSI GS NFV-SOL 002 [2] v3.6.1
+    ...    Reference: Clause 10.4.2.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
     ...    Config ID: Config_prod_VE
     ...    Applicability: When there are many coordination actions exist, or conflicting ones, are in progress.
     ...    Post-Condition: none
@@ -70,7 +70,7 @@ POST Coordination of LCM Operation Occurance Service Unavailable
     ...    Test title: Post Coordination of an LCM operation occurrence Service Unavailable 
     ...    Test Objective: The objective is to test the request for the coordination of an LCM operation occurrence and the verify that the NFVO cannot perform immediately the request, but can perform it sometime in the future. 
     ...    pre-condition: The status of the related LCM opeation occurrence is "PROCESSING" but API producer cannot perform immediately the request
-    ...    Reference: Clause 10.4.2.3.1 - ETSI GS NFV-SOL 002 [2] v3.6.1
+    ...    Reference: Clause 10.4.2.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
     ...    Config ID: Config_prod_VE
     ...    Applicability: API producer has chosen the synchronous mode
     ...    Post-Condition: none
@@ -84,7 +84,7 @@ POST Coordination of an LCM operation occurrence without authentication
     ...    Test title:  Request a Coordination of an LCM operation occurrence without authentication
     ...    Test objective: The objective is to test the failure of the request for the coordination of an LCM operation occurrence without providing an authentication token
     ...    Pre-conditions: The status of the related LCM opeation occurrence is "PROCESSING"
-    ...    Reference: Clause 10.4.2.3.1 - ETSI GS NFV-SOL 002 [2] v3.6.1
+    ...    Reference: Clause 10.4.2.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
     ...    Config ID: Config_prod_VE
     ...    Applicability: none
     ...    Post-Conditions: none
@@ -96,7 +96,7 @@ GET Coordination of a LCM Operation Occurance - Method not implemented
     ...    Test title: GET Coordination of a LCM Operation Occurance - Method not implemented
     ...    Test Objective: The objective is to test that GET method for Resource Coordinations is not implemented.
     ...    pre-condition: none
-    ...    Reference: Clause 10.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v3.6.1
+    ...    Reference: Clause 10.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
     ...    Config ID: Config_prod_VE
     ...    Applicability: none  
     ...    Post-Condition: none
@@ -108,7 +108,7 @@ PUT Coordination of a LCM Operation Occurance - Method not implemented
     ...    Test title: PUT Coordination of a LCM Operation Occurance - Method not implemented
     ...    Test Objective: The objective is to test that PUT method for Resource Coordinations is not implemented.
     ...    pre-condition: none
-    ...    Reference: Clause 10.4.2.3.3 - ETSI GS NFV-SOL 002 [2] v3.6.1
+    ...    Reference: Clause 10.4.2.3.3 - ETSI GS NFV-SOL 002 [2] v4.3.1
     ...    Config ID: Config_prod_VE
     ...    Applicability: none  
     ...    Post-Condition: none
@@ -120,7 +120,7 @@ PACTH Coordination of a LCM Operation Occurance - Method not implemented
     ...    Test title: PATCH Coordination of a LCM Operation Occurance - Method not implemented
     ...    Test Objective: The objective is to test that PATCH method for Resource Coordinations is not implemented.
     ...    pre-condition: none
-    ...    Reference: Clause 10.4.2.3.4 - ETSI GS NFV-SOL 002 [2] v3.6.1
+    ...    Reference: Clause 10.4.2.3.4 - ETSI GS NFV-SOL 002 [2] v4.3.1
     ...    Config ID: Config_prod_VE
     ...    Applicability: none  
     ...    Post-Condition: none
@@ -132,7 +132,7 @@ DELETE Coordination of a LCM Operation Occurance - Method not implemented
     ...    Test title: DELETE Coordination of a LCM Operation Occurance - Method not implemented
     ...    Test Objective: The objective is to test that DELETE method for Resource Coordinations is not implemented.
     ...    pre-condition: none
-    ...    Reference: Clause 10.4.2.3.5 - ETSI GS NFV-SOL 002 [2] v3.6.1
+    ...    Reference: Clause 10.4.2.3.5 - ETSI GS NFV-SOL 002 [2] v4.3.1
     ...    Config ID: Config_prod_VE
     ...    Applicability: none  
     ...    Post-Condition: none
diff --git a/SOL002/VNFLCMCoordination-API/IndividualCoordinationAction.robot b/SOL002/VNFLCMCoordination-API/IndividualCoordinationAction.robot
index 98ef18a02cb3ac9f7fac5bc13a0c8f396318df7c..871540dac54629527625c04dc0f9b6f4f264922c 100644
--- a/SOL002/VNFLCMCoordination-API/IndividualCoordinationAction.robot
+++ b/SOL002/VNFLCMCoordination-API/IndividualCoordinationAction.robot
@@ -14,7 +14,7 @@ POST Individual LCM Operation Coordination Results - Method not implemented
     ...    Test title: POST Individual LCM Operation Coordination Results - Method not implemented
     ...    Test Objective: The objective is to test that POST method for individual LCM operation coordination results is not implemented.
     ...    pre-condition: none
-    ...    Reference: Clause 10.4.3.3.1 - ETSI GS NFV-SOL 002 [2] v3.6.1
+    ...    Reference: Clause 10.4.3.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
     ...    Config ID: Config_prod_VE
     ...    Applicability: none  
     ...    Post-Condition: none
@@ -26,7 +26,7 @@ GET Individual LCM Operation Coordination Results - Coordination is Finished
     ...    Test title: GET Individual LCM Operation Coordination Results
     ...    Test Objective: The objective is to test that coordination is finished and GET method reads individual LCM operation coordination results successfully, and perform a JSON schema validation of the returned LCM coordination data structure.
     ...    pre-condition: LCM operation occurrence resource is in Processing state
-    ...    Reference: Clause 10.4.3.3.2 - ETSI GS NFV-SOL 002 [2] v3.6.1
+    ...    Reference: Clause 10.4.3.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
     ...    Config ID: Config_prod_VE
     ...    Applicability: When the Individual LCM Operation Coordination is finished
     ...    Post-Condition: none
@@ -39,7 +39,7 @@ GET Individual LCM Operation Coordination Results - Coordination is Not Finished
     ...    Test title: GET Individual LCM Operation Coordination Results
     ...    Test Objective: The objective is to test that GET method checks that whether Individual LCM Operation Coordination is still ongoing or in the process of being cancelled.
     ...    pre-condition: LCM operation occurrence resource is in Processing state
-    ...    Reference: Clause 10.4.3.3.2 - ETSI GS NFV-SOL 002 [2] v3.6.1
+    ...    Reference: Clause 10.4.3.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
     ...    Config ID: Config_prod_VE
     ...    Applicability: When the Individual LCM Operation Coordination is still ongoing or in the process of being cancelled.
     ...    Post-Condition: none
@@ -52,7 +52,7 @@ Get Individual LCM Operation Coordination Results without authentication
     ...    Test title:  Get information about a finished coordination task without authentication
     ...    Test objective: The objective is to try to read an individual coordination task without using authentication
     ...    Pre-conditions: none
-    ...    Reference: Clause 10.4.3.3.2 - ETSI GS NFV-SOL 002 [2] v3.6.1
+    ...    Reference: Clause 10.4.3.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
     ...    Config ID: Config_prod_VE
     ...    Applicability: none
     ...    Post-Conditions: none
@@ -64,7 +64,7 @@ PUT Individual LCM Operation Coordination Results - Method not implemented
     ...    Test title: PUT Individual LCM Operation Coordination Results - Method not implemented
     ...    Test Objective: The objective is to test that PUT method for individual LCM operation coordination results is not implemented.
     ...    pre-condition: none
-    ...    Reference: Clause 10.4.3.3.3 - ETSI GS NFV-SOL 002 [2] v3.6.1
+    ...    Reference: Clause 10.4.3.3.3 - ETSI GS NFV-SOL 002 [2] v4.3.1
     ...    Config ID: Config_prod_VE
     ...    Applicability: none  
     ...    Post-Condition: none
@@ -76,7 +76,7 @@ PATCH Individual LCM Operation Coordination Results - Method not implemented
     ...    Test title: PATCH Individual LCM Operation Coordination Results - Method not implemented
     ...    Test Objective: The objective is to test that PATCH method for individual LCM operation coordination results is not implemented.
     ...    pre-condition: none
-    ...    Reference: Clause 10.4.3.3.4 - ETSI GS NFV-SOL 002 [2] v3.6.1
+    ...    Reference: Clause 10.4.3.3.4 - ETSI GS NFV-SOL 002 [2] v4.3.1
     ...    Config ID: Config_prod_VE
     ...    Applicability: none  
     ...    Post-Condition: none
@@ -88,7 +88,7 @@ DELETE Individual LCM Operation Coordination Results - Method not implemented
     ...    Test title: PUT Individual LCM Operation Coordination Results - Method not implemented
     ...    Test Objective: The objective is to test that DELETE method for individual LCM operation coordination results is not implemented.
     ...    pre-condition: none
-    ...    Reference: Clause 10.4.3.3.5 - ETSI GS NFV-SOL 002 [2] v3.6.1
+    ...    Reference: Clause 10.4.3.3.5 - ETSI GS NFV-SOL 002 [2] v4.3.1
     ...    Config ID: Config_prod_VE
     ...    Applicability: none  
     ...    Post-Condition: none
diff --git a/SOL002/VNFLCMCoordination-API/schemas/LcmCoord.schema.json b/SOL002/VNFLCMCoordination-API/schemas/LcmCoord.schema.json
index fdadd65b75a5c0ba3b2036f5cf91b61a1abcc967..e685d25af5ed21c0a201fd0fd674865fadd7f0b8 100644
--- a/SOL002/VNFLCMCoordination-API/schemas/LcmCoord.schema.json
+++ b/SOL002/VNFLCMCoordination-API/schemas/LcmCoord.schema.json
@@ -1,148 +1,148 @@
 {
-    "description": "This type represents an LCM coordination result.\n",
-    "type": "object",
-    "required": [
-      "id",
-      "coordinationResult",
-      "vnfInstanceId",
-      "vnfLcmOpOccId",
-      "lcmOperationType",
-      "coordinationActionName",
-      "_links"
-    ],
-    "properties": {
-      "id": {
-        "description": "An identifier with the intention of being globally unique.\n",
-        "type": "string"
-      },
-      "coordinationResult": {
-        "description": "The enumeration LcmCoordResultType defines the permitted values to represent the result of executing an LCM coordination action. The coordination result also implies the action to be performed by the VNFM as the follow-up to this coordination. Value | Description ------|------------ CONTINUE | The related LCM operation shall be continued, staying in the state \"PROCESSING\". ABORT | The related LCM operation shall be aborted by transitioning into the state \"FAILED_TEMP\". CANCELLED | The coordination action has been cancelled upon request of the API consumer, i.e. the VNFM. The related LCM operation shall be aborted by transitioning into the state \"FAILED_TEMP\".\n",
-        "type": "string",
-        "enum": [
-          "CONTINUE",
-          "ABORT",
-          "CANCELLED"
-        ]
-      },
-      "vnfInstanceId": {
-        "description": "An identifier with the intention of being globally unique.\n",
-        "type": "string"
-      },
-      "vnfLcmOpOccId": {
-        "description": "An identifier with the intention of being globally unique.\n",
-        "type": "string"
-      },
-      "lcmOperationType": {
-        "description": "The enumeration LcmOperationForCoordType defines the permitted values to represent VNF lifecycle operation types in VNF LCM operation coordination actions. * INSTANTIATE: Represents the \"Instantiate VNF\" LCM operation. * SCALE: Represents the \"Scale VNF\" LCM operation. * SCALE_TO_LEVEL: Represents the \"Scale VNF to Level\" LCM operation. * CHANGE_FLAVOUR: Represents the \"Change VNF Flavour\" LCM operation. * TERMINATE: Represents the \"Terminate VNF\" LCM operation. * HEAL: Represents the \"Heal VNF\" LCM operation. * OPERATE: Represents the \"Operate VNF\" LCM operation. * CHANGE_EXT_CONN: Represents the \"Change external VNF connectivity\" LCM operation. * MODIFY_INFO: Represents the \"Modify VNF Information\" LCM operation. * CREATE_SNAPSHOT: Represents the \"Create VNF Snapshot\" LCM operation. * REVERT_TO_SNAPSHOT: Represents the \"Revert To VNF Snapshot\" LCM operation. * CHANGE_VNFPKG: Represents the \"Change current VNF package\" LCM operation.\n",
-        "type": "string",
-        "enum": [
-          "INSTANTIATE",
-          "SCALE",
-          "SCALE_TO_LEVEL",
-          "CHANGE_FLAVOUR",
-          "TERMINATE",
-          "HEAL",
-          "OPERATE",
-          "CHANGE_EXT_CONN",
-          "MODIFY_INFO",
-          "CREATE_SNAPSHOT",
-          "REVERT_TO_SNAPSHOT",
-          "CHANGE_VNFPKG"
-        ]
-      },
-      "coordinationActionName": {
-        "description": "Indicates the actual LCM coordination action. The coordination actions that a VNF supports are declared in the VNFD.\n",
-        "type": "string"
-      },
-      "outputParams": {
-        "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of keyvalue pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 8259. In the following example, a list of key-value pairs with four keys (\"aString\", \"aNumber\", \"anArray\" and \"anObject\") is provided to illustrate that the values associated with different keys can be of different type.\n",
-        "type": "object"
-      },
-      "warnings": {
-        "description": "Warning messages that were generated while the operation was executing.\n",
-        "type": "string"
-      },
-      "error": {
-        "description": "The definition of the general \"ProblemDetails\" data structure from IETF RFC 7807 is reproduced inthis structure. Compared to the general framework defined in IETF RFC 7807, the \"status\" and \"detail\" attributes are mandated to be included by the present document, to ensure that the response contains additional textual information about an error. IETF RFC 7807 foresees extensibility of the \"ProblemDetails\" type. It is possible that particular APIs in the present document, or particular implementations, define extensions to define additional attributes that provide more information about the error. The description column only provides some explanation of the meaning to Facilitate understanding of the design. For a full description, see IETF RFC 7807.\n",
-        "type": "object",
-        "required": [
-          "status",
-          "detail"
-        ],
-        "properties": {
-          "type": {
-            "description": "A URI reference according to IETF RFC 3986 that identifies the problem type. It is encouraged that the URI provides human-readable documentation for the problem (e.g. using HTML) when dereferenced. When this member is not present, its value is assumed to be \"about:blank\".\n",
-            "type": "string",
-            "format": "URI"
-          },
-          "title": {
-            "description": "A short, human-readable summary of the problem type. It should not change from occurrence to occurrence of the problem, except for purposes of localization. If type is given and other than \"about:blank\", this attribute shall also be provided. A short, human-readable summary of the problem type.  It SHOULD NOT change from occurrence to occurrence of the problem, except for purposes of localization (e.g., using proactive content negotiation; see [RFC7231], Section 3.4).\n",
-            "type": "string"
-          },
-          "status": {
-            "description": "The HTTP status code for this occurrence of the problem. The HTTP status code ([RFC7231], Section 6) generated by the origin server for this occurrence of the problem.\n",
-            "type": "integer"
-          },
-          "detail": {
-            "description": "A human-readable explanation specific to this occurrence of the problem.\n",
-            "type": "string"
-          },
-          "instance": {
-            "description": "A URI reference that identifies the specific occurrence of the problem. It may yield further information if dereferenced.\n",
-            "type": "string",
-            "format": "URI"
-          }
+  "description": "This type represents an LCM coordination result.\n",
+  "type": "object",
+  "required": [
+    "id",
+    "coordinationResult",
+    "vnfInstanceId",
+    "vnfLcmOpOccId",
+    "lcmOperationType",
+    "coordinationActionName",
+    "_links"
+  ],
+  "properties": {
+    "id": {
+      "description": "An identifier with the intention of being globally unique.\n",
+      "type": "string"
+    },
+    "coordinationResult": {
+      "description": "The enumeration LcmCoordResultType defines the permitted values to represent the result of executing an LCM coordination action. The coordination result also implies the action to be performed by the VNFM as the follow-up to this coordination. Value | Description ------|------------ CONTINUE | The related LCM operation shall be continued, staying in the state \"PROCESSING\". ABORT | The related LCM operation shall be aborted by transitioning into the state \"FAILED_TEMP\". CANCELLED | The coordination action has been cancelled upon request of the API consumer, i.e. the VNFM. The related LCM operation shall be aborted by transitioning into the state \"FAILED_TEMP\".\n",
+      "type": "string",
+      "enum": [
+        "CONTINUE",
+        "ABORT",
+        "CANCELLED"
+      ]
+    },
+    "vnfInstanceId": {
+      "description": "An identifier with the intention of being globally unique.\n",
+      "type": "string"
+    },
+    "vnfLcmOpOccId": {
+      "description": "An identifier with the intention of being globally unique.\n",
+      "type": "string"
+    },
+    "lcmOperationType": {
+      "description": "The enumeration LcmOperationForCoordType defines the permitted values to represent VNF lifecycle operation types in VNF LCM operation coordination actions. * INSTANTIATE: Represents the \"Instantiate VNF\" LCM operation. * SCALE: Represents the \"Scale VNF\" LCM operation. * SCALE_TO_LEVEL: Represents the \"Scale VNF to Level\" LCM operation. * CHANGE_FLAVOUR: Represents the \"Change VNF Flavour\" LCM operation. * TERMINATE: Represents the \"Terminate VNF\" LCM operation. * HEAL: Represents the \"Heal VNF\" LCM operation. * OPERATE: Represents the \"Operate VNF\" LCM operation. * CHANGE_EXT_CONN: Represents the \"Change external VNF connectivity\" LCM operation. * MODIFY_INFO: Represents the \"Modify VNF Information\" LCM operation. * CREATE_SNAPSHOT: Represents the \"Create VNF Snapshot\" LCM operation. * REVERT_TO_SNAPSHOT: Represents the \"Revert To VNF Snapshot\" LCM operation. * CHANGE_VNFPKG: Represents the \"Change current VNF package\" LCM operation.\n",
+      "type": "string",
+      "enum": [
+        "INSTANTIATE",
+        "SCALE",
+        "SCALE_TO_LEVEL",
+        "CHANGE_FLAVOUR",
+        "TERMINATE",
+        "HEAL",
+        "OPERATE",
+        "CHANGE_EXT_CONN",
+        "MODIFY_INFO",
+        "CREATE_SNAPSHOT",
+        "REVERT_TO_SNAPSHOT",
+        "CHANGE_VNFPKG"
+      ]
+    },
+    "coordinationActionName": {
+      "description": "Indicates the actual LCM coordination action. The coordination actions that a VNF supports are declared in the VNFD.\n",
+      "type": "string"
+    },
+    "outputParams": {
+      "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of keyvalue pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 8259. In the following example, a list of key-value pairs with four keys (\"aString\", \"aNumber\", \"anArray\" and \"anObject\") is provided to illustrate that the values associated with different keys can be of different type.\n",
+      "type": "object"
+    },
+    "warnings": {
+      "description": "Warning messages that were generated while the operation was executing.\n",
+      "type": "string"
+    },
+    "error": {
+      "description": "The definition of the general \"ProblemDetails\" data structure from IETF RFC 7807 is reproduced inthis structure. Compared to the general framework defined in IETF RFC 7807, the \"status\" and \"detail\" attributes are mandated to be included by the present document, to ensure that the response contains additional textual information about an error. IETF RFC 7807 foresees extensibility of the \"ProblemDetails\" type. It is possible that particular APIs in the present document, or particular implementations, define extensions to define additional attributes that provide more information about the error. The description column only provides some explanation of the meaning to Facilitate understanding of the design. For a full description, see IETF RFC 7807.\n",
+      "type": "object",
+      "required": [
+        "status",
+        "detail"
+      ],
+      "properties": {
+        "type": {
+          "description": "A URI reference according to IETF RFC 3986 that identifies the problem type. It is encouraged that the URI provides human-readable documentation for the problem (e.g. using HTML) when dereferenced. When this member is not present, its value is assumed to be \"about:blank\".\n",
+          "type": "string",
+          "format": "URI"
+        },
+        "title": {
+          "description": "A short, human-readable summary of the problem type. It should not change from occurrence to occurrence of the problem, except for purposes of localization. If type is given and other than \"about:blank\", this attribute shall also be provided. A short, human-readable summary of the problem type.  It SHOULD NOT change from occurrence to occurrence of the problem, except for purposes of localization (e.g., using proactive content negotiation; see [RFC7231], Section 3.4).\n",
+          "type": "string"
+        },
+        "status": {
+          "description": "The HTTP status code for this occurrence of the problem. The HTTP status code ([RFC7231], Section 6) generated by the origin server for this occurrence of the problem.\n",
+          "type": "integer"
+        },
+        "detail": {
+          "description": "A human-readable explanation specific to this occurrence of the problem.\n",
+          "type": "string"
+        },
+        "instance": {
+          "description": "A URI reference that identifies the specific occurrence of the problem. It may yield further information if dereferenced.\n",
+          "type": "string",
+          "format": "URI"
         }
-      },
-      "_links": {
-        "description": "Links to resources related to this resource.\n",
-        "type": "object",
-        "required": [
-          "self",
-          "vnfLcmOpOcc",
-          "vnfInstance"
-        ],
-        "properties": {
-          "self": {
-            "description": "This type represents a link to a resource using an absolute URI.\n",
-            "type": "object",
-            "required": [
-              "href"
-            ],
-            "properties": {
-              "href": {
-                "description": "String formatted according to IETF RFC 3986.\n",
-                "type": "string"
-              }
+      }
+    },
+    "_links": {
+      "description": "Links to resources related to this resource.\n",
+      "type": "object",
+      "required": [
+        "self",
+        "vnfLcmOpOcc",
+        "vnfInstance"
+      ],
+      "properties": {
+        "self": {
+          "description": "This type represents a link to a resource using an absolute URI.\n",
+          "type": "object",
+          "required": [
+            "href"
+          ],
+          "properties": {
+            "href": {
+              "description": "String formatted according to IETF RFC 3986.\n",
+              "type": "string"
             }
-          },
-          "vnfLcmOpOcc": {
-            "description": "This type represents a link to a resource using an absolute URI.\n",
-            "type": "object",
-            "required": [
-              "href"
-            ],
-            "properties": {
-              "href": {
-                "description": "String formatted according to IETF RFC 3986.\n",
-                "type": "string"
-              }
+          }
+        },
+        "vnfLcmOpOcc": {
+          "description": "This type represents a link to a resource using an absolute URI.\n",
+          "type": "object",
+          "required": [
+            "href"
+          ],
+          "properties": {
+            "href": {
+              "description": "String formatted according to IETF RFC 3986.\n",
+              "type": "string"
             }
-          },
-          "vnfInstance": {
-            "description": "This type represents a link to a resource using an absolute URI.\n",
-            "type": "object",
-            "required": [
-              "href"
-            ],
-            "properties": {
-              "href": {
-                "description": "String formatted according to IETF RFC 3986.\n",
-                "type": "string"
-              }
+          }
+        },
+        "vnfInstance": {
+          "description": "This type represents a link to a resource using an absolute URI.\n",
+          "type": "object",
+          "required": [
+            "href"
+          ],
+          "properties": {
+            "href": {
+              "description": "String formatted according to IETF RFC 3986.\n",
+              "type": "string"
             }
           }
         }
       }
     }
-  }  
\ No newline at end of file
+  }
+}
\ No newline at end of file