Skip to main content

2024-2025 Next Frontier Program Priorities

Download a printable version of 2024-2025 Next Frontier Program Priorities

In alignment with the FY25 Next Frontier Budget Request and the original goals of the Next Frontier Program, the Next Frontier Program Committee proposes the following 2024-2025 priorities. The reference numbers in this document tie back to the original program goals:

1. Critical Current and Pending Initiatives

Current and pending projects for FY25 include (i) resolving the security and reconciliation issues of the Sponsored Project Budget v. Actuals (BvA) Report, (ii) identifying needs for data integration and reporting to support campus needs for RCM (Responsibility Center Management) and ensuring consistency with data management best practices by both preserving continuity of reporting when Axiom is utilized and ensuring the right Axiom data is flowing to the right places (e.g. Oracle, Data Warehouse, etc), also ensuring this work supports priority 1.v, (iii) to reduce current security risks, finalize the move from the current on-premise data warehouse to Oracle Cloud Infrastructure, (iv) establishing and maintaining regular communication channels with stakeholders across campus, and (v) working toward the all funds BvA report (6.1.1.b). All of the above activities will incorporate end user input, including for requirements gathering, technology assessment, and evaluation.

2. Foundational Objectives that will Support Next Frontier Program Success

(i) Review and update definitions for the data owner, data steward, and data custodian roles and begin to educate the campus community (4.1 & 4.1.1).

  • Where practicable, identify high-priority data areas and support adoption of the newly defined responsibilities.
  • Identify active projects that can be bolstered by this support and engage where bandwidth allows.

(ii) Intentionally use inclusive practices for gathering and incorporating campus and end user input and requirements for projects (3.3) AND guard against unintentional negative spillover impacts (for example, changes in the AAR report need to account for the various stakeholders across campus with appropriate change management accompanying updates). This will include defined methods for measuring progress toward program goals.

(iii) Make progress toward our goal of a singular and comprehensive visualization tool that addresses campus-wide requirements (5.2) by:

  • Conducting a review of shadow systems to understand capabilities and reasons for them to inform overall design and development of data structures and to explore scalable best practice approaches (5.3), including data sources and uses.
  • Developing a Next Frontier Program roadmap, inclusive of technical requirements (will aid 1.6) and consistent with the inclusive practices referenced in objective 3.3.
  • Note: It will be difficult to identify a visualization tool that can meet the needs of the University until after the two steps above are complete, likely pushing the goal of adopting a singular and comprehensive data visualization tool (5.2) into a future prioritization plan.

(iv) Continued improvements to the Data Cookbook (6.3)

Upgrade to the Data Cookbook Intelligence edition to replace our discontinued Knowledge edition. This will support data validation and integrity, as well as more efficient reporting design and information system integration work.

(v) Define values for the next Frontier Program to guide our approach and decision-making in alignment with the Next Frontier Program’s vision and charge.

(vi) Strive to improve data quality by refining the Data Governance Committee’s role in identifying, understanding, and enforcing data governance best practices.

9/23/2024