Infor SyteLine3 min readNetray Engineering TeamUpdated March 4, 2025

Live Dashboards over SyteLine, Without the Six-Month BI Project

The dashboard most SyteLine sites actually run on is an Excel file someone refreshes every morning. Not because anyone chose that architecture, but because the alternative was a BI program: warehouse, ETL, modeling, licenses, months. There is a middle path, curated dashboards that read the live database directly through a semantic layer, and it covers the daily-operations use case that BI projects are overkill for.

What Daily Dashboards Actually Need to Cover

The daily questions are stable across manufacturers: what is in the order book, what is late, how do AR and AP stand, where is inventory unhealthy, what is running on the floor, what is shipping, what failed quality. SyteRay's shipped set maps onto exactly that: Sales Overview, an Open Orders Board, AR/Collections, AP/Payables, Inventory Health, Item Watch, Production/Jobs, Purchasing, Shipping, and Quality, plus three cross-module views, an Executive Pulse of headline KPIs, My Day, and Site Comparison. Thirteen curated views, designed around the questions rather than around what was easy to render.

The Properties That Make Dashboards Trustworthy

Three properties separate working dashboards from wall decoration. Freshness with honesty: render live on open, with a visible as-of timestamp, so nobody wonders whether they are looking at yesterday. Consistency by construction: dashboards must read the same definitions as every other surface, SyteRay's tiles read the same SyteRay_ semantic views its chat answers use, so the numbers cannot disagree. And workability: click-to-sort tables, chart/table toggles, CSV export, and clean printing, because dashboards feed meetings, and a number you cannot take with you is a number that gets retyped wrong.

Live render on open with an as-of stamp and refresh control.
Same semantic views as chat and reports: one set of definitions everywhere.
KPI tiles, sortable tables, bar/line charts, and multi-site comparison.
CSV export and print-ready layout on every view.

Dashboards as Starting Points, Not Endpoints

A dashboard's job is to surface the anomaly; the next step is always why. In a conventional stack that means switching tools. When dashboards live beside a conversational layer over the same data, the follow-up happens in place: ask about the spiking tile and drill down with evidence attached. The curated set is also defined as data rather than code, so adding a site-specific view is configuration, not a development cycle.

Frequently Asked Questions

Can I have SyteLine dashboards without building a data warehouse?

Yes, for operational KPIs. Curated views reading the live database through a semantic layer cover daily-operations dashboards with fresher data than a warehouse. Warehouses remain the right tool for deep historical analytics and multi-system consolidation.

What dashboards does SyteRay include out of the box?

Thirteen curated views: Sales Overview, Open Orders Board, AR/Collections, AP/Payables, Inventory Health, Item Watch, Production/Jobs, Purchasing, Shipping, Quality, Executive Pulse, My Day, and Site Comparison, each with KPI tiles, sortable tables, charts, CSV export, and print.

How do I make sure dashboard numbers match report numbers?

Make them read the same definitions. Encode business concepts once, as semantic views in the database, and point dashboards, reports, and queries at those views. SyteRay enforces this by construction: its dashboards and chat answers read identical views.

Key Takeaways

1What Daily Dashboards Actually Need to Cover: The daily questions are stable across manufacturers: what is in the order book, what is late, how do AR and AP stand, where is inventory unhealthy, what is running on the floor, what is shipping, what failed quality. SyteRay's shipped set maps onto exactly that: Sales Overview, an Open Orders Board, AR/Collections, AP/Payables, Inventory Health, Item Watch, Production/Jobs, Purchasing, Shipping, and Quality, plus three cross-module views, an Executive Pulse of headline KPIs, My Day, and Site Comparison.
2The Properties That Make Dashboards Trustworthy: Three properties separate working dashboards from wall decoration. Freshness with honesty: render live on open, with a visible as-of timestamp, so nobody wonders whether they are looking at yesterday.
3Dashboards as Starting Points, Not Endpoints: A dashboard's job is to surface the anomaly; the next step is always why. In a conventional stack that means switching tools.