Use Case Description & Contacts:
Select Project*:
—Please choose an option— test - please delete MARE SUSTAIN-6G SNS CO-OP AMAZING-6G 6G-LEADER AMBIENT-6G 6GARROW 6G-MIRAI FLECON-6G MultiX 6G-VERSUS UNITY-6G X-TREME 6G XTRUST-6G 6G-DALI NexaSphere 6G-TWIN SAFE-6G ENVELOPE ROBUST-6G 6G4Society 6G-CLOUD TeraGreen EXIGENCE 6G-DISAC ECO-eNET PROTEUS-6G 6G-REFERENCE INSTINCT FirstTo6G 6G-PATH 6G-MUSICAL 6G-EWOC 6G-XCEL iTrust6G 6G-GOALS SUNRISE-6G 6G-INTENSE ORIGAMI 6G-SENSES NATWORK iSEE-6G Opti-6G ELASTIC 5G-STARDUST 6G-BRICKS 6G-NTN 6Green 6G-SANDBOX 6G-SHINE 6GTandem 6G-XR ACROSS ADROIT6G BeGREEN CENTRIC CONFIDENTIAL6G DESIRE6G DETERMINISTIC6G ETHER FIDAL FLEX-SCALE Hexa-X-II HORSE IMAGINE-B5G NANCY PREDICT-6G PRIVATEER RIGOUROUS SEASON SNS ICE SNS OPS SUPERIOT TARGET-X TERA6G TERRAMETA TIMES TrialsNet VERGE
Select Stream*:
—Please choose an option— Stream A Stream B Stream C Stream D CSA
Use Case Name*:
Use Case Location*:
Use case/Solution description*: Please explain in a concise manner what your Use case will deliver (max 200 words)
Project Representative Name*:
Project Representative eMail*:
Technical dimension - 11 Questions (T1-T11):
This assessment dimension would determine if a project result/solution is replicable or scalable from a technical point of view.
T1: Openness of components: Component provides interfaces that could allow easy integration in other environments
Easy to integrate in another environment--2 Difficult to integrate in another environment without expert support--1 Impossible to integrate in another environment--0
T2: Interoperability of components - Standardized device communication API: Provides application developers with uniform and transparent access to physical devices and wearables. (e.g. SCRAL, LinkSmart)
Standardised API available--1 No API available--0
T3: Standardized Data Modeling: Allows IoT syntactic and semantic interoperability (e.g. OGC SensorThings API), Standardized Data model available
Standardised Data Model--1 Proprietary data model--0
T4: IoT Platform interoperability: Allows the integration with other IoT platforms (e.g. oneM2M, FIWARE, Azzure, …, see SCoDIHNet platform catalogue)
Component is running on one of the IoT platforms--1 Component is running on a proprietary platform--0
T5: Modularity: Referred to modular IoT architecture that can be customized for a diverse range of applications or, in general, to a design principle that subdivides a system into smaller parts called modules, which can be independently created, modified, replaced, or exchanged with other modules or between different systems
Components have been designed with several modules--1 Components have been designed in one single module--0
T6: Compatibility with legacy infrastructure and equipment: The solution is using legacy network infrastructure (5G, Sigfox, Lora, NB-IoT, …) and devices
The solution is using legacy infrastructure and legacy devices--2 The solution is using legacy infrastructure and proprietary devices--1 The solution is using proprietary infrastructure and legacy devices--1 The solution is using proprietary infrastructure and proprietary devices--0
T7: Updates & Maintenance: Components should evolve to add new functionalities or to correct bugs, this could be made could be easily remotely or need intervention of experts
Components updated and maintained by the integrator--1 Maintenance and updates need expert intervention--0
T8: Standards Compliance: Many standards have been developed for IoT and communication, interoperability could only become a reality if components are compliant to one or the other standards
Components are compliant to a standard--1 Components are not compliant to any standard--0
T9: Communication/Cloud infrastructure: Data generated by IoT need to be stored and manipulated before feeding the end user application. This topic targets the communication protocol used to send out data to the cloud data centre. There are several types of protocol available (Sigfox, LoRa, 4G, 5G, RF, NFC, …) which need to offer interoperability
Components compliant with a standard communication protocol--1 Components use a proprietary communication protocol --0
T10: Exploitation potential/applicability to industrial relevant environment: In order to contribute to the Digitalisation of the European Industry (Digital Europe Program) through the Digital Innovation Hubs, a component should be used for use cases addressing industry whatever it is
Components are able to be used in an industrial environment --1 Components are not usable in an industrial environment--0
T11: Technology Readiness Level: A method to estimate the technology maturity of the solution
TRL 1 - Basic principles observed--1 TRL2 - Technology concept formulated--2 TRL3 - Experimental proof of concept--3 TRL4 - Technology validated in lab--4 TRL5 - Technology validated in relevant environment--5 TRL6 - Technology demonstrated in relevant environment--6 TRL7 - System prototype demonstration in operational environment--7 TRL8 - System complete and qualified--8 TRL9 - Actual system proven in operational environment--9
Technical Replicability factor score:
Data dimension - 6 Questions (D1-D6):
This assessment dimension would determine if a project result/solution is replicable or scalable from a “Data” point of view.
D1: Compatibility with data privacy rules: Data provided by IoT and used by applications should be under the European regulation. IoT are providing basic information but also videos, pictures or human sensors data that fall under GDPR
Components are not collecting personal data--1 Components are collecting personal data but respect the GDPR--0
D2: Data Modelling: Data modelling is the process of creating a visual representation of either a whole information system or parts of it to communicate connections between data points and structures. Data modelling employs standardized schemas and formal techniques. This provides a common, consistent, and predictable way of defining and managing data resources across an organization, or even beyond. A number of tools are available to support the methodology (Erwin Data Modeller, Enterprise Architect, ER/Studio, Open ModelSphere, …)
A data modelling tool has been used--1 No data modelling tool has been used--0
D3: Data Security: Data security is the practice of protecting digital information from unauthorized access, corruption, or theft throughout its entire lifecycle. How many of these 4 security components: Data Encryption, Data erasure, Data masking and Data resiliency is the component implementing?
Component is implementing all 4 Data security components--4 Component is implementing 3 of 4 Data security components--3 Component is implementing 2 of 4 Data security components--2 Component is implementing 1 of 4 Data security components--1 No security components are implemented--0
D4: Data Quality: Data quality measures the condition of data relying on factors such as how useful it is to the specific purpose. How many of these 6 quality factors: Completeness, Accuracy, Timeliness (e.g., is it up to date?), Consistency, Validity, and Uniqueness is the component implementing?
Component is implementing all 6 Data quality factors--6 Component is implementing 5 of 6 Data quality factors--5 Component is implementing 4 of 6 Data quality factors--4 Component is implementing 3 of 6 Data quality factors--3 Component is implementing 2 of 6 Data quality factors--2 Component is implementing 1 of 6 Data quality factors--1 No Data quality factors are implemented--0
D5: Data Assets Management: Data assets management (DAM) has the objective to acquire, monitor, use, optimise, and exploit data assets to generate value. The 3 DAM factors encompass Accessibility, Compliance and Risk management.
Component is providing all 3 DAM factors--3 Component is providing 2 DAM factors--2 Component is providing 1 DAM factor--1 No DAM factors implemented--0
D6: Data Relevance: Data relevance is a measure of the impact of specific data on decisions or actions by the user. Collecting irrelevant data contributes to information “overload” and complicates decision‐making
Component is able to select relevant data--1 Component is only using specific collected data--0
Data Replicability Factor score:
Market dimension - 8 Questions (M1-M8):
This assessment dimension would determine if a project result/solution is replicable or scalable from a business point of view.
M1: Market analysis: A market analysis provides information about industries, customers, competitors, and other market variables. You can also determine the relationship between supply and demand for a specific product or service. Based on these insights, you can make more informed decisions about possible marketing strategies.
A market analysis has been conducted--1 No market analysis conducted yet--0
M2: Demand analysis: Demand analysis is a research done to estimate or find out the customer demand for a product or service in a particular market. Demand analysis process needs to be done in a structured manner for a particular market and affects the business strategy and decisions. Some of the steps which are to be followed for the analysing the demand are: Market selection, Product/service category analysis, understanding business parameters, understanding the competitors and partner trends.
A demand analysis has been conducted--1 No demand analysis conducted yet--0
M3: Business model: The term business model refers to a company's plan for making a profit. It identifies the products or services the business plans to sell, its identified target market, and any anticipated expenses. There are a number of Business models but for a manufacturer which is responsible for sourcing raw materials and producing finished products by leveraging internal labor, machinery, and equipment. A manufacturer may make custom goods or highly replicated, mass produced products. A manufacturer can also sell goods to distributors, retailers, or directly to customers.
A business model has been developed--1 No business model available yet--0
M4: Stakeholder needs analysis: A stakeholder analysis is a project management tool used to identify the project’s stakeholders, issues they care about and how they will be impacted by the project.
A stakeholder needs analysis has been conducted--1 No stakeholder needs analysis conducted yet--0
M5: IPR analysis: Intellectual Property Rights (IPR) aim to stimulate innovation by enabling inventors to appropriate the returns on their investments.
An IPR analysis has been conducted--1 No IPR analysis conducted yet--0
M6: Intellectual Property (IP) strategy for your solution: An IP strategy is a plan for you to develop, grow, leverage and monetize your portfolio of IP assets.
There is no specific IP strategy defined yet--0 An IP strategy has been defined--1 An IP strategy is in place--2
M7: Solution validated in the market: Market validation includes reviewing your solution with your market (customers and prospects).
Your solution has not been deployed at customer site--0 Your solution is deployed at (prospect) customer site--1 Your solution is generating revenues--2
M8: Business Readiness Level: A method to estimate the business maturity of the solution.
BRL1 - Concept--1 BRL2 - Problem-solution fits--2 BRL3 - Build team and plan--3 BRL4 - Customer definition--4 BRL5 - Hypothesis testing--5 BRL6 - Minimum viable product--6 BRL7 - Feedback--7 BRL8 - Scale--8 BRL9 - Fully embedded business--9
Marketing Replicability Factor score:
Acceptance Dimension - 6 Questions (A1-A6):
This assessment dimension would determine if a project result/solution is replicable or scalable from a product acceptance point of view.
A1: End-user interface design/usability: User interface design is responsible for a product's appearance, interactivity, usability, behaviour, and overall feel. UI design can determine whether a user has a positive experience with a product.
User Interface not previewed/published yet--0 A focus group has been conducted--1 A user test has been conducted--2 A pilot/experiment has been conducted--3
A2: Implementation instructions and documentation: Product documentation is a type of technical documentation that explains almost everything there is to know about a product or piece of software. Typically 5 documents should be available: Product specifications and system requirements; Instructions for product setup, installation and configuration; Specific use case instructions; Troubleshooting info; User documentation & answers to frequently asked questions.
All 5 documents are available--5 4 of 5 are available--4 3 of 5 are available--3 2 of 5 are available--2 1 of 5 is available--1 No documents are available yet--0
A3: Adoption by DIHs: The use case/solution will be well accepted by the DIHs if the component answers to the end user needs, is easy to use, to modify, to maintain and cost effective.
The use case/solution is well-known by the DIHs--1 The use case/solution is unknown to the DIHs--0
A4: User experience: User Experience refers to the feeling users experience when using a product, application, system, or service. It is a broad term that can cover anything from how well the user can navigate the product, how easy it is to use, how relevant the content displayed is etc.
UX testing has been conducted--1 UX testing has not been conducted yet--0
A5: Language: In European projects, user Interface (UI) are usually designed using the English language. In the case of replicability, it is obvious that the UI has to be adapted to the targeted country (even outside Europe).
The solution can't use other languages easily--0 The solution could use other languages--1 The solution is already supports other languages--2
A6: Societal readiness: The Societal Readiness Level https://innovationsfonden.dk/sites/default/files/2019-03/societal_readiness_levels_-_srl.pdf is a way of assessing the level of societal adaptation of, for instance, a particular social project, a technology, a product, a process, an intervention, or an innovation (whether social or technical) to be integrated into society. There are 9 levels (SRL) which help to qualify the solution, which one fits the best with your case:
SRL1 - Identifying problem and identifying societal readiness--1 SRL2 - Formulation of problem, proposed solution(s) and potential impact, expected societal readiness; identifying relevant stakeholders for projects--2 SRL3 - Initial testing of proposed solutions(s) together with relevant stakeholders--3 SRL4 - problem validated through pilot testing in relevant environment to substantiate proposed impact and societal readiness--4 SRL5 - proposed solution(s) validated, now by relevant stakeholders in the area--5 SRL6 - Solution(s) demonstrated in relevant environment and in co-operation with relevant stakeholders to gain initial feedback on potential impact--6 SRL7 - Refinement of project and/or solution and, if needed, retesting in relevant environment with relevant stakeholders--7 SRL8 - Proposed solution(s) as well as a plan for societal adaptation complete and qualified--8 SRL9 - Actual project solution(s) proven in relevant environment--9
Acceptance Replicability Factor score:
Regulation/Policy Dimension - 3 Questions (R1-R6):
The European Commission and Member states are elaborating a policy strategy that give a long term vision of the evolution of Europe that are translated into laws. It addresses Environment, economy, health, democracy, …).
The European Union is based on the rule of law. This means that every action taken by the EU is founded on treaties that have been approved democratically by its members. EU laws help to achieve the objectives of the EU treaties and put EU policies into practice. There are several EU acts that are applying to European citizens and industries. There are a number of regulations addressing the digital sectors that all products need to respect.
R1: EU regulation compliance: Looking to the EUR-Lex tool (https://eur-lex.europa.eu), there are 633 regulations that are applicable to the digital sector.
A check of compliance with European Regulations has been conducted--1 No check of compliance with European Regulations has been conducted yet--0
R2: National regulation Compliance: At national levels there are also specific laws that are not contrary to European legislation but could bring additional constraints.
A check the compliance with the National Regulations has been conducted--1 No check of compliance with National Regulations has been conducted yet--0
R3: EU Policy support: The political strategy of this European Commission is to set Europe on a path to successfully achieving climate neutrality by 2050, shaping our digital future, strengthening our unique social market economy, building a Union of prosperity, and making Europe stronger in the world. 6 priorities have been identified: A European Green deal; An economy that works for people; Promoting our European way of life; A Europe fits the digital age; A stronger Europe in the world; and A new push for European democracy. To what extent does your solution address these goals?
The solution is addressing all 6 European strategic goals--6 The solution is addressing 5 European strategic goals--5 The solution is addressing 4 European strategic goals--4 The solution is addressing 3 European strategic goals--3 The solution is addressing 2 European strategic goals--2 The solution is addressing 1 European strategic goal--1 The solution is not addressing any European strategic goals--0
Regulation/Policy Replicability Factor score:
The Replicability Factor for the use case based on the data entered above is: