24
Updated 12/19/08 AGENDA SLU Business Manager Meeting April 10, 2008 Sanctuary Room, Il Monastero (Berea Hall) 9:00a.m.-10:30a.m. 1) Meeting Overview/Announcements Sign in Sheet Review of March and April ‘What’s New?’ 2) Arena details and Opening Day information – Janice Crawford (10 minutes) 3) Pre-Commencement exercises and locations - Erin Kruse (10 minutes) 4) Logical Access and Change Management – Ken Gebken (30 minutes) 5) Q & A

AGENDA SLU Business Manager Meeting April 10, … · Meeting minutes of the Saint Louis University Business Managers held at 9:00 a.m. on Thursday, April 10, 2008 at Il Monastero

  • Upload
    lenhi

  • View
    212

  • Download
    0

Embed Size (px)

Citation preview

Updated 12/19/08

AGENDA

SLU Business Manager Meeting

April 10, 2008 Sanctuary Room, Il Monastero (Berea Hall)

9:00a.m.-10:30a.m.

1) Meeting Overview/Announcements

• Sign in Sheet • Review of March and April ‘What’s New?’

2) Arena details and Opening Day information – Janice Crawford (10 minutes) 3) Pre-Commencement exercises and locations - Erin Kruse (10 minutes)

4) Logical Access and Change Management – Ken Gebken (30 minutes)

5) Q & A

Updated 12/19/08

Business Manager Meeting

Minutes of the Meeting of April 10, 2008

Meeting minutes of the Saint Louis University Business Managers held at 9:00 a.m. on Thursday, April 10, 2008 at Il Monastero (Berea Hall). Business & Finance Staff Present:

Bruce Andres Tim Brooks Vicki Cassady Janice Crawford Mary Drexl Keith Emge Melissa Ezell Sharon Gajewski Tonya Gallina Jeff Hovey Lee Kneibert Eric Lewis Michael Lucido Marsha McBride Lori Myers Annaliese Neff Linda Pizzo Gary Whitworth Lisa Zoia Number of Business Managers Present:79 Michael Lucido welcomed everyone to the meeting. There will not be a Business Manager’s meeting in May, however the “What’s New” newsletter will be emailed to the Business Managers with any updates or new information. The next meeting is scheduled for June 12, 2008, in the Medical School, Lecture Hall A . Please check the meeting schedule for the location of all future meetings. Going forward, the Business Manager’s meetings will be held every other month at various locations throughout campus. The “What’s New” newsletter will continue to be sent out monthly with updates. Any important changes/updates will be sent out immediately by email. What’s New Review - Keith Emge reviewed the current issue of “What’s New”. Salary Planner Updates – The April “What’s New” issue includes information on a new report available, PWB0005 which is located under the “Salary Planner Reports” heading in the Salary Planner domain. Check the April issue for more information. eSeePay – Online DPV System – Steps are being taken to improve the system response time for the new eSeeIDO process. The new online DPV – eSeePay manual, tutorial and workflow process are posted on the web. These materials should be reviewed prior to taking the quiz that will give you access to the new on line system. Travel Updates – Keith reminded Business Managers to run their department trip reports in Web Focus and to work with their employees to submit all expense reports on any active or past due travels. Invoice Reminders - Jeff Hovey (Procurement) and Sharon Gajewski (Accounts Payable) are notifying vendors that a valid SLU PO number must be on all invoices and the invoices should be mailed directly to Accounts Payable. Vendors are also being asked if they would like to receive payment by direct deposit. If the prefer payment by direct deposit, they will need to provide AP with their banking information. Leave Reporting – Effective in April, Leave Reporting should now be completed in Self Service Banner. This new reporting will eliminate the need to estimate exception time (absences) in advance. This should eliminate the processing of Time Reporting Change Forms. Pay Date Reminder – Beginning with the April paychecks, the monthly pay date will move to the last working day of each month (rather than the second to last working day). Monthly Pay dates for the remainder of 2008 are:

Updated 12/19/08

