CASE FOR CHANGE
We heard from the community that collecting data and transforming it into useable information can be frustrating, time consuming, and labor intensive.
There are multiple factors that contribute to our current state. Below are six that can be directly linked to this perception of both data and analytics being difficult to acquire.
Click on a section title below to expand for more information.
Absence of Common Terminology & Definitions
- Many terms are used regulary which have different meanings to different people at different times (e.g. FTE, GPA)
- Reports may be interpreted differently or use different sources to answer the same question
Limited Fluency Across Systems and Functional Areas
- Limited number of employees that are fluent in one enterprise system or functional area and have a working knowledge in one or two others (e.g., fluent in student data, working knowledge of human resources data).
Lack of a Comprehensive Analytics Environment
- Our current environments (provided centrally and by units) for reporting and data analysis meet many needs, but do not support all needs of Penn State, and are not integrated into a coherent system.
Inconsistent System Integration
- This makes reporting and analytics difficult, especially when trying to combine data from multiple systems (e.g., three ERPs, CRMs, advising)
Unclear Engagement Models
- Processes are confusing, labor intensive, slow, and opaque.
Lack of Consistent Data Governance
- Inconsistencies exist between Penn State policies and processes. In some cases, the policy changes have not been reflected in processes.
- We lack a defined governing body to review existing policies for needed changes and to consider new policies. With the increasing amount of data available and the escalating need to leverage the data, there is a need for dedicated resources to execute policies and procedures.
Absence of Common Terminology & Definitions
- Many terms are used regulary which have different meanings to different people at different times (e.g. FTE, GPA)
- Reports may be interpreted differently or use different sources to answer the same question
Limited Fluency Across Systems and Functional Areas
- Limited number of employees that are fluent in one enterprise system or functional area and have a working knowledge in one or two others (e.g., fluent in student data, working knowledge of human resources data).
Lack of a Comprehensive Analytics Environment
- Our current environments (provided centrally and by units) for reporting and data analysis meet many needs, but do not support all needs of Penn State, and are not integrated into a coherent system.
Inconsistent System Integration
- This makes reporting and analytics difficult, especially when trying to combine data from multiple systems (e.g., three ERPs, CRMs, advising)
Unclear Engagement Model
- Processes are confusing, labor intensive, slow, and opaque.
Lack of Consistent Data Governance
- Inconsistencies exist between Penn State policies and processes. In some cases, the policy changes have not been reflected in processes.
- We lack a defined governing body to review existing policies for needed changes and to consider new policies. With the increasing amount of data available and the escalating need to leverage the data, there is a need for dedicated resources to execute policies and procedures.