Do I need to know how to program?
No. A test plan is a short text with groups, measuring points and tolerances as they appear in the data sheet. calServer shows you immediately what it turns into as you write. If you prefer working in a table, you can switch at any time.
What happens to our MET/CAL® procedures?
They stay as they are: you keep starting MET/CAL® directly from the calibration in calServer. If you would rather maintain individual procedures as a test plan in calServer, you import them. Whatever cannot be transferred reliably is named in the import report.
Do I need a separate plan for every device?
No. The plan contains no device commands. Which device is at the workstation and how it is read are kept separate. The same plan runs at the automated workstation, with a camera or with manual entry.
A customer wants tighter limits. Do I need a copy of the plan?
No. The limits are stored with the device type, and that is where you create a separate variant for the customer. You select it before calibrating. The certificate states which requirement was used for evaluation.
Can an AI write test plans?
Yes. calScript is short and unambiguous, which makes it ideal for working with AI. Any available AI can be taught it: a compact language description with one example is enough. You can also connect the AI internally, for example as a model on your own server. Then no plan leaves your building. calServer checks every draft, and nothing is saved until you have reviewed it.
What does beta mean?
Test plans with calScript are usable and run on real hardware, but the feature set is still growing. Custom formulas and loops in the plan, for example, are not available yet. For the beta we are looking for labs that test along with us and give feedback. We discuss the terms with each lab.
Is calScript a Fluke product?
No. calScript and the calServer Runner were developed independently. MET/CAL® is a trademark of Fluke Corporation.