Download presentation
Presentation is loading. Please wait.
1
C3RS DataBase Query Tool (DBQT) Demo
C3RS User Group August 2016 Elisa T. Marfise C3RS Human Factors Manager (BAH) Linda Connell NASA ASRS & C3RS Program Director
2
Process Overview
3
Process Overview Reporter Submits Report to C3RS
4
Creation of a C3RS Database Record
[1] C3RS Assigns an Accession Number (ACN) to each individual Report received [2] Process looks for reports on the same event from different reporters (ACNs) and combines them into a single “record” [3] Analyst selects primary report for the record [4] Analyst speaks to individual reporters, writes separate Callbacks (1, 2, etc.) for each Person (ACN) that is part of the single record DataBase Query Tool (DBQT)
5
Process Overview Expert Analyst Utilizes Analyst Workbench
6
Process Overview Expert Analyst Conducts Full Form Analysis
7
Process Overview Full Form & Abbreviated Processing is completed
ID Strips are returned Records are quality checked Automated update is completed to DBQT Every 30 days DBQT is updated with completed records that have a minimum of 60 days from Date of Receipt
8
DBQT Development
9
DBQT Development December Designed the User Interface (UI) and wrote requirements Quarter 1 of 2016 – Developed DBQT Launched beta version in March 2016 Available now to C3RS stakeholders via username and password using a secure website hosted at NASA C3RS
10
DBQT Login username: c3rssafety16 password:
11
DBQT Development Built with the latest technology for speed and efficiency Front-end is built in AngularJS and HTML5 Backend is Python / Django web framework and PostgreSQL database
12
Features
13
Features - Search Web Based (any browser)
Password controlled access to the site Easy to use interface that allows search criteria on left side (accordions) and results to display on the right side (same page) Search for C3RS reports using common criteria Export is available in CSV, Microsoft Excel and Word compatible format
14
Features - Export You may choose to export, and then save and/or print, the records in: Comma Separated Value (.csv) - The .csv export generates one row for each incident record. Microsoft Excel® (.xls) - The .xls export generates one row for each incident record. Microsoft Word® (.doc) - The content of the .doc file will closely match the format of the on-screen view of incident records.
15
Features – About and Help Sections
Information and help is available New Users Program Summary About C3RS Data Multiple Report Handling, Confidentiality C3RS Coding Form (PDF) is available
16
Features – Result Display
Number of records per page (10, 20, or 50) Synopsis Only view - only the report number (ACN) and the synopsis will show for each record. This gives you the ability to quickly scan the type of incident records that were from your search. Full record view – all available data will show for each record (highest to lowest) Note: The view you are in (synopsis or full records) will be the data that exports.
17
Results Display The count of how many records were returned in your search results will display at the top of the search page. The search criteria used in the search to obtain the displayed results can be viewed and printed by clicking on the Current Search Criteria button. By default the results will show up to 10 records per page. You have the option to change the results to show 20 or 50 records per page. There is a Synopsis Only view in which only the report number (ACN) and the synopsis will show for each record, giving you the ability to quickly scan the type of incident records that were returned from your search. The results of your search display in HTML format, sorted by report number (ACN) from highest to lowest.
18
DBQT Demo
19
Login for DBQT
20
Main Search Page
21
Export Drop Down
22
DBQT Demo – Search Example
Search Example 1 – Scenario An Assistant Conductor has been on a yard job for 3 years. Last week, the train crew was given a move to wye a train and the Assistant Conductor was riding the point. The Conductor told the Assistant Conductor they were all lined up, but the Assistant Conductor was unaware that another train had taken their lineup away and had not lined the switch back for their movement. The combination of not knowing about this train and poor lighting contributed to this incident. The Assistant Conductor is curious to see how many other people have experienced having their lineup taken away and not being notified that it was changed.
23
DBQT Demo – Search Example
Search Example 1 – Search Criteria Train / Equipment = Type of Operation: Yard Assignment Train / Equipment = Rules in Effect: Other Than Main Track Rules Train / Equipment = Train / Equipment Location: Yard Event Type = Encounter: Misaligned Switch Event Result = Transportation: Run Through Switch Contributing Factors = Human Factors
24
DBQT Demo – Search Example
Search Example 2 – Scenario An extra board Engineer who has 4 years of experience working on a familiar territory was approaching a Permanent Speed Restriction. All signs were visible and properly placed. He was contacted by the Train Dispatcher inquiring about the equipment on his train. During the conversation with the Dispatcher, he became distracted by the radio communication and applied the brakes a little too late, exceeding Maximum Authorized Speed. He realized his loss of situational awareness allowed this to happen. He is interested in how many C3RS over speed reports are related to distraction and situational awareness.
25
DBQT Demo – Search Example
Search Example 2 – Search Criteria Train / Equipment = Type of Operation: Passenger/Commuter Train / Equipment = Train / Equipment Location: Main Track Train / Equipment = Speed Restriction: (All) - Maximum Authorized Speed, Equipment Based Speed Restriction, Permanent Speed Restriction, Temperature Based Speed Restriction, Temporary Speed Restriction Person = Human Factors: Distraction, Situational Awareness Event Type = Procedural Deviation: Operations Policy Event Type = Speed Deviation: (All) - Maximum Authorized Speed, Temporary Speed Restriction, At or Above 10 MPH Deviation, Equipment Based Speed Restriction Event Result = Slowing of Train/Equipment, No Action Taken, Returned to Compliance Contributing Factors = Human Factors
26
Future Update
27
DBQT Future Update DBQT will soon include triaged records
Full Form Records with Callback Full Form Records without a Callback Abbreviated Records
28
DBQT Future Update
29
DBQT Future Update
30
DBQT Future Update
31
DBQT Future Update
32
DBQT Future Update
33
Elisa Marfise, Booz Allen Hamilton
Questions? Elisa Marfise, Booz Allen Hamilton Human Factors Manager (408) Linda Connell, NASA ASRS/C3RS Program Director (408)
Similar presentations
© 2025 SlidePlayer.com. Inc.
All rights reserved.