New York City Sub Regional ITS Architecture


Menu
Region Home
Stakeholders
Inventory by Stakeholder
Inventory by Entity
Sausage Diagram
Market Package Descriptions
Market Packages by Functional Area
Market Packages by Stakeholder
Equipment Package Descriptions
Architecture Flow Descriptions
Project Documents
Send Your Comments

 

Architecture Flow: incident information request

Description:
Request for incident information, clearing time, severity. The request can be a subscription that initiates as-needed information updates as well as a one-time request for information.

Communications Standards:
NTCIP C2C AASHTO-17 Application Profile for File Transfer Protocol (FTP) NTCIP 2303
NTCIP C2C AASHTO1-9 Application Profile for Common Object Request Broker Architecture (CORBA) NTCIP 2305
NTCIP C2C AASHTO-20 Application Profile for Data Exchange ASN.1 (DATEX) NTCIP 2304
NTCIP C2C AASHTO-21 Base Standard: Octet Encoding Rules (OER) NTCIP 1102
NTCIP C2C AASHTO-28 Subnet Profile for Ethernet NTCIP 2104
NTCIP C2C AASHTO-44 Information Profile for CORBA NTCIP 2502
NTCIP C2C AASHTO-46 Information Profile for DATEX NTCIP 2501
NTCIP C2C S-88 Internet (TCP/IP and UDP/IP) Transport Profile NTCIP 2202
Message Standards:
IEEE7 IEEE7 Standard for Common Incident Management Message Sets (IMMS) for use by EMCs IEEE P1512-2000
P1512.1 P1512.1 Standard for Traffic Incident Management Message Sets for Use by EMCs IEEE P1512.1
Data Standards:
IEEE7 IEEE7 Standard for Common Incident Management Message Sets (IMMS) for use by EMCs IEEE P1512-2000
P1512.1 P1512.1 Standard for Traffic Incident Management Message Sets for Use by EMCs IEEE P1512.1
P1512.a P1512.a Standard for Emergency Management Data Dictionary IEEE P1512.a

Last updated: 11-02-04