Frequently Asked Questions
Frequently Asked Questions
To make this clearer
Smart Land
It is a Competence Centre: it works on projects, trials and replicable models, with an approach focused on measurable outcomes and transfer.
Smart Land broadens the scope: not only urban services, but territories and settlement contexts, with a strong focus on community-based care, living environments, the environment and intelligent management of spaces.
The approach is applied: we work on proofs of concept and real-world trials, with metrics and governance, to prepare for replication and transfer.
Yes, because it makes a project assessable: it clarifies where the value lies, reduces uncertainty and builds evidence useful for partnerships and scalability
It depends on the clarity of the use case, willingness to define metrics and responsibilities, data quality, and the possibility of testing in a real-world setting under shared rules.
A replicable project defines metrics, roles, flows and minimum requirements, and produces evidence that can be transferred to other contexts without reinventing everything each time.
Monitoring observes and measures; remote control enables controlled and traceable actions on the system. They make sense together only when roles, rules and indicators exist to justify action.
By selecting objectives and indicators before sensors, defining sensible thresholds, validating data quality and linking signals to real operational procedures.
In Smart Land, it concerns both. Territories, spaces and people are part of the same system: environmental data become useful when they support safety, prevention, maintenance and quality of life.
No. A lean, well-designed and maintainable system often creates more value than complex architectures that do not remain sustainable over time.
? A partnership is assessable when it defines the objective, scope, roles, metrics and timelines, and when it includes a trial that generates evidence to guide a decision on extension or industrialisation.
It depends on the use case and context, but it must be long enough to generate reliable data and span real-world conditions, not just ideal scenarios. The objective is to reduce uncertainty and prepare for replication.
No. It is suitable for public administrations, businesses and investors precisely because it works on replicable models and evidence: the common language is governance, metrics and operational sustainability.
No. SEETI works mainly on the operating model and practical effectiveness of digital services: processes, roles, quality, data and sustainability. Technology is selected or integrated according to the process, not as an end in itself.
No. Remote monitoring is one possible component of telemedicine; in a community-based model, telemedicine also includes processes, responsibilities, integrations, communication tools and continuity of care.
A well-defined use case: objective, context, stakeholders, constraints, available data and expected outcome. From there, metrics are defined and a controlled experiment is built.
Emergency telecare is centred on emergencies and response; teleassistance works on continuity and prevention. In an effective model, they integrate without being confused.
Not necessarily. The device may be one component, but what determines resilience is the service: procedures, operations centre, community network, responsibilities and information quality.
With clear rules, sensible thresholds, event contextualisation, training and service design that avoids generating unnecessary signals. Technology helps, but it does not replace design.
It depends on the use case. It is often a bridge: it starts with support and safety and, when necessary, integrates with healthcare pathways and telemedicine.
A smart home is oriented towards comfort and automation; assistive home automation is designed for autonomy, safety and continuity, with operational rules and integration with caregivers and services.
Not always, but it is often useful to provide an escalation channel. Integration only makes sense if it delivers context and clear actions, not if it simply generates more notifications.
Yes. The assisted-living unit model can be adapted to residential settings and healthcare or care facilities, with appropriate requirements and governance.
A lab is a repeatable method: use-case selection, indicators, governance, field experimentation and preparation for replication. A pilot can remain an isolated episode if it does not produce reusable standards and criteria.
No. It is a governance capability: useful data, processes, responsibilities, maintenance and continuity. Technology is a tool, not a definition.
It must last long enough to produce reliable data and span real-world conditions, not just ideal scenarios. Duration depends on the use case, but the objective remains to make the result measurable and transferable.
Almost everything changes. A device without a response chain, procedures, indicators and exception management creates an illusion of safety. A designed service, by contrast, makes the response predictable and measurable.
When there are no priority rules, manageable thresholds, criteria for false alarms and clear responsibilities. In that case, operators become overloaded and the service loses effectiveness.
Yes, especially when the service is active but fragile: too many false alarms, unused data, duplication, integration difficulties and an unsustainable operational workload.