Abstract

AbstractThe up‐front systems analysis including consideration or development of a use concept as related to the threat of interest is essential in the initiation of the acquisition process for a detector for chemical and/or biological warfare agents. The analysis must address not only the application of a given technology, but also topics such as the employment concept, human factors considerations, and the performance envelope specifically focused on the threat. The analysis results in a series of requirements against which the system can be evaluated for effectiveness and utility. This case study will discuss the differences in design considerations of a handheld point chemical vapor detector and a man‐portable, vehicle‐mounted standoff chemical vapor detector as developed for the uniformed services of the Department of Defense as compared to the application for use by Homeland Security personnel. The article will focus on the differences and similarities in requirements and performance testing to illustrate how the intended use influences design and system qualification.The essential initial step in the development of any system is requirements definition. In this study, the primary discussion pertains to design, development, testing, production, and fielding of threat chemical vapor detectors. However, it is a significant point to make that development of any piece of equipment begins with an accurate requirements definition. The process is initiated when a user identifies a need in the field. In the case of equipment for Homeland Security, the “field” is wherever the user employs the equipment, such as at an airport security checkpoint, on a civil support team, or special team assigned to protect a unique asset. The need could be defined in terms of a complete void of capability, additional performance required as a result of a new threat, or perhaps a lower detection limit of a given material, for example. Several chemical agent detection systems fielded by the Department of Defense have immediate application to the Homeland Security mission. However, in order to ensure that the current system performance envelopes satisfy the requirements of the Homeland Security, the considerations such as use scenarios, detection limits, response to potential interferents, target materials detected, and life cycle costs must be addressed against the Homeland Security‐unique requirements. The involvement of the developer with the customer, tester/evaluator, and any additional parties that influence requirements is the key to ensuring that the end product will provide the desired capability.

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call

Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.