Difference between revisions of "May 2008 Subsystem Review"
m |
m |
||
| Line 11: | Line 11: | ||
The scope of this review includes all aspects of the following Hall D systems and efforts: electronics, trigger, DAQ, event and hardware monitoring, experiment and detector controls, and detector integration, construction, and maintenance. Performance requirements, development and construction schedules, costs, and ES&H issues may be reviewed for all systems, as well as any other considerations that may influence the construction and operation of the Hall D detector. | The scope of this review includes all aspects of the following Hall D systems and efforts: electronics, trigger, DAQ, event and hardware monitoring, experiment and detector controls, and detector integration, construction, and maintenance. Performance requirements, development and construction schedules, costs, and ES&H issues may be reviewed for all systems, as well as any other considerations that may influence the construction and operation of the Hall D detector. | ||
| − | In addition, for electronics systems this may include functional design, technology choice, fabrication considerations, quality control, maintainability, and long-term viability. For computing systems this may include computing architecture, network design, data flow issues, protocol choices, and network and computing hardware choices. For software this may include functional design, complexity, coding and language concerns, testing and quality control, operational concerns, and long-term maintainability. For hardware this may include design philosophy, material selection, fabrication choices, levels of redundancy, commissioning procedures, costs for materials and labor, quality control, and operational reliability and longevity. | + | In addition, for electronics systems this may include functional design, technology choice, fabrication considerations, testing and quality control, maintainability, and long-term viability. For computing systems this may include computing architecture, network design, data flow issues, protocol choices, and network and computing hardware choices. For software this may include functional design, complexity, coding and language concerns, testing and quality control, operational concerns, and long-term maintainability. For hardware this may include design philosophy, material selection, fabrication choices, levels of redundancy, commissioning procedures, costs for materials and labor, quality control, and operational reliability and longevity. |
You are asked to address the following questions: | You are asked to address the following questions: | ||
Revision as of 17:33, 4 March 2008
Contents
Introduction
The May 2008 Hall D Subsystem Review will cover all aspects of Hall D that have not been reviewed previously under the auspices of the 12 GeV project office. This includes electronics, trigger, DAQ, event and hardware monitoring, experiment and hardware controls, and detector integration assembly, and maintainability.
Charge for the Review Committee
No charge for the committee has been established yet (Mar 2008). A potential charge, based on charges from previous reviews, might be:
The scope of this review includes all aspects of the following Hall D systems and efforts: electronics, trigger, DAQ, event and hardware monitoring, experiment and detector controls, and detector integration, construction, and maintenance. Performance requirements, development and construction schedules, costs, and ES&H issues may be reviewed for all systems, as well as any other considerations that may influence the construction and operation of the Hall D detector.
In addition, for electronics systems this may include functional design, technology choice, fabrication considerations, testing and quality control, maintainability, and long-term viability. For computing systems this may include computing architecture, network design, data flow issues, protocol choices, and network and computing hardware choices. For software this may include functional design, complexity, coding and language concerns, testing and quality control, operational concerns, and long-term maintainability. For hardware this may include design philosophy, material selection, fabrication choices, levels of redundancy, commissioning procedures, costs for materials and labor, quality control, and operational reliability and longevity.
You are asked to address the following questions:
1. Are the technical performance requirements adequate, appropriate, and complete for each system?
2. Do the current designs and plans appear likely to achieve the performance specifications with a low risk of cost increases, schedule delays, and performance problems? Are there opportunities for improvements in cost or performance that the design teams should consider?
3. Are the R&D efforts appropriate, complete, and likely to reduce risks?
4. Have ES&H considerations been adequately incorporated into the designs and plans?
Preparation
Below I list topics the review committee might focus on. Clearly the committee cannot investigate all of these in depth, but we can expect they will want an overview of all of them, and may probe a few in depth.
