This pages shows the steps needed to onboard an existing Radar customer into Nova.
Transition of Radar Reporting service to Nova Reporting
The data is the same for both Nova Reporting and Radar Reporting, both services can be used by the customer post successful transition. The purpose of the onboarding is to verify the Nova Reporting service is working prior to customer uptake of the Nova Reporting service.
If customer has Radar data collected and used for Radar it will be used for Nova too.
What’s preventing customers from using Nova?
- Licenses – the customer will need to be enabled with the correct Nova software licenses. – e.g. Reporting
- Roles – the customer will need to be enabled with the correct role – e.g Radar Classic
- This role is additional to roles like System Admin, or User Admin.
- Possibly other roles, if services like Adoption Accelerator are enabled as well.
- Service enablement for Nova reporting services – see below on Service Placement
Steps for ‘migration’ to Nova
- Add entry to conversion queue.
- Check tenant in TMS
-
if nothing showing in overview click on edit and ensure that both Parent organizations are selected
-
Ensure that tenant is connected, if not as customer to https://info.quadrotech-it.com/knowledge-base/tenant-not-connected/
-
- Check services and ensure they point in correct geo location (See later in this article)
In case they are not correct, post it in Teams and wait till it is fixed
Add subscription
You can copy the same dates as they are in FG. This can only by done by someone with TMS QT Admin role.
Customers should get Radar, Reporting, and Availability when they move from Radar to Nova.
Adoption and DPC needs to be mentioned in the migration request and this would require additional steps not covered here.
What to choose:
- Service: Reporting, Radar, Availability
- Feature: Core
- Start date: Will be prefilled
- End date: For now you can find this value in FG. Later Accounting Team will provide this information
- Cancelation: Do not need to set this
- Type: Paid
- Qty: 1
Let the customer know that all this is done.
Update Hubspot (see later)
Update the conversion queue information
Additional notes for Adoption Accelerator
If Adoption Accelerator needs to be added, just the subscription should be all that is needed.
What to choose:
- Service: Adoption
- Feature: Core
- Start date: Will be prefilled
- End date: For now you can find this value in FG. Later Accounting Team will provide this information
- Cancelation: Do not need to set this
- Type: Paid
- Qty: 1
Additional notes for DPC
The process to follow is shown below:
- Create ADO in Autopilot/Issues
- Fill all information in ADO – you can use template link to *ADO template for DPC request*
- Invitation to tenant for Martin Svancarek <martin.svancarek@quadrotech-it.com> from tenant where DPC should be deployed with roles System Administrator and Autopilot Classic
- Once DPC is onboarded remove Martin’s account
- Add DPC subscription
ADO template for DPC Request
Title: DPC Deployment for OrganizationToBeDeployed
Description:
Org ID: 2222–guid
Region: US
Name of tenant: OrganizationToBeDeployed
Number of users/mailboxes: Actual or best estimate on the number of users
Severity: Can be taken from the Support Ticket
Ticket ID: Ticket number from Kayako
Environment: Production
Additional notes
If the onboarding process was requested by a customer. Following the email communication plan in this OneNote.
Additional reporting SA could be added https://info.quadrotech-it.com/knowledge-base/change-the-service-account-password-in-tms/
After adding these services, Hubspot should be updated. (See below)
In case of any issues reach out to CET, or ask in Nova channel in Teams.
Updating Hubspot
When the customer is onboarded/transitioned to Nova we have some duty to update information in Hubspot. This means that Marketing will then be able to target Nova customers with correct materials. The steps to follow are:
Go to Hubspot
Change the Nova Status to On-boarded
Select the services which were enabled for the customer
Save the changes!
Service placement
For Nova Reporting to work successfully there are 3 services that must be provisioned. This can be checked in TMS>Services tab (visible for users with System Administrator role)
aggr.us.uapi.quadro.tech US uAPI – this will be US always even it is global service
reports.o365radar.eu EU Radar
eu.uapi.quadro.tech EU Radar uAPI
Location must be the same as physical location of Radar data (US,EU) and last two services must have the same location.
If all of these tests pass, then:
- Go to customers tenant in TMS
- Add trial license for Reporting, and add trial license for Availability
I have a suggestion/request!
Is there something you are looking for on these pages that doesn’t seem to be here?
Is there information and content that you would like to see on the Readiness pages?
Or perhaps you want to see a change to the layout, or there is something here that doesn’t seem to be in the right place?
Then please tell us about it in the box below!