opmerking werksessie adam/utrecht verwerkt

Author: NielsHoffmann

Diff for: respec/H2-approach.md

@@ -48,4 +48,9 @@ Explicitly bringing together stakeholders with a different level of maturity on
 
 The framework also aims to address 'lessons learned' from early adopters, so organisations embarking on a journey to implement LDT's can learn from the early adopters and hopefully implement those lessons more easily.
 
-Following from the critical questions some best practices are also documented in the following chapter.
+Following from the critical questions some best practices and lessons learned are also documented in the following chapter.
+
+### Maturity levels
+
+It is also important to note that an LDT solution can grow in maturity.
+While an initial solution can be small and limited in scope and functionality, it might grow over time to a more mature system.

Diff for: respec/H3-findings.md

@@ -2,7 +2,9 @@
 
 ## Lab questions
 
-The lab phase starts with the basic, fundamental questions. Why do I want a DT and to which guardrails and principles should the LDT adhere?
+The lab situation starts with the basic, fundamental questions. Why do I want a DT and to which guardrails and principles should the LDT adhere?
+
+For each 
 
 ### How do we avoid lock-ins?
 
@@ -12,42 +14,59 @@ __Best practices__
 
     Open standards are a way to enable systems to be interoperable and to avoid lock-in.
 
+- There is a clear difference between Open Standards, Open Licenses and Open Source. Adhering to Open Standards makes sure systems are interoperable. Open Licenses and Open Source are not technically necessary to enable interoperability, but might provide other benefits to the envisioned solution.
+
+- The dutch government implements a 'comply or explain' policy for certain standards (Pas toe of Leg Uit). This approach facilitates the adoption of certain standards to improve interoperability and compliance. Besides the 'comply or explain' policy, there is also a 'recommended' list of standards.
 
 ### How do we make sure our solution is re-usable?
 
 __Best practices__
 
 - Driven by and from use-case
 
-    Even from technical framework viewpoint, a socio-technical approach should be expected. 
+    Even from a technical framework viewpoint, a socio-technical approach should be expected. 
+
+__Lessons learned__
+
+- Having 'amabassadors' or 'champions' in your organisation that promote solutions and can enthousiastically demonstrate the use and adoption of LDT's is a huge benefit and success factor.
 
 
 ### How do we make sure our solution is interoperable with other organisations?
 
 __Best practices__
 
-- 'The web is the operating system'
+- 'The web is the operating system' 
+By this we mean that web technology is the fundamental approach to design systems, not only for the visualisation part, but also all other parts of the system, like storage and processing.
 
-    Modern architectures operate on a web-scale and can work in a distributed environment.
+__Lessons Learned__
+    Modern architectures operate on a web-scale and can work in a distributed environment, technologies like WebAssembly and memory optimized architectures make scaling systems a lot more feasible. 
 
 
 ### How do we create insights that are interpretable and well balanced?
 
 __Best practices__
 
-
+- documentation and clear definitions are key. Design systems in such a way that provenance is available and results are transparant. Be wary of 'black box' solutions where you do not have a clue how results are calculated.
 
 ### How can we create results in the short term, while staying relevant towards the future?
 
 __Best practices__
 
 - Work with the best that is available today (affordable, reliable, scalable & resilient)
 
+__Lessons learned__
+
+- Pay attention to agile development practices, deliverables should add value. But also take 'technical debt' into account. Be aware that system components need maintenance as well and reserve development time for a solid foundation.
+
 ---
 
 ## Studio questions
 
-The studio phase focusses on the capabilities. Which building blocks do we need to define.
+The studio situation focusses on the capabilities. Which building blocks do we need to define.
+
+<img src="./respec/media/capabilities.png" width="900">
+
+Main capabilities mapped to the Digital Twin Capabilities Periodic Table
 
 ### Which capabilities do we need to find, operate and interrogate our data sources?
 
@@ -93,19 +112,30 @@ __Best practices__
 
 By splitting the system in different building blocks (which are based on standards and interoperable interfaces) we make sure the system is flexible. We can use for example different visualisation solutions with a processing backend, and we can upgrade certain parts without needing to upgrade the complete system.
 
