Transcript:

[00:00:00.990]

Nine, eight, seven, six, five, four, three, two, one.

[00:00:21.010]

Hello and welcome to our PROSTEP day. The meeting of the PROSTEP community, I’m so pleased that so many of you have managed to make it today. This is the first time we’re holding this event online live. I can promise you it’s worth taking part. It’s very interactive, very interesting. And we have a great deal prepared for you. I’d like to start by introducing myself.

[00:00:46.570]

I’m Julia the TV host and event host, and I’ll be guiding you through the program today. This is our last session of the day. It will continue until 3:30 pm and we’ll be dealing with product suite OpenPDM.

[00:01:04.450]

We have speakers from PROSTEP, we have a custom presentation and we also have a completely new product that will be presenting to you today, OpenCLM. And what’s interactive about all of this?

[00:01:19.090]

You’ll be getting involved.

[00:01:20.920]

We want you to be able to ask your questions. They’ll then be answered, but we want you to be able to network as well. You can see on your screen that there’s a box for you to enter your questions and you can direct your questions at the speakers, but you can also ask questions of the customer. We’ll go through these questions. I’ll see them on my tablet and then I’ll put them to the experts. Please do ask your questions.

[00:01:47.380]

And what about the networking aspect?

[00:01:49.630]

Well, following the session, there will be a 60 minute session in another team meeting where you can go into a little bit more depth of the issues that were raised.

[00:02:04.450]

You might find it a shame that you’ve missed the first two sessions or you might want to share these sessions with a colleague. Well, that’s not a problem at all. We’re recording these sessions.

[00:02:16.240]

We’re translating everything into English, and you’ll be able to find them online in a few days.

[00:02:26.350]

So this is all from me for now. Obviously, the question is what’s been happening at PROSTEP step recently? We would also like to look at the agenda a bit more closely. There is someone better placed to do so than myself, someone who has been working for the company for 23 years and heads the business unit products. Welcome Peter Pfalzgraf.

[00:02:49.840]

Yeah, welcome back. And also welcome to those who are not with us this morning at our Tech Day.

[00:02:58.720]

Mrs. Bauer has already said that we are now in our third session today from two until half past three, about Open suite PDM

[00:03:10.600]

TechDay is an event at which we can provide detailed information about all of our products. I want to show what has happened over the last few years here.

[00:03:23.800]

So here once again, the agenda for our session this afternoon. In the following slot, we’re going to be talking about novelty’s on topics that have been integrated in the product OpenPDM.

[00:03:36.970]

And I’m also going to address Post-ABC News in general at about 2:25. We want to present a client presentation that Lockheed Martin Aeronautics of America, Clifton Davis, this is also prerecorded.

[00:03:58.060]

But in our Q&A session later on, you will have the possibility to have a live discussion with Clifton. And he’s on the West Coast of America.

[00:04:06.970]

So you can work out for yourself what time that would be half past five in the morning, I presume. But he did promise to be with us. Highlights then the highlights from the PROSTEP Lab.

[00:04:17.740]

It’s about presenting the topics that we’re working on at the moment that will, of course, become highly important in future and in this context, we’ll have a preview on a new product, OpenCLM.

[00:04:33.700]

That’s the first time that we’ll be talking about it. It’s very important for us next year, 2021, and it’s important for us to give you initial preview of this product.

[00:04:43.930]

Last but not least, the roadmap, again, it’s about showing you what specifically we have in planning the new versions, new issues for 2021. And so address topics that are relevant, for OpenPDM  in future.

[00:05:04.810]

And then the Q&A section I said beginning we’ll have two of them, one directly after the client presentation.

[00:05:13.280]

That’s Clifton Davis from Lockheed Martin. And then at the end, a 10 minute session again that worked very well this morning for product managers and everybody else on the team.

[00:05:27.700]

Nevertheless, we’ll have a separate team session, which gives you the possibility to discuss things in a smaller group with our product manager.

[00:05:37.180]

Got the feedback this morning that that worked very well as a small group.

[00:05:41.470]

But you can discuss with our two product managers.

[00:05:52.090]

Now, just a few words about PROSTEP,  these two pictures that with a straight our past, that was our last TechDay at end of 2018.

[00:06:02.140]

So pretty much exactly two years ago here in our neighborhood from where we are today in Darmstadt  computing center in community.

[00:06:11.200]

And we were able to communicate in person with you there today online. But as we’ve seen so far today, it seems to be working very well.

[00:06:19.820]

And this is a picture of our 25th year anniversary. And that was at the beginning of 2019, more than a year ago now, of course.

[00:06:31.120]

But it was a very nice get together with 300 people. And we were able to have a look back at past.

[00:06:41.920]

Last year again novelty’s I’d like to point out to you PROSTEP besides the products of its portfolio, starting with PLM management consulting and continues with our solution components, implementation of projects.

[00:07:01.390]

But then, of course, also in the context of our projects or  specific customer projects. And quite a lot has happened in this area as well.

[00:07:12.760]

In 2019, PROSTEP became a majority stakeholder on GMBH. That’s a consulting company which is positioned in PLM for EE, as it is called. It’s about application lifecycle management, the whole thing in context with PLM systems engineering software development. They’re very much focused on consulting.

[00:07:33.820]

Philip Holidaymaker as the business manager has a team of about 35 people who can significantly extend our competence in consulting. So we see ourselves as a partner of digital transformation  in your company, which is also expressed in the bottom part of this slide. We have white papers for things like, for instance, Industry 4.0 and the context of PLM and digital twin.

[00:08:08.220]

So if you’re interested, you can download these white papers directly from our website. Then our solutions and implementation, again, an important step in 2019 in Poland.

[00:08:24.040]

 We started a new software development center in Cyprus, that Poland from sluff. We have a new team there of software developers who help us in customer’s software projects, particularly with our main clients, but also in product development.

[00:08:41.920]

And that’s a nice connection to the products that we are talking about today, because that team is involved as well, particularly thinking of our new product solution, OpenCLM, but also in the context of PDM.

[00:08:57.010]

Today of our products in total and now, as I said, particularly about OpenPDM, you can see our trends in the market OpenPDM, under the main key integration, OpenCLM on the right as a preview listed as well on the slide that in the following session and what he announced, it’s going to be about OpenPDM, Mrs Bauer.

[00:09:24.190]

Thank you.

[00:09:26.430]

I think we should now talk a little bit about OpenPDM and not just with Mr. Pfalzgraf, but also with another colleague who has been at the company since 1996. He heads product management. Udoh Hering, welcome.

[00:09:40.180]

I have a question for you. I would like to know about the market trends around this issue.

[00:09:47.710]

Oh, well, I’m glad to answer that.  When we talk about OpenDXM GlobalX.

[00:09:55.000]

the same slide here. Here we can see all the known vendors and suppliers of our PLM system.

[00:10:02.170]

And the trend is absolutely clear. They’re all heading towards cloud at the moment. That means all these large vendors have cloud solutions to offer via the cloud and cloud. First, amongst other things, means that this cloud is the cloud vendors. You want to provide a cloud or develop for cloud and then on demand,  offer an on premise solution. So there’s a very clear trend visible there, which we have to confront. And we have done so about looking product manager, Mirko.

[00:10:38.050]

About two and a half years ago, we decided to go to introduce a completely new technology in OpenPDM so that for this cloud scenario which are meant to be used by the vendors, it could be supported the best way possible.

[00:11:00.190]

That means an OpenPDM would have a completely new approach in technology. But of course, our expertise and all the available know how in various connectors is continue to be used.

[00:11:17.320]

We’ve continued that in micro-services, for instance, we have a completely new browser’s engine.

[00:11:29.470]

We have standardized REST interfaces, which, of course, with the integration in such cloud environments, will make things much easier in future.

[00:11:38.290]

And right now, we’re analyzing cloud environment to see what that means for us in the context of deployment capabilities in KUKA.

[00:11:51.250]

That’s going to be something that’s going to be with us the next one or two years.

[00:11:55.480]

Then, of course, the minor issues like the authorization,  and also beyond that, with the new technology, it’s easier for us to make these solutions available to our partners.

[00:12:13.030]

Now, that’s the technology where we are at the moment, where we’re developing, but of course, functionally we have extended our portfolio, for instance, in shipbuilding.

