1 / 27

ITIAG

ITIAG. January 8, 2009. Mission Statement.

jonny
Télécharger la présentation

ITIAG

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. ITIAG January 8, 2009

  2. Mission Statement • The mission of the SIS Replacement Project (MetamorphoSIS) is to successfully replace CU’s current student information system, and its components, within budget and on schedule, taking advantage of new features and technology to improve services to students, faculty, staff, and others.  To achieve this mission, the Project must develop the knowledge and skills that staff will need to implement the system and to support it in the future.

  3. Objectives • Implement a system that gives CU a single system of record for all students with the flexibility to accommodate distinct processes of campus offices to support different student populations and campus policies. Such a system will support the needs of undergraduate and graduate programs, professional schools, continuing education, and extended study programs.

  4. Objectives • Minimize customizations to the system as much as possible. Consider modifications to the new student system only when they are required for compliance reasons or to support core functionality, or if it can be proven that the work cannot be accomplished by adjusting business practices, and that any modification significantly enhances the delivery of services to system stakeholders. Consider revising business processes and adopting best practices where appropriate. Take advantage of new features, technology, and opportunities in the system to improve service and enable more efficient operations. Enhance self-service functions for students and faculty while maintaining comparable levels of service found in the existing system.

  5. Objectives • Improve inter-operability between SIS and satellite systems, in particular, more real-time inter-operability using industry standards.

  6. Objectives • Provide University administrators with comprehensive data for planning and analysis, using both easy-to-use reporting tools and more sophisticated tools for analysis. Improve data quality and timeliness when and where possible.

  7. Objectives • Develop the IT infrastructure for high availability and reliability, driving toward 24/7 availability, 365 days per year. Establish a cost-effective disaster recovery and business continuity program including processes, systems, and an off-site recovery facility.

  8. Major Components • Campus Solutions including Admissions, Student Records and Registration, Financial Aid, Student Financials (billing and collections), self-service for students and faculty. • Customer Relationship Management (CRM) for student recruiting • Degree Audit • Document Management • Data Conversion • Data Warehouse, reporting, and analysis • Master Data Management for ID management and data quality • New portal for faculty, staff, and students • Classroom scheduling • Web-based training and on-line help system • Software systems to support improved integration of systems and automated workflow

  9. Go-Live Target Term and Dates • Customer Relationship Management Pilot (September 2008). Now “live” for CU Denver undergraduate programs and School of Nursing • Degree Audit, Fall 2008 on a phased roll-out, all campuses • Admissions and full deployment of CRM to all campuses, Summer 2009 • Financial Aid, January 2010 • Registration for Fall, April 2010 • Tuition Calculation and Billing, Summer 2010 • Full “go-live,” Fall 2010

  10. Project Go-Live Dates

  11. Project Organization • SIS Executive Steering Committee • Vice Chancellors and Associate Vice Chancellors for Academic Affairs, Administration and Student Services • Vice Presidents for Administration, Budget and Finance, and Academic Affairs • Chair, Faculty Council • Chair, Staff Council • Project management team • SIS Project Advisory Committee • Student service directors, all campuses • Associate Deans • Institutional Research • Faculty Council representative

  12. Project Organization • Campus Review Teams (at each campus) • Student services • Faculty Assembly representatives • Associate Deans • Technology • Institutional Research • Campus Liaisons • UCB – Barb Todd • UCCS – Steve Ellis • UCD – Kaye Orten, Teri Burleson, Ingrid Eschholz

  13. Project Organization • Special Interest Groups • Academic Administrators • Data Warehouse • System Architecture • Project Teams (project managers, student service experts, IT experts) • Admissions/CRM • Financial Aid • Student Finance • Student Records • Degree Audit • Application Programming • Document Management • Portals • Data Warehouse/Reporting • IT Infrastructure • Consulting Partner • Oracle/Ciber

  14. Technology Components • SOA Suite • Workflow capability • Reporting • Master Data Management

  15. SOA Suite • Product Name for Oracle Fusion Middleware suite. • Includes the technology that enables BPEL processing, policy based security management of web services, message transformation and routing, etc. • Foundational technology, controlled scope for the implementation • Five integration Patterns

  16. Workflow • Native, application-based workflow • Enterprise, BPEL-based workflow • Flex as a front end

  17. Reporting • Source: Transactional System vs. the new CIW • Tool: PS Query (with or without XMLP) vs. Cognos • Determining factors: Data availability, timeliness of data, complexity of reporting

  18. Goals for MDM • De-Dup Constituent Data for Campus Solutions Implementation • Synchronize Constituent Information • HCM 8.9 • Campus Solutions 9.0 • CRM 9.0 • Publish Constituent Information • Campus Directories • Identity (user) Provisioning • Numerous administrative & academic systems • Retire Expensive Custom Solutions • Complex pseudo hubs • Redundant business logic (affiliations!) • Limited integration capabilities (nightly!) • Expensive to maintain & leverage • Various “exception” constituent provisioning systems

  19. Before…

  20. Before… Lots of awkward, point to point, batch oriented (daily at best!) Flat-File based integration

  21. After…

  22. Legacy PSFT CS Legacy Legacy Boulder SIS New SIS Colorado Springs SIS Denver SIS Cleansing/Matching Server(s) Data Quality Engine Pre-Conversion

  23. PSFT CS PSFT CRM PSFT HCM OSS SCM Cross Referencing • Stores all Student identifiers for the operational applications connected to UCM • Provides critical mappings used for data synchronization, reporting, and analytics • Supports 1-to-many cases in which multiple Student records exist in an application that map to one master Student record Student ID:333333 Applicant ID:111111 Employee ID:444444 Universal ID:1ASCLSCC

  24. PSFT CS PSFT CRM PSFT HCM Search/Match Prospect Load New-Hire Application • Informatica’s Matching Engine • High Volume, High Precision real time matching • OTB Integrated with Campus Solution’s Search/Match • Fuzzy searches (Mike = Michael…) Search/Match Do we already know you??? UCM

  25. Survivorship Rules • Survivorship Rules: • Preserves master data • Are highly configurable • Determines: • Update privileges • Contention resolution • Granular Rules: • Object based rules • Source confidence rules • Temporal rules • Attribute groups • Attribute group fields

  26. Questions?

More Related