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

S

sreekiran14

Involved In Discussions
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
 
Y

yodon

Leader
Super Moderator
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.
 
S

sreekiran14

Involved In Discussions
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



yodon said:
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.
Click to expand...
 
Y

yodon

Leader
Super Moderator
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.
 
J

Jackwilders

Registered
Some popular web development companies include Wix, Squarespace, Weebly, Shopify, Webflow, WordPress, Drupal, Magento, BigCommerce, and mlsdev.com
 
You must log in or register to reply here.
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
adztesla Sterile packaging validation for medical device - ASTMD4332 and ISTA2A ISO 13485:2016 - Medical Device Quality Management Systems 2
K Validation of cleaning, disinfection and sterilization method EU Medical Device Regulations 3
P Process Validation - OQ & PQ Other Medical Device and Orthopedic Related Topics 2
P Validation for blown film extrusion ISO 13485:2016 - Medical Device Quality Management Systems 0
V PQ parameters for computer system validation of configurable software of laboratory equipment Qualification and Validation (including 21 CFR Part 11) 0
M Number of samples for MDSW validation EU Medical Device Regulations 3
C Computerized System Validation in ISO 9001:2015 ISO 9000, ISO 9001, and ISO 9004 Quality Management Systems Standards 9
S Testing & Validation Phase Design and Development of Products and Processes 1
M Thread plug gauge validation/certification ASME vs Asian JJF standard Manufacturing and Related Processes 0
G PEMS Validation Plan IEC 62304 - Medical Device Software Life Cycle Processes 4
T What does "fully verify" mean exactly in process validation? 21 CFR Part 820 - US FDA Quality System Regulations (QSR) 5
P Do Barcode scanners need validation in Medical device manufacturing? Manufacturing and Related Processes 6
Mustapha FAI Template Validation ISO 13485:2016 - Medical Device Quality Management Systems 3
A Sample size selection for process validation - continuous data Reliability Analysis - Predictions, Testing and Standards 9
S Need guidance for Software validation Qualification and Validation (including 21 CFR Part 11) 5
M Sterilization Validation - Carryover Medical Device and FDA Regulations and Standards News 3
S Cleaning validation of single-use tips providing treatment of women’s intimate areas Manufacturing and Related Processes 3
T Verification vs. Validation AS9100, IAQG, NADCAP and Aerospace related Standards and Requirements 4
S Confection validation on different batch sizes Qualification and Validation (including 21 CFR Part 11) 0
E Sealing Validation for Medical devices Qualification and Validation (including 21 CFR Part 11) 5
R CNC process validation Manufacturing and Related Processes 1
A Has anyone implemented the Adobe Acrobat Sign Validation Pack to be 21 CFR Part 11 Compliant? ISO 13485:2016 - Medical Device Quality Management Systems 9
C Test Method Validation - ISO Standards Qualification and Validation (including 21 CFR Part 11) 1
J API Q1 - 5.7.1.5 - Validation of Processes for Production and Servicing Oil and Gas Industry Standards and Regulations 4
A Validation Plastic Injection Molding Process protocol ISO 13485:2016 - Medical Device Quality Management Systems 5
M Use of statistical techniques for Process Validation ISO 13485:2016 - Medical Device Quality Management Systems 9
M Risk-based approach to Test Method Validation for Design Verification? US Medical Device Regulations 5
K Design: Verification Vs Validation And Validation Vs Transfer ISO 13485:2016 - Medical Device Quality Management Systems 19
C Medical Device Gamma Irradiation Validation per VDmax25 (ISO 11137) Qualification and Validation (including 21 CFR Part 11) 1
A Human Factor Validation Human Factors and Ergonomics in Engineering 4
B Verification and Validation of calculations (FEA) in OCTG components. Oil and Gas Industry Standards and Regulations 9
B Validation of FEA Analyses in Oil&Gas Industries. There are a lot of guidelines for other activities. There is a similar proposal for O&G? Design and Development of Products and Processes 0
K Analytical Method Qualification Vs Validation expectations ISO 13485:2016 - Medical Device Quality Management Systems 1
C. Tejeda Process validation of rework assembly methods (medical devices) Medical Device and FDA Regulations and Standards News 3
B Validation of design for valve api 6d 25 edition ISO 9000, ISO 9001, and ISO 9004 Quality Management Systems Standards 0
P Validation for RUO (Research Use Only) ISO 9000, ISO 9001, and ISO 9004 Quality Management Systems Standards 2
B Hi , everyone i need a procedure for validation of design prototype api 6d (valve manufacturing) Oil and Gas Industry Standards and Regulations 1
Ed Panek Validation of Signature Software (Off the shelf) US Medical Device Regulations 6
Q Combining Validation Protocol & Report into 1 template Document Control Systems, Procedures, Forms and Templates 4
K ISO 17025 Method Validation and Verification for Test Lab ISO 17025 related Discussions 5
S Environment Monitoring System Validation ISO 14001:2015 Specific Discussions 1
B Supplier Evaluation report - Validation required or not ISO 13485:2016 - Medical Device Quality Management Systems 3
M Cleaning Validation of components Manufacturing and Related Processes 2

Similar threads

Top Bottom