A higher-education institution using Ellucian Banner SaaS for Student Aid needed a clearer way for Student Aid administrators and finance users to understand application activity and award candidacy. Here, award candidacy refers to whether an applicant had moved into the award candidate stage for a fund.

The operational picture included aid years and periods, students, funds, application states, candidate and award states, and monetary amounts. The goal was to turn those related records into an analytical view that staff could use for day-to-day oversight.

The resulting Student Aid Progress dashboard in Ellucian Insights, Ellucian’s reporting and analytics environment, combines high-level metrics, filters, and student-level detail. Users can move from an overall view of activity to the records behind it.

Give Student Aid administrators and finance users a unified analytical view of application activity and award status that supports operational tracking.

Why Student Aid teams needed a clearer operational view

The institution’s Banner SaaS environment already held the Student Aid operational data behind the process. The reporting challenge was to organize that data around the questions administrative users actually needed to answer.

An application belongs to an aid year and period. A student may apply for a particular fund, progress through an online application, become a candidate for an award, and receive a corresponding status and amount. Those aspects of the process are represented through related Banner data structures rather than a single business-facing view.

The institution therefore needed both summary and detail. Staff needed to see application volume and monetary information by fund, but they also needed to narrow the view to a particular year, period, student, fund, or processing state and inspect the corresponding records.

Turn related Student Aid application and award records into one coherent management view without losing the different business states those records represent.

Building a Student Aid data model for operational reporting

ABCloudz built a custom analytical dataset that brings together the Student Aid information needed from Banner SaaS for the dashboard.

At the application level, the model captures the aid year and period, application completion state, locking information, and related comments. Candidate and award data adds the applicable fund, award status, outcome information, and amount. Person and reference data then provide the student identifiers, names, and business-readable descriptions needed for reporting.

This modeling layer is important because the dashboard is not simply a visualization of one source table. Relationships between Student Aid records have to be preserved, internal values have to be interpreted consistently, and the resulting fields have to support both detailed filtering and higher-level aggregation.

A useful operational dashboard depends on the state model behind it, not only on the visualization layer.

The resulting data flow keeps operational Student Aid records separate from the analytical model used for reporting. The reporting layer can then present fields and measures in terms that match how staff monitor the process.

See how the dataset connects application, award, student, and reference data

The custom dataset combines several distinct types of Banner data rather than treating Student Aid progress as a single record type.

Business concept Data object Role in the analytical model
Online application activity KVRFAPP Provides aid year and period, application completion state, locking information, and application comments
Award candidacy KVRIACA Provides candidate or award status and candidate amount
Student identity MST_PERSON Supplies the student ID and display name associated with the application
Aid fund description KVVFNDC Converts the applicable fund code into a readable fund description
Outcome description KVVCREA Supplies the outcome and longer outcome explanation used in the detailed view

At a functional level, the model starts with the application record and associates it with the corresponding person and award-candidacy information for the same Student Aid context. Reference data enriches coded values where a readable description is needed.

A simplified view of the relationship is:

Application context
→ identify the student and aid year/period
→ associate candidate and award information
→ enrich fund and outcome values
→ derive reporting statuses
→ expose the resulting fields through the custom dataset.

This relationship model allows the same analytical dataset to support both granular application records and aggregated measures used at the top of the dashboard.

See how raw Banner states become reporting-friendly application and award statuses

Some of the most important dashboard fields are derived from operational indicators rather than presented as raw codes.

For application progress, the custom logic maps the application completion indicator to business-readable states:

Operational value Dashboard status
C Complete
P In Progress

Award candidacy is normalized separately:

Candidate status value Dashboard status
1 Awarded
2 Not Awarded
3 In Progress
No candidate status value Candidate

The same principle applies to reference data. For example, the aid fund code is mapped to its description so users see a recognizable fund name instead of an internal identifier.

The logic can be represented as simplified pseudocode:



application_status =

    if completion_indicator == "C":

        "Complete"

    else if completion_indicator == "P":

        "In Progress"



award_status =

    if candidate_status == "1":

        "Awarded"

    else if candidate_status == "2":

        "Not Awarded"

    else if candidate_status == "3":

        "In Progress"

    else if candidate_status is null:

        "Candidate"

This normalization does more than improve labels. It creates consistent business states that can be displayed, filtered, and aggregated across the dashboard.

Turning the data model into an interactive operational dashboard

The analytical model powers a dashboard that combines summary information with detailed operational data.

At the top level, users can see the total number of applications, the monetary total associated with awards, and a breakdown by aid fund. Filters let them narrow the view by Aid Year, Aid Period, Student, Aid Fund, Application Status, and Award Status.

What should a user be able to learn before opening another report or inspecting an individual Banner record?

The detailed view answers that question within the same dashboard. Users can see the student and fund context alongside application and award status, outcome information, award amount, lock state, and award comments.

The design gives users an immediate summary view along with enough detail to investigate the applications and awards contributing to it.

How the dashboard supports day-to-day Student Aid oversight

The completed dashboard gives Student Aid and finance users one place to review application and award information.

Users can begin with overall activity, identify how records are distributed across funds, and then narrow the view by year, period, student, fund, or processing state. The custom data model also translates much of the underlying Banner complexity into business-facing fields and statuses, so the dashboard reflects the administrative process instead of mirroring the database structure.

Dashboard access is limited to the relevant Student Aid and finance users through role- or individual-level permissions.

Student Aid staff can move from a summary view to individual application and award details without leaving the dashboard.

Frequently asked questions

What Student Aid information can the dashboard bring together?

The dashboard combines application activity, aid year and period, student and fund context, application and award statuses, outcome information, monetary amounts, and other operational details needed to understand Student Aid progress.

Does the dashboard replace Ellucian Banner Student Aid?

No. Ellucian Banner SaaS remains the operational system for the underlying Student Aid process. The dashboard provides an analytical view of that data for administrative and finance users.

Why was a custom dataset needed instead of a single Banner report source?

The required business view spans related application, candidate and award, person, and reference data. The custom dataset brings those elements together, applies the necessary relationships and transformations, and exposes them in a structure suitable for filtering, aggregation, and detailed reporting.

Can users filter the dashboard by student, fund, year, or status?

Yes. The implemented dashboard supports filtering by Aid Year, Aid Period, Student, Aid Fund, Application Status, and Award Status, allowing users to progressively narrow the operational view.

How are Banner codes and statuses made understandable to business users?

The analytical model maps relevant operational indicators to reporting-friendly states such as Complete, In Progress, Candidate, Awarded, and Not Awarded, while reference data provides readable descriptions for values such as aid funds.

Can the same approach be used for other Ellucian reporting needs?

The same general pattern can support other reporting scenarios where a useful business view depends on combining multiple Banner data areas. The specific relationships, transformations, measures, and user experience still need to be designed around the business process being analyzed.

Need a clearer operational view of your Banner SaaS data?

If your teams have the Banner SaaS data they need but lack a clear analytical view for managing an important process, ABCloudz can help design the underlying data model and turn it into a practical reporting solution.

Contact ABCloudz to discuss your Ellucian reporting or modernization challenge and the next step.

Ready to start the conversation?