Can I lock programs?

[[Da...]]

I would like to know if there is a way to lock a program to avoid someone changing things in the program? We have 3-4 operators and we switch back and forth all day long.

[[Ch...]]

Users.

we have one master user that can control everything. Then operator users that have most stuff restricted.

[[Lo...]]

I've made them read only and had the operators close the program after each run. This keeps the original "safe" and will force the "save as" prompt to happen.

[[Ma...]]

Utilizing Autorun might help as well.

[[Mi...]]

AutoRun + Users with different permissions. One of them is preventing them from saving or even executing programs from other users.

Meaning, you program in Master, save it, they run in User, they can't edit or change anything. Just don't give up the Master password

With Autorun you can make it so they can't even close the AutoRun window without a password.

[[Da...]]

I want to lock a program, not a person. Certain programs are completely tested and vetted. All my guys can change things on most programs if they need to, but certain programs are to be left alone.

[[Th...]]

It's possible that using digital signatures will do what you need, but I've never worked with that function.

[[Ch...]]

Please sign in to view this quote.

In that case, just make the inspection file for that specific program read only.

[[Ro...]]

You can lock programs by turning your measurement plan into a Macro. If you try to open a feature or characteristic, it'll say "Unable to Open" and you can only run the measurement plan. It's pretty simple and straight forward. Send me a PM and ill send you a Step-By-Step PDF on how to do it.

Macro-1.jpgMacro-2.jpg

[[Er...]]

Lots of creative suggestions.

Place a file called afpbsi inside your measurement plan folder, and it will be "locked". Altough, it's not bulletproof in any way.

[[Cl...]]

I tried your suggestion Eric and I like it, but how do you create the password?

[[Gu...]]

Please sign in to view this quote.

Excellent, it works for me. I'm curious how to set the password ?


Thanks

Guillaume

[[Je...]]

Measurement plan versioning
CALYPSO supports measurement plan versioning. This function allows
you to "freeze" versions or variants of a measurement plan and save
them as fixed, unchangeable revisions. A revision can be opened at any
time and executed. After having edited a revision further, you can save it
as a further revision or simply as a measurement plan or discard it.
If you want to work with versions and revisions, you must choose one of
three options:
– Local versioning in CALYPSO
With local versioning, CALYPSO saves the revisions and working
copies locally in directories on your system.
– Versioning with Connected Quality
If you have the corresponding access, you also can use Connected
Quality as an alternative method of versioning measurement plans.
In this case, the measurement plans and versions are not saved locally. You must be connected to Connected Quality in order to
download and upload versions.
– Versioning with Teamcenter
If you have Option 28 CALYPSO teamcenter in/out and the corresponding programs, you can save revisions of measurement plans to
Teamcenter. In this case, the measurement plans and versions are
not saved locally. You must be connected to Teamcenter in order to
download and upload versions. Information on versioning in Teamcenter can be found under Using CAD models and measurement
plans in Teamcenter

Teamcenter_In_Out module manual attached (also in your manuals directory on all PCs with CALYPSO installed)

Calypso_28_teamcenter_in_out.pdf

[[Ri...]]

I shall pay my respects to MCC.

[[Je...]]

I'd like to offer another perspective on this topic, one that I advocate for both locally and within the metrology community as a whole.

While versioning and information management is vital in manufacturing, I believe that we should facilitate an environment that encourages skill development. I want our operators and those with less metrology experience to be empowered. I want them to have access to Calypso not simply for offline planning but at the machine.

Perhaps unsolicited program changes are more of a symptom than the root issue. Perhaps it is an indication that communication, team culture, and trust has room for growth. I love it when companies can showcase collaboration and mutual knowledge sharing.

When my ear is open to others, including those with lesser experience, I find that I learn and improve. When I make myself available to train others and field questions, I find that trust and collaboration thrive.

This doesn't make user accounts and rights management obsolete, but it probably makes them less necessary.

[[Ri...]]

Jeff,

I agree 100% on empowering your operators. I'm not a fan of glorified button pushers as even the operators having a fundamental understanding on how the part is manufactured and measured will help ensure that the results that are supplied to the machinists are believed to be as accurate as possible.

For the user rights/versioning controls, it will just completely depend on the industry you work in and the requirements per whatever quality standard/policy you have set in place.

[[Da...]]

Please sign in to view this quote.

Jeff, I agree completely! I strive to bring my guys up as far as I can. I explain and share any and all knowledge that I can with them.
This is not about protecting our average program from a bit of experimentation. We have quite a few programs that are real ball busters. I spent a lot of time hammering these out. We have programs that check .004 X 90 degree seal areas on a face that varies .005 in location. I don't want anyone changing anything on that program. Some have progressive alignments that run multi operational parts from start to finish. Most are high production parts that need in process inspections and can't wait while we re-program! I need a bit of insurance on these types of projects.

[[Mi...]]

Agreed with all of those points about teaching and trust, but this is where users with different levels of permissions come into play, some sort of changelog would be important too. We have 3 or 4 levels of user depending on which machine and area of the plant.

As skills and trust develop they get the various Technician level passwords, in our facility a very small group of us with offline seats actually have the Master password for programming the production parts, but we can't afford to have somebody making a change to a production program. We REALLY can't afford to have somebody edit one program on one CMM when another CMM may have that same program that doesn't get edited, so now you have 2 versions out there... such a mess.

However our technicians and even some of the QA Inspectors can write programs freely at the QA Lab CMMs so they can verify various gauges and such that we have.

I also have a copy of the full complete layout programs left available to them, saved in User not Master, so it can be used to Save As and make a sort program as needed without passwords, so it can be done at 3am on Saturday. Not that we ever have to CMM sort, because we never make bad parts....

But as Standardization, Databases, and Audit requirements become bigger factors, you just can't afford to have people adjusting programs. Better to control it early, so you're not like us who started with Washing Machine and KitchenAid mixer parts, now graduated to complicated gear carriers and 30+ CMMs and having to do it all after. It's much easier to consider and control early, then learn where to ease up, than it is to add it after the fact.

[[Je...]]

Please sign in to view this quote.

.

Dave,

Thank you for providing context to your situation. It makes sense that you would want to manage risk, especially in regards to the programs you have invested a lot of labor and thought into. We're also stakeholders in mitigating risk for our customers, and safeguarding measurement plans and machines is part of this task.

I agree with you, and thanks again for explaining your situation.