Merged PR 9870: Columns and table descriptions with tables schema

PR Summary:

Added client-shared database schema to the repository.

Included table-level descriptions for incident, apparatus, and personnel datasets (views as well).

Documented column-level metadata including data types and descriptions.

Related work items: #15799, #15800

data/rag_input_data/apparatus_columns_details.txt

@@ -0,0 +1,549 @@
+Column Name: incidentkey
+Description: The primary key for the incident table. This is a unique, system-generated 14-character identifier for every incident record. It serves as the fundamental link to all other related tables in the database, such as apparatus, personnel, and supplemental data. This value is used to join with the incident table to get incident-level details.
+Data Type: char(14), NOT NULL
+Examples: _4GR15262U_SMS, _4GR15HZEC_SMS, _4GR166YT7_SMS
+
+Column Name: apparatuskey
+Description: The primary key for the apparatus table. This is a unique, system-generated 14-character identifier for a specific apparatus response to an incident. It serves as the primary link between apparatus response records and personnel assignments.
+Data Type: char(14), NOT NULL
+Examples: _4GR15265W_SMS, _4GR15HZF7_SMS, _4GR166YUI_SMS
+
+Column Name: pslid
+Description: The primary key for the personnel table. This is a unique, system-generated identifier for each individual firefighter, officer, or other personnel member. This value is used to join with the personnel table for demographic and qualification details.
+Data Type: varchar(15), NOT NULL
+Examples: _1XL0XJ7VGDEFA, _26H0W4XBHCPAU, _2FW0KTEBFCPAU
+
+Column Name: personnelid
+Description: A unique, human-readable identifier for each individual. This number is likely used for payroll, internal tracking, and linking to other systems. It is distinct from the system-generated pslid and may correspond to employee or badge numbers.
+Data Type: int, NOT NULL
+Examples: 219, 378, 390, 337, 394
+
+Column Name: namefirst
+Description: The first name of the individual as stored in the personnel table. This is denormalized data from the personnel table for reporting convenience.
+Data Type: varchar(25), NOT NULL
+Examples: Dale, Brandon, Kyle, Andrew, Stephen
+
+Column Name: namemi
+Description: The middle initial of the individual as stored in the personnel table. May be blank or contain a space if no middle name is recorded.
+Data Type: varchar(2), NULLable
+Examples: E, A, S, M, R
+
+Column Name: namelast
+Description: The last name of the individual as stored in the personnel table.
+Data Type: varchar(25), NOT NULL
+Examples: Bryan, Davis, Coles, Puetz, Vizzard
+
+Column Name: namesuffix
+Description: A suffix for the individual's name, such as Jr., Sr., III. This field appears to be largely unused or NULL in the provided data.
+Data Type: varchar(6), NULLable
+Examples: NULL
+
+Column Name: namefirstlast
+Description: A concatenated field displaying the individual's first and last name (e.g., "First Last"). This is likely generated for display purposes.
+Data Type: varchar(51), NOT NULL
+Examples: Dale Bryan, Brandon Davis, Kyle Coles, Andrew Puetz
+
+Column Name: namelastfirst
+Description: A concatenated field displaying the individual's last name, then first name (e.g., "Last, First"). Used for alphabetical sorting and formal listings.
+Data Type: varchar(51), NOT NULL
+Examples: Bryan, Dale; Davis, Brandon; Coles, Kyle; Puetz, Andrew
+
+Column Name: namefull
+Description: A concatenated field displaying the individual's full name, typically formatted as "First Middle Last" or "First M. Last". This is used for formal display and official reports.
+Data Type: varchar(53), NOT NULL
+Examples: Dale E Bryan, Brandon A Davis, Kyle S Coles, Andrew M Puetz
+
+Column Name: rank
+Description: The rank code of the individual (e.g., CAPT, FF, ENG, BC). This indicates their role and seniority within the department and corresponds to a rank table in the database.
+Data Type: varchar(6), NOT NULL
+Examples: CAPT, FF, ENG, BC
+
+Column Name: actiontaken1code
+Description: A code representing the primary action taken by this personnel on the incident. This corresponds to the actiontaken1 field in the apparatus table and references a standardized list of NFIRS (National Fire Incident Reporting System) action codes.
+Data Type: varchar(4), NULLable
+Examples: 93, 86, 32, 31, (empty)
+
+Column Name: actiontaken1descip
+Description: A text description of the primary action taken, corresponding to actiontaken1code. Note the misspelling of "descrip" in the column header, which likely originates from a data export view.
+Data Type: varchar(100), NULLable
+Examples: Cancelled en route, Investigate, Provide basic life support (BLS), Provide first aid & check for injuries
+
+Column Name: actiontaken2code
+Description: A code representing a secondary action taken by this personnel on the incident, following NFIRS coding standards.
+Data Type: varchar(4), NULLable
+Examples: 31, 12, 86, (empty)
+
+Column Name: actiontaken2descip
+Description: A text description of the secondary action taken, corresponding to actiontaken2code.
+Data Type: varchar(100), NULLable
+Examples: Provide first aid & check for injuries, Salvage & overhaul, Investigate
+
+Column Name: actiontaken3code
+Description: A code representing a tertiary action taken by this personnel on the incident, following NFIRS coding standards.
+Data Type: varchar(4), NULLable
+Examples: 86, 82, (empty)
+
+Column Name: actiontaken3descip
+Description: A text description of the tertiary action taken, corresponding to actiontaken3code.
+Data Type: varchar(100), NULLable
+Examples: Investigate, Notify other agencies.
+
+Column Name: actiontaken4code
+Description: A code representing a quaternary action taken by this personnel on the incident, following NFIRS coding standards.
+Data Type: varchar(4), NULLable
+Examples: (empty)
+
+Column Name: actiontaken4descip
+Description: A text description of the quaternary action taken, corresponding to actiontaken4code.
+Data Type: varchar(100), NULLable
+Examples: (empty)
+
+Column Name: amount1
+Description: A monetary value field from the apparatus table. In NFIRS reporting, this may represent dollar amounts for property loss, equipment value, or other financial metrics. The specific meaning depends on the context of the action taken.
+Data Type: money, NULLable
+Examples: NULL, 1
+
+Column Name: amount2
+Description: A second monetary value field from the apparatus table. May represent additional financial data such as property saved, contents value, or other monetary metrics.
+Data Type: money, NULLable
+Examples: NULL, 1
+
+Column Name: crole
+Description: Likely indicates the "credit role" or a specific assignment type for the personnel. The meaning is unclear from the data but often contains "NULL". May relate to NFIRS crew role designations.
+Data Type: varchar(4), NULLable
+Examples: NULL
+
+Column Name: losapcreditcode
+Description: A code indicating if the personnel received LOSAP (Length of Service Award Program) credit for this incident. LOSAP is a program that provides retirement or service awards to volunteer firefighters.
+Data Type: int, NULLable
+Examples: 1, (empty)
+
+Column Name: losapcreditdescrip
+Description: A text description of the LOSAP credit status, corresponding to losapcreditcode. Values are consistently "Losap Credit".
+Data Type: varchar(20), NULLable
+Examples: Losap Credit
+
+Column Name: incidentkey (duplicate)
+Description: This appears to be a duplicate of the main incidentkey column, possibly included due to a data join or export from a denormalized view that includes both incident and apparatus tables.
+Data Type: char(14), NOT NULL
+Examples: _4GR15262U_SMS, _4GR15HZEC_SMS
+
+Column Name: apparatuskey (duplicate)
+Description: This appears to be a duplicate of the main apparatuskey column, likely included from the apparatus table when joining personnel assignment data.
+Data Type: char(14), NOT NULL
+Examples: _4GR15265W_SMS, _4GR15HZF7_SMS
+
+Column Name: apparatusid
+Description: The public-facing identifier or "unit number" for the apparatus (e.g., "BE7", "BE6", "BE3"). This is what is used in radio communications and official logs to refer to a specific vehicle or unit. Stored as char(8) in the schema.
+Data Type: char(8), NOT NULL
+Examples: BE7, BE6, BE3, BE14, BTK7, BE13, BE5
+
+Column Name: deptunitornotcode
+Description: A code indicating whether the apparatus is a department unit or some other type of resource. A value of "0" seems consistent. In the schema, this might correspond to a flag indicating unit type.
+Data Type: int, NOT NULL
+Examples: 0
+
+Column Name: deptunitornotdescrip
+Description: A text description of the apparatus type, corresponding to deptunitornotcode. The value "DeptUnit" suggests it is a standard department unit.
+Data Type: varchar(10), NOT NULL
+Examples: DeptUnit
+
+Column Name: priorityresponsecode
+Description: A code indicating the priority level of the response for this apparatus. A value of "1" likely indicates the highest priority. This corresponds to the priorityresponseflag bit field in the apparatus table.
+Data Type: int, NOT NULL
+Examples: 1
+
+Column Name: priorityresponsedescrip
+Description: A text description of the response priority. "Yes" may indicate it was a priority response (lights and sirens).
+Data Type: varchar(5), NOT NULL
+Examples: Yes
+
+Column Name: cancelledenroutecode
+Description: A code indicating whether the apparatus was cancelled while en route to the incident. Corresponds to the cancelledenrouteflag bit field in the apparatus table.
+Data Type: int, NOT NULL
+Examples: 0, 1
+
+Column Name: cancelledenroutedescrip
+Description: A text description of the cancellation status. "No" means not cancelled, "Yes" means cancelled en route.
+Data Type: varchar(5), NOT NULL
+Examples: No, Yes
+
+Column Name: firstarrivingunitcode
+Description: A code indicating whether this apparatus was the first to arrive at the scene. Corresponds to the firstarrivingunit field in the apparatus table, which uses the udtlogical data type.
+Data Type: int, NOT NULL
+Examples: 1, 0
+
+Column Name: firstarrivingunitdescrip
+Description: A text description of the first-arriving status. "Yes" indicates it was the first unit, "No" indicates it was not.
+Data Type: varchar(5), NOT NULL
+Examples: Yes, No
+
+Column Name: dispatchtype
+Description: A code representing the type of dispatch for this apparatus. Often NULL or "NULL". This may correspond to a dispatch code table.
+Data Type: varchar(4), NULLable
+Examples: NULL
+
+Column Name: dispatchtypedescrip
+Description: A text description of the dispatch type. Often NULL or empty.
+Data Type: varchar(30), NULLable
+Examples: (empty)
+
+Column Name: respondedfromquarterscode
+Description: A code indicating whether the apparatus responded directly from its quarters (station) or from another location. Corresponds to the respondfromquarters field in the apparatus table, which uses the udtlogical data type.
+Data Type: int, NOT NULL
+Examples: 0
+
+Column Name: respondedfromquarterdescrip
+Description: A text description of the response origin. "No" may indicate it did not respond from quarters (e.g., was already on the road or at another location).
+Data Type: varchar(5), NOT NULL
+Examples: No
+
+Column Name: mainapparatususecode
+Description: A code indicating if this was the main apparatus used for the incident. This likely corresponds to the usecode field in the apparatus table.
+Data Type: int, NOT NULL
+Examples: 1, 0
+
+Column Name: mainapparatususedescrip
+Description: A text description of the main apparatus status. "Suppression" is common for fire suppression units, "Chief officer car" for command vehicles.
+Data Type: varchar(30), NOT NULL
+Examples: Suppression, Chief officer car
+
+Column Name: apparatustypecode
+Description: A code representing the type of apparatus (e.g., engine, truck, chief's car). Corresponds to the apparatustype field in the apparatus table, which references a standard NFIRS apparatus type code.
+Data Type: int, NOT NULL
+Examples: 11, 12, 92, 0
+
+Column Name: apparatustypedescrip
+Description: A text description of the apparatus type, corresponding to apparatustypecode. Based on NFIRS standard descriptions.
+Data Type: varchar(40), NOT NULL
+Examples: Engine, Truck or aerial, Chief officer car, Other apparatus/resource
+
+Column Name: actiontaken1code (duplicate)
+Description: A duplicate column, representing the primary action taken by the apparatus as a whole. This corresponds to the actiontaken1 field in the apparatus table and follows NFIRS coding standards.
+Data Type: varchar(4), NULLable
+Examples: 93, 86, 32, 31
+
+Column Name: actiontaken1descip (duplicate)
+Description: A duplicate text description of the primary action taken by the apparatus.
+Data Type: varchar(100), NULLable
+Examples: Cancelled en route, Investigate, Provide basic life support (BLS)
+
+Column Name: actiontaken2code (duplicate)
+Description: A duplicate column for a secondary action taken by the apparatus. Corresponds to actiontaken2 in the apparatus table.
+Data Type: varchar(4), NULLable
+Examples: 31, 12, 86
+
+Column Name: actiontaken2descip (duplicate)
+Description: A duplicate text description of the secondary action taken by the apparatus.
+Data Type: varchar(100), NULLable
+Examples: Provide first aid & check for injuries, Salvage & overhaul, Investigate
+
+Column Name: actiontaken3code (duplicate)
+Description: A duplicate column for a tertiary action taken by the apparatus. Corresponds to actiontaken3 in the apparatus table.
+Data Type: varchar(4), NULLable
+Examples: 86, 82
+
+Column Name: actiontaken3descip (duplicate)
+Description: A duplicate text description of the tertiary action taken by the apparatus.
+Data Type: varchar(100), NULLable
+Examples: Investigate, Notify other agencies.
+
+Column Name: actiontaken4code (duplicate)
+Description: A duplicate column for a quaternary action taken by the apparatus. Corresponds to actiontaken4 in the apparatus table.
+Data Type: varchar(4), NULLable
+Examples: (empty)
+
+Column Name: actiontaken4descip (duplicate)
+Description: A duplicate text description of the quaternary action taken by the apparatus.
+Data Type: varchar(100), NULLable
+Examples: (empty)
+
+Column Name: numberofresponders
+Description: The number of personnel who responded on this apparatus. This corresponds to the numberpeople field in the apparatus table. Note that this value is repeated for each personnel row, indicating data redundancy in this export.
+Data Type: int, NOT NULL
+Examples: 3, 4, 2, 0, 1
+
+Column Name: dispatchdatetime
+Description: The full date and time when the apparatus was dispatched. Corresponds to the dispatchdate field in the apparatus table.
+Data Type: datetime, NOT NULL
+Examples: 08:31.0 10/9/2015, 20:21.0 10/9/2015, 39:16.0 10/9/2015
+
+Column Name: dispatchtime
+Description: The time component of the dispatch, likely extracted for reporting convenience.
+Data Type: time, NOT NULL
+Examples: 19:08:31, 19:20:21, 19:39:16
+
+Column Name: dispatchdate
+Description: The date component of the dispatch, likely extracted for reporting convenience.
+Data Type: date, NOT NULL
+Examples: 10/9/2015, 10/10/2015
+
+Column Name: dispatchenroutetime
+Description: The date and time when the apparatus acknowledged dispatch and began moving en route to the scene. This corresponds to the enroutedate field in the apparatus table. NULL if cancelled before en route.
+Data Type: datetime, NULLable
+Examples: 09:15.0 10/9/2015, 21:36.0 10/9/2015, (empty)
+
+Column Name: dispatchenroutediffseconds
+Description: The difference in seconds between dispatch time and en route time. This represents the time it took for the unit to get moving (turnout time).
+Data Type: int, NULLable
+Examples: 44, 75, (empty)
+
+Column Name: enroutetoscenedatetime
+Description: The date and time when the apparatus began traveling from its current location to the scene. Often identical to or very close to dispatchenroutetime. Corresponds to the enroutedate field.
+Data Type: datetime, NULLable
+Examples: 09:15.0 10/9/2015, 21:36.0 10/9/2015
+
+Column Name: enroutetoscenetime
+Description: The time component of enroutetoscenedatetime.
+Data Type: time, NULLable
+Examples: 19:09:15, 19:21:36
+
+Column Name: enroutetoscenedate
+Description: The date component of enroutetoscenedatetime.
+Data Type: date, NULLable
+Examples: 10/9/2015
+
+Column Name: enroutearrivalscenetime
+Description: This column header appears to be a misnomer. Based on the data, it likely represents the difference between en route time and arrival time. This is calculated as a time interval.
+Data Type: varchar(10), NULLable
+Examples: 0:01:55, 0:03:37, (empty)
+
+Column Name: enroutearrivalscenediffseconds
+Description: The difference in seconds between en route time and arrival time. This is the travel time to the scene.
+Data Type: int, NULLable
+Examples: 115, 217, (empty)
+
+Column Name: responsetime
+Description: The total time from dispatch to arrival on scene, formatted as HH:MM:SS. This is likely calculated as a reporting field.
+Data Type: varchar(10), NULLable
+Examples: 0:02:39, 0:04:52, (empty)
+
+Column Name: responsetimeseconds
+Description: The total time from dispatch to arrival on scene, expressed in seconds.
+Data Type: int, NULLable
+Examples: 159, 292, (empty)
+
+Column Name: arrivaldatetime
+Description: The full date and time when the apparatus arrived at the scene of the incident. Corresponds to the arrivaldate field in the apparatus table.
+Data Type: datetime, NULLable
+Examples: 11:10.0 10/9/2015, 25:13.0 10/9/2015, (empty)
+
+Column Name: arrivaltime
+Description: The time component of the arrival.
+Data Type: time, NULLable
+Examples: 19:11:10, 19:25:13
+
+Column Name: arrivaldate
+Description: The date component of the arrival.
+Data Type: date, NULLable
+Examples: 10/9/2015
+
+Column Name: arrivaltoenroutehospdifftime
+Description: Time difference between arrival at scene and en route to hospital. This would represent on-scene time before transporting a patient. Typically NULL for non-EMS runs.
+Data Type: varchar(10), NULLable
+Examples: NULL
+
+Column Name: arrivaltoenroutehospdiffseconds
+Description: The difference in seconds between arrival at scene and en route to hospital.
+Data Type: int, NULLable
+Examples: 0
+
+Column Name: enroutetohospitaldatetime
+Description: The date and time when the apparatus began en route to the hospital with a patient. This would correspond to a hospital transport leg. Typically NULL for non-EMS runs.
+Data Type: datetime, NULLable
+Examples: 00:00.0, (empty)
+
+Column Name: enroutetohospitaltime
+Description: The time component of enroutetohospitaldatetime.
+Data Type: time, NULLable
+Examples: (empty)
+
+Column Name: enroutetohospitaldate
+Description: The date component of enroutetohospitaldatetime.
+Data Type: date, NULLable
+Examples: (empty)
+
+Column Name: enroutetoarrivalhospdifftime
+Description: Time difference between en route to hospital and arrival at hospital. This represents transport time to the medical facility.
+Data Type: varchar(10), NULLable
+Examples: NULL
+
+Column Name: enroutetoarrivalhospdiffseconds
+Description: The difference in seconds between en route to hospital and arrival at hospital.
+Data Type: int, NULLable
+Examples: 0
+
+Column Name: arrivalscenetoarrivalhospdifftime
+Description: Time difference between arrival at scene and arrival at hospital. This is the total time spent on scene before leaving for the hospital plus transport time.
+Data Type: varchar(10), NULLable
+Examples: NULL
+
+Column Name: arrivalscenetoarrivalhospdiffseconds
+Description: The difference in seconds between arrival at scene and arrival at hospital.
+Data Type: int, NULLable
+Examples: 0
+
+Column Name: hospitalarrivaldatetime
+Description: The full date and time when the apparatus arrived at the hospital. Corresponds to the FACILITYDATE field in the apparatus table. Typically NULL for non-EMS runs.
+Data Type: datetime, NULLable
+Examples: 00:00.0, (empty)
+
+Column Name: hospitalarrivaltime
+Description: The time component of hospitalarrivaldatetime.
+Data Type: time, NULLable
+Examples: (empty)
+
+Column Name: hospitalarrivaldate
+Description: The date component of hospitalarrivaldatetime.
+Data Type: date, NULLable
+Examples: (empty)
+
+Column Name: arrivalclearhospdifftime
+Description: Time difference between arrival at hospital and clearing from the hospital (becoming available). This represents time spent at the hospital transferring patient care and completing paperwork.
+Data Type: varchar(10), NULLable
+Examples: NULL
+
+Column Name: arrivalclearhospdiffseconds
+Description: The difference in seconds between arrival at hospital and clearing from the hospital.
+Data Type: int, NULLable
+Examples: 0
+
+Column Name: cleardatetime
+Description: The full date and time when the apparatus cleared the incident and became available for another call. Corresponds to the cleardate field in the apparatus table.
+Data Type: datetime, NULLable
+Examples: 16:17.0 10/9/2015, 40:39.0 10/9/2015, 41:06.0 10/9/2015
+
+Column Name: cleartime
+Description: The time component of the clear time.
+Data Type: time, NULLable
+Examples: 19:16:17, 19:40:39, 19:41:06
+
+Column Name: cleardate
+Description: The date component of the clear time.
+Data Type: date, NULLable
+Examples: 10/9/2015, 10/10/2015
+
+Column Name: dispatchcleardifftime
+Description: The total time from dispatch to clear, formatted as HH:MM:SS. This is the total time the unit was committed to the incident.
+Data Type: varchar(10), NULLable
+Examples: 0:07:46, 0:20:18, 0:01:50
+
+Column Name: dispatchcleardiffseconds
+Description: The total time from dispatch to clear, expressed in seconds.
+Data Type: int, NULLable
+Examples: 466, 1218, 110
+
+Column Name: inservicedatetime
+Description: The date and time when the apparatus returned to service/in quarters and was marked as available. Corresponds to the inservicedate and inservicetime fields in the apparatus table. Often 00:00.0, suggesting it may not be consistently populated.
+Data Type: datetime, NULLable
+Examples: 00:00.0, (empty)
+
+Column Name: inservicetime
+Description: The time component of inservicedatetime.
+Data Type: time, NULLable
+Examples: (empty)
+
+Column Name: inservicedate
+Description: The date component of inservicedatetime.
+Data Type: date, NULLable
+Examples: (empty)
+
+Column Name: emsruncode
+Description: A code indicating whether this was an EMS (Emergency Medical Services) run. "Not EMS Run" appears as text in this code field, which may be a display value rather than the actual stored code.
+Data Type: varchar(15), NULLable
+Examples: Not EMS Run, (empty)
+
+Column Name: emsrundescrip
+Description: A text description of the EMS run status. This field is often NULL. May correspond to the emsrun bit field in the apparatus table.
+Data Type: varchar(40), NULLable
+Examples: NULL
+
+Column Name: emsrunnumber
+Description: A number associated with the EMS run, likely a sequential identifier for the patient care report. Corresponds to the emsrunnumber field in the apparatus table. Often NULL for non-EMS runs.
+Data Type: varchar(14), NULLable
+Examples: NULL
+
+Column Name: losapcode
+Description: A code indicating if the apparatus or its personnel received LOSAP credit. Corresponds to the lLosap_credit bit field in the apparatus table. Often 1, corresponding to the description.
+Data Type: int, NULLable
+Examples: 1
+
+Column Name: losapdescrip
+Description: A text description of the LOSAP credit status. "Losap Credit" is the common value.
+Data Type: varchar(20), NULLable
+Examples: Losap Credit
+
+Column Name: alarmscode
+Description: A code related to the alarm level or type. Corresponds to the alarms field in the apparatus table, which is char(10). Often NULL.
+Data Type: int, NULLable
+Examples: NULL
+
+Column Name: alarmdescrip
+Description: A text description of the alarm level. Often NULL.
+Data Type: varchar(30), NULLable
+Examples: NULL
+
+Column Name: amount1 (duplicate)
+Description: Another duplicate of the amount1 field, likely for apparatus-level monetary data.
+Data Type: money, NULLable
+Examples: NULL
+
+Column Name: amount2 (duplicate)
+Description: Another duplicate of the amount2 field, likely for apparatus-level monetary data.
+Data Type: money, NULLable
+Examples: NULL
+
+Column Name: fdid_no
+Description: Fire Department ID Number - a unique identifier for the fire department. This field is consistently NULL in the sample data but corresponds to the fdid_no field in the apparatus table using the udtfdid data type.
+Data Type: udtfdid (custom data type), NULLable
+Examples: NULL
+
+Column Name: stagingdatetime
+Description: The date and time when the apparatus was placed in a staging area. Corresponds to the stagingDate field in the apparatus table. Often NULL or zero values.
+Data Type: datetime, NULLable
+Examples: 00:00.0, (empty)
+
+Column Name: stagingtime
+Description: The time component of stagingdatetime.
+Data Type: time, NULLable
+Examples: (empty)
+
+Column Name: stagingdate
+Description: The date component of stagingdatetime.
+Data Type: date, NULLable
+Examples: (empty)
+
+Column Name: AtPatientSideDateTime
+Description: The date and time when personnel reached the patient's side. This field is specific to medical calls and corresponds to the AtPatientSideTime field in the apparatus table. Often NULL or zero.
+Data Type: datetime, NULLable
+Examples: 00:00.0, (empty)
+
+Column Name: AtPatientSideTime
+Description: The time component of AtPatientSideDateTime.
+Data Type: time, NULLable
+Examples: (empty)
+
+Column Name: AtPatientSideDate
+Description: The date component of AtPatientSideDateTime.
+Data Type: date, NULLable
+Examples: (empty)
+
+Column Name: FacilityDateTime
+Description: The date and time when the patient was transferred to a medical facility. Corresponds to the FACILITYDATE field in the apparatus table. Often NULL or zero.
+Data Type: datetime, NULLable
+Examples: 00:00.0, (empty)
+
+Column Name: FacilityTime
+Description: The time component of FacilityDateTime.
+Data Type: time, NULLable
+Examples: (empty)
+
+Column Name: FacilityDate
+Description: The date component of FacilityDateTime.
+Data Type: date, NULLable
+Examples: (empty)
+
+Column Name: changedate
+Description: A timestamp indicating the last time this record was modified in the source system. The format in the export appears to be minutes and seconds past midnight (e.g., 17:39.0 = 17 minutes and 39 seconds past midnight). In the schema, this is a datetime field.
+Data Type: datetime, NOT NULL
+Examples: 17:39.0, 42:11.5, 48:24.5, 57:38.2

data/rag_input_data/apparatus_table_details.txt

@@ -0,0 +1,19 @@
+Table Name: apparatus
+
+This table represents a denormalized operational dataset that combines incident, apparatus response, and personnel participation details for emergency response events. Each row typically corresponds to a specific personnel member assigned to a particular apparatus responding to an incident. Because of this structure, incident-level and apparatus-level data may repeat across multiple rows when multiple responders are involved in the same response unit.
+
+The dataset links three core operational entities: incidents, apparatus units, and personnel. The incident identifier serves as the primary reference to the emergency event itself, while the apparatus identifier represents the responding vehicle or resource unit. Personnel identifiers represent the firefighters, officers, or responders assigned to that apparatus during the incident. This structure allows the dataset to capture the full relationship between responders, equipment, and the incident event.
+
+Operational details in the table include responder information such as personnel names, ranks, and role-related attributes. It also contains standardized action codes describing the actions performed during the response. These action codes follow the NFIRS (National Fire Incident Reporting System) standards, which classify operational activities such as investigations, medical assistance, suppression, or cancellations.
+
+The dataset also includes apparatus-level operational attributes such as apparatus identifiers, apparatus type, response priority, dispatch type, cancellation status, and whether the unit was the first arriving resource. These attributes help describe how each unit participated in the response and what role it played in the overall incident management.
+
+Another major component of the dataset is the detailed response timeline. Multiple timestamps track the lifecycle of a response, including dispatch time, en route time, arrival on scene, hospital transport events, and the time when the unit cleared the incident and returned to service. Derived duration fields calculate response metrics such as turnout time, travel time to the scene, total response time, and total committed time for the apparatus.
+
+For incidents involving emergency medical services (EMS), the table also includes patient care milestones such as arrival at patient side, en route to hospital, and arrival at a medical facility. These timestamps help measure EMS operational performance and patient transport timelines.
+
+Financial or administrative metrics may also appear in the dataset, including monetary amount fields and LOSAP (Length of Service Award Program) credit indicators used for volunteer firefighter service recognition. These fields provide additional operational and administrative context for the response.
+
+Because the table appears to originate from a reporting view or export, several columns are duplicated from related entities such as apparatus actions or financial values. These duplicates exist to simplify reporting and reduce the need for additional joins when generating analytics, reports, or operational summaries.
+
+Overall, this dataset functions as a comprehensive response activity record that captures incident context, apparatus deployment details, personnel assignments, operational actions, and the full response timeline. It is particularly useful for operational analytics, response time analysis, personnel participation tracking, and emergency service performance reporting.

data/rag_input_data/incident_columns_details.txt

@@ -0,0 +1,794 @@
+Column Name: incidentkey
+Description: The primary key for the incident table. This is a unique, system-generated 14-character identifier for every incident record. It serves as the fundamental link to all other related tables in the database, such as apparatus, personnel, and supplemental data.
+Data Type: char(14), NOT NULL
+Examples: _48Y00K5I8_SMS, _48Y00K5IA_SMS, _48Y00JH1N_SMS
+
+Column Name: incidentdate
+Description: The official date and time of the incident. This field is often populated by the CAD (Computer-Aided Dispatch) system (referred to as ZMS in the extended properties). It typically represents the same moment as the alarm date and time.
+Data Type: datetime, NULLable
+Examples: 08:50.0 1/1/2015, 09:25.0 1/1/2015
+
+Column Name: incidentnumber
+Description: The public-facing, human-readable number assigned to the incident. This is the number used for official records, reports, and public inquiries. Multiple records (e.g., for different apparatus or exposures) may share the same incident number.
+Data Type: char(10), NULLable
+Examples: 1500003, 1500004, 1500002
+
+Column Name: exposure
+Description: The exposure number for the incident. An exposure is a separate incident, often a fire, that is caused by or related to a primary incident (e.g., a fire spreading to a neighboring building). A value of '0' or blank typically indicates the primary incident.
+Data Type: char(3), NULLable
+Examples: 0
+
+Column Name: incidentstatus
+Description: A status field that, combined with the incident number, can indicate the number of this supplemental record. Its precise use is not fully detailed in the provided schema, but it likely tracks the state of the incident report itself.
+Data Type: char(20), NULLable
+Examples: (mostly empty in sample)
+
+Column Name: reviewstatusflag
+Description: A boolean flag indicating whether the incident report has undergone an official review. A value of 0 means 'Not Reviewed', and a value of 1 means 'Reviewed'. This is a key part of the quality assurance process.
+Data Type: bit, NOT NULL (Default 0)
+Examples: 0, 1
+
+Column Name: publicreleaseflag
+Description: A boolean flag indicating if the incident report has been approved for release to the public, media, or other external requestors. A value of 0 means 'Not Released', and a value of 1 means 'Released'.
+Data Type: bit, NOT NULL (Default 0)
+Examples: 0
+
+Column Name: completed
+Description: A boolean flag indicating if all data entry for the incident report is considered complete. A value of 0 means 'Not Completed', and a value of 1 means 'Completed'. This helps manage workflow and reporting.
+Data Type: bit, NOT NULL (Default 0)
+Examples: 1
+
+Column Name: transactiontype
+Description: A code used internally, likely for data synchronization or replication purposes. It indicates the type of transaction, such as a new record (blank or 'A'), an edit ('1'), a delete ('2'), or 'None' ('3').
+Data Type: char(4), NULLable
+Examples: (blank in sample)
+
+Column Name: district
+Description: The identifier for the fire district or geographic zone in which the incident occurred. This is used for resource allocation, performance analysis, and administrative purposes.
+Data Type: char(10), NULLable
+Examples: B07, B04, 67, B08
+
+Column Name: station
+Description: The identifier or designation of the primary fire station responsible for the incident's district. This field is often populated based on the district.
+Data Type: char(30), NULLable (Default '')
+Examples: B7, 4, K65, B1
+
+Column Name: shift
+Description: The code for the duty shift that was on duty at the time of the incident (e.g., A, B, C). This is used for personnel tracking and resource management.
+Data Type: char(2), NULLable (Default '')
+Examples: B, A, C
+
+Column Name: company
+Description: This field is noted in the extended properties as 'Not Used'. It is likely a legacy field or reserved for future functionality.
+Data Type: char(64), NULLable
+Examples: (mostly empty)
+
+Column Name: incidenttype
+Description: A crucial classification code for the incident, based on standards like the National Fire Incident Reporting System (NFIRS). It defines the nature of the incident, such as a fire, EMS call, or hazardous condition. The corresponding description can be found by joining to the `codes901` table where `category = 'incident'`.
+Data Type: char(4), NOT NULL (Default '')
+Examples: 243, 2430, 321, 6111
+
+Column Name: initialdispatchcode
+Description: The code that was used by the dispatch center when resources were first sent to the incident. This may be a more specific or initial assessment code compared to the final `incidenttype`.
+Data Type: varchar(25), NULLable
+Examples: FWX, MA, FST
+
+Column Name: mutualaidcode
+Description: A code indicating the type of mutual aid provided or received, if any. Standard codes can be found in the `codes901` table under the `category = 'aid'`. Common examples include 'N' for None, '4' for Automatic Aid Given, and '2' for Automatic Aid Received.
+Data Type: char(4), NOT NULL (Default '')
+Examples: N, 4, 2
+
+Column Name: alarmdate
+Description: The date and time when the initial alarm was first received, marking the official start of the incident response.
+Data Type: datetime, NULLable (Default '')
+Examples: 08:50.0 1/1/2015, 09:25.0 1/1/2015
+
+Column Name: arrivaldate
+Description: The date and time when the first responding unit arrived on the scene of the incident. This is a critical performance metric.
+Data Type: datetime, NULLable
+Examples: 16:56.0 1/1/2015, 14:44.0 1/1/2015
+
+Column Name: didnotarriveflag
+Description: A boolean flag set to '1' if the responding unit(s) were cancelled en route and did not actually arrive at the incident location. A value of '0' indicates they did arrive.
+Data Type: bit, NOT NULL (Default 0)
+Examples: 0, 1
+
+Column Name: controlleddate
+Description: The date and time when the incident was declared "under control". For fires, this might be when the main body of the fire was knocked down. This field may be left blank for non-fire incidents like EMS calls.
+Data Type: datetime, NULLable
+Examples: 00:00.0 (mostly empty)
+
+Column Name: lastunitcleareddate
+Description: The date and time when the last fire department unit left the scene and became available for another call. This marks the official end of the incident response.
+Data Type: datetime, NULLable
+Examples: 25:33.0 1/1/2015, 22:25.0 1/1/2015
+
+Column Name: includemutualaidflag
+Description: A boolean flag indicating whether any mutual aid resources were included in the response. A value of '1' typically means 'Yes' (mutual aid was involved), while '0' means 'No'.
+Data Type: bit, NOT NULL (Default 0)
+Examples: 0, 1
+
+Column Name: madepartment
+Description: The name or identifier of the mutual aid department that responded, if mutual aid was provided or received.
+Data Type: char(30), NULLable
+Examples: (blank in sample)
+
+Column Name: madeptincidentno
+Description: The incident number assigned by the mutual aid department to this same incident, used for their own record-keeping and cross-referencing.
+Data Type: char(9), NULLable
+Examples: 1500009, 1500038, 1500050
+
+Column Name: alarms
+Description: The number of alarms sounded for this incident. A higher number of alarms (e.g., 2nd, 3rd, 4th alarm) indicates a larger, more resource-intensive incident that required more units to be called in.
+Data Type: int, NULLable
+Examples: 1
+
+Column Name: actiontaken1
+Description: A code representing the primary action taken by fire department personnel at the scene. Descriptions for these codes are stored in the `codes901` table with a `category = 'action'`.
+Data Type: char(4), NULLable
+Examples: 86, 32, 93, 80
+
+Column Name: actiontaken2
+Description: A code representing a secondary action taken at the scene, if applicable.
+Data Type: char(4), NULLable
+Examples: 85, 0, 93, 73
+
+Column Name: actiontaken3
+Description: A code representing a tertiary action taken at the scene, if applicable.
+Data Type: char(4), NULLable
+Examples: (often blank), 93
+
+Column Name: resourceformusedflag
+Description: This field is noted in the extended properties as 'Not Used'. It is likely a legacy field.
+Data Type: bit, NOT NULL (Default 0)
+Examples: (likely 0)
+
+Column Name: apparatussuppression
+Description: A summary count of the total number of fire suppression apparatus (e.g., engines, trucks, quints) from the reporting department that responded to the incident.
+Data Type: int, NULLable (Default 0)
+Examples: 1, 3, 4, 5
+
+Column Name: apparatusems
+Description: A summary count of the total number of EMS apparatus (e.g., ambulances, medic units) from the reporting department that responded to the incident.
+Data Type: int, NULLable (Default 0)
+Examples: 0, 1
+
+Column Name: apparatusother
+Description: A summary count of any other apparatus from the reporting department that responded, such as command vehicles, air units, or support units.
+Data Type: int, NULLable (Default 0)
+Examples: 0
+
+Column Name: personnelsuppression
+Description: A summary count of the total number of suppression personnel from the reporting department who responded to the incident.
+Data Type: int, NULLable (Default 0)
+Examples: 3, 7, 11, 14
+
+Column Name: personnelems
+Description: A summary count of the total number of EMS personnel from the reporting department who responded to the incident.
+Data Type: int, NULLable (Default 0)
+Examples: 0
+
+Column Name: personnelother
+Description: A summary count of any other personnel from the reporting department who responded.
+Data Type: int, NULLable (Default 0)
+Examples: 0
+
+Column Name: lossproperty
+Description: The estimated dollar amount of loss or damage to the property itself, as a direct result of the incident (e.g., fire damage to a building).
+Data Type: money, NULLable
+Examples: 500, 6000, 20000, 30000, NULL
+
+Column Name: losscontents
+Description: The estimated dollar amount of loss or damage to the contents within the property (e.g., furniture, inventory, personal belongings).
+Data Type: money, NULLable
+Examples: 200, 1000, 500, 2500, NULL
+
+Column Name: valueproperty
+Description: The estimated total dollar value of the property *before* the incident occurred.
+Data Type: money, NULLable
+Examples: 500, 7000, 1000, 70000, NULL
+
+Column Name: valuecontents
+Description: The estimated total dollar value of the contents *before* the incident occurred.
+Data Type: money, NULLable
+Examples: 200, 500, 1000, 10000, NULL
+
+Column Name: fatalfireservice
+Description: The number of fatalities that occurred involving fire service personnel. A value of 0 indicates none.
+Data Type: int, NULLable (Default 0)
+Examples: 0, 1
+
+Column Name: fatalother
+Description: The number of fatalities that occurred involving civilians or other non-fire-service persons. A value of 0 indicates none.
+Data Type: int, NULLable (Default 0)
+Examples: 0, 1
+
+Column Name: nonfatalfireservice
+Description: The number of non-fatal injuries sustained by fire service personnel. A value of 0 indicates none.
+Data Type: int, NULLable (Default 0)
+Examples: 0
+
+Column Name: nonfatalother
+Description: The number of non-fatal injuries sustained by civilians or other non-fire-service persons. A value of 0 indicates none.
+Data Type: int, NULLable (Default 0)
+Examples: 0, 2
+
+Column Name: detector
+Description: A code indicating the performance and role of smoke or fire detection equipment. Lookup descriptions are in `codes901` with `category = 'det_alrt'`. Common values include 'U' for Unknown, '1' for Detector alerted occupants, and '2' for Detector did not alert occupants.
+Data Type: char(4), NULLable
+Examples: U, 1, 2
+
+Column Name: hazardmaterialreleased
+Description: A code indicating if hazardous materials were released during the incident. Lookup descriptions are in `codes901` with `category = 'haz_rel'`. A common value is 'U' for Unknown.
+Data Type: char(4), NULLable
+Examples: (mostly blank), U
+
+Column Name: mixeduse
+Description: A code indicating if the property involved in the incident had a mixed-use occupancy (e.g., residential above commercial). Lookup descriptions are in `codes901` with `category = 'mixeduse'`. '20' for example, represents 'Educational use' in the sample data.
+Data Type: char(4), NULLable
+Examples: (mostly blank), 20
+
+Column Name: propertyuse
+Description: A code classifying the primary use or occupancy of the property where the incident occurred, based on NFIRS standards. Lookup descriptions are in `codes901` with `category = 'prop_use'`.
+Data Type: char(4), NULLable
+Examples: 429, 419, 962, 311
+
+Column Name: emsprovidedflag
+Description: A boolean flag indicating whether Emergency Medical Services (EMS) were provided at the scene. '1' means EMS was provided, '0' means it was not.
+Data Type: bit, NOT NULL (Default 0)
+Examples: 0, 1
+
+Column Name: casualtiesflag
+Description: A flag indicating the presence of casualties. According to the schema description: 0-Blank, 1-No, 2-Yes. However, the sample data shows a value of '1' for 'Casualties Incident'.
+Data Type: tinyint, NULLable
+Examples: 1
+
+Column Name: priorityresponseflag
+Description: A boolean flag indicating if the incident was handled as a priority response (e.g., with lights and sirens). '1' means Yes, '0' means No.
+Data Type: bit, NULLable
+Examples: 1, 0
+
+Column Name: vendorid
+Description: This field is noted in the extended properties as 'Not Used'. It is likely a legacy field.
+Data Type: char(20), NULLable
+Examples: (mostly empty)
+
+Column Name: locationtype
+Description: A code indicating the type of location used for the address. The schema provides the mapping: 1-Address, 2-Intersection, 3-In Front Of, 4-In Rear Of, 5-Adjacent To, 6-Directions, 7-US National Grid, 8-Lat/Long, 9-Township or Range.
+Data Type: float, NULLable (Default 1)
+Examples: 1, 2, 3, 4
+
+Column Name: censustract
+Description: The census tract identifier for the geographic area where the incident occurred. This is used for demographic analysis and planning.
+Data Type: char(7), NULLable (Default '')
+Examples: 28.15, 7, 9.03
+
+Column Name: numberormile
+Description: The street number of the address. For highway incidents, this may be a mile marker.
+Data Type: char(8), NULLable (Default '')
+Examples: 2601, 327, 3700-BLK, 1809
+
+Column Name: streetprefix
+Description: A directional prefix for the street name, such as N, S, E, or W. Lookup codes can be found in `codes901` with `category = 'dir'`.
+Data Type: char(2), NULLable (Default '')
+Examples: S, (blank), E, W
+
+Column Name: streethighway
+Description: The name of the street or highway.
+Data Type: char(30), NULLable (Default '')
+Examples: REAL, CHESTNUT, CARDINAL, WHITE LN
+
+Column Name: streettype
+Description: The street suffix, such as RD, AV, ST, DR, WY, LN, HWY, BLVD. Lookup codes can be found in the `dptCodes` table with `category = 'type'`.
+Data Type: char(4), NULLable (Default '')
+Examples: RD, AV, ST, DR, HWY
+
+Column Name: streetsuffix
+Description: A directional suffix for the street name, such as N, S, E, or W. Lookup codes can be found in `codes901` with `category = 'dir'`.
+Data Type: char(2), NULLable (Default '')
+Examples: (mostly blank), W
+
+Column Name: apartment
+Description: The apartment, suite, unit, or building number.
+Data Type: char(15), NULLable (Default '')
+Examples: 77, (blank), 13, 1006
+
+Column Name: city
+Description: The name of the city where the incident occurred.
+Data Type: char(20), NULLable (Default '')
+Examples: Bakersfield, KERN COUNTY, BAKERSFIELD
+
+Column Name: state
+Description: The two-letter abbreviation for the state.
+Data Type: char(2), NULLable (Default '')
+Examples: CA
+
+Column Name: postalcode
+Description: The 5-digit or 9-digit postal (ZIP) code.
+Data Type: char(20), NULLable (Default '')
+Examples: 93309, 93305, 93312, 93301
+
+Column Name: crossstreetprefix
+Description: The directional prefix for the nearest cross street.
+Data Type: char(2), NULLable (Default '')
+Examples: (mostly blank), W
+
+Column Name: crossstreethighway
+Description: The name of the nearest cross street.
+Data Type: char(30), NULLable (Default '')
+Examples: (mostly blank), LYNN ST, GOSFORD RD
+
+Column Name: crossstreettype
+Description: The street suffix for the nearest cross street.
+Data Type: char(4), NULLable (Default '')
+Examples: (mostly blank), ST
+
+Column Name: crossstreetsuffix
+Description: The directional suffix for the nearest cross street.
+Data Type: char(2), NULLable (Default '')
+Examples: (mostly blank)
+
+Column Name: directions
+Description: A free-text field for general directions to the incident location, often used for locations that are not a standard street address.
+Data Type: varchar(max), NULLable (Default '')
+Examples: (mostly blank)
+
+Column Name: latitude
+Description: The geographic latitude coordinate of the incident location.
+Data Type: char(20), NULLable (Default '')
+Examples: 35.33065871, 35.39931674, 35.40617403
+
+Column Name: longitude
+Description: The geographic longitude coordinate of the incident location.
+Data Type: char(20), NULLable (Default '')
+Examples: -119.0455376, -118.9926012, -118.9520503
+
+Column Name: meridian
+Description: For township/range coordinate systems, this field stores the meridian code. Lookup codes can be found in `codes901` with `category = 'meridian'`.
+Data Type: char(20), NULLable (Default '')
+Examples: (mostly blank)
+
+Column Name: northsouth
+Description: For township/range systems, this field stores the north-south direction. Lookup codes can be found in `dptCodes` with `category = 'dir'`.
+Data Type: char(1), NULLable (Default '')
+Examples: (mostly blank)
+
+Column Name: eastwest
+Description: For township/range systems, this field stores the east-west direction. Lookup codes can be found in `dptCodes` with `category = 'dir'`.
+Data Type: char(1), NULLable (Default '')
+Examples: (mostly blank)
+
+Column Name: subsection
+Description: For township/range systems, this field stores the subsection code. Lookup codes can be found in `codes901` with `category = 'subsectn'`.
+Data Type: char(4), NULLable
+Examples: (mostly blank)
+
+Column Name: section
+Description: For township/range systems, this field stores the section number.
+Data Type: int, NULLable
+Examples: (mostly blank)
+
+Column Name: range
+Description: For township/range systems, this field stores the range number.
+Data Type: int, NULLable
+Examples: (mostly blank)
+
+Column Name: township
+Description: For township/range systems, this field stores the township number.
+Data Type: decimal(5,1), NULLable
+Examples: (mostly blank)
+
+Column Name: compositeaddress
+Description: A single, concatenated string field that combines the full address (number, prefix, street name, type, suffix, apartment) for easy display and searching.
+Data Type: char(50), NOT NULL (Default '')
+Examples: 2601 S REAL RD 77, 327 CHESTNUT AV, 1809 LACEY ST 13
+
+Column Name: MAAPPARATUSSUPPRESSION
+Description: A summary count of the total number of suppression apparatus from any mutual aid department(s) that responded to the incident.
+Data Type: int, NULLable
+Examples: 0
+
+Column Name: MAAPPARATUSEMS
+Description: A summary count of the total number of EMS apparatus from any mutual aid department(s) that responded.
+Data Type: int, NULLable
+Examples: 0
+
+Column Name: MAAPPARATUSOTHER
+Description: A summary count of any other apparatus from any mutual aid department(s) that responded.
+Data Type: int, NULLable
+Examples: 0
+
+Column Name: MAPERSONNELSUPPRESSION
+Description: A summary count of the total number of suppression personnel from any mutual aid department(s) that responded.
+Data Type: int, NULLable
+Examples: 0
+
+Column Name: MAPERSONNELEMS
+Description: A summary count of the total number of EMS personnel from any mutual aid department(s) that responded.
+Data Type: int, NULLable
+Examples: 0
+
+Column Name: MAPERSONNELOTHER
+Description: A summary count of any other personnel from any mutual aid department(s) that responded.
+Data Type: int, NULLable
+Examples: 0
+
+Column Name: useoptionaltabs
+Description: A boolean flag indicating whether optional data entry tabs or sections of the incident report were used. '1' means Yes, '0' means No.
+Data Type: bit, NULLable (Default 0)
+Examples: (mostly blank/0)
+
+Column Name: fdid_no
+Description: The Fire Department ID number. This is a unique identifier for the fire department, often used in state and national reporting. Lookup codes can be found in the `dptCodes` table under `category = 'agency'`.
+Data Type: char(5), NULLable
+Examples: (mostly blank)
+
+Column Name: madeptstate
+Description: The two-letter state abbreviation for the mutual aid department that responded, if applicable.
+Data Type: char(2), NULLable
+Examples: (mostly blank)
+
+Column Name: appversion
+Description: The version of the FireRMS software that was in use when the incident record was created.
+Data Type: char(10), NULLable
+Examples: (mostly blank)
+
+Column Name: county
+Description: The name of the county where the incident occurred.
+Data Type: varchar(20), NULLable
+Examples: KERN, Kern, NULL
+
+Column Name: CityOther
+Description: A field for an "other" city name, possibly used when the city is not in a standard picklist.
+Data Type: char(15), NULLable
+Examples: (mostly blank)
+
+Column Name: occupancykey
+Description: A foreign key linking the incident to a specific occupancy record in the `occ_bas` table.
+Data Type: char(14), NULLable
+Examples: (mostly blank)
+
+Column Name: occupancynumber
+Description: The number or identifier of the occupancy record, as stored in `occ_bas.number`.
+Data Type: char(16), NULLable
+Examples: (mostly blank)
+
+Column Name: occupancyname
+Description: The name of the occupancy (e.g., a business name), as stored in `occ_bas.name`.
+Data Type: char(40), NULLable
+Examples: (mostly blank)
+
+Column Name: runcard
+Description: This field is noted in the extended properties as 'Not Used'.
+Data Type: char(8), NULLable
+Examples: (mostly blank)
+
+Column Name: mappage
+Description: A map page, grid, or book reference to help locate the incident on a paper or digital map.
+Data Type: char(20), NULLable
+Examples: NULL
+
+Column Name: descrip
+Description: This field is noted in the extended properties as 'Not Used'.
+Data Type: char(30), NULLable
+Examples: (mostly blank)
+
+Column Name: SubstitudeFireForm
+Description: A boolean flag indicating if an alternative or substitute fire form was used. '1' means Yes, '0' means No. The data type `udtlogical` is a user-defined data type, likely representing a boolean.
+Data Type: udtlogical, NULLable (Default 0)
+Examples: (likely 0)
+
+Column Name: addressvalidated
+Description: A flag indicating if the address was validated against a master address database. '1' means Yes, '0' means No.
+Data Type: tinyint, NULLable
+Examples: NULL
+
+Column Name: CADCompleted
+Description: A boolean flag indicating if the Computer-Aided Dispatch (CAD) process for this incident was marked as complete. '1' means Yes, '0' means No.
+Data Type: bit, NULLable (Default 0)
+Examples: (mostly blank/0)
+
+Column Name: changedate
+Description: The date and time when any field in the incident record was last modified.
+Data Type: datetime, NULLable
+Examples: 55:21.4, 19:27.9, 58:03.2
+
+Column Name: rowguid
+Description: A globally unique identifier for the row, automatically generated by SQL Server using `newsequentialid()`. It is primarily used for replication and merging data between different databases or systems.
+Data Type: uniqueidentifier, ROWGUIDCOL NOT NULL
+Examples: (binary data, not shown in sample)
+
+Column Name: OtherInfo
+Description: A field included in the incident table for use with the Day Book To Do Items, but it is noted as 'Not populated in the incident table'.
+Data Type: varchar(20), NULLable
+Examples: (mostly blank)
+
+Column Name: LogComments
+Description: A field for comments entered via the Daybook Log.
+Data Type: varchar(max), NULLable
+Examples: (mostly blank)
+
+Column Name: CO_Flag
+Description: A boolean flag indicating whether the incident was related to carbon monoxide (CO). '1' means Yes, '0' means No.
+Data Type: bit, NULLable
+Examples: (mostly blank/0)
+
+Column Name: Alarm_Trans
+Description: This field is noted in the extended properties as 'Not Used'.
+Data Type: char(4), NULLable
+Examples: (mostly blank)
+
+Column Name: Incident_ID
+Description: This field is noted in the extended properties as 'Not Used'.
+Data Type: int, NOT NULL (Default 0)
+Examples: 0
+
+Column Name: loss_not_known
+Description: A boolean flag indicating if the property and contents losses could not be estimated. '1' means Loss Not Known, '0' means losses were estimated or not applicable.
+Data Type: bit, NOT NULL (Default 0)
+Examples: 0, 1
+
+Column Name: iMobile
+Description: A flag indicating if the incident record was created or modified via a mobile data application. '1' means Yes, '0' means No.
+Data Type: tinyint, NULLable (Default 0)
+Examples: 0
+
+Column Name: collecteddate
+Description: The date and time when the incident data was exported to a mobile data collection application (e.g., FireRMS Collector).
+Data Type: datetime, NULLable
+Examples: NULL
+
+Column Name: DispatchIncType
+Description: The incident type as it was entered or received from the CAD system at the moment of dispatch. This may be more general than the final `incidenttype`.
+Data Type: varchar(80), NULLable
+Examples: (mostly blank)
+
+Column Name: nfscasualtycnt
+Description: The total count of fire service casualties (both fatal and non-fatal). This may be a calculated or duplicated field for easier reporting.
+Data Type: smallint, NULLable
+Examples: (mostly blank)
+
+Column Name: ncivcasualtycnt
+Description: The total count of civilian casualties (both fatal and non-fatal). This may be a calculated or duplicated field for easier reporting.
+Data Type: smallint, NULLable
+Examples: (mostly blank)
+
+Column Name: nEstKMDistance
+Description: For departments in the Province of Ontario, Canada, this field stores the estimated distance in kilometers for the response.
+Data Type: smallint, NULLable
+Examples: (mostly blank)
+
+Column Name: ofm_nbrrescued
+Description: For the Ontario Office of the Fire Marshal (OFM), this field stores the number of people rescued.
+Data Type: smallint, NULLable
+Examples: (mostly blank)
+
+Column Name: criticalincident
+Description: A flag for the Ontario Province indicating a Critical Incident. '1' likely means 'No', '2' likely means 'Yes'.
+Data Type: char(1), NULLable
+Examples: (mostly blank)
+
+Column Name: teammobilized
+Description: A flag for the Ontario Province indicating if a team was mobilized. '1' likely means 'No', '2' likely means 'Yes'.
+Data Type: char(1), NULLable
+Examples: (mostly blank)
+
+Column Name: psaptime
+Description: The date and time the incident was first received by the Public Safety Answering Point (PSAP), i.e., the 9-1-1 center.
+Data Type: datetime, NULLable
+Examples: 00:00.0 (mostly empty)
+
+Column Name: circumstance1
+Description: A code for the first of up to three circumstances contributing to a wildland fire. Lookup codes can be found in the `dptCodes` table with `category = 'cstance'`.
+Data Type: varchar(10), NULLable
+Examples: (mostly blank)
+
+Column Name: circumstance2
+Description: A code for the second circumstance. Lookup codes are in `dptCodes` with `category = 'cstance'`.
+Data Type: varchar(10), NULLable
+Examples: (mostly blank)
+
+Column Name: circumstance3
+Description: A code for the third circumstance. Lookup codes are in `dptCodes` with `category = 'cstance'`.
+Data Type: varchar(10), NULLable
+Examples: (mostly blank)
+
+Column Name: lArsonFlag
+Description: A boolean flag for wildland fires indicating if arson was suspected. '1' means Yes, '0' means No.
+Data Type: bit, NULLable
+Examples: (mostly blank/0)
+
+Column Name: ReportedBy
+Description: A code indicating who or what agency reported the incident. Lookup codes can be found in the `dptCodes` table with `category = 'inreptby'`.
+Data Type: varchar(8), NULLable
+Examples: (mostly blank)
+
+Column Name: lReExport
+Description: A boolean flag indicating if the record was corrected and needs to be re-exported to a state or federal reporting system (like NFIRS). '1' means Yes, '0' means No.
+Data Type: bit, NULLable (Default 0)
+Examples: (likely 0)
+
+Column Name: XCoord
+Description: The X-coordinate for geographic mapping systems (e.g., state plane coordinate system).
+Data Type: char(20), NULLable
+Examples: (mostly blank)
+
+Column Name: YCoord
+Description: The Y-coordinate for geographic mapping systems.
+Data Type: char(20), NULLable
+Examples: (mostly blank)
+
+Column Name: lValidated
+Description: A boolean flag indicating if the incident location has been validated, likely through a geocoding process. '1' means Yes, '0' means No.
+Data Type: bit, NULLable
+Examples: (likely 0)
+
+Column Name: isEPCR
+Description: A boolean flag indicating if this incident record originated from or is linked to an electronic Patient Care Report (ePCR) system. '1' means Yes, '0' means No.
+Data Type: bit, NULLable
+Examples: (likely 0)
+
+Column Name: ofm_mutualaid
+Description: For the Ontario Office of the Fire Marshal (OFM), this is a code for the type of mutual aid. Lookup codes can be found in the `dptCodes` table with `category = 'mutl_aid'`.
+Data Type: char(10), NULLable
+Examples: (mostly blank)
+
+Column Name: EMSModule
+Description: A flag indicating the type of EMS module or standard used. According to the description: 1-Basic EMS, 2-Advanced EMS, 3-NEMSIS (National EMS Information System).
+Data Type: tinyint, NULLable
+Examples: (mostly blank)
+
+Column Name: inc_exc
+Description: A code for an incident delay or exception. Lookup codes can be found in the `dptCodes` table with `category = 'incexcep'`.
+Data Type: char(10), NULLable
+Examples: (mostly blank)
+
+Column Name: CensusArea
+Description: A code for the Census Area. Lookup codes can be found in the `dptCodes` table with `category = 'censara'`.
+Data Type: char(10), NULLable
+Examples: (mostly blank)
+
+Column Name: finaldispatchcode
+Description: The final dispatch code used for the incident. This may be the same as or different from the `initialdispatchcode`, reflecting any updates made during the response.
+Data Type: varchar(25), NULLable
+Examples: FWX, MA, FST
+
+Column Name: created
+Description: The date and time when the incident record was first created in the database.
+Data Type: datetime, NOT NULL (Default getdate())
+Examples: (not in sample, but would be a date/time)
+
+Column Name: ResponseType
+Description: A code for the type of response. Lookup codes can be found in the `dptCodes` table with `category = 'resptype'`.
+Data Type: varchar(10), NULLable
+Examples: (mostly blank)
+
+Column Name: CADText1
+Description: A user-defined text field for custom CAD data, number 1.
+Data Type: varchar(50), NULLable
+Examples: (mostly blank)
+
+Column Name: CADText2
+Description: A user-defined text field for custom CAD data, number 2.
+Data Type: varchar(50), NULLable
+Examples: (mostly blank)
+
+Column Name: CADText3
+Description: A user-defined text field for custom CAD data, number 3.
+Data Type: varchar(50), NULLable
+Examples: (mostly blank)
+
+Column Name: CADCombo1
+Description: A user-defined combo box field for custom CAD data, number 1. Lookup codes can be found in the `dptCodes` table with `category = 'cadcomb1'`.
+Data Type: varchar(50), NULLable
+Examples: (mostly blank)
+
+Column Name: CADCombo2
+Description: A user-defined combo box field for custom CAD data, number 2. Lookup codes can be found in the `dptCodes` table with `category = 'cadcomb2'`.
+Data Type: varchar(50), NULLable
+Examples: (mostly blank)
+
+Column Name: CADCombo3
+Description: A user-defined combo box field for custom CAD data, number 3. Lookup codes can be found in the `dptCodes` table with `category = 'cadcomb3'`.
+Data Type: varchar(50), NULLable
+Examples: (mostly blank)
+
+Column Name: GMTOffSet
+Description: The GMT offset for the time zone of the record's location.
+Data Type: varchar(6), NULLable
+Examples: (mostly blank)
+
+Column Name: CADDate1
+Description: A user-defined date/time field for custom CAD data, number 1.
+Data Type: datetime, NULLable
+Examples: (mostly blank)
+
+Column Name: CADDate2
+Description: A user-defined date/time field for custom CAD data, number 2.
+Data Type: datetime, NULLable
+Examples: (mostly blank)
+
+Column Name: CADDate3
+Description: A user-defined date/time field for custom CAD data, number 3.
+Data Type: datetime, NULLable
+Examples: (mostly blank)
+
+Column Name: WaterOnFireDate
+Description: This field has been moved to the `fire` table. It was originally an incoming benchmark field from CAD.
+Data Type: datetime, NULLable
+Examples: (mostly blank)
+
+Column Name: PriSearchCompDate
+Description: An incoming benchmark field from CAD for the date/time the primary search was completed. It is moved to the `fire` table via a trigger.
+Data Type: datetime, NULLable
+Examples: (mostly blank)
+
+Column Name: SecSearchCompDate
+Description: The date and time the secondary search was completed.
+Data Type: datetime, NULLable
+Examples: (mostly blank)
+
+Column Name: AllClearDate
+Description: The date and time the incident scene was declared "All Clear," meaning no further victims or hazards were found.
+Data Type: datetime, NULLable
+Examples: (mostly blank)
+
+Column Name: LossStoppedDate
+Description: The date and time when the spread of loss or damage was stopped.
+Data Type: datetime, NULLable
+Examples: (mostly blank)
+
+Column Name: CustStabilizedDate
+Description: The date and time when the customer or patient was stabilized.
+Data Type: datetime, NULLable
+Examples: (mostly blank)
+
+Column Name: Investigations_Notified
+Description: A flag indicating if the fire investigation unit was notified. '1' likely means 'No', '2' likely means 'Yes'.
+Data Type: tinyint, NULLable (Default 0)
+Examples: (mostly blank/0)
+
+Column Name: Extrication
+Description: A boolean flag indicating if extrication was performed. '1' means Yes, '0' means No.
+Data Type: bit, NOT NULL (Default 0)
+Examples: 0
+
+Column Name: ApparatusImported
+Description: A flag used for exposure records. '0' means apparatus was not imported from the primary incident, '1' means apparatus was imported.
+Data Type: bit, NULLable (Default 0)
+Examples: (mostly blank/0)
+
+Column Name: lHazMatTabFlag
+Description: A boolean flag indicating if the Hazardous Materials tab should be included in the report. '1' means include the tab, '0' means do not include it. It is set based on the `hazardmaterialreleased` selection.
+Data Type: bit, NULLable (Default 0)
+Examples: (mostly blank/0)
+
+Column Name: responseTime
+Description: The calculated maximum allowable response time for the selected incident type, used for performance benchmarking.
+Data Type: varchar(20), NULLable
+Examples: (mostly blank)
+
+Column Name: ProQA
+Description: The dispatch code or protocol information from the ProQA emergency dispatch system.
+Data Type: varchar(100), NULLable
+Examples: (mostly blank)
+
+Column Name: turnTime
+Description: The calculated turnout time for the incident, representing the time from alarm to apparatus leaving the station.
+Data Type: varchar(20), NULLable
+Examples: (mostly blank)
+
+Column Name: Mapset
+Description: The map set identifier from the AGIS geographic information system.
+Data Type: varchar(6), NULLable
+Examples: (mostly blank)
+
+Column Name: Easting
+Description: The Easting coordinate from the AGIS system.
+Data Type: varchar(5), NULLable
+Examples: (mostly blank)
+
+Column Name: Northing
+Description: The Northing coordinate from the AGIS system.
+Data Type: varchar(5), NULLable
+Examples: (mostly blank)

data/rag_input_data/incident_table_details.txt

@@ -0,0 +1,15 @@
+Table name: incident
+
+The incident table serves as the central repository for all emergency incident data within the Fire Records Management System (RMS5). Each record in this table represents a unique incident, identified by a system-generated key (incidentkey). This table acts as the primary hub, linking to numerous other tables that store granular details about apparatus, personnel, casualties, and more.
+
+Core Information: The table stores the foundational details of an incident, including its public-facing number (incidentnumber), exposure status (exposure), and official date and time (incidentdate). Key workflow statuses are tracked via boolean flags, indicating if a report is completed, has been reviewstatusflag, or is approved for publicreleaseflag.
+
+Temporal Data: A critical function of this table is to record all major timestamps associated with an incident's lifecycle. This includes the initial alarmdate, the first unit's arrivaldate, the time the incident was brought under controlleddate, and when the last unit lastunitcleareddate. These timestamps are essential for calculating performance metrics like response time.
+
+Location and Jurisdiction: The table comprehensively captures the incident's location. This includes administrative identifiers like district, station, and shift, as well as detailed address components (streetnumber, streethighway, city, state, zipcode) and geographic coordinates (latitude, longitude). A pre-built compositeaddress field is also provided for easy display.
+
+Incident Classification and Response: It classifies the nature of the incident using standardized codes for incidenttype, initialdispatchcode, and actions taken (actiontaken1, actiontaken2, actiontaken3). It also tracks resource allocation through summary counts for department and mutual aid apparatus and personnel (e.g., apparatussuppression, mapersonnelsuppression).
+
+Property and Casualty Information: For incidents involving property damage or loss, the table stores financial data such as valueproperty, lossproperty, and their contents counterparts. It also tracks the number of fatalfireservice, fatalother, and non-fatal casualties, along with flags for casualties (casualtiesflag) and EMS provision (emsprovidedflag).
+
+Supplementary and Legacy Data: A significant portion of the table is dedicated to fields that are either legacy columns, placeholders for data moved to more specific tables (like fire or carbonmonoxide), or fields for CAD (Computer-Aided Dispatch) integration (e.g., CADText1, ProQA). This design makes the table a comprehensive, all-encompassing record of the incident from dispatch to final closure.

data/rag_input_data/incidentappratus_columns_details.txt

@@ -0,0 +1,369 @@
+Column Name: incidentkey
+Description: The primary key for the incident table. This is a unique, system-generated 14-character identifier for every incident record. It serves as the fundamental link to connect this apparatus response record back to the main incident details. This value is used to join with the incident table to get incident-level information such as incident type, location, and final disposition.
+Data Type: char(14), NOT NULL
+Examples: _48Y061NFN_SMS, _48Y006CZ7_SMS, _48Y09QZRO_SMS
+
+Column Name: apparatuskey
+Description: The primary key for the apparatus table. This is a unique, system-generated 14-character identifier for a specific apparatus response to an incident. It serves as the primary link between apparatus response records and personnel assignments, indicating which piece of equipment a person was assigned to for a given incident. This value is used to join with the apparatus table to get details about the vehicle itself.
+Data Type: char(14), NULL
+Examples: _48Y062BSQ_SMS, _48Y006D02_SMS, _48Y09RO93_SMS
+
+Column Name: apparatusid
+Description: The public-facing identifier or "unit number" of the apparatus (e.g., 'BE5', 'BB2'). This is the common name used in radio communications and reports to identify a specific fire station and vehicle type (e.g., Engine, Truck, Chief). This value is often used in conjunction with the apparatuskey for display and reporting purposes.
+Data Type: char(?), NULL
+Examples: BE5, BE13, BE2, BB2
+
+Column Name: deptunitornotcode
+Description: A code indicating whether the apparatus is a primary department unit or another type of resource. The code '0' corresponds to 'DeptUnit', meaning it is a department-owned unit.
+Data Type: int, NULL
+Examples: 0
+
+Column Name: deptunitornotdescrip
+Description: A description of the apparatus's departmental affiliation. The value 'DeptUnit' indicates the apparatus is owned and operated by the fire department, as opposed to a mutual aid or private resource.
+Data Type: nvarchar, NULL
+Examples: DeptUnit
+
+Column Name: priorityresponsecode
+Description: A code indicating the priority of the response. '1' signifies a high-priority, emergent response (e.g., with lights and sirens). '0' signifies a non-emergent or routine response.
+Data Type: int, NULL
+Examples: 0, 1
+
+Column Name: priorityresponsedescrip
+Description: A description of the response priority. 'Yes' indicates a priority or emergent response, while 'No' indicates a non-priority or non-emergent response.
+Data Type: nvarchar, NULL
+Examples: No, Yes
+
+Column Name: cancelledenroutecode
+Description: A code indicating whether the apparatus was cancelled while responding to the incident. '1' signifies Yes (the unit was cancelled), '0' signifies No.
+Data Type: int, NULL
+Examples: 0, 1
+
+Column Name: cancelledenroutedescrip
+Description: A description of the cancellation status. 'Yes' means the apparatus was cancelled en route. 'No' means it was not.
+Data Type: nvarchar, NULL
+Examples: No, Yes
+
+Column Name: firstarrivingunitcode
+Description: A code indicating whether this apparatus was the first to arrive on the scene of the incident. '1' signifies Yes, '0' signifies No.
+Data Type: int, NULL
+Examples: 1, 0
+
+Column Name: firstarrivingunitdescrip
+Description: A description of the first-arriving status. 'Yes' means this unit was the first to arrive. 'No' means it was not.
+Data Type: nvarchar, NULL
+Examples: Yes, No
+
+Column Name: dispatchtype
+Description: A code indicating the type of dispatch. This field appears to be unused or deprecated, as all values are NULL.
+Data Type: int, NULL
+Examples: NULL
+
+Column Name: dispatchtypedescrip
+Description: A description of the dispatch type. This field appears to be unused or deprecated, as all values are NULL.
+Data Type: nvarchar, NULL
+Examples: NULL
+
+Column Name: respondedfromquarterscode
+Description: A code indicating whether the apparatus responded directly from its quarters (the fire station). '1' signifies Yes, '0' signifies No.
+Data Type: int, NULL
+Examples: 0, 1
+
+Column Name: respondedfromquarterdescrip
+Description: A description of the response origin. 'Yes' means the apparatus responded from its station. 'No' typically indicates it was already out on another call, staged, or returning from a previous incident.
+Data Type: nvarchar, NULL
+Examples: No, Yes
+
+Column Name: mainapparatususecode
+Description: A code representing the primary function or use of the apparatus during this response. '1' commonly indicates a suppression role, while '2' might indicate EMS or other support. This code is used in conjunction with apparatustypecode to define the unit's role.
+Data Type: int, NULL
+Examples: 1
+
+Column Name: mainapparatususedescrip
+Description: A description of the primary apparatus use. 'Suppression' indicates the apparatus is primarily for firefighting.
+Data Type: nvarchar, NULL
+Examples: Suppression
+
+Column Name: apparatustypecode
+Description: A code that specifies the type of apparatus. '11' indicates an Engine, '12' indicates a Truck or Aerial, '92' indicates a Chief Officer Car, and '16' indicates a Brush Truck. This code is used to categorize the vehicle.
+Data Type: int, NULL
+Examples: 11, 92, 12, 16
+
+Column Name: apparatustypedescrip
+Description: A description of the apparatus type. Examples include "Engine", "Chief officer car", "Truck or aerial", and "Brush truck". This provides the full textual name for the apparatustypecode.
+Data Type: nvarchar, NULL
+Examples: Engine, Chief officer car, Truck or aerial, Brush truck
+
+Column Name: actiontaken1code, actiontaken2code, actiontaken3code, actiontaken4code
+Description: A code representing the first, second, third, and fourth primary actions taken by the crew of this apparatus at the scene. Codes like '93' indicate "Cancelled en route", '86' indicates "Investigate", and '31' indicates "Provide first aid & check for injuries". The presence of multiple action codes allows for recording a sequence of activities.
+Data Type: nvarchar, NULL
+Examples: 93, 86, 31, NULL
+
+Column Name: actiontaken1descip, actiontaken2descip, actiontaken3descip, actiontaken4descip
+Description: A description of the corresponding actiontaken#code. Examples include "Cancelled en route", "Investigate", and "Provide first aid & check for injuries". This provides the human-readable narrative of the actions taken by the crew.
+Data Type: nvarchar, NULL
+Examples: Cancelled en route, Investigate, Provide first aid & check for injuries, NULL
+
+Column Name: numberofresponders
+Description: The number of personnel who responded on this apparatus to the incident. This count is used for staffing analysis and resource tracking.
+Data Type: int, NULL
+Examples: 3, 1, 4
+
+Column Name: dispatchdatetime
+Description: The date and time when the apparatus was dispatched to the incident. This is the starting point for measuring response timelines.
+Data Type: datetime, NULL
+Examples: 48:09.0, 02:38.0, 30:25.0
+
+Column Name: dispatchtime
+Description: The time of day when the apparatus was dispatched, derived from dispatchdatetime. This field is used for analyzing time-of-day patterns.
+Data Type: time, NULL
+Examples: 2:48:09, 0:02:38, 4:30:25
+
+Column Name: dispatchdate
+Description: The date on which the apparatus was dispatched, derived from dispatchdatetime.
+Data Type: date, NULL
+Examples: 1/1/2015, 1/2/2015, 1/3/2015
+
+Column Name: dispatchenroutetime
+Description: The time of day when the apparatus acknowledged the dispatch and began traveling to the scene (en route). The format is h:mm:ss.
+Data Type: time, NULL
+Examples: 0:01:31, 0:01:19, 0:01:49
+
+Column Name: dispatchenroutediffseconds
+Description: The time difference, in seconds, between dispatchdatetime and enroutetoscenedatetime. This measures the "turnout time" – how long it took the crew to get the apparatus rolling after being dispatched.
+Data Type: int, NULL
+Examples: 91, 79, 109
+
+Column Name: enroutetoscenedatetime
+Description: The date and time when the apparatus reported that it was en route to the scene. This marks the beginning of the travel phase.
+Data Type: datetime, NULL
+Examples: 49:40.0, 03:57.0, 32:14.0
+
+Column Name: enroutetoscenetime
+Description: The time of day when the apparatus reported it was en route to the scene, derived from enroutetoscenedatetime.
+Data Type: time, NULL
+Examples: 2:49:40, 0:03:57, 4:32:14
+
+Column Name: enroutetoscenedate
+Description: The date on which the apparatus reported it was en route to the scene, derived from enroutetoscenedatetime.
+Data Type: date, NULL
+Examples: 1/1/2015
+
+Column Name: enroutearrivalscenetime
+Description: The time of day when the apparatus arrived at the scene of the incident. The format is h:mm:ss. NULL values indicate the unit did not arrive (e.g., was cancelled en route).
+Data Type: time, NULL
+Examples: NULL, 0:06:12, NULL
+
+Column Name: enroutearrivalscenediffseconds
+Description: The time difference, in seconds, between enroutetoscenedatetime and arrivaldatetime. This measures the "travel time" from the station to the scene.
+Data Type: int, NULL
+Examples: 0, 372, 0
+
+Column Name: responsetime
+Description: The total time from dispatch to arrival on scene, calculated as dispatchdatetime to arrivaldatetime. The format is h:mm:ss. NULL values indicate the unit did not arrive.
+Data Type: time, NULL
+Examples: NULL, 0:07:37, NULL
+
+Column Name: responsetimeseconds
+Description: The total response time, in seconds, from dispatch to arrival on scene. This is a numeric equivalent of responsetime.
+Data Type: int, NULL
+Examples: 0, 457, 0
+
+Column Name: arrivaldatetime
+Description: The date and time when the apparatus arrived on the scene of the incident.
+Data Type: datetime, NULL
+Examples: 00:00.0, 54:06.0, 00:00.0
+
+Column Name: arrivaltime
+Description: The time of day when the apparatus arrived on the scene, derived from arrivaldatetime.
+Data Type: time, NULL
+Examples: , 0:54:06,
+
+Column Name: arrivaldate
+Description: The date on which the apparatus arrived on the scene, derived from arrivaldatetime.
+Data Type: date, NULL
+Examples: , 1/1/2015,
+
+Column Name: arrivaltoenroutehospdifftime
+Description: This field appears to be unused or deprecated for this dataset, as all values are NULL. It may relate to EMS transport time calculations.
+Data Type: time, NULL
+Examples: NULL
+
+Column Name: arrivaltoenroutehospdiffseconds
+Description: This field appears to be unused or deprecated for this dataset, as all values are NULL.
+Data Type: int, NULL
+Examples: 0
+
+Column Name: enroutetohospitaldatetime
+Description: The date and time when the apparatus began transporting a patient to the hospital. This is NULL for non-EMS responses.
+Data Type: datetime, NULL
+Examples: 00:00.0, 00:00.0, 00:00.0
+
+Column Name: enroutetohospitaltime
+Description: The time of day when the apparatus began transporting a patient to the hospital, derived from enroutetohospitaldatetime.
+Data Type: time, NULL
+Examples: , , ,
+
+Column Name: enroutetohospitaldate
+Description: The date on which the apparatus began transporting a patient to the hospital, derived from enroutetohospitaldatetime.
+Data Type: date, NULL
+Examples: , , ,
+
+Column Name: enroutetoarrivalhospdifftime
+Description: This field appears to be unused or deprecated for this dataset, as all values are NULL.
+Data Type: time, NULL
+Examples: NULL
+
+Column Name: enroutetoarrivalhospdiffseconds
+Description: This field appears to be unused or deprecated for this dataset, as all values are NULL.
+Data Type: int, NULL
+Examples: 0
+
+Column Name: arrivalscenetoarrivalhospdifftime
+Description: This field appears to be unused or deprecated for this dataset, as all values are NULL.
+Data Type: time, NULL
+Examples: NULL
+
+Column Name: arrivalscenetoarrivalhospdiffseconds
+Description: This field appears to be unused or deprecated for this dataset, as all values are NULL.
+Data Type: int, NULL
+Examples: 0
+
+Column Name: hospitalarrivaldatetime
+Description: The date and time when the apparatus arrived at the hospital with a patient. This is NULL for non-EMS responses.
+Data Type: datetime, NULL
+Examples: 00:00.0, 00:00.0, 00:00.0
+
+Column Name: hospitalarrivaltime
+Description: The time of day when the apparatus arrived at the hospital, derived from hospitalarrivaldatetime.
+Data Type: time, NULL
+Examples: , , ,
+
+Column Name: hospitalarrivaldate
+Description: The date on which the apparatus arrived at the hospital, derived from hospitalarrivaldatetime.
+Data Type: date, NULL
+Examples: , , ,
+
+Column Name: arrivalclearhospdifftime
+Description: This field appears to be unused or deprecated for this dataset, as all values are NULL.
+Data Type: time, NULL
+Examples: NULL
+
+Column Name: arrivalclearhospdiffseconds
+Description: This field appears to be unused or deprecated for this dataset, as all values are NULL.
+Data Type: int, NULL
+Examples: 0
+
+Column Name: cleardatetime
+Description: The date and time when the apparatus was cleared from the incident and became available for another response. This marks the end of the incident for this unit.
+Data Type: datetime, NULL
+Examples: 57:19.0, 08:03.0, 41:20.0
+
+Column Name: cleartime
+Description: The time of day when the apparatus was cleared from the incident, derived from cleardatetime.
+Data Type: time, NULL
+Examples: 2:57:19, 0:08:03, 4:41:20
+
+Column Name: cleardate
+Description: The date on which the apparatus was cleared from the incident, derived from cleardatetime.
+Data Type: date, NULL
+Examples: 1/1/2015, 1/2/2015, 1/3/2015
+
+Column Name: dispatchcleardifftime
+Description: The total time from dispatch to being cleared from the incident, calculated as dispatchdatetime to cleardatetime. The format is h:mm:ss. This measures the total time the unit was committed to the incident.
+Data Type: time, NULL
+Examples: 0:09:10, 0:05:25, 0:10:55
+
+Column Name: dispatchcleardiffseconds
+Description: The total time from dispatch to being cleared, in seconds. This is a numeric equivalent of dispatchcleardifftime.
+Data Type: int, NULL
+Examples: 550, 325, 655
+
+Column Name: inservicedatetime
+Description: The date and time when the apparatus was placed back in service and available for responses. This may be the same as cleardatetime or may differ if post-incident activities (e.g., decontamination, refueling) occurred.
+Data Type: datetime, NULL
+Examples: 00:00.0, 00:00.0, 00:00.0
+
+Column Name: inservicetime
+Description: The time of day when the apparatus was placed back in service, derived from inservicedatetime.
+Data Type: time, NULL
+Examples: , , ,
+
+Column Name: inservicedate
+Description: The date on which the apparatus was placed back in service, derived from inservicedatetime.
+Data Type: date, NULL
+Examples: , , ,
+
+Column Name: emsruncode
+Description: A code indicating whether this was an EMS (Emergency Medical Services) run. The value 'Not EMS Run' suggests the apparatus was not on a primary EMS call.
+Data Type: nvarchar, NULL
+Examples: Not EMS Run
+
+Column Name: emsrundescrip
+Description: A description of the EMS run status. The consistent value NULL suggests this incident type is not primarily an EMS event.
+Data Type: nvarchar, NULL
+Examples: NULL
+
+Column Name: emsrunnumber
+Description: A number associated with the EMS run, potentially a sequential or tracking number. This is NULL for non-EMS runs.
+Data Type: int, NULL
+Examples: NULL
+
+Column Name: losapcode
+Description: A code related to LOSAP (Length of Service Award Program) credit. '1' indicates the response qualifies for LOSAP credit.
+Data Type: int, NULL
+Examples: 1
+
+Column Name: losapdescrip
+Description: A description of the LOSAP credit status. 'Losap Credit' indicates the response is eligible for credit in the service award program.
+Data Type: nvarchar, NULL
+Examples: Losap Credit
+
+Column Name: alarmscode
+Description: A code indicating the alarm level or number of alarms for the incident. All values are NULL in this sample, suggesting this is for a single-alarm incident or this field is not used.
+Data Type: int, NULL
+Examples: NULL
+
+Column Name: alarmdescrip
+Description: A description of the alarm level. This field is consistently NULL in the provided data.
+Data Type: nvarchar, NULL
+Examples: NULL
+
+Column Name: amount1, amount2
+Description: Generic numeric fields, possibly for recording quantities like hose lengths, water used, or other resources. They are NULL in this dataset, indicating they were not used for these incidents.
+Data Type: int, NULL
+Examples: NULL
+
+Column Name: fdid_no
+Description: The Fire Department ID number. This field is NULL in the provided data, suggesting it may not be used or is populated from a related table.
+Data Type: nvarchar, NULL
+Examples: NULL
+
+Column Name: stagingdatetime
+Description: The date and time when the apparatus was placed in a staging area. This is used for large-scale incidents where units are held in a designated area before being assigned.
+Data Type: datetime, NULL
+Examples: 00:00.0, 00:00.0, 00:00.0
+
+Column Name: stagingtime
+Description: The time of day when the apparatus was placed in a staging area, derived from stagingdatetime.
+Data Type: time, NULL
+Examples: , , ,
+
+Column Name: stagingdate
+Description: The date on which the apparatus was placed in a staging area, derived from stagingdatetime.
+Data Type: date, NULL
+Examples: , , ,
+
+Column Name: AtPatientSideDateTime, AtPatientSideTime, AtPatientSideDate
+Description: The date and time when the crew arrived at the patient's side, typically for EMS calls. This is 00:00.0 in the sample, indicating it was either not an EMS call or this timestamp was not recorded.
+Data Type: datetime / time / date, NULL
+Examples: 00:00.0 / / (blank)
+
+Column Name: FacilityDateTime, FacilityTime, FacilityDate
+Description: The date and time when the apparatus arrived at a medical facility with a patient. This is 00:00.0 in the sample, indicating it was either not an EMS transport call or this timestamp was not recorded.
+Data Type: datetime / time / date, NULL
+Examples: 00:00.0 / / (blank)
+
+Column Name: changedate
+Description: A timestamp indicating the last time this record was modified in the database. The values appear to be in seconds or a time-of-day format, but given the context of other datetime fields, it likely represents a time component of a full datetime stamp.
+Data Type: datetime, NULL
+Examples: 43:34.2, 10:02.9, 36:07.4

data/rag_input_data/incidentappratus_table_details.txt

@@ -0,0 +1,19 @@
+Table Name: auv_incidentapparatus
+
+This table contains detailed apparatus response records for emergency incidents. Each row represents a specific apparatus unit responding to an incident and includes operational, status, and timing information related to that response. The table links emergency incidents, apparatus units, and operational activities, enabling comprehensive analysis of how fire department resources respond to emergencies.
+
+The dataset is structured around a relational connection between incidents and apparatus responses. A unique incident identifier connects each record to the main incident dataset, while a separate apparatus identifier represents the individual vehicle or response unit assigned to that incident. These identifiers allow the dataset to integrate with related tables containing additional incident information, apparatus details, and personnel assignments.
+
+Operational characteristics of the responding apparatus are included to describe how the unit participated in the response. These attributes capture the apparatus type, whether it belongs to the department, its operational role, and whether it was the first unit to arrive at the scene. Additional flags indicate conditions such as priority responses, cancellation while en route, and whether the unit responded directly from its station.
+
+The dataset also records the operational actions performed by the apparatus crew during the incident. Multiple action fields allow the system to store a sequence of activities carried out at the scene. These actions typically follow standardized fire reporting classifications such as those defined by the National Fire Incident Reporting System (NFIRS), which categorize activities like investigation, providing medical assistance, or suppression operations.
+
+A major component of the table is the detailed response timeline for each apparatus. Multiple timestamps capture key milestones in the response lifecycle, including dispatch, acknowledgement of dispatch, travel to the scene, arrival on scene, patient transport events, clearing the incident, and returning to service. In addition to raw timestamps, the table includes calculated duration fields that measure turnout time, travel time, response time, and the total amount of time a unit remained committed to the incident.
+
+For incidents involving emergency medical services (EMS), the dataset includes additional patient care milestones such as arrival at the patient’s side, transport to a medical facility, and arrival at the hospital. These fields enable analysis of EMS response performance and patient transport timelines. When incidents do not involve EMS activities, these fields remain empty.
+
+Administrative and operational tracking information is also included. Fields indicate whether the response qualifies for LOSAP (Length of Service Award Program) credit, which is often used by volunteer fire departments to track service participation for benefits or recognition programs. Additional metadata fields record staging activity, modification timestamps, and optional numeric values that may be used for resource or reporting metrics.
+
+Several fields in the dataset appear unused or consistently null, suggesting they are either reserved for future use, applicable only to specific incident types, or part of a standardized reporting schema where not all attributes are required for every incident.
+
+Overall, this table provides a detailed operational view of apparatus-level activity during emergency incidents. It captures apparatus characteristics, response actions, operational status flags, and a complete response timeline, making it useful for analyzing response performance, apparatus utilization, operational efficiency, and emergency service reporting.

data/rag_input_data/incidentbase_columns_details.txt

@@ -0,0 +1,159 @@
+Column Name: incidentkey
+Description: The primary key for the incident record. This is a unique, system-generated 14-character identifier for every incident record, typically following a pattern like _48Y..._SMS. It serves as the fundamental link to other tables.
+Data Type: char(14), NOT NULL
+Examples: _48Y00K5I8_SMS, _48Y00K5IA_SMS, _48Y00JH1N_SMS
+
+Column Name: IncidentNumber
+Description: The human-readable, sequential number assigned to an incident by the dispatch center. Based on the data, it appears to be a 7-digit number.
+Data Type: char(7), NOT NULL
+Examples: 1500003, 1500004, 1500002
+
+Column Name: IncidentExposureNumber
+Description: A number used to differentiate between multiple separate fire or event "exposures" or buildings involved in a single original incident number. A value of '0' indicates the primary incident.
+Data Type: char(1), NOT NULL
+Examples: 0
+
+Column Name: CompletedReportCode
+Description: A code indicating the completion status of the incident report. A value of '1' likely signifies a "Completed" report.
+Data Type: char(1), NOT NULL
+Examples: 1
+
+Column Name: CompletedReportDescrip
+Description: A textual description corresponding to the CompletedReportCode. From the data, '1' maps to "Completed".
+Data Type: varchar(50), NULL
+Examples: Completed
+
+Column Name: ReviewedReportCode
+Description: A code indicating whether the incident report has been reviewed. A value of '0' likely signifies "Not Reviewed".
+Data Type: char(1), NOT NULL
+Examples: 0
+
+Column Name: ReviewReportDescrip
+Description: A textual description corresponding to the ReviewedReportCode. From the data, '0' maps to "Not Reviewed".
+Data Type: varchar(50), NULL
+Examples: Not Reviewed
+
+Column Name: PublicReleaseReportCode
+Description: A code indicating if the report is cleared for public release. A value of '0' likely signifies "Not Released".
+Data Type: char(1), NOT NULL
+Examples: 0
+
+Column Name: PublicReleaseReportDEscrip
+Description: A textual description corresponding to the PublicReleaseReportCode. From the data, '0' maps to "Not Released". (Note the typo in the original column name, DEscrip).
+Data Type: varchar(50), NULL
+Examples: Not Released
+
+Column Name: DidNotArriveCode
+Description: A flag indicating whether the fire unit arrived on the scene. '0' signifies "Did Arrive", and '1' signifies "Did Not Arrive".
+Data Type: char(1), NOT NULL
+Examples: 0, 1
+
+Column Name: DidNotArriveDescrip
+Description: A textual description corresponding to the DidNotArriveCode. From the data, '0' maps to "Did Arrive" and '1' to "Did Not Arrive".
+Data Type: varchar(50), NULL
+Examples: Did Arrive, Did Not Arrive
+
+Column Name: AlarmDateTime, Alarmtime, Alarmdate
+Description: These three columns represent the same timestamp - the date and time the alarm was received. The data is split into separate date and time fields for ease of use. The AlarmDateTime column appears to contain the combined time portion, but the date is stored separately in Alarmdate. For example, 08:50.0 is the time and 1/1/2015 is the date.
+Data Type: time, date, date
+Examples: (Time: 08:50.0, Date: 1/1/2015)
+
+Column Name: ArrivalDateTime, Arrivaltime, Arrivaldate
+Description: These three columns represent the same timestamp - the date and time the first unit arrived on the scene. The data is split into separate date and time fields.
+Data Type: time, date
+Examples: (Time: 16:56.0, Date: 1/1/2015)
+
+Column Name: ClearedDateTime, Clearedtime, Cleareddate
+Description: These three columns represent the same timestamp - the date and time the incident was cleared, and the last unit left the scene. The data is split into separate date and time fields.
+Data Type: time, date
+Examples: (Time: 25:33.0, Date: 1/1/2015). Note that times can exceed 24 hours, indicating duration.
+
+Column Name: ResponseTime
+Description: A human-readable representation of the time taken from alarm to arrival on scene. It is formatted as MM:SS. For example, 8:06 represents 8 minutes and 6 seconds.
+Data Type: char(5)
+Examples: 8:06, 5:19, 9:45
+
+Column Name: ResponseTimediffseconds
+Description: The ResponseTime expressed purely as a total number of seconds. This is useful for calculations.
+Data Type: int
+Examples: 486, 319, 585
+
+Column Name: District
+Description: The district code for the geographic area in which the incident occurred. Examples are B07, B04, 67.
+Data Type: char(5), NULL
+Examples: B07, B04, 67
+
+Column Name: Station
+Description: The station number or code of the primary fire station that responded to the incident.
+Data Type: char(5), NULL
+Examples: B7, 4, B1
+
+Column Name: IncidentTypeCode
+Description: A code that classifies the primary type of incident (e.g., type of fire, EMS call). Examples include 243 for "Fireworks explosion", 321 for "EMS call".
+Data Type: char(4), NULL
+Examples: 243, 2430, 321
+
+Column Name: IncidentTypeDescrip
+Description: A textual description corresponding to the IncidentTypeCode. This provides a clear explanation of the incident type.
+Data Type: varchar(255), NULL
+Examples: Fireworks explosion (no fire), EMS call, excluding vehicle accident with injury
+
+Column Name: actiontaken1code, actiontaken2code, actiontaken3code
+Description: Codes describing the primary, secondary, and tertiary actions taken by the fire personnel on scene. 86 maps to "Investigate", 85 to "Enforce code".
+Data Type: char(2), NULL
+Examples: 86, 85, 80
+
+Column Name: actiontaken1descip, actiontaken2descip, actiontaken3descip
+Description: Textual descriptions corresponding to the actiontaken codes, explaining what was done by the crew.
+Data Type: varchar(255), NULL
+Examples: Investigate, Enforce code, Information, investigation & enforcement, other
+
+Column Name: ApparatusSuppressionCount, ApparatusEMSCount, ApparatusOtherCount, ApparatusTotalCount
+Description: A set of columns that counts the number of fire apparatus (vehicles) that responded, broken down by type: Suppression (fire engines), EMS (ambulances), Other, and a Total count.
+Data Type: int, NULL
+Examples: 1, 0, 0, 1
+
+Column Name: PersonnelSuppressionCount, PersonnelEMSCount, PersonnelOtherCount, PersonnelTotalCount
+Description: A set of columns that counts the number of personnel who responded, broken down by their role: Suppression, EMS, Other, and a Total count.
+Data Type: int, NULL
+Examples: 3, 0, 0, 3
+
+Column Name: AddressComposite
+Description: A single, concatenated string field that combines the individual address components (Street Number, Prefix, Name, Type, etc.) into a full, formatted street address.
+Data Type: varchar(255), NULL
+Examples: 2601 S REAL RD 77, 327 CHESTNUT AV
+
+Column Name: CityStateZipComposite
+Description: A single, concatenated string field that combines the city, state, and zip code into a single field.
+Data Type: varchar(255), NULL
+Examples: Bakersfield, CA 93309, KERN COUNTY, CA 93305
+
+Column Name: latitude, longitude
+Description: The geographic coordinates (latitude and longitude) of the incident location. These are used for mapping and spatial analysis.
+Data Type: decimal, NULL
+Examples: (35.33065871, -119.0455376)
+
+Column Name: memberdescrip
+Description: The role or description of the crew member who made the report (e.g., "Member Making Report").
+Data Type: varchar(50), NULL
+Examples: Member Making Report
+
+Column Name: memberidnumber
+Description: The unique identifier or employee ID number for the reporting member.
+Data Type: char(10), NULL
+Examples: 326, 298, 128
+
+Column Name: membernamelast, membernamefirst, membermi
+Description: Individual components of the reporting member's name: last name, first name, and middle initial.
+Data Type: varchar(50), varchar(50), char(1), NULL
+Examples: (Last: Taylor, First: Michael, MI: D)
+
+Column Name: memberpositiondescrip
+Description: The job title or rank of the reporting member (e.g., "Captain").
+Data Type: varchar(50), NULL
+Examples: Captain
+
+Column Name: memberassignmentdescrip
+Description: The crew or unit assignment of the reporting member at the time of the incident (e.g., "Suppression").
+Data Type: varchar(50), NULL
+Examples: Suppression

data/rag_input_data/incidentbase_table_details.txt

@@ -0,0 +1,21 @@
+Table Name: auv_incidentbase
+
+This table represents a comprehensive operational dataset that combines incident, apparatus, and personnel participation information for emergency response events. Each record typically represents a personnel assignment to a specific apparatus responding to a particular incident. Because multiple responders may be assigned to the same apparatus, incident and apparatus information may appear repeatedly across multiple rows.
+
+The table acts as a relational bridge between three core operational entities: incidents, apparatus units, and personnel members. Unique identifiers connect each record to the original incident record, the responding apparatus, and the firefighter or responder assigned to that apparatus. This structure allows the system to track exactly which personnel participated in a response and which unit they were assigned to.
+
+Personnel-related information is included in the dataset to provide context about the responders involved in the incident. This includes identifying attributes such as personnel identifiers, names, and rank within the department. Rank information is particularly useful for understanding the command structure and operational hierarchy during emergency response activities.
+
+Operational activity performed during the response is captured through standardized action codes and their textual descriptions. These actions typically follow NFIRS (National Fire Incident Reporting System) standards, which categorize activities such as investigation, suppression, rescue operations, or cancellation events. Multiple action fields allow the system to record several tasks performed during the incident.
+
+The dataset also includes detailed apparatus-level operational attributes. These fields describe the responding unit, its type (such as engine or truck), whether it belongs to the department, the priority of the response, and whether it was the first arriving unit on scene. These attributes provide insight into the role and operational context of each responding vehicle.
+
+A significant portion of the table focuses on response timeline tracking. Multiple timestamp fields capture the lifecycle of the emergency response, including dispatch time, en route time, arrival on scene, hospital transport events, and the time when the unit cleared the incident. Derived duration fields calculate important operational metrics such as turnout time, travel time to the scene, response time, and the total time the apparatus remained committed to the incident.
+
+For incidents involving emergency medical services (EMS), the dataset also includes additional patient care milestones such as arrival at the patient’s side, transport to a medical facility, and arrival at the hospital. These fields allow departments to analyze EMS response performance and patient transport timelines.
+
+Administrative and service recognition information is also included in the dataset. Fields related to LOSAP (Length of Service Award Program) credit indicate whether personnel received service credit for their participation in the incident. These fields are commonly used in volunteer fire departments to track eligibility for service awards or retirement benefits.
+
+Several fields appear duplicated or repeated within the dataset, which suggests that the table may originate from a denormalized reporting view or data export. This design simplifies analytics and reporting by reducing the need for complex joins between multiple operational tables.
+
+Overall, this dataset provides a complete operational view of emergency response activity, capturing incident context, apparatus deployment details, personnel participation, operational actions, and the full response timeline. It is particularly useful for response performance analysis, operational reporting, personnel participation tracking, and compliance with national fire reporting standards such as NFIRS.

data/rag_input_data/incidentpersonnel_columns_details.txt

@@ -0,0 +1,656 @@
+Column Name: incidentkey
+Description: The primary key for the incident table. This is a unique, system-generated 14-character identifier for every incident record. It serves as the fundamental link to all other related tables in the database, such as apparatus and personnel. This value is used to join with the incident table to get incident-level details.
+Data Type: char(14), NOT NULL
+Examples: _4GR15262U_SMS, _4GR15HZEC_SMS, _4GR166YT7_SMS
+
+Column Name: apparatuskey
+Description: The primary key for the apparatus table. This is a unique, system-generated 14-character identifier for a specific apparatus response to an incident. It serves as the primary link between apparatus response records and personnel assignments. It indicates which piece of equipment a person was assigned to for a given incident.
+Data Type: char(14), NOT NULL
+Examples: _4GR15265W_SMS, _4GR15HZF7_SMS, _4GR166YUI_SMS
+
+Column Name: pslid
+Description: A unique, system-generated identifier for an individual firefighter or personnel record. This key links a personnel record to their assignments in an incident. It is the primary identifier used to join with a master personnel table to retrieve static information like name and rank.
+Data Type: char(15), NOT NULL
+Examples: _1XL0XJ7VGDEFA, _26H0W4XBHCPAU, _2FW0KTEBFCPAU
+
+Column Name: personnelid
+Description: An employee or badge number assigned to the firefighter or personnel. This is a human-readable identifier, likely used for payroll, scheduling, or internal identification, and is distinct from the system-generated pslid.
+Data Type: int, NOT NULL
+Examples:
+219, 378, 390
+
+Column Name: namefirst
+Description: The first name of the firefighter or personnel. The data shows it is stored with trailing spaces to pad the value to a fixed length.
+Data Type: char(25), NOT NULL
+Examples:
+Dale, Brandon, Kyle
+
+Column Name: namemi
+Description: The middle initial of the firefighter or personnel. This field may contain a single character, a space, or be blank.
+Data Type: char(2), NULL
+Examples:
+E, A, S
+
+Column Name: namelast
+Description: The last name of the firefighter or personnel. The data shows it is stored with trailing spaces to pad the value to a fixed length.
+Data Type: char(25), NOT NULL
+Examples:
+Bryan, Davis, Coles
+
+Column Name: namesuffix
+Description: A suffix for the personnel's name (e.g., Jr., Sr., III). This field is entirely NULL in the provided data sample.
+Data Type: char(5), NULL
+Examples:
+NULL, NULL, NULL
+
+Column Name: namefirstlast
+Description: A concatenated string of the personnel's first and last name in "First Last" format (e.g., "Dale Bryan"). This is likely a pre-processed field for reporting or display purposes.
+Data Type: varchar(51), NOT NULL
+Examples:
+Dale Bryan, Brandon Davis, Kyle Coles
+
+Column Name: namelastfirst
+Description: A concatenated string of the personnel's last and first name in "Last, First" format (e.g., "Bryan, Dale"). This is likely a pre-processed field for reporting or display purposes, such as in lists sorted by last name.
+Data Type: varchar(51), NOT NULL
+Examples:
+Bryan, Dale, Davis, Brandon, Coles, Kyle
+
+Column Name: namefull
+Description: The full name of the personnel, including first name, middle initial, and last name (e.g., "Dale E Bryan"). This is likely a pre-processed field for display purposes.
+Data Type: varchar(77), NOT NULL
+Examples:
+Dale E Bryan, Brandon A Davis, Kyle S Coles
+
+Column Name: rank
+Description: The rank or title of the firefighter (e.g., Captain, Firefighter, Engineer). This is used to identify the role and seniority of the personnel on the incident scene.
+Data Type: char(10), NOT NULL
+Examples:
+CAPT, FF, ENG
+
+Column Name: actiontaken1code
+Description: A code representing the primary action taken by the personnel on the incident. This field is likely a foreign key to a reference table of action codes.
+Data Type: int, NULL
+Examples:
+NULL, NULL, 93
+
+Column Name: actiontaken1descip
+Description: A textual description corresponding to the actiontaken1code. This provides a human-readable explanation of the primary action taken (e.g., "Cancelled en route").
+Data Type: varchar(50), NULL
+Examples:
+NULL, NULL, Cancelled en route
+
+Column Name: actiontaken2code
+Description: A code representing a secondary action taken by the personnel on the incident. This field is likely a foreign key to a reference table of action codes.
+Data Type: int, NULL
+Examples:
+NULL, NULL, NULL
+
+Column Name: actiontaken2descip
+Description: A textual description corresponding to the actiontaken2code. This provides a human-readable explanation of the secondary action taken.
+Data Type: varchar(50), NULL
+Examples:
+NULL, NULL, NULL
+
+Column Name: actiontaken3code
+Description: A code representing a tertiary action taken by the personnel on the incident. This field is likely a foreign key to a reference table of action codes.
+Data Type: int, NULL
+Examples:
+NULL, NULL, NULL
+
+Column Name: actiontaken3descip
+Description: A textual description corresponding to the actiontaken3code. This provides a human-readable explanation of the tertiary action taken.
+Data Type: varchar(50), NULL
+Examples:
+NULL, NULL, NULL
+
+Column Name: actiontaken4code
+Description: A code representing a quaternary action taken by the personnel on the incident. This field is likely a foreign key to a reference table of action codes.
+Data Type: int, NULL
+Examples:
+NULL, NULL, NULL
+
+Column Name: actiontaken4descip
+Description: A textual description corresponding to the actiontaken4code. This provides a human-readable explanation of the quaternary action taken.
+Data Type: varchar(50), NULL
+Examples:
+NULL, NULL, NULL
+
+Column Name: amount1
+Description: A generic numeric field, likely used for various purposes depending on the context of the action taken or a specific data collection requirement. In this dataset, it is predominantly NULL.
+Data Type: float, NULL
+Examples:
+NULL, NULL, NULL
+
+Column Name: amount2
+Description: A secondary generic numeric field, likely used for various purposes depending on the context of the action taken or a specific data collection requirement. In this dataset, it is predominantly NULL.
+Data Type: float, NULL
+Examples:
+NULL, NULL, NULL
+
+Column Name: crole
+Description: A numeric code indicating the specific role of the personnel on the incident or apparatus assignment (e.g., officer, driver, firefighter). This is distinct from their permanent rank and specific to the call.
+Data Type: int, NULL
+Examples:
+NULL, NULL, NULL
+
+Column Name: losapcreditcode
+Description: A numeric code indicating whether the personnel received LOSAP (Length of Service Award Program) credit for their participation in this incident.
+Data Type: int, NULL
+Examples:
+1, 1, 1
+
+Column Name: losapcreditdescrip
+Description: A textual description corresponding to the losapcreditcode, indicating whether LOSAP credit was awarded (e.g., "Losap Credit").
+Data Type: varchar(50), NULL
+Examples:
+Losap Credit, Losap Credit, Losap Credit
+
+Column Name: incidentkey (duplicate)
+Description: (Duplicate) The primary key for the incident table, repeated here likely to facilitate joins or reporting within this dataset.
+Data Type: char(14), NOT NULL
+Examples:
+_4GR15262U_SMS, _4GR15HZEC_SMS, _4GR166YT7_SMS
+
+Column Name: apparatuskey (duplicate)
+Description: (Duplicate) The primary key for the apparatus table, repeated here likely to facilitate joins or reporting within this dataset.
+Data Type: char(14), NOT NULL
+Examples:
+_4GR15265W_SMS, _4GR15HZF7_SMS, _4GR166YUI_SMS
+
+Column Name: apparatusid
+Description: A human-readable identifier or "unit number" for the apparatus (e.g., "BE7", "BE6", "BE3"). This is the identifier used in radio communications and daily operations to refer to the vehicle.
+Data Type: char(10), NOT NULL
+Examples:
+BE7, BE6, BE3
+
+Column Name: deptunitornotcode
+Description: A numeric code indicating whether the apparatus is a department-owned unit or from another agency/service. A value of 0 likely means it is a department unit.
+Data Type: int, NOT NULL
+Examples:
+0, 0, 0
+
+Column Name: deptunitornotdescrip
+Description: A textual description corresponding to the deptunitornotcode, indicating if the apparatus is a department unit (e.g., "DeptUnit").
+Data Type: varchar(50), NOT NULL
+Examples:
+DeptUnit, DeptUnit, DeptUnit
+
+Column Name: priorityresponsecode
+Description: A numeric code indicating the priority of the response (e.g., emergency vs. non-emergency). A value of 1 typically signifies an emergency response (lights and sirens).
+Data Type: int, NOT NULL
+Examples:
+1, 1, 1
+
+Column Name: priorityresponsedescrip
+Description: A textual description corresponding to the priorityresponsecode. This confirms the response priority, e.g., "Yes" for emergency, "No" for non-emergency.
+Data Type: varchar(50), NOT NULL
+Examples:
+Yes, Yes, Yes
+
+Column Name: cancelledenroutecode
+Description: A numeric code indicating whether the apparatus was cancelled while en route to the incident. A value of 1 typically means "Yes", 0 means "No".
+Data Type: int, NOT NULL
+Examples:
+0, 1, 1
+
+Column Name: cancelledenroutedescrip
+Description: A textual description corresponding to the cancelledenroutecode. This indicates if the unit was cancelled en route, e.g., "No" or "Yes".
+Data Type: varchar(50), NOT NULL
+Examples:
+No, Yes, Yes
+
+Column Name: firstarrivingunitcode
+Description: A numeric code indicating whether this apparatus was the first to arrive on the scene of the incident. A value of 1 means "Yes", 0 means "No".
+Data Type: int, NOT NULL
+Examples:
+1, 0, 1
+
+Column Name: firstarrivingunitdescrip
+Description: A textual description corresponding to the firstarrivingunitcode. This confirms if the unit was the first to arrive, e.g., "Yes" or "No".
+Data Type: varchar(50), NOT NULL
+Examples:
+Yes, No, Yes
+
+Column Name: dispatchtype
+Description: A numeric code representing the type of dispatch (e.g., how the call was received or categorized). This field is often NULL.
+Data Type: int, NULL
+Examples:
+NULL, NULL, NULL
+
+Column Name: dispatchtypedescrip
+Description: A textual description corresponding to the dispatchtype. This field is often NULL.
+Data Type: varchar(50), NULL
+Examples:
+NULL, NULL, NULL
+
+Column Name: respondedfromquarterscode
+Description: A numeric code indicating whether the apparatus responded directly from its quarters/station. A value of 1 likely means "Yes", 0 means "No".
+Data Type: int, NOT NULL
+Examples:
+0, 0, 0
+
+Column Name: respondedfromquarterdescrip
+Description: A textual description corresponding to the respondedfromquarterscode. This indicates if the response was from quarters, e.g., "No" (meaning they were likely already in service or responding from another location).
+Data Type: varchar(50), NOT NULL
+Examples:
+No, No, No
+
+Column Name: mainapparatususecode
+Description: A numeric code describing the primary function or use of the apparatus (e.g., suppression, rescue). A value of 1 indicates suppression.
+Data Type: int, NOT NULL
+Examples:
+1, 1, 1
+
+Column Name: mainapparatususedescrip
+Description: A textual description corresponding to the mainapparatususecode, describing the apparatus's primary function (e.g., "Suppression").
+Data Type: varchar(50), NOT NULL
+Examples:
+Suppression, Suppression, Suppression
+
+Column Name: apparatustypecode
+Description: A numeric code representing the specific type of apparatus (e.g., engine, truck, ambulance). A value of 11 indicates an engine, 12 indicates a truck/aerial.
+Data Type: int, NOT NULL
+Examples:
+11, 11, 11
+
+Column Name: apparatustypedescrip
+Description: A textual description corresponding to the apparatustypecode, providing the type of vehicle (e.g., "Engine", "Truck or aerial").
+Data Type: varchar(50), NOT NULL
+Examples:
+Engine, Engine, Engine
+
+Column Name: actiontaken1code (duplicate)
+Description: (Duplicate) A code representing the primary action taken by the apparatus on the incident. This is likely the same as the personnel-level action code.
+Data Type: int, NULL
+Examples:
+NULL, 93, 86
+
+Column Name: actiontaken1descip (duplicate)
+Description: (Duplicate) A textual description corresponding to the apparatus-level actiontaken1code.
+Data Type: varchar(50), NULL
+Examples:
+NULL, Cancelled en route, Investigate
+
+Column Name: actiontaken2code (duplicate)
+Description: (Duplicate) A code representing a secondary action taken by the apparatus.
+Data Type: int, NULL
+Examples:
+NULL, NULL, NULL
+
+Column Name: actiontaken2descip (duplicate)
+Description: (Duplicate) A textual description corresponding to the apparatus-level actiontaken2code.
+Data Type: varchar(50), NULL
+Examples:
+NULL, NULL, NULL
+
+Column Name: actiontaken3code (duplicate)
+Description: (Duplicate) A code representing a tertiary action taken by the apparatus.
+Data Type: int, NULL
+Examples:
+NULL, NULL, NULL
+
+Column Name: actiontaken3descip (duplicate)
+Description: (Duplicate) A textual description corresponding to the apparatus-level actiontaken3code.
+Data Type: varchar(50), NULL
+Examples:
+NULL, NULL, NULL
+
+Column Name: actiontaken4code (duplicate)
+Description: (Duplicate) A code representing a quaternary action taken by the apparatus.
+Data Type: int, NULL
+Examples:
+NULL, NULL, NULL
+
+Column Name: actiontaken4descip (duplicate)
+Description: (Duplicate) A textual description corresponding to the apparatus-level actiontaken4code.
+Data Type: varchar(50), NULL
+Examples:
+NULL, NULL, NULL
+
+Column Name: numberofresponders
+Description: The total number of personnel who responded on this apparatus to the incident.
+Data Type: int, NOT NULL
+Examples:
+3, 3, 3
+
+Column Name: dispatchdatetime
+Description: The combined date and time the apparatus was dispatched to the incident. Stored as a string in the format "HH:MM.ss" or similar.
+Data Type: nvarchar(255), NULL
+Examples:
+08:31.0, 20:21.0, 39:16.0
+
+Column Name: dispatchtime
+Description: The time the apparatus was dispatched, represented in a 24-hour format (e.g., 19:08:31 for 7:08:31 PM).
+Data Type: nvarchar(255), NULL
+Examples:
+19:08:31, 19:20:21, 19:39:16
+
+Column Name: dispatchdate
+Description: The date the apparatus was dispatched, in MM/DD/YYYY format.
+Data Type: nvarchar(255), NULL
+Examples:
+10/9/2015, 10/9/2015, 10/9/2015
+
+Column Name: dispatchenroutetime
+Description: The duration between the dispatch time and the time the unit went en route. Formatted as HH:MM:SS.
+Data Type: nvarchar(255), NULL
+Examples:
+0:00:44, 0:01:15, NULL
+
+Column Name: dispatchenroutediffseconds
+Description: The dispatchenroutetime expressed in total seconds. Useful for calculating average response times.
+Data Type: int, NULL
+Examples:
+44, 75, 0
+
+Column Name: enroutetoscenedatetime
+Description: The combined date and time the apparatus marked that it was en route to the scene.
+Data Type: nvarchar(255), NULL
+Examples:
+09:15.0, 21:36.0, 00:00.0
+
+Column Name: enroutetoscenetime
+Description: The time the apparatus marked en route, in a 24-hour format.
+Data Type: nvarchar(255), NULL
+Examples:
+19:09:15, 19:21:36, 
+
+Column Name: enroutetoscenedate
+Description: The date the apparatus marked en route.
+Data Type: nvarchar(255), NULL
+Examples:
+10/9/2015, 10/9/2015, NULL
+
+Column Name: enroutearrivalscenetime
+Description: The duration between the unit marking en route and its arrival on the scene. Formatted as HH:MM:SS.
+Data Type: nvarchar(255), NULL
+Examples:
+0:01:55, 0:03:37, NULL
+
+Column Name: enroutearrivalscenediffseconds
+Description: The enroutearrivalscenetime expressed in total seconds.
+Data Type: int, NULL
+Examples:
+115, 217, 0
+
+Column Name: responsetime
+Description: The total duration from dispatch to arrival on scene. Formatted as HH:MM:SS.
+Data Type: nvarchar(255), NULL
+Examples:
+0:02:39, 0:04:52, 0:00:00
+
+Column Name: responsetimeseconds
+Description: The total responsetime expressed in seconds. This is a critical metric for performance analysis.
+Data Type: int, NULL
+Examples:
+159, 292, 0
+
+Column Name: arrivaldatetime
+Description: The combined date and time the apparatus arrived on the scene.
+Data Type: nvarchar(255), NULL
+Examples:
+11:10.0, 25:13.0, 00:00.0
+
+Column Name: arrivaltime
+Description: The time the apparatus arrived on the scene, in a 24-hour format.
+Data Type: nvarchar(255), NULL
+Examples:
+19:11:10, 19:25:13, 
+
+Column Name: arrivaldate
+Description: The date the apparatus arrived on the scene.
+Data Type: nvarchar(255), NULL
+Examples:
+10/9/2015, 10/9/2015, NULL
+
+Column Name: arrivaltoenroutehospdifftime
+Description: The duration between arrival on scene and the unit going en route to a hospital (for EMS calls). This field is largely NULL for non-EMS runs.
+Data Type: nvarchar(255), NULL
+Examples:
+NULL, NULL, NULL
+
+Column Name: arrivaltoenroutehospdiffseconds
+Description: The arrivaltoenroutehospdifftime expressed in seconds.
+Data Type: int, NULL
+Examples:
+0, 0, 0
+
+Column Name: enroutetohospitaldatetime
+Description: The combined date and time the unit went en route to the hospital.
+Data Type: nvarchar(255), NULL
+Examples:
+00:00.0, 00:00.0, 00:00.0
+
+Column Name: enroutetohospitaltime
+Description: The time the unit went en route to the hospital.
+Data Type: nvarchar(255), NULL
+Examples:
+, , 
+
+Column Name: enroutetohospitaldate
+Description: The date the unit went en route to the hospital.
+Data Type: nvarchar(255), NULL
+Examples:
+NULL, NULL, NULL
+
+Column Name: enroutetoarrivalhospdifftime
+Description: The duration between going en route to the hospital and arriving at the hospital. This field is largely NULL.
+Data Type: nvarchar(255), NULL
+Examples:
+NULL, NULL, NULL
+
+Column Name: enroutetoarrivalhospdiffseconds
+Description: The enroutetoarrivalhospdifftime expressed in seconds.
+Data Type: int, NULL
+Examples:
+0, 0, 0
+
+Column Name: arrivalscenetoarrivalhospdifftime
+Description: The total duration from arrival on scene to arrival at the hospital (for patient transports). This field is largely NULL.
+Data Type: nvarchar(255), NULL
+Examples:
+NULL, NULL, NULL
+
+Column Name: arrivalscenetoarrivalhospdiffseconds
+Description: The arrivalscenetoarrivalhospdifftime expressed in seconds.
+Data Type: int, NULL
+Examples:
+0, 0, 0
+
+Column Name: hospitalarrivaldatetime
+Description: The combined date and time the apparatus arrived at the hospital.
+Data Type: nvarchar(255), NULL
+Examples:
+00:00.0, 00:00.0, 00:00.0
+
+Column Name: hospitalarrivaltime
+Description: The time the apparatus arrived at the hospital.
+Data Type: nvarchar(255), NULL
+Examples:
+, , 
+
+Column Name: hospitalarrivaldate
+Description: The date the apparatus arrived at the hospital.
+Data Type: nvarchar(255), NULL
+Examples:
+NULL, NULL, NULL
+
+Column Name: arrivalclearhospdifftime
+Description: The duration between arrival at the hospital and the unit clearing (becoming available) from the hospital. This field is largely NULL.
+Data Type: nvarchar(255), NULL
+Examples:
+NULL, NULL, NULL
+
+Column Name: arrivalclearhospdiffseconds
+Description: The arrivalclearhospdifftime expressed in seconds.
+Data Type: int, NULL
+Examples:
+0, 0, 0
+
+Column Name: cleardatetime
+Description: The combined date and time the apparatus cleared the incident and became available for service.
+Data Type: nvarchar(255), NULL
+Examples:
+16:17.0, 40:39.0, 41:06.0
+
+Column Name: cleartime
+Description: The time the apparatus cleared the incident, in a 24-hour format.
+Data Type: nvarchar(255), NULL
+Examples:
+19:16:17, 19:40:39, 19:41:06
+
+Column Name: cleardate
+Description: The date the apparatus cleared the incident.
+Data Type: nvarchar(255), NULL
+Examples:
+10/9/2015, 10/9/2015, 10/9/2015
+
+Column Name: dispatchcleardifftime
+Description: The total duration from initial dispatch to the unit clearing the incident. Formatted as HH:MM:SS.
+Data Type: nvarchar(255), NULL
+Examples:
+0:07:46, 0:20:18, 0:01:50
+
+Column Name: dispatchcleardiffseconds
+Description: The total dispatchcleardifftime expressed in seconds. This represents the total time the unit was committed to the incident.
+Data Type: int, NULL
+Examples:
+466, 1218, 110
+
+Column Name: inservicedatetime
+Description: The combined date and time the unit was marked as "in service" or available at the start of their shift. This field is largely NULL or 00:00.0.
+Data Type: nvarchar(255), NULL
+Examples:
+00:00.0, 00:00.0, 00:00.0
+
+Column Name: inservicetime
+Description: The time the unit was marked "in service".
+Data Type: nvarchar(255), NULL
+Examples:
+, , 
+
+Column Name: inservicedate
+Description: The date the unit was marked "in service".
+Data Type: nvarchar(255), NULL
+Examples:
+NULL, NULL, NULL
+
+Column Name: emsruncode
+Description: A code or identifier for an EMS (Emergency Medical Services) run, if applicable. The value "Not EMS Run" indicates this was not an EMS incident.
+Data Type: nvarchar(255), NULL
+Examples:
+Not EMS Run, Not EMS Run, Not EMS Run
+
+Column Name: emsrundescrip
+Description: A description of the EMS run. This field is largely NULL.
+Data Type: nvarchar(255), NULL
+Examples:
+NULL, NULL, NULL
+
+Column Name: emsrunnumber
+Description: A specific run number for the EMS call. This field is largely NULL.
+Data Type: nvarchar(255), NULL
+Examples:
+NULL, NULL, NULL
+
+Column Name: losapcode
+Description: A code indicating LOSAP credit, similar to losapcreditcode.
+Data Type: int, NULL
+Examples:
+1, 1, 1
+
+Column Name: losapdescrip
+Description: A description of the LOSAP credit, similar to losapcreditdescrip.
+Data Type: nvarchar(255), NULL
+Examples:
+Losap Credit, Losap Credit, Losap Credit
+
+Column Name: alarmscode
+Description: A code indicating the alarm level or type for the incident. This field is largely NULL.
+Data Type: int, NULL
+Examples:
+NULL, NULL, NULL
+
+Column Name: alarmdescrip
+Description: A description of the alarm level. This field is largely NULL.
+Data Type: nvarchar(255), NULL
+Examples:
+NULL, NULL, NULL
+
+Column Name: amount1 (duplicate)
+Description: (Duplicate) Another instance of the generic amount1 field, likely for apparatus-level data. Predominantly NULL.
+Data Type: float, NULL
+Examples:
+NULL, NULL, NULL
+
+Column Name: amount2 (duplicate)
+Description: (Duplicate) Another instance of the generic amount2 field, likely for apparatus-level data. Predominantly NULL.
+Data Type: float, NULL
+Examples:
+NULL, NULL, NULL
+
+Column Name: fdid_no
+Description: The Fire Department ID number or identifier. This field is consistently NULL in the provided sample.
+Data Type: nvarchar(255), NULL
+Examples:
+NULL, NULL, NULL
+
+Column Name: stagingdatetime
+Description: The combined date and time the apparatus went to a staging area. This field is largely NULL or 00:00.0.
+Data Type: nvarchar(255), NULL
+Examples:
+00:00.0, 00:00.0, 00:00.0
+
+Column Name: stagingtime
+Description: The time the apparatus went to a staging area.
+Data Type: nvarchar(255), NULL
+Examples:
+, , 
+
+Column Name: stagingdate
+Description: The date the apparatus went to a staging area.
+Data Type: nvarchar(255), NULL
+Examples:
+NULL, NULL, NULL
+
+Column Name: AtPatientSideDateTime
+Description: The combined date and time the personnel arrived at the patient's side (for EMS incidents). This field is largely NULL or 00:00.0.
+Data Type: nvarchar(255), NULL
+Examples:
+00:00.0, 00:00.0, 00:00.0
+
+Column Name: AtPatientSideTime
+Description: The time the personnel arrived at the patient's side.
+Data Type: nvarchar(255), NULL
+Examples:
+, , 
+
+Column Name: AtPatientSideDate
+Description: The date the personnel arrived at the patient's side.
+Data Type: nvarchar(255), NULL
+Examples:
+NULL, NULL, NULL
+
+Column Name: FacilityDateTime
+Description: The combined date and time the personnel arrived at a medical facility. This field is largely NULL or 00:00.0.
+Data Type: nvarchar(255), NULL
+Examples:
+00:00.0, 00:00.0, 00:00.0
+
+Column Name: FacilityTime
+Description: The time the personnel arrived at a medical facility.
+Data Type: nvarchar(255), NULL
+Examples:
+, , 
+
+Column Name: FacilityDate
+Description: The date the personnel arrived at a medical facility.
+Data Type: nvarchar(255), NULL
+Examples:
+NULL, NULL, NULL
+
+Column Name: changedate
+Description: The date and time the record was last updated or changed. The format appears to be a floating-point number representing time, possibly the number of minutes or seconds after a reference point.
+Data Type: float, NULL
+Examples:
+17:39.0, 42:11.5, 48:24.5

data/rag_input_data/incidentpersonnel_table_details.txt

@@ -0,0 +1,21 @@
+Table Name: auv_incidentpersonnel
+
+This table represents a comprehensive operational dataset that combines incident, apparatus response, and personnel participation details for emergency response events. Each record generally represents a firefighter or personnel member assigned to a specific apparatus during a particular incident. Because multiple personnel can be assigned to the same apparatus, incident and apparatus information may appear multiple times across rows.
+
+The dataset forms a relational bridge between three core operational entities: incidents, apparatus units, and personnel. A unique incident identifier links each record back to the main incident dataset, while a separate apparatus identifier represents the specific vehicle or response unit involved in the incident. Personnel identifiers link individual firefighters to their assignments, allowing the system to track which responders participated in each response and which apparatus they were assigned to.
+
+Personnel-related information in the dataset provides identifying and organizational context about responders. This includes employee identifiers, names, and rank within the fire department. Rank information helps identify the command hierarchy and roles of personnel during emergency operations, while additional fields capture the specific operational role a responder may have had during a particular incident.
+
+Operational activities are recorded through standardized action codes that represent tasks performed during the response. These codes typically follow standardized emergency response reporting systems such as the National Fire Incident Reporting System (NFIRS). Multiple action fields allow the dataset to capture a sequence of activities performed by both individual personnel and the apparatus crew during the incident.
+
+The dataset also contains apparatus-level operational attributes that describe the responding unit. These attributes include the apparatus identifier, apparatus type, operational role, and departmental ownership. Additional indicators describe operational conditions such as whether the response was high priority, whether the apparatus was cancelled while en route, whether it responded directly from the station, and whether it was the first unit to arrive on the scene.
+
+A significant portion of the dataset captures the timeline of the response lifecycle. Multiple timestamp fields record key milestones such as dispatch time, acknowledgement of dispatch, travel to the scene, arrival on scene, clearing the incident, and returning to service. The table also includes calculated duration metrics such as turnout time, travel time, response time, and total committed time for the apparatus. These measurements are commonly used for operational performance analysis and response time reporting.
+
+For incidents involving emergency medical services (EMS), the dataset includes additional patient care milestones such as arrival at the patient’s side, transport to a medical facility, and arrival at a hospital. When incidents do not involve EMS transport, these fields typically remain empty.
+
+Administrative and service-related fields are also present in the dataset. These include indicators for LOSAP (Length of Service Award Program) credit, which tracks participation eligibility for service recognition programs commonly used by volunteer fire departments. Additional metadata fields track record modifications, staging activities, and optional numeric fields used for reporting or operational metrics.
+
+Some columns appear duplicated or consistently null, suggesting that the table originates from a denormalized reporting view or export designed to simplify analytics and reporting. This structure allows incident, apparatus, and personnel information to be analyzed together without requiring complex joins across multiple tables.
+
+Overall, this dataset provides a detailed operational view of emergency response activities by capturing the relationships between incidents, apparatus units, and personnel, along with the actions performed and the full response timeline. It is particularly useful for operational reporting, responder participation tracking, apparatus utilization analysis, and emergency response performance evaluation.

data/rag_input_data/personnel_columns_details.txt

@@ -0,0 +1,149 @@
+Column Name: personnelkey
+Description: The primary key for the personnel table. This is a unique, system-generated 14-character identifier for every firefighter or personnel record. It serves as the fundamental link to all other related tables in the database, such as apparatus, incident, and supplemental data. This value is used to join with the apparatus table to link personnel to a specific apparatus assignment.
+Data Type: char(14), NOT NULL
+Examples: _48Y00K5KE_SMS, _48Y00K5KF_SMS, _48Y00K5KG_SMS
+
+Column Name: incidentkey
+Description: The primary key for the incident table. This is a unique, system-generated 14-character identifier for every incident record. It serves as the fundamental link to all other related tables in the database, such as apparatus, personnel, and supplemental data. This value is used to join with the incident table to get incident-level details.
+Data Type: char(14), NOT NULL
+Examples: _48Y00K5I8_SMS, _48Y00K5IA_SMS, _48Y00JH1N_SMS
+
+Column Name: apparatuskey
+Description: The primary key for the apparatus table. This is a unique, system-generated 14-character identifier for a specific apparatus response to an incident. It serves as the primary link between apparatus response records and personnel assignments. It indicates which piece of equipment a person was assigned to for a given incident.
+Data Type: char(14), NULL
+Examples: _48Y00K5JZ_SMS, _48Y00K5J4_SMS, _48Y00K5L9_SMS
+
+Column Name: pslid
+Description: An identifier for a personnel assignment. This is a system-generated identifier that likely represents a unique combination of a person and a shift or assignment for a specific period. It can be used to link to a shift or assignment table to determine which station or apparatus a person was assigned to for that day.
+Data Type: char(14), NULL
+Examples: _1XL0VELG6DEFA, _1XL0Y55W0DEFA, _3UH0YU1COSMAG
+
+Column Name: rosid
+Description: Unknown. This field appears to be entirely NULL in the sample data, suggesting it may be a legacy field or one used for a very specific, infrequent purpose (e.g., "Report of Service" ID).
+Data Type: char(14), NULL
+Examples: NULL
+
+Column Name: personnelid
+Description: A unique, human-readable identifier for each individual. This number is likely used for payroll, internal tracking, and linking to other systems. It is distinct from the system-generated personnelkey and may correspond to employee or badge numbers.
+Data Type: char(9), NULL (but likely NOT NULL in practice)
+Examples: 359, 326, 436
+
+Column Name: lastname
+Description: The last name of the firefighter or personnel member.
+Data Type: char(25), NULL
+Examples: Woodard, Taylor, Topete
+
+Column Name: firstname
+Description: The first name of the firefighter or personnel member.
+Data Type: char(25), NULL
+Examples: Randall, Michael, Adrian
+
+Column Name: middleinitial
+Description: The middle initial of the firefighter or personnel member.
+Data Type: char(1), NULL
+Examples: E, D, T
+
+Column Name: namesuffix
+Description: A suffix for the name, such as Jr., Sr., III. This field appears to be mostly NULL.
+Data Type: char(4), NULL
+Examples: NULL
+
+Column Name: rank
+Description: The rank or title of the firefighter (e.g., Engineer, Captain, Firefighter). This is used for determining roles, pay grades, and command structure.
+Data Type: char(10), NULL
+Examples: ENG, CAPT, FF
+
+Column Name: actiontaken1
+Description: A code representing the primary action taken by this personnel member. These are likely standardized codes (e.g., NFIRS codes). The sample shows "93" which corresponds to "Mutual Aid Received", indicating the personnel member was part of a mutual aid response.
+Data Type: char(4), NULL
+Examples: NULL, 93, 86
+
+Column Name: actiontaken2
+Description: A code representing a secondary action taken by this personnel member.
+Data Type: char(4), NULL
+Examples: NULL
+
+Column Name: actiontaken3
+Description: A code representing a third action taken by this personnel member.
+Data Type: char(4), NULL
+Examples: NULL
+
+Column Name: actiontaken4
+Description: A code representing a fourth action taken by this personnel member.
+Data Type: char(4), NULL
+Examples: NULL
+
+Column Name: amount1
+Description: A monetary amount associated with the personnel, potentially related to overtime pay, stipends, or specialized service fees for a particular incident.
+Data Type: money, NULL
+Examples: NULL
+
+Column Name: amount2
+Description: A second monetary amount.
+Data Type: money, NULL
+Examples: NULL
+
+Column Name: changedate
+Description: The timestamp when the record was last changed. This is used for auditing and tracking data modifications.
+Data Type: datetime, NULL
+Examples: 35:07.7, 35:08.1, 35:09.1
+
+Column Name: rowguid
+Description: A globally unique identifier (GUID) for the row, often used for replication and system-level tracking. The ROWGUIDCOL property indicates this column is used by SQL Server for operations like replication.
+Data Type: uniqueidentifier, NOT NULL
+Examples: A58628E4-154E-4369-AA48-B6AA569CABEA, 66660C59-3899-463F-8268-C09209928414
+
+Column Name: crole
+Description: A code representing a special role the person played at the incident (e.g., Safety Officer, Incident Commander). This field appears to be NULL in the sample data.
+Data Type: char(4), NULL
+Examples: NULL
+
+Column Name: lLosap_credit
+Description: A boolean flag indicating eligibility for LOSAP (Length of Service Award Program) credit. A value of 1 likely means credit is earned for this incident, while 0 means it is not.
+Data Type: bit, NULL
+Examples: 1, 0
+
+Column Name: MedCert
+Description: A code representing the level of medical certification for the personnel at the time of the incident (e.g., EMT, Paramedic). This field appears to be NULL in the sample data.
+Data Type: char(4), NULL
+Examples: NULL
+
+Column Name: cAdditionalRole
+Description: An additional role the person might have fulfilled, which is not captured by other role codes. This field appears to be NULL in the sample data.
+Data Type: varchar(8), NULL
+Examples: NULL
+
+Column Name: AgencyID
+Description: An identifier for a specific agency, used when the personnel is from another department, such as in a mutual aid context. This would link to an agency table for details.
+Data Type: varchar(14), NULL
+Examples: NULL
+
+Column Name: AgencyDesc
+Description: A description of the agency identified in AgencyID. This field appears to be NULL in the sample data.
+Data Type: varchar(40), NULL
+Examples: NULL
+
+Column Name: AgencyCode
+Description: A short code for the agency. This field appears to be NULL in the sample data.
+Data Type: varchar(8), NULL
+Examples: NULL
+
+Column Name: lNFIRSExported
+Description: A boolean flag indicating whether the personnel record has been successfully formatted and exported for NFIRS (National Fire Incident Reporting System). A value of 1 likely indicates it has been exported, while 0 indicates it is pending.
+Data Type: bit, NULL
+Examples: 1, 0
+
+Column Name: NFIRSExportedDate
+Description: The date and time when the record was exported for NFIRS. This is used for tracking and auditing exports.
+Data Type: datetime, NULL
+Examples: 35:07.0, 35:08.0
+
+Column Name: iNFIRSSequence
+Description: A sequence number for records when multiple are exported in a single NFIRS batch. This helps maintain order and group related records together.
+Data Type: tinyint, NULL
+Examples: 1, 2, 3
+
+Column Name: NFIRSTransactiontype
+Description: The type of NFIRS transaction, such as an insert (A), update (U), or delete (D). This field is crucial for data synchronization and reporting systems to understand how to process the record. In the sample, a blank space may represent an "Insert" transaction.
+Data Type: char(1), NULL
+Examples:  (blank),  (blank),  (blank)

data/rag_input_data/personnel_table_details.txt

@@ -0,0 +1,19 @@
+Table Name: personnel
+
+The personnel table stores detailed information about firefighters and emergency response personnel who participate in incident responses. Each record represents a personnel member and their participation in a specific incident or apparatus assignment. The table links individuals to emergency events and the apparatus units they were assigned to, allowing the system to track which responders were involved in each response.
+
+This table plays a key role in connecting multiple operational entities within the emergency response system. It uses unique identifiers to link personnel to incident records and apparatus response records, forming a relational structure that captures the association between a person, the vehicle or unit they responded with, and the incident itself. This relationship enables accurate tracking of responder participation across multiple emergency events.
+
+The dataset also contains identifying and descriptive information about the personnel, including their names, internal personnel identifiers, and ranks within the organization. These attributes provide context about the individual responder and help define the operational hierarchy during incidents. Rank information is particularly important for understanding command structure and responsibilities during emergency operations.
+
+Operational activity is captured through standardized action codes that represent the actions taken by personnel during an incident. These codes follow the NFIRS (National Fire Incident Reporting System) standards, which are used by fire departments to classify response activities such as suppression, investigation, or mutual aid participation. Multiple action fields allow the system to record several actions performed by the same responder during the incident.
+
+The table may also include administrative or financial attributes associated with personnel involvement. These can include monetary fields that represent stipends, overtime, or other compensation-related values tied to incident participation. In addition, flags such as LOSAP credit indicators allow departments to track eligibility for Length of Service Award Program benefits, which are often used for volunteer firefighter recognition programs.
+
+Several fields support integration with external reporting systems, particularly NFIRS reporting requirements. Export flags, export timestamps, and sequence numbers help track whether the personnel record has been exported to national reporting systems and maintain synchronization between local systems and federal reporting databases.
+
+The table also supports multi-agency response scenarios. Fields related to agency identifiers and agency descriptions allow personnel from other departments or mutual aid agencies to be recorded within the system. This enables comprehensive tracking of collaborative responses where multiple fire departments or emergency agencies respond to the same incident.
+
+Additional metadata fields such as GUID identifiers and change timestamps support auditing, replication, and system-level tracking. These attributes ensure that the database can maintain data integrity, support synchronization processes, and track when personnel records were last modified.
+
+Overall, the personnel table serves as a central dataset for tracking responder participation in emergency incidents. It provides the connection between individual firefighters, the apparatus units they were assigned to, and the incidents they responded to, while also supporting operational reporting, administrative tracking, and national incident reporting standards.