ERP & CRM
Connect customer and product data from your commercial system with advice and order preparation in iCrop. FarmPlus uses a connection with Microsoft Dynamics F&O. Define which records move in each direction and where the order is processed.
Connected systems.
Trusted foundations.
Review data flows, access, security and hosting in one place.
Integrations & APIs
Connected systems.
Clear ownership.
A useful integration starts with responsibility for the data. Agree the source system and the direction of exchange for your configuration.
| Information | Typical responsibility to agree | What to connect |
|---|---|---|
| Growers & contacts | CRM, ERP or iCrop, depending on your landscape | Identifiers, contact data and the grower relationship. |
| Fields & cultivations | The agreed field or farm-management source | Field context, crop and season. |
| Visits, observations & advice | The agronomy workflow in iCrop | The field record and information needed for follow-up or reporting. |
| Products & orders | The relevant commercial system and iCrop order preparation | Product identifiers, requirements, quantities and the defined handover. |
| Management reporting | The agreed reporting or BI environment | Operational records and measures relevant to the business. |
SYSTEM LANDSCAPEWork with the systems
Work with the systems
already in your operation.
Connect iCrop to your commercial, field and reporting systems. Interface availability and delivery scope are confirmed for each project.
Farm & field systems
Agrovision, Dacom, JoinData and FarmMaps are named in the integration materials. Scope the relevant field data and permissions.
NETHERLANDS
iCrop connects with FarmMaps, owned by WUR, for agreed data exchange around biodiversity reporting with BO Akkerbouw’s BMA app. Define the required crop data and permissions for your setup.
FarmMaps & biodiversityManagement reporting
Use the recorded visits, recommendations and tasks as input for the reporting your organisation needs. Agree the datasets and any BI connection for your environment.
Know what is included in the plan.
In iCrop
Grower, field and crop records, visits, observations, recommendations and tasks form the core of the workflow.
For your organisation
We define the source system, user rights, data mapping and required exchange.
Additional integration work
Connections to ERP, CRM or BI are specified separately for the available interfaces. Mentioning a system does not imply a standard connector.
Security & hosting
Role-basedAccess to relevant records
Cloud or on-premiseDeployment choice
EEA hostingAvailable for regional requirements
Hosting-provider ISO 27001Certification applies to the hosting provider
DATA OWNERSHIP & ACCESSThe right information.
The right information.
For the right people.
Keep the agronomy record useful to the team while controlling access to grower and operational information.
Data ownership
Your organisation retains ownership of its operational data. Define rights to grower information, sharing and access in the relevant agreements.
Configurable permissions
Configure access around operational roles and the organisation’s team structure. Review the scope needed across agronomists, teams, crops and regions.
Operational history
Keep records available across visits and seasons. Audit logging supports review of activity within the platform; the applicable logging scope is part of the technical review.
SECURITY CONTROLSReview the controls
Review the controls
for your environment.
Security and operational responsibilities need to match the chosen deployment.
Encrypted infrastructure
Encryption forms part of the infrastructure described for iCrop. Review the applicable controls and data flows for your selected environment.
Secure interfaces
API integrations use controlled interfaces. Agree access, the information exchanged and the responsibilities at each system boundary.
Monitoring & recovery
Review monitoring, backup and recovery arrangements as part of the service design. Service levels and recovery commitments are defined in your agreement.
ISO 27001 refers
to the hosting provider.
The hosting provider’s ISO 27001 certification covers its information-security management scope. Application controls and your organisation’s responsibilities are assessed separately. Review the applicable certificate and scope for the selected hosting arrangement.
For an on-premise deployment, infrastructure controls and responsibilities are agreed with your own IT team.
Request a demoDEPLOYMENT OPTIONSChoose the environment
Choose the environment
that fits your IT requirements.
Cloud and on-premise options are available. Select the deployment model and responsibilities during the technical review.
AWS cloud infrastructure
A cloud deployment for organisations that want iCrop delivered within a cloud environment. Agree the operating responsibilities and service arrangements.
EEA data hosting
EEA hosting is available for organisations with regional data-location requirements. Confirm the location and scope for the chosen deployment.
On-premise deployment
An enterprise deployment option for organisations that need the environment within their own infrastructure. Agree infrastructure, upgrades, monitoring and support responsibilities.
Know what is included in the plan.
Access in the application
Manage access to records through user roles and the configured team structure.
For your hosting choice
Cloud or on-premise, the storage region and infrastructure responsibilities belong to the deployment scope.
Evidence for your review
Review the applicable provider certificate, data processing agreement, backups and service terms for the proposed environment.
QUESTIONS THAT MATTERClear answers.
Clear answers.
Useful next steps.
Can we connect our own BI environment?
BI integration is part of the offering. Define the dataset, reporting needs, access and refresh requirements. A Power BI connector can form part of the scope; confirm the required datasets and delivery in your proposal.
Can API documentation be part of our review?
Ask for the interface documentation relevant to the records and operations in your proposed integration. Access and delivery responsibilities are agreed for your environment.
Can growers’ data be shared with everyone in our organisation?
Access is controlled through the agreed permissions. Define the purpose, recipients and rights to grower information in your data arrangements; a shared platform does not mean unrestricted access.
Can we review backup, incident and service arrangements?
Yes. Include backup and recovery, incident contacts, support coverage and service-level commitments in the technical review and commercial agreement. Service levels and recovery targets are set for the selected deployment in your service agreement.
How should we assess data protection?
Review the roles of the parties, processing purposes, chosen hosting location, subprocessors and the applicable processing agreement with your IT and privacy team.
YOUR NEXT STEP
Map your data flow with us.
Review the systems, records and responsibilities involved, then define a practical integration scope.