SBS - The best value in QMS software

Software service provider as critical supplier

#1
Hello everyone.
We have a problem within our team and we want to hear a 3rd opinion. ;)
Our company uses an eQMS solution, we accepted their Terms and conditions. In our system, they are deemed as a critical supplier.
Now, to place the adequate controls, one part of our team wants to send the eQMS provider a typical supplier quality agreement.
Is it really necessary or can we just stick with the accepted Terms and conditions?
Thanks a lot for any input.
 
Elsmar Forum Sponsor

planB

Super Moderator
#2
Bill,

in case _their_ Terms & Conditions adequately cover the supplier control requirements _your_ QMS defines for critical (software) suppliers, you might be fine without a supplier quality agreement issued by you. Otherwise, a dedicated supplier agreement issued by your organisation might be warranted.

Hope this helps,
 

yodon

Staff member
Super Moderator
#3
Why are they deemed a critical supplier? Do you really have any control over them? I would assume this is a commercial supplier. One of the typical things seen in a quality agreement is that they don't change their processes without informing you first. A commercial supplier isn't going to agree to that. You likely don't have any control over what changes they make to the software, when they make them, or when they release updates.

If my assumption about them being a commercial supplier is wrong, then, um, ignore all that. :)
 

William55401

Quite Involved in Discussions
#4
Yodon is spot on. I have been in this space before for a s/w based FAI tool. The org I was supporting had to actively monitor the supplier for updates and determine when re-validation would occur. Through central password / account control we could positively prevent the user community from accessing s/w when re-validation was triggered. HTH
 

Jim Ivey

Grand Avenue Software
#5
Our company uses an eQMS solution, we accepted their Terms and conditions. In our system, they are deemed as a critical supplier. Now, to place the adequate controls, one part of our team wants to send the eQMS provider a typical supplier quality agreement. Is it really necessary or can we just stick with the accepted Terms and conditions?
Ditto what planB said earlier. Speaking from the perspective of a commercial eQMS supplier, the overwhelming majority of our customers have all of their requirements addressed by our Master License Agreement, and don't have a separate SQA. Occasionally a new customer will have additional requirements outside that scope, and if they make sense we work out an addendum to cover those specifically.

Separately, to another commenter's point about software changes: Just one supplier's perspective, but we'd never change the software out from underneath a customer. Each hosted customer has separate environments for Production vs. Upgrade Testing, and when a new version of the software is released (3-4 times/year), we refresh the customer's Upgrade Testing environment with a new copy of their Production data, and then update that environment to the new version. We provide a detailed list of all changes, so they can use that environment to review whether they want to update to that version and perform any validation, before requesting that we update their Production environment with the new version. Some customers may even skip a couple versions of the software before catching up later when some new features or modules drive their interest.

Anyway, just one datapoint. I'm sure other suppliers have different approaches/policies.

Jim Ivey
Grand Avenue Software
 

LUFAN

Involved In Discussions
#6
Separately, to another commenter's point about software changes: Just one supplier's perspective, but we'd never change the software out from underneath a customer.
This is obviously the right method for eQMS solutions to MedDev and Pharma, however I have personal experience with company's marketing their software to those industry that publish change sometimes multiple times per quarter without advanced communication. That was a nightmare and never ending battle. System existed before I got there unfortunately otherwise I would have convinced management to find something else.

I certainly think there is a major difference in company's which start by designing software for the regulated industries vs ones that adapt to it. My example above is most definitely the later. Great software and functionality, but they were not thinking about "us" when they decided that was their software upgrade approach.
 
