Forced ServiceNow validation - No change in our current user and functional requirements

sreekiran14

Starting to get Involved
#1
Hi, our Organization is going through the forced ServiceNow upgrade as the vendor will not support our current validated version.
I am looking for input on "to what extent the validation need be updated" as there is no change in out current user and functional requirements.

This is a cloud based system, appreciate your input.

Thank you
 
Elsmar Forum Sponsor

yodon

Staff member
Super Moderator
#2
Validation is never intended to be a one-time event. This is but one of the circumstances that could take you out of the validated state.

But to answer your question, the vendor should be able to provide the list of changes and bugs fixed. You should look at the changes and consider if they touch any of the areas for which you previously validated. Look at the problems fixed to determine if your previously-validated version may have been allowing errors to slip through. If you did something along the lines of an installation qualification, ensure all that's still valid (they may require, for example, updated versions of infrastructure software or may no longer support certain browsers / versions). Take a structured approach to all this and document the results.

It's also a good time to review your intended use. Have any of your use cases changed (are you using the software differently than originally intended, are there substantially more users now than previously expected, have you started using new features than originally planned, etc.)?

You may be able to justify a reduced-scope re-validation. In keeping with the risk-based philosophy, identify the higher-risk functions are and probably at least re-validate those areas, regardless.

Last "soap box" statement: you *should* have a master validation plan that helps you in these decisions! If not a master plan, you should have a specific validation plan for this software that drives the efforts.
 

sreekiran14

Starting to get Involved
#3
Thank you so much for the detailed input Yodon!
We have more users than previously. Wondering what kind of testing to perform to address that.

really appreciate your help.

thanks



Validation is never intended to be a one-time event. This is but one of the circumstances that could take you out of the validated state.

But to answer your question, the vendor should be able to provide the list of changes and bugs fixed. You should look at the changes and consider if they touch any of the areas for which you previously validated. Look at the problems fixed to determine if your previously-validated version may have been allowing errors to slip through. If you did something along the lines of an installation qualification, ensure all that's still valid (they may require, for example, updated versions of infrastructure software or may no longer support certain browsers / versions). Take a structured approach to all this and document the results.

It's also a good time to review your intended use. Have any of your use cases changed (are you using the software differently than originally intended, are there substantially more users now than previously expected, have you started using new features than originally planned, etc.)?

You may be able to justify a reduced-scope re-validation. In keeping with the risk-based philosophy, identify the higher-risk functions are and probably at least re-validate those areas, regardless.

Last "soap box" statement: you *should* have a master validation plan that helps you in these decisions! If not a master plan, you should have a specific validation plan for this software that drives the efforts.
 

yodon

Staff member
Super Moderator
#4
Are you seeing any errors, delays, or crashes due to the increased number of users? If not, maybe just acknowledge the fact and note that since operations are not impacted, no additional testing is required. Given it's a cloud app, I'm guessing it's suitably robust.
 
