This operation creates a new route (e.g. for restoration purposes) and associates it to the SNC. The route is created in LOCKED state.
A route belongs to only one SNC. However CCs/CTPs can be shared by routes of different SNCs.
A route applies to CCs at the same layer of the SNC. The route identifier must be an unique identifier within the SNC name, with format up to EMS.
It is possible to specify if the creating route is the intended route or not; if intended, then the former intended route is updated to backup route. Only one intended route can be associated to a SNC at a time.
It is possible to specify if the route to be created is exclusive or not; if exclusive, then the EMS must find a route that does not conflict or share CCs with any other existing SNC route, in any administrative state . Once an exclusive route has been created by the EMS, any further creation operation which conflicts with the exclusive route shall be rejected.

The route implicitly inherits from its SNC the following attributes:
- the endpoints
- owner
- direction
- rerouteAllowed
- networkRouted
- connectionRate
- sncType
- staticProtectionLevel
- protectionEffort is considered EFFORT_SAME, i.e. if EMS can not create a route with same static protection level
   as the SNC, the operation is rejected.

Note: The relationship between Bundled SNC service and the SNC with Multiple Routes feature requires further study and is not applicable for v3.0.

Operation Exceptions:
1. NOT_IMPLEMENTED - Raised when the EMS does not provide this operation.
2. INTERNAL_ERROR - Raised in case of non-specific EMS internal failure.
3. INVALID_INPUT - Raised when any input parameter (e.g. createRouteData) is syntactically incorrect.
4. ENTITY_NOT_FOUND - Raised when fields of createRoute refer to an object that does not exist.
5. PROTECTION_EFFORT_NOT_MET - Raised when the NMS requests a route with a static protection level
    (inherited from SNC) that cannot be met by the EMS.
6. UNABLE_TO_COMPLY - Raised when the EMS is unable to find an appropriate route.
    Raised when the EMS can not meet the tolerableImpact requested by the NMS.
    Raised when the EMS is unable to execute the request because at least one of the parameters although valid can
    not be set and that parameter is identified as "not best effort" in additionalInfo.
    If the EMS cannot determine the reason it could not comply, it is also allowed to throw UNABLE_TO_COMPLY.
7. OBJECT_IN_USE - Raised when the route is in conflict with an "exclusive" (even locked) route of another SNC.
8. NE_COMM_LOSS - Raised when communication to managed element is lost and this prevents creation of the route.
9. UNSUPPORTED_ROUTING_CONSTRAINTS - Raised when the EMS does not support the routing constraints specified.
