1. Nordic NE ROC Face 2 Face Meeting
ROD TRAINING
Nordic NE ROC Face 2 Face Meeting
15 June 2009
Vera Hansper
CSC/NDGF/NE ROC

2. Regional dashboard Accessed from the CIC portal
e=dashboard
Share the dashboard with SARA
You need to apply for the REGIONAL STAFF role in the GOCDB
Although a lot of progress has been made on the dashboard, refreshing the screen is still, unfortunately, slow
15-Jun-09, CSC

3. Regional Dashboard – HOME
Gives a summary of current alarms and tickets
No action can be performed on this page
Except opening a link to status of SAM tests
Except opening a link to a GGUS ticket
15-Jun-09, CSC

4. Regional Dashboard – PREFERENCES
Select the Regional Staff role from the list.
Clicking on Save preferences brings up another screen
Choose Regional Staff Role
You will be identified as ROC Staff for Northern Europe in the dashboard
You will also have site and 1st line support roles by default
1st line support information is now also accessible from the ROD role
15-Jun-09, CSC

5. Regional Dashboard – PREFERENCES
Choose the sites that are relevant to Nordic operations
You can optionally choose to also display only those sites which have problems
Your preferences are saved until you choose to change your role
15-Jun-09, CSC

6. Regional Dashboard – ALARMS
You can select the age of the alarm as a filter
This is useful for identifying 1st Line Support tasks
Site notes can be added here
An can be sent to the site with the entry by selecting the envelope buttonView of alarms per site
NOT per node
You can check alarm status in SAM pages from here
Selecting the ALARM ID gives a view of the alarm details (next slide)
15-Jun-09, CSC

7. Regional Dashboard – ALARMS
Clearing and masking alarms and adding notes is possible from this page
15-Jun-09, CSC

8. Regional Dashboard – TICKETS
This view provides current tickets for ROD.
You can also check the ROD ticket OR the GGUS ticket from here.
Note that these are two seperate entities, as in the old COD dashboard.
15-Jun-09, CSC

9. Handling Tickets
Tickets should be escalated in a similar manner to the old COD operations.
Track ticket for responses from sites
Escalate tickets after 1-2 days if no response
OLD tickets (> 30 days) will be automatically escalated to C-COD
Tickets have a colour assigned to assist with easy age identification
Try to assist site in solving ticket if appropriate
Solved tickets should, ideally, have a well written description of the solution to the problem.
Not applicable in all cases – use some discretion
15-Jun-09, CSC

10. Regional Dashboard – DASHBOARD
The main work page for ROD operations.
This is THE place where tickets can be created!
View is reflected by preferences chosen.
Roll over icons bring drop down menus for information about alarms and tickets
GOCDB page for the site is opened if the GOCDB icon is selected
The last icon will open a GSTAT status page
15-Jun-09, CSC

11. Regional Dashboard – DASHBOARD
ALARMS
A drop down page with current alarms for the SITE appears when the cursor rolls over the ALARM symbol
This page then disappears when the cursor is moved away
DOWNTIME
A spanner symbol indicates the site is currently in downtime.
The drop menu page gives details of the downtime
15-Jun-09, CSC

12. Regional Dashboard – DASHBOARD
TICKETS
The “T” symbol gives a list of current tickets for that site.
15-Jun-09, CSC

13. Regional Dashboard – DASHBOARD
CREATING TICKETS
The magnifying symbol on the left of the site name will present a summary drop down page when clicked on.
This page can be acted on for turning off alarms, generating tickets, and also accessing tickets.
15-Jun-09, CSC

14. Creating Tickets
A ticket should be created for an alarm as soon as possible after the age of alarm exceeds 24 hours.
Creating a ticket brings up a similar page as in the OLD COD dashboard.
Fill in the appropriate fields. The more information given to the site, the better they will be able to solve the problem.
You can choose to make a ticket for all or only some of the alarms for a given site.
There are other options for adding extra comments and solutions at the end of the page.
PLEASE try to keep the deadlines as short as reasonable.
PLEASE check all fields for accuracy before submitting.
15-Jun-09, CSC

15. Regional Dashboard – DASHBOARD
There is a notepad in this view where information can be stored. Useful for sharing information with other operators.
15-Jun-09, CSC

16. Regional Dashboard – DASHBOARD
It is also possible to create a ticket for a site without an alarm.
Use with caution!
15-Jun-09, CSC

17. Regional Dashboard – SAMAP
Same tool as in the old COD dashboard. Allows one to resubmit a SAM test
15-Jun-09, CSC

18. Regional Dashboard – DOWNTIME, VIEW
Downtime TAB gives a quick overview of current downtimes in your region/scope.
The View TAB allows you to view information about sites in another ROC.
15-Jun-09, CSC

19. Regional Dashboard – HANDOVER
A handover log is available. (This might also be used by the WLCG meetings.)
You can use this to pass on messages to C-COD or other RODS.
PLEASE also add the information here to the OoD handover , or separately to
15-Jun-09, CSC

20. Regional Dashboard – METRICS
Weekly
and monthly
ROD metrics for all regions can be accessed here
15-Jun-09, CSC