EU Data Act Switching Documentation for Senseye¶
I. Switching Information - Initiating the Switching Process¶
You can initiate the switching process by contacting Senseye support team at senseye.support.industry@siemens.com
II. List of (Exportable) Data and Digital Assets¶
Exportable Data¶
This category includes data that the customer has entered the service or that has been generated through their use, excluding the provider's assets or data that are protected by intellectual property rights or constitute a trade secret.
Input data¶
| Subcategory | Supported Formats | Available Transfer Methods | Limitations/Restrictions/Risk Factors | Special Notes |
|---|---|---|---|---|
| Knowledge Files Customer uploaded documents such as Word and PDF documents that provide contextual information to enhance Senseye's predictive maintenance analysis. | Specified by Customer on upload. Common file formats supported e.g., Microsoft office formats, pdf, png, mp4 | REST-API | see Guidelines | |
| Work events Structured records of work activities performed on monitored assets (e.g. maintenance history). | JSON | GraphQL | see Guidelines | |
| Notes Customer-specified notes | JSON with Markdown text syntax for body of note | GraphQL | see Guidelines | |
| External ID Mappings Customer-defined references that link Senseye's internal identifiers with external system identifiers | JSON | GraphQL | see Guidelines | |
| Hierarchy Customer-defined organizational structure of assets showing parent-child relationships betweens equipment, production lines and facilities | JSON | REST-API | see Guidelines | |
| Groups Customer-created collections of assets organized by custom criteria, allowing users to manage and analyze related equipment together regardless of their position in the hierarchy. | JSON | GraphQL | see Guidelines | |
| Watch list Customer-defined collection of priority assets that require special attention or monitoring, enabling users to quickly access and track critical equipment that may need immediate intervention | JSON | REST-API | see Guidelines | |
| Sensor data Sensor-generated measurement sent from sensors on customer site | JSON | REST-API | This is likely to be a large volume of data. Please contact support team to arrange export | see Guidelines |
Meta data¶
| Subcategory | Supported Formats | Available Transfer Methods | Limitations/Restrictions/Risk Factors | Special Notes |
|---|---|---|---|---|
| Asset metadata Descriptive information about monitored assets, including names, types, specifications, locations, and other identifying characteristics. | JSON | GraphQL | see Guidelines | |
| Sensor metadata Descriptive information about the characteristics of data collection points (sensors) that monitor physical assets. | JSON, CSV | GraphQL, REST-API | see Guidfelines |
Output data¶
| Subcategory | Supported Formats | Available Transfer Methods | Limitations/Restrictions/Risk Factors | Special Notes |
|---|---|---|---|---|
| Cases Issues on assets identified by Senseye's predictive maintenance system that require investigation or action, containing details about issues, recommended solutions, and resolution history to facilitate maintenance decision-making and knowledge sharing. | JSON | REST-API | see Guidelines |
Jointly Generated data¶
| Subcategory | Supported Formats | Available Transfer Methods | Limitations/Restrictions/Risk Factors | Special Notes |
|---|---|---|---|---|
| Derived Measures Expressions that transform raw Sensor data into data that is more appropriate for analytics. | JSON | REST-API | see Guidelines | |
| Aggregated sensor data (Features) Statistical aggregations of sensor data, such as hourly mean, that serve as inputs for algorithms. | - | - | This is likely to be a large volume of data. Please contact support team to arrange export which be provided in a number of different formats including CSV, JSON (SenML), parquet | |
| Attention Aggregate information from analytics related to assets and detected issues. | JSON | GraphQL | see Guidelines | |
| Case Events Individual actions, status changes, or updates that occur throughout the lifecycle of a Case, such as case creation, assignment, progress updates, resolution steps, and closure, providing an audit trail and timeline of activities within each case. | JSON | REST-API | see Guidelines |
Digital Assets¶
This category includes elements in digital form for which the customer has a right of use, regardless of the contractual relationship with the data processing service.
| Type | Specific Element | Supported Formats | Available Transfer Methods | Special Notes |
|---|---|---|---|---|
Categories of data specific to internal functioning¶
This category includes data that is specific to the internal functioning of the provider's data processing service and whose disclosure would violate the provider's trade secrets.
Analytic Configuration¶
| Specific Element(s) | Purpose | Reasons / Special Notes |
|---|---|---|
| System settings, parameters, algorithmic configurations | Define how Senseye analyzes data, detects anomalies, and generates predictions, including thresholds, model parameters, and analysis rules. | Proprietary data optimized through extensive testing and operational experience that constitute Siemens' trade secrets and provide competitive advantage in predictive maintenance accuracy. |
Patterns¶
| Specific Element(s) | Purpose | Reasons / Special Notes |
|---|---|---|
| Behavioral signatures, Anomaly templates, Failure mode characteristics | Used by Senseye's algorithms to recognize specific asset conditions, predict potential failures, and classify maintenance issues, representing the accumulated knowledge base of how different types of equipment problems manifest in sensor data. | Proprietary data developed through extensive machine learning training and domain expertise that constitute Siemens' trade secrets and provide competitive advantage in predictive maintenance accuracy. |
Internal Security Data¶
| Specific Element(s) | Purpose | Reasons / Special Notes |
|---|---|---|
System Configuration Parameters¶
| Specific Element(s) | Purpose | Reasons / Special Notes |
|---|---|---|
| User systems | User-specific settings that customize the Senseye interface and functionality according to individual user needs. This includes notification settings, dashboards, display options, data visualization layouts, and widget configuration. | Proprietary system optimization settings and resource management configurations that define internal platform behavior, constituting Siemens’ trade secrets and providing competitive advantage in platform performance. |
| User reports | Specifications that generate documents that summarize predictive analysis results in the context of a customer site. | Proprietary system optimization settings and resource management configurations that define internal platform behavior, constituting Siemens’ trade secrets and providing competitive advantage in platform performance. |
Operational Control Data¶
| Specific Element(s) | Purpose | Reasons / Special Notes |
|---|---|---|
| Infrastructure configuration | Configuration relating to the deployment of Senseye in the cloud | Proprietary automation parameters and operational procedures that control platform monitoring and recovery processes, constituting Siemens’ trade secrets and providing competitive advantage in system reliability. |
Operational Data¶
| Specific Element(s) | Purpose | Reasons / Special Notes |
|---|---|---|
| Logging, Metrics | Information captured by the routine operation of the Senseye Application | Proprietary operational details that detail Senseye processes, constituting Siemens’ trade secrets and providing competitive advantage in system reliability. |
III. Special Complexity Factors¶
The following aspects of our service may complicate or increase the cost of switching:
| Components | Complexity Factors | Impact | Possible Additional Costs |
|---|---|---|---|
| Derived Measures | Proprietary format | Derived measures not supported by other systems | Implement translation to target platform's capabilities |
IV. International Access and Transfer¶
Jurisdiction to which the ICT infrastructure deployed for data processing of their individual services is subject¶
ICT infrastructure for Senseye Cloud PDM is deployed in mainland Europe.
Technical, organizational and contractual Measures¶
Infrastructure is hosted by Azure and AWS. 3rd party databases are also in Azure.