Improved SelfService Solution FAMIS Team Current SelfService Screenshots

Improved Self-Service Solution FAMIS Team

Current Self-Service � Screenshots 1 of current process 2 3 4 5

Current Self-Service � Screenshots 6 of current process 7

Current Self-Service � Screenshots 8 of current process 9 10

Current Self-Service � Screenshots of current process 11 12

Current Self-Service � Screenshots 13 of current process 14 14 steps to complete a single work order request!!

Current Self-Service � What if using the customized request form Problems - More screens to select COA, and account segments=>bothering - Missing UC issues Solutions - Default values - List of values for account segments - Suggested values - Validation

How does the SS System work? � 7 URLs, each may be used for more than once loc. create. Loc_2 loc. process_info Every step in site, building, floor, room selection wq. goto_create_sr rfs. Put_Req rfs. select_service_c Every step in requestor information, service selection rfs. select_service_s rfs_process_select_service All 14 staging steps submit information to the URLs above

How does the current SS System work? � Workflow loc. create. Loc_ 2 View loc. process_info wq. goto_create_sr rfs. Put_Req rfs. select_service_c rfs. select_service_ s rfs_process_select_servic e 0 1 -5 6 7 -14

How does the current SS System work? � Workflow loc. create. Loc_ 2 View loc. process_info wq. goto_create_sr rfs. Put_Req rfs. select_service_c rfs. select_service_ s rfs_process_select_serv ice Can be improved by making short-cuts, auto-submit, etc. 0 1 -5 6 7 -14

Main Challenge: “Cookie” mechanism � FAMIS_LOC_COOKIES � FAMIS_WQ_STORE � FAMIS_COOKIES Final cookie It takes 3 steps to get a final cookie

Cookie mechanism � How to get a cookie? � Can not read from the HTML due to the cross-domain issue � Able to query FAMIS_LOC_COOKIES for the most recent location cookie corresponding to the logged-in user � Then query FAMIS_WQ_STORE for the corresponding wq-store cookie � Then query FAMIS_COOKIES for the corresponding final cookie given the location cookie and the wq-store cookie

Is it even possible to implement? � Invented mechanism � Pushes transition between steps on FAMIS side instead of having users do it � Feeds required data fields by FAMIS to FAMIS in an automatic and time cost effective manner UCONN fac_self_service_step_0. p hp Auto submit FAMIS Auto submit info to FAMIS fac_ss_loc_create. Loc_2. p hp fac_self_service_step_1. p hp loc. create. Loc_ 2

UCONN fac_self_service_step_1. p hp Auto submit FAMIS Auto submit info to FAMIS fac_ss_loc_process_info. p hp loc. process_inf o fac_self_service_step_2. p hp Auto submit info to FAMIS Auto submit fac_ss_wq_goto_create_sr. p hp wq. goto_create_s r fac_self_service_step_3. p hp Auto submit info to FAMIS Auto submit fac_ss_rfs_Put_Req. php fac_self_service_step_4. p hp rfs_Put_Req

UCONN FAMIS fac_self_service_step_4. p hp Select Submit book/chapter/section fac_self_service_step_5. p hp Auto submit info to FAMIS Auto rfs. select_service_c submit rfs_select_service_c. php fac_self_service_step_6. p hp Auto submit rfs_select_service_s. php fac_self_service_step_7. p hp Auto submit info to FAMIS rfs_process_select_service. p hp Submit info to FAMIS fac_self_service_step_last. p hp Select site/building/floor/room rfs_process_select_serv ice rfs_Put_Req

Example closer look Call an other UCONN side page to submit required information to FAMIS Auto submit to the next step on UCONN side

Block View UCONN Side Accruent Side Current Self Service module loc. create. Loc_2 loc. process_info wq. goto_create_sr Current users rfs. Put_Req rfs. select_service_c rfs. select_service_s rfs_process_select_service Added Functionalities (newly written code) support FAMIS users to automate processes using support information by querying/reading FAMIS database

Block View Accruent Side Current Self Service module UCONN Side loc. create. Loc_2 loc. process_info Current users wq. goto_create_sr Added Functionalitie s rfs. Put_Req rfs. select_service_c rfs. select_service_s to automate procesess rfs_process_select_service Improved Self Service module Note: We have no write access to FAMIS database. Processes are automated by using supporting information read from the database and simulating user submit actions with all FAMIS-required information

New GUI � Select all books, chapters, and sections in 1 page � Auto Submit after selecting all the options � Tested on IE 10 The customized WO request format is not included yet

New GUI � Select site, building, floor and room � Fill in the details Selection of sites, buildings, floors and room can be faster using JQuery Design can be better using CSS Can even combine the previous step to 1 page

New GUI � After clicking Finish, the details are submitted to FAMIS and a confirmation is returned from the system Can replace this by a customized page Can even by pass this step

Test SS Users � 3 users added for testing

Mobile solution � Simple demo available at � http: //famis. test. uconn. edu/direct/ios_wrap. php � Playable � Using Sencha Touch framework � Tested on Chrome � Not a working solution yet � Can make it work on i. Phones/i. Pads

What to do next? � Tests � Some tests will need to be done in Test � Creation of Test Service Requests � Creation of Test Work Order Requests � Work Order Assignments, and Printing � Billing � Browser tests for different browsers, fixes provided if necessary

Risk analysis � Legal � If risk questioned by the vendor: � The newly added module does not write but submit to FAMIS database system � It reads necessary information from FAMIS database system to feed FAMIS Self-Service in each step � It supports the transition between steps instead of having users do it Can combine, customize steps Make it faster to complete a SS request � Operational risk � Span on 2 locations: added risk from outage events in Storrs web servers, networks, etc. � More opinion?

Estimate of time for completion � An improved version of Self Service in Test environment, including the customized “Create your own requests” � 70 -105 hours (a lot of testing) �A mobile version in Test environment (using Sencha Touch) � 70 -105 � Design hours work � 16 hours (approved, professional design support from another team) � Total � 156 -226 hours for completion in Test