Dynamic Behavior Modeling (DBM) is an innovative approach to understanding and simulating the dynamic behaviors of complex systems. By integrating principles from systems theory, artificial intelligence, and data analytics, DBM enables the creation of models that can accurately represent the interactions and evolutions of various components within a system over time. This methodology is particularly useful in fields such as engineering, biology, economics, and social sciences, where systems are often characterized by non-linear dynamics and emergent properties. Through DBM, researchers and practitioners can gain deeper insights into system behaviors, predict future states, and optimize performance in a wide range of applications.

...

...

...

...

...

...

I tried extending various existing information models, but ultimately couldn't find any that could solve these problems. I am committed to implementing a truly non-intrusive model, which I believe is the nearly only feasible approach to cope with highly complex industrial brownfield environments. Existing information models typically focus on static data representation and storage, lack the ability to understand and simulate the dynamic behavior of systems, and often fail to effectively capture the complex interactions among components and their time-varying dynamics, limiting prediction and optimization of system performance. Therefore, I decided to develop a completely new modeling approach to reflect system dynamics.

In my definition, a model is intrusive if it requires others to comply (including but not limited to fully understanding and learning it, or modifying existing product firmware or software) in order to be effective (including but not limited to standardization, communication, interoperability, etc.). Intrusive models are usually mutually exclusive with incompatible model systems. In my view, the vast majority (almost all) of existing industrial standards and models are intrusive.

A model is non-intrusive if it does not require others to comply, or even to understand it — it can operate transparently even to developers. Non-intrusive models typically require a middleware layer or intermediary orchestrator to function. Non-intrusive models must achieve compatibility with all existing intrusive models under the premise of loose coupling; otherwise non-intrusiveness is not achievable.

...

...

...

The code structure of this project is primarily based on JavaScript, so in terms of affiliation, it would fall under the OpenJS Foundation (which, as far as I know, is still part of the Linux Foundation). We haven’t engaged with the relevant foundations before, as this project is a general-purpose solution in the industrial domain and not fundamentally part of the JavaScript language infrastructure itself. We’ll reach out to these foundations based on your suggestions, but I’m not sure how well it aligns — we may first need to study their existing project landscape to see if there are any application-level projects related to our domain.

This project also includes some innovative implementations based on WASM (web-based physical engine). However, this part is not currently planned to be open-sourced. If that changes in the future, we would also consider reaching out to the Bytecode Alliance.

In the future, if we’re in a position to contribute to the development of WebGL-related standards themselves, we’ll consider reaching out to the Khronos Group (GPU/Web Standardization) and explore the possibility of becoming a member.

...