Jump to content

Setting Standards

Showing all content tagged 'Standards' and 'Regulation' and posted in for the last 365 days.

This stream auto-updates

  1. Last week
  2. Humanner

    Planning Golden Thread

    Can you tell me why every NEW houses same all across the UK? I do not saw in Europe similar boring and monotonous architect - where are the creativity and nice design in housing industry? Why cannot build individuals they own houses with unique plan?
  3. Humanner

    Digital twin Internship

    Hi Amir, If you interested in scope of social system innovation would be great to have a discus - transdisciplinarian public engagement. Cross sectorCultural heritage https://www.linkedin.com/pulse/citizen-social-science-age-alpha-generation-humanner-/ these are not directly relevant : TransportEnergyResidential buildingsCommercial buildingsIndustrial buildings
  4. Humanner

    Digital Twins Standards Roadmap Published

    Am I wrong or just I can't see any connection with a local council and / or community - COLLABORATION - in this Digital Twins program? Where is any democratic function for local consultation?
  5. Earlier
  6. Dave Murray

    Test Engineering and DTs

    I am considering starting a network for topics related to Lifecycle V&V (Validation and Verification) centred on Evaluation and Testing, and this message is to poll the level of potential interest. I imagine the network would offer the following: · A place for Test Engineers from different market sectors to share experiences and gain knowledge · Support for those areas where DT activity is low but growing, the Defence Sector is an example, to benefit from the experiences of other sectors Test Engineers have a mix of technical and customer skills that are central to successful project implementation. The DT concept provides a lifecycle project-thread that provides Test Engineers with an unprecedented opportunity to exercise their skills. Maybe finding a way to maximise this opportunity might also attract more people to the career, and be a way to improve recruitment into the world of Engineering? If we launch this Network, would you consider joining it? Dave Murray
  7. The Good Homes Alliance seeks to drive up standards, performance and quality in new homes built in the UK. We have developed a concept built upon existing IP that digitises an assured performance process to enable a comprehensive outcome that will enable net zero (and other desirable outcomes such as health and wellbeing of occupants) to be met and verified. This concept would address a number of issues currently being discussed and deabted by the investment/finance/insurance/warranty sectors and would upskill design teams and constructors because of the built in on demand training that accompanies the app-concept. The concept is called NetZeTT (Net Zero Tool and Training) and has an existing set of project partners, what it doesn't yet have is funding, if any potential funders are interested in this project please reply.
  8. Hi @besse the Digital Twin Toolkit can help with this, let us know if you need any more help
  9. Firstly, thank you to everyone who joined the concepts and principles standards workshop on the 11th of February. With 70+ attendees and a wealth of engagement, I feel that we managed to make some real progress in establishing the DT Hub community's views on the future BSI Flex standard. As mentioned during the workshop, the slide deck presented will be given to the technical author and advisory group for consideration, acting as a seed for further standardisation development. A copy of the slide deck used with the comments and changes incorporate is available here. In this article, I wanted to highlight some of the key insights that came from the workshop as well as provide you with the ability to keep track of this work as it progresses. Scope: Generally, the community appeared to be content with the draft scope, which had used the scope of ISO/DIS 23247-1 (Digital Twins for Manufacturing) as its basis. The comments received focused on types of assets, systems and processes which should be highlighted. Of particular note was the desire to include information assets, natural assets, and safety and control systems which have all now been included. There was also a strong desire to highlight the relationship to information and information management. A comment has been included to ask that this is done within the introduction as opposed to the scope. Concepts: After I had introduced a series of different conceptual diagrams, I was surprised to see a preference for the figure within ISO/DIS 23247-1. However while this figure appeared to be preferred, several attendees pointed out the need to articulate the scalability of the built environment; with mention made of effective visuals previously used by @Mark Enzer to explain the relationship between components, systems, and systems of systems. In addition, previous comments around the need to highlight the natural environment as a distinct facet were echoed. This led to the introduction of another figure from Flourishing Systems which highlights the built environment as economic infrastructure, social infrastructure and the natural environment. Principles: Having discussed the overall concept, we moved to the principles that should govern digital twins for the built environment. Using the original Gemini Principles as a basis, the community did not challenge the existing principles but did suggest a potential 10th, Provenance. Distinct from Quality, provenance would focus on the origin of information to enable someone to assess its potential accuracy or trustworthiness. Terminology: After discussing observable elements and references we concluded with Terminology. Using the existing terms on the DTHub Glossary as a basis, the community suggested several additional terms such as: interoperability, asset, system, process, system of systems, semantics and syntax. In addition @Ramy, a Northumbrian University PhD student, shared a figure and thoughts around Digital Twin uses and a “DT uses taxonomy” which he has also published on the DT Hub, here. It is this sort of engagement that makes the DT Hub a community, thank you. As I mentioned, the outcomes of this workshop will be fed into the development of BSI’s Flex standard around digital twins for the built environment. And there we have it. Please feel free to keep the conversation going by commenting below or directly on the slide deck. Stay tuned on the DT Hub for more news, updates and ways to get involved in the development of BSI’s Flex standard.
  10. The idea of a Digital Twin [DT] needs to advance in a standardized and formal manner. As @DRossiter87 pointed out, this is necessary to "support the consistent adoption of, and interoperability between, digital twins for the built environment within the UK" To aid in this endeavour, it is useful to delineate the difference between the following terms: “DT General Use Case” [GUC]: a very short sentence, possibly consisting of two or three words – ideally a verb followed by a noun – ultimately concerned with the brief and blunt statement of the central business aim that is motivating the use and implementation of a DT, e.g., ‘optimize traffic’. “DT Use Case Scenario” [UCS]: a documentation of the sequence of actions, or in other words, DT-user interactions executed through a particular DT case study or an actual DT real-world project. “DT Use”: a typical technical function or action executed by any DT throughout the course of any UCS. Accordingly, the DT uses are seen as the standard building blocks by which a standard common language can be founded. Such a standard language, which can possibly be machine-readable as well, can be used in documenting and detailing the DT-user interactions in a standard format to facilitate their publishing and sharing of knowledge. Below is a figure of a “DT uses taxonomy”. It is made up of three distinct hierarchical levels, these are respectively: ‘Included Uses’ containing four high-level cornerstone uses that are, besides rare exceptional cases, included in and executed by almost every DT throughout any UCS (i.e. Mirror, Analyse, Communicate and Control); ‘Specialized Uses’ including special forms of the Included Uses, where each specialized use enjoys unique strengths suitable for specific purposes; and “Specialized Sub-Uses” at the lowest hierarchical level of the taxonomy, which further differentiates between variant types within a Specialized Use at the higher level by virtue of very fine inherent variations that distinguish one type from another and thus, enhances the DT’s practical adequacy in dealing with alternative contexts and user specifically defined purposes. The table below include a formal definition of each DT Use. DT Use Definition Synonyms 01 Mirror To duplicate a physical system in the real world in the form of a virtual system in the cyber world. Replicate, twin, model, shadow, mimic 1.1 Capture Express in a digital format within the virtual world the status of a physical system at a point of time. (Usually, offline DT) collect, scan, survey, digitalize 1.2 Monitor Collecting information related to the performance of a physical system. (Online or Offline DT) Sense, observe, measure 1.3 Quantify Measure quantity of a physical system’s particulars, instances or incidents. (Online or Offline DT) Quantify, takeoff, count 1.4 Qualify Track the ongoing status of a physical system (Online or Offline DT) Qualify, follow, track DT Use Definition Synonyms 02 Analyse To create new knowledge and provide insights for users and stakeholders about a physical system. Examine, manage 2.1 Compute To perform conventional arithmetical calculations, traditional mathematical operations and functions and simple statistical techniques like correlations Calculate, add, subtract, multiply, divide 2.2 Mine To uncover, identify and recognize the web of interdependencies, interconnected mechanisms, complex processes, interwoven feedback loops, masked classes, clusters or typologies, hidden trends and patterns within the physical system. Learn, recognize, identify, detect, AI, ML, BDA 2.3 Simulate To explore and discover the implications and possible emerging behaviours of a complex web of interacting set of variables. 2.3.1 Scenario To find out the implications, impacts or consequences of implementing pre-defined scenarios (akin to non-destructive tests) What-if, evaluate, assess 2.3.2 Stress-Test To identify the scenarios that may lead to failure or breakdown of physical system (akin to destructive tests) Test, inspect, investigate 2.4 Predict Concerned with futures studies 2.4.1 Forecast to predict the most likely state of a real system in the future, by projecting the known current trends forward over a specified time horizon. foresee 2.4.2 Back-cast To question or prove in a prospective manner, how the physical system is operating towards achieving the pre-set aims and goals. manage, confirm 2.5 Qualitize Enhance and improve the quality of the outcomes or deliverables produced by an intervention in real world. 2.5.1 Verify Verify conformance and compliance of physical system with standards, specifications and best practice. Validate, check, comply, conform 2.5.2 Improve Inform the future updating, modifying or enhancing the current standards to be in better coherence and harmony with the actual operational and usage behaviours and patterns. Update, upgrade, revise DT Use Definition Synonyms 03 Communicate To exchange collected and analysed information amongst stakeholders. interact 3.1 Visualize To form and vision a realistic representation or model of current or predicted physical system. review, visioning 3.2 Immerse To involve interested stakeholders in real-like experiences using immersive technologies such as VR, AR and MR. involve 3.3 Document Document and represent gathered and/or analysed data in a professional manner and technical language, forms or symbols. Present 3.4 Transform To modify, process or standardize information to be published and received by other DT(s) or other DT users (e.g. a National DT) or overcome interoperability issues Translate, map 3.5 Engage To involve citizens and large groups of people including marginalized groups in policy and decision-making processes. Empower, include DT Use Definition Synonyms 04 Control To leverage the collected and analysed information to intervene back into the real world to achieve a desirable state. Implement, execute 4.1 Inform To support human decision making throughout the implementation of interventions in the real world. Support, aid 4.2 Actuate Using CPS and actuators to implement changes to physical system. Regulate, manipulate, direct, automate, self-govern Standardised set of ‘DT Uses’ can help avoid miscommunication and confusion while sharing or publishing DT Use Case Scenarios and their content explicitly explaining the 'know-how'. It can also support the procurement of DT services by ensuring the use of a one common language across the supply chain and stakeholders. Al-Sehrawy R., Kumar B. @Bimal Kumarand Watson R. (2021). Digital Twin Uses Classification System for Urban Planning & Infrastructure Program Management. In: Dawood N., Rahimian F., Seyedzadeh S., Sheikhkhoshkar M. (eds) Enabling The Development and Implementation of Digital Twins. Proceedings of the 20th International Conference on Construction Applications of Virtual Reality. Teesside University Press, UK.
  11. HenryFT

    Confused buyers don't buy digital twins

    I tend to agree with you Vladimir, because the last thing we need is mis-selling in this area in the way that we've seen BIM wash, but I know that Michael Grieves would argue that a virtual model for simulation purposes was the first digital twin at NASA (that was then used for managing the asset once it was in space). So perhaps we're in danger of being too focused on the built environment where we have developed our own terms for 3D models with embedded information aka BIM which has its own problem, what is BIM?! The lines are very grey and Digital Twins could well have the same issue. Take a listen to what Michael has to say. It's a tricky subject, because we do seem to be diverging from the international vision of digital twins, but as the man says himself 'it's an analogy you know'
  12. DRossiter87

    Consolidating Concepts: Gemini Principles

    Hi @tombartley, thank you for this. I'm glad you support the general premise, and I agree aspects like Applications (Uses) and Observable elements are important. The goal of the workshop on the 11th is to test/challenge these headings with the community so Benefits may fall out. As I mentioned in the previous post, I've (shamelessly) taken the clause structure from the manufacturing standard and adapted the headings to suit. As the scope relates to an overview and principles standard (like ISO 19650-1) it behaves more like a guide to inform further standardization as opposed to a code of practice or a specification; meaning that a clause on benefits *could* work as guidance can include both recommendations as well as statements of fact. However, just as Jeff Goldblum says in Jurassic Park: I think it'll depend as to whether the benefits we can identify relate specifically to the applications, or are more generic benefits. Fully agree that the standard needs to formalize terminology. This has been a strong theme from the CDBB team too.
  13. simonvaux

    Consolidating Concepts: Scope

    Same here! Error messages, so can't access the docs
  14. James Harris

    The National Digital Twin Legal Implications

    @James C, A very astute observation and excellent feedback. Thank you. You are entirely right that there is a story that needs to be told on how the emergence of an NDT works outside of the technical narrative that we have chosen to lead off with; keeping fairly close to home in recent times, to ensure that the message has the right starting point. There are of course significant areas of impact on areas such as finance and underwriting, where the availability of better decision making and risk visibility mechanisms could do lots for the reduction of WACC/hurdle rates for infrastructure investments, or in reducing project or through-life premiums. The potential impact on financial liquidity, investor confidence, project pipelines and therefore employment and ultimately, national economic output, should be clearer. In fact, the contributors to the roundtable raised this point on several occasions, and we will certainly be expanding our engagement in these areas in the next phase. Similarly, the social value of this improved transparency, in terms of how it can create new or improved ecosystems of digital services for the general public, is an interesting angle. How we plan for, and control this secondary market (or whether we should at all) is a multi-headed problem. A necessary one to start talking about though. There are parallels to be drawn in the way the energy sector is beginning to manage the emergence of its own secondary data market, enabled by technology such as the Smart Meters that many of us now have in our homes. We're working closely with Ofgem and others to learn how their own governance arrangements are maturing, to inform our thinking. The legal roundtable was the first step to pointing out where we had gaps. You are right that it does address threat rather than opportunity as a priority. We were looking primarily for the big hairy problems which might have caught us by surprise. There were also many areas of opportunity raised that were redolent with potential to explore further, but we chose to focus on the potential blockers this time around. We've yet to solidify our activity plan for the legal sub-stream in the next phase, but I would be highly supportive of your recommendations. A long winded response, sorry. @Sarah Rock, @Miranda Sharp, have I missed anything? James
  15. It is proposed that the Information Management Framework (IMF) for the creating of a National Digital Twin will consist of three technical elements: the Foundation Data Model (FDM), Reference Data Library (RDL) and Integration Architecture (IA). The IMF will underpin the creation of an environment which supports the use, management and integration of digital information across the life-cycle of assets. The IMF will also enable secure, resilient information sharing between organisations and will facilitate better decision making across sectors. The National Digital Twin Programme has initiated work investigating this approach with a thin slice of the IMF for the Construction Innovation Hub, to support the development of CIH’s Platform Ecosystem. This thin slice of the IMF is called the FDM Seed. The FDM describes basic concepts such as space-time which are attributable across all areas of our industry. By developing this, the FDM provides a way to explore relationships between these different areas. The FDM Seed is an inception of the above concept and is proposed by starting smaller and watching the development grow - similar to a seed. The first steps of the FDM Seed project is to survey the landscape, to investigate what ontologies and Data models are already in use out there, what they can do, and their limitations, and assess what tools may be useful as a starting point for the FDM and the RDL. The starting point for the FDM is a top-level ontology, this contains the fundamental and generic types of things that exist and the fundamental relationships between them. The survey of Top-Level Ontologies (TLOs) uncovered a surprisingly high number of candidate TLOs with 40 being identified and reviewed, many more that we could have imagined. Fig 1.General classification of the TLO – taken from A Survey of Top-level Ontologies The final survey of top-level ontologies is, we think, the first of its kind. We were looking for an ontology that was rigorous, simple and with sufficient explanatory detail to cover our scope of interest, which is very broad. There are roughly two groups of TLOS, Foundational and Generic: The foundation are rigorous, principled foundations and provide a basis for consistent development and would be suitable for the FDM. The Generic tended to generalisations of lower level, rather than principled and lack a principled basis for extension, and therefore not suitable for the structure of the FDM, though likely to be use for the FDM generic lower levels. An RDL provides the classes and properties to describe the detail of an asset. The survey hoped to identify the most prominent of Industry Data Models and show the best starting point for the IMF RDL. There are many different RDLs in use across sectors. For the purpose of the FDM seed a limited analysis was carried out, but the list is open, and more candidates will be added for future consideration. Surveying and analysing the most commonly used RDLs will mean we are able to give guidance to organization when mapping their existing RDLs to the NDT. Next steps The Survey papers have now been published. We encourage you to engage with the National Digital Twin Programme to find out more about the approach, the results of the survey and the Assessments of the TLOs and Industry Data Models & RDLs. You can find these resources under the 'Files' tab. The Programme is now in the process of gathering their recommendations for the TLOs to use to start the work on the FDM Seed thin slice. We anticipate basing the FDM development on one of the TLOs, bringing in elements from others, based on the survey & analysis.
  16. If you missed the free webinar last month on how to generate OIRs and critical success factors from an executive strategy join me again on Monday morning. its 1.5 hrs of presentation and 1.5 hrs of workshop. please feel free to attend just the presentation. There is an optional session the following day taking in Function Information Requirements and their impact on delivering digital assets. Sign up and attend what you can! https://event.on24.com/wcc/r/2513815/F72E835712666BB4969CC328281F134D?partnerref=SocialMedia see you all then Iain
  17. HenryFT

    [Very very draft] HE DT Policy

    oh man this is big, I've skimmed it, but I'll come back to it in earnest soon @Ian Gordon. From my first pass the tone is right and it doesn't read like policy statements of old that sought to write in stone eternal truths and irrefutable facts with thou shalts and orders from on high, but ultimately were trying to nail jelly to the wall. This reads like something that clearly sets out the philosophy, the context and the direction of travel for digital twins in HE that understands the fluid nature of the situation and is ready to adapt to that.
  18. Ian Gordon

    What is the difference between Twins & BIMs

    I stole a lot of this content and wrote the following: Our definition of a Digital Twin is as follows: A Digital Twin is a digital representation of a physical thing (and its operation) that one can query. This definition helps us to distinguish between the concept of a Digital Twin, and the more established practice of BIM. The key differences are: Digital Twins can and should be part of the construction phase, but the focus of their use is on the operation of existing physical assets (e.g. the 99%+ of assets that are not currently under construction). Within our organisation (and the wider industry), there is often a loss of data capability as projects move from construction to operations as operators have typically been unable to exploit BIM products. By designing our construction models as nascent Digital Twins we have the opportunity to define the data and logic required to operate an asset at the start of the lifecycle, and ensure that the models we create during construction have operational value. The emphasis on being able to query Digital Twins is important. A Digital Twin should not be a static representation of an asset, it should reflect the logic of that asset in operation. This means that Digital Twins need to expose not just the material properties of an asset (e.g. location, dimensions, materials, etc.) but also the business logic governing that asset (e.g. how we as the infrastructure owner can intervene on that asset to change how it performs). This allows Digital Twins to enable better organisational decision-making through simulation and 'what if' scenarios. In order to realise the two points above, the data schema underpinning Digital Twins is necessarily more complex, and more focused on relationships rather than properties. BIM data standards, such as COBie or Uniclass focus on the hierarchies of assets, and their properties (e.g. "span belongs to bridge and is made of steel"). Emergent Digital Twin data models (including our own Highways England Ontology) capture not just the properties of assets but how the relate to their wider environmental and operational context (e.g. "span is corroded by road salts, damaged by vehicle incursions, is maintained when the flange has 20%+ corrosion, and supports a flow of 50,000 vehicles per day travelling on the M25 (as well as a broadband internet cable) causing significant safety and KPI impact in the event of failure"). Creating these data models demands the creation and maintenance of a deep 'knowledge graph' of the organisation.
  1. Load more activity
  • Create New...