Unfortunately, this is often a misjudgement, because what we are currently seeing in the market – namely the integration of AI functionality into existing software – can quickly become a problem.

According to the AI Regulation, every system manufacturer that integrates Chat GPT into its software, for example, becomes a “downstream provider” (section 3, paragraph 68) and is therefore automatically subject to the obligations of the AI Regulation.

And this happens faster than you think: even a simple, purchased chatbot or a translation function via the Chat GPT API makes you a “downstream provider”. And we are currently finding such use cases almost everywhere!

Damn… so this does affect us after all!
And now?

Well, now you actually have to carry out a conformity assessment for your system and the downstream system. This must be documented and in most cases also means that you have to implement a series of measures (e.g. transparency obligation, documentation, monitoring, risk assessment, etc.).

This also includes measures that must be publicly visible (e.g. transparency), similar to the implementation of the GDPR or cookie notices. I would therefore not be surprised if we soon see the next wave of warnings coming our way.

So it’s best not to let this become a problem in the first place…

#itsachverständigesindcoolSLW Streitz Liesegang Wagenpfeil & Partner

P.S..yes, I deliberately said “𝘗𝘳𝘰𝘣𝘭𝘦𝘮” here and not “𝘏𝘦𝘳𝘢𝘶𝘴𝘧𝘰𝘳𝘥𝘦𝘳𝘶𝘯𝘨” (bad “no-go” in manager-speak – I know), but what needs to be done is clear and not a big challenge. However, the issue quickly becomes a problem if nothing is done… hence “𝘗𝘳𝘰𝘣𝘭𝘦𝘮”…

Der Beitrag AI Regulation – the “downstream provider” erschien zuerst auf Prof. Dr.-Ing. Stefan Wagenpfeil.

Today it’s “yes, I edited that a bit with AI”. Running…

I now find this irritating, to say the least. To be more precise – outrageous!

When I look at the LinkedIn feed, for example, I get the impression more and more that the majority of images, videos and texts (anyway) no longer reflect people, but are simply designed for reach and algorithms.

Authenticity is the most important asset that should exist on platforms like LinkedIn. What use is a network with fakes? What good are business contacts who are not “real”? What good are people who are not authentic? What good is “experience and expertise” that is only generated?

Clearly, the train that we can reliably recognize or at least identify AI-generated content has long since left the station. So we have to turn the tables and label “real” content.

I therefore advocate a “Made-By-Human” seal!

