The objective of the Polaris Project is to define an Intelligent Transportation Systems (ITS) architecture for the state of Minnesota. An architecture is a framework that defines how multiple ITS Components interrelate and contribute to the overall ITS objectives and requirements. Minnesota ITS Components include things like Freeway Traffic Management Center, Regional ITS Management Center, Emergency Vehicle, Freeway Roadside Equipment, etc. The Polaris architecture provides multiple benefits including (1) definition and optimization of the location of system functions, (2) identification of critical interfaces, (3) illustration of how associated systems can be integrated to share resources and information, and (4) identifying where opportunities exist to establish standards for communications and physical components so that interoperability can be maintained as the system evolves to incorporate new capabilities and technologies. This appendix (Appendix C) lists the requirements that have been allocated to each service, function, and subfunction.
ITS System Specification. Appendix B: Requirements by Service/Function/Subfunction
1997
221 pages
Report
Keine Angabe
Englisch
Transportation & Traffic Planning , Transportation , Road Transportation , Minnesota , Transportation systems , Systems management , Requirements , Services , Transit industries , Public transportation , Prices , Architecture , Incident management , Traffic management , Information systems , Fleet management , Specifications , Polaris Project , ITS(Intelligent Transportation Systems)
STANDARD GALLEY SYSTEM SPECIFICATION APPENDIX II 20.0 DATA REQUIREMENTS AND PROCEDURES
SAE Technical Papers | 1991
Standard Galley System Specification Appendix II 20.0 Data Requirements and Procedures
SAE Technical Papers | 2013
Standard Galley System Specification Appendix II 20.0 Data Requirements and Procedures
SAE Technical Papers | 2005
APOLLO : system requirements specification
TIBKAT | 1984
ETCS system requirements specification (SRS)
SLUB | 1996