OID reference

timeBaseDayPlanTable

1.3.6.1.4.1.1206.4.2.6.3.3.5

Description

<Definition>A table containing day plan numbers, the times when to implement them and the associated actions. The number of rows in this table shall be equal to the product of the maxDayPlans object and the maxDayPlanEvents object. The dayPlanNumbers within this table shall begin with day plan number 1 and increment b…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.1206.4.2.6.3.3 (timebase, maxFontCharacters)
Node code
5
Node name
timeBaseDayPlanTable
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.1206.4.2.6.3.3.5
URN notation
urn:oid:1.3.6.1.4.1.1206.4.2.6.3.3.5
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 1206 4 2 6 3 3 5}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) global(6) globalTimeManagement(3) timebase(3) timeBaseDayPlanTable(5)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) global(6) globalTimeManagement(3) maxFontCharacters(3) timeBaseDayPlanTable(5)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) global(6) fontDefinition(3) timebase(3) timeBaseDayPlanTable(5)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) global(6) fontDefinition(3) maxFontCharacters(3) timeBaseDayPlanTable(5)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) dms(6) globalTimeManagement(3) timebase(3) timeBaseDayPlanTable(5)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) dms(6) globalTimeManagement(3) maxFontCharacters(3) timeBaseDayPlanTable(5)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) dms(6) fontDefinition(3) timebase(3) timeBaseDayPlanTable(5)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) dms(6) fontDefinition(3) maxFontCharacters(3) timeBaseDayPlanTable(5)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) global(6) globalTimeManagement(3) timebase(3) timeBaseDayPlanTable(5)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) global(6) globalTimeManagement(3) maxFontCharacters(3) timeBaseDayPlanTable(5)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) global(6) fontDefinition(3) timebase(3) timeBaseDayPlanTable(5)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) global(6) fontDefinition(3) maxFontCharacters(3) timeBaseDayPlanTable(5)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) dms(6) globalTimeManagement(3) timebase(3) timeBaseDayPlanTable(5)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) dms(6) globalTimeManagement(3) maxFontCharacters(3) timeBaseDayPlanTable(5)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) dms(6) fontDefinition(3) timebase(3) timeBaseDayPlanTable(5)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) dms(6) fontDefinition(3) maxFontCharacters(3) timeBaseDayPlanTable(5)}
  • Additional combinations skipped.
OID-IRI notation
  • /1/3/6/1/4/1/1206/4/2/6/3/3/5
  • /ISO/Identified-Organization/6/1/4/1/1206/4/2/6/3/3/5
  • /ISO/3/6/1/4/1/1206/4/2/6/3/3/5
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/1206/transportation/devices/global/globalTimeManagement/timebase/timeBaseDayPlanTable
  • /iso/identified-organization/dod/internet/private/enterprise/1206/transportation/devices/global/globalTimeManagement/maxFontCharacters/timeBaseDayPlanTable
  • /iso/identified-organization/dod/internet/private/enterprise/1206/transportation/devices/global/fontDefinition/timebase/timeBaseDayPlanTable
  • /iso/identified-organization/dod/internet/private/enterprise/1206/transportation/devices/global/fontDefinition/maxFontCharacters/timeBaseDayPlanTable
  • /iso/identified-organization/dod/internet/private/enterprise/1206/transportation/devices/dms/globalTimeManagement/timebase/timeBaseDayPlanTable
  • /iso/identified-organization/dod/internet/private/enterprise/1206/transportation/devices/dms/globalTimeManagement/maxFontCharacters/timeBaseDayPlanTable
  • /iso/identified-organization/dod/internet/private/enterprise/1206/transportation/devices/dms/fontDefinition/timebase/timeBaseDayPlanTable
  • /iso/identified-organization/dod/internet/private/enterprise/1206/transportation/devices/dms/fontDefinition/maxFontCharacters/timeBaseDayPlanTable
  • /iso/identified-organization/dod/internet/private/enterprise/nema/transportation/devices/global/globalTimeManagement/timebase/timeBaseDayPlanTable
  • /iso/identified-organization/dod/internet/private/enterprise/nema/transportation/devices/global/globalTimeManagement/maxFontCharacters/timeBaseDayPlanTable
  • /iso/identified-organization/dod/internet/private/enterprise/nema/transportation/devices/global/fontDefinition/timebase/timeBaseDayPlanTable
  • /iso/identified-organization/dod/internet/private/enterprise/nema/transportation/devices/global/fontDefinition/maxFontCharacters/timeBaseDayPlanTable
  • /iso/identified-organization/dod/internet/private/enterprise/nema/transportation/devices/dms/globalTimeManagement/timebase/timeBaseDayPlanTable
  • /iso/identified-organization/dod/internet/private/enterprise/nema/transportation/devices/dms/globalTimeManagement/maxFontCharacters/timeBaseDayPlanTable
  • /iso/identified-organization/dod/internet/private/enterprise/nema/transportation/devices/dms/fontDefinition/timebase/timeBaseDayPlanTable
  • /iso/identified-organization/dod/internet/private/enterprise/nema/transportation/devices/dms/fontDefinition/maxFontCharacters/timeBaseDayPlanTable
  • Additional combinations skipped.

SNMP properties

Value type
SEQUENCE OF TimeBaseDayPlanEntry
Maximum access defined by MIB
not-accessible
Status in MIB
mandatory, deprecated

Definitions may combine these properties differently.

