Scenario SAT

A - Traffic and System Monitoring 13

B - Incident Management 21
C - Urban Traffic Control & Management 1
D - Predefined Plan Management 8
E - Information Dissemination 3
F - Detours and Roadwork 5
G - Maintenance 7
H - Reporting 17
I - User Management 1
J - Video Export 1
Total 77
*TC-B.2.4-001 has been obsolete

Results of Tes
Pass, 60, 86%

Pass C
 SAT Test Execution Summary
Updated on: 2-Feb-2022

Pass C-Pass Fail Deferred Obsolete Total Tested Completion Remarks

11 2 0 0 0 13 100.00%
13 2 0 5 1 21 100.00%
1 0 0 0 0 1 100.00%
8 0 0 0 0 8 100.00%
2 1 0 0 0 3 100.00%
3 1 0 1 0 5 100.00%
6 1 0 0 0 7 100.00%
14 1 2 0 0 17 100.00%
1 0 0 0 0 1 100.00%
1 0 0 0 0 1 100.00%
60 8 2 6 1 77 100.00%

Results of Testcases Executed

60, 86%

C-Pass, 8, 11%
Fail , 2, 3%
Pass C-Pass Fail
Total Testcases 77 100.0%
Tested with RTA 77 100.0%
Remaining 0

Total Tested 77 100.0%

Pass 60 77.9% Checking Purpose TALLY
C-Pass 8 10.4%
Fail 2 2.6%
Obsolete 1 1.3%
Deferred 6 10.0%
S.no Scenario Type Scenario ID Scenario Name

1 A - Traffic and System Monitoring A.1.1 Operator morning shift login and check the
current road network conditions and travel
times in his zone. Traffic in free flow
conditions.

2 A - Traffic and System Monitoring A.1.2 Authorized user morning shift login and
check the current road network conditions
on the videowall after configuring the same.

3 A - Traffic and System Monitoring A.2.1 Traffic congestion on E Road

4 A - Traffic and System Monitoring A.2.2 Traffic congestion on E Road with upstream
RVD field equipment failure
5 A - Traffic and System Monitoring A.2.3 Traffic congestion on E Road with
downstream RVD field equipment failure

6 A - Traffic and System Monitoring A.2.4 Traffic congestion on E Road with upstream
and downstream RVD field equipment failure

7 A - Traffic and System Monitoring A.2.5 Traffic congestion on E Road during heavy fog

8 A - Traffic and System Monitoring A.2.6 Traffic congestion on E Road with nearest
CCTV field equipment failure

9 A - Traffic and System Monitoring A.3.1 Incident Creating a Partial Closure on a Road
in the Network - accident event with manual
detection
10 A - Traffic and System Monitoring A.3.2 Incident Creating a Partial Closure on a Road
in the Network - system detects traffic
accident

11 A - Traffic and System Monitoring A.3.3 Incident Creating a Partial Closure on a Road
in the Network - system detects traffic
accident with nearest CCTV malfunction

12 A - Traffic and System Monitoring A.3.4 Incident Creating a Partial Closure on a Road
in the Network - system detects traffic
accident during heavy fog

13 A - Traffic and System Monitoring A.4.1 Congestion on an E Road during a scheduled

roadblock event.

14 B - Incident Management B.1.1 Congestion on an E Road

15 B - Incident Management B.1.2 Congestion on a E Road (Expressway),

Neighboring D Roads Uncongested
16 B - Incident Management B.1.3 Congestion on a D Road (Arterial),
Neighboring E Roads Uncongested

17 B - Incident Management B.1.4 Congestion on E Roads and D Roads

18 B - Incident Management B.2.1 Incident (main carriageway) Creating a Partial

Closure on a E Road in the Network

19 B - Incident Management B.2.2 Incident (main carriageway) Creating a Partial

Closure (increasing number of lanes blocked)
on a E Road in the Network
20 B - Incident Management B.2.3 Incident (exit) Creating a Partial Closure on a
E Road in the Network

21 B - Incident Management B.2.4 Incident (entrance) Creating a Partial Closure

on a E Road in the Network

22 B - Incident Management B.2.5 Incident (shoulder) Creating a Partial Closure

on a E Road in the Network
23 B - Incident Management B.2.6 Incident Creating a Full Closure on a E Road
in the Network

24 B - Incident Management B.2.7 Incident (main carriageway) Creating a Partial

Closure on a D Road in the Network
25 B - Incident Management B.2.8 Incident (exit) Creating a Partial Closure on a
D Road in the Network
26 B - Incident Management B.2.9 Incident Creating a Full Closure on a D Road
in the Network

27 B - Incident Management B.3.1 Incident Creating a Partial Closure on a E

Road in the Network, with 1 additional
accident upstream
28 B - Incident Management B.3.2 Incident Creating a Partial Closure on a E
Road in the Network, with 1 additional
accident upstream and 1 DMS equipment
failure

29 B - Incident Management B.3.3 Incident Creating a Partial Closure on a E

Road in the Network, with 1 additional
accident at same location

30 B - Incident Management B.3.4 Incident Creating a Partial Closure on a E

Road in the Network, with 1 additional
accident on a parallel road travelling in
opposite direction
31 B - Incident Management B.3.5 Incident Creating a Partial Closure on a E
Road in the Network, with 1 additional
accident upstream and 1 additional accident
32 B - Incident Management B.4.1 Incidents on Multiple
on a parallel Roadsin
road travelling inopposite
the Network -
accident
direction #1 on E road and accident #2 in the
alternate E road in accident #1's response
plan

33 B - Incident Management B.4.2 Incidents on Multiple Roads in the Network -

accident #1 on E road and accident #2 in the
alternate D road in accident #1's response
34 B - Incident Management B.5.1 Congestion
plan on an E Road with weather
condition of Fog.

35 C - Urban Traffic Control & Manag C.1.1 Incident on E road cause an impact on the
parallel signalised corridor. System proposes
RP with GWAV command to relieve the
traffic at the signalised junction.

36 D - Predefined Plan Management D.1.1 Daily recurring event at a fix time in a fix
location with total closure
37 D - Predefined Plan Management D.1.2 Daily recurring event at a fix time in a fix
location with total closure, plus 1 accident
along the alternate route.
38 D - Predefined Plan Management D.1.3 Annual recurring event on a predefined date
39 D - Predefined Plan Management D.1.4 Annual recurring event on a predefined date,
and morning peak hour congestion

40 D - Predefined Plan Management D.2.1 Planned non-recurring event

41 D - Predefined Plan Management D.2.2 Planned non-recurring event, plus accident

on E road (exit) in the vicinity of the event
site.

42 D - Predefined Plan Management D.3.1 Predefined one time event with Manual
Implementation
43 D - Predefined Plan Management D.3.2 Predefined one time event with Manual
Implementation, plus accident on E road
(exit) in the vicinity of the event site.

44 E - Information Dissemination E.1.1 Operator to send and activate display

schedules of a DMS.
45 E - Information Dissemination E.1.2 Operator to retrieve both messages and
schedules from a DMS.

46 E - Information Dissemination E.1.3 Operator to perform diagnostics of DMS

subsystems for pixel failure
47 F - Detours and Roadwork F.1.1 Scheduled Roadworks on a segment of the E
Road with full closure.

48 F - Detours and Roadwork F.1.2 Scheduled Roadworks on a segment of the E

Road with partial closure.

49 F - Detours and Roadwork F.1.3 Scheduled Roadworks on a segment of the E

Road with partial closure, and 1 accident
upstream.

50 F - Detours and Roadwork F.1.4 Scheduled Roadworks for Tunnel with full
closure.
51 F - Detours and Roadwork F.1.5 Scheduled Roadworks for Bridge with full
closure.

52 G - Maintenance G.1.1 System detects and reports equipment fault.

Corrective Maintenance of ATMS equipment
- BT.

53 G - Maintenance G.1.2 System detects and reports equipment fault.

