Frequently Asked Questions (FAQ)
Calibration Control Questions
We created the Calibration Control help topics to be useful for existing as well as prospective users. Within these topics you'll find lots of screen shots, videos, and animated GIFs that answer questions and give you a good feel for the product.
Don't forget that one of the best ways to learn about Calibration Control is to Download and use it for free.
There are several ways Calibration Control lets you know when Equipment needs to be calibrated.
- Grid Shading: When equipment is past due, it has a pink background in the Equipment Grid. When it's soon due, the background is yellow. Check out the Highlight Colors help topic.
- Browse Due Cal: Click on the [Browse Due Cal] menu item and you'll see a grid of nothing but the Past Due and Soon Due Equipment.
- Calibration Due Report: Print a formal report of all the Equipment Due for Calibration by clicking on the [Due Cal Report] button in the ribbon menu. This report is completely editable. Check out the Calibration Due Report help topic for more information.
- Calendar: Use the Calendar feature see how many equipment are due for calibration on any given day of the calendar. Refer to the Due Cal Calendars help topic to learn more.
- Auto Emails: Calibration Control can also automatically send reminder emails with list of equipment to Custodians, Technicians, Owners, Department Managers, etc. letting them know that their equipment is due for Calibration. Refer to the Auto Notify Utility help topic for instruction on how to set this feature up.
We can import your data for you! We don't have a single automated method to import your data because everyone's data is different so importing is a manual process.
Check out the article on importing data for much more information on the subject.
Yes, but perspective really makes a difference. If your external auditor is asking for validation, she's usually referring to a standard that talks about software you design in-house that is used inside products that you produce and sell. In this scenario, you define the requirements of the software before creating it, create the software, and then validate that the software met your initial design requirements.
With off-the-shelf software like ours, we didn't design it specifically for one scenario in one organization. Therefore, we won't have the same list of initial requirements to validate against as you might. Since our software is continually improved with new features and bug fixes, the validation reports we create address these specific product advancement goals. In other words, our validation reports are created from a different perspective than an end user organization.
If you would like a copy of the most recent validation report, just ask us. If you need us to generate a new report for the current version, we charge for that service.