April 30 May 30 June 30 August 29 September 30 October 31 November 26 December 30 Arena Opening – Janice Crawford reported on the Arena Open House scheduled for later in the day. The event is free and open to the public and Janice encouraged everyone to attend and check out the new facility. The first event is scheduled for Friday, April 11 when the Harlem Globetrotters will perform. Other events include the Missouri/Illinois High School All Star game, Barry Manilow, Raven Symone and Stevie Nicks. Janice thanked everyone in attendance that assisted with the project in any capacity. The Arena will generate revenue for the University and hold future commencements as well as many other events. Pre-Commencement/Commencement activities – Erin Kruse, of event services, reported that 8 of the 11 pre-commencement services will be held at the new Arena. For more information on commencement activities you can call 977-6338 or visit The Commencement website Logical Access and Change Management – Tim Brooks gave an update on the Logical Access process and reported that the Password Change Rollout Schedule was on track and going well throughout campus. Tim Brooks gave a power point presentation on the Logical Access and Change Management process. Tim discussed the procedures for requesting, changing, and terminating access to our critical business and administrative applications. Tim then discussed the new 6 step process for requesting, managing, and approving changes to the University computing environment. Before installing any software on University computers, users need to contact IT so they can determine what other areas, if any, may be affected by this change. To initiate a change, either contact the IT person assigned to your area, or the Help Desk at 977-4000. The meeting was adjourned at 10:10 a.m. Minutes respectfully submitted by Mary Drexl.

Updated 12/19/08

Password Rollout Schedule

Organization Unit Tues. TUES.

CSC Sends email notification to O/U about scheduled password change

Date of Roll Out: Server team applies password policy to theO/U

ITS 1/29/2008 2/5/2008 Graduate School 1/29/2008 2/12/2008 HSC Administration 1/29/2008 2/12/2008 HSC Finance (in HSC Administration?) 1/29/2008 2/12/2008 Human Resources 1/29/2008 2/12/2008 Mission and Ministry 1/29/2008 2/12/2008 Research Administration 2/5/2008 2/12/2008 Business and Finance 2/5/2008 2/19/2008 Community Relations 2/5/2008 2/19/2008 Counsel Division 2/5/2008 2/19/2008 VP-University Advancement/ Development and University Relations 2/5/2008 2/19/2008 Enrollment and Academic Services 2/5/2008 2/19/2008 School of Law 2/12/2008 2/19/2008 Arts and Sciences 2/26/2008 2/26/2008 Business and Administration - CSB 3/5/2008 3/4/2008 Affirmative Action 3/5/2008 3/11/2008 Allied Health 3/5/2008 3/11/2008 Athletics 3/5/2008 3/11/2008 Auditing (University Audit Services) 3/5/2008 3/11/2008 School of Nursing 3/12/2008 3/11/2008 Parks 3/12/2008 3/18/2008 Presidents Office 3/12/2008 3/14/2008 Public Services 3/12/2008 3/18/2008 Research 3/12/2008 3/18/2008 Risk Management 3/12/2008 3/18/2008 Social Services 3/12/2008 3/18/2008 SOM - Anesthesiology (some TENET) 3/12/2008 3/18/2008 SOM - Community and Family Medicine 3/12/2008 3/18/2008 SOM - Admissions 3/12/2008 3/25/2008 SOM - Anatomy/Ctr for Anatomical Science & Ed 3/18/2008 3/25/2008 SOM - Biochemistry & Molecular Biology 3/18/2008 3/25/2008 SOM - Cancer Center 3/18/2008 3/25/2008 SOM - Comparative Medicine 3/18/2008 3/25/2008 SOM - Core Grad Student Training 3/18/2008 3/25/2008 SOM - Curricular Affairs 3/18/2008 3/25/2008 Provost 3/18/2008 3/31/2008 SOM - Dermatology (some Tenet EMAIL) 3/18/2008 4/1/2008 SOM - Emergency Room 3/25/2008 4/1/2008 SOM - Employee Assistance Program 3/25/2008 4/1/2008 SOM - Employee Health 3/25/2008 4/1/2008 SOM - Family Health Services 3/25/2008 4/1/2008 SOM - Graduate Medical Education 3/25/2008 4/1/2008

Updated 12/19/08

