Business intelligence in a project
Record attendance, tickets, revenue, occupancy, production data, and reporting snapshots
The Business Intelligence project component collects data for analysis and reporting. It combines manual entries with the project's events, rooms, and properties. Visibility and editing depend on the project settings and the component permission. If you may only read, you see the notice Read-only view; Data quality with the missing items is only shown to people who may edit the component. The Export button only appears if you may edit the component and additionally have the permission Export BI data (module Business Intelligence).
Key figures and data quality
The key figure tiles summarise values such as attendance, sold tickets, revenue, and occupancy. Values that have not been recorded are shown as — rather than 0, so "not entered yet" and "actually zero" remain distinguishable. At the very top, Data quality shows how much of the information required for a reliable report is present. Under Still missing, each missing item is a button; a click jumps to the matching section.
A missing value is not automatically zero. If a figure genuinely does not apply, mark it Not relevant for this project so reports can distinguish a deliberate exclusion from an overlooked entry.
The component follows the principle "record first, then evaluate": you enter figures at the top, and key figures, comparisons and snapshots below evaluate them. The save feedback names the reason if a value was not accepted and highlights the field concerned.
Attendance, tickets, and revenue
The section Audience & revenue records four figures: Visitors, Sold tickets, Revenue and Costs. Costs are always entered as one total for the project. The other three can be entered in one of two input modes:
| Input mode | Use |
|---|---|
| Total | One figure for the whole production. |
| Per event | Relevant project events receive individual values and Artwork calculates totals. Required for period comparisons and the monthly trend in the BI dashboard. |
In per event mode a table of the project's events appears. By default it shows Audience events only — events whose event type carries the BI tag for performances; Show all events adds the rest. The table can be searched and sorted by room and event. Several selected rows can be filled with a common value; events in the future are marked as such. The total row shows the current state; occupancy is calculated from sold tickets and the effective room capacity.
Do not switch the input mode casually
Switching between total and per-event recording discards the figures of the other mode. Artwork asks for confirmation; export or note any values you still need first.
If attendance is missing, Artwork may provisionally estimate it from sold tickets and labels the figure as an estimate. With Break down by category you record the tickets per audience category (full, reduced, free); from these Artwork derives rates such as the paying rate. Adopt sum enters the sum of the paying categories as sold tickets.
For Revenue (input mode Total) and Costs, Artwork suggests a value from the budget where available: in the actual view the Revenue from Sage bookings or Costs from Sage bookings, in the plan view the Income side or Expense side of the project budget. Adopt value enters the suggestion; you can overwrite it at any time.
Recording plan values
Next to the title of the component you switch between Actual and Plan. In the plan view you record the expected visitors, tickets, revenue and costs; the actual figures stay untouched. When you open it for the first time, you choose the starting point:
| Choice | Effect |
|---|---|
| Start empty | Creates empty plan values |
| Copy structure from actuals | Takes over the input modes of the actual view, but no figures |
| Copy values from another project | Searches for a project and takes over its actual figures for visitors, sold tickets and revenue as plan totals, for example the predecessor production of a revival |
As soon as plan values and actual figures exist, the actual view shows the Plan vs. actual comparison with difference and Attainment. Production data, capacities, time efforts and custom fields are maintained only in the actual view; they apply to both.
Room capacity and occupancy
Artwork initially uses the room's Default capacity. Enter a Project-specific capacity if this production uses a different seating layout. The Effective capacity column shows which value is used. The table only lists rooms in which the project has events. Maintain capacity before judging occupancy; no reliable percentage can be calculated without it.
Production data
The standard production information records whether the project is a new, co-, or in-house production, whether it is a German premiere, and the premiere date. These fields can be exported across projects for statistics and funding reports.
Derived values and BI tags
Artwork calculates further values from the project, events, and BI entries. Configured BI tags can group event types for reporting without changing the event types shown in the calendar.
The key figures performances, event days and occupancy are only calculated if the respective BI tag is assigned to at least one event type. Which tag controls which key figure is set in the tag dialog under System → Events → BI tags with Controls key figure — exactly one tag controls "Performances" (also the capacity basis of the occupancy rate), one controls "Event days". Without the assignment, — is shown with a hint; there is no fallback to all events.
Correct the source event, capacity, or entry rather than trying to overwrite a derived value.
Effort ranges
Record a named effort in one of the ranges 0–10, 10–25, 25–50,
50–100, or 100+. The name should identify the area being assessed, such
as “production management” or “technical preparation”. The creator remains
visible on the entry.
The ranges are estimates in hours. They enter the effort score of the BI dashboard with fixed hour values: 5, 17.5, 37.5, 75 and 125 hours.
Snapshots
A snapshot (German label: Stichtag) preserves the project's current BI values under a name and date. Use it for planned, interim, and final reporting states.
Snapshots do not change with live project data. Deletion is permanent.
The Period comparison and the Attainment shown in the component refer to the live values instead. The period comparison contrasts two periods, optionally with Previous year or Previous period as the comparison; it only shows figures recorded per event, because totals cannot be assigned to a period. Attainment relates the actual figures to the plan values.
Custom fields and Excel export
Administrators can add organisation-specific text, number, selection, and other fields; in the component the section is called Custom fields. They can also contribute to the data-quality indicator.
Excel export
You open the BI export in the project's BI component or in the BI dashboard; it is the same dialog. It requires the permission Export BI data and covers all productions of the house, regardless of your project access. It can cover multiple projects and a date range; opened from the project, the range is prefilled with the project period.
Under Export structure you decide what the file contains: Project rows only, Event rows only or Projects and events (2 sheets). The events sheet always has the same columns; the column selection applies to the productions sheet. In addition, productions can be filtered by cost bearer and events by BI tags.
The column selection is grouped and searchable: select columns for master data, project period, capacity, attendance, tickets, revenue, occupancy, production details, BI tags, and custom fields. Save common column combinations as presets with unique names. While the Excel file is being created you see a waiting state with Cancel export. The data sheets are called Productions and Events; they have a frozen header row, autofilter and real date, currency and percentage values. The Info sheet is always included, even with only one data sheet, and states creation time, creator, period and its source, export structure, BI tag filter and the productions included. Export files stay available for 24 hours — only to the person who started the export; after that you have to create the export again. Before downloading, verify the date range, projects, and selected columns against the reporting state you intend to deliver.
Recommended workflow
- Complete the project's events and rooms.
- Verify capacities and add project-specific values where needed.
- Choose the total or per-event input mode for attendance, tickets, and revenue; record plan values where needed.
- Complete production data and custom fields.
- Resolve the data-quality notices.
- Create snapshots at important reporting dates.
- Generate the cross-project export only after these checks.
Last updated on