+__Lessons Learned__
+Critical succesfactors comprise of concrete, understandable building blocks. By adopting an agile mindset a roadmap can be realized in smaller steps which deliver value in their own rights.
+
+An area that needs further research revolves around quantifiable key performance indicators that are comparable accross different organisations. 
+
 
 ---
 
 ## Arena questions
 
-The Arena phase is all about the questions regarding the actual implementation of capabilities in applications and processes.
+The Arena situation is all about the questions regarding the actual implementation of capabilities in applications and processes.
 
 ### What kind of visualisation interface do I need to communicate my insights to the users? 
 Does it need to be a 3D viewer, or is a 2D or a chart sufficient?
 
 __Best practices__
 
 - A responsive, userfriendly 3D environment helps with the adoption of the technology stack.
+
+__Lessons Learned__
+
+- An accessible 3D environment can help very much in creating support in a community and explain proposed scenarios. Bear in mind that a 'high definition' simulated environment can also set certain expectations that you do not want to set just yet. Sometimes a generic, not too detailed scene is advisable to communicate the uncertainty around future scenarios.
+
+- Coordinate system alignment is not a given. While solutions might start isolated, once you want to combine different parts together it is imperative to make sure visualisations actually align by adhering to collective coordination system definitions.
 
 
 ### How does my data storage landscape look like? 
@@ -124,11 +154,29 @@ __Lessons Learned__
 What type of catalogue do I need, how proficient are my users in searching and finding products.
 
 __Best practices__
+The use of OGC and W3C standards to describe and expose datasources help interoperability, understanding and reuseability of those datasources.
+
+Specifically:
+- DCAT-AP (European dcat application profile) and relevant extension to the european profile. (GeoDCAT-AP, MobilityDCAT-AP, DCAT-AP-NL, ...)
+- OGC API records for describing catalogues 
+- SPARQL for querying linked data
 
 ### How do I make sure the different components in my landscape can actually 'talk' to eachother?
 
 __Best practices__
 
+Use OGC API standards to facilitate interoperability
+
+- OGC API Feature, Tyles, Maps
+- OGC API Processes
+
+__Lessons Learned__
+
+- While an architecture based on OGC API's is viable in many use cases, in more advanced scenario's involving for example high throughput 3D analysis and rendering Cloud Native and other standards are also applicable.
+Bear in mind though, that even then a separation of concerns between processing and visualisation is a sound architectural principle.
+
+- These interoperability questions do not only involve technical standards, but also require semantic harmonization. To be able to 'add' different metrics together, they need to be comparable and aligned. One way to address this is to standardize on common vocabularies.
+
 ### Which systems do I need to have in place to support my data governance processes?
 Make sure your technical system aligns with the operating model of your organisation.
 
@@ -148,7 +196,7 @@ Be aware that innovation is unpredictable a try to built 'just enough'.
 
 ## Agora questions
 
-The Agora phase is focussing on the implementation and deployment of LDT's in production. Focussing on wider use, stability, trustworhyness etc.
+The Agora situation is focussing on the implementation and deployment of LDT's in production. Focussing on wider use, stability, trustworhyness etc.
 
 ### How do I want my deployments to be rolled out to users?
 
@@ -173,5 +221,7 @@ __Best practices__
 
 __Best practices__
 
+### How do I make sure the maturity of my LDT is aligned with the maturity of my organisation?
 
+For an organisation to be able to benefit from the results from a mature LDT solution the organisation needs to be mature in digital change management as well. To be able to keep track of all the different components of a complex LDT system a configuration management system needs to be in place.
 

Diff for: respec/H4-conclusions.md

@@ -1,6 +1,6 @@
 # Conclusions, recommendations, next steps
 
-<img src="./respec/media/nldt-3hoek.png" width="900">
+<img src="./respec/media/Architectuur driehoek EngelsGeen achtergrond.png" width="900">
 
 Visualisation of the building block architecture.