Please enable JavaScript.
Coggle requires JavaScript to display documents.
MAX ONE - Coggle Diagram
MAX ONE
Architecture
Site controller
Tony's diagram
3rd party connections to site controllers
Common edge platform
Venue
Terminal
Pre commitment - cashier component
Host
Billing
Monitoring
Jackpot
Multi Venue jackpot
Not sure people will use it
Is it similar to state wide links
Data lake / DWH
There is a huge gap here
We have to get the data in the right shape
Regulator will define what they want
We will have to provide the tooling to run on DWH
Regulator to define the fields and DWH sill be developed using that
APEX project - look for the diagram from Tony
Solution
Catalogue to be provided
Tier 1, Tier 2 and Tier 3
Business capability Matrix
Floor status management
How we support this
Wild cat - floor management
MAXsys 2 - Live view
Running the monitoring side of things
Not things like cash cleranace
What can be done and cannot be done to be marked here
This is In Venue side ?
Venue Operations management
For the Venue
API management
Cash and reconciliation
Cougar is rich in this area
Similar to TAS hopper reports
In Venue operations - This is for us
3rd piece to monitor 3rd party
Should we consider edge devices - Stef's point
Patron message display management
Vocuehers and prootions management
markd organge as we have to handle integrations
Approving tech and config management
jackpot management included
Does this include EGM limits
More discussions needed around the process
Cougar is pretty complex stuff
Beyond monioring system
Job management
request install and new config
Loyalty management
Refer boxes
Marketing management is huge
barrell draws here as well
earning and redeeming
Consider API side of things - Rae
Venue grouping should be considered here as well
Reporting
Regulatory Reporting
COre function
Other Reports
Regulatory approvals management
What is core vs rest
what data to be provided
to 3rd parties for the rest ( non core)
platform - will be MAX
But there will be misses obviously
Core
Foundation
Guidance on customisations
best practices on doing this
How to get the best out of micro site architecture
Current platforms
Cougar
we have to support the growth in QLD while building MAX ONE
MAXsys 1
Maxsys 2
MAX API is not an API rather it is a gateway
Only monitoring
LMO providing integrating capabilities
Very little up take due to technical limitations ??
Maxsys 2.1
QCOM is supported
Have asked about the QCOM3 on 23rd Sep
Just monitoring
QCOM 1.6
Doing minimum by June 2026
What is minimum
Still some specific stuff been done to facilitate this
Victoria is dependent on this work
EGM wont be available - there is a long tail
Manufactureres are not ready
Industry will take time to adopt
Bring controls that manufacturers wont be very excited about
Victoria
Rollout/ Implementation to be started - date ?
Is it QCOM3
More like QLD from opportunity
Our bidding is more of LMO capability
But can provide anciliary services
TITO
Cashless
Cardless
Card based gaming
Account based gaming
Have a chat with Nina and try to simplify the above list. VIC might not require all of them
Monitoring and Pre commitment
Two products?
Pre commitment
Knowing who plays
Player identity
Cross venue player capability
Within group identity
Across jurisdiction identity management
This is the biggest gap we have
Capabilities under this
Cardless
Account based gaming?
Victoria just needs identify player
Not the wallet side of things
Includes visitors which is called Casual
Should be possible to build integrated capabilities
Through APIs
Its in roadmap
Have to support competitor integrations
We have given capabilities
We have not shared how part
What it means
Suite of products - Tony
Core product and capability to integrate with 3rd parties
Refer to the chat
Placeholder MAX ONE
chat
discussion around 2:03 on 24th
Different tiers
Opportunity ahead
International market
Casinos - Australia
SAS protocol
Define customer groups and tackle this
QCOM 3
EGM availability
Industry will take time to adopt
This is a platform
software
Running games
Transfer meters via a component and provide to Cougar
Do not need a box
Mental model
Core vs context ( customer specific)
Platform thinking
Gradually replacing legacy components with consolidated services wrapping up old systems
Strangler Fig pattern
business capability model (Draft)
All the project level inputs
have been considered for this work
Product features
Core
Value added
ex: Loyalty
Exclusions/ assumptions
Not a single instance ?
This means multiple instances
Why did we fail
Project delivery mindset
Business priority changes
Near opportunities
Victoria
Single platform Discussions
The work Matt did to be presented
to Rob - Consolidation
Capability
Venue Grouping capability
Loyalty across on grouping
Venue group based reporting
Goals and guiding principles of Multi jurisdiction platform - Refer confluence page