Difference between revisions of "User:Shawndouglas/sandbox/sublevel9"

From CannaQAWiki
Jump to navigationJump to search
Line 1: Line 1:
===License and SLA basics===
===Implementation basics===
Please describe the details of any applicable license agreements and SLAs (e.g., if SaaS) for the various LIMS products and services you provide, including any negotiable aspects of those agreements. Provide examples. Any relevant measurements and ranges for work performed by you (e.g., response times, accuracy) should also be clearly defined and stated. Explain what the cost implications related to any differing license or service levels are. Finally, explain whether or not your organization provides clients with a 30-day proof of concept test of the LIMS and any related services to ensure your organization can prove its marketing and operational claims.
Please describe your approach to implementing your on-premises or cloud-based cannabis testing LIMS for clients. You should address:


* the standard timeframe for implementation and onboarding (overall average or last 10 customers);
* whether or not a dedicated point of contact will be maintained throughout implementation, to the end of the contract;
* what resources clients will require to support the implementation and throughout the contract's duration;
* what client processes and procedures your organization has found to be vital to optimal implementation and operation;
* what device and database integrations are supported in an implementation;
* whether or not unsupported devices and databases can be added for support;
* how the impact or disruption of client resources is minimized during implementation; and
* what your normalization and fine-tuning procedures are.




Line 8: Line 16:




===SLAs for SaaS===
In the case of SaaS-related LIMS cloud agreements (if applicable) with your organization, please explain how software customization, upgrades, testing, and versioning are addressed in such agreements.


===Completion and handoff===
Please describe what steps are taken to ensure the implementation is complete, as well as how the software or service is handed off to the client afterwards. If your organization provides training and documentation at handoff, describe how this training and documentation is administered, and at what additional cost, if any.




Line 17: Line 25:




===Agreement failure===
Please explain how your organization monitors and measures its compliance with agreements, as well as client compliance with agreements. Describe what options are available to clients and your organization upon the other party failing to meet an agreed-upon term.


===Multi-site implementations===
Please describe the process used when implementing a LIMS solution or service to a client with many geographically dispersed facilities.




Line 26: Line 34:




===Business associate agreements===
If your organization's cannabis testing LIMS is offered via the cloud, state whether or not the hosting organization—whether it be your organization or a third-party organization—will sign a business associate agreement or addendum for purposes of ensuring the hosting organization appropriately safeguards protected health information, as dictated by the Health Insurance Portability and Accountability Act (HIPAA).


 
===Updates and releases===
 
Please describe the expected frequency and approach to providing and implementing security updates and versioned releases for your LIMS.
 
 
 
 
===Contract termination===
Please describe what happens with a client and their data at contract termination. If the cannabis testing LIMS is a cloud solution, the hosting provider—whether it be your organization or a third-party organization—should be able to explain their policy on archiving, deleting, and helping transition client data from any of their systems upon contract termination, including particulars about data formats, deletion methodologies, and transfer methods. Any explanation should include the respective termination rights of both the organization and the client.
 
 
 
 
 
 
 
===Organization termination or catastrophic loss===
Please describe what would happen to a client's LIMS and associated data in the event of your organization going out of business or suffering a catastrophic loss.

Revision as of 14:05, 21 August 2021

Implementation basics

Please describe your approach to implementing your on-premises or cloud-based cannabis testing LIMS for clients. You should address:

  • the standard timeframe for implementation and onboarding (overall average or last 10 customers);
  • whether or not a dedicated point of contact will be maintained throughout implementation, to the end of the contract;
  • what resources clients will require to support the implementation and throughout the contract's duration;
  • what client processes and procedures your organization has found to be vital to optimal implementation and operation;
  • what device and database integrations are supported in an implementation;
  • whether or not unsupported devices and databases can be added for support;
  • how the impact or disruption of client resources is minimized during implementation; and
  • what your normalization and fine-tuning procedures are.




Completion and handoff

Please describe what steps are taken to ensure the implementation is complete, as well as how the software or service is handed off to the client afterwards. If your organization provides training and documentation at handoff, describe how this training and documentation is administered, and at what additional cost, if any.




Multi-site implementations

Please describe the process used when implementing a LIMS solution or service to a client with many geographically dispersed facilities.




Updates and releases

Please describe the expected frequency and approach to providing and implementing security updates and versioned releases for your LIMS.

Retrieved from "https://www.cannaqa.wiki/index.php?title=User:Shawndouglas/sandbox/sublevel9&oldid=17140"