SOM - Internal Medicine 3/25/2008 4/8/2008 SOM - Machine Shop (in HSC Administration?) 4/1/2008 4/15/2008 SOM - Marketing and Provider Services 4/8/2008 4/15/2008 SOM - MD-PhD Program 4/8/2008 4/15/2008 SOM - Molecular Microbiology 4/8/2008 4/15/2008 SOM - Molecular Virology 4/8/2008 4/15/2008 SOM - Multi Cultural Affairs 4/8/2008 4/15/2008 SOM - Neurology (some TENET) 4/8/2008 4/22/2008 SOM - Obgyn (TENET EMAIL) 4/15/2008 4/22/2008 SOM - Ophthalmology 4/15/2008 4/22/2008 SOM - Orthopedic Surgery 4/15/2008 4/22/2008 SOM - Otolaryngology 4/15/2008 4/22/2008 SOM - Psychiatry 4/15/2008 4/22/2008 SOM - Call Center (SLU CARE) 4/15/2008 4/29/2008 SOM - Pathology 4/22/2008 4/29/2008 SOM - Pediatrics 4/22/2008 4/29/2008 SOM - Pharm Phys 4/22/2008 4/29/2008 SOM - PMO (TENET EMAIL) 4/22/2008 4/29/2008 Students – Undergraduate Begin4/4/2008 4/29/2008 School of Professional Studies 4/22/2008 5/6/2008 SOM - Radiation Oncology 4/29/2008 5/6/2008 SOM - Radiology 4/29/2008 5/6/2008 SOM - Records (University?) 4/29/2008 5/6/2008 SOM - SOM Continuing Education 4/29/2008 5/6/2008 SOM - Student Affairs 4/29/2008 5/6/2008 SOM - Student Financial Services-Med Sch 4/29/2008 5/6/2008 SOM - Surgery 5/6/2008 5/13/2008 SOM - UMG Administration 5/6/2008 5/13/2008 SOM - UMG Ambulatory Care/Medical Records 5/6/2008 5/13/2008 SOM - UMG Finance 5/6/2008 5/13/2008 SOM - UMG Support Services 5/6/2008 5/13/2008 SOM - University Health Plan 5/6/2008 5/13/2008 School of Public Health 5/13/2008 5/20/2008 SLU-Spain 5/13/2008 5/20/2008 Student Development 5/13/2008 5/20/2008 Student Facilities 5/13/2008 5/20/2008 Alumni Relations 5/13/2008 5/20/2008 University Development 5/13/2008 5/20/2008 University Galleries 5/13/2008 5/20/2008 University Marketing and Communications 5/13/2008 5/20/2008 Facilities 5/20/2008 6/3/2008 Facilities Planning-Civic Affairs 5/20/2008 6/3/2008 University Event Services 5/20/2008 6/3/2008 Guests 5/20/2008 6/3/2008 Academic Affairs 6/3/2008 6/10/2008 Center for Advanced Dental Education 6/3/2008 6/10/2008 Students – Graduate 6/3/2008 6/10/2008 Oracle 10G Data Base - (proposed) 6/16/2008

Updated 12/19/08

Logical Access Change Management Implementation – Phase 1 Business Managers Meeting Presentation

April 10, 2008 Summary

LOGICAL ACCESS

Process by which user access accounts are created, changed, terminated, and monitored within the Saint Louis University primary application architecture.

The Scope of Phase 1 included:

• Banner • WebFOCUS • Xtender • Workflow • Axiom • Related databases

UNIVERSITY ACCESS SECURITY REQUEST FORM

Formal documentation of request and approval.

1. Form must be submitted for all requests. 2. Used for the following requests:

• New, change, and delete user access • Faculty/staff, student workers, contractors, guest accounts

3 Location of forms, desk procedures and key document: http://www.slu.edu/services/HR/university_security_forms.html

MONITORING and REVIEW Ensure user access rights are appropriate and authorized.

1. Service Access Report – Biannual Review (April and October) – A comprehensive listing of

user access rights. Key management, as notified, will be involved in the review of the reports.

2. Position Change Report – Weekly Review - Lists users who have changed positions, which

may require updates to access rights. Management involvement may vary depending on department activity. Will be notified by Security Officers, as necessary.

3. Termination Reports – Weekly Review - Lists users who have separated from the university,

but who still have access rights. Security Officers will request that Business Managers confirm terminations as needed; depends on termination activity for the week, if any.

4. Account Inactivity Report – Biannual Review (April and October) - Lists users whose accounts

have shown no activity over a specified period of time. Management involvement may vary depending on number of inactive accounts in department.

PASSWORD POLICY You will receive an email message on or about the date as noted in the roll-out schedule that includes specific directions to change your password.

Updated 12/19/08

E. CHANGE MANAGEMENT

The goal of the change management process is to ensure standardization across all sites and all departments, as well as to ensure that all necessary parties are contacted, informed and approve each change request. While some changes may have no budgetary impact, each requested change must be recorded and properly tracked to completion.

The Scope of Phase 1 included:

• Banner • WebFOCUS • Xtender • Workflow • Axiom • Related databases

F. SLU’S CHANGE MANAGEMENT PROCESS

