How Your Machines Get Into Multiviz

Customer Onboarding

One of the most important steps in using Multiviz effectively is getting your machines and sensor data into the system. This is something we take care of for you as part of the onboarding process when we start our partnership.

That said, if you're curious about how it works behind the scenes, or if you need to prepare anything on your end, this page explains the key steps and useful details to help you follow along.

Let’s get started.

How Multiviz Connects to Your Data

Multiviz connects to your existing sensor infrastructure through two primary methods, each tailored to different industrial setups and sensor brands. Both approaches follow a standardized integration workflow to ensure seamless data flow from your sensors to actionable insights.

Connection Methods Overview

MQTT Protocol (Preferred Method)

Best for: Real-time monitoring with wireless sensor networks

• Advantages: Lightweight, real-time data streaming, ideal for industrial IoT environments
• Typical use case: New installations or systems that support MQTT publishing

API Integration

Best for: Existing sensor systems with established data management platforms

• Advantages: Leverages existing infrastructure, works with proprietary sensor management systems
• Typical use case: Legacy systems or sensor brands with dedicated management platforms

MQTT Integration Workflow

Typical setup for wireless sensors:

• Sensors connect to a wireless gateway
• The gateway pushes data to an MQTT broker (cloud or on-premises)
• Multiviz connects to the broker and ingests the data in real-time
• You view insights and alerts in your dashboard

Prerequisites

• Sensor brand identification
• Tenant ID and Tenant Token (provided by Viking Analytics)
• Decision on customer or sub-customer structure

Integration Steps

1. Customer Setup initiated by Viking Analytics
   • Create customer or sub-customer in Multiviz using credentials
2. Integration Configuration
   • Add new integration for your specific sensor brand
   • Multiviz generates unique MQTT credentials (Username, Password, and topic

1. Gateway Configuration
   • Configure your gateway(s) using the Multiviz-generated credentials
   • Initiate measurement collection on connected sensors
2. Data Verification
   • Verify data reception in Multiviz

API Integration Workflow

For sensor systems with existing data management platforms, Multiviz integrates directly through REST APIs. The specific requirements vary by sensor brand:

General Requirements

• Customer name and organizational structure
• Gateway location information for timezone configuration
• API endpoint URLs and authentication credentials
• Optional: exclusion lists for specific data points or equipment

Brand-Specific Integration

For detailed integration requirements specific to each sensor brand, please visit our comprehensive integration documentation at How-to’s.

Security Note

Authentication credentials are used solely to generate secure API keys for ongoing data access. Original login credentials are not stored or used for regular operations.

Which Method Should You Choose?

Choose MQTT if:

• You're setting up new sensor infrastructure
• You need real-time data streaming
• Your sensors support MQTT protocol
• You want the fastest, most efficient data transfer

Choose API Integration if:

• You have existing sensor management systems
• Your sensors are from supported brands (RONDS, TWave, etc.)
• You prefer to leverage existing infrastructure
• You need to integrate with legacy systems

For Local Environment Deployments:If your data resides in a local, on-premises environment with specific network restrictions or security requirements, please contact our onboarding team at Viking Analytics. We'll work with you to determine the best integration approach tailored to your infrastructure and security needs.

Both methods provide the same rich dashboard experience with real-time insights, alerts, and analytics capabilities.

What We Need From You

To get started, we need a few key details:

• Sensor brand
• (e.g. CTC, I-care, SPM, Brüel & Kjær — [link to supported list])
• Sensor type
• Wireless, wired, handheld, or other?
• Data access method
• MQTT (preferred), API, file uploads, database connections?
• Data encoding
• Is the data encoded? Do you have a decoder or documentation?

There’s no long and tedious forms: we’ll review this together in a kickoff meeting or via email.

Timelines and setup

Once we have your information, the process can take 1–2 weeks, based on both teams’ availability. This includes:

• Understanding data structure
• Extracting asset hierarchy
• Decoding formats (if needed)
• Developing, testing, and deploying the integration

When your dashboard is ready, we’ll schedule a walkthrough and give you full access.

Note: New integrations for local environment deployments can take slightly longer.

Who You’ll Work With

We’ll guide you throughout the process, but we’ll also need a technical contact on your side to help with:

• Data format or decoder info
• Preferred asset hierarchy
• API/MQTT credentials
• VPN access or firewall filtering

Your onboarding team:

• Sergio — sergio.mdcb@vikinganalytics.se
• Kaveh — kaveh.toyser@vikinganalytics.se

✅ Ready to Go

Once you’re live, you’ll have:

• A customized dashboard
• Alerts and modes enabled
• The ability to track, assess, and collaborate on machine health

We’re here to support you as you get started — just reach out if anything needs adjusting.