1. OUTCOMES OBJECTIVES FUNCTIONS ACTIONS TERRITORIES LOCATIONS MARKET SEGMENTS TIME LINESCHALLENGE IMPACT RESOURCESACTIVITIESCHANNELS RELATIONS PARTNERS CUSTOMERS TIME-BASED GAINS/PAINS VALUE PROPOSITION SOLUTION INNOVATION PROCESSES WORK FLOWS DISTRIBUTION CONNECTION PARTICIPANTS USERS TRANSACTION CONVERSION PERFORMANCE EFFECTIVENESS APPLICATIONS SERVICES INTEGRATION AGGREGATION NETWORKS CONNECTIVITY DEVELOPMENT MAINTENANCE RESPONSE AVAILABILITY RELIABILITY SCALABILITY 3 rd PARTY COMPONENTS INTERFACES CONFIGUR. ACCESS MOBILITY SUPPLIERS PROVIDERS INTERACTION SYNCHRON. USAGE ACCEPTANCE DATA SOURCES TYPES ALGORITHMS RULES STORAGE SECURITY HUMAN INTERACTION EVENTS SCHEDULES INFORMATION QUALITY MARKET CONTEXT MARKET CONTEXT HOW WHERE WHO WHEN WHY WHAT BUSINESS CONCEPT BUSINESS CONCEPT SOLUTION DESIGN SOLUTION DESIGN TECNOLOGY PLATFORM TECNOLOGY PLATFORM DEVICES & SERVICES DEVICES & SERVICES DATA SCHEMAS DATA SCHEMAS

2. The rows can be considered as different perspectives, different stakeholders, different scopes, or different levels of detail. IDENTIFICATION View: Stakeholder/investor Scope: Operating eco-system Level: Market strategy DEFINITION View: Owner/directors Scope: Business concept Level: Business model/plan REPRESENTTION View: Solution architect/design Scope: Systems logic model Level: Product/service plans SPECIFICATION View: Systems engineering Scope: Technology model Level: Infrastructure services CONFIGURATION View: ICT/clinical Developer Scope: Standards & interoper. Level: Service development INSTANTIATION View: Internal & external use Scope: Data modelling Level: Data management

3. The columns address different interrogatives or questions in relation to model representations. They indicate the primary elements of communication of the project both internally and externally. WHAT: Inventory Entities Assets Resources Items HOW: Functions Relationships Processes Activities Flows WHERE: Locations Place/space Networks Distribution Mobility WHO: People Customers Users Partners Responsibilities WHEN: Time Events/milestones Schedules Behaviour/queues Speed /cycles WHY: Challenge Motivation Need/problem Opportunity Improvement

4. Communicates business model and value proposition to interested stakeholders and targeted market. Communicates socio- economic challenge and public and private investment opportunities and priorities. Shaped by initial call and consortium response.

5. Communicates how system and service design provides unique and innovative solution to deliver performance goals within operating evnironment. Communicates business model, value proposition and operational needs to those responsible for solution design and implementation.

6. Communicates how the technology platform ( and its underlying components and data ) together supports the system solution to deliver the business value. These layers can be further sub-divided if necessary. Communicates how system and services will need to operate in terms of demands upon the technology platform.

7. Stronger public orientation – features / characteristics / results / performance / quality Stronger consortium orientation – process & technical engineering / internal organisation / intellectual property / quantity

8. Research proposal model Final research model A start-up model An enterprise model / / Technology modelling TRL 3 – experimental proof of concept TRL 4 – technology validated in lab TRL 5 – technology validated in relevant environment TRL 6 – technology demonstrated in relevant environment TRL 7 – system prototype demonstration in operational environment TRL 8 – system complete and qualified TRL 9 – actual system proven in operational environment Business modelling Customer discovery Customer validation Customer creation Value building