(systems engineering, implementation stretch goal)
Description:
Requestors that create transaction requests on the ONAP Platform, have a need to effectively manage the requests they create. The Requestor is the responsible owner for the transaction and thus, need visibility into the volumes of requests created by a requestor, in order to better balance the workload among their labor resources.

•BSS/OSS system will call the API providing one of the following options:
1.Specific Service Request ID
2.Specific User ID of the Requestor
3.All Users
ONAP will respond with what activity is happening, who is doing it, and how old is it. Profile information can include Service Request Type, Creation/Completion Dates, and User ID of the Requestor. This information may require a dip into VID
Relevance:
Complexity: Average
Prerequisites: Could implement in two phases, 1st phase implement request profile information that is currently available in the Service Orchestration (SO) API, while the 2nd phase add additional status information from VID
Resources: