Programming Best Known Methods

[[Do...]]

Hi all,

Do you have defined processes/procedures for programming at your respective workplaces? If so, what sort of information is flowed down? If not, what information do you use to inform your decision-making when programming? The Zeiss Cookbook is a great starting place for establishing point densities, scanning speeds, filter/outlier settings, etc. What about the other considerations surrounding metrology? I am looking to create a standard work procedure that covers CMM programming across multiple disciplines including Zeiss, Camio, etc. What sort of information would be useful to include? I have a running list of things so far, including:

Scope

Roles/responsibilities

Environment controls

Machine/probe calibrations

Fixture considerations

Measurement planning/strategy

Feature/characteristic naming conventions

Data filtering/evaluation

Reporting

Change control

 

Feel free to chime in or share your expertise. I look forward to hearing from everyone. Thanks in advance.

-Don

[[Cl...]]

We have a recommended "Best-Practices" procedure that all of "us" programmers are supposed to follow. It details things like sensor calibrations frequencies, stylus / program naming conventions. Grouping features/Characteristics/Constructed features (to keep things neat in appearance). The use of written instruction (including pictures) on how to load the part in the fixture. Applying appropriate cookbook settings. Establishing a start alignment. The use a POKA YOKE fixturing which allows us to Run the program from Base Alignment. Production strictly uses autorun. All program variable data saved to a specific drive/file. All new programs (at a minimum) have to pass a type-1 Gage R&R. The program must pass a verification procedure (Measuring the part on a different piece of equipment) who's results must fall within 10% of the CMM program results.