DOCSLIB.ORG

Copyrighted Material

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Copyrighted Material Subject Index ACC, see Adaptive Cruise Control reliable, 70 evaluation repetitive, 69 communication failure, 216 coexistence, 266 controller, 217 compliance, 107 sensor robustness, 216 CSMA, 66, 240 ADA, see Advanced Driver Assistance DHCP, 76 cooperative FTP, 163 ACC controller, 224 geocast, 12, 15, 17, 18, 20, 78 safety margin, 177 geographical addressing, 185 SUMMITS, 208 HTTP, 163 IEEE 1609.0, 159 Balise, see also European Train Control IEEE 1609.1, 158, 174 System, 84 IEEE 1609.2, 106, 109, 159, 174 IEEE 1609.3, 159, 174 CDN, see Content Distribution Network, 265 IEEE 1609.4, 62, 65, 159, 174 Collision avoidance IEEE 1609.5, 159 Adaptive Cruise Control, 217, 218 IEEE 802.11p, 240 cooperative, 119, 150 IEEE 802.11 Positive Train Control, 135 SyncScan, 237 Communication ACK, 233 application basic access procedure, 233 voice communication, 33 DeuceScan, 238 public safety DIFS, 233 failure, 33 http://www.pbookshop.comfast handover support, 228, 231–238, first responder, 30 240 GPS, 31 OpportunisticScanning, 238 history, 30–31 Post Transmission Backoff, see PTB inter-agency, 33 PTB, 233 9/11, 31, 33 COPYRIGHTED MATERIALTBTT, 233, 237 Wi-Fi locator, 31 TSF, 232 traffic class IEEE 802.11n, 178 WiMAX, 184 IGMP, 194 Communication protocol IP, 18, 155, 163, 266 anonymous gossip, 70 IPv6, 175, 186–187 Application Sub Layer, 162 6lowpan, 197 ARIB STD-T88, 162 uIPv6, 197 automotive message set, 159, 168 ISA-SP100.11a, 196 broadcast, 17, 18, 66, 85, 88, 158, 180, MANET, 65, 76 220 MEXT, 176 Vehicular Networking Edited by Marc Emmelmann, Bernd Bochow, C. Christopher Kellum c 2010 John Wiley & Sons, Ltd 286 SUBJECT INDEX MLD, 194 46, 61, 66–69, 75, 157, 158, Mobile IP 160–162, 172, 173, 175, 181 inter-agent handover, 196 IEEE 802.11p, 95, 158, 173, Mobile IPv4, 175 178–181, 235 Mobile IPv6, 176, 186–194 multichannel MAC, 61–66 multiple access networks, 190 propagation model, 48–50 network mobility, 187 autonomicity and evolvability, 259, 266 multicast, 85, 90, 194, 238 availability, 108 acknowledged, 87, 181 basic security, 111–112 anonymous gossip, 71 coexistence, 258 NEMO, 76, 175, 176, 187–190 cognitive, 253, 259, 266 Binding Update, 188 collaboration and cooperation, 267 flow identification, 190 coordination, 267 HA proxy, 193 distributed, 267 handover delay, 194 dynamical coordination, 253 multiple flow handover, 191 convergence, see also integration, RO security issues, 193 interoperability, 259 RO solution space, 193 data centric, 119 equipment certification, 41 Route Optimization, 191–194 fast handover architecture, 240–241 PIM-SM, 194 macro cell, 240 position-based, 111, 113, 186 micro cell, 240 routing, 78 overlay MAC, 240, 250 routing RCU, see RCU geographical, 185 RCU, 240–243 IP multicast, 194–196 Remote Base Station, see RBS, see Route Optimization, 176 RBS RTCP, 88 RBS, 240–243, 250 SAE J2735, 159, 168 future system, 253 security, 231 GSM-R IEEE 1609.2, 106, 109 CAB Radio, 173 spanning tree, 32 handover delay, 184, 237 TCP, 12, 155, 163, 266 APTT metric, 245 UDP, 12, 155, 266 challenges, 239 unicast, 15, 17–19 DeuceScan, 238 WAVE stack, 174 http://www.pbookshop.comIEEE 802.11, 231–238 Wireless HART, 196 influence of data rate, 233–235 WSMP, 11, 12, 15, 16, 18, 64, 186 mobile WiMAX, 185 Z-Wave, 196 OpportunisticScanning, 238 ZigBee, 196 SyncScan, 237 Communication system handover requirements, 229–230, 239 ad hoc handover taxonomy, 228, 230–231 MANEMO, 176 handover criteria, 230–231 MANET, 71, 176 handover decision, 230–231 aggregated moving network, 176 higher layer aspects, 230 automotive link layer reestablishment, 230–231 ad hoc, 36, 161, 175, 178 network discovery, 230–231 antenna patterns, 47–48 HSDPA ARIB STD-T75, 162 hard handover, 98 DSRC, see Dedicated Short Range IEEE 802.15.1, 196 Communications, 2, 4, 5, 7, 26, 37, IEEE 802.15.4, 196 SUBJECT INDEX 287 implementation, 228, 239 TCN, see Train Communication automated toolchain, 243–244 Network, 99–100 C-code, 243–244 TORNAD, 84 intra-macro-cell handover, 242–243 TGV, 84 intra-micro-cell handover, 242 WTB, see Wire Train Bus, 100 key postulates, 239 PHY MAC scheme, 241–242 synchronization, 231 methodology, 243–244 public safety performance evaluation, 245–252 ad hoc, 35 predictive fast handover, 242–243 Extended Area Network, 38–40 proof-of-concept demonstrator, group communication, 34 244–245 IEEE 802.11p, 39 RBS, 244 Incident Area Network, 35–36 SDL, 243–244 Jurisdictional Area Network, 36–38 system architecture, 240–241 packet data, 30 integration, see also interoperability, 38, permanent infrastructure, 36 101–102, 125, 261 push to talk, 31 interoperability, see also integration, quick kits, 36 35–37, 151–152, 175 regional network integration, 39 protocols, 163 trunking, 31, 34 standardization , 151–152 vehicular relay, 31 railway MAC Airlink, 102 centralized, 240 EIRENE, 97 deterministic, 229, 240 GSM-R, 85, 96, 258 hybrid, 229 hard real time, 99 SDU, 231 IAGO, 102 stochastic, 229, 240 integration, 101–102 synchronization, 231, 232 magnetic coupling technology, 93 mesh network, 238, 253 MODCOMM, 102 IEEE 802.11s, 36 on-board, 99–100 public safety, 32, 253 propagation model, 92 mobile AP regulation, 93 public safety, 31 satellite, 99 mobile router services, 88–91 Mobile IPv4, 175http://www.pbookshop.comsoft real time, 100 NEMO, 187, 190 train motion influence, 93 public safety, 32 wireless link model, 92–93 multi-radio, 36, 177, 190 wireless systems, 93–99 multichannel coordination, 61 requirements multiple control channels, 66 access delay, 229 single control channel, 65 delay, 231 on-board Inter-Arrival Time, 229, 249 CAN, see Controller Area Network, jitter, 229 150, 155, 163, 196 location information, 229 Ethernet, 100 packet loss, 231 gateway, 101 packet reordering, 231 IPTrain, 100 radio cell overlap, 237, 242 MVB, see Multifunction Vehicle Bus, RSSI, 231, 237, 247 99 railway, 85–88, 229–230 Profinet, 100 Round Trip Time, 229 288 SUBJECT INDEX RFID, 175 V2I system safety performance criteria, 205 beacon, 112 vehicle-driver, 204 satellite, 99 vehicle-infrastructure, 204 IRIDIUM, 30 vehicle-infrastructure system Teledesic, 30 design problems, 204–205 security human factors, 205 necessity, 122 human factors, 203, 204, 206, 208, security architecture, 106, 109–111, 225 116, 124 traffic flow, 203, 204, 206 service interruption time, see handover vehicle-vehicle, 209 delay CR, see Cognitive Radio, 267 Software Defined Radio, 153 Credential certification traintowayside Certification Authorities evolution, 83–84 cooperation, 117 vehicular Certification Authority, 106, 109, 116, IEEE 802.11, 228, 232, 240, 253 154 wearable, 42 multi-domain, 117 WiBree, 196 organizational concerns, 124 wireless Pseudonym Provider, 111 3GPP LTE, 173, 181–184 regional, 109 break-before-make handover, see revocation, 117 hard handover self-certification, 113 BSS association, 180 DOD, see United States Department of cost, 231 Defense EDGE, 97 Strategic Rail Corridor Network, 130 GPRS, 97, 176, 181, 258 DOT, see United States Department of GSM, 96, 181 Transportation, 21 handover, 230, 239 ITS spectrum, 2 handover frequency, 230 STB, see Surface Transportation Board handover phases, see handover interstate commerce act, 144 taxonomy Transportation Technology Center, 137 hard handover, 183, 231 DTN, see Disruption- and Delay Tolerant HSDPA, 98, 182 Network, 265 HSUPA, 98 VANET, 265 LMR, see Land Mobilehttp://www.pbookshop.com Radio, 36, 38 make-before-break handover, see soft EAN, see Extended Area Network, 38–40 handover IEEE 802.16e, 38 mobile WiMAX, 185 integration, 38 soft handover, 231 LMR, 38 support for high user velocities, 230 Equipment certification UMTS, 98, 181 military, 41 vertical handover, 183 Future Internet virtual beacon, 181 Internet of things, 265 Wi-Fi, 94, 155, 181 Network symbiosis, 265 wide-area automotive, 181–185 Smart objects, 265 WiMAX, 36, 38, 95, 173, 184–185 VANET, 265 Cooperation awareness, 119 IAN, see Incident Area Network, 35–36 cognitive, 267 IEEE 802.11s, 36 collision avoidance, 119 mesh network, 36, 238, 253 SUBJECT INDEX 289 temporary infrastructure, 35 APTT, 245 use cases, 35–36 active scanning, 232–233 VANET, 35, 40 association, 232 IRSA, see Integrated Full-Range Speed authentication, 232 Assistant handover, 231–238 controllers, 209–212 handover decision, 232, 237 implementation, 219 joining a BSS, 232 scenarios, 209 link layer reestablishment, 232–235, ITS modeller, 204 238, 253 network discovery, 232, 237–238 JAN, see Jurisdictional Area Network, 36–38 passive scanning, 232–233 IEEE 802.11, 36 radio system IEEE 802.16e, 36 channel switch time, 245 IEEE 802.22, 37 train communication mesh network, 36, 238 IEEE 802.16d, 95 permanent infrastructure, 36 train control MARS, see Multi-Agent Real-time Simulator, performance management, 144 204 security cost, 142 Multi-Aspect Assessment security indicator, 145 approach, 204 VANET applications, 20 NSA, see United States National Security broadcast protocols, 69 Agency broadcast reliability, 66 information assurance technical gossip protocol, 71 framework, 139 multichannel coordination, 64–65 NEMO, 76 OSI, see Open Systems Interconnection, 89, packet drop burst, 67 138, 149, 154, 162 packet drop rate, 67 packet loss, 64 Performance evaluation Positioning Access Point Transition Time, see APTT ERTMS, 102 APTT, 245 GNSS, 119 application CALM, 175 cryptographic overhead, 116 Doppler shift, 121 application reliability, 69 forged signal, 119 cooperative system,http://www.pbookshop.com 205 GPS, see Global Positioning System empirical results, 249–252 Inter-Arrival Time, 249 PTC, 134, 144 emulation public safety, 31 vehicular
Load more

