SIS M

ODERNIZAT

ION

PROJE

CT

I NS

TI T

UT

I ON

AL

EF

FE

CT

I VE

NE

SS

& S

TU

DE

NT

SU

CC

ES

S

NO

VE

MB

ER

20

, 20

13

IMPLEMENTATION TEAM

The SIS project is a joint project managed by both the Educational Programs and Institutional Effectiveness Division and Information Technology Division at LACCD

Administrative Oversight: • Ms. Bobbi Kimble, Interim Vice Chancellor of Educational Programs and Institutional

Effectiveness

• Mr. Jorge Mata, Chief Information Officer

Implementation Team Consists of Three Leads: • Mr. Chris Nersisyan, IT Project Manager for LACCD

• Mrs. Betsy Regalado, Lead Functional Administrator for SIS Project, LACCD

• Mr. Joey Harpst, Project Manager, Ciber

WHAT IS THE STUDENT INFORMATION SYSTEM? The SIS is a vital tool in delivering student services while at the same time supporting teaching and learning. It is an electronic system that: • Creates the schedule of classes;• Provides transcripts;• Manages the financial aid process;• Links faculty assignments to the courses they teach;• Records grades;• Calculates a student’s GPA;• Serves as a data source for MIS, accreditation, AtD, SLO ;• Manages student fees; • And much more

CURRENT STATUS: PHASES OF THE PROJECT

• Discovery (Complete)• Configuration(In-progress)• Testing• Training• Go-live

CURRENT STATUS: FIT GAP ANALYSIS SESSIONS

February 19 throughApril 23,

2013

40 Sessions

27 Departments

&150

Unduplicated Employees

CURRENT STATUS: COMMUNICATION PLAN

• Monthly Newsletters• SharePoint Collaboration hosted

on district server• On-going in-person presentation

at the various district committees• College Roadshows

ORIGINAL DEPLOYMENT OPTIONS

• RFP proposed plan was to use two beta campuses • Pierce College• Valley College

• In year two , the SIS will be deployed at the remaining 7 colleges

At the conclusion of the Discovery Phase of the Project , the management team revisited the deployment plan and now is considering a pilot by module roll-out instead.

CHANGE INITIATIVE: ORIGINAL DEPLOYMENT PLAN RATIONALE

• Reduce Project Risk• Prevent repeat of SAP implementation

issues• Prevent “Big-Bang” deployment • Be able to conduct a thorough test of a

complete system before all campuses Go Live.

CHANGE INITIATIVE: ORIGINAL DEPLOYMENT TIMELINEProject Schedule

2012

Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec

Install

LACCD PHASE 2

LACCD PHASE 1

LOS ANGELES COMMUNITY COLLEGE DISTRICT IMPLEMENTATION TIMELINE

2013 2014 2015 2016

DiscoveryCharter

Fit/Gap Admissions / Recruiting Production Support

Student Records Production Support

Financial Aid

Test / Train

Test / Train

Student Financials

Academic Advising

Enterprise Portal Test

Test / Train

Test / Train

Test

Production Support

Production Support

Production Support

Data Warehouse

MIS/320 Reporting Test

Test Production Support

Production Support

ADM Test / Train

SR Test / Train

FA Test / Train

SF Test / Train

Production Support

Production Support

Production Support

Production Support

AA Testing Production Support

Enterprise Portal Production Support

Data Conversion

Data Conversion

MIS/320 Reporting

CHANGE INITIATIVE:RECOMMENDED DEPLOYMENT RATIONALE• Module-by-Module - across all nine colleges• Prevents a BIG BANG roll-out• Based on student enrollment life -cycle

ADMISSIONS PROGRESS TIMELINE

STUDENT RECORDS PROGRESS TIMELINE

FINANCIAL AID PROGRESS TIMELINE

STUDENT FINANCIALS PROGRESS TIMELINE

ENTERPRISE PORTAL PROGRESS TIMELINE

CHANGE INITIATIVE: COMPARISONS

A D V A N T A G E

•Ease of maintenance

•Standardized business processes

•Regulatory compliance

•MIS and “320” Reporting

•Minimized duplication

•Data between PeopleSoft and DEC remains consistent

•Implementation Go-Live once

•Resolves enrollment issues

W H A T ’ S D I F F E R E N T

•Current plan deploys two beta campuses in year one and remaining seven in year two

•Future Plan would deploy all nine colleges at one time in a phased deployment

Mitigation strategy wouldn’t extend beyond the original project timeline

DEPLOYMENT PLAN CHANGE RATIONALE

• Original RFP assumption was that LACCD operated as nine separate, independent colleges and the original configuration design considered was multi-institution.

• After the technical analysis was completed, it became apparent how much the Colleges share data and are tightly coupled

• ESC would need to increase its support staff to maintain the multiple solutions.

• Self Service issues with students having to switch back and forth between legacy and new system if they attend both pilot and non-pilot colleges

• Essentially running two SIS systems in same organization, integrity of MIS and 320 reporting would be compromised

CONSULTATION – SUPPORTING GROUPS

New module deployment plan was vetted and supported by the following district-wide committees:

1) Business functional users

2) Student Affairs Council

3) AFT College Staff Guild

4) District Academic Senate Execute Council

5) Operational Steering Committee

6) SIS Policy Advisory Committee

7) Senior Management

8) President Cabinet

9) Interim Chancellor

CHANGE INITIATIVE:ACTION ITEMS

Project Team & Legal Counsel

•Amend Implementation Agreement

Board of Trustees

•Approve Amended Implementation Agreement

PROJECTED PLANS:CONTINUED CONFIGURATION

• Weekly Configuration Meetings with Functional Users• Monthly Configuration Review Meetings• Data Conversion and Validation• Design and Development of required in-scope

customization • Development of the Marketing and Communication Plan

PROJECTED PLANS:STUDENT AND FACULTY INVOLVEMENT

• Student and Faculty Focus Groups:• Feedback on system and navigation • Feedback on the enterprise portal• Feedback on mobile device access and ease

• Assist with Marketing Campaign

THANK YOU FOR YOUR CONTINUED SUPPORT!