Real-Time System Management Information Program Data Exchange Format Specification
3. Functional Requirements
This section defines the Functional Requirements based on the user needs identified in the Concept of Operations (see Section 2). This section includes:
- A tutorial which describes the type of requirements contained in this document and gives some indication of how requirements are written.
- Scope of the Interface – Describes the nature of the interfaces covered by this document.
- The Needs to Requirements Traceability Matrix – A Functional Requirement is a requirement to satisfy a given feature and therefore is only required to be implemented if the associated feature (e.g., user need) is selected through the use of the Needs to Requirements Traceability Matrix (NRTM). The NRTM also indicates which of the items are mandatory, conditional, or optional. The NRTM can be used by procurement personnel to specify the desired features of a connected device or can be used by a manufacturer to document the features supported by their implementation. Due to the size of the NRTM it is contained in a separate Annex A.
- Architectural Requirements – This section defines basic modes of operation.
- Data Exchange Requirements – These are requirements related to the features identified in Section 2.5 that can be realized through a data exchange. For example, this includes the requirement to be able to transmit a vehicle’s position and speed.
- Performance Requirements – These are some basic performance requirements derived from TMDD.
This systems requirements specification (SRS) defines the formal requirements that are intended to satisfy the user needs identified in Section 2.5 of this document. This is achieved through the development of a NRTM that traces each user need to one or more requirements defined in this section. The details of each requirement are then presented following the NRTM. The functional requirements are presented in three broad categories as follows:
- Architectural Requirements – These requirements define the required behavior of the system in exchanging data across the communications interface, including any restrictions to general architectural requirements, based upon the architectural needs identified in this document.
- Data Exchange and Operational Environmental Requirements – These requirements define the required behavior of the system in exchanging data across the communications interface based upon the features identified in this document.
The SRS is a specification for a particular product that performs certain functions in a specific environment. The purpose of this SRS is to document the full set of functions to meet the user needs defined in this DXFS. This SRS will address the functionality needed to meet the user needs of the RTSMIP as defined by this DXFS.
The following criteria are used when documenting and writing requirements:
- Is it a well-formed requirement? Some of the attributes of well-formed requirements are:
- Necessary – Is the requirement an essential part of the system?
- Clear – Can the requirement be interpreted one and only one way?
- Complete – Can the requirement stand on its own without further clarification?
- Consistent – Does the requirement contradict or duplicate another requirement?
- Achievable – Is the requirement technically feasible at a reasonable cost and in a reasonable time?
- Verifiable – Can one unambiguously determine if the requirement has been met?
- Concise – Is the requirement described succinctly and without superfluous text?
- Technology independent – Is the requirement statement technology independent?
- Is the requirement mapped to one or more user needs? This will also address whether the requirement is in fact needed.
- Does the requirement, with its sibling requirements, satisfy the intent and all key items of the need?
The well-formed requirements will generally take the form: [Actor] [Action] [Target] [Constraint] [Localization].
The localization and constraint portions are important, but not all requirements will have both. The constraint identifies how you will measure success or failure of the requirement. The localization identifies the circumstances under which the requirement applies. For example: The System [Actor] shall generate [Action] event reports [Target] containing the following information [Constraint] on a scheduled interval [localization].
The DXFS addresses information that is sent from an owning center to another external center. There are several stakeholders that can represent either owning center or external center, but fundamentally all the information sharing is between these two types of centers. This same situation applies to the Traffic Management Data Dictionary (TMDD) standard as well. This standard is the only ITS center to center standard that contains a set of requirements, and many of these requirements apply to RTSMIP. Where requirements from TMDD Vol 1 satisfy RTSMIP needs defined in this DXFS (e.g., providing link or route travel times), the DXFS does not reproduce the requirement, but contains a reference to the requirement name and paragraph number in the TMDD. Because some but not all of the TMDD requirements are used here, the paragraph numbering of the DXFS (in Section 3) does not match that found in the TMDD standard.
The Needs to Requirements Traceability Matrix (NRTM) discussed in Section 3.3.3 (and contained in Annex A), maps the user needs defined in Section 2.5 to the requirements defined in Section 3.5-3.6 of this document. The table lists each user need to be addressed by the DXFS, followed immediately by the requirement(s) that supports (and traces to) that user need. The table can be used by:
- A user or specification writer to indicate which requirements are to be implemented in a project-specific implementation.
- The interface implementer, as a checklist to reduce the risk of failure to conform to the standard through oversight.
- The supplier and user, as a detailed indication of the capabilities of the implementation.
- The user, as a basis for initially checking the potential interoperability with another implementation.
Annex A – Needs to Requirements Traceability Matrix (NRTM), contained in a separate volume, includes a Needs to Requirements Traceability Matrix (Table A-1) followed by a smaller table (Table A-2) which maps user needs to requirements in Section 3.4 Architecture Requirements.
The following notations and symbols are used to indicate status and conditional status in the NRTM within this standard. Not all of these notations and symbols are necessarily used within this standard.
The following symbols are used to indicate status in the NRTM table (Section 3.3.3):
The O.# (range) notation is used to show a set of selectable options (e.g., O.2 (1..*)) would indicate that one or more of the optio
Table 21. Conformance Symbols.
| Symbol |
Value |
| M |
Mandatory – This requirement(s) is required to support the specified user need. |
| M.# |
Support of every item of the group labeled by the same numeral # is required, but only one is active at a time |
| O |
Optional – This requirement may be included in support of the specified user need |
| O.# (range) |
Part of an option group. Support of the number of items indicated by the ‘(range)’ is required from all options labeled with the same numeral # |
| N/A |
Not-applicable (i.e., logically impossible in the scope of the standard) |
n group 2 options must be implemented.
Much of the NRTM is based upon the NTRM from TMDD Volume 1 (meaning that the conformance indication for requirements equals that given in TMDD). In some cases the entry in the NRTM is different due to the specific user need. For example user need 2.5.2.1 Speed Data for Limited Access Roads will have requirement 3.5.3.3.2.5.2.5 Link Average Speed as M, in this DXFS while in TMDD this requirement is O. Where the conformance requirement differs from TMDD the entry in the NRTM will indicated with a “*”.
3.3.1.2 Conditional Status Notation
The following predicate notation may be used:
Table 22. Predicate Notations.
| Symbol |
Value |
| <predicate>: |
This notation introduces a single item that is conditional on the <predicate>. |
| <predicate>:: |
This notation introduces a table or a group of tables, all of which are conditional on the <predicate>. |
| (predicate) |
This notation introduces the first occurrence of the predicate either in the NRTM or in that specific user need. The feature associated with this notation is the base feature for all options that have this predicate in their conformance column. |
The <predicate>: notation means that the status following it applies only when the NRTM states that the feature or features identified by the predicate are supported. In the simplest case, <predicate> is the identifying tag of a single NRTM item. When the group predicate is true then the associated section shall be completed. The symbol <predicate> also may be a Boolean expression composed of several indices. .AND., .OR., and .NOT. shall be used to indicate the Boolean logical operations.
The predicates used in the NRTM map to the following sections.
Table 23. Predicates.
| Predicate |
Section |
| AreaLocation |
3.5.2.6.4.7.1 |
| Detour |
3.5.2.6.4.6.2 |
| EventComments |
3.5.2.7.4 |
| EventDescription |
3.5.2.6.4.6 |
| EventHazMat |
3.5.2.6.5.1 |
| EventIndicator |
3.5.2.7.2 |
| EventLane |
3.5.2.6.4.9 |
| EventLocation |
3.5.2.6.4.7 |
| EventPeriod |
3.5.2.6.4.1.2.1 |
| EventReferences |
3.5.2.7.3 |
| EventReports |
3.5.2.7.5 |
| EventTime |
3.5.2.6.4.1 |
| HazMatCode |
3.5.2.6.5.1.1 |
| HazMatPlacard |
3.5.2.6.5.1.2 |
| Landmark |
3.5.2.6.4.7.6 |
| LinkLocation |
3.5.2.6.4.7.2 |
| PointOnALink |
3.5.2.6.4.7.4 |
| ProjectReference |
3.5.2.7.1 |
| SiteMetadata |
3.5.4.2.4.3.7 |
| StationMetadata |
3.5.4.2.4.3.8 |
| Subscription |
3.4.2 |
3.3.2 Needs to Requirements Traceability Matrix (NRTM) Table
In addition to the conformance column and the support column, which were discussed in Section 3.3.1, the additional columns in the NRTM table are the User Need ID and User Need columns, FR ID and Functional Requirement columns.
3.3.2.1 User Need ID and User Needs Column
The user needs are defined within the Section 2.5 of this document and the NRTM is based upon the user need within that Section. The section number and user need name are indicated within these columns.
3.3.2.2 FR ID Requirements Type and Requirements Columns
The requirements are defined within Sections 3.4 to 3.6 and the NRTM references the traces from user needs to these requirements. The requirement type, section number and requirements name are indicated within these columns.
3.3.2.3 Using the NRTM to define a system
This document is an informational level specification used to define information exchanges between a center and other centers. In order to use the specification to define a system the developer should first select the user needs that will be addressed by the system. For each user need, the NRTM identifies the set of requirements that relate to that user need. All Mandatory requirements must be selected in order to satisfy the user need. Depending on the deployment some (or all, or none) of the optional requirements will be selected. The requirements identified in the NRTM are mapped in Section 4 of this document to data concepts (dialogs, messages, data frames, or data elements) of other ITS standards (e.g., Traffic Management Data Dictionary). In order to facilitate the selection of the optional requirements, all the requirements under each user need in the NRTM have been organized to indicate what type of data concept will be implemented to satisfy the requirement. This mapping can be categorized as one of four types of data concept:
- Dialog – a requirement to describe the sequence or conditions for information exchanges between a center and other centers.
- Request Message – the requirement used to describe the message sent from an external center to an owner center.
- Response Message – a requirement to describe the message sent from an owner center to an external center.
- Error Message – a requirement to describe the error report message.
Note that many requirements are mapped in Section 4 to data concepts that form a part of a message (e.g., data frames or data elements), but these lower level data concepts are never exchanged by themselves, but always as a part of a message. Hence the characterization of requirements into the four categories shown above. A more detailed discussion of how to use the DXFS to define a system is provided in the DXFS Implementation Guidance Document.
3.4 Architectural Requirements
The requirements to manage the interface connections between centers are as follows:
3.4.1 Connection Management
The requirements to manage the interface connections between centers are as follows:
3.4.1.1 Exchange Center Active Verification
Each center that is part of the C2C network supports the exchange of center active information with the following requirements.
3.4.1.1.1 Send Center Active Verification Upon Request
The requirement for Send Center Active Verification Upon Request is defined by Section 3.3.1.1.1 of the TMDD standard.
3.4.1.1.2 Publish Center Active Verification Information
The requirement for Publish Center Active Verification Information is defined by Section 3.3.1.1.2 of the TMDD standard.
3.4.1.1.3 Subscribe to Center Active Verification Information
The requirement for Subscribe to Center Active Verification Information is defined by Section 3.3.1.1.3 of the TMDD standard.
3.4.1.1.4 Contents of the Center Active Verification Request
The requirement for Contents of the Center Active Verification Request is defined by Section 3.3.1.1.4 of the TMDD standard.
3.4.1.1.5 Required Center Active Verification Request Content
The requirement for Required Center Active Verification Request Content is defined by Section 3.3.1.1.4.1 of the TMDD standard.
3.4.1.1.6 Contents of the Center Active Information
The requirement for Contents of the Center Active Information is defined by Section 3.3.1.1.5 of the TMDD standard.
3.4.1.1.7 Required Center Active Information
The requirement for Required Center Active Information is defined by Section 3.3.1.1.5.1 of the TMDD standard.
3.4.1.1.8 Optional Center Active Information
The following are optional requirements that an owner center may include in the center active information sent to an external center.
3.4.1.1.9 Restrictions – Center Active
The requirement for Restrictions – Center Active is defined by Section 3.3.1.1.5.2.1 of the TMDD standard.
3.4.2 Support Request-Response
The requirement for Support Request-Response is defined by Section 3.3.1.2 of the TMDD standard.
3.4.3 Support Subscription-Publication
The requirements to support subscription-publication of messages between centers are as follows:
3.4.3.1 Support Periodic Updates
The requirement for Support Periodic Updates is defined by Section 3.3.1.3.1 of the TMDD standard.
3.4.3.2 Support Event-Driven Updates
The requirement for Support Event-Driven Updates is defined by Section 3.3.1.3.2 of the TMDD standard.
3.4.4 Support Error Handling Report
The following are requirements for reporting errors encountered during the exchange of information between centers.
3.4.4.1 Contents of the Error Report
The requirement for Contents of the Error Report is defined by Section 3.3.1.4.1 of the TMDD standard.
3.4.4.1.1 Required Error Report Contents
The requirement for Required Error Report Contents is defined by Section 3.3.1.4.1.1 of the TMDD standard.
3.4.4.1.2 Optional Error Report Contents
The following are optional requirements that an owner center may include in the error report information sent to an external center.
3.4.4.1.3 Restrictions – Error Report: The requirement for Restrictions – Error Report is defined by Section 3.3.1.4.1.2.1 of the TMDD standard.
3.5 Functional Requirements
3.5.1 Provide Information on Organizations and Centers
This section covers the relevant requirements for the information regarding organizations that will be sent as part of the real time network, event and device information that addresses the RTSMIP user needs. A more complete set of organizational data that could form part of information exchange between centers in contexts beyond those defined by the DXFS is contained in TMDD Section 3.3.2.
3.5.1.1 Contents of the Organization and Centers Information
The requirement for Contents of the Organization and Centers Information is defined by Section 3.3.2.5 of the TMDD standard.
3.5.1.1.1 Required Organization Information Content
The requirement for Required Organization and Information Content is defined by Section 3.3.2.5.1 of the TMDD standard.
3.5.2 Events Information Sharing
The key needs of RTSMIP described in this DXFS for the sharing of incident information and construction related road or lane closures is addressed by the TMDD requirements for Events Information Sharing. The following set of requirements represents a subset of the complete event information requirements that are relevant to RTSMIP.
3.5.2.1 Send Event Information Upon Request
The requirement for Send Event Information Upon Request is defined by Section 3.3.3.1 of the TMDD standard.
3.5.2.2 Publish Event Information
The requirement for Publish Event Information is defined by Section 3.3.3.2 of the TMDD standard.
3.5.2.3 Subscribe to Event Information
The requirement for Subscribe to Event Information is defined by Section 3.3.3.3 of the TMDD standard.
3.5.2.4 Contents of Event Information Request
The requirement for Contents of Event Information Request is defined by Section 3.3.3.4 of the TMDD standard.
3.5.2.4.1 Required Event Information Request Content
The requirements for Required Event Information Request Content are defined by Section 3.3.3.4.1 of the TMDD standard.
3.5.2.4.2 Optional Event Message Header Information
The following are optional requirements that an external center may include in the event information request sent to an external center.
3.5.2.4.2.1 Authentication – Events
The requirement for Authentication – Events is defined by Section 3.3.3.4.2.1 of the TMDD standard.
3.5.2.4.2.2 Operator Identifier – Events
The requirement for Operator Identifier – Events is defined by Section 3.3.3.4.2.1.1 of the TMDD standard.
3.5.2.4.2.3 Requesting Organization – Events
The requirement for Requesting Organization – Events is defined by Section 3.3.3.4.2.2 of the TMDD standard.
3.5.2.4.3 Event Information Request Filter Content
Centers may be tracking multiple events at any one time, with each event containing lengthy pieces of information. Centers may wish to search for only those events that meet specific criteria, such as a specific type of event, events at a specific location or a recap of current events that had been updated since a specified date and time.
If the owner center supports filtering of event information, the following are optional filtering requirements that an external center may include in the event information request sent to the owner center. Multiple filters may be sent.
3.5.2.4.3.1 Event Unique Identifier Filter
The requirement for Event Unique Identifier Filter is defined by Section 3.3.3.4.3.1 of the TMDD standard.
3.5.2.4.3.2 Event Response Plan Identifier Filter
The requirement for Event Response Plan Identifier Filter is defined by Section 3.3.3.4.3.2 of the TMDD standard.
3.5.2.4.3.3 Event Category Filter
The requirement for Event Category Filter is defined by Section 3.3.3.4.3.3 of the TMDD standard.
3.5.2.4.3.4 Event Priority Filter
The requirement for Event Priority Filter is defined by Section 3.3.3.4.3.4 of the TMDD standard.
3.5.2.4.3.5 Event Description Confidence Level Filter
The requirement for Event Description Confidence Level Filter is defined by Section 3.3.3.4.3.5 of the TMDD standard.
3.5.2.4.3.6 Event Access Level Filter
The requirement for Event Access Level Filter is defined by Section 3.3.3.4.3.6 of the TMDD standard.
3.5.2.4.3.7 Event Action Flag Filter
The requirement for Event Action Flag Filter is defined by Section 3.3.3.4.3.7 of the TMDD standard.
3.5.2.4.3.8 Event Severity Filter
The requirement for Event Severity Filter is defined by Section 3.3.3.4.3.8 of the TMDD standard.
3.5.2.4.3.9 External Center Organization Filter
The requirement for External Center Organization Filter is defined by Section 3.3.3.4.3.9 of the TMDD standard.
3.5.2.4.3.10 Event Location Filter
The requirements for Event Location Filter are defined by Section 3.3.3.4.3.10 of the TMDD standard.
3.5.2.4.3.11 Request Start Time Filter
The requirement for Request Start Time Filter is defined by Section 3.3.3.4.3.11 of the TMDD standard.
3.5.2.4.3.12 Request End Time Filter
The requirement for Request End Time Filter is defined by Section 3.3.3.4.3.12 of the TMDD standard.
3.5.2.4.3.13 Hazardous Material Codes Filter
The requirement for Hazardous Material Codes Filter is defined by Section 3.3.3.4.3.13 of the TMDD standard.
3.5.2.4.3.14 Hazardous Material Placard Codes Filter
The requirement for Hazardous Material Placard Codes Filter is defined by Section 3.3.3.4.3.14 of the TMDD standard.
3.5.2.4.3.15 Event Headline Filter
The requirement for Event Headline Filter is defined by Section 3.3.3.4.3.15 of the TMDD standard.
3.5.2.5 Contents of the Event Information:
The requirement for Contents of the Event Information is defined by Section 3.3.3.5 of the TMDD standard.
3.5.2.6 Required Event Information Content
The requirements for Required Event Information Content are defined by Section 3.3.3.6 of the TMDD standard. The requirements for each aspect of the event information are given below.
3.5.2.6.1 Event Message Header
The following are requirements for the contents of the event message header information sent from an owner center to an external center.
3.5.2.6.2 Required Event Message Header Information
The requirements for Required Event Message Header Information are defined by Section 3.3.3.6.1.1 of the TMDD standard.
3.5.2.6.3 Optional Event Message Header Information
The following are optional requirements that an owner center may include in the event message header information sent to an external center.
3.5.2.6.3.1 External Center Organization – Events
The requirement for External Center Organization – Events is defined by Section 3.3.3.6.1.2.1 of the TMDD standard.
3.5.2.6.3.2 Responding Organization
The requirement for Responding Organization is defined by Section 3.3.3.6.1.2.2 of the TMDD standard.
3.5.2.6.3.3 Message Expiry Time
The requirement for Message Expiry Time is defined by Section 3.3.3.6.1.2.3 of the TMDD standard.
3.5.2.6.4 Event Reference
The following are requirements for the contents of the event reference information sent to an external center.
3.5.2.6.4.1 Required Event Reference Information
The requirement for Required Event Reference Information is defined by Section 3.3.3.6.2.1 of the TMDD standard.
3.5.2.6.4.2 Optional Event Reference Information
The following are optional requirements that an owner center may include in the event reference information sent to an external center.
3.5.2.6.4.3 Event Response Plan Identifier
The requirement for Event Response Plan Identifier is defined by Section 3.3.3.6.2.2.1 of the TMDD standard.
3.5.2.6.4.4 Event Headline
The following are requirements for the contents of the event headline information sent from an owner center to an external center. There may be multiple instances of event headline information.
Note: The event headline information is optional IF and ONLY IF the event information message is used to close an open event.
3.5.2.6.4.5 Required Event Headline Information
The requirement for Required Event Headline Information is defined by Section 3.3.3.6.3.1 of the TMDD standard.
3.5.2.6.4.6 Optional Event Headline Information
The following are optional requirements that an owner center may include in the event headline information sent to an external center.
3.5.2.6.4.6.1 Event Headline Element
The requirement for Event Headline Element is defined by Section 3.3.3.6.3.2.1 of the TMDD standard.
3.5.2.6.5 Event Element Details
The following are requirements for the contents of the event element details information sent to an external center. There may be multiple instances for the event element details information.
Note: The event element details information is optional IF and ONLY IF the event information message is sent to close an open event.
3.5.2.6.5.1 Event Time
The requirement for Event Time is defined by Section 3.3.3.6.4.1 of the TMDD standard.
3.5.2.6.5.1.1 Required Event Time Information
The requirement for Required Event Time Information is defined by Section 3.3.3.6.4.1.1 of the TMDD standard.
3.5.2.6.5.1.2 Optional Event Time Information
The following are optional requirements that an owner center may include in the event time information sent to an external center.
3.5.2.6.5.1.2.1 Event Valid Period
The requirement for Event Valid Period is defined by Section 3.3.3.6.4.1.2.1 of the TMDD standard.
3.5.2.6.5.1.2.1.1 Required Event Effective Period Information
The requirement for Required Event Effective Period Information is defined by Section 3.3.3.6.4.1.2.1.1 of the TMDD standard.
3.5.2.6.5.1.2.1.2 Optional Effective Period Information
If the event valid period is defined by an effective period, then the following are optional requirements that an owner center may include in the event valid period sent to an external center.
3.5.2.6.5.1.2.1.3 Effective Period Qualifier
The requirement for Effective Period Qualifier is defined by Section 3.3.3.6.4.1.2.1.2.1 of the TMDD standard.
3.5.2.6.5.1.2.1.4 Days Event Not In Effect
The requirement for Days Event Not In Effect is defined by Section 3.3.3.6.4.1.2.1.2.2 of the TMDD standard.
3.5.2.6.5.1.2.2 Planned Event Schedule Element Identifier
The requirement for Planned Event Schedule Element Identifier is defined by Section 3.3.3.6.4.1.2.2 of the TMDD standard.
3.5.2.6.5.1.2.3 Sequence Date/Time
The requirement for Sequence Date/Time is defined by Section 3.3.3.6.4.1.2.3 of the TMDD standard.
3.5.2.6.5.1.2.4 Event Start Date/Time
The requirement for Event Start Date/Time is defined by Section 3.3.3.6.4.1.2.4 of the TMDD standard.
3.5.2.6.5.1.2.5 Alternate Start Date/Time
The requirement for Alternate Start Date/Time is defined by Section 3.3.3.6.4.1.2.5 of the TMDD standard.
3.5.2.6.5.1.2.6 Alternate End Date/Time
The requirement for Alternate End Date/Time is defined by Section 3.3.3.6.4.1.2.6 of the TMDD standard.
3.5.2.6.5.1.2.7 Expected Start Date/Time
The requirement for Expected Start Date/Time is defined by Section 3.3.3.6.4.1.2.7 of the TMDD standard.
3.5.2.6.5.1.2.8 Expected End Date/Time
The requirement for Expected End Date/Time is defined by Section 3.3.3.6.4.1.2.8 of the TMDD standard.
3.5.2.6.5.1.2.9 Recurrent Times Event in Effect
The requirement for Recurrent Times Event in Effect is defined by Section 3.3.3.6.4.1.2.9 of the TMDD standard.
3.5.2.6.5.1.2.10 Planned Event Continuous Flag
The requirement for Planned Event Continuous Flag is defined by Section 3.3.3.6.4.1.2.10 of the TMDD standard.
3.5.2.6.5.2 Element Identifier
The requirement for Element Identifier is defined by Section 3.3.3.6.4.2 of the TMDD standard.
3.5.2.6.5.3 Schedule Element Identifier
The requirement for Schedule Element Identifier is defined by Section 3.3.3.6.4.3 of the TMDD standard.
3.5.2.6.5.4 Event Category
The requirement for Event Category is defined by Section 3.3.3.6.4.4 of the TMDD standard.
3.5.2.6.5.5 Event Source
If the owner center supports event source, the elements details information sent from an owner center to an external center may include the event source information as described in the following.
3.5.2.6.5.5.1 Information Source Organization
The requirement for Information Source Organization is defined by Section 3.3.3.6.4.5.1 of the TMDD standard.
3.5.2.6.5.5.2 Event Detection Method
The requirement for Event Detection Method is defined by Section 3.3.3.6.4.5.2 of the TMDD standard.
3.5.2.6.5.6 Event Description
The requirement for Event Description is defined by Section 3.3.3.6.4.6 of the TMDD standard.
Each event may support multiple instances of event description information.
3.5.2.6.5.6.1 Event Quantity
The requirement for Event Quantity is defined by Section 3.3.3.6.4.6.1 of the TMDD standard.
3.5.2.6.5.6.2 Detour
The requirement for Detour is defined by Section 3.3.3.6.4.6.2 of the TMDD standard.
3.5.2.6.5.6.2.1 Required Detour Information
The requirement for Required Detour Information is defined by Section 3.3.3.6.4.6.2.1 of the TMDD standard.
3.5.2.6.5.6.2.2 Optional Detour Information
The following are optional requirements that an owner center may include in the detour information sent to an external center.
3.5.2.6.5.6.2.2.1 Destination
The requirement for Destination is defined by Section 3.3.3.6.4.6.2.2.1 of the TMDD standard.
3.5.2.6.5.6.2.2.2 Location on Alternate Route
The requirement for Location on Alternate Route is defined by Section 3.3.3.6.4.6.2.2 of the TMDD standard.
3.5.2.6.5.6.3 Additional Text Description Information
The following are optional requirements that an owner center may include in the event description information sent to an external center.
3.5.2.6.5.6.3.1 Description Language
The requirement for Description Language is defined by Section 3.3.3.6.4.6.3.1 of the TMDD standard.
3.5.2.6.5.6.3.2 Report Medium
The requirement for Report Medium is defined by Section 3.3.3.6.4.6.3.2 of the TMDD standard.
3.5.2.6.5.7 Event Location
The requirement for Event Location is defined by Section 3.3.3.6.4.7 of the TMDD standard.
3.5.2.6.5.7.1 Area Location Information
If area location is used to describe the event location, then the following are optional requirements that an owner center may include in the event location information sent to an external center.
3.5.2.6.5.7.1.1 Area Identifier
The requirement for Area Identifier is defined by Section 3.3.3.6.4.7.1.1 of the TMDD standard.
3.5.2.6.5.7.1.2 Name of Area
The requirement for Name of Area is defined by Section 3.3.3.6.4.7.1.2 of the TMDD standard.
3.5.2.6.5.7.1.3 Area Location Rank
The requirement for Area Location Rank is defined by Section 3.3.3.6.4.7.1.3 of the TMDD standard.
3.5.2.6.5.7.1.4 Secondary Area Location Reference
The requirement for Secondary Area Location Reference is defined by Section 3.3.3.6.4.7.1.4 of the TMDD standard.
3.5.2.6.5.7.2 Required Link Location Information
The requirement for Required Link Location Information is defined by Section 3.3.3.6.4.7.2 of the TMDD standard.
3.5.2.6.5.7.3 Optional Link Location Information
If link location information is used to describe event location, then the following are optional requirements that an owner center may include in the event location information sent to an external center.
3.5.2.6.5.7.3.1 Link Ownership
The requirement for Link Ownership is defined by Section 3.3.3.6.4.7.3.1 of the TMDD standard.
3.5.2.6.5.7.3.2 Route Designator
The requirement for Route Designator is defined by Section 3.3.3.6.4.7.3.2 of the TMDD standard.
3.5.2.6.5.7.3.3 Second Route Designator
The requirement for Second Route Designator is defined by Section 3.3.3.6.4.7.3.3 of the TMDD standard.
3.5.2.6.5.7.3.4 Link Identifier
The requirement for Link Identifier is defined by Section 3.3.3.6.4.7.3.4 of the TMDD standard.
3.5.2.6.5.7.3.5 Link Name – Events
The requirement for Link Name – Events is defined by Section 3.3.3.6.4.7.3.5 of the TMDD standard.
3.5.2.6.5.7.3.6 Secondary Point
The requirement for Secondary Point is defined by Section 3.3.3.6.4.7.3.6 of the TMDD standard.
3.5.2.6.5.7.3.7 Link Direction
The requirement for Link Direction is defined by Section 3.3.3.6.4.7.3.7 of the TMDD standard.
3.5.2.6.5.7.3.8 Link Alignment
The requirement for Link Alignment is defined by Section 3.3.3.6.4.7.3.8 of the TMDD standard.
3.5.2.6.5.7.3.9 Linear Reference – Events
The requirement for Linear Reference – Events is defined by Section 3.3.3.6.4.7.3.9 of the TMDD standard.
3.5.2.6.5.7.3.10 Alternate Link Location
The requirement for Alternate Link Location is defined by Section 3.3.3.6.4.7.3.10 of the TMDD standard.
3.5.2.6.5.7.4 Required Point on a Link Location Information
The requirement for Required Point on a Link Location Information is defined by Section 3.3.3.6.4.7.4 of the TMDD standard.
3.5.2.6.5.7.5 Optional Point on a Link Location Information
If point on a link location information is used to describe event location, then the following are optional requirements that an owner center may include in the event location sent to an external center.
3.5.2.6.5.7.5.1 Linear Reference Location
The requirement for Linear Reference Location is defined by Section 3.3.3.6.4.7.5.1 of the TMDD standard.
3.5.2.6.5.7.5.2 Link Name – Event Point
The requirement for Link Name – Event Point is defined by Section 3.3.3.6.4.7.5.2 of the TMDD standard.
3.5.2.6.5.7.5.3 Point Name
The requirement for Point Name is defined by Section 3.3.3.6.4.7.5.3 of the TMDD standard.
3.5.2.6.5.7.5.4 Cross Street Identifier
The requirement for Cross Street Identifier is defined by Section 3.3.3.6.4.7.5.4 of the TMDD standard.
3.5.2.6.5.7.5.5 Cross Street Name
The requirement for Cross Street Name is defined by Section 3.3.3.6.4.7.5.5 of the TMDD standard.
3.5.2.6.5.7.5.6 Signed Destination
The requirement for Signed Destination is defined by Section 3.3.3.6.4.7.5.6 of the TMDD standard.
3.5.2.6.5.7.5.7 Point Location Rank
The requirement for Point Location Rank is defined by Section 3.3.3.6.4.7.5.7 of the TMDD standard.
3.5.2.6.5.7.5.8 Landmark Type
The requirement for Landmark Type is defined by Section 3.3.3.6.4.7.5.8 of the TMDD standard.
3.5.2.6.5.7.5.9 Secondary Link Location
The requirement for Secondary Link Location is defined by Section 3.3.3.6.4.7.5.9 of the TMDD standard.
3.5.2.6.5.7.6 Required Landmark Location Information
The requirement for Required Landmark Location Information is defined by Section 3.3.3.6.4.7.6 of the TMDD standard.
3.5.2.6.5.7.7 Optional Landmark Location Information
If landmark location is used to describe the event location, then the following are optional requirements that an owner center may include in the event location information sent to an external center.
3.5.2.6.5.7.7.1 Landmark Point Name
The requirement for Landmark Point Name is defined by Section 3.3.3.6.4.7.7.1 of the TMDD standard.
3.5.2.6.5.7.7.2 Landmark Location Rank
The requirement for Landmark Location Rank is defined by Section 3.3.3.6.4.7.7.2 of the TMDD standard.
3.5.2.6.5.7.7.3 Landmark Location
The requirement for Landmark Location is defined by Section 3.3.3.6.4.7.7.3 of the TMDD standard.
3.5.2.6.5.7.7.4 Secondary Landmark Location
The requirement for Secondary Landmark Location is defined by Section 3.3.3.6.4.7.7.4 of the TMDD standard.
3.5.2.6.5.7.8 Geographic Location
The requirement for Geographic Location is defined by Section 3.3.3.6.4.7.8 of the TMDD standard.
3.5.2.6.5.8 Event Name
The requirement for Event Name is defined by Section 3.3.3.6.4.8 of the TMDD standard.
3.5.2.6.5.9 Event Lane
The requirement for Event Lane is defined by Section 3.3.3.6.4.9 of the TMDD standard.
3.5.2.6.5.9.1 Optional Event Lane Information
The following are optional requirements that an owner center may include in the event lane information sent to an external center.
3.5.2.6.5.9.1.1 Lane Type
The requirement for Lane Type is defined by Section 3.3.3.6.4.9.1.1 of the TMDD standard.
3.5.2.6.5.9.1.2 Direction of Travel
The requirement for Direction of Travel is defined by Section 3.3.3.6.4.9.1.2 of the TMDD standard.
3.5.2.6.5.9.1.3 Total Number of Lanes
The requirement for Total Number of Lanes is defined by Section 3.3.3.6.4.9.1.3 of the TMDD standard.
3.5.2.6.5.9.1.4 Number of Lanes Affected
The requirement for Number of Lanes Affected is defined by Section 3.3.3.6.4.9.1.4 of the TMDD standard.
3.5.2.6.5.9.1.5 Lane Number Affected
The requirement for Lane Number Affected is defined by Section 3.3.3.6.4.9.1.5 of the TMDD standard.
3.5.2.6.5.9.1.6 Lane Status
The requirement for Lane Status is defined by Section 3.3.3.6.4.9.1.6 of the TMDD standard.
3.5.2.6.5.10 Event Description Confidence Level
The requirement for Event Description Confidence Level is defined by Section 3.3.3.6.4.11 of the TMDD standard.
3.5.2.6.6 Event Access Level
The requirement for Event Access Level is defined by Section 3.3.3.6.4.12 of the TMDD standard.
3.5.2.6.6.1 Event Hazardous Material Code
The requirement for Event Hazardous Material Code is defined by Section 3.3.3.6.4.13 of the TMDD standard.
The following are optional requirements that an owner center may include in the event hazardous materials information sent to an external center.
3.5.2.6.6.1.1 Event HazMat Code
The requirement for Event HazMat Code is defined by Section 3.3.3.6.4.13.1 of the TMDD standard.
3.5.2.6.6.1.2 Event HazMat Placard Code
The requirement for Event HazMat Placard Code is defined by Section 3.3.3.6.4.13.2 of the TMDD standard.
3.5.2.6.6.1.3 Placard Code Displayed Correctly on Vehicle
The requirement for Placard Code Displayed Correctly on Vehicle is defined by Section 3.3.3.6.4.13.3 of the TMDD standard.
3.5.2.7 Optional Event Information Content
The following are optional requirements that an owner center may include in the full event update information sent to an external center.
3.5.2.7.1 Restrictions – Events
The requirement for Restrictions – Events is defined by Section 3.3.3.7.1 of the TMDD standard.
3.5.2.7.2 Project Reference
The requirement for Project Reference is defined by Section 3.3.3.7.2 of the TMDD standard.
3.5.2.7.2.1 Project Reference Information
The requirement for Project Reference Information is defined by Section 3.3.3.7.2.1 of the TMDD standard.
3.5.2.7.2.2 Permit Reference Information
The requirement for Permit Reference Information is defined by Section 3.3.3.7.2.2 of the TMDD standard.
3.5.2.7.2.3 Owner Organization – Project Reference
The requirement for Owner Organization – Project Reference is defined by Section 3.3.3.7.2.3 of the TMDD standard.
3.5.2.7.2.4 Project Description
The requirement for Project Description is defined by Section 3.3.3.7.2.4 of the TMDD standard.
3.5.2.7.3 Event Indicator
The requirement for Event Indicator is defined by Section 3.3.3.7.3 of the TMDD standard. Multiple instances of event indicator information may be sent. Each instance of event indicator information consists of one of the following:
3.5.2.7.3.1 Event Status
The requirement for Event Status is defined by Section 3.3.3.7.3.1 of the TMDD standard.
3.5.2.7.3.2 Event Duration Exceeded Flag
The requirement for Event Duration Exceeded Flag is defined by Section 3.3.3.7.3.2 of the TMDD standard.
3.5.2.7.3.3 Event Priority Level
The requirement for Event Priority Level is defined by Section 3.3.3.7.3.3 of the TMDD standard.
3.5.2.7.3.4 Event Severity
The requirement for Event Severity is defined by Section 3.3.3.7.3.4 of the TMDD standard.
3.5.2.7.3.5 Event Impact Level
The requirement for Event Impact Level is defined by Section 3.3.3.7.3.5 of the TMDD standard.
3.5.2.7.3.6 Event Active Flag
The requirement for Event Active Flag is defined by Section 3.3.3.7.3.6 of the TMDD standard.
3.5.2.7.3.7 Event Class
The requirement for Event Class is defined by Section 3.3.3.7.3.7 of the TMDD standard.
3.5.2.7.4 Other References
Center can associate one event with another event, regardless if the other event was originated by the owner center or by an external center. Two separate centers may enter the same event into their own systems (each event having a unique event identifier), or a single event, such as a crash, may cause a secondary accident nearby. In these situations, it is helpful to associate one event with another event to obtain a complete picture of a situation. The requirement for Other References is defined by Section 3.3.3.7.4 of the TMDD standard. Multiple instances of other reference information may be sent. Each instance of other reference information consists of one of the following:
3.5.2.7.4.1 Trip Reference
The requirement for Event Active Flag is defined by Section 3.3.3.7.4.1 of the TMDD standard.
3.5.2.7.4.2 Responsible Reference
The requirement for Responsible Reference is defined by Section 3.3.3.7.4.2 of the TMDD standard.
3.5.2.7.4.3 Related Event
The requirement for Related Event is defined by Section 3.3.3.7.4.3 of the TMDD standard.
3.5.2.7.4.4 Previous Event
The requirement for Previous Event is defined by Section 3.3.3.7.4.4 of the TMDD standard.
3.5.2.7.4.5 Split Event
The requirement for Split Event is defined by Section 3.3.3.7.4.5 of the TMDD standard.
3.5.2.7.4.6 Merged Event
The requirement for Merged Event is defined by Section 3.3.3.7.4.6 of the TMDD standard.
3.5.2.7.4.7 Sibling Event
The requirement for Sibling Event is defined by Section 3.3.3.7.4.7 of the TMDD standard.
3.5.2.7.4.8 Associated Device
The requirement for Associated Device is defined by Section 3.3.3.7.4.8 of the TMDD standard.
3.5.2.7.4.9 Associated URL
The requirement for Associated URL is defined by Section 3.3.3.7.4.9 of the TMDD standard.
3.5.2.7.5 Event Comments
The requirement for Event Comments is defined by Section 3.3.3.7.5 of the TMDD standard.
3.5.2.7.5.1 Required Event Comments
The requirement for Required Event Comments is defined by Section 3.3.3.7.5.1 of the TMDD standard.
3.5.2.7.5.2 Optional Event Comments
The following are optional requirements that an owner center may include in the event comments information sent to an external center.
3.5.2.7.5.2.1 Operator Identifier – Event Comments
The requirement for Operator Identifier – Event Comments is defined by Section 3.3.3.7.5.2.1 of the TMDD standard.
3.5.2.7.5.2.2 Operator Comments
The requirement for Operator Comments is defined by Section 3.3.3.7.5.2.2 of the TMDD standard.
3.5.2.7.5.2.3 Comment Description Language
The requirement for Comment Description Language is defined by Section 3.3.3.7.5.2.3 of the TMDD standard.
3.5.2.7.6 Event Reports
The requirement for Event Reports is defined by Section 3.3.3.7.6 of the TMDD standard.
3.5.2.7.6.1 Required Event Reports
The requirement for Required Event Reports is defined by Section 3.3.3.7.6.1 of the TMDD standard.
3.5.2.7.6.2 Optional Event Reports
The following are optional requirements that an owner center may include in the event reports information sent to an external center.
3.5.2.7.6.2.1 Report Description Language
The requirement for Report Description Language is defined by Section 3.3.3.7.6.2.1 of the TMDD standard.
3.5.2.8 Action Logs
The action logs are used to exchange information that accompanies a basic or full event message. The action logs act as a timeline for the event where each action log element represents a change to an event, or a free text description that describes an operator or device function that is associated with an event.
The requirements for exchanging action logs information between centers are as follows:
3.5.2.8.1 Send Action Logs Upon Request
The requirement for Send Action Logs Upon Request is defined by Section 3.3.3.8.1 of the TMDD standard.
3.5.2.8.2 Publish Action Log Information
The requirement for Publish Action Log Information is defined by Section 3.3.3.8.2 of the TMDD standard.
3.5.2.8.3 Subscribe to Action Log Information
The requirement for Subscribe to Action Log Information is defined by Section 3.3.3.8.3 of the TMDD standard.
3.5.2.8.4 Contents of Action Log Information
The requirement for Contents of Action Log Information is defined by Section 3.3.3.8.4 of the TMDD standard.
3.5.2.8.4.1 Required Action Log Information Content
The requirement for Required Action Log Information Content is defined by Section 3.3.3.8.4.1 of the TMDD standard.
3.5.2.8.4.2 Optional Action Log Information Content
The following are optional requirements that an owner center may include in the action log information sent to an external center.
3.5.2.8.4.2.1 Restrictions – Action Logs
The requirement for Restrictions – Action Log is defined by Section 3.3.3.8.4.2.1 of the TMDD standard.
3.5.2.9 Event Index
The event index message is used to determine a list of events that an owner center is currently tracking.
The requirements for exchanging event index information between centers are as follows:
3.5.2.9.1 Send Event Index Information Upon Request
The requirement for Send Event Index Information Upon Request is defined by Section 3.3.3.9.1 of the TMDD standard.
3.5.2.9.2 Publish Event Index Information
The requirement for Publish Event Index Information is defined by Section 3.3.3.9.2 of the TMDD standard.
3.5.2.9.3 Subscribe to Event Index Information
The requirement for Subscribe to Event Index Information is defined by Section 3.3.3.9.3 of the TMDD standard.
3.5.2.9.4 Contents of Event Index Request
The requirement for Contents of Event Index Request is defined by Section 3.3.3.9.4 of the TMDD standard.
3.5.2.9.4.1 Required Event Index Request Content
The requirement for Required Event Index Request Content is defined by Section 3.3.3.9.4.1 of the TMDD standard.
3.5.2.9.4.2 Optional Event Index Request Information
The following are optional requirements that an external center may include in the event index request sent to an external center.
3.5.2.9.4.2.1 Authentication – Event Index
The requirement for Authentication – Event Index is defined by Section 3.3.3.9.4.2.1 of the TMDD standard.
3.5.2.9.4.2.2 Operator Identifier – Event Index
The requirement for Operator Identifier – Event Index is defined by Section 3.3.3.9.4.2.1.1 of the TMDD standard.
3.5.2.9.4.2.3 Requesting Organization – Event Index
The requirement for Requesting Organization – Event Index is defined by Section 3.3.3.9.4.2.2 of the TMDD standard.
3.5.2.9.5 Contents of the Event Index Information
The requirement for Contents of the Event Index Information is defined by Section 3.3.3.9.5 of the TMDD standard.
3.5.2.9.5.1 Required Event Index Information Content
The requirement for Required Event Index Information Content is defined by Section 3.3.3.9.5.1 of the TMDD standard.
3.5.2.9.5.2 Optional Event Index Information Content
The following are optional requirements that an owner center may include in the event index information sent to an external center.
3.5.2.9.5.3 Event URL File Update Date and Time Information
The requirement for Event URL File Update Date and Time Information is defined by Section 3.3.3.9.5.2.1 of the TMDD standard.
3.5.2.9.5.4 Event URL Reference Medium
The requirement for Event URL Reference Medium is defined by Section 3.3.3.9.5.2.2 of the TMDD standard
3.5.3 Share Roadway Network Data
This section of requirements covers the sharing of link speed and travel time to support data sharing user needs. In order to share speed and travel time, centers need to have GIS-based traffic network inventory and location attributes including linear reference and geographic coordinates to support the location of devices and the location of events between operational centers. This includes requirements for the sharing of traffic data and traffic detector based link status, which can be attributed to the underlying link and route-based traffic network.
The requirements to exchange traffic network inventory and status information between centers, which are derived from the TMDD standard are as follows:
3.5.3.1 Share Traffic Network Information
The requirements to exchange traffic network information between centers are as follows:
3.5.3.1.1 Contents of the Traffic Network Information Request
The requirement for Contents of the Traffic Network Information Request is defined by Section 3.3.4.1.1 of the TMDD standard.
3.5.3.1.1.1 Required Traffic Network Information Request Content
The requirement for Required Traffic Network Information Request Content is defined by Section 3.3.4.1.1.1 of the TMDD standard.
3.5.3.1.1.2 Optional Traffic Network Information Request Content
If the owner center supports it, the following are optional requirements that an external center may include in the traffic network information request sent to an owner center.
3.5.3.1.1.2.1 Authentication – Network
The requirement for Authentication – Network is defined by Section 3.3.4.1.1.2.1 of the TMDD standard.
3.5.3.1.1.2.1.1 Operator Identifier – Network
The requirement for Operator Identifier – Network is defined by Section 3.3.4.1.1.2.1.1 of the TMDD standard.
3.5.3.1.1.2.2 Roadway Network Identifier
The requirement for Roadway Network Identifier is defined by Section 3.3.4.1.1.2.2 of the TMDD standard.
3.5.3.1.1.2.3 Traffic Network Identifier
The requirement for Traffic Network Identifier is defined by Section 3.3.4.1.1.2.3 of the TMDD standard.
3.5.3.2 Share Node Information
The requirements to exchange node information between centers are as follows:
3.5.3.2.1 Share Node Inventory Information
The requirements to exchange node inventory information between centers are as follows:
3.5.3.2.1.1 Send Node Inventory Information Upon Request
The requirement for Send Node Inventory Information Upon Request is defined by Section 3.3.4.2.1.1 of the TMDD standard.
3.5.3.2.1.2 Publish Node Inventory Information
The requirement for Publish Node Inventory Information is defined by Section 3.3.4.2.1.2 of the TMDD standard.
3.5.3.2.1.3 Subscribe to Node Inventory Information
The requirement for Subscribe to Node Inventory Information is defined by Section 3.3.4.2.1.3 of the TMDD standard.
3.5.3.2.1.4 Contents of the Node Inventory Request
The requirement for Contents of the Node Inventory Request is defined by Section 3.3.4.2.1.4 of the TMDD standard.
3.5.3.2.1.5 Contents of the Node Inventory Information
The requirement for Contents of the Node Inventory Information is defined by Section 3.3.4.2.1.5 of the TMDD standard.
3.5.3.2.1.5.1 Required Node Inventory Information Content
The requirement for Required Node Inventory Information Content is defined by Section 3.3.4.2.1.5.1 of the TMDD standard.
3.5.3.2.1.5.2 Optional Node Inventory Information Content
The following are optional requirements that an owner center may include in the node inventory information sent to an external center.
3.5.3.2.1.5.2.1 Restrictions – Node Inventory
The requirement for Restrictions – Node Inventory is defined by Section 3.3.4.2.1.5.2.1 of the TMDD standard.
3.5.3.2.1.5.2.2 Roadway Network Name – Node Inventory
The requirement for Roadway Network Name – Node Inventory is defined by Section 3.3.4.2.1.5.2.2 of the TMDD standard.
3.5.3.2.1.5.2.3 Node Name – Node Inventory
The requirement for Node Name – Node Inventory is defined by Section 3.3.4.2.1.5.2.3 of the TMDD standard.
3.5.3.2.1.5.2.4 Node Description
The requirement for Node Description is defined by Section 3.3.4.2.1.5.2.4 of the TMDD standard.
3.5.3.2.1.5.2.5 Route Designator – Node Inventory
The requirement for Route Designator – Node Inventory is defined by Section 3.3.4.2.1.5.2.5 of the TMDD standard.
3.5.3.2.1.5.2.6 Node Direction
The requirement for Node Direction is defined by Section 3.3.4.2.1.5.2.6 of the TMDD standard.
3.5.3.2.1.5.2.7 Linear Reference – Node Inventory
The requirement for Linear Reference – Node Inventory is defined by Section 3.3.4.2.1.5.2.7 of the TMDD standard.
3.5.3.2.1.5.2.8 Node Type
The requirement for Node Type is defined by Section 3.3.4.2.1.5.2.8 of the TMDD standard.
3.5.3.2.1.5.2.9 Number of Links
The requirement for Number of Links is defined by Section 3.3.4.2.1.5.2.9 of the TMDD standard.
3.5.3.2.1.5.2.10 Node Inventory Date and Time Change Information
The requirement for Node Inventory Date and Time Change Information is defined by Section 3.3.4.2.1.5.2.10 of the TMDD standard.
3.5.3.3 Share Link Information
The requirements to exchange link information between centers are as follows:
3.5.3.3.1 Share Link Inventory Information
The requirements to exchange link inventory information between centers are as follows:
3.5.3.3.1.1 Send Link Inventory Information Upon Request
The requirement for Send Link Inventory Information Upon Request is defined by Section 3.3.4.3.1.1 of the TMDD standard.
3.5.3.3.1.2 Publish Link Inventory Information
The requirement for Publish Link Inventory Information is defined by Section 3.3.4.3.1.2 of the TMDD standard.
3.5.3.3.1.3 Subscribe to Link Inventory Information
The requirement for Subscribe to Link Inventory Information is defined by Section 3.3.4.3.1.3 of the TMDD standard.
3.5.3.3.1.4 Contents of the Link Inventory Request
The requirement for Contents of the Link Inventory Request is defined by Section 3.3.4.3.1.4 of the TMDD standard.
3.5.3.3.1.5 Contents of the Link Inventory Information
The requirement for Contents of the Link Inventory Request is defined by Section 3.3.4.3.1.5 of the TMDD standard.
3.5.3.3.1.5.1 Required Link Inventory Information Content
The requirement for Required Link Inventory Information Content is defined by Section 3.3.4.3.1.5.1 of the TMDD standard.
3.5.3.3.1.5.2 Optional Link Inventory Information Content
The following are optional requirements that an owner center may include in the link inventory information sent to an external center.
3.5.3.3.1.5.2.1 Restrictions – Link Inventory
The requirement for Restrictions – Link Inventory is defined by Section 3.3.4.3.1.5.2.1 of the TMDD standard.
3.5.3.3.1.5.2.2 Roadway Network Name – Link Inventory
The requirement for Roadway Network Name – Link Inventory is defined by Section 3.3.4.3.1.5.2.2 of the TMDD standard.
3.5.3.3.1.5.2.3 Link Name – Link Inventory
The requirement for Link Name – Link Inventory is defined by Section 3.3.4.3.1.5.2.3 of the TMDD standard.
3.5.3.3.1.5.2.4 Alternate Names – Link Inventory
The requirement for Roadway Network Name – Link Inventory is defined by Section 3.3.4.3.1.5.2.4 of the TMDD standard.
3.5.3.3.1.5.2.5 Route Designator – Link Inventory
The requirement for Route Designator – Link Inventory is defined by Section 3.3.4.3.1.5.2.5 of the TMDD standard.
3.5.3.3.1.5.2.6 Secondary Route Designator
The requirement for Secondary Route Designator is defined by Section 3.3.4.3.1.5.2.6 of the TMDD standard.
3.5.3.3.1.5.2.7 Linear Reference – Link Inventory
The requirement for Linear Reference – Link Inventory is defined by Section 3.3.4.3.1.5.2.7 of the TMDD standard.
3.5.3.3.1.5.2.8 Link Length
The requirement for Link Length is defined by Section 3.3.4.3.1.5.2.8 of the TMDD standard.
3.5.3.3.1.5.2.9 Link Capacity
The requirement for Link Capacity is defined by Section 3.3.4.3.1.5.2.9 of the TMDD standard.
3.5.3.3.1.5.2.10 Link Speed Limit – Link Inventory
The requirement for Link Speed Limit – Link Inventory is defined by Section 3.3.4.3.1.5.2.10 of the TMDD standard.
3.5.3.3.1.5.2.11 Link Truck Speed Limit – Link Inventory
The requirement for Link Truck Speed Limit –Link Inventory is defined by Section 3.3.4.3.1.5.2.11 of the TMDD standard.
3.5.3.3.1.5.2.12 Speed Limit Units – Link Inventory
The requirement for Speed Limit Units – Link Inventory is defined by Section 3.3.4.3.1.5.2.12 of the TMDD standard.
3.5.3.3.1.5.2.13 Link Law Enforcement Jurisdiction
The requirement for Link Law Enforcement Jurisdiction is defined by Section 3.3.4.3.1.5.2.13 of the TMDD standard.
3.5.3.3.1.5.2.14 Designated Owner
The requirement for Designated Owner is defined by Section 3.3.4.3.1.5.2.14 of the TMDD standard.
3.5.3.3.1.5.2.15 Left Shoulder Width
The requirement for Left Shoulder Width is defined by Section 3.3.4.3.1.5.2.15 of the TMDD standard.
3.5.3.3.1.5.2.16 Right Shoulder Width
The requirement for Right Shoulder Width is defined by Section 3.3.4.3.1.5.2.16 of the TMDD standard.
3.5.3.3.1.5.2.17 Median Type
The requirement for Median Type is defined by Section 3.3.4.3.1.5.2.17 of the TMDD standard.
3.5.3.3.1.5.2.18 Link Inventory Date and Time Change Information
The requirement for Link Inventory Date and Time Change Information is defined by Section 3.3.4.3.1.5.2.18 of the TMDD standard.
3.5.3.3.2 Share Link Status Information
The requirements to exchange link status information between centers are as follows:
3.5.3.3.2.1 Send Link Status Information Upon Request
The requirement for Send Link Status Information Upon Request is defined by Section 3.3.4.3.2.1 of the TMDD standard.
3.5.3.3.2.2 Publish Link Status Information
The requirement for Publish Link Status Information is defined by Section 3.3.4.3.2.2 of the TMDD standard.
3.5.3.3.2.3 Subscribe to Link Status Information
The requirement for Subscribe to Link Status Information is defined by Section 3.3.4.3.2.3 of the TMDD standard.
3.5.3.3.2.4 Contents of the Link Status Request]
The requirement for Contents of the Link Status Request is defined by Section 3.3.4.3.2.4 of the TMDD standard.
3.5.3.3.2.5 Contents of the Link Status Information
The requirement for Contents of the Link Status Information is defined by Section 3.3.4.3.2.5 of the TMDD standard.
3.5.3.3.2.5.1 Required Link Status Information Content
The requirement for Required Link Status Information Content is defined by Section 3.3.4.3.2.5.1 of the TMDD standard.
3.5.3.3.2.5.2 Optional Link Status Information Content
The following are optional requirements that an owner center may include in the link status information sent to an external center.
3.5.3.3.2.5.2.1 Restrictions – Link Status
The requirement for Restrictions – Link Status is defined by Section 3.3.4.3.2.5.2.1 of the TMDD standard.
3.5.3.3.2.5.2.2 Link Name – Link Status
The requirement for Link Name – Link Status is defined by Section 3.3.4.3.2.5.2.2 of the TMDD standard.
3.5.3.3.2.5.2.3 Link Direction – Link Status
The requirement for Link Direction – Link Status is defined by Section 3.3.4.3.2.5.2.3 of the TMDD standard.
3.5.3.3.2.5.2.4 Link Travel Time
The requirement for Link Travel Time is defined by Section 3.3.4.3.2.5.2.25 of the TMDD standard.
3.5.3.3.2.5.2.5 Link Average Speed
The requirement for Link Average Speed is defined by Section 3.3.4.3.2.5.2.28 of the TMDD standard.
3.5.3.3.2.5.2.6 Link Estimated Speed
The requirement for Link Estimated Speed is defined by Section 3.3.4.3.2.5.2.29 of the TMDD standard.
3.5.3.3.2.5.2.7 Link Speed Limit – Link Status
The requirement for Link Speed Limit – Link Status is defined by Section 3.3.4.3.2.5.2.30 of the TMDD standard.
3.5.3.3.2.5.2.8 Link Current Advisory Speed
The requirement for Link Current Advisory Speed is defined by Section 3.3.4.3.2.5.2.31 of the TMDD standard.
3.5.3.3.2.5.2.9 Link Truck Speed Limit – Link Status
The requirement for Link Truck Speed Limit – Link Status is defined by Section 3.3.4.3.2.5.2.32 of the TMDD standard.
3.5.3.3.2.5.2.10 Speed Limit Units – Link Status
The requirement for Speed Limit Units – Link Status is defined by Section 3.3.4.3.2.5.2.33 of the TMDD standard.
3.5.3.3.2.5.2.11 Link Status Date and Time Change Information
The requirement for Link Status Date and Time Change Information is defined by Section 3.3.4.3.2.5.2.38 of the TMDD standard.
3.5.3.4 Share Route Information
The requirements to exchange route information between centers are as follows:
3.5.3.4.1 Share Route Inventory Information
The requirements to exchange route inventory information between centers are as follows:
3.5.3.4.1.1 Send Route Inventory Information Upon Request
The requirement for Send Route Inventory Information Upon Request is defined by Section 3.3.4.4.1.1 of the TMDD standard.
3.5.3.4.1.2 Publish Route Inventory Information
The requirement for Publish Route Inventory Information is defined by Section 3.3.4.4.1.2 of the TMDD standard.
3.5.3.4.1.3 Subscribe to Route Inventory Information
The requirement for Subscribe to Route Inventory Information is defined by Section 3.3.4.4.1.3 of the TMDD standard.
3.5.3.4.1.4 Contents of the Route Inventory Request
The requirement for Contents of the Route Inventory Request is defined by Section 3.3.4.4.1.4 of the TMDD standard.
3.5.3.4.1.5 Contents of the Route Inventory Information
The requirement for Contents of the Route Inventory Information is defined by Section 3.3.4.4.1.5 of the TMDD standard.
3.5.3.4.1.5.1 Required Route Inventory Information Content
The requirement for Required Route Inventory Information Content is defined by Section 3.3.4.4.1.5.1 of the TMDD standard.
3.5.3.4.1.5.2 Optional Route Inventory Information Content
The following are optional requirements that an owner center may include in the route inventory information sent to an external center.
3.5.3.4.1.5.2.1 Restrictions – Route Inventory
The requirement for Restrictions – Route Inventory is defined by Section 3.3.4.4.1.5.2.1 of the TMDD standard.
3.5.3.4.1.5.2.2 Roadway Network Name
The requirement for Roadway Network Name is defined by Section 3.3.4.4.1.5.2.2 of the TMDD standard.
3.5.3.4.1.5.2.3 Route Name – Route Inventory
The requirement for Route Name – Route Inventory is defined by Section 3.3.4.4.1.5.2.3 of the TMDD standard.
3.5.3.4.1.5.2.4 Alternate Names – Route Inventory
The requirement for Alternative Name-Route Inventory is defined by Section 3.3.4.4.1.5.2.4 of the TMDD standard.
3.5.3.4.1.5.2.5 Route Length
The requirement for Route Length is defined by Section 3.3.4.4.1.5.2.5 of the TMDD standard.
3.5.3.4.1.5.2.6 Node List
The requirement for Node List is defined by Section 3.3.4.4.1.5.2.6 of the TMDD standard.
3.5.3.4.1.5.2.7 Route Image URL
The requirement for Route Image URL is defined by Section 3.3.4.4.1.5.2.7 of the TMDD standard.
3.5.3.4.1.5.2.8 Route Image URL Reference Medium
The requirement for Route Image URL Reference Medium is defined by Section 3.3.4.4.1.5.2.8 of the TMDD standard.
3.5.3.4.1.5.2.9 Route Inventory Date and Time Change Information
The requirement for Route Inventory Date and Time Change Information is defined by Section 3.3.4.4.1.5.2.9 of the TMDD standard.
3.5.3.4.2 Share Route Status Information
The requirements to exchange route status information between centers are as follows:
3.5.3.4.2.1 Send Route Status Information Upon Request
The requirement for Send Route Status Information Upon Request is defined by Section 3.3.4.4.2.1 of the TMDD standard.
3.5.3.4.2.2 Publish Route Status Information
The requirement for Publish Route Status Information is defined by Section 3.3.4.4.2.2 of the TMDD standard.
3.5.3.4.2.3 Subscribe to Route Status Information
The requirement for Subscribe to Route Status Information is defined by Section 3.3.4.4.2.3 of the TMDD standard.
3.5.3.4.2.4 Contents of the Route Status Request
The requirement for Contents of the Route Status Request is defined by Section 3.3.4.4.2.4 of the TMDD standard.
3.5.3.4.2.5 Contents of the Route Status Information
The requirement for Contents of the Route Status Information is defined by Section 3.3.4.4.2.5 of the TMDD standard.
3.5.3.4.2.5.1 Required Route Status Information Content
The requirement for Required Route Status Information Content is defined by Section 3.3.4.4.2.5.1 of the TMDD standard.
3.5.3.4.2.5.2 Optional Route Status Information Content
The following are optional requirements that an owner center may include in the route status information sent to an external center.
3.5.3.4.2.5.2.1 Restrictions – Route Status
The requirement for Restrictions – Route Status is defined by Section 3.3.4.4.2.5.2.1 of the TMDD standard.
3.5.3.4.2.5.2.2 Route Name – Route Status
The requirement for Route Name-Route Status is defined by Section 3.3.4.4.2.5.2.2 of the TMDD standard.
3.5.3.4.2.5.2.3 Route Detour Status Flag
The requirement for Route Detour Status Flag is defined by Section 3.3.4.4.2.5.2.3 of the TMDD standard.
3.5.3.4.2.5.2.4 Route Surface Conditions
The requirement for Route Surface Conditions is defined by Section 3.3.4.4.2.5.2.4 of the TMDD standard.
3.5.3.4.2.5.2.5 Route Data Stored Type
The requirement for Route Data Stored Type is defined by Section 3.3.4.4.2.5.2.8 of the TMDD standard.
3.5.3.4.2.5.2.6 Route Traffic Algorithm Data Type
The requirement for Route Traffic Algorithm Data Type is defined by Section 3.3.4.4.2.5.2.9 of the TMDD standard.
3.5.3.4.2.5.2.7 Route Travel Time
The requirement for Route Travel Time is defined by Section 3.3.4.4.2.5.2.13 of the TMDD standard.
3.5.3.4.2.5.2.8 Route Average Speed
The requirement for Route Average Speed is defined by Section 3.3.4.4.2.5.2.16 of the TMDD standard.
3.5.3.4.2.5.2.9 Route Current Advisory Speed
The requirement for Route Current Advisory Speed is defined by Section 3.3.4.4.2.5.2.19 of the TMDD standard.
3.5.3.4.2.5.2.10 Speed Limit Units – Route Status
The requirement for Speed Limit Units – Route Status is defined by Section 3.3.4.4.2.5.2.20 of the TMDD standard.
3.5.3.4.2.5.2.11 Event Description Time – Route Status
The requirement for Event Description Time – Route Status is defined by Section 3.3.4.4.2.5.2.21 of the TMDD standard.
3.5.3.4.2.5.2.12 Route Status Date and Time Change Information
The requirement for Route Status Date and Time Change Information is defined by Section 3.3.4.4.2.5.2.22 of the TMDD standard.
3.5.4 Provide Device Inventory and Status.
In the context of RTSMIP, the section below provides requirements for sharing road weather data between centers. These requirements fall into two general types-sharing of static data such as device inventory and location, and sharing of dynamic data such as the status and observations of the road weather devices. The requirements are taken from TMDD.
3.5.4.1 Generic Devices
This section contains those requirements from TMDD that apply to all types of devices, although in the context of RTSMIP, these requirements apply only to road weather measurement devices.
The requirements to share device information between centers are as follows:
3.5.4.1.1 Share Device Information
The following should be considered when exchanging device information between centers:
- It is not necessary to send the device inventory when organization, center or contact information is updated, unless the unique identifier changes.
- The object IDs should be unique within the TMC but concatenating with NTCIP 1104 naming convention (use as prefixes) in a regional environment. NTCIP 1104 naming convention uses the following: country ID, state ID, agency ID, center ID, entity kind, entity type and entity instance.
The requirements for a device information request are as follows:
3.5.4.1.1.1 Contents of Device Information Request
The requirement for Contents of Device Information Request is defined by Section 3.3.5.1.1.1 of the TMDD standard.
3.5.4.1.1.1.1 Required Device Information Request Content
The requirement for Required Device Information Request Content is defined by Section 3.3.5.1.1.1.1 of the TMDD standard.
3.5.4.1.1.1.2 Optional Device Information Request Content
If the owner center supports it, the following are optional requirements that an external center may include in the device information request sent to an owner center.
3.5.4.1.1.1.2.1 Authentication – Device Information
The requirement for Authentication – Device Information is defined by Section 3.3.5.1.1.1.2.1 of the TMDD standard.
3.5.4.1.1.1.2.1.1 Operator Identifier-Device Information
The requirement for Operator Identifier – Device Information is defined by Section 3.3.5.1.1.1.2.1.1 of the TMDD standard.
3.5.4.1.1.1.2.2 External Center Organization – Device Information
The requirement for External Center Organization-Device Information is defined by Section 3.3.5.1.1.1.2.2 of the TMDD standard
3.5.4.1.1.1.3 Content of Device Information Request Filter
The requirement for Content of Device Information Request Filter is defined by Section 3.3.5.1.1.1.3 of the TMDD standard.
3.5.4.1.1.1.3.1 Device Identifier Filter
The requirement for Device Information Filter is defined by Section 3.3.5.1.1.1.3.1 of the TMDD standard.
3.5.4.1.1.1.3.2 Roadway Network Identifier Filter
The requirement for Roadway Network Identifier Filter is defined by Section 3.3.5.1.1.1.3.2 of the TMDD standard.
3.5.4.1.1.1.3.3 Link Identifier Filter
The requirement for Link Identifier Filter is defined by Section 3.3.5.1.1.1.3.3 of the TMDD standard.
3.5.4.1.1.1.3.4 Route Designator Filter
The requirement for Route Designator Filter is defined by Section 3.3.5.1.1.1.3.4 of the TMDD standard.
3.5.4.1.1.1.3.5 Linear Reference Filter
The requirement for Linear Reference Filter is defined by Section 3.3.5.1.1.1.3.5 of the TMDD standard.
3.5.4.1.2 Share Device Inventory Header Information
The requirements to exchange device inventory information between centers are as follows:
3.5.4.1.2.1 Contents of the Device Inventory Header
The requirement for Contents of the Device Inventory Header is defined by Section 3.3.5.1.2.1 of the TMDD standard.
3.5.4.1.2.1.1 Required Device Inventory Content
The requirement for Required Device Inventory Content is defined by Section 3.3.5.1.2.1.1 of the TMDD standard.
3.5.4.1.2.1.2 Optional Device Inventory Content
The following are optional requirements that an owner center may include in the device inventory information sent to an external center.
3.5.4.1.2.1.2.1 Restrictions – Device Inventory
The requirement for Restrictions-Device Inventory is defined by Section 3.3.5.1.2.1.2.1 of the TMDD standard
3.5.4.1.2.1.2.2 Device Description
The requirement for Device Description is defined by Section 3.3.5.1.2.1.2.2 of the TMDD standard.
3.5.4.1.2.1.2.3 Device Control Type
The requirement for Device Control Type is defined by Section 3.3.5.1.2.1.2.3 of the TMDD standard.
3.5.4.1.2.1.2.4 Roadway Network Identifier – Device Inventory
The requirement for Roadway Network Identifier – Device Inventory is defined by Section 3.3.5.1.2.1.2.5 of the TMDD standard.
3.5.4.1.2.1.2.5 Node Identifier-Device Inventory
The requirement for Node Identifier – Device Inventory is defined by Section 3.3.5.1.2.1.2.6 of the TMDD standard.
3.5.4.1.2.1.2.6 Node Name – Device Inventory
The requirement for Node Name – Device Inventory is defined by Section 3.3.5.1.2.1.2.7 of the TMDD standard.
3.5.4.1.2.1.2.7 Link Identifier – Device Inventory
The requirement for Link Identifier – Device Inventory is defined by Section 3.3.5.1.2.1.2.8 of the TMDD standard.
3.5.4.1.2.1.2.8 Link Name – Device Inventory
The requirement for Link Name – Device Inventory is defined by Section 3.3.5.1.2.1.2.9 of the TMDD standard.
3.5.4.1.2.1.2.9 Link Direction – Device Inventory
The requirement for Link Direction – Device Inventory is defined by Section 3.3.5.1.2.1.2.10 of the TMDD standard.
3.5.4.1.2.1.2.10 Linear Reference – Device Inventory
The requirement for Linear Reference – Device Inventory is defined by Section 3.3.5.1.2.1.2.11 of the TMDD standard.
3.5.4.1.2.1.2.11 Linear Reference Version
The requirement for Linear Reference Version is defined by Section 3.3.5.1.2.1.2.12 of the TMDD standard.
3.5.4.1.2.1.2.12 Route Designator – Device Inventory
The requirement for Route Designator – Device Inventory is defined by Section 3.3.5.1.2.1.2.13 of the TMDD standard.
3.5.4.1.2.1.2.13 Device Uniform Resource Locator (URL)
The requirement for Device Uniform Resource Locator (URL) is defined by Section 3.3.5.1.2.1.2.14 of the TMDD standard.
3.5.4.1.2.1.2.14 Device URL Reference Medium
The requirement for Device URL Reference Medium is defined by Section 3.3.5.1.2.1.2.15 of the TMDD standard
3.5.4.1.2.1.2.15 Device Inventory Date and Time Change Information
The requirement for Device Inventory Date and Time Change Information is defined by Section 3.3.5.1.2.1.2.16 of the TMDD standard.
3.5.4.1.3 Share Device Status Header Information
The requirements to exchange device status information between centers are as follows:
3.5.4.1.3.1 Contents of the Device Status Header
The requirement for Contents of the Device Status Header is defined by Section 3.3.5.1.3.1 of the TMDD standard.
3.5.4.1.3.1.1 Required Device Status Header Content
The requirement for Required Device Status Header Content is defined by Section 3.3.5.1.3.1.1 of the TMDD standard.
3.5.4.1.3.1.2 Optional Device Status Header Content
The following are optional requirements that an owner center may include in the device status header sent to an external center.
3.5.4.1.3.1.2.1 Restrictions – Device Status
The requirement for Restrictions – Device Status is defined by Section 3.3.5.1.3.1.2.1 of the TMDD standard.
3.5.4.1.3.1.2.2 Unique Identifier of the Controlling Center
The requirement for Unique Identifier of the Controlling Center is defined by Section 3.3.5.1.3.1.2.2 of the TMDD standard.
3.5.4.1.3.1.2.3 Device Communications Status
The requirement for Device Communications Status is defined by Section 3.3.5.1.3.1.2.3 of the TMDD standard.
3.5.4.1.3.1.2.4 Operator Identifier – Device Status
The requirement for Operator Identifier – Device Status is defined by Section 3.3.5.1.3.1.2.4 of the TMDD standard.
3.5.4.1.3.1.2.5 Event Identifier – Device Status
The requirement for Event Identifier – Device Status is defined by Section 3.3.5.1.3.1.2.5 of the TMDD standard.
3.5.4.1.3.1.2.6 Event Response Plan – Device Status
The requirement for Event Response Plan – Device Status is defined by Section 3.3.5.1.3.1.2.6 of the TMDD standard.
3.5.4.1.3.1.2.7 Device Status Date and Time Change Information
The requirement for Device Status Date and Time Change Information is defined by Section 3.3.5.1.3.1.2.7 of the TMDD standard.
3.5.4.2 Environment Sensors
The environmental sensor station (ESS) model assumes that each environmental sensor station may have multiple environmental sensors. Each environmental sensor may collect different types of environmental or roadway data. Each environmental sensor may also be located on different links (roadways), on different lanes, bodies of water, or different elevations.
The requirements to exchange ESS information between centers are as follows:
3.5.4.2.1 Share ESS Inventory Information
The requirements for sharing ESS inventory information with other authorized centers are as follows:
3.5.4.2.1.1 Send ESS Inventory Information Upon Request
The requirement for Send ESS Inventory Information Upon Request is defined by Section 3.3.5.6.1.1 of the TMDD standard.
3.5.4.2.1.2 Publish ESS Inventory Information
The requirement for Publish ESS Inventory Information is defined by Section 3.3.5.6.1.2 of the TMDD standard.
3.5.4.2.1.3 Subscribe to ESS Inventory Information
Subscribe to ESS Inventory Information is defined by Section 3.3.5.6.1.3 of the TMDD standard.
3.5.4.2.1.4 Contents of the ESS Inventory Request
The requirement for Contents of the ESS Inventory Request is defined by Section 3.3.5.6.1.4 of the TMDD standard.
3.5.4.2.1.5 Contents of the ESS Inventory Information
The requirement for Contents of the ESS Inventory Information is defined by Section 3.3.5.6.1.5 of the TMDD standard.
3.5.4.2.1.6 Required ESS Inventory Content Information
The requirement for Required ESS Inventory Content Information is defined by Section 3.3.5.6.1.5.1 of the TMDD standard.
3.5.4.2.1.6.1 Optional ESS Inventory Content
The following are optional requirements that an owner center may include in the ESS inventory information sent to an external center.
3.5.4.2.1.6.2 Lane Number – ESS
The requirement for Lane Number – ESS is defined by Section 3.3.5.6.1.5.2.1 of the TMDD standard.
3.5.4.2.1.6.3 Device Elevation
The requirement for Device Elevation is defined by Section 3.3.5.6.1.5.2.2 of the TMDD standard.
3.5.4.2.1.6.4 Device Height
The requirement for Device Height is defined by Section 3.3.5.6.1.5.2.3 of the TMDD standard.
3.5.4.2.1.6.5 Device Type
The requirement for Device Type is defined by Section 3.3.5.6.1.5.2.4 of the TMDD standard.
3.5.4.2.1.6.6 Device Operation Type
The requirement for Device Operation Type is defined by Section 3.3.5.6.1.5.2.5 of the TMDD standard.
3.5.4.2.1.6.7 Device Mobility Type
The requirement for Device Mobility Type is defined by Section 3.3.5.6.1.5.2.6 of the TMDD standard.
3.5.4.2.2 Share ESS Status Information
The requirements for sharing ESS status information with other authorized centers are as follows:
3.5.4.2.2.1 Send ESS Status Information Upon Request
The requirement for Send ESS Status Information Upon Request is defined by Section 3.3.5.6.2.1 of the TMDD standard.
3.5.4.2.2.2 Publish ESS Status Information
The requirement for Publish ESS Status Information is defined by Section 3.3.5.6.2.2 of the TMDD standard.
3.5.4.2.2.3 Subscribe to ESS Status Information
The requirement for Subscribe to ESS Status Information is defined by Section 3.3.5.6.2.3 of the TMDD standard.
3.5.4.2.2.4 Contents of the ESS Status Request
The requirement for Contents of the ESS Status Request is defined by Section 3.3.5.6.2.4 of the TMDD standard.
3.5.4.2.2.5 Contents of the ESS Status Information
The requirement for Contents of the ESS Status Information is defined by Section 3.3.5.6.2.5 of the TMDD standard.
3.5.4.2.3 Share ESS Observation Data Information
The requirements for sharing ESS observation data information with other authorized centers are as follows:
3.5.4.2.3.1 Send ESS Observation Data Information Upon Request
The requirement for Send ESS Observation Data Information Upon Request is defined by Section 3.3.5.6.3.1 of the TMDD standard.
3.5.4.2.3.2 Publish ESS Observation Data Information
The requirement for Publish ESS Observation Data Information is defined by Section 3.3.5.6.3.2 of the TMDD standard.
3.5.4.2.3.3 Subscribe to ESS Observation Data Information
The requirement for Subscribe to ESS Observation Data Information is defined by Section 3.3.5.6.3.3 of the TMDD standard.
3.5.4.2.3.4 Contents of the ESS Observation Data Information Request
The requirement for Contents of the ESS Observation Data Information Request is defined by Section 3.3.5.6.3.4 of the TMDD standard.
3.5.4.2.3.5 Contents of the ESS Observation Data Information
The requirement for Contents of the ESS Observation Data Information is defined by Section 3.3.5.6.3.5 of the TMDD standard.
3.5.4.2.3.5.1 Required ESS Observation Data Information Content
The requirement for Required ESS Observation Data Information Content is defined by Section 3.3.5.6.3.5.1 of the TMDD standard.
3.5.4.2.3.5.2 Optional ESS Observation Data Information Content
The following are optional requirements that an owner center may include in the ESS observation data information sent to an external center.
3.5.4.2.3.5.2.1 Restrictions – ESS Data
The requirement for Restrictions – ESS Data is defined by Section 3.3.5.6.3.5.2.1 of the TMDD standard.
3.5.4.2.4 Share ESS Metadata
The requirements for sharing ESS metadata information with other authorized centers are as follows:
3.5.4.2.4.1 Send ESS Metadata Information Upon Request
The requirement for Send ESS Metadata Information Upon Request is defined by Section 3.3.5.6.4.1 of the TMDD standard.
3.5.4.2.4.2 Contents of the ESS Metadata Request
The requirement for Contents of the ESS Metadata Request is defined by Section 3.3.5.6.4.2 of the TMDD standard.
3.5.4.2.4.3 Contents of the ESS Metadata Information
The requirement for Contents of the ESS Metadata Information is defined by Section 3.3.5.6.4.3 of the TMDD standard.
3.5.4.2.4.3.1 Required ESS Metadata Information Content
The requirement for Required ESS Metadata Information Content is defined by Section 3.3.5.6.4.3.1 of the TMDD standard.
3.5.4.2.4.3.2 Optional ESS Metadata Information Content
The following are optional requirements that an owner center may include in the ESS observation metadata information sent to an external center.
3.5.4.2.4.3.2.1 Username
The requirement for Username is defined by Section 3.3.5.6.4.3.2.1 of the TMDD standard.
3.5.4.2.4.3.2.2 Password
The requirement for Password is defined by Section 3.3.5.6.4.3.2.2 of the TMDD standard.
3.5.4.2.4.3.3 Collector Configuration Information
The requirement for Collector Configuration Information is defined by Section 3.3.5.6.4.3.3 of the TMDD standard.
3.5.4.2.4.3.4 Optional Collector Configuration Information Content
The following are optional requirements that an owner center may include in the ESS observation metadata information sent to an external center.
3.5.4.2.4.3.4.1 Observation Type
The requirement for Observation Type is defined by Section 3.3.5.6.4.3.4.1 of the TMDD standard.
3.5.4.2.4.3.4.2 Null Value
The requirement for Null Value is defined by Section 3.3.5.6.4.3.4.2 of the TMDD standard.
3.5.4.2.4.3.5 Owner Organization – ESS Metadata
The requirement for Owner Organization – ESS Metadata is defined by Section 3.3.5.6.4.3.5 of the TMDD standard.
3.5.4.2.4.3.6 Sensor Specific Information
The requirement for Sensor Specific Information is defined by Section 3.3.5.6.4.3.6 of the TMDD standard.
3.5.4.2.4.3.6.1 Required Sensor Specific Metadata Information
The requirement for Required Sensor Specific Metadata Information is defined by Section 3.3.5.6.4.3.6.1 of the TMDD standard.
3.5.4.2.4.3.6.2 Optional Sensor Specific Metadata Information Content
The following are optional requirements that an owner center may include in the sensor specific metadata information sent to an external center.
3.5.4.2.4.3.6.2.1 Sensor Description
The requirement for Sensor Description is defined by Section 3.3.5.6.4.3.6.2.1 of the TMDD standard.
3.5.4.2.4.3.6.2.2 Minimum Value of the Sensor Range
The requirement for Minimum Value of the Sensor Range is defined by Section 3.3.5.6.4.3.6.2.2 of the TMDD standard.
3.5.4.2.4.3.6.2.3 Maximum Value of the Sensor Range
The requirement for Maximum Value of the Sensor Range is defined by Section 3.3.5.6.4.3.6.2.3 of the TMDD standard.
3.5.4.2.4.3.6.2.4 Maximum Positive Rate of Change
The requirement for Maximum Positive Rate of Change is defined by Section 3.3.5.6.4.3.6.2.4 of the TMDD standard.
3.5.4.2.4.3.6.2.5 Maximum Negative Rate of Change
The requirement for Maximum Negative Rate of Change is defined by Section 3.3.5.6.4.3.6.2.5 of the TMDD standard.
3.5.4.2.4.3.6.2.6 Rate Interval
The requirement for Rate Interval is defined by Section 3.3.5.6.4.3.6.2.6 of the TMDD standard.
3.5.4.2.4.3.6.2.7 Persistence Interval
The requirement for Persistence Interval is defined by Section 3.3.5.6.4.3.6.2.7 of the TMDD standard.
3.5.4.2.4.3.6.2.8 Persistence Threshold
The requirement for Persistence Threshold is defined by Section 3.3.5.6.4.3.6.2.8 of the TMDD standard.
3.5.4.2.4.3.6.2.9 Like Instrument Threshold
The requirement for Like Instrument Threshold is defined by Section 3.3.5.6.4.3.6.2.9 of the TMDD standard.
3.5.4.2.4.3.6.2.10 Date of Calibration
The requirement for Date of Calibration is defined by Section 3.3.5.6.4.3.6.2.10 of the TMDD standard.
3.5.4.2.4.3.6.2.11 Date of Last Maintenance
The requirement for Date of Last Maintenance is defined by Section 3.3.5.6.4.3.6.2.11 of the TMDD standard.
3.5.4.2.4.3.6.2.12 Serial Number
The requirement for Serial Number is defined by Section 3.3.5.6.4.3.6.2.12 of the TMDD standard.
3.5.4.2.4.3.6.2.13 Sensor Resolution
The requirement for Sensor Resolution is defined by Section 3.3.5.6.4.3.6.2.13 of the TMDD standard.
3.5.4.2.4.3.6.2.14 Sensor Accuracy
The requirement for Sensor Accuracy is defined by Section 3.3.5.6.4.3.6.2.14 of the TMDD standard.
3.5.4.2.4.3.6.2.15 Minimum Value Output
The requirement for Minimum Value Output is defined by Section 3.3.5.6.4.3.6.2.15 of the TMDD standard.
3.5.4.2.4.3.6.2.16 Maximum Value Output
The requirement for Maximum Value Output is defined by Section 3.3.5.6.4.3.6.2.16 of the TMDD standard.
3.5.4.2.4.3.6.2.17 Sensor to Station North South Offset
The requirement for Sensor to Station North South Offset is defined by Section 3.3.5.6.4.3.6.2.17 of the TMDD standard.
3.5.4.2.4.3.6.2.18 Sensor to Station East West Offset
The requirement for Sensor to Station East West Offset is defined by Section 3.3.5.6.4.3.6.2.18 of the TMDD standard.
3.5.4.2.4.3.6.2.19 Sensor to Station Elevation Offset
The requirement for Sensor to Station Elevation Offset is defined by Section 3.3.5.6.4.3.6.2.19 of the TMDD standard.
3.5.4.2.4.3.6.2.20 Sensor to Surface Offset
The requirement for Sensor to Surface Offset is defined by Section 3.3.5.6.4.3.6.2.20 of the TMDD standard.
3.5.4.2.4.3.6.2.21 Embedded Material Description
The requirement for Embedded Material Description is defined by Section 3.3.5.6.4.3.6.2.21 of the TMDD standard.
3.5.4.2.4.3.6.2.22 Output Average Interval
The requirement for Output Average Interval is defined by Section 3.3.5.6.4.3.6.2.22 of the TMDD standard.
3.5.4.2.4.3.6.2.23 Output Internal Units
The requirement for Output Internal Units is defined by Section 3.3.5.6.4.3.6.2.23 of the TMDD standard.
3.5.4.2.4.3.6.2.24 Initial Installation Date – ESS Sensor
The requirement for Initial Installation Date – ESS Sensor is defined by Section 3.3.5.6.4.3.6.2.24 of the TMDD standard.
3.5.4.2.4.3.6.2.25 Begin Date/Time of Out of Service Period
The requirement for Begin Date/Time of Out of Service Period is defined by Section 3.3.5.6.4.3.6.2.25 of the TMDD standard.
3.5.4.2.4.3.6.2.26 End Date/Time of Out of Service Period
The requirement for End Date/Time of Out of Service Period is defined by Section 3.3.5.6.4.3.6.2.26 of the TMDD standard.
3.5.4.2.4.3.6.2.27 Sampling Interval
The requirement for Sampling Interval is defined by Section 3.3.5.6.4.3.6.2.27 of the TMDD standard.
3.5.4.2.4.3.7 Site Specific Information
If available, the following are requirements for site specific metadata information that an owner center may include in the ESS metadata information sent to an external center.
3.5.4.2.4.3.7.1 Required Site Specific Metadata Information
The requirement for Required Site Specific Metadata Information is defined by Section 3.3.5.6.4.3.7.1 of the TMDD standard.
3.5.4.2.4.3.7.2 Roadway Name
The requirement for Roadway Name is defined by Section 3.3.5.6.4.3.7.2 of the TMDD standard.
3.5.4.2.4.3.7.3 Linear Reference – ESS Metadata
The requirement for Linear Reference – ESS Metadata is defined by Section 3.3.5.6.4.3.7.3 of the TMDD standard.
3.5.4.2.4.3.7.4 Linear Reference Units
The requirement for Linear Reference Units is defined by Section 3.3.5.6.4.3.7.4 of the TMDD standard.
3.5.4.2.4.3.7.5 Distance to Roadway
The requirement for Distance to Roadway is defined by Section 3.3.5.6.4.3.7.5 of the TMDD standard.
3.5.4.2.4.3.7.6 Elevation from Roadway
The requirement for Elevation from Roadway is defined by Section 3.3.5.6.4.3.7.6 of the TMDD standard.
3.5.4.2.4.3.7.7 Jurisdiction
The requirement for Jurisdiction is defined by Section 3.3.5.6.4.3.7.7 of the TMDD standard.
3.5.4.2.4.3.7.8 State
The requirement for State is defined by Section 3.3.5.6.4.3.7.8 of the TMDD standard.
3.5.4.2.4.3.7.9 Country
The requirement for Country is defined by Section 3.3.5.6.4.3.7.9 of the TMDD standard.
3.5.4.2.4.3.7.10 Access Directions
The requirement for Access Directions is defined by Section 3.3.5.6.4.3.7.10 of the TMDD standard.
3.5.4.2.4.3.7.11 Site Representativeness
The requirement for Site Representativeness is defined by Section 3.3.5.6.4.3.7.11 of the TMDD standard.
3.5.4.2.4.3.7.12 Site Obstructions
The requirement for Site Obstructions is defined by Section 3.3.5.6.4.3.7.12 of the TMDD standard.
3.5.4.2.4.3.7.13 Site Landscape
The requirement for Site Landscape is defined by Section 3.3.5.6.4.3.7.13 of the TMDD standard.
3.5.4.2.4.3.7.14 Site Access Control
The requirement for Site Access Control is defined by Section 3.3.5.6.4.3.7.14 of the TMDD standard.
3.5.4.2.4.3.7.15 Site Slope
The requirement for Site Slope is defined by Section 3.3.5.6.4.3.7.15 of the TMDD standard.
3.5.4.2.4.3.7.16 Site Grade Direction
The requirement for Site Grade Direction Information is defined by Section 3.3.5.6.4.3.7.16 of the TMDD standard.
3.5.4.2.4.3.7.17 Site Wind Roughness
The requirement for Site Wind Roughness Information is defined by Section 3.3.5.6.4.3.7.17 of the TMDD standard.
3.5.4.2.4.3.7.18 Site Soil Type
The requirement for Site Soil Type is defined by Section 3.3.5.6.4.3.7.18 of the TMDD standard.
3.5.4.2.4.3.7.19 Unique Site Identifier
The requirement for Unique Site Identifier is defined by Section 3.3.5.6.4.3.7.19 of the TMDD standard.
3.5.4.2.4.3.8 Station Specific Information
If available, the following are requirements for station specific metadata information that an owner center may include in the ESS metadata information sent to an external center.
3.5.4.2.4.3.8.1 Required Station Specific Metadata Information
The requirement for Required Station Specific Metadata Information is defined by Section 3.3.5.6.4.3.8.1 of the TMDD standard.
3.5.4.2.4.3.8.2 Station Description
The requirement for Station Description is defined by Section 3.3.5.6.4.3.8.2 of the TMDD standard.
3.5.4.2.4.3.8.3 Station Operation Type
The requirement for Station Operation Type is defined by Section 3.3.5.6.4.3.8.3 of the TMDD standard.
3.5.4.2.4.3.8.4 Station Geo-coordinate Referencing Model
The requirement for Station Geo-coordinate Referencing Model is defined by Section 3.3.5.6.4.3.8.4 of the TMDD standard.
3.5.4.2.4.3.8.5 Station Power Source
The requirement for Station Power Source is defined by Section 3.3.5.6.4.3.8.5 of the TMDD standard.
3.5.4.2.4.3.8.6 Door Status
The requirement for Door Status is defined by Section 3.3.5.6.4.3.8.6 of the TMDD standard.
3.5.4.2.4.3.8.7 Battery Status
The requirement for Battery Status is defined by Section 3.3.5.6.4.3.8.7 of the TMDD standard.
3.5.4.2.4.3.8.8 Line Volts
The requirement for Line Volts is defined by Section 3.3.5.6.4.3.8.8 of the TMDD standard.
3.5.4.2.4.3.8.9 Station Maintenance Group Name
The requirement for Station Maintenance Group Name is defined by Section 3.3.5.6.4.3.8.9 of the TMDD standard.
3.5.4.2.4.3.8.10 Preventive Maintenance Interval
The requirement for Preventive Maintenance Interval is defined by Section 3.3.5.6.4.3.8.10 of the TMDD standard.
3.5.4.2.4.3.8.11 Maintenance Calibration Interval
The requirement for Maintenance Calibration Interval is defined by Section 3.3.5.6.4.3.8.11 of the TMDD standard.
3.5.4.2.4.3.8.12 Maintenance Status
The requirement for Maintenance Status is defined by Section 3.3.5.6.4.3.8.12 of the TMDD standard.
3.5.4.2.4.3.8.13 Initial Installation Date
The requirement for Initial Installation Date is defined by Section 3.3.5.6.4.3.8.13 of the TMDD standard.
3.5.4.2.4.3.8.14 Number of Devices
The requirement for Number of Devices is defined by Section 3.3.5.6.4.3.8.14 of the TMDD standard.
3.5.4.2.4.3.8.15 Communications Method
The requirement for Communications Method is defined by Section 3.3.5.6.4.3.8.15 of the TMDD standard.
3.5.4.2.4.3.8.16 Station Phone Number
The requirement for Station Phone Number is defined by Section 3.3.5.6.4.3.8.16 of the TMDD standard.
3.5.4.2.4.3.8.17 Station IP Address
The requirement for Station IP Address is defined by Section 3.3.5.6.4.3.8.17 of the TMDD standard.
3.5.4.2.4.3.8.18 Station Manufacturer
The requirement for Station Manufacturer is defined by Section 3.3.5.6.4.3.8.18 of the TMDD standard.
3.5.4.2.4.3.8.19 Observation Collection Interval
The requirement for Observation Collection Interval is defined by Section 3.3.5.6.4.3.8.19 of the TMDD standard.
3.5.4.2.4.3.8.20 Observation Collection Offset
The requirement for Observation Collection Offset is defined by Section 3.3.5.6.4.3.8.20 of the TMDD standard.
3.5.4.2.4.3.8.21 Transmission Interval
The requirement for Transmission Interval is defined by Section 3.3.5.6.4.3.8.21 of the TMDD standard.
3.5.4.2.4.3.8.22 Transmission Offset
The requirement for Transmission Offset is defined by Section 3.3.5.6.4.3.8.22 of the TMDD standard.
3.5.4.2.4.3.8.23 Transmission Format
The requirement for Transmission Format is defined by Section 3.3.5.6.4.3.8.23 of the TMDD standard.
3.5.4.2.4.3.8.24 Station Maintenance Contact Information
The requirement for Station Maintenance Contact Information is defined by Section 3.3.5.6.4.3.8.24 of the TMDD standard.
3.5.4.2.4.3.9 Climate Record Information
The requirement for Climate Record Information is defined by Section 3.3.5.6.4.3.9 of the TMDD standard.
3.5.4.2.4.3.10 Data Collector Information
The requirement for Data Collector Information is defined by Section 3.3.5.6.4.3.10 of the TMDD standard.
3.5.4.2.4.3.11 Image Information
The requirement for Image Information is defined by Section 3.3.5.6.4.3.11 of the TMDD standard.
3.5.4.2.4.3.12 Restrictions – ESS Metadata
The requirement for Restrictions – ESS Metadata is defined by Section 3.3.5.6.4.3.12 of the TMDD standard.
3.5.5 Transit Related Requirements
The following sections define requirements for sharing real time information on transit vehicle location and passenger loading as well as transit vehicle arrival and departure times.
3.5.5.1 Transit Vehicle Location and Passenger Loading
This feature enables a transit agency to provide transit vehicle location and passenger load information.
3.5.5.1.1 Request Transit Vehicle Location and Passenger Loading Information
An owner center shall respond to an authorized external center requesting transit vehicle and passenger loading information with a message containing the owner center’s transit vehicle and passenger loading information.
3.5.5.1.2 Subscribe to Transit Vehicle Location and Passenger Loading Information
An external center shall send a subscription message to an owner center requesting its transit vehicle location and passenger loading information.
3.5.5.1.3 Publish Transit Vehicle Location and Passenger Loading Information
An owner center shall publish a message containing its transit vehicle location and passenger loading information to all authorized, subscribing external centers.
3.5.5.1.4 Contents of Transit Vehicle Location and Passenger Loading Information Request
The owner center shall provide to an external center transit vehicle travel time information.
3.5.5.1.4.1 Transit Vehicle Location and Passenger Loading Request – Transit Vehicle Identifier
An external center shall include the transit vehicle identifier as part of transit vehicle travel time information request.
3.5.5.1.4.2 Transit Vehicle Location and Passenger Loading Request – Trip Identifier
An external center shall include the trip identifier as part of transit vehicle travel time information request.
3.5.5.1.4.3 Transit Vehicle Location and Passenger Loading Request – Route Identifier
An external center shall include the route identifier as part of transit vehicle travel time information request.
3.5.5.1.5 Contents of Transit Vehicle Location Information
The owner center shall provide to an external center transit vehicle location information.
3.5.5.1.5.1 Transit Vehicle Location – Measurement Time
The owner center shall provide to an external center the measurement time of the vehicle location information. The measurement time, in hours, minutes, and seconds, is the time when the owner center measured the transit vehicle location information.
3.5.5.1.5.2 Transit Vehicle Location – Transit Vehicle Identifier
The owner center shall provide to an external center the identifier of the transit vehicle as part of transit vehicle location information.
3.5.5.1.5.3 Transit Vehicle Location – Trip Identifier
The owner center shall provide to an external center the trip identifier of the transit vehicle as part of the transit vehicle location information.
3.5.5.1.5.4 Transit Vehicle Location – Route Identifier
A RSU shall provide to an external center the route identifier of the transit vehicle as part of the transit vehicle location information.
3.5.5.1.5.5 Transit Vehicle Location – Block Identifier
The owner center shall provide to an external center the identifier of the block of the transit vehicle as part of the transit vehicle location information.
3.5.5.1.5.6 Transit Vehicle Location – Vehicle Position
The owner center shall provide to an external center the transit vehicle geographic position (latitude, longitude, elevation) at the measurement time as part of the transit vehicle location information. The latitude and longitude are measured in units of 1/10th micro degree. The elevation represents the location of the surface of the roadway above or below the reference ellipsoid in units of 1 decimeter.
3.5.5.1.5.7 Transit Vehicle Location – Vehicle Heading
The owner center shall provide to an external center the transit vehicle heading at the measurement time as part of the transit vehicle location information. The vehicle heading is measured in heading sectors and each heading sector is 22.5 degrees wide.
3.5.5.1.5.8 Transit Vehicle Location – Passenger Load
The owner center shall provide to an external center the total number of passengers onboard the transit vehicle at the measurement time as part of the transit vehicle location information.
3.5.5.2 Transit Vehicle Arrival and Departure Times
This feature enables a transit agency to provide current transit vehicle arrival and departure time information.
3.5.5.2.1 Request Transit Vehicle Arrival and Departure Time Information
An owner center shall respond to an authorized external center requesting transit vehicle arrival and departure times with a message containing the owner center’s transit vehicle arrival and departure time information.
3.5.5.2.2 Subscribe to Transit Vehicle Arrival and Departure Time Information
An external center shall send a subscription message to an owner center requesting its transit vehicle arrival and departure time information.
3.5.5.2.3 Publish Transit Vehicle Arrival and Departure Time Information
An owner center shall publish a message containing its transit vehicle arrival and departure time information to all authorized, subscribing external centers.
3.5.5.2.4 Contents of Transit Vehicle Arrival and Departure Time Information Request
The owner center shall provide to an external center transit vehicle travel time information.
3.5.5.2.4.1 Transit Vehicle Arrival and Departure Time Information Request – Transit Vehicle Identifier
An external center shall include the transit vehicle identifier as part of transit vehicle travel time information request.
3.5.5.2.4.2 Transit Vehicle Arrival and Departure Time Information Request – Trip Identifier
An external center shall include the trip identifier as part of transit vehicle travel time information request.
3.5.5.2.4.3 Transit Vehicle Arrival and Departure Time Information Request – Route Identifier
An external center shall include the route identifier as part of transit vehicle travel time information request.
3.5.5.2.4.4 Transit Vehicle Arrival and Departure Time Information Request –Stop Identifier
An external center shall include the trip identifier as part of transit vehicle travel time information request.
3.5.5.2.5 Contents of Transit Vehicle Arrival and Departure Time Information
The owner center shall provide to an external center transit vehicle arrival and departure time information.
3.5.5.2.5.1 Transit Vehicle Arrival/ Departure Time – Publication Time
The owner center shall provide to an external center the publication time as part of the transit vehicle arrival/departure time information. The publication time is the time at which the passenger load information is provided by the external center and is in the format of hour, minute, and seconds (hhmmss).
3.5.5.2.5.2 Transit Vehicle Arrival/ Departure Time – Transit Vehicle Identifier
The owner center shall provide to an external center the identifier of the transit vehicle as part of transit vehicle arrival/departure time information.
3.5.5.2.5.3 Transit Vehicle Arrival/ Departure Time – Trip Identifier
The owner center shall provide to an external center the trip identifier of the transit vehicle as part of the transit vehicle location information.
3.5.5.2.5.4 Transit Vehicle Arrival/ Departure Time – Route Identifier
The owner center shall provide to an external center the route identifier of the transit vehicle as part of the transit vehicle arrival/departure time information.
3.5.5.2.5.5 Transit Vehicle Arrival/ Departure Time – Block Identifier
The owner center shall provide to an external center the identifier of the block of the transit vehicle as part of the transit vehicle arrival/departure time information.
3.5.5.2.5.6 Transit Vehicle Arrival/ Departure Time – Stop Identifier
The owner center shall provide to an external center the transit stop identifier as part of the transit vehicle arrival/departure time information.
3.5.5.2.5.7 Transit Vehicle Arrival/ Departure Time – Stop Location
The owner center shall provide to an external center the geographic location of the transit stop as part of the transit vehicle arrival/departure time information. The geographic location is defined as latitude and longitude. The latitude and longitude are measured in units of 1/10th micro degree.
3.5.5.2.5.8 Transit Vehicle Arrival/ Departure Time – Expected Stop Arrival Time
The owner center shall provide to an external center the expected arrival time at the stop as part of the transit vehicle arrival/departure time information. The arrival time is in the format hour, minute, and seconds (hhmmss).
3.5.5.2.5.9 Transit Vehicle Arrival/ Departure Time – Expected Stop Departure Time
The owner center shall provide to an external center the expected departure time from the stop as part of the transit vehicle arrival/departure time information. The departure time is in the format hour, minute, and seconds (hhmmss).
3.5.5.2.5.10 Transit Vehicle Arrival/Departure Time – Uncertainty
The owner center shall provide to an external center the expected uncertainty (defined in seconds) associated with the expected arrival or departure times.
3.5.5.2.5.11 Transit Vehicle Arrival/Departure Time – Service Alerts
The owner center shall provide to an external center service alerts that to provide updates whenever there is disruption on the network.
3.5.5.3 Transit Vehicle Travel Time
This feature enables a transit agency to provide current transit vehicle travel times for specific routes.
3.5.5.3.1 Request Transit Vehicle Travel Time Information
An owner center shall respond to an authorized external center requesting transit vehicle travel time with a message containing the owner center’s transit vehicle travel time information.
3.5.5.3.2 Subscribe to Transit Vehicle Travel Time Information
An external center shall send a subscription message to an owner center requesting its transit vehicle travel time information.
3.5.5.3.3 Publish Transit Vehicle Travel Time Information
An owner center shall publish a message containing its transit vehicle travel time information to all authorized, subscribing external centers
3.5.5.3.4 Contents of Transit Vehicle Travel Time Information Request
The owner center shall provide to an external center transit vehicle travel time information.
3.5.5.3.4.1 Transit Vehicle Travel Time Request – Transit Vehicle Identifier
An external center shall include the transit vehicle identifier as part of transit vehicle travel time information request.
3.5.5.3.4.2 Transit Vehicle Travel Time Request – Trip Identifier
An external center shall include the trip identifier as part of transit vehicle travel time information request.
3.5.5.3.4.3 Transit Vehicle Travel Time Request – Route Identifier
An external center shall include the route identifier as part of transit vehicle travel time information request.
3.5.5.3.4.4 Transit Vehicle Travel Time Request – Start Stop Identifier
An external center shall include the start stop identifier as part of transit vehicle travel time information request.
3.5.5.3.4.5 Transit Vehicle Travel Time Request – End Stop Identifier
An external center shall include the end stop identifier as part of transit vehicle travel time information request.
3.5.5.3.5 Contents of Transit Vehicle Travel Time Information
The owner center shall provide to an external center transit vehicle travel time information.
3.5.5.3.5.1 Transit Vehicle Travel Time – Publication Time
The owner center shall provide to an external center the publication time as part of the transit vehicle travel time information. The time is in the format hour, minute, and seconds (hhmmss).
3.5.5.3.5.2 Transit Vehicle Travel Time – Transit Vehicle Identifier
The owner center shall provide to an external center the identifier of the transit vehicle as part of transit vehicle travel time information.
3.5.5.3.5.3 Transit Vehicle Travel Time – Trip Identifier
The owner center shall provide to an external center the trip identifier of the transit vehicle as part of the transit vehicle travel time information.
3.5.5.3.5.4 Transit Vehicle Travel Time – Route Identifier
A owner center shall provide to an external center the route identifier of the transit vehicle as part of the transit vehicle travel time information.
3.5.5.3.5.5 Transit Vehicle Travel Time – Block Identifier
The owner center shall provide to an external center the identifier of the block of the transit vehicle as part of the transit vehicle travel time information.
3.5.5.3.5.6 Transit Vehicle Travel Time – Start Stop Identifier
The owner center shall provide to an external center the stop identifier of the starting stop for the determination of transit vehicle travel time.
3.5.5.3.5.7 Transit Vehicle Travel Time – End Stop Identifier
The owner center shall provide to an external center the stop identifier of the ending stop for the determination of transit vehicle travel time.
3.5.5.3.5.8 Transit Vehicle Travel Time – Trip Travel Time
The owner center shall provide to an external center the estimated travel time for the trip from the starting to ending stop as part of the transit vehicle travel time information. The time is in the format hour, minute, and seconds (hhmmss).
3.5.6 Weather Alert Requirements
The following subsections define requirements for providing weather related alerts.
3.5.6.1 Request Weather Alert Information
An owner center shall respond to an authorized external center requesting weather alerts with a message containing the owner center’s transit vehicle travel time information.
3.5.6.2 Contents of Weather Alerts Request
The owner center shall provide to an external center all weather based alerts that are currently in effect for the road network managed by the owner center.
3.5.6.3 Contents of Weather Alerts Information
The contents of the weather alert are contained in the following requirements.
3.5.6.3.1 Weather Alerts – Links
The owner center shall provide to an external center the roadway links associated with the weather alerts.
3.5.6.3.2 Weather Alerts – Node
The owner center shall provide to an external center the roadway node associated with the weather alert.
3.5.6.3.3 Weather Alerts – Area
The owner center shall provide to an external center the geographic area associated with the weather alert.
3.5.6.3.4 Weather Alerts – Start Time of Alert
The owner center shall provide to an external center the start time of the weather alert.
3.5.6.3.5 Weather Alerts – End Time of Alert
The owner center shall provide to an external center the end time of the weather alert.
3.5.6.3.6 Weather Alerts – Duration of Alert
The owner center shall provide to an external center the duration of the weather alert.
3.5.6.3.7 Weather Alerts – Hazardous Wind Speeds
The weather alert shall include indication of hazardous wind speed conditions. Hazardous wind speeds are defined as speeds in excess of 40 MPH.
3.5.6.3.8 Weather Alerts – Hazardous Precipitation
The weather alert shall include an indication of hazardous precipitation conditions. Hazardous precipitation conditions are defined as moderate or heavy rain, snow, or mixed precipitation. The definition of moderate or heavy precipitation is given in NTCIP 1204, Section 5.8.9.
3.5.6.3.9 Weather Alerts – Storm Cell Warning
The weather alert shall include a warning of hazardous storm cells. Hazardous storm cells include tornado, thunderstorm, and hail related cells.
3.5.6.4 Request Weather Alerts – NWS Bulletins
An owner center shall respond to an authorized external center requesting weather alert-NWS Bulletins with a message containing the owner center’s weather alert-NWS Bulletins upon request.
3.5.6.4.1 Contents of Weather Alerts – NWS Bulletins Request
The owner center shall provide to an external center all weather based alert-NWS Bulletins that are currently in effect for the road network managed by the owner center.
3.5.6.4.2 Contents of Weather Alerts – NWS Bulletins
The weather alert shall include National Weather Service Bulletins, including warnings for tornado, severe thunderstorm, flood, flash flood, dense fog, high wind, winter storm, snow, blizzard, or ice storm.
3.6 Performance Requirements
The performance requirements for RTSMIP, as defined below in this DXFS, are taken from TMDD. The purpose of the performance requirements is to specify the communications performance requirements for the information exchanges between two centers. This section defines the range of allowable time intervals between when an event takes place at an owner center (e.g., an action, a change in status, or a change in the data) to when it transmits the updated information to an external center, and the allowable time intervals between when a receiving center first receives a request to when it must begin transmitting a response.
The time intervals for each implementation will vary based on the message, the importance and size of the message, and environmental conditions, such as the communications network used and congestion on the network.
For example, an external center monitoring another agency’s traffic signal controller may be interested in receiving second-by-second information from the owner center, but may receive the owner center’s traffic signal inventory only when the inventory changes. Also, the response time to a request for an owner center’s complete traffic signal inventory will be different than the response time to a request for event data of a single event.
3.6.1 Message Transmission Time – Publication Updates
The owner center shall begin sending information update message to an authorized external center within 15 minutes after the information is updated in the owner center. This requirement is for owner centers that transmit updates to subscribing external centers, and assumes that the owner center has approved an external center’s subscription for information updates on an event-driven basis (See 3.4.2.2). The maximum time for an owner center to begin sending information update messages after the information is updated shall be between a range from 100 milliseconds to 24 hours.
3.6.2 Response Time
The owner center shall process a request from an external center within 1 minute of receiving the request. The response time is measured as the time, in milliseconds, between when a receiving center receives the last byte of a request message from another center, to the transmission of the first byte of the response. During the response time, the receiving center shall process the request in accordance with all of the rules of the relevant standards, including updating any values in its database and initiating the transmission of the appropriate response. The maximum response time for an owner center to process a request shall be between a range from 100 milliseconds to 1 hour.
