Portfolio:Elements of Laboratory Technology Management - Revision history

Shawndouglas: Tweaks

2024-06-21T00:41:04Z

Tweaks

← Older revision		Revision as of 17:41, 20 June 2024
Line 5:		Line 5:
	'''License for content''': [https://creativecommons.org/licenses/by/4.0/ Creative Commons Attribution 4.0 International]		'''License for content''': [https://creativecommons.org/licenses/by/4.0/ Creative Commons Attribution 4.0 International]

	'''Publication date''': 2014		'''Publication date''': Originally published 2014; republished February 2021

			NOTE: This was originally published on [https://www.limswiki.org/index.php/LII:Elements_of_Laboratory_Technology_Management LIMSwiki.org] and is reproduced here using the same license.


	==Introduction==		==Introduction==
Line 383:		Line 386:
	# Stable operating system environment		# Stable operating system environment

	'''Education''': Facilities with integrated systems are built by people trained to do it. This has been discussed within the concept of LAEs, published in 2006.<ref name="LiscouskiAreYou06">{{cite journal \|title=Are You a Laboratory Automation Engineer? \|journal=SLAS Technology \|author=Liscouski, J.G. \|volume=11 \|issue=3 \|pages=157-162 \|year=2006 \|doi=10.1016/j.jala.2006.04.002}}</ref>{{Efn\|You can also find the expanded version of the paper ''Are You a Laboratory Automation Engineer'' [[~~LII~~:Are You a Laboratory Automation Engineer?\|here]].}} However, the educational issues don’t stop there. Laboratory management needs to understand their role in technology management. It isn’t enough to understand the science and how to manage people, as was the case 30 or 40 years ago. Managers have to understand how the work gets done and what technology is used to do it. The effective use (or the unintended misuse) of technologies can have as big an impact on productivity as anything else. The science also has to be adjusted for advanced lab technologies. Method development should be done with an eye toward method execution, asking "can this technique be automated?"		'''Education''': Facilities with integrated systems are built by people trained to do it. This has been discussed within the concept of LAEs, published in 2006.<ref name="LiscouskiAreYou06">{{cite journal \|title=Are You a Laboratory Automation Engineer? \|journal=SLAS Technology \|author=Liscouski, J.G. \|volume=11 \|issue=3 \|pages=157-162 \|year=2006 \|doi=10.1016/j.jala.2006.04.002}}</ref>{{Efn\|You can also find the expanded version of the paper ''Are You a Laboratory Automation Engineer'' [[Portfolio:Are You a Laboratory Automation Engineer?\|here]].}} However, the educational issues don’t stop there. Laboratory management needs to understand their role in technology management. It isn’t enough to understand the science and how to manage people, as was the case 30 or 40 years ago. Managers have to understand how the work gets done and what technology is used to do it. The effective use (or the unintended misuse) of technologies can have as big an impact on productivity as anything else. The science also has to be adjusted for advanced lab technologies. Method development should be done with an eye toward method execution, asking "can this technique be automated?"

	'''User community commitment''': Vendors and developers aren’t going to provide the facilities needed for integration unless the user community demands them. Suppliers are going to have to spend resources in order to meet the demands for integration, and they aren’t going to do this unless there is a clear market need and users force them to meet that need. If we continue with “business as usual” practices of force fitting things together and not being satisfied with the result, where is the incentive for vendors to spend development money? The choices come down to these: you only purchase products that meet your needs for integration, you spend resources trying to integrate systems that aren’t designed for it, or your labs continue to operate as they have for the last 30 years, with incremental improvements.		'''User community commitment''': Vendors and developers aren’t going to provide the facilities needed for integration unless the user community demands them. Suppliers are going to have to spend resources in order to meet the demands for integration, and they aren’t going to do this unless there is a clear market need and users force them to meet that need. If we continue with “business as usual” practices of force fitting things together and not being satisfied with the result, where is the incentive for vendors to spend development money? The choices come down to these: you only purchase products that meet your needs for integration, you spend resources trying to integrate systems that aren’t designed for it, or your labs continue to operate as they have for the last 30 years, with incremental improvements.
Line 660:		Line 663:
	They should also understand statistical process control so that the behavior of automated systems can be monitored, with potential problems detected and corrected before they become significant. Rather than simply being part of the execution of a procedure, they manage the process. We're talking about LAEs.		They should also understand statistical process control so that the behavior of automated systems can be monitored, with potential problems detected and corrected before they become significant. Rather than simply being part of the execution of a procedure, they manage the process. We're talking about LAEs.

	Those LAEs must be capable of planning, implementing, and supporting lab systems, as well as developing products and technologies for labs.{{Efn\|See ''[[~~LII~~:Are You a Laboratory Automation Engineer?\|Are You a Laboratory Automation Engineer?]]'' for more details.}} This type of knowledge isn't limited to the people developing systems; those supporting them also require those capabilities. After all, the implementation of laboratory systems is an engineering program and should be approached in the same manner as any systems development activity.		Those LAEs must be capable of planning, implementing, and supporting lab systems, as well as developing products and technologies for labs.{{Efn\|See ''[[Portfolio:Are You a Laboratory Automation Engineer?\|Are You a Laboratory Automation Engineer?]]'' for more details.}} This type of knowledge isn't limited to the people developing systems; those supporting them also require those capabilities. After all, the implementation of laboratory systems is an engineering program and should be approached in the same manner as any systems development activity.

	The use of advanced technology products isn’t going to improve until we have people that are fully competent to work with them, understand their limitations, and drive vendors to create better products.		The use of advanced technology products isn’t going to improve until we have people that are fully competent to work with them, understand their limitations, and drive vendors to create better products.
Line 699:		Line 702:

	<!---Place all category tags here-->		<!---Place all category tags here-->
	[[Category~~:LII~~:Guides, white papers, and other publications]]		[[Category:Guides, white papers, and other publications]]

Shawndouglas: Shawndouglas moved page LII:Elements of Laboratory Technology Management to Portfolio:Elements of Laboratory Technology Management without leaving a redirect: Namespace change

2024-06-21T00:12:48Z

Shawndouglas moved page LII:Elements of Laboratory Technology Management to Portfolio:Elements of Laboratory Technology Management without leaving a redirect: Namespace change

← Older revision

Revision as of 17:12, 20 June 2024

Shawndouglas: 22 revisions imported: Importing my work from LIMSwiki, using the same CC license

2024-06-18T15:44:09Z

22 revisions imported: Importing my work from LIMSwiki, using the same CC license

← Older revision	Revision as of 08:44, 18 June 2024
(No difference)

test>Shawndouglas: Text replacement - "\[\[Accelrys, Inc.(.*)" to "[[Vendor:Accelrys, Inc.$1"

2024-03-29T16:17:45Z

Text replacement - "\[\[Accelrys, Inc.(.*)" to "[[Vendor:Accelrys, Inc.$1"

← Older revision		Revision as of 09:17, 29 March 2024
Line 92:		Line 92:
	At the time of this writing, there is no standardized definition of an ELN, though a forthcoming update of [[ASTM E1578]] intends to rectify that. However, given the current hype about ELNs, any product with that designation is going to get noticed. Let’s avoid the term and replace it with a set of software types that addresses similar functionality:		At the time of this writing, there is no standardized definition of an ELN, though a forthcoming update of [[ASTM E1578]] intends to rectify that. However, given the current hype about ELNs, any product with that designation is going to get noticed. Let’s avoid the term and replace it with a set of software types that addresses similar functionality:

	1. Scripted execution systems – These are software systems that guide an analyst in the conduct of a procedure (process); examples include Velquest (now owned by [[Accelrys, Inc.\|Accelrys]]) products and the scripting notebook function (vendor's description) in [[Vendor:LabWare, Inc.\|LabWare LIMS]].		1. Scripted execution systems – These are software systems that guide an analyst in the conduct of a procedure (process); examples include Velquest (now owned by [[Vendor:Accelrys, Inc.\|Accelrys]]) products and the scripting notebook function (vendor's description) in [[Vendor:LabWare, Inc.\|LabWare LIMS]].

	2. Journal or diary system - These are software systems that provide a record of laboratory work; a word processing system might fill this need, although there are products with features specifically designed to assist lab work.		2. Journal or diary system - These are software systems that provide a record of laboratory work; a word processing system might fill this need, although there are products with features specifically designed to assist lab work.

test>Shawndouglas: Text replacement - "\[\[PerkinElmer Inc.(.*)" to "[[Vendor:PerkinElmer Inc.$1"

2024-03-28T01:40:42Z

Text replacement - "\[\[PerkinElmer Inc.(.*)" to "[[Vendor:PerkinElmer Inc.$1"

← Older revision		Revision as of 18:40, 27 March 2024
Line 16:		Line 16:
	Mercury switches and timers triggered by cams on a rotating shaft provided chromatographs with the ability to automatically take [[Sample (material)\|samples]], actuate back flush valves, and take care of other functions without operator intervention. This left the analyst with the task of measuring peaks, developing calibration curves, and performing calculations, at least until data systems became available.		Mercury switches and timers triggered by cams on a rotating shaft provided chromatographs with the ability to automatically take [[Sample (material)\|samples]], actuate back flush valves, and take care of other functions without operator intervention. This left the analyst with the task of measuring peaks, developing calibration curves, and performing calculations, at least until data systems became available.

	The direction of laboratory automation changed significantly when computer chips became available. In the 1960s, companies such as [[PerkinElmer Inc.\|PerkinElmer]] were experimenting with the use of computer systems for data acquisition as precursors to commercial products. The availability of general-purpose computers such as the PDP-8 and PDP-12 series (along with the Lab 8e) from Digital Equipment, with other models available from other vendors, made it possible for researchers to connect their instruments to computers and carry out experiments. The development of microprocessors from Intel (4004, 8008) led to the evolution of “intelligent” laboratory equipment ranging from processor-controlled stirring hot-plates to chromatographic integrators.		The direction of laboratory automation changed significantly when computer chips became available. In the 1960s, companies such as [[Vendor:PerkinElmer Inc.\|PerkinElmer]] were experimenting with the use of computer systems for data acquisition as precursors to commercial products. The availability of general-purpose computers such as the PDP-8 and PDP-12 series (along with the Lab 8e) from Digital Equipment, with other models available from other vendors, made it possible for researchers to connect their instruments to computers and carry out experiments. The development of microprocessors from Intel (4004, 8008) led to the evolution of “intelligent” laboratory equipment ranging from processor-controlled stirring hot-plates to chromatographic integrators.

	As researchers learned to use these systems, their application rapidly progressed from data acquisition to interactive control of the experiments, including data storage, analysis, and reporting. Today, the product set available for laboratory applications includes data acquisition systems, [[laboratory information management system]]s (LIMS), [[electronic laboratory notebook]]s (ELNs), laboratory robotics, and specialized components to help researchers, scientists, and technicians apply modern technologies to their work.		As researchers learned to use these systems, their application rapidly progressed from data acquisition to interactive control of the experiments, including data storage, analysis, and reporting. Today, the product set available for laboratory applications includes data acquisition systems, [[laboratory information management system]]s (LIMS), [[electronic laboratory notebook]]s (ELNs), laboratory robotics, and specialized components to help researchers, scientists, and technicians apply modern technologies to their work.

test>Shawndouglas: Text replacement - "LabWare LIMS" to "LabWare LIMS"

2024-03-28T00:32:14Z

Text replacement - "LabWare LIMS" to "LabWare LIMS"

← Older revision		Revision as of 17:32, 27 March 2024
Line 92:		Line 92:
	At the time of this writing, there is no standardized definition of an ELN, though a forthcoming update of [[ASTM E1578]] intends to rectify that. However, given the current hype about ELNs, any product with that designation is going to get noticed. Let’s avoid the term and replace it with a set of software types that addresses similar functionality:		At the time of this writing, there is no standardized definition of an ELN, though a forthcoming update of [[ASTM E1578]] intends to rectify that. However, given the current hype about ELNs, any product with that designation is going to get noticed. Let’s avoid the term and replace it with a set of software types that addresses similar functionality:

	1. Scripted execution systems – These are software systems that guide an analyst in the conduct of a procedure (process); examples include Velquest (now owned by [[Accelrys, Inc.\|Accelrys]]) products and the scripting notebook function (vendor's description) in [[LabWare, Inc.\|LabWare LIMS]].		1. Scripted execution systems – These are software systems that guide an analyst in the conduct of a procedure (process); examples include Velquest (now owned by [[Accelrys, Inc.\|Accelrys]]) products and the scripting notebook function (vendor's description) in [[Vendor:LabWare, Inc.\|LabWare LIMS]].

	2. Journal or diary system - These are software systems that provide a record of laboratory work; a word processing system might fill this need, although there are products with features specifically designed to assist lab work.		2. Journal or diary system - These are software systems that provide a record of laboratory work; a word processing system might fill this need, although there are products with features specifically designed to assist lab work.

test>Shawndouglas: /* Why "process" is important */ Fix

2023-11-18T00:09:58Z

Why "process" is important: Fix

← Older revision		Revision as of 17:09, 17 November 2023
Line 92:		Line 92:
	At the time of this writing, there is no standardized definition of an ELN, though a forthcoming update of [[ASTM E1578]] intends to rectify that. However, given the current hype about ELNs, any product with that designation is going to get noticed. Let’s avoid the term and replace it with a set of software types that addresses similar functionality:		At the time of this writing, there is no standardized definition of an ELN, though a forthcoming update of [[ASTM E1578]] intends to rectify that. However, given the current hype about ELNs, any product with that designation is going to get noticed. Let’s avoid the term and replace it with a set of software types that addresses similar functionality:

	1. Scripted execution systems – These are software systems that guide an analyst in the conduct of a procedure (process); examples include Velquest (now owned by [[Accelrys, Inc.\|Accelrys]]) products and the scripting notebook function (vendor's description) in [LabWare, Inc.\|LabWare LIMS]].		1. Scripted execution systems – These are software systems that guide an analyst in the conduct of a procedure (process); examples include Velquest (now owned by [[Accelrys, Inc.\|Accelrys]]) products and the scripting notebook function (vendor's description) in [[LabWare, Inc.\|LabWare LIMS]].

	2. Journal or diary system - These are software systems that provide a record of laboratory work; a word processing system might fill this need, although there are products with features specifically designed to assist lab work.		2. Journal or diary system - These are software systems that provide a record of laboratory work; a word processing system might fill this need, although there are products with features specifically designed to assist lab work.

test>Shawndouglas: Cats

2022-02-09T19:39:42Z

Cats

← Older revision		Revision as of 12:39, 9 February 2022
Line 697:		Line 697:
	==References==		==References==
	{{Reflist\|colwidth=30em}}		{{Reflist\|colwidth=30em}}

			<!---Place all category tags here-->
			[[Category:LII:Guides, white papers, and other publications]]

test>Shawndouglas: /* Abbreviations, acronyms, and initialism */

2021-02-18T19:23:35Z

Abbreviations, acronyms, and initialism

← Older revision		Revision as of 12:23, 18 February 2021
Line 665:		Line 665:


	==Abbreviations, acronyms, and ~~initialism~~==		==Abbreviations, acronyms, and initialisms==

	'''AIA''': Analytical Instrument Association		'''AIA''': Analytical Instrument Association

test>Shawndouglas: /* Abbreviations */

2021-02-18T19:22:10Z

Abbreviations

← Older revision		Revision as of 12:22, 18 February 2021
Line 665:		Line 665:


	==Abbreviations==		==Abbreviations, acronyms, and initialism==

	'''AIA''': Analytical Instrument Association		'''AIA''': Analytical Instrument Association