Dependency Mapping is often viewed from a purely IT configuration item (CI) perspective including racks, servers and such. We’ve been working with organisations that have been gaining great benefit from using our tool and specifically the drag node facility (shown in the graphic below) to map their key logical IT and business processes. One example is a financial services organisation that needed to track file transfers between their data centre and several of their customers. They wanted to see the end points, volume, status and speed of the file transfers graphically.
All well and good I hear you say, but doesn’t mapping all of these dependencies involve a massive manual overhead with staff creating these relationships using a graphical drag and drop tool? The short answer is no, we have a way to automatically (automagically :-)) read in your configuration information and dependencies from practically any machine readable source (files, database tables, etc) and create the graphical maps with no human intervention, we call this a data-driven approach and the great thing is as your source data changes our drag node dependency map changes too, staying up to date with no manual intervention.
Examples of the drag node depicting dependencies.