Corrective Maintenance of ATMS equipment
- RVD.

54 G - Maintenance G.1.3 System detects and reports equipment fault.

Corrective Maintenance of ATMS equipment
- RWIS.
55 G - Maintenance G.1.4 System detects and reports equipment fault.
Corrective Maintenance of ATMS equipment
- CCTV.
56 G.1.5 System detects and reports equipment fault.
Corrective Maintenance of ATMS equipment
- DMS.

G - Maintenance

57 G - Maintenance G.1.6 System detects and reports equipment fault.

Corrective Maintenance of ATMS equipment
- TMC.
58 G - Maintenance G.1.7 System detects and reports equipment fault.
Corrective Maintenance of Traffic Signal
equipment.

59 H - Reporting H.1.1 Operator to retrieve detail information of a

specific event.

60 H - Reporting H.1.2 At the end of each work week, the Operator

submits a report of all the accidents occurred
during that week.

61 H - Reporting H.1.3 On the first day of every month, the Operator

to review all the False Incidents of the
previous month.

62 H - Reporting H.1.4 Operator to review all the incidents at the

end of his work shift
63 H - Reporting H.1.5 Operator to review all the Response Plan
activated for his shift.

64 H - Reporting H.2.1 On the first day of every month, the Operator

to review all the Events of the previous
month.

65 H - Reporting H.2.2 On the first day of every month, the Operator

to review all the Events of the previous
month, where he wants to see a breakdown
of the Events by Severity, Source and Zone.

66 H - Reporting H.2.3 On the last day of every week the Operator

to review all the Events by time of that week,
where he wants to see a breakdown of
events by the hour of the day - the morning
peak, evening peek and off peak.
67 H - Reporting H.2.4 At the end of each month, the Operator to
review the Incident and Congestion Hotspots
for that month and how it compares with the
previous months.

68 H - Reporting H.2.5 On the last day of every week, the Operator

to review all the Event Response Plans and
Clearance Timeline of that week.

69 H - Reporting H.3.1 Operator to prepare Traffic Data Report for

External Distribution.

70 H - Reporting H.3.2 Operator to prepare Traffic Data Report for

Internal Distribution.

71 H - Reporting H.3.3 Operator to prepare Traffic Data Prediction

Report

72 H - Reporting H.3.4 Operator to prepare Traffic Data Comparison

Report

73 H - Reporting H.4.1 At the end of the week, the Operator to

review the iTraffic system activities for the
week.

74 H - Reporting H.4.2 At the end of the week, the Operator to

review the activities that he has done for the
week.
75 H - Reporting H.5.1 At the end of the week, the Operator to
review the weather condition for a location

76 I - User Management I.1.1 Administrators can create ATMS application

users. Administrators will be created initially.
Administrators will be given the privileges to
create ATMS application users for specific
role and user group

77 J - Video Export J.1.1. Upon request from external entity or also

from internal entity, the authorized user can
export video to the local workstation and
copy the exported video to external storage
device.
Test Case ID Test Case Description Name of Tester SAT Prod SAT Planned
Version Test Date

TC-A.1.1-001 MONITORING A FREE FLOW ROAD Sundeep 0.9.8.2 27-Sep-21

TRAFFIC NETWORK

TC-A.1.2-001 Monitoring A Free Flow Road Traffic Sundeep 0.9.8.2 3-Oct-21

Network on the Video wall

TC-A.2.1-001 AUTOMATED CONGESTION Azlan 0.9.8.2 28-Sep-21

DETECTION BY SOURCE AID

TC-A.2.2-001 AUTOMATED CONGESTION Sundeep 0.9.8.2 28-Sep-21

DETECTION THROUGH VA AND RVD
EQUIPMENT FAILURE
TC-A.2.3-001 AUTOMATED CONGESTION Lakshmi 0.9.8.2 28-Sep-21
DETECTION THROUGH AID AND
DOWNSTREAM RVD EQUIPMENT
FAILURE

TC-A.2.4-001 AUTOMATED CONGESTION Azlan 0.9.8.2 29-Sep-21

DETECTION THROUGH PMM WITH
UPSTREAM AND DOWNSTREAM
RVD EQUIPMENT FAILURE

TC-A.2.5-001 AUTOMATED VISIBILITY DETECTION Lakshmi 0.9.8.2 29-Sep-21

FROM RWIS AND CONGESTION
PREDICTION FROM PMM

TC-A.2.6-001 AUTOMATED DETECTION OF FOG Lakshmi 0.9.8.2 29-Sep-21

AND CONGESTION AND NO
NEAREST CCTV

TC-A.3.1-001 MANUAL DETECTION OF ACCIDENT Sundeep 0.9.8.2 28-Sep-21

THROUGH CCTV CAUSING PARTIAL
CLOSURE
TC-A.3.2-001 VA SYSTEM DETECTS INCIDENT Sundeep 0.9.8.2 29-Sep-21
THAT CREATES PARTIAL CLOSURE
OF THE ROAD NETWORK

TC-A.3.3-001 AID DETECTS INCIDENT ON E ROAD Xiao Bo 0.9.8.2 30-Sep-21

AND NEAREST CCTV FIELD
EQUIPMENT FAILURE

TC-A.3.4-001 AID DETECTS ACCIDENT IN HEAVY Xiao Bo 0.9.8.2 30-Sep-21

FOG AREA

TC-A.4.1-001 AUTOMATED CONGESTION Deepa Ramesh 0.9.8.2 30-Sep-21

DETECTION WHEN SCHEDULED
ROADBLOCK

TC-B.1.1-001 AUTOMATED CONGESTION Azlan 0.9.8.2 30-Sep-21

DETECTION ON E ROAD AND
IMPLEMENT RESPONSE PLAN

TC-B.1.2-001 AUTOMATED CONGESTION Deepa Ramesh 0.9.8.2 3-Oct-21

DETECTION ON E ROAD AND
IMPLEMENT RESPONSE PLAN
TC-B.1.3-001 AUTOMATED CONGESTION Deepa Ramesh 0.9.8.2 4-Oct-21
DETECTION ON D ARTERIAL ROAD
AND IMPLEMENT RESPONSE PLAN

TC-B.1.4-001 AUTOMATED CONGESTION Deepa Ramesh 0.9.8.2 4-Oct-21

DETECTION ON E & D ROAD AND
IMPLEMENT RESPONSE PLAN

TC-B.2.1-001 INCIDENT ON MAIN CARRIAGEWAY Deepa Ramesh 0.9.8.2 4-Oct-21

CREATING PARTIAL CLOSURE ON E
ROAD

TC-B.2.2-001 AUTOMATED INCIDENT DETECTION Deepa Ramesh 0.9.8.2 5-Oct-21

ON E ROAD CAUSING PARTIAL
CLOSURE AND JAM
TC-B.2.3-001 AUTOMATED INCIDENT DETECTION Azlan 0.9.8.2 5-Oct-21
ON E ROAD EXIT

TC-B.2.4-001 AUTOMATED INCIDENT DETECTION Deepa Ramesh 0.9.8.2 5-Oct-21

ON E ROAD AT ENTRANCE

TC-B.2.5-001 AUTOMATED INCIDENT DETECTION Azlan 0.9.8.2 6-Oct-21

ON E ROAD AT SHOULDER
TC-B.2.6-001 AUTOMATED INCIDENT DETECTION Deepa Ramesh 0.9.8.2 6-Oct-21
ON E ROAD WITH FULL ROAD
CLOSURE

TC-B.2.7-001 AUTOMATED INCIDENT DETECTION Azlan 0.9.8.2 6-Oct-21

ON D ROAD WITH PARTIAL
CLOSURE
TC-B.2.8-001 AUTOMATED INCIDENT DETECTION Deepa Ramesh 0.9.8.2 7-Oct-21
ON D ROAD EXIT
TC-B.2.9-001 AUTOMATED INCIDENT DETECTION Azlan 0.9.8.2 7-Oct-21
ON D ROAD WITH FULL CLOSURE

