Ok, well, evidently there are systems out there I don't know about.
If you only have the one scanner, you won't be able to follow audio conversations with something like Trunkview. However, you will be able to figure out talkgroup and radio IDs.
All you have to do for MPT1327 is take a cable and patch it from the headphone jack on your scanner to the line-in jack on your sound card. Make sure your system is set up to use the sound card for "recording" (I don't have a Windows machine handy, but if you go Start>Control Panel>Sounds & Audio Devices>Volume Control, I think you may be 90% of the way there). Run Trunkview and it should start receiving data almost right away.
Determining the channel number(s) will be your next task. Much like UHF/VHF Motorola trunking, MPT systems have a base, step, and offset setting. The only way to know what setting to use is to start running the Trunkview program and get some data, then figure out what you have. Having a second scanner you can play with while Trunkview is running is especially helpful here. For example, if you see a voice call (known as a Go To Channel on an MPT system) come up, scan (with your non-Trunkview occupied scanner) through the other frequencies on that site/tower. Once you hear a voice, you're (hopefully, if the system isn't too busy) on the right channel.
Now, the frequency shown by the channel number and the one you see on your second scanner are almost certainly going to be not the same. For example, Trunkview might say the GTC (Go To Channel) command should move to channel 105, or frequency 187.2250, when you see on your other scanner that the actual voice channel is 217.1250. That would mean that you are exactly 29.9 MHz off (too low) in your settings. If you're lucky, Trunkview will catch at least one other channel while you're doing all this. If not another voice channel, then the control channel - which may come in the form of a Clear Down message. Let's say it says "Clear-down - return to control channel 135 (187.6000)". In this case you'd be lucky because 187.6 is exactly 29.9 less than 217.5 - the control channel of the site I'm using as an example (from your referenced public utility system). You'd then know that channel 135 is actually 217.5, channel 105 is actually 217.1250, and thus you have 12.5 kHz spacing (step) - because the difference (0.375) between the two channels goes into 0.0125 exactly 30 times.
Now you can figure out the base with a little bit more simple math. If 217.5 is channel 135, and the step is 12.5 kHz (0.0125 MHz), then channel 1 would be 217.5 minus (134 times 0.0125), or 215.825. So, with base 215.825, offset 0, and step 12.5 kHz, you should then get the right frequencies showing up on your Trunkview display. And now if you have a computer-controllable scanner, Trunkview will tune it to the proper frequency on every Go To Channel call, and you will hear calls on both "talkgroups" and "private calls".
I know that's a little lengthy, but it'll get you where you want to be. If you need more help, this thread is the place to come - citylink has a ton of info and spends a lot of time on these systems, I think, more than I did when I had them available in my area.