Compare 2 source variants

Variant 1 — ITE public NTCIP working repository MIBs, NTCIP published standard MIB annexes (reviewed modules)

Value type
SEQUENCE OF TimeBaseDayPlanEntry
Maximum access defined by MIB
not-accessible
Status in MIB
mandatory

Variant 2 — NTCIP published standard MIB annexes (reviewed modules), ITE public NTCIP working repository MIBs

Value type
SEQUENCE OF TimeBaseDayPlanEntry
Maximum access defined by MIB
not-accessible
Status in MIB
deprecated

Properties come from available MIB definitions. Actual device support and access can differ. See source records below for original files and qualifications.

Available source records contain 6 distinct definitions; some records may not include a definition.

Show 6 published definitions

timeBaseDayPlanTable · mandatory

timeBaseDayPlanTable OBJECT-TYPE
SYNTAX	SEQUENCE OF TimeBaseDayPlanEntry
ACCESS	not-accessible
STATUS	mandatory
DESCRIPTION
"<Definition>A table containing day plan numbers, the times when to implement them and the associated actions. The number of rows in this table shall be equal to the product of the maxDayPlans object and the maxDayPlanEvents object.  The dayPlanNumbers within this table shall begin with day plan number 1 and increment by one to the maxDayPlans.  The dayPlanEventNumbers within this table shall begin with day plan event number 1 and increment by one to the maxDayPlanEvents.

This table is always used in association with device-type specific objects specifying device-type specific actions such as activating a message on a VMS sign or initiating a pattern for a signal controller.  A device MIB that defines an action table should define the relative priority of the action table as compared to the priority of system and other commands.  The device-type specific action will only be initiated when (1) the specific DayPlan has been activated, (2) the scheduler has sufficient priority to override the current operation of the device, and (3) at the indicated time.  

After a power recovery or after a change to globalTime, the operational mode called for by the scheduler shall be per the last event that would have been called by the currently defined schedule; the logic will search for all events that may have occurred for at least the previous 24 hours.  
<DescriptiveName>DayPlanTable
<DataConceptType>Entity Type
<TableType> static"
::= { timebase 5 }

timeBaseDayPlanTable · mandatory

timeBaseDayPlanTable OBJECT-TYPE
SYNTAX       SEQUENCE OF TimeBaseDayPlanEntry
ACCESS       not-accessible
STATUS       mandatory
DESCRIPTION
       "<Definition>A table containing day plan numbers, the times when
       to implement them and the associated actions. The number of rows
       in this table shall be equal to the product of the maxDayPlans
       object and the maxDayPlanEvents object. The dayPlanNumbers within
       this table shall begin with day plan number 1 and increment by one
       to the maxDayPlans. The dayPlanEventNumbers within this table
       shall begin with day plan event number 1 and increment by one to
       the maxDayPlanEvents.

       This table is always used in association with device-type specific
       objects specifying device-type specific actions such as activating
       a message on a VMS sign or initiating a pattern for a signal
       controller. A device MIB that defines an action table should
       define the relative priority of the action table as compared to
       the priority of system and other commands. The device-type
       specific action will only be initiated when (1) the specific
       DayPlan has been activated, (2) the scheduler has sufficient
       priority to override the current operation of the device, and (3)
       at the indicated time.

       After a power recovery or after a change to globalTime, the
       operational mode called for by the scheduler shall be per the last
       event that would have been called by the currently defined
       schedule; the logic will search for all events that may have
       occurred for at least the previous 24 hours.
       <DescriptiveName>DayPlanTable
       <DataConceptType>Entity Type
       <TableType> static"



                                                                                  

                                                                                    
                                                                                   


::= { timebase 5 }

timeBaseDayPlanTable · mandatory

timeBaseDayPlanTable OBJECT-TYPE
SYNTAX            SEQUENCE OF TimeBaseDayPlanEntry
ACCESS            not-accessible
STATUS            mandatory
DESCRIPTION
"A table containing day plan numbers, the times when to implement them and the associated actions. The
number of rows in this table shall not exceed the value of the maxDayPlans object. This table is always
used in association with device-type specific objects specifying device-type specific actions such as
activating a message on a VMS sign or initiating a pattern for a signal controller. The device-type specific
action will only be initiated when the specific DayPlan has been activated and at the indicated time."
::= { timebase 5 }

timeBaseDayPlanTable · unconfirmed

timeBaseDayPlanTable OBJECT-TYPE
SYNTAX      SEQUENCE OF TimeBaseDayPlanEntry
MAX-ACCESS not-accessible
STATUS      deprecated
DESCRIPTION
   "<Definition>A table containing day plan numbers, the times when to
   implement them and the associated actions. The number of rows in this table
   shall be equal to the product of the maxDayPlans object and the
   maxDayPlanEvents object. The dayPlanNumbers within this table shall begin
   with day plan number 1 and increment by one to the maxDayPlans. The
   dayPlanEventNumbers within this table shall begin with day plan event
   number 1 and increment by one to the maxDayPlanEvents.
  This table is always used in association with device-type specific objects
  specifying device-type specific actions such as activating a message on a
  VMS sign or initiating a pattern for a signal controller. A device MIB that
  defines an action table should define the relative priority of the action
  table as compared to the priority of system and other commands. The device-
  type specific action is only initiated when (1) the specific DayPlan has
  been activated, (2) the scheduler has sufficient priority to override the
  current operation of the device, and (3) at the indicated time.




                                                                                    

                                                                                      
                                                                                     

  After a power recovery, or after a change to any object that affects
  controlerLocalTime, the operational mode called for by the scheduler shall
  be per the last event that would have been called for by the currently
  defined schedule; the logic searches for all events that may have occurred
  for at least the previous 24 hours.
  <Table Type> static
  <Supplanted by> ISO26048-1-DayPlan.fdDayPlanTable & ISO26048-1-
  DayPlan.fdDayPlanTriggerTable (ISO 26048-1)
  <Informative> The replacement tables are designed to trigger an action,
  which can include activating a day plan (as originally envisioned by this
  object) and/or to call other actions (e.g., creating a log entry).
  <Object Identifier> 1.3.6.1.4.1.1206.4.2.6.3.3.5"