TC-B.3.1-001 MULTIPLE AUTOMATED INCIDENT Deepa Ramesh 0.9.8.2 7-Oct-21

DETECTION ON E ROAD
TC-B.3.2-001 MULTIPLE INCIDENTS ON E ROAD Lakshmi 0.9.8.2 10-Oct-21
AND DMS EQUIPMENT FAILURE

TC-B.3.3-001 MULTIPLE INCIDENTS ON E ROAD Deepa Ramesh 0.9.8.2 10-Oct-21

CAUSING PARTIAL CLOSURE

TC-B.3.4-001 INCIDENTS ON E ROAD CAUSING Lakshmi 0.9.8.2 10-Oct-21

PARTIAL CLOSURE AND ACCIDENT
IN PARALLEL ROAD IN OPPOSITE
DIRECTION
TC-B.3.5-001 INCIDENTS ON E ROAD CAUSING Lakshmi 0.9.8.2 11-Oct-21
PARTIAL CLOSURE AND MULTIPLE
ACCIDENTS IN PARALLEL ROAD IN
TC-B.4.1-001 INCIDENTS ON MULTIPLE ROADS IN
OPPOSITE DIRECTION Deepa Ramesh 0.9.8.2 11-Oct-21
THE NETWORK - ACCIDENT #1 ON E
ROAD AND ACCIDENT #2 IN THE
ALTERNATE E ROAD IN ACCIDENT
#1'S RESPONSE PLAN

TC-B.4.2-001 INCIDENTS ON MULTIPLE ROADS IN Lakshmi 0.9.8.2 11-Oct-21

THE NETWORK - ACCIDENT #1 ON E
ROAD AND ACCIDENT #2 IN THE
TC-B5.1-001 CONGESTION
ALTERNATE D ON
ROADANIN
E ROAD WITH
ACCIDENT Deepa Ramesh 0.9.8.2 12-Oct-21
WEATHER CONDITION
#1'S RESPONSE PLAN OF FOG

TC-C.1.1-001 INCIDENT ON E ROAD CAUSE AN Deepa Ramesh 0.9.8.2 12-Oct-21

IMPACT ON THE PARALLEL
SIGNALISED CORRIDOR

TC-D.1.1-001 Create a Daily Recurring Predefined Lakshmi 0.9.8.2 12-Oct-21

Plan Event via Event Management
Implement Predefined Daily
TC-D.1.2-001 Recurring Scheduled Event and Lakshmi 0.9.8.2 13-Oct-21
Update the Response plan as
Create anhappened
accident Annual Predefined
in alternate
TC-D.1.3-001 Recurring
route. Scheduled Event on a Lakshmi 0.9.8.2 13-Oct-21
predefined date via Event
Management
TC-D.1.4-001 Lakshmi 0.9.8.2 13-Oct-21
Annual Predefined recurring event
on a predefined date, and morning
peak hour congestion
TC-D.2.1-001 PREDEFINED NON-RECURRING Lakshmi 0.9.8.2 13-Oct-21
PLANNED EVENT [ONETIME EVENT]

TC-D.2.2-002 PLANNED NON-RECURRING EVENT, Lakshmi 0.9.8.2 14-Oct-21

PLUS ACCIDENT ON E ROAD (EXIT)
IN THE VICINITY OF THE EVENT SITE

TC-D.3.1-001 Predefined one time event with Lakshmi 0.9.8.2 14-Oct-21

Manual Implementation
TC-D.3.2-001 Predefined one time event with Lakshmi 0.9.8.2 14-Oct-21
Manual Implementation, plus
accident on E road (exit) in the
vicinity of the event site.
TC-E.1.1-001 OPERATOR TO SEND AND ACTIVATE Sundeep 0.9.8.2 28-Sep-21
DISPLAY SCHEDULES OF A DMS
TC-E.1.2-001 OPERATOR TO RETRIEVE BOTH THE Sundeep 0.9.8.2 28-Sep-21
MESSAGES AND THE SCHEDULE OF
ANY DMS SIGN

TC-E.1.3-001 DMS ROUTINE DIAGNOTICS Sundeep 0.9.8.2 28-Sep-21

TC-F.1.1-001 SCHEDULED ROADWORKS ON A Lakshmi 0.9.8.2 17-Oct-21

SEGMENT OF THE E-ROAD WITH
FULL CLOSURE

TC-F.1.2-001 SCHEDULED ROADWORKS ON A Lakshmi 0.9.8.2 17-Oct-21

SEGMENT OF THE E-ROAD WITH
PARTIAL CLOSURE

TC-F.1.3-001 SCHEDULED ROADWORKS ON A Lakshmi 0.9.8.2 17-Oct-21

SEGMENT OF THE E ROAD WITH
PARTIAL CLOSURE, AND 1 ACCIDENT
UPSTREAM
TC-F.1.4-001 SCHEDULED ROADWORK FOR Lakshmi 0.9.8.2 18-Oct-21
TUNNEL WITH FULL CLOSURE
TC-F.1.5-001 Scheduled Roadwork for Bridge with Lakshmi 0.9.8.2 18-Oct-21
full closure.

TC-G1.1-001 SEND SERVICE REQUEST TO AMS Azlan 0.9.8.2 28-Sep-21

MANUALLY FOR AN AUTO-
ACKNOWLEDGED BT ALARM

TC-G1.2-001 ACKNOWLEDGE RVD EQUIPMENT Azlan 0.9.8.2 28-Sep-21

ALARM AND SEND SERVICE
REQUEST TO AMS FROM ALARM
NOTIFICATION
TC-G1.3-001 ACKNOWLEDGE RWIS EQUIPMENT Azlan 0.9.8.2 28-Sep-21
ALARM AND SEND SERVICE
REQUEST TO AMS MANUALLY
TC-G1.4-001 ACKNOWLEDGE CCTV EQUIPMENT Azlan 0.9.8.2 28-Sep-21
ALARM AND SEND SERVICE
REQUEST TO AMS MANUALLY
TC-G1.5-001 ACKNOWLEDGE DMS EQUIPMENT Sundeep 0.9.8.2 19-Oct-21
ALARM AND SEND SERVICE
REQUEST TO AMS MANUALLY

TC-G1.6-001 SEND SERVICE REQUEST TO AMS Azlan 0.9.8.2 19-Oct-21

FOR AN AUTO-ACKNOWLEDGED
TMC ALARM FROM EQUIPMENT
ALARM
TC-G1.7-001 ACKNOWLEDGE TS EQUIPMENT Azlan 0.9.8.2 19-Oct-21
ALARM FROM ALARM
NOTIFICATION

TC-H.1.1-001 OPERATOR TO VERIFY THE EVENT Geethanjali 0.9.8.2 27-Sep-21

DETAILS AND TIMELINE REPORT.

TC-H.1.2-001 OPERATOR TO VERIFY THE EVENT Geethanjali 0.9.8.2 27-Sep-21

SUMMARY REPORT

TC-H.1.3-001 OPERATOR TO VERIFY THE FALSE Geethanjali 0.9.8.2 27-Sep-21

EVENT ALARM REPORT.

TC-H.1.4-001 OPERATOR TO VERIFY THE Geethanjali 0.9.8.2 25-Oct-21

INCIDENT SUMMARY REPORT
TC-H.1.5-001 OPERATOR TO VERIFY THE Geethanjali 0.9.8.2 27-Sep-21
RESPONSE PLAN SUMMARY
REPORT.

TC-H.2.1-001 OPERATOR TO VERIFY THE EVENTS Geethanjali 0.9.8.2 25-Oct-21

BY ITS TYPE

TC-H.2.2-001 OPERATOR TO REVIEW ALL THE Geethanjali 0.9.8.2 26-Oct-21

EVENTS BY ZONE LEVEL

TC-H.2.3-001 OPERATOR TO REVIEW THE EVENTS Geethanjali 0.9.8.2 26-Oct-21

