娇色导航

Hi everybody, welcome to DEMO, the show where companies come in and show us their new products or features. Today I'm joined by Rob McAveney. He is from Aris and you are the CTO. And you're going to show us the Aris Innovator, right? I am. Okay.

So tell me about what Aris Innovator is, as far as I know, it's a cloud based product lifecycle management tool.

But if you can expand on what that means, sure, so for context, Aras customers, build planes, trains, and automobiles, as well as things like implantable medical devices, or industrial robotics, or even energy drinks. There's complexity involved in doing that.

And many of our customers are using this, this product to build their digital thread, which is what we're going to talk about, okay. And for the most part, the the main users of this would be well, who within a company, really anyone involved with the product.

So anyone, anyone from engineering, procurement, quality control service, anybody that's that's working with the product data would be a user of this. Okay, and you mentioned digital threads. So what does that necessarily mean, in in terms of your scope? Sure.

So the digital thread is really bringing the data, the people in the process all together, to have interconnectedness to have traceability across the product lifecycle.

So if you imagine if you have a problem, that's or an issue that's being reported, how do you trace that back, figure out its root cause, figure out whether the the product is performing up to its original requirements, that's really what it's about is that traceability across the product lifecycle, and the problem that people would have before if they weren't using this product was kind of take a guess it's that they're all in little individual silos, and they don't see this, you know, something at the end of the lifecycle versus something in the beginning.

And maybe they're just focused on this one area here. Exactly, exactly. So you have somebody that's in maintenance, for example, and they don't have any access to the original design, they have no idea why this problem is occurring.

And they have trouble getting through organizational boundaries to actually collaborate with the designers and the people that manufacture the product. That's why I like that term, digital thread, because it's very visual, you can imagine a thread going through the entire stream here. Right, exactly.

Alright, so let's, let's show the demo, or talk about a little bit about what we're what we're going to be seeing.

So I mean, just just high level, digital thread spans the entire product lifecycle, so everything from original design and original concept and requirements, all the way through through the operation of the product.

And what Eric provides is a platform for product lifecycle management, as well as digital thread solutions that bring together a product data platform, local development environment to be able to adapt to different to different use cases, we have an application library that covers a lot of a lot of the the different departments and organizations that will utilize it along the digital thread.

And then we believe in a heterogeneous world in it where you can't buy all your technology from one vendor. So you have to be able to do integrations with other systems that are involved in in this product. That's an excellent point. Yeah.

So okay, so what else we're gonna see here, I think we're jumping straight to software. Okay. All right. So here's Aris Innovator. Just real quick, what use case Are we are we kind of talking about you kind of set us up with this scenario.

So we're gonna we're going to begin with a collaboration session where someone's request has come in to research a problem. We're going to go through how all that research happens, how we're navigating the digital thread to get to the answer.

So here we're looking at Aris Innovator, this is the the the initial screen that the the dashboard.

At the top left, this is really the process part of the digital thread, where I've been assigned tasks through workflows to do things like Approved Documents or sign off on engineering changes.

The top right is the kind of the data side where we have data residing or being being created by all these applications at different stages of the product's lifecycle by different people.

And all this data is coming together in that data integration layer to be able to to handle it all together. And at the bottom of the screen, we're seeing what we call my discussions, which is really like your social feed.

So this is the people part of the digital thread, bring them together to be able to collaborate about this data without having to in advance know who the design engineer that worked on this particular particular item might be.

Now it's important to note that all this is happening in context. So when someone asked me to please investigate, please investigate. I can see what they're asking me to investigate and follow the link.

And now I see the details of my, in this case, my bill of materials of my my extruder assembly. So here we're working with a 3d printer. And this is the extruder extruder sub assembly for that 3d printer and we're collaborating about this thing, okay.

And on the right side, we see the discussion that is now filtered. only to this thing.

So now anybody who comes in and needs to work with the extruder is able to visualize this, we can get into the details of what this user Manish was seeing when they when they created the report.

So we're able to have markup and and view for everybody in the organization.

If we look at what what's called the were used view, we now see all the connections from this thing to other things in the in the digital thread, okay, so we can jump directly to, for example, the parent assembly. So let me open that thing up.

And now we're seeing the full 3d printer as opposed to only the extruder. Okay, right.

And we can we can jump into a 3d visualization of this thing, to be able to, to, you know, spin it and do all sorts of operations to be able to see more detail about what we're looking at, let me just go ahead and zoom in on this thing and isolate it.

