Regulated Casino
Version evidence, surveillance coordination, TITO, and governed release windows.
Plan cabinet geometry, payment interfaces, software evidence, service access, and jurisdictional acceptance as one controlled deployment—not five disconnected purchases.

Cabinet and aisle geometry. Check footprint, door travel, ventilation, accessibility, and component-removal clearance against the actual plan.
Payment responsibility. Name the owner of bill-validator, TITO, cashless-wallet, reconciliation, and outage-recovery work.
Version control. Freeze game package, software hash, peripherals, and rollback media before acceptance testing.
Service limits. Separate remote triage from physical repair, restricted components, parts lead time, and site-access dependencies.
Floor measurement. Define coin-in, occupancy, actual hold, downtime, and sample windows before comparing a pilot.
Approval boundary. Laboratory evidence can support review; the local authority and operator license govern activation.
| Reference envelope | Use the selected model drawing; confirm width, depth, height, door travel, and required rear access. |
|---|---|
| Electrical scope | Confirm voltage, branch circuit, plug, power quality, and heat load by configuration. |
| Payments | Bill validator, TITO, approved cashless interface, accounting handoff, and failure-mode ownership. |
|---|---|
| Network | Managed segmentation, monitoring permissions, time synchronization, change window, and rollback path. |
| Evidence pack | Applicable GLI-19 test record, electrical evidence, version register, and jurisdiction-specific submissions. |
|---|---|
| Activation gate | Commissioning pass does not replace local authorization or operator licensing. |
Version evidence, surveillance coordination, TITO, and governed release windows.
Distributed service, depot stock, mixed connectivity, and technician authorization.
Compact zoning, acoustic control, guest escalation, and constrained service access.
Cross-property governance, wallet integration, asset reporting, and phased refreshes.
Match the report to cabinet, game version, peripherals, and intended jurisdiction. The standard is not a site license.
Confirm the applicable UL or market evidence against the exact model and power configuration.
Verify certificate entity, scope, issuing body, site, and validity instead of relying on a logo alone.
Bring the jurisdiction, candidate cabinet mix, floor plan, payment architecture, network owner, and planned commissioning window.