Thread starter Similar threads Forum Replies Date
S We're certified AS9100 / AS9006!!! Software and Service Provider for Aerospace AS9100, IAQG, NADCAP and Aerospace related Standards and Requirements 6
F 21 CFR Part 11 - Implicit requirements - Validation plan for a Software as a Service Other US Medical Device Regulations 1
sagai Is service related software a non medical device? IEC 62304 - Medical Device Software Life Cycle Processes 4
J Interpreting clause 7.5.2.1 (validation of software used in production & service) ISO 13485:2016 - Medical Device Quality Management Systems 2
M ISO 9001 Requirements for associated service - Design and develop software Design and Development of Products and Processes 7
M Service Level Agreement between Software Vendors and Client - Need help Urgently Software Quality Assurance 5
J Nonconformance Elimination as a business - Service - Software Service Industry Specific Topics 3
Y Software updates considered servicing (7.5.4) ISO 13485:2016 - Medical Device Quality Management Systems 4
S How to perform verification of the Statistical Analysis Software? Qualification and Validation (including 21 CFR Part 11) 2
I Document Control Software Document Control Systems, Procedures, Forms and Templates 2
E Software maintenance Process Software maintenance Process to IEC 6204? IEC 62304 - Medical Device Software Life Cycle Processes 3
L Micro-Vu InSpec Software Program Qualification and Validation (including 21 CFR Part 11) 6
A For software change - New Channel of interoperability CE Marking (Conformité Européene) / CB Scheme 4
T IVDR Medical device software CE Marking (Conformité Européene) / CB Scheme 8
N ISO 13485 7.3.9 Change control in medical device software ISO 13485:2016 - Medical Device Quality Management Systems 6
C SharePoint Contract Management Software General Information Resources 0
gramps What do you think about automated QA testing For software app industry? Misc. Quality Assurance and Business Systems Related Topics 5
V Software as medical device (SaMD) replicated for multiple clients through APIs IEC 62304 - Medical Device Software Life Cycle Processes 4
U API Spec Q1 - 5.6.1.2 C (3) - Design software Oil and Gas Industry Standards and Regulations 3
B Complaint Records - Accessing records on Easy Track Software Records and Data - Quality, Legal and Other Evidence 3
GreatNate Master Control QMS software Quality Tools, Improvement and Analysis 0
GreatNate Anyone using the Intellect QMS software? Quality Assurance and Compliance Software Tools and Solutions 1
S DHF/DMR/MDF for a software-only, cloud-based, single-instance device Medical Information Technology, Medical Software and Health Informatics 2
H Software Validation for FFS Packaging Machine Qualification and Validation (including 21 CFR Part 11) 1
E Any sample of a full software life cycle IEC 62304 report ( any class )? IEC 62304 - Medical Device Software Life Cycle Processes 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
J Do Software Subcontractors need to be ISO13485 compliant in the EU? EU Medical Device Regulations 3
D Safety data sheets software REACH and RoHS Conversations 2
N What are the software audit and control steps Reliability Analysis - Predictions, Testing and Standards 2
N Validating Software before getting approved as Class 2 device US Food and Drug Administration (FDA) 5
M Clinical Decision Support Software Question 21 CFR Part 820 - US FDA Quality System Regulations (QSR) 2
P Missing 1m visual alarm signal in case of software/display failure, mitigation? ISO 14971 - Medical Device Risk Management 3
S Asterisk in DOE minitab software Using Minitab Software 23
M Surgical angle measurement guide device with an application software Medical Device and FDA Regulations and Standards News 1
M Advice needed for SEH Compliance Software and ISNETWord Compatabiliy Occupational Health & Safety Management Standards 2
bruceian Software Quality Metrics Software Quality Assurance 11
optomist1 How Secure Are Our Software Systems Software Quality Assurance 7
M 'Active' device? Software/laptop with attached camera 'looking' at passive metal probe EU Medical Device Regulations 3
D Software validation team Misc. Quality Assurance and Business Systems Related Topics 3
O Any info on release date of FDA “Computer Software Assurance for Manufacturing and Quality System Software” document? 21 CFR Part 820 - US FDA Quality System Regulations (QSR) 0
L Radiology software Class I exemption Medical Device and FDA Regulations and Standards News 3
O Software for comparing text of PDF files Contract Review Process 2
J Implementing an ISO 13485 QMS Software ISO 13485:2016 - Medical Device Quality Management Systems 6
K Software Updates in the Field and ISO scope ISO 13485:2016 - Medical Device Quality Management Systems 2
M Recurrent event analysis software (python) General Auditing Discussions 2
Y UL 1998 Standard: software classes Software Quality Assurance 0
P Need a programmer for QVI's VMS software for optical inspection machine Inspection, Prints (Drawings), Testing, Sampling and Related Topics 0
S IEC 62304 software costs and time Medical Device and FDA Regulations and Standards News 3
S IEC 62304 - Software verification cost IEC 62304 - Medical Device Software Life Cycle Processes 3

Similar threads

Top Bottom