Keep the naming short using the FYxx-FYyy format. This format allows the administrator to see the scope and name of the Time Range in the module blueprint without referring back to the Time Range itself; it fits within the column of the blueprint. This aids auditing and analysis
However, this does mean that the Time Range may need to be renamed if the range changes, so if your Time Range needs to be incremented each year, and it is clearly documented, an alternative would be to use a generic name ("History Years"). It requires less maintenance, but is not as clear
Best Practice article:
Time Range Application
Questions on this topic? See 1.01-06 Time Range Naming in our Planual forum.