Process: SVM SAM

How does SVM Sam do his job?

GOAL 1:  SVM Sam needs to make sure notifications displayed here match the ones in SVM

1. Sam goes to the notification search page and searches for notifications that have the status = new

2. Sam opens one and edits it to make sure it has the correct information or to add missing information.

3. On notifications details page, he will associate the appropriate components to this notification based on the details of the SVM Notification.

   1. Sam will need to manually add components by vendor and name. If he also knows SVM component ID, he can also enter it here

   2. For each component, Sam creates suggested updates for it using information from SVM Notification.

4. Sam finalizes the notification and changes the status to done.

5. The notification is now marked as done.

Notifications Search

One of SVM Sam's jobs is to edit notifications sent from the SVM regarding patch updates. Therefore in our design, we had to make it easy for him to find the notifications he wants to edit. The search criteria consists of fields that are the most common ways for him to look for a notification. 

Notifications Details | Suggested Updates Tab

After Sam finds the notification he is looking for, he needs to edit it to match the one that is coming from SVM system. Because this system is not capable of populating the information directly into the following fields, Sam hes to manually transcribe information seen in SVM and put it here.  

Along with notification details, there are updates that are included in SVM notifications. These are the focal points in these notifications as this is key information that will help Evaluator Eddie make recommendations to SLA 2 and SLA 3 customers about how they should update their substation devices. SVM Sam needs to also include this information in the notification by adding the updates mentioned in the SVM notification.

Notifications Details | Affected Components Tab

This section is autopopulated when the notification is generated since notifications can only be created based on the components that are affected by it. We differentiated this from the notification details section because this information is not about the notification itself, but what is affected by it. Also because this is a read only view, it does not belong in a section that is completely editable. 

GOAL 2: SVM Sam needs to fill in missing component Ids

1. Sam wants to search for missing component Ids.

2. He goes to the Component search which will search for components in the component catalog

3. On that search screen, there’s an option to search for only components with missing SVM Ids

4. Sam will search SVM for missing component Id's by the component vendor and component name as these attributes uniquely define a component so the database will return a limited number of results.

5. Results generated. SVM Sam edits each component information and fills in the missing SVM component Ids that he finds in SVM

   1. However the vendor or component name may be spelled differently in SVM vs SDM populated from the As Found device snapshot. Sam will need to sort out the various spellings to determine the component Id in SVM if it exists

Components Search page

This is our standard search page which uses the EXTJS framework. The  yellow section is where the search fields go. After user selects on the search button, the grid below will show all results that pertain to that search. To enhance the search to find components that have missing SVM ids, we have also added a checkbox where SVM Sam could select it to only show components that have a missing SVM id. This way it will be easy for him to identify which components he needs to fill in missing ids. 

Component Details

After the user selects a component to edit from the search page, it will lead them to this component detail page which will be read only. To edit, SVM Sam would choose the edit option from the action drop down, which puts the detail page into edit mode. Here he can edit the component name, version, vendor, and add the missing SVM id. However, the notification section below is not editable. This will be the list of notifications from the Security Vulnerability Management bulletin that are related to the component, which will be handy for Evaluator Eddie to review before making decisions on how to upgrade certain device components.