DEV LAB Live-Coding mit Nutzer&Nerd – Modellieren mit uuwemo.com

[00:00:07]Welcome to the wonderful world of a well- maintained business process.

[00:00:11]We model, automate and optimize business processes, and here is your host. Hey everyone, I'm Mörk, I'm Processor versus Process Patch, the show for process rescuers and all those who want to become one, and we're changing the world of modeling tools.

[00:00:30]With UVMO, we plan to create a wonderful tool that anyone who values understanding and modeling their processes can use.

[00:00:44]We create Business Process Entertainment. That means someone has to provide entertainment, right? Someone has to talk and tell stories.

[00:00:51]In most cases, the user does this, not usually. Yes, in other cases it's obviously someone else who's talking. And we know the person who is familiar with it and who is contributing intensively to enriching this world with a wonderful tool. There he is. Have a wonderful good day. I close my eyes again. It's nice that I can be there as always, or as regularly as I have been lately, but it's fun.

[00:01:26]Yes, he hears it and has to work intensively just before his vacation. We have two more shows this week, you know?

[00:01:33]Only one left. It's already running.

[00:01:35]So, here it is, therefore everything is fine.

[00:01:37]I've already got that sorted. That's already taken care of.

[00:01:39]That's almost done, right? Exactly. But you're still having fun. I always find it really pleasant how optimistic and positive you are. So, my, um, you can ask people who know me. Yes, I'm more the type who says, "Let me think for a moment about how to phrase this."

[00:02:04]He's dead. He's 100% dead. There's no doubt about it. That's the way it is. Yes. Or half empty, right? As they say, everything is half empty for me. I always see it as half full, and there's still room to go higher.

[00:02:20]Well, you have a truly remarkable optimism that you display in every respect. I find that quite remarkable. I cannot agree with that in every respect. Yes, well, I am definitely a skeptic as well.

[00:02:33]Yes, I admit that. But that's okay. Yes, one must be allowed to have doubts sometimes, so yes. Yes, but you also need to find people who will cultivate this optimism. Yes, simply to restore balance.

[00:02:47]I like it.

[00:02:48]Yin and Yang and Jong and Jung.

[00:02:51]Oh, exactly. A purple hat, a pink hat, and then it'll be fine. Exactly.

[00:02:55]So. So. That's how it works.

[00:02:58]Ah, I just need to quickly go into the next room and get something. I'll be right back.

[00:03:04]I do not know what you mean. I do not know what you mean. Um, like this. Um, we need to summarize. Yes, you always assume that everyone watches all the shows. Uh, let's do a quick recap.

[00:03:16]Yes, should I take over that again, or should I do it myself? You do it. I'll assume what we've done in the meantime.

[00:03:23]I'll pick up the ball and then we'll talk a little bit about it.

[00:03:25]OK. So, for anyone who is here for the first time, let me tell you, the world is being changed here. Yes, period. Um, I made a wish. I was reminiscing about old times and said, oh, those were the days. Yes, back when we had a team-based modeling tool, uh, that we could just use and uh, model, save information about models, and discuss online with people what makes this model special and what the problem is.

[00:03:57]And um, the product was called Kavemo, yes, that was the Kamunda Webmodeller. Great guys who dealt with that back then.

[00:04:07]Yes, very likeable colleagues, uh, and very intensely dedicated colleagues. Yes, so greetings again. It was great cinema. So. Uh, this product has transitioned into a product—uh, the name of which I've forgotten—but we want to, we have, we are preparing to bless the world with a product called UWMO. Yes.

[00:04:35]Um, I submitted this request and the nerd, well, the nerd is crazy enough to go along with something like that and he said: "Oh, sure, we can do that." So, and since then we've been following this in, I don't know, which session is this? The fourth one. Fourth, I think. I think it's the fourth one now. Yes, I think so too. Yes, in the fourth session we will follow the history of this project. This led to an idea that included the following: "Oh, what if we developed an open source modeler from this project, which would provide the basis for teams to work with it?" Yes, the world needs an open source modeler. Yes, there are others, but this is our idea. So. Uh, and um, that fell through, and the idea of, um, doing the whole thing here in the stream, how do I put this now? Um, to accompany. The accompaniment is documented. Exactly. Exactly. So there are some crazy people around. Um, we haven't yet asked your colleague, who is currently on vacation, if her name may be mentioned, but we have it in mind. She has created things that we have already shown in the last sessions. So, and today we're in our fourth session and, uh, we want to do something. Okay, I'll hand it over to you now. Yes, so what did we, uh, plan to accomplish today?

[00:06:05]Um, what does "intended to do" mean?

[00:06:06]Firstly, we have given the website a further polish in the meantime.

[00:06:10]I'll show you in a moment. We've thought of a few more features, a few more marketing things, but the big thing we've prepared for today is the discussion about architecture and roadmap. So, in other words, how do we build, where do we start, how do we build now? We discussed and considered this a bit last time, didn't we?

[00:06:30]Frontend, backend, database, and so on. There were various questions and answers that we had to ping-pong together a bit.

[00:06:37]I've been thinking about this in the meantime, and um, I'd just like to go over the roadmap via screen sharing with all the people who are already watching us, and then we can talk a little bit about the architecture and see where the session is headed today.

[00:06:55]Exactly, exactly. We always improvise. We are, uh, well prepared, so you are well prepared and I am not.

[00:07:01]And then we'll talk about what we haven't prepared, or what you have prepared, let's say. Um, the root map was already discussed last time. Yes, you said, oh, we haven't done that yet, but today we're focusing on the roadmap story, because we're focusing on the content of the roadmap, where we've thought about how we want to approach development now, what our rough building blocks and cookies look like. Mhm.

[00:07:25]And um, we're going into all of that today. Yes.

[00:07:30]Uh, that's also important because, um, some people think I also received mail, yeah, some people think we're just joking around here, yeah, but we're really serious about this, right? Well, that 's definitely it.

[00:07:42]Okay, good. Should I share this, or, because now bring me to the "Bring my screen on screen" or whatever it's called. Exactly. Is this a website you know?

[00:07:52]Is it on the right, or do you want to go to the top left, uh, away? slip away. What do you have there? Is that possible? I'd also be happy to stay next to you. That's fine. Yes, we are familiar with the website. I think the last time we discussed this, I don't even remember, was when we finished the submit feature request topic.

[00:08:10]No, we didn't really show that. That was what Kumakkasten was.

[00:08:13]Exactly, the comma. So, we've now created a roadmap. This means, however, that we have not yet decided everything down to the last detail, what we will do, where we will do it, how we will do it, and so on and so forth.

[00:08:30]Yes, if someone has ideas from their past experience that they would like to see included, we welcome the input. Either you can provide an email address; we have marked it as optional here. You don't have to out yourself by saying, "I have a crazy idea," but you can out yourself because we would be happy to talk to you about the idea. What's the background, huh? So, to make sure we understand it better, because I have two follow-up questions, but otherwise you can just put in a 2000-character description here and tell us what the idea is, so to speak, and then we can consider how to include it, whether to include it, when to include it, and so on, in order to integrate it into the roadmap. Wait, I have another question for the advice column, uh, or rather, a question for you. Can you think of any people one could approach directly? Well, one person comes to mind right now. Um, so I don't mean to name anyone specifically, but I just wanted to know if you actually know any people from the Cavemo community who were heavily involved in making the product a reality back then?

