To use the automated entity creation feature of Time Series, your data source must be configured to refresh automatically. If you are unfamiliar with how data loading works at your site, check with your system administrator.
Example 1
You have an initial load of a delimited file, and you want the Time Series project to automatically load a new file every quarter to check compliance. Since Trillium is rarely installed on the same system that houses the data source files, your system administrators can automate a process (probably using a simple UNIX shell script) to copy the quarterly files from the production location to the Trillium server, overwriting the original file. Because the quarterly file lands in the same place with the same name, it will be picked up by Time Series the next time it runs, creating a new entity.
Example 2
If your data source is a Relational Database Management System (RDBMS) table, the database contains every row entered. Your administrator may have to set up filters that pick up only those rows that have been created in the last quarter. The next Time Series entity is created against the same database, but it will pick up completely different records, depending on the filter results.