::= { timebase 5 }

timeBaseDayPlanTable · mandatory

timeBaseDayPlanTable OBJECT-TYPE
SYNTAX       SEQUENCE OF TimeBaseDayPlanEntry
ACCESS       not-accessible
STATUS       mandatory
DESCRIPTION
       "<Definition>A table containing day plan numbers, the times when
       to implement them and the associated actions. The number of rows
       in this table shall be equal to the product of the maxDayPlans
       object and the maxDayPlanEvents object. The dayPlanNumbers within
       this table shall begin with day plan number 1 and increment by one
       to the maxDayPlans. The dayPlanEventNumbers within this table
       shall begin with day plan event number 1 and increment by one to
       the maxDayPlanEvents.

        This table is always used in association with device-type specific
        objects specifying device-type specific actions such as activating
        a message on a VMS sign or initiating a pattern for a signal



                                                                                     

                                                                                     
                                                                                    

       controller. A device MIB that defines an action table should
       define the relative priority of the action table as compared to
       the priority of system and other commands. The device-type
       specific action is only initiated when (1) the specific DayPlan
       has been activated, (2) the scheduler has sufficient priority to
       override the current operation of the device, and (3) at the
       indicated time.

      After a power recovery, or after a change to any object that
      affects controlerLocalTime, the operational mode called for by the
      scheduler shall be per the last event that would have been called
      for by the currently defined schedule; the logic searches for all
      events that may have occurred for at least the previous 24 hours.
      <TableType> static
      <Object Identifier> 1.3.6.1.4.1.1206.4.2.6.3.3.5"
::= { timebase 5 }

timeBaseDayPlanTable · deprecated

timeBaseDayPlanTable OBJECT-TYPE
SYNTAX	SEQUENCE OF TimeBaseDayPlanEntry
MAX-ACCESS	not-accessible
STATUS	deprecated
DESCRIPTION
"<Definition>A table containing day plan numbers, the times when to implement them and the associated actions. The number of rows in this table shall be equal to the product of the maxDayPlans object and the maxDayPlanEvents object.  The dayPlanNumbers within this table shall begin with day plan number 1 and increment by one to the maxDayPlans.  The dayPlanEventNumbers within this table shall begin with day plan event number 1 and increment by one to the maxDayPlanEvents.

This table is always used in association with device-type specific objects specifying device-type specific actions such as activating a message on a VMS sign or initiating a pattern for a signal controller.  A device MIB that defines an action table should define the relative priority of the action table as compared to the priority of system and other commands.  The device-type specific action is only initiated when (1) the specific DayPlan has been activated, (2) the scheduler has sufficient priority to override the current operation of the device, and (3) at the indicated time.  

After a power recovery, or after a change to any object that affects controlerLocalTime, the operational mode called for by the scheduler shall be per the last event that would have been called for by the currently defined schedule; the logic searches for all events that may have occurred for at least the previous 24 hours.  
<TableType> static
<Superseded by> DAY-PLAN-MIB.fdDayPlanTable & DAY-PLAN-MIB.fdDayPlanTriggerTable (ISO 20684-3)
<Informative> The replacement tables are designed to trigger an action, which can include activating a day plan (as originally envisioned by this object) and/or to call other actions (e.g., creating a log entry).
<Object Identifier> 1.3.6.1.4.1.1206.4.2.6.3.3.5"
::= { timebase 5 }

Meaning

Descriptions

5 unique

Identical descriptions are grouped. Different wording and device-specific notes are retained.

Description 1

<Definition>A table containing day plan numbers, the times when to implement them and the associated actions. The number of rows in this table shall be equal to the product of the maxDayPlans object and the maxDayPlanEvents object. The dayPlanNumbers within this table shall begin with day plan number 1 and increment by one to the maxDayPlans. The dayPlanEventNumbers within this table shall begin with day plan event number 1 and increment by one to the maxDayPlanEvents. This table is always used in association with device-type specific objects specifying device-type specific actions such as activating a message on a VMS sign or initiating a pattern for a signal controller. A device MIB that defines an action table should define the relative priority of the action table as compared to the priority of system and other commands. The device-type specific action will only be initiated when (1) the specific DayPlan has been activated, (2) the scheduler has sufficient priority to override the current operation of the device, and (3) at the indicated time. After a power recovery or after a change to globalTime, the operational mode called for by the scheduler shall be per the last event that would have been called by the currently defined schedule; the logic will search for all events that may have occurred for at least the previous 24 hours. <DescriptiveName>DayPlanTable <DataConceptType>Entity Type <TableType> static

Sources for this description