The Change Management process is a six step process has been designed to track all changes using the existing ITS Management Tracking System (REMEDY); the existing responsible areas have also been incorporated into the design.

1. Initiate Request - Submit request to appropriate ITS Functional Group

2. Change Review – ITS determines the risk level and completes a Business Case

3. Change Assessment – ITS gathers requirements, performs risk, Impact assessment and creates a Back-Out Plan.

4. Testing – Create a test plan: specifying all criteria. Test results and approval are

documented in Remedy.

5. Approve and Implement – Stakeholder and, if necessary, the CCB and the QA office, and reviews/approves all phases of the change. The change is communicated and implemented.

6. Change Closure – Stakeholders and ITS verify the change operates properly and

completes the Closure Form. ITS closes file in Remedy. G. CHANGE MANAGEMENT DOCUMENTS AND FORMS

Nine forms have been developed for use by the ITS team and Stakeholders. All forms require approval by the primary Stakeholder (requestor). Forms, tools and templates can be found in Remedy.

1. Business Case 2. Impact and Risk Analysis 3. Change Build Form 4. Back Out Plan 5. Test Plan 6. Implementation Plan 7. Communication Plan 8. Acceptance Form 9. Closure Form

1

LOGICAL ACCESSLOGICAL ACCESS&&

CHANGE MANAGEMENTCHANGE MANAGEMENT

Business Managers PresentationBusiness Managers Presentationforfor

Saint Louis UniversitySaint Louis University

2

Why Are We Here?Why Are We Here?

• Expanding University Technology Services– Banner Project– Research/Grant Projects– Electronic Data Warehouse Project

• Desire to Implement Best Practices Organization Wide– Ensure controls impacting financial statements are

effective– Controls minimize problems, enhances bottom line – Right thing to do

• Statement on Auditing Standard 112 (SAS 112)

3

•• Part One: Part One: IntroductionIntroduction•• Purpose of LACMIPurpose of LACMI

•• Part Two: Part Two: Logical AccessLogical Access•• Purpose of Access Security Request FormPurpose of Access Security Request Form•• Completion & Submission of FormCompletion & Submission of Form•• Tips to Make the Process WorkTips to Make the Process Work•• Monitoring Access RightsMonitoring Access Rights

•• Part Three: Part Three: Change ManagementChange Management•• Purpose and BackgroundPurpose and Background•• Process flow chartProcess flow chart•• Six key steps: roles and responsibilities Six key steps: roles and responsibilities •• Tips to Make the Process WorkTips to Make the Process Work

AgendaAgenda

Presenter
Presentation Notes
On your desk make sure each student has 4 documents. They are: copy of the quick reference guide, a copy of the 12 LA controls, a copy of a Access Control Form and a copy of the presentation. HOLD UP EACH ONE! KEY Points: -This LA process is a working document: there are a couple of updates to the slides I will mention as we go along. -Ask how many people already use remedy and webFOCUS -Emphasis that the presentation is designed for new users of Remedy -Emphasis this document will give an overview of the entire process that many of you have been a part of. -Emphasis changes that everyone, regardless of their participation in the project, will see in Remedy -Educate the audience on new procedures and password changes to SLUnet ID passwords

4

•• Formal documentation of request and Formal documentation of request and approvalapproval–– Replaces email, phone, and verbal requestsReplaces email, phone, and verbal requests–– Increases consistency in requestsIncreases consistency in requests

•• Used for the following requests: Used for the following requests: –– Banner, Banner, WebFOCUSWebFOCUS, , XtenderXtender, Workflow, Axiom, and related , Workflow, Axiom, and related

databasesdatabases–– New, change, and delete user accessNew, change, and delete user access–– Faculty/staff, student workers, contractors, guest accountsFaculty/staff, student workers, contractors, guest accounts

•• Location of the form and instructionsLocation of the form and instructions–– http://www.slu.edu/services/HR/university_security_forms.htmlhttp://www.slu.edu/services/HR/university_security_forms.html–– Titled Titled ““University Access Security Request FormUniversity Access Security Request Form””–– ““Security Request Form HowSecurity Request Form How--To InstructionsTo Instructions””

Logical Access Form: Logical Access Form: PurposePurpose

Presenter
Presentation Notes
Segregation of duties: For example, a user who accesses data to read and write reports, should not have, in most cases, the ability to change or manipulate that data for his or her results. (See student grades)

5