BY ITS TIME
TC-H.2.4-001 OPERATOR TO VERIFY THE EVENTS Geethanjali 0.9.8.2 26-Oct-21
BY ITS SEVERITY

TC-H.2.5-001 OPERATOR TO REVIEW ALL THE Geethanjali 0.9.8.2 26-Oct-21

EVENT RESPONSE PLANS AND
CLEARANCE TIMELINE.

TC-H.3.1-001 VERIFY IF OPERATOR CAN Geethanjali 0.9.8.2 26-Oct-21

GENERATE TRAFFIC DATA REPORT
FOR EXTERNAL DISTRIBUTION
[SUMMARY]

TC-H.3.2-001 VERIFY IF OPERATOR CAN Geethanjali 0.9.8.2 26-Oct-21

GENERATE TRAFFIC DATA REPORT
FOR INTERNAL DISTRIBUTION
[SUMMARY]
TC-H.3.3-001 VERIFY IF THE TRAFFIC PREDICTION Geethanjali 0.9.8.2 24-Oct-21
REPORTS ARE GENERATED

TC-H.3.4-001 VERIFY THE TRAFFIC COMPARISON Geethanjali 0.9.8.2 24-Oct-21

REPORTS ARE GENERATED

TC-H.4.1-001 VERIFY THE ITRAFFIC SYSTEM LOG Geethanjali 0.9.8.2 24-Oct-21

REPORTS ARE GENERATED

TC-H.4.2-001 VERIFY THE USER ACTIVITY REPORTS Sundeep 0.9.8.2 25-Oct-21

ARE GENERATED
TC-H.5.1-001 OPERATOR TO RETRIEVE DETAIL Geethanjali 0.9.8.2 25-Oct-21
INFORMATION OF WEATHER FOR
PARTICULAR LOCATION

TC-I.1.1-001 PRIVILEGED USER CAN CREATE NEW Sundeep 0.9.8.2 26-Oct-21

USER.

TC-J.1.1-001 EXPORT VIDEO FROM THE SYSTEM Sundeep 0.9.8.2 3-Oct-21

UPON REQUEST
SAT Actual POL Test
Test Date Witness Status
[C-Pass /
Pass /
31-Oct-21 Umair Pass
Fail]

31-Oct-21 Umair Pass

28-Nov-21 Rahim Pass

15-Jan-22 Khalid Pass

21-Nov-21 Rahim Pass

15-Jan-22 Rahim C-Pass

28-Nov-21 Rahim Pass

30-Oct-21 Rahim Pass

15-Jan-22 Rahim/Khalid Pass

29-Dec-21 Rahim C-PASS

31-Oct-21 Khalid Pass

21-Dec-21 Rahim Pass

28-Nov-21 Rahim Pass

21-Dec-21 Rahim C-Pass

3-Jan-22 Rahim Pass

15-Nov-21 Rahim Deferred

20-Nov-21 Rahim Pass

26-Oct-21 Rahim Deferred

14-Nov-21 Rahim Deferred

28-Oct-21 Rahim Pass

14-Nov-21 Rahim Obsolete

28-Oct-21 Rahim Pass

14-Nov-21 Rahim Deferred

27-Oct-21 Rahim Pass

16-Nov-21 Rahim Pass

28-Oct-21 Rahim Pass

8-Nov-21 Rahim Pass

28-Oct-21 Rahim/ Pass
Khalid

29-Oct-21 Rahim Deferred

31-Oct-21 Rahim Pass

1-Nov-21 Rahim Pass

17-Nov-21 Rahim Pass

31-Oct-21 Rahim Pass

4-Jan-22 Rahim C-Pass

18-Nov-21 Khalid Pass

30-Sep-21 Rahim PASS

29-Sep-21 Rahim PASS

29-Sep-21 Rahim PASS

30-Sep-21 Rahim PASS

30-Sep-21 Rahim PASS

30-Sep-21 Rahim PASS

30-Sep-21 Rahim PASS

30-Sep-21 Rahim PASS

2-Feb-22 Khalid C-Pass

3-Oct-21 Rahim/ PASS
Khalid

14-Oct-21 Khalid Pass

3-Jan-22 Rahim C-Pass

14-Nov-21 Rahim Pass

6-Oct-21 Rahim Pass

5-Oct-21 Rahim Pass

15-Jan-22 Rahim Deferred

4-Oct-21 Khalid Pass

5-Oct-21 Khalid Pass

18-Oct-21 Khalid Pass

4-Oct-21 Khalid Pass

13-Jan-22 Khalid Pass

25-Oct-21 Umair Pass

20-Nov-21 Khalid C-Pass

9-Nov-21 Khalid Pass

28-Dec-21 Khalid Pass

9-Nov-21 Khalid Pass

19-Oct-21 Khalid Pass

25-Jan-22 Khalid Pass

14-Oct-21 Khalid Pass

20-Nov-21 Khalid Pass

25-Nov-21 Khalid Pass

18-Nov-21 Khalid Pass

24-Oct-21 Khalid Pass

24-Oct-21 Khalid Pass

20-Nov-21 Khalid Pass

14-Nov-21 Khalid Pass

14-Nov-21 Rahim Pass

22-Nov-21 Khalid Fail

2-Feb-22 Khalid Fail

18-Dec-21 Rahim C-pass

29-Jan-22 Rahim Pass

24-Oct-21 Khalid Pass

POL Comments RTA
Comments

Oct 31st :-
D92/05 CCTV shows traffic is NOT CONGESTED, but GIS is showing traffic
congestion on 3 sides of functions

MPV should allow the user to move the camera with in the grid. [Drag and
drop CCTV equipment between the screens inside the grid] -P4

Step 1.
-GIS is very
Oct 31st :- slow in loading & refreshing maps.
-GIS
D92/05 CCTVof
preview speedtraffic
shows is notisrealtime.
NOT CONGESTED, but GIS is showing traffic
congestion on 3 sides of functions
Step 2. Fail show dstance to the destination from origin point. It is good to
TT doesn’t
-No LOS show despite
have estimated distance volume
also to&destination.
LOS is calculated example link id:
17840005983733
-Volume
AID is notdata
workingis available
properly butand
notcan
used
not(not consistent)
continue with SAT while AID is not
-Add RVD
doing any Lane diagram
detection. ThisinisRVD details.D63
informed to XiaoRVD02
Bo already
1. One camera rightly selected but second camera was not selected rightly [C
StepC3.
55, 59]
-Latency
2. in video
Zone details arecontrol
missing& video quality is not right up to mark
3.congestion alarm doesnt disappear after making alarm true[GIS refresh
Step
issue]4 & 5. Fail
-Camera
4.Lane video performance
blockage is not updated is poor in iTraffic
for heavy mpv
traffic & GIS,
event latency
which observed.
is created in RVD
-Jostick feature
location by AID.are nottoused/not
It has be included.working for keypad and other buttons.
-Joystick
5.we need preset
to add nosource
programmed.
in filter and report
- In type "Dropdown", The type is duplicated for alarm/alert
Step
-In 6. CPass no dropdown
equipment
-CCTV"others"
-The E11CCTV48-C13
should bewrong on TOP location
-Sometimes
-Default CCTV all
selection failfor
to the
connect to server
equipment error.
is not enabled
-Not all has
-LinkID CCTV to in
beglobal
included tourindisplaying.
the report
-CCTV appearing in GIS but not in MPV.

Step 7. CPass
-Switching the screen takes time to load cameras loading.

Step 8.. Fail

-The Travel Time does not reflect the actual status. TT is Red (congested) but
VA alarm
in GIS was generated
showing influx but
Green. Example didn'tIDappear
journey 21938 in iTRAFFIC (DISAT-35)
VA Fallen Object false alarms from D54CCTV01 (DISAT-44)
VA
StepPedestrian
9. CPass False Alarms (DISAT-49)
VA Inverse Direction
-Current Travel Time False
is notAlarms
shown (DISAT-50)
in the detailed page
1) Event Monitoring camera lock issue (DISAT-65)
2) Location
Step of VA alarm is not located on the detection area instead located at
10. CPass
the
-Freeflow onlocation.
camera GIS does(IT-7520)
not match with detail shown in Travel Time on all
journey