ITE public NTCIP working repository MIBsNTCIP published standard MIB annexes (reviewed modules)

See 1 matching source record

Description 2

A table containing day plan numbers, the times when to implement them and the associated actions. The number of rows in this table shall not exceed the value of the maxDayPlans object. This table is always used in association with device-type specific objects specifying device-type specific actions such as activating a message on a VMS sign or initiating a pattern for a signal controller. The device-type specific action will only be initiated when the specific DayPlan has been activated and at the indicated time.

Sources for this description

NTCIP published standard MIB annexes (reviewed modules)

See 1 matching source record

Description 3

<Definition>A table containing day plan numbers, the times when to implement them and the associated actions. The number of rows in this table shall be equal to the product of the maxDayPlans object and the maxDayPlanEvents object. The dayPlanNumbers within this table shall begin with day plan number 1 and increment by one to the maxDayPlans. The dayPlanEventNumbers within this table shall begin with day plan event number 1 and increment by one to the maxDayPlanEvents. This table is always used in association with device-type specific objects specifying device-type specific actions such as activating a message on a VMS sign or initiating a pattern for a signal controller. A device MIB that defines an action table should define the relative priority of the action table as compared to the priority of system and other commands. The device- type specific action is only initiated when (1) the specific DayPlan has been activated, (2) the scheduler has sufficient priority to override the current operation of the device, and (3) at the indicated time. After a power recovery, or after a change to any object that affects controlerLocalTime, the operational mode called for by the scheduler shall be per the last event that would have been called for by the currently defined schedule; the logic searches for all events that may have occurred for at least the previous 24 hours. <Table Type> static <Supplanted by> ISO26048-1-DayPlan.fdDayPlanTable & ISO26048-1- DayPlan.fdDayPlanTriggerTable (ISO 26048-1) <Informative> The replacement tables are designed to trigger an action, which can include activating a day plan (as originally envisioned by this object) and/or to call other actions (e.g., creating a log entry). <Object Identifier> 1.3.6.1.4.1.1206.4.2.6.3.3.5

Sources for this description

NTCIP published standard MIB annexes (reviewed modules)

See 1 matching source record

Description 4

<Definition>A table containing day plan numbers, the times when to implement them and the associated actions. The number of rows in this table shall be equal to the product of the maxDayPlans object and the maxDayPlanEvents object. The dayPlanNumbers within this table shall begin with day plan number 1 and increment by one to the maxDayPlans. The dayPlanEventNumbers within this table shall begin with day plan event number 1 and increment by one to the maxDayPlanEvents. This table is always used in association with device-type specific objects specifying device-type specific actions such as activating a message on a VMS sign or initiating a pattern for a signal controller. A device MIB that defines an action table should define the relative priority of the action table as compared to the priority of system and other commands. The device-type specific action is only initiated when (1) the specific DayPlan has been activated, (2) the scheduler has sufficient priority to override the current operation of the device, and (3) at the indicated time. After a power recovery, or after a change to any object that affects controlerLocalTime, the operational mode called for by the scheduler shall be per the last event that would have been called for by the currently defined schedule; the logic searches for all events that may have occurred for at least the previous 24 hours. <TableType> static <Object Identifier> 1.3.6.1.4.1.1206.4.2.6.3.3.5

Sources for this description

NTCIP published standard MIB annexes (reviewed modules)

See 1 matching source record

Description 5

<Definition>A table containing day plan numbers, the times when to implement them and the associated actions. The number of rows in this table shall be equal to the product of the maxDayPlans object and the maxDayPlanEvents object. The dayPlanNumbers within this table shall begin with day plan number 1 and increment by one to the maxDayPlans. The dayPlanEventNumbers within this table shall begin with day plan event number 1 and increment by one to the maxDayPlanEvents. This table is always used in association with device-type specific objects specifying device-type specific actions such as activating a message on a VMS sign or initiating a pattern for a signal controller. A device MIB that defines an action table should define the relative priority of the action table as compared to the priority of system and other commands. The device-type specific action is only initiated when (1) the specific DayPlan has been activated, (2) the scheduler has sufficient priority to override the current operation of the device, and (3) at the indicated time. After a power recovery, or after a change to any object that affects controlerLocalTime, the operational mode called for by the scheduler shall be per the last event that would have been called for by the currently defined schedule; the logic searches for all events that may have occurred for at least the previous 24 hours. <TableType> static <Superseded by> DAY-PLAN-MIB.fdDayPlanTable & DAY-PLAN-MIB.fdDayPlanTriggerTable (ISO 20684-3) <Informative> The replacement tables are designed to trigger an action, which can include activating a day plan (as originally envisioned by this object) and/or to call other actions (e.g., creating a log entry). <Object Identifier> 1.3.6.1.4.1.1206.4.2.6.3.3.5

Sources for this description

ITE public NTCIP working repository MIBs

See 1 matching source record

Evidence

Source records

5 records

Matching descriptions are grouped; open a group to compare definitions and supporting files.

Records for description 1ITE public NTCIP working repository MIBs, NTCIP published standard MIB annexes (reviewed modules)1 record · 2 sources

Description 1

timeBaseDayPlanTable · mandatoryITE public NTCIP working repository MIBs, NTCIP published standard MIB annexes (reviewed modules)2 sources

Status in source: mandatory.

