Date/time data requirements

Minitab Model Ops requires Coordinated Universal Time (UTC) date/time formats for prediction and stability requests.
Specifically, Minitab Model Ops uses the following standard Coordinated Universal Time (UTC) format:

yyyy-MM-dd HH:mm:ssZ

Separate the year, month, and day with dashes. Separate the hours, minutes, and seconds with colons. All date/time information, whether a Z is used or not, are assumed to be in UTC time. If you do not specify date/time information, Minitab Model Ops uses the current server time, also in UTC time.

Any excluded time information is the equivalent of entering 0 for the value. For example, if a time entry does not have minutes and seconds, the minutes and seconds are 0. Excluded date information is not permitted. You must specify a complete date.


For example, 2024-05-14 is May 14 of the year 2024. Because this format does not include time, the time is set as midnight and the time zone is Coordinated Universal Time (UTC).

For example, use any of the following to represent 8:30 in the morning in Coordinated Universal Time (UTC) on May 14 of the year 2024.
  • 2024-05-14 08:30:00
  • 2024-05-14 08:30:00Z
  • 2024-05-14T08:30:00
  • 2024-05-14T08:30:00Z

When you use a T instead of a blank space, you must also include HH:mm. If a time entry does not have seconds, the seconds are 0.

Using future and past dates

Requests with future date/time values are not supported. Prediction requests with prior date/time values beyond 3 months are not logged; thus, are not available in the drift and stability reports. Stability data are logged only if a matching observation id was found within the last 6 months.