[00:12:25.720]

We’ve been active for many years already. And actually you have exactly the same needs as we know primarily from the automotive sector as well.

[00:12:37.570]

We have completely different PDM landscapes, the quite specific trends, for instance, at the big vendors associations or whatever they may be called.

[00:12:46.940]

But there are also systems like AVEVA, Mudflap, CADMATIC, Mattick, Plastics, etc. These are specific systems that are used in shipbuilding, which have really more to do with factory building because the approach is completely different when you build a ship and in the morning we got to see one that’s completely different than a car.

[00:13:11.110]

And of course, you talk about different numbers as well.

[00:13:14.740]

And you need the respective systems that can support that. And these systems do that. But these systems all have to interact with each other as well.

[00:13:22.870]

And for us, it was an obvious choice to use the technology from OpenPDM, which is there to reflect these processes and extend it by the respective connectors further, as will follow.

[00:13:38.860]

And we have contractors with the respective partners. And my colleague Peter Pfalzgraf talk about that as well, of course.

[00:13:44.950]

And we’re very well equipped for the future, digitalization in shipbuilding in order to be able to support people there as well as we can.

[00:13:57.590]

It’s already been mentioned the last TechDay, CCenter, our collaboration solutions for OpenPDM, you can offer the latest data with PDM CAD structures be made available and in which change processes can be initiated with partners so partners can be incorporated. But the whole thing in a totally separate environment, completely separate from the backend system so that they’re again in the greatest possible IP protection is given. And you don’t have to exert a huge amount of effort so that external partners and suppliers can be given access to your internal systems.

[00:14:42.110]

Because if you’ve done that in this kind of environment, you know what kind of administrative effort that is. But beyond that, the platform offers great options, as my colleague Timo Trautman has already demonstrated. That is because you’re basically using the same technology as in the PDF Generator 3D. We’re certainly going to continue expanding this topic in future and we’ll talk about the details later on.

[00:15:13.970]

And back to Mrs. Bauer.

[00:15:18.080]

Thank you.

[00:15:20.360]

I think we should continue with Mr. Pfalzgraf immediately. What customers use OpenPDM and how is it used?

[00:15:27.890]

I have tried to reflect this on one slide and put together a few examples and customers.

[00:15:34.910]

Right at the beginning we saw this OpenPDM puzzle on the shipbuilding puzzle. The basis is always technological partnerships, which have been running for many years already was addressed in OpenCLM as well as our partnerships with SIEMENS, Dassault, and others ARAS, et cetera, but also an OpenPDM  scheduled.

[00:15:55.790]

The hearing is already mentioned. This is a completely new toolset.

[00:16:00.950]

Also supplies AVEVA, CADMATIC, Artomatic, Néstor and others here. We have expanded our collaboration and on this slide you can see various versions of OpenPDM.

[00:16:14.810]

And here’s how our marketing, this tool as well as these things you can see OpenPDM Connect and Integrate on the left hand side, connect really means system of a link between two systems and integrate is more comprehensive idea, which means you can couple several systems into two customers as examples of very good examples for how that can then develop such a connect solution. Because I have to collect two systems, but then I might need to incorporate further systems in my company that I put something in inverted commas quotes below these reference testimonials and stories which we have published as well.

[00:16:57.080]

You can find them in our newsletter, but just an example. And also we had a project which are called JT Factory.

[00:17:02.420]

It was about providing 3D data in a coupling between experience and SAP here that’s been extended our OpenPDM solution in similar in WEBASTO we had an integration of two solutions together for partner B or C, they offered an SAP based solution 4PEP and that’s connected with 3D Experience.

[00:17:28.730]

But here we’re talking about a further extension even, requirements management system, DOORS for instance and the solution should be further expanded.

[00:17:40.380]

The next column, a very important topic for us is migration. We have a OpenPDM Migrate. We have projects running with Continental. It’s about replacing legacy system and migration towards a Windchill based system, which is the back burning Contee in the automotive sector in general. Just the same with KUKA. It’s a very nice name. Pops up here, you know, the data washing machine,  that’s what they call it in turn, because they said they have a whole lot of legacy systems that have to be replaced.

[00:18:19.460]

That’s going into a new architecture PLM center and on the Upper East Side.

[00:18:25.940]

And we are migrating data more specifically for KUKA that’s been running for one or two years now. And we say typical applications for our migration solutions.

[00:18:40.070]

Collaborate, they’re clearly  working together across companies.

[00:18:44.900]

As you walk around, just by way of example, the company BMW, we’ve run several integration project that’s called __________. With BMW, we work with other OEMs, zero point five tier suppliers as another expression used with launching a new product.

[00:19:04.800]

They were not allowed to talk about it right now, but it’s certainly a continuous issue, similar for Bombardier, but it’s about building train.

[00:19:14.550]

And here from is working on large train projects to build trains together. It’s known in the past that with Siemens at the time they built the ICE and it’s currently got a brand new project we’ve started. And probably at the next TechDay will be allowed to present the name and talk about the project at the moment. Not yet. Last but not least, OpenPDM Ship as we’ve already found.

[00:19:41.490]

That’s a completely that’s a world of its own and their main point this hour. Now, if you have any questions about that later on in team session next , Mirko Theiss will always going to be available. Who is responsible for shipbuilding in our company? So should there be any specific questions? We can also discuss back then but here as customer projects, we have a project with Meyer Werft it’s about integration between 3DEXPERIENCE, solution and CADMATIC solution. That’s a ship specific management system.

[00:20:18.890]

And here folks who were a Hong from Singapore, they integrate the design world of manufacturing, world of marine NESTIX and we’ve integrated that we used to the customer. So you can see a huge bandwidth which covers our OpenPDM suite.

[00:20:40.400]

These are very interesting current issues. But, Mr. Hering, let’s look into the future. What can we expect from OpenPDM in the future?

[00:20:51.000]

That’s before we get to talk about that.

[00:20:52.900]

I would just like to highlight two development projects where we are involved of our PDM expertise that is set level four to five. It’s about autonomous driving at this point.

[00:21:08.430]

And set level five is a fully autonomous vehicle that can drive without a driver. And for it’s the precursor level. But in this set, level four to five, project , it’s about to simulate the development to get the testing.

[00:21:35.010]

And the data obviously have to be provided that were made available for the approval of these vehicles.

[00:21:45.030]

That means they have to be seamlessly traceable and in this context, we become active.

[00:21:52.590]

So a traceability solution is being developed. It’s called Tracy. That’s the name of the project. You could argue who came first  our product idea, as Mr. Pfalzgraf indicated before, was there first and then the project followed. But we’re very able to incorporate our knowledge at this point. The next project, all supported by .BMW, a smaller consortium, if you compare that to set level 4 to 5, project to project that level four to five.

[00:22:31.180]

It’s about building a digital twin for monitoring processes and optimizing processes, to manufacturing and assembly.

[00:22:46.190]

There’s a great need for optimization. And with our experience that we have in shipbuilding at this point, we can support people so that the respective processes can be optimized.

[00:22:57.640]

And of course, the data can be presented in a usual data model, all of which can then be continued to be used in other companies in other areas.

[00:23:10.660]

Last but not least.

[00:23:19.120]

What else is there in OpenPDM. Mirko Theiss will address that as well later on. But I’ve already pointed it out. The driver, cloud readiness.

[00:23:29.080]

We will, of course, make sure that dock environments Khubani is OK and shift this kind of technology can be supported.

[00:23:40.420]

Better to be able to scale more easily. We’re at it.

[00:23:45.880]

Of course, it will take a while for things to be implemented fully, but that’s going to be a major topic the next two years. Last but not least, we want functional extensions as well.

[00:23:54.880]

We need that. It’s more like ALM systems, for instance, integration plan is planned to save them systems like from Oracle Primavera, even that was just totally a rough outlook.

[00:24:13.300]

And I would like to pass back to Mrs. Bauer.

[00:24:18.610]

Thank you.

[00:24:19.930]

A rough idea of the future and first insights into OpenPDM. We already mentioned the last TechDay they took place two years ago. So a great deal has changed. We want to tell you about this. Who’s going to do so? Well someone who knows a lot about the subject. And he has worked at PROSTEP for fifteen years, is the deputy head of the business unit PLM, and has been responsible for OpenPDM since 2017. Welcome, Mirko Theis.

