WEBVTT

1
00:00:00.250 --> 00:00:04.539
Let me show you how Hive Node
connects a real casino.

2
00:00:15.262 --> 00:00:17.983
Let’s start on the casino floor.

3
00:00:17.983 --> 00:00:23.878
A player wants continuity, a technician
needs the right job, and a manager

4
00:00:23.878 --> 00:00:29.320
needs a clear picture. We’ll follow
those people through the same connected

5
00:00:29.320 --> 00:00:30.226
operating environment.

6
00:00:38.264 --> 00:00:42.644
A casino is a physical operation. Machines,
people, money

7
00:00:42.904 --> 00:00:47.204
and decisions must stay connected. Hive
Node brings them into one operating

8
00:00:47.244 --> 00:00:50.424
environment, with John T eight hundred
supporting the work.

9
00:00:50.864 --> 00:00:54.944
This is a concept demonstration using
fictional data: a view of the

10
00:00:54.984 --> 00:00:58.364
platform's intended capabilities and the
workflows behind them.

11
00:01:08.116 --> 00:01:10.315
This cabinet has just arrived.

12
00:01:10.315 --> 00:01:16.034
Before it becomes available, Owen checks
the inventory and Alex pairs its node.

13
00:01:16.034 --> 00:01:22.192
Watch them prove the installation, then hand
the evidence to the manager for release.

14
00:01:31.198 --> 00:01:35.398
Start with a machine. Owen imports its
inventory record, resolves

15
00:01:35.418 --> 00:01:39.978
duplicates and places it on the floor. Alex
pairs the embedded S M I

16
00:01:39.998 --> 00:01:44.158
B with the correct cabinet. Capabilities
remain restricted until commissioning

17
00:01:44.258 --> 00:01:48.758
tests and approval are complete. The
operator can then see the installation,

18
00:01:49.058 --> 00:01:51.018
its health and its full history.

19
00:02:00.762 --> 00:02:04.538
Maya wants to leave her
seat for a few minutes.

20
00:02:04.538 --> 00:02:09.068
She’ll move the controls to her
phone, continue from the restaurant, and

21
00:02:09.068 --> 00:02:13.976
return. Watch for the confirmation that
tells her which device currently has control.

22
00:02:23.804 --> 00:02:28.124
Maya is playing machine S L forty two. She
wants to leave her

23
00:02:28.184 --> 00:02:32.664
seat briefly. On her phone, she requests
control of the same physical

24
00:02:32.744 --> 00:02:37.264
machine. Hive Node finishes the current
operation and confirms an exclusive

25
00:02:37.304 --> 00:02:41.524
handover. Maya can continue from the
lounge, then return control to the

26
00:02:41.564 --> 00:02:42.764
cabinet when she comes back.

27
00:02:52.491 --> 00:02:54.591
Now Maya is at home.

28
00:02:54.591 --> 00:03:00.052
She chooses an available machine on
the real casino floor and completes the

29
00:03:00.052 --> 00:03:05.512
access checks. We’ll keep the cabinet
and her device together in view, so

30
00:03:05.512 --> 00:03:07.612
the physical connection is clear.

31
00:03:15.533 --> 00:03:20.093
At home, an eligible verified member can
select an available physical

32
00:03:20.193 --> 00:03:24.473
casino machine. Location and account checks
come before access.

33
00:03:25.073 --> 00:03:29.213
A single control grant protects the
session. The cabinet remains the source of

34
00:03:29.253 --> 00:03:33.273
accepted actions and outcomes. If
communication fails,

35
00:03:33.693 --> 00:03:37.253
uncertain operations are recovered before
the player can send a replacement

36
00:03:37.313 --> 00:03:37.813
request.

37
00:03:47.512 --> 00:03:51.104
Sometimes she wants a
break from play altogether.

38
00:03:51.104 --> 00:03:56.942
Maya can reserve the machine, see the
included time, and decide whether extra