[00:09:42]I could just say we write to [email protected] and see. No no no.

[00:09:50]But that's not something you do. No, you don't do that. No, you don't do that. We, well, theoretically, one could, um, yes, I know two, three, four people one could approach, where one could just, uh, exchange information, uh, chat, um, whether they are also no longer there, the ones we approach there, then only for, well, in case Kamon is involved or something, right? And can we mention some names, or do you not want to mention any names? I would have to get it out now. I know that there were a few people involved in the frontend team at Kamunda who put a lot of work into it, did really good work, and basically just had fun doing it. It would be interesting to interview them to learn about their thoughts or the history. That 's an idea we discussed before, I think, just to see if we could take away things from it that we need to consider, should consider, or whatever.

[00:10:48]OK.

[00:10:49]And on that side, I'll go on the offensive. You know me, I'm the one who always barges in and says things that you shouldn't really say.

[00:10:58]Volker Gerserbeck. Yes, well, um, I'm a product manager for KWMO.

[00:11:05]I'll raise my hand. Yes, we can talk about what you're currently doing. Yes, and maybe yes, so it's an invitation Volker, yes, you're welcome to come here. I know that it's very insightful when one talks to you. Yes, well, a lot of um, um, a lot comes across. Um, firstly, I'd like to know what you're currently doing, since you're no longer with Kamunda, and secondly, um, can we talk about old times? So, we had a fantastic, um, Kamunda 7 Community Edition party. Maybe we can celebrate something like that sometime – um, we're all thinking of Kavemo, um, um – and then we can draw some positive conclusions for the next generation of tools. Okay, there you have it. May I say this now? The advice column is here. What else do we have?

[00:11:56]Ah, we've now included some of the parts that we consider important. The topic of on-premises solutions, Linux, Docker, AirGap and so on will come later, right? Active Directory, all the features we've already mentioned in general, but which we also consider absolutely necessary in this situation, are simply written down so that you can see it again and don't forget what we want to build here. And the big feature, which we now have, or rather, the big feature, but the major information expansion, we just deployed 5 minutes ago. Is the roadmap history just a way of saying we're starting from scratch, then? This topic exists in Germany too, right? Uh, in Germany, in German, we want to create a stable platform, right, into which we can then model BPMN processes. An important point you mentioned last time, right? We want our own BPMN, or just like in the intro, the modeler is the linchpin. Um, a few ideas have come up in the last few days where we need to, um, tell me where we need to adjust it, where we need to optimize it, in order to use it as a quasi- element in this UVEMO application, but also as a standalone situation for anyone who needs a modeler in their application, especially since we also want to offer it as a desktop version. Yes, please. So, a quick question. Yes. To say no, not "Mr. Teacher". You are the teacher. I am the one, yes, I am the knowing one, only just because you did it so beautifully, you know?

[00:13:32]Yes, exactly. That's great, you recognize it. Um, um, modeler, yes, so that you understand. Yes, the modeler will be available as open source.

[00:13:44]Yes, it will be a separate software, so to speak.

[00:13:47]Exactly, because the question comes up again. Uvemo is, uh, a modeler plus teamwork skills, let's put it that way. Yes, simply put.

[00:13:56]This is the very flat, but correct version. Correct. Exactly.

[00:13:59]Very flat. Yes, I am a seller. Yes, very flat. Hello. Yes, like that. Yes, it's good that we're talking about it.

[00:14:07]So. Um, and then and then it's also open, so both the desktop version and the desktop version are open. Yes, well, there are those who say: "Okay, I want to have all of this on my computer and, uh, I want to model it on the desktop." Yes, that's what you know from other models, but also—and I find this very remarkable— the possibility of using the Free and Open Source Modeler, is it actually called Ubato Modeler or what is it actually called?

[00:14:36]We haven't really thought about that yet. That's one point, but at the moment he's the modeler, so to speak, afterwards, but that the model can also be embedded. So, many people make it very easy for themselves, yes, they say: "Okay, we now have our own modeler and then they take BPO and then they just slap it in there, right?" Well, that 's quite a common principle. It 's stable and good, too. It's been going on for over 10, 12 years, uh, it started in 2026, I think, 2013, so 13 years, I think. Yes, and then roughly a year, plus or minus, knowledge, ideas, and development flowed into it. Well, things have been locked in there for a really, really long time. Less so in recent years, but that's still the case. Yeah, I'm not saying it's a legacy product, not me. Yes, well, I'm just saying something new is coming, yes, something different is coming, or something is coming that we'll put alongside it, let's put it that way, but will basically move in the same, um, same atmosphere. Yes, so you can embed it, you can use it as a variant, but you can also, um, yes, okay, good, I understand. Nice. So, now for phase 1.

[00:15:46]Exactly, phase 1 is about us simply thinking about it, so building the system, right? So, to put it another way, get the model ready so that it becomes open source now. That will happen in the next two weeks. I'm on vacation, so since dear Mirko wants to cut this ribbon or press the button for publication, we either have to do it from somewhere in Tuscany, Italy, or we'll do it sometime after that, right? Well, but we will have to prepare it, there are still a few steps to take, um, so that we can do the whole thing. But I'm really looking forward to it, I'm also looking forward to this moment, because, well, I have to be honest, I experience this with Operation, I experience this in many other projects, giving something back where you yourself have benefited for years is just cool, and that's why this is a [ __ ], this is a [ __ ] historic moment. So that's exactly what I definitely want to experience.

[00:16:43]Firstly, because I haven't experienced it yet, and secondly, because I truly consider it a historic moment. Yes, so cutting the red ribbon there, saying, here is the world. Yes, that's definitely an experience I'd like to treat myself to. So, in that sense, go on vacation, go on vacation. Yes, but we need to tackle this. Exactly. Yes. And um, then a few other things come in, right? Like XML validation, Andu Redo, we already have some of those things, which we might need to check again in the context of the system, and so on, but what we then build is the basic system. Well, we use a postgrade database. This is a decision I have made for myself. Uh, Linux support, sure, but we've also received internal feedback that we can of course support Windows, but because we opted for Docker Deployment Docker Compose, this will be able to run virtually anywhere, whether it's a Windows Server or a Windows Desktop device later on. You can probably try that out at some point and say, okay, we'll consider whether we have some kind of test package where you can sneak in for a few days. Um, and you could then run that anywhere you have Docker installed, right? Then we have the topic of automatic saving.

[00:18:05]It's kind of like, I build something, I model something, and then I want to save it here at that point in the situation.