[00:24:51.370]

Yeah. Thank you, Mrs. Bauer. Welcome from my side as well to the entire PDM team. We’d like to welcome you as well in the next five minutes. I would like to show you a little bit of what we have been developing over the last two years. My colleagues, Mr. Hering, Mr. Pfalzgraf, already shown how we integrated that have used it in projects. And now we would like to talk about the level below that technology, as one of our customers.

[00:25:24.310]

And it’s like a Swiss Army knife. And now we announced that two years ago, at last TechDay, we thought for a long time to begin to deal with, integrate, collaborate in our solutions. And we’ve seen that their actively in use with our customers.

[00:25:39.460]

And we’d also announced that we will have a new release of OpenPDM 9 of micro-services architecture and also a cloud. And what did we do?

[00:25:52.870]

What new things were there? Connectivity and new solutions. And on the one hand, of course, you have two new OpenPDM 8 releases last year, OpenPDM 8.6  and this year 8.7. That means the inverted commas, old architecture is still in use and supported but made use of last two years to develop the new OpenPDM 9, which had its release last year.

[00:26:24.080]

In the meantime, we’re preparing for this open PDM 9.2 which you will get to see connectors and we have new OpenPDM 8 connector for a customer PTC Integrity Connector.

[00:26:39.190]

And that means these days it’s called Windchill RV. And that’s when you’re going to rename our Connector, of course, as the vendor calls it.

[00:26:48.610]

And then we have connectors for 8 and 9. So customers, you can use Windchill integrity can also use this for E!  We have also OSLC provider.

[00:27:05.710]

OpenPDM supplies near OSLC, provided all current systems which we already support for connectors with.

[00:27:14.620]

That means we can I believe that we can offer an OSLC interface for any system for our provider and to implement them.

[00:27:28.510]

OpenCLM  is an issue that has been mentioned several times already that traceability, particularly in ALM sector and now we have a JIRA? Connector which can be used in PDM. The solutions I’ve already said that we are constantly thinking about new solutions for specific solutions, one can apply preconfigured  processes were not just offer connectivity, but real use cases. On the one hand, you have the entire connectivity think world for PTC. And of course, that’s an obvious choice.

[00:28:06.690]

And we provide non PTC information I think works has the IOT platform needs data and information on other systems to obviously help those with him and a complaint system.

[00:28:22.160]

We have to continue EXALEAD. EXALEAD OnePart, which you when you find who’s diametrically opposed, you can do that when the data come from Teamcenter and ensure their safety and you can work within suite and you’re not, the systems can be elected directly.

[00:28:45.640]

And last but not least, OSLC thinking.

[00:28:50.890]

And we’re quite proud of this OSLC provider, which we have was bought by NASA directly from development. The first release is now very productive at NASA. We’re quite proud that this concept is working and they’re reputable customers using it right away. And I think that we’re on the right way, particularly thinking towards OpenCLM, because here we have precisely the kind of connectivity which we look for for OpenCLM.

[00:29:24.220]

In the live session I would like to introduce our new process engine.

[00:29:39.340]

Everybody should hope done the micro services here.

[00:29:43.750]

You can see these micro-services the process and 3DEXPERIENCE connector, and the SAP connector and how with this process, I imagine the graphical process can be worked with. We’ll have a look at that in real life in the post up map so you can see it, because normally OpenPDM works in the background.

[00:30:09.130]

You don’t even realize it’s there and here. I would like to show you how simple OpenPDM processes can be done.

[00:30:21.010]

We have reworked our process cockpit graphical interfaces so that at any time you can see what status your processes are at and the monitoring is being re-worked as well. So that particularly for the administrator, it’s very simple to identify errors, to remedy them and continue working.

[00:30:40.990]

But you see that in the PROSTEP lab live in a moment.

[00:30:45.760]

Yes, thank you. And I’d like to remind our viewers that we look forward to receiving your questions. You might have questions for our speakers here. Please send them to us. We’ll answer them in the Q&A session at the end. You can also ask questions to the speaker speaking now. He will be joining us live following his pre-recorded video and then we’ll hold a Q&A session with him.

[00:31:12.280]

So at this point, I’ll be switching into English because our next guest is actually at the west coast of the United States. We have a prerecorded video that he sent in and it’s going to be really, really interesting. Now, who is going to be this guest? Who is going to get up so early for our session later on? He’s a technical fellow at Lockheed Martin Aeronautics and he’s currently assigned to the post as business architect for the engineering and technology organization.

[00:31:37.930]

He’s really experienced. He has more than 30 years of experience talking and working in the field of aircraft conceptual design, as well as the development and implementation of new engineering tools and processes. He’s now going to talk about and explain the role of OpenPDM within the PLM landscape. And I’m really happy to give it up now to the video message of Clifton Davies.

[00:32:05.020]

Welcome to PROSTEP TechDay 2020. I get the pleasure of presenting for Lockheed Martin Aeronautics. I’m Clifton Davies. I’m a technical fellow for Lockheed Martin Aeronautics and an engineering business architect. And I’m here to give you a brief overview of the project we did with PROSTEP. Integrating, using PROSTEP skills to integrate 3DX with our downstream business system applications.  A very quick introduction to who you’re talking to, so Lockheed Martin is the worldwide aerospace and defense contractor that has four large divisions, space missiles and fire control, rotary and mission systems.

[00:32:49.010]

And where this project was conducted is in the aeronautics sector that does fighters, airlift, advance development, which is where this project was taking place in terms of creating new integrations for our new programs in aeronautics. To introduce you to the project, our original vision was to use PROSTEP as a partner to integrate our PLM product data down throughout the manufacturing workflow. In spring of 2019, LMAero selected 3DX as our PLM system for our new programs that are coming up.

[00:33:28.740]

But we had the challenge of doing a very rapid implementation and we knew as part of that we needed to also integrate our business systems to be able to quickly build up our digital thread for our programs. And we had to combine this with a modern integration architecture and try to avoid the point to point integrations that we’ve done in past to be able to maximize our efficiency and flexibility also in the context of our in-house resources were very limited. They were already overloaded with other IT projects and PLM projects and our time frames to be able to meet the demands of our internal customer were very short.

[00:34:05.700]

We needed an integration partner. We had a new PLM system, and we needed somebody to be able to bring in those connections to what we call the Big Three PLM, ERP and MES. And based on recommendations, we selected PROSTEP as our partner to be able to accelerate those integrations. Another big change in how we were doing this is that we were going to a service bus or a hub architecture and a micro services approach, which is, as I mentioned before, different than the point to point connectors that we had put in place in previous programs and efforts.

[00:34:40.170]

And we’re going to do that for all system integrations, not just for 3DX. The way that the advanced development programs works at Lockheed Martin, we have quite a few different programs that operate on different networks. And so another important aspect to this is it had to be a template for new programs so that we could take what we did with PROSTEP on this one effort and instantiate it in several other places as we migrated more and more programs to 3DX and the new business system model. The initial scope for the interface between PLM and ERP and MES, was relatively to limit our risk.

[00:35:18.780]

There’s a lot of things you can do to enhance your digital thread with your integrations, with your downstream systems, but for this project to try to get the essentials into place, you know, our interface has had to deal with getting fundamental part information down to SAP. So the material masters and the MBOM. Getting work centers from SAP back up into 3DExperience, where we’re doing all of our detailed planning and then bringing work instructions and links to the graphics down to iBaseT for execution in the MES system.

[00:35:53.280]

If you look at the diagram in the bottom, you can see the different elements of the high level architecture, our integration buses, red hats for use and as opposed to the product that PROSTEP sells, is that part of their product portfolio. So that was part of the challenge to PROSTEP is to not be able to use their own off the shelf integration service. We had them use a third party system to be able to perform the integrations because that was our our corporate standard.

[00:36:28.370]

So the overall technical approach that PROSTEP came up with to be able to execute this project in a timely manner was to go ahead and leverage their existing capabilities in terms of their connectivity to 3DX and their expertise with that and leverage their OpenPDM Fuse toolkit to be able to connect to the other parts of our of our enterprise. So fundamentally, we had 3DX connectivity, the 3DX to be able to talk to Fuse. Within fuse, you had it executing the business logic, the workflows, mapping, cues, and other capabilities and keeping all of those within the service bus and exposing the net result as Web services to other systems that needed to be extract information.

