The Data Sheet describes the categories of Data configured in, or processed/generated by the DPS and made available, as well as the access methods, channels (e.g., UI/API/export), formats, frequencies, retention, and the indication of availability for portability and/or switching.
Data category | Description / Examples | Source | Availability | Format | Frequency | Retention | Portability & Switching |
|---|---|---|---|---|---|---|---|
Raw Data (telemetry) | Values published by the Objects through the IoT Connector (MQTT, HTTP) or third-party connectors and stored by the DPS as time series | Connected Product | UI: widgets, charts and pages of the DPS Frontend. API: historical values (optionally aggregated), last values, BLOB content. Export: Data Export from the Data Management page or via API. | API: JSON Export: ZIP archive with one CSV file per Product. | UI/API: from receipt of the data (near/real-time update in widgets). Export: on demand, asynchronous processing. | 12 months (default), plus any additional time provided by the Object’s service level. | Yes, within the retention period. |
Computed Data | Values of metrics of type DERIVED, COUNTER computed by the DPS from other Metric Data (e.g. unit conversions, cumulative counters, differences between readings). | DPS Backend | Same as for Raw Data | Same as for Raw Data | Same as for Raw Data, but computed on receipt of the source data and according to the periodic computation. | Same as for Raw Data | Yes, within the retention period. |
Insight Data | Insights computed on Products and Locations by means of built-in algorithms (e.g. Uptime, Downtime, Proper Functioning Index, Connection Index, Energy, Working Time) or custom algorithms. | DPS Backend | Same as for Raw Data | Same as for Raw Data | 10 years | Yes | |
Events / Alerts | Events detected on Objects and locations: failures (Failure), anomalies (Anomaly), operations (Operation), Location events; with date and time, duration, severity, and description. | DPS Backend | UI: lists of active and historical Events, with export from the widget where enabled. API: active and historical Events | API: JSON
| Recorded in real time when the Event occurs and according to the periodic computation. Export on demand. | Failures with HEALTH topic: 10 years. | Yes, within the retention period. |
Work Sessions | Active and completed Work Sessions of the Products (e.g., production cycles), with start, end, duration, additional properties, monitored metrics, and post-computation values. | DPS Backend | UI: lists of active and historical Work Sessions.
| API: JSON | Real-time according to the periodic computation. Export: on demand | Completed Work Sessions: 12 months (default), plus any additional time. | Yes, within the retention period. |
Actions | Pending and completed Actions (e.g., replace oil), with start, end, duration, additional properties, performer, notes, and attachments. | DPS Backend | UI: lists of pending and historical Actions
| API: JSON | Real-time according to the periodic computation. Export: on demand | Historical Actions: 10 years (default). | Yes, within the retention period. |
Application Data | Master data and data managed by the DPS Backend: organization and sub-organizations, partners, customers, locations, Products (serial number, model, properties, status), users with profiles, permissions and authorizations, subscriptions to digital services, tickets, work orders, maintenance activities, actions, orders, uploaded documents and attachments. | DPS Users | UI: lists with export where enabled. | API: JSON Export: CSV file downloadable from the widget. | API: Real-time Export: on demand | Term of the Agreement, unless deleted by the Customer or the End User. | Yes, limited to the entities authorized to the DPS user. |
Metric Metadata | Metric documentation: technical name, label, group, type, unit of measurement, description and technical description (format, sampling frequency, publishing policy); composition of Metric Sets; | Console User | UI: Data Management.
| API: JSON | On demand. | Term of the Agreement | Yes |
Configuration Code | The elements, templates, images, JS, and CSS that constitute the Configuration Code. | Console User | Console: version creation and archive download. | ZIP archive: JSON-lines files (one per element type), HTML, JavaScript, CSS, images, and text. | On demand. | Term of the Agreement | Yes, limited to the Console User. |
Audit Log | Actions of DPS users: login and logout, page views, creation, update, and deletion of DPS elements, and also parameter updates, command execution, and file import. | DPS Backend | UI: list of audit events, with export where enabled. Console: export by period. | Export: CSV file downloadable from the widget or from the Console. | Recorded in real time. Consultation and export on demand. | 3 months | Yes, within the retention period. |
Notes to the table
The retention periods indicated are the default ones described in the Data section of the Console Advanced Settings page; any different provisions of the Commercial Offer prevail.
Orphan Data is kept for 6 months and progressively deleted; within this period the Customer may ask support to restore an element deleted by mistake.
Exporting Metric Data requires the “Export Things Data” (EXPORT_DATA) user permission; only one export can run at a time, and the generated archives remain downloadable for 30 days after completion.
Each user can access and export only the data of the Products and metrics allowed by their permissions and authorizations.The APIs are subject to the request rate limits configured for each API key and to an overall limit per environment, by default 2,000 requests per minute, as described in the Documentation.
Data Recipients may access, through export or API, only the Metric Data included in the “Raw Data” Metric Set of the Objects for which the Customer or the End User has generated a sharing token, under the conditions configured by the Customer in the DPS.
Data exports can be autonomously performed by DPS users in accordance with the available UI/API features.
Entities in the DPS can be extended with new properties; therefore, the export will include all default properties plus all those defined by the User Console.
The Data Sheet forms part of the Agreements referred to in the Terms and Conditions page.
Exclusions / Limitations
The following are not made available to the Customer and do not constitute Exportable Digital Assets:
The technical, security and internal operational logs of the Platform (e.g. distributed microservice logs, infrastructure monitoring metrics, System Administrator access logs).
The source code, built-in algorithms and standard components of the Servitly Software (including standard widgets and filters), which constitute Intellectual Property and trade secrets of Servitly.
The Customer’s custom algorithms and components are instead included in the Configuration Code.The backup copies of the Platform, which are not made available as such.
Third-party data not stored on the Platform, such as values read on the fly from external systems through integration plugins (e.g. volatile metrics) and data held on third-party IoT platforms or connectors.
The log of messages exchanged between Products and the DPS Backend (Message Logger), available through the UI for diagnostic purposes only.
Data deleted upon expiry of the retention period or upon deletion by the Customer or the End User.
Access or export requests requiring the Supplier’s intervention may be submitted through the support channels as stated in the Servitly SLA and in accordance with the contract with Servitly.
Data Sheet updates
The Data Sheet may be updated to reflect technical developments of the Servitly Software (DPS, Console).
In the event of inconsistencies, the provisions of the Agreement and of the Commercial Offer prevail; the Documentation and the Data Sheet describe the operational access methods and technical details.