Names: timeBaseDayPlanTable

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "timeBaseDayPlanTable",
    "OBJECT-TYPE",
    "SYNTAX",
    "SEQUENCE",
    "OF",
    "TimeBaseDayPlanEntry",
    "ACCESS",
    "not-accessible",
    "STATUS",
    "mandatory",
    "DESCRIPTION",
    "\"<Definition>A table containing day plan numbers, the times when to implement them and the associated actions. The number of rows in this table shall be equal to the product of the maxDayPlans object and the maxDayPlanEvents object. The dayPlanNumbers within this table shall begin with day plan number 1 and increment by one to the maxDayPlans. The dayPlanEventNumbers within this table shall begin with day plan event number 1 and increment by one to the maxDayPlanEvents. This table is always used in association with device-type specific objects specifying device-type specific actions such as activating a message on a VMS sign or initiating a pattern for a signal controller. A device MIB that defines an action table should define the relative priority of the action table as compared to the priority of system and other commands. The device-type specific action will only be initiated when (1) the specific DayPlan has been activated, (2) the scheduler has sufficient priority to override the current operation of the device, and (3) at the indicated time. After a power recovery or after a change to globalTime, the operational mode called for by the scheduler shall be per the last event that would have been called by the currently defined schedule; the logic will search for all events that may have occurred for at least the previous 24 hours. <DescriptiveName>DayPlanTable <DataConceptType>Entity Type <TableType> static\"",
    "::=",
    "{",
    "timebase",
    "5",
    "}"
  ],
  "syntax_tree": [
    [
      "conceptualTable",
      [
        "row",
        "TimeBaseDayPlanEntry"
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "not-accessible"
    ],
    [
      "Status",
      "mandatory"
    ],
    [
      "DESCRIPTION",
      "<Definition>A table containing day plan numbers, the times when to implement them and the associated actions. The number of rows in this table shall be equal to the product of the maxDayPlans object and the maxDayPlanEvents object. The dayPlanNumbers within this table shall begin with day plan number 1 and increment by one to the maxDayPlans. The dayPlanEventNumbers within this table shall begin with day plan event number 1 and increment by one to the maxDayPlanEvents. This table is always used in association with device-type specific objects specifying device-type specific actions such as activating a message on a VMS sign or initiating a pattern for a signal controller. A device MIB that defines an action table should define the relative priority of the action table as compared to the priority of system and other commands. The device-type specific action will only be initiated when (1) the specific DayPlan has been activated, (2) the scheduler has sufficient priority to override the current operation of the device, and (3) at the indicated time. After a power recovery or after a change to globalTime, the operational mode called for by the scheduler shall be per the last event that would have been called by the currently defined schedule; the logic will search for all events that may have occurred for at least the previous 24 hours. <DescriptiveName>DayPlanTable <DataConceptType>Entity Type <TableType> static"
    ],
    null,
    null,
    null,
    null
  ]
}
Records for description 2NTCIP published standard MIB annexes (reviewed modules)1 record · 1 source

Description 2

timeBaseDayPlanTable · mandatoryNTCIP published standard MIB annexes (reviewed modules)1 source

Status in source: mandatory.

