BEACON Customer Integration Roadmap

The BEACON Customer Integration Roadmap is designed to provide clarity of all development phases and to simplify the process of attracting and on-boarding of as many as possible AgI companies into Lighthouse Customers Group.

Therefore, BEACON Business Team divides this process into 6 phases:

FIRST APPROACH WITH THE POTENTIAL LHC / INVOLVEMENT INTO LHCs GROUP

Timeframe: M1-M37 (ongoing process)
BEACON Responsible Partners: InoSens, Agroapps, Karavias  

Activities:

  • B2B meetings/ B2G meetings.
  • Mails, initiations to join the Lighthouse Customers Group, presentations.
  • Official involvement – Letter of Support.

CURRENT VERSION OF THE BEACON TOOLBOX / PREPARATION FOR THE CO-CREATION PHASE

Timeframe: M1-M13
BEACON Responsible Partners: InoSens, Agroapps, Karavias        

Activities:

  • Involvement of BEACON Technical/Scientific team and the coordinator into the communication with Lighthouse Customer.
  • Presentation of the BEACON Toolbox idea.
  • Demonstration of the current version of the Toolbox.

BEGINNING OF THE CO-CREATION PHASE OF BEACON TOOLBOX DEVELOPMENT

Timeframe: 1st and 2nd month of communication with new LHC
BEACON Responsible Partners: InoSens, UBFCE, Agroapps       

1st BEACON Minimum Viable Product (MVP) for the user requirements/ co-creation:

  • Feedback collection from LHCs through co-creation questionnaires (or teleconferences).

SUPPLY OF LHCs DATA/MVP DEVELOPMENT

Timeframe: M2-M12
BEACON Responsible Partners: InoSenS, AgroApps           

2nd BEACON MVP - Specific data collection from LHCs:

  • Historical data on crop damages (and related data).
  • The current template of agri-insurance contract of the company.

3rd BEACON MVP – Before integration, the collection of feedback on services is performed together with collection of opinions with regards to the functionality and bugs. After this, 2 types of integration will be proposed (based on needs of LHC):

  • Partial integration – selected BEACON services to be integrated into current operational setting of LHC.
  • Total integration of all BEACON Toolbox within the current setting.

PILOT SPECIFICATION/ IMPLEMENTATION BASED ON THE 3 STAGES

Timeframe: M13
BEACON Responsible Partners: All BEACON partners

  • Alpha stage: Alpha stage demonstrates in practical settings previously defined processes and workflows between EO data processing partners and LHCs;
  • Beta stage: Beta stage serves to validate following BEACON services: Weather Risk Probability (Prediction and Assessment) and Smart Contracts; as well as the required services: Crop Monitoring, Crop Damage Assessment Calculator, Parcel Anti-Fraud Inspector, Crop Damage Prevention-Prognosis, and Extreme Weather Events Early Warning System.
  • Gamma stage: Gamma stage serves to validate the use of the infrastructure as a means of storing and transferring information between actors involved. Once these processes have been executed in operational settings, Gamma stage will proceed to validate the execution of damage payments through automated smart contracts.

INTEGRATION OF BEACON INTO THE BUSINESS WORKFLOW OF LHC/ PRICING STRATEGY, STRUCTURE AND PAYMENT METHOD

Timeframe: M36
BEACON Responsible Partners: InoSens, Agroapps

BEACON Business team leverages the BEACON price scheme within this final stage, based upon the modularity of BEACON Toolbox and chosen integration method of BEACON services by each LHC. In addition, the payment method will be defined within this phase.

  •  
  •  
  •  
  •  
  •  
  •  

Leave a Reply

Your email address will not be published. Required fields are marked *

TOP