–– Access Type & Level: Service Level Review GuideAccess Type & Level: Service Level Review Guide•• Descriptions of classes, forms, etc. Use to determine and evaluaDescriptions of classes, forms, etc. Use to determine and evaluate te

appropriateness of access rights (Segregation of Duties)appropriateness of access rights (Segregation of Duties)http://http://www.slu.edu/services/HR/university_security_forms.htmlwww.slu.edu/services/HR/university_security_forms.html

–– Authorized ApproversAuthorized Approvers•• Business Manager or above (some exceptions):Business Manager or above (some exceptions):

–– Directors, Associate Directors, etcDirectors, Associate Directors, etc

–– Segregation of Duties Segregation of Duties -- Prevents a single person from Prevents a single person from performing two or more incompatible functions. Failure to adequaperforming two or more incompatible functions. Failure to adequately tely segregate, or implement compensating controls, increases the rissegregate, or implement compensating controls, increases the risk that k that errors or unauthorized actions may occur and not be detected in errors or unauthorized actions may occur and not be detected in a timely a timely manner.manner.

–– Submit to Appropriate Security Officer as noted on Submit to Appropriate Security Officer as noted on the Access Formthe Access Form

Logical Access Form: Logical Access Form: Completion & SubmissionCompletion & Submission

Presenter
Presentation Notes
Segregation of duties: For example, a user who accesses data to read and write reports, should not have, in most cases, the ability to change or manipulate that data for his or her results. (See student grades)

6

All users, including contractors and guests, are required to havAll users, including contractors and guests, are required to have e SLUnetSLUnet (Banner) ID prior to new user access request(Banner) ID prior to new user access requestEnsure completion and accuracy of form dataEnsure completion and accuracy of form dataSubmit access requests for new users (or transfers) in advance Submit access requests for new users (or transfers) in advance of userof user’’s first day of works first day of workReply to Security Officers request for user access confirmationReply to Security Officers request for user access confirmationSubmit access form to remove or change user access, at least 2 Submit access form to remove or change user access, at least 2 days prior to last day of work or transfer/changedays prior to last day of work or transfer/changeMonitor and communicate last days for contractors, including Monitor and communicate last days for contractors, including guests, to Security Officersguests, to Security OfficersEnsure timely notification of terminations to HREnsure timely notification of terminations to HR

Begin using the forms immediately!Begin using the forms immediately!

Logical Access: Tips to Logical Access: Tips to Make the Process Work!Make the Process Work!

Presenter
Presentation Notes
Segregation of duties: For example, a user who accesses data to read and write reports, should not have, in most cases, the ability to change or manipulate that data for his or her results. (See student grades)

7

Review of reports to ensure that users have appropriate and authReview of reports to ensure that users have appropriate and authorized orized access rights (Banner, access rights (Banner, WebFOCUSWebFOCUS, , XtenderXtender, Workflow, Axiom and , Workflow, Axiom and related databases). The following reports will be used:related databases). The following reports will be used:

•• Service Access Report Service Access Report –– Biannual Review (April and October)Biannual Review (April and October)–– A comprehensive listing of user access rightsA comprehensive listing of user access rights

•• Position Change Report Position Change Report –– Weekly ReviewWeekly Review–– Lists users who have changed positions, which may require updateLists users who have changed positions, which may require updates to access rightss to access rights–– All Business Managers involvement is not required each week; depAll Business Managers involvement is not required each week; depends on ends on

department activitydepartment activity

•• Termination Reports Termination Reports –– Weekly ReviewWeekly Review–– Lists users who have separated from the university, but who stilLists users who have separated from the university, but who still have access rightsl have access rights–– Security Officers will request that Business Managers confirm teSecurity Officers will request that Business Managers confirm terminations as needed; depends rminations as needed; depends

on termination activity for the week, if any.on termination activity for the week, if any.

•• Account Inactivity Report Account Inactivity Report –– Biannual Review (April and October)Biannual Review (April and October)–– Lists users whose accounts have shown no activity over a specifiLists users whose accounts have shown no activity over a specified period of timeed period of time–– Business Managers involvement dictated by number of inactive accBusiness Managers involvement dictated by number of inactive accounts in departmentounts in department

Logical Access: Monitoring Logical Access: Monitoring OverviewOverview

Presenter
Presentation Notes
Segregation of duties: For example, a user who accesses data to read and write reports, should not have, in most cases, the ability to change or manipulate that data for his or her results. (See student grades)

8

Service Access and Account Inactivity Reports – Review Process

• QA Administrator sends email to Business Managers (BMs) notifying them of the review

