Request: Unique DCID for cue parts

Just curious, why would the cue part need a unique DCID if it is a part of the same overall cue? It makes sense that the parts inherit the DCID of their parent as they aren't a separate object.

Wouldn't it be better to use discrete timing and/or separate cues in this instance?

This has more to do with the CSV data rather than real-time control data. When exporting to CSV, parts are their own records/CSV lines. When importing from that CSV into other solutions, I'd like to be able to have a single match field that never changes for updating rather than having to match cue number and cue part from the CSV. 

If the DCID never changes, then it makes it easy to update table records if, for example, you move a cue within EOS.