Step 12. CPass

-Report header is missing in the report
-Filter shall allow multiple selection of RVDs or by Road
-No search option available for device selections
GIS Map very slow while performing "Go to map" function
In Alarm Details page, Alarm Type CF should be explanded as "Constant Fault"
(P4)

Additional category for Predicted Congestion Alarm for PMM (DISAT-45)

Consolidate PMM alarm instead of individual alarm on each links (DISAT-46)
24-Oct-2021:-
Road code needs to be displayed in PMM alarms instead of road names
Alarm details with thresholds and explaination to be added in "Help" section
for operational understanding
On GIS, PMM alarms to be shown on separate layer with check box for each
interval.
Alarm validation

Oct 31:-
Response Plan message and content is subjected to RTA feedback. The
contractor to update/edit the message as per client feedback
Event type in weather/fog:-
1) Event and response plan is updated based on weather value
2) If event is on auto update, then the weather value should be updated
automatically
3) Event Severity is not high event if visibility < 75m, < 150m
4)DMS message in english is good, but arabic still seems to be not central
aligned.
1. Data in RVD report doesn’t match to AID alarm (AID speed:42kph,
RVD:94kph, So congestion not valid) [DISAT-66]-P4
2. At congestion location the congestion location or queue length did not
update [DISAT-67]-P2
3. RVDPerformance
CCTV checked for comments
e44RVD13 same
& alarm no1.1
as A 476537 didnt match
4.Response
Unable plan toPTZ
to control be and
updated as per RTA
not working comment
properly
Latency in video control & video quality is not right up to mark
Camera video performance is poor in iTraffic mpv & GIS, latency observed.
Jostick feature are not used/not working for keypad and other buttons.
Unable to add additional camera into the event after event is created
System recommended event location is not correct
Unable to view CCTV Snapshot after creating
Routing of Response Plan is not correct [FRC Codes not maintained]
Retested-8-Nov-2021
1. CCTV cannot be added after creating event
2. While creating event the added cctv cannot be removed or updated
3. No indication message when reached he maximum no of cameras that can
be added in the event.
1) Event Monitoring camera lock issue (DISAT-65)
2) Location of VA alarm is not located on the detection area instead located at
the camera location. (IT-7520)
Nov 15 2021:-
Bookmark to be created and tagged to a VA alarm. This is in addition to the
existing image.
The Video Bookmark for all VAS Alarms and can be deleted if marked as FALSE
or is unverified for 5 - 10 days (sys-param)

Incident alarm from AID is not generated during the test period. Verified from
congestion alarm

Weather condition such as visibility doesn’t get updated from the alarm to
event management. This causes no creation of response plan.Issue occurs
only in Gis layer.creating from EM is not an issue.
Preview of DMS message ; if TT is implemented is not seen.
2. Blue circle and equipment selection when go to map for equipment is not
shown

16th Nov 2021:- (Retested on -16-Dec-2021)

Event created from EM<-GIS [WEA-Alarm] doesnt have the description of
alarm -P3

Lane Number / No of Lanes should be displayed from GIS "Right click on any
link and choose "Info" [P3]

AID alarm came in the same link place where event was open.which is
unexpected.
16th Nov 2021:-
AID ->Congestion and Heavy Traffic Or Accident are filtered , Add Road Block -
DISAT-72

1. Congestion alarm is shown at the middle or tail of the congestion queue

2. User should be able to navigate to the map by clicking on alarm window
[should have go to map option inside alarm details window also]
3. Event 20211010/0041 , Camera:- E311CCTV27, Snapshots are not taken
properly
4. Camera Focus was wrong
5. "Send to MPV" not working before we save the event created from an
alarm
6. Qlength calculated is wrong, only shorter Qlength is considered.
7. For any event, if there is no RVD [Source to change lane info] then the lane
blockage is updated
1. When Event by fron
created the user shall take
congestion precedence.
alarm, Current
congestion issueisisnot
end point even if
the user update, the lane info where there is no RVD and
updated by the system even though the queue length was 2061 (m) if the event
"autoupdate" checked,
2. Almarakah street Exitthe AID will
should switchinitthe
be added to normal
system configuration
24th Oct 2021:-
3. For traffic congestion the severity is low (Need to confirm this with
While opening an alarm from GIS Map, there should be an option to send
operations)
CCTV Cameras to MPV
9th Nov 2021:-
1. Recurring congestion & congestion due to incident/event are not
differentiated-
2.Alarms shall not be generated if the link is already part of queue length for
another generated alarm
No Alarm detected for arterial (D) road - while congestion can be seen from
GIS
Nov 15th 2021:-
AID detection on D-Roads are not working except for few locations. The AID
Model for D-Roads to bet trained and properly tuned to cover all D-Roads.
SAT Scenarions related to congestion & incident detection on D-Roads can not
be continued, until the AID performance is improved for D-Roads as well.

Subject to successful completion of AID performance

1. Event severity updated to high from low. No response plan generated

when the event updated again from low to high
2. Diversion routes are not reasonable one plan is correct but the other plan is
through the local streets.
3. UI Issues noted Slow response for changing lanes
4. In Historical Plan, when plan 1 is clicked the diversion route is displayed in
the GIS minimap but when plan 2 is clicked the second plan's diversion route
is not displayed in the GIS minimap. It always shows only 1 route either plan 1
or plan 2

1. Detection rate and performance is not up to the mark, This has to be

enhanced and update the model specially for D-Road
2. No incident alarm generated even at location of incidents
3. Our alarm generated but with false update by lane blockage (111 to 112)
4. AID - D-Road model did not detect incident at location of RVD with lane
speed =0 (For E-Road one example is there)
5. The event does not update low-->med-->high
severity din't change automatically when the event open time is reached to
threshold value

Nov 14th 2021:-

1. Incident Alarms can only be generated at RVD Location at down stream link
of AID segment

2. Subject to Successful completion of AID performance

Tested using congestion alarm. No Incident alarm is detected. No-Alarm

detected for incident in the whole week history.
Update - 14-Nov-2021
1. Incident alarms can oly be generated at RVD locations at downstream link
of AID segment
2. Subject to successfull completion of AID performance
Not tested with automated detection, Used Congestion alarm

1. No Alarm detected at any exit/entrance/ramp/interchange, no historical

data available
2. Blue circle and equipment selection was not shown while doing "Go to
map" function

1. Incident not detected at all the locations though speed is below10kph

2. E44 RVD13 does not show incident situation while CCTV confirmed
3. RVD reported shall provide lanewise speed data to verify
4. E44RVD13 :Didn't show incident at 7:24 am
Ref:E44CCTV10 Confirmed incident
5. No diversion route proposed
6. For high severity event only, one RP is proposed. Location E311[N]
20211028/0167
Nov 11 2021:-
Event 20211110/0026
Incident occured and had road impact but the AID didnt detect any alarm.
UpStrean links showed low speed profiles
14-Nov-2021
1. Incident alarms can oly be generated at RVD locations at downstream link
of AID segment
2. Subject to successful completion of AID performance

1. System is very slow, GIS is very slow in response