[00:37:15.110]

And then the OpenPDM Fuse toolkit was also used to talk to the system specific scripts which then talked to SAP into iBaseT to be able to communicate with them. So high level example, this is the 3DX to SAP integration of what the architecture kind of looks like in terms of the actual implementation of getting it to work, and I’ll walk through this step by step. So for our particular case, the first thing that happens in getting information transferred from SAP is there’s an event trigger in 3DX in the fully automated case where events like this or transfers like this would be triggered by workflows or manufacturing organization wasn’t quite ready for that yet.

[00:38:08.380]

So we’re doing a manual trigger to be able to activate the Web services that PROSTEP exposes. The controllers, then pass to the fuse,server, which has the Lockheed specific business for and it goes ahead and then triggers the exports using the PROSTEP 3DX connectors to use the various Dassault mechanisms, such as XPDM, their Java interface, to be able to pull in this particular case, the information out of the manufacturing part of the data model, 3DX, the mid and et cetera, and pulling that into fuse to be able to go ahead and perform the operations.

[00:38:48.220]

PROSTEP then takes the the data that’s brought into the .fuse and goes ahead and performs their operations and formatting and translations and logic as dictated by the Lockheed Martin specification to be able to transfer that information or translate it into the forms to that our version of SAP needs and send it to the correct location. And then once that that information is transferred, it’s then brought back down and sent through the normal SAP pipo Web services into SAP for consumption. A last step in there that’s not documented.

[00:39:25.840]

Is the we do send a return code back to 3DX demonstrating and the success and providing an identifier to show that the transaction was successful and where it was recorded. An example, I’ll go through two examples here and a little bit more detail for the MBOM case. So we talked about on the previous slide on the the MBOM trigger that starts in three 3DX Delmia. So we use 3DX knowledge where to be able to go ahead and create a button that is able to trigger the Web services.

[00:40:04.320]

So it’s able to extract the information from Delmia that is needed for the particular object you’re standing on. Send that to the Web service, OpenPDM then gets that information from 3DX from the Web service and then connects back into 3DX using the connector and then uses their knowledge and their capability to be able to get the MBOM , the implement links to follow the scope links, manufacturing responsibility and effectivity. So for those of you familiar with 3DX and the fact that you’re not copying information from engineering to manufacturing, that requires a significant amount of traversal of the 3DX data structure to be able to gather all that information and PROSTEP a great job of that with the tools that are available to them.

[00:40:48.120]

So I’ve got the information in the service bus. I performed the operations on it and then I have to split that into two parallel routes. Part of it’s got to go to SAP and part of it has to go to iBaseT the MES system. So I have two parallel routes that are created. The ERP import is handled in FUSE using the PIPO Web services, as we talked about before, and you send your material master and MBOM and change master down to SAP.

[00:41:15.270]

And this is probably no different than almost any any enterprise. It’s not unique to aerospace. The MES import is then handled also by a FUSE. But taking that data, transfer it to a OAGIS format, which is what iBaseT uses as their standard and using their sync BOMcapability to be able to go ahead. And once you drop the data in active MQ, they go ahead and reach that for that information and bring that into iBaseT. For the routings, which is another case, we’re not just sending parts now, we’re actually sending manufacturing planning detailed information from 3DX Delmia down to iBaseT. We have a similar mechanism in terms of we’re doing a manual interface, we have a trigger within 3DX within Delmia to stand on a routing and send it to iBaseT.

[00:42:12.040]

OpenPDM again goes through the interfaces through XPDM but pulls different sets of information and traverses different parts of the product structure to be able to get the information into the service bus. So they extract the MBOM implements links, scope links, and et cetera, that are all part of the detailed planning that’s done within 3DX. I guess that is one thing I should mention is that we are doing all of our detailed planning in 3DX in the PLM system as opposed to down in the MES system.

[00:42:40.090]

So that’s why all of this information has to be pulled from from 3DX Delmia. So once the information’s there and any transformation’s and business logic take place, the data is then sent to SAP using the same PIPO mechanism. But then it’s a group idea sent back from SAP that 3DX doesn’t know about that’s required for the iBaseT import. The ERP import is handled that translates to your work centers, your routings and your plant allocation all down to SAP automatically.

[00:43:17.740]

And then the MES import is handled also again mapping to the OAGIS format using the sync routing via service from iBaseT and then pushed into active MQ for it to be able to go ahead and ingest that information. So what we’re having is that the detailed planning information that was originally developed in the PLM system to be able to give you that full digital thread continuity between engineering and manufacturing is now communicated down to iBaseT for execution. So at a high level, the results of what we’ve gotten so far in terms of this project and again, as I mentioned, we’re  at a limited scope.

[00:44:00.940]

There’s a lot more that we need to do. But this is as far as we’ve gotten with PROSETEP so far and it’s been successful. But some interesting results that we’ve had. We started out in 3DX 2019x and per hour schedule for our 3DX upgrades. We switch to 2020x or upgraded during the middle of this project. And one of the really nice things that that happened based on the the capability of the PROSTEP COTS tools in terms of their, their integration and connectors, but also the capability of their team.

[00:44:37.450]

And the code that they deliver to us is that it was an almost immediate update from them. I think it took less than 24 hours for the team to be able to go ahead and take their set up, be able to upgrade their connectors to the 2020x version and make any tweaks needed to their their integration code and have us up and running again in a very, very short period of time. So that was much faster than we ever could have done ourselves.

[00:45:07.870]

And it was a really nice surprise. We do have the material master and MBOMs information successfully being pulled from 3DX Delmia and sent down to SAP. Right now, is it mentioned where you’re currently using xPDM, which has its own challenges.  And so we’re anticipating an upgrade to the Dassault RESTful APIs in 2021 when they’re made available to us to be able to go to a full micro-services architecture that we really want to do with our our business system applications.

[00:45:40.120]

But that said, the PROSTEP xPDM adapter met all of our requirements and was later supplemented by some Java APIs when when there were some limitations of xPDM discovered for what we were trying to do. Lockheed Martin is using a rather new business model following the Dassault recommendation on how to use the manufacturing data structures within 3DX. And so there were some things that, while they were implemented correctly in their product, hadn’t quite necessarily rippled down through to their their interfaces yet.

[00:46:10.540]

So PROSTEP did a great job of being able to supplement the Dassault out of the box capability in xPDM. Another thing that was essential in this is PROSTEP demonstrated excellent teaming and flexibility, not only with Lockheed Martin and our folks, but working with Dassault  with the FUSE, the service plus integration team, the MES team and the SAP team in a very short period of time, they were welcomed on board as an essential, integral part of the team.

[00:46:41.260]

And and the barriers kind of dropped very quickly between who was internal and who was external. It was just a team trying to get something done.

[00:46:50.410]

Their delivery of their code was seamlessly transitioned to the LM team for long term maintenance. That was part of the concept of our contract was, you know, PROSTEP offer several different ways, as any service person does, to be able to go ahead and implement a project, you know, if you want to own it yourself or you need somebody to maintain that long term. And they transitioned it to us into a long term maintenance so that we can be self-sufficient with this integration in the future.

[00:47:21.450]

And that said, we we in the recent past to again increase the scope of this project from just SAO to supporting iBaseT, and they were able to very quickly absorb those additional requirements and shift gears from supporting just the ERP system and start supporting the MES system. So, you know, we’ve completed the SAP work. We’re in process with the iBaseT work in terms of MES. We do have the work instructions, routing transfer for iBaseT working successfully and we’re looking forward to in the future.

[00:47:53.440]

We’re waiting for an update from Dassault to be able to go ahead and complete bringing work center data from SAP back up into 3DX so very quickly, some lessons learned. You know, as Project lead to this, I am not an IT expert, but these are lessons learned that happens sometimes in almost any project. And in our case, multiple firsts can add significant risks. We had a new PLM system, a new PLM planning process, a new way of using a service for integrations.

[00:48:24.270]