• BMs obtain reports; review access rights of users in their department for appropriateness; review users with inactivity– Utilize “Service Level Review Guide”

• If necessary, BMs initiate changes/removal of access rights using Access Security Request Form

• BMs email a Monitoring Review Form to QA Administrator noting review has been performed and action taken, if any.

• BMs maintains documentation of review for own records• QA Administrator maintains overall documentation of reviews• Service Level Review Guide and Monitoring Form:

http://http://www.slu.edu/services/HR/university_security_forms.htmlwww.slu.edu/services/HR/university_security_forms.html

Logical Access: Logical Access: Monitoring ProcessMonitoring Process

Presenter
Presentation Notes
Segregation of duties: For example, a user who accesses data to read and write reports, should not have, in most cases, the ability to change or manipulate that data for his or her results. (See student grades)

9

Position Change and Termination Reports – Review Process

• Security Officers obtain reports and confirm user status with BMs, as necessary

• If necessary, Security Officer will request that BM initiates changes to access rights using Access Security Request Form

• BM sends email reply to Security Officer noting review has been performed and action taken.

• BM maintains documentation of review for own records• Security Officer forwards Monitoring Review Form to QA

Administrator• QA Administrator maintains overall documentation of

reviews

Logical Access: Logical Access: Monitoring ProcessMonitoring Process

Presenter
Presentation Notes
Segregation of duties: For example, a user who accesses data to read and write reports, should not have, in most cases, the ability to change or manipulate that data for his or her results. (See student grades)

10

Logical Access:Logical Access:

Questions

11

Change Management : Change Management : PurposePurpose

• The IT Infrastructure is in a constant state of change. – New requirements need to be accommodated – Errors need to be corrected – Problems need solutions

• Change Management is the discipline that is used to control that process. – Understanding the risk of service failure – Ensuring that the risk is understood– Confirming that the risk is minimized

12

• Step One: Initiate the request– Business Manager (lead)– ITS (recorder)– ITS, Business Manager and/or Stakeholders (build scope)

• Step Two: Manage the Change Review– ITS Manager, Change Control Board, Quality Assurance Office

and/or Project Office (lead)– Business Manager (advise and approve)– Additional Stakeholders (advise)

• Step Three: Change Assessment– ITS Manager, Change Control Board, Quality Assurance Office

and/or Project Office (lead)– ITS and outside vendor (assess) – Business Manager and/or Stakeholders (advise and approve)

Change Management : Change Management : ProceduresProcedures

13

• Step Four: Testing– ITS Manager, Change Control Board, Quality Assurance Office or

Project Office (lead)– ITS and outside vender (build)– Business Manager and/or additional Stakeholder (review)

• Step Five: Approve and Implement– ITS Manager, Change Control Board, Quality Assurance Office or

Project Office (lead and approve)– Business Manager and/or Stakeholders (approve)– ITS (approve, manage & implement)

• Step Six: Change Closure – ITS Manager, Change Control Board, Quality Assurance Office or

Project Office (lead, review)– ITS (manage & review)– Business Manager and/or Stakeholders (review & approve)

Change Management: Change Management: ProceduresProcedures

14

– All required forms are hyperlinked in the Remedy

– All additional memo’s, electronic approvals and other documentation copied in log or files are attached

Change Management: Change Management: DocumentationDocumentation

•Documentation related to Change Management request is stored in Remedy.

•Remedy is supported by ITS.

15

Clearly define Change Goals and Objectives Clearly define Change Goals and Objectives before initiating requestbefore initiating request

Allow adequate time for all phases of Change Allow adequate time for all phases of Change process before implementation deadlineprocess before implementation deadline

Maintain accurate and complete information for all Maintain accurate and complete information for all StakeholdersStakeholders

Signatory Approval will now be requiredSignatory Approval will now be required

Tips to Make the Process Tips to Make the Process Work!Work!

Presenter
Presentation Notes
Segregation of duties: For example, a user who accesses data to read and write reports, should not have, in most cases, the ability to change or manipulate that data for his or her results. (See student grades)

16

Q & AQ & A

17

Thank You!Thank You!

Contacts:Contacts:Quality Assurance OfficeQuality Assurance Office

Tim Brooks: 977-7221

Instructional Technology ServicesInstructional Technology ServicesKen Gebken: 977-7295

Security OfficersSecurity Officers::Nick Hebel (HR) Lisa Zoia (B&F)Will Curran (Adv.) John Majesky (STU-FIA)Ellen Weis (STU)