[00:18:14]What I find really interesting is that you don't go and say, "You're not really you, are you?" Uh, I'm announcing a marketing message and saying, we're now doing, yes, but that you paint a very realistic picture of, uh, software development, the way a nerd would. Yes. um and also gives um a realistic picture of the development um really um to the people so that they can assume, okay, he's not promising me the moon, but he knows exactly uh what needs to be done and what is realistically feasible in the different phases. I'm good. Exactly, exactly. Uh, yeah, yeah, I like it. Exactly. So, we're now, uh, getting to the topic, which isn't entirely clear here, is that we obviously need a certain setup, which I haven't included here. We opted for a two-stage, or rather two-part, software setup frontend based purely on React, because the modeler is also built in React. This is the easier frontend situation. And um, the other one will be a Laravel pure API backend, where data storage takes place, where, um, uh, the situation is basically what the backend does, right? Whether it's communicating with Mitup, communicating with other plugins, or communicating with other systems, everything that might be added later on will ultimately go through the backend. This situation has scaling points and naturally involves some complexity regarding development, but I think it's actually the most elegant approach at this point, and we will also set it up in Docker Compost as two containers, so that we don't just mix a package and build a monolith. Um, monoliths do n't sound bad, but in principle it's still a way to say, okay, I have a narrow frontend and only scale my backend and maybe the database behind it a little more, but theoretically it will end up being three containers, roughly speaking. We might add caching or something else as a fourth container, but we can prepare all of that nicely as a deployment in Docker Compose, and then people can use it.

[00:20:36]What's inside the three containers? The modeler, or what?

[00:20:40]Yes, the frontend, basically the frontend, contains the modeler plus everything else, which is the Vemo package. The model is just one component in the frontend, hence the name frontend. It includes the modeler, login, admin tool, and so on. Essentially, the entire administration of UWemo is contained within the frontend, allowing users to create folders, project groups, and so on. Um, we also have a few more ideas that will come later, which can then be integrated into Fortnite. And the backend is theoretically, first and foremost, the subject of validation, authentication, data storage, information output, and everything that goes with it, so to speak. If you're crazy enough, you could even consider using this setup to build an app to direct certain data from this tool to another app, right? Because then you have a neutral API and could do it.

[00:21:36]But I don't think I see any multi-purpose use for an app at the moment, because we don't have a production tool here, we only have, let's say, that sounds lower than it should perhaps be. Well, yes, there is Word on mobile phones, but I don't find it very user-friendly, do you? Okay, let's set the record straight.

[00:21:58]There are apps that don't belong on your phone.

[00:22:01]OK. Why did you mention that now?

[00:22:03]Yes, because it makes it possible, but there are other options as well. I could order a dashboard. I want to see how many process models I have.

[00:22:11]I might possibly want to create some kind of map from it at some point.

[00:22:16]This could then be done in a separate app as a monitoring app, where, for example, I have a 66-inch TV hanging here in the hallway that shows me my quasi-interactive process map when something changes or something like that. Yeah, right? Yes, that 's cutting-edge.

[00:22:33]That's an exciting crazy idea for phase 3 4 5 6 7 5 6 7 at the end. Yes, okay. Understood. Yes, okay. Understand.

[00:22:41]Exactly, if we want that, I want that too, by the way. Yes, I find it quite interesting.

[00:22:46]I also want a monitor, but we need to talk about the internal one again. I would like to play WoW on the monitor.

[00:22:54]The lamp is about to fall over. Yes, okay. I would do that too.

[00:22:58]Now the user is causing trouble again at his home office.

[00:23:03]Yes, that shouldn't happen again. Yes, I would also like that screen. No, really. So I definitely think it's important to get management involved in such stories. Yes, I know that you're not all really interested in these types, but they're the ones who release the budget for this kind of thing.

[00:23:20]Yes, that's correct. They'll give out the money later and then we'll see what happens.

[00:23:23]Yes, then comes a very exciting part. This is real-time collaboration.

[00:23:27]We should or will try to incorporate this relatively early on, or even implement it at all, to enable simultaneous editing, live synchronization, seeing the cursor, who is working on what, or something like that, conflict-free editing.

[00:23:41]Very complicated, very complex. I thought about it for a long time because I am familiar with another product, the successor to Kavemo, and I realize that conflict-free processing is difficult there.

[00:23:54]But then I also compared that to, uh, Microsoft Office 365. It's also possible to work collaboratively on a Word document online, and what many people don't know is that the technical aspects come out again. There's also an XML file inside it. As you can see, for many it's just writing.

[00:24:14]Yes, but the font must carry metadata. Am I formatted here in italics or bold? Am I now in this paragraph or list, and is all of this stored in the XML structure? So, does that mean it's okay, or what?

[00:24:26]What is the conclusion to be drawn from this?

[00:24:28]Sure, it's possible.

[00:24:29]So, work must also be done on lines, right? In Google Docs and Word, you can see the other cursor, where the colleague is currently standing, the one who is working on something or has highlighted something or whatever.

[00:24:41]So, you see that. So there must be a way to do that too. Of course, they also have that behind a paywall. Well, I ca n't get the source code out of there, but I know it's a solvable situation because we're ultimately working on a technical structure, on XML-based elements, and with that we can create conflict-free situations, or I believe almost conflict-free situations. And that is a very exciting and complex task. That's why Phase 2 will be a big deal, but it will also be an exciting one, because that's what I'm most looking forward to, because I believe we will be fulfilling a heartfelt wish for many people.

[00:25:21]May I have another go at eating in between? Yes, I 'm here, that's why we're here as a pair, otherwise I'm alone. From what I gather, you're optimistic. Yes, the glass is half full in that you are optimistic about solving a problem, namely collaborative work on a process model.

[00:25:46]Um, that you think you can pull that off. Um, okay. Something that others may not have managed to do properly so far. Yes. Yes.

[00:25:56]In products whose names you ca n't quite remember. OK.

[00:25:59]Well, whose name we're not allowed to mention, but yes, exactly. Yes. So, I think there are only two or three tools that really go in that direction, generally speaking, towards collaboration, right? Step one is one thing, and step two is another, which then happens in a conflict-free, real-time, and live cursor situation, right? So this topic is really exciting to look at, right? Where is he traveling right now and everything that goes with it, right? I just remembered the name. It's a Miro dashboard and that's the situation.

[00:26:34]We could open one now.

[00:26:36]Then you can see, when I send you the link for the dashboard, for such a test, you can fiddle around with it using your mouse and I'll see where you're working with your mouse pointer, right? That's right, they've really got it down. I think the product is stupid, but they're really good at it. That's exactly it. So, everything is already resolved.

[00:26:52]We just need to rebuild it cleanly for ourselves, and that already happens in phase 2, because, assuming the modeler works, I want to focus on the Unix selling point, the USB, that I'm bringing to the table, namely real-time collaboration on such a model. Uh, that's what I would focus on. That's what I intend to implement. OK.