And we had some scheduled dependencies between those that were obvious during the initial planning. So as in any project, when you’re trying to do several things for the very first time, you can wind up paying the price for that. Vendor selection is really crucial for these kind of projects. When you have somebody to bring in expertise and you have a somewhat chaotic situation where you do something new internally with new teams, it’s very important to to bring in a good vendor that can can really adapt to your team and your experience and be flexible.

[00:48:55.890]

So PROSTEP brought in 3DX integration experience and FUSE experience that was critical to the making the project succeed. You know, we focused on our open enterprise and our service bus, and that really worked with very well with PROSTEP in terms of their ability to step up and and work with a third party bus. And their agility was essential to this because in many cases they were waiting on Lockheed Martin as our understanding of 3DX and the new manufacturing processes was maturing on a daily and weekly basis.

[00:49:27.360]

And we had to adapt. And the way we changed the requirements on beneath underneath them on the fly, and they did really well at making still making the project successful. So again, we had some aggressive guidelines, timelines that we were able to see to succeed. But a lot of those were happening because we were debating technical solutions for strategic solutions. And that’s something we all face, which is, you know, what do you need to do to get it done quickly and get something working versus getting working it right so that in the long term it’s a successful integration architecture and perfect can be the enemy of good enough.

[00:50:07.500]

And our example of using a a knowledge worker trigger inside Delmia to trigger the interface versus waiting for the perfect answer of workflow triggers and making it work seamlessly allows us to go ahead and go forward and get the programs working without having to wait for the perfect answer. So again, thank you again to the the PROSTEP team for all that they did for us. They did a great job and they’re still working and things are succeeding still.

[00:50:36.210]

So that’s the short version of the integration at Lockheed Martin has been done using 3DX and PROSTEP, talking to our business systems. Feel free to join us for the Q&A session after this to be able to go ahead and answer any questions that you have regarding our integration project with PROSTEP. Thank you.

[00:51:00.310]

That was Clifton Davies via video message, but now he’s with us life, a very wonderful. Good morning, Mr. Davies.

[00:51:08.110]

Good morning. Thank you so much. This has been a great presentation. I especially love the touch with the American flag in the background. It’s been quite some interesting times over there. So thank you so much for getting up early and taking time for us. And obviously, it’s been quite inspirational. So we’ve received quite some questions for you. And I’ll just go down one by one, if that’s OK with you.

[00:51:28.630]

The first one is what efforts does it roughly take to adapt existing processes?

[00:51:39.890]

Process adaptation mostly took place in the new PLM we are adapting to. That was actually more difficult in adapting our manufacturing processes than it was to adapt our integration processes to PROSTEP’s connectors and using a an open source service bus as the method to communicate between business systems.

[00:52:10.940]

Thank you so much for that.

[00:52:12.460]

The second question that came in, do you run OpenPDM 8 or OpenPDM 9 in your solution?

[00:52:21.690]

We are currently using OpenPDM 8. We had looked to transition to open PDM nine, but that did not to fit in with our schedule, with all of the other upgrades happening on this complex project. So open the OpenPDM 9 upgrade is being deferred to 2021 to align with this also adapting to the new micro services APIs in the PLM system. So we will use the new technology and OpenPDM 9. At the same time we use the restful APIs and other new APIs exposed by Dassault and iBaseT.

[00:53:12.120]

So more interesting stuff. Coming up, a third question that we’ve received is do you plan to integrate other PLM systems or other subsidiary of Lockheed in the integration platform?

[00:53:26.670]

Yes. We and Lockheed Martin Aeronautics have two main PLM systems that we use, Siemens Teamcenter and Dassault 3DX. Right now, 3DX is the only one integrated using PROSTEP technology and the FUSE service bus. But we plan on integration with Teamcenter in the near future.

[00:53:53.220]

Sounds interesting. Thank you. And how many users are actually working with the integrated solutions and what is plan for the future?

[00:54:03.830]

We have not deployed it to the customer yet, it’s currently in final testing and plan to be deployed hopefully before the end of the year. And as I mentioned, our future plans have to do with accommodating the technology upgrades in 3DX, version2020x in terms of the APIs and expanding the interface between the PLM system, the ERP and the MES to instead of having kind of a one way transaction to having the full bidirectional information so that your design and manufacturing community in the PLM system has much better awareness of what’s happening in the other business systems so that they can make better decisions.

[00:55:01.640]

Thank you.

[00:55:02.900]

Another question just came in before I was about to put the iPad aside, so it says you mentioned limitations in xPDM, which you addressed with Java API or REST services. What are the main xPDM limitations that you’ve encountered?

[00:55:23.170]

I’m probably not the right expert to speak to that, because that was something PROSTEP handled, but there are challenges in the use of xPDM to traverse some of the more recent product structure changes in the PLM system in 3DX.

[00:55:44.740]

And so sometimes we had to adapt to the the the difference in readiness level between xPDM and the manufacturing data model techniques in use in the Delmia product in 3DX.

[00:56:05.780]

Mr. Davies, thank you very, very much for being with us here. Obviously, a great remaining day. Stay healthy and maybe we’ll see you some other time.

[00:56:12.980]

Thank you so much.

[00:56:15.180]

Thank you.

[00:56:19.050]

We will now continue with something that’s very interesting. We’ll be talking about integration processes and how they can be graphically modulated. And that is one highlight from the PROSTEP lab. Mirko Theiss, over to you.

[00:56:35.150]

Welcome back. Also from my side has already announced by Mrs. Bauer, I am planning to present a new process engine live.

[00:56:46.670]

Before we get started with these processes, though, I just like to tell you a little bit about the technical background, what OpenPDM 9 actually means and which technologies are used.

[00:56:57.860]

Two years ago, we had announced already that with OpenPDM 9 we’re going to  switch entirely to Java 11. The long supported release of Java also openJT is going to be supported.

[00:57:13.160]

We’re going to adopt JDK. But if you use different JDK, then we don’t see any problems that you think this is as well. But officially we support adopt JDK.

[00:57:33.110]

We’ve broken it down into micro services.

[00:57:42.350]

So what you know you can already do with OpenPDM 8,  is taken care of by many different services which are broken down functionally and can also operate independently.

[00:57:52.760]

Why did we do that, having already introduced that before? But we’re going to the cloud. You’re going to join us going to the cloud. And Corona is actually accelerating that tremendously we can tell. And we can see that later on the roadmap. And it’s only by breaking it down this way into a monolithic architecture in such micro services can merge to the cloud. And I think at this point, we have taken exactly the right architectural decision looking at today’s requirements.

[00:58:21.350]

And of course, we going to support all communications based on the REST protocols as cloud architectures simply required today.

[00:58:34.790]

What’s that mean for our connectors?

[00:58:36.380]

We also have an export logic so workers who can autonomously the import and export data from the systems to the connectors before they used to be part on base.

[00:58:48.770]

Now they are part of the connectors and such architectures as just presented by Cliff are possible established connectivity to other service buses and platforms.

[00:59:07.880]

And that means you have to more options to get to PLM systems.

[00:59:10.880]

And of course we’ve done something to our process engine.

[00:59:13.160]

We’ve announced that already that we’re going to ,move away from our Java based engine ourselves and much, much more open source here.

[00:59:26.480]

And after open so many tests, decided to use them on the tests a VPM based process engine.

[00:59:35.300]

And I would like to present that in the next few minutes.

[00:59:43.700]

So what do you have in mind listening to Timo Trautman this morning, these days, no product can make without using Excel and according I thought we’ll just export process based on Excel.

[00:59:57.680]

We can have an Excel spreadsheet with a few tasks and each line Excel sheet. It’s a task, we’ll map it and import it into  3DX.

[01:00:09.120]

In just a moment, where’s my mouse with my he is my mouse 3DEXPERIENCE.

[01:00:21.050]

We’re going to edit this process so you can see how simply this process can be edited.

[01:00:24.740]

And then we’re going to import the same Excel sheet to Windchill.

[01:00:32.720]

What does the architecture look like? So if you have an idea and the technology is what you’re going to see most applications run on my laptop here.

[01:00:43.400]

That means we’re going to start my process to look at the process, the processes then deployed in OpenPDM micro-services and carried out as well as during execution we can access many other services. For instance, the mapping service, which is also on my laptop and the 3DEXPERIENCE connector.

