How we manage change on Unifize

So oftentimes, you know, I'll be using SolidWorks to do our computer modeling. I'll use Apache subversion to handle our version control. Outside of that, we're not really software heavy here. Most of what we do is I mean, we have product in back, maybe debugging robots, working hands on with stuff, doing repairs, prototypes, that sort of thing.

So, you know, as a mechanical engineer here, primarily it's going to be SolidWorks and our chosen version control system.

So at Harmonic Bionics, we follow a system where we document our design outputs. So the file that we would send to our vendors is a step file or a PDF or some immutable document that captures a snapshot and the design of the robot that is reviewed and released and entered into Unifize my day to day workflow will usually start with me.

You know, maybe looking at a quality notification on Unifize saying that, hey, we should update maybe our cosmetic finishes standard and maybe I sit down, discuss the vendors over the phone, come to an agreement and update a print in SolidWorks that calls out a new specification. I'll make a commit to our version control software, get my commit number, and I will create my export files, my step in my PDF and those together we'll go on to a change order that I've created on Unifize.

That change order will get released and those parts will be live in our system. Our purchaser can go in, download those parts from Unifize. He knows that it's the same file that I was working on earlier that day and he knows that if he sends it to that vendor, that that's the print. The changes that we talked about that day are going to be on there.

So it's very versatile. You know, everybody has access to the data. There's no, you know, gates or, you know, blocks that could prevent somebody from getting to the information that they need. And it's easy to use.