At Minitab, we conduct extensive internal testing to maintain the highest quality of our software products. We employ rigorous testing methods such as automated regression tests, manual calculations, and comparison with other notable benchmarks to validate proper functionality of the software and numerical accuracy of results. Our number one quality objective is to provide results you can trust.
Recognizing that many businesses must meet FDA and other regulatory agency requirements by validating software according to their intended use, we provide a Minitab 18 Software Validation Kit to facilitate our customers’ validation efforts. The kit includes information about our software testing procedures and an automated script of representative analyses with instructions for use. The output you generate from the script can be compared to an output file we have validated internally. If the script does not cover all the tools you use, it can be used as a template for your validation efforts or you can
contact our consultants for assistance.
For clarifying examples regarding software validation, visit the
If your software validation process requires adherence to FDA regulation CFR Title 21 - Part 11, you can find more information about this regulation and Minitab Statistical Software below:
Minitab customers from industries regulated by the Food and Drug Administration (FDA) have asked about the compliance of Minitab software products with the FDA regulation on electronic records and electronic signatures (21 CFR Part 11). We want to help our customers use our products in accordance with the guidelines of all regulatory agencies, including the FDA.
Minitab Statistical Software provides password protection for opening, saving, and modifying project files. This protection serves as an electronic signature for validating the ongoing use and storage of Minitab project files. For complete control, password protection should be combined with a file or source control system to verify dates, times, and approved access. Minitab Statistical Software also provides a scripting language that can be archived along with validated output. The script and the output can be stored as part of a password-protected project file.
The extent to which a regulated company satisfies the FDA requirements does not depend exclusively on whether the Minitab software is compliant, but on how the regulated company uses Minitab as a tool in their research and their data analyses. Just as our customers are responsible for validating their processes and systems that use Minitab, they are also ultimately responsible for adhering to the guidelines for electronic record keeping and electronic signatures. In other words, the use of Minitab by itself does not make users compliant with this regulation. Providing audit trails and secure record keeping requires a system that satisfies all the components described by the Title 21 regulations, and specifically the Part 11 guideline.
Minitab recommends that our customers contact the FDA for the most up-to-date information on the Part 11 regulations. Both the current 21 CFR Part 11 document (the complete Code of Federal Regulations is revised annually) and the Guidance for Industry Part 11 document are available on the www.fda.gov website. Minitab also welcomes feedback from customers that may help to direct future software development of our products.
Note: Software validation may also be of interest to users in regulated industries. To learn more about the Minitab software validation process, software development life cycle, and other relevant information, click the link, Minitab Software Validation Kit, below.
We recognize the importance of software that is accessible to all customers, including those with a disability. We have documented the limitations our software may have when interacting with accessibility tools.
If you are looking for accessibility information specific to Section 508 of the Rehabilitation Act, we also have the Voluntary Product Accessibility Template (VPAT) available.
contact Minitab Technical Support for either of these documents.
For additional questions about our internal software validation process, please