Details
-
Type:
CR
-
Status:
Closed
(View Workflow)
-
Resolution: Fixed
-
Component/s: None
-
Customer:OMAN-Tel
-
Severity:Minor
-
Classification:CR
Description
Kindly can you assist in the SRd reporting as I need the below information:-
1. SRD’s requests/Completed based on yearly/Staff ID/ Type of service.
As we are reporting below OKR’s we need to map it accordingly, from when the SRD requests come to TAS until all solution is gathered and closed.
Design/Optimize economically cost effective, innovative WAN connectivity ( Fixed, FBB, ILL, DIA, MPLS, MPLS GOLD, P2P, VSAT, WFBB, SIP, WIFI, SDWAN, Ethernet P2P) solutions customized for Enterprise Business corporate clients. Ensuring complete end to end design For
• Network Available within 2 working days,
• partial network Available within 6 working days,
• Green field within 14 working days.
Design/Optimize economically cost effective, innovative Mobile solutions ( RAN/IBS) customized for Enterprise Business corporate clients. Ensuring complete end to end design For:
• Network Available within 2 working days,
• partial network Available within 6 working days,
• Green field within 14 working days
Request raised in GTM
Attachments
Activity
- All
- Comments
- Work Log
- History
- Activity
- Links Hierarchy
- Transitions
- Trace
1.5 wd
After the deployment of patch 3.7.0.1268, the assignee column of the CUSTOM_TASK_FIXED tasks will be filled.
Kindly note that the old data will not change. This feature will apply only to new data.
@salem , plz validate /confirm below 2 bugs are solved and update the ticket status accordingly
• Task SLA report should cover open and closed requests
• Task SLA report custom task should reflect the users who participated in the request from TAS team
we will need to update the old data as well with new custom_task_fixed name via script
fixed as per internal testing , awaiting customer final feedback , to be followed by with other SLA ticket
We will add a new report under the SLA tab called TAS SLA report, which will include the following columns:
Each record will show the duration from the activation date of the CONFIRM_SOLUTION task to the completion of the SOLUTION_ACCEPTANCE task.
The time between these tasks represents the total SLA for TAS, displayed in days (e.g., 2.4 days).
For sure the Total SLA will take into consideration the working hours and weekend / Holidays as configured in SRD.
Note: We will modify the current workflow for fixed services to make CONFIRM_SOLUTION the default task after SELECT_SOLUTION. If SSE wishes to bypass this task, they can select the ‘Skip TAS Confirmation’ option in the Service Resource panel.