The approach for working with ports changed after the migration from UPDM2, as outlined below:

  1. For all UPDM2 ports (Node Port and Resource Port), new Operational / Resource Interfaces are created and set as the port types. Separate interfaces are created for each of the ports. The name will be the same as the Type of the port with the keyword In, Out, or Inout added at the end according to the Flow Properties summarized in #2 below (for example, Data In). The location of the keywords will be next to the owner of the port. The new Operational / Resource Interface will be applied as a Type for port. No interface will be created if a port has no type.
  2. Flow Properties are created for all the Interfaces (Operational / Resource / Service Interfaces). The Flow Property type is a Conveyed Item that is conveyed by the connector. The Flow Property direction is specified according to the information flow or relation direction from the current port perspective. If there is no Conveyed Item on the connector between ports, the Flow Property is created, the Port Type from UPDM2 is set as a type, and the direction is inout. If the Types of Ports are the same, the same interface can be reused. The new Flow Property will not be created if the type was Service Interface in UPDM2.
  3. If Service / Request Ports interfaces are already created, they also have operations. Flow Properties will be created according to the parameters of these operations. The same number of Flow Properties and operations will have parameters with the same types. The Flow property direction will be the same as the parameter direction.
  4. Services Access is migrated to Capability Configuration for Request/Service Ports (the new interface, Operational/Resource interface, will be created with a Flow Property).

The validation rules are updated according to all changes.