Telecom Service Priority -(TSP Field) is not Handled Consistently Across ISR, PSR and ASR

(Doc ID 2342930.1)

Last updated on JUNE 17, 2018

Applies to:

Oracle Communications MetaSolv Solution - Version 6.3.0 and later
Information in this document applies to any platform.

Symptoms

Telecom Service Priority is not handled consistently across ISR, PSR and ASR

The handling and storage of Telecom Service Priority information is inconsistent across order types and results in corrupt or invalid TSP information in MSS.
ISR seems to require a properly formatted TSP (including the hyphen ('-') however stores the TSP WITH the 10th character hyphen ('-')
ASR seems to expect a valid TSP however allows the TSP to be entered with or without the hyphen and stores the TSP without the hyphen, inconsistent with the ISR behavior
PSR seems to require 12 characters to be entered however does not impose any meaningful validation., It stores the 12 characters as-is with no regard to format and the placement of the hyphen.

Due to the critical nature of Telecom Service Priority, it is essential that TSP information be high quality and accurate since the service provider is held accountable for proper tracking, recognition, and handling of priority circuits from a provisioning and restoration perspective.
When specified, TSP information should follow these key integrity rules:
  

TSP code must specify 12 characters
Characters 1-9 (TSP Control ID) most be specified as follows:
Characters 1-3 must specify 'TSP'
Characters 4-9 must specify digits or letters
Character 10 must always be a hyphen ('-')
Character 11 (Provisioning Priority) must be one of the following: E, 1, 2, 3, 4, 5, or 0
Character 12 (Restoration Priority) must be one of the following: Values include 1, 2, 3, 4, 5 or 0

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms