Efficient Visualization Tool for Investigative Analysis: NodeXL

1. NodeXLVisualization Tool Teresa Yenovkian Program Analyst Compliance and Investigations Division

2. Original Concept • This project started out identified as “Predictive Analytics” • The investigators use tools such as simple flowcharts to record and organize the data which consists primarily of product codes, distribution information, PFGE results, production information, and sales receipts.

3. Original Concept cont. • This NodeXL Visualization Tool will be beneficial to both FSIS and consumers . WHY? • It will ensure more efficient results, showing connections between consumer illnesses , suspect product flow and producing establishments.

4. Basic Facts • What is Visualization? • The process of converting data entered on one or more spreadsheets into graphs that make the data more intelligible. • The information gathered by investigators during investigations is entered into: • FSIS Incident Management System (FIMS) • Incident Report (IR) • In Commerce System (ICS) • Investigation

5. Relationship Between IR and VT • The Incident Report (IR) provides the information which enables completion of the NodeXL Visualization Tool (VT). • When completing the IR its essential for everyone involved to REMEMBER: • Accuracy • Completeness • Readability

6. Open IR - Approved

7. Open IR - Activated

8. Open IR – EMC Activated

9. Necessary Information in IR • Accurate name, address and establishment number • If a store in a chain the individual store number • Relationship between firms • Consumer directly related to illness (retail store, picnic etc)

10. Modifying an IR in FIMS • If placing an attachment in the IR note in the additional comments block the file name of the attachment (when modifying the incident) • In the “file attachments” section briefly complete the descriptions block • When modifying an incident write a short narrative of the modification

11. Components of the VT • The Tool consist of three main data sites: • Data Input (Input_e, Input_r) • Network Diagram Visualization (Spider Graph) • Timeline Visualization

12. Necessary Information for the VT

13. Main VT Input Screen

14. Input_e Screen

15. Input_r Screen

16. What is a VT “Spider” Graph ?

17. What is a Timeline?

18. Future • Next generation: • More user friendly tool • Incorporated into: • Public Health Information System (PHIS)FSIS • Incident Management System (FIMS) • Consumer Complaint Monitoring System (CCMS) • ICS

19. DEMO

20. Navigating the VT Folder • \\dchqfps7\shares\opeer\Opeer\visualization_tool • Open IRs • Create Folder using the IR number from FIMS • Closed IRs • Once an IR closes, move entire folder into here • Practice Folders • Main VT • Problem Files

21. Files to Use in VT Folders • NewTemplate.xlsm • This is the file that you will save with a new name in the new folder you created for the ongoing IR • May need to have multiple files for one IR, due to the large scope of the investigation • Master Word Document for Graph • This is the file that you will paste your VT graph into before sending for final approval • Tracker • This is the file that shows the updated status of all ongoing IR investigations

22. Review User’s Guide • Step by Step Instructions in Creating Your Graph • Enter Entity Information in Input_e Tab • Enter Relationship Information in Input_r Tab • Go to Start Tab and Follow Steps 2-3 • Show Graph and make necessary modifications • Copy Image to Clipboard & Paste in Word Doc • Send graph to Team Leader for review • Make any necessary changes

23. Practical Exercise Create your own vt graph

24. Practical Exercise Step 1 • Create Folder and File on the Shared Drive • Use the IR number for both folder & file name • Will reflect the year, month, day and incident number • To create the file, copy the file, NewTemplate into folder and rename • Put entry in Tracking file • Open the IR, list time/date current for information • Use green for open IRs • Create Template for Initial Graph • Copy Master Word Document for Graph to new folder • Rename file with IR number and current date

25. Practical Exercise Step 2 • Pull Initial Information out of IR in FIMS • How to determine what information to use • Number of Consumers/Case Patients • What to do when there is no FDIB Line List • What to do if the Consumer ate at a “friend’s” home • Pull Information from the Investigative Plan • Usually gives additional details on either Point of Purchase locations or Distributors • May give product information, i.e., from specific Establishment (this has not been proven)

