DRAFT NDT Architecture Principles

25 views
Skip to first unread message

dr.matt...@gmail.com

unread,
Feb 12, 2021, 5:22:24 AM2/12/21
to UK-ND...@googlegroups.com

Dear Colleagues,

A key part of the Information Management Framework is the Integration Architecture. The basic requirements for this were set out in the Pathway document. The attached draft document is a next level down document looking at the architectural principles that need to be considered.

 

We would welcome your comments on this document and discussion of any issues in this forum, or privately if you prefer.

 

Regards

Matthew

 

Dr Matthew West OBE
Technical Lead – National Digital Twin programme
https://www.cdbb.cam.ac.uk/what-we-do/national-digital-twin-programme

 

 

 

image001.png
image002.jpg
NDT Architecture Principles v1.3.pdf

Gamrat, Max

unread,
Feb 12, 2021, 5:45:45 AM2/12/21
to Matthew West, uk-nd...@googlegroups.com

Thanks for Sharing Matthew, a good read, I will discuss with the Water Data Taskforce at the next meet

 

With regards

 

Max

 

From: uk-nd...@googlegroups.com <uk-nd...@googlegroups.com> On Behalf Of dr.matt...@gmail.com
Sent: 12 February 2021 10:22
To: UK-ND...@googlegroups.com
Subject: [FDM] DRAFT NDT Architecture Principles

 

CAUTION: This email originated from outside of the organisation. Do not click links or open attachments unless you recognise the sender and know the content is safe.

--
You received this message because you are subscribed to the Google Groups "UK NDT FDM" group.
To unsubscribe from this group and stop receiving emails from it, send an email to uk-ndt-fdm+...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/uk-ndt-fdm/003a01d70128%24eedadf40%24cc909dc0%24%40gmail.com.

_________________________________________________________________________ This e-mail (including any attachments) is confidential and may also be legally privileged or otherwise protected from disclosure. If you are not the intended recipient of this e-mail or any parts of it please notify us by reply e-mail or by telephone on 01707 268 111 immediately on receipt and then delete the message from your system. You should not disclose the contents to any other person, nor take copies nor use it for any purposes and to do so could be unlawful. The presence of this footnote indicates: this email message has been tested for the presence of known computer viruses, unless the email has been encrypted (in part or full) wherein the email will not be checked for computer viruses. All incoming and outgoing emails may be monitored in line with current legislation. Affinity Water Limited (Company Number 02546950) is registered in England and Wales having their registered office, at Tamblin Way, Hatfield, Hertfordshire, AL10 9EZ. www.affinitywater.co.uk _____________________________________________________________________________

Gamrat, Max

unread,
Mar 12, 2021, 10:37:29 AM3/12/21
to Matthew West, uk-nd...@googlegroups.com, Bob Styles, Mills, Jamie - Xylem

Dear Matthew – what is your deadline on consultation for this document? I will aim to give some feedback from other participants of the WDTF in the next week or so, in the meantime some comments from me

 

  • Requirements overview: the use cases around resilience are plentiful in water and Ofwat would be interested to see how a system could be interrogated to provide feedback on asset performance and maintenance activities in near real time
  • Use cases (Page 8): do you want some potential use cases which could applied in the real world (I.e operational context in the water sector) if the answer is yes then some of those could be sent over, particularly with reference to “provide information to customers” or “support legal and regulatory requirements”
  • Service catalogue: how far are you with defining the catalogue?

 

Happy to discuss… you have support from water.

 

Max

NDT Architecture Principles v1.3.pdf

dr.matt...@gmail.com

unread,
Mar 12, 2021, 1:19:21 PM3/12/21
to Gamrat, Max, uk-nd...@googlegroups.com, Bob Styles, Mills, Jamie - Xylem

Dear Max,

With minor updates this document will be going out for publication in the next few days. However, the publication will be for consultation anyway. Making it available on the NDT-FDM list is a pre-publication review to improve quality and give those closest to us an early look at what we are doing.

We have not decided on the consultation period, but it will be at least a month after publication, so that would be the timescale to make comments within (unless you want to tell me that longer is needed).

The plan for next financial year is to develop one or more technology demonstrators to test out possible technologies to implement the architecture.

I hope that helps.

Regards

Matthew West

image001.png
image003.jpg

Ian Cornwell

unread,
Apr 15, 2021, 5:29:45 AM4/15/21
to UK NDT FDM
Sorry for the late response to this very interesting document. 
The technical content seems reasonable, and the recommended architectural concept seems reasonable as a target.

What I wonder is whether NDT would realise more benefit by a more iterative approach. A series of 10 tasks is identified but they are mostly to define details before anything actually runs. There is one early proof of concept (good) which comes before certain functional developments. Perhaps it is simply not the purpose of this document, but I would like to see more definition of the iterative path towards the target architecture, where perhaps some benefit could be realised through operational subsets of the architecture allowing some lesser version of NDT to operate. That would help manage the considerable risk associated with the full NDT vision.


matthe...@informationjunction.co.uk

unread,
Apr 15, 2021, 12:30:49 PM4/15/21
to uk-nd...@googlegroups.com

Dear Ian,

Thanks for the feedback, see responses below.

 

Sorry for the late response to this very interesting document. 

The technical content seems reasonable, and the recommended architectural concept seems reasonable as a target.

[MW] Good. That is what it was trying to do.

What I wonder is whether NDT would realise more benefit by a more iterative approach. A series of 10 tasks is identified but they are mostly to define details before anything actually runs. There is one early proof of concept (good) which comes before certain functional developments. Perhaps it is simply not the purpose of this document,

[MW] This should be (have been) set out in the Pathway document. The extent to which it is can be seen on Page 50 under Task 5. I can already see that things have moved on, but no plan survives first contact with the enemy.

but I would like to see more definition of the iterative path towards the target architecture, where perhaps some benefit could be realised through operational subsets of the architecture allowing some lesser version of NDT to operate. That would help manage the considerable risk associated with the full NDT vision.

[MW] Task 9 says: “An early proof of concept to validate the Integration Architecture components and their interactions. This will provide the basis to start producing open-source components to fulfil the Integration Architecture functions.”

So our approach will be to try to identify in the first place what already exists to meet our architecture specification with demonstrators/prototypes to evaluate what is available and establish what gaps there are that we need to fill. Our aim is that there should be open source software that can be deployed to meet the architecture requirements, though we plan to specify the architecture as a series of standards that developers can aim to produce software against.

 

I hope that helps clarify what we are proposing to do.

Regards

image001.png
image002.jpg
Reply all
Reply to author
Forward
0 new messages