Skip to main content

 

Background

TrendMiner provides a set of Time/Date Tags by default with installation. These tags deliver time and date information directly from the system – independent of any process data – and are available for all time zones:

  • TM_hour_* – Hour of the day

  • TM_day-* – Day of the month

  • TM_month_* – Month

  • TM_year_* – Year

Time/Date Tags in TrendMiner
Time/Date Tags for all time zones in TrendMiner

They allow for precise configuration of searches, calculations, or monitors tied to specific moments or recurring time patterns – think daily reports at a fixed time or tracking values at the beginning of each month.
For full details, see the User Guide.

 

🎓 Deep Dive & Training Resource

Want to go further? Check out these advanced trainings for practical, hands-on examples:

 

🌟 Community Inspiration – Related Posts

Here are great examples of how Time/Date Tags are already in action:

 

 

🛠️ Further Practical Tips & Tricks with Time/Date Tags

 

📧 Tip 1: Daily Email at a Specific Time with Dashboard Link

Benefit: Automatically receive a daily update via email – complete with a direct link to your live dashboard. 

Steps:

  1. 🖥️ Create a Live Mode dashboard showing your process overview, then copy the URL.

    Live Mode in DashHub

     

  2. 🔍 Set up a value-based search in TrendHub using Time/Date Tags (e.g., when time is 6 am for 2 minutes, here: daily) and save it.

    Value based search

     

  3. 📩 Create a monitor to send an email every day at 6:02 AM, pasting in the dashboard URL.

    Enable a monitor

    💡 Pro tip: Combine multiple dashboards/views by adding more links into the same email.

 

📊 Tip 2: Display a Value at a Fixed Time on a Dashboard for 24 Hours

Benefit: Capture a measurement at a precise time (e.g., 6:00 AM) and have it displayed in your dashboard tile until it updates the next day at the same time.

Steps:

  1. 🧮 Create a new formula with the value and the time of interest (e.g., at 6 am):

    if(and(A=B,A=6),abs(C),0) 

    Variable mapping:

    • A = TM_hour_* (based on your time zone)

    • B = TM_hour_*  shifted by 59 minutes 59 seconds

    • C = tag with your desired measurement

      Create a formula

       

  2. 📐 Create an aggregation based on the previous formula to receive the constant value measured at a specific time for the next 24 hours:

    • Tag: formula from step 1

    • Operator: Maximum

    • Direction: Backward

    • Interval: 24 hours

      Create an aggregation

       

  3. 📌 Add a Current Value tile to your dashboard using the aggregation tag as the component.

    Current valie tile in DashHub

     

💬 Conclusion / Call to Action

With Time/Date Tags, TrendMiner empowers you to align your analyses, reports, and monitors with exact time points—making it easy to automate workflows and empower timely decisions.

Now it’s your turn: How are you using Time/Date Tags in your workflows? Share your tips, dashboards, or clever formulas in the comments—we’d love to hear them!

Nice set of tags, very handy!

Is there a specific reason why we don't have minutes? Due to the 1 minute index resolution?


Hey ​@Roger Palmen,

 

Thanks a lot for the kind feedback and the great question!
With a 1-minute index resolution in TrendMiner, e.g., in searches a minimum duration of 2 minutes is required, so a 1-minute tag wouldn’t provide additional value in that context (see this article for more background).

That said, if you do have use cases where a minute tag is helpful – e.g. for very short cycles or specific analyses, provided that your index resolution is less than 1 minute– it’s absolutely possible to create your own time tags for minutes and import them via CSV. More details on how to do that can be found here: TrendMiner Tag Builder & Data Import.

Hope this helps – and thanks again for raising the point!

 

Best regards,

Natasha


Hi Roger! Indeed, if I recall correctly a tag with 1m steps does not work very well together with the default index resolution of 1 minute.

Depending on the use case, slightly larger steps (at least 2m) or a linearly interpolated minute tag might work. Note that it is always possible to import additional, more custom time tags via the csv import feature. Let us know if you would like some help with that.


Reply