39
00:03:56.942 --> 00:03:59.637
time is worth the stated price.

40
00:03:59.637 --> 00:04:03.678
The countdown and her confirmation
make the choice clear.

41
00:04:10.594 --> 00:04:13.414
Sometimes Maya simply wants to hold her
machine.

42
00:04:14.214 --> 00:04:18.754
An example policy includes five minutes,
with an optional ten minute extension

43
00:04:18.794 --> 00:04:22.434
for two dollars. She sees the price and
confirms it herself.

44
00:04:22.974 --> 00:04:27.174
No automatic renewal. The reservation
countdown, charge and venue

45
00:04:27.214 --> 00:04:31.414
record stay linked. A machine fault
triggers the defined unused time

46
00:04:31.454 --> 00:04:32.354
refund process.

47
00:04:42.117 --> 00:04:47.374
Let’s walk with Alex. His phone shows
what needs attention today, and John

48
00:04:47.374 --> 00:04:52.631
suggests the next stop. At the
machine, Alex confirms he is in the

49
00:04:52.631 --> 00:04:55.462
right place before asking
for service access.

50
00:05:05.139 --> 00:05:07.999
Alex starts his shift with a prioritized
work list.

51
00:05:08.819 --> 00:05:12.839
John recommends a route using the fault,
the technician's qualifications and

52
00:05:12.879 --> 00:05:16.999
available parts. At the destination, Alex
scans the machine's

53
00:05:17.039 --> 00:05:21.639
dynamic code with his assigned phone.
Identity, proximity and

54
00:05:21.739 --> 00:05:24.859
permission are checked before service
access can be granted.

55
00:05:25.279 --> 00:05:27.299
A scan alone never unlocks a cabinet.

56
00:05:37.221 --> 00:05:39.437
Arriving is only the beginning.

57
00:05:39.437 --> 00:05:43.869
Alex needs a confirmed service
state before opening the cabinet.

58
00:05:43.869 --> 00:05:49.631
We’ll watch the repair, record what
changed, and follow the tests and signoff

59
00:05:49.631 --> 00:05:52.734
that return this machine to the floor.

60
00:06:00.283 --> 00:06:04.543
Service begins only after active play and
unresolved obligations are

61
00:06:04.583 --> 00:06:09.063
safely handled. Alex follows diagnostics,
records the repair and

62
00:06:09.123 --> 00:06:13.203
runs the required tests. The manager
reviews the evidence where approval is

63
00:06:13.243 --> 00:06:17.803
required. The machine becomes available
again only after acknowledged release.

64
00:06:18.543 --> 00:06:21.463
Every step stays attached to the
equipment's maintenance history.

65
00:06:31.200 --> 00:06:33.932
The same approach helps everyone on shift.

66
00:06:33.932 --> 00:06:39.005
Alex checks in with his own phone,
Nina reviews a staffing request, and

67
00:06:39.005 --> 00:06:41.346
Daniel hands over a cash drawer.

68
00:06:41.346 --> 00:06:44.858
Each person can see the
action they own next.

69
00:06:54.302 --> 00:06:57.462
Staff check in with their own devices and
location evidence.

70
00:06:57.862 --> 00:07:02.342
They see shifts, request leave, arrange
coverage and hand over tasks.

71
00:07:03.182 --> 00:07:06.102
Managers approve changes against the
current staffing plan.

72
00:07:06.482 --> 00:07:10.902
Cashiers count drawers, verify payouts and
record custody

73
00:07:10.942 --> 00:07:15.462
transfers. Financial exceptions become
visible work items with an

74
00:07:15.562 --> 00:07:17.642
owner and a path to resolution.

75
00:07:27.346 --> 00:07:31.551
Nina is designing a jackpot
experience for the floor.

76
00:07:31.551 --> 00:07:37.157
She chooses its funding and presentation,
reviews the rules, and tests the

77
00:07:37.157 --> 00:07:42.296
numbers. Then we’ll follow the award,
while keeping promotional rewards and