[00:27:16]Yes, it is also necessary, especially during times when we are all lying on some island on a sandy beach and trying to talk to our colleagues about business process optimization or similar things. Afterwards, I think that's the most important thing these days, that you don't have to wait until you see, okay, the colleague has postponed his/her activity and who knows what afterwards, right? But, um, you can see in real time, ah, he's currently using his mouse on the activity, so I can focus on before or behind or elsewhere, right? Um, the fact that there's a conflict when I touch the same activity in such a model, or the same element, let's call it that for now, is pre-programmed, that's perfectly normal, there's nothing you can do about it. But if you can see in real time where your colleagues are in this model, then you can use the power of thought in your brain— where you have a brain, no, in your head—where you have a brain that you can use, yes, swim around the colleague's cursor and say, I'll continue in a different place.

[00:28:18]OK. Google and Microsoft have, um, well, the nice thing is, user behavior is what basically always drives software manufacturers, or rather, the provider, forward, right?

[00:28:33]So, if people say, "I want to open an account at the bank and it shouldn't take longer than a day or whatever, or what I know, 3 hours," then that's an expectation that a bank can't always meet if it's not ready yet. So. Um, there are also people who, um, do n't have what you just described under control. Yes, from the software that we are not allowed to name. Um, whether Microsoft and Google are driving it with their working features, or Miro, yeah, I don't care. Um, do they then drive others into a corner, that they do n't have that, and do the users then demand exactly what they experienced somewhere, or could you ignore that? I think you can ignore that, so to speak. So, Google Docs and Microsoft Word, for example, have the exact same, or rather, they have a similar feature setup for using a written document or document and collaborating on it, right? I can share this with a colleague and say, "I invite you," and we can work on the text together in real time.

[00:29:49]I can also write or create texts and do something together, right?

[00:29:52]There are other examples we can use. Um, and there are large and small products that offer the same thing, complete with a comment function and everything. Um, I think what's crucial for the user isn't that I can collaborate on, so if I want to compare this to a document situation, um, no, that has nothing to do with the document itself, but rather it's about what I can do around it, right? What can I do with the items surrounding this document?

[00:30:21]I believe that now, because the situations involving documents are actually quite similar these days. So, Word obviously has 50 years of experience in how to structure a document, including bold, thin, italic, left, and right text, nothing more. Until, uh, I have a bit too many buttons in my bar at the top, maybe I had them at some point or specifically, right? They then optimized and tidied things up again. So they went through all the phases regarding UI and usage, and they solved the collaborative situations in the same way.

[00:30:55]I think they used Google Docs first, if I'm not mistaken, because Word was n't interested. They said that there are computers, there's something called SharePoint, I think.

[00:31:05]We can basically play it out in our own little bubble. Um, but that was only half the battle, and then they solved it, and I think now it's two things. If I like Google, I like Microsoft, right? If I choose this path, it 's somewhat about the image, and then of course what do these surrounding systems offer me afterwards, right? So, how can I work with my teams, how can I work with my folders, how can I work with my plan, right? And so on and so forth. So, there is understanding there.

[00:31:30]Letter.

[00:31:30]The target audience is crucial, isn't it? So business to consumer nonsense.

[00:31:35]Yes, okay. Yes, then yes, when you go and decide. Yes, it 's the same business; consumer is the smaller niche, the large niche is enterprise customers, where they are fighting. We constantly hear in the news which federal state, which city, or something like that, is buying a Microsoft license volume package or something similar, where it then involves millions and billions in license fees. That's where they play the same game as Google, although Google even has more of this one, they also have the Enterprise, but I think it doesn't even matter there, they make money through search and YouTube and the rest is okay. Just do something. Yes.

[00:32:19]And um, I think they have an active sales force, right? Typical consultants and so on, basically selling, making things happen, and doing things. Uh, Google does n't even know. I've never encountered one on Google. They're probably all sitting on their couch somewhere, waiting for someone to call and say, "I have a problem."

[00:32:36]Um, but now you've really offended all the sellers who are active in Google. Yes, that you just said that.

[00:32:50]Yes, well, I've never been called by Microsoft people before, and I've also been called by SP people before. I haven't received a single call or email from Google. Uh, I'd like to offer you the business account, but usually, once you're in and have decided, they come up to you and say, "Yeah, don't you want to spend any more?" or something like that, right? Don't you want to upgrade or something? Would n't you like that feature too?

[00:33:17]Okay, here's a couple of pieces of information about that.

[00:33:19]Basically, they drive around the world all day in these camera cars. Yes, well, they simply don't have the time to deal with you.

[00:33:28]That's the side job that was displaced at Google, right? Just like in the old days, academics had to take taxis. Yes, now as a Google employee you are required to drive around in a camera car.

[00:33:40]So, first of all, that. Secondly, you have, of course, um, you have optimized this inbound stuff, that's correct. Yes, because they do everything for free. Yes. We're not the devil, yes, if we've offered something somewhere, then this threshold, yes, so now you can spend money, is of course very low. That's true. I agree with you. Then at some point they have to get out of the car and say, okay, now you can buy your Google Workspace. Yes, good. Okay, we've gotten sidetracked.

[00:34:13]We have strayed somewhat. So, once we've solved the real-time collaboration issue and we arrive at the next step in our roadmap, we're in the section where we consider the enterprise aspect to be important, meaning customers with a large workforce, or even just 20 or 30 customers/employees in a company.

[00:34:38]Most of them are organized and structured. That means we need to take care of user management. This means either they have their own Eldup or AD, or we have to offer an account, or so to speak, a user management system, or as we have written it here, user administration. As I said, either through external tools or, of course, through internal administration processes or similar afterwards.

[00:35:03]I said that recently too; that's what I really ask everyone at the very front. Yes, so what about the Elder? So, no administrator at a company wants to copy and paste the entire employee master data archive to integrate it, for example, or even if only five people are working on it at the beginning and more will be added later. No, it has to work, and certain filters and situations need to be included, and so on.

[00:35:36]And then we're already talking about permissions, which is actually the right-hand topic here. Um, which roles, which groups, project permissions, read/ write rights, um, who is allowed to set what, who is allowed to look where, right? How is it closed? So, are there any roles at all? That's another discussion, but generally it's part of the process. Well, at the very least we will certainly think about the topic of groups, because we've already discussed it – I ca n't manage all my models in one cupboard, so to speak. That means I have to do subordination, right? So, at least folders, and I could attach groups to folders, where I say, "Here's group A for, I don't know, this is my application process system," for example, if you think in terms of processes or HR departments, right? I have a group A for applicants, but I also have a group B that regularly reminds my long-term employees to do their annual reviews, something like that, right? I have different groups, and I release the different projects to them, and so on and so forth, right?

[00:36:41]That's why the issue of authorization arises, right?

[00:36:44]Not everyone needs to be able to write, but I think 99% need to be able to read. The thing is, you also need to be able to release such a model for reading purposes later, right? and then present that to the people.

[00:36:57]The technical aspects behind it are, so to speak, a bit like administrative issues.

[00:37:04]I mentioned earlier that an admin area is definitely needed, because that's exactly where user management and administration will go – it will definitely be in a separate admin area. Permissions, at least regarding group creation, project permissions, and read /write rights, will most likely be implemented directly on the models or folders, because that 's simply state of the art, that's where it belongs, right? I'm here in the folder now, I created it, and now I'd like to invite my colleague Hans Meer to read along, or Ms. Müller Schulze, and uh, she should also be allowed to take a look at it later as an example, right? And that's what I want to do there, right? Therefore, this is again a bit of a question about which section we will technically be working in later. But we need audit logs, and I think that's a great thing.

