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

NGSSNGSS

NGSS ProjectStudent Data User Group Meeting

Class of ‘55 RoomVan Pelt LibraryMay 22nd, 2014

12:00pm – 1:00pm

1Student Data User Group May 22nd, 2014

NGSSNGSS Agenda Agenda

¨ The Team¨ Project Updates and Timeline¨ Reporting Planning¨ Questions/Comments/Discussion

Student Data User Group May 22nd, 2014 2

NGSSNGSS Team Organization Chart Team Organization Chart

Student Data User Group May 22nd, 2014

3

NGSSNGSS Project Updates 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/


4

http://www.upenn.edu/almanac/volumes/v60/n31/ngssname.html

http://www.upenn.edu/almanac/volumes/v60/n31/ngssname.html

NGSSNGSS Project Updates - Timeline 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


5

NGSSNGSS Project Updates - Infrastructure 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


6

NGSSNGSS Project Updates - Infrastructure Project Updates - Infrastructure


7

NGSSNGSS Project Updates – Core Foundations 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


8

NGSSNGSS Project Updates – AR Solutions 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


9

NGSSNGSS Project Updates – AR Conversion and Integration 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


10

NGSSNGSS Project Updates – Academic Data in Release 1 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


11


¨ Pennant’s data model, as required by the Banner software, mandates a 4 term structure


12

SRS Term Pennant Term Description

2014A 201410 Spring, 2014

2014B 201422 Summer I, 2014

2014B 201424 Summer II, 2014

2014C 201430 Fall, 2014


¨ Banner’s software additionally requires that Penn’s Division be represented by a 2 character College code


13

SRS Division Pennant College Description

CGS AL College of Liberal & Professional Studies

COL AB College of Arts & Sciences

GAS AP Graduate Arts & Sciences

SPC AE English Program for Foreign Students

NGSSNGSS Reporting Planning 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


14


¨ 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


15



16

NGSSNGSS Operational Data Store 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


17

NGSSNGSS Data Warehouse 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


18

NGSSNGSS Questions? Questions?


19

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

Documents

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