Names: timeBaseDayPlanTable

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "timeBaseDayPlanTable",
    "OBJECT-TYPE",
    "SYNTAX",
    "SEQUENCE",
    "OF",
    "TimeBaseDayPlanEntry",
    "ACCESS",
    "not-accessible",
    "STATUS",
    "mandatory",
    "DESCRIPTION",
    "\"A table containing day plan numbers, the times when to implement them and the associated actions. The number of rows in this table shall not exceed the value of the maxDayPlans object. This table is always used in association with device-type specific objects specifying device-type specific actions such as activating a message on a VMS sign or initiating a pattern for a signal controller. The device-type specific action will only be initiated when the specific DayPlan has been activated and at the indicated time.\"",
    "::=",
    "{",
    "timebase",
    "5",
    "}"
  ],
  "syntax_tree": [
    [
      "conceptualTable",
      [
        "row",
        "TimeBaseDayPlanEntry"
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "not-accessible"
    ],
    [
      "Status",
      "mandatory"
    ],
    [
      "DESCRIPTION",
      "A table containing day plan numbers, the times when to implement them and the associated actions. The number of rows in this table shall not exceed the value of the maxDayPlans object. This table is always used in association with device-type specific objects specifying device-type specific actions such as activating a message on a VMS sign or initiating a pattern for a signal controller. The device-type specific action will only be initiated when the specific DayPlan has been activated and at the indicated time."
    ],
    null,
    null,
    null,
    null
  ]
}
  • NTCIP published standard MIB annexes (reviewed modules) · Publisher's source file: NTCIP 1201:1996, Global Object Definitions Published December 2001 (superceded by NTCIP 1201 v02) — original PDF · Official record

    Module: GLOBAL

    See published definition above

    Source data warning: Recovered from a file whose complete MIB does not parse. The original assignment and definition are preserved. Registration and implementation details may be inaccurate; consult the original file. Other damaged or unresolved declarations are not established registrations.

    Source data warning: This record is transcribed from a published NTCIP MIB annex. The downloadable text is a derived transcription with page furniture and section headings masked; the unmodified original PDF is authoritative. Native definitions, DESCRIPTION and STATUS are retained. A published object definition does not establish support by any particular device.

    Source data warning: A typographic closing DESCRIPTION quotation delimiter occurs immediately at a native SMI field boundary. Normalize this delimiter only in the derived transcription; retain the literal published definition, full description and unchanged numeric assignments.

    Source data warning: A typographic closing quotation mark terminates a DESCRIPTION in this PDF. Normalize that delimiter only in the derived MIB transcription; preserve the literal published definition and unmodified PDF. No numeric assignment changes.

    Source data warning: A typographic opening DESCRIPTION quotation delimiter occurs immediately at a native SMI field boundary. Normalize this delimiter only in the derived transcription; retain the literal published definition, full description and unchanged numeric assignments.

    Source data warning: The GLOBAL moduleMake/moduleVersion assignment closes its explicitly opened brace with a parenthesis. Normalize only that delimiter in the derived parsing copy; retain the original definition and unchanged numeric expression.

    Source data warning: The historical GLOBAL security grouping explicitly prints the parent global and suffix 5 but omits assignment braces. Reuse two adjacent whitespace bytes for those braces in the parsing copy; retain the original expression and qualify this syntactic interpretation. No numeric arc is invented or replaced.

    Source data warning: Unconfirmed historical GLOBAL parent interpretation: the assignment names EventLogConfigTable, while its native table or entry declaration uses eventLogConfigTable. Interpret only this byte-pinned reference using that explicit local declaration. All numeric suffixes and the original published definition remain unchanged; verify the original before implementation.

    Source data warning: Unconfirmed historical GLOBAL parent interpretation: the assignment names EventLogEntry, while its native table or entry declaration uses eventLogEntry. Interpret only this byte-pinned reference using that explicit local declaration. All numeric suffixes and the original published definition remain unchanged; verify the original before implementation.

    Source data warning: Unconfirmed historical GLOBAL parent interpretation: the assignment names globalmoduleTable, while its native table or entry declaration uses globalModuleTable. Interpret only this byte-pinned reference using that explicit local declaration. All numeric suffixes and the original published definition remain unchanged; verify the original before implementation.

    Source data warning: Unconfirmed historical GLOBAL parent interpretation: the assignment names moduleTableEntry, while its native table or entry declaration uses moduleEntry. Interpret only this byte-pinned reference using that explicit local declaration. All numeric suffixes and the original published definition remain unchanged; verify the original before implementation.

    Source data warning: Potentially inaccurate interpretation of historical NTCIP namespace references: missing or unreadable imports of devices, profiles. These exact source files require the reviewed bindings shown below. The numeric roots used here are the explicit assignments in normative Annex A.2 of published NTCIP 8004 v02 (2010), physical pages 43–44. This does not establish that every historical module revision is identical. The annex also prints enterprise instead of RFC 1155 enterprises and declares Protocols while referencing protocols; those spelling interpretations are disclosed. The original IMPORTS, numeric suffixes and definitions remain unchanged. Verify both originals before implementation.

    · Download NTCIP1201v0110b.pdf — GLOBAL (MIB transcription)
Records for description 3NTCIP published standard MIB annexes (reviewed modules)1 record · 1 source

Description 3

timeBaseDayPlanTable · unconfirmedNTCIP published standard MIB annexes (reviewed modules)1 source

Status in source: unconfirmed.

Names: timeBaseDayPlanTable

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "timeBaseDayPlanTable",
    "OBJECT-TYPE",
    "SYNTAX",
    "SEQUENCE",
    "OF",
    "TimeBaseDayPlanEntry",
    "MAX-ACCESS",
    "not-accessible",
    "STATUS",
    "deprecated",
    "DESCRIPTION",
    "\"<Definition>A table containing day plan numbers, the times when to implement them and the associated actions. The number of rows in this table shall be equal to the product of the maxDayPlans object and the maxDayPlanEvents object. The dayPlanNumbers within this table shall begin with day plan number 1 and increment by one to the maxDayPlans. The dayPlanEventNumbers within this table shall begin with day plan event number 1 and increment by one to the maxDayPlanEvents. This table is always used in association with device-type specific objects specifying device-type specific actions such as activating a message on a VMS sign or initiating a pattern for a signal controller. A device MIB that defines an action table should define the relative priority of the action table as compared to the priority of system and other commands. The device- type specific action is only initiated when (1) the specific DayPlan has been activated, (2) the scheduler has sufficient priority to override the current operation of the device, and (3) at the indicated time. After a power recovery, or after a change to any object that affects controlerLocalTime, the operational mode called for by the scheduler shall be per the last event that would have been called for by the currently defined schedule; the logic searches for all events that may have occurred for at least the previous 24 hours. <Table Type> static <Supplanted by> ISO26048-1-DayPlan.fdDayPlanTable & ISO26048-1- DayPlan.fdDayPlanTriggerTable (ISO 26048-1) <Informative> The replacement tables are designed to trigger an action, which can include activating a day plan (as originally envisioned by this object) and/or to call other actions (e.g., creating a log entry). <Object Identifier> 1.3.6.1.4.1.1206.4.2.6.3.3.5\"",
    "::=",
    "{",
    "timebase",
    "5",
    "}"
  ],
  "syntax_tree": [
    [
      "conceptualTable",
      [
        "row",
        "TimeBaseDayPlanEntry"
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "not-accessible"
    ],
    [
      "Status",
      "deprecated"
    ],
    [
      "DESCRIPTION",
      "<Definition>A table containing day plan numbers, the times when to implement them and the associated actions. The number of rows in this table shall be equal to the product of the maxDayPlans object and the maxDayPlanEvents object. The dayPlanNumbers within this table shall begin with day plan number 1 and increment by one to the maxDayPlans. The dayPlanEventNumbers within this table shall begin with day plan event number 1 and increment by one to the maxDayPlanEvents. This table is always used in association with device-type specific objects specifying device-type specific actions such as activating a message on a VMS sign or initiating a pattern for a signal controller. A device MIB that defines an action table should define the relative priority of the action table as compared to the priority of system and other commands. The device- type specific action is only initiated when (1) the specific DayPlan has been activated, (2) the scheduler has sufficient priority to override the current operation of the device, and (3) at the indicated time. After a power recovery, or after a change to any object that affects controlerLocalTime, the operational mode called for by the scheduler shall be per the last event that would have been called for by the currently defined schedule; the logic searches for all events that may have occurred for at least the previous 24 hours. <Table Type> static <Supplanted by> ISO26048-1-DayPlan.fdDayPlanTable & ISO26048-1- DayPlan.fdDayPlanTriggerTable (ISO 26048-1) <Informative> The replacement tables are designed to trigger an action, which can include activating a day plan (as originally envisioned by this object) and/or to call other actions (e.g., creating a log entry). <Object Identifier> 1.3.6.1.4.1.1206.4.2.6.3.3.5"
    ],
    null,
    null,
    null,
    null
  ]
}
Records for description 4NTCIP published standard MIB annexes (reviewed modules)1 record · 1 source

