How MobileView RTLS Uses Data and API Integration for Actionable Insights

The value of a real time location system (RTLS) goes beyond active location tracking of people and assets. It lies in how location and status data can be used to trigger actions, support reporting, improve decision-making, and connect with wider business systems.

In the third part of our MobileView Q&A series, we spoke with Jon Miles, APAC Regional Team Leader about the data value behind MobileView, including alerts, audit logs, asset history, long-term data storage, integrations and API functionality. This Q&A introduces how our MobileView Enterprise RTLS Visibility Software can help organizations turn real time visibility into operational insight, with more detailed onshore and offshore use case deep dives to follow in future articles.

Q: How do alerts work? 

A: Alerts in MobileView can be automatically triggered by processing location and status data in real time, based on pre-set criteria such as movement, personnel activity, or time-based rules. Location data derived from wireless signals can be used to determine when certain conditions are met, with location accuracy influencing how reliably position-based alert conditions can be evaluated. When these conditions are met, the system then generates an alert that can be sent to phones, workstations or third-party systems, while also being logged for reporting and audit purposes.

Q: What types of alerts can MobileView generate? 

A: MobileView has a wide range of standard alerts and events. Some examples include:

  • Battery reports allow the system manager to monitor the battery condition of all RTLS tags. Additionally, the tag also notifies the user when a tag battery reaches the lower threshold and enters “reserve” capacity. It is also possible to charge the tag from flat for 20 minutes, and the tag will continue to operate for a shift before a full recharge is required.
  • The MobileView Solution also provides a quantity of different movement alarms and events that are provided as standard and can be manipulated to suit a specific client. This includes Geo Fencing of restricted areas, Dwell Alarms (if someone does not move), Tag not heard from (is generated when a tag message has not been received for a settable period of time). There are also a multitude of other conditions that can be set in the system and have their setting and operation modified to suit a specific site or condition.

    Q: Who receives these alerts? 

    A: Alerts generated through worker location tracking and personnel status monitoring can be directed to specific team members or departments depending on the type of event. For example, personnel location tracking can support emergency response by helping identify when a Man Down alert needs to be sent to the CCR (Central Control Room), ERT (Emergency Response Team) and medical teams. Similarly, an alert for someone remaining in a restricted or red zone for too long could be sent to the area supervisor and displayed on their device.

    Because MobileView is highly configurable, organizations can tailor alerts to match their safety procedures and operational workflows, supporting personal accountability, encouraging open communication between relevant teams, and helping personnel respond quickly and effectively.

    Q: How is asset history handled? 

    A:  Alongside real time location tracking, MobileView allows users to view historical movement trails for people and assets, helping organizations identify trends, support audits, maintain compliance, and improve operational decision-making.

    Q: Does MobileView keep a record of system activity? 

    A: Yes. The MobileView software system includes a comprehensive audit log that records every action taken within the system. This allows organizations to review who performed an action, what was done, and how events were responded to, providing a documented record of individual actions and supporting staff in demonstrating personal accountability.

    The audit log records not only user actions, but also automated system activity, ensuring that all events within the platform are fully logged.

    Q: How long is data stored in MobileView? 

    A: The standard database log period is typically 90 days, allowing organizations to review recent activity and operational events. However, MobileView can also be deployed with a data warehouse solution, enabling organizations to retain analytical and historical data for up to 10 years.

    Because MobileView is highly configurable, deployments can be tailored to meet each organization’s reporting, analytics and compliance requirements.

    Q: Does MobileView integrate with other systems? 

    A: Yes. MobileView supports integrations through optional gateway modules and external data sources, helping organizations connect RTLS technology with other operational systems and unify visibility across different data sources.

    Q: Can MobileView work with existing tracking technologies? 

    A: Yes. MobileView can integrate with other location technologies that may already be deployed on site. For example, if an organization already uses an asset tracking solution for equipment or a fleet management system for vehicles, this data can be integrated into MobileView via the ELE (Extronics Location Engine).

    Q: How does MobileView share data with other business systems? 

    A: MobileView provides API (Application Programming Interface) functionality, allowing data to be securely extracted or sent to other systems within the organization. For example, data entered into an Access Control System (ACS) can also be relevant to POB (Personnel on Board) or RTLS systems, supporting personnel accountability by ensuring organizations can maintain consistent personnel records across connected platforms. Using the API, personnel data can be automatically pushed or retrieved from the ACS into MobileView, helping streamline workflows and reduce duplicate data entry.

    Q: What are the operational benefits of system integration? 

    A: Integrating MobileView with existing systems can establish an automated workflow that reduces administrative workload and improves operational efficiency. For example, when personnel data is shared between the ACS and MobileView, security teams can provision both access cards and tracking tags more efficiently, saving time and ensuring data consistency across systems.

    Want to see how MobileView data and API integration could support your site? 

    MobileView Enterprise RTLS Visibility Software demonstrates how RTLS solutions can turn real-time location and status data into actionable insights. From alerts and audit logs to long-term data storage, integrations and API connectivity, MobileView supports faster decisions, improved visibility, and more efficient operations.

    Contact our team to find out more.

    About the Author
    JM Jon Miles
    Jon Miles
    Regional Team Leader - APAC

    Jon leads business development across Asia Pacific, expanding our presence in explosion-proof engineering and RTLS technologies. With deep experience deploying wireless and tracking solutions across high-risk industries, He works globally to deploy WIRELESS, RTLS/POB, and AUTOID systems.

     

    More Blogs

    EXgateTM or iWAP: Which Wireless Enclosure for Your Application

    EXgateTM or iWAP: Which Wireless Enclosure for Your Application

    Should you choose EXgateTM or iWAP for wireless equipment in a hazardous area?  The right choice depends on…

    Read More
    The Design Principles Behind the EXgateTM215 and EXgateTM360 Wireless Enclosures

    The Design Principles Behind the EXgateTM215 and EXgateTM360 Wireless Enclosures

    What makes the EXgateTM215 and EXgateTM360 different from a standard hazardous area enclosure?  The EXgateTM range is designed…

    Read More
    Selecting the Right iWAP for Hazardous Area Wireless

    Selecting the Right iWAP for Hazardous Area Wireless

    Which iWAP is right for my application?  Choosing the right iWAP starts with your hazardous area requirements, but…

    Read More