1 Retention Alert Process This process has been written according to the specific objectives to be attained by The Connections Center during the Retention Alert Pilot Prepared by Laurimar Paniagua, Connections Center Developer/ Academic Success Coordinator, For the Title V HSI Grant, Dale Mabry Campus of Hillsborough Community College, Tampa, FL September 30, 2014
2 Retention Alert Process Overview of Retention Alert (RA) Overview of RA Components Interaction of Components Development Process Requirements Defined Software Subsystems Defined Testing Training Analyzing Functionality Results ***This process was created using guides and references from Institutionalization of Technology in Schools Checklist, Evaluation Checklists Project, as suggested within the Title V Grant, pg. e19/19
3 Overview of Retention Alert The Retention Alert case management system enables institutions to track specific information about students, open a case about a student, and automatically send alerts of any issues so that the student can be helped immediately. Based on the strategies agreed upon in the Retention Alert Decision document, scenarios are developed to track and monitor students. Once the case is opened, either automatically or manually, a notification is sent to the appropriate, institution-defined staff member or resource who can initiate communication with the student. The case information includes symptoms of the problem, the owner of the problem (advisor, professor, etc), and a history of the communication between the student and the owner. -ellucian 2013
4 Overview of Retention Alert Components Installation of software (access & permissions) Analyzing process (maintain and review records of success, issues and deficiencies) and readjusting process Calculate Results Development (of software usage & of process usage) Actualization of Process Report Results (findings and suggestions for institutionalization) Testing (of software usage & of the developed) Training (on software usage & Process usage)
5 Interaction of Components Technology Process Usage Process Staff/Faculty Participation and Administrative Support
6 Development This portion documents the two-part development that happens simultaneously: Software Development (Webadvisor/ellucian) Retention Process Development (working the case) Software & process developments affect each other s function: the software developments facilitate the capability to access, share & maintain information used in the Retention process. The Retention process is developed to facilitate the flow and timeliness of case creation, follow-up & measurement of results. Usage Process Technology Process Staff/Faculty Participation and Administrative Support
7 Development of Software set-up The person listed as having the role of Workflow Administrator will: Meet with each department head to: decide on the staff participation, roles and access levels decide on parameters for student identification Conduct training and testing on use of the software Technology Process Contact the Technical (IT) department to: provide the information (listed in the prior slide) of the participants needing access to Retention Alert in Colleague and WebAdvisor. specify the level of access each participant may have within Retention Alert & WebAdvisor activate the different accounts within Retention Alert The Technical (IT) department will respond with accessibility obtained for each staff member and inform of issues in obtaining permissions for any staff.
8 Development of Retention set-up The person listed as having the role of Workflow Administrator will meet with each department head to: Decide on the steps and responsibilities of each of the participant roles Decide on parameters for student identification (case types) Decide on best process to move students from identification, to working the case, and the case closure. Conduct testing on use of the software throughout the process identified above Contact the Technical (IT) department Usage Process Report initial accessibility issues to be resolved (later issues are reported by participating staff directly to the IT department) The Technical (IT) department will respond with accessibility obtained for each staff member and inform of issues in obtaining permissions for any staff.
9 Development of Process Specialization of roles- Identify who will be the Workflow Administrator, Reporting, Case Worker/Manager, and Contributors Development of routine & policy, practices and responsibilities Once each person has a decided role, each person knows who to go to for the different parts of the process, support, and preventative maintenance. Define each step of the process from creation of the case, to referrals, to closure. Standardized configurations and platforms- standardized infrastructure within WebAdvisor and Ellucian defines rules and case types to work together.
10 Retention Alert Process Roles Contributor Case Worker/Manager Reports Workflow Administrator Responsibilities include: Entering data for test students Accessing contribution information Document any errors Responsibilities include: Access My To Do List Add notes to cases Reassign cases Close cases Send from case Add Communication Code (if applicable) Document any errors Responsibilities include: Accessing open and close case reports Document any errors Responsibilities include: Accessing and manipulating RA parameters and/or setup Document any errors
11 Development of Staff/Faculty & Administrative Support The person listed as having the role of Department Administrator will meet with each department head to: decide on the staff participation, roles and access levels decide on parameters for student identification Determine how workload shifts/changes to accommodate & promote use of new software will take place Follow-up with department heads to provide support & accountability throughout the semester or time of initial development period. strong incentives in place to ensure that all staff/faculty receive appropriate training in the use of the software/ application & uses the technology Staff/Faculty Participation and Administrative Support
12 Sample Process Student case is contributed (a student is identified & Referred to Retention Alert by a professor or staff Notes of meeting, referrals & resources provided to the student are entered on Webadvisor. Reassign (add) case to include appropriate departments for follow-up advising. Student s Case is created & received at The Connections Center (DLRC 105) Student attends appointment and receives in-depth advising, resources, referrals and follow-up tasks (as needed). Each department adds notes to case as they interact with students Within 24 hours, the Student Case is assigned to Connections Center Staff Student is contacted and an appointment is made for an in-depth Advising session with Connections Center Staff. These steps are repeated as needed until Case meets closure criteria and is closed by Connections Center Staff
13 Process Requirements Defined Software - Staff have access to Colleague software and to WebAdvisor. Staff access - Both Colleague and Webadvisor software require that staff receive access to see and use the Retention Alert links. Access is provided by the person listed as having the role of Workflow Administrator. They will be contacted by the director of the department requesting staff access. The director will provide the Workflow Administrator with the staff s name, last name, employee number, department and employee address. The Workflow Administrator will add this information to the Case Worker/Manager list within the parameters of Retention Alert in Colleague. Staff permissions Staff is provided with permissions according to the different levels of access they will need to successfully complete their function within the Retention Alert process. Software rules and parameters- These are codes and specific guides that are outlined within Colleague to define the transaction functions that will be available for case creation, access of case, and reporting
14 Software Subsystems Defined The software is comprised of 4 different subsystems: Contribute Retention Info this subsystem allows the faculty or staff member(s) to enter institution-defined information about a student, thereby opening a case. Working the cases this subsystem allows the institution-defined faculty or staff member(s) to work on open cases through a to-do list Reporting this subsystems allows those institutiondefined faculty or staff member(s) to use the delivered reports to track the progress and count of open and closed cases Administration this subsystems allows the institution-defined administrator to manipulate the parameters for the Retention Alert software -ellucian, 2013
15 Testing of Software Usage Software testing will be divided into the following sections: Database/Server Parameters are defined & settings are finalized) Security and Access Control accessibility for participating staff to use software within their role s access Functionality system responds appropriately and accuracy to specific commands, requests, and reports WebAdvisor User Interface System is uploading from Colleague database to provide predefined access of student record
16 Testing of Retention Process Process testing will be divided into the following sections: Creation of cases manual & batch process is functional Accessibility Each person has access to perform tasks pertaining to their role Functionality Defined process is properly functioning to identify students, record information, and close cases as defined.
17 Software Training Software training to address: How to use of the software/application staff s fears and concerns, and emphasizes the application of technology to core tasks (as defined by each department s retention process) full range of technology experience, comfort, and development needs across the staff as assessed. follow-up training- provide opportunity to receive additional assistance, instruction, or clarification after the initial training, particularly in one-on-one settings. formal and/or informal application of the technology. plan for New staff/faculty to receive training and access throughout the year refresher and update trainings
18 Process Training staff development to address staff s fears and concerns, and emphasizes the application of process with use of the new technology to core Retention tasks. Flexibility and appropriateness process- training addresses the full range of the Retention Alert experience, discuss comfort, and any development of needs as assessed. Follow-up training- staff/faculty have the opportunity to receive additional assistance, instruction, or clarification after the initial training, particularly in one-on-one settings. Plan for dealing with personnel turnover Plan for refresher and update training
19 Analyzing Functionality of Retention Process How does attention to how technology changes the work dynamics Longer advising periods Staff to student ratio to provide adequate time for management of staff responsibility while engaging students Accessibility of technology software and connectivity are physically located where it is convenient for staff to integrate them into the flow of daily procedures. Staff comfort level with basic skills staff have sufficient skills to see opportunities to use the technology as a tool to reach institutional objectives and be willing to use the technology with Collaborative time staff have opportunities to collaborate with and learn from peers as they work with the technology. Administrative priorities administrators demonstrate commitment to technology integration through the allocations given to technology in schedules and budgets, leadership through modeling technology use, and the creation of incentive systems that reward use of technology.
20 Calculate Results Results achieved Totals for referred cases Totals for parties involved in the process of set-up, training, testing, and attaining results Totals of students retained Timeliness of result attainment Time for development Time for training Time for testing Time for actualization of process
Engineer Position Description February 9, 2015 Engineer Position Description February 9, 2015 Page i Table of Contents General Characteristics... 1 Career Path... 2 Explanation of Proficiency Level Definitions...
Configuration, Change, and Release Management Policies and Procedures Guide Table of Contents Section 1 Introducing Configuration, Change, and Release Management...5 1.1 Overview of Configuration, Change,
Prologue This amendment of The FAA and Industry Guide to Product Certification (CPI Guide) incorporates changes based on lessons learned and supports the broader use of this guide by providing additional
SUCCESSION PLANNING and LEADERSHIP DEVELOPMENT TOOLKIT April 2015 CONTENTS 1 Succession planning 3 What is succession planning? Succession planning process Leadership development 4 What is leadership development?
UT Market Project Charter Document Doc. Ref.: Charter UT Market Version: Draft 6 Status: REVISED on 4/27/2010 Initial Date: 2/4/2010 To be Approved by: FRMS Operational Sponsors and Executive Sponsor Document:
Navajo Nation Department of Information Technology (NNDIT) Helpdesk Policy P100 HelpDesk Problem & Request Management Process The following discussion of Problem Management procedures is intended to provide
Oak Park School District Counselor Evaluation Program Table of Contents Foreword... 1 Purpose of Evaluation... 3 Timelines for Implementation... 3 Overview of Counselor Evaluation... 4 Plan I Individual
TREASURY INSPECTOR GENERAL FOR TAX ADMINISTRATION Disaster Recovery Testing Is Being Adequately Performed, but Problem Reporting and Tracking Can Be Improved May 3, 2012 Reference Number: 2012-20-041 This
TREASURY INSPECTOR GENERAL FOR TAX ADMINISTRATION Corrective Actions to Address the Disaster Recovery Material Weakness Are Being Completed June 27, 2011 Report Number: 2011-20-060 This report has cleared
Vanderbilt University Medical Center Project Implementation Process (PIP).......... Project Implementation Process OVERVIEW...4 PROJECT PLANNING PHASE...5 PHASE PURPOSE... 5 TASK: TRANSITION FROM PEP TO
Ivy Tech Community College of Indiana POLICY TITLE Distance Education Course Design and Development POLICY NUMBER ASOM 6.0 (Formerly APPM 5. & 5.) PRIMARY RESPONSIBILITY Instructional Design CREATION /
Data Center Services Production Support Providing Call, Incident, and Change Management for customers throughout the Johns Hopkins Enterprise The Johns Hopkins Health Systems And The Johns Hopkins University
Mays Business School PhD Program Handbook NOTE: Mays Departments may have a Departmental PhD Handbook, set internal PhD Program procedures, requirements, and deadlines in additional to this Handbook. Contact
. VA Office of Inspector General OFFICE OF AUDITS & EVALUATIONS Department of Veterans Affairs Review of Alleged Improper Program Management within the FLITE Strategic Asset Management Pilot Project September
University of Northern Iowa School Psychology Program Internship Manual Revised August 2012 Table of Contents 1. Objectives & Purposes of Internship... 3 2. Registering for Internship... 3 3. The Internship
Southern Association of Colleges and Schools Commission on Colleges 1866 Southern Lane Decatur, Georgia 30033-4097 Guidelines for Addressing Distance and Correspondence Education A Guide for Evaluators
James Madison University Best Practices for Online Programs Updated December 2013 JMU Best Practices for Online Programs I. Introduction... 2 II. Institutional Context and Commitment... 2 III. Curriculum
Clinical Mental Health Counseling Practicum/Internship Manual Academic Policies Professional Standards Student Resources Program Curricula Spring 2014 1 CNDV 5393 Practicum/Internship TABLE OF CONTENTS
Master of Public Administration Program (MPA) Student Handbook This student handbook has been prepared as a guide for graduate students in the Clemson University Master of Public Administration program
August 2008 International Accreditation Guidelines for Accounting Degree Programs CPA Australia Mission statement and principles underlying accreditation CPA Australia is committed to ensuring excellence
Request for Proposals for Enterprise Information Archive System Gary R. Cavin, CIO Table of Contents 1 Introduction...1 2 SCOPE AND CLASSIFICATION...1 2.1 Scope...1 2.2 Classification...3 2.3 Budget...3
Executive Summary FLORIDA DEPARTMENT OF EDUCATION On September 23, 2013, following the Governor's Education Summit, Governor Rick Scott released an Executive Order announcing a plan for policy improvements
Audit of IT Asset Management Report Recommended by the Departmental Audit Committee for approval by the President on Approved by the President on September 4, 2012 e-doc : 3854899 1 Table of Contents EXECUTIVE
Commission on Colleges Southern Association of Colleges and Schools Best Practices For Overview to the Best Practices These Best Practices are divided into five separate components, each of which addresses
Overview Part A: Strategic assessment Part B1: Business case developing the business case Part B2: Business case procurement options Part B3: Business case funding and financing options Part C: Project