Edify - Institutional Data Warehouse

Edify Implementation Roadmap

Edify FAQs
MSU has data across many systems. Five main benefits driving the implementation of Edify include:
- Increased quick access to high-quality data for decision support
- Established institution-wide source of truth
- Reduced manual effort and reporting burden
- Stronger data governance and security
- Foundation for future AI and advanced analytics
Edify can bring together data from major university systems such as student, HR, finance, learning management, advising, admissions, and other operational systems. The rollout will occur in phases based on institutional priorities and implementation timelines. Current information systems Edify has access to includes Banner, Canvas, Navigate, and DegreeWorks.
No. Edify does not replace Banner or other source systems. Those systems remain the official systems where daily business transactions occur. Edify is designed to organize and prepare data from those systems for reporting, analytics, and decision support.
Access will be based on a person’s role, business need, and approved permissions.
Users will only be able to see the data they are authorized to access. These roles
and permissions may differ by each MSU campus and respective data goverance efforts.
Currently, the Chief Data Officer and Edifiy Implementation Advisory Group is informing
access permission levels while setup is happening.
Over time, campus users should experience:
- Clearer definitions for commonly used data
- More consistent reporting across MSU
- Easier access to approved reports and dashboards
- Better understanding of where data come from
- Stronger data governance and access controls
- Less reliance on one-off manual data pulls
Edify supports role-based permissions and row-level security, helping ensure sensitive student, employee, financial, and institutional data are protected and only available to approved users. EAB is in compliance with FERPA and GDPR practices and requirements. Please visit the EAB Trust Center for more details.
Yes. Edify includes a data catalog, data dictionary, business glossary, metadata tools, and data lineage features. These tools help users understand where data comes from, what fields mean, and how data are used across reports and dashboards.
Yes. Edify supports dashboards, reports, and analytics workspaces. MSU will prioritize reporting and analytics based on institutional needs, including common “must-run” reports and decision-support tools.
Yes. Edify can support data delivery to external business intelligence tools, including tools such as Power BI and Tableau.
Yes. Edify includes AI-enabled features that can help users search for data, better
understand data structures, explain SQL, and support plain-language report development.
MSU institutional data are not accessible to external AI applications, and the data
cannot be retained or used to train AI models outside the approved IDW environment.
Edify will be implemented in phases. Availability of specific data domains, reports, dashboards, and user access will depend on MSU’s implementation schedule, data validation, governance review, and training readiness. Continue to review the above roadmap for updated times each month.
The Edify Implementation Advisory Group informs the development and implementation of MSU’s new institutional data warehouse. This is accomplished through the following engagements:
- Provide subject-matter expertise to support data definitions, business rules, priorities, and use cases during implementation.
- Contribute feedback and recommendations on data availability, quality, governance, and reporting needs to ensure the IDW supports institutional decision-making.
- Support change management and adoption by communicating updates, gathering feedback, and helping translate IDW capabilities into practical use within your area.
Here is the teams linke to join: Teams Link
The Edify Implementation Advisory Group informs the development and implementation
of MSU’s new institutional data warehouse. Edifiy Implementation Advisory Group members
change based on data domain implementation.
This is accomplished through the following engagements:
- Provide subject-matter expertise to support data definitions, business rules, priorities, and use cases during implementation.
- Contribute feedback and recommendations on data availability, quality, governance, and reporting needs to ensure the IDW supports institutional decision-making.
- Support change management and adoption by communicating updates, gathering feedback, and helping translate IDW capabilities into practical use within your area.
Questions about Edify, data access, reporting priorities, or data definitions should be routed to MSU’s Chief Data Officer (luke.schalewski@montanta.edu).
