GlossaryKind of term: Manufacturing termProgramming time
What is programming time?
Programming time is the time to create the NC program for a part, in CAM or at the control; in principle it falls once per part and revision.
The inputs are model, drawing and route; the work consists of choosing a strategy per feature, setting tools and cutting data, simulating the toolpaths and post-processing for the control. Programming at the control itself is mainly a matter of simple work. Proving out the program on the machine counts as programming in some shops and as setup in others.
What does programming time depend on?
Programming time depends on the number and kind of features, free-form surfaces, the number of setups and axes, the tolerances, the material and whether templates, tool libraries and proven strategies already exist. A housing with pockets, dozens of holes and threads takes more time than a flat plate with four holes, for example. A program belongs to a part, a revision and a machine or control: moving to another machine needs at least a new post-process and a check.
How does programming time work in practice?
Programming falls, in principle, once per part and revision. You can recover it in the first batch, as a separate one-off item, or spread over expected repeat orders. On a new free-form one-off, programming time can exceed machining time. On an unchanged repeat order it usually drops out; a drawing change can bring part of it back, depending on which features change.
What is programming time often confused with?
Programming time is not setup time: programming usually happens at a workstation, once per part, setup at the machine for every batch and setup. Nor is it cycle time: writing the program is not running it.
How do you see programming time in Blake?
In Blake programming has a line of its own, apart from setup and machining. For a repeat part the estimate sits beside the last priced one, so you see whether the programming line still belongs. More on estimating.
Frequently asked questions
Do you charge programming time again on a repeat order?
Usually not if revision, route and machine are unchanged: the program exists. If the drawing changes or the work moves to another machine, part of the programming work can come back.
What counts as programming time?
Choosing strategies and tools, setting cutting data, simulating toolpaths and post-processing. Whether prove-out on the machine belongs here or under setup is a convention; fix it so your estimate and time booking count the same thing.