Auditing and Reviewing the Design Change in Teamcenter Transcript

Hello, and welcome to the next installment of our Saratech Enablement Series. My name is Andrea Hall, and I'm the Customer Care Manager here at Saratech, and I'll be your host today.

Presenting today, we have Jason West, who's an application.

He was Applications engineer. Now, he's a project manager of PDM Deployments and CAM Solutions here at Saratech, and he'll be teaching you some tips and tricks about Teamcenter, specifically auditing and reviewing the design change. This is part three of his three part series, and so if you'd like to see parts 1 and 2, make sure you check it out on our YouTube channel, will give you that address at the end.

But first, I want to tell you a little bit about Saratech and the enablement series. We've had great success with it so far, and this free online training is the first and third Thursday of the month at 11 AM Pacific.

We usually ran about 30 to 45 minutes, sometimes a little more, sometimes a little less. And our training is always led by subject matter experts.

We cover topics including the Femap, NX, Solid Edge, Teamcenter and much more.

Our goal for the Saratech Enablement Series is just to help you get the most out of your software and we also are here to share knowledge amongst each other and to build a community of users that will help empower each other.

As always, this is an open forum, and so we look forward to you participating in the training.

If you have any questions or comments during the presentation, please type them in the chat box over to the right and I'll kindly interrupt Jason and let them know about your comments and questions.

So please feel free to interact throughout the, throughout the webcast, and with that, I will pass the baton over to Jason.

Hello, everyone. So today, we're going to finish up our third part of the series.

So topics we're going to cover today.

We're going to close out the series with reviewing the engineering change order.

So now we we've gone through the process of taking a look at releasing the document, making the changes.

Now we're going to review it so we can finalize it and and put it into a release state.

So some of the tools that we're going to have inside of our Teamcenter, we're going to be able to do a bomb compare. So we're going to take a look at that so we can make sure we track our changes.

We'll take a look at verifying the two D elements on the drawing.

So we can see how we can use that Compare tool to analyze what physically changed on the prints.

Then, we're going to sign off and complete the engineering change process, and we will take a look at some reports better available inside of Teams, or as well to help manage that.

So, just to recap why we're doing this, we'll take a look in an overview here of where we got to this state.

So, no changes are inevitable.

We're going to have design changes as we go through our design phase.

In the production phase, even after production, you know, there may be some post-production changes that we need to make.

What we fail to realize, sometimes, are everything that really comes into play when we do a design change.

So, looking at drawings, Maybe emotion analysis or structural simulation, so we need to have a way of keeping track of all this, and controlling our products, right?

So, this is where a team center comes into play, because we have all these supporting documents that are vital information to our product, but we don't have a good way of storing it outside of the data management system.

You know, again, to recap: These are all the different documentation that we would have for a specific product.

So, we're able to bring all these together, and manage and control within our system.

Identifying key attributes.

I'm tying that in an item revision level, so, that way we have, are all the information we need at our fingertips.

This is definitely helpful, you know, in just keeping track of design changes. Why did we make changes, revision history?

Being able to go back and look at, you know, the state of our documentation at a certain revision.

And understand why.

And, the single most important, is having a single source of where we're storing all this information apps.

So, through this series, we've taken a look at, you know, the data management process, documenting that change, kicking off some workflows that send this out to the end user, or out to the the CAD designer, where he's only focusing on working in his tools.

So, if you've seen the series, he was inside of solid Edge and inside of Microsoft Outlook, so he never had to go into team Senate to do his job.

So, you know, everything there was happening to help support all of these efforts.

And keep all this information together.

He was so able to just focus on his day to day job and the tools that he's used to.

So, now, we're going to go into our, our last part of our series here, which is documenting the change.

So, we're going to verify the change. We're going to finalize the workflow. We're going to take a look at some reports.

So, let's go ahead and move over to Team Center to take a look at that.

So, in this organization, I have a checker role.

So, again, we've moved through this process from an engineering so engineering, if you remember, we had a document that came out from the field saying that we needed to make a design change to a component on our motorcycle.

That move through engineering, engineering process to change or you know, evaluated the change, created supporting documentation on to say yes, this is a valid change, and sent that off to the CAD designer.

His role was to go in and make the physical changes: update the prints update. 

You know, rub the bill of material, wrap the parts and that was all done through his care products, which were in this case with solid edge, and then he did all of his sign offs inside of Outlook.

So, on the chapter side, they have access to Teamenter. So they're going, we're going to do all of our work today, here, out of Teams.