Description 4

timeBaseDayPlanTable · mandatoryNTCIP published standard MIB annexes (reviewed modules)1 source

Status in source: mandatory.

Names: timeBaseDayPlanTable

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "timeBaseDayPlanTable",
    "OBJECT-TYPE",
    "SYNTAX",
    "SEQUENCE",
    "OF",
    "TimeBaseDayPlanEntry",
    "ACCESS",
    "not-accessible",
    "STATUS",
    "mandatory",
    "DESCRIPTION",
    "\"<Definition>A table containing day plan numbers, the times when to implement them and the associated actions. The number of rows in this table shall be equal to the product of the maxDayPlans object and the maxDayPlanEvents object. The dayPlanNumbers within this table shall begin with day plan number 1 and increment by one to the maxDayPlans. The dayPlanEventNumbers within this table shall begin with day plan event number 1 and increment by one to the maxDayPlanEvents. This table is always used in association with device-type specific objects specifying device-type specific actions such as activating a message on a VMS sign or initiating a pattern for a signal controller. A device MIB that defines an action table should define the relative priority of the action table as compared to the priority of system and other commands. The device-type specific action is only initiated when (1) the specific DayPlan has been activated, (2) the scheduler has sufficient priority to override the current operation of the device, and (3) at the indicated time. After a power recovery, or after a change to any object that affects controlerLocalTime, the operational mode called for by the scheduler shall be per the last event that would have been called for by the currently defined schedule; the logic searches for all events that may have occurred for at least the previous 24 hours. <TableType> static <Object Identifier> 1.3.6.1.4.1.1206.4.2.6.3.3.5\"",
    "::=",
    "{",
    "timebase",
    "5",
    "}"
  ],
  "syntax_tree": [
    [
      "conceptualTable",
      [
        "row",
        "TimeBaseDayPlanEntry"
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "not-accessible"
    ],
    [
      "Status",
      "mandatory"
    ],
    [
      "DESCRIPTION",
      "<Definition>A table containing day plan numbers, the times when to implement them and the associated actions. The number of rows in this table shall be equal to the product of the maxDayPlans object and the maxDayPlanEvents object. The dayPlanNumbers within this table shall begin with day plan number 1 and increment by one to the maxDayPlans. The dayPlanEventNumbers within this table shall begin with day plan event number 1 and increment by one to the maxDayPlanEvents. This table is always used in association with device-type specific objects specifying device-type specific actions such as activating a message on a VMS sign or initiating a pattern for a signal controller. A device MIB that defines an action table should define the relative priority of the action table as compared to the priority of system and other commands. The device-type specific action is only initiated when (1) the specific DayPlan has been activated, (2) the scheduler has sufficient priority to override the current operation of the device, and (3) at the indicated time. After a power recovery, or after a change to any object that affects controlerLocalTime, the operational mode called for by the scheduler shall be per the last event that would have been called for by the currently defined schedule; the logic searches for all events that may have occurred for at least the previous 24 hours. <TableType> static <Object Identifier> 1.3.6.1.4.1.1206.4.2.6.3.3.5"
    ],
    null,
    null,
    null,
    null
  ]
}
  • NTCIP published standard MIB annexes (reviewed modules) · Publisher's source file: NTCIP 1201 v03.15 — Global Object (GO) Definitions, published March 2011 — original PDF · Official record

    Module: NTCIP1201-v03

    See published definition above

    Module imports
    {'RFC-1212': ['OBJECT-TYPE'], 'RFC1155-SMI': ['Opaque', 'Counter', 'Gauge', 'null'], 'RFC1213-MIB': ['DisplayString'], 'NTCIP8004v02': ['devices', 'Protocols', 'profiles', 'global']}

    Source data warning: Recovered from a file whose complete MIB does not parse. The original assignment and definition are preserved. Registration and implementation details may be inaccurate; consult the original file. Other damaged or unresolved declarations are not established registrations.

    Source data warning: This record is transcribed from a published NTCIP MIB annex. The downloadable text is a derived transcription with page furniture and section headings masked; the unmodified original PDF is authoritative. Native definitions, DESCRIPTION and STATUS are retained. A published object definition does not establish support by any particular device.

    Source data warning: Potentially inaccurate interpretation of historical NTCIP namespace references: NTCIP8004v02. These exact source files require the reviewed bindings shown below. The numeric roots used here are the explicit assignments in normative Annex A.2 of published NTCIP 8004 v02 (2010), physical pages 43–44. This does not establish that every historical module revision is identical. The annex also prints enterprise instead of RFC 1155 enterprises and declares Protocols while referencing protocols; those spelling interpretations are disclosed. The original IMPORTS, numeric suffixes and definitions remain unchanged. Verify both originals before implementation.

    · Download NTCIP1201v0315r.pdf — NTCIP1201-v03 (MIB transcription)