[01:01:04.940]

And second step, the Windchill connector, which run our test center OpenPDM system.

[01:01:13.940]

Now, that’s enough on the background and enough of PowerPoint.

[01:01:17.990]

I think that we should just look at the whole thing in real life and let’s get started with the process.

[01:01:24.680]

 I’d already said our processes in future are going to be based on VPM standard they’re going to be graphically modeled.

[01:01:34.220]

That means we have a model with which I can simply drag tasks.

[01:01:41.180]

You need to edit them accordingly to get the OpenPDM predefined templates that can be connected.

[01:01:48.350]

You can also build your own templates so that the specific processes can be implemented.

[01:01:55.130]

And that way this process is orchestrated, to put it in simple words, to unify behind the arrows between the different tasks. Now, for 15 minutes, of course, it’s quite a lot to click a process like this together. So of course, I prepared this beforehand.

[01:02:12.920]

What you can see on the top line is our OpenPDM process is always there and people always supply that.

[01:02:22.490]

What does this whole process do?

[01:02:25.730]

It prepares the entire OpenPDM integration. That means the process is set up.

[01:02:32.300]

It’s prepared.

[01:02:33.240]

So you have all the data which you’ll need for system integration.

[01:02:43.260]

Of course, the process is ended in a controlled manner. Well, we can report every process has a report and we’ll look at that live as well to see what it looks like.

[01:02:54.360]

And last but not least, the very important errors occur again and again.

[01:03:00.000]

We do have error handling and error handling has to be carried out in a controlled manner as well. And we’ve prepared that as well.

[01:03:07.560]

And if you started this preparation, then you can see how the lines here, the top line deals with reading the Excel file and mapping the data to the 3DExperience.

[01:03:20.220]

And then when I have an imported the data and we’ve updated them as well, so you can see right away that the update also work. But we’ll do that in one process, because we don’t have much time to import/update the data right away, to gain a bit of time and update.

[01:03:38.980]

And once we’ve carried out this process, I’m going to structure it so that down the bottom line becomes activated.

[01:03:49.680]

Mapping to  Windchill and import to Windchill will be carried out.

[01:03:55.080]

When you click on these things, then you can see exactly how the fields that you can pick on these tasks depending on which template you select.

[01:04:06.030]

And OpenPDM got quite a lot of templates already prepared template, which is basically the standard use cases you always need for standard integration.

[01:04:16.530]

And of course, we’re going to put them in the next places.

[01:04:21.510]

More and more of our new products are switching to OpenPDM or a starting with OpenPDM 9.0. And that’s how we’re going to proceed. Now we’re going to have a look at the whole thing.

[01:04:31.770]

So I’m going to switch to the process server. I’m going to start with the new cockpit.

[01:04:39.570]

You can see the cockpit you can see that no process is running we don’t have a problem. And there’s no process waiting for human interaction.

[01:04:52.140]

So we’ve got to process definitions deployed in this process, which, of course, is always deployed.

[01:05:00.720]

And I’ve got one more process deployed. The process, if I click on this, then we can see exactly the same graphical interface because it gets in the administration interface.

[01:05:16.080]

Now, let’s start the process. I’ll just do that manually so that you can see it manually.

[01:05:23.220]

So I’m going to do this by hand.

[01:05:28.530]

Using the task list, that’s possible to test processes just as now to carry out a demo. Now I’m just going to click on Start Process and select the respective templates.

[01:05:45.980]

I’m going to enter a business case so that this process can be found better later on and it will start a process if I don’t get into that here and then.

[01:05:57.130]

And then you have a time stamp isn’t as easy to read as 3Dexperience demo of course.

[01:06:05.510]

Now, you see the processes running at the moment and updating the structure. And after the updates, then it will prepare.

[01:06:17.300]

Re-import, when I click on this, I can see what for many that have this stuff done naturally here at line and one small dot.

[01:06:27.260]

So that is where the process instance is right now.

[01:06:30.650]

So we’ve got graphical feedback as well by process.

[01:06:34.520]

Then let’s go back. And the process should have been completed successfully and that’s how it is. Let’s go to 3DExperience and have a look and see what is important.

[01:06:44.300]

These are different tasks for which of them to be carried out and upgrade by the panel. Got it done on the section..

[01:07:01.450]

The tasks, so these tasks can be easily started.

[01:07:06.310]

We’ve provided a small text file and a text that a few so it’s easier when you’re processing the task now.

[01:07:13.470]

The session has recovered, so the data are loaded and I can see the tasks down here. They’ve been imported.

[01:07:21.320]

And that is also precisely what we had in our Excel sheet.

[01:07:26.780]

And if I look at these tasks in detail, then I can see that each of these tasks also has an attached document which I could work on, download the demo, and TechDay colleagues have also left their open PDF logo behind.

[01:07:51.910]

So that was 3DExperience. Let’s have a brief look to see how it is for change he process.

[01:07:59.650]

At this point.

[01:08:00.310]

I’ll just use a different PLM system.

[01:08:03.520]

That means I’m going to break down the process in such a way that the connection is no longer with the task to then go to through 3DExperience and 3DExperience mapping.

[01:08:15.220]

But now I’m able to connect the process, flow, orchestration, all the parts after the file to mapping to Windchill.

[01:08:25.300]

And here we have a Windchill connector addressed to our test system.

[01:08:31.720]

And the map data are then imported so that at this point the import worker on the uninsured is dressed.

[01:08:41.710]

They are automatically imported. And before we deployed, we should store it before and then deploy..

[01:08:51.610]

That’s very simple in my development environment. The process is now deployed on the process server.

[01:08:57.790]

I can go back to my cockpit and if I go to my cockpit, then here it looks like this is the last version that to run.

[01:09:07.690]

But I can see that the new version 37 and they have this process is now running Windchill and the next instance, which is on the imported Windchill.

[01:09:22.090]

So we really have a version control of our process server and the server would allow instances that are running and not disturbed by such a deployment.

[01:09:33.020]

Now we’re going to start the process the same way we’ve just done it , will enter Windchill demo and  start the process over again,  and we’ll go back to the processes.

[01:09:46.360]

You can see of this process is running. And I hope and I think that it will be helpful encounter and error  right away.

[01:09:55.900]

And at this point I’d like to process monitoring the new process monitoring, which I’ve already announced on the last slide last session.

[01:10:09.820]

Here is the error. Thank goodness for expecting it this time. But the question is, how can I find out what I have to do as the administrator in order to resolve this problem?

[01:10:21.430]

So I go into process monitoring and I can see that the process has six steps in total. The first five of these run successfully from the sixth one. There is a mistake and error. I can look at details and I hope that it’s not too small.

[01:10:35.860]

But I’ll just tell you that a word file was not found.

[01:10:41.770]

And what is not there cannot be uploaded the server. And accordingly, the system reports an error. ,So why can OpenPDM not find it?

[01:10:52.060]

I quite deliberately entered a wrong file. Now, I’m going to correct this file name as an administrator, I have found the mistake. Imagine it would be a network problem.

[01:11:05.910]

You’ve just fixed and found and as an administrator, of course, I don’t want to call the engineer and say please stop the process.

[01:11:18.010]

I re-established network connection.

[01:11:20.290]

No, you want to restart the process immediately.

[01:11:25.120]

To get the data into the system and I’ve done that on the administration. So right away, that means your colleagues didn’t notice that there was a slight network problem.

[01:11:35.530]

You the message something has to be corrected and you were able to trigger the process from the administration console. And as I’ve now entered the right name, that has happened successfully.

[01:11:50.560]

If we look at the whole thing in Windchill and update it, then we can see here we have tasks.

[01:11:57.850]

As Windchill notes and the word document.

[01:12:04.900]

is also attached to notes and open it opens OpenPDM.

[01:12:11.620]

Now, that’s an example of how we design processes together with you and how you can administer them in future.

[01:12:41.710]

This micro-services architecture is highly suitable.

[01:12:42.070]

Thank you very much.

[01:12:46.700]

Thank you Mr. Theiss.  We’ll now move on from open PDM to OpenCLM, what is that? Well, it’s what we announced the start, the new product that we are presenting to you today. It’s all about traceability. It’s about tracing complex processes in the future logically.

