Here is one thing to watch out for, as it caused me some serious heartburn when I put this into motion.
We had old lookups which were created, and I had to re-build them. The reason was, the lookup Hidden Key said lookup_code instead of lookup_enum. I had to recreate some of them to be lookup_enum (to go the admin tool, click Lookups, find your lookup, then click Parent Window) because the ID of those values is where your numerical score would be (example, on some we used a scale of 0, 25, 75, 100). That was the main gotcha for us.
The rest was a matter of making sure the scoring and weighting made sense based on various combinations of selections, and making sure your overall score was meaningful. Also note that calculated attributes are not stored in the database, thus they are not available for reporting. They are however stored as objects so if you can pull them in as a column into your portfolio.
Happy to help wherever I can!
Lori
Lori.Hagewood@asurion.com