BEECN Journaling System: Difference between revisions
From Portland NET Wiki
mNo edit summary |
mNo edit summary |
||
| Line 1: | Line 1: | ||
X | X | ||
In order to help ensure BEECN caches are ready for deployment at a moment's notice, PBEM asks BEECN volunteer teams to: | |||
* Once a month, do a visual check of their assigned BEECN cache (opening the box is not required); | |||
* Once a quarter, do an inventory of the BEECN cache (opening the box and confirming contents are present and functional); | |||
* Once a year, participate in a BEECN test. An inventory can be done concurrently with a test. | |||
The purpose of the BEECN Journaling System is to centralize monitoring of BEECN caches, which contributes to the [[BEECN Readiness Score]]. | A BEECN Coordinator should not always complete these tasks. PBEM recommends a BEECN Coordinator assign these tasks to be regularly completed by their team members in rotation. | ||
The purpose of the BEECN Journaling System is to centralize readiness monitoring of BEECN caches, which contributes to the [[BEECN Readiness Score]] and also helps PBEM address security concerns. The BEECN Journaling System is powered by Smartsheet, and BEECN volunteers make inputs to it through the [https://app.smartsheet.com/b/form/a24081bbae014eb89cd5d6357196b218 BEECN Journal Entry form]. | |||
<nowiki>__TOC__</nowiki> | |||
== BEECN Journal Entry Form == | |||
X | |||
