Slaying Monsters in the Department of Defense with Graph Analysis
•
0 likes•219 views
Speaker: Brandon Campbell, Principal Software Engineer, Northrop Grumman
Recommended
Recommended
More Related Content
More from Neo4j
More from Neo4j (20)
Recently uploaded
Recently uploaded (20)
Slaying Monsters in the Department of Defense with Graph Analysis
- 1. 9/15/2020 Brandon Campbell 1 Slaying Monsters With Graph Analysis in the Department of Defense
- 2. Northrop Grumman Proprietary Level I 2
- 3. How I Became a Graphstronaut 3
- 5. An Elegant Solution 5 Consider this crane To store in table, unfold In graph, it is whole
- 7. Turning on the Light 7
- 11. Solution 11 “There is no such thing as garbage data – only garbage assumptions”
- 16. Engineering our Assumptions 16 What is a failure?
- 17. Engineering our Assumptions 17 A Boolean flag DBA
- 18. Engineering our Assumptions 18 A 4 hour drive and a 6 hour repair job Maintainer
- 19. Engineering our Assumptions 19 An inventory adjustment Depot Manager
- 20. Engineering our Assumptions 20 A threat to National Security System Director
- 22. Engineering our Assumptions 22 BrokenPart IS What counts as broken?
- 24. Engineering our Assumptions 24 BrokenPart Job CAN’T PERFORM IS What about parts that can be used in more than one way?
- 28. Objection 28 “I could do that with SQL”
- 29. Solution 29 “In graph, schemas are derived, not imposed!”
- 30. Prototype #1 30
- 31. Prototype #2 31
- 32. The Data Paradigm Problem 32
- 33. Ontologies & Knowledge Representation 33
- 34. Smart Data Pipe Demo 34
- 35. Ontologies & Knowledge Representation 35
- 36. Objection 36 “That looks more complicated, not less”
- 37. Solution 37 “Ask it a question”
- 39. Objection 39 “This sounds like a panacea”
- 40. Solution 40 “Think of it as a paradigm shift.”
- 41. Graph Analysis at Northrop Grumman 41