So the first thing that I got, I got an e-mail, and also when I came into my team center, I see that on my work list, I have an engineering change order that requires a sign off.

So just like in the past, we want to go through and evaluate this.

So we want to look at everything that is Grandma created this point.

So I can go down here and start looking at, OK, I see that there was, uh, our change request that was filled out, Um, no parts there.

So I have a part that's going to get obsolete it, so this was the original a revision of a parts.

So I could see that information, I can take a look at the physical part.

If I go down to, or reference data.

If you remember this all started from, a napkin basically scanned into the system.

I'm saying that, hey, there's an issue here, and we need to make a design change to this, to this triple tree here on this motorcycle.

They were our testing of the track and farm if there was a need to make this change for the configuration.

So the engineer went through, pulled up the power, pulled up the assembler big, made a markup.

So this is the review of the markup.

Again, now, I'm in my chapter role.

So I'm just going through invalidating why we made these changes, so that I can go through and actually, I do my analysis and my checking on what was changed.

So we see that there's an image of a mark up here.

Again, that coincides with the field report.

We have a quick image here that they did a markup.

And then I can go and look at the engineers, the reports, to see what notes he put in here for, for information.

Because this is part of our process, This has to be done in the engineering group. They have to do a write up, justify the change.

While we bring this up, this, if you remember in the series this was demonstrated in Microsoft office products.

This was done inward and then once we bring it into, team center, were also able to do, at its word, at its right, inside a team center as well, because we're embedded here.

So again, just reviewing what his findings were, what actions needed to be, B John here, and, you know, the graphic of the part.

So now I see that we have the field report.

You came out from the field on a napkin.

We have a markup, we have the engineers' investigation report into this change.

So now we can go and look at the other documentation that we have.

So first thing I want to do is since we're focusing on this part, it is let us go ahead and take a look at the physical part.

So you see we have an a revision that's released.

The 60 status is where at least.

And then we have a B, B revision. So let's go ahead and look at these.

And what I'm going to focus on here is I'm going to take a look at these dry ash because I want to do a compare between these two.

Now I can sit here and switch back and forth, say, OK, maybe I've focused on a dimension.

Then I come over here and try to focus on dimension and see what's changed.

But I want to see if there's anything else that was maybe missed during the update.

Maybe they forgot to add a dimension, or maybe they added an additional dimension, I just wanna make sure.

So, what I'm going to do, is I'm gonna select these two documents and I'm going to bring that over into my life cycle viewer.

So, I want to assert these both into an active window.

So, again, I can jump between the two snapshots here of my, my drawings, but I want to do a compare, so I want to overlay these on top of each other.

It will know more window space here, so, here on my toolbar, I have this Compare options, Compare Layers.

I want to take these two documents.

Now, you see here, I can, I can overlay and look and see exactly what's changed between my two brands.

So you can see the dimensions, OK? That was, uh.

No change there.

So, I can quickly go in and take a look and validate and make sure that, then my parks update, I can even see here that, uh, the text change down here from one graph to the other.

And that's fine, just want to validate and see the to be changed.

So So that's great. Now I know exactly what's changed. I can verify that the dimensions are there.

They're all correct.

So this is this is good to go.

So I'm going to go back to my work list. So, I've reviewed my prints now.

So, that looks good.

But now I want to make sure that the: the materials got updated properly.

So, what I'm gonna do is I'm gonna look at the assembly because I see that there's an assembly that's attached here.

I can see that there's an A and a B revision to the Assembly's.

So, what I'm going to do is, I'm going to send this over to, um, Structure Manager.

Oh, and.

Once and this level, over to Instruction Manager.

So, there's my revision.

I can see the parts that are in there, I can expand these.

What I want to do is, I want to do a compare, so I want to have an additional one over here as well.

So, I added that extra window, and I'm going to come over here and send this one over to that, that view there.

So, again, I can go through line by line, and take a look at this, but let's utilize the tools that we have inside of Teamcenter two to help us find what changes were made.

So I'm going to go up to Tools. I'm going to go into Compare.

I want to do a single algol multi-level for this one, I'm just going to do a single Hello, but I do want to create a report.

Again, we only have one change in here, so it's going to be pretty simple exercise here.

But, if we had our more complex bill, and we had multiple changes that we're going through, you know, this report would really come in handy as well as the highlighting showing us what the differences are between the two.

So you can see, we have our a revision RB revision, then we have, this component, we have R A and B revisions, and our report is basically showing us that same thing.

So, this part here has changed from revision A, revision B The quantity, then change, if the quantity did change, we would see that over here, So, this is a great tool for analyzing what the changes are to the bill material.

