Current NetSuite reporting
Existing saved searches, result screenshots, criteria, formulas, exports, and roles the team already uses.
Question to scoreboard
Validate the NetSuite definition before the number goes on the screen.
Xillix Scoreboard projects move from one recurring question to approved reporting definitions, reconciled values, display-specific pages, and a maintained browser deployment.
The starting principle
A scoreboard is only as clear as its reporting definitions.
Fields and visuals come after the question, audience, formulas, filters, permissions, and scope are understood.
Project sequence
A seven-stage path from recurring question to shared screen.
The technical details vary by NetSuite account, but the source and validation responsibilities remain consistent.
Define the recurring question
Identify the audience, current checking process, intended display, and action the scoreboard should support.
Define the NetSuite reporting requirements
Inventory the current reports and define the information required for the agreed scoreboard scope.
Confirm formulas, filters, permissions, and scope
Document dates, locations, subsidiaries, statuses, exclusions, roles, and ownership.
Design for the intended audience
Create scoreboard pages with the right hierarchy and density for a TV, warehouse screen, workstation, tablet, or meeting room.
Reconcile the results against NetSuite
Compare representative scoreboard values with approved NetSuite results and review exceptions.
Deploy the browser display
Configure the supported or compatible display, data-as-of communication, and separate page-rotation timing.
Maintain the agreed configuration
Manage approved changes to reporting definitions, pages, audiences, and the NetSuite-to-screen setup.
Useful starting material
Bring the current checking process, not a polished specification.
The recurring question
What the team opens, refreshes, exports, or asks someone else to check.
Definitions and exceptions
The meaning of complete, open, late, aged, held, ready, location, period, and other local terms.
Audience and display
Who needs the answer, where they will see it, and how far they will be from the screen.
Standard timing
Updated NetSuite data and rotating pages use separate schedules.
NetSuite data refresh
Standard scoreboard configurations are designed to receive updated NetSuite results approximately every 15-20 minutes. Exact completion time may vary slightly because of NetSuite processing, reporting complexity, and the agreed implementation.
Scoreboard page rotation
Pages may rotate every 20-60 seconds or at another configured interval. Rotation uses the latest available NetSuite snapshot and does not trigger a new data collection.
Shared responsibilities
Customer approval stays part of the project.
Xillix
- Translate the agreed question into reporting definitions and scoreboard pages
- Document displayed definitions, formulas, filters, and source mappings
- Build and test the scoped browser display
- Surface constraints, assumptions, and reconciliation results
Customer team
- Approve NetSuite access, reporting definitions, fields, roles, locations, and audiences
- Confirm operating definitions and reporting ownership
- Review calculations and usefulness with responsible stakeholders
- Protect credentials and own operational action based on the view
Bring the question your team keeps checking.
A current report is helpful but not required. Xillix can use the recurring question to define the reporting and scoreboard work that a first scope needs.
Start a Scoreboard