UBC IT Integrated Reporting Working Committee April 4 th, 2012.

UBC IT

Integrated Reporting Working Committee

April 4th, 2012

Recap & Action Items from Last Meeting (Pam/Andrew/Heather, 5 min)

Program Status: (Dave, 10 min)

Recap Student Foundation Scope Confirmation(Heather, 20 min)

Budget for Undergraduate Admissions Functionality (Dave, 30 min)

Finance Demo (Andrea, 15 min)

Next Steps and Wrap Up (Pam/Andrew/Heather, 5 min)

Agenda

(Feb 15)• If you have feedback (regarding the program Status) please

contact David Truong for further discussion.• Question for members (regarding Finance Discovery): Need to

confirm that there is no need to bring Finance Data prior to 2004 into the Enterprise Data Warehouse.

• We (Andrea and Heather) are working on a program glossary.

(March 15)• Add agenda item for next regular Working Committee meeting on

April 4: Detailed funding proposal associated with new scope.• DONE!

Follow Up Items:

Need approval to add two statements to the Minutes from Feb 15, 2012 meeting:

In Summary (Finance Foundation Scope Confirmation):The Working Committee, represented by all in attendance, confirms the Release 1 scope for Finance Foundation as presented by Andrea. In Summary(Student Foundation Scope Confirmation):The Working Committee, represented by all in attendance, confirms the Release 1 scope for Student Foundation as presented by Heather.

Amendment to February 15 Minutes







Agenda

May Jul Aug Sept Oct Dec Jan-2013 NovOn-going Management

Foundation Phase, Release 1 Plan

Finance Foundation Development

Quality Assurance

Define QA Approach Finance SIT Preparation

Student SIT Preparation

Finance UAT Preparation

Technical Architecture

Plan & Analyze

Setup Finance DEV Setup PROD

Environment Support

Change Management1

INFA & OBIEE Training

Prepare Train-Trainer Materials (Finance)

Train-Trainer

Today

Feb

Finance BRD Sol’n Blueprint

Updated WBS Updated

JunApr Mar

Design/Build/Test GL Dashboards Execute SIT Execute UAT

Execute Performance Test

Mar-2012

Plan & Analyze

SIT Test Results

Test Summary Sign-off

UAT Test Results Test Summary Sign-off Deployment to core

Financial Users

ORT completed Deployment to Broad

Financial users

Design/Build /Test Records & Registration

Student Foundation Development

Student BRD Sol’n Blueprint

Updated WBS Updated

Design/Build/Test Student BIO Design/Build/Test SFM Execute UAT

Execute Performance Test

Deploy

Go Live #3

Plan & Analyze

ETL Data Mapping Logical Data Model

Updated Report mock-ups Sol’n Blueprint Updated QA Test Plan

ETL Code DW DDL OBIEE Code Unit Test Results SIT Test Plan

Updated

SIT Test Results


UAT Test Results


ORT completed

Deploy to all users

QA Approach

Deploy 2

Go-Live #2

Design Common Components

Build/Prototype Common Components

Setup Student DEV

Setup Finance SIT Setup Finance UAT & PERF

Setup Student SIT

Test Plan & Scripts Expected Results

Plan & Prepare Performance Test

Plan & Prepare Performance Test


Student UAT Preparation



Change MgmtApproach

Program Communication

PerfResults & Stress Baseline

PerfResults & Stress Baseline

Support End-User Training Prepare Train-Trainer Materials (Student)

Train-Trainer

Support End-User Training

Setup Student UAT & PERF

Test Plan & Scripts Test Plan & Scripts

Tech Arch diagrams

Tech Arch diagrams

Regression SIT


Updated

Design/Build /Test Admission

Design/Build/TestAP & PO Dashboards


Updated

HR/PayrollChartfieldLookup

Deploy 1

Go-Live #1

Program Status







Agenda

Confirmed original proposal in February ISI Proposal sent to Governance Committee Chairs Adjusted student scope proposal presented to Governance Committee Held interim meeting to consider ISI proposal to add Admissions and

Recruitment to Release 1 Confirmed addition of Undergraduate Admissions Subject Area to Release 1

subject to approval of additional resources required

Now … Going to review Project Charter for Student Foundation That includes amended high-level scope for Release 1

Student Foundation Scope Confirmation - RECAP