78
00:07:42.296 --> 00:07:44.165
player balances clearly distinguished.

79
00:07:50.328 --> 00:07:54.848
The jackpot builder connects funding
sources, eligibility, mathematics

80
00:07:54.988 --> 00:07:59.248
and presentation. Teams simulate the rules,
approve a version

81
00:07:59.628 --> 00:08:04.168
and activate it deliberately. Awards create
traceable obligations and payout

82
00:08:04.208 --> 00:08:08.448
records. Promotions, loyalty and
hospitality share the player

83
00:08:08.488 --> 00:08:11.188
experience while keeping their balance
rules distinct.

84
00:08:11.588 --> 00:08:15.888
Personal awards follow governed eligibility
and do not change the base game's

85
00:08:15.948 --> 00:08:16.428
outcomes.

86
00:08:26.242 --> 00:08:31.275
At the sportsbook, Liam is watching
the feed and the venue’s exposure.

87
00:08:31.275 --> 00:08:35.469
We’ll follow one player’s quote through
acceptance and settlement, including

88
00:08:35.469 --> 00:08:40.501
the moment a changing event means
the team must stop new bets.

89
00:08:49.244 --> 00:08:53.404
The sportsbook uses external odds within an
internally controlled operation.

90
00:08:54.284 --> 00:08:57.724
Liam monitors feed freshness, exposure and
event state.

91
00:08:58.744 --> 00:09:03.324
Players accept a defined quote; stale or
suspended markets stop new

92
00:09:03.384 --> 00:09:07.884
acceptance. Results, cash out and retail
tickets follow explicit

93
00:09:07.944 --> 00:09:12.184
validation. Corrections preserve the
original history, so

94
00:09:12.244 --> 00:09:14.524
teams can explain what happened and why.

95
00:09:24.305 --> 00:09:29.426
In the studio, a team is turning
an original idea into a member

96
00:09:29.426 --> 00:09:33.759
experience. We’ll see how the brief,
artwork and development evidence stay

97
00:09:33.759 --> 00:09:38.486
together, and how the reviewed version
reaches the right catalogue and channel.

98
00:09:47.307 --> 00:09:51.847
Game Studio carries an idea through a
structured brief, mathematics, development,

99
00:09:52.087 --> 00:09:56.607
review and controlled release. Media and
evidence remain attached to

100
00:09:56.647 --> 00:10:00.827
the right version. Operators can shape
branded member experiences and catalogue

101
00:10:00.867 --> 00:10:05.167
availability. A change is released with
evidence and a recovery plan,

102
00:10:05.867 --> 00:10:07.427
not just a new visual design.

103
00:10:17.159 --> 00:10:22.562
Back in the control room, John
has a recommendation for Nina.

104
00:10:22.562 --> 00:10:28.455
She checks the evidence, approves a
specific action and follows its result.

105
00:10:28.455 --> 00:10:33.367
The same connected records help the
operator understand performance, ownership

106
00:10:33.367 --> 00:10:34.840
and future changes.

107
00:10:40.181 --> 00:10:43.961
Across the platform, John T eight hundred
assembles permitted evidence,

108
00:10:44.361 --> 00:10:47.801
explains uncertainty and prepares
structured proposals.

109
00:10:48.601 --> 00:10:51.261
Authorized people and policies govern
execution.

110
00:10:51.721 --> 00:10:56.241
Outcomes return to the shared action inbox,
with ownership, escalation

111
00:10:56.541 --> 00:11:01.021
and audit history. Hive Node connects the
casino floor to the decisions

112
00:11:01.061 --> 00:11:05.621
that keep it operating. Explore every
capability in the complete workflow

113
00:11:05.721 --> 00:11:06.021
guide.

114
00:11:15.865 --> 00:11:18.925
Explore every workflow in the complete guide and

115
00:11:19.045 --> 00:11:20.125
interactive demo.