Skip to main content

system.mes.oee.splitDowntimeEvent

Description

Splits an existing downtime event (an OEE state record) at a specified time. This action modifies the original record, shortening its duration, and creates a new record for the remaining time. This is useful for categorizing a single downtime period with multiple causes.

Permissions

This method requires the OEE.WRITE.SAVE permission.

Syntax

system.mes.oee.splitDowntimeEvent(oeeStateRecordId, splitDate)

Parameters

ParameterTypeNullableDescription
oeeStateRecordIdStringFalseThe ID of the OEE state record to split.
splitDateDateFalseThe date and time at which to split the event.

Returns

Returns a JSON representation of the new OeeStateRecordDTO object that was split off from the original state record.

NameTypeNullableDescriptionDefault Value
idStringTrueThe id of the OEE State Recordnull
codeIntegerFalseInteger state numbernull
locationIdStringFalseIdentifier of the associated location where this state record was recordednull
locationNameStringTrueName of the associated locationnull
locationPathStringTruePath of the location where this state record was recordednull
nameStringFalseName of the recorded statenull
calculationTypeOeeStateCalculationTypeFalseSpecifies how this state contributes to OEE calculationsDOWNTIME
colorStringFalseHex color code representing the state visually"#000000"
statusStatusFalseStatus of the OEE record (e.g., running, faulted, canceled, complete)UNKNOWN
startDateInstantFalseStart date and time of the state recordInstant.now()
endDateInstantTrueEnd date and time of the state recordnull
durationDoubleFalseDuration of the state record in seconds0.0
availabilityReasonIdStringTrueIdentifier of the associated availability reason, if applicablenull
availabilityReasonStringTrueTitle of the availability reason. (Name - Code) For display purposes onlynull
availabilityReasonPathStringTruePath to the current availability reasonnull
interruptionLocationIdStringTrueLocation id that caused the blocked/starved state on the machinenull
interruptionLocationNameStringTrueName of the interruption location that caused the blocked/starved statenull
interruptionLocationPathStringTrueLocation path that caused the blocked/starved state on the machinenull
acknowledgedBooleanFalseBoolean indicating whether the state record has been acknowledgedfalse
acknowledgedByStringTrueAcknowledged By. This is the user who acknowledged the state recordnull
acknowledgedDateInstantTrueAcknowledged Date. This is the date when the state record was acknowledgednull
modeRecordIdStringTrueIdentifier of the associated mode recordnull
rootCauseStateRecordIdStringTrueIdentifier of the root cause state record, if applicablenull
primaryAlarmRecordIdStringTrueIdentifier of the associated OEE Alarm Record, if applicablenull
primaryAlarmNameStringTruePrimary alarm name, if applicablenull
primaryAlarmDisplayPathStringTruePrimary alarm display path, if applicablenull
primaryAlarmLabelStringTruePrimary alarm display name, if applicablenull
notesStringTrueNotes associated with the OEE State Recordnull
enabledbooleanTrueIndicates whether the OEE State Record is enabledtrue
spare1StringTrueExtra field 1null
spare2StringTrueExtra field 2null
spare3StringTrueExtra field 3null

Code Examples

from java.util import Date
import system.date

# The ID of the downtime event to split
stateRecordId = "some-state-record-id"

# The time to split the event
splitDatetime = system.date.parse("2023-10-27 14:30:00", "yyyy-MM-dd HH:mm:ss")

try:
# Split the event
system.mes.oee.splitDowntimeEvent(stateRecordId, splitDatetime)
print "Successfully split downtime event", stateRecordId

# After splitting, you can assign different reasons to the original and new records
# (You would need to query for the new record that was created)

except Exception as e:
print "Error splitting event:", str(e)