Student Foundation Business Drivers

Be THE source of enterprise student data, that is: Centrally defined and governed Of the best quality possible Well-documented

Cross-functional analysis Self-service reporting Designed to be Extensible Improved traceability

Success Criteria for Student Foundation

Functionality Subject Areas Architecture Integration Data Quality Documentation

Student Foundation Scope for Release 1

Student Revenue Analytics capabilities: Support the Faculty Funding Model

From the perspective of the faculties, central finance and PAIR Linkages: Tuition Revenue – Course Registration – Finance Chart fields Ad hoc student revenue analysis

Enrolment Data for Admissions and Recruitment Applicant Funnel: current data set Total Registered Students for ISI

Impact Analysis on Existing Capabilities Impact analysis on existing content: reports, data feeds, interfaces Consider systems consuming SIS data such as PAIR

Historical Scope

Functionality

Undergrad Application

RecruitmentStudent Financials

Records & Registration

Student Biographical• Name• Address• Email Address• Phone No.

• Country of Citizenship• Visa type, effective date• Age, Gender• …..

• Campus• Faculty• Department• Specialization

• Course• Grades• Sessional

Average• …….

• Application, Intention(s) • Program, Degree, Spec• ISI Status, Region• Previous Institutions• Basis of Admission• …..

• Campus Tours• School Visits• Email Campaigns• Events (e.g. Degree in a

Day)

• Assessment• Installment• Payment• Awards

Student Subject Areas

Architecture

Integration

FMS

FMSDept

SIS

SISDept

EDW

Dept

Conformance Consistent Definition: Student = Finance

Business : e.g. match department, faculty relationship trees Technical : make sure internal structures match

Industry Lingo: “Conform Dimensions” Time (Fiscal Year, Academic Year … ) Organization (Faculty, Department, School …) Student (Person)

Role of Governance

Linkage between Student Revenue and Finance synchronization

Integration

Identification of data quality issues Definition violation

e.g. Course cannot have an end date in year 4000 Business Rules violation

e.g. Student cannot apply to session 2010W in November 2011 Structural Integrity violation

e.g. Tuition assessment with no corresponding student

Cleansing mechanisms Process to manage data quality issues once identified

Some automated (minimal) Some manual (most)

Governance when required

Data Quality Management

Central Repository of Data and Business Definitions Existing Systems + Enterprise Data Warehouse Foundational data

Student Biographical Student Finance Course Registration Curriculum

Derived data, e.g. ISI flag FTE

Documentation

Migration of existing reports, data feeds, interfaces Decommissioning Existing Reporting Tables and Replacing or decommissioning PAIR infrastructure Future Student Subject Areas Campus Solutions Warehouse Implementation

Have demo with a demo data only

NOT in Scope for Student Foundation R1

Risks Risk/Issue Likelihood - Impact Mitigation Strategy Status1.0 Resource Availability High - High Open

1.1 Addition of Admissions Scope to Student Foundation Release 1.

High - High Additional budget to fund additional human resources

Open

2.0 Lack of DW experience on the team and use of OBIEE tools: Schedules may be impacted

High - Medium Training; Expectations managementScope Management

Open.Will attenuate with time.

3.0 Poor source system data quality; Lower data quality in a source system means unpredictability in time estimates and schedules because of unanticipated issues;

High - Medium Open

4.0 Newness of Master Data Management and data governance process to UBC;

High - Medium Program level training and reinforcement.Organizational training.

Open.Will attenuate with time.

5.0 Newness of PMO methodology: Medium - Medium Program level training and reinforcement.

Open.Will attenuate with time and Experience.

Questions or concerns?

Confirmation of Student Foundation Scope







Agenda

Total Design, Build & Unit Test Effort (days) 634Total Project Estimate - No Contingency (days) 1,413

Total Project Estimate - Contingency (days) 1,555Number of FTEs 7.9

Desired Duration (months) 9contingency (%) 10%

Total Contingency (days) 141

FactorH M L (days/unit)

1. Project Management 140Project Management % of Development Effort 10% 127QA Review(s) % of Project Management 10% 13

2. Plan & Analyze 35

Gather Inital Information f ixed 10 10Project Definition f ixed 10 10Mobilize Project f ixed 10 10Requirements Analysis Subject Areas 1 5 5

