--- title: "What’s New in Tracking 3.0" id: "en:tracking:ROOT:whats-new.adoc" site: en component: tracking module: ROOT version: 3.0 lang: en url: "https://help.rtlscloud.io/en/tracking/3.0/whats-new.html" source_repo: "https://github.com/iot-invent/xCloud.git@3.0.x" source_path: "tracking/docs/en/modules/ROOT/pages/whats-new.adoc" --- # What’s New in Tracking 3.0 This page summarises what changes for you in Tracking 3.0. The complete list of all changes is in the [release notes](release-notes.md). > **NOTE:** Version 3.0 is still under development. The information on this page may still change before release. ## Several use cases on one installation A space can now hold the business data of one use case alone — assets, tracks, routes, rules — and obtain its locations, devices and position events from an **infrastructure space**. A hall fitted out once therefore serves several use cases, say returnable-packaging tracking and tool management, which stay separate from one another. What you see of it: in an application space the full location tree of the infrastructure appears in the navigation and on the map, although the space itself owns no locations — read-only there. And infrastructure spaces are no longer offered in Tracking; switching application selects a use case running on them instead. > **NOTE:** If a tag is assigned to an asset in two application spaces, two separate tracks are created — the same tag can legitimately matter to two use cases. Per-tag figures therefore cannot be added up across application spaces. See [Space type and infrastructure space](../../accounts/3.0/spaces.md#space-type). ## Four new reports from data you already have No additional collection is needed for these four analyses: - **Silent assets** – how many assets have not reported for how long. The only one of the four that also covers assets without a route. - **Locations by asset stock** – how many assets are standing where right now, per location and broken down by asset type. A click on a bar lists them. - **Location dwell times** – how long the assets stand at each location, with minimum, median, mean and maximum. - **Movement matrix** – between which locations the assets move, how often, and how long a transport takes. The last three are computed from route data: assets without a route are not included, and each of these reports says so. See [Reports](reports.md). ## Two new cockpit tiles "Assets out of contact" shows how long the assets have been silent; "Top locations by asset count" shows where most assets are standing right now. See [Cockpit](cockpit.md). ## Maps rebuilt Every map view – assets, events and tracks – now runs on a newly built map component. Operation is essentially unchanged, though presentation and behaviour may differ in places. Affected views include the [location view](locations.md) and the [cockpit](cockpit.md). ## Floor plans on the world map If a location has a calibrated floor plan, it is shown on the world map – correctly placed and rotated according to its stored calibration. A calibrated plan is required; maps in a coordinate system other than Web Mercator are unaffected. See [Locations](locations.md). ## Reports and cockpit noticeably faster Reports, cockpit and key figures are now computed in the database instead of loading every record and evaluating it in the browser. The larger the number of assets and events, the more noticeable the difference. Concerns [reports](reports.md) and the [cockpit](cockpit.md). ## Trace delays down to the individual track Delays are grouped by number of days – for example "exactly 3 days delay" or "more than 5 days delay". From a group you can open the list of the individual tracks it is made up of. See [Reports](reports.md). ## Clearer asset pins on the map Assets at the same position are merged into a single pin instead of stacking invisibly on top of each other. Panning and zooming reloads only the part of the map that is actually visible. See [Locations](locations.md).