Right, Because we don't only have the part that we have to worry and focus on. 

We also have the building material where these parts go, so, we want to make sure that, that we've hit all those areas and have all that covered.

So, going back over to my work list, I can see, you know, all the changes that have been made.

I go in and see if there was any, or any other references, or anything else in here, so everything looks good.

Um, taking a look at the, ah priority, and this is all customizable to fit your needs, versus just out of the box here for, for this particular activity, some options.

So, taking a look at that, that all looks good.

So I can come back up here and make my decision on this.

Before I do that, I want to show you some other reports that we have have available.

So, if I come up here to my tools, I go down to Reports, I go into Report Builder, I have all these options in here doing audits. So, sign off our workforce sign off report.

So, if I go in and take a look at that, I could specify a specific job or a specific item.

I just want to go ahead and create a generalized report of everything, ah that's pending out there.

So, I can see, you know, other things that may need to be signed off, Ah, So, I see that there's this change here that has as items that need to be signed off oh, another one here for this work sport. So, this is the one armoire town right now.

So, I haven't, I haven't finished the sign off. That's why I wanted to wait until I came in and took the look at the reports.

But I can see that it's been approved by the engineer, so it was originally created by the engineer.

The engineer started the workflow.

He approved his end of the workflow once he put all his, his items in there.

He was requesting to make the change, went to the CAD guy.

He approved it, changed on, so he signed off on it.

And then, once I go and sign off on it, as the chatter, then it'll be completed.

So, we can go through and look and see, you know, all outstanding items where they're at.

Um.

No.

Where they're at in the process.

So, all these still need to be completed.

Maybe some that, some of them are in my organization, maybe not.

But I can get in there and view the report, and take a look at that.

I'm gonna go ahead and close this out.

So, now, I'm ready to go in and finalize and make my change.

So, just like in the past, we come into, to our main view, I'm the checker and I need to make my decision.

So, I'm going to approve this.

Good.

Just add notes, that make sense.

Good.

Make my decision.

Put that out there.

You see that as no longer in my tasks to perform, it's not an tracking because it's actually complete.

So I no longer have any any sign offs that needed to be done.

The item's has gone per the work instruction.

So, items would have moved from a release date to an obsolete state for the specific a revision of the part, and then, the B revision would have been released.

So, now, I am done with my duties as the checker, because that's the only thing that I had on my plate for, for this particular item.

Now, I can go on to the rest of my day and continue work.

Save a few things.

So, in review, you know, we have some powerful comparison tools.

We've gone medically crapshoot traceability, extensive reporting and auditing, so, you know, we're able to go, in, do our compares, do the auditing of those materials, make sure that we have the revisions and the quantities correct.

And then tie that all together in the reporting, to make sure that we have all of our sign offs in place.

See where other items might be in the time-out process.

And you'll be able to process and run that inflammation.

So, what this does is this enforces your company's best practices, because you would, you would set this workflow around your organization and your needs.

Make sure that it gets to the proper people for sign offs and the proper orders.

Again, if you remember, we can go in and set, um, a template of who's going to sign off on these.

But if we have people on vacation or we have other individuals that may need to be part of this particular sign off, we can route those at any point by quickly updating that workflow process.

As we're deploying it, and making sure that we get the proper sign offs, make sure the proper people are in involved, and everybody in organization has access to the data that they need when they need it.

So, again, just tying everything around back into a single source.

one place to go and look for all this information from specks to, to e-mails, to drawings, to the Models, manufacturing, Information, Analysis, Information, having it all in one place that we can access.

So, with that, I hand it back off to Andrea. Awesome. Thank you, Jason. Great job today.

Um, our next upcoming Customer Enablement Session will be on Thursday, June eighth.

At 11 AM Same time same place I will be talking the math and the post-processing toolbox. So please join us for that and our presenter will be ....

If you don't mind, please stick around for just a couple, maybe just one minute after this session closes and fill out a survey for us. We would really appreciate your feedback. Let us know how we did today.

And, of course, like always, we'll be posting the recording for this webcast on our YouTube channel, directly following the webcast. As soon as we close out, we'll be uploading it there.

And please be sure to check us out on all of our social media, as you can see, they're all listed here. And we do post our videos on there. we post blogs, and all kinds of great articles, and all kinds of great engineering news. So please check us out there. And if there's anything else we can do for you, please just reach out.

You can also comment after we close out this session, so thanks again for joining us. Great job today, Jason, and we will see you on June eighth.

For more videos like this, subscribe to our YouTube Channel.

Teamcenter health check