In-Service Performance Evaluation: Guidelines for the Assembly and Analysis of Data (2022) / Chapter Skim
Currently Skimming:
Pages 44-54
The Chapter Skim interface presents what we've algorithmically identified as the most significant single chunk of text within every page in the chapter.
Select key terms on the right to highlight them within pages of the chapter.
From page 44... ...
44 The preparation of a comprehensive ISPE report is of paramount importance to successful completion of the ISPE, communicating your results, and collaborating with other jurisdictions to facilitate improved roadside safety. The ISPE report should be prepared as a formal technical report.
|
From page 45... ...
ISPE Documentation 45 interest (e.g., ownership of the analyst's organization, other organizational relationships, proprietary rights and interests) and explains how each was accounted for in the ISPE.
|
From page 46... ...
46 In-Service Performance Evaluation: Guidelines for the Assembly and Analysis of Data as well as information regarding the crash test documentation for the safety feature studied. Other references used should also be included here.
|
From page 47... ...
ISPE Documentation 47 Figure 2 provides the ISPE Data Set Assemblage and Case Reduction Sheet, which is the recommended format for documenting the assembly of the data set and the case reduction process. Figure 3 is a completed example of the same.
|
From page 48... ...
48 In-Service Performance Evaluation: Guidelines for the Assembly and Analysis of Data Crash Information Data Reduction Year Cases Intent/Codes Removed Data Years Cases Remaining 2010 215,813 1 Identified Cases with Safety Feature(s) : 2010 11,117 2011 221,483 2011 12,029 2012 220,190 2012 11,480 2013 218,794 Retain cases having values of 25 and 26 in harmful events field 13.
|
From page 49... ...
ISPE Documentation 49 MAX_SEV Jurisdictional Equivalence K 1 – Killed A 2 – Major injury B 3 – Moderate injury C 4 – Minor injury O 0 – Not injured U 8 – Injury/unknown severity 9 – Unknown Table 11. Example of recommended equivalence table for ISPE data set MAX_SEV.
|
From page 50... ...
50 In-Service Performance Evaluation: Guidelines for the Assembly and Analysis of Data example of the completed equivalence. Table 14 is the recommended format for documenting the PostHE equivalence, and Table 15 provides an example of the documentation of the PostHE equivalence.
|
From page 51... ...
ISPE Documentation 51 PostHE Jurisdictional Equivalence 00 No harmful event following impact with the safety feature listed in crash sequence.
|
From page 52... ...
52 In-Service Performance Evaluation: Guidelines for the Assembly and Analysis of Data NAME Jurisdiction's Description a b c d e f g h i j k l m n p q r s t u v w x y z 99 Note: The letter o is not used in the NAME field. Table 16.
|
From page 53... ...
ISPE Documentation 53 Column Field Name Definition Source A SFUE Safety feature under evaluation B CRN Crash number C CRASH_DATE Date of crash D TOTAL_UNITS Number of units involved in crash E MAX_SEV Maximum severity of injuries to occupants of impacting vehicle F VEH_TYPE Body type of vehicle G SPEED_LIMIT Posted speed limit H PostHE First harmful event after impact with safety feature I MHE Impact with safety feature was most harmful event J FHE Impact with safety feature was first harmful event K AHE Impact with safety feature occurred anywhere in crash sequence of events L FOHE Impact with safety feature was first and only harmful event M BREACH Vehicle breached safety feature N BREAK Predictable breakaway of safety feature O PRS Controlled penetration, redirection, or stop P PEN Roadside hardware penetrated into occupant compartment Q ICP Initial point on impacting vehicle at which it made contact with safety feature R NAME Subgroups of safety feature S INSTALL Safety feature inspected at installation T MAINT Safety feature inspected on a routine schedule Table 18. Recommended format for ISPE data set and source material.
|
From page 54... ...
54 In-Service Performance Evaluation: Guidelines for the Assembly and Analysis of Data Column Field Name Definition Source A SFUE Safety feature under evaluation Crash data Harmful Event Fields 1–4, Field Codes 25 and 26. B CRN Crash number Crash data, Field Code CRN.
|
Key Terms
This material may be derived from roughly machine-read images, and so is provided only to facilitate research.
More
information on Chapter Skim is available.