PlanMaker SECOND Function: Syntax and Verified Time Examples

SECOND is helpful for quality checks on timestamp granularity, spotting times unexpectedly rounded to the minute, sorting alert logs by seconds within a minute, and validating exact minute boundaries. It is not enough to establish event order without date, hour and minute.

=SECOND(Time)

There is exactly one argument, so no argument-order ambiguity and no optional arguments or defaults. A cell reference such as A3 is not quoted; a text literal such as "12:34:56 AM" is quoted. The latter requires locale-aware parsing. This function does not accept separate hour, minute and second parameters—that is what the constructor TIME(Hour,Minute,Second) is for. The English manual uses comma-separated arguments for TIME; an installation may use a different formula-list separator depending on its settings. Official function page; TIME constructor.

PlanMaker stores times as numerical fractions of a day. To avoid ambiguous date strings, enter the formulas in column A below. The constructor TIME(Hour,Minute,Second) is described in SoftMaker’s TIME reference. Formula names and commas follow SoftMaker’s English documentation; if your installation uses semicolons for arguments, replace the separators accordingly. The displayed format may vary independently of the stored fraction. Format A2:A6 as hh:mm:ss if necessary. Do not type the visible time as a string.

Validation label: The component values above were independently calculated from 24-hour clock arithmetic with Python’s datetime.time; they are expected outputs, not observed PlanMaker results. Each constituent function is documented separately, but this complete sheet has not been opened in PlanMaker. If a locale uses another time display or formula separator, adapt presentation or separators rather than changing the intended numeric times. SoftMaker time entry documentation.

Place =SECOND(A2) in B2 and fill through B6. Independent component arithmetic predicts 0, 12, 56, 9, 59. SoftMaker specifically documents SECOND("12:34:56 AM")→56 and SECOND("09/25/2018 10:30:36")→36; these literal parsing examples are documented vendor claims rather than observed runs during this review.

Advanced: detect timestamps that include nonzero seconds

Put =SECOND(A3)<>0 in C3. For 06:45:12 this is independently TRUE; for TIME(6,45,0) it is FALSE. This can identify rows needing rounding if the stored input is a genuine time. For subsecond measurements, SECOND(...)=0 does not mean that no milliseconds remain: explicitly test the PlanMaker-only MILLISECONDS function or show fractional seconds in a suitable format.

Advanced: 67 seconds versus a 7-second component

Put =TIME(10,10,58) in D2 and =TIME(10,12,5) in E2. The independently calculated elapsed time is 67 seconds. =SECOND(E2-D2) extracts the component of that 1-minute-7-second duration, expected 7, whereas =ROUND((E2-D2)*86400,0) is mathematically 67, because 86,400 seconds make up a day. The ROUND step is a deliberate rounding policy that protects an integer-second result from small floating-point representation differences; it is not evidence of a PlanMaker rounding defect. Same-day assumption applies.

If the end time can fall on the next day, use dates plus times rather than calculating a negative time difference and guessing its meaning.

SECOND returns the seconds component, not millisecond precision. PlanMaker documents a separate MILLISECONDS(Time) function and the format-codes documentation includes fractional-second formats. A time printed as 12:30:56 may contain subsecond precision not shown by that display. Never infer the presence or absence of milliseconds from SECOND alone. How SECOND rounds a value near the next second (for example xx:xx:59.999) was not specified by the brief function reference and is pending native verification; this guide deliberately makes no claim about the exact boundary behavior.

Important uncertainty: The brief function page does not supply a complete matrix of conversion/overflow/error-code rules. No #VALUE!, #NUM!, precision threshold or input coercion is promised without application execution. Regional parsing, saved file formats and the numeric time’s stored precision deserve manual testing.

Microsoft Excel documents SECOND(serial_number) with a result in 0–59; PlanMaker 2021, 2024 and 2026 document SECOND(Time). Basic calendar-time purpose aligns, but syntax metadata differs and parity for text parsing, milliseconds, and error-code edge cases was not demonstrated through execution. For precision-heavy files, preserve the numeric datetime and separately test the Excel round-trip.

Official reference pages checked 2026-10-12 (UTC): PlanMaker 2026 SECOND, PlanMaker 2024 SECOND, and PlanMaker 2021 SECOND. The syntax printed on these three English manuals agrees. These are documentation checks, not proof that every installation and edition executes identical edge cases. More information: TIME constructor; regional cell entry; custom number formats. Excel SECOND reference was consulted as an interoperability reference, not a native test.

For adjacent components, refer to the official HOUR, MINUTE, SECOND and MILLISECONDS pages.

Verification summary: Official documentation and independent arithmetic were checked. Native PlanMaker and Excel execution, platform/edition behavior and workbook exchange remain untested.