A new industrial UI is here! All future feature releases will require the new UI. Please read below to understand what to expect and how to upgrade before August 25th. Future feature releases will require the UI upgrade.
A banner in your dashboard will launch on August 10th, where you will then have the option to migrate to the new UI.
We’re excited to offer all industrial customers a new way to visualize their operations. With the UI upgrade, you'll be able to create an asset-centric view of your entire organization that mirrors your physical operations. Please read the blog to learn more about this exciting change. All new Industrial features are built for customers using the upgraded UI. You can move the new UI yourself by clicking “Enable” in the banner at the top of your Samsara cloud dashboard, or we’ll automatically migrate you on August 25th at 8 PM PT.
Note: If you are also a Samsara Fleet customer, the new UI will not impact your Fleet experience!
Watch the overview of the changes to expect here. Then, read the rest of this article.
How to tell if you are on the old UI:
Below is what the left sidebar looks like in the old UI of a Samsara Industrial organization:
The new UI will have a left sidebar and navigation like this:
How to Migrate to Asset-Based Navigation:
- First, notify your organization’s Samsara cloud users that the UI change is happening and point them to this article outlining what the changes look like
- Please make the change during an off-hour. We don't expect any issues if another user logs in during the migration, but they may run into UI changes they aren’t expecting if they are logged in when the change is made
- Log in to your cloud.samsara.com account
- Select “Enable” when you see this banner at the top of your Samsara Cloud
- Once you hit “Enable”, the time it will take to migrate depends on the amount of machines you have configured in Samsara. It should take anywhere from 1 second (if you have no machines) to 1 minute.
If you don’t migrate yourself by August 25th, we will automatically migrate you at 8 PM PT that day.
If you don’t have any machines in your organization, you can stop reading.
If you have machines, please keep reading. All machines will be migrated to assets and there are corresponding changes you need to know.
Assets are Replacing Machines
- Machine name will match asset name
- OLD VIEW: What machines looked like in the Samsara cloud
- NEW VIEW: What assets look like in the Samsara cloud
- You can now “nest” your assets for better organization. For example, by Region → Site Location → Well Pad → Asset
To organize your assets, see below for how to do this:
- We no longer explicitly associate a gateway to a particular asset. Instead, data inputs and outputs (or I/O) will be associated with specific assets. Assets are a collection of IO and a lot of customers associate all IO from one gateway to a single asset.
- You can edit a gateway’s name to include the asset name for easier tracking.
Data Inputs Changes
- Data inputs will be copied over to the new asset
- Your sensor data (HMs, EMs) will now show up as data inputs
- Thermistor Temperature
- Vibration Root Mean Square Velocity (Max)
- For each HM sensor, these data inputs will be created (since machines don’t have data inputs for machine temperature and vibration data):
- Sensor properties remain the same
- To visualize the vibration (FFT) waterfall graphs, you will need to add FFT data inputs
- Watch the video here to learn how to re-add and visualize your FFT data from HM11 sensors. Write in 1800 for RPM.
- Navigate to the asset on the left sidebar. Click on the “I/O” tab at the top. You can now find the FFT vibration data input there.
Data Input “Type” Changes
- Data input types are now called “Data Groups” in the data input configuration
- You cannot have multiple data inputs with the same data group within one asset. If you get an “Data Validation Error,” this means you have the same data group name for more than one data input in one asset. Learn how to quickly resolve this issue by following the steps here.
- Watch this video to learn how to find the vibration time series graphs in the new UI
- This changed location to reduces human error - it's much easier for you now to manage both the vibration analysis and alert thresholds all in one place (before, the thresholds set for machines for the time series graph were separate from the actual alerts, which is prone to human error if you forgot to update both places
Vibration Time-Series in the Old UI
Vibration Time-Series in the New UI
Class, Type, and Custom Field Changes
- OLD VIEW: Machines looked like this
- NEW VIEW: Machine class, type, and custom fields will move to asset custom fields. You can use this area to add optional asset information, notes, or custom metadata
- Existing machine information in Optional Machine Information will be migrated over in the "Custom Fields" section of the Details tab of the new Asset
- From Machine "Optional Machine Information"
- To Assets "Custom Field" section
- If there is an existing address (or lat/long) on the machine, it will move to the asset. Otherwise, the asset’s location will be determined by the gateway location (if there is more than one gateway on a machine, it will default to the last-created gateway).
- To view the location, navigate to the asset on the left sidebar and click the “Details” tab at the top
- All machine alert information is transferred to asset alerts (notifications, alert contacts, warning, and error thresholds)
- An alert is created for each vibration (HM) sensor based on these current thresholds: On, Warning, Error. To change these, go to Alert Settings
- Tags are copied over from the machine to the Asset
- Custom machine reports are migrated to asset reports. Navigate to reports on the left sidebar, then select “Assets”
- Data input reports are migrated as well. Navigate to reports on the left sidebar, then select “Data Inputs”
- You can now schedule reports! Go to the “Scheduled” tab
Manual Entry Changes
- OLD VIEW: Manual Entry in machines looked like this:
- NEW VIEW: Manual Entry in assets looks like this:
- If a data input is shared by multiple Machines (2+ IGs/Machine):
- These data inputs are duplicated when transferring to Assets. The cloned inputs will point towards the same data source, and be named “<Data Input Name> Copy”
- To find the duplicated data inputs, go to Settings in the bottom left corner (gear icon)
- Go to “Data Inputs” on the left sidebar
- Search “copy”
- To change the Data Input name and configuration, click on the copied data input and edit the configuration
- If you use our API:
- Read about our API here.
- If you are using machines in the API - https://api.samsara.com/v1/machines/history
- The old endpoints will still work since we’re not deleting the machines during the migration (machines moving to assets), but the machines will no longer be supported since there will be no way to view/edit those machines as they will now will be assets
If you have any concerns about the migration, please reach out to firstname.lastname@example.org. We’re excited to enable this new experience for you and look forward to your feedback!