What Is a Reporting Window?

A reporting window is the from-and-to date range a report runs over, chosen before the report opens and adjustable while it is open. It is the first filter applied and the one that most often explains an empty grid, and it works alongside the fact that reports here query fresh every time rather than serving anything cached.

This entry defines the reporting window and shows how it reads inside EDGEBIC by User Solutions. For the wider index of terms, see the manufacturing glossary; for the reports it governs, see EDGEBIC reports explained; and for the built-in column reference beside it, see what is a column glossary in reporting.

How It Works

Reports fall into two shapes. Some describe a period, such as what each work center produced per day, or every reschedule that happened. Others describe the current state, such as which jobs are late right now. The first shape needs a window; the second does not.

For the windowed reports, choosing the range happens before anything loads. A date-range dialog asks you to pick a from date and a to date, and only then does the report open and query. Once it is open, most reports also carry inline filters, often including their own date pickers plus an optional job or work-center narrowing, so you can adjust and reload without starting over.

The second half of the model is that every report is point-in-time. It queries the database fresh when it opens and again on every reload, and nothing is cached between opens. No background process refreshes anything. What you read is what was true at the moment you asked.

That has a consequence worth internalizing. Two people opening the same report with the same window a few minutes apart can see different numbers, and neither is looking at stale data. Something changed in between, which is what a live plant does. If you need a figure that will hold still, export the grid, because the export is a captured artifact while the report is a live question.

Defaults are set per report to suit its most common use, and each report tile states its own default range in its small print. Many operational reports default forward from today, since their usual job is to say what is coming.

A Concrete Example

A supervisor wants the dispatch queue for the next fortnight. They open the dispatch report, whose default range is today through fourteen days out, which is exactly right, and click load. Every operation whose planned window overlaps those two weeks appears, grouped by station and ordered by planned start.

The same supervisor then wants to review how the previous month went. They open the daily production report, and this time the default range is not what they want, so they set the from and to dates to cover the month and click OK. The report opens on the period they asked for.

A third attempt goes wrong. They open an actuals-based report for a period last spring and get the message that there is no data in this window. Nothing is broken. That period predates the plant logging actuals at all, so there is genuinely nothing to report. Widening the range would not help; the data does not exist.

A fourth report, job progress, has no date dialog at all. It is a snapshot of every job as things stand, so a window would be meaningless. The absence of the dialog is the signal.

How EDGEBIC Uses It

In EDGEBIC, date-ranged reports show a select-date-range dialog first, asking you to choose the reporting window with a from and a to before confirming. The report then opens in the shared report shell and loads automatically, with a busy indicator while it queries.

Every report queries fresh with no caching, which is what makes the point-in-time description accurate rather than aspirational. Refining an inline filter and reloading runs the queries again from the database.

An empty result reports itself as no data in this window, and that wording is deliberate. It is a statement about your filters, not a failure. The three things to check are whether the range overlaps the period you care about, whether a job or work-center filter is narrower than you meant, and whether the underlying data exists at all, since actuals-based reports are empty by definition until hours are being logged.

Each report tile advertises its own default range and filter behavior in its small print, so you can tell before opening whether the defaults suit you.

Every report in the shell also offers export to Excel and to PDF, which is how you turn a live window into a fixed record. When a column in the result is unclear, the column details button explains it with a definition, a formula, a unit, and worked example values.

For a windowed report whose column needs the same treatment, see what is a blocker hint on a late job. For the captured artifact an export produces, see what is a grid export snapshot, and for the always-on view that complements reports, see what is a KPI tile.