3. Functional Design 137

Functional Design - Back-EndFunctional Design - Oracle Pre-Built ETLs Oracle Pre-Built Extracts 0 2 1 0.5 Complexity 0Functional Design - ETL tool ETL tools 46 3 2 1 Complexity 133Functional Design - Non-Oracle Non-Oracle Custom 0 3 2 1 Complexity 0Functional Design - Data Stores Data Stores 3 3 2 1 Complexity 3

Functional Design - Front End Functional Design - Ad-hoc Queries Ad-hoc Queries 5 1 0.5 0.25 Complexity 1Functional Design - BI Publisher Reports BI Publisher Reports 0 1.5 1 0.5 Complexity 0Functional Design - Dashboards Dashboards 0 1.5 1 0.5 Complexity 0Functional Design - Data Exports Data Exports 0 1 1 0.25 Complexity 0

4. Technical Design 137Technical Design - Back End

Technical Design - Oracle Pre-Built ETLs Oracle Pre-Built Extracts 0 2 1 0.5 Complexity 0Technical Design - ETL tool ETL tools 46 3 2 1 Complexity 133Technical Design -Non-Oracle Non-Oracle Custom 0 3 2 1 Complexity 0Technical Design - Data Stores Data Stores 3 3 2 1 Complexity 3

Technical Design - Front EndTechnical Design - Ad-hoc Queries Ad-hoc Queries 5 1 0.5 0.25 Complexity 1Technical Design - BI Plublisher Reports BI Publisher Reports 0 1.5 1 0.5 Complexity 0Technical Design - Dashboards Dashboards 0 3 2 1 Complexity 0Technical Design - Data Exports Data Exports 0 1.5 1 0.5 Complexity 0

5. Build and Unit Test 359Build & Unit Test Back End

Build & Unit Test - Oracle Extracts/Datasources Oracle Extracts 0 4 2 1 Complexity 0Build & Unit Test - Non-Oracle Extracts/Datasources Non-Oracle Extracts 0 8 4 2 Complexity 0Build & Unit Test - ETL tool ETL tools 46 8 4 2 Complexity 348Build & Unit Test - Data Stores Data Stores 3 8 4 2 Complexity 6

Build & Unit Test Front EndBuild & Unit Test - Ad-hoc Queries Ad-hoc Queries 5 4 2 1 Complexity 5Build & Unit Test - BI Publisher BI Publisher Reports 0 6 4 2 Complexity 0Build & Unit Test - Dashboards Dashboards 0 8 6 3 Complexity 0Build & Unit Test - Data Exports Data Exports 0 4 2 1 Complexity 0

6. System Integration, Perf., User Acceptance Tests 276System Integration Test % build 50% 180Performance Test % build 35% 48User Acceptance Test % build 35% 48

7. Change Management 25Develop Learning Products & Train Users subject areas 1 5 5Train Users training sessions 4 5 20

8. Deploy 50% of build 10%

9. Technical Architecture 153% of Total Development 15%

10. Post Production Support 102% of Total Development 10%

Notes:-White fields are editable-Estimating factor # Units are sources from "Estimating Factors" sheet

Work EffortTask Factor Applied # Units Estimate

(days)Complexity

Solution Layer AssumptionReports/Interfaces 5 medium Ad-hoc queriesData Stores Followed Sources (4 high, 1 medium)Data Integration Followed Sources (41 high, 5 medium)Sources (total):

Sources Previous Institution (5 medium)Sources Intention (10 high)Sources BBA (score, P.P.) (6 high)Sources Highschool Grades (10 high)Sources Misc. Docs (15 high)

Data Stores Assumed 1 datamart, 1 DW, 1 ODS (all low)Users assumed 100 users

634 person-days of effort$253,200 budget2.5 FTE

1. Estimating Factors 2. Top-Down Estimating Model

Impact Analysis conducted for Admission

3. Impact of Admission:

Potential Sources of funding?

• ISI• Faculties• Moving budget forward from FY13/14• Other?

We need to discuss how to fund the increased Admission scope:







Agenda

Finance Demo by Andrea







Agenda

Next Steps and Wrap-Up

UBC IT Integrated Reporting Working Committee April 4 th, 2012.

Documents

Transcript of UBC IT Integrated Reporting Working Committee April 4 th, 2012.