Thread starter Similar threads Forum Replies Date
A Validation of Forced Aeration Process ISO 13485:2016 - Medical Device Quality Management Systems 3
M Brazil forced degradation study requirements Reliability Analysis - Predictions, Testing and Standards 0
supadrai Forced into Regulatory Affairs Role - Where do I begin? Career and Occupation Discussions 4
M Forced NOT to meet End Customer Expectations - Corrupt Third World Country ISO 9000, ISO 9001, and ISO 9004 Quality Management Systems Standards 4
Marc UK Executive Forced Out of Job For Posting Resume On LinkedIn Career and Occupation Discussions 2
C Keeping ISO TS 16949 Certification During Forced Production Interruption IATF 16949 - Automotive Quality Systems Standard 2
Marc Will the weather service be forced to stop giving weather information for free? World News 4
R SAP B1 Computer System Validation Qualification and Validation (including 21 CFR Part 11) 0
A GAGE R&R Binomial with master list (for method validation) Gage R&R (GR&R) and MSA (Measurement Systems Analysis) 0
Y ISO 13485:2015 Software Validation IQ/OQ/PQ ISO 13485:2016 - Medical Device Quality Management Systems 12
N Validation of special processes - thread closed Oil and Gas Industry Standards and Regulations 3
L Validation without Tolerance Qualification and Validation (including 21 CFR Part 11) 0
shimonv Test Method Validation ISO 13485:2016 - Medical Device Quality Management Systems 10
R Debug mode in software/device validation IEC 62304 - Medical Device Software Life Cycle Processes 2
M Software verification and validation AS9100 AS9100, IAQG, NADCAP and Aerospace related Standards and Requirements 4
Melissa Process Validation of Rotary Heat Sealer Speeds Design and Development of Products and Processes 4
C Validation of process for releasing the UDI EU Medical Device Regulations 4
C Validation of process for production and servicing 5.7.1.5 API Spec Q1, 9th Edition Oil and Gas Industry Standards and Regulations 9
W Transport validation Qualification and Validation (including 21 CFR Part 11) 4
M Is validation required when consumables are changed Qualification and Validation (including 21 CFR Part 11) 7
C 8.3.4 Verification and Validation ISO 9000, ISO 9001, and ISO 9004 Quality Management Systems Standards 4
W Transport validation Qualification and Validation (including 21 CFR Part 11) 12
mustomutlu Process Validation Final Report Other Medical Device and Orthopedic Related Topics 2
P Software verification and validation procedure IEC 62304 - Medical Device Software Life Cycle Processes 6
Y SaMD Verification and Validation SOP and Plan IEC 62304 - Medical Device Software Life Cycle Processes 8
C Spreadsheet Validation and Release Qualification and Validation (including 21 CFR Part 11) 2
M Packing Validation & Accelerated Aging Test ISO 13485:2016 - Medical Device Quality Management Systems 2
M Sterile packing validation tests to be performed and protocol Other Medical Device and Orthopedic Related Topics 1
S OEM full range calibrations vs Validation special test points Medical Device and FDA Regulations and Standards News 1
H Software Validation for FFS Packaging Machine Qualification and Validation (including 21 CFR Part 11) 1
Q ISO 13485 7.5.6 Validation - Off the shelf Software ISO 13485:2016 - Medical Device Quality Management Systems 3
M ERP / QMS related software standards for Validation IEC 62304 - Medical Device Software Life Cycle Processes 6
C ISO 19227 Validation Cost Other Medical Device Related Standards 2
A CNC Mill and Lathe - Validation Manufacturing and Related Processes 2
N Example for design and development planning,input,output,review,verification,validation and transfer Misc. Quality Assurance and Business Systems Related Topics 4
N Sterilization Protocol Change in Validation Process and further impacts ISO 13485:2016 - Medical Device Quality Management Systems 1
B Oracle Cloud ERP Validation during Quarterly Patch ISO 13485:2016 - Medical Device Quality Management Systems 1
D Software validation team Misc. Quality Assurance and Business Systems Related Topics 3
W LTPD, AQL, Ppk and Cpk validation sampling plan table Inspection, Prints (Drawings), Testing, Sampling and Related Topics 0
J Validation Sample Size for Tray Seal Qualification and Validation (including 21 CFR Part 11) 4
F AS9100 - Validation, FAIR's, ITAR and Sub-Contracting AS9100, IAQG, NADCAP and Aerospace related Standards and Requirements 3
R PCBA process validation Qualification and Validation (including 21 CFR Part 11) 2
A ISO 17025 - Methods validation and clients ISO 17025 related Discussions 3
S Sterilization validation after changing sterilization process provider Qualification and Validation (including 21 CFR Part 11) 3
B Sterilization Validation Plan Other Medical Device Related Standards 3
D Difference between Test Method Validation and Gage R&R Qualification and Validation (including 21 CFR Part 11) 18
T Laboratory Verification after validation ISO 17025 related Discussions 3
silentmonkey Rationalising the level of effort and depth of software validation based on risk ISO 13485:2016 - Medical Device Quality Management Systems 10
D Questions regarding process validation ISO 13485:2016 - Medical Device Quality Management Systems 15
Y We found out we have been using a equipment without validation for past 4 years Quality Manager and Management Related Issues 6

Similar threads

Top Bottom