Know why each feature on your array that is off is off

Yes 2

Written down, with a date (a log, a screen, a document), and it meets your own plan.

Partly 1

Remembered, but not written down, or the record shows you missed your plan.

No 0

Nobody knows, or it was never done. A blank is a finding.

"None, checked on a date" counts as a record. No plan or target written down? Write your guess first, then measure: the guess is your plan.

Tap No, Partly or Yes for each question. Your score adds up as you go. Nothing you tap is saved or sent.

Five questions about your own setup

1. 1 When did you last read the licensed features screen, and is every feature written down as on, off or not licensed?

   Your answer, and where it is written down (with the date) The date you last read the array's licensed features screen, with every feature written as on, off or not licensed.

   Your answer

   No 0Partly 1Yes 2
   Score 0, 1 or 2This quarterNext quarter

   How to raise it

   Where to find it:

   The licensed features screen in the array's management page, or ask the maker's support for the list tied to your serial number.

   To get it to a 2:

   A dated list, read from the screen or the maker's list, not from memory, inside the interval your team sets. No interval written down? Write your guess and score against it.

   What this does not prove:

   The list shows what you hold. It does not prove a feature marked on is set up the way you think, or that it works. Row 2 is how you check.

2. 2 Does each feature's own settings screen agree with that list?

   Your answer, and where it is written down (with the date) For each feature, the status its own settings screen shows, and the date you looked.

   Your answer

   No 0Partly 1Yes 2
   Score 0, 1 or 2This quarterNext quarter

   How to raise it

   Where to find it:

   Each feature's settings screen in the array's management page. Reading it changes nothing.

   To get it to a 2:

   A dated note for every feature, and it matches the list from row 1.

   What this does not prove:

   A settings screen shows how the feature is set today. It does not prove the feature works when it is needed.

3. 3 For each feature that is off, is the reason written down, and who gave it?

   Your answer, and where it is written down (with the date) For every feature that is off, the reason, and who gave it. "Nobody knows" is an answer, and it is the useful one.

   Your answer

   No 0Partly 1Yes 2
   Score 0, 1 or 2This quarterNext quarter

   How to raise it

   Where to find it:

   Ask the person who set the array up. Write down what they say and who said it.

   To get it to a 2:

   A reason and a name written next to every feature that is off, with the date. "Nobody knows", written down, counts as a record but scores 1 until someone finds the reason.

4. 4 Do the change records back up each reason?

   Your answer, and where it is written down (with the date) For each feature that is off, whether the change records show when it was switched off, or that it was never switched on.

   Your answer

   No 0Partly 1Yes 2
   Score 0, 1 or 2This quarterNext quarter

   How to raise it

   Where to find it:

   The array's change log, your change tickets, or the notes from the person who set the array up.

   To get it to a 2:

   A dated change record that backs up the reason for every feature that is off. No record for one? That feature scores 1.

   What this does not prove:

   A change record shows who changed a setting and when. It does not show the reason was a good one.

5. 5 Which feature has been off the longest, and since when?

   Your answer, and where it is written down (with the date) Which feature has been off the longest, since what date, and whether anyone knows why.

   Your answer

   No 0Partly 1Yes 2
   Score 0, 1 or 2This quarterNext quarter

   How to raise it

   Where to find it:

   The oldest change record for an off feature, or the date the array was installed if it was never switched on.

   To get it to a 2:

   One named feature with a date and a reason from a record. If you decide to switch it on, do it in a change window (a planned maintenance slot) with the maker's notes, not on the day you find it.