[00:37:50]Companies above a certain size are terrified of reality, of the fact that everyone wants to do harm, right? It's actually quite common practice.

[00:37:59]Everyone is evil. Every mobile phone we own is evil. Um, theoretically it's true, right? So, we can hack any mobile phone and we can use any camera if they walk through Dresen or take pictures of something and take them away.

[00:38:13]Um, and in companies, of course, this is taken even further, and that's okay too. And that's why we need to be able to understand it in general terms or in detail; we need to look at that, right? Perhaps a Ken switch needs to be added or a configuration needs to be done. I want a very detailed audit, I want a very rough audit lock. It depends a bit.

[00:38:38]If this tool is used by a customer, UVEMO as a product will be considered security-critical, audit-related, uh, certification-related, and so on, right? That's the question, what impact does such software have on the overall data security structure of a company afterwards, right? Is it, for example, also a system-critical and, uh, uh, system in such a way that it has to have 24/7 availability, right, that it has to work all the time, and there are a thousand things we haven't even thought of yet, but where companies will then ask us questions, saying, yes, but it also has to be able to run at 3 a.m. on a Sunday night, because the boss is bored then—that was the example, um, which brings us back to the big screen, right?

[00:39:25]Correct, correct, correct. Exactly. OK.

[00:39:28]Um, backup management, versioning, all these things are kind of included. Change history, that 's simply put, I can understand it, I can look at it, so we'll also have numbers like that in the admin area, right? Does that mean how many models are there in total?

[00:39:45]For data protection reasons, we are not allowed to give any details. That's important too, of course, that you do n't tell the admin, okay, this is the termination process and he knows what it's like if he gets fired or something like that afterwards, because that's always an example of transparency.

[00:39:59]Um, but for some people it's important to know, okay, well, we now have 6000 process models running in different folder groups and projects, and that's why having some numbers there is quite nice, and that also makes things more appealing to the boss, like, is the system worth it or not in the end, right?

[00:40:17]Large screen. Yes, exactly. HTTPS security is usually in place. The use of auto-off-the-box and even partial AP tokens is a situation when we talk about APIs; this has simply been included in general terms.

[00:40:30]Password policy is essential; every company must be able to define it. At least a number, a character, a special character, and so on. This topic also needs to be changed every year, assuming the situation is handled via this tool for authentication.

[00:40:46]If we have Eldab or AD or whatever it may be, then password policies are obviously out of the question.

[00:40:52]But we'll initially set everything up as if we didn't have Eldup, and then we'll set it up accordingly.

[00:40:57]When we turn on Eldup, we'll of course turn off the other things, but that's part of the process. You simply have to keep that in mind, and password security is absolutely essential for such a tool. But you mustn't forget that if this tool is actually used— and some might forget this or not think about it—it's similar to a wiki. Wikis are knowledge-based document systems; they contain company knowledge, and a process management system like this also contains detailed company knowledge. This is something that eventually happens when a company—for those who might know, the OMG (Organization for Management of Processes) released something called Leveling of Standards for BPMN modeling—and whoever achieves the highest standard out of four or five, I believe, is essentially fully modeled within their company.

[00:41:52]That means I've put all my knowledge about my company's processes into BPMN models, and thus I've essentially incorporated my knowledge into the documents, so it should be secure afterwards, right? Because then it becomes highly relevant, depending on what I put in there, and therefore security is paramount and the most important point.

[00:42:14]Mhm. Exactly, we're at phase 4. Now we're going to talk about team collaboration again, right? We already saw that above, right? We can see each other, we see the day-to-day activity, but just knowing that my colleague is moving his mouse around and maybe dragging the element from left to right doesn't mean that the collaboration is 100% there, because things like comments are also part of it, right? I might also want to leave him a message, if he's not around right now, saying something like, "Hey, look, I 've changed something here," or "Why did you do that?" So, ask the element a question and say, " We can talk about this later, okay?"

[00:42:53]And similar things besides. We've thought about it one step further, have n't we? So, of course, comparing different versions means that if we have versioning above, then we also need to consider how we can see what has changed in the version, right? That's kind of part of the review, but we can also think about things like, yeah, we'll include review workflows or approval situations, meaning one person models and another says it's crap or good, right? And that's called a review workflow in co-approvals, or you do n't immediately introduce a change to the model, but I find that interesting too, you just introduce an idea and say, "I could imagine if we did it this way," and then we branch off and say, "Okay, here's the original, my colleague made a change." It 's like a kind of branch, a fork in the road, and then it's suggested, and if it's accepted, then it can be integrated, right? The developers know what I mean. Git commit and merch and stuff, players in, right? So, we're changing something, but we're not putting it into the main code yet. Instead, we're just saying, here's an idea, I'm giving it to you as a request, and saying, here, I have an idea, take a look at it, and then, if you're satisfied, you can merge it into your process. And that 's a whole other world that does n't exist yet, just so you know.

[00:44:14]Um, documentation. I believe this is one of the most sought-after, discussed, debated, contested, and whatever other situations in the world of processes, because we always only talk about the model itself, but the surrounding aspects, BPMN doesn't solve those, right?

[00:44:39]BPMN does not offer a place to say, "I'm documenting what I want in these BPMN elements, and there's a textbox, yes, but that's not enough."

[00:44:48]And that's why we've added the topic of documentation for team collaboration here, so that we attach a separate metadata element to the model, where we say, there's the BPMN XML plus description, attachments and so on, right, links to other systems or so on, right? Documenting directly within the process is out of the box. It's a little bit involved, but it can also be expanded, but we want to do a little more and then we'll be finished and it will probably be Christmas.

[00:45:21]Is this about process mapping, process documentation itself, or process documentation? Yes, we're not a map yet.

[00:45:29]Okay, that's not thawing at all, is it?

[00:45:31]So, at the moment, we haven't planned for that in the initial phases. That could happen later. Yes, okay. But they've both talked about it before, and also with others. Yes. Um, that's a different perspective on the processes we see or have in the company, so to speak, right? So, from the company's perspective, right? I'd like to get an overview and not just try to understand the individual models; I also need a general overview afterwards. Yes. Um, this additional information is attached to models because there are limits with OMG and PPMN, right? So, that's what the comments on process models are about, if I understand correctly. Um, so where does the product differentiate itself? Where do you say UWMO?

[00:46:26]UWMO doesn't need to be able to do that?

[00:46:32]difficult question.

[00:46:33]Yes, I'm thinking about it right now. Wow, that's an interesting question, but it's not difficult, but it's interesting because we all want everything to be the same as always, right? But is it sensible to be able to do everything? That's the question afterwards, right? Because, um, I believe that when we get to phase 4, we'll have a cool product in our hands. Step 1, right? That's us already, mhm.

