Skip to main content
    Select a Language

    Connected Product Data Specification Sheet

    1.  Connect

    Machine data

    Nature of collection

    • Telemetry Data Hub (TDH): Diagnostics and CAN data & Location data from machines – volume and actual data vary by machine type / series.
    • Connect portal: Diagnostics and CAN data from machines – volume and actual data vary by machine type / series. 

    Estimated volume

    • Telemetry Data Hub (TDH): CAN data from machines related to task execution relevant sensors stored locally at the machine and sent in a batch after task completion – volume and actual data vary by machine type / series. A Data Package varies from 100 Kb to < 1,5 Mb, depending on task execution duration and task related sensors available at the machine.
    • Connect portal: For 100000 connected machines, last 18 months of data roughly 10 terabytes.

    Frequency of collection

    • Telemetry Data Hub (TDH): Pipeline: KAFKA engine receives data every 10 seconds and We run process in less than 5 minutes. It also depends on batch size & type of message for process. 
    • Connect portal: Every time machine sends data, which is every 10 seconds on average. 

    User access to the data

    • Telemetry Data Hub (TDH): A new feature would be added to connect portal. In report section in connect, two new report types would be added so customer can extract one report for CANs and one report for Diagnostic codes.
    • Connect portal: Users can create a data request for the target machine’s data by logging in to Connect portal. The link to the ordered data will become available in the portal once it is ready. 

    Data storage arrangements

    • Telemetry Data Hub (TDH): The data are stored in Databricks data warehouse which is built on S3.
    • Connect portal: Telemetry and diagnostics data is stored in Mongo Atlas database. 

    Retention period

    • Telemetry Data Hub (TDH): 5 years- We have access to 5 years of data but based on our plans, we will provide data started from Sep 2025.
    • Connect portal: Connect stores past 18 months data for each machine. Data older than that will be automatically deleted. 

    Service data generation

    Nature of service data which can be generated

    • Telemetry Data Hub (TDH): Telemetry data could be utilized for following services: CO2 emission, Machine performance, Issues in machines, Machine pattern & strategies for usage, etc.
    • Connect portal: Machine performance daily statistics and long-term reports, active alarms, upcoming service date, Proactive Alerts, signal data diagnostics tool and geofence alerts. 

    Estimated volume to be generated by the solution

    • Telemetry Data Hub (TDH): Estimated volume of service is the amount of errors code multiplied by all telemetry sensors columns(670) plus any virtual sensors can be created.
    • Connect portal: Roughly 100 megabytes per machine. 

    Service data

    User access to the data

    • Telemetry Data Hub (TDH): For now the feature is designed just for raw data.
    • Connect portal: User can log in to Connect portal to access all the service data. 

    Storage arrangements

    • Telemetry Data Hub (TDH): NA.  
    • Connect portal: Mongo Atlas database. 

    Retention period

    • Telemetry Data Hub (TDH): NA. 
    • Connect portal: Past 18 months except the long-term reports and geofence alerts, which is stored indefinitely or until the user deletes the data themselves. 

    Expected use (and purpose for use)

    • Telemetry Data Hub (TDH): NA. 
    • Connect portal: Machine location, signal data, diagnostics tool, Proactive Alerts and upcoming service date are utilized by the service locations to provide timely service to the owner and minimize the downtime of the machine. 

    Third party data use

    Expected third party data use

    • Telemetry Data Hub (TDH): For the temporary solution in connect portal, we’re not going to consider third party access. 
    • Connect portal: Owners can enable telemetry data relay to a few selected data vendors in the Nordics, if they want. This relay feature is off by default. 

    User prevention of sharing with third parties

    • Telemetry Data Hub (TDH): -
    • Connect portal: If the user has enabled the data sharing to external service inside the Connect portal, they have the power to disable it at any time. Users can send feedback about their issues through feedback tool inside the portal. Those cases are automatically created into the CRM and handled by Digital Support team.  

    2.  TASK Doc

    TASK Doc is hosted by third party DeviceInsight.

    Machine data

    Nature of collection

    CAN data from machines related to task execution relevant sensors stored locally at the machine and sent in a batch after task completion – volume and actual data vary by machine type / series. 

    Estimated volume

    A Data Package varies from 100 Kb to < 1,5 Mb, depending on task execution duration and task related sensors available at the machine. 

    Frequency of collection

    User initiated, after task completion.

    User access to the data

    A Data Package varies from 100 Kb to < 1,5 Mb, depending on task execution duration and task related sensors available at the machine. 

    Data storage arrangements

    Data packages are stored with Device Insight at their AWS environment.

    Unpacked data being stored at FendtONE leveraging AGCOs AWS cloud storage.

    Retention period

    • n.N. for Device Insight / TaskDoc Server
    • 5 yrs for FendtONE unpacked data

    Service data generation

    Nature of service data which can be generated

    Agriculture task data containing a time bound record of machine sensor data bound to geographical locations (e.g. fields) used to conduct gov. reporting, client reports, performance analysis.  

    Estimated volume to be generated by the solution

    The volume varies by machine configuration and the different number of sensors along. In addition, it depends on the implement and the sensors of that device. As well the volume per transferred data package largely depends on the length of the recording (size of the field and working width of the applying implement). 

    Service data

    User access to the data

    Users can register an account in FendtONE free of charge and verify their machine ownership to get their service data displayed/accessible in our solution. 

    Storage arrangements

    Service data being stored at FendtONE leveraging AGCOs AWS cloud storage.

    Retention period

    5 years. 

    Expected use (and purpose for use)

    Internal reporting (anonymized) on Engaged acres and highly engaged acres. 

    Third party data use

    Expected third party data use

    The customer can decide to share data with third party applications they subscribed for by setting up data routing scenarios. AGCO won’t share data with their party providers aside of that. 

    User prevention of sharing with third parties

    By email to software.support@ptxag.com creating a ticket within FendtONE or calling the country specific phone number listed in FendtONE. 

    3.  PTx display data collection (GFX display)

    Machine data

    Nature of collection

    ISO 11783 CAN data & Location data from machines – volume and actual data vary by machine type / series.

    Estimated volume

    Average data consumption is 3 mb/hour.

    Frequency of collection

    CAN data from machines relative to task execution is streamed. Sample rate is a mix of periodic, and event based. On average every 60s.

    User access to the data

    Data is made available via the cloud portal. 

    Data storage arrangements

    Cloud Storage.

    Retention period

    N/A ( portal)

    Service data generation

    Nature of service data which can be generated

    Telemetry data could be utilized for following services: CO2 emission, Machine performance, Issues in machines, Machine pattern & strategies for usage, etc. 

    Estimated volume to be generated by the solution

    Tens of kilobytes per day per machine 

    Service data

    User access to the data

    Data is made available via the cloud portal. 

    Storage arrangements

    Cloud storage

    Retention period

    N/A (portal)

    Expected use (and purpose for use)

    Not applicable

    Third party data use

    Expected third party data use

    No

    User prevention of sharing with third parties

    N/A

    4.  PTx display data collection (Connected Farm)

    Machine data    

    Nature of collection

    Diagnostics and CAN data from machines – volume and actual data vary by machine type / series.

    Estimated volume

    N/A

    Frequency of collection

    N/A

    User access to the data

    Cloud portal www.trimbleag.com makes machine/device utilization data accessible to subscribed customers in a graphical web interface.

    Data storage arrangements

    Data is stored in MongoDB in PTx’s secure AWS hosted environment.

    Retention period

    N/A

    Service data generation

    Nature of service data which can be generated

    N/A

    Estimated volume to be generated by the solution

    N/A

    Service data

    User access to the data

    Device analytics data is anonymized and not exposed to end customers.

    Storage arrangements

    Google Firebase analytics service securely houses the anonymized usage data for connected devices.

    Retention period

    The data retention policy for Analytics/Service data is 90 days.

    Expected use (and purpose for use)

    Third party data use

    Expected third party data use

    No

    User prevention of sharing with third parties

    N/A