Getting started

How TraX works

1. An installer physically mounts the sensor on a wheel end, and configures it using the TraX mobile app.
2. The sensor is then onboarded (added) to SKFs and the partner's platforms through integrations.
3. When the vehicle has been in motion (and some other criteria are met), the sensor broadcasts sensor data. 
4. The partner captures and persists the sensor data, and then analyzes and presents it in UI. The sensor data is shared with SKF.

Integrating the TraX sensor into your platform

Learn about TraX

• Learn about sensor backplate options, and how to mount and commission sensors in the  Commissioning sensors article.
• Understand the big picture by reviewing Concepts, and how the Process integration spans between clouds, vehicles, and devices.
• Familiarize yourself with the Architecture, and the Integration architecture, and ensure that you can meet the Partner integration requirements.
• How the sensor works is described in detail in the SKF TraX Technical Specification Connected version document.
• We also provide an introduction to the the latest major firmware release in the Introduction to firmware BSS10 article.

Build your own TraX client

Preparation

• We provide development and production Integration environments. Your client needs to be onboarded by SKF to each environment before you can connect.
• During onboarding, we set up various Accounts and resources required for integration.

Build your TraX client

• Learn How to connect to queues and How to connect to the web API.
• Get server URLs from the Integration environments
• Next up is to implement Process integration that enables efficient operation. The process has been broken down into several Integrations. We provide detailed step-by-step guidance for quickly getting the implementation work done.
• Set up alarms and design the UI in your platform based on guidance in the Acting on sensor data.

Deploy to the development environment

• Once you´re ready for integration tests, deploy your TraX client to the dev environment.
• Use the QA protocol to ensure your TraX client meets the acceptance criteria.

Deploy to the production environment

• Next up is to deploy the solution to the production environment.
• Use the User acceptance test protocol to perform a final validation that the technical integration and users are ready to go live.

Getting ready for go-live

• Integrate SKF and your support teams to ensure the support model is well understood and connected.
• Training sessions.

Go live 🚩

• Onboard new fleets, and installers. SKF can assist in the first customer cases.
• Support TraX users.
• To scale the deployment of TraX sensors, you are empowered to manage users through self-service to support the growth demand for installers.

Final notes

The "SKF TraX sensor" is henceforth referred to as "the sensor" in this documentation.

The CAPITALIZED words throughout these guidelines have a special meaning:

The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC2119.

Refer to RFC2119 for details.