Access Management
Last updated
Last updated
This guide provides a comprehensive overview of the Condense OEM Tool, designed to simplify managing your devices and vehicles.
Visit the OEM tool web page and provide your username and password to log in. If you don't have an account, contact Zeliot for creation.
If you manage accounts for both standard fitment and aftermarket products, the OEM tool allows you to create and manage accounts for both.
The OEM Tool offers three methods for adding new devices:
Manual: Add individual devices one at a time.
Bulk Upload: Upload a file containing details for multiple devices using a downloadable sample template.
API: API integration for automated device addition.
Similar to devices, you can manage SIMs using three methods:
Manual: Add individual SIM cards one at a time.
Bulk Upload: Upload a file containing details for multiple SIMs using a downloadable sample template.
API: API Integration for automated SIM addition
Once uploaded, the OEM Tool displays real-time SIM status information, including:
TSP1 (Telecom Service Provider 1)
TSP2 (Telecom Service Provider 2)
Activation Start Date
Activation End Date
This section focuses on Vehicle Identification Number (VIN) and device (IMEI) mapping. There are three ways to complete VIN-IMEI mapping:
Individual Mapping: Manually map a VIN to an IMEI for a single vehicle.
Bulk Upload: Upload a file containing VIN-IMEI pairings for multiple vehicles using a downloadable sample template.
API Integration: API Integration for automated VIN-IMEI mapping.
The VIN Journey tab also displays the following information:
Device Status (Real-Time)
End-of-Line Testing (EOLT) details for each VIN-IMEI mapping
After mapping is complete, the OEM Tool performs an EOLT to confirm device connectivity.
If the device communicates with the server after EOLT, the "Telematics Check" option becomes available.
This feature offers a real-time status report on the device, allowing you to verify its functionality. Clicking "Telematics Check" displays detailed information about the device
User can now access EOLT timestamp as well as latest packet status with Device and Server Timestamp
This feature enables OEM to make changes in the existing mapping of VIN-IMEI under scenarios when IMEI needs change. Users can manually edit VIN IMEI mapping in OEM tool through this functionality.
The KYC Journey tab within the Condense OEM Tool offers functionalities for managing KYC details and activation through integration with your SIM provider. This tab provides insights into the KYC processing lifecycle, including adding KYC information and managing approvals/rejections.
The OEM Tool provides two methods for adding KYC information for each VIN:
1. Manual KYC:
Users can enter mandatory KYC details for a specific VIN through a designated form within the Manual KYC option. Once the user fills in and submits the details, a new KYC record is created for that VIN.
API Integration:
The OEM Tool offers API integration capabilities to connect with client's system.
Through this integration, KYC details can be automatically added to the KYC processing tab upon creation.
Regardless of the method used to add KYC details (manual or API), all KYC records appear in the KYC Details tab. This tab allows the client's service team to manually review and approve or reject each KYC record.
Approvals and rejections are timestamped for reference and record-keeping purposes.
- Real-Time Status Updates:
The KYC Processing tab within the OEM Tool displays the current status of each KYC record in real-time. This status reflects the approval/rejection decision made by the service team in the KYC Details tab.
- Integration with Client System (API):
When using API integration for KYC processing, the OEM Tool communicates with your client's system in both directions: KYC record updates from your client's system are reflected in the KYC processing tab within the OEM Tool.
Approval/rejection decisions made by the service team in the KYC Details tab are communicated back to your client's system via the API, updating the KYC status within their system.
The OEM Tool provides a dedicated KYC Logs page to track all KYC-related activity. KYC Logs page provides an audit trail of all KYC activity, including re-attempts, updates, and the previous state of KYC details for each VIN.
KYC logs are created in two scenarios:
Re-attempts After Submission/Rejection: Whenever a user attempts to modify KYC details for a VIN after an initial submission (successful or rejected), a new KYC log is generated. This allows for tracking changes made to KYC information.
KYC Details Update: A KYC log is created whenever the KYC Details associated with a specific VIN are updated. This includes both:
Updating existing details for a previously submitted KYC record.
Adding new KYC details for a VIN that didn't have any KYC information before
Each KYC log captures the following information:
Previous KYC Details: The details associated with the VIN before the update.
Updated KYC Details: The new details entered after the update.
Timestamp: The date and time the update occurred.
The KYC Logs page displays these logs, allowing you to review the history of changes made to KYC information for each VIN.
The latest KYC details for a VIN are also reflected on the VIN Journey page within the OEM Tool. This ensures you have easy access to the most current KYC information associated with each vehicle.
The VIN Logs feature within OEM Tool provides a centralized location to view the history of VIN-IMEI mappings. location data, connectivity details, and EOLT status.
The VIN Logs feature displays a table containing a comprehensive record of all VIN-IMEI mappings.
Clicking on a specific VIN number in the table opens a pop-up window showing detailed logs for that VIN. This pop-up window includes the following information:
Serial Number: Unique identifier for the specific log entry.
Sequence: Order in which the mapping details were created.
VIN: Vehicle Identification Number.
IMEI: International Mobile Equipment Identity of the connected device.
Vehicle Type: Type of vehicle associated with the VIN (obtained from mapping details).
Vehicle Model: Model of the vehicle associated with the VIN (obtained from mapping details).
Fuel Type: Type of fuel used by the vehicle (obtained from mapping details).
Status: Current status of the VI N-IMEI mapping (e.g., "VIN-IMEI Mapped").
Created On: Date and time the log entry was created.
Latitude & Longitude: Geographic coordinates of the device (if available).
Plus Code: Location reference code for the device (if available).
Device Timestamp: Date and time of the packet received from the device.
Server Timestamp: Date and time of the packet received by the server.
Packet Type: Type of data packet received from the device (e.g., tracking data).
The latest VIN-IMEI mapping details for a specific VIN are also reflected on the VIN Journey page within the OEM Tool. This ensures you have easy access to the most current information about each connected vehicle.
Whenever the IMEI associated with a VIN is updated, a new log entry is created in the VIN-IMEI logs page.
This log entry captures
This guide provides an overview of Zeliot's E-FOTA system, which enables remote firmware updates for ECUs in vehicles.
Zeliot FOTA system consists of majorly 4 components:
Campaign Manager: A FOTA Campaign Manager is an application responsible for communication with a backend server and updating campaign management for all the other ECUs in the vehicle. Typically runs on FOTA gateway.
FOTA server: responsible for the management of vehicle software release, and optionally to customise updates for every vehicle client based on OEM policies.
Condense: responsible for all device related communication like push command for flash initiation, package download, etc. It will act as an interface between device and OTA.
TCU Flash Manager: application that performs final updating of firmware for ECUs during run-time.
Type
ECU Flashing, Read Error codes, Erase Error Codes, Read Error codes with Snapshots, Read Data Identifiers, Update Data Identifiers
ECU Flash refers to Program Flash and data flash sometimes, Reading ECU common error codes, erasing these error codes, read and update data identifiers includes sensor readings
File Name
Name
Delphi, Bosch, Bosch_IFX, Cummins, Albonair
Group
Engine, ACU
Engine Control Unit, etc
File Type
Base, Calibration, Base + Calibration
Uploaded By
Zeliot Admin, Client
Uploaded Date
DD-MM-YYYY HHMMSS
Actions
DD-MM-YYYY HHMMSS
To create a campaign, please find the process flow below:
User can create package (inclusive of file name, ECU name, ECU Group, Schedule Type and Group) for target ECU using the tab “Upload New File” as shown in below fig
Upload New file will open a dialog box as depicted in below fig. Here user will have provision to enter below fields:
Schedule Type
ECU Flashing, Read Error codes, Erase Error Codes, Read Error codes with Snapshots, Read Data Identifiers, Update Data Identifiers
ECU Group
Engine, ACU
ECU Name
Delphi, Bosch, Bosch_IFX, Cummins, Albonair
File Type
Base, Calibration, Base + Calibration
Upload File
Bin File
Cancel/Upload File
User can either cancel or upload the file. If the file is uploaded successfully, a record is created in the Files Tab.
Then the user needs to go to “Campaign” tab to create the campaign wrt package created.
A campaign allows you to deploy software updates to groups of devices. When you create a campaign, you need to specify the criteria of campaign type, ECU group, ECU name, file type and expiry days.
To create a campaign, user needs to click on “New Campaign” tab in Campaigns page. A dialog box will open up where the user needs to input the details as shown in below fig
Select Campaign Type
Dropdown option of VIN and IMEI
User can either select it individually or in bulk
Select ECU Group
BCU, ACU, Cluster, Engine, Powertrain
User can select the ECU group from the drop-down menu
Select ECU Name
Delphi, Bosch, Bosch_IFX, Cummins, Albonair
User can enter the ECU Name
Select File Type
Base, Calibration, Base+Calibration
User to select type of file is whether Base or calibration or both.
Select File
Bin File
User to upload the file and select bin.
Type Expiry Number
Expiry in days
User to provide the expiry date or validity of the campaign
Once user provides the details to create campaign, an OTP will be sent to email (as shown in below fig). The user needs to provide the OTP as confirmation for the package created/campaign created to be downloaded.
For OTP, there are multiple statuses associated with package. These statuses will reflect in “Campaigns” tab as shown in fig – New Campaign.
No OTP
Not Validated
NA
Pending for Approval
Incorrect OTP
Validated
Approved
Pending for Approval
Correct OTP
Validated
Approved
In Progress
Correct OTP and File Download and ECU flashing for all VINs
Validated
Approved
Completed
Manually Rejected
Validated
Approved
Rejected
Once the OTP is validated in OTA, it will act as a trigger for Condense to request for package download to TCU Flash Manager. TCU Flash manager acknowledges the command received by Condense and requests FOTA server to download the package (this package is stored in S3 bucket). TCU Flash Manager downloads the package and saves it. Simultaneously, the status is updated as Completed.
As a subset of Creating Campaign Successfully, File Download and ECU flashing are 2 integral points. For File Download, below are the possible cases and flow:
Campaign - Rejected
NA
NA
NA
Inactive
Inactive
Campaign - Pending for Approval
NA
NA
NA
Active
PENDING
Campaign - In Progress
File Download option in Green - Not Triggered
Trigger yet to be received for package download command
Trigger yet to be received to download package
Active
PENDING
Campaign - In Progress
File Download option in Green - Triggered
Trigger received for package download command
Trigger received to download package
Active
FILE_DWNLD_REQ UESTED
Campaign - In Progress
File Download option in Green - Triggered
OTP validation success, Trigger received for package download command
Trigger received to download package, downloading in progress
Active
DEVICE_FILE_DO WNLOAD
Campaign - Completed
File Download option greyed out
OTP validation success, Trigger received for package download command
Package downloaded successfully
Active
FILE_DWLD_COM PLETED
Campaign - Completed
File Download option greyed out
OTP validation success, Trigger received for package download command
Package unavailable, deleted, corrupt, directory does not exist, pre-requisites not fulfilled, etc
Active
FILE_DWLD_FAILE D
For ECU Flashing, below are the possible cases and flow:
Inactive
NA
Inactive/Active
NA
NA
Inactive
PENDING
NA
Active
NA
NA
PENDING
FILE_DWNLD_REQ UESTED
NA
Active
Trigger received for package download command
Trigger received to download package
FILE_DWNLD_REQ UESTED
DEVICE_FILE_DO WNLOAD
NA
Active
Trigger received for package download command
Trigger received to download package, downloading in progress
DEVICE_FILE_DO WNLOAD
FILE_DWLD_COM PLETED
Enabled, not triggered
Active
Trigger received for package download command
Package downloaded successfully
FILE_DWLD_COM PLETED
FILE_DWLD_COM PLETED
Enabled, Triggered
Active
Latest Vehicle status check with pre- requisites satisfied
Package downloaded successfully
FLASH_REQUEST ED
FLASH_REQUEST ED
Disabled
Active
Latest Vehicle status check with pre- requisites satisfied
NA
FLASH_COMPLET ED
FLASH_REQUEST ED
Disabled
Active
Latest Vehicle status check with pre- requisites satisfied
NA
FLASH_FAILED
(security key check failed, etc)
Once the Campaign Status is “Completed”, File Download Status is “FILE_DWLD_COMPLETED” and ECU Flash (for all VINs) is FLASH Completed with date and timestamp and progress as 100%, it reflects that Campaign is successful.
