Process: Evaluator Eddie

How does Eddie do his job?

GOAL: Eddie needs to make recommendations about how devices should be upgraded and maintained. 

1. Login. Note Evaluater Eddie repeats this process for every organization.   

2. Goes to the evaluations search screen to see which new evaluation requests came in

3. For each evaluation request:

   1. Open the request and sees the configuration of all the components of all the devices and their child devices that pertain to the evaluation.

   2. When he selects on a component in the configuration, the details of the suggested update will appear on the right

      1. Details on the right are a list of notifications and some of the important details that affect the selected component

         1. He can drill down into the notification associated with it

   3. If customer is SLA 0

      1. Nothing is done. No recommendations are made

   4. If customer is SLA 1

      1. Edited notifications automatically result in suggested recommendations

   5. If customer is SLA 2

      1. Eddie will make an educated guess if the suggested updates should become certified updates or if they should be ignored

   6. If customer is SLA 3

      1. Eddie will conduct patch testing to see if the components should follow the suggested update for the particular configuration.

      2. He can look in the Related Evaluations Tab to see if an evaluation was already done for the same device snapshot that also had the same suggested updates.

   7. After analysis, Eddie creates the certified updates and/or approves, rejects, or override the suggested updates. After he approves ,rejects or overrides them, they will become certified updates

   8. Eddie completes the evaluation request and marks the evaluation as complete

4. Eddie finishes all the evaluation requests for this org, logs out, then repeats the process for the next organization.

5. Determines that the notification is good enough to recommend a component to update to that version.

   1. if Sam reviews the notification and decides to not recommend, that also needs to be tracked and removed from the “notification needs attention” list.

Evaluation Search

This search pages is necessary for Evaluator Eddie to find the evaluations requests that he needs to address. He will typically search based by Status, Evaluation level, and Priority. However, there are several other search criteria that are necessary for him to search for a particular item. He can also assign evaluation requests to different people 

The search results will show the newest ones on top as those are normally the ones that need to be addressed immediately. It is likely that the ones that are older have already been taken care of so these will be pushed toward the bottom of the list. 

Evaluation Configurations

Evaluations are generated based on notifications created and edited by SVM Sam. Only after Sam edits these notifications will evaluations be generated with the suggested updates from the notifications in the configuration section

This is the default evaluation details page after a user selects an evaluation from the search page. The left hand view block houses all of the specific fields regarding the evaluation. Most of these fields will be filled out by the time Eddie views it. However, because there is no automatic way to update these evaluations after they are created, Eddie needs to manually edit it when the process changes such as the status and assignee. To do so, he will select the edit button on the top right of this section which will put the editable fields into edit mode.

The configurations subtab is automatically selected and shown when Eddie arrives at this screen. This section shows a list of all the components that this evaluation influences. The back end system will have done its best to populate the fields using the suggested updates information from notifications. The primary edits that Eddie will make in this section will be to accept, override, or reject the suggested version for each component by using a drop down. After he selects the option for each component and saves, the suggested version column will be color coded by the following: red if Eddie downgrades or rejects the suggested version or green if Eddie accepts or upgrades the suggested version. If the user selects accept, then the target version will automatically populate with the suggested version. If the user selects reject, then the target version will automatically populate with the current version. If the user selects override, then the target version field will be editable so the user can directly input what the target version should be. 

Related Evaluations 

This subtab lists all of the evaluations that have the same components as the current evaluation. This section is useful for Eddie to help make recommendations on component versions because he can peruse related evaluations and see what were the recommendations made in those cases. 

This section is read only. The left side lists all of the related evaluation. When the user selects on one, the right hand side will show the configuration details of that evaluation. It was designed this way so the user does not need to open up the link in a separate tab to see the configuration details. This is similar to the outlook model where a user can view details of emails without having to open them in a separate window. 

Add Attachment Popup

This popup will appear when Eddie clicks on the Add button that is in the subheader of the Attachments subtab. He will name the file, write a brief description indicating what the contents of the file are, and upload the file. 

Assign Evaluation Popup

This popup will appear after Eddie selects Assign under the Action drop down on the Evaluation search page. Here he can search for a user by username to assign an evaluation.