Recommended publications
  • Federal Railroad Administration Office of Safety Headquarters Assigned Accident Investigation Report HQ-2008-96
    Federal Railroad Administration Office of Safety Headquarters Assigned Accident Investigation Report HQ-2008-96 Amtrak (ATK) Northbrook, IL December 25, 2008 Note that 49 U.S.C. §20903 provides that no part of an accident or incident report made by the Secretary of Transportation/Federal Railroad Administration under 49 U.S.C. §20902 may be used in a civil action for damages resulting from a matter mentioned in the report. DEPARTMENT OF TRANSPORTATION FRA FACTUAL RAILROAD ACCIDENT REPORT FRA File # HQ-2008-96 FEDERAL RAILROAD ADMINISTRATION 1.Name of Railroad Operating Train #1 1a. Alphabetic Code 1b. Railroad Accident/Incident No. Amtrak [ATK ] ATK 110589 2.Name of Railroad Operating Train #2 2a. Alphabetic Code 2b. Railroad Accident/Incident No. N/A N/A N/A 3.Name of Railroad Operating Train #3 3a. Alphabetic Code 3b. Railroad Accident/Incident No. N/A N/A N/A 4.Name of Railroad Responsible for Track Maintenance: 4a. Alphabetic Code 4b. Railroad Accident/Incident No. Northeast IL Regional Commuter Rail Corp. [NIRC] NIRC USB041 5. U.S. DOT_AAR Grade Crossing Identification Number 6. Date of Accident/Incident 7. Time of Accident/Incident 388037N Month 12 Day 25 Year 2008 07:05:00 AM PM 8. Type of Accident/Indicent 1. Derailment 4. Side collision 7. Hwy-rail crossing 10. Explosion-detonation 13. Other Code (single entry in code box) 2. Head on collision 5. Raking collision 8. RR grade crossing 11. Fire/violent rupture (describe in narrative) 3. Rear end collision 6. Broken Train collision 9. Obstruction 12. Other impacts 07 9.
    [Show full text]
  • Federal Railroad Administration Office of Safety Headquarters Assigned Accident Investigation Report HQ-2009-64
    Federal Railroad Administration Office of Safety Headquarters Assigned Accident Investigation Report HQ-2009-64 Amtrak (ATK) Fairbury, NE December 9, 2009 Note that 49 U.S.C. §20903 provides that no part of an accident or incident report made by the Secretary of Transportation/Federal Railroad Administration under 49 U.S.C. §20902 may be used in a civil action for damages resulting from a matter mentioned in the report. DEPARTMENT OF TRANSPORTATION FRA FACTUAL RAILROAD ACCIDENT REPORT FRA File # HQ-2009-64 FEDERAL RAILROAD ADMINISTRATION 1.Name of Railroad Operating Train #1 1a. Alphabetic Code 1b. Railroad Accident/Incident No. Amtrak [ATK ] ATK 114102 2.Name of Railroad Operating Train #2 2a. Alphabetic Code 2b. Railroad Accident/Incident No. N/A N/A N/A 3.Name of Railroad Operating Train #3 3a. Alphabetic Code 3b. Railroad Accident/Incident No. N/A N/A N/A 4.Name of Railroad Responsible for Track Maintenance: 4a. Alphabetic Code 4b. Railroad Accident/Incident No. Norfolk Southern Corp. [NS ] NS 114102 5. U.S. DOT_AAR Grade Crossing Identification Number 6. Date of Accident/Incident 7. Time of Accident/Incident 735236Y Month 12 Day 09 Year 2009 05:18: AM PM 8. Type of Accident/Indicent 1. Derailment 4. Side collision 7. Hwy-rail crossing 10. Explosion-detonation 13. Other Code (single entry in code box) 2. Head on collision 5. Raking collision 8. RR grade crossing 11. Fire/violent rupture (describe in narrative) 3. Rear end collision 6. Broken Train collision 9. Obstruction 12. Other impacts 07 9. Cars Carrying 10. HAZMAT Cars 11.
    [Show full text]
  • WESTRACE First-Line Maintenance Manual 11.0
    WESTRACE First-Line Maintenance Manual for WESTRACE MkI WRTOFLMM Issue 11.0 CONTACTING INVENSYS RAIL W http://www.invensysrail.com Asia Pacific ABN 78 000 102 483 179–185 Normanby Rd (Locked Bag 66) South Melbourne Victoria 3205 Australia T +61 1300 724 518 F +61 3 9233 8777 E [email protected] India No. 112–114 Raheja Chambers 12 Museum Road Bangalore 560 001 Karnataka India T +91 80 3058 8763/64 F +91 80 3058 8765 North America 2400 Nelson Miller Parkway Louisville Kentucky 40223 USA T +1 502 618 8800 F +1 502 618 8810 E [email protected] Spain, Portugal and Latin America Avda. de Castilla Apartado de Correos 6 Parque Empresarial (Edif Grecia) 28830 San Fernando de Henares Madrid Spain T +34 9 1675 4212 F +34 9 1656 9840 E [email protected] UK and Northern Europe PO Box 79 Pew Hill Chippenham Wiltshire SN15 1JD UK T +44 1249 44 1441 F +44 1249 65 2322 E [email protected] WESTRACE First-Line Maintenance Manual for WESTRACE MkI Document CI: WRTOFLMM Issue: 11.0 Date of Issue: 03 Dec 2010 Change History: Issue Date Comment Changed Checked Approved 1.0 7/9/94 WRTFGEN. initial issue 2.0 4/4/96 WRTFGEN, CR273 3.0 30/10/96 WRTFGEN, CR319 1.0 16/11/94 WETFWAYE, initial release 2.0 17/12/96 WETFWAYE, CR1385, CR1728, WR348, WR349, WR350 4.0 1/9/00 WRTOFLMM, initial issue. Compiled PGB from WRTFGEN 3.0 and WETFWAYE 2.0 CR333, 334, 379, 394, 395, 402, 404, 405, 406, 407, 440, 454, 502, 515 5.0 3/8/01 Rebuilt to correct faulty 4.0 build PGB 6.0 20/2/03 CR 783, 789, 790 PGB 7.0 11/10/04 CR831 ML DJ WMcD 8.0 12/9/05 CR325, 340, 345, 372, 378 ML SR WMcD 9.0 29/1/07 CR423, 428, 433 ML SR WMcD 10.0 10/2/09 Updated branding ML ML WMcD 11.0 03/12/10 Updated branding MH WMcD WMcD Copyright This document is protected by Copyright and all information contained therein is confidential.
    [Show full text]
  • Federal Railroad Administration Office of Safety Headquarters Assigned Accident Investigation Report HQ-2008-94
    Federal Railroad Administration Office of Safety Headquarters Assigned Accident Investigation Report HQ-2008-94 Canadian Pacific (CP) River JCT, MN December 17, 2008 Note that 49 U.S.C. §20903 provides that no part of an accident or incident report made by the Secretary of Transportation/Federal Railroad Administration under 49 U.S.C. §20902 may be used in a civil action for damages resulting from a matter mentioned in the report. DEPARTMENT OF TRANSPORTATION FRA FACTUAL RAILROAD ACCIDENT REPORT FRA File # HQ-2008-94 FEDERAL RAILROAD ADMINISTRATION 1.Name of Railroad Operating Train #1 1a. Alphabetic Code 1b. Railroad Accident/Incident No. SOO Line RR Co. [SOO ] SOO 209549 2.Name of Railroad Operating Train #2 2a. Alphabetic Code 2b. Railroad Accident/Incident No. SOO Line RR Co. [SOO ] SOO 209549 3.Name of Railroad Operating Train #3 3a. Alphabetic Code 3b. Railroad Accident/Incident No. N/A N/A N/A 4.Name of Railroad Responsible for Track Maintenance: 4a. Alphabetic Code 4b. Railroad Accident/Incident No. SOO Line RR Co. [SOO ] SOO 209549 5. U.S. DOT_AAR Grade Crossing Identification Number 6. Date of Accident/Incident 7. Time of Accident/Incident Month 12 Day 17 Year 2008 04:48:00 AM PM 8. Type of Accident/Indicent 1. Derailment 4. Side collision 7. Hwy-rail crossing 10. Explosion-detonation 13. Other Code (single entry in code box) 2. Head on collision 5. Raking collision 8. RR grade crossing 11. Fire/violent rupture (describe in narrative) 3. Rear end collision 6. Broken Train collision 9. Obstruction 12. Other impacts 04 9.
    [Show full text]
  • Federal Railroad Administration Office of Safety Headquarters Assigned Accident Investigation Report HQ-2008-48
    Federal Railroad Administration Office of Safety Headquarters Assigned Accident Investigation Report HQ-2008-48 Canadian National-North America (CN) Crystal Springs, MS May 27, 2008 Note that 49 U.S.C. §20903 provides that no part of an accident or incident report made by the Secretary of Transportation/Federal Railroad Administration under 49 U.S.C. §20902 may be used in a civil action for damages resulting from a matter mentioned in the report. DEPARTMENT OF TRANSPORTATION FRA FACTUAL RAILROAD ACCIDENT REPORT FRA File # HQ-2008-48 FEDERAL RAILROAD ADMINISTRATION 1.Name of Railroad Operating Train #1 1a. Alphabetic Code 1b. Railroad Accident/Incident No. Amtrak [ATK ] ATK 108129 2.Name of Railroad Operating Train #2 2a. Alphabetic Code 2b. Railroad Accident/Incident No. N/A N/A N/A 3.Name of Railroad Operating Train #3 3a. Alphabetic Code 3b. Railroad Accident/Incident No. N/A N/A N/A 4.Name of Railroad Responsible for Track Maintenance: 4a. Alphabetic Code 4b. Railroad Accident/Incident No. Canadian National - North America [CN ] CN 596181 5. U.S. DOT_AAR Grade Crossing Identification Number 6. Date of Accident/Incident 7. Time of Accident/Incident 299824D Month 05 Day 27 Year 2008 01:00: AM PM 8. Type of Accident/Indicent 1. Derailment 4. Side collision 7. Hwy-rail crossing 10. Explosion-detonation 13. Other Code (single entry in code box) 2. Head on collision 5. Raking collision 8. RR grade crossing 11. Fire/violent rupture (describe in narrative) 3. Rear end collision 6. Broken Train collision 9. Obstruction 12. Other impacts 07 9.
    [Show full text]
  • NTSB Hearing Jeff Young Asst
    NTSB Hearing Jeff Young Asst. Vice President – Transportation Systems March 4, 2009 1 Topics to Address • Current Train Control Systems • Concerns with Existing Systems • How does PTC Address Concerns with Existing Systems • UP PTC Pilot Locations • PTC Challenges • PTC Implementation Plan • PTC Project Timeline 2 Dark Territory Track Warrant Control Track Warrant Authority Limits AMTK • Main Track Not Signaled • Movement Authority Conveyed By Track Warrant or Direct Traffic Control permit •2. [X] Proceed From (Station or Location) To (Station or Location) On Main Track Spokane Subdivision •8. [X] Hold Main Track At Last Named Point • Train separation provided by train dispatcher and train crew 3 Automatic Block System (ABS) Track Warrant Control Track Warrant Authority Limits AMTK • Main Track Signaled for Movement in Both Directions • Movement Authority Conveyed By Track Warrant or Direct Traffic Control permit •2. [X] Proceed From ( Station or Location) To ( Station or Location ) On Main Track Spokane Subdivision •8. [X] Hold Main Track At Last Named Point • Train separation provided by train dispatcher, train crew and signal system 4 Automatic Block Signal (ABS) Current Of Traffic Field Signal Indication • Two Main tracks with an assigned direction of movement • Movement authority is conveyed by signal system • The tracks are only signaled for movement in the assigned direction • Train separation provided by train crew and signal system 5 Centralized Traffic Control (CTC) Field Signal Indication • One or More Main Tracks Signaled
    [Show full text]
  • View / Open TM Database Composite.Pdf
    • • • • TRANSPORTATION-MARKINGS • DATABASE • COMPOSITE CATEGORIES • CLASSIFICATION & INDEX • • • -­ • III III • 1 TRANSPORTATION-MARKINGS: A STUDY IN CO.MMUNICATION MONOGRAPH SERIES Alternate Series Title: An Inter-modal Study of Safety Aids Transportatiol1-Markings Database Alternate T-M Titles: Transport [ation] Mark [ing]s / Transport Marks / Waymarks T-MFoundations, 4th edition, 2005 (Part A, Volume I, First Studies in T-M) (3rd edition, 1999; 2nd edition, 1991) Composite Categories A First Study in T-M: The US, 2nd edition, 1993 (Part B, Vol I) Classification & Index International Marine Aids to Navigation, 2nd edition, 1988 (parts C & D, Vol I) [Unified First Edition ofParts A-D, University Press ofAmerica, 1981] International Traffic Control Devices, 2nd edition, 2004 (Part E, Volume II, Further Studies in T-M) (lst edition, 1984) Part Iv Volume III, Additional Studies, International Railway Signals, 1991 (Part F, Vol II) International Aero Navigation Aids, 1994 (Part G, Vol II) Transportation-Markil1gs: A Study il1 T-M General Classification with Index, 2nd edition, 2004 (Part H, Vol II) (1st edition, 1994) Commllnication Monograph Series Transportation-Markings Database: Marine Aids to Navigation, 1st edition, 1997 (I'art Ii, Volume III, Additional Studies in T-M) TCDs, 1st edition, 1998 (Part Iii, Vol III) Railway Signals. 1st edition, 2000 (part Iiii, Vol III) Aero Nav Aids, 1st edition, 2001 (Part Iiv, Vol III) Composite Categories Classification & Index, 1st edition, 2006 (part Iv, Vol III) (2nd edition ofDatabase, Parts Ii-v,
    [Show full text]
  • UPRR - General Code of Operating Rules
    Union Pacific Rules UPRR - General Code of Operating Rules Seventh Edition Effective April 1, 2020 Includes Updates as of September 28, 2021 PB-20280 1.0: GENERAL RESPONSIBILITIES 2.0: RAILROAD RADIO AND COMMUNICATION RULES 3.0: Section Reserved 4.0: TIMETABLES 5.0: SIGNALS AND THEIR USE 6.0: MOVEMENT OF TRAINS AND ENGINES 7.0: SWITCHING 8.0: SWITCHES 9.0: BLOCK SYSTEM RULES 10.0: RULES APPLICABLE ONLY IN CENTRALIZED TRAFFIC CONTROL (CTC) 11.0: RULES APPLICABLE IN ACS, ATC AND ATS TERRITORIES 12.0: RULES APPLICABLE ONLY IN AUTOMATIC TRAIN STOP SYSTEM (ATS) TERRITORY 13.0: RULES APPLICABLE ONLY IN AUTOMATIC CAB SIGNAL SYSTEM (ACS) TERRITORY 14.0: RULES APPLICABLE ONLY WITHIN TRACK WARRANT CONTROL (TWC) LIMITS 15.0: TRACK BULLETIN RULES 16.0: RULES APPLICABLE ONLY IN DIRECT TRAFFIC CONTROL (DTC) LIMITS 17.0: RULES APPLICABLE ONLY IN AUTOMATIC TRAIN CONTROL (ATC) TERRITORY 18.0: RULES APPLICABLE ONLY IN POSITIVE TRAIN CONTROL (PTC) TERRITORY GLOSSARY: Glossary For business purposes only. Unauthorized access, use, distribution, or modification of Union Pacific computer systems or their content is prohibited by law. Union Pacific Rules UPRR - General Code of Operating Rules 1.0: GENERAL RESPONSIBILITIES 1.1: Safety 1.1.1: Maintaining a Safe Course 1.1.2: Alert and Attentive 1.1.3: Accidents, Injuries, and Defects 1.1.4: Condition of Equipment and Tools 1.2: Personal Injuries and Accidents 1.2.1: Care for Injured 1.2.2: Witnesses 1.2.3: Equipment Inspection 1.2.4: Mechanical Inspection 1.2.5: Reporting 1.2.6: Statements 1.2.7: Furnishing Information
    [Show full text]
  • Ortungsanforderungen Und Ortungsmöglichkeiten Bei Sekundärbahnen
    Fakultät Verkehrswissenschaften „Friedrich List“ Professur für Verkehrssicherungstechnik Diplomarbeit Ortungsanforderungen und Ortungsmöglichkeiten bei Sekundärbahnen eingereicht von Fabian Kirschbauer geb. am 21.01.1991 in Straubing Prüfer: Prof. Dr.-Ing. Jochen Trinckauf Dr.-Ing. Ulrich Maschek Betreuer: Dr.-Ing. Michael Kunze (CERSS) Dipl.-Ing. Martin Sommer (CERSS) Dresden, den 15. Juli 2016 .......................................... Unterschrift des Studenten Autorenreferat Autorenreferat Die Sicherung von Zugfahrten erfolgt bei Eisenbahnen durch verschiedene Systeme der Sicherungstechnik. Die Ausrüstungsstandards, und damit auch die Ortungslösungen, orientieren sich an den Bedürfnissen des Kernnetzes und sind auf Bahnen untergeordne- ter Bedeutung, sog. Sekundärbahnen, hauptsächlich aus wirtschaftlichen Gründen nicht tragfähig. Steigende Anforderungen an die Sicherheit und der weiter zunehmende Kos- tendruck werden für diese Bahnen eine Ablösung der bisherigen Betriebsweise mit Hil- fe neuer technischer Möglichkeiten erfordern. Die vorliegende Arbeit soll Anforderun- gen an Ortungslösungen für Sekundärbahnen auf Grundlage bereits bestehender Umset- zungen identifizieren. Die Ergebnisse sollen die Basis für eine bedarfsgerechte Weiter- entwicklung bisheriger Techniken zur Sicherung von Zugfahrten auf Sekundärbahnen bilden. Bibliografischer Nachweis Fabian Kirschbauer Ortungsanforderungen und Ortungsmöglichkeiten bei Sekundärbahnen Technische Universität Dresden, Fakultät Verkehrswissenschaften „Friedrich List“, Professur für Verkehrssicherungstechnik
    [Show full text]
  • Finished Vehicle Logistics by Rail in Europe
    Finished Vehicle Logistics by Rail in Europe Version 3 December 2017 This publication was prepared by Oleh Shchuryk, Research & Projects Manager, ECG – the Association of European Vehicle Logistics. Foreword The project to produce this book on ‘Finished Vehicle Logistics by Rail in Europe’ was initiated during the ECG Land Transport Working Group meeting in January 2014, Frankfurt am Main. Initially, it was suggested by the members of the group that Oleh Shchuryk prepares a short briefing paper about the current status quo of rail transport and FVLs by rail in Europe. It was to be a concise document explaining the complex nature of rail, its difficulties and challenges, main players, and their roles and responsibilities to be used by ECG’s members. However, it rapidly grew way beyond these simple objectives as you will see. The first draft of the project was presented at the following Land Transport WG meeting which took place in May 2014, Frankfurt am Main. It received further support from the group and in order to gain more knowledge on specific rail technical issues it was decided that ECG should organise site visits with rail technical experts of ECG member companies at their railway operations sites. These were held with DB Schenker Rail Automotive in Frankfurt am Main, BLG Automotive in Bremerhaven, ARS Altmann in Wolnzach, and STVA in Valenton and Paris. As a result of these collaborations, and continuous research on various rail issues, the document was extensively enlarged. The document consists of several parts, namely a historical section that covers railway development in Europe and specific EU countries; a technical section that discusses the different technical issues of the railway (gauges, electrification, controlling and signalling systems, etc.); a section on the liberalisation process in Europe; a section on the key rail players, and a section on logistics services provided by rail.
    [Show full text]
  • Federal Railroad Administration Office of Safety Headquarters Assigned Accident Investigation Report HQ-2008-19
    Federal Railroad Administration Office of Safety Headquarters Assigned Accident Investigation Report HQ-2008-19 New Orleans Public Belt RR (NOPB) New Orleans, LA February 12, 2008 Note that 49 U.S.C. §20903 provides that no part of an accident or incident report made by the Secretary of Transportation/Federal Railroad Administration under 49 U.S.C. §20902 may be used in a civil action for damages resulting from a matter mentioned in the report. DEPARTMENT OF TRANSPORTATION FRA FACTUAL RAILROAD ACCIDENT REPORT FRA File # HQ-2008-19 FEDERAL RAILROAD ADMINISTRATION 1.Name of Railroad Operating Train #1 1a. Alphabetic Code 1b. Railroad Accident/Incident No. New Orleans Public Belt RR [NOPB] NOPB P8576 2.Name of Railroad Operating Train #2 2a. Alphabetic Code 2b. Railroad Accident/Incident No. New Orleans Public Belt RR [NOPB] NOPB P8576 3.Name of Railroad Operating Train #3 3a. Alphabetic Code 3b. Railroad Accident/Incident No. N/A N/A N/A 4.Name of Railroad Responsible for Track Maintenance: 4a. Alphabetic Code 4b. Railroad Accident/Incident No. New Orleans Public Belt RR [NOPB] NOPB P8576 5. U.S. DOT_AAR Grade Crossing Identification Number 6. Date of Accident/Incident 7. Time of Accident/Incident 464686V Month 02 Day 12 Year 2008 07:43:13 AM PM 8. Type of Accident/Indicent 1. Derailment 4. Side collision 7. Hwy-rail crossing 10. Explosion-detonation 13. Other Code (single entry in code box) 2. Head on collision 5. Raking collision 8. RR grade crossing 11. Fire/violent rupture (describe in narrative) 3. Rear end collision 6.
    [Show full text]
  • Federal Railroad Administration Office of Safety Headquarters Assigned Accident Investigation Report HQ-2005-104
    Federal Railroad Administration Office of Safety Headquarters Assigned Accident Investigation Report HQ-2005-104 Northeastern Illinois Regional Commuter Railroad (NIRC) Elmwood Park, Illinois November 23, 2005 Note that 49 U.S.C. §20903 provides that no part of an accident or incident report made by the Secretary of Transportation/Federal Railroad Administration under 49 U.S.C. §20902 may be used in a civil action for damages resulting from a matter mentioned in the report. DEPARTMENT OF TRANSPORTATION FRA FACTUAL RAILROAD ACCIDENT REPORT FRA File # HQ-2005-104 FEDERAL RAILROAD ADMINISTRATION 1.Name of Railroad Operating Train #1 1a. Alphabetic Code 1b. Railroad Accident/Incident No. Northeast IL Regional Commuter Rail Corp. [NIRC] NIRC NC016Y 2.Name of Railroad Operating Train #2 2a. Alphabetic Code 2b. Railroad Accident/Incident N/A N/A N/A 3.Name of Railroad Responsible for Track Maintenance: 3a. Alphabetic Code 3b. Railroad Accident/Incident No. Northeast IL Regional Commuter Rail Corp. [NIRC] NIRC NC016Y 4. U.S. DOT_AAR Grade Crossing Identification Number 5. Date of Accident/Incident 6. Time of Accident/Incident Month Day Year 372131E 11 23 2005 04:43:00 AM PM 7. Type of Accident/Indicent 1. Derailment 4. Side collision 7. Hwy-rail crossing 10. Explosion-detonation 13. Other (single entry in code box) 2. Head on collision 5. Raking collision 8. RR grade crossing 11. Fire/violent rupture (describe in narrative) 3. Rear end collision 6. Broken Train collision 9. Obstruction 12. Other impacts 07 8. Cars Carrying 9. HAZMAT Cars 10. Cars Releasing 11. People 12. Division HAZMAT Damaged/Derailed HAZMAT Evacuated 0 0 0 0 CHICAGO UNION STATIO 13.
    [Show full text]