usatlas-hllhc-l2deputymgmt-nsf-l AT lists.bnl.gov
Subject: U.S. ATLAS HL-LHC Upgrade Level 2 and Deputies-NSF only Management Mailing List
List archive
[Usatlas-hllhc-l2deputymgmt-nsf-l] RVM: next steps
- From: Hal Evans <hgevans AT indiana.edu>
- To: "Usatlas-hllhc-l2deputymgmt-nsf-l AT lists.bnl.gov" <Usatlas-hllhc-l2deputymgmt-nsf-l AT lists.bnl.gov>
- Subject: [Usatlas-hllhc-l2deputymgmt-nsf-l] RVM: next steps
- Date: Tue, 17 Mar 2020 15:35:00 -0400
Dear NSF L2Ms and DL2Ms,
Thanks for your work in putting together the Requirement Verification Matrices for your systems. We're still waiting for a few of these to come in, but based on what's been received so far, a few issues have emerged.
1. Tech Specs update. In some cases, what is written in the US Technical Specifications Spreadsheet (docdb # 216) is out of date. We want the RVM to match exactly what's in the Specifications Spreadsheet, so if you would like to make any changes, now would be a good time to do them. I would suggest that any changes you do make be minimal in the spirit of keeping the US specs as simple a summary of the most important ATLAS specifications as possible.
Please let us know if you intend to make changes to the US specs.
2. Multiple institutes contributing to test of a given requirement. For the purpose of developing/verifying QA criteria, this does not pose any issues. There can certainly be multiple sources of input to QA. Also, multiple sites can perform QC tests on the hardware that is distributed to them. However, the situation is different for firmware QC since there the tests are really only performed once. Presumably this should be done at some centralized location where all the firmware and hardware are present (the CERN STF?) and not at individual institute test stands. This central location should be listed as the test site. We could then list the (single) institute that is responsible to see that the test is done correctly at the central location for each requirement.
3. QC for requirements. We should make sure that each requirement listed will actually be part of the suite of QC tests done on every item produced. For some requirements, it may be enough to demostrate that the design meets QA. We may want to add a "QC element" column that indicates whether this requirement is tested for all production items (100%), for only a subset of items (xx%), or is verified as part of QA (---).
Please let us know your thoughts on these issues, and also speak up if you have other questions or comments. Based on the feedback here, we can decide upon any changes to the current RVM format.
Please send at least an initial response by this Friday, March 20.
Thanks - Hal
--
^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v
Hal Evans hgevans AT indiana.edu
https://urldefense.com/v3/__http://pages.iu.edu/*hgevans/__;fg!!P4SdNyxKAPE!WFXyOw4UoX6nTdabbO_qgFZixp7mgUcF7HN7IRjQ8EQio5XfYjrB0k4HPsmJZQTg08cBp25fbdBsmTLjtXwQ-_GI60zF$ Tel: (812)856-3828 Fax: (812)855-5533
253 Swain Hall West Indiana University
727 E. Third St. Bloomington, IN 47405
v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^
- [Usatlas-hllhc-l2deputymgmt-nsf-l] RVM: next steps, Hal Evans, 03/17/2020
Archive powered by MHonArc 2.6.24.