1. ASSIST: Next Generation 2013 CIAC Annual Conference April 25 – 26, 2013 Nathan Evans, Chancellor’s Office, California State University Shawn Brick, Office of the President, University of California Jeff Spano, Chancellor’s Office, California Community Colleges

2. What We Plan to Cover Today Project Background Project Status, Challenges and Risks Visual Prototype Screens How Articulation Officers Can Help

3. ASSIST Organizational Structure ASSIST is intersegmentally funded and managed – CSU, CCC, UC (also the fiscal agent for ASSIST) Executive Management and Oversight Committee (EMOC) – Nathan Evans (CSU), Jeff Spano (CCC), Shawn Brick (UC ) Technical Advisory Committee (TAC) – George Mansoor (CSU), Bob Quinn (CCC), Jane Meyer (UC) ASSIST Client Services (ACS) – Five support staff located in Irvine CA ASSIST Advisory Committee

4. How We Got Here… ASSIST started in the mid-1980’s, last significant update mid- 1990’s – ASSIST has not kept pace with technology advances over the years – Unsupported software, poor database architecture, disjointed systems, outdated views, etc. Timeline – 2008 Vision Meeting – 2009 Segment Funding Commitment, Business Plan – 2010 Requirements Gathering with Users – 2011 Competitive Request for Proposal Process – 2012 to present; Vendor Award, Project Start, Prototypes

5. Project Status Three Development Phases, One Implementation – Core Services, Enhanced Services, Data & Reporting Methodology – Each phase: Design, Prototype, Develop, Test, Sign-off – Final: System testing, data migration, training, implementation Timeline (now) Concluding core services prototyping, beginning development portion (Oct ‘13) Begin enhanced services design and prototype phase (July ‘14) Begin prototyping Data Services & Reporting phase (Nov ‘14)Next Generation implementation go-live

6. Key Challenges / Risks Migrating Published Agreements Implementing During or Between Update Cycles Training Users: Counselors, Students, Faculty, Staff, etc. Successfully Managing Scope and Timeline Adapting to a Data-driven Environment

7. Text in ASSIST

8. Let’s Take a Look at Some Screens…

9. Public / Home Page

10. Public / Options Page

11. Public Views

13. Curriculum Maintenance

14. Articulation Maintenance

15. Reports

16. Workflow

17. Expected Project Outcomes An Updated and More Intuitive ASSIST Web Site; Efficiency Gains From the Integration of Segment Tasks; More Well Designed and Easily Searchable ASSIST Database; Enhanced Features eg: workflow module, user defaults, etc. Improved Data Services to Provide Rich Exchanges of Data; Minimized Maintenance Costs

18. How AOs Can Help… Remain informed, and keep others on campus informed Understand any changes necessary at your campus to support the new application Develop a campus implementation plan that compliments the overall project plan Volunteer your time when called upon

19. Questions / Comments Nathan Evans nevans@calstate.edunevans@calstate.edu Shawn Brick shawn.brick@ucop.edushawn.brick@ucop.edu Jeff Spano jspano@cccco.edujspano@cccco.edu