The Cove Business Standards Discussion Forums More Free Files Forum Discussion Thread Post Attachments Listing Cove Discussion Forums Main Page
UL - Underwriters Laboratories - Health Sciences
Go Back   The Elsmar Cove Business Systems and Standards Discussion Forums > Common Quality Assurance Processes and Tools > Software Quality Assurance
Forum Username

Elsmar Cove Forum Visitor Notice(s)

Wooden Line

COTS (commercial off-the-shelf) Validation FDA Requirements


Elsmar XML RSS Feed
Elsmar Cove Forum RSS Feed

Monitor the Elsmar Forum
Sponsor Links




Courtesy Quick Links


Links that Cove visitors will find useful in your quest for knowledge:

International Standards Bodies - World Wide Standards Bodies

ASQ - American Society for Quality

International Standards Organization - ISO Standards and Information

Howard's
International Quality Services


Marcelo Antunes'
SQR Consulting, and
Medical Devices Expert Forum


Bob Doering
Bob Doering's Blogs and,
Correct SPC - Precision Machining


Ajit Basrur
Claritas Consulting, LLC


NIST's Engineering Statistics Handbook

IRCA - International Register of Certified Auditors

SAE - Society of Automotive Engineers

Quality Digest

IEST - Institute of Environmental Sciences and Technology


Some Related Topic Tags (Not all threads are Tagged)
cots (commercial off-the-shelf), fda requirements, software (general topics)
Reply
 
Thread Tools Search this Thread Rate Thread Content Display Modes
  Post Number #1  
Old 29th April 2015, 04:08 PM
Sarath9000

 
 
Total Posts: 2
Please Help! COTS (commercial off-the-shelf) Validation FDA Requirements

Hello All,

This question may have been asked before but I couldn't find appropriate answer.If any Commercial off the shelf application is being used in a FDA regulated industry, can we leverage the testing performed by the vendor? If not why do we need to do additional testing at the site if the vendor has already tested the software functionality?

Sponsored Links
  Post Number #2  
Old 29th April 2015, 04:35 PM
Marcelo Antunes's Avatar
Marcelo Antunes

 
 
Total Posts: 3,030
Re: COTS software validation

Because he has not tested your use of the software. But depending on what he did, you can use any testing as part of your validation testing.
Thanks to Marcelo Antunes for your informative Post and/or Attachment!
Sponsored Links

  Post Number #3  
Old 29th April 2015, 06:32 PM
yodon

 
 
Total Posts: 925
Re: COTS software validation

Marcelo is right, of course, but let me add on a bit.

The software was not tested for your use (as Marcelo points out) NOR was it tested in your environment. I don't know if it's your case, but a lot of software has security features which you have to tailor for your needs, back-end databases which are user-provided, custom forms / routing, etc. These can only be assessed on your installation in your environment.

And one additional point: you should assess the list of known issues to determine if any might impact your operations.

So while you may be able to leverage a lot of the testing the vendor did (presuming you can establish equivalence) you will still probably need to take some efforts to complete validation.
Thanks to yodon for your informative Post and/or Attachment!
  Post Number #4  
Old 13th May 2015, 02:57 PM
Sarath9000

 
 
Total Posts: 2
Re: COTS software validation

Thank you Marcelo and Yodon for your quick responses. I am sorry that I haven't got a chance to reply until today. The COTS application I was asking is image analysis software which is used to measure thickness and porosity of samples. This software also has the capability to be configured by using VB script. But I am not sure at this point if that is the case at my company. So I already checked with the vendor and they told me that they would not be able to provide their validation documentation. Also it isn't that the software used at my company was never validated. In fact it was validated here as part of the process without much focus on the software (which includes microscope calibration along with basic software testing ex: Intended use was tested). We also have a procedure here on how to measure the thickness and porosity. Now I want to make sure that adequate testing was performed in the past validation. I have the following questions:

Would it suffice if we can prove that work flow written in the procedure was tested?

Further, the software may have a lot of functionality and my company may not be using all of it. So I am thinking to gather the list of only areas/functionality (through user manual) used at my company and verify that they were tested in the past validation. Any thoughts?
  Post Number #5  
Old 14th May 2015, 05:10 PM
c.mitch's Avatar
c.mitch

 
 
Total Posts: 175
COTS (commercial off-the-shelf) Validation FDA Requirements

Hi Sara,
The validation of the vendor won't be useful (perhaps food for thought if you had it).
The validation of software is a classical IQ OQ PQ.
IQ is verifying installation and configuration (the VB script may be seen as part if the configuration),
OQ is verifying sw functionalities one by one,
PQ is verifying sw with real use scenarios.
OQ sometimes is done on a testing platform, different from the target platform used for PQ.

Testing the workflow in your procedure sounds more like PQ.

Before PQ you need an OQ. To do so write a Software Requirement Specification document (many templates are on the internet) containing the functions you use of the software and probably the custom features of the VB script. So when you're thinking of gathering only the functions used at your company and test them, you're right.

Btw, don't forget in you SRS to write the functions used by technicians who maintain the software (eg: backup/restore, calibration ...).

In terms of documentation, you'll have at minimum a SRS, IQ/OQ/PQ protocols and IQ/OQ/PQ reports. One very important thing is to record in your reports which version of software you tested (consequence: the VB script should probably be version controlled).

Bye.
Thank You to c.mitch for your informative Post and/or Attachment!
Reply

Lower Navigation Bar
Go Back   The Elsmar Cove Business Systems and Standards Discussion Forums > Common Quality Assurance Processes and Tools > Software Quality Assurance

Bookmarks



Visitors Currently Viewing this Thread: 1 (0 Registered Visitors (Members) and 1 Unregistered Guest Visitors)
 
Thread Tools Search this Thread
Search this Thread:

Advanced Forum Search
Display Modes Rate Thread Content
Rate Thread Content:

Forum Posting Settings
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Emoticons are On
[IMG] code is On
HTML code is Off


Similar Discussion Threads
Discussion Thread Title Thread Starter Forum Replies Last Post or Poll Vote
COTS (Commercial Off-The-Shelf) Parts with AS9102 FAI? lorenambrose AS9100, IAQG 9100, Nadcap and related Aerospace Standards and Requirements 16 9th June 2015 08:13 AM
COTS (commercial off-the-shelf) Computers - Warranty return rate? normzone Benchmarking 3 2nd February 2010 05:05 PM
Packaging Commercial off-the-shelf (COTS) Products as a Single System assyrian47 Design and Development of Products and Processes 2 30th May 2009 10:38 PM
Validation of Commercial off-the-shelf software - Spreadsheets ISO 13485 - Medical ISO 13485:2016 - Medical Device Quality Management Systems 16 2nd May 2008 10:07 PM
Process for receiving functions - COTS (commercial off the shelf) vs Custom parts. al40 Document Control Systems, Procedures, Forms and Templates 6 14th January 2008 08:14 PM



The time now is 03:00 AM. All times are GMT -4.
Your time zone can be changed in your UserCP --> Options.


 
 


NOTE: This forum uses "Cookies"