The PoC has been elaborated within the startup section of BSB SF platform for accelerating digitalization and smart technology transfer into agri-food ecosystem within BSB region. The propose of this section is to create relevant environment where the PoC or the Prototype can meet with their potential users or/and funding companies sponsors within the platform.
Anyone be a natural person or an organization individually or as a team from Armenia, Bulgaria, Georgia, Greece, Moldova and Rumania can present the PoC to focus on smart technologies and address the agriculture challenges in agri-food ecosystem through potential the potential users, funding companies etc. (the direction is small and smart farming, climate smart solutions, technologies and IoTs, across the agri-food production value chains).
What is PoC?
PoC shows the viability and get investor’s buy in smart and brilliant ideas for the next best solution to be an exciting venture for project teams. PoCs describes the idea and proposed functionality of the product, including its general design or specific features, and how achievable they are.
Proof of Concept vs Prototype
Proof of Concept
- Proof of concept (PoC) is a theoretical demonstration of a product/process/concept.
- It basically determines whether an idea can be turned into a reality.
- PoC exhibits the idea’s viability and its potential to be developed or/and build.
- It also verifies if the idea will function as envisioned.
- PoC identify potential technical and logistical issues that might be interfere with success.
- Exhibits how the proposed product or/and service will support organizational goals or other business requirements as a secondary goal.
- Not intended to explore market demand for the idea, or determine the best production process.
- It is a theoretical demo that the solution is achievable.
- Describe very beginning draft of a product/process/concept.
- It can be tested and evaluated for usability, functionality and design.
- Not expected to have all features and functions of a market-ready product.
- Present draft of what the final product might be.
- Accelerate full production for a final market-ready item.
- It is a physical demo or sample of how the product will operate.
I. Executive Summary (To be completed at the conclusion)
- Background (Current state, problem, environment and how we got here)
- Purpose (Why is this initiative important)
- Scope of Initiative (What’s in and out of scope for this initiative)
III. Goals & Key Objectives for the Proof of Concept, or Prototype
- Define the goals
- Define the objectives of the goals
- Define the relevant resource, environmental, operational, and/or political constraints in which the initiative must operate under
V. Evaluation Approach Overview
- Define the proposed options or alternatives to be evaluated
- Define the evaluation approaches
- Define comparative analysis to be conducted for the proposed options or alternatives
- Define the environment, location(s), and general composition of the evaluation team(s)
- Define projected duration of initiative ( i.e., components, phases, and overall)
VI. Key Decisions to be made at the conclusion of the initiative
VII. Evaluation Design
- What will be evaluated specifically
- How and where will products/concepts/alternatives/systems/processes and their specific components be configured, tested, monitored, evaluated, and documented
- Where and when will specific components be tested (Locations, environments, sequencing and their associated interdependencies)
- Identify known and potential impacts to business and/or technical operations and define corresponding criticalities and mitigation strategies
- Resources required (i.e., facilities, equipment, people, etc.)
- Team composition (e.g., SMEs, skill sets, etc.) for each phase and their respective roles and responsibilities
- Outline Expected Outcomes and Criteria for success
- Establish Evaluation Matrix and Worksheets
- Governance and Decision Authority and Approvals
VIII. Evaluation Logistics
- Project WBS/Plan, Milestones, Deliverables, Project Execution, Control & Monitoring (including issues/risk management), Close-out, Team member and resource allocations
- Preliminary Preparations Required (e.g., Environments, facilities, people, scenarios associated with each component test & evaluation cycle)
- Alignment of stakeholders, resources, and facilities
- Travel and coordination affiliated with geographically disbursed teams and/or test sites involved in the initiative
- Communications (Reports, PEP Document, and Project Plan to stakeholders)
IX. Lessons Learned (Feedback and perhaps discussion on topics, considerations, and valuable information that are above and beyond the scope of this initiative)
X. Evaluation Findings & Conclusions
XI. Recommendations & Final Decisions