MétaCan
Menu
Back to cohort
Record W2261239996 · doi:10.2172/814296

DOE Safety Metrics Indicator Program (SMIP) Fiscal Year 2001 Fourth Quarter Report of Packaging- and Transportation-related Occurrences

2001· report· en· W2261239996 on OpenAlexaboutno aff
L.S. Dickerson

Bibliographic record

Venuenot available
Typereport
Languageen
FieldDecision Sciences
TopicRisk and Safety Analysis
Canadian institutionsnot available
Fundersnot available
KeywordsHazardous wasteQuarter (Canadian coin)Transport engineeringDatabaseOperations managementEngineeringComputer scienceWaste managementGeographyArchaeology

Abstract

fetched live from OpenAlex

The Safety Metrics Indicator Program (SMIP) retrieved 44 packaging- or transportation-related occurrences from the Occurrence Reporting and Processing System (ORPS) during the period from July 1 through September 30, 2001. Only those incidents that occur in preparation for transport, during transport, and during unloading of hazardous material are considered as packaging- or transportation-related occurrences. Other incidents with packaging and transportation (P and T) significance but not involving hazardous material (such as vehicle accidents or empty packagings) are not rated to the SMIP criteria, but are archived in the SMIP Subsidiary Database of occurrences, a sub-database of the main SMIP P and T Occurrence Database. Thirty-two of the originally-selected 44 occurrences were appropriate for classification to the SMIP criteria, only 7 of which have offsite applicability. Eight of the original 44 reports are archived in a subsidiary database because they either do not involve the transport of hazardous material or do not involve transport by vehicle, plane, boat, or rail. The others either were deleted because more thorough review revealed that they were not strictly related to P and T or were canceled by the reporting site and removed from the ORPS. These occurrences have not been normalized as in the Annual Report of Occurrences because the necessary information is not yet available. The number and severity of the selected occurrence reports (ORs) are consistent with historical reporting. Contamination events continue to be among the most common type of occurrences; however, ''Shipping Preparation'' events decreased this quarter to only 4 events from the 21 reported last quarter. None of the 32 ORs that were rated had event consequence measures (W{sub EC}) greater than 2; 14 of them were categorized as having a W{sub EC} of 1. This means that all of the fourth-quarter FY 2001 ORs had only slight consequences at worst (i.e., resulting in minimal safety consequences with little potential for ultimately leading to suspected endangerment of people or environmental contamination). Because the event consequence measure is low, the overall hazard significance ratings (HSRs) are relatively low, indicating that the actual risks posed by the occurrences are not highly threatening. In fact, even the one reported emergency OR and the two unusual ORs had HSRs of 24 or less. The ORs are summarized in the appendix and listed along with their HSRs and stakeholder interest [currently termed the stakeholder and publicity rating (SPR)]. This enables one to get a feel for how the nature of an occurrence and its P and T significance translate into a severity rating. During the quarter, it was noticed that the number of events pertaining to either dropping packages or damaging packages while moving material by forklift had increased from previous years. Only four such events were reported in FY 1999 and seven events reported during FY 2000. However, 13 events have been reported during this fiscal year. Therefore a lessons learned (LL) pertaining to minimizing accidents while moving material by forklift was developed and posted to the U.S. Department of Energy LL list server to mitigate this trend.

Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.

How this classification was reachedexpand

Full frame machine prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.

metaresearch head score (Codex)0.005
metaresearch head score (Gemma)0.013
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: Not applicable
GenreCandidate signal: Other · Consensus signal: none
Teacher disagreement score0.070
Threshold uncertainty score0.138

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0050.013
Meta-epidemiology (narrow)0.0020.001
Meta-epidemiology (broad)0.0010.000
Bibliometrics0.0110.015
Science and technology studies0.0010.000
Scholarly communication0.0030.001
Open science0.0020.001
Research integrity0.0010.001
Insufficient payload (model declined to judge)0.0080.004

Machine scores (provisional)

The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.

Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.

Opus teacher head0.075
GPT teacher head0.389
Teacher spread0.313 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it

Classification

machine, unvalidated

Machine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.

The models applied no category: nothing in the taxonomy fit this work.
Study designNot applicable
Domainnot available
GenreOther

How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".

Quick stats

Citations0
Published2001
Admission routes1
Has abstractyes

Explore more

Same topicRisk and Safety AnalysisFrench-language works237,207