Well id say ateast 1/4 orf the people here have designed their own pipeline and allmost all are up to maintaing their own on perosnal projects 
What exactly in this si so perplexing?
assets are files wich include textures, modells and such... save them on disk, prefeerably a server so everyone can acces it. It might be that you want to use some file management software on this to automate verison controll finding of stuff etc. At easiest this is just a plain disk with some directory sttructures and naming conventions on top. You can go as fancyt as you like but theres nothing realy facy to it even if you complicate it to the extreme. Such as offering a aui fro doing it wich makes it a push button solution for the user and a nightmare for the eytem admin. Basicaly any literature with topic on asset management, storahge or documentation systems decribe this deeply. Even a amanual on how to store physical things cover most of this.
As for the glue, whell theres a lot fo it. Somne are pure sytemm admin sutuff, such as making backup of important files. other are more prcise such as what image formats to use and where to store them.
Then theres how to cue your renders so that servers keep curning alot. And maybe how to build delatyed read archives and how to filter the data before renders.
You might even need soem strategy on how to slap two animation sdoen by 2 different animators to gether by script.
So could you be a BIT more precice. Id hate to go trough every piece of computer science stuff ever developped. Becasue a good 3d pipe prettymuch covers it all.