Records for description 5ITE public NTCIP working repository MIBs1 record · 1 source

Description 5

timeBaseDayPlanTable · deprecatedITE public NTCIP working repository MIBs1 source

Status in source: deprecated.

Names: timeBaseDayPlanTable

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "timeBaseDayPlanTable",
    "OBJECT-TYPE",
    "SYNTAX",
    "SEQUENCE",
    "OF",
    "TimeBaseDayPlanEntry",
    "MAX-ACCESS",
    "not-accessible",
    "STATUS",
    "deprecated",
    "DESCRIPTION",
    "\"<Definition>A table containing day plan numbers, the times when to implement them and the associated actions. The number of rows in this table shall be equal to the product of the maxDayPlans object and the maxDayPlanEvents object. The dayPlanNumbers within this table shall begin with day plan number 1 and increment by one to the maxDayPlans. The dayPlanEventNumbers within this table shall begin with day plan event number 1 and increment by one to the maxDayPlanEvents. This table is always used in association with device-type specific objects specifying device-type specific actions such as activating a message on a VMS sign or initiating a pattern for a signal controller. A device MIB that defines an action table should define the relative priority of the action table as compared to the priority of system and other commands. The device-type specific action is only initiated when (1) the specific DayPlan has been activated, (2) the scheduler has sufficient priority to override the current operation of the device, and (3) at the indicated time. After a power recovery, or after a change to any object that affects controlerLocalTime, the operational mode called for by the scheduler shall be per the last event that would have been called for by the currently defined schedule; the logic searches for all events that may have occurred for at least the previous 24 hours. <TableType> static <Superseded by> DAY-PLAN-MIB.fdDayPlanTable & DAY-PLAN-MIB.fdDayPlanTriggerTable (ISO 20684-3) <Informative> The replacement tables are designed to trigger an action, which can include activating a day plan (as originally envisioned by this object) and/or to call other actions (e.g., creating a log entry). <Object Identifier> 1.3.6.1.4.1.1206.4.2.6.3.3.5\"",
    "::=",
    "{",
    "timebase",
    "5",
    "}"
  ],
  "syntax_tree": [
    [
      "conceptualTable",
      [
        "row",
        "TimeBaseDayPlanEntry"
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "not-accessible"
    ],
    [
      "Status",
      "deprecated"
    ],
    [
      "DESCRIPTION",
      "<Definition>A table containing day plan numbers, the times when to implement them and the associated actions. The number of rows in this table shall be equal to the product of the maxDayPlans object and the maxDayPlanEvents object. The dayPlanNumbers within this table shall begin with day plan number 1 and increment by one to the maxDayPlans. The dayPlanEventNumbers within this table shall begin with day plan event number 1 and increment by one to the maxDayPlanEvents. This table is always used in association with device-type specific objects specifying device-type specific actions such as activating a message on a VMS sign or initiating a pattern for a signal controller. A device MIB that defines an action table should define the relative priority of the action table as compared to the priority of system and other commands. The device-type specific action is only initiated when (1) the specific DayPlan has been activated, (2) the scheduler has sufficient priority to override the current operation of the device, and (3) at the indicated time. After a power recovery, or after a change to any object that affects controlerLocalTime, the operational mode called for by the scheduler shall be per the last event that would have been called for by the currently defined schedule; the logic searches for all events that may have occurred for at least the previous 24 hours. <TableType> static <Superseded by> DAY-PLAN-MIB.fdDayPlanTable & DAY-PLAN-MIB.fdDayPlanTriggerTable (ISO 20684-3) <Informative> The replacement tables are designed to trigger an action, which can include activating a day plan (as originally envisioned by this object) and/or to call other actions (e.g., creating a log entry). <Object Identifier> 1.3.6.1.4.1.1206.4.2.6.3.3.5"
    ],
    null,
    null,
    null,
    null
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.1206)

Schopp Bruce J.

Direct children (1)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.1206.4.2.6.3.3.5.1 timeBaseDayPlanEntry55

Siblings (6)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.1206.4.2.6.3.3.1 maxTimeBaseScheduleEntries00
1.3.6.1.4.1.1206.4.2.6.3.3.2 timeBaseScheduleTable16
1.3.6.1.4.1.1206.4.2.6.3.3.3 maxDayPlans00
1.3.6.1.4.1.1206.4.2.6.3.3.4 maxDayPlanEvents00
1.3.6.1.4.1.1206.4.2.6.3.3.6 dayPlanStatus00
1.3.6.1.4.1.1206.4.2.6.3.3.7 timeBaseScheduleTableStatus00