Database Reference
In-Depth Information
As we have returned the nodes rather than the properties on these nodes, our Neo4j
browser returns a nice graphical representation that immediately provides the
required insight.
Which buildings are affected if something happens to Appl_9
Hopefully, this is a very good illustration of the use case already, but we can make it a
bit more complex by including the RTO information. Let's examine one more query.
What BusinessProcesses with an RTO of 0-2 hours
would be affected by a ire at location Loc_100
One thing you would have already noticed is that there is something peculiar about
the RTO characteristic. Most people would assume that such a characteristic would
become a property of the (business) processes, but in our model, we have created
separate nodes to represent these characteristics and linked them together in a
chain of RTO values:
• An RTO of 0-2 hours precedes one of 2-4 hours
• An RTO of 2-4 hours precedes one of 4-24 hours
• An RTO of 4-24 hours precedes one of 1-7 days
• An RTO of 1-7 days precedes one of 7-14 days
• Andinally,anRTOof7-14daysprecedesonofmorethan14days
You can see this in the following browser graph. The advantage of doing this is
thatwecannowveryeasily"slide"alongtheRTO-lineandigureout"similar"
or "close to" RTO targets very easily.