[01:13:07.370]

The product manager that will be introducing the new product to you is almost as new as a product itself. He joined the company in March and took on product management. He came from the car manufacturer Sheffler, and now he’s so pleased to be able to introduce his product to you. Welcome, Fabrice Mogo Nem.

[01:13:28.190]

Thank you very much for the nice introduction in 3’s a Charm. So I’m very happy to be here with you in the third session to present our new solution, OpenCLM. As we’ve seen the OpenCLM solution , not only that will help you to better control your complex development processes.

[01:13:47.930]

We believe it is an essential element of digitalisation strategy as that will work, you find after a brief introduction.

[01:13:57.290]

I would like to have a look at the environment that we’re working in as a company.

[01:14:03.110]

As you know, we’re in constant change, and novelty that we’re working together, but we’ll be confronted with.

[01:14:14.330]

The future is higher frequency in which changes novelty’s happen in our business environment and also the unpredictability with which these changes happen and examples of covid-19 pandemics.

[01:14:28.750]

If that is quite taxing at the moment and it shows that on singular event outlooks and planning can be totally turned upside down.

[01:14:40.960]

We don’t have a crystal ball.

[01:14:42.860]

And so we have to make use of other means to be able to prepare better for the future.

[01:14:49.090]

What is the solution in in future we see companies have the necessity to become more flexible. Also potentially innovation, cost reduction, but also risk management.

[01:15:05.390]

You have to exploit all the potential we can find.

[01:15:10.450]

There are possibilities to make use of in simple ways. Some of the potential detected looking at these numbers.

[01:15:26.030]

These are fact that establish that because of insufficient processes.

[01:15:31.880]

There is still plenty of potential which is only waiting for it to be lifted.

[01:15:37.700]

One example, we are losing a lot of our capacity as 61 percent, according to statistics,  and a large part of that shadow work.

[01:15:54.320]

That means work is done that cannot necessarily be billed to your customers.

[01:15:58.070]

And 22 percent of this waste is because documents searching.

[01:16:03.380]

Now, that’s certainly not a new phenomenon for you. That’s pretty well known in many companies.

[01:16:08.390]

Document hunters exist in many companies and

[01:16:13.100]

And we have ways you can give it a try and increase your efficiency.

[01:16:17.930]

There are further numbers which are meant to make us think we are in the United States alone.

[01:16:24.770]

25 billion dollars spent every year on warranty claims.

[01:16:28.760]

If you were to break this down to the automotive industry, that’s nine billion euros which are spent on such claims.

[01:16:37.020]

And that is a considerable number.

[01:16:39.200]

And if you look behind these numbers, a lot of money spent on this is because in development as well as the downstream processes of the development, we did not meet certain compliance requirements for at least not fully of the feeling that it was due to lack of transparency in processes.

[01:17:02.270]

IT landscapes and the databases which are often used to support decision.

[01:17:07.430]

It’s this lack of transparency which leads to such a lack of respect, for compliance rules. We at PROSTEP see plenty of potential here.

[01:17:18.460]

And after optimization of manufacturing industry 4.0 . There are some of the topics like this work management, or compliance and traceability is a cornerstone of your digitalization strategy and future.

[01:17:44.560]

So what’s that look like?

[01:17:45.580]

You can see an example of a potential solution that is going to be all components, which are how many meetings could you save if you had all the information about your development project and develop the maturity at your fingertips?

[01:18:04.030]

Certainly lots of calls could be saved that way.

[01:18:08.770]

Or the development is currently spending a lot of time to integrate data which are beyond barriers and establishing trace’s between data in order to meet compliance requirements, creating transparency requirements who need needed such a complex development project addressing Excel solutions because they have no other choice for you as decision makers most responsible for the complex releases.

[01:18:39.310]

How secure? If you have the possibility to get the information you need for a decision instantly for a traceability report that would give you a lot of certainty, a lot of security in your decisions.

[01:18:52.660]

These are examples that are imaginable, but there are other application scenarios which would come possible with such solution brave enough to keep working on this so that it becomes reality and we have confronted this challenge at PROSTEP. And with this new solution, OpenCLM, we can provide precisely such a platform, which is based on our proven capabilities and have 25 years of experience.

[01:19:19.750]

And we are continuing to build on that, our colleague, Mr. Theiss as presented for integration, that process can look like it’s certainly not possible to imagine it getting simpler. I’m sure he has other ideas about it could be more optimized, but integration has never been so simple. And that’s what we’re based on.

[01:19:40.060]

We have the possibility to enter your system world, you process world, and from there you take all the necessary information process data, project data, we can extract information process it and illustrate it in a suitable way so that the process that the activities can be triggered.

[01:20:02.690]

Our consulting team will support you that, in preparing such an approach in strategic consulting, of course, taking into account experts.

[01:20:14.800]

These are capabilities we have established over the years, and that is what we have based on in OpenCLM.

[01:20:21.640]

You will certainly want to know is OpenCLM a new PDM product or PDM system. Of course not.

[01:20:28.900]

There are plenty of PDM systems in the market and increasingly that companies are moving away from one center pendent strategy to best of breed strategies because they can see that by increased product, strategic complexity and also the need to remain innovative, they have different use cases, their products, their services that are different tools, and we feel more at home in such a heterogenous landscapes because we’ve proven that we have the ability to integrate these worlds andOpenCLM is precisely this layer which offers these additional at all.

[01:21:12.100]

And you have the possibility of seeing in the Lockheed Martin presentation before and in such a landscape our OpenCLM solution, which could also see a smaller version, which enables them to look into the system to get the information, implicit or explicit or implicit the semantic search and intelligence networks and ensure that the traces in the data that belong to it and we illustrate that the process can be supported by the baseline and such baselines.

[01:21:54.610]

Before we heard about this GlobalX, such consideration can  be exchange with partners and also customers and with PDF Generator 3D.

[01:22:05.960]

We have the possibility to pack them based on standards. For instance, with the TDP container, that is a project which I was one of the initiators in VDA  in the PROSTEP iVIP Association. So that we can work on such standards for exchanging network data and operations can be supported.

[01:22:32.560]

When can you buy OpenCLM steps? We developed in January 2021 and a half unbeaten, the first demo version we can offer based on demo and the whole thing will then be available to experience.

[01:22:44.890]

You can interact because we’re involved in several projects and NASA for instance

[01:22:57.190]

We have modules and  system world, DOORS, magicDraw,  Windchill integration traces beyond system boundaries that OpenCLM for such traces can visualize.

[01:23:15.680]

It will only be available on July 21 but beforehand, of course, you’re welcome to get in touch with us so that we can, together with consultant, work on use cases which are most important to you.

[01:23:29.660]

And of course, we also want to make you ready for the use of  OpenCLM.

[01:23:35.070]

Now, back to you, Mrs. Bauer.

[01:23:37.970]

and I’m very happy to be working together in future with OpenCLM.

[01:23:45.380]

We’re also looking forward to the Q&A session that will take place at the end. You will then be able to ask Fabrice Mogo Nem a few questions.

[01:23:54.440]

The future is in the cloud, particularly regarding OpenPDM. This is what we’ve heard about trends and highlights. We’ll now look at the roadmap if it’s correct and Mirko Theiss will tell us.

[01:24:09.680]

Yeah, thank you very much. I think the road map is correct. As every year the outlook for the future.

[01:24:22.530]

What have we planned in future staff and what have we done in the last two years? What did I look like then? Where are we now?

[01:24:32.850]

Now heading towards the future and perhaps an improvement on what our release model look like in future.

[01:24:43.280]

OpenPDM 8, now beginning OpenPDM 9 one release per year in between those patches and system extensions.

[01:24:52.500]

You only have one big release in April.

[01:24:55.650]

But this year we’ve opened PDM 8.7 and the last time in March.

[01:25:03.370]

And now I’m going to switch to biannually, twice annaully release in February and August, in between feature packs and bug fixes.

[01:25:20.400]

That’s important.

[01:25:24.360]

And as Fabrice has just indicated, you’re use to us talking about things long before we release them. And that means these are points we can say now we’re going to announce it.

[01:25:38.190]

Now we’re going to advertise it. But of course, in between will always feature packs.

[01:25:52.260]

