• Are the sensors ready for production?
• How do they connect and send the information?
• How do they work, do they use batteries?
• Which are the types of sensors, which ones are available? What is the cost? If we plan to use them, are they an eligible cost?

Answer:

Firstly, the Amicare sensors are handled by the Amicare application and servers, and your technology will interact with the sensors only via the Amicare APIs. The same applies to all PHArA-ON technologies.

Secondly, if you wish to integrate with Amicare or other PHArA-ON technologies, please remember that this is to be done only as part of the optional SA3, which will result in a separate system that is not run in a production environment with real users. For the SA3 integration, you will receive one or two copies of the needed Amicare sensors, but this is for technical testing and not for use in a production environment. If you are interested in using them in a production environment, this would be out of scope of the call.

Amicare sensors (or other PHArA-ON technologies) will be available at the beginning of your project. The Amicare HW device includes the following sensors:

• External sensor mat that can be placed in an armchair or bed for occupancy detection.
• Infrared sensors for movement detection.
• Environmental sensors: temperature, humidity and luminosity.
• External sensor to detect when the fridge is opened and closed.

Since you asked, Amicare sends sensor data through WiFi to a cloud server. It will be provided with no batteries, but with a wall power supply. For additional details, see section 3 of the OC2 technical document. Just to provide a little context, let me clarify that there are two main parts of an application that addresses all SAs:

SA1+SA2:

• These SAs are mandatory and thus common to all applications.
• All proposals should “create a pilot and a real deployment with relevant stakeholders on the basis of the selected PCHs and SAs” (section 2.2 OC2 text).
• Each consortium should provide its own technological solution to address this part and it does not require any integration with PHArA-ON.
• Regarding the evaluation of this part: “Evaluation of the applicant’s technology with respect to SA1 and SA2 will include full deployment of the standalone version of the technology in a care setting and evaluating with real end users.” (Section 3.1 OC2 text)

SA3:

• It is optional.
• It requires integration with 3 PHArA-ON technologies (see section 3.2 OC2 text) and the PHArA-ON Hub (described in the OC2 technical document).
• Evaluation: “For SA3, it involves a primarily technical evaluation of the integrated version of the technology to validate the implemented integration. End user evaluation for SA3 can be limited to only a small usability evaluation with target groups, which does not require a production environment.” (Section 3.1 OC2 text). So, it does not require deployment in the proposal’s pilot, only a technical validation and user evaluation with a small group of users.

In summary, the pilot in the proposal should be built considering SA1 and SA2 and using only its own technological solution (it does not include any PHArA-ON technology). If the proposal addresses SA3, an integration will be done with the goal of demonstrating the merits of the PHArA-ON approach to interoperability. The evaluation of this part will be limited to technical validation and user evaluation with a small group of users.

You should have your own pilot that you include in the proposal and not plan to involve Pharaon pilots.

Each proposal should “create a pilot and a real deployment with relevant stakeholders on the basis of the selected PCHs and SAs” (section 2.2 OC2 text). Applicants should be using their own technology and recruiting their own users. This OC2 pilot will be separate from Pharaon pilots, and thus, no users of current Pharaon pilots will be part of the OC2 (Open Call 2) project.

The pilot can be deployed in any EU country, with no budget limitation per region.

Only if SA3 is addressed, integration with 3 Pharaon technologies is required (see section 3.2 OC2 text) and the Pharaon Hub (described in the OC2 technical document). For the Slovenian pilot, the available technologies are Sentab, IoTool (Senlab) and Discovery (Ascora). These technologies are described in the OC2 technical document.

No, the whole consortium together can request up to 200.000,00 EUR.

Yes, you can apply with tax registration. However, see the request of validated PIC number.

As it is written in the call text, beneficiaries of Open Call 1 are not eligible to apply (see page 19 of the call)

For the mandatory part, addressing SA1 and SA2, you must build your own pilot with your own solutions and own users. This pilot will be completely independent from Pharaon, but it has to address the defined Pharaon Challenges (PCHs). Validation of this part “will include full deployment of the standalone version of the technology in a care setting and evaluating with real end users”. See section 2.2 in the OC2 text.

SA3 runs independently from the abovementioned pilot with users, but no deployment of this part is expected. Integration with 3 Pharaon technologies is required by the use of the Pharaon Hub (described in the OC2 technical document).

Regarding its validation: “… it involves a primarily technical evaluation of the integrated version of the technology to validate the implemented integration. End user evaluation for SA3 can be limited to only a small usability evaluation with target groups, which does not require a production environment.” (Section 3.1 OC2 text). So, it does not require deployment in the proposal’s pilot, only a technical validation and user evaluation with a small group of users.

Proposals should refer to the list of available technologies for the Second Open Call (OC2) in the Technical Document (section 3). Please, note that Pharaon platforms are not included.

After OC2 evaluation process is over, there will be some other Pharon technologies available. These technologies will be presented to the selected winner consortiums, who can then change their initial selection.

If any of the Pharaon technologies chosen by the applicant consortium includes HW devices, at least two devices will be made available for testing. Please, note that addressing SA3 only implies a technical evaluation and does not require a production environment. There will be end user usability evaluation, but only with a small target group.

Unlike the full pilot addressing SA1 and SA2, SA3 does not require deployment in the proposal’s pilot, only a technical validation and user evaluation with a small group of users.

The call text is clear, that the validated PIC number is required. No exceptions will be made.

Yes, this is correct. You should use your own technology.

The OC2 text on page 19 states:” Consortia other sizes may be considered. Including at least one SME or Micro SME is recommended.”

Sections 2.2 and 3.1 in OC2 text include the main elements of what would be considered for evaluation.

You can submit 2, if you coordinate one. You can’t submit in any case more than 2 proposals.