Brand 360 Overview

Brand 360 is a data-sharing model that facilitates data analytics service for franchise business models related to the hospitality sector. The key stakeholders in this model, brands and partners, are bound by a service-level agreement (SLA) that sets the benchmark for the service quality and operations management of the network that is expected to be delivered by the partners.

Brand 360 provides an isolated environment for the brands to view network data of multiple partners collected from network infrastructures deployed across different properties. Brand 360 enables the brands to set SLA thresholds for certain metrics and helps them gain quick insight into the network health and service quality of the properties managed by their partners.

Brand: A brand is a parent company or organization that monitors the overall performance of its franchise partners or sub branches. Brands can reflect the image, values, and recognition associated with an organization or its products or services, regardless of whether they involve franchise networks.
Partner: A partner is a subsidiary or franchise of the parent company or organization. A partner is an entity that collaborates, exchanges data, or provides access to its resources or services.

RUCKUS AI provides several valuable resources for the brands:

Dashboard: Provides exclusive access to partner network data that summarizes their SLA compliance level against key metrics.
Data Studio: Extends intuitive reporting functionality support.
Labels: Helps to organize and monitor partners and properties.

Brand Invitation

A user can be invited to have the role of a Brand to access and monitor partner's network data. The user who sends the brand invitation is considered the partner and the user who accepts the invitation is considered the brand. When the brand invitation is sent to a user who does not belong to the partner's organization, the partner is explicitly granting the Brand role access to its RUCKUS AI service account to the invitee. In addition, depending on the assigned role, the invitee gains access to the partner's account with Prime Administrator or Administrator privileges. If the Prime Administrator role is granted, the brand will also be able to invite other users into the partner's account. If this is not desired, make sure to assign the Administrator role.

The following prerequisites apply to sending and accepting the brand invitation:

Only the users who have Prime Administrator privileges can send a brand invitation.
The invitees must have a valid email address registered with RUCKUS Support and have access to their own RUCKUS AI service account.
The invitee cannot have preexisting access to the RUCKUS AI service account of the user sending the invitation. The invitee's user account must be removed before sending the brand invitation.

Complete the following steps to invite a user as a brand.

On the navigation bar, click Administration > Account Management > Users. The Users page is displayed.
Click Invite Brand. The Invite Brand dialog box is displayed.
In the Search field, enter an email ID, and click Find. After RUCKUS AI completes validating the email ID, the Resource Group and Role fields are displayed.
Note: The user must have a valid email ID that is registered with RUCKUS Support. Else, the third-party account will be rendered invalid.
Invite Brand Dialog Box
In the Resource Group field, select a resource group from the drop-down list to assign a resource group to which the invitee will have access at the brand level. For more information, refer to Resource Groups.
In the Role field, select one of the following roles to assign to the user from the Role list:
- Admin, Brand: The invitee will have the Brand role at the barnd level and the Admin role at the partner level.
- Network Admin, Brand: The invitee will have the Brand role at the barnd level and the Network Admin role at the partner level.
Select the I understand and agree check box and click Invite.
Information relevant to the invitee is displayed on the Users page. The invitee may accept or reject the invitation; the status of which is also displayed on this page as Accepted, Rejected, or Pending.
An automated email notification with all the invitation details and an access link to RUCKUS AI is sent to the specified email address of the invitee. Simultaneously, the brand invitation details are displayed on the Accounts page of the invitee's RUCKUS AI service account.

Accepting the Brand Invitation

After receiving the brand invitation, the invitee must complete the following steps to accept the invitation.

The invitee logs in to their RUCKUS AI account.
On the Navigation bar, click Administration > Account Management > Users. The Users page is displayed.
Click User Icon > Accounts in the Header Panel to open the Accounts page. The Accounts page displays the brand invitation details.
Accounts Page: Brand Invitation Notification Details
Click Accept.
A rejected invitation is removed from the account immediately. After an invitation is accepted, a new toggle button is displayed which allows the invitee to switch between the Admin and Brand modes. For more information, refer to Brand 360 Dashboard.
Note: The toggle button is displayed only under the user's organization service account.
Admin and Brand Mode Toggle Button

Brand 360 Dashboard

The Brand 360 dashboard provides an overview of the associated partners and summarizes the data operations management and service quality data of the property managed by the partners. The dashboard provides a centralized monitoring window exclusively for the brand to track the aggregate network data of the partners and assess their performance against some key metrics and compliance with service-level agreements (SLAs).

The brand can view the dashboard in two different modes:

