1 / 19

NGSS Project Student Data User Group Meeting Class of ‘55 Room Van Pelt Library May 22 nd , 2014

. NGSS Project Student Data User Group Meeting Class of ‘55 Room Van Pelt Library May 22 nd , 2014 12:00pm – 1:00pm.  Agenda. The Team Project Updates and Timeline Reporting Planning Questions/Comments/Discussion.  Team Organization Chart.  Project Updates.

kelda
Download Presentation

NGSS Project Student Data User Group Meeting Class of ‘55 Room Van Pelt Library May 22 nd , 2014

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. NGSS Project Student Data User Group Meeting Class of ‘55 Room Van Pelt Library May 22nd, 2014 12:00pm – 1:00pm Student Data User Group May 22nd, 2014

  2.  Agenda • The Team • Project Updates and Timeline • Reporting Planning • Questions/Comments/Discussion Student Data User Group May 22nd, 2014

  3.  Team Organization Chart Student Data User Group May 22nd, 2014

  4.  Project Updates • Pennant was selected as the name for the portfolio of applications the team is delivering • The name was selected from over 100 entries submitted by the University community • The name is meant to connote “championship quality, collegiate life and festivity” • The name also “gracefully alludes to Ellucian’s Banner software” • Pennant also shows institutional affiliation – “Penn + Banner = Pennant!” Adam Sherr • An announcement was made in the April 22nd, 2014 edition of The Almanac http://www.upenn.edu/almanac/volumes/v60/n31/ngssname.html#sthash.1ANluIak.dpuf • Other project updates and milestones can be found in the news section of the NGSS Project Web Site: http://www.sfs.upenn.edu/ngss/ Student Data User Group May 22nd, 2014

  5.  Project Updates - Timeline • The project is divided into distinct releases, reflecting the major functional areas to be implemented • Release 1 is Pennant Accounts, which will replace the current BRS system. • Scheduled implementation is Fall, 2015 • Subsequent releases will be Pennant Records (Student Records and Registration), and Pennant Aid (Student Financial Aid), replacing SRS and SAM respectively • Scheduled implementation is TBD – but at least several years out Student Data User Group May 22nd, 2014

  6.  Project Updates - Infrastructure • Installed 6 Banner environments (Baseline, Training, Conversion, and Development, Build, and Test) • Installed Enterprise Service Bus (ESB) software (Mule), which is a key strategic component for application interfaces • Developed strategy for ESB use • Currently working on configuring Single-Sign-On for PennKey authentication Student Data User Group May 22nd, 2014

  7.  Project Updates - Infrastructure Student Data User Group May 22nd, 2014

  8.  Project Updates – Core Foundations • Completed all data mapping (bio-demographic and curricula) necessary to support Pennant Accounts (Release 1) • Worked with AR Conversion and Integration Team on first round of data migration • Student Records “Proof of Concept” effort completed with recommendations for both Release 1 and later • Currently working on design and development of ongoing interfaces to and from SRS and Pennant Student Data User Group May 22nd, 2014

  9.  Project Updates – AR Solutions • Conducted Business Process Modeling, mapping current and new processes to Banner software • Completed Fit/Gap analysis • From Fit/Gap – have developed list of Gap Solution Recommendations • Beginning design and development efforts of Fit/Gap and Banner delivered solutions Student Data User Group May 22nd, 2014

  10.  Project Updates – AR Conversion and Integration • Completed data mapping of all AR related data • Defined population of students to be included in Release 1 • Conducted initial round of data conversion • Mapped over 70 distinct integration points to the application • Currently working on design and development of all integrations, including the AR ‘Feeder Application’, which will consolidate over 30 of the integrations into a single application Student Data User Group May 22nd, 2014

  11.  Project Updates – Academic Data in Release 1 • The Academic Structure implemented in Release 1 of Pennant will include only what is required to support Student Accounts • Academic records will reflect what is in SRS, which remains the system of record for that data throughout Release 1 • Tuition Calculation will still occur in SRS during Release 1 • Release 1 decisions which affect core curricula data will be reviewed with School and Central representatives • Decisions such as consolidating Penn’s current career structure are not needed until Release 2 Student Data User Group May 22nd, 2014

  12.  Project Updates – Academic Data in Release 1 Pennant’s data model, as required by the Banner software, mandates a 4 term structure Student Data User Group May 22nd, 2014

  13.  Project Updates – Academic Data in Release 1 Banner’s software additionally requires that Penn’s Division be represented by a 2 character College code Student Data User Group May 22nd, 2014

  14.  Reporting Planning • Reporting Assumptions and Constraints • Reporting will be made available to all users requiring access • In general, currently supported tools will be employed for report delivery • Most reporting will be delivered from Oracle RDBMS data stores • Certain reports will be delivered via a static reporting environment • Report delivery from the various environments will be based on user requirements • Project budget and schedule will allow for the implementation of required reporting tools and environments • Strategies for later releases will be addressed during those implementations • Cross-collection reporting will be available via the Data Warehouse • Access to reporting will be based on users’ positions and roles Student Data User Group May 22nd, 2014

  15.  Reporting Planning • The Strategy for Release 1 Reporting is to deliver a multi-tier reporting environment for Student Accounts data • Operational Reports delivered directly via Banner software, run against the production environment • Operational Reports against an Operational Data Store – a near real time reporting environment • Other reports run against an Operational Data Store • Point-in-time operational reports delivered via a static reporting environment, such as Penn’s current implementation of systemware’s content integrator, ORM • Point-in-time reports delivered via a set of static reporting tables • Data Warehouse reports through new tables and structures in the existing Warehouse environment Student Data User Group May 22nd, 2014

  16.  Reporting Planning Student Data User Group May 22nd, 2014

  17.  Operational Data Store The Operational Data Store (ODS) will be a near real time copy of a subset of Pennant tables Data synchronization will be enabled via TCVision software, which allows for both Adabas to Oracle and Oracle to Oracle data replication In most cases, the tables will be direct copies of production data In certain tables, there may be some data decoding and de-normalization The ODS allows us to move some operational reporting off the production database, and will increase timeliness of reporting and data access for certain users and applications Student Data User Group May 22nd, 2014

  18.  Data Warehouse The current BRS tables in the Data Warehouse will continue to exist, but will no longer be refreshed Student records reporting will continue against the current Warehouse tables until the implementation of Release 2 A new set of tables will be created in the Warehouse and populated from Pennant Existing processes, such as Tuition Distribution, will be re-written to use the new data and tables Certain key reports will be centrally provided against the new data tables Mapping tables will be provided to facilitate longitudinal and cross-collection reporting An analysis is underway to determine the feasibility of converting legacy Warehouse tables into the new structures Student Data User Group May 22nd, 2014

  19.  Questions? Student Data User Group May 22nd, 2014

More Related