Your Products have been synced, click here to refresh
Programming efforts need to be relative to what the routine's intended purpose is. Some of this is static for an organization, but can definitely vary by company or industry.
Some things to consider before even pressing a single keystroke:
-Is it for a one-off part or short production run?
-Is it going to require MSA and/or validation?
-Is it for high production/reliability?
-Is there a way to consolidate or parametrically adapt method of measure for multiple parts or phases of the parts?
-What are the common defects or failure modes of the part?
-Who/what skillset is going to be physically executing the routine?
-How does data need to be documented, controlled or exhibited?
Programming efforts need to be relative to what the routine's intended purpose is. Some of this is static for an organization, but can definitely vary by company or industry.
Some things to consider before even pressing a single keystroke:
-Is it for a one-off part or short production run?
-Is it going to require MSA and/or validation?
-Is it for high production/reliability?
-Is there a way to consolidate or parametrically adapt method of measure for multiple parts or phases of the parts?
-What are the common defects or failure modes of the part?
-Who/what skillset is going to be physically executing the routine?
-How does data need to be documented, controlled or exhibited?
© 2024 Hexagon AB and/or its subsidiaries. | Privacy Policy | Cloud Services Agreement |