[00:47:01]really cool. Then the current discussion is about what we have here under Phase 8, namely AI Assistance, as an example.

[00:47:08]Oh, wait a minute. The topic of AI integration will undoubtedly be demanded or discussed by customers sooner or later, or the question is, do you need it? Is that sensible or not? And so, right?

[00:47:19]You just have to take a look. Um, I need to get you over here. I need to try it myself; I didn't see the phases. So we were there, and we could n't go any lower. Um, down there are the five phases that have been indicated. Whether they come in that order or something. Everything is still completely open at that point.

[00:47:40]Mhm. Um, but in principle, what doesn't Uvemo need to be able to do, so to speak?

[00:47:48]So, what don't you need to be able to do, let's put it that way. So, I can absolutely understand that when you create a product, you say to yourself, okay, we'll start, and I already admired this earlier, yes, we'll start with a realistic root map, yes, so we say, this can do this at the beginning, yes, you can already work well with this in this phase, yes, then this and this and this follow.

[00:48:10]So, we're in phase 4, team collaboration, and then all of a sudden we say, um, it can do this too, and it can do that too, and it can do that too. Um, egg-laying tree-like sow. Do you want that?

[00:48:24]So, do you think the world... No, but I think we've got to deal with it, so I think there are few steps after that. So the map would be one point I could really imagine. Um, this is an extension of the documentation, so to speak, right? We have now entered the documentation area.

[00:48:40]But I wouldn't create a file storage system that has nothing to do with BP, meaning nothing to do with Bpimn, later DMN, and therefore nothing to do with the processes surrounding it, right? So, we do have attachments here, but they all relate to a process. There won't be a folder simply called "File Storage," for example, right? Where I see nothing else but this, right? That would be unnecessary baggage for me to manage in there.

[00:49:06]Interjection. Yes. I usually have to manage this baggage as well. Um, if I'm dealing with a client who is n't familiar with BPMN modeling at all, in the traditional way, right? Then data will be generated, because you just said you won't manage it, but data will be generated in different formats related to this process, to this topic. Then they belong to the process, but not, I don't want to create a folder for miscellaneous things, there's no process model in there, it only contains Word documents. I know, but sometimes, no, but sometimes it's okay, you don't want a SharePoint sentence or anything else, but I understand that, but um, this is just pure brainstorming now.

[00:49:50]Yes, well, I'm good. So someone says, "I drew this in Viso," or someone says, "I have a PNG file, yes, I took a picture of the dashboard somewhere," or something else. Yes. Yes.

[00:50:06]So, this very process of collecting the life cycle of a truly functioning process model, yes, starts much earlier, it starts before BPMN, I think. Yes, so that's the background of the process, but the process model still has a name or a section or a heading, right? Yes. Yes, exactly.

[00:50:26]So, we have our order process, and Kalle from Ja. has it.

[00:50:32]He once wrote down "database administrator for 35 years".

[00:50:34]Correct. I think you can look at it under the documentation attachments later, so to speak, right? But I already have a goal in mind: to manage a BPMN model later.

[00:50:46]Of course it can be misused, right?

[00:50:48]So, I'd say someone could also misuse this idea of ​​allowing attachments to the process model or to the situation. We'll have to see how it goes. I don't think your idea is bad at all; what if someone starts out and has just drawn something on a piece of paper?

[00:51:07]We scanned that. It will be available now as a PDF or later as an image. Um, how do we want to handle this afterwards, so that this origin story is documented, so to speak, or the history is filed retrospectively?

[00:51:22]Um, we simply need to discuss how we build the UI at that point and where we say, okay, well, you either create a folder for the order process or you create a BPMN model for the order process and a file is attached to the BPMN model afterwards.

[00:51:37]Um, so that you can, let's say, automatically—I mean, you want to eventually create a BPMN file from it—there might be a tab at the beginning where there's the possibility to store attachments, which are then linked, so to speak, but I don't want to create a situation like that.

[00:51:54]So now I'm deliberately saying " maybe" because I don't yet know what will happen when we get to the point where I say, "I'm going to create a folder called 'Order Process'" in which I simply dump everything I've collected about the order process over the last 10 years." Um, but I'll never see a BPM file in there, right? Then I would have built another SharePoint or a OneDrive or similar replacement later on, and so on, right? That 's the question, and it depends very much on the UI, the usability, the situation. But no matter what we do, I'll bet on it. MKO, if we get this thing onto the market, get it to the people, and we will certainly be able to offer it to some customers, we will see things in it in a few years that we never even dreamed of, because the imagination of people to misuse software as we once envisioned it is infinitely large, because I have already experienced so many things where I have built things. Um, what's it called, where people suddenly came up with the idea, yeah, no, I could actually use it like that, and then I think, dude, how did you come up with the idea of thinking of the field like that, instead of as it's written there, that it's blablabla, right? Yeah, dude, that's where people have an endless imagination to use software in ways you'd never think of, right? Okay, speaking of imagination, we 've now drawn, or rather written down, a red map. That's the one you can also find on Wemo, it's already, uh, live.

[00:53:33]It's live. Okay, good. Cool. So, you can go there now and say, okay, yes, that's where I see myself again.

[00:53:39]The product would then be shaped accordingly. Uh, what's the process if I want something extra, or if I want to talk to you about it, or if I have anything else to contribute? What does it do?

[00:53:54]So, there are two ways. You can contact us as usual at the bottom of this page.

[00:54:01]Yes, that's one thing, right? Quite normal. I would like to be the new beta tester, so there is a need for discussion. Then you write " need for discussion" here, write your name before it and then after it, uh, al ne, that's then Mail Ad and so on.

[00:54:16]And then you write "company" here, if you want, and then you write "blah" and then you say here, I'll enter the math problem here, the task briefly, and then I'll send the message and then we'll get back to you, right? Step one is the opportunity; I want to talk.

[00:54:31]Step two is the topic we showed earlier. I'd like to submit the feature request, okay? I have here m I would like it if we could b uh I can't type right now, um, also model pictures or something, right?

[00:54:50]Mhm.

[00:54:51]And then it goes on, right? Then I can do that, send it off and say: "Well, both ways, either you take that, but it's attached to the red map, right? So a feature request of this kind is, uh, that would definitely make us think more about whether and when we might implement it, if we decide to implement it." Yes, exactly.

[00:55:13]Okay, I understand. I think that will change at some point when we've progressed further, the software exists, and the first customers give us feedback; then there will be a feedback channel from within the software itself to submit ideas, or at least a link somewhere. That needs to be discussed with the customers again, right? Are we even allowed to send emails from this thing? Because I do n't see that right now, since we have a very important point here. This is the option to activate the Airgap system, in case anyone isn't familiar with it. That means I can run in completely isolated network operation, i.e., one box, maximum access to it and no internet access or anything like that, because, you know, high-security data matters, you know, we were just talking a bit about data protection earlier. Yes, then there might be companies that say, no, no, with me that thing is isolated, because it contains all my company knowledge. And then it's all over, and then not even an email can be sent afterwards, right? That's all things you have to think about at that point, um, and similar things, right? Then you have to see how you can deal with it. Exactly. But those are the ways.