2.Updating Lane Blockage is very non-responsive
3. In report, event with timeline graph report and event details like alarm and
No
linkIncident
Id shouldalarm raised, Have to use congestion alarm
be included
For full closure,
4. Diversion Default
route is notwill be highby, No
proposed theauto change from low to high
system
severity
5.No twoisdiversion
applicableroute is proposed for event ID 0087
Depend on near
6. No incident by RVD.
alarm, onlyIfcongestion
near by RVD available,
alarm is usedlane blockage changes will
be performed automatically
1. The message previewed & generated in response plan was different than
the message sent to DMS[e44test] ref event: 29/0025. TT was available for
that DMS at the time and previewed
2. when response plan was executed with guide zone message, the displayed
message in the DMS equiment changed to alert message after sometime.The
event was executed at 13:41 but the DMS was updated at 13:50 with out any
intervention and the event log didnt show any information on this update.
3.Event log time of execution & DMS message log time didnt match
4.Arabic translation for "Massive Jam after hessa street" is wrong
1. AID did not change the event severity from medium to high after 120 mins
2. Once message is posted from EM, DMS goes offline, the current message is
showing incorrectly
3. Event :- 20211027/0056 and 0057 when multiple events are executed ,the
alert zone, message replaced the guidezone message based on the time .
Though the severity is same and the event is updated the alert zone
Message didnt get updated from the guide zone message

Unable to merge two incident events at the same location with merged event
into & update the response plan
When 2 incident events are merged, the details of two response plan should
be captured in the primary event and response plan should be based on both
the events.[congestion & lane blockage]
details of
Tested both
with the events
response planshould
as per be merged
message to one event
structure anddesign
in FSDD Response plan
should
any be generated.
feedback from RTA ops related to DMS message to be implemented

Alternate routes generated for E-roads are not on E or major roads. It goes
into small streets [Major Issue highlighted] 20201031/0051 and 0046]
Retested on 8-Nov-21 :-
1. Response plan diversion route is wrong, Incase of road closure diversion
route going through the closed lane & Two diversion route not generated for
high severity - EVENT no"20211108/0023"
2. Response plan is configuration to be improved "20211108/0031" - No
major difference seen n both the response plan. "20211108/0024" - Diversion
route is showing unwanted extra travelliing, start point can be syncronised.

Wrong response plan

wrong event severity even if it closes the road
weather data type not filled in event info
Event severity is selected as "low" even if weather [visibility]caused road
closure
For road closure level, event severity to be high
weather type is not selected from alarm [For fog alarm, it shall select visibility]
In historical plan,and
20211030/0048 the0047]
TS comments added in the response plan is not
displayed in detail
DMS selection didnt follow the zone A & B perimetre as per system
in case of 2 response
parameters. plan's the plan number is not displayed in historical
[20211030/0047]
plan.
Update:
Weather value for visibility shall be auto updated by the system to generate
response plan based on the system parameters. (DISAT112)
Nov 15th 2021:-
Event :- 20211115/0032, for E11DMSG12N[A]
The pictogram needs to be added to the Zone B Weather related event
messages.
Test Case - E.1.1 - 001
1st Test Case-1.6
-> Manual Refresh is required for the OFFLINE DMS
-> Full image pictogram not functioning for Type C
-> Scheduling has an issue in posting and removing the sign, when posting the
message 5 Secs delay and whenremoving the message 20 secs delay
2nd Test Case - 1.6.1
Test Procedure to be updated--- Done
3rd Case - 1.6.2
->The Travel Time generated is incorrect, looks like double of the actual time
for some joutneys
-->Multiple mid points required
-> Current TT is not shown in the detail page
-> Mini Map sometimes takes too much time to load
-> Distribution toggle not working UI Issues
28th Oct 2021:-
Current TT in predicted TT window is not shown
Selected midpoint reappear after reopening alternate route tab
Route generation to be imporved with out midpoint
16th Nov 2021:-
Detected midpoint reappear after reopening alternate route
Route generation to be improved [W/O midpoints]
water mark issue in Pixel preview -> webservice is used NTCIP Pixel Status
1. System Parameter Configuration must be added in test procedure for pre-
conditions [Added]
2.For Full closure roadworks, the severity shall be "high"
3. System shall select all lane closed when event subtype roadclosure is
chosen
4.Reset/Refresh button shall allow the user to reset the event information
filled in initial state
5. Response Plan not requested when the event is saved. When scheduled
event
1. Alertis Zone
saved, the response
message plan should
to be updated be RTA
as per generated same time.
ops remarks
6.Arabic Translation of DMS Messages are wrong
2. Gis Map doesn't maximize properly when user choose to enlarge from
minimap
3. E44 road direction is to be updated
E44 [E] --> E44[N]
E44[W]--> E44[S]
4.MPV failed to create a new tab when multiple DMS is sent for viewing from
event response plan mini map
5. Rejected DMS should be circled in red color
Note:-
The message structure/content to be updated based on client/RTA feedback

1.System to handle landmarks i.e., tunnel & bridges with its name
2.Rule bases Response Plan can't be applied on tunnel closure. Only case
based can be used currently
1.
3. Diversion routestravel
Need to attach are completely
time to usewrong
message in the case library
2.
4. When
Need tocase
addbase response
an option plan is used
to duplicate theand
casemajor
basedevent
plan is
toselected, userones
create New is
unable to evaluate the response plan
[Resuable]
3.In Case
5. The rulebased
basedparameters, user can only
Alert Zone message to beselect oneas
updated link and
per RTAonly that link to
operations
be matched which is not practical. Range links [start and end] to be able to be
feedback
selected. Otherwise user has to create one response plan for each link of
event of same attribute
4.In Casebased response plan, user shall add route of the response plan
[desired route]. system shall allow to create a response plan route simply in
the case base plan. Then the same route to be used in event management
response plan. If major event,then this shall not be sent to PMM along the
system generated route for evaluation.

Unable to send RVD Warning alarm to AMS

RWIS /Send to AMS/ Flag error due to not added in InforEAM

Require Hierarchy Structure for RWIS in InforEAM
1)Ack Time shown 12/10/2021 00:00:00 incorrect when device turn online
(DISAT68
2)The DMS status in detail page is not sync with the DMS Alarm page[41]
(DISAT 68
3)Send DMS message to offline DMS , The error is misleading (UAT is ok)

1. Receiving too many unwanted false alarms.

Equipment goes up and down frequently, but in actual location there is no
issue in traffic signal equipment
2.INFOREAM is not integrated with the iTrafficAD and is not able to sign in
using sso
3. The mechanism for finding intersections (junctions) on iTraffic map
Step 4.1:- Linked
The method CCTV details
of searching for aare not present.
specific junctionRecovery time
is different fromonthe
event time
method
line is not adjusted .
of searchingfor RVD or DMS.
Step 5:-Response
e.g. When writtingplan
the ID is not is
junction not displayed ,it
numberwithout hasoptions
J, all only request
relatedID.
toStep
the
6.Plan
same number are displayed, and when writting the junction number withgive
ID should be there in event log details and it should clickable and
the fullJ or
letter details of thescan
the entire palnnumber,
ID. system does not give any option.
Searchig TS signals should be similar to the number displayed in GIS map.
Step 1:-Report is taking long time to load.
Step 2:-Report name does not appear in the header before loading of the
report.
Step 6:-Deleted event are not shown in the event report.details of the deleted
events should be present.

Step 5 :- Loading bar is invisible when click on the event

Step 6 :- Updated date is not there in the report
Step 7:- Header of the child report is not in the center [In PDF Format]
Step 8:- Word is not aligned properly [E.g.,EIS_TRAFFICDATA] Under (Source )
--> PDF is breaking into 2 page for the first report
Step 1 :- There is no loading process once we click the plan ID.
The report shows details of PLAN 3 where there is no plan 3.
Step 2 :- Response plan report doesnt show the route information proposed in the
response plan.
Step 3:- Two plans created at the same time,while showing no data for the second.
Step 4:- There is an error in plan name like plan 3
Step 5 :- It is unclear which plan ID is revised and there are no details which is
implemented on plan ID
Step 6:- End user can not see the purpose of change in plan ID [For Eg., change in
DMS/ Addition of DMS/ Change in DMS message/Adding CCTV]
6. After loading of the response plan page, the landing page is on the middle hich
should target on top of the page
-> Plan A in sub report for Plan1 which needsto report
--> Need to reduce the spacing of the details page of image section

