small cleanups and clarifications

docs/recommendations.md

@@ -166,9 +166,9 @@ We have found that using structured workflows and deliberate infrastructure can
 
 ### Context specific considerations
 
-We note that implementations were partially motivated by scenario specific considerations. The first consideration would be whether there is a pre-existing infrastructure a lab should or must utilise. If there are existing solutions that can be used, continued and adapted use of that infrastructure is a very likely option. However, the issues, as described below (sample volume, finances, regulatory issues, etc) should be considered before committing to an existing solution. If there are outside factors dictating the use of an existing infrastructure, it is advisable to evaluate and describe the appropriateness of the existing solutions to ensure that all parties are aware of the actual costs that would be involved. See questions in the Subgrantees document for more information on using existing infrastructures.
+We note that implementations were partially motivated by scenario specific considerations. The first consideration would be whether there is a pre-existing infrastructure a lab should or must utilise. If there are existing solutions that can be used, continued and adapted use of that infrastructure is a very likely option. However, the issues, as described below (sample volume, finances, regulatory issues, etc) should be considered before committing to an existing solution. If there are outside factors dictating the use of an existing infrastructure, it is advisable to evaluate and describe the appropriateness of the existing solutions to ensure that all parties are aware of the actual costs that would be involved.
 
-The second consideration would be sample volume. The number of samples to be analysed within a defined period may determine how much resources are invested in the setup. An institution that will analyse 500-1000 isolates per year most likely needs a different setup than the one that will analyse 1000’s of samples. A bigger operation will require more resources, more up front design and development of the process, and more standardisation of both processes and analyses. A smaller operation might however choose to either co-opt other existing solutions, or to outsource the process to someone with a larger setup, i.e. most likely go for a SaaS like solution.
+The second consideration would be the expected data throughput for the lab. The average number of specimens to be sequenced and analysed per month may determine how much resources are invested in the setup. An institution that will analyse hundreds of isolates per year most likely needs a different setup than the one that will analyse thousands of samples per month. A bigger operation will require more resources, more up front design and development of the process, and more standardisation of both processes and analyses. A smaller operation might however choose to either co-opt other existing solutions, or to outsource the process to someone with a larger setup, i.e. most likely go for a SaaS like solution.
 
 The third consideration is that of available resources, both human and financial. Significant skills and knowledge is required to set up and run such systems. Some institutions have people inhouse that can run the setup, or learn how to do it, while other institutions rather have financial resources and may choose to use those funds to outsource the setup. This factor may to a significant degree dictate what kind of infrastructure level the institution chooses to go for. If there are inhouse human resources, an on-prem or an IaaS solution may be selected, while if not, an outsourced PaaS or SaaS solution might be more cost effective. As a general consideration, if considerable flexibility in the system is needed, it will be more efficient and cost effective to have the necessary competences inhouse which will increase the speed of communication and help ensure that there is no direct financial cost associated with introducing modifications than to use a purely vendored solution.