Gold Day of the Daleks model (Cinema 4D R21, with Collada Export) 1.0.0

This is very nicely rigged. It has a nice, simple, and clean user interface that doesn't require a lot of explanation and pretty much any user could use. Barring some very nit-picky details, it covers all the bases of how a Dalek should be rigged.

I think the only major update I might suggest is adding another rigging method for alternate applications. As a long time C4D user myself, I often prefer XPresso rigging, mostly because I find it easier to do and more reliable than conventional rigging. That said, it's very much a C4D exclusive feature. Even the really robust applications like Maya don't have anything quite as easy to implement. However, even really robust applications like Maya can't use a rig like this.

Don't misunderstand...it's totally their loss that they can't use it. Conventional rigging, however less efficient and troublesome, is just more universal. Granted, without going into the applications and doing the rigging from within, the soft parenting constraints (again, I MUCH prefer C4D's system for this...I guess we're just spoiled) don't reliably transfer over to the other programs. And asking someone to go into half a dozen or more commonly used programs to implement a rig just isn't a very realistic expectation.

On the question of the model itself, I think it's extremely well modeled. It's nice and clean. Not a lot of unnecessary triangulation, and the materials are also quite good.

Any serious critique I could offer is going to come down to a question of methodology and personal preference. Nothing really strikes me as anything that would make any significant improvement. Everything I can add should be taken as suggestion, and not something that I feel affects the overall quality of the model.

With that, suggestions I can offer...
With the rigging, I very much like the interface you chose for the arm and gun positioning. I like 2D fields as well. The issue here is that we are quite literally using a square peg for a round hole.
In the corners, they clip into the body a bit. Adding two null objects (one for the home position and one as a child of each respective arm) and a distance constraint will keep the arms from moving into a corner and clipping into the body. Since one null is static, as soon as the one moving with the arm is a certain distance from the static one, the arm just stops. Advantage C4D, most other programs would break the rig with a setup like this (Granted, anything pre-R14 would too), but it works.
I did say it was nit-picky.

On the issue of modeling, a C4D feature I really like is the cloner. I'm working on a model myself that's going to sere as a set of plans for a real world build. So, having precise measurements is slightly more important than would be for a more casual situation. I just found the cloner produced more accurate coordinates for the bumps. I just needed to make sure the panels were subdivided properly (I also really appreciate the edge loop tool for this) and set the cloner to polygon center placement.

This also cuts down on the file size, since it's technically only one bump's worth of geometry instead of 56.

With all of that, you've probably figured out that I'm also a hardcore C4D person. Pretty much this entire review is less about critique and more about sharing ideas with a fellow user. When I saw how you rigged your model, it made me super happy that I found someone else that uses C4D much the same way as myself. Once I start posting my own models, I hope someone gets just as nit-picky reviewing my work.