Functional objects are deemed to be valid from their entry into service until they are finally suppressed : their lifecycle spans the lifecycle of (possibly) several physical entities. For instance, track section from A to B may undergo maintenance, renewal, etc., but as long as the track functions are "available" between A and B (except during track possessions of course), the corresponding functional object (or net entity) "track" is considered existing and keeps its UUID.<br/>