Knowledge-Enabled Variable Interpretation Network

KEVIN SUPPORT

Use KEVIN with confidence from setup through final results.

Find the recommended workflow, field-by-field guidance, screen tours, recommendation review help, and troubleshooting answers in one place.

Recommended workflow

A KEVIN run works best as a complete measurement and feedback loop.

The recommendation depends on the quality of the part information, measurements, and process settings entered before the run. The value increases when the actual result is recorded afterward.

01

Enter the part

Enter part, geometry, pad, slurry, and machine setup information.

02

Enter measurements

Enter the current and target measurement values for the optic.

03

Select the pattern

Choose the surface error pattern that best matches the interferometer result.

04

Run KEVIN

Review the entries, then start the recommendation engine.

05

Review the advice

Review the recommendation, math, historical evidence, confidence, and risk warnings.

06

Close the loop

Perform the polishing run, measure again, and record the actual results.

Enter the run correctly

Give KEVIN the part, process, and measurement context it needs.

The recommendation is only as good as the information entered. Review required fields, units, and the selected surface pattern before running the analysis.

Part model

Job + Geometry

What KEVIN is doingKEVIN builds the starting model for the optic from the material, surface shape, aperture, thickness, and radius of curvature.

Why it mattersGeometry affects flex risk, pressure sensitivity, recommended tool size, and how aggressive a correction can safely be.

View all Job + Geometry fields
  1. Run ID: unique name for this polishing run.
  2. Technician: operator completing the run.
  3. Material: optic material; KEVIN uses this to adjust expected polishing response.
  4. Surface Shape: convex, concave, or plano surface being corrected.
  5. Back Surface Geometry: geometry on the opposite side of the optic.
  6. Aperture Diameter: clear aperture or working diameter.
  7. Center Thickness: thickness through the center of the optic.
  8. Edge Thickness: thickness at the optic edge.
  9. Lens ROC: current or nominal radius of curvature.
  10. Recommended Polisher: KEVIN’s calculated tool-size guidance.
  11. Aspect Ratio: diameter-to-thickness indicator used for flex risk.
  12. Target Ratio: normal setup ratio KEVIN compares against.
  13. Flex Risk: pressure guardrail based on geometry.
  14. Geometry Risk: overall geometry warning status.
Process setup

Pad, Slurry + Machine

What KEVIN is doingKEVIN reads the current consumables and machine settings so its next move fits the actual polishing setup.

Why it mattersPad type, hardness, slurry chemistry, stroke, pressure, speed, and cycle time all affect removal behavior.

View all setup fields
  1. Pad Type: polishing pad currently on the machine.
  2. Pad Durometer: pad hardness.
  3. Slurry Baume: slurry concentration.
  4. Slurry pH: slurry chemistry condition.
  5. Stroke Distance: current stroke setting.
  6. Bladder Pressure: current pressure setting.
  7. Speed Factor: automatically calculated speed relationship.
  8. Cycle Time: current run time.
  9. Tool Speed: polisher/tool RPM.
  10. Part Speed: optic/carrier RPM.
Optical condition

Measurement Entry

What KEVIN is doingKEVIN compares the current optical condition with the target. The size and direction of those gaps drive the recommendation.

Why it mattersPower and ROC values drive radius correction, while irregularity and pattern selection describe the form error.

View all measurement fields
  1. Power Error Now: current measured power error.
  2. Target Power Error: desired power value.
  3. ROC Now: current radius measurement.
  4. Target ROC: required radius.
  5. Irregularity Now: current form error.
  6. Target Irregularity: required form tolerance.
  7. Units: measurement units used for irregularity.
  8. Priority: whether KEVIN should balance correction or favor power/ROC or irregularity.
  9. Pattern Selection: select the pattern that best matches the interferometer result.
Close the feedback loop

Final results make the run useful later.

Future recommendations improve when technicians record the actual changes, final optical measurements, and observations from the completed polishing run.

After polishing

Record what actually happened.

KEVIN captures the actual settings and final measurements after polishing. That closes the loop between recommendation and outcome and turns a completed run into useful historical evidence.

Actual strokeActual pressureActual speedActual time
Polisher usedPower afterROC afterIrregularity after
UsefulnessRecommendation followed?Effectiveness scoreTechnician notes
Final-results field guide
  1. Actual Stroke Change: stroke adjustment used.
  2. Actual Pressure Change: pressure adjustment used.
  3. Actual Speed Change: speed adjustment used.
  4. Actual Time: actual cycle time.
  5. Actual Polisher Used: tool diameter used.
  6. Power Error After: final power result.
  7. ROC After: final radius result.
  8. Irregularity After: final form result.
  9. KEVIN Useful?: technician judgment of usefulness.
  10. Recommendation Followed?: whether the recommendation was followed.
  11. Effectiveness Score: 1-5 rating.
  12. Technician Notes: observations, lessons learned, or concerns.
  13. Calculate Result: generates the outcome summary.
FAQ + troubleshooting

Start with the inputs, units, pattern selection, and final-result requirements.

These are the common questions and troubleshooting checks included in the KEVIN Operator Training Manual.

Does KEVIN replace technician judgment?

No. KEVIN is a decision-support tool. Technicians should review the recommendation, math, historical evidence, and risk warnings before making changes.

Why does KEVIN need geometry information?

Geometry affects flex risk, pressure sensitivity, recommended tool size, and how aggressive the next move should be.

What if my interferogram does not exactly match one pattern?

Choose the closest pattern and explain any uncertainty in Technician Notes.

Why should every run be logged?

Logged runs create the historical evidence KEVIN uses to compare future jobs and improve recommendations.

Can I edit a run after saving it?

Yes. Open My KEVIN Runs, select the saved or incomplete run, make the correction, and save the updated record.

Run KEVIN button does not produce a recommendation.

Check that all required measurement fields are completed and that a pattern is selected.

Recommendation seems too aggressive.

Check geometry, thickness, units, pressure, and cycle time. Review the risk warnings before making the change.

My KEVIN Runs does not load.

Refresh the page and verify that the page finished loading normally. If the issue continues, sign out and back in, then reopen My KEVIN Runs.

The wrong units were entered.

Correct the measurement fields before logging the run. If the run was already saved, reopen it from My KEVIN Runs and update the record there.

Run result will not save.

Complete all required final-result fields and add notes if the outcome is unusual.

Need the full field-by-field reference?

The Operator Training Manual includes annotated KEVIN screens and numbered callouts for the run setup, measurements, recommendation review, final results, and saved runs.