1) No event numbers shows if we drill down to see the table

2)Color code information is not required to be in the table
3)Source of the event needs to add in the event summary report
4)we have some of the events on zone 0 which needs to validate and needs to
map to correct zone ID.

1)Detection time is in negative time

2)Event by hour table has option called "Exclude". When we click, we can not
3)select any other hour
Incident clearance time is not clear
Nov 2nd:-
There is a delay in log timing and actual system timing
when we click over on event it should be capture the same timing in DB and
event log
20210910/0019
20211027/0027
1) Source Drop down has duplicate/test data
2)Behavior of the selection of event on map is wrong
3)Legend of the event type is missing
4)Focus of the map is wrong when we select the events
5)Performance of the map is very slow

1.If the road code has no RVD ,It should not show in roadcode Selection
Dropdown.

PDF format is not aligned

1.Road name should be there in the report in pdf format.Blank page is showin
in PDF .Time line in PDF is not alined and it should show the proper timing i.e
every 5 min.Start time is missing.

DMS Action like Create/Edit/Review/Approve/Delete Message in Library

ANM Actions like True/False/ Unverified

Infra Down like VM/Server down should be captured( comment from Khalid)

if any Module is down then the log should be generated( comment from
Khalid)

abbreviation
In PDF the duration need
of the to chane
report shouldforbeF there,No
and A. of links should be there.

Nov 22nd
20th 2021:-
Nov 2021:-
Module
1. Event down
Creationlikefrom
DVMS or DMS
alarm or in
is not DMRPT
detail.should be show
It should shownthe
in alarm
the report
details
POL Requirement
also.
2. "Event updated" is showing in log when we close the event with out any
Infra
update down like server/node should be notified in the system log report
on event
3. For "Event over" also it is showing as event updated when there is no
TT log ison
update notevent
clear in the system log report
4. User name in the report is empty, Last Name +first name is incorrect
start
5. date reserved
Camera and end date validation
reason in system [Camera
to be mentioned log and other report
reserved by to
VA]be
rechecked
6. User group added is not shown in user activity report
7. Cosmetic Issues add Bracket + comma
message
8. in log should
which privilege berole
of the formal "because"
is updated should
to be shownbe added instead of "cos"
10.User Group Management not referring into user action
Event
11. whenQueue length change
a predefined doesn't
plan is updated,shown
the which eventbethe
log should change
clear done.
enough to
show the change [Eg., DMS added/Removed]
Response plan generated
12.Notification subscriptionfortorequest id should show event ID also.
be captured
13.Eqt details updated is not shown correctly
When
14.Systema user
logdoes PTZ should
for book be captured
mark export
15.Case based plan modification not captured
Event lane blockage updated is not there shown and also it should contain the
event23rd
Nov ID 2021:-
Oct 31st:-
User Management Tab, Mouse hover should be disabled instead of showing
1.Header of the report is not aligned properly
tooltip information
2.Road Code needs
Instead of saving thetodata
add in
into the page,
every reportthe user should save the data in any
3.Location duplicate has to be reviewed
tab or to have specific tab where all the data will be saved
4.Error popup
Notify the usershows
if any wrong
unsaved data in the tab
5. UI Issues
After [Columns
user chooses theare
newnotpassword,
aligned] go to login page should show
6. No Threshold value in alarm
7.Downloaded
Step 2 :- PDF is in landscape format
1.while creating new user, In user management tab, mouse hover should be
disabled instead of showing tooltip information.

Step 3 :-
1.Some rare cases, Same OTP is being generated for multiple times and for
different activities within 1-2 mins.

Step 5
1.Multiple OTP request may cause / add several user actions/stages.
2.One OTP for one page or when similar function is performance to be
implemented.

Step 11:-
1.Junk data in user management has been showing .
2.New users will not be able to login if they do not have access to their email
in the workstation(URL).
3.Option to provide temporary password/first time login OTP.

Step 15:-
1.Instead of saving the data in every page the user should save the data in any
tab, or to have a specific tab where all the data will saved.
2.Notify the user if any unsaved data in the tab.

Step 20:-
1.After user chooses the new password ,Go to login page should show.
1) After video export,message should be shown as "Video Exported
successfully"
2) BookMark export video quality to be adjusted currently 1 frame per second
3) Export option from joystick
 JIRA ID Remarks

DISAT-26 Step 1.
DISAT-7 -GIS is very slow in laoding & refreshing maps.
DISAT-85 Solve by Xiaobo
DISAT-87 -GIS preview of speed is not realtime.
Due to different loading time by GIS and Speed value, need to
quickly right click and click on Info.

Step 2. Fail
-No LOS show despite volume & LOS is calculated example link id:
DISAT-85 17840005983733
DISAT-87 -Volume data is available but not used (not consistent)
D63RVD05 with speed but no VOL, OCC and LOS
No raw between 10:49:30 and 10:52:00 for this link as below
-Add RVD Lane diagram in RVD details.D63 RVD02
Not implementing
DISAT-61-P5-Done
DISAT-62- P3-Done Step 3.
DISAT-63-P3-Done -Latency in video control & video quality is not right up to mark
Solved by Zhangwei, due to performance issue.

Step 4 & 5. Fail

-Camera video performance is poor in iTraffic mpv & GIS, latency
observed.
Solved by Zhangwei, due to performance issue.
-Jostick feature are not used/not working for keypad and other
buttons.
According to Dev team it will not be implemented at this phase.
-Joystick preset no programmed.
According to Dev team it will not be implemented at this phase.

Step 6. CPass
-CCTV E11CCTV48-C13 wrong location.
Sayed has informed Umair to inform to get the correct
coordinates.
-Sometimes CCTV fail to connect to server error.
Solved by Zhangwei, due to performance issue.
-Not all CCTV in global tour displaying.
DISAT-35-P2-Done Solved by Zhangwei, due to performance issue.
DISAT-44-P3-Done -CCTV appearing in GIS but not in MPV.
DISAT-65-P3-Reopen Solved by Zhangwei, due to performance issue.
DISAT-53-P3-Done
DISAT-30-P4-Done Step 7. CPass
DISAT -51 -P2 -Done -Switching the screen takes time to load cameras loading.
Solved by Zhangwei, due to performance issue.

Step 8.. Fail

-The Travel Time does not reflect the actual status. TT is Red
(congested) but in GIS showing Green. Example journey ID 21938
Solved by Xiaobo

Step 9. CPass
-Current Travel Time is not shown in the detailed page
Solve by Xiaobo

Step 10. CPass

-Freeflow on GIS does not match with detail shown in Travel Time
on all journey
Solved by Xiaobo

Step 12. CPass

-Report header is missing in the report
-Filter shall allow multiple selection of RVDs or by Road
 DISAT-64-P4 Alarm is reporting speed of 42kph, while RVD on same link is
94kph (E44RVD13)
D54S: Roadname is wrong (Correct D54)

DISAT-66-P4-Invalid DISAT-46 Retested in 29-Dec-2021, not fixed as POL expected.

DISAT-67 -P2 Issue re-opened with comments
DISAT-46-P3
DISAT-45-P4-Done Comment:-29th Dec 2021
DISAT- 109 (P4)-IP As per our call with POL on 29th Dec, this is what we discussed to
DISAT-110 (P4)-ToDo take it forward.

We have 6 intervals for PMM alarms for 5,10,15,30,45,60 mins.

whenever we receive PMM alarms for those intervals and if the

predicted time pass by for any alarm and interval, that alarm
should not be displayed on GIS

As time pass by, it is no more valid. so we need to have this check

for every interval to see if the generated PMM alarms are valid or
not.
DISAT-92-P4-Done
if it is not a valid alarm anymore, Perform system based house
Keeping to clear alarm from GIS view for easy operation.

T+5min alarm to be valid for 5 min only.. After the predicted

period (5 min) these alarm shall not be shown.

T+10min alarm to be valid for 10 min only.. After the predicted