The C2PA, for example, is a good start(https://c2pa.org, recognizable by the small cr symbol), but is still far too superficial.

Incidentally, I am firmly convinced (perhaps old-fashioned and endangered) that authenticity will prevail in the end. Fakes will become boring at some point.

…. I hope.

#informatikersindcool#realcontentisimportant#authenticitycounts

P.S.: I can also create AI-generated fakes myself, I don’t need a platform for that: “You’re a successful influencer on LinkedIn. Generate a picture with a pretty person who looks positive and successful and write a text every day on the topic of xxx that generates as much reach as possible. Use the posts from A, B and C as a template” – and you have your own social network!

Der Beitrag Made by Human – we need a new seal of quality erschien zuerst auf Prof. Dr.-Ing. Stefan Wagenpfeil.

Even if these models are not up to date with the current Chat GPT, they can be operated internally, especially for security-critical data. You can run a “small Chat GPT” on your own server, with your own data, without any internet connection.

Open AI is pursuing the strategy that it is better for customers to get everything from a single provider rather than relying on competitor models for internal, secure purposes. The company is thus positioning itself in all areas:

– Free online version (note: data protection issues)
– Paid version (EUR 23), better data protection, better model
– Pro version (EUR 229), Ph.D. level assistant
– Open source version for self-installation

This is not meant to be an advertisement for Open AI (God forbid), but it shows the ways in which the big AI companies are going about achieving customer loyalty as well as end-to-end solutions.

However, if you really want to approach the subject seriously (and in a corporate context), you also need to provide the appropriate hardware. An A100 from NVIDIA is recommended here, which can easily cost over 35k. However, you then also have your “own little chat GPT” in the basement…

Irrespective of this, there are of course now tons of language models from various providers. The most common is probably the Llama model from Meta, which is also used in many corporate applications.

In any case, I’m curious to see how the use of these models develops and will try it out myself.

#informatikersindcool#opensourceisimportant

Der Beitrag Operate ChatGPT yourself – OpenAI publishes open source models! erschien zuerst auf Prof. Dr.-Ing. Stefan Wagenpfeil.

What is the status of your IT project? Do you lack a sound basis for making decisions on further development? Is the project in a precarious situation, does it need to be restructured or is an orderly wind-up on the cards?

𝗛𝗲𝗿𝗮𝘂𝘀𝗳𝗼𝗿𝗱𝗲𝗿𝘂𝗻𝗴𝗲𝗻 𝗶𝗻 𝗜𝗧-𝗣𝗿𝗼𝗷𝗲𝗸𝘁𝗲𝗻 𝘀𝗶𝗻𝗱 𝗸𝗲𝗶𝗻𝗲 𝗦𝗲𝗹𝘁𝗲𝗻𝗵𝗲𝗶𝘁 – 𝗲𝗻𝘁𝘀𝗰𝗵𝗲𝗶𝗱𝗲𝗻𝗱 𝗶𝘀𝘁, 𝘄𝗶𝗲 𝗺𝗮𝗻 𝗶𝗵𝗻𝗲𝗻 𝗯𝗲𝗴𝗲𝗴𝗻𝗲𝘁.

A crucial step is to bring in an experienced expert to determine the target state and objectively assess the actual state of your project.

Streitz Liesegang Wagenpfeil & Partner is the leading German expert company for the integration of strategic, technical and commercial expertise. We combine more than 100 years of experience as full-time publicly appointed IT experts.

𝗚𝗲𝗺𝗲𝗶𝗻𝘀𝗮𝗺 𝗲𝗿𝗮𝗿𝗯𝗲𝗶𝘁𝗲𝗻 𝘄𝗶𝗿 𝗟𝗼̈𝘀𝘂𝗻𝗴𝗲𝗻, 𝗱𝗶𝗲 𝗜𝗵𝗿𝗲𝗻 𝗣𝗿𝗼𝗷𝗲𝗸𝘁𝗲𝗿𝗳𝗼𝗹𝗴 𝘀𝗶𝗰𝗵𝗲𝗿𝗻.

Der Beitrag SLW – the IT experts! erschien zuerst auf Prof. Dr.-Ing. Stefan Wagenpfeil.

Because when the development is finished, that’s usually when things really get going:

Solutions have to be operated (processes, teams, support are needed), they have to be updated (refactoring, updates), new functions have to be integrated (backlog, product management), all this requires continuous testing (key users, specialist department) and external framework conditions also have to be taken into account (laws, new standards, security issues) – modern software can be in operation for decades!

For years, it has been proven time and again (sometimes painfully) that the maintenance costs of individual software, even when considering a 5-year term, take up to 80% of the budget and thus exceed the pure development costs many times over.

So if we want to make software engineering sustainable, we have to take these costs into account and take specific measures during the development phase in order to keep the subsequent running costs low. Even small changes to the architecture are often enough to secure long-term investments and reduce costs.

I can only recommend that you pay attention to these aspects when planning and tendering projects!

#informatikersindcool#cost-saving sense#sustainabledevelopment

P.S.: Of course we can also help you to identify and integrate these aspects.

Der Beitrag Up to 80% of the costs of individual development end up in maintenance! erschien zuerst auf Prof. Dr.-Ing. Stefan Wagenpfeil.

1. the legal situation:
The U.S. CLOUD Act allows the American government to access all data (business + private) as long as it is located on servers of U.S. companies. It does not matter where these servers are located and by whom they are operated – as long as there is a U.S. parent company. Orders can also be issued directly by decree, for example(https://www.heise.de/news/Strafgerichtshof-Microsofts-E-Mail-Sperre-als-Weckruf-fuer-digitale-Souveraenitaet-10387368.html)

2. national and EU law:
It is now often argued that the U.S. CLOUD Act would not apply if, for example, European subsidiaries of the U.S. provider were to violate European law(https://www.m365einfuehrung.de/blog/microsoft-unter-eid-was-wirklich-hinter-dem-cloud-act-steckt).

All-clear? No, because how would that work in practice?

3. current example case:
Microsoft recently blocked the email account of a high-ranking EU politician(https://www.heise.de/news/Strafgerichtshof-Microsofts-E-Mail-Sperre-als-Weckruf-fuer-digitale-Souveraenitaet-10387368.html)– by order. Legal action then had to be taken, but the account remained blocked for the time being.

Thinking further: Your data would therefore be blocked (and therefore no longer usable for you) or – even worse – already released and you could then fight to have it protected again.

4. assurances and the “damper”:
Until now, many U.S. companies have been on a major “charm offensive”, promising digital sovereignty. Now, however, Microsoft managers have admitted under oath that they cannot guarantee protection from the CLOUD Act(https://www.itmagazine.ch/artikel/85137/Unter_Eid_Microsoft_kann_Schutz_vor_Cloud_Act_nicht_garantieren.html).

This must be a wake-up call for all European companies!

So what to do?
– Encryption? It helps, but only as long as the encryption methods are secure in the long term (keyword: post-quantum encryption).
– Relocate? Certainly an option, but a huge effort. In addition, sovereign European cloud structures are only just being established and we have all become very accustomed to the convenient Microsoft services
– but in any case: take the issue seriously and don’t ignore it!

Company data and knowledge are worth protecting. They represent your assets and your competitive advantage. We no longer just have to deal with the threat of hackers, but also with international law and derive suitable strategies from it.

#informatikersindcool#law is becoming more and more important#itandrightmostright

P.S. Cloud here does not stand for “the cloud” but for “Clarifying Lawful Overseas Use of Data Act”

Der Beitrag The U.S. CLOUD Act – starting to be a real problem… erschien zuerst auf Prof. Dr.-Ing. Stefan Wagenpfeil.

Der Beitrag I realize I’m getting suspicious…. erschien zuerst auf Prof. Dr.-Ing. Stefan Wagenpfeil.

Der Beitrag Experience must be valued more again! erschien zuerst auf Prof. Dr.-Ing. Stefan Wagenpfeil.

Der Beitrag Taking responsibility – despite, with and because of AI erschien zuerst auf Prof. Dr.-Ing. Stefan Wagenpfeil.

Der Beitrag AI is just a human being…. erschien zuerst auf Prof. Dr.-Ing. Stefan Wagenpfeil.