What have listed here, the large PLM systems on the market.

[01:25:58.080]

They’ve been listed specifically, of course, for our releases, for all the other connectors out there. But that would be too much to fit on the slide.

[01:26:05.790]

The Windchill ,3DExperience, Teamcenter, and SAP..

[01:26:14.280]

have also indicated when the vendors release their systems and you can see we’re always two months, three months after the official release of the enterprise.

[01:26:27.990]

That’s when the respective connectors will be ready. That’s something I’ve been doing for years and we seem to be getting on fine feel that way.

[01:26:37.800]

And we’re going to do that every six months.

[01:26:42.480]

with OpenPDM 9 now. OpenPDM 8 if it’s technically possible.

[01:26:48.030]

Then each one of these, the major this will of provide provided to update as well.

[01:26:57.180]

We’ll just have to communicate with each other to see whether that’s technically possible.

[01:27:01.830]

Or for instance, the Java version might have changed so much that we might have to switch from OpenPDM 8 to something modern like OpenPDM 9.

[01:27:11.430]

Now the individual features, for OpenPDM 9, as Cliff mentioned, the OSLC provider, which is used at NASA and and can enter class specific locations.

[01:27:34.090]

If you want smaller connectors, from January OpenPDM migrate off switch to nine entirely migration objects which we had at the beginning of Kuka and Continental.

[01:27:47.070]

will be able to run entirely on OpenPDM 9 so that we can use the new technology and support new technologies for the summer planned use to do what’s already been said along cloud with my together with micro service architecture.

[01:28:05.670]

It’s now ready for tests and requirements which we’ve received so far

[01:28:15.480]

You want to get to fared fairly well. There were no problems at all.

[01:28:20.910]

But we also see that 3DExperience, particularly last week, see it through cloud interface.

[01:28:30.630]

So here you can go a step further and see if you’d asked me two years ago, what about integration services for PROSTEP and so on?

[01:28:40.260]

At the time, I couldn’t imagine that COVID 19 is  revitalizing conversation means that we have presales with you, though, so that I do believe that we’re heading precisely in that direction and we’re putting all our efforts into so that, um, we have an OpenPDM cloud version.

[01:29:08.880]

But, something like we presented Docker container and all that.

[01:29:12.600]

That can be done already today. We’re already in that respect.

[01:29:15.840]

There will be new projects solutions.

[01:29:19.180]

Adding, planning Windchill with 3DExperience, if you have the Windchill system and production planning with Delmia and you connect solution with PRSOTEP we’re just thinking whether we should do the same thing with Teamcenter manufacturing stuff with a question mark there, because that’s not official yet.

[01:29:38.320]

But the support of production planning processes, that’s why we see the future for  OpenPDM as well besides the cloud.

[01:29:46.630]

And then, of course, I put it on the back here. But that does not mean that that will be fine by the year 2020.

[01:29:54.210]

To my colleague it’s all quite sad.

[01:29:59.740]

You can see the corner if you can see it slanted and mangled.

[01:30:03.310]

So all the connectors could be *inaudible* these connectors will be released in parallel with this plan that we do based on the project.

[01:30:16.510]

And, of course for OpenCLM, also to very happy that you join us in the chat in a moment.

[01:30:22.810]

Thank you very much and goodbye.

[01:30:25.510]

You are not excused quite yet. We are now going to start our Q&A session and I’m sure there’ll be questions for you, but you will have a bit of a break first, because I’ll start with Mr. Mogo Nem. We’ve received the question, what is meant exactly by indirect areas?

[01:30:47.970]

Indirect areas are basically engineering anything that isn’t manufacturing.

[01:30:53.220]

Short and sweet, very clear.

[01:30:55.080]

Mr. Thiess, over to you. The question for you is some customers are using OpenPDM 8. How do you recommend them moving on to version nine, upgrade or completely new? What about the current licenses?

[01:31:10.290]

Are they valid? And is the maintenance contract valid?

[01:31:15.330]

That was more than one question.

[01:31:19.320]

Let me start from the back.

[01:31:21.360]

The licenses, of course, remain. We didn’t have new licenses and we switched from seven to eight or anything like that, maintenance contract, et cetera.

[01:31:31.560]

That’s precisely why we have maintenance contracts.

[01:31:34.770]

You get the newest release and upgrade recommendation that was just here has been so far.

[01:31:41.990]

I always recommend the OpenPDM upgrade when you update your PLM systems. We see that integration. We see integrate the integration to be the mix between different systems.

[01:31:53.620]

That means if your 3DExperience, Teamcenter, Windchill, Aras or whatever kind of PLM system is updated for the next release, then you have the test phase anyway.

[01:32:03.630]

So that would be a good opportunity to switch to new OpenPDM,  and then also switch to the new processes as illustrated.

[01:32:15.610]

But that needs a bit of work, of course, I tell you right in advance, but it’s not a totally new development.

[01:32:20.920]

We’ll continue with you. You seem to be on a roll. Are there customers that use OSLC based solutions?

[01:32:29.280]

Few, but, yes, it’s been mentioned several times today, in our case, it’s mainly NASA using OSLC provider ours.

[01:32:44.850]

We’re talking to lots of customers about OSLC at the moment.

[01:32:48.920]

And that’s a similar trend to Cloud  Link. Don’t copy data.

[01:32:56.700]

And I think that in future that will be more incoming. That’s why with the OSLC provider we offer a solution to OpenPDM and OpenPDM can do both, copy and link.

[01:33:12.440]

You can also do both listen and ask questions and continuing to read the questions out live. We still have a few to cover, Mr. Theiss. What do you understand by cloud support in OpenPDM?

[01:33:28.370]

I’ve already said cloud, I think if you ask five people go get seven different answers, what they understand cloud to meean. At the moment cloud is morelike renting virtual machine with the known cloud providers like Amazon. And deploy my application there.

[01:33:51.320]

That’s what we see.

[01:33:52.220]

PLM systems are taken from people cellar’s to the cloud, but on a dedicated machine to machine that for  OpenPDM that no big change is really in comparison to what it was like before because of are OpenPDM  can install on your server or on a cloud server.

[01:34:12.920]

That’s exactly the same thing. And I’ve already announced this in the cloud.

[01:34:18.230]

We want to go a step further with cloud services are used, load balancing, database in the cloud should be made available.

[01:34:28.160]

And we are also considering going a step further and offering this integration service.

[01:34:35.550]

But that’s really looking far ahead. I can’t give you any guarantees of that. But we’re looking at the future.

[01:34:43.790]

That’s the right thing to do. I would also like you to help me with the definition, Mr. Theiss. Can you explain what integration as a service is?

[01:34:54.170]

As if I’d known it was coming.

[01:34:55.370]

Integration as a service.  We develop integration in most cases.

[01:35:04.250]

But you don’t operate this integration ourselves. We’ve got administrators, engineers as well.

[01:35:11.530]

Who know a lot about Open PDN, we have a lot of requests from customers who don’t want to do that in future at all.

[01:35:18.050]

And they say we’re going to go to Dassault or Teamcenter in future and have our PLM in the cloud.

[01:35:28.070]

So we don’t want to have OpenPDM ourselves

[01:35:32.060]

Can’t PROSTEP operate that for us? And do this connectivity in the cloud? And I think that that will be one of our jobs in the future to do that as well.

[01:35:43.940]

But  that’s a long shot. That’s the future. We’re still thinking about how that might work. But, well, you just have to look at these things.

[01:35:55.110]

Exactly, and it will work. Thank you. There are no further questions, so thank you to all our listeners, our viewers who are so many questions, but also thank you to our speakers who informed you so well today.

[01:36:12.660]

I have two things to remind you of at this point in time. They’ll now be another session for you. You can continue to exchange ideas with Mr. Theiss. Just look on your screen. There’s a link to another team session. Click on this and you’ll be transferred to that meeting.

[01:36:30.300]

You might obviously want to share these sessions with colleagues that can take part today over the next few days. These sessions will be online. We recorded them. We translated them into English. So there should be no problems for anyone.

[01:36:48.720]

Thank you once again for joining us. It was our first digital event and I think it was a great success. I hope we can do the same in the future.

[01:36:59.340]

Thank you.

[01:37:00.600]

Stay healthy. Goodbye.