I don't think I have a whole lot to add - I think I basically already covered everything in my earlier posts.
We had a three-day class last November. We didn't send Michael anything before class, I just talked to him over the phone and explained that we are surveyors and not engineers, we do lots of construction surveying (both site and roadway), we do lots of design surveys, lots of volume calcs, and lots of plats. By this time, Michael had a lot more experience teaching C3D than when he did Dino's class, so he didn't seem to need to know much else.
Michael didn't see any of our data until the class, but that didn't seem to matter. The bulk of the students had not used C3D at all, and there was more than enough for them to learn. From time to time, Michael would decide we needed to grab some data, like a surface to use as a daylight target for our corridors. So we would go grab one from one of our projects. We did this a few times in a few different ways, and learned a variety of ways to get data - from XML, directly from old Land Desktop projects, or by importing CSV data and adding the points to a surface. We had not been using the FBK stuff in Land Desktop, so that was a new item for us, but Michael provided us with a sample FBK file that we used for the class, and we used the surface created by that FBK file at one point. Other than that, it was basically all our data. (I later used the FBK file he provided as an example for getting our office using automated linework, which has been an overall boon to our office despite the flaws in the design of the process.)
At another point, he started showing us how to do some construction calcs from the type of data we usually get. In this particular case, we used a parking lot that we needed to stake. We had terribly messy linework provided by another company that was not using Civil-3D (and may not have even been using Land Desktop). Contours were hand-drawn - incorrectly, of course. Our only good vertical data came from spot elevations on the flowlines. Plus, it was drawn by someone who apparently had an aversion to OSNAPs and commands like Chamfer, Fillet, and Offset - in other words, the data was about as bad as it could get. Over the course of a couple of hours, Michael showed us how to turn the terrible drawing into one with nice, solid linework that we could turn into feature lines, which we graded with the Elevation Editor. In a very short period of time, we had a 3D model of the parking lot, complete with contours that were far better than the flawed and impossible ones the engineer had drawn in. (This then led to the question of how to create stakeout points for 3' offsets to TBC from the feature lines, which eventually became the motivation behind the STAKEFEATURES command in the SincpacC3D.)
All in all, we spent very little time retrieving and cleaning up data, and I think we got about as much C3D training as the guys were able to absorb at once. By the end of the three days, we had EVERYONE in our company creating surfaces, alignments, feature lines, parcels, and simple corridors. This was in comparison to the Sitelines webcast that we had been watching on Autodesk's web site, where we watched one woman at a company go spend a week at official Autodesk training, then spend the next five months struggling to accomplish what everyone in my office could do after three days of training.
And I suppose the ability to pull in all kinds of data is more important to us than to engineers, who create much of their data. But it was a critical aspect of the class for us. We have little say over what sort of data we get, it's usually sloppy and difficult to work with, and it's never done in C3D, but we still have to deal with it. For us, pulling in "bad data" and making it usable is actually a large part of using C3D, one of our most-frequent tasks. Training that did not cover this aspect of C3D would have ill-served us. It was definitely not a distraction from "more important" topics, or anything like that. It was critical knowledge, and probably a large part of the reason why we didn't follow the path of some others we've seen, who get C3D and training, only to drop C3D in frustration a month or two later.
Of course, after the class, we had no idea what lay ahead with regard to creating Plats. But as it turns out, there's probably enough in Parcels and Parcel Labels and the related sundry mess that it could take up a complete three-day class in itself, and Michael was undoubtedly wise to leave that topic out of our three-day intro...