Can an agricultural IoT project use an existing or third-party platform?
Yes. System integration can connect equipment to your existing platform or a suitable third-party service. Agree the data interface, included functions, account ownership, recurring costs and handover responsibilities before configuration begins.
- Equipment
Device IDs and configuration versions
- Data service
Fields, exports and retention
- System owner
Accounts, renewals and service responsibilities
List the readings, alerts and exports your team uses
A current reading, a historical graph, an export, an alert and a control command are different functions. List the functions required for the pilot and those planned later. A dashboard demonstration does not establish that every function is included in a quotation.
Write a small data contract
For each field, state device identity, measurement meaning, unit, timestamp, missing-value handling and upload interval. Add the authentication and acknowledgement requirements. Confirm export, retention and API access for the chosen service tier.
Make ownership operational
Identify who administers the account, retains configuration records, renews subscriptions and responds to incidents. Document credentials handover through an agreed secure channel. If control is included, separately define command authority, local protection and behaviour during communication loss.
Separate a phone app from a service-provider platform
An app may handle one account and its devices well. A project serving multiple customers also needs site separation, user roles, enrollment and service records. Confirm those functions on the intended platform tier. API availability and branding can require additional agreements or integration work. Demonstrate the specific owner and operator workflows before treating them as part of the delivered system.
Walk through a replacement before closing the handover
Ask the future system owner to show how a failed unit would be replaced and associated with the same site. Confirm which settings and historical records remain, who provides access and whether new fees apply. Then export one useful dataset using that owner’s account. A handover is easier to use when it includes these actions, not only a list of passwords and product manuals.
| Task | Handover detail |
|---|---|
| Add or replace a device | Enrollment access and device-to-site mapping |
| Export historical readings | Format, retention and applicable service tier |
| Renew connectivity | SIM or subscription owner and charges |
| Investigate an alert | Recipient, record access and local response owner |
Common questions
Does using a third-party platform mean SunGene only supplies hardware?
No. We can take responsibility for the agreed planning, configuration, data integration, testing and delivery work while using the platform appropriate to the project.
Are platform subscriptions always included?
No. Setup, hosting, subscriptions, retention and API access depend on the chosen service and are identified in the agreed scope.
