Skip to Content.
Sympa Menu

usatlas-hllhc-lartl2l3-l - Re: [Usatlas-hllhc-lartl2l3-l] [Usatlas-hllhc-l2deputymgmt-nsf-l] NSF annual report - clarification

usatlas-hllhc-lartl2l3-l AT lists.bnl.gov

Subject: U.S. ATLAS HL-LHC Upgrade LAr Level 2 and Level 3 Managers Mailing List

List archive

Chronological Thread  
  • From: Michael Tuts <tuts AT pmtuts.net>
  • To: John Parsons <parsons AT nevis.columbia.edu>
  • Cc: "usatlas-hllhc-lartl2l3-l AT lists.bnl.gov" <usatlas-hllhc-lartl2l3-l AT lists.bnl.gov>
  • Subject: Re: [Usatlas-hllhc-lartl2l3-l] [Usatlas-hllhc-l2deputymgmt-nsf-l] NSF annual report - clarification
  • Date: Sun, 15 Oct 2023 17:26:21 +0000

Thanks

Get Outlook for Android

From: John Parsons <parsons AT nevis.columbia.edu>
Sent: Sunday, October 15, 2023 1:04:58 PM
To: Michael Tuts <tuts AT pmtuts.net>
Cc: usatlas-hllhc-lartl2l3-l AT lists.bnl.gov <usatlas-hllhc-lartl2l3-l AT lists.bnl.gov>
Subject: Re: [Usatlas-hllhc-l2deputymgmt-nsf-l] NSF annual report - clarification
 

Hi Mike,

        I attach the draft of the LAr contributions to the FY23 Annual Report.
(I removed the parts from the other subsystems, but kept the various
section headings to aid you in putting everything together.)
        Any questions or comments, let me know.
        Regards,
                John

On 9/26/23 8:08 PM, Michael Tuts wrote:
> Aaargh, I sent the wrong DOCDB for the annual report. It is DocDB #1036.
> Apologies.
>
> *From:*Michael Tuts
> *Sent:* Tuesday, September 26, 2023 8:07 PM
> *To:* usatlas-hllhc-l2deputymgmt-nsf-l AT lists.bnl.gov
> *Subject:* NSF annual report - clarification
>
> Hi All,
>
> Apparently, there might be some confusion regarding the September
> monthly report and the annual report. If it was not clear in the
> previous message I sent:
>
>   * You do NOT need to send Rosemarie the NSF September monthly report
>   * You DO need to send me the NSF Annual Report (for 10/1/22-9/30/23).
>     It will take the place of the usual September report.
>
> I had included a copy of last year’s annual report in the previous
> message, but you can find it in DocDB#1022 if you want it as a template.
>
> Thanks, Mike
>
> ===== Here is what I sent on 9/19/23 ==================
>
> Dear NSF Scope L2 managers,
>
> The third annual (FY23 - October 1, 2022 – Sept 30, 2023) report to the
> NSF is due in draft form to NSF by October 24. I would like about a week
> to compile your report information before sending the draft,*_so I would
> like to get your report before COB October 17_*. For your convenience I
> have attached the previous annual report (10/1/21-9/30/22) that we sent
> to NSF.
>
> The nature of this Annual Report is different from the typical monthly
> report and in fact will take the place of the September monthly report
> (so there is no need to file a September monthly report separately with
> Rosemarie). So please work with your CAMs and Institutional Contacts to
> provide a narrative for your L2 subsystem that includes input to four
> sections (in different places in the document, so don’t forget to update
> _all four sections_ for your L2 system):
>
>   * _Work Accomplished in your L2 system by L3 (see p. 4-17 in FY22
>     report attached)_: ~1-2 pages of narrative on accomplishments in the
>     past year (10/1/22-9/30/23), and any pictures you might have of
>     equipment you have built during that period
>   * _International ATLAS Accomplishments and Plans (see p. 17-18 in FY22
>     report attached)_: ~1-2 paragraphs should probably suffice for your
>     international subsystem accomplishments and plans
>   * _US ATLAS plans for FY24 for your system (see p. 18-19 in FY22
>     report attached)_: A bulleted list would work well.
>   * _Retention and Materials and Tooling in Support of Operations (see
>     p. 19-20 in FY22 report attached)_: ~1-2 paragraph. As some systems
>     are nearing completion, you may have a better handle on what might
>     be needed to be passed on to Operations.
>
> Since the report is in Word, the most convenient form would be if you
> update all your four sections in Word and send them to me. If that
> doesn’t work for some reason, send me a text file that I can insert.
>
> Thanks, Mike for the PO
>
>  From our NSF MREFC Cooperative Agreement Terms and Conditions:
>
> /Annual reports/
>
> /  1) The Annual Report may be submitted in place of its corresponding
> monthly financial and status report, but must include the current
> monthly status information listed above./
>
> /  2) Annual Reports must also include a summary of work accomplished
> during the reporting period (i.e. the prior 12 months), including major
> scientific and technical accomplishments by subawardees and an
> accounting of financial expenditures and obligations./
>
> /  3) Each Annual Report must provide a brief overview of the
> accomplishments and plans of the international ATLAS program and the
> efforts of CERN and partners to upgrade the LHC, including any
> adjustments or plans under consideration that might impact the
> NSF-funded scope, schedule, or budget for this award./
>
> /  4) Annual Reports must recommend materials and tooling to be retained
> to support future operation of the detector, and recommendations for
> custodianship of these items./
>
> /  6) Annual reports must be submitted to NSF via NSF's electronic
> systems no later than October 31:/
>
> //
>
>
> _______________________________________________
> Usatlas-hllhc-l2deputymgmt-nsf-l mailing list
> Usatlas-hllhc-l2deputymgmt-nsf-l AT lists.bnl.gov
> https://lists.bnl.gov/mailman/listinfo/usatlas-hllhc-l2deputymgmt-nsf-l

--
______________________________________________________________________

John Parsons
Nevis Labs,              Email: parsons AT nevis.columbia.edu
  Columbia University   Phone: (914) 591-2820
P.O. Box 137            Fax: (914) 591-8120
Irvington, NY 10533     WWW: http://www.nevis.columbia.edu/~parsons/    

______________________________________________________________________



Archive powered by MHonArc 2.6.24.

Top of Page