Its Component Specification Sample Contracts

NOTE TO READER:
Its Component Specification • April 10th, 1998

RSR Manage Rideshare Requests DRI Distribute Rideshare Information RRQ Manage Rider Requests TC Traffic Control MSNEO Manage Signal Network Operations CSM Control Signal Modes ISTP Implement/Adapt Signal Timing Plans MSR Manage Signal Resources MSNO Manage Signal Network Operations CSM Control Sign Modes STP Implement/Adapt Signing Plans MSIR Manage Signing Resources MTC Monitor Traffic Conditions CTD Collect Traffic Surveillance Data DITC Distribute Traffic Conditions DETC Determine Traffic Conditions STSD Sense Traffic Surveillance Data PTCS Plan Traffic Control Strategies MTCP Manage Traffic Control Strategies/Plans MTCR Manage Traffic Control Requirements TCI Travel Conditions Information MTCD Manage Travel Conditions Data CTC Collect Travel Conditions Source Data BTC Determine Basic Travel Conditions and Travel Effects STD Sense Travel Conditions Data MTCI Manage Travel Conditions I

AutoNDA by SimpleDocs
Minnesota Department of Transportation Agreement Number: 73807P
Its Component Specification • April 14th, 1998

This appendix defines the input data flows for each component of the Polaris Physical Architecture. The appendix is arranged in alphabetical order according to the destination component (i.e., the component that is receiving the data). For each destination component, the data flows are listed in alphabetical order. Each data flow is defined and its associated source component (i.e., the component that sent the data) is listed. Duplicate source component entries indicate that multiple services utilize the same data flow between source and destination components.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!