1. User Office Status CANARIE Site Visit July, 2009

2. User Office within the SS ‘big picture’

3. 3 Status Overview User OfficeDraft ReqsSolid ReqsDesignCodeTestProduction User Training   User Survey and Feedback   Scheduling   Proposal, Task and Sample management Workflow   Reporting  Search  Security   User management  

4. User Office High Level Architecture (block diagram)  User Office follows the classic 3-Tier layered web app approach and uses Ajax Technologies

5. User Training Module  Goal: To automate the user training process at CLS which is prerequisite to gaining unescorted access, and performing different roles at the facility  Side effects: improved quality of training immediate feedback on exams reduced manual grading and entry of training records one database with improved reporting capabilities. increased overall efficiency and reduction in duplication and data entry error.

6. User Training Module Features User Management Registration User and Admin Views User Management Registration User and Admin Views Intuitive Materials Categorization Modules Exams Sections Questions Presentation Intuitive Materials Categorization Modules Exams Sections Questions Presentation Reports Search results Validate training Export to Excel Trace generated tests Statistics and charts Reports Search results Validate training Export to Excel Trace generated tests Statistics and charts Test Taking Timed Examination Support for disconnections Time stamps Multiple attempts e.g. successful, firstUnsuccessful, lastUnsuccessful, alternative Test Taking Timed Examination Support for disconnections Time stamps Multiple attempts e.g. successful, firstUnsuccessful, lastUnsuccessful, alternative Test Creation Flexible question format Randomized questions Test Expiry Automatic Validation e.g. empty choice selected as correct Test Creation Flexible question format Randomized questions Test Expiry Automatic Validation e.g. empty choice selected as correct

7. User Survey and Feedback Module  Goal: To automate the user feedback and survey process at CLS to facilitate scientists  Enables User Office experiment monitoring service and accurate metrics on whether: Check in procedures are efficient and user-friendly End station equipment is ready & in good working order Shifts are being utilized Beam is being delivered without interruption Identify unforseen problems

8. Scheduling Module  Goal: To automate the review process and the method by which beam time is allocated and scheduled to users depending on the access mechanism chosen by the user and the stage of operation (construction, commissioning or operation) of the beamline.  Side effects: Facilitate the management of cycles, runs and modes of operation Use automatic scheduling to handle more scheduling conditions and constraints than human beings are able to handle manually and identify optimal solutions.

9. Scheduling Module Features Users Submit proposals Integer Programming and Heuristic Algorithm Schedule INPUT: SEARCH AND CONSTRAINT SATISFIABILITY: OUTPUT: Beamlines2 Experiments3 Release Times[1,1,2] Deadlines[8,15,5] Weights[4,5,1] Processing Times[10,4,3] Eligibility[[0,1,0],[1,0,1]] CONSTRAINTS 1. One beamline per experiment 2. Start time after release time 3. Only eligible beamlines can be selected. 7. No overlap of experiment per beamline

10. Heuristic algorithm:  Sort the experiments.  Arrange the first experiment to the first possible beamline.  Arrange the next experiment to the next possible beamline.  Repeat step 2 and step 3 until all the experiments are arranged.

11. Evaluation: 2 beamlines, 3 experiments Input data: ParameterValueComment M22 beamlines N33 experiments R[1,1,2]earliest possible start time for each experiment D[8,15,5]latest finish time for each experiment W[4,5,1]priority given to the experiment P[10,4,3]processing time for each experiment E[[0,1,0],[1,0,1]] beamline 1 is eligible for experiment 2 only. Beamline 2 is eligible for experiment 1 and 3. St1when the scheduling cycle starts Te100when the scheduling cycle ends

12. Evaluation:

13. Evaluation: 3 beamlines, 7 experiments Input data: ParameterValue M3 N7 R[23,66,27,51,86,46,39] D[67,101,57,70,111,67,74] W[2,2,2,1,4,2,2] P[37,17,21,14,5,15,18] E[[1,0,1,0,0,1,0],[1,1,0,1,1,0,0],[0,1,1,1,0,0,1]] St5 Te591

14. Evaluation:

15. Development Plan  Scheduling modes manual approach  use GUI (JQuery) to collect information from the user  calendar view can be used similar as the spreadsheet automatic approach  use GUI input for the heuristic algorithm

16. Calendar view in JQuery

17. User Office Workflow Goal: Many tasks in proposal & sample management at CLS To develop a workflow management system that manages ordering of tasks e.g. (training  before  shipping) Tracks manual as well as SS task progression JanMarJun 6-month cycle CLS calls for proposals Proposal submission To CLS CLS gathers proposals CLS reviews proposals CLS grants scientist Beamline time Scientist packs sample I wonder if CLS received my sample yet? Scientist must complete Online SS training CLS health & safety inspection Many other tasks Perform Experiment Return Sample Take Survey …

18. User office Workflow Status Workflow Management Engine Beamline User User Office Task :Training Completed Notify Approved Notify Record Progress Features Open source Petri-nets based Direct support for workflow control flow patterns Ability to interact with web services declared in WSDL Relies on XML standards e.g. XPath and XQuery for data & doesn’t use proprietary languages Architecture System Core: YAWL engine. Engine instantiates specifications designed using YAWL designer. managed by the YAWL repository Environment composed of YAWL services inspired by “web services” paradigm, end-users, applications, and organizations are all services in YAWL.

19. User Office Workflow Example Prototype Implementation 1. CLS issues a call for proposals and gives deadline 2. Beamline users submit proposals 3. User Office administrator ends registration or extends deadline 4. User Office administrator assigns proposals to user office reviewers 5. Reviewers look at proposals and rank them 6. User Office looks at ranking and chooses the proposals to accept 7. Accepted proposals contact persons are notified 8. Beamline User completes training (web service) 9. After training is completed (simulated by a delay) the CLS is notified

20. Screenshot: User Training Statistics

21. Screenshot: User Training Test Creation

22. Screenshot: User Survey Taking Page

23. Screenshot: User Survey Edit Page

24. Screenshot: Workflow Sample Management

25. Screenshot: Workflow Call for Proposals