Digital Twin Blockers – Your Priorities Please

[Lola Carbajal]

Wow @JoaoF! I couldn’t agree more 

 

[David Murray]

Hi Katie,

Thanks for sending me a link to the map. Unfortunately, the resolution is such that I can’t read it!

However, I have added some comments that may be duplicates (my background is defence, so maybe some of these don’t apply to other areas):

Data Issue:

A way is needed to store data so that it can be recalled as easily as possible against a whole list of search criteria. Creating the list of criteria is a significant task. Finding a way to store data, tagged with these criteria, is an even bigger task.

Governance and Guidance Issues:

Having an identifiable and accessible owner of issues is important to avoid spurious decisions being taken to overcome them.

Need and Want:

It is important for purposes of prioritisation of tasks by the supplier, that needs and wants are separated and ranked by the user, not the supplier.

Readiness:

The current state of the art helps to identify next tasks. In turn that helps to coordinate deployment of resources to bridge gaps. That’s important to maintain a good rate of progress and reduce nugatory effort. This comment could also apply to “Vision and Value”

I hope this helps!

Cheers,

Dave Murray

[Katie Walsh]

@Dave Many thanks for the extra blockers – we will include these on the board. When looking at the ‘map’ – the ‘jam board’, it’s on software called Mural –  to see the individual bits clearly just zoom in however you would normally do this (pinch the mouse pad, or right click or whatever). Or utilise the Outline function, then each bit of the board automatically zooms up when you hit each line of the outline. Annotated screen grab attached about outline function, if you have a mo, but you have certainly done your bit.

“/>

[Laurie Reynolds]

I had same  problem as Dave Murray,  the PNG was too coarse resolution to read individual post-it notes.

The summaries are useful but it would be good to be able to read individual post-its under a specific toipic, e.g. Interoperability for example.

Can you also post a link to the Mural document please?

I’m sorry I missed the event but 

[Laurie Reynolds]

On 29/09/2021 at 18:10, JoaoF said:

Readiness

‘Skills’ are a blocker when there is a lack of knowledge about new technologies, training for new roles required and clarity about how DTs are changing industry processes. 

‘Standardisation’ is a blocker when there is no framework and a lack of standards or standardised data structure.

‘Expertise’ is a blocker when the lack of it makes it difficult to know where to start and when DT advice or guidance sounds exclusive. 

I absloutely support the importance of interoperability standards but another important blocker is misalignment of public procurement methods and diffiiculty of arranging collaborative, risk sharing for problem definition and development.

[David Simoes-Brown]

Thanks DW. Very interesting additions.   Am I right in thinking that you have identified two new blockers as follows:

1. Misalignment of public procurement methods (with what please?) 

2. Lack of collaborative problem definition

Thanks!

 

David 

 

[Katie Walsh]

@Digital would be interesting to have your views on @Deeyesbee‘s question above here. No @s so I think you might not have seen it. 

[Laurie Reynolds]

On 20/10/2021 at 11:46, Deeyesbee said:

Thanks DW. Very interesting additions.   Am I right in thinking that you have identified two new blockers as follows:

1. Misalignment of public procurement methods (with what please? – see below) 

2. Lack of collaborative problem definition. Yes, although this is often easily resolved.

Thanks!

David

There are a number of examples of misalignment of public procurement and innovation projects

1)      SaaS business models pose problems for public sector CAPEX/OPEX financial budgeting

2)      Learning by ‘brilliant failure’ doesn’t sit comfortably in risk-averse cultures

3)      Procurement risk tends to favour tried & proven solutions and doesn’t promote the experimentation needed for successful innovation outcomes.

4)      Competitive tendering to obtain ‘best value’ makes innovation of new concepts and technology difficult.

5)      A view that new foreground IP and background IP used to develop the foreground should belong to the Purchaser.

6)      Data security and privacy concerns tend to be problematic in public-sector organisations. Cyber-security concerns often used as excuse for not engaging.

7)      Data quality often much worse than in equivalent industrial organisations, especially in asset intensive sectors where much of the asset infrastructure predates computer records.

😎      Lack of technical confidence necessary to judge the level of detail and compromise and relationship with risk. The ‘good enough for the problem we need to solve’ and ability to ‘start somewhere and see where it lleads’.

9)      Genuine systems complexity, especially in asset-centric organisations which lack the technical experience to take a Systems-thinking approach.

10)   Inadequate IT budgets and large desktop requirements which are not able to support modern browser technologies and security policies which exacerbate the problem.

 

 

[David Simoes-Brown]

Thanks again DW for the expansion of public procurement issues. Elsewhere we are looking at ‘open procurement’ from SMEs by local authorities and a lot of your points are echoed there.  

 

David