Okay. And now we're looking directly at the, at the extruder assembly itself. And, of course, we can rotate this, let me go ahead. And as parts of the bottom or what we're circled exactly those nozzles. At the bottom or circled. So I call them parts.

So now we can explode it and see how this stuff all comes together and kind of kind of get a good look at the at the nozzles themselves. And here I can fall again a link. So this is this is a link between the 3d geometry.

Now back to the data, we're looking at the details of this nozzle itself. And we can see that this was imported from a third party solution for 3d mechanical design, in this case, SolidWorks.

And this is all coming in through that connectivity that we that we talked about at the beginning, right. Other things that are connected. So as part of our research, we might look at the manufacturing process plan. So now we're jumping applications into the Aris manufacturing process planning application.

And we can see all the work instructions for how this thing is assembled. Maybe that's part of the problem, maybe the the nozzles getting clogged, because because we're assembling it wrong, entirely possible.

On the left side, we see a breakdown of all the operations and steps and tools and resources and consume parts that you need.

And on the right side, we're seeing the work instructions, the detailed instructions for how the the technician on the shop floor actually puts this thing together, we jump back to our where use view, we see some other things that that might be of interest.

So here is, in this case, a simulation study. So when we're designing, designing this 3d, this 3d printer, we do lots of simulation to predict how it might perform in different conditions.

Right, and one of the ways we do that is by creating a simulation study that has a bunch of steps that produce a bunch of artifacts.

And if we follow the digital thread through this through this process view of of the simulation, we can get to an artifact which represents the results of my simulation. So let me go ahead and open that. And we can see it in in an image view.

But perhaps more interesting is this 3d view that showing us how the heat distribution happens after I turn the heating element on how that heat propagates through through this nozzle assembly that might have something to do with the clogging.

Let's pretend in this case that it doesn't jump back to jump back to my digital thread thread view, or my were use view and I can see oh, well look, there's another problem report that's actually already been been issued.

And this problem report is indicating that we have nozzle clogging.

So here now we're going to trace the digital thread again, through from nozzle clogging the problem that's been reported, trace it through this corrective action plan, we see that now we have root cause analysis that has actually been been performed against this.

And as we expand that now we can drive into the cars itself. And from the cars we can draw drive into the risk analysis that predicted that this might actually happen.

And from that risk analysis, we can get back to the original extruder part and expand further into the requirements documents to be able to see and follow this this link to see whether or not the the extruder was actually living up to its original requirements.

Okay, so you see that thread is the most important thing is is being able to trace back from the problem back to the original design or vice versa.

Yeah, if you if you have a requirement, you're able to go forward, forward traceability to determine whether it's performing up to its specification.

Now, is it true that there's a bunch of different applications that are being integrated into this, this inter rater platform and like, what would an engineer do have to do if they didn't have this?

You know, pencil and paper or other platforms, email, I'm assuming they would have lots of lots of that kind of thing going on. They'd probably be logging into six or seven different systems to get all this information.

And they wouldn't have really any way to correlate the data between between the systems, because they use different numbering conventions and different naming, they might not even have a license to get into the quality management software, for example, or the manufacturing execution software.

So by going through this digital thread platform, we're able to bring everything together into a single user interface, a single viewpoint right for everyone to collaborate to go and what other people within the company also have access to this.

And that's where, you know, maybe a customer service rep could then absolutely, if the same problem keeps happening over and over again, they can already see that things have been addressed, or they're being worked on kind of a thing. That's absolutely our goal.

And the way we the way we handle licensing not to get into too much detail. But we encourage companies to have 1000s and 1000s of users, we have dozens of companies that have that have 10 or 10,000 or more users that are that are accessing this.

So it's really important to spread that spread the wealth spread. And I think I started with this is cloud based. So this is all a cloud based system that's subscription, no one, you don't have to install anything on your own computers or servers, nothing like that.

Just just subscribe to the SaaS offering. And in you get access to all this. And we include through that offering the connectors to all the relevant engineering and manufacturing qualities. And I know we only focus on a few of the features.

There's a lot of other cool features about this too, right. So where can people go for more details. So aras.com is probably your best bet. That's where you get a lot of detail there.

And you know, we can from there, you can download case studies and watch videos, demos, more detailed demos than we had today. Lots of lots of information on our stuff. Alright, Rob McAveney, thanks again for showing us this. And thanks for the demo. Thank you very much.