SCCM OSD - How to accomplish LOB specific builds

In my organization, our current build process leverages applications 'groups' which are specific to various lines of buinsess.  This allows us to keep a rather generic 'base build' image, and then layer on the appropriate apps depending on which department will receive the device.  That was built heavily on the Altiris DS platform.
 
We are now trying to accomplish a similar design in SCCM 2012, but are running into some issues/confusion.
 
My first idea was to create multiple task sequences for building the machine and including the apps for individual departments.  This results in many full OSD task sequences (drop image, configure, install apps), so a minor change to the base build TS has to be reflected many many TS's.
 
Linking task sequences seems like a better approach (keep the OS image deploy and config in one TS, then link to the individual department 'app mix' TS based on a condition+variable.)  So far this appears impossible.
 
Curious if anyone else has a similar approach to OSD, and if so, how did you accomplish this in SCCM?  Are we trying to do to much in OSD and should rely on the SCCM software/application distribution model to get the LOB specific apps to the device?

Integrate MDT into your Config Manager environment, and then define roles within MDT. Then you can set a single task sequence, which will query those roles within MDT, and apply the LOB apps as specified.

I agree with Gunth0s...
 
we are doing the same thing and it works great...
 
we put in a front end wizard pane where the techs select the dept from a drop down and then it is fully automated after that including which apps they will get, what the osdcomputername will be (location-based on default gw-dept function-assettag { a chichago sales pc would be chi-sal-xyz1213}, and even what OU they will live in after they join the domain. (laptops and desktops are going to different OU and we base this on Is-Laptop true or false)
 
I even went as far as having 2 task sequences as we are deploying win 7 pro to desktops and enterprise (with bitlocker) for laptops and it auto applies the correct one based on chasis type :)
 
this much easier to manage than a TS for each dept IMO!
 
 

Thanks for the insite guys, does this same approach work for zero touch deployment scenarios?  I'm assuming that those roles can be deployed to known devices (vs having a tech select it at build time).
 
Just turned on MDT integration so I have a lot of exploring to do.

you should be able to since it is basically a refresh scenerio and most of that info should already be determined.
 
you can't really do zti for a bare metal build in a production environment... (i guess you probably could) but i don't' like the idea of just blindly accepting unknown computers into production, but that is just me) :)