Standardized User Notices

BC Project: FY06-10
Date of Policy: 16 Apr 2007
Last Updated: 26 Apr 2018 (see Revision Log)

HPCMP centers shall notify users of events or situations which affect significant numbers of their users. Such situations include, but are not limited to:

  • Scheduled and unscheduled system downtime
  • Emergency maintenance
  • Disasters
  • Critical Security Bulletins
  • Any issue that a center deems urgent

In the event of unscheduled or emergency system downtime, users should be notified immediately after the system is determined to be down. A follow-up notification containing more specifics, such as cause and expected return to service date/time, can be sent when these specifics become available. In the event of any type of downtime, a notification informing users of system availability should be sent out as soon as the system has been returned to production.

Delivery should occur through multiple channels including Email, Message of the Day, and Web Posting to provide the widest possible coverage.

Email

Notification must be sent to:

  • All enabled users of the center.
  • All S/AAAs with projects at the center.
  • HPC Help Desk.

Centers must establish and maintain email addresses of users and the S/AAA's, and have this information readily available. Membership in these lists is mandatory.

Message of The Day (MOTD)

Entry created in applicable system message of the day (MOTD).

Web Posting

Message posted on the center's website (e.g., Use the Web team's News and Maintenance Tool (NAMT)).

Centers shall follow established HPCMP and DoD security policies and procedures concerning information dissemination, especially regarding security bulletins and messages posted to public websites.

In the event of disaster or loss of connectivity, a center can ask the HPC Help Desk to send email and post NAMT messages on behalf of the center.


Revision Log
Date Revision
26 Apr 2018BC Team Audit
02 Jun 2016BC Team Audit
17 Apr 2014BC Team Audit
12 Sep 2012Emphasized importance of communicating with users whenever unscheduled maintenance or problem occurs
23 Mar 2012BC Team Audit
13 Nov 2008Added file containing blocked ports at participating sites
29 Nov 2007Changed link to Kirby, added other systems