26. Practical Exercise Step 3 • List all Consumers • At this point all consumers use a 1 illness flag • Use FDIB Line List, if available • If multiple consumers from one state and they all lead to an unknown point of purchase, list state with number of consumers • List all Point of Purchases • If there is a single location, leave illness flag blank • If there are multiple locations, use a 2 illness flag • If the location is unknown, use a 3 illness flag • Use store/location #’s, if known, or city/state

27. Practical Exercise Step 4 • List all Distributors • Leave all illness flags blank • Most large chain grocery stores use their own distribution center, i.e., BJ’s, Wal-Mart, Giant • Use city/state to differentiate, if needed • List all Manufacturers/Suppliers • Leave illness flag blank if the Est # is known • If it is a Foreign Est., use 4 illness flag • If it is a named source and Est # unknown, use 5 • If it is a live cattle supplier, use 6 illness flag • List the Est # in parenthesis after name

28. Practical Exercise Step 5 • Save Your Document Prior to Entering Relationship Types • Enter Relationship Types on Input_r Tab • Start with your first Consumer and list all relationship types known • Ensure when entering that you note all Point of Purchases when there are multiple, you may have several lines with one Consumer • Remember ALWAYS use the drop-down lists---DO NOT type names on this worksheet • May be easier to fill in the TO column first

29. Practical Exercise Step 6 • Save Your Document Prior to Data Validation • Run Data Validation • Click Yes to continue when asked are you sure • Once complete, ensure rows 23 and 24 have no errors (From and To Relationships) (click OK) • Run Select Network Type • Use Regular, unless you are looking at specific group or product information • Click OK multiple times until it says Data Success …Push to Show Graph, then OK one last time

30. Practical Exercise Step 7 • Push Show Graph • Select Sugiyama as your default graph choice • Verify/modify, as needed • Copy Image to Clipboard • Paste Image to Word Document • Modify Graph, as needed • Update Header in Word Document with the time the graph was generated • Save file with the day/time of the graph

31. Customizing Your VT Graph • Changing the format of the Lines using NodeXL • Color and Width of Lines depending on traceback verification • Rearranging the layout for Optimal Viewing • Placing all Consumers in one location with POP, then Distributors, then Mfg and finally Suppliers • No crossed lines, if possible, change colors to show different relationships if crossing is inevitable • Changing the format of the Lines using Paint • May need to dash a line using Paint • Adding Comments/Notes using Word • If multiple distributors link to one manufacturer, may need to notate which received product from which supplier

32. Practical Exercise Create a word document with notes and dashed lines

33. Procedures to Remember • Ensure team leader sends the updates to you along with everyone else • Email graph to team leader prior to CID Director, Regional Director, etc. • Once approved by team leader, send graph to “team” and “management” • Uploading graph to FIMS—how, information required, what not to do • Updating the tracking log • Monitoring and updating twice daily

34. Procedures to Remember • This is the #1 Priority • What to do if it is during scheduled time off—who’s your back up? • Create schedule for vacations in VT Folder • Utilize Out of Office to show who to contact • VT practice folder—monthly review • Monthly hands on exercise • Follow up meeting to discuss

35. Review • What did we learn today? • Any questions/problems? • Additional information/documentation desired

36. Other Notes: • Investigative Plan • Should include the MA’s names for all regions affected • Receive initial notification from RD • Monitor IR in FIMS twice daily • Send initial email to Team Leader • MA is responsible for creating the VT Graph, so have them send you copies of the daily summaries & any relevant information in between • Your name should always be part of the cc line of the email traffic • Let them know you will be sending the VT Graph for verification prior to emailing to management and posting in FIMS • Only one VT Graph posted in FIMS at once

37. “Common Mistakes” • Illness Flag • Using the number of illnesses in the state instead of illness flag 1 and putting multiple entities in the system • Putting the illness flag number under the group entity column • Putting the point of purchase illness flag number under the consumer’s name, i.e., 2 or 3 not a 0 or 1