Brand: Allows a view of the partner's network data for the predefined metrics.
Admin: Allows a view of the brand's own RUCKUS AI service account.
Note: The terms brand and partner as used in this guide have different meanings in different contexts, and denote roles, modes, and view types at the User Admin level. The brand can customize the UI display names for these attributes in the My Profile settings page, where standard vocabulary that aligns with the company's common business glossary can be added. For more information, refer to Naming Convention.

The brand can switch between the Admin and Brand modes using the toggle button on the header panel. The brand can also access the RUCKUS AI service account of the partner by selecting the specific account from a list (which is available when the Admin mode is selected). At the partner level, the brand will have Prime Administrator or Administrator privileges depending on the assigned role. For more information about roles and resource groups assigned to the brand, refer to Brand Invitation.

The dashboard displays RUCKUS AI data for three key metrics: P1 Incidents, Guest Experience, and Brand SSID Compliance. These metrics measure the level of service that is expected to be delivered by the partner. The data on the dashboard is displayed based on the selection of date and time range filters. The top portion of the dashboard displays the following tiles:

P1 Incidents: Displays the total number of high-severity incidents that have occurred in the network across all the partners.
Guest Experience: Displays the average percentage for the "guest experience" -related metrics across all partners. The guest experience score is determined by calculating the average percentage of three metrics: Time to Connect, Connection Success, and Client Throughput.
Brand SSID Compliance: Displays the percentage of the network properties that conforms to the SSID compliance rules set in the My Profile settings.

All of the three metrics have the following common elements in their respective tiles:

Delta counter: Displays the difference in value compared to the previous time period indicating positive or negative change with respect to the metrics.
Time-series graph: Displays the value of respective metrics over time. Pausing the cursor over the time-series graph at a particular cursor displays the value at that time and date.
Selector arrow: The top three best performing and three underperforming partners or properties with respect to each metric are displayed. The selector arrow can be used to toggle the view to display the three best performers and the three underperformers. The selector arrow is available only if there are more than three partners or properties.

The lower portion of the dashboard displays the data of each partner and property in a table. The brand can customize the SLA threshold for the metrics according to requirements. Every time a new SLA threshold is set, the values displayed on the table change simultaneously as the metrics that meet the updated SLA are considered for RUCKUS AI. To customize the SLA, in the SLA panel, move the slider to adjust the threshold value of each metric and click Save.

Depending on the selected view type, the format in which the data is populated in the table also changes. The brand can choose between the following view types from the menu:

Partner: Displays the high-level data of each partner associated with the brand. You must expand each partner to view the details of each property.
Property: Displays the data of each partner at a granular level showing the data of each property.

Dashboard - View types — Brand 360 Dashboard View types

The dashboard table at the bottom displays more information about each brand, partner, and property.

Dashboard Table Information — Brand 360 Dashboard Table

The search field under each column head allows you to filter the data and narrow down the search results. Data that matches the search input is rendered in the table. The search field is case-sensitive.

Table 1. Brand 360 Dashboard Table Information
Header Field	Description	Additional Information
Partner	Displays the name of the account that is associated with the brand account as a partner.
Property	Displays the properties managed by the partners.	If the Partner view type is selected from the menu in the top-right of the dashboard, the total number of properties managed by each partner is displayed.
Label	Displays the color-coded labels attached to the partners and properties.	The color-coded labels help the brand to identify the properties managed by different partners spreading across different locations, sites, geographical regions, or networks. For more information, refer to Labels.
No. P1 Incidents	Displays the number of critical-severity incidents that have occurred in the network.	The following design elements indicate SLA compliance status: Value in a red-outlined cell: Indicates that some of the properties managed by the partner do not meet the SLA defined for the respective metrics. This status indication is available only at the partner level. Expand the partner to view the properties that do not meet the SLA. Value in a red- filled cell: Indicates that the property does not meet the SLA defined for the respective metrics.
Guest Experience	Displays the average percentage for the "guest experience"-related metrics for each partner and property.
Brand SSID Compliance	Displays the percentage of the network properties that conforms to the SSID compliance rules.

Naming Convention

Company standards may specify certain naming conventions that must be followed to enable enterprise-wide views of the performance and metrics related to partners and properties. These naming conventions help to maintain consistency and conduct faster analysis of enterprise data. The brand can modify the My Profile settings page to change the default naming convention. Enter the standard vocabulary that aligns with the company's common business glossary and click Save.

The naming convention changes are reflected on the dashboard.

Company standards may require specific naming conventions related to SSIDs too. According to the specified standards, the brand can set the regular expression to validate brand SSID compliance in the Compliance Rules section of the My Profile settings page. Choose the pattern and click Save.

Note: Regular expressions must be compatible with Java standards.