[00:56:22]Otherwise, uwo.com, ubato.com, and so on. You can reach us there, reach me, reach Mirko, reach everyone who has something to do with the project and wants to talk to us.

[00:56:35]Okay, so you can also comment under the video. Yes, commenting is also important sometimes. Um, let's talk about target audiences. Yes, I have to say again, so yes, um, yes, very open about target groups, is that the disappointed one, no, differently the doubter, that Sa is the absolute solution for him, is a target group or as far as modeling with Uwemo is concerned. Yes, well, we've decided that we'll consider that. So, we want to make it clear that we don't have any doubts here, and we ourselves say that SAS isn't the right way to go for this product. Instead, we say it makes sense for the customer to be able to decide where they store their data, whether they do it in their own cloud, in the public cloud, or something like that.

[00:57:29]We can't dictate that to them, but in principle, they can decide. He has the option to go up to Airgap status later, but he can essentially choose the location where he wants to set it up later.

[00:57:44]So, what other problems could he or the target group have that would lead them to use such a product?

[00:57:50]Yes, the issue is that several departments, spread internationally, might be working on models, and they do n't all sit on a plane and meet every day.

[00:57:57]Team sessions can also be tiring at some point, or something like that, or I don't know what. Um, but you also have to deal with time zone issues and want to work on the model afterwards, right? So, the topic of teamwork, um, process model maintenance, documentation, so processes also need to be documented, across several departments, as all these topics, um, possibly topic, um, how I want to, I'm currently considering. Um, what about the PPMN standard itself? So, a consistent BPMN20 standard implementation.

[00:58:38]If you're concerned about security when it comes to BPMN, then this is a feature. Yes. Um, if you don't want any other models besides BPN, it's a feature, so to speak; if you only focus on the topic, it's a product that definitely delivers added value. Um, yeah, what about multi-multi, uh, multi-engine capability in the end?

[00:59:07]Our roadmap states that we will consider process automation at that point, right? So, on the topic at hand, we definitely won't be bringing the engine into Uw, but we are considering how to get a process from Uvemo into the engine and possibly also get metadata from the engine back into UVMO afterwards, right? So, the topic, um, analysis, the topic, we call that BPMN, the life cycle, so to speak, right? So, I build something, I execute it, I evaluate it, I improve it again, right? So classic, right? Versioning.

[00:59:46]I'm making a new version based on my experience. We'll have to take a look. At least that way will be found, leading into the engines. So, like you said, right? So, a bit tool-neutral, because I think this is an exciting situation and I also believe that in years to come there will still be customers who will have the Kamunda 7 flying around somewhere.

[01:00:09]OK. Yes.

[01:00:10]Is it a Tey tool or is it a, um, a borderline tool? No, that's definitely true for both worlds. Yes. Yes. OK. OK.

[01:00:21]So, this is where I see the majority at the moment. So, I believe it's a good tool if, um, as a company with 20, 30, 40 people, I want to build on BPMN moduleization all at once to highlight my processes, which we've all had for years, but now want to make them more visible; it has two advantages.

[01:00:49]The models don't just end up on a single computer and then disappear one day.

[01:00:54]Step one.

[01:00:55]Yes, they don't necessarily end up in a SharePoint where you can't find the folder again because you have n't navigated through the structure and only one person knows the way there.

[01:01:05]Um, you have a sort of, I'll call it that for now, as it's sometimes negatively portrayed, but a data sink where process models can end up, and you have a point that you create. Okay, let's describe it in real-world terms. I have a cabinet where all my processes are located in various subfolders, and so on, but I know where the cabinet is. I know where this information is afterwards, and not that I have it on a computer belonging to an employee who then leaves the company after 3 years and we say: "Okay, well, he 's gone now, the backup was made, but nobody checked what was actually on this computer, so to speak." Afterwards, you know what I find really exciting? Yes. that the topic of AI Assistance will be covered in Phase 8.

[01:01:54]I agree with you, we will have the discussion that customers want this even earlier. Yes. Yes, exactly.

[01:02:00]Especially since it's such a loaded word, especially in that situation, but you're not like that, are you? Well, that 's really not your thing.

[01:02:07]I find that quite exciting to see.

[01:02:08]Well, I get asked this again and again, because I also come from the operator field. Yes. What do we do in operation or in such an engine with AI, or what do we do in terms of modeling and AI?

[01:02:22]So, a colleague in the project quite rightly pointed out that there are two major problems when you say, "I want to do AI and build process models."

[01:02:33]The AI ​​knows nothing about your business.

[01:02:37]Point 1. What does that mean? What do I need to do to fulfill this requirement so that I can build my models with it? It means I have to basically pull down my pants, make my ass plank, give the Egemand knowledge and say, here this is my company secret, this is how I work, this is how I live, this is how I earn money, this is how I make my revenue, this is how I want to grow my company. And now consider this: if you don't have anyone who knows how to build a local AI or a local language model, how do I uphold my data privacy here to ensure that my language models don't leak this expertise? Have a good meal.

[01:03:20]And what we want to do here is not to change the AI, the idea behind it – we've thought about that too, haven't we? I find the idea behind it much more charming. This AI Assistance has nothing to do with creating models for you; rather, the AI ​​Assistance is the idea of supporting you in creating models correctly. You are the experts, the assistant is there to, uh, recognize, ah, this could be optimized, right? I know there are better gateways with the structure you have, right? She gives feedback or something like that. So she looks at the models; that 's the idea behind it, to one day look at them neutrally.

[01:04:04]And actually, my big dream would be that this language information comes from the local instance that we have trained, perhaps simply because of the BPMN, DMN, and so on standards that we then use, and can then be operated locally and support local support, in order to say, here I see difficulties, this could cause a problem, perhaps even at some point related to the engine context. Yes, I know a little bit about the Operation Engine. Pay attention here, okay?

[01:04:35]If you do it that way, it could cause problems. Bla bla bla.

[01:04:39]For me, this is AI support. But if I am the person who says I need an order process or a business process, as many companies are currently advertising, please remember that these AIs do not know how your orders work. They do n't know how your recruiting works.

[01:04:57]They don't know what your HR department processes, sales processes, marketing processes, or development processes are like. So, in that respect, folks, you have to give AI the knowledge beforehand so that it can advise you at all.

[01:05:11]I find that a really interesting aspect. I spoke today with a colleague, Sarah Wiesenborn, who will be a guest on the show in September. Yes, cool. Then we'll take exactly this topic, namely the recording process. Yes, so many customers claim, oh my god, I'll tell the AI, yes, let's create a proper process, yes, uh, for my topic XY and then we can work with it, right? And this is exactly the topic we discuss in the show, that it's nonsense, yes, that it's not at all what you just described, yes, the prerequisite that one has to create in order to even consider it in this way. But nevertheless, it is of course relevant to bring in the people involved, to talk to them, to record that accordingly and to bring the knowledge into the model in some form, which may not yet be present in the LM. And then there's the risk on top of that. Yes, if I pump it in and don't run my own instance, then I might as well go to the marketplace and say, "Hey guys, let's talk." Yes, I will explain everything that makes up my process model. Um, I find that interesting, precisely because there's also a certain degree of gullibility among the customer. Yes. Well, that's just how it is. And uh, you know better. Yes. And if you know better, you prioritize it or define it differently. Yes, so how can I use it more effectively? Yes. Um, and because you have this knowledge, you tackle it in phase 8, even though everyone else says, oh God, come on, let's do something with her.

