Hey Phillip,
I considered an approach like this to tailor reopens to the anchors that are actually working on a given day, but our decision has always been to feature anchors whose show it is, so I've never fleshed it completely out.
My thinking is that you would build an intro scene, a music scene, anchor1, anchor2, anchor3, and so on, then a close scene if needed.
Each element scene would do whatever you design and then end with a Scene Director Trigger and an offline event (but not on the music and reopen scenes.)

The Scene Director triggers would release pauses in the reopen control scene so each element can be the length you need it to be. Triggers only work on scenes that are online.

The first script event may not work at the very head of the scene director, so slide it down the way a bit. Anchor1, Anchor2, etc are fed by a static list in the Data Source tab of the Object Inspector with the columns named to match the text objects, otherwise you would have to assign objects to columns or vice versa.

Number the scenes in the Xpression Studio sequence to match your VBscripts.

The line Sequence.GetTakeItemByName(CInt(ID1.Text), item) converts the text 5101 to an integer

Reopen and music need to be on separate, unused layers so they stay online. You would decide what layers the element scenes play on depending on how you plan it----with just a dissolve between element scenes, using the same layer would work, but if you plan an effect from one to the next you'd probably want to use sequential, increasing layers.

Hope this helps...I'd surely like to hear back on whether you have success.
Oh, another approach would be to build all the scenes and then put them in a timed group in the Xpression sequence----but that is something the operator would have to build every show and what if they forgot?
Thanks,
James.
------------------------------
James Hessler
WAAY TV (ALLEN MEDIA BROADCASTING)
------------------------------