Getting Started with MaP Bundle
MultiPing and PingPlotter Standard can both be downloaded from the Product Downloads page. If you already have a version of either MultiPing or PingPlotter (Standard or Pro) installed, here's an opportunity to make sure you're running the latest version.
MultiPing 1.01 and PingPlotter Standard v2.50 are the minimum versions of each tool required to take advantage of the MaP interoperability. Also, if you've exceeded the trial period on either product, and not purchased a license, then the MaP functionality won't work.
As covered on the the MaP Bundle product page, MultiPing's main focus is on the monitoring of multiple hosts (with additional functionality like the very flexible alert capabilities, ability to see trending with timeline graphs, etc.).
For example, you may have 20-30 servers you want to monitor for uptime. You can very easily setup MultiPing to watch those servers for you and configure an email alert to notify you when the network connection to those servers starts experiencing high latency. You also have the capability within MultiPing to then scroll-back on the timeline graph for that host to see network performance trending over time.
If you want to save all that historical data (for archival purposes, later analysis, to distribute it via email to other members of your team, your network provider, etc.) you will want to send that data to PingPlotter (Note: both Standard and Pro editions can receive this data - however PingPlotter Standard is the version that's packaged in the MaP Bundle). You can easily do this by right-clicking on that particular host and selecting the "Send data to PingPlotter" menu option. PingPlotter will then launch (if it's not already running) and load the data from MultiPing. You've got a number of things you can do at this point. Since PingPlotter will be paused waiting for your instructions, you can "Resume" tracing from where the data left off in MultiPing (by clicking the Resume button in the lower left-hand corner of PingPlotter) if you need to start digging deeper to diagnose and trouble-shoot a problem. You can also then save the data you brought over from MultiPing or save off a graph of that data.
Within MultiPing you can also right-click on a host and select the "Trace in PingPlotter" menu option to launch PingPlotter and immediately start tracing that target. The difference between this option and the "Send data to PingPlotter" feature is that by doing "Trace in PingPlotter" you don't bring the data over from MultiPing. Basically this option is for when you really don't care about that historical data (you're most likely still gathering data via MultiPing for that host), but instead you want to leverage PingPlotter's ability to see the entire route to a host to troubleshoot and diagnose where the problem lies.