[01:07:07]Yes, okay, I understand. Yes, good.

[01:07:11]Safe route, right?

[01:07:12]Yes, absolutely. Yes. Yes, I'm not saying that's why I organized the AI ​​Weeks and said, " Come on, let's talk about Trusted AI" or anything like that. But anyway, that's a side issue. I find it quite interesting that you, um, that when prioritizing the tasks that necessarily need to be addressed in such a product, um, um, you categorize them in this way and that you have a realistic picture. I make you seem very likeable, by the way. Yes, so you're not a marketing person, and you're not a salesperson either. But you already are there, you already know it, you just do n't know it yet. I haven't done that yet, but I have you, yes, but uh, it's really cool, yes, a lot of trust comes across, yes, you know what it's about and you know what you're doing and you know how to do it. I think that's pretty cool. Yes. Yes. Okay, there's one more thing I'd like to quickly clarify. We were talking about Operation's web apps the other day, and a colleague on the team asked me about the dark mode issue, right? He said you had an Unw just for fun, right? He told me this with a broad grin on his face. You have Dark Mode enabled. There is a dark mode, but it's only automatic. Only automatically.

[01:08:34]But you can't adjust them.

[01:08:36]The applications usually offer the option to specify whether the setting will be automatically or permanently light or dark afterwards. And he said, well, if you start the web apps and you have dark mode enabled, then they will also start in dark mode. I say that's nice, but it's not written down anywhere, you have to smell it, right?

[01:08:52]But my colleague installed that, right? Dark mode for the nerds. It's available with Dark Mode.

[01:08:57]I'm not saying that, but uh, it happens automatically. You ca n't just say, "Ah, I want to work in the light during the day and in the dark at night," or something like that, can you?

[01:09:07]You can only control this via your operating system if you explicitly switch between day and night modes. Yes.

[01:09:13]Um, but everything else is, um, but it's still feedback. Paul, I like you. I, I, I will carry you around on a silver platter for the next few years.

[01:09:25]Paul, great cinema. Darkme is here. Yes, I wanted to bring that to your attention again. I saw a huge tender today, yes, where exactly Paul's, uh, Paul's, uh, um activities were being requested. Yes, I would say so. Yes.

[01:09:39]Um, so let's continue, yes, so that we can win the tender.

[01:09:45]Exactly, so that we can maintain a calm and collected atmosphere. Yes, Paul delivered. We are there. Yes, just a quick note. Do we have another topic? Is there anything else we need to go through?

[01:09:55]How long have we been traveling here? Wait a minute.

[01:09:57]No, I think we're done for this time. So Rad, I would take the first step now, until we talk again after the holiday.

[01:10:07]Modeler publicly presents herself, i.e., in preparation for the Open position. We will tie the bow, hang up the red ribbon. We will, um, create a situation in which we virtually cut a ribbon or whatever.

[01:10:20]You prepare that. Just like in the old days, I can arrive and say, " Now I'm here, I'll press the button," and then the nuclear power plant will be online. OK. Yes, good. Something, or we sit next to each other and hold a real red ribbon between us and cut it properly, or whatever. That would be funny too. Let's come up with something. So this is the next level. We will hold the Webmodel Opens House, whether with a symbolic act or with actual chamomile tea for a toast or something else. We'll manage it. Cool. Yes.

[01:10:51]Yes, but I will also start with the basic structure, taking the first steps towards the application now.

[01:10:59]Yes, setting up the frameworks, I 've already discussed a concept with AI, how we approach it and what we work through, right? Tasdisten is created and then it begins.

[01:11:11]Next time, you'll have to explain to me what you had to prepare so that it would be, uh, okay, good. Yes, so that I can understand it too. and then easily implement it themselves in the future. Yes, that's why I'm asking. Yes. Yes, you'll do Uw 2.0 then. I know, right? No. Yes, something. Yes, but that's the beauty of it, it's just like playing WoW.

[01:11:39]Yes, when I first understand, when the spirit brings me back to life for money, I don't end up where I just died, but I end up, do you see that? You have to experience that for yourself. Yes, and that's exactly how it is with cutting the red ribbon when we put something on Open House. Yes, I need to feel it and then I'll know, okay, that's how it should be. Yes. Yes, yes, yes, yes. Cool, we'll do that next time too.

[01:12:10]We'll see each other again on Friday, right? Yes. Yes. For those who don't already know, we do the following. We're having a tool talk. Yes, a tool talk. Yes, we're talking about open source products.

[01:12:28]Um, and uh, you're doing something there. So, what are they for? What can you do with it? And we try things out.

[01:12:36]We are referring to truly free Open Source products that can be used in a corporate environment.

[01:12:50]We also take a look at enterprise-relevant open source products in the Deathlab.

[01:12:52]So it's a format of Deathlab. Yes, so we sit there and watch it.

[01:12:57]Uh, we call it Tool Talk because, uh, it's not always clear what you're getting dragged along, what the cat puts on our doorstep. Yes.

[01:13:04]We don't know that for sure yet. We'll make an initial suggestion for the topic, and then we also wanted to ask people what further questions they had, what they would like to see, what they would like us to look at, where we ourselves might experience something surprising, because there is so much open source, many people don't even realize it.

[01:13:24]That is also the point we need to make public. Besides Paul's Dark Mode, yes, we also have to say, you have no idea. I keep remembering this customer who said, "I was already done with the topic when I heard, uh, that's Open so hor." You have no idea what kind of boxes I have here, all of which are open. Yes, well, I'm satisfied with it. We can do that. Yes. Yes, that was cool. He already pulled the hook through for me, it fits. That's exciting.

[01:13:58]But still, there are plenty of people who use it, but have no idea what it actually consists of and where it's used.

[01:14:06]We'll talk about that on the Friday before your vacation. Um, we're creating a new format. But we're also quite good at hosting right now, um, and we'll have a lot of fun watching things.

[01:14:18]I will learn again, and you will boast about your knowledge. Yes, I understand.

[01:14:23]Yes, just like always. Just like always. Okay, then I can open myself a camel tea now. See you Friday. Um, and yes, we're having a nice celebration, so open the chamomile tea.

[01:14:37]Yes, the next evening and I'll see you later on Friday.

[01:14:40]Understood. Thank you so much for being there, thank you so much for the root map. You can see them on owmo.com, you can help them, and uh, definitely uh, get in touch uh if you want to be part of it when we change the world. Yeah right.

[01:14:56]Good. Have a nice evening. Bye! See you then. Ciao.

[01:15:19]I'm out. See you next week.