period (10 min) these alarm shall not be shown.

T+60min alarm to be valid for 60 min only. After the predicted

period (60 min) these alarm shall not be shown.

1 hour for 1hour alarm....45 min for 45 min alarm

DISAT-26-P3 DISAT -7 tested
After House by azlan,
keeping, PMM Khalid to confirm
alarms will be visible in the GIS only
DISAT-7-P2 same comments as A1.1[Added]
for the predicted time valid period.
DISAT-104-Closed DISAT108-Cannot be tested until Snapshot issue is fixed.
DISAT-108 (P3)-Done the whole point of maintaining this approach is to keep only valid
PMM alarms for valid intervals on GIS for
 DISAT-65-P2 Need to take sign off from Rahim
DISAT-115-P3-Re-open Issue Re-tested on 29-Dec-2021 - Adding video clip to VA Alarm,
but POL says that image also been seen along with the video clip

Rahim says, The image snapshot of the VA alarm should be shown

along with the Video clip.

DISAT-86-P2 Verified by POL. Need to get signoff

DISAT-101-P2 Signed off on 21st Dec
DISAT-116-P3-VIP
DISAT-117-P3-VIP

DISAT-72-P4-Done

DISAT-31-P3
DISAT-32-P2
DISAT-33-P3
DISAT-34-P3
DISAT-57 (P5)
DISAT-106[P4]-VIP
DISAT-111 (P5)-RP

DISAT-73- P4-VIP
DISAT-74- P5-VIP
 DISAT-75-P5
DISAT-88-P3-Inprogress

In waiver list to exit SAT.

DISAT-75-P5-DONE
DISAT -122-Enhancement

DISAT-88-P3-Inprogress Subject to Successful completion of AID performance- Agreed by

POL

DISAT-88-P3-Inprogress Subject to Successful completion of AID performance- Agreed by

POL
 DISAT-89-P2 Obsolete based on new FSDD
DISAT-101-P2

DISAT-76-P4-Closed[Covered under Subject to Successful completion of AID performance- Agreed by

DISAT-88] POL
DISAT-113-Invalid-[ToDo]
DISAT-88-P3-Inprogress

DISAT-97 (P3) System is very slow, GIS is very slow in response-Still remains the
DISAT-98 (P4) same

DISAT-99-P2
 DISAT-71

DISAT-100-P2-FID Proposed for Waiver, In waiver list to exit SAT.

DISAT-90-P2-DONE
DISAT-107 (P2)-DONE

DISAT-91-P2 Can not be.

DISAT -112-P3-IP Weather parameters such as Rain be optimized to standard
DISAT-114-P5-Done recommendation

DISAT-96-P4-DONE
DISAT-9-P4-Re-Open
DISAT-10-P2
DISAT-11-P2
DISAT-12_p2
DISAT-14-P4-DONE
DISAT-15-P3-DONE
DISAT-8-P2
DISAT-17-P3-DONE
DISAT-118-P2-DONE
DISAT-123- P3-Done
DISAT-124 -P3-Invalid
 DISAT-18-P3-ToDo
DISAT-19-P3-Done
DISAT-20-P4-FID

DISAT-21-P4
DISAT-22-P4
DISAT-23-P3
DISAT-24-P5

DISAT-94-P4-Invalid Enhamcement C-Pass to Pass. Response Plan enhancement comment to be in

undertaking list to deploy after RT
DISAT-27-P2-VIP Proposed for Deferred
DISAT-28-P2-ToDo
DISAT-29-P3-Done

DISAT-16

DISAT-13
DISAT-43
 DISAT-68-P5

DISAT-70-P2-Invalid From POL Khalid 27/11/21

DISAT-102-P3-IP Dear JD,
DISAT-120-P3 We can proceed to test the SAT scenario. However, please note
DISAT-121-P3 that it will be marked as Conditoanlly passed due to the fact that
the scenario requires alarm to be sent to InforEAM. SCOOT assets
DISAT-3-P3 are yet to be configured in InforEAM.

DISAT-4-P3-DIP Can not be Comments moved to FAT

DISAT-80-P3

DISAT-5- P3
 DISAT-6-P4

DISAT -47-P3-DONE

DISAT-59-P2
DISAT-103-P2-Done
 DISAT-48-P2 Legend of the event type is missing -->Geetanjali will test with
khalid
18th Nov 2021:-
Include/Exclude options need to be reviewed again

DISAT-78-P3-DONE

DISAT-80-P3

DISAT-79-P3

DISAT-95-P2-Done
DISAT-127-P2-VIP

DISAT-81-P2-VIP
DISAT-83-P2-Done
DISAT-84-Task-VIP
DISAT-125 -P2
DISAT - 134 P2
DISAT - 135 P3
DISAT-139 P3
DISAT - 141 P2
 DISAT-60-P3 2 UI issues has been reported by rahim
Geetha updated them in same JIRA DISAT-60

Update - 6-Jan-2022
Severity reduced from P3 to P5 after discussing with Rahim
DISAT-36-P4-VIP DISAT-38 needs to be retested as we had an issue changing
DISAT-37-P3-DONE password from WS. We have a policy says user need to wait for 1
DISAT-38-P3-DONE day to change the password which can be initiated today. Will be
DISAT-39-P2 discussed with Rahim
DISAT-93-Task-Closed Tested latest on 15th Jan 2022:-
The user is not able to change the password from
workstation[Thru change password option] when logged in for the
1st time. Kannan is aware of this issue.

DISAT-52-P2
 Legends

Color Coding:-

Black: - In-testing, Reopen, Open

Red: - Invalid
Red & Strike Off:-Rejected is Accepted by POL
Green: - Internal Testing Done and ready to test with POL
Green & Strike Off:-Done with POL
Test Cases with P2 tickets are considered Failed

S/N  Test Case ID P2 P3 P4

DISAT-109 – AFTER
1 A.2.4 (P4) RT
DISAT-110

DISAT-66
2 A.3.2 (P3) DISAT-115 IN PROGRESS
3 B.5.1 (P3) DISAT-112 IN PROGRESS

4 B.1.1 (P5)

5 E.1.1 (P3) DISAT-124 DISAT- 9 (Reopened)

6 F.1.1 (P3) DISAT-18-FIX IN DEV (r1.1) DISAT-20-FIX IN DEV

7 G.1.7 (P3) DISAT-102-IN PROGRESS

DISAT-120-IN PROGRESS

8 H.4.1 (P2) DISAT-127-IN

PROGRESS

9 H.4.2 (P2) DISAT-141 DISAT-139 (Reopened)

(New)

10 H.5.1 (P3) DISAT-60 (Reopened & Upgraded)

Total Bugs (16) 2 8 5

S/N Scenario Type Test Case ID Test Cases Description Completion

TC-B.1.3-001 AUTOMATED CONGESTION
DETECTION ON D ARTERIAL
1
Incident ROAD AND IMPLEMENT After RT
Management RESPONSE PLAN

TC-B.2.1-001 INCIDENT ON MAIN

Incident CARRIAGEWAY CREATING
2 After RT
Management PARTIAL CLOSURE ON E ROAD
TC-B.2.2-001 AUTOMATED INCIDENT
DETECTION ON E ROAD
Incident CAUSING PARTIAL CLOSURE
3
Management After RT
AND JAM
 TC-B.2.6-001 AUTOMATED INCIDENT
Incident DETECTION ON E ROAD WITH
4 After RT
Management FULL ROAD CLOSURE
TC-B.3.3-001 MULTIPLE INCIDENTS ON E
Incident ROAD CAUSING PARTIAL
5
Management After RT
CLOSURE

Incident TC-F.1.5-001 Scheduled Roadwork for Bridge

6 with full closure. After RT
Management

Obsolete Test
Case
TC-B.2.4-001 AUTOMATED INCIDENT
Incident DETECTION ON E ROAD AT
1 Management -
ENTRANCE
P5

DISAT-111-IN
PROGRESS