During our recent webinar, we demonstrated several new Argos X capabilities designed to make institutional data easier to explore, understand, and share.

Afterward, Jonathan sat down with Andy for a quick conversation about what these tools mean for institutions and how they fit into the continued modernization of Argos.

Everyone in higher education wants to be “data driven.” Haven’t we already solved that problem?

Andy: Part of it.

Institutions have gotten very good at producing reports. They’ve spent years building DataBlocks, dashboards, definitions, permissions, and governance around their data.

That foundation is incredibly valuable. But having a lot of reports doesn’t automatically create a data culture.

Jonathan: What’s missing?

Andy: The ability to keep going.

Someone opens an enrollment report, finds the number they need, and immediately asks another question. Why did it change? Which programs were affected? Was it new students or returning students? Did the same thing happen last year?

The report did its job. The problem is that the next question often means another request, another export, or another trip back to the analyst.

So this isn’t about replacing reports?

Andy: Not at all.

If you’re printing a class roster or producing a financial statement, you may not be looking to have a conversation. You just want the report.

But that report might spark another question. We can’t always predict what the question will be or which report will trigger it.

What we’re doing in Argos X is giving users more ways to continue from that first answer.

Jonathan: Walk me through those.

Andy: Right now there are three major features.

Explore Data lets someone work directly with the report results. They can filter, sort, group, and focus on the records that matter without needing a new report.

Data Agent lets them ask questions about the data in plain language.

Dashboard Designer lets them turn trusted DataBlocks and report queries into visual, interactive experiences they can publish and share, without needing to know SQL.

Sometimes you need the report. Sometimes you need to dig into the records. Sometimes you need to ask a completely new question. Those experiences should connect.

What does Dashboard Designer add?

Andy: It gives institutions a modern way to present and explore their data without rebuilding the reporting logic underneath it.

A creator can take an existing DataBlock or report query and, entirely in the browser, transform it into a modern operational or executive dashboard using scorecards, charts, maps, interactive tables, information cards, filters, notes, and other visual elements.

Jonathan: So they aren’t starting from scratch?

Andy: Exactly.

The DataBlocks, definitions, permissions, and report logic are already there. Dashboard Designer makes them easier to use and communicate.

A user can start with a high-level metric, click into a chart, filter a table, and see the records behind the number.

That is much more useful than simply putting a prettier chart on top of a report.

Can a dashboard use more than one source?

Andy: Yes.

You could place student success data and financial data on the same dashboard, for example.

The sources are not blended into a new data model. Each dashboard object still uses its assigned source. But the user can see related information together instead of bouncing between multiple reports and systems.

Does that create more work for the reporting team?

Andy: It should create less.

Dashboard Designer access is separate from DataBlock Designer access. You can let someone build a dashboard from an approved DataBlock without letting them change the DataBlock itself.

That matters because reporting teams are already overloaded. They shouldn’t have to personally build every chart and dashboard someone on campus needs.

Where does Data Agent fit?

Andy: Dashboard Designer helps someone see what is happening. Data Agent helps them investigate it.

A user can ask: “How have applications by major changed over time?” “Which student groups are behaving differently from the overall trend?” “What anomalies should I look into?”

Data Agent translates that question into SQL, analyzes the available data, and returns an understandable answer.

Then the user can keep asking follow-up questions without starting over.

Jonathan: Which sounds useful, but institutions are understandably cautious about AI.

Andy: They should be.

The question shouldn’t be, “Does this use AI?” It should be, “What data is the AI using, who can access it, and can I understand how it reached the answer?”

Data Agent works with governed Argos DataBlocks and report queries. It honors existing MAPS permissions, so users can only access data they are already authorized to see.

It also shows the SQL, filters, logic, and source information behind the answer.

We’re not asking people to blindly trust the result because AI produced it. We’re giving them a way to review how the answer was calculated.

What if someone asks a vague question?

Andy: Then Data Agent should ask for clarification.

If someone asks, “Which students are at risk?” the system shouldn’t invent a definition of “at risk.”

Does that mean low GPA? Poor attendance? Financial holds? Low LMS activity?

If the question or data doesn’t provide enough context, the responsible answer is to ask the user what they mean.

What is the difference between Data Agent Core and Advanced?

Andy: Core lets users ask questions about the report query connected to a DataBlock.

They can summarize a dataset, compare populations, identify trends, find anomalies, and ask follow-up questions.

Advanced expands that beyond a single report query. It can work across dashboards and multiple DataBlocks.

Jonathan: So someone could ask a question that touches recruiting, enrollment, and financial aid?

Andy: Right.

The user doesn’t need to know which DataBlock contains every piece of the answer. Data Agent can identify the relevant information, perform the analysis, and generate a supporting visualization.

Does that make analysts less important?

Andy: I think it makes them more valuable.

Analysts spend a lot of time answering variations of questions they’ve already answered.

“Can you filter it differently?” “Can I see last year?” “What about first-generation students?”

Those are good questions. But they don’t always require another full reporting cycle.

If users can explore approved data on their own, IT gets time back and analysts get more time for the work that really needs their expertise: governance, complex analysis, institutional definitions, predictive work, and strategy.

How is this different from buying another analytics or AI platform?

Andy: We’re not asking institutions to rebuild everything.

The DataBlocks, reporting logic, permissions, and institutional knowledge they’ve created over the years become the foundation for these new experiences.

Dashboard Designer makes that foundation more visual. Data Agent makes it conversational. MAPS continues to govern access.

That’s how we think about Argos modernization: protect what already works, then make it more useful.

What is the shift you want institutions to see?

Andy: Reporting tells people what happened.

A data culture helps them understand why it happened, decide what to do next, and share what they learned.

We’re not moving beyond reporting by leaving it behind. We’re building on it.

Dashboard Designer and Data Agent Q&A

Is Dashboard Designer included with Argos?

Yes. Dashboard Designer is included for existing Argos customers. Data Agent Core and Advanced are separately licensed.

What is required to enable Dashboard Designer?

At the time of the webinar, institutions need MAPS 6.14.3 and an Evisions Cloud Link connection for each MAPS instance where it would be enabled.

Are dashboards built entirely in the browser?

Yes. Dashboard Designs are created in Argos X through the browser using report queries from existing DataBlocks.

Can existing classic dashboards be converted automatically?

Not currently. Institutions can reuse the existing DataBlock and report query, but the dashboard itself must be recreated.

Are Argos and MAPS permissions maintained?

Yes. Dashboard Designer and Data Agent honor the permissions associated with the source DataBlocks, folders, fields, and users.

How can users verify a Data Agent answer?

Users can review the SQL, filters, logic, and source information used to produce the response.

How can an institution learn more?

Existing Argos customers can contact support@evisions.com to discuss enabling Dashboard Designer or sales@evisions.com to schedule a Data Agent demonstration.