Lasers, Optics & Photonics Manufacturing worked example
Optics Polishing Time at 23% setup and inspection allowance: a worked example
This scenario runs the optics polishing time calculation on the strong side: 23% setup and inspection allowance, with every other input held at its documented default. Use this when scheduling polishing work for a production lot of lenses or flats, quoting delivery time to a customer, or deciding whether to add a second polishing spindle to meet demand.
The inputs for this scenario
- Number of optical surfaces to polish: 100 surfaces (unchanged)
- Polishing rate: 5 surfaces / hr (unchanged)
- Setup and inspection allowance: 23 % (raised for this scenario; the documented default is 20)
Working through the calculation
- Applying the documented formula (Base polishing time = number of optical surfaces / polishing rate) to the inputs above produces each figure below.
- At this operating point the engine returns 24.6 hr for total polishing time (with setup), the number this scenario is built around.
- At this operating point the engine returns 20 hr for base polishing time.
- At this operating point the engine returns 23 % for setup and inspection time added.
- At this operating point the engine returns 5 pieces / min for polishing rate.
How this compares with the baseline
- Against the tool's baseline example, where setup and inspection allowance sits at 20% and the headline result is 24 hr, this scenario comes in 2.5% above the baseline at 24.6 hr.
- Use it when scheduling polishing capacity or quoting delivery for a batch of optical components. Treat this as a target state: the delta against the baseline quantifies what the improvement is worth before you commit to chasing it.
Results at a glance
- Total polishing time (with setup): 24.6 hr (headline result)
- Base polishing time: 20 hr
- Setup and inspection time added: 23 %
- Polishing rate: 5 pieces / min
Run it with your numbers
- Every input above is editable in the live Optics Polishing Time calculator, which recalculates instantly and can be shared with the inputs intact.
Last reviewed 2026-05-12.