Calendar Entries
- Sean L McLane (Unlicensed)
- danao
- ejerome
- Jennifer Murray (Unlicensed)
https://www.itap.purdue.edu/operations/ioc-log/production/index.php
There are times when an admin advises us to ignore an alarm/alert until further notice. If that happens, the entry needs to remain on the log for three consecutive shift logs. After the entry has cycled through three logs, the entry needs to be moved to the shift log calendar and not made as a regular log entry. If at all possible. please try to get the admin to commit to a time period or definition of what “until further notice” means. If the admin provides a timeframe, use that for the duration on the calendar. If the admin can’t/won’t provide a period of time then put it on the calendar for the duration of a week. Once the duration has ended then the admin will need to be contacted to provide an update on the alarm/alert. Remember it is part of your daily duties to check the shift log calendar on a daily basis.
How to add a calendar entry:
First, you must get to a page with the "Add Event to Calendar" button. You can click on any current or upcoming event from the active log or select the Calendar option from the Site Utilities dropdown menu (calendar will usually take a little time to load). In either case, the add event button will be in the top left of the next page.
Second, you fill in details as necessary. As noted in the below screenshot, start and end dates must be entered in MM/DD/YYYY format and the end date must be after the start date to save properly. Event titles must be maximum 32 characters or the entry will not save. Editing an entry and using a title that is too long will also prevent that entry from saving again, essentially deleting it from the calendar.
Example errors:
How to edit a calendar entry
Any event can be edited by clicking on the pencil icon from its page.
If editing a previous/ongoing entry and adding new information, these edits are usually separated on different lines with the edit date added in front for clarity.
How to end/remove a calendar entry
If an alarm clears, it can typically be removed from the calendar. In this context, removing means editing the event and changing its end date to the current day or a previous date as needed. If you delete an event, that removes it from the entire calendar.
Preferred method: editing the end date
Deletion is not generally required.
Asking for follow-up on DCM calendar entries
As mentioned further above, once an event's duration has ended, the admin will need to be contacted to provide an update on the alarm/alert. For any Data Center Management (DCM) alarms, that contact happens about once a month, before the ongoing events expire. (Entries can be temporarily extended until we get a reply.) Depending on their reply, we can extend the events by another month, add/remove any requested information from specific entries, or end the events as needed.
While it may be easiest to copy and paste entries from the previous month's email, the general email format is copied below:
To: ITIDataCenterManagement@groups.purdue.edu
Subject: Follow-up about Struxureware/Siemens/Metasys/walkthrough alarms to ignore in calendar (Monitoring systems can be removed or added as necessary.)
Body:
Admins,
Are the following alarms to ignore still current?
Calendar Entry Formatting
Group - Title: Description - current event ending date (All text would typically be left black, but this color legend helps show how the different fields are copied into the email. The event screenshot below also has the relevant areas circled/highlighted in similar colors.)
Example entries:
DCM - Strux: pfw and pnw devices: StruxureWare: new devices being added for PFW and PNW. Ignore these groups until further notice. - 01/08/2024
DCM - MSYS: Module 4, 7 & 9:
Metasys: Module 9 Airstack fault value 2 - Ignore alarm.
10/03/23 - Module 7 Airstack fault value 4 - Ignore alarm.
10/06/23 - Module 4 Airstack fault value 3 - Ignore alarm. - 01/08/2024
DCM - Walkthru alarms to ignore:
Always ignore A31 alarm for MATH-G190-CIT-CDU-01 since it is plumbed incorrectly. Ignore A28 for MATH-G190-CDU-A PDU-3 C28 unless water is pooling in unit. G190 CDU-F had alarm codes "w23" primary filter dirty. Ignore G190-PDU-20 alarm and dead screen.
10/3/23 - Math-g190-crac-8 has been shut off and will be removed eventually.
10/23/23 - Walkthroughs: Math B60 CRAC-1 error message "REM SENSOR 3 FAILURE." Ignore alarm.
11/6/23 - Math B60 unit CAB 4 active alarm "Internal Comm Error." Ignore Alarm Math B60 crac-02 and 03. Both listing "general" and "WRN REM SENSOR 3 FAILURE." Ignore alarm.
11/23/23 - Fast, steady drip coming from sixth Negishi unit door (K-10). Admin disabled MATH G109 Rack K-10 Rear Door Cooling. RCAC Engineers and DCM will investigate further on Monday (11-27). - 01/08/2024
DCM - Siemens: Unack Report:
Siemens: Alerts MAP4W1, MAP4W2, MAP5CA, MAP5CAL, MAP5W1, MAP5W2 in Unack report related to MATH DC Issues.
10/19/23 - Siemens: Siemens report was not working correctly after power outage. Admin will have vendor investigate.
10/27/23 - There are currently no alarms in Siemens. However, continue to ignore all Siemens alarms as the backup chiller is offline since the campus power outage. - 01/08/2024
DCM - TEL/MATH Key Card Checkout:
Vertical Horizon Networks has checked out TEL key cards #596076 and #596077 and return them after work is finished in 30 days. Ron - Contractor received TEL Cards as of 06/06/2022
7/24/22 - Keycards are still missing from IOC binder - assuming these have not been returned yet.
8/26/22 - Keycards checked out by Ron and Greg until further notice, approval given by Todd.
8/14/23 - Todd took TEL Department Guest cards/MATH key cards 600083, 600084, and 600085 to be issued to contractors.
8/18/23 - 600083, 600084, and 600085 issued to Greg Piercy, Quentin Foley, and Nathan Lane respectively. - 01/08/2024
These summary statements are separated by monitoring system. Screenshots can be included for clarity. If a system has no alarms, then it can be omitted. You may also state that [insert monitoring system] has no noteworthy alarms.
Example statements:
The only red alarms currently showing in Metasys are for Airstack Modules 4 and 7.
The only red alarms currently showing in StruxureWare that are not marked for maintenance are haas-234-pdu-01, math-g190-crac-01, 2550-1370a-crac-01, tel-210-crac-03, math-b60-crac-03, and lamb-20-apc-5000-02.
The only unacknowledged alarms currently showing in Siemens are for MAP4W1, MAP4W2, MAP4WET, MAP5CA, MAP5CAL, MAP5W1, and MAP5W2.
TEL Key Cards #596076 and #596077 are still checked out by Ron and Greg with Vertical Horizon Networks. MATH Key Cards #600083, #600084, and #600085 are still issued to Greg Piercy, Quentin Foley, and Nathan Lane with D.A. Dodd contractors.
Signature:
[insert name]
Purdue IT IOC/Service Desk Specialist
(765) 496-7272
Example replies from DCM (original text left black and edits left red as they usually appear in the email):
DCM - Strux: pfw and pnw devices: StruxureWare: new devices being added for PFW and PNW. Ignore these groups until further notice. - 12/13/2023 continue
DCM - TEL/MATH Key Card Checkout:
Vertical Horizon Networks has checked out TEL key cards #596076 and #596077 and return them after work is finished in 30 days. Ron - Contractor received TEL Cards as of 06/06/2022
7/24/22 - Keycards are still missing from IOC binder - assuming these have not been returned yet.
8/26/22 - Keycards checked out by Ron and Greg until further notice, approval given by Todd.
8/14/23 - Todd took TEL Department Guest cards/MATH key cards 600083, 600084, and 600085 to be issued to contractors.
8/18/23 - 600083, 600084, and 600085 issued to Greg Piercy, Quentin Foley, and Nathan Lane respectively. - 12/13/2023 continue
DCM - Walkthru alarms to ignore:
Always ignore A31 alarm for MATH-G190-CIT-CDU-01 since it is plumbed incorrectly. continue Ignore A28 for MATH-G190-CDU-A PDU-3 C28 unless water is pooling in unit. continue G190 CDU-F had alarm codes "w23" primary filter dirty. remove Ignore G190-PDU-20 alarm and dead screen. continue
10/3/23 - Math-g190-crac-8 has been shut off and will be removed eventually. continue
10/23/23 - Walkthroughs: Math B60 CRAC-1 error message "REM SENSOR 3 FAILURE." Ignore alarm. continue
11/6/23 - Math B60 unit CAB 4 active alarm "Internal Comm Error." Ignore Alarm Math B60 crac-02 and 03. Both listing "general" and "WRN REM SENSOR 3 FAILURE." Ignore alarm. continue
11/23/23 - Fast, steady drip coming from sixth Negishi unit door (K-10). Admin disabled MATH G109 Rack K-10 Rear Door Cooling. RCAC Engineers and DCM will investigate further on Monday (11-27). - 12/13/2023 continue
DCM - MSYS: Module 4, 7 & 9:
Metasys: Module 9 Airstack fault value 2 - Ignore alarm.
10/03/23 - Module 7 Airstack fault value 4 - Ignore alarm.
10/06/23 - Module 4 Airstack fault value 3 - Ignore alarm. - 12/13/2023 continue
DCM - Strux: math-g109-pdu-06:
StruxureWare: The output current in phase L1 has risen above the output current high threshold of 320A math-g109-pdu-06.itap.purdue.edu. Call if sensor reaches 360A.
11/4/23 - StruxureWare: Admin testing alarm parameters. Ignore alarms for math-g109-pdu-06. - 12/03/2023 remove